Show all posts by user

Re: Linux kernel 3.2.28 Kirkwood package - 12 years ago

Hi chessplayer, There is really no special reason why I'm still on kernel 3.2.x. I tend to upgrade slowly to get the most stable kernel, and still get the latest packages for the OS. IMO, if you run Kirkwood, then you should use Kirwood-patched kernel 3.2.x. or later. This is because of discovery of problem in booting older uBoot with kernel 3.2.x, and also problem with chip timing. These

by bodhi - Debian

Re: [Pogoplug Series 4] Booting Debian with Arch Linux ARM uBoot - 12 years ago

duduke Wrote: ------------------------------------------------------- > bodhi, How can I revert to Arch uBoot if I've > already installed davy's uBoot on my PPV4? You could do it from Linux command line, if you have a saved mtd0 image (saved after you've installed Arch). Be careful to note the size and the mtdparts payout.

by bodhi - uBoot

Re: Linux kernel 3.2.28 Kirkwood package - 12 years ago

Updated 1st post to attach the patch file.

by bodhi - Debian

Re: [Pogoplug Mobile] Install uBoot/Debian - 12 years ago

Hi Twinclouds, Sorry I was a little too vague about the starting point! that was because post was copied from another thread, i.e. context:) I will update it to be a little more elaborate. 1. The goal is to flash this uBoot from Linux environment. Davy's instruction for this uBoot was written to show how he installed it from serial console. See here: http://forum.doozan.com/read.php?3

by bodhi - Debian

Re: Booting Debian on Pogoplug Pro - 12 years ago

thespacepope Wrote: ------------------------------------------------------- > I am trying to use the shv rootfs and it seems to > work fine with wired but I am having issues > getting the wireless to work. I followed the > hints in the post he linked over at the > archlinuxarm.org site: I copied over the RT2860 > from the pogoplug side, installed wireless-tools > and

by bodhi - uBoot

Re: Linux kernel 3.2.28 Kirkwood package - 12 years ago

@shv, I have consolidate patch that I can post here later, so you can try building your own kernel.

by bodhi - Debian

[Pogoplug Mobile/Series 4] Install uBoot/Debian - 12 years ago

Notice: this thread is now obsolete! Please use the new U-boot and Debian rootfs/kernel threads. Background: The installation starting point should be one of these 3 environments: 1. From inside Pogo OS with a brand new, unhacked Pogo Mobile/Series4. SSH into Pogo OS and start from there. 2. From Arch Linux command line. 3. From Debian command line. To install, you must have NAND

by bodhi - Debian

Re: Debian/uBoot installation for pogoplug mobile? - 12 years ago

Twinclouds, I've documented it here: http://forum.doozan.com/read.php?3,7477,10982#msg-10982 Perhaps it should be on a separate thread.

by bodhi - Debian

Re: [Pogoplug] Booting with multiple USB devices plugged in - 12 years ago

Perhaps this thread will give you some ideas to get around this problem: http://forum.doozan.com/read.php?3,10966

by bodhi - uBoot

Re: [Pogoplug] Booting with multiple USB devices plugged in - 12 years ago

bodhi Wrote: ------------------------------------------------------- > > Yes, the 3TB drives tend to cause problem booting. > Is the Ext3 formatted as whole GPT partition? If > it is then it's best to plug it in later, because > even though you don't have rootfs on it, I suspect > it still causes problem because uBoot must have > tried to scan it (current u

by bodhi - uBoot

Re: Hello, pbs with Uboot/Nand... :( - 12 years ago

To trouble shoot netconsole problem, boot into the Rescue system, and run fw_printenv Pls post the output here.

by bodhi - uBoot

Re: [Pogoplug] Booting with multiple USB devices plugged in - 12 years ago

Sure, you can the boot order for any these parts, except reset is independent so it should be last.

by bodhi - uBoot

Re: [Pogoplug] Booting with multiple USB devices plugged in - 12 years ago

Looks like it got worse?! do you see this if booting with only the thumb drive? Device nand0 not found! Error initializing mtdparts! Yes, the 3TB drives tend to cause problem booting. Is the Ext3 formatted as whole GPT partition? If it is then it's best to plug it in later, because even though you don't have rootfs on it, I suspect it still causes problem because uBoot must have

by bodhi - uBoot

Re: [Pogoplug] Booting with multiple USB devices plugged in - 12 years ago

If you don't care about rescue system, a quick fix would be: boot with only the system thumb drive, and then at Linux com mandline, change this bootcmd=usb start; run force_rescue_bootcmd; run ubifs_bootcmd; run usb_bootcmd; usb stop; run rescue_bootcmd; run pogo_bootcmd; reset to bootcmd=usb start; run ubifs_bootcmd; run usb_bootcmd; usb stop; run rescue_bootcmd; run pogo_bootcmd;

by bodhi - uBoot

Re: Linux kernel 3.2.28 Kirkwood package - 12 years ago

lincomatic Wrote: ------------------------------------------------------- > OK, great. But just for reference, what's the > proper arcNumber for Pogo E02? > I tried 2097 and also 3542 as recommended here: > http://archlinuxarm.org/forum/viewtopic.php?t=2780 > > and it /proc/cpuinfo still shows it as Marvell > SheevaPlug Reference Board. Using current uBoot,

by bodhi - Debian

Re: Linux kernel 3.2.28 Kirkwood package - 12 years ago

For the Pogo E02, it's really not much! LEDs settings are the thing that's extra from 2097. For other plugs, a lot more to gain when you use appropriate kernel. For example, Goflex Net has 2 SATA connectors, and whole bunch of LEDs that can be lighted in various ways. If you're happy with the way the LED work now, then there's no needs to change arcNumber. Much more gain to

by bodhi - Debian

Re: Linux kernel 3.2.28 Kirkwood package - 12 years ago

Cool! yes, I think /sys/class/leds/plug:red:misc was just a remnant of the old patch for machine 2097, where you would mix green and red to get orange. And blue now is actually orange in Pogo E02 :) If everything is working correctly for your Pogoplug E02, cat /proc/cpuinfo also will identfy the hardware as Pogoplug E02.

by bodhi - Debian

Re: Linux kernel 3.2.28 Kirkwood package - 12 years ago

That's normal, since the kernel is not named 3.2.28-kirkwood, the uImage and uInitrd are not generated automatically by dpkg (through flash-kernel). The naming is intentional so that it can be recognized as a patched kernel, not a vanilla kernel from mainline. And also the uImage and uInitrd will not be overwritten automatically by flash-kernel without manual action. I'd suggest sav

by bodhi - Debian

Re: Pogoplug E02 information sought ... - 12 years ago

I've reuploaded it to Dropbox.

by bodhi - Debian

Re: Pogoplug E02 information sought ... - 12 years ago

@lincomatic, I will reupload it to Dropbox instead. But it will take awhile, I have a very slow uplink :)

