On Sun, 9 Nov 2008 23:01:59 +0100, Florian Kulzer <[EMAIL PROTECTED]> wrote:
>
> That looks more and more like you found a regression in the USB driver.
> If you can reproduce the problem with an upstream 2.6.27 kernel then it
> is probably best to contact the kernel mailing list directly about thi
On Sun, Nov 09, 2008 at 18:13:21 +, Virgo Pärna wrote:
> On Sun, 9 Nov 2008 13:34:21 +0100, Florian Kulzer wrote:
> >
> > modprobe -r ehci_hcd
> >
>
> That did not work for me.
>
> > You could also try if the 2.6.27 kernel improves the situation. (What
> > you report in your other mail in
On Sun, 9 Nov 2008 13:34:21 +0100, Florian Kulzer <[EMAIL PROTECTED]> wrote:
>
> modprobe -r ehci_hcd
>
That did not work for me.
> You could also try if the 2.6.27 kernel improves the situation. (What
> you report in your other mail indicates that WinXP can operate the
>
I quess, I can
On Sun, Nov 09, 2008 at 09:05:33 +, Virgo Pärna wrote:
[...]
> Here is the log:
>
> virsik:~# tail -fn0 /var/log/syslog
[ snip: camera recognized, hal reacts normally, sd driver loaded;
everything looks fine until... ]
> Nov 9 10:54:18 virsik kernel: [ 4016.216143] usb 4-3: reset high s
Additionally - I rebooted my laptop toto Windows XP Home, connected
the camera and copied ~500 MB of video clips and images to computer. It
worked just fine, it took less than a minute to copy and there were no
errors in event log.
--
Virgo Pärna
[EMAIL PROTECTED]
--
To UNSUBSCRIBE, ema
On Sat, 8 Nov 2008 17:27:04 +0100, Florian Kulzer <[EMAIL PROTECTED]> wrote:
>
> tail -fn0 /var/log/syslog
>
> This will list all new messages appearing in the system log. (You can
> exit with CTRL-C.) Then plug in the camera, turn it on, and wait at
> least thirty seconds. Post the syslog messages
On Thu, Nov 06, 2008 at 11:31:25 +, Virgo Pärna wrote:
> On Thu, 30 Oct 2008 09:52:46 +1030, en0f wrote:
> >
> > I am pretty sure this is hardware problem. Check that it works under
> > other OS and make sure the cablings and USB2IDE adapters are OK.
> >
>
> I am having same problem with
On Thu, 30 Oct 2008 09:52:46 +1030, en0f <[EMAIL PROTECTED]> wrote:
>
> I am pretty sure this is hardware problem. Check that it works under
> other OS and make sure the cablings and USB2IDE adapters are OK.
>
I am having same problem with my Pentax Optio E50 digital
compact camera. It work
Hugo Wau wrote:
My external 500 GB USB drive had never worked immediately, but when it
was warmed up, it finally connected and could be used. But now have I
come to a point, that the connection does not work any more - not with
ohci_hcd, nor with ehci_hcd, when the letter "o" (in *o*hci_hcd) ge
My external 500 GB USB drive had never worked immediately, but when it
was warmed up, it finally connected and could be used. But now have I
come to a point, that the connection does not work any more - not with
ohci_hcd, nor with ehci_hcd, when the letter "o" (in *o*hci_hcd) gets
replace by an
On (23/06/03 16:11), Kent West wrote:
>
> Thanks for the response, Clive. Turns out I was doing things the proper
> way; it's just that something was screwy with the MBR I reckon. (hd0
> refers to the first hard drive that the BIOS lists, not to the first
> hard drive on the first IDE port -- g
Clive Menzies wrote:
On (23/06/03 11:22), Kent West wrote:
So I've tried "grub-install /dev/hd0 which complains about hd0 having a
tray open or drive not ready, and that /dev/hd0 does not have any
corresponding BIOS drive.
I may be "barking up the wrong tree" bu
On (23/06/03 11:22), Kent West wrote:
> Date: Mon, 23 Jun 2003 11:22:38 -0500
> From: Kent West <[EMAIL PROTECTED]>
> Subject: tray open or drive not ready
> To: [EMAIL PROTECTED],
> debian users <[EMAIL PROTECTED]>
> Reply-To: [EMAIL PROTECTED]
>
> I&
hat /dev/hdc is
not found or not a block device.
So I've tried "grub-install /dev/hd0 which complains about hd0 having a
tray open or drive not ready, and that /dev/hd0 does not have any
corresponding BIOS drive.
So I cd'd into /dev, and ran "./MAKEDEV hd0", which does
Hi, this is for those who met the same errors
I just have this kind of problem; I was scared about a HD failure,
as many mails are talking about. Since it is an 8 months HD, I was
quite sure is was not a failure.
So I opened the beast and had a look:
it was simply the power supply connector of th
15 matches
Mail list logo
