elastic_dog has joined #maemo-leste
lolcat has quit [Quit: had to jack off]
akossh has quit [Quit: Leaving.]
nmdv has joined #maemo-leste
nmdv has quit [Ping timeout: 268 seconds]
xmn has quit [Read error: Connection reset by peer]
xmn has joined #maemo-leste
xmn has quit [Ping timeout: 272 seconds]
joerg has quit [Ping timeout: 260 seconds]
joerg has joined #maemo-leste
SystemError has quit [Ping timeout: 260 seconds]
SystemError has joined #maemo-leste
jrayhawk has quit [Ping timeout: 272 seconds]
jrayhawk has joined #maemo-leste
jrayhawk has quit [Ping timeout: 264 seconds]
jrayhawk has joined #maemo-leste
Livio has joined #maemo-leste
akossh has joined #maemo-leste
[TheBug] has quit [Changing host]
[TheBug] has joined #maemo-leste
inky1 has joined #maemo-leste
inky1 has quit [Client Quit]
inky1 has joined #maemo-leste
inky1 has quit [Client Quit]
Livio has quit [Ping timeout: 256 seconds]
SystemError has quit [Remote host closed the connection]
SystemError has joined #maemo-leste
SystemError has quit [Remote host closed the connection]
SystemError has joined #maemo-leste
ceene has quit [Ping timeout: 264 seconds]
eloy has quit [Ping timeout: 240 seconds]
antranigv_ has joined #maemo-leste
antranigv has quit [Ping timeout: 268 seconds]
eloy has joined #maemo-leste
xmn has joined #maemo-leste
lolcat has joined #maemo-leste
pere has quit [Ping timeout: 255 seconds]
SystemError has quit [Remote host closed the connection]
SystemError has joined #maemo-leste
fab_ has joined #maemo-leste
xmn has quit [Ping timeout: 240 seconds]
Somebody3456 has joined #maemo-leste
SystemError has quit [Ping timeout: 260 seconds]
pere has joined #maemo-leste
duuude has quit [Ping timeout: 264 seconds]
duuude has joined #maemo-leste
antranigv_ is now known as antranigv
antranigv is now known as antranigv_
pere has quit [Ping timeout: 268 seconds]
doc has joined #maemo-leste
Somebody3456 is now known as SystemError
antranigv_ is now known as antranigv
pere has joined #maemo-leste
fab_ has quit [Ping timeout: 255 seconds]
<sicelo> i've built a kernel for Librem5, and took the latest image from Pinephone iirc (or was it generic arm64?). anyway, i'm getting "Failed to execute /init (error -13) ... Starting init: /sbin/init exists but couldn't execute it (error -13)" error when booting
<sicelo> i think kernel is ok. what should i set for `init=`?
* sicelo is also a bit tired and not really thinking straight
<sicelo> my uboot cmdline is 'setenv bootargs rootwait root=/dev/sda2 rw console=ttymxc0,115200 debug console=tty0'
<sicelo> yes, it's sda2 ... because i'm using sd card, and on the Librem5 it's sitting behind USB. u-boot knows how to find it there, and i've built both ext4 and the usb support in, so that's not the problem
<Wizzup> sicelo: does it mount rootfs?
<sicelo> yes
<sicelo> let me see if i can upload a picture (because no serial to this thing) :p
<sicelo> serial is ... something like N900
ikmaak has quit [Ping timeout: 256 seconds]
ikmaak has joined #maemo-leste
<Wizzup> interesting
<Wizzup> maybe armhf kernel and userland is arm64 or vice versa?
<Wizzup> maybe google for the error a bi
<Wizzup> wait..
<Wizzup> /etc/init ?
<Wizzup> Does it manage to run /sbin/init ?
<sicelo> it says it can see /sbin/init, but can't run it
<sicelo> Starting init: /sbin/init exists but couldn't execute it (error -13)
<Wizzup> I don't see that on the screen
<Wizzup> and you're sure that sda2 contains /sbin/init?
<Wizzup> maybe run 'file' on it ot see what kind of file it is
<sicelo> it's there on the screen - at 7.125814
<sicelo> and yes sda2 contains the file. sbin/init: ELF 64-bit LSB pie executable, ARM aarch64, version 1 (SYSV), dynamically linked, interpreter /lib/ld-linux-aarch64.so.1, BuildID[sha1]=a32a90ca33581febfd8a89839d20aeec0b85b975, for GNU/Linux 3.7.0, stripped
<sicelo> let me try set init=/bin/sh and see what happens
<Wizzup> sicelo: no
xmn has joined #maemo-leste
<Wizzup> sicelo: that says /etc/init
<sicelo> ah indeed.
<sicelo> /sbin/init is tried a bit earlier up. so somehow it fails. actually init=/bin/sh also doesn't work
<Wizzup> the tomoyo stuff seems suspect
<sicelo> that one's there in mobian too. i'm not sure where it comes from, but i don't think it's the issue
<sicelo> maybe let me re-do the rootfs in case something's borked somewhere
<Wizzup> you could perhaps chroot from another arm64 device just in case
<Wizzup> ok
<Wizzup> does it work wiht the mobian kernel?
<Wizzup> maybe try that first
<sicelo> it is the mobian kernel ... just not the actual binary, because theirs (including pmOS) expects an initramfs, so they haven't built in stuff like SD card support, etc.
<Wizzup> ok
<Wizzup> there might some trickyness there, like certain things having to be built in
cockroach has joined #maemo-leste
lolcat has quit [Quit: had to jack off]
<sicelo> yay! progress ... now x server is crashing. but at least that means we got somewhere
<Wizzup> cool :)
<sicelo> i think i must sleep now and see this next time :-)
<Wizzup> seems like you might need some xorg conf
<Wizzup> either that or our mesa lacks the driver
<Wizzup> but I don't think it does
<sicelo> we might be missing it. i was just doing a find, and this is what i can find:
<sicelo> sudo find . -name "*etnaviv*"
<sicelo> [sudo] password for mobian:
<sicelo> ./usr/lib/aarch64-linux-gnu/dri/etnaviv_dri.so
<sicelo> ./usr/src/linux-headers-5.10.0-28-common/include/uapi/drm/etnaviv_drm.h
<sicelo> ./usr/src/linux-headers-6.1.15/include/uapi/drm/etnaviv_drm.h
<sicelo> altough i think i saw it in the sources. maybe we don't have config option to actually build it
<sicelo> i.e. mesa
<sicelo> ah, the first one is from mesa, so we have it