Problem installing extensions in 7.0alpha6 for armv6

[johand]

Raspberry Pi 1 A

How to reproduce:
- New install on SD card.
- Expand the mmcblk0p2 partition following this instruction http://tinycorelinux.net/7.x/armv6/test_releases/README (BTW, resize2fs require sudo, not mentioned in the instruction).
- Install wifi.tcz (with tce-ab).

Result:
wifi.tcz.dep OK
wireless_tools.tcz.dep OK
wpa_supplicant.tcz.dep OK
readline.tcz.dep OK
Downloading: wireless-4.1.7-piCore+.tcz
Connecting to repo.tinycorelinux.net (89.22.99.37:80)
wireless-4.1.7-piCor 100% |*******************************|  2620k  0:00:00 ETA
wireless-4.1.7-piCore+.tcz: OK
Downloading: libiw.tcz
Connecting to repo.tinycorelinux.net (89.22.99.37:80)
libiw.tcz            100% |*******************************| 16384   0:00:00 ETA
libiw.tcz: OK
mount: /mnt/mmcblk0p2/tce/optional/libiw.tcz: failed to setup loop device: No such file or directory


Everything seems OK if I manually add libiw.tcz to /mnt/mmcblk0p2/tce/onboot.lst and reboot.

Have seen this on multiple extensions. Have tried 3 or 4 times with same result. 7.0alpha3 is OK with same SD card in same Raspberry.

Johan

[bmarkus]

Hi Johan

thanks for reporting. I see it also randomly but only on the armv6 system, not on armv7. If you experience it with installing e.g. wifi.tcz try to install it again with

tce-load -iw wifi

It will install. If not, repeat till no error received. Once installed, it will be loaded correctly after reboot.

I'm investigating the cause.

[jgrulich]

I've mentioned similar issue when installing gzip.tcz. It doesn't modify the simlink in the /bin directory and therefor doesn't use the installed extension, but busybox.

[bmarkus]

I've mentioned similar issue when installing gzip.tcz. It doesn't modify the simlink in the /bin directory and therefor doesn't use the installed extension, but busybox.

gzip do not have to modify symlink in /bin, it is installed in /usr/local/bin as other extensions with command replacing BusyBox applets like in coreutils. They are installed in /usr/local/bin or /usr/local/sbin. In search order ($PATH) /usr/local/ has higher priority, system will use binary from /usr/local/bin instead of /usr/bin or /bin without any modification in base.

[jgrulich]

Yes, I know how it works, but the priority searching is not working until rebooted.

[jncl]

Hi,

  You can update the shell's hash table of commands

Code: [Select]

hash -rThis will allow the newly loaded commands to found.