5 minutes ago, MCredbear said:

why rock64's and station M1's images still need be tested while renegade's image is already works

You said that Renegade image is corrupting filesystem when used on SD card, didn't  you? That is what we want to fix.

55 minutes ago, JMCC said:

You said that Renegade image is corrupting filesystem when used on SD card, didn't  you? That is what we want to fix.

OK,station M1's image with 4.x kernel and desktop had a filesystem error after the first boot,but the second time it fixed the error correctly.log: http://ix.io/2PWU. I'll try rock64's image soon.

1 hour ago, JMCC said:

You said that Renegade image is corrupting filesystem when used on SD card, didn't  you? That is what we want to fix.

Rock64's image with 5.x kernel didn't have filesystem error, log: http://ix.io/2PX6

26 minutes ago, MCredbear said:

Rock64's image with 5.x kernel didn't have filesystem error

Well, kernel 5.x doesn't have the error with Renegade either. The bug is specific to the 4.4 kernel.

 

NOTE: I moved all the posts to the proper place, in the Renegade thread. Please use this thread for this issue from now on.

44 minutes ago, MCredbear said:

OK,station M1's image with 4.x kernel and desktop had a filesystem error after the first boot,but the second time it fixed the error correctly.

Rock64's image with 4.x kernel and desktop is as the same as it.log: http://ix.io/2PXh

2 minutes ago, MCredbear said:

Rock64's image with 4.x kernel and desktop is as the same as it.log: http://ix.io/2PXh

It's strange, that it only has the filesystem error the first time. Did you use it for a while? Normally, the error appears after some intensive I/O, like using the desktop for a while (e.g.: browsing with Chromium), or installing a big number of packages through APT.

3 minutes ago, JMCC said:

It's strange, that it only has the filesystem error the first time. Did you use it for a while? Normally, the error appears after some intensive I/O, like using the desktop for a while (e.g.: browsing with Chromium), or installing a big number of packages through APT.

Maybe,I run touch as soon as the desktop was just prepared.

As far as I know, Libre Renegade is the same model as Firefly-rk3328. I got Firefly-rk3328 and built a set of images for it. I checked, everything works. I'm wondering if someone can test these images on Renegade rk3328.

 

https://users.armbian.com/balbes150/renegade/

I'd be interested in buster current and legacy, but your link is to checksums.

8 minutes ago, cibolajerry said:

I'd be interested in buster current and legacy, but your link is to checksums.

I see both the images and the checksums there. Retry with glasses

It seems like images have not finished uploading yet, some of the links are broken. Just wait a few hours...

 

 

On 4/9/2021 at 4:58 AM, Werner said:

I see both the images and the checksums there. Retry with glasses

Every file in that directory has the sha filename extension

Hm was not the case when I took a look. Now I can see it too. Odd.

11.04.2021 в 11:30, Werner сказал:

Hm was not the case when I took a look. Now I can see it too. Odd.

@lanefu It looks like the synchronization is broken. 

11.04.2021 в 07:50, cibolajerry сказал:

Every file in that directory has the sha filename extension

 

 

https://disk.yandex.ru/d/YSO7Ik-YWCEBbA?w=1

4 hours ago, balbes150 said:

@lanefu It looks like the synchronization is broken. 

Yeah weird error message

 

Spoiler

