latest 4.0 snapshot breaks tcpdump
I just installed the latest 4.0 snap off of ftp2.freebsd.org. Didn't install the DES libraries... I get this when trying to run tcpdump on the system: unstable# tcpdump /usr/libexec/ld-elf.so.1: Shared object "libcrypto.so.1" not found enjoy -- Jason Garman http://web.wedgie.org/ Student, University of Maryland [EMAIL PROTECTED] From fortune(1): Whois: JAG145 "... Had this been an actual emergency, we would have fled in terror, and you would not have been informed." To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: latest 4.0 snapshot breaks tcpdump
On Mon, 13 Mar 2000, Jason Garman wrote: I just installed the latest 4.0 snap off of ftp2.freebsd.org. Didn't install the DES libraries... I get this when trying to run tcpdump on the system: unstable# tcpdump /usr/libexec/ld-elf.so.1: Shared object "libcrypto.so.1" not found Hmm. I think you'll find several other things are broken in the same way - the crypto collection has effectively become mandatory thesedays. For example, ppp and pppd both link against libcrypto as well, and I can't think of an easy way to make the same binary work correctly with and without libcrypto. Either we make a binary which doesn't require libcrypto, in which case there's no way for someone to obtain the full functionality from a binary install, or we make one which does and people have to install the crypto collection to use it. It's a different matter if you compile from source yourself, but with a binary distribution you only have one possible set of binaries and can't mix and match dependencies. IMO (and I suggested this the other day), we should make the crypto collection mandatory, and have sysinstall ask a question about whether to point the libcrypt symlinks at libscrypt or libdescrypt (libdescrypt is the only real reason people wouldn't want to install the crypto collection). 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: latest 4.0 snapshot breaks tcpdump
IMO (and I suggested this the other day), we should make the crypto collection mandatory, and have sysinstall ask a question about whether to point the libcrypt symlinks at libscrypt or libdescrypt (libdescrypt is I'm still waiting for your diffs which do this. :) - Jordan To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: Sound driver
On Sun, 12 Mar 2000, Ron 'The InSaNe One' Rosson wrote: I am running CURRENT as of last week. I seem to be only able to get my sound to work when I use: option PNPBIOS device pcm0 Here is the dmesg output: unknown9: ESS0009 at port 0x800-0x807 on isa0 sbc0: ESS ES1879 at port 0x220-0x22f,0x388-0x38b,0x330-0x331 irq 5 drq 1,5 on isa0 pcm0: SB DSP 3.01 (ESS mode) on sbc0 unknown10: ESS0001 at port 0x201 on isa0 I would like to get rid of all the unknowns caused by the PNPBIOS option. If anyone has any ideas I am game to try. Sorry for the cross-post Don't worry about the unknowns. They are placeholders for attaching other standard devices (e.g. keyboard, mouse etc). Not all of the drivers were converted for various reasons but later releases will use these entries. -- 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: latest 4.0 snapshot breaks tcpdump
On Mon, 13 Mar 2000, Jordan K. Hubbard wrote: IMO (and I suggested this the other day), we should make the crypto collection mandatory, and have sysinstall ask a question about whether to point the libcrypt symlinks at libscrypt or libdescrypt (libdescrypt is I'm still waiting for your diffs which do this. :) Well yeah, that's fun to say, but my days have been literally completely full with getting other things ready for 4.0, without trying to figure out sysinstall on top of it all. All I can do is warn you to expect bug reports about this once people start upgrading to 4.0. 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: YA ssh question (ssh-askpass?)
On Tue, 7 Mar 2000, Richard J Kuhns wrote: But then I'm back to my original question/problem: how to get ssh to ask for a password using ssh-askpass. I've looked through the code (a little); how would you feel about a patch to openssh/readpass.c that caused it to call ssh-askpass if there's no controlling tty but DISPLAY is set? That would probably be something the openssh guys would like. 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: latest 4.0 snapshot breaks tcpdump
IMO (and I suggested this the other day), we should make the crypto collection mandatory, and have sysinstall ask a question about whether to point the libcrypt symlinks at libscrypt or libdescrypt (libdescrypt is I'm still waiting for your diffs which do this. :) Well yeah, that's fun to say, but my days have been literally completely full with getting other things ready for 4.0, without trying to figure out sysinstall on top of it all. All I can do is warn you to expect bug reports about this once people start upgrading to 4.0. Can't it be handled the same way init, ppp and a few others are? The binary shipped in the bin distribution is compiled/linked without crypto, but then a version compiled/linked with it is included in the crypto distribution. John -- John Hay -- [EMAIL PROTECTED] To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: latest 4.0 snapshot breaks tcpdump
On Mon, 13 Mar 2000, John Hay wrote: Can't it be handled the same way init, ppp and a few others are? The binary shipped in the bin distribution is compiled/linked without crypto, but then a version compiled/linked with it is included in the crypto distribution. Hmm. I didn't know that - probably it could. The question is then whether make release correctly compiles everything without libcrypto (the original poster suggests not). 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: latest 4.0 snapshot breaks tcpdump
On Mon, 13 Mar 2000, Kris Kennaway wrote:
Hmm. I didn't know that - probably it could. The question is then whether
make release correctly compiles everything without libcrypto (the original
poster suggests not).
Looks like it needs the following patch:
Index: usr.sbin/tcpdump//tcpdump/Makefile
===
RCS file: /home/ncvs/src/usr.sbin/tcpdump/tcpdump/Makefile,v
retrieving revision 1.25
diff -u -r1.25 Makefile
--- usr.sbin/tcpdump//tcpdump/Makefile 2000/03/02 13:27:25 1.25
+++ usr.sbin/tcpdump//tcpdump/Makefile 2000/03/13 10:54:05
@@ -21,7 +21,7 @@
CLEANFILES+= version.c
DPADD+=${LIBL} ${LIBPCAP}
LDADD+=-ll -lpcap
-.if exists(../../../crypto) !defined(NOSECURE) !defined(NO_OPENSSL)
+.if exists(../../../crypto) !defined(NOCRYPT) !defined(NOSECURE)
+!defined(NO_OPENSSL) !defined(RELEASE_CRUNCH)
DPADD+= ${LIBCRYPTO}
LDADD+= -lcrypto
CFLAGS+= -I${DESTDIR}/usr/include/openssl -DCRYPTO -DHAVE_LIBCRYPTO -DHAVE_RC5_H
-DHAVE_CAST_H
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: latest 4.0 snapshot breaks tcpdump
It also needs DISTRIBUTION=crypto inside that .if so that it will end up
in the crypto distribution. And maybe the exists(../../../crypto should
be exists(${.CURDIR}/../../secure) like the ppp/Makefile?
Hmm. I didn't know that - probably it could. The question is then whether
make release correctly compiles everything without libcrypto (the original
poster suggests not).
Looks like it needs the following patch:
Index: usr.sbin/tcpdump//tcpdump/Makefile
===
RCS file: /home/ncvs/src/usr.sbin/tcpdump/tcpdump/Makefile,v
retrieving revision 1.25
diff -u -r1.25 Makefile
--- usr.sbin/tcpdump//tcpdump/Makefile2000/03/02 13:27:25 1.25
+++ usr.sbin/tcpdump//tcpdump/Makefile2000/03/13 10:54:05
@@ -21,7 +21,7 @@
CLEANFILES+= version.c
DPADD+= ${LIBL} ${LIBPCAP}
LDADD+= -ll -lpcap
-.if exists(../../../crypto) !defined(NOSECURE) !defined(NO_OPENSSL)
+.if exists(../../../crypto) !defined(NOCRYPT) !defined(NOSECURE)
!defined(NO_OPENSSL) !defined(RELEASE_CRUNCH)
DPADD+= ${LIBCRYPTO}
LDADD+= -lcrypto
CFLAGS+= -I${DESTDIR}/usr/include/openssl -DCRYPTO -DHAVE_LIBCRYPTO -DHAVE_RC5_H
-DHAVE_CAST_H
In God we Trust -- all others must submit an X.509 certificate.
-- Charles Forsythe [EMAIL PROTECTED]
John
--
John Hay -- [EMAIL PROTECTED]
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message
B_WRITE cleanup patch, please test!
http://phk.freebsd.dk/misc/b_iocmd.patch B_WRITE is bogusly defined as zero, which is a perfect candidate for coding and logic mistakes, we saw the most recent victim of this bogosity as recently as a few days ago. This patch moves the "io-command" aspect of the b_flags into a new struct buf field called b_iocmd. This patch is the first step towards the stackable BIO system as sketched out on http://www.freebsd.org/~phk/Geom/ Please test review. -- 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
Re: Sound driver
Ron 'The InSaNe One' Rosson wrote: I am running CURRENT as of last week. I seem to be only able to get my sound to work when I use: option PNPBIOS device pcm0 Here is the dmesg output: unknown9: ESS0009 at port 0x800-0x807 on isa0 sbc0: ESS ES1879 at port 0x220-0x22f,0x388-0x38b,0x330-0x331 irq 5 drq 1,5 on isa0 pcm0: SB DSP 3.01 (ESS mode) on sbc0 unknown10: ESS0001 at port 0x201 on isa0 I would like to get rid of all the unknowns caused by the PNPBIOS option. If anyone has any ideas I am game to try. Try adding "device joy" to your configuration file. The ESS0001 looks like a game/joystick port. Someone might need to add device ID to the driver though. Jim Bloom [EMAIL PROTECTED] To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
[sound] PCI ESS support
Ok, being a newbie to FreeBSD, I'm trying to get my laptop (WinBook XL2)
sound working under -CURRENT. If someone could point me to the relavent
docs, I'd be happy Here is what I'm finding:
dmesg reports:
chip2: ESS Technology Maestro 2E Audio controller port 0xec00-0xecff irq 5 at
device 9.0 on pci0
chip3: ESS Technology Maestro 2E Audio controller port 0xee00-0xeeff irq 5 at
device 9.1 on pci0
but no combination of device {pcm,pcm0,sbc,sbc0} (that I've found) result in
sound devices.
I also find these in my dmesg output which may be related in some way:
unknown0: PNP0c01 at iomem 0-0x9fbff,0x9fc00-0x9,0xe-0xf,0x10-
0x3fe,0x3ff-0x3ff7fff,0x3ff8000-0x3ff,0xfec0-0xfec00fff,0xfee000
00-0xfee00fff on isa0
unknown: PNP can't assign resources
unknown1: PNP0200 at port 0-0xf,0x80-0x90,0x94-0x9f,0xc0-0xdf drq 4 on isa0
unknown2: PNP0100 at port 0x40-0x43 irq 0 on isa0
unknown3: PNP0b00 at port 0x70-0x71 irq 8 on isa0
unknown: PNP0303 can't assign resources
unknown: PNP0800 can't assign resources
unknown4: PNP0c04 at port 0xf0-0xff irq 13 on isa0
unknown5: PNP0c02 at port 0x4d0-0x4d1,0xcf8-0xcff,0x440-0x44f,0x400-0x43f,0x38
10-0x384f,0x10,0x11,0x12,0x13,0x14,0x15,0x16,0x17 on isa0
unknown: PNP0c02 can't assign resources
unknown: PNP0501 can't assign resources
unknown: PNP0400 can't assign resources
unknown: PNP0700 can't assign resources
unknown6: PNP0e03 at port 0x3e1-0x3e2 on isa0
unknown: PNP0f13 can't assign resources
unknown7: PNP0a03 on isa0
AlanC
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message
Re: B_WRITE cleanup patch, please test!
It is most ironic that of course you were the loudest supporter of SOS when he ripped out all my code that did EXACTLY all this. (I might add that this was done without any warning to me. The The commit messages being my first notice). It was fully working and quite a few people were running it at the time. It looks like what you are suggesting is pretty much exactly what I had running so I certainly agree with it. I just am still still smarting from the fact that it was apparently deleted simply because it was written by me. It certainly ended most of my direct involvement with freebsd other than through my work so I guess it had it's desired effect. Poul-Henning Kamp wrote: http://phk.freebsd.dk/misc/b_iocmd.patch B_WRITE is bogusly defined as zero, which is a perfect candidate for coding and logic mistakes, we saw the most recent victim of this bogosity as recently as a few days ago. This patch moves the "io-command" aspect of the b_flags into a new struct buf field called b_iocmd. This patch is the first step towards the stackable BIO system as sketched out on http://www.freebsd.org/~phk/Geom/ Please test review. -- 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! Unless of course it wasn't written in Denmark To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message -- __--_|\ Julian Elischer / \ [EMAIL PROTECTED] ( OZ) World tour 2000 --- X_.---._/ presently in: Perth v To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: B_WRITE cleanup patch, please test!
Poul-Henning Kamp wrote: This patch is the first step towards the stackable BIO system as sketched out on http://www.freebsd.org/~phk/Geom/ you don't mention how you plan to get around the problem that arbitrarily stacking devices means arbitrarily allocating minor numbers. I used devfs to do this. -- __--_|\ Julian Elischer / \ [EMAIL PROTECTED] ( OZ) World tour 2000 --- X_.---._/ presently in: Perth v To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: MAX_UID ?
On Sun, Mar 12, 2000 at 05:51:17PM -0800, John Polstra wrote: In article [EMAIL PROTECTED], Giorgos Keramidas [EMAIL PROTECTED] wrote: On Sun, Mar 12, 2000 at 05:59:09AM +, Paul Richards wrote: Are expressions like ((uid_t)0-1) portable/safe ? Maybe that's a better way of approaching this. To get the all-1's number, maybe it's better to use ((uid_t)~0), but that is a rather controversial topic anyway. That works, but on machines like the Alpha where longs are bigger than ints it only works by virtue of sign extension. Our existing headers seem to prefer ((uid_t)0-1). That's what is used in the i386's machine/limits.h. My bummer, I thought the definition was the same in /sys/sys/types.h and in /usr/include/sys/types.h -- and there I could see: % cd /sys ; grep uid sys/* | grep type sys/conf.h:typedef void devfs_create_t __P((dev_t dev, uid_t uid... sys/types.h:typedef u_int32_t uid_t; /* user id */ % cd /usr/include ; grep uid sys/* | grep type sys/conf.h:typedef void devfs_create_t __P((dev_t dev, uid_t uid... sys/types.h:typedef u_int32_t uid_t; /* user id */ and I mistakenly assumed that both x86 and alpha's use uid_t's of 32 bits. What did I miss? - Giorgos To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: B_WRITE cleanup patch, please test!
It seems Julian Elischer wrote: It is most ironic that of course you were the loudest supporter of SOS when he ripped out all my code that did EXACTLY all this. (I might add that this was done without any warning to me. The The commit messages being my first notice). It was fully working and quite a few people were running it at the time. I think there are at least two wildly different oppinions on that Julian, besides this was not my/phk's decision alone. It looks like what you are suggesting is pretty much exactly what I had running so I certainly agree with it. I just am still still smarting from the fact that it was apparently deleted simply because it was written by me. It certainly ended most of my direct involvement with freebsd other than through my work so I guess it had it's desired effect. I'll let phk comment on that one :) -Søren To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: Bug: atapi-cd ioctls called in cdcontrol
After discussion with Soren off list, I'm bringing this onlist :) Machine: K6/2-450 on Asus P5A with 128 Meg PC133 (runnin 100) ram, Western Digital Caviar AC23400L 4.3 gig, Sony DDU220E dvd rom OS: FreeBSD 3.x-STABLE for much time, switch to 4.0-CURRENT ~month and a half ago?, been updating and building/installing worlds now and again since Problem: Drive does not support (or claims to not support) the LBA access methods. I'm not certain if there's some little tweak that's wrong in the bios, or if the acd driver's confused, or if the drivey (Sony DDU220E) generally hates LBA. Problem _did not exist_ under 3.x-STABLE that I recall. (read as, maybe somone should point me to how to debug this really low level ;) Specifically, I could go into cdcontrol and attempt to play by block, track, disk in general, etc. and it would fail with an i/o error in the program, and a PLAY_BIG -- ILLEGAL REQUEST on console. WHen forcing it to play by the MSF methods (specify the Minute Second and Frame to start and end with) it worked. Further, I did a hack in atapi-cd.c to translate the lba PLAYBLOCKS (I think) to translate to MSF and use PLAY_MSF instead. That, too, worked. Three things) 1) Soren or some other highly educated person, can you give me a hand (read as: give me insight into where to look) to see where the lba would be failing so that it might be fixed 2) If one fails (which I don't see as happening since the drive worked under 3.x-Stable just fine ;), it would be really nice if the kernel would handle this and say, 'Oh, he wants to use LBA playing methods which won't work on an MSF drive... We need to translate and call the MSF.' I don't like this, and I take from the sound of it, Soren didn't either (he mentioned that there wasn't a real good soloution). 3) If cdcontrol allows switching from msf (default) to lba can we have this better documented I don't really know what this switches between. I certainly _want_ cdcontrol to play MSF since it can't LBA, but this doesn't do that. (Note: The reason I suggest having the kernel do the translation to MSF is that it's not going to be easy/possible to ask every program to check it themselves ***sigh***) j. PS dmesg w/ ACDDEBUG 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 #10: Sun Mar 12 19:37:43 EST 2000 [EMAIL PROTECTED]:/net/dragonstar/project/FreeBSD/4.0-CURRENT/src/sys/compile/KNIGHTSTAR Timecounter "i8254" frequency 1193182 Hz CPU: AMD-K6(tm) 3D processor (451.02-MHz 586-class CPU) Origin = "AuthenticAMD" Id = 0x58c Stepping = 12 Features=0x8021bfFPU,VME,DE,PSE,TSC,MSR,MCE,CX8,PGE,MMX AMD Features=0x8800SYSCALL,3DNow! real memory = 134201344 (131056K bytes) config q avail memory = 126963712 (123988K bytes) Preloaded elf kernel "kernel" at 0xc030f000. Preloaded userconfig_script "/boot/kernel.conf" at 0xc030f09c. VESA: v2.0, 8192k memory, flags:0x0, mode table:0xc02b9c42 (122) VESA: ATI MACH64 md0: Malloc disk npx0: math processor on motherboard npx0: INT 16 interface apm0: APM BIOS on motherboard apm: found APM BIOS v1.2, connected at v1.2 pcib0: AcerLabs M1541 (Aladdin-V) PCI host bridge on motherboard pci0: PCI bus on pcib0 pcib1: AcerLabs M5243 PCI-PCI bridge at device 1.0 on pci0 pci1: PCI bus on pcib1 chip1: AcerLabs M15x3 Power Management Unit at device 3.0 on pci0 isab0: AcerLabs M1533 portable PCI-ISA bridge at device 7.0 on pci0 isa0: ISA bus on isab0 xl0: 3Com 3c905B-TX Fast Etherlink XL port 0xd800-0xd87f mem 0xdf00-0xdf7f irq 9 at device 9.0 on pci0 xl0: Ethernet address: 00:10:5a:05:6a:43 miibus0: MII bus on xl0 xlphy0: 3Com internal media interface on miibus0 xlphy0: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, auto pci0: ATI Mach64-GP graphics accelerator at 10.0 irq 9 pci0: unknown card (vendor=0x1105, dev=0x8300) at 12.0 irq 10 atapci0: AcerLabs Aladdin ATA33 controller port 0xd000-0xd00f irq 0 at device 15.0 on pci0 ata0: at 0x1f0 irq 14 on atapci0 ata1: at 0x170 irq 15 on atapci0 fdc0: NEC 72065B or clone at port 0x3f0-0x3f5,0x3f7 irq 6 drq 2 on isa0 fdc0: FIFO enabled, 8 bytes threshold fd0: 1440-KB 3.5" drive on fdc0 drive 0 atkbdc0: keyboard controller (i8042) at port 0x60-0x6f on isa0 atkbd0: AT Keyboard irq 1 on atkbdc0 psm0: PS/2 Mouse irq 12 on atkbdc0 psm0: model Generic PS/2 mouse, device ID 0 vga0: Generic ISA VGA at port 0x3c0-0x3df iomem 0xa-0xb on isa0 sc0: System console 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 ppc0: Parallel port at port 0x378-0x37f irq 7 on isa0 ppc0: Generic chipset (EPP/NIBBLE) in COMPATIBLE mode ppi0: Parallel I/O on ppbus0 lpt0: Printer on ppbus0 lpt0: Interrupt-driven port plip0: PLIP network interface on ppbus0 unknown: PNP0400 can't assign resources unknown:
Re: IPv6 setup...
On Mon, 13 Mar 2000 10:22:08 +0900, Yoshinobu Inoue [EMAIL PROTECTED] said:
echo 24.113.25.85 | sed -e s/"\."/" "/g | awk '{$5 = $1*256 + $2; $6 = $3*256 +
$4; printf "2002:%x:%x:\n", $5, $6}'
Or, without only one extra process:
myaddr=24.113.25.85
OIFS="$IFS"
IFS=".$IFS"
set $myaddr
IFS="$OIFS"
printf "2002:%x:%x:\n" $(($1 * 256 + $2)) $(($3 * 256 + $4))
-GAWollman
--
Garrett A. Wollman | O Siem / We are all family / O Siem / We're all the same
[EMAIL PROTECTED] | O Siem / The fires of freedom
Opinions not those of| Dance in the burning flame
MIT, LCS, CRS, or NSA| - Susan Aglukark and Chad Irschick
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message
pccard.conf.sample ? Is that a great name ???
Am I the only one who thinks that having a .sample file containing active settings is a not so great ting ? Why not simply rename it to pccard.conf, pccard.conf.default or default/pccard.conf --- Nicolai Petri Software-developer To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
suggestion: a g77 - f77 link
Hello,
While trying to compile Scilab-2.5 (the math/Scilab port is outdated),
I found that the "configure" script, when instructed to use the
GNU Fortran compiler, searchs for "g77". Unfortunately, this compiler
is installed as /usr/bin/f77. The solution is simple: "ln f77 g77",
but I think that the "g77" link should be standard, since it's coherent
with the existence of the "cc" and "gcc" links.
I think that this patch could do the trick:
-- BEGIN
--- gnu/usr.bin/cc/f77/Makefile.origMon Jan 24 21:12:05 2000
+++ gnu/usr.bin/cc/f77/Makefile Mon Mar 13 16:53:11 2000
@@ -7,6 +7,9 @@
PROG= f77
SRCS= gcc.c g77spec.c version.c
+LINKS= ${BINDIR}/f77 ${BINDIR}/g77
+MLINKS= f77.1 g77.1
+
DPADD+=${LIBCC_INT} ${LIBCC_FBSD}
LDADD+=${LIBCC_INT} ${LIBCC_FBSD}
END
Cheers,
-- JMA
---
José Mª Alcaide | mailto:[EMAIL PROTECTED]
Universidad del País Vasco | mailto:[EMAIL PROTECTED]
Dpto. de Electricidad y Electrónica | http://www.we.lc.ehu.es/~jose
Facultad de Ciencias - Campus de Lejona | Tel.: +34-946012479
48940 Lejona (Vizcaya) - SPAIN | Fax: +34-946013071
---
"Beware of Programmers who carry screwdrivers" -- Leonard Brandwein
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message
Re: B_WRITE cleanup patch, please test!
This patch is the first step towards the stackable BIO system as sketched out on http://www.freebsd.org/~phk/Geom/ Please test review. There's no code to test- it's just a sketch. It's fine as a start, but it's important that you clarify the role of node device drivers in informing the geometry device about what's what (to get information about physical limits) and how errors are to be flagged (if an out of range request comes floating thru). Presumably the latter is just marking a transaction with B_ERROR and setting b_errno to something specific that would say that the block is out of range (insert argument over 'correct' errno here), and that the range involved is the physical device limit (and what about commands that overlap the end of the device?). Presumably the former, if to give the geometry stack something worthwhile to chew on, can handle the case of devices that resize and devices where, unlike most devices currently, geometry really does matter. -matt To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: pccard.conf.sample ? Is that a great name ???
On Mon, 13 Mar 2000, Nicolai Petri (ML) wrote: Am I the only one who thinks that having a .sample file containing active settings is a not so great ting ? Why not simply rename it to pccard.conf, pccard.conf.default or default/pccard.conf I assumed that the .sample was to emphasize the need to customize it as needed and save it as pccard.conf (where pccardd expects to find it). While not intuitive for new users, it is necissary so that upgrades can modify the pccard.conf.sample file without disturbing and localizations in pccard.conf. See manpath.config.sample for another example of this logic. It doesn't strike me as a candidate for /etc/defaults/ unless it is made to include /etc/pccard.conf if it exists and override and config entries that are duplicated (i.e. if it were truly just defaults that could be overridden). In other words, it may not be intuitive, but it fits the existing protocol. Kelly -- Kelly Yancey - [EMAIL PROTECTED] - Richmond, VA Analyst / E-business Development, Bell Industries http://www.bellind.com/ Maintainer, BSD Driver Database http://www.posi.net/freebsd/drivers/ Coordinator, Team FreeBSDhttp://www.posi.net/freebsd/Team-FreeBSD/ To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: MAX_UID ?
In article [EMAIL PROTECTED], Giorgos Keramidas [EMAIL PROTECTED] wrote: On Sun, Mar 12, 2000 at 05:51:17PM -0800, John Polstra wrote: In article [EMAIL PROTECTED], Giorgos Keramidas [EMAIL PROTECTED] wrote: On Sun, Mar 12, 2000 at 05:59:09AM +, Paul Richards wrote: Are expressions like ((uid_t)0-1) portable/safe ? Maybe that's a better way of approaching this. To get the all-1's number, maybe it's better to use ((uid_t)~0), but that is a rather controversial topic anyway. That works, but on machines like the Alpha where longs are bigger than ints it only works by virtue of sign extension. Our existing headers seem to prefer ((uid_t)0-1). That's what is used in the i386's machine/limits.h. My bummer, I thought the definition was the same in /sys/sys/types.h and in /usr/include/sys/types.h -- and there I could see: % cd /sys ; grep uid sys/* | grep type sys/conf.h:typedef void devfs_create_t __P((dev_t dev, uid_t uid... sys/types.h:typedef u_int32_t uid_t; /* user id */ % cd /usr/include ; grep uid sys/* | grep type sys/conf.h:typedef void devfs_create_t __P((dev_t dev, uid_t uid... sys/types.h:typedef u_int32_t uid_t; /* user id */ and I mistakenly assumed that both x86 and alpha's use uid_t's of 32 bits. What did I miss? Sorry, I wasn't clear. I was talking about the general case, not about uid_t in particular. John To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
LD_LIBRARY_PATH not working?
Today I have been having problems with applications being unable to find shared libraries at run time with LD_LIBRARY_PATH set correctly. If the library is moved into a directory set at boot time with ldconfig (via rc), it works fine. I have tried it with several different libraries (both C and C++ used by both C and C++ apps), and the results are always the same. This is on a -current system built with sources cvsup'd at approximately 09:10 (CST) March 11, 2000. Did I overlook some configuration change? Thanks. -Patrick Patrick L. Hartling | Research Assistant, VRAC [EMAIL PROTECTED] | 2624 Howe Hall -- (515)294-4916 http://www.137.org/patrick/ | http://www.vrac.iastate.edu/ To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: MAX_UID ?
In article [EMAIL PROTECTED], Bruce Evans [EMAIL PROTECTED] wrote: I would prefer standard maxof() and minof() interfaces that work on any arithmetic type. These can almost be written in portable C, at least in C89 where types are restricted to char, signed char, ..., long double: #define isfloat(type) ((type)0.5 != 0) #define issigned(type)((type)-1 0) #define isschar(type) (!isfloat(type) issigned(type) sizeof(type) == 1) #define isuchar(type) (!isfloat(type) !issigned(type) sizeof(type) == 1) ... #define maxof(type) ((type)(isschar(type) ? SCHAR_MAX : isuchar(type) ? UCHAR_MAX ...)) I like this idea. John To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: B_WRITE cleanup patch, please test!
On Mon, 13 Mar 2000, Matthew Jacob wrote:
This patch is the first step towards the stackable BIO system as
sketched out on http://www.freebsd.org/~phk/Geom/
Please test review.
{ as Poul reminded me, I missed the header line that had the patch - sorry
about that }
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message
Weird problems with my IDE HD
I've got two HD's in my machine: one's an older one (WDMA2) and the other one, my main one, is newer (UDMA33). With recent kernel builds, I've noticed some strange problems with the older HD. When I try to to something like fsck -y on the drive, fsck just hangs. Also, if I have that drive mounted, and I do umount on that drive, umount hangs, and sometimes umount hangs my whole system. I'm trying to determine if it's because my drive is bad, or was there something that was changed in the ATA driver that may be causing this? Output of dmesg: [snip] atapci0: SiS 5591 ATA33 controller port 0xd000-0xd00f,0xd400-0xd403,0xd800-0xd 807,0xe000-0xe003,0xe400-0xe407 irq 11 at device 1.1 on pci0 ata0: at 0x1f0 irq 14 on atapci0 ata1: at 0x170 irq 15 on atapci0 [snip] ad0: 3093MB FUJITSU MPB3032ATU [6704/15/63] at ata0-master using UDMA33 ad1: 1040MB M1614TA [2114/16/63] at ata0-slave using WDMA2 acd0: CDROM BCD-24X 1997-06-27 at ata1-master using WDMA2 In this case, it is ad1 that is hanging. This was with kernels built from yesterday's cvsup sources. I'm recompiling the kernel now. - Donn To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: LD_LIBRARY_PATH not working?
In article [EMAIL PROTECTED], Patrick Hartling [EMAIL PROTECTED] wrote: Today I have been having problems with applications being unable to find shared libraries at run time with LD_LIBRARY_PATH set correctly. If the library is moved into a directory set at boot time with ldconfig (via rc), it works fine. I have tried it with several different libraries (both C and C++ used by both C and C++ apps), and the results are always the same. This is on a -current system built with sources cvsup'd at approximately 09:10 (CST) March 11, 2000. Did I overlook some configuration change? Thanks. Nothing has changed in connection with LD_LIBRARY_PATH recently. In fact, it has been at least a few weeks since the dynamic linker changed at all. Remember, LD_LIBRARY_PATH is ignored for setuid/setgid programs. John -- John Polstra [EMAIL PROTECTED] John D. Polstra Co., Inc.Seattle, Washington USA "Disappointment is a good sign of basic intelligence." -- Chögyam Trungpa To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: Weird problems with my IDE HD
It seems Donn Miller wrote: I've got two HD's in my machine: one's an older one (WDMA2) and the other one, my main one, is newer (UDMA33). With recent kernel builds, I've noticed some strange problems with the older HD. When I try to to something like fsck -y on the drive, fsck just hangs. Also, if I have that drive mounted, and I do umount on that drive, umount hangs, and sometimes umount hangs my whole system. I'm trying to determine if it's because my drive is bad, or was there something that was changed in the ATA driver that may be causing this? Output of dmesg: There was a window where the ata driver had a problem due to me committing a premature fix to enable the disksort stuff. This is now backed out in 4.0 and the prober fix is in -current. -Søren To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: Weird problems with my IDE HD
On Mon, 13 Mar 2000, Soren Schmidt wrote: It seems Donn Miller wrote: I'm trying to determine if it's because my drive is bad, or was there something that was changed in the ATA driver that may be causing this? Output of dmesg: There was a window where the ata driver had a problem due to me committing a premature fix to enable the disksort stuff. This is now backed out in 4.0 and the prober fix is in -current. Oh -- thanks for the info! So, it wasn't my imagination. Yeah, some strange stuff was happening. - Donn To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: latest 4.0 snapshot breaks tcpdump
Well yeah, that's fun to say, but my days have been literally completely full with getting other things ready for 4.0. And you think mine haven't been? :) My point is simply that I'm going to need a lot more than rough suggestions at this point if people want to help. I don't have time to go implement all these little ideas myself. - Jordan To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
4.0R ?
I do follow current, but I must be blind if I missed it. What is the latest date for 4.0R ? Will there be instead another Release Candidate and more testing ? ---Mike Mike Tancsa, tel +1 519 651 3400 Network Administrator,[EMAIL PROTECTED] Sentex Communications www.sentex.net Cambridge, Ontario Canada To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: 4.0R ?
The tag was laid down earlier today. Here is what my current kernel claims to be at the moment: FreeBSD 5.0-CURRENT #31: Mon Mar 13 10:59:41 EST 2000 Actually, there might be a couple fixes slipped in between now and the release, but 4.0R exists. You may cvsup with the tag RELENG_4 now if you like. Jim Bloom [EMAIL PROTECTED] Mike Tancsa wrote: I do follow current, but I must be blind if I missed it. What is the latest date for 4.0R ? Will there be instead another Release Candidate and more testing ? To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
calcru / microuptime problem
I have had these problems ever since upgrading to -current about a month ago. The kernel very regularly spews out messages like: Mar 13 14:23:39 gemini /kernel: calcru: negative time of -2663631 usec for pid 568 (sshd2) or a message that "microuptime() went backwards'. I have noticed that these messages usually coincide with moderate to heavy disk IO. I do not have the dmesg or kernel config here with me right now, but I believe I can provide most of the usefull information. The system is an ASUS P2B-DS running ROM revision 1009. It has 2 Pentium II - 400Mhz CPUs, and is running with 'device apm flags 0x20' to get the stat-clock (this was needed in FreeBSD-3.x, I have not yet tried without it. I am also running vinum across 3 disks, one Ultra-2-wide SCSI, and 2 IDE (each on their own bus). Furthermore I am running xntpd to keep my clock in sync. Any suggestions? -- David Cross | email: [EMAIL PROTECTED] Acting Lab Director | NYSLP: FREEBSD Systems Administrator/Research Programmer | Web: http://www.cs.rpi.edu/~crossd Rensselaer Polytechnic Institute, | Ph: 518.276.2860 Department of Computer Science| Fax: 518.276.4033 I speak only for myself. | WinNT:Linux::Linux:FreeBSD To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: calcru / microuptime problem
I have had these problems ever since upgrading to -current about a month ago. The kernel very regularly spews out messages like: Mar 13 14:23:39 gemini /kernel: calcru: negative time of -2663631 usec for pid 568 (sshd2) or a message that "microuptime() went backwards'. I have noticed that these messages usually coincide with moderate to heavy disk IO. I do not have the dmesg or kernel config here with me right now, but I believe I can provide most of the usefull information. The system is an ASUS P2B-DS running ROM revision 1009. It has 2 Pentium II - 400Mhz CPUs, and is running with 'device apm flags 0x20' to get the stat-clock (this was needed in FreeBSD-3.x, I have not yet tried without it. I am also running vinum across 3 disks, one Ultra-2-wide SCSI, and 2 IDE (each on their own bus). Furthermore I am running xntpd to keep my clock in sync. Any suggestions? Remove the flags on the apm device and update to at least the 1011 BIOS. -- \\ Give a man a fish, and you feed him for a day. \\ Mike Smith \\ Tell him he should learn how to fish himself, \\ [EMAIL PROTECTED] \\ and he'll hate you for a lifetime. \\ [EMAIL PROTECTED] To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: pccard.conf.sample ? Is that a great name ???
On Tue, 14 Mar 2000, Daniel C. Sobral wrote: You'd be right, if you were right. :-) Pccardd expects what you said, but defaults/rc.conf configures it to read pccard.conf.sample. In other words, what is used is the .sample file, *NOT* the customized version, unless you change that in /etc/rc.conf[.local]. Ah, sure enough, I had overridden it myself in /etc/rc.conf to do the right thing. Kelly -- Kelly Yancey - [EMAIL PROTECTED] - Richmond, VA Analyst / E-business Development, Bell Industries http://www.bellind.com/ Maintainer, BSD Driver Database http://www.posi.net/freebsd/drivers/ Coordinator, Team FreeBSDhttp://www.posi.net/freebsd/Team-FreeBSD/ To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: calcru / microuptime problem
On Mon, 13 Mar 2000, David E. Cross wrote: I have had these problems ever since upgrading to -current about a month ago. The kernel very regularly spews out messages like: Mar 13 14:23:39 gemini /kernel: calcru: negative time of -2663631 usec for pid 568 (sshd2) I know you've probably already tried this, but I'll say it just in case: try setting the kern.timecounter.method sysctl to 1 and see if that works around the problem. Kelly -- Kelly Yancey - [EMAIL PROTECTED] - Richmond, VA Analyst / E-business Development, Bell Industries http://www.bellind.com/ Maintainer, BSD Driver Database http://www.posi.net/freebsd/drivers/ Coordinator, Team FreeBSDhttp://www.posi.net/freebsd/Team-FreeBSD/ To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: MAX_UID ?
On Mon, 13 Mar 2000 02:13:30 GMT, Paul Richards wrote:
I guess my next question is, are there any objections to
#define UID_MAX ((uid_t)0-1)
If you decide to go the static macro definition (instead of Bruce's
maxof() / minof() idea), please consider using UID_T_{MAX,MIN} or, even
better, BSD_UID_T_{MAX,MIN}.
Thanks,
Sheldon.
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message
Re: calcru / microuptime problem
In message [EMAIL PROTECTED], "David E. Cross" writes: I have had these problems ever since upgrading to -current about a month ago. The kernel very regularly spews out messages like: Mar 13 14:23:39 gemini /kernel: calcru: negative time of -2663631 usec for pid 568 (sshd2) Disable APM in your bios and remove apm from your config. -- 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
Re: pccard.conf.sample ? Is that a great name ???
Unheedful of thy elder's warnings, Kelly Yancey wrote: On Mon, 13 Mar 2000, Nicolai Petri (ML) wrote: Am I the only one who thinks that having a .sample file containing active settings is a not so great ting ? Why not simply rename it to pccard.conf, pccard.conf.default or default/pccard.conf The correct would be the later, and I'll be doing that soon. It hasn't been done yet for weird reasons better left unsaid. :-) I assumed that the .sample was to emphasize the need to customize it as needed and save it as pccard.conf (where pccardd expects to find it). You'd be right, if you were right. :-) Pccardd expects what you said, but defaults/rc.conf configures it to read pccard.conf.sample. In other words, what is used is the .sample file, *NOT* the customized version, unless you change that in /etc/rc.conf[.local]. It doesn't strike me as a candidate for /etc/defaults/ unless it is made to include /etc/pccard.conf if it exists and override and config entries that are duplicated (i.e. if it were truly just defaults that could be overridden). That's my plan. In other words, it may not be intuitive, but it fits the existing protocol. The .sample file is being read because we need pccardd ok for sysinstall from pcmcia ethernet cards. -- Daniel C. Sobral (8-DCS) [EMAIL PROTECTED] [EMAIL PROTECTED] I have had my television aerials removed. It's the moral equivalent of a prostate operation. -- Malcolm Muggeridge To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
5.0?
I noted the tag on the kernel today was updated to 5.0-CURRENT... where is 4.0-RELEASE? To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: Weak symbols in libc_r broken?
On Mon, Mar 13, 2000 at 06:12:22PM +1100, John Birrell wrote: I deleted the weak definitions in the _THREAD_SAFE PRSYSCALL in lib/libc/i386/SYS.h and the problem goes away. I don't understand why Jason needed to add them in the first place. I didn't need to add them. At some point during all the changes I made, I mistakenly got it in my mind that the weak aliases had been there before I started mucking with things, and therefore I, uh, left them there. =) Unfortunately, I didn't notice this problem until a week ago, and it was only this weekend that I understood the root of the problem. Jason To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: 5.0?
On Mon, Mar 13, 2000 at 03:57:18PM -0500, Forrest Aldrich wrote: I noted the tag on the kernel today was updated to 5.0-CURRENT... where is 4.0-RELEASE? Multiple choice test: (1) There's a secret consipiracy going around to keep the release of it really, really quiet. (2) The consipiracy is to keep _you_ from knowing about it. (3) It hasn't been released yet because the rough edges are still being taken care of and polished of. (4) The developers all dropped FreeBSD and are now running Redhat. -- Bill Fumerola - Network Architect Computer Horizons Corp - CVM e-mail: [EMAIL PROTECTED] / [EMAIL PROTECTED] Office: 800-252-2421 x128 / Cell: 248-761-7272 To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
build-meisters
I'd like to solicit comments on pr 17304. This pr makes it possible to build a kld outside of the kernel source area. This is useful in our enviornment because we have lots of different FreeBSD machines around and we build modules for embedded systems on one sthat are "close" to the actual version, but not necessarily the same. These minro patches make that practice safe. By defining KERN to be /usr/src/sys/kern, or whereever you have your kernel (in my case /h/imp/tsc/FreeBSD-tsc-4/kern). Can anybody comment on this? I know I'm slightly abusing KERN, but having a new variable KERNBASE or KERNBASEDIR seemed too much., The second patch in the PR is the one I'm interested in feedback on. It has survived at least one buildworld here. Warner To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: 4.0R ?
Jim Bloom wrote: The tag was laid down earlier today. Here is what my current kernel claims to be at the moment: I saw the RELENG_4 tag in my cvsup log, but I don't think that's the same as the 4.0 release tag is it? That would be RELENG_4_0_0_RELEASE surely. -- Ben Smithurst / [EMAIL PROTECTED] / PGP: 0x99392F7D To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
(no subject)
auth e96ad1c2 subscribe freebsd-current [EMAIL PROTECTED] To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: calcru / microuptime problem
In message [EMAIL PROTECTED], "David E. Cross" writes: I have had these problems ever since upgrading to -current about a month ago. The kernel very regularly spews out messages like: Mar 13 14:23:39 gemini /kernel: calcru: negative time of -2663631 usec for pid 568 (sshd2) Disable APM in your bios and remove apm from your config. This isn't the fix for this problem, and especially not on this board. -- \\ Give a man a fish, and you feed him for a day. \\ Mike Smith \\ Tell him he should learn how to fish himself, \\ [EMAIL PROTECTED] \\ and he'll hate you for a lifetime. \\ [EMAIL PROTECTED] To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: pccard.conf.sample ? Is that a great name ???
In message [EMAIL PROTECTED] "Nicolai Petri (ML)" writes: : Am I the only one who thinks that having a .sample file containing active : settings is a not so great ting ? No. It is bad. I was asleep at the time it happened, and didn't notice until we were in code freeze. In hind sight, Id have changed it anyway... : Why not simply rename it to pccard.conf, pccard.conf.default or : default/pccard.conf I'd call it /etc/default/pccard.conf. The problem with doing this today is that there's no include file to chain things... Warner To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Compaq SMART EISA and ida driver - kernel panic
hello *!
i was very happy to se, that the eisa bus attachment stuff had been reviewed
and comitted to the source tree. the kernel compiles w/o problems but
panics, when booting :-(
has anybody with an eisa board have had success (maybe my setup is somehow
wrong?!)
relevent kernel messages:
ahb0: Adaptec 174x SCSI host adapter at 0x3c00-0x3cff, irq 12 (edge)
ahb0: on eisa0 slot 3
ahb0: AHA1740A Single Ended SCSI Adapter, FW Rev. E, ID=7, 64 ECBs
ida0: Compaq SMART array controller at 0x4c88-0x4c9e, irq 15 (level)
ida0: on eisa0 slot 4
panic: ida_wait: incorrect qcb returned
Debugger("panic")
Stopped at Debugger+0x35: movb$0,in_Debugger.372
"trace" in the kernel debugger returnes following output:
panic(c01f7520,c0ca7000,c0ca5d00,,c029ee84) at panic+0xf8
ida_wait(c0ca5d00,c0ca7000,1f4,c0ca5d00,0) at ida_wait+0x75
ida_command(c0ca5d00,11,c029eeb4,9,0,1,c0ca5d00,0) at ida_command+0xf8
ida_attach(c0ca5d00,c0ca4c80,c0ca4f00,0,c0ca5d00) at ida_attach+0x28
ida_eisa_attach(c0ca4c80,c029ef08,c01561fb,c0ca4c80,c0ca4c80) at
ida_eisa_attach+0x187
DEVICE_ATTACH(c0ca4c80,c0ca4c80,c0ca2000,0,c029ef18) at DEVICE_ATTACH+0x2e
[some more, but i think, that was the importtant part, since the adaptec
board ist probed and initialized correclty]
unfortunaly no core dump available.
information on machine:
compaq prosignia 486 w/pentium overdrive (bios version as from 09/25/97)
os set to "UNIX/XENIX"
1x compaq smart array controller (firmware revision 2.26)
os set to "UNIX/XENIX"
one logical volume:
2x quantum fireball 1.08GB (drive mirroring)
setup via compaq system configuration utility (did i miss something?)
1x adaptec 1740
1x adaptec 2742 (floppy controller disabled)
2x 3com 3c597 NICs
without the driver the machine runs just rock solid (lacking a raid, of
course). so something must be wrong, when probing for the controller.
any ideas?
if more information is needed, i will try to provide them,
cheers,
oliver
--
email: [EMAIL PROTECTED]
[EMAIL PROTECTED]
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message
[URGENT] OpenSSH changes
Can everyone please do a make world of RELENG_4 with my latest OpenSSH changes, and verify that everything still works properly? The only thing that should have changed is that it will now report a more descriptive error when trying to talk to a server which uses long (1024 bit) keys and you're using the RSAREF version. In particular I would like international people (those who use crypto ultimately derived from internat.freebsd.org) to test this, as I haven't done any testing myself from there. If there are any problems, I'd really like to know about them *ASAP* (i.e. before the release announcement, so I can fix them). Thanks! 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: [URGENT] OpenSSH changes
Is there actually a RELENG_4 (release) ? I have seen a couple messages saying there is and a few saying there isnt. On 13-Mar-00 Kris Kennaway wrote: Can everyone please do a make world of RELENG_4 with my latest OpenSSH changes, and verify that everything still works properly? The only thing that should have changed is that it will now report a more descriptive error when trying to talk to a server which uses long (1024 bit) keys and you're using the RSAREF version. In particular I would like international people (those who use crypto ultimately derived from internat.freebsd.org) to test this, as I haven't done any testing myself from there. If there are any problems, I'd really like to know about them *ASAP* (i.e. before the release announcement, so I can fix them). Thanks! 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 -- E-Mail: [EMAIL PROTECTED] Date: 13-Mar-00 Time: 15:32:15l -- NOTICE TO BULK E-MAILERS: Pursuant to US Code, Title 47, Chapter 5, Subchapter II, 227, and all unsolicited commercial e-mail sent to this address is subject to a download and archival fee in the amount of $500 US To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: [URGENT] OpenSSH changes
On Mon, Mar 13, 2000 at 03:33:05PM -0800, William Woods wrote: Is there actually a RELENG_4 (release) ? I have seen a couple messages saying there is and a few saying there isnt. There is a RELENG_4 branch, but no 4.0-RELEASE as yet. Regards, --Keith Stevenson-- -- Keith Stevenson System Programmer - Data Center Services - University of Louisville [EMAIL PROTECTED] PGP key fingerprint = 4B 29 A8 95 A8 82 EA A2 29 CE 68 DE FC EE B6 A0 To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: [URGENT] OpenSSH changes
On Mon, Mar 13, 2000 at 03:33:05PM -0800, William Woods wrote: Is there actually a RELENG_4 (release) ? I have seen a couple messages saying there is and a few saying there isnt. There is a RELENG_4 (cvsup'ing my CVS repository took forever this morning ;-), but there is not a 4.0 release tag yet. -- Brooks -- Any statement of the form "X is the one, true Y" is FALSE. To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
RE: [URGENT] OpenSSH changes
On Mon, 13 Mar 2000, William Woods wrote: Is there actually a RELENG_4 (release) ? I have seen a couple messages saying there is and a few saying there isnt. Do a cvsup and you'll soon find out :-) 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: 5.0?
On Mon, 13 Mar 2000, in a never-ending search for enlightenment, Bill Fumerola wrote: On Mon, Mar 13, 2000 at 03:57:18PM -0500, Forrest Aldrich wrote: I noted the tag on the kernel today was updated to 5.0-CURRENT... where is 4.0-RELEASE? Multiple choice test: (1) There's a secret consipiracy going around to keep the release of it really, really quiet. (2) The consipiracy is to keep _you_ from knowing about it. (3) It hasn't been released yet because the rough edges are still being taken care of and polished of. (4) The developers all dropped FreeBSD and are now running Redhat. -- Bill Fumerola - Network Architect Computer Horizons Corp - CVM e-mail: [EMAIL PROTECTED] / [EMAIL PROTECTED] Office: 800-252-2421 x128 / Cell: 248-761-7272 Ummmis it 4? -- Walter Brameld Microsoft: Where do you want to go today? Linux: Where do you want to go tomorrow? BSD: Are you guys coming, or what? Walter:Where the hell am I? To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: 5.0?
Oh, it MUST be #4:-) (hide) At 04:19 PM 3/13/00 -0500, Bill Fumerola wrote: On Mon, Mar 13, 2000 at 03:57:18PM -0500, Forrest Aldrich wrote: I noted the tag on the kernel today was updated to 5.0-CURRENT... where is 4.0-RELEASE? Multiple choice test: (1) There's a secret consipiracy going around to keep the release of it really, really quiet. (2) The consipiracy is to keep _you_ from knowing about it. (3) It hasn't been released yet because the rough edges are still being taken care of and polished of. (4) The developers all dropped FreeBSD and are now running Redhat. -- Bill Fumerola - Network Architect Computer Horizons Corp - CVM e-mail: [EMAIL PROTECTED] / [EMAIL PROTECTED] Office: 800-252-2421 x128 / Cell: 248-761-7272 To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: IPv6 setup...
echo 24.113.25.85 | sed -e s/"\."/" "/g | awk '{$5 = $1*256 + $2; $6 = $3*256 +
$4; printf "2002:%x:%x:\n", $5, $6}'
Or, without only one extra process:
myaddr=24.113.25.85
OIFS="$IFS"
IFS=".$IFS"
set $myaddr
IFS="$OIFS"
printf "2002:%x:%x:\n" $(($1 * 256 + $2)) $(($3 * 256 + $4))
-GAWollman
It's fine.
I'll also use it in /etc/rc.network6.
Thanks,
Yoshinobu Inoue
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message
Re: ES1370 - no sound completely :(
It doesn't helps :( The card consists of two chips the ES1370 plus a codec chip. And if I remember correctly that one is different from the AK4531 on the original Audio PCI card (they used a cheaper one for the PCI64). Creative probably bought Ensoniq because of the Audio PCI card which seems to be mostly identical to the PCI128. I would suggest changing the PCI64 into a PCI128 if possible. If not you must first identify what codec is used on the board - maybe we find specs or an existing Linux driver.. Regards, Marc To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
pcm use /dev/dsp to where?
I am using the new pcm driver which works great, however, I managed to remove the ln -s to dsp. I do not know what it was linked and 'sh MAKEDEV snd' links dsp to dsp. How can I fix this? pcm0: AudioPCI ES1371 port 0xef00-0xef3f irq 7 at device 16.0 on pci0 Thanks, Aaron - Aaron Hughes - [EMAIL PROTECTED] - For public PGP key: finger [EMAIL PROTECTED] - Key fingerprint = AD 67 37 60 7D 73 C5 B7 33 18 3F 36 C3 1C C6 B8 To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: pcm use /dev/dsp to where?
I am using the new pcm driver which works great, however, I managed to remove the ln -s to dsp. I do not know what it was linked and 'sh MAKEDEV snd' links dsp to dsp. How can I fix this? pcm0: AudioPCI ES1371 port 0xef00-0xef3f irq 7 at device 16.0 on pci0 ^ sh MAKEDEV snd0 (you would use 'snd1' if your card was detected as pcm1, etc). To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: Compaq SMART EISA and ida driver - kernel panic
On Tue, 14 Mar 2000, Oliver Schonefeld wrote:
i was very happy to se, that the eisa bus attachment stuff had been
reviewed and comitted to the source tree. the kernel compiles w/o
problems but panics, when booting :-( has anybody with an eisa board
have had success (maybe my setup is somehow wrong?!)
Could you add
printf("0x%lx\n0x%lx0x%lx\n", qcb, completed, qcb_done);
to ida.c:ida_wait() after this line:
454:qcb_done = idahwqcbptov(ida, completed ~3);
And show us the output.
relevent kernel messages:
ahb0: Adaptec 174x SCSI host adapter at 0x3c00-0x3cff, irq 12 (edge)
ahb0: on eisa0 slot 3
ahb0: AHA1740A Single Ended SCSI Adapter, FW Rev. E, ID=7, 64 ECBs
ida0: Compaq SMART array controller at 0x4c88-0x4c9e, irq 15 (level)
ida0: on eisa0 slot 4
panic: ida_wait: incorrect qcb returned
Debugger("panic")
Stopped atDebugger+0x35: movb$0,in_Debugger.372
"trace" in the kernel debugger returnes following output:
panic(c01f7520,c0ca7000,c0ca5d00,,c029ee84) at panic+0xf8
ida_wait(c0ca5d00,c0ca7000,1f4,c0ca5d00,0) at ida_wait+0x75
ida_command(c0ca5d00,11,c029eeb4,9,0,1,c0ca5d00,0) at ida_command+0xf8
ida_attach(c0ca5d00,c0ca4c80,c0ca4f00,0,c0ca5d00) at ida_attach+0x28
ida_eisa_attach(c0ca4c80,c029ef08,c01561fb,c0ca4c80,c0ca4c80) at
ida_eisa_attach+0x187
DEVICE_ATTACH(c0ca4c80,c0ca4c80,c0ca2000,0,c029ef18) at DEVICE_ATTACH+0x2e
[some more, but i think, that was the importtant part, since the adaptec
board ist probed and initialized correclty]
unfortunaly no core dump available.
information on machine:
compaq prosignia 486 w/pentium overdrive (bios version as from 09/25/97)
os set to "UNIX/XENIX"
1x compaq smart array controller (firmware revision 2.26)
os set to "UNIX/XENIX"
one logical volume:
2x quantum fireball 1.08GB (drive mirroring)
setup via compaq system configuration utility (did i miss something?)
1x adaptec 1740
1x adaptec 2742 (floppy controller disabled)
2x 3com 3c597 NICs
without the driver the machine runs just rock solid (lacking a raid, of
course). so something must be wrong, when probing for the controller.
any ideas?
if more information is needed, i will try to provide them,
cheers,
oliver
--
| 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: pcm use /dev/dsp to where?
Thanks Steve, That did it, I figured it was something minor I had screwed up. Aaron On Mon, 13 Mar 2000, Steve Coltrin wrote: I am using the new pcm driver which works great, however, I managed to remove the ln -s to dsp. I do not know what it was linked and 'sh MAKEDEV snd' links dsp to dsp. How can I fix this? pcm0: AudioPCI ES1371 port 0xef00-0xef3f irq 7 at device 16.0 on pci0 ^ sh MAKEDEV snd0 (you would use 'snd1' if your card was detected as pcm1, etc). - Aaron Hughes - [EMAIL PROTECTED] - For public PGP key: finger [EMAIL PROTECTED] - Key fingerprint = AD 67 37 60 7D 73 C5 B7 33 18 3F 36 C3 1C C6 B8 To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: Buffer troubles, and machine hangs?
On Sun, Mar 12, 2000 at 03:13:20PM -0500, Howard Leadmon wrote: Hello, I am getting the following errors out of FreeBSD 4.0-CURRENT trying to run an IRC server, and was wondering if anyone had any ideas or recommended tunables I should set?? Mar 9 22:32:03 u /usr/ircd/undernet/ircd[154]: Unable to create auth socket for [@163.152.216.46]:No buffer space available Mar 9 22:32:03 u /usr/ircd/undernet/ircd[154]: Unable to create auth socket for [@208.164.193.201]:No buffer space available Mar 9 22:33:00 u syslogd: sendto: No buffer space available You can probably get away with increasing NMBCLUSTERS. I have actually been fighting a problem with this machine locking up, and requiring a hard reset, and this is the only type errors I am actually seeing in the messages file. But lockups are certainly not a good thing, IMHO. If you can debug the kernel, and see where it locks up, perhaps someone with more knowledge of the kernel internals than me will be able to help you sort this out. - Giorgos Keramidas To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: MAX_UID ?
On Mon, Mar 13, 2000 at 05:28:47PM +1100, Bruce Evans wrote: ... I would prefer standard maxof() and minof() interfaces that work on any arithmetic type. These can almost be written in portable C, at least in C89 where types are restricted to char, signed char, ..., long double: #define isfloat(type) ((type)0.5 != 0) #define issigned(type)((type)-1 0) #define isschar(type) (!isfloat(type) issigned(type) sizeof(type) == 1) #define isuchar(type) (!isfloat(type) !issigned(type) sizeof(type) == 1) ... #define maxof(type) ((type)(isschar(type) ? SCHAR_MAX : isuchar(type) ? UCHAR_MAX ...)) This is marvellous in it's simplicity of interface. Yet, using sizeof(char) and assuming that it's going to be 1, strikes me like a dangerous thing to do. I have never heard of machines where this isn't true, but I seem to recall that the comp.lang.c FAQ mentions this somewhere. I'll look it up tomorrow, since it's getting too late.. - Giorgos Keramidas To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: MAX_UID ?
Giorgos Keramidas [EMAIL PROTECTED] wrote: : This is marvellous in it's simplicity of interface. : : Yet, using sizeof(char) and assuming that it's going to be 1, strikes me : like a dangerous thing to do. I have never heard of machines where this : isn't true, but I seem to recall that the comp.lang.c FAQ mentions this : somewhere. I'll look it up tomorrow, since it's getting too late... In both C and C++, sizeof(T) is defined to be the size of T in terms of the size of a char, so by definition sizeof(char) == 1. You can look it up (for C) at: http://www.eskimo.com/~scs/C-faq/q7.8.html For C++, see section 4.6 of The C++ Programming Language. -Ed To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
ATA still panics during boot on P66
Hi, I can't find the date or sender of the original email - the mailing list archives haven't been updated since Feb 20 - but my Pentium 66 still panics during boot with a kernel compiled today. Here's what I get... atapci0: RZ 100? ATA controller !WARNING! buggy chip data loss possible port 0x3f4-0x3f7,0x1f0-0x1f7 at device 1.0 on pci0 atapci0: Busmastering DMA not supported panic: resource_list_alloc: resource entry is busy Everything works fine, however, when I move the drives to the secondary IDE channel on the ISA bus. Any ideas? Greg To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: MAX_UID ?
On Tue, 14 Mar 2000, Giorgos Keramidas wrote: On Mon, Mar 13, 2000 at 05:28:47PM +1100, Bruce Evans wrote: ... #define isschar(type) (!isfloat(type) issigned(type) sizeof(type) == 1) This is marvellous in it's simplicity of interface. Yet, using sizeof(char) and assuming that it's going to be 1, strikes me like a dangerous thing to do. I have never heard of machines where this It is sure to be 1 (the C standard requires this). The problem is going in the opposite direction -- sizeof(long) may also be 1. sizeof(signed char) == sizeof(long) doesn't imply that SCHAR_MAX == LONG_MAX, so the macros may give the wrong result for: typedef long foo_t; ... assert(maxof(foo_t) == LONG_MAX); Bruce To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: MAX_UID ?
On 2000-Mar-14 15:42:52 +1100, Bruce Evans [EMAIL PROTECTED] wrote: On Tue, 14 Mar 2000, Giorgos Keramidas wrote: On Mon, Mar 13, 2000 at 05:28:47PM +1100, Bruce Evans wrote: ... #define isschar(type) (!isfloat(type) issigned(type) sizeof(type) == 1) This is marvellous in it's simplicity of interface. Yet, using sizeof(char) and assuming that it's going to be 1, strikes me like a dangerous thing to do. I have never heard of machines where this It is sure to be 1 (the C standard requires this). The problem is going in the opposite direction -- sizeof(long) may also be 1. If this was comp.std.c, then I'd agree that such constructs may fail in some environments. It's not so clear that we need to worry about this here (this being FreeBSD). I believe that most or all such machines belong to Seymour Cray's legacy (CDC6600, Cray etc), and aren't likely to be running FreeBSD (or any other free Unix). I don't see any real impediment to such constructs being used within FreeBSD. A comment could be added warning of the problems if the code is used on `unusual' architectures. Peter To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
microuptime() still going backwards (long)
I followed the suggestions from people earlier today. That is to say that I have upgraded my BIOS to 1012, disabled APM in the BIOS, and removed 'device apm' from the kernel config, however I still receive lines like: calcru: negative time of 20585525 usec for pid 477 (cvsup) and also lines about microuptime() being negative (I think these are related :) Below is a dmesg and my kernel config. Cheers 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 #0: Mon Mar 13 23:45:03 EST 2000 [EMAIL PROTECTED]:/usr/src/sys/compile/GEMINI Timecounter "i8254" frequency 1193182 Hz CPU: Pentium II/Pentium II Xeon/Celeron (400.62-MHz 686-class CPU) Origin = "GenuineIntel" Id = 0x652 Stepping = 2 Features=0x183fbffFPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,MMX,FXSR real memory = 268423168 (262132K bytes) config pnp 1 1 os enable port0 0x534 port2 0x220 port3 0xe0d irq0 10 drq0 1 drq1 6 Invalid command or syntax. Type `?' for help. avail memory = 256532480 (250520K bytes) Programming 24 pins in IOAPIC #0 IOAPIC #0 intpin 2 - irq 0 FreeBSD/SMP: Multiprocessor motherboard cpu0 (BSP): apic id: 1, version: 0x00040011, at 0xfee0 cpu1 (AP): apic id: 0, version: 0x00040011, at 0xfee0 io0 (APIC): apic id: 2, version: 0x00170011, at 0xfec0 Preloaded elf kernel "kernel" at 0xc0363000. Preloaded userconfig_script "/boot/kernel.conf" at 0xc036309c. Pentium Pro MTRR support enabled md0: Malloc disk npx0: math processor on motherboard npx0: INT 16 interface pcib0: Intel 82443BX (440 BX) host to PCI bridge on motherboard pci0: PCI bus on pcib0 pcib1: Intel 82443BX (440 BX) PCI-PCI (AGP) bridge at device 1.0 on pci0 pci1: PCI bus on pcib1 pci1: NVidia Riva TNT graphics accelerator at 0.0 irq 16 isab0: Intel 82371AB PCI to ISA bridge at device 4.0 on pci0 isa0: ISA bus on isab0 atapci0: Intel PIIX4 ATA33 controller port 0xd800-0xd80f at device 4.1 on pci0 ata0: at 0x1f0 irq 14 on atapci0 ata1: at 0x170 irq 15 on atapci0 uhci0: Intel 82371AB/EB (PIIX4) USB controller port 0xd400-0xd41f irq 19 at device 4.2 on pci0 usb0: Intel 82371AB/EB (PIIX4) USB controller on uhci0 usb0: USB revision 1.0 uhub0: Intel UHCI root hub, class 9/0, rev 1.00/1.00, addr 1 uhub0: 2 ports with 2 removable, self powered ums0: Microsoft Microsoft IntelliMouse\M-. Explorer, rev 1.10/1.03, addr 2, iclass 3/1 ums0: 5 buttons and Z dir. ukbd0: Microsoft Natural Keyboard Elite, rev 1.00/1.04, addr 3, iclass 3/1 Timecounter "PIIX" frequency 3579545 Hz chip1: Intel 82371AB Power management controller port 0xe800-0xe80f at device 4.3 on pci0 ahc0: Adaptec aic7890/91 Ultra2 SCSI adapter port 0xd000-0xd0ff mem 0xdf80-0xdf800fff irq 19 at device 6.0 on pci0 ahc0: aic7890/91 Wide Channel A, SCSI Id=7, 16/255 SCBs pci0: unknown card (vendor=0x1102, dev=0x0002) at 9.0 irq 19 pci0: unknown card (vendor=0x1102, dev=0x7002) at 9.1 xl0: 3Com 3c900-TPO Etherlink XL port 0xb000-0xb03f irq 18 at device 10.0 on pci0 xl0: Ethernet address: 00:60:08:a9:db:e2 xl0: selecting 10baseT transceiver, half duplex bktr0: BrookTree 878 mem 0xe200-0xe2000fff irq 17 at device 11.0 on pci0 iicbb0: I2C generic bit-banging driver on bti2c0 iicbus0: Philips I2C bus on iicbb0 master-only smbus0: System Management Bus on bti2c0 bktr0: Hauppauge Model 38061 B226 Hauppauge WinCast/TV, Philips NTSC tuner, remote control. pci0: unknown card (vendor=0x109e, dev=0x0878) at 11.1 irq 17 ahc1: Adaptec 2940 Ultra SCSI adapter port 0xa800-0xa8ff mem 0xdf00-0xdf000fff irq 16 at device 12.0 on pci0 ahc1: aic7880 Wide Channel A, SCSI Id=7, 16/255 SCBs isa0: too many memory rangesfdc0: NEC 72065B or clone at port 0x3f0-0x3f5,0x3f7 irq 6 drq 2 on isa0 fdc0: FIFO enabled, 8 bytes threshold fd0: 1440-KB 3.5" drive on fdc0 drive 0 fd1: 1200-KB 5.25" drive on fdc0 drive 1 WARNING: "fd" is usurping "fd"'s cdevsw[] WARNING: "fd" is usurping "fd"'s bmaj vga0: Generic ISA VGA at port 0x3c0-0x3df iomem 0xa-0xb on isa0 sc0: System console at flags 0x100 on isa0 sc0: VGA 16 virtual consoles, flags=0x100 sio0: configured irq 4 not in bitmap of probed irqs 0 sio0 at port 0x3f8-0x3ff irq 4 flags 0x30 on isa0 sio0: type 16550A, console sio1: configured irq 3 not in bitmap of probed irqs 0 sio1 at port 0x2f8-0x2ff irq 3 on isa0 sio1: type 16550A ppc0: Parallel port at port 0x378-0x37f irq 7 on isa0 ppc0: SMC-like chipset (ECP/EPP/PS2/NIBBLE) in COMPATIBLE mode ppc0: FIFO with 16/16/9 bytes threshold ppi0: Parallel I/O on ppbus0 lpt0: Printer on ppbus0 lpt0: Interrupt-driven port ep0: 3Com 3C509-TPO EtherLink III at port 0x310-0x31f irq 11 on isa0 ep0: Ethernet address 00:a0:24:12:8d:10 unknown: PNP0401 can't assign resources unknown: PNP0501 can't assign resources unknown: PNP0501 can't assign resources unknown: PNP0700 can't assign resources unknown0: PNP0c01 at iomem
ppp / nat pptp
[ Please redirect me to a better mailinglist if needed, I haven't had any replies on this subject yet ] I'm getting closer. Basically, I have at home a win-machine behind a FreeBSD box with user-ppp and isdn. It is cheaper for me to use an alternative ISP than ourselves to get the machines at work. However, then I don't have access to some servers, because I come from a foreign (and dynamic) ip-adress. So I install pptpd on a machine at work to make a tunnel and get a "trusted" ip-adress. Questions: man ppp, topic nat pptp suggest, that only one machine behind ppp can run MS-vpn (over GRE). True? Is it a problem that I only have one ethernet card on the pptpd-machine: am I supposed to go in on one interface, be translated, and go out on the other? Any clues on setting up pptpd and ppp? It seems that the adresses (localip and remoip) in pptpd.conf are ignored, and the adresses in ppp.conf are used instead. Currently, I can now connect from ms-vpn, and from the box running nntpd ping the ip on the win-box. But then I can't ping from any other adresses. Can I find some examples of poptop/pptpd and user-ppp somewhere? Leif To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: calcru / microuptime problem
On Mon, Mar 13, 2000 at 09:00:26PM +0100, Poul-Henning Kamp [EMAIL PROTECTED] wrote: In message [EMAIL PROTECTED], "David E. Cross" writes: I have had these problems ever since upgrading to -current about a month ago. The kernel very regularly spews out messages like: Mar 13 14:23:39 gemini /kernel: calcru: negative time of -2663631 usec for pid 568 (sshd2) Disable APM in your bios and remove apm from your config. The 'microuptime() went backwards' happened to me also lately, week or so ago. Tyan mobo with GX chipset, power management disabled completely in the BIOS, no apm in kernel. Two PIII-550, one 20GB IBM disk (ATA). Same symptoms as above, heavy disk I/O, I was stress-testing the machine, except the machine hung for some unknown reason: I was able to switch vty's and ping the machine but not login, no disk I/O. I'm waiting for two 36GB IBM SCSI disks, which should arrive soon, then the next round without ATA is what I'm planning. -- Vallo Kallaste [EMAIL PROTECTED] To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: calcru / microuptime problem
On 14-Mar-00 Vallo Kallaste wrote: in the BIOS, no apm in kernel. Two PIII-550, one 20GB IBM disk (ATA). Same symptoms as above, heavy disk I/O, I was stress-testing the machine, except the machine hung for some unknown reason: I was able to switch vty's and ping the machine but not login, no disk I/O. I'm waiting for two 36GB IBM SCSI disks, which should arrive soon, then the next round without ATA is what I'm planning. Do you have the latest BIOS rev? --- Daniel O'Connor software and network engineer for Genesis Software - http://www.gsoft.com.au "The nice thing about standards is that there are so many of them to choose from." -- Andrew Tanenbaum To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
RE: microuptime() still going backwards (long)
Try w/o PNPBIOS option. I had the similar problem, and that fixed it. Val - I followed the suggestions from people earlier today. That is to say that I have upgraded my BIOS to 1012, disabled APM in the BIOS, and removed 'device apm' from the kernel config, however I still receive lines like: calcru: negative time of 20585525 usec for pid 477 (cvsup) and also lines about microuptime() being negative (I think these are related :) Below is a dmesg and my kernel config. Cheers __ Do You Yahoo!? Talk to your friends online with Yahoo! Messenger. http://im.yahoo.com To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: calcru / microuptime problem
On Tue, Mar 14, 2000 at 04:40:43PM +1030, Daniel O'Connor [EMAIL PROTECTED] wrote: On 14-Mar-00 Vallo Kallaste wrote: in the BIOS, no apm in kernel. Two PIII-550, one 20GB IBM disk (ATA). Same symptoms as above, heavy disk I/O, I was stress-testing the machine, except the machine hung for some unknown reason: I was able to switch vty's and ping the machine but not login, no disk I/O. I'm waiting for two 36GB IBM SCSI disks, which should arrive soon, then the next round without ATA is what I'm planning. Do you have the latest BIOS rev? You mean for Tyan mobo? No, it's version 1.16b nongraphical AMIBIOS which come with board. I'm having exactly same board but with SCSI only configuration for my workstation which works without any problem for half a year now. Also SMP, two PIII-500. When the new disks arrive, well, I can try the new BIOS also. -- Vallo Kallaste [EMAIL PROTECTED] To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: calcru / microuptime problem
On 14-Mar-00 Vallo Kallaste wrote: You mean for Tyan mobo? No, it's version 1.16b nongraphical AMIBIOS which come with board. I'm having exactly same board but with SCSI only configuration for my workstation which works without any problem for half a year now. Also SMP, two PIII-500. When the new disks arrive, well, I can try the new BIOS also. Worth a shot I suppose.. Other people seem to recommend it anyway 8-) --- Daniel O'Connor software and network engineer for Genesis Software - http://www.gsoft.com.au "The nice thing about standards is that there are so many of them to choose from." -- Andrew Tanenbaum To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: ATA still panics during boot on P66
It seems Greg Childers wrote: Hi, I can't find the date or sender of the original email - the mailing list archives haven't been updated since Feb 20 - but my Pentium 66 still panics during boot with a kernel compiled today. Here's what I get... atapci0: RZ 100? ATA controller !WARNING! buggy chip data loss possible port 0x3f4-0x3f7,0x1f0-0x1f7 at device 1.0 on pci0 atapci0: Busmastering DMA not supported panic: resource_list_alloc: resource entry is busy Everything works fine, however, when I move the drives to the secondary IDE channel on the ISA bus. Any ideas? Can you get a verbose boot off it with an older kernel ?? if so mail that to me and I'll see if I can spot anything... -Søren To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
