On Monday 30 June 2008, Simon McVittie wrote:
> On Mon, 30 Jun 2008 at 02:15:23 +0200, Frans Pop wrote:
> > On Monday 30 June 2008, Simon McVittie wrote:
> > > PALO reports that the boot image contains 0/vmlinux32, 0/vmlinux64
> > > and 0/ramdisk, but that it will try to boot 0/linux - however, it
On Mon, Jun 30, 2008 at 02:38:55AM +0100, Simon McVittie wrote:
> > And in this case it's not even clear who's at fault.
> > AFAIK the kernel will normally survive not being able to load firmware:
> > the module will be loaded, but the device not enabled.
>
> Not in this case, apparently!
>
> I
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Mon, 30 Jun 2008 at 02:15:23 +0200, Frans Pop wrote:
> On Monday 30 June 2008, Simon McVittie wrote:
> > PALO reports that the boot image contains 0/vmlinux32, 0/vmlinux64 and
> > 0/ramdisk, but that it will try to boot 0/linux - however, it turns o
Hi Simon,
On Monday 30 June 2008, Simon McVittie wrote:
> Comments/Problems:
> PALO isn't very intuitive, but I eventually got the machine netbooted
> using the serial console and the built-in Tulip network interface.
> PALO reports that the boot image contains 0/vmlinux32, 0/vmlinux64 and
> 0/ra
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Package: installation-reports
Severity: normal
- -- Package-specific info:
Boot method: network
Image version: lenny d-i beta 2
Date: 2008-06-29
Machine: A500
Partitions: (sda: guided partitioning, sdb: kept previous installation)
club:~# sfdisk -l
5 matches
Mail list logo
