WelcomeWelcome | FAQFAQ | DownloadsDownloads | WikiWiki

Author Topic: [4.5.6] udev problems  (Read 10138 times)

Offline jls

  • Hero Member
  • *****
  • Posts: 2135
[4.5.6] udev problems
« on: July 30, 2012, 05:04:20 AM »
I was trying eeze which is used by enlightenmenet to manage the devices  (cdrom, usb sticks) but it doesn't work, so I asked why on the #e freenode irc channel and 1 of the "e" developers typed me me to pastebin the results of:
Code: [Select]
udevadm info --export-db
The guy examined what I pastedbin and typed:
Quote
(13:41:35) zmike:
well either your kernel or udev are broken then
(13:41:43) zmike:
because they aren't setting the bus of your hard disks properly

and again
(13:45:34) zmike:
BUS is not set for your hard drives
(14:05:22) zmike:
your distribution seems to be incompatible with eeze due to your udev+kernel setup
...........
(14:11:36) zmike:
I will not change eeze to accommodate your distribution
(14:11:47) zmike:
I will close any bugs filed about this
« Last Edit: July 30, 2012, 05:27:43 AM by jls_legalize »
dCore user

Offline Rich

  • Administrator
  • Hero Member
  • *****
  • Posts: 11256
Re: [4.5.6] udev problems
« Reply #1 on: July 30, 2012, 05:46:25 AM »
Hi jls_legalize
You might also want to include the pastebin link in case someone needs to see it.

Online Juanito

  • Administrator
  • Hero Member
  • *****
  • Posts: 14569
Re: [4.5.6] udev problems
« Reply #2 on: July 30, 2012, 05:51:17 AM »
I seem to recall that if you load udev-extra and copy the full "60-persistent-storage.rules" from the udev source tarball, then you'll get the bus type reported correctly.

Offline jls

  • Hero Member
  • *****
  • Posts: 2135
Re: [4.5.6] udev problems
« Reply #3 on: July 30, 2012, 06:00:46 AM »
Hi jls_legalize
You might also want to include the pastebin link in case someone needs to see it.
http://pastebin.ca/2175816
juanito, thanks I'll try your suggestion
dCore user

Online Juanito

  • Administrator
  • Hero Member
  • *****
  • Posts: 14569
Re: [4.5.6] udev problems
« Reply #4 on: July 30, 2012, 06:06:58 AM »
You should see something like:
Code: [Select]
$ udevadm info -q env -n /dev/sda
DEVPATH=/devices/pci0000:00/0000:00:1f.2/host0/target0:0:0/0:0:0:0/block/sda
MAJOR=8
MINOR=0
DEVNAME=/dev/sda
DEVTYPE=disk
SUBSYSTEM=block
ID_ATA=1
ID_TYPE=disk
ID_BUS=ata
ID_MODEL=ST320LT007-9ZV142
...

Offline jls

  • Hero Member
  • *****
  • Posts: 2135
Re: [4.5.6] udev problems
« Reply #5 on: July 30, 2012, 07:20:58 AM »
I did what u suggested juanito,
I've installed udev-extra and I've copied all the  60 rules from ftp://ftp.nluug.nl/pub/metalab/distributions/tinycorelinux/4.x/x86/release/src/udev-2a30eaa.tar.xz to /lib/udev/rules.d and also to /etc/udev/rules.d
but I don't see extra info u reported like
Code: [Select]
ID_ATA=1
ID_TYPE=disk
ID_BUS=ata
ID_MODEL=ST320LT007-9ZV142
dCore user

Online Juanito

  • Administrator
  • Hero Member
  • *****
  • Posts: 14569
