bodhi Wrote: ------------------------------------------------------- > Without GPL source code, it will take too much > time to complete a new u-boot for this box. That's a shame, but you've done quite a lot! Thanks for all the work you've put into making this into a quite capable little server! Nealby nwestfal - Debian
bodhi Wrote: > Indeed, it looks wrong. > > If it is still interesting to others, I will post > new info about GPIOs that I have found? Sure! I don't suppose you found poweroff though? Here's my output: # gpioinfo gpiochip0 - 32 lines: line 0: unnamed unused output active-high line 1: unnamed unused outputby nwestfal - Debian
Since I hadn't tried it before, decided to try running that OpenWRT GPIO test script from stock OS to see if anything came up different. Interesting thing is stock OS sees the GPIO as a single chip whereas Debian sees two chips. On stock, GPIO6 doesn't seem to be connected to anything so I guess it is just Debian grabbing that one for something. As expected, I was unable to testby nwestfal - Debian
Is it just the stock SSD that people are having issues with running Debian? Any issues with regular SATA hard drives? Nealby nwestfal - Debian
bodhi Wrote: > You can only see the reset is 41 while in stock > OS. Okay. Yeah I did the test in Debian, not in stock. I'm still curious about GPIO 6 though... Nealby nwestfal - Debian
bodhi Wrote: ------------------------------------------------------- > > When you run this script did you let it cycle > through all GPIOs? i.e further than the LED GPIOs > 37 and and 38? Yes > > GPIO 41 is actually the RESET > > So I'm wondering that this box even has a GPIO for > poweroff if indeed you have tried all GPIOs and > did not sby nwestfal - Debian
mikeh49 Wrote: ------------------------------------------------------- > Nice. I have another M300 on the way and this > will be a concise way to get it set up. Thanks > for the instructions. Yep, picked up another one as well. Still in the box, but I’ll easily find a use for it. Wonder how long before sources for these dry up. :)by nwestfal - Debian
@bodhi, Very nice! Tested fine. Nealby nwestfal - Debian
bodhi Wrote: > That OpenWrt script is close. But it's needed to > be modified. > > Try the procedure, but don't set GPIO 41 (it is > the power off GPIO!) Oops had already run the script before I saw your post! GPIO41 gave this error as did GPIO6: /scripts/test_gpio: 8: echo: echo: I/O error It doesn't seem to have hurt anything! Anyway, it lookby nwestfal - Debian
bodhi Wrote: ------------------------------------------------------- > One last topic on this box. It is not important, > but would be nice to find out where the LED(s) is, > and which GPIO controls that LED. How do we go about figuring this out? In Debian I see: root@Gilrain:/sys/firmware/devicetree/base/gpio-leds# ls -l total 0 drwxr-xr-x 3 root root 0 Sep 11 11:19 .by nwestfal - Debian
@bodhi, That got it! BTW now that I've disabled preview generation in Nextcloud, performance is quite good! I need to go through a clean installation now to document all the steps. I consulted various pages getting it installed and working and I'd like to pull all the pieces together to document the process thoroughly. With this much RAM there's plenty of headroom for ruby nwestfal - Debian
mikeh49 Wrote: > I don't know if this is the best place to do this, > but it works. I think this is better: fw_setenv bootcmd_stock 'setenv mainlineLinux no; echo Booting stock ...; run bootcmd_ide' Also, set_bootargs_stock as is produces an error when executed (e.g. while in uboot, type "run set_bootargs_stock" and you will see it). As far as I canby nwestfal - Debian
I'm thinking this: setenv set_bootargs_stock 'console=ttyS0,115200 mtdparts=spi_flash:0x7f000@0(uboot),0x1000@0x7f000(u-boot-env) root=/dev/sda1 rw' Should be this: setenv set_bootargs_stock 'setenv bootargs console=ttyS0,115200 mtdparts=spi_flash:0x7f000@0(uboot),0x1000@0x7f000(u-boot-env) root=/dev/sda1 rw' Except that doesn't solve it either. Somethby nwestfal - Debian
So I've been playing with Nextcloud trying to get it optimized for best performance. It does work much better on this M300 than an E02 for example. The extra memory really helps a lot. The real achilles heel though is the single core CPU. Performance is fairly good until you try to view images, which bogs down the CPU pretty quickly: top - 12:26:38 up 4 min, 1 user, load average:by nwestfal - Debian
bodhi Wrote: ------------------------------------------------------- > For more experienced users, we always connect > serial console. But It would make the box more > popular for beginners if serial console is not > needed for installation. True that. > I did not mean we want a SATA drive inside this > box :) The SATA-USB connection is outside and > temporary,by nwestfal - Debian
mikeh49 Wrote: > Getting into the Pogo plugs with SSH from the > get-go, was a good deal. Even then it only worked because Pogoplug made it doable through their web site. Now that they're gone, the only way to hack a stock pogo is through serial. Nealby nwestfal - Debian
bodhi Wrote: > So you can change the IP to anything you want > through the web page (from the original > 192.168.2.100) ? Yes. I guess the idea is for initial configuration you hook it up direct to an unused ethernet port that you configure to 192.168.2.x, then access the web page via 192.168.2.100. So at least you can do that to get it on your network. Not sure why they didn&by nwestfal - Debian
mikeh49 Wrote: ------------------------------------------------------- > Good work, Neal! > > OK, got ssh working in stock OS per the above, but > also had to edit the /etc/network/interfaces file > to set the the eth0 interface to dhcp. It was > static 192.168.2.1 or something like that. My > network is 192.168.1.x. Oh yes I had forgotten that I had done that eby nwestfal - Debian
Looks like there is an sshd running: root@gilrain:~# ps -ef | grep sshd root 725 1 0 16:36 ? 00:00:00 /usr/sbin/sshd root 22517 21824 0 23:32 ttyS0 00:00:00 grep sshd root@gilrain:~# If you kill it and restart it with -ddd to get some debug info you can see it is listening on port 22 but it's binding to loopback only: root@gilrain:/usr/sbin# /usr/sbinby nwestfal - Debian
bodhi Wrote: ------------------------------------------------------- > All, > > Did you use the box web page during first time > installation? and how did you gain root to stock > OS without serial console (if you did)? I used serial console. I also mounted the SATA and chroot to reset the root password. I never looked at the web page. Nealby nwestfal - Debian
So far, so good: root@debian:~# uname -a Linux debian 5.2.9-kirkwood-tld-2 #1 PREEMPT Wed Aug 28 03:55:21 PDT 2019 armv5tel GNU/Linux root@debian:~# free -h total used free shared buff/cache available Mem: 1.7Gi 15Mi 1.7Gi 0.0Ki 44Mi 1.7Gi Swap: 0B 0B 0B And here are my stress tesby nwestfal - Debian
bodhi Wrote: ------------------------------------------------------- > @Neal, > > Please give it a shot! I think your use case is > the best test case for this kernel memory > capacity. Excellent! I'll keep you posted on my progress! Nealby nwestfal - Debian
Hi guys, Frequent lurker, but infrequent poster here. After I stumbled on this thread, I picked one of these up for $10 after $5 ebay coupon. Got Debian booted from a thumb drive using bodhi's instructions. This looks like a nice souped up version of a pogoplug. If the 2 GB issue can get resolved, it would open up some interesting possibilities. For instance I've found Nextcloudby nwestfal - Debian
asterix Wrote: ------------------------------------------------------- > I will try it later after my jtag arrived. not > possible to do it by SSH? > JTAG not needed. You can use the serial console, and log into stock OS and enable SSH.by nwestfal - Debian
Pogoplug.com still works fine (at least for me). But devices that have never been activated before can no longer enable ssh via the web site. Interestingly, whenever you log in there now a message pops up stating that they are shutting down their cloud service on September 28th. Then clicking on "More Details" brings up this blog post: http://blog.pogoplug.com/pogoplug-cloud-is-shby nwestfal - uBoot
bodhi Wrote: ------------------------------------------------------- > Netconsole should work. > > Fyi . I changed that command since it was > conflicted with jffs2 ls. Moonman version doesnot > have jffs2. Alarm determined to get rid off stock, > so even jffs2 was eliminated :) Ah okay. Maybe I'll create a separate thread for netconsole. Not a huge deal sincby nwestfal - uBoot
Yes, on different Linux machine (i.e. Ubuntu, in my case I have OpenSUSE). But I meant trying to mount the partition to read it: Example: mount /dev/sdb1 /mnt ls -l /mnt ls -l /mnt/boot Note: might be different /dev/sdXX on your box depending on how many drives you have.by nwestfal - uBoot
I guess it is ext2ls / ext4ls on that older U-Boot on qnology blog. I just recently did this with bodhi's latest U-Boot on a Pro (labeled as POGO-BIZ02-US from Adorama). My earlier post with "ls" was based on a moonman U-Boot on an E02 which has netconsole working. When you said "ls" didn't work, I hooked a serial console to the Pro and found that with V3 latest Uby nwestfal - uBoot
Ah I guess in this version of U-Boot it is "fsls" usb start fsls usb 0 fsls usb 0 /bootby nwestfal - uBoot
Seems like problem still with rootfs partition. Interrupt U-Boot and type: usb start ls usb 0 ls usb 0 /boot (post back the results)by nwestfal - uBoot