I've tried both linux-headers-2.6.33-4.dmz.3-liquorix-amd64 and linux-headers-2.6.33-4.dmz.1-liquorix-amd64, and the both oops on boot with a kernel null pointer de-ref.

The debian 2.6.33 kernel does not oops on boot.

This is on a laptop with an Intel C2D@2.53ghz /w 4G ram.
Back to top

I'll be uploading a kernel which may fix your bug. Look forward to 2.6.34-0.dmz.5.
Back to top

Thanks! And obviously I mean linux-image, not linux-headers.. Guh.
Back to top

Hi, me again.

Seems the latest liquorix (2.6.34-0.dmz.12-liquorix-amd64) oopses again, though -10 works fine. It seemed to mention rfkill in what little of the backtrace I could see.
Back to top

What's your wireless card? I heard that ath9k causes kernel oopses on certain devices.
Back to top

It seems to be an ath5k

dmesg: ath5k phy0: Atheros AR2425 chip found
lspci: 02:00.0 Ethernet controller: Atheros Communications Inc. AR5001 Wireless Network Adapter (rev 01)

It works just fine with the standard debian and kernel.org kernels when I try them. I could try .34 straight from kernel.org if you think that would help.
Back to top

Try blacklisting ath5k and use the madwifi modules (ath_pci) instead.
Back to top

I can't even get ath_pci to /work/. I blacklisted ath5k, and it loads ath_pci, but wicd just won't see any networks (under an older liquorix: 2.6.34*-10 iirc).

With ath5k blacklisted in /etc/modutils.d/blacklist.conf I tried booting up the latest liquorix, but it still dies in the rfkill subsystem (no ath5k symbols are listed at all).

I took a picture, maybe it'll help:


Back to top

Heres the upper half of the OOPS:



And its still happening as of the latest update.

The only version I can boot so far is 2.6.34-0.dmz.10-liquorix-amd64 many before, and all after will OOPS.
Back to top

have you tried the 2.6.35 kernel that damentz uploaded to his repo?
Back to top