screwed 8.0 install -- help?
this is *really* fun . . . . . my sister just got a new, empty machine, p-4 2-gig with 256 megs and a 40-meg maxtor drive. she got it so that she could install linux, and the linux she chose was suse 8.0 pro. the cd boots and she makes it as far as "probing hard disks" and there it sits, during which time the floppy light is on as well. she has phoned me for help. i am 1,000 miles away. and i cannot figure out what in the world would be causing the machine to hang. ideas? i saw in the support database that 7.3 had a problem with new maxtor drives, but nothing about 8.0; also, i do not know that the drive, a diamondmax plus D740X, is among those affected. -- dep http://www.linuxandmain.com -- outside the box, barely within the envelope, and no animated paperclip anywhere.
On Thu, Jul 18, 2002 at 09:31:06PM -0400, dep wrote:
this is *really* fun . . . . .
my sister just got a new, empty machine, p-4 2-gig with 256 megs and a 40-meg maxtor drive. she got it so that she could install linux, and the linux she chose was suse 8.0 pro. the cd boots and she makes it as far as "probing hard disks" and there it sits, during which time the floppy light is on as well. she has phoned me for help. i am 1,000 miles away. and i cannot figure out what in the world would be causing the machine to hang.
ideas? i saw in the support database that 7.3 had a problem with new maxtor drives, but nothing about 8.0; also, i do not know that the drive, a diamondmax plus D740X, is among those affected.
I can't tell where the problem might be in your sister's machine but I can confirm that maxtor D740X 80 GB drive works with SuSE 8.0 with no problems. An IBM SCSI disk failed for me in my aged Compaq Deskpro 6000 (it's a P-II 266 MHz 128 MB RAM box). I threw in an 80 GB IDE Maxtor and performed a new install of SuSE 8.0 Pro. BIOS reports some disk error on POST and asks me to hit F1 to boot. After that system boots and works as a charm. Regards, -Kastus
Ya, I had troubles with the maxtor hdd as well. Try the failsafe install and then after it boots try a regular boot. I also found that partitioning it was quirky as well. But, as I said, went for the failsafe and then boot the regular after the install was finished. Oh, and I also found the turning on the idedma module for the newer maxtor caused it to stall on boot. My older maxtor doesn't have these issues. It's a ata66. The newer maxtor is an ide133 and I'm guessing therein is the problem. HTH, Curtis dep wrote:
this is *really* fun . . . . .
my sister just got a new, empty machine, p-4 2-gig with 256 megs and a 40-meg maxtor drive. she got it so that she could install linux, and the linux she chose was suse 8.0 pro. the cd boots and she makes it as far as "probing hard disks" and there it sits, during which time the floppy light is on as well. she has phoned me for help. i am 1,000 miles away. and i cannot figure out what in the world would be causing the machine to hang.
ideas? i saw in the support database that 7.3 had a problem with new maxtor drives, but nothing about 8.0; also, i do not know that the drive, a diamondmax plus D740X, is among those affected.
dep
my sister just got a new, empty machine, p-4 2-gig with 256 megs and a
It could be the P4. If it's the one with the ht (hyper threading) flag set, YaST2 mistakenly thinks it's a SMP machine and chooses the SMP kernel. Search the SuSE support database because I'm quite sure there's an article dealing with that problem. But hast your sister tried booting in fail safe mode? Philipp -- Philipp Thomas work: pthomas@suse.de Development SuSE Linux AG private: philippt@t-online.de
begin Philipp Thomas's quote: | It could be the P4. If it's the one with the ht (hyper threading) | flag set, YaST2 mistakenly thinks it's a SMP machine and chooses | the SMP kernel. Search the SuSE support database because I'm quite | sure there's an article dealing with that problem. | | But hast your sister tried booting in fail safe mode? she's tried failsafe; she took back the maxtor and got a western digital; she's disabled udma in the bios -- and no matter what she does, it hangs on probing the hard drive. i do not know what she has decided, but i suspect what she has decided is that linux is not for her. saddens me, but she was actually angry at me over it, for having suggested linux. -- dep http://www.linuxandmain.com -- outside the box, barely within the envelope, and no animated paperclip anywhere.
On Sat, Jul 20, 2002 at 05:54:40PM -0400, dep wrote:
begin Philipp Thomas's quote:
| It could be the P4. If it's the one with the ht (hyper threading) | flag set, YaST2 mistakenly thinks it's a SMP machine and chooses | the SMP kernel. Search the SuSE support database because I'm quite | sure there's an article dealing with that problem. | | But hast your sister tried booting in fail safe mode?
she's tried failsafe; she took back the maxtor and got a western digital; she's disabled udma in the bios -- and no matter what she does, it hangs on probing the hard drive.
Faulty controller? Cable? Which mobo?
i do not know what she has decided, but i suspect what she has decided is that linux is not for her. saddens me, but she was actually angry at me over it, for having suggested linux.
Unfortunate as it is, this being her first impression and all, I'm leaning towards hw-error. 'Cause if it's not the drive(s), and not the OS, then... One of the things I'd do, would be to get the drive partitioned some other way, to see if that helped. *I* would get stubborn about it, but then, that's me and I'm already 'converted' :) Of course, if it *were* me I'd know the exact combination of hw, and I could research any issues there might be. Sorry to not be able to give a 'one-liner' solution, but if she's given up on the idea already, I guess it wouldn't matter much anyway. kind regards, Jon Clausen
begin Jon Clausen's quote: | Faulty controller? | Cable? | | Which mobo? it's an asus p4b533; there was brief mention of it on the kernel mailing list. | Unfortunate as it is, this being her first impression and all, I'm | leaning towards hw-error. 'Cause if it's not the drive(s), and not | the OS, then... i agree. problem is, she's a physician and mother and has neither time nor inclination to go chasing around all that much replacing things so that an operating system her brother recommends will merely install. problem was exacerbated when she popped in a windows cd and it installed uneventfully. which means that her first impression will most likely also be her last impression, and should the subject ever arise i'm sure she'll describe her hellish day with linux. very sad, but i do not know much of a way of countering her decision. linux is more secure? "well, yes, if it doesn't even install and therefore the drive is blank, it's certainly secure." linux doesn't suffer from the kinds of infections that have plagued your windows use. "right. linux doesn't need a virus to make it stop working -- it does it on its own." and so on. i'm sure if i'd been there instead of 1,000 miles away, i'd have been able to come up with a way of solving the problem. but it does make you wonder how many such experiences there are out there that we*don't* know about. -- dep http://www.linuxandmain.com -- outside the box, barely within the envelope, and no animated paperclip anywhere.
On Monday 22 July 2002 00:51, dep wrote:
Which mobo?
it's an asus p4b533; there was brief mention of it on the kernel mailing list.
hi there, I think that your problem may lies in the ICH4. I have a intel i845BGV motherboard that have a i845G + ICH4, your sisters motherboard has i845E + ICH4. I have a problem with the ICH4, that make me can't turn on the DMA, and make the SuSE sluggish. (I upgraded the mobo from Asus CUSL2... So, I install 8.0 in the CUSL2 a long time ago, and change to this new mobo, I don't know will it successed or failed if I install SuSE with this new mobo dirrectly). I have do some research here and there, and the ICH4 support in Linux will be available in kernel 2.4.19. Currently the 2.4.19 has reach the rc3 (release candidate) tag.
Greeting's everyone. My problem: I'm using SuSE 8 Pro on a bunch of machines, today I have purchaced the SuSE Linux Pro-Office CD and failed in all of my attempts to instal it onto any of my SuSE 8.0 systems. I followed the directions (mounted CD, used YaST2's "Patch CD Update" utility) and the following message was consistently returned in a dialogue box. ---snip--- Cannot access the patch descriptions. Insert the SuSE patch CD and restart the "Patch CD Update". | OK | ---snip--- Every time I do so, I am met with the same message, and nothing happens. My system is well patched and up to date via YOU. Any advice would be most welcome. Yours sincerely, Marcel Lecker
Try not mounting the CD. Just put the patch cd in and then run YaST2. On Sat, 2002-07-27 at 08:56, Marcel Lecker wrote:
Greeting's everyone.
My problem: I'm using SuSE 8 Pro on a bunch of machines, today I have purchaced the SuSE Linux Pro-Office CD and failed in all of my attempts to instal it onto any of my SuSE 8.0 systems.
I followed the directions (mounted CD, used YaST2's "Patch CD Update" utility) and the following message was consistently returned in a dialogue box.
---snip---
Cannot access the patch descriptions. Insert the SuSE patch CD and restart the "Patch CD Update".
| OK |
---snip---
Every time I do so, I am met with the same message, and nothing happens. My system is well patched and up to date via YOU.
Any advice would be most welcome.
Yours sincerely,
Marcel Lecker
-- 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
No change, same result and message. On Sat, 2002-07-27 at 10:57, Robert Schwedler wrote:
Try not mounting the CD. Just put the patch cd in and then run YaST2.
On Sat, 2002-07-27 at 08:56, Marcel Lecker wrote:
Greeting's everyone.
My problem: I'm using SuSE 8 Pro on a bunch of machines, today I have purchaced the SuSE Linux Pro-Office CD and failed in all of my attempts to instal it onto any of my SuSE 8.0 systems.
I followed the directions (mounted CD, used YaST2's "Patch CD Update" utility) and the following message was consistently returned in a dialogue box.
---snip---
Cannot access the patch descriptions. Insert the SuSE patch CD and restart the "Patch CD Update".
| OK |
---snip---
Every time I do so, I am met with the same message, and nothing happens. My system is well patched and up to date via YOU.
Any advice would be most welcome.
Yours sincerely,
Marcel Lecker
-- 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
-- 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
** Reply to message from Marcel Lecker
participants (9)
-
Curtis Rey -
dep -
jfweber＠eternal.net -
Jon Clausen -
Konstantin (Kastus) Shchuka -
Marcel Lecker -
Mojojojo -
Philipp Thomas -
Robert Schwedler