thagrol / guides Goto Github PK

Add network manager instructions.
Check initrd stuff

Add instruction for including "dtparam=sd_poll_once=on" to config.txt to avoid potential CPU overhead of repeatedly check for the presence of an SD card.

First thanks, for those excellent guides!

I wonder if there is any chance to have them available on a website where we can directly link to individual chapters? Currently, I see no way of pointing someone to specific information.

Advatages

BTW thanks for all great guides!

Is it possible to present just a normal text file to the USB host?
I want to pass a script so the user can go sh /dev/something.
(And the script will execute commands passed by serial.)

Thank you.

Replace bullseye instructions in point 3 section 4.4 with:

nft add table nat
nft -- add chain nat prerouting
nft -- add chain nat postrouting
nft add rule ip nat postrouting oifname "eth0" counter masquerade

As suggested at

https://forums.raspberrypi.com/viewtopic.php?p=1987314#p1987314

here is an issue to add the user and password migration instructions

1. Edit the /etc/passwd on the new system and paste the entries for the users copied from the same file on the old system
2. Same for /etc/shadow
3. Copy the file /var/lib/samba/private/passdb.tdb from the old to the new system
4. sudo systemctl restart smbd

as in

https://forums.raspberrypi.com/viewtopic.php?p=1987216#p1987216

to nas.pdf maybe as Section 11.4 or maybe not.

When ethernet gadget is plugged into a Pi that is connected to wireless repeater, its nameserver is set to localhost (/etc/resolve.conf), and name resolution on the gadget does not work:
https://www.raspberrypi.org/forums/viewtopic.php?f=91&t=306121&p=1912854#p1912787

There might be a better solution, I just added a valid nameserver IP address to the ethernet gadget, and that worked.

As you highlighted, using internet nameserver cannot resolve name of wireless repeater and other computers of internal network. The Pi the ethernet gadget is plugged in uses the wireless repeater as DNS server, perhaps the ethernet gadget can do so as well? Alternatively perhaps the Pi where the gadget is plugged into can forward the gadget DNS requests ...

Great guide!

In section 6.2.1, sudo usemod -L username should be sudo usermod -L username

Hello.
In 2.4 it mentions bullseye has smb v1 disabled.

Does that mean I don't need to install smb v1 on Win10 clients nor install wssd on the Pi ?

Is it possible to present just a normal text file to the USB host?
I want to pass a script so the user can go sh /dev/something.
(And the script will execute commands passed by serial.)

Thank you.

Add network manager

NFS troubleshooting add to check whether all packages including nfs-kernel-server are installed.

I have read the entire pdf, and associated forums where people have specific problems. All I want is for a specific gpio pin (17) to start in mode "a3" on boot. I can get the pin when set as an output to not trigger on boot, as it is "on" when booted and I have a script that sets it to not on on boot. However, simply adding "@reboot raspi-gpio set 17 a3" does not actually set the pin to a3 mode unless I run that command inthe command window as raspi-gpio set 17 a3...

Is there a simple way to just write in the command into the boot config.txt file i am running?

thank you for your time and efforts!

Hi, thanks for the guide, it's very helpful.

I've been using the mass-storage-gadget guide and found that the script in section 5.3.4 would not work every time.

ls: write error: Device or resource busy

I added an intentional delay before the last line and it seems to work reliably now.

#!/bin/bash
# /sbin/modprobe g_mass_storage file=/dev/mmcblk0p3

modprobe libcomposite
mkdir -p /sys/kernel/config/usb_gadget/mygadget
cd /sys/kernel/config/usb_gadget/mygadget
echo 0x1d6b > idVendor
echo 0x0104 > idProduct
echo 0x0100 > bcdDevice
echo 0x0200 > bcdUSB
mkdir -p strings/0x409
echo "1234567890" > strings/0x409/serialnumber
echo "me" > strings/0x409/manufacturer
echo "My USB Device" > strings/0x409/product
mkdir -p configs/c.1/strings/0x409
echo "Config 1: Mass Storage" > configs/c.1/strings/0x409/configuration
echo 250 > configs/c.1/MaxPower
mkdir -p functions/mass_storage.usb0
echo 0 > functions/mass_storage.usb0/lun.0/cdrom
echo 0 > functions/mass_storage.usb0/lun.0/ro
echo /dev/mmcblk0p3 > functions/mass_storage.usb0/lun.0/file
ln -s functions/mass_storage.usb0 configs/c.1/
sleep 1  # required to make the following line work
ls /sys/class/udc > UDC

Hope this helps somebody.

"t" missing in last command "sudo netfilter-persistent save", also netfilter-persistent needs to be installed via apt.

Ref: USB Mass Storage Gadget
A Beginner's Guide

Section 7.2 Changing The Backing Store On The Fly, on page 30 -

"The risks and dangers are the same as those when disconnection any drive "

Perhaps that should be 'disconnecting' ?

See https://www.raspberrypi.org/forums/viewtopic.php?f=91&t=306121&p=1906932#p1906876

Consider adding software RAID to the NAS guide.

Bullseye has dropped iptables in favour of nftables.

Maybe you could add a comment, that the Path key is ignored on startup, when you execute the file manually it works. This is critical for apps which rely on data in the working directory.

Detailed information here: https://forums.raspberrypi.com/viewtopic.php?t=292120

As a workaround you can define a shell script, which first changes the directory and then executes the file, also described in the link above:

Exec=sh -c "cd /home/pi/folder; /home/pi/folder/script"

I'd suggest adding a few journalctl aliases to section 5.1. These obviously aren't complete, but will help people move forward instead of reflexively installing rsyslog.

For example:

    alias jc='journalctl --boot'         #Pager journal of current boot
    alias jca='journalctl'               #Undecorated journalctl operates on all boots, not just current boot
    alias jcf='journalctl --follow'      #Follow end of journal
    alias jcg='journalctl --boot --grep' #From current boot for specified message string
    alias jcr='journalctl --list-boots'  #List all the system boots

To look at the log from the previous boot, one would do sudo jc -1. More generally, to look at the Nth previous boot, sudo jc -N

Wayland autostart
Python venvs

Bullseye has dropped iptables in favour of nftables

python venvs

Hi thagrol.
I'm writing a simple command for the the Rasperry Pi USB On-The-Go functionality, so you can do echo "type Hello!" | gadget and the like.
I was wondering if it's possible to have the script configure everything at runtime, so you don't need to put dtoverlay=dwc2,dr_mode=peripheral and modules-load=dw2,g_hid in the /boot files.

I know there's modprobe and there seems to be a dtoverlay util on Rasperry Pi Os but not elsewhere (my Pi is on Void Linux).
I also found this page, where (right at the bottom) they use the /sys file system: https://www.96boards.org/documentation/consumer/dragonboard/dragonboard410c/guides/dt-overlays.md.html

Here's my little project is here if you're interested: https://git.sr.ht/~geb/gadget

Hello, when executing the last line of the libcomposite approach to using my Pi Zero W as a USB mass storage gadget, I get the following error:
‘’’
root@pi:/sys/kernel/config/usb_gadget/mygadget# ls /sys/class/udc > UDC
ls: write error: Invalid argument
‘’’

Do you have any tips for resolving this issue?

• Quick Wifi connection setup with nmcli:

  nmcli con add type wifi con-name FSL ssid FSL wifi-sec.key-mgmt wpa-psk wifi-sec.psk MixedFruitS@l@d save yes
  

• Possibly a new section for Firmware management differences (i.e. location of config.txt, cmdline.txt etc.):

  Firmware size/mountpoint differences
  Bullseye: First partition of SD containing the firmware is mounted on `/boot` , sized at 256M
  Bookworm: First partition of SD containing the firmware is mounted on `/boot/firmware` sized at 512M
  

• Headless logging optimization across all Pi's and OS version:

  For purely headless setups, the order of the 2 console options in the cmdline.txt is very important: the last of the options should be the serial console, so that all boot messages are redirected to serial console. The default setup causes the messages to be directed to /dev/tty1:
  Code:

  ... console=tty1 console=ttyAMA0,115200 ...
  

• A way of combining venv activation and python invocation into single shell command - helps when using multiple venv for tasks without affecting the parent shell environment:

  bash -c "source $VENV_ROOT/bin/activate ; python $PYTHON_SCRIPT"
  

  where the example of VENV_ROOT is /home/pi/.venv/ and example of 'PYTHON_SCRIPT is '/home/pi/SomeProgram.py