#Ken's Labyrinth

355 messages Β· Page 1 of 1 (latest)

surreal sorrel
#

Ken's Labyrinth is a first person game designed by Ken Silverman for DOS before he worked on the build engine for Duke3D. This game is now free and can run native on Linux (no need for DOSBox). Everything is here and ready-to-run.

Tested on:
βœ… RG351P/ArkOS
βœ… RG351P/AmberElec
βœ… RG351P/JelOS
βœ… RG351MP/ArkOS
βœ… RG503/ArkOS
βœ… RG503/TheRA
β˜‘οΈRG353M/ARKOS
βœ… RG353P/ArkOS
βœ… x55/JelOS

Controls (2 Joysticks)

D-Pad = Move/Turn (Tailored to navigate menus, too)
Left Thumbstick = Move/Strafe
Right Tumbstick = Turn/Stand/Crouch
L1 = Run
L2 = Esc
R2 = Enter
R1 = Shoot
A = Cycle Weapon selection
X = Use/Action
B = Additional Shoot
Y = Strafe Modifier

Controls (1 Joystick)

D-Pad = Move/Turn (Tailored to navigate menus, too)
Left Thumbstick = Same as D-Pad
L1 = Run
L2 = Esc
R2 = Enter
R1 = Shoot
A = Cycle Weapon selection
X = Use/Action
B = Stand (Move up)
Y = Strafe Modifier
Left Thumbstick button = Crouch (Move down)

kenslabyrinth.jpg
olive sinew
#

<@&1123159718874058882>

#

@surreal sorrel

