I can't answer all, but try my best. But almost all of them do not
affect your operation, right?
On 7/17/2013 7:54 PM, Erik van Linstee wrote:
I have installed 0.9.1 on an Alix board and ran into several errors
during boot. I reported the same errors with 0.9.0 a while back.
What ALIX board are you using?
Here are the relevant parts of the boot log:
> [ 1.634822] Linux agpgart interface v0.103
> [ 1.650229] brd: module loaded
> [ 1.650525] ACPI Exception: AE_BAD_PARAMETER, Thread 3343006656
could not acquire Mutex [0x1] (20121018/utmutex-278)
> [ 1.654595] ACPI Exception: AE_BAD_PARAMETER, Thread 3343006656
could not acquire Mutex [0x1] (20121018/utmutex-278)
> [ 1.657625] cs5535-gpio cs5535-gpio: reserved resource region
[io 0x6100-0x61ff]
> [ 1.659422] ACPI Exception: AE_BAD_PARAMETER, Thread 3343006656
could not acquire Mutex [0x1] (20121018/utmutex-278)
> [ 1.663458] ACPI Exception: AE_BAD_PARAMETER, Thread 3343006656
could not acquire Mutex [0x1] (20121018/utmutex-278)
> [ 1.668559] ACPI Exception: AE_BAD_PARAMETER, Thread 3343006656
could not acquire Mutex [0x1] (20121018/utmutex-278)
> [ 1.672595] cs5535-mfd 0000:00:0f.0: 5 devices registered.
Not sure, perhaps you are using ALIX3d3.
> Begin: Running /scripts/init-bottom ... Setting up serial console
for inittab ...
> DEFCONSOLE=console=ttyS0,38400n8
> LIVE_GETTY=
> AUTOINSTALL=
> Setting Serial Port to ttyS0 38400
> sed: can't create temp file '/root/etc/inittabYp7rxF': Read-only
file system
> done.
This is used for PXE installation, could safely ignore.
> [ 6.488793] Error: Driver 'pcspkr' is already registered,
aborting...
> [info] Loading kernel module w83627hf.
> ERROR: could not insert 'w83627hf': No such device
w83627 no longer be used for ALIX, not sure why. But should be remove
from ALIX installation profile.
> can't create /var/lib/dhcp/dhclient.eth0.leases: No such file or
directory
Actually, the directory does exist, by /var/lib/dhcp is mounted readonly.
Known, the leases file remember what IP your have leased. If this bugs
you, you can add "var/lib/dhcp" to $VOYAGE_SYNC_RECOVER_DIRS and/or
$VOYAGE_SYNC_DIRS in /etc/default/voyage-sync
> [....] Starting OpenBSD Secure Shell server: sshdCould not load host
key: /etc/ssh/ssh_host_ecdsa_key
> . ok
This error can be fixed by removing the following line from
/etc/ssh/sshd_config:
> HostKey /etc/ssh/ssh_host_ecdsa_key
Or by creating the key manually.
This was fixed in voyage-util 0.12-4, after 0.9.1, the key could be
regenerated by "dpkg-reconfigure openssh-server"
Also, the leds module does not seem to be available anymore (since
0.8.x).
> root@voyage:~# modprobe leds-alix
> FATAL: Module leds-alix not found.
leds-alix is obsoleted. Leds is now using GPIO_CS5535 to drive. Works
on ALIX2 and ALIX3d2.
regards,
Erik
--
Regards,
Kim-man "Punky" Tse
* Open Source Embedded Solutions and Systems
- Voyage Linux (http://linux.voyage.hk)
- Voyage MPD (http://linux.voyage.hk/voyage-mpd)
- Voyage MuBox (http://mubox.voyage.hk)
* Voyage Store (http://store.voyage.hk)
_______________________________________________
Voyage-linux mailing list
[email protected]
http://list.voyage.hk/mailman/listinfo/voyage-linux
