README-kernels.txt? failed to create symbolic links

The SARPi project forum. For anything and everything relating to Slackware ARM on a Raspberry Pi 1, 2, and 3. This forum is NOT a replacement or substitute for the Slackware (ARM) forums on Linux Questions website! Please try to seek help there first about any issues you may be experiencing, or question you might have, before posting on here.
User avatar
glorsplitz
Registered user
Registered user
Posts: 35
Joined: Sun Aug 07 2016 - 22:54:24

README-kernels.txt? failed to create symbolic links

Postby glorsplitz » Wed Oct 05 2016 - 02:29:29

I'm trying to get familiar with slackware arm vs what I know about plain old slackware and followed the SARPI install guides and got a system up and running, not sure what's going on with updates.

Just noticed README-kernels.txt says something about "a number of symbolic links and their corresponding versioned file."

When I ran last slackpkg upgrade-all today and it was running through kernel upgrade, I noticed a few lines saying the following:
Executing install script for kernel_armv7-4.7.6-arm-1.txz.
ln: failed to create symbolic link 'uImage-armv7': Operation not permitted

After slackpkg upgrade-all completed I tried to do
ln -s /boot/uImage-armv7-4.7.6 /boot/uImage-armv7
and got
ln: failed to create symbolic link '/boot/uImage-armv7': Operation not permitted
just like slackpkg upgrade-all

There are no symbolic links in /boot.

Not sure what I missed in install guides or has something changed since I last installed?

THANKS!

if it helps any here's boot folder:
total 51256
drwx------ 4 root root 16384 Oct 3 13:02 ./
drwxr-xr-x 21 root root 4096 Oct 4 19:54 ../
-rw------- 1 root root 41 Oct 4 19:27 .firmware_revision
-rw------- 1 root root 18693 Aug 27 15:28 COPYING.linux
-rw------- 1 root root 1494 Aug 27 15:28 LICENCE.broadcom
-rw------- 1 root root 7178 Sep 5 15:10 README
-rw------- 1 root root 2530 Sep 26 16:25 README-kernels.txt
-rw------- 1 root root 699 Sep 5 13:57 README.boot
-rw------- 1 root root 2081770 Sep 5 13:58 System.map
-rw------- 1 root root 2673392 Oct 3 12:57 System.map-armv7-4.7.6
-rw------- 1 root root 14273 Oct 4 19:26 bcm2708-rpi-b-plus.dtb
-rw------- 1 root root 14010 Oct 4 19:26 bcm2708-rpi-b.dtb
-rw------- 1 root root 13964 Oct 4 19:26 bcm2708-rpi-cm.dtb
-rw------- 1 root root 15356 Oct 4 19:26 bcm2709-rpi-2-b.dtb
-rw------- 1 root root 15992 Oct 4 19:26 bcm2710-rpi-3-b.dtb
-rw------- 1 root root 15343 Oct 4 19:26 bcm2710-rpi-cm3.dtb
-rw------- 1 root root 17932 Oct 4 19:26 bootcode.bin
-rw------- 1 root root 89 Jan 1 1980 cmdline.txt
-rw------- 1 root root 182313 Oct 3 12:57 config-armv7-4.7.6
-rw------- 1 root root 1655 Sep 22 21:36 config.txt
drwx------ 2 root root 45056 Oct 3 13:02 dtb-4.7.6/
-rw------- 1 root root 6504 Oct 4 19:26 fixup.dat
-rw------- 1 root root 2532 Oct 4 19:26 fixup_cd.dat
-rw------- 1 root root 9744 Oct 4 19:26 fixup_db.dat
-rw------- 1 root root 9740 Oct 4 19:26 fixup_x.dat
-rw------- 1 root root 9077050 Oct 3 12:57 initrd-armv7-4.7.6
-rw------- 1 root root 4127480 Oct 4 19:26 kernel.img
-rw------- 1 root root 4229408 Oct 4 19:26 kernel7.img
drwx------ 2 root root 8192 Oct 4 19:26 overlays/
-rw------- 1 root root 2763940 Oct 4 19:26 start.elf
-rw------- 1 root root 633252 Oct 4 19:26 start_cd.elf
-rw------- 1 root root 4944996 Oct 4 19:26 start_db.elf
-rw------- 1 root root 3895396 Oct 4 19:26 start_x.elf
-rw------- 1 root root 4258512 Oct 3 12:57 uImage-armv7-4.7.6
-rw------- 1 root root 9077114 Oct 3 12:57 uinitrd-armv7-4.7.6
-rw------- 1 root root 103 Sep 5 13:58 version-kernel_rpi3.txt
-rw------- 1 root root 99 Sep 5 13:57 version-rpi3-boot.txt
-rw------- 1 root root 4258448 Oct 3 12:57 zImage-armv7-4.7.6

After reboot:
Linux slackrpi 4.4.23-v7+ #913 SMP Tue Oct 4 14:16:19 BST 2016 armv7l BCM2709 GNU/Linux