export LD_LIBRARY_PATH=$GAMEDIR/gl4es:$GAMEDIR/sdl12-compat:$GAMEDIR/lib32:$LD_LIBRARY_PATH```
#

what's with all the lib folders

#

ususally we just use the libs/ folder

#

does it use gl4es?

#

ah yeah

#

May I ask why the game is compiled in armhf?

#

this should really only be the case for box86 games

#

so you put gl4es and sdl2 compat libs in one folder (same architecture) anyway

#

but will wait until i get the answer for the 32 bit part πŸ˜›

lusty epoch
#

RG353v ark seems to be running very odd game lol

olive sinew
lusty epoch
#

Yep

olive sinew
lusty epoch
#

And I forgot the password thought it was default turns out I changed it

marsh grove
#

passwords? f_TurtleThink

olive sinew
marsh grove
#

ΰ² _ΰ² 

lusty epoch
olive sinew
#

...

#

πŸ˜„

marsh grove
#

You can reset it

#

@lusty epoch ssh-keygen and ssh-copy-id are your friend

lusty epoch
#

?

olive sinew
marsh grove
olive sinew
#

@marsh grove else you give me the ldd --version of ark please πŸ˜„

marsh grove
#

looks

#

my rg353v is too far away

#

its like 1m away

#

nvm, the child handed it over

# 
ldd (Ubuntu GLIBC 2.30-0ubuntu2.2) 2.30
Copyright (C) 2019 Free Software Foundation, Inc.
This is free software; see the source for copying conditions.  There is NO
warranty; not even for MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.
Written by Roland McGrath and Ulrich Drepper.
lusty epoch
#

Now to find out how to reset it lol

marsh grove
#

Configuration -> Change Password

lusty epoch
marsh grove
#

lmao

#

okay ...

lusty epoch
#

ark@rg353v:~$ ldd --version οΏ½οΏ½οΏ½οΏ½οΏ½οΏ½οΏ½οΏ½οΏ½οΏ½οΏ½οΏ½
ldd (Ubuntu GLIBC 2.30-0ubuntu2.2) 2.30
Copyright (C) 2019 Free Software Foundation, Inc.
This is free software; see the source for copying conditions. There is NO
warranty; not even for MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.
Written by Roland McGrath and Ulrich Drepper.

olive sinew
marsh grove
#

you could've made a port to reset the password

lusty epoch
#

Man I need sleep

lusty epoch
olive sinew
marsh grove
#

Then don't

#

πŸ˜„

lusty epoch
#

Oh no why that ?

olive sinew
#

game devs won't always allow compiling on old ass libs πŸ˜›

#

So at the moment we have to uninstall the os packages and compile them ourselfes

#

to get newer versions

#

amber and jelos are newer but ark is not πŸ™‚

marsh grove
lusty epoch
#

Guessing Christian no want to update ?

olive sinew
marsh grove
#

just so you know, glibc can reference up to 200 or so shared libs and they all have to version match πŸ˜„

#

so you cant include it

#

BUT

#

there is an alternative if you have some free time

olive sinew
#

build my own os?

marsh grove
#

Oh yeah that too

olive sinew
#

πŸ˜„

marsh grove
#

or you make your own runtime with all the shared libs

olive sinew
#

Portmaster OS

#

*based on ubuntu 22.04

marsh grove
#

you can do it

#

maybe fork JELOS

lusty epoch
#

Lol

olive sinew
#

and don't want pipewire

#

πŸ˜„

marsh grove
#

im not making a launcher

#

fuck off

#

πŸ˜„

#

❀️

wooden wing
marsh grove
#

πŸ˜„

wooden wing
#

yeah, unsuprisingly while it works fine in arkos (duh) it crashes in emuelec and I suppose elsewhere as well

olive sinew
marsh grove
#

MinUI ?

olive sinew
marsh grove
#

oh

#

its been a long day

#

πŸ˜„

wooden wing
olive sinew
full surge
#

Is Arkos dieing off slowly or something?

olive sinew
#

Was never state of the art in terms of cutting edge updates πŸ™‚

#

Stability vs cutting edge libraries with no direct benefit in emulating

full surge
#

πŸ‘

full surge
olive sinew
olive sinew
#

You have the same everywhere

#

like windows 7 -> windows 10

#

at some point you have to leave them behind

#

πŸ˜„

lusty epoch
#

You mean I'm gonna have to make a new sdcard up running jelos ? I keep seeing people saying when it updates it breaks things be it a emulator or portmaster ect lol

olive sinew
#

but all user error

lusty epoch
#

Dunno seen a few things online

#

Also I like being able to pop card out and drop in reader to copy stuff from backup of Roms and port folder on my pc

#

Can portmaster on jelos load it's ports from second card slot or does it have to be main ?

lusty epoch
#

Don't worry tested it my self yeppers it works okay that makes things easier

ornate ember
#

Or the audio on the gmloader.
That is probably the main problem of being a lot less LTS than arkos lol

surreal sorrel
#

@olive sinew The 32 Bit ARM executable I'm going to come clean, I didn't compile it, I took it from a zip where it was already prebuilt. I don't have a problem changing this, of course and compiling an aarch64 build of it. Also, the three lib folders, I hope I'll never have more than 3. I only like keeping gl4es and sdl12-compat 'out-on-display' so it's clear what it's working with, but I also don't have a problem moving everything into just the one lib folder if it's too ugly.

surreal sorrel
#

I see on the page that there's a build for gles. I'm going to play around with that later to see what that does.

olive sinew
#

because most cfws already dropped support for it

#

only if no other way around it

#

we already converted all 32 bit apps except gmloader and box86

#

the libs folder you can do how you like for me it saves some time just putting it all in one folder πŸ™‚

ornate ember
surreal sorrel
olive sinew
surreal sorrel
#

Anyhow, I'll be doing TG with fam and I'll be back to compile a new binary and combine the libs for us.

surreal sorrel
#

So I've found a few different sources - one newer version of this very app that uses SDL1 & GL, another that uses GLES (which I can't compile atm), and an SDL2 version that compiles and segfaults. I don't know how far I wish to go with this or if it's not going to bother anyone that I just make the aarch64 binary and pass it through sdl12-compat and gl4es and call it a day. I could try things with the source code, but I'm no master programmer and I could easily spend many fruitless hours not having a working build afterwards. I don't mind a challenge, but let me know what you all think.

ornate ember
#

sdl12 compact seems to perform a bit slow sometimes with arkos/amber, fixable on some devices with a trick. at the same time probably this game is really low on resource required, so if after some test works good everywhere i would call it a day too

surreal sorrel
ornate ember
#

probably clusterfucked more than needed i guess lol

surreal sorrel
#

Converting a surface to a texture, passing the texture to the renderer, then renderpresent every frame...

ornate ember
#

that said, sdl12 is not low perf, just happen sometimes with some games when using them

#

like some zelda port in experimental

surreal sorrel
#

Gotcha. I've had pretty good luck with the sdl12-compat wrapper, but it's not uncommon to have a game that just doesn't like it.

ornate ember
#

sort of, more a sdl2 version and a game to be precise ahaha

#

more weird than ever

surreal sorrel
#

oh wow

#

What caught my eye in the other sources that I liked was an added 'cycle-weapons' button so I don't have to map 3 buttons to switch weaps. I'd really like to implement that so it can favor a limited number of buttons.

ornate ember
surreal sorrel
#

right

ornate ember
#

definitely comfy for a controller btw lol

surreal sorrel
#

I just found out something else while chatting with ya. The new source I just compiled (the new aarch64 shitz) runs hella better when I switched it to software rendering (this game was software render based in the old days anyways).

#

I think I'm going to skip the GL side of things and see if I can bring over the cycle weapons feature.

#

The guys have been working on a tool to get the screen resolution of the device. I'm thinking about using it to change the res in the settings.ini file (if I have to do it this way, that is). What's the proper usage? (i.e. Is it included in portmaster, do I include device_info.txt in the gamedir and call it from there, if it's in PM do I call it from the PortMaster dir or does it already do this via control.txt...?)

ornate ember
ornate ember
#

i'm kinda good at mixing code doggokek

surreal sorrel
ornate ember
#

sure, for a similar thing guess it's not terrible lol

#

i mean, it's more port the logic than find how to do it

surreal sorrel
#

@ornate ember I think I might need a hand. Here's the source I'm looking at and the code to change weaps is in lab3d.c starting after line 468

surreal sorrel
#

This is the SDL2 version I was comparing it against where the weapon cycle was added, but just enough of the code was changed that I can't decipher what to do with it. This lab3d.c after line 955

ornate ember
#

Okay, thx

#

If I can I give a look later

#

Worse scenario ever I guess we can recreate a new script that does this

#

Lol

full surge
#

β˜‘οΈRG353M-ARKOS
looks great but wanna force 640.
Is left ana supposed to raise and lower character view point? Odd controls as I've never played this

surreal sorrel
# full surge β˜‘οΈRG353M-ARKOS looks great but wanna force 640. Is left ana supposed to raise ...

Yeah, I wanted to keep it so that single analog devices can still work. It's a simple game and there are no dedicated strafe left/right buttons. The up and down work like stand and crouch. I haven't played enough of the game to know if moving up and down is required. If tekken can add the weapon cycle button that'll free up two "button slots" which will help a lot. I'm open for suggestions on configuring the controls differently. If you open the game menu and hit help, that'll show what controls it uses. I'll need a couple of letters anyway in case you want to save progress.

#

I can always use export TEXTINPUTINTERACTIVE="Y" for gptokeyb text entry, but most users don't seem to know it exists or how to even use it.

#

You can also force the 640x480 option by editing the settings.ini and the res is at the very top. When I recompile the new one I already plan to have it set to 640x480 and sdl12-compat will scale it on lower/higher res screens from there anyway.

#

It'll scale perfectly on 640x480 screens, but this was never a high-res game in the first place πŸ˜›

full surge
surreal sorrel
#

I've attributed the slow performance on my RG351P to be the internal res was set rather high. It runs great even in GL(ES) after putting the resolution at an appropriate level. I'm still going to try a few things. Let me know if you guys have a preferred control scheme over the one I set.

ember coyote
#

won't run on rg351v (amberlec) -- ./ken: error while loading shared libraries: libbsd.so.0: cannot open shared object file: No such file or directory

ornate ember
#

i should have it somewhere

#

not sure is the right version but lemme see

#

need rename obv

ember coyote
# ornate ember

thanks ... but -- ./ken: error while loading shared libraries: libbsd.so.0: wrong ELF class: ELFCLASS64

ornate ember
#

oh it's 32 bit

ember coyote
ornate ember
#

also, i figured out why didn't work the compiling

#

i'm using arm64 doggokek

full surge
#

There's a few newer fps that are made to look super similar to this game. Such a sought after game style for fps'ers

#

...and of course, the dungeon lovers

surreal sorrel
#

I have an update. I've managed to add controls to one of the builds and I've compiled said build into arm64 (I do this when I can, but y'know). It also has a configuration for single joystick and dual joystick setups, too now.

#

Controls (2 Joysticks)

D-Pad = Move/Turn (Tailored to navigate menus, too)
Left Thumbstick = Move/Strafe
Right Tumbstick = Turn/Stand/Crouch
L1 = Run
L2 = Esc
R2 = Enter
R1 = Shoot
A = Cycle Weapon selection
X = Use/Action
B = Additional Shoot
Y = Strafe Modifier

Controls (1 Joystick)

D-Pad = Move/Turn (Tailored to navigate menus, too)
Left Thumbstick = Same as D-Pad
L1 = Run
L2 = Esc
R2 = Enter
R1 = Shoot
A = Cycle Weapon selection
X = Use/Action
B = Stand (Move up)
Y = Strafe Modifier
Left Thumbstick button = Crouch (Move down)

#

tekken is still working on getting the GLES version up and going which would be the bees knees if he can get that one to work, but if not, this build will probably suffice.

surreal sorrel
#

I'm also interested to know if this will work with EmuElec if anyone wishes to test 😎

surreal sorrel
#

@olive sinew Hey, bro. What do you think? Should I leave it in 640x480 and have it just scale (which for the most part seems fine) or do you think it would be cooler to source device_info.txt and sed the native resolution of the device into the settings.ini so it fills the screen?

olive sinew
#

But now that we soon can use device_info why not use it

#

So it will always be filled no matter the resolution

marsh grove
#

i was thinking, since no major bugs in the gui i might just send out the new version ... see what breaks. πŸ™ˆ

#

before i add the stuff tekken wants added

#

then we can use device_info.txt

olive sinew
surreal sorrel
marsh grove
#

use chatgpt πŸ˜„

#

its great at sed

surreal sorrel
#

That new PortMaster GUI is friggin' killer. I'm thinking about adding a Doom theme to it.

surreal sorrel
marsh grove
#

yeah

surreal sorrel
#

I could totally do that!

surreal sorrel
#

That's nice. I just tested it and it worked! Before I go too crazy, I'll drop the sh here so you can tell me if I 'over-engineered' this.

marsh grove
#

what happens when you run it twice? f_TurtleThink

#

maybe you could have a template.ini -> sed it into -> settings.ini

surreal sorrel
#

Seems to behave. Once that line is changed I don't think sed will touch it again. My settings.ini remained set at 480x320 after launching it the second time. It's originally set at 640x480 in the settings.ini that's in the package.

marsh grove
#

what happens if you move the files to a new device after it has changed the resolution once

surreal sorrel
#

I added a check if it detects a resolution width other than 640 to make the alteration, but I'm thinking that might not be necessary.

surreal sorrel
#

I think sed can only change the line once.

marsh grove
#

or if you have a template.ini, and copy it and adjust the values, rather than modify in place

surreal sorrel
marsh grove
#

hrmmmm

surreal sorrel
#

It wouldn't bother me per se

marsh grove
#

okay

#

if someone copies it over they can just reinstall the port, that should restore the original settings.ini

surreal sorrel
#

This is true, too

#

But I like your idea

marsh grove
#

i am?

surreal sorrel
#

derp

marsh grove
#

πŸ˜„

surreal sorrel
#

I think we're safe to do the template.ini. I just opened up the source code to see what these numbers are and they're just this in this order:
inputdevice (which is the keyboard)
resolutionnumber (which is a preset, but won't be used)
fullscreen
nearest (filter)
music (on)
sound (on)
keydefs (controls, this might be the only concern, but hopefully my settings are agreeable)
sound volume
music volume
cheats (off)
channel (stereo)
gammalevel (default)
soundblock (not sure what this does, but I never messed with it)
timing (left default)
texturedepth (default to whatever software mode uses)
musicchannel (stereo)
scaling (default)
renderer (This wouldn't matter if it got changed since I altered the source to run in software mode no matter what the setting)

#

The only thing might be the controls, but I'm not for certain anyone could bother to change them I don't think.

#

They'd have to run setup manually in order to do that, actually.

#

Should I just make a copy of the settings.ini and then copy template.ini over settings.ini before making the change with sed?

olive sinew
#

Whatever works best

surreal sorrel
#

True

#

New flavour. I even deleted the original settings.ini to make sure that template.ini actually gets copied (if it didn't I would have been taken to the setup screen instead of the game). I'm curious to know what this might look like on the X55 now.

πŸ“Ž kenslabyrinth.zip
#

Kinda wished I had one to test lol.

#

@marsh grove No joke. Chatgpt knew exactly what syntax to give me. I guess I'll need to add to the json Porters: @chat.openai.com

marsh grove
surreal sorrel
#

lol

surreal sorrel
#

I keep tossing around a solution for the RG353P and the bumpers and triggers being swapped for controls - esp for first person titles. I'm thinking about creating a 3rd gptk controller config file and having it check for the RG353P specifically, then setting the GPTOKEYB envar to that file with the L1/L2 and R1/R2 swapped for it. On that note, wasn't there another device that has the bumpers and triggers laid out just like this?

olive sinew
#

from portmaster

#

maybe the affected person can veifify via sdljoytest

surreal sorrel
#

Nah, it's like this for every game. It's a device layout choice. The bumpers and triggers aren't swapped on the RG353P per se, rather we've been accomodating the trigger and bumper locations for all the other devices resulting in the controls being backwards on devices that are properly laid out. For instance, the triggers are on the inside of all these devices - R2 and L2, the triggers, on the RG351P, RG351MP, RG503, etc. etc. are on the inside which are not easily reachable and so those buttons have been chosen to be mapped to the bumpers instead of the triggers for easy access which then leads them to being wrongly mapped on the RG353P which has those buttons located in the correct places.

#

It's a physical placement issue, not a logical one.

olive sinew
#

oh

surreal sorrel
#

Not that it couldn't be set that way intentionally in the gamecontrollerdb.txt and have them swapped there, but then it'd be wrong for everything that's already set that way for, say, retroarch.

olive sinew
#

Yeah you could do with device info and a simple sed command

surreal sorrel
olive sinew
#

so a single liner to swap around whatever is responsible

surreal sorrel
#

To make my life easy when I do it for games on my RG353P, I open the gptk file and literally replace L1 with L2, L2 with L1, and then the same for the R's and save it.

#

It's easier than trying to move around the keyboard keys they're set to.

olive sinew
#

or 2nd gptk would also work I guess but if you have a 2nd device where its the case it gets ugly πŸ˜›

surreal sorrel
#

Right. It'd be something along the lines of if Device = RG353P then
sed L1 = mouse_left \ L2 = mouse_left 2analog.gptk

olive sinew
#

Yep

surreal sorrel
olive sinew
#

yep

#

that way my idea behind it

#

expandable

surreal sorrel
#

devicewithtriggers.gptk

#

Which devices have the actual trigger layout like this? I think a few PowKiddy units are like this, but I'm not sure if the powkiddy units have the button numbers like this, so I don't want to assume that 5 devices are matching and find out they're not.

surreal sorrel
olive sinew
#

R2 is trigger

surreal sorrel
#

If you play on it, do you have to hit the bumper to fire or does your trigger fire in Ken's Lab?

olive sinew
#

Neither

#

I never play fps on consoles

#

πŸ˜„

surreal sorrel
#

ahahaha I got ya

olive sinew
#

But i can test of course πŸ˜›

surreal sorrel
#

I know what you mean, though. Keyb and mouse ftw (which I do agree).

olive sinew
#

R1 so the button

#

not the trigger

surreal sorrel
#

I suspected such

olive sinew
#

But for me i would just use what the game suggest

#

its not more comfortable using the trigger πŸ˜„

#

Both are click buttons πŸ˜„

surreal sorrel
#

To each their own, as they say. It's not the end of the world, but I could just leave well enough alone.

#

If someone really wants to have it the other way, they can always edit the gptk

#

(that rhymed)

olive sinew
#

now one the 552 for example where they're not stacked swapped r1 and r2 is a big problem

#

because you can't reach r2 while normally playing

#

comfortably

#

on my x55 right now both buttons felt good

#

on my 552 my hand gets cramped if i have to use the other one for shooting

surreal sorrel
#

Hmm.. wouldn't opting out the RG552 still result in the shoulder button being fire? Or does the RG552 have something a tad different going on?

olive sinew
surreal sorrel
#

I've only seen a 552 in person once because a lad brought one into the shop for me to fix because the power button broke off into the system.

olive sinew
#

classic

surreal sorrel
#

I wasn't able to fix it

olive sinew
#

Same problem applies to 353 devices I guess

#

or 351p

surreal sorrel
#

The solder joints were too clean a break

olive sinew
#

all fps on these devices idk

surreal sorrel
#

I guess we could just leave it be.

#

Less work the better I suppose, what do you think?

#

I might do this for myself, but y'know

#

twas a thought

#

πŸ€”

olive sinew
#

I would leave it and put a note in the keys can be swaped in the gptk

#

done πŸ˜›

surreal sorrel
#

Fair enough

#

Like you said, buttons be buttons

surreal sorrel
#

@olive sinew I went ahead and did something for the lulz

surreal sorrel
#

This one picks a custom gptk if the x55 or the RG353P are detected.

#

It doesn't work for me because I'm running the 353M image of ArkOS on my RG353P and so device_info obv detects it as a 353M instead. It should work on the 353P if running JelOS or some other FW. If only CH was awesome enough to make a dedicated ArkOS image for the 353P πŸ˜› . Kinda wished there was a way I could talk him into it, but it is what it is.

ornate ember
#

Only the p?

#

This lucky bastard with normal triggers

#

Jokes aside, that's a nice touch imho

surreal sorrel
surreal sorrel
#

tekkenfede and I decided we'll go ahead and ship it in its current state. If we ever get the GLES flavour working, we can just do that at a later point like an enhancement/upgrade.

marsh grove
surreal sorrel
# marsh grove they're basically identical?

The RG353M image works perfectly logical-wise because the internal hardware is indeed indentical, but the physical layout is different. Since CH doesn't have a RG353P image and I use the RG353M ArkOS image to get Ark on my 353P, this in turn causes device_info.txt to return it as the RG353M (this info is retrieved from ~/.config/.DEVICE and /sys/firmware/devicetree/base/model - which you already knew. Additionally, /sys/firmware/devicetree/base/model isn't actually a file that can be modified, but instead retrieves its information containted in the .dtb file in /boot and editing it will only change its contents for a split second before a refresh and re-read of the /boot/xxx.dtb file).
Most of the FPS games have the buttons mapped to the bumpers on all of these devices since they're easier to reach and then the secondary controls which would ordinarily be on the bumpers get mapped to the triggers instead respectively.
This in turn causes the controls to be swapped on the x55 and the RG353P because the buttons are now located in their correct positions. Changing the gamecontrollerdb.txt would work here, but then it would swap the buttons on ALL the other units sharing the retrogame-joypad controller.
Furthermore, since you did what you have with the device_info.txt filling in the DEVICE_NAME envar - this made it worth my while to make a change for those using ArkOS with the RG353P using the RG353M image - change the entry in ~/.config/.DEVICE to read RG353P instead of RG353M (which gets overridden by /sys/..../model anyway) and then change out the /boot/rk3566-OC.dtb file with one that reports a RG353P instead. How did I get this rk3566-OC.dtb file I hear you ask? Simple. I used the exact file from the RG353M image, just changed the entry in it using a HEX editor.

marsh grove
#

i see

#

you can just say "controls are better if mapped specifically for the rg353p" πŸ˜„

surreal sorrel
#

Sorry. Got carried away. Sometimes I feel like if I don't explain things thoroughly that it leaves a lot of unanswered questions. It's not you, of course - I've always been like that.

#

I guess I also get a little excited when I reverse engineer something that I learn it without being taught and so I have to share it with the world as if I'm trying to impress someone.

marsh grove
#

Its cool πŸ˜„

surreal sorrel
#

P.S. sometimes it works πŸ˜„

marsh grove
surreal sorrel
#

LOL I getcha

marsh grove
#

πŸ˜„

#

does it source the ~/.config/.DEVICE first?

surreal sorrel
marsh grove
#

oh yeah it does, neat

#

so you can just override it that way? πŸ˜„

#

excellent, how serendipitous

surreal sorrel
#

More or less. If I only edited the dtb file it would've worked due to the script's "order of operations".

#

I haven't actually tried it to see if that's factual, but that's what I gather.

marsh grove
#

Oh does it get re-written on every boot?

surreal sorrel
marsh grove
#

~/.config/.DEVICE

surreal sorrel
#

~/.config/.DEVICE once edited actually stays. It appears to just be a simple text file and nothing more than that.

marsh grove
#

Okay, because i can just add something like ~/.config/.CUSTOM_DEVICE if it does. So the workaround long term is to set it in ~/.config/.DEVICE ?

surreal sorrel
#

That's a good question, actually. I'm not certain that the .DEVICE file isn't just created and 'planted' by the firmware dev.

#

I also believe this to be the case since, for example, all of the 353 models use the exact same board, I'm not even sure there's a way to detect which unit that board is being installed in or how it would 'know'.

marsh grove
#

353v is slightly different i think, a mono speaker?

#

other than that is identical

surreal sorrel
#

I'm also not fully confident in that since JelOS has one image for multiple devices and it somehow knows which unit to assign which dtb.

marsh grove
#

hrmmm

surreal sorrel
marsh grove
#

it designates it as RK3566

#

?

surreal sorrel
#

Right. I saw your device_info pick up JelOS on RG353P when another tested it. The JelOS image for that unit also covers like 4 other models, too. I'm not sure how it 'knows' after imaging.

marsh grove
#

can you run the hardware dump script on your rg353p with jelos?

surreal sorrel
#

Sure.

marsh grove
# 
wget "https://raw.githubusercontent.com/kloptops/harbourmaster/main/tools/dump_info.py"
python3 dump_info.py > slayer366_353p_jelos.txt
#

πŸ˜„

surreal sorrel
#

You got it. Gimme a few since I've been juggling microSD cards.

marsh grove
#

thats fine

#

a label maker is a good idea btw πŸ˜„

surreal sorrel
#

lol

#

I used a marker to put a dot on the one I have Jel for my RG351P on. These things are just too damn small, but I still like 'em LOL.

surreal sorrel
#

JelOS picks between one of six dtb files within the boot folder for six different devices. I'm not sure how it knows which dtb file to load.

marsh grove
#

magic, it seems πŸ˜„

surreal sorrel
#

I'm tellin' ya πŸ˜›

#

All 6 of those dtb files remain in the boot partition even after the phase where it expands the partitions and whatever else the first steps are set to run on first launch.

#

I'm used to seeing a preset boot.ini that has a fixed dtb file picked out for that image, but no such ini file exists in the JelOS boot partition. I'm scratching my head a bit on this one.

#

Perhaps brookystech knows how it's set up?