Straight out of the box problems with fresh PureOS install

Software PureOS
, ,
3

I appreciate the recommendation. Perhaps I simply don’t know, but wouldn’t I need to be able to access the boot menu to do so? That is part of the problem.
The ‘esc’ key does not allow me to gain access to the boot menu, as described here. I am having a different issue. Upon system startup, the first thing I am presented with (just to be clear) is the decryption passphrase input screen; afterward, the graphical overlay for PureOS starts up, and if I press the ‘esc’ key at this juncture, it just takes me to the black screen listing the individual tasks being performed on system initialization. I have tried all the ‘f1-12’ keys, and holding down the ‘shift’ key (per the debian documentation, since PureOS is based off of it, I thought I would try…) but nothing helps. I also do not see any text displayed in the graphical overlay detailing how to gain access to the bootloader/boot menu. As such, how then would I reinstall the OS, if I am unable to gain access to such menu, in order to switch the bootable device? Perhaps I am missing something… I have never had this kind of an issue with a linux install before.

Edit: this is why I was wondering if I should just wipe the filesystem. I am reticent to do so, however, after reading posts to this effect. I don’t need the disc to be encrypted for my purposes. But now that it is, I want to make sure I won’t just be causing more hassle for myself by trying to fix this issue… whatever it is.

1 Like
4

Sounds like the Coreboot menu with the Purism logo splash screen is not displaying. You may want to reflash your boot firmware with Coreboot to see if that solves your issue.

After following those instructions, you should be able to press Esc to access the boot menu.

One issue at a time.

2 Likes
5

Thanks. I will look into that.

1 Like
6

Haven’t really had time or energy to focus on fixing this around my school schedule, but maybe the following is part of the issue? Just noticed that sudo apt full-upgrade gives readout:

E: Failed to fetch https://repo.pureos.net/pureos/pool/main/p/pureos-meta/pureos-stanard_0.11.0_amd64.deb Could not resolve 'repo.pureos.net'
E: Failed to fetch https://repo.pureos.net/pureos/pool/main/s/systemd/systemd-timesyncd_247.3-7%2bdeb11u4_amd64.deb Could not resolve 'repo.pureos.net'
E: Unable to fetch some archives, maybe run apt-get update or try with --fix-missing?

Any thoughts? I am talking with support as well. Appreciate the help.

Edit: following the recommendations on 3rd error line yield no results, gives same error for sudo apt full-upgrade --fix-missing, sans “maybe run/maybe try” comment. apt-get yields no errors, but also no results.

2nd Edit: I am going to look through the arch wiki’s systemd page to see if I can’t figure anything out, since there seems to be some kind of issue with it…?

1 Like
7

Do you live in a country where repo.pureos.net is blocked, or is your Librem offline?

1 Like
9

I am in California, same as the Purism company. The Librem is online.

Edit: Partial solution provided by tech support…

sudo apt clean
sudo rm -rf /var/cache/apt/*
sudo apt update
sudo apt full-upgrade

PureOS now shown as updated. Repo conflict is resolved. Applications in ‘Software’ app still show splash text: “Unable to remove [APPLICATION]: no packages to remove.” Was able to remove “cheese” via terminal, however, many others still output:

E: Unable to locate package [PACKAGE]

Thoughts?

1 Like
10

You need to uninstall the software from the command line (Terminal)
Sudo apt remove [[package-name]]

1 Like
11

Was able to remove “cheese” via terminal, however, many others still output:

E: Unable to locate package [PACKAGE]

Screenshot from 2024-02-06 12-56-18
Screenshot from 2024-02-06 12-56-181200×640 168 KB

Edit: obviously, a typo in the terminal input (“vidos”, vs “videos”; this was corrected; I have same output for all applications, save for “cheese”, thus far)

1 Like
12

That looks like fairly agricultural syntax. It simply isn’t right.

Regardless, the key point that you are missing is that (unfortunately) every package has two names.

  1. The name that might get displayed on a GUI.
  2. The actual name of the package.

To remove a package via terminal, you have to know the actual name of the package, and that can be difficult to achieve, and may even involve guesswork unless you really want to deep dive. So I guess it depends on how much time you want to put in to removing software, which in turn may depend on what your reason is for doing so.

Edit: Adding: To help you on your way, Parental Controls, which I also want to remove from my Librem 5 (I have no need for it and disk space is a lot tighter) requires

sudo apt remove malcontent

2 Likes
13

Well, my reason for doing so is to create a linux environment in which I have installed only those applications that I would actually be using.

I appreciate your input, and I will work on my syntax. That issue notwithstanding, I am still having persistent issues unaddressed. I cannot access the bootloader menu and switch to other bootable devices.

What I have been told, and read in the other forum posts, is that the ‘esc’ key is what is pressed to access the boot menu. That simply is not true on my machine. I am looking into the comment made by user FranklyFlawless, concerning reflashing the coreboot firmware, as stated here.

What I see upon system startup is the following:

  1. Hard drive decryption prompt;
  2. Loading bar with no text;
  3. PureOS splash graphical overlay;
  4. User profile select/login;

and between steps 2-3 I can press the ‘esc’ key to access the kernel init script (black screen, green text, etc.), nothing more.

As I have already stated earlier, upon attempting to update PureOS and/or any of the preinstalled apps via the ‘Software’ application, it declared that there were unmet dependencies; furthermore, that the packages cannot be found for individual applications. As adding/removing programs is the sole purpose of the ‘Software’ application, if it is non-usable for that intended purpose, I have no use for it. I seek to optimize the system.

Switching to the terminal and inputting:

sudo apt update
sudo apt upgrade

I found that the ‘Software’ application still listed the PureOS update as pending. When trying to complete the update via the app, it would display a similar message of “unmet dependencies”, but fail to display what those dependencies were, for the message being cut off.

This was addressed by help from the technical support staff, as stated earlier, here. I am also experiencing erratic behavior of the operating system, such as the ‘Software’ program being opened while I am running ‘Tweaks’, specifically when I am in the “extensions” menu. I do not know what to attribute these all to.

Edit: my mistake on that last one (see edits).

1 Like
14

You would be pressing Esc earlier than that. To take a step back though, there are two possible firmware options: Coreboot and Pureboot. Have you stated which of these you are running? Which did you specify on your order? Sometimes it can be helpful to post a photo of the first thing that comes up on the screen.

Is there anything unusual / demanding about your monitor? Can you try a different monitor?

1 Like
15

If you mean that it should appear before the decryption prompt, then I suppose it would likely be the monitor. I do not have another monitor at present, so I would have to deal with that some other time.

Edit: it is an older monitor. I will see if it makes a difference trying to press the esc key as soon as I power the machine on.

Also, it is pureboot that is on the machine. Thanks.

1 Like
16

Older is often better unless it is really really old. What video interface are you using with the monitor?

I don’t have a Librem Mini but looking at the product page, it seems the options are:

  • HDMI 2.0
  • DisplayPort 1.2

(and for either of those options, up to 4K @ 60Hz)

which should be more than enough for an older monitor.

I guess another thing to check is the video cable even if you don’t have another monitor to try.

1 Like
17

I guess it depends how old is really old. I think it is a 2011 monitor. It is using a vga output to a Rankie vga-to-display port adapter. I originally was using this monitor for a dell optiplex 5055 that I have had for a while, however I bought the monitor and the computer separately. I didn’t realize how much older than the computer the monitor was, so when it arrived in the mail I decided to just get an adapter instead of returning it.

Thanks to your input, I did notice something odd. Namely, if I time the pressing of the ‘esc’ key shortly after the computer turns on, the monitor simply won’t turn on at all. If I leave it alone until the decryption prompt pops up, it will work fine. I may need to simply get another monitor. It worked fine for my other computer, and it works fine once PureOS has been loaded by default by the bootloader… but the monitor and/or adapter doesn’t seem to initialize/recognize/process the signal prior to that point.

If you think there is anything else that could be worth trying, I would look into it, but I don’t really know what else I can do presently.

1 Like
18

VGA is really old. I mean in theory it should work but there is much more scope for something not to work.

So to be clear … you are using the DisplayPort video output on the Librem Mini, going into a DisplayPort-to-VGA adapter, going into the VGA input port of the monitor?

There was a transitional period when monitors had both a VGA input and a digital video input of some sort (DVI, or HDMI, or theoretically DisplayPort). I take it that your monitor offers only a VGA input?

If you let it boot normally, what video resolution does PureOS report?

What about a TV? Do you have a TV that has either a DisplayPort input or an HDMI input?

Since the Librem Mini is so easily portable, can you take it round to a friend’s place and try a suitable monitor (or TV) there?

That is kind of expected. I would suggest: It shows that Esc is working. The boot firmware is stopping early on, because you pressed Esc, before even attempting to load an operating system, but due to some incompatibility between the boot firmware and the video output arrangements, you see nothing on the screen - and, unless you take some other action, the boot firmware will wait forever for you to do something.

In theory you could fly blind to continue the boot but as (I assume) you have never seen the boot firmware and don’t know what menus and options exist, that would be difficult.

2 Likes
19

If that is the case, Esc is not used during the boot sequence.

1 Like
20

So to be clear … you are using the DisplayPort video output on the Librem Mini, going into a DisplayPort-to-VGA adapter, going into the VGA input port of the monitor?

Correct. And it does have a DVI output. The monitor, however, was shipped with a VGA cable, so that was what I set about to using. I could see if there is any difference with the DVI port.

If you let it boot normally, what video resolution does PureOS report?

So like from neofetch? It reads out as 1920x1080.

I think I will take it with me, per your suggestion, to the computer lab at my university tomorrow, and put that hypothesis to the test. That seems the most likely explanation presently. You’ve been incredibly helpful, so thanks for the patience and willingness to walk through this with me.

2 Likes
21

Thanks for pointing that out. wouldn’t’ve figured out the main issue was (or at least seems to be) my monitor. Once I get it hooked up to something else, I can see if the issue persists, or no. You’ve been very helpful, so thanks.

1 Like
22

Then if you get yourself an HDMI-to-DVI cable, that is definitely worth trying. (Check carefully the genders that you need at each end of the cable.)

Note:

  • HDMI-to-DVI need only be a passive cable (i.e. connector conversion) - there is no signal conversion
  • You will not get any sound via the monitor because DVI simply does not have the capability to transport sound (whereas HDMI does). So if sound output is important to you then you will have to keep your computer configured to output sound via something other than HDMI. However flying deaf will be better than flying deaf and blind. (In any case a monitor of that vintage may not even have sound capability i.e. no built-in speakers and no 3.5mm audio output jack for external speakers or headphones.)

I would have used xrandr or some such but whatever shows you the answer.

2 Likes
23

I just got a DVI–HDMI cable and have confirmed that was indeed the issue preventing display of the boot menu. Now I can finally move on to tweaking the OS to my preferences. Much appreciated.

2 Likes