On Thu, Jun 15, 2017 at 07:56:13AM +0530, Mayuresh wrote:
> On Thu, Jun 15, 2017 at 07:54:18AM +0930, Brett Lymn wrote:
> > Ah, that is a bit of an issue then. The touchpad drivers themselves
> > don't have any fine grained controls for turning off some gestures. I
> > guess a bunch of sysctl
On Thu, Jun 15, 2017 at 09:37:39AM +0200, Manuel Bouyer wrote:
> that's fine, pckbc (pms@pckbd@pckbc, actually) handles synaptics too.
> There's no separate driver for synaptics in the NetBSD kernel.
'man pms' shows a lot of hw.synaptics.* properties.
But 'sysctl -a' does not show them. I
On Thu, Jun 15, 2017 at 10:53:26AM +0200, Manuel Bouyer wrote:
> On Thu, Jun 15, 2017 at 02:04:24PM +0530, Mayuresh wrote:
> > On Thu, Jun 15, 2017 at 09:37:39AM +0200, Manuel Bouyer wrote:
> > > that's fine, pckbc (pms@pckbd@pckbc, actually) handles synaptics too.
> > > There's no separate driver
http://netbsd.gw.com/cgi-bin/man-cgi?ss+4.i386+NetBSD-7.0.2
Andreas Beck schrieb:
https://wiki.netbsd.org/scanner/
"
User access
To grant another user access to use the scanner, create a 'scanner'
group.
|# groupadd scanner |
Add user to the group scanner:
|# usermod -G scanner
yes, I think so too, in the manpage ive send here are three devices listed.
http://netbsd.gw.com/cgi-bin/man-cgi?ss+4.i386+NetBSD-7.0.2
BERTRAND Joël schrieb:
Andreas Beck a écrit :
https://wiki.netbsd.org/scanner/
"
User access
To grant another user access to use the scanner, create a
Andreas Beck a écrit :
https://wiki.netbsd.org/scanner/
"
User access
To grant another user access to use the scanner, create a 'scanner' group.
|# groupadd scanner |
Add user to the group scanner:
|# usermod -G scanner user_name |
Change group for a device:
|# chgrp scanner
On Thu, Jun 15, 2017 at 02:28:50PM +0530, Mayuresh wrote:
> On Thu, Jun 15, 2017 at 10:53:26AM +0200, Manuel Bouyer wrote:
> > On Thu, Jun 15, 2017 at 02:04:24PM +0530, Mayuresh wrote:
> > > On Thu, Jun 15, 2017 at 09:37:39AM +0200, Manuel Bouyer wrote:
> > > > that's fine, pckbc (pms@pckbd@pckbc,
currently, ive no netbsd installation on this place. But, do u have
added the user to other needed groups, something like, scanner, sane,
saned... stuff like that?
BERTRAND Joël schrieb:
Andreas Beck a écrit :
Hi,
put your user in the staff group and test it with chmod 777 /dev/ss0
(only
On Wed, 14 Jun 2017, Michael van Elst wrote:
On Wed, Jun 14, 2017 at 10:32:18AM +0530, Mayuresh wrote:
On Wed, Jun 14, 2017 at 04:23:08AM -, Michael van Elst wrote:
An ISCSI target on the other hand doesn't require any privileges if
you just export a file as a disk image.
I mean, even to
Hi,
put your user in the staff group and test it with chmod 777 /dev/ss0
(only for testing, chmod 777)
If its not working, its no rights Problem.
Andreas
BERTRAND Joël schrieb:
Hello,
I use a venerable Agfa scanner 1236S (SCSI) on a Digital PWS500au
workstation running NetBSD 8
Andreas Beck a écrit :
Hi,
put your user in the staff group and test it with chmod 777 /dev/ss0
(only for testing, chmod 777)
If its not working, its no rights Problem.
Thanks for your answer. My user is in staff group and permissions on
/dev/ss0 is 777. With root privileges, xsane runs as
https://wiki.netbsd.org/scanner/
"
User access
To grant another user access to use the scanner, create a 'scanner' group.
|# groupadd scanner |
Add user to the group scanner:
|# usermod -G scanner user_name |
Change group for a device:
|# chgrp scanner /dev/ugen* |
For some drivers,
On Thu, Jun 15, 2017 at 11:05:20AM +0200, Manuel Bouyer wrote:
> It's probably a newer synaptics hardware, which may need a different code.
> It needs to be looked at.
> BTW the code is in src/sys/dev/pckbport/, look at pms* and synaptics*
I tried hacking the condition below to force-detect
On Thu, Jun 15, 2017 at 04:46:22PM +0200, Manuel Bouyer wrote:
> not surprising. you should look what is happening in
> pms_synaptics_probe_init()
> instead.
Sorry for a naive question: How do I see messages printed by
aprint_debug_dev?
Tried booting with -x as well as -v and looked in dmesg.
Andreas Beck a écrit :
yes, I think so too, in the manpage ive send here are three devices listed.
http://netbsd.gw.com/cgi-bin/man-cgi?ss+4.i386+NetBSD-7.0.2
OK. I have found the mistake. ss0, nss0 _and_ enss0 are used by sane.
With 660 permissions an these devices, xsane runs as expected
On Thu, Jun 15, 2017 at 11:37:13PM +0530, Mayuresh wrote:
> On Thu, Jun 15, 2017 at 04:46:22PM +0200, Manuel Bouyer wrote:
> > not surprising. you should look what is happening in
> > pms_synaptics_probe_init()
> > instead.
>
> Sorry for a naive question: How do I see messages printed by
>
On Thu, 15 Jun 2017, BERTRAND Jo?l wrote:
> OK. I have found the mistake. ss0, nss0 _and_ enss0 are used by
> sane. With 660 permissions an these devices, xsane runs as expected
> and withtout root permissions.
Glad it works. Often you can use ktrace to run a tool and then after run
On Fri, Jun 16, 2017 at 10:32:49AM +0700, Robert Elz wrote:
> Most likely for your touchpad synaptics mode is enabled by sending it
> some magic string. You might be able to find out from the linux sources
> as they apparently manage to enable synaptics mode for it.
For x11, Linux sources
On Thu, Jun 15, 2017 at 04:46:22PM +0200, Manuel Bouyer wrote:
> > /* Probe for synaptics touchpad. */
> > if (pms_synaptics_probe_init(sc) == 0) { // made this if(1)
> > sc->protocol = PMS_SYNAPTICS;
> > } else
>
> not surprising. you should look what is happening in
>
On Fri, Jun 16, 2017 at 12:32:32PM +0700, Robert Elz wrote:
> I had also wondered about the possibility of having the pms driver simply
> ignore mouse input when typing - perhaps by simply ignoring anything received
> from the mouse in the the next N milliseconds after a keystroke.
While that
Date:Fri, 16 Jun 2017 08:32:07 +0530
From:Mayuresh
Message-ID: <20170616030207.ga17...@warunjikardental.com>
| Tried forcing synaptics detection by commenting this block.
| Now synaptics is "detected", but it does not work.
Most likely for your
Date:Fri, 16 Jun 2017 09:37:04 +0530
From:Mayuresh
Message-ID: <20170616040704.ga18...@warunjikardental.com>
| For x11, Linux sources simply mean xorg.
Perhaps, but it is not impossible that they are doing something to it
as part of device setup
On Thu, Jun 15, 2017 at 08:11:06PM +0530, Mayuresh wrote:
> On Thu, Jun 15, 2017 at 11:05:20AM +0200, Manuel Bouyer wrote:
> > It's probably a newer synaptics hardware, which may need a different code.
> > It needs to be looked at.
> > BTW the code is in src/sys/dev/pckbport/, look at pms* and
23 matches
Mail list logo