<apritzel>
"No official support" is still miles ahead of those vendor provided images
<aphorise>
So Focal or Bullseye whats the difference acctually
<Werner>
Focal is Ubuntu and Bullseye is next Debian ;)
<apritzel>
what he said ^^^^
<aphorise>
Bullseye it is that
<aphorise>
thanks
<aphorise>
So do I boot off of USB / SD card and bpi-copy that img onto eMMC?
<aphorise>
is that bpi-copy just dd?
<Werner>
Armbian comes with a script called nand-sata-install that will do this job for you
<Werner>
But you do not have to copy your system to emmc, you can simply leave it on sd as well
<aphorise>
But I'd like to have it boot off of the 8gb emmc
<aphorise>
its a bit faster
<Werner>
up to you :)
<apritzel>
aphorise: mainline can boot the same image from SD card or eMMC alike, it's just those stupid BSPs that need different images for that
<apritzel>
so I recommend dd'ing to an SD card, boot it, try it, then transfer to the eMMC
<aphorise>
Thats a good idea too but I have to get the old laptop out for the SD drive writer and I'm too lazy - so going to play it wild
<aphorise>
ryncing image already and just booted off of their old image from SD card
<aphorise>
Didnt boot though
<aphorise>
just black screen - no activity lights
<Werner>
serial console handy?
asdf28 has joined #linux-sunxi
<aphorise>
How to serial interface? - with just power I can do that?
<Werner>
It is always wise to have an USB UART adapter laying around when tinkering with SBCs. It is great help to debug things when you cannot get either network or display to work
tuxillo has quit [Remote host closed the connection]
<aphorise>
Oh wait it came up eventually with "Loading Please wait" and a few other lines in 1080 :-) but nothing else its kind of hung
<aphorise>
USB UART? - Is that just a 4-3/pin to USB?
<Werner>
First boot always takes longer because the filesystem expands itself across the whole sd card. depending on quality and size this can take a while
<aphorise>
I booted off of eMMC - I'll leave it for another 20 minutes but doesnt seem to be doing anything.
<Werner>
It should not take that long as long as it was no 1TB sd card or something :)
<aphorise>
Last message was: "... Scanning Brfs filesystems."
<Werner>
32GB U3 takes a few seconds for me as comparison
<Werner>
Each board usually has an accessible serial console via UART pins that allows debugging down to the boot loader. Also kernel errors will be posted there
tuxillo has joined #linux-sunxi
<Werner>
Dont know where it is located on your partiuclar board but I assume you will find info on wiki for debug ttl uart and needed baud rate
<gediz0x539>
hi. any guide on making qt work utilizing mali on mainline? either proprietary or lima would be ok.
<gediz0x539>
I could successfully probe mali on 5.8 kernel using sunxi-mali repo of mripard and bootlin/mali-blobs but I get that infamous 0x3003 EGL_BAD_ALLOC while trying to launch an example qt app
<gediz0x539>
I'm not sure I could set DRM properly. How to tell?
<gediz0x539>
I can modprobe sun4i-drm but the only thing I see on dmesg about DRM is "[drm:drm_core_init] Initialized", despite setting "loglevel=7" and "drm.debug=0xff"
<asdf28>
i think the drm driver should create a device in /dev/dri
<gediz0x539>
I may say something stupid, but I could not see /dev/dri until I enable LIMA on kernel config
<gediz0x539>
and could not enable mali when I've enabled lima
<asdf28>
yes you need to blacklist lima
<asdf28>
but you can use either one
<asdf28>
just not both
<asdf28>
no, wait
<gediz0x539>
so /dev/dri is not removed when I blacklist lima?
<asdf28>
i don't think you can use the ARM blobs using lima
<asdf28>
at least i did not get that to work
<asdf28>
no
<gediz0x539>
oh okay then let me try this. thanks
<gediz0x539>
it's just more than complicated. it does not seem like something easy to comprehend in a short while.
<asdf28>
it's extremely complicated, yes
<asdf28>
and the error messages are often unhelpful
<gediz0x539>
yep
<asdf28>
for example, i've had EGL_BAD_ALLOC when it just couldn't find the monitor... and such things
<gediz0x539>
wew
<gediz0x539>
btw, another thing to ask, is it necessary to add something like "panel" to dts to make drm work properly?
<asdf28>
what system are you using? i mean what distro?
<gediz0x539>
trying to compile it with buildroot right now
<asdf28>
sorry, i don't know this setting
<asdf28>
but i never had to change anything in the dts to make it work
<gediz0x539>
br 2020.11.x, sun5i-a13-olinuxino-micro and u-boot 2020.10 if it matters
<gediz0x539>
I had to add mali node to dts because mali was not included in sun5i-a13.dtsi
<asdf28>
you should also check if you have a /dev/mali
<gediz0x539>
if I can somehow make it work properly, I'd like to submit it. I just do not want to cargo cult and send some copy/pasted thing.
<asdf28>
after loading the mali driver
<gediz0x539>
fortunately /dev/mali is there
<asdf28>
that
<asdf28>
's good
<asdf28>
:)
<gediz0x539>
thanks :)
<asdf28>
what platform will you be running QT on? x11, wayland or framebuffer?
<gediz0x539>
currently trying for framebuffer but if it's easier to do on x11, I'd prefer it. or wayland.
<asdf28>
would be very interesting if you can make it work
<gediz0x539>
I just feel like it'd cause more abstraction layers/bloat to start with x11. not to mention that I do not know how to properly configure an x server
<gediz0x539>
and I have basically zero knowledge about wayland
<gediz0x539>
I hope so...
<asdf28>
yes i also don't know anything about it
<asdf28>
wayland
<asdf28>
because i found it too complicated
<asdf28>
i never got it to work when i wanted to try it
<gediz0x539>
I can relate
<gediz0x539>
booting an archaic twm/x11 took some days for me. and x11 seems to have more info around the interwebs
<gediz0x539>
I just cannot think about wayland :D
<asdf28>
if you run a qt app in framebuffer, how does that look like?
<asdf28>
do you still have a window title bar at the top?
<gediz0x539>
I could actually make it work on legacy kernel
<gediz0x539>
using eglfs
<gediz0x539>
it was a basic QML app, there were no window bars
<gediz0x539>
but you can have if you want using some custom widgets, iirc.
<asdf28>
interesting
<gediz0x539>
yes. it was kinda easier.
<gediz0x539>
btw I've enabled lima and got some stack traces on dmesg
<gediz0x539>
I mean I executed "make clean" on buildroot directory, which completely wipes out staging and target directories
<asdf28>
oh, okay
<asdf28>
sorry, i do not know about buildroot
<gediz0x539>
my fault, I had to provide ctx lol
<gediz0x539>
btw it probably depends on the case but using ccache sometimes reduces compile time about 50%. which is great.
gaston1980 has joined #linux-sunxi
t3st3r has quit [Remote host closed the connection]
t3st3r has joined #linux-sunxi
tis_me has joined #linux-sunxi
cmeerw has quit [Ping timeout: 272 seconds]
mps has left #linux-sunxi [#linux-sunxi]
tis_me has quit [Quit: Leaving]
victhor has joined #linux-sunxi
netlynx has quit [Remote host closed the connection]
asdf28 has quit [Ping timeout: 265 seconds]
<gediz0x539>
and there some errors I have never encountered before. "drmModeGetResources failed (Operation not supported)" and "Cannot create window: no screens available"
popolon has quit [Quit: WeeChat 3.0]
gaston1980 has quit [Quit: Konversation terminated!]
lurchi__ has quit [Quit: Konversation terminated!]
lurchi_ has joined #linux-sunxi
qschulz has quit [Read error: Connection reset by peer]