Trying to fix Sluggish System

CaptainKirk · 2009-11-12 12:28:59

My Firefox has been slow for a while. I see online some say to reinstall 3.5 or to make a new profile. After the xorg 1.7 upgrade, however, I had to switch to nouveau drivers instead of nvidia and now my system seems unbearably slow sometimes. When I launch an app or save a spreadsheet, it takes literally a few seconds. Should be fast on a dual core 2G CPU with 2 G RAM.

My only thought is to downgrade xorg as per http://bbs.archlinux.org/viewtopic.php? … 93#p651793 and try to return to nvidia.

I also have a bug with nouveau that sometimes colors change at random in FF and Thunderbird. What happens it that half the text on a page on FF suddenly goes white, for no known reason. I must restart FF and then it's OK. I realize this is *may* be a bug with nouveau and not Arch, but anyway I need a stable system.

any other suggestions beyond the above forum post?

Thanks.

MadTux · 2009-11-12 18:07:18

Did you already play around with kernel mode setting, e.g. disabling it with nomodeset in /boot/grub/menu.lst? On my two systems, one requires KMS and the other is almost unusable if it is enabled.

CaptainKirk · 2009-11-12 18:13:13

No. Don't even know what that is. But you are saying to disable it as per http://wiki.archlinux.org/index.php/ATI#Disable_KMS by changing this in my grub.lst

# (0) Arch Linux
title  Arch Linux
root   (hd1,0)
kernel /vmlinuz26 root=/dev/disk/by-uuid/d9383ddd-35dd-406a-b0d1-1fe7a753d9b5 ro
initrd /kernel26.img

to:

# (0) Arch Linux
title  Arch Linux
root   (hd1,0)
kernel /vmlinuz26 root=/dev/disk/by-uuid/d9383ddd-35dd-406a-b0d1-1fe7a753d9b5 ro nomodeset
initrd /kernel26.img

?

I also must "Rebuild the initramfs" like it says there?

Thank you.

MadTux · 2009-11-12 19:00:47

You need to rebuild your initramfs, if you made changes to /etc/mkinitcpio.conf (however, it doesn't hurt to rebuild it anyways). If you want a higher resolution in your console, don't forget to add vga=773 after nomodeset.

CaptainKirk · 2009-11-13 09:00:50

I tried adding nomodeset. How can I tell if it worked? I don't see anywhere how to determine if I am running KMS or not.

shining · 2009-11-13 09:25:53

This is how you tell :

$ cat /proc/fb 
0 nouveaufb

nouveaufb is used = kms is enabled

Please try both with and without kms.
And please report these issues to nouveau developers before downgrading.

signor_rossi · 2009-11-13 09:29:46

May not be related, but latest xorg update fixed some sluggishness I saw with yakuake and kmenu, radeon card and driver, though. kms is diasabled, but it did work well and I only disabled it because no power saving with it yet.

signorRossi.

CaptainKirk · 2009-11-13 10:16:10

The command "cat /proc/fb" yields no results. So I guess I got it disabled. But it doesn't seem to help much. Opening a 7K spreadsheet in OpenOffice takes a few seconds. But the CPU monitor is flat, meaning almost no stress on the CPU.

Maybe it's the hard disk?

I can't even upgrade xorg-server now due to:

:: xorg-server conflicts with nvidia-173xx-utils. Remove nvidia-173xx-utils? [Y/n] y
error: failed to prepare transaction (could not satisfy dependencies)
:: xorg-server: requires libgl
:: mesa: requires libgl
:: mplayer: requires libgl
:: nvidia-173xx: requires nvidia-173xx-utils
:: xorg-utils: requires libgl

Yeah, I will report to nouveau b/c also sometimes my mouse in FF flickers--like it changes mouse icons very fast and I almost can't click on a link. Weird.

OK, unless there's anything else I can try, I will try to downgrade X.

Thanks.

shining · 2009-11-13 10:23:59

CaptainKirk wrote:

The command "cat /proc/fb" yields no results. So I guess I got it disabled. But it doesn't seem to help much. Opening a 7K spreadsheet in OpenOffice takes a few seconds. But the CPU monitor is flat, meaning almost no stress on the CPU.
Maybe it's the hard disk?
I can't even upgrade xorg-server now due to:
:: xorg-server conflicts with nvidia-173xx-utils. Remove nvidia-173xx-utils? [Y/n] y
error: failed to prepare transaction (could not satisfy dependencies)
:: xorg-server: requires libgl
:: mesa: requires libgl
:: mplayer: requires libgl
:: nvidia-173xx: requires nvidia-173xx-utils
:: xorg-utils: requires libgl
Yeah, I will report to nouveau b/c also sometimes my mouse in FF flickers--like it changes mouse icons very fast and I almost can't click on a link. Weird.
OK, unless there's anything else I can try, I will try to downgrade X.
Thanks.

Remove nvidia-173xx and nvidia-173xx-utils then add "nouveau.modeset=1" in grub kernel boot line.
Then try again until you see nouveaufb in cat /proc/fb

CaptainKirk · 2009-11-13 10:39:55

Sorry if this is a stupid question, but is it safe to remove those? I know that those 2 packages themselves I'm not using and I know that I can remove mplayer and reinstall it later (I hope I can anyhow) but last time I tried this I got a never-ending list of dependencies that I had to remove first and I don't know what these things are that I'm removing.

Maybe I need some of them? like libgl and mesa etc.

shining · 2009-11-13 10:42:42

CaptainKirk wrote:

Sorry if this is a stupid question, but is it safe to remove those? I know that those 2 packages themselves I'm not using and I know that I can remove mplayer and reinstall it later (I hope I can anyhow) but last time I tried this I got a never-ending list of dependencies that I had to remove first and I don't know what these things are that I'm removing.
Maybe I need some of them? like libgl and mesa etc.

1) pacman -Rd nvidia-173xx nvidia-173xx-utils
2) pacman -S libgl

