default enabled upstream at fedora, make a key and it works
default enabled upstream at fedora, make a key and it works
Lbasically editing the Containerfile and the system_files folder ?
Sdoes it not have username/password ssh? how do I go about making a key then?
Lif it's just stuff like installing and configuring another DE and thing like that I think it's manageable
Kit's configured by default to not allow that
Kyou can change it
Show?
Hi thought the VC was really cool @j0rge. i agree with pretty much everything you said. except i believe it could be even better then standard chromeOS. only a few years ago i was assisting my local high school and middle school and the process of managing the atomic chromeOS and all the bugs inside of it was insane. if anything happened if lets say the bluetooth or wifi broke or chrome decided to not work then the easiest solution was to literally reflash the entire operating system. i feel like ublue could solve that a lot if they could have a signed internal image with known working packages instead of praying google doesn't push out a broken update or it doesn't just break on it's own
K@antheas Next release has BMI323 and BMI150 blacklisted on ASUS images. I've also messaged Sentry about the kernel build options. That just leaves the patch in 6.7
K@CharlieBros ^
Aadding ayaneo air support right now
Auses the same driver
Kbeauty
Asame everything as ally
Ksame need to blacklist 150?
Ayep]
Kok, I'll just do that global then unless you know of something that *needs* 150
Kglobal meaning all *-deck images
Ai do not know of a device that uses bmi150 and would need hhd
Kand what's the product name of that Air device? I'll just add it now to be ready
Abut maybe theres an obscure one and it will break autorotation on it?
Aone sec
Athe bmi is "AIR Plus"
Admi*
CAnd what blacklisting those modules do for the Ally? Does it fix the sleep issues or that’s until 6.7 drops?
Ksleep is 6.7
Kfixes gyro
LI think I'm going to do the following :
- fork bazzite
- Add new variants for my version and a friend's version (I think sharing a repo would be easier)
- In the containerfile, at the end, include either his script or my script.
- Setup the repo so that customizations we add are separated into different scripts inside a new folder so wen can enable/disable/share them easily
- Maybe try to disable other unneeded variants in the github action's build.yml
LWould there be any downside to this setup ?
KThanks, that'll enable HHD now and also has a defined nested desktop resolution
Kand bmi150 is disabled on deck builds in favor of bmi323
Kjust the maintenance burden
Kit's certainly doable
LI think keeping all customization in scripts and not touching the containerfile except for the calls helps keeping maintenance low
Lwell thanks for the answers, I'll go set that up lol
S....so how do I set it so bazzite uses username/password ssh
TWhat do you mean by this? SSH should always require authentication
Snvm i figured it out
Sno i did not
Sso I used the deck to make an ssh key pair
Scopied the public key to my pc
Asudo nano /etc/ssh/sshd_config#PasswordAuthentication yesin case youre so inclined
Ai usually do it the other way where I disable it
Ahmmmm for some reason its enabled on my img
Agood news I was not hacked though!
Sit keeps saaying connection refused
SI litterally just made the key
Ldid you add it in your authorized_keys file ?
Sdid i do something wrong? how do I get it to work with my program (am using winscp)
Lon the deck ?
