Hi
My current problem is that I can do xinit on :1 but not on :0. This is a bit of a thorn in my side, as I have to use a VNC client to access the machine and I'd rather use it locally.
My hardware, output of lspci:
My xorg.conf
For my driver install, I have downloaded ati-driver-installer-8.36.5-x86.x86_64.run. I used the --buildpkg Fedora/FC6 option. This failed for the following reasons, all have been corrected and this fileset is the generated result.
ATI-fglrx-8.36.5-1.fc6.i386.rpm
ATI-fglrx-control-center-8.36.5-1.fc6.i386.rpm
ATI-fglrx-devel-8.36.5-1.fc6.i386.rpm
kernel-module-ATI-fglrx-2.6.20-1.2944.fc6-8.36.5-1.fc6.i386.rpm
Reasons for failure - default repos = livna was not involved
1. Missing kernel sources/headers (downloaded via yum, default repos)
2. Mismatched sources to kernel version (downloaded via yum, default repos)
Installed kernel module, then ATI-fglrx, then ATI-fglrx-devel, then the control center. I then run aticonfig --initial --input=/etc/X11/xorg.conf --resolution=0,1280x1024,1024x768,800x600 and it overwrites my xorg.conf file.
All seems to go fine. I reboot using kernel 2.6.20-1.2944.fc6 and try to startx. While the system is working, its nonresponsive. I can't switch terminals after startx is issued. I edited my /root/.vnc/xstartup to use xinit instead of twm and gnome shows just fine via a VNC client. SSH is working as well.
That's where it all stops. So, if I'm able to start a display on :1, why not :0? Things seem to be going OK.
Brief output of /var/log/Xorg.0.log
Any other information I can provide? While I'm not without a system, this isn't exactly ideal, but I can get by with what I need to do. Thanks in advance.
My current problem is that I can do xinit on :1 but not on :0. This is a bit of a thorn in my side, as I have to use a VNC client to access the machine and I'd rather use it locally.
My hardware, output of lspci:
Code:
00:00.0 RAM memory: nVidia Corporation C51 Host Bridge (rev a2) 00:00.1 RAM memory: nVidia Corporation C51 Memory Controller 0 (rev a2) 00:00.2 RAM memory: nVidia Corporation C51 Memory Controller 1 (rev a2) 00:00.3 RAM memory: nVidia Corporation C51 Memory Controller 5 (rev a2) 00:00.4 RAM memory: nVidia Corporation C51 Memory Controller 4 (rev a2) 00:00.5 RAM memory: nVidia Corporation C51 Host Bridge (rev a2) 00:00.6 RAM memory: nVidia Corporation C51 Memory Controller 3 (rev a2) 00:00.7 RAM memory: nVidia Corporation C51 Memory Controller 2 (rev a2) 00:02.0 PCI bridge: nVidia Corporation C51 PCI Express Bridge (rev a1) 00:03.0 PCI bridge: nVidia Corporation C51 PCI Express Bridge (rev a1) 00:04.0 PCI bridge: nVidia Corporation C51 PCI Express Bridge (rev a1) 00:09.0 RAM memory: nVidia Corporation MCP51 Host Bridge (rev a2) 00:0a.0 ISA bridge: nVidia Corporation MCP51 LPC Bridge (rev a3) 00:0a.1 SMBus: nVidia Corporation MCP51 SMBus (rev a3) 00:0a.2 RAM memory: nVidia Corporation MCP51 Memory Controller 0 (rev a3) 00:0b.0 USB Controller: nVidia Corporation MCP51 USB Controller (rev a3) 00:0b.1 USB Controller: nVidia Corporation MCP51 USB Controller (rev a3) 00:0d.0 IDE interface: nVidia Corporation MCP51 IDE (rev a1) 00:0e.0 IDE interface: nVidia Corporation MCP51 Serial ATA Controller (rev a1) 00:0f.0 IDE interface: nVidia Corporation MCP51 Serial ATA Controller (rev a1) 00:10.0 PCI bridge: nVidia Corporation MCP51 PCI Bridge (rev a2) 00:10.1 Audio device: nVidia Corporation MCP51 High Definition Audio (rev a2) 00:14.0 Bridge: nVidia Corporation MCP51 Ethernet Controller (rev a3) 00:18.0 Host bridge: Advanced Micro Devices [AMD] K8 [Athlon64/Opteron] HyperTransport Technology Configuration 00:18.1 Host bridge: Advanced Micro Devices [AMD] K8 [Athlon64/Opteron] Address Map 00:18.2 Host bridge: Advanced Micro Devices [AMD] K8 [Athlon64/Opteron] DRAM Controller 00:18.3 Host bridge: Advanced Micro Devices [AMD] K8 [Athlon64/Opteron] Miscellaneous Control 01:09.0 USB Controller: NEC Corporation USB (rev 43) 01:09.1 USB Controller: NEC Corporation USB (rev 43) 01:09.2 USB Controller: NEC Corporation USB 2.0 (rev 04) 02:00.0 VGA compatible controller: ATI Technologies Inc R520 [Radeon X1800] 02:00.1 Display controller: ATI Technologies Inc R520 [Radeon X1800] (Secondary)
My xorg.conf
Code:
[root@localhost X11]# cat xorg.conf # Xorg configuration created by pyxf86config Section "ServerLayout" Identifier "Default Layout" Screen 0 "aticonfig-Screen[0]" 0 0 InputDevice "Keyboard0" "CoreKeyboard" EndSection Section "Files" EndSection Section "Module" EndSection Section "InputDevice" Identifier "Keyboard0" Driver "kbd" Option "XkbModel" "pc105" Option "XkbLayout" "us" EndSection Section "Monitor" Identifier "aticonfig-Monitor[0]" Option "VendorName" "ATI Proprietary Driver" Option "ModelName" "Generic Autodetecting Monitor" Option "DPMS" "true" EndSection Section "Device" Identifier "Videocard0" Driver "vesa" EndSection Section "Device" Identifier "aticonfig-Device[0]" Driver "fglrx" EndSection Section "Screen" Identifier "Screen0" Device "Videocard0" DefaultDepth 24 SubSection "Display" Viewport 0 0 Depth 24 EndSubSection EndSection Section "Screen" Identifier "aticonfig-Screen[0]" Device "aticonfig-Device[0]" Monitor "aticonfig-Monitor[0]" DefaultDepth 24 SubSection "Display" Viewport 0 0 Depth 24 Modes "1280x1024" "1024x768" "800x600" EndSubSection EndSection [root@localhost X11]#
ATI-fglrx-8.36.5-1.fc6.i386.rpm
ATI-fglrx-control-center-8.36.5-1.fc6.i386.rpm
ATI-fglrx-devel-8.36.5-1.fc6.i386.rpm
kernel-module-ATI-fglrx-2.6.20-1.2944.fc6-8.36.5-1.fc6.i386.rpm
Reasons for failure - default repos = livna was not involved
1. Missing kernel sources/headers (downloaded via yum, default repos)
2. Mismatched sources to kernel version (downloaded via yum, default repos)
Installed kernel module, then ATI-fglrx, then ATI-fglrx-devel, then the control center. I then run aticonfig --initial --input=/etc/X11/xorg.conf --resolution=0,1280x1024,1024x768,800x600 and it overwrites my xorg.conf file.
All seems to go fine. I reboot using kernel 2.6.20-1.2944.fc6 and try to startx. While the system is working, its nonresponsive. I can't switch terminals after startx is issued. I edited my /root/.vnc/xstartup to use xinit instead of twm and gnome shows just fine via a VNC client. SSH is working as well.
That's where it all stops. So, if I'm able to start a display on :1, why not :0? Things seem to be going OK.
Brief output of /var/log/Xorg.0.log
Code:
[root@localhost log]# cat Xorg.0.log | grep "(EE)" (WW) warning, (EE) error, (NI) not implemented, (??) unknown. [root@localhost log]# cat Xorg.0.log | grep "(WW)" (WW) warning, (EE) error, (NI) not implemented, (??) unknown. (WW) The core pointer device wasn't specified explicitly in the layout. (WW) fglrx: No matching Device section for instance (BusID PCI:2:0:1) found [root@localhost log]#
Comment