Re: [ARMedslack] Cant get -current 3.1.5 to boot

2012-02-10 Thread Robby Workman
On Sun, 01 Jan 2012 03:29:24 -0500
John O'Donnell unixjohn1...@gmail.com wrote:

 I upgraded from 3.1.2 to the 3.1.5 packages yesterday. Before
 attempting to compile the guruplug UAP drivers I tried to boot and
 had no luck.  Hung at:
 
 
 -- ## Booting kernel from Legacy Image at 0080 ...
 Image Name:   Linux-3.1.5-kirkwood
 Image Type:   ARM Linux Kernel Image (uncompressed)
 Data Size:2090424 Bytes = 2 MiB
 Load Address: 8000
 Entry Point:  8000
 Verifying Checksum ... OK
 ## Loading init Ramdisk from Legacy Image at 0110 ...
 Image Name:   Slackware ARM Initial RAM disk f
 Image Type:   ARM Linux RAMDisk Image (gzip compressed)
 Data Size:5811263 Bytes = 5.5 MiB
 Load Address: 
 Entry Point:  
 Verifying Checksum ... OK
 Loading Kernel Image ... OK
 OK
 
 Starting kernel ...
 
 Uncompressing Linux... done, booting the kernel.
 
 
 I compiled up the modules and my own uImage with the .config that
 comes with the armedslack kernel source and the same thing happens.
 
 I set it back to 3.1.2 and it boots fine.


Oh bah, something definitely changed somewhere along the line :/

For a new project here, I need a newer kernel than the one in 13.37,
so I decided to use the 3.2.2 kernel from -current.  I get the same
problem here (albeit under slightly different circumstances).

Mine is installed to the NAND, and rootfs is on the mtd, so I don't
need an initrd at all; thus, my env settings are this:

Marvell printenv
arcNumber=2659
baudrate=115200
bootargs_console=console=ttyS0,115200
bootargs_root=ubi.mtd=2 root=ubi0:rootfs rootfstype=ubifs rootfs=ubifs
bootcmd=setenv bootargs $(bootargs_console) $(bootargs_root); run bootcmd_nand; 
run bootcmd_slack
bootcmd_nand=nand read 0x80 0x10 0x40
bootcmd_slack=bootm 0x80
bootdelay=3
eth1addr=02:50:43:eb:75:43
ethact=egiga0
ethaddr=00:50:43:01:5D:EA
fileaddr=80
filesize=36D00
ipaddr=192.168.13.1
mainlineLinux=yes
nand_erasesize=2
nand_oobsize=40
nand_writesize=800
serverip=192.168.13.11
stderr=serial
stdin=serial
stdout=serial


When I boot, here's what happens:

U-Boot 2011.06 (Jul 26 2011 - 12:26:42)
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
Hit any key to stop autoboot:  0 

NAND read: device 0 offset 0x10, size 0x40
 4194304 bytes read: OK
## Booting kernel from Legacy Image at 0080 ...
   Image Name:   Linux-3.2.2-kirkwood
   Image Type:   ARM Linux Kernel Image (uncompressed)
   Data Size:2082616 Bytes = 2 MiB
   Load Address: 8000
   Entry Point:  8000
   Verifying Checksum ... OK
   Loading Kernel Image ... OK
OK

Starting kernel ...

Uncompressing Linux... done, booting the kernel.

...  nothing ...


I can boot the 13.37 kernel and such just fine still, but I don't
have any of the old 3.1.x kernels from -current.  I guess I'll have
to compile my own, because I *really* need something newer than 
2.6.38 :/

-RW 
___
ARMedslack mailing list
ARMedslack@lists.armedslack.org
http://lists.armedslack.org/mailman/listinfo/armedslack


Re: [ARMedslack] Cant get -current 3.1.5 to boot

