Hi Punky, Before digging to deeply, what is your candidate kernel config? I tried to solve item 3). acpi=off didn't resolve the ACPI Exception messages. Can have to do with disabled rtc.
Parts of grep RTC config-3.*.voyage config-3.10.11-voyage:CONFIG_RTC_LIB=y config-3.8.13-voyage:CONFIG_HPET_EMULATE_RTC=y config-3.8.13-voyage:CONFIG_RTC=m config-3.8.13-voyage:CONFIG_SND_RTCTIMER=m diff output is much longer. Thanks, Teco Op 10 dec. 2013, om 15:35 heeft Teco Boot <[email protected]> het volgende geschreven: > Hi Punky, > > 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. > > > 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 > > > 2) > Kernel is quite old, it is 3.10.11. We are at 3.10.23 at the moment. > > > 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 added acpi=off kernel parameter. > > 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 > > > 5) > [ 5.646127] Error: Driver 'pcspkr' is already registered, aborting... > > > 6) > [info] Loading kernel module rtc. > FATAL: Module rtc not found. > > Verified: > root@voyage:/etc# modprobe rtc > FATAL: Module rtc not found. > > > 7) > During update-initramfs -u: > === > Warning: Not updating LILO; /etc/lilo.conf not found! > > > Try to get it as clean as possible? With reasonable efforts of course. > > 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. > > > Thanks, Teco > > > > Op 9 dec. 2013, om 14:12 heeft Punky Tse <[email protected]> het volgende > geschreven: > >> Hi Teco, >> >> Please test daily to see what is still missing. >> >> Regards, >> Punky >> >> On 11/28/2013 2:18 AM, Teco Boot wrote: >>> Hi Punky, >>> >>> I’m preparing an upgrade procedure to 0.9.1 (or perhaps wait for new >>> 0.9.2). I’ll put some effort in having a clean boot. >>> Are the topics below addressed? I know this is minor, but it hides other >>> more important warnings. >>> >>> Thanks, Teco >>> >>> >>> Op 17 jul. 2013, om 15:31 heeft Erik van Linstee <[email protected]> >>> het volgende geschreven: >>> >>>> On 17-07-13 15:08, Punky Tse wrote: >>>>> I can't answer all, but try my best. But almost all of them do not >>>>> affect your operation, right? >>>> As far as I can tell, no they don't, but I am just getting started testing. >>>> >>>>> What ALIX board are you using? >>>> 2d13 >>>> >>>>> Not sure, perhaps you are using ALIX3d3. >>>> No, 2d13. It seems some ACPI device where expected but could not be found. >>>> >>>> >>>>>>> sed: can't create temp file '/root/etc/inittabYp7rxF': Read-only >>>>>> file system >>>>>>> done. >>>>> This is used for PXE installation, could safely ignore. >>>> I see. I disabled the line in the init-bottom script. >>>> >>>>>>> [ 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. >>>> Oke, will do. You will fix this in 0.9.x? >>>> >>>>>>> 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 >>>> I already did. But that does not help. This runs before the tmpfs is >>>> created. >>>> >>>> >>>>> This was fixed in voyage-util 0.12-4, after 0.9.1, the key could be >>>>> regenerated by "dpkg-reconfigure openssh-server" >>>> Great. >>>> >>>>> leds-alix is obsoleted. Leds is now using GPIO_CS5535 to drive. Works >>>>> on ALIX2 and ALIX3d2. >>>> Aha. >>>> >>>> Thanks >>>> Erik >>>> >>>> >>>> -- >>>> ir. E.J.P. (Erik) van Linstee >>>> Van Linstee ICT >>>> 0467-111230 >>>> >>>> >>>> _______________________________________________ >>>> Voyage-linux mailing list >>>> [email protected] >>>> http://list.voyage.hk/mailman/listinfo/voyage-linux >> >> >> -- >> >> 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
