Skip to contentSkip to conversation

[2.5.24] RTL8139: ioctl(SIOCGIFHWADDR): No such device

DISCUSSION Axel Siebenwirth 2 participants 4 messages Jul 1, 2002 – Jul 2, 2002

lore
Share & tools
lore
#0 lore raw

Hi,

Environment: Kernel 2.5.24, SuSE Linux 7.2, Intel Chipset 440FX

NIC: RTL1839 connected to ADSL Modem

When trying to connect to ADSL, I get the following error msgs (I guess the "ioctl(SIOCGIFHWADDR): No such device" is the important part):

pppd[823]: pppd 2.4.1 started by root, uid 0
pppd[823]: Using interface ppp0
pppd[823]: Connect: ppp0 <--> /dev/pts/0
pppoe[824]: ioctl(SIOCGIFHWADDR): No such device
pppd[823]: Modem hangup
pppd[823]: Connection terminated.
pppd[823]: Exit.

Have not tried 2.5.23 but 2.5.22 works fine. Since there have been changes to the 8139too driver I guess thats it. Unfortunately I do not know where to fix this.

Regards,
Axel

#1 lore raw
Quoted 2 lines · Axel Siebenwirth

Have not tried 2.5.23 but 2.5.22 works fine. Since there have been changes to the 8139too driver I guess thats it. Unfortunately I do not know where to fix this.

None that should affect this, however.

Can you please copy your 2.5.22 drivers/net/8139too.c into 2.5.24, and test 2.5.24 with the older driver?

Jeff

#2 lore raw

Hi Jeff!

Quoted 9 lines · Jeff Garzik
Quoted 4 lines

Have not tried 2.5.23 but 2.5.22 works fine. Since there have been changes to the 8139too driver I guess thats it. Unfortunately I do not know where to fix
this.

None that should affect this, however.

Can you please copy your 2.5.22 drivers/net/8139too.c into 2.5.24, and test 2.5.24 with the older driver?

Ok. I copied 8139too driver of 2.5.22 to 2.5.24 and it it was still the same.

I attached output of "lspci -vvv" and "dmesg".

"ifconfig eth1 up" returns with something like "device not found".

Regards,
Axel

#3 lore raw
In reply to Jeff Garzik

Hi Jeff!

Quoted 5 lines · Jeff Garzik
Quoted 4 lines · Axel Siebenwirth

Have not tried 2.5.23 but 2.5.22 works fine. Since there have been changes to the 8139too driver I guess thats it. Unfortunately I do not know where to fix
this.

Kai made some changes about net_dev_init ...

<[email protected]>
Make net_dev_init() an __initcall

If you were looking to find where net_dev_init() is called, you
wouldn'
t
have guessed it's in drivers/block/genhd.c, would you?

Nothing should break if the __initcall net_dev_init is called too
late
now, since register_netdevice() will call it for us in that case.

With my poor knowledge I guess this could be it?! If you are sure it's not the 8139too driver.

Regards,
Axel