Snakeoil 1.4.0 (High End)

[Snoopy8]

Thanks. I'd found that page. And tried substituting the official RPi 5 PSU for my Linear PSU, but no joy 

There is also a YouTube video where the guy shows a way to override the Ubuntu error message on boot supposedly to allow the machine to boot. I haven't tried that, but perhaps I should.

It was a pain to get a power supply that the Pi5 recognises as 5V, 5A. Failed with super duper Gaan USB charger with 65W and Dell laptop 45W charger. Best to attach monitor to see what is happening. It will give you a message to press the power button to temporarily bypass this restriction, and also what to change in config file for permanent bypass.

Was not expecting a SQ difference, but the USB boot is better than microSD!     Brought it back closer to the NUC. So may have to start looking for a new LPS

[hkphantomgtr]

Thanks. I'd found that page. And tried substituting the official RPi 5 PSU for my Linear PSU, but no joy 

There is also a YouTube video where the guy shows a way to override the Ubuntu error message on boot supposedly to allow the machine to boot. I haven't tried that, but perhaps I should.

It was a pain to get a power supply that the Pi5 recognises as 5V, 5A. Failed with super duper Gaan USB charger with 65W and Dell laptop 45W charger. Best to attach monitor to see what is happening. It will give you a message to press the power button to temporarily bypass this restriction, and also what to change in config file for permanent bypass.

Was not expecting a SQ difference, but the USB boot is better than microSD!     Brought it back closer to the NUC. So may have to start looking for a new LPS