Re: [4.5.6] udev problems
« Reply #6 on: July 30, 2012, 07:53:03 AM »
did you try:
Code: [Select]
$ sudo udevadm control --reload-rules [shouldn't be required]
$ sudo udevadm trigger

..after copying the rules and loading udev-extra?

Edit:
Code: [Select]
$ udevadm info -q env -n /dev/sda
DEVPATH=/devices/pci0000:00/0000:00:1f.2/host0/target0:0:0/0:0:0:0/block/sda
MAJOR=8
MINOR=0
DEVNAME=/dev/sda
DEVTYPE=disk
SUBSYSTEM=block
ID_PATH=pci-0000:00:1f.2-scsi-0:0:0:0
ID_PATH_TAG=pci-0000_00_1f_2-scsi-0_0_0_0
DEVLINKS=/dev/disk/by-path/pci-0000:00:1f.2-scsi-0:0:0:0

cp 60-persistent-storage.rules from udev-173 and load udev-extra:
Code: [Select]
$ sudo udevadm trigger
$ udevadm info -q env -n /dev/sda
DEVPATH=/devices/pci0000:00/0000:00:1f.2/host0/target0:0:0/0:0:0:0/block/sda
MAJOR=8
MINOR=0
DEVNAME=/dev/sda
DEVTYPE=disk
SUBSYSTEM=block
ID_ATA=1
ID_TYPE=disk
ID_BUS=ata
ID_MODEL=APPLE_SSD_TS256C
« Last Edit: July 30, 2012, 08:05:48 AM by Juanito »

Offline roberts

  • Administrator
  • Hero Member
  • *****
  • Posts: 7361
  • Founder Emeritus
Re: [4.5.6] udev problems
« Reply #7 on: July 30, 2012, 08:32:31 AM »
did you try:
Code: [Select]
$ sudo udevadm control --reload-rules [shouldn't be required]
$ sudo udevadm trigger

..after copying the rules and loading udev-extra?

Perhaps such should be added to udev-extra's info file or even its startup script?
10+ Years Contributing to Linux Open Source Projects.

Offline jls

  • Hero Member
  • *****
  • Posts: 2135
Re: [4.5.6] udev problems
« Reply #8 on: July 30, 2012, 08:43:37 AM »
coping the rules to /etc/udev/rules.d/ and then issuing
Code: [Select]
sudo udevadm trigger works!
Thanks so much juanito

dCore user

Offline jls

  • Hero Member
  • *****
  • Posts: 2135
Re: [4.5.6] udev problems
« Reply #9 on: July 30, 2012, 09:15:22 AM »
now I see my cdrom & usb stick on my desktop, but the mount command eeze is using includes also the destination (2nd mount parameter) so it needs to be executed by root.
That's the problem now
dCore user

Online Juanito

  • Administrator
  • Hero Member
  • *****
  • Posts: 14569
Re: [4.5.6] udev problems
« Reply #10 on: July 30, 2012, 09:27:48 AM »
you could try set uid root for the command in question?

Offline jls

  • Hero Member
  • *****
  • Posts: 2135
Re: [4.5.6] udev problems
« Reply #11 on: July 30, 2012, 09:28:48 AM »
the command eeze uses is:
Code: [Select]
/usr/local/bin/mount -o noexec,nodev,nosuid,uid=1000, /dev/sr0 /media/sr0
I created a link from /mnt to media
If I try this command myself I get this error:
mount: only root can do that
dCore user

Offline curaga

  • Administrator
  • Hero Member
  • *****
  • Posts: 10969
Re: [4.5.6] udev problems
« Reply #12 on: July 30, 2012, 09:49:45 AM »
That's how linux mounts work. Only root can do arbitrary mounts that aren't specified in fstab.

Run eeze as root.
The only barriers that can stop you are the ones you create yourself.

Offline curaga

  • Administrator
  • Hero Member
  • *****
  • Posts: 10969
Re: [4.5.6] udev problems
« Reply #13 on: July 30, 2012, 09:51:51 AM »
Perhaps such should be added to udev-extra's info file or even its startup script?

I don't think it should, because this concerns adding custom rules, outside of the udev-extra extension.

Basically, custom rules will need that command regardless of whether the rule uses extra apps from the udev-extra extension.
The only barriers that can stop you are the ones you create yourself.

Offline Arslan S.

  • Hero Member
  • *****
  • Posts: 825
Re: [4.5.6] udev problems
« Reply #14 on: July 31, 2012, 02:04:50 AM »