Mailinglist Archive: opensuse (888 mails)
|< Previous||Next >|
Re: [opensuse] OpenSUSE 11.3 hangs with Firefox or Google Chrome running.
- From: dwgallien <dwgallien@xxxxxxxxx>
- Date: Thu, 27 Jan 2011 10:49:41 -0500
- Message-id: <email@example.com>
Hi,There are two open source drivers for ATI cards. The first is radeon, which is
I am running this on an IBM T42 laptop. This is not an kind of virtual box.
The video driver is just what the install tool picked out.
I don't think this is the right information from lsmod, it does not specify
what the driver is.
samhaber-nb:/var # lsmod | grep vid
video 21141 0
output 2031 1 video
thermal_sys 14735 4 video,fan,processor,thermal
Would it help to know what driver is from my SUSE 10.1 installation. Some of
those files might still be valid if someone can tell me where to look.
included with the kernel. The second is radeonhd, which is in the package
xorg-x11-driver-video-radeonhd but I suspect this is for newer chipsets than
you have. (It wouldn't hurt to install it anyway.)
Do an lsmod without the qualifier, check for fbdev or vesa or vesafb. If you
are getting a graphical display, there is some graphics driver running.
In your log I would ignore the vboxvideo error. X now does automatic graphics
device detection and driver selection. I haven't seen many of the new logs
yet, but it is conceivable that X works through a list checking for the
presence of possible driver candidates. vboxvideo is the driver used in a
virtualbox guest, so in any case this obviously doesn't apply to you.
The errors and info remarks in the log suggest to me that X couldn't find a
driver and so it fell back to vesafb. While vesa is the actual X vesa driver,
vesafb is the framebuffer driver compiled into the kernel; that's what enables
the graphical splash. When run level 5 is reached and control of the display
passes to X, it selects its own driver. If you don't find an X graphics driver
being loaded, my speculation is that X is falling back to the kernel's. That
would explain your getting some graphics but having problems, because the
framebuffer is very limited.
Recommendation: X still provides for the user to manually control the driver
it uses. When the automatic change was first introduced, manual control was
done through the traditional xorg.conf file, i.e., if that file was still
present, it would be used. I finally remembered, the method was changed again:
Look in the /etc/X11/xorg.conf.d directory. There you will find config files
each of which corresponds to a section of the old xorg.conf file. Look at
50-device-conf. This file corresponds to the old "device" section, and is
where the graphics driver can be specified. I noticed that there is even a
remark in the file specific to the radeon driver. so here may be your problem
and solution. Remove the comment # on the - Driver "radeon" - line, and
restart the machine. Hopefully you'll get a gui and lsmod will show radeon
Then take a look at the X log to determine what timings and resolution X chose.
The timings are very important on laptops, particularly some older ones. If
you need to set the timings manually, that's done in the file 50-monitor-conf.
If you need to force the correct resolution too, that can be done in the file
Finally, there is also the ATI proprietary driver option. It's been too long
since I've used that driver (worked fine with my RV350 card, btw), and there
have been a lot of issues on and off with it over the years. If radeon or
radeonhd don't work for you (and/or, if you want compositing, I don't think the
open source drivers support that) I'd point you to the wiki and maybe the
Forums for the most current info. The Forums deal with graphics driver issues
all the time, so it's a good resource.
To unsubscribe, e-mail: opensuse+unsubscribe@xxxxxxxxxxxx
For additional commands, e-mail: opensuse+help@xxxxxxxxxxxx
|< Previous||Next >|