CDR drive installation - now HD and cdrom problems
Hello everyone, I have successfully installed an older HP CDR drive (7200-i) on my SuSE 7.3 pro box. A few hiccups, but it is now running just fine. I ahve not burned anything yet because I want to resolve my new issues first. Now, when I reboot I get errors with my harddisk (hda). The errors showed up immediately after I connected my CDR drive and turne the box back on. The original configuration was: hda - hard disk hdb - nothing hdc - hard disk hdd - cdrom drive This worked just fine. The new configuration is: hda - hard disk hdb - HP CDR/W drive hdc - hard disk hdd - cdrom drive The errors I am getting are: <4>hda: dma_intr: status=0x51 { DriveReady SeekComplete Error } <4>hda: dma_intr: error=0x84 { DriveStatusError BadCRC } <4>hda: dma_intr: status=0x51 { DriveReady SeekComplete Error } <4>hda: dma_intr: error=0x84 { DriveStatusError BadCRC } <4>hda: dma_intr: status=0x51 { DriveReady SeekComplete Error } <4>hda: dma_intr: error=0x84 { DriveStatusError BadCRC } <4>hda: dma_intr: status=0x51 { DriveReady SeekComplete Error } <4>hda: dma_intr: error=0x84 { DriveStatusError BadCRC } <4>hda: dma_intr: status=0x51 { DriveReady SeekComplete Error } <4>hda: dma_intr: error=0x84 { DriveStatusError BadCRC } <4>blk: queue c02f4900, I/O limit 4095Mb (mask 0xffffffff) <4>hdb: DMA disabled <4>ide0: reset: success <4>hda: dma_intr: status=0x51 { DriveReady SeekComplete Error } <4>hda: dma_intr: error=0x84 { DriveStatusError BadCRC } <4>hda: dma_intr: status=0x51 { DriveReady SeekComplete Error } <4>hda: dma_intr: error=0x84 { DriveStatusError BadCRC } <4>hda: dma_intr: status=0x51 { DriveReady SeekComplete Error } <4>hda: dma_intr: error=0x84 { DriveStatusError BadCRC } <4>hda: dma_intr: status=0x51 { DriveReady SeekComplete Error } <4>hda: dma_intr: error=0x84 { DriveStatusError BadCRC } <4>hda: dma_intr: status=0x51 { DriveReady SeekComplete Error } <4>hda: dma_intr: error=0x84 { DriveStatusError BadCRC } <4>hda: dma_intr: status=0x51 { DriveReady SeekComplete Error } <4>hda: dma_intr: error=0x84 { DriveStatusError BadCRC } <4>hda: dma_intr: status=0x53 { DriveReady SeekComplete Index Error } <4>hda: dma_intr: error=0x84 { DriveStatusError BadCRC } <4>ide0: reset: success later: <4> ide0: BM-DMA at 0xffa0-0xffa7, BIOS settings: hda:DMA, hdb:DMA <4> ide1: BM-DMA at 0xffa8-0xffaf, BIOS settings: hdc:DMA, hdd:DMA <4>hda: WDC WD300BB-00AUA1, ATA DISK drive <4>hdb: HP CD-Writer+ 7200, ATAPI CD/DVD-ROM drive <4>hdc: Maxtor 90840D6, ATA DISK drive <4>hdd: MATSHITA CR-585, ATAPI CD/DVD-ROM drive <4>ide0 at 0x1f0-0x1f7,0x3f6 on irq 14 <4>ide1 at 0x170-0x177,0x376 on irq 15 <4>blk: queue c02f4900, I/O limit 4095Mb (mask 0xffffffff) <6>hda: 58633344 sectors (30020 MB) w/2048KiB Cache, CHS=3649/255/63, UDMA (100) <4>blk: queue c02f4c1c, I/O limit 4095Mb (mask 0xffffffff) <6>hdc: 16406208 sectors (8400 MB) w/256KiB Cache, CHS=16276/16/63, UDMA(33) <4>hdd: ATAPI 24X CD-ROM drive, 128kB Cache, DMA <6>Uniform CD-ROM driver Revision: 3.12 I added the line in lilo.conf to append: hdb=ide-scsi (but the errors were happening before I did this). ALSO, i cannot mount my original cdrom drive. At the root directory where i have the cdrom directory, I used to be able to do mount cdrom and then access the drive. Now when I try, it gives me an error 'you must specify the filesystem type'. When I specify auto for the file system type it gives me the error message 'cdrom is not a block device'. Does anyone know what I can do to resolve this? Thanks, Jim
-----BEGIN PGP SIGNED MESSAGE----- Check your IDE Cables and make sure they are in there tight. I had that problem when I added another CDROM and fixed it by pulling the cable off and re-attaching them. Robert K Davies Textbox Networks Administrator ~Phantasm http://www.textbox.net ********************************************************************** This post is encrypted in the "english language method", any attempt to decipher meaning from these symbols is a violation of the DMCA. This includes, but is not limited to: interpreting the symbols through use of biological, visual decryption devices, translating the symbols into another language encryption scheme, and digital processing the symbols into a form conducive to oral intrepretation. Thank you for your time. ********************************************************************** On Thu, 27 Dec 2001, James Bliss wrote:
Hello everyone,
I have successfully installed an older HP CDR drive (7200-i) on my SuSE 7.3 pro box. A few hiccups, but it is now running just fine. I ahve not burned anything yet because I want to resolve my new issues first.
Now, when I reboot I get errors with my harddisk (hda). The errors showed up immediately after I connected my CDR drive and turne the box back on. The original configuration was:
hda - hard disk hdb - nothing hdc - hard disk hdd - cdrom drive
This worked just fine. The new configuration is:
hda - hard disk hdb - HP CDR/W drive hdc - hard disk hdd - cdrom drive
The errors I am getting are:
<4>hda: dma_intr: status=0x51 { DriveReady SeekComplete Error } <4>hda: dma_intr: error=0x84 { DriveStatusError BadCRC } <4>hda: dma_intr: status=0x51 { DriveReady SeekComplete Error } <4>hda: dma_intr: error=0x84 { DriveStatusError BadCRC } <4>hda: dma_intr: status=0x51 { DriveReady SeekComplete Error } <4>hda: dma_intr: error=0x84 { DriveStatusError BadCRC } <4>hda: dma_intr: status=0x51 { DriveReady SeekComplete Error } <4>hda: dma_intr: error=0x84 { DriveStatusError BadCRC } <4>hda: dma_intr: status=0x51 { DriveReady SeekComplete Error } <4>hda: dma_intr: error=0x84 { DriveStatusError BadCRC } <4>blk: queue c02f4900, I/O limit 4095Mb (mask 0xffffffff) <4>hdb: DMA disabled <4>ide0: reset: success <4>hda: dma_intr: status=0x51 { DriveReady SeekComplete Error } <4>hda: dma_intr: error=0x84 { DriveStatusError BadCRC } <4>hda: dma_intr: status=0x51 { DriveReady SeekComplete Error } <4>hda: dma_intr: error=0x84 { DriveStatusError BadCRC } <4>hda: dma_intr: status=0x51 { DriveReady SeekComplete Error } <4>hda: dma_intr: error=0x84 { DriveStatusError BadCRC } <4>hda: dma_intr: status=0x51 { DriveReady SeekComplete Error } <4>hda: dma_intr: error=0x84 { DriveStatusError BadCRC } <4>hda: dma_intr: status=0x51 { DriveReady SeekComplete Error } <4>hda: dma_intr: error=0x84 { DriveStatusError BadCRC } <4>hda: dma_intr: status=0x51 { DriveReady SeekComplete Error } <4>hda: dma_intr: error=0x84 { DriveStatusError BadCRC } <4>hda: dma_intr: status=0x53 { DriveReady SeekComplete Index Error } <4>hda: dma_intr: error=0x84 { DriveStatusError BadCRC } <4>ide0: reset: success
later:
<4> ide0: BM-DMA at 0xffa0-0xffa7, BIOS settings: hda:DMA, hdb:DMA <4> ide1: BM-DMA at 0xffa8-0xffaf, BIOS settings: hdc:DMA, hdd:DMA <4>hda: WDC WD300BB-00AUA1, ATA DISK drive <4>hdb: HP CD-Writer+ 7200, ATAPI CD/DVD-ROM drive <4>hdc: Maxtor 90840D6, ATA DISK drive <4>hdd: MATSHITA CR-585, ATAPI CD/DVD-ROM drive <4>ide0 at 0x1f0-0x1f7,0x3f6 on irq 14 <4>ide1 at 0x170-0x177,0x376 on irq 15 <4>blk: queue c02f4900, I/O limit 4095Mb (mask 0xffffffff) <6>hda: 58633344 sectors (30020 MB) w/2048KiB Cache, CHS=3649/255/63, UDMA (100) <4>blk: queue c02f4c1c, I/O limit 4095Mb (mask 0xffffffff) <6>hdc: 16406208 sectors (8400 MB) w/256KiB Cache, CHS=16276/16/63, UDMA(33) <4>hdd: ATAPI 24X CD-ROM drive, 128kB Cache, DMA <6>Uniform CD-ROM driver Revision: 3.12
I added the line in lilo.conf to append: hdb=ide-scsi (but the errors were happening before I did this).
ALSO, i cannot mount my original cdrom drive. At the root directory where i have the cdrom directory, I used to be able to do mount cdrom and then access the drive. Now when I try, it gives me an error 'you must specify the filesystem type'. When I specify auto for the file system type it gives me the error message 'cdrom is not a block device'.
Does anyone know what I can do to resolve this?
Thanks,
Jim
-- To unsubscribe send e-mail to suse-linux-e-unsubscribe@suse.com For additional commands send e-mail to suse-linux-e-help@suse.com Also check the FAQ at http://www.suse.com/support/faq and the archives at http://lists.suse.com
-----BEGIN PGP SIGNATURE----- Version: PGP 6.5.8 Comment: Made with pgp4pine 1.75-6 iQEVAwUBPCrN77zz1EMmEs4tAQGV/Af8CJlPbzDM1sgW3MCXD0+4+SqU+4c5rN7k wGSanBKKzryJQ50Z047SKIs1wi4CGagMHnodkfxwM8TluJgY0bo9Dx5eaYomn4X3 g3C3NDcge9pR3C6JqkppUBKhIg+rGU6NDia2XjAJcYcF6DTyDs1BYr8yTWaaV0+4 JUd/3CLogr/nAQuXrS0590Pnyeii8g9M6SepR6bBih+i/dm8FJufOyuXbbfygRpp ybyMnZjTwRYWWLbMuGbC63/dxLygxaIBDM+O03iXwJA13FQiSvikegrYfk4MUukn hyDTY/hDTh3hC70UkNjsf822HU0HNAK6gwkKt8NKUbDzKSnFr0piEA== =Bqmm -----END PGP SIGNATURE-----
I resolved the cdrmo problem. The symbolic link in /dev for cdrom was pointing to hdb
(what is now the CDR drive). I assume that this is pointing here because the original
config did not use hdb at all (although I thought this was cable based, not device
connected based). So, when I deleted and readded the link with it pointing to hdd the
mount works. (Sorry, I should have checked this before my first email).
I pulled and re-sat all of the drive cables and the errors continue.
The DMA errors still occur. I went into my bios and attempted to turn off DMA, Ultra DMA
was disabled and there was no way to turn off DMA (this is a relatively new Intel board
with a PIII 933 chip). But, other than the errors, I have no problems accessing any of my
drives or the original CDrom drive.
Thanks for the suggestions. I will continue to hunt on this, I found a lot of links regarding
this by searching Google.
I will let everyone know if I resolve this problem.
Jim
12/27/01 01:29:48 AM, Phantasm
-----BEGIN PGP SIGNED MESSAGE-----
Check your IDE Cables and make sure they are in there tight. I had that problem when I added another CDROM and fixed it by pulling the cable off and re-attaching them.
Robert K Davies Textbox Networks Administrator ~Phantasm http://www.textbox.net
********************************************************************** This post is encrypted in the "english language method", any attempt to decipher meaning from these symbols is a violation of the DMCA. This includes, but is not limited to: interpreting the symbols through use of biological, visual decryption devices, translating the symbols into another language encryption scheme, and digital processing the symbols into a form conducive to oral intrepretation. Thank you for your time. **********************************************************************
On Thu, 27 Dec 2001, James Bliss wrote:
Hello everyone,
I have successfully installed an older HP CDR drive (7200-i) on my SuSE 7.3 pro box. A few hiccups, but it is now running just fine. I ahve not burned anything yet because I want to resolve my new issues first.
Now, when I reboot I get errors with my harddisk (hda). The errors showed up immediately after I connected my CDR drive and turne the box back on. The original configuration was:
hda - hard disk hdb - nothing hdc - hard disk hdd - cdrom drive
This worked just fine. The new configuration is:
hda - hard disk hdb - HP CDR/W drive hdc - hard disk hdd - cdrom drive
The errors I am getting are:
<4>hda: dma_intr: status=0x51 { DriveReady SeekComplete Error } <4>hda: dma_intr: error=0x84 { DriveStatusError BadCRC } <4>hda: dma_intr: status=0x51 { DriveReady SeekComplete Error } <4>hda: dma_intr: error=0x84 { DriveStatusError BadCRC } <4>hda: dma_intr: status=0x51 { DriveReady SeekComplete Error } <4>hda: dma_intr: error=0x84 { DriveStatusError BadCRC } <4>hda: dma_intr: status=0x51 { DriveReady SeekComplete Error } <4>hda: dma_intr: error=0x84 { DriveStatusError BadCRC } <4>hda: dma_intr: status=0x51 { DriveReady SeekComplete Error } <4>hda: dma_intr: error=0x84 { DriveStatusError BadCRC } <4>blk: queue c02f4900, I/O limit 4095Mb (mask 0xffffffff) <4>hdb: DMA disabled <4>ide0: reset: success <4>hda: dma_intr: status=0x51 { DriveReady SeekComplete Error } <4>hda: dma_intr: error=0x84 { DriveStatusError BadCRC } <4>hda: dma_intr: status=0x51 { DriveReady SeekComplete Error } <4>hda: dma_intr: error=0x84 { DriveStatusError BadCRC } <4>hda: dma_intr: status=0x51 { DriveReady SeekComplete Error } <4>hda: dma_intr: error=0x84 { DriveStatusError BadCRC } <4>hda: dma_intr: status=0x51 { DriveReady SeekComplete Error } <4>hda: dma_intr: error=0x84 { DriveStatusError BadCRC } <4>hda: dma_intr: status=0x51 { DriveReady SeekComplete Error } <4>hda: dma_intr: error=0x84 { DriveStatusError BadCRC } <4>hda: dma_intr: status=0x51 { DriveReady SeekComplete Error } <4>hda: dma_intr: error=0x84 { DriveStatusError BadCRC } <4>hda: dma_intr: status=0x53 { DriveReady SeekComplete Index Error } <4>hda: dma_intr: error=0x84 { DriveStatusError BadCRC } <4>ide0: reset: success
later:
<4> ide0: BM-DMA at 0xffa0-0xffa7, BIOS settings: hda:DMA, hdb:DMA <4> ide1: BM-DMA at 0xffa8-0xffaf, BIOS settings: hdc:DMA, hdd:DMA <4>hda: WDC WD300BB-00AUA1, ATA DISK drive <4>hdb: HP CD-Writer+ 7200, ATAPI CD/DVD-ROM drive <4>hdc: Maxtor 90840D6, ATA DISK drive <4>hdd: MATSHITA CR-585, ATAPI CD/DVD-ROM drive <4>ide0 at 0x1f0-0x1f7,0x3f6 on irq 14 <4>ide1 at 0x170-0x177,0x376 on irq 15 <4>blk: queue c02f4900, I/O limit 4095Mb (mask 0xffffffff) <6>hda: 58633344 sectors (30020 MB) w/2048KiB Cache, CHS=3649/255/63, UDMA (100) <4>blk: queue c02f4c1c, I/O limit 4095Mb (mask 0xffffffff) <6>hdc: 16406208 sectors (8400 MB) w/256KiB Cache, CHS=16276/16/63, UDMA (33) <4>hdd: ATAPI 24X CD-ROM drive, 128kB Cache, DMA <6>Uniform CD-ROM driver Revision: 3.12
I added the line in lilo.conf to append: hdb=ide-scsi (but the errors were happening before I did this).
ALSO, i cannot mount my original cdrom drive. At the root directory where i have the cdrom directory, I used to be able to do mount cdrom and then access the drive. Now when I try, it gives me an error 'you must specify the filesystem type'. When I specify auto for the file system type it gives me the error message 'cdrom is not a block device'.
Does anyone know what I can do to resolve this?
Thanks,
Jim
-- To unsubscribe send e-mail to suse-linux-e-unsubscribe@suse.com For additional commands send e-mail to suse-linux-e-help@suse.com Also check the FAQ at http://www.suse.com/support/faq and the archives at http://lists.suse.com
-----BEGIN PGP SIGNATURE----- Version: PGP 6.5.8 Comment: Made with pgp4pine 1.75-6
iQEVAwUBPCrN77zz1EMmEs4tAQGV/Af8CJlPbzDM1sgW3MCXD0+4+SqU+4c5rN7k wGSanBKKzryJQ50Z047SKIs1wi4CGagMHnodkfxwM8TluJgY0bo9Dx5eaYomn4X3 g3C3NDcge9pR3C6JqkppUBKhIg+rGU6NDia2XjAJcYcF6DTyDs1BYr8yTWaaV0+4 JUd/3CLogr/nAQuXrS0590Pnyeii8g9M6SepR6bBih+i/dm8FJufOyuXbbfygRpp ybyMnZjTwRYWWLbMuGbC63/dxLygxaIBDM+O03iXwJA13FQiSvikegrYfk4MUukn hyDTY/hDTh3hC70UkNjsf822HU0HNAK6gwkKt8NKUbDzKSnFr0piEA== =Bqmm -----END PGP SIGNATURE-----
-- To unsubscribe send e-mail to suse-linux-e-unsubscribe@suse.com For additional commands send e-mail to suse-linux-e-help@suse.com Also check the FAQ at http://www.suse.com/support/faq and the archives at http://lists.suse.com
On Thu, 2001-12-27 at 02:27, James Bliss wrote:
(Sorry, I should have checked this before my first email).
Okay, good to hear things are almost operational, but I still think that putting a sensitive device like a CD-RW in hdb is braindead.
The DMA errors still occur. I went into my bios and attempted to turn off DMA, Ultra DMA was disabled and there was no way to turn off DMA
a) Horsehockey; the option is called something like "PIO Only" b) Linux doesn't give a rat's patoot what the BIOS is set to; if the chip is DMA-capable, and you tell the system to use DMA (hdparm), it's going to try to use DMA.
(this is a relatively new Intel board with a PIII 933 chip).
Which? `lspci -v` will do. I don't think it's an ancient hardware problem, but a buggy hardware problem. Which kernel are you running? You may have to roll your own. -- -=|JP|=- Need a good geek? I'm unemployed! '01 B15 SE/PP | http://www.xanga.com/cowboydren/ | />< '95 SL2 Auto | cowboydren @ yahoo . com | _________________________________________________________ Do You Yahoo!? Get your free @yahoo.com address at http://mail.yahoo.com
On Thu, 2001-12-27 at 01:12, James Bliss wrote:
hda - hard disk hdb - HP CDR/W drive hdc - hard disk hdd - cdrom drive
This isn't a great configuration. Why is there a disk on hdc? I ran with hda and hdb as disks with hdc a CD-ROM and hdd a CD-RW for years with no problems. My father-in-law's HP 7200, though, insisted on being a master (though on an ALI motherboard), so we run disk/LS-120/CDRW/CDROM, again with no problems. Try swapping hdb and hdc to see what happens.
<4>hda: dma_intr: status=0x51 { DriveReady SeekComplete Error } <4>hda: dma_intr: error=0x84 { DriveStatusError BadCRC }
This is due to a misconfigured kernel or an ancient chipset running in DMA-enabled mode. There's a hack for the kernel, but I can't recall it at the moment. Alternatively, you could turn DMA off, as I had to do with my MVP3 chipset motherboard.
when I try, it gives me an error 'you must specify the filesystem type'. When I specify auto for the file system type it gives me the error message 'cdrom is not a block device'.
Don't set it to auto. That's just not bright. If you need UDF, specify UDF on the command line, otherwise leave it ISO9660 in /etc/fstab. -- -=|JP|=- Need a good geek? I'm unemployed! '01 B15 SE/PP | http://www.xanga.com/cowboydren/ | />< '95 SL2 Auto | cowboydren @ yahoo . com | _________________________________________________________ Do You Yahoo!? Get your free @yahoo.com address at http://mail.yahoo.com
If I change the configuration to:
hda - hard disk
hdb - hard disk (used to be hdc)
hdc - HP CDR/W drive (it is a 7200)
HDD - cdrom drive
Do I need to edit any configuration files other than:
fstab (change all hdc entries to hdb)
lilo.conf (change hdb to hdc=ide-scsi)
I do not want to be in a situation that prevents me from booting or requires me to reinstall
everything.
I have tracked down some reasonable responses to the below error message which
indicate that there is 'dirty crosstalk on your ribbon' so I am imagining that the problem
may be that the HP 7200i drive wants to be a master while I am making it a slave and it is
causing some bad communication problems on the cable.
Thanks for everyone's help.
Jim
12/27/01 01:34:00 AM, Jon Pennington
On Thu, 2001-12-27 at 01:12, James Bliss wrote:
hda - hard disk hdb - HP CDR/W drive hdc - hard disk hdd - cdrom drive
This isn't a great configuration. Why is there a disk on hdc? I ran with hda and hdb as disks with hdc a CD-ROM and hdd a CD-RW for years with no problems. My father-in-law's HP 7200, though, insisted on being a master (though on an ALI motherboard), so we run disk/LS-120/CDRW/CDROM, again with no problems. Try swapping hdb and hdc to see what happens.
<4>hda: dma_intr: status=0x51 { DriveReady SeekComplete Error } <4>hda: dma_intr: error=0x84 { DriveStatusError BadCRC }
This is due to a misconfigured kernel or an ancient chipset running in DMA-enabled mode. There's a hack for the kernel, but I can't recall it at the moment. Alternatively, you could turn DMA off, as I had to do with my MVP3 chipset motherboard.
when I try, it gives me an error 'you must specify the filesystem type'. When I specify auto for the file system type it gives me the error message 'cdrom is not a block device'.
Don't set it to auto. That's just not bright. If you need UDF, specify UDF on the command line, otherwise leave it ISO9660 in /etc/fstab.
-- -=|JP|=- Need a good geek? I'm unemployed!
'01 B15 SE/PP | http://www.xanga.com/cowboydren/ | />< '95 SL2 Auto | cowboydren @ yahoo . com |
_________________________________________________________
Do You Yahoo!?
Get your free @yahoo.com address at http://mail.yahoo.com
-- To unsubscribe send e-mail to suse-linux-e-unsubscribe@suse.com For additional commands send e-mail to suse-linux-e-help@suse.com Also check the FAQ at http://www.suse.com/support/faq and the archives at http://lists.suse.com
On Thu, 2001-12-27 at 04:23, James Bliss wrote:
Do I need to edit any configuration files other than: fstab (change all hdc entries to hdb) lilo.conf (change hdb to hdc=ide-scsi)
We may have a winner, James. I'd triple-check the jumpers on the drives to make absolutely certain that the slaves are set to slaves and the masters set to masters; cable select mode is not to be trusted, even on modern hardware. Edit the files you've mentioned, run lilo, and you should be just fine. Keep us posted on the DMA issue...that can spell trouble in the long run. -- -=|JP|=- Need a good geek? I'm unemployed! '01 B15 SE/PP | http://www.xanga.com/cowboydren/ | />< '95 SL2 Auto | cowboydren @ yahoo . com | _________________________________________________________ Do You Yahoo!? Get your free @yahoo.com address at http://mail.yahoo.com
Thanks for your help Robert and Jon.
I now have it up and running. I still get some:
<4>hda: dma_intr: status=0x51 { DriveReady SeekComplete Error }
<4>hda: dma_intr: error=0x84 { DriveStatusError BadCRC }
But it is half the previous number. So, having the HP 7200i CDR-W drive as a slave was
causing half of the errors. I must imagine that the Western Digital drive does not like
having a slave drive on its cable (ribbon). These errors only occur on boot and I never
see them after that. I guess I will just have to keep my eye out for any other ideas and
possibly just get some sleep and dream up an idea.
In the process of changing all of the drives around I made certain that each was properly
set as master or slave. In the process, all cables were reset. If I come up with anything I
will let everyone know.
Again, thanks for the help.
Jim
12/27/01 05:08:08 AM, Jon Pennington
On Thu, 2001-12-27 at 04:23, James Bliss wrote:
Do I need to edit any configuration files other than: fstab (change all hdc entries to hdb) lilo.conf (change hdb to hdc=ide-scsi)
We may have a winner, James. I'd triple-check the jumpers on the drives to make absolutely certain that the slaves are set to slaves and the masters set to masters; cable select mode is not to be trusted, even on modern hardware. Edit the files you've mentioned, run lilo, and you should be just fine.
Keep us posted on the DMA issue...that can spell trouble in the long run.
-- -=|JP|=- Need a good geek? I'm unemployed!
'01 B15 SE/PP | http://www.xanga.com/cowboydren/ | />< '95 SL2 Auto | cowboydren @ yahoo . com |
_________________________________________________________
Do You Yahoo!?
Get your free @yahoo.com address at http://mail.yahoo.com
-- To unsubscribe send e-mail to suse-linux-e-unsubscribe@suse.com For additional commands send e-mail to suse-linux-e-help@suse.com Also check the FAQ at http://www.suse.com/support/faq and the archives at http://lists.suse.com
On Thu, 2001-12-27 at 07:01, James Bliss wrote:
Thanks for your help Robert and Jon.
I hope my usefulness is not over yet... :)
I now have it up and running. I still get some: <4>hda: dma_intr: status=0x51 { DriveReady SeekComplete Error } <4>hda: dma_intr: error=0x84 { DriveStatusError BadCRC }
I remember now. In 2.4 and the last of the 2.2 Linux kernels, if you have Experimental support on, in the IDE/ATA drivers, there's an option called "Use multi-mode by default," which should be ON. From the help on this option: CONFIG_IDEDISK_MULTI_MODE: If you get this error, try to say Y here: hda: set_multmode: status=0x51 { DriveReady SeekComplete Error } hda: set_multmode: error=0x04 { DriveStatusError } If in doubt, say N. You still haven't mentioned which kernel your box is running. I believe that `uname -a` will tell us everything we need to know. If you're already running SuSE's Pentium-optimised kernel, you may need to recompile from source.
In the process of changing all of the drives around I made certain that each was properly set as master or slave.
Well, at this point I'm suspecting a dead cable or a dying disk. Let's have a look at that kernel, one last try from source, maybe, and then we'll get cracking on the hardware. A short anecdote: Just a few weeks ago, I was at our LUG meeting, and a fellow brought in his computer for us to install Linux on. He had a "new" Western Digital 6.4GB or so disk, received by him from WD as a replacement for his 3.2G only a few weeks ago. He also had a cable that was as old as the rest of his components, but not more than a year or so. Well, the Mandrake installer hung, the RH installer didn't write to the MBR, and we were all perplexed, so we took the disk out and put it in a new machine. With the new cable in the new machine, the disk appeared much happier, until it was time to reboot. The disk was bad, even though it was only a year old (by manufacturing date) and had only been in use for a few weeks! Disks die; it's a fact of life. Mechanical parts are prone to failure, and a disk is no exception. Considering the millions upon millions of disks like Junker Jim's SO's laptop that have never needed replaced, and a disk or two that we geeks replace is nothing at all. Don't cry too many tears, but pray that it's still under warranty! -- -=|JP|=- Need a good geek? I'm unemployed! '01 B15 SE/PP | http://www.xanga.com/cowboydren/ | />< '95 SL2 Auto | cowboydren @ yahoo . com | _________________________________________________________ Do You Yahoo!? Get your free @yahoo.com address at http://mail.yahoo.com
Thanks for your help. I was afraid that the disk may be the problem, although the only
time I get these errors is on boot. I did replace the cable with a new cable which I had
laying around. So, if it is hardware, it is the disk (ah well). The disk appeared to be
happy when no other device was on the cable with it.
I am running 2.4.16-4GB kernel. It is the stock kernel rpm from SuSE and I believe that
they have experimental support on by default. Is the Use multi-mode by default and
configuration file option or a option in the config file for compiling the kernel?
Thanks,
JIm
12/27/01 01:59:33 PM, Jon Pennington
On Thu, 2001-12-27 at 07:01, James Bliss wrote:
Thanks for your help Robert and Jon.
I hope my usefulness is not over yet... :)
I now have it up and running. I still get some: <4>hda: dma_intr: status=0x51 { DriveReady SeekComplete Error } <4>hda: dma_intr: error=0x84 { DriveStatusError BadCRC }
I remember now. In 2.4 and the last of the 2.2 Linux kernels, if you have Experimental support on, in the IDE/ATA drivers, there's an option called "Use multi-mode by default," which should be ON. From the help on this option:
CONFIG_IDEDISK_MULTI_MODE:
If you get this error, try to say Y here:
hda: set_multmode: status=0x51 { DriveReady SeekComplete Error } hda: set_multmode: error=0x04 { DriveStatusError }
If in doubt, say N.
You still haven't mentioned which kernel your box is running. I believe that `uname -a` will tell us everything we need to know. If you're already running SuSE's Pentium-optimised kernel, you may need to recompile from source.
In the process of changing all of the drives around I made certain that each was properly set as master or slave.
Well, at this point I'm suspecting a dead cable or a dying disk. Let's have a look at that kernel, one last try from source, maybe, and then we'll get cracking on the hardware.
A short anecdote:
Just a few weeks ago, I was at our LUG meeting, and a fellow brought in his computer for us to install Linux on. He had a "new" Western Digital 6.4GB or so disk, received by him from WD as a replacement for his 3.2G only a few weeks ago. He also had a cable that was as old as the rest of his components, but not more than a year or so. Well, the Mandrake installer hung, the RH installer didn't write to the MBR, and we were all perplexed, so we took the disk out and put it in a new machine. With the new cable in the new machine, the disk appeared much happier, until it was time to reboot. The disk was bad, even though it was only a year old (by manufacturing date) and had only been in use for a few weeks!
Disks die; it's a fact of life. Mechanical parts are prone to failure, and a disk is no exception. Considering the millions upon millions of disks like Junker Jim's SO's laptop that have never needed replaced, and a disk or two that we geeks replace is nothing at all. Don't cry too many tears, but pray that it's still under warranty!
-- -=|JP|=- Need a good geek? I'm unemployed!
'01 B15 SE/PP | http://www.xanga.com/cowboydren/ | />< '95 SL2 Auto | cowboydren @ yahoo . com |
_________________________________________________________
Do You Yahoo!?
Get your free @yahoo.com address at http://mail.yahoo.com
-- To unsubscribe send e-mail to suse-linux-e-unsubscribe@suse.com For additional commands send e-mail to suse-linux-e-help@suse.com Also check the FAQ at http://www.suse.com/support/faq and the archives at http://lists.suse.com
Just click in the box that shows the extensions and add *rpm, and it will remember it.
Tried that and it doesn't work. You can enter the extension but it will not remain in the file filter box. I received information (via newsgroup) that the extension has to be compiled into the program. In the meantime, I'll just use the last stable version (before 2.2.2) of the utility. I've updated everything else to 2.2.2. Thanks anyway though. Zach
On Thursday 27 December 2001 15.56, Zach Smith wrote:
Just click in the box that shows the extensions and add *rpm, and it will remember it.
Tried that and it doesn't work. You can enter the extension but it will not remain in the file filter box. I received information (via newsgroup) that the extension has to be compiled into the program. In the meantime, I'll just use the last stable version (before 2.2.2) of the utility. I've updated everything else to 2.2.2. Thanks anyway though.
There's an error in the .spec-file. Download and install the kdeadmin.src.rpm for 2.2.2, edit /usr/src/packages/SPECS/kdeadmin.spec, find the line that says --with-rpm=/usr/ \ and change it to --with-rpm \ do rpm -bb /usr/src/packages/SPECS/kdeadmin.spec and a correct rpm will land in /usr/src/packages/RPMS/i386. add --target i686 to the rpm command if you want to optimize the compile. Then the rpm will land in RPMS/i686 (duh! :) regards Anders
On Thursday 27 December 2001 10:52 am, Anders Johansson, went on about:
There's an error in the .spec-file. Download and install the kdeadmin.src.rpm for 2.2.2, edit /usr/src/packages/SPECS/kdeadmin.spec, find the line that says --with-rpm=/usr/ \ and change it to --with-rpm \
do rpm -bb /usr/src/packages/SPECS/kdeadmin.spec and a correct rpm will land in /usr/src/packages/RPMS/i386. add --target i686 to the rpm command if you want to optimize the compile. Then the rpm will land in RPMS/i686 (duh! :)
regards Anders
Whut? Huh? Is Anders speaking some type of foreign language here? ;-) Anders, this just went whoosh, right over my head. It certainly sounds doable, but I don't think I would even know where to start with all those unknown instructions. Just goes to show me how little I still know about Linux! :-) But I love when you talk technical to us! Patrick -- ---KMail 1.3.2--- SuSE Linux v7.2 Pro--- Registered Linux User #225206 /tracerb@sprintmail.com/ *Magic Page Products* Amiga-Sales & Service-http://home.sprintmail.com/~tracerb
On Thursday 27 December 2001 17.17, Patrick wrote:
On Thursday 27 December 2001 10:52 am, Anders Johansson, went on about:
There's an error in the .spec-file. Download and install the kdeadmin.src.rpm for 2.2.2, edit /usr/src/packages/SPECS/kdeadmin.spec, find the line that says --with-rpm=/usr/ \ and change it to --with-rpm \
do rpm -bb /usr/src/packages/SPECS/kdeadmin.spec and a correct rpm will land in /usr/src/packages/RPMS/i386. add --target i686 to the rpm command if you want to optimize the compile. Then the rpm will land in RPMS/i686 (duh! :)
regards Anders
------------------------------------------- Whut? Huh? Is Anders speaking some type of foreign language here? ;-) Anders, this just went whoosh, right over my head. It certainly sounds doable, but I don't think I would even know where to start with all those unknown instructions. Just goes to show me how little I still know about Linux! :-) But I love when you talk technical to us!
:) OK, in shorter steps Download kdeadmin-2.2.2-45.src.rpm and install. You now have a file /usr/src/packages/SPECS/kdeadmin.spec. Edit this, find the line that says --with-rpm=/usr/ \ This is wrong, --with-rpm doesn't take a parameter. Change it to --with-rpm \ Note that you should keep the backslash. Now rebuild the rpm. Do this with rpm -bb /usr/src/packages/SPECS/kdeadmin.spec If you have a newer computer you can make an optimized compile with rpm -bb --target i686 /usr/src/packages/SPECS/kdeadmin.spec the default is i386. The new rpm will be created in /usr/src/packages/RPMS/<target>/ For example /usr/src/packages/RPMS/i686/ Just install this new rpm and you should have a functioning kpackage. //Anders
Zach Smith wrote:
Just click in the box that shows the extensions and add *rpm, and it will remember it.
Tried that and it doesn't work. You can enter the extension but it will not remain in the file filter box. I received information (via newsgroup) that the extension has to be compiled into the program. In the meantime, I'll just use the last stable version (before 2.2.2) of the utility. I've updated everything else to 2.2.2. Thanks anyway though.
Zach
Were you root? I had the same problem and it worked for me. Also try *.rpm not *rpm as indicated above. kdesu kpackage -- Mark Hounschell dmarkh@cfl.rr.com
On Thursday 27 December 2001 02:12, James wrote:
Now, when I reboot I get errors with my harddisk (hda). The errors showed up immediately after I connected my CDR drive and turne the box back on. The original configuration was:
hda - hard disk hdb - nothing hdc - hard disk hdd - cdrom drive
This worked just fine. The new configuration is:
hda - hard disk hdb - HP CDR/W drive hdc - hard disk hdd - cdrom drive
What I am about to mention may not have anything to do with your problem. However, I thought I'd mention that it is customary to put your hard drives together on the same controller and your cd drives together on the same controller (i.e. hda and hdb would be your hard drives on IDE 1 and hdc and hdd would be your cd drives on IDE 2). The configuration you listed is not wrong as far as I know, so changing it may not make a difference. On the other hand, if you are running out of things to try, maybe you can try it just to see what happens. *************************************************** Powered by SuSE Linux 7.2 Professional KDE 2.1.2 KMail 1.2 Bryan S. Tyson bryantyson@earthlink.net ***************************************************
participants (8)
-
Anders Johansson
-
Bryan Tyson
-
James Bliss
-
Jon Pennington
-
Mark Hounschell
-
Patrick
-
Phantasm
-
Zach Smith