Differences

This shows you the differences between two versions of the page.

Link to this comparison view

Both sides previous revision Previous revision
Next revision		 Previous revision
raspberry-pi:ipfire-on-rpicm4 [2024/04/20 18:07] – [Open serial console using screen] Zyzonixraspberry-pi:ipfire-on-rpicm4 [2025/04/13 12:02] (current) – [Adjusting Interfaces (MAC Addresses) (important!)] Samsoneko
Line 22: Line 22:
   * //HDMI-Cable//   * //HDMI-Cable//
   * //Keyboard//   * //Keyboard//
 +  * //or USB2TTL Apdapter//
  
 ===== Download and flash the Image to the SD-Card ===== ===== Download and flash the Image to the SD-Card =====
Line 47: Line 48:
 Now connect the following pins on your carrier board's GPIO and your second Pi's GPIO with three jumper wires (female to female): Now connect the following pins on your carrier board's GPIO and your second Pi's GPIO with three jumper wires (female to female):
 <WRAP 40%> <WRAP 40%>
-^ Carrier Board (CM4)  ^ 2nd Raspberry Pi  ^ Use               ^ +^ Carrier Board (CM4)  ^ 2nd Raspberry Pi / USB2TTL  ^ Use               ^ 
-| **''6''**            | **''6''**         | Ground            | +| **''6''**            | **''6''** / **''GND''**     | Ground (GND)      | 
-| **''10''**           | **''8''**         | Receive and send  | +| **''10''**           | **''8''** / **''TX''**      | Receive and send  | 
-| **''8''**            | **''10''**        | Send and receive  |+| **''8''**            | **''10''** / **''RX''**     | Send and receive  |
 </WRAP> </WRAP>
  
Line 80: Line 81:
 Then you can execute the follwing command from the second Pi to connect to your serial console. **It's strongly recommended to use a local attached keyboard and monitor on a Pi that boots to CLI(!) rather than creating the serial connection via SSH / Desktop.** Then you can execute the follwing command from the second Pi to connect to your serial console. **It's strongly recommended to use a local attached keyboard and monitor on a Pi that boots to CLI(!) rather than creating the serial connection via SSH / Desktop.**
 <code bash>screen /dev/ttyS0 115200</code> <code bash>screen /dev/ttyS0 115200</code>
 +(root-permission required!)
 → you might install ''screen'' befire by running the following command: → you might install ''screen'' befire by running the following command:
 <code bash>sudo apt install screen</code> <code bash>sudo apt install screen</code>
Line 94: Line 96:
 **Select the 3rd option, that contains ''serial console''!** **Select the 3rd option, that contains ''serial console''!**
  
-===== Adjusting interfaces (important!) =====+===== Adjusting Interfaces (MAC Addresses) (important!) =====
  
 As described also in this [[https://community.ipfire.org/t/rpi-cm4-red-interface-not-available-after-reboot/7119/3|blog post]] in IPFire's official forum, there are assigment issues with the carrier board's NICs. It seems that the second PCIe NIC gets a self-assignet MAC everytime the device boots up. This is followed by the host OS no longer recognizing the NIC. To solve this issue there is a more or less fancy workaround here in this wiki: [[linux:linux-tutorials:set-persistent-mac-rtl8111|Set persistent MAC for RTL8111/8168/8411 (r8169) with udev]] (internal link). As described also in this [[https://community.ipfire.org/t/rpi-cm4-red-interface-not-available-after-reboot/7119/3|blog post]] in IPFire's official forum, there are assigment issues with the carrier board's NICs. It seems that the second PCIe NIC gets a self-assignet MAC everytime the device boots up. This is followed by the host OS no longer recognizing the NIC. To solve this issue there is a more or less fancy workaround here in this wiki: [[linux:linux-tutorials:set-persistent-mac-rtl8111|Set persistent MAC for RTL8111/8168/8411 (r8169) with udev]] (internal link).
  • raspberry-pi/ipfire-on-rpicm4.1713629271.txt.gz
  • Last modified: 2024/04/20 18:07
  • by Zyzonix