2012-02-10 Thread Robby Workman
On Sat, 11 Feb 2012 01:08:13 -0600
Robby Workman r...@rlworkman.net wrote:

 On Sun, 01 Jan 2012 03:29:24 -0500
 John O'Donnell unixjohn1...@gmail.com wrote:
 
  I upgraded from 3.1.2 to the 3.1.5 packages yesterday. Before
  attempting to compile the guruplug UAP drivers I tried to boot and
  had no luck.  Hung at:
  
  
  -- ## Booting kernel from Legacy Image at 0080 ...
  Image Name:   Linux-3.1.5-kirkwood
  Image Type:   ARM Linux Kernel Image (uncompressed)
  Data Size:2090424 Bytes = 2 MiB
  Load Address: 8000
  Entry Point:  8000
  Verifying Checksum ... OK
  ## Loading init Ramdisk from Legacy Image at 0110 ...
  Image Name:   Slackware ARM Initial RAM disk f
  Image Type:   ARM Linux RAMDisk Image (gzip compressed)
  Data Size:5811263 Bytes = 5.5 MiB
  Load Address: 
  Entry Point:  
  Verifying Checksum ... OK
  Loading Kernel Image ... OK
  OK
  
  Starting kernel ...
  
  Uncompressing Linux... done, booting the kernel.
  
  
  I compiled up the modules and my own uImage with the .config that
  comes with the armedslack kernel source and the same thing happens.
  
  I set it back to 3.1.2 and it boots fine.
 
 
 Oh bah, something definitely changed somewhere along the line :/
 
 For a new project here, I need a newer kernel than the one in 13.37,
 so I decided to use the 3.2.2 kernel from -current.  I get the same
 problem here (albeit under slightly different circumstances).
 
 Mine is installed to the NAND, and rootfs is on the mtd, so I don't
 need an initrd at all; thus, my env settings are this:
 
 Marvell printenv
 arcNumber=2659
 baudrate=115200
 bootargs_console=console=ttyS0,115200
 bootargs_root=ubi.mtd=2 root=ubi0:rootfs rootfstype=ubifs rootfs=ubifs
 bootcmd=setenv bootargs $(bootargs_console) $(bootargs_root); run
 bootcmd_nand; run bootcmd_slack bootcmd_nand=nand read 0x80
 0x10 0x40 bootcmd_slack=bootm 0x80
 bootdelay=3
 eth1addr=02:50:43:eb:75:43
 ethact=egiga0
 ethaddr=00:50:43:01:5D:EA
 fileaddr=80
 filesize=36D00
 ipaddr=192.168.13.1
 mainlineLinux=yes
 nand_erasesize=2
 nand_oobsize=40
 nand_writesize=800
 serverip=192.168.13.11
 stderr=serial
 stdin=serial
 stdout=serial
 
 
 When I boot, here's what happens:
 
 U-Boot 2011.06 (Jul 26 2011 - 12:26:42)
 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
 Hit any key to stop autoboot:  0 
 
 NAND read: device 0 offset 0x10, size 0x40
  4194304 bytes read: OK
 ## Booting kernel from Legacy Image at 0080 ...
Image Name:   Linux-3.2.2-kirkwood
Image Type:   ARM Linux Kernel Image (uncompressed)
Data Size:2082616 Bytes = 2 MiB
Load Address: 8000
Entry Point:  8000
Verifying Checksum ... OK
Loading Kernel Image ... OK
 OK
 
 Starting kernel ...
 
 Uncompressing Linux... done, booting the kernel.
 
 ...  nothing ...
 
 
 I can boot the 13.37 kernel and such just fine still, but I don't
 have any of the old 3.1.x kernels from -current.  I guess I'll have
 to compile my own, because I *really* need something newer than 
 2.6.38 :/


And just found this:

  http://www.mail-archive.com/debian-bugs-dist@lists.debian.org/msg986288.html
  http://lists.denx.de/pipermail/u-boot/2012-February/117020.html

So I went here:

  http://www.cyrius.com/debian/kirkwood/sheevaplug/uboot-upgrade.html

and grabbed this:

  http://people.debian.org/~tbm/u-boot/2011.12-2/guruplug/u-boot.kwb

Even so, this still hangs:

U-Boot 2011.12 (Jan 08 2012 - 21:46:50)
Marvell-GuruPlug

SoC:   Kirkwood 88F6281_A1
DRAM:  512 MiB
WARNING: Caches not enabled
NAND:  512 MiB
In:serial
Out:   serial
Err:   serial
Net:   egiga0, egiga1
88E1121 Initialized on egiga0
88E1121 Initialized on egiga1
Hit any key to stop autoboot:  0 

NAND read: device 0 offset 0x10, size 0x40
 4194304 bytes read: OK
## Booting kernel from Legacy Image at 0080 ...
   Image Name:   Linux-3.2.2-kirkwood
   Image Type:   ARM Linux Kernel Image (uncompressed)
   Data Size:2082616 Bytes = 2 MiB
   Load Address: 8000
   Entry Point:  8000
   Verifying Checksum ... OK
   Loading Kernel Image ... OK
