[Xorg] ~/.bashrc prevents Xorg to start [SOLVED]

kozaki · 2007-05-21 10:59:35

Houston, got a serious issue with X that started with Voodo install last March (updates since then did not change nothing).

So Xorg starts but stay * black * with a cursor and then I have to kill it as nothing happends.
There's not a single (EE) in the log !
Rest of the systems runs fine.
This is my main desktop PC (Arch's runs *fine* on my laptop and on a little server I have).
AMD64, GeForce 6200 TC256 PCIe, ViewSonic E92f+ 19".
Arch x86_64 0.8 Voodoo & Duke (latest packages) + Mandriva + other distribs I test.

- Xorg.0.log shows no error and a single warning: (WW) VGA(0): Bad V_BIOS checksum. With VGA driver it also shows (WW) VGA(0): Mode pool is empty
- It stays black whatever driver I use : NV & VGA (did not tested with nvidia as it does not find module)
- Stays black whatever WM I use : startkde, fluxbox or enlightenment_start, and with/without dbus (exec dbus-launch --auto-syntax --exit-with-session)
- Stays black whatever xorg.conf configuration: that one created with xorgconfig or the one that used to work with Arch until Christmas, and that works fine under Mandriva 2007(.1). Also tried w/ 1024x768 15 & 8-bit (vesa) with no change :!:

Conf & logs :
1 - xorg-server is installed.
2 - main xorg.conf
3 - xorg.conf generated with xorgconfig
4 - Xorg.0.log:
4.1 - with NV

cat Xorg.0.log|grep EE
Current Operating System: Linux llewellyn 2.6.21-ARCH #1 SMP PREEMPT Sun May 6 22:27:01 CEST 2007 x86_64

cat Xorg.0.log|grep WW
(WW) VGA(0): Bad V_BIOS checksum

4.2 - avec vga

cat Xorg.0.log|grep EE
Current Operating System: Linux llewellyn 2.6.21-ARCH #1 SMP PREEMPT Sun May 6 22:27:01 CEST 2007 x86_64unknown.

cat Xorg.0.log|grep WW
(WW) VGA(0): Bad V_BIOS checksum
(WW) VGA(0): Mode pool is empty

That warning "(WW) NVIDIA(0): Bad V_BIOS checksum" is supposed to not beeing an issue

5. udev seems to works fine, as agpgart (and does so for peripherals -> /dev/disks/by-*)

ls -l /dev/agpgart
crw-rw---- 1 root video 10, 175 mai 19 12:06 /dev/agpgart

dmesg shows nothing but standard about agpgart :

cat var/log/kernel.log |grep agpgart
May 19 09:04:10 llewellyn agpgart: Detected AGP bridge 20
May 19 09:04:10 llewellyn agpgart: AGP aperture is 128M @ 0xd8000000
May 19 09:04:10 llewellyn Linux agpgart interface v0.101 (c) Dave Jones

Same thing under Mandriva :

Linux agpgart interface v0.101 (c) Dave Jones
agpgart: Detected AGP bridge 20
agpgart: AGP aperture is 128M @ 0xd800000

/me lost and looking for indications about further steps

EDIT : forgot to say graphic card's a PCI Express.
Any chance this issue could be AGP/PCIgart related?

EDIT' : title to reflect the cause of this hard-to-find-out issue

Last edited by kozaki (2007-06-02 14:25:58)

kozaki · 2007-05-24 08:15:27

Hope someone can helps on this !
Without any usable log yet i simply dunno where to look for.

klixon · 2007-05-24 08:57:42

Is your user in the video-group?

# gpasswd -a <user> video

kozaki · 2007-05-24 18:50:04

yes he is klixton

video:x:91:kozaki

klixon · 2007-05-25 08:49:28

Is there a reason for you commenting out the HorizSync and VertRefresh in the monitor-section of xorg.conf?

Could you post the output of

# grep "HorizSync\|hsync\|VertRefresh\|vrefresh" /var/log/Xorg.0.log

Maybe pastebin your whole Xorg.0.log?

shining · 2007-05-25 09:00:34

klixon wrote:

Is there a reason for you commenting out the HorizSync and VertRefresh in the monitor-section of xorg.conf?

The reason is given in the xorg.conf itself :

### Comment all HorizSync and VertSync values to use DDC:

I don't have to specify these on any on my laptops or desktops.
There might be some cases where you need to find out the correct values and put them manually though
(I guess if DDC fails or reports wrong values, and it doesn't fall back on working values).

klixon · 2007-05-25 09:17:30

DDC aren't always correct. If you know the values from a specification (ie manual - tech specs), better put 'm in there.
My guess is you either recieve incorrect values or none, as your mode-pool is empty, even when you supply a mode-line (you probably have a lot of "{h,v}sync value out of range" in you Xorg log

But that's just a guess of course

ps: stupid question, but loads of PCIe cards need an extra power-supply feed to the card itself. Is that needed/connected?

Last edited by klixon (2007-05-25 09:19:10)

kozaki · 2007-05-25 23:43:59

Oh! I didn't think about checkin' this yet, and did not know this syntax thank you klixton
grep "HorizSync\|hsync\|VertRefresh\|vrefresh" /var/log/Xorg.0.log

(II) VGA(0): ViewSonic E92f+: Using default hsync range of 31.50-37.90 kHz
(II) VGA(0): ViewSonic E92f+: Using default vrefresh range of 50.00-70.00 Hz
(II) VGA(0): Modeline "Generic 320x200 default mode"   12.59  320 336 384 400  200 206 207 224 vscan 2 -hsync +vsync

I've put the whole Xorg.0.log (VESA) on pastebin.
I'll post the one with nv ASAP, and here's the log under running Mandriva 2007.1 (i586 with nvidia drivers, same machine).

There are no "{h,v}sync value out of range", but some interesting lines just arround hsync & vrefresh range:

(==) VGA(0): videoRam: 64 kBytes.
...
(II) VGA(0): Clock range:  23.17 to  30.32 MHz
(II) VGA(0): Not using default mode "640x350" (insufficient memory for mode)
(II) VGA(0): Not using default mode "320x175" (bad mode clock/interlace/doublescan)
(II) VGA(0): Not using default mode "640x400" (insufficient memory for mode)

woow.
- a screen that is not well recognized since this ViewSonic default's are : HorizSync 30-97 & VertRefresh 50-180.
- a GPU with 64 KO videoRAM Which would explain why it prints "Insufficient memory for default mode 640x350".

Things to remember:
1. Arch (32/64-bit) runned pretty well on this PC until January, and I changed nothin but a HDD that I added for lvm/software raid ;
2. it runs fine under installed Mandriva as well as every live Linux I trhow in it ;
3. and the GPU is one of the smallest PCIe nVidia cards (fanless without additional power-supply)

Next thing I'll try is uncommenting h/vsync range since I know them from the manual, check the card is well plugged (even if I know it works 5/5, or how could I watch tvtime or play another 3D game every evening ?)

kozaki · 2007-05-28 12:00:34

Update of this issue after some tweaks:
- BIOS : no more Cool'& Quiet, AGP aperture size 64Mo, PCI Latency edited to 64.
- Full système update
- re-installed nvidia then modprobe
- uncommented hsync & vsync with official VIewSonic E92f+ specs

Man, the're NO change
Beside that one : once, I've seen the nVidia logo (startx -- -layout NVIDIA) half a second, after what same full darj screen with "X" cursor

Les logs :
- No (EE) beside the one when using "nv" when I uncomment "glx" module's line
- RAM is actually well detected (see below with nv & nvidia) ;
- with "nv" every resolution seem to be a problem (?) but none with "nvidia"

/var/log/Xorg.0.log on Arch Linux 0.8 "Duke" (full update 2007-05-28) with "nv" driver
no "mode-pool is empty"

(EE) Failed to initialize GLX extension (Compatible NVIDIA X driver not found)
(WW) VGA(0): Bad V_BIOS checksum
...
(II) NV(0): Supported VESA Video Modes:
(II) NV(0): 720x400@70Hz
(II) NV(0): 720x400@88Hz
(II) NV(0): 640x480@60Hz
...
(II) NV(0): 1280x1024@75Hz
...
(--) NV(0): VideoRAM: 65536 kBytes
(==) NV(0): Using gamma correction (1.0, 1.0, 1.0)
(II) NV(0): ViewSonic E92f+: Using hsync range of 30.00-97.00 kHz
(II) NV(0): ViewSonic E92f+: Using vrefresh range of 50.00-180.00 Hz
(II) NV(0): Clock range:  12.00 to 400.00 MHz
(II) NV(0): Not using default mode "1600x1200" (hsync out of range)
(II) NV(0): Not using default mode "800x600" (hsync out of range)
(II) NV(0): Not using default mode "1360x768" (monitor doesn't support reduced blanking)
(II) NV(0): Not using default mode "1024x768" (hsync out of range)
(II) NV(0): Not using default mode "2048x1536" (width too large for virtual size)

/var/log/Xorg.0.log on Arch Linux 0.8 "Duke" (full update 2007-05-28) with "nvidia" driver
No (EE), (WW), nor "out of range"

(II) Bus -1: bridge is at (0:7:0), (0,-1,-1), BCTRL: 0x0008 (VGA_EN is set)
(--) PCI:*(1:0:0) nVidia Corporation NV44 [GeForce 6200 TurboCache(TM)] rev 161, Mem @ 0xfd000000/24, 0xc0000000/28, 0xfc000000/24, BIOS @ 0xfe7e0000/17
(II) Setting vga for screen 0.
(**) NVIDIA(0): Depth 24, (--) framebuffer bpp 32
(==) NVIDIA(0): RGB weight 888
(==) NVIDIA(0): Default visual is TrueColor
(==) NVIDIA(0): Using gamma correction (1.0, 1.0, 1.0)
(**) NVIDIA(0): Option "NoLogo" "0"
(**) NVIDIA(0): Option "NoDDC" "false"
(**) NVIDIA(0): Enabling RENDER acceleration
(II) NVIDIA(0): NVIDIA GPU GeForce 6200 TurboCache(TM) at PCI:1:0:0 (GPU-0)
(--) NVIDIA(0): Memory: 262144 kBytes
(--) NVIDIA(0): VideoBIOS: 05.44.02.11.00
(II) NVIDIA(0): Detected PCI Express Link width: 16X
(--) NVIDIA(0): Interlaced video modes are supported on this GPU
(--) NVIDIA(0): Connected display device(s) on GeForce 6200 TurboCache(TM) at
(--) NVIDIA(0):     PCI:1:0:0:
(--) NVIDIA(0):     ViewSonic E92f+-2 (CRT-0)
(--) NVIDIA(0): ViewSonic E92f+-2 (CRT-0): 400.0 MHz maximum pixel clock
(II) NVIDIA(0): Assigned Display Device: CRT-0
(II) NVIDIA(0): Validated modes:
(II) NVIDIA(0):     "1280x1024"
(II) NVIDIA(0):     "1024x768"
(II) NVIDIA(0):     "800x600"
(II) NVIDIA(0):     "640x480"
(II) NVIDIA(0):     "512x384"
(II) NVIDIA(0):     "400x300"
(II) NVIDIA(0):     "320x240"
(II) NVIDIA(0): Virtual screen size determined to be 1280 x 1024
(--) NVIDIA(0): DPI set to (90, 96); computed from "UseEdidDpi" X config
(--) NVIDIA(0):     option
(--) Depth 24 pixmap format is 32 bpp

Updated xorg.conf
Should I try with VESA as well ? edit 'Section "Files"' ?

still lost.

klixon · 2007-05-28 12:39:10

Wait, you do have a window-manager starting do you??
The log with nvidia-driver looks promising...

Last edited by klixon (2007-05-28 12:40:27)

hacosta · 2007-05-28 12:40:06

i think it's more of a wm issue why don't you try another one?

kozaki · 2007-05-28 12:54:13

Unfortunetly *nothing* starts visually but the "X" cursor.
I tried with 3 differents wm with same visual & log result.

kozaki wrote:

Stays black whatever WM I use : startkde, fluxbox or enlightenment_start, and with/without dbus (exec dbus-launch --auto-syntax --exit-with-session)
- Man, the're NO change
Beside that one : once, I've seen the nVidia logo (startx -- -layout NVIDIA) half a second, after what same full dark screen with "X" cursor

Last edited by kozaki (2007-05-28 12:54:50)

kozaki · 2007-05-28 14:48:21

osku asked me to check the rights on /tmp
Actually they are wrong :

drwxr-xr-x  2 root root

Will check it ASAP

Last edited by kozaki (2007-05-28 14:48:34)

kozaki · 2007-06-02 09:45:51

Solved !
There was 2 issues preventing X to load correctly.

1) Rights on /tmp
# chmod 777 /tmp
# chmod +t /tmp
# ls -ld /tmp
drwxrwxrwt 7 root root 26624 jun 2 09:27 /tmp
Did not change the way X starts : all black with a cursor.

2) User configuration's file
Missed ~/{.xseesion,.bash_profile}.
Copied default from /etc/skel
Did not change the way X starts : all black with a cursor.
Then I changed ~/.bashrc for default one.
My ~/.bashrc was heavily personnalized. It worked without issue with previous Arch.

That made Xorg startx perfectly (currently with nvidia driver)

Oh man! What a difference in term of speed
- pacman's operation are so much faster than back to pacman 2 (same machine) or current pacman on my small Dell Latitude L400 with arch32
- apps (like firefox) and everything's incredibly starts faster than on Mandriva with KDE or e17 (same machine)

Arch Linux

#1 2007-05-21 10:59:35

[Xorg] ~/.bashrc prevents Xorg to start [SOLVED]

#2 2007-05-24 08:15:27

Re: [Xorg] ~/.bashrc prevents Xorg to start [SOLVED]

#3 2007-05-24 08:57:42

Re: [Xorg] ~/.bashrc prevents Xorg to start [SOLVED]

#4 2007-05-24 18:50:04

Re: [Xorg] ~/.bashrc prevents Xorg to start [SOLVED]

#5 2007-05-25 08:49:28

Re: [Xorg] ~/.bashrc prevents Xorg to start [SOLVED]

#6 2007-05-25 09:00:34

Re: [Xorg] ~/.bashrc prevents Xorg to start [SOLVED]

#7 2007-05-25 09:17:30

Re: [Xorg] ~/.bashrc prevents Xorg to start [SOLVED]

#8 2007-05-25 23:43:59

Re: [Xorg] ~/.bashrc prevents Xorg to start [SOLVED]

#9 2007-05-28 12:00:34

Re: [Xorg] ~/.bashrc prevents Xorg to start [SOLVED]

#10 2007-05-28 12:39:10

Re: [Xorg] ~/.bashrc prevents Xorg to start [SOLVED]

#11 2007-05-28 12:40:06

Re: [Xorg] ~/.bashrc prevents Xorg to start [SOLVED]

#12 2007-05-28 12:54:13

Re: [Xorg] ~/.bashrc prevents Xorg to start [SOLVED]

#13 2007-05-28 14:48:21

Re: [Xorg] ~/.bashrc prevents Xorg to start [SOLVED]

#14 2007-06-02 09:45:51

Re: [Xorg] ~/.bashrc prevents Xorg to start [SOLVED]

Board footer