• Home
  • Help
  • Search
  • Login
  • Register
  Show Posts
Pages: [1] 2 3
1  Hardware and U-Boot firmware / U-Boot stuff / Re: D2Plug - reinstall u-boot on bricked device on: November 27, 2012, 12:38:56 AM
Bit of a gravedig, but....

I think I'm in a similar situation here.  I just got a Mirabox from Globalscale, and managed in a couple of hours to screw up u-boot by carelessness after months of hacking on GuruPlugs.  Documentation on this thing (both official and otherwise) is basically nonexistent since it just came out, and nothing I've tried has brought u-boot back to life (stuck in a loop of "BootROM: Bad header at offset 00B00000 ..." counting the address space).

I think (but am not 100% sure) that the Mirabox is closer to the d2plug than the GuruPlug (which I have plenty of experience with, as mentioned above), so it seems that there's basically no way at present to restore u-boot?
2  Linux Stuff / Kernel / Re: sheevaplug USB mount fails periodically (debian) on: July 01, 2011, 12:35:00 PM
FYI, all the hard drives I've plugged into my plug were on external power, so power from the USB bus was never the issue in my case.  I swapped out the hard drive into a new USB enclosure and that seemed to fix the problem -- don't think I've seen it in the past couple of months.
3  Hardware and U-Boot firmware / U-Boot stuff / Re: One good uniform way to install a guru/sheeva wanted on: March 10, 2011, 05:32:59 PM
Actually, I'm thinking that it may be a problem with the uImage load address (0x400000 in my above uboot env) -- I think this may overlap with what u-boot uses itself, and so sometimes causes a problem.  I changed my load address (both occurrences) to 0x800000 and I haven't seen the error since, although I haven't rebooted that many times since I changed it.
4  Hardware and U-Boot firmware / U-Boot stuff / Re: One good uniform way to install a guru/sheeva wanted on: March 05, 2011, 08:27:53 AM
Has anyone actually figured out what causes the problem where u-boot gets to "Done, booting the kernel" and then hangs?  I didn't use the installer or any OpenOCD stuff, but I still get this message about 30% of the time.  The other 70% of the time, the plug boots normally (without having changed anything, same kernel, u-boot version and u-boot parameters).  I'm booting off a microSD card using flipflip's u-boot, with the following relevant u-boot vars:

Code:
setenv bootargs_console 'console=ttyS0,115200n8'
setenv bootargs_root 'root=/dev/sda2 rootwait ro'
setenv bootcmd_usb 'usb start; ext2load usb 0:1 0x400000 /uImage'
setenv bootcmd 'setenv bootargs $(bootargs_console) $(bootargs_root); run bootcmd_usb; bootm 0x400000'
saveenv
5  Linux Stuff / Kernel / Re: Where can I download uap8xxx.ko? on: February 26, 2011, 05:45:37 AM
Damn it!
I've flashed kernel 2.6.36.4 from sheeva.with-linux.com and now got:
Code:
Uncompressing Linux... done, booting the kernel.
That's all. System doesn't boot at all now.
I've gotten this issue from time to time, and one or two simple reboots fixed it (as in, I just tried once or twice more without changing anything and it got past that point).  I haven't been able to identify what makes it occur or not occur.
6  Hardware and U-Boot firmware / U-Boot stuff / Re: One good uniform way to install a guru/sheeva wanted on: February 22, 2011, 02:42:49 PM
Are you using the built-in SD slot on the GuruPlug Server Plus or a USB adapter on a standard GuruPlug?  The latter is what I'm most familiar with.  If that's what you're doing, is your card recognized by u-boot?  Run 'usb start' in u-boot and see if the device is recognized at all -- I've found that u-boot can be finicky about what devices it recognizes, and have had both readers and cards that worked fine in my computer but could not be read by u-boot.
7  Linux Stuff / Kernel / GuruPlug wifi client setup on: February 22, 2011, 04:56:43 AM
There's a lot of stuff out there on configuring the GuruPlug as a wifi client, but most of it is either pretty involved or kind of hacked (throwing random commands in rc.local and the like).  I wrote up a tutorial (http://blog.zortrium.net/archives/67) on getting client mode working reliably and cleanly (through the regular /etc/network/interfaces file) that shouldn't take more than about 5 minutes to follow.  I'm posting it here for anyone to use and also for any feedback on good client setups people have.
8  Hardware and U-Boot firmware / U-Boot stuff / Re: One good uniform way to install a guru/sheeva wanted on: February 21, 2011, 03:52:42 PM
I've deployed about 15 Sheeva/GuruPlugs so far, so I've messed around with my share of bootloaders.  As far as booting from SD cards is concerned (which, generally speaking, is the best approach):

