Updates for UM41 #85
Updates for UM41 #85
Conversation
Deploying ultramarine-wiki with
|
| Latest commit: |
31601be
|
| Status: | ✅ Deploy successful! |
| Preview URL: | https://90e244a7.ultramarine-wiki.pages.dev |
| Branch Preview URL: | https://um41.ultramarine-wiki.pages.dev |
| @@ -10,4 +10,4 @@ import Alert from "../../../../components/Docs/Alert.astro"; | |||
| page is subject to change. | |||
| </Alert> | |||
|
|
|||
| Would use [StardustXR](https://stardustxr.org/). Our packaging effort can be found [here.](https://github.com/Ultramarine-Linux/stardustxr) | |||
| Would use [StardustXR](https://stardustxr.org/). StardustXR is fully packaged in Terra since Fedora 41 | |||
There was a problem hiding this comment.
stardust-server: terrapkg/packages#2048
PR still open
There was a problem hiding this comment.
stardust-server: terrapkg/packages#2048PR still open
Should be merged by UM41, gonna look at this later
| - 16GB of Storage | ||
|
|
||
| ## Minimum Requirements | ||
|
|
||
| These requirements are the **_bare minimum_** to run Ultramarine Linux. Using Ultramarine on a computer of this caliber will not be a good time. | ||
|
|
||
| - 1gb of RAM | ||
| - 64-bit processor (x86_64 **OR** aarch64) | ||
| - 10GB of disk space | ||
| - Dual Core 64-bit processor (x86_64 **OR** aarch64) |
There was a problem hiding this comment.
Why dual core here? It would run on single core
There was a problem hiding this comment.
just copied from recommended, i don't think a single core cpu has been made in the last 5 years
There was a problem hiding this comment.
These are the min requirements though.
| ## Ultramarine 41 | ||
|
|
||
| - 🔥 Switched to Readymade from Anaconda | ||
| - 🔥 Switched to Raspberry Pi Foundation Kernel |
There was a problem hiding this comment.
Add Pi/raw ARM images will be BTRFS
Can also include Chromebook change, will be worth looking at closer to release.
|
|
||
| ## Raspberry Pi 5 | ||
|
|
||
| <Alert type="info"> | ||
| This device type is still in the **Planning Phase**. All information on this | ||
| This device type is still in the **Testing**. All information on this |
There was a problem hiding this comment.
category not phase
| @@ -5,34 +5,34 @@ description: "Minimum Requirements for Ultramarine Linux" | |||
|
|
|||
| import Alert from "../../../../components/Docs/Alert.astro"; | |||
|
|
|||
| ## Recommended Requirements for Standard PCs | |||
| ## Recommended Specifications for Standard PCs | |||
|
|
|||
| These are our suggestions for the most basic (daily-driveable) system: | |||
|
|
|||
| - 4GB of RAM (8GB or more recommended) | |||
There was a problem hiding this comment.
| - 4GB of RAM (8GB or more recommended) | |
| - 4GB of RAM |
Adding (8GBs recommended) seems redundant since its the 'most basic' suggestion, and 4GBs ram will run the OS just fine for basic tasks.
There was a problem hiding this comment.
no, we suggest more storage here, and this is important information
| | Surface Go | No | Cameras and LTE will not work without Surface Kernel | ✓ | | ||
| | Surface Go 2 | No | Same as Surface Go | ✓ | | ||
| | Surface Go 3 | No | | | | ||
| | Surface Go 4 | Yes | UFS Storage, requires some manual intervention to get working | | |
There was a problem hiding this comment.
Manual intervention guide should be provided below this chart, along with any other manual workarounds needed?
There was a problem hiding this comment.
I would talk about what surface_aggregator is/how to use it
There was a problem hiding this comment.
Manual intervention guide should be provided below this chart, along with any other manual workarounds needed?
they should go to surface wiki imo, but maybe
I would talk about what surface_aggregator is/how to use it
I can make a mention
| @@ -55,9 +50,9 @@ These can be found in the [Raw Image](https://images.fyralabs.com/images/ultrama | |||
| it on another device. | |||
There was a problem hiding this comment.
Change raw images link to /41/
|
|
||
| Open your Edition's app store, on Flagship, GNOME, and Xfce, this is Software, on Plasma this is Discover. The upgrade should be in the updates section, simply press upgrade, wait for the packages to download, and reboot from the app store. | ||
|
|
||
| You may need to update your copy of Ultramarine 40 before the upgrade will become available. |
There was a problem hiding this comment.
Talk about/guide for UMhop/Pantheon upgrade path?
There was a problem hiding this comment.
we can make another page for that
| ## Ultramarine 41 | ||
|
|
||
| - 🔥 Switched to Readymade from Anaconda | ||
| - 🔥 Switched to Raspberry Pi Foundation Kernel |
There was a problem hiding this comment.
| - 🔥 Switched to Raspberry Pi Foundation Kernel | |
| - 🔥 Switched to Raspberry Pi Foundation Kernel | |
| - Raw/Pi images switched to BTRFS | |
| - Added WSL support |
|
|
||
| ## Raspberry Pi 5 | ||
|
|
||
| <Alert type="info"> | ||
| This device type is still in the **Planning Phase**. All information on this | ||
| This device type is still in the **Testing**. All information on this |
There was a problem hiding this comment.
category not phase
Co-authored-by: Owen Zimmerman <[email protected]>
|
|
||
| ## Raspberry Pi 5 | ||
|
|
||
| <Alert type="info"> | ||
| This device type is still in the **Planning Phase**. All information on this | ||
| This device type is still in the **Testing**. All information on this |
There was a problem hiding this comment.
| This device type is still in the **Testing**. All information on this | |
| This device type is still in the **Testing Category**. All information on this |
| @@ -5,34 +5,34 @@ description: "Minimum Requirements for Ultramarine Linux" | |||
|
|
|||
| import Alert from "../../../../components/Docs/Alert.astro"; | |||
|
|
|||
| ## Recommended Requirements for Standard PCs | |||
| ## Recommended Specifications for Standard PCs | |||
|
|
|||
| These are our suggestions for the most basic (daily-driveable) system: | |||
|
|
|||
| - 4GB of RAM (8GB or more recommended) | |||
| ## Ultramarine 41 | ||
|
|
||
| - 🔥 Switched to Readymade from Anaconda | ||
| - 🔥 Switched to Raspberry Pi Foundation Kernel |
There was a problem hiding this comment.
| - 🔥 Switched to Raspberry Pi Foundation Kernel | |
| - 🔥 Switched to Raspberry Pi Foundation Kernel | |
| - Raw images switched to BTRFS | |
| - Added WSL support |
| 2. Simply select "Other General Purpose OS" then your Ultramarine Edition of choice. | ||
| 3. Insert the storage device into your Pi and boot up! The root filesystem will automatically be expanded. | ||
| 4. You will be prompted to set up a user, do this and you're done!. | ||
| - Your storage device will need to be larger than 16GB (the image is ~15GB) We suggest 20GB so you have space for software. |
There was a problem hiding this comment.
Raw images consists of mostly blank space:
Maximum is around 7.1GB (plasma), final raw image size is 12.1 GB, 3.6 GB after compression, nowhere to 15GB.
If I understand this correctly, a system with 10 GB can install plasma with 3 GB to spare. This of course requires verifications.
If true, also edit rpi3 notes.
There was a problem hiding this comment.
compression doesn't matter here, we're decompressing, i swore they were like 12-15gb now, thanks for the correction
There was a problem hiding this comment.
The largest is 15GBs, the smallest is 8GBs. There is free space within those images but they still take up that much space once decompressed.
@madonuko didn't you have a way to shrink these sizes down? Especially the plasma one? If we can shrink down the plasma one, the next largest raw image is 12GBs.
There was a problem hiding this comment.
The largest is 15GBs, the smallest is 8GBs. There is free space within those images but they still take up that much space once decompressed.
@madonuko didn't you have a way to shrink these sizes down? Especially the plasma one? If we can shrink down the plasma one, the next largest raw image is 12GBs.
There was a problem hiding this comment.
You're showing imgs from 2 Aug, that's old as heck.
There was a problem hiding this comment.
Looks like the most recent KDE raw image is 13GBs.
There was a problem hiding this comment.
Wait that's x86, the ARM raw image is probably still 15, checking now.
| @@ -10,4 +10,4 @@ import Alert from "../../../../components/Docs/Alert.astro"; | |||
| page is subject to change. | |||
| </Alert> | |||
|
|
|||
| Would use [StardustXR](https://stardustxr.org/). Our packaging effort can be found [here.](https://github.com/Ultramarine-Linux/stardustxr) | |||
| Would use [StardustXR](https://stardustxr.org/). StardustXR is fully packaged in Terra since Fedora 41 | |||
| - See the [anywhere page](/en/anywhere/rpi) | ||
|
|
||
| ## Minimum Requirements for ARM Devices Using UEFI | ||
|
|
||
| - 64-bit processor (aarch64) | ||
| - 4GB or RAM | ||
| - 4GB of RAM | ||
| - 16GB of Storage | ||
|
|
||
| ## Minimum Requirements |
There was a problem hiding this comment.
This entire section should be moved up above rpi.
| 5. Run `dracut -f` to make sure the new kernel is installed as the initramfs. | ||
|
|
||
| 6. Exit the chroot and reboot! | ||
| Microsoft Surface support is provided in partnership with the Linux Surface team. |
There was a problem hiding this comment.
We only got permissions to use their provided software, we did not negotiate any partnerships afaik.
There was a problem hiding this comment.
it's probably okay to say but changing it is likely safer, just copied the copy from chromebook and pi
|
|
||
| ## Upgrading | ||
|
|
||
| Open your Edition's app store, on Flagship, GNOME, and Xfce, this is Software, on Plasma this is Discover. The upgrade should be in the updates section, simply press upgrade, wait for the packages to download, and reboot from the app store. |
There was a problem hiding this comment.
| Open your Edition's app store, on Flagship, GNOME, and Xfce, this is Software, on Plasma this is Discover. The upgrade should be in the updates section, simply press upgrade, wait for the packages to download, and reboot from the app store. | |
| Open your Edition's app store ("Software" on Flagship, GNOME, and Xfce; "Discover" on Plasma). The upgrade should be in the updates section, simply press upgrade, wait for the packages to download, and reboot from the app store. |
There was a problem hiding this comment.
neither of our options are very clear, i can just try again here
| - 🔥 Switched to Readymade from Anaconda | ||
| - 🔥 Switched to Raspberry Pi Foundation Kernel | ||
| - WSL Support | ||
| - 📦 Chromebook Images |
There was a problem hiding this comment.
| - 📦 Chromebook Images | |
| - 📦 Chromebook Images | |
| - 🛳️ `kcalc` in Plasma Edition instead of `kalk` | |
| - 📦 `mesa-va-drivers-freeworld`, `mesa-vdpau-drivers-freeworld` | |
| - 📦 [`umcli`](https://github.com/Ultramarine-Linux/um) (A CLI tool for managing an Ultramarine Linux system) | |
| - 🛳️ `fastfetch`, `nmtui` | |
| - 📦 Flagship: switch to `helium-gtk-theme` and `hydrogen-icon-theme` (instead of Fluent); `ptyxis` (instead of `gnome-terminal`) | |
| - 🔥 GNOME: remove `pop-launcher`, `qalculate`, [Pop shell extension](https://github.com/pop-os/shell) (`gnome-shell-extension-pop-shell`); add `geary` email client | |
| - 🔥 Plasma: switch from `ibus` entirely to `fcitx5`; remove excessive KDE apps |
There was a problem hiding this comment.
we always shipped kcalc, but i wanted to switch to kalk in this release, that's not really a change, other than that good
There was a problem hiding this comment.
Ah… that's why I didn't find it on my system…
Well people seem to like kcalc more, not sure
| - 📦 [System76 Scheduler](https://github.com/pop-os/system76-scheduler) (significantly better scheduling for low-end devices) | ||
| - 📦 [KWin Script for system76-scheduler Integration](https://github.com/maxiberta/kwin-system76-scheduler-integration) | ||
| - 📦 [KWin Script for system76-scheduler Integration](https://github.com/maxiberta/kwin-system76-scheduler-integration) | ||
| - Numerous popular GNOME extensions | ||
| - 🛳️ [AppIndicator/KStatusNotifierItem support](https://github.com/ubuntu/gnome-shell-extension-appindicator) (`gnome-shell-extension-appindicator`) | ||
| - 🛳️ [Pop shell extension](https://github.com/pop-os/shell) (`gnome-shell-extension-pop-shell`) | ||
| - 🛳️ Support for keyboard selection of windows and workspaces in GNOME Shell (`gnome-shell-extension-windowsNavigator`) | ||
| - 🛳️ [Bringing back the app menu](https://github.com/fthx/appmenu-is-back) (`gnome-shell-extension-appmenu-is-back`) | ||
| - 📦 [Pop Launcher](https://github.com/pop-os/launcher) (`pop-launcher`) | ||
| - 🛳️ [AppIndicator/KStatusNotifierItem support](https://github.com/ubuntu/gnome-shell-extension-appindicator) (`gnome-shell-extension-appindicator`) | ||
| - 🛳️ [Pop shell extension](https://github.com/pop-os/shell) (`gnome-shell-extension-pop-shell`) | ||
| - 🛳️ Support for keyboard selection of windows and workspaces in GNOME Shell (`gnome-shell-extension-windowsNavigator`) | ||
| - 🛳️ [Bringing back the app menu](https://github.com/fthx/appmenu-is-back) (`gnome-shell-extension-appmenu-is-back`) | ||
| - 📦 [Pop Launcher](https://github.com/pop-os/launcher) (`pop-launcher`) |
There was a problem hiding this comment.
prettier ran on this
There was a problem hiding this comment.
I use prettier too, can relate… please revert
|
|
||
| We believe that recent innovations in the Linux space serve to greatly improve the user and developer experience. Technologies like Flatpak and xdg-portals allow developers to provide great experiences to our users more consistently. Work done upstream improves the experience for our users, and work done in the Ultramarine ecosystem; like accent colours, and Chromebook support, improves the larger Linux ecosystem. It's a win-win. | ||
|
|
||
| ### Ultramarine is User-friendly. | ||
|
|
||
| While it may seem trivial to more advanced users to tweak a few settings and install some packages from 3rd party repositories, it may take people who are new to Linux (or even just new to Fedora) hours to figure out what packages they need, and where to find them. Ultramarine allows users new and old to get up and running quickly. | ||
|
|
||
| ### Ultramarine is Accesible |
There was a problem hiding this comment.
new value we're adding, per flock talk, still need to write it out
There was a problem hiding this comment.
that's part of it, a11y is part of making ultramarine accessible to as many people as possible. accessibility comes from access-ability the ability to access, we want ultramarine to be easy to access, this is done with hardware, a11y, etc etc
Co-authored-by: madomado <[email protected]>
No description provided.