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

Bug#253789: netwinder tc1 success



Package: installation-reports

Debian-installer-version: test candidate 1
uname -a: Linux orodruin 2.4.25-netwinder #1 Tue May 18 00:49:19 BST 2004 armv4l GNU/Linux
Date: Fri Jun 11 00:53:40 EDT 2004
Method: netboot
	Booted off the network (tftp) and installed from archive.progeny.com.

Machine: Rebel Netwinder
Processor: StrongARM-110 rev 3
Memory: 64M
Root Device: IDE
Root Size/partition table: 
	100M /dev/hda1	/boot
	1.9G /dev/hda2	/
	128M /dev/hda3	swap

Output of lspci: [typed by hand, excuse errors]

0000:00:00.0 Co-processor: Digital Equipment Corporation StrongARM DC21285 (rev 03)
0000:00:09.0 VGA compatible controller: Intergraphics Systems CyberPro 2000 (rev 01)
0000:00:0a.0 Ethernet controller: Digital Equipment Corporation DECchip 21142/43 (rev 30)
0000:00:0c.0 ISA bridge: Symphony Labs W83C553 (rev 05)
0000:00:0c.1 IDE interface: Symphony Labs SL82c105 (rev 05)
0000:00:0d.0 Ethernet controller: Winbond Electronics Corp W89C940F

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:    [O]
Install boot loader:    [O]
Reboot:                 [O]
[O] = OK, [E] = Error (please elaborate below), [ ] = didn't try it

Comments/Problems:

Everything went swimmingly. When I rebooted to finish the install, I had 
to manually set the kernfile variable to /vmlinuz-2.4.25-netwinder. A 
better solution would be for the installer to detect that it's installing 
to a seperate /boot partition and to add a /boot/vmlinuz symlink instead of 
an /vmlinuz one.

As well, when I finished the base install (opting out of using tasksel or
dselect), I was unable to install ssh. It installed to the point where it
tried to generate keys, and then died with Illegal instruction. I suspect
this is a hardware problem with my netwinder, however.

Cheers for the good work, the progress is fantastic!
-- 
Kyle McMartin



Reply to: