Re: mount(2) broken?
In message [EMAIL PROTECTED], Luoqi Chen writes: I'd like to add something about the last buffer wouldn't sync. This occurs when a shutdown syscall is issued when the syncer process is asleep waiting for a buffer write to complete. The write will never complete, because the syncer won't be given a chance to run again, and the buffer will stay marked as busy and become the buffer that wouldn't sync. I haven't thought about a clean way of handling this situation, maybe some of you out there have better ideas... I always thought it would make sense to have the syncer perform the shutdown and cleanup since it had code to write buffers with anyway... -- Poul-Henning Kamp FreeBSD coreteam member [EMAIL PROTECTED] "Real hackers run -current on their laptop." FreeBSD -- It will take a long time before progress goes too far! To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
3.3-stable - 4.0-current problem...
Hi! I've cvsup'ed my 3.3-stable source tree to 4.0-current source tree, and when i'm trying to make buildworld, i'm getting following: echo '#include "i386/freebsd.h"' tm.h echo '#include "i386/perform.h"' tm.h rm -f .depend mkdep -f .depend -a -I/usr/src/gnu/lib/libgcc/../../../contrib/gcc/config -I/usr/src/gnu/lib/libgcc/../../../contrib/gcc -I. -DIN_GCC -I/usr/obj/usr/src/tmp/usr/include /usr/src/gnu/lib/libgcc/../../../contrib/gcc/frame.c Bad system call - core dumped mkdep: compile failed *** Error code 1 Stop in /usr/src/gnu/lib/libgcc. *** Error code 1 And when i'm trying to run buildworld again, following happens: cc -O -pipe -I/usr/src/usr.bin/make -I/usr/obj/usr/src/tmp/usr/include -c /usr/src/usr.bin/make/arch.c *** Signal 12 Stop in /usr/src/usr.bin/make. *** Error code 1 Anybody knows where can be a problem? On my another 4.0 box make world goes just fine... Adios, /KONG Hostas Red (KVK10, KVK10-RIPN) || UNiX Systems Administrator, ComSet ISP To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: 3.3-stable - 4.0-current problem...
I've tried to do the same and it seems that there have been some changes of the signal achitecture. A solution I found was to build a kernel 4.0 before building world. I haven't tried though. Tell me if it works!! EXT Hostas Red wrote: Hi! I've cvsup'ed my 3.3-stable source tree to 4.0-current source tree, and when i'm trying to make buildworld, i'm getting following: echo '#include "i386/freebsd.h"' tm.h echo '#include "i386/perform.h"' tm.h rm -f .depend mkdep -f .depend -a -I/usr/src/gnu/lib/libgcc/../../../contrib/gcc/config -I/usr/src/gnu/lib/libgcc/../../../contrib/gcc -I. -DIN_GCC -I/usr/obj/usr/src/tmp/usr/include /usr/src/gnu/lib/libgcc/../../../contrib/gcc/frame.c Bad system call - core dumped mkdep: compile failed *** Error code 1 Stop in /usr/src/gnu/lib/libgcc. *** Error code 1 And when i'm trying to run buildworld again, following happens: cc -O -pipe -I/usr/src/usr.bin/make -I/usr/obj/usr/src/tmp/usr/include -c /usr/src/usr.bin/make/arch.c *** Signal 12 Stop in /usr/src/usr.bin/make. *** Error code 1 Anybody knows where can be a problem? On my another 4.0 box make world goes just fine... Adios, /KONG Hostas Red (KVK10, KVK10-RIPN) || UNiX Systems Administrator, ComSet ISP To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: 3.3-stable - 4.0-current problem...
Building the kernel first works. also you will need to run the /usr/sbin/config from the /usr/src/usr.sbin tree as the installed one is for the older kernel format. Sean. On Tue, 7 Dec 1999, Marc Solsona wrote: I've tried to do the same and it seems that there have been some changes of the signal achitecture. A solution I found was to build a kernel 4.0 before building world. I haven't tried though. Tell me if it works!! EXT Hostas Red wrote: Hi! I've cvsup'ed my 3.3-stable source tree to 4.0-current source tree, and when i'm trying to make buildworld, i'm getting following: echo '#include "i386/freebsd.h"' tm.h echo '#include "i386/perform.h"' tm.h rm -f .depend mkdep -f .depend -a -I/usr/src/gnu/lib/libgcc/../../../contrib/gcc/config -I/usr/src/gnu/lib/libgcc/../../../contrib/gcc -I. -DIN_GCC -I/usr/obj/usr/src/tmp/usr/include /usr/src/gnu/lib/libgcc/../../../contrib/gcc/frame.c Bad system call - core dumped mkdep: compile failed *** Error code 1 Stop in /usr/src/gnu/lib/libgcc. *** Error code 1 And when i'm trying to run buildworld again, following happens: cc -O -pipe -I/usr/src/usr.bin/make -I/usr/obj/usr/src/tmp/usr/include -c /usr/src/usr.bin/make/arch.c *** Signal 12 Stop in /usr/src/usr.bin/make. *** Error code 1 Anybody knows where can be a problem? On my another 4.0 box make world goes just fine... Adios, /KONG Hostas Red (KVK10, KVK10-RIPN) || UNiX Systems Administrator, ComSet ISP 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 To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: 3.3-stable - 4.0-current problem...
Sean Jensen-Grey wrote: Building the kernel first works. also you will need to run the /usr/sbin/config from the /usr/src/usr.sbin tree as the installed one is for the older kernel format. Sean. This will work: src/usr.sbin/config # make all install use this new config to compile a newly edited current kernel reboot with new kernel make buildworld and so on To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
ps: proc size mismatch for root
Hello everyone, I have just compiled the newest current as of yesterday. The following only happens when the root user does it. [Other users see the normal results for 'ps'] keichii[root]:~# ps -ax ps: proc size mismatch (60320 total, 712 chunks) keichii[root]:~# ps ps: proc size mismatch (36400 total, 712 chunks) keichii[root]:~# This baffles me because it only happens for the root user. However, I used to have a larger procfs when I ran -stable. Here is my df currently, and it used to be bigger. [Another user admined the box, so I do not know what he did.] keichii[root]:~# df Filesystem 1K-blocks UsedAvail Capacity Mounted on [deleted] /dev/wd0s3g230191 216594-4818 102%/usr/obj /dev/wd0s3d109837401436090840%/var procfs 440 100%/proc [deleted] keichii[root]:~# Did I misconfigure procfs? Or what should I do? Thank you, Michael Wu [EMAIL PROTECTED] To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
sbc and ViBRA16X
Alright, I was under the impression that in order for the ViBRA16X soundcard (sound blaster) to work, these lines were needed in the kernel: device pcm0 device sbc0 Am I right, because it doesn't attach a driver to the soundcard. = | Kenneth Culver | FreeBSD: The best OS around.| | Unix Systems Administrator | ICQ #: 24767726 | | and student at The | AIM: AgRSkaterq | | The University of Maryland, | Website: (Under Construction) | | College Park. | http://www.wam.umd.edu/~culverk/| = To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: 3.3-stable - 4.0-current problem...
Hi! On Tue, 7 Dec 1999, Sean Jensen-Grey wrote: Building the kernel first works. also you will need to run the /usr/sbin/config from the /usr/src/usr.sbin tree as the installed one is for the older kernel format. Yes, worked fine, thanks. I've tried to compile new kernel before, but forgot that new config(8) can be made from new source tree ;) Adios, /KONG Hostas Red (KVK10, KVK10-RIPN) || UNiX Systems Administrator, ComSet ISP To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: ps: proc size mismatch for root
Michael Chin-Yuan Wu wrote: Hello everyone, I have just compiled the newest current as of yesterday. The following only happens when the root user does it. [Other users see the normal results for 'ps'] By the way, just to clarify this, I am running -current updated kernels. :) To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: ps: proc size mismatch for root
In message [EMAIL PROTECTED], Michael Chin-Yuan Wu writes: Michael Chin-Yuan Wu wrote: Hello everyone, I have just compiled the newest current as of yesterday. The following only happens when the root user does it. [Other users see the normal results for 'ps'] By the way, just to clarify this, I am running -current updated kernels. :) what is roots ps aliased to ? -- Poul-Henning Kamp FreeBSD coreteam member [EMAIL PROTECTED] "Real hackers run -current on their laptop." FreeBSD -- It will take a long time before progress goes too far! To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: ps: proc size mismatch for root
Poul-Henning Kamp wrote: Michael Chin-Yuan Wu wrote: I have just compiled the newest current as of yesterday. The following only happens when the root user does it. [Other users see the normal results for 'ps'] By the way, just to clarify this, I am running -current updated kernels. :) what is roots ps aliased to ? -- Poul-Henning Kamp FreeBSD coreteam member [EMAIL PROTECTED] ps is not aliased to anything. all the other users have exactly the same .profile .bashrc etc. as root. Only root has this problem To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: ps: proc size mismatch for root
In message [EMAIL PROTECTED], Michael Chin-Yuan Wu writes: Poul-Henning Kamp wrote: Michael Chin-Yuan Wu wrote: I have just compiled the newest current as of yesterday. The following only happens when the root user does it. [Other users see the normal results for 'ps'] By the way, just to clarify this, I am running -current updated kernels. :) what is roots ps aliased to ? -- Poul-Henning Kamp FreeBSD coreteam member [EMAIL PROTECTED] ps is not aliased to anything. all the other users have exactly the same .profile .bashrc etc. as root. Only root has this problem what happens if you type /bin/ps as root ? -- Poul-Henning Kamp FreeBSD coreteam member [EMAIL PROTECTED] "Real hackers run -current on their laptop." FreeBSD -- It will take a long time before progress goes too far! To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Initio SCSI driver
Is there any particular reason why the Initio SCSI driver (available at http://www.initio.com/drivers/BSD3sourc91xx.zip) is not part of the FreeBSD source tree? I was contemplating buying this SCSI host adapter instead of an Adaptec 2940UW, but I fear that there will be problems in the future (for example late or no support for FBSD 4.0+). The license seems ok and the driver seems to be cam-ified. Blaz Zupan, [EMAIL PROTECTED], http://home.amis.net/blaz/ Medinet d.o.o., Linhartova 21, 2000 Maribor, Slovenia To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
grep -a (-stable)
hi, there! it is not possible to make short equivalent for old grep -a option (as in grep 2.3 -a is used for other purposes). it is possible to make a long option (--skip-binary) but long options are quite unusable. GREP_OPTIONS cannot help much (I want an equiv. for old 'grep -aRl pattern .') any thoughts? /fjoe To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: Initio SCSI driver
Thus spake Blaz Zupan ([EMAIL PROTECTED]): http://www.initio.com/drivers/BSD3sourc91xx.zip) is not part of the FreeBSD source tree? good question. A Friend of mine has already asked me if the initio-controllers are supported. It's the only stone in his way to FreeBSD (yet) 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: ATA driver as the default
Nick Hibma wrote: The other one is my laptop, and that one seems to be a lot faster and the system load is down (PIIX4 chipset). Except that it always gives me a timeout at boot. acd0: UJDA110/1.06 CDROM drive at ata1 as master acd0: read 2416KB/s (2416KB/s), 128KB buffer, PIO acd0: supported read types: CD-DA acd0: Audio: play, 16 volume levels acd0: Mechanism: ejectable tray acd0: Medium: no/blank disc inside, unlocked pccard: card inserted, slot 0 ata_command: timeout waiting for interrupt Same here (similar hardware): acd0: UJDA150/1.02 CDROM drive at ata1 as master acd0: read 4134KB/s (4134KB/s), 128KB buffer, PIO acd0: supported read types: CD-R, CD-RW, CD-DA acd0: Audio: play, 256 volume levels acd0: Mechanism: ejectable tray acd0: Medium: CD-ROM 120mm photo disc loaded, unlocked ata_command: timeout waiting for interrupt The command it's failing on is 0xa1 (ATA_C_ATAPI_IDENTIFY). Perhaps the driver should keep a list of misbehaving devices and not try to identify them? Alex To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: mount(2) broken?
Most probably this is exactly the problem I was describing to you a couple of days ago on IRC, phk. The solution is to boot single user, fsck / and reboot. After that things are back to normal. Even crashing the machine does not make this problem reoccur. Nah. This is about the third time I've seen this. I hadn't really gathered any useful information (and no data was lost) so I didn't bother to report it. I suspect it has something to do with soft-updates however. No softupdates in my case. Nick -- [EMAIL PROTECTED] [EMAIL PROTECTED] USB project http://www.etla.net/~n_hibma/ To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: sbc and ViBRA16X
Donn Miller wrote: Kenneth Culver wrote: Alright, I was under the impression that in order for the ViBRA16X soundcard (sound blaster) to work, these lines were needed in the kernel: device pcm0 device sbc0 Am I right, because it doesn't attach a driver to the soundcard. In my kernel config, I've got the order of the two switched around. Don't know if that makes a difference or not. Under -current, the kernel config file order is totally irrelevant. You can order it however you like. The only ordering is imposed on old drivers in the sys/i386/isa/isa_compat.* files. New-style drivers are supposed to set the 'sensitive' flag so they get probed first but I don't recall this being quite implemented properly. - Donn Cheers, -Peter -- Peter Wemm - [EMAIL PROTECTED]; [EMAIL PROTECTED]; [EMAIL PROTECTED] To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: Initio SCSI driver
Alexander Langer [EMAIL PROTECTED] writes: Thus spake Blaz Zupan ([EMAIL PROTECTED]): http://www.initio.com/drivers/BSD3sourc91xx.zip) is not part of the FreeBSD source tree? Maybe no one else knew about those drivers? good question. A Friend of mine has already asked me if the initio-controllers are supported. It's the only stone in his way to FreeBSD (yet) Get him to try the driver. tg To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: grep -a (-stable)
On Tue, 7 Dec 1999, Max Khon wrote: hi, there! it is not possible to make short equivalent for old grep -a option (as in grep 2.3 -a is used for other purposes). it is possible to make a long option (--skip-binary) but long options are quite unusable. GREP_OPTIONS cannot help much (I want an equiv. for old 'grep -aRl pattern .') any thoughts? Get textproc/freegrep out of the ports collection. :) Let me know if you see any bugs. Jamie To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: grep -a (-stable)
On Tue, 07 Dec 1999 18:42:56 +0600, Max Khon wrote: it is not possible to make short equivalent for old grep -a option (as in grep 2.3 -a is used for other purposes). Que? I've used grep -a since the update to grep 2.3 and haven't noticed any strange behaviour from the -a option. You wanna explain what's going on? Ciao, Sheldon. To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: Compiler looping
I can also vouch that there is nothing wrong with mysql-server-3.22.27. When my machine was compiling sql_yacc.cc the compiler was using 200 MB of memory (this is on a machine with 64 MB RAM!). The solution is to minimize other memory use (stop the X server and setiathome if you run it) and go to bed. In the morning it was all finished without problems. On Tue, 7 Dec 1999, Jeroen Ruigrok/Asmodai wrote: -On [19991206 21:57], Forrest Aldrich ([EMAIL PROTECTED]) wrote: Someone recently posted a note about a compiler error (loop?) when compiling mysql. I just did buildworld/installworld from today's cvsup and still get the same problem when it goes to: c++ -DMYSQL_SERVER -DDEFAULT_MYSQL_HOME="\"/usr/local\"" -DDATADIR="\"/var/db/mysql\"" -DSHAREDIR="\"/usr/local/share/mysql\""-DHAVE_CONFIG_H -I./../include -I./../regex-I. -I../include -I.. -I. -D_LARGEFILE_SOURCE -D_LARGEFILE64_SOURCE -D_FILE_OFFSET_BITS=64 -DDBUG_OFF -O -pipe -fno-implicit-templates -c sql_yacc.cc As what said in the other mail. This is not a `loop'. The C++ compilation takes ages before it is done compiling. Just let it finish, if you are worried about resources, you can limit those per instructions in the other mail. -- /===\ | Work: [EMAIL PROTECTED] | Home: [EMAIL PROTECTED] | \===/ "If it is true that our Universe has a zero net value for all conserved quantities, then it may simply be a fluctuation of the vacuum of some larger space in which our Universe is imbedded. In answer to the question of why it happened, I offer the modest proposal that our Universe is simply one of those things which happen from time to time." E. P. Tryon from "Nature" Vol.246 Dec.14, 1973 To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: grep -a (-stable)
hi, there! On Tue, 7 Dec 1999, Sheldon Hearn wrote: it is not possible to make short equivalent for old grep -a option (as in grep 2.3 -a is used for other purposes). Que? I've used grep -a since the update to grep 2.3 and haven't noticed any strange behaviour from the -a option. You wanna explain what's going on? -stable grep (2.0 + FreeBSD-specific features) uses -a to skip binary files at all. Very useful in such context as: vi `grep -aRl foo .` in -current both 'grep -al' and 'grep -l' print names of binary files and there is no way to tell grep to skip them /fjoe To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: ATA driver as the default
hi, there! On Tue, 7 Dec 1999, Alex wrote: The other one is my laptop, and that one seems to be a lot faster and the system load is down (PIIX4 chipset). Except that it always gives me a timeout at boot. acd0: UJDA110/1.06 CDROM drive at ata1 as master acd0: read 2416KB/s (2416KB/s), 128KB buffer, PIO acd0: supported read types: CD-DA acd0: Audio: play, 16 volume levels acd0: Mechanism: ejectable tray acd0: Medium: no/blank disc inside, unlocked pccard: card inserted, slot 0 ata_command: timeout waiting for interrupt Same here (similar hardware): acd0: UJDA150/1.02 CDROM drive at ata1 as master acd0: read 4134KB/s (4134KB/s), 128KB buffer, PIO acd0: supported read types: CD-R, CD-RW, CD-DA acd0: Audio: play, 256 volume levels acd0: Mechanism: ejectable tray acd0: Medium: CD-ROM 120mm photo disc loaded, unlocked ata_command: timeout waiting for interrupt The command it's failing on is 0xa1 (ATA_C_ATAPI_IDENTIFY). Perhaps the driver should keep a list of misbehaving devices and not try to identify them? Same here (kernel world built from sources cvsupped 29 Nov 1999): acd0: FX320M/m02 CDROM drive at ata1 as master acd0: read 5512KB/s (5512KB/s), 256KB buffer, PIO acd0: supported read types: CD-R, CD-RW, CD-DA, packet acd0: Audio: play, 255 volume levels acd0: Mechanism: ejectable tray acd0: Medium: CD-ROM 120mm data disc loaded, unlocked ata_command: timeout waiting for interrupt /fjoe To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: grep -a (-stable)
On Tue, 7 Dec 1999, Max Khon wrote: I know about this beast. It would be nice if our out-of-box grep had this option. Hah, it used to. I modeled it exactly on it (option-wise). BTW, if you do choose to use it, get it soon. I submitted a PR yesterday for my newest version. It is a faster, but most of the options are broken. Unfortunetly with exams and all, I will not be able to fix it until Christmas or so. Patches are more than welcome ;) Jamie To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: grep -a (-stable)
On Tue, 07 Dec 1999 08:56:53 EST, James Howard wrote: I submitted a PR yesterday for my newest version. It is a faster, but most of the options are broken. Unfortunetly with exams and all, I will not be able to fix it until Christmas or so. Then I suggest sending PR follow-up requesting that the update be postponed until _after_ 3.4-RELEASE. Ciao, Sheldon. To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: grep -a (-stable)
hi, there! On Tue, 7 Dec 1999, James Howard wrote: I know about this beast. It would be nice if our out-of-box grep had this option. Hah, it used to. -stable grep used -a to skip binary files. -current does not. /fjoe To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Cannot mount cd9660
Michael Chin-Yuan Wu wrote: Hi all, I have just made -current last night. I decided to use the new ata0 driver for the first time. All the devices detect fine. But this happens when I try to mount my acd0 and acd1 acd0 is a 40x sony cdrom and acd1 is a sony 6/4/4 cd-r keichii[root]:/usr/home/keichii# mount -t iso9660 /dev/acd0 /cdrom1 mount: exec mount_iso9660 not found in /sbin, /usr/sbin: No such file or directory keichii[root]:/usr/home/keichii# Same with mount_cd9660. I tried with acd1 and all other *cd* devices and still same error. Then I went to src/sbin and did make all install. Tested and still same error. No result went to each of the mount directories and did make all install Tested and still same error message. No result. Dos partitions and floppy drives mount fine What should I do? P.S. I did a patch for cd9660 and patch for reading Chinese filenames [patch is in attachment] =uname -a FreeBSD keichii.internal.org 4.0-CURRENT FreeBSD 4.0-CURRENT #0 8:09 CST 1999 [EMAIL PROTECTED]:/usr/current/src .ATA i386 ===dmesg= as attachment =kernel= as attachment patches for chinese filesystems== as attachment == Thank you, Michael Wu -- Copyright (c) 1992-1999 The FreeBSD Project. Copyright (c) 1982, 1986, 1989, 1991, 1993 The Regents of the University of California. All rights reserved. FreeBSD 4.0-CURRENT #0: Mon Dec 6 04:48:09 CST 1999 [EMAIL PROTECTED]:/usr/current/src/sys/compile/RHEA.ATA Timecounter "i8254" frequency 1193182 Hz Timecounter "TSC" frequency 598624067 Hz CPU: Pentium III/Xeon (598.62-MHz 686-class CPU) Origin = "GenuineIntel" Id = 0x673 Stepping = 3 Features=0x383f9ffFPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,MMX,FXSR,XMM real memory = 402653184 (393216K bytes) config di zp0 No such device: zp0 Invalid command or syntax. Type `?' for help. config di ze0 No such device: ze0 Invalid command or syntax. Type `?' for help. config di lnc0 No such device: lnc0 Invalid command or syntax. Type `?' for help. config di le0 No such device: le0 Invalid command or syntax. Type `?' for help. config di ie0 No such device: ie0 Invalid command or syntax. Type `?' for help. config di fe0 No such device: fe0 Invalid command or syntax. Type `?' for help. config di ex0 No such device: ex0 Invalid command or syntax. Type `?' for help. config di ep0 No such device: ep0 Invalid command or syntax. Type `?' for help. config di ed0 No such device: ed0 Invalid command or syntax. Type `?' for help. config di cs0 No such device: cs0 Invalid command or syntax. Type `?' for help. config di wt0 No such device: wt0 Invalid command or syntax. Type `?' for help. config di scd0 No such device: scd0 Invalid command or syntax. Type `?' for help. config di mcd0 No such device: mcd0 Invalid command or syntax. Type `?' for help. config di matcdc0 No such device: matcdc0 Invalid command or syntax. Type `?' for help. config di bt0 No such device: bt0 Invalid command or syntax. Type `?' for help. config di aha0 No such device: aha0 Invalid command or syntax. Type `?' for help. config di adv0 No such device: adv0 Invalid command or syntax. Type `?' for help. config q avail memory = 386830336 (377764K bytes) Preloaded elf kernel "kernel" at 0xc0327000. Preloaded userconfig_script "/boot/kernel.conf" at 0xc032709c. Pentium Pro MTRR support enabled md0: Malloc disk npx0: math processor on motherboard npx0: INT 16 interface pcib0: Intel 82443BX (440 BX) host to PCI bridge on motherboard pci0: PCI bus on pcib0 pcib1: Intel 82443BX (440 BX) PCI-PCI (AGP) bridge at device 1.0 on pci0 pci1: PCI bus on pcib1 vga-pci0: NVidia Riva TNT2 graphics accelerator irq 11 at device 0.0 on pci1 isab0: Intel 82371AB PCI to ISA bridge at device 7.0 on pci0 isa0: ISA bus on isab0 ata-pci0: Intel PIIX4 IDE controller at
ed driver, resources not released (was: Re: PCCARD eject freeze)
I've cleaned this up, worked it around, and managed to insert and
eject my ep card 5 times in a row on my desktop kludge environment.
It even appeared to be working. Don't know if this will work on a
Hm, The machine is not crashing at the moment when unplugging the
device. But plugging it back in gives me a 'No free configuration for
card Ethernet' ('Ethernet' being the quite splendid name of the card in
the CIS).
A quick browse reveals the following difference between ep and ed. It
doesn't have any effect however.
Let me know if I can test anything. I'd like to get that working, but
don't have the time to dig into this (utun driver is more important :)
Nick
Index: if_ed_pccard.c
===
RCS file: /home/ncvs/src/sys/dev/ed/if_ed_pccard.c,v
retrieving revision 1.6
diff -u -w -r1.6 if_ed_pccard.c
--- if_ed_pccard.c 1999/11/20 05:16:13 1.6
+++ if_ed_pccard.c 1999/12/03 22:04:06
@@ -91,6 +91,7 @@
ifp-if_flags = ~IFF_RUNNING;
if_down(ifp);
bus_teardown_intr(dev, sc-irq_res, sc-irq_handle);
+ ed_release_resources(dev);
sc-gone = 1;
device_printf(dev, "unload\n");
}
Nick
--
[EMAIL PROTECTED]
[EMAIL PROTECTED] USB project
http://www.etla.net/~n_hibma/
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message
Re: grep -a (-stable)
On Tue, Dec 07, 1999 at 06:42:56PM +0600, Max Khon wrote: it is not possible to make short equivalent for old grep -a option (as in grep 2.3 -a is used for other purposes). it is possible to make a long option (--skip-binary) but long options are quite unusable. GREP_OPTIONS cannot help much (I want an equiv. for old 'grep -aRl pattern .') any thoughts? Talk to the GNU Grep maintainers. I told them such an option was needed in GNU Grep and they said people *liked* the behavior of printing out a match in binary files. I was especially saying with "-l" this behavior us useless. Email them at Paul Eggert [EMAIL PROTECTED] and Alain Magloire [EMAIL PROTECTED]. See the archives of this list from 11/11/1999 - 11/12/1999 where this was discussed. Are you new to -CURRENT, or were you just not reading this list as you are suppose to? -- -- David([EMAIL PROTECTED]) To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: grep -a (-stable)
On Tue, Dec 07, 1999 at 03:36:55PM +0200, Sheldon Hearn wrote: Que? I've used grep -a since the update to grep 2.3 and haven't noticed any strange behavior from the -a option. You are in for a *BIG* surprise next time you hit a binary file. You really should read what "-a" is now about in the man page. Lets just say "-a" now does the opposite of what you think it does. -- -- David([EMAIL PROTECTED]) To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: grep -a (-stable)
On Tue, 07 Dec 1999 07:14:41 PST, "David O'Brien" wrote: You are in for a *BIG* surprise next time you hit a binary file. You really should read what "-a" is now about in the man page. Lets just say "-a" now does the opposite of what you think it does. Ah wunnerful. So this is why we always argue for days on end about the inclusion of new options in existing utilities. :-) Ciao, Sheldon. To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: Initio SCSI driver
On Tue, Dec 07, 1999 at 01:13:54PM +0100, Blaz Zupan wrote: Is there any particular reason why the Initio SCSI driver (available at http://www.initio.com/drivers/BSD3sourc91xx.zip) is not part of the FreeBSD source tree? Ask on [EMAIL PROTECTED] The people there would have a much better knowledge about it. I've seen this driver, and when I asked, I think Justin Gibbs said he didn't have time to review it and clean it up, or something. Well ask on the SCSI list. -- -- David([EMAIL PROTECTED]) To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: 3.3-stable - 4.0-current problem...
On Tue, Dec 07, 1999 at 11:41:43AM +0300, Hostas Red wrote: I've cvsup'ed my 3.3-stable source tree to 4.0-current source tree, and ... /usr/src/gnu/lib/libgcc/../../../contrib/gcc/frame.c Bad system call - core dumped mkdep: compile failed *** Error code 1 ..snip.. Anybody knows where can be a problem? On my another 4.0 box make world goes just fine... (*sigh, this comes up again*) Yes, you are both running -CURRENT when you have *NO* business doing so. You obviously didn't *_READ_* /usr/src/UPDATING. You obviously haven't been *_READING_* this mailing list. You obviously haven't *_READ_* the past 1-2 months of archives looking for "HEADS UP" messages. I would suggest staying at 3-STABLE. 4-CURRENT is for developers that have the time and ability to follow this list, and read the documentation provided. Please go read http://www.freebsd.org/handbook/cutting-edge.html. -- -- David([EMAIL PROTECTED]) To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: mount(2) broken?
Happens to me every boot. And I'm up to date with all binaries and kernel. I don't have softupdates on the root filesystem. On Mon, 6 Dec 1999, Mike Smith wrote: On Mon, 6 Dec 1999, Nick Hibma wrote: Most probably this is exactly the problem I was describing to you a couple of days ago on IRC, phk. The solution is to boot single user, fsck / and reboot. After that things are back to normal. Even crashing the machine does not make this problem reoccur. Nah. This is about the third time I've seen this. I hadn't really gathered any useful information (and no data was lost) so I didn't bother to report it. I suspect it has something to do with soft-updates however. aol Me too. /aol I just manifested this after a particularly nasty crash this evening (about 500 outstanding buffers), but softupdates weren't active. (It's too easy to kill the system with them enabled; there's a whole realm of exploration still untouched there.) -- \\ 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 To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: mount(2) broken?
On Tue, 7 Dec 1999, Luoqi Chen wrote: I've seen this exact same thing before too. In fact it was two rather annoying things, one being a single solitary last buffer that wouldn't sync and thus left the whole fs marked dirty, and then fsck would check it, see it was fine, but mount wouldn't recognize that it was clean. 'Course I saw this this morning too. Yes, with a new kernel, new devices, ata driver, and new world. 'Twas very odd. - alex I'd like to add something about the last buffer wouldn't sync. This occurs when a shutdown syscall is issued when the syncer process is asleep waiting for a buffer write to complete. The write will never complete, because the syncer won't be given a chance to run again, and the buffer will stay marked as busy and become the buffer that wouldn't sync. I haven't thought about a clean way of handling this situation, maybe some of you out there have better ideas... Ah. That *could* be happening to me, but this happens even with a quiescent system (I mean, several times with nothing happening). To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: ed driver, resources not released (was: Re: PCCARD eject freeze)
In message [EMAIL PROTECTED] Nick Hibma writes:
: Hm, The machine is not crashing at the moment when unplugging the
: device. But plugging it back in gives me a 'No free configuration for
: card Ethernet' ('Ethernet' being the quite splendid name of the card in
: the CIS).
:
: A quick browse reveals the following difference between ep and ed. It
: doesn't have any effect however.
:
: Let me know if I can test anything. I'd like to get that working, but
: don't have the time to dig into this (utun driver is more important :)
Quick question. If you kill and restart pccardd does the problem go
away?
Warner
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message
Re: Sound Blaster ViBRA16X and pcm driver
On Mon, 6 Dec 1999, Doug White wrote: unknown0: SupraExpress 56i at port 0x2f8-0x2ff irq 3 on isa0 unknown1: Creative ViBRA16X PnP at port 0x220-0x22f,0x300-0x301,0x388-0x38b ir q 9 drq 0,1 on isa0 unknown2: Game at port 0x201 on isa0 So what exactly do I need to do to get this working? Can you report the entire dmesg? I suspect this is only one of the logical devices. the nice thing about the old PnP code (in -STABLE and earlier) is that it showed the Vendor ID and Serials so that it would be trivial to check whether this is the issue or not. (the driver may simply not know thats its a card thats supported? incomplete ID list in the driver?) having not looked at newpcm for a few months and not having a -current box here currently to look at source, I couldn't say whther this is the case or not. the question I have is, is there an easy way for a "user" to probe for these ID's and get this kind of information? -Pat ___ Pat Lynch [EMAIL PROTECTED] [EMAIL PROTECTED] Systems Administrator Rush Networking ___ To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: Sound Blaster ViBRA16X and pcm driver
Just use pnpinfo to find out device vender id's and logical id's. It appears that the ViBRA16X is supported (with the correct logical id) in /usr/src/sys/dev/sound/isa/sbc.c but for some reason a driver is still not being attached for it. Any suggestions? = | Kenneth Culver | FreeBSD: The best OS around.| | Unix Systems Administrator | ICQ #: 24767726 | | and student at The | AIM: AgRSkaterq | | The University of Maryland, | Website: (Under Construction) | | College Park. | http://www.wam.umd.edu/~culverk/| = On Tue, 7 Dec 1999, Pat Lynch wrote: On Mon, 6 Dec 1999, Doug White wrote: unknown0: SupraExpress 56i at port 0x2f8-0x2ff irq 3 on isa0 unknown1: Creative ViBRA16X PnP at port 0x220-0x22f,0x300-0x301,0x388-0x38b ir q 9 drq 0,1 on isa0 unknown2: Game at port 0x201 on isa0 So what exactly do I need to do to get this working? Can you report the entire dmesg? I suspect this is only one of the logical devices. the nice thing about the old PnP code (in -STABLE and earlier) is that it showed the Vendor ID and Serials so that it would be trivial to check whether this is the issue or not. (the driver may simply not know thats its a card thats supported? incomplete ID list in the driver?) having not looked at newpcm for a few months and not having a -current box here currently to look at source, I couldn't say whther this is the case or not. the question I have is, is there an easy way for a "user" to probe for these ID's and get this kind of information? -Pat ___ Pat Lynch [EMAIL PROTECTED] [EMAIL PROTECTED] Systems Administrator Rush Networking ___ To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: ed driver, resources not released (was: Re: PCCARD eject freeze)
On Tue, Dec 07, 1999 at 09:22:31AM -0700, Warner Losh wrote:
In message [EMAIL PROTECTED] Nick Hibma writes:
: Hm, The machine is not crashing at the moment when unplugging the
: device. But plugging it back in gives me a 'No free configuration for
: card Ethernet' ('Ethernet' being the quite splendid name of the card in
: the CIS).
:
: A quick browse reveals the following difference between ep and ed. It
: doesn't have any effect however.
:
: Let me know if I can test anything. I'd like to get that working, but
: don't have the time to dig into this (utun driver is more important :)
Quick question. If you kill and restart pccardd does the problem go
away?
It doesn't for me (I have the same problem). This last commit was
unfortunate, as it didn't really help the eject situation and now
I can't use my sio card at all. :-(
--
Christopher Masto Senior Network Monkey NetMonger Communications
[EMAIL PROTECTED][EMAIL PROTECTED]http://www.netmonger.net
Free yourself, free your machine, free the daemon -- http://www.freebsd.org/
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message
Re: Intel 810?
Mark Newton writes: | On Mon, Dec 06, 1999 at 07:52:20PM -0500, Garrett Wollman wrote: | | On Mon, 6 Dec 1999 19:41:15 -0500, "Douglas Kuntz" [EMAIL PROTECTED] said: | |As others have stated, Socket370 boards arent all 810/810c...my 4.0-Current | | The important issue to me is: will FreeBSD work on an 810 motherboard? | The reason I care is because I need the form-factor (a 1U-high | server); if I am to use some alternate motherboard, I'll need to be | certain in advance that it will fit in a MicroATX opening. | | For what it's worth, we've been buying 1U servers pre-configured | (and pre-installed with FreeBSD) from Telenet Systems, http://www.tesys.com. | US$1199 for the entry-level model. To add to the 1U 810 thread. - 810 does not support ECC memory from what I've read. - Several cases are available that use ATX or PICMG SBC boards. There are some others but not as interesting or standard. - ATX boards that can fit in a 1U case need a socket and not a slot. I think it is a risk to depend on generic ATX motherboard venders to make them in the future since the ATX spec does not meet the needs of 1U. 2U is fine, no issues. Boomrack has lots of solutions. Also you need to get everything on board since you only have one precious expansion slot (a right angle adapter). - NLX has same problem as ATX (besides I have a grip against NLX since you can't use off the shelf AGP cards in them ... there is a special spec for AGP/NLX) Try to buy one I dare you I eventually dug one up at 2X suggested retail). - PICMG SBC guys need to make thin boards for multi-slot machines so there are lots of Socket boards out their with "real" chipset (ie BX that support ECC memory). Also you can get onbard SCSI, VGA, Ethernet, USB etc. SBC's usually have watchdogs, DiskOnChip (in which you can easily stick a netboot rom) etc. - Lots of 1U cases a little "lame", meaning the SBC cases don't have mounts for all of the SBC boards options. You can only get so many things out a single slot. Mitac is the only company I've seen so far that has more then enough knock outs in their case (www.mitacinds.com). Also the Mitac case can fit a - CDROM - 3.5" hard drive - 3.5" floppy - 2.5" laptop drive All at the same time. I haven't found any other cases that can do that. Most require a laptop drive if you use a CDROM. Now most FreeBSD machines can get away with not having a CDROM so it isn't critical. - Expansion is usually one PCI/ISA slot. We use a D-Link 4 port ethernet card. This card is short enough to fit in the slot since it is not quite a full lenght slot with a CDROM. - Mitac does not use the Intel ethernet chip :-( We have a Mitac case in house and it is very nice. BTW the IBM 1U system is OEM'ed. There is also another company doing dual PII in 1U. Doug A. To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
AWE64 problems
Hi! I am still having problems getting my AWE64 soundcard to work with the newpcm driver (the "old" pcm driver worked fine). I have updated the world last week and am using the kernel as of today. I'm using the "pcm0" and "sbc0" devices in my kernel options. My card is recognized correctly, but not attached to the pcm0 driver (it is listed as unknown0:), so all audio devices don't work. Any ideas what I am doing wrong? Are there more people having problems with their AWE64? Any help is appreciated! I have included my dmesg and pnpinfo outputs: Copyright (c) 1992-1999 The FreeBSD Project. Copyright (c) 1982, 1986, 1989, 1991, 1993 The Regents of the University of California. All rights reserved. FreeBSD 4.0-CURRENT #0: Tue Dec 7 18:26:28 CET 1999 [EMAIL PROTECTED]:/usr/src/sys/compile/STARFIRE Timecounter "i8254" frequency 1193182 Hz CPU: Pentium II/Xeon/Celeron (412.05-MHz 686-class CPU) Origin = "GenuineIntel" Id = 0x652 Stepping = 2 Features=0x183fbffFPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,MMX,FXSR real memory = 268423168 (262132K bytes) avail memory = 256204800 (250200K bytes) Programming 24 pins in IOAPIC #0 FreeBSD/SMP: Multiprocessor motherboard cpu0 (BSP): apic id: 1, version: 0x00040011, at 0xfee0 cpu1 (AP): apic id: 0, version: 0x00040011, at 0xfee0 io0 (APIC): apic id: 2, version: 0x00170011, at 0xfec0 Preloaded elf kernel "kernel" at 0xc03e6000. Preloaded userconfig_script "/kernel.config" at 0xc03e609c. Preloaded splash_image_data "/boot/starfire.bmp" at 0xc03e60e8. Preloaded elf module "splash_bmp.ko" at 0xc03e6138. Pentium Pro MTRR support enabled splash_bmp: No appropriate video mode found module_register_init: MOD_LOAD (splash_bmp, c03e1654, 0) error 19 npx0: math processor on motherboard npx0: INT 16 interface pcib0: Intel 82443BX (440 BX) host to PCI bridge on motherboard pci0: PCI bus on pcib0 pcib1: Intel 82443BX (440 BX) PCI-PCI (AGP) bridge at device 1.0 on pci0 pci1: PCI bus on pcib1 vga-pci0: Matrox model 0521 graphics accelerator irq 16 at device 0.0 on pci1 isab0: Intel 82371AB PCI to ISA bridge at device 4.0 on pci0 isa0: ISA bus on isab0 ata-pci0: Intel PIIX4 IDE controller at device 4.1 on pci0 ata-pci0: Busmastering DMA supported ata0 at 0x01f0 irq 14 on ata-pci0 ata1 at 0x0170 irq 15 on ata-pci0 pci0: UHCI USB controller (vendor=0x8086, dev=0x7112) at 4.2 irq 19 Timecounter "PIIX" frequency 3579545 Hz chip1: Intel 82371AB Power management controller at device 4.3 on pci0 ahc0: Adaptec aic7890/91 Ultra2 SCSI adapter irq 19 at device 6.0 on pci0 ahc0: aic7890/91 Wide Channel A, SCSI Id=7, 16/255 SCBs pci0: unknown card (vendor=0x121a, dev=0x0002) at 9.0 ed0: NE2000 PCI Ethernet (Compex) irq 18 at device 10.0 on pci0 ed0: address 00:80:48:c4:b7:99, type NE2000 (16 bit) devclass_alloc_unit: npx0 already exists, using next available unit number isa0: unexpected tag 14 fdc0: NEC 72065B or clone at port 0x3f0-0x3f7 irq 6 drq 2 on isa0 fdc0: FIFO enabled, 8 bytes threshold fd0: 1440-KB 3.5" drive on fdc0 drive 0 atkbdc0: keyboard controller (i8042) at port 0x60-0x6f on isa0 atkbd0: AT Keyboard irq 1 on atkbdc0 psm0: PS/2 Mouse irq 12 on atkbdc0 psm0: model Generic PS/2 mouse, device ID 0 vga0: Generic ISA VGA at port 0x3c0-0x3df iomem 0xa-0xb on isa0 sc0: System console on isa0 sc0: VGA 16 virtual consoles, flags=0x200 sio0 at port 0x3f8-0x3ff irq 4 flags 0x10 on isa0 sio0: type 16550A sio1 at port 0x2f8-0x2ff irq 3 on isa0 sio1: type 16550A joy0 at port 0x201 on isa0 ppc0 at port 0x378-0x37f irq 7 on isa0 ppc0: SMC-like chipset (ECP/EPP/PS2/NIBBLE) in COMPATIBLE mode ppc0: FIFO with 16/16/9 bytes threshold plip0: PLIP network interface on ppbus 0 lpt0: generic printer on ppbus 0 lpt0: Interrupt-driven port ppi0: generic parallel i/o on ppbus 0 pps0: Pulse per second Timing Interface on ppbus 0 unknown0: Creative SB AWE64 at port 0x220-0x22f,0x330-0x331,0x388-0x38b irq 5 drq 1,5 on isa0 joy1: Generic PnP Joystick at port 0x208-0x20f on isa0 unknown1: WaveTable at port 0x620-0x623 on isa0 APIC_IO: Testing 8254 interrupt delivery APIC_IO: routing 8254 via pin 2 IP packet filtering initialized, divert enabled, rule-based forwarding disabled, default to accept, logging limited to 100 packets/entry by default IP Filter: initialized. Default = pass all, Logging = enabled IP Filter: v3.3.3 SMP: AP CPU #1 Launched! ad0: IBM-DPTA-372730/P78OA30A ATA-4 disk at ata0 as master ad0: 26105MB (53464320 sectors), 53040 cyls, 16 heads, 63 S/T, 512 B/S ad0: 16 secs/int, 32 depth queue, UDMA33 ad1: IBM-DTTA-351010/T56OA73A ATA-4 disk at ata1 as master ad1: 9671MB (19807200 sectors), 19650 cyls, 16 heads, 63 S/T, 512 B/S ad1: 16 secs/int, 32 depth queue, UDMA33 ahc0:A:2: refuses WIDE negotiation. Using 8bit transfers ahc0:A:2: refuses WIDE negotiation. Using 8bit transfers ahc0:A:2: refuses WIDE negotiation. Using 8bit transfers ahc0:A:2: refuses WIDE negotiation. Using 8bit transfers ahc0:A:2: refuses
Re: mount(2) broken?
On Mon, 6 Dec 1999, Mike Smith wrote:
On Mon, 6 Dec 1999, Nick Hibma wrote:
Most probably this is exactly the problem I was describing to you a
couple of days ago on IRC, phk.
The solution is to boot single user, fsck / and reboot. After that
things are back to normal. Even crashing the machine does not make this
problem reoccur.
Nah. This is about the third time I've seen this. I hadn't really
gathered any useful information (and no data was lost) so I didn't bother
to report it. I suspect it has something to do with soft-updates however.
aol
Me too.
/aol
"mount -f /" on a dirty root file system causes the clean flag to stay off
forever. (I forgot to change the unclean flag for mount -u.)
diff -c2 ffs_vfsops.c~ ffs_vfsops.c
*** ffs_vfsops.c~ Thu Nov 25 23:27:44 1999
--- ffs_vfsops.cSun Dec 5 05:12:51 1999
***
*** 218,222
--- 220,226
}
+ fs-fs_flags = ~FS_UNCLEAN;
if (fs-fs_clean == 0) {
+ fs-fs_flags |= FS_UNCLEAN;
if (mp-mnt_flag MNT_FORCE) {
printf(
Bruce
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message
[PATCHES] Two fixes for lpd/lpc for review and test
Well, here's my third attempt to get someone to at least acknowledge some minor patches for lpd. The patches are also covered in PR's, as noted in the previous attempts. My theory is that my previous attempts had a subject which made it sound like I was looking for someone to *make* some fixes, as opposed to the fact that I already have fixes for these known bugs and I thought someone with commit privs might want to apply them to the official distribution. In my next installment, I'm going to try a subject of "Make Money Fast via Sex With Green Card Lawyers" Although with this crowd I'd probably have better luck with something like: "I have vmware running native on FreeBSD 3.2-release"... While I'm at it, I'd like to note another patch for lpd which looked interesting. This one might be a bit too risky to get into 3.4-release, but it would be nice to at least add it to current. To quote from another message: - - - Date: Mon, 22 Nov 1999 20:08:13 +0100 From: Andre Albsmeier [EMAIL PROTECTED] Subject: Enhancement for lpr (maybe for STABLE-3.4) A while ago I sent a PR containing an enhancement for lpr -r for the case that the file to be printed is on the same filesystem as lpd's spooling directory. The PR is bin/11997 and can be found at: http://www.freebsd.org/cgi/query-pr.cgi?pr=11997 Maybe someone can look at it, review it and eventually commit it to -STABLE (and current, of course). The patch now runs nearly 2 years without problems and saves quite a lot of time when printing large temporay files. - - - Note that the above patch not only saves time, but reduces the amount of disk space needed in a print-spooling partition. That may not seem like much of an issue when you're printing 10-Kbyte files, but when you're throwing around 200-Meg files (for color plotters, for instance), then it can be very nice. The text from my previous attempts follow. - - - - - - - - - - - - - - - - - - - - - - - - - At 5:04 PM -0500 11/20/99, Garance A Drosihn wrote: Back when we were closing in on the release date for 3.3, I sent the following message. As we now close in on the release date for 3.4, I thought I'd send it again, seeing that both of the problem reports are still marked "open", and neither of the two patches have been applied yet. (not even to current) These are both pretty tiny minor lovable cuddly changes... Any chance of getting them in for 3.4? Note that problem report bin/12912 probably depends on what umask is set when lpd starts up. The pr says "the problem doesn't seem to be reproducible", but reproducing the problem may depend on someone making a change elsewhere. Given that lpd uses the actual access-bit settings to govern it's behavior, then it should make sure the exactly-correct bit settings are set up when it creates the file. Also note that the fix for bin/9362, sent in as bin/13549, is also confirmed in bin/14975. Date: Mon, 6 Sep 1999 18:14:55 -0500 To: [EMAIL PROTECTED] From: Garance A Drosihn [EMAIL PROTECTED] Subject: Two fixes for lpd/lpc (printing) Cc: [EMAIL PROTECTED] I noticed problem-report bin/9362, which reported that the 'lpc start' command no longer works. (it claims to start the queue, but it doesn't actually start it). I came up with a two or three line fix for that bug, and sent it in as problem-report bin/13549. This patch should work on both freebsd-current and freebsd-stable. I also noticed problem report bin/12912. This PR includes a patch to make sure that if a lockfile does not already exist, then it will be created such that the queue is both "enabled" and "started". I have not tried this exact patch yet, but here at RPI we've had a similar patch to lpd for a long time. We add printer queues to a master printcap file, which is then copied to a few hundred workstations. We really don't want to have to run around all those workstations to 'enable' and 'start' a queue that we have just added. Perhaps we have a different 'umask' setting when lpd starts up than most freebsd sites do... Could some other people try these simple patches, and see how well they work? I am hoping these could make it into the next official release, although I realize that time is rapidly running out for that! :-) --- Garance Alistair Drosehn = [EMAIL PROTECTED] Senior Systems Programmer or [EMAIL PROTECTED] Rensselaer Polytechnic Institute --- Garance Alistair Drosehn = [EMAIL PROTECTED] Senior Systems Programmer or [EMAIL PROTECTED] Rensselaer Polytechnic Institute To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: Initio SCSI driver
Blaz Zupan wrote... Is there any particular reason why the Initio SCSI driver (available at http://www.initio.com/drivers/BSD3sourc91xx.zip) is not part of the FreeBSD source tree? I was contemplating buying this SCSI host adapter instead of an Adaptec 2940UW, but I fear that there will be problems in the future (for example late or no support for FBSD 4.0+). The license seems ok and the driver seems to be cam-ified. As David O'Brien mentioned, it's best to ask on the SCSI list about SCSI stuff. In any case, the license on the driver for their Ultra-Wide controllers has not always been a BSD-style license. It used to have one file with a BSD-style license, one file with a proprietary license, and one file with no license. Thomas Graichen [EMAIL PROTECTED] has been working on getting both of Initio's drivers into FreeBSD. This may explain why Initio has fixed the copyright on their Ultra-Wide driver. (Their Ultra2 driver never had a copyright problem.) You may want to contact Thomas and see how things are going. Ken -- Kenneth Merry [EMAIL PROTECTED] To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
is there any heap functions in the kernel ?
Hi, i was wondering if there is any place in the kernel with functions to implement a "heap" data structure. I would expect so, as typically this structure is used wherever we need to do some kind of scheduling, but i am not sure on where to look... Ideas ? (for those who wonder why I ask -- i redesigning dummynet so it handles more efficiently large numbers of pipes, and while i have rewritten the heap management code, i was wondering if i am not duplicating existing funcionality.) cheers luigi ---+- Luigi RIZZO, [EMAIL PROTECTED] . Dip. di Ing. dell'Informazione http://www.iet.unipi.it/~luigi/ . Universita` di Pisa TEL/FAX: +39-050-568.533/522 . via Diotisalvi 2, 56126 PISA (Italy) http://www.iet.unipi.it/~luigi/ngc99/ First International Workshop on Networked Group Communication ---+- To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: mount(2) broken?
I'd like to add something about the last buffer wouldn't sync. This occurs when a shutdown syscall is issued when the syncer process is asleep waiting for a buffer write to complete. The write will never complete, because the syncer won't be given a chance to run again, and the buffer will stay marked as busy and become the buffer that wouldn't sync. I haven't thought about a clean way of handling this situation, maybe some of you out there have better ideas... I always thought it would make sense to have the syncer perform the shutdown and cleanup since it had code to write buffers with anyway... This sounds like a good idea, and should be easy to implement. I'll work on it tonight. -- Poul-Henning Kamp FreeBSD coreteam member [EMAIL PROTECTED] "Real hackers run -current on their laptop." FreeBSD -- It will take a long time before progress goes too far! -lq To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: AWE64 problems
I hate me too messages, but I'm having problems too. Exact same symptoms. I looked at sbc.c and it has the correct logical id, I spent some time looking at this last night, but was stymied by my lack of understanding of how the pnp system works. I even tried it with PNPBIOS defined, but that didn't help any either. I have attached dmesg output and pnpinfo output. -Charlie -- Charles Anderson[EMAIL PROTECTED] No quote, no nothin' Copyright (c) 1992-1999 The FreeBSD Project. Copyright (c) 1982, 1986, 1989, 1991, 1993 The Regents of the University of California. All rights reserved. FreeBSD 4.0-CURRENT #0: Tue Dec 7 12:19:46 EST 1999 [EMAIL PROTECTED]:/usr/src/sys/compile/MIDGARD Timecounter "i8254" frequency 1193182 Hz Timecounter "TSC" frequency 451024486 Hz CPU: Pentium II/Celeron (451.02-MHz 686-class CPU) Origin = "GenuineIntel" Id = 0x660 Stepping = 0 Features=0x183f9ffFPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,MMX,FXSR real memory = 134217728 (131072K bytes) avail memory = 126877696 (123904K bytes) Preloaded elf kernel "kernel" at 0xc030c000. Preloaded elf module "splash_bmp.ko" at 0xc030c09c. Preloaded elf module "vesa.ko" at 0xc030c140. Preloaded splash_image_data "/root/daemon_640.bmp" at 0xc030c1dc. VESA: v1.2, 4096k memory, flags:0x0, mode table:0xc00c5e02 (c0005e02) VESA: Alliance Semiconductor PMAT3D Pentium Pro MTRR support enabled npx0: math processor on motherboard npx0: INT 16 interface pcib0: Intel 82443BX (440 BX) host to PCI bridge on motherboard pci0: PCI bus on pcib0 pcib1: Intel 82443BX (440 BX) PCI-PCI (AGP) bridge at device 1.0 on pci0 pci1: PCI bus on pcib1 isab0: Intel 82371AB PCI to ISA bridge at device 7.0 on pci0 isa0: ISA bus on isab0 chip1: Intel PIIX4 IDE controller at device 7.1 on pci0 pci0: UHCI USB controller (vendor=0x8086, dev=0x7112) at 7.2 irq 15 intpm0: Intel 82371AB Power management controller at device 7.3 on pci0 intpm0: I/O mapped 5000 intpm0: intr IRQ 9 enabled revision 0 smbus0: System Management Bus on intsmb0 smb0: SMBus general purpose I/O on smbus0 intpm0: PM I/O mapped 4000 fxp0: Intel EtherExpress Pro 10/100B Ethernet irq 14 at device 11.0 on pci0 fxp0: Ethernet address 00:a0:c9:78:ae:3a vga-pci0: Alliance model 643d VGA-compatible display device at device 13.0 on pci0 ncr0: ncr 53c875 fast20 wide scsi irq 11 at device 15.0 on pci0 ncr1: ncr 53c825 fast10 wide scsi irq 15 at device 17.0 on pci0 fdc0: NEC 72065B or clone at port 0x3f0-0x3f7 irq 6 drq 2 on isa0 fdc0: FIFO enabled, 8 bytes threshold fd0: 1440-KB 3.5" drive on fdc0 drive 0 sio0 at port 0x3f8-0x3ff irq 4 flags 0x10 on isa0 sio0: type 16550A sio1 at port 0x2f8-0x2ff irq 3 on isa0 sio1: type 16550A atkbdc0: keyboard controller (i8042) at port 0x60-0x6f on isa0 atkbd0: AT Keyboard irq 1 on atkbdc0 psm0: PS/2 Mouse irq 12 on atkbdc0 psm0: model MouseMan+, device ID 0 vga0: Generic ISA VGA at port 0x3b0-0x3df iomem 0xa-0xb on isa0 sc0: System console on isa0 sc0: VGA 16 virtual consoles, flags=0x200 joy0 at port 0x201 on isa0 ppc0 at port 0x378-0x37f irq 7 on isa0 ppc0: Generic chipset (NIBBLE-only) in COMPATIBLE mode plip0: PLIP network interface on ppbus 0 lpt0: generic printer on ppbus 0 lpt0: Interrupt-driven port ppi0: generic parallel i/o on ppbus 0 unknown0: Creative SB16 PnP/SB32 at port 0x220-0x22f,0x330-0x331,0x388-0x38b irq 5 drq 1,5 on isa0 unknown1: IDE at port 0x168-0x16f,0x36e-0x36f irq 10 on isa0 unknown2: WaveTable at port 0x620-0x623 on isa0 unknown: Game can't assign resources (sa0:ncr0:0:4:0): found quirk entry 2 sa0 at ncr0 bus 0 target 4 lun 0 sa0: ARCHIVE VIPER 2525 25462 -007 Removable Sequential Access SCSI-CCS device sa0: 3.300MB/s transfers Mounting root from ufs:/dev/da0s1a cd0 at ncr0 bus 0 target 5 lun 0 cd0: PIONEER CD-ROM DR-U06S 1.05 Removable CD-ROM SCSI-2 device cd0: 19.230MB/s transfers (19.230MHz, offset 16) cd0: cd present [306474 x 2048 byte records] da3 at ncr0 bus 0 target 15 lun 0 da3: IBM DDRS-34560D DC1B Fixed Direct Access SCSI-2 device da3: 40.000MB/s transfers (20.000MHz, offset 15, 16bit), Tagged Queueing Enabled da3: 4357MB (8925000 512 byte sectors: 255H 63S/T 555C) da2 at ncr0 bus 0 target 10 lun 0 da2: IBM OEM DFHSS2W 4B4B Fixed Direct Access SCSI-2 device da2: 20.000MB/s transfers (10.000MHz, offset 15, 16bit) da2: 2150MB (4404489 512 byte sectors: 255H 63S/T 274C) da1 at ncr0 bus 0 target 9 lun 0 da1: IBM OEM DFHSS2W 4B4B Fixed Direct Access SCSI-2 device da1: 20.000MB/s transfers (10.000MHz, offset 15, 16bit) da1: 2150MB (4404489 512 byte sectors: 255H 63S/T 274C) da0 at ncr0 bus 0 target 8 lun 0 da0: IBM OEM DFHSS2W 4B4B Fixed Direct Access SCSI-2 device da0: 20.000MB/s transfers (10.000MHz, offset 15, 16bit) da0: 2150MB (4404489 512 byte sectors: 255H 63S/T 274C) (cd1:ncr0:0:6:0): got CAM status 0x4c (cd1:ncr0:0:6:0): fatal error, failed to attach to device (cd1:ncr0:0:6:0): lost device (cd1:ncr0:0:6:0): removing device entry Copyright (c) 1992-1999 The
Re: ATA driver as the default
David O'Brien schrieb: Since the ATA driver is destined to be the default in 4.0-R, and we hare hitting the feature freeze date; can we make the switch now? I think it is very important to get ATA into more hands to see where it breaks. It certainly has problems on my Vaio 505 laptop; and I wonder where else it will have problems. Better to find them now than right before release. I occasionaly tested the new ATA driver on my laptop but decided to go back to the old wd driver: There seems to be a problem if I enable DMA for the hard disk. With DMA turned on the disk sometimes hung for a few seconds, then got resetted and worked again. No data corruption occured. This happened under FreeBSD and Windows. I therefor disabled DMA transfer for the disk. The CD-ROM works just happily with DMA turned on though. Disk and CD-ROM are connected to the same IDE controller (Intel standard). I just want a flag to selectively disable DMA transfer for certain files, just like I could for the old wd driver. I just re-enabled the ATA driver again after reading the change log of better error handling and automatic falldown DMA-PIO under specific circumstances. But a few days later, while making world (with the ata driver), the system crashed quite heavily. The file system was totally screwed up afterwards (I found my /usr/local after some heavy searching: It magically moved to /usr/obj/usr/src/tmp/usr/share/zoneinfo (!) and got tons of fsck messages). The file system had softupdates enabled. I don't know the last kernel messages before the crash (was running X at that time). Daniel To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: ATA driver as the default
D. Rock writes: | I just re-enabled the ATA driver again after reading the change log | of better error handling and automatic falldown DMA-PIO under specific | circumstances. | But a few days later, while making world (with the ata driver), the | system | crashed quite heavily. The file system was totally screwed up afterwards | (I found my /usr/local after some heavy searching: It magically | moved to /usr/obj/usr/src/tmp/usr/share/zoneinfo (!) and got tons of | fsck | messages). The file system had softupdates enabled. I don't know the | last kernel messages before the crash (was running X at that time). You might want to look at ata-disk.c and the timeout value around line 438: /* start timeout for this transfer */ if (panicstr) request-timeout_handle.callout = NULL; else request-timeout_handle = timeout((timeout_t*)ad_timeout, request, 5*hz); Originally it was 3s and recently increased to 5s. Personally I switched it to 30s after it trashed my filesystem when it was 3s. The issue was that 3s, is that it is to short to wait for my laptop's drive to spin back up. Sometimes I would get a corrupted read sometimes on a write it would trash things. I noticed in the old wd driver that it tried 10s first then a couple 3s timeouts. After making this change my system has been rock solid when the drive spins down. Note I haven't tried to tune this value since trashing a 14G filesystem is pain full. Doug A. To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: [PATCHES] Two fixes for lpd/lpc for review and test
In message v04210102b472f8589876@[128.113.24.47], Garance A Drosihn writes: I've been using the patch from PR 13549 on 4 -stable stable machines for about 3 weeks with no ill effects -- and it fixes the problem. In my next installment, I'm going to try a subject of "Make Money Fast via Sex With Green Card Lawyers" You can get screwed by a lawyer without sex. Regards, Phone: (250)387-8437 Cy Schubert Fax: (250)387-5766 Sun/DEC Team, UNIX GroupInternet: [EMAIL PROTECTED] ITSD [EMAIL PROTECTED] Province of BC "e**(i*pi)+1=0" To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: [PATCHES] Two fixes for lpd/lpc for review and test
I've been reviewing this patch with someone and I think the last version is ready to commit. I'll take a look at my tree to make sure. Warner To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: 3.3-stable - 4.0-current problem...
David O'Brien wrote: On Tue, Dec 07, 1999 at 11:41:43AM +0300, Hostas Red wrote: I've cvsup'ed my 3.3-stable source tree to 4.0-current source tree, and ... /usr/src/gnu/lib/libgcc/../../../contrib/gcc/frame.c Bad system call - core dumped mkdep: compile failed *** Error code 1 ..snip.. Anybody knows where can be a problem? On my another 4.0 box make world goes just fine... (*sigh, this comes up again*) Yes, you are both running -CURRENT when you have *NO* business doing so. All they need is a simple pointer, why not be a bit nicer? :) Please try this tutorial when you move from -stable to -current www.external.org/freebsd/current.html To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: AWE64 problems
On Tue, Dec 07, 1999 at 06:43:55PM +0100, Thomas Schuerger wrote: Hi! I am still having problems getting my AWE64 soundcard to work with the newpcm driver (the "old" pcm driver worked fine). Any ideas what I am doing wrong? Are there more people having problems with their AWE64? Any help is appreciated! I had the same problem with my AWE64. An older kernel @(#)FreeBSD 4.0-CURRENT #1: Sun Nov 28 18:54:55 CET 1999 was working correct with "device pcm" and "device sbc" I dived into the source and put some printf's. I noticed that the sbc_attach never got called. This is my patch. Now it is working again, but I don't have a clue if I did it the right way. --- sbc.c.orig Mon Dec 6 19:26:31 1999 +++ sbc.c Tue Dec 7 22:15:25 1999 @@ -110,7 +110,7 @@ if (error) return error; else - return -100; + return -1; } static int Frank -- ~/.signature not found: wellknown error 42 To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: Samba Performance
Try to look into the ports/samba/patches for the patch-ah file (which provided to resolve such misbehaviour). If that file doesn't exist than either try to cvsup your ports, or manually add following patch and recompile/reinstall samba: This patch is only relevant for Samba 2.0.5a. If you look at the Changelog for 2.0.6 you'll see that MSG_WAITALL was removed specifically because of the performance problems under FreeBSD it caused. -- Greg Lewis [EMAIL PROTECTED] Computing Officer +61 8 8303 5083 Teletraffic Research Centre To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: AWE64 problems
I am still having problems getting my AWE64 soundcard to work with the newpcm driver (the "old" pcm driver worked fine). Any ideas what I am doing wrong? Are there more people having problems with their AWE64? I had the same problem with my AWE64. An older kernel @(#)FreeBSD 4.0-CURRENT #1: Sun Nov 28 18:54:55 CET 1999 was working correct with "device pcm" and "device sbc" I dived into the source and put some printf's. I noticed that the sbc_attach never got called. This is my patch. Now it is working again, but I don't have a clue if I did it the right way. --- sbc.c.origMon Dec 6 19:26:31 1999 +++ sbc.c Tue Dec 7 22:15:25 1999 @@ -110,7 +110,7 @@ if (error) return error; else - return -100; + return -1; } static int Works fine for me. Thanks!!! Ciao, Thomas Schürger. http://www.menden.augustin.de To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: Samba Performance
I have FreeBSD 3.3-RELEASE on a computer that is having Samba performance problems. Using an Intel EtherExpress Pro100 (100MBit) it takes 10 times as long to copy the same large file from a Win98 computer to the FreeBSD computer than it takes to copy from a Win98 to Win98 computer. On looking at the Samba man page I see that FeeBSD 3.3-RELEASE is using Samba 2.0.5a. This Samba was installed as a precompiled package from the 3.3-RELEASE CD-ROM. Could someone please advise me if the Samba package on the CD-ROM contains this problem. If so I assume it is best to download Samba 2.0.6. Thanks in advance Craig Wilson National software Pty Ltd Greg Lewis wrote: Try to look into the ports/samba/patches for the patch-ah file (which provided to resolve such misbehaviour). If that file doesn't exist than either try to cvsup your ports, or manually add following patch and recompile/reinstall samba: This patch is only relevant for Samba 2.0.5a. If you look at the Changelog for 2.0.6 you'll see that MSG_WAITALL was removed specifically because of the performance problems under FreeBSD it caused. To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
NO! Re: [PATCHES] Two fixes for lpd/lpc for review and test
On Tue, 7 Dec 1999, Warner Losh wrote:
I've been reviewing this patch with someone and I think the last
version is ready to commit. I'll take a look at my tree to make
sure.
please do not, the patch in PR 11997 introduces a major security flaw.
someone can hardlink to any file and clobber it with a file owned by
them:
try this:
as root:
# cd /var/tmp ; touch rootfile ; chown root:wheel rootfile ; chmod 600 rootfile
as a user:
% cd /var/tmp ; echo foo foo
% lpr -r foo
sleeping
in another session as user:
% rm foo ; ln rootfile foo
wait a second...
# ls -l rootfile
-rw-rw 3 user daemon5 Dec 7 13:38 rootfile
# cat rootfile
foo
#
ouch!
-Alfred
use this patch to make the race condition apparrent:
Index: usr.sbin/lpr/lpr/lpr.c
===
RCS file: /home/ncvs/src/usr.sbin/lpr/lpr/lpr.c,v
retrieving revision 1.27.2.2
diff -u -u -r1.27.2.2 lpr.c
--- lpr.c 1999/08/29 15:43:29 1.27.2.2
+++ lpr.c 1999/12/08 01:47:47
@@ -370,6 +370,27 @@
}
if (sflag)
printf("%s: %s: not linked, copying instead\n", name, arg);
+ if( f ) { /* means that the file should be deleted */
+ printf("sleeping\n");
+ sleep(5);
+ printf("done.\n");
+ seteuid(euid); /* needed for rename() to succeed */
+ if( ! rename( arg, dfname ) ) {
+ register int i;
+ chmod( dfname, S_IRUSR | S_IWUSR | S_IRGRP |
+S_IWGRP );
+ chown( dfname, userid, getgrnam("daemon")-gr_gid
+);
+ seteuid(uid);
+ if (format == 'p')
+ card('T', title ? title : arg);
+ for (i = 0; i ncopies; i++)
+ card(format, dfname[inchar-2]);
+ card('U', dfname[inchar-2]);
+ card('N', arg);
+ nact++;
+ continue;
+ }
+ seteuid(uid);
+ }
if ((i = open(arg, O_RDONLY)) 0) {
printf("%s: cannot open %s\n", name, arg);
} else {
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message
Re: 3.3-stable - 4.0-current problem...
On Tue, 7 Dec 1999, Darryl Okahata wrote: Michael Chin-Yuan Wu [EMAIL PROTECTED] wrote: Please try this tutorial when you move from -stable to -current www.external.org/freebsd/current.html I think you're missing the recent block device obsolescence change. I had to build and install a -CURRENT yacc when I upgraded right before thanks giving. I haven't looked to see if this has been changed. (I think it was a Makefile.inc? problem.) To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
gasp broke world.
Doug, 'gasp' broke world. targ-env.h: No such file or directory -- - bill fumerola - [EMAIL PROTECTED] - BF1560 - computer horizons corp - - ph:(800) 252-2421 - [EMAIL PROTECTED] - [EMAIL PROTECTED] - To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
this is wierd, PCM madness
Alright, Now with the last patch that was on here, FreeBSD detects my ViBRA16X, but for some reason, whenever I try to play something, it doesn't work... eg: culverk:~/.licq/data esdplay message.wav unsupported sound format: 4112 culverk:~/.licq/data This file played fine with the Voxware drivers, I can't use those anymore though because they only worked when I was using PNP OS = NO in BIOS... With the most recent PnP fixes I've had to go back to using PnP OS = yes in Bios... = | Kenneth Culver | FreeBSD: The best OS around.| | Unix Systems Administrator | ICQ #: 24767726 | | and student at The | AIM: AgRSkaterq | | The University of Maryland, | Website: (Under Construction) | | College Park. | http://www.wam.umd.edu/~culverk/| = To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: this is wierd, PCM madness
In addition to the soundcard... my modem won't attach to the sio driver... this is driving me nuts; any help would be appreciated... Kenneth Culver To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
make world broken on a 3 month old system
I'm trying to "make world" on a system last built on Sep 29th; it's failing like so: === f77doc /usr/obj/usr/src/gnu/usr.bin/cc/f77doc created for /usr/src/gnu/usr.bin/cc/f77doc cd /usr/src/gnu/lib/libgcc; /usr/obj/usr/src/tmp/usr/bin/make -DWORLD -DNOINFO -DNOMAN -DNOPIC -DNOPROFILE -DNOSHARED cleandepend; /usr/obj/usr/src/tmp/usr/bin/make -DWORLD -DNOINFO -DNOMAN -DNOPIC -DNOPROFILE -DNOSHARED all; /usr/obj/usr/src/tmp/usr/bin/make -DWORLD -DNOINFO -DNOMAN -DNOPIC -DNOPROFILE -DNOSHARED -B install; /usr/obj/usr/src/tmp/usr/bin/make -DWORLD -DNOINFO -DNOMAN -DNOPROFILE -DNOSHARED -B cleandir obj rm -f .depend /usr/obj/usr/src/gnu/lib/libgcc/GPATH /usr/obj/usr/src/gnu/lib/libgcc/GRTAGS /usr/obj/usr/src/gnu/lib/libgcc/GSYMS /usr/obj/usr/src/gnu/lib/libgcc/GTAGS echo '#include i386/xm-i386.h' config.h echo '#include xm-freebsd.h' config.h echo '#include "gansidecl.h"'tconfig.h echo '#include "i386/xm-i386.h"' tconfig.h echo '#include "i386/i386.h"'tm.h echo '#include "i386/att.h"' tm.h echo '#include "svr4.h"' tm.h echo '#include freebsd.h' tm.h echo '#include "i386/freebsd.h"' tm.h echo '#include "i386/perform.h"' tm.h cc -c -O -pipe -I/usr/src/gnu/lib/libgcc/../../../contrib/gcc/config -I/usr/src/gnu/lib/libgcc/../../../contrib/gcc -I. -fexceptions -DIN_GCC -I/usr/obj/usr/src/tmp/usr/include -DL_mulsi3 -o _mulsi3.o /usr/src/gnu/lib/libgcc/../../../contrib/gcc/libgcc1.c *** Signal 12 Stop in /usr/src/gnu/lib/libgcc. *** Error code 1 Stop in /usr/src. *** Error code 1 Stop. *** Error code 1 Stop. *** Error code 1 Stop. Should I be expecting this? :-) - mark -- Mark Newton Email: [EMAIL PROTECTED] (W) Network Engineer Email: [EMAIL PROTECTED] (H) Internode Systems Pty Ltd Desk: +61-8-82232999 "Network Man" - Anagram of "Mark Newton" Mobile: +61-416-202-223 To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: make world broken on a 3 month old system
Mark Newton wrote: I'm trying to "make world" on a system last built on Sep 29th; it's failing like so: === f77doc /usr/obj/usr/src/gnu/usr.bin/cc/f77doc created for /usr/src/gnu/usr.bin/cc/f77doc cd /usr/src/gnu/lib/libgcc; /usr/obj/usr/src/tmp/usr/bin/make -DWORLD -DNOINFO -DNOMAN -DNOPIC -DNOPROFILE -DNOSHARED cleandepend; /usr/obj/usr/src/tmp/usr/bin/make -DWORLD -DNOINFO -DNOMAN -DNOPIC -DNOPROFILE -DNOSHARED all; /usr/obj/usr/src/tmp/usr/bin/make -DWORLD -DNOINFO -DNOMAN -DNOPIC -DNOPROFILE -DNOSHARED -B install; /usr/obj/usr/src/tmp/usr/bin/make -DWORLD -DNOINFO -DNOMAN -DNOPROFILE -DNOSHARED -B cleandir obj rm -f .depend /usr/obj/usr/src/gnu/lib/libgcc/GPATH /usr/obj/usr/src/gnu/lib/libgcc/GRTAGS /usr/obj/usr/src/gnu/lib/libgcc/GSYMS /usr/obj/usr/src/gnu/lib/libgcc/GTAGS echo '#include i386/xm-i386.h' config.h echo '#include xm-freebsd.h' config.h echo '#include "gansidecl.h"'tconfig.h echo '#include "i386/xm-i386.h"' tconfig.h echo '#include "i386/i386.h"'tm.h echo '#include "i386/att.h"' tm.h echo '#include "svr4.h"' tm.h echo '#include freebsd.h' tm.h echo '#include "i386/freebsd.h"' tm.h echo '#include "i386/perform.h"' tm.h cc -c -O -pipe -I/usr/src/gnu/lib/libgcc/../../../contrib/gcc/config -I/usr/src/gnu/lib/libgcc/../../../contrib/gcc -I. -fexceptions -DIN_GCC -I/usr/obj/usr/src/tmp/usr/include -DL_mulsi3 -o _mulsi3.o /usr/src/gnu/lib/libgcc/../../../contrib/gcc/libgcc1.c *** Signal 12 Stop in /usr/src/gnu/lib/libgcc. *** Error code 1 Stop in /usr/src. *** Error code 1 Stop. *** Error code 1 Stop. *** Error code 1 Stop. Should I be expecting this? :-) - mark I think that your problem is covered in this cut and paste from /usr/src/UPDATING that has very interesting content:-) Be sure and read everything previous to this also. 19990929: The sigset_t datatype has been changed from an integral type to a compound type and can hold 128 signals. Syscalls directly or indirectly using the new sigset_t have been added as to maintain compatibility with existing binaries. A new kernel must be made and installed and booted with before a make world can be done. Hope that helps. ed To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: mount(2) broken?
That sounds like the conclusion I came to as well. I had a different
patch, but looking at yours, mine looks wrong.
Nick
"mount -f /" on a dirty root file system causes the clean flag to stay off
forever. (I forgot to change the unclean flag for mount -u.)
diff -c2 ffs_vfsops.c~ ffs_vfsops.c
*** ffs_vfsops.c~ Thu Nov 25 23:27:44 1999
--- ffs_vfsops.c Sun Dec 5 05:12:51 1999
***
*** 218,222
--- 220,226
}
+ fs-fs_flags = ~FS_UNCLEAN;
if (fs-fs_clean == 0) {
+ fs-fs_flags |= FS_UNCLEAN;
if (mp-mnt_flag MNT_FORCE) {
printf(
Bruce
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message
--
[EMAIL PROTECTED]
[EMAIL PROTECTED] USB project
http://www.etla.net/~n_hibma/
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message
Re: AWE64 problems
I looked for some meaning to the -100, is this documented somewhere? Who calls it? -Charlie On Wed, Dec 08, 1999 at 11:30:46AM +0900, Seigo Tanimura wrote: On Tue, 7 Dec 1999 23:00:02 +0100 (MET), Thomas Schuerger [EMAIL PROTECTED] said: --- sbc.c.orig Mon Dec 6 19:26:31 1999 +++ sbc.c Tue Dec 7 22:15:25 1999 @@ -110,7 +110,7 @@ if (error) return error; else - return -100; + return -1; } static int Thomas Works fine for me. Thanks!!! Yes, this patch should work. The probe likelyhood(do we call it so?) for unknown device is -100, so it does not make sense for sbc to return -100. -1 might be too high, -50 sounds good to me. -- Seigo Tanimura [EMAIL PROTECTED] [EMAIL PROTECTED] To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message -- Charles Anderson[EMAIL PROTECTED] No quote, no nothin' To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: AWE64 problems
I looked for some meaning to the -100, is this documented somewhere? It's not, yet. We should move to using some defines for this. A while back I proposed something like: #define DEVICE_MATCH_EXACT -100 #define DEVICE_MATCH_CLASS -200 #define DEVICE_MATCH_GENERIC-300 The 'exact' response is still 0 so that you can tune between two 'exact' drivers on a per-instance basis. The meanings should be pretty obvious... Who calls it? -Charlie On Wed, Dec 08, 1999 at 11:30:46AM +0900, Seigo Tanimura wrote: On Tue, 7 Dec 1999 23:00:02 +0100 (MET), Thomas Schuerger [EMAIL PROTECTED] said: --- sbc.c.orig Mon Dec 6 19:26:31 1999 +++ sbc.cTue Dec 7 22:15:25 1999 @@ -110,7 +110,7 @@ if (error) return error; else -return -100; +return -1; } static int Thomas Works fine for me. Thanks!!! Yes, this patch should work. The probe likelyhood(do we call it so?) for unknown device is -100, so it does not make sense for sbc to return -100. -1 might be too high, -50 sounds good to me. -- Seigo Tanimura [EMAIL PROTECTED] [EMAIL PROTECTED] To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message -- Charles Anderson [EMAIL PROTECTED] No quote, no nothin' 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: gasp broke world.
In [EMAIL PROTECTED] Bill Fumerola
[EMAIL PROTECTED] wrote:
Doug,
'gasp' broke world.
targ-env.h: No such file or directory
The next patch at least unbroke 'make buildworld'.
N.Dudorov
=
--- src/gnu/usr.bin/binutils/gasp/Makefile.ORIG Wed Dec 8 09:52:19 1999
+++ src/gnu/usr.bin/binutils/gasp/Makefile Wed Dec 8 09:52:19 1999
@@ -11,7 +11,7 @@
CFLAGS+= -I${SRCDIR}
CFLAGS+= -I${SRCDIR}/gas
CFLAGS+= -I${SRCDIR}/gas/config
-CFLAGS+= -I${.CURDIR}/../as/as_${MACHINE_ARCH}
+CFLAGS+= -I${.CURDIR}/../as/${MACHINE_ARCH}-freebsd
CFLAGS+= -DBFD_ASSEMBLER
LDADD+=-L${RELTOP}/libiberty -liberty
DPADD+=${RELTOP}/libiberty/libiberty.a
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message
Re: Using USB modules with an USB keyboard...
Thank you for your detailed report. I added your recommendations above to the kernel config file (TWELVE). It didn't work. As can be seen from the dmesg below, when the USB options are present in the kernel, ukbd0 is found. When USB KLDs are used, uhid0 seems to grab the keyboard. [This is the dmesg from a kernel (ELEVEN) that works. The config file for this includes all the USB options except for ums, which is loaded at bootup] As seen below, I have an USB mouse (ums0), and an USB keyboard (which seems to register as an USB keyboard and a mouse -- ums1). The keyboard does have a PS/2 mouse connector on it. This is the correct hehavior. If a USB device has more than one interface, it may require multiple drivers; one driver for each interface. [This is the kernel (TWELVE) that has no USB options. All the USB modules are loaded at bootup by the loader.conf scripts.] Dec 7 19:57:33 frabjous /kernel: real memory = 134217728 (131072K bytes) Dec 7 19:57:33 frabjous /kernel: avail memory = 127352832 (124368K bytes) Dec 7 19:57:33 frabjous /kernel: Preloaded elf kernel "kernel" at 0xc02ae000. Dec 7 19:57:33 frabjous /kernel: Preloaded elf module "vesa.ko" at 0xc02ae09c . Dec 7 19:57:33 frabjous /kernel: Preloaded elf module "cd9660.ko" at 0xc02ae1 38. Dec 7 19:57:33 frabjous /kernel: Preloaded elf module "procfs.ko" at 0xc02ae1 d8. Dec 7 19:57:33 frabjous /kernel: Preloaded elf module "green_saver.ko" at 0xc 02ae278. Dec 7 19:57:33 frabjous /kernel: Preloaded elf module "usb.ko" at 0xc02ae31c. Dec 7 19:57:33 frabjous /kernel: Preloaded elf module "ugen.ko" at 0xc02ae3b8 . Dec 7 19:57:33 frabjous /kernel: Preloaded elf module "uhid.ko" at 0xc02ae454 . Dec 7 19:57:33 frabjous /kernel: Preloaded elf module "ukbd.ko" at 0xc02ae4f0 . Dec 7 19:57:33 frabjous /kernel: Preloaded elf module "ulpt.ko" at 0xc02ae58c . Dec 7 19:57:33 frabjous /kernel: Preloaded elf module "ums.ko" at 0xc02ae628. Dec 7 19:57:33 frabjous /kernel: Preloaded elf module "umass.ko" at 0xc02ae6c 4. Dec 7 19:57:33 frabjous /kernel: link_elf: symbol cam_simq_alloc undefined ... Dec 7 19:57:33 frabjous /kernel: uhci0: Intel 82371AB/EB (PIIX4) USB control ler irq 10 at device 7.2 on pci0 Dec 7 19:57:33 frabjous /kernel: usb0: Intel 82371AB/EB (PIIX4) USB controll er on uhci0 Dec 7 19:57:33 frabjous /kernel: usb0: USB revision 1.0 Dec 7 19:57:33 frabjous /kernel: uhub0: Intel UHCI root hub, class 9/0, rev 1 .00/1.00, addr 1 Dec 7 19:57:33 frabjous /kernel: uhub0: 2 ports with 2 removable, self powere d Dec 7 19:57:33 frabjous /kernel: ums0: Logitech USB-PS/2 Mouse M-BA47, rev 1. 00/1.10, addr 2, iclass 3/1 Dec 7 19:57:33 frabjous /kernel: ums0: 4 buttons and Z dir. Dec 7 19:57:33 frabjous /kernel: uhid0: QTRONIX USB Keyboard and Mouse, rev 1 .00/1.10, addr 3, iclass 3/1 Dec 7 19:57:33 frabjous /kernel: ums1: QTRONIX USB Keyboard and Mouse, rev 1. 00/1.10, addr 3, iclass 3/1 Dec 7 19:57:33 frabjous /kernel: ums1: 3 buttons [...] Ok, I got the picture. The fix is on the way. I will contact you later. Kazu To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: Cannot mount cd9660
Keith Jang wrote: Michael Chin-Yuan Wu wrote: P.S. I did a patch for cd9660 and patch for reading Chinese filenames [patch is in attachment] [...] chinese_joliet.patch.for_3.2-19990615.gzType: application/x-gzip chinese_vfat-3.0.patch.gzType: application/x-gzip Come on, these patches have been available at ftp://freebsd.csie.nctu.edu.tw/pub/taiwan/CSIE/kernel_patch/ since 2.2.7, and the author is [EMAIL PROTECTED] Now you just rip it off and claim that's your work? I didn't take credit for this. :) Sorry if I didnt make myself clear. If you will look at my email again, P.S. I did a patch for cd9660 and patch for reading Chinese filenames [patch is in attachment] =uname -a FreeBSD keichii.internal.org 4.0-CURRENT FreeBSD 4.0-CURRENT #0 8:09 CST 1999 [EMAIL PROTECTED]:/usr/current/src .ATA i386 ===dmesg= as attachment =kernel= as attachment patches for chinese filesystems== as attachment == The === lined parts are all information meant to help people debug/understand my problem. The "p.s." part was also meant to help solve the problem. Sorry for not making myself clear. What I meant was, "I applied the patches to the sources, which may have caused the cdrom to not mount" Apologies for bad English usage and causing the confusion. [Doing/did a patch can mean two things in English A. to write the patch B. to patch the source with the file I know that A is usually the default definition, but it was 3am in the morning when I wrote that email. I apologize. -- Many humble apologies, Michael To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
