Portsnap snapshot date in past abort
Receiving this recently: Looking up portsnap.FreeBSD.org mirrors... 3 mirrors found. Fetching snapshot tag from portsnap1.FreeBSD.org... done. Latest snapshot on server is older than what we already have! Cowardly refusing to downgrade from Sun Mar 28 01:00:58 MST 2010 to Sat Mar 27 01:20:17 MST 2010. I recall in other systems' package management repository update schemes seeing similar metadata errors and I've always felt it may be due to the caching on a transparent HTTP proxy on the network egress. Is the above likely due to such a situation? If so, is there a canonical fix for the issue (configuring cacheability on mirrors, configuration/tuning on proxies, options that may be passed on client side to signal bypass of cache? Or am I completely off base on this one? FreeBSD 8.0-RELEASE-p2 FreeBSD 8.0-RELEASE-p2 #0: Tue Jan 5 21:11:58 UTC 2010 r...@amd64-builder.daemonology.net:/usr/obj/usr/src/sys/GENERIC amd64 # /etc/portsnap.conf SERVERNAME=portsnap.FreeBSD.org KEYPRINT=9b5feee6d69f170e3dd0a2c8e469ddbd64f13f978f2f3aede40c98633216c330 INDEX INDEX-6 DESCRIBE.6 INDEX INDEX-7 DESCRIBE.7 INDEX INDEX-8 DESCRIBE.8 -- Darren Spruell phatbuck...@gmail.com ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
smbutil crypt'd password authentication failures
controller port 0xfe00-0xfe07,0xfe10-0xfe13,0xfe20-0xfe27,0xfe30-0xfe33,0xfec0-0xfedf mem 0xff97-0xff9703ff irq 20 at device 31.2 on pci0 atapci1: [ITHREAD] atapci1: AHCI called from vendor specific driver atapci1: AHCI Version 01.10 controller with 6 ports detected ata2: ATA channel 0 on atapci1 ata2: [ITHREAD] ata3: ATA channel 1 on atapci1 ata3: [ITHREAD] ata4: ATA channel 2 on atapci1 ata4: [ITHREAD] ata5: ATA channel 3 on atapci1 ata5: [ITHREAD] ata6: ATA channel 4 on atapci1 ata6: [ITHREAD] ata7: ATA channel 5 on atapci1 ata7: port not implemented ata7: [ITHREAD] pci0: serial bus, SMBus at device 31.3 (no driver attached) fdc0: floppy drive controller port 0x3f0-0x3f5,0x3f7 irq 6 drq 2 on acpi0 fdc0: [FILTER] fd0: 1440-KB 3.5 drive on fdc0 drive 0 sio0: 16550A-compatible COM port port 0x3f8-0x3ff irq 4 flags 0x10 on acpi0 sio0: type 16550A sio0: [FILTER] sio1: 16550A-compatible COM port port 0x2f8-0x2ff irq 3 on acpi0 sio1: type 16550A sio1: [FILTER] pmtimer0 on isa0 orm0: ISA Option ROMs at iomem 0xc-0xcbfff,0xcc000-0xcdfff,0xce000-0xd2fff,0xd3000-0xd3fff pnpid ORM on isa0 atkbdc0: Keyboard controller (i8042) at port 0x60,0x64 on isa0 atkbd0: AT Keyboard irq 1 on atkbdc0 kbd0 at atkbd0 atkbd0: [GIANT-LOCKED] atkbd0: [ITHREAD] ppc0: Parallel port at port 0x378-0x37f irq 7 on isa0 ppc0: SMC-like chipset (ECP/EPP/PS2/NIBBLE) in COMPATIBLE mode ppc0: FIFO with 16/16/8 bytes threshold ppbus0: Parallel port bus on ppc0 ppbus0: [ITHREAD] plip0: PLIP network interface on ppbus0 lpt0: Printer on ppbus0 lpt0: Interrupt-driven port ppi0: Parallel I/O on ppbus0 ppc0: [GIANT-LOCKED] ppc0: [ITHREAD] sc0: System console at flags 0x100 on isa0 sc0: VGA 16 virtual consoles, flags=0x300 vga0: Generic ISA VGA at port 0x3c0-0x3df iomem 0xa-0xb on isa0 uhub5: Dell Dell USB Keyboard Hub, class 9/0, rev 1.10/48.01, addr 2 on uhub0 uhub5: 3 ports with 2 removable, bus powered ukbd0: Dell Dell USB Keyboard Hub, class 0/0, rev 1.10/48.00, addr 3 on uhub5 kbd2 at ukbd0 uhid0: Dell Dell USB Keyboard Hub, class 0/0, rev 1.10/48.00, addr 3 on uhub5 ums0: vendor 0x0461 USB Optical Mouse, class 0/0, rev 2.00/2.00, addr 4 on uhub5 ums0: 3 buttons and Z dir. Timecounters tick every 1.000 msec firewire0: 1 nodes, maxhop = 0, cable IRM = 0 (me) firewire0: bus manager 0 (me) acd0: DVDR PHILIPS DVD+/-RW DVD8801/AD21 at ata0-master UDMA33 ad4: 152587MB WDC WD1600ADFS-75SLR2 21.07Q21 at ata2-master SATA300 ad6: 152587MB WDC WD1600ADFS-75SLR2 21.07Q21 at ata3-master SATA300 pcm0: HDA Codec: Sigmatel STAC9220 pcm0: HDA Driver Revision: 20071129_0050 acd0: FAILURE - INQUIRY ILLEGAL REQUEST asc=0x24 ascq=0x00 acd0: FAILURE - INQUIRY ILLEGAL REQUEST asc=0x24 ascq=0x00 ar0: 152585MB Intel MatrixRAID RAID1 status: READY ar0: disk0 READY (master) using ad4 at ata2-master ar0: disk1 READY (mirror) using ad6 at ata3-master cd0 at ata0 bus 0 target 0 lun 0 cd0: PHILIPS DVD+-RW DVD8801 AD21 Removable CD-ROM SCSI-0 device cd0: 33.000MB/s transfers cd0: Attempt to query device size failed: NOT READY, Medium not present SMP: AP CPU #1 Launched! SMP: AP CPU #2 Launched! SMP: AP CPU #3 Launched! SMP: AP CPU #6 Launched! SMP: AP CPU #7 Launched! SMP: AP CPU #4 Launched! SMP: AP CPU #5 Launched! Trying to mount root from ufs:/dev/ar0s1a WARNING: / was not properly dismounted WARNING: /tmp was not properly dismounted WARNING: /usr was not properly dismounted WARNING: /var was not properly dismounted -- Darren Spruell [EMAIL PROTECTED] ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: ftpd help
On Thu, Apr 3, 2008 at 8:23 AM, Victor Farah [EMAIL PROTECTED] wrote: Hey I have a default install of freebsd 6.2, and I enable ftpd in inetd. That all works nicely, I add a user to the system that needs to access ONLY two directories that are in two different places. For example: /usr/local/www/dir1 and /usr/local/www/dir2/ There are many directories in /usr/local/www/ that this person SHOULD not have access too. I also made this person a home directory: /usr/home/personX/. I then made the symlinks to the two directories they need to access. After all that setup I went into my /etc/ftpchroot file and added the following line: personX saved and I try to log on to test to see if it is locked in the home directory but has access to the two other directories they need. Does work, is there anyway to do this with the default ftpd package that comes with this? If you're attempting to restrict this FTP user to their home directory, then symlinks to directories outside of their home directory won't be accessible; this is the nature of chroot. You could create those directories in that user's home directory and create symlinks to those directories in the web directories (the opposite of what you have) and that might work how you want. If the permissions on your user's home directory are restricted you'd probably have to modify permissions so that the web user could access them. -- Darren Spruell [EMAIL PROTECTED] ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: FreeBSD 7.0 nvidia-driver woes
On Tue, Mar 18, 2008 at 12:00 PM, Derek Ragona [EMAIL PROTECTED] wrote: Is it worthwhile to contact NVidia with bug reports? Does the FreeBSD community amount to much of a blip on their radar? Do we have a direct liaison in the community? Never hurts to file a bug report. It seems to be in the nvidia older driver, I've not heard of the problem with the driver for the current cards. Four days ago I emailed a problem report to [EMAIL PROTECTED] I haven't heard a peep back. The NVIDIA support site is structured about like this: - If your NVIDIA card shipped with the computer direct from the OEM manufacturer, it's not our problem. Contact [Dell,HP,Compaq,etc] for resolution. - If your NVIDIA card was purchased retail, it's not our problem. Contact the card manufacturer [Gigabyte,MSI,etc.] for assistance. Does anyone know a contact in NVIDIA that would have any concern over (driver, etc.) issues like this? -- Darren Spruell [EMAIL PROTECTED] ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: desktop dominance
-0xfe27,0xfe30-0xfe33,0xfec0-0xfedf mem 0xff97-0xff9703ff irq 20 at device 31.2 on pci0 atapci1: [ITHREAD] atapci1: AHCI called from vendor specific driver atapci1: AHCI Version 01.10 controller with 6 ports detected ata2: ATA channel 0 on atapci1 ata2: [ITHREAD] ata3: ATA channel 1 on atapci1 ata3: [ITHREAD] ata4: ATA channel 2 on atapci1 ata4: [ITHREAD] ata5: ATA channel 3 on atapci1 ata5: [ITHREAD] ata6: ATA channel 4 on atapci1 ata6: [ITHREAD] ata7: ATA channel 5 on atapci1 ata7: port not implemented ata7: [ITHREAD] pci0: serial bus, SMBus at device 31.3 (no driver attached) fdc0: floppy drive controller port 0x3f0-0x3f5,0x3f7 irq 6 drq 2 on acpi0 fdc0: [FILTER] fd0: 1440-KB 3.5 drive on fdc0 drive 0 sio0: 16550A-compatible COM port port 0x3f8-0x3ff irq 4 flags 0x10 on acpi0 sio0: type 16550A sio0: [FILTER] sio1: 16550A-compatible COM port port 0x2f8-0x2ff irq 3 on acpi0 sio1: type 16550A sio1: [FILTER] pmtimer0 on isa0 orm0: ISA Option ROMs at iomem 0xc-0xcbfff,0xcc000-0xcdfff,0xce000-0xd2fff,0xd3000-0xd3fff pnpid ORM on isa0 atkbdc0: Keyboard controller (i8042) at port 0x60,0x64 on isa0 atkbd0: AT Keyboard irq 1 on atkbdc0 kbd0 at atkbd0 atkbd0: [GIANT-LOCKED] atkbd0: [ITHREAD] ppc0: Parallel port at port 0x378-0x37f irq 7 on isa0 ppc0: SMC-like chipset (ECP/EPP/PS2/NIBBLE) in COMPATIBLE mode ppc0: FIFO with 16/16/8 bytes threshold ppbus0: Parallel port bus on ppc0 ppbus0: [ITHREAD] plip0: PLIP network interface on ppbus0 lpt0: Printer on ppbus0 lpt0: Interrupt-driven port ppi0: Parallel I/O on ppbus0 ppc0: [GIANT-LOCKED] ppc0: [ITHREAD] sc0: System console at flags 0x100 on isa0 sc0: VGA 16 virtual consoles, flags=0x300 vga0: Generic ISA VGA at port 0x3c0-0x3df iomem 0xa-0xb on isa0 uhub5: Dell Dell USB Keyboard Hub, class 9/0, rev 1.10/48.01, addr 2 on uhub0 uhub5: 3 ports with 2 removable, bus powered ukbd0: Dell Dell USB Keyboard Hub, class 0/0, rev 1.10/48.00, addr 3 on uhub5 kbd2 at ukbd0 uhid0: Dell Dell USB Keyboard Hub, class 0/0, rev 1.10/48.00, addr 3 on uhub5 umass0: Lexar USB Flash Drive, class 0/0, rev 2.00/11.00, addr 4 on uhub5 ums0: vendor 0x0461 USB Optical Mouse, class 0/0, rev 2.00/2.00, addr 5 on uhub5 ums0: 3 buttons and Z dir. Timecounters tick every 1.000 msec firewire0: 1 nodes, maxhop = 0, cable IRM = 0 (me) firewire0: bus manager 0 (me) acd0: DVDR PHILIPS DVD+/-RW DVD8801/AD21 at ata0-master UDMA33 ad4: 152587MB WDC WD1600ADFS-75SLR2 21.07Q21 at ata2-master SATA300 ad6: 152587MB WDC WD1600ADFS-75SLR2 21.07Q21 at ata3-master SATA300 pcm0: HDA Codec: Sigmatel STAC9220 pcm0: HDA Driver Revision: 20071129_0050 acd0: FAILURE - INQUIRY ILLEGAL REQUEST asc=0x24 ascq=0x00 acd0: FAILURE - INQUIRY ILLEGAL REQUEST asc=0x24 ascq=0x00 ar0: 152585MB Intel MatrixRAID RAID1 status: READY ar0: disk0 READY (master) using ad4 at ata2-master ar0: disk1 READY (mirror) using ad6 at ata3-master SMP: AP CPU #5 Launched! SMP: AP CPU #7 Launched! SMP: AP CPU #4 Launched! SMP: AP CPU #6 Launched! SMP: AP CPU #1 Launched! SMP: AP CPU #3 Launched! SMP: AP CPU #2 Launched! cd0 at ata0 bus 0 target 0 lun 0 cd0: PHILIPS DVD+-RW DVD8801 AD21 Removable CD-ROM SCSI-0 device cd0: 33.000MB/s transfers cd0: Attempt to query device size failed: NOT READY, Medium not present da0 at umass-sim0 bus 0 target 0 lun 0 da0: Lexar USB Flash Drive 1100 Removable Direct Access SCSI-0 device da0: 1.000MB/s transfers da0: 1920MB (3932160 512 byte sectors: 255H 63S/T 244C) Trying to mount root from ufs:/dev/ar0s1a -- Darren Spruell [EMAIL PROTECTED] ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: smbfs CIFS
On Thu, Mar 20, 2008 at 12:40 PM, Wojciech Puchar [EMAIL PROTECTED] wrote: isn't SMB and CIFS the same? Superficially, although there are differences in the protocols. CIFS descended from the original SMB specification and adds to it. Hence, why e.g. in Linux you find separate module support for cifs and smbfs. -- Darren Spruell [EMAIL PROTECTED] ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: smb_iod_recvall: drop resp with mid errors
On Wed, Mar 19, 2008 at 10:25 AM, Chuck Swiger [EMAIL PROTECTED] wrote: Hi, Darren-- On Mar 18, 2008, at 4:33 PM, Darren Spruell wrote: While this host was experiencing these issues a different FreeBSD host also encountered issues with a different share on the same Windows server. I think this points to issues of some sort on the Windows filesystem, but I'd like to understand the smb_iod_recvall output. While a fair number of people using FreeBSD also use Samba, asking here about the details of the Samba code is less likely to receive detailed responses compared to asking on a Samba-specific list, such as [EMAIL PROTECTED]... No, nothing to do with samba. This is the native mount_smbfs(8) code in FreeBSD. -- Darren Spruell [EMAIL PROTECTED] ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
FreeBSD 7.0 nvidia-driver woes
](B) [12] -1 0 0xdd00 - 0xddff (0x100) MX[B](B) [13] 0 0 0x000a - 0x000a (0x1) MS[B] [14] 0 0 0x000b - 0x000b7fff (0x8000) MS[B] [15] 0 0 0x000b8000 - 0x000b (0x8000) MS[B] [16] -1 0 0x - 0x (0x1) IX[B] [17] -1 0 0x - 0x00ff (0x100) IX[B] [18] -1 0 0xece0 - 0xecff (0x20) IX[B]E [19] -1 0 0xfec0 - 0xfeff (0x40) IX[B]E [20] -1 0 0xfe30 - 0xfe3f (0x10) IX[B]E [21] -1 0 0xfe20 - 0xfe2f (0x10) IX[B]E [22] -1 0 0xfe10 - 0xfe1f (0x10) IX[B]E [23] -1 0 0xfe00 - 0xfe0f (0x10) IX[B]E [24] -1 0 0xffa0 - 0xffbf (0x20) IX[B]E [25] -1 0 0x0374 - 0x0377 (0x4) IX[B]E [26] -1 0 0x0170 - 0x017f (0x10) IX[B]E [27] -1 0 0x03f4 - 0x03f7 (0x4) IX[B]E [28] -1 0 0x01f0 - 0x01ff (0x10) IX[B]E [29] -1 0 0xff20 - 0xff3f (0x20) IX[B]E [30] -1 0 0xff40 - 0xff5f (0x20) IX[B]E [31] -1 0 0xff60 - 0xff7f (0x20) IX[B]E [32] -1 0 0xff80 - 0xff9f (0x20) IX[B]E [33] 0 0 0x03b0 - 0x03bb (0xc) IS[B] [34] 0 0 0x03c0 - 0x03df (0x20) IS[B] (II) NVIDIA(0): Initialized GPU GART. (WW) NVIDIA(0): WAIT (2, 6, 0x8000, 0x, 0x0500) (WW) NVIDIA(0): WAIT (1, 6, 0x8000, 0x, 0x0500) (II) NVIDIA(0): Setting mode nvidia-auto-select (WW) NVIDIA(0): WAIT (2, 1, 0x8000, 0x, 0x0598) (WW) NVIDIA(0): WAIT (1, 1, 0x8000, 0x, 0x0598) (II) Loading extension NV-GLX (WW) NVIDIA(0): WAIT (2, 11, 0x8000, 0x0aac, 0x0b00) (WW) NVIDIA(0): WAIT (1, 11, 0x8000, 0x0aac, 0x0b00) (II) NVIDIA(0): NVIDIA 3D Acceleration Architecture Initialized (II) NVIDIA(0): Using the NVIDIA 2D acceleration architecture (==) NVIDIA(0): Backing store disabled (==) NVIDIA(0): Silken mouse enabled (**) Option dpms (**) NVIDIA(0): DPMS enabled (II) Loading extension NV-CONTROL (WW) NVIDIA(0): WAIT (2, 6, 0x8000, 0x0aac, 0x104c) (WW) NVIDIA(0): WAIT (1, 6, 0x8000, 0x0aac, 0x104c) (==) RandR enabled (II) Setting vga for screen 0. (II) Initializing built-in extension MIT-SHM (II) Initializing built-in extension XInputExtension (II) Initializing built-in extension XTEST (II) Initializing built-in extension XKEYBOARD (II) Initializing built-in extension XC-APPGROUP (II) Initializing built-in extension XAccessControlExtension (II) Initializing built-in extension SECURITY (II) Initializing built-in extension XINERAMA (II) Initializing built-in extension XFIXES (II) Initializing built-in extension XFree86-Bigfont (II) Initializing built-in extension RENDER (II) Initializing built-in extension RANDR (II) Initializing built-in extension COMPOSITE (II) Initializing built-in extension DAMAGE (II) Initializing built-in extension XEVIE (II) Initializing extension GLX (**) Option Protocol auto (**) Mouse0: Device: /dev/sysmouse (**) Mouse0: Protocol: auto (**) Option CorePointer (**) Mouse0: always reports core events (**) Option Device /dev/sysmouse (==) Mouse0: Emulate3Buttons, Emulate3Timeout: 50 (**) Option ZAxisMapping 4 5 6 7 (**) Mouse0: ZAxisMapping: buttons 4, 5, 6 and 7 (**) Mouse0: Buttons: 11 (**) Mouse0: Sensitivity: 1 (**) Option CoreKeyboard (**) Keyboard0: always reports core events (**) Option Protocol standard (**) Keyboard0: Protocol: standard (**) Option AutoRepeat 500 30 (**) Option XkbRules xorg (**) Keyboard0: XkbRules: xorg (**) Option XkbModel pc105 (**) Keyboard0: XkbModel: pc105 (**) Option XkbLayout us (**) Keyboard0: XkbLayout: us (**) Option CustomKeycodes off (**) Keyboard0: CustomKeycodes disabled (II) evaluating device (Keyboard0) (II) XINPUT: Adding extended input device Keyboard0 (type: KEYBOARD) (II) evaluating device (Mouse0) (II) XINPUT: Adding extended input device Mouse0 (type: MOUSE) (II) Mouse0: SetupAuto: hw.iftype is 4, hw.model is 0 (II) Mouse0: SetupAuto: protocol is SysMouse (WW) NVIDIA(0): WAIT (2, 6, 0x8000, 0x1418, 0x1448) (WW) NVIDIA(0): WAIT (1, 6, 0x8000, 0x1418, 0x1448) (WW) NVIDIA(0): WAIT (2, 6, 0x8000, 0x1418, 0x1474) (WW) NVIDIA(0): WAIT (1, 6, 0x8000, 0x1418, 0x1474) (WW) NVIDIA(0): WAIT (2, 6, 0x8000, 0x1418, 0x1490) (WW) NVIDIA(0): WAIT (1, 6, 0x8000, 0x1418, 0x1490) (WW) NVIDIA(0): WAIT (2, 6, 0x8000, 0x1418, 0x17e0) (WW) NVIDIA(0): WAIT (1, 6, 0x8000, 0x1418, 0x17e0) FreeFontPath: FPE /usr/local/lib/X11/fonts/misc/ refcount is 2, should be 1; fixing. -- Darren Spruell [EMAIL PROTECTED] ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: FreeBSD 7.0 nvidia-driver woes
On Tue, Mar 18, 2008 at 11:07 AM, Derek Ragona [EMAIL PROTECTED] wrote: At 11:58 AM 3/18/2008, Darren Spruell wrote: Xorg + nvidia-driver woes... I also have a server running FreeBSD 7.0 with xorg 7.3 and an older Nvidia card. I first had trouble under 6.3 when I upgraded to xorg 7.3 from 7.1. The nvidia driver seems to cause an interupt storm that paralyzes the system. It doesn't freeze, but is so busy it is useless. It runs OK, not great, using the native xorg 7.3 driver which has no GL support. Do you (anyone?) know if it is possible to use dual-monitor support in the X.org nv driver? I don't need 3D acceleration necessarily, but I've been of the impression that TwinView is needed for usable dual-monitor capabilities. Someone (I thought) had mentioned earlier that this driver didn't support Xinerama correctly (everything stretched across two monitors). I don't have any idea what to do except wait for a new driver or xorg release that might fix this. I notice it seems to be an unpopular sentiment in the FreeBSD community, but as a user I feel it's worth mentioning it's upsetting being at the mercy of a binary blob kernel driver. I've had pain from 6.3 also, and hoped that a clean installation of 7.0 might have brought some good changes. Not the case, it seems. Is it worthwhile to contact NVidia with bug reports? Does the FreeBSD community amount to much of a blip on their radar? Do we have a direct liaison in the community? -- Darren Spruell [EMAIL PROTECTED] ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Problem with ssh
On Tue, Mar 18, 2008 at 10:15 AM, White Hat [EMAIL PROTECTED] wrote: I have tried using the following command with negative results. ssh -L 5902:localhost:5901 scorpio That produces this error message: Permission denied (publickey). The host 'scorpio' is denying you access to the system from your user (it attempted public key authentication and that failed). It should work if you make sure your authentication to the destination host works. -- Darren Spruell [EMAIL PROTECTED] ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
smb_iod_recvall: drop resp with mid errors
I have a CIFS share mounted from a Windows 2003 server on FreeBSD
6.2/i386 host (FreeBSD 6.2-RELEASE-p9 FreeBSD 6.2-RELEASE-p9 #0: Thu
Nov 29 04:22:49 UTC 2007
[EMAIL PROTECTED]:/usr/obj/usr/src/sys/SMP i386).
Earlier today we ran into a case where we were intermittently unable
to write to files on the mounted filesystem. The following errors were
encountered when this occurred:
smb_iod_recvall: drop resp with mid 5412
smb_iod_recvall: drop resp with mid 5417
smb_iod_recvall: drop resp with mid 5422
smb_iod_recvall: drop resp with mid 5531
smb_iod_recvall: drop resp with mid 5591
smb_iod_recvall: drop resp with mid 5662
smb_iod_recvall: drop resp with mid 7278
smb_iod_recvall: drop resp with mid 7285
smb_iod_recvall: drop resp with mid 7297
smb_iod_recvall: drop resp with mid 12
smb_iod_recvall: drop resp with mid 15
smb_iod_recvall: drop resp with mid 18
$ mount
//[EMAIL PROTECTED]/MALWARE_BEWARE on /caffeineaddicts-malware (smbfs)
# /etc/fstab:
//[EMAIL PROTECTED]/Malware_Beware /caffeineaddicts-malware
smbfs rw,-N,late 0 0
While this host was experiencing these issues a different FreeBSD host
also encountered issues with a different share on the same Windows
server. I think this points to issues of some sort on the Windows
filesystem, but I'd like to understand the smb_iod_recvall output. I
think this is the relevant code, with a check on line 361 resulting in
the error. Is there enough information to suggest what might be wrong
on the remote system to cause this?
/*
288 * Process incoming packets
289 */
290 static int
291 smb_iod_recvall(struct smbiod *iod)
292 {
293 struct smb_vc *vcp = iod-iod_vc;
294 struct thread *td = iod-iod_td;
295 struct smb_rq *rqp;
296 struct mbuf *m;
297 u_char *hp;
298 u_short mid;
299 int error;
300
...
360 SMB_IOD_RQUNLOCK(iod);
361 if (rqp == NULL) {
362 SMBERROR(drop resp with mid %d\n, (u_int)mid);
363 /* smb_printrqlist(vcp);*/
364 m_freem(m);
365 }
--
Darren Spruell
[EMAIL PROTECTED]
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Blocking undesirable domains using BIND
On Dec 30, 2007 9:52 AM, Maxim Khitrov [EMAIL PROTECTED] wrote: I was trying to do something similar. I didn't research too hard, but figured the only way to use Bind would be to make my server authoritative for all those domains, which meant a huge config file and potential overhead, as well as possibly breaking access to desirable servers in the domains. So hosts seemed easier, but apparently Bind never looks at hosts. I did find that Squid (which I already had installed and in limited use) has its own DNS resolver, and it does look at hosts first before going to the nameserver. Then I found this site: http://everythingisnt.com/hosts.html and put their list in hosts, and now client PCs get a squid error in place of ad junk. Works ok for me ;) Well... you were right about overhead. In the last two days I wrote a script that would fetch a list of domains from several different sites, and output a valid BIND configuration file that could be included in the main config. I just ran the second test and the results are extremely poor. With only 27,885 blocked domains the server is now consuming 208 MB of ram. The first time I tried reloading the full list of domains (91,137 of them) and that nearly crashed my server. Had to kill bind, remove two of the largest sources, and try a second time. Nearly 100,000 zones on that server is a fairly impressive amount. Give it credit for what you're trying to do. :) Nonetheless, crashing is unacceptable. Honestly, I can't figure out what BIND could possibly be using so much memory for. It's taking up about 7 KB for each zone. The zone file itself is not even 1 KB, and given that all the records are pointing to the exact same thing it seems to be needlessly wasting memory. In addition to that, if I comment out the blacklist config file and run rndc reload, it only frees up about 16 MB. So it doesn't even release memory when it is no longer needed. My experience, albeit with a smaller number of zones, is a bit different. First you need to account for main program memory and memory utilized by the nameserver's cache, if any. You may also be running your own authoritative zones which will add memory utilization outside of that. You can't account for all of the utilized memory in your additional blocking zones. Without my blocking zones loaded, I have 6 native zones on my nameserver and the resident memory size of named is 2.2 MB. After a fresh server startup, I expect minimum memory for cached records, so that comes out to be about 375 KB/zone, unscientifically. If I restart named (kill and start server fresh) with my blocking zones in the config, I come out with 17239 zones and a resident process memory size of 59 MB. (Unscientifically again,) this breaks down to about 3.5 KB/zone. In my configuration, each of these blocking zones points to a simple zone file 244B in size on disk: $TTL 86400 @ IN SOA ns.local. admin.local. ( 1 ; serial 1h ; refresh 30m ; retry 7d ; expiration 1h ); minimum IN NS ns.local. IN A 127.0.0.1 * IN A 127.0.0.1 So all told, I seem to notice somewhat slimmer utilization than you (roughly half the memory utilization per zone, and though I have 61% as many zones loaded my named takes only 28% of the memory yours does.) It looks like my plan of using BIND for filtering purposes will not work. Given how poorly it performed on this test I'm actually inclined to try another name server to see if something else would be more memory-efficient. You will almost certainly find most of the popular alternatives to be much more resource efficient. djbdns in particular would be my next choice if memory efficiency and stability are concerns. DS ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Imaging to new system
On Dec 30, 2007 10:54 AM, Robert Fitzpatrick [EMAIL PROTECTED] wrote: I have a server running 5.4-RELEASE using RAID-5 on an Intel RAID controller that I need to move to faster RAID. Is it possible to image or some other way to save the current install and restore after setting up the RAID or should I just plan to reinstall everything? Running dump(8) and restore(8) would allow you to back up and restore your system. http://www.freebsd.org/cgi/man.cgi?query=dump http://www.freebsd.org/cgi/man.cgi?query=restore This is typically used with tape, although you can dump to disk as well. If your data/system is critical, you ought to already have some backup strategy you could restore the system from to your new RAID. If not, you might put one in place (RAID != backups). -- Darren Spruell [EMAIL PROTECTED] ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Imaging to new system
On Dec 30, 2007 11:47 AM, Robert Fitzpatrick [EMAIL PROTECTED] wrote: Running dump(8) and restore(8) would allow you to back up and restore your system. http://www.freebsd.org/cgi/man.cgi?query=dump http://www.freebsd.org/cgi/man.cgi?query=restore This is typically used with tape, although you can dump to disk as well. If your data/system is critical, you ought to already have some backup strategy you could restore the system from to your new RAID. If not, you might put one in place (RAID != backups). Yes, of course, we have data backup and can restore after reinstalling everything, but I was looking for a complete system restore option. I'll look into these docs, thanks. There is no tape system, so I guess the only hope is if it can be dumped and restored from an NFS drive. From looking at the docs, it does appear this is possible, as long as the data in on a fs mounted by fstab? Can be data on a mounted fs or an umounted filesystem altogether: 'files-to-dump' is either a mountpoint of a filesystem or a list of files and directories on a single filesystem to be backed up as a subset of the filesystem. In the former case, either the path to a mounted filesystem or the device of an unmounted filesystem can be used. (dump(8)) DS ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: remote x session
On Dec 30, 2007 7:16 PM, Jonathan Horne [EMAIL PROTECTED] wrote: On Thursday 27 December 2007 02:35:05 am Steve Franks wrote: Perhaps I misunderstand, but I use x11vnc on the 'server' and vncviewer or tightvnc on the 'client'. There are several pages to google on tunneling it thru ssh, and it's much better with latency than sending x iteslf over ssh, I'm told. If you start x11vnc with no options, it will export the current session/desktop, but there is a switch to have it spawn a new x session also. All the other vnc ports only spawn new sessions, and I usually use it to help my wife fix problems when I'm away at the office ;) Best, Steve well ultimately, im looking for something that i can operate a headless server with. the server itself wouldnt be pre-logged into any x session (be it kde, gnome, xfce or whatever), so thats why im trying to get its x session into a window of my local desktop. There is the XDMCP option, which allows you to remotely connect to an X display manager for full, remote display sessions. This isn't regarded to be a secure solution by most people. If your remote system is a server, do you have a need for remote desktop access? If you have one or two X applications on the remote server, could you just get by with SSH X11 forwarding to access those applications from your management station's display? DS ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Still having problems burning DVDs
On Dec 29, 2007 3:41 PM, Andrew Falanga [EMAIL PROTECTED] wrote: Ok, Thanks to the help of earlier posts (a couple of weeks ago), using kldload atapicam now allows for the scsi ioctls on my IDE CD/DVD burner. However, when I do the following: growisofs -Z /dev/cd0 -dvd-video /usr/local/dvds/whereisGod1.iso I get this output: Executing 'mkisofs -dvd-video /usr/local/dvds/whereisGod1.iso | builtin_dd of=/dev/pass0 obs=32k seek=0' mkisofs: Value too large to be stored in data type. File /usr/local/dvds/whereisGod1.iso is too large - ignoring mkisofs: Unable to make a DVD-Video image. :-( write failed: Input/output error You should use the alternate syntax which takes a pre-mastered DVD image: growisofs -dvd-compat -Z /dev/cd0=/usr/local/dvds/whereisGod1.iso Notice how above it's trying to run mkisofs to create the image. You've supposedly already got the image, so no need to master. See '18.7.3 Burning Data DVDs'. DS ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Blocking undesirable domains using BIND
On Dec 28, 2007 8:49 AM, Kevin Kinsey [EMAIL PROTECTED] wrote: Olivier Nicole wrote: Again, I'm not trying to convince you otherwise or say that using BIND is a bad idea. It's just that I'm curious because we use Squid for this sort of thing, and I was wondering why BIND instead? I think another issue is that Squid will only filter HTTP/FTP connections, while DNS would allow to filter any type of traffic that would try to go to places with a bad name. Olivier In the absence of egress filtering on the firewall, that would definitely be an advantage. Does anyone use BIND for filtering in a small to medium business environment then? How does it perform? Performs fine. # rndc status number of zones: 17210 ... My 17000+ zones are loaded from the DNS-BH project and increase the startup time of named to about 10 seconds and bump the resident memory size up to about 55M. (AMD Duron 750MHz). There's no real performance hit per se by DNS blackholing, other than the resource utilization increase needed for handling additional zones; your name server would normally be handling these DNS lookups anyway.You're just overriding the response locally rather than recursing for it. The zones themselves typically end up being very small, like a single wildcard record pointing to 127.0.0.1 or a honeypot or whatever. DS ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Small Unix install
On Dec 28, 2007 10:56 AM, DAve [EMAIL PROTECTED] wrote: Good morning, I am looking for a small install for an old laptop. I have an old but quite reliable Toshiba 330CDT that used to be my personal laptop. I ran FBSD 3.x/4.x on it for years but it has been wiped and in a closet for years. I want to use it again just to access a few web forums and read my email. I don't do POV RAY or 3D, I don't need Open Office, I don't watch any Tubes. Mutt, Fluxbox and a minimal browser would make me happy. I don't have the time or inclination to roll my own again. PCBSD can't finish the install due to only having 96mb of memory. Desktop BSD wants more than 4gb of drive space just to complete the install. I currently have 98SE on it only consuming 300mb and it runs fine, but it's 98SE ;^) Does anyone know of anything ready to install? BSD, Linux, I don't care. Yes, there's plenty of options for very small Unix installs. Those you've tried have been the modern desktop-oriented distributions of FreeBSD and they of course don't shoot for the older class of systems. Unix has resisted bloat For example, I've put a smaller OpenBSD build on my Soekris that I run for a firewall on my cable connection. Fits in 22 MB: # df -h Filesystem SizeUsed Avail Capacity Mounted on /dev/wd0a 236M 22.1M202M10%/ Granted your desktop build will be plenty larger, but 300 MB is certainly achievable. Follow the advice for a minimal installation of the vanilla FreeBSD 6.x or 7 + whatever packages you need and you'll be rolling. You can find similar options in any of the BSDs and GNU/Linux. DS ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Blocking undesirable domains using BIND
On Dec 27, 2007 1:46 PM, Maxim Khitrov [EMAIL PROTECTED] wrote: Hello, I'm currently setting up a new firewall for my home network using FreeBSD 7. The firewall will also act as our local name server (authoritative for the local domain, and caching for everything else). One of the things I'd like to do with it is use BIND to block various undesirable domains (ad servers, malicious sites, etc.). The plan is to have a separate BIND config file which is included in the main one. In that file I map all the blocked domains to either the empty zone or perhaps my local web server that's just serving a blank page for any request. Haven't decided which way is better yet. This file is updated periodically (once a week maybe) and BIND is then told to reload the config. That's the plan as it stands now, eventually I hope to add a web interface to the system for adding and removing blocked domains. My question for you guys is if know any _reliable_ sources for getting that list of domains in the first place? I currently use the hosts file on all my machines, which is about 2MB in size and hasn't been updated in several years. I'll definitely import all of those entries myself, but it would be good if I could periodically pull an updated list from somewhere else. The following site has a pretty decent collection of ad servers, though it's a bit short compared to what I already have: http://pgl.yoyo.org/adservers/. It even provides the list in a BIND format, meaning that I don't need to do any additional processing with it. Just fetch the page and reload BIND. This, however, is not one of my requirements. I'm perfectly happy getting just a list of the domains (in any format), and then processing them into a BIND config file myself. Just need good sources. What are your recommendations? Look into the Blackhole-DNS project, formerly one of the BleedingThreats projects hosted at http://www.bleedingsnort.com/blackhole-dns/. This project tracks many hostile domains and produces BIND format files for this very purpose. It's not a great resource for ad blocking, as it focuses mainly on security threats (spyware, other malware, etc.) Since there has been some shuffling and reorganization happening around the BleedingThreats project, it's in a state of flux right now. The current home of the DNS-BH project is at http://malwaredomains.com/. -- Darren Spruell [EMAIL PROTECTED] ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: BIND9 won't start
On Dec 23, 2007 3:45 PM, QADMOS [EMAIL PROTECTED] wrote: Gelsema, P (Patrick) a écrit : On Sun, December 23, 2007 23:04, QADMOS wrote: Jonathan Horne a écrit : On Sunday 23 December 2007 02:52:43 pm QADMOS wrote: Hi everyone, i'm having a hard time with bind9. I'm trying to set up an authoritative dns server. Unfortunately when i try to launch it with an 'rndc start' i get this error message : rndc: connect failed: 127.0.0.1#953: connection refused do you get same problem with: /etc/rc.d/named start Well i've also tried that actually and when i do that : 1/ nothing is logged 2/ nothing is launched either Do you have the following in rc.conf? hulk# cat /etc/rc.conf | grep named named_enable=YES To me it seems your problem lies in the fact that named is not starting, so rndc can not control anything. Rgds, Patrick there's just no error message despite that the named is not running (checked with ps waux | grep named ) Well Patrick i followed your suggestion and rebooted (it didn't do much after just editing rc.conf) the box and now /etc/rc.d/named start works fine annd named is running, 'rndc' still has the same problem though (???) I'm a bit befuddled though, because i don't understand why it's necessary to use the named_enable directive to have named running ? I understand this is necessary if you want the daemon to run at boot time but why is this necessary if you want to run it manually once the box is on ? /etc/rc.d/named is the rc script to control (start, stop etc.) named, and this script is inactive unless you've specified that named is to be enabled using the named_enable variable. You can get around the need to activate the variable by prefixing your commands with the 'force' keyword (e.g. /etc/rc.d/named forcestart, etc.) Use sockstat(1) to figure out if the control port (953/tcp) is listening. 'sockstat -4l' should show a listener on 127.0.0.1:953. Also, 'start' is not a valid command to rndc. You would have a chicken and egg problem; if named has not been started, then there is no service to handle the start command to rndc. Use the rc script to start named and rndc to control its runtime operation. DS ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: BIND9 won't start
On Dec 23, 2007 10:43 PM, Jonathan McKeown [EMAIL PROTECTED] wrote: On Monday 24 December 2007 02:15, Jonathan Horne wrote: otherwise, there is always 'forcestart' intead of 'start'. and Darren Spruell wrote: You can get around the need to activate the variable by prefixing your commands with the 'force' keyword (e.g. /etc/rc.d/named forcestart, etc.) To start a service which isn't enabled in rc.conf, it's better to use onestart From the rc.subr(8) manpage: force Skip the checks for rcvar being set to ``YES'', and sets rc_force=YES. This ignores argument_precmd returning non-zero, and ignores any of the required_* tests failing, and always returns a zero exit status. oneSkip the checks for rcvar being set to ``YES'', but performs all the other prerequisite tests. Good to know, thx. DS ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
TCP window scaling 14
WD1600ADFS-75SLR2 21.07Q21 at ata2-master SATA300 ad6: 152587MB WDC WD1600ADFS-75SLR2 21.07Q21 at ata3-master SATA300 pcm0: HDA Codec: Sigmatel STAC9220 pcm0: HDA Driver Revision: 20071129_0050 acd0: FAILURE - INQUIRY ILLEGAL REQUEST asc=0x24 ascq=0x00 acd0: FAILURE - INQUIRY ILLEGAL REQUEST asc=0x24 ascq=0x00 ar0: 152585MB Intel MatrixRAID RAID1 status: READY ar0: disk0 READY (master) using ad4 at ata2-master ar0: disk1 READY (mirror) using ad6 at ata3-master SMP: AP CPU #1 Launched! SMP: AP CPU #7 Launched! SMP: AP CPU #2 Launched! SMP: AP CPU #3 Launched! SMP: AP CPU #6 Launched! SMP: AP CPU #5 Launched! SMP: AP CPU #4 Launched! cd0 at ata0 bus 0 target 0 lun 0 cd0: PHILIPS DVD+-RW DVD8801 AD21 Removable CD-ROM SCSI-0 device cd0: 33.000MB/s transfers cd0: Attempt to query device size failed: NOT READY, Medium not present Trying to mount root from ufs:/dev/ar0s1a -- Darren Spruell [EMAIL PROTECTED] ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Set perms on attach of USB umass disk
I've been trying (and failing) to figure out how to adjust ownership
or permissions of a USB memory stick on device attach.
umass0: SanDisk Corporation Cruzer Mini, rev 2.00/0.20, addr 5
da0 at umass-sim0 bus 0 target 0 lun 0
da0: SanDisk Cruzer Mini 0.4 Removable Direct Access SCSI-2 device
da0: 1.000MB/s transfers
da0: 977MB (2001888 512 byte sectors: 64H 32S/T 977C)
$ usbdevs -v
Controller /dev/usb0:
addr 1: full speed, self powered, config 1, UHCI root hub(0x),
Intel(0x), rev 1.00
port 1 addr 2: full speed, power 100 mA, config 1, Dell USB Keyboard
Hub(0x1004), Dell(0x413c), rev 48.01
port 1 addr 3: low speed, power 90 mA, config 1, Dell USB Keyboard
Hub(0x2006), Dell(0x413c), rev 48.00
port 2 addr 5: full speed, power 100 mA, config 1, Cruzer
Mini(0x5150), SanDisk Corporation(0x0781), rev 0.20
I've tried altering devfs.conf but this appears to only work for
devices that are attached at startup of devfs. I've tried configuring
devd(8):
attach 100 {
device-name da[0-9]+s1;
action /bin/chmod 0660 $device-name;
};
attach 100 {
device-name da[0-9]+;
action /bin/chmod 0660 $device-name;
};
Neither of these seem to result in the permission change I'm after
(making device writable by my user which is in the operator group):
$ ls -l /dev/da0*
crw-r- 1 root operator0, 165 Oct 21 13:08 /dev/da0
crw-r- 1 root operator0, 166 Oct 21 13:08 /dev/da0s1
What's the right way to handle this?
--
Darren Spruell
[EMAIL PROTECTED]
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Set perms on attach of USB umass disk
I've tried altering devfs.conf but this appears to only work for devices that are attached at startup of devfs. [snip] As a matter of fact, this is documented in the devfs.conf manual page. This will also tell you where to look; Yep: It does not work for devices plugged in and out after the system is up and running, e.g. USB devices. See devfs.rules(5) for setting ownership and permissions for all device nodes, and usbd.conf(5) for actions to be taken when USB devices are attached or detached. I overlooked that for some reason. :( create a new file /etc/devfs.rules with contents [system=10] add path 'da*' mode 660 group operator Then in /etc/rc.conf add devfs_system_ruleset=system and restart devfs (/etc/rc.d/devfs restart) Works great, thanks. -- Darren Spruell [EMAIL PROTECTED] ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Multiple Instances of OpenVPN
On 9/26/07, Marcos Vinicius Buzo [EMAIL PROTECTED] wrote: Good afternoon. I would like to know how could I run multiple instances of openvpn with one startup script for each config file. I'm running one instance with the /usr/local/etc/rc.d/openvpn script and another with the command openvpn --config configfile. Read the rc script that controls openvpn (/usr/local/etc/rc.d/openvpn). It has information about running multiple tunnels. DS ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: nvidia-driver rebooting machine on X startup
On 9/18/07, Eric Ekong [EMAIL PROTECTED] wrote:
Seems there is a new driver in ports as of yesterday for nvidia.
Anyone tried it as of yet?
The update alone hasn't done anything for me, but I'm thinking I'm
suffering from an issue not directly related to the driver itself;
stale libraries like Mel suggested, or something.
I just completed an update to xorg-7.3_1 following the procedure in
UPDATING 20070519. Now running FreeBSD 6.2-RELEASE-p7 and
nvidia-driver-100.14.11 and the reboot still occurs when starting X.
Something else I noticed is that my xorg.conf gets truncated to 0
bytes when I 'startx' and hit a reboot. I can't figure what would
cause this, and it's intermittent (post reboot I'll sometimes see the
file whole whole, sometimes truncated). Must be connected somehow to
the reboot?
On the off chance it had anything to do with stale libraries, how
would I determine which those were and how to right what is wrong? I
don't see anything notable in the output of ldconfig -r, but I'm not
certain I know what to look for. I'll include the ldconfig* related
configurations from rc.conf and ldconfig -r output below. Any other
ideas?
# grep -i ld /etc/{defaults/rc.conf,rc.conf}
/etc/defaults/rc.conf:# to change the default startup behavior of your
system. You should
/etc/defaults/rc.conf:# The ${rc_conf_files} files should only contain
values which override
/etc/defaults/rc.conf:kldxref_enable=NO # Build linker.hints files
with kldxref(8).
/etc/defaults/rc.conf:kldxref_clobber=NO # Overwrite old linker.hints at
boot.
/etc/defaults/rc.conf:kldxref_module_path=# Override
kern.module_path. A ';'-delimited list.
/etc/defaults/rc.conf:pflog_logfile=/var/log/pflog# where pflogd
should store the logfile
/etc/defaults/rc.conf: # node, you should stop
advertisement.
/etc/defaults/rc.conf:ldconfig_insecure=NO# Set to YES to disable
ldconfig security checks
/etc/defaults/rc.conf:ldconfig_paths=/usr/lib/compat /usr/X11R6/lib
/usr/local/lib /usr/local/lib/compat/pkg
/etc/defaults/rc.conf:ldconfig32_paths=/usr/lib32 # 32-bit
compatibility shared library search paths
/etc/defaults/rc.conf:ldconfig_paths_aout=/usr/lib/compat/aout
/usr/X11R6/lib/aout /usr/local/lib/aout
/etc/defaults/rc.conf:ldconfig_local_dirs=/usr/local/libdata/ldconfig
/usr/X11R6/libdata/ldconfig
/etc/defaults/rc.conf: # Local directories with ldconfig
configuration files.
/etc/defaults/rc.conf:ldconfig_local32_dirs=/usr/local/libdata/ldconfig32
/usr/X11R6/libdata/ldconfig32
/etc/defaults/rc.conf: # Local directories with 32-bit
compatibility ldconfig
/var/run/ld-elf.so.hints:
search directories:
/lib:/usr/lib:/usr/lib/compat:/usr/X11R6/lib:/usr/local/lib:/usr/local/lib/compat/pkg:/usr/local/lib/compat:/usr/local/lib/nss
0:-lcrypt.3 = /lib/libcrypt.so.3
1:-lkvm.3 = /lib/libkvm.so.3
2:-lm.4 = /lib/libm.so.4
3:-lmd.3 = /lib/libmd.so.3
4:-lncurses.6 = /lib/libncurses.so.6
5:-lsbuf.3 = /lib/libsbuf.so.3
6:-lutil.5 = /lib/libutil.so.5
7:-lalias.5 = /lib/libalias.so.5
8:-latm.3 = /lib/libatm.so.3
9:-lbegemot.2 = /lib/libbegemot.so.2
10:-lbsnmp.3 = /lib/libbsnmp.so.3
11:-lc.6 = /lib/libc.so.6
12:-lcam.3 = /lib/libcam.so.3
13:-ldevstat.5 = /lib/libdevstat.so.5
14:-ledit.5 = /lib/libedit.so.5
15:-lbsdxml.2 = /lib/libbsdxml.so.2
16:-lgeom.3 = /lib/libgeom.so.3
17:-lgpib.1 = /lib/libgpib.so.1
18:-lipsec.2 = /lib/libipsec.so.2
19:-lipx.3 = /lib/libipx.so.3
20:-lufs.3 = /lib/libufs.so.3
21:-lkiconv.2 = /lib/libkiconv.so.2
22:-lpcap.4 = /lib/libpcap.so.4
23:-lpthread.2 = /lib/libpthread.so.2
24:-lz.3 = /lib/libz.so.3
25:-lreadline.6 = /lib/libreadline.so.6
26:-lcrypto.4 = /lib/libcrypto.so.4
27:-lbsm.1 = /usr/lib/libbsm.so.1
28:-lcom_err.3 = /usr/lib/libcom_err.so.3
29:-lnetgraph.2 = /usr/lib/libnetgraph.so.2
30:-lradius.2 = /usr/lib/libradius.so.2
31:-lrpcsvc.3 = /usr/lib/librpcsvc.so.3
32:-ltacplus.2 = /usr/lib/libtacplus.so.2
33:-lypclnt.2 = /usr/lib/libypclnt.so.2
34:-larchive.2 = /usr/lib/libarchive.so.2
35:-lbluetooth.2 = /usr/lib/libbluetooth.so.2
36:-lbz2.2 = /usr/lib/libbz2.so.2
37:-lc_r.6 = /usr/lib/libc_r.so.6
38:-lcalendar.3 = /usr/lib/libcalendar.so.3
39:-ldevinfo.3 = /usr/lib/libdevinfo.so.3
40:-lfetch.4 = /usr/lib/libfetch.so.4
41:-lform.3 = /usr/lib/libform.so.3
42:-lftpio.6 = /usr/lib/libftpio.so.6
43:-lmagic.2 = /usr/lib/libmagic.so.2
44:-lmemstat.1 = /usr/lib/libmemstat.so.1
45:-lmenu.3 = /usr/lib/libmenu.so.3
46:-lmilter.3 = /usr/lib/libmilter.so.3
47:-lmp.5 = /usr/lib/libmp.so.5
48:-lncp.2 = /usr/lib/libncp.so.2
49:-lngatm.2 = /usr/lib/libngatm.so.2
Re: Good FreeBSD Supported Gigabit Ethernet Card?
On 9/13/07, Subhro Kar [EMAIL PROTECTED] wrote: Oliver Hansen wrote: I'm looking to eventually upgrade my home network to all gigabit so I'm going to start by purchasing a few NICs for some old servers I just received. I know there are quite a few supported by FreeBSD6 which I found ( http://www.freebsd.org/releases/6.0R/hardware-i386.html#ETHERNET ) but I'm wondering if there is any real benefit in buying a $40 or $50 NIC like the Netgear GA311 or just get a $20 NIC like the D-Link DFE-530TX+. The use will probably be a firewall, proxy, file server, and DVR. http://www.EagleBit.com/Netgear_GA311_Gigabit_PCI_Card_p/eb-400-00357.htm No offence meant, but why would you like to upgrade a home network to Gbit? Is it required at all? This is a useless response. Why do you feel the need to question his intentions? Maybe he wants faster throughput. Maybe he'd like to utilize GigE speeds on a switch he bought. Maybe he wants to learn more about gigabit networking. At any rate, why really doesn't matter. DS ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Strange port 80 access problem
On 9/12/07, Reid Linnemann [EMAIL PROTECTED] wrote: Written by Beech Rintoul on 09/12/07 11:14 It's very possible that your ISP is blocking port 80. It seems more and more of them are doing that with home subscribers. I know someone who has service with one of the large telcos and they not only block port 80, but mail and ftp as well. They told him if he wanted to run servers he would have to subscribe to business service at 5X the cost of residential. I've had a similar experience with COX Communications in the US midwest. They block http, https, alternate http ports like 8000 and 8080, smtp, and I think pop and imap/imaps. I'm sure part of the reason for this paranoid behavior is to protect their networks from saturation from bots and whatnot, but part of me thinks they just want to stick it to their customers whom they view as pesky annoyances rather than valuable consumers. I circumvent these hassles by boring ssh tunnels to the services I need access to on my home machines. This is a stopgap until I get time to fiddle with openvpn. It might depend where you are on their network, but there's some inconsistencies with the blocking. Port 80 is blocked, but port 443 is allowed. Port 25 is blocked, but 587 is allowed. 135, 137, 139, and 445 are blocked. 8080, 8081, and 1 get through to my network. Most other ports are allowed by default. Like it or hate it, it's a control designed to support their subscriber AUP, which states pretty plainly that customers are forbidden to host servers on the home user accounts (http://www.cox.com/policy/ #6). Business lines have such restrictions listed and allow hosting services by policy, and puts the burden of security on the customer rather than attempting to enforce by technical means. DS ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: nvidia-driver rebooting machine on X startup
On 9/11/07, Bruce Cran [EMAIL PROTECTED] wrote: Mel wrote: There's 3 things left I can think of: - weird module clash - bug in nvidia-driver (I assume you're running Xorg 7.x) - driver was not built against running kernel I'm seeing a similar problem, but my system spontaneously reboots whenever it uses any 3D - for example any of the 3D xscreensaver modules in full screen mode. I'm running 7.0-CURRENT and just realised I have PREEMPTION enabled since it's now in GENERIC. I remember a while ago this caused stability problems with the nvidia driver - does anyone know if this could still be a problem? I think there's more going on however, since the driver doesn't seem to know about my card during bootup (it shows Unknown) though it clearly does find it when starting Xorg. Going back to the nvidia-driver-96xx port appears to fix the problems, and that driver does know what nVidia card I'm using during boot. 3 of us have posted a thread on nvidia forums as problem reports; I've at least tried an older (legacy) driver version to no luck and eliminated every suggestion I've gotten from the fbsd community as well. If anyone would like, feel free to piggyback on the thread. There's been no help response on the forums for a couple of days now. http://forums.nvidia.com/index.php?showtopic=45590 If this *is* an issue with the nvidia driver, is there a good way for us to alert Nvidia? Customer support, I guess? -- Darren Spruell [EMAIL PROTECTED] ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: nvidia-driver rebooting machine on X startup
On 9/6/07, Derek Ragona [EMAIL PROTECTED] wrote: At 03:10 PM 9/6/2007, Darren Spruell wrote: Wondering if this is a known issue, or if anyone has suggestions to get it working...? Running FreeBSD 6.2-RELEASE-p4 SMP i386. I installed nvidia-driver-100.14.11 from ports (Sep. 5 snapshot), Linux compatibility enabled. After loading modules 'linux' and 'nvidia', I do: # X -configure # X -config /root/xorg.conf.new At this point the system spontaneously reboots. 'X -configure' runs fine and produces a configuration without issue, but the reboot occcurs when launching X. Nothing is output to screen (it flickers as if starting X), and nothing is written to /var/log/Xorg.0.log. I do get the same behavior if running 'xorgcfg'. Card info: NV41 [Quadro FX 3450/4000 SDI] rev 162 [EMAIL PROTECTED]:0:0: class=0x03 card=0x029b10de chip=0x00cd10de rev=0xa2 hdr=0x00 vendor = 'NVIDIA Corporation' class= display subclass = VGA I've tried an alternate version of the binary driver (nvidia-driver-96xx) to see if there was any change, and it also reboots on X startup. -- Check your AGP settings and consult the readme, chapter 9, for the latest driver. You should be running the latest driver with your card. Make sure you have the correct AGP settings, either letting FreeBSD do it in the kernel or disable the kernel and let the Nvidia driver manage it. So, I'm not having terrific luck with any combination of settings I try. The latest FreeBSD driver release from Nvidia is the same as the version in the ports tree. This is what I've installed. Attempting the AGPGART route (building the driver with WITH_FREEBSD_AGP=yes and disabling NvAgp support in xorg.conf) still results in a reboot. Going the NvAGP route (Building without support for AGPGART, setting NvAgp to 1 in the xorg.conf, and setting hint.agp.0.disabled=1 in /boot/device.hints) also results in a reboot when X starts. One thing I notice here; when I specify hint.agp.0.disabled=1, and check the output of 'kldstat -v' after booting, I still see several agp drivers loaded: $ kldstat -v |grep -i agp 387 pci/agp_ali 388 pci/agp_amd 389 pci/agp_amd64 390 pci/agp_ati 391 pci/agp_i810 392 pci/agp_intel 393 pci/agp_nvidia 394 pci/agp_sis 395 pci/agp_via Is this a problem? I suspect a couple of problems with what I'm doing. Number one, there's several knobs to turn (in the driver, in the OS, etc.) and it's possible I'm not getting the correct combination. Other thing is, I've been told by a technician that this is a PCI Express video card, so would AGP even come into play? DS ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: nvidia-driver rebooting machine on X startup
On 9/7/07, Mel [EMAIL PROTECTED] wrote: On Friday 07 September 2007 19:43:03 Darren Spruell wrote: On 9/6/07, Derek Ragona [EMAIL PROTECTED] wrote: At 03:10 PM 9/6/2007, Darren Spruell wrote: Wondering if this is a known issue, or if anyone has suggestions to get it working...? Running FreeBSD 6.2-RELEASE-p4 SMP i386. I installed nvidia-driver-100.14.11 from ports (Sep. 5 snapshot), Linux compatibility enabled. After loading modules 'linux' and 'nvidia', I do: # X -configure # X -config /root/xorg.conf.new At this point the system spontaneously reboots. 'X -configure' runs fine and produces a configuration without issue, but the reboot occcurs when launching X. Nothing is output to screen (it flickers as if starting X), and nothing is written to /var/log/Xorg.0.log. I do get the same behavior if running 'xorgcfg'. Card info: NV41 [Quadro FX 3450/4000 SDI] rev 162 [EMAIL PROTECTED]:0:0: class=0x03 card=0x029b10de chip=0x00cd10de rev=0xa2 hdr=0x00 vendor = 'NVIDIA Corporation' class= display subclass = VGA I've tried an alternate version of the binary driver (nvidia-driver-96xx) to see if there was any change, and it also reboots on X startup. -- Check your AGP settings and consult the readme, chapter 9, for the latest driver. You should be running the latest driver with your card. Make sure you have the correct AGP settings, either letting FreeBSD do it in the kernel or disable the kernel and let the Nvidia driver manage it. So, I'm not having terrific luck with any combination of settings I try. The latest FreeBSD driver release from Nvidia is the same as the version in the ports tree. This is what I've installed. Attempting the AGPGART route (building the driver with WITH_FREEBSD_AGP=yes and disabling NvAgp support in xorg.conf) still results in a reboot. Going the NvAGP route (Building without support for AGPGART, setting NvAgp to 1 in the xorg.conf, and setting hint.agp.0.disabled=1 in /boot/device.hints) also results in a reboot when X starts. One thing I notice here; when I specify hint.agp.0.disabled=1, and check the output of 'kldstat -v' after booting, I still see several agp drivers loaded: $ kldstat -v |grep -i agp 387 pci/agp_ali 388 pci/agp_amd 389 pci/agp_amd64 390 pci/agp_ati 391 pci/agp_i810 392 pci/agp_intel 393 pci/agp_nvidia 394 pci/agp_sis 395 pci/agp_via Is this a problem? I suspect a couple of problems with what I'm doing. Number one, there's several knobs to turn (in the driver, in the OS, etc.) and it's possible I'm not getting the correct combination. Other thing is, I've been told by a technician that this is a PCI Express video card, so would AGP even come into play? Probably not. I'm seeing the same thing on one machine, no AGP on MB, and agp kernel modules loaded, but nvidia-driver doesn't care about it. Let's kill all red herrings: - Is COMPAT5X in the kernel? COMPAT5X doesn't show up anywhere in /usr/src/; I do have 'options COMPAT_FREEBSD5' defined, though (stock SMP kernel). - Does running `nvidia-xconfig --query-gpu-info' reboot the system? - If you do not load the nvidia kernel module, but use Xorg's nv driver does this reboot the system? No, doesn't reboot the system. Output attached below. With the 'nv' driver, X starts fine. I don't use it because I don't have success with the two output displays and xinerama window sizing. nvidia-xconfig --query-gpu-info: Number of GPUs: 1 GPU #0: Name : Quadro FX 3450/4000 SDI PCI BusID : PCI:7:0:0 Number of Display Devices: 2 Display Device 0 (CRT-0): EDID Name : DELL 2001FP Minimum HorizSync : 31.000 kHz Maximum HorizSync : 80.000 kHz Minimum VertRefresh : 56 Hz Maximum VertRefresh : 76 Hz Maximum PixelClock: 162.000 MHz Maximum Width : 1600 pixels Maximum Height: 1200 pixels Preferred Width : 1600 pixels Preferred Height : 1200 pixels Preferred VertRefresh : 60 Hz Physical Width: 410 mm Physical Height : 310 mm Display Device 1 (CRT-1): EDID Name : DELL 2001FP Minimum HorizSync : 31.000 kHz Maximum HorizSync : 80.000 kHz Minimum VertRefresh : 56 Hz Maximum VertRefresh : 76 Hz Maximum PixelClock: 162.000 MHz Maximum Width : 1600 pixels Maximum Height: 1200 pixels Preferred Width : 1600 pixels Preferred Height : 1200 pixels Preferred VertRefresh : 60 Hz Physical Width: 410 mm Physical Height : 310 mm -- Darren Spruell [EMAIL PROTECTED
nvidia-driver rebooting machine on X startup
pending error: blocks 0 files 1 WARNING: /usr was not properly dismounted WARNING: /var was not properly dismounted bge0: firmware handshake timed out xorg.conf.new Section ServerLayout Identifier X.org Configured Screen 0 Screen0 0 0 InputDeviceMouse0 CorePointer InputDeviceKeyboard0 CoreKeyboard EndSection Section Files RgbPath /usr/local/share/X11/rgb ModulePath /usr/local/lib/xorg/modules FontPath /usr/local/lib/X11/fonts/misc/ FontPath /usr/local/lib/X11/fonts/TTF/ FontPath /usr/local/lib/X11/fonts/OTF FontPath /usr/local/lib/X11/fonts/Type1/ FontPath /usr/local/lib/X11/fonts/100dpi/ FontPath /usr/local/lib/X11/fonts/75dpi/ EndSection Section Module Load dbe Load dri Load extmod Load record Load xtrap Load glx Load freetype Load type1 EndSection Section InputDevice Identifier Keyboard0 Driver kbd EndSection Section InputDevice Identifier Mouse0 Driver mouse Option Protocol auto Option Device /dev/sysmouse Option ZAxisMapping 4 5 6 7 EndSection Section Monitor Identifier Monitor0 VendorName Monitor Vendor ModelNameMonitor Model EndSection Section Device Identifier Card0 Driver nvidia VendorName nVidia Corporation BoardName NV41 [Quadro FX 3450/4000 SDI] BusID PCI:7:0:0 EndSection Section Screen Identifier Screen0 Device Card0 MonitorMonitor0 SubSection Display Viewport 0 0 Depth 1 EndSubSection SubSection Display Viewport 0 0 Depth 4 EndSubSection SubSection Display Viewport 0 0 Depth 8 EndSubSection SubSection Display Viewport 0 0 Depth 15 EndSubSection SubSection Display Viewport 0 0 Depth 16 EndSubSection SubSection Display Viewport 0 0 Depth 24 EndSubSection EndSection -- Darren Spruell [EMAIL PROTECTED] ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: nvidia-driver rebooting machine on X startup
On 9/6/07, Mel [EMAIL PROTECTED] wrote: On Thursday 06 September 2007 22:10:42 Darren Spruell wrote: Wondering if this is a known issue, or if anyone has suggestions to get it working...? Running FreeBSD 6.2-RELEASE-p4 SMP i386. I installed nvidia-driver-100.14.11 from ports (Sep. 5 snapshot), Linux compatibility enabled. After loading modules 'linux' and 'nvidia', I do: # X -configure # X -config /root/xorg.conf.new At this point the system spontaneously reboots. 'X -configure' runs fine and produces a configuration without issue, but the reboot occcurs when launching X. Nothing is output to screen (it flickers as if starting X), and nothing is written to /var/log/Xorg.0.log. I do get the same behavior if running 'xorgcfg'. Card info: NV41 [Quadro FX 3450/4000 SDI] rev 162 [EMAIL PROTECTED]:0:0: class=0x03 card=0x029b10de chip=0x00cd10de rev=0xa2 hdr=0x00 vendor = 'NVIDIA Corporation' class= display subclass = VGA Section Device Identifier Card0 Driver nvidia VendorName nVidia Corporation BoardName NV41 [Quadro FX 3450/4000 SDI] BusID PCI:7:0:0 EndSection Removing BusID do anything? All those Displays sounds a bit much too. I *strongly* recommend using nvidia-xconfig (x11/nvidia-config). Commenting BusID has the same effect - prompt reboot. The Display subsections are pretty standard for every X configuration I've ever used; why would they cause a problem in this case? And anything /var/log/Xorg.0.log? Using nvAgp or FreeBSD Agp? No, nothing gets to the log before reboot occurs. Not using either of nvAgp or FreeBSD Agp, that I'm aware of. I did not enable FREEBSD_AGP at build time. DS ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: nvidia-driver rebooting machine on X startup
On 9/6/07, Jona Joachim [EMAIL PROTECTED] wrote: On Thu, 6 Sep 2007 13:10:42 -0700 Darren Spruell [EMAIL PROTECTED] wrote: Wondering if this is a known issue, or if anyone has suggestions to get it working...? Running FreeBSD 6.2-RELEASE-p4 SMP i386. I installed nvidia-driver-100.14.11 from ports (Sep. 5 snapshot), Linux compatibility enabled. After loading modules 'linux' and 'nvidia', I do: # X -configure # X -config /root/xorg.conf.new At this point the system spontaneously reboots. 'X -configure' runs fine and produces a configuration without issue, but the reboot occcurs when launching X. Nothing is output to screen (it flickers as if starting X), and nothing is written to /var/log/Xorg.0.log. I do get the same behavior if running 'xorgcfg'. Did you reinstall/upgrade X after having installed nvidia-driver? X actually overwrites libraries that nvidia-driver installs so you have to reinstall nvidia-driver every time you upgrade X. I remember having had some bad crashes some time ago because X overwrote nvidia GLX libraries. Best regards, Jona Nope - driver was the most recent thing installed. I'm looking into AGP options as suggested earlier... didn't realize that this _needed_ AGP support to function. -- Darren Spruell [EMAIL PROTECTED] ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
xset dpms during X startup?
Is it possible to configure xset(1) DPMS settings in a ~/.xsession file for when a login session starts? I have the following ~/.xsession file: /usr/X11R6/bin/xset -b /usr/X11R6/bin/xset dpms 1800 7200 14400 /usr/X11R6/bin/xscreensaver -no-splash exec startfluxbox But after logging into XDM after X is restarted 'xset q' still shows: DPMS (Energy Star): Standby: 7200Suspend: 7200Off: 14400 DPMS is Disabled Option DPMS is enabled in my xorg.conf. Is there something I don't know about DPMS and .xsession? FreeBSD 6.0-RELEASE-p4 xorg-6.9.0 fluxbox-devel-0.9.14_1 TIA, -- Darren Spruell [EMAIL PROTECTED] ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
OpenSSH 3.6.1 support in RELENG_5_0?
Greetz, I just updated from 5.0 release per the RELENG_5_0 tag. I had expected that the source tree would then contain openssh-3.6.1p but after a make installworld I see that it is still at 'OpenSSH_3.5p1 FreeBSD-20021029' (according to a scanssh query.) Should I be seeing 3.6.1 or is it not in the tree? TIA -- Darren Spruell Sento I.S. Department [EMAIL PROTECTED] ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: OpenSSH 3.6.1 support in RELENG_5_0?
Dan Nelson wrote: In the last episode (Jul 23), Darren Spruell said: I just updated from 5.0 release per the RELENG_5_0 tag. I had expected that the source tree would then contain openssh-3.6.1p but after a make installworld I see that it is still at 'OpenSSH_3.5p1 FreeBSD-20021029' (according to a scanssh query.) Should I be seeing 3.6.1 or is it not in the tree? RELENG_5_0 is the branch for people that are running 5.0 on production systems and only want security patches. I doubt RELENG_5_0 has many differences from RELENG_5_0_0_RELEASE. You probably want to track either HEAD or RELENG_5_1, since openssh 3.6.1 got imported before FreeBSD 5.1 was released. Or if you want to stick with 5.0, install the openssh port. $ uname -r 5.1-CURRENT $ /usr/bin/ssh -V OpenSSH_3.6.1p1 FreeBSD-20030423, SSH protocols 1.5/2.0, OpenSSL 0x0090701f $ _ Hope you don't mind me asking. I'm more familiar with OpenBSD's model which is strictly two CVS tags: M_m and OPENBSD_M_m which are -current and -stable respectively, with M being major version and m being minor version. So OPENBSD_3_2 tag would be -stable for 3.2 (if I understand correctly, that is...) What is HEAD and RELENG_5_1 in FreeBSD? It sounds like the tag RELENG_5_0 that I followed is little more than the critical patch branch for 5.0; how do I accomplish following the -stable branch, if there exists one: something in between strictly neccesary patches and possibly buggy Current? -- Darren Spruell Sento I.S. Department [EMAIL PROTECTED] ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
{SOLVED}Re: Trouble mounting USB pen drive in 4.7
Joshua Oreman wrote: On Tue, Mar 18, 2003 at 11:38:48PM -0700 or thereabouts, darren_spruell wrote: Filesystem = unknown. I am able to mount it under Windows 2000 Pro and in the past on an identical FreeBSD box. I believe the command I used was 'mount /dev/rda0 /mnt' and it worked, sometimes. Under Linux it mounts flawlessly with 'mount /dev/sda /mnt'... The device is not partitioned. Now all my attempts under FreeBSD end in ...I/O error. To find out the filesystem: # file -s /dev/da0 This will run 'file' on the contents of the drive (-s flag) instead of the drive itself (otherwise, it would say `character device' or something). Some common `mount' commands you could use: If `file' says something about DOS or Windows: # kldload msdosfs # mount_msdosfs /dev/da0 /mnt If `file' says it's UFS: # mount /dev/da0 /mnt If `file' says it's ext2: # kldload ext2fs # mount_ext2fs /dev/da0 /mnt Otherwise, send me the output of the file command above and I'll see what I can do. Notes: 1) If you're running 4.x, replace 'msdosfs' with 'msdos' above. 2) `mount' wants /dev/da0, not /dev/rda0. -- Darren Spruell Sento IS Department [EMAIL PROTECTED] Hope this helps, Josh This is with the device plugged into the USB port, but not mounted: # file -s /dev/da0 file /dev/da0: can't read `/dev/da0' (Input/output error). I found out that I can mount it like this: # mount -t msdos /dev/rd0s1 /mnt Output with device mounted: # file -s /dev/da0 /dev/da0: x86 boot sector So, I can mount it now, knowing that I have to mount it as msdos, and that I must mount /dev/rda0s1 (wouldn't have thought to mount just a slice...?) -- Darren Spruell Sento I.S. Department [EMAIL PROTECTED] To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-questions in the body of the message
Trouble mounting USB pen drive in 4.7
Greetz, running 4.7 RELEASE and I insert my USB pocket drive into USB slot. I see the following come into my dmesg: umass0: USB Solid state disk, rev 1.10/1.00, addr 2 da0 at umass-sim0 bus 0 target 0 lun 0 da0: Generic Traveling Disk 1.11 Removable Direct Access SCSI-2 device da0: 650KB/s transfers da0: 126MB (258048 512 byte sectors: 64H 32S/T 126C) How can I mount this onto my filesystem? I've tried variations of the da driver (rda0, da0, rda0s1, etc...) but I get I/O errors... Many TIA, -- Darren Spruell Sento IS Department [EMAIL PROTECTED] To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-questions in the body of the message
printing to HP LaserJet 4050 TN
We have this printer set up to print to from the network and I have printed to it by IP address before. It is connected to a Windows server but I would like to print directly to it by IP from my fbsd 4.7 box. I have installed the cups-base, cups-pstoraster, and ghostscript-gnu packages. Afterwards I looked through the Handbook but didn't see anything that cleared up the process of configuring this printer. TIA, -- Darren Spruell Sento IS Department [EMAIL PROTECTED] To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-questions in the body of the message
USB flash drive mount - da device?
Greetz, I use a USB pocket drive and am having the hardest time figuring out how to mount it into the filesystem. Following are what I thought to be important: # dmesg |grep da0 da0 at umass-sim0 bus 0 target 0 lun 0 da0: Generic Traveling Disk 1.11 Removable Direct Access SCSI-2 device da0: 650KB/s transfers da0: 126MB (258048 512 byte sectors: 64H 32S/T 126C) da0: reading primary partition table: error reading fsbn 0 da0: reading primary partition table: error reading fsbn 0 (da0:umass-sim0:0:0:0): READ(6)/WRITE(6) not supported, increasing minimum_cmd_size to 10. # ps auxwww |grep usbd root 78 0.0 0.2 916 580 ?? Ss 12:03PM 0:00.01 /usr/sbin/usbd === Generally I use the command 'mount -t msdos /dev/rda0s1 /mnt' to mount this to my filesystem. Sometimes it works, sometimes it fails. When it does work I can only mount it as root. In order to be able to mount this as a regular user, do I have to put some flags into a line in /etc/fstab? What would be the best way to make this drive user mountable? The other question is, is there a better way to mount up the device or control it via a usb tool or is the way I am doing it correct? TIA. -- Darren Spruell Sento I.S. Department [EMAIL PROTECTED] To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-questions in the body of the message
ftp_proxy syntax
Hi, I'm trying to enable apps such as ftp and yafc to use our Squid proxy for outgoing FTP connections, but my environment variable doesn't seem to work... === [darren@freebsd:~]$ echo $SHELL /usr/local/bin/bash [darren@freebsd:~]$ export ftp_proxy=squid.sento.com:8080 [darren@freebsd:~]$ echo $ftp_proxy squid.sento.com:8080 [darren@freebsd:~]$ ftp ftp.FreeBSD.org ^C[darren@freebsd:~]$ yafc ftp.FreeBSD.org yafc 0.7.10 Copyright (C) 1998-2001 Martin Hedenfalk [EMAIL PROTECTED]. This program comes with ABSOLUTELY NO WARRANTY; for details type 'warranty'. This is free software; type 'copyright' for details. Connecting to ftp.beastie.tdk.net (62.243.72.50) at port 21... === ...and just sits there. Shouldn't the connection be made to squid.sento.com:8080? Trying to run 'ftp ftp.gnu.org' from shell ends up doing the same thing. What am I doing wrong? I know our proxy listens on 8080 and supports FTP. TIA, -- Darren Spruell Sento IS Department [EMAIL PROTECTED] To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-questions in the body of the message
Re: X problems on i810 | AddScreen/ScreenInit failed
Shantanu Mahajan wrote: in which file you have made changes? from the logs, you are using ./XF86Config.new Make changes in that file. Regards, Shantanu That is the file I am changing and testing (/root/XF86Config.new). +++ Darren Spruell [10-02-03 13:28 -0700]: | Date: Mon, 10 Feb 2003 13:28:42 -0700 | From: Darren Spruell [EMAIL PROTECTED] | User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.1) Gecko/20020826 | To: Shantanu Mahajan [EMAIL PROTECTED] | CC: [EMAIL PROTECTED] | Subject: Re: X problems on i810 | AddScreen/ScreenInit failed | | Shantanu Mahajan wrote: | try adding following lines | | in Device section | Option NoDDC | | in Monitor section | Option DPMS | | Regards, | Shantanu | | Added as suggested. Relevant sections now read: | | Section Monitor | Identifier Monitor0 | Option DPMS | VendorName Gateway | ModelNameEV700 | HorizSync30 - 69 | VertRefresh 50 - 110 | EndSection | | Section Device | ### Available Driver options are:- | ### Values: i: integer, f: float, bool: True/False, | ### string: String, freq: f Hz/kHz/MHz | ### [arg]: arg optional | #Option ShadowFB # [bool] | #Option VGAClocks # [bool] | Option NoDDC | Identifier Card0 | Driver vga | VendorName Intel | BoardName i810-dc100 | BusID PCI:0:1:0 | EndSection | | | | Still the same error occurs. Here is the full output of the | /var/log/XFree86.0.log for this attempt: | | | | XFree86 Version 4.2.1 / X Window System | (protocol Version 11, revision 0, vendor release 6600) | Release Date: 3 September 2002 | If the server is older than 6-12 months, or if your card is | newer than the above date, look for a newer version before | reporting problems. (See http://www.XFree86.Org/) | Build Operating System: FreeBSD 5.0-CURRENT i386 [ELF] | 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 14:23:18 2003 | (++) Using config file: ./XF86Config.new | (==) ServerLayout XFree86 Configured | (**) |--Screen Screen0 (0) | (**) | |--Monitor Monitor0 | (**) | |--Device Card0 | (**) |--Input Device Mouse0 | (**) |--Input Device Keyboard0 | (==) 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.1 | XFree86 Video Driver: 0.5 | XFree86 XInput driver : 0.3 | XFree86 Server Extension : 0.1 | XFree86 Font Renderer : 0.3 | (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.1, module version = 1.0.0 | Module class: XFree86 Font Renderer | ABI class: XFree86 Font Renderer, version 0.3 | (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.1, module version = 0.1.0 | ABI class: XFree86 Video Driver, version 0.5 | (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,7122 card , rev 03 class 06,00,00 | hdr 00 | (II) PCI: 00:01:0: chip 8086,7123 card 8086,5355 rev 03 class 03,00,00 | hdr 00 | (II) PCI: 00:1e:0: chip 8086,2418 card , rev 02 class 06,04,00 | hdr 01 | (II) PCI: 00:1f:0: chip 8086,2410 card , rev 02 class 06,01,00 | hdr 80 | (II) PCI: 00:1f:1: chip 8086,2411 card 8086,2411 rev 02 class 01,01,80 | hdr 00 | (II) PCI: 00:1f:2: chip 8086,2412 card 8086,2412 rev 02 class 0c,03,00 | hdr 00 | (II) PCI: 00:1f:3: chip 8086,2413 card 8086,2413 rev 02 class 0c,05,00 | hdr 00 | (II) PCI: 00:1f:5: chip 8086,2415 card 8086,5355 rev 02 class 04,01,00 | hdr 00 | (II) PCI: 01:01:0: chip 8086,1229 card 8086,3002 rev 08 class 02,00,00 | hdr 00 | (II) PCI: End of PCI scan | (II) LoadModule: scanpci | (II) Loading /usr/X11R6/lib/modules/libscanpci.a | (II) Module scanpci: vendor=The XFree86 Project | compiled for 4.2.1, module version = 0.1.0 | ABI class: XFree86 Video Driver, version 0.5 | (II) UnloadModule
Re: X problems on i810 | AddScreen/ScreenInit failed
Andrew Lankford wrote: To my knowledge, DRI extensions have never worked with i810 on FreeBSD. Whenever I felt tinkering with the config to see I could enable DRI, it wouldn't take, but I don't think it ever mucked up my screen. My video monitor did have some trouble with the DDC option (on my stable partition, just after I had upgraded the bios), but DDC seems to work ok now. If you do get it working, I would stay with a DefaultDepth of 16 instead of 24, as a setting of 24 tends to slow demanding apps down without noticeably improving picture quality. Notice also that the HorizSync and VertRefresh values are a tiny bit different on mine as well. Anyway, here's my XF86Config: [...] Aargh. I tried both the changes you suggested, as well as adjusting only the relevant parts of your config and trying it.. same result in both cases. I even pulled a Red Hat 7.3 XFree86-4 config off of a working X station and adjusted paths, etc. Same stupid staticy crap with the white square ;) Anyway. I hate getting whooped by something this stupid, but I'm at wit's end. Any other suggestions? If not, I found another huddy OEM Gateway box with a different video card. I've got half a mind to try X out on it. -- Darren Spruell Sento IS Department [EMAIL PROTECTED] To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-questions in the body of the message
X problems on i810 | AddScreen/ScreenInit failed
controller port 0xffa0-0xffaf at device 31.1 on pci0 ata0: at 0x1f0 irq 14 on atapci0 ata1: at 0x170 irq 15 on atapci0 uhci0: Intel 82801AA (ICH) USB controller port 0xef80-0xef9f irq 10 at device 31.2 on pci0 usb0: Intel 82801AA (ICH) USB controller on uhci0 usb0: USB revision 1.0 uhub0: Intel UHCI root hub, class 9/0, rev 1.00/1.00, addr 1 uhub0: 2 ports with 2 removable, self powered pci0: unknown card (vendor=0x8086, dev=0x2413) at 31.3 irq 9 chip1: Intel 82801AA (ICH) AC'97 Audio Controller port 0xef00-0xef3f,0xe800-0xe8ff irq 9 at device 31.5 on pci0 orm0: Option ROMs at iomem 0xc-0xc9fff,0xcc000-0xccfff on isa0 fdc0: NEC 72065B or clone at port 0x3f0-0x3f5,0x3f7 irq 6 drq 2 on isa0 fdc0: FIFO enabled, 8 bytes threshold fd0: 1440-KB 3.5 drive on fdc0 drive 0 atkbdc0: Keyboard controller (i8042) at port 0x60,0x64 on isa0 atkbd0: AT Keyboard flags 0x1 irq 1 on atkbdc0 kbd0 at atkbd0 psm0: failed to get data. psm0: PS/2 Mouse irq 12 on atkbdc0 psm0: model IntelliMouse, device ID 3 vga0: Generic ISA VGA at port 0x3c0-0x3df iomem 0xa-0xb on isa0 sc0: System console at flags 0x100 on isa0 sc0: VGA 16 virtual consoles, flags=0x300 sio0 at port 0x3f8-0x3ff irq 4 flags 0x10 on isa0 sio0: type 16550A sio1: configured irq 3 not in bitmap of probed irqs 0 ppc0: Parallel port at port 0x378-0x37f irq 7 on isa0 ppc0: SMC-like chipset (ECP/EPP/PS2/NIBBLE) in COMPATIBLE mode ppc0: FIFO with 16/16/8 bytes threshold plip0: PLIP network interface on ppbus0 lpt0: Printer on ppbus0 lpt0: Interrupt-driven port ppi0: Parallel I/O on ppbus0 ad0: 14324MB QUANTUM FIREBALLlct15 15 [29104/16/63] at ata0-master UDMA66 acd0: MODE_SENSE_BIG trying to write on read buffer acd0: MODE_SENSE_BIG - NO SENSE asc=0x00 ascq=0x00 error=0x04 acd0: CDROM CD-224E at ata1-slave PIO4 Mounting root from ufs:/dev/ad0s1a WARNING: / was not properly dismounted THANKS IN ADVANCE!!! -- Darren Spruell Sento IS Department [EMAIL PROTECTED] To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-questions in the body of the message
Re: X problems on i810 | AddScreen/ScreenInit failed
. Please report problems to [EMAIL PROTECTED] +++ Darren Spruell [freebsd] [10-02-03 11:07 -0700]: | Date: Mon, 10 Feb 2003 11:07:22 -0700 | From: Darren Spruell [EMAIL PROTECTED] | Subject: X problems on i810 | AddScreen/ScreenInit failed | | Greetz, | | I'm trying to configure v4.7 to run X but am having a hard time getting | the server to start. | | I've followed the config instructions at | http://www.freebsd.org/doc/en_US.ISO8859-1/books/handbook/x-config.html | by doing the following steps: | | Run XFree86 -configure | to create the default XF86Config.new | Run XFree86 -xf86config ./XF86Config.new | to ensure that it works w/my hardware | Edit it to taste, to change specifics for HorizSync, VertRefresh, and | the Display subsection under Screen. | | However, running 'XFree86 -xf86config ./XF86Config.new' after changing | my config does not work. The output error is: | | == | (==) VGA(0): Write-combining range (0xa,0x1) was already clear | | Fatal server error: | AddScreen/ScreenInit failed for driver 0 | == | | I followed through the part in the Advanced Configuration section about | adding in support for agpgart and created the device node and added the | following to /boot/loader.conf: | agp_load=YES | | dmesg now shows: | Preloaded elf module agp.ko at 0xc051a09c. | agp0: Intel 82810-DC100 (i810-DC100 GMCH) SVGA controller mem | 0xffa8-0xffaf,0xf800-0xfbff irq 11 at device 1.0 on pci0 | | Here is the current XF86Config.new (non-working). The Monitor section | was taken from a specs page on the Monitor (Gateway EV700). Full dmesg | included below this: | | Section ServerLayout | Identifier XFree86 Configured | Screen 0 Screen0 0 0 | InputDeviceMouse0 CorePointer | InputDeviceKeyboard0 CoreKeyboard | EndSection | | Section Files | RgbPath /usr/X11R6/lib/X11/rgb | ModulePath /usr/X11R6/lib/modules | FontPath /usr/X11R6/lib/X11/fonts/misc/ | FontPath /usr/X11R6/lib/X11/fonts/Speedo/ | FontPath /usr/X11R6/lib/X11/fonts/Type1/ | FontPath /usr/X11R6/lib/X11/fonts/75dpi/ | FontPath /usr/X11R6/lib/X11/fonts/100dpi/ | EndSection | | Section Module | Load dbe | Load dri | Load extmod | Load glx | Load pex5 | Load record | Load xie | Load xtrap | Load speedo | Load type1 | EndSection | | Section InputDevice | Identifier Keyboard0 | Driver keyboard | EndSection | | Section InputDevice | Identifier Mouse0 | Driver mouse | Option Protocol MouseSystems | Option Device /dev/sysmouse | EndSection | | Section Monitor | Identifier Monitor0 | VendorName Gateway | ModelNameEV700 | HorizSync30 - 69 | VertRefresh 50 - 110 | EndSection | | Section Device | ### Available Driver options are:- | ### Values: i: integer, f: float, bool: True/False, | ### string: String, freq: f Hz/kHz/MHz | ### [arg]: arg optional | #Option ShadowFB # [bool] | #Option VGAClocks # [bool] | Identifier Card0 | Driver vga | VendorName Intel | BoardName i810-dc100 | BusID PCI:0:1:0 | EndSection | | Section Screen | Identifier Screen0 | Device Card0 | MonitorMonitor0 | DefaultDepth 16 | SubSection Display | Depth 16 | Modes 1024x768 | EndSubSection | EndSection | | Copyright (c) 1992-2002 The FreeBSD Project. | Copyright (c) 1979, 1980, 1983, 1986, 1988, 1989, 1991, 1992, 1993, 1994 | The Regents of the University of California. All rights reserved. | FreeBSD 4.7-RELEASE #0: Wed Oct 9 15:08:34 GMT 2002 | [EMAIL PROTECTED]:/usr/obj/usr/src/sys/GENERIC | Timecounter i8254 frequency 1193182 Hz | CPU: Pentium III/Pentium III Xeon/Celeron (697.88-MHz 686-class CPU) |Origin = GenuineIntel Id = 0x686 Stepping = 6 | | Features=0x383f9ffFPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,MMX,FXSR,SSE | real memory = 267124736 (260864K bytes) | avail memory = 254693376 (248724K bytes) | Preloaded elf kernel kernel at 0xc051a000. | Preloaded elf module agp.ko at 0xc051a09c. | Pentium Pro MTRR support enabled | md0: Malloc disk | Using $PIR table, 11 entries at 0xc00f35a0 | npx0: math processor on motherboard | npx0: INT 16 interface | pcib0: Intel 82810-DC100 (i810-DC100 GMCH) Host To Hub bridge on | motherboard | pci0: PCI bus on pcib0 | agp0: Intel 82810-DC100 (i810-DC100 GMCH) SVGA controller mem
Re: X problems on i810 | AddScreen/ScreenInit failed
Continuing on from my previous posting below, I have scoured some docs to make some changes to the XF86Config: * Added Option DPMS to Monitor section (by suggestion of list member) * Added Option NoDDC to Device section (by suggestion of list member) * Changed Device section to now read as follows, from i810 man page... (in short, was using the vga driver, changed to the i810 driver.) Section Device ### Available Driver options are:- ### Values: i: integer, f: float, bool: True/False, ### string: String, freq: f Hz/kHz/MHz ### [arg]: arg optional #Option ShadowFB # [bool] #Option VGAClocks # [bool] #VideoRam16 Option NoDDC Identifier Intel i810 Driver i810 VendorName Intel BoardName i810-dc100 BusID PCI:0:1:0 EndSection The problem now is that when I run XFree86 -xf86config ./XF86Config.new, it looks like the X display is coming up but all it shows me is a 1 inch by 1 inch white square surrounded by a screen of staticy purplish, bluish, and greenish lines.. and stays. Desktop never displays. The log file shows lines like this, with the following error: drmOpenDevice: node name is /dev/dri/card0 drmOpenDevice: open result is -1, (Unknown error: 999() drmOpenDevice: Open failed drmOpenDevice: minor is 1 drmOpenDevice: node name is /dev/dri/card1 drmOpenDevice: open result is -1, (Unknown error: 999() drmOpenDevice: Open failed [...] drmOpenDevice: minor is 13 drmOpenDevice: node name is /dev/dri/card13 drmOpenDevice: open result is -1, (Unknown error: 999() drmOpenDevice: Open failed drmOpenDevice: minor is 14 drmOpenDevice: node name is /dev/dri/card14 drmOpenDevice: open result is -1, (Unknown error: 999() drmOpenDevice: Open failed drmOpenDevice: Open failed (II) I810(0): [drm] drmOpen failed (EE) I810(0): [dri] DRIScreenInit failed. Disabling DRI. Any other suggestions? DS +++ Darren Spruell [freebsd] [10-02-03 11:07 -0700]: | Date: Mon, 10 Feb 2003 11:07:22 -0700 | From: Darren Spruell [EMAIL PROTECTED] | Subject: X problems on i810 | AddScreen/ScreenInit failed | | Greetz, | | I'm trying to configure v4.7 to run X but am having a hard time getting | the server to start. | | I've followed the config instructions at | http://www.freebsd.org/doc/en_US.ISO8859-1/books/handbook/x-config.html | by doing the following steps: | | Run XFree86 -configure | to create the default XF86Config.new | Run XFree86 -xf86config ./XF86Config.new | to ensure that it works w/my hardware | Edit it to taste, to change specifics for HorizSync, VertRefresh, and | the Display subsection under Screen. | | However, running 'XFree86 -xf86config ./XF86Config.new' after changing | my config does not work. The output error is: | | == | (==) VGA(0): Write-combining range (0xa,0x1) was already clear | | Fatal server error: | AddScreen/ScreenInit failed for driver 0 | == | | I followed through the part in the Advanced Configuration section about | adding in support for agpgart and created the device node and added the | following to /boot/loader.conf: | agp_load=YES | | dmesg now shows: | Preloaded elf module agp.ko at 0xc051a09c. | agp0: Intel 82810-DC100 (i810-DC100 GMCH) SVGA controller mem | 0xffa8-0xffaf,0xf800-0xfbff irq 11 at device 1.0 on pci0 | | Here is the current XF86Config.new (non-working). The Monitor section | was taken from a specs page on the Monitor (Gateway EV700). Full dmesg | included below this: | | Section ServerLayout | Identifier XFree86 Configured | Screen 0 Screen0 0 0 | InputDeviceMouse0 CorePointer | InputDeviceKeyboard0 CoreKeyboard | EndSection | | Section Files | RgbPath /usr/X11R6/lib/X11/rgb | ModulePath /usr/X11R6/lib/modules | FontPath /usr/X11R6/lib/X11/fonts/misc/ | FontPath /usr/X11R6/lib/X11/fonts/Speedo/ | FontPath /usr/X11R6/lib/X11/fonts/Type1/ | FontPath /usr/X11R6/lib/X11/fonts/75dpi/ | FontPath /usr/X11R6/lib/X11/fonts/100dpi/ | EndSection | | Section Module | Load dbe | Load dri | Load extmod | Load glx | Load pex5 | Load record | Load xie | Load xtrap | Load speedo | Load type1 | EndSection | | Section InputDevice | Identifier Keyboard0 | Driver keyboard | EndSection | | Section InputDevice | Identifier Mouse0 | Driver mouse | Option Protocol MouseSystems | Option Device /dev/sysmouse | EndSection | | Section Monitor | Identifier Monitor0 | VendorName Gateway | ModelName
