Forum

Ok, but can you please check if

a) enough space available on that partition
b) you can create a file on that partition
c) try to reinstall xbian-package-initramfs-tools, maybe this one is not correctly installed

(20th Mar, 2018 04:30 AM)Nachteule Wrote: [ -> ]Ok, but can you please check if

a) enough space available on that partition
b) you can create a file on that partition
c) try to reinstall xbian-package-initramfs-tools, maybe this one is not correctly installed

a) 34Mb available (=49%)
b) No problem creating a file on /boot
c) I run in same problem that the script gets stuck:

xbian@xbian ~ $ sudo apt-get install --reinstall xbian-package-initramfs-tools
Reading package lists... Done
Building dependency tree
Reading state information... Done
0 upgraded, 0 newly installed, 1 reinstalled, 0 to remove and 0 not upgraded.
Need to get 19.9 kB of archives.
After this operation, 0 B of additional disk space will be used.
Get:1 http://apt.xbian.org stable/main armhf xbian-package-initramfs-tools armhf 20180317-0 [19.9 kB]
Fetched 19.9 kB in 8s (2,309 B/s)
Create a snapshot of '/run/btrfs-snap/root/@' in '/run/btrfs-snap/root/@btrfs-auto-snap_apt-run-2018-03-19-2108'
Delete subvolume (no-commit): '/run/btrfs-snap/root/@last_good_known'
Create a snapshot of '/run/btrfs-snap/root/@btrfs-auto-snap_apt-run-2018-03-19-2108' in '/run/btrfs-snap/root/@last_good_known'
Delete subvolume (no-commit): '/run/btrfs-snap/root/@btrfs-auto-snap_apt-run-2018-03-18-1319'
@btrfs-auto-snap_apt-run-2018-03-19-2108, 1 created snapshots, 1 destroyed snapshots, 0 warnings.
(Reading database ... 38304 files and directories currently installed.)
Preparing to unpack .../xbian-package-initramfs-tools_20180317-0_armhf.deb ...
Unpacking xbian-package-initramfs-tools (20180317-0) over (20180317-0) ...
Replaced by files in installed package xbian-package-repo (20180305-0) ...
Setting up xbian-package-initramfs-tools (20180317-0) ...
Processing triggers for xbian-package-initramfs-tools (20180317-0) ...

