The reason I am asking is the following: You will have to wait anyway for all the "usb start" calls to finish. And I don't know the exact code, so I don't know if it's a good idea, bad idea, or if it doesn't matter how often you run it. So my reasoning would be: Better run it once a wait a few seconds before. But in the end it probably doesn't matter, and is mby ingmar_k - uBoot
Just a quick question, out of curiosity: Why run "usb start" more than once, instead of using a wait/sleep command to insert a break of a few seconds before running usb start once?by ingmar_k - uBoot
Big thumbs up from me for your persistance, bodhi! If this ever gets resolved, dinjo should at least treat you with a free beer or something similar (http://startupstats.com/startup-trend-beer-2012-03/). ;-)by ingmar_k - Debian
You have netconsole, that is a great start. Now the next best thing to do is to stop the boot process and issue a "printenv" command. Then post the output here. Much more useful than just the failing default boot process you posted above. ;-)by ingmar_k - uBoot
Good luck! I hope you get it to work soon. I know those embedded device topics and their specifics are not very easy to understand at first. But I guess you will learn a lot if you read up on it. The trick is not to give up too easy. The good thing is that it is virtually impossible to really brick the Pogoplug V3. Even if you completely erase the NAND, you can always still boot from SATA.by ingmar_k - uBoot
@SCrid2000: You might not like a lecture, but from what you continue to write, you definitely need(ed) one. The kernels that I provided were and still are strictly for testing purposes. If you do not understand that hint and its implications, then don't use stuff like that. Simple as that. Howto resolve your situation: I already gave you the hint, but I will describe it again, more detby ingmar_k - uBoot
As bodhi already provides a 3.12 kernel, you can be pretty sure that the problem is taken care of. It probably was "just" (understatement ;-) ) a question of changing the original 3.11 patches a bit.by ingmar_k - Debian
Simple: Using the external libaccept4 solution is kind of a half-assed solution. You still have to edit some udev files and there isn't even a official debian package providing libaccept4. Besides, the accept4 support was in the kernel since 2.6.28 or something like that, but simply was not enabled, because there was no need for that until udev started requiring it. So, the kernel IMHO isby ingmar_k - uBoot
Hi, I noticed a strange problem. I first compiled my own 3.11.6 kernel uImage and saw the problem and now tried your kernel 3.12 with the same results. I have tried to setup different swap partitions/files whatever, which get recongnized and seen correctly, but it seems that these never get used. And that, although free memory gets VERY low while copying huge files. Even to the point wheby ingmar_k - Debian
Probably simply a power limitation. Those 7200rpm drives tend to have pretty high startup currents. Especially the older models. And the Goflex + its external power supply can only deliever as much. You can maybe get around this by using a higher rated 12V power supply, plus soldering some thicker cables from the 12V plug to the SATA ports power pins. I think I saw something to that extent in tby ingmar_k - Debian
I'm sorry to write the following, but if you had truly read the instructions, you would have realized that a serial connection to the device is nearly indispensable. Especially when changing something kernel related. And from what you wrote I guess you don't have a serial connection set up, yet. Right? Besides that the device can still be booted via SATA. Oh and BTW, let me guess:by ingmar_k - uBoot
I now remeber having had a similar problem some months ago. Ubuntu seemed to have HFS+ support enabled by default, while Debian does not.by ingmar_k - Debian
This is probably a question of wether the HFS+ support is included in the kernel that you use, or not. ;-)by ingmar_k - Debian
If I remember correctly, some of the WD drives have a USB to SATA controller that also implements an extra (virtual) drive. That very virtual drive could probably get in the way and hinder the normal boot process. ;-) Worth checking out, I think.by ingmar_k - Debian
Maybe the modules are now built in? Already checked the kernel config?by ingmar_k - Debian
joebob2000 Wrote: ------------------------------------------------------- > I tried working through your instructions for > creating a SATA boot drive for the pogopro but you > kind of hand-wave over the issue of wheezy not > having the right kernel. >... Now let me think, why would I do that...? Hmm.... Maybe because it just works, if you use the kernels that I provide?by ingmar_k - uBoot
And if you feel like trying Debian (after having installed Arch!), then you could have a look at this: https://github.com/ingmar-k/Pogoplug_V3_Emdebian_Debian.gitby ingmar_k - Debian
As I already wrote on the Arch Linux forums: The easiest way is direct SATA booting using my Emdebian/debian scripts. So in short you take a SATA drive and create a new Emdebian or Debian install on it, using my installer scripts and the corresponding settings. Then you connect that harddrive to the internal SATA port of the Pogoplug.by ingmar_k - uBoot
Just updated my scripts with support for booting directly from SATA. Everything is documented in the README.md, as always.by ingmar_k - Debian
Just added an option for directly booting from SATA to my Debian/Emdebian scripts: https://github.com/ingmar-k/Pogoplug_V3_Emdebian_Debianby ingmar_k - uBoot
Hmm, I might be wrong, but segfaults don't sound like a apt-get database problem to me. With a database problem shouldn't you just get some error message, telling you that the operation can't be done correctly, or that a dependency can't be satisfied, or something of the likes? Segfaults sound more like a hardware problem, or running out of RAM. But that's just my 2 centby ingmar_k - Debian
Do you have a sort of swap partition defined? What does the command "swapon -s" say? If not, you are probably running out of RAM. Either that, or maybe your rootfs is corrupted.by ingmar_k - Debian
http://www.debianhelp.co.uk/samba.htmby ingmar_k - Debian
Eric Wrote: ------------------------------------------------------- >... > In general, can I run any program on start-up by > simply typing in "update-rc.d ProgramName > defaults" into the console, and then looking for > the ProgramName in the </etc/default/ProgramName> > entry to make sure daemon is set to yes? I don't know if I understand your qby ingmar_k - Debian
Did the update-rc.d command create the corresponding links in the /etc/rcX.d/ folders, too? If not, something went wong and that's why it doesn't start. You probably should try to start motion once manually first by running "/etc/init.d/motion start". That's in order to see if the script in /etc/init.d/ does work at all. If this works, starting it automatically when sby ingmar_k - Debian
Is there a start script for motion in "/etc/init.d/" ? If not, the command you posted can't ever work.by ingmar_k - Debian
Hello, I finally have reached the point, where I think I can officially annouce my scripts. They are available here: https://github.com/ingmar-k/Pogoplug_V3_Emdebian_Debian Features: - build a Debian or Emdebian rootfs for the Pogoplug V3 - include a kernel image - setup the system so that it should work from the get-go if you give the scripts the correct input - wireless support inby ingmar_k - Debian
I've got a interesting problem at the moment. I got the patched 2.6.31.14 Medion kernel to work with wheezy, as stated before. Problem is: The module loading of the gmac ethernet module takes AGES, thus some debian init processes (procps, networking, ssh) fail, due to the delay. If run later on, all he inits work perfectly fine. I'm experimenting with building in the gmac suppoby ingmar_k - uBoot
It probably just describes the procedure of flashing a uImage to the backup/secondary kernel area of NAND, at the 0xB00000 address. And also the command to explictly boot that secondary/backup uImage, instead of the primary/main uImage. That should be all. I don't know chinese, but the commands look very familiar. Like here (section "Flashing and testing a new kernel"): https:by ingmar_k - uBoot
I honestly don't know why raniadoll answered here, but I have to say that gnexus's suggestions does indeed make sense to me. Allwinner A10 for a long time wasn't the best choice anymore. So, something else than A10 as the name would be great.by ingmar_k - Allwinner A10