17:42 <Armbian-Discord> <T​heBug> 😉

18:20 <Armbian-Discord> <d​ave> I'm sorry for your loss (of free time).

18:24 <Armbian-Discord> <d​ave> @IgorPec so my PCIe patch broke your R4S?

18:25 <Armbian-Discord> <d​ave> I thought it was a different device

18:25 <Armbian-Discord> <M​anoftheSea> heh, yeah. But then in a decade, I can get the kids to help do computer work.

18:26 <Armbian-Discord> <T​enkawa> @ManoftheSea got any kids that already like electronics/computers yet?

18:26 <Armbian-Discord> <M​anoftheSea> yes.

18:26 <Armbian-Discord> <T​enkawa> neat

18:27 <Armbian-Discord> <T​enkawa> That's how I was

18:27 <Armbian-Discord> <I​gorPec> yes, it broke

18:27 <Armbian-Discord> <d​ave> that's so odd..

18:28 <Armbian-Discord> <I​gorPec> my kids are just looking PCB under the magnifying glass 🙂

18:28 <Armbian-Discord> <M​anoftheSea> They had snap circuits, which they loved eating batteries with

18:29 <Armbian-Discord> <I​gorPec> don't know how to attract them to hack kernel or similar 😉

18:29 <Armbian-Discord> <M​anoftheSea> And the oldest liked running SNES emulators on an orange pi

18:30 <Armbian-Discord> <M​anoftheSea> but that was more video game than electronics

18:30 <Armbian-Discord> <T​enkawa> Granted this stuff was all still barely even considered a "microcomputer" when I was young

18:36 <Armbian-Discord> <d​ave> I'm testing 6.0 with my patch now to double check

18:39 <Armbian-Discord> <d​ave> what's media-6.0 vs rockchip-6.0?

18:39 <Armbian-Discord> <I​gorPec> how to explain ? 🙂

18:40 <Armbian-Discord> <I​gorPec> media is maintained by one person

18:40 <Armbian-Discord> <I​gorPec> its coming from tv boxes scene, trying to cover more at once

18:40 <Armbian-Discord> <d​ave> ah

18:40 <Armbian-Discord> <I​gorPec> rockchip is main target

18:42 <Armbian-Discord> <I​gorPec> will build one image for r4s

18:42 <Armbian-Discord> <I​gorPec> with your parch and see

18:45 <Armbian-Discord> <I​gorPec> sent you invite to Jira. Log is created from Jira. If you want that works is mention, it has to be there.

18:47 <Armbian-Discord> <d​ave> does it take a minute to show up?

18:48 <Armbian-Discord> <I​gorPec> you mean boot process?

18:48 <Armbian-Discord> <d​ave> no, the Jira invite

18:48 <Armbian-Discord> <I​gorPec> it should go at once

18:49 <Armbian-Discord> <d​ave> was it this email?

18:49 <Armbian-Discord> <d​ave> https://cdn.discordapp.com/attachments/858684284070789130/1034901513946013786/unknown.png

18:49 <Armbian-Discord> <d​ave> I filled out that form already 🙂

18:49 <Armbian-Discord> <I​gorPec> no, another onme

18:49 <Armbian-Discord> <I​gorPec> to your email you have changed there

18:50 <Armbian-Discord> <I​gorPec> david at your firstlast.com

18:50 <Armbian-Discord> <I​gorPec> perhaps Jira system is off line 😉

18:50 <Armbian-Discord> <d​ave> yep that's correct

18:51 <Armbian-Discord> <d​ave> just got it now

18:52 <Armbian-Discord> <d​ave> I'm on the jira now 🙂

18:54 <Armbian-Discord> <d​ave> yeah booted up flawlessly on my R4S.

18:56 <Armbian-Discord> <I​gorPec> i am few minutes away

19:01 <Armbian-Discord> <d​ave> do a fresh build if possible

19:07 <Armbian-Discord> <I​gorPec> it works

19:07 <Armbian-Discord> <d​ave> huh, that's good

19:07 <Armbian-Discord> <I​gorPec> yeah, will see if survives reboot

