[SOLVED] System got totally messed up after huge update yesterday

MTK358 · 04-11-2010, 01:59 PM

Code:

$ cd /lib/firmware/radeon
$ ls
R100_cp.bin  R600_pfp.bin   RV610_pfp.bin  RV635_pfp.bin  RV730_pfp.bin
R200_cp.bin  RS600_cp.bin   RV620_me.bin   RV670_me.bin   RV770_me.bin
R300_cp.bin  RS690_cp.bin   RV620_pfp.bin  RV670_pfp.bin  RV770_pfp.bin
R420_cp.bin  RS780_me.bin   RV630_me.bin   RV710_me.bin
R520_cp.bin  RS780_pfp.bin  RV630_pfp.bin  RV710_pfp.bin
R600_me.bin  RV610_me.bin   RV635_me.bin   RV730_me.bin

MTK358 · 04-11-2010, 02:03 PM

Quote:

Originally Posted by adamk75

Specifically, you probably need R700_rlc.bin (does it exist in /lib/firmware/radeon ?) from http://people.freedesktop.org/~agd5f/radeon_ucode/

I added that file, restarted X, still nothing.

Do I need to reboot?

adamk75 · 04-11-2010, 04:05 PM

Yes. The firmware gets loaded by the DRM module when it's initially loaded by the kernel.

Adam

MTK358 · 04-11-2010, 04:07 PM

Rebooting...

adamk75 · 04-11-2010, 04:08 PM

Also, if the 'radeon' module is in your initrd, that firmware needs to be as well. If 'radeon' is compiled into the kernel, the firmware needs to be compiled in too :-)

Adam

adamk75 · 04-11-2010, 04:09 PM

Also, if the 'radeon' module is in your initrd, that firmware needs to be as well. If 'radeon' is compiled into the kernel, the firmware needs to be compiled in too :-)

Adam

MTK358 · 04-11-2010, 04:10 PM

3D works after rebooting.

So what about VBox?

adamk75 · 04-11-2010, 04:13 PM

Did you recreate the vboxdrv kernel module(s)?

Adam

MTK358 · 04-11-2010, 04:18 PM

What does that mean?

MTK358 · 04-11-2010, 04:20 PM

I noticed this:

Code:

$ sudo modprobe vboxdrv
Password: 
FATAL: Module vboxdrv not found.

It worked before.

adamk75 · 04-11-2010, 04:22 PM

Right, the kernel module needs to be compiled for your kernel. The screenshot you attached earlier even tells you want command to run. Have you done that?

Adam

damgar · 04-11-2010, 04:23 PM

Quote:

Originally Posted by damgar

VirtualBox uses a kernel driver/module so when you change kernels you have to update that module by running the setup command it gave you. The path it gave you in the error may not be 100% accurate. In slackware the command would be

Code:

/etc/rc.d/rc.vboxdrv setup

Code:

locate vboxdrv

ought to put out the proper path.

Did you try this? It should work.

MTK358 · 04-11-2010, 04:25 PM

Code:

$ sudo /etc/rc.d/rc.vboxdrv setup
Password: 
sudo: /etc/rc.d/rc.vboxdrv: command not found
$ locate vboxdrv > locate_vboxdrv.txt # See Attachment

damgar · 04-11-2010, 04:44 PM

Try doing it as root. The location will be around your init scripts some where, it doesn't look like that's in your path? I'm assuming you are running as a regular user.

Something like init.d or rc.d .........something like that.

I"m assuming you did the exact command Virtual Box gave you first?

damgar · 04-11-2010, 04:49 PM

For Arch it seems to be exactly what the original error message from Vbox gave you.

Code:

/etc/init.d/vboxdrv setup