On Tue, 16 Dec 2003, Cornelius Claussen wrote:
> > As for eliminating the I/O errors, well, there's no way to do it. It's
> > not a fault of the driver or of Linux; it's the fault of your DVD drive or
> > disc. They just sometimes get transient errors. The best we can hope to
> > do is recover
Am Dienstag, 16. Dezember 2003 20:49 schrieben Sie:
> Actually this is quite different from what you posted before. In the old
> log you got multiple errors in multiple sectors. In this log there's just
> a single error, and the read operation gets retried so in the end the
> error doesn't matter
SPINNING + MUSCULAÇÃO
+ GINÁSTICA =
Plano anual (doze meses). (+ O
mês de aniversario de graça) = 13
meses.Valor do mês R$
46.15 (Quarenta e seis reais e quinze
centavos).Valido para spinning, musculaçã
On Tue, 16 Dec 2003, Cornelius Claussen wrote:
> Hi Alan,
>
> thank you for the patch, but unfortunately it doesn't solve the problem.
> There are still I/O errors from time to time, see attached log file.
Actually this is quite different from what you posted before. In the old
log you got mult
...
kobject 'devices' does not have a release() function, it is broken and must be fixed.
...
this happens if I rmmod usb modules, like:
pear:~ # rmmod hid {e,o,u}hci_hcd ; umount -v usbdevfs && rmmod -v
usbcore
ERROR: Module hid does not exist in /proc/modules
ERROR: Module ehci_hcd does not exis
Am Dienstag, 16. Dezember 2003 18:13 schrieb Alan Stern:
> This patch does what James Bottomley suggested. Try using it instead of
> the one I sent to Matthias Geissert (that one is included in here). Let
> me know if it helps solve your problems.
>
> Alan Stern
Hi Alan,
thank you for the patch
I've been thinking some more about this. Although the driver is
apparently at fault here by issuing a reset without telling the
mid-layer, it might be useful to filter out other common ASC/ASCQ codes
in scsi_io_completion() we retry on "in the process of becoming ready",
then for any other UNIT_AT
Hello Pat,
What is the current direction and state of USB Device,
or USB Client, development for the latest Linux 2.4 kernels
and beyond?
Well the 2.4 and 2.6 kernels have merged the "USB Gadget"
API, and there have already been several drivers contributed
to that framework ... both for controller
On Mon, 15 Dec 2003, AAZ wrote:
> > It looks like the macro version of usb_settoggle() is correct. We see
> >
> >printk(KERN_WARNING "Mio: %x %x {%x} %x {%x}\n"
> > ,ep
> > , (ps->dev)->toggle[!(ep & USB_DIR_IN)]
> > ,((ps->dev)->toggle[!(ep & USB_DIR_IN)] & ~( 1 << ep &
On 15 Dec 2003, James Bottomley wrote:
> It looks like the driver sent a reset to the device on its own without
> reporting it to the mid-layer.
>
> There's an expecting_cc_ua flag in the scsi_device. It gets set on
> error recovery actions, or if the device does something to detect or
> trigger
Hello Everyone,
What is the current direction and state of USB Device,
or USB Client, development for the latest Linux 2.4 kernels
and beyond?
I know of work done by Belcarra (ex-Lineo) folks which
provides a USB Device stack and a set of functions. I've also
seen the announcement of the Gadget
On Tue, 16 Dec 2003, glenn lawyer wrote:
> Hi,
>
> Re-compiled the kernel with gcc296, the kernel bug is gone. Sorry to
> take your time with that.
>
> Still have the same problem with the camera (as my last message), but I
> noticed one new twist. When I have the memory-stick pro, mount says:
Hi all,
ISD200 based IDE harddrive bay doesn't work. This problem
was already discussed some time ago (before 2.5.67) and
patch was included in 2.5.67 to fix it. Unfortunately this
harddrive bay isn't mine and I got it for testing only
yesterday.
Kernel message log attached (compressed because it
Hi everyone!
I'm just starting to make my own USB devices with the Microchip PIC16c745
microcontroller.
For those who don't already know, the 16c745 is a low-speed only device,
and hence limited to control and interrupt endpoints.
I'll be making various kinds of IO devices and for ease of use I'
Hi,
Re-compiled the kernel with gcc296, the kernel bug is gone. Sorry to
take your time with that.
Still have the same problem with the camera (as my last message), but I
noticed one new twist. When I have the memory-stick pro, mount says:
~/temp :)mount /dev/sda /mnt/camera/ -t vfat
mount: wro
好消息！站长快抢！
电影+电子书+Flash+软件的网站！4级下线制、长期免费拥有，免费注册开始啦！机不可失！！快快抢注！！！
加入四级下线制！帮您赚钱永无限！
长期免费――
1：看电影；2：下载书籍 3：赏玩Flash;4:下载软件； 5：获赠一个网站；
6：获赠网站推广经验；
本站吸收免费代理站长时间：2003.12.2日――2003.12.27日23.59分结束,15日零点正式开始进入收费期.
http://www.100wy.com/index.asp?userid=tonm
On Mon, Dec 15, 2003 at 11:35:33PM +, Johann Deneux wrote:
> Attached is a patch doing two things:
> hid-lgff.c: Fixes an obvious list handling issue.
> hid-core.c: - Use INT out urbs instead of bulk out urbs. That's the way
> it should be
> - Remove some report->id magic.
>
> IMP
Hi, again,
Stephen suggests:
What is in your log files when you load the driver? DO you have scsi disk
and generic in your kernel?
Ok, I just re-compiled the kernel. Previously I had the following as
modules, now they are included:
SCSI device support
SCSI disk support
SCSI generic support
U
>From 2.4.23 (same thing with 2.6.0-test11):
struct iso_packet_descriptor
{
unsigned int offset;
unsigned int length;// expected length
unsigned int actual_length;
unsigned int status;
};
where status is used for storing Linux error code. However, since
Hi folks,
following my recent posts on libusb-devel and hidups, here's
a patch to disable hiddev support for MGE UPSs. It only
declares VID/PID as QUIRK_IGNORE in hid-core's blacklist.
This simply prevent hiddev to be loaded when plugging
an MGE UPS.
As always, due to my brain damaged Notes mai
From: Mrs Serena Jones
PLEASE ENDEAVOUR TO USED IT FOR THE CHILDREN OF GOD.
I am the above named person from Kuwait. I am married to Dr.
Harry Jones who worked with Kuwait embassy in Ivory Coast for nine years
before he died in the year
2000.
We were married for eleven years
21 matches
Mail list logo
