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



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.

--
DaveG
The above post is ROT13 encoded, twice for extra protection.
.



Relevant Pages

  • Re: problems mounting usb device in FBSD 7.1 [partial solution]
    ... the command line and not from the script still escapes me. ... now it won't download pics from the camera without corrupting ... underlying hardware are all fine unless it's a far more exotic RAM error ...
    (comp.unix.bsd.freebsd.misc)
  • Re: How to compile Ruby on Windows
    ... Download and install the following: ... Download the latest Ruby release from: ... Uncompress the download into a folder that doesn't have any spaces in the name. ... change the command inside the double-quotes of IO.foreach. ...
    (comp.lang.ruby)
  • Re: unable to update
    ... the others seem to download and install using "Custom" just fine. ... > Restart the system and check out Windows update again. ... > the following command ...
    (microsoft.public.windowsupdate)
  • Re: Error 0x800703e3 when trying to install Windows update program
    ... (note the space after regsvr) ... download the WindowsUpdateAgent20-x86.exe and save it to the Desktop - ... If it says "Install is not needed since Windows Update Agent is ... The command line will appear as ...
    (microsoft.public.windowsupdate)
  • Re: [SLE] Weird RealPlayer Problem
    ... > If you look at the bottom of the above page, ... Download all of these files ... Command line is no problem, ... > download the files and you'll get the option with each one to install ...
    (SuSE)