[gentoo-user] New mobo change

[gentoo-user] New mobo change

[Dale]

Howdy,

I ordered the new mobo as much as I needed to wait.  The mobo is the
same brand but a different chipset and a couple other things are
different.  I have already built a kernel for those changes.  I plan to
put everything on the old mobo on the new mobo.  That includes the CPU. 
I'm pretty sure this will not be needed but want to ask to be sure.  Do
I need to do a emerge -e world or should it "just work" like it is? 
Since the CPU is going to be the exact same CPU, I'm thinking it is not
needed.  I do have march=native set in make.conf. 

Thoughts?  Thanks.

Dale

:-)  :-) 

P. S.  I think this is the most I have ever spent on a mobo.  $120.00
with shipping.

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

Re: [gentoo-user] New mobo change

[Pandu Poluan]

[-- Attachment #1: Type: text/plain, Size: 1016 bytes --]

On Oct 15, 2013 10:51 AM, "Dale" <rdalek1967@gmail.com> wrote:
>
> Howdy,
>
> I ordered the new mobo as much as I needed to wait.  The mobo is the
> same brand but a different chipset and a couple other things are
> different.  I have already built a kernel for those changes.  I plan to
> put everything on the old mobo on the new mobo.  That includes the CPU.
> I'm pretty sure this will not be needed but want to ask to be sure.  Do
> I need to do a emerge -e world or should it "just work" like it is?
> Since the CPU is going to be the exact same CPU, I'm thinking it is not
> needed.  I do have march=native set in make.conf.
>
> Thoughts?  Thanks.
>

Personally, I think all you need to do is to ensure that the kernel has all
the drivers it needs to speak to the new mobo. Other members of the @world
set relies on the drivers in the kernel.

But I don't use any GUI or audio; if you're using a GUI and/or audio, you
might also have to re-emerge the relevant bits.

BSTS: just re-emerge @world :-)

Rgds,
--

[-- Attachment #2: Type: text/html, Size: 1322 bytes --]

Re: [gentoo-user] New mobo change

[Dale]

[-- Attachment #1: Type: text/plain, Size: 1687 bytes --]

Pandu Poluan wrote:
>
>
> On Oct 15, 2013 10:51 AM, "Dale" <rdalek1967@gmail.com
> <mailto:rdalek1967@gmail.com>> wrote:
> >
> > Howdy,
> >
> > I ordered the new mobo as much as I needed to wait.  The mobo is the
> > same brand but a different chipset and a couple other things are
> > different.  I have already built a kernel for those changes.  I plan to
> > put everything on the old mobo on the new mobo.  That includes the CPU.
> > I'm pretty sure this will not be needed but want to ask to be sure.  Do
> > I need to do a emerge -e world or should it "just work" like it is?
> > Since the CPU is going to be the exact same CPU, I'm thinking it is not
> > needed.  I do have march=native set in make.conf.
> >
> > Thoughts?  Thanks.
> >
>
> Personally, I think all you need to do is to ensure that the kernel
> has all the drivers it needs to speak to the new mobo. Other members
> of the @world set relies on the drivers in the kernel.
>
> But I don't use any GUI or audio; if you're using a GUI and/or audio,
> you might also have to re-emerge the relevant bits.
>
> BSTS: just re-emerge @world :-)
>
> Rgds,
> --
>

It uses the same audio chip so that should be OK but that is something
that I hadn't thought of tho.  I have a seperate video card which will
be moving over as well.  So that *should* work.  We hope.

I'm hoping this will be as painless as I hope it will be.  I just got to
remember how to hook the drivers up.  Especially the first one.  I
certainly want sda to be correct.  ;-) 

Thanks.  You thought of something I hadn't thought of.

Dale

:-)  :-)

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


[-- Attachment #2: Type: text/html, Size: 2653 bytes --]

Re: [gentoo-user] New mobo change

[Bruce Hill]

On Tue, Oct 15, 2013 at 02:49:54AM -0500, Dale wrote:
> Pandu Poluan wrote:
> >
> > Personally, I think all you need to do is to ensure that the kernel
> > has all the drivers it needs to speak to the new mobo. Other members
> > of the @world set relies on the drivers in the kernel.
> >
> > But I don't use any GUI or audio; if you're using a GUI and/or audio,
> > you might also have to re-emerge the relevant bits.
> >
> > BSTS: just re-emerge @world :-)
> >
> 
> It uses the same audio chip so that should be OK but that is something
> that I hadn't thought of tho.  I have a seperate video card which will
> be moving over as well.  So that *should* work.  We hope.
> 
> I'm hoping this will be as painless as I hope it will be.  I just got to
> remember how to hook the drivers up.  Especially the first one.  I
> certainly want sda to be correct.  ;-) 
> 
> Thanks.  You thought of something I hadn't thought of.
> 
> Dale

Run "blkid" on your present mobo, and you will see where your filesystem(s)
are located in regards to /dev/sd{a,b,c,d}.

When you plug your SATA drive(s) to your new mobo, look for labels on the mobo
to indicate SATA{1,2,3,4,5,6} or whatever. Generally they are going to use sda
on 1, sdb on 2, etc. What can throw that off is the ATAPI drive (DVD/CD). I'd
put it on the highest SATA#, at least for that first boot.

Also look at your /var/log/dmesg output. NB: "less /var/log/dmesg" is NOT the
same as "dmesg". Do the former and it will show you only that part from boot
to Linux login (or whatever).

As previously stated, be sure to have all the drivers you need built into your
new kernel. You may or may not be able to ascertain that w/out the board in
your possession. You can look it up by make/model on
http://kmuto.jp/debian/hcl/ but they are using an old kernel, therefore,
caveat emptor. One way you can check that is to boot with SystemRescueCd
first, select their kernel version closest to the one you'll be using, and run
"lspci -k" from it. If you don't have something you need in your kernel, go
ahead and chroot into the new system.

I've moved stuff around like this...sold the wife's computer sans hard drive a
few weeks ago, and it booted fine. So long as you have the new board's / fs
and it's controller built into the new kernel, you'll get into the system.
From there you can "make nconfig" on the running kernel and change/add
whatever you missed.

Don't forget that grub (if you use it for bootloader, not just fishing), has
an editable line when you boot up. So if /dev/sda1 is not valid, edit it and
try booting with /dev/sd{b,c,d}1 or whatever until you get it. Then once
you're into the system, you can change it.

Trivial, Homie! Call if you need help...you have my number. :-)
-- 
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

[gentoo-user] Re: New mobo change

[Dale]

Dale wrote:
> Howdy,
>
> I ordered the new mobo as much as I needed to wait.  The mobo is the
> same brand but a different chipset and a couple other things are
> different.  I have already built a kernel for those changes.  I plan to
> put everything on the old mobo on the new mobo.  That includes the CPU. 
> I'm pretty sure this will not be needed but want to ask to be sure.  Do
> I need to do a emerge -e world or should it "just work" like it is? 
> Since the CPU is going to be the exact same CPU, I'm thinking it is not
> needed.  I do have march=native set in make.conf. 
>
> Thoughts?  Thanks.
>
> Dale
>
> :-)  :-) 
>
> P. S.  I think this is the most I have ever spent on a mobo.  $120.00
> with shipping.
>


Well, this is interesting.  I swapped out the mobo.  First, it has the
UEFI BIOS thing.  That was interesting for sure.  I'm not complaining
but not used to it and wasn't expecting it either.  Second, it works
except for the third part.  Third thing is, no mouse worky.  It works in
the BIOS but not in the OS.  I have gpm set to start and it doesn't work
in a console or a GUI.  I tried everything I can think of, no mouse.  I
had to swap again.  I'm back to my old mobo.  Here is the kicker.  I
plugged the USB mouse into the old mobo, it works just fine.  It works
in KDE, console etc.  It just works.  The only kernel change I made was
for the chipset on the mobo.  I left the USB stuff alone.  

Instead of me posting a lot of worthless stuff, what do y'all need me to
post?  Keep in mind, I'm on my old mobo and it works on here.  I got the
kernel config tho.  It's a start, I hope?   I followed this wiki howto.

http://wiki.gentoo.org/wiki/USB/HOWTO

Thoughts?  What do you need to figure this out?

Dale

:-)  :-)

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

[gentoo-user] Re: New mobo change

[walt]

On 10/17/2013 02:40 PM, Dale wrote:

> Third thing is, no mouse worky.  It works in
> the BIOS but not in the OS.

Dale, I don't understand what you mean by "works in the BIOS".
Could you give us a few more details?

Re: [gentoo-user] Re: New mobo change

[Bruce Hill]

On Thu, Oct 17, 2013 at 04:57:46PM -0700, walt wrote:
> 
> > Third thing is, no mouse worky.  It works in
> > the BIOS but not in the OS.
> 
> Dale, I don't understand what you mean by "works in the BIOS".
> Could you give us a few more details?

He means the mouse works when he boots and has to select something with the
mouse, such as Esc or F12 of Delete to get into the BIOS. But once his Gentoo
system loads, it doesn't.
-- 
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

