Re: [DNG] mouse driver question

[Fred]

On 4/24/22 13:56, k...@aspodata.se wrote:

Fred:

On 4/23/22 12:53, k...@aspodata.se wrote:

...

If so, press Ctl-Alt-F2 buttons simultaineusly to get to a console.
There log in as root
and then try one of
gpm -b 1200 -m /dev/ttyUSB0 -t msc
gpm -b 1200 -m /dev/ttyUSB0 -t sun
gpm -b 1200 -m /dev/ttyUSB0 -t mman
and move the mouse to test.


This works.  The msc protocol works best, the mman protocol doesn't work
at all.  All three buttons show some effect.


Very good.

...

B, try inputattach to make the mouse appear as a /dev/input/* device
 and be automatically included by X11, I haven't tested this. See

 https://wiki.archlinux.org/title/Serial_input_device_to_kernel_input
 https://sourceforge.net/projects/linuxconsole/files/
 https://help.ubuntu.com/community/SerialMouseHowto
 https://wiki.alpinelinux.org/wiki/Serial_Mouse

...

There is some progress. The inputattach package in Devuan apparently
doesn't have a config file.  Specifying the baud on the command line
results in an invalid baud message. inputattach does work with the Sun
mouse but the middle button doesn't work.  I tried msc and sun protocol
and both work the same.  I may try some other protocols but I suspect a
bug in inputattach.  Maybe I should contact the maintainer?


I have no experience with inputattach, but looking at
utils/inputattach.c from
  https://sourceforge.net/projects/linuxconsole/files/latest/download
around line 1163:

switch(baud[i]) {
case -1: break;
case 2400: type[i]->speed = B2400; break;
case 4800: type[i]->speed = B4800; break;
case 9600: type[i]->speed = B9600; break;
case 19200: type[i]->speed = B19200; break;
case 38400: type[i]->speed = B38400; break;
case 115200: type[i]->speed = B115200; break;
default:
fprintf(stderr, "inputattach: invalid baud rate '%d'\n",
baud[i]);
return EXIT_FAILURE;
}

and

$ grep -A2 msc inputattach.c
{ "--mousesystems", "-msc", "3-button Mouse Systems mouse",
 B1200, CS8,
 SERIO_MSC,  0x00,   0x01,   1,  NULL },

So, yes, you found a bug.

Add this before the "case 2400" line:

case 1200: type[i]->speed = B1200; break;

compile and test.

Regards,
/Karl Hammar


Hi Karl,

The compile fails because SDL.h can't be found.
Package sd12 was not found in the pkg-config search path.  It also 
mentions adding directory containing sd12.pc to the PKG-CONFIG_PATH 
environment variable.


Best regards,
Fred
___
Dng mailing list
Dng@lists.dyne.org
https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng

Re: [DNG] mouse driver question

[karl]

Fred:
...
> The middle button is being seen as the pointer won't move when it is 
> held down.  It would appear the application is being told something 
> different than when the standard pc mouse is used.

It is probably because you were forced to set the wron baudrate.

Regards,
/Karl Hammar

___
Dng mailing list
Dng@lists.dyne.org
https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng

Re: [DNG] mouse driver question

[karl]

Fred:
> On 4/23/22 12:53, k...@aspodata.se wrote:
...
> > If so, press Ctl-Alt-F2 buttons simultaineusly to get to a console.
> > There log in as root
> > and then try one of
> >gpm -b 1200 -m /dev/ttyUSB0 -t msc
> >gpm -b 1200 -m /dev/ttyUSB0 -t sun
> >gpm -b 1200 -m /dev/ttyUSB0 -t mman
> > and move the mouse to test.
> > 
> This works.  The msc protocol works best, the mman protocol doesn't work 
> at all.  All three buttons show some effect.

Very good.

...
> > B, try inputattach to make the mouse appear as a /dev/input/* device
> > and be automatically included by X11, I haven't tested this. See
> > 
> > https://wiki.archlinux.org/title/Serial_input_device_to_kernel_input
> > https://sourceforge.net/projects/linuxconsole/files/
> > https://help.ubuntu.com/community/SerialMouseHowto
> > https://wiki.alpinelinux.org/wiki/Serial_Mouse
...
> There is some progress. The inputattach package in Devuan apparently 
> doesn't have a config file.  Specifying the baud on the command line 
> results in an invalid baud message. inputattach does work with the Sun 
> mouse but the middle button doesn't work.  I tried msc and sun protocol 
> and both work the same.  I may try some other protocols but I suspect a 
> bug in inputattach.  Maybe I should contact the maintainer?

I have no experience with inputattach, but looking at
utils/inputattach.c from
 https://sourceforge.net/projects/linuxconsole/files/latest/download
around line 1163:

switch(baud[i]) {
case -1: break;
case 2400: type[i]->speed = B2400; break;
case 4800: type[i]->speed = B4800; break;
case 9600: type[i]->speed = B9600; break;
case 19200: type[i]->speed = B19200; break;
case 38400: type[i]->speed = B38400; break;
case 115200: type[i]->speed = B115200; break;
default:
fprintf(stderr, "inputattach: invalid baud rate '%d'\n",
baud[i]);
return EXIT_FAILURE;
}

and

$ grep -A2 msc inputattach.c 
{ "--mousesystems", "-msc", "3-button Mouse Systems mouse",
B1200, CS8,
SERIO_MSC,  0x00,   0x01,   1,  NULL },

So, yes, you found a bug.

Add this before the "case 2400" line:

case 1200: type[i]->speed = B1200; break;

compile and test.

Regards,
/Karl Hammar


___
Dng mailing list
Dng@lists.dyne.org
https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng

Re: [DNG] mouse driver question

[Fred]

On 4/24/22 10:49, Fred wrote:

Hi,

On 4/23/22 12:53, k...@aspodata.se wrote:

Fred:

On 4/23/22 02:34, k...@aspodata.se wrote:

...

So, make sure you are running in a virtual console and logged in as
root, then run the gpm -b etc. thing and move the mouse around.

To make the mouse to work in X11, please test the mouse with gpm in
a console first to assert basic functionality, and then come back.


Did you do the test above ?

As long the serial port isn't opened by anything,
you can let X11 and openbox be running.

If so, press Ctl-Alt-F2 buttons simultaineusly to get to a console.
There log in as root
and then try one of
   gpm -b 1200 -m /dev/ttyUSB0 -t msc
   gpm -b 1200 -m /dev/ttyUSB0 -t sun
   gpm -b 1200 -m /dev/ttyUSB0 -t mman
and move the mouse to test.

This works.  The msc protocol works best, the mman protocol doesn't work 
at all.  All three buttons show some effect.



A previous post mentioned xorg.conf which doesn't appear to exist in
Devuan Beowulf (AMD64).
So, where do I go from here?


You can either
A, do a xorg configuration with the mouse driver
    man xorg.conf is your friend.

B, try inputattach to make the mouse appear as a /dev/input/* device
    and be automatically included by X11, I haven't tested this. See

    https://wiki.archlinux.org/title/Serial_input_device_to_kernel_input
    https://sourceforge.net/projects/linuxconsole/files/
    https://help.ubuntu.com/community/SerialMouseHowto
    https://wiki.alpinelinux.org/wiki/Serial_Mouse

Regards,
/Karl Hammar

There is some progress. The inputattach package in Devuan apparently 
doesn't have a config file.  Specifying the baud on the command line 
results in an invalid baud message. inputattach does work with the Sun 
mouse but the middle button doesn't work.  I tried msc and sun protocol 
and both work the same.  I may try some other protocols but I suspect a 
bug in inputattach.  Maybe I should contact the maintainer?


Best regards,
Fred

The middle button is being seen as the pointer won't move when it is 
held down.  It would appear the application is being told something 
different than when the standard pc mouse is used.


Best regards,
Fred
___
Dng mailing list
Dng@lists.dyne.org
https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng

Re: [DNG] trouble with rdiff-backup

[Florian Zieboll via Dng]

On Sun, 24 Apr 2022 13:17:38 -0400
Hendrik Boom  wrote:

> OSError: [Errno 30] Read-only file system
>
> Is anyone else having problems like these?  Is rdiff-backup busted?
> Or is my new backup drive or my USB interface busted?


No issues with my rdiff-backup (chimaera) here: I just moved it to
another location yesterday (a newly formatted ext4 partition on a SATA
drive; the backup script was run before and after the move) and created
a second backup on an also newly ext4-formatted LUKS-Partition on a USB
attached external disk.

Did your backup drive really go (permanently?) 'read only', or have you
been able to write to it by other means? 

libre Grüße,
Florian
___
Dng mailing list
Dng@lists.dyne.org
https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng

Re: [DNG] mouse driver question

[Fred]

Hi,

On 4/23/22 12:53, k...@aspodata.se wrote:

Fred:

On 4/23/22 02:34, k...@aspodata.se wrote:

...

So, make sure you are running in a virtual console and logged in as
root, then run the gpm -b etc. thing and move the mouse around.

To make the mouse to work in X11, please test the mouse with gpm in
a console first to assert basic functionality, and then come back.


Did you do the test above ?

As long the serial port isn't opened by anything,
you can let X11 and openbox be running.

If so, press Ctl-Alt-F2 buttons simultaineusly to get to a console.
There log in as root
and then try one of
   gpm -b 1200 -m /dev/ttyUSB0 -t msc
   gpm -b 1200 -m /dev/ttyUSB0 -t sun
   gpm -b 1200 -m /dev/ttyUSB0 -t mman
and move the mouse to test.

This works.  The msc protocol works best, the mman protocol doesn't work 
at all.  All three buttons show some effect.



A previous post mentioned xorg.conf which doesn't appear to exist in
Devuan Beowulf (AMD64).
So, where do I go from here?


You can either
A, do a xorg configuration with the mouse driver
man xorg.conf is your friend.

B, try inputattach to make the mouse appear as a /dev/input/* device
and be automatically included by X11, I haven't tested this. See

https://wiki.archlinux.org/title/Serial_input_device_to_kernel_input
https://sourceforge.net/projects/linuxconsole/files/
https://help.ubuntu.com/community/SerialMouseHowto
https://wiki.alpinelinux.org/wiki/Serial_Mouse

Regards,
/Karl Hammar

There is some progress. The inputattach package in Devuan apparently 
doesn't have a config file.  Specifying the baud on the command line 
results in an invalid baud message. inputattach does work with the Sun 
mouse but the middle button doesn't work.  I tried msc and sun protocol 
and both work the same.  I may try some other protocols but I suspect a 
bug in inputattach.  Maybe I should contact the maintainer?


Best regards,
Fred

___
Dng mailing list
Dng@lists.dyne.org
https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng

[DNG] trouble with rdiff-backup

[Hendrik Boom]

I've experienced trouble using rdiff-backup when backing up a file tree onto a 
new backup drive.

The backup drive (initially something like vfat) was reformatted by creating an 
ext4 file system on its first and only partition.

Subsequently asking rdiff-backup to back up /farhome/hendrik onto 
/usbackup/backup-by-rdiff/april/farhome--hendrik (creating the necessary 
directories first; abd usbackup is where the new backup drive's one partition 
is mounted)

I get error messages.

FIRST:

A lot of complaints that it has trouble reading an ACL because th utf-8 codec 
cannot encode character \udsf1.
So where could it get thes character from?
The file it's complaining about is 
/usbackup/backup-by-rdiff/april/farhome--hendrik/amiga/susehendrik/amiga/foo/emulation/shared/dir/system/locale/catalogs/espa�ol
This is clearly a file on the backup disk, which is a new disk.  So wouldn't it 
have to have put this character there itself?

There are a lot of error message like this.  Now I don't use access control 
lists, as far as I know, so where are they coming from?  Perhaps I should tell 
it not to back up ACL's?

SECOND:




Eventually it gets around to delivering a python error message:

Exception '[Errno 30] Read-only file system' raised of class '':
  File "/usr/lib/python3/dist-packages/rdiff_backup/Main.py", line 395, in 
error_check_Main
Main(arglist)
  File "/usr/lib/python3/dist-packages/rdiff_backup/Main.py", line 417, in Main
take_action(rps)
  File "/usr/lib/python3/dist-packages/rdiff_backup/Main.py", line 353, in 
take_action
Backup(rps[0], rps[1])
  File "/usr/lib/python3/dist-packages/rdiff_backup/Main.py", line 442, in 
Backup
backup.Mirror(rpin, rpout)
  File "/usr/lib/python3/dist-packages/rdiff_backup/backup.py", line 39, in 
Mirror
DestS.patch(dest_rpath, source_diffiter)
  File "/usr/lib/python3/dist-packages/rdiff_backup/backup.py", line 269, in 
patch
ITR(diff.index, diff)
  File "/usr/lib/python3/dist-packages/rdiff_backup/rorpiter.py", line 313, in 
__call__
last_branch.fast_process(*args)
  File "/usr/lib/python3/dist-packages/rdiff_backup/backup.py", line 587, in 
fast_process
if self.patch_to_temp(mirror_rp, diff_rorp, tf):
  File "/usr/lib/python3/dist-packages/rdiff_backup/backup.py", line 612, in 
patch_to_temp
result = self.patch_snapshot_to_temp(diff_rorp, new)
  File "/usr/lib/python3/dist-packages/rdiff_backup/backup.py", line 659, in 
patch_snapshot_to_temp
(diff_rorp, new))
  File "/usr/lib/python3/dist-packages/rdiff_backup/robust.py", line 35, in 
check_common_error
return function(*args)
  File "/usr/lib/python3/dist-packages/rdiff_backup/rpath.py", line 148, in copy
return copy_reg_file(rpin, rpout, compress)
  File "/usr/lib/python3/dist-packages/rdiff_backup/rpath.py", line 181, in 
copy_reg_file
return rpout.write_from_fileobj(rpin.open("rb"), compress=compress)
  File "/usr/lib/python3/dist-packages/rdiff_backup/rpath.py", line 1475, in 
write_from_fileobj
copyfileobj(fp, outfp)
  File "/usr/lib/python3/dist-packages/rdiff_backup/rpath.py", line 90, in 
copyfileobj
outputfp.write(inbuf)

Suddenly it cannot write on a file system.  Presumably the backup drive?  The 
one it has already filled with 215831712 iK blocks and has abother 1608278664 
available?

Then more complaints about banned unicode characters, and then another similar 
backtrace ending with

OSError: [Errno 30] Read-only file system

Is anyone else having problems like these?  Is rdiff-backup busted?  Or is my 
new backup drive or my USB interface busted?

-- hendrik
___
Dng mailing list
Dng@lists.dyne.org
https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng

Re: [DNG] Hardware support for new Thinkpad?

[Gastón via Dng]

On Sun, Apr 24, 2022 at 07:28:38AM -0400, . via Dng wrote:
> I just got a Thinkpad P1 gen 4, and Chimaera doesn't recognize the audio,
> camera, or HDMI port (not to mention the fingerprint sensor in the power
> switch).  I could use some guidance in what to look for...
> 
> It has a Tiger Lake-H processor, I don't know what chipset.  I think I need
> a command like "lspci" to identify the multimedia hardware, but I don't know
> what to look for.
> 
> For what it's worth, the last couple of releases of Ubuntu *do* support the
> multimedia hardware.  Do I need to move to Daedalus?  If so, is there an
> install package for that?
> 
Hi, did you try to install the kernel that is in the chimaera
backports repo?

It is version 5.16, the same that will come in Daedalus.

$ apt-cache madison linux-image-amd64
linux-image-amd64 | 5.17.3-1 | http://deb.devuan.org/merged unstable/main amd64 
Packages
linux-image-amd64 | 5.16.18-1 | http://deb.devuan.org/merged daedalus/main 
amd64 Packages
linux-image-amd64 | 5.16.12-1~bpo11+1 | http://deb.devuan.org/merged 
chimaera-backports/main amd64 Packages
linux-image-amd64 | 5.10.106-1 | http://deb.devuan.org/merged chimaera/main 
amd64 Packages


--
gast0n

___
Dng mailing list
Dng@lists.dyne.org
https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng

Re: [DNG] mouse driver question

[Arnt Karlsen]

On Sat, 23 Apr 2022 21:11:18 +0200, Florian wrote in message 
<2022042328.14e36a59.f.zieb...@web.de>:

> Some time ago, in a similar situation, I had been successful with
> 
> $ find / | grep xorg.conf
> 
> Also worth a try:
> 
> $ man 5 xorg.conf


..also worth trying:~$ man -k xorg.conf

...and the educational: $ man -h  # ;o)


-- 
..med vennlig hilsen = with Kind Regards from Arnt Karlsen
...with a number of polar bear hunters in his ancestry...
  Scenarios always come in sets of three: 
  best case, worst case, and just in case.
___
Dng mailing list
Dng@lists.dyne.org
https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng

Re: [DNG] Hardware support for new Thinkpad?

[onefang]

On 2022-04-24 07:28:38, . via Dng wrote:
> I just got a Thinkpad P1 gen 4, and Chimaera doesn't recognize the audio,
> camera, or HDMI port (not to mention the fingerprint sensor in the power
> switch).  I could use some guidance in what to look for...
> 
> It has a Tiger Lake-H processor, I don't know what chipset.  I think I need
> a command like "lspci" to identify the multimedia hardware, but I don't know
> what to look for.
> 
> For what it's worth, the last couple of releases of Ubuntu *do* support the
> multimedia hardware.  Do I need to move to Daedalus?  If so, is there an
> install package for that?
> 
> Thanks for any help in getting this machine up on Devuan.

Need more info.

Do you mean it's not even showing the devices using those commands others
replied with?

Are you using pulseaudio, which is the default, and it's just not showing
up in their mixer?

Are you using raw ALSA like me, and being very surprised that my graphics
card with two HDMI and two Display Port connectors is showing a dozen HDMI
audio ports, most of which don't work?  But two or three of them do work,
and not always the same ones.

Or something else?

VLC was quite useful in listing all the audio devices, and letting me
quickly switch between them.

-- 
A big old stinking pile of genius that no one wants
coz there are too many silver coated monkeys in the world.
___
Dng mailing list
Dng@lists.dyne.org
https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng

Re: [DNG] Hardware support for new Thinkpad?

[Dr. Nikolaus Klepp via Dng]

Anno domini 2022 Sun, 24 Apr 07:28:38 -0400
 . via Dng scripsit:
> I just got a Thinkpad P1 gen 4, and Chimaera doesn't recognize the 
> audio, camera, or HDMI port (not to mention the fingerprint sensor in 
> the power switch).  I could use some guidance in what to look for...
> 
> It has a Tiger Lake-H processor, I don't know what chipset.  I think I 
> need a command like "lspci" to identify the multimedia hardware, but I 
> don't know what to look for.
> 
> For what it's worth, the last couple of releases of Ubuntu *do* support 
> the multimedia hardware.  Do I need to move to Daedalus?  If so, is 
> there an install package for that?
> 
> Thanks for any help in getting this machine up on Devuan.
> 
> -Bob Montante
> 
> 

Have you tried devuan/deadalus, too?

Nik

-- 
Please do not email me anything that you are not comfortable also sharing with 
the NSA, CIA ...
___
Dng mailing list
Dng@lists.dyne.org
https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng

Re: [DNG] mouse driver question

[aitor]

On 24/4/22 13:52, aitor wrote:

but enable it when using vdev.


*disable*


___
Dng mailing list
Dng@lists.dyne.org
https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng

Re: [DNG] Hardware support for new Thinkpad?

[Antony Stone]

On Sunday 24 April 2022 at 13:28:38, . via Dng wrote:

> I just got a Thinkpad P1 gen 4, and Chimaera doesn't recognize the
> audio, camera, or HDMI port (not to mention the fingerprint sensor in
> the power switch).  I could use some guidance in what to look for...

I would start with lspci, lsusb and possibly dmidecode.

> It has a Tiger Lake-H processor, I don't know what chipset.  I think I
> need a command like "lspci" to identify the multimedia hardware, but I
> don't know what to look for.

Anything which says "audio" or "video" in the output is a good start :)

> For what it's worth, the last couple of releases of Ubuntu *do* support
> the multimedia hardware.

In that case I would boot into a (live?) version of Ubuntu and run:

lsusb
lspci
lsmod

That last command will tell you which kernel modules have been loaded in order 
to support the various hardware devices.

> Do I need to move to Daedalus?

Possibly - it's worth a try, to see whether it does a better job with less 
work than persuading Chimaera.

> If so, is there an install package for that?

Yes, for example http://devuan.bardia.tech/devuan_daedalus/installer-iso/

> Thanks for any help in getting this machine up on Devuan.

Feel free to post the output of lsusb and lspci here (best from Ubuntu, since 
it seems really to know what the things are) in case anyone recognises devices 
and can point you further in a helpful direction.


Antony.

-- 
The first fifty percent of an engineering project takes ninety percent of the 
time, and the remaining fifty percent takes another ninety percent of the time.

   Please reply to the list;
 please *don't* CC me.
___
Dng mailing list
Dng@lists.dyne.org
https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng

Re: [DNG] mouse driver question

[aitor]

Hi Ralph,

On 23/4/22 23:32, Ralph Ronnquist wrote:

Then, I think the X11 system relies on udev for setting up its inputs
and load the appropriate modules. You may take over that and do things
"by hand" by a) making the following file /etc/X11/xorg.conf.d/a.conf

Section "ServerFlags"
 Option "AutoAddDevices" "false"
EndSection



X11-common contains a file config/udev.c and -if i'm not mistaken- as 
long as the sources are built enabling CONFIG_UDEV, the above option 
"AutoAddDevices" is set up to true by default. On the contrary, vdev 
requires the following setup to get both the keyboard and mouse working:


Section "ServerFlags"     Option "AutoAddDevices" "off"     Option 
"AllowEmptyInput" "on" (either "off") EndSection


I don't think this configuration would work with eudev, because I guess 
that "AutoAddDevices" is required to carry out udev monitor's event 
processing (libudev-enumerate.c). On the contrary, vdev removes the 
netlink connection to udev, in favor of creating the underlying 
`udev_monitor`specific directory:


* /dev/events/libudev-$PID

watched by vdev's helpers for new packet events. This is the way vdev 
works. So, libudev-compat (vdev) connects to a netlink socket only if 
the name is "kernel" and removes this netlink connection if the name is 
"udev", because vdevd's helper scripts will send serialized device 
events by writing them as files (here, Jude Nelson recommends the 
installation of eventfs).


It's because libeudev and libudev-compat work with opposing approaches, 
my recommendation is to not disable "AutoAddDevices" when using eudev, 
but enable it when using vdev.


Cheers,

Aitor.


___
Dng mailing list
Dng@lists.dyne.org
https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng

[DNG] Hardware support for new Thinkpad?

[. via Dng]

I just got a Thinkpad P1 gen 4, and Chimaera doesn't recognize the 
audio, camera, or HDMI port (not to mention the fingerprint sensor in 
the power switch).  I could use some guidance in what to look for...


It has a Tiger Lake-H processor, I don't know what chipset.  I think I 
need a command like "lspci" to identify the multimedia hardware, but I 
don't know what to look for.


For what it's worth, the last couple of releases of Ubuntu *do* support 
the multimedia hardware.  Do I need to move to Daedalus?  If so, is 
there an install package for that?


Thanks for any help in getting this machine up on Devuan.

-Bob Montante


--

“The first ten million years were the worst," said Marvin, "and the 
second ten million years, they were the worst too. The third ten million 
years I didn't enjoy at all. After that I went into a bit of a decline.”


___
Dng mailing list
Dng@lists.dyne.org
https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng

Re: [DNG] mouse driver question

[karl]

Fred:
...
> I also don't like the beetle wings for buttons one and three because
> I am often accidentally clicking button three.
...

Yes, it is wery annoying when you accidentally press button three.

Regards,
/Karl Hammar

___
Dng mailing list
Dng@lists.dyne.org
https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng

Re: [DNG] mouse driver question

[karl]

Ralph Ronnquist:
...
> I think all mice are supposed to be handled by the kernel and will
> then get presented at /dev/input/mice
...

At some level every hardware is handled by the kernel. What you are
talking about is the input subsystem. To make a serial mouse work
or use the input subsystem you have to do an inputattach so the mouse
attached at /dev/ttySx is available as /dev/input/mouseY.

As you kan see in the kernel source/drivers/input/mouse/sermouse.c,
in function
 static void sermouse_process_msc(struct sermouse *sermouse, signed char data)
it takes the protocol and converts it to another protocol.

For that function to work you need it be configured in the kernel, 
build in or as a module. This command should return y or m.

# grep MOUSE_SERIAL /boot/config-`uname -r`
CONFIG_MOUSE_SERIAL=y

If done as a module, you need to
 modprobe sermouse

After that you do the inputattach of the serial port.
At this stage you need to know the protocol used, there is no
autodetection.

It is in a sense similar to the gpm repeater mode.

> Section "ServerFlags"
> Option "AutoAddDevices" "false"
> EndSection

I.e. either you do it all by yourself, or you use hw that can be auto 
detected, there is no midpoint, like auto detect gpu and monitor, but 
use this mouse...

Yea, thanks x devs. for ditching us with unusual hw.

> and b) installing xserver-xorg-input-kbd and xserver-xorg-input-mouse
...

Thoose two drivers are abandoned upstream from what I heard.

Regards,
/Karl Hammar


___
Dng mailing list
Dng@lists.dyne.org
https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng

Re: [DNG] mouse driver question

[karl]

Fred:
...
> If gpm only works in a virtual terminal why do I need to continue 
> working with it?  I don't use a virtual terminal.
...

Since it is such a simple test to do, e.g. you don't have to restart
the X server to try another protocol.

Regards,
/Karl Hammar

___
Dng mailing list
Dng@lists.dyne.org
https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng

Re: [DNG] Looking for xorg.conf (was Re: mouse driver question)

[karl]

Olaf Meeuwissen:
...
> As I mentioned in a previous response, nowadays Xorg gets by without
> this file quite well, most of the time.  It simply probes your system
> and uses what it finds.
...

That has never worked for serial mice, sorry.

Regards,
/Karl Hammar

___
Dng mailing list
Dng@lists.dyne.org
https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng

[DNG] Find efficiency [Was: Re: mouse driver question]

[Antony Stone]

On Sunday 24 April 2022 at 04:15:35, Olaf Meeuwissen via Dng wrote:

> Hi,
> 
> Antony Stone writes:
> > 
> > I just tried several successive searches for a few unique filenames in a
> > directory tree (all files in the same directory, just in case the
> > position made a difference).
> > 
> > The first search took 6 minutes and clearly set up some cache of results,
> > because subsequent searches were consistently:
> > 
> > find . | grep filename : 20 seconds
> > 
> > find . -name filename : 25 seconds
> > 
> > That was consistent no matter whether the two filenames were the same, or
> > different but still in the same directory, and no matter which command
> > was run first.
> > 
> > Nice observation.
> 
> Indeed but you must have an awful lot of files, slow disks and/or a slow
> network connection.  After setting up the cache on my machine, I get 0.7
> seconds for the -name approach and 0.5 seconds for grep.
> That's with close to half a million filesystem entries and about 7000 of
> those on an NFS backed filesystem on the NAS downstairs.  The rest is on
> an SSD (NVMe).

I deliberately chose a large file system because I prefer comparing bigger 
numbers when I can.

In my case there are 11,174,006 files occupying 8.8 Tbytes, all on spinning 
metal disks, and housed in not-especially-fast HP N54L microservers.

Antony.

-- 
"It would appear we have reached the limits of what it is possible to achieve 
with computer technology, although one should be careful with such statements; 
they tend to sound pretty silly in five years."

 - John von Neumann (1949)

   Please reply to the list;
 please *don't* CC me.
___
Dng mailing list
Dng@lists.dyne.org
https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng

Re: [DNG] Looking for xorg.conf (was Re: mouse driver question)

[aitor]

Hi,

On 24/4/22 4:24, Olaf Meeuwissen via Dng wrote:

You can configure things yourself but you'll
have to write your own /etc/X11/xorg.conf yourself.


Yes, but don't forget also /usr/share/X11/xorg.conf.d/*.conf files.

Cheers,

Aitor.


___
Dng mailing list
Dng@lists.dyne.org
https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng