Does anyone know how to set up the mbr in lilo.conf for the udev naming
scheme?
I'm getting the error:
/dev/root: unknown volume type
mounting /dev/root on /root failed: no such device
etc. with the lilo.conf below
and the ash shell starts to try to troubleshoot.
the simple ide module is
Ok, the reason I didn't have my nice small fonts was simply that I
didn't enable framebuffer console support.
Since I have a Matrox G550 Dual-Head card I decided to try the Matrox fb
(Matrox Acceleration) instead of the vesafb.
That works fine for console mode (although I'm not sure what dual-hea
On Fri, Jul 02, 2004 at 07:34:20PM +0200, Andreas Janssen wrote:
> Probably missing Framebuffer support. Did you use the bf24 Kernel
> before? That one did come with compiled-in VESA framebuffer support.
> Check the config of your 2.6 Kernel for this.
Right, I don't have CONFIG_FB set in the new k
Hello
Bill Moseley (<[EMAIL PROTECTED]>) wrote:
> Under my 2.4 kernel I used
>
>vga=0x317
>
> which was a nice small console font.
>
> Now with 2.6 vga=ask and then using "scan" I don't have that choice
> any more (screen is blank if I use vga=0x317).
Probably missing Framebuffer support.
Under my 2.4 kernel I used
vga=0x317
which was a nice small console font.
Now with 2.6 vga=ask and then using "scan" I don't have that choice any
more (screen is blank if I use vga=0x317).
Why do I not have that mode any more?
The other interesting thing is in 2.6 my mouse moves *much* fas
>
> --
> From: Sreelal Chandrasenan
> Sent: Monday, December 15, 2003 9:25:22 AM
> To: Debian User (E-mail)
> Subject: FW: lilo.conf
> Auto forwarded by a Rule
>
>
>
-Original Message-
From: Alvin Oga [mailto:[EMAIL PROTEC
On Monday December 15 at 03:09pm
Gavin Seddon <[EMAIL PROTECTED]> wrote:
> Hi,
> I use lilo as my boot-loader and I need to add an "append" statement
> to it in order for my ide cdrw to work. Additionally, there is a SCSI
> tape drive on the system. Will someone pls tell me the correct line
> re
-Original Message-
From: Alvin Oga [mailto:[EMAIL PROTECTED]
Sent: Monday, December 15, 2003 8:02 AM
To: Gavin Seddon
Cc: debian list
Subject: Re: lilo.conf
hi ya gavin
On Mon, 15 Dec 2003, Gavin Seddon wrote:
> Hi,
> I use lilo as my boot-loader and I need to add an &
ine required?
vi /etc/lilo.conf
#
root=/dev/hda1
#
# assuming your cdrw is on "hdc"
#
append="hdc=ide-scsi"
#
rest of the cdrw stuff
http://www.Linux-1U.net/CDRW
c ya
alvin
--
To UNSUBSCRIBE, email to [EMAIL
Hi,
I use lilo as my boot-loader and I need to add an "append" statement to it in
order for my ide cdrw to work. Additionally, there is a SCSI tape drive on
the system. Will someone pls tell me the correct line required?
Gavin.
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject o
Kevin McKinley wrote:
> Bob Proulx wrote:
> > installed, the symlinks pointing to it, and running lilo will set up
> > the boot to go to the new kernel.
> [...]
> When I got to the "install ... existing lilo.conf" question, if I answered
> yes rebooting the sys
On Wed, 13 Aug 2003 19:36:17 -0600
[EMAIL PROTECTED] (Bob Proulx) wrote:
> > A longer answer is that writing a new boot block with the existing
> > lilo.conf would simply re-write the current boot sector, which would
> > boot the old kernel.
>
> Are we talking about th
I don't understand WHY this excellent reference:
http://newbiedoc.sourceforge.net/system/kernel-pkg.html
advises one to do the following:
"Be sure you say "no" when the script asks if you want
to install a boot block using the existing /etc/lilo.conf."
So when the scr
he script asks if you want
> to install a boot block using the existing /etc/lilo.conf."
The short answer is "because when I said 'Yes' it didn't work". :)
A longer answer is that writing a new boot block with the existing lilo.conf
would simply re-write the curre
Kevin McKinley wrote:
> Andy wrote:
> > advises one to do the following:
> > "Be sure you say "no" when the script asks if you want
> > to install a boot block using the existing /etc/lilo.conf."
>
> The short answer is "because when I said &#
J F wrote:
Rob Weir wrote:
On Mon, Jul 28, 2003 at 06:42:47PM -0700, J F wrote:
Based on the output from aptitude and my current
lilo.conf, do you think I need to do anything to lilo.conf?
aptitude is just a frontend. dpkg is doing the actual work of unpacking
and installing the package.
Is
Rob Weir wrote:
On Mon, Jul 28, 2003 at 06:42:47PM -0700, J F wrote:
Based on the output from aptitude and my current
lilo.conf, do you think I need to do anything to lilo.conf?
aptitude is just a frontend. dpkg is doing the actual work of unpacking
and installing the package.
Is aptitude going
On Mon, Jul 28, 2003 at 06:42:47PM -0700, J F wrote:
> Based on the output from aptitude and my current
> lilo.conf, do you think I need to do anything to lilo.conf?
aptitude is just a frontend. dpkg is doing the actual work of unpacking
and installing the package.
> Is aptitude goi
Based on the output from aptitude and my current
lilo.conf, do you think I need to do anything to lilo.conf?
Is aptitude going to put the new kernel
in /boot?
Will aptitude fix the link /vmlinuz ?
I ran aptitude and it did a lot of things and then said:
aptitude wrote:
Unpacking kernel-image
On Tue, 27 May 2003 12:22:54 -0400
"Brian W. Carver" <[EMAIL PROTECTED]> wrote:
> I just compiled a custom 2.4.18 kernel for my woody-running laptop.
>
> I'm new at this and am pretty sure I am about to shutdown and be unable to
>
> boot back up, because this initrd/lilo stuff has me baffled. P
On Tuesday 27 May 2003 14:08, Mark Roach wrote:
> I imagine this is because you don't have initrd-tools installed. For
> some reason the stock kernel images put this for depends:
> Depends: initrd-tools (>= 0.1.40), coreutils | fileutils (>= 4.0),
> modutils (>= 2.4.19)
>
> but when you use make-
On (27/05/03 10:32), Brian Carver wrote:
> New problem:
>
> When I proceeded with the
>
> dpkg -i kernel-image-2.4.18-custom.1.0_i386.deb
>
> after deciding that initrd.img was ok to put in lilo.conf I get an
> error:
> -
> Setting up kernel-image-2.4.1
On Tue, 2003-05-27 at 13:32, Brian Carver wrote:
> New problem:
>
> When I proceeded with the
>
> dpkg -i kernel-image-2.4.18-custom.1.0_i386.deb
>
> after deciding that initrd.img was ok to put in lilo.conf I get an error:
> -
> Setting up kernel-image-2.4.18 (
On Tuesday 27 May 2003 12:22, Brian W. Carver wrote:
> I just compiled a custom 2.4.18 kernel for my woody-running laptop.
>
> I'm new at this and am pretty sure I am about to shutdown and be unable to
> boot back up, because this initrd/lilo stuff has me baffled. Please help!
I had the same quest
New problem:
When I proceeded with the
dpkg -i kernel-image-2.4.18-custom.1.0_i386.deb
after deciding that initrd.img was ok to put in lilo.conf I get an error:
-
Setting up kernel-image-2.4.18 (custom.1.0) ...
Failed to create initrd image.
dpkg: error processing kernel-image-2.4.18
help!
> I followed the instructions about building a kernel using
> make-kpkg carefully (the README in /usr/doc/kernel-package)
> and while in menuconfig chose the initrd option because it
> suggested I needed to do so.
> my /etc/lilo.conf says:
>
> image=/vm
-kpkg
carefully (the README in /usr/doc/kernel-package) and while in menuconfig
chose the initrd option because it suggested I needed to do so.
my /etc/lilo.conf says:
image=/vmlinuz
label=Linux
read-only
initrd=/initrd.img
I added that last line since the first prompt of dpkg -i
k
On Tue, Feb 04, 2003 at 12:43:54PM +0100, boukhairi wrote:
> Does any one know what kind
> of information i'v got to
> put into lilo.conf (line append = "") to
> define resolution of the frame
> buffer on a radeon 7000
> (not vesa, as i know it cannot be over
&g
On Sat May 11, 2002 at 07:03:31PM -0700, Jaye Inabnit ke6sls wrote:
> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA1
>
>
> Greetings:
>
> Would anyone care to drop me a copy of their lilo.conf for booting Debian and
> another *nix on the same hard drive? I am ou
On Sat, May 11, 2002 at 07:03:31PM -0700, Jaye Inabnit ke6sls wrote:
| Greetings:
|
| Would anyone care to drop me a copy of their lilo.conf for booting Debian and
| another *nix on the same hard drive? I am out of practice, and could use it
| as a quick reference to get both Debian and
>
> Greetings:
>
> Would anyone care to drop me a copy of their lilo.conf for booting Debian and
> another *nix on the same hard drive? I am out of practice, and could use it
> as a quick reference to get both Debian and his old RedHat booting via lilo.
> The box
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Greetings:
Would anyone care to drop me a copy of their lilo.conf for booting Debian and
another *nix on the same hard drive? I am out of practice, and could use it
as a quick reference to get both Debian and his old RedHat booting via lilo
On Mon, Feb 04, 2002 at 04:23:56PM -0800, Kapil Khosla wrote:
> Hi,
> I have installed Potato on my laptop and edited my lilo.conf to have
> dual boot At boot time, I have to press shift and enter windows. I
> have seen some graphic selection option in some systems What is the
>
Hi,
I have installed Potato on my laptop and edited my
lilo.conf to have dual boot
other=/dev/hda1
label=Windows
table = /dev/hda
# restricted
# alias=3
At boot time, I have to press shift and enter windows.
I have seen some graphic selection option in some systems
ears and won` t stop it) also with
> boot in the mbr. I try a lot, but couldn` t boot Debian from my harddisk. I
> think, something in the lilo.conf is wrong ... i post it here and hope
> someone can say whats wrong (dont look at the label "debian" ... its only one
> of a lot
Debian from my harddisk. I
think, something in the lilo.conf is wrong ... i post it here and hope
someone can say whats wrong (dont look at the label "debian" ... its only one
of a lot wrong things
Thanks
Herbert
My lilo.conf:
boot=/dev/hda
map=/boot/map
install=/boot/boot.b
4x768,font:SUN12x22"
root = /dev/hda2
label = Linux
read-only
that makes lilo initialize the VMA _before_ it boots the kernel. At
least that's my understanding.
You can find my lilo.conf and other configuration files (X etc.) at:
http://www.goingware.com/linux/configs/
On Mon, 2002
I'm trying to set up a amchien that I need to pass multiple append commands
to. I need to tell it to use framebuffer, and to reserve /dev/hdc for the
ide-scsi driver.
I can make it do either, but not both.
Here's the relavent peice of what I've got for lilo.conf:
image=/vmlinu
> Notes: If my scsi controller is set to boot from scsi id 0, and try to boot
> windows, I get the following lilo prompt: LILO, and I see the windows
> label (i.e. windows_98), and that's it. Windows will not boot, but Debian
> boots up and runs fine.
>
What does your /etc/lilo.conf look like?!
Cheers.
Eamon Roque.
l (i.e. windows_98), and that's it. Windows will not boot, but Debian
boots up and runs fine.
P.S. If possible I would like to use lilo, and not grub. I wish I made a
backup of my lilo.conf.
Thanks, Jim
[EMAIL PROTECTED]
[EMAIL PROTECTED]
hi,
lilo boot: linux init=/bin/sh rw
i think you can boot linux with this parameters and then repair your
lilo.conf
- Original Message -
From: <[EMAIL PROTECTED]>
To:
Sent: Thursday, August 02, 2001 10:13 PM
Subject: Dead Lilo.conf
> I modified my LILO.CONF trying to make it
I modified my LILO.CONF trying to make it dual-boot properly with Windows 98,
but now whenever I choose Linux, I get an error saying it can't load init and
the boot fails. When I launch Windows I get an error saying: L? which then
turned into L?80. (What?!) Does anyone know what I should
On Thu, May 10, 2001 at 01:46:37AM -0600, GMAN wrote:
> I am trying to get lilo.conf to load up the latest kernel I recently
> installed, but I am lost at this since I am a total newbie. Any help will be
> greatly appreciated.
>
If you installed with kernel-package you could pro
I am trying to get lilo.conf to load up the latest
kernel I recently installed, but I am lost at this since I am a total
newbie. Any help will be greatly appreciated.
Dan
Thanks guys.
I had seen the hex mode numbers at the lilo stage, but then I remembered
doc/lilo/Manual.txt:
vga= alters the VGA mode set at startup. The values normal ,
extended , ask or a decimal number are recognized. (See also
"Booting
kernel images from a file".)
And so I didn'
Hello,
Am Tuesday, den 06. March 2001 20:15:48 schrieb Jonathan Matthews:
> I'd like to have vga=9 (132Xsomething_or_other) in lilo.conf, but '9' as
> an option only crops up after a manual 'scan' at the "Press ENTER or
> type SCAN to . . " prompt.
lilo uses hex notation...I can't remember if it'd be 0x09 or just 0x9.
On Tue, 6 Mar 2001, Jonathan Matthews wrote:
>I'd like to have vga=9 (132Xsomething_or_other) in lilo.conf, but '9' as
>an option only crops up after a manual 'scan' at the "Pres
I'd like to have vga=9 (132Xsomething_or_other) in lilo.conf, but '9' as
an option only crops up after a manual 'scan' at the "Press ENTER or
type SCAN to . . " prompt.
Lilo complains if I put vga=9 in, as it appears to be an invalid mode,
but it works afte
can someone send me a working lilo.conf file for a debian and linux dual
boot? mine seems to be hosed for reasons I can't work out.
much thanks,
Renai
Dear Debian users,
Sorry for the last badly conceived e-mail., and my apologies if
anyone went to went to any trouble over it.t
Just in case anyone out there might be interested:
One needs to have EACH kernel, which is pointed to by
lilo.conf 'image = ' record on a partitio
unworkable,.
Would somebody be able to kindly have a look at my existing lilo.conf,
and suggest
how it incorprated into a Debian lilo.conf file, so that I can boot up
to either my Debian or
Mandrake Linux systems.? ( I had no problem booting up to Windows)
On my current system, the root partitions are
To quote Russell Coker <[EMAIL PROTECTED]>,
# http://www.coker.com.au/bonnie++/ Bonnie++ hard drive benchmark
Hey, I didn't know you wrote bonnie++ :) Great utility, thanks :)
Dave
I've got a new lilo package on http://www.coker.com.au/lilo/ . It will be in
unstable in a few days.
--
http://www.coker.com.au/bonnie++/ Bonnie++ hard drive benchmark
http://www.coker.com.au/postal/ Postal SMTP/POP benchmark
http://www.coker.com.au/projects.html Projects I am working
On Sunday 07 January 2001 07:34, Mircea Luca wrote:
> Since this thread is CC'ed to debian-user,is it a known fact that
> message=/boot/graphic_screen doesn't work with the new lilo or is it a
> bug
> I should report ?For now I installed the storm's version of lilo and
> holded
> the official lilo(
line: ## swat ...
> > There I found that these lines can be changed by the "update-inetd"-tool.
> > I think something like that would be cool, so one can insert own lines,
> > but some tool can also handle those labeled-lines (and only those). So
> > the config-
etd"-tool.
> I think something like that would be cool, so one can insert own lines,
> but some tool can also handle those labeled-lines (and only those). So
> the config-files remain transparent.
> I think it's not the idea of debconf, to really have all possible
> variab
led-lines (and only those). So
the config-files remain transparent.
I think it's not the idea of debconf, to really have all possible
variables of lilo.conf/squid.conf changed, but only the "most wanted"
for a fast setup.
Greetings,
Tibor
r
> doing it. I do recognize the configuration in that file as being an old
> one, however. Does yours not overwrite a .old file if it finds one? Why
> was a backup necessary in the first place? I wasn't asked if I wanted my
The following command is used:
mv /etc/lilo.conf /etc/
On Saturday 06 January 2001 16:57, David B.Harris wrote:
> To quote Russell Coker <[EMAIL PROTECTED]>,
> # On Saturday 06 January 2001 14:55, you wrote:
> # > I request that you provide support for me telling lilo that I don't
> # > want it touching my lilo.conf at al
On Saturday 06 January 2001 21:19, Tibor D. wrote:
> I like it that by now you can set up lilo with debconf, thats a good
> idea, it's now possible to set lilo up very fast. But: would it be
> possible to leave lilo.conf's original "look and feel"? I mean like when
> you install exim, you can confi
On Sat, Jan 06, 2001 at 11:19:39AM +0100, Tibor D. wrote:
> And the problem with overwriting the old configfile isn't very nice,
> just 1 lilo.conf.old isn't enough, maybe a first possibility would be
> with "logrotate"?
its not just not nice, its a policy violation. packages are
*forbidden* f
ad of archaic ones".
I must admit I was taken slightly aback by the lack of warning given when
conducting the lilo update. I've seen some much more blatant warnings in
my time, and I thought something of this nature required a bit more notice
than it gave, but, thats just my opinion. In the
e it impossible to login to machines that
have them installed. In two cases those packages had bugs which came back on
more than one occasion. I admit that in regard to one of the packages I got
a bit edgy after my machine became unusable for the third time in a week, but
I felt no need to start
Hi,
I like it that by now you can set up lilo with debconf, thats a good
idea, it's now possible to set lilo up very fast. But: would it be
possible to leave lilo.conf's original "look and feel"? I mean like when
you install exim, you can config it with debconf, but the exim.conf
looks like th
To quote Russell Coker <[EMAIL PROTECTED]>,
# On Saturday 06 January 2001 14:55, you wrote:
# > I request that you provide support for me telling lilo that I don't
# > want it touching my lilo.conf at all. Also, you should consider how
# > to deal with changes that the u
quote from postinst) You KNEW this was going to do this.
As for filing bug reports, I note that several people already have on these
issues. Should I add another? Would it have helped?
You haven't MADE a request for my lilo.conf. Here it is:
boot=/dev/hda
root=/dev/hda3
install=/boot/boot.
ce a risk that it won't
work correctly. The proceedure that you should follow is to file a bug
report describing how it didn't work as you expected. If you are unable to
file bug reports and have a risk of things not working as designed then you
should stick to potato.
Also you have i
Marc> you removed their configurations, and replaced them with
Marc> configurations pointing to the root of the filesystem where,
Marc> needless to say, there are no kernel images.
The scripts probably should (at the very least) make a backup copy of
/etc/lilo.conf, just in cas
On Saturday 06 January 2001 14:09, David B.Harris wrote:
> To quote Russell Coker <[EMAIL PROTECTED]>,
> # I am working on the Debian package of lilo and am writing code for
> # auto-generating lilo.conf files.
> #
> # Below is an example of the type of lilo.conf that ca
On Saturday 06 January 2001 14:55, you wrote:
> I request that you provide support for me telling lilo that I don't
> want it touching my lilo.conf at all. Also, you should consider how
> to deal with changes that the user makes by hand to lilo.conf. If you
> don't regener
Russell Coker [mailto:[EMAIL PROTECTED]
Sent: Friday, January 05, 2001 6:52 PM
To: debian-user@lists.debian.org
Subject:lilo.conf
I am working on the Debian package of lilo and am writing code for
auto-generating lilo.conf files.
Below is an example of the type of lilo.conf that can b
To quote Russell Coker <[EMAIL PROTECTED]>,
# I am working on the Debian package of lilo and am writing code for
# auto-generating lilo.conf files.
#
# Below is an example of the type of lilo.conf that can be generated.
The
# debconf asks whether you want boot or boot-menu as the boot
I am working on the Debian package of lilo and am writing code for
auto-generating lilo.conf files.
Below is an example of the type of lilo.conf that can be generated. The
debconf asks whether you want boot or boot-menu as the boot loader, it asks
what VGA mode you want, what parameters to
Yes I did.
I ran /sbin/lilo before reboot.
After reboot, I can use my CD-RW, but lilo.conf is
restored to original form, so after the next reboot I
can't use my CD-RW.
--- Jeremy <[EMAIL PROTECTED]> escribió: >
>thanks for responding.
> >
> >Cristoph:
> >
>thanks for responding.
>
>Cristoph:
>
>It's working. But lilo.conf is still restored to
>original form "non-scroll" after reboot.
>
>Any idea what's happening?
>
>Peter:
>I'm using kwrite. ¿does it's matter?
>
I hope I'm
thanks for responding.
Cristoph:
It's working. But lilo.conf is still restored to
original form "non-scroll" after reboot.
Any idea what's happening?
Peter:
I'm using kwrite. ¿does it's matter?
--- Peter Palfrader <[EMAIL PROTECTED]> escribió: > >
> ---
> ^X^C
> q
> quit
> :q
> ^C
> end
> x
> exit
> ZZ
> ^D
> ?
> help
> shit
> .
ed is a fine editor, isn't it?
yours,
peter
--
PGP signed and encrypted messages preferred.
http://www.palfrader.org/
On Wed, 27 Dec 2000 15:17:08 -0600 (CST)
Enrique Gutiérrez <[EMAIL PROTECTED]> wrote:
> Hi!
>
> I'm trying to modify the lilo.conf file (configuring a
> IDE/ATAPI CD-ROM burner), by adding
>
> append="hdc=ide-scsi",
>
> however, there i
Hi!
I'm trying to modify the lilo.conf file (configuring a
IDE/ATAPI CD-ROM burner), by adding
append="hdc=ide-scsi",
however, there is already a line with
append="non-scroll"
I can't just add the entire line for ide-scsi, neither
"hdc=ise-scsi" por
What does your lilo.conf file look like?
You should have something like this
append="ether=0,0,eth1"
in your image section
Jason
>
>
> I have a network set up (one other machine) and have now decided to go
> to cable for Internet access (phone service here is painfull
t and Boot HOW-TOs both prescribe including the following in
lilo.conf, to force the kernel to search for the second card:
ether=0,0,eth1
or
ether=12,0x320,eth1
ether=10,0x300,eth0
When I do this, and run lilo, it tells me I have a syntax error (in both
cases), and will not process anything pas
Hoi Kent!
Kent> I am using vga=9 on at the moment in my lilo.conf . I would
Kent> like to use the next mode, but my my eyes dont like the low
Kent> refreshrate :( I dont use framebuffer, since the console gets
Kent> so slow, try running ls /dev if you are using framebuff
> If one can change the refreshrate with framebuffer, then i might give it a
> try.
>
if there is a native driver for your card, then you can change the
refresh rate with fbset.
if not, then you must use the vesa driver - and this one does not support
mode selection via fbset. the mode is set befo
I am using vga=9 on at the moment in my lilo.conf .
I would like to use the next mode, but my my eyes dont like the low
refreshrate :(
I dont use framebuffer, since the console gets so slow, try running ls
/dev if you are using framebuffer at 1280x1024 :(
Well, i dont like framebuffer at all
Quoting Alex Kwan ([EMAIL PROTECTED]):
>
> After I using dpkg -i to install kernel image
> (kernel-image-2.2.14-ide_2.2.14-3.deb),
> Do I need modify the /etc/lilo.conf to config the system to use this new
> kernel?
Only if the parameters are now wrong, and need changing.
What *i
Hi!
After I using dpkg -i to install kernel image
(kernel-image-2.2.14-ide_2.2.14-3.deb),
Do I need modify the /etc/lilo.conf to config the system to use this new
kernel?
Thanks
x338,SoundScape
> sbpcd-0 [12]: with your REAL address.
> sbpcd-0 [13]: = = = = = = = = = = END of WARNING = = = = = == = = =
>
> my /etc/lilo.conf looks like this:
> boot=/dev/hda1
> root=/dev/hda1
> install=/boot/boot.b
> map=/boot/map
> vga=normal
> delay=20
&g
sbpcd-1 [17]: You should read linux/Documentation/cdrom/sbpcd
> sbpcd-1 [18]: and then configure sbpcd.h for your hardware.
^
File is located /linux/drivers/cdrom/sbpcd.h
>
> my /etc/lilo.conf looks like this:
> boot=/dev/hda1
> ro
d-1 [17]: You should read linux/Documentation/cdrom/sbpcd
sbpcd-1 [18]: and then configure sbpcd.h for your hardware.
my /etc/lilo.conf looks like this:
boot=/dev/hda1
root=/dev/hda1
install=/boot/boot.b
map=/boot/map
vga=normal
delay=20
image=/vmlinuz
label=Linux
read-only
sbpcd=0x
Joseph de los Santos wrote:
>
> I have installed debian to coexist with windows 98 but I can no longer
> boot windows. my lilo.conf only shows linux.it automatically boots linux and
> the windows partition is no where to be found. worse, I even forgot to label
> my window
On 27-Jan-2000 [EMAIL PROTECTED] wrote:
> If you installed lilo on the mbr, you could modify /etc/lilo.conf adding
> the win98 partitions.
> In this moment I don't remember the exact syntax, (I am working on WINNT4.0
> now),
> but you could look for it in "/usr/doc/lilo
Could you attach, please, your lilo.conf?
a.
On Thu, 27 Jan 2000, Joseph de los Santos wrote:
> Hello,
>
> I have installed debian to coexist with windows 98 but I can no longer
> boot windows. my lilo.conf only shows linux.it automatically boots linux and
&
If you installed lilo on the mbr, you could modify /etc/lilo.conf adding
the win98 partitions.
In this moment I don't remember the exact syntax, (I am working on WINNT4.0
now),
but you could look for it in "/usr/doc/lilo" or 'man lilo'
When you will modify "/e
Hello,
I have installed debian to coexist with windows 98 but I can no longer
boot windows. my lilo.conf only shows linux.it automatically boots linux and
the windows partition is no where to be found. worse, I even forgot to label
my windows partition. is there a way this can be fixed
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
ilities 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&qu
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
) 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)
valid boot image, see below.
>
> Anyone who have gone through this before? The suse 6.3 installation
> did not cover this case. Also reading the lilo and lilo.conf man-pages
> did not give sufficient info to resolve this issu (at least not for me).
>
> On hda/suse / is mou
suse 6.3 installation
did not cover this case. Also reading the lilo and lilo.conf man-pages
did not give sufficient info to resolve this issu (at least not for me).
On hda/suse / is mounted on hda6 and /boot on hda1.
On sda/debian / is mounted on sda1.
For lilo.conf files and info see below
1 - 100 of 136 matches
Mail list logo
