| Summary: | The low VideoRam problem with no accelation method in use | ||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|
| Product: | xorg | Reporter: | xuji <ji.xu> | ||||||||
| Component: | Driver/intel | Assignee: | Wang Zhenyu <zhenyu.z.wang> | ||||||||
| Status: | VERIFIED FIXED | QA Contact: | Xorg Project Team <xorg-team> | ||||||||
| Severity: | major | ||||||||||
| Priority: | high | CC: | eric, gordon.jin, nian.wu | ||||||||
| Version: | git | ||||||||||
| Hardware: | x86 (IA32) | ||||||||||
| OS: | Linux (All) | ||||||||||
| Whiteboard: | |||||||||||
| i915 platform: | i915 features: | ||||||||||
| Bug Depends on: | |||||||||||
| Bug Blocks: | 10102 | ||||||||||
| Attachments: |
|
||||||||||
Created attachment 8614 [details]
xorg.conf
Created attachment 8615 [details]
xorg.log
You may set VideoRam in your xorg.conf for no accel or other accel method. Current code seems failed to detect what should be the apropriate mem size, I'll take a look, you may use VideoRam for now. As I said above, if I assigned VideoRam with a value 131072 or so then X can be started with DRI disabled >>Moreover, if the VideoRam is set, X can start but DRI is disabled: >>(EE) AIGLX: Screen 0 is not DRI capable Then you should attach the failure log in that case. It might doesn't load your dri driver correctly, maybe an install or config issue. Created attachment 8620 [details]
xorg.log after setting VideoRam
Please try with the current modesetting branch and no VideoRam setting. with the current modesetting 2D driver, the problem remains the same. Sorry about the phenomenal bug spam, guys. Adding xorg-team@ to the QA contact so bugs don't get lost in future. Now the issue has some changes: With the NoAccel option enabled, starting X will fail with following backtrace: Backtrace: 0: X(xf86SigHandler+0x81) [0x80b3dd1] 1: [0xb7f24420] 2: X(AddScreen+0x1ee) [0x806f49e] 3: X(InitOutput+0x21e) [0x80a0b2e] 4: X(main+0x27b) [0x806fc3b] 5: /lib/libc.so.6(__libc_start_main+0xdc) [0x9eb7e4] 6: X(FontFileCompleteXLFD+0xa9) [0x806f181] Fatal server error: Caught signal 11. Server aborting Setting the VideoRam value renders the same result. Fix pushed. |
Use of freedesktop.org services, including Bugzilla, is subject to our Code of Conduct. How we collect and use information is described in our Privacy Policy.
--Architecture(ia32,ia32e): ia32 & ia32e --Xf86_video_intel modesetting(785a59ead0e8d1d681b2cb6827ee58ad2c51f8c6) --Mesa: master(8518ddda7b5f8e43de4859042fe59f55aa0c2760) --Xserver: server-1.2-branch(4e6872fca75b77c342a7e1e715b1c30dc2642a73) --OS: FC5 Description: ======================= If no accelation method is implemented, X can not start with following info: (EE) intel(0): Failed to allocate framebuffer. Is your VideoRAM set too low? Fatal server error: AddScreen/ScreenInit failed for driver 0 Moreover, if the VideoRam is set, X can start but DRI is disabled: (EE) AIGLX: Screen 0 is not DRI capable Reproduce step: ======================= Revise xorg.conf to: # Option "AccelMethod" "exa" Option "NoAccel" "TRUE" then start X Expected result: ======================= X can start.