JDS420, > In order to enable ssh the way Dell intended, you > have to enter a "tether key" which allows customer > support to ssh into the box an undo/fix anything > someone may have broken. Without a legitimate key, > you have you purge all openssh packages and > reinstall them. You might have to remove the > kace-tether app too, but it's been monthsby bodhi - Debian
jmandawg, > [ 362.200133] sata_oxnas: resetting SATA core > [ 362.560099] ata1.00: exception Emask 0x0 SAct > 0x0 SErr 0x0 action 0x6 frozen > [ 362.567132] ata1.00: failed command: WRITE DMA > EXT I have not seen this on the Popgo OXNAS V3. But have seen similar error on a Kirkwood box. I can't say it is the same. But usually when you see this, check your SATby bodhi - Debian
That's encouraging! See how well it run :) When it's all done, please make a nice post for your OMV installation, including your log. I'd like to add this to the Wiki.by bodhi - Debian
Looker, Something strange in your system. The only way is to find out is to observe it booting with serial console. My Pogo V4's don't have any problem booting with drives attached to USB 3.0 ports. One boots with USB 2.0 on top, and other boot with NFS rootfs. Once in a while, I plugged in a USB 3.0 drive and don't recall any problem. But it would be great if there is inby bodhi - uBoot
Jxjhheric, The reason you can't see anything after this was because you have netconsole activated at the same time you're connecting with serial console. > host 192.168.1.105 is alive So what you can do to fix this quiclky: change the IP address of the box that you have serial console module plugged in to other number, eg. 192.168.1.106. If you'd rather not doing thby bodhi - uBoot
bodhi note: This old installation instruction is deprecated. Please see this post for new Installation Instruction: https://forum.doozan.com/read.php?2,61344,89559,page=5#msg-89559 =================== A. Installation instruction. Here is how to boot the new Debian rootfs 1. Create the USB rootfs using Debian-4.12.1-kirkwood-tld-1-rootfs-bodhi.tar.bz2 from the kernel/rooby bodhi - Debian
Jxjhheric Wrote: ------------------------------------------------------- > here is console : > > U-Boot 2017.07-tld-1 (Sep 05 2017 - 00:13:18 > -0700) > Pogo E02 > SoC: Kirkwood 88F6281_A0 > DRAM: 256 MiB > WARNING: Caches not enabled > NAND: 128 MiB > In: serial > Out: serial > Err: serial > Net: egiga0 > Using egiga0 devicby bodhi - uBoot
Looker Wrote: ------------------------------------------------------- > Bodhi, > > Thank you!! I got everything running . . . I tried > to use the USB ports but I read this was broken on > the Pogo v4 under Debian. Is there a workaround > for this? > > Thanks again for your help, > Looker No, USB ports definitely not broken. The only restriction is you caby bodhi - uBoot
argent88, Cool! so you are all done with installation. Regarding OMV, I recall users reportd difficulty in running in Debian stretch (which is what you have now). So you should do either of these 2 options: 1. Create the jessie rootfs Debian-4.4.0-kirkwood-tld-1-rootfs-bodhi.tar.bz2 or wheezy rootfs Debian-3.17.0-kirkwood-tld-1. And try it. After that, upgrade the kernel only. 2. Dowby bodhi - Debian
argent88, > Hit any key to stop autoboot: 0 Interrupt it here and printenv dtb_file If it shows the file name then check that file in the rootfs. Mount the drive on a different box (if it is mounted at /media/sdb1): ls -l /media/sdb1/boot/dts/kirkwood-goflexnet.dtbby bodhi - Debian
@Ray, Marvell>> flinfo Bank # 1: Flash Base Address : 0xf8000000 Flash Model : MXIC MX25L4005 Manufacturer ID : 0xc2 Device Id : 0x2013 Sector Size : 4K Number of sectors : 128 Page Size : 256 Write Protection : Upper 1 of 2 So that chip marking for SPI that you've observed is probably accurate, but not what stock u-bootby bodhi - Debian
> Just wondered if I need to run make using a > specific shell, since I get a few hundred errors > when running 'make oldconfig'... Remember this is Linux source tree. I don't know what adjustment you'd need for FreeBSD.by bodhi - uBoot
Here is how to boot the new Debian rootfs. Please see updated instruction in the post below.by bodhi - Debian
JT, > P.S. - I assume you were able to remove the SATA > module? There's only two screws holding it in. I have not tried that (I have permanent serial console now so root access is not urgent atm). Updated: I've gained root access to the box (chrooting from Debian).by bodhi - Debian
Here is the first boot with the rootfs 4.12.1-kirkwood-tld-1. Debian GNU/Linux 9 M300 ttyS0 M300 login: root Password: Last login: Wed Dec 31 16:01:32 PST 1969 from 192.168.0.220 on pts/0 Linux M300 4.12.1-kirkwood-tld-1 #1 PREEMPT Sat Jul 15 21:40:50 PDT 2017 armv5tel The programs included with the Debian GNU/Linux system are free software; the exact distribution terms for eacby bodhi - Debian
argent88, > U-Boot 2017.07-tld-1 (Sep 05 2017 - 00:17:19 > -0700) > Seagate GoFlex Net Cool! > Checking if uenvcmd is set ... > Running default loadzimage ... > ** File not found /boot/zImage ** > Running default loaduimage ... > 3821592 bytes read in 1002 ms (3.6 MiB/s) > Booting from 0 ... > ## Booting kernel from Legacy Image at 00810000 > ...by bodhi - Debian
Ron, > I'm using a GPT partition label. Should I have > used msdos instead? Exactly! this stock u-boot is quite old. You need to reformat your USB with MBR partition.by bodhi - Debian
JT, > I didn't bother researching it too much. I took > out the SATA module, put it in a USB/SATA > enclosure, plugged it into my Dockstar and used > chroot to change the root password. > That's a good way to do it :) I think they let us enable SSH through the web page, too, but probably just an admin user, not root. Was it easy to remove the SATA module? Iby bodhi - Debian
> Received the unit I purchased on ebay today. It's > a brand new unit and in my opinion in violation of > the GPL as none of the documents included tell me > how to get the source code. A search of Dell's > website isn't helpful as it appears they have spun > the Kace unit off to Quest KACE which appears to > be oriented toward the software and have noby bodhi - Debian
argent88, > "Better to add a little more than necessary than > to take away too much" This is actually counterproductive do do more than necessary in the embedded Linux worls (you will know what I mean when you see more booting scenarios). But in this case it happens to work:) > > > 2. Arch u-boot setup does not load uInitrd, so > > that's sometby bodhi - Debian
Got my unit and connected serial console. ><><><><><><><><><><><><><><><><><><><><><><><><><><><><><><><><><><><><><><>< Mby bodhi - Debian
Please be careful, do not connect 3.3.V! Only connect 3 wire TX,RX, GND.by bodhi - Debian
Ron Nelson Wrote: ------------------------------------------------------- > For the serial console, I have one of > these > for my odroid-xu4 (faster rPi clone). Could I use > that? Will I need to solder it on to the router's > header? That's a good USB serial module converter to use. Open the EA4500, see if you can use the existing header. If not, you would nby bodhi - Debian
Kernel linux-4.17.2-kirkwood-tld-1 package has been uploaded. Please see 1st post for download link.by bodhi - Debian
> Debian GNU/Linux 9 debian ttyS0 > > debian login: Cool :) However, you've got it to boot into Debian because you did a wrong step during rootfs creation, and it happens to work with this Arch u-boot setup! 1. You must have performed Step 4, while you should have skipped this step. This Arch u-boot is considered "new" so it should load the DTB separately. Qby bodhi - Debian
Ron, > my understanding is > that I need a serial connection to a Linux box. > (Raspberry pi should be fine?) The best way to hack embedded Linux is serial console. Yes, use rPi to connect. Run picocom on the rPi terminal. > get the most recent > dtb that you posted, then use stock u-boot to load > the kernel and dtb. No need to. When you create the Debian rootby bodhi - Debian
argent88, See the post right above, I've just edited it.by bodhi - Debian
Now that you have a working serial console, everything else is easy! QuoteArch Linux 4.2.2-1-ARCH (ttyS0) alarm login: You got to this point, meaning there is nothing wrong with your Arch installation. The reason you could not SSH in was probably because some setting need to be adjusted. You can log in with serial console and fix that, if you'd like to continue using Arch. ==by bodhi - Debian
argent88, > Reverting cables worked!! :D Congrats :) > Here's what I see now! > > U-Boot 2014.04.R2-1 (May 15 2014 - 14:36:22) Arch > Linux ARM > Seagate GoFlex Net It's an older but good Arch built u-boot.by bodhi - Debian