Talkback for article: 240, May2002

Using the Minolta Dimage 5 camera under Linux

Back to: http://cgi.linuxfocus.org/English/May2002/article240.shtml

From: Michael Schroeder <mi.schroeder(at)gmx.de> [ date: 2002-05-03 ]
thanks to this article i managed to run the
Minolta Dimage S404 camera under Linux.
Just replace (or insert) the following lines in
the file:unusual_devs.h:

UNUSUAL_DEV(0x0686,0x400a,0x0001,0x0001,
"Minolta",
"Dimage S404",
US_SC_SCSI,US_PR,BULK,NULL,US_FL_START_STOP),
From: Frank Miles [ date: 2002-05-03 ]
It's my understanding that Minolta image data is not in the standard
RGB space. Has anyone figured out how to correct the color of these
images?
From: guido socher [ date: 2002-05-04 ]
Hello Fank,
when you strore the images on the compact flash card as tiff or jpg files
(that's the normal case) then you will have no problems use the images
with any Linux software. I don't think that Minolta uses a non standard
RGB space. Colors are OK.
From: Jan Hugo Prins [ date: 2002-05-07 ]
Hello,

Minolta does use a different RGB format then normal and in the software that Minolta delivers with their camera's they do some collour corrections for there images. The exact transformation they do is documented somewhere and I already heard that someone had made something in Gimp to do the transformation but I can't find it at the moment. Read the the messages in www.dpreview.com.

From: Peter V. Pretsch [ date: 2002-05-14 ]
I think this is the page you are looking for:

http://dimage-color.sourceforge.net/

But if you compare the images that it generates to the DiMage Viewers output then you will notice that the images differs a lot.It looks like the gimp plugin has some kind of rounding issue, which can be seen by the fact that values are missing in the Histogram.
From: James Addison <addi(at)slodoun.com> [ date: 2002-05-19 ]
This is the perfect article for someone trying to set up one of these great cameras.

It took me about 30 mins to get the USB connection up and running, and then another couple of hours to get the GIMP running with the RGB colour space converter plugin.

Minolta does in fact use a different colourspace, however, if I were to guess, I would say that it is only for *.MRW or *.TIFF and not for *.JPG. (MRW is for Minolta Raw, I would guess). Correct me if I'm wrong, but the JPEGs don't seem to suffer from this colourspace issue...

James
From: Seth W. Klein <sk(at)sethwklein.net> [ date: 2002-06-05 ]
It is no longer best to make symlinks from /usr/include to /usr/src/linux/...; the directories should be copied instead. For the reason, see the FAQ item at http://www.linuxfromscratch.org/faq/#AEN494 which points to a post by Linus and the Kernel Traffic issue covering the thread in which it occurred.
From: guido socher [ date: 2002-06-06 ]
There seems to be an issue with the Minolta firmware reporting
a too small block size (probably windows ignores it):
attempt to access beyond end of device
rw=0, want=64346, limit=62576

Has anybody else seen this?
I will try to write a kernel patch to fix it (... or does anybody know about a patch).
The effect is basically that you can only read the first 62Mb of any
compact flash card.
From: Mike Seymour <michael.seymour at wanadoo fr> [ date: 2002-06-19 ]
Hi

Thanks for the page. After flailing around for a
couple of nights, your very informative page
helped me to get our first images off our new
Olympus 3020Z digital camera. I use Mandrake
8.1 which already has all the hotplug/usb etc
stuff setup, so it was just a case of mounting
the camera correctly.

Mike
From: guido socher [ date: 2002-06-26 ]
Concering the firmware problem [ see above date: 2002-06-06 ]:
I finally traced it down to a problem of the formatting program
inside the dimage 5.
The problem goes if you format the card with the linux command mkdosfs
(or format under win98, that's what others have told me. I don't have
windows).

I first had this printout (with a 128Mb card):
Jun 26 21:10:44 sophus kernel: attempt to access beyond end of device
Jun 26 21:10:44 sophus kernel: 08:11: rw=0, want=130866, limit=125040
Jun 26 21:10:44 sophus kernel: attempt to access beyond end of device
Jun 26 21:10:44 sophus kernel: 08:11: rw=0, want=130867, limit=125040
Jun 26 21:10:44 sophus kernel: attempt to access beyond end of device
Jun 26 21:10:44 sophus kernel: 08:11: rw=0, want=130867, limit=125040
Jun 26 21:10:44 sophus kernel: Filesystem panic (dev 08:11).
Jun 26 21:10:44 sophus kernel: FAT error
Jun 26 21:10:44 sophus kernel: Directory 368: bad FAT


Then I used mkdosfs /dev/sda1
and filled the card again full with pictures. The probem was gone.

The card should be formatted with FAT16.

From: guido socher [ date: 2002-06-26 ]
If you want to read out image information like data and time, shutter
speed and f-stop used when taking the picture ....
Then take a look at:
http://sourceforge.net/projects/libexif/

From: Robert Irving <robert(at)juggling.co.uk> [ date: 2002-07-19 ]
I am using Mandrake 8.2. Everything goes very well and in accordance with the instructions until I get to "fdisk -l /dev/sda" at which point the camera reports that the USB connection has been disconnected.

I am at a loss. Anyone any idea?

Robert
From: guido [ date: 2002-07-21 ]
Hello Robert,
what kind of Kernel is used for Mandrake 8.2. Try a more recent
Kernel. This is not how it should be.


From: Filip <fmechant(at)yahoo.com> [ date: 2002-07-23 ]
Hello,

works also for the Dimage 7i if used with the following code:

UNUSUAL_DEV( 0x0686, 0x400b, 0x0001, 0x0001,
"Minolta",
"Dimage 7i",
US_SC_SCSI, US_PR_BULK, NULL,
US_FL_START_STOP ),

Notice the different prodID compared to the Dimage 7.

I had the same problem on my RedHat 7.3. Every thing was ok, until I tried to mount the device. Then it would disconnect.

Recompiled the kernel with the above change, and everything worked.
Recompiling RedHat is covered in The Official Red Hat Linux Customization Guide (Appendices).

Thanx for the push in the back.
Filip.
From: Marco [ date: 2002-07-25 ]
Guido, I'm in trouble...
I've won a Fujifilm Ix-30 Camera which works as a Mass Storage but I can't make it works...

PLEASE HELP ME
From: Marco (again...) [ date: 2002-07-25 ]
This is my devices file...

C:* #Ifs= 1 Cfg#= 1 Atr=e0 MxPwr=100mA
I: If#= 0 Alt= 0 #EPs= 1 Cls=09(hub ) Sub=00 Prot=00 Driver=hub
E: Ad=81(I) Atr=03(Int.) MxPS= 1 Ivl=255ms
T: Bus=01 Lev=02 Prnt=02 Port=03 Cnt=01 Dev#= 3 Spd=12 MxCh= 0
D: Ver= 1.10 Cls=00(>ifc ) Sub=00 Prot=00 MxPS=64 #Cfgs= 1
P: Vendor=0461 ProdID=081a Rev= 1.10
S: Manufacturer=PRIMAX
S: Product=ix-30
C:* #Ifs= 1 Cfg#= 1 Atr=a0 MxPwr=500mA
I: If#= 0 Alt= 0 #EPs= 2 Cls=ff(vend.) Sub=06 Prot=50 Driver=(none)
E: Ad=81(I) Atr=02(Bulk) MxPS= 64 Ivl= 0ms
E: Ad=05(O) Atr=02(Bulk) MxPS= 64 Ivl= 0ms

As you can see, the camera is recognised by Linux, but with no driver. How could I use it? What should I mount?
From: Rob van den Berg [ date: 2002-08-05 ]
Thank you for your information. Just following the steps it wasn't that hard to get it working. I never tried to compile a new kernel but this was a good time to do so (using RedHat 7.3).
After downloading the first pictures from my Minolta Dimage S404 via Linux, I was amazed. It works 5-6 times faster then it did under Windows98SE with the Minolta driver!!!
From: Irwin Hutchinson <ihutch(at)operamail.com> [ date: 2002-08-08 ]
I have a Dimage5 and Suse8. I cannot find the file unusual_devs.h in my system. Do I have to make this file?
My system "sees' the camera as it is listed in my devices file, but when I try to mount it I get the message "No media found"
Can you help please.
From: Rob van den Berg [ date: 2002-08-08 ]
Irwin,
You probably did not install the kernel-source and kernel-headers.
From: Linards Skuja <nospam_skuja(at)cfi.lu.lv> [ date: 2002-08-10 ]
With Mandrake 8.2 and with Sony DSC85 camera ("USB storage class") everything worked fine without kernel recompilation. Just the entries in fstab and mounting were necessary, as described in your advice. Many thanks!
From: patrice <polypa(at)free.fr> [ date: 2002-09-06 ]
i am triyng to connect a Minolta Dimage S404 under Mandrake 8.2
The camerais seen as a scsi disk under /dev/sda
When i try to mont /dev/sda3 /dev/camera0 ( vfat,rw,noauto,user 0 0),
it disconnects and mount returns bad fs type,bad superblock on /dev/sda,
or too many file systems

Any one as an idea ??

Thanks !
From: Dusan <dule(at)mijavec.com> [ date: 2002-09-17 ]
I am running RedHat 7.3 and trying to connect Dimage 5
recompile kernel no problem, can see camera in /proc/bus/usb and even can see it in scsi list. If I try to connect mount return bad fs type,bad superblock on /dev/sda1 or to many file systems and disconnect from camera
If I try fith fdisk -l /dev/sda camera disonnect
Thank you
From: sebi <huberse(at)phys.ethz.ch> [ date: 2002-09-24 ]
Thank you for your page and all your comments. thanks to filip for your information concerning dimage 7i.

After some minor problems my 7i is now working perfectly with SuSE 8.0.
From: guido socher [ date: 2002-10-13 ]
From the talkbacks above I can see that a number of people
get disonnect when they run fdisk -l /dev/sda.
This happens when don't re-compile the Kernel or you did not install the
new Kernel module.
Minolta does not follow the usb standard. That's why
you need to add the US_FL_START_STOP in unusual_devs.h

There is simply no shortcut.
Philip has written a really detailed article on how to compile the Kernel:
http://linuxfocus.org/English/July2002/article252.shtml
From: Michael Lindner <mikel(at)att.net> [ date: 2002-11-01 ]
After a frustrating time trying to get the Minolta SW loaded under Windows 98,
and a frustrating time trying to get Gphoto2 working with my 7i, a Google search
led me here, and I'm glad it did. a few lines changed in a couple of files, a
kernel recompile, and I can upload everything easily. Thanks!
From: Irwin Hutchinson <ihutch(at)operamail.com> [ date: 2002-11-05 ]
Thanks for this article, I got my Dimage 5 working under Linux so now I can get rid of Microdaft windows for good. But your comment that changing the unususl_devs.h file was the hard part was a bit misleading, I presume that was a joke. For me compiling my first kernel was the hard part but thanks to Philip de Groot's article in Linuxfocus July 02 I even accomplished that.
From: Huopa <huopa(at)skyscrapers.com> [ date: 2002-11-11 ]
My Dimage 7i works also fine with these instructions and the occasional kernel crashing problems while mounting with Dimage 5 are now gone. I don't know what caused the Dimage 5 mounting to crash the kernel randomly (1 in 10 mounts or so), but 7i is working superb. Thanks to all.
From: Huopa <huopa(at)skyscrapers.com> [ date: 2002-11-28 ]
Some problems appeared with my Dimage 7i. It has this same trouble as Dimage 5 with big 128MB flash cards. I tried the hint and tried to format the card using mkdosfs, but it didn't help. With default settings it formatted my card into 16MB size and I have no idea what is the trouble with it. I tried to format with bigger sector size and then my camera firmware crashes every time I insert the card and turn on the camera.

I have Toshiba 128MB cards and when formatting with mkdosfs it outputs this:

/dev/sda1 has 1 head and 31 sectors per track,
logical sector size is 512,
using 0xf8 media descriptor, with 31328 sectors;
file system has 2 16-bit FATs and 4 sectors per cluster.
FAT size is 31 sectors, and provides 7808 clusters.
Root directory contains 512 slots.
Volume ID is 3de63596, no volume label.

as you can see 512bytes/sector x 31328 sectors = 16MB, when it should be 128MB. The camera formatting gives 128MB, but where is the difference?
From: guido [ date: 2002-11-29 ]
Hello Huopa,
I bought now a 256Mb card and there I had no other option
than to find a windows computer and format the card there. After that
I had no problems at all. I don't know what's wrong with the filesystem.
But the problem definitly comes from the filesystem because now I can
access the entire card. I just have to remember to not format it
with the camera.
From: guido [ date: 2002-11-29 ]
If you are afraid to update your linux kernel then check this:
http://main.linuxfocus.org/~guido/kernel.html

There is no risk as long as you do not overwrite the kernel that
you currently have.
From: Gábor Szentiványi <szenti(at)suselinux.hu> [ date: 2002-12-03 ]
Does anyone know the 7Hi, F100, X, Xi parameters for the UNUSUAL_DEV?



From: Gary James <gary_r_james(at)yahoo.com> [ date: 2003-01-01 ]
Thanks for the article on how you connected your
Minolta Dimage 5 to linux as a mass-storage device. I
have been trying to do the same thing with a Kodak
DC290. I can use it via serial or usb with gphoto2 but
would prefer to use it as mass-storage as I did in
Win****. I am thinking about trying to edit
unusual_devs.h as you mention. However there is one
major question, where did you get the values from?

From: guido [ date: 2003-01-01 ]
Hello Gary,
you get the numbers from /proc/bus/usb/devices . The third and
fourth are revision ranges (Rev= 0.01 becomes 0x0001).

Note also that this needed because minolta did not follow
the USB standard. The US_FL_START_STOP activates a work around
for that specific bug in their chip.
There are companies who did actually read the usb mass storage
standard and those devices can just be plugged-in and you do
not need any kernel modification at all. I have e.g a pen-drive
from http://www.pendrive.com and it works without any change
and without any driver on any operating system.

From: Peace Monger [ date: 2003-01-12 ]
Fuji Finepix 2650 also connects via USB and is recognized as a SCSI device.

To get to the pictures I did the following:
mkdir /mnt/fuji

and added the following line to /etc/fstab
/dev/sda1 /mnt/fuji vfat noauto,owner,ro,user

Next step:
mount /mnt/fuji

If you receive the message No medium found, make sure that you have the camera powered on. The pictures are in the /mnt/fuji/dcim/100_fuji directory.

From: shakayoda [ date: 2003-01-25 ]
Thx, works great for the Minolta DimageXi. Didn't need to add any lines in unusual_devs.h. I use kernel 2.4.20. I only needed to recompile it for usb-storage and scsi-support.
From: Patrick Hall <pat(at)fieldmethods.net> [ date: 2003-01-31 ]
Hi, I've got a Minolta Dimage F100.

I have successfully copied files off my sister's identical model, using this command:

#mount -t vfat /dev/sda1 /mnt/cam

To my surprise, the command doesn't work with my own camera, which returns "mount:no medium found."

The only difference I can think of between her camera and mine is the fact that hers has a larger flash memory card.

Could this be what's causing the problem?

Regards,
Patrick Hall
From: Gionatan <gionatan20(at)inwind.it> [ date: 2003-02-16 ]
Ho aquistato un afotocamera digitale fujifilm ix-30 ha un mese di vita e non riesco a scattare fotografie, cancellare foto. Qualsiasi operazione faccio si visualizza "Prot" sapete cosa significa?
From: chort [ date: 2003-02-26 ]
Thank you SO MUCH for the assistence here! mount -t vfat -o noauto,ro,owner,user /mnt/fujifilm (<--- my dir) worked splendidly for my Fuji Finepix 2650!!!
From: Nik <don.nico(at)tiscali.it> [ date: 2003-03-16 ]
I got an asus T9400 with mp3 player module that should work via usb. My problem is that i can't get it to work even if, when turned on and docked, the player is displayed (as shown at the end) in the /proc/bus/usb/devices file.
I'm quite a newbie so i'm missing something quite probably. Any help eould be useful, I work with Mandrake 9.0 and i successfully managed to work with my dimage 7i. I paste here also the output of devices file:

T: Bus=02 Lev=01 Prnt=01 Port=01 Cnt=01 Dev#= 5 Spd=12 MxCh= 0
D: Ver= 1.00 Cls=00(>ifc ) Sub=00 Prot=00 MxPS= 8 #Cfgs= 1
P: Vendor=0483 ProdID=163d Rev= 1.00
S: Manufacturer=Asus Technologies
S: Product=Asus MPs Player
S: SerialNumber=2001
C:* #Ifs= 1 Cfg#= 1 Atr=40 MxPwr= 0mA
I: If#= 0 Alt= 0 #EPs= 4 Cls=ff(vend.) Sub=00 Prot=00 Driver=(none)
E: Ad=81(I) Atr=02(Bulk) MxPS= 64 Ivl=0ms
E: Ad=02(O) Atr=02(Bulk) MxPS= 64 Ivl=0ms
E: Ad=83(I) Atr=02(Bulk) MxPS= 64 Ivl=0ms
E: Ad=04(O) Atr=02(Bulk) MxPS= 64 Ivl=0ms

Needless to say... thank to anybody helpful or just suggest...ful

Nik
From: Rob Reid <reid+lf(at)astro.utoronto.ca> [ date: 2003-03-23 ]
Solution for disconnection with "no media found" at fdisk step!

Each new DiMage seems to have its own product id, but the rest of the USB interface is the same. Take the ProdID from `cat /proc/bus/usb/devices` and insert it in a new entry in linux/drivers/usb/storage/unusual_devs.h. Then recompile. For example, my Minolta s414 works with

/* The magic number
vvv */
UNUSUAL_DEV( 0x0686, 0x4014, 0x0001, 0x0001,
"Minolta",
"Dimage s414",
US_SC_SCSI, US_PR_BULK, NULL,
US_FL_START_STOP ),

From: m.izban <mizban(at)web.de> [ date: 2003-04-27 ]
Thanks for this side.

I have nearly the same problems as some others with my 7hi. The camera connects to the pc (suse-linux 8.2) and some seconds later it disconnects. /var/log/messages says:

athlon kernel: hub.c: new USB device 00:07.2-1, assigned address 2
athlon kernel: usb.c: USB device 2 (vend/prod 0x686/0x400f) is not claimed by any active driver.
athlon kernel: Initializing USB Mass Storage driver...
athlon kernel: usb.c: registered new driver usb-storage
athlon kernel: scsi2 : SCSI emulation for USB Mass Storage devices
athlon kernel: Vendor: MINOLTA Model: DIMAGE CAMERA Rev: 1.00
athlon kernel: Type: Direct-Access ANSI SCSI revision: 02
athlon kernel: Attached scsi removable disk sdd at scsi2, channel 0, id 0, lun 0
athlon kernel: SCSI device sdd: 1027089 512-byte hdwr sectors (526 MB)
athlon kernel: sdd: Write Protect is off
athlon kernel: sdd: sdd1
athlon kernel: WARNING: USB Mass Storage data integrity not assured
athlon kernel: USB Mass Storage device found at 2
athlon kernel: USB Mass Storage support registered.
athlon insmod: Using /lib/modules/2.4.20-4GB-athlon/kernel/drivers/usb/storage/usb-storage.o
athlon insmod: Symbol version prefix ''
athlon kernel: sdd : READ CAPACITY failed.
athlon kernel: sdd : status = 1, message = 00, host = 0, driver = 08
athlon kernel: Info fld=0xa00 (nonstd), Current sd00:00: sns = 70 2
athlon kernel: Raw sense data:0x70 0x00 0x02 0x00 0x00 0x0a 0x00 0x00
athlon kernel: sdd : block size assumed to be 512 bytes, disk size 1GB.
athlon kernel: sdd: I/O error: dev 08:30, sector 0
athlon kernel: lost async page write due to I/O error on 08:30
athlon last message repeated 7 times

the card is a 512MB, the same happens with the original 16MB-Card, coming with the camera.

On my son's win98-pc everything runs pretty good. No problems.

Next I will try to compile a new kernel.


From: Dave <dp_AT_NO_SPAM_christopherwhitehead.worcs.sch.uk> [ date: 2003-04-30 ]
This all makes sense so far ... however, I can't find any of the files refered to.
I can get the camera connected - HardDrake detects it and lists it - KDE 3.1 detects the SCSI and USB connection - but, as with everyone else, it falls over when you try to mount it.

I'm running Mandrake 9.1, and the only contents of /usr/src/ is a folder called RPM, with a series of empty sub folders/sub-sub folders.

Also, I haven't been able to track down the file unusual_dev.h at all

I'm rather nervous about trying to recompile the kernel as there is no linux folder in the path specified in the linuxfocus article #255 ... especially as this is the first step given.

I do have file:/lib/modules/2.4.21-0.13mdk/kernel/drivers/usb/storage/usb-storage.0.gz
... but I can't edit it.

if I try and recompile the kernel, would the folder /lib/modules/2.4...etc have the same in as /usr/src/linux ???

Camera- Minolta DiMAGE S414
OS - Mandrake 9.1
Kernel - 2.4.21-0.13mdk

Help - please!

Thanks for any help


From: guido [ date: 2003-04-30 ]
Hello everybody!!!
The point of this article is that YOU MUST RECOMPILE YOUR KERNEL
You can also take a recent binary kernel for your distribution (2.4.20 and up) which has
by default the needed parameters for Dimage 7 and 7i (unfortunately not
dimage 5).
So there is no point saying "i have the same problem as everybody". The
truth is that you have the same problem as all those who did not read the
article. The article says: Edit unusual_devs.h and re-compile the kernel!!!

How to compile a kernel is described in at least 2 other LF aritcles.

If you read the comments of those who have it working you will see that
they did actually re-compile the kernel (or just the usb-storage module).
From: Bryan Simmons <bsimmo1(at)umbc.edu> [ date: 2003-05-17 ]
Actually, I am running Mandrake 9.1 and using the Fuji FinePix 2650. I DID NOT have to recompile ANYTHING, nor did I have to edit any files other than one line in /etc/fstab (as talked about in the article).

Simply do: modprobe usb_storage (after usb-uhci module is loaded; mine is at boot)
run lsusb (comes with usb-tools rpm) to make sure the usb_storage module found the cam.
Create a mount folder for the cam (/mnt/fuji for me)
Then edit /etc/fstab as shown in the article.
Then mount the folder created for the device (/mnt/fuji) AS THE USER ACCOUNT WHO WILL USE THE CAMERA.
VIOLLA!!
Werks GREAT!!!

Hats off to Mandrake (in this case).
From: Allard <raves036(at)zonnet.nl> [ date: 2003-05-23 ]
I got my Minolta dimage 7HI to work under linux, kernel 2.4.17 (other kernels will probably work too)

lines for unusual_devs.h :

UNUSUAL_DEV( 0x0686, 0x400f, 0x001, 0x0001,
"Minolta",
"Dimage 7hi",
US_SC_SCSI, US_PR_BULK, NULL,
US_FL_START_STOP ),

Good luck !!
From: Girard <girard(at)iml.univ-mrs.fr> [ date: 2003-06-29 ]
I have not yet made my mind as to which
camera I should buy. I have not understood whether
or not the non-reflex cameras, eg DIMAGE F300
are compatible with, say, Mandrake 8.0
Thanks for any help (and the nice page anyway).
J-Y Girard
From: Matt <mystic_i(at)hotmail.com> [ date: 2003-09-14 ]
Talking about USB Mass Storage Devices, Most of the USB drives out there are too large and bulky to have sticking out of your Camera. I have found very small and slimline USB Drives that fit in nicely in my Camera. These can be found in http://www.usbflash.com and in particular their Ultraslim product http://www.usbflash.com/products/ultraslim.php

From: meg <mystic_i(at)hotmail.com> [ date: 2003-09-19 ]
I reccommend anyone USB Flash www.usbflash.com and their Cuteflash product

http://www.usbflash.com/products/cuteflash.php
From: C Klocker <nesslegg( at ) hotmail com> [ date: 2003-10-19 ]
Does anyone get the dimage 7i working with kernel 2.4.22??.
I always get compiling failures with the inserted code.

Chri

From: C Klocker [ date: 2003-10-19 ]
Fixed it, it works without the additional lines

chri
From: F. Zick <f-zick(at)gmx.de> [ date: 2003-11-16 ]
Although I followed your article (how to install and compile my system) to get pictures from my camera Minolta Dimage S414. I have the problem, that in the program "Digikam" my camera is shortly recognized, but closes next moment the USB-connection.
Could you please help me ?
Sincerely
F. Zick
From: Guido Socher [ date: 2004-03-15 ]
This article was written for 2.4.17. If you have a 2.4.22 or more
recent then be aware that usb-storage has changed a lot. The syntax is
now something like:
UNUSUAL_DEV( 0x0686, 0x4008, 0x0001, 0x0001,
"Minolta",
"DiMAGE 5",
US_SC_SCSI, US_PR_DEVICE, NULL,
0 ),

Note also that it is now very important to not probe for multiple lun
in the scsi setup:
# CONFIG_SCSI_MULTI_LUN is not set
From: iain [ date: 2004-05-04 ]
I have SuSE 9.0 and i have installed the kernal source and header files... however i can not find the unusual_dev header... and i appear to have slightly differant problem...
when i try to activate the transfer on my dimage 7hi my puter freezes up. since this isnt useful, i have tried using a Jenoptik compact flash USB Jenreader... and when that is plugged in, my puter freezes!

i am a newbie and dont really have much of a clue what im doing so please be gentle with me,
thanks for any help
From: iain [ date: 2004-05-04 ]
ok scrap that... i found it...

but the kernel compile doesnt work... i follow the instructions in the article and on the linked compile instruction page and i have 2 problems...
i dont know how to "ls al" so i tried just typing that... and it didnt do anything... something about no path or something...

so i skipped it, and i get an error making bzImage module... i get
"In file included from usb.c:190:
unusual_devs.h:408: error: `US_FL_START_STOP' undeclared here (not in a function)
unusual_devs.h:408: error: initializer element is not constant
unusual_devs.h:408: error: (near initialization for `us_unusual_dev_list[52].flags')"

followed by a load of fails along the lines of
"unusual_devs.h:617: error: initializer element is not constant
unusual_devs.h:617: error: (near initialization for `us_unusual_dev_list[80]')"
then
"usb.c:198: error: initializer element is not constant
usb.c:198: error: (near initialization for `us_unusual_dev_list[91]')"
finnished by "make[3]: *** [usb.o] Error 1
make[3]: Leaving directory `/usr/src/linux-2.4.21-215/drivers/usb/storage'
make[2]: *** [_modsubdir_storage] Error 2
make[2]: Leaving directory `/usr/src/linux-2.4.21-215/drivers/usb'
make[1]: *** [_modsubdir_usb] Error 2
make[1]: Leaving directory `/usr/src/linux-2.4.21-215/drivers'
make: *** [_mod_drivers] Error 2"

what in Tux name am i doing wrong?


From: Anonymous User [ date: 2004-05-09 ]
Hello Ian,
check if the 2.4.21 kernel which you have does already define
US_PR_DEVICE (see talkback from the 2004-03-15). If yes use that.
Make also sure that scsi configuration does not probe for multiple LUNs.

From: Russell Davie <russell(dot)davie(at)gmail(dot)com> [ date: 2005-05-08 ]
Hi Guido
I have bought a 2nd hand Dimage S404 and found Michael Schroeder's modifications for S404 didn't suit kernel 2.6.6 ie wouldn't compile.

this does and works!

UNUSUAL_DEV( 0x0686, 0x400a, 0x0001, 0x0001,
"Minolta",
"Dimage S404",
US_SC_SCSI, US_PR_BULK, NULL, 0 ),

best wishes!
Russell

56 talkbacks in English
Other talkbacks:   Italiano Francais




Due to the increased amount of web spam we have deciced to removed the talkback posting possibility. You can read old talkbacks but you can no longer post new ones.

Back to http://cgi.linuxfocus.org/English/May2002/article240.shtml

Please contact webmaster(at)linuxfocus.org if you have any questions with regards to this talkback

lftalkback version 3.10