On Thu, 17 Jul 2014 01:36:07 -0400 (EDT), Sven Joachim wrote:
>
> I don't think there's a linux16 command on sparc, for lack of x86 real
> mode.
> ...
> There is no lilo for sparc since lilo is written in x86 assembly.
You are absolutely right. Somehow, I missed the fact that he was using
sparc.
On 2014-07-17 07:57 +0200, Dennis Luehring wrote:
> Am 17.07.2014 07:36, schrieb Sven Joachim:
>> I don't think there's a linux16 command on sparc, for lack of x86 real
>> mode.
>
> does that mean vga=ask is an x86 only feature?
According to Documentation/kernel-pa
Hi.
On Thu, Jul 17, 2014 at 07:57:39AM +0200, Dennis Luehring wrote:
> Am 17.07.2014 07:36, schrieb Sven Joachim:
> >I don't think there's a linux16 command on sparc, for lack of x86 real
> >mode.
>
> does that mean vga=ask is an x86 only feature?
It depends
Am 17.07.2014 07:36, schrieb Sven Joachim:
I don't think there's a linux16 command on sparc, for lack of x86 real
mode.
does that mean vga=ask is an x86 only feature?
or does https://wiki.debian.org/GrubTransitionjust just ignores
non x86 systems by giving the advice to use linux
; textmode works) so i want to
>> try using the vga=ask boot parameter if there is a working framebuffer
>> variant
>>
>> but the vga=ask parameter seems to be deprecated - is there any other
>> parameter i can try?
>>
>> after qemus OpenBios boot
On Wed, 16 Jul 2014 03:41:26 -0400 (EDT), Dennis Luehring wrote:
>
> i try to install an qemu-sparc version of debian wheezy 7.6 (dvd-iso)
> the qemu graphics emulation is not full ready yet (freezing very early,
> textmode works) so i want to
> try using the vga=ask boot paramete
i try to install an qemu-sparc version of debian wheezy 7.6 (dvd-iso)
the qemu graphics emulation is not full ready yet (freezing very early,
textmode works) so i want to
try using the vga=ask boot parameter if there is a working framebuffer
variant
but the vga=ask parameter seems to be
On 5/21/2013 2:20 PM, Sven Joachim wrote:
> On 2013-05-21 04:03 +0200, Stan Hoeppner wrote:
>
>> On 5/20/2013 4:30 AM, Sven Joachim wrote:
>>> MIPS and ARM machines don't have a traditional BIOS either,
>>
>> Yes, that was my point. You'll probably never see UEFI on these
>> platforms. So LILO
On 2013-05-21 04:03 +0200, Stan Hoeppner wrote:
> On 5/20/2013 4:30 AM, Sven Joachim wrote:
>> MIPS and ARM machines don't have a traditional BIOS either,
>
> Yes, that was my point. You'll probably never see UEFI on these
> platforms. So LILO could be used basically forever.
Hardly, because L
>
> >> Another note, GRUB2 is more similar to Lilo than you think.
> >
> > They're both boot loaders. Of course they're similar. But they have
> > some serious differences. Serious enough that many folks, such as
> > myself, choose to stick with LILO.
>
> Good luck in patching LILO to work
8 has flopped. There are no [note|net]book
computers shipping with 2TB+ 2.5" or 1.8" drives, so this is a non
issue. Is anyone even making a 2TB+ 2.5" drive? Last I checked the
largest on the market is 1TB.
>> UEFI is little endian only and will never be usable on some emb
On Mon, 20 May 2013 02:48:55 -0400 (EDT), Sven wrote:
>
> Good luck in patching LILO to work without a BIOS.
It is true that lilo requires a BIOS interface. However, many
EFI/UEFI machines also provide a BIOS for forward compatibility;
so lilo may still work.
However, for those EFI/UEFI machine
On Sun, 19 May 2013 23:15:54 -0400 (EDT), Dirk wrote:
>
> but... i ask myself: /why/ i am supposed to read and memorize all this
> when even /lilo/ is still working...?
>
> lilo, then grub, then grub2... no real change in functionality... a
> kernel gets booted.. that's it... but all three func
to get 80x50
> text consoles instead of framebuffer. You may also replace ext by F00,
> F01, F02, F03, F05, F06 or F07 to get alternate VGA text resolutions
> (respectively 80x25, 80x50, 80x43, 80x28, 80x30, 80x34 and 80x60). Use
> vga=ask to get a chance at boot time to list
aditional BIOS - people want to be able to use hard disks
bigger than 2 TiB under Windows.
> UEFI is little endian only and will never be usable on some embedded
> RISC processor platforms. Linux will be required to support many
> different flavors of system board firmware now and into the di
On 5/20/2013 1:48 AM, Sven Joachim wrote:
> On 2013-05-20 07:26 +0200, Stan Hoeppner wrote:
>
>> On 5/19/2013 11:04 PM, staticsafe wrote:
>>
>>> The Debian developers (and many other distros) have chosen to put their
>>> support behind GRUB2 which allows for (please correct me, if I'm wrong)
>>> f
On 2013-05-20 07:26 +0200, Stan Hoeppner wrote:
> On 5/19/2013 11:04 PM, staticsafe wrote:
>
>> The Debian developers (and many other distros) have chosen to put their
>> support behind GRUB2 which allows for (please correct me, if I'm wrong)
>> features like UEFI support and better support for au
On Mon, 2013-05-20 at 00:26 -0500, Stan Hoeppner wrote:
> They're both boot loaders. Of course they're similar. But they have
> some serious differences. Serious enough that many folks, such as
> myself, choose to stick with LILO. If I had to come up with one word to
> describe today's LILO use
On 5/19/2013 11:04 PM, staticsafe wrote:
> You can use Lilo if you so choose,
I do.
> but don't expect integration
> (specifically kernel package installation scripts).
I don't. I roll my own kernels sans initrd. lilo in MBR, vmlinuz in
ext2 /boot partition.
> The Debian developers (and ma
On Mon, May 20, 2013 at 05:15:54AM +0200, Dirk wrote:
> On 05/20/13 04:57, staticsafe wrote:
> >On Mon, May 20, 2013 at 02:59:43AM +0200, Dirk wrote:
> >>hello,
> >>
> >>do I see that right that vga=ask has been removed in grub2 without
> >>offe
On 05/20/13 04:57, staticsafe wrote:
On Mon, May 20, 2013 at 02:59:43AM +0200, Dirk wrote:
hello,
do I see that right that vga=ask has been removed in grub2 without
offering a working replacement? because all those gfxpayload=bla bs
i found online surely doesn't work...
so i reverted to
On Mon, May 20, 2013 at 02:59:43AM +0200, Dirk wrote:
> hello,
>
> do I see that right that vga=ask has been removed in grub2 without
> offering a working replacement? because all those gfxpayload=bla bs
> i found online surely doesn't work...
>
> so i reverted to g
On Mon, 20 May 2013 02:59:43 +0200
Dirk wrote:
> hello,
>
> do I see that right that vga=ask has been removed in grub2 without
> offering a working replacement? because all those gfxpayload=bla bs i
> found online surely doesn't work...
>
> so i reverted to g
On Mon, May 20, 2013 at 02:59:43AM +0200, Dirk wrote:
> hello,
>
> do I see that right that vga=ask has been removed in grub2 without
> offering a working replacement? because all those gfxpayload=bla bs
> i found online surely doesn't work...
what branch of debian do you us
hello,
do I see that right that vga=ask has been removed in grub2 without
offering a working replacement? because all those gfxpayload=bla bs i
found online surely doesn't work...
so i reverted to grub-legacy...
doesn't anybody check the crap that makes it into debian anymore?
be
Ragga Muffin wrote:
> Have you tried the svgatextmode package ?
I actually just downloaded it and installed it at another person's
reccommendation. It will suffice. Thanks.
A. Scott White
Director of Information Systems and Product Strategy
ACS
Subject: vga=ask
Date: Thu, Jun 01, 2000 at 10:38:02PM -0500
In reply to:A. Scott White
Quoting A. Scott White([EMAIL PROTECTED]):
> I've set vga=ask in my lilo.conf and run lilo.
>
> I've specified the kernel image along with the command line vga=auto a
"A. Scott White" wrote:
> I want to use a different vga text mode (like 80x50) on my terminal. I do
> not like to use X Windows, it is too slow. I prefer to use the standard,
> text based terminal. I want, however, to be able to see more text on the
> screen at one time.
Have you tried the svgat
On Fri, Jun 02, 2000 at 11:20:11AM -0500, A. Scott White wrote:
> Jo wrote:
> > A full screen console (no X), is that what you want?
> > If so check out framebuffer. There is an HOWTO on it.
> > Jo
>
> I want to use a different vga text mode (like 80x50) on my terminal. I do
> not like to use X Wi
On Fri, Jun 02, 2000 at 09:39:22AM -0500, A. Scott White wrote:
> > I've set vga=ask in my lilo.conf and run lilo.
> >
> > I've specified the kernel image along with the command line
> > vga=auto at the
> > lilo prompt.
I set vga=ask in my lilo.conf gl
Jo wrote:
> A full screen console (no X), is that what you want?
> If so check out framebuffer. There is an HOWTO on it.
> Jo
I want to use a different vga text mode (like 80x50) on my terminal. I do
not like to use X Windows, it is too slow. I prefer to use the standard,
text based terminal. I wa
> > I've set vga=ask in my lilo.conf and run lilo.
> >
> > I've specified the kernel image along with the command line
> > vga=auto at the
> > lilo prompt.
> >
> > I've run rdev -v \boot\vmlinuz-2.2.15 -3
> >
> > I've run
on from my kernel or something?
Thanks.
> I've set vga=ask in my lilo.conf and run lilo.
>
> I've specified the kernel image along with the command line
> vga=auto at the
> lilo prompt.
>
> I've run rdev -v \boot\vmlinuz-2.2.15 -3
>
> I've run vidmode
"A. Scott White" wrote:
>
> I've set vga=ask in my lilo.conf and run lilo.
>
> I've specified the kernel image along with the command line vga=auto at the
> lilo prompt.
>
> I've run rdev -v \boot\vmlinuz-2.2.15 -3
>
> I've run vidmode
I've set vga=ask in my lilo.conf and run lilo.
I've specified the kernel image along with the command line vga=auto at the
lilo prompt.
I've run rdev -v \boot\vmlinuz-2.2.15 -3
I've run vidmode \boot\vmlinuz-2.2.15 -3
I have also tried all of the above with "extended&q
Hi Andy,
The VGA stuff is kernel-based. SVGATextMode is a program that you can load
after the kernel's loaded to use SVGA instead of VGA.
So generally the answer to your question is, yes. However, you can use the
SVGA stuff to get higher resolutions also.
Personally, I don't use the SVGATextM
Hi,
It's when it gets to "Invoking SVGATextMode..." on bootup that it switches
back to 80x25. Is "svgatextmode" some sort of driver I should unload in
order to get this to "stick?"
Thanks
Andy
ose"). Once
> it "crashed the video" (after choosing something like 132 x something
> mode)... another time I chose 80x50 and it went that way for awhile, then
> reverted to 80x25. Most of the time though the menu never comes up at all
> during boot.
Not sure what's
132 x something
mode)... another time I chose 80x50 and it went that way for awhile, then
reverted to 80x25. Most of the time though the menu never comes up at all
during boot.
vga=ask was indicated as an option by the O'Reilly book.
TIA for any insight into this.
Andy
-BEGIN PGP SIGNED MESSAGE-
This may be a stupid question, but, are you typing make *config in the
"/usr/src/linux" directory? It doesn't work in any other directory. If
you are then you should replace your kernel source files because somthin
aint right.
On 05-Apr-97 Nikolaj Richers wrot
Hello Douglas and Carey,
On 03-Apr-97, Douglas L Stewart wrote
>On 4 Apr 1997, Carey Evans wrote:
>> APM support can be in a 2.0.27 kernel if it's compiled in.
>> Recompiling your kernel isn't too bad, if you make sure you have all
>> the information about all your hardware and use "make menuconf
On 4 Apr 1997, Carey Evans wrote:
> APM support can be in a 2.0.27 kernel if it's compiled in.
> Recompiling your kernel isn't too bad, if you make sure you have all
> the information about all your hardware and use "make menuconfig" or
> "make xconfig". make-kpkg is supposed to make it easier to
> > I do have one question about /lilo.conf/: I'd like Linux to use 480
> > pixels vertically rather than the 400 scans it seems to use by default.
> > So I read and read and read, and eventually came accross the 'vga=ask'
> > entry for lilo.conf. Only, it
Nikolaj Richers <[EMAIL PROTECTED]> writes:
> I do have one question about /lilo.conf/: I'd like Linux to use 480
> pixels vertically rather than the 400 scans it seems to use by default.
> So I read and read and read, and eventually came accross the 'vga=ask'
&
rtically rather than the 400 scans it seems to use by default.
So I read and read and read, and eventually came accross the 'vga=ask'
entry for lilo.conf. Only, it doesn't ask anything, just boots
up as it usually would, at 400 scans. Is this broken or am I missing
an obvious st
45 matches
Mail list logo
