[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Bug#295934: Installer issues



 
Package: installation-reports

Debian-installer-version: <rc2 / alpha>
uname -a: <n/a>
Date: <2-18-2005 23:35 CST6CDT>
Method: <CD-ROM from ISO image dated 11-21-2004>

Machine: <AlphaServer 4100>
Processor: 4 x 600MHz / 8MB Cache
Memory: 512MB
Root Device: <SCSI>
Root Size/partition table: <sda0: 1 Meg aboot, sda1: 80MB ext2 @ /boot, sda3: 4096 MB ext3 @ /, sda4: 256MB swap>
Output of lspci and lspci -n: Not Available

Base System Installation Checklist:
[O] = OK, [E] = Error (please elaborate below), [ ] = didn't try it

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:    [O]
Install boot loader:    [O]
Reboot:                 [E]

Comments/Problems:
Aboot l (ist) command ouput is not numbered. Every selection begins "n:"

Install fails if you do not format partitions, even on a fresh (never successfully booted) install, apparently during ln of /target/usr/bin/awk. This failure cannot be successfully continued past. (i.e. to install kernel image) 
I have the choice of installing one out of 8 possible kernels. Should I choose a kernel that doesn't like my particular machine/setup, due in part to the above issue, a FULL reinstall is required to try a different kernel. Would it be possible to either allow installation of multiple kernels, or bypass the full install when only a different kernel is needed?
Using df in a shell during install reports partitions as somewhat larger than the actual size: (df -h) -> 80Meg ext2 is reports used as 2292756.0T, and size as 136276.0T, this affects all fs, inc tmpfs. This may be a non-install problem, I have nopt yet successfully booted to test in 'normal' mode.
 
The 2.6.8-1-smp kernel errors on the first boot, related to scsi symbols not loaded, then Machine checks and halts. I don't have specific info at the moment, but I'm guessing this is a kernel package issue more than an installer issue.
 
 
 

Reply to: