mozingod n00b
Joined: 15 Jun 2003 Posts: 64 Location: Ohio
|
Posted: Fri Jun 20, 2003 10:10 pm Post subject: Bad NIC driver? [solved] |
|
|
I've been getting the following error:
SIOCSIFADDR- File exisits
SIOCSIFFLAGS: cannot assign requested address
SIOCSIFBRDADDR: cannot assign requested address
SIOCSIFFLAGS: cannot assign requested address
SIOCSIFNETMASK: cannot assign requested address
Now before the flames begin, I've been reading through the forums on this, but no previous posts seem to apply to me. I had the NIC working fine before (a 3Com 3c905B onboard), loaded w/the 3c59x drivers. I had KDE/sound goin fine too. Then I tried getting my USB mouse/jump drive working and added into the kernel what was needed (or at least what the guides said). On a reboot I started getting that above error. I tried removing and adding the module back in (it is loaded as a module BTW). Is it possible for it to get corupted somehow? Can I somehow get a fresh copy on there? Any help would be great, kinda lost at this point. Thanks!
Edit:
Here's what I get when I add the drivers as a module, which is how I had it working fine before (tried adding it into the kernel too... didn't work):
<path to 3c59x.o> unresolved symbol - skb_over_panic_Rsmp_7b5c8a72
<path to 3c59x.o> unresolved symbol - irq_stat_Rsmp_a0b017c3
<path to 3c59x.o> unresolved symbol - eth_type_trans_Rsmp_2f9af85e
<path to 3c59x.o> unresolved symbol - __kfree_skb_Rsmp_a75e3630
<path to 3c59x.o> unresolved symbol - zone_table_Rsmp_29fc4e32
<path to 3c59x.o> unresolved symbol - soft_data_net_Rsmp_<number>
<path to 3c59x.o> unresolved symbol - netif_rx_Rsmp_<number>
<path to 3c59x.o> unresolved symbol - alloc_skb_Rsmp_<number>
<path to 3c59x.o> unresolved symbol - __netdev_watchdog_up_Rsmp_<number>
insmod <path to 3c59x.o> failed.
Also, I was going to try a different 3Com driver, but when I add the 3Com group in the config menu of the kernel it only shows the 3c95x driver... the others don't appear at all. Any help would be greatly appreciated... thanks!
Edit 2:
Updated BIOS, took out 3c59x module, recompiled and rebooted. Then added it all back in and it's working now. Odd... oh well. |
|