Bug#235044: No installable kernel found w/20040226 sarge bus. card daily
On Tue, Mar 02, 2004 at 04:01:09PM -0500, Barry Hawkins wrote:
> On Feb 27, 2004, at 12:14 AM, Barry Hawkins wrote:
> >Package: installation-reports
> >uname -a: N/A, install fails
> >Date: 02/26/2004, 23:30 EST
> >Method: Booted to CD-ROM by holding down C after chime, using
> >Machine: 15" Aluminum PowerBook G4 1GHz
> >Processor: G4 1GHz
> >Memory: 768MB RAM
> >Root Device: IDE 60GB drive
> >Root Size/partition table: Root size is 4.4GB, I can't access the
> >table right now
> >Output of lspci: sarge-powerpc-businesscard.iso
> >Base System Installation Checklist:
> >Initial boot worked: [O]
> >Configure network HW: [O]
> >Config network: [O]
> >Detect CD: [O]
> >Load installer modules: [O]
> >Detect hard drives: [O]
> >Partition hard drives: [O]
> >Create file systems: [O]
> >Mount partitions: [O]
> >Install base system: [E]
> >Install boot loader: [ ]
> >Reboot: [ ]
> >[O] = OK, [E] = Error (please elaborate below), [ ] = didn't try it
> >Toward the end of the install, past 70%, the following message appears:
> > No installable kernel found
> >No installable kernel was found in the defined APT sources.
> >The current default kernel package is 'kernel-image'.
> >You may try to continue though this strange error is probably fatal.
> >The debug console shows the following:
> >Setting up tasksel (1.44) ...
> >chroot: cannot execute apt-get: No such file or directory
> Is there some reason that this and other powerpc installation reports
> are not being followed up on?
Because the ones who care about powerpc are busy right now ? I think it
is exam time for some of them, or they are busy with other stuff. I
myself don't have a pmac, so there is not much i can do, and i think
gaudenz has gone to work on discovery mostly. Don't know about the
Maybe this is the right time for you (or others) to step in and have a
go at fixing this problem, if we want to have good powerpc support by
Anyway, i have no idea about the keyboard problem you reported, but
this kernel issue, it should not be problematic. Does choosing unstable
instead of testing make a change here ?