Page 1 of 1

Revpi core S and jessie image

Posted: 16 Dec 2022, 19:41
by chi.pham
Dear,
I have picore S version and try to upload jessie image and have no luck. The led at the ethernet is not green. However, i upload the RevPi Buster image with the same steps and able to ssh to the device.
We used piCore and since it is discontinue, we switch to piCore S version and it seems not working with jessie image. For RevPi Buster, i can't not login using password on the sticker. I try the script "revpi_buster_fix_pictory.sh" and still have no luck. Is piCore S version compatible with jessie image?

Please help

Chi

Re: Revpi core S and jessie image

Posted: 17 Dec 2022, 00:30
by nicolaiB
Hi,

The Jessie image is not compatible with the S/SE models, as they require a more recent kernel version. Also Jessie is really end of life and even it's successor Stretch ended LTS support in June this year.

Therefore I strongly recommend to use our latest Buster image. If you have trouble with the password from the sticker on the enclosure, you can check if the password matches the output of the command 'piserial -p'.

Nicolai

Re: Revpi core S and jessie image

Posted: 17 Dec 2022, 02:28
by chi.pham
Thank you for the response. I tried the piSerial and here the errors i got. I expected to get the password, serial and version.

pi@RevPi10035982976:~ $ piSerial
WARNING: Can't write to `/dev/i2c-1': Remote I/O error
WARNING: Can't write to `/dev/i2c-1': Remote I/O error
WARNING: Can't write to `/dev/i2c-1': Remote I/O error
WARNING: Can't write to `/dev/i2c-1': Remote I/O error
WARNING: Can't write to `/dev/i2c-1': Remote I/O error
ERROR: FATAL: Can't get serial number from device

Re: Revpi core S and jessie image

Posted: 17 Dec 2022, 09:41
by nicolaiB
Looks like there is something wrong with the devices crypto chip connection (either device not configured properly or hardware issue).

Could you please run factory reset again and post the complete output? You can start the factory reset with the following command: sudo revpi-factory-rest

Nicolai

Re: Revpi core S and jessie image

Posted: 17 Dec 2022, 14:39
by chi.pham
nicolai,
I did the fatory reset and here the response are below.

Thank you

Code: Select all


pi@RevPi10035982976:~ $ sudo revpi-factory-reset --help

Usage: revpi-factory-reset <compact|connect|core|flat|core-se|connect-se> <serial> <mac addr>

(see front plate)

[b][u][b]pi@RevPi10035982976:~ $ sudo revpi-factory-reset core-se 10035982976 c83e-a710-2c61[/b][/u][/b]

DTOVERLAY[error]: failed to open '/boot/overlays/revpi-core-se.dtbo'

* Failed to read '/boot/overlays/revpi-core-se.dtbo'

ERROR: Can't open file `/dev/i2c-1': No such file or directory

ERROR: FATAL: Can't get serial number from device

Password:	

No password supplied

No password supplied

No password supplied

chpasswd: (user pi) pam_chauthtok() failed, error:

Authentication token manipulation error

chpasswd: (line 1, user pi) password not changed

ERROR: Can't open file `/dev/i2c-1': No such file or directory

ERROR: FATAL: Can't get serial number from device

Hostname:	RevPi10035982976

MAC Address eth0:	c83ea7102c61

Reboot to activate the MAC Address

Be sure to write down the password if you have lost the sticker

on your RevPi!

pi@RevPi10035982976:~ $ piSerial

ERROR: Can't open file `/dev/i2c-1': No such file or directory

ERROR: FATAL: Can't get serial number from device

pi@RevPi10035982976:~ $ piSerial -p

ERROR: Can't open file `/dev/i2c-1': No such file or directory

ERROR: FATAL: Can't get serial number from device

pi@RevPi10035982976:~ $ uname -all

uname: invalid option -- 'l'

Try 'uname --help' for more information.

pi@RevPi10035982976:~ $ rname -all

-bash: rname: command not found

pi@RevPi10035982976:~ $ uname --help

Usage: uname [OPTION]...

Print certain system information.  With no OPTION, same as -s.



  -a, --all                print all information, in the following order,

                             except omit -p and -i if unknown:

  -s, --kernel-name        print the kernel name

  -n, --nodename           print the network node hostname

  -r, --kernel-release     print the kernel release

  -v, --kernel-version     print the kernel version

  -m, --machine            print the machine hardware name

  -p, --processor          print the processor type (non-portable)

  -i, --hardware-platform  print the hardware platform (non-portable)

  -o, --operating-system   print the operating system

      --help     display this help and exit

      --version  output version information and exit



