[lkml]   [1996]   [Apr]   [29]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
Messages in this thread
SubjectRe: 3C509 not being detected in 1.3.95
>>>>> "Jay" == anderson  <> writes:

Jay> I have a WD8003 and 3C509 in my system. Both cards were being
Jay> detected just fine until about 1.3.93, then the 3C509 stopped
Jay> being detected. I was able to compile it as a module in .94 and
Jay> insmod it sucessfully, but even that failed in .95.

Jay> I'm a bit stumped as what to try next (aside from looking through
Jay> the past 2 or 3 patches and try to find out what changed).

Jay> Is anyone else seeing this or is just me?

I had a problem that sounds similar to this. I've got a machine with
both a WD8013 and 3c509. The 3c509 was not often recognized on boot
without opening the machine reseating the card and rebooting. It did
not matter whether it was eth0 or eth1, coax or 10baseT, and I always
compiled the drivers straight in not modules, and did the append
"ether=..." thing in /etc/lilo.conf. (Kernel versions 1.2.1 through
1.2.13 and 1.3.73 through 1.3.8?).

My problem was apparently due to a conflict between the Boca 4 port
serial and the 3c509. I compiled a test kernel at one point with
module support for the 3c509, but then couldn't load the driver due to
an addressing conflict. The 3c509 driver does probing in the same
address range used by the Boca (low 0x100s).

Since I've removed the Boca the 3c509 has been recognized at boot
every time.

-- baur
Unsolicited commercial e-mail will be proofread for $250/hour.
Andrea Seastrand: For your vote on the Telecom bill, I will vote for anyone
except you in November.

 \ /
  Last update: 2005-03-22 13:37    [W:0.028 / U:3.700 seconds]
©2003-2018 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site