Re: [gentoo-user] Re: New mobo change

[Dale]

Bruce Hill wrote:
> On Thu, Oct 17, 2013 at 04:57:46PM -0700, walt wrote:
>>> Third thing is, no mouse worky.  It works in
>>> the BIOS but not in the OS.
>> Dale, I don't understand what you mean by "works in the BIOS".
>> Could you give us a few more details?
> He means the mouse works when he boots and has to select something with the
> mouse, such as Esc or F12 of Delete to get into the BIOS. But once his Gentoo
> system loads, it doesn't.

Correct.  This BIOS isn't like the older BIOS where you use arrow keys,
or only use the arrow keys.  In this new BIOS, you can use a mouse to
point and click.  Also, it moves very very slowly.  It feels like I need
the mouse on the hood of a truck.  You have to move the mouse a long
ways to get a smaller amount of movement on the screen.  I just used the
arrow keys tho.  ;-)

Dale

:-)  :-) 

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

Re: [gentoo-user] Re: New mobo change

[Bruce Hill]

On Thu, Oct 17, 2013 at 04:40:52PM -0500, Dale wrote:
> 
> Well, this is interesting.  I swapped out the mobo.  First, it has the
> UEFI BIOS thing.  That was interesting for sure.  I'm not complaining
> but not used to it and wasn't expecting it either.  Second, it works
> except for the third part.  Third thing is, no mouse worky.  It works in
> the BIOS but not in the OS.  I have gpm set to start and it doesn't work
> in a console or a GUI.  I tried everything I can think of, no mouse.  I
> had to swap again.  I'm back to my old mobo.  Here is the kicker.  I
> plugged the USB mouse into the old mobo, it works just fine.  It works
> in KDE, console etc.  It just works.  The only kernel change I made was
> for the chipset on the mobo.  I left the USB stuff alone.  
> 
> Instead of me posting a lot of worthless stuff, what do y'all need me to
> post?  Keep in mind, I'm on my old mobo and it works on here.  I got the
> kernel config tho.  It's a start, I hope?   I followed this wiki howto.
> 
> http://wiki.gentoo.org/wiki/USB/HOWTO
> 
> Thoughts?  What do you need to figure this out?
> 
> Dale

Obliviously something simple, but why don't you throw your BB gun in the truck
and come over so we can sight in the .44 magnum?

Put all the stuff on the new mobo, boot with SystemRescueCD, see that the
mouse works, take 2 aspirins, and let's go from there.
-- 
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

Re: [gentoo-user] Re: New mobo change

[Dale]

Bruce Hill wrote:
> On Thu, Oct 17, 2013 at 04:40:52PM -0500, Dale wrote:
>> Well, this is interesting.  I swapped out the mobo.  First, it has the
>> UEFI BIOS thing.  That was interesting for sure.  I'm not complaining
>> but not used to it and wasn't expecting it either.  Second, it works
>> except for the third part.  Third thing is, no mouse worky.  It works in
>> the BIOS but not in the OS.  I have gpm set to start and it doesn't work
>> in a console or a GUI.  I tried everything I can think of, no mouse.  I
>> had to swap again.  I'm back to my old mobo.  Here is the kicker.  I
>> plugged the USB mouse into the old mobo, it works just fine.  It works
>> in KDE, console etc.  It just works.  The only kernel change I made was
>> for the chipset on the mobo.  I left the USB stuff alone.  
>>
>> Instead of me posting a lot of worthless stuff, what do y'all need me to
>> post?  Keep in mind, I'm on my old mobo and it works on here.  I got the
>> kernel config tho.  It's a start, I hope?   I followed this wiki howto.
>>
>> http://wiki.gentoo.org/wiki/USB/HOWTO
>>
>> Thoughts?  What do you need to figure this out?
>>
>> Dale
> Obliviously something simple, but why don't you throw your BB gun in the truck
> and come over so we can sight in the .44 magnum?
>
> Put all the stuff on the new mobo, boot with SystemRescueCD, see that the
> mouse works, take 2 aspirins, and let's go from there.

That was my plan B, Sysrescue.  It wouldn't boot either.  It gets to the
point where it is trying to find the USB stick, then errors out because
it can't find it which is odd since it is plugged into a USB port and
the mousey don't work from there either.  Thing is, it works just fine
with the old mobo.  I actually tested it, mounted some stuff and
everything.  Works fine on old mobo, errors out on the new one.  I also
switched back to the legacy and desabled the UEFI stuff.  It still
didn't work.  It does try to boot from it tho so it does see the USB
stick at first.  It just can't see it later on.  Hmmmm.

Dale

:-)  :-) 

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

Re: [gentoo-user] Re: New mobo change

[J. Roeleveld]

On Fri, October 18, 2013 05:33, Dale wrote:
> Bruce Hill wrote:
>> On Thu, Oct 17, 2013 at 04:40:52PM -0500, Dale wrote:
>>> Well, this is interesting.  I swapped out the mobo.  First, it has the
>>> UEFI BIOS thing.  That was interesting for sure.  I'm not complaining
>>> but not used to it and wasn't expecting it either.  Second, it works
>>> except for the third part.  Third thing is, no mouse worky.  It works
>>> in
>>> the BIOS but not in the OS.  I have gpm set to start and it doesn't
>>> work
>>> in a console or a GUI.  I tried everything I can think of, no mouse.  I
>>> had to swap again.  I'm back to my old mobo.  Here is the kicker.  I
>>> plugged the USB mouse into the old mobo, it works just fine.  It works
>>> in KDE, console etc.  It just works.  The only kernel change I made was
>>> for the chipset on the mobo.  I left the USB stuff alone.
>>>
>>> Instead of me posting a lot of worthless stuff, what do y'all need me
>>> to
>>> post?  Keep in mind, I'm on my old mobo and it works on here.  I got
>>> the
>>> kernel config tho.  It's a start, I hope?   I followed this wiki howto.
>>>
>>> http://wiki.gentoo.org/wiki/USB/HOWTO
>>>
>>> Thoughts?  What do you need to figure this out?
>>>
>>> Dale
>> Obliviously something simple, but why don't you throw your BB gun in the
>> truck
>> and come over so we can sight in the .44 magnum?
>>
>> Put all the stuff on the new mobo, boot with SystemRescueCD, see that
>> the
>> mouse works, take 2 aspirins, and let's go from there.
>
> That was my plan B, Sysrescue.  It wouldn't boot either.  It gets to the
> point where it is trying to find the USB stick, then errors out because
> it can't find it which is odd since it is plugged into a USB port and
> the mousey don't work from there either.  Thing is, it works just fine
> with the old mobo.  I actually tested it, mounted some stuff and
> everything.  Works fine on old mobo, errors out on the new one.  I also
> switched back to the legacy and desabled the UEFI stuff.  It still
> didn't work.  It does try to boot from it tho so it does see the USB
> stick at first.  It just can't see it later on.  Hmmmm.

Is USB-support ENABLED in the BIOS-settings?

Current (From last 5+ years?) BIOSs (and especially UEFI ones) should be
able to boot Sysrescue from USB.

If it can't, I would suspect USB being disabled, or the USB ports on the
mainboard being broken.

It might also be a legacy support setting that needs enabling/disabling?

--
Joost

Re: [gentoo-user] Re: New mobo change

[Pandu Poluan]

On Fri, Oct 18, 2013 at 10:52 PM, J. Roeleveld <joost@antarean.org> wrote:
> On Fri, October 18, 2013 05:33, Dale wrote:
>> Bruce Hill wrote:
>>> On Thu, Oct 17, 2013 at 04:40:52PM -0500, Dale wrote:
>>>> Well, this is interesting.  I swapped out the mobo.  First, it has the
>>>> UEFI BIOS thing.  That was interesting for sure.  I'm not complaining
>>>> but not used to it and wasn't expecting it either.  Second, it works
>>>> except for the third part.  Third thing is, no mouse worky.  It works
>>>> in
>>>> the BIOS but not in the OS.  I have gpm set to start and it doesn't
>>>> work
>>>> in a console or a GUI.  I tried everything I can think of, no mouse.  I
>>>> had to swap again.  I'm back to my old mobo.  Here is the kicker.  I
>>>> plugged the USB mouse into the old mobo, it works just fine.  It works
>>>> in KDE, console etc.  It just works.  The only kernel change I made was
>>>> for the chipset on the mobo.  I left the USB stuff alone.
>>>>
>>>> Instead of me posting a lot of worthless stuff, what do y'all need me
>>>> to
>>>> post?  Keep in mind, I'm on my old mobo and it works on here.  I got
>>>> the
>>>> kernel config tho.  It's a start, I hope?   I followed this wiki howto.
>>>>
>>>> http://wiki.gentoo.org/wiki/USB/HOWTO
>>>>
>>>> Thoughts?  What do you need to figure this out?
>>>>
>>>> Dale
>>> Obliviously something simple, but why don't you throw your BB gun in the
>>> truck
>>> and come over so we can sight in the .44 magnum?
>>>
>>> Put all the stuff on the new mobo, boot with SystemRescueCD, see that
>>> the
>>> mouse works, take 2 aspirins, and let's go from there.
>>
>> That was my plan B, Sysrescue.  It wouldn't boot either.  It gets to the
>> point where it is trying to find the USB stick, then errors out because
>> it can't find it which is odd since it is plugged into a USB port and
>> the mousey don't work from there either.  Thing is, it works just fine
>> with the old mobo.  I actually tested it, mounted some stuff and
>> everything.  Works fine on old mobo, errors out on the new one.  I also
>> switched back to the legacy and desabled the UEFI stuff.  It still
>> didn't work.  It does try to boot from it tho so it does see the USB
>> stick at first.  It just can't see it later on.  Hmmmm.
>
> Is USB-support ENABLED in the BIOS-settings?
>

