Maddy, You did not give enough info for us to help you. How did you install Debian? Now I formatted new USB drive to install debian there are many different ways to do this for the Pogo Pro!by bodhi - Debian
Jeffy, Please post your output of dmesg. And also which slot (left/right) did you plug in the hard drive? which u-boot version do you have on the GF Net?by bodhi - Debian
Greg, Usually netconsole will give you lot of kernel messages, but not everything. So serial console is needed to troubleshoot problem like this. And also if you're running stock U-Boot, I don't recall if netconsole is availale either. The NSAxx series is quite easy to hook up serial console.by bodhi - Debian
theliquid, Yes, the latest Dockstar U-Boot one should work fine.by bodhi - uBoot
effendi, - Which U-Boot and kernel was you running on this Pogo before installing the new kernel? - Did you follow the instruction to set up U-Boot envs? This section: - Setup U-Boot envs: Disclaimer: The following U-Boot envs settings are recommendation only. If you don't have serial console connected, please do not attempt. Be aware that changing U-Boot env settings to the wrongby bodhi - Debian
Awesome! Note in booting multiple USB/SATA. If only one partition is labeled rootfs, then it will be found correctly. And it does not matter how many devices that contain Debian installation . But if more than one partition are labeled rootfs then you might run into the situation when the kernel uImage and uInitrd from one partition, but the actual rootfs is from another! In this situation, tby bodhi - Debian
theliquid, Yes, it should work fine. Your arcNumber is 2998 which is the Dockstar's. And that what's Jeff's script set to during installation. But as always, pls backup your kernel files or the rootfs before installing the kernel.by bodhi - Debian
Excellent! Thanks for testing it.by bodhi - Debian
Hi theliquid, Cool! so the classic DTB works fine after you've replaced it? I would like to include that fact in the 1st post.by bodhi - Debian
theliquid, It should work for the Pogo V1. But you should back up your rootfs before trying it. The archNumber should be set to 2097 to boot it. And as always, make sure you have serial console or netconsole connected before changing arcNumber. If you want to be extra careful, then list the V1 dmesg output and/or U-Boot boot log here so we can verify. EDIT: I believe arcNumber 2998 shoby bodhi - Debian
theliquid, This kernel is for the Pro with PCI. You can try to use the ox820-pogoplug-classic.dtb file that I've attached in this post: http://forum.doozan.com/read.php?3,15912,16053#msg-16053 Save your ox820-pogoplug-pro.dtb and replace this dtb to the same place, same name. And see if you can boot with it. The Classic does not have PCI controller, hopefully the DTB will tell itby bodhi - Debian
HighTower Wrote: ------------------------------------------------------- > looks like it burned... > I used usb-ttl board (PL2303) and now it doesn't > work, then I plug it into pc com port appears, but > no data can be send/receive > Try another cable TTL232R-3V3, it works itself, > but nothing is received then connect to stora... If you don't take precautioby bodhi - Debian
Arnaud, You kernel is too old. I'd suggest: 1. Run complete fsck. Let the system fix any filesystem errors that you might have. 2. Backup your USB rootfs. 3. If you can boot into Debian, then download and install new kernel from this thread (the latest is linux-3.14.0-kirkwood-tld-2-bodhi.tar.bz2 dated 21 April 2014): http://forum.doozan.com/read.php?2,12096 4. If you can not bby bodhi - Debian
@ebbes, I'd like to bring in your patch for Pogo V4 into the u-boot-kirwood repo. So if you prefer, I could take pull request. Or I could just check in your patch and commit (I've tested the Pogo V4 u-boot with your patch locally).by bodhi - uBoot
Greg, > Hi, Does anyone else have the problem with booting > after a power loss or a 'shutdown -h now'? My > NSA325v2 reboots (at the time of ethernet > initialisation or pretty soon after that) and does > that until I restart to_stock and then back > to_linux again. This is behaviour I've observed > with bodhi's linux-3.14.0-kirkwood-tld-2 and tlby bodhi - Debian
Check your serial cable, keep trying UART booting. Even if you destroyed your NAND, it should boot with UART.by bodhi - Debian
velo, If that is the content of the /var directory on SD card, then either the SD card file system itself has problem, or this U-Boot mmc driver has problem. I don't think it has anything to do with mtdparts. OTOH, If that is the content of the /var directory on NAND stock rootfs then it might be the mtdparts problem. You could try to reformat the SD card to Ext3 to see if the problem goeby bodhi - uBoot
This is a basic but completed set of U-Boot environment variables that is good for booting Debian/Arch using USB. Please be aware that mistakes in changing U-Boot envs could block you out the box, so please use this as a guide only if you have serial console or netconsole. 1. U-Boot version must be one that was installed by Jeff's script, or newer U-Boot that was manually installed (stocby bodhi - uBoot
Looker Wrote: ------------------------------------------------------- > Hello Bodhi, > > Thank you for your help so far, I have oe > immediate question regarding the "ethaddr=", does > this need to be the mac address off the bottom of > the device? > > Thanks Yes, it needs to be that MAC address on the sticker.by bodhi - uBoot
HighTower, To run new kernel/rootfs on HDD, you will need to install new U-Boot and install new kernel on your current rootfs, or get the new rootfs that I uploaded and use that. Running new U-Boot using UART is the same as running U-Boot from NAND. There is no difference after U-Boot is loaded. So there is no need to install U-Boot first. Just boot the box with new U-Boot using UART, and iby bodhi - Debian
HighTower, > so, I'm still wonder what to do next.. i checked > via uart that new uboot can be used. > You could flash u-boot in serial console. However, running new U-boot with old kernel is really overkilled, there is no point in doing that, IMO. So it is best to stay with UART booting, try to get the new Debian rootfs running first. After that, the rest is pretty easy.by bodhi - Debian
OK. Let's go back to the basic. The idea is to make the output of your printenv looks like mine. yours: baudrate=115200 bootargs=root=/dev/nfs nfsroot=: ip=::::::off bootcmd=bootp; setenv bootargs root=/dev/nfs nfsroot=${serverip}:${rootpath} ip=${ipaddr}:${serverip}:${gatewayip}:${netmask}:${hostname}::off; bootm bootdelay=5 ethact=egiga0 ethaddr=00:25:31:04:88:1D machid=dby bodhi - uBoot
I've just notice this. It does not look like a typical /root directory either. Do these files show up if you look at /root in another Linux box? ext2ls mmc 0:1 /root <DIR> 4096 . <DIR> 4096 .. <DIR> 4096 empty <DIR> 4096 games <DIR> 4096 opt <DIR> 4096 spool <SYM> 10 mail <SYM> 6by bodhi - uBoot
Looker, Yes, the u-boot envs that are needed to boot USB drive are not defined at all, they were gone! Below are what usually defined: ethact=egiga0 bootdelay=3 baudrate=115200 mainlineLinux=yes console=ttyS0,115200 led_init=green blinking led_exit=green off led_error=orange blinking mtdparts=mtdparts=orion_nand:1M(u-boot),4M(uImage),32M(rootfs),-(data) mtdids=nand0=orion_nand parby bodhi - uBoot
Looker, You are in good shape as long as you can see the u-boot prompt like that! I think your u-boot envs might have been messed up for whatever reason. So the first step is to get a listing for that at the u-boot prompt > printenv Most definitely, you only need to adjust u-boot envs to correctly boot the Arch rootfs on USB.by bodhi - uBoot
velo, Pls see my questions updated above. Copying /boot/uImage to /uImage as a work around is a nice temporary solution! but I'm still wondering why there is a difference.by bodhi - uBoot
Have you tried the latest Arch rootfs ? Both Debian and Arch have /boot/uImage, so the difference as shown is strange indeed. Update: Were both extracted into the same SD card? what fs is the card (ext2/ext3)?by bodhi - uBoot
HighTower, To use fw_setenv and fw_printenv, you must install u-boot-tools package first. apt-get install u-boot-tools And make sure your Debian env config file is consistent with this u-boot: # cat /etc/fw_env.config # MTD device name Device offset Env. size Flash sector size Number of sectors /dev/mtd0 0xc0000 0x20000 0x20000by bodhi - Debian
My pleasure :) It took some minor retrofitting to rebase this Oxnas 3.12 kernel to 3.14 (common PCIe kernel interface changes). I did try to look at OpenWrt patch, but due to my unfamiliarity with it, I could not see exactly what changes they've made!by bodhi - Debian
Nice! you can see the links I posted previously for how heychrist set u-boot envs and the new 3.14 kernel I've uploaded. This U-boot set the envs at 0xC0000 which is the same as other Kirkwood boxes, but the Stora uses a different location, so you need to set them manually and save at least once to get rid of the error message: *** Warning - bad CRC, using default environment BTW, Iby bodhi - Debian