Thanks for all the help that I've gotten from everyone about this problem. I've
tried a bunch of stuff over the last few days and I still can't get my ethernet
card running. I've looked at the manual for dhcpcd and tried that command
several times, with the verbose switch it says that it is unable to assign the
requested address. I've tried manually specifying the host address and all the
other stuff you can manually specify using the dhcpcd switches, and nothing
worked.
So I went to the /var/log/message file and had a look through it for any info
that it might give about why it's not working... this is what I found that was
related to my network card:
Apr 9 20:47:05 COOLIE kernel: 3c59x.c:v0.99H 11/17/98 Donald Becker
http://cesdis.gsfc.nasa.gov/linux/drivers/vortex.html
Apr 9 20:47:05 COOLIE kernel: eth0: 3Com 3c900 Boomerang 10baseT at 0xff00,
00:a0:24:d1:45:19, IRQ 10
Apr 9 20:47:05 COOLIE kernel: 8K word-wide RAM 3:5 Rx:Tx split, 10baseT
interface.
Apr 9 20:47:05 COOLIE kernel: Enabling bus-master transmits and whole-frame
receives.
Apr 9 20:46:32 COOLIE kerneld: Starting kerneld, version 2.1.121 (pid 141)
Apr 9 20:46:32 COOLIE kerneld: kerneld startup succeeded
Apr 9 20:46:32 COOLIE kerneld: started, pid=141, qid=0
Apr 9 20:46:32 COOLIE ifup: SIOCADDRT: Network is unreachable
Apr 9 20:46:34 COOLIE network: Bringing up interface lo succeeded
Apr 9 20:46:34 COOLIE ifup: Using DHCP for eth0...
Apr 9 20:46:34 COOLIE dhcpcd[233]: ioctl SIOCSIFBRDADDR (ifConfig): Cannot
assign requested address
Apr 9 20:47:04 COOLIE ifup: failed.
Apr 9 20:47:04 COOLIE network: Bringing up interface eth0 failed
It looks like the dhcpcd command is being executed automatically during the
boot, so it wouldn't make any difference if I tried doing it from the command
line. Can anybody make some sense of what's going on in that log? Being a newbie
I really can't gather any useful info from looking at that log.
Back in Win95, I ran "winipcfg" which brought up a bunch of info about my
network card and configuration for my network. Note that this is all
automatically configured whenever I boot up and log into RoadRunner. This is the
info that I got from winipcfg:
Host Name : COOLIE.san.rr.comDEST
DNS Servers : 204.210.7.33
Node Type : Broadcast
Adapter Address : 00-A0-24-D1-45-19
IP Address : 24.94.4.224
Subnet Mask : 255.255.255.0
Default Gateway : 24.94.4.1
DHCP Server : 204.210.7.33
Primary WINS Server : <blank>
Secondary WINS Server : <blank>
Lease Obtained : Fri Apr 9 99 20:59:10
Lease Expires : Fri Apr 9 99 21:44:10
I figured maybe if I took this info into Linuxconf, I could find someplace to
enter in this info manually. The few places under the Network setup in Linuxconf
already had the correct info that was preconfigured when I initially installed
Linux though. Nothing has changed from when I had the network card working with
the old 2.0.36 kernel. If anybody could lend a hand or point me in the right
direction to fixing this I would be ever so grateful :) I'm damn curious about
what changed in the 2.2.3 kernel that's keeping my card from working properly.
Thanks for the help,
Howard Au
>> > Hi all,
>> >
>> > I installed Mandrake Linux 5.3 (Kernel 2.0.36) for the first time a
>> > couple weeks ago and have been using it problem free. But I recently
>> > installed the RPM's for the Kernel 2.2.3-ac4 upgrade using kpackage,
>> > updated the lilo.conf file, and the new kernel booted just fine, except
>> > that my ethernet card has stopped working. The "using DHCP for eth0"
>> > line (or words to that effect) found during the boot process now says
>> > "Failed" after a few seconds. It's a PCI card, 3Com 3C900-TPO. When I
>> > upgraded I installed all the RPM's available on the FTP site, including
>> > the DHCP update, and as far as I can tell they all installed with no
>> > problem.
>> >
>> > When I did the initial installation of Linux the ethernet card worked
>> > without any setup needed, so I have no idea where to go from here. Any
>> > help would be greatly appreciated, Linux is practically worthless to me
>> > if I can't get the ethernet card to work again. Thanks.
>>
>> Is the Ethernet card detected during boot? Use dmesg to check.
>>
>> --
>> Steve Philp
>> [EMAIL PROTECTED]
>
>Thanks for the reply Steve, yes the card is detected properly during boot.
>Here's a cut & paste of part of the dmesg output that pertains to networking
>and the ethernet card:
>
>-----
>PCI: PCI BIOS revision 2.10 entry at 0xfceb1
>PCI: Using configuration type 1
>PCI: Probing PCI hardware
>Linux NET4.0 for Linux 2.2
>Based upon Swansea University Computer Society NET3.039
>NET4: Unix domain sockets 1.0 for Linux NET4.0.
>NET4: Linux TCP/IP 1.0 for NET4.0
>IP Protocols: ICMP, UDP, TCP
>Initializing RT netlink socket
><snipped a bunch of filesystem stuff>
>3c59x.c:v0.99H 11/17/98 Donald Becker
>http://cesdis.gsfc.nasa.gov/linux/drivers/vortex.html
>eth0: 3Com 3c900 Boomerang 10baseT at 0xff00, 00:a0:24:d1:45:19, IRQ 10
> 8K word-wide RAM 3:5 Rx:Tx split, 10baseT interface.
> Enabling bus-master transmits and whole-frame receives.
>-----
>
>As far as I can tell, it seems like it's detecting the card properly, at
>least, none of this is out of the ordinary as compared to the older kernel
>version. But it's still giving the "Using DHCP for eth0.... Failed" message
>on boot. And if it helps, the card is hooked up via a 10base-T to a
>RoadRunner cable modem.
>
>Howard
