Hi, 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. Thanks, Bruce. On Wednesday 26 January 2011 23:23:50 dwgallien wrote:
Hi Markus,
From lspci
01:00.0 VGA compatible controller: ATI Technologies Inc RV350 [Mobility Radeon 9600 M10]
I get the following messages from /var/log/Xorg.0.log that seem like they might be relevant butnot sure what they mean.
[ 28.443] (EE) Failed to load module "vboxvideo" (module does not exist, 0) [ 29.193] (EE) No input driver/identifier specified (ignoring) [ 29.211] (EE) No input driver/identifier specified (ignoring) [ 29.213] (EE) ioctl EVIOCGNAME failed: Inappropriate ioctl for device [ 29.213] (EE) PreInit returned NULL for "TPPS/2 IBM TrackPoint" [ 29.213] (EE) No input driver/identifier specified (ignoring) [ 281.728] (EE) No input driver/identifier specified (ignoring)
[ 282.896] (EE) No input driver/identifier specified (ignoring) [ 1483.375] (II) FBDEV(0): FBIOBLANK: Invalid argument (Screen blanking not supported by vesafb of Linux Kernel) [ 1483.375] (II) FBDEV(0): FBIOBLANK: Invalid argument (Screen blanking not supported by vesafb of Linux Kernel) [ 1483.379] (II) FBDEV(0): FBIOBLANK: Invalid argument (Screen blanking not supported by vesafb of Linux Kernel) [ 1810.579] (II) FBDEV(0): FBIOBLANK: Invalid argument (Screen blanking not supported by vesafb of Linux Kernel) [ 1810.579] (II) FBDEV(0): FBIOBLANK: Invalid argument (Screen blanking not supported by vesafb of Linux Kernel)
Thank you, Bruce.
On Wednesday 19 January 2011 00:52:22 Markus Koßmann wrote,
What type of information should I collect to find the problem? I would really like to fix this.
Could you tell us more about the hardware (i.e graphics card) ? Are there any hints to the problem in the log files /var/log/Xorg.0.log and/or /var/log/messages ?
Are you running in a VirtualBox virtual machine? It is strange that otherwise you would be getting an error on loading the VirtualBox video driver.
The next error you are getting is a failure to load the fallback vesa framebuffer driver. Possibly for some reason the new automatic driver detection by X is not working for you. In the past I had an RV350 card and it worked fine with both the ATI proprietary driver and radeon open source.
Somebody help me out here: I know that when X was changed to do its automatic on-the-fly configuration, it would first use /etc/X11/xorg.conf if that file still existed. But didn't that get subsequently get changed to a rules file (maybe under modprobe.d)??? I don't remember offhand.
Bruce, when you do an lsmod, what is the video driver that is loaded? You may need to force X to use to right driver. (Unless of course this is VBox, which will be a different problem.)
-- Bruce Samhaber Tel/Fax: 613-724-5987 112 Kenora St. Cell: 613-297-6961 Ottawa, Ontario K1Y 3L1 mailto: bruce.samhaber@samhaber.ca http://www.samhaber.ca -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org