LinuxQuestions.org
Visit Jeremy's Blog.
Go Back   LinuxQuestions.org > Forums > Linux Forums > Linux - Distributions > Slackware
User Name
Password
Slackware This Forum is for the discussion of Slackware Linux.

Notices

Reply
 
Search this Thread
Old 03-24-2009, 08:41 AM   #1
pierpatbsz
LQ Newbie
 
Registered: Mar 2009
Location: Trieste - Italy
Distribution: slackware
Posts: 8

Rep: Reputation: 0
Cannot mount hitachi fotocamera as usb mass-storage in slackware 12.2


i'm upgrading my system from slackware 11.0 (kernel 2.6.20.4) to slackware 12.2 (kernel 2.6.27.7)

the new kernel is compiled starting from the same .config of the old.

All work fine, except for my HITACHI HDC-763E digital camera (Vivitar, Inc) that i cannot mount or partition.

In slack 11.0 I mounted it like a usb mass-storage device; and now I can't. I try to compile the old kernel in slack 12.2 and it still doesn't work.

So, I suppose I forget some packeges of slackware. Other usb mass-storage disk work fine. I don't think it's a kernel problem.



This is my logs:

# uname -a
Linux bsz 2.6.27.7 #3 SMP Sat Mar 21 15:00:52 CET 2009 i686 Intel(R) Core(TM)2 CPU 6400 @ 2.13GHz GenuineIntel GNU/Linux

#dmesg
scsi4 : SCSI emulation for USB Mass Storage devices
usb-storage: device found at 2
usb-storage: waiting for device to settle before scanning
scsi 4:0:0:0: Direct-Access HITACHI HDC-763E 1.10 PQ: 0 ANSI: 0 CCS
sd 4:0:0:0: [sdc] 4095630 512-byte hardware sectors (2097 MB)
sd 4:0:0:0: [sdc] Write Protect is off
sd 4:0:0:0: [sdc] Mode Sense: 00 06 00 00
sd 4:0:0:0: [sdc] Assuming drive cache: write through
sd 4:0:0:0: [sdc] 4095630 512-byte hardware sectors (2097 MB)
sd 4:0:0:0: [sdc] Write Protect is off
sd 4:0:0:0: [sdc] Mode Sense: 00 06 00 00
sd 4:0:0:0: [sdc] Assuming drive cache: write through
sdc: sdc1
sd 4:0:0:0: [sdc] Attached SCSI removable disk
sd 4:0:0:0: Attached scsi generic sg2 type 0
usb-storage: device scan complete
sd 4:0:0:0: [sdc] Result: hostbyte=0x00 driverbyte=0x08
sd 4:0:0:0: [sdc] Sense Key : 0x3 [current]
sd 4:0:0:0: [sdc] ASC=0x11 ASCQ=0x0
end_request: I/O error, dev sdc, sector 4095488
Buffer I/O error on device sdc, logical block 2047744
Buffer I/O error on device sdc, logical block 2047745
Buffer I/O error on device sdc, logical block 2047746
Buffer I/O error on device sdc, logical block 2047747

#cat syslog
Mar 24 10:19:28 bsz kernel: end_request: I/O error, dev sdd, sector 135
Mar 24 10:19:28 bsz kernel: end_request: I/O error, dev sdd, sector 135
Mar 24 10:19:28 bsz kernel: end_request: I/O error, dev sdd, sector 0
Mar 24 10:19:31 bsz last message repeated 5 times

# lsusb
Bus 006 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 007 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 005 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 004 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 003 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 002 Device 003: ID 0784:1692 Vivitar, Inc.
Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 001 Device 004: ID 0718:0188 Imation Corp.
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub

# cat /proc/partitions
major minor #blocks name

3 0 80043264 hda
3 1 730926 hda1
3 2 506047 hda2
3 3 2963992 hda3
3 4 1 hda4
3 5 265041 hda5
3 6 2104483 hda6
3 7 73465213 hda7
8 0 244198584 sda
8 1 8193118 sda1
8 2 236002882 sda2
8 16 244198584 sdb
8 17 995998 sdb1
8 18 489982 sdb2
8 19 4996215 sdb3
8 20 1 sdb4
8 21 4008186 sdb5
8 22 233705556 sdb6
8 32 4029440 sdc
8 33 4029424 sdc1
8 48 2047815 sdd
8 49 1931196 sdd1

# cat /proc/devices
Character devices:
1 mem
2 pty
3 ttyp
4 /dev/vc/0
4 tty
4 ttyS
5 /dev/tty
5 /dev/console
5 /dev/ptmx
6 lp
7 vcs
10 misc
13 input
14 sound
21 sg
116 alsa
128 ptm
136 pts
162 raw
171 ieee1394
180 usb
189 usb_device
202 cpu/msr
203 cpu/cpuid
226 drm
254 usb_endpoint

Block devices:
1 ramdisk
3 ide0
7 loop
8 sd
11 sr
22 ide1
33 ide2
34 ide3
65 sd
66 sd
67 sd
68 sd
69 sd
70 sd
71 sd
128 sd
129 sd
130 sd
131 sd
132 sd
133 sd
134 sd
135 sd
 
Old 03-24-2009, 09:10 AM   #2
hitest
Senior Member
 
Registered: Mar 2004
Location: Prince Rupert, B.C., Canada
Distribution: Slackware, OpenBSD
Posts: 4,169

Rep: Reputation: 534Reputation: 534Reputation: 534Reputation: 534Reputation: 534Reputation: 534
Maybe take a look at /etc/group to ensure that your user has permission to mount the device. just a thought.
 
Old 03-24-2009, 09:29 AM   #3
Didier Spaier
Senior Member
 
Registered: Nov 2008
Location: Paris, France
Distribution: Slackware{,64}-{14.1,current} on a Lenovo Thinkpad T61 6457-4XG
Posts: 4,234

Rep: Reputation: 1040Reputation: 1040Reputation: 1040Reputation: 1040Reputation: 1040Reputation: 1040Reputation: 1040Reputation: 1040
As there are a lot of differences between 2.6.20.4 and 2.6.27.7 I would install one of the stock 2.6.27.7 kernels instead of re-using the old .config otherwise you could miss some important stuff. And it is very possible that some software in 12.2 simply won't work with your old kernel. It will always be possible to customize the new kernel after you have checked that everything works with the stock one if you like or need.

Not to miss any package during the upgrade, I would have done this
1) install slackpkg (included in 2.2) then edit /etc/slackpkg/mirrors to un comment one mirror as stated in the file
2) slackpkg update
3) slackpkg update-gpg
4) slackpkg glibc-solibs # a lot of other packages rely in this one, which should be at the good version
4) slackpkg upgrade-all # does what it says
5) slackpkg install-new # to get new packages of course, aka those not included in 11.0
6) slackpkg clean-system # to remove obsolete packages and all other packages no included in 12.2, unless you un check it when asked
7) slackpkg new-config # to check all modified configuration files, replace or update the old ones

As you will have installed a new kernel, check/edit /etc/lilo.conf and run lilo

Of course make executable the (possibly new) scripts you need to run in /etc/rc.d

And remember that UDEV's usage is almost mandatory in slackware 12.2.

Anyhow, as 12.2 very different from 11.0, my feeling is you would have been better off making a clean new install than upgrading.

About groups, following Hitest's post, check that your regular users are members of plugdev group (as well audio, cdrom, floppy, video and may be lp as needed).

Last edited by Didier Spaier; 03-24-2009 at 09:34 AM.
 
Old 03-26-2009, 10:21 AM   #4
pierpatbsz
LQ Newbie
 
Registered: Mar 2009
Location: Trieste - Italy
Distribution: slackware
Posts: 8

Original Poster
Rep: Reputation: 0
Quote:
Originally Posted by Didier Spaier View Post
Anyhow, as 12.2 very different from 11.0, my feeling is you would have been better off making a clean new install than upgrading.

About groups, following Hitest's post, check that your regular users are members of plugdev group (as well audio, cdrom, floppy, video and may be lp as needed).
Sorry, in fact i installed 12.2 in another disk with almost packages that i used in 11.0.
Now i've re-installed with every packages of 12.2: during installation i plugged the camera in usb port, and installation recognized it, and i mounted it as vfat from second console.

But when i started with kernel distribuited whit slack hugesmp i still could not mount my camera.

i'm asking me what kind of kernel is running during installation while i suppose that huge fully support devices?
 
Old 03-26-2009, 01:56 PM   #5
Didier Spaier
Senior Member
 
Registered: Nov 2008
Location: Paris, France
Distribution: Slackware{,64}-{14.1,current} on a Lenovo Thinkpad T61 6457-4XG
Posts: 4,234

Rep: Reputation: 1040Reputation: 1040Reputation: 1040Reputation: 1040Reputation: 1040Reputation: 1040Reputation: 1040Reputation: 1040
By default the same huge-smp kernel is used during installation.