Are you powering Pi5 thru USB C？ If so, in my understanding (I've searched a lot in internet last two months), the simplest way is to buy the original Pi 5 power supply.  Most of the USB switching power supply in the consumer market are not able to output more than 3A/4A in 5V.  

If you are powering pi5 thru GPIO, then you need to modify the /boot/firmware/boot.txt to let Pi 5 knows that, the incoming power supply can be more than 3A.  Or no matter how strong your power supply to GPIO, Pi 5 just keeps warning you for not enough power.  Then it slows down itself and limits the current output to those peripherals.  That will be very obvious if one boot into a desktop OS, e.g. Raspberry Pi OS, Ubuntu OS.  Everything will take very long time to load and they are slow.

---

Confirming my Pi5 has 2 blue  USB ports and they are the bootable USB ports.  One more thing to consider.  The Pi5 expects 5V 5A when booting from USB (but this can be overwritten temporarily during boot or permanently in config file).  This may help:

https://bret.dk/usb-boot-on-the-raspberry-pi-5/

Thanks. I'd found that page. And tried substituting the official RPi 5 PSU for my Linear PSU, but no joy 

There is also a YouTube video where the guy shows a way to override the Ubuntu error message on boot supposedly to allow the machine to boot. I haven't tried that, but perhaps I should.

For the LPSU, did you modify the /boot/firmware/config.txt? 
Misc. sharing for building Raspberry Pi 5 as music server

[Snoopy8]

@hkphantomgtr using USB C, not GPIO.  And the change was set_max_current_enable=1 in config.txt so that it would boot with 3A power supply.

May look at getting official power supply.

[uglymusic]

<snip>

But I haven't yet tried your fix for the non-booting from the USB stick, AK. Hopefully tomorrow.

It works, AK. The config.txt line.

Thank you!

[uglymusic]

Thanks. I'd found that page. And tried substituting the official RPi 5 PSU for my Linear PSU, but no joy 

There is also a YouTube video where the guy shows a way to override the Ubuntu error message on boot supposedly to allow the machine to boot. I haven't tried that, but perhaps I should.

It was a pain to get a power supply that the Pi5 recognises as 5V, 5A. Failed with super duper Gaan USB charger with 65W and Dell laptop 45W charger. Best to attach monitor to see what is happening. It will give you a message to press the power button to temporarily bypass this restriction, and also what to change in config file for permanent bypass.

Was not expecting a SQ difference, but the USB boot is better than microSD!     Brought it back closer to the NUC. So may have to start looking for a new LPS

Interesting about the PSU problems. Have you tried a shorter power lead? I've just remembered as I write this that I had problems with earlier RPis not working satisfactorily with longer power leads. I'll put that on my list of things to try when I have the will to mess about more!

---

@hkphantomgtr using USB C, not GPIO.  And the change was set_max_current_enable=1 in config.txt so that it would boot with 3A power supply.

May look at getting official power supply.

FWIW, the official PSU made no difference for me.

[aabman]

I upgraded from SO1.3 to SO1.4. It sounds a bit clear and gained better solution. Thanks for the effort. However, I found some mirror hurdles as follows:
1. My SO1.4 mounted 3 partitions. /dev/sda3 is parted from the system disk which only is "root" 505 permission. And the demountable disk /dev/sdb2 and /dev/sdc2 have only 705 permission. I tried as root and executive chmod -R -R 777 to the device. Then listed the result which shown 777, but in operation actually the permission was not modified. I did't understand at all.

2. Followed the steps uninstall /update/install, I couldn't upgrade to SO 1.4 indeed.

Would someone help please.

[agent_kith]

I upgraded from SO1.3 to SO1.4. It sounds a bit clear and gained better solution. Thanks for the effort. However, I found some mirror hurdles as follows:
1. My SO1.4 mounted 3 partitions. /dev/sda3 is parted from the system disk which only is "root" 505 permission. And the demountable disk /dev/sdb2 and /dev/sdc2 have only 705 permission. I tried as root and executive chmod -R -R 777 to the device. Then listed the result which shown 777, but in operation actually the permission was not modified. I did't understand at all.

can you run "sudo mount" and show me the output? You don't run chmod on the device, you run them straight on the mounted paths. e.g. if /dev/sdb2 is mounted under /x/y/z, you then run "sudo chmod -R 777 /x/y/z".

You don't need to bother to look at mount points outside "/media", and I would suggest you do not run chmod unless you really know what you're doing. Giving the wrong permissions would be a security risk.

2. Followed the steps uninstall /update/install, I couldn't upgrade to SO 1.4 indeed.

To move on to 1.4.0 you should just run the install script if you havn't run it before. Read this section of the guide: https://www.snakeoil-os.net/reference/ba...il_package

Unfortunately when I post in the forums information for this may not be included - I kind of assumed people read posts for 1.4.0, 1.4.1, 1.4.2 and so on so not all information is contained in this first post I think.

[aabman]

Thanks for your kind reply. Yes, I did run what you said before : sudo chmod -R 777 \media\music\sda3.  "ls" command shown the device permission was modified, but it didn't work in actual operation. BTW, could I directly log in as root, instead log in user account then elevate to root via sudo su command.

[aabman]

Thanks for your kind reply. Yes, I did run what you said before : sudo chmod -R 777 \media\music\sda3.  "ls" command shown the device permission was stricted to read only.
As per web instruction of apt installion, I upgradeed to 1.4.3 and found it is noticable sonic improvement.
BTW, could I directly log in as root, instead log in user account then elevate to root via sudo su command?  Thanks again.

---

Thanks for your kind reply. Yes, I did run what you said before : sudo chmod -R 777 \media\music\sda3.  "ls" command shown the device permission was stricted to read only.
As per web instruction of apt installion, I upgradeed to 1.4.3 and found it is noticable sonic improvement.
BTW, could I directly log in as root, instead log in user account then elevate to root via sudo su command?  Thanks again.

[agent_kith]

@hkphantomgtr using USB C, not GPIO.  And the change was set_max_current_enable=1 in config.txt so that it would boot with 3A power supply.

May look at getting official power supply.

Technically this will just disable some of the software checks on the Pi and allow operations to continue. There are pros and cons of doing so I guess, if you try to run more things and the PSU cannot supply enough current then things will not work (would components be damaged? Possibly but unlikely).

Also although the official power supply will work - however bear in mind under load it can emit a high pitch noise that is super irritating. I think I have lost my ability to hear these noises from my listening position so that's not going to be a problem for me, but if you are still sensitive bear this in mind . Transformer hum is no way as bad as these high pitch squeaks.

Thanks for your kind reply. Yes, I did run what you said before : sudo chmod -R 777 \media\music\sda3.  "ls" command shown the device permission was stricted to read only.

Hmm. I may have to look into the permissions thing. If you can still scan for the music then it's not something you need to bother for now.

BTW, could I directly log in as root, instead log in user account then elevate to root via sudo su command?  Thanks again.

Best practice is not do do this actually. Good practice is to  prefix everything with sudo if you want..

But technically you can modify the SSH daemon to do whatever you want (including directly logging in as root). Look up the Internet on instructions on how to do so. Snakeoil OS is unlike other OS because you have FULL control, and this includes logging into the root account directly. I do not recommend it personally, but not going to stop people from doing what they like. Our motto is - designed by us, defined by you, i.e. you have complete freedom.