I suspect this.

Since the UEFI BIOS (or whatever it's supposed to be called) is
mouse-driven-able, the USB is turned on _while_in_the_UEFI_BIOS_.

Outside of the UEFI BIOS, the USB might be enabled/disabled based on
the settings inside the UEFI BIOS.


Rgds,
-- 
FdS Pandu E Poluan
~ IT Optimizer ~

 • LOPSA Member #15248
 • Blog : http://pepoluan.tumblr.com
 • Linked-In : http://id.linkedin.com/in/pepoluan

Re: [gentoo-user] Re: New mobo change

[Walter Dnes]

On Thu, Oct 17, 2013 at 04:40:52PM -0500, Dale wrote
> 
> Well, this is interesting.  I swapped out the mobo.  First, it has the
> UEFI BIOS thing.  That was interesting for sure.  I'm not complaining
> but not used to it and wasn't expecting it either.  Second, it works
> except for the third part.  Third thing is, no mouse worky.  It works in
> the BIOS but not in the OS.  I have gpm set to start and it doesn't work
> in a console or a GUI.  I tried everything I can think of, no mouse.  I
> had to swap again.  I'm back to my old mobo.  Here is the kicker.  I
> plugged the USB mouse into the old mobo, it works just fine.  It works
> in KDE, console etc.  It just works.  The only kernel change I made was
> for the chipset on the mobo.  I left the USB stuff alone.

  I've run into this in the past.  The USB 2.0 drivers are *SUPPOSED* to
provide support for lowspeed USB 1.X devices, like mice and keyboards.
But it doesn't always work that way.  There is direct USB 1.X driver
support in the kernel.  In "make menuconfig", got to...

Device Drivers  --->
[*] USB support  --->
< >     OHCI HCD support
< >     UHCI HCD (most Intel and VIA) support

  I don't see any mention in your message whether the motherboard cpu is
AMD or Intel.  Generally, build UHCI for Intel+VIA, OHCI for AMD.  Try
it out and see what happens.

-- 
Walter Dnes <waltdnes@waltdnes.org>
I don't run "desktop environments"; I run useful applications

Re: [gentoo-user] Re: New mobo change

[Dale]

Walter Dnes wrote:
> On Thu, Oct 17, 2013 at 04:40:52PM -0500, Dale wrote
>> Well, this is interesting.  I swapped out the mobo.  First, it has the
>> UEFI BIOS thing.  That was interesting for sure.  I'm not complaining
>> but not used to it and wasn't expecting it either.  Second, it works
>> except for the third part.  Third thing is, no mouse worky.  It works in
>> the BIOS but not in the OS.  I have gpm set to start and it doesn't work
>> in a console or a GUI.  I tried everything I can think of, no mouse.  I
>> had to swap again.  I'm back to my old mobo.  Here is the kicker.  I
>> plugged the USB mouse into the old mobo, it works just fine.  It works
>> in KDE, console etc.  It just works.  The only kernel change I made was
>> for the chipset on the mobo.  I left the USB stuff alone.
>   I've run into this in the past.  The USB 2.0 drivers are *SUPPOSED* to
> provide support for lowspeed USB 1.X devices, like mice and keyboards.
> But it doesn't always work that way.  There is direct USB 1.X driver
> support in the kernel.  In "make menuconfig", got to...
>
> Device Drivers  --->
> [*] USB support  --->
> < >     OHCI HCD support
> < >     UHCI HCD (most Intel and VIA) support
>
>   I don't see any mention in your message whether the motherboard cpu is
> AMD or Intel.  Generally, build UHCI for Intel+VIA, OHCI for AMD.  Try
> it out and see what happens.
>


Mine is AMD based.  I have this right now but tried every other version
I could find too.

<*>   xHCI HCD (USB 3.0) support
<*>   EHCI HCD (USB 2.0) support
<*>   OHCI HCD support
[*]     Generic OHCI driver for a platform device
<*>   Generic EHCI driver for a platform device
<*>   UHCI HCD (most Intel and VIA) support

Under USB HID support, I have this enabled:

<*> USB HID transport layer
[*] PID device support
[*] /dev/hiddev raw HID device support


This may help:

root@fireball /usr/src/linux # cat .config | grep -i hid | grep =y
CONFIG_HID=y
CONFIG_HIDRAW=y
CONFIG_UHID=y
CONFIG_HID_GENERIC=y
CONFIG_HID_A4TECH=y
CONFIG_HID_APPLE=y
CONFIG_HID_BELKIN=y
CONFIG_HID_CHERRY=y
CONFIG_HID_CHICONY=y
CONFIG_HID_CYPRESS=y
CONFIG_HID_EZKEY=y
CONFIG_HID_KYE=y
CONFIG_HID_GYRATION=y
CONFIG_HID_KENSINGTON=y
CONFIG_HID_LOGITECH=y
CONFIG_HID_MICROSOFT=y
CONFIG_HID_MONTEREY=y
CONFIG_HID_NTRIG=y
CONFIG_HID_PANTHERLORD=y
CONFIG_HID_PETALYNX=y
CONFIG_HID_SAMSUNG=y
CONFIG_HID_SONY=y
CONFIG_HID_SUNPLUS=y
CONFIG_HID_TOPSEED=y
CONFIG_USB_HID=y
CONFIG_HID_PID=y
CONFIG_USB_HIDDEV=y
root@fireball /usr/src/linux #

Right before I swapped back, I tried them all.  ;-)  Here is some more info:

root@fireball /usr/src/linux # cat .config | grep -i hci
CONFIG_SATA_AHCI=y
# CONFIG_SATA_AHCI_PLATFORM is not set
# CONFIG_SATA_ACARD_AHCI is not set
# CONFIG_FIREWIRE_OHCI is not set
CONFIG_USB_ARCH_HAS_OHCI=y
CONFIG_USB_ARCH_HAS_EHCI=y
CONFIG_USB_ARCH_HAS_XHCI=y
CONFIG_USB_XHCI_HCD=y
# CONFIG_USB_XHCI_HCD_DEBUGGING is not set
CONFIG_USB_EHCI_HCD=y
CONFIG_USB_EHCI_ROOT_HUB_TT=y
CONFIG_USB_EHCI_TT_NEWSCHED=y
CONFIG_USB_EHCI_PCI=y
CONFIG_USB_OHCI_HCD=y
CONFIG_USB_OHCI_HCD_PLATFORM=y
CONFIG_USB_EHCI_HCD_PLATFORM=y
# CONFIG_USB_OHCI_BIG_ENDIAN_DESC is not set
# CONFIG_USB_OHCI_BIG_ENDIAN_MMIO is not set
CONFIG_USB_OHCI_LITTLE_ENDIAN=y
CONFIG_USB_UHCI_HCD=y
CONFIG_PROVIDE_OHCI1394_DMA_INIT=y
root@fireball /usr/src/linux #


My thinking, there is some driver that is different from my old mobo to
this new mobo and I'm missing it or just missing something really
simple.  I went by the Debian HCL site but maybe something got changed. 
If I could boot the Sysrescue stick then I could likely figure it out
from that.  I'm going to update that stick before the next test. 

Keep in mind, for me to test anything, I have to swap mobos again. 
Naturally I don't want to do that any more times than I have to.  Each
times runs the risk of me messing up something.  :/

Thanks much to all.

Dale

:-)  :-)

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

Re: [gentoo-user] Re: New mobo change

[Volker Armin Hemmann]

