Hi Everyone,

So I have been catching up upgrading packages from
http://ftp.arm.slackware.com/slackwa...rch64-current/

But now I am unable to see permissions, nor date stamps of any files in the whole entire system.
for example, doing 'cd /' then ' ls -al' produces:
d????????? ? ? ? ? ? media
d????????? ? ? ? ? ? mnt
d????????? ? ? ? ? ? opt
d????????? ? ? ? ? ? proc
d????????? ? ? ? ? ? root
d????????? ? ? ? ? ? run
d????????? ? ? ? ? ? sbin
d????????? ? ? ? ? ? srv
d????????? ? ? ? ? ? swap
d????????? ? ? ? ? ? sys
d????????? ? ? ? ? ? tmp
d????????? ? ? ? ? ? tmp2
d????????? ? ? ? ? ? usr
d????????? ? ? ? ? ? var


Also, issuing 'ls /root (or any subdirectory name)' produces this message:
ls: cannot access '/root': Function not implemented Using /root as an example.

Doing ls of any specific filename produces this error: for example,
cd /bin
ls bash
ls: cannot access 'bash': Function not implemented


To do any work at all, I have to 'cd' to the subdirectory and then to an ls to at least get the file names to show up.

Should I recompile the kernel or upgrade the kernel from a rockpro64 kernel source.?

I dont know if it matters, but am running kernel 4.4.202

I already rebooted the rockpro64 but the issue still present.

Any ideas?

Thanks

This is exactly what is important; in Patrick’s slackware, the glibc setting looks like this:
in slackware aarch64:
slarm64 strictly adhered to the original scripts.

1 members found this post helpful.

I got a 6.x kernel source.

Would installing new kernel fix my problem with the directory permissions not showing up?

yes, it will completely solve your problem: kernel-rk3399#6.8.2-1.pkg.tar.gz unpack and replace the files, also check that dtb is registered in /boot/uEnv.txt

1 members found this post helpful.

hi There,

Thanks for your help. I am very close to rebooting my rockpro64 with the new kernel.

A couple of more questions:

Can you give an example of the dtb line in the uEnv.txt
Am confused if it points to the /boot/dtb subdirectory or a specific rockpro64.dtb file within it?

ie
dtb=/boot/dtb ?
or
dtb=rk3399-rockpro64.dtb ?



Also, my current /boot has some extra files:
boot.cmd
boot.scr

Do I keep these files using the new kernel?

thanks again

Hi,

The initial boot script is boot.cmd which is compiled into boot.scr and loaded by u-boot by default. it contains the prefix to DTB as /boot/dtb/ therefore it must be written in uEnv.txt fdtfile=rockchip/rk3399-rockpro64.dtb

1 members found this post helpful.

SOLVED.

Hey Admin, you can mark this as solved.

Thanks for helping.
Thanks for pointing me in the right direction.

1 members found this post helpful.