Bug 116332

Summary: No video output when X starts. Stopping X freezes system
Product: [openSUSE] SUSE LINUX 10.0 Reporter: Tom Eastep <teastep>
Component: X.OrgAssignee: Stefan Dirsch <sndirsch>
Status: RESOLVED FIXED QA Contact: Stefan Dirsch <sndirsch>
Severity: Critical    
Priority: P5 - None    
Version: RC 1   
Target Milestone: ---   
Hardware: i586   
OS: SUSE Other   
Whiteboard:
Found By: Beta-Customer Services Priority:
Business Priority: Blocker: ---
Marketing QA Status: --- IT Deployment: ---
Attachments: Xorg.0.log
xorg.conf
Xorg.0.log after xorg.conf changes

Description Tom Eastep 2005-09-10 15:18:16 UTC
Upgraded system (Giga-byte Technology GA-7VAX Mainboard) from 9.3 to 10.0 RC 1.
After initial boot, when X started the LCD monitor (ViewSonic XV900) gave a "No
Signal" indication. Restarted upgrade in Text mode and upgrade completed. When
entering runlevel 5, monitor again reported "No Signal". Attempting to switch to
console 1 (ctrl-alt-f1) froze system (at least it stopped responding to ping).

Installed xorg-x11-server-6.8.2-30 (and xorg-x11-server-glx-6.8.2-30) from 9.3
and X worked as expected.

hwinfo output:
21: PCI(AGP) 100.0: 0300 VGA compatible controller (VGA)
  [Created at pci.277]
  UDI: /org/freedesktop/Hal/devices/pci_1106_7205
  Unique ID: VCu0.q7rHBloBfx9
  Parent ID: vSkL.S16qDHSKEeD
  SysFS ID: /devices/pci0000:00/0000:00:01.0/0000:01:00.0
  SysFS BusID: 0000:01:00.0
  Hardware Class: graphics card
  Model: "VIA KM400"
  Vendor: pci 0x1106 "VIA Technologies, Inc."
  Device: pci 0x7205 "KM400"
  SubVendor: pci 0x1106 "VIA Technologies, Inc."
  SubDevice: pci 0x7205
  Revision: 0x01
  Memory Range: 0xd8000000-0xdbffffff (rw,prefetchable)
  Memory Range: 0xdc000000-0xdcffffff (rw,non-prefetchable)
  Memory Range: 0xdd000000-0xdd00ffff (ro,prefetchable,disabled)
  IRQ: 10 (78768 events)
  I/O Ports: 0x3c0-0x3df (rw)
  Module Alias: "pci:v00001106d00007205sv00001106sd00007205bc03sc00i00"
  Driver Info #0:
    XFree86 v4 Server Module: via
    Extensions: dri
  Config Status: cfg=yes, avail=yes, need=yes, active=unknown
  Attached to: #11 (PCI bridge)

Primary display adapter: #21
Comment 1 Tom Eastep 2005-09-10 15:19:54 UTC
Created attachment 49516 [details]
Xorg.0.log
Comment 2 Tom Eastep 2005-09-10 15:20:47 UTC
Created attachment 49517 [details]
xorg.conf
Comment 3 Stefan Dirsch 2005-09-10 15:50:33 UTC
Try adding 'Load "dri"' to Modules section of xorg.conf to prevent Xserver 
from crashing during mode switch (default for a new X configuration) and 
remove 'UseModes "Modes[0]"' to get standard VESA modelines. 
Comment 4 Tom Eastep 2005-09-10 18:45:06 UTC
The two recommended changes to xorg.conf corrected the problem.

Thanks
Comment 5 Stefan Dirsch 2005-09-10 21:55:24 UTC
Could you please attach the new logfile? Thanks. 
Comment 6 Tom Eastep 2005-09-10 22:09:21 UTC
Created attachment 49529 [details]
Xorg.0.log after xorg.conf changes
Comment 7 Tom Eastep 2005-09-10 22:39:53 UTC
I've also noticed that at some point after the upgrade, I have lost the ability
to switch to the text-mode consoles via ctrl-alt-Fn.
Comment 8 Stefan Dirsch 2005-09-11 07:40:19 UTC
>  I've also noticed that at some point after the upgrade, I have lost the    
> ability to switch to the text-mode consoles via ctrl-alt-Fn.   
  
[...]   
(EE) Couldn't load XKB keymap, falling back to pre-XKB keymap    
[...]   
  
That's the reason. From which SUSE version did you update exactly? 
Comment 9 Stefan Dirsch 2005-09-11 07:40:49 UTC
>  I've also noticed that at some point after the upgrade, I have lost the    
> ability to switch to the text-mode consoles via ctrl-alt-Fn.   
  
[...]   
(EE) Couldn't load XKB keymap, falling back to pre-XKB keymap    
[...]   
  
That's the reason. From which SUSE version did you update exactly? 
Comment 10 Stefan Dirsch 2005-09-11 10:13:16 UTC
Need to check an update from 9.3 --> 10.0 RC1 
Comment 11 Tom Eastep 2005-09-11 14:43:07 UTC
I suspect that the XKB keymap problem is fallout from the RPM shuffling that
I've done after the upgrade rather than from the upgrade itself. Recall in my
initial report that immediately after the upgrade, ctrl-alt-F1 would apparently
freeze the system. 
Comment 12 Stefan Dirsch 2005-09-11 14:46:43 UTC
Thanks for the hint. Anyway, it's good to verify this since there has been
problems in the past.
Comment 13 Stefan Dirsch 2005-09-11 15:03:55 UTC
Since 'Load "dri"' will be default on 10.0 and I can't reproduce the xkb problem
(see also comment #11) I close this as FIXED now.