NFS Client error
Freebsd 8 stable amd64 It mounts different file systems by NFS (with locking) on a data server directly connected (gigabit) to the server Apache running in a several jails on those nfs folders. Now and then I get huge slow-down. When I look in the logs I get thousand of lines like these: Mar 5 11:50:52 virt2 kernel: vm_fault: pager read error, pid 46487 (httpd) Mar 5 11:50:52 virt2 kernel: pid 46487 (httpd), uid 80: exited on signal 11 What should I do? ___ freebsd-hackers@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-hackers To unsubscribe, send any mail to freebsd-hackers-unsubscr...@freebsd.org
Re: ZFS group ownership
Nate Eldredge wrote: On SysV, you can get BSD-type behavior by setting the sgid bit on the directory in question, e.g. chmod g+s dir. Then new files will inherit their group from the directory. I suspect this will work on FreeBSD/ZFS too even though chmod g+s on a directory is undocumented. Yes, it does. Thanks, I'll use this for my needs. Giulio. ___ freebsd-hackers@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-hackers To unsubscribe, send any mail to freebsd-hackers-unsubscr...@freebsd.org
Re: ZFS group ownership
Adrian Penisoara wrote: Is the ownership of the new file decided by the open() syscall or by the filesystem layer ? On a superficial lookup through the sources it appears a filesystem layer choice... Which of the following would then be the best option (also taking POLA into account): * leave things are they are * make ZFS under FreeBSD behave the way open(2) describes * have a new ZFS property govern the behavior and default to one of the above Thanks, Adrian Penisoara EnterpriseBSD Thanks all for answering (sorry for the multiple posts, I was tuning my mail server) I believe that on a same freebsd there should be a consistent behavior among different mounts. So in my opinion ZFS should conform to UFS (or UFS to ZFS, if that's desirable). The best thing would be to have a sysctl tunable to choose that (sysv5 / bsd). BSD should be default, since it makes more sense for workgroups... ___ freebsd-hackers@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-hackers To unsubscribe, send any mail to freebsd-hackers-unsubscr...@freebsd.org
ZFS group ownership
I don't know if this is the correct list to discuss this matter, if not I apologize in advance. I've always understood group ownership as a way to allow members of the same group to operate on files / folders which belong to that group, while leaving out others. Let's suppose to have a directory /root/test (UFS file system) I do this: cd /root chmod -R 770 test chown -R www:www test (I use group www as an example, since it's already present on a base system) My user gferro also belongs to group www and has umask 007 su - gferro touch qweq mkdir asda If I watch now the file and directory I've just created: --- %ls -la total 6 drwxrwx--- 3 www www512 Sep 12 13:39 . drwxr-xr-x 4 rootwheel 512 Sep 12 13:02 .. drwxrwx--- 2 gferro www512 Sep 12 13:39 asda -rw-rw 1 gferro www 0 Sep 12 13:38 qweq --- I see that both belongs to group www, even though gferro's base group is gferro: --- id gferro uid=1001(gferro) gid=1001(gferro) groups=1001(gferro),80(www) --- This means that all those user's who belong to group www will be able to work with the files and directories I've created. Now I try to do the same on a zfs partition on the same machine This is what I see with ls --- ls -la total 4 drwxrwx--- 3 www www 4 Sep 12 13:43 . drwxr-xr-x 4 rootwheel 4 Sep 12 13:43 .. drwxrwx--- 2 gferro gferro 2 Sep 12 13:43 asda -rw-rw 1 gferro gferro 0 Sep 12 13:43 qweq --- As you can see, both file and directory belongs now to gferro and not www. This means that other users won't even be able to read my files / dir, let alone modify them. What I ask now is: is this a bug or a feature? How can I achieve my goal in ZFS, that is allowing members of the same group to operate with the files / dirs they create? Thanks in advance. ___ freebsd-hackers@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-hackers To unsubscribe, send any mail to freebsd-hackers-unsubscr...@freebsd.org
ZFS group ownership
I don't know if this is the correct list to discuss this matter, if not I apologize in advance. I've always understood group ownership as a way to allow members of the same group to operate on files / folders which belong to that group, while leaving out others. Let's suppose to have a directory /root/test (UFS file system) I do this: cd /root chmod -R 770 test chown -R www:www test (I use group www as an example, since it's already present on a base system) My user gferro also belongs to group www and has umask 007 su - gferro touch qweq mkdir asda If I watch now the file and directory I've just created: --- %ls -la total 6 drwxrwx--- 3 www www512 Sep 12 13:39 . drwxr-xr-x 4 rootwheel 512 Sep 12 13:02 .. drwxrwx--- 2 gferro www512 Sep 12 13:39 asda -rw-rw 1 gferro www 0 Sep 12 13:38 qweq --- I see that both belongs to group www, even though gferro's base group is gferro: --- id gferro uid=1001(gferro) gid=1001(gferro) groups=1001(gferro),80(www) --- This means that all those user's who belong to group www will be able to work with the files and directories I've created. Now I try to do the same on a zfs partition on the same machine This is what I see with ls --- ls -la total 4 drwxrwx--- 3 www www 4 Sep 12 13:43 . drwxr-xr-x 4 rootwheel 4 Sep 12 13:43 .. drwxrwx--- 2 gferro gferro 2 Sep 12 13:43 asda -rw-rw 1 gferro gferro 0 Sep 12 13:43 qweq --- As you can see, both file and directory belongs now to gferro and not www. This means that other users won't even be able to read my files / dir, let alone modify them. What I ask now is: is this a bug or a feature? How can I achieve my goal in ZFS, that is allowing members of the same group to operate with the files / dirs they create? Thanks in advance. ___ freebsd-hackers@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-hackers To unsubscribe, send any mail to freebsd-hackers-unsubscr...@freebsd.org
ZFS group ownership
I don't know if this is the correct list to discuss this matter, if not I apologize in advance. I've always understood group ownership as a way to allow members of the same group to operate on files / folders which belong to that group, while leaving out others. Let's suppose to have a directory /root/test (UFS file system) I do this: cd /root chmod -R 770 test chown -R www:www test (I use group www as an example, since it's already present on a base system) My user gferro also belongs to group www and has umask 007 su - gferro touch qweq mkdir asda If I watch now the file and directory I've just created: --- %ls -la total 6 drwxrwx--- 3 www www512 Sep 12 13:39 . drwxr-xr-x 4 rootwheel 512 Sep 12 13:02 .. drwxrwx--- 2 gferro www512 Sep 12 13:39 asda -rw-rw 1 gferro www 0 Sep 12 13:38 qweq --- I see that both belongs to group www, even though gferro's base group is gferro: --- id gferro uid=1001(gferro) gid=1001(gferro) groups=1001(gferro),80(www) --- This means that all those user's who belong to group www will be able to work with the files and directories I've created. Now I try to do the same on a zfs partition on the same machine This is what I see with ls --- ls -la total 4 drwxrwx--- 3 www www 4 Sep 12 13:43 . drwxr-xr-x 4 rootwheel 4 Sep 12 13:43 .. drwxrwx--- 2 gferro gferro 2 Sep 12 13:43 asda -rw-rw 1 gferro gferro 0 Sep 12 13:43 qweq --- As you can see, both file and directory belongs now to gferro and not www. This means that other users won't even be able to read my files / dir, let alone modify them. What I ask now is: is this a bug or a feature? How can I achieve my goal in ZFS, that is allowing members of the same group to operate with the files / dirs they create? Thanks in advance. ___ freebsd-hackers@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-hackers To unsubscribe, send any mail to freebsd-hackers-unsubscr...@freebsd.org
Problems with twa
I've installed a 3ware 9500 sata controller with 4 1TB disks in raid 5. Apart from the usual wrong geometry warning the starting configuration is ok: I create a single partition with the default labels plus a /usr/home label with takes most of the disk space (about 2.7TB). When I reboot the system the /usr/home partition size drops unexplainably to about 640GB. In order to try to understand what happens I've installed freebsd anew, this time creating 2 partitions: the first one 50GB, the second about 2.7TB (the remaining space). Everything seems to work correctly. I reboot the system and lo! the second partitions shrinks to about 640GB and the partitioner (using sysinstall) tells me that there are 2048GB free! This happens both with freebsd 7 and 8 current amd64. Thanks for any help. ___ freebsd-hackers@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-hackers To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: multi-ip jail patch on freebsd 7
Bjoern A. Zeeb wrote: Since the multi-ip jail feature isn't yet part of the base system (why???) I was searching the internet for a suitable patch to apply manually. I couldn't find any. The one I found didn't apply cleanly to a 7 system. Can any of you point me to a working multi-ip jail patch? freebsd-jail@ would be a better list. I would happily point you at one but my webserver is down at the moment. I hope you can waut anther few days as I am swamped... Thanks anyway, I'll ask there... ___ freebsd-hackers@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-hackers To unsubscribe, send any mail to [EMAIL PROTECTED]
multi-ip jail patch on freebsd 7
Since the multi-ip jail feature isn't yet part of the base system (why???) I was searching the internet for a suitable patch to apply manually. I couldn't find any. The one I found didn't apply cleanly to a 7 system. Can any of you point me to a working multi-ip jail patch? Thanks in advance. ___ freebsd-hackers@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-hackers To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Synaptics Xorg driver for FreeBSD/amd64
Eygene Ryabinkin wrote: Hi Eygene, I could only now test the new port and it works. Now it's just a matter of fine-tuning it (i.e. I'd like to increase the acceleration of the pointer) Thanks for the great job! ___ freebsd-hackers@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-hackers To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Synaptics Xorg driver for FreeBSD/amd64
Eygene Ryabinkin wrote: Giulio, good day. Long time ago, in December 2007, we discuissed the problem with Synaptics touchpad driver for FreeBSD in the freebsd-hackers list. I had corrected the problem and driver seems to work, but I need more testing with real hardware. I had opened the FreeBSD PR: http://www.freebsd.org/cgi/query-pr.cgi?pr=120783 It will be great if you will be able to try the patch in the PR (I assume that you still have FreeBSD/amd64 and Xorg on some of your machines) and report the result either to the list or as the PR followup. Thank you! Hi Eygene, first of all thanks for your effort. Unfortunately I couldn't still get the synaptyc driver work on my laptop. Here's what I did: 1) I extracted the port driver with make extract patch 2) put your patch in /usr/ports/x11-drivers/synaptics/files (I named it newpatch) 3) applied the patch with that directory with patch newpatch 4) compiled the driver with make install clean 5) loaded the driver in /boot/loader.conf (as per pkg-message) 6) modified the /etc/X11/xorg.conf (//) 7) disabled the moused demon (//) When I launched startx the xorg server aborted with the same No Device specified I got the last time. I attach the complete log of the server. I hope it will be of help to you. Regards. X.Org X Server 1.4.0 Release Date: 5 September 2007 X Protocol Version 11, Revision 0 Build Operating System: FreeBSD 7.0-PRERELEASE amd64 Current Operating System: FreeBSD aurynmob2.giulioferro.it 7.0-PRERELEASE FreeBSD 7.0-PRERELEASE #1: Wed Jan 30 22:06:30 CET 2008 [EMAIL PROTECTED]:/usr/obj/usr/src/sys/AURYNMOB2 amd64 Build Date: 18 February 2008 10:16:05AM Before reporting problems, check http://wiki.x.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/Xorg.0.log, Time: Mon Feb 18 13:23:34 2008 (==) Using config file: /etc/X11/xorg.conf (==) ServerLayout Simple Layout (**) |--Screen Screen 1 (0) (**) | |--Monitor My Monitor (**) | |--Device * Generic VESA compatible (**) |--Input Device Keyboard1 (**) |--Input Device Synaptics_Touchpad (**) Option DontVTSwitch (**) Option DontZap (**) Option DontZoom (==) Automatically adding devices (==) Automatically enabling devices (WW) `fonts.dir' not found (or not valid) in /usr/local/lib/X11/fonts/local/. Entry deleted from font path. (Run 'mkfontdir' on /usr/local/lib/X11/fonts/local/). (==) Including the default font path /usr/local/lib/X11/fonts/misc/,/usr/local/lib/X11/fonts/TTF/,/usr/local/lib/X11/fonts/OTF,/usr/local/lib/X11/fonts/Type1/,/usr/local/lib/X11/fonts/100dpi/,/usr/local/lib/X11/fonts/75dpi/. (**) FontPath set to: /usr/local/lib/X11/fonts/misc/, /usr/local/lib/X11/fonts/TTF/, /usr/local/lib/X11/fonts/OTF, /usr/local/lib/X11/fonts/Type1/, /usr/local/lib/X11/fonts/100dpi/, /usr/local/lib/X11/fonts/75dpi/, /usr/local/lib/X11/fonts/misc/, /usr/local/lib/X11/fonts/TTF/, /usr/local/lib/X11/fonts/OTF, /usr/local/lib/X11/fonts/Type1/, /usr/local/lib/X11/fonts/100dpi/, /usr/local/lib/X11/fonts/75dpi/ (==) RgbPath set to /usr/local/share/X11/rgb (==) ModulePath set to /usr/local/lib/xorg/modules (II) No default mouse found, adding one (**) |--Input Device default pointer (II) Loader magic: 0x680ce0 (II) Module ABI versions: X.Org ANSI C Emulation: 0.3 X.Org Video Driver: 2.0 X.Org XInput driver : 2.0 X.Org Server Extension : 0.3 X.Org Font Renderer : 0.5 (II) Loader running on freebsd (II) LoadModule: pcidata (II) Loading /usr/local/lib/xorg/modules//libpcidata.so (II) Module pcidata: vendor=X.Org Foundation compiled for 1.4.0, module version = 1.0.0 ABI class: X.Org Video Driver, version 2.0 (--) Using syscons driver with X support (version 2.0) (--) using VT number 9 (WW) OS did not count PCI devices, guessing wildly (II) PCI: PCI scan (all values are in hex) (II) PCI: 00:00:0: chip 8086,2a00 card 104d,9016 rev 0c class 06,00,00 hdr 00 (II) PCI: 00:01:0: chip 8086,2a01 card , rev 0c class 06,04,00 hdr 01 (II) PCI: 00:1a:0: chip 8086,2834 card 104d,9016 rev 03 class 0c,03,00 hdr 80 (II) PCI: 00:1a:1: chip 8086,2835 card 104d,9016 rev 03 class 0c,03,00 hdr 00 (II) PCI: 00:1a:7: chip 8086,283a card 104d,9016 rev 03 class 0c,03,20 hdr 00 (II) PCI: 00:1b:0: chip 8086,284b card 104d,9016 rev 03 class 04,03,00 hdr 00 (II) PCI: 00:1c:0: chip 8086,283f card , rev 03 class 06,04,00 hdr 81 (II) PCI: 00:1c:1: chip 8086,2841 card , rev 03 class 06,04,00 hdr 81 (II) PCI: 00:1c:2: chip 8086,2843 card , rev 03 class 06,04,00 hdr 81 (II) PCI: 00:1d:0: chip 8086,2830 card 104d,9016 rev 03 class 0c,03,00 hdr 80 (II) PCI:
Re: Synaptics Xorg driver for FreeBSD/amd64
Eygene Ryabinkin wrote: Please, try again if you have some spare time. Ok. Now the server starts, but the mouse pointer isn't moving... in the ServerLayout section I have this: #InputDevice Mouse1 CorePointer InputDevice Keyboard1 CoreKeyboard InputDevice Synaptics_TouchpadCorePointer and I didn't start the moused demon. ___ freebsd-hackers@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-hackers To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Synaptics Xorg driver for FreeBSD/amd64
Eygene Ryabinkin wrote: in the ServerLayout section I have this: #InputDevice Mouse1 CorePointer InputDevice Keyboard1 CoreKeyboard InputDevice Synaptics_TouchpadCorePointer And if you'll try 'InputDevice Synaptics_Touchpad CorePointer SendCoreEvents'? Nothing changes, sorry... If not, drop me a letter, I'll try to get the real hardware into my hands and test it. But this likely won't be done until the end of the week, sorry. Thanks again. I include the complete log of the xorg session, I hope it can help you somehow. If you need me further tests just say so... Bye. X.Org X Server 1.4.0 Release Date: 5 September 2007 X Protocol Version 11, Revision 0 Build Operating System: FreeBSD 7.0-PRERELEASE amd64 Current Operating System: FreeBSD aurynmob2.giulioferro.it 7.0-PRERELEASE FreeBSD 7.0-PRERELEASE #1: Wed Jan 30 22:06:30 CET 2008 [EMAIL PROTECTED]:/usr/obj/usr/src/sys/AURYNMOB2 amd64 Build Date: 18 February 2008 10:16:05AM Before reporting problems, check http://wiki.x.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/Xorg.0.log, Time: Mon Feb 18 15:46:59 2008 (==) Using config file: /etc/X11/xorg.conf (==) ServerLayout Simple Layout (**) |--Screen Screen 1 (0) (**) | |--Monitor My Monitor (**) | |--Device * Generic VESA compatible (**) |--Input Device Keyboard1 (**) |--Input Device Synaptics_Touchpad (**) Option DontVTSwitch (**) Option DontZap (**) Option DontZoom (==) Automatically adding devices (==) Automatically enabling devices (WW) `fonts.dir' not found (or not valid) in /usr/local/lib/X11/fonts/local/. Entry deleted from font path. (Run 'mkfontdir' on /usr/local/lib/X11/fonts/local/). (==) Including the default font path /usr/local/lib/X11/fonts/misc/,/usr/local/lib/X11/fonts/TTF/,/usr/local/lib/X11/fonts/OTF,/usr/local/lib/X11/fonts/Type1/,/usr/local/lib/X11/fonts/100dpi/,/usr/local/lib/X11/fonts/75dpi/. (**) FontPath set to: /usr/local/lib/X11/fonts/misc/, /usr/local/lib/X11/fonts/TTF/, /usr/local/lib/X11/fonts/OTF, /usr/local/lib/X11/fonts/Type1/, /usr/local/lib/X11/fonts/100dpi/, /usr/local/lib/X11/fonts/75dpi/, /usr/local/lib/X11/fonts/misc/, /usr/local/lib/X11/fonts/TTF/, /usr/local/lib/X11/fonts/OTF, /usr/local/lib/X11/fonts/Type1/, /usr/local/lib/X11/fonts/100dpi/, /usr/local/lib/X11/fonts/75dpi/ (==) RgbPath set to /usr/local/share/X11/rgb (==) ModulePath set to /usr/local/lib/xorg/modules (II) No default mouse found, adding one (**) |--Input Device default pointer (II) Loader magic: 0x680ce0 (II) Module ABI versions: X.Org ANSI C Emulation: 0.3 X.Org Video Driver: 2.0 X.Org XInput driver : 2.0 X.Org Server Extension : 0.3 X.Org Font Renderer : 0.5 (II) Loader running on freebsd (II) LoadModule: pcidata (II) Loading /usr/local/lib/xorg/modules//libpcidata.so (II) Module pcidata: vendor=X.Org Foundation compiled for 1.4.0, module version = 1.0.0 ABI class: X.Org Video Driver, version 2.0 (--) Using syscons driver with X support (version 2.0) (--) using VT number 9 (WW) OS did not count PCI devices, guessing wildly (II) PCI: PCI scan (all values are in hex) (II) PCI: 00:00:0: chip 8086,2a00 card 104d,9016 rev 0c class 06,00,00 hdr 00 (II) PCI: 00:01:0: chip 8086,2a01 card , rev 0c class 06,04,00 hdr 01 (II) PCI: 00:1a:0: chip 8086,2834 card 104d,9016 rev 03 class 0c,03,00 hdr 80 (II) PCI: 00:1a:1: chip 8086,2835 card 104d,9016 rev 03 class 0c,03,00 hdr 00 (II) PCI: 00:1a:7: chip 8086,283a card 104d,9016 rev 03 class 0c,03,20 hdr 00 (II) PCI: 00:1b:0: chip 8086,284b card 104d,9016 rev 03 class 04,03,00 hdr 00 (II) PCI: 00:1c:0: chip 8086,283f card , rev 03 class 06,04,00 hdr 81 (II) PCI: 00:1c:1: chip 8086,2841 card , rev 03 class 06,04,00 hdr 81 (II) PCI: 00:1c:2: chip 8086,2843 card , rev 03 class 06,04,00 hdr 81 (II) PCI: 00:1d:0: chip 8086,2830 card 104d,9016 rev 03 class 0c,03,00 hdr 80 (II) PCI: 00:1d:1: chip 8086,2831 card 104d,9016 rev 03 class 0c,03,00 hdr 00 (II) PCI: 00:1d:2: chip 8086,2832 card 104d,9016 rev 03 class 0c,03,00 hdr 00 (II) PCI: 00:1d:7: chip 8086,2836 card 104d,9016 rev 03 class 0c,03,20 hdr 00 (II) PCI: 00:1e:0: chip 8086,2448 card , rev f3 class 06,04,01 hdr 01 (II) PCI: 00:1f:0: chip 8086,2811 card 104d,9016 rev 03 class 06,01,00 hdr 80 (II) PCI: 00:1f:1: chip 8086,2850 card 104d,9016 rev 03 class 01,01,8a hdr 00 (II) PCI: 00:1f:2: chip 8086,282a card 104d,9016 rev 03 class 01,04,00 hdr 00 (II) PCI: 00:1f:3: chip 8086,283e card 104d,9016 rev 03 class 0c,05,00 hdr 00 (II) PCI: 01:00:0: chip 10de,0407 card 104d,9016 rev a1 class 03,00,00 hdr
Re: Synaptics Xorg driver for FreeBSD/amd64
Eygene Ryabinkin wrote: Aargh, this is the funny thing: you have no devices that are handled by the 'mouse' driver. And Xorg automatically adds one. Please, uncomment your 'Mouse1' device inside ServerLayout, start moused and try again. The 'default pointer' should disappear. And probably mices will start working. It will be good to see Xorg.log from this attempt. Ok, now I've uncommented both mouse1 and synaptics: InputDevice Mouse1 CorePointer InputDevice Keyboard1 CoreKeyboard InputDevice Synaptics_TouchpadCorePointer and the moused demon. Here's is what I get: 1) The mouse pointer now moves 2) The drag and drop with double click on the touchpad _doesn't_ work 3) Window scrolling with the touchpad _doesn't_ work (either horizontally or vertically) I attach the log of the attempt. X.Org X Server 1.4.0 Release Date: 5 September 2007 X Protocol Version 11, Revision 0 Build Operating System: FreeBSD 7.0-PRERELEASE amd64 Current Operating System: FreeBSD aurynmob2.giulioferro.it 7.0-PRERELEASE FreeBSD 7.0-PRERELEASE #1: Wed Jan 30 22:06:30 CET 2008 [EMAIL PROTECTED]:/usr/obj/usr/src/sys/AURYNMOB2 amd64 Build Date: 18 February 2008 10:16:05AM Before reporting problems, check http://wiki.x.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/Xorg.0.log, Time: Mon Feb 18 15:46:59 2008 (==) Using config file: /etc/X11/xorg.conf (==) ServerLayout Simple Layout (**) |--Screen Screen 1 (0) (**) | |--Monitor My Monitor (**) | |--Device * Generic VESA compatible (**) |--Input Device Keyboard1 (**) |--Input Device Synaptics_Touchpad (**) Option DontVTSwitch (**) Option DontZap (**) Option DontZoom (==) Automatically adding devices (==) Automatically enabling devices (WW) `fonts.dir' not found (or not valid) in /usr/local/lib/X11/fonts/local/. Entry deleted from font path. (Run 'mkfontdir' on /usr/local/lib/X11/fonts/local/). (==) Including the default font path /usr/local/lib/X11/fonts/misc/,/usr/local/lib/X11/fonts/TTF/,/usr/local/lib/X11/fonts/OTF,/usr/local/lib/X11/fonts/Type1/,/usr/local/lib/X11/fonts/100dpi/,/usr/local/lib/X11/fonts/75dpi/. (**) FontPath set to: /usr/local/lib/X11/fonts/misc/, /usr/local/lib/X11/fonts/TTF/, /usr/local/lib/X11/fonts/OTF, /usr/local/lib/X11/fonts/Type1/, /usr/local/lib/X11/fonts/100dpi/, /usr/local/lib/X11/fonts/75dpi/, /usr/local/lib/X11/fonts/misc/, /usr/local/lib/X11/fonts/TTF/, /usr/local/lib/X11/fonts/OTF, /usr/local/lib/X11/fonts/Type1/, /usr/local/lib/X11/fonts/100dpi/, /usr/local/lib/X11/fonts/75dpi/ (==) RgbPath set to /usr/local/share/X11/rgb (==) ModulePath set to /usr/local/lib/xorg/modules (II) No default mouse found, adding one (**) |--Input Device default pointer (II) Loader magic: 0x680ce0 (II) Module ABI versions: X.Org ANSI C Emulation: 0.3 X.Org Video Driver: 2.0 X.Org XInput driver : 2.0 X.Org Server Extension : 0.3 X.Org Font Renderer : 0.5 (II) Loader running on freebsd (II) LoadModule: pcidata (II) Loading /usr/local/lib/xorg/modules//libpcidata.so (II) Module pcidata: vendor=X.Org Foundation compiled for 1.4.0, module version = 1.0.0 ABI class: X.Org Video Driver, version 2.0 (--) Using syscons driver with X support (version 2.0) (--) using VT number 9 (WW) OS did not count PCI devices, guessing wildly (II) PCI: PCI scan (all values are in hex) (II) PCI: 00:00:0: chip 8086,2a00 card 104d,9016 rev 0c class 06,00,00 hdr 00 (II) PCI: 00:01:0: chip 8086,2a01 card , rev 0c class 06,04,00 hdr 01 (II) PCI: 00:1a:0: chip 8086,2834 card 104d,9016 rev 03 class 0c,03,00 hdr 80 (II) PCI: 00:1a:1: chip 8086,2835 card 104d,9016 rev 03 class 0c,03,00 hdr 00 (II) PCI: 00:1a:7: chip 8086,283a card 104d,9016 rev 03 class 0c,03,20 hdr 00 (II) PCI: 00:1b:0: chip 8086,284b card 104d,9016 rev 03 class 04,03,00 hdr 00 (II) PCI: 00:1c:0: chip 8086,283f card , rev 03 class 06,04,00 hdr 81 (II) PCI: 00:1c:1: chip 8086,2841 card , rev 03 class 06,04,00 hdr 81 (II) PCI: 00:1c:2: chip 8086,2843 card , rev 03 class 06,04,00 hdr 81 (II) PCI: 00:1d:0: chip 8086,2830 card 104d,9016 rev 03 class 0c,03,00 hdr 80 (II) PCI: 00:1d:1: chip 8086,2831 card 104d,9016 rev 03 class 0c,03,00 hdr 00 (II) PCI: 00:1d:2: chip 8086,2832 card 104d,9016 rev 03 class 0c,03,00 hdr 00 (II) PCI: 00:1d:7: chip 8086,2836 card 104d,9016 rev 03 class 0c,03,20 hdr 00 (II) PCI: 00:1e:0: chip 8086,2448 card , rev f3 class 06,04,01 hdr 01 (II) PCI: 00:1f:0: chip 8086,2811 card 104d,9016 rev 03 class 06,01,00 hdr 80 (II) PCI: 00:1f:1: chip 8086,2850 card 104d,9016 rev 03 class 01,01,8a hdr 00 (II) PCI:
new linux-flashplugin9
Doesn't work. Both with linux-firefox and native firefox it either hangs or crashes. I tried this site: http://www.patek.com os: 7.0 beta 4 amd64 Hope it helps... ___ freebsd-hackers@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-hackers To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Synaptics
Donnie wrote: On Dec 12, 10:51 am, Giulio Ferro [EMAIL PROTECTED] wrote: Unfortunately those settings are already specified in /e tc/X11/xorg.conf in the section InputDevice for thetouchpad. If you look in the /usr/ports/x11-drivers/synaptics/pkg-message it's all already there I had the same problem, but finally happened on this solution: despite what the pkg-message says, in xorg.conf you have to specify both a non-existent mouse and the touchpad, in addition to following all the other pkg-message directions. So, my xorg.conf has: Section ServerLayout Identifier X.org Configured Screen 0 Screen0 0 0 InputDeviceMouse0 AlwaysCore InputDeviceKeyboard0 CoreKeyboard InputDeviceSynaptics_Touchpad CorePointer EndSection ### Note that touchpad MUST be CorePointer and non-existent mouse must be AlwaysCore ### Section InputDevice Identifier Mouse0 Driver mouse Option Protocol auto Option Device /dev/sysmouse EndSection Section InputDevice IdentifierSynaptics_Touchpad Driversynaptics OptionSendCoreEvents OptionDevice /dev/psm0 OptionProtocolpsm OptionTouchpadOff 0 OptionLeftEdge 1700 OptionRightEdge 5300 OptionTopEdge 1700 OptionBottomEdge4200 OptionFingerLow 25 OptionFingerHigh 30 OptionMaxTapTime 180 OptionMaxTapMove 220 OptionVertScrollDelta 100 OptionMinSpeed0.06 OptionMaxSpeed0.06 OptionAccelFactor 0.0010 OptionHorizScrollDelta100 OptionUpDownScrolling on OptionUpDownRepeat on OptionLeftRightScrollingon OptionLeftRightRepeat on OptionSHMConfig on EndSection Good luck! -- Donnie Doesn't work, sorry. The server starts, but the mouse pointer isn't moving. Anyway I'm not sure this is the right way to do thinks. I'd dearly like to listen from the maintainer, maybe it can shed some light on the /dev/input/event issue... ___ freebsd-hackers@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-hackers To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Synaptics
Eygene Ryabinkin wrote: Giulio, good day. Good day. -- (II) Synaptics touchpad driver version 0.14.6 (1406) Synaptics_Touchpad no synaptics event device found (checked 10 nodes) Synaptics_Touchpad The /dev/input/event* device nodes seem to be missing (EE) xf86OpenSerial: No Device specified. Synaptics driver unable to open device And what if you'll specify - Option Device/dev/psm0 Option Protocol psm - in the xorg.conf? I assume that you have your synaptics touchpad as the /dev/psm0. Yes, I have the touchpad as /dev/psm0 Unfortunately those settings are already specified in /e tc/X11/xorg.conf in the section InputDevice for the touchpad. If you look in the /usr/ports/x11-drivers/synaptics/pkg-message it's all already there ___ freebsd-hackers@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-hackers To unsubscribe, send any mail to [EMAIL PROTECTED]
Synaptics
Hi, I just wanted to report that the synaptics touchpad driver (/usr/ports/x11-drivers/synaptics) doesn't work in my configuration: freebsd 7 beta4 - amd64 - synaptics-0.14.6_2 I set hw.psm.synaptics_support=1 in /boot/loader.conf, disable moused, change /etc/X11/xorg.conf according to the instructions in pkg-messages. Unfortunately every time I try to start X the following error occurs: -- (II) Synaptics touchpad driver version 0.14.6 (1406) Synaptics_Touchpad no synaptics event device found (checked 10 nodes) Synaptics_Touchpad The /dev/input/event* device nodes seem to be missing (EE) xf86OpenSerial: No Device specified. Synaptics driver unable to open device (EE) PreInit failed for input device Synaptics_Touchpad (II) UnloadModule: synaptics Fatal server error: Caught signal 11. Server aborting -- Any idea is appreciated. ___ freebsd-hackers@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-hackers To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: doubt about IPSEC - Freebsd 7
Bjoern A. Zeeb wrote: On Mon, 26 Nov 2007, Baldur Gislason wrote: Hi, And since we're on this subject... is it possible to do IPSEC over UDP tunnels in FreeBSD now? I have a couple of networks with dumb NAT and need a way to tunnel out of them in a reliable manner. only with the patch, not out of the box. A good question could be : when the natt patch will be integrated? I've been using it for more than 1 year and it seems solid. Are there issues about that? ___ freebsd-hackers@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-hackers To unsubscribe, send any mail to [EMAIL PROTECTED]
doubt about IPSEC - Freebsd 7
I've noticed that in the kernel configuration IPSEC_ESP disappeared from the options. It says that you just need device crypto and IPSEC. Does this mean that with crypto and IPSEC I have all I need to treat ESP like the old IPSEC_ESP option? I'm having some problems right now setting up a vpn to complete phase 2, (the error is no proposal chosen). Since ipsec-tools uses the facilities in the kernel, I want to make sure that the kernel provides everything racoon needs... ___ freebsd-hackers@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-hackers To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: doubt about IPSEC - Freebsd 7
VANHULLEBUS Yvan wrote: I'm having some problems right now setting up a vpn to complete phase 2, (the error is no proposal chosen). Since ipsec-tools uses the facilities in the kernel, I want to make sure that the kernel provides everything racoon needs... That really sounds like a configuration issue (racoon.conf, or perhaps your SPD entries), racoon's debug on responder should give you more informations on the problem. Yes, that's what I thought as well , but I'm at the rope's end. I've already sent a mail to ipsec-tools mailing list describing the problem, but I had to rule out the possibility that it was os-related first. I hope some of them guys can help me. Unfortunatyle isakmpd doesn't work in freebsd 7 and I couln't find any other IKE manager for the os... ___ freebsd-hackers@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-hackers To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Nvidia amd64
Sam Fourman Jr. wrote: if there was a bounty system for FreeBSD I would pledge $100 USD for work that would help amd64 nvidia... heck I would even settle for someone that wants to take lead and setup a paypal collection. Sam Fourman Jr. I completely agree. Some guy here went as far as saying that nobody gives a damn about nvidia drivers, but from what I see (here and on nvidia forum) the opposite is true. Ok, let's see how we can fund this project. First of all the interested developers should assess the bulk of work to do and how long it will take them to complete it. Then we can think about how many people are interested in opening their wallet to see it come into being. ___ freebsd-hackers@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-hackers To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Nvidia amd64
Remko Lodder wrote: Ok, let's see how we can fund this project. First of all the interested developers should assess the bulk of work to do and how long it will take them to complete it. Then we can think about how many people are interested in opening their wallet to see it come into being. Lets do it the other way around ,lets see what people are willinoneg to pay for this, so that the person applying for this knows what he can expect. Pay by feature instead of pay by time. I'm in, as are at least other two posters in this thread. I think that if someone set up a web page for the bounty and spread the news to other forums a fair number of subscriptions will come up. What we need to know is : what is the bulk of work needed? Can't anyone sketch a simple plan with the tasks and the hours/man for each? ___ freebsd-hackers@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-hackers To unsubscribe, send any mail to [EMAIL PROTECTED]
Nvidia amd64
What is the status of the work required by the vidia guys so that they can code their driver for amd64 architecture? ___ freebsd-hackers@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-hackers To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Nvidia amd64
Alastair Hogge wrote: On Thu, 27 Sep 2007 18:15:52 Giulio Ferro wrote: What is the status of the work required by the vidia guys so that they can code their driver for amd64 architecture? Hey, There is no driver. I sort of surmised that already... Status can be found here: http://wiki.freebsd.org/NvidiaFeatureRequests Also you can find more info on the nvnews FreeBSD fourms. So, we are still years away from seeing a working nvidia driver, by the look of it... ___ freebsd-hackers@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-hackers To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Nvidia amd64
Sam Fourman Jr. wrote: There is no driver. I sort of surmised that already... So, we are still years away from seeing a working nvidia driver, by the look of it... I guess what I am confused about, is there someone actively working on the Nvidia requests, or does a capable individual need to take the lead on this project? And that's exactly what I'd very much like to know... ___ freebsd-hackers@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-hackers To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Nvidia amd64
Remko Lodder wrote: without that, do notice that people do this in their own free time, which could either take some time before it's there, or might not be interesting enough to work on currently (because of other things at work, private life other code etc). To say that there isn't enough interest in the nvidia driver would be outrageous. The lack of a amd64 nvidia driver currently the first cause that makes desktop users like myself prefer other operating systems to freebsd. I'm still using fb, of course, because on the whole it's still worth it. But I'm not happy about it (the nv driver doesn't work on the 8600M GT, so I'm forced to use the dumb vesa driver)... There's a lot of projects going on, and I appreciate it, but I can't help thinking that maybe some developers should consider this a priority as much as many of us users do... ___ freebsd-hackers@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-hackers To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Nvidia amd64
Dag-Erling Smørgrav wrote: Giulio Ferro [EMAIL PROTECTED] writes: To say that there isn't enough interest in the nvidia driver would be outrageous. No, it would be true. From the slew of messages on the subject (on the nvidia forum, for example) it wouldn't seem to be so true... I can understand the lack of interest of the developers for a task so difficult as this one, but please don't assume that others have no interest as well... ___ freebsd-hackers@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-hackers To unsubscribe, send any mail to [EMAIL PROTECTED]
WPI driver
Hi, I'm trying your driver in my sony AR41S notebook: pciconf -lv ... device = '3945ABG Intel 3945ABG Wireless LAN controller' ... [EMAIL PROTECTED]:3:0: class=0x060700 card=0x9016104d chip=0x8039104c rev=0x00 hdr=0x02 uname -a ... 7.0-CURRENT FreeBSD 7.0-CURRENT #3 : Tue Aug 21 12:41:59 CEST 2007 ... amd64 I've downloaded the source: 20070715-wpi-freebsd-7.0-current.tgz I've built and installed both the firmware and the driver without problems. Unfortunately when I start the driver: ifconfig wpi0 up I get a neverending output which loops on and on: Aug 21 13:36:13 aurynmob2 kernel: wpi_init Aug 21 13:36:13 aurynmob2 kernel: Resetting the card - clearing any uploaded firmware Aug 21 13:36:13 aurynmob2 kernel: EEPROM Version 0x1004, HW 0x200 Aug 21 13:36:13 aurynmob2 kernel: Loading firmware to adapter at 0x80, size 0x8000 Aug 21 13:36:13 aurynmob2 kernel: firmware status=0xbfbf, val=0x4040, result=0x0 Aug 21 13:36:13 aurynmob2 kernel: firmware status=0x, val=0x4040, result=0x4040 Aug 21 13:36:13 aurynmob2 kernel: Status Match! - ntries = 1 Aug 21 13:36:13 aurynmob2 kernel: Loading firmware to adapter at 0x0, size 0x95c Aug 21 13:36:13 aurynmob2 kernel: firmware status=0xbfbf, val=0x4040, result=0x0 Aug 21 13:36:13 aurynmob2 kernel: firmware status=0x, val=0x4040, result=0x4040 Aug 21 13:36:13 aurynmob2 kernel: Status Match! - ntries = 1 Aug 21 13:36:13 aurynmob2 kernel: DATA Aug 21 13:36:13 aurynmob2 kernel: DATA Matched Aug 21 13:36:13 aurynmob2 kernel: TEXT Aug 21 13:36:13 aurynmob2 kernel: TEXT Matched Aug 21 13:36:13 aurynmob2 kernel: notify qid=80 idx=0 flags=0 type=1 len=36 Aug 21 13:36:13 aurynmob2 kernel: microcode alive notification version 10e02 alive 1 Aug 21 13:36:13 aurynmob2 kernel: temperature -135 Aug 21 13:36:13 aurynmob2 kernel: NEWSTATE:SCAN Aug 21 13:36:13 aurynmob2 kernel: wpi_cmd 72 size 8 async 1 Aug 21 13:36:13 aurynmob2 kernel: wpi_scan_start Aug 21 13:36:13 aurynmob2 kernel: wpi_ops: command: 1 Aug 21 13:36:13 aurynmob2 kernel: notify qid=4 idx=0 flags=0 type=72 len=4 Aug 21 13:36:13 aurynmob2 kernel: cmd notification qid=4 idx=0 flags=0 type=72 len=4 Aug 21 13:36:13 aurynmob2 kernel: wpi_ops: command: 8 Aug 21 13:36:13 aurynmob2 kernel: wpi_cmd 119 size 32 async 0 Aug 21 13:36:13 aurynmob2 kernel: notify qid=4 idx=1 flags=0 type=119 len=4 Aug 21 13:36:13 aurynmob2 kernel: cmd notification qid=4 idx=1 flags=0 type=119 len=4 Aug 21 13:36:13 aurynmob2 kernel: wpi_cmd 155 size 12 async 0 Aug 21 13:36:13 aurynmob2 kernel: notify qid=4 idx=2 flags=0 type=155 len=4 Aug 21 13:36:13 aurynmob2 kernel: cmd notification qid=4 idx=2 flags=0 type=155 len=4 Aug 21 13:36:13 aurynmob2 kernel: wpi_cmd 16 size 43 async 0 Aug 21 13:36:13 aurynmob2 kernel: notify qid=4 idx=3 flags=0 type=16 len=4 Aug 21 13:36:13 aurynmob2 kernel: cmd notification qid=4 idx=3 flags=0 type=16 len=4 Aug 21 13:36:13 aurynmob2 kernel: chan 1/rate 12: power index 41 Aug 21 13:36:13 aurynmob2 kernel: chan 1/rate 18: power index 41 Aug 21 13:36:13 aurynmob2 kernel: chan 1/rate 24: power index 41 Aug 21 13:36:13 aurynmob2 kernel: chan 1/rate 36: power index 41 Aug 21 13:36:13 aurynmob2 kernel: chan 1/rate 48: power index 41 Aug 21 13:36:13 aurynmob2 kernel: chan 1/rate 72: power index 41 Aug 21 13:36:13 aurynmob2 kernel: chan 1/rate 96: power index 41 Aug 21 13:36:13 aurynmob2 kernel: chan 1/rate 108: power index 41 Aug 21 13:36:13 aurynmob2 kernel: chan 1/rate 2: power index 51 Aug 21 13:36:13 aurynmob2 kernel: chan 1/rate 4: power index 51 Aug 21 13:36:13 aurynmob2 kernel: chan 1/rate 11: power index 51 Aug 21 13:36:13 aurynmob2 kernel: chan 1/rate 22: power index 51 Aug 21 13:36:13 aurynmob2 kernel: wpi_cmd 151 size 52 async 0 Aug 21 13:36:13 aurynmob2 kernel: notify qid=4 idx=4 flags=0 type=151 len=4 Aug 21 13:36:13 aurynmob2 kernel: cmd notification qid=4 idx=4 flags=0 type=151 len=4 Aug 21 13:36:13 aurynmob2 kernel: wpi_cmd 24 size 64 async 0 Aug 21 13:36:13 aurynmob2 kernel: notify qid=4 idx=5 flags=0 type=24 len=8 Aug 21 13:36:13 aurynmob2 kernel: cmd notification qid=4 idx=5 flags=0 type=24 len=8 Aug 21 13:36:13 aurynmob2 kernel: wpi_cmd 71 size 52 async 0 Aug 21 13:36:13 aurynmob2 kernel: notify qid=4 idx=6 flags=0 type=71 len=4 Aug 21 13:36:13 aurynmob2 kernel: cmd notification qid=4 idx=6 flags=0 type=71 len=4 Aug 21 13:36:13 aurynmob2 kernel: wpi_cmd 71 size 52 async 0 Aug 21 13:36:13 aurynmob2 kernel: notify qid=4 idx=7 flags=0 type=71 len=4 Aug 21 13:36:13 aurynmob2 kernel: cmd notification qid=4 idx=7 flags=0 type=71 len=4 Aug 21 13:36:13 aurynmob2 kernel: wpi_ops: command: 2 Aug 21 13:36:13 aurynmob2 kernel: Scanning Essid: Aug 21 13:36:13 aurynmob2 kernel: Scanning 1 Passive: 0 Aug 21 13:36:13 aurynmob2 kernel: notify qid=4 idx=8 flags=0 type=128 len=8 Aug 21 13:36:13 aurynmob2 kernel: cmd notification qid=4 idx=8 flags=0 type=128 len=8 Aug 21 13:36:13 aurynmob2 kernel: notify qid=80 idx=1 flags=0
