[Bug 248775] New: X server hangs on Toshiba Portege R100
https://bugzilla.novell.com/show_bug.cgi?id=248775 Summary: X server hangs on Toshiba Portege R100 Product: openSUSE 10.2 Version: Final Platform: i686 URL: http://www.cl.cam.ac.uk/~mgk25/suse-10.2/ OS/Version: Other Status: NEW Severity: Major Priority: P5 - None Component: X.Org AssignedTo: sndirsch@novell.com ReportedBy: Markus.Kuhn@cl.cam.ac.uk QAContact: sndirsch@novell.com I'm trying to use openSUSE on a laptop Toshiba Portege R100. [Graphics chip: Trident CYBER 2100 [Rev: RXT 7.3 (16.29)], 32 MB (Recognized by X as Trident Trident CyberbladeXP4). BIOS version: 1.50 (11/25/2004)] When the X server (with vesa driver) starts, - the screen goes black (backlight remains on) - the X process starts to utilize 99.9% of the CPU $ top PID USER PR NI VIRT RES SHR S %CPU %MEM TIME+ COMMAND 5041 root 25 0 40612 2500 1916 R 99.9 0.3 15:07.45 X - The X server does not react to Alt-Ctrl-Backspace, Alt-Ctrl-F1, SIGINT, SIGHUP. - After killing the X server (via ssh) with SIGABRT, the screen remains black until I press Alt-Ctrl-F1 to get back to my virtual console. The relevant log and config files are at http://www.cl.cam.ac.uk/~mgk25/suse-10.2/Xorg.0.log http://www.cl.cam.ac.uk/~mgk25/suse-10.2/xorg.conf This happens both when booting from the installation disk, as well as on the installed system (which was upgraded from SUSE 10.1, which had no such problem). This also happens when I start the X server manually with "startx" after booting in safe mode. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug, or are watching someone who is.
https://bugzilla.novell.com/show_bug.cgi?id=248775 sndirsch@novell.com changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |ASSIGNED ------- Comment #1 from sndirsch@novell.com 2007-02-26 03:01 MST ------- Thanks for giving openSUSE 10.2 a try. I'll the files for my convenience. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug, or are watching someone who is.
https://bugzilla.novell.com/show_bug.cgi?id=248775 ------- Comment #2 from sndirsch@novell.com 2007-02-26 03:02 MST ------- Created an attachment (id=120987) --> (https://bugzilla.novell.com/attachment.cgi?id=120987&action=view) xorg.conf -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug, or are watching someone who is.
https://bugzilla.novell.com/show_bug.cgi?id=248775 ------- Comment #3 from sndirsch@novell.com 2007-02-26 03:02 MST ------- Created an attachment (id=120988) --> (https://bugzilla.novell.com/attachment.cgi?id=120988&action=view) Xorg.0.log -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug, or are watching someone who is.
https://bugzilla.novell.com/show_bug.cgi?id=248775 ------- Comment #4 from sndirsch@novell.com 2007-02-26 03:09 MST ------- Created an attachment (id=120990) --> (https://bugzilla.novell.com/attachment.cgi?id=120990&action=view) vesa_drv.so Could you give the latest vesa driver a try? Copy it to /usr/lib/xorg/modules/drivers. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug, or are watching someone who is.
https://bugzilla.novell.com/show_bug.cgi?id=248775 sndirsch@novell.com changed: What |Removed |Added ---------------------------------------------------------------------------- Status|ASSIGNED |NEEDINFO Info Provider| |Markus.Kuhn@cl.cam.ac.uk ------- Comment #5 from sndirsch@novell.com 2007-02-26 03:18 MST ------- Also I wonder, why we don't configure the trident driver (any longer?) for this GPU. So could you also give the trident driver a try? Use sax2 -r -m 0=trident for configuration. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug, or are watching someone who is.
https://bugzilla.novell.com/show_bug.cgi?id=248775 Markus.Kuhn@cl.cam.ac.uk changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEEDINFO |ASSIGNED Info Provider|Markus.Kuhn@cl.cam.ac.uk | ------- Comment #6 from Markus.Kuhn@cl.cam.ac.uk 2007-02-26 03:46 MST ------- Trying the replacement vesa_drv.so from #4: $ startx [...] (II) LoadModule: "vesa" (II) Loading /usr/lib/xorg/modules/drivers//vesa_drv.so (II) Module vesa: vendor="X.Org Foundation" compiled for 7.2.0, module version = 1.3.0 Module class: X.Org Video Driver ABI class: X.Org Video Driver, version 1.1 (EE) module ABI minor version (1) is newer than the server's version (0) (II) UnloadModule: "vesa" (II) Unloading /usr/lib/xorg/modules/drivers//vesa_drv.so (EE) Failed to load module "vesa" (module requirement mismatch, 0) [...] (EE) No devices detected. $ startx -- -ignoreABI [same symptoms as before] Trying trident driver next. The reason I used the vesa driver instead of the trident one was that under SUSE 9.3 and 10.1, the external VGA output was garbled when I used the trident driver. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug, or are watching someone who is.
https://bugzilla.novell.com/show_bug.cgi?id=248775 ------- Comment #7 from Markus.Kuhn@cl.cam.ac.uk 2007-02-26 04:03 MST ------- Re #4: The trident driver does work, but as under SUSE 9.3/10.1, the external VGA output is garbled with it. So the trident driver is only a workaround until I have to give my next lecture from this laptop ... Any idea what might possibly have changed in the vesa driver between 10.1 and 10.2 that could cause this? -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug, or are watching someone who is.
https://bugzilla.novell.com/show_bug.cgi?id=248775 ------- Comment #8 from sndirsch@novell.com 2007-02-26 05:09 MST ------- I think the issue is related to a change in the Xserver and not to any vesa driver change. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug, or are watching someone who is.
https://bugzilla.novell.com/show_bug.cgi?id=248775 ------- Comment #9 from Markus.Kuhn@cl.cam.ac.uk 2007-02-26 06:16 MST ------- Any suggestions for options that would be particularly worth experimenting with? What changed parts of the Xserver could the vesa driver use that the trident driver doesn't? -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug, or are watching someone who is.
https://bugzilla.novell.com/show_bug.cgi?id=248775 sndirsch@novell.com changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |mhopf@novell.com, eich@novell.com Status|ASSIGNED |NEEDINFO Info Provider| |Markus.Kuhn@cl.cam.ac.uk ------- Comment #10 from sndirsch@novell.com 2007-02-26 06:26 MST ------- Just a wild guess. Try exclusively: Option "InitPrimary" "on" Option "NoInt10" "on" Option "NoMTRR" "on" see also xorg.conf. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug, or are watching someone who is.
https://bugzilla.novell.com/show_bug.cgi?id=248775 ------- Comment #11 from mhopf@novell.com 2007-02-26 10:40 MST ------- Markus, you probably won't get *any* output on the external VGA with the vesa driver (except maybe if booted with a monitor attached, depends on the BIOS). But that is just an educated guess. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug, or are watching someone who is.
https://bugzilla.novell.com/show_bug.cgi?id=248775 Markus.Kuhn@cl.cam.ac.uk changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEEDINFO |ASSIGNED Info Provider|Markus.Kuhn@cl.cam.ac.uk | ------- Comment #12 from Markus.Kuhn@cl.cam.ac.uk 2007-02-27 02:18 MST ------- Re #10: I tried all three options individually with the vesa_drv.so, but none provided any improvement:
Option "InitPrimary" "on"
This one causes the backlight to go off, otherwise symptoms remain the same (i.e., X process hangs at full CPU load). The log file ends with: (II) Loading sub module "int10" (II) LoadModule: "int10" (II) Reloading /usr/lib/xorg/modules//libint10.so (II) VESA(0): initializing int10 (**) VESA(0): Option "InitPrimary" "on" (II) Attempted to read BIOS 256KB from /sys/bus/pci/devices/0000:01:00.0/rom: go t 48KB (II) VESA(0): VESA BIOS detected (II) VESA(0): VESA VBE Version 2.0 (II) VESA(0): VESA VBE Total Mem: 32768 kB (II) VESA(0): VESA VBE OEM: Trident CYBER 2100 (II) VESA(0): VESA VBE OEM Software Rev: 2.0 (II) VESA(0): VESA VBE OEM Vendor: TRIDENT MICROSYSTEMS INC. (II) VESA(0): VESA VBE OEM Product: CYBER 2100 (II) VESA(0): VESA VBE OEM Product Rev: RXT 7.3 (16.28) (II) VESA(0): Splitting WC range: base: 0xffffffff, size: 0x2000000
Option "NoInt10" "on"
The server aborts with this log and error message: (II) Loading sub module "int10" (II) LoadModule: "int10" (II) Reloading /usr/lib/xorg/modules//libint10.so (II) VESA(0): initializing int10 (**) VESA(0): Option "NoINT10" "on" Fatal server error: AddScreen/ScreenInit failed for driver 0 This one causes the backlight to go off, otherwise symptoms remain the same.
Option "NoMTRR" "on"
This one causes a reboot. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug, or are watching someone who is.
https://bugzilla.novell.com/show_bug.cgi?id=248775 sndirsch@novell.com changed: What |Removed |Added ---------------------------------------------------------------------------- Status|ASSIGNED |NEEDINFO Info Provider| |Markus.Kuhn@cl.cam.ac.uk ------- Comment #13 from sndirsch@novell.com 2007-02-27 02:25 MST ------- Ouch. Does the Trident chip already support framebuffer ("vga=0x317" kernel boot option), so you can give the fbdev driver a try (use "sax2 -r -m 0=fbdev" for configuration)? -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug, or are watching someone who is.
https://bugzilla.novell.com/show_bug.cgi?id=248775 ------- Comment #14 from Markus.Kuhn@cl.cam.ac.uk 2007-02-27 02:29 MST ------- Re: #11 External VGA output worked very nicely with the vesa driver under SUSE 9.3/10.1; I could simply activate it via the Toshiba BIOS hotkey Fn+F5 while the X server was already running. (BTW: Doing the same with the trident driver causes a quarter of the screen content to be repeated horizontally three times, thereby half of the screen content becoming invisible: http://lists.freedesktop.org/archives/xorg/2005-November/011289.html ) -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug, or are watching someone who is.
https://bugzilla.novell.com/show_bug.cgi?id=248775 Markus.Kuhn@cl.cam.ac.uk changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEEDINFO |ASSIGNED Info Provider|Markus.Kuhn@cl.cam.ac.uk | ------- Comment #15 from Markus.Kuhn@cl.cam.ac.uk 2007-02-27 03:00 MST ------- Re: #13 I've now booted with kernel option vga=0x317 and then tried the fbdev driver. Everything seems to work nicely, including the external VGA output with Fn+F5. This looks like a usable workaround for the moment! However, my first impression is that the performance is less than what it was with the vesa driver; moving windows around has now a very unaccelerated early-1990s feel to it ... -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug, or are watching someone who is.
https://bugzilla.novell.com/show_bug.cgi?id=248775 sndirsch@novell.com changed: What |Removed |Added ---------------------------------------------------------------------------- Severity|Major |Normal ------- Comment #16 from sndirsch@novell.com 2007-02-27 03:22 MST ------- Ok. I think this is no longer major with this workaround. You might get better performance results using the tridentfb kernel module, but I honestly must say that I don't have experience with the any native framebuffer modules at all. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug, or are watching someone who is.
https://bugzilla.novell.com/show_bug.cgi?id=248775 ------- Comment #17 from Markus.Kuhn@cl.cam.ac.uk 2007-02-27 03:30 MST ------- Thanks for your very quick help and the useful workaround! (While I'm quite happy now, the vesa issue will of course continue to annoy owners of this laptop during installation of or update to 10.2; I had to switch to ssh-based installation to get it done.) -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug, or are watching someone who is.
https://bugzilla.novell.com/show_bug.cgi?id=248775 sndirsch@novell.com changed: What |Removed |Added ---------------------------------------------------------------------------- Summary|X server hangs on Toshiba |vesa: X server hangs on Toshiba Portege R100 |Portege R100 | -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug, or are watching someone who is.
https://bugzilla.novell.com/show_bug.cgi?id=248775 eich@novell.com changed: What |Removed |Added ---------------------------------------------------------------------------- AssignedTo|sndirsch@novell.com |eich@novell.com ------- Comment #18 from eich@novell.com 2007-05-14 13:15 MST ------- I'll take this one. I've got a similar portege here and can see a similar problem. We have several bugs releated to the VESA driver. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug, or are watching someone who is.
https://bugzilla.novell.com/show_bug.cgi?id=248775
Stefan Dirsch
https://bugzilla.novell.com/show_bug.cgi?id=248775#c19
--- Comment #19 from Markus Kuhn
https://bugzilla.novell.com/show_bug.cgi?id=248775
User eich@novell.com added comment
https://bugzilla.novell.com/show_bug.cgi?id=248775#c20
Egbert Eich
participants (1)
-
bugzilla_noreply＠novell.com