Re: UPDATE3: ATA/ATAPI driver new version available.
Driver works fine, but on my notebook, when HDD awake from sleep I see at0: unvanted interrupt message. Maybe we need flag similar to SLEEP_HACK on wd driver? Sincerely, Maxim S?ren Schmidt wrote: Third update to the new ATA/ATAPI driver: ZIP drives should now be working, I'm not sure about LS120 drives, reports on those most welcome! Fixed problems: ??? Hang on probe on fantom devices. ??? The probe now use a timeout to avoid hangs if no interrupt ??? is received. There has also been more general code clenaups, and some reorgs. As usual USE AT YOUR OWN RISK!!, this is still pre alpha level code. But please tell me how it works for you! Enjoy! -S?ren 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: UPDATE3: ATA/ATAPI driver new version available.
It seems Maxim Sobolev wrote: Driver works fine, but on my notebook, when HDD awake from sleep I see at0: unvanted interrupt message. Maybe we need flag similar to SLEEP_HACK on wd driver? I'm not sure how I'm going to handle this yet, but it is on my TODO list... -Søren To Unsubscribe: send mail to majord...@freebsd.org with unsubscribe freebsd-current in the body of the message
Re: buildworld failure as of 1999-03-08
Hmm, must have been a gremlin. cvsup'ed again yesterday (didn't look like anything related to the problem had changed), did another buildworld, and this time it worked. Oh, well. -- Christian naddy Weisgerber na...@mips.rhein-neckar.de H Deutsche Transhumanismus-Mailingliste echo 'subscribe trans-de' | mail majord...@lists.rhein-neckar.de To Unsubscribe: send mail to majord...@freebsd.org with unsubscribe freebsd-current in the body of the message
egcs-snap-world
Hi,
just in case someone is interested (i'm not a particular advocat of
the need of the world and kernel being able to be compiled with
something else than the system-compiler; just to show that the current
sources apparently do not depend a lot on FreeBSD-specific features of
gcc/binutils): applying some minor changes, I compiled the world with
an arbitrary mix of a recent egcs-cvs-snapshot and binutils-2.9.1.0.19
(haifa-scheduling enabled) I regularly use for userland compilations,
using the following script:
#! /bin/bash
export CC='/usr/vol/opt/freebsd3/egcs-snap/bin/gcc
-B/usr/vol/opt/freebsd3/egcs-snap/bin/
-B/usr/vol/opt/freebsd3/egcs-snap/lib/gcc-lib/i686-pc-freebsdelf/egcs-2.92.32/
-v -MD '
export CXX='/usr/vol/opt/freebsd3/egcs-snap/bin/c++
-B/usr/vol/opt/freebsd3/egcs-snap/bin/
-B/usr/vol/opt/freebsd3/egcs-snap/lib/gcc-lib/i686-pc-freebsdelf/egcs-2.92.32/
-v -I/usr/vol/opt/freebsd3/egcs-snap/include/g++-2 -MD '
make -DNOGAMES -DNOAOUT $*
I compiled buildworld on an Intel Madrona:
FreeBSD siamese-twins 3.1-STABLE FreeBSD 3.1-STABLE #1: Fri Feb 19 21:16:03 MET
1999
t...@siamese-twins:/usr/src_RELENG_3/sys/compile/SIAM i386
Further, I did an installworld on my current-machine, an Intergraph TD4
(dual-P90):
CPU: Pentium/P54C (90.00-MHz 586-class CPU)
eisa0: ING2280 (System Board)
ncr0: ncr 53c810 fast10 scsi rev 0x01 int a irq 11 on pci0.7.0
da0 at ncr0 bus 0 target 0 lun 0
da0: QUANTUM FIREBALL ST3.2S 0F0C Fixed Direct Access SCSI-2 device
da0: 10.000MB/s transfers (10.000MHz, offset 8), Tagged Queueing Enabled
da0: 3090MB (6328861 512 byte sectors: 255H 63S/T 393C)
and then re-compiled the kernel with CC='/usr/bin/cc -pipe -fformat-extensions '
This is not a really good test since this system is very slow and rather
unreliable under cc-compiled world as well; anyway, for basic
``workstation-use''
(xntpd, nfs, xterm, compiling ports etc.) so far I did not notice any difference
with the cc-compiled world (when I've time, I'll install a Dual-PPro as
alternative
current-machine).
For completeness, this is kldstat-output: (I recompiled nfs into the kernel; no
notable
difference with using nfs.ko)
Id Refs AddressSize Name
14 0xf010 189ef0 kernel
21 0xf08f4000 6000 procfs.ko
31 0xf090d000 e000 linux.ko
41 0xf0922000 2000 green_saver.ko
Voila the cvs-diff on the source tree: (especially for the vinum-mods, I was not
concerned at all for semantic correctness; if someone is interested, I put a
cvs-context-diff
as well as my log-file and dependency-output on
ftp://heho.snv.jussieu.fr/pub/FreeBSD_egcs/ )
Index: bin/sh/Makefile
===
RCS file: /home/ncvs/src/bin/sh/Makefile,v
retrieving revision 1.28
diff -r1.28 Makefile
41a42,43
${BRANDELF} ${.TARGET}
Index: gnu/lib/Makefile
===
RCS file: /home/ncvs/src/gnu/lib/Makefile,v
retrieving revision 1.19
diff -r1.19 Makefile
3c3
SUBDIR= libdialog libg++ libgmp libmp libobjc libregex libreadline libstdc++
---
SUBDIR= libdialog libgmp libmp libregex libreadline
Index: gnu/usr.bin/Makefile
===
RCS file: /home/ncvs/src/gnu/usr.bin/Makefile,v
retrieving revision 1.44
diff -r1.44 Makefile
3c3
SUBDIR= awk bc binutils bison cc cpio cvs dc dialog diff diff3 genclass gperf
\
---
SUBDIR= awk bc binutils bison cpio cvs dc dialog diff diff3 genclass gperf \
Index: gnu/usr.bin/cc/cc_tools/Makefile
===
RCS file: /home/ncvs/src/gnu/usr.bin/cc/cc_tools/Makefile,v
retrieving revision 1.14
diff -r1.14 Makefile
30a31
${BRANDELF} ${.TARGET}
62a64
${BRANDELF} ${.TARGET}
72a75
${BRANDELF} ${.TARGET}
Index: lib/libmytinfo/Makefile
===
RCS file: /home/ncvs/src/lib/libmytinfo/Makefile,v
retrieving revision 1.16
diff -r1.16 Makefile
35a36,37
${BRANDELF} ${.TARGET}
39a42,43
${BRANDELF} ${.TARGET}
46a51,52
${BRANDELF} ${.TARGET}
52a59,60
${BRANDELF} ${.TARGET}
61a70,71
${BRANDELF} ${.TARGET}
64a75,76
${BRANDELF} ${.TARGET}
Index: share/mk/bsd.kern.mk
===
RCS file: /home/ncvs/src/share/mk/bsd.kern.mk,v
retrieving revision 1.15
diff -r1.15 bsd.kern.mk
12c12
-fformat-extensions -ansi
---
-ansi
Index: share/mk/bsd.prog.mk
===
RCS file: /home/ncvs/src/share/mk/bsd.prog.mk,v
retrieving revision 1.81
diff -r1.81 bsd.prog.mk
39a40
${BRANDELF} ${.TARGET}
54a56
${BRANDELF} ${.TARGET}
Index: share/mk/sys.mk
===
RCS file: /home/ncvs/src/share/mk/sys.mk,v
retrieving revision 1.43
diff -r1.43 sys.mk
Re: Simple DOS against 3.x locks box solid
At 04:35 PM 3/4/99 -0800, Matthew Dillon wrote: Well, this was easy to duplicate. I'll try to track it down. It seems to occur under -4.x as well as -3.x. Definitely an inode deadlock of some kind. -Matt :Try changing the 'find' to 'find -x'. If this still locks up the machine :we will have to then determine whether it occurs under 4.x as well, or :if it only occurs under 3.x. : -Matt : :: As posted by y...@dgtu.donetsk.ua :: :: This script freeze my 3.1-RELEASE box. :: I can't make any connection with my box, also from console. :: :: cut here --- :: #! /bin/sh :: :: for j in 1 2 3 4 5 6 7 8 9 10 :: do :: echo -n $j :: nohup sh -c 'while :; do find / -type file |xargs fgrep fticom; done' :: /dev/null 21 :: echo :: done :: - cut here :: :: -- :: Yury V. Yaroshevsky | Donetsk State Technical University :: YY18-RIPE | (380 622) 356455 y...@dgtu.donetsk.ua Mike Tancsa, tel 01.519.651.3400 Network Administrator,m...@sentex.net Sentex Communications www.sentex.net Cambridge, Ontario Canada To Unsubscribe: send mail to majord...@freebsd.org with unsubscribe freebsd-current in the body of the message
Re: fd broken [!!!]
On Sat, 6 Mar 1999, Thomas Dean wrote: So Does anyone have an idea why the hell fd(4) broke?! I have the same problem on 4.0-current SMP of Mon Feb 15 03:34:29 PST 1999. tomdean To Unsubscribe: send mail to majord...@freebsd.org with unsubscribe freebsd-current in the body of the message Brian Feldman_ __ ___ ___ ___ gr...@unixhelp.org _ __ ___ | _ ) __| \ http://www.freebsd.org/ _ __ ___ | _ \__ \ |) | FreeBSD: The Power to Serve! _ __ ___ _ |___/___/___/ To Unsubscribe: send mail to majord...@freebsd.org with unsubscribe freebsd-current in the body of the message
Secondary IDE woes
Hi all, I recompiled -current last week, and have been having intermittent problems with my secondary IDE controller not being detected since. Sometimes when I boot, it sees the controller with no problems. Most often though, it doesn't detect it at all. I recompiled again with today's sources and the problem persists. Here's the dmesg output, any help would be appreciated. Cheers, Peter Copyright (c) 1992-1999 FreeBSD Inc. Copyright (c) 1982, 1986, 1989, 1991, 1993 The Regents of the University of California. All rights reserved. FreeBSD 4.0-CURRENT #19: Tue Mar 9 15:21:37 CST 1999 p...@orthanc.kellogg.nwu.edu:/usr/src/sys/compile/ORTHANC Timecounter i8254 frequency 1193182 Hz Timecounter TSC frequency 297998769 Hz CPU: Pentium II (298.00-MHz 686-class CPU) Origin = GenuineIntel Id = 0x634 Stepping=4 Features=0x80f9ffFPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,SEP,MTRR,PGE,MCA,CMOV,MMX real memory = 134217728 (131072K bytes) avail memory = 127864832 (124868K bytes) Preloaded elf kernel kernel at 0xf02ad000. Probing for devices on PCI bus 0: chip0: Host to PCI bridge (vendor=8086 device=7180) rev 0x03 on pci0.0.0 chip1: PCI to PCI bridge (vendor=8086 device=7181) rev 0x03 on pci0.1.0 chip2: Intel 82371AB PCI to ISA bridge rev 0x01 on pci0.7.0 ide_pci0: Intel PIIX4 Bus-master IDE controller rev 0x01 on pci0.7.1 chip3: Intel 82371AB Power management controller rev 0x01 on pci0.7.3 ahc0: Adaptec 2940 Ultra SCSI adapter rev 0x01 int a irq 10 on pci0.13.0 ahc0: aic7880 Wide Channel A, SCSI Id=7, 16/255 SCBs vga0: Matrox MGA 2164W graphics accelerator rev 0x00 int a irq 9 on pci0.14.0 chip4: PCI to PCI bridge (vendor=1011 device=0024) rev 0x03 on pci0.15.0 xl0: 3Com 3c905 Fast Etherlink XL 10/100BaseTX rev 0x00 int a irq 11 on pci0.17.0 xl0: Ethernet address: 00:c0:4f:8c:c1:c1 xl0: autoneg complete, link status good (full-duplex, 100Mbps) Probing for devices on PCI bus 1: vga1: ATI model 4744 graphics accelerator rev 0x5c on pci1.0.0 Probing for devices on PCI bus 2: Probing for devices on the ISA bus: sc0 on isa sc0: VGA color 16 virtual consoles, flags=0x0 atkbdc0 at 0x60-0x6f on motherboard atkbd0 irq 1 on isa sio0 at 0x3f8-0x3ff irq 4 flags 0x10 on isa sio0: type 16550A sio1 at 0x2f8-0x2ff irq 3 on isa sio1: type 16550A psm0 irq 12 on isa psm0: model MouseMan+, device ID 0 fdc0 at 0x3f0-0x3f7 irq 6 drq 2 on isa fdc0: FIFO enabled, 8 bytes threshold fd0: 1.44MB 3.5in wdc0 at 0x1f0-0x1f7 irq 14 on isa wdc0: unit 0 (wd0): QUANTUM FIREBALL ST6.4A wd0: 6149MB (12594960 sectors), 13328 cyls, 15 heads, 63 S/T, 512 B/S wdc1 not found at 0x170 npx0 on motherboard npx0: INT 16 interface vga0 at 0x3b0-0x3df maddr 0xa msize 131072 on isa Waiting 15 seconds for SCSI devices to settle sa0 at ahc0 bus 0 target 0 lun 0 sa0: EXABYTE EXB-85058SQANXR1 07T0 Removable Sequential Access SCSI-2 device sa0: 5.000MB/s transfers (5.000MHz, offset 11) da0 at ahc0 bus 0 target 1 lun 0 da0: SEAGATE ST19101W 0014 Fixed Direct Access SCSI-2 device da0: 20.000MB/s transfers (10.000MHz, offset 8, 16bit), Tagged Queueing Enabled da0: 8363MB (17127880 512 byte sectors: 255H 63S/T 1066C) changing root device to wd0s1a OSS/FreeBSD loading, address = f0bc1d58 -- - Peter Cox - Systems Administrator, Phone: (847) 467 1842 Kellogg Graduate School of Management, Fax: (847) 467 3500 Northwestern University.Email: p-...@nwu.edu - It is impossible to travel faster than light, and certainly not desirable, as one's hat keeps blowing off. -- Woody Allen To Unsubscribe: send mail to majord...@freebsd.org with unsubscribe freebsd-current in the body of the message
HEADS UP: new loader.rc stuff
A new loader.rc mechanism has been introduced. Nothing has changed with loader, mind you, and you can continue to use your current loader.rc (if any) unchanged, but Jordan thinks it might be better to install a loader.rc using the new mechanism by default, to keep support easy, so things might change in the future... Meanwhile, the new loader.rc stuff, for those who want it. It is modeled after rc.conf files. We now have a /boot/defaults/loader.conf, with all defaults (meaning it hardly does anything, serving more as a template), which will also load /boot/loader.conf and /boot/loader.conf.local, in that order, if present. The idea is to leave /boot/loader.conf for sysinstall, /boot/loader.conf.local for the user, and /boot/defaults/loader.conf to installworld. To use this, put the following lines in your /boot/loader.rc: include /boot/loader.4th start Then you can create a /boot/loader.conf.local with whatever other stuff you'd like, such as using a splash screen. Feedback, comments, musings and flames are welcome. (I'd particularly like a better name than start :) -- Daniel C. Sobral(8-DCS) d...@newsguy.com d...@freebsd.org FreeBSD is Yoda, Linux is Luke Skywalker. To Unsubscribe: send mail to majord...@freebsd.org with unsubscribe freebsd-current in the body of the message
wchar.h?
The jikes Java compiler relies on an include file whcar.h being on the system. However, even if it's not, it includes routines to do what it needs... only about 40 lines or so for these functions: wcslen() wcscpy() wcsncpy() wcscat() wcscmp() wcsncmp() How come FreeBSD doesn't have these? Is there a complicated problem preventing us from adding them? Thanks, -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: wchar.h?
On Tue, Mar 09, 1999 at 08:28:41PM -0800, Archie Cobbs wrote: The jikes Java compiler relies on an include file whcar.h being wcsncmp() How come FreeBSD doesn't have these? Is there a complicated problem preventing us from adding them? Wide chars manipulations simple not implemented, if you plan to write some implementation please take a look to some standards first like Single UNIX Specs: http://www.opengroup.org/onlinepubs/7908799/xsh/wchar.h.html -- Andrey A. Chernov http://nagual.pp.ru/~ache/ MTH/SH/HE S-- W-- N+ PEC+ D A a++ C G+ QH+(++) 666+++ Y To Unsubscribe: send mail to majord...@freebsd.org with unsubscribe freebsd-current in the body of the message
Re: HEADS UP: new loader.rc stuff
On Wed, 10 Mar 1999, Daniel C. Sobral wrote: A new loader.rc mechanism has been introduced. Nothing has changed with loader, mind you, and you can continue to use your current loader.rc (if any) unchanged, but Jordan thinks it might be better to install a loader.rc using the new mechanism by default, to keep support easy, so things might change in the future... Meanwhile, the new loader.rc stuff, for those who want it. It is modeled after rc.conf files. We now have a /boot/defaults/loader.conf, with all defaults (meaning it hardly does anything, serving more as a template), which will also load /boot/loader.conf and /boot/loader.conf.local, in that order, if present. The idea is to leave /boot/loader.conf for sysinstall, /boot/loader.conf.local for the user, and /boot/defaults/loader.conf to installworld. To use this, put the following lines in your /boot/loader.rc: include /boot/loader.4th start Then you can create a /boot/loader.conf.local with whatever other stuff you'd like, such as using a splash screen. Feedback, comments, musings and flames are welcome. (I'd particularly like a better name than start :) As long as the man page makes it clear what's going on. All this including of files is going to get damn confusing for newbies. It's also unlike anything i've ever seen before... -Alfred To Unsubscribe: send mail to majord...@freebsd.org with unsubscribe freebsd-current in the body of the message
Re: wchar.h?
Archie Cobbs wrote: The jikes Java compiler relies on an include file whcar.h being on the system. However, even if it's not, it includes routines to do what it needs... only about 40 lines or so for these functions: wcslen() wcscpy() wcsncpy() wcscat() wcscmp() wcsncmp() How come FreeBSD doesn't have these? Is there a complicated problem preventing us from adding them? Look at /usr/include/machine/ansi.h. It has a brief statement about wchar_t. -- Steve To Unsubscribe: send mail to majord...@freebsd.org with unsubscribe freebsd-current in the body of the message
Re: HEADS UP: new loader.rc stuff
Alfred Perlstein wrote: All this including of files is going to get damn confusing for newbies. Hopefully, they won't have to touch them directly, and just use sysinstall. It's also unlike anything i've ever seen before... Actually, it reminds me of the Linux boot loader a little tiny bit... :-) And you could certainly make comparisons with OpenBoot. But, aside from that, you are on the mark here. The new loader gave us a lot of power, and we are not exactly sure how to put that to good use. Up to now, it meant putting actual code inside loader.rc, which results in all sorts of trouble. Using a configuration files is a natural solution for that, and the similarities with rc.conf will, hopefully, make using it easier. Also hopefully, we'll get feedback to correct any mistakes before we get this back to -stable. :-) -- Daniel C. Sobral(8-DCS) d...@newsguy.com d...@freebsd.org FreeBSD is Yoda, Linux is Luke Skywalker. To Unsubscribe: send mail to majord...@freebsd.org with unsubscribe freebsd-current in the body of the message