Reverse these two operations when you want to switch back to nvidia. (but you cannot use nvidia anyway while you have xorg-server 1.7).

CaptainKirk · 2009-11-13 11:35:56

OK, I got it. I had to reboot a few times and do full system upgrade, but now I have nouveaufb in cat /proc/fb and everything up to date. It does appear to be better as well. I must run more tests to be sure.

But now the problem is that my dual monitor setup is lost.

Here is xrandr and below my xorg.conf that worked for dual monitor without
nouveaufb in cat /proc/fb.

I don't see how to renable my second monitor.

[kirk@localhost ~]$ xrandr -q
Screen 0: minimum 320 x 200, current 1024 x 768, maximum 8192 x 8192
DVI-I-0 connected 1024x768+0+0 (normal left inverted right x axis y axis) 310mm x 230mm
   1024x768       85.0*+   85.0     75.1     70.1     60.0  
   1280x1024      60.0  
   800x600        85.1     72.2     75.0     60.3     56.2  
   640x480        72.8     75.0     60.0  
   720x400        70.1  
VGA-0 disconnected (normal left inverted right x axis y axis)
[kirk@localhost ~]$ xrandr --output VGA-0 --mode 1024x768 --rate 75
xrandr: cannot find mode 1024x768
[kirk@localhost ~]$ cat /etc/X11/xorg.conf
Section "ServerLayout"
    Identifier     "X.org Configured"
    Screen      0  "Screen0" 0 0
    InputDevice    "Mouse0" "CorePointer"
    InputDevice    "Keyboard0" "CoreKeyboard"
EndSection

Section "Files"
    ModulePath   "/usr/lib/xorg/modules"
    FontPath     "/usr/share/fonts/misc"
    FontPath     "/usr/share/fonts/100dpi:unscaled"
    FontPath     "/usr/share/fonts/75dpi:unscaled"
    FontPath     "/usr/share/fonts/TTF"
    FontPath     "/usr/share/fonts/Type1"
EndSection

Section "Module"
    Load  "glx"
    Load  "record"
    Load  "extmod"
    Load  "dri"
    Load  "dbe"
    Load  "dri2"
EndSection

Section "InputDevice"
    Identifier  "Keyboard0"
    Driver      "kbd"
EndSection

Section "InputDevice"
    Identifier  "Mouse0"
    Driver      "mouse"
    Option        "Protocol" "auto"
    Option        "Device" "/dev/input/mice"
    Option        "ZAxisMapping" "4 5 6 7"
EndSection