Am 18.10.2013 05:54, schrieb Dale:
> Walter Dnes wrote:
>> On Thu, Oct 17, 2013 at 04:40:52PM -0500, Dale wrote
>>> Well, this is interesting.  I swapped out the mobo.  First, it has the
>>> UEFI BIOS thing.  That was interesting for sure.  I'm not complaining
>>> but not used to it and wasn't expecting it either.  Second, it works
>>> except for the third part.  Third thing is, no mouse worky.  It works in
>>> the BIOS but not in the OS.  I have gpm set to start and it doesn't work
>>> in a console or a GUI.  I tried everything I can think of, no mouse.  I
>>> had to swap again.  I'm back to my old mobo.  Here is the kicker.  I
>>> plugged the USB mouse into the old mobo, it works just fine.  It works
>>> in KDE, console etc.  It just works.  The only kernel change I made was
>>> for the chipset on the mobo.  I left the USB stuff alone.
>>   I've run into this in the past.  The USB 2.0 drivers are *SUPPOSED* to
>> provide support for lowspeed USB 1.X devices, like mice and keyboards.
>> But it doesn't always work that way.  There is direct USB 1.X driver
>> support in the kernel.  In "make menuconfig", got to...
>>
>> Device Drivers  --->
>> [*] USB support  --->
>> < >     OHCI HCD support
>> < >     UHCI HCD (most Intel and VIA) support
>>
>>   I don't see any mention in your message whether the motherboard cpu is
>> AMD or Intel.  Generally, build UHCI for Intel+VIA, OHCI for AMD.  Try
>> it out and see what happens.
>>
>
> Mine is AMD based.  I have this right now but tried every other version
> I could find too.
>
> <*>   xHCI HCD (USB 3.0) support
> <*>   EHCI HCD (USB 2.0) support
> <*>   OHCI HCD support
> [*]     Generic OHCI driver for a platform device

there you go. platform driver. Take that one out.
Make the rest modules.
Amd board? kill uhci while you are at it.

> <*>   Generic EHCI driver for a platform device
> <*>   UHCI HCD (most Intel and VIA) support
>
> Under USB HID support, I have this enabled:
>
> <*> USB HID transport layer
> [*] PID device support
> [*] /dev/hiddev raw HID device support
>
>
> This may help:
>
> root@fireball /usr/src/linux # cat .config | grep -i hid | grep =y
> CONFIG_HID=y
> CONFIG_HIDRAW=y
> CONFIG_UHID=y
> CONFIG_HID_GENERIC=y
> CONFIG_HID_A4TECH=y
> CONFIG_HID_APPLE=y
> CONFIG_HID_BELKIN=y
> CONFIG_HID_CHERRY=y
> CONFIG_HID_CHICONY=y
> CONFIG_HID_CYPRESS=y
> CONFIG_HID_EZKEY=y
> CONFIG_HID_KYE=y
> CONFIG_HID_GYRATION=y
> CONFIG_HID_KENSINGTON=y
> CONFIG_HID_LOGITECH=y
> CONFIG_HID_MICROSOFT=y
> CONFIG_HID_MONTEREY=y
> CONFIG_HID_NTRIG=y
> CONFIG_HID_PANTHERLORD=y
> CONFIG_HID_PETALYNX=y
> CONFIG_HID_SAMSUNG=y
> CONFIG_HID_SONY=y
> CONFIG_HID_SUNPLUS=y
> CONFIG_HID_TOPSEED=y
> CONFIG_USB_HID=y
> CONFIG_HID_PID=y
> CONFIG_USB_HIDDEV=y
> root@fireball /usr/src/linux #
>
> Right before I swapped back, I tried them all.  ;-)  Here is some more info:
>
> root@fireball /usr/src/linux # cat .config | grep -i hci
> CONFIG_SATA_AHCI=y
> # CONFIG_SATA_AHCI_PLATFORM is not set
> # CONFIG_SATA_ACARD_AHCI is not set
> # CONFIG_FIREWIRE_OHCI is not set
> CONFIG_USB_ARCH_HAS_OHCI=y
> CONFIG_USB_ARCH_HAS_EHCI=y
> CONFIG_USB_ARCH_HAS_XHCI=y
> CONFIG_USB_XHCI_HCD=y
> # CONFIG_USB_XHCI_HCD_DEBUGGING is not set
> CONFIG_USB_EHCI_HCD=y
> CONFIG_USB_EHCI_ROOT_HUB_TT=y
> CONFIG_USB_EHCI_TT_NEWSCHED=y
> CONFIG_USB_EHCI_PCI=y
> CONFIG_USB_OHCI_HCD=y
> CONFIG_USB_OHCI_HCD_PLATFORM=y
> CONFIG_USB_EHCI_HCD_PLATFORM=y
> # CONFIG_USB_OHCI_BIG_ENDIAN_DESC is not set
> # CONFIG_USB_OHCI_BIG_ENDIAN_MMIO is not set
> CONFIG_USB_OHCI_LITTLE_ENDIAN=y
> CONFIG_USB_UHCI_HCD=y
> CONFIG_PROVIDE_OHCI1394_DMA_INIT=y
> root@fireball /usr/src/linux #
>
>
> My thinking, there is some driver that is different from my old mobo to
> this new mobo and I'm missing it or just missing something really
> simple.  I went by the Debian HCL site but maybe something got changed. 
> If I could boot the Sysrescue stick then I could likely figure it out
> from that.  I'm going to update that stick before the next test. 
>
> Keep in mind, for me to test anything, I have to swap mobos again. 
> Naturally I don't want to do that any more times than I have to.  Each
> times runs the risk of me messing up something.  :/
>
> Thanks much to all.
>
> Dale
>
> :-)  :-)
>

Re: [gentoo-user] Re: New mobo change

[Dale]

Volker Armin Hemmann wrote:
> Am 18.10.2013 05:54, schrieb Dale:
>> Walter Dnes wrote:
>>> On Thu, Oct 17, 2013 at 04:40:52PM -0500, Dale wrote
>>>> Well, this is interesting.  I swapped out the mobo.  First, it has the
>>>> UEFI BIOS thing.  That was interesting for sure.  I'm not complaining
>>>> but not used to it and wasn't expecting it either.  Second, it works
>>>> except for the third part.  Third thing is, no mouse worky.  It works in
>>>> the BIOS but not in the OS.  I have gpm set to start and it doesn't work
>>>> in a console or a GUI.  I tried everything I can think of, no mouse.  I
>>>> had to swap again.  I'm back to my old mobo.  Here is the kicker.  I
>>>> plugged the USB mouse into the old mobo, it works just fine.  It works
>>>> in KDE, console etc.  It just works.  The only kernel change I made was
>>>> for the chipset on the mobo.  I left the USB stuff alone.
>>>   I've run into this in the past.  The USB 2.0 drivers are *SUPPOSED* to
>>> provide support for lowspeed USB 1.X devices, like mice and keyboards.
>>> But it doesn't always work that way.  There is direct USB 1.X driver
>>> support in the kernel.  In "make menuconfig", got to...
>>>
>>> Device Drivers  --->
>>> [*] USB support  --->
>>> < >     OHCI HCD support
>>> < >     UHCI HCD (most Intel and VIA) support
>>>
>>>   I don't see any mention in your message whether the motherboard cpu is
>>> AMD or Intel.  Generally, build UHCI for Intel+VIA, OHCI for AMD.  Try
>>> it out and see what happens.
>>>
>> Mine is AMD based.  I have this right now but tried every other version
>> I could find too.
>>
>> <*>   xHCI HCD (USB 3.0) support
>> <*>   EHCI HCD (USB 2.0) support
>> <*>   OHCI HCD support
>> [*]     Generic OHCI driver for a platform device
> there you go. platform driver. Take that one out.
> Make the rest modules.
> Amd board? kill uhci while you are at it.

Change made.  I plan to give this a shot again before to long.  I got a
few thigns to try out now.  I updated sysrecue and Knoppix.  I also put
them both on CD/DVD to just in case it is a USB issue.  At least I can
test some things and hopefully find one that works. 

Thanks for all the help.  I'll post back what happens.  If it doesn't
work next time or fails from sysrescue/Knoppix, I plan to RMA the board
for another one.  If it doesn't work with either of those, then I
suspect hardware issues again. 

Dale

:-)  :-) 

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

Re: [gentoo-user] Re: New mobo change

[Volker Armin Hemmann]

Am 20.10.2013 07:39, schrieb Dale:
> Volker Armin Hemmann wrote:
>> Am 18.10.2013 05:54, schrieb Dale:
>>> Walter Dnes wrote:
>>>> On Thu, Oct 17, 2013 at 04:40:52PM -0500, Dale wrote
>>>>> Well, this is interesting.  I swapped out the mobo.  First, it has the
>>>>> UEFI BIOS thing.  That was interesting for sure.  I'm not complaining
>>>>> but not used to it and wasn't expecting it either.  Second, it works
>>>>> except for the third part.  Third thing is, no mouse worky.  It works in
>>>>> the BIOS but not in the OS.  I have gpm set to start and it doesn't work
>>>>> in a console or a GUI.  I tried everything I can think of, no mouse.  I
>>>>> had to swap again.  I'm back to my old mobo.  Here is the kicker.  I
>>>>> plugged the USB mouse into the old mobo, it works just fine.  It works
>>>>> in KDE, console etc.  It just works.  The only kernel change I made was
>>>>> for the chipset on the mobo.  I left the USB stuff alone.
>>>>   I've run into this in the past.  The USB 2.0 drivers are *SUPPOSED* to
>>>> provide support for lowspeed USB 1.X devices, like mice and keyboards.
>>>> But it doesn't always work that way.  There is direct USB 1.X driver
>>>> support in the kernel.  In "make menuconfig", got to...
>>>>
>>>> Device Drivers  --->
>>>> [*] USB support  --->
>>>> < >     OHCI HCD support
>>>> < >     UHCI HCD (most Intel and VIA) support
>>>>
>>>>   I don't see any mention in your message whether the motherboard cpu is
>>>> AMD or Intel.  Generally, build UHCI for Intel+VIA, OHCI for AMD.  Try
>>>> it out and see what happens.
>>>>
>>> Mine is AMD based.  I have this right now but tried every other version
>>> I could find too.
>>>
>>> <*>   xHCI HCD (USB 3.0) support
>>> <*>   EHCI HCD (USB 2.0) support
>>> <*>   OHCI HCD support
>>> [*]     Generic OHCI driver for a platform device
>> there you go. platform driver. Take that one out.
>> Make the rest modules.
>> Amd board? kill uhci while you are at it.
> Change made.  I plan to give this a shot again before to long.  I got a
> few thigns to try out now.  I updated sysrecue and Knoppix.  I also put
> them both on CD/DVD to just in case it is a USB issue.  At least I can
> test some things and hopefully find one that works. 
>
> Thanks for all the help.  I'll post back what happens.  If it doesn't
> work next time or fails from sysrescue/Knoppix, I plan to RMA the board
> for another one.  If it doesn't work with either of those, then I
> suspect hardware issues again. 
no, the mouse works in bios - so it is not a hardware issue, but in
worst case a bios setting issue.

