Re: Upgrading from linux-image-2.6.18-686 to linux-image-2.6.24-686 breaks on AMD Geode LX CPU
2009/4/9 Sven Hoexter s...@timegate.de: On Thu, Apr 09, 2009 at 04:03:18PM +0100, Paul Richards wrote: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=464962 Turns out the AMD Geode LX is affected by the same problem, and there is already a fix in the pipeline. I've just taken a fresh look at this to see if I'm now able to move back to a normal 686 kernel, but I see that the fixed version 2.6.26-8 is not available on Lenny. Currently Lenny still has 2.6.26-1. Is there any chance this will become available on Lenny eventually? Hm currently there's -13 with -13lenny2 scheduled for the next stable release available for Lenny. s...@arthur:~$ rmadison linux-image-2.6.26-1-686 linux-image-2.6.26-1-686 | 2.6.26-13 | stable | i386 linux-image-2.6.26-1-686 | 2.6.26-13 | testing | i386 linux-image-2.6.26-1-686 | 2.6.26-13lenny2 | proposed-updates | i386 If you've still something older than that you should check your system and maybe the mirror why this is the case. I don't have proposed-updates in my sources.list. Is it advisable to add proposed-updates for a stable system? Personally I decided to run my Geode LX system with the 486 kernel image. Donno how much of a performance penalty there is but I guess for usual system usage it doesn't matter. Likewise, I can't imagine that it makes a significant difference. It would just make my Geode system sound more powerful if the login message splurted 686 instead of 486.. :) -- Paul Richards -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Re: Upgrading from linux-image-2.6.18-686 to linux-image-2.6.24-686 breaks on AMD Geode LX CPU
On Fri, Apr 10, 2009 at 11:11:15AM +0100, Paul Richards wrote: Hi, I don't have proposed-updates in my sources.list. Is it advisable to add proposed-updates for a stable system? No usually not. But in this case the patch in question should be included since the -8 release of the package and default for stable is -13 so you should've the -13 release installed. If it's not fixed in this package you've hit a different bug I'd guess or the issue wasn't solved completly. I haven't checked the changelog for -13lenny2 but I doubt that it includes a fix relevant for this case. Sven -- forevermore -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Re: Upgrading from linux-image-2.6.18-686 to linux-image-2.6.24-686 breaks on AMD Geode LX CPU
2008/4/9 Paul Richards paul.richa...@gmail.com: 2008/4/8 Paul Richards paul.richa...@gmail.com: Hi, I recently upgraded from etch to lenny and in the process my kernel was upgraded from linux-image-2.6.18-686 to linux-image-2.6.24-686. This new kernel crashes immediately after being uncompressed on boot, and I have been forced to use the 486 build of the kernel if I want 2.6.24. This AMD Geode LX processor has always executed 686 kernels in the past. Have I previously just been lucky or is this a bug in 2.6.24? A friend of mine pointed me towards this: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=464962 Turns out the AMD Geode LX is affected by the same problem, and there is already a fix in the pipeline. I've just taken a fresh look at this to see if I'm now able to move back to a normal 686 kernel, but I see that the fixed version 2.6.26-8 is not available on Lenny. Currently Lenny still has 2.6.26-1. Is there any chance this will become available on Lenny eventually? -- Paul Richards -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Re: Upgrading from linux-image-2.6.18-686 to linux-image-2.6.24-686 breaks on AMD Geode LX CPU
On Thu, Apr 09, 2009 at 04:03:18PM +0100, Paul Richards wrote: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=464962 Turns out the AMD Geode LX is affected by the same problem, and there is already a fix in the pipeline. I've just taken a fresh look at this to see if I'm now able to move back to a normal 686 kernel, but I see that the fixed version 2.6.26-8 is not available on Lenny. Currently Lenny still has 2.6.26-1. Is there any chance this will become available on Lenny eventually? Hm currently there's -13 with -13lenny2 scheduled for the next stable release available for Lenny. s...@arthur:~$ rmadison linux-image-2.6.26-1-686 linux-image-2.6.26-1-686 | 2.6.26-13 |stable | i386 linux-image-2.6.26-1-686 | 2.6.26-13 | testing | i386 linux-image-2.6.26-1-686 | 2.6.26-13lenny2 | proposed-updates | i386 If you've still something older than that you should check your system and maybe the mirror why this is the case. Personally I decided to run my Geode LX system with the 486 kernel image. Donno how much of a performance penalty there is but I guess for usual system usage it doesn't matter. Sven -- forevermore -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Re: Upgrading from linux-image-2.6.18-686 to linux-image-2.6.24-686 breaks on AMD Geode LX CPU
In a1138db30904090803g198b0d61ycd5895041b293...@mail.gmail.com, Paul Richards wrote: I've just taken a fresh look at this to see if I'm now able to move back to a normal 686 kernel, but I see that the fixed version 2.6.26-8 is not available on Lenny. Currently Lenny still has 2.6.26-1. Is there any chance this will become available on Lenny eventually? I think Lenny is scheduled for an update soon. You might see if the release team can squeeze that in. (Is it in testing, yet?) -- Boyd Stephen Smith Jr. ,= ,-_-. =. b...@iguanasuicide.net ((_/)o o(\_)) ICQ: 514984 YM/AIM: DaTwinkDaddy `-'(. .)`-' http://iguanasuicide.net/\_/ signature.asc Description: This is a digitally signed message part.
Re: Upgrading from linux-image-2.6.18-686 to linux-image-2.6.24-686 breaks on AMD Geode LX CPU
On Thu, Apr 9, 2009 at 11:21 AM, Boyd Stephen Smith Jr. wrote: Is there any chance this will become available on Lenny eventually? I think Lenny is scheduled for an update soon. You might see if the release team can squeeze that in. (Is it in testing, yet?) (Funny tone) I had to read that twice, since squeeze is also the name of the current testing! :-) To the OP, if you are in a hurry and want to try building your own kernel, you could use the kernel-package to build a vannila kernel from the latest kernel sources. That way, you get the kernel as a Debian package, the latest kernel, and get to tweak the .config and customize some drivers and settings (I use preempting for desktop my desktop, for example). Basically, you can have the cake, eat it too and, optionally, add more icing! :-) Kumar -- Kumar -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Re: Upgrading from linux-image-2.6.18-686 to linux-image-2.6.24-686 breaks on AMD Geode LX CPU
2008/4/8 Paul Richards [EMAIL PROTECTED]: Hi, I recently upgraded from etch to lenny and in the process my kernel was upgraded from linux-image-2.6.18-686 to linux-image-2.6.24-686. This new kernel crashes immediately after being uncompressed on boot, and I have been forced to use the 486 build of the kernel if I want 2.6.24. This AMD Geode LX processor has always executed 686 kernels in the past. Have I previously just been lucky or is this a bug in 2.6.24? A friend of mine pointed me towards this: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=464962 Turns out the AMD Geode LX is affected by the same problem, and there is already a fix in the pipeline. -- Paul Richards -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Upgrading from linux-image-2.6.18-686 to linux-image-2.6.24-686 breaks on AMD Geode LX CPU
On Tuesday 08 April 2008 21:12:40 Paul Richards wrote: Hi, I recently upgraded from etch to lenny and in the process my kernel was upgraded from linux-image-2.6.18-686 to linux-image-2.6.24-686. This new kernel crashes immediately after being uncompressed on boot, and I have been forced to use the 486 build of the kernel if I want 2.6.24. This AMD Geode LX processor has always executed 686 kernels in the past. Have I previously just been lucky or is this a bug in 2.6.24? This was the only problem I encountered during the etch to lenny upgrade, so congratulations to everyone involved! Below is my /proc/cpuinfo. [EMAIL PROTECTED]:~$ cat /proc/cpuinfo processor : 0 vendor_id : AuthenticAMD cpu family : 5 model : 10 model name : Geode(TM) Integrated Processor by AMD PCS stepping: 2 cpu MHz : 498.066 cache size : 128 KB fdiv_bug: no hlt_bug : no f00f_bug: no coma_bug: no fpu : yes fpu_exception : yes cpuid level : 1 wp : yes flags : fpu de pse tsc msr cx8 sep pge cmov clflush mmx mmxext 3dnowext 3dnow bogomips: 997.66 clflush size: 32 -- Paul Richards I think a bug should be reported again d-i. If one choose to install lvm, and let d-i choose the partition, when you select to have home, tmp, usr and var in separated partition, it gives a too small partition for root. Then, when there is an update of the kernel, or ia32-libs, at least, you get this problem. I had that on the last two install I made. Fortunately, with lvm, you can change the partition size, but it's not an easy process. Thierry -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Upgrading from linux-image-2.6.18-686 to linux-image-2.6.24-686 breaks on AMD Geode LX CPU
Hi, I recently upgraded from etch to lenny and in the process my kernel was upgraded from linux-image-2.6.18-686 to linux-image-2.6.24-686. This new kernel crashes immediately after being uncompressed on boot, and I have been forced to use the 486 build of the kernel if I want 2.6.24. This AMD Geode LX processor has always executed 686 kernels in the past. Have I previously just been lucky or is this a bug in 2.6.24? This was the only problem I encountered during the etch to lenny upgrade, so congratulations to everyone involved! Below is my /proc/cpuinfo. [EMAIL PROTECTED]:~$ cat /proc/cpuinfo processor : 0 vendor_id : AuthenticAMD cpu family : 5 model : 10 model name : Geode(TM) Integrated Processor by AMD PCS stepping: 2 cpu MHz : 498.066 cache size : 128 KB fdiv_bug: no hlt_bug : no f00f_bug: no coma_bug: no fpu : yes fpu_exception : yes cpuid level : 1 wp : yes flags : fpu de pse tsc msr cx8 sep pge cmov clflush mmx mmxext 3dnowext 3dnow bogomips: 997.66 clflush size: 32 -- Paul Richards -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Upgrading from linux-image-2.6.18-686 to linux-image-2.6.24-686 breaks on AMD Geode LX CPU
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 04/08/08 14:12, Paul Richards wrote: Hi, I recently upgraded from etch to lenny and in the process my kernel was upgraded from linux-image-2.6.18-686 to linux-image-2.6.24-686. This new kernel crashes immediately after being uncompressed on boot, and I have been forced to use the 486 build of the kernel if I want 2.6.24. This AMD Geode LX processor has always executed 686 kernels in the past. Have I previously just been lucky or is this a bug in 2.6.24? Maybe there's a new sub-arch, and 686 is more specific? This was the only problem I encountered during the etch to lenny upgrade, so congratulations to everyone involved! Below is my /proc/cpuinfo. [EMAIL PROTECTED]:~$ cat /proc/cpuinfo processor : 0 vendor_id : AuthenticAMD cpu family : 5 model : 10 model name : Geode(TM) Integrated Processor by AMD PCS stepping: 2 cpu MHz : 498.066 cache size : 128 KB fdiv_bug: no hlt_bug : no f00f_bug: no coma_bug: no fpu : yes fpu_exception : yes cpuid level : 1 wp : yes flags : fpu de pse tsc msr cx8 sep pge cmov clflush mmx mmxext 3dnowext 3dnow bogomips: 997.66 clflush size: 32 - -- Ron Johnson, Jr. Jefferson LA USA We want... a Shrubbery!! -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.6 (GNU/Linux) iD8DBQFH+91cS9HxQb37XmcRAkbRAJ9afZOheiepIiKfQ4dVE6ACcezwXwCeMcP9 TPmoYH19RF3XCIuJBCCT0tY= =9rit -END PGP SIGNATURE- -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