pr 12 13:16:24 worksonarmbian.armbian.com rclone[2558396]: Elapsed time:       9m3.9s
Apr 12 13:16:24 worksonarmbian.armbian.com rclone[2558396]: Transferring:
Apr 12 13:16:24 worksonarmbian.armbian.com rclone[2558396]:  * jetson-nano/Armbian_21…current_5.10.29.img.xz:  2% /238.977M, 115.268k/s, 34m22s
Apr 12 13:16:24 worksonarmbian.armbian.com rclone[2558396]:  * jetson-nano/Armbian_21…29_xfce_desktop.img.xz:  0% /782.986M, 111.006k/s, 1h59m21s
Apr 12 13:16:24 worksonarmbian.armbian.com rclone[2558396]:  * jetson-nano/Armbian_21…current_5.10.29.img.xz:  2% /260.381M, 115.042k/s, 37m37s
Apr 12 13:16:24 worksonarmbian.armbian.com rclone[2558396]:  * jetson-nano/Armbian_21…current_5.10.29.img.xz:  2% /338.123M, 119.849k/s, 47m9s
Apr 12 13:16:29 worksonarmbian.armbian.com rclone[2558396]: ERROR : jetson-nano/Armbian_21.05.0-trunk_Jetson-nano_focal_current_5.10.29.img.xz: Failed to copy: Update ReadFrom failed: failed to send packet: EOF
Apr 12 13:16:30 worksonarmbian.armbian.com rclone[2558396]: ERROR : jetson-nano/Armbian_21.05.0-trunk_Jetson-nano_hirsute_current_5.10.29.img.xz: Failed to copy: Update ReadFrom failed: Connection Lost
Apr 12 13:16:30 worksonarmbian.armbian.com rclone[2558396]: ERROR : jetson-nano/Armbian_21.05.0-trunk_Jetson-nano_focal_current_5.10.29_xfce_desktop.img.xz: Failed to copy: Update ReadFrom failed: failed to send packet: EOF
Apr 12 13:16:30 worksonarmbian.armbian.com rclone[2558396]: ERROR : jetson-nano/Armbian_21.05.0-trunk_Jetson-nano_sid_current_5.10.29.img.xz: Failed to copy: Update ReadFrom failed: failed to send packet: EOF
Apr 12 13:17:24 worksonarmbian.armbian.com rclone[2558396]: INFO  :
Apr 12 13:17:24 worksonarmbian.armbian.com rclone[2558396]: Transferred:             240.454M / 2.878 GBytes, 8%, 414.604 kBytes/s, ETA 1h51m24s
Apr 12 13:17:24 worksonarmbian.armbian.com rclone[2558396]: Errors:                32 (retrying may help)
Apr 12 13:17:24 worksonarmbian.armbian.com rclone[2558396]: Checks:                32 / 32, 100%
Apr 12 13:17:24 worksonarmbian.armbian.com rclone[2558396]: Transferred:            7 / 13, 54%
Apr 12 13:17:24 worksonarmbian.armbian.com rclone[2558396]: Elapsed time:      10m3.9s
Apr 12 13:17:24 worksonarmbian.armbian.com rclone[2558396]: Transferring:
Apr 12 13:17:24 worksonarmbian.armbian.com rclone[2558396]:  * rk3288/Armbian_21.05.0…current_5.10.29.img.xz:  1% /283.066M, 115.071k/s, 41m9s
Apr 12 13:17:24 worksonarmbian.armbian.com rclone[2558396]:  * rk3288/Armbian_21.05.0…29_xfce_desktop.img.xz:  0% /888.227M, 119.986k/s, 2h5m27s
Apr 12 13:17:24 worksonarmbian.armbian.com rclone[2558396]:  * rk3288/Armbian_21.05.0…current_5.10.29.img.xz:  2% /226.541M, 119.959k/s, 31m20s
Apr 12 13:17:24 worksonarmbian.armbian.com rclone[2558396]:  * rk3288/Armbian_21.05.0…29_xfce_desktop.img.xz:  0% /770.747M, 114.984k/s, 1h53m35s
Apr 12 13:17:36 worksonarmbian.armbian.com rclone[2558396]: ERROR : rk3288/Armbian_21.05.0-trunk_Rk3288_buster_current_5.10.29.img.xz: Failed to copy: Update ReadFrom failed: failed to send packet: EOF
Apr 12 13:17:36 worksonarmbian.armbian.com rclone[2558396]: ERROR : rk3288/Armbian_21.05.0-trunk_Rk3288_buster_current_5.10.29_xfce_desktop.img.xz: Failed to copy: Update ReadFrom failed: failed to send packet: EOF
Apr 12 13:17:36 worksonarmbian.armbian.com rclone[2558396]: ERROR : rk3288/Armbian_21.05.0-trunk_Rk3288_focal_current_5.10.29_xfce_desktop.img.xz: Failed to copy: Update ReadFrom failed: failed to send packet: EOF
Apr 12 13:17:36 worksonarmbian.armbian.com rclone[2558396]: ERROR : rk3288/Armbian_21.05.0-trunk_Rk3288_focal_current_5.10.29.img.xz: Failed to copy: Update ReadFrom failed: failed to send packet: EOF

 

