From mboxrd@z Thu Jan  1 00:00:00 1970
Return-Path: <gentoo-user+bounces-151797-garchives=archives.gentoo.org@lists.gentoo.org>
Received: from lists.gentoo.org (pigeon.gentoo.org [208.92.234.80])
	by finch.gentoo.org (Postfix) with ESMTP id 558EE1381F3
	for <garchives@archives.gentoo.org>; Tue, 22 Oct 2013 09:04:30 +0000 (UTC)
Received: from pigeon.gentoo.org (localhost [127.0.0.1])
	by pigeon.gentoo.org (Postfix) with SMTP id 372CFE0B60;
	Tue, 22 Oct 2013 09:04:25 +0000 (UTC)
Received: from mail-yh0-f42.google.com (mail-yh0-f42.google.com [209.85.213.42])
	(using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits))
	(No client certificate requested)
	by pigeon.gentoo.org (Postfix) with ESMTPS id CBFB1E0B3B
	for <gentoo-user@lists.gentoo.org>; Tue, 22 Oct 2013 09:04:23 +0000 (UTC)
Received: by mail-yh0-f42.google.com with SMTP id z6so2043307yhz.15
        for <gentoo-user@lists.gentoo.org>; Tue, 22 Oct 2013 02:04:23 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;
        d=gmail.com; s=20120113;
        h=message-id:date:from:user-agent:mime-version:to:subject:references
         :in-reply-to:content-type;
        bh=lknUpW4cnsVw+D6Z0iLlgvnbsrHxZKQrEHSXM0Ox3Xw=;
        b=puSSsWEz/FyAy6Ts3dgvZs4K6iVmAME69uwBqD82SiRHEm1hhnP+WD+P2AOzC5HwUt
         /QJkriOq2u04IkuPbCKCwstBvEgmaYG8vrftGHIZ9TvwQ2FrUK/3rH+n/YG3iUS6+dpI
         /NOA3BU/KjYywMDom4pQ52+gCUReQ27wDD3AZaJyh2KRRIX7Iei7DTUXWYyXUfMxRDaG
         F07ooht3uRGl/mFAk4JG4+rt9lLAU2M4s5dGn64TZHXSIhHWNt2Ayw4XySmSD2/Ba28Y
         ysqKkt3oMImngyyIaV5KOMDK6N3hXCh6k+s2dxaohpeo72a2slUfhQYaVKMWuSwGE8kD
         VSgg==
X-Received: by 10.236.62.169 with SMTP id y29mr695640yhc.81.1382432662931;
        Tue, 22 Oct 2013 02:04:22 -0700 (PDT)
Received: from [192.168.2.5] (adsl-65-0-124-201.jan.bellsouth.net. [65.0.124.201])
        by mx.google.com with ESMTPSA id s4sm34018098yhs.14.2013.10.22.02.04.21
        for <multiple recipients>
        (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128);
        Tue, 22 Oct 2013 02:04:22 -0700 (PDT)
Message-ID: <52663F95.8060601@gmail.com>
Date: Tue, 22 Oct 2013 04:04:21 -0500
From: Dale <rdalek1967@gmail.com>
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:24.0) Gecko/20100101 Firefox/24.0 SeaMonkey/2.21
Precedence: bulk
List-Post: <mailto:gentoo-user@lists.gentoo.org>
List-Help: <mailto:gentoo-user+help@lists.gentoo.org>
List-Unsubscribe: <mailto:gentoo-user+unsubscribe@lists.gentoo.org>
List-Subscribe: <mailto:gentoo-user+subscribe@lists.gentoo.org>
List-Id: Gentoo Linux mail <gentoo-user.gentoo.org>
X-BeenThere: gentoo-user@lists.gentoo.org
Reply-to: gentoo-user@lists.gentoo.org
MIME-Version: 1.0
To: gentoo-user@lists.gentoo.org, Dale <rdalek1967@gmail.com>
Subject: Re: [gentoo-user] Re: New mobo change
References: <525CBB88.3070202@gmail.com>	<526448C6.2000501@gmail.com>	<52646297.4040604@gmail.com>	<52646CB4.5030400@gmail.com>	<5264831C.5090909@iinet.net.au>	<52649AE9.8040708@gmail.com>	<5264A199.1070604@iinet.net.au>	<5264A55D.5010508@gmail.com>	<20131021150701.GH2497@nukleus.Speedport_W723_V_Typ_A_1_00_098>	<52656844.2000602@gmail.com>	<20131022003506.22bb1af7@digimed.co.uk>	<5265BF61.4040500@gmail.com> <20131022085019.5ee805b3@digimed.co.uk>
In-Reply-To: <20131022085019.5ee805b3@digimed.co.uk>
X-Enigmail-Version: 1.5.2
Content-Type: multipart/alternative;
 boundary="------------080207030005030401010303"
