From Bugzilla Helper: User-Agent: Mozilla/5.0 (X11; U; Linux i686) Gecko/20030530 Galeon/1.3.5 Description of problem: I have an intel motherboard (Intel D865-GBF) which has a sound card onboard (ICH5). The problem is that when you click on test sound at the sound configuration utility of firstboot the system crashes and it's impossible to cancel it because even the keyboard dies. As firstboot says the model is: Vendor: Intel Corp. Model: 82801EB AC'97 Audio Controller Module: i810_audio I think the process could be skipped and run when firstboot finishes, other way there should be a text explaining the users that the system could crash because the driver provided by the kernel may not suppor their sound card. Version-Release number of selected component (if applicable): How reproducible: Always Steps to Reproduce: 1. After installation follow the firstboot sequence 2. In the Sound configuration utility click on test sound 3. If you have the same mother than I have you should be rebooting your pc Actual Results: The system crashes after clicking on Test Sound Expected Results: It's supposed that the system should play 3 sounds, or not if the driver doesn't suppose that sound board, but instead of doing it the system crashed Additional info:
Reassigning to the kernel.
We need a few bits of information from your system: 1) The output of "lspci -vxx" (run as root) on this system 2) The oops message produced when the system crashes. The second is going to be a bit harder to get. If you have two systems and a serial cable, you can set up serial console. Otherwise, we'll have to get you some alternate instructions to reproduce this at a text console so that you can copy down the oops information and provide it to us. Let us know which is the case.
Ok, I'm downloading the latest severn version, to see how it works now,I don't have the serial cable (but I could do it if you tell me how),the only problem is that in my network the only machine with Linux is mine and I don't know if the serial will work ok with other systems.
ok, if you can get a null modem serial cable connected between two machines, here's how to use it: to your boot line, add to the end: console=ttyS0,9600 console=tty0 and on the machine at the other end, capture the serial data with settings of 9600 bps, no parity, 8 bits -- that's a very common setting that should work on any system with an application that can capture serial output. Note that even the text console will be limited to 9600 bps output, so it will be a lot slower.
Does this problem still occur in the latest { RHEL3 | Fedora }?