[Bug 237164] New: openSuse 10.2 turns off DVD drive DMA all by itself when DVD movie starts playing
https://bugzilla.novell.com/show_bug.cgi?id=237164 Summary: openSuse 10.2 turns off DVD drive DMA all by itself when DVD movie starts playing Product: openSUSE 10.2 Version: Final Platform: x86-64 OS/Version: Other Status: NEW Severity: Major Priority: P5 - None Component: Basesystem AssignedTo: bnc-team-screening@forge.provo.novell.com ReportedBy: rmuncrief@comcast.net QAContact: qa@suse.de OS: openSuse 10.2 Motherboard: Gigabyte GA-K8N Pro-SLI Processor: Ahtlon 64 3000+ Video: Nvidia 7800GT Sound: Integrated AC7 RAM: 1GB Hard Disks: SATA Maxtor 6V200E0, SATA Western Digital WD1200JS CD-ROM: Sony CDU5221 DVD-RW: Lite-On LH-18A1P I installed openSuse 10.2 to see if Linux worked yet. One of the many killer reasons its still not useable is because it's turning off the DMA on DVD drives, all by itself. When I first boot into the OS and look at my DVD drives DMA setting in Yast it is correctly set to UltraDMA 66. However, the minute I try to play a DVD your OS actually turns the DMA off. I can actually watch it happen with Yast. It's also impossible to turn the DMA back on again until I stop playing the DVD. I made sure I had all of the latest updates (as of today) and have tried to install Linux many times over the last decade so I naturally looked everywhere on the Internet to try to find an answer to the problem, but what I found was that currently Linux has problems with DMA in general. Sheesh. I don't know why I waste my time. You really should stop claiming Linux is "technically superior" to anything. Currently it has massive DMA problems, and a bug that has existed for over two years that makes it impossible for people to turn on the SPDIF output unless they know the magic trick of installing "aumix" and hitting mute/unmute. And getting TV Out?. Even with the latest high end video cards you have to go back, back, back, to 1989 and hand hack some file called "xorg.conf" to get a barely useable overscanned display that overflows the screen. Sheesh again people. Why don't you fix the basic things that make your OS completey useless before going on to a "better" GUI. Lord almighty, do you realize it's 2007 and there still has never been one, not one, functioning Linux desktop that could replace Windows? I sure wish there were, because I would buy it in a heartbeat. Oh yeah. People also need to browse the Internet, with full multimedia support, in 2007. Linux currently has a few extremely poor quality browser plugins that can play some media, sometimes, but even then you can't rewind, fast forward, pause, etc. I mean honestly, I'm an engineer and if this were my product these problems would be fixed in a matter of months, not decades. It's just very, very, unfortunate that Linux always has been, and it appears will continue to be, an unuseable mess, and no one developing it has ever seemed to give a hoot. And yeah, I know. It's not Linux's fault, or the Linux development communities fault, it's always someone elses fault. Usually Microsofts. Well, your red herrings don't fly anymore. Either make an OS that works and is worth spending money on, or stop wasting the worlds time. We're just sick of it. Plain and simple. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug, or are watching someone who is.
https://bugzilla.novell.com/show_bug.cgi?id=237164 pavel@novell.com changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |pavel@novell.com Severity|Major |Minor ------- Comment #1 from pavel@novell.com 2007-01-22 13:40 MST ------- So... you probably have broken DVD drive that can not keep up on UDMA64... and you do not know how to submit a bug report. Key word is "one bug per report". For the DVD problem, do dmesg while playing DVD, and see what kernel reports. If it reports CRC problems, feel free to hack your kernel not to slow down on CRC errors. ... Also try latest vanilla kernel, perhaps some problem is fixed there.
pause, etc. I mean honestly, I'm an engineer and if this were my product these problems would be fixed in a matter of months, not decades.
This is opensource, so where are your patches? -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug, or are watching someone who is.
https://bugzilla.novell.com/show_bug.cgi?id=237164 mhorvath@novell.com changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |NEEDINFO Info Provider| |rmuncrief@comcast.net ------- Comment #2 from mhorvath@novell.com 2007-01-26 13:11 MST ------- Please attach your /var/log/messages. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug, or are watching someone who is.
https://bugzilla.novell.com/show_bug.cgi?id=237164 rmuncrief@comcast.net changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEEDINFO |NEW Info Provider|rmuncrief@comcast.net | ------- Comment #3 from rmuncrief@comcast.net 2007-01-26 13:55 MST ------- I uninstalled Suse 10.2 and do not have the time to reinstall it again. As I said before, even if I could play a DVD movie I still wouldn't be able to fully browse the internet, and would have to go through complex configuration operations to simply utilize my Nvidia 7800GT in TV out mode. And no, there is nothing wrong with my DVD drive. I have no idea why you would jump to such an arbitrary conclusion. Under Windows XP I can play DVD movies with stunning quality utilizing the same DVD drive with the same video card. Finally, I did not offer a "patch" because I am not a Linux developer, and have no desire to become one. I simply wanted to pay $40 or $50 for an alternative OS because I think Microsoft is an illegal monopoly and should be prosecuted to the fullest extent of the law. Unfortunately, Apple is even more expensive and closed, and Linux simply isn't a viable desktop OS. In any case, I perceive a clear "shoot the messenger" mentality here, so go ahead and do so. Blame me, and other users, and Microsoft, for everything. Ignore us. Don't work on multimedia. You could even say that it's our fault for filing multiple bugs in one ticket, or something like that. And close this bug. I just wanted to help by letting you know about a serious bug plauging many, many, Linux users (just Google and look at all the Linux DMA problems, and how many relate to playing DVDs) and all you want to do is complain about my complaining. Sheesh. Good luck. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug, or are watching someone who is.
https://bugzilla.novell.com/show_bug.cgi?id=237164 mhorvath@novell.com changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |RESOLVED Resolution| |WONTFIX ------- Comment #4 from mhorvath@novell.com 2007-01-26 14:07 MST ------- Thank you for your activity and partially I agree with you. However without the logs it's impossible to target the problem and fix it. Therefore I have to close this bug as wontfix. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug, or are watching someone who is.
https://bugzilla.novell.com/show_bug.cgi?id=237164 ------- Comment #5 from rmuncrief@comcast.net 2007-01-26 18:57 MST ------- Created an attachment (id=115622) --> (https://bugzilla.novell.com/attachment.cgi?id=115622&action=view) This is the /var/log/messages file showing my DVD drives DMA being turned off. This log shows the OS receiving responses from my DVD drive that it believes are errors, and then turning my drive DMA off (it starts out as UDMA 66 at boot). The drive plays DVD movies perfectly smoothly under Windows XP Professional, actually the video is quite stunning and even better than my standalone DVD player. However, since the DMA is turned off under Linux the DVD playback is jerky. By the way, the drive also reads and writes DVD and CD R and RW media perfectly, so I would be very surprised if there were really anything wrong with my DVD drive. I've also seen many complaints via Google about DVD/DMA problems, so maybe this has something to do with it. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug, or are watching someone who is.
https://bugzilla.novell.com/show_bug.cgi?id=237164 rmuncrief@comcast.net changed: What |Removed |Added ---------------------------------------------------------------------------- Status|RESOLVED |REOPENED Resolution|WONTFIX | ------- Comment #6 from rmuncrief@comcast.net 2007-01-26 19:00 MST ------- Since you replied so civilly and seemed genuinely concerned about the problem I spent the time to reinstall openSuse 10.2 and have attached the /var/log/messages file that you requested to this bug. I will leave openSuse installed so if you need any other logs please let me know and I will send them to you. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug, or are watching someone who is.
https://bugzilla.novell.com/show_bug.cgi?id=237164 ------- Comment #7 from pavel@novell.com 2007-01-27 04:04 MST ------- Jan 26 15:48:48 linux kernel: hda: cdrom_decode_status: status=0x51 { DriveReady SeekComplete Error } Jan 26 15:48:48 linux kernel: hda: cdrom_decode_status: error=0x40 { LastFailedSense=0x04 } Jan 26 15:48:48 linux kernel: ide: failed opcode was: unknown Jan 26 15:48:48 linux kernel: hda: cdrom_decode_status: status=0x51 { DriveReady SeekComplete Error } Jan 26 15:48:48 linux kernel: hda: cdrom_decode_status: error=0x40 { LastFailedSense=0x04 } Jan 26 15:48:48 linux kernel: ide: failed opcode was: unknown Jan 26 15:48:48 linux kernel: hda: cdrom_decode_status: status=0x51 { DriveReady SeekComplete Error } Jan 26 15:48:48 linux kernel: hda: cdrom_decode_status: error=0x40 { LastFailedSense=0x04 } Jan 26 15:48:48 linux kernel: ide: failed opcode was: unknown Jan 26 15:48:48 linux kernel: hda: cdrom_decode_status: status=0x51 { DriveReady SeekComplete Error } Jan 26 15:48:48 linux kernel: hda: cdrom_decode_status: error=0x40 { LastFailedSense=0x04 } Jan 26 15:48:48 linux kernel: ide: failed opcode was: unknown Jan 26 15:48:48 linux kernel: hda: DMA disabled Jan 26 15:48:48 linux kernel: hda: ide_intr: huh? expected NULL handler on exit Jan 26 15:48:48 linux kernel: hda: ATAPI reset complete Jan 26 15:48:52 linux kernel: st: Version 20050830, fixed bufsize 32768, s/g segs 256 .. Jan 26 17:16:07 ENTROPOD kernel: st: Version 20050830, fixed bufsize 32768, s/g segs 256 Jan 26 17:16:08 ENTROPOD kernel: hda: drive_cmd: status=0x51 { DriveReady SeekComplete Error } Jan 26 17:16:08 ENTROPOD kernel: hda: drive_cmd: error=0x04 { AbortedCommand } Jan 26 17:16:08 ENTROPOD kernel: ide: failed opcode was: 0xec Jan 26 17:16:08 ENTROPOD kernel: hdc: drive_cmd: status=0x51 { DriveReady SeekComplete Error } Jan 26 17:16:08 ENTROPOD kernel: hdc: drive_cmd: error=0x04 { AbortedCommand } Jan 26 17:16:08 ENTROPOD kernel: ide: failed opcode was: 0xec Jan 26 17:16:49 ENTROPOD kernel: hda: drive_cmd: status=0x51 { DriveReady SeekComplete Error } Jan 26 17:16:49 ENTROPOD kernel: hda: drive_cmd: error=0x04 { AbortedCommand } Jan 26 17:16:49 ENTROPOD kernel: ide: failed opcode was: 0xec Jan 26 17:16:49 ENTROPOD kernel: hdc: drive_cmd: status=0x51 { DriveReady SeekComplete Error } Jan 26 17:16:49 ENTROPOD kernel: hdc: drive_cmd: error=0x04 { AbortedCommand } Jan 26 17:16:49 ENTROPOD kernel: ide: failed opcode was: 0xec Jan 26 17:17:03 ENTROPOD kernel: hda: drive_cmd: status=0x51 { DriveReady SeekComplete Error } Jan 26 17:17:03 ENTROPOD kernel: hda: drive_cmd: error=0x04 { AbortedCommand } Jan 26 17:17:03 ENTROPOD kernel: ide: failed opcode was: 0xec Jan 26 17:17:03 ENTROPOD kernel: hdc: drive_cmd: status=0x51 { DriveReady SeekComplete Error } Jan 26 17:17:03 ENTROPOD kernel: hdc: drive_cmd: error=0x04 { AbortedCommand } Jan 26 17:17:03 ENTROPOD kernel: ide: failed opcode was: 0xec Jan 26 17:17:44 ENTROPOD kernel: hda: drive_cmd: status=0x51 { DriveReady SeekComplete Error } Jan 26 17:17:44 ENTROPOD kernel: hda: drive_cmd: error=0x04 { AbortedCommand } Jan 26 17:17:44 ENTROPOD kernel: ide: failed opcode was: 0xec Jan 26 17:17:44 ENTROPOD kernel: hdc: drive_cmd: status=0x51 { DriveReady SeekComplete Error } Jan 26 17:17:44 ENTROPOD kernel: hdc: drive_cmd: error=0x04 { AbortedCommand } Jan 26 17:17:44 ENTROPOD kernel: ide: failed opcode was: 0xec Jan 26 17:17:53 ENTROPOD kernel: hda: cdrom_decode_status: status=0x51 { DriveReady SeekComplete Error } Jan 26 17:17:53 ENTROPOD kernel: hda: cdrom_decode_status: error=0x40 { LastFailedSense=0x04 } Jan 26 17:17:53 ENTROPOD kernel: ide: failed opcode was: unknown Jan 26 17:17:53 ENTROPOD kernel: hda: cdrom_decode_status: status=0x51 { DriveReady SeekComplete Error } Jan 26 17:17:53 ENTROPOD kernel: hda: cdrom_decode_status: error=0x40 { LastFailedSense=0x04 } Jan 26 17:17:53 ENTROPOD kernel: ide: failed opcode was: unknown Jan 26 17:17:53 ENTROPOD kernel: hda: cdrom_decode_status: status=0x51 { DriveReady SeekComplete Error } Jan 26 17:17:53 ENTROPOD kernel: hda: cdrom_decode_status: error=0x40 { LastFailedSense=0x04 } Jan 26 17:17:53 ENTROPOD kernel: ide: failed opcode was: unknown Jan 26 17:17:53 ENTROPOD kernel: hda: cdrom_decode_status: status=0x51 { DriveReady SeekComplete Error } Jan 26 17:17:53 ENTROPOD kernel: hda: cdrom_decode_status: error=0x40 { LastFailedSense=0x04 } Jan 26 17:17:53 ENTROPOD kernel: ide: failed opcode was: unknown Jan 26 17:17:53 ENTROPOD kernel: hda: DMA disabled Jan 26 17:17:53 ENTROPOD kernel: hda: ide_intr: huh? expected NULL handler on exit Jan 26 17:17:53 ENTROPOD kernel: hda: ATAPI reset complete Jan 26 17:18:11 ENTROPOD kernel: hda: drive_cmd: status=0x51 { DriveReady SeekComplete Error } Jan 26 17:18:11 ENTROPOD kernel: hda: drive_cmd: error=0x04 { AbortedCommand } Jan 26 17:18:11 ENTROPOD kernel: ide: failed opcode was: 0xec Jan 26 17:18:11 ENTROPOD kernel: hdc: drive_cmd: status=0x51 { DriveReady SeekComplete Error } Jan 26 17:18:11 ENTROPOD kernel: hdc: drive_cmd: error=0x04 { AbortedCommand } Jan 26 17:18:11 ENTROPOD kernel: ide: failed opcode was: 0xec Yes, something is wrong there... can you try if normal reading from dvd (say, reading pictures, data?) works ok at expected speed? -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug, or are watching someone who is.
https://bugzilla.novell.com/show_bug.cgi?id=237164 ------- Comment #8 from rmuncrief@comcast.net 2007-01-27 09:24 MST ------- Created an attachment (id=115668) --> (https://bugzilla.novell.com/attachment.cgi?id=115668&action=view) This is the /var/log/messages file showing the DMA turned off when a data DVD is inserted. Thank you for addressing this problem so quickly. While I'm still disappointed by Linux, I am impressed by your efforts to fix this bug. I will start reporting bugs formally from now on. I apologize for earlier stating that Linux developers don't give a hoot, because you obviously do. I put a data DVD in my DVD drive as you requested, but as soon as I did the DMA was turned off. Note that I didn't even try to transfer any data from it, or even look at the data on it. I simply put it in the DVD drive and looked at the DMA settings in Yast and saw it had immediately been turned off. The DVD was actually the DVD I installed Suse 10.2 from, the media is a Memorex DVD+RW 4X. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug, or are watching someone who is.
https://bugzilla.novell.com/show_bug.cgi?id=237164 ------- Comment #9 from rmuncrief@comcast.net 2007-01-27 09:34 MST ------- I forgot to note that I just bought this drive about a month ago, and my previous DVD drive, a Toshiba, exhibited the same symptoms of jerky DVD playback. However, I discarded the Toshiba drive (it burned very unreliably) and can't remember the model number. I also never investigated the problem so far as to look in Yast and see if DMA was the problem. However, after my experiences and those I've read via Google I expect it had the same type of DMA problem. I know this is very vague information, but I just wanted to be as complete as possible in my reporting. Note also that Suse 10.2 has been reinstalled many times since then, so this new problem has nothing to do with the old drive and occurs immediately after a new install/update. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug, or are watching someone who is.
https://bugzilla.novell.com/show_bug.cgi?id=237164 rmuncrief@comcast.net changed: What |Removed |Added ---------------------------------------------------------------------------- Status|REOPENED |NEW ------- Comment #10 from rmuncrief@comcast.net 2007-01-27 22:40 MST ------- I figured out the problem. I went back to Windows XP and saw that it was setting the DVD drive mode to "Ultra DMA Mode 2", wich is 33.3MB/s. So I went back to Suse and using Yast forced the DMA mode to UDMA/33 (remember Suse is setting the DVD drive speed to UDMA/66) and the DVD drive worked perfectly. I watched an entire encrypted DVD (ID4) flawlessly just to be sure. This indicates a few things. First of all, it appears that Suse is detecting the DMA mode incorrectly, or at least not adjusting to what it really is. There must be a way to do it accurately, because the drive is set to the correct DMA mode by Windows XP. Secondly, and this is the worst part, if a DVD drive doesn't work at the expected speed it appears that Suse doesn't try any other DMA modes, it just drops the drive into PIO mode. There may be valid system stability issues requiring this, but I have a feeling it's what's causing the plethora of "jittery DVD" and "mysterious DVD/DMA" complaints I'm seeing on Google. I hope this helps. I'm reassigning the bug in hopes in can be fixed, and that it will enable a lot more customers to adopt openSuse. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug, or are watching someone who is.
https://bugzilla.novell.com/show_bug.cgi?id=237164 chrubis@novell.com changed: What |Removed |Added ---------------------------------------------------------------------------- AssignedTo|bnc-team- |lslezak@novell.com |screening@forge.provo.novell| |.com | -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug, or are watching someone who is.
https://bugzilla.novell.com/show_bug.cgi?id=237164 lslezak@novell.com changed: What |Removed |Added ---------------------------------------------------------------------------- AssignedTo|lslezak@novell.com |kernel-maintainers@forge.provo.novell.com Component|Basesystem |Kernel Summary|openSuse 10.2 turns off DVD |wrong DMA mode used for a DVD drive (UDMA66 |drive DMA all by itself when|instead of UDMA33) |DVD movie starts playing | ------- Comment #11 from lslezak@novell.com 2007-01-29 06:49 MST ------- Thanks for comment #10, I have updated the summary to better describe the problem. Reassigned to the kernel team... -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug, or are watching someone who is.
https://bugzilla.novell.com/show_bug.cgi?id=237164 lmb@novell.com changed: What |Removed |Added ---------------------------------------------------------------------------- AssignedTo|kernel- |teheo@novell.com |maintainers@forge.provo.nove| |ll.com | -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug, or are watching someone who is.
https://bugzilla.novell.com/show_bug.cgi?id=237164 teheo@novell.com changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |NEEDINFO Info Provider| |rmuncrief@comcast.net ------- Comment #12 from teheo@novell.com 2007-01-30 01:41 MST ------- Thanks for the reporting, ranting & nice diagnosis. 1. First on ranting. I've been using Linux as my primary desktop for around ten years now and making living out of working on Linux, but I'm in full agreement with you. For servers composed of reliable and well-documented hardware pieces, Linux really excels from both developer's and administrator's point of view (I've been both), but, yeah, for desktop, it really needs serious improvements on hardware support and multimedia as you pointed out. I also feel obligated to point out that Linux desktop has progressed a lot in recent years with maturing desktop environment (both gnome and kde), openoffice and all the great things mozilla has been doing. Still lacking on multimedia front but I now feel very comfortable using it as office desktop. So, please bear with us. Desktop hardware is just very difficult. I'm trying my best to improve ATA side of it but it's still lacking as you just frustratingly found out. 2. And on the bug itself, yeap, it seems cable detection went wrong. There are two types of parallel ATA cables. One is 40 conductor cable while the other is 80-c cable with 40 extra ground lines to reduce signal noise to allow higher transfer rate. Each controller implements cable detection differently and we sometimes get it wrong (sometimes due to lack of documentation). Please post the content of /var/log/boot.msg and the result of 'hwinfo --all'. JFYI, driver/ide/* drivers are going out of service and will be replaced by new libata drivers, which, just as you suggested, will slow down to 40-c speed limit on cases like yours. I appreciate the bug report. Please give us more time to improve things. I'm confident we can achieve comfortable desktop environment in not-so-distant future. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug, or are watching someone who is.
https://bugzilla.novell.com/show_bug.cgi?id=237164 ------- Comment #13 from rmuncrief@comcast.net 2007-01-30 14:39 MST ------- Created an attachment (id=116384) --> (https://bugzilla.novell.com/attachment.cgi?id=116384&action=view) Requested boot.msg file Hi, Thanks for addressing this bug so quickly Here is the boot.msg log you requested and the hwinfo file will follow. I apologize for my initial rant, and wish I would have said what I said but in a more civil way. It was an expression of many years of frustration, but as you can see I am indeed trying to help as much as I can. It appears that some of the multimedia bugs that have been plaguing openSuse and Linux in general, while discussed sometimes endlessly on the internet, may not have been reported to you. Either that or I am searching for bugs incorrectly. So what I'm doing now is trying to report any bug I find that is a show stopper for the adoption of openSuse. These are mostly multimedia related, and I just filed another bug (240102) on a long standing SPDIF issue that doesn't appear to have ever been reported, although you can literally find years of discussion about it via Google. I could be wrong, and let me know if I am filing duplicate bugs, but that's what it looks like so far. And by the way, I and many others are absolutely desperate to adopt Linux. I started seriously trying again with openSuse 10.1, and have already spent $200.00 on VMWare Workstation for Linux in hopes I could migrate to it. I will not only buy openSuse when I can use it as my primary desktop, but I will also donate another $50.00 to openSuse, and I'm sure many others would follow. Look, we only have two other choices, Windows Vista, which is expensive and bloated and intrusive, or Apple which is even worse. Linux has been so close, for so long, that some of us just find it a mystery as to why it still doesn't work completely. But perhaps as I said before, we have done too much complaining and not enough helping. I have also been surprised by how quickly openSuse responds to bug reports, and how interested you seem to be in fixing them as quickly as possible. This is the primary reason I'm spending so much of my time exclusively with openSuse. I'm trying to at least make sure you have some idea of what the average user is running into, and giving you the most detailed information about it that I can. Please let me know if you need any other help. I have a fairly standard NVidia based system and will help in whatever way I can. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug, or are watching someone who is.
https://bugzilla.novell.com/show_bug.cgi?id=237164 ------- Comment #14 from rmuncrief@comcast.net 2007-01-30 14:42 MST ------- Created an attachment (id=116390) --> (https://bugzilla.novell.com/attachment.cgi?id=116390&action=view) hwinfo --all output you requested Here is the hwinfo --all output. I hope it helps!. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug, or are watching someone who is.
https://bugzilla.novell.com/show_bug.cgi?id=237164 rmuncrief@comcast.net changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEEDINFO |ASSIGNED Info Provider|rmuncrief@comcast.net | -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug, or are watching someone who is.
https://bugzilla.novell.com/show_bug.cgi?id=237164 teheo@novell.com changed: What |Removed |Added ---------------------------------------------------------------------------- Status|ASSIGNED |NEEDINFO Info Provider| |rmuncrief@comcast.net ------- Comment #15 from teheo@novell.com 2007-01-30 19:17 MST ------- Okay, I need a bit more info. 1. Please verify that doing 'hdparm -X udma2 /dev/hda' fixes the problem. 2. Are the LITE-ON and SONY ODDs connected using 80c or 40c cable? http://upload.wikimedia.org/wikipedia/commons/2/26/ATA_cables.jpg Thanks. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug, or are watching someone who is.
https://bugzilla.novell.com/show_bug.cgi?id=237164 rmuncrief@comcast.net changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |rmuncrief@comcast.net Status|NEEDINFO |ASSIGNED Info Provider|rmuncrief@comcast.net | ------- Comment #16 from rmuncrief@comcast.net 2007-02-02 15:04 MST ------- Hi, I'm sorry it has taken me so long to reply, but changing cable types caused all hell to break loose under XP and it took awhile to characterize the problem, at least as best I could without an oscilloscope, logic analyzer, or spectrum analyzer. To summarize, the LITE-ON drive was installed with the cable it came with, a 40c cable, and it was rock solid under XP. When I changed it to an 80c cable XP set the drive to Ultra DMA mode 4 (UDMA66) but the drive became poly-unstable. It could only intermittently read DVD/CDs. I was eventually able to make it work but it appears the drive is shipped with a 40c cable for a reason, it is highly susceptible to noise if you use an 80c cable and it operates in UDMA66 mode. The Sony drive is using a 40c cable, and changing it to an 80c cable had no effect on it. By the way, XP places the Sony drive in PIO mode no matter what the cable, while openSuse places it in UDMA33. In any case, the Sony drive works fine under both operating systems. I didn't use the "hdparm -X udma2 /dev/hda" command you suggested but had manually set the DMA mode to UDMA33 via Yast when I was using the DVD with the 40c cable and it did fix the problem. I believe the command you suggested does the same thing. In the end I got the DVD drive to work at UDMA66 by placing the Sony drive as a slave on the same IDE cable as the DVD drive and removing the secondary IDE cable. This seemed to eliminate enough noise to allow the DVD drive to work at top speed. Keep in mind this is a very short summary, you just can't imagine (or maybe you can) all the different data and power routing solutions I tried, or how many different cables of all different types I tried. The bottom line is that it appears some ODD manufacturers will sell products whose hardware may report an operating speed that it's not actually capable of operating at. At least the operating speed may vary depending upon the noise of its environment, which is typically pretty bad in a PC cabinet. I believe your plan to adjust to the actual tested operating speed is the only reliable solution. And by the way, I took the plunge. I converted all of my data to ext3 and am using Suse 10.2 as my primary OS. Only 20GB of my 200GB of hard drive space is now formatted as NTFS, and I'm using a translator program to access the ext3 partitions from Windows XP when I need to. I have installed VMWare Workstation and am now running three separate Windows XP systems under openSuse to develop my three web sites. I'm still not completely happy with openSuse, and am having a lot of problems getting anyone to truly care or do anything about the multimedia problems, but I'm giving openSuse the best chance I can, and will do everything I can to stick with it and make it work. However, if I'm still struggling a month or so from now I will have to go out and buy Vista. I'm losing a lot of development time trying to get openSuse to perform basic desktop OS tasks. On the other hand, maybe it will work out and I can finally actually purchase a fully functional version of Linux!. That will be a great day!. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug, or are watching someone who is.
https://bugzilla.novell.com/show_bug.cgi?id=237164 ------- Comment #17 from teheo@novell.com 2007-02-02 23:26 MST ------- Welcome aboard and thanks for all the testing. The problem here is that the driver is supposed to detect that 40c cable is attached and configure UDMA33 accordingly. I'll look into cable detection logic and run some tests here. Please standby. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug, or are watching someone who is.
https://bugzilla.novell.com/show_bug.cgi?id=237164 teheo@novell.com changed: What |Removed |Added ---------------------------------------------------------------------------- Status|ASSIGNED |NEEDINFO Info Provider| |rmuncrief@comcast.net ------- Comment #18 from teheo@novell.com 2007-02-03 01:50 MST ------- Okay, possible problem spotted. amd74xx driver is not using eighty_ninty_three() to see the drive's side of cable detection and BIOS seemed to have screwed up setting up 80c bits. Can you restore your machine to the original setup with 40c cable and report the content of /var/log/boot.msg and the result of 'hdparm -I /dev/hda'? That should confirm my diagnosis. This is fixed in the new libata stack. You can choose the new driver in yast's hardware menu. The new driver is named pata_amd. It would be great if you can test this and report how it works. Ah... also, when you connected the LITE-ON using 80c cable by itself, to which connector did you connect it? In transfer modes > UDMA33, you need to connect the device to the connector at the end of the cable in single device configuration. This is to eliminate signal reflecting from the end of cable interfere with the original signal. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug, or are watching someone who is.
https://bugzilla.novell.com/show_bug.cgi?id=237164 ------- Comment #19 from teheo@novell.com 2007-02-03 01:52 MST ------- I forgot, in the original (not working) setup, please report the result of 'hdparm --Istdout /dev/hda'. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug, or are watching someone who is.
https://bugzilla.novell.com/show_bug.cgi?id=237164 rmuncrief@comcast.net changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEEDINFO |ASSIGNED Info Provider|rmuncrief@comcast.net | ------- Comment #20 from rmuncrief@comcast.net 2007-02-03 13:25 MST ------- Created an attachment (id=117249) --> (https://bugzilla.novell.com/attachment.cgi?id=117249&action=view) Debug files for IDE/UDMA cable detection problem Hi, I restored my machine to its original configuration and gathered and attached the requested information, and a little more. Unfortunately, when I changed the driver to pata_ata it loaded with an error and failed to work correctly. The drives were instantiated as SCSI drives (sr0 and sr1), so they didn't appear in Yasts IDE DMA Mode section, and couldn't play DVD movies. They were capable of reading data though. I've attached a full set of hardware info output and logs for the pata_amd attempt also. By the way, I couldn't find any "new" pata_amd driver updates, I just used the existing one on my system. Were you talking about some other updated driver? I was also able to test the "hdparm -X udma2 /dev/hda" as you previously requested (with amd74xx) and it fixed the problem for the current session, setting the drive to UDMA/33 mode. However, it's important to note that after rebooting the drive is set back to UDMA/66. The only way to permanently fix the problem right now is to go into Yast and set the "Required DMA Mode" to UDMA/33. If you do this, the drive works perfectly and will remain in UDMA/33 mode even after rebooting. I will leave my system in its original configuration until we get this problem worked out. As I said, it works fine with the manual Yast UDMA/33 setting. Please let me know when you need more testing or info. There are ten files in the compressed attachment so I'll list what they are below. Test 1 - Original configuration with amd74xx --------------------------------------------- boot.msg.amd74xx - boot.msg file. hdparm_I.amd74xx.udma66 - Output of "hdparm -I /dev/hda" command after boot, before inserting disk into DVD drive. hdparm_Istdout.amd74xx.udma66 - Output of "hdparm --Istdout /dev/hda" command after boot, before inserting disk into DVD drive. hdparm_I.amd74xx.pio - Output of "hdparm -I /dev/hda" command after inserting disk into DVD drive and drop into PIO mode. hdparm_Istdout.amd74xx.pio - Output of "hdparm --Istdout /dev/hda" command after inserting disk into DVD drive and drop into PIO mode. messages.amd74xx - messages log for this entire test session. The log was cleared before booting for the test so it only contains info for this session. Test 2 - Original configuration with pata_amd --------------------------------------------- boot.msg.pata_amd - boot.msg file. hdparm_I.pata_amd - Output of "hdparm -I /dev/sr0" command after boot. It's just an error message but is included for completeness. hdparm_Istdout.pata_amd - Output of "hdparm --Istdout /dev/sr0" command after boot. It's also just an error message included for completeness. messages.pata_amd - messages log for this entire test session. The log was cleared before booting for the test so it only contains info for this session. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug, or are watching someone who is.
https://bugzilla.novell.com/show_bug.cgi?id=237164 teheo@novell.com changed: What |Removed |Added ---------------------------------------------------------------------------- Status|ASSIGNED |RESOLVED Resolution| |FIXED ------- Comment #21 from teheo@novell.com 2007-02-05 01:49 MST ------- Debugging your problem was really interesting. I found three separate bugs while chasing your case. All fixes are submitted for mainline inclusion and I will commit to suse kernel cvs tree soon. Thanks for the detailed bug report and I wish you find suse desktop to your liking. (Please reopen and complain LOUDLY if the next update doesn't fix your problem.) -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug, or are watching someone who is.
https://bugzilla.novell.com/show_bug.cgi?id=237164 rmuncrief@comcast.net changed: What |Removed |Added ---------------------------------------------------------------------------- Status|RESOLVED |REOPENED Resolution|FIXED | ------- Comment #22 from rmuncrief@comcast.net 2007-02-06 01:02 MST ------- Hi, I'm sorry but nothing has changed except that the pata_amd driver loads without reporting an error in the boot log (the amd74xx driver still detects the drive as UDMA/66). In any case the pata_amd driver also sets the LITE-ON drive to UDMA/66 and then it evidently drops down into PIO mode. The drives were once again errantly set to Sr0/Sr1 with the pata_amd driver so they don't show up under Yast's DMA Mode settings. The only reason I haven't included more logs is that I'm really tired and I just upgraded to 3GB of RAM so my kernel has changed to "bigsmp" which I know greatly degrades the OS performance. I'm really trying to decide what to do, especially since I've got nothing but developers playing dumb on the multimedia side (see bug 240102, I honestly just don't know what else to say to this developer. As you know I'm trying to help, and will go to extraordinary lengths to do so, but most developers are making it almost impossible, you being a welcome and appreciated exception of course). Should I try to run openSuse 10.2 x64 or just give up and run Vista?. I just don't know. But the developer handling bug 240102 has really left me disheartened. I don't know how well you are coordinated there, but if you could find a cooperative developer on multimedia I would be willing to continue to try and help. Otherwise I'm beginning to feel that despite your and my best efforts, we are wasting our time. And this is not a rant my friend. Just an honest train of thought from a tired but still hopeful supporter. I just need people on your side, such as yourself, willing to work with me. In any case, the bug remains so I am reopening it. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug, or are watching someone who is.
https://bugzilla.novell.com/show_bug.cgi?id=237164 teheo@novell.com changed: What |Removed |Added ---------------------------------------------------------------------------- Status|REOPENED |RESOLVED Resolution| |FIXED ------- Comment #23 from teheo@novell.com 2007-02-06 01:43 MST ------- 1. The patch went in earlier today meaning KOTD (kernel of the day) will be updated later today; then, kernel update will be released after some time. So, for the time being, you can fix the transfer mode using YaST and with later updates you won't have to do that. 2. With [s|p]ata_* drivers disks will appear as /dev/sdX and ODDs as /dev/srX. No direct control of transfer mode (yet), but it should put your device into udma33 after some number of errors. So, what you're seeing is normal. 3. pata_amd/amd74xx cable detection still isn't perfect (but should work in your case). The solution is being discussed in upstream and will be implemented in not-too-distant future. So, I'm closing the bug again. Regarding #240102, look, you're talking directly to kernel developers. Takashi Iwai is _the_ ALSA developer and probably one of the most overloaded kernel developers. If you're going to hang around this place, expect to hear technical comments and please stop ranting. I'm afraid this bugzilla is not the type of customer service you're expecting. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug, or are watching someone who is.
https://bugzilla.novell.com/show_bug.cgi?id=237164 ------- Comment #24 from rmuncrief@comcast.net 2007-02-06 13:53 MST ------- I misunderstood when the fix would be available. I apologize for errantly reopening the bug. As for the rest of your comments, I was very surprised. In fact, they caused me to go out and plunk down $280.00 for a Windows Vista Ultimate upgrade this morning. You and your colleagues will no longer be receiving bug reports, complaints, or suggestions from this old engineer, as it seems is your wish. openSuse developers indeed have a "shoot the messenger" attitude, no matter how helpful the messenger or message is, and have a code word for any legitimate complaint - just a "rant" to be ignored. Well, you've succeeded. This messenger has been fatally wounded, as I'm sure have many others who have tried to help you. Good luck. And keep insulting anyone who tries to help you. Because of the development communities attitude and inability to organize and pursue rational goals, I'm sure Linux will be just as it is today ten years from now, ten years behind the times. It could have been different if, as a group, you had learned to listen. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug, or are watching someone who is.
https://bugzilla.novell.com/show_bug.cgi?id=237164 ------- Comment #25 from pavel@novell.com 2007-02-07 02:52 MST ------- One day, messenger came, yelling "I need to talk to the king, it is very urgent, I have urgent message for the king". So they let him to the king, where he said something like "You know, the important message is, ummm, it is blue. But king your roads are in very bad shape, and the trees are just wrong color of green, and if it was my kingdom, I'd fix it immediatelly". Knight Tejun actually asked him, what is blue, and it turned out that it is sky that is blue, after long inquiry. (And sky was fixed, by brave Tejun). It also turned out that his cart only has 3 wheels (and broken BIOS). Then he started yelling "don't shoot the messenger, don't shoot the messenger", as if shooting the messenger was inherently bad thing to do. We hanged him on the nearest tree. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug, or are watching someone who is.
https://bugzilla.novell.com/show_bug.cgi?id=237164 ------- Comment #26 from rmuncrief@comcast.net 2007-02-07 04:03 MST ------- There was no need to pesonally threaten me, or any user, with hanging or bodily harm of any type. Your threat will be reported to your management, and the proper legal authorities. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug, or are watching someone who is.
https://bugzilla.novell.com/show_bug.cgi?id=237164 lmb@novell.com changed: What |Removed |Added ---------------------------------------------------------------------------- Status Whiteboard| |kernel:sles10,sles10sp1 -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug, or are watching someone who is.
https://bugzilla.novell.com/show_bug.cgi?id=237164
User kgw@novell.com added comment
https://bugzilla.novell.com/show_bug.cgi?id=237164#c28
Klaus Wagner
participants (1)
-
bugzilla_noreply＠novell.com