Resolution NOOBS
-
This is interesting...
can you explain it better?
I would like to have more details ... -
If I modify the files:
/media/pi/SYSTEM/noobs.conf ?or
/ Media / pi / 01A6-0A6B (I believe the noobs partition) /config.txt ?
For a reboot i saw the picture of noobs, bad quality, but i was fine, then i deleted the string: "hdmi_drive = 1" and after everything came back as before ... then i got it back but nothing.
I really do not understand.Ps: I will reboot 30 times to do the tests.
-
I have no idea where it is mounted in raspbian, i'd rather trust it's the /dev/mmcblk0p1, up to you to check where it is mounted with
mount
-
This was the result of "mount"
/dev/mmcblk0p9 on / type ext4 (rw,noatime,data=ordered)
devtmpfs on /dev type devtmpfs (rw,relatime,size=469532k,nr_inodes=117383,mode=755)
sysfs on /sys type sysfs (rw,nosuid,nodev,noexec,relatime)
proc on /proc type proc (rw,relatime)
tmpfs on /dev/shm type tmpfs (rw,nosuid,nodev)
devpts on /dev/pts type devpts (rw,nosuid,noexec,relatime,gid=5,mode=620,ptmxmode=000)
tmpfs on /run type tmpfs (rw,nosuid,nodev,mode=755)
tmpfs on /run/lock type tmpfs (rw,nosuid,nodev,noexec,relatime,size=5120k)
tmpfs on /sys/fs/cgroup type tmpfs (ro,nosuid,nodev,noexec,mode=755)
cgroup on /sys/fs/cgroup/systemd type cgroup (rw,nosuid,nodev,noexec,relatime,xattr,release_agent=/lib/systemd/systemd-cgroups-agent,name=systemd)
cgroup on /sys/fs/cgroup/cpu,cpuacct type cgroup (rw,nosuid,nodev,noexec,relatime,cpu,cpuacct)
cgroup on /sys/fs/cgroup/blkio type cgroup (rw,nosuid,nodev,noexec,relatime,blkio)
cgroup on /sys/fs/cgroup/memory type cgroup (rw,nosuid,nodev,noexec,relatime,memory)
cgroup on /sys/fs/cgroup/devices type cgroup (rw,nosuid,nodev,noexec,relatime,devices)
cgroup on /sys/fs/cgroup/freezer type cgroup (rw,nosuid,nodev,noexec,relatime,freezer)
cgroup on /sys/fs/cgroup/net_cls type cgroup (rw,nosuid,nodev,noexec,relatime,net_cls)
tmpfs on /etc/machine-id type tmpfs (ro,mode=755)
systemd-1 on /proc/sys/fs/binfmt_misc type autofs (rw,relatime,fd=22,pgrp=1,timeout=300,minproto=5,maxproto=5,direct)
debugfs on /sys/kernel/debug type debugfs (rw,relatime)
mqueue on /dev/mqueue type mqueue (rw,relatime)
fusectl on /sys/fs/fuse/connections type fusectl (rw,relatime)
configfs on /sys/kernel/config type configfs (rw,relatime)
/dev/mmcblk0p8 on /boot type vfat (rw,relatime,fmask=0022,dmask=0022,codepage=437,iocha**et=ascii,shortname=mixed,errors=remount-ro)
tmpfs on /run/user/1000 type tmpfs (rw,nosuid,nodev,relatime,size=94776k,mode=700,uid=1000,gid=1000)
gvfsd-fuse on /run/user/1000/gvfs type fuse.gvfsd-fuse (rw,nosuid,nodev,relatime,user_id=1000,group_id=1000)
/dev/mmcblk0p7 on /media/pi/3b5fdb55-32a7-4b35-85e2-c7144bb88443 type ext4 (rw,nosuid,nodev,relatime,data=ordered,uhelper=udisks2)
/dev/mmcblk0p6 on /media/pi/01A6-0A6B type vfat (rw,nosuid,nodev,relatime,uid=1000,gid=1000,fmask=0022,dmask=0077,codepage=437,iocha**et=ascii,shortname=mixed,showexec,utf8,flush,errors=remount-ro,uhelper=udisks2)
/dev/mmcblk0p5 on /media/pi/SETTINGS type ext4 (rw,nosuid,nodev,relatime,data=ordered,uhelper=udisks2)
/dev/mmcblk0p12 on /media/pi/share type ext4 (rw,nosuid,nodev,relatime,data=ordered,uhelper=udisks2)
/dev/mmcblk0p11 on /media/pi/root0 type ext4 (rw,nosuid,nodev,relatime,data=ordered,uhelper=udisks2)
/dev/mmcblk0p10 on /media/pi/boot01 type vfat (rw,nosuid,nodev,relatime,uid=1000,gid=1000,fmask=0022,dmask=0077,codepage=437,iocha**et=ascii,shortname=mixed,showexec,utf8,flush,errors=remount-ro,uhelper=udisks2)I honestly do not understand what to do.
-
@Usato The aim is to mount /dev/mmcblk0p1 (the very first partition of the sdcard that is in fact noobs) and add a config.txt from here
just out of my mind, try :
mkdir -p /tmp/noobs mount /dev/mmcblk0p1 /tmp/noobs
If mount succeeded, you should be able to
cd /tmp/noobs
and create a config.txt from there. Do you know which lines you're supposed to add to the config.txt for noobs ? -
hmdi_group=2
hdmi_mode=87
hdmi_cvt 1024 600 60 3 0 0 0correct?
-
command:
mount /dev/mmcblk0p1 /tmp/noobsmessage:
mount: only root can do that????
-
@Usato Sorry I'm so used to be root, and not having to sudo
So :
mkdir -p /tmp/noobs sudo mount mount /dev/mmcblk0p1 /tmp/noobs
Then editing the file needs to be done through sudo, always. For example :
sudo nano /tmp/noobs/config.txt
. I'm not sure about the mount options to give any user the read/write access to the mount point -
ok, now?
ps
Why created folder / tmp / noobs? -
@Usato now you edit the config.txt as suggested
I made you create a new folder in /tmp as it will get erased on reboot, so that you don't have ghost reps in /media/pi
-
ok done.
Reboot? -
You are a fantastic genius.
If I could embrace you -
@Substring I thank you heartily.
-
@Usato One more happy user