LME, It was burried under the bullseye rootfs release notes. Quotehttps://forum.doozan.com/read.php?2,12096 1. I realized I've missed one package that needs to be installed in order to make fw_printenv and fw_setenv available (these binaries have been moved to package libubootenv-tool in bullseye) . So do this if you want to list or set envs in Debian. apt-get install libubootenby bodhi - uBoot
Updated 01 Jan 2023 I've updated the script rsync.backup.ondemand to make it a bit more robust. I'm making sure the USB can be used as the rootfs and a boot drive.by bodhi - Debian
Hi Alan, > Of course, it would > be more convenient to have the config included in > your kernels. Yes indeed. I'm testing kernel 6.1.x-mvebu, atm. I moved a couple less commonly used file systems to loadable module, and add CONFIG_USER_NS and CONFIG_MEMCG to the kernel. It all seems working fine, and the kernel size does not change much. So it will be probably a few stableby bodhi - Debian
Mark, > Any experience with running data sync utilities > like syncthing with pogo? Do they run well on this > platform since this seem to have a gigabit > ethernet connection to router (vs wifi/100mbps > connection for my pi)? This Pogoplug E02 is very fast as far as network is concerned. We could get over 900Mbs running iperf test between the 2 Kirkwood boxes such as thby bodhi - Debian
kennywest, I think you should try pihole community (and of course users here who use pihole), to see which kernel versions people have reported running, and whether a segfault was seen lately.by bodhi - Debian
Hi Trond, > Success. Thanks! Maybe these updated dts-files > should be pushed upstream? Not sure if I will have time to do that, atm. I will eventually. > # Let the backup LED show disk activity on > rootfs > echo disk-activity > > /sys/class/leds/rn104:blue:backup/trigger What you saw here, disk-activity is the mainline kernel default trigger for all HDDs.by bodhi - Debian
Hi Trond, You're right! the RN104 DTS is missing that eSATA node. Here is the new DTB, please try.by bodhi - Debian
QuoteAlso, if I need to switch the rootfs to another usb stick, what is the process? Is it just a matter of running a "dd" command to copy the rootfs to the new device? Do I need to copy everything including label and UUID, so that I can switch to the new flash drive seamlessly? Don't use dd. Use this opportunity to create a backup tarball and restore it to the new USB drive. Andby bodhi - Debian
> The photo in that post appears to be for a HP > t5325 not the t5335z which is very different in > appearance. See the photos at > https://wikidevi.wi-cat.ru/images/8/8b/HP_t5335z_Top.jpeg > showing P4 at the top of the photo which doesn't > look similar in any way to photo in that post. OK when I have a chance, I'll open up the T5335z to verify. It was a lonby bodhi - Debian
OK. Close but no cigar :) I took a close look at the mainline DTS, and realized that there are drivers that have not been ported to mainline kernel 6.x yet! The kernel was built fine (I'd bet it will run fine too). But lacking drivers such as for USB, SATA, PCIe would make it too much works for me to actually try to port tthem.by bodhi - uBoot
Mark, > I noticed the above thread had instructions on > dual boot between openwrt running on NAND and > debian from usb stick. Any benefits with openwrt > implementation over debian? Debian is good for NAS. OpenWrt is good for router. So really there is no advantage/disadvantage comparing the two. Using NAS, you'd want to update kernel and Debian packages regularlby bodhi - Debian
QuoteChristmas is coming soon! Season greeting is here :) I'm building 6.1.x kernel for this box. Make sure you check back and test it when I release for testing in a couple days (before the New Year). After that I'll be slowing down, getting busy with works.by bodhi - uBoot
> I will wait for your instructions on swap file. > Thanks for all the help. I definitely learned a > few things. See above post.by bodhi - Debian
> I did it: I have used a rPi2, rPi2, MacBook Pro > (aluminum) and a MacMini, using an USB extender > cable (and with out it), using an usb-c to usb-a > converter. Nothing worked, with all of them I have > had to connect the 3.3v cable. I could read the > boot messages, but I could not type. Ok cool. Something seems to be particular about this NAS.by bodhi - Debian
Mark, Here is the instruction for swapfile https://forum.doozan.com/read.php?2,133753by bodhi - Debian
This instruction will be revised to add more detailed discussion. Below are the basic steps to create a swap file and activate it. 1. Create the swap file of 512MB at the rootfs top directory cd / dd if=/dev/zero of=swapfile1 bs=1024 count=524288 mkswap swapfile1 chmod 0600 swapfile1 2. Turn on swap swapon /swapfile1 3. Check the swap space free -h totalby bodhi - Debian
i5Js, Do you have another low power ARM board, such as the rPi? I'm curious to know what'll happen if you connect the serial converter to that ARM board and wired only GND+RXD+TXD to this EX2 Ultra NAS.by bodhi - Debian
> BTW, I bought > this > and > this > and both needed the 3.3v connected, without it, I > could see the boot process, but I could not type. Strange, the 2nd one is a typical CP2102 converter. I never connect 3.3V using this type of converter (I have several of these). I also have a couple of PL3xxx converters, and same rule applied.by bodhi - Debian
> 2. Swap space - are there any instructions on how > to do this? The current USB that I am using is > only 3.7GB. I may need help with relocating this > to another bigger flashdrive as I am assuming swap > along with additional utilities/tools that I may > install could go over that limit. I meant to add this swapfile instruction, but forgot all about it. Will do that sby bodhi - Debian
Orientation. We should not be too rely on marking, because it could change from on production lot to the next. "Left-to-Right, Inside facing out" means "Reading from left to righ, from inside the case facing outward)". See the picture in this post (the picture orientation is also inside-facing-out): https://forum.doozan.com/read.php?2,66989,116939#msg-116939 Perhapsby bodhi - Debian
QuoteI am curious - should I rebuild rootfs and then incorporate the above steps to get better visibility? Or is this only possible after the boot is successful to the new debian OS on pogo? No. Eventhough it is possible with chroot, you won't see everything that a serial console will give. And a big part of that is rootfs mounting. So, I would recommend retracing yourr USB rootfs crearby bodhi - Debian
Mark, > I am not sure how to run the serial console with > pogo since the device is not on the network. Is it > something from putty? I thought usually those need > a serial cable using a usb connected to computer > and pins to hook back to the board (at least when > I flashed dd-wrt) I see. I mistakenly assumed that you have serial console. So forget about removing nby bodhi - Debian
> About the 3.3v trust me, I have tried everything, > all the combinations,and without the 3.3v it > didn’t work I could see, badly the serial > output, but I could not type anything. With it, > everything worked fine. Don't get me wrong, I don't doubt what Gisab and you found! just may be the particular serial module converter you are using does not have 3.3v atby bodhi - Debian
Mark, Congrats! u-boot was installed successfully. But you missed this instruction: Quote10. Set up netconsole. It's important to set up neconsole if you don't already have serial console connected. If you have serial console, don't set up netconsole at this moment, because it will interfere with serial console. So now when you boot, the input and output go to serial conby bodhi - Debian
Mark, Quote> -bash-3.2# diff -s > uboot.2017.07-tld-1.pogo_e02.mtd0.kwb uBoot.dump > Files uboot.2017.07-tld-1.pogo_e02.mtd0.kwb and > uBoot.dump are identical Cool! > arcNumber=3542 > ethaddr=xx:xx:xx:xx:xx:xx > uenv_init_devices=echo Initializing devices...; > setenv init_usb "usb start"; setenv init_ide "ide > reset"; setenv iby bodhi - Debian
There is really no good way that I know of (other than removing the security apt source, meaning you will stop receiving secirity patches). See: https://wiki.debian.org/LTS/Using QuoteImportant: Debian 10 buster LTS will only support amd64, i386, arm64 and armhf. Users of other architectures are encouraged to upgrade to Debian 11 bullseye.by bodhi - Debian
Quote** Console: It's a must; you need an FT23RL USB UART converted. There are a lot on amazon. You can check this blog for more details (Thanks Nico) ** Minicom for Linux or putty for windows. I have always used minicom. This is really not accurate. You can use any serial module converter. We discussed it in this Wiki thread: QuoteWiki thread Unbricking with Serial Console &by bodhi - Debian
Hi i5Js, Thanks for writing this up! I will review it for you. But it is annoying to read and quite hard to follow because the Steps are not in the same post! There is no good reason for each step to be in a separate post.by bodhi - Debian
Mark, Your log was all messed up. Very hard to read. See if I can reformat it and read it the same time. -bash-3.2# ./flash_erase /dev/mtd0 0 5 Erasing 128 Kibyte @ 40000 -- 40 % complete flash_erase: Skipping bad block at 0 0060000by bodhi - Debian
mark, > Look like there are some badblocks based on dmesg > > > [ 1.050000] Scanning device for bad blocks > [ 1.050000] Bad eraseblock 3 at 0x00060000 > [ 1.090000] Bad eraseblock 654 at 0x051c0000 > > > Should I stop flashing or try the method outlined > in the following thread? - i.e. erase 8 blocks > instead of 4 and make sure that flasby bodhi - Debian