[csmall@debian.org: installation-reports: Does not install on Alpha PC164SX]
As this looks alpha-specific, I thought I'd forwarded it to the list.
The only good thingabout this is my main mail/firewall/whatever server
is no longer the alpha, so I can play with it more.
I'm surprised mainly about
- why was partition i created
- why did the kernel work fine booting from CD but not from the disk
drive?
----- Forwarded message from Craig Small <csmall@debian.org> -----
Subject: installation-reports: Does not install on Alpha PC164SX
Debian-installer-version: RC1 from cdimage.debian.org
X-Virus-Scanned: by amavisd-new-20030616-p10 (Debian) at enc.com.au
X-Virus-Scanned: by amavisd-new-20030616-p10 (Debian) at enc.com.au
Package: installation-reports
uname -a: Linux fozzie 2.4.26-1-generic #1 Thu Jun 10 23:43:13 CDT 2004
alpha GNU/Linux
Date: Fri Aug 13 22:13:58 EST 2004
Method: Installed from netinst CD
Machine: Alpha PC164SX
Processor: PCA56
Memory: 256M
Root Device: ide drive /dev/hda
Root Size/partition table: Standard Debian autopartition for multi-user
Output of lspci:
0000:00:05.0 VGA compatible controller: Cirrus Logic GD 5434-8 [Alpine]
(rev fc)0000:00:06.0 Ethernet controller: 3Com Corporation 3c905B 100BaseTX [Cyclone] (rev 28)
0000:00:07.0 Multimedia audio controller: Ensoniq ES1370 [AudioPCI]
0000:00:08.0 ISA bridge: Contaq Microsystems 82c693
0000:00:08.1 IDE interface: Contaq Microsystems 82c693
0000:00:08.2 IDE interface: Contaq Microsystems 82c693
0000:00:08.3 USB Controller: Contaq Microsystems 82c693
0000:00:09.0 Ethernet controller: 3Com Corporation 3c905C-TX/TX-M [Tornado] (rev 74)
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: [E]
Create file systems: [O]
Mount partitions: [O]
Install base system: [O]
Install boot loader: [E]
Reboot: [E]
[O] = OK, [E] = Error (please elaborate below), [ ] = didn't try it
Comments/Problems:
Partition making thingy makes a i (part 9) partition that starts
at some large number and ends at 0 (yes, this is back to front)
Because of the above-mentioned partition aboot fails to get installed
because partition 9 conflicts where aboot needs to go, you cannot
use -f9 flag because it says you can only have 8 partitions.
Manually removing partition 'i' makes aboot installer happy.
(fdisk commands, d i w x )
Rebooting, it still tries to reboot off cdrom (dqb0) instead of
drive (dqa0). Hit reset button to fix this.
Booting with kernel that is installed initially results in massive
number of pci errors, just like before. However this problem is not
present when booting from CDROM. I am unsure why it happens only
when rebooted.
----- End forwarded message -----
--
Craig Small GnuPG:1C1B D893 1418 2AF4 45EE 95CB C76C E5AC 12CA DFA5
Eye-Net Consulting http://www.enc.com.au/ MIEE Debian developer
csmall at : enc.com.au ieee.org debian.org
Reply to: