> > Seeing that this is the second device that has shown these symptoms, I > > would consider it *extremely unlikely* that this is the problem. > > So do I.
Me also. > > Here is what should have been done to diagnose a burner problem: > > Check for software problems. These can be caused by hardware problems > and can at times be difficult to distinguish from hardware problems. > > Check syslog - this indicates a hardware problem. > Possibilities: > > Media I/O errors cause IDE busses to lock up. Check with different > media. > > Defective drive - connect to another computer > > Defective cable - replace cable, preferably with an unused one > > Defective motherboard - connect a different drive > > Two pieces of hardware being fine by themselves, but mutually > incompatible. > > Make sure you connect only one drive per cable for testing. > > In theory, it could be a kernel driver problem. Test with OtherOS if > possible. Very good description of what should be done Volker. I agree entirely. > At this point, the defective piece of hardware should be located, and > the tests shouldn't have taken long. Now's the time to go back to the > shop. I wouldn't request a replacement drive unless I had at least > somewhat excluded other hardware. If the parts were purchased at the > same time to make a system, one can argue it's the shop's problem to > sort the lot. > At the moment from following the thread I do not believe that we have entirely eliminated a chipset/drive interaction and before returning this to the shop I would probably attempt the hdparm line. hdparm -d 1 -X32 /dev/hdc as taken from http://www.dtek.chalmers.se/groups/dvd/faq.shtml question 44. Just in case.