18 минут назад, lanefu сказал:

Yeah weird error message

I have already tried clearing all files in both places (on the build server and on the upload server). it didn't work. for some reason, sending large files (images) does not work.

yeah... it seems like network issue.. or something. need @Igor to look on his side..

I read concurrency can cause problems.. so I made some adjustments so that it only does 2 sessions.. but still getting error

Spoiler

 send packet: EOF
Apr 12 15:00:52 worksonarmbian.armbian.com systemd[1]: armbian_users_sync_balbes150.service: Current command vanished from the unit file, execution of the command list won't be resumed.
Apr 12 15:00:55 worksonarmbian.armbian.com systemd[1]: armbian_users_sync_balbes150.service: Succeeded.
Apr 12 15:01:00 worksonarmbian.armbian.com systemd[1]: Started "Sync /home/balbes150/users_armbian_com_upload".
Apr 12 15:01:03 worksonarmbian.armbian.com rclone[3290808]: INFO  : sftp://balbes150@users.armbian.com:22/web/: Running all checks before starting transfers
Apr 12 15:01:13 worksonarmbian.armbian.com rclone[3290808]: INFO  : sftp://balbes150@users.armbian.com:22/web/: Checks finished, now starting transfers
Apr 12 15:02:04 worksonarmbian.armbian.com rclone[3290808]: INFO  :    11.305M / 22.565 GBytes, 0%, 228.470 kBytes/s, ETA 1d4h45m10s (xfr#0/45)
Apr 12 15:02:18 worksonarmbian.armbian.com rclone[3290808]: ERROR : jetson-nano/Armbian_21.05.0-trunk_Jetson-nano_buster_current_5.10.29_xfce_desktop.img.xz: Failed to copy: Update ReadFrom failed: failed to send packet: EOF
Apr 12 15:02:18 worksonarmbian.armbian.com rclone[3290808]: ERROR : jetson-nano/Armbian_21.05.0-trunk_Jetson-nano_focal_current_5.10.29.img.xz: Failed to copy: Update ReadFrom failed: failed to send packet: EOF
Apr 12 15:03:03 worksonarmbian.armbian.com rclone[3290808]: INFO  :    23.359M / 21.449 GBytes, 0%, 216.143 kBytes/s, ETA 1d4h52m23s (xfr#0/43)
Apr 12 15:03:23 worksonarmbian.armbian.com rclone[3290808]: ERROR : jetson-nano/Armbian_21.05.0-trunk_Jetson-nano_hirsute_current_5.10.29.img.xz: Failed to copy: Update ReadFrom failed: failed to send packet: EOF
Apr 12 15:03:23 worksonarmbian.armbian.com rclone[3290808]: ERROR : jetson-nano/Armbian_21.05.0-trunk_Jetson-nano_focal_current_5.10.29_xfce_desktop.img.xz: Failed to copy: Update ReadFrom failed: failed to send packet: EOF
Apr 12 15:04:03 worksonarmbian.armbian.com rclone[3290808]: INFO  :    35.820M / 20.443 GBytes, 0%, 214.922 kBytes/s, ETA 1d3h39m27s (xfr#0/41)
Apr 12 15:04:28 worksonarmbian.armbian.com rclone[3290808]: ERROR : jetson-nano/Armbian_21.05.0-trunk_Jetson-nano_sid_current_5.10.29.img.xz: Failed to copy: Update ReadFrom failed: failed to send packet: EOF
Apr 12 15:04:28 worksonarmbian.armbian.com rclone[3290808]: ERROR : jetson-nano/Armbian_21.05.0-trunk_Jetson-nano_buster_current_5.10.29.img.xz: Failed to copy: Update ReadFrom failed: failed to send packet: EOF
Apr 12 15:05:03 worksonarmbian.armbian.com rclone[3290808]: INFO  :    47.812M / 19.797 GBytes, 0%, 212.254 kBytes/s, ETA 1d3h6m11s (xfr#0/39)
Apr 12 15:05:33 worksonarmbian.armbian.com rclone[3290808]: ERROR : renegade/Armbian_21.05.0-trunk_Renegade_buster_current_5.10.29.img.xz: Failed to copy: Update ReadFrom failed: failed to send packet: EOF
Apr 12 15:05:33 worksonarmbian.armbian.com rclone[3290808]: ERROR : renegade/Armbian_21.05.0-trunk_Renegade_buster_current_5.10.29_xfce_desktop.img.xz: Failed to copy: Update ReadFrom failed: failed to send packet: EOF
Apr 12 15:06:04 worksonarmbian.armbian.com rclone[3290808]: INFO  :    60.180M / 18.530 GBytes, 0%, 212.008 kBytes/s, ETA 1d1h22m36s (xfr#0/37)
Apr 12 15:06:38 worksonarmbian.armbian.com rclone[3290808]: ERROR : renegade/Armbian_21.05.0-trunk_Renegade_buster_legacy_4.4.194_xfce_desktop.img.xz: Failed to copy: Update ReadFrom failed: failed to send packet: EOF
Apr 12 15:06:38 worksonarmbian.armbian.com rclone[3290808]: ERROR : renegade/Armbian_21.05.0-trunk_Renegade_focal_current_5.10.29.img.xz: Failed to copy: Update ReadFrom failed: failed to send packet: EOF
Apr 12 15:07:04 worksonarmbian.armbian.com rclone[3290808]: INFO  :    72.578M / 17.391 GBytes, 0%, 211.938 kBytes/s, ETA 23h48m9s (xfr#0/35)
Apr 12 15:07:43 worksonarmbian.armbian.com rclone[3290808]: ERROR : renegade/Armbian_21.05.0-trunk_Renegade_focal_current_5.10.29_xfce_desktop.img.xz: Failed to copy: Update ReadFrom failed: failed to send packet: EOF
Apr 12 15:07:43 worksonarmbian.armbian.com rclone[3290808]: ERROR : renegade/Armbian_21.05.0-trunk_Renegade_hirsute_current_5.10.29.img.xz: Failed to copy: Update ReadFrom failed: failed to send packet: EOF
Apr 12 15:08:03 worksonarmbian.armbian.com rclone[3290808]: INFO  :    84.883M / 16.326 GBytes, 1%, 211.655 kBytes/s, ETA 22h21m11s (xfr#0/33)
Apr 12 15:08:48 worksonarmbian.armbian.com rclone[3290808]: ERROR : renegade/Armbian_21.05.0-trunk_Renegade_sid_current_5.10.29.img.xz: Failed to copy: Update ReadFrom failed: failed to send packet: EOF
Apr 12 15:08:48 worksonarmbian.armbian.com rclone[3290808]: ERROR : aw-h6-tv/Armbian_21.05.0-trunk_Aw-h6-tv_buster_current_5.10.29.img.xz: Failed to copy: Update ReadFrom failed: failed to send packet: EOF
Apr 12 15:09:03 worksonarmbian.armbian.com rclone[3290808]: INFO  :    96.906M / 15.634 GBytes, 1%, 210.832 kBytes/s, ETA 21h28m6s (xfr#0/31)

 

I had numerous issues when using rclone in the past which eventually lead to dropping our main mirror which only had rclone capabilities. But what could in my network cause that? I am moving large amount of data via rsync all the time.

yeah its a really weird error..I'll try switching to https://github.com/mar10/pyftpsync/

 

 

Maybe the ancient way ? use rsync and one file at a time, this does not need to happen so often and will not be a problem.

Hello,

 

my renegade started failing about two weeks ago after a "apt update && apt -y upgrade".

 

Symptoms are: slow network, shutdowns, kernel panics

 

I tried to repair by installing a fresh kernel, compiled from the source, with no real improvement.

So I resorted to creating a new SD card with a complete image (current, focal, server, minimal). 

This boots stable, but still shows issues. Find my "armbianmonitor -u" at http://ix.io/3rCS

 

The only suspicious messages I can see in the logs are

[ ] vdd_logic: Restricting voltage, 1175000-950000uV

[ ] rk3328-dmc-freq dmc: Cannot set voltage 1175000 uV

[ ] devfreq dmc: dvfs failed with (-22) error

 

Is the board dying of age or is some software no longer working ? I'll try an official image next.

1 hour ago, ls48ju said:

with no real improvement.

This means some regression was introduced upstream. Nothing unusual in this world. Also possible that our patches are clashing with upstream changes ... 

 

1 hour ago, ls48ju said:

I'll try an official image next.

 

If you seek images without support, you can just use images from our archive (below) and don't upgrade. That's the main reason why we have it.

1 час назад, ls48ju сказал:

Symptoms are: slow network, shutdowns, kernel panics

Can you check the behavior of your instance on these images (they use different patches than in the official version) ? On a Firefly-roc3328-roc-cc system similar to your model, everything works stably and without problems.

 

There are links to the images in my posts above in this topic.

 

p/s/ if everything works correctly with my test versions, I will be able to send patches to the official version.

On 1/17/2018 at 9:38 AM, mattkosem said:

I ordered one of these the other day. Not sure when it'll be shipped or anything, but I was curious about the level of support it might have at this point.  The only Linux image I see for it anywhere is a 32-bit Ubuntu image on the Firefly site.  Any chance this would boot/run on a rock64 image, or anything like that, until a targeted install is available?

 

--Matt

Armbian has an unsupported image. Here is a list of OS's https://www.electromaker.io/blog/article/best-oses-for-the-libre-computer-roc-rk3328-cc

3 hours ago, EndtheFED said:

Here is a list of OS's 

Which are all unsupported. We take support a bit more serious. Most recent images there were updated in 2018, ours few months ago: https://mirrors.netix.net/armbian/dl/renegade/archive/

 

We just don't have this board in automated testing facility and there are no dedicated persons to have spare time & this board around to check in case of some board specific low-level troubles. Which do come around from time to time - which is for Linux normal MO.

Hello,

 

it seems I got miss understood - my posting was not meant as a plea for support, more like "has anybody seen this already ?".

 

I have not yet found the time to test the supported Armbian image yet, but will do so later today.

 

Yours,

 

Alexander

 

 

ok, I tried it with the official images (focal with 5.10 and buster with 4.4). Both start, but show kernel oops as soon as something is started there. 

 

Seems like the voltage regulator has some hardware problem.

 

Yours,

 

Alexander

I think i read somewhere that this problem was fixed ... try with nightly builds (if they exists) or build image on your own. Worth trying.

On 7/1/2021 at 3:32 AM, ls48ju said:

Hello,

 

my renegade started failing about two weeks ago after a "apt update && apt -y upgrade".

 

Symptoms are: slow network, shutdowns, kernel panics

 

I tried to repair by installing a fresh kernel, compiled from the source, with no real improvement.

So I resorted to creating a new SD card with a complete image (current, focal, server, minimal). 

This boots stable, but still shows issues. Find my "armbianmonitor -u" at http://ix.io/3rCS

 

The only suspicious messages I can see in the logs are

[ ] vdd_logic: Restricting voltage, 1175000-950000uV

[ ] rk3328-dmc-freq dmc: Cannot set voltage 1175000 uV

[ ] devfreq dmc: dvfs failed with (-22) error

 

Is the board dying of age or is some software no longer working ? I'll try an official image next.

 

The RAM controller was being starved for voltage.

 

I have recently rectified this problem and moved to the official mainline USB3 driver for this board.  The GPU and DMC share the same regulator, so there was conflict.  https://github.com/armbian/build/commit/ee610096bc5d252307789c3818aa8b59147bf1d5