Your message dated Fri, 03 Apr 2020 04:48:27 +
with message-id
and subject line Bug#955507: Removed package(s) from unstable
has caused the Debian Bug report #380416,
regarding lilo fails to install when using XFS root partition on AMD64
to be marked as done.
This means that you claim that
On Thu, Jan 24, 2019 at 12:23:31PM +0100, Martin Zobel-Helas wrote:
>Hi,
>
>i was asked yesterday to try to avoid virtio as harddisk driver, which
>i did. This now works like a charm, i can install and successfully boot
>the VM in kvm.
>
>So it seems it is /dev/vda being the problem for lilo-insta
Hi,
i was asked yesterday to try to avoid virtio as harddisk driver, which
i did. This now works like a charm, i can install and successfully boot
the VM in kvm.
So it seems it is /dev/vda being the problem for lilo-installer.
Still, the error message could be a bit more explaining rather than
Your message dated Wed, 08 Sep 2010 03:58:35 +
with message-id
and subject line Closing old installation report #244323
has caused the Debian Bug report #244323,
regarding [i386] [beta3] [netinst] xfs on / : lilo fails to install
to be marked as done.
This means that you claim that the
Processing commands for [EMAIL PROTECTED]:
> reassign 498879 lilo
Bug#498879: LILO fails when doing XFS on / on KVM virtual disk
Bug reassigned from package `lilo-installer' to `lilo'.
> severity 498879 wishlist
Bug#498879: LILO fails when doing XFS on / on KVM virtual disk
reassign 498879 lilo
severity 498879 wishlist
retitle 498879 lilo: please add support for virtio drives
thanks
On Sun, Sep 14, 2008 at 06:58:17PM -0300, André Luís Lopes wrote:
> Frans Pop escreveu:
> > Are you sure that the problem is XFS? It could also be that lilo does not
> > support KVM's /d
reassign 498879 lilo-installer
retitle 498879 LILO fails when doing XFS on / on KVM virtual disk
thanks
On Sunday 14 September 2008, André Luís Lopes wrote:
> Comments/Problems:
>I do not use LILO personally, but as I probably will use XFS for
> some future projects, I wanted to know
Processing commands for [EMAIL PROTECTED]:
> reassign 498879 lilo-installer
Bug#498879: [debian-testing-i386-netinst] LILO fails when doing XFS on / (daily
from 20080913)
Bug reassigned from package `installation-reports' to `lilo-installer'.
> retitle 498879 LILO fails when d
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Package: installation-reports
Boot method: Installer booted from a ISO file use as a virtual CD by
KVM, using the following command-line :
sudo kvm -name lenny-daily -net
nic,macaddr=DE:AD:BE:EF:17:19,model=virtio -net
tap,script=/etc/kvm/kvm-ifup -d
Package: lilo-installer
Version: 1.16
I'm using the latest daily build of the AMD64 netinst CD. I have a
single SATA drive, and I selected "use entire drive" in the
partitioner and it created one large root partition and one swap
partition. Then I changed the root partition to XFS. There was a
I tried a new install of Sarge RC2 on this laptop (Acer Aspire 1300) today.
I boot with option :
expert26 noscsi vga=792
Grub stops on message "Determining Grub boot device..." during several
minutes, then I'm back to the main menu.
I tried to install Lilo on /dev/hda7, but lilo f
Package: debian-installer
Severity: important
This is an older Dell Dimension desktop with Bios version A05 and a
PIII-450. I am using the Sarge RC2 net-installer.
Using the expert26 install, attempting to use LVM on top of raid-1.
Install raid-1 across two IDE hard drives, raid device md0, conf
* Ariel Garcia <[EMAIL PROTECTED]> [2004-06-02 21:04]:
> > > -Preliminary comment: please write down the right boot parameters in
> > > the INSTALLATION_HOWTO!! :-)
> > > devfs=mount console=tty0 ramdisk_size=8192 root=/dev/ram0
> >
> > Do you know if this has been documented now?
>
> Yes, it is d
pgpMwX9kMcaKJ.pgp
Description: PGP message
* Ariel Garcia <[EMAIL PROTECTED]> [2004-02-11 16:01]:
> -Preliminary comment: please write down the right boot parameters in the
> INSTALLATION_HOWTO!! :-)
> devfs=mount console=tty0 ramdisk_size=8192 root=/dev/ram0
Do you know if this has been documented now?
> there was nothing inside /target
Package: installation-reports
Debian-installer-version: testing beta2 (got vmlinuz + netboot-initrd on
Feb. 6 approx.)
uname -a: didn't check, but has to be vmlinuz from testing/beta2
Date: Feb. 10
Method: PXE boot, IP by dhcp, network install from DE debian mirror
(ftp2.de.debian.org i think)
Hello to all!
On my home server I installed an unstable debian system on an
IDE-Software-Raid5. All was working fine, but now I am in trouble:
I just compiled a new kernel from the kernel-source-2.4.22-1 after I
made a backup to a usb-harddisk and now lilo fails to work
Thanks in advance
h [mailto:[EMAIL PROTECTED]]
> Sent: den 4 oktober 2002 13:26
> To: Christer Jansson A (QRA)
> Cc: '[EMAIL PROTECTED]'
> Subject: Re: LILO fails
>
>
> #include
> Christer Jansson A (QRA) wrote on Mon Sep 30, 2002 um 02:15:55PM:
>
> > LILO prints "L&
#include
Christer Jansson A (QRA) wrote on Mon Sep 30, 2002 um 02:15:55PM:
> LILO prints "L", followed by the number "07" which seems to repeat endlessly.
I think, D-I will face the same problem with any boot loader, sooner or later.
If the disk presentation of the kernel differs from that used
- - - - - - - -
When LILO loads itself, it displays the word "LILO". Each letter is printed
before or after performing some specific action. If LILO fails at some
point, the letters printed so far can be used to identify the problem. This
is described in more detail in the technical overview
Hello,
I´m having problems with LILO and I can´t find any documentation that seems related...
Symtoms:
LILO prints "L", followed by the number "07" which seems to repeat endlessly.
I´ve bought a Debian 3.0 CD set and have installed LILO (and Linux) using the install
CD.
I can now boot from a b
21 matches
Mail list logo
