Argon One script installation script freeze with OS Lite 64 bit install

Clean install, no other software on my Raspberry Pi 4. I’ve repeated the install procedure 10 times without success, formatting the SD card every time.

I’m going to return this product if software can’t be properly installed.

After launching the script it freezes at “Created symlink”… even after reboot, manually try to start the service result in a freeze:

pi@Raspberry-Pi-4:~ $ sudo systemctl status argononed.service
● argononed.service - Argon One Fan and Button Service
     Loaded: loaded (/lib/systemd/system/argononed.service; enabled; vendor preset: enabled)
     Active: inactive (dead)

Install log:

pi@Raspberry-Pi-4:~ $ curl https://download.argon40.com/argon1.sh | bash
  % Total    % Received % Xferd  Average Speed   Time    Time     Time  Current
                                 Dload  Upload   Total   Spent    Left  Speed
100 21560  100 21560    0     0  19284      0  0:00:01  0:00:01 --:--:-- 19284
Reading package lists... Done
Building dependency tree... Done
Reading state information... Done
python3-rpi.gpio is already the newest version (0.7.0-0.2+b2).
0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded.
Reading package lists... Done
Building dependency tree... Done
Reading state information... Done
The following additional packages will be installed:
  i2c-tools libi2c0 read-edid
Suggested packages:
  libi2c-dev python-smbus
The following NEW packages will be installed:
  i2c-tools libi2c0 python3-smbus read-edid
0 upgraded, 4 newly installed, 0 to remove and 0 not upgraded.
Need to get 119 kB of archives.
After this operation, 431 kB of additional disk space will be used.
Get:1 http://deb.debian.org/debian bullseye/main arm64 libi2c0 arm64 4.2-1+b1 [10.6 kB]
Get:2 http://deb.debian.org/debian bullseye/main arm64 i2c-tools arm64 4.2-1+b1 [79.3 kB]
Get:3 http://deb.debian.org/debian bullseye/main arm64 python3-smbus arm64 4.2-1+b1 [13.2 kB]
Get:4 http://deb.debian.org/debian bullseye/main arm64 read-edid arm64 3.0.2-1.1 [16.1 kB]
Fetched 119 kB in 0s (706 kB/s)
Selecting previously unselected package libi2c0:arm64.
(Reading database ... 37391 files and directories currently installed.)
Preparing to unpack .../libi2c0_4.2-1+b1_arm64.deb ...
Unpacking libi2c0:arm64 (4.2-1+b1) ...
Selecting previously unselected package i2c-tools.
Preparing to unpack .../i2c-tools_4.2-1+b1_arm64.deb ...
Unpacking i2c-tools (4.2-1+b1) ...
Selecting previously unselected package python3-smbus:arm64.
Preparing to unpack .../python3-smbus_4.2-1+b1_arm64.deb ...
Unpacking python3-smbus:arm64 (4.2-1+b1) ...
Selecting previously unselected package read-edid.
Preparing to unpack .../read-edid_3.0.2-1.1_arm64.deb ...
Unpacking read-edid (3.0.2-1.1) ...
Setting up libi2c0:arm64 (4.2-1+b1) ...
Setting up read-edid (3.0.2-1.1) ...
Setting up i2c-tools (4.2-1+b1) ...
Setting up python3-smbus:arm64 (4.2-1+b1) ...
Processing triggers for man-db (2.9.4-2) ...
Processing triggers for libc-bin (2.31-13+rpt2+rpi1+deb11u4) ...
Reading package lists... Done
Building dependency tree... Done
Reading state information... Done
i2c-tools is already the newest version (4.2-1+b1).
i2c-tools set to manually installed.
0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded.
Created symlink /etc/systemd/system/multi-user.target.wants/argononed.service → /lib/systemd/system/argononed.service.

Basically I have the same problem of this different model: Argoneon script stuck

1 Like

Did you ever get a fix for this? I have a very similar situation. I believe it is related to the i2c bus which doesn’t seem to be loading.

I get the error “modprobe: FATAL: Module i2c-dev not found in directory /lib/modules/5.15.76-v8+” When I run the argon1.sh script.

LJ

Yes sure. make sure you create the “Pi” user when you format the SD drive. At least for me it fixes the problem all the times.

Hi, I am having exactly the same problem. Did you ever fix it?

The error happens when you DO NOT create the defaul user, formatting new sd card. Make sure you create the “Pi” user when you format the SD drive. At least for me this fixes the problem.