You are not logged in.
Pages: 1
It however cannot be considered a permanent solution as it does not take advantage of the newly created home partition and it does not use the rest of the sd drive (uses only 7GB out of it).
I agree and thank you for your support. I can't mark the copy text in Console. So I made a
sudo blkid > blkid-movuan.txt
After turning off the PP, I chose the SD card and put it in a notebook where I made the proposed UUID modification. Then the system starts earlier and the text "or press Control-D to continue" has not appeared. So it really helped.
I was intrigued that now the names of mmcblk1 are mmcblk2 and vice versa.
:-)
The situation in the first picture occurred even though I don't have a keyboard. That's why I was amazed that it is written about Pinephone-Keyboard.
Preliminary: The issue may be /etc/fstab entry for /home where field 6 is currently 2 and could be changed to 0 instead, in order to avoid failure if pinephone shuffles /dev/mmcblk# during TowBoot.
The entry should be changed to reference UUID (as reported by blkid) instead of /dev/mmcblk1p3.
At the moment I have been uptime 3 days, but Mobian has not tried for a long time. Inside on the device is installed one still from 2022. Now I can't compare with the current mobian. I will look at the one /etc /fstab and let know if something has changed.
.
Hi. I tried this Movuan and it works overall. However, I experienced problems when the system is triggered.
It is probably due to the fact, that I have installed Tow-Boot. When the system is started, it ended in 2/3 of the cases, as in the pictures.
.
pinephone-keyboard
.
.
.
or press Control-D to continue
.
.
.
If someone has the same problem, it is necessary to keep the Volume-Down key pressed longer at the start. In my case up to about 15 seconds to start the system.
Thank you for trying this alternative to Mobian. It's interesting.
.
.
I like to know the source of your information. Perhaps I can find some more hints or other possible options to use.
Best source is internet search ...
Some good source is maybe:
https://wiki.archlinux.org/index.php/Intel_graphics
or
https://bbs.archlinux.org/search.php?se … 1922492135
But not all things from arch are applicable on different operating system
Best regards...
.
I am pretty sure its not a hardware or BIOS issue. Its a driver or a set of configurations which makes the Intel iGPU fuzzy
.
Hi, you can try create file 20-intel.conf
with content
Section "Device"
Identifier "intel Graphics"
Driver "intel"
Option "TearFree" "true"
Option "AccelMethod" "uxa"
EndSection
Create directory in /etc/X11 named xorg.conf.d
And copy as root file 20-intel.conf
to
/etc/X11/xorg.conf.d
restart
.
.
After that installation I got error messages from nvidia-persistenced both in Synaptic and the console during installation of any package:
nvidia-persistenced failed to initialize. Check syslog for more details
I've got the same message during nvidia-persistenced installation process.
This can be avoided, you can run command in terminal :
sudo dpkg --configure nvidia-persistenced
If nvidia-persistenced runs, check in terminal :
ps aux | grep -i nvidia-persistenced
Possible answer looks like
nvpd 1632 0.0 0.0 4672 1596 ? Ss 21:03 0:00 /usr/bin/nvidia-persistenced --user nvpd
.
Pages: 1