SlackwareThis Forum is for the discussion of Slackware Linux.
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
or both are set in the Device section of xorg.conf
I have done a reboot and it still does this.
My xorg.conf follows:
Quote:
#X11 xorg.conf for Toshiba M100
Section "Files"
# FontPath "unix/:7100" # local font server
# if the local font server has problems, we can fall back on these
FontPath "/usr/lib/X11/fonts/misc"
FontPath "/usr/lib/X11/fonts/cyrillic"
FontPath "/usr/lib/X11/fonts/100dpi/:unscaled"
FontPath "/usr/lib/X11/fonts/75dpi/:unscaled"
FontPath "/usr/lib/X11/fonts/Type1"
# FontPath "/usr/lib/X11/fonts/CID"
# FontPath "/usr/lib/X11/fonts/Speedo"
FontPath "/usr/lib/X11/fonts/100dpi"
FontPath "/usr/lib/X11/fonts/75dpi"
EndSection
Just in case anybody stumbles about the same problem:
This is problem with the ring buffer not being flushed (whatever that might be).XFree 4.3.0 didn't work so well and with XFree 4.3.99 it seems to be fixed.
Now how do you fix that ... lemme search around a bit.
Above is my report. Further experimenting shows that disabling *all* power management seems to prevent this from happening but obviously disabling acpi entirely is not a viable solution.
Dunno if that will work, but it is a viable solution in most cases. Search google for 'Error in I830WaitLpRing()', it seems to be a prevalent error.
Last edited by H_TeXMeX_H; 01-27-2007 at 03:10 PM.
Start with your '/etc/X11/xorg.conf-vesa', copy it to xorg.conf, and then change only the minimum required to get dri working. (this is because I suspect your current xorg.conf is poorly configure and cannot be easily fixed)
One more idea which just came to me after looking at all that output and thinking about it for a while
Seems like it's a problem with the framebuffer
Code:
intelfb: Initial info: FB is 0xd8000000/0xfd0000 (16192 kByte)
intelfb: Initial info: mode is 1024x768-16 (2048)
intelfb: update_dinfo
intelfb: intelfb_var_to_depth: bpp: 16, green.length is 6
intelfb: intelfb_set_fbinfo
intelfb: intelfb_init_var
intelfb: Initial video mode is 1024x768-16@60.
intelfb: Initial video mode is from 5.
intelfb: update_dinfo
intelfb: intelfb_var_to_depth: bpp: 16, green.length is 6
intelfb: intelfbhw_print_hw_state
...
intelfb: Changing the video mode is not supported.
intelfb: ring buffer : space: 65400 wanted 65472
intelfb: lockup - turning off hardware acceleration
2 things to notice:
In blue is the initial mode for framebuffer.
In red is the ring buffer reporting that it wanted 65472 much space but could only get 65400 causing the lockup right after that which turns off hardware acceleration.
I wonder ... if you change the vga start mode to something less than 1024x768-16 it might not error and hardware accel will remain enabled.
Now, how do you do that ... I think it is set in /etc/lilo.conf, so go there and change:
Code:
vga = ###
where ### is some number such as 773 (for me), to:
Code:
vga = normal
Then run:
Code:
/sbin/lilo
as root to apply changes. And try rebooting.
Last edited by H_TeXMeX_H; 01-27-2007 at 06:14 PM.
I didn't modify the xorg.conf (but I have changed it a bit - I have edited the new one in my first post).
I put vga=normal in lilo, and now I have no errors and DRI again!
But... the bootup text and following command line (basically anything before X) is at a very small resolution, which is annoying.
How can I make vga=791 work again?
Riddick
First of all, I'm glad to hear it actually worked !
Well, now that we know what the problem is it may be possible to use the framebuffer in lower resolutions if you want. So in /etc/lilo.conf select a resolution that is less than 1024x768x64k or vga=791. Sorry, but I don't think it's possible to get vga=791 to work again. It uses up too much memory which causes the crash, but anything under that should work, I think. I mean the memory was off by just a few bytes or kilobytes (whatever units they are in)
Quote:
intelfb: ring buffer : space: 65400 wanted 65472
that's 72 kilobytes I think.
So:
Code:
# VESA framebuffer console @ 1024x768x32k
# vga=790
# VESA framebuffer console @ 1024x768x256
# vga=773
# VESA framebuffer console @ 800x600x64k
# vga=788
# VESA framebuffer console @ 800x600x32k
# vga=787
# VESA framebuffer console @ 800x600x256
# vga=771
# VESA framebuffer console @ 640x480x64k
# vga=785
# VESA framebuffer console @ 640x480x32k
# vga=784
# VESA framebuffer console @ 640x480x256
# vga=769
choose one of these and see if it still crashes. If it does, then lower the resolution until it doesn't anymore.
Last edited by H_TeXMeX_H; 01-28-2007 at 11:39 AM.
I tried 790 and it said "video mode not supported", but then I went back to 791 and everything is fine - maybe it just needed a change?
Shall we pursue this further?
Thanks for ALL your help H_TeXMeX_H, you've been great!
Riddick
Hmm ... that's strange. Why would that video mode not be supported ? Maybe it has to be ###x###x64k ?
I've heard that most newer video cards and chipsets don't support or deal with the framebuffer very well at all. Maybe that's part of it ? Maybe it's the drivers for the card. I don't quite know.
If you wanted to know which modes work and which don't you could try them all. But, now that you got the mode you want working properly, maybe you shouldn't
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.
