For the Dockstar top mini USB plug, this adapter works great: http://dx.com/p/usb-a-female-to-mini-usb-5-pin-female-adapter-26780by bodhi - Debian
I've uploaded an update for Kirkwood linux-3.12 for testing: added supports for Zyxel NSA325 and NSA310. For those who have the NSA325 and NSA310, and perhaps NSA320 also, please try this kernel and let me know if it works for you or there is any problem. If every thing goes well, I will update the main thread to include this deb package, along with the patch and headers. This tarballby bodhi - Debian
Andi, I'm regression testing with other plugs, and will upload it today or tomorrow.by bodhi - Debian
Cool! Glad it works well for you.by bodhi - Debian
GeorgeRosar, Your uBoot envs for bootargs were not setup correctly. alarm_args=setenv $boot_args_console root /dev/mmcblk0p1 rootwait rootfstype ext3 alarm_boot=ide reset alarm_mmc=mmc init; mmc init; ext2load mmc 0:1 0x800000 /boot/uImage; ext2load mmc 0:1 0x1100000 /boot/uInitrd; setenv device /dev/mmcblk0p1; run alarm_args; bootm 0x800000 0x1100000 arcNumber=2097 baudrate=115by bodhi - uBoot
ingmar_k, This is a very exciting development :) it is Debian right? did you cross compile or native? so we will just flash it in the same NAND partition and use Arch or stock uBoot?by bodhi - Debian
dinjo, What is you /etc/fstab looks like?by bodhi - Debian
SOL, I'll extract the patch and build it in the new kernel release and you can test it!by bodhi - Debian
Tommes, Indeed, you are running the GoFlex Net as the Referrence Board. Meaning it runs as a Sheeva Plug. This is needed because you're running Kirkwood kernel from mainline. So after you've installed my kernel 3.12 or davy's 3.3.2, you can change the uBoot env arcNumber to the correct one. But before changing any uBoot env, make sure the new kernel is running, and set up neby bodhi - Debian
Hi Mark, I forgot :) I've already uploaded kernel 3.2.28 back in March. Try this and see if it has what you need. http://forum.doozan.com/read.php?2,11601,11601#msg-11601by bodhi - Debian
I got the Arch pach which includes NSA325 from their GITHub.by bodhi - Debian
dinjo Wrote: ------------------------------------------------------- > Hmm,.. not sure why its a delay but I'll just let > it go but i could not figure out why its not > allowing me to go to command mode in netconsole > i.e its in readonly mode. It meant your netconsole server nc or socat... Is not working correctly. The box side is working. Tried different programs? &by bodhi - Debian
Tommes, It is the kernel. The Kirkwood kernel in mainline does not have the GoFlex Net patch so you are probably running the Dockstar version. You can try either that 3.3.2 kernel, or this 3.12.0 kernel (latest): http://forum.doozan.com/read.php?2,12096 Also, at Debian command line, please print both your cpuinfo, and uBoot envs and post the output here (it will confirm which machine yby bodhi - Debian
Hi Mark, It might work, but I'm not sure, though, because it was a little old. In fact, I have 3.2.26 and 3.2.28 kernels saved in my build folder! I could take a look to see how different the patch is for Pogo E02. But if you want to try the kernel 3.2.28 as it was built, then let me know and I'll upload it. In the mean time, could you verify that you are running the latest uBoot?by bodhi - Debian
@SOL, If you can find where to get the patch, I'll build and release a new Debian kernel. I think WarheadsSE already solved some show-stopper problem for this box.by bodhi - Debian
See this also: http://forum.doozan.com/read.php?2,12096,12450#msg-12450by bodhi - Debian
Agreed. It does not matter, which ever way works to get around the problem is good enough :) My observation from reading uBoot code: - the time out value for starting either MMC or USB in uBoot code is 5ms max. This duration might be too short for certain USB thumbs or SD cards, they certainly have different build quality. My observation from uBoot serial console behavior: - the warm staby bodhi - uBoot
Ingmar_k, I have not tried that. But my thinking was during warm start, the scan timeout period is set too short in uBoot code. Iirc, the reset excutes different code during cold start.by bodhi - uBoot
ingmar_k, > (http://startupstats.com/startup-trend-beer-2012-03/). ;-) :)) thanks for the interesting link. I suspected that dinjo's rootfs is taking more time to mount then normal.by bodhi - Debian
We will drink no wine before its time :) So after testing on my GoFlex Home, I've uploaded the 2013.10 uBoot image for GoFlex Home. Please see 1st post for download link.by bodhi - uBoot
Sherman, It's likely that the brand of your USB stick. Some takes longer to be reset. In the past, people have discovered this problem, some sticks are OK with cold boot, but have problem with warm boot. The most reliable brand is Sandisk (based on my own experience, and other reports). Your log showed that in the warm boot, the USB stick was timed out during "usb start". Howby bodhi - uBoot
vds Wrote: ------------------------------------------------------- > [*]Verified your rootfs worked for usb-key disk > only. It should work fine with hard disk. It does not make any difference what type of disk the rootfs is on. Could be thumb drives, HDDs, SD cards ….by bodhi - uBoot
dinjo, Your HDD or kernel is taking too long to boot up. It took 23 seconds before the disk is fully recognized, and then at that time it took another 10 seconds for netconsole to run. And eth0 was already up by this time. As comparison, mine takes about 6 seconds on the GoFlex Net (instead of 23), and eth0 was not up yet at that time. A sure way to tell what's really going on is to coby bodhi - Debian
Hi markweng, I used the wrong extension :)! sorry about that. Just use command tar without the j option: tar -xf uboot.2013.10.goflexnet.bodhi.tar.bz2 Update: Fixed the archive file name to uboot.2013.10.goflexnet.bodhi.tarby bodhi - uBoot
I've uploaded a new uBoot 2013.10 image for GoFlex Net. Please see 1st post for download link, description, and installation instruction.by bodhi - uBoot
vds, You are running the latest uBoot version for this box. The easiest way to recover is using this wheezy rootfs (latest version is 3.12) . Put this rootfs on another USB thumb, and boot it. http://forum.doozan.com/read.php?2,12096 After you've booted into Debian, mount your USB and take a look to see what is missing. If you have a lot of packages installed on it , then you shoulby bodhi - uBoot
@moddy, As dinjo suggested, it's better to use a label to make sure it is mounted as rootfs (UUID should work, but not full proof). See this thread: http://forum.doozan.com/read.php?3,8044,8152#msg-8152by bodhi - Debian
Max, To make sure that udev does not reassign eth0/eth1 every boot, see this post: http://forum.doozan.com/read.php?2,13053,13070#msg-13070 Those 2 files mentioned in there are important. Mount the disk on another Linux box, or Live CD and check and correct those files. Your problem might have been as simple as that. To boot with SATA, you will need to change uBoot envs. Below are 4 nby bodhi - Debian
@daveeeee, Sorry, I'm out of ideas :) not sure what's in your rootfs would cause the auto-removal like that. We've tried the apt configuration files that I'm aware of.by bodhi - Debian
There is not enough info here to undestand your problem! Have you connected this serial converter to any other boxes to verify that it's working?by bodhi - uBoot