GNU coreutils online help: <https://www.gnu.org/software/coreutils/>

Full documentation at: <https://www.gnu.org/software/coreutils/uname>

or available locally via: info '(coreutils) uname invocation'

pi@RevPi10035982976:~ $ uname -a

Linux RevPi10035982976 5.10.103-rt62-v7l #1 SMP PREEMPT_RT Tue, 24 May 2022 11:41:05 +0000 armv7l GNU/Linux

pi@RevPi10035982976:~ $

Re: Revpi core S and jessie image

Posted: 17 Dec 2022, 15:01
by chi.pham
Nicolai,
previous responses were from fresh install image.
i do the upgrade using "sudo apt update and sudo apt-get upgrade " and now could not find the command "revpi-factory-reset"

here are the responses:

Code: Select all

Updating PPD files for gutenprint ...

Updating PPD files for hpcups ...

Updating PPD files for postscript-hp ...

Processing triggers for libc-bin (2.28-10+rpt2+rpi1+deb10u1) ...

Processing triggers for systemd (241-7~deb10u8+rpi1) ...

Processing triggers for man-db (2.8.5-2) ...

Processing triggers for libgdk-pixbuf2.0-0:armhf (2.38.1+dfsg-1) ...

Processing triggers for install-info (6.5.0.dfsg.1-4+b1) ...

Processing triggers for desktop-file-utils (0.23-4) ...

Processing triggers for mime-support (3.62) ...

Processing triggers for initramfs-tools (0.133+deb10u1) ...

Processing triggers for hicolor-icon-theme (0.17-2) ...

Processing triggers for gnome-menus (3.31.4-3) ...

pi@RevPi10035982976:~ $ uname -a

Linux RevPi10035982976 5.10.103-rt62-v7l #1 SMP PREEMPT_RT Tue, 24 May 2022 11:41:05 +0000 armv7l GNU/Linux

pi@RevPi10035982976:~ $ piSerial -p

ERROR: Can't open file `/dev/i2c-1': No such file or directory

ERROR: FATAL: Can't get serial number from device

pi@RevPi10035982976:~ $ piSerial -v

PiSerial 3.0.0

pi@RevPi10035982976:~ $ piSerial 

ERROR: Can't open file `/dev/i2c-1': No such file or directory

ERROR: FATAL: Can't get serial number from device

pi@RevPi10035982976:~ $ sudo revpi-factory-reset core-se 10035982976 c83e-a710-2c61

sudo: revpi-factory-reset: command not found

pi@RevPi10035982976:~ $ sudo revpi-factory-reset

sudo: revpi-factory-reset: command not found

pi@RevPi10035982976:~ $ sudo revpi-factory-rest

sudo: revpi-factory-rest: command not found

pi@RevPi10035982976:~ $ find / -name factory-reset 2>dev/null

-bash: dev/null: No such file or directory

pi@RevPi10035982976:~ $ find / -name factory-reset 2>/dev/null

pi@RevPi10035982976:~ $ find / -name revpi-factory-reset 2>/dev/null

Re: Revpi core S and jessie image

Posted: 17 Dec 2022, 15:21
by chi.pham
using "sudo raspi-config" to enable I2c. and here the response. Is i2c file correct attribute?

Code: Select all

[b]crw-rw---- 1 root i2c      89,   1 Dec 17 15:10 i2c-1[/b]



pi@RevPi10035982976:~ $ piSerial -p

WARNING: Can't write to `/dev/i2c-1': Remote I/O error

WARNING: Can't write to `/dev/i2c-1': Remote I/O error

WARNING: Can't write to `/dev/i2c-1': Remote I/O error

WARNING: Can't write to `/dev/i2c-1': Remote I/O error

WARNING: Can't write to `/dev/i2c-1': Remote I/O error

ERROR: FATAL: Can't get serial number from device

pi@RevPi10035982976:~ $


Re: Revpi core S and jessie image

Posted: 17 Dec 2022, 15:33
by nicolaiB
In the future please format the output with code tags for better readability. I took the liberty and fixed it in your last posts.

You don't have a Core SE, so please don't select the SE model during factory reset. The correct model ist core.

BTW: Looks like you put the product number into the serial. See https://revolutionpi.com/hrf_faq/where- ... my-device/

Nicolai

Re: Revpi core S and jessie image

Posted: 17 Dec 2022, 17:58
by chi.pham
Nicolai,
Sorry for the confused response. I finally got it. I reload the image and use picore instead picore se and it works

Thanks