LiveUSB booting fails strangely on Dell XPS 13/ubuntu
My machine is a Dell XPS 9343 with ubuntu 16.04 installed (64 bit), memory 7.7 GB. It's a machine with loads of proprietary drivers which shipped with ubuntu installed by the manufacturer.
I created a liveUSB of Trisquel 11 using different software: with Startup Disk Creator, with mkusb and with Etcher. I tried two different USB pens.
In GRUB, I choose to boot from the USB pen and I get to a Trisquel home screen (mountains and the trisquel logo superimposed at the centre of the screen), then a black screen and finally I enter the OS.... except that it's the wrong OS! It is ubuntu 14.04. If I choose to log off, I am greeted with "Goodbye, trisquel".
This is really odd.
Can anyone help?
I tried creating a liveUSB of another OS, SparkyLinux, and that works!
Thank you
Sorry, maybe it's me, but I hardly follow what happened here, but seems like the tool you are using does more that is supposed to do.
I would,
a) download the iso I want, mate, kde, lxde.
b) verify it
c) copy it the way you know and trust, dd, ventoy, or whatever tool you use.
d) try to boot again
When reporting issues like this I think the issue tracker would be best, sometimes "a picture is worth a thousand words" so maybe adding a picture on the report could help.
Cheers.
Thanks, I tried different ways to create a liveUSB simply because the way advised on the Trisquel website (ie Startup Disk Creator) did not work for me. By trying different tools I could establish that the problem is not with the tool I used. When I try and boot the result is always the same: I get into an OS that should not even be installed on my machine.
Out of your list the only step I did not go through is verification (b), because the instructions posted here https://trisquel.info/en/wiki/verify-trisquel-download do not work for me. By following those steps no .asc file is downloaded.
Well, I still think the tool my be involved, or the ISO might have issues.
Download the corresponding asc file for the ISO from: http://cdimage.trisquel.org/trisquel-images/
Maybe you'll like to give ventoy a try, format a USB drive then just copy the ISO images as files, that will make easier to test several ISOs and no background processing is done as it will require a copy paste the verbatim ISO file.
Cheers
Thanks, if I verify with the .asc file from the repository you sent me to, here is what I get:
$ gpg --verify trisquel_11.0_amd64.iso.asc trisquel_11.0_amd64.iso
gpg: Signature made Sun 19 Mar 2023 00:33:30 WET using RSA key ID 4AD4C938
gpg: Good signature from "Trisquel GNU/Linux Archive Automatic Signing Key (11/aramo) <name at domain>"
gpg: WARNING: This key is not certified with a trusted signature!
gpg: There is no indication that the signature belongs to the owner.
Primary key fingerprint: D24D DAC9 226D 5BA5 E9F3 BED3 F5DA AAF7 4AD4 C938
Any idea of why gpg is not happy with the key?
It's better to check the exit status of the program instead of looking for a "good signature" or "bad signature" response, which might be included as something as a part of key comment to trick people: https://trisquel.info/en/wiki/verify-trisquel-download
If you're asking about:
gpg: WARNING: This key is not certified with a trusted signature!
That's just because you didn't say you trust the key, not that there's anything "wrong" with it necessarily. Even if the crypto signature matches, how do you know that that key is the "right" one and not an attempt from Malory to trick you into trusting the wrong key?
https://en.wikipedia.org/wiki/Alice_and_Bob?useskin=vector
That's always a question in public key crypto systems. But, to whatever extent you trust the key, you can trust the results just as much. :)