Package: alsa-source Version: 1.0.8-4 Severity: important I am opening a bug report with your message. It is an important problem.
-------- Forwarded Message -------- From: George McNinch <[EMAIL PROTECTED]> Reply-To: [EMAIL PROTECTED] To: [EMAIL PROTECTED] Cc: George McNinch <[EMAIL PROTECTED]> Subject: [Pkg-alsa-devel] alsa issue Date: Sun, 06 Feb 2005 08:53:54 -0500 Hi-- I had a serious issue upon upgrading FROM alsa-base-1.0.7-2 TO alsa-base-1.0.8-4 (which upgrade happened in the testing distribution in the last few days). I'm just sending this email rather than a bug report because I doubt I can be precise enough, and for that I apologize in advance. After the upgrade, I was no longer able to boot kernel 2.6.8-1, though I was able to boot kernel 2.4.22. The boot simply stopped with a message related to isapnp and the module for my (very old, legacy) sound card cs4232. By way of hopefully letting you know what ordinarily happens, here is the portion of /var/log/syslog reltaed to this card that appears during boot for kernel 2.6.8-1 when alsa-base-1.0.7-2 is installed. Feb 5 22:42:54 mars kernel: isapnp: Scanning for PnP cards... Feb 5 22:42:54 mars kernel: isapnp: Card 'CS4236B' Feb 5 22:42:54 mars kernel: isapnp: 1 Plug & Play card detected total Feb 5 22:42:54 mars kernel: ad1848/cs4248 codec driver Copyright (C) by Hannu Savolainen 1993-1996 Feb 5 22:42:54 mars kernel: ad1848: WSS/SB detected Feb 5 22:42:54 mars kernel: ad1848: ISAPnP reports 'WSS/SB' at i/o 0x534, irq 5, dma 1, 3 Feb 5 22:42:54 mars kernel: cs4232: set synthio and synthirq to use the wavefront facilities. Something was different under alsa-base-1.0.8-4, and as I said before, the system was not booted. Unfortunately, during those failed boots (I tried several times) /var/log/syslog was not succesfully written to. (In fact, fsck complained a lot each time on reboot, so I suspect that various things on the filesystem were left open). And I didn't write down verbatim the complaining kernel-message. Boot halted in a strange way (the system wasn't locked up -- pressing Enter on the keyboard actually scrolled the boot messages -- but the system did not boot). I did not have this problem booting the old kernel 2.4 with the new alsa-base 1.0.8. I have resolve MY problem by booting in 2.4.22 and "downgrading" alsa-base to 1.0.7-2. Now I can boot the 2.6 kernel again. Sorry if this is not helpful, but I thought it fairly serious. Please let me know what I could do to give you more useful information. best, gm -- Thomas Hood <[EMAIL PROTECTED]> -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]