bugs181, A. The basic steps to install Debian on Pogo Mobile: 1. Install Arch first (to update u-boot): http://archlinuxarm.org/platforms/armv5/pogoplug-series-4 2. Create Debian rootfs on USB: http://forum.doozan.com/read.php?2,12096 3 . Setup u-boot envs to boot Debian with Arch U-boot version (do this while running Arch system) http://forum.doozan.com/read.php?3,11538 B. Toby bodhi - Debian
gulizi, I will provide a patch to the mainline kernel as mentioned here: http://forum.doozan.com/read.php?2,16044,16434#msg-16434by bodhi - Debian
@gulizi, Read a few posts back.by bodhi - Debian
kuemmel Wrote: ------------------------------------------------------- > Okay. > I installed Arch Linux on my Pogo. It runs > perfect, but the Debian doesn't boot from the > Flash Drive. > I've done everything as described but it won't > boot. > Can anyone help me? > > regards, > kuemmel To boot Debian with current Arch U-boot version:by bodhi - Debian
Ill, Sorry about this :) I was so sure that it's was included the Netgear patch in u-Boot. But you've found out the hard way, I missed that 1 line of code in the Netgear Stora patch!!! Must have been an editing error. Seems like other Stora users have not tried this feature. I will release a new u-boot version soon which will include this. Pls check back in a couple weeks.by bodhi - uBoot
metric, - Set up netconsole (if you don't have serial console): http://forum.doozan.com/read.php?3,14 - Power up and monitor u-boot boot log to see any error during boot. It is likely a power problem. But best to see the boot process to see if u-boot has failed bring up the hub.by bodhi - Debian
Quotemy next Oxnas kernel release (in about 2 weeks). I will include netfilter in this release.by bodhi - Debian
Brom, In kernel 3.14+ you should be able to select CONFIG_NETFILTER in make menuconfig. If you have trouble with make menuconfig, try make oldconfig: - manually edit the .config file to have CONFIG_NETFILTER=y - run make oldconfig and respond to each question. - then run make again to build If somehow it does not work for you, wait for my next Oxnas kernel release (in about 2 weeks)by bodhi - Debian
Brom, QuoteDoes that mean that I can skip step 9 and 10 with an older kernel or do I need a different file to flash? No, it means that you will need to make sure your current u-boot envs can boot old kernel. And change them if necessary. So if you're not sure how, then I would recommend to use the latest rootfs so that it conforms to requirement 3 in first post: 3. Your Pogo V3 is aby bodhi - uBoot
Ill, If the disk does not contain data, reformat it in Debian with parted. Or back up the data and reformat.by bodhi - uBoot
Quotepbg4 > if you don't use saveenv and something went wrong, > at the next boot you are at the same state as > before,.. Better advice :) and you can do this with netconsole too. Quotegaogao tks bodhi, I was under the assumption that using fw_setenv was not the preferred/safe way to set uboot params. IIRC I read about it some time ago. It is safe only if you have netcby bodhi - Debian
@gaogao, If you have netconsole then it is perfectly safe to modify kernel args to add a customed pararam at the end. For example, if your usb boot args is: usb_set_bootargs=setenv bootargs console=$console root=$usb_root rootdelay=$usb_rootdelay rootfstype=$usb_rootfstype $mtdparts $usb_custom_params then this would be enough usb_custom_params=coherent_pool=1M usb_set_bootargs=setenvby bodhi - Debian
@TEN, - ntp should work as it is instaled in rootfs - crontab should work too - in resolve.conf nameserver 8.8.8.8 You should probably create a new thread for these Debian packages installation discussion.by bodhi - Debian
TEN, All these behavior you've observed were intentional! I've setup this Debian rootfs as a basic Debian system. The rest are up to users who must install needed packages as they wish. Just like the debootstrap system installed by Jeff's script, and a few more tools to make it a little more convenient, but not too many extras, so that experienced users have to uninstall them, aby bodhi - Debian
TEN, Quote> So the arcNumber=3542 and NAND layout are correct > and compatible as they are for your uboot & Debian > 3.14, i.e. I should go ahead (even within Arch) > with uboot.2014.01-tld-1.pogo_e02.bodhi.tar Yes. Quote> install onto a second USB stick (i.e. only uboot > goes into NAND , but neither Arch's nor > Debian's kernel on Kirkwood) ?by bodhi - Debian
gaogao, Compare the output of lsmod lsusb between 3.13.1-kirkwood-tld-2 and your current installtion.by bodhi - Debian
TEN, No, your Pogo is NOT Pogo V3! I'm glad you've asked questions before trying the installation. You have installed Arch, and thus your system is # uname -r 3.1.10-13-ARCH And u-boot envs showed this arcNumber: arcNumber=3542 What you have is Pogo V2 (or E02) Kirkwood. So the correct thread for Debian kernel or rootfs is: http://forum.doozan.com/read.php?2,12096by bodhi - Debian
Thanks WarheadsSE! have corrected the link above.by bodhi - uBoot
herb, Looks like it is in the mainline: https://github.com/mibodhi/u-boot-kirkwood/blob/2014.01-kirkwood/arch/arm/include/asm/arch-orion5x/cpu.h /* Orion-1 (88F5181) and Orion-VoIP (88F5181L) */ #define MV88F5181_DEV_ID 0x5181 #define MV88F5181_REV_B1 3 #define MV88F5181L_REV_A0 8 #define MV88F5181L_REV_A1 9 /* Orion-NAS (88F5182) */ #define MV88F5182_DEby bodhi - uBoot
Looker, You've missed the single quote at the end: setenv usb_scan ‘usb_scan_done=0;for scan in $usb_scan_list; do run usb_scan_$scan; if test $usb_scan_done -eq 0 && ext2load usb $usb 0x800000 /boot/uImage 1; then usb_scan_done=1; echo "Found bootable drive on usb $usb";by bodhi - uBoot
@davygravy, Good to see you stopping by! interesting to hear you're using OwnCloud, but not a customized setup with LAMP?by bodhi - Debian
kuemmel Wrote: ------------------------------------------------------- > But whats about these step ?And what must I do at > these step? > edit /media/sdb1/etc/fstab entry for /dev/root to > match the rootfstype of your usb_rootfstype. There is no need to worry about this. Arch installation already set the rootfstype to Ext3.by bodhi - Debian
kuemmel Wrote: ------------------------------------------------------- > If I now understood everything correctly, the > first thing I had to to is install Arch Linux on > my Pogo as described on the page. Next thing I had > to do unpack the Debian file to a second USB Stick > from a random pc. Now i must unplug the first USB > stick with Arch on it and boot from the secoby bodhi - Debian
kuemmel Wrote: ------------------------------------------------------- > But i don't need Arch Linux on my Pogoplug.. Must > I have 2 Sticks installed on my Pogo? No, the first one is the result of the Arch installation. You can keep it around until after you have Debian running, then only one stick is used. It is good practice to have a fallback plan in case you can't bootby bodhi - Debian
kuemmel Wrote: ------------------------------------------------------- > is the usb stick then not overwritten with the > Arch ? Use different USB sticks for Debian and Archby bodhi - Debian
Stefnas, Try regenerating the /boot/initrd-xxx.img with update-initramfs -u command, and then generate new uInitrd with mkimage command. Watch serial console if you have one connected, for any abnormal activities during rootfs mounting.by bodhi - Debian
kuemmel, The easiest way to install Debian on Pogoplug Series 4 is: - Install Arch Linux first: http://archlinuxarm.org/platforms/armv5/pogoplug-series-4 - Download the latest Debian rootfs from this thread: http://forum.doozan.com/read.php?2,12096 - Extract Debian rootfs to a new USB stick follow the instruction , and boot with it.by bodhi - Debian
gulizi, This is what was defined by kref (the orginal author), so I kept it the same: mtd0: 00e00000 00020000 "boot" mtd1: 07200000 00020000 "data" It could have been kept as the orginal layout mtd0: 08000000 00020000 "NAND 128MiB 3,3V 8-bit" mtd1: 00e00000 00020000 "boot" mtd2: 07200000 00020000 "rootfs" If you don't intenby bodhi - uBoot
farsheed, > The only > issue is that the dockstar loses connection to > router after a day or so without any reason.I did > not have this issue with the older archlinux > install. I am not sure if the whole system > actually crashes or there is some issue with my > network/dhcp setting . Any ideas how to > troubleshoot this problem. .I was trying to find > sby bodhi - uBoot
gulizi Wrote: ------------------------------------------------------- > Thanks for the replys guys. > Another silly question, can I just use the > existing uImage in your debian rootfs? what is the > purpse of running mkimage ourselves? Reread the instructions, it's really 2 different types of installations. 1. Using pre-prepared rootfs, there is no need to generate uIby bodhi - uBoot