19:10 <Armbian-Discord> <d​ave> My R4S did.

19:10 <Armbian-Discord> <I​gorPec> in theory patch should not do harm

19:11 <Armbian-Discord> <I​gorPec> perhaps it was something else in my case

19:11 <Armbian-Discord> <I​gorPec> i am testing this with K6, before it was 5.15

19:11 <Armbian-Discord> <I​gorPec> reboot works

19:11 <Armbian-Discord> <d​ave> ahhhhhhhh

19:11 <Armbian-Discord> <d​ave> I never tested 5.15

19:11 <Armbian-Discord> <d​ave> only 5.19

19:12 <Armbian-Discord> <I​gorPec> that we need to checkl

19:13 <Armbian-Discord> <d​ave> eh, I don't mind just removing the patch for 5.15

19:13 <Armbian-Discord> <I​gorPec> 5.15.y is LTS kernel which will stay for awhile

19:13 <Armbian-Discord> <I​gorPec> 5.19.y is EOL

19:13 <Armbian-Discord> <I​gorPec> 6.1 LTS is next year

19:14 <Armbian-Discord> <I​gorPec> did several reboots, works

19:15 <Armbian-Discord> <d​ave> On 5.15?

19:15 <Armbian-Discord> <I​gorPec> no, on 6.y ... building kernel 5.15 now

19:16 <Armbian-Discord> <d​ave> Also, the RNG seems to somehow work better now…

19:17 <Armbian-Discord> <d​ave> Earlier today and yesterday I was seeing a lot of AA and 55 values.

19:23 <Armbian-Discord> <I​gorPec> works

19:23 <Armbian-Discord> <I​gorPec> on 5.15.y too

19:25 <Armbian-Discord> <I​gorPec> now you can do some records to Jira so this gets to the list

19:25 <Armbian-Discord> <I​gorPec> great work!

19:27 <Armbian-Discord> <I​gorPec> here we could tweak nic devices names - > lan0 wan0 instead of defaults

19:27 <Armbian-Discord> <I​gorPec> which is purely optional

19:28 <Armbian-Discord> <d​ave> Weird. Wonder what your old issue was.

19:29 <Armbian-Discord> <d​ave> Is the cpuid always unique?

19:30 <Armbian-Discord> <I​gorPec> CPU implementer : 0x41 CPU architecture: 8 CPU variant : 0x0 CPU part : 0xd08 CPU revision : 2

19:30 <Armbian-Discord> <I​gorPec> this?

19:50 <Armbian-Discord> <d​ave> na this. https://github.com/u-boot/u-boot/blob/master/arch/arm/dts/rk3399.dtsi#L1314

19:50 <Armbian-Discord> <I​gorPec> this is display in u-boot?

20:15 <Armbian-Discord> <d​ave> should be

20:15 <Armbian-Discord> <d​ave> lemme try checking

20:15 <Armbian-Discord> <I​gorPec> don't have console on this hw

20:16 <Armbian-Discord> <d​ave> should be doable without u-boot though, one sec

20:17 <Armbian-Discord> <d​ave> cpu-id@7 { reg = <0x07 0x10>; phandle = <0x10f>; };

20:23 <Armbian-Discord> <d​ave> xxd /sys/bus/nvmem/devices/rockchip-efuse0/nvmem Might be this?

20:23 <Armbian-Discord> <d​ave> https://forum.armbian.com/topic/14653-rock64-same-mac-on-two-boards/?do=findComment&comment=105425

20:30 <Armbian-Discord> <I​gorPec> so those numbers are unique per device?

20:31 <Armbian-Discord> <I​gorPec> mine are different that those, yes

20:31 <Armbian-Discord> <d​ave> if I'm reading it correctly, I think bytes 0x07 to 0x10 should be unique?

