You are not logged in.
when installing the new kernel i got a message to change my menu.lst so it changed "/dev/discs/disc0/part3" to "/dev/hda3" (and nothing else) cause of udev instead of devfs.
after rebooting i get few error messages:
[after network start]
SIOCSIFADDR: No such device
eth0: unknown interface: No such device
SIOCSIFBRDADDR: No such device
etho0: unknwon interface: No such device
Offline
What modules are you loading? And are you using SATA or IDE drives?
Offline
IDE
just found out that adls-start doesn't work, too cause eth0 isn't found.
i'll bet it all has to do with udev - but how to fix that?
Offline
Do a lsmod to check if the network module has been loaded.
Offline
doesn't show up - at least not eth0 ...
i ran hwd what showed me that my network card is 8139too.
then i added "alias eth0 8139too" to the modprobe.conf
Offline
I'm also having an issue after upgrading neither eth0 nor eth1 are showing up in /dev .... I think it's due to the switch from devfs to udev...
Offline
Did you run your boot manager (lilo/grub) again?
Offline
I'm also having an issue after upgrading neither eth0 nor eth1 are showing up in /dev .... I think it's due to the switch from devfs to udev...
for the record - network interfaces never show up in /dev - they're not normal devices
edit: I guess I should provide some help...
ifconfig and "ifconfig -a" will list network devices (also in /proc/net somewhere). If you do not have a network device that means that your module is not properly loaded for that device.
This should have nothing to do with a devfs/udev switch and everything to do with a kernel upgrade.
Just for some more info, can you please report the output of:
· lsmod
· uname -r
· ls /lib/modules
· ifconfig -a
Offline
Thanks for the clarification. I did run ifconfig and there were still no network devices, I think the loopback might have shown up but not eth0 or eth1. Unfortunately this is my only machine thus when I couldn't get my network up and running I was forced (by my own ignorance not by forces beyond my control) to reinstall. So now I'm up and running again but cannot get anymore information about what had gone wrong. All I know is that during the boot sequence hot-plug fails and I have no working network, there was also a message about trying a differnet driver '8139too' or some such thing. My system worked fine before the upgrade, and is working fine since the reinstall but now I'm a little afraid of doing a complete 'pacman -Syu' any ideas...sorry about the lack of detail. and please feel free to ignore this post as I do understand that it lacks information.
Offline
read my last post and there you go
Offline
read my last post and there you go
.......peachy thanks i'll give that a try. Sorry I missed that
Offline
Hi there.
I had the same problem after an update to 'noodles' and solved it as fdrebin suggested:
i ran hwd what showed me that my network card is 8139too.
then i added "alias eth0 8139too" to the modprobe.conf
But I am curious: How can this happen, that after an update I have to put an alias into modprobe.conf to describe my network card?
Could someone try to explain it to me (in easy words )
Thanks.
Michael
$>man woman
no manual entry for woman
Offline