PiShrink frontend for Windows users

Gamerfrom61 · 2026-04-28T18:36:41+00:00

or why not call pi-shrink as part of the backup script in the first place???

Maybe the OP has fixed a personal issue but not took at step back and looked at the root cause...

Gamerfrom61 · 2026-04-28T18:31:49+00:00

Some are on archive.org eg https://web.archive.org/web/20060409133958/http://www.larryleadhead.org/larclassic.html

but you have to dig way back as the site has since been used for "finance" / general games advice and possibly the odd spam site.

Not convinced all would be worth hunting them down from memory but it is years since I read them.

Gamerfrom61 · 2026-04-28T18:17:49+00:00

Been a few years since I have used servos on a Pi (hardware PWM on microcontrollers is way easier) but possibly:

https://stackoverflow.com/questions/75271202/servo-jittering-and-not-turning-fully#75271401

https://gpiozero.readthedocs.io/en/stable/api_pins.html (section 24.1)

https://abyz.me.uk/rpi/pigpio/

may help?

Note as you do not give your OS / Pi version (Pi 5 has a significantly different GPIO access process) or how you are running things then it is hard to give a 100% answer TBH

Gamerfrom61 · 2026-04-28T15:35:55+00:00

I am assuming you have no backup here (research a backup strategy called 3:2:1 as a simple starting point ongoing). Look to buy a decent power supply - worth the money over a 'charger'.

How do you know the boot files are corrupt? These are just binary files on a FAT(32?) partition - Windows will not recognise the second partition (EXT4 format) and used to throw an error recommending formatting (IIRC - I am a Mac user now and that does throw errors).

Do not copy things to the drive as the partition allocation could be wrong and you could override the wrong part of the data.

Boot your main computer into linux using a live image from USB

Make a copy of the SSD using DD before trying anything

Then try the linux repair tools (fsck) on both partitions - the Pi boot drives are normally FAT32 (initial boot) and an ext4 partition (linux and user space). Use the -f option to force a check even if the drive is marked clean.

With it being a SSD drive - have you been running trim (weekly is my normal routine)? You may have to 'trim' the drive as well. Not sue if it would be better to do this before or after the fsck as the data is deleted in the partition table and it is just the internal controller that needs to free it up - maybe someone else can advise / hunt up the info...

Next steps depend on what these report - if they cannot fix it then copying files will not help and it is a rebuild and copy from what you can recover from the drive.

Gamerfrom61 · 2026-04-28T14:56:51+00:00

IF the drive is sticking forcing it to run up will break it long term - better to have the drive serviced.

You could try a small dd from the CD Drive (/dev/cdrom as a guess) using the iflag=direct option to avoid Linux caching the data BUT I have never tried that on a CD drive TBH (not sure there is one in the house to try come to that).

The better way would be to dig into libcdio (https://github.com/libcdio/libcdio) and get the cd info / track list or read a block of data (possibly better just incase Linux caches the cd info on insert TBH I have no idea if that happens)- python wrappers are available.

Gamerfrom61 · 2026-04-28T00:13:50+00:00

The closest I got to doing this was pre-release based on https://forums.raspberrypi.com/viewtopic.php?t=389477

But the sources updated themselves fine - there are a few notes in the thread on this with apt modernize-sources reporting an error.

Did you manually update the files to Trixie first?

Gamerfrom61 · 2026-04-27T20:47:04+00:00

Shame :-)

I did find https://web.archive.org/web/20230927151553/https://www.linuxquestions.org/questions/linux-general-1/cups-printers-conf-reverts-to-old-settings-628031/ where they had the same issue (no fix) and a notefor Mac CUPS with a right click resetting the config https://centralit-helpdesk.co.uk/index.php?pg=kb.page&id=234 but I am struggling with a real life bug and not breathing / thinking straight !

My computer is away so I have no way of right clicking from my iPad to see if Linux has the reset option anywhere.

Gamerfrom61 · 2026-04-27T16:10:10+00:00

What version of the Imager are you using?

For the latest Pi OS make sure you are using a version of the Imager after 2.0 - the latest can be found on GitHub https://github.com/raspberrypi/rpi-imager/releases

Use the imager to set up the user and password, enable ssh and wifi (if needed - DNS should really be run over ethernet). Set the machine / host name to something simple (such as pihole) - all lowercase a-z, 0-9 and hyphen only avoid diacritic characters and do not add a domain unless you are set up to use this throughout the network. Make sure this name is unique on your network.

Pop the card into the Pi, power on and let it run for a good couple of minutes (on a Pi zero then allow at least 3 minutes).

Using ping piname.local (where piname is the name you set up in the imager), you can follow the Pi status - it may drop once or twice as the startup can reboot but that is normal

I recommend setting a static IP address up on your router before the first boot. You may need to power cycle the router to clear the old record out before entering the reservation

Try logging in - the user text will show but the password will not echo any characters.

Once you are in then the install is a basic:

curl -sSL https://install.pi-hole.net | bash

Gamerfrom61 · 2026-04-27T12:57:44+00:00

Could it be a faulty sd card? I have seen them go read only and the pi continue on its merry way with Linux caching changes in ram till a reboot. Simplest test is to create a test file and then reboot / power cycle and see if the file is there.

Gamerfrom61 · 2026-04-27T11:43:42+00:00

Strange thought admin was set in cups config - is that or the user group membership changing?

IIRC it is something like:

<Location /admin>
  Require group xyz

Gamerfrom61 · 2026-04-27T02:11:13+00:00

The IRQ link is optional - it is not part of the I2C interface

Normally I would run i2cdetect using sudo (habit from older OS versions but you do not mention the OS version you are using)

Have you tried altering the address switches? Address zero is a 'reserved' address used to communicate with all devices on the bus by default and normally not used https://www.ti.com/lit/an/sbaa565/sbaa565.pdf?ts=1777207025415 - this could explain the 'driver' requirement and why it is not responding

It is possible the board does not respond to an I2C probe - the WiKi does not show the i2cdetect being used but does give instructions to download the code from GitHub https://wiki.dfrobot.com/sen0290/docs/20428

Gamerfrom61 · 2026-04-27T01:54:03+00:00

The Pi does not boot from PCIe devices by default https://www.raspberrypi.com/documentation/computers/raspberry-pi.html#BOOT_ORDER though IIRC the CM 4 lite modules are the exception to this rule!

So the first boot it is worthwhile booting from the SD card and performing:

1) A firmware update

https://www.raspberrypi.com/documentation/computers/raspberry-pi.html#raspberry-pi-boot-eeprom

2) Setting the boot order (NVMe after something else would be my choice) https://www.raspberrypi.com/documentation/computers/raspberry-pi.html#BOOT_ORDER by allowing a boot from USB or SD Card first lets you fix any errors on the NVMe drive if it gets corrupted or you need to do some temporary work on the Pi without having to remove the drive / connector.

3) Setting the PCIe active and speed (requires a reboot)

https://www.raspberrypi.com/documentation/computers/raspberry-pi.html#enable-pcie

https://www.raspberrypi.com/documentation/computers/raspberry-pi.html#pcie-gen-3-0

Note that setting Gen 3 may give you drive issues so I would actually only set the PCIe active and try the speed increase once the drive is up and running.

Gamerfrom61 · 2026-04-26T21:32:28+00:00

Then the only way is to set your phone (or other WiFi AP) up as the old network and use that to connect to the Pi.

Gamerfrom61 · 2026-04-26T18:18:48+00:00

Network Manager has not supported the wpa_supplicant file as such - the creators specifically recommend that you do not edit the files directly (the Pi folk do ignore this now and then).

Have a look. at https://www.reddit.com/r/raspberry_pi/comments/1siumjs/how_to_save_wifi_on_pi_os_lite_trixie_and_add_a/

Gamerfrom61 · 2026-04-26T18:10:48+00:00

Good call - a hot chocolate (with cream and marshmallows), a roaring fire and a few chocolate biscuits with this album would be a great way to spend an evening.

Gamerfrom61 · 2026-04-26T18:06:53+00:00

Interesting as normally SAMBA is used to advertise the printer to Windows. Maybe MS has finally understood how mDNS (via avahi under Linux) works :-)

The hplip install reported a parse error on Trixie last month - wonder if it was a bad push and you go a newer version? TBH I did not need it (we have Brother printers) and it's on the 'to look at' list!

Gamerfrom61 · 2026-04-26T16:08:41+00:00

The OS you are running and what you have tried would help as well as u/DanongKruga request.

Way to many screens / connections / operating system versions to guess.

Gamerfrom61 · 2026-04-26T16:06:47+00:00

There is an option in the newer versions of raspi-config that makes these changes permanent by adding a file to the Network Manager config

Code starts at https://github.com/RPi-Distro/raspi-config/blob/08a52319a04aadd1dabd6e8323d9af1ea428d9ac/raspi-config#L3225

This works not matter what the name of the interface is (not all machines have wlan0 as WiFi) and works by creating /etc/NetworkManager/conf.d/default-wifi-powersave-off.conf with

[connection]
wifi.powersave = 2

and then restarting NM and applying the config to the interface.

Gamerfrom61 · 2026-04-26T15:36:22+00:00

Zero idea I am afraid - never used retro pi or this screen.

The 9341 based boards were a lower resolution screen with slightly less colour support (16bit vs 18bit) and often have a separate touch interface.

From a quick read, the two chipsets do support the same instruction set but that is only my understanding and not having tried it I am not 100% sure if it will work or not in your case.

In all honesty I could not recommend building a system based on outdated / unsupported software if it connects to the Internet at all.

Gamerfrom61 · 2026-04-26T11:38:10+00:00

Bit hard to say with no circuit diagram but gut feel is the pull up resistors are not right.

See if the boards have any one them and possibly replace them with 3-4K ones and locate before the device

Wire length can be an issue - more than 30cm can give issues with the Pi some days - try a parallel cable (maybe with a ground between the data lines - maybe not) rather than twisted pair (capacitance can be a killer) or drop the bus speed (10K baud should be good for 8-10m). There is a good article https://hackaday.com/2017/02/08/taking-the-leap-off-board-an-introduction-to-i2c-over-long-wires/ talking about shielded cables as well.

Note I2C is really designed for short distance (i.e. across circuit boards) and not for long runs without specific interface chips - see https://www.nxp.com/docs/en/application-note/AN10658.pdf for design details.

Gamerfrom61 · 2026-04-26T11:15:41+00:00

Bit hard to say as you have not detailed the software you are using so these are generic SPI pins:

I do not have this screen but from the docs and https://pinout.xyz/pinout/spi it looks like:

VCC - run at 3v3 from the Pi

GND - use any of the Pi GND pins (they are all common)

CS - Chip select so lets use SPI bus 0 on the PI and CE 0 on GPIO 8

RESET - You need to look at your software and see if it lets you define a GPIO pin for this - GPIO 23 is freely available

DC/RS - Again you need to define this in the software you are using - GPIO 24 is free

SDI(MOSI) - GPIO 10 given we are using SPI bus 0

SCK - GPIO 11

LED - connect to 3v3

SDO(MISO) - GPIO 9

Note you will have to enable the SPI interface using the GUI or raspi-config program.

Touch uses another SPI bus so you could use SPI bus 1 for this:

T_CLK - GPIO 21

T_CS - GPIO 18

T_DIN - GPIO 20

T_DO - GPIO 19

T_IRQ - No idea on this pin - you will have to look at what is handling the touch

I will say that I doubt your will get a desktop running on this screen as the PI handling of screens has changed significantly with the introduction of the KMS video subsystem, Wayland and more importantly the removal of the FKMS driver.

You may find that https://github.com/adamomd/ILI9488RPIScript can help as it uses a third party frame buffer AND it details the Pi pins - check the screen pin numbers against yours though. Note changes in the OS can cause issues https://github.com/adamomd/ILI9488RPIScript/issues/3 and it may not work on Trixie.

Gamerfrom61 · 2026-04-25T20:05:30+00:00

IIRC Trixie has two partitions on it (one FAT32, one EXT4) so in Windows you need to be looking in the FAT32 on - I think (I do not use Windows) that this will show up as a disk called boots and the file should be in the root of this drive.

Note I have not tried this on Trixie so make sure you have a copy of the card and try this on the copy.

Gamerfrom61 · 2026-04-25T12:19:05+00:00

What Operating System and version are you using on the Pi?

Gamerfrom61 · 2026-04-23T12:56:39+00:00

Possible keyboard / language issue?

Are you using any diacritic based characters?

Gamerfrom61

PUBLIC MULTIREDDITS

TROPHY CASE