On Sunday 14 September 2003 05:10 am, you 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
What does your lilo.conf look like? Remmeber that board has to boot with noapic acpi=off. Can you boot off the cd in rescue mode or does every attempt to boot result in this error? -- /g "Outside of a dog, a man's best friend is a book, inside a dog it's too dark to read" -Groucho Marx
Want to buy your Pack or Services from MandrakeSoft? Go to http://www.mandrakestore.com
