public inbox for gentoo-user@lists.gentoo.org
 help / color / mirror / Atom feed
From: Volker Armin Hemmann <volkerarmin@googlemail.com>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] USB Problems
Date: Sun, 12 Jun 2011 23:55:33 +0200	[thread overview]
Message-ID: <18169270.XOo3lSFH5F@localhost> (raw)
In-Reply-To: <4DF5268A.904@gmail.com>

On Sunday 12 June 2011 15:50:18 Dale wrote:
> meino.cramer@gmx.de wrote:
> > Hi John,
> > 
> > if sysreq does not work after inserting the usbstick then the kernel
> > stops working completly (the sysreq-code of the kernel is not
> > entered), which seems to be that something happening on very low
> > level (the problem not the sysreq-code of course... ;)
> > 
> > Just another shot into the dark:
> > Do you have modularized all usb-related stuff? This also may help to
> > let the usb-sticks work correctly.
> > 
> > Ah! Another thing: Insert the related modules into
> > /etc/conf.d/modules so that they get loaded in a very early
> > phase of the bootprocess.
> > 
> > With modules loaded and with no usb-sticks as root inspect the
> > according modules with modinfo -p<modulename>  to see, whether
> > there a additional parameters you may pass to the modules to get
> > an extra of informations or - better - to fix the issue.
> > 
> > Modify under "Kernel hacking" in the kernel config the
> > "Default message log level" to see more.
> > 
> > Furthermore there is a switch "Kernel debugging" with sub-options.
> > May be turning on these may also help to get closer to all evil ;)
> > 
> > Last thing:
> > If there is nothing valueable stored on the usbsticks:
> > Try to reformat the usbsticks. Instead of putting a FAT32-fs on the
> > bare device, create a regular partition and create a Linux-fs
> > (reiserfs, ext2/3/4 or like that) on that partition.
> > 
> > This may not be good idea in general, but - if it works - this would
> > give a hint, where to search next.
> > 
> > Good luck!
> > 
> > Best regards,
> > mcc
> 
> Have you looked to see if that mobo has a USB problem and a BIOS update
> to fix it?

lets see:
2.6.36 works fine
2.6.37 works fine
2.6.38.0 works fine
2.6.39 panic

does not look like mobo problem.

-- 
#163933



  parent reply	other threads:[~2011-06-12 21:57 UTC|newest]

Thread overview: 40+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-06-12 14:30 [gentoo-user] USB Problems john
2011-06-12 14:45 ` meino.cramer
2011-06-12 18:45   ` john
2011-06-12 19:20     ` meino.cramer
2011-06-12 20:50       ` Dale
2011-06-12 21:32         ` john
2011-06-12 21:57           ` Dale
2011-06-13  5:22             ` john
2011-06-13  5:44               ` Dale
2011-06-14  5:38                 ` john
2011-06-14  6:59                   ` Thanasis
2011-06-13  6:42               ` meino.cramer
2011-06-13 11:00                 ` Volker Armin Hemmann
2011-06-12 21:55         ` Volker Armin Hemmann [this message]
2011-06-12 22:04           ` Dale
2011-06-12 21:30       ` john
2011-06-12 23:35         ` Volker Armin Hemmann
2011-06-12 23:56         ` meino.cramer
2011-06-12 21:54 ` Volker Armin Hemmann
2011-06-15 23:34 ` Peter Humphrey
  -- strict thread matches above, loose matches on Subject: below --
2011-06-14  7:18 JDM
2011-06-14 11:52 ` Indi
2011-06-14 15:50   ` Dale
2011-06-14 15:56     ` Thanasis
2011-06-16  7:30 JDM
2014-08-26 20:29 siefke_listen
2014-08-27  5:54 ` Alexander Kapshuk
2014-08-27  6:04 ` Alexander Kapshuk
2014-08-28 18:49 ` siefke_listen
2014-09-03 23:25 ` siefke_listen
2014-09-04  4:58   ` J. Roeleveld
2014-09-06 16:52     ` siefke_listen
2014-09-06 17:38       ` Alexander Kapshuk
2014-09-06 18:35       ` J. Roeleveld
2014-09-06 23:11         ` siefke_listen
2014-09-07  7:42           ` J. Roeleveld
2014-09-07 15:54             ` siefke_listen
2014-09-08 19:03               ` J. Roeleveld
2014-09-08 20:04                 ` Neil Bothwick
2014-09-09  5:04                 ` Stroller

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=18169270.XOo3lSFH5F@localhost \
    --to=volkerarmin@googlemail.com \
    --cc=gentoo-user@lists.gentoo.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