Arch Linux

filam

Wiki Maintainer

From: Portland, ME

Registered: 2008-04-11

Posts: 158

Website

Resolution Failure

I just installed Arch on an old desktop and get this resolution problem (wmii,dwm, and awesome). What is the best way to increase my resolution?

Section "Monitor"
        Identifier   "Monitor0"
        VendorName   "Monitor Vendor"
        ModelName    "Monitor Model"
EndSection

Arg. What is the best way to upload my xorg? Can I just upload it as a file rather than copy and paste. I can't drag to select the entire file in nano.

edit: I'm looking at this res on a 20.1 in screen. :-(

Last edited by filam (2008-09-18 02:32:35)

byte

Member

From: Düsseldorf (DE)

Registered: 2006-05-01

Posts: 2,046

Re: Resolution Failure

Your /var/log/Xorg.0.log and monitor specs might help... try nopaste for uploading.

---

1000

Onwards

Member

From: Pakistan

Registered: 2007-04-18

Posts: 108

Re: Resolution Failure

edit: I'm looking at this res on a 20.1 in screen. :-(

That must be painful

filam

Wiki Maintainer

From: Portland, ME

Registered: 2008-04-11

Posts: 158

Website

Re: Resolution Failure

edit: I'm looking at this res on a 20.1 in screen. :-(

That must be painful

Haha. Oh yes. Its actually very funny. Especially for my roomates ("Linux is so silly. Why not install a better OS" and such, mostly joking). I also forgot to mention my mouse issues.

The mouse is restricted to the top half of the screen. This does not mean, however that I can't click on things in the lower half. The image of the mouse on the screen does not indicate where the mouse really is. It will actually ghost over the bottom half of the screen when the mouse image is in the bottom half of the top section of the screen. To further confuse you. The relation of the ghost to the image is exponential, meaning that the ghost is below the image at the top of the top half of the screen. When the image is at the bottom of the top half of the screen the ghost is at the bottom of the lower half of the screen. Make sense? :-)

Thanks byte. I'll upload it when I have the time and patience to deal with the aforementioned machine.

edit: xorg.conf & log

Originally I had the resolution problems with the trident driver. I am currently using vesa and don't experience the same problems with the resolution or the mouse. Is there an advantage of using trident over vesa?

Section "ServerLayout"
        Identifier     "X.org Configured"
        Screen      0  "Screen0" 0 0
        InputDevice    "Mouse0" "CorePointer"
        InputDevice    "Keyboard0" "CoreKeyboard"
EndSection

Section "Module"
        Load  "GLcore"
        Load  "dbe"
        Load  "dri"
        Load  "extmod"
        Load  "glx"
        Load  "record"
        Load  "xtrap"
        Load  "freetype"
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"
        Identifier   "Monitor0"
        VendorName   "Monitor Vendor"
        ModelName    "Monitor Model"
EndSection

Section "Device"
        ### Available Driver options are (removed for simplicity)
        Identifier  "Card0"
        Driver      "trident"
        VendorName  "Trident Microsystems"
        BoardName   "TGUI 9660/938x/968x"
        BusID       "PCI:0:13: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

Noteworthy sections of Xorg.0.log

...
(WW) Open ACPI failed (/var/run/acpid.socket) (No such file or directory)
...

I am currently using vesa so the outpot won't be the same, but when I was looking at Xorg.0.log before I switched I noticed it failed to default to the higher resolution because of lack of memory and failed to default to lower resolutions for another reasion I can not remember.

Last edited by filam (2008-09-18 14:05:51)

Onwards

Member

From: Pakistan

Registered: 2007-04-18

Posts: 108

Re: Resolution Failure

Advantage of using trident over vesa would be direct rendering support (better 2D, 3D performance). Plain vesa won't give you any direct rendering. But vesa is a catch-all generic driver for cards complying to vesa standard.