You are not logged in.
hello!
yesterday, before upgrading the system (pacman -Syu - think it was udev etc.) i had the devices eth0, eth1, eth2 and sit0. eth2 was my wireless (ipw2200) device. now, after reboot, all devices but eth0 and sit0 are away. what's happened? any ideas? where i can get an older version of udev? i have no old udev-pkg in the pacman-cache. i also had renamed the /etc/sysctl.conf because of errors at bootup.
kernel26 2.6.12.2-1
ipw2200 1.0.4-4
udev 060-1
sorry for my english
sorry for my bad english
Offline
I have exactly the same problem here after I did a pacman -Syu. My wireless interface is gone. I use ipw2200. From the kernel messages:
ipw2200: Detected Intel PRO/Wireless 2200BG Network Connection
ipw2200: ipw-2.3-boot.fw load failed: Reason -2
ipw2200: Unable to load firmware: 0xFFFFFFFE
ipw2200: failed to register network device
ipw2200: probe of 0000:02:02.0 failed with error -5
Offline
I have similar problems since my last upgrade (also think it was udev). On my notebook, I have to load the wireless lan driver and do a /etc/rc.d/network ifup wlan0 manually. On my desktop, the usb printer module isn't loaded automatically when I switch on my printer. This still worked yesterday.
Offline
Not an ipw user myself, but I dn't think this is a udev problem - udev doesn't touch network interfaces. AFAIK the ipw packages are compiled for use with specific stock Arch kernels, so each time the kernel package is upgraded, the ipw package needs to be redone as well. It's possible there's a lag - different maintainers, or whatever the reason. I'd say downgrade your kernels again, and wait a few days.
Going OT a bit, this is one of the reasons why I object to kernels being upgraded in the same manner as other packages. If you would prefer to choose when your kernel gets changed, instead of discovering it when things start to break, put
IgnorePkg = kernel26
in the [options] section of /etc/pacman.conf.
Offline
@tomk: thx for help - but i also reinstalled the old kernel and old ipw-pkg. the problem was still there.
i have no idea, where the problem is. searched through the www - nothing.
i hope, it will be fixed soon.
sorry for my bad english
Offline
Offline
Not an ipw user myself, but I dn't think this is a udev problem - udev doesn't touch network interfaces.
I thought so as well. But since yesterday's udev update, hotplug is definitively broken for me on both machines.
Obviously hotplug doesn't load modules and bring up interfaces any more. I don't know how this is related to udev, but just look at this:
[07/04/05 01:45] synchronizing package lists
[07/04/05 01:45] starting full system upgrade
[07/04/05 01:48] upgraded e2fsprogs (1.37-1 -> 1.38-1)
[07/04/05 01:48] upgraded gnome-desktop (2.10.1-1 -> 2.10.2-1)
[07/04/05 01:48] upgraded gnome-menus (2.10.1-2 -> 2.10.2-1)
[07/04/05 01:48] upgraded gnome-panel (2.10.1-3 -> 2.10.2-1)
[07/04/05 01:48] upgraded heimdal (0.6.4-1 -> 0.6.5-1)
[07/04/05 01:48] upgraded pmount (0.7.1-1 -> 0.9.3-1)
[07/04/05 01:48] upgraded udev (058-4 -> 060-1)
[07/04/05 01:48] upgraded wine (20050419-1 -> 20050628-1)
and this:
[07/04/05 01:45] synchronizing package lists
[07/04/05 01:45] starting full system upgrade
[07/04/05 01:47] upgraded e2fsprogs (1.37-1 -> 1.38-1)
[07/04/05 01:47] upgraded heimdal (0.6.4-1 -> 0.6.5-1)
[07/04/05 01:47] upgraded udev (058-4 -> 060-1)
Edit:
This is from /etc/start_udev
case "$(uname -r)" in
2.6.[0-9]|2.6.[0-9][!0-9]*) ;;
*) echo "/sbin/udevsend" > /proc/sys/kernel/hotplug ;;
esac
So there is a relation between hotplug and udev, because udevsend handles hotplug requests. It also did so with udev 058-4, but 058-4 worked perfectly.
Offline
I just noticed that Judd has posted another upgrade to udev (udev 060-2) so maybe this will fix some of these problems. It might not be available on all mirrors just yet, as it was only posted a few minutes ago.
BTW: the previous upgrade broke some of my USB stuff.
oz
Offline
I looked at the changes. This should fix the above problems (at least my network and usb problems) as far as I can see. Thanks to the Arch Team (even if they don't read this).
Offline
yeah, the udev-060-2 fixed the problem. so it was udev!
thx arch-team! arch - big fat 1337 distribution - i love it!
sorry for my bad english
Offline
This is getting interesting... first udev 060-2 was posted a few hours ago, and now udev 060-3 has just been posted!
oz
Offline
I stand corrected - and relieved. udev 060-1 broke my network too! I've gone back to 058-4 for now, as it seems 060 may need some time to settle in.
Offline
If anyone's interested, here's what Judd had to say about this on the mailing list:
<gripe>
Ugh, I know about it. I appreciate Greg K-H's effort with udev and I
agree with his rationale about devfs, but at least devfs didn't break
everytime we upgraded devfsd. It seems that every udev upgrade requires
a new arcane rule in udev.rules to work around something or other.
</gripe>
So, the testing repo - what's that all about? :?
Sorry - did I say that out loud?
Offline