On Sat, Oct 25, 2008 at 01:06:47AM +0200, Jonas Meurer wrote: > On 22/10/2008 Jonas Meurer wrote: > > On 22/10/2008 Michael Pobega wrote: > > > When I installed cryptsetup on my Eee PC (using debian-eeepc and the > > > madwifi drivers) and rebooted, my wireless would not work. dmesg | tail > > > would just say "Wireless off" everytime I turned it back on with Fn+2. > > > After recovering /boot/initrd-`uname -r`.bak the wireless works again. > > > > > > I'm not exactly sure what about it killed it, but whatever cryptsetup > > > appended to my initrd killed my wireless. > > > > I doubt that cryptsetup really stops your wireless from working. > > Instead, something else might have changed since you last recreated the > > initramfs file that causes this bug. > > > > What happens if you simply remove cryptsetup and regenerate the > > initramfs file afterwards? > > > > Is it possible to reproduce the bug over and over again (i.e: install > > cryptsetup - system is broken. remove cryptsetup - system works. install > > cryptsetup - system is broken. remove cryptsetup ...) > > Hey, > > any news about the bug? I'm absolutely sure that your wifi troubles > don't have anything to do with cryptsetup. > > Please provide more information. Unfortunately I'm unable to reproduce > the bug, as I've no hardware with wireless hardware. > > greetings, > jonas
I think the problem lies in HAL. When I keep the device activated it works fine, but if I use my hotkey (Fn+F2) the device refuses to reload, dmesg reports that the device didn't respond properly and couldn't be loaded. I feel that I put this bug in the wrong place, I'll bring it up with madwifi when I get the chance, I'm sorry for wasting your time.
signature.asc
Description: Digital signature