[gentoo-user] Re: New mobo change

[Dale]

Dale wrote:
> Howdy,
>
> I ordered the new mobo as much as I needed to wait.  The mobo is the
> same brand but a different chipset and a couple other things are
> different.  I have already built a kernel for those changes.  I plan to
> put everything on the old mobo on the new mobo.  That includes the CPU. 
> I'm pretty sure this will not be needed but want to ask to be sure.  Do
> I need to do a emerge -e world or should it "just work" like it is? 
> Since the CPU is going to be the exact same CPU, I'm thinking it is not
> needed.  I do have march=native set in make.conf. 
>
> Thoughts?  Thanks.
>
> Dale
>
> :-)  :-) 
>
> P. S.  I think this is the most I have ever spent on a mobo.  $120.00
> with shipping.
>


Here is another update.  I currently have the new mobo in the puter. 
The only port that works is the 3.0 ports.  None of the other ports
work.  I mean nothing.  When I plug my cell phone in, it doesn't even
get power much less see it.  When I plug the mouse in, the light doesn't
come on.  It's just plain dead.  While in the BIOS, the mouse works in
any USB port.  So, I got the USB 3 ports working but something is
killing the other ports.  Nothing I plug into the USB 1/2 ports works
outside of BIOS. 

I still think this is a kernel issue.  I just don't know which part.  I
have tried switching stuff on/off and such but nothing works.  I'm
thinking about putting my sledge hammer to work.  :/ 

What do I need to post so someone can compare this to something that
works?  I'll post the whole kernel config if needed/requested.  If you
just need certain parts, just let me know what to grep for. 

Thanks.  I'll be beating on it until I hear some more ideas from y'all. 

Dale

:-)  :-)

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

Re: [gentoo-user] Re: New mobo change

[Edward M]

On 10/20/2013 2:19 PM, Dale wrote:
> I still think this is a kernel issue.  I just don't know which part.  I
> have tried switching stuff on/off and such but nothing works.  I'm
> thinking about putting my sledge hammer to work.  :/


            Hello,


         Have you tried booting into a linux distro that offers a 
recent  live cd to see
         if that distro  can properly detect and load the needed 
drivers?  And If they work, then you can find out which drivers were 
loaded.

Re: [gentoo-user] Re: New mobo change

[Dale]

Edward M wrote:
> On 10/20/2013 2:19 PM, Dale wrote:
>> I still think this is a kernel issue.  I just don't know which part.  I
>> have tried switching stuff on/off and such but nothing works.  I'm
>> thinking about putting my sledge hammer to work.  :/
>
>
>            Hello,
>
>
>         Have you tried booting into a linux distro that offers a
> recent  live cd to see
>         if that distro  can properly detect and load the needed
> drivers?  And If they work, then you can find out which drivers were
> loaded.
>
>

I did once before and it failed to boot with a error.  I didn't write it
down.  I may try that later on tho.  I have since updated sysrescue. 
While it is not like I want it, the mouse does move when I poke it.  lol 

Thanks for the reminder tho.  I'll post results when I try it. 

Dale

:-)  :-) 

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

Re: [gentoo-user] Re: New mobo change

[William Kenworthy]

On 21/10/13 07:52, Dale wrote:
> Edward M wrote:
>> On 10/20/2013 2:19 PM, Dale wrote:
>>> I still think this is a kernel issue.  I just don't know which part.  I
>>> have tried switching stuff on/off and such but nothing works.  I'm
>>> thinking about putting my sledge hammer to work.  :/
>>
>>            Hello,
>>
>>
>>         Have you tried booting into a linux distro that offers a
>> recent  live cd to see
>>         if that distro  can properly detect and load the needed
>> drivers?  And If they work, then you can find out which drivers were
>> loaded.
>>
>>
> I did once before and it failed to boot with a error.  I didn't write it
> down.  I may try that later on tho.  I have since updated sysrescue. 
> While it is not like I want it, the mouse does move when I poke it.  lol 
>
> Thanks for the reminder tho.  I'll post results when I try it. 
>
> Dale
>
> :-)  :-) 
>

sysrescuecd is gentoo based ... try ubuntu or linuxmint to provide a
better "spread" of capabilities.

Have you checked the bios for usb parameters (i.e., defaults to off, or
wrong mode?) - whats on offer "in" the bios may not be the same as when
you exit it.

Billk

Re: [gentoo-user] Re: New mobo change

[Dale]

William Kenworthy wrote:
> On 21/10/13 07:52, Dale wrote:
>> Edward M wrote:
>>> On 10/20/2013 2:19 PM, Dale wrote:
>>>> I still think this is a kernel issue.  I just don't know which part.  I
>>>> have tried switching stuff on/off and such but nothing works.  I'm
>>>> thinking about putting my sledge hammer to work.  :/
>>>            Hello,
>>>
>>>
>>>         Have you tried booting into a linux distro that offers a
>>> recent  live cd to see
>>>         if that distro  can properly detect and load the needed
>>> drivers?  And If they work, then you can find out which drivers were
>>> loaded.
>>>
>>>
>> I did once before and it failed to boot with a error.  I didn't write it
>> down.  I may try that later on tho.  I have since updated sysrescue. 
>> While it is not like I want it, the mouse does move when I poke it.  lol 
>>
>> Thanks for the reminder tho.  I'll post results when I try it. 
>>
>> Dale
>>
>> :-)  :-) 
>>
> sysrescuecd is gentoo based ... try ubuntu or linuxmint to provide a
> better "spread" of capabilities.
>
> Have you checked the bios for usb parameters (i.e., defaults to off, or
> wrong mode?) - whats on offer "in" the bios may not be the same as when
> you exit it.
>
> Billk
>
>
>

I rebooted and the newest sysrescue still wouldn't boot up.  It says it
can't find /sysrcd.dat which I think is caused because it can't use the
USB port that the sysrescue stick is plugged into.  So, I booted Knoppix
instead from DVD.  Success.  I got a list of drivers from lspci and plan
to research them and see if I am missing something.  If not, I may just
start with a fresh config and see if that helps. 

At least the mobo is working tho.  That's a good thing.  It's a start at
least. 

Dale

:-)  :-)

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

Re: [gentoo-user] Re: New mobo change

[William Kenworthy]

On 21/10/13 11:09, Dale wrote:
> William Kenworthy wrote:
>> On 21/10/13 07:52, Dale wrote:
>>> Edward M wrote:
>>>> On 10/20/2013 2:19 PM, Dale wrote:
>>>>> I still think this is a kernel issue.  I just don't know which part.  I
>>>>> have tried switching stuff on/off and such but nothing works.  I'm
>>>>> thinking about putting my sledge hammer to work.  :/
>>>>            Hello,
>>>>
>>>>
>>>>         Have you tried booting into a linux distro that offers a
>>>> recent  live cd to see
>>>>         if that distro  can properly detect and load the needed
>>>> drivers?  And If they work, then you can find out which drivers were
>>>> loaded.
>>>>
>>>>
>>> I did once before and it failed to boot with a error.  I didn't write it
>>> down.  I may try that later on tho.  I have since updated sysrescue. 
>>> While it is not like I want it, the mouse does move when I poke it.  lol 
>>>
>>> Thanks for the reminder tho.  I'll post results when I try it. 
>>>
>>> Dale
>>>
>>> :-)  :-) 
>>>
>> sysrescuecd is gentoo based ... try ubuntu or linuxmint to provide a
>> better "spread" of capabilities.
>>
>> Have you checked the bios for usb parameters (i.e., defaults to off, or
>> wrong mode?) - whats on offer "in" the bios may not be the same as when
>> you exit it.
>>
>> Billk
>>
>>
>>
> I rebooted and the newest sysrescue still wouldn't boot up.  It says it
> can't find /sysrcd.dat which I think is caused because it can't use the
> USB port that the sysrescue stick is plugged into.  So, I booted Knoppix
> instead from DVD.  Success.  I got a list of drivers from lspci and plan
> to research them and see if I am missing something.  If not, I may just
> start with a fresh config and see if that helps. 
>
> At least the mobo is working tho.  That's a good thing.  It's a start at
> least. 
>
> Dale
>
> :-)  :-)
>

