Post new topic   Reply to topic
View previous topic Printable version Log in to check your private messages View next topic
Author Message
BarlafussOffline
Post subject:   PostPosted: 19.11.2013, 18:04



Joined: 2010-09-14
Posts: 45

Status: Offline
but, is CD/DVD Auto detection now YET functional?
As reported above by krisbee, vinur, phileom, it seemed NOT working with D U of some days ago ...
Thanks,
Barlafuss
 
 View user's profile Send private message  
Reply with quote Back to top
phileomOffline
Post subject:   PostPosted: 20.11.2013, 11:05



Joined: 2012-05-04
Posts: 10

Status: Offline
The problem is still here for me
 
 View user's profile Send private message  
Reply with quote Back to top
polixOffline
Post subject:   PostPosted: 20.11.2013, 16:06



Joined: 2012-10-20
Posts: 28
Location: Germany
Status: Offline
      phileom wrote:
The problem is still here for me


Maybe the upgrade to next KDE 4.11.4 will solve your problem.

Greetings
polix
 
 View user's profile Send private message  
Reply with quote Back to top
gawlOffline
Post subject:   PostPosted: 22.11.2013, 20:33



Joined: 2011-01-26
Posts: 9

Status: Offline
      vinur wrote:
its true, Auto detection seems to be non functional...


After my last d-u, it seems even worse: Not only does auto-detection of CDs/DVDs fail, but auto-detection of all USB-storage media fails as well.

--lsusb lists all connected USB devices correctly.

--But...:
      Code:
dmesg|tail
does not show the usual message(s) related to a newly connected USB media.

--No automatic creation of a block device in /dev (at least not for flash storage cards in a card reader; with external USB hard drives, device creation seems to succeed).

--However, if I manually create a new device the way I did in the good old days, e.g. via
      Code:
sudo mknod /dev/sdd1 b 8 49

then I can mount the USB media without any problem, even if it's a flash card. (But even then dolphin does not show this device.)

--After(!) such a manual mount some messages related to the usb media are added to dmesg. (Before my d-u, these messages appeared automatically.)

Info: I've got a desktop PC with an Intel i5-2500 CPU, kernel is 3.12-0.slh.3-aptosid-686,
udev 204-5 seems to be running properly. udisks 1.0.4-8+b1 is installed.
 
 View user's profile Send private message  
Reply with quote Back to top
finottiOffline
Post subject:   PostPosted: 22.11.2013, 21:41



Joined: 2010-09-12
Posts: 312

Status: Offline
I seem to have the same problem, FWIW.
 
 View user's profile Send private message  
Reply with quote Back to top
slhOffline
Post subject:   PostPosted: 22.11.2013, 22:10



Joined: 2010-08-25
Posts: 733

Status: Offline
While pretty unlikely to accidentally lose it, please check that you have udev installed (and at which version).
 
 View user's profile Send private message  
Reply with quote Back to top
finottiOffline
Post subject:   PostPosted: 22.11.2013, 22:37



Joined: 2010-09-12
Posts: 312

Status: Offline
OK, perhaps my situation is different. The device does appear in dmesg:

      Code:

[30831.327945] sd 7:0:0:0: Attached scsi generic sg2 type 0
[30831.753131] sd 7:0:0:0: [sdb] 7823360 512-byte logical blocks: (4.00 GB/3.73 GiB)
[30831.754105] sd 7:0:0:0: [sdb] Write Protect is off
[30831.754111] sd 7:0:0:0: [sdb] Mode Sense: 23 00 00 00
[30831.754824] sd 7:0:0:0: [sdb] No Caching mode page found
[30831.754847] sd 7:0:0:0: [sdb] Assuming drive cache: write through
[30831.759716] sd 7:0:0:0: [sdb] No Caching mode page found
[30831.759723] sd 7:0:0:0: [sdb] Assuming drive cache: write through
[30831.791033]  sdb: sdb1
[30831.793622] sd 7:0:0:0: [sdb] No Caching mode page found
[30831.793630] sd 7:0:0:0: [sdb] Assuming drive cache: write through
[30831.793636] sd 7:0:0:0: [sdb] Attached SCSI removable disk


