Bug#458154: Install of debian-4.0r2 on NSLU2
Package: installation-reports
Boot method: network
Image version: http://www.slug-firmware.net/d-dls.php
Date: Fri Dec 28 2007 18:30 EST
Machine: Linksys NSLU2
Processor: ARM
Memory: Standard slug (32MB I think)
Partitions: df
Filesystem 1k-blocks Used Available Use% Mounted on
tmpfs 14992 392 14600 3% /dev
tmpfs 14992 392 14600 3% /dev
tmpfs 14992 392 14600 3% /.dev
/dev/scsi/host0/bus0/target0/lun0/part1 16516052 402220 15274840 3% /target
/dev/scsi/host0/bus0/target0/lun0/part6 215578152 191832 204435216 0%
/target/home
Output of lspci -nn and lspci -vnn:
# /usr/bin/lspci -nn
00:01.0 USB Controller [0c03]: NEC Corporation USB [1033:0035] (rev 43)
00:01.1 USB Controller [0c03]: NEC Corporation USB [1033:0035] (rev 43)
00:01.2 USB Controller [0c03]: NEC Corporation USB 2.0 [1033:00e0] (rev 04)
# /usr/bin/lspci -nn
00:01.0 USB Controller [0c03]: NEC Corporation USB [1033:0035] (rev 43)
00:01.1 USB Controller [0c03]: NEC Corporation USB [1033:0035] (rev 43)
00:01.2 USB Controller [0c03]: NEC Corporation USB 2.0 [1033:00e0] (rev 04)
/proc # /usr/bin/lspci -vnn
00:01.0 USB Controller [0c03]: NEC Corporation USB [1033:0035] (rev 43)
(prog-if 10)
Subsystem: NEC Corporation USB [1033:0035]
Flags: bus master, medium devsel, latency 8, IRQ 28
Memory at 48000000 (32-bit, non-prefetchable) [size=4K]
Capabilities: [40] Power Management version 2
00:01.1 USB Controller [0c03]: NEC Corporation USB [1033:0035] (rev 43)
(prog-if 10)
Subsystem: NEC Corporation USB [1033:0035]
Flags: bus master, medium devsel, latency 8, IRQ 27
Memory at 48001000 (32-bit, non-prefetchable) [size=4K]
Capabilities: [40] Power Management version 2
00:01.2 USB Controller [0c03]: NEC Corporation USB 2.0 [1033:00e0] (rev
04) (prog-if 20)
Subsystem: NEC Corporation USB 2.0 [1033:00e0]
Flags: bus master, medium devsel, latency 68, IRQ 26
Memory at 48002000 (32-bit, non-prefetchable) [size=256]
Capabilities: [40] Power Management version 2
Base System Installation Checklist:
[O] = OK, [E] = Error (please elaborate below), [ ] = didn't try it
Initial boot: [O]
Detect network card: [O]
Configure network: [O]
Detect CD: [ ]
Load installer modules: [O]
Detect hard drives: [O]
Partition hard drives: [O]
Install base system: [O]
Clock/timezone setup: [O]
User/password setup: [O]
Install tasks: [E]
Following instructions at
http://www.cyrius.com/debian/nslu2/install.html and using the
"unofficial" image (because I don't have a USB ethernet dongle), all
seems to go well. But since the install takes a long time, if I walk
away and come back, I see this screen:
┌───────┤ [!] Configuring popularity-contest ├─────────┐
│ │
│ The system may anonymously supply the distribution developers with
│ statistics about the most used packages on this system. This
│ information influences decisions such as which packages should go on
│ the first distribution CD.
┌│
││ If you choose to participate, the automatic submission script will
││ run once every week, sending statistics to the distribution
││ developers. The collected statistics can be viewed on
││ http://popcon.debian.org/.
││ │
└│ This choice can be later modified by running "dpkg-reconfigure
│ popularity-contest".
│
│ Participate in the package usage survey? │
Unfortunately the ssh session times out, since the install takes over 2
hours and I walked away. When I try to start the install again ("% ssh
installer@myslug") I come back part way, but then get a red screen that
says the install failed. Even if I try to redo the step, the install is
labeled as failing.
Install boot loader: [E]
Would not proceed with prior error(s)
Overall install: [E]
Comments/Problems:
Attempt to install debian-4.0r2 onto an NSLU2 following instructions
provided at http://www.cyrius.com/debian/nslu2/install.html all seems to
go well, but you can't walk away during the install lest the ssh session
timeout. Is there a way to tell ssh, "don't time out at all"? Or is
there a proper way to restart the installer at the point where the ssh
session timed out? It seems the installer may have left some temporary
files in place that, when restarted/reentered, confuse it and keep it
from completing the installation.
Reply to: