User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:20.0) Gecko/20100101 Firefox/20.0
Test performed on a Samsung X22 laptop. Boot not successful.
Error Reply Type0x00000005 cmd C_TX seq 0x0000 ser 0x00740000
can't stop Rx DMA
Error sending C_RXON: time out after 500ms.
Error setting new configuration (-110).
Microcode SW error detected. Restarting 0x82000008.
Loaded firmware version: 22.214.171.124
I don't know if these lines are helpful. Booting stops. F19 LXDE Live iso didn't boot in the last builds, always the same error.
Steps to Reproduce:
1. Download F19 LXDE Live iso i383, i686
2. Try to boot
3. Boot not successful
Simply start LXDE Live iso. The result was a black screen, with a with rectangle in the left upper corner.
It's still present in RC4. I am attaching /var/log/messages. There are some interesting errors, "file not found" for spice-agent, selinux preventing /usr/bin/login...
Created attachment 737552 [details]
Are you sure the two of you are talking about the same problem? As far as I understand Jörg his laptop doesn't boot at all, which would probably be a kernel problem.
What Jan describes on the other hand seems to be a problem after logging in, probably a duplicate of bug 947558.
You are right, I /am/ able to boot, although I don't know if it's the same problem as in bug 947558. After bootscreen, xserver doesn't start successfully. Screen is blinking, switching between console and xserver. Mouse cursor appeared, but desktop wallpaper didn't.
Fedora-Live-LXDE-i686-19-Beta-TC3-1.iso 04-May-2013 00:23 706M, can repeatedly boot this Live Image
Jörg, did you try any other media? I find it hard to believe this only affects LXDE. Even if one image was bad due to a bug in image creation, it shouldn't happen afraid.
If it affects other images, this bug should be reassigned to the kernel package.
Jörg, please get back to us, you are the only one to have that hardware.
(In reply to comment #5)
> Fedora-Live-LXDE-i686-19-Beta-TC3-1.iso 04-May-2013 00:23 706M, can
> repeatedly boot this Live Image
I read this as "problem solved" and as there was no further response despite my requests, I will close thus bug now.