Section "Monitor"
    #DisplaySize      310   230    # mm
    Identifier   "DVI-I-0"
    VendorName   "BNQ"
    ModelName    "BENQ G774"
    HorizSync    30.0 - 72.0
    VertRefresh  50.0 - 120.0
    Option        "DPMS"
EndSection

Section "Monitor"
    Identifier   "VGA-0"
    Option       "RightOf" "DVI-I-0"

    HorizSync       30.0 - 72.0
    VertRefresh     50.0 - 120.0
    EndSection

Section "Device"
        ### Available Driver options are:-
        ### Values: <i>: integer, <f>: float, <bool>: "True"/"False",
        ### <string>: "String", <freq>: "<f> Hz/kHz/MHz"
        ### [arg]: arg optional
        #Option     "SWcursor"               # [<bool>]
        #Option     "HWcursor"               # [<bool>]
        #Option     "NoAccel"                # [<bool>]
        #Option     "ShadowFB"               # [<bool>]
        #Option     "VideoKey"               # <i>
        #Option     "FPDither"               # [<bool>]
        #Option     "FPScale"                # [<bool>]
        #Option     "ScalingMode"            # <str>
        #Option     "EXAPixmaps"             # [<bool>]
    Identifier  "Card0"
    Driver      "nouveau"
    VendorName  "nVidia Corporation"
    BoardName   "G98 [GeForce 9300 GS]"
    BusID       "PCI:4:0:0"
EndSection

Section "Screen"
    Identifier "Screen0"
    Device     "Card0"
    Monitor    "Monitor0"
    SubSection "Display"
        Viewport   0 0
        Depth     1
    EndSubSection
    SubSection "Display"
        Viewport   0 0
        Depth     4
    EndSubSection
    SubSection "Display"
        Viewport   0 0
        Depth     8
    EndSubSection
    SubSection "Display"
        Viewport   0 0
        Depth     15
    EndSubSection
    SubSection "Display"
        Viewport   0 0
        Depth     16
    EndSubSection
    SubSection "Display"
        Viewport   0 0
        Depth     24
    EndSubSection
EndSection

shining · 2009-11-13 11:47:23

Could you paste the output of dmesg and /var/log/Xorg.0.log somewhere ?
dmesg is the most important

Your card is G98 [GeForce 9300 GS] ??
Why the hell were you trying to use nvidia-173xx then ?
http://www.nvidia.com/object/linux_disp … 90.42.html

CaptainKirk · 2009-11-13 12:00:32

dmesg http://pastebin.com/m10b02120
xorg.0.log : http://pastebin.com/m11d2928d

> Your card is G98 [GeForce 9300 GS] ??

Yep.

> Why the hell were you trying to use nvidia-173xx then ?

What, you think I know what I'm doing? I actually don't. I don't recall why I tried that, but it worked. Dual monitor and all.

Thanks for your help.

shining · 2009-11-13 12:22:49

CaptainKirk wrote:

dmesg http://pastebin.com/m10b02120
xorg.0.log : http://pastebin.com/m11d2928d

The two logs were cut , can you try again, making sure the full thing was pasted ?
Maybe try another paste site : http://pastebin.ca/

> Your card is G98 [GeForce 9300 GS] ??
Yep.
> Why the hell were you trying to use nvidia-173xx then ?
What, you think I know what I'm doing? I actually don't. I don't recall why I tried that, but it worked. Dual monitor and all.
Thanks for your help.

If you want to contribute to open source community and nouveau development, keep trying to investigate why your dual monitor does not work, it really should.

If you don't, you can use the latest nvidia proprietary driver (nvidia and nvidia-utils).
Only the people who have older nvidia cards are forced to use the older 173xx version which does not support xorg 1.7

CaptainKirk · 2009-11-13 12:47:08

Full files are here: http://tinyurl.com/y8s4zgy

Thank you.

shining · 2009-11-13 12:58:16

