From: Florian Philipp <lists@f_philipp.fastmail.net>
To: gentoo-user@lists.gentoo.org
Subject: [gentoo-user] Kernel 2.6.26 and iwl3945
Date: Fri, 14 Nov 2008 22:30:55 +0100 [thread overview]
Message-ID: <491DEE0F.1090805@f_philipp.fastmail.net> (raw)
[-- Attachment #1.1: Type: text/plain, Size: 1176 bytes --]
Hi list!
I recently updated from tuxonice-2.6.24-r9 to tuxonice-2.6.26.
I hoped it would solve irregular kernel crashes on my Dell notebook and
would reactivate the wifi LED. However, it caused more problems than it
solved.
- the pvrusb2 (V4L2) kernel module works but causes kernel panics and oops
- the bay (ACPI) module can't be loaded
- suddenly Thunderbird disappears on suspend2disk/resume
- the RFKILL switch is not always recognized (needs interface restart)
- iwlwifi sometimes causes (non-critical) kernel oops when initialized
- the wifi LED still doesn't work
The first three points will need more investigation on my part and might
soon be the topic of other threads. However, I'd like to hear your input
on the other issues:
Is this kernel version generally unstable?
What do I need to make the LED work?
What could I do to solve all these problems? I'm out of ideas at the
moment and Gentoo Bugzilla doesn't offer much on these topics.
I've attached the kernel config and a part of dmesg where iwlwifi caused
an oops after I've restarted the net.eth1 script but then it worked
flawlessly.
Thanks in advance!
Florian Philipp
[-- Attachment #1.2: kernel_config.gz --]
[-- Type: application/x-gzip, Size: 14545 bytes --]
[-- Attachment #1.3: dmesg.gz --]
[-- Type: application/x-gzip, Size: 896 bytes --]
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 260 bytes --]
next reply other threads:[~2008-11-14 21:31 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-11-14 21:30 Florian Philipp [this message]
2008-11-16 11:02 ` [gentoo-user] Kernel 2.6.26 and iwl3945 Florian Philipp
2008-11-16 13:20 ` Alan McKinnon
2008-11-17 8:02 ` Sebastian Günther
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=491DEE0F.1090805@f_philipp.fastmail.net \
--to=lists@f_philipp.fastmail.net \
--cc=gentoo-user@lists.gentoo.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox