Re: [gentoo-user] new CPU march=athlon-xp
On 8 Oct 2003, at 9:18 pm, Hemmann, Volker Armin wrote: On Wednesday 08 October 2003 00:14, mathieu perrenoud wrote: CFLAGS=-O3 -march=athlon-xp -funroll-loops -fprefetch-loop-arrays -pipe -fomit-frame-pointer After some years of compiling with different gcc versions I state, that using O3 is a useless waste of time. The binaries are bigger (less catch left for anything else), the compiling needs a whole lot of time longer than evverything else and a lot of proggies are not very stable. Try Os. I am using Os with my athlon-xp for some time now, with pleasurable results. You've mentioned this before. I've just finished an `emerge -up world` which took several days because KDE was rebuilt, so if I can speed compiling I'll be very pleased. KDE is slow enough running, or rather *desperately slow* running, but I hope to speed this by prelinking (which I'm about to attempt). For the future, tho', what CFLAGS do you recommend for a Pentium 2, please..? I see that a week or so you recommended for the Pentium 3: -march=pentium3 -Os -fomit-frame-pointer -msse -mfpmath=sse but I gather from `man gcc` that -msse -mfpmath=sse are not supported on Pentium 2. Currently I'm using: CFLAGS=-march=pentium2 -O3 -pipe -fomit-frame-pointer Would you recommend: CFLAGS=-march=pentium2 -Os -pipe -fomit-frame-pointer or is there anything else i could usefully (and stably) add..? Many thanks in advance for your time, Stroller. -- [EMAIL PROTECTED] mailing list
Re: [gentoo-user] new CPU march=athlon-xp
On Thursday 09 October 2003 22:50, Stroller wrote: I see that a week or so you recommended for the Pentium 3: -march=pentium3 -Os -fomit-frame-pointer -msse -mfpmath=sse but I gather from `man gcc` that -msse -mfpmath=sse are not supported on Pentium 2. Currently I'm using: CFLAGS=-march=pentium2 -O3 -pipe -fomit-frame-pointer Would you recommend: CFLAGS=-march=pentium2 -Os -pipe -fomit-frame-pointer or is there anything else i could usefully (and stably) add..? you could add -ftracer, anything else should be done my pentium2 and Os, so your line looks fine for me, but pentium2 users should be give more reliable advice. Glück Auf Volker -- Conclusions In a straight-up fight, the Empire squashes the Federation like a bug. Even with its numerical advantage removed, the Empire would still squash the Federation like a bug. Accept it. -Michael Wong -- [EMAIL PROTECTED] mailing list
Re: [gentoo-user] new CPU march=athlon-xp
On Wed, 8 Oct 2003 01:29:30 +0100 Peter Ruskin [EMAIL PROTECTED] wrote: On Wednesday 08 Oct 2003 01:14, mathieu perrenoud wrote: Hello, Since two months, everything goes wrong in my pc: erratic disks, mb's chipset overheating... And since yesterday, my box has freezed 3 times (the three times during OO1.1 compilation). So I've decided to blame this on my mobo and to buy a new one, and I new CPU btw. (If you think that I'm wrong, thanks to warn me). I've compiled every app with the following flags: CFLAGS=-O3 -march=athlon-xp -funroll-loops -fprefetch-loop-arrays -pipe -fomit-frame-pointer If you change these to: CFLAGS=-march=athlon-mp -O2 -fomit-frame-pointer -pipe ...I bet you can save yourself a lot of money. I've never had a problem with CFLAGS=-march=athlon-xp -O3 -pipe -fomit-frame-pointer -- [EMAIL PROTECTED] mailing list
Re: [gentoo-user] new CPU march=athlon-xp
And a stupid question to end: could it be the OO's compilation that freeze my box? Yes and no. It could be because you were compiling OO, but not OO's fault. Building OO is a very processor intensive task. If you've already been having problems with overheating, then the first thing I'd try is to get better fans. Although, if this has been a problem for a while, there is a good chance that the mobo is damaged anyway from the overheating. Before you get the mobo, get better/more cooling fans. If that doesn't help, get the new mobo, and you'll already have the better fans to use with it :) I've got 2 brand new fans, and I've monitored temp, usage disk and whatever during compilation. everything was fine. As for the processor and RAM, it is okay to keep the old ones as long as you know that they work fine. Try running memtest86 on your RAM to make sure its in decent condition. Unless you're getting weird errors and segfaults everywhere, your processor is probably fine. If I understand well: if the mem is fine then the cpu is fine too? -- mathieu -- [EMAIL PROTECTED] mailing list
Re: [gentoo-user] new CPU march=athlon-xp
On Wed, 8 Oct 2003, mathieu perrenoud wrote: Yes and no. It could be because you were compiling OO, but not OO's fault. Building OO is a very processor intensive task. If you've already been having problems with overheating, then the first thing I'd try is to get better fans. Although, if this has been a problem for a while, there is a good chance that the mobo is damaged anyway from the overheating. Before you get the mobo, get better/more cooling fans. If that doesn't help, get the new mobo, and you'll already have the better fans to use with it :) I've got 2 brand new fans, and I've monitored temp, usage disk and whatever during compilation. everything was fine. What's the temp of the north bridge and RAM? As for the processor and RAM, it is okay to keep the old ones as long as you know that they work fine. Try running memtest86 on your RAM to make sure its in decent condition. Unless you're getting weird errors and segfaults everywhere, your processor is probably fine. If I understand well: if the mem is fine then the cpu is fine too? Probably but not necessarily. memtest86 is still not the most cpu-intensive program, since the only thing it does is memory. On the other hand, if memtest86 were to crash, you know you've got a bad cpu. I once had a board I was using memtest86 on. It always found bad RAM at a certain memory range, even with completely different RAM (which had tested good elsewhere) and a different CPU. It seemed the motherboard itself was bad. -- Marshal Newrock, unemployed Linux user in Lansing, MI Caution: Product will be hot after heating -- [EMAIL PROTECTED] mailing list
Re: [gentoo-user] new CPU march=athlon-xp
To eliminate overheating as the source of the problem, take off the side of your case, and blow a desktop fan onto the internals while using the machine for a few hours. If the problems go away, you know it's cooling problems- if not, you have other problems. From what you've said, and my own experience, your system and/or cpu is probably overheating. Try cleaning out the dust, and check the contact of your heatsink/cpu- the contact grease will eventually go dry and lose heat transfer capability, and need to be redone. Use Artic silver, or another high quality grease. All your symtoms are classic overheating problems. Robert Crawford On Tuesday 07 October 2003 8:30 pm, Andrew Gaffney wrote: mathieu perrenoud wrote: Hello, Since two months, everything goes wrong in my pc: erratic disks, mb's chipset overheating... And since yesterday, my box has freezed 3 times (the three times during OO1.1 compilation). So I've decided to blame this on my mobo and to buy a new one, and I new CPU btw. (If you think that I'm wrong, thanks to warn me). I've compiled every app with the following flags: CFLAGS=-O3 -march=athlon-xp -funroll-loops -fprefetch-loop-arrays -pipe -fomit-frame-pointer And I'd like to just switch the new mobo and cpu plug play, without reinstalling and recompiling everything. My actual mother board is an asus a7v266 and my cpu an amd 1800+. I guess that if I don't want to recompile everything, I have to stick to AMD. But could I keep the old one or do I have to change my cpu if I change my mb? And buy new ram? What should I include in my kernel before installing the new card? And a stupid question to end: could it be the OO's compilation that freeze my box? Yes and no. It could be because you were compiling OO, but not OO's fault. Building OO is a very processor intensive task. If you've already been having problems with overheating, then the first thing I'd try is to get better fans. Although, if this has been a problem for a while, there is a good chance that the mobo is damaged anyway from the overheating. Before you get the mobo, get better/more cooling fans. If that doesn't help, get the new mobo, and you'll already have the better fans to use with it :) As for the processor and RAM, it is okay to keep the old ones as long as you know that they work fine. Try running memtest86 on your RAM to make sure its in decent condition. Unless you're getting weird errors and segfaults everywhere, your processor is probably fine. -- [EMAIL PROTECTED] mailing list
Re: [gentoo-user] new CPU march=athlon-xp
On Wed, 8 Oct 2003, Robert Crawford wrote: To eliminate overheating as the source of the problem, take off the side of your case, and blow a desktop fan onto the internals while using the machine for a few hours. If the problems go away, you know it's cooling problems- if not, you have other problems. From what you've said, and my own experience, your system and/or cpu is probably overheating. Try cleaning out the dust, and check the contact of your heatsink/cpu- the contact grease will eventually go dry and lose heat transfer capability, and need to be redone. Use Artic silver, or another high quality grease. All your symtoms are classic overheating problems. I like Arctic Alumina (available from Arctic Silver), which is nicely non-conductive. -- Marshal Newrock, unemployed Linux user in Lansing, MI Caution: Product will be hot after heating -- [EMAIL PROTECTED] mailing list
Re: [gentoo-user] new CPU march=athlon-xp
On Wednesday 08 October 2003 14:13, Marshal Newrock wrote: I like Arctic Alumina (available from Arctic Silver), which is nicely non-conductive. and you can sparte some bucks and use any paste. If you put so much paste on the cpu that its heat transfer rate becomes realy significant, you put to much on it ;o) For testing: try cpuburn. If your cpu survives some hours, everything should be fine. Glück Auf Volker who tried 5 different pastes/pads (artic silver, thermaltake silver, some 'normal', some 'normal' of my silverado, one pad) and did not see differences between the pastes (the pad was worse) -- Conclusions In a straight-up fight, the Empire squashes the Federation like a bug. Even with its numerical advantage removed, the Empire would still squash the Federation like a bug. Accept it. -Michael Wong -- [EMAIL PROTECTED] mailing list
Re: [gentoo-user] new CPU march=athlon-xp
On Wednesday 08 October 2003 00:14, mathieu perrenoud wrote: Hello, Since two months, everything goes wrong in my pc: erratic disks, mb's chipset overheating... And since yesterday, my box has freezed 3 times (the three times during OO1.1 compilation). So I've decided to blame this on my mobo and to buy a new one, and I new CPU btw. (If you think that I'm wrong, thanks to warn me). I've compiled every app with the following flags: CFLAGS=-O3 -march=athlon-xp -funroll-loops -fprefetch-loop-arrays -pipe -fomit-frame-pointer After some years of compiling with different gcc versions I state, that using O3 is a useless waste of time. The binaries are bigger (less catch left for anything else), the compiling needs a whole lot of time longer than evverything else and a lot of proggies are not very stable. Try Os. I am using Os with my athlon-xp for some time now, with pleasurable results. Glück Auf Volker -- Conclusions In a straight-up fight, the Empire squashes the Federation like a bug. Even with its numerical advantage removed, the Empire would still squash the Federation like a bug. Accept it. -Michael Wong -- [EMAIL PROTECTED] mailing list
Re: [gentoo-user] new CPU march=athlon-xp
I had some similar problems with freezing. It appeared after several months with a perfectly stable computer. I tried to blame it on everything, but it only became better after I swithed to the gentoo-sources kernel. Try that! It made stability wonders for me! mathieu perrenoud wrote: Hello, Since two months, everything goes wrong in my pc: erratic disks, mb's chipset overheating... And since yesterday, my box has freezed 3 times (the three times during OO1.1 compilation). So I've decided to blame this on my mobo and to buy a new one, and I new CPU btw. (If you think that I'm wrong, thanks to warn me). I've compiled every app with the following flags: CFLAGS=-O3 -march=athlon-xp -funroll-loops -fprefetch-loop-arrays -pipe -fomit-frame-pointer And I'd like to just switch the new mobo and cpu plug play, without reinstalling and recompiling everything. My actual mother board is an asus a7v266 and my cpu an amd 1800+. I guess that if I don't want to recompile everything, I have to stick to AMD. But could I keep the old one or do I have to change my cpu if I change my mb? And buy new ram? What should I include in my kernel before installing the new card? And a stupid question to end: could it be the OO's compilation that freeze my box? -- [EMAIL PROTECTED] mailing list
