Gentoo Websites Logo
Go to: Gentoo Home Documentation Forums Lists Bugs Planet Store Wiki Get Gentoo!

Bug 176618

Summary: udev-109-r1 breaks wireless
Product: Gentoo Linux Reporter: Renato Caldas <seventhguardian>
Component: [OLD] Core systemAssignee: udev maintainers <udev-bugs>
Status: RESOLVED INVALID    
Severity: normal CC: jmbsvicetto, m.debruijne
Priority: High    
Version: 2006.1   
Hardware: All   
OS: Linux   
Whiteboard:
Package list:
Runtime testing required: ---

Description Renato Caldas 2007-04-30 19:41:45 UTC
I'm using the ipw3945 driver, and updating to udev-109-r1 broke wireless, that is, I was unable to associate with any AP (no errors what-so-ever), either using plain wireless-tools or wpa_supplicant. Reverting to udev-109 solved it.

I've done a lot of debugging tests, including installing the new iwlwifi driver, and as soon as I reverted udev and reinstalled ipw3945 wpa associated..
Comment 1 Renato Caldas 2007-04-30 20:06:24 UTC
I found something that may be interesting: issuing a "udevstart" command actually makes wireless work again. Not even "modprobe ipw3945 -r && modprobe ipw3945" does that..
Comment 2 Matthias Schwarzott gentoo-dev 2007-05-01 07:41:26 UTC
Sounds strange. Only change between udev-109 and udev-109-r1 is in build system:
1. Make it respect normal CFLAGS:
+       epatch ${FILESDIR}/${P}-respect-CFLAGS.diff
+
2. Use emake instead of make
-       # Do not work with emake
-       make \
+       emake \
                EXTRAS="${extras}" \

If you are sure it works with udev-109, then try to modifiy udev-109-r1 in either of these two places.
I suggest to first try what happens if you add "-j1" to emake resulting in
+       emake -j1 \
                EXTRAS="${extras}" \

and re-emerge udev-109-r1.
Comment 3 Renato Caldas 2007-05-01 10:31:16 UTC
Apparently recompiling udev-109-r1 solved it (?), but I seem to still get random glitches.. My CFLAGS are as follows: "-march=nocona -O3 -pipe".

Wireless framework is a bit unstable now, so I'll test it a bit more thoroughly before blaming udev :)

Marked as invalid for now, I'll reopen if I can confirm it. Thanks!