Ive found that with gentoo/sysrescuecd before - the other distros do a
better job of detection - I have a dell system here that wont work on
SRD for instance.  But after using ubuntu to find what was missing, its
running gentoo fine.

Billk

Re: [gentoo-user] Re: New mobo change

[Dale]

William Kenworthy wrote:
> On 21/10/13 11:09, Dale wrote:
>>
>> I rebooted and the newest sysrescue still wouldn't boot up.  It says it
>> can't find /sysrcd.dat which I think is caused because it can't use the
>> USB port that the sysrescue stick is plugged into.  So, I booted Knoppix
>> instead from DVD.  Success.  I got a list of drivers from lspci and plan
>> to research them and see if I am missing something.  If not, I may just
>> start with a fresh config and see if that helps. 
>>
>> At least the mobo is working tho.  That's a good thing.  It's a start at
>> least. 
>>
>> Dale
>>
>> :-)  :-)
>>
> Ive found that with gentoo/sysrescuecd before - the other distros do a
> better job of detection - I have a dell system here that wont work on
> SRD for instance.  But after using ubuntu to find what was missing, its
> running gentoo fine.
>
> Billk
>
>
>
>

Well, I have enabled everything I could find from the Knoppix test and
it still does not work.  I'm likely going to just try to config a kernel
from scratch later on.  That or go back to the one from my old mobo and
just change the chipset.  See if that works. 

Thanks for the help.  I'll post updates when I can.  I may be pretty
busy for a few days.  Could be a bit. 

Dale

:-)  :-) 

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

Re: [gentoo-user] Re: New mobo change

[Dale]

Dale wrote:
> William Kenworthy wrote:
>> On 21/10/13 11:09, Dale wrote:
>>> I rebooted and the newest sysrescue still wouldn't boot up.  It says it
>>> can't find /sysrcd.dat which I think is caused because it can't use the
>>> USB port that the sysrescue stick is plugged into.  So, I booted Knoppix
>>> instead from DVD.  Success.  I got a list of drivers from lspci and plan
>>> to research them and see if I am missing something.  If not, I may just
>>> start with a fresh config and see if that helps. 
>>>
>>> At least the mobo is working tho.  That's a good thing.  It's a start at
>>> least. 
>>>
>>> Dale
>>>
>>> :-)  :-)
>>>
>> Ive found that with gentoo/sysrescuecd before - the other distros do a
>> better job of detection - I have a dell system here that wont work on
>> SRD for instance.  But after using ubuntu to find what was missing, its
>> running gentoo fine.
>>
>> Billk
>>
>>
>>
>>
> Well, I have enabled everything I could find from the Knoppix test and
> it still does not work.  I'm likely going to just try to config a kernel
> from scratch later on.  That or go back to the one from my old mobo and
> just change the chipset.  See if that works. 
>
> Thanks for the help.  I'll post updates when I can.  I may be pretty
> busy for a few days.  Could be a bit. 
>
> Dale
>
> :-)  :-) 
>

Update.  I did some googling and found out that I have to add "
iommu=pt" to the kernel command line.  When I do that, it works fine. 
It seems that this mobo doesn't play well with 64 bit Linux.  Some even
said it appears to be a windoze only mobo.  So, my question is this.  I
just spent $120 on a mobo that it appears it doesn't work up to its full
value.  Should I swap this mobo for another board, brand to most likely,
and be done with it?  I like my last Gigabyte mobo but if this one isn't
going to support what I use, maybe I need to rethink this selection. 

What are the thoughts of some mobo gurus?   I bought it from newegg so
return shouldn't be to big of a issue if I get this started pretty
soon.  I'll check for BIOS updates but the posts I found said it didn't
help a bit.

Thoughts?

Dale

:-)  :-)

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

Re: [gentoo-user] Re: New mobo change

[J. Roeleveld]

[-- Attachment #1: Type: text/plain, Size: 2820 bytes --]

Dale <rdalek1967@gmail.com> wrote:
>Dale wrote:
>> William Kenworthy wrote:
>>> On 21/10/13 11:09, Dale wrote:
>>>> I rebooted and the newest sysrescue still wouldn't boot up.  It
>says it
>>>> can't find /sysrcd.dat which I think is caused because it can't use
>the
>>>> USB port that the sysrescue stick is plugged into.  So, I booted
>Knoppix
>>>> instead from DVD.  Success.  I got a list of drivers from lspci and
>plan
>>>> to research them and see if I am missing something.  If not, I may
>just
>>>> start with a fresh config and see if that helps. 
>>>>
>>>> At least the mobo is working tho.  That's a good thing.  It's a
>start at
>>>> least. 
>>>>
>>>> Dale
>>>>
>>>> :-)  :-)
>>>>
>>> Ive found that with gentoo/sysrescuecd before - the other distros do
>a
>>> better job of detection - I have a dell system here that wont work
>on
>>> SRD for instance.  But after using ubuntu to find what was missing,
>its
>>> running gentoo fine.
>>>
>>> Billk
>>>
>>>
>>>
>>>
>> Well, I have enabled everything I could find from the Knoppix test
>and
>> it still does not work.  I'm likely going to just try to config a
>kernel
>> from scratch later on.  That or go back to the one from my old mobo
>and
>> just change the chipset.  See if that works. 
>>
>> Thanks for the help.  I'll post updates when I can.  I may be pretty
>> busy for a few days.  Could be a bit. 
>>
>> Dale
>>
>> :-)  :-) 
>>
>
>Update.  I did some googling and found out that I have to add "
>iommu=pt" to the kernel command line.  When I do that, it works fine. 
>It seems that this mobo doesn't play well with 64 bit Linux.  Some even
>said it appears to be a windoze only mobo.  So, my question is this.  I
>just spent $120 on a mobo that it appears it doesn't work up to its
>full
>value.  Should I swap this mobo for another board, brand to most
>likely,
>and be done with it?  I like my last Gigabyte mobo but if this one
>isn't
>going to support what I use, maybe I need to rethink this selection. 
>
>What are the thoughts of some mobo gurus?   I bought it from newegg so
>return shouldn't be to big of a issue if I get this started pretty
>soon.  I'll check for BIOS updates but the posts I found said it didn't
>help a bit.
>
>Thoughts?
>
>Dale
>
>:-)  :-)
>
>-- 
>I am only responsible for what I said ... Not for what you understood
>or how you interpreted my words!

Of the general consensus is that it is a ms windows only board. Then I would return it.

I have had good experiences with ASUS and Tyan boards. The latter are more expensive, but Tyan does officially support Linux. (The Linux driver section is as easy to find as the ms windows driver section.)

--
Joost
-- 
Sent from my Android device with K-9 Mail. Please excuse my brevity.

[-- Attachment #2: Type: text/html, Size: 3412 bytes --]

Re: [gentoo-user] Re: New mobo change

[Dale]

[-- Attachment #1: Type: text/plain, Size: 1978 bytes --]

J. Roeleveld wrote:
> Dale <rdalek1967@gmail.com> wrote:
>
>     Dale wrote:
>
>
>     Update.  I did some googling and found out that I have to add "
>     iommu=pt" to the kernel command line.  When I do that, it works fine. 
>     It seems that this mobo doesn't play
>     well with 64 bit Linux.  Some even
>     said it appears to be a windoze only mobo.  So, my question is this.  I
>     just spent $120 on a mobo that it appears it doesn't work up to its full
>     value.  Should I swap this mobo for another board, brand to most likely,
>     and be done with it?  I like my last Gigabyte mobo but if this one isn't
>     going to support what I use, maybe I need to rethink this selection. 
>
>     What are the thoughts of some mobo gurus?   I bought it from newegg so
>     return shouldn't be to big of a issue if I get this started pretty
>     soon.  I'll check for BIOS updates but the posts I found said it didn't
>     help a bit.
>
>     Thoughts?
>
>     Dale
>
>     :-)  :-)
>
>
> Of the general consensus is that it is a ms windows only board. Then I
> would return it.
>
> I have had good experiences with ASUS and Tyan boards. The latter are
> more expensive, but Tyan does officially support Linux. (The Linux
> driver section is as easy to find as the ms windows driver section.)
>
> --
> Joost
> -- 
> Sent from my Android device with K-9 Mail. Please excuse my brevity. 

I have heard good things about both brands.  If I end up switching,
those two are certainly options I like.  I don't caare about the flashy
stuff, I just want solid performance with years of service.  Save all
the fancy/flashy stuff for those that like a light show.  I just want
one that works very well with Linux.  I could care less about windoze. 
None of my rigs will ever see windoze.  lol

