WelcomeWelcome | FAQFAQ | DownloadsDownloads | WikiWiki

Author Topic: [SOLVED] numlockx and Xvesa  (Read 6679 times)

gordon64

  • Guest
Re: numlockx and Xvesa
« Reply #15 on: August 23, 2015, 10:07:04 PM »
and I was not aware that numlockx could work without Xorg

so thanks to Rich and  tinycore

Maybe we can mark as solved?

Offline madmax

  • Jr. Member
  • **
  • Posts: 98
Re: numlockx and Xvesa
« Reply #16 on: August 24, 2015, 10:30:41 AM »
Hello Gordon64:
... not aware that numlockx could work without Xorg.
so thanks to Rich and  tinycore
Only to Rich, you and others who pitched in.
Knowing nothing much about Linux, I just ask the questions.  =-)

Which begs yet another question:

If numlockx works with the Xvesa-7.1.tcz from the 4.x/x86 repo ...
Why does it fail with the Xvesa (Xvesa-old.tcz or Xvesa.tcz) from the 6.x/x86 repo?

Cheers,

TC

gordon64

  • Guest
Re: [SOLVED] numlockx and Xvesa
« Reply #17 on: August 24, 2015, 04:35:46 PM »
Hi

Until you get a better reply....

Why not pm the maintainer of our current package and ask if support can be built for your issue?

good luck


Offline curaga

  • Administrator
  • Hero Member
  • *****
  • Posts: 10225
Re: [SOLVED] numlockx and Xvesa
« Reply #18 on: August 25, 2015, 01:00:40 AM »
The default Xvesa does not support XKB. Take a look at the size difference.
The only barriers that can stop you are the ones you create yourself.

Offline madmax

  • Jr. Member
  • **
  • Posts: 98
Re: [SOLVED] numlockx and Xvesa
« Reply #19 on: August 25, 2015, 10:29:29 AM »
Hello curaga:
The default Xvesa does not support XKB.
I see ...

Take a look at the size difference.
Indeed ...
740K vs. 356K ~ 52% less.

Any other way around it save using xvesa-7.1?

Thanks in advance,

TC

Offline curaga

  • Administrator
  • Hero Member
  • *****
  • Posts: 10225
Re: [SOLVED] numlockx and Xvesa
« Reply #20 on: August 25, 2015, 12:11:39 PM »
Xorg? :P

If the default numlock state bothers you enough, you can add a switch to change it in the tinyX code. Patches welcome.
The only barriers that can stop you are the ones you create yourself.

Offline madmax

  • Jr. Member
  • **
  • Posts: 98
Re: [SOLVED] numlockx and Xvesa
« Reply #21 on: August 25, 2015, 01:42:25 PM »
Hello curaga:
Xorg? :P
Nah !
It's huge and (to me) far too complex.

I'd take it up only if it allowed me to use my Matrox G400/450 Dual with two monitors and one desktop instead of the useless mirror/clone screens.
But from what I understand, Xorg dropped support for the Matrox chips long ago.
If the default numlock state bothers you enough ...
No, it does not bother me at all.
It works fine. I just wonder how long it will be before xvesa-7.1 stops working with TCore and as a result, no more numlockx.   =-/

... you can add a switch to change it in the tinyX code. Patches welcome.
I'm afraid that's all way over my head, at the moment at least.

Cheers,

TC

Offline curaga

  • Administrator
  • Hero Member
  • *****
  • Posts: 10225
Re: [SOLVED] numlockx and Xvesa
« Reply #22 on: August 26, 2015, 01:46:19 AM »
Xvesa-7.1 will likely continue working for the next 10 years or so, barring major changes. Xorg might support dual head, depending on what card you have, but the mga driver would need to be built.

PS: Please stop with the red coloring...
The only barriers that can stop you are the ones you create yourself.

Offline madmax

  • Jr. Member
  • **
  • Posts: 98
Re: [SOLVED] numlockx and Xvesa
« Reply #23 on: August 26, 2015, 04:26:33 AM »
Good morning:
Xvesa-7.1 will likely continue working for the next 10 years or so, barring major changes.
OK

Xorg might support dual head, depending on what card you have ... but the mga driver would need to be built.
There was an mga driver from Xorg that supported the card (Matrox G400/450 Dual) up to some version of the Xserver but I cannot recall which one.
http://www.x.org/archive/X11R7.7/doc/man/man4/mga.4.xhtml
... but the mga driver would need to be built.
No idea as to how to go about that.
Maybe this is a matter for another thread.
PS: Please stop with the red coloring...
:D OK, sorry.

Cheers,

TC