User avatar
linicks
Registered user
Registered user
Posts: 124
Joined: Mon Oct 27 2014 - 20:26:01
Location: Pompey, England

Re: README-kernels.txt? failed to create symbolic links

Postby linicks » Wed Oct 05 2016 - 15:19:20

I've never used Slack tools to update the kernel - I use rpi-update:

http://rpi.fatdog.eu/?p=rpiupdate

Always works (for me, at least).

Nick
EDIT: I don't update kernels much on my Pi's, as everything works fine - but I just ran rpi-update on my Pi test server - here's what to expect:

Code: Select all


root@pitest:~# rpi-update
 *** Raspberry Pi firmware updater by Hexxeh, enhanced by AndrewS and Dom
 *** Performing self-update
 *** Relaunching after update
 *** Raspberry Pi firmware updater by Hexxeh, enhanced by AndrewS and Dom
This update bumps to rpi-4.4.y linux tree
Be aware there could be compatibility issues with some drivers
Discussion here:
https://www.raspberrypi.org/forums/viewtopic.php?f=29&t=144087
##############################################################
 *** Downloading specific firmware revision (this will take a few minutes)
  % Total    % Received % Xferd  Average Speed   Time    Time     Time  Current
                                 Dload  Upload   Total   Spent    Left  Speed
100   168    0   168    0     0    175      0 --:--:-- --:--:-- --:--:--   180
100 51.7M  100 51.7M    0     0   554k      0  0:01:35  0:01:35 --:--:--  397k
 *** Updating firmware
 *** Updating kernel modules
 *** depmod 4.4.23+
 *** depmod 4.4.23-v7+
 *** Updating VideoCore libraries
 *** Using SoftFP libraries
 *** Updating SDK
 *** Running ldconfig
 *** Storing current firmware revision
 *** Deleting downloaded files
 *** Syncing changes to disk
 *** If no errors appeared, your firmware was successfully updated to 9063f3eefb3469fcf2e9181aa623d2ca4908a675
 *** A reboot is needed to activate the new firmware
https://linicks.net/

Q. What is the difference between a duck and an elephant?
A. You can't get down off an elephant.

User avatar
Exaga
FatDog Network Administrator
FatDog Network Administrator
Posts: 194
Joined: Wed Apr 18 2012 - 02:01:03
Location: England [UK]

Re: README-kernels.txt? failed to create symbolic links

Postby Exaga » Wed Oct 05 2016 - 16:45:45

glorsplitz wrote:There are no symbolic links in /boot.


No, because the /boot partition on a Raspberry Pi is formatted FAT32. :high:
Exaga

====
__ KEEP THE DOG ALIVE!!!
()'`; /
/\|` W00f W00f W00f
www.fatdog.eu

User avatar
linicks
Registered user
Registered user
Posts: 124
Joined: Mon Oct 27 2014 - 20:26:01
Location: Pompey, England

Re: README-kernels.txt? failed to create symbolic links

Postby linicks » Wed Oct 05 2016 - 17:00:48

Duh - I knew there was a simple reason.

Nice one - something you don't think about.

Nick
https://linicks.net/

Q. What is the difference between a duck and an elephant?
A. You can't get down off an elephant.

User avatar
glorsplitz
Registered user
Registered user
Posts: 35
Joined: Sun Aug 07 2016 - 22:54:24

Re: README-kernels.txt? failed to create symbolic links

Postby glorsplitz » Wed Oct 05 2016 - 21:13:24

thanks for replies

uncommented kernel stuff in /etc/slackpkg/blacklist

have rpi-update installed and will use that

CHEERS

User avatar
Exaga
FatDog Network Administrator
FatDog Network Administrator
Posts: 194
Joined: Wed Apr 18 2012 - 02:01:03
Location: England [UK]

Re: README-kernels.txt? failed to create symbolic links

Postby Exaga » Wed Oct 05 2016 - 21:37:40

linicks wrote:Duh - I knew there was a simple reason.

Nice one - something you don't think about.


Nick :lol:

Ja, I guess it's not on your mind if you don't deal with the /boot partition and files regularly. Most users will expect it to be ext4 or something. However, the /boot partition on a RPi _must_ be FAT32. EXT*, NTFS, FAT16 won't work. As we all know, NTFS, FAT32, FAT16 filesystems don't support symlinks.

http://sarpi.fatdog.eu/index.php?p=sdconfig

I've modified the SARPi guide in places to highlight that a FAT32 partition is essential in order for the RPi to boot. :geek:

@glorsplitz - you're welcome. ;)
Exaga

====
__ KEEP THE DOG ALIVE!!!
()'`; /
/\|` W00f W00f W00f
www.fatdog.eu

Return to “SARPi Project - Slackware ARM on a Raspberry Pi”

Who is online

Users browsing this forum: CommonCrawl [Bot] and 0 guests