[Voyage-linux] Immediate response
Well look at that. I got an immediate response from the list. Usually I hear nothing for months and then receive several months worth at once. ___ Voyage-linux mailing list Voyage-linux@list.voyage.hk http://list.voyage.hk/mailman/listinfo/voyage-linux
Re: [Voyage-linux] Voyage 0.11 and SDHC kernel/driver problem
On 07-06-17 05:45, Kim-man 'Punky' TSE wrote:
Hi Erik,
Please check if this kernel (32-bit only) fix for you:
http://mirror.voyage.hk/dists/experimental/linux/linux-image-4.9.25-voyage_18.0-1_i386.deb
Thanks, but...
when I posted my messages I received error messages about the list and
your account not being available. There also seemed to be hardly any
work being done on Voyage Linux.
Also, I need 64-bit.
So I started with building kernel 4.9.18, which was current for Jessie
at the time. I replaced your kernel package with this and that worked
well. I did not use the quirks.
Then I did what I had been wanting to do for a long time, but never did
since I could not justify the time, and that is investigate the Debian
live build system.
The result is that I now have my own live build that produces a complete
system exactly as I need it. Before that I started with Voyage and then
removed what I did not need and added what I did.
In the process I also cleaned up the initramfs-tools, because that kept
complaining that fsck.ext2 was not available. I did this by adding a
file to config/includes.chroot/usr/share/initramfs-tools/hooks with the
contents below. It makes sure fsck.ext2 is included in the initramfs
everytime it is rebuilt.
By doing so, the system can now do a fsck on the rootfs before it is
mounted.
I also improved some other parts that had some minor defects, such as
"voyage-util stop" giving an error on the directories that had write
access, by where not included when syncing.
#!/bin/sh
PREREQ=""
prereqs()
{
echo "$PREREQ"
}
case $1 in
# get pre-requisites
prereqs)
prereqs
exit 0
;;
esac
. /usr/share/initramfs-tools/hook-functions
# TODO Get fs type from some profile file.
for type in ext2; do
prog="/sbin/fsck.${type}"
if [ -h "$prog" ]; then
link=$(readlink -f "$prog")
copy_exec "$link"
ln -s "$link" "${DESTDIR}/$prog"
elif [ -x "$prog" ] ; then
copy_exec "$prog"
else
echo "Warning: /sbin/fsck.${type} doesn't exist, can't install
to initramfs, ignoring."
fi
done
___
Voyage-linux mailing list
Voyage-linux@list.voyage.hk
http://list.voyage.hk/mailman/listinfo/voyage-linux
[Voyage-linux] Release 0.11
Hi, Does anyone have any idea when 0.11 is ready to release? Or how mature it is? I need to work with APU2 boards and 0.10 does not seem to support the mmc. And I really need that for SD. regards, Erik -- View this message in context: http://voyage-linux.34677.n3.nabble.com/Release-0-11-tp4026559.html Sent from the Voyage Linux mailing list archive at Nabble.com. ___ Voyage-linux mailing list Voyage-linux@list.voyage.hk http://list.voyage.hk/mailman/listinfo/voyage-linux
[Voyage-linux] Voyage 0.11 and SDHC kernel/driver problem
I have been experimenting with Voyage current (0.11) lately and found that there is a problem with the SDHC driver. At least with fast SD card, such as the PcEngines pSLC SD. There are frequent time-outs which sometimes lead to the system freezing. I have installed the 4.9 kernel from Jessie backports and so far the problem has not returned. -- View this message in context: http://voyage-linux.34677.n3.nabble.com/Voyage-0-11-and-SDHC-kernel-driver-problem-tp4026562.html Sent from the Voyage Linux mailing list archive at Nabble.com. ___ Voyage-linux mailing list Voyage-linux@list.voyage.hk http://list.voyage.hk/mailman/listinfo/voyage-linux
[Voyage-linux] SDK says: chroot: binary/live/filesystem.dir no such file or directory
I am running the SDK iso and have pulled voyage-live from SVN. If I run ./build.sh tar everything goes smoothly for a long time, until: P: Saving caches... No /usr/local/sbin/mount-proc.sh, call Chroot() instead chroot: cannot change root directory to binary/live/filesystem.dir: No such file or directory And then nothing. What am I missing here? I have tried it both on an APU2, running the SDK from a USB stick, and in a Virtualbox VM. Same results. Doesn't produce an iso or img either. I have tried the 0.10.0 and 0.11.0 SDK, same result, nothing. -- View this message in context: http://voyage-linux.34677.n3.nabble.com/SDK-says-chroot-binary-live-filesystem-dir-no-such-file-or-directory-tp4026564.html Sent from the Voyage Linux mailing list archive at Nabble.com. ___ Voyage-linux mailing list Voyage-linux@list.voyage.hk http://list.voyage.hk/mailman/listinfo/voyage-linux
[Voyage-linux] Current (0.11) does not install on /dev/mmcblk0
I read in the Changelog that voyage-util supports MMC block devices (e.g. mmvblk0p1), so I expected that would also include all the other parts the expect block devices, especially voyage.update. But it seems it does not. It accepts /dev/mmcblk0 as a device name, but than happily cuts of the '0'. So when asked about the system device, it does not accept p0. It does accept 0p1, which leads it to continu until somewhere further on in the process it dies on 0p1 not being numerical. Obviously. I am very sad to see Voyage Linux having stagnated for so long. The APU devices have been out for a long while now, even re-engineered into APU already, but still no decent support from Voyage. I have been satisfied with Voyage on Alix devices for a long time, and have been putting off APU for a long time now to give Voyage a chance to catch up. I can't any longer. Before I have used symlinks to the mmcblk0 devices in order to fool voyage.update. I will be trying that again to see if 0.11 supports the APU2 mmc so that I can access the SD slot, and if it is stable enough. I might even invest some time into trying to fix the scripts. But I do hope Voyage gets more love and attention. -- View this message in context: http://voyage-linux.34677.n3.nabble.com/Current-0-11-does-not-install-on-dev-mmcblk0-tp4026560.html Sent from the Voyage Linux mailing list archive at Nabble.com. ___ Voyage-linux mailing list Voyage-linux@list.voyage.hk http://list.voyage.hk/mailman/listinfo/voyage-linux
[Voyage-linux] fsck fails during boot
When booting Voyage 0.10 and 0.11 fsck fails. I have tried several suggestions found with the help of Google, but nothing helped. Hopefully someone how knows how to build Voyage can find out more about which file or directory is missing exactly. The exact message on my APU 1D (same message, different dev on APU 2C2) is: Begin: Will now check root file system ... fsck from util-linux 2.25.2 fsck: error 2 (No such file or directory) while executing fsck.ext2 for /dev/sda2 fsck exited with status code 8 done. Warning: File system check failed but did not detect errors -- View this message in context: http://voyage-linux.34677.n3.nabble.com/fsck-fails-during-boot-tp4026563.html Sent from the Voyage Linux mailing list archive at Nabble.com. ___ Voyage-linux mailing list Voyage-linux@list.voyage.hk http://list.voyage.hk/mailman/listinfo/voyage-linux
Re: [Voyage-linux] Problems unmounting with voyage.update
On 07-08-15 03:48, Kim-man 'Punky' TSE wrote: Hi Erik, I traced the problem to setboot.sh, where an attempt is made to unmount /mnt/cf/dev, right after GRUB has been set up. If I add a sleep 1 before the unmount, there is no problem. If you get another chance to reproduce it, could you add sync instead of sleep 1 before unmount? I will, but it might take some time before I get around to it. Erik ___ Voyage-linux mailing list Voyage-linux@list.voyage.hk http://list.voyage.hk/mailman/listinfo/voyage-linux
[Voyage-linux] Problems unmounting with voyage.update
Hi, I recently noticed that if I create a new CF using voyage.update, at the end of the process the script complains that /mnt/cf/dev and /mnt/cf can't be unmounted. If I then unmount them manually, there is no problem. I traced the problem to setboot.sh, where an attempt is made to unmount /mnt/cf/dev, right after GRUB has been set up. If I add a sleep 1 before the unmount, there is no problem. Apparently there is a timing problem, which could in my case be due to the CF being mounted in a USB card-reader. I have reproduced the same behaviour on more than one machine, with different card readers (same make though). It seems that the failure to unmount does not result in an unfinished CF. Apparently the installation script is done anyway. But it might be smart to fix it, just to make sure people do not get confused by it. regards, Erik van Linstee ___ Voyage-linux mailing list Voyage-linux@list.voyage.hk http://list.voyage.hk/mailman/listinfo/voyage-linux
Re: [Voyage-linux] Voyage-linux Digest, Vol 103, Issue 15
On 31-07-13 06:00, voyage-linux-requ...@list.voyage.hk wrote: there is a config file (not sure and not near a pc, maybe /etc/module or so) where you can specify what modules need to be loaded at boot. Saves the trouble of unpacking/repacking initrd The file is /etc/modules. Below is mine, with the rtc module added as you can see. And two obsolete modules deactivated, but I suspect the next release, or maybe even one of the nightlies will fix that. - # /etc/modules: kernel modules to load at boot time. # # This file contains the names of kernel modules that should be loaded # at boot time, one per line. Lines beginning with # are ignored. # Parameters can be specified after the module name. # # These lines generated automatically by copyfiles.sh, # parsing VOYAGE_SYSTEM_MODULES from Profile: ALIX # on wo jul 17 12:43:18 CEST 2013 # lm90 #w83627hf scx200_acb geodewdt led-class #leds-alix2 ledtrig-heartbeat ledtrig-timer ledtrig-netdev rtc regards, Erik -- ir. E.J.P. (Erik) van Linstee Van Linstee ICT 0467-111230 ___ Voyage-linux mailing list Voyage-linux@list.voyage.hk http://list.voyage.hk/mailman/listinfo/voyage-linux
[Voyage-linux] Problem with 0.9.1 and timezone
Hi, It appears that the posix timezone info is missing. If you look at this excerpt, you will notice that European timezone files are all links to ../posix/Europe/country. But the directory ../posix does not exist. Anyone know how to fix this? And can someone fix it in the tarball distribution too? regards, Erik -- ir. E.J.P. (Erik) van Linstee Van Linstee ICT 0467-111230 ___ Voyage-linux mailing list Voyage-linux@list.voyage.hk http://list.voyage.hk/mailman/listinfo/voyage-linux
[Voyage-linux] Errors during boot of 0.9.1 on ALIX
Hi, 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. 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 :00:0f.0: 5 devices registered. 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. [6.488793] Error: Driver 'pcspkr' is already registered, aborting... [info] Loading kernel module w83627hf. ERROR: could not insert 'w83627hf': No such device 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. [] 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. 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. regards, Erik -- ir. E.J.P. (Erik) van Linstee Van Linstee ICT 0467-111230 ___ Voyage-linux mailing list Voyage-linux@list.voyage.hk http://list.voyage.hk/mailman/listinfo/voyage-linux
Re: [Voyage-linux] Problem with 0.9.1 and timezone
On 17-07-13 13:33, Kim-man 'Punky' TSE wrote: Some timezone data are intentionally deleted to save space (legacy code) To fix, reinstall tzdata: remountrw apt-get update apt-get install --reinstall tzdata. Regards, Thanks, I just realised that you added that to the getting started list. Sorry for asking :-) I also ran into some other errors that I have posted to the list. Mostly cosmetic I think. Erik -- ir. E.J.P. (Erik) van Linstee Van Linstee ICT 0467-111230 ___ Voyage-linux mailing list Voyage-linux@list.voyage.hk http://list.voyage.hk/mailman/listinfo/voyage-linux
Re: [Voyage-linux] Errors during boot of 0.9.1 on ALIX
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 Voyage-linux@list.voyage.hk http://list.voyage.hk/mailman/listinfo/voyage-linux
[Voyage-linux] Error during boot of 0.9.0
Hi, I noticed the following error during boot: [] Starting OpenBSD Secure Shell server: sshdCould not load host key: /etc/ssh/ssh_host_ecdsa_key regards, Erik -- ir. E.J.P. (Erik) van Linstee Van Linstee ICT 0467-111230 ___ Voyage-linux mailing list Voyage-linux@list.voyage.hk http://list.voyage.hk/mailman/listinfo/voyage-linux
[Voyage-linux] Missing files with 0.9.0 and boot errors
Hi, I have just installed Voyage Linux 0.9.0 from the tarball and found several files missing and some errors during boot. I double checked against the tarball and the files are missing from that too. - The entire directory /usr/share/zoneinfo/posix is missing, which makes it impossible to select the proper timezone. - The file /lib/modules/3.8.11-voyage/kernel/drivers/leds/leds-alix2 is also missing. Leds are blinking though. Also, during the boot process several errors are reported. 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/inittabJseZPM': Read-only file system done. And: [info] Loading kernel module w83627hf. ERROR: could not insert 'w83627hf': No such device Since the 2d13 uses lm90, it should not be trying to load this module in the first place. Maybe something to consider adding to the installation process? And: [info] Loading kernel module leds-alix2. FATAL: Module leds-alix2 not found. And after changing /etc/network/interfaces to have eth1 use DHCP: Internet Systems Consortium DHCP Client 4.2.2 Copyright 2004-2011 Internet Systems Consortium. All rights reserved. For info, please visit https://www.isc.org/software/dhcp/ can't create /var/lib/dhcp/dhclient.eth1.leases: No such file or directory regards, Erik -- ir. E.J.P. (Erik) van Linstee Van Linstee ICT 0467-111230 ___ Voyage-linux mailing list Voyage-linux@list.voyage.hk http://list.voyage.hk/mailman/listinfo/voyage-linux
