https://qa.mandrakesoft.com/show_bug.cgi?id=569

           Product: Installation
         Component: stage1
           Summary: Installation freeze on Packard Bell iXtreme AMD 2000+
           Version: 1.759
          Platform: PC
        OS/Version: All
            Status: UNCONFIRMED
          Severity: normal
          Priority: P2
        AssignedTo: [EMAIL PROTECTED]
        ReportedBy: [EMAIL PROTECTED]


Hi, I have a Packard Bell iXtreme with:- 

Explorer A (MS65-11) MB using the Via KM133A Chipset (Via VT8365A Northbridge 
and Via VT686B Southbridge controllers). 
AMD Athlon 2000+
256MB Ram 
nVidia GForce 2 MX400 
Blank Seagate IDE 40Gb disk 
Pioneer DVD
CDRW 
Intel 10/100 Nic. 
USB Keyboard and Mouse

I am trying to install either LM8.2 (boxed set) or LM9.0 (downloaded Checksums 
OK).

Following the manual I setup my BIOS and then booted off the CD. I then got to 
the splash screen, pressed <enter> and the PC locks up. Nothing happens, blank 
screen, I cannot CTRL-ALT-DEL, I have to cold boot to recover.

I tried the TEXT install and got: -
Loading CDROM.RDZ........... 
Loading VMLINUZ...........Ready 
Uncompressing Linux...OK, Booting Kernel
And then another lockup.

I have tried many options from the <F1> screen such as nopentium, ide=nodma, 
noauto, mem=nopentium, nobiospnp, etc... none help. I tried the Patch.pl file 
for the K6 processor on the advice of the ESupport site and still no joy. I 
don't think the kernel is booting to the point where it can see the floppy.

I have posted on Esupport and Mandrakeuser forums and no one can help, I have 
tried several different boot images but still no joy.

I tried the ALT1 ALT2 kernels and after the install (no mouse in ALT1, no 
Keybaord in ALT2) and re-boot the PC locks up again. Most of the hardware is 
listed as <unknown> in the hardware screen (I clicked on the button on the 
harddrive selection screen)

I don't think the boot kernel likes my PC. I also tried Redhat linux 8.0 and 
got the same problem.

Any ideas?
Thanks
Paul.



------- You are receiving this mail because: -------
You are on the CC list for the bug, or are watching someone who is.

Reply via email to