View previous topic :: View next topic |
Author |
Message |
Omead n00b
Joined: 06 Oct 2012 Posts: 18
|
Posted: Thu Oct 11, 2012 8:21 pm Post subject: "Swiching to clocksource tsc" delay in boot up |
|
|
Hi,
After I tried manipulating my radeon HD 4000 series, I suddenly encountered this 2 min delay in booting. I am currently using the open source driver for the graphic card, at least I think so. I searched the forum for the problem but couldn't find out how to resolve this problem. |
|
Back to top |
|
|
asturm Developer
Joined: 05 Apr 2007 Posts: 8933
|
|
Back to top |
|
|
silent_Walker Tux's lil' helper
Joined: 25 Jul 2012 Posts: 100 Location: forums.gentoo.org
|
Posted: Thu Oct 11, 2012 8:46 pm Post subject: |
|
|
I have a mobile 4200 series GPU and fixed the delay by emergng radeon-ucode and going into the kernel and entering the blobs :
radeon/R600_rlc.bin radeon/R700_rlc.bin
Device Drivers --->
Generic Driver Options --->
[*] Include in-kernel firmware blobs in kernel binary
(radeon/R600_rlc.bin radeon/R700_rlc.bin)
rebuild kernel and reboot. _________________ ^.^ |
|
Back to top |
|
|
Omead n00b
Joined: 06 Oct 2012 Posts: 18
|
Posted: Thu Oct 11, 2012 10:13 pm Post subject: |
|
|
silent_Walker wrote: | I have a mobile 4200 series GPU and fixed the delay by emergng radeon-ucode and going into the kernel and entering the blobs :
radeon/R600_rlc.bin radeon/R700_rlc.bin
Device Drivers --->
Generic Driver Options --->
[*] Include in-kernel firmware blobs in kernel binary
(radeon/R600_rlc.bin radeon/R700_rlc.bin)
rebuild kernel and reboot. |
I got this error
Code: |
make[1]: Nothing to be done for `all'.
make[1]: Nothing to be done for `relocs'.
CHK include/linux/version.h
CHK include/generated/utsrelease.h
CALL scripts/checksyscalls.sh
CHK include/generated/compile.h
make[1]: *** No rule to make target `firmware/radeon/R600_rlc.bin', needed by `firmware/radeon/R600_rlc.bin.gen.o'. Stop.
make: *** [firmware] Error 2
|
|
|
Back to top |
|
|
Hu Moderator
Joined: 06 Mar 2007 Posts: 21490
|
Posted: Fri Oct 12, 2012 1:33 am Post subject: |
|
|
If the firmware came with the kernel sources, then use the default firmware directory as chosen by the kernel configuration system. If you installed the firmware separately, you need to set CONFIG_EXTRA_FIRMWARE_DIR to the directory where the firmware was installed. |
|
Back to top |
|
|
Omead n00b
Joined: 06 Oct 2012 Posts: 18
|
Posted: Fri Oct 12, 2012 10:48 am Post subject: |
|
|
Thanks all. Solved. |
|
Back to top |
|
|
|