VU+ Solo 4k - Bootloader to Linux init problem, after upgrade.

boneco69

Vu+ Newbie
Hello team!

After install new image the box stuck at logo. Connecting to RS232 I have the kernel exception because no root image found. I could stop the boot (CTRL+c) but do not know to fix because there is no information to resolve the problem.
Attached is the minicom session saved in txt.

I could stop the reboot after upgrade removing the reboot.update file from USB. In there i tryed to mount with sucess the mmcblk0p4 (root) filesystem, so the problem must be or in the image itself or the bootloader not sending the correct address to kernel, or it misses the init file. I've tryed with other images and the problem stays the same.

[ 2.192253] Waiting for root device /dev/mmcblk0p4...
[ 2.439384] mmc1: BKOPS_EN bit is not set
[ 2.449619] mmc1: new high speed MMC card at address 0001
[ 2.455419] mmcblk0: mmc1:0001 4FPD3R 3.64 GiB
[ 2.460066] mmcblk0boot0: mmc1:0001 4FPD3R partition 1 4.00 MiB
[ 2.466097] mmcblk0boot1: mmc1:0001 4FPD3R partition 2 4.00 MiB
[ 2.475297] mmcblk0: p1 p2 p3 p4
[ 2.480139] mmcblk0boot1: unknown partition table
[ 2.485714] mmcblk0boot0: unknown partition table
[ 2.526274] EXT3-fs (mmcblk0p4): error: couldn't mount because of unsupported optional features (40)
[ 2.535781] EXT4-fs (mmcblk0p4): Mount option "data=journal" incompatible with ext2
[ 2.543773] EXT4-fs: Warning: mounting with data=journal disables delayed allocation and O_DIRECT support!
[ 2.559324] EXT4-fs (mmcblk0p4): mounted filesystem with journalled data mode. Opts: data=journal
[ 2.568244] VFS: Mounted root (ext4 filesystem) on device 179:4.
[ 2.574665] devtmpfs: error mounting -2
[ 2.578794] Freeing unused kernel memory: 248K (c0798000 - c07d6000)
[ 2.589107] Kernel panic - not syncing: No working init found. Try passing init= option to kernel. See Linux Documentation/init.txt for guidance.
[ 2.602253] CPU: 1 PID: 1 Comm: swapper/0 Not tainted 3.14.28-1.8 #1
[ 2.608643] [<c00164bc>] (unwind_backtrace) from [<c0012284>] (show_stack+0x10/0x14)
[ 2.616404] [<c0012284>] (show_stack) from [<c0588eb4>] (dump_stack+0x80/0x90)
[ 2.623637] [<c0588eb4>] (dump_stack) from [<c05882cc>] (panic+0x9c/0x1f0)
[ 2.630522] [<c05882cc>] (panic) from [<c058590c>] (cpu_die+0x0/0x80)
[ 2.636971] [<c058590c>] (cpu_die) from [<00000000>] ( (null))
[ 2.642905] CPU0: stopping
[ 2.645618] CPU: 0 PID: 0 Comm: swapper/0 Not tainted 3.14.28-1.8 #1
[ 2.651987] [<c00164bc>] (unwind_backtrace) from [<c0012284>] (show_stack+0x10/0x14)
[ 2.659742] [<c0012284>] (show_stack) from [<c0588eb4>] (dump_stack+0x80/0x90)
[ 2.666974] [<c0588eb4>] (dump_stack) from [<c0015034>] (handle_IPI+0x14c/0x16c)
[ 2.674380] [<c0015034>] (handle_IPI) from [<c00085d0>] (gic_handle_irq+0x58/0x5c)
[ 2.681959] [<c00085d0>] (gic_handle_irq) from [<c0012e00>] (__irq_svc+0x40/0x50)
[ 2.689448] Exception stack(0xc07d9f60 to 0xc07d9fa8)
[ 2.694507] 9f60: ffffffed 0cfee000 c07e141c 00000000 c07d8030 c07e03f8 c07e0474 c059002c
[ 2.702694] 9f80: c081bfa5 c081bfa5 c07d8000 00000000 00000000 c07d9fa8 c000fc68 c000fc60
[ 2.710879] 9fa0: 60000113 ffffffff
[ 2.714375] [<c0012e00>] (__irq_svc) from [<c000fc60>] (arch_cpu_idle+0x2c/0x38)
[ 2.721788] [<c000fc60>] (arch_cpu_idle) from [<c006133c>] (cpu_startup_entry+0x100/0x144)
[ 2.730073] [<c006133c>] (cpu_startup_entry) from [<c0798b60>] (start_kernel+0x3a0/0x3ac)


If there is someone that had the same problem before and solved it i appreciate the knowledge share. This is an original VU+ box.
Best regards.
 

