From: "Robert J. Bell" <rob@bellfamily.org>
To: Matthew Dharm <mdharm-kernel@one-eyed-alien.net>
Cc: kernel-list <linux-kernel@vger.kernel.org>
Subject: Re: USB Mass Storage in 2.4.0
Date: Fri, 12 Jan 2001 17:34:32 -0800 [thread overview]
Message-ID: <3A5FB0A8.4040506@bellfamily.org> (raw)
In-Reply-To: <3A5F8956.9040305@bellfamily.org> <20010112151008.A5798@one-eyed-alien.net> <3A5F9108.4030706@bellfamily.org> <20010112152415.B5798@one-eyed-alien.net> <3A5F9491.20109@bellfamily.org> <20010112161347.A6792@one-eyed-alien.net>
[-- Attachment #1: Type: text/plain, Size: 1483 bytes --]
No luck using the standard UHCI driver, attached logs.
Matthew Dharm wrote:
> Do you have an OHCI controller or an UHCI controller? I noticed that
> you're using the "alternate" UHCI driver... can you try this with the
> standard UHCI driver?
>
> Matt
>
> On Fri, Jan 12, 2001 at 03:34:41PM -0800, Robert J. Bell wrote:
>
>> Unfortunately I lost everything on my system (the one that worked) and I
>> don't believe I ever looked in /proc/scsi/scsi because It was working
>> and I didn't feel the need to go poking around. I had this problem
>> initially the first time I compiled 2.4.0 but I went back and added SCSI
>> Generic "on" and that seemed to fix it. I am just confused why it
>> thinks this is a scanner. IS there any way to force it to detect it as a
>> scsi disk?
>>
>> I must have recompiled this kernel 50 times trying to recreate the the
>> scenario where this worked. I can send you my .config if you think that
>> will help.
>>
>> Robert
>>
>>
>>
>>
>>
>> Matthew Dharm wrote:
>>
>>> Hrm... from these logs, everything looks okay, except for the fact that the
>>> device refuses to return any INQUIRY data.
>>>
>>> Can you reproduce the conditions under which it was working and send logs
>>> from that? Or at least remember what the /proc/scsi/scsi info looked like?
>>>
>>> Matt
>>>
>>> On Fri, Jan 12, 2001 at 03:19:36PM -0800, Robert J. Bell wrote:
>>>
>>>> Matthew here is the info you requested, thanks for your help.
>>>>
>>>>
[-- Attachment #2: dmesg2.out --]
[-- Type: application/octet-stream, Size: 3349 bytes --]
[-- Attachment #3: mesg.out --]
[-- Type: application/octet-stream, Size: 760 bytes --]
Jan 12 17:25:17 t20 PAM_unix[648]: (login) session opened for user root by LOGIN(uid=0)
Jan 12 17:25:17 t20 -- root[648]: ROOT LOGIN ON tty1
Jan 12 17:26:13 t20 kernel: usb.c: USB disconnect on device 2
Jan 12 17:26:13 t20 kernel: usb-uhci.c: interrupt, status 3, frame# 1060
Jan 12 17:26:55 t20 kernel: hub.c: USB new device connect on bus1/1, assigned device number 3
Jan 12 17:26:55 t20 kernel: Product: USB Mass Storage
Jan 12 17:26:55 t20 kernel: SerialNumber: Y-170^^^^^000810X0000003005237
Jan 12 17:26:55 t20 kernel: scsi0 : SCSI emulation for USB Mass Storage devices
Jan 12 17:26:55 t20 kernel: Vendor: à-À ÀòÏ Model: \206 Øÿ-À¡# À ÝòÏ Rev: ÿÿÿÿ
Jan 12 17:26:55 t20 kernel: Type: Scanner ANSI SCSI revision: 02
next prev parent reply other threads:[~2001-01-13 1:34 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-01-12 22:46 Robert J. Bell
2001-01-12 23:10 ` Matthew Dharm
2001-01-12 23:19 ` Robert J. Bell
2001-01-12 23:24 ` Matthew Dharm
2001-01-12 23:34 ` Robert J. Bell
2001-01-13 0:13 ` Matthew Dharm
2001-01-13 1:34 ` Robert J. Bell [this message]
2001-01-14 19:46 ` Jamie Lokier
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=3A5FB0A8.4040506@bellfamily.org \
--to=rob@bellfamily.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mdharm-kernel@one-eyed-alien.net \
/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
all inboxes | Powered by JetHome®