@ Lewy1, everything up above looks normal to me. The only errors that I see in the messages are expected ones, triggered by the uboot not finding a recovery script token, for instance. Btw, what is your usb_rootfstype? Ext2 or Ext3? Are you using a flash drive, or a USB<->SATA adapter w/ an actual HDD?by davygravy - uBoot
I don't have any familiarity w/ PirateBox, but I can tell you that it is booting correctly, at least up until line 140 or even 148. After that it looks like there is some sort of permissions problem. Does PirateBox require special permissions to run on Debian? (note all of those statements after 148 about "only root can do that". I'd try googling "debian pirateboxby davygravy - uBoot
docbee Wrote: ------------------------------------------------------- > Great progress! I would love to give it a try on > my pogo V4 as well. Before bricking it by > installing the wrong uboot I would like to ask if > the uboot linked above > "u-boot_032012_pogoplugE02-debian" does have the > SD/MMC boot features needed in V4/mobile inside? > Or do you refeby davygravy - Debian
At this point, I'm unable to solve the SATA problem. I can get it to initialize the SATA port correctly. It recognizes the drive, but complains about an IRQ error: U-Boot 2012.04-rc1-dirty (Apr 08 2012 - 16:10:53) Cloud Engines-Pogoplug v4 SoC: Kirkwood 88F6281_A1 DRAM: 128 MiB WARNING: Caches not enabled NAND: 128 MiB *** Warning - bad CRC, using default environment In:by davygravy - uBoot
There are two way of doing this. One is with a UART uboot. It requires wiki.scottn.us/goflex:uartboot. This will work on the GoFlex net. The other is chainloading a regular uboot kwb file, tftp-ing it into memory, and the executing it. It is not reliable in many cases.by davygravy - Debian
Currently it does _not_ allow one to boot back into the Pogoplug software.by davygravy - uBoot
laprjns Wrote: ------------------------------------------------------- > That's embarrassing. hehehe, doesn't matter! > tftpboot 0x800000 > uboot.mtd0.kwb-pogo_e02-DGL2CDisabled > Using egiga0 device > TFTP from server 192.168.1.75; our IP address is > 192.168.1.161 > Filename 'uboot.mtd0.kwb-pogo_e02-DGL2CDisabled'. > Load address: 0x800000by davygravy - uBoot
Well, its a tar.gz file. Just untar it and then try. I put that bit in the directions, so that if anyone missed the directions about untarring it, they'd still catch that bit on the length comparison. ----------------- I'll go back and bold that chunk... I do get it, it can be easy for someone to miss.by davygravy - uBoot
I've been booting 3.3-rcN for a few months now... it boots fine if you have a u-boot that can deal w/ the new kernel L2-cache configuration, or you can configure the kernel differently and boot w/ the older u-boots.by davygravy - Debian
Thank you, baafie! Great catch. I'm mid-stride in a u-boot problem, but eventually I'll roll a kernel 3.3 kernel .deb package for my boxes, and I'll make sure to apply your patch.by davygravy - Debian
baafie Wrote: ------------------------------------------------------- > YES! Yes!!!!!!!!!! Indeed! You found what no one else had been able to see... > The issue appears to be caused by the driver. > > Long story short: given that uBoot was working > fine for most people (at least as far as booting), > I suspected there must be some difference between > uBoot andby davygravy - Debian
Works great w/ the Mainline Debian Netboot installer... and the following booting commands in u-boot's env vars: setenv bootargs_console console=ttyS0,115200 setenv bootcmd_mmc 'mmc init; ext2load mmc 0:1 0x00800000 /uImage; ext2load mmc 0:1 0x01100000 /uInitrd' setenv bootcmd 'setenv bootargs $(bootargs_console); run bootcmd_mmc; bootm 0x00800000 0x01100000' saveeby davygravy - uBoot
This concept works on the Pogoplug V4 also, using the new u-boot that I created for it that enables MMC/SD cards in u-boot. This same u-boot should probably work on a Pogoplug Mobile. Don't attempt to use the u-boot for the PogoE02... instead, you'd have to use the u-boot mentioned here http://forum.doozan.com/read.php?3,7477,7477#msg-7477 , and have serial access - I don't haby davygravy - Debian
I have an TTL-232R-3V3 http://www.google.com/products/catalog?client=ubuntu&channel=fs&q=TTL-232R-3V3&oe=utf-8&um=1&ie=UTF-8&tbm=shop&cid=306274749503843287&sa=X&ei=t_J1T9KeO9GXtwe5ypTXDg&ved=0CGcQ8wIwAw I'm not sure which cable you have... I don't think the 5V works correctly. You do need to be careful w/ the serial connection. If the circby davygravy - uBoot
Booting from both USB2 (top port) and MMC card are both possible now. U-Boot 2011.12 (Mar 30 2012 - 11:49:20) Pogo v4 SoC: Kirkwood 88F6281_A1 DRAM: 128 MiB WARNING: Caches not enabled NAND: 128 MiB In: serial Out: serial Err: serial Net: egiga0 Hit any key to stop autoboot: 0 Pogov4> usb start (Re)start USB... USB: Register 10011 NbrPorts 1 USB EHCI 1.00 sby davygravy - uBoot
You should not need JTAG, since this device supports UART booting. About the garbled unreadable characters in serial console: are you _sure_ you have serial connected correctly? Did you have _serial_ working before this correctly? (it is clear from what you said that _net_console was working before for you)by davygravy - uBoot
STOP: Don't flash unless you have serial/UART connection and understand the risks and how to recover. STATUS : What works: USB2 (topside) and MMC/SD Card slot both work for booting and once booted into Linux USB3 works once booted into Linux Not working: SATA - currently works in neither U-Boot nor in Linux (if you need SATA booting or access, try the U-Boot from ArchLinuxArm0 Doby davygravy - uBoot
I notice it says "2048+64 bytes". I'm not very familiar w/ this sort of memory spec thing... I'm wondering if the 64 bytes is used for something else. Anybody? (I _am_ interested in solving this, but I'm mid-stride in getting GoFlex Net supported in U-Boot mainline right now. ... maybe someone stumbling over this discussion will chime in w/ the definitive answer...)by davygravy - Debian
While booted in Linux it will be the same from ssh, telnet or serial console. The difference is that you can interact with the bootloader (uboot) and change variables there without seeing that error. Knock on wood. I've never seen the problem from the uboot side. It might still show up here or there... It is also possible that a subpage problem is what is causing the chained originalby davygravy - Debian
I'm wondering if it is a question of maker of the NAND. Baffie, what does dmesg tell you that your NAND is, in terms of a brand or manufacturer? ============== This looks like what we see, exactly. http://wiki.beyondlogic.org/index.php/Seagate_FreeAgent_GoFlex_Home_MTDTests_Toshiba_TC58NVG1S3ETA00 Also http://www.mail-archive.com/linuxkernelnewbies@googlegroups.com/msg00559.htby davygravy - Debian
are you sure you are actually booting debian, or are you booting just the pogo stockware right now? uname -r will tell you... 2.6.20-ish will be pogo, 2.6.32-ish or higher will prolly be Debian...by davygravy - uBoot
hmmm... I'm not sure what the docs say... that arcNumber value looks correct to me, but personally, I use a arcNumber value of 2678, since that is the one for Sheevaplug eSATA (closest thing to GoFlex in mainline linux), but if the docs say 3089 and you are using a GoFlex kernel, then I guess follow the docs. (the replacement uboot for the current ones will have 2678 as the default fall-bby davygravy - Debian
It seems odd to me that so many of us are seeing the annoying Too few good blocks within range error... I find it interesting that flashing within U-Boot is perfectly/completely successful for me on the same machine that throws up this error. Is it possible that there is some other problem, something wrong (in kernel) with a setting for a chip, or some bit value is set incorrectly somewheby davygravy - Debian
Well, I didn't solder. The header pins are already populated. You just need to attach the leads to the 3 pins.by davygravy - Debian
Yes, I've got the same problem w/ mine - the flash is a weak batch from the supplier... I had to turn on netconsole w/ a console/serial cable. :^\by davygravy - Debian
Yup, doing it right now. Just read the direction carefully through before you actually do it, making sure you understand each step in advance. Then actually try the process, if you are at all new to it. (...just my suggestion...)by davygravy - Debian
Well, the short end of a long story is that u-boot for kirkwood had never been conscious of disabling the Level 2 Cache at boot time. On the other hand, Linux now assumes that to be the case. The reason things wouldn't get passed the decompressing stage is that the processor would hang, because u-boot never disabled the L2C... (... can't everyone please just let's get along witby davygravy - uBoot
@ pazos: are you planning to submit this to mainline ever?by davygravy - Debian
Hopefully it will all be purely drop in replacement, using Jeffs already-proven scripts. Still a tad of testing to do. :)by davygravy - uBoot
Yes, you'll have to read the forum threads that document how to do it. Google doozan SATA boot goflex net, for starters. Did you actually clone the USB rootfs and other partitions to the SATA drive already? Did you enable and set up netconsole already?by davygravy - Debian