Did you try to mount the camera as root or as a regular user ? In the latter case, which groups is this regular user member of (you can check with "cat /etc/group|grep <user>"). Is (s)he member of "plugdev" (I suppose you use KDE ?) ?.

Anyway first try to mount it as root.

Please send output of "dmesg|tail" again 30 seconds after having plugged in the camera, as well as the output of "lsmod" whilst the camera is still plugged-in.

Last edited by Didier Spaier; 03-26-2009 at 02:09 PM.
 
Old 03-27-2009, 04:39 AM   #6
pierpatbsz
LQ Newbie
 
Registered: Mar 2009
Location: Trieste - Italy
Distribution: slackware
Posts: 8

Original Poster
Rep: Reputation: 0
Quote:
Originally Posted by Didier Spaier View Post
By default the same huge-smp kernel is used during installation.

Did you try to mount the camera as root or as a regular user ? In the latter case, which groups is this regular user member of (you can check with "cat /etc/group|grep <user>"). Is (s)he member of "plugdev" (I suppose you use KDE ?) ?.

Anyway first try to mount it as root.

Please send output of "dmesg|tail" again 30 seconds after having plugged in the camera, as well as the output of "lsmod" whilst the camera is still plugged-in.
I mount the camera as root. Now I re-compiled the kernel with the config file in kernel/hugesmp.s directory of slackware without any good news...
Now all USB support is compiled built-in the kernel.
Here are the logs. Thanks a lot for your collaboration!

dmesg
usb 3-1: new full speed USB device using uhci_hcd and address 2
usb 3-1: configuration #1 chosen from 1 choice
scsi10 : SCSI emulation for USB Mass Storage devices
usb-storage: device found at 2
usb-storage: waiting for device to settle before scanning
usb 3-1: New USB device found, idVendor=0784, idProduct=1692
usb 3-1: New USB device strings: Mfr=1, Product=2, SerialNumber=3
usb 3-1: Product: HDC-763E
usb 3-1: Manufacturer: HITACHI
usb 3-1: SerialNumber: 0000000000000000
scsi 10:0:0:0: Direct-Access HITACHI HDC-763E 1.10 PQ: 0 ANSI: 0 CC
S
sd 10:0:0:0: [sdc] 4095630 512-byte hardware sectors (2097 MB)
sd 10:0:0:0: [sdc] Write Protect is off
sd 10:0:0:0: [sdc] Mode Sense: 00 06 00 00
sd 10:0:0:0: [sdc] Assuming drive cache: write through
sd 10:0:0:0: [sdc] 4095630 512-byte hardware sectors (2097 MB)
sd 10:0:0:0: [sdc] Write Protect is off
sd 10:0:0:0: [sdc] Mode Sense: 00 06 00 00
sd 10:0:0:0: [sdc] Assuming drive cache: write through
sdc: sdc1
sd 10:0:0:0: [sdc] Attached SCSI removable disk
sd 10:0:0:0: Attached scsi generic sg2 type 0
usb-storage: device scan complete
sd 10:0:0:0: [sdc] Result: hostbyte=0x00 driverbyte=0x08
sd 10:0:0:0: [sdc] Sense Key : 0x3 [current]
sd 10:0:0:0: [sdc] ASC=0x11 ASCQ=0x0
end_request: I/O error, dev sdc, sector 4095488
Buffer I/O error on device sdc, logical block 2047744
sd 10:0:0:0: [sdc] Result: hostbyte=0x00 driverbyte=0x08
sd 10:0:0:0: [sdc] Sense Key : 0x3 [current]
sd 10:0:0:0: [sdc] ASC=0x11 ASCQ=0x0
end_request: I/O error, dev sdc, sector 4095490
Buffer I/O error on device sdc, logical block 2047745
Buffer I/O error on device sdc, logical block 2047746
Buffer I/O error on device sdc, logical block 2047747
sd 10:0:0:0: [sdc] Result: hostbyte=0x00 driverbyte=0x08
sd 10:0:0:0: [sdc] Sense Key : 0x3 [current]
sd 10:0:0:0: [sdc] ASC=0x11 ASCQ=0x0
end_request: I/O error, dev sdc, sector 4095488

