Re: [ARMedslack] Cant get -current 3.1.5 to boot
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 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. Its possible, but I hope it doesnt refer to all the current Sheevas that are really Guruplugs. -- === 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
Re: [ARMedslack] Cant get -current 3.1.5 to boot
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
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 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 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
