From: Robert Hancock <hancockrwd@gmail.com>
To: ST <st@iss.tu-darmstadt.de>
Cc: linux-kernel@vger.kernel.org
Subject: Re: 2.6.33-rc7 problems
Date: Wed, 10 Feb 2010 18:52:41 -0600 [thread overview]
Message-ID: <4B7354D9.50909@gmail.com> (raw)
In-Reply-To: <201002092306.07449.st@iss.tu-darmstadt.de>
On 02/09/2010 04:06 PM, ST wrote:
> Hi
>
> I am currently running the linus main git tree with the last commit beeing:
> deb0c98c7f6035d47a247e548384517a955314a5 (2.6.33-rc7)
>
> USB Cardreader:
> Since i am now in my third attempt to get my usb flashreader going under this
> kernel (damn this must be simple right?). I have my doubts if this is probably
> not a .config but a kernel problem. If i plug in the usb card reader i get the
> output as attached in the file "usb_problems". The .config will be also
> attached. So i thought "ok, no problem i messed up", what about the defconfig.
> (arch/x86/configs/x86_64_defconfig).
> The defconfig works slightly better by omitting the repeating thread
> awake/thread sleeping output but no device is found usable. The distribution
> is Debian/Sid. The hardware is working with the standard Debian kernel 2.6.30.
> I had a similar error when i had an typo in the default codepage "utf-8" vs.
> "utf8". But this error is fixed now and USB Sticks are working fine.
Well, the card reader apparently reports medium not present.. is there
anything in there? how is it not working?
next prev parent reply other threads:[~2010-02-11 0:52 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-02-09 22:06 2.6.33-rc7 problems ST
2010-02-10 23:40 ` 2.6.33-rc7 problems usb CF ST
2010-02-11 0:52 ` Robert Hancock [this message]
2010-02-11 21:11 ` 2.6.33-rc7 problems ST
2010-02-11 22:54 ` ST
2010-02-12 1:49 ` Robert Hancock
2010-02-12 23:18 ` ST
2010-02-13 1:14 ` Robert Hancock
2010-02-13 20:02 ` PATCH was " ST
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=4B7354D9.50909@gmail.com \
--to=hancockrwd@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=st@iss.tu-darmstadt.de \
/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