Re: No disks found msg in /stand/sysinstall, how come?
On Sat, Dec 18, 1999 at 06:01:21PM -0800, Mike Smith [EMAIL PROTECTED] wrote: Sysinstall is not build with 'make world', and should not be used on a system that's been updated that way. Well, thanks for the pointer, I've never looked at sysinstall build process. -- Vallo Kallaste [EMAIL PROTECTED] To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
world breakage in binutils
Hello
The world is broken for me for two days in:
--
elf make world started on Sun Dec 19 10:17:50 EET 1999
--
cc -O -pipe -D_GNU_SOURCE -I- -I. -I/usr/src/gnu/usr.bin/binutils/libiberty
-I/usr/src/gnu/usr.bin/binutils/libiberty/../libbfd/i386
-I/usr/src/gnu/usr.bin/binutils/libiberty/../../../../contrib/binutils/include
-I/opt/obj/usr/src/i386/usr/include -c
/usr/src/gnu/usr.bin/binutils/libiberty/../../../../contrib/binutils/libiberty/xstrerror.c
-o xstrerror.o
cc -O -pipe -D_GNU_SOURCE -I- -I. -I/usr/src/gnu/usr.bin/binutils/libiberty
-I/usr/src/gnu/usr.bin/binutils/libiberty/../libbfd/i386
-I/usr/src/gnu/usr.bin/binutils/libiberty/../../../../contrib/binutils/include
-I/opt/obj/usr/src/i386/usr/include -c
/usr/src/gnu/usr.bin/binutils/libiberty/../../../../contrib/binutils/libiberty/insque.c
-o insque.o
building standard iberty library
ranlib libiberty.a
=== libbfd
cc -O -pipe -D_GNU_SOURCE -I- -I. -I/usr/src/gnu/usr.bin/binutils/libbfd/i386
-I/usr/src/gnu/usr.bin/binutils/libbfd
-I/usr/src/gnu/usr.bin/binutils/libbfd/../libbfd/i386
-I/usr/src/gnu/usr.bin/binutils/libbfd/../../../../contrib/binutils/include
-DDEFAULT_VECTOR=bfd_elf32_i386_vec -DHAVE_bfd_elf32_i386_vec
-I/usr/src/gnu/usr.bin/binutils/libbfd/../../../../contrib/binutils/bfd
-DSELECT_ARCHITECTURES=" bfd_i386_arch" -DSELECT_VECS=" bfd_elf32_i386_vec"
-I/opt/obj/usr/src/i386/usr/include -c
/usr/src/gnu/usr.bin/binutils/libbfd/../../../../contrib/binutils/bfd/cpu-i386.c -o
cpu-i386.o
cc -O -pipe -D_GNU_SOURCE -I- -I. -I/usr/src/gnu/usr.bin/binutils/libbfd/i386
-I/usr/src/gnu/usr.bin/binutils/libbfd
-I/usr/src/gnu/usr.bin/binutils/libbfd/../libbfd/i386
-I/usr/src/gnu/usr.bin/binutils/libbfd/../../../../contrib/binutils/include
-DDEFAULT_VECTOR=bfd_elf32_i386_vec -DHAVE_bfd_elf32_i386_vec
-I/usr/src/gnu/usr.bin/binutils/libbfd/../../../../contrib/binutils/bfd
-DSELECT_ARCHITECTURES=" bfd_i386_arch" -DSELECT_VECS=" bfd_elf32_i386_vec"
-I/opt/obj/usr/src/i386/usr/include -c
/usr/src/gnu/usr.bin/binutils/libbfd/../../../../contrib/binutils/bfd/elf32-i386.c -o
elf32-i386.o
cc -O -pipe -D_GNU_SOURCE -I- -I. -I/usr/src/gnu/usr.bin/binutils/libbfd/i386
-I/usr/src/gnu/usr.bin/binutils/libbfd
-I/usr/src/gnu/usr.bin/binutils/libbfd/../libbfd/i386
-I/usr/src/gnu/usr.bin/binutils/libbfd/../../../../contrib/binutils/include
-DDEFAULT_VECTOR=bfd_elf32_i386_vec -DHAVE_bfd_elf32_i386_vec
-I/usr/src/gnu/usr.bin/binutils/libbfd/../../../../contrib/binutils/bfd
-DSELECT_ARCHITECTURES=" bfd_i386_arch" -DSELECT_VECS=" bfd_elf32_i386_vec"
-I/opt/obj/usr/src/i386/usr/include -c
/usr/src/gnu/usr.bin/binutils/libbfd/../../../../contrib/binutils/bfd/elf32.c -o
elf32.o
{standard input}: Assembler messages:
{standard input}:2028: Error: no such 386 instruction: `ovl'
*** Error code 1
Stop in /usr/src/gnu/usr.bin/binutils/libbfd.
*** Error code 1
Stop in /usr/src/gnu/usr.bin/binutils.
*** Error code 1
Stop in /usr/src.
*** Error code 1
Stop in /usr/src.
*** Error code 1
Stop in /usr/src.
Also it isn't possible to do make includes in the /usr/src, the way
around was to cd /usr/src/include; make WANT_CSRG_LIBM=yes install.
--
Vallo Kallaste
[EMAIL PROTECTED]
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message
Re: ata: Mount root failure: 6
Warner Losh writes: : : The fstab looks good : : : Is the kernel-config ok? : : I didn't see anything wrong with it, but maybe soren should take a : close look. This stuff definitely works for me on my laptop. Hate to follow up myself, but what boot blocks are you using? Really old ones use the disk label to determine what root device to pass to the kernel, and maybe that's where the problem lies? On any sort of -current system, the loader ignores this and uses the contents of /etc/fstab instead. I still haven't seen the plaintiff actually bother to transcribe the few relevant lines out of his startup log, so I'm not too highly motivated to worry about this in return, however ENXIO definitively means "the device you're trying to mount as root was not probed". Since it works with 'wd', and the 'ad' driver registers a 'wd' device as well, the actual options for dysfunction are pretty small. If and when more information is forthcoming, a diagnosis will be trivial. -- \\ 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: Weird story with dump | restore
On Fri, Dec 17, 1999 at 09:32:04AM -0800, Matthew Dillon [EMAIL PROTECTED] wrote: sysctl -a | fgrep dirty sysctl -w vfs.lodirtybuffers=X sysctl -w vfs.hidirtybuffers=Y Matt, I've tried your patch to sys/kern/vfs_bio.c, made no difference. Lowering the vfs.hidirtybuffers from 221 to 110 helps as before. The vfs.lodirtybuffers sysctl is gone for some reason. dmesg: 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: Sun Dec 19 09:45:03 EET 1999 root@tiiu:/usr/src/sys/compile/Tiiu Timecounter "i8254" frequency 1193199 Hz Timecounter "TSC" frequency 380232525 Hz CPU: AMD-K6(tm) 3D processor (380.23-MHz 586-class CPU) Origin = "AuthenticAMD" Id = 0x58c Stepping = 12 Features=0x8021bfFPU,VME,DE,PSE,TSC,MSR,MCE,CX8,PGE,MMX AMD Features=0x8800SYSCALL,3DNow! real memory = 31391744 (30656K bytes) avail memory = 27590656 (26944K bytes) Preloaded elf kernel "kernel" at 0xc02cd000. Preloaded userconfig_script "/boot/kernel.conf" at 0xc02cd09c. VESA: v2.0, 2048k memory, flags:0x4, mode table:0xc02815c2 (122) VESA: SiS devclass_alloc_unit: pcib0 already exists, using next available unit number npx0: math processor on motherboard npx0: INT 16 interface pcib0: Host to PCI bridge on motherboard pci0: PCI bus on pcib0 ata-pci0: SiS 5591 ATA controller irq 0 at device 0.1 on pci0 ata-pci0: Busmastering DMA supported ata0 at 0x01f0 irq 14 on ata-pci0 ata1 at 0x0170 irq 15 on ata-pci0 isab0: SiS 85c503 PCI-ISA bridge at device 1.0 on pci0 isa0: ISA bus on isab0 pci0: unknown card (vendor=0x1039, dev=0x0009) at 1.1 pcib2: PCI to PCI bridge (vendor=1039 device=0001) at device 2.0 on pci0 pci1: PCI bus on pcib2 vga-pci0: SiS model 6306 VGA-compatible display device at device 0.0 on pci1 fxp0: Intel EtherExpress Pro 10/100B Ethernet irq 11 at device 9.0 on pci0 fxp0: Ethernet address 00:a0:c9:97:90:65 pcm0: AudioPCI ES1371 irq 10 at device 11.0 on pci0 devclass_alloc_unit: pci1 already exists, using next available unit number pcib1: SiS 5591 host to AGP bridge on motherboard pci2: PCI bus on pcib1 atkbdc0: keyboard controller (i8042) at port 0x60-0x6f on isa0 atkbd0: AT Keyboard irq 1 on atkbdc0 vga0: Generic ISA VGA at port 0x3b0-0x3df iomem 0xa-0xb on isa0 sc0: System console on isa0 sc0: VGA 8 virtual consoles, flags=0x200 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 ppc0 at port 0x378-0x37f irq 7 on isa0 ppc0: Generic chipset (EPP/NIBBLE) 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: PNP0c01 at iomem 0-0x9,0xe-0xf on isa0 unknown: PNP can't assign resources unknown1: PNP0200 at port 0-0xf,0x80-0x90,0x94-0x9f,0xc0-0xde drq 4 on isa0 unknown2: PNP0100 at port 0x40-0x43 irq 0 on isa0 unknown3: PNP0b00 at port 0x70-0x71 irq 8 on isa0 unknown: PNP0303 can't assign resources unknown: PNP0800 can't assign resources unknown4: PNP0c04 at port 0xf0-0xff irq 13 on isa0 unknown5: PNP0a03 on isa0 unknown: PNP0501 can't assign resources unknown: PNP0400 can't assign resources unknown: PNP0700 can't assign resources unknown: PNP0c02 can't assign resources ad0: IBM-DPTA-353750/P51OA30A ATA-4 disk at ata0 as master ad0: 35772MB (73261440 sectors), 72680 cyls, 16 heads, 63 S/T, 512 B/S ad0: 16 secs/int, 32 depth queue, UDMA33 ad1: ST36530A/841273 ATA-3 disk at ata1 as master ad1: 6208MB (12715920 sectors), 13456 cyls, 15 heads, 63 S/T, 512 B/S ad1: 16 secs/int, 1 depth queue, UDMA33 acd0: NEC CD-ROM DRIVE:283/3.04 CDROM drive at ata1 as slave acd0: read 1376KB/s (1376KB/s), 128KB buffer, PIO acd0: Reads: CD-DA acd0: Audio: play, 256 volume levels acd0: Mechanism: ejectable tray acd0: Medium: no/blank disc inside, unlocked Mounting root from ufs:/dev/ad0a -- Vallo Kallaste [EMAIL PROTECTED] To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: ata: Mount root failure: 6
Thus spake Soren Schmidt ([EMAIL PROTECTED]): I now just build a kernel with the old wd drivers and everything works fine... Have you checked the badsect flags then ?? Yes. It was not set. 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: No disks found msg in /stand/sysinstall, how come?
Hi Mike, On Sat, Dec 18, 1999 at 06:01:21PM -0800, Mike Smith wrote: On Sat, Dec 18, 1999 at 04:21:19PM +0200, Vallo Kallaste wrote: Is is not possible to configure and add a second disk via the /stand/sysinstall Label and Fdisk menu's? ... I got this, too, ... but Hmm, yes I got it too. Me thinks it's related to change from block devices to char and to the MAKEDEV. Anybody out there please correct me if I'm wrong. I had to do standard disklabel -rw ad1 auto and after that edit the disklabel by hand. It's certainly not Sysinstall is not build with 'make world', and should not be used on a system that's been updated that way. ... but my /stand/sysinstall came from a freshly installed snapshot (19991208). In principle I'm (or was) rather used to using disklabel for labeling new disks. But recently (I would say for the last 12 months) I had various difficulties in disklabeling new drives. (on -stable and on -current) I found a solution in each of the cases eventually, but it made me not really happy. Once I just 'dd-ed' an existing label from another disk. This time I tried this strategy, too, but to no avail, since writing back the afterwards edited disklabel seemed not to be possible. (the "no space left on device"-message appeared ... ) ... just after having the standard disklabel -rw ad0 auto (my boot disk is da0) complained about 'no space left on device'. Yes, ... I did the disklabel -W ad0 ... You forgot to overwrite the beginning of the disk. ... and yes I did (before doing the 'fdisk') a nice little dd if=/dev/zero of=/dev/rad0 count=1 Do you have any further hints? Kind regards, Andreas Sidemark: Yes, ... I'm running -current on a few machines (and yes I know, that I get what I pay for ;). I'm used to live with -current since I switched my cvsup-Tag from stable to current on a 'brand new' dual PPro/200. standard disclaimer: I really don't want to sound insulting or arrogating or whatsoever. If anybody really might read such an undertone from my message(s), please ignore it and blame it on my rather ugly written English. -- Andreas Braukmann - TSE GmbH - Neue Medien - http://www.tse-online.de To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: ata: Mount root failure: 6
Thus spake Warner Losh ([EMAIL PROTECTED]): Hate to follow up myself, but what boot blocks are you using? Really old ones use the disk label to determine what root device to pass to the kernel, and maybe that's where the problem lies? Uhm. I don't know, what exactly you want to know, but I think you want to know these: alex:/boot $ ls -l boot* loader -r--r--r-- 1 root wheel 512 17 Dez 16:34 boot0 -r--r--r-- 1 root wheel 512 17 Dez 16:34 boot1 -r--r--r-- 1 root wheel7680 17 Dez 16:34 boot2 -r-xr-xr-x 1 root wheel 143360 17 Dez 16:34 loader* They are build on Dez, 17th, together with the make world. Or what do you mean? 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: No disks found msg in /stand/sysinstall, how come?
Okay that explains it, have to go back to the good old shell command's then... Thanks, Ron. - Original Message - Is is not possible to configure and add a second disk via the /stand/sysinstall Label and Fdisk menu's? ... I got this, too, ... but Sysinstall is not build with 'make world', and should not be used on a system that's been updated that way. To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: HEADSUP: wd driver will be retired!
On Wed, 15 Dec 1999, Robert Watson wrote: On Tue, 14 Dec 1999, Peter Wemm wrote: The RZ1000 is *dangerous*! We are doing no favours by making it run.. :-/ IMHO It is better to loose the user by not playing ball than to corrupt their data or run unreliably and make them hate us for it. http://www.faqs.org/faqs/pc-hardware-faq/enhanced-IDE/part1/ ... In both cases, the corruption occurs only in specific software environments and is very subtle; you can go on working for months without suspecting anything more than buggy software. The damage can I believe the FreeBSD environment is not one of the environments that has the problem. E.g., since the same spl (splbio()) is used for IDE and floppy interrupts and all device accesses occur at this spl (or higher), so mixing IDE and floppy accesses is almost automatically prevented. Since someone has code to detect these, how about putting this code in the ata driver probe so it can say something appropriately obscene and we start getting feedback about how widely deployed they are, and so that users can evaluate their risk in using the new driver? There's also Here is the code to detect and fix the problem with rz1000's in the wd driver: "" :-). The code to detect and fix the problem with CMD640B's is larger (about 60 lines plus grot in the infrastructure). Detection alone is easy (just a pci id compare). The ata driver already prints something obscene: "CMD 640 ATA controller (generic mode)" :-). Bruce To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: Sv: Dr Neuhaus niccy go not recognized
On Sun, 7 Nov 1999, German Tischler wrote: On Sun, Nov 07, 1999 at 06:27:37PM +0100, Leif Neland wrote: I'd like to test, So how do I proceed from here? Get the latest i4b-dev snapshot (00.83.11), get my patches from http://www.mayn.franken.de/home/tanis/i4b-11.tar.gz, get a recent current source tree, unpack i4b, unpack the layer1 patches over it, use the overinstall script, use I just want to say that it works in current -current. Leif To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: minor gcc-issue ?
On Sat, 18 Dec 1999, David O'Brien wrote: On Sat, Dec 18, 1999 at 02:43:03AM +1100, Bruce Evans wrote: 0301 is an old (bad) way of spelling MASK_80387 | MASK_IEEE_FP | MASK_FLOAT_RETURNS. Cygnus finally fixed it in in gcc/config/i386/freebsd.h on 1999/03/23 (see the ChangeLog), but FreeBSD hasn't merged the change. Actually Cygnus hasn't merged it. Cygnus's gcc/config/i386/freebsd.h is our gcc/config/i386/freebsd-aout.h. Their gcc/config/i386/freebsd-elf.h is our gcc/config/i386/freebsd.h. Cygnus has fixed the hard-coded constant. Merging only applies to FreeBSD. FreeBSD obtained the MASK_NO_FANCY_MATH_387 fix from somewhere (it was lost in at least the FreeBSD version of egcs). I now think it was obtained without merging, by using the old gcc version of TARGET_DEFAULT. Bruce To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: AMI MEGARAID problems.
On Wed, 15 Dec 1999, Mike Smith wrote: dd if=/dev/zero of=/dev/amrd0 count=16 disklabel -rw amrd0 auto newfs amrd0c Don't bother slicing the array in this case; it's not worth the effort. (The probable cause of your trouble is garbage at the beginning of the slice you've created). Also, "auto" doesn't work for slices (except for slices that cover the whole disk). Bruce To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: ata: Mount root failure: 6
Thus spake Mike Smith ([EMAIL PROTECTED]): I still haven't seen the plaintiff actually bother to transcribe the few relevant lines out of his startup log, so I'm not too highly motivated to worry about this in return, however ENXIO definitively means "the device you're trying to mount as root was not probed". Since it works with 'wd', and the 'ad' driver registers a 'wd' device as well, the actual options for dysfunction are pretty small. Ok, I scrolled up and wrote the stuff down by hand (args! :) Here are the messages regarding ata and hdd's: ata-pci0: VIA 82C586 ATA controller at device 7.1 on pci0 ata-pci0: Busmastering DMA supported ata0 at 0x01f0 irq 14 on ata-pci0 ata1 at 0x0170 irq 15 on ata-pci0 ... ad0: IBM-DHEA-36481/HP6OA20C ATA-3 disk at ata0 as master ad0: 6197 MB (12692736 sectors), 12592 cyls, 16 heads, 63 S/T, 512 B/S ad0: 16 secs/int, 1 depth queue, UDMA33 HTH, 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: more Promise Ultra wedges
It seems Andrew Gallatin wrote: Søren, It looks like I spoke to soon when I said the world was safe for Promise Ultra users: ad3: ad_timeout: lost disk contact - resetting ata4: resetting devices .. ad3: HARD WRITE ERROR blk# 6594768ad3: DMA problem en countered, fallback to PIO mode ad3: DMA problem encountered, fallback to PIO mode done ad1: UDMA CRC READ ERROR blk# 10522095 retrying ad3: ad_timeout: lost disk contact - resetting ata4: resetting devices .. done Is the above all info, or is it snipped somehow, its looks a bit wierd.. At this point the machine is unpingable will not respond to a break on the console. This is with a ccd stripe set, striped across 4 Maxtor "Diamondmax" drives attached one per channel to 2 Promise Ultra cards. `The kernel sources are dated slightly before the build time in the below boot messages. (I'd have given you verbose messages, but this is a transcript from the serial console logs the machine is wedged solid right now). I'm running with a timeout of 30 seconds as I was hoping to avoid a 'lost contact - resetting' situation as all hell breaks loose when those appear. BTW, I'd really like a tunable or some way to prevent a permanent fallback to PIO. I'm more than willing to tolerate one hard error per week or so on a disk which sees 10s of gigabytes of data read written between errors. Hmm, I'll think about what we can do here... The driver was much more stable back in July when (I guess) you just ignored errors. Using a July kernel, this machine will stay up for months with nothing but the occasional: ad3: status=51 error=84 ad_interrupt: hard error It never looses contact, never wedges. Oh for the good old days.. Hmm, back then you would get hosed data without knowing it, you feel better taht way ? I dont :) but I need to solve the hanging problem, I'll agree on that, anybody having a couple of bad disks I could borrow :) -Søren To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: ATA driver problem?? (lost disk contact)
It seems Allen Pulsifer wrote: According to the DPTA-3x spec from IBM, if the drive has fully entered Standby mode, it can take up to 31 seconds for it to spin back up. (See sections 3.3.6.1 and 13.0). Other drive models may take even longer, and even after the drive is back up, it may take a few seconds to respond to the command. You might have to set the timeout value as high as 45-60 seconds in order to get reliable operation. One possibility: the Check Power Mode command (sections 10.5.2 and 12.1) allows you to determine if the drive is in Standby mode. You might be able to timeout after 5-10 seconds, abort the read/write command, do a Check Power Mode command, and if the drive is in the process of spinning back up, then wait patiently for it to come to life before retrying the original read/write command. It looks to me like you would have to do a soft reset (sections 11.0, 9.6 and 10.1) in order to abort the read/write command. A soft reset would also cause the drive to come back to life if it were in Sleep mode (sections 3.3.6, 10.5.1 and 12.31). Note that section 13.0 (page 190) is explicit about this procedure: "We recommend that the host system executes Soft reset and then retry to issue the command if the host system would occur timeout for the device." This is more or less what is done now, I just doesn't do the check power mode after the reset, there is not much point, I know the disk is coming up. -Søren To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
ES1869 sound on laptop.
I just realized that my sound on my laptop has disappeared during the last couple of weeks. I usually keep the volume all the way down. Current as of yesterday. AMS Tech Laptop with AMD k-6 300. This is part of the dmesg. unknown6: ESS ES1869 Plug and Play AudioDrive at port 0x800-0x807 on isa0 sbc0: ESS ES1869 at port 0x220-0x22f,0x388-0x38b,0x330-0x331 irq 5 drq 1,0 on isa0 pcm0: SB DSP 3.01 on sbc0 unknown7: ESS ES1869 Plug and Play AudioDrive at port 0x201 on isa0 My configuration is: options PNPBIOS device pcm0 device sbc0 The output of cat /dev/sndstat is: FreeBSD Audio Driver (newpcm) Dec 18 1999 13:06:22 Installed devices: pcm0: SB DSP 3.01 at io 0x220 irq 5 drq 1:0 (1/1 channels duplex) I try to play anything even a cat gong.au/dev/audio and it just sticks. I just did new sh MAKEDEV snd0 just in case something had changed. I scanned the /usr/src/sys/i386/isa/sound readme's and haven't found a solution. Any ideas? I'm not sure if it has worked with the bridge driver or not. I really haven't been paying attention.:-( Thanks, ed To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: No disks found msg in /stand/sysinstall, how come?
... just after having the standard disklabel -rw ad0 auto (my boot disk is da0) complained about 'no space left on device'. Yes, ... I did the disklabel -W ad0 ... You forgot to overwrite the beginning of the disk. ... and yes I did (before doing the 'fdisk') a nice little dd if=/dev/zero of=/dev/rad0 count=1 Do you have any further hints? dd if=/dev/zero of=/dev/ad0 count=16 disklabel -rwB ad0 auto works. At some point you deviated from this. -- \\ 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: ata: Mount root failure: 6
On Sun, 19 Dec 1999, Mike Smith wrote: On any sort of -current system, the loader ignores this and uses the contents of /etc/fstab instead. which /etc/fstab? our systems always have 2 root partitions :-) To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: ata: Mount root failure: 6
On Sun, 19 Dec 1999, Mike Smith wrote: On any sort of -current system, the loader ignores this and uses the contents of /etc/fstab instead. which /etc/fstab? our systems always have 2 root partitions :-) Unless overridden, the one on the same filesystem the kernel was read from. -- \\ 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: ESS 1868, newpcm, and Linux RealPlayer 5.0
Edwin Culp wrote: You're lucky, you got to the realplayer.:-) My ESS1869 hangs on a simple cat gong.au/dev/audio. Do you have sound with everything except realplayer? Nope. Just tried cat hello.au /dev/dsp. Nothing. It hangs at the command line. Same with cat *.au /dev/audio. Hangs. Same behavior with RealPlayer in fact; RealPlayer just hangs when I press "play", and I get no sound. - Donn To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: ESS 1868, newpcm, and Linux RealPlayer 5.0
Donn, Thanks for the feedback. Misery loves company, they say.:-) We seem to have the same problem. Does anyone with a ESS 186[89] have their sound working with a recent world and device pcm0 device sbc0 Thanks, ed Donn Miller wrote: Edwin Culp wrote: You're lucky, you got to the realplayer.:-) My ESS1869 hangs on a simple cat gong.au/dev/audio. Do you have sound with everything except realplayer? Nope. Just tried cat hello.au /dev/dsp. Nothing. It hangs at the command line. Same with cat *.au /dev/audio. Hangs. Same behavior with RealPlayer in fact; RealPlayer just hangs when I press "play", and I get no sound. - Donn 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
Mount msdos floppy
When I try to mount an msdos floppy, that I almost never do, I am getting the following: # mount -tmsdos /dev/fd0 /mnt msdos: vfsload(msdos): Exec format error Disk works in windows. Any ideas? Thanks, ed Today's world without rebooting today's kernel. Still using yesterday's kernel. AMS laptop, AMD K-6/300. To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: Recent current hangs frequently for 1 to 2 seconds.
: driver, but it's also possible that they are due to a bug in the
: buffer cache flushing code which the following patch fixes. So try
: the patch and see if that fixes your problem. If it doesn't then
: we can at least rule it out as being the cause of the problem you
: are seeing.
:[..]
:
:Just one comment.. You've replaced vfs_bio's call to speedup_syncer() with
:a bufdaemon speedup..Granted I don't understand the details here, but
:I'm curious why? (or why not use both?) The reason I ask is that I wonder
:whether removing of the speedup of the vnode cleanup rate is a good idea or
:not.. or if the bufdaemon speedup does this as a side effect via the hooks
:softupdates has got in the bio system. This is not a criticism, just a
:request for enlightenment. :-)
speedup_syncer() was designed for softupdates to allow softupdates to
regulate the number of pending transactions. The problem with it,
though, is that calling the function results in a 'slow reaction' by
the system rather then an 'immediate reaction', and in this particular
case we need an immediate reaction. A slow reaction gets us nowhere
(gets us multi-second delays, in fact).
bd_speedup() wakes up the buf_daemon and as part of the patch the
buf_daemon has been redesigned to handle the 'immediate reaction' case
without compromising its dynamic stability characteristics (which are
what tend to make it efficient under normal operation).
-Matt
Matthew Dillon
[EMAIL PROTECTED]
:
: @@ -1571,9 +1573,8 @@
: flags = VFS_BIO_NEED_ANY;
: }
:
: -/* XXX */
: +bd_speedup(); /* hlp */
:
: -(void) speedup_syncer();
: needsbuffer |= flags;
: while (needsbuffer flags) {
: if (tsleep(needsbuffer, (PRIBIO + 4) | slpflag,
:
:Cheers,
:-Peter
:
:
:
:
: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: Weird story with dump | restore
:On Fri, Dec 17, 1999 at 09:32:04AM -0800, Matthew Dillon :[EMAIL PROTECTED] wrote: : : sysctl -a | fgrep dirty : sysctl -w vfs.lodirtybuffers=X : sysctl -w vfs.hidirtybuffers=Y : :Matt, I've tried your patch to sys/kern/vfs_bio.c, made no difference. :Lowering the vfs.hidirtybuffers from 221 to 110 helps as before. The :vfs.lodirtybuffers sysctl is gone for some reason. Oh my. Maybe we have two problems here. Alfred had similar problems and the patch fixed it right up. Try running a 'top -S -s1' while you are running your test, with my patch but without doing the sysctl's, and tell me what the various programs block on when the problem occurs (buf_daemon and whatever program is causing the hicup). -Matt To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: make world broken
On Sat, Dec 18, 1999 at 05:13:39PM -0800, Steve Kargl wrote: I did a "make -j 4 buildworld" every day last week. I did not see this error. Did you by any chance run configure in the contrib/gcc (or whatever the current gcc contrib source tree is called)? No. If your build tree ends up in /usr/obj, then you might try rm -rf /usr/obj chflags -r noschg /usr/obj rm -rf /usr/obj cd /usr/src make clean make buildworld That did the trick (although I had to do the buildworld twice - the first time there was this error about not knowing how to make .../stdarg.h). All is well again on my home box now. Maybe this was caused by my having done a world build in the middle of the build restructuring, which left /usr/obj in a "bad" state somehow. Thanks for your help sorting this one out. -- Jos Backus _/ _/_/_/ "Reliability means never _/ _/ _/ having to say you're sorry." _/ _/_/_/ -- D. J. Bernstein _/ _/ _/_/ [EMAIL PROTECTED] _/_/ _/_/_/ use Std::Disclaimer; To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: Got diskless Sun booting from FreeBSD server...
Thanks to Ian Dowse and Patrick Gardella i got my SPARCclassic booting and running as a nice Xterminal server. -- cut --- And a message I got from Ian Dowse said: I think sometime around 3.0, the networking code in FreeBSD stopped responding to IP broadcasts where the 'zero' subnet broadcast address, which in your case is 209.9.69.0. We currently work around this on some 3.x machines by adding an alias address (which can be anything, even not in the same subnet) that has a broadcast address of our subnet zero address. Try something like: ifconfig fxp0 inet 10.0.0.1 netmask 0x broadcast 209.9.69.0 alias Maybe the old behaviour of responding to the subnet zero address should be available via a sysctl? --- cut --- Among a lot of other things the bug above stopped my kernel from booting... The ifconfig workaround solved that.. All works ok now... I start this manually to keep my Sun booting: #!/bin/sh ifconfig xl0 inet 10.0.0.1 broadcast 192.168.1.0 alias bootparamd xdm -config /xsun/usr/lib/X11/xdm/xdm-config xfs Thanks all. Ron. To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: ** HEADS UP ** location of sendmail.cf changed
On Sun, Dec 19, 1999 at 12:05:43PM -0800, David O'Brien wrote: On your next CVSup, /usr/sbin/sendmail will look for sendmail.cf in /etc/mail/ , not /etc/. Then change was made because the current offical Sendmail Inc. version uses /var/mail/ and when we upgrade our repository to that version, we s/var/etc/ presunably. Joe -- Ua lawa küpono ka hakahaka pä o këia pä malule To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: ** HEADS UP ** location of sendmail.cf changed
On your next CVSup, /usr/sbin/sendmail will look for sendmail.cf in /etc/mail/ , not /etc/. Then change was made because the current offical Sendmail Inc. version uses /var/mail/ and when we upgrade our repository to that version, we s/var/etc/ presunably. Grrr. Yes. To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
make world broken?
I'm getting the following when I try to build world (cvs'd yesterday) i've blown away /usr/obj, re-cvs'd, and tried again.. it always fails in the same place. Writing Makefile for DynaLoader mkdir /usr/obj/c1/current/src/gnu/usr.bin/perl/perl/lib/auto/DynaLoader perl -I/usr/obj/c1/current/src/gnu/usr.bin/perl/perl/lib -I/usr/obj/c1/current/src/gnu/usr.bin/perl/perl/lib -I/usr/obj/c1/current/src/gnu/usr.bin/perl/perl/lib -I/usr/obj/c1/current/src/gnu/usr.bin/perl/perl/lib DynaLoader_pm.PL DynaLoader.pm Perl lib version (5.00503) doesn't match executable version (5.00501) at /usr/obj/c1/current/src/gnu/usr.bin/perl/perl/lib/Config.pm line 7. BEGIN failed--compilation aborted at DynaLoader_pm.PL line 2. *** Error code 255 Stop in /c1/obj/c1/current/src/gnu/usr.bin/perl/perl/ext/DynaLoader. *** Error code 1 Stop in /c1/current/src/gnu/usr.bin/perl/perl. *** Error code 1 Stop in /c1/current/src/gnu/usr.bin/perl. *** Error code 1 Stop in /c1/current/src/gnu/usr.bin. *** Error code 1 Stop in /c1/current/src/gnu. *** Error code 1 Stop in /c1/current/src. *** Error code 1 Stop in /c1/current/src. *** Error code 1 Stop in /c1/current/src. -- Welcome My Son, Welcome To The Machine -- Bob Vaughan | [EMAIL PROTECTED] | [EMAIL PROTECTED] | [EMAIL PROTECTED]| KC6SXC@W6YX.#NCA.CA.USA.NOAM | P.O. Box 9792, Stanford, Ca 94309-9792 -- I am Me, I am only Me, And no one else is Me, What could be simpler? -- To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: PCCARD vs GENERIC
On Sun, 19 Dec 1999, Warner Losh wrote: 4) The xe and wi drivers are not enabled in GENERIC but are in PCCARD. No reason at all not to have them in GENERIC. I think that the 40k that we saved in removal of old cdrom devices would more than make up for the extra pcic/pccard/wi/xe devices, but I'm biased. I'd love to see the xe driver in GENERIC, however I'd also love to see it _working_, not just compiling. My recent attempts to look at the code have proven just how little I know about device drivers. I have a few of these cards Warner, and would send one (you could even send me those cards I gave you at the con and I'll send one of these in that box.. :-). -- - 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
Re: PCCARD vs GENERIC
In message [EMAIL PROTECTED] Bill Fumerola writes: : I'd love to see the xe driver in GENERIC, however I'd also love to see : it _working_, not just compiling. My recent attempts to look at the code : have proven just how little I know about device drivers. Think of it as an opportunity :-) : I have a few of these cards Warner, and would send one (you could even : send me those cards I gave you at the con and I'll send one of these : in that box.. :-). I think that I have cards that would be supported by xe. I don't have the time to get them working on the old pccard system. I would make time on a consulting basis, but I really want to spend most of my spare time on the newcard stuff in advance of 4.0. Warner To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: PCCARD vs GENERIC
On Sun, 19 Dec 1999, Warner Losh wrote: In message [EMAIL PROTECTED] Bill Fumerola writes: : I'd love to see the xe driver in GENERIC, however I'd also love to see : it _working_, not just compiling. My recent attempts to look at the code : have proven just how little I know about device drivers. Think of it as an opportunity :-) My timesheet for last week had 100+ hours, I don't need more work. :- I think that I have cards that would be supported by xe. I don't have the time to get them working on the old pccard system. I would make time on a consulting basis, but I really want to spend most of my spare time on the newcard stuff in advance of 4.0. Okay, I have cardbus versions of this card too, if you need those for your newcard stuff. -- - 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
Re: No disks found msg in /stand/sysinstall, how come?
On Sun, Dec 19, 1999 at 10:12:16AM +0200, Vallo Kallaste wrote: On Sat, Dec 18, 1999 at 06:01:21PM -0800, Mike Smith [EMAIL PROTECTED] wrote: Sysinstall is not build with 'make world', and should not be used on a system that's been updated that way. Well, thanks for the pointer, I've never looked at sysinstall build process. # cd /usr/src/release/sysinstall # make all install This is in the "make world" section of the Handbook (makeworld.html), in the "Update /stand" section. N -- If you want to imagine the future, imagine a tennis shoe stamping on a penguin's face forever. --- with apologies to George Orwell To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: make world broken?
I think i'm crying wolf here.. i just noticed that there was an older version
of perl hanging out in /usr/local/bin.. lets see if thats the problem.
-- Welcome My Son, Welcome To The Machine --
Bob Vaughan | techie@{w6yx|tantivy}.stanford.edu | [EMAIL PROTECTED]
| P.O. Box 9792, Stanford, Ca 94309-9792
-- I am Me, I am only Me, And no one else is Me, What could be simpler? --
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message
Re: PCCARD vs GENERIC
In message [EMAIL PROTECTED] Bill Fumerola writes: : Okay, I have cardbus versions of this card too, if you need those for : your newcard stuff. Through the kind and generous efforts of FreeBSD Inc (or maybe walnut creek cdrom) I have this and lots of other cards as well. Warner To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
more wierd pcm behavior
I just recently started noticing with the ViBRA16X soundcard that in addition to the visualization plugins being lagged with newpcm, many songs play as static. When I first start playing the song, it plays as static, then if I pause it and unpause it, it plays fine. Just letting someone know what's going on. = | 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
