LinuxQuestions.org
Help answer threads with 0 replies.
Go Back   LinuxQuestions.org > Forums > Linux Forums > Linux - Hardware
User Name
Password
Linux - Hardware This forum is for Hardware issues.
Having trouble installing a piece of hardware? Want to know if that peripheral is compatible with Linux?

Notices

Reply
 
Search this Thread
Old 09-16-2002, 03:06 PM   #1
Harpune
Member
 
Registered: Sep 2002
Location: Seattle, WA
Distribution: Ubuntu
Posts: 101

Rep: Reputation: 15
Arrow hda fails to respond to partition check


I want to install Redhat 7.3 on to a computer i built. when the kernel is loading and it gets to the partition check, hda fails to respond giving a dma timeout error. this happens with redhat 7.3, 7.2 and mandrake 8.0.

I have an old version of storm linux 2000 which works fine, windows will install fine, as well. what could be the problem and how can i get around this error or fix it?

Last edited by Harpune; 09-16-2002 at 03:10 PM.
 
Old 09-16-2002, 06:53 PM   #2
born4linux
Senior Member
 
Registered: Sep 2002
Location: Philippines
Distribution: Slackware, RHEL&variants, AIX, SuSE
Posts: 1,127

Rep: Reputation: 49
pass this parameter at the installation boot prompt:

hda=nodma

See if this will work.
 
Old 09-16-2002, 08:10 PM   #3
Harpune
Member
 
Registered: Sep 2002
Location: Seattle, WA
Distribution: Ubuntu
Posts: 101

Original Poster
Rep: Reputation: 15
Thanks for the help, that parameter didn't seem to work but it think that the answer may lie in something like that. where can i go to find a list of possible boot parameters?

storm linux, i think, automatically disabled dma to get past the stall, would there be any way to do that manually?
 
Old 09-16-2002, 09:21 PM   #4
Harpune
Member
 
Registered: Sep 2002
Location: Seattle, WA
Distribution: Ubuntu
Posts: 101

Original Poster
Rep: Reputation: 15
i passed a hda=noprobe param to the kernel when i booted, it got me into the setup program but it tells me i need to manually choose hard disk drivers. the next window only has options for SCSI and network cards, though. maybe i am missing something here...
 
Old 09-17-2002, 11:09 AM   #5
mrGee
Member
 
Registered: Dec 2001
Location: Netherlands
Distribution: redhat suse mandrake freebsd
Posts: 344

Rep: Reputation: 30
hi
For all those boot prompt options check;
http://www.tldp.org/HOWTO/BootPrompt-HOWTO.html
Dunno which one might do the trick, maybe passing
the right cyl/head/sector layout for your disk does it.
good luck

hda=noprobe will skip your hda disk, i use it and the
hdb=noprobe to speed up booting cause i use
hde on a promise controler.


Last edited by mrGee; 09-17-2002 at 11:12 AM.
 
Old 09-19-2002, 04:59 PM   #6
mm_2k
LQ Newbie
 
Registered: Sep 2002
Distribution: Redhat (hopefully)
Posts: 4

Rep: Reputation: 0
so, which of those parameters should be used.

"hdx=noprobe" : drive may be present, but do not probe for it
"hdx=none" : drive is NOT present, ignore cmos and do not probe
"hdx=nowerr" : ignore the WRERR_STAT bit on this drive
"hdx=cdrom" : drive is present, and is a cdrom drive
"hdx=cyl,head,sect" : disk drive is present, with specified geometry
"hdx=autotune" : driver will attempt to tune interface speed
to the fastest PIO mode supported,
if possible for this drive only.
Not fully supported by all chipset types,
and quite likely to cause trouble with
older/odd IDE drives.

"idex=noprobe" : do not attempt to access/use this interface
"idex=base" : probe for an interface at the addr specified,
where "base" is usually 0x1f0 or 0x170
and "ctl" is assumed to be "base"+0x206
"idex=base,ctl" : specify both base and ctl
"idex=base,ctl,irq" : specify base, ctl, and irq number
"idex=autotune" : driver will attempt to tune interface speed
to the fastest PIO mode supported,
for all drives on this interface.
Not fully supported by all chipset types,
and quite likely to cause trouble with
older/odd IDE drives.
"idex=noautotune" : driver will NOT attempt to tune interface speed
This is the default for most chipsets,
except the cmd640.
"idex=serialize" : do not overlap operations on idex and ide(x^1)


