On 2/12/20 12:07 PM, Matwey V. Kornilov wrote: > 12.02.2020 20:58, ITwrx пишет: >> On 2/12/20 11:56 AM, Matwey V. Kornilov wrote: >>> 12.02.2020 18:37, ITwrx пишет: >>>> On 2/12/20 8:59 AM, ITwrx wrote: >>>>> On 2/12/20 1:49 AM, Matwey V. Kornilov wrote: >>>>>> Hi, >>>>>> >>>>>> It is very strange to hear that. I deployed this image to couple of >>>>>> Rock64-s week ago. >>>>>> So, could you please be more specific? What are you trying to do exactly? >>>>>> >>>>>> You are supposed to download >>>>>> openSUSE-Tumbleweed-ARM-JeOS-rock64.aarch64-2020.01.30-Build5.29.raw.xz >>>>>> uncompress it with `xz -d >>>>>> openSUSE-Tumbleweed-ARM-JeOS-rock64.aarch64-2020.01.30-Build5.29.raw.xz` >>>>>> and write .raw file to microsd card as the following `dd_rescue >>>>>> openSUSE-Tumbleweed-ARM-JeOS-rock64.aarch64-2020.01.30-Build5.29.raw >>>>>> /dev/your_sd_card_here`. >>>>> That's what i did, but i'll try it again. I didn't get any errors when >>>>> writing the image. This time, i'll wipe the sd card and create one fat >>>>> partition, just to be on the safe side. >>>>>> Do you have usb rs232 ttl converter to attach the Rock64 console? What >>>>>> does it say? >>>>> i did, but i don't remember. It didn't get very far. If it fails this >>>>> time, i'll copy and paste the output. >>>>> >>>>> Thanks >>>>> >>>>>> ср, 12 февр. 2020 г. в 10:17, Guillaume Gardet >>>>>> <[email protected]>: >>>>>>> Hi, >>>>>>> >>>>>>>> -----Original Message----- >>>>>>>> From: ITwrx <[email protected]> >>>>>>>> Sent: 12 February 2020 03:49 >>>>>>>> To: [email protected] >>>>>>>> Subject: [opensuse-arm] Rock64 >>>>>>>> >>>>>>>> Thorston/All, >>>>>>>> >>>>>>>> i just wanted to report that there are not Rock64 microOS images, only >>>>>>>> images for >>>>>>>> the older pine64. >>>>>>>> >>>>>>>> Also, the instructions on the Rock64 openSUSE wiki don't work (exactly >>>>>>>> as they >>>>>>>> are), using the below linked image file. I don't know what the >>>>>>>> corresponding >>>>>>>> "packages" file is for or how to use it, so it was not used in any >>>>>>>> way. The Rock64 >>>>>>> The "packages" file is just the list of installed packages in this >>>>>>> *.raw.xz image. >>>>>>> >>>>>>>> openSUSE wiki page didn't mention anything about it. Probably why the >>>>>>>> board >>>>>>>> won't boot... :) >>>>>>>> >>>>>>>> http://download.opensuse.org/repositories/devel:/ARM:/Factory:/Contrib:/Roc >>>>>>>> kchip/images/openSUSE-Tumbleweed-ARM-JeOS-rock64.aarch64-2020.01.30- >>>>>>>> Build5.29.raw.xz >>>>>>>> >>>>>>>> Any tips appreciated. >>>>>>> Added Matwey in Cc who may help. >>>>>>> >>>>>>> Cheers, >>>>>>> Guillaume >>>>>>> >>>>>>>> Thanks, >>>>>>>> >>>>>>>> ITwrx >>>>>>>> >>>>>>>> >>>>>>>> -- >>>>>>>> To unsubscribe, e-mail: [email protected] >>>>>>>> To contact the owner, e-mail: [email protected] >>>> Ok, i misspoke earlier. The first time i didn't extract, then run >>>> dd_rescue per your instructions. i ran "xzcat [image].raw.xz | dd bs=4M >>>> of=/dev/sdX iflag=fullblock oflag=direct; sync" (substituting relevant >>>> info) per the wiki. This time i did use your commands. I got the same >>>> result and output in the serial console as before. >>>> >>>>> U-Boot TPL 2020.01 (Jan 30 2020 - 10:43:44) >>>>> data training error >>>>> col error >>>>> data training error >>>>> LPDDR3, 800MHz >>>>> BW=16 Col=12 Bk=8 CS0 Row=16 CS=1 Die BW=8 Size=4096MB >>>> I don't know much about Arm, so i don't know what that output means. :) >>> It is very first stage of bootloader. Do you see anything else next? >> no. That's where it stops, unfortunately. I guess i could try the ALARM >> install process and see if it stops at the same point, in which case >> maybe it's an hardware issue. > For me, the output looks like. (My testing board is 2GB, but I > successfully use 4GB also) > > U-Boot TPL 2020.01 (Jan 30 2020 - 10:43:44) > LPDDR3, 800MHz > BW=32 Col=10 Bk=8 CS0 Row=15 CS1 Row=15 CS=2 Die BW=16 Size=2048MB > Trying to boot from BOOTROM > Returning to boot ROM... > > U-Boot SPL 2020.01 (Jan 30 2020 - 10:43:44 +0000) > Trying to boot from MMC1 > NOTICE: BL31: v2.1(debug): > NOTICE: BL31: Built : 22:19:57, Sep 4 2019 > ERROR: over or zero region, nr=4187432, max=10 > NOTICE: BL31:Rockchip release version: v1.2 > INFO: ARM GICv2 driver initialized > INFO: plat_rockchip_pmu_init: pd status 0xe > INFO: BL31: Initializing runtime services > WARNING: BL31: cortex_a53: CPU workaround for 819472 was missing! > WARNING: BL31: cortex_a53: CPU workaround for 824069 was missing! > WARNING: BL31: cortex_a53: CPU workaround for 827319 was missing! > WARNING: BL31: cortex_a53: CPU workaround for 855873 was missing! > INFO: BL31: Preparing for EL3 exit to normal world > INFO: Entry point address = 0x200000 > INFO: SPSR = 0x3c9 > > > Well, maybe something is still wrong with U-boot (It is known to be not > quite stable for Rock64 at the time of 2019.10 release). > > Could you try this section? > https://en.opensuse.org/HCL:Rock64#Using_proprietary_TPL_bootloader > > If the proprietary boot-loader works, then the issue should be reported > to u-boot maillist.
sure, i'll try it out. i wonder if the ALARM image is using the proprietary bootloader. https://archlinuxarm.org/platforms/armv8/rockchip/rock64 I've been using ALARM on this board for several months, but it has always had intermittent kernel panics, and i never got any good log data. A few days ago it panicked while i was installing software, which borked the OS enough to make me want to go ahead and try openSUSE on it. > > >>>> Thanks >>>> >>>> > -- To unsubscribe, e-mail: [email protected] To contact the owner, e-mail: [email protected]