Attachments

  • bootproblem.txt
    170.5 KB · Views: 71

boneco69

Vu+ Newbie
Ok. Resolved. For the people that might need help:

I remembered to verify if the install usb images clean-up the root filesystem, so i create an boot usb with an empty rootfs.tar.bz2.
How to make the USB disk...

1 - unzip the file to USB
2 - cd to file location in the USB...
cd (....)/vuplus/solo4k/
rename the original root_fs file ...
mv rootfs.tar.bz2 rootfs.tar.bz2.dis
and create an empty file so the bootloader boots to USB Linux installer...
touch rootfs.tar.bz2
removed the reboot.update file so Linux wont reboot at the end of the flash procedure.
rm reboot.update
Plugged the USB in the receiver and let it "update" (pressing front button).

It booted... and, now it is supposed to the flash system to be empty... afterall the source is invalid/empty...
Waited until the flash update process is completed


I mounted the filesystem and voilá... leftovers of the file in /etc directory.
One of them is an old script that i made to "recover" the password if it is changed... (copied from oldpasswd to passwd).
NOTE - those files are chattr +i ... so that was the reason for the unpack script to fail to empty the rootfs... be warned of this caveat.

# mount /dev/mmcblk0p4 /mnt/hd/
[ 41.314766] EXT4-fs (mmcblk0p4): couldn't mount as ext3 due to feature incompatibilities
[ 41.323516] EXT4-fs (mmcblk0p4): couldn't mount as ext2 due to feature incompatibilities
[ 41.341087] EXT4-fs (mmcblk0p4): mounted filesystem with ordered data mode. Opts: (null)
#
# ls /mnt/hd/
etc
# ls /mnt/hd/
.cache/ .local/ .python-history etc/
# ls /mnt/hd/
.cache/ .local/ .python-history etc/
# cd /mnt/hd/
# ls
etc
# ls -lat
drwx------ 3 root root 4096 Jun 26 2017 .local
drwxrwxr-x 6 root root 120 Feb 8 2017 ..
-rw------- 1 root root 0 Jan 1 1970 .python-history
drwxr-xr-x 3 root root 4096 Jan 1 00:00 .cache
drwxr-xr-x 5 root root 4096 Jan 1 00:00 .
drwxr-xr-x 3 root root 4096 Jan 1 00:00 etc
# cd etc
# ls
init.d oldpasswd passwd shadow
# ls -la
drwxr-xr-x 3 root root 4096 Jan 1 00:00 .
drwxr-xr-x 5 root root 4096 Jan 1 00:00 ..
drwxr-xr-x 2 root root 4096 Jan 1 00:00 init.d
-rw-r--r-- 1 root root 1037 May 22 2018 oldpasswd
-rw-r--r-- 1 root root 1007 May 23 2018 passwd
-rw-r--r-- 1 root root 876 May 23 2018 shadow
# cd init.d/
# ls
lockpasswd
# ls -la
drwxr-xr-x 2 root root 4096 Jan 1 00:00 .
drwxr-xr-x 3 root root 4096 Jan 1 00:00 ..
-rwxr-xr-x 1 root root 50 May 22 2018 lockpasswd
# cat lockpasswd
#!/bin/sh
cat /etc/oldpasswd > /etc/passwd
exit 0
# cd /


So i umount and recreate the filesystem...

# umount /mnt/hd/
# mkfs.ext4 /dev/mmcblk0p4
mke2fs 1.41.14 (22-Dec-2010)
Filesystem label=
OS type: Linux
Block size=4096 (log=2)
Fragment size=4096 (log=2)
Stride=0 blocks, Stripe width=0 blocks
236176 inodes, 943616 blocks
47180 blocks (5.00%) reserved for the super user
First data block=0
Maximum filesystem blocks=968884224
29 block groups
32768 blocks per group, 32768 fragments per group
8144 inodes per group
Superblock backups stored on blocks:
32768, 98304, 163840, 229376, 294912, 819200, 884736

Writing inode tables: done
Creating journal (16384 blocks): done
Writing superblocks and filesystem accounting information: done

This filesystem will be automatically checked every 39 mounts or
180 days, whichever comes first. Use tune2fs -c or -i to override.


Rebooted the box to install with the original unziped files ... and voila... box is recovered.

