Re: USB scanner unrecognized on 1.11-DEVELOPMENT

2008-01-16 Thread Francois Tigeot
On Tue, Jan 15, 2008 at 11:06:21AM +0100, Matthias Schmidt wrote:
 
 * Francois Tigeot wrote:
  
  I recently upgraded a machine from Dragonfly 1.10.1 to a recent
  1.11.0-DEVELOPMENT (as of today).
  
  An Epson Perfection 1240U USB scanner which worked fine with 1.10.1 is now
  unrecognized. Pluging and unpluging the USB cord doesn't result in any
  kernel message visible in dmesg.
 
 According to the sources we have an entry for your model:
 
  {{ USB_DEVICE(0x04b8, 0x010b) }, 0 }, /* Perfection 1240U/1240Photo */
 
 I'm currently preparing a mass update of USB quirks and it seems like
 the vendor ID of Epson has changed.  The new entry from FreeBSD device
 ID list looks like this:
 
  {{ USB_DEVICE(0x03f8, 0x010b) }, 0 }, /* Epson Perfection 1240U / */
 
 Note the difference between 0x04b8 and 0x03f8.  To check that I'm not
 wrong, you could change the ID in the uscanner source, recompile the
 module, reload it and check again if the scanner is detected:

I tried it and it didn't change anything: no kernel messages either.

However, I found out there's was a difference between a standalone
uscanner module and one compiled in the kernel.

Standalone module:
- original - nothing
- patched - nothing

Uscanner in kernel:
- original - some kernel messages appear at startup

# dmesg | grep uscanner
uscanner0: EPSON Perfection1240, class 255/255, rev 1.00/1.04, addr 2 
on uhub0
uscanner0: at uhub0 port 2 (addr 2) disconnected
uscanner0: detached

- patched - some messages about ugen0
ugen0: at uhub0 port 2 (addr 2) disconnected
ugen0: detached

There's definitely something fishy going there.

-- 
Francois Tigeot


Re: USB scanner unrecognized on 1.11-DEVELOPMENT

2008-01-16 Thread Simon 'corecode' Schubert

Hasso Tepper wrote:

Francois Tigeot wrote:

However, I found out there's was a difference between a standalone
uscanner module and one compiled in the kernel.

Standalone module:
- original - nothing
- patched - nothing


Note that loading module doesn't rescan devices. You have to unplug and 
plug again the device to rescanning happen.


That sucks.  We should do that, or at least operate on the previously 
detected devices.


cheers
  simon

--
Serve - BSD +++  RENT this banner advert  +++ASCII Ribbon   /\
Work - Mac  +++  space for low €€€ NOW!1  +++  Campaign \ /
Party Enjoy Relax   |   http://dragonflybsd.org  Against  HTML   \
Dude 2c 2 the max   !   http://golden-apple.biz   Mail + News   / \



Re: USB scanner unrecognized on 1.11-DEVELOPMENT

2008-01-16 Thread Sepherosa Ziehau
On Jan 16, 2008 8:14 PM, Simon 'corecode' Schubert
[EMAIL PROTECTED] wrote:
 Hasso Tepper wrote:
  Francois Tigeot wrote:
  However, I found out there's was a difference between a standalone
  uscanner module and one compiled in the kernel.
 
  Standalone module:
   - original - nothing
   - patched - nothing
 
  Note that loading module doesn't rescan devices. You have to unplug and
  plug again the device to rescanning happen.

 That sucks.  We should do that, or at least operate on the previously
 detected devices.

I think USB devices are different than PCI/cardbus devices;
Unrecognized devices are taken by ugen.

Best Regards,
sephe

-- 
Live Free or Die


Re: USB scanner unrecognized on 1.11-DEVELOPMENT

2008-01-16 Thread Simon 'corecode' Schubert

Sepherosa Ziehau wrote:

On Jan 16, 2008 8:14 PM, Simon 'corecode' Schubert
[EMAIL PROTECTED] wrote:

Hasso Tepper wrote:

Francois Tigeot wrote:

However, I found out there's was a difference between a standalone
uscanner module and one compiled in the kernel.

Standalone module:
 - original - nothing
 - patched - nothing

Note that loading module doesn't rescan devices. You have to unplug and
plug again the device to rescanning happen.

That sucks.  We should do that, or at least operate on the previously
detected devices.

I think USB devices are different than PCI/cardbus devices;
Unrecognized devices are taken by ugen.


Then devices should be probed and if there is a better match than ugen and 
if the ugen device is not open, it should be detached from ugen and 
attached to the new driver.  Do you think this would be possible?


cheers
  simon

--
Serve - BSD +++  RENT this banner advert  +++ASCII Ribbon   /\
Work - Mac  +++  space for low €€€ NOW!1  +++  Campaign \ /
Party Enjoy Relax   |   http://dragonflybsd.org  Against  HTML   \
Dude 2c 2 the max   !   http://golden-apple.biz   Mail + News   / \



Re: USB scanner unrecognized on 1.11-DEVELOPMENT

2008-01-16 Thread Francois Tigeot
On Wed, Jan 16, 2008 at 12:45:49PM +0200, Hasso Tepper wrote:
 Francois Tigeot wrote:
  However, I found out there's was a difference between a standalone
  uscanner module and one compiled in the kernel.
 
  Standalone module:
  - original - nothing
  - patched - nothing
 
 Note that loading module doesn't rescan devices. You have to unplug and 
 plug again the device to rescanning happen.

