From: Christian Roche <christian.roche.fr@gmail.com>
To: Greg KH <greg@kroah.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: Oops: sysfs: duplicate filename 'usbdev3.3_ep81' can not be created
Date: Tue, 18 Aug 2009 21:53:51 +0100 [thread overview]
Message-ID: <589ee1d0908181353o5a648242p702ec607b78c2e56@mail.gmail.com> (raw)
In-Reply-To: <20090818015504.GA29939@kroah.com>
>> I just installed a 2.6.30 kernel:
>>
>> > uname -a
>> Linux jimi 2.6.30.5-32.fc11.i586 #1 SMP Mon Aug 17 16:21:07 EDT 2009
>> i686 i686 i386 GNU/Linux
>>
>> but it looks like I still have the pb. Below is what happens after the
>> modeswitch, and the output of lsusb.
>
> It's harmless, only a warning, but I thought it really was fixed. Oh
> well, how about the 2.6.31-rc6 kernel?
Hi again Greg,
can I test again a 2.6.31 kernel with Fedora 11 ? I don't find any
build in this series on koji. Or should I try to compile it on my own
? ( argh! :-( I haven't done that in a long time)
Besides is this message really only a harmless warning ? I'm unable to
have the USB modem work on linux, and I thought this was due to this
pb. However if you say this is really only a warning then I should
look for another cause.
In particular I get the following error :
> setserial /dev/ttyACM0
/dev/ttyACM0: Input/output error
and similarly ttyACM0 (or ACM1, ACM2, which are created by the USB
key) cannot be accessed with minicom, wvdial, etc. Do you have an idea
what could be the culprit here ?
Thanks a lot for your help!
Chris
next prev parent reply other threads:[~2009-08-18 20:53 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-08-16 13:56 Christian Roche
2009-08-17 4:44 ` Greg KH
[not found] ` <589ee1d0908171837u70e14c41hdd6fd4ab0aa50c7@mail.gmail.com>
[not found] ` <20090818015504.GA29939@kroah.com>
2009-08-18 20:53 ` Christian Roche [this message]
2009-08-18 21:19 ` Greg KH
2009-08-19 22:16 ` Christian Roche
2009-08-19 23:36 ` Greg KH
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=589ee1d0908181353o5a648242p702ec607b78c2e56@mail.gmail.com \
--to=christian.roche.fr@gmail.com \
--cc=greg@kroah.com \
--cc=linux-kernel@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
all inboxes | Powered by JetHome®