Re: problems mounting usb device in FBSD 7.1 [almost complete solution]



On Sun, 22 Feb 2009 20:09:38 -0600, DaveG <nospam@xxxxxxxxxx> wrote:

On Sun, 22 Feb 2009 22:04:17 +0000, Chris wrote:

On Sun, 22 Feb 2009 15:42:17 -0600, DaveG <nospam@xxxxxxxxxx> wrote:

On Sun, 22 Feb 2009 20:49:28 +0000, Chris wrote:

On Sun, 22 Feb 2009 12:08:22 -0600, DaveG <nospam@xxxxxxxxxx> wrote:

On Thu, 12 Feb 2009 19:45:36 +0000, DaveG wrote:

Sort of fixed. There was a typo in devfs.rules. Why it worked from
the command line and not from the script still escapes me. Maybe
devfs.conf had something to do with it.

But, now it won't download pics from the camera without corrupting
them. This might be a USB2/USB1 issue. The mount command is exactly
as used on my FBSD5.5 system. The first JPeG image partially
downloads, ie the first 5% or so is decodable. Any further image
files are so corrupt that nothing can decode them.

Anyone seen this sort of thing before and solved it?

OK, I've eliminated almost everything. csup'ed source, rebuilt
GENERIC as a custom kernel (removing ehci as well all the debug/trace
settings, unwanted SCSI/RAID/Ethernet stuff, *NOT* the scsi stuff
required for USB though), rebuilt world, put all the devfs stuff back
to defaults and test mounted both the camera and a pendrive.

Files still get corrupted when reading/copying from them.

The one remaining item which is different is a PCI USB2.0 card I
added just before installing 7.1 (the devices are not plugged into
it). This has no effect on my 5.5Stable install still sitting there
on the other HDD. I can boot that, and have done a number of times,
and copy files from the camera with no problems, both as root and as
a user with correct devfs settings.

I'll pull the PCI USB card tonight and see what happens.


If you know what you are doing, try to play with cvsup and bring in
patches which were either added or removed and pinpoint where the
problem started with a patch that was added, then you can speak to the
person who added that patch and either have it reverted or fixed.

Playing with it for days will not fix the problem without any
hackering. Something broke the code.

I can see your point in suggesting that, but since no one else seems to
have seen this problem, it seems more likely to be me who is the source
of the problem.

As Warren suggested, I've tested the RAM and memtest was well through
test#9 before I killed it. That suggests to me that the RAM and it's
underlying hardware are all fine unless it's a far more exotic RAM
error than anything I've come across before. RAM errors almost always
show up no later that test#4 on memtest86.

I'm going to drop in a spare hard disk now and do a clean, minimal
install of 7.1 and see what happens.


I forgot to mention also that I always had issues looking at photos in
PTP mode and always had to use Disk Mode on Free or Linux so maybe that
can help some. If your camera has the ability to change that.

Chris, your various points made me look a little more closely. Or maybe
I stepped back. Either way, I spotted the difference at last! :-)

It appears something has certainly changed either in the main USB stack
or in the support for the SiS USB chipset because USB2 devices now work
at USB2 speeds.

The upshot is that *some* USB1.0 devices are no longer detected correctly
and the USB2.0 chipset doesn't fallback gracefully.

I've been testing with my Fuji Finepix E500 camera and an old USB
pendrive, both of which are USB1.0 devices. I didn't dare to plug in my
USB2.0 pendrive as that contains some important files. Anyway, I took a
chance on the newer USB2.0 pendrive, and not only did it work, but it
registered properly as a USB2.0 device with transfers reported on plug as
being capable of 40MB/s. Wow. It never did that before.

FBSD 5.5 and the SiS chipset only ever ran at USB1.0 speeds.

Anyway, a quick dig around found a USB2.0 powered external hub. I
plugged the camera into that and file transfers, at USB1.0 speeds, now
work just fine. I have no idea what made me try the hub though. Maybe I
read something about that some time ago and ignored it as not applicable
(ie I may have read it before I came across the problem)

Anyway, it's a workable workaround.

I guess I should just thank a certain mail order supplier who mistakenly
chucked a USB hub into my box when I ordered some other bits. I never
knew I might need one. It wasn't on the order, the picking list or the
invoice. :-)


Like I said before FreeBSD is a stable OS but it has very poor USB support. All my servers have this disabled as it causes problems. Glad some of my advice helped you :)

--
Using Opera's revolutionary e-mail client: http://www.opera.com/mail/
.



Relevant Pages

  • Re: problems mounting usb device in FBSD 7.1 [almost complete solution]
    ... now it won't download pics from the camera without corrupting ... I'll pull the PCI USB card tonight and see what happens. ... I've tested the RAM and memtest was well through ...
    (comp.unix.bsd.freebsd.misc)
  • Re: USB cable
    ... When I plug my mp3 or camera cable into the usb socket it freezes my ... download any music or download my photos, ... Plug in the USB camera. ... Un-plug it and re-boot. ...
    (microsoft.public.windowsxp.music)
  • Re: Scanner and Camera Problems
    ... I can download the photos from the camera using the USB connector. ... the software from HP as well as the camera and scanner wizard. ...
    (microsoft.public.windowsxp.photos)
  • Re: Does Canon Powershot use battry power when on USB lead
    ... actually run the camera, but may power the USB interface circuitry inside. ... download using the PC control. ...
    (rec.photo.digital)
  • Re: No Video from encoder
    ... I tested bia Fireware versus USB. ... PLAY mode (versus CAMERA mode, ... real-life video via MSN, Yahoo and via WME 9 in Input tab, I do see myself! ...
    (microsoft.public.windowsmedia.encoder)