Replies: 6 comments
-
who wishes to test> the commit have been made on my fork so have fun seem to be stable |
Beta Was this translation helpful? Give feedback.
-
I have started some testing the Jammy Release Installed on my arm64 chromebook with Developer mode Crostini available. case $SUITE in |
Beta Was this translation helpful? Give feedback.
-
This the update mate desktop targets with Jammy and xiwi runs super nice, some of the targets need to be updated the crouton image is on a google drive I did -r jammy -t mate, audio, xiwi,touch I have not found a web broswer yet this is one a arm64 lenovo with crostini enabled My older lenovo amd64 will not install jammy stop after stage 1 extractor fails debootstrap fails Im sure this can be address i have zstd have fun |
Beta Was this translation helpful? Give feedback.
-
I'm missing something. When I download and make crouton_jammy executable, I get a message "Refusing to exec...from noexec mount." Maybe I downloaded incorrectly. I'd like to try this out, because all of my attempts to install jammy with the official crouton version have failed at launching X11. My focal chroot with xfce and mate both load without any trouble. |
Beta Was this translation helpful? Give feedback.
-
The existing crouton is in a holding pattern so as to support EOL devices. David said the testing labs are no longer available, so you can't just go making changes willy nilly to the existing repository. I believe this is the proper approach. You don't need anyone's permission to fork crouton and make it work for modern Chromebooks. Currently, sudo is not available in the crosh shell, so the "standard" work around is to enter the chroot in VT-2, start SSH, then go to the crosh shell and SSH into localhost, and finally, kick off a desktop with some command, like sudo startxfce4. A more experimental approach is to install Chromebrew, then the crew_sudo package, which intercepts calls to sudo and makes it work once again in the crosh shell. Another wrinkle is that the security folder has to be made writable, or you can't complete an installation and launch a chroot. I've written a new how-to in the wiki, which shows the standard work around without the use of Chromebrew or other 3rd party tools: |
Beta Was this translation helpful? Give feedback.
-
who is the new fork if this is to remain static
2 votes ·
Beta Was this translation helpful? Give feedback.
All reactions