OK

Starting kernel ...

Uncompressing Linux... done, booting the kernel.

... bah ...



___
ARMedslack mailing list
ARMedslack@lists.armedslack.org
http://lists.armedslack.org/mailman/listinfo/armedslack


Re: [ARMedslack] Cant get -current 3.1.5 to boot

2012-01-02 Thread Davide
Have not yet fiddled with new 3.x.x kernels yet but experience forced me to be 
carefull wneb copying .config's across releases.
Using 2.6.38.1 config on 2.6.38.x  was possible but using 2.6.38.x confin on 
2.6.39.x would produce unexpected results. (38 and 39 ar just examples coz I've 
forgotten the names of each number)




 Da: John O'Donnell unixjohn1...@gmail.com
A: Slackware ARM port armedslack@lists.armedslack.org 
Inviato: Domenica 1 Gennaio 2012 9:29
Oggetto: [ARMedslack] Cant get -current 3.1.5 to boot
 
I upgraded from 3.1.2 to the 3.1.5 packages yesterday. Before attempting to 
compile the guruplug UAP drivers I tried to boot and had no luck.  Hung at:


-- ## Booting kernel from Legacy Image at 0080 ...
   Image Name:   Linux-3.1.5-kirkwood
   Image Type:   ARM Linux Kernel Image (uncompressed)
   Data Size:    2090424 Bytes = 2 MiB
   Load Address: 8000
   Entry Point:  8000
   Verifying Checksum ... OK
## Loading init Ramdisk from Legacy Image at 0110 ...
   Image Name:   Slackware ARM Initial RAM disk f
   Image Type:   ARM Linux RAMDisk Image (gzip compressed)
   Data Size:    5811263 Bytes = 5.5 MiB
   Load Address: 
   Entry Point:  
   Verifying Checksum ... OK
   Loading Kernel Image ... OK
OK

Starting kernel ...

Uncompressing Linux... done, booting the kernel.


I compiled up the modules and my own uImage with the .config that comes with 
the armedslack kernel source and the same thing happens.

I set it back to 3.1.2 and it boots fine.
John

Oh yeah - Happy New Year ;-)

=== Never ask a geek why, just nod your head and slowly back away.===
++==+
|  John O'Donnell                |                                  |
|  (Sr. Systems Engineer,        |    http://juanisan.homeip.net    |
|  Net Admin, Programmer, etc.)  |  E-Mail: unixjohn1...@gmail.com  |
++==+
No man is useless who has a friend, and if we are loved we are
indispensable.  -- Robert Louis Stevenson
___
ARMedslack mailing list
ARMedslack@lists.armedslack.org
http://lists.armedslack.org/mailman/listinfo/armedslack___
ARMedslack mailing list
ARMedslack@lists.armedslack.org
http://lists.armedslack.org/mailman/listinfo/armedslack


Re: [ARMedslack] Cant get -current 3.1.5 to boot

2012-01-02 Thread Stuart Winter
On Mon, 2 Jan 2012, Davide wrote:

 Have not yet fiddled with new 3.x.x kernels yet but experience forced me to 
 be carefull wneb copying .config's across releases.
 Using 2.6.38.1 config on 2.6.38.x  was possible but using 2.6.38.x confin on 
 2.6.39.x would produce unexpected results. (38 and 39 ar just examples coz 
 I've forgotten the names of each number)

He's using the .config provided in armedslack's tree - which works fine
for me on the sheevaplug and openrd client.

I've just prepared linux 3.2rc7 packages so you can see whether those
work.
Perhaps something about the guruplug support got broken in 3.1.5.___
ARMedslack mailing list
ARMedslack@lists.armedslack.org
http://lists.armedslack.org/mailman/listinfo/armedslack


Re: [ARMedslack] Cant get -current 3.1.5 to boot

2012-01-01 Thread Stuart Winter

 I set it back to 3.1.2 and it boots fine.

Do you have the same memory location settings as in the INSTALL_KIRKWOOD
doc?

I've seen this before when there's not enough RAM been allocated.

-- 
Stuart Winter
Slackware ARM: www.armedslack.org
___
ARMedslack mailing list
ARMedslack@lists.armedslack.org
http://lists.armedslack.org/mailman/listinfo/armedslack