On Sun, 2003-09-14 at 05:10, Philip Webb wrote: > 030727 Greg Meyer wrote: > > On Sunday 27 July 2003 04:13 pm, you wrote: > >> 030725 Greg Meyer wrote: > >>> Seems you may have tripped over a bug > >> that affects true 333fsb processors & very specific video chipsets. > >> i've sent the mobo to Soyo via the retailer, > >> so all awaits its return after 1 - 2 wk . > > Let me know how it goes once you get the board back. > > [ cc to Mdk Expert, in case anyone else has helpful advice ] > > the retailer -- to whom i returned the Soyo Dragon Ultra KT400 mobo -- > told me that Soyo had recalled them & were replacing them with new ones. > last week, i picked up a mobo, which i assume is a replacement > (i forgot to make a note of the serial numbers) > & i have now reassembled the box & tried it out. > > it seems to be an improvement at the BIOS level: > it recognises the processor as 'AMD XP 2500+' (correctly) > & defaults the DRAM clock to 166 MHz (previously it set it to 133 MHz ). > > however, there's a new problem: Linux won't start! > i had installed Mdk 9.1 , which is still there of course, > & Lilo comes up properly & tries to boot the system, > but fails with a kernel panic, which is quite new (Linux was ok before). > the lines on the screen are as follows: > > Unable to handle kernel NULL pointer dereference > at virtual address 00000000 > printing eip: c02360d0 > *pde = 00000000 Ooops: 0000 > > there follow a dozen lines of registers, call traces etc, then: > > <0> Kernel panic: Attempted to kill init! > spurious 8259A interrupt: IRQ7 > > (the last line occurs only some of the time: > it's the printer IRQ, but i haven't defined a printer on the box yet).
ahhh,,, not to sound _too_ impertinent, but printers do not need a irq,, it is the LPT (printer port on the MOBO) that takes an IRQ, so even if no printer is assigned, the port still has the IRQ, and maybe something else too. did you reset the bios for no plug and play? and did you try and run hard drake during boot up? > i tried (1) Lilo with 'nofsb', 'failsafe' & 'linux rescue': no difference; have you consider trying 'noapic' and or 'acpi=NO'? > (2) BIOS set to 'failsafe' & 'optimised': no difference; > (3) Mdk 9.1 boot diskette: no difference; > (4) Mdk 9.1 CD1 : Lilo starts regardless, even with 'hdd1' given priority > (BIOS does recognise the HDD & CDD correctly); > (5) Mdk 8.2 boot diskette: boots, but can't find 'init': > it expects a ReiserFS, which i have on the existing box; > (6) checking h/ware, ie memory & drive cables: all firmly in place; > (7) DOS diskette: boots & accepts simple commands; > (8) RAMF-118 rescue diskette: ok & allows 'mount /dev/hde1 /test', > then 'cd test' & 'ls etc' showing the appropriate files, > so the problem doesn't seem to be damage to the HDD. > > this problem is new to me: anyone have any suggestions what to try next ? -- ++++++++++++++++++++++++++++++++++++++++++ Mandrake HowTo's & More: http://twiki.mdklinuxfaq.org
Want to buy your Pack or Services from MandrakeSoft? Go to http://www.mandrakestore.com
