vidcontrol is not working properly
Maybe something broke with the "3rd stage of syscons code reorganization".
I'm sure this worked properly around the end of December last year. I
don't know when exactly it stopped working.
$ vidcontrol -r black green VGA_80x60 green black
does not set the reverse colours.
$ vidcontrol -r black green
does.
This is happening on -current cvsup'd and built Jan 26, 2000.
--
:{ [EMAIL PROTECTED]
Andy Farkas
System Administrator
Speednet Communications
http://www.speednet.com.au/
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message
Re: IP-Filter w/FreeBSD-current
Cy Schubert - ITSD Open Systems Group [EMAIL PROTECTED] writes: With the impending release of FreeBSD-4.0, is anyone on this list using IP-Filter on FreeBSD-current? I'm planning to install -current w/IP-Filter on a testbed and would like to know of there are any gotchas or if it even runs on FreeBSD-current. I've been using ipfilter with -current since 24 Jan 2000, and this night I'm running my buildworld with cvsup'ed sources. With user PPP on tun0 and kernel PPP on ppp0 there seem to be no problems, so far. If something comes up after tonight's build, I'll let you know. -- Giorgos Keramidas, keramida @ ceid . upatras . gr For my public PGP key: finger [EMAIL PROTECTED] PGP fingerprint, phone and address in the headers of this message. To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: HEADS UP: GNU grep 2.4d
hi, there! On Mon, 31 Jan 2000, Jeremy Lea wrote: It was a local FreeBSD feature; now it is part of the official GNU grep. Any chance of -R coming back too? it is already there (-r) /fjoe To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
make release breakage (readline.h)
My make releases here keep falling over... === gnu/usr.bin/binutils/doc === gnu/usr.bin/binutils/gdb Making init.c yacc -o c-exp.c /usr/src/gnu/usr.bin/binutils/gdb/../../../../contrib/gdb/gdb/c-exp.y yacc -o f-exp.c /usr/src/gnu/usr.bin/binutils/gdb/../../../../contrib/gdb/gdb/f-exp.y yacc: 4 rules never reduced yacc -o jv-exp.c /usr/src/gnu/usr.bin/binutils/gdb/../../../../contrib/gdb/gdb/jv-exp.y yacc -o m2-exp.c /usr/src/gnu/usr.bin/binutils/gdb/../../../../contrib/gdb/gdb/m2-exp.y rm -f .depend mkdep -f .depend -a-D_GNU_SOURCE -I- -I. -I/usr/src/gnu/usr.bin/binutils/gdb/i386 -I/usr/src/gnu/usr.bin/binutils/gdb -I/usr/src/gnu/usr.bin/binutils/gdb/../libbfd/i386 -I/usr/src/gnu/usr.bin/binutils/gdb/../../../../contrib/binutils/include -I/usr/src/gnu/usr.bin/binutils/gdb/i386 -I/usr/src/gnu/usr.bin/binutils/gdb/../../../../contrib/binutils/binutils -I/usr/src/gnu/usr.bin/binutils/gdb/../../../../contrib/binutils/bfd -I/usr/src/gnu/usr.bin/binutils/gdb/../../../../contrib/gdb/gdb -I/usr/src/gnu/usr.bin/binutils/gdb/../../../../contrib/gdb/gdb/config -DFREEBSD_ELF -I/usr/src/gnu/usr.bin/binutils/gdb -I/usr/obj/usr/src/i386/usr/include/readline -DNO_MMALLOC -I/usr/obj/usr/src/i386/usr/include init.c /usr/src/gnu/usr.bin/binutils/gdb/../../../../contrib/gdb/gdb/annotate.c /usr/src/gnu/usr.bin/binutils/gdb/../../../../contrib/gdb/gdb/ax-general.c /usr/src/gnu/usr.bin/binutils/gdb/../../../../contrib/gdb/gdb/ax-gdb.c /usr/src/gnu/usr.bin/binutils/gdb/../../../../contrib/gdb/gdb/bcache.c /usr/src/gnu/usr.bin/binutils/gdb/../../../../contrib/gdb/gdb/blockframe.c /usr/src/gnu/usr.bin/binutils/gdb/../../../../contrib/gdb/gdb/breakpoint.c /usr/src/gnu/usr.bin/binutils/gdb/../../../../contrib/gdb/gdb/buildsym.c c-exp.c /usr/src/gnu/usr.bin/binutils/gdb/../../../../contrib/gdb/gdb/c-lang.c /usr/src/gnu/usr.bin/binutils/gdb/../../../../contrib/gdb/gdb/c-typeprint.c /usr/src/gnu/usr.bin/binutils/gdb/../../../../contrib/gdb/gdb/c-valprint.c /usr/src/gnu/usr.bin/binutils/gdb/../../../../contrib/gdb/gdb/ch-exp.c /usr/src/gnu/usr.bin/binutils/gdb/../../../../contrib/gdb/gdb/ch-lang.c /usr/src/gnu/usr.bin/binutils/gdb/../../../../contrib/gdb/gdb/ch-typeprint.c /usr/src/gnu/usr.bin/binutils/gdb/../../../../contrib/gdb/gdb/ch-valprint.c /usr/src/gnu/usr.bin/binutils/gdb/../../../../contrib/gdb/gdb/coffread.c /usr/src/gnu/usr.bin/binutils/gdb/../../../../contrib/gdb/gdb/command.c /usr/src/gnu/usr.bin/binutils/gdb/../../../../contrib/gdb/gdb/complaints.c /usr/src/gnu/usr.bin/binutils/gdb/../../../../contrib/gdb/gdb/copying.c /../../../contrib/gdb/gdb/corefile.c /usr/src/gnu/usr.bin/binutils/gdb/../../../../contrib/gdb/gdb/corelow.c /usr/src/gnu/usr.bin/binutils/gdb/../../../../contrib/gdb/gdb/core-regset.c /usr/src/gnu/usr.bin/binutils/gdb/../../../../contrib/gdb/gdb/cp-valprint.c /usr/src/gnu/usr.bin/binutils/gdb/../../../../contrib/gdb/gdb/dcache.c /usr/src/gnu/usr.bin/binutils/gdb/../../../../contrib/gdb/gdb/dbxread.c /usr/src/gnu/usr.bin/binutils/gdb/../../../../contrib/gdb/gdb/demangle.c /usr/src/gnu/usr.bin/binutils/gdb/../../../../contrib/gdb/gdb/dwarfread.c /usr/src/gnu/usr.bin/binutils/gdb/../../../../contrib/gdb/gdb/dwarf2read.c /usr/src/gnu/usr.bin/binutils/gdb/../../../../contrib/gdb/gdb/elfread.c /usr/src/gnu/usr.bin/binutils/gdb/../../../../contrib/gdb/gdb/environ.c /usr/src/gnu/usr.bin/binutils/gdb/../../../../contrib/gdb/gdb/eval.c /usr/src/gnu/usr.bin/binutils/gdb/../../../../contrib/gdb/gdb/exec.c /usr/src/gnu/usr.bin/binutils/gdb/../../../../contrib/gdb/gdb/expprint.c f-exp.c /usr/src/gnu/usr.bin/binutils/gdb/../../../../contrib/gdb/gdb/f-lang.c /usr/src/gnu/usr.bin/binutils/gdb/../../../../contrib/gdb/gdb/f-typeprint.c /usr/src/gnu/usr.bin/binutils/gdb/../../../../contrib/gdb/gdb/f-valprint.c /usr/src/gnu/usr.bin/binutils/gdb/../../../../contrib/gdb/gdb/findvar.c /usr/src/gnu/usr.bin/binutils/gdb/../../../../contrib/gdb/gdb/fork-child.c /usr/src/gnu/usr.bin/binutils/gdb/../../../../contrib/gdb/gdb/gdbarch.c /usr/src/gnu/usr.bin/binutils/gdb/../../../../contrib/gdb/gdb/gdbtypes.c /usr/src/gnu/usr.bin/binutils/gdb/../../../../contrib/gdb/gdb/infcmd.c /usr/src/gnu/usr.bin/binutils/gdb/../../../../contrib/gdb/gdb/inflow.c /usr/src/gnu/usr.bin/binutils/gdb/../../../../contrib/gdb/gdb/infptrace.c /usr/src/gnu/usr.bin/binutils/gdb/../../../../contrib/gdb/gdb/infrun.c /usr/src/gnu/usr.bin/binutils/gdb/../../../../contrib/gdb/gdb/inftarg.c /usr/src/gnu/usr.bin/binutils/gdb/../../../../contrib/gdb/gdb/language.c jv-exp.c /usr/src/gnu/usr.bin/binutils/gdb/../../../../contrib/gdb/gdb/jv-lang.c /usr/src/gnu/usr.bin/binutils/gd -valprint.c /usr/src/gnu/usr.bin/binutils/gdb/../../../../contrib/gdb/gdb/jv-typeprint.c /usr/src/gnu/usr.bin/binutils/gdb/../../../../contrib/gdb/gdb/nlmread.c /usr/src/gnu/usr.bin/binutils/gdb/../../../../contrib/gdb/gdb/m2-lang.c m2-exp.c /usr/src/gnu/usr.bin/binutils/gdb/../../../../contrib/gdb/gdb/m2-typeprint.c
Re: ata: Mount root failure: 6
It seems Alexander Langer wrote: For the archive of this ml: Some of the commits over the time since I got this error solved the problem silently. I'm now using ata this machine w/o any problem. On another machine that had problems with DMA with the old wd drivers UDMA33 now works ok, too. Nice. Thanks! You're welcome, glad to hear it finally worked for you too... -Søren To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: UPDATING
On Tue, 01 Feb 2000 13:48:57 +0600, Max Khon wrote:
2129:
{set,get}flags have been added to the tree for rather dubious
reasons. An unintended side effect of this is that you must
rebuild install before the rest of the world.
I'm surprised that this hasn't been resolved yet, but you're right;
the installworld target is still broken. Presumably, the reason for the
delay is that Joe is being very careful about testing the fix. :-)
Ciao,
Sheldon.
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message
Re: Possible IPv6-related problem
On Sun, Jan 16, 2000 at 05:40:18PM -0500, Barry Lustig wrote:
--- ipme.c.~1~ Mon Jun 15 06:53:16 1998
+++ ipme.c Sat Nov 20 18:21:26 1999
@@ -48,7 +48,7 @@
if ((s = socket(AF_INET,SOCK_STREAM,0)) == -1) return -1;
- len = 256;
+ len = 1024;
for (;;) {
if (!stralloc_ready(buf,len)) { close(s); return 0; }
buf.len = 0;
Sorry for getting back to you this late. This patch does indeed fix the
problem over here. (I still wonder why I am not seeing this problem on my home
system though. Oh well.)
It's sort of strange that this works at all with such a small buffer.
ifc.ifc_len is 568 bytes on my system here, at line 59 of ipme.c.
I built ipme standalone by sticking
main()
{
ipme_init();
}
at the end of ipme.c and doing
gcc -o ipme ipme.c str.a stralloc.a alloc.a error.a ipalloc.o
--
Jos Backus _/ _/_/_/ "Reliability means never
_/ _/ _/ having to say you're sorry."
_/ _/_/_/ -- D. J. Bernstein
_/ _/ _/_/
[EMAIL PROTECTED] _/_/ _/_/_/ use Std::Disclaimer;
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message
Re: Dell 2400 and APIC problem
After much messing around I have found the point on current where it hangs. It seems to hang during the PnP probe: isa_probe_children: probing PnP devices Is there anyway I can stop this probing of PnP devices? I have tried adding "optons PNPBIOS" to the kernel but it causes the kernel to panic. If I drop into the debugger and type panic, the kernel seems to be stuck in mp_lock. I also cant seem to get the kernel to save core. The bios doesnt have an option to disable PnP. Any ideas on what else I can do? On Mon, Jan 31, 2000 at 02:31:22PM +0200, Conrad Juleff wrote: I have a Dell 2400 with 2x 500 PIII cpu's. I cannot get an SMP kernel to run on this machine and I believe it has something to do with the Reliance/RCC chipset. It has 2 x IO APIC's and there seems to be a problem with this. I have looked at the SMP page on freebsd.org and it recommends disabling the 2nd IO APIC in the bios. The bios doesnt have this option and the vendor tells me it cannot be disabled. The machine runs fine in UP mode. I have built a kernel with DDB and debugging and stepped through it. There is a problem setting up the APIC's but I cannot save the output since it flashes past and the machine reboots. Without running boot -d the machine hangs and freezes totally after the serial ports are detected(I dont think it can be related to this) and there is nothing I can do except a reset. I have attached the output of mptable and dmesg(in UP mode). What can I do to locate the exact problem and how do I fix it? I have sent through a send-pr but have had no response. Regards Conrad === MPTable, version 2.0.15 --- MP Floating Pointer Structure: location: BIOS physical address: 0x000fe710 signature: '_MP_' length: 16 bytes version:1.4 checksum: 0x91 mode: Virtual Wire --- MP Config Table Header: physical address: 0x000f signature: 'PCMP' base table length: 468 version:1.4 checksum: 0x53 OEM ID: 'DELL' Product ID: 'POWEREDGE 9B' OEM table pointer: 0x OEM table size: 0 entry count:50 local APIC address: 0xfee0 extended table length: 88 extended table checksum:246 --- MP Config Base Table Entries: -- Processors: APIC ID Version State Family Model StepFlags 1 0x11BSP, usable 6 7 3 0x383fbff 0 0x11AP, usable 6 7 3 0x383fbff -- Bus: Bus ID Type 0 PCI 1 PCI 2 PCI 3 ISA -- I/O APICs:APIC ID Version State Address 2 0x11usable 0xfec0 3 0x11usable 0xfec01000 -- I/O Ints: TypePolarityTrigger Bus ID IRQAPIC ID PIN# ExtINT active-hiedge3 0 20 INT conformsconforms3 1 21 INT conformsconforms3 3 23 INT conformsconforms3 4 24 INT conformsconforms3 5 25 INT conformsconforms3 6 26 INT conformsconforms3 7 27 INT conformsconforms3 8 28 INT conformsconforms3 9 29 INT conformsconforms312 2 12 INT conformsconforms315 2 15 INT conformsconforms0 8:A 30 INT conformsconforms1 6:A 3 14 INT conformsconforms1 4:A 3 15 INT conformsconforms2 6:A 3 12 INT conformsconforms2 6:C 3 12 INT conformsconforms2 6:B 3 13 INT conformsconforms2 6:D 3 13 INT conformsconforms2 8:A 3 10 INT conformsconforms
Re: Dell 2400 and APIC problem
* Conrad Juleff [EMAIL PROTECTED] [000201 04:13] wrote: After much messing around I have found the point on current where it hangs. It seems to hang during the PnP probe: isa_probe_children: probing PnP devices Is there anyway I can stop this probing of PnP devices? I have tried adding "optons PNPBIOS" to the kernel but it causes the kernel to panic. If I drop into the debugger and type panic, the kernel seems to be stuck in mp_lock. I also cant seem to get the kernel to save core. The bios doesnt have an option to disable PnP. Any ideas on what else I can do? Hmm, it seems a lot of the devices in GENERIC have flags to disable PnP probes (see LINT), maybe you can try a custom kernel to install, or try using the kernel config to set the appropriate flags on each device to disable pnp probing. -Alfred To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: HEADS UP: GNU grep 2.4d
Thus spake Max Khon ([EMAIL PROTECTED]): It was a local FreeBSD feature; now it is part of the official GNU grep. Any chance of -R coming back too? it is already there (-r) Hmm. Somehow I dislike name-changes of params. :-( Alex -- I doubt, therefore I might be. To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: UPDATING
On Tue, 1 Feb 19100, Sheldon Hearn wrote:
2129:
{set,get}flags have been added to the tree for rather dubious
reasons. An unintended side effect of this is that you must
rebuild install before the rest of the world.
I'm surprised that this hasn't been resolved yet, but you're right;
the installworld target is still broken.
Kewl, then ignore the report I was about to make about b0rken installworld.
Just one problem, when I follow the instructions, in usr.bin/xinstall,
make depend all install clean ...
Then make installworld with my configuration dies in
install -c -o root -g wheel -m 444 install.1.gz /usr/share/man/man1
install: install.1.gz: No such file or directory
(Of course I can work around that, and if there's been discussion
of this already, I haven't looked back far enough just yet)
thanks,
barry bouwsma, tele danmork internet
(use reply-to header if needed, from is b0rked)
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message
Re: UPDATING
* I am not any sort of Fluffy [EMAIL PROTECTED] [000201 04:44]
wrote:
On Tue, 1 Feb 19100, Sheldon Hearn wrote:
2129:
{set,get}flags have been added to the tree for rather dubious
reasons. An unintended side effect of this is that you must
rebuild install before the rest of the world.
I'm surprised that this hasn't been resolved yet, but you're right;
the installworld target is still broken.
Kewl, then ignore the report I was about to make about b0rken installworld.
Just one problem, when I follow the instructions, in usr.bin/xinstall,
make depend all install clean ...
Then make installworld with my configuration dies in
install -c -o root -g wheel -m 444 install.1.gz /usr/share/man/man1
install: install.1.gz: No such file or directory
(Of course I can work around that, and if there's been discussion
of this already, I haven't looked back far enough just yet)
um, why are you cleaning?
Obviously the install is failing when you wipe out the binaries it
wants to install.
-Alfred
thanks,
barry bouwsma, tele danmork internet
(use reply-to header if needed, from is b0rked)
If the offensive 'from' is broken, then why use it at all?
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message
Re: HEADS UP: GNU grep 2.4d
hi, there! On Tue, 1 Feb 2000, Alexander Langer wrote: It was a local FreeBSD feature; now it is part of the official GNU grep. Any chance of -R coming back too? it is already there (-r) Hmm. Somehow I dislike name-changes of params. :-( GREP guys decided to use -r (which was absent in grep 2.0). -a changed its behavior to opposite also. /fjoe To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: UPDATING
On Tue, 1 Feb 19100, Alfred Perlstein wrote: Just one problem, when I follow the instructions, in usr.bin/xinstall, make depend all install clean ... um, why are you cleaning? Just blindly following the instructions in UPDATING... But at the wrong place, before the `make installworld', instead of starting again at `make buildworld'... Obviously the install is failing when you wipe out the binaries it wants to install. Never mind me, I'll just sit quietly in the corner now To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
boot2.c
I think I've just stumbled over a little problem with boot2.c in -current. If I boot a kernel directly from boot2 rather than through the loader, the root filesystem gets mounted as the old-style wd0s1a rather than the new ad0a (or whatever). This means that init gets somewhat upset if /etc/fstab has / as /dev/ad0a. :-) Given that the old wd driver is now deprecated, the correct fix is presumably just to change "wd" to "ad" on line 91 of src/sys/boot/i386/boot2/boot2.c? Chris. -- Chris Webb [EMAIL PROTECTED] Office: +44 1299 404075 Arachsys Internet Services LtdMobile: +44 7801 090045 To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
On a lighter note... how-to upgrade (Version 2)
In my origional version, I forgot the "make includes" line --- which has frustrated a few friends, so: Source Upgrade 3.4 to 4.x, Version 2: I have followed the UPDATES file... and I have source-make-world upgraded several machines from 3.3 and 3.4 to 4.0-CURRENT recently. I thought I'd contribute a method that is reasonably likely to work and reasonably likely to not be going overboard. Someone should maintain a file like this. (Bootstrap) cd /usr/src make includes (generate things needed to make kernel) make all-install usr.sbin/config make all-install usr.bin/genassym (it appears that a lot of things don't work right until the new kernel is in place, and it can be installed first) make 4.0 kernel reboot with 4.0 kernel (remember de-dc change and other device name changes.) (you will have trouble with root not being fsck'd if you crash in here requiring manual intervention. This goes away after you makedev your disks again.) (bootstap compile process) make all-install 1) lib/libc 2) lib/util 3) lib/kvm and usr.bin/top (if you like to watch things run) 4) usr.sbin/yacc 5) gnu/usr.bin/cc make world cp /usr/src/etc/MAKEDEV /dev; cd /dev; MAKEDEV all std (you might also want to MAKEDEV any disk devices that you like) reboot (Paranoia?) make kernel again make world again reboot again The only problem I've run into ... and it was a system that had been source upgraded repeatedly from somewhere back around 2.2.5 ... was that I had a /usr/local/bin/makeinfo lying around that caused trouble for the gnu/usr.bin/cc build. Dave. -- |David Gilbert, Velocet Communications. | Two things can only be | |Mail: [EMAIL PROTECTED] | equal if and only if they | |http://www.velocet.net/~dgilbert | are precisely opposite. | =GLO To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: HEADS UP: GNU grep 2.4d
On Mon, Jan 31, 2000 at 08:28:30PM +0200, Ruslan Ermilov wrote: Yes, that's why all this fuss have taken place ;=) WOOHOO! I agree with Alex Langer, though. -R - -r gets on my nerves. But I suppose it is consistent with `rm`, just not `cp`.. hmm, consistency. -- Will Andrews [EMAIL PROTECTED] GCS/E/S @d- s+:++:- a---+++ C++ UB P+ L- E--- W+++ !N !o ?K w--- ?O M+ V-- PS+ PE++ Y+ PGP t++ 5 X++ R+ tv+ b++ DI+++ D+ G+ e- h! r--+++ y? To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: Dell 2400 and APIC problem
On Tue, Feb 01, 2000 at 04:19:55AM -0800, Alfred Perlstein wrote: Is there anyway I can stop this probing of PnP devices? I have tried adding "optons PNPBIOS" to the kernel but it causes the kernel to panic. If I drop into the debugger and type panic, the kernel seems to be stuck in mp_lock. I also cant seem to get the kernel to save core. The bios doesnt have an option to disable PnP. Any ideas on what else I can do? Hmm, it seems a lot of the devices in GENERIC have flags to disable PnP probes (see LINT), maybe you can try a custom kernel to install, or try using the kernel config to set the appropriate flags on each device to disable pnp probing. I have tried doing this on -current but it doesnt make any difference. I have also removed every non-essential item out of the kernel. I am using boot -dv with "options DIAGNOSTIC" in the kernel and it doesnt tell me what the PnP probe is hanging on. Any other suggestions? To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: HEADS UP: GNU grep 2.4d
On Tue, Feb 01, 2000 at 08:24:41AM -0500, Will Andrews wrote: On Mon, Jan 31, 2000 at 08:28:30PM +0200, Ruslan Ermilov wrote: Yes, that's why all this fuss have taken place ;=) WOOHOO! I agree with Alex Langer, though. -R - -r gets on my nerves. But I suppose it is consistent with `rm`, just not `cp`.. hmm, consistency. In fact, it is consistent with GNU grep ;=) Old -a and -R were FreeBSD extensions that have gone now. -- Ruslan Ermilov Sysadmin and DBA of the [EMAIL PROTECTED]United Commercial Bank, [EMAIL PROTECTED] FreeBSD committer, +380.652.247.647Simferopol, Ukraine http://www.FreeBSD.org The Power To Serve http://www.oracle.com Enabling The Information Age To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: HEADS UP: GNU grep 2.4d
Thus spake Ruslan Ermilov ([EMAIL PROTECTED]): I agree with Alex Langer, though. -R - -r gets on my nerves. But I suppose it is consistent with `rm`, just not `cp`.. hmm, consistency. In fact, it is consistent with GNU grep ;=) Old -a and -R were FreeBSD extensions that have gone now. That's why we all don't like the GNU folks *duck* ;-) Alex -- I doubt, therefore I might be. To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: Make world problems
On Tue, Feb 01, 2000 at 03:34:51AM +0100, Marc Schneiders wrote: As far as this is possible for me in rather heterogenous threads, I've tried to follow the messages about recent make world problems. I've done exactly what is in src/UPDATING (and like another poster here I did *not* get the 24/01/2000 message until today...): build and install (x)install, make buildworld, installworld, distrib dirs, kernel. Some problems have disappeared, some remain, to wit: /kernel: cmd ntpd pid 86 tried to use non-present sched_get_priority_max /kernel: cmd ntpd pid 86 tried to use non-present sched_setscheduler ntpd [86]: sched_setscheduler(): Function not implemented This shouldn't (IIR comments to this list C) affect ntp, but if you want the nasty messages to go away, include: options P1003_1B options _KPOSIX_PRIORITY_SCHEDULING options _KPOSIX_VERSION=199309L in your kernel config. -- Mike Bristow, Geek At Large ``Beware of Invisible Cows'' To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
[LONG] Successful install report
Hello, I've installed a recent snapshot on an oldish P5-75 HP PC : here is the verbose dmesg (at the end, there seems to be some problems linked to ipsec) Jan 31 19:20:23 pc249 /kernel: Copyright (c) 1992-2000 The FreeBSD Project. Jan 31 19:20:23 pc249 /kernel: Copyright (c) 1982, 1986, 1989, 1991, 1993 Jan 31 19:20:23 pc249 /kernel: The Regents of the University of California. All rights reserved. Jan 31 19:20:23 pc249 /kernel: FreeBSD 4.0-2127-CURRENT #0: Wed Jan 31 19:11 :17 CET 1990 Jan 31 19:20:23 pc249 /kernel: [EMAIL PROTECTED]:/usr/s rc/sys/compile/P5-lnc Jan 31 19:20:23 pc249 /kernel: Calibrating clock(s) ... TSC clock: 75003346 Hz, i8254 clock: 1193236 Hz Jan 31 19:20:23 pc249 /kernel: CLK_USE_I8254_CALIBRATION not specified - using d efault frequency Jan 31 19:20:23 pc249 /kernel: Timecounter "i8254" frequency 1193182 Hz Jan 31 19:20:23 pc249 /kernel: CLK_USE_TSC_CALIBRATION not specified - using old calibration method Jan 31 19:20:23 pc249 /kernel: Timecounter "TSC" frequency 75000774 Hz Jan 31 19:20:23 pc249 /kernel: CPU: Pentium/P54C (75.00-MHz 586-class CPU) Jan 31 19:20:23 pc249 /kernel: Origin = "GenuineIntel" Id = 0x525 Stepping = 5 Jan 31 19:20:23 pc249 /kernel: Features=0x1bfFPU,VME,DE,PSE,TSC,MSR,MCE,CX8 Jan 31 19:20:23 pc249 /kernel: real memory = 25165824 (24576K bytes) Jan 31 19:20:23 pc249 /kernel: Physical memory chunk(s): Jan 31 19:20:23 pc249 /kernel: 0x1000 - 0x0009efff, 647168 bytes (158 pages) Jan 31 19:20:23 pc249 /kernel: 0x002bb000 - 0x017fdfff, 22294528 bytes (5443 pag es) Jan 31 19:20:23 pc249 /kernel: config q Jan 31 19:20:23 pc249 /kernel: avail memory = 21901312 (21388K bytes) Jan 31 19:20:23 pc249 /kernel: bios32: Found BIOS32 Service Directory header at 0xc00fd710 Jan 31 19:20:23 pc249 /kernel: bios32: Entry = 0xfd6e0 (c00fd6e0) Rev = 0 Len = 1 Jan 31 19:20:23 pc249 /kernel: pcibios: PCI BIOS entry at 0xd720 Jan 31 19:20:23 pc249 /kernel: pnpbios: Found PnP BIOS data at 0xc00f0c90 Jan 31 19:20:23 pc249 /kernel: pnpbios: Entry = f:b1d Rev = 1.0 Jan 31 19:20:23 pc249 /kernel: Other BIOS signatures found: Jan 31 19:20:23 pc249 /kernel: ACPI: Jan 31 19:20:23 pc249 /kernel: Preloaded elf kernel "kernel" at 0xc02a2000. Jan 31 19:20:23 pc249 /kernel: Preloaded userconfig_script "/boot/kernel.conf" a t 0xc02a209c. Jan 31 19:20:23 pc249 /kernel: Intel Pentium detected, installing workaround for F00F bug Jan 31 19:20:23 pc249 /kernel: md0: Malloc disk Jan 31 19:20:23 pc249 /kernel: pci_open(1): mode 1 addr port (0x0cf8) is 0x8 068 Jan 31 19:20:23 pc249 /kernel: pci_open(1a):mode1res=0x8000 (0x8000) Jan 31 19:20:23 pc249 /kernel: pci_cfgcheck:device 0 [class=06] [hdr=00] is there (id=00071004) Jan 31 19:20:23 pc249 /kernel: npx0: math processor on motherboard Jan 31 19:20:23 pc249 /kernel: npx0: INT 16 interface Jan 31 19:20:24 pc249 /kernel: i586_bzero() bandwidth = 79032640 bytes/sec Jan 31 19:20:24 pc249 /kernel: bzero() bandwidth = 39791492 bytes/sec Jan 31 19:20:24 pc249 /kernel: pci_open(1): mode 1 addr port (0x0cf8) is 0x0 000 Jan 31 19:20:24 pc249 /kernel: pci_open(1a):mode1res=0x8000 (0x8000) Jan 31 19:20:24 pc249 /kernel: pci_cfgcheck:device 0 [class=06] [hdr=00] is there (id=00071004) Jan 31 19:20:24 pc249 /kernel: pcib0: Host to PCI bridge on motherboard Jan 31 19:20:24 pc249 /kernel: found- vendor=0x1004, dev=0x0007, revid=0x01 Jan 31 19:20:24 pc249 /kernel: class=06-00-00, hdrtype=0x00, mfdev=0 Jan 31 19:20:24 pc249 /kernel: subordinatebus=0 secondarybus=0 Jan 31 19:20:24 pc249 /kernel: found- vendor=0x1004, dev=0x0008, revid=0x01 Jan 31 19:20:24 pc249 /kernel: class=06-01-00, hdrtype=0x00, mfdev=0 Jan 31 19:20:24 pc249 /kernel: subordinatebus=0 secondarybus=0 Jan 31 19:20:24 pc249 /kernel: found- vendor=0x1013, dev=0x00a8, revid=0xfc Jan 31 19:20:24 pc249 /kernel: class=03-00-00, hdrtype=0x00, mfdev=0 Jan 31 19:20:24 pc249 /kernel: subordinatebus=0 secondarybus=0 Jan 31 19:20:24 pc249 /kernel: map[10]: type 1, range 32, base fd00, size 24 Jan 31 19:20:24 pc249 /kernel: found- vendor=0x1022, dev=0x2000, revid=0x02 Jan 31 19:20:24 pc249 /kernel: class=02-00-00, hdrtype=0x00, mfdev=0 Jan 31 19:20:24 pc249 /kernel: subordinatebus=0 secondarybus=0 Jan 31 19:20:24 pc249 /kernel: intpin=a, irq=10 Jan 31 19:20:24 pc249 /kernel: map[10]: type 1, range 32, base ffe0, size 5 Jan 31 19:20:24 pc249 /kernel: found- vendor=0x1095, dev=0x0640, revid=0x02 Jan 31 19:20:24 pc249 /kernel: class=01-01-00, hdrtype=0x00, mfdev=0 Jan 31 19:20:24 pc249 /kernel: subordinatebus=0 secondarybus=0 Jan 31 19:20:24 pc249 /kernel: intpin=a, irq=14 Jan 31 19:20:24 pc249 /kernel: pci0: PCI bus on pcib0 Jan 31 19:20:24 pc249 /kernel: isab0: PCI to ISA bridge (vendor=1004 device=000 8) at device 1.0 on pci0 Jan 31 19:20:24 pc249 /kernel: isa0: ISA bus on isab0 Jan 31 19:20:24 pc249 /kernel: vga-pci0: Cirrus Logic GD5434 SVGA controller m em
Re: UPDATING
hi, there! On Tue, 1 Feb 2000, Sheldon Hearn wrote: Just one problem, when I follow the instructions, in usr.bin/xinstall, make depend all install clean ... Then make installworld with my configuration dies in install -c -o root -g wheel -m 444 install.1.gz /usr/share/man/man1 install: install.1.gz: No such file or directory You're not following the instructions. :-) The instructions say you must "make depend all install clean before make world or buildworld" -- you're doing it _after_ buildworld. actually instructions are wrong. you can't build xinstall before `make buildworld' now with old libc. /fjoe To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: UPDATING
Max Khon [EMAIL PROTECTED] writes: actually instructions are wrong. you can't build xinstall before `make buildworld' now with old libc. Yep, I have to do buildworld _first_, then build xinstall _without_ cleaning, then make a installworld. -- Eric Jacoboni Ta mère, son mot de passe c'est « toto » ! To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: ftpd now cores
In ftpd.c inithosts() there is a getaddrinfo() that can fail with TRY_AGAIN. Afterwards there is an if that checks to see if res is a null pointer before using it. A little later there is a freeaddrinfo(res) that will core in this case. I changed the line toif (res) freeaddrinfo(res) and all is well. Thanks! I'll include the fix. Yoshinobu Inoue Later Mark Hittinger Mindspring/Netcom/Dallas [EMAIL PROTECTED] To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: [LONG] Successful install report
Hello, I've installed a recent snapshot on an oldish P5-75 HP PC : here is the verbose dmesg (at the end, there seems to be some problems linked to ipsec) Those ipsec related error messages are just too verbose and not harmful. And I believe those message are printed only at debug mode after revision 1.76 of inetd.c (after Jan 25). Cheers, Yoshinobu Inoue To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: Make world problems
Marc Schneiders wrote: As far as this is possible for me in rather heterogenous threads, I've tried to follow the messages about recent make world problems. I've done exactly what is in src/UPDATING (and like another poster here I did *not* get the 24/01/2000 message until today...): build and install (x)install, make buildworld, installworld, distrib dirs, kernel. Some problems have disappeared, some remain, to wit: /kernel: cmd ntpd pid 86 tried to use non-present sched_get_priority_max /kernel: cmd ntpd pid 86 tried to use non-present sched_setscheduler ntpd [86]: sched_setscheduler(): Function not implemented (I've checked, ntpd was built.) And when doing startx: /usr/libexec/ld-elf.so.1: /usr/lib/libstdc++.so.3: Undefined symbol "_vt$9exception" My problem was with kde11 and family. I switched back to twm in xinitrc and X worked as expected and then removed all kde with pkg_delete, rebuilt many dependencies, just in case, such as qt, graphics libs, etc and then rebuilt kde11 and it works fine and I did it all while using twm. I changed from twm back to kde and everything works. I am still having problems with apache and ssl. I could use some suggestions. Thanks, ed This looks very much like the example in UPDATING. Does this mean I have to rebuild X ?? And libstdc++.so.3 was built as part of the make world... Forgive me for not understanding. (Unrelated are probably the following messages: inetd[117]: IPv6 for RPC is not supported yet network_pass4: not found) Any help appreciated. Additional info: SMP kernel (irrrelevant, I presume), last build before this three weeks ago, cvsup January 31, 15:45 GMT, from Dutch mirror. -- Marc Schneiders [EMAIL PROTECTED] [EMAIL PROTECTED] [EMAIL PROTECTED] 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
wired devices under current?
Howdy, I've got -current and -stable both on one disk, and I'm able to wire that disk to da0 when there's a lower ID'ed drive on the bus with no problems under -stable. But the comments in -current's LINT config file appear to be out of date. If I say device da0 at scbus0 target 1 config complains that scbus 0 is not defined. -stable's LINT has `controller scbus0', while -current has just `scbus'. Similarly if I say device scbus0 at ahc0 then config complains about ahc 0 not defined. If I make it just ahc, then I get a syntax error. What's the correct way to define this? And if so, would someone care to update LINT's examples to reflect this? I've gone ahead and made `controller scbus' into `scbus0' which satisfies config, and I'm now about to try it out and see if it gives the desired results... No. It didn't. So then, how to do it, or have I overlooked something when customizing the kernel? thanks, barry bouwsma, tele danmrk internet To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: Dell 2400 and APIC problem
I have tried doing this on -current but it doesnt make any difference. I have also removed every non-essential item out of the kernel. I am using boot -dv with "options DIAGNOSTIC" in the kernel and it doesnt tell me what the PnP probe is hanging on. Any other suggestions? I don't think it's pnp probing. You don't seem to have any pnp devices at all from your dmesg output. Could you do a 'pnpinfo' and verify if it is indeed the case? Isa bus is the last bus probed, and immediately (well, almost) follows that configure hooks with interrupt enabled. That is also the first time BSP gives up mplock, and the APs have a chance to initialize themselves. I believe that is where it hangs. Just to make sure, do you have "options NAPIC 2" in your kernel config? The default is 1, so you absolutely need this line for things to work. -lq To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: UPDATING
In message [EMAIL PROTECTED] Max Khon writes: : actually instructions are wrong. : you can't build xinstall before `make buildworld' now with old libc. I've seen multiple, conflicting reports on this. I've not personally hit this bug. What's the exact sequence one must do? Warner To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Mapping files into kernel memory space
Hi! I am writing an FS driver, and i need often to compose some FS internal information from fragments. The first idea was to malloc a poll and copy data from buffers, returned by bread(). But it seems to me simplier to write VOP_BMAP, VOP_STRATEGY, and then map needed portion into kernel space. I suppose there is no major problems, isn't it? So the question is: Is it a good idea at all? Will it be faster/slower? Good luck. To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: UPDATING
On Tue, Feb 01, 2000 at 12:11:51PM -0700, Warner Losh wrote: In message [EMAIL PROTECTED] Max Khon writes: : actually instructions are wrong. : you can't build xinstall before `make buildworld' now with old libc. I've seen multiple, conflicting reports on this. I've not personally hit this bug. What's the exact sequence one must do? The old /usr/bin/install will fail right after new libutil gets installed. But at this point, we will already have new libc in /usr/lib. So, if the installworld fails, we need to install new "install" with itself: cd src/usr.bin/xinstall make install INSTALL=/usr/obj/usr/src/usr.bin/xinstall/xinstall And then repeat installworld again. There is no need to repeat this procedure every time, just once, and only if installworld fails ;=) -- Ruslan Ermilov Sysadmin and DBA of the [EMAIL PROTECTED]United Commercial Bank, [EMAIL PROTECTED] FreeBSD committer, +380.652.247.647Simferopol, Ukraine http://www.FreeBSD.org The Power To Serve http://www.oracle.com Enabling The Information Age To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: UPDATING
On Tue, 1 Feb 19100, Warner Losh wrote: : you can't build xinstall before `make buildworld' now with old libc. I've seen multiple, conflicting reports on this. I've not personally hit this bug. What's the exact sequence one must do? Here's what *did* work for me: * make buildworld. (sleep, I have a slow machine, one reason I didn't want to do it again if I could help it) * make xinstall, following the UPDATING instructions, but *without* the `clean'... * make installworld. Voila. Oops, I've just given the answer to the question you asked in the other message... Bah. barry bouwsma, tele danmork internet To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
errors running make DESTDIR
When i run: make DESTDIR=/var/tmp/root-000201 distrib-dirs distribution, the last thing i get (and this same line is printed several times) is: usage: mknod name [b | c] major minor What can I do to resolve this? To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
4.0 release cosmetics: ftpd
Feb 1 18:21:44 propro ftpd[676]: no modules loaded for `ftpd' service Feb 1 18:21:44 propro ftpd[676]: auth_pam: Permission denied This error message has been there for a long time, when I ftp from one box to another (anonymous ftp not enabled). I think I saw a message some time ago that it doesn't hurt. If it is not my fault, it may be an idea to look into it before 4.0 is released as release. I am utterly incompetent to do this :-) Might save some questions on questions. IIRC there is a pr-report about this, which is marked closed, for stable. -- Marc Schneiders [EMAIL PROTECTED] [EMAIL PROTECTED] [EMAIL PROTECTED] To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: Make world problems
On Tue, 1 Feb 2000, Edwin Culp wrote: Marc Schneiders wrote: As far as this is possible for me in rather heterogenous threads, I've tried to follow the messages about recent make world problems. I've done exactly what is in src/UPDATING (and like another poster here I did *not* get the 24/01/2000 message until today...): build and install (x)install, make buildworld, installworld, distrib dirs, kernel. Some problems have disappeared, some remain, to wit: [...] And when doing startx: /usr/libexec/ld-elf.so.1: /usr/lib/libstdc++.so.3: Undefined symbol "_vt$9exception" My problem was with kde11 and family. I switched back to twm in xinitrc and X worked as expected and then removed all kde with pkg_delete, rebuilt many dependencies, just in case, such as qt, graphics libs, etc and then rebuilt kde11 and it works fine and I did it all while using twm. I changed from twm back to kde and everything works. Yes! "rm .xinitrc" was all I had to do. Thanks very much. A good opportunity to try another windowmanager or build a newer kde. The one I have came with 3.1 I think :-) I am still having problems with apache and ssl. I could use some suggestions. Thanks, ed This looks very much like the example in UPDATING. Does this mean I have to rebuild X ?? And libstdc++.so.3 was built as part of the make world... Forgive me for not understanding. [...] -- Marc Schneiders [EMAIL PROTECTED] [EMAIL PROTECTED] [EMAIL PROTECTED] To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
rpc.rstatd
As far as I can see nothing changed about rpc.rstatd. And there are
no error messages at startup (and it is uncommented in
/etc/inetd.conf and lo0 is in rc.conf). It is not working however:
propro:marc {104} rup propro
rup: propro : RPC: Program not registered
Nfs is working, but when unmounting a filesystem (on this host on
another) it says:
umount: can't get net id for host.
This error is vice versa, I mean it works the other way around, when
umounting a nfs-filesystem on another host on this host. On the other
host (also running 4.0, but of 11 January) 'rup' does work however.
--
Marc Schneiders
[EMAIL PROTECTED]
[EMAIL PROTECTED]
[EMAIL PROTECTED]
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message
Re: UPDATING
I did the following and it worked for me: cd /usr/src make buildworld make installworld cd /usr/src/usr.bin/xinstall make install cd /usr/src make installworld The first make installworld terminates with an errors, but the second on goes through. I don't see any reason why the following wouldn't work as well: cd /usr/src make buildworld cd /usr/src/usr.bin/xinstall make install cd /usr/src make installworld I just NFS mounted a completed buildworld on my laptop (which had a two week old -current) and I am trying this as I type. It is a slow machine, so it might take a while. I'll post an update when it completes. Jim Bloom [EMAIL PROTECTED] Warner Losh wrote: In message [EMAIL PROTECTED] Max Khon writes: : actually instructions are wrong. : you can't build xinstall before `make buildworld' now with old libc. I've seen multiple, conflicting reports on this. I've not personally hit this bug. What's the exact sequence one must do? Warner To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Nasty messages from ATA
Yesterday, I upgraded my system from mid-Jan to the latest (cvs-cur.6044) to see if it would cure some hard-hangs. Last night, I got the following messages: Feb 1 18:00:21 gsmx07 /kernel: ad2: ad_timeout: lost disk contact - resetting Feb 1 18:00:21 gsmx07 /kernel: ata1: resetting devices .. done Feb 1 18:00:21 gsmx07 /kernel: ad0: ad_timeout: lost disk contact - resetting Feb 1 18:00:21 gsmx07 /kernel: ata0: resetting devices .. ata0-slave: timeout waiting for command=ef s=00 e=64 Feb 1 18:00:21 gsmx07 /kernel: done Feb 1 18:05:40 gsmx07 /kernel: ad2: ad_timeout: lost disk contact - resetting Feb 1 18:05:40 gsmx07 /kernel: ata1: resetting devices .. done Feb 1 18:05:40 gsmx07 /kernel: ad0: ad_timeout: lost disk contact - resetting Feb 1 18:05:40 gsmx07 /kernel: ata0: resetting devices .. ata0-slave: timeout waiting for command=ef s=00 e=64 Feb 1 18:05:40 gsmx07 /kernel: done The system should have been virtually quiescent at this time. Any suggestions? I am running soft-updates. Relevant config lines: device ata0at isa? port IO_WD1 irq 14 device ata1at isa? port IO_WD2 irq 15 device ata device atadisk # ATA disk drives device atapicd # ATAPI CDROM drives options ATA_STATIC_ID #Static device numbering Complete kernel boot messages: Feb 1 11:49:37 gsmx07 /kernel: Copyright (c) 1992-2000 The FreeBSD Project. Feb 1 11:49:38 gsmx07 /kernel: Copyright (c) 1982, 1986, 1989, 1991, 1993 Feb 1 11:49:38 gsmx07 /kernel: The Regents of the University of California. All rights reserved. Feb 1 11:49:38 gsmx07 /kernel: FreeBSD 4.0-CURRENT #26: Tue Feb 1 11:35:57 EST 2000 Feb 1 11:49:38 gsmx07 /kernel: root@:/3.0/cvs/src/sys/compile/gsmx Feb 1 11:49:38 gsmx07 /kernel: Timecounter "i8254" frequency 1193182 Hz Feb 1 11:49:38 gsmx07 /kernel: Timecounter "TSC" frequency 267309469 Hz Feb 1 11:49:38 gsmx07 /kernel: CPU: Pentium II/Pentium II Xeon/Celeron (267.31-MHz 686-class CPU) Feb 1 11:49:38 gsmx07 /kernel: Origin = "GenuineIntel" Id = 0x633 Stepping = 3 Feb 1 11:49:38 gsmx07 /kernel: Features=0x80f9ffFPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,SEP,MTRR,PGE,MCA,CMOV,MMX Feb 1 11:49:38 gsmx07 /kernel: real memory = 67108864 (65536K bytes) Feb 1 11:49:38 gsmx07 /kernel: avail memory = 61902848 (60452K bytes) Feb 1 11:49:38 gsmx07 /kernel: Preloaded elf kernel "kernel" at 0xc030c000. Feb 1 11:49:38 gsmx07 /kernel: VESA: v2.0, 4096k memory, flags:0x1, mode table:0xc02ba922 (122) Feb 1 11:49:38 gsmx07 /kernel: VESA: Matrox Graphics Inc. Feb 1 11:49:38 gsmx07 /kernel: Pentium Pro MTRR support enabled Feb 1 11:49:38 gsmx07 /kernel: npx0: math processor on motherboard Feb 1 11:49:38 gsmx07 /kernel: npx0: INT 16 interface Feb 1 11:49:38 gsmx07 /kernel: pcib0: Intel 82443LX (440 LX) host to PCI bridge on motherboard Feb 1 11:49:38 gsmx07 /kernel: pci0: PCI bus on pcib0 Feb 1 11:49:38 gsmx07 /kernel: pcib1: Intel 82443LX (440 LX) PCI-PCI (AGP) bridge at device 1.0 on pci0 Feb 1 11:49:38 gsmx07 /kernel: pci1: PCI bus on pcib1 Feb 1 11:49:38 gsmx07 /kernel: isab0: Intel 82371AB PCI to ISA bridge at device 7.0 on pci0 Feb 1 11:49:38 gsmx07 /kernel: isa0: ISA bus on isab0 Feb 1 11:49:38 gsmx07 /kernel: ata-pci0: Intel PIIX4 ATA-33 controller port 0xf000-0xf00f at device 7.1 on pci0 Feb 1 11:49:38 gsmx07 /kernel: ata0 at 0x01f0 irq 14 on ata-pci0 Feb 1 11:49:38 gsmx07 /kernel: ata1 at 0x0170 irq 15 on ata-pci0 Feb 1 11:49:38 gsmx07 /kernel: pci0: Intel 82371AB/EB (PIIX4) USB controller (vendor=0x8086, dev=0x7112) at 7.2 irq 11 Feb 1 11:49:38 gsmx07 /kernel: chip1: Intel 82371AB Power management controller port 0x5f00-0x5f0f at device 7.3 on pci0 Feb 1 11:49:38 gsmx07 /kernel: vga-pci0: Matrox MGA Millennium II 2164W graphics accelerator mem 0xe500-0xe57f,0xe580-0xe5803fff,0xe400 -0xe4ff irq 10 at device 9.0 on pci0 Feb 1 11:49:38 gsmx07 /kernel: tx0: SMC 83c170 port 0x6800-0x68ff mem 0xe5804000-0xe5804fff irq 9 at device 10.0 on pci0 Feb 1 11:49:38 gsmx07 /kernel: tx0: address 00:e0:29:24:34:1f, type SMC9432TX, Auto-Neg 100Mbps Feb 1 11:49:38 gsmx07 /kernel: tx0: driver is using old-style compatability shims Feb 1 11:49:38 gsmx07 /kernel: ed0 at port 0x300-0x31f iomem 0xcc000-0xc irq 7 on isa0 Feb 1 11:49:38 gsmx07 /kernel: ed0: address 00:00:c0:57:99:47, type WD8013EPC (16 bit) Feb 1 11:49:38 gsmx07 /kernel: atkbdc0: keyboard controller (i8042) at port 0x60-0x6f on isa0 Feb 1 11:49:38 gsmx07 /kernel: atkbd0: AT Keyboard irq 1 on atkbdc0 Feb 1 11:49:38 gsmx07 /kernel: psm0: PS/2 Mouse irq 12 on atkbdc0 Feb 1 11:49:38 gsmx07 /kernel: psm0: model Generic PS/2 mouse, device ID 0 Feb 1 11:49:38 gsmx07 /kernel: vga0: Generic ISA VGA at port 0x3c0-0x3df iomem 0xa-0xb on isa0 Feb 1 11:49:38 gsmx07 /kernel: sc0: System console on isa0 Feb 1 11:49:38 gsmx07 /kernel: sc0: VGA 16 virtual consoles, flags=0x200 Feb 1 11:49:38 gsmx07 /kernel: ata-isa0:
xinstall
I keep seeing stuff about xinstall on this list, but I haven't read anything about it anywhere in any of the docs. What is it and should I know about it? To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: Nasty messages from ATA
It seems Peter Jeremy wrote: Yesterday, I upgraded my system from mid-Jan to the latest (cvs-cur.6044) to see if it would cure some hard-hangs. Last night, I got the following messages: Feb 1 18:00:21 gsmx07 /kernel: ad2: ad_timeout: lost disk contact - resetting Feb 1 18:00:21 gsmx07 /kernel: ata1: resetting devices .. done Feb 1 18:00:21 gsmx07 /kernel: ad0: ad_timeout: lost disk contact - resetting Feb 1 18:00:21 gsmx07 /kernel: ata0: resetting devices .. ata0-slave: timeout waiting for command=ef s=00 e=64 Feb 1 18:00:21 gsmx07 /kernel: done Feb 1 18:05:40 gsmx07 /kernel: ad2: ad_timeout: lost disk contact - resetting Feb 1 18:05:40 gsmx07 /kernel: ata1: resetting devices .. done Feb 1 18:05:40 gsmx07 /kernel: ad0: ad_timeout: lost disk contact - resetting Feb 1 18:05:40 gsmx07 /kernel: ata0: resetting devices .. ata0-slave: timeout waiting for command=ef s=00 e=64 Feb 1 18:05:40 gsmx07 /kernel: done The system should have been virtually quiescent at this time. Any suggestions? I am running soft-updates. Feb 1 11:49:38 gsmx07 /kernel: ad0: 6187MB FUJITSU MPB3064ATU E [13410/15/63] at ata0-master using UDMA33 Feb 1 11:49:38 gsmx07 /kernel: ad2: 1222MB QUANTUM FIREBALL_TM1280A [2484/16/63] at ata1-master using WDMA2 Try to switch of DMA on ad2 with the systel like documented ata.4 and see if that helps... -Søren To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: UPDATING
The method below worked just fine on my laptop. I can't guarantee how it will do on a 3.x system for upgrading. Also, if a kernel is being installed, it must be done before installing install or after the installworld. Jim Bloom [EMAIL PROTECTED] Jim Bloom wrote: I don't see any reason why the following wouldn't work as well: cd /usr/src make buildworld cd /usr/src/usr.bin/xinstall make install cd /usr/src make installworld I just NFS mounted a completed buildworld on my laptop (which had a two week old -current) and I am trying this as I type. It is a slow machine, so it might take a while. I'll post an update when it completes. To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: 4.0 release cosmetics: ftpd
On Tue, 1 Feb 2000, Will Saxon wrote: All you have to do is add a line to your /etc/pam.conf to fix this, I have: ftpdauthrequiredpam_unix.so try_first_pass Thanks for your help. This does the trick. although I'm sure there is a more general/better way to do it. Any way is better than just leaving it and wondering every time :-) And it does not look good for a release. On Tue, 1 Feb 2000, Marc Schneiders wrote: Feb 1 18:21:44 propro ftpd[676]: no modules loaded for `ftpd' service Feb 1 18:21:44 propro ftpd[676]: auth_pam: Permission denied This error message has been there for a long time, when I ftp from one box to another (anonymous ftp not enabled). I think I saw a message some time ago that it doesn't hurt. If it is not my fault, it may be an idea to look into it before 4.0 is released as release. I am utterly incompetent to do this :-) Might save some questions on questions. IIRC there is a pr-report about this, which is marked closed, for stable. -- Marc Schneiders [EMAIL PROTECTED] [EMAIL PROTECTED] [EMAIL PROTECTED] To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message -- Marc Schneiders [EMAIL PROTECTED] [EMAIL PROTECTED] [EMAIL PROTECTED] To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: IP-Filter w/FreeBSD-current
Mike Tancsa wrote: The only thing I discovered a few days ago is that when I dialin to the company network I have to unload and reload the filter rules to get ppp over the tun0 device working. Before starting /usr/sbin/ppp I do a ifconfig xl0 down to disable the cable modem interface completely. Anybody any idea where I can start to debug this weird problem? What does your routing table look like before and after ? Before: DestinationGatewayFlags Netif Expire default212.83.94.94 UGScxl0 127.0.0.1 127.0.0.1 UH lo0 192.168.1 link#3 UC ed0 = 212.83.94.64/27link#1 UC xl0 = 212.83.94.94 0:90:2b:7e:f4:0UHLWxl0 1155 (ed0: internal network, xl0 cable modem interface) xl0 is now shut down by my dialin script, and the old default route is deleted before starting /usr/sbin/ppp: DestinationGatewayFlags Netif Expire default172.16.122.2 UGSc tun0 127.0.0.1 127.0.0.1 UH lo0 172.16.122.2 172.16.122.66 UH tun0 192.168.1 link#3 UC ed0 = As far as I can see they look pretty OK... I just did some more testing, this is what I see: - fresh reboot, xl0 gets its IP address via DHCP and ipf filter rules get loaded with a small script: # flush all rules ipf -D # enable ipmon ipmon -s # load rules ipf -f /etc/ipf.conf # enable ipf -E W.r.t. filter rules for the tun0 interface: [...] # TUNNEL pass out quick on tun0 pass in quick on tun0 [...] Cable modem connection works, filter rules work as well. - Now I dialin to my company via /usr/sbin/ppp which uses the tun0 device. Connection and PPP negotiations succeeds succesfully but there's no IP traffic possible. Only after executing my ipf.reload script: # flush all rules on the inactive list ipf -I -F a # load new ones ipf -I -f /etc/ipf.conf # swap rule sets ipf -s the PPP connection works (ipf.conf not changed of course). - Now the fun part: - shut down the PPP connection, xl0 becomes 'up' again; cable modem works again. - dialin to the company again: PPP connection now works without running ipf.reload! - repeat until infinity... So it seems that only initially something weird is going on with the tun0 device. I've done the whole test three times and it's reproducable. Arjan -- Arjan de Vet, Eindhoven, The Netherlands [EMAIL PROTECTED] URL: http://www.iae.nl/users/devet/ for PGP key: finger [EMAIL PROTECTED] To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: The Commit That Broke PCM
OK, the bad news is that reverting to pcm of Dec 5 doesn't fix my problem. The good news is that "options PNPBIOS" does fix it. Now if only someone could explain all this junk: # pnpinfo Checking for Plug-n-Play devices... No Plug-n-Play devices were found # dmesg ... pcm0: CS4231 at port 0x530-0x537,0x538-0x539 irq 5 drq 1 flags 0xa110 on isa0 unknown0: PNP0c02 at port 0x80,0x398-0x399 iomem 0x-0x,0xc9a00-0xc on isa0 unknown1: PNP0c01 at iomem 0-0x9,0xe8000-0xf,0x10-0x7ff on isa0 unknown2: PNP0200 at port 0-0xf,0x81-0x8f,0xc0-0xdf drq 4 on isa0 unknown: PNP can't assign resources unknown3: PNP0100 at port 0x40-0x43 irq 0 on isa0 unknown4: PNP0b00 at port 0x70-0x71 irq 8 on isa0 unknown: PNP0303 can't assign resources unknown5: PNP0c04 at port 0xf0-0xff irq 13 on isa0 unknown: PNP0800 can't assign resources unknown6: PNP0a03 at port 0xcf8-0xcff on isa0 unknown7: PNP0c02 at port 0x4d0-0x4d1,0x8000-0x803f,0x2180-0x218f on isa0 unknown: YMH0021 can't assign resources unknown: YMH0023 can't assign resources unknown: PNP0400 can't assign resources unknown: PNP0f13 can't assign resources unknown: PNP0501 can't assign resources unknown: PNP0700 can't assign resources unknown8: YMH0022 at port 0x201 on isa0 unknown9: PNP0e03 at port 0x3e0-0x3e1 on isa0 If I don't have any PnP devices, where does all that PNPBLAH crap come from? Also, I'm guessing that YMH stands for Yamaha, and indeed, Windows thinks my sound card is a Yamaha. Why does ymf_test fail to detect it then? I never used to have "controller pnp0" in my config file. This option disappeared on Dec. 6 as PnP stuff became a standard part of the kernel. It also seems to have broken my *NON-PNP* ISA sound card, unless PNPBIOS is used. Incidentally, I have PnP OS=YES in my BIOS, but that shouldn't matter since I don't have any PnP devices, right? What on earth is going on? Alex Alex wrote: PCM has been broken for me since December 1999. I would very much appreciate if someone could help me fix it before the code freeze (cg, dfr and tanimura CC'd). I have an unknown MSS-compatible non-PnP ISA sound card, which identifies itself as a CS4231. Unknown, because it's inside a laptop. Before you ask, it has always been identified as a CS4231, and always worked very well. The last kernel that I have which still works is dated 6 Dec 1999, and I'm playing mp3's with it right now. Here's its verbose boot message: mss_detect - chip revision 0x0a mss_detect() - Detected CS4231 pcm0: CS4231 at port 0x530-0x53f,0x310-0x311 irq 5 drq 1 flags 0xa210 on isa0 pcm: setmap 3, ff00; 0xc8421000 - 3 pcm: setmap 4, ff00; 0xc8431000 - 4 isa_probe_children: probing PnP devices Kernels built after 26 Dec 1999 print the following: mss_detect - chip revision 0x0a mss_detect() - Detected CS4231 pcm0: CS4231 at port 0x530-0x537,0x538-0x539 irq 5 drq 1 flags 0xa110 on isa0 pcm: setmap 3, ff00; 0xc840e000 - 3 pcm: setmap 4, ff00; 0xc841e000 - 4 isa_probe_children: probing PnP devices mss_intr: irq, but not from mss and screw up the card - there is no sound and the driver gets stuck in "pcmwr". Something was committed between the 6th and 26th of December that broke pcm. The question is: which commit broke it? What has changed? 1) I/O port allocation and flags in dmesg: 0x310-0x311 vs 0x538-0x539, and 0xa210 vs 0xa110 2) The "mss_intr: irq, but not from mss" line Why? My config file hasn't changed a bit, neither has my hardware or BIOS setup.I don't have "controller pnp" in my config file, so it probably has nothing to do with PnP. The list of commits that might have broken it is appended below for your convenience. Please let me know if I have missed something obvious. Thank you for your attention Alex - (commits skipped) To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: My ATAPI CD not come ready
Mike Smith wrote: JFWIW, this sounds like something that I "fixed" in the old wd driver, where a device 'echoed' on the bus after it was deselected. Increasing the timeout between deselecting the device and trying to talk again to the bus was, AFAIR, the workaround then. Mike, I couldn't find your fix in the commit logs - perhaps someone else committed it? Do you have the revision number? The problem still persists: ata1-slave: ata_command: timeout waiting for intr ata1-slave: identify failed ad0: 6194MB TOSHIBA MK6409MAV [13424/15/63] at ata0-master using UDMA33 acd0: CDROM UJDA150 at ata1-master using BIOSPIO Alex It seems Alex wrote: OK - here's the part relevant to ata: ata-pci0: Intel PIIX4 ATA-33 controller port 0xfcf0-0xfcff at device 1.1 on pci0 ata0: iobase=0x01f0 altiobase=0x03f6 bmaddr=0xfcf0 ata0: mask=03 status0=50 status1=00 ata0: mask=03 status0=50 status1=00 ata0: devices = 0x1 ata0 at 0x01f0 irq 14 on ata-pci0 ata1: iobase=0x0170 altiobase=0x0376 bmaddr=0xfcf8 ata1: mask=03 status0=00 status1=00 ata1: mask=03 status0=00 status1=00 ata1: devices = 0xc Here it sees two devices, apparently you cdrom is reacting both on master AND slave addresses :( ata1-slave: ata_command: timeout waiting for intr ata1-slave: identify failed But when we try to talk to it it fails... ata0-master: success setting up UDMA2 mode on PIIX4 chip But when we try to talk to it it fails... Any ideas? I'll try to come up with a patch that solves this... -Søren To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message -- \\ 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: [PATCH] Please test the PS/2 mouse driver patch
Do you have specs on the Trackpoint PS/2 mice found on Thinkpads? No. The version on my 770X has a double click by "pushing hard on the trackpoint" feature. It also has the ability to do the scroll thing if you hold the middle mouse button and move the trackpoint. You mean, there features are available in W*ndoes, but not in FreeBSD? Yes. There can be two possible explanations: a) These features are implemented in the device firmware level and need to be explicitly activated by the driver software on the host computer. W*ndows driver knows it, but our psm driver doesn't. This would be my guess. b) These features are entirely implemented by the W*ndows driver software. The TrackPoint itself is behaving just like the ordinary 2, or 3, button pointing device. The W*ndows driver is so smart, our psm driver isn't :-) Could be. PSM does see it as just a 'Generic' device, but I do notice some odd behavior if I move the trackpoint really fast. I've always assumed that this was from a spurious double-click event caused by pressing on the trackpoint, but I could be wrong. -- Justin To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
pid 48800 (install), uid 0: exited on signal 12 (core dump)
Problems to install parts of -current after make world (upgrade from 3.4-STABLE to 4.0) I wanted to install config to make a new kernel. As soon as I do a cd config make install I get install -c -s -o root -g wheel -m 555 config /usr/sbin pid 48800 (install), uid 0: exited on signal 12 (core dump) It looks, as If I'm stuck here in the installation process... Luckily I only did a make buildworld ;-) Any ideas ? -- Andreas Klemm http://www.FreeBSD.ORG/~andreas http://www.freebsd.org/~fsmp/SMP/SMP.html powered by Symmetric MultiProcessor FreeBSD Get new songs from our band: http://www.freebsd.org/~andreas/64bits/index.html To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: bootp and diskless failure
On Mon, Jan 31, 2000 at 12:17:11AM +0100, Nicolas Souchu wrote: Hi, Is there something changed on BOOTP/diskless configuration? This problem reappears some times and was fixed in August if I remember. A hack was proposed before August, something like 'make root dev' call in bootp_subr.c Thanks, Nicholas NFS_ROOT which wasn't mandotory, is now. -- [EMAIL PROTECTED] / [EMAIL PROTECTED] FreeBSD - Turning PCs into workstations - http://www.FreeBSD.org To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Serious problems installing -CURRENT (was: UPDATING)
On Tuesday, 1 February 2000 at 16:08:44 +0100, Eric Jacoboni wrote: Max Khon [EMAIL PROTECTED] writes: actually instructions are wrong. you can't build xinstall before `make buildworld' now with old libc. I have to do buildworld _first_, then build xinstall _without_ cleaning, then make a installworld. I've been trying to build a world for a week now. It's not as simple as that. I can install the new libc with an old version of install, then build xinstall and install it, and I still get these errors. On one occasion did a complete installworld (less xinstall) with the old version of install, but the next make world (with new xinstall) still failed. I'm investigating, but something else seems to be wrong. My best guess is that the C library isn't being built correctly. I'm also getting: $ rlogin localhost /usr/libexec/ld-elf.so.1: rlogin: Undefined symbol "rcmd_af" Feb 1 12:14:59 panic ntpd[96]: ntpd 4.0.99b Tue Feb 1 05:21:28 CST 2000 (1) Feb 1 12:14:59 panic /kernel: cmd ntpd pid 96 tried to use non-present sched_get_priority_max Feb 1 12:14:59 panic /kernel: cmd ntpd pid 96 tried to use non-present sched_setscheduler I've seen a message that this last is related to POSIX threads, but I haven't had any confirmation, and that should be mentioned somewhere UPDATING. Greg -- Finger [EMAIL PROTECTED] for PGP public key See complete headers for address and phone numbers To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: Serious problems installing -CURRENT (was: UPDATING)
On Wed, 2 Feb 2000, Greg Lehey wrote: On Tuesday, 1 February 2000 at 16:08:44 +0100, Eric Jacoboni wrote: Max Khon [EMAIL PROTECTED] writes: actually instructions are wrong. you can't build xinstall before `make buildworld' now with old libc. I have to do buildworld _first_, then build xinstall _without_ cleaning, then make a installworld. I've been trying to build a world for a week now. It's not as simple as that. I can install the new libc with an old version of install, then build xinstall and install it, and I still get these errors. On one occasion did a complete installworld (less xinstall) with the old version of install, but the next make world (with new xinstall) still failed. I'm investigating, but something else seems to be wrong. My best guess is that the C library isn't being built correctly. I'm also getting: $ rlogin localhost /usr/libexec/ld-elf.so.1: rlogin: Undefined symbol "rcmd_af" Feb 1 12:14:59 panic ntpd[96]: ntpd 4.0.99b Tue Feb 1 05:21:28 CST 2000 (1) Feb 1 12:14:59 panic /kernel: cmd ntpd pid 96 tried to use non-present sched_get_priority_max Feb 1 12:14:59 panic /kernel: cmd ntpd pid 96 tried to use non-present sched_setscheduler I've seen a message that this last is related to POSIX threads, but I haven't had any confirmation, and that should be mentioned somewhere UPDATING. I can confirm that adding the POSIX options mentioned in the messages of Mike Bristow makes the messages go away. Which is something else than explaining what is going on here. I cannot even guess. I have a number of problems building things, esp. ports that depend on the libraries involved, giflib e.g. Maybe the fact that I built world, then got the message to first install xinstall (after 5 days!), and subsequently did so and made world again is to blame? -- Marc Schneiders [EMAIL PROTECTED] [EMAIL PROTECTED] To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: 4.0 release cosmetics: ftpd
On Tue, 1 Feb 2000, Will Saxon wrote: Well, apparently we are supposed to replace a bunch of files is /etc whenever we make world. There is a command called mergemaster that does this, but the one time i used it (I did not read the directionsvery carefully) I basically messed everything up. Yes, I don't like mergemaster either. I look at the cvs-messages to see what files have changed and copy/merge those by hand. I have a machine that a fresh install of 4.0-current (1/27) and the pam.conf is totally different, and I dont get the error messages. Oops. Overlooked the new pam.conf for some reason a few weeks ago. Apologies to all! Maybe you should look into this if you have more problems. Glad I could help though :). Thanks again :-) [...] -- Marc Schneiders [EMAIL PROTECTED] [EMAIL PROTECTED] [EMAIL PROTECTED] To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Some current kernel wizdom.
I'm looking at producing a netgraph node that is going to be potentially very hard on kernel memory. The node may have to manage as many as 10K netgraph hook connections (each one requires a small amount of memory) and access to the hooks requires that they be in a table (not a linked list). This means that I'm forced to make either a rather large static allocation or making reallocations as required. I'd like to poll the collected wizdom of various strategies. In this case, the actual usage is hard to predetermine and can range from small (a few entries) to very large (a few thousand entries). Is it bad, in the kernel context, to allocate a moderate amount and then increase one's allocation a la realloc(3)? Dave. -- |David Gilbert, Velocet Communications. | Two things can only be | |Mail: [EMAIL PROTECTED] | equal if and only if they | |http://www.velocet.net/~dgilbert | are precisely opposite. | =GLO To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: Some current kernel wizdom.
* David Gilbert [EMAIL PROTECTED] [000201 17:41] wrote: I'm looking at producing a netgraph node that is going to be potentially very hard on kernel memory. The node may have to manage as many as 10K netgraph hook connections (each one requires a small amount of memory) and access to the hooks requires that they be in a table (not a linked list). This means that I'm forced to make either a rather large static allocation or making reallocations as required. I'd like to poll the collected wizdom of various strategies. In this case, the actual usage is hard to predetermine and can range from small (a few entries) to very large (a few thousand entries). Is it bad, in the kernel context, to allocate a moderate amount and then increase one's allocation a la realloc(3)? Why not use a linked list, with a hash header to reduce search times. I don't think there is a realloc for the kernel btw. -Alfred To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: Some current kernel wizdom.
"Alfred" == Alfred Perlstein [EMAIL PROTECTED] writes: Alfred Why not use a linked list, with a hash header to reduce search Alfred times. Well... I think a linked list is already created for me (we're talking netgraph hooks here) and a hash isn't required since I can canive my problem to fit a completely used set of integers (by choosing unused integers when I create a new hook). That's not the problem. I'm just concerned about statically allocating (say) 10K pointers in that array for each instance of my node and then only using 5 in one node and 5K in another. Alfred I don't think there is a realloc for the kernel btw. Trivial exercise left to the reader, really. I was just curious if this type of behaviour tends to badly frustrate memory allocation in the kernel. Is it good, for instance, to plan reallocations at roughly the page size in increments? Dave. -- |David Gilbert, Velocet Communications. | Two things can only be | |Mail: [EMAIL PROTECTED] | equal if and only if they | |http://www.velocet.net/~dgilbert | are precisely opposite. | =GLO To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: The Commit That Broke PCM
In message [EMAIL PROTECTED] Alex writes: : # pnpinfo : Checking for Plug-n-Play devices... : No Plug-n-Play devices were found Makes sense because this looks for PnP ISA addin cards. OK, taking the lead from http://members.hyperlink.net.au/~chart/pnpid.txt, lets have a crack at these things: : unknown0: PNP0c02 at port 0x80,0x398-0x399 iomem : 0x-0x,0xc9a00-0xc on isa0 These are your motherboard registers. : unknown1: PNP0c01 at iomem : 0-0x9,0xe8000-0xf,0x10-0x7ff on isa0 This is your system board. : unknown2: PNP0200 at port 0-0xf,0x81-0x8f,0xc0-0xdf drq 4 on isa0 This is your AT DMA controller : unknown: PNP can't assign resources This is your AT interrupt controller : unknown3: PNP0100 at port 0x40-0x43 irq 0 on isa0 this is your AT Timer : unknown4: PNP0b00 at port 0x70-0x71 irq 8 on isa0 This is your AT Realtime clock. : unknown: PNP0303 can't assign resources This is your IBM Enhanced keyboard contoller : unknown5: PNP0c04 at port 0xf0-0xff irq 13 on isa0 This is your math coprocessor : unknown: PNP0800 can't assign resources This is your AT Speaker controller : unknown6: PNP0a03 at port 0xcf8-0xcff on isa0 This is a PCI bus. : unknown7: PNP0c02 at port 0x4d0-0x4d1,0x8000-0x803f,0x2180-0x218f on isa0 More motherboard registers. : unknown: YMH0021 can't assign resources Yamaha OPL3-SAx Sound system. : unknown: YMH0023 can't assign resources Yamaha OPL3-SAx COM Port : unknown: PNP0400 can't assign resources Standard LPT printer port. : unknown: PNP0f13 can't assign resources PS/2 Port for PS/2-style mice : unknown: PNP0501 can't assign resources 16550A-Compatible com port : unknown: PNP0700 can't assign resources PC Standard Floppy disk controller. : unknown8: YMH0022 at port 0x201 on isa0 Yamaha OPL3-SAx GamePort : unknown9: PNP0e03 at port 0x3e0-0x3e1 on isa0 Intel 82365-compatible CardBus controller : kernel. It also seems to have broken my *NON-PNP* ISA sound card, : unless PNPBIOS is used. Incidentally, I have PnP OS=YES in my BIOS, : but that shouldn't matter since I don't have any PnP devices, right? You should have PnP OS = *NO* in your BIOS. Otherwise that PCI bus that you have won't necessarily be configured correctly. Warner To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
AIC-7899 SCSI Driver?
Is anybody here working on driver for AIC-7899, Ataptec's Ultra160 SCSI controller??? -- Osamu MIHARA // NEC Printers Division To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
mail.freebsd.org's host id changed
Did someone do something to mail.freebsd.org, my ssh is telling me it's hostid has been changed. -Matt Matthew Dillon [EMAIL PROTECTED] To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Solved: Serious problems installing -CURRENT (was: UPDATING)
On Wednesday, 2 February 2000 at 9:37:44 +1030, Greg Lehey wrote: On Tuesday, 1 February 2000 at 16:08:44 +0100, Eric Jacoboni wrote: Max Khon [EMAIL PROTECTED] writes: actually instructions are wrong. you can't build xinstall before `make buildworld' now with old libc. I have to do buildworld _first_, then build xinstall _without_ cleaning, then make a installworld. I've been trying to build a world for a week now. It's not as simple as that. I can install the new libc with an old version of install, then build xinstall and install it, and I still get these errors. On one occasion did a complete installworld (less xinstall) with the old version of install, but the next make world (with new xinstall) still failed. I'm investigating, but something else seems to be wrong. My best guess is that the C library isn't being built correctly. Well, I've found the problem: I was using the wrong libraries after all. Sure, I checked, but what I was checking for was lib/libc.so.4, and that's what I had, unfortunately on the wrong system. Specifically, it seems that ldconfig -m doesn't work the way I thought. During the system startup, I had effectively: ldconfig /usr/lib/compat /usr/X11R6/lib /usr/X11R6/lib/aout /usr/local/lib ldconfig -m /freebie/usr/lib /T/local/lib /freebie/usr/X11R6/lib The second list of directories are on another -CURRENT machine, one older than the one I'm building on. I do this to have access to programs on that machine (specifically the ones in its /usr/local, which is mounted on /T/local). But it seems that the -m option *replaces* all the local libraries with the ones that it finds, so my libc was /freebie/usr/lib/libc.so.4, which was old. I'm also getting: $ rlogin localhost /usr/libexec/ld-elf.so.1: rlogin: Undefined symbol "rcmd_af" This is gone as well now. Greg -- Finger [EMAIL PROTECTED] for PGP public key See complete headers for address and phone numbers To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: UPDATING
hi, there! On Tue, 1 Feb 2000, Warner Losh wrote: In message [EMAIL PROTECTED] Max Khon writes: : actually xinstall cannot be built before make world or make buildworld : because of undefined symbols `setflags'. What's the right thing then? make buildworld; cd /usr/src/usr.bin/xinstall; make depend all install and then, make installworld /fjoe To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: mail.freebsd.org's host id changed
On Tuesday, 1 February 2000 at 18:49:22 -0800, Matthew Dillon wrote: Did someone do something to mail.freebsd.org, my ssh is telling me it's hostid has been changed. Right, hub had disk problems, so jmb moved mail to builder. Greg -- Finger [EMAIL PROTECTED] for PGP public key See complete headers for address and phone numbers To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: AIC-7899 SCSI Driver?
On Wed, Feb 02, 2000 at 11:00:56 +0900, Osamu MIHARA wrote: Is anybody here working on driver for AIC-7899, Ataptec's Ultra160 SCSI controller??? It should work fine under -current. It will only work at Ultra2 speeds right now, Ultra160 support is coming, though. Ken -- Kenneth Merry [EMAIL PROTECTED] To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: Serious problems installing -CURRENT (was: UPDATING)
According to Greg Lehey: Feb 1 12:14:59 panic /kernel: cmd ntpd pid 96 tried to use non-present sched_get_priority_max Feb 1 12:14:59 panic /kernel: cmd ntpd pid 96 tried to use non-present sched_setscheduler I've seen a message that this last is related to POSIX threads, but I haven't had any confirmation, and that should be mentioned somewhere UPDATING. As the sched_* functions are now enabled by default (POSIX stuff) in GENERIC I decided to enable their use within ntpd. See -current just after I did the upgrade. -- Ollivier ROBERT -=- FreeBSD: The Power to Serve! -=- [EMAIL PROTECTED] FreeBSD keltia.freenix.fr 4.0-CURRENT #77: Thu Dec 30 12:49:51 CET 1999 To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: AIC-7899 SCSI Driver?
It will only work at Ultra2 speeds right now, Ultra160 support is coming, though. To be fair, the sym driver already supports Ultra3. And Qlogic Ultra3 support is coming too. To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: UPDATING
On Wed, 2 Feb 2000, Max Khon wrote: hi, there! On Tue, 1 Feb 2000, Warner Losh wrote: In message [EMAIL PROTECTED] Max Khon writes: : actually xinstall cannot be built before make world or make buildworld : because of undefined symbols `setflags'. What's the right thing then? make buildworld; cd /usr/src/usr.bin/xinstall; make depend all install and then, make installworld Nope. If buildworld completed right, then only need the make install in xinstall. xinstall will already be built. /fjoe To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message Chuck Robey| Interests include C Java programming, FreeBSD, [EMAIL PROTECTED] | electronics, communications, and signal processing. New Year's Resolution: I will not sphroxify gullible people into looking up fictitious words in the dictionary. To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: AIC-7899 SCSI Driver?
On Tue, Feb 01, 2000 at 20:11:38 -0800, Matthew Jacob wrote: It will only work at Ultra2 speeds right now, Ultra160 support is coming, though. To be fair, the sym driver already supports Ultra3. And Qlogic Ultra3 support is coming too. Yes, I should have qualified that. "Ultra160 support for the Adaptec chips is coming." Ken -- Kenneth Merry [EMAIL PROTECTED] To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: Serious problems installing -CURRENT (was: UPDATING)
On Wed, 2 Feb 2000, Ollivier Robert wrote: According to Greg Lehey: Feb 1 12:14:59 panic /kernel: cmd ntpd pid 96 tried to use non-present sched_get_priority_max Feb 1 12:14:59 panic /kernel: cmd ntpd pid 96 tried to use non-present sched_setscheduler I've seen a message that this last is related to POSIX threads, but I haven't had any confirmation, and that should be mentioned somewhere UPDATING. As the sched_* functions are now enabled by default (POSIX stuff) in GENERIC I decided to enable their use within ntpd. ntp should use the POSIX feature test macros for these functions. Unfortunately, it uses autoconfig, and we turn this into hard coded configuration by committing the generated config.h file as a source file. Bruce To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: mail.freebsd.org's host id changed
: :On Tuesday, 1 February 2000 at 18:49:22 -0800, Matthew Dillon wrote: : Did someone do something to mail.freebsd.org, my ssh is telling me : it's hostid has been changed. : :Right, hub had disk problems, so jmb moved mail to builder. : :Greg Ah, ok. Thanks! Just making sure. -Matt Matthew Dillon [EMAIL PROTECTED] To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Creative SB AWE64 recording does not work
A kernel, current, sources cvsuped today. When I try to record from line, (source does not seem to matter), I get full scale white noise. The remainder of the system is from about a week ago, I will try a buildworld/installworld later. Anything I should try? This is with both device pcm and device pcm device sbc in the config file. section from dmesg --- sbc0: Creative SB AWE64 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: SB DSP 4.16 on sbc0 unknown0: Game at port 0x200-0x207 on isa0 unknown1: WaveTable at port 0x620-0x623 on isa0 --- Brian Beattie| The only problem with [EMAIL PROTECTED] | winning the rat race ... www.aracnet.com/~beattie | in the end you're still a rat To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
inetd problem: IPv6 for RPC is not supported yet
Apart from disabling INET6 in the inetd build, is there any way of supressing inetd from trying to bind v6 services? I like using rup on the internal network, but it's not working on my latest-sup-current. To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: inetd problem: IPv6 for RPC is not supported yet
Apart from disabling INET6 in the inetd build, is there any way of
supressing inetd from trying to bind v6 services? I like using rup
on the internal network, but it's not working on my latest-sup-current.
Sorry for your problem and please try this patch.
Now I am waiting to get commit permission.
Yoshinobu Inoue
Index: inetd.c
===
RCS file: /home/ncvs/src/usr.sbin/inetd/inetd.c,v
retrieving revision 1.77
diff -u -r1.77 inetd.c
--- inetd.c 2000/01/28 20:06:15 1.77
+++ inetd.c 2000/02/01 15:11:35
@@ -1522,8 +1522,9 @@
} else
sep-se_proto = newstr(arg);
if (strncmp(sep-se_proto, "rpc/", 4) == 0) {
- if (sep-se_family != AF_INET) {
- syslog(LOG_ERR, "IPv6 for RPC is not supported yet");
+ if (no_v4bind != 0) {
+ syslog(LOG_INFO, "IPv4 bind is ignored for %s",
+ sep-se_service);
freeconfig(sep);
goto more;
}
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message
Re: Dell 2400 and APIC problem
On Tue, Feb 01, 2000 at 12:08:38PM -0500, Luoqi Chen wrote: I am using boot -dv with "options DIAGNOSTIC" in the kernel and it doesnt tell me what the PnP probe is hanging on. Any other suggestions? I don't think it's pnp probing. You don't seem to have any pnp devices at all from your dmesg output. Could you do a 'pnpinfo' and verify if it is indeed the case? You are correct: # pnpinfo Checking for Plug-n-Play devices... No Plug-n-Play devices were found Isa bus is the last bus probed, and immediately (well, almost) follows that configure hooks with interrupt enabled. That is also the first time BSP gives up mplock, and the APs have a chance to initialize themselves. I believe that is where it hangs. This looks like the problem, thanks for your help. Do you know how I can narrow this down and perhaps get it working? Just to make sure, do you have "options NAPIC 2" in your kernel config? The default is 1, so you absolutely need this line for things to work. Yes I have "options NAPIC 2" in my kernel config, the kernel complains and halts if I have it set to 1. -Conrad To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: Serious problems installing -CURRENT (was: UPDATING)
According to Bruce Evans: ntp should use the POSIX feature test macros for these functions. Unfortunately, it uses autoconfig, and we turn this into hard coded configuration by committing the generated config.h file as a source file. Wouldn't work. Autoconf finds the sched_* functions regardless of their presence in the kernel config. file. Autoconf is a compile-time utility whereas we'd need something more sophisticated to get this right. -- Ollivier ROBERT -=- FreeBSD: The Power to Serve! -=- [EMAIL PROTECTED] FreeBSD keltia.freenix.fr 4.0-CURRENT #77: Thu Dec 30 12:49:51 CET 1999 To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: UPDATING
On Wed, Feb 02, 2000 at 01:47:25PM +1100, Bruce Evans wrote: On Tue, 1 Feb 2000, Ruslan Ermilov wrote: On Tue, Feb 01, 2000 at 12:11:51PM -0700, Warner Losh wrote: In message [EMAIL PROTECTED] Max Khon writes: The old /usr/bin/install will fail right after new libutil gets installed. But at this point, we will already have new libc in /usr/lib. No. libutil is a prerequisite for some libraries, so it is installed before libc. So, if the installworld fails, we need to install new "install" with itself: After first installing the new libc. Other things can easilty break if prerequisites are not installed in the correct order. There may be no correct order for the current building scheme (there are too many old utilities which may be corrupted by installing new shared libraries). cd src/usr.bin/xinstall make install INSTALL=/usr/obj/usr/src/usr.bin/xinstall/xinstall Installing the xinstall built by buildworld, with itself, would be safe. Similarly for the new libc -- install it using the new xinstall using something like cd /usr/src/libc MAKEOBJDIRPREFIX=/somehwere INSTALL=/somehwere/.../xinstall install Simpler method: build and install the host xinstall static (NOSHARED=yes) before running installworld. It's too late to do this after installworld corrupts the host's includes and libutil.a. But this will not work, since at this point we will have old libraries :-) -- Ruslan Ermilov Sysadmin and DBA of the [EMAIL PROTECTED]United Commercial Bank, [EMAIL PROTECTED] FreeBSD committer, +380.652.247.647Simferopol, Ukraine http://www.FreeBSD.org The Power To Serve http://www.oracle.com Enabling The Information Age To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: Serious problems installing -CURRENT (was: UPDATING)
ntp should use the POSIX feature test macros for these functions. Unfortunately, it uses autoconfig, and we turn this into hard coded configuration by committing the generated config.h file as a source file. Wouldn't work. Autoconf finds the sched_* functions regardless of their presence in the kernel config. file. Autoconf is a compile-time utility whereas we'd need something more sophisticated to get this right. Actually the current way works pretty well. Ntpd will try to use the sched_* functions, but if they fail it will try other ways to set the priority. It is just the fact that it logs the the fact that the sched_* functions are not available that gives people a shock ... and a chance to enable it in their kernel. :-) John -- John Hay -- [EMAIL PROTECTED] To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Release build of 3.4-STABLE
I checked out the sources from RELENG_3 for 3.4-STABLE and i got the same error i got last year, the release breaks at kerberos. My CHROOTDIR = /DRIVE2/R2/ It could'nt find /DRIVE2/R2/R/stage/trees/krb, so once again i had to make a link in DRIVE2/R2/R/stage/trees/krb from krb4 to krb, then it built fine. Is this an error in the Makefile or is there something i missed ? Johan Kruger ( B.Ing Electronic Engineering ) Developement Engineer Nanoteq PTA ( 012 6727000 ) e-mail : [EMAIL PROTECTED] e-mail : [EMAIL PROTECTED] To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
