Xorg hangs on exit

[gpatrick]

Using OpenBSD 4.6 on a Toshiba satellite L505D-S5983 laptop. At first when I tried to start X it would give me a black screen and the entire machine would freeze. Only a hard reset would work. It uses the radeonhd driver and ATI card.

I tried (using all combinations):
Option "DRI" "True"
Option "UseAtomBIOS" "True"
Option "AtomBIOS" "pll=on"

Found one forum where someone had the exact problem and solved it using the option "UseAtomBIOS" but that doesn't work for me.

Only when I switched the driver to vesa does X start and I have a working display. The only problem is when I try to exit, it closes all apps and then hangs. Nothing in the log file indicating a problem when using the vesa driver at exit. Nothing in the log file at all when using the radeonhd driver.

My /etc/X11/xorg.conf:
Section "ServerLayout"
Identifier "X.org Configured"
Screen 0 "Screen0" 0 0
InputDevice "Mouse0" "CorePointer"
InputDevice "Keyboard0" "CoreKeyboard"
EndSection

Section "Files"
ModulePath "/usr/X11R6/lib/modules"
FontPath "/usr/X11R6/lib/X11/fonts/misc/"
FontPath "/usr/X11R6/lib/X11/fonts/TTF/"
FontPath "/usr/X11R6/lib/X11/fonts/OTF"
FontPath "/usr/X11R6/lib/X11/fonts/Type1/"
FontPath "/usr/X11R6/lib/X11/fonts/100dpi/"
FontPath "/usr/X11R6/lib/X11/fonts/75dpi/"
EndSection

Section "Module"
Load "dbe"
Load "dri"
Load "extmod"
Load "glx"
Load "freetype"
EndSection

Section "InputDevice"
Identifier "Keyboard0"
Driver "kbd"
EndSection

Section "InputDevice"
Identifier "Mouse0"
Driver "mouse"
Option "Protocol" "wsmouse"
Option "Device" "/dev/wsmouse"
Option "ZAxisMapping" "4 5 6 7"
EndSection

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

Section "Device"
### Available Driver options are:-
### Values: <i>: integer, <f>: float, <bool>: "True"/"False",
### <string>: "String", <freq>: "<f> Hz/kHz/MHz"
### [arg]: arg optional
#Option "NoAccel" # [<bool>]
#Option "AccelMethod" # [<str>]
#Option "offscreensize" # [<str>]
#Option "SWcursor" # [<bool>]
#Option "ignoreconnector" # [<str>]
#Option "forcereduced" # [<bool>]
#Option "forcedpi" # <i>
#Option "useconfiguredmonitor" # [<bool>]
#Option "HPD" # <str>
#Option "NoRandr" # [<bool>]
#Option "RROutputOrder" # [<str>]
#Option "DRI" # [<bool>]
#Option "TVMode" # [<str>]
#Option "ScaleType" # [<str>]
#Option "UseAtomBIOS" # [<bool>]
#Option "AtomBIOS" # [<str>]
#Option "UnverifiedFeatures" # [<bool>]
#Option "Audio" # [<bool>]
#Option "HDMI" # [<str>]
#Option "COHERENT" # [<str>]
Identifier "Card0"
#Driver "radeonhd"
Driver "vesa"
VendorName "ATI"
BoardName "Unknown Board"
BusID "PCI:1:5: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

[Beastie]

I don't know if the radeonhd driver supports the NoAccel option. Try Option "NoAccel" "TRUE" (with Driver "radeonhd" instead of VESA).

I have an integrated Intel card and Xorg used to hang randomly at startup. Of course after enabling NoAccel, a lot of things are slower, but at least it doesn't hang anymore.

[gpatrick]

Thanks for the suggestion but X still sits on a blank screen and the entire machine is frozen. Using the vesa driver, X starts but it hangs on logout; when shutdown is selected in X, that works and the machine powers off with the vesa driver.

[BSDfan666]

The radeon/ati(4) driver may support this device, consider trying Driver "radeon".. it may be a simple case of the shipped drivers not having the product ID for your card yet.

Google would indicate it's the ATI® Radeon™ 4100 (RS880/0x9711), what does dmesg/pcidump show for vga1?

OpenBSD 4.6 shipped with xf86-video-ati version 6.9.0, this version of the driver only supported the ATI® Radeon™ 3100 (RS780/0x9613).

A common trick is to pick a (..similar) supported models product ID, forcing ChipID 0x9613 may allow at least accelerated 2D to work, which is what you want.. right?

The unsupported alternative is to compiler a newer version of the radeon/radeonhd drivers.. but they would rather have you install the latest snapshot.

[gpatrick]

Using the radeon driver results in "no screens found".

# dmesg | grep vga
vga1 at pci1 dev 5 function 0 vendor "ATI", unknown product 0x9712 rev 0x00
wsdisplay0 at vga1 mux1: console (80x25, vt100 emulation)

I have two identical Toshiba Satellite L505D-S5983 laptops and one is running FreeBSD 8.0 RC3 and it displays fine. Also using the xfce4 window manager in both FreeBSD and OpenBSD. In FreeBSD under display in xfce I have multiple resolutions and can change the refresh rate; with xfce in OpenBSD I only have a 1024x768 resolution and the refresh rate says 0 and no other options.

[BSDfan666]

You didn't read all of my post, but I told you that OpenBSD 4.6 (..tagged in July) does not include implicit support for your NEWER graphics card.

I indicated how it might be possible to force things, by pretending to have an earlier model.. but you seemingly ignored me.

A refresh rate of '0' is impossible, it is a placeholder that's used by the vesa driver.. which is a standardized software framebuffer interface provided by a video card (..very unsophisticated).

You have what you need, now you can decide.. here's a start.
1) Be content with the VESA framebuffer.
2) Force a different (..older) ChipID for the radeon driver.
3) Install a snapshot release, which has a newer version of xf86-video-ati.
4) Manually compile a newer version of said driver, entirely unsupported.
5) Use FreeBSD instead.

[gpatrick]

Installed the latest snapshot and it's working.

Thank you!!!

[ocicat]

Originally Posted by gpatrick

Installed the latest snapshot and it's working.

While you have a reason to be running -current, recognize that you have also implicitly accepted the responsibility which comes with running development code. To fully understand the implications, study Section 5.1 of the FAQ:

http://openbsd.org/faq/faq5.html#Flavors