• Home
  • Help
  • Search
  • Login
  • Register
Pages: [1]
Author Topic: Upgraded U-Boot, now I can't boot anything  (Read 2047 times)
Alucard
Newbie
*

Karma: 0
Posts: 10


View Profile
« on: June 26, 2010, 07:43:58 PM »

Hi,

I've been trying to compile my own kernel so I can enable CONFIG_NETFILTER_XT_MATCH_PHYSDEV for a Shorewall bridge. I only successfully got as far as loading the latest U-Boot from http://plugcomputer.org/index.php/us/resources/downloads?func=select&id=15.  It works fine (U-Boot 2010.03-01161-gd91b0a9 (Apr 22 2010 - 03:24:41)) but now nothing boots.  I have been trying custom kernels following the wiki, but with no luck, and I give up for now.

So, problem #1 is just booting the factory image again.  It's still on flash, though I have an SD card plugged in.

Code:
Marvell>> printenv
bootcmd=${x_bootcmd_usb}; ${x_bootcmd_kernel}; setenv bootargs ${x_bootargs} ${x_bootargs_root}; boo                                                                                                           tm 0x6400000;
bootdelay=3
baudrate=115200
x_bootcmd_usb=usb start
x_bootcmd_kernel=nand read.e 0x6400000 0x100000 0x400000
x_bootargs=console=ttyS0,115200
x_bootargs_root=ubi.mtd=2 root=ubi0:rootfs rootfstype=ubifs
ethaddr=02:50:43:6e:96:26
eth1addr=02:50:43:0c:0c:1f
ethact=egiga0
filesize=285144
fileaddr=6400000
ipaddr=10.0.0.99
serverip=10.0.0.9
stdin=serial
stdout=serial
stderr=serial

Environment size: 491/131068 bytes
Marvell>> saveenv
Saving Environment to NAND...
Erasing Nand...
Erasing at 0x40000 -- 100% complete.
Writing to Nand... done
Marvell>> boot
(Re)start USB...
USB:   Register 10011 NbrPorts 1
USB EHCI 1.00
scanning bus for devices... 3 USB Device(s) found
       scanning bus for storage devices... Device NOT ready
   Request Sense returned 02 3A 00
1 Storage Device(s) found

NAND read: device 0 offset 0x100000, size 0x400000
 4194304 bytes read: OK
## Booting kernel from Legacy Image at 06400000 ...
   Image Name:   Linux-2.6.32-00007-g56678ec
   Image Type:   ARM Linux Kernel Image (uncompressed)
   Data Size:    2789756 Bytes =  2.7 MB
   Load Address: 00008000
   Entry Point:  00008000
   Verifying Checksum ... OK
   Loading Kernel Image ... OK
OK

Starting kernel ...

Uncompressing Linux.................................................................................                                                                                                           ...................................................................................................                                                                                                            done, booting the kernel.


And it just sits there.  As you can see, arcNumber and mainlineLinux are not set.

How do I boot now?  Also, where can I get the factory U-Boot image?
Logged

sfzhi
Jr. Member
**

Karma: 1
Posts: 83


View Profile
« Reply #1 on: June 27, 2010, 03:10:16 AM »

Not sure if this is what you want to hear, but for what it's worth:

You can do one of the following, which will work:
  • Use factory u-boot with factory kernel
  • Use "normal" u-boot with "normal" kernel

Other combinations are possible too, but you will have to mess with arcNumber and mainlineLinux variables. That seems simple enough at the first sight, but considering how many people (including myself) are having or have had trouble with it, I would not even try going that way if I were you.

The factory u-boot (and the kernel) you can find here: http://code.google.com/p/guruplug/downloads/list.

Logged

Lack of knowledge is not such a big problem, unwillingness to learn is.

Alucard
Newbie
*

Karma: 0
Posts: 10


View Profile
« Reply #2 on: July 07, 2010, 03:18:23 PM »

Thanks, you're right; factory uboot lets Linux boot again.

Time to play some more.  I'm glad I can go back to factory defaults relatively easily.
Logged

Pages: [1]
Print
Jump to: