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
Next revisionBoth sides next revision
toh:gnubee:personal_cloud_one [2024/08/13 14:19] – [Install Recovery tools or Debian from USB key] Add gnubee-tools github repo vinceletoh:gnubee:personal_cloud_one [2024/09/08 14:17] – Trivial - move TFTP boot section one level upper, out of performance vincele
Line 70: Line 70:
 ==== OEM easy installation ==== ==== OEM easy installation ====
  
-GnuBee already comes with a preinstalled version of OpenWRT. However, original maintainer does not maintain it'OpenWRT builds, so it's safe to use official OpenWRT builds, as it is officially supported by the community.+GnuBee already comes with a preinstalled version of OpenWRT. However, original maintainer does not maintain its OpenWRT builds, but you can use official OpenWRT builds, as they are officially supported by the community.
  
 Two methods are available: Two methods are available:
Line 102: Line 102:
  
 This image is also capable to boot other systems: This image is also capable to boot other systems:
-* Simply create a partition with a GNUBEE-ROOT label to boot it. You can choose any of micro-sd, internal drive, md array or LVM. You can have different partitions with different OS, and swap labels if you want to change boot OS.+  * Simply create a partition with a GNUBEE-ROOT label to boot it. You can choose any of micro-sd, internal drive, md array or LVM. You can have different partitions with different OS, and swap labels if you want to change boot OS.
   * For ext3/ext4 with sde1 partition: tune2fs -l /dev/sde1 | grep GNUBEE-ROOT || e2label  /dev/sde1 GNUBEE-ROOT   * For ext3/ext4 with sde1 partition: tune2fs -l /dev/sde1 | grep GNUBEE-ROOT || e2label  /dev/sde1 GNUBEE-ROOT
   * For fat: exfatlabel /dev/sda3 GNUBEE-ROOT   * For fat: exfatlabel /dev/sda3 GNUBEE-ROOT
Line 169: Line 169:
 -> [[docs:guide-user:troubleshooting:generic.debrick]] -> [[docs:guide-user:troubleshooting:generic.debrick]]
  
-GnuBee is provided with a Serial USB cable. From a Linux computer, you can get into the serial consol with: <nowiki>screen /dev/ttyUSB0 57600</nowiki>+GnuBee is provided with a serial to USB cable. From a Linux computer, you can get to the serial console with: <nowiki>screen /dev/ttyUSB0 57600</nowiki>
  
 ===== Failsafe mode ===== ===== Failsafe mode =====
Line 357: Line 357:
  
 Test run on: OpenWrt 23.05.0 r23497-6637af95aa Test run on: OpenWrt 23.05.0 r23497-6637af95aa
 +
 +Alternative tests: [[https://forum.openwrt.org/t/feedbacks-on-gnubee-personal-cloud-device-performances/178002|Here]] (newer kernel, higher performance)
  
 Conclusion: Conclusion:
Line 444: Line 446:
 -rw-r--r--    1 root     root      953.7M Nov 18 13:21 /mnt/sdc2/TMP -rw-r--r--    1 root     root      953.7M Nov 18 13:21 /mnt/sdc2/TMP
 </code> </code>
 +
 +
 +===== TFTP Boot =====
 +
 +An openwrt image can be booted via TFTP without being flashed, for example to test a snapshot or custom build.
 +
 +You should have a TFTP server ready, for example:
 +<code>
 +wget -O /srv/tftp/GB-PCx_uboot.bin https://downloads.openwrt.org/snapshots/targets/ramips/mt7621/openwrt-ramips-mt7621-gnubee_gb-pc1-initramfs-kernel.bin
 +ip a add 192.168.1.100/24 dev eth0
 +in.tftpd -vvv -4 -L -s /srv/tftp
 +</code>
 +On the serial console interrupt the normal boot process with the "1" key, this is the "Load system code to SDRAM via TFTP".
 +<code>
 +Please choose the operation:
 +   1: Load system code to SDRAM via TFTP.
 +   2: Load system code then write to Flash via TFTP.
 +   3: Boot system code via Flash (default).
 +   4: Enter boot command line interface.
 +   5: Load system code then write to Flash via USB Storage.
 +   6: Load system code then write to Flash via Httpd.
 +   9: Load U-Boot code then write to Flash via TFTP.
 +</code>
 +It will ask you if you want to change from the default TFTP boot parameters:
 +<code>
 +1: System Load Linux to SDRAM via TFTP.
 + Please Input new ones /or Ctrl-C to discard
 +        Input device IP (192.168.1.1) ==:192.168.1.1
 +        Input server IP (192.168.1.100) ==:192.168.1.100
 +        Input Linux Kernel filename (GB-PCx_uboot.bin) ==:GB-PCx_uboot.bin
 +</code>
 +It will then dowload the image in RAM and run it:
 +<code>
 + NetTxPacket = 0x9BFB6C00
 +
 + KSEG1ADDR(NetTxPacket) = 0xBBFB6C00
 +
 + NetLoop,call eth_halt !
 +
 + NetLoop,call eth_init !
 +Trying eth2
 +
 + ETH_STATE_ACTIVE!!
 +Using eth2 device
 +TFTP from server 192.168.1.100; our IP address is 192.168.1.1
 +Filename 'GB-PCx_uboot.bin'.
 +
 + TIMEOUT_COUNT=10,Load address: 0x80a00000
 +Loading: Got ARP REPLY, set server/gtwy eth addr (98:f2:b3:c3:11:f0)
 +Got it
 +T
 +         #################################################################
 +         [...]
 +         ###################
 +done
 +Bytes transferred = 6086802 (5ce092 hex)
 +LoadAddr=80a00000 NetBootFileXferSize=005ce092
 +Automatic boot of image at addr 0x80A00000 ...
 +## Checking image at 80a00000 ...
 +   Image Name:   MIPS OpenWrt Linux-6.6.45
 +   Image Type:   MIPS Linux Kernel Image (uncompressed)
 +   Data Size:    6086738 Bytes =  5.8 MB
 +   Load Address: 80001000
 +   Entry Point:  80001000
 +   Verifying Checksum ... OK
 +OK
 +No initrd
 +## Transferring control to Linux (at address 80001000) ...
 +## Giving linux memsize in MB, 512
 +
 +Starting kernel ...
 +
 +OpenWrt kernel loader for MIPS based SoC
 +Copyright (C) 2011 Gabor Juhos <juhosg@openwrt.org>
 +Decompressing kernel... done!
 +Starting kernel at 80001000...
 +
 +[    0.000000] Linux version 6.6.45 (builder@buildhost) (mipsel-openwrt-linux-musl-gcc (OpenWrt GCC 13.3.0 r27140-ccc06f6716) 13.3.0, GNU ld (GNU Binutils) 2.42) #0 SMP Tue Aug 13 10:22:33 2024
 +[...]
 +</code>
 +And that's it.
  
  
  • Last modified: 2024/09/08 14:22
  • by vincele