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

2012-02-11 Thread Stuart Winter
> attaching my image (gpg signed) to this message: here are md5sums: [..] I'll add this to the ftp site once I push the next round of updates. -- Stuart Winter Slackware ARM: www.armedslack.org ___ ARMedslack mailing list ARMedslack@lists.armedslack.o

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

2012-02-11 Thread Robby Workman
On Sat, 11 Feb 2012 09:12:41 + (GMT) Stuart Winter wrote: > > > Starting kernel ... > > > > Uncompressing Linux... done, booting the kernel. > [..] > > I wonder though whether the kernel is actually booting but the serial > console output has stopped. Have you tried pinging the machine's I

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

2012-02-11 Thread Jim Hammack
FWIW, this is exactly what I am seeing on my Dreamplug Ser 114xxx.  I can only boot using the original u-boot shipped with the plug (which doesn't support ext2) and a 2.6 kernel.  It's not a serial output problem - no ping replies. On 02/11/2012 0

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

2012-02-11 Thread Stuart Winter
> Starting kernel ... > > Uncompressing Linux... done, booting the kernel. [..] I wonder though whether the kernel is actually booting but the serial console output has stopped. Have you tried pinging the machine's IP after a few mins? I pushed out Linux 3.2.5 yesterday to -current. Does this

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 wrote: > On Sun, 01 Jan 2012 03:29:24 -0500 > John O'Donnell 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: > > > > >

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 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:

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

2012-01-03 Thread John O'Donnell
On 01/02/2012 04:41 AM, Stuart Winter wrote: 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

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

2012-01-02 Thread John O'Donnell
On 01/02/2012 04:41 AM, Stuart Winter wrote: 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

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 an

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

2012-01-02 Thread Davide
forgotten the names of each number) Da: John O'Donnell A: Slackware ARM port 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 compi

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

2012-01-01 Thread John O'Donnell
On 01/01/2012 01:25 PM, Stuart Winter wrote: 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. GuruPlug>> printenv bootcmd_slk bootcmd_slk=usb start;fatl

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 ___ ARMedsl

[ARMedslack] Cant get -current 3.1.5 to boot

2012-01-01 Thread John O'Donnell
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 (uncompres