nouveau 0000:04:00.0: PCI INT A -> GSI 16 (level, low) -> IRQ 16
nouveau 0000:04:00.0: setting latency timer to 64
[drm] nouveau 0000:04:00.0: Detected an NV50 generation card (0x298080a2)
[drm] nouveau 0000:04:00.0: Attempting to load BIOS image from PRAMIN
[drm] nouveau 0000:04:00.0: ... appears to be valid
[drm] nouveau 0000:04:00.0: BIT BIOS found
[drm] nouveau 0000:04:00.0: Bios version 62.98.39.00
[drm] nouveau 0000:04:00.0: TMDS table revision 2.0 not currently supported
[drm] nouveau 0000:04:00.0: Found Display Configuration Block version 4.0
[drm] nouveau 0000:04:00.0: Raw DCB entry 0: 02000300 00000028
[drm] nouveau 0000:04:00.0: Raw DCB entry 1: 01000302 00020030
[drm] nouveau 0000:04:00.0: Raw DCB entry 2: 04011310 00000028
[drm] nouveau 0000:04:00.0: Raw DCB entry 3: 010223f1 00c0c080
[drm] nouveau 0000:04:00.0: Parsing VBIOS init table 0 at offset 0xD4FE
[drm] nouveau 0000:04:00.0: 0xD7BA: Init table command not found: 0x5C
[drm] nouveau 0000:04:00.0: Parsing VBIOS init table 1 at offset 0xD8D0
[drm] nouveau 0000:04:00.0: Parsing VBIOS init table 2 at offset 0xE176
[drm] nouveau 0000:04:00.0: Parsing VBIOS init table 3 at offset 0xE268
[drm] nouveau 0000:04:00.0: Parsing VBIOS init table 4 at offset 0xE474
[drm] nouveau 0000:04:00.0: Parsing VBIOS init table at offset 0xE4D9
.....
[drm] nouveau 0000:04:00.0: 0xE4D9: Condition still not met after 2000ms, skipping following opcodes
[drm] nouveau 0000:04:00.0: 0xC47C: parsing output script 0
[drm] nouveau 0000:04:00.0: 0xAE8A: parsing output script 0
[TTM] Zone  kernel: Available graphics memory: 443110 kiB.
[TTM] Zone highmem: Available graphics memory: 1036906 kiB.
[drm] nouveau 0000:04:00.0: 256 MiB VRAM
[drm] nouveau 0000:04:00.0: 512 MiB GART (aperture)
[drm] nouveau 0000:04:00.0: Allocating FIFO number 1
[drm] nouveau 0000:04:00.0: nouveau_channel_alloc: initialised FIFO 1
[drm] nouveau 0000:04:00.0: Detected a DAC output
[drm] nouveau 0000:04:00.0: Detected a TMDS output
[drm] nouveau 0000:04:00.0: Detected a DAC output
[drm] nouveau 0000:04:00.0: DCB encoder 1 unknown
[drm] nouveau 0000:04:00.0: Detected a DVI-I connector
[drm] nouveau 0000:04:00.0: Detected a VGA connector
[drm:edid_is_valid] *ERROR* Raw EDID:
<3>00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00  ................
<3>00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00  ................
<3>00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00  ................
<3>00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00  ................
<3>00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00  ................
<3>00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00  ................
<3>00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00  ................
<3>00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00  ................

nouveau 0000:04:00.0: VGA-1: EDID invalid.
[drm] nouveau 0000:04:00.0: DDC responded, but no EDID for VGA-1
[drm] nouveau 0000:04:00.0: allocated 1024x768 fb: 0x40250000, bo f6462a00
[drm] DAC-7: set mode 1024x768 20
Console: switching to colour frame buffer device 128x48
[drm] nouveau 0000:04:00.0: 0x1203: parsing clock script 0
fb0: nouveaufb frame buffer device
registered panic notifier
[drm] Initialized nouveau 0.0.15 20090420 for 0000:04:00.0 on minor 0

The EDID invalid stuff does not look good at all.
Then your log is full of it :

[drm:edid_is_valid] *ERROR* Raw EDID:
<3>00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00  ................
<3>00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00  ................
<3>00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00  ................
<3>00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00  ................
<3>00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00  ................
<3>00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00  ................
<3>00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00  ................
<3>00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00  ................

nouveau 0000:04:00.0: VGA-1: EDID invalid.
[drm] nouveau 0000:04:00.0: DDC responded, but no EDID for VGA-1
[drm:edid_is_valid] *ERROR* Raw EDID:
<3>00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00  ................
<3>00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00  ................
<3>00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00  ................
<3>00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00  ................
<3>00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00  ................
<3>00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00  ................
<3>00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00  ................
<3>00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00  ................