But it does not show up in KDE.

I do have the latest udev

      Code:

root@t510[/home/finotti]# apt-cache policy udev
udev:
  Installed: 204-5
  Candidate: 204-5
  Version table:
 *** 204-5 0
        500 http://ftp.us.debian.org/debian/ sid/main amd64 Packages
        100 /var/lib/dpkg/status


Thanks,

Luis
 
 View user's profile Send private message  
Reply with quote Back to top
finottiOffline
Post subject:   PostPosted: 22.11.2013, 22:47



Joined: 2010-09-12
Posts: 312

Status: Offline
OK, I might have to take it back...

I am having problems with my (android) phone. When I saw the post above, I also tried as USB stick (the one above from dmesg above), but it was my live aptosid stick (by mistake). Maybe that is why is not showing in KDE... (It did use to show up before...)

Other sticks and SD cards are showing and mounting fine in KDE.

My phone still won't show. The funny thing is: when I plug it, I get "/dev/sdb", but not sdb1. If I try:

      Code:

root@t510[~]# mount /dev/sdb
mount: can't find /dev/sdb in /etc/fstab or /etc/mtab


after the error message, the phone shows up in KDE (notification) and there is sdb1.

      Code:

root@t510[~]# lsusb
Bus 002 Device 008: ID 413c:2005 Dell Computer Corp. RT7D50 Keyboard
Bus 002 Device 002: ID 8087:0020 Intel Corp. Integrated Rate Matching Hub
Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 001 Device 005: ID 17ef:480f Lenovo Integrated Webcam [R5U877]
Bus 001 Device 004: ID 0a5c:217f Broadcom Corp. BCM2045B (BDC-2.1)
Bus 001 Device 014: ID 18d1:0c96 Google Inc.
Bus 001 Device 011: ID 0461:4d15 Primax Electronics, Ltd Dell Optical Mouse
Bus 001 Device 002: ID 8087:0020 Intel Corp. Integrated Rate Matching Hub
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub


and here is dmesg (with the phone) before the mounting attempt:

      Code:

[31150.651953] usb 1-1.2: new high-speed USB device number 14 using ehci-pci
[31150.751095] usb 1-1.2: New USB device found, idVendor=18d1, idProduct=0c96
[31150.751101] usb 1-1.2: New USB device strings: Mfr=1, Product=2, SerialNumber=3
[31150.751105] usb 1-1.2: Product: myTouch 4G
[31150.751108] usb 1-1.2: Manufacturer: T-Mobile
[31150.751111] usb 1-1.2: SerialNumber: SH15VRM00126
[31150.754030] usb-storage 1-1.2:1.0: USB Mass Storage device detected
[31150.754171] scsi9 : usb-storage 1-1.2:1.0
[31151.757611] scsi 9:0:0:0: Direct-Access     T-Mobile myTouch 4G       0100 PQ: 0 ANSI: 2
[31151.758076] sd 9:0:0:0: Attached scsi generic sg2 type 0
[31151.771637] sd 9:0:0:0: [sdb] Attached SCSI removable disk



Luis
 
 View user's profile Send private message  
Reply with quote Back to top
slhOffline
Post subject:   PostPosted: 22.11.2013, 23:17



Joined: 2010-08-25
Posts: 733

