Re: Netscape 4.76 & MGA DRI
Scott Long wrote: > > Rhett Monteg Hollander wrote: > > > Hello gentlemen, > > > > several days ago I've installed 5.0-RELEASE onto one > > of my machines, which already carried 4.7-RC1. To > > avoid possible compatibility problems, I did a clean > > install onto another hard drive, and later recompiled > > everything. Here I have a couple of annoying issues. > > > > Shell refuses to start Netscape Communicator 4.76 (for > > FreeBSD) saying "binary file is not executable", but > > it was (and is) running fine under 4.7. Since it was > > compiled under FreeBSD 2.2.x, I have compat22 > > installed (together with compat3x and compat4x). No > > help. > > Recompile your kernel with COMPAT_AOUT, or load the aout.ko kernel module. Floating exception (core dumped), ~2 megs > > > > > Second issue comes to be about hardware-accelerated > > OpenGL under XFree86 4.2.0, using Matrox G400 > > hardware. Simply, there is no hardware acceleration at > > all. DRM kernel modules that come with 4.2.0 are > > intended for use with FreeBSD 4.x, and they don't even > > compile under 5.x. I built kernel with "device mgadrm" > > and "options DRM_LINUX", as well as "options > > COMPAT_LINUX". After launching glxgears system hangs > > up completely. Problem seems to be within libdrm. So > > far I have no DRI, but software OpenGL, and 162fps > > compared to 368fps under 4.7. > > FreeBSD 5.0 comes with the DRM kernel modules in the base system, as it > looks like you discovered. Can you enable a serial console and capture > the crash? Fixed. Problem was in XF86Config, which was set up improperly. Not sure what exactly led to that point, because I've overwritten it with a substitute from 4.7. Now glxgears run fine, at 357fps; interesting, I supposed 5.0 to be faster than 4.7 in this case, at least in honour of gcc-3.2.1 > > Scott > > > > > --- > > Regards, > > Rhett > > __ Do you Yahoo!? Yahoo! Shopping - Send Flowers for Valentine's Day http://shopping.yahoo.com To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: Netscape 4.76 & MGA DRI
Rhett Monteg Hollander wrote: Hello gentlemen, several days ago I've installed 5.0-RELEASE onto one of my machines, which already carried 4.7-RC1. To avoid possible compatibility problems, I did a clean install onto another hard drive, and later recompiled everything. Here I have a couple of annoying issues. Shell refuses to start Netscape Communicator 4.76 (for FreeBSD) saying "binary file is not executable", but it was (and is) running fine under 4.7. Since it was compiled under FreeBSD 2.2.x, I have compat22 installed (together with compat3x and compat4x). No help. Recompile your kernel with COMPAT_AOUT, or load the aout.ko kernel module. Second issue comes to be about hardware-accelerated OpenGL under XFree86 4.2.0, using Matrox G400 hardware. Simply, there is no hardware acceleration at all. DRM kernel modules that come with 4.2.0 are intended for use with FreeBSD 4.x, and they don't even compile under 5.x. I built kernel with "device mgadrm" and "options DRM_LINUX", as well as "options COMPAT_LINUX". After launching glxgears system hangs up completely. Problem seems to be within libdrm. So far I have no DRI, but software OpenGL, and 162fps compared to 368fps under 4.7. FreeBSD 5.0 comes with the DRM kernel modules in the base system, as it looks like you discovered. Can you enable a serial console and capture the crash? Scott --- Regards, Rhett __ Do you Yahoo!? Yahoo! Shopping - Send Flowers for Valentine's Day http://shopping.yahoo.com 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
Netscape 4.76 & MGA DRI
Hello gentlemen, several days ago I've installed 5.0-RELEASE onto one of my machines, which already carried 4.7-RC1. To avoid possible compatibility problems, I did a clean install onto another hard drive, and later recompiled everything. Here I have a couple of annoying issues. Shell refuses to start Netscape Communicator 4.76 (for FreeBSD) saying "binary file is not executable", but it was (and is) running fine under 4.7. Since it was compiled under FreeBSD 2.2.x, I have compat22 installed (together with compat3x and compat4x). No help. Second issue comes to be about hardware-accelerated OpenGL under XFree86 4.2.0, using Matrox G400 hardware. Simply, there is no hardware acceleration at all. DRM kernel modules that come with 4.2.0 are intended for use with FreeBSD 4.x, and they don't even compile under 5.x. I built kernel with "device mgadrm" and "options DRM_LINUX", as well as "options COMPAT_LINUX". After launching glxgears system hangs up completely. Problem seems to be within libdrm. So far I have no DRI, but software OpenGL, and 162fps compared to 368fps under 4.7. --- Regards, Rhett __ Do you Yahoo!? Yahoo! Shopping - Send Flowers for Valentine's Day http://shopping.yahoo.com To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: MSDOSFS wastes 256k when nothing is mounted!
On Mon, 10 Feb 2003 13:31:48 +1100 Tim Robbins <[EMAIL PROTECTED]> wrote: > It might be better to initialise the table the first time an > msdosfs filesystem is mounted. > This implies that the existence of the hash table be revealed outside the module. Is this a layering violation? None of the _vfsops functions (except for init/uninit) can currently see the hash table, and of the ones that deal with denodes, none of them uses it directly. We can keep knowledge of the hashtable"in module" if we do the initialization in deget(), before the vnode lock. This seems like a better(if a little hackish) option to me, but this is the first time I've dealt with the filesystem so please let me know if I have the wrong idea. Cheers. -- Mike Makonnen | GPG-KEY: http://www.identd.net/~mtm/mtm.asc [EMAIL PROTECTED] | Fingerprint: D228 1A6F C64E 120A A1C9 A3AA DAE1 E2AF DBCC 68B9 To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: Synaptics touchpad support
On Mon, 10 Feb 2003, Paul A. Mayer wrote: > Well, it compiles on 5.0-Release-p1. The psm initialization gives some > specs about the device and some of it's features. ... but I don't see > any consequences of this in apps, like mozilla. And under gnome the > pressure sensitivity of the touchpad (e.g., tap to click) is now gone. > > I have no great understanding of how any of this should work. Can you > give some pointers. (How do I get touch sensitivity back? How should > it be configured into X? Where should I be able to see the effects of > the patch?) Here is what I'm using. In /etc/rc.conf: moused_enable="YES" moused_flags="-m2=4 -m4=2" And in /etc/X11/XF86Config: Section "InputDevice" Identifier "Mouse0" Driver "mouse" Option "Protocol" "Auto" Option "Device" "/dev/sysmouse" Option "Resolution" "250" Option "EmulateWheel" Option "EmulateWheelInertia" "60" Option "EmulateWheelButton" "4" Option "Buttons" "4" EndSection This gives me 3 buttons, plus an emulated "scroll wheel", when I hold down the fourth button and move my finger up or down on the mousepad. (see mouse(4) in /usr/X11R6/man, not mouse(4) in /usr/share/man...) $.02, /Mikko To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: Synaptics touchpad support
On Mon, 10 Feb 2003, Terry Lambert wrote: [...] > You actually lose the tap/tap-tap click and doubleclick button > emulation with the new driver, and, as you note, the pressure > sensitivity. [...] > Probably the best thing to do would be to disassemble the BIOS on > your box, knowing the difference between the older driver's interface, > and use the same techniques that were hidden from the older driver > (and "just built in" instead). I doubt that would help. The mousepad can operate in two different modes, in the basic mode you get built-in tapping, but only two buttons, in the other mode you get more information (e.g. all buttons), but have to figure out the tap action yourself from the pressure delta over time. The behavior is documented by the manufacturer (synaptics.com.tw), who actually provides specs on-line (whee!). $.02, /Mikko (who likes using all buttons and have learned to live without tapping...) To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: GCC 3.2.2 import -- questions
Craig Rodrigues wrote: > There is a long thread on the GCC mailing list right now complaining > about compile-time speed regressions from 2.95.x, with many complaints > coming from Apple: I don't think the original poster was talking about compile-time speed. The running speed of applications is vastly improved under gcc 3.2.x, sometimes by 30% over gcc 2.95.x, in my experience. To the OP -- any speed improvement from gcc 3.2.1 to 3.2.2 would probably be marginal. If some particular port really bothers you with its slow performance, try recompiling (though it's unlikely to help), otherwise don't bother. - Rahul To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: GCC 3.2.2 import -- questions
At 9:43 PM -0500 2/10/03, Craig Rodrigues wrote: There is a long thread on the GCC mailing list right now complaining about compile-time speed regressions from 2.95.x, with many complaints coming from Apple: http://gcc.gnu.org/ml/gcc/2003-02/msg00558.html Whether these complaints lead to actual improvements is yet to be seen I do not follow that mailing list. Looking at the thread you pointed at, I see comments from Apple, openbsd developers, and someone in the linux world. Could someone who is regularly on that mailing list add a comment about the freebsd project's experience with switching from 2.95.x to 3.x? I'm the type of person who decided I had to buy a new machine after gcc 3.x went in, because I couldn't stand the slowdown of the new compiler. To me, the cost of that was $1500 and a fair amount of my spare time to shuffle machines around. Sounds like a good reason to complain, but I wouldn't want to jump into the gcc mailing list if someone from FreeBSD is already covering compile-time performance. -- Garance Alistair Drosehn= [EMAIL PROTECTED] Senior Systems Programmer or [EMAIL PROTECTED] Rensselaer Polytechnic Instituteor [EMAIL PROTECTED] To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: Still problems with ULE
On Mon, Feb 10, 2003 at 08:36:50PM -0500, Jeff Roberson wrote: > Very weird. Is this on UP or SMP? This is on UP. I can still break into DDB, so let me know if you want me to run console tests (no serial console though). Kris msg52192/pgp0.pgp Description: PGP signature
Re: Still problems with ULE
On 2003-02-10 20:36 +, Jeff Roberson wrote: > On Mon, 10 Feb 2003, Kris Kennaway wrote: > > > I gave ULE another try just now, following your recent commits, and > > I'm seeing even worse problems: > > > > At boot time when the X server is loading, disk activity occurs > > briefly about once every 2 seconds; the mouse is active briefly at the > > same time, and nothing much else happens for about a minute until the > > entire system deadlocks. > > Very weird. Is this on UP or SMP? I'm still working on a couple of > issues with ule. I think I am very happy with the dynamic priority > selection now but in the process the slice size selection got kinda dirty. > Its pretty much bug for bug compatible with the old scheduler's context > switching decisions but the errors there are more serious with this > design. I also think the max slice size is way too high now. I was > experimenting with that and I accidentally checked it in. > I'm seeing some of the same with sources from about 90 minutes ago. UP system, loading X is a pain. Interactivity is somewhat alright up until I start a compile, at which point the system goes down on it's knees. It hasn't completely deadlocked (yet?), but it's pretty much unusable if anything intensive is happening. -- Munish Chopra To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: GCC 3.2.2 import -- questions
On Mon, Feb 10, 2003 at 09:50:06PM -0500, Scott Dodson wrote: > Excellent, > > Which optimization strings are you using in make.conf if you don't mind? > > -- > Scott Plain cflags and cxxflags taken from /usr/share/examples/etc/make.conf just modify the CPUTYPE as p4 Cheers, Jiawei Ye -- "Without the userland, the kernel is useless." --inspired by The Tao of Programming To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: GCC 3.2.2 import -- questions
On Mon, 10 Feb 2003, Craig Rodrigues wrote: > Many people are upgrading from 4.7.x to -current for the first > time these days, so I thought I would mention that for reference. > > GCC 3.2.2 was an incremental bugfix over GCC 3.2.1, and there are no > earth-shattering performance improvements. I have not done > such benchmarking myself, so have no empirical evidence to support this, > but I am basing this on the traffic I have been watching on the > GCC mailing list, and by reading the release notes > at http://gcc.gnu.org/gcc-3.2/changes.html . Well what I am really interested in is whether or not higher levels of optimization are more reliable now than before. Previously we have been warned against using many of the CPU specific optimizations, especially for the pentium 4, and the release notes offer little to support any conclusions... So without digging through mountains of GCC mailing list archives... Are these optimizations SAFER now? -- Hi! I'm a .signature virus! Copy me into your ~/.signature to help me spread! To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: GCC 3.2.2 import -- questions
On Mon, Feb 10, 2003 at 08:06:19PM -0600, Juli Mallett wrote: > I would assume the OP meant relative to the previous version of GCC in > tree. Current hasn't been 2.95.x for some time. Many people are upgrading from 4.7.x to -current for the first time these days, so I thought I would mention that for reference. GCC 3.2.2 was an incremental bugfix over GCC 3.2.1, and there are no earth-shattering performance improvements. I have not done such benchmarking myself, so have no empirical evidence to support this, but I am basing this on the traffic I have been watching on the GCC mailing list, and by reading the release notes at http://gcc.gnu.org/gcc-3.2/changes.html . There is a long thread on the GCC mailing list right now complaining about compile-time speed regressions from 2.95.x, with many complaints coming from Apple: http://gcc.gnu.org/ml/gcc/2003-02/msg00558.html Whether these complaints lead to actual improvements is yet to be seen -- Craig Rodrigues http://home.attbi.com/~rodrigc [EMAIL PROTECTED] To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: GCC 3.2.2 import -- questions
On Mon, Feb 10, 2003 at 08:44:33PM -0500, Wesley Morgan wrote: > The import of gcc 3.2.2 brings a question to mind... Many people have > mentioned problems with SSE / SSE2 instructions, optimizer problems etc > that are supposedly fixed with 3.2.2... My question is, should I consider > rebuilding my ports with this new compiler because of stability and/or > speed improvements? Or is this point release not worth the effort. lcms post-build tests now finishes correctly with pentium4 optimizations. And I have world with the p4 optimization with no ill-effact so far. Jiawei Ye -- "Without the userland, the kernel is useless." --inspired by The Tao of Programming To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: GCC 3.2.2 import -- questions
* De: Craig Rodrigues <[EMAIL PROTECTED]> [ Data: 2003-02-10 ] [ Subjecte: Re: GCC 3.2.2 import -- questions ] > On Mon, Feb 10, 2003 at 08:44:33PM -0500, Wesley Morgan wrote: > > that are supposedly fixed with 3.2.2... My question is, should I consider > > rebuilding my ports with this new compiler because of stability and/or > > speed improvements? Or is this point release not worth the effort. > > Speed improvements? No. gcc 3.2.2 is definitely slower than gcc 2.95. > There is a lot of arguing on the gcc mailing list right now about this, > but no concrete action to improve the situation yet. I would assume the OP meant relative to the previous version of GCC in tree. Current hasn't been 2.95.x for some time. -- Juli Mallett <[EMAIL PROTECTED]> AIM: BSDFlata -- IRC: juli on EFnet OpenDarwin, Mono, FreeBSD Developer ircd-hybrid Developer, EFnet addict FreeBSD on MIPS-Anything on FreeBSD To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: GCC 3.2.2 import -- questions
On Mon, Feb 10, 2003 at 08:44:33PM -0500, Wesley Morgan wrote: > that are supposedly fixed with 3.2.2... My question is, should I consider > rebuilding my ports with this new compiler because of stability and/or > speed improvements? Or is this point release not worth the effort. Speed improvements? No. gcc 3.2.2 is definitely slower than gcc 2.95. There is a lot of arguing on the gcc mailing list right now about this, but no concrete action to improve the situation yet. Stability improvements? For a list of bug fixes see: http://gcc.gnu.org/gcc-3.2/changes.html and decide for yourself. -- Craig Rodrigues http://home.attbi.com/~rodrigc [EMAIL PROTECTED] To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
GCC 3.2.2 import -- questions
The import of gcc 3.2.2 brings a question to mind... Many people have mentioned problems with SSE / SSE2 instructions, optimizer problems etc that are supposedly fixed with 3.2.2... My question is, should I consider rebuilding my ports with this new compiler because of stability and/or speed improvements? Or is this point release not worth the effort. -- Hi! I'm a .signature virus! Copy me into your ~/.signature to help me spread! To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: RE : IPFilter
On Mon, Feb 10, 2003 at 11:43:27PM +0100, Coercitas Temet'Nosce wrote: > Yes, kinda :p > > Thanx for all your answers btw > Are you getting confused between ipfw in Linux and ipfw in FreeBSD maybe? When I first saw ipfw I thought it must be old and obsolete, because it's been around for a long time, whereas Linux has had lots of different firewalls, with ipfw being in 2.0, ipchains in 2.2 and ipfilter in 2.4. ipfw in FreeBSD is just like ipfilter in Linux - it too can do connection tracking, and just like while in Linux you've got iptables in the user-space and ipfilter in the kernel, in FreeBSD there's ipfirewall in the kernel and ipfw is the user-space control program. I don't know much about firewalling in FreeBSD since I've not been using it all that long, but from what I understand, ipfw has taken over from ipf as the main firewalling system. -- Bruce Cran To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: Still problems with ULE
On Mon, 10 Feb 2003, Kris Kennaway wrote: > I gave ULE another try just now, following your recent commits, and > I'm seeing even worse problems: > > At boot time when the X server is loading, disk activity occurs > briefly about once every 2 seconds; the mouse is active briefly at the > same time, and nothing much else happens for about a minute until the > entire system deadlocks. Very weird. Is this on UP or SMP? I'm still working on a couple of issues with ule. I think I am very happy with the dynamic priority selection now but in the process the slice size selection got kinda dirty. Its pretty much bug for bug compatible with the old scheduler's context switching decisions but the errors there are more serious with this design. I also think the max slice size is way too high now. I was experimenting with that and I accidentally checked it in. I think I know what the remaining problems are. I'll make a post on current@ when they're all sorted out. Thanks for testing! Cheers, Jeff To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Still problems with ULE
I gave ULE another try just now, following your recent commits, and I'm seeing even worse problems: At boot time when the X server is loading, disk activity occurs briefly about once every 2 seconds; the mouse is active briefly at the same time, and nothing much else happens for about a minute until the entire system deadlocks. Kris msg52181/pgp0.pgp Description: PGP signature
Re: Two witness panics in vfs_bio
On Mon, 10 Feb 2003, Kris Kennaway wrote: > > It was tested. I ran it on my desktop and did several buildworlds on an > > smp machine. I should have let it kick around for a bit longer than a few > > days, I agree. I will commit the fix in just a moment. > > Thanks! > Yeah, I really am sorry about the trouble. I didn't test in any low memory situations or with slow enough disks. The problems that came up were due to this. My machine was able to sync fast enough to avoid buffer starvation. Cheers, Jeff To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
alpha tinderbox failure
-- >>> Rebuilding the temporary build tree -- >>> stage 1: bootstrap tools -- >>> stage 2: cleaning up the object tree -- >>> stage 2: rebuilding the object tree -- >>> stage 2: build tools -- >>> stage 3: cross tools -- >>> stage 4: populating /home/des/tinderbox/alpha/obj/h/des/src/alpha/usr/include -- >>> stage 4: building libraries -- >>> stage 4: make dependencies -- >>> stage 4: building everything.. -- >>> Kernel build for GENERIC started on Mon Feb 10 15:35:47 PST 2003 -- >>> Kernel build for GENERIC completed on Mon Feb 10 16:12:02 PST 2003 -- >>> Kernel build for LINT started on Mon Feb 10 16:12:03 PST 2003 -- ===> vinum "Makefile", line 4458: warning: duplicate script for target "geom_bsd.o" ignored /h/des/src/sys/dev/lmc/if_lmc.c:32:2: warning: #warning "The lmc driver is broken and is not compiled with LINT" /h/des/src/sys/dev/pdq/pdq.c: In function `pdq_initialize': /h/des/src/sys/dev/pdq/pdq.c:1606: warning: cast discards qualifiers from pointer target type /h/des/src/sys/pci/meteor.c:149:2: warning: #warning "The meteor driver is broken and is not compiled with LINT" /h/des/src/sys/pci/simos.c:30:2: warning: #warning "The simos driver is broken and is not compiled with LINT" /h/des/src/sys/dev/gfb/gfb_pci.c: In function `pcigfb_open': /h/des/src/sys/dev/gfb/gfb_pci.c:268: `gfb_devclass' undeclared (first use in this function) /h/des/src/sys/dev/gfb/gfb_pci.c:268: (Each undeclared identifier is reported only once /h/des/src/sys/dev/gfb/gfb_pci.c:268: for each function it appears in.) cc1: warnings being treated as errors /h/des/src/sys/dev/gfb/gfb_pci.c:275: warning: passing arg 1 of `genfbopen' from incompatible pointer type /h/des/src/sys/dev/gfb/gfb_pci.c: In function `pcigfb_close': /h/des/src/sys/dev/gfb/gfb_pci.c:284: `gfb_devclass' undeclared (first use in this function) /h/des/src/sys/dev/gfb/gfb_pci.c:285: warning: passing arg 1 of `genfbclose' from incompatible pointer type /h/des/src/sys/dev/gfb/gfb_pci.c: In function `pcigfb_read': /h/des/src/sys/dev/gfb/gfb_pci.c:293: `gfb_devclass' undeclared (first use in this function) /h/des/src/sys/dev/gfb/gfb_pci.c:294: warning: passing arg 1 of `genfbread' from incompatible pointer type /h/des/src/sys/dev/gfb/gfb_pci.c: In function `pcigfb_write': /h/des/src/sys/dev/gfb/gfb_pci.c:302: `gfb_devclass' undeclared (first use in this function) /h/des/src/sys/dev/gfb/gfb_pci.c:303: warning: passing arg 1 of `genfbwrite' from incompatible pointer type /h/des/src/sys/dev/gfb/gfb_pci.c: In function `pcigfb_ioctl': /h/des/src/sys/dev/gfb/gfb_pci.c:311: `gfb_devclass' undeclared (first use in this function) /h/des/src/sys/dev/gfb/gfb_pci.c:312: warning: passing arg 1 of `genfbioctl' from incompatible pointer type /h/des/src/sys/dev/gfb/gfb_pci.c: In function `pcigfb_mmap': /h/des/src/sys/dev/gfb/gfb_pci.c:320: `gfb_devclass' undeclared (first use in this function) /h/des/src/sys/dev/gfb/gfb_pci.c:321: warning: passing arg 1 of `genfbmmap' from incompatible pointer type *** Error code 1 Stop in /h/des/obj/h/des/src/sys/LINT. *** Error code 1 Stop in /h/des/src. *** Error code 1 Stop in /h/des/src. To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: Two witness panics in vfs_bio
On Mon, Feb 10, 2003 at 05:32:42PM -0500, Jeff Roberson wrote: > On Mon, 10 Feb 2003, Kris Kennaway wrote: > > > *Grump* I can't get my boxes to stay up more than a few > > minutes..evidently this code was not tested prior to commit. > > > > So much for getting work done on the package cluster today. > > > > It was tested. I ran it on my desktop and did several buildworlds on an > smp machine. I should have let it kick around for a bit longer than a few > days, I agree. I will commit the fix in just a moment. Thanks! Kris msg52178/pgp0.pgp Description: PGP signature
printf...! and BSD
Hi, First of all, Thanks to all of you for your help and support. I have tried to go deeper and deeper to find out how "printf" works. ((( Of course the aim of trying to understand the "printf", is to understand how the internals of the BSD kernel work))) till i've faced the following function: "fo_write" which was confusing for me =) Then, I've figured out that i need to understand two important things in the BSD to know how the "printf" works. The first thing is how dose the device driver works, and the second thing is the file system, and small knowledge about the process structure. I will try to do that, but which resources can help me. For Linux, there are two great book which can make my life easier "FOR LINUX ONLY" 1.UNDERSTANDING THE LINUX KERNEL. 2.LINUX DEVICE DRIVERS. Now what resources you can recommend for me! I prefer Internet resources. Yours, _ MSN 8 with e-mail virus protection service: 2 months FREE* http://join.msn.com/?page=features/virus To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: IPFilter
On 2003-02-09 20:07, Coercitas Temet'Nosce <[EMAIL PROTECTED]> wrote: > Pardon my poor knowledge about IPFW 2 but if I remember well, IPFW > wasn't a SPI Firewall, which is what I need. Btw, previous Kernel > allows us to fine tune its building for IPF and now, it simply > gone...was really wondering where those features are. What sort of fine tuning are you talking about? To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
RE : IPFilter
Yes, kinda :p Thanx for all your answers btw -Message d'origine- De : Simon L. Nielsen [mailto:[EMAIL PROTECTED]] Envoyé : lundi 10 février 2003 23:43 À : Coercitas Temet'Nosce Cc : [EMAIL PROTECTED] Objet : Re: IPFilter On 2003.02.10 23:37:36 +0100, Coercitas Temet'Nosce wrote: > Yes, SPI stands for Statefull Packet Inspection. Wasn't aware IPFW was a > SPI Firewall, always thought IPFilter was much better. I used to run > iptables on Linux and tried IPFilter (which is very good imho). IPFW > pages aren't that explicit or I didn't looked at the right place. >From ipfw(8) : HISTORY The ipfw utility first appeared in FreeBSD 2.0. dummynet(4) was intro duced in FreeBSD 2.2.8. Stateful extensions were introduced in FreeBSD 4.0. ipfw2 was introduced in Summer 2002. > Any of you can point me some nice pages to learn more about it ? The ipfw manpage has a lot of information... This is getting off-topic for current... -- Simon L. Nielsen To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: IPFilter
On 2003.02.10 23:37:36 +0100, Coercitas Temet'Nosce wrote: > Yes, SPI stands for Statefull Packet Inspection. Wasn't aware IPFW was a > SPI Firewall, always thought IPFilter was much better. I used to run > iptables on Linux and tried IPFilter (which is very good imho). IPFW > pages aren't that explicit or I didn't looked at the right place. From ipfw(8) : HISTORY The ipfw utility first appeared in FreeBSD 2.0. dummynet(4) was intro duced in FreeBSD 2.2.8. Stateful extensions were introduced in FreeBSD 4.0. ipfw2 was introduced in Summer 2002. > Any of you can point me some nice pages to learn more about it ? The ipfw manpage has a lot of information... This is getting off-topic for current... -- Simon L. Nielsen msg52174/pgp0.pgp Description: PGP signature
RE : RE : IPFilter
Yes, SPI stands for Statefull Packet Inspection. Wasn't aware IPFW was a SPI Firewall, always thought IPFilter was much better. I used to run iptables on Linux and tried IPFilter (which is very good imho). IPFW pages aren't that explicit or I didn't looked at the right place. Any of you can point me some nice pages to learn more about it ? Regards -Message d'origine- De : [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]] De la part de Daniel C. Sobral Envoyé : lundi 10 février 2003 13:46 À : Coercitas Temet'Nosce Cc : 'Don'; [EMAIL PROTECTED] Objet : Re: RE : IPFilter Coercitas Temet'Nosce wrote: > Pardon my poor knowledge about IPFW 2 but if I remember well, IPFW > wasn't a SPI Firewall, which is what I need. Btw, previous Kernel allows > us to fine tune its building for IPF and now, it simply gone...was > really wondering where those features are. What, exactly, is a 'SPI' firewall? If you mean stateful firewall, you haven't looking into ipfw for at least five years (making your remark obsolete, not ipfw :). The only thing I couldn't do with the old ipfw was atomic replacement of rules. With ipfw2 I can do that. ipfw2 is default on 5.0 and can be turned on on 4.7 (options IPFW2 on kernel and WITH_IPFW2, iirc, on make.conf). The '2' is the version, the binary, man pages etc still have all the same names. > > Is there any web place where I can find stuff about IPFW2 by chance ? > > regards > > -Message d'origine- > De : [EMAIL PROTECTED] > [mailto:[EMAIL PROTECTED]] De la part de Don > Envoyé : dimanche 9 février 2003 19:47 > À : Coercitas Temet'Nosce > Cc : [EMAIL PROTECTED] > Objet : Re: TR : IPFilter > > >>Btw, I was looking for some docs on the FreeBSD website and didn't > > found > >>anything interesting, only firewall that FreeBSD seems to support >>nowadays >>is the old IPFW, which is quite obsolete now imo. Why are > > documentation > >>pages not dealing with IPF at all ? is there any reason ? > > Try ipfw2 > > -Don > > 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 -- Daniel C. Sobral (8-DCS) Gerencia de Operacoes Divisao de Comunicacao de Dados Coordenacao de Seguranca TCO Fones: 55-61-313-7654/Cel: 55-61-9618-0904 E-mail: [EMAIL PROTECTED] [EMAIL PROTECTED] [EMAIL PROTECTED] Outros: [EMAIL PROTECTED] [EMAIL PROTECTED] [EMAIL PROTECTED] The past always looks better than it was. It's only pleasant because it isn't here. -- Finley Peter Dunne (Mr. Dooley) 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
Re: Two witness panics in vfs_bio
On Mon, 10 Feb 2003, Kris Kennaway wrote: > *Grump* I can't get my boxes to stay up more than a few > minutes..evidently this code was not tested prior to commit. > > So much for getting work done on the package cluster today. > It was tested. I ran it on my desktop and did several buildworlds on an smp machine. I should have let it kick around for a bit longer than a few days, I agree. I will commit the fix in just a moment. Cheers, Jeff To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: Realport Xircom 10/100 + Modem 56: anyone successful in 5.0-R
> Date: Mon, 10 Feb 2003 20:34:12 +0100 (CET) > From: Jaroslaw Bazydlo <[EMAIL PROTECTED]> > Sender: [EMAIL PROTECTED] > > > Does anyone manage to make it work under 5.0-RELEASE??? This > card has code "Realport Xircom 100/100 + Modem 56 + Modem" and > REM56G-100 on the bottom of it. Of course it works with Windows > and Linux. I was trying xe and dc drivers. I found someone on > mailing list archive reporting that he uses it. Not for me. > > I have borrowed Xircom Relport2 with the same code wich was detected > as dc ethernet but still did not work. Is it a 16 or 32 bit card? If it's 32-bit, it uses if_dc. If it is 16-bit, it uses if_xe. I have both and both are working for Ethernet. Unfortunately the modem is non-functional at this time. Do you have devd enabled? What messages do you get at boot time and/or card insertion? I am not running RELEASE. I am running RELENG_5_0 which could probably be called "semi-stable". It may have some fixes that are not in RELEASE. R. Kevin Oberman, Network Engineer Energy Sciences Network (ESnet) Ernest O. Lawrence Berkeley National Laboratory (Berkeley Lab) E-mail: [EMAIL PROTECTED] Phone: +1 510 486-8634 To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: Two witness panics in vfs_bio
On Mon, Feb 10, 2003 at 09:52:11AM -0800, Kris Kennaway wrote:
> recursed on non-recursive lock (sleep mutex) needsbuffer lock @
>/local0/src-client/sys/kern/vfs_bio.c:1159
> first acquired @ /local0/src-client/sys/kern/vfs_bio.c:1151
> /local0/src-client/sys/kern/kern_synch.c:152: sleeping with "buf queue lock" locked
>from /local0/src-client/sys/kern/vfs_bio.c:1778
> Debugger("witness_sleep")
*Grump* I can't get my boxes to stay up more than a few
minutes..evidently this code was not tested prior to commit.
So much for getting work done on the package cluster today.
Kris
msg52170/pgp0.pgp
Description: PGP signature
Realport Xircom 10/100 + Modem 56: anyone successful in 5.0-R
Does anyone manage to make it work under 5.0-RELEASE??? This card has code "Realport Xircom 100/100 + Modem 56 + Modem" and REM56G-100 on the bottom of it. Of course it works with Windows and Linux. I was trying xe and dc drivers. I found someone on mailing list archive reporting that he uses it. Not for me. I have borrowed Xircom Relport2 with the same code wich was detected as dc ethernet but still did not work. Some useful tips? Best regards J. To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Bluetooth stack for FreeBSD
Dear Hackers, I'm very pleased to announce that another engineering release is available for download at http://www.geocities.com/m_evmenkin/ngbt-fbsd-20030210.tar.gz Note: This release has new tree layout that matches FreeBSD source tree. Quick summary of changes - New in-kernel RFCOMM implementation with SOCK_STREAM interface. The old user space implementation (rfcommd-1.1) is no longer required and is not included in this release. - Support for RFCOMM based DUN and LAN profiles. Note: DUN profile required patch for PPP. The patch was submitted to Brian Somers for review. In the mean time contact me if you want it. - OBEX support. This release includes simple OpenOBEX library based (included) client/server application. It supports both Object Push and File Transfer profiles. It is now possible to get phone book, calendar, pictures etc. from your cell phone. - SDP port has been upgraded to 1.0rc3 - share/examples/netgraph/bluetooth now has sample script that will setup your Bluetooth devices. - Minor bug fixes As usual all comments, bug reports and success stories are appreciated :) thanks, max To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: Does bg fsck have problems with large filesystems?
On Mon, 10 Feb 2003, Attila Nagy wrote: > Hello, > > > > I also gave him access to our machine, which has a 1.2 TB filesystem > > > on it. > > I have a 1.9TB FS about 4 km from him.. > That's great! > Could you please contact him? (do you also have this problem, BTW?) He also has a login on the machine for testing but it's turned off at the moment I'll turn it on again if he asks. > > Thanks, > --[ Free Software ISOs - http://www.fsn.hu/?f=download ]-- > Attila Nagy e-mail: [EMAIL PROTECTED] > Free Software Network (FSN.HU) phone @work: +361 210 1415 (194) > cell.: +3630 306 6758 > > 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
Re: Problems with Current & XFree86
> Since it works with 4.7-STABLE it must(?) be a current problem > more than a XFree86 problem. Or? I had the same problem -- something to do with files left over from the original 4.7 installation. Cured by deinstalling XFree86-* ports, renaming /usr/X11R6 to something else (in case something was needed), and then reinstalling everything. Thanks to portupgrade this was pretty easy. I reused the old XF86Config. To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: kld problem ? (was: Re: MSDOSFS wastes 256k when nothing is mounted!)
- Original Message -
From: "Hiten Pandya" <[EMAIL PROTECTED]>
To: "Alexey Zelkin" <[EMAIL PROTECTED]>
Cc: "Poul-Henning Kamp" <[EMAIL PROTECTED]>; <[EMAIL PROTECTED]>
Sent: Monday, February 10, 2003 12:38 PM
Subject: Re: kld problem ? (was: Re: MSDOSFS wastes 256k when nothing is
mounted!)
> On Sun, Feb 09, 2003 at 10:16:21PM +0200, Alexey Zelkin wrote the words in
effect of:
> > hi,
> >
> > On Sun, Feb 09, 2003 at 08:39:59PM +0100, Poul-Henning Kamp wrote:
> >
> > > /*ARGSUSED*/
> > > int
> > > msdosfs_init(vfsp)
> > > struct vfsconf *vfsp;
> > > {
> > > dehashtbl = hashinit(desiredvnodes/2, M_MSDOSFSMNT, &dehash);
> > > mtx_init(&dehash_mtx, "msdosfs dehash", NULL, MTX_DEF);
> > > return (0);
> > > }
> >
> > BTW, it reminds me a problem I found last month. If you've MSDOSFS
> > compiled in kernel and try to load msdosfs.ko with loader -- then
> > you're 100% will hit into 'mutex already initialized' (or something
> > like that) panic later in boot process. (i.e. msdosfs_init() is called
> > twice for some reason)
> >
> > I not sure if it's applicable to KLDs at all or to msdosfs only.
>
> This also happens when the Linux kernel module is loaded twice.
> Cheers.
I've seen this occur with at least one device/pseudodevice module before: if
I both compiled itinto my kernel and have it loaded in /boot/loader.conf, my
machine panics almost immediately.
At the time I just assumed I was being a moron for trying to load the same
driver twice, two different ways, and disabled the kld. If this isn't
supposed to happen I'll go back and try to find the modules that gave me
problems.
(I *think* it was either random.ko or procfs.ko).
--Mike
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message
Two witness panics in vfs_bio
recursed on non-recursive lock (sleep mutex) needsbuffer lock @
/local0/src-client/sys/kern/vfs_bio.c:1159
first acquired @ /local0/src-client/sys/kern/vfs_bio.c:1151
panic: recurse
Debugger("panic")
Stopped at Debugger+0x54: xchgl %ebx,in_Debugger.0
db> trace
Debugger(c041c671,c048f620,c041f142,d8da9b00,1) at Debugger+0x54
panic(c041f142,c0421d15,47f,c0421d15,487) at panic+0xab
witness_lock(c04b4e20,8,c0421d15,487,c0492508) at witness_lock+0x3a4
_mtx_lock_flags(c04b4e20,0,c0421d15,487,0) at _mtx_lock_flags+0xb1
bwillwrite(0,c0498960,0,0,0) at bwillwrite+0x148
kern_rename(c55b8d20,8091480,bfbfcbe0,0,d8da9d40) at kern_rename+0x1e
rename(c55b8d20,d8da9d10,c0436514,407,2) at rename+0x29
syscall(808002f,bfbf002f,bfbf002f,8090b00,bfbfcbe0) at syscall+0x28e
Xint0x80_syscall() at Xint0x80_syscall+0x1d
--- syscall (128, FreeBSD ELF32, rename), eip = 0x2819e538, esp = 0xbfbec794, ebp =
0xbfbfd3e0 ---
db>
/local0/src-client/sys/kern/kern_synch.c:152: sleeping with "buf queue lock" locked
from /local0/src-client/sys/kern/vfs_bio.c:1778
Debugger("witness_sleep")
Stopped at Debugger+0x54: xchgl %ebx,in_Debugger.0
db> trace
Debugger(c03f4e18,c041ce2d,98,c041f4e1,c0421d48) at Debugger+0x54
witness_sleep(0,c04b4e20,c041ce2d,98,1) at witness_sleep+0x135
msleep(c04b4e14,c04b4e20,50,c0421c6e,0) at msleep+0x73
getnewbuf(0,0,4000,4000,0) at getnewbuf+0x543
geteblk(4000,0,0,d6810aac,c0223ca8) at geteblk+0x3c
spec_freeblks(d6810b10,d6810b3c,c035553c,d6810b10,0) at spec_freeblks+0x35
spec_vnoperate(d6810b10,0,16f60,0,0) at spec_vnoperate+0x18
ffs_blkfree(c45cc000,c45d5b18,48e408,0,4000) at ffs_blkfree+0x1fc
indir_trunc(c642a400,11fe040,0,0,c) at indir_trunc+0x335
handle_workitem_freeblocks(c642a400,0,2,c04925f8,c4029600) at
handle_workitem_freeblocks+0x21e
process_worklist_item(0,0,3e47df7e,0,c0423463) at process_worklist_item+0x1ed
softdep_process_worklist(0,0,c0423463,6dc,0) at softdep_process_worklist+0xc0
sched_sync(0,d6810d48,c041a2d8,361,3e722020) at sched_sync+0x2ee
fork_exit(c02ae1f0,0,d6810d48) at fork_exit+0xc4
fork_trampoline() at fork_trampoline+0x1a
--- trap 0x1, eip = 0, esp = 0xd6810d7c, ebp = 0 ---
db>
msg52164/pgp0.pgp
Description: PGP signature
Re: kld problem ? (was: Re: MSDOSFS wastes 256k when nothing is mounted!)
On Sun, Feb 09, 2003 at 10:16:21PM +0200, Alexey Zelkin wrote the words in effect of:
> hi,
>
> On Sun, Feb 09, 2003 at 08:39:59PM +0100, Poul-Henning Kamp wrote:
>
> > /*ARGSUSED*/
> > int
> > msdosfs_init(vfsp)
> > struct vfsconf *vfsp;
> > {
> > dehashtbl = hashinit(desiredvnodes/2, M_MSDOSFSMNT, &dehash);
> > mtx_init(&dehash_mtx, "msdosfs dehash", NULL, MTX_DEF);
> > return (0);
> > }
>
> BTW, it reminds me a problem I found last month. If you've MSDOSFS
> compiled in kernel and try to load msdosfs.ko with loader -- then
> you're 100% will hit into 'mutex already initialized' (or something
> like that) panic later in boot process. (i.e. msdosfs_init() is called
> twice for some reason)
>
> I not sure if it's applicable to KLDs at all or to msdosfs only.
This also happens when the Linux kernel module is loaded twice.
Cheers.
--
Hiten Pandya ([EMAIL PROTECTED], [EMAIL PROTECTED])
http://www.unixdaemons.com/~hiten/
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message
Re: firewire hangs on Thinkpad
On Sun, Feb 09, 2003 at 10:06:54AM -0700, M. Warner Losh wrote: > Maybe something more like the following would be closer to correct: > Yes, that seems to work. After changing carbus.c as you suggested, kldload'ing sbp.ko and inserting the card results in: brian# cbb0: card inserted: event=0x, state=3920 cbb0: cbb_power: CARD_VCC_0V and CARD_VPP_0V [44] cbb0: cbb_power: CARD_VCC_3V and CARD_VPP_VCC [11] found-> vendor=0x104c, dev=0x8023, revid=0x00 class=0c-00-10, hdrtype=0x00, mfdev=0 cmdreg=0x, statreg=0x0210, cachelnsz=8 (dwords) lattimer=0xa8 (5040 ns), mingnt=0x02 (500 ns), maxlat=0x04 (1000 ns) intpin=a, irq=255 cardbus0: Expecting link target, got 0x42 cardbus0: Resource not specified in CIS: id=10, size=800 cardbus0: Resource not specified in CIS: id=14, size=4000 cardbus0: Resource not specified in CIS: id=18, size=800 cardbus0: Non-prefetchable memory at 88004000-88008fff cardbus0: Non-prefetchable memory rid=14 at 88004000-88007fff (4000) cardbus0: Non-prefetchable memory rid=18 at 88008000-880087ff (800) cardbus0: Non-prefetchable memory rid=10 at 88008800-88008fff (800) fwohci0: mem 0x88008000-0x880087ff,0x88004000-0x 88007fff,0x88008800-0x88008fff irq 11 at device 0.0 on cardbus0 fwohci0: PCI bus latency was changing to 250. fwohci0: OHCI version 1.10 (ROM=1) fwohci0: No. of Isochronous channel is 4. fwohci0: EUI64 00:01:fb:00:00:00:00:6e fwohci0: Phy 1394a available S400, 2 ports. fwohci0: Link S400, max_rec 2048 bytes. firewire0: on fwohci0 sbp0: on firewire0 fwohci0: Initiate bus reset fwohci0: BUS reset fwohci0: BUS reset fwohci0: node_id = 0xc000ffc0, CYCLEMASTER mode firewire0: 1 nodes, maxhop <= 0, cable IRM = 0 (me) However, if I do it in the opposite direction, i.e. I load sbp.ko when the card is already in the system I get: found-> vendor=0x104c, dev=0x8023, revid=0x00 class=0c-00-10, hdrtype=0x00, mfdev=0 cmdreg=0x, statreg=0x0210, cachelnsz=8 (dwords) lattimer=0xa8 (5040 ns), mingnt=0x02 (500 ns), maxlat=0x04 (1000 ns) intpin=a, irq=11 cardbus0: Bad header in rom 0: [0] fwohci0: at device 0.0 on cardbus0 fwohci0: PCI bus latency is 255. fwohci0: Could not map memory device_probe_and_attach: fwohci0 attach returned 6 This might be completely unrelated but it might help you, I don't know. What's weird is that my Thinkpad 570E has never had any problem recognizing cards already present at boot, for instance. Bye, Andrea -- To boldly go where I surely don't belong. To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: bus_setup_intr() vs. ether_ifattach() race
On Sun, 9 Feb 2003, Nate Lawson wrote: > Which is the correct order to do these two functions? If the irq is > enabled before the device is attached, it seems a response cannot be > sent if a packet arrives before the attach. The right way seems to be > to attach the device before setting up an irq but does this have side > effects? The interrupt handler should be checking IFF_UP. The driver shouldn't enable card interrupts until if_init() has been run and should disable them in it foo_stop() routine (or when the interface is brought down, detached etc.) -- | Matthew N. Dodd | '78 Datsun 280Z | '75 Volvo 164E | FreeBSD/NetBSD | | [EMAIL PROTECTED] | 2 x '84 Volvo 245DL| ix86,sparc,pmax | | http://www.jurai.net/~winter | For Great Justice! | ISO8802.5 4ever | To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: Synaptics touchpad support
Hi, Rahul Siddharthan wrote: Paul A. Mayer said on Feb 10, 2003 at 11:01:45: Hi Rahul, Well, it compiles on 5.0-Release-p1. The psm initialization gives some specs about the device and some of it's features. ... but I don't see any consequences of this in apps, like mozilla. And under gnome the pressure sensitivity of the touchpad (e.g., tap to click) is now gone. Yes, this was noted back then. See http://docs.freebsd.org/cgi/getmsg.cgi?fetch=0+0+archive/2003/freebsd-hackers/20030112.freebsd-hackers I have no great understanding of how any of this should work. Can you give some pointers. (How do I get touch sensitivity back? How should it be configured into X? Where should I be able to see the effects of the patch?) Well, without doing anything, you should be able to see some activity from the "up" button: in my case, it worked by default as a middle button, while the "down" button did nothing but showed up in xev, for example. Basically, left=1, up=2 right=3 ,down=4. What I really wanted was for "up" to mean up, "down" to mean down, and I was happy to emulate "middle" with simultaneous left-right as before. The following does it for me: I run moused with the options -m 5=4 -m 4=2 -a 0.5 (the -a is because this driver scales the speed up a bit too much for my liking). And in my XF86Config I have Option "Emulate3Buttons" Option "Buttons" "5" I *don't* have the Option "ZAxisMapping "4 5" which the howto's for wheel mice will tell you to insert -- seems it's there by default. And if I insert it, curiously, it stops working... This was very helpful and works as you describe. Thank you very much! /Paul To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: Synaptics touchpad support
Hi, Terry Lambert wrote: "Paul A. Mayer" wrote: You actually lose the tap/tap-tap click and doubleclick button emulation with the new driver, and, as you note, the pressure sensitivity. Both of these issues were noted when the driver was posted for review. It semed the consensus at the time that until at least the tap/tap-tap was brought back (via software emulation), the driver would not be replaced, only optioned. You can check the list archives for details, I think. I wasn't aware of the prehistory ... (Rahul's link in another post was very interesting.) The "pressure sensitivity is, I think, really an area sensitivity and not a real pressure sensitivity (I can't imagine actually losing an axis of data!). That would mean, like the tap/tap-tap, it could be emulated in software. It would be interesting to get this back. I can (and have) lived without the "roller" buttons, but I wasn't aware of how used I had become to tapping instead of clicking. Probably the best thing to do would be to disassemble the BIOS on your box, knowing the difference between the older driver's interface, and use the same techniques that were hidden from the older driver (and "just built in" instead). This is certainly beyond my technical understanding! /Paul To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: Synaptics touchpad support
Terry Lambert said on Feb 10, 2003 at 04:07:25: > > You actually lose the tap/tap-tap click and doubleclick button > emulation with the new driver, and, as you note, the pressure > sensitivity. > > Both of these issues were noted when the driver was posted for > review. It semed the consensus at the time that until at least > the tap/tap-tap was brought back (via software emulation), the > driver would not be replaced, only optioned. You can check the > list archives for details, I think. I don't think there was a consensus, by anyone "in the know". I don't think any committer responded in the whole thread. Personally, at the time I was ambivalent, but now I'm happy it's gone... Perhaps it can indeed be reimplemented in userspace software. R To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: Synaptics touchpad support
Paul A. Mayer said on Feb 10, 2003 at 11:01:45: > Hi Rahul, > > Well, it compiles on 5.0-Release-p1. The psm initialization gives some > specs about the device and some of it's features. ... but I don't see > any consequences of this in apps, like mozilla. And under gnome the > pressure sensitivity of the touchpad (e.g., tap to click) is now gone. Yes, this was noted back then. See http://docs.freebsd.org/cgi/getmsg.cgi?fetch=0+0+archive/2003/freebsd-hackers/20030112.freebsd-hackers > I have no great understanding of how any of this should work. Can you > give some pointers. (How do I get touch sensitivity back? How should > it be configured into X? Where should I be able to see the effects of > the patch?) Well, without doing anything, you should be able to see some activity from the "up" button: in my case, it worked by default as a middle button, while the "down" button did nothing but showed up in xev, for example. Basically, left=1, up=2 right=3 ,down=4. What I really wanted was for "up" to mean up, "down" to mean down, and I was happy to emulate "middle" with simultaneous left-right as before. The following does it for me: I run moused with the options -m 5=4 -m 4=2 -a 0.5 (the -a is because this driver scales the speed up a bit too much for my liking). And in my XF86Config I have Option "Emulate3Buttons" Option "Buttons" "5" I *don't* have the Option "ZAxisMapping "4 5" which the howto's for wheel mice will tell you to insert -- seems it's there by default. And if I insert it, curiously, it stops working... - Rahul To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: HEADS UP: GCC 3.2.2 is coming
Alexander Kabaev said on Feb 10, 2003 at 08:31:43: > Apparently, you caught the src tree at the bad moment. See if another > cvsup/buildworld changes anything. Yes, it works now. Thanks and sorry for false alarm. R > On Mon, 10 Feb 2003 02:33:48 -0500 > Rahul Siddharthan <[EMAIL PROTECTED]> wrote: > > > Alexander Kabaev wrote: > > > The import should be complete now. Please let us know if you > > > see any problems introduced with this GCC version. > > > > > > cc -O -pipe -mcpu=i686 -march=i686 -DIN_GCC -DHAVE_CONFIG_H > > -DPREFIX=\"/usr/obj/usr/src/i386/usr\" > > -I/usr/obj/usr/src/i386/usr/src/gnu/usr.bin/cc/cc1plus/../cc_tools > > -I/usr/src/gnu/usr.bin/cc/cc1plus/../cc_tools > > -I/usr/src/gnu/usr.bin/cc/cc1plus/../../../../contrib/gcc > > -I/usr/src/gnu/usr.bin/cc/cc1plus/../../../../contrib/gcc/config > > -I/usr/src/gnu/usr.bin/cc/cc1plus/../../../../contrib/gcc/cp -I. > >-c /usr/src/contrib/gcc/cp/decl.c > > /usr/src/contrib/gcc/cp/decl.c: In function > > `cxx_init_decl_processing': > > /usr/src/contrib/gcc/cp/decl.c:6671: `c_size_type_node' undeclared > > (first use in this function) > > /usr/src/contrib/gcc/cp/decl.c:6671: (Each undeclared identifier is > > reported only once > > /usr/src/contrib/gcc/cp/decl.c:6671: for each function it appears in.) > > *** Error code 1 > > > > > > > -- > Alexander Kabaev To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: HEADS UP: GCC 3.2.2 is coming
Apparently, you caught the src tree at the bad moment. See if another cvsup/buildworld changes anything. On Mon, 10 Feb 2003 02:33:48 -0500 Rahul Siddharthan <[EMAIL PROTECTED]> wrote: > Alexander Kabaev wrote: > > The import should be complete now. Please let us know if you > > see any problems introduced with this GCC version. > > > cc -O -pipe -mcpu=i686 -march=i686 -DIN_GCC -DHAVE_CONFIG_H > -DPREFIX=\"/usr/obj/usr/src/i386/usr\" > -I/usr/obj/usr/src/i386/usr/src/gnu/usr.bin/cc/cc1plus/../cc_tools > -I/usr/src/gnu/usr.bin/cc/cc1plus/../cc_tools > -I/usr/src/gnu/usr.bin/cc/cc1plus/../../../../contrib/gcc > -I/usr/src/gnu/usr.bin/cc/cc1plus/../../../../contrib/gcc/config > -I/usr/src/gnu/usr.bin/cc/cc1plus/../../../../contrib/gcc/cp -I. >-c /usr/src/contrib/gcc/cp/decl.c > /usr/src/contrib/gcc/cp/decl.c: In function > `cxx_init_decl_processing': > /usr/src/contrib/gcc/cp/decl.c:6671: `c_size_type_node' undeclared > (first use in this function) > /usr/src/contrib/gcc/cp/decl.c:6671: (Each undeclared identifier is > reported only once > /usr/src/contrib/gcc/cp/decl.c:6671: for each function it appears in.) > *** Error code 1 > > -- Alexander Kabaev To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: Best method to produce patches?
On Sun, Feb 09, 2003 at 04:33:41PM -0600, David Leimbach wrote: > I am about to try to make some changes to FreeBSD current... > > What is the recommend method to use for playing with the source? I've attached an e-mail from Matt Dillon that gives a very good de- scription for setting up a FreeBSD development environment. > Thanks! > > Dave Leimbach Date: Sat, 21 Dec 2002 16:41:23 -0800 (PST) From: Matthew Dillon <[EMAIL PROTECTED]> To: Trent Nelson <[EMAIL PROTECTED]> Subject: Re: Trying to chase up an old post. :Hi Matt, : :You posted something to [EMAIL PROTECTED] (or hackers@ possibly) :just over a year ago describing how you set up your -stable and :-current environments for doing development. : :I've attempted to search for the post, but I'm coming up with false :hits left right and centre. Any idea which post I'm referring to, :or even better, can you point me to a URL where it's been archived? : :Much appreciated. : :Regards, : :Trent. : :-- :Trent Nelson -- Director, Alcyon Enterprises, Ltd. I remember making the post, but I don't remember when and I doubt I could find it in my archives. Hmm. This would be another good manual page. Maybe I will call it 'developer' or 'development'. Ok, here we go: ENVIRONMENT SETUP Basically I recommend having at least two machines. Run -stable on your main development system. Create a huge partition called /FreeBSD. Mine is 12GB (and currently holds 8G of junk in it, including portions of NetBSD, OpenBSD, and Linux as well as FreeBSD). REASON>> This way you can export /FreeBSD to any other machines you have via read-only NFS without exposing sensitive partitions on your main development machine. REASON>> You always want your main development environment to be on a stable, reliable platform, otherwise you might blow something up and then not be able to fix it. Use cvsup (once a night via cron) to keep a local copy of the FreeBSD CVS tree. mkdir /FreeBSD/FreeBSD-CVS ln -s /FreeBSD/FreeBSD-CVS /home/ncvs cron entry: 20 6 * * * /usr/local/bin/cvsup -g -r 20 -L 2 -h cvsup.freebsd.org /usr/share/examples/cvsup/cvs-supfile Then use cvs to checkout and maintain a -stable source tree and a -current source tree. I do this: mkdir /FreeBSD/FreeBSD-4.x mkdir /FreeBSD/FreeBSD-current cd /FreeBSD/FreeBSD-4.x cvs -d /home/ncvs checkout -rRELENG_4 src cd /FreeBSD/FreeBSD-current cvs -d /home/ncvs checkout src cvs -d /home/ncvs checkout ports cvs -d /home/ncvs checkout doc REASON>> Keeping the broken-out source in /FreeBSD allows you to export it to other machines along with the rest of the development environment. Now create a softlink for /usr/src and /usr/src2. I usually point /usr/src at -stable and /usr/src2 at -current: cd /usr rm -rf src src2 ln -s /FreeBSD/FreeBSD-4.x/src src ln -s /FreeBSD/FreeBSD-current/src src Put /usr/obj in /FreeBSD as well, or give it its own partition (at least 4GB is recommended). Example: mkdir /FreeBSD/obj cd /usr rm -rf obj ln -s /FreeBSD/obj obj ALTERNATIVE: (/usr/obj has its own partition) REASON>> you are going to want to export /usr/obj via read-only NFS to your other boxes, which I explain in the BUILDING section. If you want to be able to compile the world and kernels on the clients, rather then only compiling on your main development box, I recommend making /usr/obj its own partition to make it easier to give each client its own /usr/obj (for client-side compiling), or mounting /usr/obj on the client from the main development server via read-only NFS. I usually keep track of ports via CVS and, as you can see above, a checkedout version can be maintained in /FreeBSD/FreeBSD-current/ports. However, in order to be able to build ports on other machines you will need to change the distfiles subdirectory: cd /usr rm -rf ports ln -s /FreeBSD/FreeBSD-current/ports ports cd /usr/ports (this pushes into the softlink) rm -rf distfiles ln -s /usr/ports.distfiles distfiles mkdir /usr/ports.distfiles mkdir /usr/ports.workdir IN /etc/make.conf add -- WRKDIRPREFIX=/usr/ports.workdir -- REASON>> This allows you to export /usr/ports via a read-only NFS mount. In fact, just exporting /FreeBSD also gives you ports for free and on your other machines you can simply softlink /usr/ports to /FreeBSD/FreeBSD-current/ports. NOT!!! You may want to choose different directories for distfiles and workdir, but try to mak
Re: Comments welcome: 1-line patch: teach FTP_PASSIVE_MODE to${CHROOT}/mk
Makoto Matsushita <[EMAIL PROTECTED]> writes: > You know there are many solutions about this issue. IIRC, it can be > easily fixed with "passing FTP_PASSIVE_MODE variable to the chroot > sandbox." Following patch was tested on FreeBSD/i386, and it should > work on other archs since this is arch-independent code. You may want to do the same thing with HTTP_PROXY and FTP_PROXY. DES -- Dag-Erling Smorgrav - [EMAIL PROTECTED] To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: RE : IPFilter
Coercitas Temet'Nosce wrote: Pardon my poor knowledge about IPFW 2 but if I remember well, IPFW wasn't a SPI Firewall, which is what I need. Btw, previous Kernel allows us to fine tune its building for IPF and now, it simply gone...was really wondering where those features are. What, exactly, is a 'SPI' firewall? If you mean stateful firewall, you haven't looking into ipfw for at least five years (making your remark obsolete, not ipfw :). The only thing I couldn't do with the old ipfw was atomic replacement of rules. With ipfw2 I can do that. ipfw2 is default on 5.0 and can be turned on on 4.7 (options IPFW2 on kernel and WITH_IPFW2, iirc, on make.conf). The '2' is the version, the binary, man pages etc still have all the same names. Is there any web place where I can find stuff about IPFW2 by chance ? regards -Message d'origine- De : [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]] De la part de Don Envoyé : dimanche 9 février 2003 19:47 À : Coercitas Temet'Nosce Cc : [EMAIL PROTECTED] Objet : Re: TR : IPFilter Btw, I was looking for some docs on the FreeBSD website and didn't found anything interesting, only firewall that FreeBSD seems to support nowadays is the old IPFW, which is quite obsolete now imo. Why are documentation pages not dealing with IPF at all ? is there any reason ? Try ipfw2 -Don 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 -- Daniel C. Sobral (8-DCS) Gerencia de Operacoes Divisao de Comunicacao de Dados Coordenacao de Seguranca TCO Fones: 55-61-313-7654/Cel: 55-61-9618-0904 E-mail: [EMAIL PROTECTED] [EMAIL PROTECTED] [EMAIL PROTECTED] Outros: [EMAIL PROTECTED] [EMAIL PROTECTED] [EMAIL PROTECTED] The past always looks better than it was. It's only pleasant because it isn't here. -- Finley Peter Dunne (Mr. Dooley) To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Comments welcome: 1-line patch: teach FTP_PASSIVE_MODE to${CHROOT}/mk
I'd like to commit following patch to src/release/Makefile. Here's background: A user may want to build their own FreeBSD distribution. During the release build, pkg_add(1) runs within chroot sandbox to install mkisofs(8) iff MAKE_ISOS=YES. Imagine what's happen if the user is living behind the Internet firewall -- pkg_add(1) try to fetch the package from outside but it can't since firewall usually doesn't allow outer-to-inner connections. According to the pkg_add(1) manpage, FTP_PASSIVE_MODE environment variable enables passive ftp connections. You know there are many solutions about this issue. IIRC, it can be easily fixed with "passing FTP_PASSIVE_MODE variable to the chroot sandbox." Following patch was tested on FreeBSD/i386, and it should work on other archs since this is arch-independent code. If there's no problem around, I'll commit it later. Any comments and/or suggestions are welcome. -- - Makoto `MAR' Matsushita Index: Makefile === RCS file: /home/ncvs/src/release/Makefile,v retrieving revision 1.749 diff -u -r1.749 Makefile --- Makefile4 Feb 2003 16:07:20 - 1.749 +++ Makefile10 Feb 2003 11:19:41 - @@ -430,6 +430,7 @@ DOMINIMALDOCPORTS \ EXTRA_SRC \ FIXCRYPTO \ + FTP_PASSIVE_MODE \ KERNELS \ KERNEL_FLAGS \ MAKE_ISOS \ To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
alpha tinderbox failure
-- >>> Rebuilding the temporary build tree -- >>> stage 1: bootstrap tools -- >>> stage 2: cleaning up the object tree -- >>> stage 2: rebuilding the object tree -- >>> stage 2: build tools -- >>> stage 3: cross tools -- >>> stage 4: populating /home/des/tinderbox/alpha/obj/h/des/src/alpha/usr/include -- >>> stage 4: building libraries -- >>> stage 4: make dependencies -- >>> stage 4: building everything.. -- >>> Kernel build for GENERIC started on Mon Feb 10 03:14:59 PST 2003 -- >>> Kernel build for GENERIC completed on Mon Feb 10 03:46:44 PST 2003 -- >>> Kernel build for LINT started on Mon Feb 10 03:46:45 PST 2003 -- ===> vinum "Makefile", line 4458: warning: duplicate script for target "geom_bsd.o" ignored /h/des/src/sys/dev/lmc/if_lmc.c:32:2: warning: #warning "The lmc driver is broken and is not compiled with LINT" /h/des/src/sys/dev/pdq/pdq.c: In function `pdq_initialize': /h/des/src/sys/dev/pdq/pdq.c:1606: warning: cast discards qualifiers from pointer target type /h/des/src/sys/pci/meteor.c:149:2: warning: #warning "The meteor driver is broken and is not compiled with LINT" /h/des/src/sys/pci/simos.c:30:2: warning: #warning "The simos driver is broken and is not compiled with LINT" /h/des/src/sys/dev/gfb/gfb_pci.c: In function `pcigfb_open': /h/des/src/sys/dev/gfb/gfb_pci.c:268: `gfb_devclass' undeclared (first use in this function) /h/des/src/sys/dev/gfb/gfb_pci.c:268: (Each undeclared identifier is reported only once /h/des/src/sys/dev/gfb/gfb_pci.c:268: for each function it appears in.) cc1: warnings being treated as errors /h/des/src/sys/dev/gfb/gfb_pci.c:275: warning: passing arg 1 of `genfbopen' from incompatible pointer type /h/des/src/sys/dev/gfb/gfb_pci.c: In function `pcigfb_close': /h/des/src/sys/dev/gfb/gfb_pci.c:284: `gfb_devclass' undeclared (first use in this function) /h/des/src/sys/dev/gfb/gfb_pci.c:285: warning: passing arg 1 of `genfbclose' from incompatible pointer type /h/des/src/sys/dev/gfb/gfb_pci.c: In function `pcigfb_read': /h/des/src/sys/dev/gfb/gfb_pci.c:293: `gfb_devclass' undeclared (first use in this function) /h/des/src/sys/dev/gfb/gfb_pci.c:294: warning: passing arg 1 of `genfbread' from incompatible pointer type /h/des/src/sys/dev/gfb/gfb_pci.c: In function `pcigfb_write': /h/des/src/sys/dev/gfb/gfb_pci.c:302: `gfb_devclass' undeclared (first use in this function) /h/des/src/sys/dev/gfb/gfb_pci.c:303: warning: passing arg 1 of `genfbwrite' from incompatible pointer type /h/des/src/sys/dev/gfb/gfb_pci.c: In function `pcigfb_ioctl': /h/des/src/sys/dev/gfb/gfb_pci.c:311: `gfb_devclass' undeclared (first use in this function) /h/des/src/sys/dev/gfb/gfb_pci.c:312: warning: passing arg 1 of `genfbioctl' from incompatible pointer type /h/des/src/sys/dev/gfb/gfb_pci.c: In function `pcigfb_mmap': /h/des/src/sys/dev/gfb/gfb_pci.c:320: `gfb_devclass' undeclared (first use in this function) /h/des/src/sys/dev/gfb/gfb_pci.c:321: warning: passing arg 1 of `genfbmmap' from incompatible pointer type *** Error code 1 Stop in /h/des/obj/h/des/src/sys/LINT. *** Error code 1 Stop in /h/des/src. *** Error code 1 Stop in /h/des/src. To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: Synaptics touchpad support
"Paul A. Mayer" wrote: > Well, it compiles on 5.0-Release-p1. The psm initialization gives some > specs about the device and some of it's features. ... but I don't see > any consequences of this in apps, like mozilla. And under gnome the > pressure sensitivity of the touchpad (e.g., tap to click) is now gone. > > I have no great understanding of how any of this should work. Can you > give some pointers. (How do I get touch sensitivity back? How should > it be configured into X? Where should I be able to see the effects of > the patch?) You actually lose the tap/tap-tap click and doubleclick button emulation with the new driver, and, as you note, the pressure sensitivity. Both of these issues were noted when the driver was posted for review. It semed the consensus at the time that until at least the tap/tap-tap was brought back (via software emulation), the driver would not be replaced, only optioned. You can check the list archives for details, I think. The "pressure sensitivity is, I think, really an area sensitivity and not a real pressure sensitivity (I can't imagine actually losing an axis of data!). That would mean, like the tap/tap-tap, it could be emulated in software. Probably the best thing to do would be to disassemble the BIOS on your box, knowing the difference between the older driver's interface, and use the same techniques that were hidden from the older driver (and "just built in" instead). -- Terry To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: Does bg fsck have problems with large filesystems?
Hello, > > I also gave him access to our machine, which has a 1.2 TB filesystem > > on it. > I have a 1.9TB FS about 4 km from him.. That's great! Could you please contact him? (do you also have this problem, BTW?) Thanks, --[ Free Software ISOs - http://www.fsn.hu/?f=download ]-- Attila Nagy e-mail: [EMAIL PROTECTED] Free Software Network (FSN.HU)phone @work: +361 210 1415 (194) cell.: +3630 306 6758 To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Problems with Current & XFree86
Resending due to the fact that I didn' include the /var/log/XFree86.0.log I have a Compaq Evo N800c witch runs with 4.7-STABLE and XFree86 with no problems. The exact same configuration for X and same version of XFree86-libs etc does not run on Current a few days old. The problems started a few weeks ago. just for a test i cvsup-ed to the lates XFree86 code. Same result. Since it works with 4.7-STABLE it must(?) be a current problem more than a XFree86 problem. Or? Any suggestions? Attaching the log file -- Gunnar Flygt, Postmaster SR This is a pre-release version of XFree86, and is not supported in any way. Bugs may be reported to [EMAIL PROTECTED] and patches submitted to [EMAIL PROTECTED] Before reporting bugs in pre-release versions, please check the latest version in the XFree86 CVS repository (http://www.XFree86.Org/cvs). XFree86 Version 4.2.99.901 (4.3.0 RC 1) Release Date: 8 February 2003 X Protocol Version 11, Revision 0, Release 6.6 Build Operating System: FreeBSD 5.0-CURRENT i386 [ELF] Build Date: 10 February 2003 Before reporting problems, check http://www.XFree86.Org/ to make sure that you have the latest version. Module Loader present Markers: (--) probed, (**) from config file, (==) default setting, (++) from command line, (!!) notice, (II) informational, (WW) warning, (EE) error, (NI) not implemented, (??) unknown. (==) Log file: "/var/log/XFree86.0.log", Time: Mon Feb 10 11:15:19 2003 (==) Using config file: "/usr/X11R6/lib/X11/XF86Config-4" (==) ServerLayout "XFree86 Configured" (**) |-->Screen "Screen0" (0) (**) | |-->Monitor "Monitor0" (**) | |-->Device "Card0" (**) |-->Input Device "Mouse0" (**) |-->Input Device "Keyboard0" (**) Option "XkbRules" "xfree86" (**) XKB: rules: "xfree86" (**) Option "XkbModel" "pc105" (**) XKB: model: "pc105" (**) Option "XkbLayout" "se" (**) XKB: layout: "se" (**) Option "XkbOptions" "compose:rwin" (**) XKB: options: "compose:rwin" (==) Keyboard: CustomKeycode disabled (**) FontPath set to "/usr/X11R6/lib/X11/fonts/misc/,/usr/X11R6/lib/X11/fonts/Speedo/,/usr/X11R6/lib/X11/fonts/Type1/,/usr/X11R6/lib/X11/fonts/75dpi/,/usr/X11R6/lib/X11/fonts/100dpi/" (**) RgbPath set to "/usr/X11R6/lib/X11/rgb" (**) ModulePath set to "/usr/X11R6/lib/modules" (--) Using syscons driver with X support (version 2.0) (--) using VT number 9 (II) Module ABI versions: XFree86 ANSI C Emulation: 0.2 XFree86 Video Driver: 0.6 XFree86 XInput driver : 0.4 XFree86 Server Extension : 0.2 XFree86 Font Renderer : 0.4 (II) Loader running on freebsd (II) LoadModule: "bitmap" (II) Loading /usr/X11R6/lib/modules/fonts/libbitmap.a (II) Module bitmap: vendor="The XFree86 Project" compiled for 4.2.99.901, module version = 1.0.0 Module class: XFree86 Font Renderer ABI class: XFree86 Font Renderer, version 0.4 (II) Loading font Bitmap (II) LoadModule: "pcidata" (II) Loading /usr/X11R6/lib/modules/libpcidata.a (II) Module pcidata: vendor="The XFree86 Project" compiled for 4.2.99.901, module version = 1.0.0 ABI class: XFree86 Video Driver, version 0.6 (II) PCI: Probing config type using method 1 (II) PCI: Config type is 1 (II) PCI: stages = 0x03, oldVal1 = 0x, mode1Res1 = 0x8000 (II) PCI: PCI scan (all values are in hex) (II) PCI: 00:00:0: chip 8086,1a30 card 0e11,004a rev 04 class 06,00,00 hdr 00 (II) PCI: 00:01:0: chip 8086,1a31 card , rev 04 class 06,04,00 hdr 01 (II) PCI: 00:1e:0: chip 8086,2448 card , rev 42 class 06,04,00 hdr 01 (II) PCI: 00:1f:0: chip 8086,248c card , rev 02 class 06,01,00 hdr 80 (II) PCI: 00:1f:1: chip 8086,248a card 0e11,004a rev 02 class 01,01,8a hdr 00 (II) PCI: 00:1f:5: chip 8086,2485 card 0e11,004a rev 02 class 04,01,00 hdr 00 (II) PCI: 01:00:0: chip 1002,4c57 card 0e11,004a rev 00 class 03,00,00 hdr 00 (II) PCI: 02:04:0: chip 11c1,0450 card 1468,0450 rev 02 class 07,80,00 hdr 00 (II) PCI: 02:06:0: chip 104c,ac50 card fffc, rev 02 class 06,07,00 hdr 02 (II) PCI: 02:08:0: chip 8086,1031 card 0e11,0093 rev 42 class 02,00,00 hdr 00 (II) PCI: 02:0e:0: chip 1033,0035 card 0e11,004a rev 41 class 0c,03,10 hdr 80 (II) PCI: 02:0e:1: chip 1033,0035 card 0e11,004a rev 41 class 0c,03,10 hdr 00 (II) PCI: 02:0e:2: chip 1033,00e0 card 0e11,004a rev 02 class 0c,03,20 hdr 00 (II) PCI: End of PCI scan (II) Host-to-PCI bridge: (II) Bus 0: bridge is at (0:0:0), (0,0,3), BCTRL: 0x0008 (VGA_EN is set) (II) Bus 0 I/O range: [0] -1 0 0x - 0x (0x1) IX[B] (II) Bus 0 non-prefetchable memory range: [0] -1 0 0x - 0x (0x0) MX[B] (II) Bus 0 prefetchable memory range: [0] -1 0 0x - 0x (0x0) MX[B] (II) PCI-to-PCI bridge: (II) Bus 1: bridge is at (0:1:0), (0,1,1), BCTRL: 0x000c (VGA_EN is set) (II) Bus 1 I/O range: [0] -1 0 0x3000 - 0x30ff (0x100) IX[B] [1] -1 0 0x3400 - 0x34ff (0x100) IX[B]
Abysmal performance for restore -r
Since growfs still doesn't work, i needed to newfs & restore the following filesystem after expanding the volume: uriah # df -k -i /dev/vinum/home_cvs Filesystem 1K-blocksUsed Avail Capacity iused ifree %iused Mounted on /dev/vinum/home_cvs 4125838 2911856 88391677% 235970 305724 44% /home/cvs restore(8)ing it from tape took about 7.5 hours(!) in order to create the 34332 directory inodes on it; that's about 1.2 directory creations per second. The machine was basically grinding to a halt while this happened, iostat (when it was possible to report something at all) reported > 350 transactions per second for both participating disks (which doesn't sound all that bad to me, the disks are 1 rpm not too old drives). In contrast, restoring the ~ 3 GB of contents (still > 25 files) didn't even take an hour to complete. The filesystem has been newfs'ed with defaults + softupdates: uriah # newfs -N -U /dev/vinum/home_cvs /dev/vinum/home_cvs: 4096.0MB (8388608 sectors) block size 16384, fragment size 2048 using 23 cylinder groups of 183.69MB, 11756 blks, 23552 inodes. with soft updates Does anybody have an idea why this was so terrible slow? (The kernel is at 5.0-RCsomething, in case that matters.) -- cheers, J"org .-.-. --... ...-- -.. . DL8DTL http://www.sax.de/~joerg/NIC: JW11-RIPE Never trust an operating system you don't have sources for. ;-) To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: Problems with Current & XFree86
On Mon, Feb 10, 2003 at 11:20:24AM +0100, Gunnar Flygt wrote: > Since it works with 4.7-STABLE it must(?) be a current problem > more than a XFree86 problem. Or? > > Any suggestions? > > -- > Gunnar Flygt, SR Could you paste your /var/log/XFree86*.log with the error parts? Maybe some will be able to detemine the cause of the errors. JY -- "Without the userland, the kernel is useless." --inspired by The Tao of Programming To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: Does bg fsck have problems with large filesystems?
On Mon, 10 Feb 2003, Attila Nagy wrote: > Hello, > > > > I'll try to reproduce the thing on my machine as soon as possible. > > > Perhaps it was just because it was Monday, who knows... > > Meanwhile I found out that my problem is 100% reproducible. > Since then, I contacted Kirk McKusick, who told me that he will > investigate this issue. > I also gave him access to our machine, which has a 1.2 TB filesystem on > it. I have a 1.9TB FS about 4 km from him.. > > I hope he can get in before I have to take that machine into production :) > > --[ Free Software ISOs - http://www.fsn.hu/?f=download ]-- > Attila Nagy e-mail: [EMAIL PROTECTED] > Free Software Network (FSN.HU) phone @work: +361 210 1415 (194) > cell.: +3630 306 6758 > > 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
Problems with Current & XFree86
Am I the only person having problems with a laptop with Current and XFree86? I have a Compaq Evo N800c witch runs with 4.7-STABLE and XFree86 with no problems. The exact same configuration for X and same version of XFree86-libs etc does not run on Current a few days old. The problems started a few weeks ago. just for a test i cvsup-ed to the lates XFree86 code. Same result. Since it works with 4.7-STABLE it must(?) be a current problem more than a XFree86 problem. Or? Any suggestions? -- Gunnar Flygt, SR To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: Does bg fsck have problems with large filesystems?
Hello, > > I'll try to reproduce the thing on my machine as soon as possible. > > Perhaps it was just because it was Monday, who knows... > Meanwhile I found out that my problem is 100% reproducible. Since then, I contacted Kirk McKusick, who told me that he will investigate this issue. I also gave him access to our machine, which has a 1.2 TB filesystem on it. I hope he can get in before I have to take that machine into production :) --[ Free Software ISOs - http://www.fsn.hu/?f=download ]-- Attila Nagy e-mail: [EMAIL PROTECTED] Free Software Network (FSN.HU)phone @work: +361 210 1415 (194) cell.: +3630 306 6758 To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: Synaptics touchpad support
Hi Rahul, Well, it compiles on 5.0-Release-p1. The psm initialization gives some specs about the device and some of it's features. ... but I don't see any consequences of this in apps, like mozilla. And under gnome the pressure sensitivity of the touchpad (e.g., tap to click) is now gone. I have no great understanding of how any of this should work. Can you give some pointers. (How do I get touch sensitivity back? How should it be configured into X? Where should I be able to see the effects of the patch?) Thanks! /Paul Rahul Siddharthan wrote: Lest this disappear, like so much else, into the black hole that is GNATS, can some laptop user take a look at this? It works great for me, I can now scroll using the "up" and "down" touchpad buttons which were useless decorations earlier. Thanks to Marcin Dalecki. PR kern/48116 http://www.freebsd.org/cgi/query-pr.cgi?pr=48116 - Rahul 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
Re: Do we still have a FIFO / named pipe problem?
On Mon, 10 Feb 2003 04:40:34 +1100 (EST) Bruce Evans <[EMAIL PROTECTED]> wrote: > Untested fix for this and rev.1.79, and for a similar race in blocking > opens of named pipes for reading: Solves my problem. Bye, Alexander. -- Actually, Microsoft is sort of a mixture between the Borg and the Ferengi. http://www.Leidinger.net Alexander @ Leidinger.net GPG fingerprint = C518 BC70 E67F 143F BE91 3365 79E2 9C60 B006 3FE7 To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: Best method to produce patches?
Thus spake David Leimbach <[EMAIL PROTECTED]>: > I am about to try to make some changes to FreeBSD current... > > Should I begin to use read-only CVS instead of CVSup for this work or > is it possible to generate diffs based on CVSup'd sources? > > What is the recommend method to use for playing with the source? > > I already found a small change in libc that should probably get > committed but I want to generate the patch properly for everyone's > approval. The best thing to do is to have a local copy of the entire repository, synced via cvsup. If you have multiple machines, you can even run a cvsup server on one of them, and sync them all from that. On older hardware that lacks sufficient disk space for the entire repo, I use anoncvs, but that's much more annoying. You need to hack up CVS/Entries manually to add and delete files, for instance. To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: MSDOSFS wastes 256k when nothing is mounted!
Thus spake Poul-Henning Kamp <[EMAIL PROTECTED]>: > Somebody: please fix so this doesn't suck. Does msdosfs even have an active maintainer? There seem to be about half a dozen PRs open against it, one of which is a semi-obvious 4-line patch I submitted last April. To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Ultra-fast Acer (Benq) ScanWit 2720S SCSI scanner
-CURRENT kernel seems to be too optimistic about my scanner speed... from 3224652.361 to 3260358.656 MB/s (that's about 3TB/s), It's too fast for any scanning device in the universe... especially for async SCSI-2 device FreeBSD 5.0-CURRENT #4: Sun Feb 9 11:18:32 MSK 2003 [EMAIL PROTECTED]:/usr/obj/usr/src/sys/FREE Preloaded elf kernel "/boot/kernel/kernel" at 0xc0463000. Preloaded elf module "/boot/kernel/snd_emu10k1.ko" at 0xc04630a8. Preloaded elf module "/boot/kernel/snd_pcm.ko" at 0xc0463158. Preloaded elf module "/boot/kernel/firewire.ko" at 0xc0463204. Calibrating clock(s) ... TSC clock: 400897760 Hz, i8254 clock: 1193149 Hz CLK_USE_I8254_CALIBRATION not specified - using default frequency Timecounter "i8254" frequency 1193182 Hz CLK_USE_TSC_CALIBRATION not specified - using old calibration method Timecounter "TSC" frequency 400911576 Hz CPU: AMD-K6(tm) 3D processor (400.91-MHz 586-class CPU) Origin = "AuthenticAMD" Id = 0x58c Stepping = 12 Features=0x8021bf AMD Features=0x8800 [part of dmesg skipped] amd0: port 0xb000-0xb07f irq 11 at device 12.0 on pci0 pass0 at amd0 bus 0 target 1 lun 0 pass0: Fixed Scanner SCSI-2 device pass0: Serial Number I pass0: 3224652.361MB/s transfers ^ pass1 at amd0 bus 0 target 3 lun 0 pass1: Removable CD-ROM SCSI-2 device pass1: Serial Number ' pass1: 10.000MB/s transfers (10.000MHz, offset 7) pass0 at amd0 bus 0 target 1 lun 0 pass0: Fixed Scanner SCSI-2 device pass0: Serial Number I pass0: 3260358.656MB/s transfers ^ cd0 at amd0 bus 0 target 3 lun 0 cd0: Removable CD-ROM SCSI-2 device cd0: Serial Number ' cd0: 10.000MB/s transfers (10.000MHz, offset 7) cd0: cd present [51814 x 2048 byte records] To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: HEADS UP: GCC 3.2.2 is coming
On Mon, 10 Feb 2003, Rahul Siddharthan wrote: > Alexander Kabaev wrote: > > The import should be complete now. Please let us know if you > > see any problems introduced with this GCC version. > > > cc -O -pipe -mcpu=i686 -march=i686 -DIN_GCC -DHAVE_CONFIG_H > -DPREFIX=\"/usr/obj/usr/src/i386/usr\" > -I/usr/obj/usr/src/i386/usr/src/gnu/usr.bin/cc/cc1plus/../cc_tools > -I/usr/src/gnu/usr.bin/cc/cc1plus/../cc_tools > -I/usr/src/gnu/usr.bin/cc/cc1plus/../../../../contrib/gcc > -I/usr/src/gnu/usr.bin/cc/cc1plus/../../../../contrib/gcc/config > -I/usr/src/gnu/usr.bin/cc/cc1plus/../../../../contrib/gcc/cp -I. >-c /usr/src/contrib/gcc/cp/decl.c > /usr/src/contrib/gcc/cp/decl.c: In function > `cxx_init_decl_processing': > /usr/src/contrib/gcc/cp/decl.c:6671: `c_size_type_node' undeclared > (first use in this function) > /usr/src/contrib/gcc/cp/decl.c:6671: (Each undeclared identifier is > reported only once > /usr/src/contrib/gcc/cp/decl.c:6671: for each function it appears in.) > *** Error code 1 I just finished a make world after the import. No such problems here. -- Hi! I'm a .signature virus! Copy me into your ~/.signature to help me spread! To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
