Redhat 6.2
XF86 3.3.3.1
3DImage 975
Set resolution to 1024x768 for 8,16,24
Halted
The power on ROM code no longer sees my 3.1Gb IDE drive.
Is this a coincidence, or did I somehow kill it?
Ed
by ekaulak » Tue, 27 Jul 1999 04:00:00
The power on ROM code no longer sees my 3.1Gb IDE drive.
Is this a coincidence, or did I somehow kill it?
Ed
by Abdullah Ramazanogl » Wed, 28 Jul 1999 04:00:00
> Redhat 6.2
> XF86 3.3.3.1
> 3DImage 975
> Set resolution to 1024x768 for 8,16,24
> Halted
> The power on ROM code no longer sees my 3.1Gb IDE drive.
> Is this a coincidence, or did I somehow kill it?
> Ed
Try booting from floppy and use your IDE root partition to see if IDE an
Linux on it works. If unsuccessful, try booting from floppy using boot
and rescue disks (you can find a generic boot and rescue disk images at
CD). Then mount your root partition (e.g. mount /dev/hda5 /mnt) and see
whether disk is working.
--
Abdullah Ramazanoglu ( aramazanoglu AT demirbank DOT com DOT tr )
by John Patrick Kru » Wed, 28 Jul 1999 04:00:00
> The power on ROM code no longer sees my 3.1Gb IDE drive.
> Is this a coincidence, or did I somehow kill it?
> Ed
HaveAGoodLife * * * * * * * ResistanceIsFutile
* * * * * * * * * * * * * -jpk- * * * * * * * * * * * * *
by David » Wed, 28 Jul 1999 04:00:00
> Redhat 6.2
> XF86 3.3.3.1
> 3DImage 975
> Set resolution to 1024x768 for 8,16,24
> Halted
> The power on ROM code no longer sees my 3.1Gb IDE drive.
> Is this a coincidence, or did I somehow kill it?
I assume you've actually powered the system down and haven't just been
trying to reboot/reset it, right?
Check your CMOS and make sure it has the correct drive parameters. If
it doesn't have an auto-detect mode (or if that's not working) try
entering (or re-entering) the drive's geometry values. They are usually
printed on the drive's cover.
-- David
by Urba » Tue, 03 Aug 1999 04:00:00
>> Redhat 6.2
>> XF86 3.3.3.1
>> 3DImage 975
>> Set resolution to 1024x768 for 8,16,24
>> Halted
>> The power on ROM code no longer sees my 3.1Gb IDE drive.
>> Is this a coincidence, or did I somehow kill it?
>> Ed
>If the disk is not being detected by BIOS at all, then it should be a
>coincidence. If it sees the disk but couldn't find a MBR (boot: prompt)
>then either disk is dead (coincidence), or you have changed disk mode
>(Normal/LBA/Large), or swiped out MBR from within Linux. All have no
>relation to X configuration AFAIK. Do you have (or tried to install)
>other OS on the same disk?
>Try booting from floppy and use your IDE root partition to see if IDE an
>Linux on it works. If unsuccessful, try booting from floppy using boot
>and rescue disks (you can find a generic boot and rescue disk images at
>CD). Then mount your root partition (e.g. mount /dev/hda5 /mnt) and see
>whether disk is working.
-Greg
1. Async on AIX 3.2 on 220 DEAD, DEAD, DEAD!!!
Dead, as in braindead. I have applied several pathces that came from IBM
defect support to fix various cu and uucp problems and slip problems. Now,
guess what happens - every other way of accessing tty's is dead. Including
gettys's and ate. The specific PIF# was U402532 - did that patch break
anyone else's ate??? Please tell me.... I can't get my slip line up because
that patch seems to have broke my ATE access to my RS6K at work - due to
another bug in slattach (the one that causes multiple slip interfaces to
RANDOMLY attach to a tty assigned for slip - otherwise known as, it picks
a slip interface randomly and if it is the wrong one, the mahcine just
discards all pakcets). Basically, I get a modem carrier (via audio) and
then it just dies andhangs up the phone. CU also does the same thing with
a "rec'd carrier lost" or "dead" or something like that. I am only now able
to get on to post news via my ancient Sun 3/60. The only reliable machine
I have ever owned. Myabe I'll just buy a Sparc...IBM, are you listening...
I think not. YES - THIS IS A FLAME!!!!!!!!!!!!!!!!!!!
I'M SICK OF THIS!!!!!!!
SLIP dies after 12 to 24 hours....depending upon how much data you send
Async dies after 5 minutes at high bps
Pathces kill things that worked before....You know the story.
Please, someone, help me. This is getting crazy. My SE is probably being
driven insane by my 1:00AM calls on Sundays or Saturdays (not that I'd spare
him to fix my problem...but I wan't it fixed!!!!)
Is there anyone from IBM here on the net?????? That can help?????
Has anyone on this group signed off on IBM and gone to Sun? I would like to
hear from you. Maybe then I can convince my management that that is what
we should do as well. It may not be a bad idea. (As my Sun 3/60 is the
only reliable machine I've got at home now. Or at work, for that matter!)
-Nathan Lane
Trico Title Company, Santa Barbar, CA
3. dead.letter will not go to directory specified in DEAD variable AIX4.3
6. Solaris 8 kernel tuning: seminfo_semmnu?
7. dead mem pages -> dead machines
8. How do I instale with 'make'?
9. ide problem - is this a known problem, or is the disk dead?
11. IDE problems ? or just a dead disk ?
12. 2.5.25 dead kbd and gpm oops (my config error ?)
13. Replacing a dead IDE cdrom on the blade 100?