Daniel Wrote: ------------------------------------------------------- > I don't know if this is dead, or anything. > > I used the ALARM installer, and my PogoPlug Pro > boots into Arch pretty well. But I don't like > Arch. > > I downloaded the prebuilt Debian, and extracted it > onto another USB. When trying to boot from USB, > the PogoPlug blinksby bodhi - uBoot
gnexus Wrote: ------------------------------------------------------- > QuoteI also heard they've shipped the A9 dual > core model already. > > A9 dual core is not an Allwinner chip. It is > likely a MT6575. Of course you're right! not Allwinner: http://www.ebay.com/itm/Dual-Core-Mini-PC-Android-4-0-TV-Box-IPTV-1-2GHz-Cortex-A9-Google-USB-Dongle-HD-/1408521389by bodhi - Allwinner A10
Well, a bit of good news! I've successfully upgraded the PogoPro Debian rootfs to Wheezy. It was a massive upgrade to go from Squeeze to Wheezy, but it went relatively without incident! The only times the upgrade process stopped were a few normal questions when one upgrading from one Debian version to the next (e.g. the current settings should be reused? should daemons be restarted automaby bodhi - uBoot
This is the newer model 802 II: http://www.ebay.com/itm/3rd-MK802-II-Android-4-0-Mini-PC-Google-TV-Box-Internet-Wifi-Player-4-Ports-USB-/280959929508?pt=US_Internet_Media_Streamers&hash=item416a844ca4 I also heard they've shipped the A9 dual core model already. Anyone has seen it?by bodhi - Allwinner A10
Currently $29.99 at buy.com: http://www.buy.com/prod/pogoplug-mobile-wireless-backup-access-share-your-pc-mac-tablet/223435914.htmlby bodhi - uBoot
Gwapenut, Changing Jeff's script should be straightforward, not a problem. The real concern is the flash_erase and nandwrite steps in the script. We need Davy's confirmation that those statements in Jeff's script will work with Davy's uBoot, or if we need to do additional steps. I'm not sure, so I thought it would be best that Davy would take a look sometime and instruby bodhi - uBoot
@Davy, Please consider making this uBoot work with Jeff's installation script! As you probably knew, there was a Pogoplug Mobile inventory sale lately, so expect to have more users coming around and looking for uBoot, to install Debian :-)by bodhi - uBoot
I hope so too! netconsole documentation did not mention that it will only work for eth (nothing specific about wlan). You could give it a try on an unsecure Wifi network and see if it works.by bodhi - Debian
@WarheadsSE, It's been a while ago, but I think back then Debian version we used did not have this support. I guess now one can just copy the whole modules tree from ALARM to /lib/modules and use it as is, providing the installed Debian version has the support.by bodhi - uBoot
Sure, it should work. Have you got connected to the router by wireless with this module 8192cu before? You might need to try it on an unsecure network!by bodhi - Debian
There are a couple ways to migrate the USB stick to a larger one. See this thread: http://forum.doozan.com/read.php?3,9339,9339#msg-9339by bodhi - Debian
Thanks Davy, I'm sure it would work with your procedure. I had doubt about "/tmp/flash_erase /dev/mtd0 0 4". And I thought just for educational purpose, someone would analyze whether if it would work or not. IOTW, can this uBoot image be flashed the same way we ususally do with Jeff install script "install_uboot_mtd0.sh"? I guess I just need to study your procedby bodhi - uBoot
You should find out the name of the module that supports the webcam model that you have. Arch Linux wiki has a list of webcams: https://wiki.archlinux.org/index.php/Webcam_Setup#Linux_webcam_support After identifying the name of the module, look for that inside your Arch Linux ARM rootfs USB drive. It should be somewhere under /lib/modules. Once you've found it, copy it to the same locatby bodhi - uBoot
Hi Davy, Thanks for the new UBoot. I've finally installed it on most of my plugs. Seamlessly! BTW, please check the README file in each folder on your Dropbox, they seem to be unreadable. Thanks, bodhiby bodhi - uBoot
Use netconsole to troubleshoot Debian kernel booting For instruction about setting up netconsole to troubleshoot uBoot, see instruction on Use netconsole to troubleshoot uBoot without a serial cable.This post continues where Jeff's instruction ended: Using netconsole to troubleshoot problem in starting kernel. There are also a couple other approaches (adding uBoot custom boot parameters aby bodhi - Debian
@Vlad, Jeff, Davy, and other Debian kernel builders, I have a question regarding the modules load order created during kernel compilation. So far I've been successfully forced certain modules to be loaded sooner in the booting process using these commands to update the initramfs image (initrd.img-3.2.xxx). /etc/initramfs-tools#modules # edit this file to add module names update-initby bodhi - Debian
lijianch Wrote: ------------------------------------------------------- > Varkey > > I appreciate your debian files. It works like a > charm. It has been on for a long time at my house. > > > Now, it comes to a situation that I need a linux > webcam on this pink box (pogoplug pro v2). > However, the existing kernel does not load wecam > modules. I haveby bodhi - uBoot
Hi Davy, I've downloaded uboot.nandpogoV4-MMC-mtdparts-noSATA.kwb.tar.gz. Before flashing it to the Pogoplug V4 NAND, I want to make sure if I understood it correctly. Can this be flashed from inside Pogo stock OS the same way described in Jeff's instruction in the old page? I'm wondering about flash erase 4 blocks, is that applicable here? - downloading flash_erase andby bodhi - uBoot
@Vlad, Update on the Dockstar booting with no L2 workaround: I found that the kernel boots only intermittenly only. But it does boot a few times among several tries! and it would not boot at all on the GoFlex Home.by bodhi - Debian
Thanks for the JST header link! Just to be clear about the upgrading trouble I had. I think most likely it's udev-related because it's one of the significant updates from Squeeze to Wheezy. Hopefully when I have a chance to hookup the serial console, it will provide more information. By the way, it's great that we can even run Debian on this box :-) it's a bonus reallyby bodhi - uBoot
I mispoke a litle bit above: I also briefly looked into using netconsole to troubleshoot the problem, but don't think this Uboot version support it (not entirely sure about this, I got no clear response from others) I've opened up the case to check out the Sata port to make sure I get the right cable. But I have not bought the serial header yet. I'm a little bit discourage toby bodhi - uBoot
bharath Wrote: ------------------------------------------------------- Does it just require one to copy the > kernel modules, firmware and led related tools > from the ALARM rootfs? Yes, basically that's the first steps we need to do to start booting with Debian rootfs. We also need other minor things such as Mac address, LED settings and depmod in rc.local. The first post basiby bodhi - uBoot
Definitely, yes. I think it's worth trying that. But I would also set up netconsole right after installing the new stick. That way you will have more info to troubleshoot (i.e. At least that will tell you there is something wrong with the rootfs, not the boot image if it's done booting UBoot).by bodhi - Debian
jedie Wrote: ------------------------------------------------------- > My old USB Stick is broken and my dockstar debian > system is away... (I can connect to the dockstar > into the rescue system.) > > My question is, how can i create a new debian on a > new USB stick? Exist here anywhere a simple Image > that i can put on a USB Drive? Something like > http://arby bodhi - Debian
Vlad Wrote: ------------------------------------------------------- > Hi bodhi, > > does it also boot without > > General setup -> Embedded System -> Enable > Patch physical to virtual translations at runtime > -> Disable > and setting PHYS_OFFSET to 0x00? Hi Vlad, You got me curious, so I rebuilt 3.2.26 without these 3 parameters. It boots on myby bodhi - Debian
It does not need to since the bootm has no second parameter.by bodhi - uBoot
You could find the definition easily, google for UBoot, uImage, uInitrd. Basically, uImage is the kernel image that UBoot expects to find, uInitrd is the ram disk image. Debian uImage is built to work with UBoot. uInitrd contains the initial roofts (not the real one), which usually contain drivers that are needed at boot time. The rest of the drivers are loaded as modules later (I've simplifby bodhi - uBoot
Just a thought to show what is possible :-) a variable contains true/false after a certain condition is met. So that could be used in the bootcmd. No I did not use different label for SATA partition, since I only want to boot exclusively when a drive is attached. iIf USB drive is attached, I only want to boot from there using a SATA drive that does not have "rootfs" label. (note thatby bodhi - uBoot
Just some suggestion and random thought on multiboot. Let's dissect this envs listing from a GoFlex Net. Basically, we see 5 relevant parts: 1. USB Boot 2. SATA Boot 3. Netconsole 4. Rootfs label 5. bootcmd To tell UBoot to boot from a correct partition, a rootfs label is the most elegant way. It can be used to set each boot partition to a label and tell UBoot to find it. To creby bodhi - uBoot
Hi Vlad, I have not tried that yet! I set these values so that I can use the same 3.2.x build on my other plugs, which still have Jeff's original UBoot on them. If you want to confirm that, I could rebuild another version without these parameters and try them? bodhiby bodhi - Debian