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
Ricke, No problem. Will do that.by bodhi - Debian
Mint, You must be using a self-built patched uBoot with MMC ? Try adding another couple extra "mmc init" to the bootcmd_mmc env. UBoot mmc is a little slow detecting the card.by bodhi - Debian
Max, Easiest way to boot Debian on GoFlex Home is to use this rootfs (latest is version 3.12.0). http://forum.doozan.com/read.php?2,12096by bodhi - Debian
Debian rootfs 3.12.0 was uploaded. Please see 1st for download link.by bodhi - Debian
gee-man, Since you're going to roll your own kernel, I would recommend to have serial console to watch the kernel booting progress. Netconsole does not show you the type of details needed to troubleshoot kernel booting.by bodhi - Debian
daveeeee, How did you create your rootfs? from davygravy's NSA320 image? or from Jeff's script and then later upgraded with davygravy's kernel 3.3.2? Do you have enough space in /boot ? Another thought, what's your output of cat /etc/apt/apt.conf ?by bodhi - Debian
> Probably simply a power limitation. I think ingmar_k is right :) The simplest approach is to use the GoFlex Home power brick, which provides a lot more juice (it is designed to drives 3.5" HDD). You can buy it from eBay. @Organized: have you tried plugging the HDD after the system is running? it is perfectly OK to do that on GoFlex Net.by bodhi - Debian
gee-man, > With those patches removed, does this mean the > 3.12 kernel will not work as well as earlier > versions? It works the same way. Just a matter of copy files back to their old place, and modify the configuration files to point the the old location. To compile the kernel you will need to apply the patches. Without them, the mainline code won't work for Kirkwook boxby bodhi - Debian
ingmar_k, I've been running kernel 3.12 on the GoFlex Net since Linux version 3.12.0-kirkwood-tld-1 (root@tldDebian) (gcc version 4.6.3 (Debian 4.6.3-14) ) #1 PREEMPT Fri Nov 8 15:57:44 PST 2013 13:27:42 up 1 day, 11:25, 1 user, load average: 0.15, 0.05, 0.06 free -m total used free shared buffers cached Mem: 120 109by bodhi - Debian
ingmar_k Wrote: ------------------------------------------------------- > This is probably a question of wether the HFS+ > support is included in the kernel that you use, or > not. ;-) Exactly! IIRC, the default installation does not have HFS+ turned on in the kernel. @Mierscheid , Look in your config file (/boot/config-3.xx.x-xx) for CONFIG_EFI_PARTITION CONFIG_HFS_FS CONby bodhi - Debian
daveeeee, This is my autoremove settings. I think you should have "^linux-image.*", and other options too, in your NeverAutoRemove list. Modify your list and reboot to verify that it takes effect after the next boot. Remember to check your kernel files in /boot to make sure they are consistent before you reboot. See it will let dpkg finish. cat /etc/apt/apt.conf.d/01autoremovby bodhi - Debian
daveeeee, Output below is normal. Since the kernel source is not included in the kernel deb package. You can safely ignore it. > > dpkg -i > linux-image-3.12.0-kirkwood-tld-1_1.0_armel.deb > Selecting previously unselected package > linux-image-3.12.0-kirkwood-tld-1. > (Reading database ... 53050 files and directories > currently installed.) > Unpacking linuxby bodhi - Debian
Kernel 3.12.0-kirkwood-tld-1 package was uploaded. Please see 1st post for download link.by bodhi - Debian
Max, Plugging in the Western Digital My Book Essentials HDD should not cause problem like that! if you can't get it solved at Arch site, come back here and we'll help.by bodhi - Debian
Max, It probably quicker to get help if you ask at Arch forum. In any case, for the "connection refused" problem, did you wait long enough? I would wait about 5 minutes or longer to see if you can ssh in.by bodhi - Debian
Kayot, Replace your Arch rootfs with Debian rootfs 3.11.1, get it from here: http://forum.doozan.com/read.php?2,12096 Regarding the nanddump, if you did ssh and dump all mtds before installing Arch, I see no reason why it woud not work later when you restore it.by bodhi - Debian
@mbmsof, Please repost this problem in a new thread (It should be in uBoot section). My question was: is only one of the 2 disks have Linux system on it? or both?by bodhi - Debian
gee-man, The source should be from kernel.org with no patch. I'm not familiar with shyd's tool chain so can't comment on that. But it should compile if it is for the Dockstar. The problem you might run into is the difference in config options. I'm building kernel 3.12, and will take a look in the config to see if any AES-related option is missing. (UPDATE: just checkedby bodhi - Debian
mbmsof Wrote: ------------------------------------------------------- > Hi, a few days ago that u-boot install in my > nas320 and everything works perfect, but today > tried to install a second hard drive and now not > boot. > > Hard drives are Seagate 2TB, with either boots, > but if I put the two no. > > This is what appears when you start: > >by bodhi - Debian
ingmar_k Wrote: ------------------------------------------------------- > Maybe the modules are now built in? Already > checked the kernel config? The modules were not built in. But I have not compared the 2 configs to see if any thing AES-related missing.by bodhi - Debian
For the second nc command, instead of nc -u 192.168.1.100 6666 try nc -up 6666 192.168.1.100 6666by bodhi - Debian
Veniq Wrote: ------------------------------------------------------- > How I can disassemble GFH cradle? I put out two > screw that was under rubber legs so I can open > only that side of cradle... opposite side seems > closed. :( No, it is not. It only looks that way. The bottom plate has several hinges that hold it snugly fit to the case. After taken off the 2 screws, use aby bodhi - uBoot
Only the serial module converter, the header might not be applicable (depending on whether the header was pre-installed or not). First, open the GF Home first to check if the header is installed or just holes on the board. Pics from Arch site: http://archlinuxarm.org/forum/viewtopic.php?f=18&t=3397 If there is already serial header then you can use wire testing clips to connect them. Aby bodhi - uBoot
Dave Wrote: ------------------------------------------------------- > Nothing. Just pulling the device. > USB sticks had not been mounted with the mount > command to be accessible but showed up in /dev > Serial adapter was in /dev and a udev rule had > created a sym link to it. But I pulled that one > out whilst the unit was rebooting. > > Never killed a device oby bodhi - Debian
gee-man Wrote: ------------------------------------------------------- > The results of lsmod are attached. Since > installing 3.11.1, I have experenced other > problems with samba, and failed reboots. gee-man, There are differences in the list of modules loaded. I suspect that is your problem. I would do this: Make a clone of your USB 3.3.2 rootfs stick. Use the new stick,by bodhi - Debian
Veniq Wrote: ------------------------------------------------------- > I doesn't understood nothing in Debian topic so I > follow yours advice and made bootable USB with > Arch onboard via last link that you posted here, > connected it to GoFlex dock, rebooted device and > it successfully start kernel. > > So I pushed new UBOOT via Jeff's guide: > >by bodhi - uBoot
Arch Installation here: http://archlinuxarm.org/platforms/armv6/pogoplug-v3oxnasend-lifeby bodhi - Debian
Veniq, > You said 'right' - so, new USB stick will really > help in my situation or it still just 'worth a > try'? Try it and see if it works. Or better yet, if you intent to run Arch, then get the Arch rootfs tarball from: http://archlinuxarm.org/platforms/armv5/seagate-goflex-home (see installation step 12), and try booting with it.by bodhi - uBoot
gee-man Wrote: ------------------------------------------------------- > Hi, can someone post the kernel config again? The > link in post #1 is not working anymore... Also, > was this kernel built with any sort of patch > files? > > Thanks, You can find the kernel config file in /boot directory. Should be something like this: config-3.3.2.xx-kirkwood-xxxby bodhi - Debian