Re: gzip(1) hanging

1999-11-06 Thread Mark Murray
> Can anyone confirm this happens on their box? Anyone have any > ideas on how to go about fixing this? I get exactly the same thing. M -- Mark Murray Join the anti-SPAM movement: http://www.cauce.org To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the bod

Re: doscmd broken on current?

1999-11-06 Thread John Hay
> >Is doscmd working for anyone on current? Here I just get: > > > >- > > > >I have tried it on a single processor and SMP -current and both do the same > >thing. I had it working a while back, so I think my configuration is ok. > > > >Ideas on how to look into this? > > Start by invoking

Re: Serious locking problem in CURRENT

1999-11-06 Thread Dmitrij Tejblum
Brian Fundakowski Feldman wrote: > There were zero comments about what order things happen in; in fact, > the ordering in this case is Just Plain Lame (TM). It's much more > correct to explicitly check for fp->f_count == 1. Not sure what you mean. The commit clearly states that POSIX and BSD lo

Re: show stopper for Gcc 2.95.2 conversion

1999-11-06 Thread David O'Brien
On Sat, Nov 06, 1999 at 10:34:18AM +0100, Gary Jennejohn wrote: > Here's a patch to bus.h which works for both EGCS and GCC 2.95.2. I have Here is the patch I've been working on (before I 1st got BDE's reply). The changes are mostly from OpenBSD + style changes for the way we do things. Can you

Old KLD bug..

1999-11-06 Thread Julian Elischer
If I have a KLD module that has a registered dependency on some other module, then when I load the forst module it will load the second. this is all well and good but it ALWYA loads it, even when it's already in the kernel.. if kldstat can see it, then surely the loading modules should be able t

Re: ESS 1868 driver, again

1999-11-06 Thread D. Rock
Peter Wemm wrote: > > "D. Rock" wrote: > > I read the last mails regarding problems with their ESS 1868 boards. > > Well, at least it is partially working for them. I didn't have any > > luck with the driver for some time now. I couldn't get a single tone. > > > > With the old voxware driver, sou

Re: sio working

1999-11-06 Thread D. Rock
Warner Losh wrote: > > In message <[EMAIL PROTECTED]> "D. Rock" writes: > : I tried many different combinations. I disabled the onboard serial devices > : in the BIOS and kernel, so config index 0xf could grap io port 0x3f8 with > : irq 4 but the only thing I get is > : sio2: configured irq -1071

Re: Old KLD bug..

1999-11-06 Thread Mike Smith
> > If I have a KLD module that has a registered dependency on some other > module, > then when I load the forst module it will load the second. > this is all well and good but it ALWYA loads it, > even when it's already in the kernel.. > > if kldstat can see it, then surely the loading modules

Re: Old KLD bug..

1999-11-06 Thread Julian Elischer
> > Yes. See my posts previously on making the distinction between 'file' > and 'module'. You've just acquired some new programming talent there; > I'm sure I could dope out enough of what was worked out last time we > talked about this to give her something to work on. 8) > As if she does

SB Live! driver

1999-11-06 Thread Ilya Naumov
Hello, good news. Creative Labs has decided to make the drivers for their Soundblaster Live open source (see http://opensource.creative.com/). so, are there any plans to port it for FreeBSD? Best regards, Ilya mailto:[EMAIL PROTECTED] To Unsubscribe: send mail to

Re: SB Live! driver

1999-11-06 Thread Amancio Hasty
Hi, Take it up with -multimedia . The gus tarted to talk about it over there. -- Amancio Hasty [EMAIL PROTECTED] To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message

Re: ESS 1868 driver, again

1999-11-06 Thread D. Rock
"D. Rock" wrote: > > > Here my configuration: > > > device pcm0at isa? port 0x220 irq 5 drq 1 flags 0x15 > > > > Err, the ESS1868 is a PNP device. You should only have "device pcm0" and > > nothing more. You might also try "options PNPBIOS". You are running > > -current, right? > W

Re: sio working

1999-11-06 Thread D. Rock
Warner Losh wrote: > > In message <[EMAIL PROTECTED]> "D. Rock" writes: > : I tried many different combinations. I disabled the onboard serial devices > : in the BIOS and kernel, so config index 0xf could grap io port 0x3f8 with > : irq 4 but the only thing I get is > : sio2: configured irq -1071

RE: SB Live! driver

1999-11-06 Thread Francis J. Bruening
I just checked the web-site for a mailing list called freebsd-multimedia. I didn't find it?!? Is the web-site out of date, or did you mean some other mailing list? I too, am very anxious to get the SBLive stuff... thanks in advance. Regards, Francis -Original Message- From: [EMAIL

Re: SB Live! driver

1999-11-06 Thread Amancio Hasty
Subscribe to : [EMAIL PROTECTED] Have Fun Amancio -- Amancio Hasty [EMAIL PROTECTED] To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message

Re: Serious locking problem in CURRENT

1999-11-06 Thread Ollivier Robert
According to Jonathan Lemon: > NOTES > Locks are on files, not file descriptors. That is, file descriptors > du- plicated through dup(2) or fork(2) do not result in multiple > instances of a lock, but rather multiple references to a single lock. > If a process holding a lock o

Re: ESS 1868 driver, again

1999-11-06 Thread Peter Wemm
"D. Rock" wrote: > "D. Rock" wrote: > > > > Here my configuration: > > > > device pcm0at isa? port 0x220 irq 5 drq 1 flags 0x15 > > > > > > Err, the ESS1868 is a PNP device. You should only have "device pcm0" and > > > nothing more. You might also try "options PNPBIOS". You are run

Re: sio working

1999-11-06 Thread Warner Losh
In message <[EMAIL PROTECTED]> "D. Rock" writes: : With the latest -current I get a slightly different output: : : Nov 7 03:34:47 /kernel.new: pccard: card inserted, slot 0 : Nov 7 03:34:57 /kernel.new: sio2: irq maps: 0x105 0x105 0x105 0x105 : Nov 7 03:34:57 /kernel.new: sio2: probe failed

Re: sio working

1999-11-06 Thread Warner Losh
In message <[EMAIL PROTECTED]> "D. Rock" writes: : device sio0at isa? port IO_COM1 flags 0x10 irq 4 : device sio1at isa? port IO_COM2 irq 3 These look good. IIRC, the kernel I tested with also had: device sio2at isa? port IO_COM3 irq 5 disabled or