via dri ?
Has anybody VIA CLE266 integrated video card? If any - have you set up direct rendering with it? ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Can not compile kernel.
Grant Wagner [EMAIL PROTECTED] wrote: Now I have a custom kernel which is failing to build. I've attached the config file for it, and it fails trying to build with references about ieee80211. The odd thing is I have no wireless in my box and have commented out all the wireless references. What else is dependant on them and should be commented out as well? The last bit of output is below. if_ural.o(.text+0xe5): In function `ural_next_scan': : undefined reference to `ieee80211_next_scan' *** Error code 1 Stop in /usr/obj/usr/src/sys/STRIPPED. *** Error code 1 Stop in /usr/src. *** Error code 1 Remove 'device ural' from your kernel config. file. Ural is a driver for wireless adapters and depends on 'device wlan' which is commented in your conf. file. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Pentium 3 Clock Frequency Control
FK [EMAIL PROTECTED] wrote: Is it posible to control Pentium 3 clock frequency on FreeBSD? The purpose is to reduce the power consumption and lengthen battery life. In addition, how can we know what speed of cpu clock frequecy a cpu supports and what speed a cpu take at any given time? I suppose that a command which returns each information exist. Well, a couple years ago I patched to, if I remember correctly, 5.4 kernel and it made this need possible at least on Pentium M. I tried to find the web page but I failed. I am using FreeBSD6.0-RELEASE now. Look at http://lists.freebsd.org/pipermail/freebsd-acpi/2005-March/001346.html Hope it helps. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: What is my TFTP Server Soing
Joshua Lewis [EMAIL PROTECTED] wrote: I am trying to figure out what my device is doing when connecting to my TFTP server. Is there a way to watch on my server what the TFTP server is doing? try tcpdump ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: brand new server timing out for sshd connections
Jonathan Horne [EMAIL PROTECTED] wrote: btw, is there a way i can try to send my tcp packets to a specific mac address? i know the mac of my target server, if i could get it to talk back to me, i could net/arping can help you in this ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: HP Embedded SATA RAID controller (FreeBSD 6.2)
George Vanev [EMAIL PROTECTED] wrote: AHA-3985 is SCSI controller. The one I have is SATA. Yes, I'm sure that it's Adaptec, but what is the model?! If FreeBSD didn't recognised it during the installation does that mean that it is incompatible with FreeBSD? Yes, I understand that AHA-3985 is SCSI HostRAID and that you've SATA one. But look at the driver for your SATA RAID for Windows. You can find in driver's files both 'SATA'/'Serial ATA' and 'SCSI' words. There is definitely 'AHA3985' string in .sys file for Windows. Maybe it was remade for SATA. Probably FreeBSD hasn't working driver for this SATA HostRAID now. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Problem with ipfw flush
In trying to tweak my firewall setup I'm using a file called
/etc/ipfw.rules
However, it seems even though I copy my rules perfectly to that file,
the system freezes up and locks me out when I do:
ipfw -f flush; ipfw /etc/ipfw.rules
I've also tried doing it as
ipfw -f flush ipfw /etc/ipfw.rules
But to no avail.
Firewall script is a common shell script. You don't need to run 'ipfw
script'.
Flushing the rules is usually done by script itself.
For example:
#!/bin/sh
ipfw=/sbin/ipfw
${ipfw} -f flush
${ipfw} rule
${ipfw} rule
${ipfw} rule
...
This file should be executable (chmod +x). You can also put any non-ipfw
additional commands in this file if you want.
Try to make such script, execute it and write again about the results.
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: HP Embedded SATA RAID controller (FreeBSD 6.2)
George Vanev [EMAIL PROTECTED] wrote: I have HP ProLiantML 110 G3 server. I am trying to install FreeBSD 6.2. But it doesn't seem to recognise the RAID controller. I don't know what exactly is the controller. In the hp site I didn't find anything usefull, except that this is HP embedded SATA RAID controller Not much, uh?! Any one could help?! Regards It's Adaptec, probably AHA-3985 - there is an appropriate string in the driver. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: 6.2 about the vlan setup
ann kok [EMAIL PROTECTED] wrote: I put the device vlan and modify and recompile the kernel. reboot the computer. uname is showing it is new kernel but I can't see the vlan interface Do you know why? See vlan(4) and ifconfig(8). Excerpt from vlan(4): Each vlan interface is created at runtime using interface cloning. This is most easily done with the ifconfig(8) create command or using the cloned_interfaces variable in rc.conf(5). So loading if_vlan / compiling into kernel isn't sufficient. Also look at http://people.freebsd.org/~arved/vlan/vlan_en.html (it's slightly outdated). ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: FreeBSD 6.2-RELEASE on Dell Optiplex 210L
Mike Barnard [EMAIL PROTECTED] wrote: if i remove the USB keyboard, all above versions of FreeBSD boot, but when i plug the keyboard back in, its not functional. i managed to get it to boot once with the keyboard plugged in, but loose it after it gets to the sysinstall part. Is everything ok with USB keyboard? Have you the same when plugged it to other boxes? Does PS/2 keyboard works well? ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: ghostscript
kalin mintchev [EMAIL PROTECTED] wrote: options screen!!! i'd love an option screen whats the command line option to ignore options?? It seems that all the ghostscript variants in ports have an options screen. Did you updated the ports? Make sure you haven't 'work' directory before running make. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Problem with ipfw flush
Dan Mahoney, System Admin [EMAIL PROTECTED] wrote: Even if I add the flush command directly to /etc/ipfw.rules, and run ipfw -f /etc/ipfw.rules right from the command line, my connection gets dropped and the rest of the commands do not run. In experimenting a bit more, I've found that I can do: nohup ipfw -f /etc/ipfw.rules This allows the rest of the ipfw command to run, but the HUP-on-disconnect still doesn't explain why the command doesn't even finish running. If I understands rightly you need -q option. ipfw(8): -q While adding, zeroing, resetlogging or flushing, be quiet about actions (implies -f). This is useful for adjusting rules by exe- cuting multiple ipfw commands in a script (e.g., `sh /etc/rc.firewall'), or by processing a file of many ipfw ^ rules across a remote login session. It also stops a table add or delete from failing if the entry already exists or is not present. If a flush is performed in normal (verbose) mode (with the default kernel configuration), it prints a message. Because all rules are flushed, the message might not be delivered to the login session, causing the remote login session to be closed and the remainder of the ruleset to not be processed. Access to the console would then be required to recover. ^^ ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
'rc.d/squid stop'
It seems Squid 2.6.6 stops strangely on my FreeBSD 6.2-PRERELEASE box. Output of '/usr/local/etc/rc.d/squid stop' Stopping squid. Waiting for PIDS: 553 564, 553 564, 553 564, 553 564, 553 564, 553 564, 553 564, 553 564, 553 564, 553 564, 553 564, 553 564, 553 564, 553 564, 553 564, 553 564 . During shutdown proccess initiated by Ctrl+Alt+Del or by ACPI power button I see the same. System says about watch-dog timer after it. Is such squid's stopping normal or not? ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: 'rc.d/squid stop'
Something strange with server. I didn't send that old message any more! ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Does 82915PM/GMS support dri???
i have a problem configuring dri support for my laptop (a celeron
1.5Ghz, with i915GM GMCH chipset and 768Mb memory).Does anyone knows
firstly if there is a support for this chipset?If so, can you please
check the glxinfo and dmesg and tell me what's wrong?
Thanks for the time.
I haven't this card but it seems that i915GM is supported.
Excerpt from /usr/src/sys/dev/drm/drm_pciids.h:
'#define i915_PCI_IDS \
{0x8086, 0x3577, 0, Intel i830M GMCH}, \
{0x8086, 0x2562, 0, Intel i845G GMCH}, \
{0x8086, 0x3582, 0, Intel i852GM/i855GM GMCH}, \
{0x8086, 0x2572, 0, Intel i865G GMCH}, \
{0x8086, 0x2582, 0, Intel i915G}, \
{0x8086, 0x2592, 0, Intel i915GM}, \
{0x8086, 0x2772, 0, Intel i945G}, \
{0x8086, 0x27A2, 0, Intel i945GM}, \
{0, 0, 0, NULL}'
Have you the following strings in kernel configuration file:
device drm
device i915drm
?
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Problem with Enabling DRI
Stevan Tiefert [EMAIL PROTECTED] wrote: (II) SIS(0): [drm] drmSetBusid failed (6, pci::01:00.0), Permission denied Driver says 'Permission denied'. Try to add the following to your xorg.conf: ' Section DRI Mode 0666 EndSection ' as written in http://people.freebsd.org/~anholt/dri/install.html. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Problem with Enabling DRI
From http://dri.freedesktop.org/wiki/DriTroubleshooting: 'If it says: [drm] drmSetBusid failed (7, PCI:1:0:0), Permission denied people have said that it's because the modules were built with a different gcc version than the kernel. Make sure they are in sync. Also, dmesg output should show something about version magic mismatches if this is the case. Another possibility (for the i915/i810 chipsets) is that you have an old buggy version of the i810 driver. Be sure to upgrade to the latest and greatest.' Maybe it will help. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
ghostscript device 'gdi'
My experience with ghoscscript device 'gdi' is that even patched it generates a correct data only for 600 dpi resolution. With -r300' option printer makes pages with large horizontal black and grey stripes. Does somebody use Samsung laser printer and ghostscript device 'gdi' for printing to it? ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: ghostscript device 'gdi'
John Nielsen [EMAIL PROTECTED] wrote: On Sunday 21 January 2007 20:07, [EMAIL PROTECTED] wrote: My experience with ghoscscript device 'gdi' is that even patched it generates a correct data only for 600 dpi resolution. With -r300' option printer makes pages with large horizontal black and grey stripes. Does somebody use Samsung laser printer and ghostscript device 'gdi' for printing to it? I have a Lexmark E210, which is basically a rebranded Samsung ML-1210. I print to it using Cups and the foomatic scripts/filters and haven't had any problems. I know it uses gs with the gdi device on the back end. I just printed a test page at 300 dpi and it looks fine. I have Samsung ML-1210 exactly, foomatic-filters-3.0.2_4, ghostscript-gnu-7.07_15. Try to print alphabet.ps from ghostscript examples with 300 dpi. For example: 'foomatic-rip --ppd path to gdi ppd -o Resolution=300x300dpi -o PageSize=A4 /usr/local/share/ghostscript/7.07/examples/alphabet.ps /dev/ulpt0'. Is page printed well? For me isn't, only ugly stripes. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Loosing Ethernet Connectivity
What about firewall and especially ipfw MAC rules? ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Disable syslogd 514..
On Thu, 18 Jan 2007 01:33:13 +0500, Agus [EMAIL PROTECTED] wrote: Hi doing a netstat -an i see that syslog is listening in UDP port 514.i am trying to disable it, but no luck i checked the rc.conf but there is nothing there.what do u recommend? to disable it or to leave it? I do not use the machine as a remote syslog server so i cant see the use.but who knows.. From syslogd(8): -s Operate in secure mode. Do not log messages from remote machines. If specified twice, no network socket will be opened at all, which also disables logging to remote machines. So 'syslogd_flags=-ss' can be added to /etc/rc.conf. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: regexp [. .]
On Wed, 17 Jan 2007 07:15:34 +0500, Parker Anderson [EMAIL PROTECTED] wrote: Is there a certain match you are trying to pattern? From the looks of it, [ch]* would match a similar set of characters, but it isn't as strict about which pattern they should be in. I need 'some[^[.pattern.]]' working, i.e. matching 'some' if it isn't followed by 'pattern'. Curiously that seems there isn't additional information about it somewhere except the page you've denoted. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
'/usr/local/etc/rc.d/squid stop' problem
It seems something strange with squid-2.6.6 on my FreeBSD 6.2-PRERELEASE box. After running 'usr/local/etc/rc.d/squid stop' (and therefore during system shutdown on 'Ctrl+Alt+Delete' or ACPI power button pushing) I see the following: Stopping squid. Waiting for PIDS: 553 564, 553 564, 553 564, 553 564, 553 564, 553 564, 553 564, 553 564, 553 564, 553 564, 553 564, 553 564, 553 564, 553 564, 553 564, 553 564. In case of shutdown /etc/rc.shutdown initiates watchdog timer. I think it isn't normal. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: '/usr/local/etc/rc.d/squid stop' problem
On Tue, 16 Jan 2007 21:51:08 +0500, Dan Nelson [EMAIL PROTECTED] wrote: Try shutting squid down manually from a shell prompt, then switch to another window/vty and take a look at /usr/local/squid/logs/cache.log . My guess is it's waiting for an active client connection to exit. The default for shutdown_lifetime in squid.conf is 30 seconds. I set it to 5 on my systems. You was right. There was 'Waiting 30 seconds for active connections to finish' in cache.log. I've made 'shutdown_lifetime 5 seconds' in squid.conf too. Squid is shutting down faster now. Thanks a lot! ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
regexp [. .]
I need to use regular expressions with a sequence of characters as a collating element. From re_format(7): Within a bracket expression, a collating element (a character, a multi- character sequence that collates as if it were a single character, or a collating-sequence name for either) enclosed in `[.' and `.]' stands for the sequence of characters of that collating element. The sequence is a single element of the bracket expression's list. A bracket expression containing a multi-character collating element can thus match more than one character, e.g. if the collating sequence includes a `ch' collating element, then the RE `[[.ch.]]*c' matches the first five characters of `chchcc'. But grep (and other programs using regexp) writes on echo somepattern | grep -Ee 'some[^[.pattern.]]': Invalid collation character. What's wrong? ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: dual duo core xeon
On Tue, 16 Jan 2007 03:58:11 +0500, kalin mintchev [EMAIL PROTECTED] wrote: can i run freebsd 6.* on a dual duo core xeon machine using full cpu capacity? does freebsd run on duo core Intels - i know it does on amds... From FAQ for FreeBSD 4.X, 5.X, and 6.X: 4.2.2. Does FreeBSD support Symmetric Multiprocessing (SMP)? Yes. SMP was enabled by default in the GENERIC kernel as of FreeBSD 5.2. The intention was also to enable it by default for the FreeBSD 5.3 release, but problems running the SMP kernel on certain UP machines led to the decision to disable it until those problems can be addressed. This is a priority for FreeBSD 5.4.' (http://www.freebsd.org/doc/en_US.ISO8859-1/books/faq/compatibility-processors.html) From FreeBSD/i386 6.2-RELEASE Hardware Notes, 2 Supported Processors and Motherboards: Almost all i386-compatible processors with a floating point unit are supported. All Intel processors beginning with the 80486 are supported, including the 80486, Pentium, Pentium Pro, Pentium II, Pentium III, Pentium 4, and variants thereof, such as the Xeon and Celeron processors. ... Symmetric multi-processor (SMP) systems are generally supported by FreeBSD, although in some cases, BIOS or motherboard bugs may generate some problems. Perusal of the archives of the FreeBSD symmetric multiprocessing mailing list may yield some clues. (http://www.freebsd.org/releases/6.2R/hardware-i386.html#PROC) ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Is it possible to have Diskless workstation in freebsd
On Tue, 16 Jan 2007 04:18:21 +0500, Dak Ghatikachalam [EMAIL PROTECTED] wrote: I have a need to setup 3 workstations to boot remotely without any ( OS) on local disks, What are ways to go about achieving that, I want the users to have all their utilities and files stores all back stored in the remote server. But confusion how the OS going to detect the correct local Hardware resources for it to run right drivers, example being the VGA driver, local keyboard and mouse. There is a 27.6 Diskless Operation paragraph in FreeBSD Handbook (http://www.freebsd.org/doc/en_US.ISO8859-1/books/handbook/network-diskless.html) and article Diskless X Server: a how to guide (http://www.freebsd.org/doc/en_US.ISO8859-1/articles/diskless-x/index.html). Maybe it helps. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Compiling mtr without GUI
--- Forwarded message --- From: [EMAIL PROTECTED] To: Christian Baer [EMAIL PROTECTED] Cc: Subject: Re: Compiling mtr without GUI Date: Tue, 16 Jan 2007 05:40:34 +0500 On Sat, 13 Jan 2007 19:03:11 +0500, Christian Baer [EMAIL PROTECTED] wrote: Somehow the mtr-port is bugging me a little. I want to install mtr on a machine with no keyboard and no monitor and thus no X - and I'd like to keep it that way. Since I couldn't find a package of mtr without the GUI, I guess, I'm stuck with the port. I've looked at the makefile and found the variable WITHOUT_X11. However, a 'make -D WITHOUT_X11' and a 'make WITHOUT_X11=1' both[1] result in X.org being downloaded and built. Now I am no real expert on makefiles but AFAIK in this case it shouldn't matter, what value WITHOUT_X11 has, as long as it is set at all. What do you see after running make? === mtr-nox11-0.72 depends on executable in : gmake - found or === mtr-0.72 depends on executable in : gmake - found ? ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: error squid when using pf
i try use pf for transparant proxy ( i get from here http://www.benzedrine.cx/transquid.html ) when i configure manual to use proxy is working fine . then i try to use pf for redirection connection to proxy : int_if=vr0 ext_if=xl0 rdr on $int_if inet proto tcp from any to any port www - 127.0.0.1 port 3128 pass in on $int_if inet proto tcp from any to 127.0.0.1 port 3128 keep state pass out on $ext_if inet proto tcp from any to any port www keep stat i always get error = Unable to determine IP address from host name for www.domain.com such like error dns but my dns resolver working fine . what should i chek squid or my pf script Maybe -D flag for squid will help (Disable initial DNS tests) ? ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
sendmail_enable in rc.conf
I have FreeBSD 6.0-RELEASE.
It seems there is collision between /etc/defaults/rc.conf and
/etc/rc.sendmail in sendmail startup control.
In /etc/defaults/rc.conf:
sendmail_enable=NO# Run the sendmail inbound daemon (YES/NO).
In /etc/rc.sendmail:
...
start_mta()
{
case ${sendmail_enable} in
[Nn][Oo][Nn][Ee])
;;
So sendmail doesn't startup during system startup only if there is
sendmail_enable=NONE in /etc/rc.conf.
Maybe I don't understand something?
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: mouse scroll up problem
I have FreeBSD 6.0-RELEASE and optical Microsoft IntelliMouse Explorer, USB native, plugged to PS/2 port via it's own USB-PS/2 adaptor. When I scroll my mouse wheel up in X11 it acts like scroll up + left button one/double-click. For example, in Opera, Firefox. In MS Windows mouse works correctly. I am running the same mouse in the same way on the same release. I have changed settings as Pete advised. Both variants (old and new) are working (scrolling) but described effect remains. Why I think that scrolling up works as scroll + left click: for example, in Opera scrolling up at the top of document (when real scroll is impossible) result in marking the word under cursor and appearing context menu for very short time. I've been having the same problem since updating to Xorg 6.9.0 two months ago. Before that, this problem did not exist for me. Here are a couple examples of what I see with use: I know it's only a workaround and not a solution, but at least until you're able to get the rodent behaving the way you like, you can change the setting in Thunderbird preferences. In v1.5: Edit -- Preferences -- Advanced [Check box] Wait XX seconds before marking a message as read (2nd item down) Effect disappears when mouse is plugged to USB port directly, without adapter. Besides that with ums(4) buttons 6 and 7 works although it has the same affect as button 1. But there is no ability to power off USB port at the moment it seems (http://lists.freebsd.org/pipermail/freebsd-usb/2005-December/001756.html). PS/2 advantage: 'killall moused' results in turning mouse off, for USB it doesn't. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: mouse scroll up problem
I have FreeBSD 6.0-RELEASE and optical Microsoft IntelliMouse Explorer, USB native, plugged to PS/2 port via it's own USB-PS/2 adaptor. When I scroll my mouse wheel up in X11 it acts like scroll up + left button one/double-click. For example, in Opera, Firefox. In MS Windows mouse works correctly. I am running the same mouse in the same way on the same release. Here is what is working for me: Section InputDevice Identifier Mouse0 Driver mouse Option Device /dev/sysmouse Option Protocol sysmouse Option ZAxisMapping 4 5 EndSection moused_enable=YES # don't use type auto with KVM moused_nondefault_enable=NO moused_type=ps/2 -l 2 # -l 2 for scroll (fails in _flags) moused_flags= I have changed settings as Pete advised. Both variants (old and new) are working (scrolling) but described effect remains. Why I think that scrolling up works as scroll + left click: for example, in Opera scrolling up at the top of document (when real scroll is impossible) result in marking the word under cursor and appearing context menu for very short time. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
mouse scroll up problem
Hello! I have FreeBSD 6.0-RELEASE and optical Microsoft IntelliMouse Explorer, USB native, plugged to PS/2 port via it's own USB-PS/2 adaptor. When I scroll my mouse wheel up in X11 it acts like scroll up + left button one/double-click. For example, in Opera, Firefox. In MS Windows mouse works correctly. boot message: psm0: model IntelliMouse Explorer, device ID 4 xorg.conf fragment: Section InputDevice Identifier Mouse0 Driver mouse Option Protocol auto Option Device /dev/sysmouse Option Buttons 5 Option ZAxisMapping 4 5 EndSection /etc/rc.conf fragment: moused_enable=YES moused_type=auto moused_port=/dev/psm0 moused_flags=-F 200 -r high -a 2.5 -l 1 mousechar_start=3 ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
