Boot hangup while loading ntspec.service

MNT Pocket Reform
1

After installing the KDE plasma desktop, my the screen blinks a couple times when it gets to network time service. In the lines leading up to that, it also fails to load some network .bin files. I have included a photo of the screen from my phone.

ETA: this is after installing KDE Plasma. I can’t even get to the login screen to try it out!

Is this something I will need to do a system image rescue on an SD card to fix?

IMG_1733
IMG_17331920×1440 392 KB

2

(It’s been a couple of weeks, and my device still doesn’t boot. It keeps hanging up as described above. I copied the system image for my processor module from the archive onto a microSD card. Simply inserting the card and booting the device doesn’t work, since I don’t have any way to mount the system image to the SD card as described in the manual with the device not working.

I seem to be stuck. Any ideas?)

I guess it would help to download a program that can mount an image file, wouldn’t it? Jeez.

3

I mounted the system image to a microSD card and reinstalled the OS and it works now. Fortunately, I have just been experimenting with the device so I didn’t lose anything important.

Is there anything one can do to when the boot hangs up like that? How do you get into the bios? I tried some common key combinations to load the bios, but that didn’t yield anything.

4

You can attempt to enter one of the other TTY sessions. Control+Alt+FN key
F1 - F7 should be alternate sessions. F7 is usually Graphical Login or Display Manager like SDDM in the case of KDE default. From there you should be able to try and debug your issue.

1 Like
5

There is no BIOS. One of the first things that get loaded when you boot the device is u-boot which will look for a file called boot.scr or extlinux.conf on a usb-stick, on an sd-card or on emmc in that order. It will load the first one it finds and that file will then govern how the boot proceeds. You have a few options in situations like yours:

  1. get a usb uart adapter and use it to connect to the device via serial and use a serial terminal to fix the problem
  2. use a different tty as @Savasten suggested
  3. pop in an sd-card with a vanilla system image on it that you can then use to repair your existing installation

Since you have just re-installed the OS it would be useful to find out whether the problem is reproducible. But you should probably only try these kind of experiments if you either feel comfortable performing either of above 3 options or if you would enjoy doing some remote debugging. :slight_smile:

1 Like