They make great remote log servers, too. My E02 runs rsyslog to collect the output from my various internet-of-things devices (mostly lighting controllers running Tasmota). A daily run of a Logwatch script emails me info on whether they're operating as expected or having issues.by dougdeep - Off-Topic
Thank you for the suggestions. I normally cruise eBay looking for used HP ProBooks and ProDesks for friends. Those that are just “off lease” typically mean that they’re business computers and not likely to be too abused. My daily driver is a HP Compaq Pro 6305 running Ubuntu LTS and now 11 years old. Works great but I know one day that weirdo semi-proprietary power supply will pack itby dougdeep - Off-Topic
What is your favorite site or store for computer parts? When I was inventorying the various computers and laptops around the house I realized that I don’t own anything newer than eight years ago and most are well over ten. I started shopping for parts to upgrade my main workstation (Intel core2 dual with 8Gb – woohoo!) but quickly realized that there aren’t any parts stores in town anymorby dougdeep - Off-Topic
Thank you for your reply. I'll give that a try next time I have the serial console attached. The fw_setenv command doesn't want to work on this box as well.by dougdeep - uBoot
I have an Iomega IX2 2-drive NAS (original version) that I wanted to get working with a newer version of Linux. Iomega actually had the two hard drives arranged in two RAID 1’s – a small one for /tmp and user configurations, and a much larger RAID for data. Since the stock uboot booted Linux from NAND, it could still boot Linux even if one or both hard drives failed. As far as I know thereby dougdeep - uBoot
Quotesudos does it still have the same no-boot behavior unless something is plugged into USB with the latest kernel/rootfs combo? For kwboot, it worked with or without a USB device plugged in. Switching back to the original uboot it would only boot the mSATA with something plugged into USB. Same as before so it doesn't seem to be the fault of the kernel or Debian version.by dougdeep - Debian
Success at latest kwboot! I bungled an attempt to upgrade the 5.2.9 kernel so had to start over with a fresh mSATA formatted to ext3. Not quite the same kernel as yours but close. Debian GNU/Linux 11 kace ttyS0 kace login: root Password: Linux kace 5.13.6-kirkwood-tld-1 #1.0 PREEMPT Sat Jul 31 22:10:39 PDT 2021 armv5tel The programs included with the Debian GNU/Linux system are frby dougdeep - Debian
I tried your latest kwb file on my Kace. It seems to have broken in the same place as the previous one: # kwboot -p -t -B 115200 -b uboot.2021.10-tld-1.m300.mtd0.kwb /dev/ttyUSB0 Sending boot message. Please reboot the target...| Sending boot image... 0 % [......................................................................] 2 % [...................................................by dougdeep - Debian
I used these ENVs that were developed for someone else's IX2 problem and got it working: setenv bootcmd_ide 'ide reset; ext2load ide 0:1 0x800000 /boot/uImage; ext2load ide 0:1 0x2100000 /boot/uInitrd' setenv bootcmd_stock 'nand read 0x800000 uImage; nand read 0x2100000 uInitrd; bootm 0x00800000 0x2100000' setenv bootcmd 'setenv bootargs $(bootargs_console) rootby dougdeep - Debian
This Iomega box is resisting any attempt at USB booting. >If at u-boot prompt in serial console, you can do this and got the USB drive initialized, then you can boot >with USB rootfs on this box. usb reset >repeat the command a few times to see if the USB drive is initialized. I tried 5 different USB sticks, including a new-in-package Sandisk Cruzer. All were formatted EXT2 orby dougdeep - Debian
I was trying to get Debian working on an original model Iomega IX2-200 but it was very erratic about booting from a USB stick. It would boot maybe one out of four times and often complained nothing was plugged into a USB port even when it had just successfully booted from the same port. I was looking into flashing the iConnect uboot version into this device and had the serial cable connected inby dougdeep - Debian
Okay, I changed uEnv.txt as suggested and got further but not all the way to login (with no USB device): # kwboot -p -t -b uboot.2021.10-tld-1.m300.mtd0.kwb -B 115200 /dev/ttyUSB0 Sending boot message. Please reboot the target...- Sending boot image... 0 % [......................................................................] 2 % [....................................................by dougdeep - Debian
I had some spare time so I tried this kwboot on a Kace machine that otherwise boots normally from mSATA into Debian if a USB device is plugged in (I use a IR receiver dongle from an old windows media player). My version of Debian is a bit older than the one bodhi used a few posts back: root@kace:~# uname -a Linux kace 5.2.9-kirkwood-tld-2 #1 PREEMPT Wed Aug 28 03:55:21 PDT 2019 armv5texby dougdeep - Debian
For fun, try plugging any old USB drive into the box and then see if it boots from mSata Thank you, Mikeh49. Attaching a USB memory stick did indeed result in a successful startup. I know that's a workaround and not a fix but it's alright for now. I also tried some non-memory USB sticks like a WIFI and an audio adapter and those worked as well. It seems like there needs to be aby dougdeep - Debian
I have two of these Kace M300 units and they work great when booted off a USB stick. The trouble I’m having is getting them to boot off the internal mSATA drive. After I got the units booting Debian and the 2Gb kernel, I tried copying the system to mSATA drive by creating a tar from the USB on another machine (as su with permissions and such also copied) and extracting it on the Kace drive afby dougdeep - Debian
Thank you for the response. I just wanted to make sure there was no funny business going on like with the Sonos brick debacle. That, plus this has Dell's name plastered all over it and I'm old enough to remember Dell's blacklisting BIOS updates aimed at keeping customers from upgrading thier Optiplexes from Pentium 2 to Pentium 3.by dougdeep - Debian
I just picked up a pair of M300's still in the factory boxes. Is there anything I can do to verify the operation of the devices before trying to replace the OS? I take it that out of the box these things are web page driven. Is it a good idea to not expose it to the internet (and letting it phone home)? I have a spare router so I guess I could make a non-internet-connected LAN and see ifby dougdeep - Debian
I tried the "e2fsck" and "sync" with no errors but the USB stick Debian would still show a "read only" file system. I was going to try your suggestion about a static IP and put the stick back in my Linux machine. I happened to have Gnome Files open and noticed that the stick had padlock symbols on every folder and sub-folder, so that explains the 'read only�by dougdeep - uBoot
Something changed over the weekend but I'm not sure what it was. The Pogoplug's Ethernet port decided to light up when I started it today (same cat5 cable, same router) but it's still not working correctly. If I start it with the Debian USB stick, it gets stuck endlessly trying to get an IP address: U-Boot 2017.07-tld-1 (Sep 05 2017 - 00:13:18 -0700) Pogo E02 SoC: Kirkwoby dougdeep - uBoot
I recently used the serial port and tftp to update the uboot on a Pogoplug E02 to the 2017.07 U-Boot Kirkwood version. It seemed to go well but the result was no Ethernet port activity after rebooting. I get a brief flash of the port status and speed LEDs after a reset but they're otherwise dark. My router does not notice the Pogoplug and all pings from the Pogoplug fail. I checked theby dougdeep - uBoot