documentation:end-users_docs
Differences
This shows you the differences between two versions of the page.
| Both sides previous revisionPrevious revisionNext revision | Previous revision | ||
| documentation:end-users_docs [2019/06/04 15:24] – [Hardware Compatibility List] olivier | documentation:end-users_docs [2025/09/28 08:54] (current) – [Filename convention] olivier | ||
|---|---|---|---|
| Line 4: | Line 4: | ||
| ===== Hardware Compatibility List ===== | ===== Hardware Compatibility List ===== | ||
| - | For BSDRP you need: | + | To run BSDRP, you will need: |
| - | * a 2GB flash disk (Compact Flash, USB stick, mSATA flash module, etc.). | + | * A 4GB flash disk (such as Compact Flash, USB stick, |
| - | * a minimum | + | * At least 1GB of RAM. |
| - | [[https:// | + | All hardware supported by the latest |
| - | + | ||
| - | Wireless, PCMCIA | + | |
| ===== Filename convention ===== | ===== Filename convention ===== | ||
| - | The BSDRP images use this filename convention: | + | BSDRP image filenames follow |
| - | BSDRP_// | + | BSDRP_// |
| The value //image type// can be: | The value //image type// can be: | ||
| - | * full : To be used for installing BSDRP. This image contain | + | * full : For full installation, |
| - | * upgrade : To be used for upgrading BSDRP. This image contain | + | * upgrade : For system upgrades, includes |
| The value //arch// can be: | The value //arch// can be: | ||
| - | | + | * amd64 : For modern |
| - | | + | * aarch64 |
| - | + | ||
| - | The value //console// can be: | + | |
| - | * vga: To be used with a vga card and keyboard as default console (but it's still possible to connect to the serial port) | + | |
| - | * serial: For headless use, use only serial port as default console | + | |
| Examples: | Examples: | ||
| - | * BSDRP_0.3_full_i386_vga.img, means full image, for arch i386, with keyboard/ | + | * BSDRP_2.0_full_amd64.img: Full image for x86_64. |
| - | * BSDRP_0.3_upgrade_amd64_serial.img, means upgrade | + | * BSDRP_2.0_upgrade_aarch64.img: Upgrade |
| The *.mtree.xz files are used for system integrity check. | The *.mtree.xz files are used for system integrity check. | ||
| Line 41: | Line 35: | ||
| == Windows users == | == Windows users == | ||
| - | Here are the 2 steps for writing the image to a CF/USB removable media: | + | Here are the 2 steps for writing the image to a CF/flasg/USB removable media: |
| - | - Decompress the BSDRP image file [[http:// | + | - Decompress the BSDRP image using [[http:// |
| - | - Use [[http:// | + | - Use [[http:// |
| == *BSD or Linux users == | == *BSD or Linux users == | ||
| - | Connect your Compact Flash or USB disk and write down the device name (can be ' | + | Connect your flash or USB drive and note its device name. |
| - | + | Decompress the image and copy it to your drive using a byte copy command. | |
| - | Then unzip the file and byte copy it to your drive (**Warning: | + | Then unzip the file and byte copy it to your drive (**Warning: |
| < | < | ||
| xzcat BSDRP_full_amd64_vga.1.0.img.xz | dd of=/dev/sd4 bs=256k | xzcat BSDRP_full_amd64_vga.1.0.img.xz | dd of=/dev/sd4 bs=256k | ||
| Line 58: | Line 52: | ||
| == Mac OS X users == | == Mac OS X users == | ||
| - | Insert the USB key, and run mount in a terminal | + | Insert the USB key, and display list of external devices: |
| + | |||
| + | < | ||
| + | % diskutil list | grep external | ||
| + | / | ||
| + | </ | ||
| + | |||
| + | Check if it is already mounted | ||
| < | < | ||
| + | % mount | grep '/ | ||
| / | / | ||
| devfs on /dev (devfs, local) | devfs on /dev (devfs, local) | ||
| Line 68: | Line 70: | ||
| / | / | ||
| </ | </ | ||
| - | The last line is your USB device. Unmount it and write the BSDRP image to it with: | + | The last line is your USB device. Unmount it and write the BSDRP image to the device adding the ' |
| < | < | ||
| sudo umount -f / | sudo umount -f / | ||
| - | xzcat BSDRP_full_amd64_vga.1.0.img.xz | dd of=/dev/disk3 bs=256k | + | xzcat BSDRP_full_amd64_vga.1.0.img.xz | sudo dd of=/dev/rdisk3 |
| </ | </ | ||
| - | If successful, OSX will pop up an error dialog telling you it doesn' | + | If successful, OSX will pop up an error dialog telling you it doesn' |
| === To an hard drive === | === To an hard drive === | ||
| Line 187: | Line 189: | ||
| < | < | ||
| fetch ' | fetch ' | ||
| + | </ | ||
| + | |||
| + | Real example to upgrade to 1.96: | ||
| + | < | ||
| + | fetch ' | ||
| </ | </ | ||
| Line 405: | Line 412: | ||
| BSDRP v1.4 and earlier have a default configuration that prevent remote syslog. This behavior can be changed by editing / | BSDRP v1.4 and earlier have a default configuration that prevent remote syslog. This behavior can be changed by editing / | ||
| </ | </ | ||
| + | |||
| + | ==== Firmware Upgrade ==== | ||
| + | |||
| + | === Mellanox === | ||
| + | |||
| + | Stat by identifying your NIC ID: | ||
| + | < | ||
| + | # mstfwmanager | ||
| + | Querying Mellanox devices firmware ... | ||
| + | |||
| + | Device #1: | ||
| + | ---------- | ||
| + | |||
| + | Device Type: ConnectX4 | ||
| + | Part Number: | ||
| + | Description: | ||
| + | PSID: | ||
| + | PCI Device Name: pci0:2:0:0 | ||
| + | Base GUID: e41d2d0300fdbd90 | ||
| + | Base MAC: | ||
| + | Versions: | ||
| + | | ||
| + | | ||
| + | | ||
| + | |||
| + | Status: | ||
| + | </ | ||
| + | |||
| + | Then go to the [[https:// | ||
| + | |||
| + | < | ||
| + | # mount /data | ||
| + | # cd /data | ||
| + | # fetch http:// | ||
| + | # unzip fw-ConnectX4-rel-12_26_4012-MCX416A-CCA_Ax-UEFI-14.19.17-FlexBoot-3.5.805.bin.zip | ||
| + | # mstfwmanager -u -i fw-ConnectX4-rel-12_26_4012-MCX416A-CCA_Ax-UEFI-14.19.17-FlexBoot-3.5.805.bin | ||
| + | Querying Mellanox devices firmware ... | ||
| + | |||
| + | Device #1: | ||
| + | ---------- | ||
| + | |||
| + | Device Type: ConnectX4 | ||
| + | Part Number: | ||
| + | Description: | ||
| + | PSID: | ||
| + | PCI Device Name: pci0:2:0:0 | ||
| + | Base GUID: e41d2d0300fdbd90 | ||
| + | Base MAC: | ||
| + | Versions: | ||
| + | | ||
| + | | ||
| + | | ||
| + | |||
| + | Status: | ||
| + | |||
| + | --------- | ||
| + | Found 1 device(s) requiring firmware update... | ||
| + | |||
| + | Perform FW update? [y/N]: y | ||
| + | Device #1: Updating FW ... | ||
| + | Initializing image partition - OK | ||
| + | Writing Boot image component - OK | ||
| + | Done | ||
| + | |||
| + | Restart needed for updates to take effect. | ||
| + | </ | ||
| + | |||
| + | |||
| ===== Debugging ===== | ===== Debugging ===== | ||
| ==== Enabling crash dump ==== | ==== Enabling crash dump ==== | ||
| + | |||
| + | === Local swap dump device === | ||
| For saving and extracting a crash dump you need: | For saving and extracting a crash dump you need: | ||
| Line 506: | Line 583: | ||
| </ | </ | ||
| + | === netdump === | ||
| + | |||
| + | In case where you didn't have enough disk space to localy store dump, you can use netdump(4). | ||
| + | |||
| + | On the receiving FreeBSD server (not your router): | ||
| + | < | ||
| + | pkg install netdumpd | ||
| + | service netdumpd enable | ||
| + | service netdumpd start | ||
| + | </ | ||
| + | |||
| + | Then on your router, declare source interface to use, source IP address, gateway | ||
| + | < | ||
| + | sysrc dumpdev=igb1 | ||
| + | sysrc dumpon_flags=" | ||
| + | </ | ||
| + | |||
| + | and enable it: | ||
| + | |||
| + | < | ||
| + | # service dumpon restart | ||
| + | kernel dumps on priority: device | ||
| + | 0: /dev/null | ||
| + | server address: 198.19.0.24 | ||
| + | client address: 192.168.1.10 | ||
| + | gateway address: 192.168.1.254 | ||
| + | </ | ||
| ==== Installing debug symbols ==== | ==== Installing debug symbols ==== | ||
| Symbol files of kernel and binary are available in the separate DEBUG archive file. | Symbol files of kernel and binary are available in the separate DEBUG archive file. | ||
documentation/end-users_docs.1559654643.txt.gz · Last modified: 2019/06/04 15:24 by olivier