X-Archives-Salt: a311d0e6-aa20-4d89-a487-f508c9078fec
X-Archives-Hash: 3fee79490d885b292a30c1d19bf9be23

This is a multi-part message in MIME format.
--------------080207030005030401010303
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit

Neil Bothwick wrote:
> On Mon, 21 Oct 2013 18:57:21 -0500, Dale wrote:
>
>>> press Tab at the boot menu to edit isolinux options. But use one of
>>> the specifically 64 bit menu items, not the generic one that tries to
>>> determine your CPU type on the fly.
>>
>> Thanks.  I thought there was a way to edit it but I was going to have to
>> just look and see if I could figure it out.  This helps.  It gives me
>> hope that it is doable too.  ;-)
>>
>> I wonder, if I try to boot the 32 bit version if it would work?
>> According to some of the things I read, it affects the 64 bit stuff but
>> not 32 bit stuff.  Hmmmmm.  Interesting.  ^-^
>
> That's a good idea. Both use the same userspace so the only difference is
> in the kernels, and I doubt there are many differences between them
> except for the target architecture, so it old be a good test. You could
> also try the two versions of the alt kernel.
>
>

Every once in a while, my brain actually comes up with something.  ROFL

Want to hear something equally funny?  I started the UPS service that
started this whole mess to see if it works.  This is from messages:

Oct 22 02:47:50 localhost kernel: [51255.888492] ohci_hcd 0000:00:12.0:
urb ffff8803ea43f980 path 2 ep1in 93120000 cc 9 --> status -121
Oct 22 02:47:52 localhost kernel: [51257.891409] ohci_hcd 0000:00:12.0:
urb ffff8803ea43f980 path 2 ep1in 92120000 cc 9 --> status -121
Oct 22 02:47:54 localhost kernel: [51259.902338] ohci_hcd 0000:00:12.0:
urb ffff8803ea43f980 path 2 ep1in 93120000 cc 9 --> status -121
Oct 22 02:47:56 localhost kernel: [51261.905256] ohci_hcd 0000:00:12.0:
urb ffff8803ea43f980 path 2 ep1in 92120000 cc 9 --> status -121
Oct 22 02:47:58 localhost kernel: [51263.916194] ohci_hcd 0000:00:12.0:
urb ffff8803ea43f980 path 2 ep1in 93120000 cc 9 --> status -121
Oct 22 02:48:00 localhost kernel: [51265.919112] ohci_hcd 0000:00:12.0:
urb ffff8803ea43f980 path 2 ep1in 92120000 cc 9 --> status -121
Oct 22 02:48:02 localhost kernel: [51267.930020] ohci_hcd 0000:00:12.0:
urb ffff8803ea43f980 path 2 ep1in 93120000 cc 9 --> status -121
Oct 22 02:48:04 localhost kernel: [51269.932920] ohci_hcd 0000:00:12.0:
urb ffff8803ea43f980 path 2 ep1in 92120000 cc 9 --> status -121
Oct 22 02:48:06 localhost kernel: [51271.943841] ohci_hcd 0000:00:12.0:
urb ffff8803ea43f980 path 2 ep1in 93120000 cc 9 --> status -121
Oct 22 02:48:08 localhost kernel: [51273.946758] ohci_hcd 0000:00:12.0:
urb ffff8803ea43f980 path 2 ep1in 92120000 cc 9 --> status -121
Oct 22 02:48:10 localhost kernel: [51275.949676] ohci_hcd 0000:00:12.0:
urb ffff8803ea43f980 path 2 ep1in 93120000 cc 9 --> status -121
Oct 22 02:48:12 localhost kernel: [51277.960606] ohci_hcd 0000:00:12.0:
urb ffff8803ea43f980 path 2 ep1in 92120000 cc 9 --> status -121
Oct 22 02:48:14 localhost kernel: [51279.963523] ohci_hcd 0000:00:12.0:
urb ffff8803ea43f980 path 2 ep1in 93120000 cc 9 --> status -121
Oct 22 02:48:16 localhost kernel: [51281.974454] ohci_hcd 0000:00:12.0:
urb ffff8803ea43f980 path 2 ep1in 92120000 cc 9 --> status -121
Oct 22 02:48:18 localhost kernel: [51283.977370] ohci_hcd 0000:00:12.0:
urb ffff8803ea43f980 path 2 ep1in 93120000 cc 9 --> status -121
Oct 22 02:48:20 localhost kernel: [51285.980286] ohci_hcd 0000:00:12.0:
urb ffff8803ea43f980 path 2 ep1in 92120000 cc 9 --> status -121
Oct 22 02:48:22 localhost kernel: [51287.991218] ohci_hcd 0000:00:12.0:
urb ffff8803ea43f980 path 2 ep1in 93120000 cc 9 --> status -121

