My bad. I must have done something wrong the first time I tried it, I now have an Ext3 stick booting to bodhi's rootfs and I can access it via ssh, so should be able to run jeff's Wheezy install script from there.by cefn - Debian
I've run the script as suggested and it's allegedly rebuilt my uBoot environment. How do I establish anything about my uBoot environment? The location 0xC0000 means nothing to me, and I don't know how to investigate what filesystem uBoot is set up for. I ran Jeff's uBoot updating script as suggested, and answered 'y' when it suggested changing the environment.by cefn - Debian
Hi, all. Can someone suggest an install sequence for Wheezy which will work on a Pink Pogoplug which was previously successfully installed with Squeeze via Jeff's script. I've done nothing to the Pogoplug's NAND build except for deleting the pre-existing debootstrap files following instructions to (unsuccessfully) work around the --no-check-gpg error. The However, the error rby cefn - Debian
Is there now a scripted sequence to go from a stock Pogoplug to one with an up-to-date wheezy kernel (which scripts the fixed uboot setup or works around it in some way)? If it exists I'm hoping to provide a link and description from my page as people still arrive there sometimes I think.by cefn - Debian
Indeed the MPD system was working, and controlling a local USB soundcard, but I couldn't stop there. I wanted to be able to send the centrally controlled audio around to other parts of the house (I have various NSLU2 devices around the house running Debian with soundcards and wireless). There is a major problem with this as detailed below. One answer is as following... #On the machine youby cefn - Debian
If I didn't make this clear, it is now a working configuration of MPD, and sounds OK once these steps were taken. I shouldn't need to change anything else I hope.by cefn - Debian
Hopefully I've remembered all the steps. Originally I had trouble with the C-Media USB card identifying itself with the right card identifier for MPD to pick it up, after getting MPD functional, I couldn't connect from a remote machine with an MPD client, and after connecting using ncpcpp I had skips and gaps in playback, which seemed to be to do with buffering or transcoding or somethiby cefn - Debian
Eric, Would love to learn if the script I proposed works for you (search "pogoplug wheezy fix" on google as I have trouble with links here). So far I've no corroboration beyond my own single test case.by cefn - Debian
Don't worry Davygravy, I'm not suggesting uboot+kernels =>3.2 will end up fixed by another route. I'm just trying to get informed. I think in response to Quoteastker Just wondering why you choose to upgrade to 3.1.0 instead of 3.3.3 thereby skipping 3.2? ...and... Quotedavygravy Also wondering... 3.3.2 is fine - no bugs, and 3.4.1 is just around the corner. Because thiby cefn - Debian
And just to clarify, are you saying the sequence of steps to upgrade my uBoot as detailed at http://forum.doozan.com/read.php?3,6965,6965 is no longer necessary if I want to run 3.3.3. Even without following this kind of sequence, you're saying 3.3.3 will just work by running dpkg -i with an appropriate kernel .deb file. I think I've been misled by statements which appear a lot in thby cefn - Debian
Thanks for the feedback. I find specifying what I'm doing in this much detail really useful to get people's perspectives on how to do it better, and I'm sure you're right. Could you suggest a reliable location from which I can get the proper kernel file (linux-image.***.deb) via http, and I'll add that into the script instead. My main intent, (and I hope this willby cefn - Debian
I've prepared a script which manages an upgrade from Debian Squeeze ( stable, as installed following http://projects.doozan.com/debian/ ) to Wheezy (testing) reliably, using only apt tools and the debian repositories. It works at the time of writing this post. It must be run as root of course. Try it at your own risk, but these steps worked on my Pink Pogoplug. Instructions at http://cefnby cefn - Debian
Thanks for your work on this, everyone. Still figuring things out. @davygravy if I was to go down the uboot route, I think the instructions you're referring to are these pretty long and detailed ones to build your own uBoot (note message id), figuring out the correct device identity (which I'm not sure of myself on my pink Pogoplug)... http://forum.doozan.com/read.php?3,6965,6965#msby cefn - Debian
I thought I needed a new Uboot to run kernel 3.2, but use of wheezy packages itself should be fine on the Pogoplug. I'm basing this on the fact that the Wheezy upgrade used to work before the kernel upgrade. Is that mistaken? Because of the complexity of fixing Uboot, my plan was to try and work out how to run a version of wheezy without completing the upgrade to 3.2, which I don't rby cefn - Debian
For reference, the instructions suggested at http://fzr.squeenus.com/debian/ which have an equivalent to Jeff's Squeeze installer script, but for Wheezy, fail with the error... "Kernel too old!" ...when running from the Pogoplug's regular shell. I imagine this script can't be run from a Debian Squeeze shell, as it would be overwriting its own system partition. Havingby cefn - Debian
I don't know how others are successfully a Wheezy build. After another two hour process I've once again got a Pogoplug which doesn't boot after trying to upgrade to wheezy from squeeze, based on the debian repositories and hitting the 3.2/uboot regression. Since 3.2 everything seems to be impossible, require serial hardware etc. It would be REALLY valuable to have a statement ofby cefn - Debian
Hi, All I have a Sytronix device which I bought specifically for the hack, and was pleased to find it has the same identifier as expected. From lsusb... Bus 001 Device 018: ID 1403:0001 Sitronix Digital Photo Frame I found it had showed up at /dev/sdb and the hack script resulted in a screen showing 'baks r ok', but I was surprised to find, that it reported... $ ./hackfw.sh /devby cefn - Displays