Gentoo Websites Logo
Go to: Gentoo Home Documentation Forums Lists Bugs Planet Store Wiki Get Gentoo!
Bug 41185 - ioctl SIOCSIFADDR errors show up in logs when I try to get an IP from DHCP
Summary: ioctl SIOCSIFADDR errors show up in logs when I try to get an IP from DHCP
Status: RESOLVED FIXED
Alias: None
Product: Gentoo Release Media
Classification: Unclassified
Component: Everything (show other bugs)
Hardware: x86 Linux
: High major (vote)
Assignee: Gentoo LiveCD Package Maintainers
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2004-02-10 17:54 UTC by Tucker McLean
Modified: 2004-05-11 22:26 UTC (History)
0 users

See Also:
Package list:
Runtime testing required: ---


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Tucker McLean 2004-02-10 17:54:28 UTC
I'm trying to install Gentoo on an IBM PC 300PL with the basic LiveCD, and this is what's happening. My network interface (eepro100) is detected, but when it tries to get an IP address from DHCP, it immediately finished, there is no delay. After it is booted up, I look in /var/log/everything/current, and there is a couple zillion lines like this:

Feb 10 17:35:30 [dhcpcd] dhcpStop: ioctl SIOCSIFADDR: Bad file descriptor
Feb 10 17:35:30 [dhcpcd] dhcpStop: ioctl SIOCSIFFLAGS: Bad file descriptor
Feb 10 17:35:30 [dhcpcd] terminating on signal 4

I tried entering in an address manually, and it works, as long as I set all the routes, etc. manually, although DHCP is nicer :-)



Reproducible: Always
Steps to Reproduce:
1. Boot up with nodhcp set
2. tail /var/log/everything/current
3. dhcpcd eth0
4. tail /var/log/everything/current, again


Actual Results:  
I saw errors, and didn't have an address assigned to eth0

Expected Results:  
There shouldn't be any errors pertaining to eth0, and it should have an address
Comment 1 Benjamin Judas (RETIRED) gentoo-dev 2004-03-22 02:32:32 UTC
Is the appropriate module for that NIC loaded?
Comment 2 Benjamin Judas (RETIRED) gentoo-dev 2004-05-11 22:26:51 UTC
Closing due to no response