So, new mobo and $120 later, same freakin error.  All this, still in the
same hole.  Now ain't that something?  < Dale is going to the shop and
getting his mini sledge >

Dale

:-)  :-)

P. S. I got a email off list that explained this IOMMU thingy.  Water is
a little clearer now.  lol

-- 
I am only responsible for what I said ... Not for what you understood or
how you interpreted my words!


--------------080207030005030401010303
Content-Type: text/html; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit

<html>
  <head>
    <meta content="text/html; charset=ISO-8859-1"
      http-equiv="Content-Type">
  </head>
  <body bgcolor="#FFFFFF" text="#000000">
    Neil Bothwick wrote:<br>
    <span style="white-space: pre;">&gt; On Mon, 21 Oct 2013 18:57:21
      -0500, Dale wrote:<br>
      &gt;<br>
      &gt;&gt;&gt; press Tab at the boot menu to edit isolinux options.
      But use one of<br>
      &gt;&gt;&gt; the specifically 64 bit menu items, not the generic
      one that tries to<br>
      &gt;&gt;&gt; determine your CPU type on the fly.<br>
      &gt;&gt;<br>
      &gt;&gt; Thanks.&nbsp; I thought there was a way to edit it but I was
      going to have to<br>
      &gt;&gt; just look and see if I could figure it out.&nbsp; This helps.&nbsp;
      It gives me<br>
      &gt;&gt; hope that it is doable too.&nbsp; ;-) <br>
      &gt;&gt;<br>
      &gt;&gt; I wonder, if I try to boot the 32 bit version if it would
      work? <br>
      &gt;&gt; According to some of the things I read, it affects the 64
      bit stuff but<br>
      &gt;&gt; not 32 bit stuff.&nbsp; Hmmmmm.&nbsp; Interesting.&nbsp; ^-^<br>
      &gt;<br>
      &gt; That's a good idea. Both use the same userspace so the only
      difference is<br>
      &gt; in the kernels, and I doubt there are many differences
      between them<br>
      &gt; except for the target architecture, so it old be a good test.
      You could<br>
      &gt; also try the two versions of the alt kernel.<br>
      &gt;<br>
      &gt;</span><br>
    <br>
    Every once in a while, my brain actually comes up with something.&nbsp;
    ROFL <br>
    <br>
    Want to hear something equally funny?&nbsp; I started the UPS service
    that started this whole mess to see if it works.&nbsp; This is from
    messages:<br>
    <br>
    Oct 22 02:47:50 localhost kernel: [51255.888492] ohci_hcd
    0000:00:12.0: urb ffff8803ea43f980 path 2 ep1in 93120000 cc 9 --&gt;
    status -121<br>
    Oct 22 02:47:52 localhost kernel: [51257.891409] ohci_hcd
    0000:00:12.0: urb ffff8803ea43f980 path 2 ep1in 92120000 cc 9 --&gt;
    status -121<br>
    Oct 22 02:47:54 localhost kernel: [51259.902338] ohci_hcd
    0000:00:12.0: urb ffff8803ea43f980 path 2 ep1in 93120000 cc 9 --&gt;
    status -121<br>
    Oct 22 02:47:56 localhost kernel: [51261.905256] ohci_hcd
    0000:00:12.0: urb ffff8803ea43f980 path 2 ep1in 92120000 cc 9 --&gt;
    status -121<br>
    Oct 22 02:47:58 localhost kernel: [51263.916194] ohci_hcd
    0000:00:12.0: urb ffff8803ea43f980 path 2 ep1in 93120000 cc 9 --&gt;
    status -121<br>
    Oct 22 02:48:00 localhost kernel: [51265.919112] ohci_hcd
    0000:00:12.0: urb ffff8803ea43f980 path 2 ep1in 92120000 cc 9 --&gt;
    status -121<br>
    Oct 22 02:48:02 localhost kernel: [51267.930020] ohci_hcd
    0000:00:12.0: urb ffff8803ea43f980 path 2 ep1in 93120000 cc 9 --&gt;
    status -121<br>
    Oct 22 02:48:04 localhost kernel: [51269.932920] ohci_hcd
    0000:00:12.0: urb ffff8803ea43f980 path 2 ep1in 92120000 cc 9 --&gt;
    status -121<br>
    Oct 22 02:48:06 localhost kernel: [51271.943841] ohci_hcd
    0000:00:12.0: urb ffff8803ea43f980 path 2 ep1in 93120000 cc 9 --&gt;
    status -121<br>
    Oct 22 02:48:08 localhost kernel: [51273.946758] ohci_hcd
    0000:00:12.0: urb ffff8803ea43f980 path 2 ep1in 92120000 cc 9 --&gt;
    status -121<br>
    Oct 22 02:48:10 localhost kernel: [51275.949676] ohci_hcd
    0000:00:12.0: urb ffff8803ea43f980 path 2 ep1in 93120000 cc 9 --&gt;
    status -121<br>
    Oct 22 02:48:12 localhost kernel: [51277.960606] ohci_hcd
    0000:00:12.0: urb ffff8803ea43f980 path 2 ep1in 92120000 cc 9 --&gt;
    status -121<br>
    Oct 22 02:48:14 localhost kernel: [51279.963523] ohci_hcd
    0000:00:12.0: urb ffff8803ea43f980 path 2 ep1in 93120000 cc 9 --&gt;
    status -121<br>
    Oct 22 02:48:16 localhost kernel: [51281.974454] ohci_hcd
    0000:00:12.0: urb ffff8803ea43f980 path 2 ep1in 92120000 cc 9 --&gt;
    status -121<br>
    Oct 22 02:48:18 localhost kernel: [51283.977370] ohci_hcd
    0000:00:12.0: urb ffff8803ea43f980 path 2 ep1in 93120000 cc 9 --&gt;
    status -121<br>
    Oct 22 02:48:20 localhost kernel: [51285.980286] ohci_hcd
    0000:00:12.0: urb ffff8803ea43f980 path 2 ep1in 92120000 cc 9 --&gt;
    status -121<br>
    Oct 22 02:48:22 localhost kernel: [51287.991218] ohci_hcd
    0000:00:12.0: urb ffff8803ea43f980 path 2 ep1in 93120000 cc 9 --&gt;
    status -121<br>
    <br>
    So, new mobo and $120 later, same freakin error.&nbsp; All this, still in
    the same hole.&nbsp; Now ain't that something?&nbsp; &lt; Dale is going to the
    shop and getting his mini sledge &gt;<br>
    <br>
    Dale<br>
    <br>
    :-)&nbsp; :-) <br>
    <br>
    P. S. I got a email off list that explained this IOMMU thingy.&nbsp;
    Water is a little clearer now.&nbsp; lol<br>
    <br>
    -- <br>
    I am only responsible for what I said ... Not for what you
    understood or how you interpreted my words!<br>
    <br>
  </body>
</html>

--------------080207030005030401010303--