udevinfo has been replaced by udevadm
1,961 views
Skip to first unread message
John Canfield
Dec 27, 2010, 4:11:36 PM12/27/10
to Weewx Weather Station Discussion
I was going to install a udev script (vis-a-vis section 10.2 on the
user guide) to create a symbolic USB port per Tom's example and ran
into trouble with what I thought would be a simple five minute job.
Things change in the Linux world and udevinfo has been replaced by
udevadm and of course the options in udevinfo don't work with
udevadm. That was a really useful step for the udev developers to
take ;-)
I do not feel like spending an hour of research and fiddling at the
moment, so I'm going to sulk off for a while and feel sorry for
myself.
John
PS: I did install ferrite chokes on each end of the USB cable - at
least I got that accomplished!
user guide) to create a symbolic USB port per Tom's example and ran
into trouble with what I thought would be a simple five minute job.
Things change in the Linux world and udevinfo has been replaced by
udevadm and of course the options in udevinfo don't work with
udevadm. That was a really useful step for the udev developers to
take ;-)
I do not feel like spending an hour of research and fiddling at the
moment, so I'm going to sulk off for a while and feel sorry for
myself.
John
PS: I did install ferrite chokes on each end of the USB cable - at
least I got that accomplished!
Thomas Keffer
Dec 27, 2010, 5:44:22 PM12/27/10
to weewx...@googlegroups.com
My fit-PC is still on version 8.04, so I have not seen this. My development machine is on 10.10, but it uses a serial device, not USB.
I'm betting the ferrite coils will solve most of your problems. If not, let me know, and I'll switch my Davis Envoy (which is on the Fit) with the console (which is on my development machine).
-tk
I'm betting the ferrite coils will solve most of your problems. If not, let me know, and I'll switch my Davis Envoy (which is on the Fit) with the console (which is on my development machine).
-tk
--
You received this message because you are subscribed to the Google Groups "Weewx Weather Station Discussion" group.
To post to this group, send email to weewx...@googlegroups.com.
To unsubscribe from this group, send email to weewx-user+...@googlegroups.com.
For more options, visit this group at http://groups.google.com/group/weewx-user?hl=en.
John Canfield
Dec 28, 2010, 9:40:08 AM12/28/10
to Weewx Weather Station Discussion
Thanks for the offer Tom. I might fiddle with udev - it would be good
to get that working. Like you say, the ferrite chokes should solve
the problems - I'll let you know in six months ;-)
John
On Dec 27, 4:44 pm, Thomas Keffer <tkef...@gmail.com> wrote:
> My fit-PC is still on version 8.04, so I have not seen this. My development
> machine is on 10.10, but it uses a serial device, not USB.
>
> I'm betting the ferrite coils will solve most of your problems. If not, let
> me know, and I'll switch my Davis Envoy (which is on the Fit) with the
> console (which is on my development machine).
>
> -tk
>
> > .
to get that working. Like you say, the ferrite chokes should solve
the problems - I'll let you know in six months ;-)
John
On Dec 27, 4:44 pm, Thomas Keffer <tkef...@gmail.com> wrote:
> My fit-PC is still on version 8.04, so I have not seen this. My development
> machine is on 10.10, but it uses a serial device, not USB.
>
> I'm betting the ferrite coils will solve most of your problems. If not, let
> me know, and I'll switch my Davis Envoy (which is on the Fit) with the
> console (which is on my development machine).
>
> -tk
>
> On Mon, Dec 27, 2010 at 1:11 PM, John Canfield <johnwcanfi...@gmail.com>wrote:
>
> > I was going to install a udev script (vis-a-vis section 10.2 on the
> > user guide) to create a symbolic USB port per Tom's example and ran
> > into trouble with what I thought would be a simple five minute job.
> > Things change in the Linux world and udevinfo has been replaced by
> > udevadm and of course the options in udevinfo don't work with
> > udevadm. That was a really useful step for the udev developers to
> > take ;-)
>
> > I do not feel like spending an hour of research and fiddling at the
> > moment, so I'm going to sulk off for a while and feel sorry for
> > myself.
>
> > John
>
> > PS: I did install ferrite chokes on each end of the USB cable - at
> > least I got that accomplished!
>
> > --
> > You received this message because you are subscribed to the Google Groups
> > "Weewx Weather Station Discussion" group.
> > To post to this group, send email to weewx...@googlegroups.com.
> > To unsubscribe from this group, send email to
> > weewx-user+...@googlegroups.com<weewx-user%2Bunsu...@googlegroups.com>
>
> > I was going to install a udev script (vis-a-vis section 10.2 on the
> > user guide) to create a symbolic USB port per Tom's example and ran
> > into trouble with what I thought would be a simple five minute job.
> > Things change in the Linux world and udevinfo has been replaced by
> > udevadm and of course the options in udevinfo don't work with
> > udevadm. That was a really useful step for the udev developers to
> > take ;-)
>
> > I do not feel like spending an hour of research and fiddling at the
> > moment, so I'm going to sulk off for a while and feel sorry for
> > myself.
>
> > John
>
> > PS: I did install ferrite chokes on each end of the USB cable - at
> > least I got that accomplished!
>
> > --
> > You received this message because you are subscribed to the Google Groups
> > "Weewx Weather Station Discussion" group.
> > To post to this group, send email to weewx...@googlegroups.com.
> > To unsubscribe from this group, send email to
> > .
John Canfield
Dec 28, 2010, 5:38:49 PM12/28/10
to Weewx Weather Station Discussion
Okay - this was bugging me so I played around and figured out the
syntax for udevadm to gather device info:
udevadm info -a -p $(udevadm info -q path -n /dev/ttyUSB0) will
return everything you wanted to know about /dev/ttyUSB0.
If you try the command on a device you don't have, it will return:
device node not found
info: option requires an argument -- 'p'
which threw me for a loop since I thought I had a bad command syntax.
Hope his helps somebody.
John
syntax for udevadm to gather device info:
udevadm info -a -p $(udevadm info -q path -n /dev/ttyUSB0) will
return everything you wanted to know about /dev/ttyUSB0.
If you try the command on a device you don't have, it will return:
device node not found
info: option requires an argument -- 'p'
which threw me for a loop since I thought I had a bad command syntax.
Hope his helps somebody.
John
John Canfield
Dec 29, 2010, 4:08:17 PM12/29/10
to Weewx Weather Station Discussion
Things aren't going well with trying to install a rule. First, I
don't have a /dev/udev/rules.d directory, I have a /dev/.udev/rules.d
directory. I created the rule as per Tom's example (our hardware is
the same) and placed it in the /dev/.udev/rules.d directory and
rebooted (didn't need to do that - I could have restarted udec with /
etc/init.d/udev restart as I discovered) - that didn't work. Then I
created /dev/udev/rules.d directory and placed the rule in it,
restarted udev and that didn't work.
Things like this annoy the heck out of me - something works in one
Ubuntu release and doesn't with the next. Grrr. I'll mess with it
later.
John
don't have a /dev/udev/rules.d directory, I have a /dev/.udev/rules.d
directory. I created the rule as per Tom's example (our hardware is
the same) and placed it in the /dev/.udev/rules.d directory and
rebooted (didn't need to do that - I could have restarted udec with /
etc/init.d/udev restart as I discovered) - that didn't work. Then I
created /dev/udev/rules.d directory and placed the rule in it,
restarted udev and that didn't work.
Things like this annoy the heck out of me - something works in one
Ubuntu release and doesn't with the next. Grrr. I'll mess with it
later.
John
bttman
Dec 31, 2010, 9:17:38 AM12/31/10
to weewx...@googlegroups.com
My apologies if this is irrelevant... I am about as ignorant as one can be regarding linux.
That said, this support thread seems to address a similar issue and suggests an alternative to udev rules for Ubuntu 10+:
http://ubuntuforums.org/showthread.php?t=1452731
If it makes sense and solves the problem, I would appreciate a more "Lucid" explanation as to how one would use xorg.conf.d with weewx and the usb VP as "xorg.conf.d" might as well have been written in martian from my perspective.
joe
That said, this support thread seems to address a similar issue and suggests an alternative to udev rules for Ubuntu 10+:
http://ubuntuforums.org/showthread.php?t=1452731
If it makes sense and solves the problem, I would appreciate a more "Lucid" explanation as to how one would use xorg.conf.d with weewx and the usb VP as "xorg.conf.d" might as well have been written in martian from my perspective.
joe
> To unsubscribe from this group, send email to weewx-user+...@googlegroups.com.
John Canfield
Dec 31, 2010, 10:01:51 AM12/31/10
to Weewx Weather Station Discussion
Joe - well, not exactly irrelevant since the focus of the thread was
writing a udev rule to address touchscreen calibration, but the xorg
stuff is not relevant - it deals with the graphical user interface. I
didn't examine the rule he wrote, but apparently it didn't work
either.
In reading the thread, I didn't notice where the original poster
solved his problem :-( When I get tired of watching the bowl games,
I'll dig into udev again.
John
writing a udev rule to address touchscreen calibration, but the xorg
stuff is not relevant - it deals with the graphical user interface. I
didn't examine the rule he wrote, but apparently it didn't work
either.
In reading the thread, I didn't notice where the original poster
solved his problem :-( When I get tired of watching the bowl games,
I'll dig into udev again.
John
bttman
Dec 31, 2010, 4:45:02 PM12/31/10
to weewx...@googlegroups.com
Thanks for the clarification...
This thread seems to discuss a similar problem. If you look at the downstream responses it appears that the suggested patch was not the correct answer.
http://www.spinics.net/lists/hotplug/msg03825.html
This thread seems to discuss a similar problem. If you look at the downstream responses it appears that the suggested patch was not the correct answer.
http://www.spinics.net/lists/hotplug/msg03825.html
And, here is a link for relevant documentation:
http://www.kernel.org/pub/linux/utils/kernel/hotplug/udev/
One question that comes to mind is why is the rule being placed in the temporary rules directory rather than the default or custom rules directories?
Again, please pardon my ignorance,
joe
bttman
Dec 31, 2010, 6:55:43 PM12/31/10
to weewx...@googlegroups.com
here's a how to article I found re udev rules.
http://hackaday.com/2009/09/18/how-to-write-udev-rules/
http://hackaday.com/2009/09/18/how-to-write-udev-rules/
They do say to put the rules file in /etc/udev/rules.d/
joe
John Canfield
Jan 1, 2011, 8:39:00 AM1/1/11
to Weewx Weather Station Discussion
Joe - that's some fine digging you did! It does appear custom rules
should be in the /etc/udev/rules.d/ directory and /dev/.udev/rules.d
is only a temporary directory. Apparently that's the scenario since
the directory begins with a dot. I'll put the rule in /etc/udev/
rules.d/ and see if that works. Stay tuned.
John
On Dec 31 2010, 5:55 pm, bttman <btt...@bigtreestech.com> wrote:
> here's a how to article I found re udev rules.http://hackaday.com/2009/09/18/how-to-write-udev-rules/
should be in the /etc/udev/rules.d/ directory and /dev/.udev/rules.d
is only a temporary directory. Apparently that's the scenario since
the directory begins with a dot. I'll put the rule in /etc/udev/
rules.d/ and see if that works. Stay tuned.
John
On Dec 31 2010, 5:55 pm, bttman <btt...@bigtreestech.com> wrote:
> here's a how to article I found re udev rules.http://hackaday.com/2009/09/18/how-to-write-udev-rules/
Reply all
Reply to author
Forward
0 new messages