WelcomeWelcome | FAQFAQ | DownloadsDownloads | WikiWiki

Author Topic: UDEV rules problem  (Read 2124 times)

Offline mbertrand

  • Full Member
  • ***
  • Posts: 225
UDEV rules problem
« on: September 11, 2012, 01:28:21 PM »
I have a rule to make touch screen persistent. It is not working at boot but after boot if I call 'sudo udevadm trigger' it works.
Anyone know why. I've been working on this for over a month and getting no where. In Debian sqeeze the same rule worked.


Offline gerald_clark

  • TinyCore Moderator
  • Hero Member
  • *****
  • Posts: 4254
Re: UDEV rules problem
« Reply #1 on: September 11, 2012, 01:38:34 PM »
Why don't you just put it in ~/.X.d ?

Offline Rich

  • Administrator
  • Hero Member
  • *****
  • Posts: 11630
Re: UDEV rules problem
« Reply #2 on: September 11, 2012, 01:40:50 PM »
Hi mbertrand
Have you tried adding  udevadm trigger  to your  /opt/bootlocal.sh? If that fails, Try placing a script in ~/.X.d that contains:
Code: [Select]
sudo udevadm trigger

Offline mbertrand

  • Full Member
  • ***
  • Posts: 225
Re: UDEV rules problem
« Reply #3 on: September 11, 2012, 01:46:16 PM »
Yes, but should I have to. Udev is suppose to take care of this at start-up. It does so for manu other harware.

Offline mbertrand

  • Full Member
  • ***
  • Posts: 225
Re: UDEV rules problem
« Reply #4 on: September 11, 2012, 01:59:09 PM »
Why don't you just put it in ~/.X.d ?
I need this processed bfore x is started

Offline Rich

  • Administrator
  • Hero Member
  • *****
  • Posts: 11630
Re: UDEV rules problem
« Reply #5 on: September 11, 2012, 02:03:10 PM »
Hi mbertrand
If the rule and/or touch screen require X to be running in order to function, then yes, you have to. Also, I seem
to recall reading in the forums, if you add a rule, you still have to tell udev to update itself.
Quote
I need this processed bfore x is started
Then put it in  /opt/bootsync.sh