Re: Help contacting Richard Stallman
2010/5/26 Brad Tilley : > Julian Acosta wrote: > >> Really we need to contact with Richard Stallman, just for give us his >> opinion and answer us some questions about free software, >> How can I contact him? >> What's his real email? > > Just talk a lot about open source and the Linux operating system. He'll > show up. Now he'll definitely come here, because you wrote "Linux" instead" of religiously correct "GNU/Linux".
Re: 4.7 pf: quick and rdr-to/nat-to
2010/5/24 Rene Maroufi : > On Sun, May 23, 2010 at 08:07:38PM +0200, Henning Brauer wrote: >> * Rene Maroufi [2010-05-23 14:04]: >> > Hi, >> > >> > i update my firewall to 4.7 and changed my rdr and nat rules. But there >> > is one thing i don't understand: I use a transparent proxy (Squid) on >> > the same machine and in pf.conf this rdr-rule: >> > >> > pass in quick on $ifklan proto tcp from $klan to ! port 80 >> > rdr-to 127.0.0.1 port 3128 >> > >> > This works fine. If I comment this rule out, traffic is blocked. Thats >> > OK. If i remove only the "quick" word, traffic is passed through the >> > firewall without being proxied. But there is no other rule after this >> > rule to let traffic through the firewall. If there was a other rule, >> > comment this rule out, can't stop the traffic. I don't understand this >> > behaviour. >> >> well, there HAS to be another rule that matches later, or this would >> not happen. > > If thats the case: Why the traffic is blocked if i comment the rule out? > > Its blocked if i comment the rule out, but its passed without redirect > if i remove the quick. That makes no sense! Then maybe, you'll show us output of: 1. cat /etc/pf.conf 2. pfctl -f /etc/pf.conf && pfctl -sr 3. pfctl -o none -f /etc/pf.conf && pfctl -sr huh?
Re: OpenBSD 4.6 release Oct 28, 2009
2009/10/18 Theo de Raadt : > Many people have received their 4.6 CDs in the mail by now, and we > really don't want them to be without the full package repository. > Oct 18, 2009. > > We are pleased to announce the official release of OpenBSD 4.6. > This is our 26th release on CD-ROM (and 27th via FTP). B We remain > proud of OpenBSD's record of more than ten years with only two remote > holes in the default install. And thank you very much for this cool present on my daughter's first birthday! ;)
Re: X60 Tablet Wacom, Atheros 5213 & others
15 April 2008 P3. 06:16:58 Vadim Jukov wrote: > Also I bought D-Link DWL-AG530 for desktop PC, because someone said > (cannot discover that letter now:( ) it's Atheros 5212-based, which is > supported. Damned me, I messed up ral(4) and ath(4) in my mind, and > bought a card from a manufacturer which do not support OpenBSD... :( > And I run in a problem that either man in the letter made a typo (530 > instead 520), or D-Link "slightly" changed chip. Novadays it's based > on 5213, which fails to initialize or doesn't work either. Sample > dmesg output (from different boots): > > ath0 at pci0 dev 11 function 0 "Atheros AR5413" rev 0x01: irq 11 > ath0: AR5413 10.5 phy 6.1 rf 6.3, FCC2A*, address 00:1c:f0:19:aa:66 > ath0: ath_chan_set: unable to reset channel 52 (5260 MHz) > ath0: unable to reset hardware; hal status 3618911128 > ath0: unable to reset hardware; hal status 3520943048 > ath0: unable to reset hardware; hal status 3520945608 > ath0: unable to reset hardware; hal status 3520946120 > ath0: unable to reset hardware; hal status 0 > ath0: unable to reset hardware; hal status 3485396992 > ath0: unable to reset hardware; hal status 0 > ath0: unable to reset hardware; hal status 3618274072 > --- > ath0 at pci0 dev 11 function 0 "Atheros AR5213 (D-Link DWL-AG530)" rev > 0x01: irq 11 ath0: unable to attach hardware; HAL status 22 > --- > ath0 at pci0 dev 11 function 0 "Atheros AR5413" rev 0x01: irq 11 > ath0: AR5413 10.5 phy 6.1 rf 6.3, FCC2A*, address 00:1c:f0:19:aa:66 > ath0: bogus xmit rate 0x0 (idx 0x7) > ath0: bogus xmit rate 0x0 (idx 0x7) > ath0: bogus xmit rate 0x0 (idx 0x7) > > When I played with this card and driver, forcing detecting it as 5212 > (second sample output), I saw message saying "failed to resume the > AR5212 (again)", see sys/dev/ic/ar5212.c line 334 (I played with > incrementing loop count and sleep time there, without luck). Do not > remember HAL status though, but it was consistent; may try again of > course if it's needed. > > A few minutes ago, while I was writing this, it freezed (no panic) > whole PC after a few "ifconfig ath0 media xxx" and "ifconfig ath0" > commands. I have no AP around there, so I cannot ever say, does it > work in BSS mode, but in hostap mode it doesn't (even when status is > "active"). But I'm newbie in Wi-Fi at all, maybe I missed something... Now I can "reliable" call a freeze or panic: boot> boot -s <...> # cd /etc # sh netstart ath0 # ^D <...> starting network... One of the panic (not from a GENERIC kernel (I tried 2: month-old and one build a few hours ago), they still just freeze, and I have stopped experiments now) is at the end of letter. Also on madwifi.org I discovered that D-Link really changed chip in A4 or A5 h/w revision (I have A6), from AR5212 to AR5213. Currently I'm trying to find a replace for this card (AR5212-based at least)... -- Best wishes, Vadim Zhukov (written by hand) ddb> trace Debugger(d1a0,de8d1960,d19ff030,4,1) at Debugger+0x4 panic(d07273ad,d072748c,7,2,d7b7df00) at panic+0x63 ieee80211_set_link_state(d19ff030,4,,919f7) at ieee80211_set_link_state ath_newstate(d19ff030,4,,0064,de9eae60) at ath_newstate+0x181 ieee80211_create_ibss(d19ff030,d19ff2ea,d0202262,d0,7f51e754) at ieee80211_create_ibss+0x11b ieee80211_end_scan(d19ff030,d0388db6,d1a1d2c0,de9eaed8) at ieee80211_end_scan_0x21e ath_next_scan(d19ff000,beaebe58,5305bdc4,0,0) at ath_next_scan+0x3d softclock(58,10,10,10,d7bd12b0) at softclock+0x22c Bad frame pointer: 0xde9eaef8 ddb> ps PID PPID PGRPUID S FLAGS WAITCOMMAND 29743 12849 12849 0 3 0x4002 biowait perl 23968 29279 29279 83 3 0x180 pollntpd 23968 29279 1 0 3 0x80 pollntpd 18665 1 18665 0 3 0x80 pollrpc.lock 28214 31308 31308 0 3 0x80 nfsdnfsd 25324 31308 31308 0 3 0x80 nfsdnfsd 265 31308 31308 0 3 0x80 nfsdnfsd 30325 31308 31308 0 3 0x80 nfsdnfsd 31308 1 31308 0 3 0x80 netcon nfsd 28807 1 28807 0 3 0x80 select mountd 24743 19443 19443 68 3 0x180 select isakmpd 12187 1 12187 28 3 0x180 pollportmap 19443 1 19443 0 3 0x80 netio isakmpd 21435 10256 10256 70 3 0x180 select named 10256 1 10256 0 3 0x180 netio named 27148 2629 2629 74 3 0x180 bpf pflogd 2629 1 2629 0 3 0x80 netio pflogd 6598 12385 12385 73 3 0x180 pollsyslogd 12385 1 12385 0 3
X60 Tablet Wacom, Atheros 5213 & others
Hello all.
A few days ago finally I almost fell-in-love - got ThinkPad X60 Tablet.
WinXP partition resized to 15GB, OpenBSD installed... And here we begin:
- GENERIC and GENERIC.MP work OK (Opera still crashes on MP as usual...
well, my hopes belong to gnash today).
- All network works fine (but Wi-Fi tested lightly, see below).
- BlueTooth (after customizing kernel and installing bluetooth-tools)
works OK, tested many times.
- azalia(4) playing works OK, both internal and extrnal (hardware mixer,
if it's matter); recording not tested yet.
- Power Management works except suspend/sleep. I'm suspecting it's
related to that:
ichpcib0 at pci0 dev 31 function 0 "Intel 82801GBM LPC" rev 0x02: PM disabled
- Keyboard and pseudomouse:) work OK.
- Pen doesn't work at all. Windows say it's connected to the LPC chip
mentioned above. Does this mean that I have to write a driver for it
(and modify wscons framework to support touch strength, and then modify
Xorg wscons driver, BTW removing usbtablet(4))? Looks like nice effort
for me, but'll take a lot of time...
- Buttons near display (are actual in the tablet mode) do not work
either. Windows says they're connected in parallel to pen device.
- sysutils/tpb works OK.
- sysutils/tphdisk not tested (and unlikely to be until Windows finally
gone from this laptop).
- external video not tested yet.
- USB works OK (tested with ubt(4) and umass(4)).
- cardbus(4) not tested.
- FireWire and finger scanner are not supported and do not work either.
BTW, does anyone have any docs for the last one (see dmesg for more
info)?
- No kernel panics discovered. :)
Also I bought D-Link DWL-AG530 for desktop PC, because someone said
(cannot discover that letter now:( ) it's Atheros 5212-based, which is
supported. Damned me, I messed up ral(4) and ath(4) in my mind, and
bought a card from a manufacturer which do not support OpenBSD... :( And
I run in a problem that either man in the letter made a typo (530
instead 520), or D-Link "slightly" changed chip. Novadays it's based on
5213, which fails to initialize or doesn't work either. Sample dmesg
output (from different boots):
ath0 at pci0 dev 11 function 0 "Atheros AR5413" rev 0x01: irq 11
ath0: AR5413 10.5 phy 6.1 rf 6.3, FCC2A*, address 00:1c:f0:19:aa:66
ath0: ath_chan_set: unable to reset channel 52 (5260 MHz)
ath0: unable to reset hardware; hal status 3618911128
ath0: unable to reset hardware; hal status 3520943048
ath0: unable to reset hardware; hal status 3520945608
ath0: unable to reset hardware; hal status 3520946120
ath0: unable to reset hardware; hal status 0
ath0: unable to reset hardware; hal status 3485396992
ath0: unable to reset hardware; hal status 0
ath0: unable to reset hardware; hal status 3618274072
---
ath0 at pci0 dev 11 function 0 "Atheros AR5213 (D-Link DWL-AG530)" rev 0x01:
irq 11
ath0: unable to attach hardware; HAL status 22
---
ath0 at pci0 dev 11 function 0 "Atheros AR5413" rev 0x01: irq 11
ath0: AR5413 10.5 phy 6.1 rf 6.3, FCC2A*, address 00:1c:f0:19:aa:66
ath0: bogus xmit rate 0x0 (idx 0x7)
ath0: bogus xmit rate 0x0 (idx 0x7)
ath0: bogus xmit rate 0x0 (idx 0x7)
When I played with this card and driver, forcing detecting it as 5212
(second sample output), I saw message saying "failed to resume the
AR5212 (again)", see sys/dev/ic/ar5212.c line 334 (I played with
incrementing loop count and sleep time there, without luck). Do not
remember HAL status though, but it was consistent; may try again of
course if it's needed.
A few minutes ago, while I was writing this, it freezed (no panic) whole
PC after a few "ifconfig ath0 media xxx" and "ifconfig ath0" commands. I
have no AP around there, so I cannot ever say, does it work in BSS mode,
but in hostap mode it doesn't (even when status is "active"). But I'm
newbie in Wi-Fi at all, maybe I missed something...
So, now I want to fix problems mentioned above (no pen, no pen-around
buttons, no suspend/resume, no ath(4)), and I can dig somethere - if
anyone could give a direction. Direction (or something more:) ) will be
very appreciated, and I hope I'll can really help the project (and
myself :) ).
(X60 dmesg below, didn't sent to www@ until I got situation clear; not
a GENERIC because BlueTooth needed, also enabled ACPI_VERBOSE and
NTFS options).
--
Best wishes,
Vadim Zhukov
OpenBSD 4.3-current (GD.MP) #0: Wed Apr 9 22:19:14 MSD 2008
[EMAIL PROTECTED]:/usr/src/sys/arch/i386/compile/GD.MP
cpu0: Intel(R) Core(TM) Duo CPU L2500 @ 1.83GHz ("GenuineIntel" 686-class) 1.83
GHz
cpu0:
FPU,V86,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,CFLUSH,DS,ACPI,MMX,FXSR,SSE,SSE2,SS,HTT,TM,SBF,SSE3,MWAIT,VMX,EST,TM2,xTPR
real mem = 1063677952 (1014MB)
avail mem = 1020264448 (973MB)
mainbus0 at root
bios0 at mainbus0: AT/286+ BIOS, date 04/18/07, BIOS32 rev. 0 @ 0xfd690, SMBIOS
rev. 2.4 @ 0xe0010 (64
entries)
bios0: vendor LENOVO version "7JET23WW (1.08 )" date 04/18/2007
bios0: LENOVO 636464G
acpi0 at bios
Re: ssh or sudo echoing password
2008/3/23, Alexey Vatchenko <[EMAIL PROTECTED]>: > 2008-03-22, Lars Noodin <[EMAIL PROTECTED]> wrote: > > When I use ssh to run sudo on a remote host, the password for sudo gets > > echoed to the screen. e.g. > > > > # ssh -l kodos 10.101.101.01 "sudo ls /" > > [EMAIL PROTECTED]'s password: > > Password:0hNoesICit > > For such things use `ssh -t` "-tt" is better, especially in shell scripts. P.S.: Sorry for previous private mail.
Re: [i386/Thinkpad T41]USB mouse + Xorg obsd 4.1
B qnnayemhh nr Ormhv` 02 mnap 2007 Mark Thomas m`ohq`k(a): > On Nov 1, 2007 6:30 PM, Vadim Jukov <[EMAIL PROTECTED]> wrote: > > The only one InputDevice section you need: > > > > Section "InputDevice" > > Identifier "Mouse1" > > Driver "mouse" > > Option "Protocol" "wsmouse" > > Option "Device" "/dev/wsmouse" > > Option "ZAxisMapping" "4 5 6 7" > > EndSection > > > > Then, in ServerLayout section you put only one string: > > > > InputDevice "Mouse1" "CorePointer" > > > > Greg is right: that's all what you need on OpenBSD.:) Put in more > > mice or get them out, your X doesn't have to bother about this. In > > very rare cases, at least on x86 architecture PCs, you will need to > > control mouse handling per device. > > I remember reading something just like a few weeks ago when I was > investigating what laptop hardware worked best with OpenBSD. It > basically said "OpenBSD just works!" > > Thanks for your time Vadim but it's still not working. > > Here again is the relevant part of my xorg.conf file > > Section "ServerLayout" > Identifier "X.org Configured" > Screen 0 "Screen0" 0 0 > InputDevice"Mouse0" "CorePointer" > InputDevice"Keyboard0" "CoreKeyboard" > EndSection > > Section "InputDevice" > Identifier "Mouse0" > Driver "mouse" > Option "Protocol" "wsmouse" > Option "Device" "/dev/wsmouse" > Option "ZAxisMapping" "4 5 6 7" > EndSection Hmmm, looks sane. Run xev(1) application (inside X, of course) and see, does it generate anything when you try to move/click/scroll while pointer is positioned in it's window. Post what you see: no reaction on second mouse touching, or sample of messages it generates. Also, please, run "usbdevs -v" and post output lines here. And last but not least: try to rename/move xorg.conf and start X without it. Does this help? -- Best wishes, Vadim Jukov
Re: [i386/Thinkpad T41]USB mouse + Xorg obsd 4.1
B qnnayemhh nr Werbepc 01 mnap 2007 Mark Thomas m`ohq`k(a): > On Oct 31, 2007 9:47 PM, Vadim Jukov <[EMAIL PROTECTED]> wrote: > > You need only one "InputDevice" section for all your mice with > > "/dev/wsmouse" as "Device" option, indeed. > > I'm sorry but I do not understand. I tried putting both mice in one > InputDevice section and X refused to start. > > Parse error on line 47 of section InputDevice in file > /etc/X11/xorg.conf Multiple "Identifier" lines. > (EE) Problem parsing the config file > (EE) Error parsing the config file > > Thanks again The only one InputDevice section you need: Section "InputDevice" Identifier "Mouse1" Driver "mouse" Option "Protocol" "wsmouse" Option "Device" "/dev/wsmouse" Option "ZAxisMapping" "4 5 6 7" EndSection Then, in ServerLayout section you put only one string: InputDevice "Mouse1" "CorePointer" Greg is right: that's all what you need on OpenBSD.:) Put in more mice or get them out, your X doesn't have to bother about this. In very rare cases, at least on x86 architecture PCs, you will need to control mouse handling per device. -- Best wishes, Vadim Jukov
Re: [i386/Thinkpad T41]USB mouse + Xorg obsd 4.1
2007/11/1, Mark Thomas <[EMAIL PROTECTED]>: > On Oct 31, 2007 9:13 PM, Vadim Jukov <[EMAIL PROTECTED]> wrote: > > > > Missing option "SendCoreEvents" for wsmouse1. And why don't use > > /dev/wsmouse, which is "cumulative" device for all mice? > > > > Thanks Vadim. I changed my xorg.conf to reflect your advise. But still > no usb mouse activity. I did get an error though. > > Section "InputDevice" > Identifier "Mouse0" > Driver "mouse" > Option "Protocol" "wsmouse" > Option "Device" "/dev/wsmouse" > Option "ZAxisMapping" "4 5 6 7" > Option "AlwaysCore" "true" > EndSection > > Section "InputDevice" > Identifier "Mouse1" > Driver "mouse" > Option "Protocol" "wsmouse" > Option "Device" "/dev/wsmouse" > Option "ZAxisMapping" "4 5" > Option "SendCoreEvents" "true" > EndSection > > (II) XINPUT: Adding extended input device "Keyboard0" (type: KEYBOARD) > (II) XINPUT: Adding extended input device "Mouse1" (type: MOUSE) > (II) XINPUT: Adding extended input device "Mouse0" (type: MOUSE) > (EE) xf86OpenSerial: Cannot open device /dev/wsmouse > Device busy. > (WW) Mouse1: cannot open input device > > thanks again for your help. You need only one "InputDevice" section for all your mice with "/dev/wsmouse" as "Device" option, indeed.
Re: [i386/Thinkpad T41]USB mouse + Xorg obsd 4.1
2007/11/1, Mark Thomas <[EMAIL PROTECTED]>: > On Oct 28, 2007 9:46 AM, Mark Thomas <[EMAIL PROTECTED]> wrote: > > I'm trying to get a USB mouse to work in X. obsd 4.1 recognizes the > > mouse as soon as I plug it in ( see dmesg output below ) as > > wsmouse1(?). When I add that as Mouse1 in the xorg.conf file it does > > not work. everything else works great! > > > > ( relevant dmesg output ) > > uhidev0 at uhub1 port 2 configuration 1 interface 0 > > uhidev0: Microsoft Microsoft Optical Mouse with Tilt Wheel, rev > > 2.00/1.20, addr 2, iclass 3/1 > > uhidev0: 24 report ids > > ums0 at uhidev0 reportid 17: 3 buttons and Z dir. > > wsmouse1 at ums0 mux 0 > > uhid0 at uhidev0 reportid 18: input=0, output=0, feature=1 > > uhid1 at uhidev0 reportid 19: input=1, output=0, feature=0 > > uhid2 at uhidev0 reportid 23: input=0, output=0, feature=1 > > uhid3 at uhidev0 reportid 24: input=0, output=0, feature=1 > > > > ( xorg.conf / InputDevice section) > > Section "InputDevice" > > Identifier "Mouse0" > > Driver "mouse" > > Option "Protocol" "wsmouse" > > Option "Device" "/dev/wsmouse" > > Option "ZAxisMapping" "4 5 6 7" > > EndSection > > > > Section "InputDevice" > > Identifier "Mouse1" > > Driver "mouse" > > Option "Protocol" "wsmouse" > > Option "Device" "/dev/wsmouse1" > > Option "ZAxisMapping" "4 5" > > EndSection > > > > still no luck but I do know a lot more about Xorg! After > searching/reading for a few says I've added the following to my > xorg.conf. > > Section "ServerLayout" > Identifier "X.org Configured" > Screen 0 "Screen0" 0 0 > InputDevice"Mouse0" "CorePointer" > InputDevice"Mouse1" > InputDevice"Keyboard0" "CoreKeyboard" > EndSection > > Section "InputDevice" > Identifier "Mouse0" > Driver "mouse" > Option "Protocol" "wsmouse" > Option "Device" "/dev/wsmouse0" > Option "ZAxisMapping" "4 5 6 7" > Option "AlwaysCore" "true" > EndSection > > Section "InputDevice" > Identifier "Mouse1" > Driver "mouse" > Option "Protocol" "wsmouse" > Option "Device" "/dev/wsmouse1" > Option "ZAxisMapping" "4 5" > EndSection Missing option "SendCoreEvents" for wsmouse1. And why don't use /dev/wsmouse, which is "cumulative" device for all mice?
Re: Microsoft Wireless Intellimouse support, take 2
2007/10/19, Vadim Jukov <[EMAIL PROTECTED]>:
> After digging in Linux HUD driver and checking again usbhidctl output, I
> realized that sometimes (and looks like in my case too) the wheel is
> represented by HID consumer "AC Pan" device. But when I just simply add
> test for this device in attach function, it doesn't work (no panic,
> just "me is not there"). I'll send extended version of your diff (which
> also tests for HUG_RZ, not only HUG_Z) later, when I'll be fully stuck
> or found solution.
Oh, how stupid I was... :(
Shortly, this modified version of your diff makes my mouse behave
absolutely correct.
I decided to not hardcode Z axis position, so it is detected as next
to sc_loc_y, same size.
(I hope that GMail will not corrupt diff, but if it'll, I'll send it
in a new thread, sorry)
--
Best wishes,
Vadim Jukov
Index: dev/usb/ums.c
===
RCS file: /cvs/src/sys/dev/usb/ums.c,v
retrieving revision 1.26
diff -u -u -r1.26 ums.c
--- dev/usb/ums.c 17 Sep 2007 01:40:38 - 1.26
+++ dev/usb/ums.c 20 Oct 2007 08:32:13 -
@@ -80,11 +80,6 @@
#define UMSUNIT(s) (minor(s))
-#define PS2LBUTMASKx01
-#define PS2RBUTMASKx02
-#define PS2MBUTMASKx04
-#define PS2BUTMASK 0x0f
-
#define MAX_BUTTONS16 /* must not exceed size of sc_buttons */
struct ums_softc {
@@ -96,9 +91,13 @@
int sc_enabled;
int flags; /* device configuration */
-#define UMS_Z 0x01/* z direction available */
-#define UMS_SPUR_BUT_UP0x02/* spurious button up events */
-#define UMS_REVZ 0x04/* Z-axis is reversed */
+#define UMS_Z 0x01/* z direction available */
+#define UMS_SPUR_BUT_UP0x02/* spurious button up
events */
+#define UMS_REVZ 0x04/* Z-axis is reversed */
+#define UMS_W 0x08/* w direction available */
+#define UMS_REVW 0x10/* W-axis is reversed */
+#define UMS_LEADINGBYTE0x20/* Unknown leading byte
*/
+#define UMS_IGNORE_WHEEL_BUTTONS 0x40/* Ignore buttons 4 and 5 */
int nbuttons;
@@ -166,7 +165,7 @@
int size;
void *desc;
u_int32_t flags, quirks;
- int i;
+ int i, wheel, twheel;
struct hid_location loc_btn;
sc->sc_hdev.sc_intr = ums_intr;
@@ -178,6 +177,8 @@
sc->flags |= UMS_REVZ;
if (quirks & UQ_SPUR_BUT_UP)
sc->flags |= UMS_SPUR_BUT_UP;
+ if (quirks & UQ_MS_LEADING_BYTE)
+ sc->flags |= UMS_LEADINGBYTE;
uhidev_get_report_desc(uha->parent, &desc, &size);
@@ -205,9 +206,22 @@
return;
}
- /* Try the wheel as Z activator first */
- if (hid_locate(desc, size, HID_USAGE2(HUP_GENERIC_DESKTOP, HUG_WHEEL),
- uha->reportid, hid_input, &sc->sc_loc_z, &flags)) {
+ /*
+* Try to guess the Z activator: check WHEEL, TWHEEL, and Z,
+* in that order.
+*/
+
+ wheel = hid_locate(desc, size,
+ HID_USAGE2(HUP_GENERIC_DESKTOP, HUG_WHEEL),
+ uha->reportid, hid_input, &sc->sc_loc_z, &flags);
+ if (wheel == 0)
+ twheel = hid_locate(desc, size,
+ HID_USAGE2(HUP_GENERIC_DESKTOP, HUG_TWHEEL),
+ uha->reportid, hid_input, &sc->sc_loc_z, &flags);
+ else
+ twheel = 0;
+
+ if (wheel || twheel) {
if ((flags & MOUSE_FLAGS_MASK) != MOUSE_FLAGS) {
DPRINTF(("\n%s: Wheel report 0x%04x not supported\n",
sc->sc_hdev.sc_dev.dv_xname, flags));
@@ -230,6 +244,8 @@
/* Bad Z coord, ignore it */
sc->sc_loc_w.size = 0;
}
+ else
+ sc->flags |= UMS_W;
}
} else if (hid_locate(desc, size,
HID_USAGE2(HUP_GENERIC_DESKTOP, HUG_Z),
@@ -243,6 +259,21 @@
}
}
+ /*
+* The Microsoft Wireless Intellimouse 2.0 reports its wheel
+* using 0x0048 (I've called it HUG_TWHEEL) and seems to expect
+* us to know that the byte after the wheel is the tilt axis.
+* There are no other HID axis descriptors other than X, Y and
+* TWHEEL, so we report TWHEEL on the W axis.
+*/
+ if (twheel) {
+ sc->sc_loc_w = sc->sc_loc_z;
+ sc->sc_loc_w.pos = sc->sc_loc_w.pos + 8;
+ sc->flags |= UMS_W | UMS_LEADINGBYTE;
+ /* Wheels need their axis reversed. */
+ sc->flags ^= U
Re: Wireless USB mouse problem
It's not very important, of course...
--
Best wishes,
Vadim Jukov
Index: ums.c
===
RCS file: /cvs/src/sys/dev/usb/ums.c,v
retrieving revision 1.26
diff -u -r1.26 ums.c
--- ums.c 17 Sep 2007 01:40:38 - 1.26
+++ ums.c 18 Oct 2007 01:45:23 -
@@ -80,11 +80,6 @@
#define UMSUNIT(s) (minor(s))
-#define PS2LBUTMASKx01
-#define PS2RBUTMASKx02
-#define PS2MBUTMASKx04
-#define PS2BUTMASK 0x0f
-
#define MAX_BUTTONS16 /* must not exceed size of sc_buttons */
struct ums_softc {
Re: Wireless USB mouse problem
2007/10/18, Miod Vallat <[EMAIL PROTECTED]>: > > Due to different reasons I bought MS Wireless Desktop (keyboard + > > mouse; Well, I don't like very much of their software, but AFAIK > > their hardware is good enough). While keyboard works fine, mouse > > produces headache. I'll try to skip most of simptoms, going > > straight to information gathered. > > This mouse is currently not correctly supported by OpenBSD. I am working > on porting FreeBSD's changes to support it (FreeBSD PR #90162); will you > be interested in testing these changes? Of course! :)
Re: Wireless ImtelliMouse problem
P QP>P>P1QP5P=P8P8 P>Q Wednesday 17 October 2007 Vadim Jukov P=P0P?P8QP0P;(a): > Even more: when I try to move objects like scrollbars by > dragging using any mouse button, they began to move up, like > mouse wheel tell is being scrolled. Sorry, I'm bit asleep now, so said something wrong. Scrollbars works OK after using xmseconfig(1), but when I, for example, try to select text in the terminal client, it begins to move selection upper and upper. No crashes still (yet?). And xmseconfig(1) says following right after startup (when mouse first time enters it's window): "Error in Tcl Script" "Error: invalid command name "tk::ScreenChanged" A copy of stack trace has been saved in the file /tmp/X.err If you think this error has not been reported before " X differs on each run, of course. Stack trace consists following: invalid command name "tk::ScreenChanged" while executing "tk::ScreenChanged :0.0" (changing screen in event binding) -- Best wishes, Vadim Jukov
Wireless ImtelliMouse problem
Hello all.
Due to different reasons I bought MS Wireless Desktop (keyboard + mouse).
While keyboard works fine, mouse produces headache. I'll skip simptoms,
going straight to information gathered.
I tried to used new mouse both alone and with Logitech UltraX Optical
in pair. Logitech works OK in both cases (it suffers from, err,
"hardware problems":), which were the reasons to buy new mouse).
IntelliMouse going wrong in both cases too.
Snip from dmesg (full version later):
uhidev0 at uhub1 port 1 configuration 1 interface 0 "Logitech USB-PS/2 Optical
Mouse" rev 2.00/20.00 addr 2
uhidev0: iclass 3/1
ums0 at uhidev0: 4 buttons and Z dir.
wsmouse0 at ums0 mux 0
uhidev1 at uhub1 port 2 configuration 1 interface 0 "Microsoft Microsoft
Wireless Optical Desktop\M-. 2.10" rev 2.00/0.41 addr 3
uhidev1: iclass 3/1
ukbd0 at uhidev1: 8 modifier keys, 6 key codes
wskbd1 at ukbd0 mux 1
wskbd1: connecting to wsdisplay0
uhidev2 at uhub1 port 2 configuration 1 interface 1 "Microsoft Microsoft
Wireless Optical Desktop\M-. 2.10" rev 2.00/0.41 addr 3
uhidev2: iclass 3/0
uhidev2: 23 report ids
uhid0 at uhidev2 reportid 1: input=7, output=0, feature=0
uhid1 at uhidev2 reportid 2: input=2, output=0, feature=0
uhid2 at uhidev2 reportid 3: input=1, output=0, feature=0
uhid3 at uhidev2 reportid 4: input=1, output=0, feature=0
uhid4 at uhidev2 reportid 5: input=3, output=0, feature=0
uhid5 at uhidev2 reportid 6: input=0, output=0, feature=1
ums1 at uhidev2 reportid 17: 5 buttons and Z dir.
wsmouse1 at ums1 mux 0
uhid6 at uhidev2 reportid 18: input=0, output=0, feature=1
uhid7 at uhidev2 reportid 19: input=1, output=0, feature=0
uhid8 at uhidev2 reportid 20: input=1, output=0, feature=0
uhid9 at uhidev2 reportid 21: input=3, output=0, feature=0
uhid10 at uhidev2 reportid 23: input=0, output=0, feature=1
xev(1) output for mouse clicks are different: while Logitech
produces single "mouse down" and "mouse release" events as
it should, IntelliMouse produces "mouse down" and "mouse up"
on each move too, which yields many strange things. I can send
exact logs (enter window, mouse move, mouse down, mouse move,
mouse up, mouse move, exit window) if anyone is interested in
them.
One more thing: xmseconfig(1) tells me that X server doesn't
handle "Protocol" option in xorg.conf, always setting it to
"microsoft" instead of "wsmouse" (or, at least, "intellimouse",
which is compatible, instead of "microsoft"). After reverting
protocol to something more closer to reality, some bugs
disappear, but xev(1) still says there are "mouse down" and
"mouse release" events on each move with pressed button.
Even more: when I try to move objects like scrollbars by
dragging using any mouse button, they began to move up, like
mouse wheel tell is being scrolled.
But mouse wheel doesn't work. At all. It worked many days,
and some days ago it sopped working. I thought that was due
to "hardware problems" (some juice over it) with Logitech
mouse, and I went to buy new mouse... And now I'm stuck.
It's more likely OpenBSD-related problem because all is OK on
a fresh (Mandriva 2008.0) Linux distribution which I pulled in.
Today I'm going to test this mouse on another OpenBSD machine,
which is CURRENT too. If I'll find something more than I'll
post it here, of course.
Thank you for any tips.
--
Best wishes,
Vadim Jukov
OpenBSD 4.2-current (GENERIC) #431: Sun Oct 14 22:00:04 MDT 2007
[EMAIL PROTECTED]:/usr/src/sys/arch/i386/compile/GENERIC
cpu0: AMD Sempron(tm) Processor 2600+ ("AuthenticAMD" 686-class, 128KB L2
cache) 1.61 GHz
cpu0:
FPU,V86,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,CFLUSH,MMX,FXSR,SSE,SSE2,SSE3
cpu0: AMD erratum 89 present, BIOS upgrade may be required
real mem = 1072459776 (1022MB)
avail mem = 1029238784 (981MB)
mainbus0 at root
bios0 at mainbus0: AT/286+ BIOS, date 06/28/05, BIOS32 rev. 0 @ 0xf0010, SMBIOS
rev. 2.3 @ 0xf0530 (55 entries)
bios0: vendor American Megatrends Inc. version "1008.013" date
06/28/2005
bios0: ASUSTeK Computer Inc. K8V-MX
apm0 at bios0: Power Management spec V1.2
apm0: AC on, battery charge unknown
apm0: flags 30102 dobusy 0 doidle 1
pcibios0 at bios0: rev 2.1 @ 0xf/0x1
pcibios0: PCI IRQ Routing Table rev 1.0 @ 0xf58a0/224 (12 entries)
pcibios0: PCI Interrupt Router at 000:17:0 ("VIA VT8237 ISA" rev 0x00)
pcibios0: PCI bus #1 is the last bus
bios0: ROM list: 0xc/0xd000 0xcd000/0x2000
cpu0 at mainbus0
pci0 at mainbus0 bus 0: configuration mode 1 (no bios)
pchb0 at pci0 dev 0 function 0 "VIA K8M800 Host" rev 0x00
pchb1 at pci0 dev 0 function 1 "VIA K8M800 Host" rev 0x00
pchb2 at pci0 dev 0 function 2 "VIA K8M800 Host" rev 0x00
pchb3 at pci0 dev 0 function 3 "VIA K8M800 Host" rev 0x00
Re: Strange Lock-ups with Opera?
2007/9/12, Antoine Jacoutot <[EMAIL PROTECTED]>: > On Wednesday 12 September 2007 08:41:26 Greg Thomas wrote: > > I don't have much to add other than I experience the same thing with > > many Flash sites. > > Same here only it does not happen only with flash sites. > Sometimes, just starting opera and going to google.com is enough to hang... > Never looked into it... I have this problem on my dual PIII-550 system, but only in dual-CPU mode. When only one CPU is enabled, Opera surfs like a charm... Looks like there are more problems with shared memory, but I'm unsure.
Ответ: other languages support?
http://www.openbsd.ru/ 2006/6/1, akonsu <[EMAIL PROTECTED]>: Hello, is there a way to install several languages on one system? say, if i have an english system, is there a way to add cyrillic to it and switch between the two languages when typing? thanks for any pointers! konstantin
