I believe UBIT 0.6 is incompatible with kernels newer than 3.1. You would need to upgrade uBoot to a newer version. Easier (and less risky) is to simply follow the steps documented in this post, which you really ought to have read...by baafie - Debian
I have just booted into the SATA drive using a kernel image downloaded via tftp. I am concluding, then, that there is nothing wrong with any of the bits of hardware involved (SATA disk, mainboard/SATA port, ...). I believe that this is a uBoot issue. I am thinking of trying a more recent uBoot (it is my understanding they can be tested, without permanent NAND writes, from e.g. a tftp source).by baafie - Debian
Having succeeded in gaining access to NAND, I decided to switch to UBIT. This works well for USB, but booting SATA doesn't: U-Boot 2010.09 (Feb 16 2011 - 18:42:02) UBIT v0.6 by Jeff Doozan and Peter Carmichael Reset IDE: Bus 0: not available Bus 1: OK Device 1: Model: <�<�<�<�<�<�<�<�<�<�<�<�<�<�<�<ï¿by baafie - Debian
I think we found the source of the problem here: http://forum.doozan.com/read.php?2,7451,7497#msg-7497 But it would be nice to have confirmation from some other people.by baafie - uBoot
Actually, I got a little wild with being able to write NAND myself, and botched the system as a result. Now, my kernel doesn't get further than [ 23.246858] drivers/rtc/hctosys.c: unable to open rtc device (rtc0) :) Oh, by the way: I heard of people being unable to boot a 3.2 kernel, so I'm curious whether 3.3 works.by baafie - Debian
davygravy Wrote: ------------------------------------------------------- > Yes!!!!!!!!!! Indeed! You found what no one else > had been able to see... Well, let's first see if it solves the problem for you too. > Could you give a pointer to that patch? I don't > know at all which one you are speaking of, and I'd > really like to fix mine, too! It is mby baafie - Debian
YES! 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 and the kernel in the way they interact with the NAND. So I started reading the relevant bits of code in both source trees and found little difference, until I saw that the chip_delay fby baafie - Debian
davygravy Wrote: ------------------------------------------------------- > Compile and create the .deb files for linux-image > and linux-headers > > make-kpkg --rootcmd fakeroot --arch armel > --append-to-version=-kirkwood --revision=1.0 > --initrd kernel_image kernel_headers > ... wait about 2 hours. The trick is to specify --arch; although the documentation spby baafie - Debian
I think it's what the mtd tests refer to as 'OOB', which appears to be the correct size. So it's probably not important. :)by baafie - Debian
Is it important that the output of your mtd tests says the page size is 2048, whereas the data sheet claims it is 2112?by baafie - Debian
davygravy Wrote: ------------------------------------------------------- > 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_Free > Agent_GoFlex_Home_MTDTests_Toshiba_TC58NVG1S3ETA00 Mine is exactly the same.by baafie - Debian
I have been beginning to suspect the same thing. I found this thread (about a different device) to be an interesting read: http://lists.infradead.org/pipermail/linux-mtd/2009-May/025712.html Perhaps something similar is going on here. Would a significantly older kernel help us?by baafie - Debian
I think my question was unclear. On my GoFlex, inside Debian, fw_setenv fails because of "Too few good blocks within range". Why would the result be any different when I execute the same command from the serial console?by baafie - Debian
At any rate: if I connect to the serial console, will I be able to use setenv to enable SATA support? I am assuming setenv arcNumber 3089 is the primary thing I am missing; I already have Varkey's GoFlex kernel running.by baafie - Debian
Running a serial cable means opening the device and soldering, right? Not really my cup of tea. If I could restore the device to factory settings I could send it back to the supplier and get a new one to see if my luck improves.by baafie - Debian
QuoteDid you actually clone the USB rootfs and other partitions to the SATA drive already? Yes. QuoteDid you enable and set up netconsole already? I have tried to follow the instructions from http://forum.doozan.com/read.php?3,14,14 but the first command fails with: Too few good blocks within rangeby baafie - Debian
Hi, using Jeff's modified script (http://dev.shyd.de/dockstar/dockstar.debian-squeeze.sh) I have successfully installed Debian on my drive. It is now booting from USB. However, I would like to connect the drive directly to the SATA port. When I plug it in, though, the device does not boot (blinks briefly green, then orange). Does anyone know how to enable booting from SATA?by baafie - Debian