So What info is required in order to troubleshoot this problem?
Or is it a bug?
Nasa
On Fri, 2003-08-15 at 20:40, Nathan A. Smith wrote:
> Hi,
>
> I am getting the following error when I try to run lilo:
>
> Warning: '/proc/partitions' does not match '/dev' directory structure.
> Name cha
On Mon, Aug 11, 2003 at 04:42:17PM +0200, Svetoslav Slavtchev wrote:
> shouldn't urpme/ rpm -e remove the entries on uninstall ?
It does unless it's been broken recently.
--
Ben Reser <[EMAIL PROTECTED]>
http://ben.reser.org
"What upsets me is not that you lied to me, but that from now on I ca
"bjørn" <[EMAIL PROTECTED]> writes:
> well,, I have 2 problems with lilo now,
> 1. It cant have more than 11 images (I use it with this mandrake theme)
>
> 2. If you uninstall the defolt kernel (the one that 9.1 come with).
> That kernel is linked to "22 Jul 23 07:07 initrd.img ->
> initrd-2.4.21
Quoting Pixel <[EMAIL PROTECTED]>:
> "bjørn" <[EMAIL PROTECTED]> writes:
>
> > well,, I have 2 problems with lilo now,
> > 1. It cant have more than 11 images (I use it with this mandrake theme)
text-mode lilo is limited to 24 if i remember correctly,
and yes i did run several times in :
"ERROR
Tibor Pittich <[EMAIL PROTECTED]> writes:
> On 30. sep 2002 11:52, Guillaume Rousse wrote:
>
> > Le Lundi 30 Septembre 2002 11:30, Tibor Pittich a écrit :
>
> > > i can't find lilo binary when i booted from 1st cd in rescue mode. grub
> > > is included (wow, gpart too :) ), but lilo don't. it
Le Lundi 30 Septembre 2002 12:44, Tibor Pittich a écrit :
> On 30. sep 2002 11:52, Guillaume Rousse wrote:
> > Le Lundi 30 Septembre 2002 11:30, Tibor Pittich a écrit :
> > > i can't find lilo binary when i booted from 1st cd in rescue mode. grub
> > > is included (wow, gpart too :) ), but lilo d
Guillaume Rousse wrote:
> Le Lundi 30 Septembre 2002 11:30, Tibor Pittich a écrit :
>
>>hello
>>
>>i can't find lilo binary when i booted from 1st cd in rescue mode. grub
>>is included (wow, gpart too :) ), but lilo don't. it is accident or on
>>purpose ?
>
> Why should it be included ? Mount yo
On 30. sep 2002 11:52, Guillaume Rousse wrote:
> Le Lundi 30 Septembre 2002 11:30, Tibor Pittich a écrit :
> > i can't find lilo binary when i booted from 1st cd in rescue mode. grub
> > is included (wow, gpart too :) ), but lilo don't. it is accident or on
> > purpose ?
> Why should it be inc
Le Lundi 30 Septembre 2002 11:30, Tibor Pittich a écrit :
> hello
>
> i can't find lilo binary when i booted from 1st cd in rescue mode. grub
> is included (wow, gpart too :) ), but lilo don't. it is accident or on
> purpose ?
Why should it be included ? Mount your / partition from disk, it should
On Tue Sep 24 23:32 +0200, Pieter Kubben wrote:
> bob and paul, thanks... I felt an idiot, but now it works fine... now
> 'just' the mouse problem
*Insert flame from GRUB user*... :o)
--
Levi Ramsey
[EMAIL PROTECTED] [EMAIL PROTECTED]
Love lies in pools of questions.
Currently p
x27; the mouse problem
>
> best regards,Pieter
>
> -Original Message-
> From: [EMAIL PROTECTED]
> [mailto:[EMAIL PROTECTED]] On Behalf Of Litwack, Paul
> Sent: dinsdag 24 september 2002 21:24
> To: '[EMAIL PROTECTED]'
> Subject: RE: [Cooker] LILO:
ECTED]'
Subject: RE: [Cooker] LILO: change OS order & default in RC3 [pieter78]
I don't mean to be cute, but did you remember to execute the lilo
program after changing the config file?
-Original Message-
From: Pieter Kubben [mailto:[EMAIL PROTECTED]]
Sent: Tuesday, S
I don't mean to be cute, but did you remember to execute the lilo program
after changing the config file?
-Original Message-
From: Pieter Kubben [mailto:[EMAIL PROTECTED]]
Sent: Tuesday, September 24, 2002 11:16 AM
To: Mandrake Linux Cooker List
Subject: [Cooker] LILO: change OS order & d
Did you run 'lilo' after the change?
bob
On Tuesday 24 September 2002 11:15 am, Pieter Kubben wrote:
> Hello,
>
> I am not sure if this is a bug (it might be one called my name ;-) ) but
> I cannot change Lilo's OS order and default OS. I su'd as a root and
> used
>
> > emacs /etc/lilo.conf
>
>
David Walser <[EMAIL PROTECTED]> writes:
> > oh, i drop support for non-lba32 at install, and
> > this will not bother
> > us again
>
> But you don't need lba32 if you make a /boot partition
> < 1024 cylinders (like at the beginning of the drive)
> :o(
you don't need it, but it doesn't break on
But you don't need lba32 if you make a /boot partition
< 1024 cylinders (like at the beginning of the drive)
:o(
If it was possible to detect that and not use lba32
then that'd be cool, dunno how hard it'd be.
--- Pixel <[EMAIL PROTECTED]> wrote:
> oh, i drop support for non-lba32 at install, an
Aurélien Bompard <[EMAIL PROTECTED]> writes:
> Hi all
>
> I've changed my boot options with drakconf, and it added the "geometric"
> option in lilo.conf, thus preventing lilo to install, since I have a debian
> partition after the 1024th cylinder.
> In the man page, lilo seems to use lba32 by
"Brian J. Murrell" <[EMAIL PROTECTED]> writes:
> Warning: Kernel & BIOS return differing head/sector geometries for
> device 0x80
> Kernel: 38792 cylinders, 16 heads, 63 sectors
> BIOS: 1023 cylinders, 255 heads, 63 sectors
> Added linux *
> Added single,nodevfs
> Added single
> Added f
[EMAIL PROTECTED] wrote on Sat, Jul 06, 2002 at 01:00:10AM -0400 :
> Look up the "optional" flag under man lilo.conf_but_ personally I'd
Sweet, I didn't even notice that it was added with the optional flag.
Thanks.
Blue skies... Todd
--
Todd Lyons -- MandrakeSoft, Inc. http:
Look up the "optional" flag under man lilo.conf_but_ personally I'd
rather have lilo fail if i typo the config file...if it was called by
a script, you could evaluate the exit code and restore a backup boot
sector.
On Fri, 5 Jul 2002, Todd Lyons wrote:
> Date: Fri, 5 Jul 2002 21:45:10 -07
<[EMAIL PROTECTED]> writes:
> i run drakboot at console text mode to config lilo.
> and i found that if lilo.conf contain the line with "vga="
> then drakboot will seg fault when i press "down".
> if lilo.conf has no "vga=" line, console drakboot seems work well.
bug accepted. will get f
÷ ÷ÓË, 10.03.2002, × 11:26, SI Reasoning ÎÁÐÉÓÁÌ:
> I have the following lilo error:
> [root@dl380 sczjd]# lilo
> Fatal: open /dev/ida/c0d0: Is a directory
>
Did installer put it in?
> [root@dl380 ida]# cd c0d0
> [root@dl380 c0d0]# d
> disc part1 part2 part5 part6 part7 part8 part9
>
>
> "guillaume" == Guillaume Cottenceau <[EMAIL PROTECTED]> writes:
guillaume> Pixel <[EMAIL PROTECTED]> writes:
>> Borsenkow Andrej <[EMAIL PROTECTED]> writes:
>>
>> > Warning: Int 0x13 function 8 and function 0x48 return different
>> > head/sector geometries for BIOS drive 0x80
>> >
>> > ev
On Tue, Feb 19, 2002 at 09:02:37AM +0300, Borsenkow Andrej wrote:
>
> >
> > When lilo locates more kernels in /boot
> > and generates appropiate entries in /etc/lilo.conf
>
> lilo does not locate or generate anything.
Well, then somebody does for lilo, maybe DrakX.
Keld
>
> When lilo locates more kernels in /boot
> and generates appropiate entries in /etc/lilo.conf
lilo does not locate or generate anything.
-andrej
Keld Jørn Simonsen <[EMAIL PROTECTED]> writes:
> When lilo locates more kernels in /boot
> and generates appropiate entries in /etc/lilo.conf
> it generates lines with initrd that are the standard
> initrd instead of looking of an initrd with the
> same version as the kernel in question. I woul
Pixel <[EMAIL PROTECTED]> writes:
> Borsenkow Andrej <[EMAIL PROTECTED]> writes:
>
> > Warning: Int 0x13 function 8 and function 0x48 return different
> > head/sector geometries for BIOS drive 0x80
> >
> > everything seems to work (I can boot :-) Anything to worry about?
>
> i don't think so.
Op do 31-01-2002, om 12:10 schreef Neuromancer:
>
> Yep. I wonder why they decided on that?
>
> -Russ
Windows uses also 16 colors(don't know the size at the to of my head).
This makes it almost certain to work
On Thu, Jan 31, 2002 at 11:06:36AM +0100, François Pons wrote:
> Look at /boot/lilo, where does it points ? Do you have modified it by hand ?
> (possible values are currently lilo-text, lilo-graphic, lilo-menu, lilo-bmp).
Argh, oups, shame on me: you were right: I don't know how it happens,
lilo
>
> But really, don't you think 640x480 (or even 800x600) in 256 colors is
not
> better ?
>
As Mandrake managed to prove it depends :-)
Neuromancer <[EMAIL PROTECTED]> writes:
> Thus spake François Pons about Life, the Universe, and Everything:
> | Look at /boot/lilo, where does it points ? Do you have modified it by hand ?
> | (possible values are currently lilo-text, lilo-graphic, lilo-menu, lilo-bmp).
>
> Out of curiosity, wh
Gregoire Favre <[EMAIL PROTECTED]> writes:
> > if that is the case, re-install lilo cleanly (eg: rpm -i lilo-22*.rpm --force)
> > and it should work.
>
> No: rpm -i lilo-22.1-4mdk.i586.rpm --force
> lilo
> Fatal: First boot sector is version 21.7. Expecting version 22.1.
> rpm -e lilo and then r
Borsenkow Andrej <[EMAIL PROTECTED]> writes:
> Warning: Int 0x13 function 8 and function 0x48 return different
> head/sector geometries for BIOS drive 0x80
>
> everything seems to work (I can boot :-) Anything to worry about?
i don't think so. AFAIK when using LBA32 you don't have to worry abou
On Wed, Jan 30, 2002 at 01:23:39AM +0100, Pixel wrote:
> > Fatal: First boot sector is version 21.7. Expecting version 22.1.
>
> i'd say you have a seperate /boot where there is an old /boot/boot.b, whereas
> /sbin/lilo is more up to date
Yep:
rpm -V lilo gives:
.M.. g /boot/lilo
Exit 1
>
Gregoire Favre <[EMAIL PROTECTED]> writes:
> and lilo
> 29.01 22:02
> Fatal: First boot sector is version 21.7. Expecting version 22.1.
i'd say you have a seperate /boot where there is an old /boot/boot.b, whereas
/sbin/lilo is more up to date
try "rpm -V lilo" to verify that things are weird.
Am Mon, 2002-01-28 um 17.30 schrieb Guillaume Cottenceau:
> suka_at <[EMAIL PROTECTED]> writes:
>
> > Will the new Lilo-Bootscreen stay like it is now? Because the image is
> > really dead ugly now (even the old one was better), and the font looks
>
> Agreed.
>
> > very dirty, the shadow makes
suka_at <[EMAIL PROTECTED]> writes:
> Will the new Lilo-Bootscreen stay like it is now? Because the image is
> really dead ugly now (even the old one was better), and the font looks
Agreed.
> very dirty, the shadow makes it nearly unreadable.
>
> I hope this changes, as the rest of the artwork
"J.P. Pasnak" <[EMAIL PROTECTED]> writes:
> On January 28, 2002 05:30 am Guillaume Rousse said:
>
> >Ainsi parlait J.P. Pasnak :
> >> !,
> >>
> >> rpm -Uvh lilo-22.1-3mdk.i586.rpm
> >> Preparing...###
> >> [100%] 1:lilo
>
On January 28, 2002 05:30 am Guillaume Rousse said:
>Ainsi parlait J.P. Pasnak :
>> !,
>>
>> rpm -Uvh lilo-22.1-3mdk.i586.rpm
>> Preparing...###
>> [100%] 1:lilo
>> ### [100%] Warning
Ainsi parlait J.P. Pasnak :
> !,
>
> rpm -Uvh lilo-22.1-3mdk.i586.rpm
> Preparing...###
> [100%] 1:lilo ###
> [100%] Warning: 'menu-scheme' not supported by boot loader
>
> Before I re
andre <[EMAIL PROTECTED]> writes:
> The new lilo shows only 7 entries for me and that is used to few for me.
> Could we go back to the previous version. It looked also better
The latest lilo in cooker contains 9 entries visible and now allow simple
scrolling (lilo-22.1-3mdk).
François.
>
> andre <[EMAIL PROTECTED]> writes:
>
> > So if i copy the message file from 8.0 it will be displayed as it was in
> > 8.0
>
> Yes, but re-run lilo for changes to be valid.
>
> François.
>
And is there also somewhere information on how to make a message file?
andre <[EMAIL PROTECTED]> writes:
> So if i copy the message file from 8.0 it will be displayed as it was in
> 8.0
Yes, but re-run lilo for changes to be valid.
François.
Op di 22-01-2002, om 17:58 schreef François Pons:
> andre <[EMAIL PROTECTED]> writes:
>
> > The new lilo shows only 7 entries for me and that is used to few for me.
> > Could we go back to the previous version. It looked also better
>
> Everything is in the message file itself, if you drop it (o
andre <[EMAIL PROTECTED]> writes:
> The new lilo shows only 7 entries for me and that is used to few for me.
> Could we go back to the previous version. It looked also better
Everything is in the message file itself, if you drop it (or change it with
another version) it will be correct.
It will
Guillaume Cottenceau <[EMAIL PROTECTED]> writes:
[...]
> > When installing Mandrake on a mixed system, SCSI and IDE drives, and the
> > system is set to boot off the SCSI drives, LILO writes the boot device as
> > /dev/hdc. It should be /dev/sda.
>
> There is no way from DrakX to know if the BI
"Pete" <[EMAIL PROTECTED]> writes:
[...]
> Yes it does ask, but still seems to pick an ide drive. I had a similar
> problem.
> Scenario:
> Mixed ide/scsi system booting from /dev/sda running cooker. Used urpmi
> --auto-select to update cooker. This installed a new kernel and updated
> lilo.conf
sure it was something I
missed, then OK that's fine. If not, I'm just trying to help make a
wonderful distro better:)
Steve
-Original Message-
From: Guillaume Cottenceau [mailto:[EMAIL PROTECTED]]
Sent: Monday, November 26, 2001 9:53 AM
To: [EMAIL PROTECTED]
Subject: Re:
"Thomas, Stephen W-CONT" <[EMAIL PROTECTED]> writes:
> I had this problem last night when installing 8.1 It may be fixed in cooker,
> but just in case
>
> When installing Mandrake on a mixed system, SCSI and IDE drives, and the
> system is set to boot off the SCSI drives, LILO writes the boo
Borsenkow Andrej wrote:
>>I had this problem last night when installing 8.1 It may be fixed in
>>cooker,
>>but just in case
>>
>>When installing Mandrake on a mixed system, SCSI and IDE drives, and
>>
>the
>
>>system is set to boot off the SCSI drives, LILO writes the boot device
>>
>as
>
>>/
>
> I had this problem last night when installing 8.1 It may be fixed in
> cooker,
> but just in case
>
> When installing Mandrake on a mixed system, SCSI and IDE drives, and
the
> system is set to boot off the SCSI drives, LILO writes the boot device
as
> /dev/hdc. It should be /dev/sda.
>
Daouda LO <[EMAIL PROTECTED]> writes:
> Guillaume Rousse <[EMAIL PROTECTED]> writes:
>
> > Ainsi parlait Guillaume Rousse :
> > > While trying to re-install cooker:
> > > Fatal: can't put the boot sector on logical partition 0x305
> > > I use reiserFS on every partition, but it worked well befor
Guillaume Rousse <[EMAIL PROTECTED]> writes:
> Ainsi parlait Guillaume Rousse :
> > While trying to re-install cooker:
> > Fatal: can't put the boot sector on logical partition 0x305
> > I use reiserFS on every partition, but it worked well before...
>
> Solved : it was just missing
> boot=/dev
> Anyway, it seems to be a bug in new DrakX (build just one or two days ago).
Well, Pixel did warn us :P!
Ainsi parlait Guillaume Rousse :
> While trying to re-install cooker:
> Fatal: can't put the boot sector on logical partition 0x305
> I use reiserFS on every partition, but it worked well before...
Solved : it was just missing
boot=/dev/hda in /etc/lilo.conf
Anyway, it seems to be a bug in new D
> there is a bug in installer (both in Mdk8 and cooker) - I have selected
> "Graphical menu" but still got just text menu. I have lilo-0.21.7-11mdk -
> is it the latest?
the lilo files names had changed, we need to update drakx according to
this.
will be done asap.
yves
--
Yves Duret
[EMAIL PR
On Sat, 5 May 2001, SI Reasoning wrote:
> Since the last lilo upgrade I have not been able to
> get it to work with either text or graphical menu. I
> have manually linked it to the directory of choice and
> also tried to get it to work through the interace in
> drakconf. I can get grub to work f
On 27 Apr 2001, François Pons wrote:
> Sebastian Dransfeld <[EMAIL PROTECTED]> writes:
>
> > Could you do
> >
> > 'mv /boot/message /boot/message-text'
> >
> > And then symlink the right message (message-graphic or message-text) to
> > message?
>
> We will do something like symlinking a directory
Sebastian Dransfeld <[EMAIL PROTECTED]> writes:
> Could you do
>
> 'mv /boot/message /boot/message-text'
>
> And then symlink the right message (message-graphic or message-text) to
> message?
We will do something like symlinking a directory where the right stage2 and its
message file are store
Armisis Aieoln <[EMAIL PROTECTED]> writes:
> Fatal: open /boot/initrd.img: No such file or directory
humm you did a bad kernel update here ?
--
MandrakeSoft Inc http://www.chmouel.org
--Chmouel
"Tim" <[EMAIL PROTECTED]> writes:
> Tried to install last night and I'm not sure if I caught the mirror in the
> middle of an update or what, but when the install got to the "Install Boot
> Loader" option I got an error message to the tune of "NOT AN ARRAY VALUE."
> Unfortunately, this means that
> Um, some of us don't like full-screen boot logos on another os because we
> like to see the start-up stuff.
>
> Matthew
Read the message. Besides if you have ever used Aurora it does cover over
the messages. What I said was twofold: #1 Make sure Aurora stays visible
(if in init 5) until kdm st
When you click on an icon it pops up the text - maybe reserve a couple
centimeters on the bottom of the screen to display these all the time,
rather than have to click on moving icons? Just a thought.
V.
OS wrote:
>
> I think all that space below the penguin could be put to more use. For
> exa
I think all that space below the penguin could be put to more use. For
example telling us the progress of e2fsck. When disk check is forced the boot
screen goes alarmingly blank, especially for a 'newbie'. Before Aurora went
Mandrake changes were put in to do just this, but they have now disapp
Um, some of us don't like full-screen boot logos on another os because we
like to see the start-up stuff.
Matthew
- Original Message -
From: David Walluck <[EMAIL PROTECTED]>
To: <[EMAIL PROTECTED]>
Sent: Friday, February 09, 2001 11:49 AM
Subject: Re: [Cooker] Lilo B
On Fri, 9 Feb 2001, Frederic Crozat wrote:
>
> Be patient, young Skywalker, be patient :))
>
Even with Aurora I can still see all the kernel messages on tty1 before
kdm starts. Can't we start kdm in the background and wait for it to be up,
and then switch over from Aurora in a way that looks se
Hi,
Dans l'article <[EMAIL PROTECTED]>,
[EMAIL PROTECTED] a écrit :
> The boot of Cooker with will aurora is very beautiful, but why not add
> in more one image on LILO,
> with MKLILOMSG MKLILOMSG uses an image PCX (256 color palette)
Be patient, young Skywalker, be patient :))
--
Frédéric C
I would prefer postinstall script limitis itself to warn user he has to
run lilo, not running it itself. If lilo.conf is not in a valid state,
result could be rather dangereous.
--
Guillaume Rousse
Murphy's law : If anything can go wrong, it will.
O'Tool's commentary : Murphy was an optimist.
---
Guillaume Rousse <[EMAIL PROTECTED]> writes:
> Pixel a écrit :
>
> > ben c'est ce qu'est fait!
> ^^^
> french speaking forbidden here ! Pan sur le bec ! :-)
sorry, i thought it was chmouel-sent only :-/
>
> > %post
> > if [ -f /etc/lilo.conf ]; then
> > if [ -x /usr/
Pixel a écrit :
> ben c'est ce qu'est fait!
^^^
french speaking forbidden here ! Pan sur le bec ! :-)
> %post
> if [ -f /etc/lilo.conf ]; then
> if [ -x /usr/sbin/detectloader ]; then
> LOADER=$(/usr/sbin/detectloader)
> if [ "$LOADER" = "LILO" ]; then
> /
Chmouel Boudjnah <[EMAIL PROTECTED]> writes:
> Guillaume Rousse <[EMAIL PROTECTED]> writes:
>
> > -why automatically run lilo once installed ? Other softs are not
> > automatically launched after installation.
>
> yup pixel why not putting a :
>
> detectloader = LILO ? /sbin/lilo : true ?
ben
Guillaume Rousse <[EMAIL PROTECTED]> writes:
> -why automatically run lilo once installed ? Other softs are not
> automatically launched after installation.
yup pixel why not putting a :
detectloader = LILO ? /sbin/lilo : true ?
--
MandrakeSoft Inc http://www.chmouel.org
On Mon, 4 Dec 2000, Guillaume Rousse wrote:
> I upgraded everything i could this week-end (i love bleeding-edge !) and
> i'm rather surprised everything seems to be ok for the moment...
[snip]
> -how to remove double identical entries in rpm database ?
> [root@agathe RPMS]# rpm -e lilo-0.21.6-5
cc:
cooker-owner@linux-maSubject: Re: [Cooker] Lilo RPM
small problem
ndra
"Sergio P. Korlowsky" <[EMAIL PROTECTED]> writes:
> Use your windows floppy boot diskette and run fdisk /MBR
> to gain access to windows again.
>
> Then use your floppy diskette to login into Linux... (your Linux diskette of course!)
> the one you made when installed Linux.
>
> start linux and
On Tue, 26 Sep 2000, you wrote:
> I just tried to reboot into windows for the first time since I installed
> beta 3 to play a game, and noticed that lilo wont let me boot into it.
> when I choose that particular option, it freezes. Can anyone clue me
> in?
Use your windows floppy boot diskette
> I just tried to reboot into windows for the first time since I installed
> beta 3 to play a game, and noticed that lilo wont let me boot into it.
> when I choose that particular option, it freezes. Can anyone clue me
> in?
>
Log into Linux as root and write 'lilo'. If you get error messages or
Pedro Rosa wrote:
>
> Ellick Chan wrote:
> >
> > On Fri, 21 Jul 2000, David Delyn wrote:
> >
> > > Date: Fri, 21 Jul 2000 19:04:35 +0930
> > > From: David Delyn <[EMAIL PROTECTED]>
> > > To: [EMAIL PROTECTED]
> > > Subject: [Cooker] Lilo - Grub Problem
> > >
> > > Hi
> > > Perhaps one of your pro
Ellick Chan wrote:
>
> On Fri, 21 Jul 2000, David Delyn wrote:
>
> > Date: Fri, 21 Jul 2000 19:04:35 +0930
> > From: David Delyn <[EMAIL PROTECTED]>
> > To: [EMAIL PROTECTED]
> > Subject: [Cooker] Lilo - Grub Problem
> >
> > Hi
> > Perhaps one of your programmers can find the solution to this pr
LINK WORLD <[EMAIL PROTECTED]> writes:
> sda: 1 GB SCSI on a Adaptec 1542 controller (FAT
> 16)
> sdb: 1 GB SCSI on the same controller (Mandrake
> Linux)
> The LILO wont work.
>
> I get a continous screen of 0's & 1s, wether I set the LILO
Robert L Martin <[EMAIL PROTECTED]> writes:
> > by default DrakX tries to install lilo/grub on the first disk. Of
> > course, it
> > doesn't know wether you have switched boot disk in the bios...
>
>
> Drakx should ask when
by default DrakX tries to install lilo/grub on the first disk. Of
course, it
doesn't know wether you have switched boot disk in the bios...
Drakx should ask when mulitple hds are present. Retail box users
if they RTFM will h
David Delyn <[EMAIL PROTECTED]> writes:
> and have made space on their new second HDD for linux, and therefore the Lilo
> setup either will not install or installs in the wrong place. Hence when they
what do you mean? on which mbr do you want lilo/grub to be installed? first disk
or second disk
On Fri, 21 Jul 2000, David Delyn wrote:
> Date: Fri, 21 Jul 2000 19:04:35 +0930
> From: David Delyn <[EMAIL PROTECTED]>
> To: [EMAIL PROTECTED]
> Subject: [Cooker] Lilo - Grub Problem
>
> Hi
> Perhaps one of your programmers can find the solution to this problem, it's
> one i find myself fixing
Fleischman" <[EMAIL PROTECTED]>
To: <[EMAIL PROTECTED]>
Sent: Thursday, June 01, 2000 6:55 PM
Subject: Re: [Cooker] lilo problems
> Question, probably not related. I have tried doing hdparm with a couple
> different -X values (66/68) with the -d 1 (dma) and it has locked u
One WD 20.5Gb ATA/66 7200rpm harddrive. /dev/hde
Only partitions I have are:
/boot /dev/hde1 ~30Mb
/ /dev/hde2 ~5GB
/dev/hde3 ~256Mb
/home /dev/hde4 ~14+Gb
Why is it trying to open /dev/hda
Brian Fleischman <[EMAIL PROTECTED]> writes:
> open("/dev/hda", O_RDWR)= -1 EROFS (Read-only file system)
this is strange, what partitions do you have?
Attached is my trace and lilo.conf. I am trying to get kernel -12 version
loaded. I did a network "upgrade" and it downloaded the -12 kernel version. This
is the exact error message displayed:
[root@brian /tmp]# strace -o /tmp/trace lilo -v
LILO version 21.4-3, Copyright (C) 1992-1998 Werner A
Thanks, I will check this out as soon as I get a chance and forward on my
lilo.conf
-Brian
Pixel wrote:
> Brian Fleischman <[EMAIL PROTECTED]> writes:
>
> > I am having a problem with lilo. I get a fatal error message like the
> > following when I try to do a lilo -v
> >
> > Fatal: /dev/hde fi
Thanks for the feedback.
No virus checkers, turned firewall and ipchains off. I installed at
Security level 4(High). What that means, I am not too sure. Tried it
again (lilo -v), no luck, same error message. Something like:
Fatal: read /dev/hde filesystem read-only
Thanks,
Brian
Guillaume
Brian Fleischman <[EMAIL PROTECTED]> writes:
> I am having a problem with lilo. I get a fatal error message like the
> following when I try to do a lilo -v
>
> Fatal: /dev/hde filesystem is read-only
can you give your lilo.conf and the strace (do "strace -o /tmp/trace lilo -v"
and take /tmp/tr
Walter Lee Queen II <[EMAIL PROTECTED]> writes:
> do you have any virus checkers , firewalls, or any utilities that
> prevent unauthorized use?
IPchains is a firewall.
on the commercial cd there is a virus checker as far as i know.
or else, install in "paranoid" security level. this will prev
do you have any virus checkers , firewalls, or any utilities that
prevent unauthorized use?
yes it works with windows 2000/98/Millennium
-Original Message-
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]]
Sent: Saturday, May 06, 2000 10:29 AM
To: [EMAIL PROTECTED]
Cc: Mandrake Cooker E-Mail List (E-mail)
Subject: Re: [Cooker] LILO Installation Question/Problem
"J.
it would be
right now.
-Original Message-From:
[EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]]On
Behalf Of rootSent: Saturday, May 06, 2000 11:18
AMTo: [EMAIL PROTECTED]Subject: Re: [Cooker]
LILO Installation Question/ProblemWell, I specified grub
during the install and I used
Well, I specified grub during the install and I used /dev/hde bios=0x80
as the device option. On reboot, I got my standard Windows 2000 boot.ini
menu. Grub apparently is not there. Any thoughts?
Pixel wrote:
"J. Keith Wedinger" <[EMAIL PROTECTED]> writes:
> My question is: where/how should I
"J. Keith Wedinger" <[EMAIL PROTECTED]> writes:
> Sure. But first...
>
> How does grub interact with Windows 2000/Windows 98? Can it handle
> dual-booting with these OS's?
> I guess my real question is...where can I find more information on grub?
its documentation (info) is quite nice :)
ssage-
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]]
Sent: Saturday, May 06, 2000 11:31 AM
To: [EMAIL PROTECTED]
Cc: [EMAIL PROTECTED]
Subject: Re: [Cooker] LILO Installation Question/Problem
"J. Keith Wedinger" <[EMAIL PROTECTED]> writes:
> My question is: where/how should I
Message-
From: Mycroft [mailto:[EMAIL PROTECTED]]
Sent: Saturday, May 06, 2000 10:53 AM
To: [EMAIL PROTECTED]
Subject: RE: [Cooker] LILO Installation Question/Problem
Crazy as it sounds, enable the 'LINEAR' option. You know, the one that
says it is for "Some SCSI Drives"
This is
"J. Keith Wedinger" <[EMAIL PROTECTED]> writes:
> My question is: where/how should I install LILO so that it works with the
> master HD on my Promise controller. This HD (/dev/hde) has the following on
> it:
could you test with grub instead of lilo?
also test with "disk=/dev/hde bios=0x80"
1 - 100 of 106 matches
Mail list logo
