On Wed, May 18, 2011 at 5:57 AM, 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
>
>
HTH,
Mark
c2
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 :
> On Wed, May 18, 2011 at 03:10:02PM +0200, JDM wrote:
>> Genthinktank,
>> How c
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 "
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
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 l
> 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 O the machine
> (it's unresponsive to {R,S,E,I,K,U}).
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 O the machine
(it's unresponsive to {R,S,E,I,K,U}).
I have th
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 t
> 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
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 v
> 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
> 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 inste
> 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 o
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 12
--- 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 e
> 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
> have you tried with just '1280x1024' ?
No help
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-6
On Sun, 3 Jun 2007 11:04:22 -0700 (PDT)
maxim wexler <[EMAIL PROTECTED]> wrote:
> > 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]
>
> 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
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=1&chap=10
>
> That gives the best explanation. Now dmesg | grep -i
> vesa concludes with:
> <...>
> vesafb: framebuffer at
> also, gentoo has a doc:
>
http://www.gentoo.org/doc/en/handbook/handbook-x86.xml?part=1&chap=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.
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 unde
> 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 conso
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 l
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
> 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 o
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 m
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, Har
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 possibil
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 solutio
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 hav
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, Ro
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 defau
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
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-102
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 h
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=
37 matches
Mail list logo
