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!