New experimental DuetPi Bookworm builds available

fractalengineer

@chrishamm Ok I just installed it on a fresh card; A couple issues:

My HDMI display shows a black, unresponsive screen after bootup despite showing the Duet bg and boot sequence just fine. Display manager service checked and active
Likewise, VNC is not connecting despite the service being turned on
I have full access through SSH though, through which I performed a git init, remote add and fetch origin in /sd to get my backup from my github backup; all is well, however...
It appears the file permissions are all bonked out; config refuses to load with this message: Error in start-up file config.g line 29: Access to the path '/opt/dsf/sd/sys/eventlog.txt' is denied. >>> This is a know issue I previously sorted out by doing sudo chmod 777 -R /opt/dsf/sd but there has to be a better way right

Any tips on fixing these quirks? Thanks!

fractalengineer

bump couldn't figure it out still

chrishamm

@fractalengineer said in New experimental DuetPi Bookworm builds available:

My HDMI display shows a black, unresponsive screen after bootup despite showing the Duet bg and boot sequence just fine. Display manager service checked and active

My DSI and HDMI screens came up straight without any problems. Maybe you need to configure your HDMI settings manually via config.txt? See here.

@fractalengineer said in New experimental DuetPi Bookworm builds available:

Likewise, VNC is not connecting despite the service being turned on

RaspPi OS based on Bookworm does not use RealVNC any more by default, instead it uses WayVNC. To get RealVNC working again, you need to turn off Wayland support via raspi-config in the advanced settings. However, that will probably make the display a bit slower than it needs to be (Wayland is faster than X11).

@fractalengineer said in New experimental DuetPi Bookworm builds available:

I have full access through SSH though, through which I performed a git init, remote add and fetch origin in /sd to get my backup from my github backup; all is well, however...

It appears the file permissions are all bonked out; config refuses to load with this message: Error in start-up file config.g line 29: Access to the path '/opt/dsf/sd/sys/eventlog.txt' is denied. >>> This is a know issue I previously sorted out by doing sudo chmod 777 -R /opt/dsf/sd but there has to be a better way right

It sounds like neither the dsf user or group can access your files in /opt/dsf/sd. If you cloned your repo as root, that's likely to happen. Instead of messing with chmod, it's better to call sudo chown -R dsf:dsf /opt/dsf/sd to fix the ownership permissions if needed.

printerguy3d

I have both HDMI and DSI connected, neither work. DSI shows just black screen. HDMI shows desktop background like extended monitor. This is with a 3b+, does this only work with a 4?

chrishamm

@printerguy3d It should work as well with a 3B+. Does your display work with the official RPi Bookworm image as expected? I don't think the new DuetPi image should be too different from it.

printerguy3d

@printerguy3d also of note, if i unplug the DSI monitor, the HDMI screen is also blank after boot.

printerguy3d

this makes the dsi screen work...

placing the directive in boot/confix.txt

dtoverlay=vc4-kms-dsi-7inch,invx,invy

and disabling the entry:

display_auto_detect=1

putting the hash sign # at the beginning

#display_auto_detect=1

printerguy3d

OK. so now bookworm loads and I have the board connected. When the Duet2 board runs 3.4.6 it gives an error that the versions are incompatible. When I update the board with Bossa to 3.5r3, it says it can't find the host. What can I do to get you access to take a look....

fractalengineer

@chrishamm interesting; just flashed latest vanila raspios bookworm and the screen works out of the box (but not the touchscreen?)

Meanwhile I'm unable to access VNC, neither through Tiger or RealVNC with both wayland and X11, even while confirmed running hmm

chrishamm

@fractalengineer I just checked and with the Wayland desktop it's possible to enable wayvnc (sudo systemctl enable --now wayvnc) and to connect using the TigerVNC client (other VNC clients may work as well).

With X11 it's a bit more difficult and apparently VNC doesn't work out of the box (yet?). This seems to be an issue in RaspiOS, too, see https://github.com/raspberrypi/bookworm-feedback/issues/41 But I could get it working on my setup by:

installing libraspberrypi0 (sudo apt install libraspberrypi0),
downloading the missing .so files via wget as described later in the GitHub issue,
enabling VNC via raspi-config

gitbls created this issue in raspberrypi/bookworm-feedback

closed RealVNC on 32-bit RasPiOS issue #41

fractalengineer

@chrishamm Ok great that definitely did something;

Now I can connect on both RealVNC and TigerVNC... But all I get is a grey screen in both cases

Such is the case on both duetpi and the official pi release, both updated to latest (I have them both on separate SD cards now to cross test)

HDMI display still shows on official release (still no touchscreen) and black on Duetpi

The search continues

oozeBot

@chrishamm will you be releasing instructions on how to "roll your own" copy of DuetPi for bookworm? We have a custom version but I've not been able to get it to connect with the old instruction set as I'm receiving:

Setting up reprapfirmware (3.4.6-3) ...
[fatal] Could not connect to Duet: Timeout while waiting for transfer ready pin

In the meantime, I'm flashing one of your builds onto an SD for testing now.

Thanks!

chrishamm

@oozeBot No, I don't plan to provide more documentation than there already is on GitHub but Duet3D can provide extra consultancy under certain conditions. If you're interested, feel free to contact info@duet3d.com.

oozeBot

