Re: [expert] 2.2.13-22mdk is bogus?
:>> Now updated my prosessor to AMD K6-2/450 Mhzso far went fine...but when :>> started combile kernel :>> started problemsmenuconfig ok,make dep ok,then bzlilo all the possible :>> errors,ie can't get it made...Boy 4 days now trying :>> no success. If I got it right, everything works OK if you put the old procesor back into your computer? In this case it has absolutely nothing to do with the software. This is allmost certainly a sign of a hardware problem. Either your new processor has a flaw, or some part of the system (RAM? Motherboard? Power suply?) cannot cope with the higher speed. Switching to another distro will not help you at al. cu Denis --- Denis Havlik ||| http://www.ap.univie.ac.at/users/havlik (@ @) [EMAIL PROTECTED] -oOO--(_)--OOo-
Fw: [expert] 2.2.13-22mdk is bogus?
- Original Message - From: "Dan Swartzendruber" <[EMAIL PROTECTED]> To: <[EMAIL PROTECTED]> Sent: Wednesday, December 08, 1999 1:07 PM Subject: [expert] 2.2.13-22mdk is bogus? > > I did a nice clean install of 6.1 (2.2.13-7mdk) to my new K7. Worked like > a champ. After it was up and (mostly) configured, I clicked on Updates and > noted an update to kernel 2.2.13-22mdk. I said, "SURE!" It downloaded. I > did 'make depend'. Fine. I then did 'make bzImage'. It got all the way > to the bind phase and then died with an unresolved symbol > _buggy_fxsr_alignment. This was in (as I recall, and machine is not > available right now), a bugs.h file? It seems to have something to do with > a misaligned field in a data structure when doing fast floating > save/restore. So, I turn off that option in the config and repeat. This > time it binds okay, but the system panics on boot. Any ideas? > > Dan, read this message from 11/19/99 from the expert list - explains it all. - Original Message - From: "Ivan J. Wagner" <[EMAIL PROTECTED]> To: <[EMAIL PROTECTED]> Sent: Friday, November 19, 1999 9:00 PM Subject: Re: [expert] Problems building kernel 2.2.13-22mdk > On Fri, 19 Nov 1999, Axalon Bloodstone wrote: > > > On Fri, 19 Nov 1999, Rob Steele wrote: > > > > > This is my first attempt to compile the the kernel so I'm probably doing > > > something stupid. I have two problems: > > > > > > I get a linker error that goes away if I disable "PII/PIII Extended Fast > > > FPU save and restore support" > > > > > > init/main.o: In function `check_fpu': > > > init/main.o(.text.init+0x25): undefined reference to > > > `__buggy_fxsr_alignment' > > > make: *** [vmlinux] Error 1 > > I just wrote about this two days ago: deselect "Enable PII/PIII Extended > Fast FPU save and restore support" under "Processor type and features" > > > This ones been reported and well documented, I believe alan's removed this > > from the ac patches (30mdk, is latest if my memory serves me) > > Well it took me a while to figure this out. It still listed as an open > bug on Mandrake bug page (Bug #402 for package: kernel sources). I > searched the archives of this mailing list and the newbie list and found > nothing. Nobody knew about it when I e-mailed and asked. I found the > answer searching alt.os.linux.mandrake > > where is this 30mdk kernel? If it is Cooker then are you saying that (in > general I should have no problems with a Cooker kernel)? > > btw, if I replace the config file in the kernel.src.rpm package and > compile it with rpm -bb kernel.spec should I have any problems? > > > Any insight into these problems would be much appreciated. > > > > > > Thanks, > > > Rob
Re: [expert] 2.2.13-22mdk is bogus?
> Has anyone else had this BIIIG problem.!!! > This far used AMD K6-2/333 with Jamicon motherboard 100mhz bus 64 megs ram, > 10G hd,34x cdrom external usrobotics sportster flash modem,realtec ether > card, > have tested many vers RH and now Mandrake 6.1-1 with 2.2.13-7 kernel. > This far all ok...recombiled kerne couple of times...especially for ax25. > > Now updated my prosessor to AMD K6-2/450 Mhzso far went fine...but when > started combile kernel > started problemsmenuconfig ok,make dep ok,then bzlilo all the possible > errors,ie can't get it made...Boy 4 days now trying > no success. > Jarmo > [EMAIL PROTECTED] I doubt the cpu switch by itself is the problem. Several weeks ago I changed motherboard and cpu, when I booted back up, Mandrake didn't even notice the change other than to report the new processor speed. p2@467 on an Aopen ax6bc to a p3@608 on a Soyo 6ba+III -- .. Tom Brinkman[EMAIL PROTECTED] .
Re: [expert] 2.2.13-22mdk is bogus?
Hello all I'm a little bit off topic...BUT Has anyone else had this BIIIG problem.!!! This far used AMD K6-2/333 with Jamicon motherboard 100mhz bus 64 megs ram, 10G hd,34x cdrom external usrobotics sportster flash modem,realtec ether card, have tested many vers RH and now Mandrake 6.1-1 with 2.2.13-7 kernel. This far all ok...recombiled kerne couple of times...especially for ax25. Now updated my prosessor to AMD K6-2/450 Mhzso far went fine...but when started combile kernel started problemsmenuconfig ok,make dep ok,then bzlilo all the possible errors,ie can't get it made...Boy 4 days now trying no success. Got ahaa!!! Took RH 6.1 started installing ,all ok got rh running,except rh's installation (full) some how leaves much selected items uninstalled. But again when started recombile kernel,troublesbut after some hours got compilaition ok and what more rh running. In Mandrake didn't get kernel combiled. Writing this in win...my linux is MESSS! OK...now do I have to do combile every time with 333Mhz prosessor and change it afterw. to 450 or is there already invented wheel? Unfortunately this gates thing works...there's nothing to do.Exept one radioamateur program,which kind haven't found yet for linux. I'll try SUSE for testing is this only RH/MANDRAKE,which making me neurotic,mean day without linux I ME! Please don't ask err files...could not get them,beside attached them could have taken hudredthousands kb's So please if somebody have had same kind probs. and found solution,other than change computer,please drop me a note. All the best Jarmo [EMAIL PROTECTED]
Re: [expert] 2.2.13-22mdk is bogus?
All, I've run into the exact same problem myself, however I've not come up with a resolution. I, too, am running -22mdk. Rebuilding the kernel and modules thus far hasn't worked. I've pondered possibly deleting my present set of modules, then rebuilding them to see what happens as a depmod produces output that indicates I still have some modules left that weren't compiled with the last build but were from a previous build and left out when I did the last make xconfig. Could that be what vmware is pissin' and moanin' about? Rich On Thu, 9 Dec 1999, David van Balen wrote: > > I already posted this, but I guess I'll repeat it in case you missed it... > it may help you figure out what's wrong. > I upgraded from 7mdk to 22mdk with the update util. Didn't to any extra > compilation, only updated and reinstalled lilo. > After rebooting, everything appeared to go fine until I tried to run > VmWare. VmWare complained that it wasn't configured to run on the current > kernel and that I should reconfig (which sounded logical to me). However, > when it tried to recompile its modules based on the kernel headers in > /usr/src/linux/include, it barfed and complained that there was a "slight > difference of configuration" between the headers and the actual compiled > kernel. > I figure that since you tried to do some extra compiling after you > installed the kernel, you may have run into the same problem. I figure > I'll have to recompile from scratch so that my kernel matches my > headers... if you can figure out some other way, please let me know. > > DvB > >
Re: [expert] 2.2.13-22mdk is bogus?
On Wed, 8 Dec 1999, Dan Swartzendruber wrote: > > thanks for the tips, but i don't see how it can possibly be hardware. a > stock 7mdk kernel builds from source and runs fine. a stock 22mdk kernel > fails with a compiler assertion (NOTE: NOT a SEGV!) the assertion is due > to something that makes complete sense. > > > > I already posted this, but I guess I'll repeat it in case you missed it... it may help you figure out what's wrong. I upgraded from 7mdk to 22mdk with the update util. Didn't to any extra compilation, only updated and reinstalled lilo. After rebooting, everything appeared to go fine until I tried to run VmWare. VmWare complained that it wasn't configured to run on the current kernel and that I should reconfig (which sounded logical to me). However, when it tried to recompile its modules based on the kernel headers in /usr/src/linux/include, it barfed and complained that there was a "slight difference of configuration" between the headers and the actual compiled kernel. I figure that since you tried to do some extra compiling after you installed the kernel, you may have run into the same problem. I figure I'll have to recompile from scratch so that my kernel matches my headers... if you can figure out some other way, please let me know. DvB
Re: [expert] 2.2.13-22mdk is bogus?
On Wed, 08 Dec 1999, you wrote: > thanks for the tips, but i don't see how it can possibly be hardware. a > stock 7mdk kernel builds from source and runs fine. a stock 22mdk kernel > fails with a compiler assertion (NOTE: NOT a SEGV!) the assertion is due > to something that makes complete sense. I know you don't want to hear it, but hardware errors will give 'statement not terminated properly', ' defined but not used', stuff like that. Error1 Not always, maybe not even often, seg faults. BTW, one of the kernels i built from source was -22mdk. I didn't try and redo a pre-built one tho, so maybe that's the difference. 'Course if it's not the no.3 cause of computer problems, could be the no.1 cause is behind your compile problems. No.1 is what had me baffled with kernel compiles for awhile ;-) -- .. Tom Brinkman[EMAIL PROTECTED] .
Re: [expert] 2.2.13-22mdk is bogus?
At 03:24 PM 12/8/99 -0600, you wrote: >On Wed, 08 Dec 1999, you wrote: >> I did a nice clean install of 6.1 (2.2.13-7mdk) to my new K7. Worked like >> a champ. After it was up and (mostly) configured, I clicked on Updates and >> noted an update to kernel 2.2.13-22mdk. I said, "SURE!" It downloaded. I >> did 'make depend'. Fine. I then did 'make bzImage'. It got all the way >> to the bind phase and then died with an unresolved symbol >> _buggy_fxsr_alignment. This was in (as I recall, and machine is not >> available right now), a bugs.h file? It seems to have something to do with >> a misaligned field in a data structure when doing fast floating >> save/restore. So, I turn off that option in the config and repeat. This >> time it binds okay, but the system panics on boot. Any ideas? > > Prob'ly just more questions. I don't/didn't know you were >supposed to do anything with a 'ready made kernel' other than >install the rpm and edit lilo.conf, run lilo and boot it ? I did a >few that way, -22mdk was one, no problems. > >I compiled one from source, I believe it was -7mdk with no >errors, edited lilo.conf, ran lilo and booted to it. I did this >one, 'cause being a newbie, I thought I ought'a try one. Beginner's >luck! A few I tried after that, no dice errors during 'make' >usually. Being a newbie I retraced my steps, where did i go wrong? >Then it dawned on me. Besides being a newbie, I'm an obsessive >o/c'r. I have a fixation on runnin pc100 ram at 135mhz cas2 >timings (2-3-3, precharge on). Altho I can run anything in Windows >clocked to the hilt (p3-450 @ 608), and most everything in Linux, >if I just reduce my ram timing to 3-3-3, compiles work, no problems. > >I know it's a hard pill to swallow, specially if you built the >system yourself, and even worse if you paid Dell to do it for you >but . Well, a lot of these kinds of problems I read about on >lists and NG's, I jus' havt'a suspect it's hardware problems. O/c'd >or not, and specially if there's a CuMine/i8whatever or a K7/athlon >motherboard involved. And, of course, anything o/c'd. > >I just havt'a believe that the newer, faster systems, 'specially >since both the Cu/i8xx and Athlon/mobo/voltages systems have ram >issues, that might be a good place to start lookin at. See if >setting your ram to 3-3-3, precharge disabled, won't get you thru a >kernel compile (from source). thanks for the tips, but i don't see how it can possibly be hardware. a stock 7mdk kernel builds from source and runs fine. a stock 22mdk kernel fails with a compiler assertion (NOTE: NOT a SEGV!) the assertion is due to something that makes complete sense.
Re: [expert] 2.2.13-22mdk is bogus?
On Wed, 08 Dec 1999, you wrote: > I did a nice clean install of 6.1 (2.2.13-7mdk) to my new K7. Worked like > a champ. After it was up and (mostly) configured, I clicked on Updates and > noted an update to kernel 2.2.13-22mdk. I said, "SURE!" It downloaded. I > did 'make depend'. Fine. I then did 'make bzImage'. It got all the way > to the bind phase and then died with an unresolved symbol > _buggy_fxsr_alignment. This was in (as I recall, and machine is not > available right now), a bugs.h file? It seems to have something to do with > a misaligned field in a data structure when doing fast floating > save/restore. So, I turn off that option in the config and repeat. This > time it binds okay, but the system panics on boot. Any ideas? Prob'ly just more questions. I don't/didn't know you were supposed to do anything with a 'ready made kernel' other than install the rpm and edit lilo.conf, run lilo and boot it ? I did a few that way, -22mdk was one, no problems. I compiled one from source, I believe it was -7mdk with no errors, edited lilo.conf, ran lilo and booted to it. I did this one, 'cause being a newbie, I thought I ought'a try one. Beginner's luck! A few I tried after that, no dice errors during 'make' usually. Being a newbie I retraced my steps, where did i go wrong? Then it dawned on me. Besides being a newbie, I'm an obsessive o/c'r. I have a fixation on runnin pc100 ram at 135mhz cas2 timings (2-3-3, precharge on). Altho I can run anything in Windows clocked to the hilt (p3-450 @ 608), and most everything in Linux, if I just reduce my ram timing to 3-3-3, compiles work, no problems. I know it's a hard pill to swallow, specially if you built the system yourself, and even worse if you paid Dell to do it for you but . Well, a lot of these kinds of problems I read about on lists and NG's, I jus' havt'a suspect it's hardware problems. O/c'd or not, and specially if there's a CuMine/i8whatever or a K7/athlon motherboard involved. And, of course, anything o/c'd. I just havt'a believe that the newer, faster systems, 'specially since both the Cu/i8xx and Athlon/mobo/voltages systems have ram issues, that might be a good place to start lookin at. See if setting your ram to 3-3-3, precharge disabled, won't get you thru a kernel compile (from source). -- .. Tom Brinkman[EMAIL PROTECTED] .
[expert] 2.2.13-22mdk is bogus?
I did a nice clean install of 6.1 (2.2.13-7mdk) to my new K7. Worked like a champ. After it was up and (mostly) configured, I clicked on Updates and noted an update to kernel 2.2.13-22mdk. I said, "SURE!" It downloaded. I did 'make depend'. Fine. I then did 'make bzImage'. It got all the way to the bind phase and then died with an unresolved symbol _buggy_fxsr_alignment. This was in (as I recall, and machine is not available right now), a bugs.h file? It seems to have something to do with a misaligned field in a data structure when doing fast floating save/restore. So, I turn off that option in the config and repeat. This time it binds okay, but the system panics on boot. Any ideas?
