LinuxQuestions.org
Download your favorite Linux distribution at LQ ISO.
Go Back   LinuxQuestions.org > Forums > Linux Forums > Linux - Distributions > Slackware
User Name
Password
Slackware This Forum is for the discussion of Slackware Linux.

Notices

Reply
 
Search this Thread
Old 05-06-2011, 10:32 PM   #1
michijo
Member
 
Registered: Apr 2011
Posts: 162

Rep: Reputation: 0
Frame Buffer Console


Having some trouble with Frame Buffer Console and 256 colors. When I boot, there are two penguins at the type, signifying 256 colors. These sit up there for a few while text scrolls, then suddenly the screen blacks, and returns, penguins vanished, and the system boots normally, but with a vga error in the Linux console. No 256. The error has to do with inteldrmfb versus VESA. If I do 'cat /proc/fb', it returns '0 inteldrmfb'. I think VESA starts and has the penguins, then inteldrmfb cuts in. Otherwise, startx works and the X server works fine.
 
Old 05-07-2011, 03:04 AM   #2
Didier Spaier
Senior Member
 
Registered: Nov 2008
Location: Paris, France
Distribution: Slackware{,64}-14.1 on a Lenovo T61 6457-4XG
Posts: 3,955

Rep: Reputation: 936Reputation: 936Reputation: 936Reputation: 936Reputation: 936Reputation: 936Reputation: 936Reputation: 936
I have a nVidia GPU, not an Intel one, but a similar event occur during boot sequence.

Less than one second after booting, the VESA frame buffer (vesafb) is loaded, because I have "vga = 873" in lilo.conf :
Code:
[    0.413714] vesafb: framebuffer at 0xd5000000, mapped to 0xf8080000, using 13781k, total 14336k
[    0.413723] vesafb: mode is 1680x1050x32, linelength=6720, pages=1
[    0.413729] vesafb: protected mode interface info at c000:d050
[    0.413735] vesafb: pmi: set display start = c00cd0b3, set palette = c00cd10e
[    0.413741] vesafb: pmi: ports = 3b4 3b5 3ba 3c0 3c1 3c4 3c5 3c6 3c7 3c8 3c9 3cc 3ce 3cf 3d0 3d1 3d2 3d3 3d4 3d5 3da 
[    0.413763] vesafb: scrolling: redraw
[    0.413768] vesafb: Truecolor: size=8:8:8:8, shift=24:16:8:0
[    0.522650] Console: switching to colour frame buffer device 210x65
[    0.623470] fb0: VESA VGA frame buffer device
Later in the boot process, the handover occur, i.e. the Nouveau frame buffer driver (nouveaufb) take over the console and vesafb is unloaded:
Code:
[   49.337655] fb: conflicting fb hw usage nouveaufb vs VESA VGA - removing generic driver
[   49.337721] Console: switching to colour dummy device 80x25
When this occur, the screen is redrawn.

This is perfectly normal.

If I want to avoid that I can blacklist the Nouveau module, as anyhow it will be automatically loaded at X startup.

I am not sure that you can do the same with the Intel driver, but you may try.

BTW the two penguins don't mean 256 colors, but only that you have a dual core CPU. And they disappear when the screen is full in all cases.

Last edited by Didier Spaier; 05-07-2011 at 03:08 AM.
 
Old 05-07-2011, 05:17 AM   #3
gnashley
Amigo developer
 
Registered: Dec 2003
Location: Germany
Distribution: Slackware
Posts: 4,746

Rep: Reputation: 458Reputation: 458Reputation: 458Reputation: 458Reputation: 458
I believe in both cases that what you are seeing is the kernel modesetting taking place.
 
Old 05-07-2011, 07:26 AM   #4
adamk75
Senior Member
 
Registered: May 2006
Posts: 3,091

Rep: Reputation: 396Reputation: 396Reputation: 396Reputation: 396
Quote:
Originally Posted by Didier Spaier View Post
If I want to avoid that I can blacklist the Nouveau module, as anyhow it will be automatically loaded at X startup.

I am not sure that you can do the same with the Intel driver, but you may try.
If the OP does anything to prevent KMS from activating, X will not start on an Intel GPU.

Adam
 
Old 05-07-2011, 08:38 AM   #5
Didier Spaier
Senior Member
 
Registered: Nov 2008
Location: Paris, France
Distribution: Slackware{,64}-14.1 on a Lenovo T61 6457-4XG
Posts: 3,955

Rep: Reputation: 936Reputation: 936Reputation: 936Reputation: 936Reputation: 936Reputation: 936Reputation: 936Reputation: 936
Quote:
Originally Posted by adamk75 View Post
If the OP does anything to prevent KMS from activating, X will not start on an Intel GPU.

Adam
That would be adding "Append=nomodeset" to the kernel command line, or (in the case of Nouveau) using the "modeset=0" module parameter.

I didn't advise the OP to do that
 
Old 05-07-2011, 09:35 AM   #6
michijo
Member
 
Registered: Apr 2011
Posts: 162

Original Poster
Rep: Reputation: 0
In any case, I cannot view images in the linux console with seejpeg. I have tried altering '/etc/vga/libvga.config' and '/etc/lilo.conf' to no avail. Its not a big deal, but I thought it could be interesting to see an image in the linux console prior to running startx. Perhaps that would lead me to use the console more often instead of running an Xserver. Is modesetting preventing images from being displayed there? Isnt modesetting supposed to help graphics?

https://fedoraproject.org/wiki/Featu...nelModesetting

