FAQ Search Today's Posts Mark Forums Read
» Video Reviews

» Linux Archive

Linux-archive is a website aiming to archive linux email lists and to make them easily accessible for linux users/developers.


» Sponsor

» Partners

» Sponsor

Go Back   Linux Archive > Debian > Debian Kernel

 
 
LinkBack Thread Tools
 
Old 02-05-2012, 09:32 PM
Donald Gordon
 
Default Bug#658759: Also on Guruplug

I've seen what looks like the same issue on my Guruplug.
linux-image-3.1.0-1-kirkwood (3.1.8-2) boots fine,
linux-image-3.2.0-1-kirkwood (3.2.2-1) doesn't get anywhere.

My U-boot banner looks like this:

----
U-Boot 2011.03 (Apr 26 2011 - 21:35:00)
Marvell-GuruPlug

SoC: Kirkwood 88F6281_A1
DRAM: 512 MiB
NAND: 512 MiB
In: serial
Out: serial
Err: serial
Net: egiga0, egiga1
88E1121 Initialized on egiga0
88E1121 Initialized on egiga1
----

And when I boot 3.2.0-1, this is what I see:

----
Loading file "/uImage.bak" from ide device 0:1 (hda1)
1570456 bytes read
Loading file "/uInitrd.bak" from ide device 0:1 (hda1)
8211832 bytes read


Marvell>> bootm 0x00800000 0x01100000
## Booting kernel from Legacy Image at 00800000 ...
Image Name: Debian kernel

Image Type: ARM Linux Kernel Image (uncompressed)
Data Size: 1570392 Bytes = 1.5 MiB
Load Address: 00008000
Entry Point: 00008000
Verifying Checksum ... OK
## Loading init Ramdisk from Legacy Image at 01100000 ...
Image Name: Debian ramdisk
Image Type: ARM Linux RAMDisk Image (gzip compressed)
Data Size: 8211768 Bytes = 7.8 MiB
Load Address: 00000000
Entry Point: 00000000
Verifying Checksum ... OK
Loading Kernel Image ... OK
OK

Starting kernel ...

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

After this, no more messages are visible on the serial console, and
there is no other indication that the boot progresses.

Thanks

donald



--
To UNSUBSCRIBE, email to debian-kernel-REQUEST@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmaster@lists.debian.org
Archive: CAK+uisC1qsj-BjrrUCWFtTgd=-Z51gN6LaQU1T=CnNzsi30OWQ@mail.gmail.com">http://lists.debian.org/CAK+uisC1qsj-BjrrUCWFtTgd=-Z51gN6LaQU1T=CnNzsi30OWQ@mail.gmail.com
 
Old 02-06-2012, 04:05 PM
Ian Campbell
 
Default Bug#658759: Also on Guruplug

On Mon, 2012-02-06 at 11:32 +1300, Donald Gordon wrote:
> I've seen what looks like the same issue on my Guruplug.
> linux-image-3.1.0-1-kirkwood (3.1.8-2) boots fine,
> linux-image-3.2.0-1-kirkwood (3.2.2-1) doesn't get anywhere.
>
> My U-boot banner looks like this:
[...]
> After this, no more messages are visible on the serial console, and
> there is no other indication that the boot progresses.

I suspect this is due to the lack of this u-boot patch:
http://lists.denx.de/pipermail/u-boot/2012-February/117020.html

I found that without this my 3.2 dreamplug kernel would not boot (with
the 2011.12-2 package from debian). It's related to
CONFIG_ARM_PATCH_PHYS_VIRT.

Ian.

--
Ian Campbell

If the rich could pay the poor to die for them, what a living the poor
could make!




--
To UNSUBSCRIBE, email to debian-kernel-REQUEST@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmaster@lists.debian.org
Archive: 1328547923.8895.4.camel@cthulhu.hellion.org.uk">ht tp://lists.debian.org/1328547923.8895.4.camel@cthulhu.hellion.org.uk
 

Thread Tools




All times are GMT. The time now is 10:50 AM.

VBulletin, Copyright ©2000 - 2014, Jelsoft Enterprises Ltd.
Content Relevant URLs by vBSEO ©2007, Crawlability, Inc.
Copyright 2007 - 2008, www.linux-archive.org