Matthew Moore wrote:
> On Saturday February 6 2010 2:36:02 pm Γιώργος Πάλλας wrote:
>
>> So I removed vga=791 and problems with getting a console were resolved.
>>
>> In order to have a good resolution for my console while the pc is
>> booting, I used the
>>
he problem was the
> 'vga=791' setting that I used to boot with, so that I have a decent
> resolution while booting, for the kernel messages.
>
> So I removed vga=791 and problems with getting a console were resolved.
>
> In order to have a good resolution for my
Γιώργος Πάλλας:
>
> In order to have a good resolution for my console while the pc is
> booting, I used the
> GRUB_GFXMODE=1440x900 directive in the grub2 config,
That only sets the resolution for the boot manager. To enable KMS at
boot time, add 'video=i915:modeset=1' to the kernel command line.
On Saturday February 6 2010 2:36:02 pm Γιώργος Πάλλας wrote:
> So I removed vga=791 and problems with getting a console were resolved.
>
> In order to have a good resolution for my console while the pc is
> booting, I used the
> GRUB_GFXMODE=1440x900 directive in the grub2 confi
Hi to all!
After I upgraded last week to latest xorg drivers my squeeze box, I had
problem getting a console: the X session just froze. I searched a bit
and found bug #567563. So I discovered that the problem was the
'vga=791' setting that I used to boot with, so that I have a decent
l, e.g. in order to
install uvesfb you have to do that.
The last Debian kernel that ran with vga=791 was 2.6.24. So I did a diff
-y beteen that and 2.6.25 that does *not* allow vga=791. That file is
here:
http://www.geocities.com/hugovanwoerkom/config-24-25-diff.txt
The only seemingly-relevant ch
to
install uvesfb you have to do that.
The last Debian kernel that ran with vga=791 was 2.6.24. So I did a diff
-y beteen that and 2.6.25 that does *not* allow vga=791. That file is here:
http://www.geocities.com/hugovanwoerkom/config-24-25-diff.txt
The only seemingly-relevant change I see is to
> From: David Witbrodt <[EMAIL PROTECTED]>
> To: Hugo Vanwoerkom <[EMAIL PROTECTED]>
> Sent: Saturday, August 2, 2008 11:41:47 AM
> Subject: Re: [!] 2.6.26 + vga=791
>
>
>
> > David Witbrodt wrote:
> > >>> So now I have to go item by i
David Witbrodt wrote:
- Forwarded Message
From: David Witbrodt <[EMAIL PROTECTED]>
To: Hugo Vanwoerkom <[EMAIL PROTECTED]>
Sent: Friday, August 1, 2008 10:34:51 PM
Subject: Re: [!] 2.6.26 + vga=791
But I did something interesting: I recompiled 2.6.26-1-686 but changed
On 08/01/08 21:35, David Witbrodt wrote:
- Forwarded Message
From: David Witbrodt <[EMAIL PROTECTED]>
To: Hugo Vanwoerkom <[EMAIL PROTECTED]>
Sent: Friday, August 1, 2008 10:34:51 PM
Subject: Re: [!] 2.6.26 + vga=791
[snip]
I use that after I compile my new kernels
- Forwarded Message
> From: David Witbrodt <[EMAIL PROTECTED]>
> To: Hugo Vanwoerkom <[EMAIL PROTECTED]>
> Sent: Friday, August 1, 2008 10:34:51 PM
> Subject: Re: [!] 2.6.26 + vga=791
>
>
>
> > But I did something interesting: I recompiled 2
Hugo Vanwoerkom wrote:
Hi,
I reported here on 5/18/2008 that I couldn't use vga=791 with the Debian
2.6.25 kernel, but *could* with the 2.6.25 from kernel.org.
Same issue with 2.6.26: vga=791 gets "undefined video mode". Yet it
works fine with 2.6.26 from kernel.org, so
On Thu, Jul 31, 2008 at 10:02:43AM -0500, Hugo Vanwoerkom wrote:
> Hi,
>
> I reported here on 5/18/2008 that I couldn't use vga=791 with the Debian
> 2.6.25 kernel, but *could* with the 2.6.25 from kernel.org.
Works here - stock Debian kernel:
[EMAIL PROTECTED]:~# uname -a
L
Hugo Vanwoerkom wrote:
David Witbrodt wrote:
And I tried vga=0x0317 and get "undefined videomode".
Bummer. Just for sanity's sake, did you try "vga=0x317"?
Yes. Same error.
But I did something interesting: I downloaded
http://cdimage.debian.org/cdimage/daily-builds/sid_d-i/arch-lates
David Witbrodt wrote:
And I tried vga=0x0317 and get "undefined videomode".
Bummer. Just for sanity's sake, did you try "vga=0x317"?
Yes. Same error.
But I did something interesting: I downloaded
http://cdimage.debian.org/cdimage/daily-builds/sid_d-i/arch-latest/i386/iso-cd/debian-tes
> And I tried vga=0x0317 and get "undefined videomode".
Bummer. Just for sanity's sake, did you try "vga=0x317"?
Dave W.
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Javier Vasquez wrote:
On Thu, Jul 31, 2008 at 9:32 AM, David Witbrodt <[EMAIL PROTECTED]> wrote:
I reported here on 5/18/2008 that I couldn't use vga=791 with the Debian
2.6.25 kernel, but *could* with the 2.6.25 from kernel.org.
Same issue with 2.6.26: vga=791 gets "undefined
David Witbrodt wrote:
I reported here on 5/18/2008 that I couldn't use vga=791 with the Debian
2.6.25 kernel, but *could* with the 2.6.25 from kernel.org.
Same issue with 2.6.26: vga=791 gets "undefined video mode". Yet it
works fine with 2.6.26 from kernel.org, so
On Thu, Jul 31, 2008 at 9:32 AM, David Witbrodt <[EMAIL PROTECTED]> wrote:
>
>> I reported here on 5/18/2008 that I couldn't use vga=791 with the Debian
>> 2.6.25 kernel, but *could* with the 2.6.25 from kernel.org.
>>
>> Same issue with 2.6.26: vga=791 gets &
On Thu, Jul 31, 2008 at 10:02:43 -0500, Hugo Vanwoerkom ([EMAIL PROTECTED])
wrote:
> Hi,
>
> I reported here on 5/18/2008 that I couldn't use vga=791 with the Debian
> 2.6.25 kernel, but *could* with the 2.6.25 from kernel.org.
>
> Same issue with 2.6.26: vga=791 get
> I reported here on 5/18/2008 that I couldn't use vga=791 with the Debian
> 2.6.25 kernel, but *could* with the 2.6.25 from kernel.org.
>
> Same issue with 2.6.26: vga=791 gets "undefined video mode". Yet it
> works fine with 2.6.26 from kernel.org, s
Hi,
I reported here on 5/18/2008 that I couldn't use vga=791 with the Debian
2.6.25 kernel, but *could* with the 2.6.25 from kernel.org.
Same issue with 2.6.26: vga=791 gets "undefined video mode". Yet it
works fine with 2.6.26 from kernel.org, so it is clearly a Debian is
> >>>> In installing linux-image-2.6.25-1-686 I find I can no longer use
> >>>> vga=791 on the kernel commandline. I get "undefined videomode number:
> >>>> 317" that's 791 hex.
Here's something funny:
I just saw this erro
David Witbrodt wrote:
On Mon, May 12, 2008 at 08:39:20PM +0200, Gilles Mocellin wrote:
Le Monday 12 May 2008 15:52:15 Hugo Vanwoerkom, vous avez écrit :
Hi,
In installing linux-image-2.6.25-1-686 I find I can no longer use
vga=791 on the kernel commandline. I get "undefined videomode n
David Witbrodt wrote:
On Mon, May 12, 2008 at 08:39:20PM +0200, Gilles Mocellin wrote:
Le Monday 12 May 2008 15:52:15 Hugo Vanwoerkom, vous avez écrit :
Hi,
In installing linux-image-2.6.25-1-686 I find I can no longer use
vga=791 on the kernel commandline. I get "undefined videomode n
> On Mon, May 12, 2008 at 08:39:20PM +0200, Gilles Mocellin wrote:
> > Le Monday 12 May 2008 15:52:15 Hugo Vanwoerkom, vous avez écrit :
> > > Hi,
> > >
> > > In installing linux-image-2.6.25-1-686 I find I can no longer use
> > > vga=791 on the k
On Mon, May 12, 2008 at 08:52:15AM -0500, Hugo Vanwoerkom wrote:
>
From my machine :
$ uname -a
Linux brahman 2.6.25-mas #2 SMP PREEMPT Sat Apr 19 07:43:57 IST 2008 i686
GNU/Linux
Using vga=795 on my system.
> In installing linux-image-2.6.25-1-686 I find I can no longer use
> v
On Mon, May 12, 2008 at 08:39:20PM +0200, Gilles Mocellin wrote:
> Le Monday 12 May 2008 15:52:15 Hugo Vanwoerkom, vous avez écrit :
> > Hi,
> >
> > In installing linux-image-2.6.25-1-686 I find I can no longer use
> > vga=791 on the kernel commandline. I get "und
Le Monday 12 May 2008 15:52:15 Hugo Vanwoerkom, vous avez écrit :
> Hi,
>
> In installing linux-image-2.6.25-1-686 I find I can no longer use
> vga=791 on the kernel commandline. I get "undefined videomode number:
> 317" that's 791 hex.
>
> I've been using
Hi,
In installing linux-image-2.6.25-1-686 I find I can no longer use
vga=791 on the kernel commandline. I get "undefined videomode number:
317" that's 791 hex.
I've been using vga=791 on kernels since time immemorial, what's wrong
with it now?
There is an alte
Hugo Vanwoerkom wrote:
Hugo Vanwoerkom wrote:
Hi,
I tried out the Etch beta1 installer.
Got some problems.
Grub screen is blank on the reboot, making reboot impossible.
Filed a bug report (342570).
Other than that:
In Sarge I could add vga=791 to the boot parameters and get fbcon.
That no
Hugo Vanwoerkom wrote:
Hi,
I tried out the Etch beta1 installer.
Got some problems.
Grub screen is blank on the reboot, making reboot impossible.
Filed a bug report (342570).
Other than that:
In Sarge I could add vga=791 to the boot parameters and get fbcon.
That no longer works: vga=791 now
Hi,
I tried out the Etch beta1 installer.
Got some problems.
Grub screen is blank on the reboot, making reboot impossible.
Filed a bug report (342570).
Other than that:
In Sarge I could add vga=791 to the boot parameters and get fbcon.
That no longer works: vga=791 now gets a blank screen
On Tue, Jan 21, 2003 at 05:04:09PM +, T. Beauregard wrote:
> Is this the memory error that GrUB 0.91 gives? This is resolved in 0.93.
>
It works.
Thanks,
--
Sridhar M.A.
She often gave herself very good advice (though she very seldom followed it).
-- Lewis Carroll
On Tue, Jan 21, 2003 at 05:04:09PM +, T. Beauregard wrote:
> Is this the memory error that GrUB 0.91 gives? This is resolved in 0.93.
>
> > Given a chance, I would like to use grub, but I _cannot_ with my present
> > motherboard :-(
>
Yes. Thanks for the info. I will try upgra
Is this the memory error that GrUB 0.91 gives? This is resolved in 0.93.
Tim
Sridhar M.A. wrote:
> Given a chance, I would like to use grub, but I _cannot_ with my present
> motherboard :-(
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAI
On Tue, Jan 21, 2003 at 08:20:52AM +1300, Haralambos Geortgilakis wrote:
>
>
>
> just change it too
>
> vga=791
>
> for each option you want too; no append statement is needed.
>
That did it. Somehow I missed that :-( Removed the append
Hi Yall & Sridhar,
just change it too
vga=791
for each option you want too; no append statement is needed.
That way, you can have multiple resolutions available @ boot time.
Well, try it with one & see how that goes. The above is how I work mine :-)
*BFN*
H :-)
Arrogant dragon w
itmap=/boot/ins64a.bmp
> bmp-colors=14,11,,15,9,0
> bmp-table=21,287p,2,4,175p
> bmp-timer=73,29,12,8,0
>
> default="deb"
> lba32
> prompt
> timeout=1200
>
> image=/vmlinuz
> label="deb"
> root=/dev/hda3
> append=&qu
On approximately Mon, Jan 20, 2003 at 09:29:20PM +0530, Sridhar M.A. wrote:
> I am facing a peculiar problem while booting with a kernel which has
> framebuffer support.
>
> My lilo.conf is as follows:
>
> root=/dev/hda
> map=/boot/map
> install=/boot/boot-bmp.
default="deb"
lba32
prompt
timeout=1200
image=/vmlinuz
label="deb"
root=/dev/hda3
append="vga=791"
read-only
image=/vmlinuz.old
label="old"
root=/dev/hda3
append="vga=791"
read-only
image=/boot/vmlinuz-2.4.19-
text screen coming up in 640x480 (as
> reported by fbset) when I have "vga=791" set in /boot/grub/menu.lst? I
> started off with the line:
>kopt=vga=791 root=/dev/hda2 ro
> but when that didn't work I added the "vag=" to my boot stanza, like so:
>kernel
and then re-ran lilo. After that I was able to boot just fine, but now a
penguin graphic shows up in the top left corner during the boot process.
What's generating that?
More importantly, why is my text screen coming up in 640x480 (as
reported by fbset) when I have "vga=791" set in
Hi all,
how can I enable the framebuffer (it is only compiled as a module in
the standard kernel (image)) with vga=791 in Lilo for Debian potato
2.2r5 with Kernel 2.2.18pre21 without compiling the kernel again/on
myself?
Oliver
--
... don't touch the bang-bang fruit ...
--
To UNSUBS
On Tue, 31 Oct 2000, Frederik wrote:
-|-BEGIN PGP SIGNED MESSAGE-
-|Hash: SHA1
-|
-|On Tue, 31 Oct 2000, Christopher W. Aiken wrote:
-|
-|> what I'm talking about? Can anyone point me to the "light"
-|> on what needs to be added to the kernel?
-|>
-|I think you might need framebuffer sup
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Tue, 31 Oct 2000, Christopher W. Aiken wrote:
> what I'm talking about? Can anyone point me to the "light"
> on what needs to be added to the kernel?
>
I think you might need framebuffer support. It's one of the last options
in the kernel configu
I may have posted this before, but for the life of me,
I can't find iti, or if there was any responses to my question.
In Rh/SuSE/Slack I can add "vga=791" to my /etc/lilo.conf
file, re-run lilo, and when I re-boot my system I get
smaller text and much more info in my text consol
47 matches
Mail list logo