# lsmod
Module Size Used by
snd_seq_dummy 6788 0
snd_seq_oss 33408 0
snd_seq_midi_event 10240 1 snd_seq_oss
snd_seq 50928 5 snd_seq_dummy,snd_seq_oss,snd_seq_midi_event
snd_seq_device 10380 3 snd_seq_dummy,snd_seq_oss,snd_seq
snd_pcm_oss 40480 0
snd_mixer_oss 17920 1 snd_pcm_oss
lp 13572 0
fuse 54684 3
snd_hda_intel 367756 0
snd_pcm 70788 2 snd_pcm_oss,snd_hda_intel
snd_timer 23176 2 snd_seq,snd_pcm
snd_page_alloc 11400 2 snd_hda_intel,snd_pcm
intel_agp 29116 0
snd_hwdep 10756 1 snd_hda_intel
agpgart 32584 1 intel_agp
snd 51748 9 snd_seq_oss,snd_seq,snd_seq_device,snd_pcm_oss,snd_mixer_oss,snd_hda_intel,snd_pcm,snd_timer,snd_hwd ep
soundcore 10080 1 snd
i2c_i801 12688 0
sg 30516 0
r8169 31236 0
mii 8448 1 r8169
evdev 13088 3
ppdev 11268 0
thermal 19484 0
parport_pc 28196 1
processor 36648 1 thermal
parport 34796 3 lp,ppdev,parport_pc
thermal_sys 15144 2 thermal,processor
psmouse 40592 0
serio_raw 9220 0
hwmon 6300 1 thermal_sys
button 10128 0
 
Old 03-27-2009, 04:54 AM   #7
gegechris99
Member
 
Registered: Oct 2005
Location: France
Distribution: Slackware 14.1 32bit
Posts: 722
Blog Entries: 3

Rep: Reputation: 76
Quote:
Originally Posted by pierpatbsz View Post
I mount the camera as root.
With gphoto2/libgphoto2 packages now inlcuded in Slackware 12.2, you should not need to mount the camera manually (and especially as root).

Did you check that your camera is configured to connect to a PC in PTP mode and not as a USB storage device?

My father's camera (BENQ something) wouldn't be recognized until I switched the connection mode to PTP. And then, the camera was automatically recognized and mounted with my normal user.
 
Old 03-27-2009, 05:15 AM   #8
Didier Spaier
Senior Member
 
Registered: Nov 2008
Location: Paris, France
Distribution: Slackware{,64}-{14.1,current} on a Lenovo Thinkpad T61 6457-4XG
Posts: 4,234

Rep: Reputation: 1040Reputation: 1040Reputation: 1040Reputation: 1040Reputation: 1040Reputation: 1040Reputation: 1040Reputation: 1040
Sorry, no clue.

We still see these errors messages in dmesg's outpt e.g.:
end_request: I/O error, dev sdc, sector 4095488
which probably prevent you to mount the device as /dev/sdc1 though you have following line too in dmesg's output:
sdc: sdc1

I think your problem is related to that, but do not see what can cause these messages.

I understand that you eventually made a full install or Slackware 12.2 from scratch. If that's hopefully true you could try to switch to kernel-generic-2.6.27.7-i486-1; check that kernel-modules-smp-2.6.27.7_smp-i686-1 package be installed as well, do not forget to make an initrd (see /boot/README.initrd) to include your root partition's file system module, edit /etc/lilo.conf accordingly then run lilo.

But to be honest, I'm afraid this will not solve your problem.

Last edited by Didier Spaier; 03-27-2009 at 05:57 AM.
 
Old 03-27-2009, 05:48 AM   #9
titopoquito
Senior Member
 
Registered: Jul 2004
Location: Ruhr Area, Germany
Distribution: Slackware64 14.0
Posts: 1,517

Rep: Reputation: 90
I wonder if your SD card might have gotten messed up somehow. If there are now no important images on it I would reformat it in the camera (something you should do anyway from time to time) to be sure that your problem is not about card errors.
 
Old 03-27-2009, 08:22 AM   #10
pierpatbsz
LQ Newbie
 
Registered: Mar 2009
Location: Trieste - Italy
Distribution: slackware
Posts: 8

Original Poster
Rep: Reputation: 0
Quote:
Originally Posted by Didier Spaier View Post
Sorry, no clue.

We still see these errors messages in dmesg's outpt e.g.:
end_request: I/O error, dev sdc, sector 4095488
which probably prevent you to mount the device as /dev/sdc1 though you have following line too in dmesg's output:
sdc: sdc1

I think your problem is related to that, but do not see what can cause these messages.
The messages appears in dmesg some seconds after "usb-storage: device scan complete"
and after mount command or other commands that i try to do on /dev/sdc1.
"mount -t vfat /dev/sdc1 /MYUSB" answers: can't read super-block

