1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
|
This package includes support for generating an initramfs that can boot on
the slug. It will be updated when the Debian kernel package is upgraded.
To use the internal ethernet interface on the slug, you should install
the non-free ixp4xx-microcode package. If the microcode is present in
/lib/firmware/, it will be placed in the initramfs when it is generated.
If you installed Debian using an image from slug-firmware.net, the microcode
be included automatically.
leds
====
This package includes a "leds" program that can be used to control the leds
manuall. It also includes an "zleds" init script that controls the leds of
the slug during boot. This can be used to diagnose boot failures. Some of
the led states:
- Cycling down all the leds from top to bottom: The APEX boot loader.
- All leds on: Early in kernel boot. (Should only persist for a few
seconds.)
- Disk off, status off (or amber): Initramfs is running, prior to mounting
root filesystem.
- Disk on, status alternating amber and green: Root filesystem mounted,
system booting.
- Disk on, status green: System is booted and running.
- Disk on, status amber: Single user mode.
- Disk on, status alternating amber and green: Shutdown/reboot in progress.
The disk leds should come on when a disk is plugged directly into the
associated USB port (this is done by udev). Disks attached via USB hubs
will not trigger the disk leds.
The system will beep three times once it is fully booted and running.
A few hints for futher configuration of Debian on your slug
===========================================================
- Unless you have a serial console, it's a good idea to edit
/etc/default/rcS and set FSCKFIX=yes, to prevent fsck problems from
hanging your boot waiting for you to press "y" on a nonexistant console.
- It's a good idea to enable bootlogd, by editing /etc/default/bootlogd.
Then you can see boot logs in /var/log/boot.
- You might want to move the ssh server startup closer to the beginning of
the init sequence so that you can ssh in earlier. You can do that by
moving /etc/rc2.d/S16ssh to /etc/rcS.d/S41ssh. (Anything after networking
is brought up will do.) You can also move /etc/rcS.d/S40networking to
S21networking to make the network come up a lot earlier, and run ssh in
/etc/rcS.d/S21ssh; this will let root log in while the system is still
booting, which can be useful if something goes wrong.
- If you want the power button to turn the system off, instead of
rebooting it like it does by default, edit /etc/inittab and change the
shutdown command to run shutdown -h now.
- If you want openslug's behavior of coming up on address 192.168.1.77 if
there is no dhcp server, edit /etc/dhclient.conf and add a default
lease, such as this:
# Prdefined default lease for networks w/o dhcp.
lease {
interface "eth0";
fixed-address 192.168.1.77;
option broadcast-address 192.168.1.255;
option routers 192.168.1.1;
}
Alternatively, install avahi-autoipd, and if no dhcp lease is obtained,
the slug will come up using zeroconf networking. You can then access it
using "hostname.local", if you have mDNS configured (install
libnss-mdns).
- The slug only has 32 mb of ram. One easy way to save memory is to remove
the openssh-server package (approx 9 mb ram) and install dropbear
(approx 1 mb ram).
using openslug
==============
If instead of booting using the Debian initrd, you are using the openslug
firmware to boot Debian from a USB drive on your slug, then it creates a
/.recovery file during boot, and unless this file is removed, the next boot
will be back into the openslug system. This package has an init script that
removes this file on each boot, so that Debian will boot each time. If you
don't want the init script to remove the file, edit
/etc/default/rmrecovery.
|