@chrishamm - I was able to get past my issue. The documentation ( https://docs.duet3d.com/User_manual/Machine_configuration/DSF_Other#gpio-transfer-ready-pin ) states The following steps can be skipped if a Raspberry Pi is used. That does not appear to be valid for the Raspberry Pi 5 as I had to switch to gpiochip4 instead of the default gpiochip0. Thanks

chrishamm

@oozeBot Right, the Bookworm build uses a startup script to determine if it's running on a Pi 5. If it is, it makes those adjustments automatically. I'll update the documentation.

oozeBot

@chrishamm said in New experimental DuetPi Bookworm builds available:

@oozeBot Right, the Bookworm build uses a startup script to determine if it's running on a Pi 5. If it is, it makes those adjustments automatically. I'll update the documentation.

Thanks. I just added something similar within duetcontrolserver's postinst script to do the same.

p8blr

Any ideas what might be causing this "incompatible software versions error?"

Also I'm running this on a Raspberry Pi 5 8GB with an NVMe hat and noticed that I'm getting freezing every few seconds. Any ideas there?

Untitled picture.png

chrishamm

@p8blr Either you don't have all three RRF/DSF/DWC versions in sync (ideally only all updated by apt) or your browser is still using a cached DWC version. Try pressing Ctrl+Shift+R in your browser and check if that helps.

I haven't noticed any occasional freezes on my setups.

p8blr

@chrishamm I just installed a fresh image, and ran sudo apt update & sudo apt dist-upgrade, also ctrl+shift+r and am getting the same message. I updated the eeprom on the raspberry pi so hopefully that'll resolve the freezing issue.

running M997 S2 gives "Error: M997: Failed to perform update: Upgrade process return non-zero exit code"

Update: the issue seems to be that the sudo apt update/upgrade commands aren't doing anything regarding the duet board firmware. I confirmed this by connecting a Raspberry Pi 4 and running the commands again, and it was able to upgrade

However, after upgrading I still get this "incompatible software versions" popup no matter how many times I ctrl+F5. Note, this is on the raspberry pi itself with a monitor attached.

Also for the life of me, I can't get M997 S2 to work.

Edit: Just an update for anybody with a similar issue, I went back to a raspbery pi 4 with a SD card and updated to the latest firmware, then copy/pasted my sys and macros over to a newly imaged NVMe and that did the trick. My best guess is that it was the drive I was using. TeamGroup MP33 stalled but a Patriot P310 seems to work fine.

kiendeleo

With Duet 3.5.0 being released, I decided I would run

apt update && apt upgrade

on my RPI5. I am getting the following errors.

rr:1 https://pkg.duet3d.com stable/armv7 arm64 duetpimanagementplugin arm64 3.5.0~rc.4+2
  404  Not Found [IP: 134.209.94.168 443]
Err:2 https://pkg.duet3d.com stable/armv7 arm64 duetpluginservice arm64 3.5.0~rc.4+2
  404  Not Found [IP: 134.209.94.168 443]
Err:3 https://pkg.duet3d.com stable/armv7 arm64 duetsoftwareframework arm64 3.5.0~rc.4+2
  404  Not Found [IP: 134.209.94.168 443]
Err:4 https://pkg.duet3d.com stable/armv7 arm64 duettools arm64 3.5.0~rc.4+2
  404  Not Found [IP: 134.209.94.168 443]
Err:5 https://pkg.duet3d.com stable/armv7 arm64 duetcontrolserver arm64 3.5.0~rc.4+2
  404  Not Found [IP: 134.209.94.168 443]
Err:6 https://pkg.duet3d.com stable/armv7 arm64 duetruntime arm64 3.5.0~rc.4+2
  404  Not Found [IP: 134.209.94.168 443]
Err:7 https://pkg.duet3d.com stable/armv7 arm64 duetwebserver arm64 3.5.0~rc.4+2
  404  Not Found [IP: 134.209.94.168 443]
Ign:8 https://pkg.duet3d.com stable/armv7 arm64 reprapfirmware all 3.5.0~rc.4+2-1
Err:8 https://pkg.duet3d.com stable/armv7 arm64 reprapfirmware all 3.5.0~rc.4+2-1
  404  Not Found [IP: 134.209.94.168 443]
E: Failed to fetch https://pkg.duet3d.com/dists/stable/armv7/binary-arm64/duetpimanagementplugin_3.5.0%7erc.4%2b2_arm64.deb  404  Not Found [IP: 134.209.94.168 443]
E: Failed to fetch https://pkg.duet3d.com/dists/stable/armv7/binary-arm64/duetpluginservice_3.5.0%7erc.4%2b2_arm64.deb  404  Not Found [IP: 134.209.94.168 443]
E: Failed to fetch https://pkg.duet3d.com/dists/stable/armv7/binary-arm64/duetsoftwareframework_3.5.0%7erc.4%2b2_arm64.deb  404  Not Found [IP: 134.209.94.168 443]
E: Failed to fetch https://pkg.duet3d.com/dists/stable/armv7/binary-arm64/duettools_3.5.0%7erc.4%2b2_arm64.deb  404  Not Found [IP: 134.209.94.168 443]
E: Failed to fetch https://pkg.duet3d.com/dists/stable/armv7/binary-arm64/duetcontrolserver_3.5.0%7erc.4%2b2_arm64.deb  404  Not Found [IP: 134.209.94.168 443]
E: Failed to fetch https://pkg.duet3d.com/dists/stable/armv7/binary-arm64/duetruntime_3.5.0%7erc.4%2b2_arm64.deb  404  Not Found [IP: 134.209.94.168 443]
E: Failed to fetch https://pkg.duet3d.com/dists/stable/armv7/binary-arm64/duetwebserver_3.5.0%7erc.4%2b2_arm64.deb  404  Not Found [IP: 134.209.94.168 443]
E: Failed to fetch https://pkg.duet3d.com/dists/stable/armv7/binary-armhf/reprapfirmware_3.5.0%7erc.4%2b2-1_all.deb  404  Not Found [IP: 134.209.94.168 443]
E: Unable to fetch some archives, maybe run apt-get update or try with --fix-missing?

Is this something wrong on my end?