Progress: [ 75%] [###########################################...............]

And then the script does not complete...

Hmmm, lets run xbian-update-initramfs manually to see what's going on


Must stuck anywhere ... or print at least error message

(20th Mar, 2018 06:43 AM)Nachteule Wrote: [ -> ]Hmmm, lets run xbian-update-initramfs manually to see what's going on

Terminal

sudo xbian-update-initramfs

Must stuck anywhere ... or print at least error message

No error message as far as I can see.
A lot of text of text scrolling by so this is the last part of it:

'/usr/bin/stdbuf' -> './usr/bin/stdbuf'
again /lib/arm-linux-gnueabihf/libc-2.24.so
again /lib/arm-linux-gnueabihf/ld-2.24.so
again /lib/arm-linux-gnueabihf/ld-2.24.so
'/usr/bin/setterm' -> './usr/bin/setterm'
again /lib/arm-linux-gnueabihf/libtinfo.so.5.9
again /lib/arm-linux-gnueabihf/libc-2.24.so
again /lib/arm-linux-gnueabihf/ld-2.24.so
again /lib/arm-linux-gnueabihf/ld-2.24.so
'/usr/bin/mkimage' -> './usr/bin/mkimage'
again /lib/arm-linux-gnueabihf/libc-2.24.so
again /lib/arm-linux-gnueabihf/ld-2.24.so
again /lib/arm-linux-gnueabihf/ld-2.24.so

And then it gets stuck and does not return to prompt...

Ok, now we know that the script stucks at the end of the copy process

Could you please make 2 changes in file /etc/xbian-initramfs/update-initramfs.sh


change to


and add


after line


and run command again

These are the last lines again now with stderr and debug:

'/usr/bin/stdbuf' -> './usr/bin/stdbuf'
cp: cannot stat 'linux-vdso.so.1': No such file or directory
again /lib/arm-linux-gnueabihf/libc-2.24.so
again /lib/arm-linux-gnueabihf/ld-2.24.so
again /lib/arm-linux-gnueabihf/ld-2.24.so
'/usr/bin/setterm' -> './usr/bin/setterm'
cp: cannot stat 'linux-vdso.so.1': No such file or directory
again /lib/arm-linux-gnueabihf/libtinfo.so.5.9
again /lib/arm-linux-gnueabihf/libc-2.24.so
again /lib/arm-linux-gnueabihf/ld-2.24.so
again /lib/arm-linux-gnueabihf/ld-2.24.so
'/usr/bin/mkimage' -> './usr/bin/mkimage'
cp: cannot stat 'linux-vdso.so.1': No such file or directory
again /lib/arm-linux-gnueabihf/libc-2.24.so
again /lib/arm-linux-gnueabihf/ld-2.24.so
again /lib/arm-linux-gnueabihf/ld-2.24.so
+ '[' xauto = xyes ']'
+ grep -q vnc

Ah, strange. Variable bootfile is not set, so grep is waiting ...

Could you please post output of command


Should be RPI

(20th Mar, 2018 07:59 AM)Nachteule Wrote: [ -> ]Ah, strange. Variable bootfile is not set, so grep is waiting ...

Could you please post output of command

Terminal

xbian-arch

Should be RPI

Nope.
It outputs:

xbian@xbian ~ $ xbian-arch
unknown

Hmmmmmmmm ?????

Please post output of

rpi_revision

and

cat /proc/cpuinfo

(20th Mar, 2018 08:06 AM)Nachteule Wrote: [ -> ]Hmmmmmmmm ?????

Please post output of

rpi_revision

and

cat /proc/cpuinfo

xbian@xbian ~ $ rpi_revision
getRaspberryPiInformation() failed ...
xbian@xbian ~ $ cat /proc/cpuinfo
processor : 0
model name : ARMv7 Processor rev 4 (v7l)
BogoMIPS : 38.40
Features : half thumb fastmult vfp edsp neon vfpv3 tls vfpv4 idiva idivt vfpd32 lpae evtstrm crc32
CPU implementer : 0x41
CPU architecture: 7
CPU variant : 0x0
CPU part : 0xd03
CPU revision : 4

processor : 1
model name : ARMv7 Processor rev 4 (v7l)
BogoMIPS : 38.40
Features : half thumb fastmult vfp edsp neon vfpv3 tls vfpv4 idiva idivt vfpd32 lpae evtstrm crc32
CPU implementer : 0x41
CPU architecture: 7
CPU variant : 0x0
CPU part : 0xd03
CPU revision : 4

processor : 2
model name : ARMv7 Processor rev 4 (v7l)
BogoMIPS : 38.40
Features : half thumb fastmult vfp edsp neon vfpv3 tls vfpv4 idiva idivt vfpd32 lpae evtstrm crc32
CPU implementer : 0x41
CPU architecture: 7
CPU variant : 0x0
CPU part : 0xd03
CPU revision : 4

processor : 3
model name : ARMv7 Processor rev 4 (v7l)
BogoMIPS : 38.40
Features : half thumb fastmult vfp edsp neon vfpv3 tls vfpv4 idiva idivt vfpd32 lpae evtstrm crc32
CPU implementer : 0x41
CPU architecture: 7
CPU variant : 0x0
CPU part : 0xd03
CPU revision : 4

Hardware : Generic DT based system
Revision : 0000
Serial : 0000000052c4f1c5

Ehm, what in hell happened with your Pi????

The output of /proc/cpuinfo should be somthing like that:

Hardware : BCM2835
Revision : a02082
Serial : 0000000012345678

I suppose your dtb files in /boot folder are missing, broken or doesn't fit to your running kernel - in other words:
your /boot folder seems to be broken

if xbian-arch reports garbage, kernel can not be installed correctly and a lot of scripts may not work

So we are back to my previous posts: please check your boot partition (/boot) and post output

df /boot

and

ls -la /boot

xbian@xbian ~ $ df /boot
Filesystem 1K-blocks Used Available Use% Mounted on
/dev/mmcblk0p1 69478 35404 34074 51% /boot
xbian@xbian ~ $ ls -la /boot
total 35000
drwxr-xr-x 4 root root 16384 Mar 19 21:47 .
drwxr-xr-x 1 root root 174 Mar 18 13:23 ..
-rwxr-xr-x 1 root root 22308 Mar 8 03:57 bcm2708-rpi-0-w.dtb
-rwxr-xr-x 1 root root 21805 Mar 8 03:57 bcm2708-rpi-b.dtb
-rwxr-xr-x 1 root root 22064 Mar 8 03:57 bcm2708-rpi-b-plus.dtb
-rwxr-xr-x 1 root root 21518 Mar 8 03:57 bcm2708-rpi-cm.dtb
-rwxr-xr-x 1 root root 23088 Mar 8 03:57 bcm2709-rpi-2-b.dtb
-rwxr-xr-x 1 root root 24284 Mar 8 03:57 bcm2710-rpi-3-b.dtb
-rwxr-xr-x 1 root root 22996 Mar 8 03:57 bcm2710-rpi-cm3.dtb
-rwxr-xr-x 1 root root 16581 Mar 8 03:57 bcm2835-rpi-a.dtb
-rwxr-xr-x 1 root root 16697 Mar 8 03:57 bcm2835-rpi-a-plus.dtb
-rwxr-xr-x 1 root root 16727 Mar 8 03:57 bcm2835-rpi-b.dtb
-rwxr-xr-x 1 root root 16984 Mar 8 03:57 bcm2835-rpi-b-plus.dtb
-rwxr-xr-x 1 root root 16860 Mar 8 03:57 bcm2835-rpi-b-rev2.dtb
-rwxr-xr-x 1 root root 16685 Mar 8 03:57 bcm2835-rpi-zero.dtb
-rwxr-xr-x 1 root root 16957 Mar 8 03:57 bcm2835-rpi-zero-w.dtb
-rwxr-xr-x 1 root root 17496 Mar 8 03:57 bcm2836-rpi-2-b.dtb
-rwxr-xr-x 1 root root 17314 Mar 8 03:57 bcm2837-rpi-3-b.dtb
-rwxr-xr-x 1 root root 52064 Mar 17 16:14 bootcode.bin
-rwxr-xr-x 1 root root 295 Feb 7 20:37 cmdline.default
-rwxr-xr-x 1 root root 295 Feb 18 13:42 cmdline.txt
-rwxr-xr-x 1 root root 295 Jan 19 11:03 cmdline.txt.old
-rwxr-xr-x 1 root root 156 Mar 18 13:22 config.txt
-rwxr-xr-x 1 root root 18693 Mar 18 13:22 COPYING.linux
-rwxr-xr-x 1 root root 9723 Mar 17 16:14 fixup.dat
-rwxr-xr-x 1 root root 9721 Mar 17 16:14 fixup_db.dat
-rwxr-xr-x 1 root root 8177885 Mar 19 21:47 initramfs.gz
-rwxr-xr-x 1 root root 8177860 Mar 19 19:56 initramfs.gz.old
-rwxr-xr-x 1 root root 5621944 Mar 8 03:57 kernel.img
-rwxr-xr-x 1 root root 1494 Mar 18 13:22 LICENCE.broadcom
drwxr-xr-x 2 root root 12288 Mar 18 13:22 overlays
-rwxr-xr-x 1 root root 76746 Mar 8 03:57 README.overlays
-rwxr-xr-x 1 root root 4966148 Mar 17 16:14 start_db.elf
-rwxr-xr-x 1 root root 3910244 Mar 17 16:14 start.elf
-rwxr-xr-x 1 root root 2216529 Mar 9 10:19 System.map
-rwxr-xr-x 1 root root 2216529 Mar 8 03:57 System.map-4.14.24+
drwxr-xr-x 2 root root 2048 Mar 14 2016 System Volume Information

Ok, most files are from Mar 8 (that's the date of kernel 4.14.24 has been built), other files are from March 17 (that files came from xbian-package-firmware). So, everything seems to be ok.

So the question is, where does the wrong /proc/cpuinfo came from.

We could make a dirty hack in /usr/local/sbin/xbian-arch

please change

platform=unknown
revision=unknown

to

platform=RPI
revision=rpi3

and check output of

xbian-arch and xbian-arch revision
should report RPI resp rpi3

If this output is ok, please reinstall kernel again and see what happens

(20th Mar, 2018 08:52 AM)Nachteule Wrote: [ -> ]Ok, most files are from Mar 8 (that's the date of kernel 4.14.24 has been built), other files are from March 17 (that files came from xbian-package-firmware). So, everything seems to be ok.

So the question is, where does the wrong /proc/cpuinfo came from.

We could make a dirty hack in /usr/local/sbin/xbian-arch

please change

platform=unknown
revision=unknown

to

platform=RPI
revision=rpi3

and check output of

xbian-arch and xbian-arch revision
should report RPI resp rpi3

If this output is ok, please reinstall kernel again and see what happens

Your little hack seems to work!
This is the output (after editing the script):

xbian@xbian ~ $ sudo apt-get install --reinstall linux-image-bcm2836=4.14.27+-1521326778
Reading package lists... Done
Building dependency tree
Reading state information... Done
0 upgraded, 0 newly installed, 1 reinstalled, 0 to remove and 0 not upgraded.
Need to get 0 B/17.8 MB of archives.
After this operation, 0 B of additional disk space will be used.
Create a snapshot of '/run/btrfs-snap/root/@' in '/run/btrfs-snap/root/@btrfs-auto-snap_apt-run-2018-03-20-0000'
Delete subvolume (no-commit): '/run/btrfs-snap/root/@last_good_known'
Create a snapshot of '/run/btrfs-snap/root/@btrfs-auto-snap_apt-run-2018-03-20-0000' in '/run/btrfs-snap/root/@last_good_known'
Delete subvolume (no-commit): '/run/btrfs-snap/root/@btrfs-auto-snap_apt-run-2018-03-18-1947'
@btrfs-auto-snap_apt-run-2018-03-20-0000, 1 created snapshots, 1 destroyed snapshots, 0 warnings.
(Reading database ... 38304 files and directories currently installed.)
Preparing to unpack .../linux-image-bcm2836_4.14.27+-1521326778_armhf.deb ...
Unpacking linux-image-bcm2836 (4.14.27+-1521326778) over (4.14.27+-1521326778) ...
Setting up linux-image-bcm2836 (4.14.27+-1521326778) ...
Processing triggers for xbian-package-initramfs-tools (20180317-0) ...
grep: /var/spool/cron/atjobs/a002a50182ef84: No such file or directory
xbian@xbian ~ $

Any other things that I need to do after rebooting?

(20th Mar, 2018 09:13 AM)Roy Terhaar Wrote: [ -> ]Any other things that I need to do after rebooting?

Yes
You can revert changes in file update-initramfs ...
... and after reverting changes in xbian-arch, you can check output of xbian-arch and xbian-arch revision again