[gentoo-user] Framebuffer
Genthinktank, How can you determine all the available frambuffer resolutions and colour depths on a particular host for vesafb. I normally set this through trial and error but there must be a command to determine these? JDM
Re: [gentoo-user] Framebuffer
On Wed, May 18, 2011 at 03:10:02PM +0200, JDM wrote: Genthinktank, How can you determine all the available frambuffer resolutions and colour depths on a particular host for vesafb. I normally set this through trial and error but there must be a command to determine these? JDM I think fbset will do, check the man page. -- caveat utilitor ♫ ❤ ♫ ❤ ♫ ❤ ♫
Re: [gentoo-user] Framebuffer
That's called vbe information.If you have grub2,you can enter the command mode and type 'vbeinfo',or if you use uvesafb,you will get vbe info here at /sys/devices/platform/uvesafb.0/graphics/fb0/modes 2011/5/18 Indi thebeelzebubtrig...@gmail.com: On Wed, May 18, 2011 at 03:10:02PM +0200, JDM wrote: Genthinktank, How can you determine all the available frambuffer resolutions and colour depths on a particular host for vesafb. I normally set this through trial and error but there must be a command to determine these? JDM I think fbset will do, check the man page. -- caveat utilitor ♫ ❤ ♫ ❤ ♫ ❤ ♫
Re: [gentoo-user] Framebuffer
On Wed, May 18, 2011 at 5:57 AM, JDM j...@arcticwolf.myzen.co.uk wrote: Genthinktank, How can you determine all the available frambuffer resolutions and colour depths on a particular host for vesafb. I normally set this through trial and error but there must be a command to determine these? JDM HTH, Mark c2stable ~ # hwinfo --framebuffer 02: None 00.0: 11001 VESA Framebuffer [Created at bios.459] Unique ID: rdCR.u0Yr_tr7pZ7 Hardware Class: framebuffer Model: NVIDIA GF100 Board - 10250008 Vendor: NVIDIA Corporation Device: GF100 Board - 10250008 SubVendor: NVIDIA SubDevice: Revision: Chip Rev Memory Size: 14 MB Memory Range: 0xd500-0xd5df (rw) Mode 0x0300: 640x400 (+640), 8 bits Mode 0x0301: 640x480 (+640), 8 bits Mode 0x0303: 800x600 (+800), 8 bits Mode 0x030e: 320x200 (+640), 16 bits Mode 0x030f: 320x200 (+1280), 24 bits Mode 0x0311: 640x480 (+1280), 16 bits Mode 0x0312: 640x480 (+2560), 24 bits Mode 0x0314: 800x600 (+1600), 16 bits Mode 0x0315: 800x600 (+3200), 24 bits Mode 0x0330: 320x200 (+320), 8 bits Mode 0x0331: 320x400 (+320), 8 bits Mode 0x0332: 320x400 (+640), 16 bits Mode 0x0333: 320x400 (+1280), 24 bits Mode 0x0334: 320x240 (+320), 8 bits Mode 0x0335: 320x240 (+640), 16 bits Mode 0x0336: 320x240 (+1280), 24 bits Mode 0x033d: 640x400 (+1280), 16 bits Mode 0x033e: 640x400 (+2560), 24 bits Config Status: cfg=new, avail=yes, need=no, active=unknown c2stable ~ #
[gentoo-user] Framebuffer change from 2.6.26 to 2.6.27
When I boot 2.6.27-r2, it creates /dev/fb0 and /dev/db, which X complains about and refuses to run. My machine has an ATI Radeon and X under 2.6.26 finds the right driver just fine, but X under 2.6.27 just barfs and refuses to run. I can del the two device entries and X is happy, but this seems like the wrong thing to do. The 2.6.27 kernel has this dmesg which 2.6.26 doesn't: Console: switching to colour frame buffer device 80x30 Framebuffer is configured as modules in both kernels, and none are loaded by conf.d/modules. However, 2.6.27 loads atyfb on its own and the boot screen flickers at two points, presumably as it switches to the frame buffer. Is there some difference in 2.6.26 and 2.6.27 regarding the frame buffer? Is there any boot option to disbale the frame buffer? -- ... _._. ._ ._. . _._. ._. ___ .__ ._. . .__. ._ .. ._. Felix Finch: scarecrow repairman rocket surgeon / [EMAIL PROTECTED] GPG = E987 4493 C860 246C 3B1E 6477 7838 76E9 182E 8151 ITAR license #4933 I've found a solution to Fermat's Last Theorem but I see I've run out of room o
Re: [gentoo-user] framebuffer hangs in 2.6.26
The current kernel that I am running is 2.6.26.5-rt9-gentoo2.
Sporadically this freezes, usually happening during the end of
emerging an ebuild or when stopping gpm. Usually, the fb only freezes
for a few seconds, but sometimes I have to AltSysRqO the machine
(it's unresponsive to AltSysRq{R,S,E,I,K,U}).
I have the feeling that this is a regression because the framebuffer
never froze on 2.6.25.4-rt5-gentoo nor on the kernel on the 2008.0
install/minimal CD.
Any suggestions?
Note: I emailed about this on lkml, yet got no replies.
I think something similar happened to me; I am using vanilla-sources.
As for version, see
$ uname -a
Linux jorge 2.6.26.6 #1 Fri Oct 10 00:52:35 BRT 2008 i686 AMD
Athlon(tm) XP 2600
+ AuthenticAMD GNU/Linux
(although, at the time of the problem, it might have been 2.6.26.5)
The computer froze during an emerge of multiple ebuilds (I couldn't
know if the emerge had finished or not, but I intensely hope it had -
I hate system inconsistencies and filesystem corruptions).
The system were completely unresponsive to ctrlaltfn and the magic
sysrq keys, except AltSysRqo. In fact, even the keyboard leds were
unresponsive AFAIR (as far as I recall).
Note: Despite the system *seeming* unresponsive to the other
altsysrq keys, *maybe* they were indeed effective, and I did the
whole AltSysRqr, AltSysRqe, wait 5 seconds, AltSysRqi,
AltSysRqs, wait 5 seconds, AltSysRqu, wait 5 seconds,
AltSysRqo hoping that this would cleanly shutdown my computer.
AFAIR, the next boot did indicate that the filesystem had been cleanly
umounted)
On 2008-10-18 it happened again. Using vanilla sources 2.6.26.6. Again, it was
after an emerge (but it wasn't immediately after, it was some minutes
later). For the record, I am using a tmpfs on PORTAGE_TMPDIR (and it
is 1536 MB, far more than enough for emerging the programs I was
emerging - gimp-help, yasm, libpcre, subversion, giflib - and I have 1
GB RAM and 972 MB of swap - and I was not running any memory-intensive
apps (just enlightenment, gkrellm, pidgin, and firefox viewing a
single page on Ubuntu wiki) The emerge went fine with absolutely no
errors. Some minutes later, when I was preparing to shutdown the
system, the system became unresponsive just after I tried to close
pidgin.
It seems that the system becomes completely unresponsive to keyboard
(except the magic sysrq keys); ctrlaltfn , ctrlaltbackspace ,
ctrlaltdel, nothing responds. The screen is completely frozen
(so I don't know if the computer responds to the mouse). The system
itself isn't frozen though - I have cron jobs that beep every 15
minutes (to keep me informed of the time), and I heard the expected
beep when the time reached 7:00 (I woke up early, at 5:45). I then
performed altsysrqr, but the system seemed still unresponsive to
keyboard. I left the system idle for more than 30 minutes, to see if
it would recover. It didn't.
I then rebooted with the EISUB sysrq keys combination. The system
indeed responded to theses keys - it rebooted and, on the next boot,
the filesystem was reportedly clean.
I was using e17. Since i changed to Xfce, I haven't had this problem.
It is very possible, though, that this was just a coincidence, and the
bug is not e17's fault
--
Software is like sex: it is better when it is free - Linus Torvalds
[gentoo-user] framebuffer hangs in 2.6.26
The current kernel that I am running is 2.6.26.5-rt9-gentoo2.
Sporadically this freezes, usually happening during the end of
emerging an ebuild or when stopping gpm. Usually, the fb only freezes
for a few seconds, but sometimes I have to AltSysRqO the machine
(it's unresponsive to AltSysRq{R,S,E,I,K,U}).
I have the feeling that this is a regression because the framebuffer
never froze on 2.6.25.4-rt5-gentoo nor on the kernel on the 2008.0
install/minimal CD.
Any suggestions?
Note: I emailed about this on lkml, yet got no replies.
--
Andrey Vul
A: Because it messes up the order in which people normally read text.
Q: Why is top-posting such a bad thing?
A: Top-posting.
Q: What is the most annoying thing in e-mail?
Re: [gentoo-user] framebuffer questions
On Mon, Jun 04, 2007 at 07:58:45PM -0700, maxim wexler wrote: Geert Uytterhoeven, who's listed as the author at the end of man fbset, pointed out that since I only have one video card, I only need one framebuffer, whereas I had two: ATI and VESA. So I reconfig'd w/o VESA and removed the video=vesafb... from the kernel line in grub.conf. Then I put fbset -a 1024x768-76 in local.start and rebooted. The framebuffer opens up beautifully. Excellent :) Always helps to ask someone who known what they're talking about I think I should put it in /etc/inittab but where? Does it matter? Or maybe it should be video=aty128fb...on the kernel line. Still some tweaking to do. But I think most of the heavy lifting is over. I would have thought video=aty128fb:[EMAIL PROTECTED] in grub.conf should do it. Have a look at /usr/src/linux/Documentation/fb/aty128fb.txt for a few other options. I wouldn't mess around with inittab if you can possibly help it. Glad to hear it's mostly working, -Nick -- GPG Key : www.njw.me.uk/nick.gpg.asc GPG Key ID: 04E4653F GPG Fingerprint: 9732 D7C7 A441 D79E FDF0 94F6 1F48 5674 04E4 653F pgpWKsNaf41Wz.pgp Description: PGP signature
Re: [gentoo-user] framebuffer questions
I would have thought video=aty128fb:[EMAIL PROTECTED] in grub.conf should Yep, that did it. For *all* the consoles Glad to hear it's mostly working, -Nick Thanks Nick. Did I call you Dale yesterday? Sorry. mw 8:00? 8:25? 8:40? Find a flick in no time with the Yahoo! Search movie showtime shortcut. http://tools.search.yahoo.com/shortcuts/#news -- [EMAIL PROTECTED] mailing list
Re: [gentoo-user] framebuffer questions
On Tue, 5 Jun 2007 07:25:48 -0700 (PDT) maxim wexler [EMAIL PROTECTED] wrote: I would have thought video=aty128fb:[EMAIL PROTECTED] in grub.conf should Yep, that did it. For *all* the consoles After all this time, the problem was just having two different frambuffer drivers in there at once? I guess they were tripping over each other. -- [EMAIL PROTECTED] mailing list
Re: [gentoo-user] framebuffer questions
Here it is in chroot: mode 1024x768-76 # D: 78.653 MHz, H: 59.949 kHz, V: 75.694 Hz geometry 1024 768 1024 768 16 timings 12714 128 32 16 4 128 4 rgba 5/11,6/5,5/0,0/0 endmode /etc/fb.modes:5: syntax error Remove the rgba line from fb.modes, and it should work OK. I don't think it's necessary, and mine works without it. Good luck, -Nick -- GPG Key : www.njw.me.uk/nick.gpg.asc GPG Key ID: 04E4653F GPG Fingerprint: 9732 D7C7 A441 D79E FDF0 94F6 1F48 5674 04E4 653F SIP : [EMAIL PROTECTED]PSTN: 0560 0030509 pgpPn37WVQUzH.pgp Description: PGP signature
Re: [gentoo-user] framebuffer questions
--- Nick [EMAIL PROTECTED] wrote: Here it is in chroot: mode 1024x768-76 # D: 78.653 MHz, H: 59.949 kHz, V: 75.694 Hz geometry 1024 768 1024 768 16 timings 12714 128 32 16 4 128 4 rgba 5/11,6/5,5/0,0/0 endmode /etc/fb.modes:5: syntax error Remove the rgba line from fb.modes, and it should work OK. I don't think it's necessary, and mine works without it. Nope. PC still boots with lame framebuffer. Now it's: #fbset -s /dev/fb0 Unknown video mode '/dev/fb0' But, #fbset -s -fb /dev/fb0 mode 640x480-60 # D: 25.171 MHz, H: 31.463 kHz, V: 59.930 Hz geometry 640 480 640 480 8 timings 39729 48 16 33 10 96 2 rgba 8/0,8/0,8/0,0/0 endmode Line 5 has been replaced #fbset -s /dev/fb1 Unknown video mode '/dev/fb1' And for #fbset -s -fb /dev/fb1 mode 1280x1024-60 # D: 108.944 MHz, H: 63.599 kHz, V: 59.999 Hz geometry 1280 1024 1280 1024 32 timings 9179 217 79 32 1 137 3 vsync high rgba 8/16,8/8,8/0,0/0 endmode Line 5 is baack! I don't think fbset even looks at /etc/fb.modes, least not with the -fb option. FWIW: $cat /proc/fb 0 ATY Rage 128 1 VESA VGA ??? Boardwalk for $500? In 2007? Ha! Play Monopoly Here and Now (it's updated for today's economy) at Yahoo! Games. http://get.games.yahoo.com/proddesc?gamekey=monopolyherenow -- [EMAIL PROTECTED] mailing list
Re: [gentoo-user] framebuffer questions
On Mon, Jun 04, 2007 at 08:21:19AM -0700, maxim wexler wrote: --- Nick [EMAIL PROTECTED] wrote: Here it is in chroot: mode 1024x768-76 # D: 78.653 MHz, H: 59.949 kHz, V: 75.694 Hz geometry 1024 768 1024 768 16 timings 12714 128 32 16 4 128 4 rgba 5/11,6/5,5/0,0/0 endmode /etc/fb.modes:5: syntax error Nope. PC still boots with lame framebuffer. Did you try just running fbset -a 1024x768-76 on the command line, after bootup? If this works (and it just doesn't set itself correctly when booting) you could add this command to /etc/conf.d/local.start This is how I do it on my machine. -- GPG Key : www.njw.me.uk/nick.gpg.asc GPG Key ID: 04E4653F GPG Fingerprint: 9732 D7C7 A441 D79E FDF0 94F6 1F48 5674 04E4 653F SIP : [EMAIL PROTECTED]PSTN: 0560 0030509 pgplExmsPv93y.pgp Description: PGP signature
Re: [gentoo-user] framebuffer questions
Did you try just running fbset -a 1024x768-76 on the command line, after bootup? If this works (and it just Well, well, well. I've tried this command before --shoulda mentioned it. What happened was that the screen would try to change itself but drop back into default(?) mode with a lot of staticky looking stuff all over the screen. But, this time, boom! Now everything is scrunched into the upper left hand corner of the screen. I've maxed out the settings in the screen control panel on the monitor itself and managed to move the text to a band down the center of the screen with margins of about two inches. Now instead of no margins, they're too big. I tried adjusting the command but whatever I enter it replies; Unknown video mode '800x600-60' for example. or Unknown video mode '1024x768-60'. But the display is otherwise just like with the boot CD. And the bare fbset command reveals the new mode. Another thing: doesn't the -a switch set (a)ll the consoles? Not in this instance. Now for my finale, hot off the hard drive there is: localhost ~ # fbset -fb /dev/fb0 mode 1024x768-76 # D: 78.653 MHz, H: 59.949 kHz, V: 75.694 Hz geometry 1024 768 1024 768 16 timings 12714 128 32 16 4 128 4 accel true rgba 5/10,5/5,5/0,0/0 endmode localhost ~ # fbset -fb /dev/fb1 mode 1280x1024-60 # D: 108.944 MHz, H: 63.599 kHz, V: 59.999 Hz geometry 1280 1024 1280 1024 32 timings 9179 217 79 32 1 137 3 vsync high rgba 8/16,8/8,8/0,0/0 endmode If I try using the last mode the screen goes blank for about a solid minute then reverts back to the first. What's even more confusing is that in the .config I have CONFIG_FB_VESA_DEFAULT_MODE=[EMAIL PROTECTED]. Why doesn't it try that since now my command line has just video=vesafb with *no* parameters at all? And no complaints in dmesg. mw Luggage? GPS? Comic books? Check out fitting gifts for grads at Yahoo! Search http://search.yahoo.com/search?fr=oni_on_mailp=graduation+giftscs=bz -- [EMAIL PROTECTED] mailing list
Re: [gentoo-user] framebuffer questions
But, this time, boom! Now everything is scrunched into the upper left hand corner of the screen. I've maxed out the settings in the screen control panel on the monitor itself and managed to move the text to a band down the center of the screen with margins of about two inches. Now instead of no margins, they're too big. ... mode 1024x768-76 # D: 78.653 MHz, H: 59.949 kHz, V: 75.694 Hz geometry 1024 768 1024 768 16 timings 12714 128 32 16 4 128 4 accel true rgba 5/10,5/5,5/0,0/0 endmode Okay, this is somewhat of a guess, but perhaps some of the timings are incorrect, as this controls margins (see fbset manpage). First it may be wise to change the first timing setting (pixclock) to 0 (at least for now), as this'll auto-select that setting. For the others, perhaps you could experiment with the settings individually, using fbset, to get an idea of whether they may have a part to play in this most odd problem. Something like fbset -left 100. Another thing: doesn't the -a switch set (a)ll the consoles? Not in this instance. Yes, it should, and does for me... What's even more confusing is that in the .config I have CONFIG_FB_VESA_DEFAULT_MODE=[EMAIL PROTECTED]. Why doesn't it try that since now my command line has just video=vesafb with *no* parameters at all? And no complaints in dmesg. As far as I can see it should... Hmm... Sorry I can't be more help. Good luck -Nick -- GPG Key : www.njw.me.uk/nick.gpg.asc GPG Key ID: 04E4653F GPG Fingerprint: 9732 D7C7 A441 D79E FDF0 94F6 1F48 5674 04E4 653F pgpwDqnfczooW.pgp Description: PGP signature
Re: [gentoo-user] framebuffer questions
Sorry I can't be more help. Geert Uytterhoeven, who's listed as the author at the end of man fbset, pointed out that since I only have one video card, I only need one framebuffer, whereas I had two: ATI and VESA. So I reconfig'd w/o VESA and removed the video=vesafb... from the kernel line in grub.conf. Then I put fbset -a 1024x768-76 in local.start and rebooted. The framebuffer opens up beautifully. Without the scrunch or big margins but still only in the one console and it doesn't switch until the boot process gets to the .start file. Rather have a continuous high-res o/p from the start like with the bootCD. I think I should put it in /etc/inittab but where? Does it matter? Or maybe it should be video=aty128fb...on the kernel line. Still some tweaking to do. But I think most of the heavy lifting is over. Thanks Dale. Maxim. Sick sense of humor? Visit Yahoo! TV's Comedy with an Edge to see what's on, when. http://tv.yahoo.com/collections/222 -- [EMAIL PROTECTED] mailing list
Re: [gentoo-user] framebuffer questions
On Sat, 2 Jun 2007 20:19:12 -0700 (PDT) maxim wexler [EMAIL PROTECTED] wrote: also, gentoo has a doc: http://www.gentoo.org/doc/en/handbook/handbook-x86.xml?part=1chap=10 That gives the best explanation. Now dmesg | grep -i vesa concludes with: ... vesafb: framebuffer at 0xf000, mapped to 0xd190, using 10240k,total 16384k fb1: VESA VGA frame buffer device. Thke vesafb driver is built into the kernel, right? You need it right away when booting. No sense in fiddling around with initrd's, just put it in the kernel. But, the screen looks the same. I started out with 1024x768 then changed to 1280x1024 but certain web pages still do not fit the screen. For example, a trip to the above handbook address using elinks is an exercise in frustration. As you scroll down using the down arrow the page jumps from side to side making it very difficult to follow. That does sound frustrating. Let me provide some qotes: | |video=vesafb:mtrr:3,ywrap,[EMAIL PROTECTED] | I still think your boot line isn't quite right. May I see the updated version from /proc/cmdline ? If I manually enter the kernel line at the prompt w/o mentioning the framebuffer at all one is installed anyway which is just like all the others :( Yes, that's why I think the boot command line isn't quite right. The kernel loads the driver eventually, if it's not specified the settings at boot, just like all other drivers get loaded, and if they find hardware to support, generally say something on the console. By the time vesafb loads on your system, it's already initialized the console and it's too late to give it the resolution you want. -- [EMAIL PROTECTED] mailing list
Re: [gentoo-user] framebuffer questions
Thke vesafb driver is built into the kernel, right? Right. I see the updated version from /proc/cmdline ? root=/dev/hda3 video=vesafb:mtrr3,ywrap,[EMAIL PROTECTED] ^^ have change these back and forth using different freqs, res's color depths -- makes no difference And see the results of vbeprobe in a fresh post. mw Fussy? Opinionated? Impossible to please? Perfect. Join Yahoo!'s user panel and lay it on us. http://surveylink.yahoo.com/gmrs/yahoo_panel_invite.asp?a=7 -- [EMAIL PROTECTED] mailing list
Re: [gentoo-user] framebuffer questions
have you tried with just '1280x1024' ? No help slaps his forhead Of course, when the LiveCD boots the framebuffer comes up in a usable configuration. So I boot the CD and chroot. In chroot #fbset -s is completely different than in regular mode. Here's #fbset -s after the PC boots as usual: mode 640x480-60 # D: 25.171 MHz, H: 31.463 kHz, V: 59.930 Hz geometry 640 480 640 480 8 timings 39729 48 16 33 10 96 2 rgba 8/0,8/0,8/0,0/0 endmode Which is quite useless to me. Here it is in chroot: mode 1024x768-76 # D: 78.653 MHz, H: 59.949 kHz, V: 75.694 Hz geometry 1024 768 1024 768 16 timings 12714 128 32 16 4 128 4 rgba 5/11,6/5,5/0,0/0 endmode More like it! Now if only I can get non-chroot to accept the chroot modes. So I copied the better mode to the /etc/fb.modes. But when I give it #fbset 1024x768-76(or anything else) it answers: /etc/fb.modes:5: syntax error But line 5(if that's what the '5' refers to) has the same format in both versions. Neither of which were touched by human hands. Anyways I know there's nothing wrong with the card or monitor. The BIOS? Doesn't seem to hamper the CD. mw Never miss an email again! Yahoo! Toolbar alerts you the instant new Mail arrives. http://tools.search.yahoo.com/toolbar/features/mail/ -- [EMAIL PROTECTED] mailing list
[gentoo-user] framebuffer questions
Hi group. For a 2.6.19 kernel w/ATI Rage128 card on a non-X box. I've been experimenting with the framebuffer and following the http://gentoo-wiki.com/HOWTO_Framebuffer:Bootsplash:Grubsplash I'd like at the least for the entire page to appear in elinks at once without having to scroll from side to side to read something Under graphics support I chose *vesa-tng and default mode [EMAIL PROTECTED] Just guessing. FWIW using a Mag-Innovision monitor XJ500T c 1996. Don't have a clue of it's Hsync or Vsync specs. I did emerge bootsplash but haven't config'd it yet. According to a posting on this group I added video=vesafs:1024x768-72:ywrap:mtrr to the kernel line in grub.conf, installed the bootloader and booted. This is what $dmesg|grep -i vesa reveals: Kernel command line: root=/dev/hda3 video=vesafb:1024x768-72:ywrap:mtrr vesafb: ATI Technologies Inc., R128, 01.00 (OEM: ATI RAGE128) vesafb: VBE version: 2.0 vesafb: protected mode interface info at c000:441b vesafb: pmi: set display start = c00c4489, set palette = c00c44c3 vesafb: pmi: ports = c810 c816 c854 c838 c83c c85c c800 c804 c8b0 c8b2 c8b4 vesafb: no monitor limits have been set vesafb: invalid resolution, width not specified vesafb: probe of vesafb.0 failed with error -22 And elinks page still scroll sideways :( Can somebody enlighten me? Maxim Moody friends. Drama queens. Your life? Nope! - their life, your story. Play Sims Stories at Yahoo! Games. http://sims.yahoo.com/ -- [EMAIL PROTECTED] mailing list
Re: [gentoo-user] framebuffer questions
On Sat, 2 Jun 2007 13:53:36 -0700 (PDT) maxim wexler [EMAIL PROTECTED] wrote: Hi group. For a 2.6.19 kernel w/ATI Rage128 card on a non-X box. I've been experimenting with the framebuffer and following the http://gentoo-wiki.com/HOWTO_Framebuffer:Bootsplash:Grubsplash I'd like at the least for the entire page to appear in elinks at once without having to scroll from side to side to read something Under graphics support I chose *vesa-tng and default mode [EMAIL PROTECTED] Just guessing. FWIW using a Mag-Innovision monitor XJ500T c 1996. Don't have a clue of it's Hsync or Vsync specs. I did emerge bootsplash but haven't config'd it yet. According to a posting on this group I added video=vesafs:1024x768-72:ywrap:mtrr to the kernel line in grub.conf, installed the bootloader and booted. This is what $dmesg|grep -i vesa reveals: Kernel command line: root=/dev/hda3 video=vesafb:1024x768-72:ywrap:mtrr For me, | [EMAIL PROTECTED] ~ $ cat /proc/cmdline | root=/dev/sda3 video=vesafb:mtrr,ywrap vga=0x031b See the comma? Also, you don't need to use vga, but are you sure you don't want an '@' where you have a '-' ? Moody friends. Drama queens. Your life? Nope! - their life, your story. Play Sims Stories at Yahoo! Games. http://sims.yahoo.com/ -- [EMAIL PROTECTED] mailing list
Re: [gentoo-user] framebuffer questions
For me, | [EMAIL PROTECTED] ~ $ cat /proc/cmdline | root=/dev/sda3 video=vesafb:mtrr,ywrap vga=0x031b This doesn't work. Get dumped to a screen with the error message: 'You passed an undefined node number' Then a request to pick 0-9 modes or use 'scan' Choosing Scan freezes the console for about 15 secs after which default(?) framebuffer boots. Picking modes 7-9 leads to Unknown mode, invalid ID. Picking modes 0-6 leads to the same default(?) framebuffer. See the comma? Also, you don't need to use vga, but are you sure you don't want an '@' where you have a '-' ? This was the model I followed in the posting http://groups.google.ca/group/linux.gentoo.user/browse_thread/thread/114f64c0165ab4f3/2007d4aca55bd086?lnk=stq=framebuffer+1024x768-60+fishrnum=1hl=en#2007d4aca55bd086 BTW, some googling revealed that that my monitor has the following specs: EISA ID:0, Horiz Khz: 30.0-70.0; Vert Hz: 50.0-120.0 Any idea how and where to incorporate this info? mw Never miss an email again! Yahoo! Toolbar alerts you the instant new Mail arrives. http://tools.search.yahoo.com/toolbar/features/mail/ -- [EMAIL PROTECTED] mailing list
Re: [gentoo-user] framebuffer questions
On Sat, 2 Jun 2007 16:01:07 -0700 (PDT) maxim wexler [EMAIL PROTECTED] wrote: For me, | [EMAIL PROTECTED] ~ $ cat /proc/cmdline | root=/dev/sda3 video=vesafb:mtrr,ywrap vga=0x031b This doesn't work. Get dumped to a screen with the error message: 'You passed an undefined node number' Then a request to pick 0-9 modes or use 'scan' Choosing Scan freezes the console for about 15 secs after which default(?) framebuffer boots. Picking modes 7-9 leads to Unknown mode, invalid ID. Picking modes 0-6 leads to the same default(?) framebuffer. See the comma? Also, you don't need to use vga, but are you sure you don't want an '@' where you have a '-' ? This was the model I followed in the posting http://groups.google.ca/group/linux.gentoo.user/browse_thread/thread/114f64c0165ab4f3/2007d4aca55bd086?lnk=stq=framebuffer+1024x768-60+fishrnum=1hl=en#2007d4aca55bd086 BTW, some googling revealed that that my monitor has the following specs: EISA ID:0, Horiz Khz: 30.0-70.0; Vert Hz: 50.0-120.0 Any idea how and where to incorporate this info? mw Never miss an email again! Yahoo! Toolbar alerts you the instant new Mail arrives. http://tools.search.yahoo.com/toolbar/features/mail/ That link made it a little clearer; the vesafb driver is being used by me because to it has been added x86_64 support. Vesafb_tng doesn't work on 64-bit -- but if you're 32bit ,that's what you should be using. But have you tried commas rather than colons? and with an @ symbol? That's how http://dev.gentoo.org/~spock/projects/vesafb-tng/, http://gentoo-wiki.com/HOWTO_gensplash#Required_Kernel_Options, and more list it. the dash goes before depth, not refresh. also, gentoo has a doc: http://www.gentoo.org/doc/en/handbook/handbook-x86.xml?part=1chap=10 good luck. -- [EMAIL PROTECTED] mailing list
Re: [gentoo-user] framebuffer questions
also, gentoo has a doc: http://www.gentoo.org/doc/en/handbook/handbook-x86.xml?part=1chap=10 That gives the best explanation. Now dmesg | grep -i vesa concludes with: ... vesafb: framebuffer at 0xf000, mapped to 0xd190, using 10240k,total 16384k fb1: VESA VGA frame buffer device. But, the screen looks the same. I started out with 1024x768 then changed to 1280x1024 but certain web pages still do not fit the screen. For example, a trip to the above handbook address using elinks is an exercise in frustration. As you scroll down using the down arrow the page jumps from side to side making it very difficult to follow. FWIW if I drop to the grub prompt and use grubvbeprobe I get 'vbeprobe 0xff00 is not found or supported' If I use grub testvbe 1280 I get 'mode 0x400 not supported'. For 1024, it's '0x400 not supported'. For 800, it's '0x300 not supported'. For 640, '0x200 not supported'. Which is weird cause the monitor is clearly using *some kind of mode*. If I manually enter the kernel line at the prompt w/o mentioning the framebuffer at all one is installed anyway which is just like all the others :( mw Choose the right car based on your needs. Check out Yahoo! Autos new Car Finder tool. http://autos.yahoo.com/carfinder/ -- [EMAIL PROTECTED] mailing list
Re: [gentoo-user] Framebuffer problems
kernel /bzImage-fb1280 root=/dev/hda8 video=vesafb:ywrap,mtrr vga=0x0317 splash=verbose,theme:Gentoo-Hornet Try 0x31B, it might be happier with 24 bit colour. Then after that brief 80x60(?) display gentoo proceeds to boot with 1280x1024 reso (and the dmesg info scrolls up while tux sits on top of it... but sadly without using my splash theme :( ). You can't have a framebuffer splash and tux, it's one or the other. I believe this is documented in some inconvenient place in the kernel configuration. Relevant parts of my grub.conf: kernel /boot/kernel-2.6.20-gentoo root=/dev/sda2 vga=0x31B splash=verbose,theme:echoes video=vesafb:mtrr,ywrap initrd /boot/initrd-fbsplash (I chose the easy method and put my splash images in an initramfs file, but if you've added yours to the kernel that should work fine too) --Thomas pgp5B5IIB4RLB.pgp Description: PGP signature
[gentoo-user] Framebuffer problems
Hello, I enabled framebuffer on the kernel (vesa-fb with 1280x1024 resolution) and I use this grub menu entry for framebuffer: kernel /bzImage-fb1280 root=/dev/hda8 video=vesafb:ywrap,mtrr vga=0x0317 splash=verbose,theme:Gentoo-Hornet But everytime I boot there's a message that says the video mode is wrong and prompts me to choose from some menu entry of video modes or go straight to boot up. Then after that brief 80x60(?) display gentoo proceeds to boot with 1280x1024 reso (and the dmesg info scrolls up while tux sits on top of it... but sadly without using my splash theme :( ). I was hoping to have a graphical background but it didn't happen. What else should I look into? I followed this howto http://gentoo-wiki.com/HOWTO_fbsplash Thanks. -- Jed R. Mallen | GPG key ID: 81E575A3 fp: 4E1E CBA5 7E6A 2F8B 8756 660A E54C 39D6 81E5 75A3 | http://jed.sitesled.com -- gentoo-user@gentoo.org mailing list
[gentoo-user] Framebuffer and kenerl options
Installing from scratch and getting confused about where the kernel framebuffer stuff is. Quoting from the handbook here: --- First of all you need to know what type of framebuffer device you're using. If you use a Gentoo patched kernel tree (such as gentoo-sources) you will have had the possibility of selecting vesafb-tng as the VESA driver type (which is default for these kernel sources). If this is the case, you are using vesafb-tng and do not need to set a vga statement. Otherwise you are using the vesafb driver and need to set the vga statement. --- I did use the gentoo-sources. I did not use genkernel. I didn't see anything about vesafb-tng in the make menuconfig options nor in the resulting .config. I'm assuming its under Graphic Drivers section? In older kernels I remember this being obvious but not in this one. The install manual tells you that you have to know which type of device but I wasn't able to tell where in the kernel config this is? I've run gentoo for about a year or more and have never really got the framebuffer stuff to work like I wanted, so have just ignored it all that time. I'd now like to get it working finally. Seemed the stumbling block has always been getting the large console resolution 1280x1024. This is easily accomplished in lilo so I've been running that way, but then ... no framebuffer. W I want the gentoo trademark too. -- gentoo-user@gentoo.org mailing list
Re: [gentoo-user] Framebuffer and kenerl options
It's under device drivers-graphic support. You select Support for framebuffer. Select it and you get a VESA VGA graphics support option in the list which has a sub item with VESA driver type Hit enter there and you can select vesa or vesafb-tng. On Thursday 08 December 2005 21:45, Harry Putnam wrote: Installing from scratch and getting confused about where the kernel framebuffer stuff is. Quoting from the handbook here: --- First of all you need to know what type of framebuffer device you're using. If you use a Gentoo patched kernel tree (such as gentoo-sources) you will have had the possibility of selecting vesafb-tng as the VESA driver type (which is default for these kernel sources). If this is the case, you are using vesafb-tng and do not need to set a vga statement. Otherwise you are using the vesafb driver and need to set the vga statement. --- I did use the gentoo-sources. I did not use genkernel. I didn't see anything about vesafb-tng in the make menuconfig options nor in the resulting .config. I'm assuming its under Graphic Drivers section? In older kernels I remember this being obvious but not in this one. The install manual tells you that you have to know which type of device but I wasn't able to tell where in the kernel config this is? I've run gentoo for about a year or more and have never really got the framebuffer stuff to work like I wanted, so have just ignored it all that time. I'd now like to get it working finally. Seemed the stumbling block has always been getting the large console resolution 1280x1024. This is easily accomplished in lilo so I've been running that way, but then ... no framebuffer. W I want the gentoo trademark too. -- gentoo-user@gentoo.org mailing list
Re: [gentoo-user] framebuffer questions
On Thu, 2005-06-30 at 11:09 -0500, LostSon wrote: Hello I am trying to set my framebuffer so at boot time i get 1024x768 i am not using a splash screen just want the terminal at 1024x768, i have read the tutorial and compiled in all the components i need but jsut cant get it to work my grub.conf looks like this title=Gentoo-2.6.11-r11-boot-1024 root (hd0,0) kernel (hd0,0)/boot/bzImage.new3 root=/dev/hda3 video=vesafb:[EMAIL PROTECTED] That is all on one line right? firstly, try a lower resolution, like 800x600-24 just to see. title=Gentoo-2.6.11-r11-boot-1024 root (hd0,0) kernel (hd0,0)/boot/bzImage.new3 root=/dev/hda3 video=vesafb:ywrap,mtrr vga=0x318 secondly, you cant mix video= and vga= thirdly, what errors (if any) did you get? don't forget this step - you might find people don't answer without it! HTH, -- Iain Buchanan [EMAIL PROTECTED] -- gentoo-user@gentoo.org mailing list
Re: [gentoo-user] framebuffer questions
Another option is to just compile the framebuffer into the kernel. That's what I did. Graphics support: [*] Support for frame buffer devices * VESA VGA graphics support VESA driver type (vesafb-tng) --- ([EMAIL PROTECTED]) VESA default mode Then my grub is simply: timeout 30 default 0 title Gentoo Latest root (hd0,0) kernel (hd0,0)/boot/vmlinuz root=/dev/sda3 HTH, Roy Iain Buchanan wrote: On Thu, 2005-06-30 at 11:09 -0500, LostSon wrote: Hello I am trying to set my framebuffer so at boot time i get 1024x768 i am not using a splash screen just want the terminal at 1024x768, i have read the tutorial and compiled in all the components i need but jsut cant get it to work my grub.conf looks like this title=Gentoo-2.6.11-r11-boot-1024 root (hd0,0) kernel (hd0,0)/boot/bzImage.new3 root=/dev/hda3 video=vesafb:[EMAIL PROTECTED] -- gentoo-user@gentoo.org mailing list
Re: [gentoo-user] framebuffer questions
I guess Roy's solution would be the best for you since you dont plan on using any splash screen or graphic candy, it would put your console to 1024x768 and you wouldn't have to worry about anything. (be careful if your monitor supports the resolution and specially the refresh rate). On 6/30/05, Roy Wright [EMAIL PROTECTED] wrote: Another option is to just compile the framebuffer into the kernel. That's what I did. Graphics support: [*] Support for frame buffer devices * VESA VGA graphics support VESA driver type (vesafb-tng) --- ([EMAIL PROTECTED]) VESA default mode Then my grub is simply: timeout 30 default 0 title Gentoo Latest root (hd0,0) kernel (hd0,0)/boot/vmlinuz root=/dev/sda3 HTH, Roy Iain Buchanan wrote: On Thu, 2005-06-30 at 11:09 -0500, LostSon wrote: Hello I am trying to set my framebuffer so at boot time i get 1024x768 i am not using a splash screen just want the terminal at 1024x768, i have read the tutorial and compiled in all the components i need but jsut cant get it to work my grub.conf looks like this title=Gentoo-2.6.11-r11-boot-1024 root (hd0,0) kernel (hd0,0)/boot/bzImage.new3 root=/dev/hda3 video=vesafb:[EMAIL PROTECTED] -- gentoo-user@gentoo.org mailing list -- Daniel da Veiga Computer Operator - RS - Brazil -- gentoo-user@gentoo.org mailing list
Re: [gentoo-user] framebuffer questions
Check that looked over by grub.conf and i had the wrong bzImage in there sorry to disturb you. On Thu, 2005-06-30 at 20:42 -0500, LostSon wrote: I have done everything you have suggested and still nothing On Thu, 2005-06-30 at 21:54 -0300, Daniel da Veiga wrote: I guess Roy's solution would be the best for you since you dont plan on using any splash screen or graphic candy, it would put your console to 1024x768 and you wouldn't have to worry about anything. (be careful if your monitor supports the resolution and specially the refresh rate). On 6/30/05, Roy Wright [EMAIL PROTECTED] wrote: Another option is to just compile the framebuffer into the kernel. That's what I did. Graphics support: [*] Support for frame buffer devices * VESA VGA graphics support VESA driver type (vesafb-tng) --- ([EMAIL PROTECTED]) VESA default mode Then my grub is simply: timeout 30 default 0 title Gentoo Latest root (hd0,0) kernel (hd0,0)/boot/vmlinuz root=/dev/sda3 HTH, Roy Iain Buchanan wrote: On Thu, 2005-06-30 at 11:09 -0500, LostSon wrote: Hello I am trying to set my framebuffer so at boot time i get 1024x768 i am not using a splash screen just want the terminal at 1024x768, i have read the tutorial and compiled in all the components i need but jsut cant get it to work my grub.conf looks like this title=Gentoo-2.6.11-r11-boot-1024 root (hd0,0) kernel (hd0,0)/boot/bzImage.new3 root=/dev/hda3 video=vesafb:[EMAIL PROTECTED] -- gentoo-user@gentoo.org mailing list -- Daniel da Veiga Computer Operator - RS - Brazil -- LostSon http://www.lostsonsvault.org Public Key http://www.lostsonsvault.org/dls/lostson.asc signature.asc Description: This is a digitally signed message part
[gentoo-user] Framebuffer versus X
I admit to knowing nothing about framebuffer, which is why I'm asking all these questions. Can a viable Gentoo system with gnumeric, gimp, etc, be built on a framebuffer-only system? Can framebuffer co-exist with X? -- Walter Dnes [EMAIL PROTECTED] My musings on technology and security at http://tech_sec.blog.ca -- gentoo-user@gentoo.org mailing list
Re: [gentoo-user] FrameBuffer + Splash Startx
On Thu, 2005-04-28 at 03:52 +0800, Ow Mun Heng wrote: It seems that on 2005.0 install, I can't have the 3 of these together like I did when I was running on 2004.3. The difference is the usage of devpts vs udev. Since 2005.0 is udev, to get gen/fbsplash to work, I need to pass vga=7xx to the kernel command line. passing video=vesafb:ywrap,[EMAIL PROTECTED] splash=silent,theme:livecd-2005.0 doesn't seem to have any effect at all. I've tried both vesafb as well as using vesafb-tng and both fails. With VGA=7xx passed, I get splash but Freevo won't come up. (and neither will startx work) as it complains about not being able to find DISPLAY and default to using fbdev. (On occations in which it does comes up it doesn't stretch the display to fullscreen!) Without the VGA=7xx line, then I don't get the splash screen at all but freevo will start with no issues. The other thing is that startx will also fail for the same reason. Doesn't anyone has any idea at all?? -- Ow Mun Heng Gentoo/Linux on DELL D600 1.4Ghz 98% Microsoft(tm) Free!! Neuromancer 17:41:37 up 2 days, 8:22, 6 users, load average: 0.87, 0.88, 0.59 -- gentoo-user@gentoo.org mailing list