For the SheevaPlug, use uboot 3.4.27 with Pingtoo's patch (linked here from the forums). This version is rock-solid for booting from SD cards and has worked flawlessly for me. The uboot version command should output this:

U-Boot 1.1.4 (Dec 27 2009 - 22:03:21) Marvell version: 3.4.27 - pingtoo patch.01

For the GuruPlug, use the custom uboot linked from the previous post.  I am currently using this version to boot from a MicroSDHC card, plugged into my GuruPlug via a USB adapter.  The uboot version command should output this:

U-Boot 2010.09-02612-g27fb783-dirty (Nov 11 2010 - 22:51:37)
Marvell-GuruPlug (-: flipflip's version 20101111 :-)

Both these bootloaders are capable of booting ext2/ext3 partitions.  I can provide any further details if you require.
9  Hardware and U-Boot firmware / U-Boot stuff / Re: Problem with Booting the kenel from a spinning USB disk on: February 17, 2011, 12:57:39 PM
The HD spin up issues crop up even when the HD is connected directly, but can be (sort of) worked around -- the USB hub is the issue that, to my knowledge, hasn't been worked around.  I was booting my plug off a USB HD for awhile (both kernel and root partition), and it worked mostly, but occasionally the spin-up issue would cause it to fail at boot and I'd have to use the serial console to kick it back into booting.  I've since switched to an SD card.
10  Hardware and U-Boot firmware / Hardware / Re: Firmware CRC load error when loading upa or wlan firmware on: January 10, 2011, 12:23:46 AM
Nevermind -- it looks like puterboy already came up with a workaround, but posted it in another thread (http://plugcomputer.org/plugforum/index.php?topic=4330.0).  In my case, the underlying issue was that I left the two relevant firmware files (helper_sd.bin and sd8688.bin) in /lib/firmware/mrvl, and when the plug reboots, it automatically tries to access them during bootup and the wifi gets screwed up.

My ugly but apparently functional solution is to put the firmware files into /lib/firmware/mrvl, switch from AP to client mode, then immediately DELETE the files out of /lib/firmware/mrvl so they're not there on the next reboot.  For completeness, here's the boot-time wifi setup script I'm using:

Code:
#!/bin/sh

# GuruPlug wireless client setup script

# Copy the firmware files to where they're expected
cp /root/firmware/helper_sd.bin /lib/firmware/mrvl/
cp /root/firmware/sd8688.bin /lib/firmware/mrvl/

# Deactivate access point functionality
rmmod uap8xxx

# Activate the wireless modules
insmod /root/wifi/mcypt.ko
insmod /root/wifi/sd8xxx.ko

# Delete the firmware files - wifi get screwed up if
# they're there when the plug reboots
rm /lib/firmware/mrvl/helper_sd.bin
rm /lib/firmware/mrvl/sd8688.bin

# Activate the wifi client
wpa_supplicant -i mlan0 -c /root/wifi.conf -B

# Bring up the interface
ifconfig mlan0 up

# For a dynamic IP
dhclient mlan0

# For a static IP
#ifconfig mlan0 192.168.1.150 netmask 255.255.255.0 up
#route add -net 192.168.1.0 netmask 255.255.255.0 mlan0
#route add default gw 192.168.1.1 mlan0

# Set LEDs for client mode
echo 0 > `eval ls /sys/class/leds/*plug*\:green\:wmode/brightness`
echo 1 > `eval ls /sys/class/leds/*plug*\:red\:wmode/brightness`
11  Hardware and U-Boot firmware / Hardware / Re: Firmware CRC load error when loading upa or wlan firmware on: January 10, 2011, 12:05:03 AM
I too am running into this problem when trying to run my GuruPlug as a Wifi client.  I'm using kernel 2.6.33.7 and the newer 'stable' drivers as outlined at http://plugcomputer.org/plugwiki/index.php/Setting_GuruPlug_to_be_a_stable_WiFi_Client.
12  Hardware and U-Boot firmware / U-Boot stuff / Re: guruplug sd card via usb adapter on: January 07, 2011, 02:25:13 PM
Okay, it looks to be an adapter or adapter/sd card combination problem.  I tried two other adapters -- one hung u-boot, but one worked (I'm using the recent custom u-boot) -- the one that worked for me is the Transcend TS-RDS5W (http://www.amazon.com/Transcend-TS-RDS5W-MMC-Card-Reader/dp/B00109XJW6), coupled with a 4 GB Transcend SD card (but I didn't try any other SD cards).
13  Hardware and U-Boot firmware / U-Boot stuff / guruplug sd card via usb adapter on: January 07, 2011, 05:19:32 AM
I'm trying to set up my GuruPlug to boot off an SD card.  Since I don't have the model with the SD card slot, I'm trying to do it via a standard SD to USB adapter.  The thread at http://forums.plugpbx.org/index.php?topic=71.0 implies that this is doable, but I'm not having any luck getting u-boot to recognize the adapter at all.  I've tried the original u-boot, the upgraded Marvell u-boot, and the tricked-out u-boot from http://oinkzwurgl.org/guruplug_uboot, but 'usb start' gives '0 storage devices found' on all of them.  A standard usb thumb drive is recognized no problem.  My adapter works fine when plugged into my computer and the activity light does blink on briefly when running 'usb start', so it shouldn't be a hardware problem.  Is it possible that my particular adapter just doesn't work for some reason, or can anyone think of any other potential problems?
14  Linux Stuff / Kernel / basic GuruPlug questions on: September 09, 2010, 02:06:26 PM
Hi all,

I'm about to get my hands on my first GuruPlug Server.  I've worked extensively with several SheevaPlugs in many configurations (booting from USB, booting from SD card, running custom kernel, etc) so I'm not a plug newbie, but I can't seem to find a general page that succinctly describes the current state of the GuruPlug in terms of distro hackability.  So, clarification to a couple questions for those with GuruPlug experience would be appreciated (or pointers to relevant pages); I'm not really looking for step-by-step instructions at this point, just basic answers.

1. I believe that the GuruPlug cannot, at present, boot a bog-standard Linux distribution as the SheevaPlug can?  E.g., I can't take the SD card running stock Debian that my SheevaPlug boots off of and use it in a GuruPlug.  Furthermore, there are special files in the included distribution that make things like the GuruPlug's wireless work correctly?

2. I've read that the u-boot in the GuruPlug is less capable than the u-boot in the SheevaPlug. Can the GuruPlug u-boot be upgraded or replaced to rectify that?

3. My current understanding of external booting is this -- you CAN mount the GuruPlug root file system from an external drive (either USB or SD), but you CANNOT boot the kernel from an external drive, so the kernel always needs to reside in flash.  For a GuruPlug Server (not the Plus) which doesn't have an SD card slot, can you boot from SD via a USB adapter?  Finally, are there any restrictions on the external drive formatting (e.g., must be formatted as FAT instead of ext2 to be read by u-boot)?

Any pointers appreciated in advance.
15  Linux Stuff / Kernel / Re: sheevaplug USB mount fails periodically (debian) on: September 09, 2010, 01:45:31 PM
Yeah, I think the disk itself (or possibly the enclosure) is going south.  It started crapping out after a period of hours rather than days and at one point failed before it was even done rebooting.  It's sitting on my disk waiting for some trial and error troubleshooting at the moment.
Pages: [1] 2 3