|
|
#1 | |
|
Registered User
Join Date: Jul 2003
Location: Houston, Tx USA
Posts: 110
|
I have been running kernel 2.4.21 with ALSA 0.9.4 and nvnet from the driver package 1.0-261 and have had no problems.
I then compiled the 2.4.22-pre2,3,4 kernels and installed the same (recompiled) versions of the drivers. The nvnet works well and ALSA works but not together! I get about 10 seconds of audio while downloading and then XMMS quits and hangs and nvnet becomes un-usable. No messages in /var/log/messages related to the problem. Kernel 2.4.21 doesn't have the problem. If I unload the nvnet module and reload it, I can restart the network. Audio will work after I unload nvnet too. The audio/nvnet mess-up only occurs with both XMMS (or mpg123) playing and nvnet active downloads. Using the audio in xawtv to watch tv doesn't cause the failure. hmmmmmmmm ... Anyone else seen similar issues with the kernel 2.4.22-pre series? Suggestions? Hardware --- Abit NF7-S v1.1 with BIOS 19, RH9 + ALSA 0.9.4, 0.9.5, nvnet 261, 256 |
|
|
|
|
|
|
#2 | |
|
Registered User
Join Date: Apr 2003
Posts: 3
|
Have you tried using acpi=off on the kernel boot line? pci=noacpi alone didn't give me joy and caused my 3com card to go out of whack every now and then...
The major merge in 2.4.22-pre is the new ACPI code. BTW, I'd also suggest updating to ALSA 0.9.5, since the SPDIF actually works on that ;-) If you want your PC to turn itself off, you'd need to go back to APM though... UGH. I think it might be the PCI IRQ routing code in ACPI that is seriously busted. Mmmmm. NVidia kernel gods? Are thee around?
__________________
This sig no verb |
|
|
|
|
|
|
#3 |
|
Registered User
Join Date: Jul 2003
Location: Houston, Tx USA
Posts: 110
|
No, I hadn't tried the acpi=off on the boot line but I was using pci=noacpi. Figured that would get the acpi issues out of the way but .... it apparently didn't. I just rebooted with acpi=off switch and you were absolutely right - the system now appears to run ok.
I had upgraded to ALSA 0.9.5 and was having the same issues as with 0.9.4. Clearly, the problem is the new acpi code in the kernel and it's interaction with the hardware. I'll just go ahead and change from pci=noacpi to acpi=off on the boot line. Thanks for the response and help. |
|
|
|
|
|
#4 | |
|
Eggplant
|
Well since 2.4.22 still is in pre stages I suggest you report this bug to the developers so it can be resolved before it goes stable
__________________
"Never bump a baby carriage out of a crosswalk unless the kid's really asking for it." |
|
|
|
|
|
|
#5 |
|
Registered User
Join Date: Apr 2003
Location: Germany
Posts: 77
|
try to append pci=noacpi and noapic
after that everythings works fine for me |
|
|
|
![]() |
| Thread Tools | |
|
|