nouveau 0000:04:00.0: VGA-1: EDID invalid.

We probably need to forward this upstream.

CaptainKirk · 2009-11-13 13:02:28

shining wrote:

We probably need to forward this upstream.

OK, so could you please:

1. Tell me what information I should post about this issue (if anything more than those 2 files) and where is the correct place to post.

2. What pacman command should I use to try the other nvidia? 196 I think.

Thank you for your assistance. I would have preferred to use the open source driver actually, but I do need dual monitors.

shining · 2009-11-13 13:10:33

CaptainKirk wrote:

shining wrote:
We probably need to forward this upstream.
OK, so could you please:
1. Tell me what information I should post about this issue (if anything more than those 2 files) and where is the correct place to post.
2. What pacman command should I use to try the other nvidia? 196 I think.
Thank you for your assistance. I would have preferred to use the open source driver actually, but I do need dual monitors.

Oh wait, before reporting, could you try the latest nouveau-drm from testing :
$ sudo pacman -U ftp://ftp.rez-gif.supelec.fr/Linux/arch … pkg.tar.gz
then reboot, and check your log again, if you still see the same EDID error.

If yes, go to http://nouveau.freedesktop.org/wiki/ and read the BUGS section.

For the bug report , just include these information :
- your card model
- the date of nouveau-drm (eg 20091101 if you keep your old logs , or 20091111 if you attach your new logs)
- output of xrandr which shows your vga disconnected
- the two logs

CaptainKirk · 2009-11-13 13:17:05