Thanks for the opinion and recommendation as well. 

Dale

:-)  :-) 

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


[-- Attachment #2: Type: text/html, Size: 2792 bytes --]

Re: [gentoo-user] Re: New mobo change

[Edward M]

[-- Attachment #1: Type: text/plain, Size: 303 bytes --]

On 10/20/2013 9:27 PM, Dale wrote:
>   I did some googling and found out that I have to add "
> iommu=pt" to the kernel command line.  When I do that, it works fine.

      In the UEFI/BIOS menus;  does it have a "|IOMMU Controller" option 
and if
   it does, try enabling it and boot linux normally.
|

[-- Attachment #2: Type: text/html, Size: 714 bytes --]

Re: [gentoo-user] Re: New mobo change

[Dale]

[-- Attachment #1: Type: text/plain, Size: 2143 bytes --]

Edward M wrote:
> On 10/20/2013 9:27 PM, Dale wrote:
>>  I did some googling and found out that I have to add "
>> iommu=pt" to the kernel command line.  When I do that, it works fine. 
>  
>      In the UEFI/BIOS menus;  does it have a "|IOMMU Controller"
> option and if
>   it does, try enabling it and boot linux normally. 
> | 

That is what I had to do.  I also had to add the line to the kernel
command line to be able to boot.  It required both to get this working. 
It *seems* that I have to force something to work by adding the command
line option.  I have done that a few times in the past but to me, it
seems like some sort of hack.  I *hope* to have this mobo for many
years.  If it is going to be flakey, weird, odd or any other words that
some may use to describe ME, lol, I'd just rather switch to something
else now.  I picked Gigabyte because they seem to be rock solid.  It
seems this mobo is a exception to the rule.

While I like Gigabyte as a brand, if this is going to be something that
reduces the value of my purchase, I want to get something else.  I
assume that the iommu has something to do with IO, input/output.  If
using that option is going to slow something down or otherwise have a
negative impact on performance, time to switch. 

I still got some reading to do so this may change as I find out more but
based on what I have read so far, this mobo just doesn't like Linux. 
Anything that doesn't like Linux in this house, doesn't stay around
long.  As some may know, I am a Linux only person. 

Tyan is a mobo I have heard good things about.  I think someone gave me
a puter to repair once that had a ASUS mobo.  It seemed to be a nice
mobo.  Pity the guys house caught fire from the central heat tho.  I'm
open to ideas here. 

Basically, I want to make sure this is going to meet my expectations for
years to come.  If it won't, time to switch. 

Thanks to all for the help.  I figured I was missing something in the
kernel but wasn't expecting this, not from Gigabyte at least.

Dale

:-)  :-) 

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


[-- Attachment #2: Type: text/html, Size: 3173 bytes --]

Re: [gentoo-user] Re: New mobo change

[Daniel Frey]

On 10/21/2013 02:13 AM, Dale wrote:
> Tyan is a mobo I have heard good things about.  I think someone gave me
> a puter to repair once that had a ASUS mobo.  It seemed to be a nice
> mobo.  Pity the guys house caught fire from the central heat tho.  I'm
> open to ideas here. 
> 
> Basically, I want to make sure this is going to meet my expectations for
> years to come.  If it won't, time to switch. 
> 
> Thanks to all for the help.  I figured I was missing something in the
> kernel but wasn't expecting this, not from Gigabyte at least.
> 
> Dale
> 
> :-)  :-) 
> 
> -- 
> I am only responsible for what I said ... Not for what you understood or how you interpreted my words!
> 

I also like the Gigabyte and ASUS motherboards. I was sticking with
Intel desktop and workstation boards but now they discontinued them back
to what I knew...

I've only got one recommendation for ASUS: Stay far away from their
gaming boards. They're unstable as hell.

I also have an ASRock motherboard (budget board) for one of my computers
around here, it's not a bad board either.

The only really bad experience I had was with ECS. Garbage boards.

Dan

Re: [gentoo-user] Re: New mobo change

[Dale]

Daniel Frey wrote:
> On 10/21/2013 02:13 AM, Dale wrote:
>> Tyan is a mobo I have heard good things about.  I think someone gave me
>> a puter to repair once that had a ASUS mobo.  It seemed to be a nice
>> mobo.  Pity the guys house caught fire from the central heat tho.  I'm
>> open to ideas here. 
>>
>> Basically, I want to make sure this is going to meet my expectations for
>> years to come.  If it won't, time to switch. 
>>
>> Thanks to all for the help.  I figured I was missing something in the
>> kernel but wasn't expecting this, not from Gigabyte at least.
>>
>> Dale
>>
>> :-)  :-) 
>>
>> -- 
>> I am only responsible for what I said ... Not for what you understood or how you interpreted my words!
>>
> I also like the Gigabyte and ASUS motherboards. I was sticking with
> Intel desktop and workstation boards but now they discontinued them back
> to what I knew...

I'm a AMD guy because of cost but also like Gigabyte and ASUS mobos.  I
wish Abit was still around.  The 10 year old mobo that is in storage was
working last I used it.  It was just slow as it gets. 


>
> I've only got one recommendation for ASUS: Stay far away from their
> gaming boards. They're unstable as hell.
>
> I also have an ASRock motherboard (budget board) for one of my computers
> around here, it's not a bad board either.
>
> The only really bad experience I had was with ECS. Garbage boards.
>
> Dan
>
>

I'm not into gaming.  It is one reason I got the one I got now.  It is
supposed to have all the kinks worked out and be ultra durable.  Well,
not so fast Gigabyte.  It's got a pretty serious issue. 

Thanks for the heads up on the gaming boards tho.  I haven't heard that
one.  The mobo I have looked at is this one. 

http://www.newegg.com/Product/Product.aspx?Item=N82E16813131873

Same chipset so basically, just a different brand is all.  I dunno yet.

Dale

:-)  :-)

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

Re: [gentoo-user] Re: New mobo change

[Edward M]

On 10/21/2013 2:13 AM, Dale wrote:
> While I like Gigabyte as a brand, if this is going to be something 
> that reduces the value of my purchase, I want to get something else.


       Appears IOMMU is becoming an industry standard and is also being 
used by other motherboard makers.

http://en.wikipedia.org/wiki/List_of_IOMMU-supporting_hardware

Re: [gentoo-user] Re: New mobo change

[Dale]

Edward M wrote:
> On 10/21/2013 2:13 AM, Dale wrote:
>> While I like Gigabyte as a brand, if this is going to be something
>> that reduces the value of my purchase, I want to get something else.
>
>
>       Appears IOMMU is becoming an industry standard and is also being
> used by other motherboard makers.
>
> http://en.wikipedia.org/wiki/List_of_IOMMU-supporting_hardware
>
>

This is one thing I am trying to figure out.  Is the iommu thing good or
bad?  It was disabled by default and I had to enable it.  Then I had to
edit the kernel command line to get the system to boot.  I don't mind it
enabled in the BIOS as that is a setting.  I just see the kernel command
line as a bit of a hack.  When I got this figured out and posted here,
that was one of the things I was wondering about.  Is this a good thing
or bad thing?  From what I have read, Linux is not supporting something
and that is the reason for the failure.  I'm just trying to figure out
which way this thing is leaning. 

Right now, this is a bit confusing.  :/

Dale

:-)  :-) 

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

Re: [gentoo-user] Re: New mobo change

[Frank Steinmetzger]

[-- Attachment #1: Type: text/plain, Size: 1108 bytes --]

On Sun, Oct 20, 2013 at 10:54:05PM -0500, Dale wrote:
> William Kenworthy wrote:
> > On 21/10/13 11:09, Dale wrote:
> >>
> >> I rebooted and the newest sysrescue still wouldn't boot up.  It says it
> >> can't find /sysrcd.dat which I think is caused because it can't use the
> >> USB port that the sysrescue stick is plugged into.

That is from the kernel which you already loaded from USB. It just can't
find the root filesystem which can have different causes (not necessarily
hardware). I have the same problem nowadays with my Gentoo-based USB linux
that I built for myself.

> Well, I have enabled everything I could find from the Knoppix test and
> it still does not work.  I'm likely going to just try to config a kernel
> from scratch later on.  That or go back to the one from my old mobo and
> just change the chipset.  See if that works. 

I don't remember having read at all what kind of board(s) you have.
Brand? Type?

-- 
Gruß | Greetings | Qapla’
Please do not share anything from, with or about me with any Facebook service.

Which animal can add?  An Octoplus.

[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 198 bytes --]

Re: [gentoo-user] Re: New mobo change

[Dale]

[-- Attachment #1: Type: text/plain, Size: 2018 bytes --]

Frank Steinmetzger wrote:
> On Sun, Oct 20, 2013 at 10:54:05PM -0500, Dale wrote:
>> William Kenworthy wrote:
>>> On 21/10/13 11:09, Dale wrote:
>>>>
>>>> I rebooted and the newest sysrescue still wouldn't boot up.  It says it
>>>> can't find /sysrcd.dat which I think is caused because it can't use the
>>>> USB port that the sysrescue stick is plugged into.
>
> That is from the kernel which you already loaded from USB. It just can't
> find the root filesystem which can have different causes (not necessarily
> hardware). I have the same problem nowadays with my Gentoo-based USB linux
> that I built for myself.

From testing, it turned out to be a BIOS setting and some things that
isn't supported in 64 bit Linux.  Basically, you have to hack your way
into getting something to work.  If I could pass the right option to the
kernel on sysrescue then it would likely work.  As it is, without that
option, it is failing because the hardware is not supported.  Again,
that is based on what I did and what resolved the issue.  I plan to test
that sysrescue option soon because something could happen that I need
that to work.


>
>> Well, I have enabled everything I could find from the Knoppix test and
>> it still does not work.  I'm likely going to just try to config a kernel
>> from scratch later on.  That or go back to the one from my old mobo and
>> just change the chipset.  See if that works.
>
> I don't remember having read at all what kind of board(s) you have.
> Brand? Type?
>

It's a Gigabyte 970A-UD3P and it seems to be a known issue as well.  
Note the 970A-UD3 is the same mobo.  The P stands for extra copper to
dissipate heat better.

Also for everyone else, I just looked, it appears the BIOS version on
the website is the version currently on the mobo.  So, no upgrade
available it seems.  It's looking like I either live with a hack job or
swap for something else.

Dale

:-)  :-)

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


