Bug 465199
Summary: | Fedora 10 Beta blocks in GDM on HP mini 2133 | ||||||
---|---|---|---|---|---|---|---|
Product: | [Fedora] Fedora | Reporter: | William Lovaton <walovaton> | ||||
Component: | xorg-x11-drv-openchrome | Assignee: | Xavier Bachelot <xavier> | ||||
Status: | CLOSED DUPLICATE | QA Contact: | Fedora Extras Quality Assurance <extras-qa> | ||||
Severity: | high | Docs Contact: | |||||
Priority: | medium | ||||||
Version: | 10 | CC: | linuxbenutzer, mcepl, xavier, xgl-maint | ||||
Target Milestone: | --- | ||||||
Target Release: | --- | ||||||
Hardware: | All | ||||||
OS: | Linux | ||||||
Whiteboard: | |||||||
Fixed In Version: | Doc Type: | Bug Fix | |||||
Doc Text: | Story Points: | --- | |||||
Clone Of: | Environment: | ||||||
Last Closed: | 2008-12-29 20:55:23 UTC | Type: | --- | ||||
Regression: | --- | Mount Type: | --- | ||||
Documentation: | --- | CRM: | |||||
Verified Versions: | Category: | --- | |||||
oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |||||
Cloudforms Team: | --- | Target Upstream Version: | |||||
Embargoed: | |||||||
Attachments: |
|
Description
William Lovaton
2008-10-02 03:40:37 UTC
Thanks for the bug report. We have reviewed the information you have provided above, and there is some additional information we require that will be helpful in our diagnosis of this issue. Please attach your X server config file (/etc/X11/xorg.conf) and X server log file (/var/log/Xorg.*.log) to the bug report as individual uncompressed file attachments using the bugzilla file attachment link below. We will review this issue again once you've had a chance to attach this information. Thanks in advance. The X server config file doesn't exists in Fedora, remember that in my original post the X server said this: (==) Using default built-in configuration (30 lines) I had to change inittab to runlevel 3 to use the mini-note reliably. When I start X I now get more messages in the output: New driver is "openchrome" (==) Using default built-in configuration (30 lines) (EE) open /dev/fb0: No such file or directory (EE) [drm] drmOpen failed. (EE) CHROME(0): [dri] DRIScreenInit failed. Disabling DRI. Freed 9834496 (pool 1) expected keysym, got XF86Info: line 914 of inet expected keysym, got XF86Info: line 914 of inet The XKEYBOARD keymap compiler (xkbcomp) reports: > Warning: Type "ONE_LEVEL" has 1 levels, but <RALT> has 2 symbols > Ignoring extra symbols Errors from xkbcomp are not fatal to the X server expected keysym, got XF86Info: line 914 of inet The XKEYBOARD keymap compiler (xkbcomp) reports: > Warning: Type "ONE_LEVEL" has 1 levels, but <RALT> has 2 symbols > Ignoring extra symbols Errors from xkbcomp are not fatal to the X server I'll attach the X server log later. Created attachment 319246 [details]
X server log from the HP 2133 mini-note
Oddly enough, if I start two X apps it blocks completely, I have to force a shutdown.
I started xclock and it starts "fine" (distorted), I can go to the X server and back to the text console. I then started xload, go to the X server and it blocks completely, I can't go back to the text console.
There are a couple configuration options I'd like you to try. Does disabling this particular bit of XAA help ? Option "XaaNoImageWriteRect" If it still doesn't work with the above option, does switching to EXA acceleration help (remove the above option) ? Option "AccelMethod" "EXA" If it's still not good with with only EXA, does disabling EXA composite help ? Option "AccelMethod" "EXA" Option "ExaNoComposite" (In reply to comment #4) I tested all the variants you posted and all of them worked fine except for the mouse pointer which still is a big distorted square. The tip of the pointer is the upper left corner so I can move around and use the desktop. Later on I'll try to post a picture of the screen. What can be done about the mouse pointer? About the mouse pointer, try to switch to software cursor : Option "SWCursor" I'll see about disabling ARGB hardware cursor in a later build, but I'd like upstream to comment on that first, there's likely a more generic issue. Unfortunately I don't have the hardware anymore, it was borrowed by HP and I returned it a few days ago. But still every single fix you said here in this bug report worked perfectly. It's just a matter of getting it to auto detect the right setup so that regular users have a working system out of the box. Thanks a lot for your help. This bug appears to have been reported against 'rawhide' during the Fedora 10 development cycle. Changing version to '10'. More information and reason for this action is here: http://fedoraproject.org/wiki/BugZappers/HouseKeeping *** This bug has been marked as a duplicate of bug 446489 *** |