linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Gregory Moyer <raven2k@syphr.com>
To: linux-kernel@vger.kernel.org
Subject: Re: sata_nv times out for BD-ROM iHOS104-08
Date: Sat, 16 Jan 2010 23:54:37 -0500	[thread overview]
Message-ID: <d4fb20ca1001162054y731bb232w4e1e999fa79372ba@mail.gmail.com> (raw)

> I contacted LiteON technical support in the meantime, but they are no
>
> help. They said they tested with one Linux system and it worked.
>
> I will probably buy one of the above VIA cards and use it for this drive.
>
> Thanks for helping!


I too am having the same problem with the iHOS104. I filed a bug
report against Ubuntu Karmic
(https://bugs.launchpad.net/ubuntu/+source/linux/+bug/344093). At
least one other person reporting on that same bug report has confirmed
the issue. We are both seeing the problem with nVidia chipsets using
the sata_nv driver. There is a lot of information in the report, so
I'll skip re-posting it all here. However, as the previous poster
mentioned, after contacting LiteOn support, I was told the drive works
in Mandriva 2007.0. I tried it and sure enough, it does. The other
poster in the linked report confirmed this as well, stating that for
that distribution, the kernel was at 2.6.17 and the sata_nv driver was
at 0.8. I have tried several distributions/kernels, including 2.6.32.
I have also tried a myriad of kernel and BIOS options, including all
of the ones mentioned so far in this thread. If I can help in any way
to get this resolved, please let me know. Thanks for taking the time
to look into it.

             reply	other threads:[~2010-01-17  4:54 UTC|newest]

Thread overview: 28+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-01-17  4:54 Gregory Moyer [this message]
  -- strict thread matches above, loose matches on Subject: below --
2010-06-03 17:40 sata_nv times out for BD-ROM iHOS104-08 Gregory Moyer
2010-01-21  3:15 Gregory Moyer
2009-12-22 16:07 Cengiz Gunay
2009-12-23  7:38 ` Tejun Heo
     [not found]   ` <d2d378040912232302u4b550dap687fcadced237935@mail.gmail.com>
2009-12-24  7:25     ` Tejun Heo
2010-01-16 21:34       ` Cengiz Günay
2010-01-17 15:28         ` Ozan Çağlayan
2010-01-19  9:05           ` Tejun Heo
2010-01-19  9:34             ` Ozan Çağlayan
2010-01-20  2:13         ` Tejun Heo
2010-01-20  2:59           ` Robert Hancock
2010-01-22 14:11             ` Cengiz Günay
2010-01-23  3:45               ` Tejun Heo
2010-01-23 21:39                 ` Cengiz Günay
     [not found]                   ` <4B67A149.10406@kernel.org>
2010-02-17 16:14                     ` Cengiz Günay
2010-02-18  1:50                       ` Tejun Heo
2010-02-20 19:11                         ` Cengiz Günay
2010-02-21  1:01                           ` Tejun Heo
2010-02-21 21:28                             ` Cengiz Günay
2010-02-23  2:38                               ` Tejun Heo
2010-02-28 17:24                                 ` Cengiz Günay
2010-03-02 11:48                                   ` Tejun Heo
2010-03-08 19:17                                     ` Cengiz Günay
2010-03-08 23:46                                       ` Robert Hancock
2010-03-09  1:21                                       ` Tejun Heo
2010-03-09  5:18                                         ` Cengiz Günay
2010-05-25 19:34                                           ` Tejun Heo

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=d4fb20ca1001162054y731bb232w4e1e999fa79372ba@mail.gmail.com \
    --to=raven2k@syphr.com \
    --cc=linux-kernel@vger.kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).