Re: Boot Failures.......
Chris Ridley wrote:
>
> Trying to install 2.2r2 on an intel i486 dx2 (80486-dx2-s) machine, (clone
> - DTK Computer), 6mhz, 24MB RAM, 428 MB HDD (Segate ST3491A), Award Bios
> v4.50g (10). Have the CD ROM set - fails on executing boot.bat from the CD
> ROM but it dies after:
>
> hda: ST3491A-XR, ATA DISK drive
> hdb: FX4820T, ATAPI CDROM drive
>
> Unable to handle kernel paging request at virtual address c1fffff9........
> ...
> ...
> Aiee, killing interrupt handler
>
> Did not expect it to load smoothly from CD.
>
> So I tired using a boot disk (got disk image from your site and tried image
> from CD) and it is ok...until...
>
> hda: ST3491A-XR, ATA DISK drive
> Unable to handle kernel NULL pointer dereference at virtual address 00000000
> current->tss.cr3 = 00101000, %cr3 = 00101000
> *pde = 00000000
> Oops: 0000
> CPU: 0
> EIP: 0010:[<c03b779f>]
> EFLAGS:00010286
> eax: 00000000 ebx: c032528c ecx: c0325270 edx: 123401f7
> esi: 00000000 edi: c0325270 ebp: c032539d esp: c17fbf68
> ds: 0018 es: 0018 ss: 0018
> Process swapper (pid: 1, process nr: 1; stackpage=c17fb000)
> Stack: 00000000 00000001 c17fbfb0 00000000 00000282 00000282 00000246 c019312e
> c0325270 00000f00 00000001 c031d6e8 00000001 00000001 00000001 00000001
> 00000001 00000001 c02dcbda c02dcc00 c02dc465 c010600 c02dccaa 00000f00
> Call Trace: [<c019312e>] [<c0106000>] [<c0106000>] [<c0100018>]
> [<c010615f>] [<c
> 0108c17>]
> Code: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
>
> And that is where she hangs. I looked at the help files and there did not
> seem to be any that were applicable - though I did try no387 (its an old
> machine) but it made no diff. Do we have a memory problem?
>
> Any suggestions would be appreciated. Really want to make it work!
>
> Chris Ridley
> cridley@drtel.net
>
I've got the exact same errrors with a bad processor.Granted it was a
PIII,but
they were the EXACT problems you describe.Replacingthe CPU solved the
problem.
Now this being a 486 it may be something specific to 486 but I'll try
and replace
the 486 in case this is not a known problem with 486.
Reply to: