Description of problem: After configuring sound in firstboot, and rebooting I got a kernel panice. I have an SATA disk,but was getting errors from ata1 failing to read. I suspect it was meaningregular ide ata drive, which isn't present in this system. This caused a panic, not being able to find a root partition. I don't know if the reboot method after firstboot caused this, or hardware probing during the first setup, but after a hard power off, and power on, the kernel found the SATA disk again, and everything was working. Version-Release number of selected component (if applicable): FC6 Test 2 DVD iso kernel How reproducible: It takes a while to install the system from scratch, so I haven't tried to reproduce this. It hasn't happened other than after the firstboot reboot. Steps to Reproduce: 1. 2. 3. Actual results: kernel panic Expected results: reboot into FC6 test 2 Additional info: System AMD 64 bit Athlon 2400 200 GB SATA hard drive 512 MB Ram Memory Gigabit ethernet USB - printer HP PSC 1210 6600 GT Nvidia Video Card ( I don't install NVIDIA's drivers, if I'm not doing something that needs the extra performance. ) 17" Samsung monitor synmaster 750s On board VIA sound ASUS A8V-E Deluxe Motherboard. The monitor,keyboard, and mouse, are shared with another computer via a KVM. This information came from my overall post on fedoraforum.org with title: "FC6 Test 2 i386 observations"
I now doubt that firstboot had anything to do with this. I had another kernel panic yesterday starting up from cold. Couln't really tell what the problem was. Again, just trying to boot again with the same kernel worked.
When you get panics, it's really important to get the text that gets displayed, otherwise we have no hope of diagnosing this.
Sorry for the lack of details. It turns out the instabilities I was having seem to be coming from my power supply failing. My system got to the point it would lock up in the bios. Tried a new cpu first, same results. New power supply seems to have it fixed. It possible the hd was also not getting spun up or something because of this. Things seem stable now. Bad luck to have that happen as I was trying to help test the software. I would suggest closing this bug report, as being failing hardware, or not a bug.
Closing, per original reporter's feedback.