1 |
Paul Stear posted on Sun, 20 Dec 2009 12:26:43 +0000 as excerpted: |
2 |
|
3 |
> On Saturday 19 Dec 2009 20:59:52 Duncan wrote: |
4 |
>> Paul Stear posted on Sat, 19 Dec 2009 14:27:49 +0000 as excerpted: |
5 |
>> > Thanks for the replies, I have updated the kernel, udev and hal and |
6 |
>> > the cd stays closed on boot. Thanks for the info. However I now |
7 |
>> > have another problem: |
8 |
>> > When I insert a usb drive or put a cd into the cd drive I am not |
9 |
>> > getting any notification that they have been detected. I have now |
10 |
>> > realised that this hasn't been working for sometime. Any thoughts on |
11 |
>> > how to resolve this? |
12 |
>> |
13 |
>> No notice... on what level? At the desktop? What desktop environment |
14 |
>> do you use? No notification in the system log? For the USB drive, |
15 |
>> does the device show up as a new /dev/sdX when you plug it in? Does |
16 |
>> lsusb see it? |
17 |
>> |
18 |
>> IOW, you didn't include enough information to know where to start on |
19 |
>> that problem, or even at what level the problem is appearing, |
20 |
>> system/kernel/ udev level, desktop environment level, or somewhere on |
21 |
>> the stack (dbus, hal, perhaps fstab) between the two. |
22 |
|
23 |
> You are right I didn't give enough information. I am running kde 4.3.4. |
24 |
> dmesg reports the flash disc as sde The entry sde1 in directory media is |
25 |
> blank. There is no entry for sde also the kde desktop did not report |
26 |
> the device, in fact no pop up at all. |
27 |
> Looking at /dev/disk/by-id: |
28 |
> ata-DVD-ROM_BVD316E link tp /hdb |
29 |
> ata-PHILIPS_DVDR16LS_DCV0516041208 linked to /hda |
30 |
> |
31 |
> The In /DEV cdrom2 cdrom3 cdrw3 dvd2 dvd3 dvdrw3 are all linked to /hdb |
32 |
> but I have no entry for /hdb in /media So again if I insert a music cd |
33 |
> in any of the drives, nothing happens. I used to get a pop up on the |
34 |
> kde desktop asking what I wanted to do and displaying various options, |
35 |
> e.g. play, copy, rip etc. |
36 |
> |
37 |
> This seems to be a bit of a mess and help will be greatly appreciated. |
38 |
|
39 |
OK, that's a bit better. We know the kernel and udev seem to be doing |
40 |
their thing correctly, if the devices are showing up in /dev. |
41 |
|
42 |
But we don't know whether it's hal or kde, now, or possibly dbus (oh, and |
43 |
do you have policykit installed and the USE flag enabled, that's another |
44 |
possibility...). hal config issues can be seriously un-fun to try to |
45 |
debug and fix, even for people who prefer the command line for most stuff. |
46 |
|
47 |
It /may/ be worth simply doing your mounts from the commandline, and |
48 |
similarly, starting your cdplayer app manually instead of letting the |
49 |
popup handle it, rather than trying to figure out hal. |
50 |
|
51 |
I do know that if there's an entry in fstab for it, hal /used/ to ignore |
52 |
the fstab entry and mount it in /media on its own anyway, but now defers |
53 |
to the fstab entry and ignores the event. I thought that might be the |
54 |
issue, but while you didn't mention fstab, since I asked you about it, |
55 |
I'm assuming there's no entry corresponding to either of the device |
56 |
entries there. |
57 |
|
58 |
Something else you might consider, tho it's not urgent and AFAIK is |
59 |
unrelated to this, but who knows? /dev/hd? indicates that you're still |
60 |
using the old kernel ide drivers. Those are now officially deprecated, |
61 |
with the newer libata SATA/PATA drivers the encouraged replacement (yes, |
62 |
even tho the config still says pata's experimental). They'll use sd? |
63 |
notation instead of the older hd? notation, so then you'll not have any |
64 |
hd? devices at all. Unless you /know/ that you don't have libata support |
65 |
for your old ide/pata chipset, I'd strongly encourage you to consider |
66 |
switching... at your leisure, tho. |
67 |
|
68 |
And I'd suggest you run kernel 2.6.27 or newer (/I'd/ suggest 2.6.30 or |
69 |
newer, probably 2.6.31 as 2.6.32 won't be keyworded stable yet, but...) |
70 |
as the newer udevs work best with it, even if they only require 2.6.25. |
71 |
|
72 |
It's /possible/ that the problem will more or less "magically" disappear, |
73 |
if you switch to the SATA/PATA drivers, with a reasonably new kernel and |
74 |
udev, and dbus and hal, while you are at it. I'd at least ensure I was |
75 |
running the latest stable of each. Then do a revdep-rebuild, and at |
76 |
least rebuild kdelibs if anything changed. If we're lucky, it's just |
77 |
something getting out of sync, not any real bug or config issue, and |
78 |
updating to the latest stable (or latest ~arch if that's what you |
79 |
normally run) on all of it, plus rebuilding kdelibs and doing a revdep- |
80 |
rebuild, will get you running without even touching the headache that hal |
81 |
and policykit could well be if it's necessary to debug their config. |
82 |
|
83 |
-- |
84 |
Duncan - List replies preferred. No HTML msgs. |
85 |
"Every nonfree program has a lord, a master -- |
86 |
and if you use the program, he is your master." Richard Stallman |