Jump to content

USB Digital Camera - how to access in MDK 9.1


chris:b
 Share

Recommended Posts

Ok, that would have been tooooo easy.

I'm on my NT machine at work so I can't really do much definitively by way of comparision.

 

I think your problem might be in automagically creating the new device.

 

You should check you have

/sbin/hotplug

 

Then you should have a file in

/proc/system/kernel/hotplug

 

Also , just checking but what kernel are you using....

You should have a /etc/hotplug directory

 

(This is a desperate measure... It might mess something else up.... but.

The modules.conf and modukes.usbmap are created by depmod. You can recreate them with a depmod -a but please read the man first)

 

Also: Check you have your usbutils intalled, if not you can urpmi them.

 

Hope this helps, I can be more specific sat at a linux box :-)

Link to comment
Share on other sites

  • Replies 42
  • Created
  • Last Reply

Top Posters In This Topic

Hello Paris,

 

1. /sbin/hotplug is already there

2. /etc/hotplug is already there (many files as usb.agent, usb.rc, usb.usermap and so on, and 3 subdir, one is .../usb with the files usb-storage and usbcam

3. kernel: 2.4.21-0.13mdk

4. modules.conf:

 

probeall scsi_hostadapter usb-storage ide-scsi

alias eth0 8139too

alias sound-slot-0 snd-cmipci

probeall usb-interface usb-uhci

alias ieee1394-controller ohci1394

above snd-cmipci snd-pcm-oss

 

5. usbutils - was installed

________________

I have to run now - doing some payed work :wink:

 

Thinking about some more options:

- bios settings?

- trying to boot with a knoppix cd and the camera plugged in

- I had no usb devices when I installed mandrake

- I only got scsi emu with the cdrw drive, no other scsi things

- ...

Link to comment
Share on other sites

I had no usb devices when I installed mandrake

 

Anna, Ive been trying to steer clear of that one, obviously its fixable somehow but it might just be quicker to .... (whisper reinstall)

 

I have to admit, Ive done it before ... :oops: specifically for this kinda thing.... If your going to doit anyway though you might try the depmod -a first :wink:

Link to comment
Share on other sites

Anna, Ive been trying to steer clear of that one, obviously its fixable somehow but it might just be quicker to .... (whisper  reinstall)  

 

LOL Stephen. I am almost sure it will work - whether reinstall or fix or waiting til MDK 9.2 release in september. I don't feel comfortable (as a newbie) with kernel upgrade and things like that at the moment, and reinstall? Geez, my system now is so stable and beautiful and all. The only thing is that my partner at home is grinning evil that the camera works fine with the win98 box and my winxp, and its a bit like a competition, you know, because I want to make sure that our next pc (replace of the win98) will be a linux only box.

 

Thanks for your kind assistance. I am learning a lot. When I am at home this evening I'll care about the 'depmod -a'

Link to comment
Share on other sites

anna: when your partner at home starts sounding off about how things work in 98/XP, tell him that's because M$ bribes hardware companies to only make drivers for their O/S ;-) and that most drivers for Linux are written by the people, for the people. No hardware company support in many cases. Atleast, that's what I tell people, makes them stop and think....

Link to comment
Share on other sites

Shot in the dark, ....

it's not supermount, it's not usb or kernel problems...

 

All you may need to do is do a

 

mknod [significant node and other data that I don't know]

 

to create the right device, and you will be able to read the cam contents.

Since the usb-storage gets loaded, and your usb device gets detected, all you need is to have the device as a file (meaning: in the filetree, as a device in /dev, probably as /dev/sda ..), and mknod is the command to fix/create that.

 

I had to do that the other day to create the /dev/lirc/0 device, all modules were loaded, all config files in place, but I just didn't have the device...

 

I did a google:

http://groups.google.com/groups?hl=en&lr=&...%3DN%26tab%3Dwg

1/ Branchez le stick USB...!

2/ Vérifiez qu'il est reconnu: >

    # ls    /proc/scsi/usb-storage-0  (s'il y en a qu'un alors c'est le /0)

    # cat /proc/scsi/usb-storage-0/0

    ...on obtient un résultat du genre:

        Host scsi0: usb-storage

          Vendor:

          Product: PenDrive

        Serial Number: 072A1C110032

        Protocol: Transparent SCSI

        Transport: Bulk

        GUID: 0d7d01000000072a1c110032

        Attached: Yes

3/ Vérifier si les devices scsi (/dev/sda,sda1...) existent!

    sinon en créer avec la commande "mknod" (en root):

    # mkmod /dev/sda b 8 0

    # mknod /dev/sda1 b 8 1 ...

4/ Créez un rep. de mountage par ex: #mkdir /mnt/usb

5/ Monter le,  par ex. pour recuperer des fichiers Dos

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

 

or:

http://groups.google.com/groups?hl=en&lr=&...%3DN%26tab%3Dwg

 

If you're not using devfs, you create device nodes (special files that

refer to hardware devices) with the "mknod" command or the /dev/MAKEDEV

script.  If /dev/MAKEDEV is present, you can create a device by doing:

MAKEDEV /dev/sda /dev/sda1

If not, use mknod like so:

mknod /dev/sda 8 0 b

for I in 1 2 3 4 5 6 7 8 9; do

  mknod /dev/sda$I 8 $I b

  done

 

So I guess your mknod command should be:

mknod /dev/sda 8 0 b

....then followed by the french stuff on mounting...

 

[edit]

Maybe/possibly you have to do both mknod commands as shown in the french message, I see the same thing here (meaning: doing both mknod commands, creating /dev/sda and /dev/sda1 .....) :

http://groups.google.com/groups?hl=en&lr=&...%3DN%26tab%3Dwg

Link to comment
Share on other sites

Shot in the dark, ....

it's not supermount, it's not usb or kernel problems...

All you may need to do is do a 

mknod [significant node and other data that I don't know]

......

 

Thanks artee, tried it. it had to be

mknod /dev/sda1 b 8 1

(not 1 8 B) -

But no luck. Could create them, but trying the mount command, I got (translation...):

 

/dev/sda1 (or sda) is not a valid block device

 

(camera was plugged, all modules loades, usb-mass storage running ...)

 

I guess though the camera gets 'detected' it's somehow not possible to initialize the mass storage - due to some non-standard strings or whatever.

 

I know that very well - my own mass storage, an embedded one, my brain, is often not initialized too

:evil:

Link to comment
Share on other sites

Just saw on MandrakeClub:

 

Someone with the same camera brand, model, just bought, is having similiar problems. It's in the section 'printing, scanning, photo', his name is Lex van Buijtenen (Netherlands). I can't post there, being not a member ... :twisted:

 

Maybe anyone with a membership can grab him and bring him here?

Link to comment
Share on other sites

Anna, try doing both mknod commands:

 

mkmod /dev/sda b 8 0

mknod /dev/sda1 b 8 1 ...

then if necessary:

mkdir /mnt/usb

and mount with:

mount -t vfat /dev/sda1 /mnt/usb

 

I've seen most references making both the 8 0 and 8 1 node, so it seems to be necessary for it to work. Worth a try IMO.

Link to comment
Share on other sites

Hi, I completely missed out on trying mknod ...

 

It seems a missing link ... Is this generic for creating devices, i.e. say a device file for a modem or is it usb only??

 

I'm wondering if this is the bit that doesn't happen autonmagically if you don't have the device at install time??

Link to comment
Share on other sites

ok, I just tried it once again, (hotplugging), now here all

lines from /var/log/messages:

 

Jul  4 10:14:15 localhost kernel: hub.c: new USB device 00:1f.4-1, assigned address 2

Jul  4 10:14:15 localhost kernel: usb.c: USB device 2 (vend/prod 0xd96/0x2105) is not claimed by any active driver.

Jul  4 10:14:18 localhost /etc/hotplug/usb.agent: Setup usb-storage for USB product d96/2105/1

Jul  4 10:14:18 localhost kernel: Initializing USB Mass Storage driver...

Jul  4 10:14:18 localhost kernel: usb.c: registered new driver usb-storage

Jul  4 10:14:18 localhost kernel: usb-uhci.c: interrupt, status 2, frame# 1425

Jul  4 10:14:18 localhost kernel: scsi1 : SCSI emulation for USB Mass Storage devices

Jul  4 10:14:46 localhost kernel: usb.c: USB disconnect on device 00:1f.4-1 address 2

Jul  4 10:14:47 localhost kernel: hub.c: new USB device 00:1f.4-1, assigned address 3

Jul  4 10:14:51 localhost kernel: usb-uhci.c: interrupt, status 3, frame# 1736

Jul  4 10:14:51 localhost kernel: scsi: device set offline - not ready or command retry failed after bus reset: host 1 channel 0 id 0 lun 0

Jul  4 10:14:51 localhost kernel: USB Mass Storage support registered.

Jul  4 10:14:51 localhost kernel: scsi2 : SCSI emulation for USB Mass Storage devices

Jul  4 10:14:51 localhost /etc/hotplug/usb.agent: Module setup usb-storage for USB product d96/2105/1

Jul  4 10:14:51 localhost /etc/hotplug/usb/usb-storage: Load scsimon

Jul  4 10:14:51 localhost /etc/hotplug/usb/usb-storage: loading ... scsimon

Jul  4 10:14:51 localhost kernel: resize_dma_pool: unknown device type -1

Jul  4 10:14:51 localhost /etc/hotplug/scsi.agent: sr_mod allready loaded

Jul  4 10:14:51 localhost /etc/hotplug/scsi.agent: Unknown type: -

 

What am I missing - a module - a 'driver' ??

Link to comment
Share on other sites

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.

Guest
Reply to this topic...

×   Pasted as rich text.   Paste as plain text instead

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.

Loading...
 Share


×
×
  • Create New...