Re: [Voyage-linux] fsck.ext2 stuck on -a, need -y
Hi, For anyone following this thread, the fix was to add fsck.repair=yes as a kernel boot parameter in /boot/grub/menu.lst. So: kernel /vmlinuz root=LABEL=VOYAGE_FS console=ttyS0,115200n8 Becomes: kernel /vmlinuz root=LABEL=VOYAGE_FS console=ttyS0,115200n8 fsck.repair=yes Then run: update-grub And presto on startup from a power loss: [/sbin/fsck.ext2 (1) -- /dev/sda1] fsck.ext2 -a -C0 /dev/sda1 Becomes: [/sbin/fsck.ext2 (1) -- /dev/sda1] fsck.ext2 -y -C0 /dev/sda1 Hope this helps someone. Cheers. On 21 September 2017 at 23:52, Erik van Linstee <e...@vanlinsteeict.nl> wrote: > > > On 21-09-17 07:28, Richard Warburton wrote: > > Hi, > > Thanks Erik for posting the fsck.ext2 fix. However, I notice that during > startup fsck runs with: > > [/sbin/fsck.ext2 (1) -- /dev/sda1] fsck.ext2 -a -C0 /dev/sda1 > > > note the -a. I need it to be -y. > > Because on the hard fixes it drops to BusyBox, and on an APU2, that's not > useful. > > At first I thought I wasn't setting the FSCKFIX correctly, but that > doesn't seem to be it. In fact given the order of parameters, I'm not > convinced it's running from checkroot.sh. I hardcoded fix="-y" in > checkroot.sh where the check was, so it wouldn't even matter what FSCKFIX > was set as. > > > You are right, it isn't running from checkroot.sh. fsck is called when the > system is booting from the initramfs. My fix makes sure fsck.ext2 is added > to the initramfs by the initramfs tools, which it wasn't before. > > I have no idea how the system in the initramfs decides to call fsck and > with which parameters. I may try to find out one day, but that does not > help you now. Sorry. > > Erik > ___ Voyage-linux mailing list Voyage-linux@list.voyage.hk http://list.voyage.hk/mailman/listinfo/voyage-linux
[Voyage-linux] fsck.ext2 stuck on -a, need -y
Hi, Thanks Erik for posting the fsck.ext2 fix. However, I notice that during startup fsck runs with: [/sbin/fsck.ext2 (1) -- /dev/sda1] fsck.ext2 -a -C0 /dev/sda1 note the -a. I need it to be -y. Because on the hard fixes it drops to BusyBox, and on an APU2, that's not useful. At first I thought I wasn't setting the FSCKFIX correctly, but that doesn't seem to be it. In fact given the order of parameters, I'm not convinced it's running from checkroot.sh. I hardcoded fix="-y" in checkroot.sh where the check was, so it wouldn't even matter what FSCKFIX was set as. Alas the boot messages remain the same. Can anyone help? Thanks. -- Richard Warburton - MSc(Hons), PGDipSci, BE(Hons) +64 9 377-2881 ext 9 Skagerrak Software - Senior Developer - http://www.skagerraksoftware.com/ 40/22a Willcott St, Mt Albert 1025 - PO Box 77039, Mt Albert, Auckland 1350 ___ Voyage-linux mailing list Voyage-linux@list.voyage.hk http://list.voyage.hk/mailman/listinfo/voyage-linux
Re: [Voyage-linux] Voyage 0.11.0 and APU2 no LEDs
Hi Bolle, Yes, your email got the leds fully working! Many thanks. For anyone else following, the modules exist but aren't being loaded on startup. After editing /etc/modules as you suggested, I was able turn the leds on an off but no heartbeat or timer etc. Adding VOYAGE_SYSTEM_MODULES to vi /etc/voyage.conf did nothing, but I could load them all by hand. So I simply added the module list to: vi /etc/modules (as opposed to just leds-apu2). And that was that. Thanks again Bolle! On 16 June 2017 at 18:01, <bo...@geodb.org> wrote: > Again me ;-) > > Maybe this could help you or bring you into the right direction. > > This is an excerpt from my manual installation: > > APU2# cp leds-apu2.ko /lib/modules/3.16.7-ckt9-voyage/kernel/drivers/leds/ > APU2# depmod -a > APU2# vi /etc/modules > >> >>>> leds-apu2 > <<< > APU2# modprobe leds-apu2 > > APU2# vi /etc/voyage.conf > >> >>>> VOYAGE_PROFILE=APU2 > VOYAGE_SYSTEM_MODULES="sp5100-tco; led-class; ledtrig-heartbeat; > ledtrig-timer; ledtrig-netdev; leds-apu2;" > <<< > > APU2# vi /etc/init.d/voyage-util > >> >>>> 'APU2') > echo heartbeat > /sys/class/leds/apu2\:2/trigger > echo ata1 > /sys/class/leds/apu2\:3/trigger > ;; > <<< > > The paths would differ on Voyage 0.11.0. The ">>>" and "<<<" are only > markers. > > I would check the following: > > - Does the kernel module exist ? > - Can you load the kernel module by hand ? > - Is the kernel module in the Voyage profile ? > > Andreas > > > On 2017-06-16 07:26, Richard Warburton wrote: > >> Thanks Andreas, >> >> Voyage 0.11.0 explicitly says that it supports APU2 leds in the >> release data (unless I'm reading it wrong), so I'm hoping it's a minor >> config issue. >> >> If I have no luck, I might have a go with the sources you provide. >> >> Thanks again. >> >> On 16 June 2017 at 17:18, <bo...@geodb.org> wrote: >> >> Hello Richard >>> >>> I don't know about a simple fix. On my APU2s with Voyage 0.10.0, the >>> kernel module has been missing. >>> >>> Using the Voyage SDK, I've compiled and installed the missing kernel >>> module using this sources: >>> http://daduke.org/dl/apu2-leds.tgz [2] >>> >>> >>> On Voyage 0.11.0, it could be the same problem. >>> >>> Cheers >>> Andreas >>> >>> On 2017-06-16 07:06, Richard Warburton wrote: >>> >>> Fresh install of Voyage 0.11.0, alas on startup I see the >>>> message: >>>> /etc/init.d/voyage-util: 76: /etc/init.d/voyage-util: cannot >>>> create >>>> /sys/class/leds/apu2:1/trigger: Directory nonexistent >>>> /etc/init.d/voyage-util: 77: /etc/init.d/voyage-util: cannot >>>> create >>>> /sys/class/leds/apu2:3/trigger: Directory nonexistent >>>> >>>> /etc/init.d/voyage-util: 78: /etc/init.d/voyage-util: cannot >>>> create >>>> /sys/class/leds/apu2:3/trigger: Directory nonexistent >>>> >>>> /etc/init.d/voyage-util: 79: /etc/init.d/voyage-util: cannot >>>> create >>>> /sys/class/leds/apu2:3/trigger: Directory nonexistent >>>> >>>> Looking inside /sys/class/leds, there's only one directory called >>>> mmc0:: >>>> >>>> Is there a simple fix for this? I tried the current release as >>>> well, >>>> but no dice. >>>> >>>> Thanks in advance. >>>> ___ >>>> Voyage-linux mailing list >>>> Voyage-linux@list.voyage.hk >>>> http://list.voyage.hk/mailman/listinfo/voyage-linux [1] >>>> >>> >> -- >> >> Richard Warburton - MSc(Hons), PGDipSci, BE(Hons) +64 9 377-2881 ext 9 >> Skagerrak Software - Senior Developer - >> http://www.skagerraksoftware.com/ >> >> 40/22a Willcott St, Mt Albert 1025 - PO Box 77039, Mt Albert, Auckland >> 1350 >> >> Links: >> -- >> [1] http://list.voyage.hk/mailman/listinfo/voyage-linux >> [2] http://daduke.org/dl/apu2-leds.tgz >> > -- Richard Warburton - MSc(Hons), PGDipSci, BE(Hons) +64 9 377-2881 ext 9 Skagerrak Software - Senior Developer - http://www.skagerraksoftware.com/ 40/22a Willcott St, Mt Albert 1025 - PO Box 77039, Mt Albert, Auckland 1350 ___ 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
Bit off topic, but I'd just like to say thanks to Erik for posting the fsck.ext2 fix. After following the instructions and running "update-initramfs -u", it now fixes any errors on startup. Hope it gets added to the next release! Thanks. -- Richard Warburton - MSc(Hons), PGDipSci, BE(Hons) +64 9 377-2881 ext 9 Skagerrak Software - Senior Developer - http://www.skagerraksoftware.com/ 40/22a Willcott St, Mt Albert 1025 - PO Box 77039, Mt Albert, Auckland 1350 ___ Voyage-linux mailing list Voyage-linux@list.voyage.hk http://list.voyage.hk/mailman/listinfo/voyage-linux
Re: [Voyage-linux] Voyage 0.11.0 and APU2 no LEDs
Thanks Andreas, Voyage 0.11.0 explicitly says that it supports APU2 leds in the release data (unless I'm reading it wrong), so I'm hoping it's a minor config issue. If I have no luck, I might have a go with the sources you provide. Thanks again. On 16 June 2017 at 17:18, <bo...@geodb.org> wrote: > Hello Richard > > I don't know about a simple fix. On my APU2s with Voyage 0.10.0, the > kernel module has been missing. > > Using the Voyage SDK, I've compiled and installed the missing kernel > module using this sources: > http://daduke.org/dl/apu2-leds.tgz > > On Voyage 0.11.0, it could be the same problem. > > Cheers > Andreas > > > > On 2017-06-16 07:06, Richard Warburton wrote: > >> Fresh install of Voyage 0.11.0, alas on startup I see the message: >> /etc/init.d/voyage-util: 76: /etc/init.d/voyage-util: cannot create >> /sys/class/leds/apu2:1/trigger: Directory nonexistent >> /etc/init.d/voyage-util: 77: /etc/init.d/voyage-util: cannot create >> /sys/class/leds/apu2:3/trigger: Directory nonexistent >> >> /etc/init.d/voyage-util: 78: /etc/init.d/voyage-util: cannot create >> /sys/class/leds/apu2:3/trigger: Directory nonexistent >> >> /etc/init.d/voyage-util: 79: /etc/init.d/voyage-util: cannot create >> /sys/class/leds/apu2:3/trigger: Directory nonexistent >> >> Looking inside /sys/class/leds, there's only one directory called >> mmc0:: >> >> Is there a simple fix for this? I tried the current release as well, >> but no dice. >> >> Thanks in advance. >> ___ >> Voyage-linux mailing list >> Voyage-linux@list.voyage.hk >> http://list.voyage.hk/mailman/listinfo/voyage-linux >> > -- Richard Warburton - MSc(Hons), PGDipSci, BE(Hons) +64 9 377-2881 ext 9 Skagerrak Software - Senior Developer - http://www.skagerraksoftware.com/ 40/22a Willcott St, Mt Albert 1025 - PO Box 77039, Mt Albert, Auckland 1350 ___ Voyage-linux mailing list Voyage-linux@list.voyage.hk http://list.voyage.hk/mailman/listinfo/voyage-linux
[Voyage-linux] Voyage 0.11.0 and APU2 no LEDs
Fresh install of Voyage 0.11.0, alas on startup I see the message: /etc/init.d/voyage-util: 76: /etc/init.d/voyage-util: cannot create /sys/class/leds/apu2:1/trigger: Directory nonexistent /etc/init.d/voyage-util: 77: /etc/init.d/voyage-util: cannot create /sys/class/leds/apu2:3/trigger: Directory nonexistent /etc/init.d/voyage-util: 78: /etc/init.d/voyage-util: cannot create /sys/class/leds/apu2:3/trigger: Directory nonexistent /etc/init.d/voyage-util: 79: /etc/init.d/voyage-util: cannot create /sys/class/leds/apu2:3/trigger: Directory nonexistent Looking inside /sys/class/leds, there's only one directory called mmc0:: Is there a simple fix for this? I tried the current release as well, but no dice. Thanks in advance. ___ Voyage-linux mailing list Voyage-linux@list.voyage.hk http://list.voyage.hk/mailman/listinfo/voyage-linux
[Voyage-linux] FSCK No such file or directory on startup.
Hi, I have a PCEngines APU running Voyage Linux Version: 0.10.0 on an sd card. I enabled fsck at startup (setting FSCKFIX=yes in /etc/default/rcS) as I've disabled remounting as readonly in /etc/init.d/voyage-util. However I see during startup connect via serial: Begin: Checking root file system ... fsck from util-linux 2.25.2 fsck: error 2 (No such file or directory) while executing fsck.ext2 for /dev/sda1 fsck exited with status code 8 Warning: File system check failed but did not detect errors This is strange as from the command line I can switch the filesystem to read only and fsck /dev/sda1 just fine. Mount point entry says: /dev/sda1 on / type ext2 (rw,noatime,errors=continue) Any solutions or pointers appreciated. Thanks. -- Richard Warburton - MSc(Hons), PGDipSci, BE(Hons) +64 9 377-2881 ext 9 Skagerrak Software - Senior Developer - http://www.skagerraksoftware.com/ 40/22a Willcott St, Mt Albert 1025 - PO Box 77039, Mt Albert, Auckland 1350 ___ Voyage-linux mailing list Voyage-linux@list.voyage.hk http://list.voyage.hk/mailman/listinfo/voyage-linux
[Voyage-linux] Fwd: iptables quota2
Hi, I'm trying (unsuccessfully) to install the quota2 pkg for iptables on a PCEngines APU board since quota isn't thread safe and doesn't work accurately on multicore systems. # apt-get install xtables-addons-dkms Reading package lists... Done Building dependency tree Reading state information... Done Recommended packages: linux-headers-generic linux-headers The following NEW packages will be installed: xtables-addons-dkms 0 upgraded, 1 newly installed, 0 to remove and 0 not upgraded. Need to get 0 B/150 kB of archives. After this operation, 590 kB of additional disk space will be used. WARNING: The following packages cannot be authenticated! xtables-addons-dkms Authentication warning overridden. perl: warning: Setting locale failed. perl: warning: Please check that your locale settings: LANGUAGE = (unset), LC_ALL = (unset), LANG = en_NZ.UTF-8 are supported and installed on your system. perl: warning: Falling back to the standard locale (C). debconf: unable to initialize frontend: Dialog debconf: (No usable dialog-like program is installed, so the dialog based frontend cannot be used. at /usr/share/perl5/Debconf/FrontEnd/Dialog.pm line 76, line 1.) debconf: falling back to frontend: Readline Selecting previously unselected package xtables-addons-dkms. (Reading database ... 13932 files and directories currently installed.) Unpacking xtables-addons-dkms (from .../xtables-addons-dkms_1.42-2_all.deb) ... Setting up xtables-addons-dkms (1.42-2) ... Loading new xtables-addons-1.42 DKMS files... First Installation: checking all kernels... Building only for 3.14.12-voyage Module build for the currently running kernel was skipped since the kernel source for this kernel does not seem to be installed. I've tried installing linux-source and linux-source-3.14.12-voyage, but no luck. Still won't build the module. Currently running Voyage 0.9.5 (link from PCEngines), but I see there's a later release... will that help? Also, installing xtables-addons-dkms has a lot of dependencies for a tiny kernel module, making the footprint huge (extra 150MB+). Is there a way around this? Does anyone have a pre-built package module? Many thanks in advance, Richard. ___ Voyage-linux mailing list Voyage-linux@list.voyage.hk http://list.voyage.hk/mailman/listinfo/voyage-linux
[Voyage-linux] iptables quota2
Hi, I'm trying (unsuccessfully) to install the quota2 pkg for iptables on a PCEngines APU board since quota isn't thread safe and doesn't work accurately on multicore systems. # apt-get install xtables-addons-dkms Reading package lists... Done Building dependency tree Reading state information... Done Recommended packages: linux-headers-generic linux-headers The following NEW packages will be installed: xtables-addons-dkms 0 upgraded, 1 newly installed, 0 to remove and 0 not upgraded. Need to get 0 B/150 kB of archives. After this operation, 590 kB of additional disk space will be used. WARNING: The following packages cannot be authenticated! xtables-addons-dkms Authentication warning overridden. perl: warning: Setting locale failed. perl: warning: Please check that your locale settings: LANGUAGE = (unset), LC_ALL = (unset), LANG = en_NZ.UTF-8 are supported and installed on your system. perl: warning: Falling back to the standard locale (C). debconf: unable to initialize frontend: Dialog debconf: (No usable dialog-like program is installed, so the dialog based frontend cannot be used. at /usr/share/perl5/Debconf/FrontEnd/Dialog.pm line 76, line 1.) debconf: falling back to frontend: Readline Selecting previously unselected package xtables-addons-dkms. (Reading database ... 13932 files and directories currently installed.) Unpacking xtables-addons-dkms (from .../xtables-addons-dkms_1.42-2_all.deb) ... Setting up xtables-addons-dkms (1.42-2) ... Loading new xtables-addons-1.42 DKMS files... First Installation: checking all kernels... Building only for 3.14.12-voyage Module build for the currently running kernel was skipped since the kernel source for this kernel does not seem to be installed. I've tried installing linux-source and linux-source-3.14.12-voyage, but no luck. Still won't build the module. Currently running Voyage 0.9.5 (link from PCEngines), but I see there's a later release... will that help? Also, installing xtables-addons-dkms has a lot of dependencies for a tiny kernel module, making the footprint huge (extra 150MB+). Is there a way around this? Does anyone have a pre-built package module? Many thanks in advance, Richard. ___ Voyage-linux mailing list Voyage-linux@list.voyage.hk http://list.voyage.hk/mailman/listinfo/voyage-linux
