(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.
When reboot, you will see all debug information, then Rock64 hangs forever
Make sure if you upgrade you get the 0.6.44 kernel, others are problematic...
Check your package sources also as it was recently tweaked (but may not have been causing issues unless you're getting 'not found' type messages)... it looks like rock64 specific packages are coming from http://ppa.launchpad.net/ayufan/rock64-ppa/ubuntu", which it just being distro being different. i.e for debian stretch "deb http://ppa.launchpad.net/ayufan/rock64-ppa/ubuntu xenial main" and for sid it would be "deb http://ppa.launchpad.net/ayufan/rock64-ppa/ubuntu bionic main".
https://github.com/ayufan-rock64/linux-build/commit/c33c7e8c96db2a3905b0d7e6f0f6662e185baa05
I want to make things more clear.
I downloaded the Debian image from official URL:
http://files.pine64.org/os/ROCK64/debian...m64.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
(05-31-2018, 07:43 PM)jzhang18 Wrote: I want to make things more clear.
I downloaded the Debian image from official URL:
http://files.pine64.org/os/ROCK64/debian...m64.img.xz
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.
06-01-2018, 08:16 AM
(This post was last modified: 06-01-2018, 09:08 AM by jzhang18.)
(05-31-2018, 11:24 PM)pfeerick Wrote: (05-31-2018, 07:43 PM)jzhang18 Wrote: I want to make things more clear.
I downloaded the Debian image from official URL:
http://files.pine64.org/os/ROCK64/debian...m64.img.xz
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.
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.
06-02-2018, 09:25 AM
(This post was last modified: 06-02-2018, 09:31 AM by jzhang18.)
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
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.
(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... 
06-03-2018, 09:17 AM
(This post was last modified: 06-03-2018, 09:26 AM by jzhang18.)
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...m64.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")
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
~# cd /myDEBDownloadFolder
/myDEBDownloadFolder# wget https://github.com/ayufan-rock64/linux-build/releases/download/0.6.44/linux-firmware-image-4.4.126-rockchip-ayufan-239_0.6.44_arm64.deb
/myDEBDownloadFolder# wget https://github.com/ayufan-rock64/linux-build/releases/download/0.6.44/linux-headers-4.4.126-rockchip-ayufan-239_0.6.44_arm64.deb
/myDEBDownloadFolder# wget https://github.com/ayufan-rock64/linux-build/releases/download/0.6.44/linux-image-4.4.126-rockchip-ayufan-239_0.6.44_arm64.deb
/myDEBDownloadFolder# wget https://github.com/ayufan-rock64/linux-build/releases/download/0.6.44/u-boot-rock64-0.6.44_all.deb
/myDEBDownloadFolder# cd ../
/# dpkg -R --install ./myDEBDownloadFolder
Selecting previously unselected package linux-firmware-image-4.4.126-rockchip-ayufan-239.
(Reading database ... 85740 files and directories currently installed.)
Preparing to unpack .../linux-firmware-image-4.4.126-rockchip-ayufan-239_0.6.44_arm64.deb ...
Unpacking linux-firmware-image-4.4.126-rockchip-ayufan-239 (0.6.44) ...
Selecting previously unselected package linux-headers-4.4.126-rockchip-ayufan-239.
Preparing to unpack .../linux-headers-4.4.126-rockchip-ayufan-239_0.6.44_arm64.deb ...
Unpacking linux-headers-4.4.126-rockchip-ayufan-239 (0.6.44) ...
Selecting previously unselected package linux-image-4.4.126-rockchip-ayufan-239.
Preparing to unpack .../linux-image-4.4.126-rockchip-ayufan-239_0.6.44_arm64.deb ...
Unpacking linux-image-4.4.126-rockchip-ayufan-239 (0.6.44) ...
Selecting previously unselected package u-boot-rock64.
Preparing to unpack .../u-boot-rock64-0.6.44_all.deb ...
Unpacking u-boot-rock64 (0.6.44) ...
Setting up linux-firmware-image-4.4.126-rockchip-ayufan-239 (0.6.44) ...
Setting up linux-headers-4.4.126-rockchip-ayufan-239 (0.6.44) ...
Setting up linux-image-4.4.126-rockchip-ayufan-239 (0.6.44) ...
update-initramfs: Generating /boot/initrd.img-4.4.126-rockchip-ayufan-239
Warning: root device does not exist
Using DTB: rk3328-rock64.dtb
Installing /usr/lib/linux-image-4.4.126-rockchip-ayufan-239/rockchip/rk3328-rock64.dtb into /boot/dtbs/4.4.126-rockchip-ayufan-239/rk3328-rock64.dtb
Installing new rk3328-rock64.dtb.
Installing /usr/lib/linux-image-4.4.126-rockchip-ayufan-239/rockchip/rk3328-rock64.dtb into /boot/dtbs/4.4.126-rockchip-ayufan-239/rk3328-rock64.dtb
Taking backup of rk3328-rock64.dtb.
Installing new rk3328-rock64.dtb.
flash-kernel: deferring update (trigger activated)
Using DTB: rk3328-rock64.dtb
Installing /usr/lib/linux-image-4.4.126-rockchip-ayufan-239/rockchip/rk3328-rock64.dtb into /boot/dtbs/4.4.126-rockchip-ayufan-239/rk3328-rock64.dtb
Taking backup of rk3328-rock64.dtb.
Installing new rk3328-rock64.dtb.
Installing /usr/lib/linux-image-4.4.126-rockchip-ayufan-239/rockchip/rk3328-rock64.dtb into /boot/dtbs/4.4.126-rockchip-ayufan-239/rk3328-rock64.dtb
Taking backup of rk3328-rock64.dtb.
Installing new rk3328-rock64.dtb.
flash-kernel: deferring update (trigger activated)
dpkg: dependency problems prevent configuration of u-boot-rock64:
u-boot-rock64 depends on debsums; however:
Package debsums is not installed.
dpkg: error processing package u-boot-rock64 (--install):
dependency problems - leaving unconfigured
Processing triggers for flash-kernel (3.79) ...
Using DTB: rk3328-rock64.dtb
Installing /usr/lib/linux-image-4.4.126-rockchip-ayufan-239/rockchip/rk3328-rock64.dtb into /boot/dtbs/4.4.126-rockchip-ayufan-239/rk3328-rock64.dtb
Taking backup of rk3328-rock64.dtb.
Installing new rk3328-rock64.dtb.
flash-kernel: installing version 4.4.126-rockchip-ayufan-239
Taking backup of Image.
Installing new Image.
Taking backup of initrd.img.
Installing new initrd.img.
Taking backup of dtb.
Installing new dtb.
Errors were encountered while processing:
u-boot-rock64
----------------------
~# uname -a
Linux rock64 4.4.77-rockchip-ayufan-136 #1 SMP Thu Oct 12 09:14:48 UTC 2017 aarch64 GNU/Linux
# reboot
....
Debian GNU/Linux 9 rock64 ttyS2
rock64 login: root
Password:
Last login: Mon Jun 4 05:18:31 UTC 2018 on ttyFIQ0
_ __ _ _
_ __ ___ ___| | __/ /_ | || |
| '__/ _ \ / __| |/ / '_ \| || |_
| | | (_) | (__| <| (_) |__ _|
|_| \___/ \___|_|\_\\___/ |_|
Linux rock64 4.4.126-rockchip-ayufan-239 #1 SMP Sun May 27 18:38:24 UTC 2018 aarch64
The programs included with the Debian GNU/Linux system are free software;
the exact distribution terms for each program are described in the
individual files in /usr/share/doc/*/copyright.
Debian GNU/Linux comes with ABSOLUTELY NO WARRANTY, to the extent
permitted by applicable law.
~# uname -a
Linux rock64 4.4.126-rockchip-ayufan-239 #1 SMP Sun May 27 18:38:24 UTC 2018 aarch64 GNU/Linux
06-04-2018, 02:38 PM
(This post was last modified: 06-05-2018, 10:15 AM by jzhang18.)
(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.
06-05-2018, 10:14 AM
(This post was last modified: 06-05-2018, 10:19 AM by jzhang18.)
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.
|
