Re: set boot parameter vga=ask before debian wheezy 7.6 dvd install
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. I didn't read the original post carefully enough. Sorry for the noise. -- .''`. Stephen Powell : :' : `. `'` `- -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/2063192006.67305.1405726263299.javamail.r...@md01.wow.synacor.com
Re: set boot parameter vga=ask before debian wheezy 7.6 dvd install
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 on grub-legacy, that's for sure. or does https://wiki.debian.org/GrubTransitionjust just ignores non x86 systems by giving the advice to use linux16? would grub-legacy linux work? In a way, it does. Grub-legacy is x86 only. Grub2 can be used on non-x86, but on those platforms it's customary to use another bootloaders (yaboot for example). So, it's assumed that one uses grub2 = one uses x86. Reco -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/20140717060811.GA15266@x101h
Re: set boot parameter vga=ask before debian wheezy 7.6 dvd install
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-parameters.txt, vga=… is x86 only: , | vga= [BOOT,X86-32] Select a particular video mode | See Documentation/x86/boot.txt and | Documentation/svga.txt. | Use vga=ask for menu. | This is actually a boot loader parameter; the value is | passed to the kernel using a special protocol. ` or does https://wiki.debian.org/GrubTransitionjust just ignores non x86 systems by giving the advice to use linux16? It can do so, since grub1 aka grub-legacy is x86 only. Sparc used silo instead, I think the current default bootloader is grub-ieee1275 there. Cheers, Sven -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/87zjg8lcsy@turtle.gmx.de
set boot parameter vga=ask before debian wheezy 7.6 dvd install
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 deprecated - is there any other parameter i can try? after qemus OpenBios boot i can see debians install prompt boot: asking for ENTER=install, resuce or expert mode - what do i need to type in booting the dvd iso kernel with parameters? thx -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/53c62ca6.60...@gmx.net
Re: set boot parameter vga=ask before debian wheezy 7.6 dvd install
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 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 i can see debians install prompt boot: asking for ENTER=install, resuce or expert mode - what do i need to type in booting the dvd iso kernel with parameters? I'm guessing that you are using grub2 as your boot loader. To use the vga option with grub2, you have to use the linux16 command (and the corresponding initrd16 command) instead of the linux and initrd commands, respectively. See https://wiki.debian.org/GrubTransition for details, particularly the footnote at the bottom of the page. I use lilo as my boot loader. See http://users.wowway.com/~zlinuxman/lilo.htm for details. -- .''`. Stephen Powell : :' : `. `'` `- -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/2040072396.50857.1405552934292.javamail.r...@md01.wow.synacor.com
Re: set boot parameter vga=ask before debian wheezy 7.6 dvd install
On 2014-07-17 01:22 +0200, Stephen Powell wrote: 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 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 i can see debians install prompt boot: asking for ENTER=install, resuce or expert mode - what do i need to type in booting the dvd iso kernel with parameters? I'm guessing that you are using grub2 as your boot loader. To use the vga option with grub2, you have to use the linux16 command (and the corresponding initrd16 command) instead of the linux and initrd commands, respectively. See https://wiki.debian.org/GrubTransition for details, particularly the footnote at the bottom of the page. I don't think there's a linux16 command on sparc, for lack of x86 real mode. I use lilo as my boot loader. See http://users.wowway.com/~zlinuxman/lilo.htm for details. There is no lilo for sparc since lilo is written in x86 assembly. Cheers, Sven -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/87ha2gmtrs@turtle.gmx.de
Re: set boot parameter vga=ask before debian wheezy 7.6 dvd install
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 linux16? would grub-legacy linux work? -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/53c765d3.7040...@gmx.net
Re: vga=ask doesn't work anymore
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 without a BIOS. There is ELILO in Debian. It is not in the installer, but I suppose they can switch to elilo or port it's UEFI code to lilo. -- Unfortunately, looks like Orwell was not to pessimistic after all. -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/519b5ef2.9050...@mail.ru
Re: vga=ask doesn't work anymore
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 LILO depends on a BIOS. And it's written in x86 assembly, so not even buildable on these architectures. As for UEFI - we'll see what the future holds. Cheers, Sven -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/87a9no6syg@turtle.gmx.de
Re: vga=ask doesn't work anymore
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 could be used basically forever. Hardly, because LILO depends on a BIOS. And it's written in x86 assembly, so not even buildable on these architectures. Note I made the point, before you, that MIPS and ARM are different beasts. The point I was making above is that grub2 will never be universal for all Linux platforms, thus there's no need for all distros to use only grub2 for x86. And since there are no LILO/Linux limitations on x86, LILO could be used basically forever. As for UEFI - we'll see what the future holds. Yes, this will be interesting to watch. What we'll see in the immediate future is more mobos with switchable UEFI/legacy BIOS support. Whether UEFI will completely takeover is the question, and if so, when? -- Stan -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/519bf6d8.5020...@hardwarefreak.com
Re: vga=ask doesn't work anymore
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 automation. It's an odd play for Debian to get behind UEFI It's not really Debian's choice, the world is finally giving up on the BIOS and your next machine might very well not provide such an interface anymore. which includes secure boot, and includes other features that tend to take control of the machine away from the user. That's not freedom. Debian does not support secure boot as of now, and whether secure boot restricts or enhances user freedom depends on your ability to install your own keys. 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 without a BIOS. Cheers, Sven -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/87vc6ejgdk@turtle.gmx.de
Re: vga=ask doesn't work anymore
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) features like UEFI support and better support for automation. It's an odd play for Debian to get behind UEFI It's not really Debian's choice, the world is finally giving up on the BIOS and your next machine might very well not provide such an interface anymore. Some big box vendors have switched or are switching to UEFI. But the x86 channel mobo manufacturers have not, nor have embedded platform vendors using MIPS and ARM. And they don't appear to have immediate, or any, plans to do so. We'll never see the day that everything is UEFI. 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 distant future. The world hasn't given up on PC BIOS. I build my systems, AMD only, and I don't see any signs of PC BIOS disappearing any time soon from AMD channel mobos. Recall that EFI and by extension UEFI are the children of the failed Intel Itanium chip. UEFI is being pushed as a standard by Intel and now Microsoft, not AMD nor VIA, nor the FLOSS community. Some of the latter are being dragged kicking and screaming. Some aren't buying in. which includes secure boot, and includes other features that tend to take control of the machine away from the user. That's not freedom. Debian does not support secure boot as of now, and whether secure boot restricts or enhances user freedom depends on your ability to install your own keys. Even if you can, the fact that you have to restricts freedom to a degree. 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 without a BIOS. I'll start worrying about this when channel vendors announce they're going UEFI only. I'm sure I've got a few years. -- Stan -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/5199e274.2030...@hardwarefreak.com
Re: vga=ask doesn't work anymore
On 2013-05-20 10:44 +0200, Stan Hoeppner wrote: 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) features like UEFI support and better support for automation. It's an odd play for Debian to get behind UEFI It's not really Debian's choice, the world is finally giving up on the BIOS and your next machine might very well not provide such an interface anymore. Some big box vendors have switched or are switching to UEFI. But the x86 channel mobo manufacturers have not, nor have embedded platform vendors using MIPS and ARM. MIPS and ARM machines don't have a traditional BIOS either, and *all* x86 motherboards have to support UEFI these days. It is a requirement for the Windows 8 logo, and Windows won't boot from GPT partitioned disks with a traditional 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 distant future. This may be so, but this thread is about the vga=ask kernel parameter and LILO, and those are pretty much x86 specific. Debian does not support secure boot as of now, and whether secure boot restricts or enhances user freedom depends on your ability to install your own keys. Even if you can, the fact that you have to restricts freedom to a degree. You don't have to, just turn Secure Boot off if you don't like it. I'll start worrying about this when channel vendors announce they're going UEFI only. I'm sure I've got a few years. There are already laptops which do not provide a BIOS interface anymore. Cheers, Sven -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/87obc6j8wf@turtle.gmx.de
Re: vga=ask doesn't work anymore
On Sun, 19 May 2013 22:57:28 -0400 (EDT), staticsafe wrote: Althought the vga=ext option is deprecated with the linux command in Grub2, it is still available with the linux16 command in Grub2 as it is with the linux command in Grub-legacy. If Grub2 displays vga=ext is deprecated. Use set gfxpayload=text before linux command instead you don't need to downgrade to grub-legacy. Just replace linux and initrd by linux16 and initrd16 in each menuentry bloc you want to use VGA mode and add vga=ext or vga=F01 near the end of the linux16 line 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 all available VGA/VESA resolutions and chose one interactively before Grub2 passes control to the kernel. If you edit /boot/grub/grub.cfg instead of /etc/grub.d/10_linux remember your changes will be dropped if update-grub is launched. By the way, vga=normal is equivalent to vga=F00 and vga=ext is equivalent to vga=F01. - http://wiki.debian.org/GrubTransition#fndef-231bbb76472490d8f289f110d30d2d982e08a663-0 Thanks for posting this, staticsafe. I am a lilo user, but if I am ever forced to use grub2 in the future, at least I now know how to get the vga option to work. -- .''`. Stephen Powell : :' : `. `'` `- -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/1442823568.1287408.1369085018358.javamail.r...@md01.wow.synacor.com
Re: vga=ask doesn't work anymore
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 function differently... it is like someone wants to keep frustrating 08/15-users before linux has even booted... I don't know what you mean by 08/15-users, but if you decide you want to switch back to lilo, you might find the following web page useful: http://users.wowway.com/~zlinuxman/lilo.htm -- .''`. Stephen Powell : :' : `. `'` `- -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/2027006505.1287538.1369085550459.javamail.r...@md01.wow.synacor.com
Re: vga=ask doesn't work anymore
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 machines that do not have a BIOS interface, those looking for an alternative to grub2 may want to look at elilo. I've never used it myself; but it appears that elilo is a boot loader based in design on lilo that is designed to use the EFI interface. I'd be interested in feedback from elilo users out there on how well it works and how they like it. -- .''`. Stephen Powell : :' : `. `'` `- -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/674656979.1287714.1369086142137.javamail.r...@md01.wow.synacor.com
Re: vga=ask doesn't work anymore
On 5/20/2013 4:30 AM, Sven Joachim wrote: On 2013-05-20 10:44 +0200, Stan Hoeppner wrote: 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) features like UEFI support and better support for automation. It's an odd play for Debian to get behind UEFI It's not really Debian's choice, the world is finally giving up on the BIOS and your next machine might very well not provide such an interface anymore. Some big box vendors have switched or are switching to UEFI. But the x86 channel mobo manufacturers have not, nor have embedded platform vendors using MIPS and ARM. 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. and *all* x86 motherboards have to support UEFI these days. You're badly misinformed. There are far more x86 mobos on the market right now without UEFI than with, which all meet the Windows 8 base requirements and will boot and run the OS just fine. http://windows.microsoft.com/en-us/windows-8/system-requirements It is a requirement for the Windows 8 logo, Yes, for the logo program. And this is one of the reasons Windows 8 has been to a large degree a big flop (the other is obviously the horrible interface). Read in the press how Microsoft has been blaming hardware OEMs for the failure of Windows 8 in the marketplace: http://www.theregister.co.uk/2013/01/24/windows_8_blame_game/ And this ramp up of Windows 8 logo certified hardware isn't limited to touchscreen notebooks. FYI, there are brand new Intel socket mobos hitting the market *with* UEFI that don't carry the Windows 8 logo. They have the Windows Vista and Windows 7 logos, but not 8. What does that say? and Windows won't boot from GPT partitioned disks with a traditional BIOS - people want to be able to use hard disks bigger than 2 TiB under Windows. This is a red herring. The Windows 8 push is touch screen portable devices. The OS was not designed for desktops; they were an afterthought. Microsoft has made this perfectly clear. And it's another reason why Win8 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 embedded RISC processor platforms. Linux will be required to support many different flavors of system board firmware now and into the distant future. This may be so, but this thread is about the vga=ask kernel parameter and LILO, and those are pretty much x86 specific. Well yes, but as is often case, this thread has drifted a bit, and you are responsible for some of that drift. The point here is that UEFI support is not mandatory nor required for Linux or its boot loaders, nor must it be in the future. UEFI is more political than technical. The fact that Intel created it, for a doomed processor architecture at that, then moved it to x86, and the fact that its partner in Wintel Microsoft adopted and pushed it, is indicative of this. Debian does not support secure boot as of now, and whether secure boot restricts or enhances user freedom depends on your ability to install your own keys. Even if you can, the fact that you have to restricts freedom to a degree. You don't have to, just turn Secure Boot off if you don't like it. And if you don't need secure boot, you don't need UEFI firmware. I'll start worrying about this when channel vendors announce they're going UEFI only. I'm sure I've got a few years. There are already laptops which do not provide a BIOS interface anymore. No one has made the argument that there are no UEFI only systems on the market. My argument has been that UEFI isn't anywhere close to being dominant, which is what you proposed above. Microsoft has lost its clout due to competition, and is no longer single handedly able to bend hardware standards to its will. Intel as well has lost some standards clout as evidenced by AMD creating x86-64 which Intel adopted. And the rise of mobile devices has also eroded Intel's clout WRT driving standards. Last but not least, the adoption of desktop Linux en mass in Asian markets on low power x86 chips such as VIA, and home grown RISC chips such as the MIPS based Longsoon, has also eroded Intel's standards clout. So again, we're in no danger of UEFI being forced upon us any time soon. Which again means LILO will be a viable boot loader for quite some time into the future. -- Stan -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive
vga=ask doesn't work anymore
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? because when i look in the documentation of the linux kernel it sure says that vga=ask is still there... but something retarded as a boot loader removes kernel options now? wow... just wow.. i thought the linux desktop would have tiles like windows8 but this is even worse... a bootloader breaks the kernel features... it really shows that linux is used by too many idiots now... i'll start a wiki on this bullshit.. how linux step-by-step becomes a badly re-invented windows.. as a warning for freebsd... i don't care about the user base my OS of choice has... but the linux marketing has started writing the linux code now.. so it is bye bye... Dirk -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/5199757f.8050...@pwnoogle.com
Re: vga=ask doesn't work anymore
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 use ? if you are using now testing or sid you sould to move to stable . if so i reverted to grub-legacy... doesn't anybody check the crap that makes it into debian anymore? because when i look in the documentation of the linux kernel it sure says that vga=ask is still there... but something retarded as a boot loader removes kernel options now? wow... just wow.. i thought the linux desktop would have tiles like windows8 but this is even worse... a bootloader breaks the kernel features... it really shows that linux is used by too many idiots now... yes I see one right now -- you .. i'll start a wiki on this bullshit.. how linux step-by-step becomes a badly re-invented windows.. the code of gnu / linux and debian is public . You can take and fix the programm . You probably to read Gnu / Linux != windows [0] as a warning for freebsd... i don't care about the user base my OS of choice has... but the linux marketing has started writing the linux code now.. so it is bye bye... why to send the mail to debian user list and not developers list maybe they will have will have your anwser .. Dirk -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/5199757f.8050...@pwnoogle.com [0] http://linux.oneandoneis2.org/LNW.htm -- Klearchos-Angelos Gkountras http://jemadux.no-ip.info -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/20130520024422.GA11747@snf-44236
Re: vga=ask doesn't work anymore
On Mon, 20 May 2013 02:59:43 +0200 Dirk noi...@pwnoogle.com 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 grub-legacy... doesn't anybody check the crap that makes it into debian anymore? because when i look in the documentation of the linux kernel it sure says that vga=ask is still there... but something retarded as a boot loader removes kernel options now? wow... just wow.. i thought the linux desktop would have tiles like windows8 but this is even worse... a bootloader breaks the kernel features... I don't like grub2. Try lilo. it really shows that linux is used by too many idiots now... i'll start a wiki on this bullshit.. how linux step-by-step becomes a badly re-invented windows.. as a warning for freebsd... Send the link. i don't care about the user base my OS of choice has... but the linux marketing has started writing the linux code now.. so it is bye bye... So ,no wiki? Dirk -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/20130520044456.03ce8aa3@fx4100
Re: vga=ask doesn't work anymore
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 grub-legacy... doesn't anybody check the crap that makes it into debian anymore? I would love for you to tell that to the face of the Debian developers who work very hard on every release. because when i look in the documentation of the linux kernel it sure says that vga=ask is still there... but something retarded as a boot loader removes kernel options now? Althought the vga=ext option is deprecated with the linux command in Grub2, it is still available with the linux16 command in Grub2 as it is with the linux command in Grub-legacy. If Grub2 displays vga=ext is deprecated. Use set gfxpayload=text before linux command instead you don't need to downgrade to grub-legacy. Just replace linux and initrd by linux16 and initrd16 in each menuentry bloc you want to use VGA mode and add vga=ext or vga=F01 near the end of the linux16 line 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 all available VGA/VESA resolutions and chose one interactively before Grub2 passes control to the kernel. If you edit /boot/grub/grub.cfg instead of /etc/grub.d/10_linux remember your changes will be dropped if update-grub is launched. By the way, vga=normal is equivalent to vga=F00 and vga=ext is equivalent to vga=F01. - http://wiki.debian.org/GrubTransition#fndef-231bbb76472490d8f289f110d30d2d982e08a663-0 wow... just wow.. i thought the linux desktop would have tiles like windows8 but this is even worse... a bootloader breaks the kernel features... it really shows that linux is used by too many idiots now... Perhaps you are referring to yourself there? i'll start a wiki on this bullshit.. how linux step-by-step becomes a badly re-invented windows.. as a warning for freebsd... i don't care about the user base my OS of choice has... but the linux marketing has started writing the linux code now.. so it is bye bye... Goodbye, and don't let the door hit you on the way out. Dirk -- staticsafe O ascii ribbon campaign - stop html mail - www.asciiribbon.org Please don't top post - http://goo.gl/YrmAb Don't CC me! I'm subscribed to whatever list I just posted on. -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/20130520025728.ga17...@uriel.asininetech.com
Re: vga=ask doesn't work anymore
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 grub-legacy... doesn't anybody check the crap that makes it into debian anymore? I would love for you to tell that to the face of the Debian developers who work very hard on every release. i know they work hard.. that is probably the reason why such rather subtle regressions escape them.. because when i look in the documentation of the linux kernel it sure says that vga=ask is still there... but something retarded as a boot loader removes kernel options now? Althought the vga=ext option is deprecated with the linux command in Grub2, it is still available with the linux16 command in Grub2 as it is with the linux command in Grub-legacy. If Grub2 displays vga=ext is deprecated. Use set gfxpayload=text before linux command instead you don't need to downgrade to grub-legacy. Just replace linux and initrd by linux16 and initrd16 in each menuentry bloc you want to use VGA mode and add vga=ext or vga=F01 near the end of the linux16 line 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 all available VGA/VESA resolutions and chose one interactively before Grub2 passes control to the kernel. If you edit /boot/grub/grub.cfg instead of /etc/grub.d/10_linux remember your changes will be dropped if update-grub is launched. By the way, vga=normal is equivalent to vga=F00 and vga=ext is equivalent to vga=F01. - http://wiki.debian.org/GrubTransition#fndef-231bbb76472490d8f289f110d30d2d982e08a663-0 thanks for your effort explaining this... 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 function differently... it is like someone wants to keep frustrating 08/15-users before linux has even booted... wow... just wow.. i thought the linux desktop would have tiles like windows8 but this is even worse... a bootloader breaks the kernel features... it really shows that linux is used by too many idiots now... Perhaps you are referring to yourself there? no i refer to people to whom it doesn't make a difference if they use windows or linux... people who do not care... but to whom everyone is catering and ruining linux as an operating system.. just look at all the bloat the ubuntu desktop requires to start a program by clicking on a little icon... it is a total joke.. i'll start a wiki on this bullshit.. how linux step-by-step becomes a badly re-invented windows.. as a warning for freebsd... i don't care about the user base my OS of choice has... but the linux marketing has started writing the linux code now.. so it is bye bye... Goodbye, and don't let the door hit you on the way out. not so fast.. there is still gentoo... :( Dirk -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/5199956a.8030...@pwnoogle.com
Re: vga=ask doesn't work anymore
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 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? I would love for you to tell that to the face of the Debian developers who work very hard on every release. i know they work hard.. that is probably the reason why such rather subtle regressions escape them.. One man's regression is another man's progression. Either way, somebody noticed the change and put up the wiki page I linked. because when i look in the documentation of the linux kernel it sure says that vga=ask is still there... but something retarded as a boot loader removes kernel options now? Althought the vga=ext option is deprecated with the linux command in Grub2, it is still available with the linux16 command in Grub2 as it is with the linux command in Grub-legacy. If Grub2 displays vga=ext is deprecated. Use set gfxpayload=text before linux command instead you don't need to downgrade to grub-legacy. Just replace linux and initrd by linux16 and initrd16 in each menuentry bloc you want to use VGA mode and add vga=ext or vga=F01 near the end of the linux16 line 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 all available VGA/VESA resolutions and chose one interactively before Grub2 passes control to the kernel. If you edit /boot/grub/grub.cfg instead of /etc/grub.d/10_linux remember your changes will be dropped if update-grub is launched. By the way, vga=normal is equivalent to vga=F00 and vga=ext is equivalent to vga=F01. - http://wiki.debian.org/GrubTransition#fndef-231bbb76472490d8f289f110d30d2d982e08a663-0 thanks for your effort explaining this... 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 function differently... it is like someone wants to keep frustrating 08/15-users before linux has even booted... You can use Lilo if you so choose, but don't expect integration (specifically kernel package installation scripts). 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 automation. Another note, GRUB2 is more similar to Lilo than you think. wow... just wow.. i thought the linux desktop would have tiles like windows8 but this is even worse... a bootloader breaks the kernel features... it really shows that linux is used by too many idiots now... Perhaps you are referring to yourself there? no i refer to people to whom it doesn't make a difference if they use windows or linux... people who do not care... but to whom everyone is catering and ruining linux as an operating system.. just look at all the bloat the ubuntu desktop requires to start a program by clicking on a little icon... it is a total joke.. I use Debian partly because it is not a distro like that. i'll start a wiki on this bullshit.. how linux step-by-step becomes a badly re-invented windows.. as a warning for freebsd... i don't care about the user base my OS of choice has... but the linux marketing has started writing the linux code now.. so it is bye bye... Goodbye, and don't let the door hit you on the way out. not so fast.. there is still gentoo... :( Gentoo does seem more like what you want. Dirk -- staticsafe O ascii ribbon campaign - stop html mail - www.asciiribbon.org Please don't top post - http://goo.gl/YrmAb Don't CC me! I'm subscribed to whatever list I just posted on. -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/20130520040409.gc17...@uriel.asininetech.com
Re: vga=ask doesn't work anymore
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 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 automation. It's an odd play for Debian to get behind UEFI which includes secure boot, and includes other features that tend to take control of the machine away from the user. That's not freedom. 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. If I had to come up with one word to describe today's LILO users, it would probably be purists. We want a reliable boot loader that is as basic as can be and accomplish the simple, single job of loading the OS kernel. -- Stan -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/5199b419.5090...@hardwarefreak.com
Re: vga=ask doesn't work anymore
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 users, it would probably be purists. We want a reliable boot loader that is as basic as can be and accomplish the simple, single job of loading the OS kernel. If you want a multi-boot including FreeBSD, there might be the need to use GRUB2. That's because I switched back from GRUB legacy to GRUB2. OTOH I can boot FreeBSD using the chainloader, so I guess I could use any other bootloader too. I'm not an expert, but many experts claim that GRUB is crap and better code is Syslinux. -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/1369029177.988.29.camel@archlinux
RE: vga=ask
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 Healthcare Solutions Group
RE: vga=ask
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 svgatextmode package ? apt-get install svgatextmode That's what I use instead of the kernel vga settings. HTH -- RM
Re: vga=ask
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 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 in place of ask (and -2 in place of -3) None of this has worked for me. Any idea how I can squeeze more that 80x25 out of my S3 Trio64 and my 21 monitor on Debian potato with kernel 2.2.15? I followed the directions in /usr/src/linux/Documentation/fb/vesafb.txt and did the following to my lilo.conf Image= /boot/Slink-2.2.15 label = Slink2.2.15 Root = /dev/hdb2 VGA= 0x317 append = video=vesa:ywrap,pro,pmipal hdd=cdrom lp=parport0 parport=0x378,none I deleted the vga=ask after experimenting with the options shown in the above doc. I settelked on the 0x317 (128x40) as the best for _my_ Monitor. YMMV HTH -- Unquestionably, there is progress. The average American now pays out twice as much in taxes as he formerly got in wages. -- H. L. Mencken ___
Re: vga=ask
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 \boot\vmlinuz-2.2.15 -3 I have also tried all of the above with extended in place of ask (and -2 in place of -3) None of this has worked for me. Any idea how I can squeeze more that 80x25 out of my S3 Trio64 and my 21 monitor on Debian potato with kernel 2.2.15? I used 'vga=ask' at the boot prompt if I remember right. If that doesn't work for you the 'lilo.conf' manpage says -- number: use the corresponding text mode. A list of available modes can be obtained by booting with vga=ask and pressing [Enter]. If this variable is omitted, the VGA mode setting contained in the kernel image is used. (And that is set at compile time using the SVGA_MODE variable in the kernel Makefile, and can later be changed with the rdev(8) program.) hth, kent
RE: vga=ask
I'm posting this again in the hopes that someone may know the problem. One person responded (and I appreciate that), but I've already tried everything they suggested. Anyone have any ideas? I'm really stumped. Is it possible that I've somehow excluded support for this option 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 \boot\vmlinuz-2.2.15 -3 I have also tried all of the above with extended in place of ask (and -2 in place of -3) None of this has worked for me. Any idea how I can squeeze more that 80x25 out of my S3 Trio64 and my 21 monitor on Debian potato with kernel 2.2.15? Thanks. A. Scott White Director of Information Systems and Product Strategy ACS Healthcare Solutions Group
Re: vga=ask
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 in place of ask (and -2 in place of -3) None of this has worked for me. Any idea how I can squeeze more that 80x25 out of my S3 Trio64 and my 21 monitor on Debian potato with kernel 2.2.15? Thanks. A full screen console (no X), is that what you want? If so check out framebuffer. There is an HOWTO on it. Jo
RE: vga=ask
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 want, however, to be able to see more text on the screen at one time. What is framebuffer? A. Scott White Director of Information Systems and Product Strategy ACS Healthcare Solutions Group
Re: vga=ask
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 global section with no mention of vga=auto anywhere and it works fine. After running lilo and rebooting I get a prompt along the lines of Press RETURN to see available modes or SPACE to continue. When I press return it brings up a list of available resolutions. -- The last time I saw him he was walking down Lover's Lane holding his own hand. -- Fred Allen pgpXEyFxfOTTl.pgp Description: PGP signature
Re: vga=ask
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 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. What is framebuffer? Framebuffer is a kernel thing that *may* allow you to run high resolution consoles. I use 1024x768x32bpp ... pretty nice. Plus you get a groovy penguin image at boot-up! Available in 2.2 kernels for x86 machines. See kernel source/Documentation/fb/*.txt. Framebuffer != X, though there is an unaccellerated X server with a Framebuffer target (XF86_FBDEV) -- suboptimal if svga or other will give you accelleeration. -- ¶ One·should·only·use·the·ASCII·characterset·when·compos » ing·email·messages.
vga=ask
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 in place of ask (and -2 in place of -3) None of this has worked for me. Any idea how I can squeeze more that 80x25 out of my S3 Trio64 and my 21 monitor on Debian potato with kernel 2.2.15? Thanks. A. Scott White Director of Information Systems and Product Strategy ACS Healthcare Solutions Group
Re: vga=ask in lilo.conf
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 SVGATextMode stuff, as the resolutions and text modes available under most of my VGA cards suit me just fine. Hope it helps, enjoy. You can read more in the man pages for the SVGA stuff if your interested. I've never really used it, as I like the VGA stuff better. Enjoy, and hope you had happy holidays, Nate, [EMAIL PROTECTED] On Sat, Dec 25, 1999 at 10:43:23AM -0800, Andy Thomas wrote: 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
Re: vga=ask in lilo.conf
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
Re: vga=ask in lilo.conf
On Mon, Dec 20, 1999 at 03:13:37PM -0800, Andy Thomas wrote: Hi, Is this known to be a bit buggy? I put this in there and once in awhile (every 5th boot or so... I know linux is stable but am saving electricity g) I get the video option in the boot menu (hit enter to choose). 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 causing this behaviour. vga=ask was indicated as an option by the O'Reilly book. Yep, this should show you all the options available to you. The kernel has built-in support for the standard VGA text modes (not to be confused with SVGATextMode package) which you can call at boot-time by passing values to the kernel from LILO. My preferred way of doing this is via the LILO prompt itself, which gives me the flexibility to turn this one on and off at will. Some video cards can't do the various modes they claim to support quite right, so on new machines, calling this stuff from the LILO boot prompt (if you have it enabled) allows you to play with the settings to find the best one for the particular machine. So at the LILO: prompt, type: linux vga=ask if your kernel image is called linux as most are... You'll be prompted through displaying the possibilities your card can support. You then choose and voila... smaller text than you had during the LILO portion of the boot. Some settings don't work so well, so play and find what's best for your machine. Then you can either define it on the command line from LILO linux vga=2, or just put it in /etc/lilo.conf and rerun lilo ... as I believe you said the O'Reilley book suggests. TIA for any insight into this. Andy Hope it helps... Nate, [EMAIL PROTECTED]
vga=ask in lilo.conf
Hi, Is this known to be a bit buggy? I put this in there and once in awhile (every 5th boot or so... I know linux is stable but am saving electricity g) I get the video option in the boot menu (hit enter to choose). 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. vga=ask was indicated as an option by the O'Reilly book. TIA for any insight into this. Andy
Re: lilo.conf--vga=ask doesn't; APM
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 menuconfig or make xconfig. make-kpkg is supposed to make it easier too, although I haven't used it. If your current setup works, you don't need to know anything about your hardware. Just keep hitting enter when running make config until near the end when it comes to APM. Just turn it on and keep hitting enter, then Thank you for your suggestions about recompiling the kernel to include APM support. Could I ask you a follow-up question to your messages? I have tried running 'make config', 'make menuconfig' and 'make xconfig', but I always get the same error, No rule to make target 'config'. Running 'make -p' shows no entries under the Make data base, which I suspect is related to the error message. I hope this isn't an utterly ignorant question--I am trying to read as fast as I can, but Unix just seems to be getting bigger and more complex at an equal or greater rate. ;-) Cheers, Nikolaj -- Nikolaj Richers, North York, Canada, [EMAIL PROTECTED]
Re: lilo.conf--vga=ask doesn't; APM
-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 wrote: 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 menuconfig or make xconfig. make-kpkg is supposed to make it easier too, although I haven't used it. If your current setup works, you don't need to know anything about your hardware. Just keep hitting enter when running make config until near the end when it comes to APM. Just turn it on and keep hitting enter, then Thank you for your suggestions about recompiling the kernel to include APM support. Could I ask you a follow-up question to your messages? I have tried running 'make config', 'make menuconfig' and 'make xconfig', but I always get the same error, No rule to make target 'config'. Running 'make -p' shows no entries under the Make data base, which I suspect is related to the error message. I hope this isn't an utterly ignorant question--I am trying to read as fast as I can, but Unix just seems to be getting bigger and more complex at an equal or greater rate. ;-) Cheers, Nikolaj -- Nikolaj Richers, North York, Canada, [EMAIL PROTECTED] Have a good one. - -- Rick Jones E-Mail: Rick [EMAIL PROTECTED] Date: 05-Apr-97 Time: 09:22:54 - -- -BEGIN PGP SIGNATURE- Version: 2.6.2 iQCVAwUBM0ZgSwi+Ph+i3TgpAQFrmgQAvmNl6LQjcbdpALJezRAzE6mtGcC8h/vz JsP6RvUHq0i/kHpivpRAbDoTXuFQMqZJUHKoPJ2dD/yq19R4Ka8IAo0pzmj3OoTt vMhmHtzr150YAX+O3f2QAPRVtSwIgQwvmszGMsH0NbTIwfTKA0/EFPkMp3idT3K7 9BFEvZxip9M= =zEX0 -END PGP SIGNATURE-
lilo.conf--vga=ask doesn't; APM
Fellow Linuxists, I've just subscribed to this list after having installed Debian on my laptop. I am very grateful that such an OS is available! It's been a steep learning curve, but a worthwhile one. 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 doesn't ask anything, just boots up as it usually would, at 400 scans. Is this broken or am I missing an obvious step? Also, I thought that /APM support/ is in the post-1.3.something kernel. I get the message that there is no APM support in my 2.0.27 one and kerneld doesn't seem to load it either. I had dselect install the APM package. Can this be set straight short of re-compiling the kernel? I'm happy I've got this thing all set up finally, and I'd like to grind my teeth on some simpler things first. Cheers, and thank you for any suggestions you might have, Nikolaj -- Nikolaj Richers, North York, Canada, [EMAIL PROTECTED]
Re: lilo.conf--vga=ask doesn't; APM
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' 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 step? Did you run lilo after modifying your lilo.conf? (This is the obvious step. You might have missed something less obvious.) You can also try this out by pressing Alt or something at boot to get the LILO boot: prompt, and type something like linux vga=ask there. Also, I thought that /APM support/ is in the post-1.3.something kernel. I get the message that there is no APM support in my 2.0.27 one and kerneld doesn't seem to load it either. I had dselect install the APM package. Can this be set straight short of re-compiling the kernel? 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 too, although I haven't used it. -- Carey Evans * [EMAIL PROTECTED] Double, double, toil and trouble, / Fire burn and cauldron bubble.
Re: lilo.conf--vga=ask doesn't; APM
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 doesn't ask anything, just boots up as it usually would, at 400 scans. Is this broken or am I missing an obvious step? You might find that svgatextmode is what you're looking for. It can be a bit of an ordeal to set up, but it gives a lot more control than the lilo vga thingy. Just be sure to read all the documentation, as you can mess your terminal up if you get it wrong (I did!). Once it works it's _very_ nice though. John Foster
Re: lilo.conf--vga=ask doesn't; APM
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 too, although I haven't used it. If your current setup works, you don't need to know anything about your hardware. Just keep hitting enter when running make config until near the end when it comes to APM. Just turn it on and keep hitting enter, then make dep;make clean make modules make modules_install make zlilo reboot and you should be fine. You'll probably want to get the apm (apmd?) package. -douglas
