• Home
  • Help
  • Search
  • Login
  • Register
  Show Posts
Pages: [1]
1  Linux Stuff / Kernel / Re: GuruPlug Server Plus and 2.6.35 on: August 23, 2010, 12:55:49 PM
Yes, you can use mainline/vanilla kernels -- but you either need to upgrade to vanilla u-boot, too, or you need to play with the arcNumber uboot setting to get those kernels to boot.

btw, I have fixed the nand problem; the patch will be in one of the next 2.6.35.y kernels and it already is in 2.6.36-rc2.
2  Linux Stuff / Kernel / Re: GuruPlug Server Plus and 2.6.35 on: August 16, 2010, 03:25:07 PM
Apparently the bad block detection code is busted in 2.6.35.
Quite some fixes have landed for that since 2.6.35 was released:

I haven't tried them all yet, and I don't know yet whether the tip of linux-2.6.git does work for the GuruPlug's NAND chip again.
3  Linux Stuff / Kernel / GuruPlug Server Plus and 2.6.35 on: August 14, 2010, 05:37:22 AM
I'm getting the following kernel messages when booting 2.6.35 on my GuruPlug Server Plus (see below).
Anyone know what's up with that? The machine's flash seems just fine -- I think if the first 128 erase blocks were b0rked for real uboot wouldn't work as nicely as it does?

