On Fri, 2003-06-20 at 10:24, Vincent Danen wrote: > On Thu Jun 19, 2003 at 10:10:38PM -0700, James Sparenberg wrote: > > > > > > Mark, do you have apic enabled? How are you booting the kernel (sorry if > > > > > this has been asked or reported already). I found with apci=on I got some > > > > > IRQ balancing and with apic on (ie. not using noapic) I had full balancing. > > > > > > > > > > But now I've found that with apci=on or apic, I can't use DRI in X. =( So > > > > > I've got to boot with apci=off noapic for X, and don't have IRQ balancing > > > > > anymore. > > > > > > > > Vincent just curious what's the video chip? I'm wondering if there > > > > isn't an IRQ conflict that arises because of something DRI does. Either > > > > that or someone removed the non-existent SCO code on you. > > > > > > LOL. > > > > > > It's an r128 chipset. I didn't have problems with 13mdk or 18mdk, but I was > > > fixing the XFS ACLs (19mdk-to-be) and all of a sudden it broke. Now when I > > > go back to 13mdk or 18mdk it doesn't work anymore so I'm not sure what the > > > heck is going on. > > > > > > Accounted for pretty much a wasted day tho... =( > > > > > > Sounds like something got overwritten when you moded for xfs and it's > > overwritten what 13 or 18 would normally use. > > I honestly have no clue what the deal is. Kinda frustrating because I don't > even know where to begin looking to track this sucker down.
FWIW If I'm right there are 5 main components in affect here. 1. Init scripts (probably haven't been modded... shouldn't have been) 2. vmlinuz (this shouldn't have been overwritten) 3. modules (there shouldn't have been any writting there but......) 4. initrd ??? 5. System Map. I'd start by looking at the System map and seeing if moving back to one of the older ones helps. Since a new kernel creates a new one. If you change the link in /boot to one of the older (say 18) system maps does it change the way things work? If not I'd start looking to see if something got accidentally overwritten in modules. Last would be rpm -e kernelxxxx18 (then verify by hand that it is 100% gone. It won't be) urpmi kernelxxxx18 and see if it resets. James
Want to buy your Pack or Services from MandrakeSoft? Go to http://www.mandrakestore.com
