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

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

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

2012-01-02 Thread Davide
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

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

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 ___