anyone got IP Filter 3.3.8 working?
Make world has been done within the past 6 hours. When compiling a new kernel for IP Filter 3.3.8, I encounter the following warnings during the make depend: In file included from ../../netinet/fil.c:27: ../../sys/ioctl.h:46: warning: #warning "Don't #include ioctl.h in the kernel. Include xxxio.h instead." In file included from ../../netinet/ip_nat.c:37: ../../sys/ioctl.h:46: warning: #warning "Don't #include ioctl.h in the kernel. Include xxxio.h instead." In file included from ../../netinet/ip_frag.c:31: ../../sys/ioctl.h:46: warning: #warning "Don't #include ioctl.h in the kernel. Include xxxio.h instead." In file included from ../../netinet/ip_state.c:38: ../../sys/ioctl.h:46: warning: #warning "Don't #include ioctl.h in the kernel. Include xxxio.h instead." In file included from ../../netinet/ip_auth.c:26: And the following error during the make: cc -c -O -Wall -Wredundant-decls -Wnested-externs -Wstrict-prototypes -Wmissing-prototypes -Wpointer-arith -Winline -Wcast-qual -fformat- extensions -ansi -nostdinc -I- -I. -I../.. -I../../../include -D_KERNEL - include opt_global.h -elf -mpreferred-stack-boundary=2 ../../netinet/mlfk_ipl.c ../../netinet/mlfk_ipl.c:77: `ipl_inited' undeclared here (not in a function) ../../netinet/mlfk_ipl.c:77: initializer element is not constant ../../netinet/mlfk_ipl.c:77: (near initialization for `sysctl___net_inet_ipf_ipl_inited.oid_arg1') *** Error code 1 Anyone else encountered this? -- Dan Langille - DVL Software Limited [I'm looking for more work] The FreeBSD Diary - http://www.freebsddiary.org/ NZ FreeBSD User Group - http://www.nzfug.nz.freebsd.org/ The Racing System - http://www.racingsystem.com/ unix @ home - http://www.unixathome.org/ To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: anyone got IP Filter 3.3.8 working?
On Thu, Feb 03, 2000 at 09:13:54PM +1300, Dan Langille wrote: Make world has been done within the past 6 hours. When compiling a new kernel for IP Filter 3.3.8, I encounter the following warnings during the make depend: In orderd to get it to work you need to apply the patches I did when importing ipfilter. See cvs tree in sys/netinet. Anyway, I asked Jordan if I could upgrade our ipfilter to 3.3.8. In the case he approves, wait a few days. -Guido To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Can't get ISA PCnet card to work with 20000127-current
As the subject says, it's 2127-current snapshot which I tried to install on my old trusty 100Mhz 486 box. All went well except the two PCnet-ISA+ cards weren't recognized. This is an old machine with ISA and VL-bus, the cards are ISA and can be configured to PnP or legacy mode. Unfortunately even in legacy mode some kind of PnP remains so the cards attached as unknown[01]: with right resources shown at boot. I did put the lines: device lnc0 at isa? port 0x300 irq 5 drq 3 device lnc1 at isa? port 0x320 irq 10 drq 5 in the kernel config so it seems the PnP is superior opposed to hardwiring and don't let the cards attach because there are no PnP support in if_lnc it seems. Pnpinfo shows right info for the two cards and they did work in the old July 1999 -current (with pnp support disabled in the kernel). Sorry I don't have the pnpinfo output and other necessary info at the moment, will post it when I get home. Are there workarounds for this problem or am I missing something? Thanks -- Vallo Kallaste [EMAIL PROTECTED] To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: [!!!] bsd.lib.mk is broken (was: Re: UPDATING)
On Wed, 2 Feb 2000, Ruslan Ermilov wrote: Damn, you're right, except the correct patch would be (see attached). Your patch is correct. Bruce To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: Serious problems installing -CURRENT (was: UPDATING)
On Thu, 3 Feb 2000, Peter Jeremy wrote: IMHO, ntp should be configured to use POSIX extensions on the i386. P1003_1B and _KPOSIX_PRIORITY_SCHEDULING are enabled in the GENERIC i386 kernel (as of 2 weeks ago), so standard utilities should be free to use it. If the running kernel doesn't support P1003.1b, then ntpd detects it at run-time, logs the fact and works around it. The This seems to depend on the relevant P1003.1b syscalls being supported as stubs when the corresponding options are not configured. ntp is doing well if it falls back to another method after the syscalls fail. (The syscalls are kind enough to return ENOSYS without generating a SIGSYS like normal unsupported syscalls.) The presence of the stubs may also confuse autoconf. The situation might be slightly different on the Alpha since it's not clear to me whether P1003_1B is supported on the Alpha or not (it's not mentioned in Alpha GENERIC, though all the code implementing _KPOSIX_PRIORITY_SCHEDULING seems to be machine-independent). This is probably just bitrot in the alpha GENERIC. Bruce To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: 3.4-4.0 ... *almost* ...
Thus spake Glendon M. Gross ([EMAIL PROTECTED]): What does the -k switch do? --Glen Gross Read the manpage. Manpages have a very high grade of information. Alex -- I doubt, therefore I might be. To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: 3.4-4.0 ... *almost* ...
Thus spake The Hermit Hacker ([EMAIL PROTECTED]):
The old install-info didn't know this new option.
go to
/usr/src/gnu/usr.bin/texinfo/install-info
and install the new isntall-info (make clean all install)
I wasn't sure where ot find install-info, so I went to
/usr/obj/usr/src/.. and did a 'find . -name install-info -print', and it
found one:
Hello?
I said /usr/src/gnu/usr.bin/texinfo/install-info.
You'll find it THERE. That's why I said this.
And copied that in place (thinking your logic above), and that didn't
work...this was before emailing the list, which was before the reminder
about -k
If you had done this the-right-way(tm), it would have worked.
primary: [EMAIL PROTECTED] secondary: scrappy@{freebsd|postgresql}.org
How do you come to a freebsd.org address?
Alex
--
I doubt, therefore I might be.
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message
Re: [usb-bsd] patches for USB
Excellent. Keep me posted on whether the small patch works as well. In that case I will submit it. Did anyone how tested see it fall over? If not I'll commit it anyway. Nick On Thu, 3 Feb 2000, MIHIRA Sanpei Yoshiro wrote: When committing the patch to get suspend to work I managed to forget to commit the parts for pci/[ou]hci_pci.c. The patch is given below. It should make your devices suspend. I tested Nick's big-patchset. http://www.etla.net/~n_hibma/usb/USB-patch-CURRENT Without this patch, I can't re-use USB mouse after suspend/resume. With this patch, now I can use USB mouse without problem. Thank you, Nick. I hope to fix this problem before FreeBSD-4-RELEASE. May I test small patch for pci/[ou]hci_pci.c which is posted at this mailing list. Thank you. --- MIHIRA Sanpei Yoshiro Yokohama, Japan. -- [EMAIL PROTECTED] [EMAIL PROTECTED] USB project http://www.etla.net/~n_hibma/ To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
error in installworld
install -c -s -o root -g wheel -m 4555 -fschg rcp /bin /usr/libexec/ld-elf.so.1: install: Undefined symbol "string_to_flags" *** Error code 1 Stop in /usr/src/bin/rcp. *** Error code 1 .. To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Something strange with my ATAPI CD
Hi, Sometimes, i'm unable to mount my ATAPI CDROM : The light of the drive is on, i can hear the drive working, but nothing... After a while (some minutes), the light turns off, the CD is not mounted and i can't eject it anymore until a reboot :( The curious thing is that, sometimes, i can mount it... Here are the relevant messages from dmesg : =-=-=-=-=-=-=- # dmesg | grep "\bata" ata-pci0: Intel PIIX4 ATA-33 controller port 0xfcd0-0xfcdf at device 7.1 on pci0 ata0 at 0x01f0 irq 14 on ata-pci0 ata1 at 0x0170 irq 15 on ata-pci0 ata-isa0: already registered as ata0 ata-isa1: already registered as ata1 ad0: 4126MB FUJITSU MHF2043AT [8944/15/63] at ata0-master using UDMA33 acd0: CDROM TOSHIBA CD-ROM XM-1802B at ata1-master using BIOSPIO ata0: resetting devices .. done ata1: resetting devices .. done acd0: atapi_timeout: cmd=READ_BIG - resetting ata1: resetting devices .. done acd0: atapi_timeout: cmd=READ_BIG - resetting ata1: resetting devices .. done acd0: atapi_timeout: cmd=READ_BIG - resetting ata1: resetting devices .. done acd0: atapi_timeout: cmd=READ_BIG - resetting ata1: resetting devices .. done acd0: atapi_timeout: cmd=READ_BIG - resetting ata1: resetting devices .. done acd0: atapi_timeout: cmd=READ_BIG - resetting ata1: resetting devices .. done (the last messages come from the mount pb...) # ps (...) 68461 p1 D 0:00.00 cd9660 -o ro -o noauto /dev/acd0c /cdrom (mount_cd9660) (...) # mount /cdrom cd9660: Device busy # umount /cdrom umount: /cdrom: not currently mounted # grep cdrom /etc/fstab /dev/acd0c /cdrom cd9660 ro,noauto 0 0 The system is a CURRENT from yesterday, on a Dell Inspiron I3500 laptop. # grep -h '$FreeBSD' *.c * $FreeBSD: src/sys/dev/ata/ata-all.c,v 1.46 2000/01/28 20:18:19 sos Exp $ * $FreeBSD: src/sys/dev/ata/ata-disk.c,v 1.54 2000/01/27 19:00:49 sos Exp $ * $FreeBSD: src/sys/dev/ata/ata-dma.c,v 1.30 2000/01/28 15:57:13 sos Exp $ * $FreeBSD: src/sys/dev/ata/atapi-all.c,v 1.40 2000/01/29 22:38:36 sos Exp $ * $FreeBSD: src/sys/dev/ata/atapi-cd.c,v 1.39 2000/01/29 14:06:41 sos Exp $ * $FreeBSD: src/sys/dev/ata/atapi-fd.c,v 1.38 2000/01/29 14:06:41 sos Exp $ * $FreeBSD: src/sys/dev/ata/atapi-tape.c,v 1.30 2000/01/28 22:17:29 sos Exp $ -- Eric Jacoboni Ta mère, son mot de passe c'est « toto » ! To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: Something strange with my ATAPI CD
It seems Eric Jacoboni wrote: Hi, Sometimes, i'm unable to mount my ATAPI CDROM : The light of the drive is on, i can hear the drive working, but nothing... After a while (some minutes), the light turns off, the CD is not mounted and i can't eject it anymore until a reboot :( The curious thing is that, sometimes, i can mount it... Here are the relevant messages from dmesg : ata-pci0: Intel PIIX4 ATA-33 controller port 0xfcd0-0xfcdf at device 7.1 on pci0 acd0: CDROM TOSHIBA CD-ROM XM-1802B at ata1-master using BIOSPIO Hmm I have that exact same HW in my Latitude, it works very well, have you tried more that one CDROM ?? it could be a bad one -Søren To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: Error message from CAM layer
On 2 Feb, Kenneth D. Merry wrote: I'm using this hardware since 2 years now and it's the first time I see this (the computercase isn't opened for 2 months now, so nothing changed recently). Is this something I should worry about? This is likely a cabling or termination problem. It could also be that you've got your cable too close to the power supply. I thinks it's too close to the power supply (da0 terminates the bus). In any case, check your hardware. Thanks, Alexander. -- I've given up trying to change the world. I'm going to toilet train it so that I never have to change it again. http://www.Leidinger.net Alexander+Home @ Leidinger.net Key fingerprint = 7423 F3E6 3A7E B334 A9CC B10A 1F5F 130A A638 6E7E To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: 3.4-4.0 ... *almost* ...
On Wed, 02 Feb 2000 14:40:06 -0400, The Hermit Hacker wrote: === lib/libcom_err/doc install-info --quiet --defsection="Programming development tools." --defentry="* libcom_err: (com_err) If you fix this problem (by reading UPDATING) and run into another error in libcom_err, make sure you supped the src-crypto stuff as well. Using a CURRENT src-all and STABLE src-crypto will break world. Ciao, Sheldon. To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: 3.4-4.0 ... *almost* ...
On Thu, 3 Feb 2000, Alexander Langer wrote:
Thus spake The Hermit Hacker ([EMAIL PROTECTED]):
The old install-info didn't know this new option.
go to
/usr/src/gnu/usr.bin/texinfo/install-info
and install the new isntall-info (make clean all install)
I wasn't sure where ot find install-info, so I went to
/usr/obj/usr/src/.. and did a 'find . -name install-info -print', and it
found one:
Hello?
I said /usr/src/gnu/usr.bin/texinfo/install-info.
You'll find it THERE. That's why I said this.
hello ... you gave me this answer after I had already fixed the problem
Marc G. Fournier ICQ#7615664 IRC Nick: Scrappy
Systems Administrator @ hub.org
primary: [EMAIL PROTECTED] secondary: scrappy@{freebsd|postgresql}.org
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message
flaw in modules system?
Morning all ...
Just recently, I upgraded from 3.4 to 4.0, and the process, all in
all, was relatively painless. I got hit by the 'lack of memory' on my
part about the 'make -k' option mostly ...
... but, one thing did hit me that I think could be fixed is the
modules. I forgot that I was using the procfs module, so, of course, when
I rebooted, it crashed because it was still using the old 3.4 one.
I'm about to upgrade my bosses computer, and looked through
modules and there is an if_xl.ko module ... right now, I have xl compiled
in by default, but getting that out of the kernel (and as much else) out
of the kernel config would be nice ... but, of course, were I to do that
now, the ethernet would be down, which means I couldn't get at the nfs
mounted /usr/{src,obj} directory to install the module ...
When we do a 'make install' on the kernel, it automatically copies
/kernel to /kernel.old, and copies the new kernel in ... is there no way
of extending this to the modules?
The one thing I was thinking might be to have it so that if you
'load kernel.old' (ie. kernel didn't boot properly, so you have to
revert), when it loads its modules, it loads module.old to go along with
it...
Basically, the modules are tied to the kernel, so is there any way
of having them install along with the kernel ... ?
Thanks...
Marc G. Fournier ICQ#7615664 IRC Nick: Scrappy
Systems Administrator @ hub.org
primary: [EMAIL PROTECTED] secondary: scrappy@{freebsd|postgresql}.org
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message
Re: [usb-bsd] Re: patches for USB
Keep me posted on whether the small patch works as well. In that case I will submit it. I tested Nick's USB suspend/resume *small* patch with latest-current. It's OK for my USB mouse. Thank you. MIHIRA Yoshiro To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
subscribe
subscribe -- This Mail has been checked for Viruses Attention: Encrypted Mails can NOT be checked ! * * * Diese Mail wurde auf Viren ueberprueft Hinweis: Verschluesselte Mails koennen NICHT geprueft werden ! -- To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: 3.4-4.0 ... *almost* ...
Thus spake Glendon M. Gross ([EMAIL PROTECTED]): What does the -k switch do? --Glen Gross This really could have been answered with a little RTFM. And if you are running -CURRENT you should be able to do that for simple things. Try this: man make / -k and you would have seen: -k Continue processing after errors are encountered, but only on those targets that do not depend on the target whose creation caused the error. BSD goes to a lot of trouble to have readable and truely useful manpages. One should consult them. To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
(no subject)
subscribe freebsd-current subscribe cvs-all To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
GNATS reply?
Hello, Shouldn't I get a response email from [EMAIL PROTECTED]? Or is this a casualty of the mail breakage? Would I be better of using the web form, or just waiting until after Linuxworld? Thanks, ==ml To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: error in installworld
this has been covered already, but basically: cd /usr/src/usr.bin/xinstall make install cd /usr/src make installworld On Thu, 3 Feb 2000, Charlie Root wrote: install -c -s -o root -g wheel -m 4555 -fschg rcp /bin /usr/libexec/ld-elf.so.1: install: Undefined symbol "string_to_flags" *** Error code 1 Stop in /usr/src/bin/rcp. *** Error code 1 .. To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message +-/ f. johan beisser /--+ email: jan[at]caustic.org web: http://www.caustic.org/~jan "knowledge is power. power corrupts. study hard, be evil." To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
libcrypto (DES - MD5)
Long time ago I used the crypto code on cvsup.internat.freebsd.org and all was nice. Now I need to use crypto from internat to be able to use OpenSSH. I have to have openssl in my base system otherwise I cannot use the port. So, on my -current box I cvsup both todays -current source and the crypto source from cvsup.internat.freebsd.org and continues with a 'make world'. make world finishes just fine and I recompile a new kernel. reboots and installs openssh port. Everything seems just fine and dandy. I add a new user, and with 'vipw' I notices that this user now gets a DES based passwd. (we only use MD5 passwords around). Then I looked in /usr/lib and noticed that libcrypt now is symlinked to libdescrypt: lrwxr-xr-x 1 root wheel 13 Feb 3 08:20 libcrypt.a@ - libdescrypt.a lrwxr-xr-x 1 root wheel 14 Feb 3 08:20 libcrypt.so@ - libdescrypt.so lrwxr-xr-x 1 root wheel 16 Feb 3 08:20 libcrypt.so.2@ - libdescrypt.so.2 This is not what I had expected, earlier FreeBSD version did not change my symlinks in /usr/lib with a make world or installworld, whatever... Of course I can change the symlinks and re-hash the passwd and be happy, but I think that this is _wrong_. The 'installworld' target should not IMHO change the libcrypto symlinks. I want to use MD5 passwords, but I also need to have the crypto source collection installed to use OpenSSH and such. Could this behaviour be turned back to what its used to be? It used to be myself that had to change the symlinks if I wanted to switch to DES passwd. -- Anders Andersson[EMAIL PROTECTED] Sanyusan International AB http://www.sanyusan.se/ To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: Something strange with my ATAPI CD
Soren Schmidt [EMAIL PROTECTED] writes: Hmm I have that exact same HW in my Latitude, it works very well, have you tried more that one CDROM ?? it could be a bad one I'm gonna test for that with some others CDs, but i've succeeded to mount _this_ CD just after my mail and a a reboot... -- - Éric Jacoboni « No sport, cigars! » (W. Churchill) - To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: Can't get ISA PCnet card to work with 20000127-current
Get me a copy of your boot output and the output of 'pnpinfo'. On Thu, 3 Feb 2000, Vallo Kallaste wrote: As the subject says, it's 2127-current snapshot which I tried to install on my old trusty 100Mhz 486 box. All went well except the two PCnet-ISA+ cards weren't recognized. This is an old machine with ISA and VL-bus, the cards are ISA and can be configured to PnP or legacy mode. Unfortunately even in legacy mode some kind of PnP remains so the cards attached as unknown[01]: with right resources shown at boot. I did put the lines: device lnc0 at isa? port 0x300 irq 5 drq 3 device lnc1 at isa? port 0x320 irq 10 drq 5 in the kernel config so it seems the PnP is superior opposed to hardwiring and don't let the cards attach because there are no PnP support in if_lnc it seems. Pnpinfo shows right info for the two cards and they did work in the old July 1999 -current (with pnp support disabled in the kernel). Sorry I don't have the pnpinfo output and other necessary info at the moment, will post it when I get home. Are there workarounds for this problem or am I missing something? Thanks -- | Matthew N. Dodd | '78 Datsun 280Z | '75 Volvo 164E | FreeBSD/NetBSD | | [EMAIL PROTECTED] | 2 x '84 Volvo 245DL| ix86,sparc,pmax | | http://www.jurai.net/~winter | This Space For Rent | ISO8802.5 4ever | To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: flaw in modules system?
On Thu, 03 Feb 2000, you wrote: When we do a 'make install' on the kernel, it automatically copies /kernel to /kernel.old, and copies the new kernel in ... is there no way of extending this to the modules? The one thing I was thinking might be to have it so that if you 'load kernel.old' (ie. kernel didn't boot properly, so you have to revert), when it loads its modules, it loads module.old to go along with it... Basically, the modules are tied to the kernel, so is there any way of having them install along with the kernel ... ? Peter W. was working on this but it wasn't going to be ready in time for the 4.0 freeze. Therefore it got put "on hold" until 4.0 gets released. Expect it soon thereafter. To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: libcrypto (DES - MD5)
On Thu, 3 Feb 2000, Anders Andersson wrote: I add a new user, and with 'vipw' I notices that this user now gets a DES based passwd. (we only use MD5 passwords around). Then I looked in /usr/lib and noticed that libcrypt now is symlinked to libdescrypt: AFAIK this has always been the way it works: if you install libdescrypt, the system makes the (mistaken) assumption you want DES passwords all the time. For now, just repoint the symlinks and edit out the build of secure/lib/libcrypt - a proper fix might be to add a login class which determines which of MD5 and DES you should use for new passwords, but I won't be able to get that committed until after 4.0. Kris "How many roads must a man walk down, before you call him a man?" "Eight!" "That was a rhetorical question!" "Oh..then, seven!" -- Homer Simpson To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Will the real libcrypto please stand up?
I'm a bit confused about the libcrypto situation and need some clarification :) I'm running -current and rebuilt the apache13-php3 port recently. The port depends on /usr/local/lib/libcrypto.so.1, however when starting the ssl version I get the following: ikhala.tcimet.net:root apachectl startssl Syntax error on line 240 of /usr/local/etc/apache/apache.conf: Cannot load /usr/local/libexec/apache/libssl.so into server: /usr/lib/libcrypto.so.1: Undefined symbol "ERR_load_RSAREF_strings" /usr/local/sbin/apachectl startssl: httpd could not be started My question is simply what is the "correct" fix so all apps needing libcrypto will find the one it needs? Should there be only one? I know I'm missing something simple. Thanxs #;^) -- So ya want ta hear da roots? bush doctor [EMAIL PROTECTED] Of course I run FreeBSD!! http://www.freebsd.org/ To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: Will the real libcrypto please stand up?
At 02:20 PM 2/3/00 -0500, bush doctor wrote: I'm a bit confused about the libcrypto situation and need some clarification :) I'm running -current and rebuilt the apache13-php3 port recently. The port depends on /usr/local/lib/libcrypto.so.1, however when starting the ssl version I get the following: ikhala.tcimet.net:root apachectl startssl Syntax error on line 240 of /usr/local/etc/apache/apache.conf: Cannot load /usr/local/libexec/apache/libssl.so into server: /usr/lib/libcrypto.so.1: Undefined symbol "ERR_load_RSAREF_strings" /usr/local/sbin/apachectl startssl: httpd could not be started My question is simply what is the "correct" fix so all apps needing libcrypto will find the one it needs? Should there be only one? I know I'm missing something simple. Thanxs I had to add -L/usr/local/lib -lrsaref -lRSAglue to the SSL_LIBS= line of /usr/ports/www/apache13-php3/work/apache_1.3.11/src/modules/ssl/Makefile then it works fine. Manfred = ||[EMAIL PROTECTED] || ||Ph. (415) 681-6235|| = To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: IP-Filter w/FreeBSD-current
Guido van Rooij wrote: If you do not reload the filter rules, but look at what ipfstat says about rule hits, you might get a clue on where things are blocked (if at all). I did that, see below. I think what happens is that the tun0 device is loaded as kld when you first run ppp. And in fact that the initial ipf loading gives errors No, during my tests kldstat output is: Id Refs AddressSize Name 13 0xc010 1b64b0 kernel 21 0xc09ef000 1linux.ko 31 0xc0a11000 3000 daemon_saver.ko In my kernel config I have: pseudo-device tun # Packet tunnel. about the fact that there is no such device as tun0. Reloading the filter rules fixes that and since tun0 is loaded and stays loaded, you'll never encounter any problems again. Try kldload if_tun before loading the rules at boot time and sees if the problem goes away. If this doesn't solve it, walk over to my room tomorrow and we'll look further. I repeated the test I described a few days ago, but this time I also looked at the kldstat output (remains the same during the whole test) and ipfstat -hi/-ho. 1. Fresh reboot; start dialin to company; try to ping a host on the company network, it says no route to host. ipfstat -hi/-ho output does not show any tun0 activity: 0 pass in quick on tun0 from any to any 0 pass out quick on tun0 from any to any 2. Type the ipf.reload command which unloads and reloads the same filter rules (see previous mail). Ping the host again, this works. ipfstat -hi/-ho now shows activity on the tun0 device: 5 pass in quick on tun0 from any to any 15 pass out quick on tun0 from any to any 3. Shut down the dialin connection. 4. Start new dialin connection, this one works without any further actions. 5. Goto 3. Arjan -- Arjan de Vet, Eindhoven, The Netherlands [EMAIL PROTECTED] URL: http://www.iae.nl/users/devet/ for PGP key: finger [EMAIL PROTECTED] To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: IP-Filter w/FreeBSD-current
On Thu, Feb 03, 2000 at 09:09:40PM +0100, Arjan de Vet wrote: In my kernel config I have: pseudo-device tun # Packet tunnel. Ah..this is a self cloning device. Before loading the filter rules, you must make sure the device is there. Do something like: dd if=/dev/tun0 count=0 or something else that opens a device and closes it again without reading. There is a bug in ipfilter: it does not return an error when loading a rule with a non-existing device (though it will work as expected in that it will never match) -Guido To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: libcrypto (DES - MD5)
In article [EMAIL PROTECTED], Kris Kennaway [EMAIL PROTECTED] wrote: On Thu, 3 Feb 2000, Anders Andersson wrote: I add a new user, and with 'vipw' I notices that this user now gets a DES based passwd. (we only use MD5 passwords around). Then I looked in /usr/lib and noticed that libcrypt now is symlinked to libdescrypt: AFAIK this has always been the way it works: if you install libdescrypt, the system makes the (mistaken) assumption you want DES passwords all the time. I agree. It has been that way as long as I can remember (since around 2.0.5-RELEASE). John To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: IP-Filter w/FreeBSD-current
Guido van Rooij wrote: pseudo-device tun # Packet tunnel. Ah..this is a self cloning device. Before loading the filter rules, you must make sure the device is there. Do something like: dd if=/dev/tun0 count=0 or something else that opens a device and closes it again without reading. OK, this solves the problem. Thanks! Arjan -- Arjan de Vet, Eindhoven, The Netherlands [EMAIL PROTECTED] URL: http://www.iae.nl/users/devet/ for PGP key: finger [EMAIL PROTECTED] To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: GNATS reply?
In article [EMAIL PROTECTED], Michael Lucas [EMAIL PROTECTED] wrote: Hello, Shouldn't I get a response email from [EMAIL PROTECTED]? Or is this a casualty of the mail breakage? It is a casualty of the mailserver HW problem. Would I be better of using the web form, or just waiting until after Linuxworld? My advice is to wait. John To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: UPDATING
If memory serves me right, Ruslan Ermilov wrote: On Wed, Feb 02, 2000 at 10:53:49AM -0500, Jim Bloom wrote: Ruslan Ermilov wrote: On Tue, Feb 01, 2000 at 02:51:11PM -0500, Jim Bloom wrote: I did the following and it worked for me: cd /usr/src make buildworld make installworld cd /usr/src/usr.bin/xinstall make install cd /usr/src make installworld The first make installworld terminates with an errors, but the second o n goes through. It can't be true! Nope, I'm pretty sure that is exactly what I did. After the first `make installworld' fails, we will have: 1) a new `libutil' without string_to_flags() 2) an old `libc' without setflags() 3) an old /usr/bin/install with string_to_flags() linked against libutil. I believe the new libc has been installed as well. My first installworld got an error while trying to install rcp. I believe this is the first program that uses any flags to install. Once you get to this point, all of the libraries have been installed. Yeah, just figured this myself, but one thing I still don't understand is how the new libc.so.4 gets installed on the first pass? The problem is that it is declared as PRECIOUSLIB in libc/Makefile, this will result in -fschg passed to install. Do you have a log from the first failed installworld? This is my first attempt at building world (starting from the 2127 snapshot, then cvsup-ing src-all and cvs-crypto this morning, California time), but I had a slightly different experience. make buildworld completed without errors, then I did a make installworld which failed (no setflags) when trying to install libcrypto. I did a make -k installworld, which of course finished, but the make installworld I did afterwards (no -k) failed in the same place. After having read through the last few messages on -current, I went to the source directory for libc and tried doing a make install there. It failed (also because of a lack of setflags). Then I went to the obj directory for libc and executed the install command for libc manually (but without the -fschg argument): install -c -o root -g wheel -m 444 libc.so.4 /usr/lib A make installworld just finished without errors. Hopefully this is useful information, and won't add to any of the confusion. Bruce. (who's now wishing he kept slightly better written records of what he's doing) PGP signature
Re: Serious problems installing -CURRENT (was: UPDATING)
On 2000-Feb-03 20:11:57 +1100, Bruce Evans [EMAIL PROTECTED] wrote: ntp is doing well if it falls back to another method after the syscalls fail. ntpd iterates (at runtime) through all the possible scheduling mechanisms that were enabled at compile time, until one works. These are (in order) SetPriorityClass() (LoseNT only), sched_setscheduler(), rtprio(), nice(), setpriority(). If all these fail, it will log a message that it couldn't improve it's priority - in which case it will still function, but probably won't be as accurate. (ntpd is probably a special case, in that the P1003.1b functions aren't essential to it, they just improve its operation). (The syscalls are kind enough to return ENOSYS without generating a SIGSYS like normal unsupported syscalls.) /sys/posix4/p1003_1b.c uses syscall_not_present() as a stub routine, this includes the comment 'a " return nosys(p, uap); " here causes a core dump.' and returns ENOSYS. I'm not sure who wrote this comment. Peter To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: Will the real libcrypto please stand up?
Out of da blue Manfred Antar aka ([EMAIL PROTECTED]) said: At 02:20 PM 2/3/00 -0500, bush doctor wrote: I'm a bit confused about the libcrypto situation and need some clarification :) I'm running -current and rebuilt the apache13-php3 port recently. The port depends on /usr/local/lib/libcrypto.so.1, however when starting the ssl version I get the following: ikhala.tcimet.net:root apachectl startssl Syntax error on line 240 of /usr/local/etc/apache/apache.conf: Cannot load /usr/local/libexec/apache/libssl.so into server: /usr/lib/libcrypto.so.1: Undefined symbol "ERR_load_RSAREF_strings" /usr/local/sbin/apachectl startssl: httpd could not be started My question is simply what is the "correct" fix so all apps needing libcrypto will find the one it needs? Should there be only one? I know I'm missing something simple. Thanxs I had to add -L/usr/local/lib -lrsaref -lRSAglue to the SSL_LIBS= line of /usr/ports/www/apache13-php3/work/apache_1.3.11/src/modules/ssl/Makefile then it works fine. Thanxs Manfred. That did the trick. I removed the crypto port. ( I remembered seeing the posts about that, but looks like I got caught napping :) Have you sent a send-pr for this? If not I can wrap one around your fix. Thanxs again ... Manfred = ||[EMAIL PROTECTED] || ||Ph. (415) 681-6235|| = #;^) -- So ya want ta hear da roots? bush doctor [EMAIL PROTECTED] Of course I run FreeBSD!! http://www.freebsd.org/ To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: Will the real libcrypto please stand up?
On Thu, 3 Feb 2000, bush doctor wrote: I'm a bit confused about the libcrypto situation and need some clarification :) I'm running -current and rebuilt the apache13-php3 port recently. The port depends on /usr/local/lib/libcrypto.so.1, however when starting the ssl version I get the following: Jim Bloom and I are in the process of preparing patches for all of the openssl-using ports. See http://www.freebsd.org/~kris/openssl for some of them, although I haven't added the latest ones Jim has sent me. I don't think the apache13-php3 has been fixed yet. I've had very minimal feedback about these, and none from our Ports Wraith (the change to bsd.port.mk really needs to go into the ports tree asap so we can start fixing them), but I hope to get them all fixed by the ports freeze on the 14th. Kris "How many roads must a man walk down, before you call him a man?" "Eight!" "That was a rhetorical question!" "Oh..then, seven!" -- Homer Simpson To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: Serious problems installing -CURRENT (was: UPDATING)
In message [EMAIL PROTECTED], Peter Jeremy writes: On 2000-Feb-03 20:11:57 +1100, Bruce Evans [EMAIL PROTECTED] wrote: ntp is doing well if it falls back to another method after the syscalls fail. ntpd iterates (at runtime) through all the possible scheduling mechanisms that were enabled at compile time, until one works. These are (in order) SetPriorityClass() (LoseNT only), sched_setscheduler(), rtprio(), nice(), setpriority(). If all these fail, it will log a message that it couldn't improve it's priority - in which case it will still function, but probably won't be as accurate. (ntpd is probably a special case, in that the P1003.1b functions aren't essential to it, they just improve its operation). Actually none of this seems to have much effect on it's performance since we timestamp packets in the kernel on input and the chances of being preempted between constructing the output packet and sending it is epsilon. -- Poul-Henning Kamp FreeBSD coreteam member [EMAIL PROTECTED] "Real hackers run -current on their laptop." FreeBSD -- It will take a long time before progress goes too far! To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
strange buildworld problem (not xinstal related)
Hello,
I am experiencing a (to me) strange error while trying to
buildworld. Sources are current as of about noon today, and this has been
happening for the past few days.
cc -O -pipe -I/usr/src/gnu/lib/libobjc/../../../contrib/gcc/objc
-I/usr/src/gnu/lib/libobjc/../../../contrib/gcc
-I/usr/obj/usr/src/i386/usr/include -Wno-import -pg -c
/usr/src/gnu/lib/libobjc/../../../contrib/gcc/objc/Object.m -o Object.po
{standard input}: Assembler messages:
{standard input}:808: Error: no such 386 instruction: `state'
{standard input}:1568: Fatal error: Symbol yydebug already defined.
*** Error code 1
Stop in /usr/src/gnu/lib/libobjc.
*** Error code 1
I have build and installed world before on this machine, both -stable and
-current branches. The only thing that has changed recently is I have a
new motherboard (shouldn't make a difference?). Machine is AMD K6-2 based.
I'm not sure what's going on, I haven't seen anyone else complain about
this so it's probably something wrong with my installation, but I thought
I would relay it anyway.
-Will
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message
Unknown PCI card
Are there any plans for the Initio INI-A100U2W PCI SCSI controller cards?
You can get driver source code for FreeBSD from http://www.initio.com/
--
:{ [EMAIL PROTECTED]
Andy Farkas
System Administrator
Speednet Communications
http://www.speednet.com.au/
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message
Re: Unknown PCI card
On Fri, Feb 04, 2000 at 17:17:20 +1100, Andy Farkas wrote: Are there any plans for the Initio INI-A100U2W PCI SCSI controller cards? You can get driver source code for FreeBSD from http://www.initio.com/ I would suggest looking at the list archives, but I don't think they're available at the moment. :) Anyway, Thomas Graichen [EMAIL PROTECTED] is working on getting the drivers integrated into FreeBSD. He sent this URL with his last piece of mail about the Initio controllers: http://www.innominate.org/~tgr/projects/FreeBSD/iha Anyway, if you've got questions about the status of the drivers, etc., contact Thomas. Ken -- Kenneth Merry [EMAIL PROTECTED] To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: error in installworld
sorry guys... I already fix this... sorry. And also I'm new in CURRENT. Now I subscribe to 'freebsd-current' mailing list... and I hope I never ask you so dummy questions. Thanks you all for your answers!!! sorry! krisOn Thu, 3 Feb 2000, Charlie Root wrote: kris kris install -c -s -o root -g wheel -m 4555 -fschg rcp /bin kris /usr/libexec/ld-elf.so.1: install: Undefined symbol "string_to_flags" kris *** Error code 1 kris Stop in /usr/src/bin/rcp. kris *** Error code 1 kris .. kris krisOkay, you're a bad boy. Not because you got the error, but because you krisdidn't read the other dozen or more messages which also talk about this krisproblem and how to fix it. And you didn't read /usr/src/UPDATING, now, did krisyou? You're really expected to do both of these things if you run kris-current. kris krisKris Regards, Listopad Alexandr ([EMAIL PROTECTED]), LAA7-RIPE ZGIA, Zaporozhye, Ukraine. http://www.zgia.zp.ua. To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
libipsec shlib version change
Hello, Yesterday I changed libipsec version number from 2 to 0. Because when it is created at Feb 3, no SHLIB number is clearly specified, and number 2 seemed to be selected by default, but it should start from 0. The contents of libipsec.so.0 and libipsec.so.2 is exactly same, so there should be no problem for now. But for safety, and to avoid confusion, I recommend you to do following. -Reinstall src/lib/libipsec -Re-build apps which use libipsec. I think they are, src/sbin/ping usr.bin/telnet usr.sbin/inetd usr.sbin/rrenumd usr.sbin/traceroute6 usr.sbin/setkey usr.sbin/rtadvd secure/usr.bin/telnet (If you are using this) kerberosIV/usr.bin/telnet (If you are using this) Or full make world will be enough instead. -Then remove /usr/lib/libipsec.so.2 Sorry for your extra work. Yoshinobu Inoue To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: Suggestions for Gigabit cards for -CURRENT
Of all the gin joints in all the towns in all the world, Kenneth D. Merry had to walk into mine and say: On Wed, Feb 02, 2000 at 13:03:09 -0500, Thomas Stromberg wrote: We're currently looking at upgrading several of our FreeBSD servers (dual PIII-600's, 66MHz PCI) and some Sun Ultra's to Gigabit Ethernet. We plan to hook these machines into our Cisco Catalyst 5000 server. They will most likely move to be running FreeBSD 4.x by the time that we actually get our budget approved. What experiences do you guys have with the cards? Currently we're looking at the ~$1000 range, specifically at Alteon 512k's ($1000) for the FreeBSD servers and Sun Gigabit 2.0's ($2000) for the Sun servers. I was interested in the Myrinet cards (for obvious reasons), but they appear to require a Myrinet switch (though I found myself slightly confused so I may be wrong) rather then being able to hook into our Catalyst 5000. The Intel PRO/1000 Gigabit cards look rather nice too, but I haven't seen drivers yet for FreeBSD (Linux yes). I'm pretty much purchasing on marketing and reputation rather then any experience here, so any help would be much appreciated. I would recommend getting Alteon boards. It is likely that the Sun boards are Alteon OEM, although I'm not positive. I think the first gigabit cards Sun had on the market were OEMed from Alteon, but I've been told that their newer cards are something else entirely. I don't know exactly what, but they're not Tigon-based. One thing to keep in mind is that both Netgear and 3Com are OEMing Alteon boards, and you'll get them much cheaper that way. The boards are pretty much identical to the Alteon branded boards (which have no identifying marks on them). The performance is the same, at least for the Netgear boards. (I don't have any 3Com boards.) There are a number of companies selling OEM'ed alteon boards for various prices. IBM sells two cards, one for PC-based hardware and one for RS/6000s which I think are basically the same hardware with different driver kits. Of course, the RS/6000 card is $2100 while the PC-based one is probably around $600 or so. My guess is they're Alteon cards with different PCI device IDs, but I can't confirm this as I don't have one. The SGI gigabit adapter, NEC gigabit adapter, DEC EtherWORKS/1000, 3Com 3c985 and 3c985B, and the Netgear GA620 are all Tigon boards (not to mention the Alteon ACEnic) and should all work fine with the ti driver. Oh, I found another one recently: Farallon also sells a gigabit PCI NIC for the Mac which is Tigon-based. The Netgear GA620 is a 512K Tigon 2 board, and generally goes for around $300 or so. The 3Com boards have 1MB of SRAM, but I'm not sure whether they're Tigon 1 or Tigon 2. You really want a Tigon 2 board. Maybe someone who has one can comment. The original 3Com 3c985 was a Tigon 1 board (I have one) and the 3c985B is a Tigon 2. The Tigon 1 is no longer in production, though of course I try to maintain support for it for those people who still have them. The Tigon 1 had only a single R4000 CPU in it while the Tigon 2 has two. The Netgear GA620 is by far the cheapest at about $320. The various OEM cards sold for the PC are usually around $600, give or take $100. The GA620 only has 512K of SRAM compared to 1MB on most of the others, however you're not likely to notice a problem with that unless you try to push the card really hard with a really big TCP window size and jumbo frames. The Intel cards may look nice, and there is a FreeBSD driver for them, but I wouldn't get one. The first problem with the Intel boards is that there are no docs for them. Supposedly they're using a Cisco chip, and the specs for the chip are top secret. This is why I don't buy or recommend Intel NICs. But that's just my personal bias. The FreeBSD driver (written by Matt Jacob) is based on the Linux driver, which Intel wrote, and he hasn't yet managed to get decent throughput through the cards. (Maybe Matt will comment.) They also only have 64K of memory on board, which is insufficient for a heavily loaded server, IMO. Even with the 512K Alteon boards, you have a minimum of about 200K, and probably more like 300K of cache for transmit and receive. The Alteon cards also need a certain amount of SRAM to run the firmware. The Intel boards also don't have the features necessary to really support zero copy TCP receive. The Alteon boards, on the other hand, have most of the features necessary, and if I get some time, I may add the last feature (header splitting) to the firmware. The other alternative is SysKonnect, and that might actually be a good alternative. I haven't seen the boards, don't know how much they cost, etc. etc. You might want to ask Bill Paul about them, he wrote the driver. The SysKonnect cards aren't bad. A single port multimode fiber card is around $700, I think. The single mode cards are more expensive. However
Re: Suggestions for Gigabit cards for -CURRENT
[ Thanks for the info Bill! ] On Thu, Feb 03, 2000 at 21:29:27 -0500, Bill Paul wrote: Of all the gin joints in all the towns in all the world, Kenneth D. Merry had to walk into mine and say: The Netgear GA620 is a 512K Tigon 2 board, and generally goes for around $300 or so. The 3Com boards have 1MB of SRAM, but I'm not sure whether they're Tigon 1 or Tigon 2. You really want a Tigon 2 board. Maybe someone who has one can comment. The original 3Com 3c985 was a Tigon 1 board (I have one) and the 3c985B is a Tigon 2. The Tigon 1 is no longer in production, though of course I try to maintain support for it for those people who still have them. The Tigon 1 had only a single R4000 CPU in it while the Tigon 2 has two. Ahh, that's good to know, I was wondering whether they had a Tigon 2 board out, since it would make a cheaper alternative to the 1MB ACEnic. The Netgear GA620 is by far the cheapest at about $320. The various OEM cards sold for the PC are usually around $600, give or take $100. The GA620 only has 512K of SRAM compared to 1MB on most of the others, however you're not likely to notice a problem with that unless you try to push the card really hard with a really big TCP window size and jumbo frames. That has been my experience as well. The FreeBSD driver (written by Matt Jacob) is based on the Linux driver, which Intel wrote, and he hasn't yet managed to get decent throughput through the cards. (Maybe Matt will comment.) They also only have 64K of memory on board, which is insufficient for a heavily loaded server, IMO. Even with the 512K Alteon boards, you have a minimum of about 200K, and probably more like 300K of cache for transmit and receive. The Alteon cards also need a certain amount of SRAM to run the firmware. Yep, thus the 200K-300K number. The minimum amount of buffer that the board will configure is 64K for transmit buffers and 128K for receive buffers. It looks at the size of the firmware and associated data structures, and allocates the rest of the card memory for transmit and receive buffer space. Both the Alteon and SysKonnect NICs are 64-bit PCI cards. (Actually, I'm pretty sure all of the PCI gigabit NICs are 64-bit.) Both kinds of cards can do jumbograms on FreeBSD. Also, both vendors have released pretty good hardware documentation, which makes them good choices for custom applications, if you're into that sort of thing. Alteon also provides firmware source, which can really come in handy. Do you know if SysKonnect has released firmware? Ken -- Kenneth Merry [EMAIL PROTECTED] To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: Suggestions for Gigabit cards for -CURRENT
Of all the gin joints in all the towns in all the world, Kenneth D. Merry had to walk into mine and say: [ Thanks for the info Bill! ] No problemo. [...] Both the Alteon and SysKonnect NICs are 64-bit PCI cards. (Actually, I'm pretty sure all of the PCI gigabit NICs are 64-bit.) Both kinds of cards can do jumbograms on FreeBSD. Also, both vendors have released pretty good hardware documentation, which makes them good choices for custom applications, if you're into that sort of thing. Alteon also provides firmware source, which can really come in handy. Do you know if SysKonnect has released firmware? The SysKonnect GEnesis controller and the XaQti XMAC II chips are both static devices and do not require firmware. If you go to www.syskonnect.com and search their online knowledge base for the word "manual" you should be able to find the gigabit NIC programmer's manual. Similarly, XaQti has the full datasheet for the XMAC II at www.xaqti.com somewhere. (As I recall, you have to go through a brief registration procedure to get it, but once that's done you should be able to download it right away.) Talking of the XMAC II, there's one other thing I forgot to mention earlier. The FreeBSD sk driver does jumbo frames, but the SysKonnect drivers don't. At least, not yet. The XMAC II's receive FIFO is 8K. By default, the chip operates in 'store and forward' mode in order to perform error checking on received frames (it has to get the entire frame in the FIFO in order to do a CRC on it, I think). This is fine for normal frames, but if you want to handle jumbograms larger than 8192 bytes, you have to put the chip into 'streaming' mode, otherwise any frame larger than 8192 bytes will be truncated. To get 'streaming' mode to work, you have to disable all of the RX error checking. Also, the default TX FIFO threshold on the XMAC is very small (8 bytes, I think). The FreeBSD sk driver bumps this up a bit (to 512 bytes, if I remember correctly). This is to deal with the case where you have a dual port card and are pumping data through both XMAC chips at once: with the default FIFO threshold, I would often see TX FIFO underruns from one of the XMACs and performance on that port would get spotty. I think the total TX FIFO memory on the XMAC II is 2K. -Bill -- = -Bill Paul(212) 854-6020 | System Manager, Master of Unix-Fu Work: [EMAIL PROTECTED] | Center for Telecommunications Research Home: [EMAIL PROTECTED] | Columbia University, New York City = "It is not I who am crazy; it is I who am mad!" - Ren Hoek, "Space Madness" = To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: Suggestions for Gigabit cards for -CURRENT
On Thu, Feb 03, 2000 at 23:09:46 -0500, Bill Paul wrote: Of all the gin joints in all the towns in all the world, Kenneth D. Merry had to walk into mine and say: Alteon also provides firmware source, which can really come in handy. Do you know if SysKonnect has released firmware? The SysKonnect GEnesis controller and the XaQti XMAC II chips are both static devices and do not require firmware. If you go to www.syskonnect.com and search their online knowledge base for the word "manual" you should be able to find the gigabit NIC programmer's manual. Similarly, XaQti has the full datasheet for the XMAC II at www.xaqti.com somewhere. (As I recall, you have to go through a brief registration procedure to get it, but once that's done you should be able to download it right away.) Well, all-hardware designs can be great when they're done right, and irritating when they're not. Thanks for the manual pointers. I've got the SysKonnect manual, and it seems pretty nifty. Talking of the XMAC II, there's one other thing I forgot to mention earlier. The FreeBSD sk driver does jumbo frames, but the SysKonnect drivers don't. At least, not yet. The XMAC II's receive FIFO is 8K. By default, the chip operates in 'store and forward' mode in order to perform error checking on received frames (it has to get the entire frame in the FIFO in order to do a CRC on it, I think). This is fine for normal frames, but if you want to handle jumbograms larger than 8192 bytes, you have to put the chip into 'streaming' mode, otherwise any frame larger than 8192 bytes will be truncated. To get 'streaming' mode to work, you have to disable all of the RX error checking. That is unfortunate, since it means you can't do checksum offloading with jumbo frames. FWIW, of the three gigabit ethernet implementations I've seen anything of (Alteon, Intel, SysKonnect), none have implemented all of the hooks necessary for a seamless zero copy receive implementation. Alteon comes the closest, but they don't support splitting out the headers (yet), which is a requirement for us. The only way to do zero copy receive with our VM architecture (that I know of) is page flipping, i.e. receive the page in the kernel, and then trade it for the user's page. You can't do it on anything less than page-sized granularity, and things have to be page aligned. (The IO-Lite stuff from Rice is an exception to all this.) The nice thing about the Alteon boards, though, is that you can modify the firmware, and so header splitting is an option there. It would even be possible to split the headers off of IPv6 packets, or any other protocol that you have knowlege of. Ken -- Kenneth Merry [EMAIL PROTECTED] To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
bug in vn, a pnaic and how to debug modules (was Re: open ref counts in CAM and vn)
On Thu, Feb 03, 2000 at 10:05:22AM -0700, Kenneth D. Merry wrote: The reference counting should be handled by PHK's disk layer (which sits above CAM), and the da driver's close routine should only get called on final close. ok. I don't know about the vn device, though. That was the reason fro the posting. vnconfig -u goes directly to the vn device but that device has no track of open count. I don't see any code to notify the upper layer that the device is gove. That is wrong of course. In fact, one can vnconfig -u a device, while the device is used in a mount. The ufs layer doesn't even know that the device is gone and accessing the mount is still possible. Unmounting is not. So in this case, I guess vnconfig -u should fail. I think this is best achieved by using a ref counter in the vn device code. There is another bug in the vn code as well, which has tom do with modules. The following will panic on a page fault in vnsetcred (in the VOP_UNLOCK call): kldload vn vnconfig -c something vnconfig -u something kldunload vn kldload vn vnconfig -c something --- instant panic I have not been able to debug this further, because it seems (but I have to recheck to be sure), that add-symbol-file /modules/vn correct address does not allow one to look at variables delcared inside the vn module. Is there an easy way btw to determine address? I looked inside the debugger in the linker_files queue and then use the load address there, plus the start address of .text as found by objdump of the vn module. -Guido To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
