LinuxQuestions.org
Visit the LQ Articles and Editorials section
Go Back   LinuxQuestions.org > Forums > Linux Forums > Linux - Distributions > Arch
User Name
Password
Arch This Forum is for the discussion of Arch Linux.

Notices

Reply
 
Search this Thread
Old 04-11-2010, 11:15 AM   #1
MTK358
LQ 5k Club
 
Registered: Sep 2009
Posts: 6,443
Blog Entries: 3

Rep: Reputation: 714Reputation: 714Reputation: 714Reputation: 714Reputation: 714Reputation: 714Reputation: 714
Exclamation 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?
 
Old 04-11-2010, 11:20 AM   #2
brianL
LQ 5k Club
 
Registered: Jan 2006
Location: Oldham, Lancs, England
Distribution: Slackware & Slackware64 14.1
Posts: 7,081
Blog Entries: 52

Rep: Reputation: Disabled
Switch to Slackware.
 
0 members found this post helpful.
Old 04-11-2010, 11:20 AM   #3
pixellany
LQ Veteran
 
Registered: Nov 2005
Location: Annapolis, MD
Distribution: Arch/XFCE
Posts: 17,802

Rep: Reputation: 728Reputation: 728Reputation: 728Reputation: 728Reputation: 728Reputation: 728Reputation: 728
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.
 
Old 04-11-2010, 11:23 AM   #4
linus72
Guru
 
Registered: Jan 2009
Location: Gordonsville-AKA Mayberry-Virginia
Distribution: PocketWriter/MinimalX
Posts: 5,084

Rep: Reputation: 336Reputation: 336Reputation: 336Reputation: 336
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
 
Old 04-11-2010, 11:24 AM   #5
MTK358
LQ 5k Club
 
Registered: Sep 2009
Posts: 6,443
Blog Entries: 3

Original Poster
Rep: Reputation: 714Reputation: 714Reputation: 714Reputation: 714Reputation: 714Reputation: 714Reputation: 714
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):
Attached Images
File Type: jpg vboxerror.jpg (75.6 KB, 11 views)
 
Old 04-11-2010, 11:28 AM   #6
pixellany
LQ Veteran
 
Registered: Nov 2005
Location: Annapolis, MD
Distribution: Arch/XFCE
Posts: 17,802

Rep: Reputation: 728Reputation: 728Reputation: 728Reputation: 728Reputation: 728Reputation: 728Reputation: 728
Quote:
Originally Posted by MTK358 View Post
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.
 
Old 04-11-2010, 11:33 AM   #7
damgar
Senior Member
 
Registered: Sep 2009
Location: dallas, tx
Distribution: Slackware - current multilib/gsb Arch
Posts: 1,949
Blog Entries: 8

Rep: Reputation: 201Reputation: 201Reputation: 201
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.

Last edited by damgar; 04-11-2010 at 11:37 AM.
 
Old 04-11-2010, 12:01 PM   #8
adamk75
Senior Member
 
Registered: May 2006
Posts: 3,091

Rep: Reputation: 397Reputation: 397Reputation: 397Reputation: 397
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
 
Old 04-11-2010, 12:03 PM   #9
adamk75
Senior Member
 
Registered: May 2006
Posts: 3,091

Rep: Reputation: 397Reputation: 397Reputation: 397Reputation: 397
Sorry, duplicate.

Last edited by adamk75; 04-11-2010 at 12:05 PM.
 
Old 04-11-2010, 12:03 PM   #10
pixellany
LQ Veteran
 
Registered: Nov 2005
Location: Annapolis, MD
Distribution: Arch/XFCE
Posts: 17,802

Rep: Reputation: 728Reputation: 728Reputation: 728Reputation: 728Reputation: 728Reputation: 728Reputation: 728
Pardon my ignorance, but what is "KMS"?
 
Old 04-11-2010, 12:07 PM   #11
adamk75
Senior Member
 
Registered: May 2006
Posts: 3,091

Rep: Reputation: 397Reputation: 397Reputation: 397Reputation: 397
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
 
Old 04-11-2010, 01:09 PM   #12
MTK358
LQ 5k Club
 
Registered: Sep 2009
Posts: 6,443
Blog Entries: 3

Original Poster
Rep: Reputation: 714Reputation: 714Reputation: 714Reputation: 714Reputation: 714Reputation: 714Reputation: 714
I noticed that now it takes much less time to switch between X and VTs, which is nice, too.
Attached Files
File Type: log Xorg.0.log (32.2 KB, 4 views)
 
Old 04-11-2010, 01:19 PM   #13
adamk75
Senior Member
 
Registered: May 2006
Posts: 3,091

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

Adam
 
Old 04-11-2010, 01:25 PM   #14
MTK358
LQ 5k Club
 
Registered: Sep 2009
Posts: 6,443
Blog Entries: 3

Original Poster
Rep: Reputation: 714Reputation: 714Reputation: 714Reputation: 714Reputation: 714Reputation: 714Reputation: 714
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
 
Old 04-11-2010, 01:36 PM   #15
adamk75
Senior Member
 
Registered: May 2006
Posts: 3,091

Rep: Reputation: 397Reputation: 397Reputation: 397Reputation: 397
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
 
1 members found this post helpful.
  


Reply


Thread Tools Search this Thread
Search this Thread:

Advanced Search

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

BB code is On
Smilies are On
[IMG] code is Off
HTML code is Off


Similar Threads
Thread Thread Starter Forum Replies Last Post
Totally messed up the user permissions.*want to cry* hottdogg Slackware 6 08-31-2007 06:00 AM
Totally messed up the user permissions.*want to cry* hottdogg Slackware 2 08-30-2007 03:13 PM
sound totally messed up djlosch Linux - Hardware 8 09-02-2004 10:24 PM
GRUB is totally messed up! is blaster to blame randyriver10 Linux - Software 6 03-22-2004 06:28 PM
Huge problem: Slackware 8.1, the file 'crt1.o' is totally missing fern Linux - General 11 07-11-2002 01:15 PM


All times are GMT -5. The time now is 06:40 PM.

Main Menu
My LQ
Write for LQ
LinuxQuestions.org is looking for people interested in writing Editorials, Articles, Reviews, and more. If you'd like to contribute content, let us know.
Main Menu
Syndicate
RSS1  Latest Threads
RSS1  LQ News
Twitter: @linuxquestions
identi.ca: @linuxquestions
Facebook: linuxquestions Google+: linuxquestions
Open Source Consulting | Domain Registration