Trisquel On A Sugar Toast: Difference between revisions

Fix typo
Inline and edit the 9.0 announcement and update to new TOAST 9.0 image
Line 4: Line 4:
__TOC__
__TOC__
==[[File:trisquel_logo.png]] Trisquel 9 Sugar Toast==
==[[File:trisquel_logo.png]] Trisquel 9 Sugar Toast==
* http://us.archive.trisquel.info/iso/trisquel-sugar_9.0_i686.iso
<noinclude>[[Category:Live USB]]</noinclude>
* Announcement: http://lists.sugarlabs.org/archive/iaep/2020-November/020943.html
 
'''T'''risquel '''o'''n '''a''' '''S'''ugar '''T'''oast (TOAST from now on) is a live/installable iso image that can be run from a CD/DVD or be used to load a USB drive with data persistence. Some other advanced uses are described below.
__TOC__
==[[File:trisquel_logo.png]] Trisquel 9 Sugar Toast==
* https://cdbuilds.trisquel.org/trisquel-sugar_9.0_i686.iso
 
Thanks to all who have made Trisquel On A Sugar TOAST a reality
(as well as being the first little-endian recursive acronym I've seen)
 
It's now the best generic Sugar Live ISO there is, beating the previous champion Fedora SOAS:
- It works on 32-bit machines
- It has lots of Activities
- It autostarts if you just turn it on
- It has a joyful splash screen
- It has a world language selector at boot
- It uses any Linux swap partitions it finds
 
Now for the bad news...
 
- On the text consoles and on reboot for some settings changes, there's
  a login prompt at which one has to guess that the username is trisquel
  and the password is [Enter]. Autologin would be better.
 
and it shares two hardware-specific bugs with the other Sugar Live systems:
- With some nVidia video cards, Xorg's "nouveau" DRI driver bug which makes
  github.com/login go all gray and affects other websites including gmail.com
  The simplest and least invasive fix is to delete
  ```/usr/lib/*-linux-gnu/dri/nouveau_dri.so```<BR>Hot fix on Live System:
  ```CTRL-ALT-F2 trisquel [Enter] [Enter] sudo rm /usr/lib/*-linux-gnu/dri/nouveau_dri.so; killall Xorg``` then login as ```trisquel [Enter] [Enter]```)<BR>
  For gory details see github.com/sugarlabs/sugar-live-build/issues/20
- The alsa "Headphone" control is muted, so no sound comes out of
  external speakers. "alsactl init" fixes this but also halves the main
  audio volume, while "amixer set Headphone unmute" makes it work.
  That leaves the Headphone volume at 0 but some sound still comes out
  of the headphone socket.<BR>Hot fix:
  ```CTRL-ALT-F2 trisquel [Enter] [Enter] alsactl init [Enter] CTRL-ALT-F7```
 
I guess I'm lucky to use an ancient laptop with a crummy video chip and
broken speakers so I could discover these issues :)
 
The above link is the second testing release of TOAST 9.0 "Etiona", different from [http://us.archive.trisquel.info/iso/trisquel-sugar_9.0_i686.iso the 18 October 2020 release] which only had English and Spanish:


==Bug Reports==
==Bug Reports==
'''Use http://trisquel.info/en/project/issues''' to report bugs
Use '''http://trisquel.info/en/project/issues''' to report bugs


==Install to disk==
==Install to disk==
Line 24: Line 64:


==Live CD persistence==
==Live CD persistence==
You can achieve user data persistence by loading TOAST from a handy USB drive, but you can also use a regular Live CD for that, and it will work in systems with no USB-boot capabilities. You just need to pass the "persistent" parameter to the Live CD kernel (pressing F4 in the boot menu) and have a ext2 (ext3 and 4 will work too) partition labeled "live-rw" available in any disk. It can be a USB flash drive too.
You can achieve user data persistence by loading TOAST from a handy USB drive, but you can also use a regular Live CD for that, and it will work in systems with no USB-boot capabilities. You just need to pass the "persistent" parameter to the Live CD kernel (pressing F4 in the boot menu) and have a ext2 (ext3 and 4 will work too) partition labeled "live-rw" available in any disk. It can be a USB flash drive too.


Line 32: Line 71:


===USB load helper===
===USB load helper===
Some computers -like Apple's- cannot boot an operating system from a thumb drive, and in some cases the computer is not configured to do so and the user doesn't have the privileges or knowledge to do that, and a CD is the only method for booting a system. As USB images run faster and can provide integrated persistence, you might want to use the Live CD to load just the kernel and run the live session from the faster flash drive instead. You just need to create a Live USB drive using the method described above, and boot the computer with both the CD and the USB drive inserted. Set the computer to boot from the CD, and it will load the kernel and search for USB drives to continue booting from them.
Some computers -like Apple's- cannot boot an operating system from a thumb drive, and in some cases the computer is not configured to do so and the user doesn't have the privileges or knowledge to do that, and a CD is the only method for booting a system. As USB images run faster and can provide integrated persistence, you might want to use the Live CD to load just the kernel and run the live session from the faster flash drive instead. You just need to create a Live USB drive using the method described above, and boot the computer with both the CD and the USB drive inserted. Set the computer to boot from the CD, and it will load the kernel and search for USB drives to continue booting from them.