On Sat, Oct 2, 2010 at 10:07 PM, Stephen Powell wrote:
>
> There are a couple of ways. One way is to use the blkid command.
> For example,
>
> blkid /dev/sda2
>
> will return the uuid of /dev/sda2. The other way is to issue
>
> ls -Al /dev/disk/by-uuid/
>
> which will list all the udev-created s
On Sat, 02 Oct 2010 13:54:11 -0400 (EDT), bri...@aracnet.com wrote:
> Stephen Powell wrote:
>> Right now, it's only a working setup for one kernel: 2.6.32-5-amd64.
>> If you're not going to make these changes, you might as well
>> de-install the other kernels. They will not boot, so what good are
On Tue, 28 Sep 2010 11:20:46 -0400 (EDT)
Stephen Powell wrote:
> If I recall correctly, you got farther with this one than you did
> with the one that had a missing initrd entry. You were able to
> boot this one with a root file system override, whereas the one
> with the missing initrd entry wo
On Mon, 27 Sep 2010 21:19:28 -0400 (EDT), bri...@aracnet.com wrote:
> On Mon, 27 Sep 2010 10:09:15 -0400 (EDT), Stephen Powell wrote:
>>
>> You had several unrelated problems.
>>
>> (1) The initial RAM disk specifications were missing from the two
>> boot menu items in /etc/lilo.conf that used th
On Mon, 27 Sep 2010 10:09:15 -0400 (EDT)
Stephen Powell wrote:
> On Sun, 26 Sep 2010 21:27:37 -0400 (EDT), bri...@aracnet.com wrote:
> >
> > and. IT WORKS !
> >
> > Talking to you from a freshly booted machine :-)
> >
> > First time it's booted properly in quite sometime.
> >
> > I'm not
On Sun, 26 Sep 2010 21:27:37 -0400 (EDT), bri...@aracnet.com wrote:
>
> and. IT WORKS !
>
> Talking to you from a freshly booted machine :-)
>
> First time it's booted properly in quite sometime.
>
> I'm not really clear on what exactly fixed things, although those
> missing initrd lines we
On Sun, 26 Sep 2010 20:01:36 -0400 (EDT)
Stephen Powell wrote:
> >> I also don't see any zz-lilo hook scripts, which the latest version
> >> of lilo would have installed. Reinstall the latest version of
> >> lilo. This should also install a file
> >> in /etc/initramfs/post-update.d called lilo o
On Sun, 26 Sep 2010 19:51:12 -0400 (EDT)
Stephen Powell wrote:
> > # Kernel image management overrides
> > # See kernel-img.conf(5) for details
> > do_symlinks = no
> > relative_links = yes
> > do_bootloader = no
> > do_bootfloppy = no
> > do_initrd = yes
> > link_in_boot = yes
> > postinst_hook
On Sun, 26 Sep 2010 22:29:34 -0400 (EDT), bri...@aracnet.com wrote:
> On Sat, 25 Sep 2010 12:28:00 -0400 (EDT), Stephen Powell wrote:
>>
>> Several problems here. S30initramfs, S50symlink_hook,
>> K30initramfs, and K50symlink_hook, though they will still
>> work, I now consider obsolete. S30initr
On Sun, 26 Sep 2010 22:14:29 -0400 (EDT), bri...@aracnet.com wrote:
> On Sat, 25 Sep 2010 12:28:00 -0400 (EDT), Stephen Powell wrote:
>> I'm also going to need
>> to see the output of the following commands:
>>
>>ls -Al /dev/disk/by-id/
>
> lrwxrwxrwx 1 root root 9 Sep 26 18:12
> ata-WDC_WD
On Sat, 25 Sep 2010 12:28:00 -0400 (EDT)
Stephen Powell wrote:
>
> Several problems here. S30initramfs, S50symlink_hook,
> K30initramfs, and K50symlink_hook, though they will still
> work, I now consider obsolete. S30initramfs and K30initramfs
> were made obsolete by newer versions of the init
On Sat, 25 Sep 2010 12:28:00 -0400 (EDT)
Stephen Powell wrote:
> On Sat, 25 Sep 2010 03:40:04 -0400 (EDT), bri...@aracnet.com wrote:
> I'm also going to need
> to see the output of the following commands:
>
>ls -Al /dev/disk/by-id/
lrwxrwxrwx 1 root root 9 Sep 26 18:12 ata-WDC_WD2500YS-01
On Sat, 25 Sep 2010 03:40:04 -0400 (EDT), bri...@aracnet.com wrote:
>
> Before I post all that stuff, let me show you exactly what's happening
> on boot. I think there is something very strange going on and it may
> not be lilo.
>
> Lin_img0 is : /boot/vmlinuz
>
> When I boot using that entry
On Sat, 25 Sep 2010 00:54:12 -0400 (EDT), Stan Hoeppner wrote:
> Stephen Powell put forth on 9/24/2010 4:06 PM:
>> Current stock Debian kernels for the
>> amd64 architecture are right on the ragged edge of being too
>> large for lilo to load below the 16M line
>
> And the bulk of these ~16MB stock
On Sat, 25 Sep 2010 00:17:30 -0500
Stan Hoeppner wrote:
> bri...@aracnet.com put forth on 9/24/2010 7:42 PM:
>
> > right now I'm thinking I've got something misconfigured, but what ??
> > Running lilo manually should fix whatever's going on and it most
> > certainly isn't.
>
> Did you possibly
On Fri, 24 Sep 2010 21:18:25 -0400 (EDT)
Stephen Powell wrote:
Before I post all that stuff, let me show you exactly what's happening
on boot. I think there is something very strange going on and it may
not be lilo.
Lin_img0 is : /boot/vmlinuz
When I boot using that entry I get the following
bri...@aracnet.com put forth on 9/24/2010 7:42 PM:
> right now I'm thinking I've got something misconfigured, but what ??
> Running lilo manually should fix whatever's going on and it most
> certainly isn't.
Did you possibly lose your BIOS LBA configuration before the
dist-upgrade, and didn't kno
Stephen Powell put forth on 9/24/2010 4:06 PM:
> Current stock Debian kernels for the
> amd64 architecture are right on the ragged edge of being too
> large for lilo to load below the 16M line
And the bulk of these ~16MB stock kernels is the initrd, correct? Wow
those are huge. I'm so glad I rol
On Fri, 24 Sep 2010 20:42:56 -0400 (EDT), bri...@aracnet.com wrote:
>
> I've run lilo and rebooted multiple times and always get the same
> result.
Interesting. What happens if you specify
root=802
as an argument to the boot prompt?
> right now I'm thinking I've got something misconfigured
On Fri, 24 Sep 2010 17:06:43 -0400 (EDT)
Stephen Powell wrote:
> On Fri, 24 Sep 2010 10:10:53 -0400 (EDT), bri...@aracnet.com wrote:
> >
> > I deleted one of the older images and when it finished I got this
> > mess:
> >
> > Could not find postrm hook script [lilo-update].
> > Looked in: '/bin'
On Fri, 24 Sep 2010 10:10:53 -0400 (EDT), bri...@aracnet.com wrote:
>
> I deleted one of the older images and when it finished I got this mess:
>
> Could not find postrm hook script [lilo-update].
> Looked in: '/bin', '/sbin', '/usr/bin', '/usr/sbin'
> Examining /etc/kernel/postrm.d .
> Purging c
On Fri, 24 Sep 2010 11:57:25 +0200
David Baron wrote:
> Try reinstalling your kernel, or if you compiled your own, install a
> recent linux-image-2.6.32.5 from Sid. The postinstall script will
> point /etc/fstab and lilo.conf to the newer UUID references and then
> it should play.
>
> The postin
On Fri, 24 Sep 2010 11:57:25 +0200
David Baron wrote:
> Try reinstalling your kernel, or if you compiled your own, install a
> recent linux-image-2.6.32.5 from Sid. The postinstall script will
> point /etc/fstab and lilo.conf to the newer UUID references and then
> it should play.
I'll give it a
Try reinstalling your kernel, or if you compiled your own, install a recent
linux-image-2.6.32.5 from Sid. The postinstall script will point /etc/fstab
and lilo.conf to the newer UUID references and then it should play.
The postinstall for home-brew kernels does not do this for you, I'm afraid a
In <4c9c2ca9.3020...@hardwarefreak.com>, Stan Hoeppner wrote:
>bri...@aracnet.com put forth on 9/23/2010 11:25 PM:
>>> No, that's normal. What had you changed on the system immediately
>>> prior to this boot problem occurring?
>>
>> apt-get dist-upgrade, natch.
>
>WTF is "natch"?
Shortening of "
bri...@aracnet.com put forth on 9/23/2010 11:25 PM:
>> No, that's normal. What had you changed on the system immediately
>> prior to this boot problem occurring?
>
> apt-get dist-upgrade, natch.
WTF is "natch"?
--
Stan
--
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org
with
On Thu, 23 Sep 2010 21:25:56 -0700
wrote:
> aaargh. I've never had so much trouble in my entire
> linux/debian/life. I have had a smooth boot or bootloader upgrade on
> this computer since I fired it up. other one works good, though. but
> really, 1/2 _is_ bad.
I have NOT had a smooth, etc..
On Thu, 23 Sep 2010 23:20:45 -0500
Stan Hoeppner wrote:
> bri...@aracnet.com put forth on 9/23/2010 10:50 PM:
>
> > Boot image: /boot/vmlinuz-2.6.32-5-amd64
> > Device 0x0802: BIOS drive 0x80, 255 heads, 30515 cylinders,
> >63 sectors. Partition offset: 120583890 sectors.
> > Usi
bri...@aracnet.com put forth on 9/23/2010 10:50 PM:
> Boot image: /boot/vmlinuz-2.6.32-5-amd64
> Device 0x0802: BIOS drive 0x80, 255 heads, 30515 cylinders,
>63 sectors. Partition offset: 120583890 sectors.
> Using Volume ID 5879D4A8 on bios 80
> Setup length is 27 sectors.
> Mappe
On boot lilo does not find the root device. I can use root=/dev/sda2
at the lilo boot prompt and it will boot correctly. So clearly it's
pointing at the incorrect root device. I've double checked the
lilo.conf file and it says:
boot=/dev/sda
root=/dev/sda2
which is correct. the lilo command
Hello
I have a problem with lilo for a compact flash
I have a compach flash that will run on a system(1) as /dev/hdc. It has
a patrition /dev/hdc1 with a root linux instalation.
But I have to configure this flas on other machine(2) (firt one have no
keyboard and can't have) thas only can detect
Hello
I have a problem with lilo for a compact flash
I have a compach flash that will run on a system(1) as /dev/hdc. It has
a patrition /dev/hdc1 with a root linux instalation.
But I have to configure this flas on other machine(2) (firt one have no
keyboard and can't have) thas only can dete
-Mensaje original-
De: Erik Steffl <[EMAIL PROTECTED]>
Para: debian-user
Fecha: Sábado, 02 de Diciembre de 2000 07:23 p.m.
Asunto: Re: A lilo config question
>Javier Sieben wrote:
Is much easier in this form.
Thanks, Erik.
Javier
-Mensaje original-
De: Oliver Elphick
Para: Javier Sieben <[EMAIL PROTECTED]>
Fecha: Sábado, 02 de Diciembre de 2000 06:23 p.m.
Asunto: Re: A lilo config question
>"Javier Sieben" wrote:
> >Hello
> >
> >I'm a newbie and need to know how
Javier Sieben wrote:
>
> -Mensaje original-
> De: Erik Steffl <[EMAIL PROTECTED]>
> Para: Debian User
> Fecha: Sábado, 02 de Diciembre de 2000 07:01 p.m.
> Asunto: Re: A lilo config question
>
> > 1) you can also create a lilo entry that will boot deb
-Mensaje original-
De: Erik Steffl <[EMAIL PROTECTED]>
Para: Debian User
Fecha: Sábado, 02 de Diciembre de 2000 07:01 p.m.
Asunto: Re: A lilo config question
> 1) you can also create a lilo entry that will boot debian into a run
>level that does not start xdm.
>
>
1) you can also create a lilo entry that will boot debian into a run
level that does not start xdm.
2) you can also specify run level at lilo prompt during boot
3) the other option is to change default run level to a run level that
does not start xdm, see /etc/nittab and look for lines like
-Mensaje original-
De: Bud Rogers <[EMAIL PROTECTED]>
Para: Debian User
Fecha: Sábado, 02 de Diciembre de 2000 06:38 p.m.
Asunto: Re: A lilo config question
>On Saturday 02 December 2000 15:21, Javier Sieben wrote:
>> Hello
>>
>> I'm a newbie and need to
On Saturday 02 December 2000 15:21, Javier Sieben wrote:
> Hello
>
> I'm a newbie and need to know how can I make a lilo item menu that
> loads the kernel and don't execute xdm (for use the text console)?
This is not a lilo issue. xdm is being started by the rc.d scripts.
You can stop xdm from
Hello
I'm a newbie and need to know how can I make a lilo item menu that loads the
kernel and don't execute xdm (for use the text console)?
Regards, Javier
> In the past, I've always just booted Debian off of a floppy, but this time I
> want to use LILO to boot Debian or Win95 depending on what I want. If I
> want to use LILO, do I just choose 'Make bootable form hard disk' at the
> last step of Debian 2.1 Slink, or do I have to do something else.
Hey,
I'm planning on reinstalling Debian on my system today (I kind of messed a
lot of stuff up, I could fix it, but I decided I'd rather just reinstall).
In the past, I've always just booted Debian off of a floppy, but this time I
want to use LILO to boot Debian or Win95 depending on what I want.
On Fri, Jan 22, 1999 at 12:51:30PM +0100, Thomas MANGIN wrote:
> As far as I noticed I didn t see any to to config lilo with a windows
> partition. I done it by hand few month ago but I needed and initrd file
> If I am right. On my actual installation which is lighter I don t get it
> any more. Wha
> As far as I noticed I didn t see any to to config lilo with a windows
> partition. I done it by hand few month ago but I needed and initrd file
> If I am right. On my actual installation which is lighter I don t get it
> any more. What can i do !!
>
> Thomas
Say again? It's kind of hard to und
As far as I noticed I didn t see any to to config lilo with a windows partition.
I done it by hand few month ago but I needed and initrd file If I am right.
On my actual installation which is lighter I don t get it any more. What
can i do !!
Thomas
--
Today's thinking : I'am not able to think
Hi,
Hopefully some lilo or configuration wizard will be able to
answer this. I posed this question--or its parallel--some weeks
ago, but this was before I had FreeBSD installed. Now I've got
Debian an FreeBSD installed on my 6x86 box, so I'm ready.
There are 3 SCSI drives. Debi
I've just guided a friend through an installation of Debian over the
phone.
He had a hard time getting LILO to install to the MBR of the first HDD.
He has Win95 on the first IDE and was installing Linux on the second. It's
hard to tell over the phone with a first time linux user if they are
rep
47 matches
Mail list logo
