From: Kay Sievers <kay.sievers@vrfy.org>
To: linux-hotplug@vger.kernel.org
Subject: Re: linmodem & fedora 3
Date: Thu, 20 Jan 2005 20:47:16 +0000 [thread overview]
Message-ID: <1106254036.3573.23.camel@localhost.localdomain> (raw)
In-Reply-To: <007301c4ff21$5ece7990$0201a8c0@desktop>
On Fri, 2005-01-21 at 05:53 +1100, Phill wrote:
> I'm told this is the place to discuss udev issues
>
> 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
>
> I have tried to install using the rpm and compiling from the source – same
> results
>
> Can anybody please put tell me how to configure udev appropriately?
What exactly is the problem? Are the nodes for your device not created
or is the device not working as you expect. udev creates/removes only
device nodes and does nothing else with your hardware and there is
probably nothing you need to configure on the udev side.
Kay
-------------------------------------------------------
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 prev parent reply other threads:[~2005-01-20 20:47 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-01-20 18:53 linmodem & fedora 3 Phill
2005-01-20 20:47 ` Kay Sievers [this message]
2005-01-21 4:33 ` Alexander E. Patrakov
-- strict thread matches above, loose matches on Subject: below --
2005-01-21 9:36 Bob Barry
2005-01-22 11:05 Phill
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=1106254036.3573.23.camel@localhost.localdomain \
--to=kay.sievers@vrfy.org \
--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).