It seems Warner Losh wrote:
In message [EMAIL PROTECTED] Soren Schmidt writes:
: Hmm, I'm also having a hell of a time here, on closer inspection it
: turns out that my problem is that the kernel allways finds an ed0
: device allthough none is present. I have both an ed0 an ep0 device
: in
On Tue, 07 Sep 1999 at 23:19:14 -0700, Jordan K. Hubbard wrote:
Using:
controller pnp0
devicepcm0
In my kernel and "pnp aware OS" turned both on and off in my BIOS,
I get this on probe:
pcm0: Vibra16X at port 0x220-0x22f,0x330-0x331,0x388-0x38b irq 5 drq 1,3 on
*This is still work in progress*
There's a new set of patches (sources: sep 8, 7am CEST):
o http://www.FreeBSD.org/~marcel/signal/sys_i386.diff
sys/i386/i386, sys/i386/include
o http://www.FreeBSD.org/~marcel/signal/sys_ibcs2.diff
sys/i386/ibcs2
o
On Tue, 7 Sep 1999, Randy Bush wrote:
I built and installed a new world today. My last make world
was some months ago.
It seems that the boot loader has changed. Now, my AWE64
soundcard is not detected anymore.
My kernel.config looks like this
pnp 1 0 os enable port0 0x220 port1
On Wed, 8 Sep 1999, Soren Schmidt wrote:
It seems Warner Losh wrote:
In message [EMAIL PROTECTED] Michael
Reifenberger writes:
: if I do an upgrade to -current on my Tecra8000 the ep* driver stopps working.
The ep driver works in -current.
: The message from pccardc is that he
It seems Doug Rabson wrote:
Hmm, I'm also having a hell of a time here, on closer inspection it
turns out that my problem is that the kernel allways finds an ed0
device allthough none is present. I have both an ed0 an ep0 device
in my config as I use both type of cards. So my only
On Wed, 8 Sep 1999, Matthew N. Dodd wrote:
On Wed, 8 Sep 1999, Soren Schmidt wrote:
Hmm, I'm also having a hell of a time here, on closer inspection it
turns out that my problem is that the kernel allways finds an ed0
device allthough none is present. I have both an ed0 an ep0 device
It seems Soren Schmidt wrote:
It seems Doug Rabson wrote:
Hmm, I'm also having a hell of a time here, on closer inspection it
turns out that my problem is that the kernel allways finds an ed0
device allthough none is present. I have both an ed0 an ep0 device
in my config as I
Some "large footprint" changes have been made to the CVS tree and should
be nearly finished. In a nutshell:
- $Id$ and all other traditional rcs keywords are now preserved and
no longer touched by our tools.
- $FreeBSD$ is expanded as an alias for $CVSHeader$ (like $Header$ but
with the
Was the card recognised as pcm1 before? You probably need to go to /dev
and type:
sh MAKEDEV snd0
indeed, that was the problem.
randy
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message
I thought I'd try kicking sb0 out of my kernel and try pcm for a change,
but I cannot get it to work with simply "device pcm0". My sb16 is not pnp,
and adding controller pnp0 did not help. With just device pcm0, the
kernel mentions nothing of pcm at all. sb0 worked fine with:
controller
Not only does the sio device give me trouble, since I don't use it I took
it out, and rebuilt the kernel. Immediately upon reboot, I got a kernel
panic. It went like this:
Copyright (c) 1992-1999 The FreeBSD Project.
Copyright (c) 1982, 1986, 1989, 1991, 1993
The Regents of the
Not only does the sio device give me trouble, since I don't use it I took
it out, and rebuilt the kernel. Immediately upon reboot, I got a kernel
panic. It went like this:
Copyright (c) 1992-1999 The FreeBSD Project.
Copyright (c) 1982, 1986, 1989, 1991, 1993
The Regents of the
Adam McDougall wrote:
I thought I'd try kicking sb0 out of my kernel and try pcm for a change,
but I cannot get it to work with simply "device pcm0". My sb16 is not pnp,
and adding controller pnp0 did not help. With just device pcm0, the
kernel mentions nothing of pcm at all. sb0 worked
On Wed, 08 Sep 1999 16:53:37 +0300, Maxim Sobolev wrote:
Why you can't be happy with "device pcm0 at isa? port 0x220 irq 5 drq
1 flags 0x15" if it works?
I think Adam's just trying to make sure that he hasn't done something
silly which is preventing him from using a more graceful
pcm0: SoundBlaster 16 4.11 at port 0x220-0x22f irq 5 drq 1 flags 0x15 on
isa0
If dmesg from sb0 would help I could get it.. Anything else I could help
with in making "device pcm0" work without params? or is that pnp only?
Yes, that is for pnp-only.
--
we are but packets in the internet
I can only start my Xfree when ppp is up and running, is that a known problem ?
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message
I can only start my Xfree when ppp is up and running, is that a known problem ?
It's known that your DNS setup is busted, yes.
--
\\ The mind's the standard \\ Mike Smith
\\ of the man. \\ [EMAIL PROTECTED]
\\-- Joseph Merrick \\ [EMAIL PROTECTED]
Hi,
I have 'make release' up to the point where it fails building
the PCCARD kernel. It needs to have the miibus0 controller added.
A patch is attached.. Would someone please commit this?
Thanks,
john
ps: I'm still having problems with the size of the fixit floppy, but
currently I've
I have 'make release' up to the point where it fails building
the PCCARD kernel. It needs to have the miibus0 controller added.
A patch is attached.. Would someone please commit this?
What a coincidence! I just fixed this!
M
--
Mark Murray
Join the anti-SPAM movement: http://www.cauce.org
yeah, thanks.
- Original Message -
From: Mike Smith [EMAIL PROTECTED]
To: Tomer Weller [EMAIL PROTECTED]
Cc: Current [EMAIL PROTECTED]; Questions [EMAIL PROTECTED]
Sent: Wednesday, September 08, 1999 8:34 PM
Subject: Re: weird Xfree86 Issue
I can only start my Xfree when ppp is up and
Hi,
Has anyone had any luck using communicator with a LDAP server? Both
communicator 4.5 and 4.61 fails to connect to any LDAP server that I
have tried. It appears that the connect() gets interrupted and not
restarted. This happens both under current and 3.0.
Lars
To Unsubscribe: send
click on "Communicator" - AddressBook , then on your ldap server:
Fill in :
Description: User Friendly name for your ldap server
LDAP Server: ldap's hostname
Server Root: your server root
Port Number : the port number where your ldap server is listening to
From the address book window you
Hi,
I can't connect to the default ldap servers;however, on my win98 box I can connect
to the InfoSpace ldap server. I have a local ldap server here and I can connect
to it using netscape with no problem.
Try it : rah.star-gate.com port 389
--
Amancio Hasty
[EMAIL PROTECTED]
To
Matthew Reimer wrote:
Maybe the code is trying to bind the local side of the socket to port
0x5B? If so, then it could be proved by running Netscape as root.
No, 0x5B is the LDAP_CONNECT_ERROR hex value. As I pointed out in the truss earlier a
SIGALRM happens that causes connect() to return
After comments from Phk and Matt..
Particularly I'm looking for someone with a ccd and knowledge of it to
look at these patches, (not big) and see if they do anything of interest..
The theory is to inherrit the blocksizes of the underlying devices up to
the ccd device. I don't have a ccd array
Hi,
The following patch to /usr/src/release/Makefile allows the
specification of the variable FASTCLEAN, which instead of doing
a recursive rm on CHROOTDIR, simply umounts/newfs/mounts. Of
course, this is only useful if your CHROOTDIR location is a
separate mount point (which mine is: /snap).
John Polstra wrote:
If/when you change the size of jmp_buf, please remember to increment
__FreeBSD_version in "src/sys/sys/param.h". This is likely to break
the Modula-3 threads support (CVSup), and I'll need a way to deal with
that.
Good one. jmp_buf has indeed changed. Consider it done.
Hi,
The following patch to /usr/src/release/Makefile allows the
specification of the variable FASTCLEAN, which instead of doing
a recursive rm on CHROOTDIR, simply umounts/newfs/mounts. Of
course, this is only useful if your CHROOTDIR location is a
separate mount point (which mine is:
To me this very much sounds like feature creap. The less options, the
better, no one is looking at them anyway. Who says you are doing a
build on ufs anyway?
It might be something for a FAQ though (if there is one) or for the
handbook.
Just my 0.01 BEF.
Nick
The following patch to
30 matches
Mail list logo
