public inbox for gentoo-user@lists.gentoo.org
 help / color / mirror / Atom feed
From: Bruce Hill <daddy@happypenguincomputers.com>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user]  Network failed and weird error message
Date: Sat, 5 Oct 2013 08:41:44 -0500	[thread overview]
Message-ID: <20131005134144.GP10604@server> (raw)
In-Reply-To: <524FE4C1.8020708@gmail.com>

On Sat, Oct 05, 2013 at 05:06:57AM -0500, Dale wrote:
> >
> > Just remove ohci and uhci from the kernel config
> >
> >
> > These days all you need is ehci for usb2 and xhci for usb3 (unless you
> > are using ancient hardware with physical usb1 ports)
> >
> 
> Well, I'm not sure about my UPS.  It could be old school usb1.  My mouse
> and keyboard is PS/2 tho. 
> 
> One additional note.  It has ran all day with no problems that I have
> seen. 
> 
> Dale 

The issue is not what interface the UPS uses, but the port(s) on your mobo.

"lspci -k" will show which kernel drivers your USB controller(s) use

You can also look at the mobo manual, or plug the model # in the
manufacturer's website, and check it's specifications.

Very doubtful you have USB 1.{0,1}, and iirc, almost, if not every, EHCI
controller has an integrated Transaction Translator so that you don't need
UHCI/OHCI anymore.

Cheers Homie!
-- 
Happy Penguin Computers               >')
126 Fenco Drive                       ( \
Tupelo, MS 38801                       ^^
support@happypenguincomputers.com
662-269-2706 662-205-6424
http://happypenguincomputers.com/

A: Because it messes up the order in which people normally read text.
Q: Why is top-posting such a bad thing?
A: Top-posting.
Q: What is the most annoying thing in e-mail?

Don't top-post: http://en.wikipedia.org/wiki/Top_post#Top-posting


  reply	other threads:[~2013-10-05 13:41 UTC|newest]

Thread overview: 36+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-10-04 16:09 [gentoo-user] Network failed and weird error message Dale
2013-10-04 19:35 ` Alan McKinnon
2013-10-04 20:19   ` Dale
2013-10-05  8:54     ` Alan McKinnon
2013-10-05 10:06       ` Dale
2013-10-05 13:41         ` Bruce Hill [this message]
2013-10-06 18:36       ` Dale
2013-10-06 18:55         ` Alan McKinnon
2013-10-06 19:24           ` Dale
2013-10-06 19:52             ` Dale
2013-10-06 19:59             ` Neil Bothwick
2013-10-06 20:31               ` Dale
2013-10-06 20:55                 ` Frank Steinmetzger
2013-10-07  0:11                   ` Dale
2013-10-07  8:08                     ` Neil Bothwick
2013-10-06 21:07             ` Alan McKinnon
2013-10-06 22:39               ` Neil Bothwick
2013-10-07  0:36               ` Dale
2013-10-06 21:42         ` Bruce Hill
2013-10-07  0:28           ` Dale
2013-10-07  8:06             ` Neil Bothwick
2013-10-07 14:17               ` Dale
2013-10-04 21:52   ` Walter Dnes
2013-10-05  9:04     ` Alan McKinnon
2013-10-05 10:13       ` Dale
2013-10-05 13:37         ` Alan McKinnon
2013-10-06 18:38           ` Dale
2013-10-13 12:26             ` Dale
2013-10-13 17:31               ` Mick
2013-10-13 21:49                 ` Dale
2013-10-14  7:23                   ` Mick
2013-10-14 15:18                     ` Dale
2013-10-14 11:03                   ` OT - RAM disks - WAS " Tanstaafl
2013-10-14 12:08                     ` Dale
2013-10-15  5:53                     ` Pandu Poluan
2013-10-07  2:29 ` Dale

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=20131005134144.GP10604@server \
    --to=daddy@happypenguincomputers.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