From: "Phill" <poflynn@bigpond.net.au>
To: linux-hotplug@vger.kernel.org
Subject: RE: linmodem & fedora 3
Date: Sat, 22 Jan 2005 11:05:55 +0000 [thread overview]
Message-ID: <000801c50072$587806e0$0201a8c0@desktop> (raw)
[-- Attachment #1: Type: text/plain, Size: 1515 bytes --]
Thanks for all the responses I have tried them out but am still having the
same problem
Here is a list of the different rules I tried to apply. Is there something
wrong with them?
KERNEL="ttLTM0", SYSFS{dev}="62:64", NAME="modem", SYMLINK="modem"
previous attempts also included
KERNEL="ttyLT0", SYMLINK="modem"
and
KERNEL="ttLTM0", NAME="modem", SYMLINK="modem"
and
KERNEL="ttyLT0", NAME="modem", SYMLINK="modem"
After using the commands "Modprobe lt_serial" and "Modprobe lt_modem"
without any errors (/dev/ttyLT0 and /dev/modem are not created), i used
the follwing commands to test the udev installation
#udevinfo -a -p /sys/module/lt_modem/
returned:
looking at class device '/sys/module/lt_modem':
SYSFS{refcnt}="3"
udevinfo -a -p /sys/class/tty/ttLTM0
returned:
looking at class device '/sys/class/tty/ttLTM0':
SYSFS{dev}="62:64"
udevinfo -a -p /sys/module/lt_serial/
returned:
looking at class device '/sys/module/lt_serial':
SYSFS{refcnt}="0"
udevinfo -a -p /sys/module/lt_modem/
returned:
looking at class device '/sys/module/lt_modem':
SYSFS{refcnt}="3"
So, after hours of frustration, i purchased a dlink dfm-562e external
modem. Which kudzu correctly detected and installed (so it would seem).
/dev/modem1 is generated but again on subsequent reboots the character
device drivers are no longer present
is this a udev problem or something else?
Regards,
Phill
[-- Attachment #2: smime.p7s --]
[-- Type: application/x-pkcs7-signature, Size: 3075 bytes --]
next reply other threads:[~2005-01-22 11:05 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-01-22 11:05 Phill [this message]
-- strict thread matches above, loose matches on Subject: below --
2005-01-21 9:36 linmodem & fedora 3 Bob Barry
2005-01-20 18:53 Phill
2005-01-20 20:47 ` Kay Sievers
2005-01-21 4:33 ` Alexander E. Patrakov
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to='000801c50072$587806e0$0201a8c0@desktop' \
--to=poflynn@bigpond.net.au \
--cc=linux-hotplug@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).