sudo pacman -U ftp://ftp.rez-gif.supelec.fr/Linux/archlinux/testing/os/i686/nouveau-drm-0.0.15_20091111-1-i686.pkg.tar.gz
Password: 
 nouveau-drm-0.0.15_...   316.3K  254.1K/s 00:00:01 [#####################] 100%
loading package data...
checking dependencies...
(1/1) checking for file conflicts                   [#####################] 100%
(1/1) upgrading nouveau-drm                         [#####################] 100%
ERROR: Module nouveau is in use
if you are running kms in early mode please rebuild your initrd
In order to use the new nouveau module, exit Xserver and unload it manually.

I can kill X and try this again, but do I still need to rebuilt initrd? How do I do that?

PS: I must go now, so I will follow up with this tomorrow.

Thank you.

shining · 2009-11-13 13:21:20

CaptainKirk wrote:

sudo pacman -U ftp://ftp.rez-gif.supelec.fr/Linux/archlinux/testing/os/i686/nouveau-drm-0.0.15_20091111-1-i686.pkg.tar.gz
Password: 
 nouveau-drm-0.0.15_...   316.3K  254.1K/s 00:00:01 [#####################] 100%
loading package data...
checking dependencies...
(1/1) checking for file conflicts                   [#####################] 100%
(1/1) upgrading nouveau-drm                         [#####################] 100%
ERROR: Module nouveau is in use
if you are running kms in early mode please rebuild your initrd
In order to use the new nouveau module, exit Xserver and unload it manually.

I can kill X and try this again, but do I still need to rebuilt initrd? How do I do that?

PS: I must go now, so I will follow up with this tomorrow.

Thank you.

You need to rebuild the initrd if you added nouveau to it in the first place. Did you ?

And after that, just reboot.

CaptainKirk · 2009-11-14 17:18:54

This is what I see now:

[kirk@localhost ~]$ sudo pacman -Qs nouveau
local/nouveau-drm 0.0.15_20091111-1
    nvidia opensource X driver
local/xf86-video-nouveau 0.0.10_git20091101-1 (xorg-video-drivers)
    Open Source 3D acceleration driver for nVidia cards (experimental)

and this in dmesg still

nouveau 0000:04:00.0: VGA-1: EDID invalid.
[drm] nouveau 0000:04:00.0: DDC responded, but no EDID for VGA-1
[drm:edid_is_valid] *ERROR* Raw EDID:
<3>00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00  ................
<3>00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00  ................
<3>00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00  ................
<3>00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00  ................
<3>00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00  ................
<3>00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00  ................
<3>00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00  ................
<3>00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00  ................

nouveau 0000:04:00.0: VGA-1: EDID invalid.
[drm] nouveau 0000:04:00.0: DDC responded, but no EDID for VGA-1
[drm] nouveau 0000:04:00.0: Allocating FIFO number 2
[drm] nouveau 0000:04:00.0: nouveau_channel_alloc: initialised FIFO 2
[drm:edid_is_valid] *ERROR* Raw EDID:
<3>00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00  ................
<3>00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00  ................
<3>00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00  ................
<3>00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00  ................
<3>00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00  ................
<3>00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00  ................
<3>00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00  ................
<3>00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00  ................

Anything else I should be checking? I didn't change anything, just upgraded nouveau like you said and rebooted.

shining · 2009-11-14 17:36:19

CaptainKirk wrote:

Anything else I should be checking? I didn't change anything, just upgraded nouveau like you said and rebooted.

grep MODULES= /etc/mkinitcpio.conf

Did you put nouveau there or not ? If yes, you need to rebuild the initrd.

Then follow the instructions I gave you earlier :
go to http://nouveau.freedesktop.org/wiki/ and read the BUGS section.

For the bug report , just include these information :
- your card model
- the date of nouveau-drm : 20091111
- output of xrandr which shows your vga disconnected
- the two logs

shining · 2009-11-14 18:46:38

Thanks for the report : http://bugs.freedesktop.org/show_bug.cgi?id=25088
You did not need to put your problems about non-kms (color and performance). They are not relevant at all. And I am not sure if non-kms is still supported.

Also from that report, I saw you DO have nouveau in mkinitcpio.conf .
Did you ever rebuild the initrd to apply that change ?
bsdtar tf /boot/kernel26.img | grep nouveau

Anyway since you added it to the initrd, you DO need to rebuild the initrd each time you update nouveau-drm ...
mkinitcpio -p kernel26

CaptainKirk · 2009-11-14 18:52:00

I was going to post the report URL here.

Yes, I put nouvea in there and then did

sudo mkinitcpio -p kernel26

Now I removed nouveau via pacman, put in nvidia and removed nouveau from modules and ran the above again to rebuild.

Now I have nvidia and both monitors back. Speed thus far seems better also.

Thanks for the report

You embarass me by thanking me for a report. I owe YOU a great deal of gratitude for all of your help in this thread.

I truly appreciate it--thank you very much.

Arch Linux

#1 2009-11-12 12:28:59

Trying to fix Sluggish System

#2 2009-11-12 18:07:18

Re: Trying to fix Sluggish System

#3 2009-11-12 18:13:13

Re: Trying to fix Sluggish System

#4 2009-11-12 19:00:47

Re: Trying to fix Sluggish System

#5 2009-11-13 09:00:50

Re: Trying to fix Sluggish System

#6 2009-11-13 09:25:53

Re: Trying to fix Sluggish System

#7 2009-11-13 09:29:46

Re: Trying to fix Sluggish System

#8 2009-11-13 10:16:10

Re: Trying to fix Sluggish System

#9 2009-11-13 10:23:59

Re: Trying to fix Sluggish System

#10 2009-11-13 10:39:55

Re: Trying to fix Sluggish System

#11 2009-11-13 10:42:42

Re: Trying to fix Sluggish System

#12 2009-11-13 11:35:56

Re: Trying to fix Sluggish System

#13 2009-11-13 11:47:23

Re: Trying to fix Sluggish System

#14 2009-11-13 12:00:32

Re: Trying to fix Sluggish System

#15 2009-11-13 12:22:49

Re: Trying to fix Sluggish System

#16 2009-11-13 12:47:08

Re: Trying to fix Sluggish System

#17 2009-11-13 12:58:16

Re: Trying to fix Sluggish System

#18 2009-11-13 13:02:28

Re: Trying to fix Sluggish System

#19 2009-11-13 13:10:33

Re: Trying to fix Sluggish System

#20 2009-11-13 13:17:05

Re: Trying to fix Sluggish System

#21 2009-11-13 13:21:20

Re: Trying to fix Sluggish System

#22 2009-11-14 17:18:54

Re: Trying to fix Sluggish System

#23 2009-11-14 17:36:19

Re: Trying to fix Sluggish System

#24 2009-11-14 18:46:38

Re: Trying to fix Sluggish System

#25 2009-11-14 18:52:00

Re: Trying to fix Sluggish System

Board footer