[ 2.472935] mmc1: new high speed MMC card at address 0001
[ 2.478647] mmcblk0: mmc1:0001 4FPD3R 3.64 GiB
[ 2.483306] mmcblk0boot0: mmc1:0001 4FPD3R partition 1 4.00 MiB
[ 2.489344] mmcblk0boot1: mmc1:0001 4FPD3R partition 2 4.00 MiB
[ 2.498524] mmcblk0: p1 p2 p3 p4
[ 2.503019] mmcblk0boot1: unknown partition table
[ 2.508452] mmcblk0boot0: unknown partition table
[ 2.569548] EXT4-fs: Warning: mounting with data=journal disables delayed allocation and O_DIRECT support!
[ 2.585275] EXT4-fs (mmcblk0p4): mounted filesystem with journalled data mode. Opts: data=journal
[ 2.594200] VFS: Mounted root (ext4 filesystem) on device 179:4.
[ 2.600662] devtmpfs: mounted
[ 2.603932] Freeing unused kernel memory: 264K (c0885000 - c08c7000)
INIT: version 2.88 booting
Starting fake hwclock: loading system time.
Wed May 30 10:03:46 UTC 2018
grep: /sys/devices/platform/Fixed: No such file or directory
grep: MDIO: No such file or directory
grep: bus.0/modalias: No such file or directory
[ 3.499077] usb 5-1: reset high-speed USB device number 2 using ehci-brcm
[ 3.658670] ieee80211 phy0: rt2x00_set_rt: Info - RT chipset 5392, rev 0223 detected
[ 3.694540] ieee80211 phy0: rt2x00_set_rf: Info - RF chipset 5372 detected
[ 3.702653] ieee80211 phy0: Selected rate control algorithm 'minstrel_ht'
[ 3.729235] usbcore: registered new interface driver rt2800usb
[ 3.811009] EXT4-fs (mmcblk0p4): re-mounted. Opts: nodelalloc,data=journal
[ 4.848486] random: dd urandom read with 75 bits of entropy available
ALSA: Restoring mixer settings...
/usr/sbin/alsactl: load_state:1735: No soundcards found...
net.ipv4.conf.default.rp_filter = 1
net.ipv4.conf.all.rp_filter = 1
vm.dirty_writeback_centisecs = 300
vm.dirty_background_ratio = 1
vm.min_free_kbytes = 8192
vm.dirty_ratio = 60
vm.swappiness = 30
Starting vuplus-platform-util[ 5.591009] procmk_init
[ 5.596955] bcm_event: module license 'Proprietary' taints kernel.
[ 5.603186] Disabling lock debugging due to kernel taint
[ 8.152640] random: nonblocking pool is initialized
[ 9.799724] DVB: registering new adapter (_vuplus_solo4k_)
[ 10.289056] bcm7376: hotplug_callback():
Hotplug - status.connected 1:0:0
[ 10.296127] bcm7376: hotplug_callback():
Hotplug - connecting HDMI to display 0xe
[ 10.559049] brcm_demux_init: $Id: bcm_demux.c,v 0.7 $
[ 10.559102] bcm7376: hotplug_callback():



Best regards to all and i hope this could save many headaches in the future for similar problems.
 
Last edited:

filman

Vu+ Newbie
Hi I have this weird problem with my receiver.
The Vu+ 4K Solo stopped working last week. The last image it had was OpenPli 4. I have tried to install new via USB stick. Tried with 3 nothing happens. Than I have detached hdd nothing, attached again started to work, but could not install the image.
Today, I have detached hdd, I have put USB stick and after 10 min the old image appeared and everything was working.
I wanted to use this to install new image from 4 to 7 or 8. But he does recognize USB stick and continued to the old image. I have make a file also mkpart.update than it did recognize USB but now on the display there was no more Vu+ appearing at all. It got back to just flashing on the left side upfront. Now power off, even change the power supply from one place to other, nothing.
Just flashes and there is no signal on the TV at all.
Please help me, because I know I can't flash images via serial port.
Thank you very much
 

AlexWilMac

Moderator
With your post you made many mistakes".
1st mistake: your post is OT: why did you attach your issue to a completely different one? Please, create a thread with an appropriate subject, for the use of every users.
2nd mistake: this is the BH and was the OBH forum (now with its own specific forum), not the OpenPLI one: go to their forum, learn German if you want to be considered a bit and get answers and ask there.
3rd mistake: a messy post. Try to be simple.

From all this complicated post I can just suggest to:
1) avoid like the plague OpenPLI and download OpenBlackHole 5.1 from the new forum
https://openbh.net/
2) Try different USB sticks.
 

filman

Vu+ Newbie
Sorry AlexWillMac,

for the many mistakes I have done.
Just to be clear:
1) tried 3 different images together with OpenBlackHole even tried with the original one.
2) tried 4 USB sticks it's not my first time to install the image
3) main problem is that the receiver just flashes upfront left side and 2 times it returned with the old image, wanted to updated with 3 different nothing happned, now just the blue light flashes

Once again sorry for all the mess here, I was thinking this is English speaking forum here, because I don't know German at all.
 
Top