14:26 <DC-IRC> [Discord] <c0rnelius77> Is it just me or is the forum broke? I can't reply to forum posts. Tried box Chrome and Firefox.

14:28 <DC-IRC> [Discord] <c0rnelius77> both*

14:45 <DC-IRC> [Discord] <laibsch> not just you

14:45 <DC-IRC> [Discord] <Werner> confirmed

14:48 <DC-IRC> [Discord] <Werner> retry

14:50 <DC-IRC> [Discord] <c0rnelius77> works. thanx.

17:32 <DC-IRC> [Discord] <x_rew_x> Hi, I'm trying to get armbian running on my Cubie A5E. I "xz -d" -ed the image and used dd to write it to an SD card. I then tried it an I don't think I got a boot. Nothing on the screen for several minutes, no activity on the leds.

17:32 <DC-IRC> [Discord] <x_rew_x> So then I started to read some documentation and... it was recommended to use "etcher". Fine, so I download etcher. Welll I dislike that program as it takes about a minute to come to the conclusion that "something went wrong, check the downloaded image". On my second attempt, it flashed "permission denied /dev/sda" at me for a short while. Oops correct. So I chmod 666 /dev/sda an <clipped message>

17:32 <DC-IRC> [Discord] <x_rew_x> d try again. Same problem.

17:32 <DC-IRC> [Discord] <x_rew_x> So... does etcher just make it easy-for-noobs-to-flash and just "more difficult" for me as a long-time linux/Unix user or does it do more than what I did with "dd"?

17:35 <DC-IRC> [Discord] <Werner> For once we do not recommend balenaEtcher at this time but do recommend USBimager. And for the other, which is also stated in the docs, these tools actually verify written data where dd does not.

17:42 <DC-IRC> [Discord] <x_rew_x> I understand that "in general" that might be necessary. In this case, a new sandisk Extreme Pro in a good sdcard reader... I trust it.

17:42 <DC-IRC> [Discord] <x_rew_x> The good news. I must have done something wrong first time around. I reimaged the sd card, and now it boots. Blue heartbeat but black screen. I have another SD card with another image and that one "has screen output" so I'm pretty confident I didn't screw that up this time.

17:42 <DC-IRC> [Discord] <x_rew_x> I'll reimage another time, and this time manually do the verify....

17:49 <DC-IRC> [Discord] <x_rew_x> I've re-imaged, removed the SD card, and reinserted it into my PC. Then read the first 1812Mb of data off the SD card and that file has the same MD5sum as the uncompressed image file. I've done the verify and I say the SD card holds the correct data.

17:53 <DC-IRC> [Discord] <x_rew_x> The machine is intended to be used "headless". It is annoying that I have to go find a screen and keyboard for the "startup procedure". I can edit my account info into /etc/passwd and /etc/shadow by hand. What else do I need to do to make it start the network, DHCP and enable ssh ?

17:59 <DC-IRC> [Discord] <Werner> DHCP and ssh are enabled by default on all images.

17:59 <DC-IRC> [Discord] <Werner> Check your router for ip address and login with root/1234

18:01 <DC-IRC> [Discord] <x_rew_x> AhH! Thanks!

18:01 <DC-IRC> [Discord] <x_rew_x> Turns out I was using the wrong ethernet port. I thought they'd both do DHCP. The second one apparently doesn't.

18:04 <DC-IRC> [Discord] <Werner> All interfaces should have DHCP enabled by default. Though maybe the other port does not work for whatever reason. The support for this fairly new SoC is barely enough to have a booting system and some basic stuff working

18:07 <DC-IRC> [Discord] <x_rew_x> Now I can log in, and have finished the "first boot" procedure, I can have a look. 🙂

18:07 <DC-IRC> [Discord] <x_rew_x> (installed ssh keys, my preferred shell... )

22:10 <Dex2x> Hi all, is there a way to see why I have a huge syslog, or turn it off somehow?

22:21 <Dex2x> erm /var/log/sysstat ** <-

22:58 <DC-IRC> [Discord] <tomurlings> you can try to disable the service:

22:58 <DC-IRC> [Discord] <tomurlings> sudo systemctl stop sysstat

22:59 <DC-IRC> [Discord] <tomurlings> sudo systemctl disable sysstat

22:59 <Dex2x> as far as I can see it wasn't even running

23:00 <DC-IRC> [Discord] <tomurlings> not entirely sure, but i think this enables/disables a cronjob that runs sar, which fills sysstat

23:02 <DC-IRC> [Discord] <tomurlings> yes, you can check /etc/cron.d/sysstat. debian-sa1. that apparantly creates the data, and sar can make reports of said data

23:02 <Dex2x> ah I do have that

23:04 <DC-IRC> [Discord] <tomurlings> do look a bit further, seems i'm only scratching the surface. it's a bit more convoluted.

23:07 <DC-IRC> [Discord] <tomurlings> seems like stop/disable sysstat does not remove the report generation in the cronjob.

23:09 <DC-IRC> [Discord] <tomurlings> yeah, not exactly. debian-sa1 seems to generate the reports and sa1 (-> sadc) seems to generate the data for the reports.