XFree86 4.0 in FreeBSD 4.0?

Hi, Just wondering if there are plans in the works to get Xfree86 4.0 into FreeBSD 4.0. I just noticed that X 4.0 has finally been released. -- Regards, Devin. To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message

Re: Error: no such 386 instruction: `state' ???

Oops! Sorry for the double post. :( Kmail got stupid on me... -- Regards, Devin. To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message

Error: no such 386 instruction: `state' ???

Hi, I am running a current snap from 2/28. FreeBSD dbm.wireless.net 4.0-2228-CURRENT FreeBSD 4.0-2228-CURRENT #2: Fri Mar 3 22:19:33 PST 2000 Often when compiling a port, the process fails with messages like the following: [...] Compiling smbd/pipes.c Compiling smbd/predict.c Compili

Error: no such 386 instruction: `state' ???

Hi, I'm running a snap from 2/28: FreeBSD dbm.wireless.net 4.0-2228-CURRENT FreeBSD 4.0-2228-CURRENT #2: Fri Mar 3 22:19:33 PST 2000 Often when compiling a port, the process will fail with messages like the following: [...] Compiling smbd/noquotas.c Compiling smbd/reply.c {standard in

Re: tunefs -p doesn't work for read-write mounts

Sheldon Hearn wrote: > > Hi folks, > > Shouldn't I be able to show the current tuneables for a given filesystem? > > # tunefs -p /usr > tunefs: cannot work on read-write mounted file system > > This is on a recent CURRENT. AFAIK, you always need to do this with unmounted file systems. Unless

Re: pcm - stutters

On Tue, 25 Jan 2000, Donn Miller wrote: > Nick Hibma wrote: > > > The output of my ESS 1869 stutters whenever there is no new data fed to > > it. For example pressing Ctrl-Z, or heavy disk usage (normally making > > mpg123 jump). The stuttering is repetition of one short fragment of > > about a

Re: load spike strangeness

> > Indeed, I could adduser bknowels and use/be Brad Knowels (for all you know > my name could also be Brad Knowels) if he prefers. I'm not like that though. > Some people just aren't happy if they aren't complaining about something. ^^^

Re: Sound and -current.

Julian Elischer wrote: > > So is there any chance that my Vibra16 Soundblaster will ever be > recognised again? > > I was surprised because I had imagined that the soundblaster would be the > first card supported under the new code. > > unknown0: at port 0x220-0x22f,0x300-0x301,0x388-0x38b

Re: ATA driver problem?? Solution (in my case)!

Hi Soren, No unfortunately it still fails with the patch and the UDMA disabled in the BIOS. I'd be happy to try anything else you can think of. :) Thanks. -- Regards, Devin. Soren Schmidt wrote: > > It seems Devin Butterfield wrote: > > Hi Soren/group, > > > >

Re: ATA driver problem?? Solution (in my case)!

Hi Soren/group, After spending a little time sniffing around in my BIOS I realized that my BIOS (Award BIOS) defaults to disabling UDMA for both master and slave and for some reason I never thought to check thisduh. Anyway after setting this to "auto" for both master and slave the problem see

Re: ATA driver problem?? (lost disk contact)

Hi, "Dave J. Boers" wrote: > > On Thu, Dec 16, 1999 at 08:29:14AM +0100, Soren Schmidt wrote: > > It seems Devin Butterfield wrote: > > > I just recently compiled a kernel with the new ATA driver and have > > > discovered a problem: if I run sysinstall, r

ATA driver problem?? (lost disk contact)

Hi, I just recently compiled a kernel with the new ATA driver and have discovered a problem: if I run sysinstall, right when it says "probing devices, please wait (this can be a while)" error messages saying... Dec 15 21:20:05 dbm /kernel: ata0-slave: ad_timeout: lost disk contact - resetting De