Bug#253789: netwinder tc1 success
Kyle McMartin
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
--
To UNSUBSCRIBE, email to debian-bugs-...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listm...@lists.debian.org
Colin Watson
> 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.
If this applies to arm in general, then we could do this:
Index: rootskel/debian/templates-arch
===================================================================
--- rootskel/debian/templates-arch (revision 16700)
+++ rootskel/debian/templates-arch (working copy)
@@ -63,6 +63,7 @@
Default[sparc]: true
Default[hppa]: true
Default[powerpc]: true
+Default[arm]: true
Description: kernel needs a link in /boot/ (linux only)
Setting this to true makes base-installer include 'link_in_boot=yes'
in /etc/kernel-img.conf.
If not, it'll be more complicated.
> 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.
No, this has been reported elsewhere; I believe it's currently
considered to be either a toolchain bug or a bug with libssl using
incorrect optimizations, but I don't know the details.
Cheers,
--
Colin Watson [cjwa...@flatline.org.uk]
Martin Michlmayr
> 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.
That's something I wanted to look in for a while.
> 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.
This is actually a compiler bug, see #250185
--
Martin Michlmayr
t...@cyrius.com
Kyle McMartin
> If this applies to arm in general, then we could do this:
>
>
> If not, it'll be more complicated.
>
edit the kernfile variable to point to different versions, it would nice
to just leave /boot/vmlinuz. The logic behind this is that the NW
firmware can only read the kernel off a ext2 revision 0 filesystem, so
you basically *must* have a seperate boot.
> No, this has been reported elsewhere; I believe it's currently
> considered to be either a toolchain bug or a bug with libssl using
> incorrect optimizations, but I don't know the details.
>
Ok. Thanks,
--
Kyle McMartin
Kyle McMartin
> That's something I wanted to look in for a while.
>
> This is actually a compiler bug, see #250185
>
Aye. I didn't mean to imply otherwise. The whole reason I'm using this
to test is that the nw running unstable was quite thoroughly broken. :)
Regards,
--
Kyle McMartin