Re: [SLE] Unable to complete install of 9.3 (Athlon 64 bit)
From: Gil Weber (gil_at_gilweber.com)
Date: 10/08/05
- Previous message: Jerry Westrick: "Re: [SLE] Help with disk integrity and RAID-1 please"
- In reply to: Stan Glasoe: "Re: [SLE] Unable to complete install of 9.3 (Athlon 64 bit)"
- Next in thread: Stan Glasoe: "Re: [SLE] Unable to complete install of 9.3 (Athlon 64 bit)"
- Reply: Stan Glasoe: "Re: [SLE] Unable to complete install of 9.3 (Athlon 64 bit)"
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
To: suse-linux-e@suse.com Date: Sat, 8 Oct 2005 17:23:53 -0400
On Sat October 8 2005 5:06 pm, Stan Glasoe wrote:
> On Friday 07 October 2005 12:25 pm, Gil Weber wrote:
> > Stan, my wife can't get a desktop from which she can try Ctrl+Alt+F1.
> > Then when she tried init3 from GRUB Sax2 does not complete. It starts
> > "spinning" the little "X" but it locks after a short time.
> My system has done this and it can take 5 minutes before it finally times
> out with a real error.
> > She has tried every other possible combination (reiser, XFS, EXT2, EXT3)
> > but all of them lock either before getting to the desktop or immediately
> > upon displaying the desktop. Further, she has also tried this in Safe
> > Mode with the same results.
> >
> > It seems that as soon as she tries to move the mouse or enter a
> > keystroke the system locks.
> >
> > We ran a memtest for about 40 minutes and got no errors. We are now
> > running another memtest and will let it go for a couple of hours to see
> > if anything shows up.
> Memtest run times need to be measured in "many hours" time frames not
> minutes. When you do memtest it has to be 12-24 hours to get more than a
> few full passes. Then you can be a little more sure its not bad memory.
We let memtest run the second time for 24 hours and 45 minutes. It reported
zero (0) errors. We figured that was long enough.
> > But at this point we're at a loss how to proceed. SuSE 9.3 worked just
> > fine as 32 bit but it's an installation disaster with the new 64 bit
> > components.
> >
> > We were surprised that changing the video card made no difference (from
> > GeForce FX6600 PCI-e to FX5500 PCI).
> >
> > On every install all of the hardware is recognized by name and chipset
> > except the Mistubishi monitor which is identified as "VESA" and the
> > Happauge Win TV 350PVR card which we have to manually identify.
>
> Have you pulled the WinTV 350PVR just to make sure it isn't the problem?
> Plug in that ratty old 15" monitor also while you are at it.
The WinTV 350 PVR was not connected to anything -- it was just installed in
the pooter. We can pull it and see what happens.
We can also try an old monitor and see what happens.
I think we'll try the old, smaller monitor first since that's an easier swap.
> > Someone in #SuSE Freenode mentioned a KDE bug that supposedly affects
> > large monitors (ours is 22"). And supposedly SuSE 10.0 will install
> > without these problems. Still, until SuSE 10.0 gets here we have a
> > non-functioning system. We can only hope that SuSE 10.0 does work.
> >
> > Any other ideas?
> Have you tried a different hard drive since there was mention of possible
> issues with >200GB drives? Grab a 4GB or larger IDE drive that you have
> just laying around and try it.
OK, we can try that, too. I think we have a 20 GB IDE drive lying around.
> Are you sure you have the latest BIOS updates for the mainboard? You did
> the Failsafe Install Mode so I'd say there is a compatibility problem with
> 64bit and the hardware. Trying PCI vs PCIe video, various filesystems,
> 32bit works, etc is quickly ruling out a lot of troubleshooting paths.
Well, 32 bit worked with the previous MB and processor -- they were 32 bit.
We have no idea if 32 bit will work with this set up.
I spoke with the technician who pulled the Athlon processor off the returned
Gigabyte board and installed in on this new MSI board, and he said it
absolutely has the latest BIOS -- that we should not need to update it at
this point. This is what he told me... :o)
> IF you find that any one of these ideas is the culprit, then we can rebuild
> the machine one piece at a time back to the way you really want it to be.
> Otherwise stick to 32bit until SUSE 10.0 arrives and try that. If 10.0
> 64bit doesn't work either, then we'll still have to do all those individual
> steps to find the problem.
Stick to 32 bit? How? When my wife puts the CDs in the player rather than
the DVD it says something like "Nice computer! Why are you trying to install
32 bit?"
Is there a way to force 32 bit install with Athlon 64? Should we try that?
Thanks. Gil and Judith
-- Check the headers for your unsubscription address For additional commands send e-mail to suse-linux-e-help@suse.com Also check the archives at http://lists.suse.com Please read the FAQs: suse-linux-e-faq@suse.com
- Previous message: Jerry Westrick: "Re: [SLE] Help with disk integrity and RAID-1 please"
- In reply to: Stan Glasoe: "Re: [SLE] Unable to complete install of 9.3 (Athlon 64 bit)"
- Next in thread: Stan Glasoe: "Re: [SLE] Unable to complete install of 9.3 (Athlon 64 bit)"
- Reply: Stan Glasoe: "Re: [SLE] Unable to complete install of 9.3 (Athlon 64 bit)"
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Relevant Pages
|