What about growing our base by supporting unsupported Chromebooks?
Hello, On Thu, Jul 28, 2022 at 11:02:24AM -0500, Larry Len Rainey wrote:
I have been helping school systems revive obsolete (by Googles requirements) Chromebooks.
By OpenSUSE standards they are not valid as btrfs and 32GB mccblk drives are not possible and most Adam processors do not have a 64 bit UEFI only a 32 bit UEFI.
I have used the i586 UEFI boot code from Thunderbird and had Leap 15.3 MATE desktop with ext4 file system working, but the upgrade to 15.4 killed the 32 bit UEFI code.
Our base of OpenSUSE users are migrating to Sparky Linux 32 bit with MATE desktop (which the teachers like it because it looks like XP or Vista and no relearning).
Until OpenSUSE can install on Chromebooks with mmcblk 32gb drives and 64 Bit Adam CPU's. Future OpenSUSE users are going Debian and we will not get them back.
There are over 1 million unsupported Chromebooks that could be converted to OpenSUSE. We need a Chromebook install instance with 32 bit UEFI and ext4 file system as a default.
1) you can use a bigger SD card (and that's what you will ikely use if useing image) 2) the installer should select the correct filesystem, if not that's a bug Thanks Michal
On Thu, Jul 28, 2022, at 12:02 PM, Larry Len Rainey wrote:
I have been helping school systems revive obsolete (by Googles requirements) Chromebooks.
By OpenSUSE standards they are not valid as btrfs and 32GB mccblk drives are not possible and most Adam processors do not have a 64 bit UEFI only a 32 bit UEFI.
I have used the i586 UEFI boot code from Thunderbird and had Leap 15.3 MATE desktop with ext4 file system working, but the upgrade to 15.4 killed the 32 bit UEFI code.
Our base of OpenSUSE users are migrating to Sparky Linux 32 bit with MATE desktop (which the teachers like it because it looks like XP or Vista and no relearning).
Until OpenSUSE can install on Chromebooks with mmcblk 32gb drives and 64 Bit Adam CPU's. Future OpenSUSE users are going Debian and we will not get them back.
There are over 1 million unsupported Chromebooks that could be converted to OpenSUSE. We need a Chromebook install instance with 32 bit UEFI and ext4 file system as a default.
My 2 cents.
I would still use btrfs on mmc because (a) the early failure detection is better with btrfs, which will report it as transient corruption of data or metadata (b) the option to use compression, which reduces wear and improves read performance, and might improve write performance. -- Chris Murphy
On Thu, Jul 28, 2022 at 02:02:49PM -0400, Chris Murphy wrote:
On Thu, Jul 28, 2022, at 12:02 PM, Larry Len Rainey wrote:
I have been helping school systems revive obsolete (by Googles requirements) Chromebooks.
By OpenSUSE standards they are not valid as btrfs and 32GB mccblk drives are not possible and most Adam processors do not have a 64 bit UEFI only a 32 bit UEFI.
I have used the i586 UEFI boot code from Thunderbird and had Leap 15.3 MATE desktop with ext4 file system working, but the upgrade to 15.4 killed the 32 bit UEFI code.
Our base of OpenSUSE users are migrating to Sparky Linux 32 bit with MATE desktop (which the teachers like it because it looks like XP or Vista and no relearning).
Until OpenSUSE can install on Chromebooks with mmcblk 32gb drives and 64 Bit Adam CPU's. Future OpenSUSE users are going Debian and we will not get them back.
There are over 1 million unsupported Chromebooks that could be converted to OpenSUSE. We need a Chromebook install instance with 32 bit UEFI and ext4 file system as a default.
My 2 cents.
I would still use btrfs on mmc because (a) the early failure detection is better with btrfs, which will report it as transient corruption of data or metadatas
And the early space exhastion makes the filesystem completely unusable, often long before the medium manages to wear out
(b) the option to use compression, which reduces wear and improves read performance, and might improve write performance.
That's not specific to btrfs Thanks Michal
participants (3)
-
Chris Murphy -
Larry Len Rainey -
Michal Suchánek