20:31 <Armbian-Discord> <d​ave> root@nanopi-r4s:~# xxd /sys/bus/nvmem/devices/rockchip-efuse0/nvmem 00000000: 524b 3399 91fe 2154 4641 5636 322e 3030 RK3...!TFAV62.00 00000010: 0000 0000 1881 061d 1318 1013 0800 0000 ................ 00000020: 0000 1000 0000 0000 0000 0000 0000 0000 ................ 00000030: 0000 0000 0000 0000 0000 0000 0000 0000 ................ 00000040: 0000 0000 0000 0000 0000 0000 0000 0000 ................

20:31 <Armbian-Discord> 00000050: 0000 0000 0000 0000 0000 0000 0000 0000 ................ 00000060: 0000 0000 0000 0000 0000 0000 0000 0000 ................ 00000070: 0000 0000 0000 0000 0000 0000 0000 0000 ................

20:31 <Armbian-Discord> <I​gorPec> 00000000: 524b 3399 91fe 2154 4141 5039 322e 3030 RK3...!TAAP92.00 00000010: 0000 0000 1100 8a27 1c23 151a 0800 0000 .......'.#......

20:31 <Armbian-Discord> <d​ave> isn't this... 91fe 2154?

20:32 <Armbian-Discord> <I​gorPec> yes, looks good

20:32 <Armbian-Discord> <I​gorPec> oh

20:32 <Armbian-Discord> <d​ave> but yours is also 91fe 2154

20:32 <Armbian-Discord> <I​gorPec> i didn't look right

20:32 <Armbian-Discord> <I​gorPec> yes

20:33 <Armbian-Discord> <I​gorPec> so this is not working right

20:36 <Armbian-Discord> <d​ave> https://github.com/u-boot/u-boot/blob/master/arch/arm/mach-rockchip/misc.c

20:36 <Armbian-Discord> <d​ave> what's your MAC address?

20:36 <Armbian-Discord> <d​ave> root@nanopi-r4s:~# ip l 1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN mode DEFAULT group default qlen 1000 link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00 2: lan: <NO-CARRIER,BROADCAST,MULTICAST,UP> mtu 1500 qdisc pfifo_fast state DOWN mode DEFAULT group default qlen 1000 link/ether e2:8b:66:ad:b5:b8 brd ff:ff:ff:ff:ff:ff altname enp1s0 3: wan:

20:36 <Armbian-Discord> <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc mq state UP mode DEFAULT group default qlen 1000 link/ether 04:91:62:b4:2f:66 brd ff:ff:ff:ff:ff:ff

20:36 <Armbian-Discord> <d​ave> oh wait wrong device

20:37 <Armbian-Discord> <d​ave> root@nanopi-r4s:~# ip l 1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN mode DEFAULT group default qlen 1000 link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00 2: lan: <NO-CARRIER,BROADCAST,MULTICAST,UP> mtu 1500 qdisc pfifo_fast state DOWN mode DEFAULT group default qlen 1000 link/ether e2:06:b3:3f:2c:74 brd ff:ff:ff:ff:ff:ff altname enp1s0 3: wan:

20:37 <Armbian-Discord> <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc mq state UP mode DEFAULT group default qlen 1000 link/ether e2:06:6c:d7:d3:41 brd ff:ff:ff:ff:ff:ff

20:37 <Armbian-Discord> <d​ave> same as me?

20:38 <Armbian-Discord> <I​gorPec> 1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN mode DEFAULT group default qlen 1000 link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00 2: enp1s0: <NO-CARRIER,BROADCAST,MULTICAST,UP> mtu 1500 qdisc pfifo_fast state DOWN mode DEFAULT group default qlen 1000 link/ether fa:b4:ff:00:ff:4d brd ff:ff:ff:ff:ff:ff 3: eth0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc mq state UP

20:38 <Armbian-Discord> mode DEFAULT group default qlen 1000 link/ether 80:1f:12:fc:71:c2 brd ff:ff:ff:ff:ff:ff

20:38 <Armbian-Discord> <I​gorPec> we could have userspace mitigation enabled by default

20:40 <Armbian-Discord> <d​ave> enp1s0 has bit set, so it's local

20:48 <Armbian-Discord> <d​ave> my MAC address doesn't change between u-boot and userspace