Last edited by michijo; 05-07-2011 at 09:40 AM.
 
Old 05-07-2011, 09:43 AM   #7
michijo
Member
 
Registered: Apr 2011
Posts: 162

Original Poster
Rep: Reputation: 0
intel

Quote:
Originally Posted by Didier Spaier View Post
Code:
[   49.337655] fb: conflicting fb hw usage nouveaufb vs VESA VGA - removing generic driver
[   49.337721] Console: switching to colour dummy device 80x25
When this occur, the screen is redrawn.

This is perfectly normal.
That is basically what happens but with Intel vs VESA.
 
Old 05-07-2011, 10:07 AM   #8
slacktroll
Member
 
Registered: May 2011
Distribution: Slackware 14.0 on Thinkpad X60
Posts: 56

Rep: Reputation: 3
the fbdev driver should work.
just tried with zgv. and that ends up with a segfault

ahh. it changes to some other colour depth.. interesting!

Last edited by slacktroll; 05-07-2011 at 10:18 AM.
 
Old 05-07-2011, 10:26 AM   #9
adamk75
Senior Member
 
Registered: May 2006
Posts: 3,091

Rep: Reputation: 396Reputation: 396Reputation: 396Reputation: 396
Quote:
Originally Posted by Didier Spaier View Post
That would be adding "Append=nomodeset" to the kernel command line, or (in the case of Nouveau) using the "modeset=0" module parameter.

I didn't advise the OP to do that
But KMS is provided by the intel DRM. If you blacklist the intel DRM, there's no KMS :-)
 
Old 05-07-2011, 11:18 AM   #10
slacktroll
Member
 
Registered: May 2011
Distribution: Slackware 14.0 on Thinkpad X60
Posts: 56

Rep: Reputation: 3
Long story short. Forget about seejpeg. It would probably need some patching to use fbdev directly instead of svgalib->fbdev. It actual search for modes and want's to set a mode. and it does not find any. mplayer worked fine with -vo fbdev but bugged out if i changed the -bpp switch. From my experience i would go with fbida directly. You will get a binary called fbi. In my case i did fbi *jpg and had a picture of usama bin laden.

git clone git://git.kraxel.org/fbida
make
make install
Works out of the box with i915 loaded with modeset=1

Url to homepage
http://www.kraxel.org/blog/linux/fbida/

Best Regards
Chris

Last edited by slacktroll; 05-07-2011 at 11:18 AM. Reason: typo
 
Old 05-07-2011, 07:30 PM   #11
michijo
Member
 
Registered: Apr 2011
Posts: 162

Original Poster
Rep: Reputation: 0
FBI

Quote:
Originally Posted by slacktroll View Post
Long story short. Forget about seejpeg. It would probably need some patching to use fbdev directly instead of svgalib->fbdev. It actual search for modes and want's to set a mode. and it does not find any. mplayer worked fine with -vo fbdev but bugged out if i changed the -bpp switch. From my experience i would go with fbida directly. You will get a binary called fbi. In my case i did fbi *jpg and had a picture of usama bin laden.

git clone git://git.kraxel.org/fbida
make
make install
Works out of the box with i915 loaded with modeset=1

Url to homepage
http://www.kraxel.org/blog/linux/fbida/

Best Regards
Chris
Awesome! Thanks for that tip. I saw my first console buffer jpg of a picture of wontons! Fbi works great and is easy to remember due to its similarity to the other FBI. Guess seejpeg doesnt work on my machine. I did try some image editing as well with ImageMagick, did composite overlapping and viewing with fbi, and found the mime settings in another thread to set fbi for elinks, so now can see images directly from elinks. Interested also in Links2. Havent installed yet.

Last edited by michijo; 05-07-2011 at 11:44 PM.
 
Old 05-08-2011, 05:07 AM   #12
Didier Spaier
Senior Member
 
Registered: Nov 2008
Location: Paris, France
Distribution: Slackware{,64}-14.1 on a Lenovo T61 6457-4XG
Posts: 3,955

Rep: Reputation: 936Reputation: 936Reputation: 936Reputation: 936Reputation: 936Reputation: 936Reputation: 936Reputation: 936
FYI, slackbuild.org host a slackbuild for fbida.
 
1 members found this post helpful.
  


Reply


Thread Tools Search this Thread
Search this Thread:

Advanced Search

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

BB code is On
Smilies are On
[IMG] code is Off
HTML code is Off


Similar Threads
Thread Thread Starter Forum Replies Last Post
[SOLVED] console:switching to colour frame buffer device 128x48 while kernel boot 2.6.33-smp matters Slackware 39 05-27-2010 11:05 AM
Linux frame buffer console help needed ssenuta Linux - Hardware 0 09-20-2007 10:55 AM
console frame buffer @ 640x480 only edM Slackware 6 08-23-2004 09:29 AM
nvidia driver form nvida & frame buffer console dosen't work together linuxlah Linux - General 0 03-11-2004 08:38 PM
Problems with changing the frame buffer setting in console. adz Linux - Software 1 10-23-2003 02:25 AM


All times are GMT -5. The time now is 08:22 PM.

Main Menu
My LQ
Write for LQ
LinuxQuestions.org is looking for people interested in writing Editorials, Articles, Reviews, and more. If you'd like to contribute content, let us know.
Main Menu
Syndicate
RSS1  Latest Threads
RSS1  LQ News
Twitter: @linuxquestions
identi.ca: @linuxquestions
Facebook: linuxquestions Google+: linuxquestions
Open Source Consulting | Domain Registration