[-- Attachment #2: Type: text/html, Size: 2854 bytes --]

Re: [gentoo-user] Re: New mobo change

[Neil Bothwick]

[-- Attachment #1: Type: text/plain, Size: 651 bytes --]

On Mon, 21 Oct 2013 12:45:40 -0500, Dale wrote:

> From testing, it turned out to be a BIOS setting and some things that
> isn't supported in 64 bit Linux.  Basically, you have to hack your way
> into getting something to work.  If I could pass the right option to the
> kernel on sysrescue then it would likely work.  As it is, without that
> option, it is failing because the hardware is not supported. 

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.


-- 
Neil Bothwick

It's not a bug, it's tradition!

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 198 bytes --]

Re: [gentoo-user] Re: New mobo change

[Dale]

Neil Bothwick wrote:
> On Mon, 21 Oct 2013 12:45:40 -0500, Dale wrote:
>
>> From testing, it turned out to be a BIOS setting and some things that
>> isn't supported in 64 bit Linux.  Basically, you have to hack your way
>> into getting something to work.  If I could pass the right option to the
>> kernel on sysrescue then it would likely work.  As it is, without that
>> option, it is failing because the hardware is not supported. 
> 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.  ^-^

Thanks again.

Dale

:-)  :-) 

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

Re: [gentoo-user] Re: New mobo change

[Neil Bothwick]

[-- Attachment #1: Type: text/plain, Size: 961 bytes --]

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.


-- 
Neil Bothwick

Sometimes too much to drink is not enough.

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 198 bytes --]

Re: [gentoo-user] Re: New mobo change

[Dale]

[-- Attachment #1: Type: text/plain, Size: 3836 bytes --]

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!


[-- Attachment #2: Type: text/html, Size: 4989 bytes --]

Re: [gentoo-user] Re: New mobo change

[Neil Bothwick]

[-- Attachment #1: Type: text/plain, Size: 685 bytes --]

On Tue, 22 Oct 2013 04:04:21 -0500, Dale wrote:

> 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:

> 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 >

Did you consider the possibility that the fault lies within the UPS?


-- 
Neil Bothwick

JPEG (JPG)
 Joint Photographic Experts Group. The original name of the
 committee that designed the eponymous standard image compression
 algorithm. Abbreviated to JPG by PPL WHO CNT TYP or WSE PCS ARE BKN.

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 198 bytes --]

Re: [gentoo-user] Re: New mobo change

[Dale]

[-- Attachment #1: Type: text/plain, Size: 786 bytes --]

Neil Bothwick wrote:
> On Tue, 22 Oct 2013 04:04:21 -0500, Dale wrote:
>
>> 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:
>
>> 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 >
>
> Did you consider the possibility that the fault lies within the UPS?
>
>


Yep.  The UPS costs even more than the mobo tho.  ;-)  Still sucks tho. 
As it was, I don't have anything to test the UPS with.  I had to replace
something.

Oh well.  Live and learn.

Dale

:-)  :-)

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


[-- Attachment #2: Type: text/html, Size: 1392 bytes --]

Re: [gentoo-user] Re: New mobo change

[Neil Bothwick]

[-- Attachment #1: Type: text/plain, Size: 491 bytes --]

On Tue, 22 Oct 2013 05:52:06 -0500, Dale wrote:

> > Did you consider the possibility that the fault lies within the UPS?

> Yep.  The UPS costs even more than the mobo tho.  ;-)  Still sucks tho. 
> As it was, I don't have anything to test the UPS with.  I had to replace
> something.

Take the UPS to a friend's house and connect it to his computer. If it
breaks:

1) Get a new UPS
2) Get a new friend


-- 
Neil Bothwick

WinErr 004: Erroneous error - Nothing is wrong

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 198 bytes --]

Re: [gentoo-user] Re: New mobo change

[Dale]

Neil Bothwick wrote:
> On Tue, 22 Oct 2013 05:52:06 -0500, Dale wrote:
>
>>> Did you consider the possibility that the fault lies within the UPS?
>> Yep.  The UPS costs even more than the mobo tho.  ;-)  Still sucks tho. 
>> As it was, I don't have anything to test the UPS with.  I had to replace
>> something.
> Take the UPS to a friend's house and connect it to his computer. If it
> breaks:
>
> 1) Get a new UPS
> 2) Get a new friend
>
>


Well, I thought of taking it to my bros.  Thing is, his puter is already
flakey.  It reboots at will sometimes, video just goes blank, keyboard
stops working etc etc etc.  I think the mobo in that thing is just about
gone.  It's about 10 years old tho.  Slow as syrup that just came out of
a freezer too.  Oh, only 768MBs of ram.  O_O  That is maxed out.  It's
all the mobo can take. 

At least now I have the makings of a new rig tho.  I got a mobo and some
ram.  LOL 

I hate crawling under my desk tho. 

Dale

:-)  :-) 

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

Re: [gentoo-user] Re: New mobo change

[Bruce Hill]

On Tue, Oct 22, 2013 at 04:04:21AM -0500, Dale wrote:
> 
> 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

I was about to suggest you search http://www.apc.com/support/answers.cfm for a
possible meaning to "status -121" from APC. Assuming it's an APC unit. I can't
search for you cause they demand cookies. Later I read Neil's reply to you.

You can always bring the UPS to Tupelo on your next visit for your brother;
along with the entire rig if you'd like.

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

Re: [gentoo-user] Re: New mobo change

[Dale]

Bruce Hill wrote:
> On Tue, Oct 22, 2013 at 04:04:21AM -0500, Dale wrote:
>> 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
> I was about to suggest you search http://www.apc.com/support/answers.cfm for a
> possible meaning to "status -121" from APC. Assuming it's an APC unit. I can't
> search for you cause they demand cookies. Later I read Neil's reply to you.
>
> You can always bring the UPS to Tupelo on your next visit for your brother;
> along with the entire rig if you'd like.
>
> Cheers, Homie!


Mine is a CyberPower UPS.  I use nut for it tho.  Just uses a different
driver.  I got it plugged into a 3.0 port now and going to test that.  I
may run up to my bothers and see what it does there too.  Bringing it up
your way could work to tho.  ;-) 

Dale

:-)  :-) 

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

Re: [gentoo-user] Re: New mobo change

[Edward M]

On 10/22/2013 2:04 AM, Dale wrote:
> I started the UPS service that started this whole mess to see if it 
> works.  This is from messages:
> 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 ffff8803ea
> Oct 22 02:47:50 localhost kernel: [51255.888492] 43f980 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

         Hello,

        Those messages appear are coming from the ohci driver;I guess, 
possibly a bug in the ohci-q.c file
         Did those messages appear after  an gentoo-sources  upgrade?
         Did you try booting into an older linux kernel version to see 
if those messages appear?

Re: [gentoo-user] Re: New mobo change

[Dale]

Edward M wrote:
> On 10/22/2013 2:04 AM, Dale wrote:
>> I started the UPS service that started this whole mess to see if it
>> works.  This is from messages:
>> 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 ffff8803ea
>> Oct 22 02:47:50 localhost kernel: [51255.888492] 43f980 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
>
>         Hello,
>
>        Those messages appear are coming from the ohci driver;I guess,
> possibly a bug in the ohci-q.c file
>         Did those messages appear after  an gentoo-sources  upgrade?
>         Did you try booting into an older linux kernel version to see
> if those messages appear?
>
>

I been running 3.9.5 for a while but did try my old 3.5.3 version.  That
was with my old mobo but same situation.  Same error.  The biggest
problem, I don't know when the error messages started.  I sort of been
busy and haven't checked the messages file in a while. 

I also tried a older version of nut just in case.  Same thing. 

Thanks.

Dale

:-)  :-) 

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