Last edited by pierpatbsz; 03-27-2009 at 08:30 AM.
 
Old 03-27-2009, 08:25 AM   #11
pierpatbsz
LQ Newbie
 
Registered: Mar 2009
Location: Trieste - Italy
Distribution: slackware
Posts: 8

Original Poster
Rep: Reputation: 0
Quote:
Originally Posted by titopoquito View Post
I wonder if your SD card might have gotten messed up somehow. If there are now no important images on it I would reformat it in the camera (something you should do anyway from time to time) to be sure that your problem is not about card errors.
Every command on device fail. So I cannot do fdisk or re-create fat partition.
 
Old 03-27-2009, 09:22 AM   #12
titopoquito
Senior Member
 
Registered: Jul 2004
Location: Ruhr Area, Germany
Distribution: Slackware64 14.0
Posts: 1,517

Rep: Reputation: 90
Quote:
Originally Posted by pierpatbsz View Post
Every command on device fail. So I cannot do fdisk or re-create fat partition.
I was not talking about fdisk but about the camera. Most cameras have the ability (look in your manual or the menus of your camera) to format new storage cards. If you delete single pictures, maybe edit some (all in the camera) and so on there can occur errors on the card. That's why some people suggest to (re)format the card (in the camera) every time it's inserted.
 
Old 03-27-2009, 09:40 AM   #13
pierpatbsz
LQ Newbie
 
Registered: Mar 2009
Location: Trieste - Italy
Distribution: slackware
Posts: 8

Original Poster
Rep: Reputation: 0
Quote:
Originally Posted by titopoquito View Post
I was not talking about fdisk but about the camera
The camera is new, I format the memory before first use with the camera;

I reformated it after the errors while tried to mount with slack 12; but when i succesfully mount in slack 11 and even 12 on other pc, I suppose that something is wrong in my slack installation or kernel compilation...

This evening at home I'll try another time.

Thank you for interesting,
Pierpaolo
 
Old 03-27-2009, 10:12 AM   #14
theNbomr
LQ 5k Club
 
Registered: Aug 2005
Distribution: OpenSuse, Fedora, Redhat, Debian
Posts: 5,395
Blog Entries: 2

Rep: Reputation: 903Reputation: 903Reputation: 903Reputation: 903Reputation: 903Reputation: 903Reputation: 903Reputation: 903
A useful exercise may be to remove the flash memory from the camera, and insert it into a (USB) card reader. This may expose whether the problem lies with the card, or the camera. Universal media card readers can be purchased for under $15 in my locale.
--- rod.
 
Old 04-06-2009, 08:59 AM   #15
pierpatbsz
LQ Newbie
 
Registered: Mar 2009
Location: Trieste - Italy
Distribution: slackware
Posts: 8

Original Poster
Rep: Reputation: 0
I stopped the udev service and i can mount the camera.
I think the problem is in the udev 1.35 of slack 12.2!

log of udevadm monitor is ready!

Other trial and result come soon as possible.

Bye,
Pierpaolo
 
  


Reply

Tags
camera, error, usb


Thread Tools Search this Thread
Search this Thread:

Advanced Search

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

BB code is On
Smilies are On
[IMG] code is Off
HTML code is Off


Similar Threads
Thread Thread Starter Forum Replies Last Post
usb mass storage device won't mount. tethysgods Linux - Hardware 3 06-21-2006 10:11 AM
Errors trying to mount USB Mass Storage Device leozumbado Linux - Software 2 06-10-2006 02:57 PM
Windows no longer recognizes my USB mass storage after installed Slackware 10.2 ivancauso General 25 12-13-2005 08:03 AM
HP Photosmart 7760 - Unable to mount usb mass storage coreyhanson Fedora - Installation 0 02-27-2005 09:25 PM
Errors trying to mount USB Mass Storage Device Ctawp Linux - Hardware 7 12-04-2003 01:32 AM


All times are GMT -5. The time now is 12:10 AM.

Main Menu
My LQ
Write for LQ
LinuxQuestions.org is looking for people interested in writing Editorials, Articles, Reviews, and more. If you'd like to contribute content, let us know.
Main Menu
Syndicate
RSS1  Latest Threads
RSS1  LQ News
Twitter: @linuxquestions
identi.ca: @linuxquestions
Facebook: linuxquestions Google+: linuxquestions
Open Source Consulting | Domain Registration