Linux Images (ROCK64) - 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: Linux Images (ROCK64) (/showthread.php?tid=4849) |
RE: Linux Images (ROCK64) - jzhang18 - 05-31-2018 (05-29-2018, 05:27 PM)pfeerick Wrote:(05-29-2018, 04:42 PM)evilbunny Wrote:(05-29-2018, 01:20 PM)jzhang18 Wrote: 3. sudo apt update && sudo apt upgrade. I want to make things more clear. I downloaded the Debian image from official URL: http://files.pine64.org/os/ROCK64/debian/stretch-mate-rock64-0.5.15-136-20171222-arm64.img.xz After installation: I checked kernel files: linux-image-4.4.77-rockchip-ayufan-136 linux-firmware-image-4.4.77-rockchip-ayufan-136 linux-headers-4.4.77-rockchip-ayufan-136 If I do a upgrade These new packages will be installed linux-headers-4.4.126-rockchip-ayufan-239 linux-image-4.4.126-rockchip-ayufan-239 u-boot-rock64 Then, my Rock64 becomes dead after install them RE: Linux Images (ROCK64) - pfeerick - 05-31-2018 (05-31-2018, 07:43 PM)jzhang18 Wrote: I want to make things more clear. Thanks for that, I'll try the image and see if I can reproduce (which I suspect I will be able to as there have been other reports of kernel updates breaking). If you want the newer kernel, give 0.6.44 a try, as it has that kernel as standard and is better than updating an old image if you have the choice. RE: Linux Images (ROCK64) - jzhang18 - 06-01-2018 (05-31-2018, 11:24 PM)pfeerick Wrote:(05-31-2018, 07:43 PM)jzhang18 Wrote: I want to make things more clear. Definitely want to give a shot. Just want to confirm, I need to download these files: linux-firmware-image-4.4.126-rockchip-ayufan-239_0.6.44_arm64.deb linux-headers-4.4.126-rockchip-ayufan-239_0.6.44_arm64.deb linux-image-4.4.126-rockchip-ayufan-239_0.6.44_arm64.deb u-boot-rock64-0.6.44_all.deb Then Code: sudo dpkg -R --install /myDEBDownloadFolder To install all above 4 files together, or there are some sequence, I need to install which one first, which one later? Appreciated for further confirmation. RE: Linux Images (ROCK64) - jzhang18 - 06-02-2018 I downloaded these 4 files linux-firmware-image-4.4.126-rockchip-ayufan-239_0.6.44_arm64.deb linux-headers-4.4.126-rockchip-ayufan-239_0.6.44_arm64.deb linux-image-4.4.126-rockchip-ayufan-239_0.6.44_arm64.deb u-boot-rock64-0.6.44_all.deb Installed as following steps 1. sudo dpkg-reconfigure locales --solved locale not set warning 2.sudo dpkg-reconfigure tzdata --set the correct time zone 3. sudo dpkg -i /myDownloadPath/u-boot-rock64-0.6.44_all.deb -- there is error, saying dependency "debsums" is missing. -- then I use "sudo apt install debsums", some further error on dependency, but follow the instructions on the screen, it is easy to fix 4. sudo dpkg -i /myDownloadPath/linux-headers-4.4.126-rockchip-ayufan-239_0.6.44_arm64.deb 5. sudo dpkg -i /myDownloadPath/linux-firmware-image-4.4.126-rockchip-ayufan-239_0.6.44_arm64.deb 6. sudo dpkg -i /myDownloadPath/linux-image-4.4.126-rockchip-ayufan-239_0.6.44_arm64.deb -- warning: root device not found -- that scares me, I thought it will be dead again 7. sudo reboot -- keep my fingers crossed. it came back. it is still alive!!! 8. sudo apt update 9. sudo apt upgrade -- I saw the kernel related image files did not show up in the upgrade list. that is good sign!!! 10. sudo reboot -- it looks good 11. sudo apt autoremove -- remove all obsoleted packages reported. 12. sudo apt upgrade -- showing everything is up to date, all set!!! I still do not understand the warning -- "root device not found". it might be just a wrong or fake message RE: Linux Images (ROCK64) - t4_4t - 06-02-2018 There are several similar reports. So I tried it twice under the conditions you presented(#111: 05-31-2018, 07:43 PM). However, it did not happen that it could not be activated due to a crash or the like. The environment I tried is ROCK64(RAM: 1GB). You'd better refer to the following "Can not boot new 0.6.41, Brendon" https://forum.pine64.org/showthread.php?tid=6087 In this case, there is a problem with a combination of a specific card and a specific ROCK64(RAM: 4GB) I have another combination environment that causes similar symptoms. In that environment, it is the same symptom as "Brendon", confirming that the card can not be read with the 0.6.4x kernel. Even if I tried with the combination above, it is obvious that it can not boot. Therefore, I have not confirmed this combination. In your report "dead" / "hang" the detailed symptoms are unknown It would be better to attach an error report etc. to symptoms and write in more detail In addition, there are some cases mentioned above, so I think that reporting "model of Card / ROCK64" is also important. RE: Linux Images (ROCK64) - pfeerick - 06-02-2018 (06-02-2018, 09:25 AM)jzhang18 Wrote: I still do not understand the warning -- "root device not found". it might be just a wrong or fake message I'm not sure of the reason for it either. I got it the other day in relation to flash-image, but it seemed to do whatever it needed to do without any issue anyway. Just curious, was there a particular reason you couldn't just start from a clean image? Then there would have been no need to go through the possible pain of installing those packages... Oh, wait, the newer stretch don't have mate, and install_desktop won't work... never mind me... RE: Linux Images (ROCK64) - jzhang18 - 06-03-2018 Quote:In addition, there are some cases mentioned above, so I think that reporting "model of Card / ROCK64" is also important. I use Rock64 4GB model, I tried Sandisk Ultra 64GB, Sandisk Ultra 32GB, SP Elite 64GB. Burning software: Etcher, http://files.pine64.org/os/ROCK64/debian/stretch-mate-rock64-0.5.15-136-20171222-arm64.img.xz My burning and first boot processes are always good,no crash, reboot many times, always good. ONLY PROBLEM -- do not run online "sudo apt upgrade" , otherwise, 100% dead when I reboot afterward. Now I am happy with my manual steps to upgrade kernel first, then "sudo apt upgrade" to keep the rest software up to date. (Even though it seems not perfect with "root device not found" warning, I also notice, the red led is always "on" now next to the white led, when I burn and use original image, red led will be turned off after booting is finished. with kernel updated to new one. the red led becomes always "on") RE: Linux Images (ROCK64) - t4_4t - 06-04-2018 I tried it three times with "RAM 4GB" Version I do not have cards that you presented, Therefore I used a card (Silicon Power: 8 GB) as an alternative. However, the problem did not occur, the result is as attached. Certainly u-boot has failed to install, and u-boot has not been updated. (Since it was not updated even when I tried it before, This is a problem unique to the "u-boot-xxx.deb" package) However, there seems to be no impact on boot due to that (in my environment) Code: ~# mkdir /myDEBDownloadFolder RE: Linux Images (ROCK64) - jzhang18 - 06-04-2018 (06-04-2018, 01:25 AM)t4_4t Wrote: However, the problem did not occur, the result is as attached. I think you misunderstood the issue I encountered. You just repeated the correct way which I did for patching the image. If you want to repeat the issue: Just burn a fresh image from: http://files.pine64.org/os/ROCK64/debian...m64.img.xz Then, $ sudo apt update && sudo apt upgrade $ sudo reboot You will see what happened. RE: Linux Images (ROCK64) - jzhang18 - 06-05-2018 Actually, The local boot process never finished after upgraded to new Kernel. Hanging at some point, that is why the red led is still "on". Connect to the monitor, I just saw a cursor flashing at the last booting message line: "..... at speed of 1Gbps/ full duplex ... " Mate desktop never comes back to screen. Because I use headless mode, I installed xrdp. Mate desktop is just fine through xrdp. SSH works also. I think that is due to "Warning: root device does not exist", that is not a fake message, it is real. I have no idea on how to fix "Warning: root device does not exist" during kernel update. search on internet, there are tons of similar posts. it seems a very common issue in Linux world. |