mousewheel scrolling
hi! what is up with the mousewheel scrolling? a while ago several people reported it as being broken, and it still appears to be broken to this day on a recent -CURRENT. i've tried several different things, like starting moused with -z 4 and having ZAxisMapping 4 5 in my XF86Config, but nothing seems to be working. the mousewheel is dead :/ anyone else seeing this? any working workaround? thanks! - martin, [EMAIL PROTECTED] ps. i guess it might have something to do with r1.56 of moused.c, i'll try reverting that and see if it makes any difference. ds. To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: Will official-NVIDIA-driver for 4.7 work with -CURRENT ?
[ sorry for not getting the in-reply-to correct, i'm no longer subscribed to current@ ] the nvidia supplied drivers appear to work fine except for libGL* which are compiled on an older system and thus give: /usr/libexec/ld-elf.so.1: /usr/X11R6/lib/libGL.so.1: Undefined symbol __sF any way to get around this? To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: Will official-NVIDIA-driver for 4.7 work with -CURRENT ?
On Fri, Nov 08, 2002 at 05:30:19PM +0100, Martin Faxer wrote: [ sorry for not getting the in-reply-to correct, i'm no longer subscribed to current@ ] the nvidia supplied drivers appear to work fine except for libGL* which are compiled on an older system and thus give: /usr/libexec/ld-elf.so.1: /usr/X11R6/lib/libGL.so.1: Undefined symbol __sF any way to get around this? i apologize for not reading current@ a bit more :) i found the __sF thread now :) i guess a temporary 'fix' will be to recompile my libc with __sF once again. To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: Will official-NVIDIA-driver for 4.7 work with -CURRENT ?
On Fri, Nov 08, 2002 at 05:43:20PM +0100, Martin Faxer wrote: On Fri, Nov 08, 2002 at 05:30:19PM +0100, Martin Faxer wrote: i apologize for not reading current@ a bit more :) i found the __sF thread now :) another apology, since this is my 3rd mail in a very short period of time! however, i can inform you all that libGL works after having removed the static qualifier from __sF and recompiled libc! 13125 frames in 5.0 seconds = 2625.000 FPS 16237 frames in 5.0 seconds = 3247.400 FPS 16091 frames in 5.0 seconds = 3218.200 FPS this is on a -CURRENT from 31st oct :) To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: buildworld failed
On 2002.06.18 16:44:01 +, Igor Roboul wrote: Hello, I have got following error while building today's -CURRENT: if you'd bothered to read the mailing lists a little bit more closely you'd know that by now this issue has been discussied in at least 2 threads already, latest one being only a day old. the fix is (yet again) to rebuild sed. === usr.bin/truss cp /opt/freebsd-current/src/usr.bin/truss/../../sys/kern/syscalls.master syscall s.master /bin/sh /opt/freebsd-current/src/usr.bin/truss/../../sys/kern/makesyscalls.sh sy scalls.master /opt/freebsd-current/src/usr.bin/truss/i386.conf syscalls.master: line 55: syscall number out of sync at 7 line is: struct rusage * rusage ) ; } wait4 wait_args int To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: Error in truss (Was: Re: error in ncurses in 'make buildworld')
On 2002.06.24 21:49:47 +, Johan Granlund wrote: Hi I'ts probably not related, but i have problems :) I have tried a couple of days to compile world, with CFLAGS=-O -pipe, with a system from Jun 16 and it stops at the same place every time. I have tried to clean out /usr/src and obj and resup. Recompiled awk and sh if something happened to them but no change. Any ideas as what happened ? This exact issue has been discussed numerous times on this list before. The fix is to rebuild sed. The error is: === usr.bin/truncate rm -f .depend mkdep -f .depend -a /usr/src/usr.bin/truncate/truncate.c echo truncate: /usr/obj/usr/src/i386/usr/lib/libc.a .depend === usr.bin/truss cp /usr/src/usr.bin/truss/../../sys/kern/syscalls.master syscalls.master /bin/sh /usr/src/usr.bin/truss/../../sys/kern/makesyscalls.sh syscalls.master / usr/src/usr.bin/truss/i386.conf syscalls.master: line 55: syscall number out of sync at 7 line is: struct rusage * rusage ) ; } wait4 wait_args int *** Error code 1 To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: kern: device pcm problems
On 2002.07.02 16:28:10 +, Michael Hostbaek wrote: I have problems getting my sound card functioning under -CURRENT. (While it was working perfect under -STABLE). I simply added 'device pcm' to the kernel config, when booting on new kernel I get lots of errors like this: ESS Technology Maestro-2E port 0x1400-0x14ff irq 5 at device 8.0 on pci0 ../../../vm/uma_core.c:1333: could sleep with pcm0 locked from ../../../dev/so und/pcm/sound.c:134 This is a well known problem; it's basically a diagnostic message telling you that there's a deficiency in the pcm driver. If you want to fix it permanently I suggest that you go and have a look at dev/sound/pcm/sound.c:134 and look for a way of invoking UMA without holding the lock. If you just want to work around it, you can probably disable INVARIANTS and WITNESS in your kernel configuration and hope that it won't turn into a real problem (ie. panic.) To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: kern: device pcm problems
On 2002.07.02 17:56:28 +, Juan Francisco Rodriguez Hervella wrote: Im a bit corious about what's the meaning of UMA. Thanks and sorry fot this simple question :) UMA is the Universal Memory Allocator, written by Jeff Roberson. It's the memory manager and things like malloc(9) make use of it. It was quite recently committed to -CURRENT so if you search the archives it shouldn't be too hard to find mails describing it in more detail. To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Another KSE problem?
Hi! This morning, when starting XMMS, I saw something weird: redpixel@lockdown:~ % xmms [1] 603 redpixel@lockdown:~ % cat cat: stdin: Resource temporarily unavailable This is on a 2 days old -CURRENT. (PS. If this has been reported and/or fixed already, I apologise in advance. My mail has been bouncing the last few days...) To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: mozilla port?
On Thu, Jul 11, 2002 at 10:58:01AM -0700, Seth Hettich wrote: Is this building for anyone? I always get: gmake[1]: Leaving directory `/u1/src/ports/www/mozilla/work/mozilla' /usr/bin/sed -e s;@PREFIX@;/usr/X11R6;g /u1/src/ports/www/mozilla/files/mozilla.sh /u1/src/ports/www/mozilla/work/mozilla/mozilla (cd /u1/src/ports/www/mozilla/work/mozilla/dist/bin; /usr/bin/env LD_LIBRARY_PATH=. MOZILLA_FIVE_HOME=. ./regxpcom; echo skin,install,select,classic/1.0 chrome/installed-chrome.txt; echo locale,install,select,en-US chrome/installed-chrome.txt; /usr/bin/env LD_LIBRARY_PATH=. MOZILLA_FIVE_HOME=. ./regchrome) [1] 32857 Segmentation fault (core dumped) *** Error code 139 Joe Marcus Clarke ([EMAIL PROTECTED]) posted a message earlier today containing a patch that fixes this. Perhaps you should read the list a little bit more closely. :) To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: mfs in current
On 2002.05.25 20:16:05 +, Emanuel Haupt wrote: i was wondering, where the mount_mfs in the current version has gone? i am using current on my dell laptop (compatibility reason with 32bit cardbus) and would like to increase the performance with a mfs mount for my swap partition. MFS is now known as MD. Try man 8 mdconfig and man 4 md. Your reason for wanting to use it sounds a little bit crazy though; Swap is used when there isn't sufficient physical memory available. I believe the FreeBSD VM system will handle your memory better if it has access to all of it rather than having some of it mounted as a memory disk. thanx for your answers. emanuel To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
