[Voyage-linux] Errors during boot of 0.9.1 on ALIX
Kim-man 'Punky' TSE
(spam-protected)
Wed Dec 11 11:00:55 HKT 2013
Hi Teco,
Please see my reply below:
On 12/10/2013 10:35 PM, Teco Boot wrote:
> Here my findings so far.
> I use my own install script, but for this verification I used voyage-pxe.
> I'll sync my scripts and the 0.9.2 rc.
I am not a perfectionist and I am only able to answer what I know. I believe that all of below are not showstopper.
BTW, you are welcome to send me any fix.
> 1) PXE README.pxe
> Before voyage-pxe can be started, remount-rw has to be performed.
> After installation, I have:
> /usr/local/sbin/voyage-install.sh: .voyage-install.conf: Read-only file system
> /usr/local/sbin/voyage-install.sh: test.conf: Read-only file system
At the end of installation, it writes installation settings to disk to current directory. If your current directory is
/tmp/root, which is a squashfs mount, you can't write it because squashfs is always a read-only filesystem.
> 2)
> Kernel is quite old, it is 3.10.11. We are at 3.10.23 at the moment.
I only use upstream debian kernel source. Right now, it only provides up-to 3.10.11.
http://packages.debian.org/wheezy-backports/linux-source-3.10
> 3)
> On Alix board, I have:
> [ 0.000000] ACPI BIOS Bug: Error: A valid RSDP was not found (20130328/tbxfroot-218)
>
> [ 1.643280] ACPI Exception: AE_BAD_PARAMETER, Thread 3473054656 could not acquire Mutex [0x1] (20130328/utmutex-285)
> [ 1.647271] ACPI Exception: AE_BAD_PARAMETER, Thread 3473054656 could not acquire Mutex [0x1] (20130328/utmutex-285)
> [ 1.652062] ACPI Exception: AE_BAD_PARAMETER, Thread 3473054656 could not acquire Mutex [0x1] (20130328/utmutex-285)
> [ 1.654997] ACPI Exception: AE_BAD_PARAMETER, Thread 3473054656 could not acquire Mutex [0x1] (20130328/utmutex-285)
> [ 1.657924] ACPI Exception: AE_BAD_PARAMETER, Thread 3473054656 could not acquire Mutex [0x1] (20130328/utmutex-285)
I have this error too. But this don't seems affect my env.
> 4)
> DEFCONSOLE=console=ttyS0,115200n8 nomfgpt
> LIVE_GETTY=
> AUTOINSTALL=
> Setting Serial Port to ttyS0 115200
> sed: can't create temp file '/root/etc/inittabSYqG9O': Read-only file system
The code is to change the inittab serial console settings in initramfs stage. The codes lies in
/usr/share/initramfs-tools/scripts/init-bottom/25serial_inittab. I didn't notice this error since serial console is
working properly?
> 5)
> [ 5.646127] Error: Driver 'pcspkr' is already registered, aborting...
Not sure why pcspkr is loaded twice.
> 6)
> [info] Loading kernel module rtc.
> FATAL: Module rtc not found.
>
> Verified:
> root at voyage:/etc# modprobe rtc
> FATAL: Module rtc not found.
Original RTC seems to be depreciated and is replaced by RTC_LIB and this cannot be compiled as module. BTW, the below
rtc is loaded on ALIX:
[ 2.366627] platform rtc_cmos: registered platform RTC device (no PNP device)
[ 4.255481] rtc_cmos rtc_cmos: rtc core: registered rtc_cmos as rtc0
[ 4.274732] rtc_cmos rtc_cmos: alarms up to one day, 114 bytes nvram
[ 4.387042] rtc_cmos rtc_cmos: setting system clock to 2000-01-16 19:19:59 U)
> 7)
> During update-initramfs -u:
> ===
> Warning: Not updating LILO; /etc/lilo.conf not found!
Not sure why it complains.
> Try to get it as clean as possible? With reasonable efforts of course.
Again, I am not perfectionist. But welcome any patch for clean-up.
> For further testing, I have to compile some kernel modules. Are headers for this daily available? Or the sdk? It would be nice to have more verification tests completed before a 0.9.2 is released.
Header could be found here:
http://www.voyage.hk/dists/experimental/linux/linux-headers-3.10.11-voyage_13.0-1_i386.deb
> Thanks, Teco
--
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)
More information about the Voyage-linux
mailing list