narmstrong changed the topic of #linux-amlogic to: Amlogic mainline kernel development discussion - our wiki http://linux-meson.com/ - ml linux-amlogic@lists.infradead.org - Publicly Logged on https://irclog.whitequark.org/linux-amlogic
vagrantc has joined #linux-amlogic
jakogut has quit [Quit: jakogut]
jakogut_ is now known as jakogut
<steev> narmstrong: do you happen to have a link to the forums post? maybe i'm searching for the wrong thing but hikey mali gnome wayland isn't bringing anything up
jakogut_ has joined #linux-amlogic
<steev> hm, and whatever i did yesterday... isn't working today
vagrantc has quit [Ping timeout: 256 seconds]
vagrantc has joined #linux-amlogic
vagrantc has quit [Client Quit]
lissyx has joined #linux-amlogic
Barada has joined #linux-amlogic
lissyx has quit [Ping timeout: 256 seconds]
vagrantc has joined #linux-amlogic
jakogut_ has quit [Quit: jakogut_]
<steev> narmstrong: one other minor thing, not sure... the odroid-c2 can't seem handle 1366x768 correct, i'm not sure if other amlogic devices are the same, and in order to use a screen with that display on the vendor kernel, you have to set it to 1360x768. would that be considered too hacky to add in for the odroid?
<narmstrong> steev: can you elaborate on the 1366x768 mode ? I also have some display showing it distorted
<steev> i'm not strictly sure on the background of it - but the upstream kernel using boot.ini uses `setenv m "1360x768p60hz"` instead of 1366x768, i'm not sure what/where the 6 pixels have gone
<steev> sorry, vendor kernel*
lissyx has joined #linux-amlogic
<steev> i also plugged in my vu7 which worked great, and this random lcd controller and it worked as well, which surprised me because it doesn't actually have an edid, it just takes whatever you throw at it and (typically) downsizes it to the lcd screen
<steev> oh shit, hdmi audio is working, i hadn't tested it :)
ldevulder_ is now known as ldevulder
<ldevulder> narmstrong, hi, don't know if you had time to test installation of opensuse on the libretech-cc, but I try and my iso is not booting... I retried on the khadas vim and same issue... weird as I was able to install it multiple time... and I tried with new u-boot and the old one used to install and it's the same...
<ldevulder> i'm trying with a more recent iso
lissyx has quit [Ping timeout: 256 seconds]
<ldevulder> ok, I tried to install leap15 instead of tumbleweed version of opensuse... and only tumbleweed work, so conclusion it's not good to try to test an os/sbc at a late hour :)
lissyx has joined #linux-amlogic
return0e_ has joined #linux-amlogic
return0e has quit [Read error: Connection reset by peer]
<ldevulder> narmstrong, lvrp16_, so I tested opensuse tumbleweed on libretech-cc successfully! Installation from iso on USB key on a ssd connected with usb (no emmc yet, but should be also ok, I tested this part on the vim board)
vagrantc has quit [Ping timeout: 256 seconds]
_whitelogger has joined #linux-amlogic
ldevulder has quit [Quit: Leaving]
Barada has quit [Quit: Barada]
ldevulder has joined #linux-amlogic
Barada has joined #linux-amlogic
Barada has quit [Quit: Barada]
lissyx has quit [Ping timeout: 256 seconds]
afaerber has quit [Quit: Leaving]
jakogut_ has joined #linux-amlogic
afaerber has joined #linux-amlogic
lissyx has joined #linux-amlogic
sputnik_ has quit [Remote host closed the connection]
<narmstrong> ldevulder: honestly I forgot... I’m really interested but I lacked time... thanks for testing it on libretech cc !!!
<narmstrong> It’s pretty cool to be able to install vanilla distros like that !
afaerber has quit [Quit: Leaving]
<ldevulder> narmstrong, yes :) it can be useful when you want something more configured/tuned than an image, it's kind of server/desktop installation :)
afaerber has joined #linux-amlogic
<ldevulder> wiki page for libretech-cc on opensuse.org is up-to-date also (it's just a link to the vim page for the installation procedure, it's to not duplicate things)
lissyx has quit [Ping timeout: 256 seconds]
return0e_ has quit [Ping timeout: 264 seconds]
lissyx has joined #linux-amlogic
mag has quit [Remote host closed the connection]
lissyx has quit [Ping timeout: 256 seconds]
trem has joined #linux-amlogic
sputnik_ has joined #linux-amlogic
return0e has joined #linux-amlogic
mag- has joined #linux-amlogic
afaerber has quit [Quit: Leaving]
ldevulder has quit [Ping timeout: 248 seconds]
ldevulder has joined #linux-amlogic
The_Coolest has joined #linux-amlogic
<The_Coolest> Hey guys, I have a question. The Xaiomi Mi Box 'AB' model has secure boot enabled. We've seen that Armbian someone managed to boot on the device, but our build (CoreELEC) obviously doesn't boot because it fails the secure boot check. It seems that Armbian somehow goes around the secure boot procedure. Does anyone have an idea how they achieve this?
<The_Coolest> *Xiaomi?
<The_Coolest> someone = somehow*
<The_Coolest> Here's the uboot log from armbian https://paste.ubuntu.com/p/z8g8PVB66H/
<ndufresne> The_Coolest, don't you just have to use the same uboot binary ?
<The_Coolest> The same as what?
<The_Coolest> From what I understand, if the secure boot efuse is set, there's no way around it (normally)
<ndufresne> as armbian
<The_Coolest> They don't replace the uboot.
<The_Coolest> Simply stick in the USB drive, and it boots up
<ndufresne> iirc it's a simple chain, so the secure boot checks that the u-boot binary is signed/trusted, and boots it
<The_Coolest> It seems that armbian employs some sort of trickery to do it, or the binary is somehow signed to match the security check
<ndufresne> And then u-boot needs to carry on security
<The_Coolest> the u-boot checks the kernel image.
<ndufresne> I'll let someone that knows reply then
<The_Coolest> Look at line #184 in the log.
<The_Coolest> ok, thanks for trying. honestly I don't really know how all of this works. Just thought I'd ask, maybe someone knows something that can help.
<ndufresne> WARNING! efuse bits is disabled, doesn't that simply mean that you won't be able to flash the lower boot eprom from armbian ?
<The_Coolest> But they are disabled after the kernel has started already
<The_Coolest> We fail after the "reading" part on line 185
<The_Coolest> aml log returns a check error
afaerber has joined #linux-amlogic
sputnik_ has quit [Remote host closed the connection]
<ndufresne> according to this article, most deployment only do SHA265 integrity check, no authentication
<ndufresne> If it's the case for you, all you need is to add the signature to your kernel
sputnik_ has joined #linux-amlogic
<The_Coolest> hmm. we tried the AMlogic sign tool, that didn't work.
<ndufresne> you could also drop an email to the armbian packagers
<ndufresne> maybe they just paid to have a key, and really signed it
<The_Coolest> That's an interesting find in that article. I don't think we tried it.
<The_Coolest> So we just need to use the aml-bootloader-tool script to update the hash on our kernel?
return0e has quit [Read error: Connection reset by peer]
return0e has joined #linux-amlogic
<ndufresne> The_Coolest, well, in the article, they update BL2, with a non-secure BL2 this way
<ndufresne> but I'm not sure how this is done
<The_Coolest> Well maybe the aml sign tool wasn't what we needed, because we compared the armbian image, and it doesn't seem to be signed with it
<The_Coolest> We'll give it a shot. Thanks for the find.
<ndufresne> finger cross, but keep in mind that you can likely contact privatly the armbian people
<The_Coolest> It was a build from one specific guy, and he wasn't very helpful, although I wasn't the one talking to him
<ndufresne> hmm, so it's not an official armbian ?
<The_Coolest> I don't think so
mag- is now known as mag
mag has quit [Ping timeout: 248 seconds]
chewitt has quit [Read error: Connection reset by peer]
mag has joined #linux-amlogic
mag is now known as Guest41740
chewitt has joined #linux-amlogic
ldevulder has quit [Quit: Leaving]
return0e has quit [Quit: Leaving...]
Guest41740 has quit [Ping timeout: 256 seconds]
mag- has joined #linux-amlogic
mag- has quit [Ping timeout: 240 seconds]
return0e has joined #linux-amlogic
trem has quit [Quit: Leaving]
sputnik_ has quit [Remote host closed the connection]