LinuxQuestions.org - [SOLVED] System got totally messed up after huge update yesterday

- Arch (https://www.linuxquestions.org/questions/arch-29/)

- - System got totally messed up after huge update yesterday (https://www.linuxquestions.org/questions/arch-29/system-got-totally-messed-up-after-huge-update-yesterday-801364/)

MTK358

04-11-2010 10:15 AM

System got totally messed up after huge update yesterday

I ran "pacman -Syu" yesterday and it was an enormous amount of updates, even including things like the kernel, drivers, etc.

When I booted up today in the morning, a lot of things are completely screwed up.

First, the text in command-line mode got much smaller and higher resolution.

Then I noticed my two monitors were switched. I fixed that by swapping the cables.

After that, I noticed that the built-in speaker beeps when I try to, for example, move the cursor in a terminal when it can't go farther. That didn't happen before.

Later I found that SuperTux goes at something like 12fps now, so I think the graphics driver doesn't work any more.

And just now I launched VirtualBox and got an error that some module isn't loaded or whatever.

How do I fix all this?

brianL

04-11-2010 10:20 AM

Switch to Slackware. ;)

pixellany

04-11-2010 10:20 AM

Some things need to be re-compiled, updated, etc. when a new kernel is installed---eg the proprietary nvidia driver.

Some of what you mention is just settings.

For VirtualBox, you would need to tell us what the error message was.

linus72

04-11-2010 10:23 AM

I also received those same updates in my 2 systems, one a AMD athlon-xp with nvidia mx4000 and the other
a AMD athlon64 with sis intergrated and I have had 0 issues.

pacman correctly reinstalled my nvidia driver and I dont have virtual box.

so, its probably not the upgrades themselves i would guess

MTK358

04-11-2010 10:24 AM

1 Attachment(s)

I'm using the xf86-video-ati driver with a Radeon HD 4850.

Here is the error message form VirtualBox (remember, it worked flawlessly before the update):

pixellany

04-11-2010 10:28 AM

Quote:

Originally Posted by MTK358 (Post 3931810)

I'm using the xf86-video-ati driver with a Radeon HD 4850.

Here is the error message form VirtualBox (remember, it worked flawlessly before the update):

So, how about doing what it suggests?

For the video, maybe try radeon or fglrx?

I might as well point out that Arch is not perfect--I've had episodes like this myself.

damgar

04-11-2010 10:33 AM

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.

adamk75

04-11-2010 11:01 AM

As for your video issues. Your kernel must have been updated to one that uses KMS by default. Your xf86-video-ati and libdrm also need to be updated to use KMS which, it sounds like, did not happen.

Plaese attach your /var/log/Xorg.0.log file and we can confirm that.

Adam

adamk75

04-11-2010 11:03 AM

Sorry, duplicate.

pixellany

04-11-2010 11:03 AM

Pardon my ignorance, but what is "KMS"?

adamk75

04-11-2010 11:07 AM

kernel modesetting. Intel, radeon, and nouveau have all started moving the modesetting code out of the Xorg driver and into the kernel direct rendering module. The fact that MTK358 now has a high resolution console is pretty indicative that he's using KMS (though, I guess, vesafb or uvesafb is also a possibility, but less likely, IMO).

Adam

MTK358

04-11-2010 12:09 PM

1 Attachment(s)

I noticed that now it takes much less time to switch between X and VTs, which is nice, too.

adamk75

04-11-2010 12:19 PM

Hmmm... I don't see why DRI is disabled, but it definitely is. Can you show us the output of 'dmesg | grep drm'?

Adam

MTK358

04-11-2010 12:25 PM

Code:

$ dmesg | grep drm

[drm] Initialized drm 1.1.0 20060810

[drm] radeon defaulting to kernel modesetting.

[drm] radeon kernel modesetting enabled.

[drm] radeon: Initializing kernel modesetting.

[drm] register mmio base: 0xFBAE0000

[drm] register mmio size: 65536

[drm] Clocks initialized !

[drm] Detected VRAM RAM=256M, BAR=256M

[drm] RAM width 256bits DDR

[drm] radeon: 256M of VRAM memory ready

[drm] radeon: 512M of GTT memory ready.

[drm] radeon: using MSI.

[drm] radeon: irq initialized.

[drm] GART: num cpu pages 131072, num gpu pages 131072

[drm] Loading RV770 Microcode

[drm:rv770_startup] *ERROR* Failed to load firmware!

[drm] Default TV standard: NTSC

[drm] Radeon Display Connectors

[drm] Connector 0:

[drm]  DVI-I

[drm]  HPD1

[drm]  DDC: 0x7e60 0x7e60 0x7e64 0x7e64 0x7e68 0x7e68 0x7e6c 0x7e6c

[drm]  Encoders:

[drm]    DFP1: INTERNAL_UNIPHY

[drm]    CRT2: INTERNAL_KLDSCP_DAC2

[drm] Connector 1:

[drm]  DIN

[drm]  Encoders:

[drm]    TV1: INTERNAL_KLDSCP_DAC2

[drm] Connector 2:

[drm]  DVI-I

[drm]  HPD2

[drm]  DDC: 0x7e20 0x7e20 0x7e24 0x7e24 0x7e28 0x7e28 0x7e2c 0x7e2c

[drm]  Encoders:

[drm]    CRT1: INTERNAL_KLDSCP_DAC1

[drm]    DFP2: INTERNAL_KLDSCP_LVTMA

[drm] fb mappable at 0xD0040000

[drm] vram apper at 0xD0000000

[drm] size 5242880

[drm] fb depth is 24

[drm]    pitch is 5120

fb0: radeondrmfb frame buffer device

[drm] Initialized radeon 2.0.0 20080528 for 0000:02:00.0 on minor 0

adamk75

04-11-2010 12:36 PM

Code:

[drm:rv770_startup] *ERROR* Failed to load firmware!

I'm guessing that either you haven't updated the package that the firmware comes in, or Arch simply doesn't package it.

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

Adam

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 (Post 3931928)

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 (Post 3931818)

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

1 Attachment(s)

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

MTK358

04-11-2010 04:51 PM

Code:

$ su

Password: 

# /etc/init.d/vboxdrv setup

bash: /etc/init.d/vboxdrv: No such file or directory

# exit

exit

$

damgar

04-11-2010 05:04 PM

damgar

04-11-2010 05:09 PM

http://wiki.archlinux.org/index.php/...vboxdrv_Module

MTK358

04-11-2010 07:08 PM

Quote:

Originally Posted by damgar (Post 3932229)

http://wiki.archlinux.org/index.php/...vboxdrv_Module

That fixed it!

damgar

04-11-2010 07:14 PM

Just wondering.... what was the exact command you used. Reading that page it seemed different than anything else I've seen for Vbox in other distros.

MTK358

04-11-2010 07:16 PM

Code:

$ su

# vbox_build_module

# modprobe vboxdrv

# exit

$

All times are GMT -5. The time now is 12:13 AM.