Ok. I'm not sure I did that with standalone modules.

  Uscanner in kernel:
  - original - some kernel messages appear at startup
 
  # dmesg | grep uscanner
  uscanner0: EPSON Perfection1240, class 255/255, rev 1.00/1.04, addr
  2 on uhub0 uscanner0: at uhub0 port 2 (addr 2) disconnected
  uscanner0: detached
 
 It's a disconnect message only.
 
  - patched - some messages about ugen0
  ugen0: at uhub0 port 2 (addr 2) disconnected
  ugen0: detached
 
 It's a disconnect message again only. And it shows that there is no need 
 for patch. Show me the full dmesg with verbose booting, please.

I have put a dmesg dump here (uscanner in kernel) :
http://www.wolfpond.org/dmesg-dfly-1.11-verbose.txt

I have disconnected and reconnected the scanner just after dumping this
file.
There were only this additional messages:

uscanner0: at uhub0 port 2 (addr 2) disconnected
uscanner: ops removed
uscanner0: detached

-- 
Francois Tigeot


USB scanner unrecognized on 1.11-DEVELOPMENT

2008-01-15 Thread Francois Tigeot
Hi,

I recently upgraded a machine from Dragonfly 1.10.1 to a recent
1.11.0-DEVELOPMENT (as of today).

An Epson Perfection 1240U USB scanner which worked fine with 1.10.1 is now
unrecognized. Pluging and unpluging the USB cord doesn't result in any
kernel message visible in dmesg.

I know the USB stuff has been heavily refactored since the last release.
How can I proceed to debug this ?

-- 
Francois Tigeot


Re: USB scanner unrecognized on 1.11-DEVELOPMENT

2008-01-15 Thread Steve O'Hara-Smith
On Tue, 15 Jan 2008 11:06:21 +0100
Matthias Schmidt [EMAIL PROTECTED] wrote:

 I'm currently preparing a mass update of USB quirks

Sorry for the hijack - but could you include this one :)

Index: sys/bus/cam/scsi/scsi_da.c
===
RCS file: /home/dcvs/src/sys/bus/cam/scsi/scsi_da.c,v
retrieving revision 1.52
diff -u -r1.52 scsi_da.c
--- sys/bus/cam/scsi/scsi_da.c  2 Dec 2007 16:38:11 -   1.52
+++ sys/bus/cam/scsi/scsi_da.c  7 Jan 2008 12:16:18 -
@@ -554,6 +554,13 @@
{T_DIRECT, SIP_MEDIA_REMOVABLE, ChipsBnk, USB*,
 *}, /*quirks*/ DA_Q_NO_SYNC_CACHE
},
+   {
+   /*
+* USB 2.0 (HS) Flash Disk MP3 player doesn't like sync cache
+*/
+   {T_DIRECT, SIP_MEDIA_REMOVABLE, USB 2.0, (HS) Flash Disk, 
*},
+   /*quirks*/ DA_Q_NO_SYNC_CACHE
+   },
 };
 
 static d_open_tdaopen;

-- 
C:WIN  |   Directable Mirror Arrays
The computer obeys and wins.| A better way to focus the sun
You lose and Bill collects. |licences available see
|http://www.sohara.org/


Re: USB scanner unrecognized on 1.11-DEVELOPMENT

2008-01-15 Thread Matthias Schmidt
* Steve O'Hara-Smith wrote:
 
   It may help to know that I am running a recent 1.11.0 (Jan 12 or
 thereabouts) which does recognise my Perfection 1240U and it works (quick
 test, I haven't had to use it in a while).

Could you please post the dmesg output (if there is any :)?

Matthias


Re: USB scanner unrecognized on 1.11-DEVELOPMENT

2008-01-15 Thread Steve O'Hara-Smith
On Tue, 15 Jan 2008 10:24:59 +0100
Francois Tigeot [EMAIL PROTECTED] wrote:

 Hi,
 
 I recently upgraded a machine from Dragonfly 1.10.1 to a recent
 1.11.0-DEVELOPMENT (as of today).
 
 An Epson Perfection 1240U USB scanner which worked fine with 1.10.1 is now
 unrecognized. Pluging and unpluging the USB cord doesn't result in any
 kernel message visible in dmesg.

It may help to know that I am running a recent 1.11.0 (Jan 12 or
thereabouts) which does recognise my Perfection 1240U and it works (quick
test, I haven't had to use it in a while).

-- 
C:WIN  |   Directable Mirror Arrays
The computer obeys and wins.| A better way to focus the sun
You lose and Bill collects. |licences available see
|http://www.sohara.org/


Re: USB scanner unrecognized on 1.11-DEVELOPMENT

2008-01-15 Thread Steve O'Hara-Smith
On Tue, 15 Jan 2008 15:02:33 +0100
Matthias Schmidt [EMAIL PROTECTED] wrote:

 * Steve O'Hara-Smith wrote:
  
  It may help to know that I am running a recent 1.11.0 (Jan 12 or
  thereabouts) which does recognise my Perfection 1240U and it works
  (quick test, I haven't had to use it in a while).
 
 Could you please post the dmesg output (if there is any :)?

Sure - there's not a lot:

uscanner0: EPSON Perfection1240, class 255/255, rev 1.00/1.04, addr 6 on
uhub3

Also from usbdevs -v 

  port 2 addr 6: full speed, self powered, config 1, Perfection1240
(0x010b), EPSON(0x04b8), rev 1.04

-- 
C:WIN  |   Directable Mirror Arrays
The computer obeys and wins.| A better way to focus the sun
You lose and Bill collects. |licences available see
|http://www.sohara.org/