Status: Offline
finotti, please check what happens if you run "/sbin/fdisk -l /dev/sdb" (or whatever device node you'd expect to appear for your phone), that might kickstart the device (phone) detection.
 
 View user's profile Send private message  
Reply with quote Back to top
finottiOffline
Post subject:   PostPosted: 23.11.2013, 13:10



Joined: 2010-09-12
Posts: 312

Status: Offline
      slh wrote:
finotti, please check what happens if you run "/sbin/fdisk -l /dev/sdb" (or whatever device node you'd expect to appear for your phone), that might kickstart the device (phone) detection.


Yes, that works too. (BTW, this is issue is the same in two different computers, a laptop and a desktop, running up to date aptosid.)

Thanks!

Luis
 
 View user's profile Send private message  
Reply with quote Back to top
gawlOffline
Post subject:   PostPosted: 24.11.2013, 20:51



Joined: 2011-01-26
Posts: 9

Status: Offline
It seems to depend on the type of USB device.
As I said above, for an "ordinary" USB hard drive, the new entry under /dev is auto-created.
But for a flash card (SD card) in a multi-card reader (which is properly listed by lsusb), nothing happens.
For such an SD card, nothing is added to dmesg automatically.

Yes, typing in the command /sbin/fdisk -l /dev/sdd, as you suggested, shows the following reaction:
The partition table of the SD card is printed, and a new device node /dev/sdd1 is created, moreover several lines of information are added to dmesg. However, still no auto-mount.
And, by the way: If I eject the unmounted SD card, this device node /dev/sdd1 is *not* removed automatically, so, this problem is not only related to the creation, but also to the removal of device nodes.

With an "ordinary" USB hard drive, it is different, the device node (plus dmesg entries) appears automatically. Nevertheless, no auto-mount.

The same behaviour for (data) CDROMs: The device nodes (/dev/sr0 plus symlink /dev/cdrom) always exist, but no auto-mount. After entering a mount command manually, I can access the data, and two new lines are added to dmesg.

And yes, my process list shows that udevd --daemon is running. (I have udev 204-5 installed.)
 
 View user's profile Send private message  
Reply with quote Back to top
vinurOffline
Post subject: auto recognition tendency’s on the latest build  PostPosted: 25.11.2013, 07:47



Joined: 2010-09-11
Posts: 58
Location: Lake Oswego
Status: Offline
I DU again today to make sure all is current.

What I am running (KDE-full with a lot of applications, some I made work from other distros - carefully:
      Code:
Host/Kernel/OS  "Eyland0" running Linux 3.11-4.slh.2-aptosid-amd64 x86_64 [ aptosid 2013-01 Ἑσπερίδες - kde-lite - (201305050307) ]
CPU Info        8x AMD FX-8120 Eight-Core 2048 KB cache flags( sse3 ht nx lm svm ) clocked at [ 1400.000 MHz ]
Videocard       NVIDIA G86 [GeForce 8500 GT]  X.Org 1.14.3  [ 1920x1080@60.0hz ]
Network cards   D-Link System Inc DGE-560T PCI Express Gigabit
Processes 189 | Uptime 2min | Memory 631.1/7973.6MB | HDD ST3500418AS,WDC WD6000HLHX-0,AS2105 Size 1484GB (3%used) | GLX Renderer Gallium 0.4 on NV86 | GLX Version Yes | Client Shell | Infobash v3.46


All about it, if interested, I keep a Linux user page: see my user www.

I am just a clever user so advanced coding capabilities are minimal - I have with some effort compiled printer drivers, video drivers and Google Earth 7. and got them to run.

Since there are some questions about auto recognition of optical drives I have done some tests and have some findings listed here.

First the USB devices all work and are auto recognized with my machine... no problems here.
I do not have any solid state drives as portable devices so I can't test those. Just USB memory sticks

I do have a 60gig laptop drive and adapted it to USB with a converter and have had no issue at all with that... but it is always plugged in through the booting as it were and just shows and is available.

The optical disc recognition worked flawlessly with the last version of KDE (4.10.xx)
I can find workarounds so this is just an exercise in giving the details to help some if possible.

CD and DVD exhibit same behaviors, without elaboration I can play any DVD.

I mention that as a clue may be hiding in the information on behaviors.

Optical media that I made behave the same. CD and DVD
With the machine running I place the media in the player and close it... time is given to see what happens.
Nothing... until I launch K3b, then any activity with the disc is available, plays in Kaffeine and it is seen in dolphin as well as a "K3b project", not by name of disc.

DVD same story, except a commercial disc is disabled due to famous issues. My DVD's discs that I made are fine.

With the machine off and a disc in the player:
when I turn on the machine and it boots all discs are available after boot up. all CD and DVD's will play and are seen by title in dolphin.

Kaffeine has playability right away (all discs CD- and DVD, commercial or otherwise)... before, when disk was placed in a running machine the disc were available only after K3b 2.02 launched.

Don't know if this helps but this is what I have found with some testing.
I don't use optical data much so this is not a problem for me at this time.

I have an internal blu-ray player as an Optical Drive.

Like I said I am pretty good with finding work-arounds so this is just a report of the state as it is currently.

Everything else is good.
 
 View user's profile Send private message Visit poster's website  
Reply with quote Back to top
stefutzOffline
Post subject:   PostPosted: 25.11.2013, 09:04



Joined: 2010-11-29
Posts: 20

Status: Offline
heve you guys tried installing udisk2 ? it is the new prerequisite for automounting
 
 View user's profile Send private message  
Reply with quote Back to top
finottiOffline
Post subject:   PostPosted: 25.11.2013, 11:01



Joined: 2010-09-12
Posts: 312

Status: Offline
It was already there for me:

      Code:

root@debian[/home/finotti]# apt-cache policy udisks2
udisks2:
  Installed: 2.1.1-1
  Candidate: 2.1.1-1
  Version table:
 *** 2.1.1-1 0
        500 http://ftp.us.debian.org/debian/ sid/main amd64 Packages
        500 http://ftp.us.debian.org/debian/ testing/main amd64 Packages
        100 /var/lib/dpkg/status
root@debian[/home/finotti]# apt-cache policy udisks
udisks:
  Installed: 1.0.4-8+b1
  Candidate: 1.0.4-8+b1
  Version table:
 *** 1.0.4-8+b1 0
        500 http://ftp.us.debian.org/debian/ sid/main amd64 Packages
        500 http://ftp.us.debian.org/debian/ testing/main amd64 Packages
        100 /var/lib/dpkg/status


(udisks-glue is not...)
 
 View user's profile Send private message  
Reply with quote Back to top
vinurOffline
Post subject: udisks2 and glue  PostPosted: 25.11.2013, 18:23



Joined: 2010-09-11
Posts: 58
Location: Lake Oswego
Status: Offline
I too have it.
      Code:
michael@Eyland0:~$ apt-cache policy udisks2
udisks2:
  Installed: 2.1.1-1
  Candidate: 2.1.1-1
  Version table:
 *** 2.1.1-1 0
        500 http://ftp.de.debian.org/debian/ unstable/main amd64 Packages
        500 http://ftp.us.debian.org/debian/ testing/main amd64 Packages
        500 http://cdn.debian.net/debian/ sid/main amd64 Packages
        100 /var/lib/dpkg/status
michael@Eyland0:~$


and I do have udisks-glue

      Code:
udisks-glue:
  Installed: 1.3.5-1
  Candidate: 1.3.5-1
  Version table:
 *** 1.3.5-1 0
        500 http://ftp.de.debian.org/debian/ unstable/main amd64 Packages
        500 http://ftp.us.debian.org/debian/ testing/main amd64 Packages
        500 http://cdn.debian.net/debian/ sid/main amd64 Packages
        100 /var/lib/dpkg/status
michael@Eyland0:~$
 
 View user's profile Send private message Visit poster's website  
Reply with quote Back to top
Display posts from previous:     
Jump to:  
All times are GMT - 12 Hours
Post new topic   Reply to topic
View previous topic Printable version Log in to check your private messages View next topic
Powered by Zafenio