Re: USB camera mount
On Sat, Apr 05, 2003 at 10:10:19AM +0100, Tim wrote: Tim wrote: Olivier wrote: scsi1 means it's /dev/sdb1 ? mount: /dev/sdb1 is not a valid block device I have a Sony with a memory stick which stores the images in jpeg format. I had no trouble in configuring a 2.4.18 kernel to support usb mass storage and adding /dev/sdb1 /sony vfat ro,users,noauto 0 0 to my fstab. I already had append=hdd=ide-scsi in lilo.conf under image=/boot/bzImage. cdrecord --scanbus reported the camera was present so after mkdir /sony I mounted /sony and downloaded all the .jpg files to a hard drive with no difficulty. Perhaps this this helps? Tom George Is it the case that unless there is individual support for a model built into the kernel, it won't be recognised? From this do I deduce that I will be unable to mount my Nikon Coolpix E4300? And thus will need to buy a CF card reader? TIA, Tim -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED] -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: USB camera mount
Craig Dickson wrote: Tim wrote: Is it the case that unless there is individual support for a model built into the kernel, it won't be recognised? From this do I deduce that I will be unable to mount my Nikon Coolpix E4300? And thus will need to buy a CF card reader? Well, a quick web search turns up the claim that your camera is a USB mass storage device, so at most, the kernel might need a simple device descriptor added to it. This is a source code change, so you'd have to rebuild your kernel Personally, I _prefer_ having a separate CF card reader. The USB ports on digital Cameras are often non-standard (so you have to use their custom cable, which can be a pain to replace if you lose or damage it) and look rather fragile (so I wouldn't want to be constantly plugging and unplugging it). Also, with a CF reader, you don't need to turn the camera on to pull pictures out of it SanDisk makes a nice CF/SM combo reader that works nicely with Linux (model SDDR-75) Craig I've not altered source code before-could you tell me if the file I need to alter is /kernel-source/drivers/usb/storage/unusual_devs.h If so, what protocols should I use? Is this where it gets sticky and complex? Thanks, Tim -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: USB camera mount
Thomas H. George wrote: I have a Sony with a memory stick which stores the images in jpeg format. I had no trouble in configuring a 2.4.18 kernel to support usb mass storage and adding /dev/sdb1 /sony vfat ro,users,noauto 0 0 to my fstab. I already had append=hdd=ide-scsi in lilo.conf under image=/boot/bzImage. cdrecord --scanbus reported the camera was present so after mkdir /sony I mounted /sony and downloaded all the .jpg files to a hard drive with no difficulty. Perhaps this this helps? Tom George I added hdd=ide-scsi to the boot parameters, but unfortunately I can't mount the device yet. This camera is also saving as jpeg. mount /dev/sdb1 /mnt/camera mount: /dev/sdb1 is not a valid block device Thanks, Tim Cdrecord 1.10 (i686-pc-linux-gnu) Copyright (C) 1995-2001 Jörg Schilling Using libscg version 'schily-0.5' scsibus0: 0,0,0 0) 'MSI ' 'CD-RW MS-8348 ' '110D' Removable CD-ROM 0,1,0 1) * 0,2,0 2) * 0,3,0 3) * 0,4,0 4) * 0,5,0 5) * 0,6,0 6) * 0,7,0 7) * scsibus1: 1,0,0 100) 'NIKON ' 'NIKON DSC E4300 ' '1.00' Removable Disk 1,1,0 101) * 1,2,0 102) * 1,3,0 103) * 1,4,0 104) * 1,5,0 105) * 1,6,0 106) * 1,7,0 107) *
Re: USB camera mount
Tim wrote: Olivier wrote: scsi1 means it's /dev/sdb1 ? mount: /dev/sdb1 is not a valid block device Is it the case that unless there is individual support for a model built into the kernel, it won't be recognised? From this do I deduce that I will be unable to mount my Nikon Coolpix E4300? And thus will need to buy a CF card reader? TIA, Tim -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: USB camera mount
Tim wrote: Is it the case that unless there is individual support for a model built into the kernel, it won't be recognised? From this do I deduce that I will be unable to mount my Nikon Coolpix E4300? And thus will need to buy a CF card reader? Well, a quick web search turns up the claim that your camera is a USB mass storage device, so at most, the kernel might need a simple device descriptor added to it. This is a source code change, so you'd have to rebuild your kernel. Personally, I _prefer_ having a separate CF card reader. The USB ports on digital Cameras are often non-standard (so you have to use their custom cable, which can be a pain to replace if you lose or damage it) and look rather fragile (so I wouldn't want to be constantly plugging and unplugging it). Also, with a CF reader, you don't need to turn the camera on to pull pictures out of it. SanDisk makes a nice CF/SM combo reader that works nicely with Linux (model SDDR-75). Craig pgp0.pgp Description: PGP signature
Re: USB camera mount
I have a cam too and when I want to connect it to the computer, I use the /dev/sda1 device (scsi) like a vfat file system. I think you should have scsi support on kernel. Regards. El jue, 03 de 04 de 2003 a las 09:13, Tim escribió: Hi, I've compiled my kernel, mass storage as a module, and all compact flash media options enabled. Yet I cannot determine what device this camera is set to, from which I can mount it. Does anyone have any clues? I've attached 'tail /var/log/messages'. TIA, Tim __ Apr 3 08:03:21 debian xfs: ignoring font path element /usr/lib/X11/fonts/cyrillic/ (unreadable) Apr 3 08:03:21 debian xfs: ignoring font path element /usr/lib/X11/fonts/CID (unreadable) Apr 3 08:03:21 debian kernel: hamcore module init Apr 3 08:03:21 debian kernel: ham: loading 536EP Release 4.51 INT (kern:2.4.18) - Feb 6 2003 Apr 3 08:03:21 debian kernel: ham: IRQ: 5, DSP-Base: 0xeb80 (phys) 0xdeb32000 (virt) (range: 4096k), DSP-Port: 0x0 (range: 0b) Apr 3 08:03:28 debian kernel: 0: NVRM: AGPGART: unable to retrieve symbol table Apr 3 08:04:26 debian kernel: hub.c: USB new device connect on bus1/3, assigned device number 2 Apr 3 08:04:26 debian kernel: scsi1 : SCSI emulation for USB Mass Storage devices Apr 3 08:04:27 debian kernel: Vendor: NIKON Model: NIKON DSC E4300 Rev: 1.00 Apr 3 08:04:27 debian kernel: Type: Direct-Access ANSI SCSI revision: 02 -- * You're currently going through a difficult transition period called Life. * .''`. : :' : `. `'Proudly running Debian GNU/Linux Sid (Kernel 2.4.18) on Ext3 `- http://acm.escet.urjc.es/~agutierr [EMAIL PROTECTED] // [EMAIL PROTECTED] signature.asc Description: PGP signature
Re: USB camera mount
Olivier wrote: scsi1 means it's /dev/sdb1 ? mount: /dev/sdb1 is not a valid block device -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: USB camera mount
Antonio Gutiérrez Mayoral wrote: I have a cam too and when I want to connect it to the computer, I use the /dev/sda1 device (scsi) like a vfat file system I think you should have scsi support on kernel I do believe that is set in my kernel config. mount: /dev/sda1 is not a valid block device # # Automatically generated make config: don't edit # CONFIG_X86=y CONFIG_ISA=y # CONFIG_SBUS is not set CONFIG_UID16=y # # Code maturity level options # CONFIG_EXPERIMENTAL=y # # Loadable module support # CONFIG_MODULES=y CONFIG_MODVERSIONS=y CONFIG_KMOD=y # # Processor type and features # # CONFIG_M386 is not set # CONFIG_M486 is not set # CONFIG_M586 is not set # CONFIG_M586TSC is not set # CONFIG_M586MMX is not set # CONFIG_M686 is not set # CONFIG_MPENTIUMIII is not set # CONFIG_MPENTIUM4 is not set # CONFIG_MK6 is not set CONFIG_MK7=y # CONFIG_MELAN is not set # CONFIG_MCRUSOE is not set # CONFIG_MWINCHIPC6 is not set # CONFIG_MWINCHIP2 is not set # CONFIG_MWINCHIP3D is not set # CONFIG_MCYRIXIII is not set CONFIG_X86_WP_WORKS_OK=y CONFIG_X86_INVLPG=y CONFIG_X86_CMPXCHG=y CONFIG_X86_XADD=y CONFIG_X86_BSWAP=y CONFIG_X86_POPAD_OK=y # CONFIG_RWSEM_GENERIC_SPINLOCK is not set CONFIG_RWSEM_XCHGADD_ALGORITHM=y CONFIG_X86_L1_CACHE_SHIFT=6 CONFIG_X86_TSC=y CONFIG_X86_GOOD_APIC=y CONFIG_X86_USE_3DNOW=y CONFIG_X86_PGE=y CONFIG_X86_USE_PPRO_CHECKSUM=y # CONFIG_TOSHIBA is not set # CONFIG_I8K is not set # CONFIG_MICROCODE is not set # CONFIG_X86_MSR is not set # CONFIG_X86_CPUID is not set CONFIG_NOHIGHMEM=y # CONFIG_HIGHMEM4G is not set # CONFIG_HIGHMEM64G is not set # CONFIG_MATH_EMULATION is not set CONFIG_MTRR=y # CONFIG_SMP is not set CONFIG_X86_UP_APIC=y # CONFIG_X86_UP_IOAPIC is not set CONFIG_X86_LOCAL_APIC=y # # General setup # CONFIG_NET=y CONFIG_PCI=y # CONFIG_PCI_GOBIOS is not set # CONFIG_PCI_GODIRECT is not set CONFIG_PCI_GOANY=y CONFIG_PCI_BIOS=y CONFIG_PCI_DIRECT=y CONFIG_PCI_NAMES=y # CONFIG_EISA is not set # CONFIG_MCA is not set CONFIG_HOTPLUG=y # # PCMCIA/CardBus support # # CONFIG_PCMCIA is not set # # PCI Hotplug Support # # CONFIG_HOTPLUG_PCI is not set # CONFIG_HOTPLUG_PCI_COMPAQ is not set # CONFIG_HOTPLUG_PCI_COMPAQ_NVRAM is not set CONFIG_SYSVIPC=y CONFIG_BSD_PROCESS_ACCT=y CONFIG_SYSCTL=y CONFIG_KCORE_ELF=y # CONFIG_KCORE_AOUT is not set CONFIG_BINFMT_AOUT=y CONFIG_BINFMT_ELF=y CONFIG_BINFMT_MISC=y CONFIG_PM=y # CONFIG_ACPI is not set CONFIG_APM=m # CONFIG_APM_IGNORE_USER_SUSPEND is not set # CONFIG_APM_DO_ENABLE is not set # CONFIG_APM_CPU_IDLE is not set # CONFIG_APM_DISPLAY_BLANK is not set # CONFIG_APM_RTC_IS_GMT is not set # CONFIG_APM_ALLOW_INTS is not set # CONFIG_APM_REAL_MODE_POWER_OFF is not set # # Memory Technology Devices (MTD) # # CONFIG_MTD is not set # # Parallel port support # CONFIG_PARPORT=m CONFIG_PARPORT_PC=m CONFIG_PARPORT_PC_CML1=m CONFIG_PARPORT_SERIAL=m # CONFIG_PARPORT_PC_FIFO is not set # CONFIG_PARPORT_PC_SUPERIO is not set # CONFIG_PARPORT_AMIGA is not set # CONFIG_PARPORT_MFC3 is not set # CONFIG_PARPORT_ATARI is not set # CONFIG_PARPORT_GSC is not set # CONFIG_PARPORT_SUNBPP is not set # CONFIG_PARPORT_OTHER is not set # CONFIG_PARPORT_1284 is not set # # Plug and Play configuration # CONFIG_PNP=y # CONFIG_ISAPNP is not set # # Block devices # CONFIG_BLK_DEV_FD=y # CONFIG_BLK_DEV_XD is not set # CONFIG_PARIDE is not set # CONFIG_BLK_CPQ_DA is not set # CONFIG_BLK_CPQ_CISS_DA is not set # CONFIG_BLK_DEV_DAC960 is not set CONFIG_BLK_DEV_LOOP=y # CONFIG_BLK_DEV_NBD is not set # CONFIG_BLK_DEV_RAM is not set # CONFIG_BLK_DEV_INITRD is not set # # Multi-device support (RAID and LVM) # # CONFIG_MD is not set # CONFIG_BLK_DEV_MD is not set # CONFIG_MD_LINEAR is not set # CONFIG_MD_RAID0 is not set # CONFIG_MD_RAID1 is not set # CONFIG_MD_RAID5 is not set # CONFIG_MD_MULTIPATH is not set # CONFIG_BLK_DEV_LVM is not set # # Networking options # CONFIG_PACKET=y # CONFIG_PACKET_MMAP is not set CONFIG_NETLINK_DEV=y CONFIG_NETFILTER=y # CONFIG_NETFILTER_DEBUG is not set # CONFIG_FILTER is not set CONFIG_UNIX=y CONFIG_INET=y # CONFIG_IP_MULTICAST is not set # CONFIG_IP_ADVANCED_ROUTER is not set # CONFIG_IP_PNP is not set # CONFIG_NET_IPIP is not set # CONFIG_NET_IPGRE is not set # CONFIG_ARPD is not set # CONFIG_INET_ECN is not set # CONFIG_SYN_COOKIES is not set # # IP: Netfilter Configuration # CONFIG_IP_NF_CONNTRACK=m CONFIG_IP_NF_FTP=m CONFIG_IP_NF_IRC=m CONFIG_IP_NF_QUEUE=m CONFIG_IP_NF_IPTABLES=m CONFIG_IP_NF_MATCH_LIMIT=m CONFIG_IP_NF_MATCH_MAC=m CONFIG_IP_NF_MATCH_MARK=m CONFIG_IP_NF_MATCH_MULTIPORT=m CONFIG_IP_NF_MATCH_TOS=m CONFIG_IP_NF_MATCH_AH_ESP=m CONFIG_IP_NF_MATCH_LENGTH=m CONFIG_IP_NF_MATCH_TTL=m CONFIG_IP_NF_MATCH_TCPMSS=m CONFIG_IP_NF_MATCH_STATE=m CONFIG_IP_NF_MATCH_UNCLEAN=m CONFIG_IP_NF_MATCH_OWNER=m CONFIG_IP_NF_FILTER=m CONFIG_IP_NF_TARGET_REJECT=m CONFIG_IP_NF_TARGET_MIRROR=m CONFIG_IP_NF_NAT=m CONFIG_IP_NF_NAT_NEEDED=y CONFIG_IP_NF_TARGET_MASQUERADE=m CONFIG_IP_NF_TARGET_REDIRECT=m CONFIG_IP_NF_NAT_SNMP_BASIC=m CONFIG_IP_NF_NAT_IRC=m
USB camera mount
Hi, I've compiled my kernel, mass storage as a module, and all compact flash media options enabled. Yet I cannot determine what device this camera is set to, from which I can mount it. Does anyone have any clues? I've attached 'tail /var/log/messages'. TIA, Tim Apr 3 08:03:21 debian xfs: ignoring font path element /usr/lib/X11/fonts/cyrillic/ (unreadable) Apr 3 08:03:21 debian xfs: ignoring font path element /usr/lib/X11/fonts/CID (unreadable) Apr 3 08:03:21 debian kernel: hamcore module init Apr 3 08:03:21 debian kernel: ham: loading 536EP Release 4.51 INT (kern:2.4.18) - Feb 6 2003 Apr 3 08:03:21 debian kernel: ham: IRQ: 5, DSP-Base: 0xeb80 (phys) 0xdeb32000 (virt) (range: 4096k), DSP-Port: 0x0 (range: 0b) Apr 3 08:03:28 debian kernel: 0: NVRM: AGPGART: unable to retrieve symbol table Apr 3 08:04:26 debian kernel: hub.c: USB new device connect on bus1/3, assigned device number 2 Apr 3 08:04:26 debian kernel: scsi1 : SCSI emulation for USB Mass Storage devices Apr 3 08:04:27 debian kernel: Vendor: NIKON Model: NIKON DSC E4300 Rev: 1.00 Apr 3 08:04:27 debian kernel: Type: Direct-Access ANSI SCSI revision: 02
