From: Bob Barry <bobb@absamail.co.za>
To: linux-hotplug@vger.kernel.org
Subject: Re: linmodem & fedora 3
Date: Fri, 21 Jan 2005 09:36:21 +0000 [thread overview]
Message-ID: <200501211136.21437.bobb@absamail.co.za> (raw)
Phill -
On Fri, 21 Jan 2005 you wrote:
> I have a lucent winmodem and am having problems after a reboot.
> I have tested the modem post install and everything seems to be ok.
> However, /dev/ttyLT0 and /dev/modem exist on the system until a
> reboot
In /etc/modules.autoload.d/kernel-2.6 (or fedora3 equivalent), add:
# Modem:
ltserial
In my udev rules file (/etc/udev/rules.d/49-udev.rules) I put:
# Lucent WinModem
KERNEL="ttyLT0", SYMLINK="modem"
...so that I can use /dev/modem
> I have tried to install using the rpm and compiling from the source
> same results
Which ltmodem source package? I've had good luck with ltmodem-2.6-alk-6.
A small patch is required for kernels after 2.6.9.
> Can anybody please put tell me how to configure udev appropriately?
It's not a udev issue - for ltmodem problems, mail to "Discuss@linmodems.org".
-------------------------------------------------------
This SF.Net email is sponsored by: IntelliVIEW -- Interactive Reporting
Tool for open source databases. Create drag-&-drop reports. Save time
by over 75%! Publish reports on the web. Export to DOC, XLS, RTF, etc.
Download a FREE copy at http://www.intelliview.com/go/osdn_nl
_______________________________________________
Linux-hotplug-devel mailing list http://linux-hotplug.sourceforge.net
Linux-hotplug-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/linux-hotplug-devel
next reply other threads:[~2005-01-21 9:36 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-01-21 9:36 Bob Barry [this message]
-- strict thread matches above, loose matches on Subject: below --
2005-01-22 11:05 linmodem & fedora 3 Phill
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=200501211136.21437.bobb@absamail.co.za \
--to=bobb@absamail.co.za \
--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).