Your message dated Sat, 02 Dec 2006 13:50:38 +0100
with message-id <[EMAIL PROTECTED]>
and subject line Bug#247743: wrong kernel installed for sparc in beta4
has caused the attached Bug report to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what I am
talking about this indicates a serious mail system misconfiguration
somewhere. Please contact me immediately.)
Debian bug tracking system administrator
(administrator, Debian Bugs database)
--- Begin Message ---
Package: installation-reports
Debian-installer-version: daily businesscard iso 20040505 from
http://cdimage.debian.org/pub/cdimage-testing/daily/sparc/current/
uname -a: Linux opal 2.4.24-sparc32 #1 Fri Jan 30 16:04:55 EST 2004
sparc unknown
Date: 20040506
Method: businesscard, external CD-RW, sunsite.ualberta.ca, not proxied
testing
Machine: SPARCstation 5
Processor: sparc4m
Memory: 64 MB
Root Device: SCSI /dev/scsi/host0/bus0/target4/lun0/disc 4.1 GB
Root Size/partition table:
scsi(0,4,0)part1 ext3 4.1GB /
scsi(0,4,0)part2 swap 181.3MB swap
scsi(0,3,0)part1 reiserfs 1.0GB /home
Output of lspci: N/A
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
Comments/Problems:
Install base system failed because the installer chose the wrong kernel:
kernel-image-2.4.24-sparc64-smp instead of kernel-image-2.4.24-sparc32.
I was not prompted for a kernel to install.
Here is the contents of /proc/cpuinfo
<Description of the install, in prose, and any thoughts, comments
and ideas you had during the initial install.>
--- End Message ---
--- Begin Message ---
I expect this has been fixed with the new infrastructure for determining
the default kernel which was introduced quite some time back.
Cheers,
FJP
--- End Message ---
