Mailinglist Archive: opensuse (4398 mails)

["Adam Vazquez Kb2jpd Internet Mobile w/ Treo" <adamvaz@xxxxxxxxxxxxx>]

> vesafb: framebuffer at 0xe0000000, mapped to 0xf0080000, using 3750k,
> total 8000k vesafb: mode is 800x600x16, linelength=1600, pages=7
> vesafb: protected mode interface info at 00ff:44f0
> vesafb: scrolling: redraw
> vesafb: Truecolor: size=0:5:6:5, shift=0:11:5:0
> 


Thanks Adam.  I checked with SAX2 and it shows the currently configured
graphic card correctly as an Intel i830.  Meanwhile dmesg shows that my
laptop is using the vesa frame buffer driver.  That makes me ask then,
what is the connection between the SAX configuration and what dmesg
shows?

***Hello again from Adam:

Putting on the Linux guru hat:

dmesg is showing you all the messages that Linux is booting up with. During the bootstrap, Linux uses information that is either setup by you thanks to Yast initial boot or factory boot (which will always use VESAFB) and whatever is on the LILO/GRUB commandline (go into yast, go to boot loader configuration, look at append commandline, see some software switches and you will see something=vesa and that will be the clue for using the VESA framebuffer driver).

Sax2,on the other hand, is the configuration utility for your X windowing system. You wont see jack of the final results  until you reach runlevel 5 and go into X (the grey graphical screen with the x in the middle). You can also startx and play god there too.

Dmesg is for the text console and your hardware info for all runlevels; Sax2 is just for X.

My advice: adjust your window manger so you can run top or the process monitor and run some video. I use mplayer because it runs well and beats the crap out of the machine. Make sure to compile it for your laptop for best speed.

Try one video driver  and then the other driver. Monitor the CPU utilization numbers. More CPU utilization on one is indicative of young, unoptimised video code. 

 >  Maybe there is a URL or other resource someone can point me to
that will further my education about these things. ;-)  John

***You are here, aren't you? Ask away, we are in it for a reason, right?

Adam SuSE 9.3 on a .8 Ghz Celeron Compaq Presario 1200.

I do Linux installs on  laptops. What a hobby.
-- 







-----Original Message-----

From:  John Shane <jslists@xxxxxxxxxxxxx>
Subj:  Re: [SLE] vesafb instead of intelfb?
Date:  Mon Sep 12, 2005 5:12 am
Size:  2K
To:  suse-linux-e@xxxxxxxx

On Sun, 11 Sep 2005 16:30:00 -0400
"Adam Vazquez Kb2jpd Internet Mobile w/ Treo" <adamvaz@xxxxxxxxxxxxx>
wrote:

> Yast is an internal product of SUSE and will probably use the most conservative Working device driver for an properly working installation.
> 
> If you want to change the driver, use SaX2 or Yast and change the driver to one that you will work best.
> 
> The VESA driver works with most everything. That is why it is used. 
> 
> Don't be surprised that with the driver that is assigned for your video card does not work as well as the VESA driver.
> 
> Adam 
> 
> 
> -----Original Message-----
> 
> From:  John Shane <jslists@xxxxxxxxxxxxx>
> Subj:  [SLE] vesafb instead of intelfb?
> Date:  Sun Sep 11, 2005 2:37 pm
> Size:  974 bytes
> To:  suse-linux-e@xxxxxxxx
> 
> After installing Suse 9.3 on my ThinkPad X30 laptop with an Intel graphics
> adapter, I find that dmesg tells me that the 2.6.11.4-20a-default kernel
> is using the vesa frame buffer driver instead of intelfb.  Does 9.3 always
> install the vesa frame buffer instead of an adapter-specific driver?
> Wouldn't the adapter-specific driver be better? Assuming that intelfb
> would be better, how do I make the change?  YAST doesn't seem to know
> about either one.  Any pointers would be appreciated.  John
> 
> 
> vesafb: framebuffer at 0xe0000000, mapped to 0xf0080000, using 3750k,
> total 8000k vesafb: mode is 800x600x16, linelength=1600, pages=7
> vesafb: protected mode interface info at 00ff:44f0
> vesafb: scrolling: redraw
> vesafb: Truecolor: size=0:5:6:5, shift=0:11:5:0
> 


Thanks Adam.  I checked with SAX2 and it shows the currently configured
graphic card correctly as an Intel i830.  Meanwhile dmesg shows that my
laptop is using the vesa frame buffer driver.  That makes me ask then,
what is the connection between the SAX configuration and what dmesg
shows?   Maybe there is a URL or other resource someone can point me to
that will further my education about these things. ;-)  John


-- 
Check the headers for your unsubscription address
For additional commands send e-mail to suse-linux-e-help@xxxxxxxx
Also check the archives at http://lists.suse.com
Please read the FAQs: suse-linux-e-faq@xxxxxxxx