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
dave Wrote: ------------------------------------------------------- > I've noticed something odd with my pogoplug pink. > I've searched a bit and found there are a few > reports of people with problems on the front USB > port and some where devices have stopped working. > I've got a similar problem. > My pogoplug kills USB devices that are plugged > intby bodhi - Debian
gee-man, After you're back running 3.3.2, could you get the list of your modules with lsmod and post the output here? Could be some missing modules that are needed by ipsec. Thanks,by bodhi - Debian
Veniq Wrote: ------------------------------------------------------- > As you can see, this guide by updating uboot > > http://projects.doozan.com/uboot > > is one of my steps to unbricking GFH at all (after > that my reset button will be active again so I can > flash stock firmware). But I can't complete that > guide at least because of I can't SSH toby bodhi - uBoot
Veniq, Looks like neither your USB or HDD rootfs is fit for booting. uBoot can't find the kernel images to load. Do these things: 1. Interrupt netconsole again and print out uBoot envs and post here. printenv 2. Shutdown and unplug both the HDD and USB drives. Use a different USB stick if you can (or use the same one if you are OK with erasing the content completely). On a differreby bodhi - uBoot
@pbg4, If for what ever reason that it does not work in NSA320, then I think it might be something related to the SATA port number assignments (the GoFlexNet runs different uBoot patched version) . Also, I've been wondering what the SATA port numbers assignment would be if we plug in a 4-disk eSata enclosure with port multiplier?!by bodhi - Debian
dinjo Wrote: ------------------------------------------------------- > I'm using a router , tried adding mac address too > didn't worked. Are the GoFlex Net and the netconsole server plugged directly in to the router LAN ports?by bodhi - Debian
dinjo Wrote: ------------------------------------------------------- > Yes i did that and also regenerated , I tried with > socat too but nothing shows up not sure why , > since its able to pass the messages prior to it It is strange. Try connecting the GoFlexNet and the netconsole server on the same Ethernet switch, see if it helps. If it still does not show all messages, then trby bodhi - Debian
Yes. It's a known bug. As log as your openssl works, I don't think it's matters. If anybody is aware that this does cause problem with openssl, please post.by bodhi - Debian
You only need to do this step: mkimage -A arm -O linux -T ramdisk -C gzip -a 0x00000000 -e 0x00000000 -n initramfs-3.11.1-kirkwood-tld-1 -d /boot/initrd.img-3.11.1-kirkwood-tld-1 /boot/uInitrd Note that you should do that after apt-get upgrade if the apt-get upgrade log shows that the initrd.img-3.11.1-kirkwood-tld-1 (or what ever kernel version is) was regenerated. When in doubt, regeneby bodhi - Debian
dinjo Wrote: ------------------------------------------------------- > I was more concerned with this warning in dmesg > have changed usbrootfs to use ext3 now. > > [ 35.595458] alg: hash: Test 1 failed for > mv-hmac-sha1 > [ 35.603134] 00000000: 0c aa 9f d5 37 c3 79 3a > 91 d9 21 5f 42 2b 2c 24a > This is the kernel bug for cryptodev HW acceleration. I havby bodhi - Debian
Please post your dmesg output.by bodhi - Debian