by bodhi - Debian

Re: Pogoplug E02 information sought ... - 12 years ago

lincomatic Wrote: ------------------------------------------------------- > bodhi, > > I tried > > "echo default-on > > /sys/class/leds/plug:green:health/trigger" > (I added the trigger part) > > to turn on the green LED and nothing happens on > mine. Can you point me to where to download your > kernel? > Thanks I've uploa

by bodhi - Debian

Re: uboot installs, but not environment. should my script mod work in theory? - 12 years ago

What you can do is trying the command setenv in serial console to set ethaddr . See if it does retain so you can boot into the kernel with the correct env. If it does I will find the env loading tool ( somebody has posted that here, but I could not remember where).

by bodhi - uBoot

Re: uboot installs, but not environment. should my script mod work in theory? - 12 years ago

Hey chackoc, congrat :) please edit your post to note that the procedure did work as intended, so will benefit others looking for solution. As for your MAC address, you'll need to set the env for ethaddr. And for LED, look in /sys/class/leds to see the trigger for green, orange... LEDs

by bodhi - uBoot

Re: [Pogoplug Series 4] Booting Debian with Arch Linux ARM uBoot - 12 years ago

See 3.2.28 kernel package in this post: http://forum.doozan.com/read.php?2,11601 The patch I used to build was partly from Vlad, and I found that I had to change some files to be able to build. So I don't have a consolidated patch yet.

by bodhi - uBoot

Linux kernel 3.2.28 Kirkwood package - 12 years ago

I have uploaded a Debian kernel deb package for 3.2.28-kirkwood which I've built with a collection of patches for GoFlex Home/Net, Pogoplug E02/V4, iConnect (Dockstar, Sheevaplug and a few other Kirkwood plugs are already in the mainline 3.2.x). Dropbox: linux-3.2.28-kirkwood-bodhi.tar.bz2 MD5: 68405b35c38bf9a1522bf63b4c7d5e5c Note on extracting: I had a typo on the file name (duh!)

by bodhi - Debian

Re: [Pogoplug Series 4] Booting Debian with Arch Linux ARM uBoot - 12 years ago

shv Wrote: ------------------------------------------------------- > Yes, I have a Pogoplug E02. Which Debian kernel version are you running on the Pogo E02? can you verify whether it has the Pogo V4 patch?

by bodhi - uBoot

Re: [Pogoplug Series 4] Booting Debian with Arch Linux ARM uBoot - 12 years ago

My appology. You're right, I assumed that this rootfs' kernel has Pogoplug E02 and V4 patch. Apparently Davy did not include these patches in this kernel. I took a peek at the config file in his dropbox: https://www.dropbox.com/sh/nwt2kbvetvgvroo/aTWj8GQj0H/Kirkwood/rootfs_images/NSA320quickstart/config-3.3.2-kirkwood-dg Perhaps Davy has this rootfs at a different location other tha

by bodhi - uBoot

Re: [Pogoplug Series 4] Booting Debian with Arch Linux ARM uBoot - 12 years ago

arcNumber 3906 in hex is 0xF78 In Debian command line: fw_setenv machid F78 In uBoot serial/net console: setenv machid F78 If you set machid in uBoot console, don't save the env. Let it boot into Debian sucessfully, and then do "fw_setenv machid F78" at Debian command line.

by bodhi - uBoot

Re: U-Boot w/ MMC/SD-card booting for Pogoplug Series 4 - 12 years ago

I am not sure what you're trying to do? are you booting with Davy's uBoot? To boot back to the PogoV4 stock OS, Arch Linux ARM's uBoot has these envs set up to boot back to stock: load_nand=nboot 0x800000 0 0x200000 load_nand2=nboot 0x800000 0 0x500000 boot=bootm 0x800000 boot_nand=run load_nand boot || run load_nand2 boot mtdparts=mtdparts=orion_nand:2M(u-boot),3M(uImag

by bodhi - uBoot

Re: [Pogoplug] Booting with multiple USB devices plugged in - 12 years ago

See this: http://forum.doozan.com/read.php?3,8044,8152#msg-8152

by bodhi - uBoot