oddness in -current
I was just watching a buildworld happen when I noticed (specifically in gcc, and a few other places) the following warning several times: warning: mktemp() possibly used unsafely; consider using mkstemp() I'm not sure if it's a big deal or not, but in the interests of satisfying my own interests, I thought I would mention it. If this has been covered already in this list, then please disregard. Next time I'll capture the entire build process to a file. To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
openssh question
Actually two. First, how does one enable TIS/SKEY authorization for ssh? It appears that the frst step would be to add -DSKEY to the Makefile conditional on something. Are there other steps? Second, how does one specify options on the command line? In ssh 1.2.x, I say ssh -o ForwardX11=yes, but that doesn't work in OpenSSH. Bug or feature? Warner To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: ssh strangeness in -current...
"Matthew N. Dodd" wrote: > > On Sun, 5 Mar 2000, Kris Kennaway wrote: > > On Sun, 5 Mar 2000, Matthew N. Dodd wrote: > > > I'm building with NO_OPENSSL and NO_OPENSSH and have still gotten hit with > > > breakage. > > > > I can't fix this if you don't tell me what it is! > > What? Nobody else is test compiling with NO_OPENSSL/NO_OPENSSH? I am. I found an error, sent it to the list, and Kris came up with a fix. The whole point of gamma testing the release candidates is that when people find problems they report them and they get fixed. Doug -- "Welcome to the desert of the real." - Laurence Fishburne as Morpheus, "The Matrix" To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: which(1), rewritten in C?
On Fri, Mar 03, 2000 at 12:04:41PM -0800, Matthew Hunt wrote: > > and the "type" builtin is too verbose, saying "which is hashed alias which='type -p' To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: ssh strangeness in -current...
On 06-Mar-00 Kris Kennaway wrote: > On Mon, 6 Mar 2000, Oliver Fromme wrote: > >> the ports (yeah, stupid me), to no avail. It complained about some >> RSA library missing. > > Did you read the error message? Perhaps you should. Perhaps reporting it > here would help someone to actually fix your problem instead of having to > guess. I think you've kind of missed the point though, Kris. How many other people are going to upgrade only to find that their previously working system is now broken. We should at least mention this in UPDATING so people have a ghost of a chance. >> Apart from my stupidness of not checking the location of the binary >> first -- what did I do wrong, and what's the recommended way of >> handling this? Am I supposed to rm /usr/bin/ssh each time I install a >> new release or snapshot? I can't believe that. > > Read /etc/defaults/make.conf > >> By the way, _why_ is ssh in the base system now, and what is >> wrong with having it in the ports? I'm sorry if there was a >> "HEADS UP" on this list, then I must have missed it. > > Enough people wanted it in the base system - in fact, when the question > was asked about importing it, I don't recall any objections - certainly it > was not a significant opposition. Actually, I don't recall a question. Rather, I recall Jordan saying that once openssl had finally been all fixed, we might as well add openssh so it would be useful. Had a vote been taken, I would have voted to pull openssl and wait until after 4.0 to straighten all this out. From other discussions I've had several other people I know would have voted the same way. Thankfully it is now in a working state for new installs and for upgrades if you sacrafice the proper animal and dance under a full moon, yada, yada, yada. :) > I'm quite surprised you've missed any discussion of OpenSSH here though, > since it's probably been one of the most discussed topics here for the > past few weeks. > > Kris -- John Baldwin <[EMAIL PROTECTED]> -- http://www.FreeBSD.org/~jhb/ PGP Key: http://www.cslab.vt.edu/~jobaldwi/pgpkey.asc "Power Users Use the Power to Serve!" - http://www.FreeBSD.org/ To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: diskprep beta -- comments wanted.
In message <[EMAIL PROTECTED]> "David O'Brien" writes: : > sysinstall doesn't work at all for me. On three different machines, : > it tells me that it found no disks. So I can't comment on this. : : Every time that happens to me, I just build and install a new sysinstall : on that machine and all of a sudden it works again. I'm guessing there : is something in the disk code that is sensitive to some structure size or : placement. This was on the machine I built it on... Warner To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: AWE64 & PCM
On Sun, Mar 05, 2000 at 09:09:02PM -0500, Jim Bloom wrote: > The only minor problem I see is that your game port is detected twice. Other > than that, the hardware is detected correctly. You have asked for help, but > what problem(s) are you seeing? Yeah, I realized that after the fact, thanks however :) > There is no support for the wave table part of the card at this time. Ok, that's the answer I was looking for, thought perhaps I was missing something there. Thanks again. Also, I was reading somewhere that turning on 3D Stereo Enhancement was simply by turning on a register somewhere (I forgot the exact explanation) is this possible also with newpcm? I kinda miss the feature of it. [I know my AWE64 supports it]. To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: diskprep beta -- comments wanted.
On Fri, Mar 03, 2000 at 05:40:17PM -0700, Warner Losh wrote: > > sysinstall doesn't work at all for me. On three different machines, > it tells me that it found no disks. So I can't comment on this. Every time that happens to me, I just build and install a new sysinstall on that machine and all of a sudden it works again. I'm guessing there is something in the disk code that is sensitive to some structure size or placement. -- -- David([EMAIL PROTECTED]) To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: VMWare 2.0R broken - linux ioctl(13, 1260, *) not implemented
On Sun, Mar 05, 2000 at 01:35:27PM +, Nick Sayer wrote: > Ah! I found it! > > --- linux_ioctl.h.orig Mon Feb 28 11:50:23 2000 > +++ linux_ioctl.h Mon Feb 28 11:24:08 2000 > @@ -32,6 +32,25 @@ > #define_LINUX_IOCTL_H_ This patch is fubar'ed. Your mailer wrapped lines and turned into 's. Can you repost this patch w/o damaging it? To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: kern/16487: please apply newpcm fix
On Mon, 6 Mar 2000 01:22:41 +0100 (CET), Oliver Fromme <[EMAIL PROTECTED]> said: Oliver> Would someone please (pretty please) have a look at kern/16487 Oliver> and commit the trivial fix in it? It's just one line, and it Oliver> makes AvanceLogic-100 soundcards work again. The logical ID of ALS100 conflicts with the one of CMI8330(mss), so we also have to check the vendor ID. Could you please give it to me? It is likely to be 0x00019305. (ALS110 is 0x10019305 and ALS120 is 0x20019305, so...) -- Seigo Tanimura <[EMAIL PROTECTED]> <[EMAIL PROTECTED]> To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: AWE64 & PCM
The only minor problem I see is that your game port is detected twice. Other than that, the hardware is detected correctly. You have asked for help, but what problem(s) are you seeing? I believe to get everything currently support on the AWE64, your config file should look like this: device pcm device sbc device joy There is no support for the wave table part of the card at this time. Jim Bloom [EMAIL PROTECTED] Chris Wasser wrote: > > Hi all, hate to post something this insignificant to the mailing list, but > I've search the entire src tree with no luck in resolving this myself > (well, grepping for awe64,wavetable,game .. found the AWE64 define in > /usr/src/sys/dev/sound/isa/sbc.c easily enough) .. I'm sure it's due to > some braindeadness on my behalf, but I'd sure appriciate someone steering > me in the right direction on this. I also searched for the > matching/compatible ID strings, no luck. > > Hopefully I provided enough information here... > > FreeBSD area51.v-wave.com 4.0-CURRENT FreeBSD 4.0-CURRENT #1: Sun Mar 5 > 12:02:16 MST 2000 [EMAIL PROTECTED]:/usr/src/sys/compile/AREA51 > i386 > > (cvsupped today -- well, at time of this posting.) > > joy0 at port 0x201 on isa0 > sbc0: at port 0x220-0x22f,0x330-0x331,0x388-0x38b irq > 5 drq 1,5 on isa0 > sbc0: setting card to irq 5, drq 1, 5 > pcm0: on sbc0 > joy1: at port 0x208-0x20f on isa0 > unknown0: at port 0x620-0x623 on isa0 > > Now I tried enabling PNPBIOS in the kernel config, but that just produced > a screenful of crap [PNP OS is disabled in the BIOS], here are the > relevant kernel config options (no, I didn't add anything else for sound > but this): > > [I read somewhere that the PCM driver doesn't support MIDI yet, not sure > if this is related] > > device pcm > device joy0at isa? port IO_GAME > > Adding the sbc driver into the config didn't help either, produced the > same dmesg output as above. > > I didn't use anything from the Voxware drivers like I used to under 3.x, I > also tried using the pnp directives for userconfig at boot time, but that > only produced syntax errors [same config I used for 3.x]: > > in /boot/kernel.conf: > > pnp 1 0 os enable irq0 5 drq0 1 drq1 5 port0 0x220 port1 0x330 port2 0x388 > pnp 1 1 os disable > pnp 1 2 os enable port0 0x620 port1 0xa20 port2 0xe20 > pnp 1 3 os disable > > devices in /dev: > > (sh MAKEDEV snd0) > > 0 lrwxrwxrwx 1 root wheel 6 Feb 24 02:05 /dev/mixer@ -> mixer0 > 0 crw-rw-rw- 1 root wheel 30, 0 Feb 24 02:05 /dev/mixer0 > 0 lrwxrwxrwx 1 root wheel10 Feb 24 02:05 /dev/sequencer@ -> > sequencer0 > 0 crw-rw-rw- 1 root wheel 30, 1 Feb 24 02:05 /dev/sequencer0 > 0 crw-rw-rw- 1 root wheel 30, 2 Feb 24 02:05 /dev/midi0 > 0 lrwxrwxrwx 1 root wheel 4 Feb 24 02:05 /dev/dsp@ -> dsp0 > 0 crw-rw-rw- 1 root wheel 30, 3 Mar 5 12:43 /dev/dsp0 > 0 lrwxrwxrwx 1 root wheel 5 Feb 24 02:05 /dev/dspW@ -> dspW0 > 0 crw-rw-rw- 1 root wheel 30, 5 Feb 24 02:05 /dev/dspW0 > 0 lrwxrwxrwx 1 root wheel 6 Feb 24 02:05 /dev/audio@ -> audio0 > 0 crw-rw-rw- 1 root wheel 30, 4 Feb 24 02:05 /dev/audio0 > 0 crw-rw-rw- 1 root wheel 30, 6 Feb 24 02:05 /dev/sndstat > 0 lrwxrwxrwx 1 root wheel 6 Feb 24 02:05 /dev/music@ -> music0 > 0 crw-rw-rw- 1 root wheel 30, 8 Feb 24 02:05 /dev/music0 > 0 lrwxrwxrwx 1 root wheel 4 Feb 24 02:05 /dev/pss@ -> pss0 > 0 crw-rw-rw- 1 root wheel 30, 9 Feb 24 02:05 /dev/pss0 > > /dev/sndstat reports: > > FreeBSD Audio Driver (newpcm) Mar 5 2000 12:00:51 > Installed devices: > pcm0: at io 0x220 irq 5 drq 1:5 (1p/1r channels duplex) > > And finally, a pnpinfo dump: > > Checking for Plug-n-Play devices... > > Card assigned CSN #1 > Vendor ID CTL00c3 (0xc3008c0e), Serial Number 0x1fa45429 > PnP Version 1.0, Vendor Version 16 > Device Description: Creative SB AWE64 PnP > *** Small Vendor Tag Detected > > Logical Device ID: CTL0045 0x45008c0e #0 > Device Description: Audio > TAG Start DF > Good Configuration > IRQ: 5 - only one type (true/edge) > DMA: channel(s) 1 > 8-bit, not a bus master, count by byte, , Compatibility mode > DMA: channel(s) 5 > 16-bit, not a bus master, , count by word, Compatibility mode > I/O Range 0x220 .. 0x220, alignment 0x1, len 0x10 > [16-bit addr] > I/O Range 0x330 .. 0x330, alignment 0x1, len 0x2 > [16-bit addr] > I/O Range 0x388 .. 0x388, alignment 0x1, len 0x4 > [16-bit addr] > TAG Start DF > Acceptable Configuration > IRQ: 5 7 9 10 - only one type (true/edge) > DMA: channel(s) 0 1 3 > 8-bit, not a bus master, count by byte, , Compatibility mode > DMA: channel(s) 5 6 7 > 16-bit, not a bus master, , count by word, Compatibility mode > I/O Range 0x220 .. 0x280, alignment 0x20, len 0x10 > [16-bit addr] > I/O Range 0x300 .. 0x330, alignment 0x30, len 0x2 > [16-bit addr] > I/O
Re: More "ld-elf.so.1: assert failed" messages
Below is a patch for "src/libexec/rtld-elf" which should fix the assert failures in wine. I'd appreciate hearing from anybody who tests this with multithreaded packages such as wine, JDK, Mozilla, and linuxthreads. Just a reminder -- be extra careful when messing with the dynamic linker. It's easy to paint yourself into a corner if it's broken badly. Make a backup copy of your current working dynamic linker (/usr/libexec/ld-elf.so.1) before installing the experimental version. Then if things fall apart you can recover with something like this: cd /usr/libexec chflags 0 ld-elf.so.1* mv ld-elf.so.1.good ld-elf.so.1 Thanks in advance for any testing you folks can make time to do. John Index: Makefile === RCS file: /home/ncvs/src/libexec/rtld-elf/Makefile,v retrieving revision 1.10 diff -u -r1.10 Makefile --- Makefile2000/01/29 03:16:54 1.10 +++ Makefile2000/03/01 02:39:13 @@ -3,7 +3,7 @@ # MAINTAINER=jdp PROG= ld-elf.so.1 -SRCS= rtld_start.S rtld.c lockdflt.c map_object.c malloc.c \ +SRCS= rtld_start.S rtld.c map_object.c malloc.c \ xmalloc.c debug.c reloc.c MAN1= rtld.1 CFLAGS+= -Wall -DFREEBSD_ELF -I${.CURDIR}/${MACHINE_ARCH} -I${.CURDIR} Index: lockdflt.c === RCS file: lockdflt.c diff -N lockdflt.c --- /tmp/cvscXuMc22613 Sun Mar 5 17:48:37 2000 +++ /dev/null Sun Mar 5 02:02:18 2000 @@ -1,89 +0,0 @@ -/*- - * Copyright 1999, 2000 John D. Polstra. - * All rights reserved. - * - * Redistribution and use in source and binary forms, with or without - * modification, are permitted provided that the following conditions - * are met: - * 1. Redistributions of source code must retain the above copyright - *notice, this list of conditions and the following disclaimer. - * 2. Redistributions in binary form must reproduce the above copyright - *notice, this list of conditions and the following disclaimer in the - *documentation and/or other materials provided with the distribution. - * - * THIS SOFTWARE IS PROVIDED BY THE AUTHOR ``AS IS'' AND ANY EXPRESS OR - * IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES - * OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE DISCLAIMED. - * IN NO EVENT SHALL THE AUTHOR BE LIABLE FOR ANY DIRECT, INDIRECT, - * INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT - * NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, - * DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY - * THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT - * (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OF - * THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE. - * - * $FreeBSD: src/libexec/rtld-elf/lockdflt.c,v 1.4 2000/01/25 01:32:56 jdp Exp $ - */ - -/* - * Default thread locking implementation for the dynamic linker. It - * is used until the client registers a different implementation with - * dllockinit(). The default implementation does mutual exclusion by - * blocking almost all signals. This is based on the observation that - * most userland thread packages use signals to support preemption. - */ - -#include -#include -#include - -#include "debug.h" -#include "rtld.h" - -typedef struct Struct_LockDflt { -sigset_t lock_mask; -sigset_t old_mask; -int depth; -} LockDflt; - -void -lockdflt_acquire(void *lock) -{ -LockDflt *l = (LockDflt *)lock; -sigprocmask(SIG_BLOCK, &l->lock_mask, &l->old_mask); -assert(l->depth == 0); -l->depth++; -} - -void * -lockdflt_create(void *context) -{ -LockDflt *l; - -l = NEW(LockDflt); -l->depth = 0; -sigfillset(&l->lock_mask); -sigdelset(&l->lock_mask, SIGTRAP); -sigdelset(&l->lock_mask, SIGABRT); -sigdelset(&l->lock_mask, SIGBUS); -sigdelset(&l->lock_mask, SIGSEGV); -sigdelset(&l->lock_mask, SIGKILL); -sigdelset(&l->lock_mask, SIGSTOP); -return l; -} - -void -lockdflt_destroy(void *lock) -{ -LockDflt *l = (LockDflt *)lock; -free(l); -} - -void -lockdflt_release(void *lock) -{ -LockDflt *l = (LockDflt *)lock; -assert(l->depth == 1); -l->depth--; -sigprocmask(SIG_SETMASK, &l->old_mask, NULL); -} Index: rtld.c === RCS file: /home/ncvs/src/libexec/rtld-elf/rtld.c,v retrieving revision 1.43 diff -u -r1.43 rtld.c --- rtld.c 2000/01/29 01:26:59 1.43 +++ rtld.c 2000/03/06 01:44:11 @@ -61,6 +61,9 @@ typedef struct Struct_LockInfo { void *context; /* Client context for creating locks */ void *thelock; /* The one big lock */ +/* Debugging aids. */ +volatile int rcount; /* Number of readers holding lock */ +volatile int wcount; /* Number of writers holding lock */
pam_ssh is broken! Would someone please review/commit PR 17191?
It's all contained in the subject. I've built world with the change and tested it and it all works fine now. -Chris -- [EMAIL PROTECTED] [EMAIL PROTECTED] Abbotsford, BC, Canada To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: ssh strangeness in -current...
On Sun, 5 Mar 2000, Matthew N. Dodd wrote: > > > I'm building with NO_OPENSSL and NO_OPENSSH and have still gotten hit with > > > breakage. > > > > I can't fix this if you don't tell me what it is! > > What? Nobody else is test compiling with NO_OPENSSL/NO_OPENSSH? Your message wasn't clear you were talking about _world_ breakage. If this is your only problem, see my other message. Kris In God we Trust -- all others must submit an X.509 certificate. -- Charles Forsythe <[EMAIL PROTECTED]> To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: ssh strangeness in -current...
On Sun, 5 Mar 2000, Kris Kennaway wrote: > On Sun, 5 Mar 2000, Matthew N. Dodd wrote: > > I'm building with NO_OPENSSL and NO_OPENSSH and have still gotten hit with > > breakage. > > I can't fix this if you don't tell me what it is! What? Nobody else is test compiling with NO_OPENSSL/NO_OPENSSH? -- | 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: ssh strangeness in -current...
On Sun, 5 Mar 2000, Matthew N. Dodd wrote: > I'm building with NO_OPENSSL and NO_OPENSSH and have still gotten hit with > breakage. I can't fix this if you don't tell me what it is! Kris In God we Trust -- all others must submit an X.509 certificate. -- Charles Forsythe <[EMAIL PROTECTED]> To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: ssh strangeness in -current...
On Mon, 6 Mar 2000, Oliver Fromme wrote: > the ports (yeah, stupid me), to no avail. It complained about some > RSA library missing. Did you read the error message? Perhaps you should. Perhaps reporting it here would help someone to actually fix your problem instead of having to guess. > PS: Just in case if it matters, I have USA_RESIDENT=NO in my > make.conf. Hmm. Can you try cvsupping your src-crypto and src-secure collections from another (non-US) cvsup server? One of the mirror sites in germany was bogusly fetching crypto from the US - I assumed it had been fixed by now after multiple emails to the maintainer, but perhaps it hasn't. SSH should work out of the box for International people. > Apart from my stupidness of not checking the location of the binary > first -- what did I do wrong, and what's the recommended way of > handling this? Am I supposed to rm /usr/bin/ssh each time I install a > new release or snapshot? I can't believe that. Read /etc/defaults/make.conf > By the way, _why_ is ssh in the base system now, and what is > wrong with having it in the ports? I'm sorry if there was a > "HEADS UP" on this list, then I must have missed it. Enough people wanted it in the base system - in fact, when the question was asked about importing it, I don't recall any objections - certainly it was not a significant opposition. I'm quite surprised you've missed any discussion of OpenSSH here though, since it's probably been one of the most discussed topics here for the past few weeks. Kris In God we Trust -- all others must submit an X.509 certificate. -- Charles Forsythe <[EMAIL PROTECTED]> To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
NO_OPENSSL world fixes
Okay, these patches were sufficient to allow me to build world with NO_OPENSSL defined. I'd like to commit these ASAP. After the release, I want to look at condensing the mass of .if defined(...) options we have, at least with respect to crypto. At the moment we have to test everywhere for things like .if !defined(NOCRYPT) && !defined(NOSECURE) && !defined(NO_OPENSSL) && defined(MAKE_KERBEROS4) when all we really want to know is whether or not OpenSSL is available to be linked with. In addition to normalizing all of the NO* options to NO_* (or other way round if I get shouted down :), they should obey the correct covering hierarchy automatically so we don't have to explicitly test for all the covering options in each instance. For example, NO_CRYPT should imply NO_OPENSSL, which in turn implies NO_OPENSSH, etc. NOSECURE should be removed since it's nonfunctional. NO_CRYPT or NO_OPENSSL should conflict with MAKE_KERBEROS?, etc. Kris Index: Makefile.inc1 === RCS file: /home/ncvs/src/Makefile.inc1,v retrieving revision 1.140 diff -u -r1.140 Makefile.inc1 --- Makefile.inc1 2000/02/28 21:04:38 1.140 +++ Makefile.inc1 2000/03/05 22:32:04 @@ -57,11 +57,11 @@ SUBDIR+= gnu .endif .if exists(${.CURDIR}/kerberosIV) && exists(${.CURDIR}/crypto) && \ -!defined(NOCRYPT) && defined(MAKE_KERBEROS4) +!defined(NOCRYPT) && !defined(NO_OPENSSL) && defined(MAKE_KERBEROS4) SUBDIR+= kerberosIV .endif .if exists(${.CURDIR}/kerberos5) && exists(${.CURDIR}/crypto) && \ -!defined(NOCRYPT) && defined(MAKE_KERBEROS5) +!defined(NOCRYPT) && !defined(NO_OPENSSL) && defined(MAKE_KERBEROS5) SUBDIR+= kerberos5 .endif .if exists(${.CURDIR}/libexec) @@ -203,7 +203,7 @@ # success, regardless of how old your existing system is. # buildworld: -.if !defined(NOSECURE) && exists(${.CURDIR}/secure) && \ +.if !defined(NOSECURE) && !defined(NO_OPENSSL) && exists(${.CURDIR}/secure) && \ (!defined(USA_RESIDENT) || (${USA_RESIDENT} != NO && \ ${USA_RESIDENT} != YES)) @echo Index: lib/Makefile === RCS file: /home/ncvs/src/lib/Makefile,v retrieving revision 1.106 diff -u -r1.106 Makefile --- lib/Makefile2000/01/21 02:00:53 1.106 +++ lib/Makefile2000/02/27 00:21:50 @@ -43,7 +43,7 @@ .endif _libcrypt= libcrypt -.if exists(${.CURDIR}/../secure) && !defined(NOSECURE) && !defined(NOCRYPT) +.if exists(${.CURDIR}/../secure) && !defined(NOSECURE) && !defined(NOCRYPT) && +!defined(NO_DESCRYPT) # Build both libraries. They have different names, so no harm, # and this avoids having stale libscrypt.* _libcrypt+=../secure/lib/libcrypt Index: lib/libpam/libpam/Makefile === RCS file: /home/ncvs/src/lib/libpam/libpam/Makefile,v retrieving revision 1.11 diff -u -r1.11 Makefile --- lib/libpam/libpam/Makefile 2000/02/28 21:00:48 1.11 +++ lib/libpam/libpam/Makefile 2000/03/05 22:32:04 @@ -62,16 +62,16 @@ # Static PAM modules: STATIC_MODULES+= ${MODOBJDIR}/pam_cleartext_pass_ok/libpam_cleartext_pass_ok.a STATIC_MODULES+= ${MODOBJDIR}/pam_deny/libpam_deny.a -.if defined(MAKE_KERBEROS4) && !defined(NOCRYPT) +.if defined(MAKE_KERBEROS4) && !defined(NOCRYPT) && !defined(NO_OPENSSL) STATIC_MODULES+= ${MODOBJDIR}/pam_kerberosIV/libpam_kerberosIV.a .endif -.if defined(MAKE_KERBEROS5__) && !defined(NOCRYPT) +.if defined(MAKE_KERBEROS5__) && !defined(NOCRYPT) && !defined(NO_OPENSSL) STATIC_MODULES+= ${MODOBJDIR}/pam_kerberos5/libpam_kerberos5.a .endif STATIC_MODULES+= ${MODOBJDIR}/pam_permit/libpam_permit.a STATIC_MODULES+= ${MODOBJDIR}/pam_radius/libpam_radius.a STATIC_MODULES+= ${MODOBJDIR}/pam_skey/libpam_skey.a -.if exists(${.CURDIR}/../../../crypto/openssh) && !defined(NO_OPENSSL) +.if exists(${.CURDIR}/../../../crypto/openssh) && !defined(NOCRYPT) && +!defined(NO_OPENSSL) STATIC_MODULES+= ${MODOBJDIR}/pam_ssh/libpam_ssh.a .endif STATIC_MODULES+= ${MODOBJDIR}/pam_tacplus/libpam_tacplus.a Index: lib/libpam/modules/Makefile === RCS file: /home/ncvs/src/lib/libpam/modules/Makefile,v retrieving revision 1.7 diff -u -r1.7 Makefile --- lib/libpam/modules/Makefile 2000/02/28 21:00:50 1.7 +++ lib/libpam/modules/Makefile 2000/03/05 22:32:04 @@ -26,16 +26,16 @@ SUBDIR+= pam_cleartext_pass_ok SUBDIR+= pam_deny -.if defined(MAKE_KERBEROS4) && !defined(NOCRYPT) +.if defined(MAKE_KERBEROS4) && !defined(NOCRYPT) && !defined(NO_OPENSSL) SUBDIR+= pam_kerberosIV .endif -.if defined(MAKE_KERBEROS5__) && !defined(NOCRYPT) +.if defined(MAKE_KERBEROS5__) && !defined(NOCRYPT) && !defined(NO_OPENSSL) SUBDIR+= pam_kerberos5 .endif SUBDIR+= pam_permit SUBDIR+= pam_radius SUBDIR+= pam_skey -.if exists(${.CURDIR}/../../../crypto/openssh) && !defined(NO_OPENSSL) +.if exists
Re: ssh strangeness in -current...
On Mon, 6 Mar 2000, Oliver Fromme wrote: > By the way, _why_ is ssh in the base system now, and what is wrong > with having it in the ports? I'm sorry if there was a "HEADS UP" on > this list, then I must have missed it. I keep asking myself this question; a default sysinstall package would give us the same end result. I'm building with NO_OPENSSL and NO_OPENSSH and have still gotten hit with breakage. -- | 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
kern/16487: please apply newpcm fix
Hi, Would someone please (pretty please) have a look at kern/16487 and commit the trivial fix in it? It's just one line, and it makes AvanceLogic-100 soundcards work again. On a related note (unfortunately I don't have a fix for this): The ALS-100 cards have a volume problem with newpcm. They're much too soft. Even if I push the mixer settings all the way to 100%, I have to turn the volume on the amplifier very high, which results in a lot of static and noise. I can literally hear every disk access and window movement through the speakers. It's horrible. :-( That did not happen with Luigi's "oldpcm": I could keep the amplifier at a moderate level, and the mixer was at about 60% to get decent audio playback -- no static, no noise. Same machine, same soundcard. Is this a known problem? I didn't find anything in the PR DB, so I should probably submit a PR about this. Regards Oliver -- Oliver Fromme, Leibnizstr. 18/61, 38678 Clausthal, Germany (Info: finger userinfo:[EMAIL PROTECTED]) "In jedem Stück Kohle wartet ein Diamant auf seine Geburt" (Terry Pratchett) To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
ssh strangeness in -current...
Hi, I have upgraded a machine to the latest -current snapshot (it was running a -current from the end of January before). Every- thing went fine, except for one thing: ssh didn't work anymore. It used to work fine before. At first I was very suprised and had no clue what was going on. I couldn't imagine how the new -current base system could affect my ssh binary which had been installed from the ports long before. I even pkg_deleted it and re-installed it from the ports (yeah, stupid me), to no avail. It complained about some RSA library missing. Finally I got the great idea to type "which ssh", showing me that there now was a (non-functional) ssh binary in /usr/bin. I removed it, and everything started working again, picking up the ports version from /usr/local/bin. Apart from my stupidness of not checking the location of the binary first -- what did I do wrong, and what's the recommended way of handling this? Am I supposed to rm /usr/bin/ssh each time I install a new release or snapshot? I can't believe that. By the way, _why_ is ssh in the base system now, and what is wrong with having it in the ports? I'm sorry if there was a "HEADS UP" on this list, then I must have missed it. Regards Oliver PS: Just in case if it matters, I have USA_RESIDENT=NO in my make.conf. -- Oliver Fromme, Leibnizstr. 18/61, 38678 Clausthal, Germany (Info: finger userinfo:[EMAIL PROTECTED]) "In jedem Stück Kohle wartet ein Diamant auf seine Geburt" (Terry Pratchett) To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
$BM-L>%?%l%s%H6KHk(BSM$B1GA|(B
http://k.manami.tripod.com/ $B$r$4Mw2<$5$$!#4|4V8BDj!#(B To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
AWE64 & PCM
Hi all, hate to post something this insignificant to the mailing list, but I've search the entire src tree with no luck in resolving this myself (well, grepping for awe64,wavetable,game .. found the AWE64 define in /usr/src/sys/dev/sound/isa/sbc.c easily enough) .. I'm sure it's due to some braindeadness on my behalf, but I'd sure appriciate someone steering me in the right direction on this. I also searched for the matching/compatible ID strings, no luck. Hopefully I provided enough information here... FreeBSD area51.v-wave.com 4.0-CURRENT FreeBSD 4.0-CURRENT #1: Sun Mar 5 12:02:16 MST 2000 [EMAIL PROTECTED]:/usr/src/sys/compile/AREA51 i386 (cvsupped today -- well, at time of this posting.) joy0 at port 0x201 on isa0 sbc0: at port 0x220-0x22f,0x330-0x331,0x388-0x38b irq 5 drq 1,5 on isa0 sbc0: setting card to irq 5, drq 1, 5 pcm0: on sbc0 joy1: at port 0x208-0x20f on isa0 unknown0: at port 0x620-0x623 on isa0 Now I tried enabling PNPBIOS in the kernel config, but that just produced a screenful of crap [PNP OS is disabled in the BIOS], here are the relevant kernel config options (no, I didn't add anything else for sound but this): [I read somewhere that the PCM driver doesn't support MIDI yet, not sure if this is related] device pcm device joy0at isa? port IO_GAME Adding the sbc driver into the config didn't help either, produced the same dmesg output as above. I didn't use anything from the Voxware drivers like I used to under 3.x, I also tried using the pnp directives for userconfig at boot time, but that only produced syntax errors [same config I used for 3.x]: in /boot/kernel.conf: pnp 1 0 os enable irq0 5 drq0 1 drq1 5 port0 0x220 port1 0x330 port2 0x388 pnp 1 1 os disable pnp 1 2 os enable port0 0x620 port1 0xa20 port2 0xe20 pnp 1 3 os disable devices in /dev: (sh MAKEDEV snd0) 0 lrwxrwxrwx 1 root wheel 6 Feb 24 02:05 /dev/mixer@ -> mixer0 0 crw-rw-rw- 1 root wheel 30, 0 Feb 24 02:05 /dev/mixer0 0 lrwxrwxrwx 1 root wheel10 Feb 24 02:05 /dev/sequencer@ -> sequencer0 0 crw-rw-rw- 1 root wheel 30, 1 Feb 24 02:05 /dev/sequencer0 0 crw-rw-rw- 1 root wheel 30, 2 Feb 24 02:05 /dev/midi0 0 lrwxrwxrwx 1 root wheel 4 Feb 24 02:05 /dev/dsp@ -> dsp0 0 crw-rw-rw- 1 root wheel 30, 3 Mar 5 12:43 /dev/dsp0 0 lrwxrwxrwx 1 root wheel 5 Feb 24 02:05 /dev/dspW@ -> dspW0 0 crw-rw-rw- 1 root wheel 30, 5 Feb 24 02:05 /dev/dspW0 0 lrwxrwxrwx 1 root wheel 6 Feb 24 02:05 /dev/audio@ -> audio0 0 crw-rw-rw- 1 root wheel 30, 4 Feb 24 02:05 /dev/audio0 0 crw-rw-rw- 1 root wheel 30, 6 Feb 24 02:05 /dev/sndstat 0 lrwxrwxrwx 1 root wheel 6 Feb 24 02:05 /dev/music@ -> music0 0 crw-rw-rw- 1 root wheel 30, 8 Feb 24 02:05 /dev/music0 0 lrwxrwxrwx 1 root wheel 4 Feb 24 02:05 /dev/pss@ -> pss0 0 crw-rw-rw- 1 root wheel 30, 9 Feb 24 02:05 /dev/pss0 /dev/sndstat reports: FreeBSD Audio Driver (newpcm) Mar 5 2000 12:00:51 Installed devices: pcm0: at io 0x220 irq 5 drq 1:5 (1p/1r channels duplex) And finally, a pnpinfo dump: Checking for Plug-n-Play devices... Card assigned CSN #1 Vendor ID CTL00c3 (0xc3008c0e), Serial Number 0x1fa45429 PnP Version 1.0, Vendor Version 16 Device Description: Creative SB AWE64 PnP *** Small Vendor Tag Detected Logical Device ID: CTL0045 0x45008c0e #0 Device Description: Audio TAG Start DF Good Configuration IRQ: 5 - only one type (true/edge) DMA: channel(s) 1 8-bit, not a bus master, count by byte, , Compatibility mode DMA: channel(s) 5 16-bit, not a bus master, , count by word, Compatibility mode I/O Range 0x220 .. 0x220, alignment 0x1, len 0x10 [16-bit addr] I/O Range 0x330 .. 0x330, alignment 0x1, len 0x2 [16-bit addr] I/O Range 0x388 .. 0x388, alignment 0x1, len 0x4 [16-bit addr] TAG Start DF Acceptable Configuration IRQ: 5 7 9 10 - only one type (true/edge) DMA: channel(s) 0 1 3 8-bit, not a bus master, count by byte, , Compatibility mode DMA: channel(s) 5 6 7 16-bit, not a bus master, , count by word, Compatibility mode I/O Range 0x220 .. 0x280, alignment 0x20, len 0x10 [16-bit addr] I/O Range 0x300 .. 0x330, alignment 0x30, len 0x2 [16-bit addr] I/O Range 0x388 .. 0x388, alignment 0x1, len 0x4 [16-bit addr] TAG Start DF Acceptable Configuration IRQ: 5 7 9 10 - only one type (true/edge) DMA: channel(s) 0 1 3 8-bit, not a bus master, count by byte, , Compatibility mode DMA: channel(s) 5 6 7 16-bit, not a bus master, , count by word, Compatibility mode I/O Range 0x220 .. 0x280, alignment 0x20, len 0x10 [16-bit addr] I/O Range 0x300 .. 0x330, alignment 0x30, len 0x2 [16-bit addr] TAG Start DF Acceptable Configuration IRQ: 5 7 9 10 - only one type (true/edge) DMA: channel(s) 0 1 3 8-bit, not a bus master, count by byte, , Compatib
Re: Make world error.....
On Sun, 5 Mar 2000, Brian Dean wrote: > The perl script h2ph does not exit immediately on des.h, it sets it's > $Exit value to 1, but continues processing. If the original poster > would check further back in his log file, he'll see: Ah, okay. There might be an ordering problem with the des.h symlink being created before the openssl/des.h file which it points to. Any ideas, Mark? Kris In God we Trust -- all others must submit an X.509 certificate. -- Charles Forsythe <[EMAIL PROTECTED]> To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: Make world error.....
The perl script h2ph does not exit immediately on des.h, it sets it's $Exit value to 1, but continues processing. If the original poster would check further back in his log file, he'll see: [...] ===> gnu/usr.bin/perl/utils/h2ph install -c -o root -g wheel -m 555 h2ph /usr/bin install -c -o root -g wheel -m 444 h2ph.1.gz /usr/share/man/man1 cd /usr/include; miniperl /usr/obj/usr/src/gnu/usr.bin/perl/utils/h2ph/h2ph -d /usr/libdata/perl/5.00503/mach * */* Skipping directory `arpa' Skipping directory `cam' Can't open des.h: No such file or directory Skipping directory `dev' Skipping directory `g++' Skipping directory `isofs' Skipping directory `machine' Skipping directory `msdosfs' [...] vm/vm_prot.h -> vm/vm_prot.ph vm/vm_zone.h -> vm/vm_zone.ph vm/vnode_pager.h -> vm/vnode_pager.ph *** Error code 1 Stop in /usr/src/gnu/usr.bin/perl/utils/h2ph. *** Error code 1 Unfortunately, I don't remember if the thing des.h pointed to (openssl/des.h) existed at the time. After I modified h2ph to not complain about that file, I did another make world a little bit later, and it completed without incident. I suspected that I had merely sup'd at a bad time and just caught things in transition. -Brian Kris Kennaway wrote: > > William Woods wrote: > > > vm/vnode_pager.h -> vm/vnode_pager.ph > > > *** Error code 1 > > > > > > Stop in /usr/src/gnu/usr.bin/perl/utils/h2ph. > > > *** Error code 1 > > > > I got the same thing here. h2ph does not like /usr/include/des.h > > which is a symlink to /usr/include/openssl/des.h, complaining about > > "no such file or directory". I fixed mine by hacking h2ph in > > What is the difference between des.h and the 19 other symlinks we have in > /usr/include? i.e. why does it just hate this one? > > The original poster also seemed to not be having this problem, at least > from the fragment of the log above: it's dying nowhere near > perlifying des.h. > > Kris To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: plist/glist query & proposal
make sure to keep me on the cc list, I'm not on -current or -scsi Matthew N. Dodd scribbled this message on Mar 5: > On Sun, 5 Mar 2000, John-Mark Gurney wrote: > > Doug White forwarded this message to me I actually have done this > > but I have not cleaned the code up for committing to the tree... > > > > I have been running this code for over a half year now... > > > > if people want, I can comitte this as is, but I'm using old daily > > routines on my box, not the newer ones... > > I like it, though you may want to have an /etc/glist.conf and let the > user add stuff with a script that tests to make sure a drive supports the > format. A script to test and populate this file wouldn't be > difficult. yeh, I originally was using block for a while, and ONE of my drives didn't support it, then I switched to phys, and haven't had a problem.. and I have quite a range of drives: hydrogen,ttyq3,~,502$grep 'Direct Access' /var/run/dmesg.boot da3: Fixed Direct Access SCSI-CCS device da0: Fixed Direct Access SCSI-2 device da5: Fixed Direct Access SCSI-CCS device da6: Fixed Direct Access SCSI-CCS device da2: Fixed Direct Access SCSI-2 device da1: Fixed Direct Access SCSI-2 device da4: Fixed Direct Access SCSI-2 device which is a selection of scsi-1 (scsi-ccs), fast scsi, and ultra scsi drives... I'm sure that just using phys will keep all drives usable.. and if the user wants a different format, they can manually run camcontrol... bad disk blocks SHOULDN'T appear that often... :) > # > # /etc/glist.conf > # > # Drive name Format (block, bfi, phys) > da0 phys > da1 block > ... something like: `awk '$1 ~ /(da|sd)'"${i}"'/ { type = $2 } END { if (type == "" ) echo "phys"; else echo type; }'` should do perfectly fine... :) > > bak=/var/backups > > echo "" > > echo "" > > echo "checking disks for defects:" > > for i in `camcontrol devlist | awk '/(da|sd)/ { if (match($0, >"(da|sd)[[:digit:]]+") != 0) { diskname = substr($0, RSTART, RLENGTH); >match(diskname, "[[:digit:]]+"); print substr(diskname, RSTART, RLENGTH) } }' | sort >-u`; do > > if [ -f ${bak}/da${i}.glist ]; then > > mv ${bak}/da${i}.glist ${bak}/da${i}.glist.bak > > fi > > echo -n "da${i}: " > > camcontrol defects -u $i -f phys -G 2>&1 > ${bak}/da${i}.glist > > if [ -f ${bak}/da${i}.glist.bak ]; then > > if ! cmp -s ${bak}/da${i}.glist ${bak}/da${i}.glist.bak; then > > diff ${bak}/da${i}.glist.bak ${bak}/da${i}.glist > > fi > > fi > > done -- John-Mark Gurney Voice: +1 408 975 9651 Cu Networking "The soul contains in itself the event that shall presently befall it. The event is only the actualizing of its thought." -- Ralph Waldo Emerson To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: Make world error.....
On Sat, 4 Mar 2000, Brian Dean wrote: > William Woods wrote: > > vm/vnode_pager.h -> vm/vnode_pager.ph > > *** Error code 1 > > > > Stop in /usr/src/gnu/usr.bin/perl/utils/h2ph. > > *** Error code 1 > > I got the same thing here. h2ph does not like /usr/include/des.h > which is a symlink to /usr/include/openssl/des.h, complaining about > "no such file or directory". I fixed mine by hacking h2ph in What is the difference between des.h and the 19 other symlinks we have in /usr/include? i.e. why does it just hate this one? The original poster also seemed to not be having this problem, at least from the fragment of the log above: it's dying nowhere near perlifying des.h. Kris In God we Trust -- all others must submit an X.509 certificate. -- Charles Forsythe <[EMAIL PROTECTED]> To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: Buildworld failures
On Sat, 4 Mar 2000, Jeff Palmer wrote: > I have cvsupped and tried to build world mutiple times over the past 3 > days, each time I get the same error. I have been following the mailing > lists and don't see any other complaints.. So I'm sure the trouble is > with my machine... Are you building with NO_OPENSSL? Kris In God we Trust -- all others must submit an X.509 certificate. -- Charles Forsythe <[EMAIL PROTECTED]> To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: [usb-bsd] Rio500 USB driver for FreeBSD
On Sun, 5 Mar 2000, Nick Hibma wrote: > > The USB patchset for FreeBSD now contains the driver for the > > Diamond Rio 500 MP3 Player > > as well. Any comments on the driver? Please contact to the author: Iwasa > Kazmi <[EMAIL PROTECTED]> > > The patchset is available from > > http://www.etla.net/~n_hibma/usb/usb.pl#URIODriver > > and is made against CURRENT as of 2000/03/05 02:00. Instructions are > included in the file. Thanks Nick. Meanwhile in addition to the ./configure command on that page, until the rio500-linux boys have commited a small patch, the above ports.tgz should more or less build the much needed userland tools; which requires just a <-> patch. > Keep us posted! Dw. > On Mon, 6 Mar 2000, Iwasa Kazmi wrote: > > > Hello all, > > > > I put a new FreeBSD driver on my web page. > > http://www02.u-page.so-net.ne.jp/ca2/kzmi/rio-tools/rio-fbsd-0306.tar.gz > > > > It includes Dirk's code for FreeBSD 4.0. > > > > Now this driver has 143 as its major number. > > Nick Hibma, a member of FreeBSD USB project, says that he would like to > > add this driver to the FreeBSD source repository. > > It's very nice. I'm going to do something for it. > > > > > > Iwasa Kazmi > > [EMAIL PROTECTED] > > > > -- > [EMAIL PROTECTED] > [EMAIL PROTECTED] USB project > http://www.etla.net/~n_hibma/ > > > > Get paid for the computing stuff you know! > Get answers for the stuff you dont. And get $10 to spend on the site! > http://click.egroups.com/1/2197/4/_/85983/_/952292433/ > > -- Create a poll/survey for your group! > -- http://www.egroups.com/vote?listname=usb-bsd&m=1 > > > rio500.tgz
Re: libcrypto.a - deja vu?
>> cc -fpic -DPIC -O -pipe -Wall >-I/usr/src/lib/libpam/modules/pam_deny/../../../../contrib/libpam/libpam/include >-I/usr/obj/usr/src/i386/usr/include -c >/usr/src/lib/libpam/modules/pam_deny/../../../../contrib/libpam/modules/pam_deny/pam_deny.c > -o pam_deny.So >> building standard pam_deny library >> ranlib libpam_deny.a >> building shared library pam_deny.so >> ===> libpam/modules/pam_kerberosIV >> make: don't know how to make /usr/obj/usr/src/i386/usr/lib/libcrypto.a. Stop >> *** Error code 2 > Are you building with NO_OPENSSL? I just ran into this exact problem > myself overnight with my buildworld with NO_OPENSSL enabled. that's the cause. > Try this patch: thanks. will do. randy To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: plist/glist query & proposal
On Sun, 5 Mar 2000, John-Mark Gurney wrote: > Doug White forwarded this message to me I actually have done this > but I have not cleaned the code up for committing to the tree... > > I have been running this code for over a half year now... > > if people want, I can comitte this as is, but I'm using old daily > routines on my box, not the newer ones... I like it, though you may want to have an /etc/glist.conf and let the user add stuff with a script that tests to make sure a drive supports the format. A script to test and populate this file wouldn't be difficult. # # /etc/glist.conf # # Drive nameFormat (block, bfi, phys) da0 phys da1 block ... > bak=/var/backups > echo "" > echo "" > echo "checking disks for defects:" > for i in `camcontrol devlist | awk '/(da|sd)/ { if (match($0, "(da|sd)[[:digit:]]+") >!= 0) { diskname = substr($0, RSTART, RLENGTH); match(diskname, "[[:digit:]]+"); >print substr(diskname, RSTART, RLENGTH) } }' | sort -u`; do > if [ -f ${bak}/da${i}.glist ]; then > mv ${bak}/da${i}.glist ${bak}/da${i}.glist.bak > fi > echo -n "da${i}: " > camcontrol defects -u $i -f phys -G 2>&1 > ${bak}/da${i}.glist > if [ -f ${bak}/da${i}.glist.bak ]; then > if ! cmp -s ${bak}/da${i}.glist ${bak}/da${i}.glist.bak; then > diff ${bak}/da${i}.glist.bak ${bak}/da${i}.glist > fi > fi > done > > -- | 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: libcrypto.a - deja vu?
Oops, my buildworld -DNOCLEAN just failed again. Updated patch: Index: libpam/Makefile === RCS file: /home/ncvs/src/lib/libpam/libpam/Makefile,v retrieving revision 1.11 diff -u -r1.11 Makefile --- libpam/Makefile 2000/02/28 21:00:48 1.11 +++ libpam/Makefile 2000/03/05 21:46:10 @@ -62,16 +62,16 @@ # Static PAM modules: STATIC_MODULES+= ${MODOBJDIR}/pam_cleartext_pass_ok/libpam_cleartext_pass_ok.a STATIC_MODULES+= ${MODOBJDIR}/pam_deny/libpam_deny.a -.if defined(MAKE_KERBEROS4) && !defined(NOCRYPT) +.if defined(MAKE_KERBEROS4) && !defined(NOCRYPT) && !defined(NO_OPENSSL) STATIC_MODULES+= ${MODOBJDIR}/pam_kerberosIV/libpam_kerberosIV.a .endif -.if defined(MAKE_KERBEROS5__) && !defined(NOCRYPT) +.if defined(MAKE_KERBEROS5__) && !defined(NOCRYPT) && !defined(NO_OPENSSL) STATIC_MODULES+= ${MODOBJDIR}/pam_kerberos5/libpam_kerberos5.a .endif STATIC_MODULES+= ${MODOBJDIR}/pam_permit/libpam_permit.a STATIC_MODULES+= ${MODOBJDIR}/pam_radius/libpam_radius.a STATIC_MODULES+= ${MODOBJDIR}/pam_skey/libpam_skey.a -.if exists(${.CURDIR}/../../../crypto/openssh) && !defined(NO_OPENSSL) +.if exists(${.CURDIR}/../../../crypto/openssh) && !defined(NOCRYPT) && +!defined(NO_OPENSSL) STATIC_MODULES+= ${MODOBJDIR}/pam_ssh/libpam_ssh.a .endif STATIC_MODULES+= ${MODOBJDIR}/pam_tacplus/libpam_tacplus.a Index: modules/Makefile === RCS file: /home/ncvs/src/lib/libpam/modules/Makefile,v retrieving revision 1.7 diff -u -r1.7 Makefile --- modules/Makefile2000/02/28 21:00:50 1.7 +++ modules/Makefile2000/03/05 21:46:25 @@ -26,16 +26,16 @@ SUBDIR+= pam_cleartext_pass_ok SUBDIR+= pam_deny -.if defined(MAKE_KERBEROS4) && !defined(NOCRYPT) +.if defined(MAKE_KERBEROS4) && !defined(NOCRYPT) && !defined(NO_OPENSSL) SUBDIR+= pam_kerberosIV .endif -.if defined(MAKE_KERBEROS5__) && !defined(NOCRYPT) +.if defined(MAKE_KERBEROS5__) && !defined(NOCRYPT) && !defined(NO_OPENSSL) SUBDIR+= pam_kerberos5 .endif SUBDIR+= pam_permit SUBDIR+= pam_radius SUBDIR+= pam_skey -.if exists(${.CURDIR}/../../../crypto/openssh) && !defined(NO_OPENSSL) +.if exists(${.CURDIR}/../../../crypto/openssh) && !defined(NOCRYPT) && +!defined(NO_OPENSSL) SUBDIR+= pam_ssh .endif SUBDIR+= pam_tacplus In God we Trust -- all others must submit an X.509 certificate. -- Charles Forsythe <[EMAIL PROTECTED]> To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: libcrypto.a - deja vu?
On Sun, 5 Mar 2000, Randy Bush wrote: > > cc -fpic -DPIC -O -pipe -Wall >-I/usr/src/lib/libpam/modules/pam_deny/../../../../contrib/libpam/libpam/include >-I/usr/obj/usr/src/i386/usr/include -c >/usr/src/lib/libpam/modules/pam_deny/../../../../contrib/libpam/modules/pam_deny/pam_deny.c > -o pam_deny.So > building standard pam_deny library > ranlib libpam_deny.a > building shared library pam_deny.so > ===> libpam/modules/pam_kerberosIV > make: don't know how to make /usr/obj/usr/src/i386/usr/lib/libcrypto.a. Stop > *** Error code 2 Are you building with NO_OPENSSL? I just ran into this exact problem myself overnight with my buildworld with NO_OPENSSL enabled. Try this patch: Index: Makefile === RCS file: /home/ncvs/src/lib/libpam/modules/Makefile,v retrieving revision 1.7 diff -u -r1.7 Makefile --- Makefile2000/02/28 21:00:50 1.7 +++ Makefile2000/03/05 21:30:35 @@ -26,10 +26,10 @@ SUBDIR+= pam_cleartext_pass_ok SUBDIR+= pam_deny -.if defined(MAKE_KERBEROS4) && !defined(NOCRYPT) +.if defined(MAKE_KERBEROS4) && !defined(NOCRYPT) && !defined(NO_OPENSSL) SUBDIR+= pam_kerberosIV .endif -.if defined(MAKE_KERBEROS5__) && !defined(NOCRYPT) +.if defined(MAKE_KERBEROS5__) && !defined(NOCRYPT) && !defined(NO_OPENSSL) SUBDIR+= pam_kerberos5 .endif SUBDIR+= pam_permit In God we Trust -- all others must submit an X.509 certificate. -- Charles Forsythe <[EMAIL PROTECTED]> To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Rio500 USB driver for FreeBSD
The USB patchset for FreeBSD now contains the driver for the Diamond Rio 500 MP3 Player as well. Any comments on the driver? Please contact to the author: Iwasa Kazmi <[EMAIL PROTECTED]> The patchset is available from http://www.etla.net/~n_hibma/usb/usb.pl#URIODriver and is made against CURRENT as of 2000/03/05 02:00. Instructions are included in the file. Keep us posted! Nick On Mon, 6 Mar 2000, Iwasa Kazmi wrote: > Hello all, > > I put a new FreeBSD driver on my web page. > http://www02.u-page.so-net.ne.jp/ca2/kzmi/rio-tools/rio-fbsd-0306.tar.gz > > It includes Dirk's code for FreeBSD 4.0. > > Now this driver has 143 as its major number. > Nick Hibma, a member of FreeBSD USB project, says that he would like to > add this driver to the FreeBSD source repository. > It's very nice. I'm going to do something for it. > > > Iwasa Kazmi > [EMAIL PROTECTED] > -- [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
plist/glist query & proposal
Doug White forwarded this message to me I actually have done this but I have not cleaned the code up for committing to the tree... I have been running this code for over a half year now... if people want, I can comitte this as is, but I'm using old daily routines on my box, not the newer ones... bak=/var/backups echo "" echo "" echo "checking disks for defects:" for i in `camcontrol devlist | awk '/(da|sd)/ { if (match($0, "(da|sd)[[:digit:]]+") != 0) { diskname = substr($0, RSTART, RLENGTH); match(diskname, "[[:digit:]]+"); print substr(diskname, RSTART, RLENGTH) } }' | sort -u`; do if [ -f ${bak}/da${i}.glist ]; then mv ${bak}/da${i}.glist ${bak}/da${i}.glist.bak fi echo -n "da${i}: " camcontrol defects -u $i -f phys -G 2>&1 > ${bak}/da${i}.glist if [ -f ${bak}/da${i}.glist.bak ]; then if ! cmp -s ${bak}/da${i}.glist ${bak}/da${i}.glist.bak; then diff ${bak}/da${i}.glist.bak ${bak}/da${i}.glist fi fi done -- John-Mark Gurney Voice: +1 408 975 9651 Cu Networking "The soul contains in itself the event that shall presently befall it. The event is only the actualizing of its thought." -- Ralph Waldo Emerson To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
libcrypto.a - deja vu?
i know i have been here before, but i forget the magic. and i checked UPDATING and mail archive (the restoration thereof is much appreciated!) cc -fpic -DPIC -O -pipe -Wall -I/usr/src/lib/libpam/modules/pam_deny/../../../../contrib/libpam/libpam/include -I/usr/obj/usr/src/i386/usr/include -c /usr/src/lib/libpam/modules/pam_deny/../../../../contrib/libpam/modules/pam_deny/pam_deny.c -o pam_deny.So building standard pam_deny library ranlib libpam_deny.a building shared library pam_deny.so ===> libpam/modules/pam_kerberosIV make: don't know how to make /usr/obj/usr/src/i386/usr/lib/libcrypto.a. Stop *** Error code 2 randy To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
"fatal trap 12" with 4.0-CURRENT
I keep getting 'trap 12' with 4.0-CURRENT when running rvplayer5. Has anyone else experienced this? I haven't got a remote terminal for debugging, but it looks like this bug is emanating from the fxp driver: fxp_start+0x110 movl %edx,0(%ecx, %eax ,1) System: % uname -a FreeBSD motsognir.unik.no 4.0-CURRENT FreeBSD 4.0-CURRENT #31: Thu Mar 2 15:34:17 CET 2000 [EMAIL PROTECTED]:/usr/src/sys/compile/ZEUS i386 % dmesg | grep fxp fxp0: port 0xb400-0xb41f mem 0xdf00-0xdf0f,0xe200-0xe2000fff irq 17 at device 11.0 on pci0 XFree version 3.3.5 I can try to borrow remote terminal to get a trace if anyone's interested. -- Andreas Dobloug : email: [EMAIL PROTECTED] To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: Modem no longer found after u/g to 4.0-current - help
On Mon, Mar 06, 2000 at 12:57:50AM +0800, Peter Wemm wrote: > Mark Ovens wrote: > > On Sun, Mar 05, 2000 at 04:04:59PM +, Doug Rabson wrote: > > > On Sun, 5 Mar 2000, Mark Ovens wrote: > > > > > > > On Sun, Mar 05, 2000 at 01:04:23PM +, Doug Rabson wrote: > > > > > Could you send me the output of pnpinfo. I think we are missing a PnP I > D > > > > > in the sio driver. > > > > > > > > > > > > > The line I've added to sio.c is: > > > > > > > > > > > > {0x3024a341, NULL}, /* PMC2430 - Pace 56 Voice Internal Modem */ > > > > > > Does the modem work with this addition? If so, I'll commit the change. > > > > > > > Yes :) > > > > sio2: at port 0x3e8-0x3ef irq 5 on > isa0 > > sio2: type 16550A > > Heh, it's already committed. (oops! :-) > > > Why did it work before though, under 3.x, without this line in sio.c? > > The PNP bios preconfigured it and left it laying around in port space, > so the old-style isa probes "found" it there. > > Under 4.0, the isa code is much more pnp centric. It was possible for an > isa probe to find a "stray" device and then for the PNP device id to match > and then fail due to resource conflicts. So, it disables the programmable > cards first so this double probing cannot happen. It also means that it > needs to know the PNP id's for supported pnp hardware. Making this more > user tweakable is on the TODO list. > Thanks for the explanation. > Cheers, > -Peter > -- Microsoft: Where do you want to go today? Linux: Where do you want to go tomorrow? BSD: Are you guys coming, or what? -Poster at LinuxWorld 2000 FreeBSD - The Power To Serve http://www.freebsd.org My Webpage http://ukug.uk.freebsd.org/~mark/ mailto:[EMAIL PROTECTED] http://www.radan.com To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: Modem no longer found after u/g to 4.0-current - help
Mark Ovens wrote: > On Sun, Mar 05, 2000 at 04:04:59PM +, Doug Rabson wrote: > > On Sun, 5 Mar 2000, Mark Ovens wrote: > > > > > On Sun, Mar 05, 2000 at 01:04:23PM +, Doug Rabson wrote: > > > > Could you send me the output of pnpinfo. I think we are missing a PnP I D > > > > in the sio driver. > > > > > > > > > > The line I've added to sio.c is: > > > > > > > > > {0x3024a341, NULL}, /* PMC2430 - Pace 56 Voice Internal Modem */ > > > > Does the modem work with this addition? If so, I'll commit the change. > > > > Yes :) > > sio2: at port 0x3e8-0x3ef irq 5 on isa0 > sio2: type 16550A Heh, it's already committed. (oops! :-) > Why did it work before though, under 3.x, without this line in sio.c? The PNP bios preconfigured it and left it laying around in port space, so the old-style isa probes "found" it there. Under 4.0, the isa code is much more pnp centric. It was possible for an isa probe to find a "stray" device and then for the PNP device id to match and then fail due to resource conflicts. So, it disables the programmable cards first so this double probing cannot happen. It also means that it needs to know the PNP id's for supported pnp hardware. Making this more user tweakable is on the TODO list. Cheers, -Peter To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Feedback: Minor problems u/g 3.4-STABLE -> 4.0
Firstly, a big thank-you to all the developers for their work on 4.x. I've just u/g 3.4-STABLE -> 4.0, following the instructions in /usr/source/UPDATING using sources cvsup'd 10:00GMT 4th March, and although it went quite smoothly came across a few minor problems which I'm posting here in case anyone is interested. 1. This message appeared 166 times during ``make buildworld'': /usr/libexec/ld-elf.so.1: Shared object "libc.so.4" not found It also caused config(8) on the new kernel to fail, but ldconfig -R /usr/obj/usr/src/lib/libc cured that. 2. UPDATING includes the following in the instructions to build the new kernel: cd src/usr.bin/genassym make depend all install clean cd ../../usr.sbin/config make depend all install clean however doing a ``make clean'' at this point then causes ``make installworld'' fail in those directories. 3. This probably won't affect most people but I'm including it so it's in the mail archives. I have a Diamond Fireport 40 SCSI card (NCR/Symbios 53c875j chip) and my 2nd (UW SCSI) disk is a single slice (although *not* dangerously dedicated) mounted as /usr. As this disk is not a boot device I had not enabled boot probing for it in the SCSI BIOS but under 2.2.x and 3.x it was still found by the old ncr driver. The new sym driver, however, failed to find the disk and caused a "device not configured" error from mount(8) which resulted in the boot-up dropping to single-user. It took me a while to find the cause (I thought it was a problem, or my mistake, when making the new device nodes for the disks). -- Microsoft: Where do you want to go today? Linux: Where do you want to go tomorrow? BSD: Are you guys coming, or what? -Poster at LinuxWorld 2000 FreeBSD - The Power To Serve http://www.freebsd.org My Webpage http://ukug.uk.freebsd.org/~mark/ mailto:[EMAIL PROTECTED] http://www.radan.com To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
ad0 Time Out
I've encountered a problem when booting my -current kernel. I'd include parts of the /var/log/messages, but it does not write to it when I boot up current. I installed the -current kernel, and made the devices for ad0 and ad1 including all the slices that I need, besides making all devices. I changed the /etc/fstab from wd to ad. I manually enter my root device when it's booting. Here's the problem I have: (I bet it's because of somethign stupid i did, or did not do...) It detects ad0 and ad1 allright, but then when it tries to mount root (ad0s3a) it gives me an error like the following: ad0: WRITE timed out. It then proceeds to crash. If anybody can help me I'd appreciate that, I know I don't have a whole lot of information, but I'll provide it if anybody needs specific things.. It's just a little harder to include it when it doesn't save it to the hard drive. Thanks, Jon To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: Modem no longer found after u/g to 4.0-current - help
On Sun, Mar 05, 2000 at 04:04:59PM +, Doug Rabson wrote: > On Sun, 5 Mar 2000, Mark Ovens wrote: > > > On Sun, Mar 05, 2000 at 01:04:23PM +, Doug Rabson wrote: > > > Could you send me the output of pnpinfo. I think we are missing a PnP ID > > > in the sio driver. > > > > > > > The line I've added to sio.c is: > > > > > > {0x3024a341, NULL}, /* PMC2430 - Pace 56 Voice Internal Modem */ > > Does the modem work with this addition? If so, I'll commit the change. > Yes :) sio2: at port 0x3e8-0x3ef irq 5 on isa0 sio2: type 16550A Why did it work before though, under 3.x, without this line in sio.c? > -- > Doug Rabson Mail: [EMAIL PROTECTED] > Nonlinear Systems Ltd.Phone: +44 181 442 9037 > > > > > To Unsubscribe: send mail to [EMAIL PROTECTED] > with "unsubscribe freebsd-questions" in the body of the message -- Microsoft: Where do you want to go today? Linux: Where do you want to go tomorrow? BSD: Are you guys coming, or what? -Poster at LinuxWorld 2000 FreeBSD - The Power To Serve http://www.freebsd.org My Webpage http://ukug.uk.freebsd.org/~mark/ mailto:[EMAIL PROTECTED] http://www.radan.com To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: Modem no longer found after u/g to 4.0-current - help
On Sun, 5 Mar 2000, Mark Ovens wrote: > On Sun, Mar 05, 2000 at 01:04:23PM +, Doug Rabson wrote: > > Could you send me the output of pnpinfo. I think we are missing a PnP ID > > in the sio driver. > > > > The line I've added to sio.c is: > > > {0x3024a341, NULL}, /* PMC2430 - Pace 56 Voice Internal Modem */ Does the modem work with this addition? If so, I'll commit the change. -- Doug Rabson Mail: [EMAIL PROTECTED] Nonlinear Systems Ltd. Phone: +44 181 442 9037 To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: current lockups
1. Is your computer overclocked? 2. Is the computer totally frozen? (i.e. scroll lock doesn't turn the light on) 3. Does similar load crash the box as well? (try make -j2 world) 4. Does it freeze in the same spot? 5. Is the computer not responding to pings? If you've answered yes to a good amount of these questions, there is a good chance that your processor(s) are overheating. Try improving the airflow to the case (But using a household fan isn't recommended due to EMI) -Dan Papasian <[EMAIL PROTECTED]> On Sat, Mar 04, 2000 at 11:50:10PM -0800, Arun Sharma wrote: > Compiling Mozilla with make -j 2 got -current to lock up, twice in > succession. I'm running a fairly recent snapshot (a week or two old) > on a Dual celeron box (BP6) with UDMA66 enabled. > > The kernel had DDB enabled. I was running X, but I didn't see any > signs of the kernel attempting to get into the debugger. > > Has this been fixed ? Is anyone interested in investigating ? > I'll post more info if I find anything. > > -Arun > > > To Unsubscribe: send mail to [EMAIL PROTECTED] > with "unsubscribe freebsd-current" in the body of the message To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
WaveLAN on RC2
Hi, I'm trying to get a Lucent WaveLAN card to work on a Dell Latitude CPxH450GT laptop running 4.0-Current RC2 (2214). As the generic kernel seem to include the wi driver from the start, I figured it would work if I just copied pccard.conf.sample to pccard.conf (removing all unnecessary entries), but it doesn't. When I boot the system I get: wi0: No irq?! pccardd[46]: driver allocation failed for Lucent Technologies (WaveLAN/IEEE): Device not configured pccardd[46]: pccardd started Then, if i remove and re-insert the card I get: wi0: No I/O space?! pccardd[46]: driver allocation I'm not sure wether this is a kernel config problem or a pccard.conf problem, I've tried to change IRQ:s etc in pccard.conf, but to no avail. Does anyone have an idea of what to try/change? Thanks in advance, /Daniel F. To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: [usb-bsd] Re: Unplugging the floppy (Support for USB floppydrives)
> I've had a look at the problem described by Guido and it is reprodicuble > here. Somehow a transfer is not descheduled when it should and this make > uhci_done bomb because of a stale pointer. > > So, do not unplug the drive without a drive until this has been fixed. ^ reboot. Sorry. Nick -- [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
Re: 3.x/4.x branch date?
Warner Losh wrote: > In message <[EMAIL PROTECTED]> Kris Ke nnaway writes: > : Can someone tell me the exact date that 4.x was split from 3.x? I couldn't > : seem to pin it down based on the CVS repository. > > Based on sys/i386/conf/files.i386: > 1/20/99 to 2/10/99 > Based on sys/conf/files: > 1/17/99 to 1/21/99 > > So I'd say it was somewhere between 1/20/99 and 1/21/99. Is that > close enough for you to "exact"? The branching proccess takes a > while, so I think this is as close as you may get. sys/conf/newvers.sh is (or was) the best spot to look at: revision 1.42 date: 1999/01/21 03:07:33; author: jkh; state: Exp; lines: +2 -2 This is now 4.0-current revision 1.41.2.1 date: 1999/01/21 05:33:18; author: jkh; state: Exp; lines: +2 -2 Now we're -STABLE Note that this is GMT. Cheers, -Peter To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: Modem no longer found after u/g to 4.0-current - help
On Sun, Mar 05, 2000 at 01:04:23PM +, Doug Rabson wrote: > On Sat, 4 Mar 2000, Mark Ovens wrote: > > > I've just done a relatively painless upgrade from 3.4-STABLE to 4.0, > > kudos to all he developers. However, one thing that doesn't work is > > causing me great problems. My ISA PnP modem is found as "unknown0", > > instead of sio2 no matter what I do: > > > > unknown0: at port > > 0x3e8-0x3ef irq 5 on isa0 > > > > The full dmseg output is at the end of this post. > > > > I've tried changing the PnP-OS seting in the BIOS, but it's no > > different. > > > > I thought I'd found the solution in LINT: > > > > # PnP `flags' (set via userconfig using pnp x flags y) > > # 0x1 disable probing of this device. Used to > > # prevent your modem from being attached > > # as a PnP modem. > > # > > > > which appears to be what is needed but ``boot -c'' and ``pnp 1 flags > > 0x1'' at the ``config>'' prompt gives: > > > > Invalid command or syntax. type '?' for help. > > > > Does anyone know the solution to this? This modem has worked > > flawlessly on this PC from 2.2.8 to 3.4-STABLE and it would be a shame > > to have to replace it now. > > Could you send me the output of pnpinfo. I think we are missing a PnP ID > in the sio driver. > The line I've added to sio.c is: {0x3024a341, NULL}, /* PMC2430 - Pace 56 Voice Internal Modem */ Output of pnpinfo: Checking for Plug-n-Play devices... Card assigned CSN #1 Vendor ID PMC2430 (0x3024a341), Serial Number 0x PnP Version 1.0, Vendor Version 0 Device Description: Pace 56 Voice Internal Plug & Play Modem Logical Device ID: PMC2430 0x3024a341 #0 Device supports I/O Range Check TAG Start DF I/O Range 0x3f8 .. 0x3f8, alignment 0x8, len 0x8 [16-bit addr] IRQ: 4 - only one type (true/edge) TAG Start DF I/O Range 0x2f8 .. 0x2f8, alignment 0x8, len 0x8 [16-bit addr] IRQ: 3 - only one type (true/edge) TAG Start DF I/O Range 0x3e8 .. 0x3e8, alignment 0x8, len 0x8 [16-bit addr] IRQ: 4 - only one type (true/edge) TAG Start DF I/O Range 0x2e8 .. 0x2e8, alignment 0x8, len 0x8 [16-bit addr] IRQ: 3 - only one type (true/edge) TAG Start DF I/O Range 0x3f8 .. 0x3f8, alignment 0x8, len 0x8 [16-bit addr] IRQ: 5 7 9 10 11 12 15 - only one type (true/edge) TAG Start DF I/O Range 0x2f8 .. 0x2f8, alignment 0x8, len 0x8 [16-bit addr] IRQ: 5 7 9 10 11 12 15 - only one type (true/edge) TAG Start DF I/O Range 0x3e8 .. 0x3e8, alignment 0x8, len 0x8 [16-bit addr] IRQ: 5 7 9 10 11 12 15 - only one type (true/edge) TAG Start DF I/O Range 0x2e8 .. 0x2e8, alignment 0x8, len 0x8 [16-bit addr] IRQ: 5 7 9 10 11 12 15 - only one type (true/edge) TAG Start DF I/O Range 0x100 .. 0xfff8, alignment 0x8, len 0x8 [16-bit addr] IRQ: 3 4 5 7 9 10 11 12 15 - only one type (true/edge) TAG End DF End Tag Successfully got 31 resources, 1 logical fdevs -- card select # 0x0001 CSN PMC2430 (0x3024a341), Serial Number 0x Logical device #0 IO: 0x03e8 0x03e8 0x03e8 0x03e8 0x03e8 0x03e8 0x03e8 0x03e8 IRQ 5 0 DMA 4 0 IO range check 0x00 activate 0x01 > -- > Doug Rabson Mail: [EMAIL PROTECTED] > Nonlinear Systems Ltd.Phone: +44 181 442 9037 > > > > > To Unsubscribe: send mail to [EMAIL PROTECTED] > with "unsubscribe freebsd-questions" in the body of the message -- Microsoft: Where do you want to go today? Linux: Where do you want to go tomorrow? BSD: Are you guys coming, or what? -Poster at LinuxWorld 2000 FreeBSD - The Power To Serve http://www.freebsd.org My Webpage http://ukug.uk.freebsd.org/~mark/ mailto:[EMAIL PROTECTED] http://www.radan.com To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
subscribe
To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: VMWare 2.0R broken - linux ioctl(13, 1260, *) not implemented
Ah! I found it! --- linux_ioctl.h.orig Mon Feb 28 11:50:23 2000 +++ linux_ioctl.h Mon Feb 28 11:24:08 2000 @@ -32,6 +32,25 @@ #define_LINUX_IOCTL_H_ /* + * disk + */ +#define LINUX_BLKROSET 0x125d +#define LINUX_BLKROGET 0x125e +#define LINUX_BLKRRPART0x125f +#define LINUX_BLKGETSIZE 0x1260 +#define LINUX_BLKFLSBUF0x1261 +#define LINUX_BLKRASET 0x1262 +#define LINUX_BLKRAGET 0x1263 +#define LINUX_BLKFRASET0x1264 +#define LINUX_BLKFRAGET0x1265 +#define LINUX_BLKSECTSET 0x1266 +#define LINUX_BLKSECTGET 0x1267 +#define LINUX_BLKSSZGET0x1268 + +#defineLINUX_IOCTL_DISK_MINLINUX_BLKROSET +#defineLINUX_IOCTL_DISK_MAXLINUX_BLKSSZGET + +/* * cdrom */ #defineLINUX_CDROMPAUSE0x5301 --- linux_ioctl.c.orig Mon Feb 28 11:50:07 2000 +++ linux_ioctl.c Mon Feb 28 11:11:09 2000 @@ -46,6 +46,7 @@ #include #include #include +#include #include @@ -55,12 +56,15 @@ #include #include +static linux_ioctl_function_t linux_ioctl_disk; static linux_ioctl_function_t linux_ioctl_cdrom; static linux_ioctl_function_t linux_ioctl_console; static linux_ioctl_function_t linux_ioctl_socket; static linux_ioctl_function_t linux_ioctl_sound; static linux_ioctl_function_t linux_ioctl_termio; +static struct linux_ioctl_handler disk_handler = +{ linux_ioctl_disk, LINUX_IOCTL_DISK_MIN, LINUX_IOCTL_DISK_MAX }; static struct linux_ioctl_handler cdrom_handler = { linux_ioctl_cdrom, LINUX_IOCTL_CDROM_MIN, LINUX_IOCTL_CDROM_MAX }; static struct linux_ioctl_handler console_handler = @@ -72,6 +76,7 @@ static struct linux_ioctl_handler termio_handler = { linux_ioctl_termio, LINUX_IOCTL_TERMIO_MIN, LINUX_IOCTL_TERMIO_MAX }; +DATA_SET(linux_ioctl_handler_set, disk_handler); DATA_SET(linux_ioctl_handler_set, cdrom_handler); DATA_SET(linux_ioctl_handler_set, console_handler); DATA_SET(linux_ioctl_handler_set, socket_handler); @@ -87,6 +92,23 @@ static TAILQ_HEAD(, handler_element) handlers = TAILQ_HEAD_INITIALIZER(handlers); + +static int +linux_ioctl_disk(struct proc *p, struct linux_ioctl_args *args) +{ + struct file *fp = p->p_fd->fd_ofiles[args->fd]; + int error; + struct disklabel dl; + + switch (args->cmd & 0x) { + case LINUX_BLKGETSIZE: + error = fo_ioctl(fp, DIOCGDINFO, (caddr_t)&dl, p); + if (error) + return (error); + return copyout(&(dl.d_secperunit), (caddr_t)args->arg, sizeof(dl.d_secperunit)); + } + return (ENOIOCTL); +} /* * termio related ioctls To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: VMWare 2.0R broken - linux ioctl(13, 1260, *) not implemented
Andrew Atrens wrote: > > A missing (not implemented) linux ioctl is breaking VMWare 2.0 - > > > linux: 'ioctl' fd=13, cmd=1260 ('^R',96) not implemented I implemented this ioctl. It's not as hard as you think. You do a DIOCGDINFO and return d_secperunit. But unfortunately, when I did this, a warning went away from the vmware log file, but vmware _still_ segfaulted immediately after, so I think there's more to it. Fortunately, this only affects raw disks. Virtual ones still work. I would attach my implementation for the missing ioctl below, but I can't find it. I send a copy to Marcel, but I I lost mine in my latest cvsup. :-( In the meantime, you can still fetch build 438 (I think), which is one of the 2.0 betas. It doesn't have this problem. Take a look at the freebsd-emulation mailing list archive. > > After rummaging around in the 2.3 kernel, I found the following in > `linux/include/linux/fs.h': > > /* the read-only stuff doesn't really belong here, but any other place is >probably as bad and I don't want to create yet another include file. */ > > #define BLKROSET _IO(0x12,93) /* set device read-only (0 = read-write) */ > #define BLKROGET _IO(0x12,94) /* get read-only status (0 = read_write) */ > #define BLKRRPART _IO(0x12,95) /* re-read partition table */ > #define BLKGETSIZE _IO(0x12,96) /* return device size */ > #define BLKFLSBUF _IO(0x12,97) /* flush buffer cache */ > #define BLKRASET _IO(0x12,98) /* Set read ahead for block device */ > #define BLKRAGET _IO(0x12,99) /* get current read ahead setting */ > #define BLKFRASET _IO(0x12,100)/* set filesystem (mm/filemap.c) read-ahead */ > #define BLKFRAGET _IO(0x12,101)/* get filesystem (mm/filemap.c) read-ahead */ > #define BLKSECTSET _IO(0x12,102)/* set max sectors per request (ll_rw_blk.c) */ > #define BLKSECTGET _IO(0x12,103)/* get max sectors per request (ll_rw_blk.c) */ > #define BLKSSZGET _IO(0x12,104)/* get block device sector size */ > > So it looks like BLKGETSIZE is the missing ioctl. > > I'm not sure how to fix this, because well, we don't have block devices, > the ATA driver doesn't support ioctls _or_ have a useful psize attribute > in its cdevsw struct. > > I naively thought I could use fstat() then devsw() to map the file > descriptor to a device, and then interrogate the device's psize. But that > goofy attempt just resulted in a kernel panic. :) Please don't dis me on > how stupid that was - instead tell me what I should do :) > > Seriously though, any help y'all could provide would be greatly > appreciated. :) > > Andrew. > > -- > > +-- > | Andrew Atrens Nortel Networks, Ottawa, Canada. | > | All opinions expressed are my own, not those of any employer. | >--+ > Berkeley had what we called "copycenter", which is "take it down > to the copy center and make as many copies as you want". > -- Kirk McKusick > +-- --+ > Bill Gates is a white Persian cat and a monocle away from becoming > another James Bond villain. "No Mr Bond, I expect you to upgrade." > -- Dennis Miller > +-- --+ > > To Unsubscribe: send mail to [EMAIL PROTECTED] > with "unsubscribe freebsd-current" in the body of the message To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: Modem no longer found after u/g to 4.0-current - help
On Sat, 4 Mar 2000, Mark Ovens wrote: > I've just done a relatively painless upgrade from 3.4-STABLE to 4.0, > kudos to all he developers. However, one thing that doesn't work is > causing me great problems. My ISA PnP modem is found as "unknown0", > instead of sio2 no matter what I do: > > unknown0: at port > 0x3e8-0x3ef irq 5 on isa0 > > The full dmseg output is at the end of this post. > > I've tried changing the PnP-OS seting in the BIOS, but it's no > different. > > I thought I'd found the solution in LINT: > > # PnP `flags' (set via userconfig using pnp x flags y) > # 0x1 disable probing of this device. Used to > # prevent your modem from being attached > # as a PnP modem. > # > > which appears to be what is needed but ``boot -c'' and ``pnp 1 flags > 0x1'' at the ``config>'' prompt gives: > > Invalid command or syntax. type '?' for help. > > Does anyone know the solution to this? This modem has worked > flawlessly on this PC from 2.2.8 to 3.4-STABLE and it would be a shame > to have to replace it now. Could you send me the output of pnpinfo. I think we are missing a PnP ID in the sio driver. -- Doug Rabson Mail: [EMAIL PROTECTED] Nonlinear Systems Ltd. Phone: +44 181 442 9037 To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Unplugging the floppy (Re: Support for USB floppy drives)
I've had a look at the problem described by Guido and it is reprodicuble here. Somehow a transfer is not descheduled when it should and this make uhci_done bomb because of a stale pointer. So, do not unplug the drive without a drive until this has been fixed. Nick On Fri, 3 Mar 2000, Guido van Rooij wrote: > On Thu, Mar 02, 2000 at 08:32:00PM +, Nick Hibma wrote: > > > > camcontrol rescan 0 > > dd if=/dev/zero of=/dev/da0 bs=10k count=100 > > disklabel -r -w da0 fd1440 > > newfs /dev/da0 > > > > Keep me posted on the results or any problems you have. > > > > Bij deze: > > plug in floppy drive op een vaio. > camcontrol rescan 0 > unplug de floppy drive > wacht 2-3 seconden > panic...en wel zodanig erg dat hij geen dump meer kan maken > > -Guido > -- [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
Re: VMWare 2.0R broken - linux ioctl(13, 1260, *) not implemented
At Sun, 5 Mar 2000 01:32:39 -0500 (EST), Andrew Atrens <[EMAIL PROTECTED]> wrote: > > A missing (not implemented) linux ioctl is breaking VMWare 2.0 - > > > linux: 'ioctl' fd=13, cmd=1260 ('^R',96) not implemented > > > After rummaging around in the 2.3 kernel, I found the following in > `linux/include/linux/fs.h': Hmm? I'm using Win98 (Japanese), Win2K (Japanese), and FreeBSD-current on vmware 2.0 with linux emulator of yesterday's -current without any problems. Am I wrong? --- Tatsumi Hosokawa [EMAIL PROTECTED] To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Modem no longer found after u/g to 4.0-current - help
I've just done a relatively painless upgrade from 3.4-STABLE to 4.0, kudos to all he developers. However, one thing that doesn't work is causing me great problems. My ISA PnP modem is found as "unknown0", instead of sio2 no matter what I do: unknown0: at port 0x3e8-0x3ef irq 5 on isa0 The full dmseg output is at the end of this post. I've tried changing the PnP-OS seting in the BIOS, but it's no different. I thought I'd found the solution in LINT: # PnP `flags' (set via userconfig using pnp x flags y) # 0x1 disable probing of this device. Used to # prevent your modem from being attached # as a PnP modem. # which appears to be what is needed but ``boot -c'' and ``pnp 1 flags 0x1'' at the ``config>'' prompt gives: Invalid command or syntax. type '?' for help. Does anyone know the solution to this? This modem has worked flawlessly on this PC from 2.2.8 to 3.4-STABLE and it would be a shame to have to replace it now. TIA BTW, please Cc: me diractly as I'm not subscribed to any lists under this temporary Internet account, thanks. dmesg output: Copyright (c) 1992-2000 The FreeBSD Project. Copyright (c) 1982, 1986, 1989, 1991, 1993 The Regents of the University of California. All rights reserved. FreeBSD 4.0-CURRENT #3: Sat Mar 4 19:45:35 GMT 2000 root@parish:/usr/src/sys/compile/PARISH Timecounter "i8254" frequency 1193182 Hz Timecounter "TSC" frequency 233864767 Hz CPU: AMD-K6tm w/ multimedia extensions (233.86-MHz 586-class CPU) Origin = "AuthenticAMD" Id = 0x562 Stepping = 2 Features=0x8001bf AMD Features=0x400<> real memory = 67108864 (65536K bytes) avail memory = 61726720 (60280K bytes) Preloaded elf kernel "kernel" at 0xc0311000. Preloaded elf module "vesa.ko" at 0xc031109c. Preloaded userconfig_script "/kernel.config" at 0xc0311138. VESA: v2.0, 4096k memory, flags:0x0, mode table:0xc030e102 (122) VESA: ATI MACH64 md0: Malloc disk npx0: on motherboard npx0: INT 16 interface pcib0: on motherboard pci0: on pcib0 isab0: at device 7.0 on pci0 isa0: on isab0 pci0: at 7.1 pci0: at 7.2 irq 11 chip1: port 0x5f00-0x5f0f at device 7.3 on pci0 pci0: at 8.0 sym0: <875> port 0x6600-0x66ff mem 0xe1002000-0xe1002fff,0xe1001000-0xe10010ff irq 10 at device 9.0 on pci0 sym0: Symbios NVRAM, ID 7, Fast-20, SE, parity checking sym0: open drain IRQ line driver, using on-chip SRAM sym0: SCAN AT BOOT disabled for targets 1 2 3 4 5 9 10 11 12 13 14 15. xl0: <3Com 3c900-COMBO Etherlink XL> port 0x6700-0x673f irq 9 at device 10.0 on pci0 xl0: Ethernet address: 00:60:08:73:4e:e0 xl0: selecting 10baseT transceiver, half duplex pcm0: port 0x6800-0x683f irq 11 at device 11.0 on pci0 fdc0: 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: at port 0x60-0x6f on isa0 atkbd0: irq 1 on atkbdc0 psm0: irq 12 on atkbdc0 psm0: model Generic PS/2 mouse, device ID 0 vga0: at port 0x3c0-0x3df iomem 0xa-0xb on isa0 sc0: on isa0 sc0: VGA <16 virtual consoles, flags=0x200> sio0 at port 0x3f8-0x3ff irq 4 flags 0x10 on isa0 sio0: type 16550A sio1 at port 0x2f8-0x2ff irq 3 on isa0 sio1: type 16550A sio2: configured irq 5 not in bitmap of probed irqs 0 ppc0: at port 0x378-0x37f irq 7 on isa0 ppc0: Generic chipset (NIBBLE-only) in COMPATIBLE mode ppbus0: IEEE1284 device found /NIBBLE/ECP Probing for PnP devices on ppbus0: ppbus0: MLC,PCL,PML plip0: on ppbus0 lpt0: on ppbus0 lpt0: Interrupt-driven port ppi0: on ppbus0 unknown0: at port 0x3e8-0x3ef irq 5 on isa0 Waiting 10 seconds for SCSI devices to settle (noperiph:sym0:0:-1:-1): SCSI BUS reset delivered. Mounting root from ufs:/dev/da0s3a cd0 at sym0 bus 0 target 6 lun 0 cd0: Removable CD-ROM SCSI-2 device cd0: 10.000MB/s transfers (10.000MHz, offset 16) cd0: Attempt to query device size failed: NOT READY, Medium not present da0 at sym0 bus 0 target 0 lun 0 da0: Fixed Direct Access SCSI-2 device da0: 40.000MB/s transfers (20.000MHz, offset 15, 16bit) da0: 4134MB (8467200 512 byte sectors: 255H 63S/T 527C) da1 at sym0 bus 0 target 8 lun 0 da1: Fixed Direct Access SCSI-2 device da1: 40.000MB/s transfers (20.000MHz, offset 15, 16bit), Tagged Queueing Enabled da1: 4357MB (8925000 512 byte sectors: 255H 63S/T 555C) -- Q. How many Software Engineers does it take to change a light bulb? A. None. It's a hardware problem FreeBSD - The Power To Serve http://www.freebsd.org My Webpage http://ukug.uk.freebsd.org/~mark To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message