Ok I realized now that if I download from the second page the 0.0.0.14 beta2.zip works fine.
I thought that on the GitHub was the same thing as many plugins ready to install..maybe not
[RPi] Argon ONE Control Add-on (Support Thread)
-
myshit -
July 31, 2023 at 9:01 PM -
Thread is Resolved
-
-
Downloaded from github right now , but latest libreelec version gives installing error.
Until now I only provided ready to install add-on packages here (attachments are at the end of the text):
So I don't really know what you are talking about and need more details with an exact version and, if necessary, a link to the debug log.
Perhaps you tried the original version 0.0.1 from Argon, which is known that it not working with versions, which are newer than LibreELEC 9? -
Until now I only provided ready to install add-on packages here (attachments are at the end of the text):
So I don't really know what you are talking about and need more details with an exact version and, if necessary, a link to the debug log.
Perhaps you tried the original version 0.0.1 from Argon, which is known that it not working with versions, which are newer than LibreELEC 9?My error. i download the zip from github and was installing it direct. but was failing the installation, just later i realized that there was a file attached in post 2 with the right one. installed perfect now. thanks
-
That's nice.
Also if you got the outdated add-on download not from my repository, you are right that "issues" is disabled. I'm currently undecided, if I should enable this opportunity or not. From the workflow view it would be the right way if someone like you can use it, but I have not the time to moderate this. -
I have to say that this is a really great job you are doing !
Nice addon, organization on github, so really really thanks for sharing your hours for this
-
This is the add-on icon that was created for a previous attempt at an add-on, if you wanted something that follows LE house-style.
-
chewitt ,
I'm appreciate your offer and hasn't forgot this Thread
Until now I was focused to make the technical part right. I wasn't unhappy with the original add-on icon, but it makes sense to follow a unified style.
Shortly after I enabled the issues option at the GitHub repo yesterday, it seems there is an interest to make some cosmetic changes... -
This is the add-on icon that was created for a previous attempt at an add-on, if you wanted something that follows LE house-style.
Maybe this addon could this be added to the LE repo ?
-
i would REALLY appreciate this. This Plugin needs to be in official repo!
-
There are no objections to it being submitted to the LE repo. The alternative will be to create an "argon40" repo for the add-on (ab)using GitHub free hosting and then have people install the add-on from that repo. The LE repo is easier for users since there's nothing extra to install, but an independent argon40 repo will probably be easier for the maintainer as fixes can be pushed on their own schedule. If there's any intent to support install on RaspiOS too, the independent repo is the right direction.
-
Currently I have no plans to support RaspiOS too. There are many reasons that speak against it:
- with a normal OS the fan control should be enabled system-wide, power button too
- system-wide solutions are already available: argon1.sh, Argon One Daemon …
- no spare system to test
- available time
- …
-
Currently I have no plans to support RaspiOS too. There are many reasons that speak against it:
- with a normal OS the fan control should be enabled system-wide, power button too
- system-wide solutions are already available: argon1.sh, Argon One Daemon …
- no spare system to test
- available time
- …
True. It's a LE addon. stop.
And surly no time for other projects is true too.
If it would be easy and doesn't take so much time to do, just push up the zip in the LE repo would be good for everyone . But I understand you if this is too complicated.
-
hello HarryH , i finally made the jump to a Raspi5 and your plugin is working fine on the Argon40 V3 case with M2-NVMe extensionboard too
speaking of NVMe: i am currently using the Raspi5 with a SD-Card. I plan to upgrade to a NVMe SSD. Do you know how what i need to add to config.txt to make it boot from the SSD? The argon scripts don't run on LibreElec i suppose?
-
With the official 27W PSU, a current bootloader (>= 2024-02-16) in your RPi5 and 100% compatible NVMe you don't need to change anything, because the autodetection should work and tells the kernel all things regarding the PCIe.
Since the Argon ONE V3 does not support the PD handshake internally, these settings are necessary to provide enough power and add the NVMe as a boot device:
bootloader config / EEPROM
CodePSU_MAX_CURRENT=5000 BOOT_ORDER=0xf416config.txt
Codeusb_max_current_enable=1
If all things work fine and after some days without errors in the kernel log, you could force the PCIe to Gen 3 if you want speed up. But this is alltime out of the current certification for the RPi5 and should observed as a kind of overclocking. Some kind of NVMe seems to need this to (maybe a firmware bug ?):
config.txt
Codedtparam=pciex1_gen=3
-
Thanks for the infos HarryH
so, if i add a NVMe SSD to the Argon case it will be booted by default? (over the microSD being in place?)
Maybe you built in a option in your addon to check if these settings are active or even to change the boot order in the addon?
-
so, if i add a NVMe SSD to the Argon case it will be booted by default? (over the microSD being in place?)
I can't answer that with certainty. I don't have a RPi5 myself. But I know that many things have changed in the bootloader and to many users fiddling with outdated parameters. Therefore my recommendation is to start with the only needed settings.
Because some weeks ago the official M.2 HAT+ (incl. specification) was published and advertised to automatically add the NVMe as boot device if detected, I'm expect that booting from NVMe is now also possible via default. Maybe this works with HAT+ only, and therefore not with the Argon ONE V3.However, to persist the boot order like you want, I would prefer to set it via EEPROM.
EDIT: The advertisement was misleading, the official M.2 HAT+ requires too, to set the boot order in EEPROM like I described above.
If you need additional settings like PCIE_PROBE=1 or dtparam=pciex1 / dtparam=nvme to get it detected, then it indicates your bootloader is very outdated or your chosen NVMe not compatible. -
hello HarryH , i finally made the jump to a Raspi5 and your plugin is working fine on the Argon40 V3 case with M2-NVMe extensionboard too
I am curious. Did you get Argon's remote control? If so, have you tried the on/off function with your new Pi5?
hello HarryH , i finally made the jump to a Raspi5 and your plugin is working fine on the Argon40 V3 case with M2-NVMe extensionboard too
Does this case have any LEDs that you find annoying?
-
no, i don't have or use a argon remote.
The case has ONE green led which lights up when powered on and flashes on sd-card access. I first thought it would annoy me but it turned out that it does not
it doesn't shine very light in a dark room, so it is ok for me.
