Rock64 no longer boots after dist-upgrade - Printable Version +- PINE64 (https://forum.pine64.org) +-- Forum: ROCK64 (https://forum.pine64.org/forumdisplay.php?fid=85) +--- Forum: Linux on Rock64 (https://forum.pine64.org/forumdisplay.php?fid=88) +--- Thread: Rock64 no longer boots after dist-upgrade (/showthread.php?tid=6180) |
Rock64 no longer boots after dist-upgrade - KernelPanic - 06-16-2018 After upgrading to the latest version of ubuntu from Ayufan Rock64 no longer boots. I had a workaround by selection "previous kernel", but now I tried installing the latest kernel and previous kernel also no longer works. Can anyone help me in the direction to use a different kernel from uboot? Could I just hook up a usb and tell it to boot a kernel I've downloaded to that? Code: Resetting CPU ... RE: Rock64 no longer boots after dist-upgrade - pfeerick - 06-16-2018 (06-16-2018, 03:16 AM)KernelPanic Wrote: After upgrading to the latest version of ubuntu from Ayufan Rock64 no longer boots. Any idea what version it updated to? So we can backtrack and see what's going on. What has just happened is you lost your previous kernel, as previous kernel is now the faulty one, due to the second update. To get around it, yes, you should be able to copy another kernel / initrd image on the fat filesystem on the SD card, and edit the [/boot/]efi/extlinux/extlinux.conf file to point to the new kernel/initrd. I don't see why you can't add it as a third option if you wish the leave the other entries alone. If you RE: Rock64 no longer boots after dist-upgrade - evilbunny - 06-16-2018 (06-16-2018, 03:16 AM)KernelPanic Wrote: After upgrading to the latest version of ubuntu from Ayufan Rock64 no longer boots. Do you have a spare sdcard, you could flash that with a known working image and copy the files in /boot over the top of the bad ones... RE: Rock64 no longer boots after dist-upgrade - KernelPanic - 06-16-2018 First of all thanks for trying to help! @pfeerick Problems began when updating to 0.6.53. After reboot it would hang on "Starting kernel". I managed to get around this by selecting previous kernel. Then I stupidly tried installing the kernel from 0.6.44: jenkins-linux-build-rock-64-239 instead of first installing the one I knew worked. And broke my previous kernel as well. So now I'm stuck without a working kernel and I can't figure out how to acces to emmc to edit it conf file and upload the new kernel. I'm a noob when it comes to uboot, but here's me trying to list the contents of the mmc: (trying 1 instead of 0 also doesn't work) => mmc dev 0 switch to partitions #0, OK mmc0(part 0) is current device => ls mmc 0 Failed to mount ext2 filesystem... ** Unrecognized filesystem type ** => @evilbunny I also made some attempts booting a spare sdcard with an image I think should be working, but I think for some reason it will still boot the non working kernel from the emmc. Here's what I do: - Turn off Rock64 - Insert sdcard - Attach jumper cables to the 2 pins closest to the recovery button (just like I did when installing to emmc) - Boot Rock64 - Break at the boot timer - Remove jumper cables - type boot - Stuck at same kernel error When I remove the emmc another weird thing is going on, it's like its trying to do a network boot.. I'm going to reflash the sdcard just to make sure I didn't mess that up. In the meantime any more help is appreciated! RE: Rock64 no longer boots after dist-upgrade - evilbunny - 06-16-2018 (06-16-2018, 04:23 AM)KernelPanic Wrote: When I remove the emmc another weird thing is going on, it's like its trying to do a network boot.. I'm going to reflash the sdcard just to make sure I didn't mess that up. In the meantime any more help is appreciated! The only way the r64 boots from the network is if you flash SPI with u-boot, I think there are some pins you can short to disable it. RE: Rock64 no longer boots after dist-upgrade - KernelPanic - 06-16-2018 I think the image was just crap, I did a format and started from scratch and now it's booting. So now I have a working image. Before I do another stupid thing, could you validate if I know have to do the following? First I mount the root of emmc to newly created folder sudo mount /dev/mmcblk0p7 /mnt/bootmmc Seems to be correct, this is the contents of emmc boot: Code: rock64@rock64:/mnt/bootmmc/boot$ ls -l Contents of the sdcard boot: Code: rock64@rock64:/boot$ ls -l So now I just copy the whole contents of sdcard boot to emmc boot? sudo cp -rp /boot/ /mnt/bootmmc/boot/ Thanks again! RE: Rock64 no longer boots after dist-upgrade - evilbunny - 06-16-2018 (06-16-2018, 05:22 AM)KernelPanic Wrote: So now I just copy the whole contents of sdcard boot to emmc boot? The 239 files look promising... https://github.com/ayufan-rock64/linux-build/releases/0.6.44 Also you need to mount partition 6 to /boot/efi otherwise you will miss copying those files. RE: Rock64 no longer boots after dist-upgrade - KernelPanic - 06-16-2018 You are right, forgot the efi parition Something weird seems to be going on with the one that's mounted by default (or I just don't understand Code: rock64@rock64:/mnt/efimmc$ df -h The following two especially: Code: /dev/mmcblk1p7 15G 1.6G 13G 12% / mmcblk1 = sdcard mmcblk0 = emmc So am I right in saying it mounts the wrong efi by default? I didn't notice at first and mounted what I thought was the emmc to my own mount point (/mnt/efimmc) but ended up copying the same files back and forth After still not being able to boot I noticed, rebooted, remounted the sdcard efi to /boot/efi and mmc to /mnt/efimmc copied and BAM we're back in action! Thanks a lot for pointing me in the right direction! Could it be that copying the /boot/ and /boot/efi messed something up with my build? Everything is working as before except for openvpn which can't initiate a connection anymore ERROR: Cannot open TUN/TAP dev /dev/net/tun: No such file or directory (errno=2) I checked, and indeed there is no /dev/net folder RE: Rock64 no longer boots after dist-upgrade - evilbunny - 06-16-2018 (06-16-2018, 06:12 AM)KernelPanic Wrote: mmcblk1 = sdcard That happens because images use the same partition titles, you could try changing the fstab to which ever device you want mounted. Quote:Everything is working as before except for openvpn which can't initiate a connection anymore try apt-get --reinstall install openvpn If that doesn't work, it may be your openvpn config loading from the wrong partition RE: Rock64 no longer boots after dist-upgrade - KernelPanic - 06-16-2018 (06-16-2018, 07:10 AM)evilbunny Wrote:(06-16-2018, 06:12 AM)KernelPanic Wrote: mmcblk1 = sdcard I think I figured it out after some more digging. I'll post what I did here in case it might help someone else. I think because I copied a kernel from the SDcard that I wasn't using before on emmc I am still missing some files I would've gotten with a normal install of the kernel. (In this case the modules in /lib/moduiles). Code: sudo modprobe tun So I purged all the kernels and reinstalled the 213 kernel. After a reboot modprobe now doesn't return any more errors and OpenVPN works again. Thanks! |