Created attachment 107200 [details] I can submit my configure file... When using the 3.10 kernel, I cannot boot my system. It blocks on udev stage(I use systemd-197). I fetched the firmware-linux-nonfree from Debian version 0.40, and there're firmwares related to my GPU (HD4330M) now.(Including the UVD firmware). It stops with the last message :"ATOM BIOS xxx".(I cannot re-try because the suddenly halts of system causes my iwl3945 to break down.Now my notebook(Compaq 511-927) is in the repair store.)
3.8 is ok.
I'm guessing you are getting a stall due to waiting for the firmware fetch to time out. Make sure your initrd contains the firmware if you are using one or if you are building the driver into the kernel, make sure the firmware is built in as well. If you wait for a few minutes the the firmware fetch will eventually timeout and the kernel will continue. You can also try backlisting radeon and then booting to a non-X runlevel and then try loading radeon manually. At that point the filesystem will be available and the driver will be able to access the firmware.
(In reply to Alex Deucher from comment #2) > I'm guessing you are getting a stall due to waiting for the firmware fetch > to time out. Make sure your initrd contains the firmware if you are using > one or if you are building the driver into the kernel, make sure the > firmware is built in as well. If you wait for a few minutes the the > firmware fetch will eventually timeout and the kernel will continue. You > can also try backlisting radeon and then booting to a non-X runlevel and > then try loading radeon manually. At that point the filesystem will be > available and the driver will be able to access the firmware. My /lib is (ofcourse) on the root filesystem. And the whole DRM support is a module. I waited for at least 10 minutes. I know the pain of waiting firmware, but it cannot cost 10 minutes.(I used to have no firmware so I know the time, It's at most 1 min).
Might be a duplicate of bug 60674. Can you try the patch on that bug? If that doesn't help, can you bisect?
(In reply to Alex Deucher from comment #4) > Might be a duplicate of bug 60674. Can you try the patch on that bug? If > that doesn't help, can you bisect? I cannot try now... And I cannot even boot, not incorrect display! I said, my boot paused when start the kernel radeon module. Sorry.
(In reply to Eastern Heart from comment #5) > I cannot try now... And I cannot even boot, not incorrect display! > I said, my boot paused when start the kernel radeon module. > Sorry. The patch is still be relevant, you may just have different symptoms on your system. Without the patch garbage gets written to certain registers which may cause the card to hang or cause display problems, or nothing at all depending on what registers are written to.
(In reply to Alex Deucher from comment #6) > (In reply to Eastern Heart from comment #5) > > I cannot try now... And I cannot even boot, not incorrect display! > > I said, my boot paused when start the kernel radeon module. > > Sorry. > > The patch is still be relevant, you may just have different symptoms on your > system. Without the patch garbage gets written to certain registers which > may cause the card to hang or cause display problems, or nothing at all > depending on what registers are written to. Although I haven't apply this patch, can I ask: will this patch be merged to linux-3.10.7?
(In reply to Eastern Heart from comment #7) > > Although I haven't apply this patch, can I ask: will this patch be merged to > linux-3.10.7? It should make it's way to 3.10 eventually. I'm not sure which 3.10.x version it will end up in.
(In reply to Alex Deucher from comment #8) > (In reply to Eastern Heart from comment #7) > > > > Although I haven't apply this patch, can I ask: will this patch be merged > to > > linux-3.10.7? > > It should make it's way to 3.10 eventually. I'm not sure which 3.10.x > version it will end up in. Today I have get my Compaq 511 back. The patch works! And I'm trying to enjoy uvd hardware decode.
Glad it's working. Please mark this bug as a duplicate of bug 60674.
*** This bug has been marked as a duplicate of bug 60674 ***