[9fans] Keyboard and Mouse

[9fans] Keyboard and Mouse

[Eldar Tsraev]

I'm just installed Plan9 on pc box (on Intel D915GAG Board)
While installing all (video, keyboard, mouse) works well.
But after first reboot i cant see a mouse pointer but can do some
things with it (buttons are works and mouse moves but i can't see it)
keyboard is ps/2, mouse is usb but connected through ps/2 adapter.

whats wrong?
where can i find some solutions.

thanx
--
SareLius

Re: [9fans] Keyboard and Mouse

[David du Colombier]

> I'm just installed Plan9 on pc box (on Intel D915GAG Board)
> While installing all (video, keyboard, mouse) works well.
> But after first reboot i cant see a mouse pointer but can do some
> things with it (buttons are works and mouse moves but i can't see it)
> keyboard is ps/2, mouse is usb but connected through ps/2 adapter.
>
> whats wrong?
> where can i find some solutions.

This problem is well known, and seems to be
caused by HyperThreading on some CPU.

Try to add the following line to "plan9.ini":
*nomp=1

It will solve this problem.

--
David du Colombier

Re: [9fans] Keyboard and Mouse

[erik quanstrom]

> This problem is well known, and seems to be
> caused by HyperThreading on some CPU.
>
> Try to add the following line to "plan9.ini":
> *nomp=1
>
> It will solve this problem.

hyperthreading?  that doesn't sound right.

do you mean a bad mp interrupt table?

- erik

Re: [9fans] Keyboard and Mouse

[erik quanstrom]

> > This problem is well known, and seems to be
> > caused by HyperThreading on some CPU.
> >
> > Try to add the following line to "plan9.ini":
> > *nomp=1
> >
> > It will solve this problem.
>
> hyperthreading?  that doesn't sound right.
>
> do you mean a bad mp interrupt table?

you can avoid ht by setting *ncpu=1 in your
plan9.ini without disabling mp interrupts.
so it should be easy to say definitivly which
one causes the problem.

as a further explainer, 8259 interrupts can't
work in an mp environment.  you need to
use either mp interrupts or msi interrupts.
since plan 9 doesn't implement msi, *nomp=1
implies that only one cpu may be activated.
so a uniprocessor may still use mp interrupts.

- erik

Re: [9fans] Keyboard and Mouse

[David du Colombier]

> hyperthreading?  that doesn't sound right.
>
> do you mean a bad mp interrupt table?

Yes, you are probably right.

-- 
David du Colombier

Re: [9fans] Keyboard and Mouse

[Eldar Tsraev]

Thanx a lot! That works.
And where a newbie can find information like that. Some known bugs and etc?

2009/7/10 erik quanstrom <quanstro@coraid.com>:
>> > This problem is well known, and seems to be
>> > caused by HyperThreading on some CPU.
>> >
>> > Try to add the following line to "plan9.ini":
>> > *nomp=1
>> >
>> > It will solve this problem.
>>
>> hyperthreading?  that doesn't sound right.
>>
>> do you mean a bad mp interrupt table?
>
> you can avoid ht by setting *ncpu=1 in your
> plan9.ini without disabling mp interrupts.
> so it should be easy to say definitivly which
> one causes the problem.
>
> as a further explainer, 8259 interrupts can't
> work in an mp environment.  you need to
> use either mp interrupts or msi interrupts.
> since plan 9 doesn't implement msi, *nomp=1
> implies that only one cpu may be activated.
> so a uniprocessor may still use mp interrupts.
>
> - erik
>
>

-- 
SareLius