- none of which stand out to me as one that will make it work.
 
Old 09-19-2002, 06:42 PM   #7
mrGee
Member
 
Registered: Dec 2001
Location: Netherlands
Distribution: redhat suse mandrake freebsd
Posts: 344

Rep: Reputation: 30
i did a few searches on this, the most useful thing to do
was; ide=nodma (instead of hda=nodma)
Some of these problems were related to the controller; like
some ata100's or raid controller. Need to feed the right
adresses with; ide2=adress1, adress2+2 ide3=adress3, addres4+2 (cat /proc/pci provides these adresses, boot
from floppy based linux or so)
And some were related to the kernel; Harpune got it running
with storm linux 2000 that probably uses an older kernel.
A search in this forum also brings up some other things like
simply formatting the drive before install.
Hope some of this fits
 
Old 09-20-2002, 06:48 AM   #8
mm_2k
LQ Newbie
 
Registered: Sep 2002
Distribution: Redhat (hopefully)
Posts: 4

Rep: Reputation: 0
ok, thanks

i will try it out and post again if i need more advice!

matt
 
Old 09-20-2002, 02:14 PM   #9
mm_2k
LQ Newbie
 
Registered: Sep 2002
Distribution: Redhat (hopefully)
Posts: 4

Rep: Reputation: 0
ok, i tried linux hda=nodma ide=nodma nodma as boot parameters.

I saw this on redhat.com's question/answery thing - not sure how efficient it is but it seemed to work and i've now installed redhat and can still boot into w2k - only problem now is it automatically boots into windows, when id really like it to ask me which to boot into.

at the moment to boot rh i use my boot floppy disk

i guess ive done something wrong in the install with partitions or something, or not specified something which i should have.
 
Old 09-20-2002, 02:44 PM   #10
mrGee
Member
 
Registered: Dec 2001
Location: Netherlands
Distribution: redhat suse mandrake freebsd
Posts: 344

Rep: Reputation: 30
mm_2 ok, try this
Boot into linux using your flop.
less /etc/fstab and see where your / is

vi /etc/lilo.conf ( or use another editor)
my entry for linux;

image=/boot/vmlinuz
label=linux
root=/dev/hde7
initrd=/boot/initrd.img
append="quiet mem=nopentium hda=noprobe hdb=noprobe devfs=mount hdd=ide-scsi"
vga=788
read-only

fill in your own root=/dev/hdX
and use the proper append=" ide=nodma "
save it
rerun lilo
see if it adds both entries linux and windows
reboot
should work, do a man lilo.conf for timeout, etc etc
and do you have to use all the nodma boot paramaters ?
regards
 
  


Reply


Thread Tools Search this Thread
Search this Thread:

Advanced Search

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

BB code is On
Smilies are On
[IMG] code is Off
HTML code is Off


Similar Threads
Thread Thread Starter Forum Replies Last Post
partition check: hda:lost interrupt Rkim1 Linux - Newbie 2 04-19-2004 01:21 PM
partition check fails on almost all distros versaulis Linux - Laptop and Netbook 5 02-09-2004 06:44 PM
Keyboard fails or respond eraticly jimsteven Linux - Newbie 1 04-24-2003 12:33 PM
Suse 8.0 prof: having hda: partition check leshka_uk Linux - Hardware 1 11-24-2002 05:31 AM
hda: partition check grunf99 Linux - General 2 09-20-2002 03:04 PM


All times are GMT -5. The time now is 03:47 PM.

Main Menu
My LQ
Write for LQ
LinuxQuestions.org is looking for people interested in writing Editorials, Articles, Reviews, and more. If you'd like to contribute content, let us know.
Main Menu
Syndicate
RSS1  Latest Threads
RSS1  LQ News
Twitter: @linuxquestions
identi.ca: @linuxquestions
Facebook: linuxquestions Google+: linuxquestions
Open Source Consulting | Domain Registration