Re: UPDATE4: ATA/ATAPI driver new version available.
It seems Tugrul Galatali wrote: There seems to be an oopsie with the includes on a system without PCI in ata-dma.c: #include ata.h +#include sys/types.h + #if NATA 0 -#include pci.h #if NPCI 0 +#include pci.h #include sys/param.h #include sys/systm.h #include sys/kernel.h The pci.h should be before the if NPCI or it will never be defined :) My 486 still spits this out tho: [...] ata0 at 0x1f0-0x1f7 irq 14 on isa [...] ad0: WDC AC2850F/28.25E40 ATA-? disk at ata0 as master ad0: 814MB (1667232 sectors), 1654 cyls, 16 heads, 63 S/T, 512 B/S ad0: piomode=3, dmamode=1, udmamode=-1 ad0: 16 secs/int, 0 depth queue, PIO mode changing root device to wd0s1a ad0: invalid primary partition table: no magic changing root device to wd0a ad0: invalid primary partition table: no magic error 22: panic: cannot mount root (2) Hmm, I'll bet the disk doesn't grok the 16 secs/int or the controller doesn't support 32bit transfers... This I really should check for... My PIIX3 box isn't happy with this update either: [...] ata-pci0: Intel PIIX3 IDE controller rev 0x00 on pci0.7.1 ata-pci0: Busmastering DMA supported [...] ata0 at 0x01f0 irq 14 on ata-pci0 [...] ata0: master: settting up WDMA2 mode on PIIX3/4 chip OK ad0: WDC AC22100H/11.09I14 ATA-? disk at ata0 as master ad0: 2014MB (4124736 sectors), 4092 cyls, 16 heads, 63 S/T, 512 B/S ad0: piomode=4, dmamode=2, udmamode=-1 ad0: 16 secs/int, 0 depth queue, DMA mode acd0: HITACHI CDR-8330/0007 CDROM drive at ata0 as slave acd0: drive speed 1779 - 4134KB/sec, 128KB cache acd0: supported read types: CD-R, CD-RW, CD-DA, packet track acd0: Audio: play, 255 volume levels acd0: Mechanism: ejectable tray acd0: Medium: no/blank disc inside, unlocked changing root device to wd0s1a [...] acd0: rezero failed -- Whenever I try to mount my cdrom drive. With or without a cd in there. mount gives me mount: Input/output error You should only get the rezero when you are WRITING to the CD, really wierd... I can't eject the cd tray either after I mount the drive. Its fine after boot but before I attempt to mount something. If you open the device and mount it, the driver will lock the CD in the drive, if something goes wrong it might be stuck in there... Granted I should do something about that too... -Søren To Unsubscribe: send mail to majord...@freebsd.org with unsubscribe freebsd-current in the body of the message
Re: Handbook DocBook cutover complete
Kris, On Sun, Mar 28, 1999 at 04:40:22PM +0930, Kris Kennaway wrote: On Sat, 27 Mar 1999, Nik Clayton wrote: Almost a year ago I started the project to switch the Handbook over from LinuxDoc to DocBook. Can I ask what the differences and benefits are? As follows; * LinuxDoc is descended from the QWERTZ DTD, and was designed to serve the needs of the Linux Documentation Project. DocBook has been designed to mark up technical books and articles, and has been designed by representatives from a large number of companies (this, for once, has not been a bad thing). It's large, comprehensive, and well supported. * LinuxDoc is designed to be quite close to LaTeX. This means there's a lot of presentational markup (i.e., markup that describes things as being bold, or italic, and so on), a lot like HTML. DocBook contains *no* presentational markup, it's entirely semantic. To write a filename in LinuxDoc you would write tt/path/to/some/file/tt where tt means teletype, i.e., a monospaced font. If you wanted to write a command the user types in, you would use the same thing, ttls /etc/tt In DocBook, you would write filename/path/to/some/file/filename commandls /etc/command When processed, both those might be displayed in a monospaced font. However, the DocBook version includes extra information. We don't do it yet, but the DocBook Handbook will eventually include several indices. One of these will be a list of each page where each filename is mentioned, allowing you to quickly see all the places where (for example) ppp.conf is referred to. This index would catch every reference to ppp.conf used as a filename, but would ignore those where it was mentioned as part of a command. So filenameppp.conf/filename would be indexed, but commandvi ppp.conf/command wouldn't. The only way to do this using LinuxDoc would be to index everywhere 'ppp.conf' appeared, which would *also* catch the second example, which is not what you want. * DocBook is extensible. It's relatively easy to add your own elements, for things that are missing from DocBook. I've done this for the Handbook, adding things like hostid and maketarget. This is harder to with LinuxDoc. * The Linux Documentation Project is moving away from LinuxDoc to DocBook. I *think* the FreeBSD Doc. Proj. switched first, and I'm pretty certain the FreeBSD Handbook is the largest free set of documentation that currently uses DocBook. I could be wrong about that though. * There's an XML implementation of DocBook (currently unofficial). This will be more important in the future, as XML browsers become more widespread. * Tools to convert DocBook to other formats are not quite as advanced as the LinuxDoc tools, but are getting their rapidly. As it currently stands in the repository, the DocBook Handbook can be converted to HTML, Postscript, plain text, and Microsoft RTF. A bug that I'll fix this week is currently preventing PDF generation. Word .doc support is in the pipeline as well, probably for the end of this week too (I've now given some money to the evil empire so I can test the output myself). Next on the list will be whatever internal format the Palm Pilot uses. I imagine this won't be too useful for the Handbook, but will probably be quite handy for the FAQ. . . More information at http://www.freebsd.org/~nik/primer/index.html N -- --+==[ Systems Administrator, Year 2000 Test Lab, Lehman Brothers, Inc. ]==+-- --+==[ 1 Broadgate, London, EC2M 7HA 0171-601-0011 x5514 ]==+-- --+==[ Year 2000 Testing: It's about time. . . ]==+-- To Unsubscribe: send mail to majord...@freebsd.org with unsubscribe freebsd-current in the body of the message
Re: Handbook DocBook cutover complete
On Mon, 29 Mar 1999 nclay...@lehman.com wrote: Kris, On Sun, Mar 28, 1999 at 04:40:22PM +0930, Kris Kennaway wrote: On Sat, 27 Mar 1999, Nik Clayton wrote: Almost a year ago I started the project to switch the Handbook over from LinuxDoc to DocBook. Can I ask what the differences and benefits are? As it currently stands in the repository, the DocBook Handbook can be converted to HTML, Postscript, plain text, and Microsoft RTF. A bug that I'll fix this week is currently preventing PDF generation. Word .doc support is in the pipeline as well, probably for the end of this week too (I've now given some money to the evil empire so I can test the output myself). Why? We can use StarOffice 5.0x, after all. Next on the list will be whatever internal format the Palm Pilot uses. I imagine this won't be too useful for the Handbook, but will probably be quite handy for the FAQ. . . Do you mean the Memo format or the Doc format? I hope you mean Doc... It might not even be worth it to do this, since a very nice, fast browser (Palmscape) has been around for a while on the Palm, and an offline browser called Plucker. More information at http://www.freebsd.org/~nik/primer/index.html N -- --+==[ Systems Administrator, Year 2000 Test Lab, Lehman Brothers, Inc. ]==+-- --+==[ 1 Broadgate, London, EC2M 7HA 0171-601-0011 x5514 ]==+-- --+==[ Year 2000 Testing: It's about time. . . ]==+-- To Unsubscribe: send mail to majord...@freebsd.org with unsubscribe freebsd-current in the body of the message Brian Feldman_ __ ___ ___ ___ ___ gr...@unixhelp.org_ __ ___ | _ ) __| \ FreeBSD: The Power to Serve! _ __ | _ \__ \ |) | http://www.freebsd.org _ |___/___/___/ To Unsubscribe: send mail to majord...@freebsd.org with unsubscribe freebsd-current in the body of the message
HEADS UP!! NOAOUT `make world' knob changed
I have just changed made a change concerning the building of legacy a.out bits during `make world'. Previous to my change, one would define NOAOUT to keep from building the legacy a.out bits. Now one would define WANT_AOUT to build them. The default of building a.out bits gets in the way of some other changes I will make to the `build world' process soon. -- -- David(obr...@nuxi.com -or- obr...@freebsd.org) To Unsubscribe: send mail to majord...@freebsd.org with unsubscribe freebsd-current in the body of the message
Re: Handbook DocBook cutover complete
On Mon, Mar 29, 1999 at 06:01:45AM -0500, Brian Feldman wrote: Word .doc support is in the pipeline as well, probably for the end of this week too (I've now given some money to the evil empire so I can test the output myself). Why? We can use StarOffice 5.0x, after all. * Not if you're on a 2.2-stable system. Don't mock, because I still am, until I find the time to upgrade. At least, I could never get it to work solidly for any length of time. I know there have been updates, but there's only so many times I'm prepared to download it. * People who haven't yet switched to using FreeBSD can get a reasonably good printed copy of the documentation (at the moment just the Handbook, but eventually all the docs) on a Windows platform. * My accountant likes various bits and pieces to be entered in to their home grown Access DB. So I needed to get hold of Office anyway (and as an aside, the ODBC driver for Postgres works very nicely). Next on the list will be whatever internal format the Palm Pilot uses. I imagine this won't be too useful for the Handbook, but will probably be quite handy for the FAQ. . . Do you mean the Memo format or the Doc format? I hope you mean Doc... It might not even be worth it to do this, since a very nice, fast browser (Palmscape) has been around for a while on the Palm, and an offline browser called Plucker. I don't know yet, I need to get a Pilot :-) I'm open to recommendations, and/or pointers to specifications for the format. And if there are any programmers out there looking for something to do, this could be quite a nice task. N -- --+==[ Systems Administrator, Year 2000 Test Lab, Lehman Brothers, Inc. ]==+-- --+==[ 1 Broadgate, London, EC2M 7HA 0171-601-0011 x5514 ]==+-- --+==[ Year 2000 Testing: It's about time. . . ]==+-- To Unsubscribe: send mail to majord...@freebsd.org with unsubscribe freebsd-current in the body of the message
Re: Handbook DocBook cutover complete
On Mon, 29 Mar 1999 nclay...@lehman.com wrote: On Mon, Mar 29, 1999 at 06:01:45AM -0500, Brian Feldman wrote: Word .doc support is in the pipeline as well, probably for the end of this week too (I've now given some money to the evil empire so I can test the output myself). Why? We can use StarOffice 5.0x, after all. * Not if you're on a 2.2-stable system. Don't mock, because I still am, until I find the time to upgrade. At least, I could never get it to work solidly for any length of time. I know there have been updates, but there's only so many times I'm prepared to download it. I meant use StarOffice to test out the Office .docs. * People who haven't yet switched to using FreeBSD can get a reasonably good printed copy of the documentation (at the moment just the Handbook, but eventually all the docs) on a Windows platform. * My accountant likes various bits and pieces to be entered in to their home grown Access DB. So I needed to get hold of Office anyway (and as an aside, the ODBC driver for Postgres works very nicely). Next on the list will be whatever internal format the Palm Pilot uses. I imagine this won't be too useful for the Handbook, but will probably be quite handy for the FAQ. . . Do you mean the Memo format or the Doc format? I hope you mean Doc... It might not even be worth it to do this, since a very nice, fast browser (Palmscape) has been around for a while on the Palm, and an offline browser called Plucker. I don't know yet, I need to get a Pilot :-) I'm open to recommendations, and/or pointers to specifications for the format. Doc is a nice format, but it's not hypertext. Check out ports/palm/pilot_makedoc And if there are any programmers out there looking for something to do, this could be quite a nice task. N -- --+==[ Systems Administrator, Year 2000 Test Lab, Lehman Brothers, Inc. ]==+-- --+==[ 1 Broadgate, London, EC2M 7HA 0171-601-0011 x5514 ]==+-- --+==[ Year 2000 Testing: It's about time. . . ]==+-- To Unsubscribe: send mail to majord...@freebsd.org with unsubscribe freebsd-current in the body of the message Brian Feldman_ __ ___ ___ ___ ___ gr...@unixhelp.org_ __ ___ | _ ) __| \ FreeBSD: The Power to Serve! _ __ | _ \__ \ |) | http://www.freebsd.org _ |___/___/___/ To Unsubscribe: send mail to majord...@freebsd.org with unsubscribe freebsd-current in the body of the message
Re: UPDATE4: ATA/ATAPI driver new version available.
Soren Schmidt said: DMA support has been added to the ATA disk driver. This only works on Intel PIIX3/4, Acer Aladdin and Promise controllers. The promise support works without the BIOS on the board, and timing modes are set to support up to UDMA speed. This solves the problems with having more than one promise controller in the same system. Excellent!!! -- John | Never try to teach a pig to sing, dy...@iquest.net | it makes one look stupid jdy...@nc.com | and it irritates the pig. To Unsubscribe: send mail to majord...@freebsd.org with unsubscribe freebsd-current in the body of the message
Re: UPDATE4: ATA/ATAPI driver new version available.
It seems John S. Dyson wrote: Soren Schmidt said: DMA support has been added to the ATA disk driver. This only works on Intel PIIX3/4, Acer Aladdin and Promise controllers. The promise support works without the BIOS on the board, and timing modes are set to support up to UDMA speed. This solves the problems with having more than one promise controller in the same system. Excellent!!! Yeah, except there is a bug in the code that always makes the promise use PIO mode :), fix coming as soon as I get home from work in an hour or so... -Søren To Unsubscribe: send mail to majord...@freebsd.org with unsubscribe freebsd-current in the body of the message
Status of 'tee' firewall action
Hello! What the status of 'tee' action? Anybody working on it? - Roman V. Palagin | RVP1-6BONE, RP40-RIPE| Network Administrator - To Unsubscribe: send mail to majord...@freebsd.org with unsubscribe freebsd-current in the body of the message
booting systems with lots of memory
We have a Quad 400MHz Xeon on evaluation here and we're trying to get
a large memory configuration working. The machine is running a recent
3.1-STABLE with the kva patch from -CURRENT (appended below). When we
have a working system with 1GB of RAM we'll increase it to 3GB of RAM
and see how it runs.
The boot blocks are from 3.0-RELEASE and they will boot the old a.out
kernel via /boot/loader quite happily. We haven't yet managed to boot
an ELF kernel, though (but we haven't tried to boot an unpatched one).
It's also somewhat painful to debug because the machine is miles away
and its serial console is causing trouble.
Are there any obvious things we have missed? I assume the kernel load
address is read by /boot/loader from the kernel's ELF header, so that
a recent loader can cope. I also assume that the patch included below
tweaks all of the required knobs.
Tony.
--
f.a.n.finch d...@dotat.at f...@demon.net
===
RCS file: /home/ncvs/src/sys/i386/conf/Makefile.i386,v
retrieving revision 1.140
retrieving revision 1.141
diff -p -u -r1.140 -r1.141
--- src/sys/i386/conf/Makefile.i386 1999/03/01 09:54:51 1.140
+++ /home/ncvs/src/sys/i386/conf/Makefile.i386 1999/03/11 18:28:41 1.141
@@ -1,7 +1,7 @@
# Makefile.i386 -- with config changes.
# Copyright 1990 W. Jolitz
# from: @(#)Makefile.i386 7.1 5/10/91
-# $Id: Makefile.i386,v 1.140 1999/03/01 09:54:51 dt Exp $
+# $Id: Makefile.i386,v 1.141 1999/03/11 18:28:41 dg Exp $
#
# Makefile for FreeBSD
#
@@ -56,7 +56,7 @@ CFLAGS+= -elf
CFLAGS+= -aout
.endif
-LOAD_ADDRESS?= F010
+LOAD_ADDRESS?= C010
DEFINED_PROF= ${PROF}
.if defined(PROF)
CFLAGS+= -malign-functions=4
===
RCS file: /home/ncvs/src/sys/i386/conf/kernel.script,v
retrieving revision 1.1
retrieving revision 1.2
diff -p -u -r1.1 -r1.2
--- src/sys/i386/conf/kernel.script 1998/09/30 12:14:39 1.1
+++ /home/ncvs/src/sys/i386/conf/kernel.script 1999/03/11 18:28:42 1.2
@@ -5,7 +5,7 @@ SEARCH_DIR(/usr/lib); SEARCH_DIR(/usr/ob
SECTIONS
{
/* Read-only sections, merged into text segment: */
- . = 0xf010 + SIZEOF_HEADERS;
+ . = 0xc010 + SIZEOF_HEADERS;
.interp : { *(.interp) }
.hash : { *(.hash) }
.dynsym: { *(.dynsym)}
===
RCS file: /home/ncvs/src/sys/i386/include/pmap.h,v
retrieving revision 1.58
retrieving revision 1.59
diff -p -u -r1.58 -r1.59
--- src/sys/i386/include/pmap.h 1999/03/02 16:20:39 1.58
+++ /home/ncvs/src/sys/i386/include/pmap.h 1999/03/11 18:28:46 1.59
@@ -42,7 +42,7 @@
*
* from: hp300: @(#)pmap.h 7.2 (Berkeley) 12/16/90
* from: @(#)pmap.h7.4 (Berkeley) 5/12/91
- * $Id: pmap.h,v 1.58 1999/03/02 16:20:39 dg Exp $
+ * $Id: pmap.h,v 1.59 1999/03/11 18:28:46 dg Exp $
*/
#ifndef _MACHINE_PMAP_H_
@@ -88,13 +88,13 @@
#define VADDR(pdi, pti) ((vm_offset_t)(((pdi)PDRSHIFT)|((pti)PAGE_SHIFT)))
#ifndef NKPT
-#defineNKPT9 /* actual number of kernel page
tables */
+#defineNKPT17 /* actual number of kernel page
tables */
#endif
#ifndef NKPDE
#ifdef SMP
-#define NKPDE 62 /* addressable number of page
tables/pde's */
+#define NKPDE 254 /* addressable number of page
tables/pde's */
#else
-#define NKPDE 63 /* addressable number of page
tables/pde's */
+#define NKPDE 255 /* addressable number of page
tables/pde's */
#endif /* SMP */
#endif
To Unsubscribe: send mail to majord...@freebsd.org
with unsubscribe freebsd-current in the body of the message
Re: booting systems with lots of memory
On Mon, Mar 29, 1999 at 03:43:16PM +0100, Tony Finch d...@dotat.at wrote:
We have a Quad 400MHz Xeon on evaluation here and we're trying to get
a large memory configuration working. The machine is running a recent
3.1-STABLE with the kva patch from -CURRENT (appended below). When we
have a working system with 1GB of RAM we'll increase it to 3GB of RAM
and see how it runs.
The boot blocks are from 3.0-RELEASE and they will boot the old a.out
kernel via /boot/loader quite happily. We haven't yet managed to boot
an ELF kernel, though (but we haven't tried to boot an unpatched one).
It's also somewhat painful to debug because the machine is miles away
and its serial console is causing trouble.
Are there any obvious things we have missed? I assume the kernel load
address is read by /boot/loader from the kernel's ELF header, so that
a recent loader can cope. I also assume that the patch included below
tweaks all of the required knobs.
Yes, you need to patch load_elf.c -- here is what I have:
nautilus% diff -u load_elf.c /usr/src/sys/boot/common/load_elf.c
--- load_elf.c Mon Mar 29 07:29:18 1999
+++ /usr/src/sys/boot/common/load_elf.c Mon Jan 4 10:37:41 1999
@@ -229,7 +229,7 @@
firstaddr = lastaddr = 0;
if (kernel) {
#ifdef __i386__
- off = - (off 0xff00u);
+ off = 0x1000; /* -0xf000 - i386 relocates after locore */
#else
off = 0;/* alpha is direct mapped for kernels */
#endif
To Unsubscribe: send mail to majord...@freebsd.org
with unsubscribe freebsd-current in the body of the message
make buildworld fails
Updated as of the build ... Script started on Sun Mar 28 22:46:48 1999 # make -DCLOBBER -j6 buildworld -- Cleaning up the temporary elf build tree -- mkdir -p /usr/obj/usr/src/tmp chflags -R noschg /usr/obj/usr/src/tmp/ rm -rf /usr/obj/usr/src/tmp -- Making make .. skipping .. cc -O -pipe -DLIBC_RCS -DSYSLIBC_RCS -I/usr/src/lib/libc_r/../libc/include -DPTHREAD_KERNEL -D_THREAD_SAFE -DNOPOLL -I/usr/src/lib/libc_r/uthread -D__DBINTERFACE_PRIVATE -DPOSIX_MISTAKE -I/usr/src/lib/libc_r/../libc/locale -DBROKEN_DES -DYP -I/usr/obj/usr/src/tmp/usr/include -c /usr/src/lib/libc_r/../libc/gen/getvfsent.c -o getvfsent.o cc -O -pipe -DLIBC_RCS -DSYSLIBC_RCS -I/usr/src/lib/libc_r/../libc/include -DPTHREAD_KERNEL -D_THREAD_SAFE -DNOPOLL -I/usr/src/lib/libc_r/uthread -D__DBINTERFACE_PRIVATE -DPOSIX_MISTAKE -I/usr/src/lib/libc_r/../libc/locale -DBROKEN_DES -DYP -I/usr/obj/usr/src/tmp/usr/include -c /usr/src/lib/libc_r/../libc/gen/glob.c -o glob.o cc -O -pipe -DLIBC_RCS -DSYSLIBC_RCS -I/usr/src/lib/libc_r/../libc/include -DPTHREAD_KERNEL -D_THREAD_SAFE -DNOPOLL -I/usr/src/lib/libc_r/uthread -D__DBINTERFACE_PRIVATE -DPOSIX_MISTAKE -I/usr/src/lib/libc_r/../libc/locale -DBROKEN_DES -DYP -I/usr/obj/usr/src/tmp/usr/include -c /usr/src/lib/libc_r/../libc/gen/initgroups.c -o initgroups.o cc -O -pipe -DLIBC_RCS -DSYSLIBC_RCS -I/usr/src/lib/libc_r/../libc/include -DPTHREAD_KERNEL -D_THREAD_SAFE -DNOPOLL -I/usr/src/lib/libc_r/uthread -D__DBINTERFACE_PRIVATE -DPOSIX_MISTAKE -I/usr/src/lib/libc_r/../libc/locale -DBROKEN_DES -DYP -I/usr/obj/usr/src/tmp/usr/include -c /usr/src/lib/libc_r/../libc/gen/isatty.c -o isatty.o cc -O -pipe -DLIBC_RCS -DSYSLIBC_RCS -I/usr/src/lib/libc_r/../libc/include -DPTHREAD_KERNEL -D_THREAD_SAFE -DNOPOLL -I/usr/src/lib/libc_r/uthread -D__DBINTERFACE_PRIVATE -DPOSIX_MISTAKE -I/usr/src/lib/libc_r/../libc/locale -DBROKEN_DES -DYP -I/usr/obj/usr/src/tmp/usr/include -c /usr/src/lib/libc_r/../libc/gen/jrand48.c -o jrand48.o In file included from /usr/src/lib/libc_r/../libc/gen/isatty.c:42: /usr/src/lib/libc_r/uthread/pthread_private.h:793: parse error before `_sched_switch_hook' /usr/src/lib/libc_r/uthread/pthread_private.h:797: warning: data definition has no type or storage class *** Error code 1 1 error *** Error code 2 1 error *** Error code 2 1 error *** Error code 2 1 error *** Error code 2 1 error *** Error code 2 1 error -- Regards, Kevin G. Eliuk Discover Rock Solid, Discover FreeBSD | http://www.FreeBSD.Org To Unsubscribe: send mail to majord...@freebsd.org with unsubscribe freebsd-current in the body of the message
Re: make buildworld fails
Kevin G. Eliuk wrote: cc -O -pipe -DLIBC_RCS -DSYSLIBC_RCS -I/usr/src/lib/libc_r/../libc/include -DPTHREAD_KERNEL -D_THREAD_SAFE -DNOPOLL -I/usr/src/lib/libc_r/uthread -D__DBINTERFACE_PRIVATE -DPOSIX_MISTAKE -I/usr/src/lib/libc_r/../libc/locale -DBROKEN_DES -DYP -I/usr/obj/usr/src/tmp/usr/include -c /usr/src/lib/libc_r/../libc/gen/jrand48.c -o jrand48.o In file included from /usr/src/lib/libc_r/../libc/gen/isatty.c:42: /usr/src/lib/libc_r/uthread/pthread_private.h:793: parse error before `_sched_switch_hook' /usr/src/lib/libc_r/uthread/pthread_private.h:797: warning: data definition has no type or storage class *** Error code 1 Has src/include been updated? The missing type should be in src/include/pthread_np.h (pthread_switch_routine_t). Dan Eischen eisc...@vigrid.com To Unsubscribe: send mail to majord...@freebsd.org with unsubscribe freebsd-current in the body of the message
Re: booting systems with lots of memory
Jan B. Koum j...@best.com wrote: Tony Finch d...@dotat.at wrote: Are there any obvious things we have missed? I assume the kernel load address is read by /boot/loader from the kernel's ELF header, so that a recent loader can cope. I also assume that the patch included below tweaks all of the required knobs. Yes, you need to patch load_elf.c Excellent! Thanks for the quick reply. Will /boot/loader still be able to boot old kernels after this patch? (I'm reluctant to completely hose the machine...) Also, w.r.t. the serial console problems, can I set the baud rate early in the boot sequence, and if so, how? The console works once getty puts up a login prompt but not before then, and I get a whole lot of garbage that I guess is baud barf (I wouldn't know for sure -- too much of a newbie). Tony. -- f.a.n.finch d...@dotat.at f...@demon.net To Unsubscribe: send mail to majord...@freebsd.org with unsubscribe freebsd-current in the body of the message
Re: booting systems with lots of memory
On Mon, Mar 29, 1999 at 05:45:02PM +0100, Tony Finch d...@dotat.at wrote: Jan B. Koum j...@best.com wrote: Tony Finch d...@dotat.at wrote: Are there any obvious things we have missed? I assume the kernel load address is read by /boot/loader from the kernel's ELF header, so that a recent loader can cope. I also assume that the patch included below tweaks all of the required knobs. Yes, you need to patch load_elf.c Excellent! Thanks for the quick reply. Will /boot/loader still be able to boot old kernels after this patch? (I'm reluctant to completely hose the machine...) AFAIK it should. Not sure myself to be honest :( Also, w.r.t. the serial console problems, can I set the baud rate early in the boot sequence, and if so, how? The console works once getty puts up a login prompt but not before then, and I get a whole lot of garbage that I guess is baud barf (I wouldn't know for sure -- too much of a newbie). Don't know. I don't use serial console. Did you check http://www.freebsd.org/~msmith/FTL/bootstrap.txt for any info? -- Yan To Unsubscribe: send mail to majord...@freebsd.org with unsubscribe freebsd-current in the body of the message
Re: Status of 'tee' firewall action
Unfortunatly the 'tee' option is quite a bit more complicated than it looks.this is because teh normal way that packets get to divert sockets and the way it'd have to get there from a 'tee' are kinda incompatible. It can be done but it's just not quite as straight forward as it first appears.. julian On Mon, 29 Mar 1999, Roman V. Palagin wrote: Hello! What the status of 'tee' action? Anybody working on it? - Roman V. Palagin | RVP1-6BONE, RP40-RIPE| Network Administrator - To Unsubscribe: send mail to majord...@freebsd.org with unsubscribe freebsd-current in the body of the message To Unsubscribe: send mail to majord...@freebsd.org with unsubscribe freebsd-current in the body of the message
Re: booting systems with lots of memory
Jan B. Koum writes: Tony Finch d...@dotat.at wrote: Excellent! Thanks for the quick reply. Will /boot/loader still be able to boot old kernels after this patch? (I'm reluctant to completely hose the machine...) AFAIK it should. Not sure myself to be honest :( Well, I took the plunge and booted with the new loader and the box came back fine, so I'm less worried about booting old kernels. Tomorrow we try it with 3GB of RAM :-) Also, w.r.t. the serial console problems, can I set the baud rate early in the boot sequence, and if so, how? The console works once getty puts up a login prompt but not before then, and I get a whole lot of garbage that I guess is baud barf (I wouldn't know for sure -- too much of a newbie). Don't know. I don't use serial console. Did you check http://www.freebsd.org/~msmith/FTL/bootstrap.txt for any info? I did, yes. Most of that is now in the loader(8) manual. I tried changing /boot.config to contain /boot/loader -h which improved matters. There's still some garbage but it's fine after FreeBSD BOOT @ 0x1: 634/15360 k of memory, serial console. We suspect a BIOS that's being too damn clever for its own good. Tony. -- f.a.n.finch f...@demon.net d...@dotat.at To Unsubscribe: send mail to majord...@freebsd.org with unsubscribe freebsd-current in the body of the message
Re: Status of 'tee' firewall action
Julian Elischer writes: Unfortunatly the 'tee' option is quite a bit more complicated than it looks.this is because teh normal way that packets get to divert sockets and the way it'd have to get there from a 'tee' are kinda incompatible. It can be done but it's just not quite as straight forward as it first appears.. On Mon, 29 Mar 1999, Roman V. Palagin wrote: What the status of 'tee' action? Anybody working on it? As a workaround, use divert instead of tee and immediately write any packet you read, using the same struct sockaddr, back to the socket. -Archie ___ Archie Cobbs * Whistle Communications, Inc. * http://www.whistle.com To Unsubscribe: send mail to majord...@freebsd.org with unsubscribe freebsd-current in the body of the message
Re: booting systems with lots of memory
I did, yes. Most of that is now in the loader(8) manual. I tried changing /boot.config to contain /boot/loader -h which improved matters. There's still some garbage but it's fine after FreeBSD BOOT @ 0x1: 634/15360 k of memory, serial console. We suspect a BIOS that's being too damn clever for its own good. That sounds about right. If your BIOS on the Intel box is set for a serial console, you could try poking it again to make sure that it's set for 9600 bps and that the various 'magic' options relating to remote health monitoring are all off. I'd fire the one here up to be more specific, but it trips the breaker on this row of offices... -- \\ Sometimes you're ahead, \\ Mike Smith \\ sometimes you're behind. \\ m...@smith.net.au \\ The race is long, and in the \\ msm...@freebsd.org \\ end it's only with yourself. \\ msm...@cdrom.com To Unsubscribe: send mail to majord...@freebsd.org with unsubscribe freebsd-current in the body of the message
Bug with afd0 (zip-drive)
Hi, I'm not able to use msdos disks with afd0. It isn't usable with the mtools too (yes, I've used MAKEDEV to make the needed dev-nodes). cvsup at 7pm CET. not able to use: mdir z: init Z: non DOS media Cannot initialize 'Z:' mount /zip msdos: /dev/afd0s4: Invalid argument Am I missing something? Bye, Alexander. P.S.: dmesg/... at request via private mail. To Unsubscribe: send mail to majord...@freebsd.org with unsubscribe freebsd-current in the body of the message
Bug with VESA?
Hi, cvsup 7pm CET. I'm not able to switch to 132x60 anymore. Last cvsup was around feb 1999. dmesg: VESA: v0.40, 40960k memory, flags:0x7461, mode table: 0xc08de022 (280c000) ^ seems to be wrong (4096k) VESA: Matrox Graphics Inc. (it's a Mystique 220) vga0: Matrox MGA 1024SG/1064SG/1164SG graphics accelerator rev 0x03 int a irq 11 on pci0.12.0 sc0: flags 0x6 on isa sc0: VGA color 16 virtual consoles, flags=0x6 More (dmesg/...) on request via private mail. Bye, Alexander. To Unsubscribe: send mail to majord...@freebsd.org with unsubscribe freebsd-current in the body of the message
Re: make buildworld fails
Hi,
I had exactly the same. Have you by chance got an old
/usr/src/lib/libc_r/uthread/pthread{.h,_nb.h}? Then remove them, they
conflict with /usr/src/include/pthread{.h,_nb.h}.
On Mon, 29 Mar 1999, Kevin G. Eliuk wrote:
Updated as of the build ...
Script started on Sun Mar 28 22:46:48 1999
# make -DCLOBBER -j6 buildworld
--
Cleaning up the temporary elf build tree
--
mkdir -p /usr/obj/usr/src/tmp
chflags -R noschg /usr/obj/usr/src/tmp/
rm -rf /usr/obj/usr/src/tmp
--
Making make
.. skipping ..
cc -O -pipe -DLIBC_RCS -DSYSLIBC_RCS -I/usr/src/lib/libc_r/../libc/include
-DPTHREAD_KERNEL -D_THREAD_SAFE -DNOPOLL -I/usr/src/lib/libc_r/uthread
-D__DBINTERFACE_PRIVATE -DPOSIX_MISTAKE -I/usr/src/lib/libc_r/../libc/locale
-DBROKEN_DES -DYP -I/usr/obj/usr/src/tmp/usr/include -c
/usr/src/lib/libc_r/../libc/gen/getvfsent.c -o getvfsent.o
cc -O -pipe -DLIBC_RCS -DSYSLIBC_RCS -I/usr/src/lib/libc_r/../libc/include
-DPTHREAD_KERNEL -D_THREAD_SAFE -DNOPOLL -I/usr/src/lib/libc_r/uthread
-D__DBINTERFACE_PRIVATE -DPOSIX_MISTAKE -I/usr/src/lib/libc_r/../libc/locale
-DBROKEN_DES -DYP -I/usr/obj/usr/src/tmp/usr/include -c
/usr/src/lib/libc_r/../libc/gen/glob.c -o glob.o
cc -O -pipe -DLIBC_RCS -DSYSLIBC_RCS -I/usr/src/lib/libc_r/../libc/include
-DPTHREAD_KERNEL -D_THREAD_SAFE -DNOPOLL -I/usr/src/lib/libc_r/uthread
-D__DBINTERFACE_PRIVATE -DPOSIX_MISTAKE -I/usr/src/lib/libc_r/../libc/locale
-DBROKEN_DES -DYP -I/usr/obj/usr/src/tmp/usr/include -c
/usr/src/lib/libc_r/../libc/gen/initgroups.c -o initgroups.o
cc -O -pipe -DLIBC_RCS -DSYSLIBC_RCS -I/usr/src/lib/libc_r/../libc/include
-DPTHREAD_KERNEL -D_THREAD_SAFE -DNOPOLL -I/usr/src/lib/libc_r/uthread
-D__DBINTERFACE_PRIVATE -DPOSIX_MISTAKE -I/usr/src/lib/libc_r/../libc/locale
-DBROKEN_DES -DYP -I/usr/obj/usr/src/tmp/usr/include -c
/usr/src/lib/libc_r/../libc/gen/isatty.c -o isatty.o
cc -O -pipe -DLIBC_RCS -DSYSLIBC_RCS -I/usr/src/lib/libc_r/../libc/include
-DPTHREAD_KERNEL -D_THREAD_SAFE -DNOPOLL -I/usr/src/lib/libc_r/uthread
-D__DBINTERFACE_PRIVATE -DPOSIX_MISTAKE -I/usr/src/lib/libc_r/../libc/locale
-DBROKEN_DES -DYP -I/usr/obj/usr/src/tmp/usr/include -c
/usr/src/lib/libc_r/../libc/gen/jrand48.c -o jrand48.o
In file included from /usr/src/lib/libc_r/../libc/gen/isatty.c:42:
/usr/src/lib/libc_r/uthread/pthread_private.h:793: parse error before
`_sched_switch_hook'
/usr/src/lib/libc_r/uthread/pthread_private.h:797: warning: data definition
has no type or storage class
*** Error code 1
1 error
*** Error code 2
1 error
*** Error code 2
1 error
*** Error code 2
1 error
*** Error code 2
1 error
*** Error code 2
1 error
--
Regards,
Kevin G. Eliuk
Discover Rock Solid, Discover FreeBSD | http://www.FreeBSD.Org
Regards,
Vladimir
===|===
Vladimir Kushnir |
ku...@mail.kar.net, |Powered by FreeBSD
kush...@ap3.bitp.kiev.ua |
To Unsubscribe: send mail to majord...@freebsd.org
with unsubscribe freebsd-current in the body of the message
make release doc failure
Hi, Subject says it all... Thanks, John === Cleaning for tidy-0.1.99.1 === Cleaning for docproj-1.0 === FAQ sgmlfmt -f html -links /usr/doc/FAQ/FAQ.sgml sgmlfmt: not found *** Error code 1 To Unsubscribe: send mail to majord...@freebsd.org with unsubscribe freebsd-current in the body of the message
Re: HEADS UP!! NOAOUT `make world' knob changed
On Monday, 29 March 1999 at 3:02:28 -0800, David O'Brien wrote: I have just changed made a change concerning the building of legacy a.out bits during `make world'. Previous to my change, one would define NOAOUT to keep from building the legacy a.out bits. Now one would define WANT_AOUT to build them. OK, which bits? Does this mean that new systems will no longer run a.out binaries? Or will the libraries no longer be built? Will the existing ones be removed? Greg -- See complete headers for address, home page and phone numbers finger g...@lemis.com for PGP public key To Unsubscribe: send mail to majord...@freebsd.org with unsubscribe freebsd-current in the body of the message
Re: HEADS UP!! NOAOUT `make world' knob changed
Previous to my change, one would define NOAOUT to keep from building the legacy a.out bits. Now one would define WANT_AOUT to build them. Does this mean that new systems will no longer run a.out binaries? No. Or will the libraries no longer be built? Yes. Will the existing ones be removed? No. -- -- David(obr...@nuxi.com -or- obr...@freebsd.org) To Unsubscribe: send mail to majord...@freebsd.org with unsubscribe freebsd-current in the body of the message
Re: Bug with VESA?
cvsup 7pm CET. I'm not able to switch to 132x60 anymore. Last cvsup was around feb 1999. Please check the revision of /sys/i386/isa/vesa.c. Is it 1.18 or 1.19? I committed fix for a palette loading problem in vesa.c at 7am PST. This is the latest revision (1.19). The modification has nothing to do with the VESA BIOS initialization and shouldn't be causing this sort of problem. But,... dmesg: VESA: v0.40, 40960k memory, flags:0x7461, mode table: 0xc08de022 (280c000) ~ ~~ ~~~ ^ seems to be wrong (4096k) They all look wrong ;- VESA: Matrox Graphics Inc. (it's a Mystique 220) Right. I think I can find one around here. vga0: Matrox MGA 1024SG/1064SG/1164SG graphics accelerator rev 0x03 int a ir q 11 on pci0.12.0 sc0: flags 0x6 on isa sc0: VGA color 16 virtual consoles, flags=0x6 More (dmesg/...) on request via private mail. Please give the '-v' option at the boot loader prompt when starting the kernel. and send me the complete dmesg output and your kernel configuration file. Thank you for your cooperation. Kazu To Unsubscribe: send mail to majord...@freebsd.org with unsubscribe freebsd-current in the body of the message
nfs_getpages: error 4, vm_fault
Greetings, I am running two machines with current from Sunday, March 28 at 3:20PM CST, but the problems I am seeing I have seen for a while now (about a month). I thought an upgrade might fix them. Here are the specs on the machines: Machine A: Dual PPro 200MHz, 128MB RAM, SCSI disks on an onboard Adaptec 7880, rl0 driver (Realtek 8139) Machine B: Dual Pentium 133, 64MB RAM, IDE disks, xl0 driver (3COM 905B) Both machines are connected via a 10/100 hub, and are operating at 100Mb/s half duplex. Machine A is the NFS server, and machine B is the client. Machine B runs apache and serves up some web pages over NFS from machine A. I am mounting with options rw,intr in machine B's fstab. According to the mount_nfs manpage, I am using nfsv3 since my server allows that. When certain files on machine A are accessed by the web daemon on machine B, the httpd process hangs, and when I eventually use apachectl to stop it, here is what is printed out on machine B's console: Mar 29 18:30:04 wall /kernel: nfs_getpages: error 4 Mar 29 18:30:04 wall /kernel: vm_fault: pager read error, pid 274 (httpd) I can reproduce this fairly easily if need be. I looked in the mail archives, but didn't see anyone else seeing this problem recently. Anyone have any clues on this one? I can provide more information if needed. Thanks. -- Kyle Mestery StorageTek's Storage Networking Group Protect your right to privacy: www.freecrypto.org To Unsubscribe: send mail to majord...@freebsd.org with unsubscribe freebsd-current in the body of the message
Re: nfs_getpages: error 4, vm_fault
You might try instrumenting nfs/nfs_bio.c to find where the EINTR is coming from. If it's reproducible then you should be able (with a few reboots) to track it back quite a distance. julian On Mon, 29 Mar 1999 mest...@visi.com wrote: Greetings, I am running two machines with current from Sunday, March 28 at 3:20PM CST, but the problems I am seeing I have seen for a while now (about a month). I thought an upgrade might fix them. Here are the specs on the machines: Machine A: Dual PPro 200MHz, 128MB RAM, SCSI disks on an onboard Adaptec 7880, rl0 driver (Realtek 8139) Machine B: Dual Pentium 133, 64MB RAM, IDE disks, xl0 driver (3COM 905B) Both machines are connected via a 10/100 hub, and are operating at 100Mb/s half duplex. Machine A is the NFS server, and machine B is the client. Machine B runs apache and serves up some web pages over NFS from machine A. I am mounting with options rw,intr in machine B's fstab. According to the mount_nfs manpage, I am using nfsv3 since my server allows that. When certain files on machine A are accessed by the web daemon on machine B, the httpd process hangs, and when I eventually use apachectl to stop it, here is what is printed out on machine B's console: Mar 29 18:30:04 wall /kernel: nfs_getpages: error 4 Mar 29 18:30:04 wall /kernel: vm_fault: pager read error, pid 274 (httpd) I can reproduce this fairly easily if need be. I looked in the mail archives, but didn't see anyone else seeing this problem recently. Anyone have any clues on this one? I can provide more information if needed. Thanks. -- Kyle Mestery StorageTek's Storage Networking Group Protect your right to privacy: www.freecrypto.org To Unsubscribe: send mail to majord...@freebsd.org with unsubscribe freebsd-current in the body of the message To Unsubscribe: send mail to majord...@freebsd.org with unsubscribe freebsd-current in the body of the message
Re: HEADS UP!! NOAOUT `make world' knob changed
I have just changed made a change concerning the building of legacy a.out bits during `make world'. Previous to my change, one would define NOAOUT to keep from building the legacy a.out bits. Now one would define WANT_AOUT to build them. The default of building a.out bits gets in the way of some other changes I will make to the `build world' process soon. Will WANT_AOUT be considered a supported option? That is, if I choose to build a.out libraries, will I be giving up the right to gripe when `make world' breaks, and be resigned to the ranks of the NOCLEAN masses? Cheers, joelh -- Joel Ray Holveck - jo...@gnu.org Fourth law of programming: Anything that can go wrong wi sendmail: segmentation violation - core dumped To Unsubscribe: send mail to majord...@freebsd.org with unsubscribe freebsd-current in the body of the message
Re: HEADS UP!! NOAOUT `make world' knob changed
Will WANT_AOUT be considered a supported option? If I can get it to work. That is, if I choose to build a.out libraries, will I be giving up the right to gripe when `make world' breaks, and be resigned to the ranks of the NOCLEAN masses? At this time (well... you will know when you time comes). Right now, I do need it tested that WANT_AOUT works. -- -- David(obr...@nuxi.com -or- obr...@freebsd.org) To Unsubscribe: send mail to majord...@freebsd.org with unsubscribe freebsd-current in the body of the message
Re: make buildworld fails
On Mon, 29 Mar 1999, Vladimir Kushnir wrote:
Hi,
I had exactly the same. Have you by chance got an old
/usr/src/lib/libc_r/uthread/pthread{.h,_nb.h}?
That's an affirmative, I've moved them and will retry the build
just as soon as I look into this new egcs stuff I checked out :)
--
Regards,
Kevin G. Eliuk
Discover Rock Solid, Discover FreeBSD | http://www.FreeBSD.Org
To Unsubscribe: send mail to majord...@freebsd.org
with unsubscribe freebsd-current in the body of the message
the ATA driver
Just letting someone know/confirming something: The ata drivers cvsupped 10 minutes ago have slowed my disk access to a crawl. I went from 12 MB per second to 6 MB per second. Just thought I'd let someone know because this seems to be a major problem. Thanks. Kenneth To Unsubscribe: send mail to majord...@freebsd.org with unsubscribe freebsd-current in the body of the message