Scanning device for bad blocks
Bad eraseblock 0 at 0x000000000000
Bad eraseblock 1 at 0x000000400000
Bad eraseblock 3 at 0x000000c00000
Bad eraseblock 4 at 0x000001000000
Bad eraseblock 5 at 0x000001400000
Bad eraseblock 6 at 0x000001800000
Bad eraseblock 7 at 0x000001c00000
Bad eraseblock 8 at 0x000002000000
Bad eraseblock 9 at 0x000002400000
Bad eraseblock 10 at 0x000002800000
Bad eraseblock 11 at 0x000002c00000
Bad eraseblock 12 at 0x000003000000
Bad eraseblock 13 at 0x000003400000
Bad eraseblock 14 at 0x000003800000
Bad eraseblock 15 at 0x000003c00000
Bad eraseblock 16 at 0x000004000000
Bad eraseblock 17 at 0x000004400000
Bad eraseblock 18 at 0x000004800000
Bad eraseblock 19 at 0x000004c00000
Bad eraseblock 20 at 0x000005000000
Bad eraseblock 21 at 0x000005400000
Bad eraseblock 22 at 0x000005800000
Bad eraseblock 23 at 0x000005c00000
Bad eraseblock 24 at 0x000006000000
Bad eraseblock 25 at 0x000006400000
Bad eraseblock 26 at 0x000006800000
Bad eraseblock 27 at 0x000006c00000
Bad eraseblock 28 at 0x000007000000
Bad eraseblock 29 at 0x000007400000
Bad eraseblock 30 at 0x000007800000
Bad eraseblock 31 at 0x000007c00000
Bad eraseblock 32 at 0x000008000000
Bad eraseblock 33 at 0x000008400000
Bad eraseblock 34 at 0x000008800000
Bad eraseblock 35 at 0x000008c00000
Bad eraseblock 36 at 0x000009000000
Bad eraseblock 37 at 0x000009400000
Bad eraseblock 38 at 0x000009800000
Bad eraseblock 39 at 0x000009c00000
Bad eraseblock 40 at 0x00000a000000
Bad eraseblock 41 at 0x00000a400000
Bad eraseblock 42 at 0x00000a800000
Bad eraseblock 43 at 0x00000ac00000
Bad eraseblock 44 at 0x00000b000000
Bad eraseblock 45 at 0x00000b400000
Bad eraseblock 46 at 0x00000b800000
Bad eraseblock 47 at 0x00000bc00000
Bad eraseblock 48 at 0x00000c000000
Bad eraseblock 49 at 0x00000c400000
Bad eraseblock 50 at 0x00000c800000
Bad eraseblock 51 at 0x00000cc00000
Bad eraseblock 52 at 0x00000d000000
Bad eraseblock 53 at 0x00000d400000
Bad eraseblock 54 at 0x00000d800000
Bad eraseblock 55 at 0x00000dc00000
Bad eraseblock 56 at 0x00000e000000
Bad eraseblock 57 at 0x00000e400000
Bad eraseblock 58 at 0x00000e800000
Bad eraseblock 59 at 0x00000ec00000
Bad eraseblock 60 at 0x00000f000000
Bad eraseblock 61 at 0x00000f400000
Bad eraseblock 62 at 0x00000f800000
Bad eraseblock 63 at 0x00000fc00000
Bad eraseblock 64 at 0x000010000000
Bad eraseblock 65 at 0x000010400000
Bad eraseblock 66 at 0x000010800000
Bad eraseblock 67 at 0x000010c00000
Bad eraseblock 68 at 0x000011000000
Bad eraseblock 69 at 0x000011400000
Bad eraseblock 70 at 0x000011800000
Bad eraseblock 71 at 0x000011c00000
Bad eraseblock 72 at 0x000012000000
Bad eraseblock 73 at 0x000012400000
Bad eraseblock 74 at 0x000012800000
Bad eraseblock 75 at 0x000012c00000
Bad eraseblock 76 at 0x000013000000
Bad eraseblock 77 at 0x000013400000
Bad eraseblock 78 at 0x000013800000
Bad eraseblock 79 at 0x000013c00000
Bad eraseblock 80 at 0x000014000000
Bad eraseblock 81 at 0x000014400000
Bad eraseblock 82 at 0x000014800000
Bad eraseblock 83 at 0x000014c00000
Bad eraseblock 84 at 0x000015000000
Bad eraseblock 85 at 0x000015400000
Bad eraseblock 86 at 0x000015800000
Bad eraseblock 87 at 0x000015c00000
Bad eraseblock 88 at 0x000016000000
Bad eraseblock 89 at 0x000016400000
Bad eraseblock 90 at 0x000016800000
Bad eraseblock 91 at 0x000016c00000
Bad eraseblock 92 at 0x000017000000
Bad eraseblock 93 at 0x000017400000
Bad eraseblock 94 at 0x000017800000
Bad eraseblock 95 at 0x000017c00000
Bad eraseblock 96 at 0x000018000000
Bad eraseblock 97 at 0x000018400000
Bad eraseblock 98 at 0x000018800000
Bad eraseblock 99 at 0x000018c00000
Bad eraseblock 100 at 0x000019000000
Bad eraseblock 101 at 0x000019400000
Bad eraseblock 102 at 0x000019800000
Bad eraseblock 103 at 0x000019c00000
Bad eraseblock 104 at 0x00001a000000
Bad eraseblock 105 at 0x00001a400000
Bad eraseblock 106 at 0x00001a800000
Bad eraseblock 107 at 0x00001ac00000
Bad eraseblock 108 at 0x00001b000000
Bad eraseblock 109 at 0x00001b400000
Bad eraseblock 110 at 0x00001b800000
Bad eraseblock 111 at 0x00001bc00000
Bad eraseblock 112 at 0x00001c000000
Bad eraseblock 113 at 0x00001c400000
Bad eraseblock 114 at 0x00001c800000
Bad eraseblock 115 at 0x00001cc00000
Bad eraseblock 116 at 0x00001d000000
Bad eraseblock 117 at 0x00001d400000
Bad eraseblock 118 at 0x00001d800000
Bad eraseblock 119 at 0x00001dc00000
Bad eraseblock 120 at 0x00001e000000
Bad eraseblock 121 at 0x00001e400000
Bad eraseblock 122 at 0x00001e800000
Bad eraseblock 123 at 0x00001ec00000
Bad eraseblock 124 at 0x00001f000000
Bad eraseblock 125 at 0x00001f400000
Bad eraseblock 126 at 0x00001f800000
Bad eraseblock 127 at 0x00001fc00000
Creating 3 MTD partitions on "orion_nand":
0x000000000000-0x000000100000 : "u-boot"
mtd: partition "u-boot" doesn't end on an erase block -- force read-only
Moving partition 1: 0x000000100000 -> 0x000000400000
0x000000400000-0x000000800000 : "uImage"
0x000000800000-0x000020000000 : "root"
4  Hardware and U-Boot firmware / Hardware / Re: GuruPlug Server Plus Heat Problems on: May 27, 2010, 12:42:26 PM
I assumed the ridiculously short warranty (I'm European :p) was an US thing Smiley

Just because you live in the EU and enjoy the 2 year warranty (which btw only works as long as your supplier hasn't gone bankrupt) doesn't make it a better product.  30 days clearly shows that it's a piece of junk. If it weren't the company would be offering a longer warranty, 30 days is not a typical warranty in the US for computer (components).

I meant: I assumed it was customary to only give 30 days warranties in the US. I know the product isn't getting better because my reseller's warranty is longer.

I don't think the GuruPlug is garbage, but at this point I really think GST should publish a statement re. the issues with the device. The silence on their part is what annoys me Sad

How is this not garbage?  I highly doubt they even tested the thing for more than 5 minutes.  Is this what you would call quality assurance?  If they had 20 or 30 plugs running at 100% cpu for a month without any failure before they start selling them, that I would call a decent test.  But these things can't even handle idling...

Well, it seems like a neat product, at least _concept_ wise Wink

Also, why should they publish a statement?

To show that they do give a crap about their customers!

FWIW, I opened up my GuruPlug today and I'm probably going to switch the internal PSU for an external one...
5  Hardware and U-Boot firmware / Hardware / Re: GuruPlug Server Plus Heat Problems on: May 26, 2010, 01:27:20 PM
This company does NOT stand behind their products because they only provide a 30 day warranty (which is a joke).

I assumed the ridiculously short warranty (I'm European :p) was an US thing Smiley

If I were you, I would NOT buy anything from Globalscales.  It just encourages them to keep doing this crap, ripping people off their money and providing nothing but garbage.

I don't think the GuruPlug is garbage, but at this point I really think GST should publish a statement re. the issues with the device. The silence on their part is what annoys me Sad
6  Linux Stuff / Kernel / Re: Cannot tftp-boot custom kernel, but only factory default kernel on: May 22, 2010, 02:46:54 PM
Yeah, I wasn't sure whether my problem was the same as the one begin discussed in that other thread.
I agree that it probably is though Smiley
7  Linux Stuff / Kernel / Re: Cannot tftp-boot custom kernel, but only factory default kernel on: May 22, 2010, 06:37:12 AM
From having another look at u-boot (the one the guruplug shipped with!), I got this:

Marvell>> bdinfo                                                               
arch_number = 0x00000A29

I guess that means that u-boot is expecting a kernel that was compiled for architecture 0xa29 (2601).
In the posted kernel tree (and in mainline now), the GuruPlug was assigned ID 2659.

Should this mismatched have been worked around by "setenv arcNumber 2659" before booting?

To hack around the problem, I edited include/generated/mach-types.h and swapped the entries for 2659 and 2601.
That gave me an uImage I can boot Smiley
8  Linux Stuff / Kernel / Cannot tftp-boot custom kernel, but only factory default kernel on: May 21, 2010, 05:40:07 PM
my goal is to eventually replace kernel and rootfs of my GuruPlug.

I started with what seemed to be the the easiest step: building a (not so) custom kernel.

So, I got the kernel sources from the GuruPlug download area at this site (http://plugcomputer.org/index.php/us/resources/downloads?func=fileinfo&id=75). Next I copied /proc/config.gz from the plug to my workstation and rebuilt the kernel:
$ make ARCH=arm CROSS_COMPILE=arm-unknown-linux-gnueabi- uImage

The resulting uImage should be the same as the same the GuruPlug was shipped with.

However, I cannot boot my build via tftp:

> setenv ipaddr
> setenv serverip
> setenv arcNumber 2659
    I got this from grepping GURUPLUG arch/arm/tools/mach-types
> setenv mainlineLinux yes
> tftpboot 0x2000000 uImage-mine
> setenv bootargs console=ttyS0,115200 root=dev/ram rw
> bootm 0x2000000

u-boot tells me:
Uncompressing kernel... done, booting kernel.

Afterwards I get no more output.

This posting (http://plugcomputer.org/plugforum/index.php?topic=1547.msg10065#msg10065) suggests that u-boot may be incompatible with mainline kernels, BUT:
* I grabbed the kernel code from this very website
* the patch from to the kernel tree posted there doesn't show any diverging architecture numbers

The u-boot environment that the GuruPlug comes up doesn't contain the arcNumber setting.

Interestingly, the kernel tree posted here is not the same as the one that was used to build the uImage that GuruPlug is shipped with.
So extra question: where do I get the kernel tree that corresponds to the build on the plug?

Hints please? I guess I could try flashing u-boot, but I'd rather not Grin

(FWIW, the kernel config that was posted along with the kernel tree looks sane. I enabled the GuruPlug-specific setup code, there's serial drivers enabled etc.)

Pages: [1]