LinuxQuestions.org - [SOLVED] Raspberry Pi 4 bcm2711 (aarch64)

- Slackware - ARM (https://www.linuxquestions.org/questions/slackware-arm-108/)

- - Raspberry Pi 4 bcm2711 (aarch64) (https://www.linuxquestions.org/questions/slackware-arm-108/raspberry-pi-4-bcm2711-aarch64-4175675454/)

Quote:

Originally Posted by glorsplitz (Post 6211551)

shot-1970-01-01_00-39-59.jpg, you didn't run ntp?

is mpv part of base install?

i have not connected to the network, ntp is set to work.
yes, mpv is included in prebuilt builds.

Quote:

Originally Posted by sndwvs (Post 6211466)

the desktop was also replaced with enlightenment.

So you mean that whoever wants to keep using Xfce, will have to use the base installer image, and install the Xfce related packages manually?

Quote:

Originally Posted by wowbaggerHU (Post 6211633)

So you mean that whoever wants to keep using Xfce, will have to use the base installer image, and install the Xfce related packages manually?

for a given image, yes.
but globally you can build with both xfce and enlightenment, this is just the first build with enlightenment.

Quote:

Originally Posted by sndwvs (Post 6211637)

for a given image, yes.
but globally you can build with both xfce and enlightenment, this is just the first build with enlightenment.

Hi sndwvs, that's understandable. Thank you for the explanation.

update kernel 5.12.0

Hi sndwvs,

I don't wish to sidetrack this thread, but I encountered a previously unknown problem (at least for me).
I have a 4 GB raspberry pi 4, and I would like to use an RTC. I own a number of them, and they all are this model.

Until now used them happily but I recently switched from a 2 GB to a 4 GB RPi4, and also upgraded to kernel 5.10.0.
The problem is that:

In /boot/config.txt, I have

Code:

dtparam=i2c_arm=on

dtoverlay=disable-vc4,i2c-rtc,ds3231

And the device shows up in i2cdetect's output:

Code:

root@raspberry-pi-4:~# i2cdetect -y 1

    0  1  2  3  4  5  6  7  8  9  a  b  c  d  e  f

00:                        -- -- -- -- -- -- -- -- 

10: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- 

20: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- 

30: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- 

40: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- 

50: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- 

60: -- -- -- -- -- -- -- -- 68 -- -- -- -- -- -- -- 

70: -- -- -- -- -- -- -- --

So it seems to be connected to the RPi4 properly.
However when I try to execute the usual commands to activate the RTC,

Code:

lsmod | grep -q i2c-bcm2708 || modprobe i2c-bcm2708

cat <<<"ds1307 0x68" >/sys/class/i2c-adapter/i2c-1/new_device

sleep 1

[ -c /dev/rtc0 ] && hwclock --hctosys

I get this:

Code:

[  11.711634] IPv6: ADDRCONF(NETDEV_CHANGE): eth0: link becomes ready

[  18.839442] random: crng init done

[  19.164643] i2c i2c-1: new_device: Instantiated device ds1307 at 0x68

[  19.174771] rtc-ds1307: probe of 1-0068 failed with error -121

On my second attempt, I'm greeted with this:

Code:

[  88.940468] i2c /dev entries driver

[  137.524802] i2c i2c-1: Failed to register i2c client ds1307 at 0x68 (-16)

Do you happen to have any tips on this?
I already spent a few hours googling around, but wasn't able to fix the problem.

Hi wowbaggerHU,
here is a similar problem

Code:

dtoverlay=i2c-rtc,ds1307,addr=0x58

Quote:

Originally Posted by sndwvs (Post 6251459)

Code:

dtoverlay=i2c-rtc,ds1307,addr=0x58

Well, it either was a contact problem (that was fixed by now through the many disassembly-reassembly cycles), or the one you mentioned, but it works now.
Although I have to point out that the address had to be (or was) corrected to 0x68.

Either way, thank you for helping me out!

update kernel 5.13.0

On a similar theme, I've noticed a lot of new files going in to Slarm64 recently (I rsync a local NAS with Slackware.UK), but slackpkg isn't detecting them. It looks as if the changelog isn't getting updated, nor are the checksums, which are throwing up md5 errors.

Not criticising, as I know its a lot of work! Just flagging up in case you were unaware.

Slackware64-curent from the same source is fine.

--
Pete