Cool. Works on my 5.13.6 file system running Logitech Media Server: root@Dell-M300:~# get_cpu_temperature CPU Temperature 43 Cby mikeh49 - Debian
@bodhi: Thanks for continuing to think about this. My M300 runs 24/7/365 and seems to boot OK with a 128GB SSD connected to SATA. My spare M300 with the stock 16GB internal SATA card will not boot without a USB connected. Keep up the good work, and thanks.by mikeh49 - Debian
For me, yes, but only limited use. My production box with an internal 128GB SSD is very reliable. I've only restarted it a few times in a couple of years, no problem. There must be something about the 16GB OEM memory card?by mikeh49 - Debian
Glad it worked! USB mood light, perfect. A USB audio adapter could make it a very good network media player. I'll try it on mine. Update Booted OK with 3 different USB audio cards and with an unpowered cheap USB 2.0 hub.by mikeh49 - Debian
Doug: Deja vu all over again for me. You can look up thread to earlier this year and see my similar troubles. For fun, try plugging any old USB drive into the box and then see if it boots from mSata. That's what I had to do to get a reliable boot using the original 16GB sata card. On the other hand, another M300 boots 95% first time from a 128GB internal sata SSD.by mikeh49 - Debian
OK, I'll try the older driver again. I think that is what I tried already, and it sort of worked but was not reliable, locked up or blue screened or something. In looking into this for my post I saw several youtubes about using the older drivers. /thread driftby mikeh49 - Debian
Some versions of the PL2303 chip used in these devices are not supported in Win10. The CP chip is better supported and might be better, but is usually more expensive. My PL2303 device works fine in Mac, Linux and Win7, but definitely not in Win10. There is no driver. Check here for info, dirivers, etc for the PL2303: PL2303 mfgr siteby mikeh49 - Debian
Could be serial; if it was the M300, I had serial connected all the time. Regenerating the keys from serial seems kind of familiar.by mikeh49 - Debian
I've been following this thread because I seem to remember I had this same connection refused problem on a Dell M300 or a Pogo E02 within the past year but I cannot remember how I solved it. I have not found any posts from me on this issue on this forum. If I indeed had the problem, the solution wasn't anything as complex as chaos did. At the most, it would have been build a new USB.by mikeh49 - Debian
Havaged worked for me on a Kirkwood box booting from SSD. I think it was simple to install, IIRC it just worked.by mikeh49 - Debian
I concur with ensuring a USB is plugged in for boot from SATA. The RAM suggestions seems interesting as the there was no consistent error in the boot failures I had with the original 16GB SATA flash card with latest Debian file system and kernel. Assuming that the stock filesystem and kernel was reliable, would there be any way to "dissect" the original kernel to see how it managed thby mikeh49 - Debian
All worked OK. Three boots, with and without extra USBs, consistent results each time, serial log looked as expected. It complains about uEnv.txt not found, but keeps going. loading envs from usb 0 ... ** File not found /boot/uEnv.txt ** In this case the rootfs was usb 0. Environments file attached.by mikeh49 - Debian
OK, will do and report shortly. It can handle the vfat device if I interrupt boot, run bootcmd_uenv and then boot. It fusses about it but keeps looking for a bootable device, eventually finds it, and boots OK. So, the basic logic is OK, it just needs to run. UPDATE: Turns out 2 environments needed to be added: bootcmd_uenv and bootcmd_exec, with that it boots with the rootfs and 2 other USBby mikeh49 - Debian
Testing results: 2 USB connected, rootfs in front USB, vfat USB in one of the back connectors, boot process not interrupted: U-Boot 2013.10-tld-3 (May 15 2014 - 14:54:14) for OXNAS DRAM: 128 MiB NAND: 128 MiB In: serial Out: serial Err: serial Net: Led: GREEN mii0 Main Loop Hit any key to stop autoboot: 0 (Re)start USB... USB0: USB EHCI 1.00 scanning bus 0 forby mikeh49 - Debian
OK, booted with just the rootfs USB connected: OX820 # setenv devices usb OX820 # setenv disks '0 1 2 3' OX820 # printenv devices devices=usb OX820 # setenv uenv_import 'echo importing envs ...; env import -t 0x60500000 $filesize' OX820 # setenv uenv_init_devices 'setenv init_usb "usb start"; setenv init_ide "ide reset"; setenv init_mmc &quoby mikeh49 - Debian
Sorry to say, it doesn't work. I plugged in a random vfat USB, not labeled rootfs, entered boot at the u-boot prompt, and it went into a boot loop. I then reentered the setenv commands, ran bootcmd_uenv and got the importing envs response and then the u-boot prompt. Plugged in the second USB and entered boot. A full serial log below: U-Boot 2013.10-tld-3 (May 15 2014 - 14:54:14) for Oby mikeh49 - Debian
OK, now I get it, what an idiot. Will be added shortly. OX820 # printenv autoload=no baudrate=115200 bootargs=console=ttyS0,115200n8 bootcmd=run bootcmd_uenv; run scan_disk; run set_bootargs; run bootcmd_exec; reset bootcmd_exec=run load_uimage; if run load_initrd; then if run load_dtb; then bootm 0x60500000 0x60e00000 0x62c00000; else bootm 0x60500000 0x60e00000; fi; else if run load_dtby mikeh49 - Debian
More results: OX820 # OX820 # setenv devices usb OX820 # setenv disks '0 1 2 3' OX820 # setenv uenv_import 'echo importing envs ...; env import -t 0x60500000 $filesize' OX820 # setenv uenv_init_devices 'setenv init_usb "usb start"; setenv init_ide "ide reset"; setenv init_mmc "mmc rescan"; for devtype in $devices; do run init_$devtyby mikeh49 - Debian
Results: OX820 # run bootcmd_uenv (Re)start USB... USB0: USB EHCI 1.00 scanning bus 0 for devices... 3 USB Device(s) found scanning usb for storage devices... 1 Storage Device(s) found Reset IDE: SATA PHY not ready for device 0 ide_preinit failed Partition Map for USB device 0 -- Partition Type: DOS Part Start Sector Num Sectors UUID Type 1by mikeh49 - Debian
Results: no errors, but nothing echoed, just return to prompt after run bootcmd_uenv. Unfortunately, I didn't look at your last post closely and booted. Note the different environment size the 2 times I printed them, before and after the run bootcmd_uenv command. Debian GNU/Linux 7 PogoPro ttyS0 U-Boot SPL 2013.10 (Apr 27 2014 - 19:08:27) Boot device: NAND Attempting to set PLby mikeh49 - Debian
I can confirm that the Pogo Pro with u-boot 2013-10 will not boot with a vfat USB plugged in in addition to the rootfs USB. It cannot find the rootfs drive, seems to get stuck on the vfat drive and where it can't understand the filesystem. I can get a serial log, if needed.by mikeh49 - Debian
OK, got it. Will be tomorrow, I expect.by mikeh49 - Debian
@Bodhi Here's the info on my Pogo Pro: root@PogoPro:~# uname -a Linux PogoPro 4.1.0-oxnas-tld-1 #3 SMP PREEMPT Wed Jul 1 05:11:47 PDT 2015 armv6l GNU/Linux root@PogoPro:~# grep -a --null-data U-Boot /dev/mtd0 U-Boot 2013.10-tld-3 for ox820 FW environments: root@PogoPro:~# fw_printenv autoload=no baudrate=115200 bootargs=console=ttyS0,115200n8 bootcmd=run dt_bootcmd_usb bootdelaby mikeh49 - Debian
I have always had the root USB plugged into the front port. I usually use a little mini device, Sandisk Cruzer Fit. It's unobtrusive and I seem to recall a recommendation from the beginning of the Pogo Plug era to use the front port for the OS. I can't make a recommendation re: exfat. I did not read everything I linked to yesterday. With only circumstantial information, if it wby mikeh49 - Debian
I have a Pogo Pro that is out of service so if I have some time, I'll give it a try. So you want me to try the 2013.10-tld5 environments instead of whatever is on the box? I don't know the u-boot on the Pro, so I'll have to check that.by mikeh49 - Debian
@tca... I have not reviewed your posts above for this, but do you have ntfs-3g installed? My understanding is that you need this to use ntfs formatted drives. I have it on my boxes that use ntfs drives. Your HITCH drive is using the old MS vfat file system that goes back to Win 95. You might need to research how that is handled in Linux; Bohdi provides a pretty basic filesystem and youby mikeh49 - Debian
My Pogo P21 u-boot is 2013.10, dated in early 2014, perhaps when I installed it. I think this may have been in the Arch days when there was a long script that downloaded and installed the u-boot, essentially automating your steps. I think that script used the root=/dev/sda1 feature. Interesting to me, is that it loads the DTB separately, so it is apparently not embedded in the uImage. This boby mikeh49 - Debian
Regarding booting, the u-boot needs to know where the root filesystem is located. This can be done a couple of ways, but in any case, AFAIK, it is specified in the firmware environment variables. You can list them with the fw_printenv command. One of my Oxnas pogos has the value set to sda1 which I think is the first drive recognized. This works fine for this device since it will only havby mikeh49 - Debian
A follow-on question: If everything is working fine, both kernel and file system, how important is it to upgrade the distro for a use case that has limited or no access to the internet? For example, Logitech Music Server only accessed audio streams and maybe fanart, nothing interactive.by mikeh49 - Debian
My second M300 does not have the m300 parameters in either rc.local or halt scripts. Yet, the light displays the expected sequence during boot. The other M300 does not have them but I have not watched the light during boot. I recall seeing Bohdi's not about light controls, but did not check them, and would not have known what to look for. I'll add the suggested changes. I'm gby mikeh49 - Debian