The new PnP code just plain does not work for my PnP AWE64.
If I configure like this:
controller pnp0
controller snd0
device sb0
device sbxvi0
device sbmidi0
device awe0
device opl0
device joy0
Which is the way it *should* work,
It seems Cejka Rudolf wrote:
I think internal bad block remapping is long time here. But
in the middle of 1996 I have bought a new Western Digital disk
with some bad sectors and it runs without any problems till today
(and without any new bad sectors - I have tried new disk format
some time
Are you sure everything is ok on your machine? I have done 4-5 make worlds
in the last 48 hours and except for the perl breakage, haven't had any
other problems. Even make release worked here.
John
--
John Hay -- [EMAIL PROTECTED]
I've been trying for the last 24 hours solid to make a new
I finally saw my first -current panic in more than 5 months (not a bad
track record).
I have a panic that I can duplicate with a 24 hour old "make world"
and a 4 hour old -current kernel. If I run the linux netscape (installed
from ports less than a week ago), the kernel panics in copystr().
According to Donald J . Maddox:
I get the same failures as above from the PnP code, but the card still
works (mostly) because it has already been configured by the PnP BIOS.
The SB16-compatible portion of the card works OK even if I take PnP
support out of the kernel completely, and always
Basically, I think not allowing ISP's to allow the Dialup lines to
forward email as a good thing, but for them to limit was businesses do
with their IP traffic is simply too big brother'ish, no matter what
their contract states.
If _we_ don't start to do something about it, big brother
If _we_ don't start to do something about it, big brother _is_ going
to do something about it. Trust me on this one, being a member of the
USPA I know that we are far better off implementing our own (as ISP's)
set of safe gaurds that help eliminate certain undesirable behavior.
[.]
When making /usr/ports/x11/gnome, the compiler fails with the following:
obgtkObject.m: In function `obgtk_signal_relay':
obgtkObject.m:133: Could not find a spill register
(insn:HI 564 562 565 (set (mem:DF (reg:SI 0 %eax))
(subreg:DF (reg:SI 128) 0)) 77 {movdf_mem+1} (insn_list 562
On Sun, 26 Sep 1999, Cejka Rudolf wrote:
Ok: Just run "disklabel -r -e ad0", clear word "badsect"
in "Flags:" line and booting of new kernels is back...
I think phk set to switch back to the wd driver to run disklabel, but
that shouldn't be necessary -- a new label can certainly be written
I made world and build a new kernel on Friday the 24th, and later that
evening, I got these:
Sep 24 18:00:33 jabberwock /kernel: ata0-master: ad_timeout: lost disk contact -
resetting
Sep 24 18:00:33 jabberwock /kernel: ata0: resetting devices .. done
Today morning, I found my machine
Brian Somers wrote in message ID
[EMAIL PROTECTED]:
I have some experience (from anti-spam mailing lists) of ISP's who
are quite prepared to open port 25 for customers who ask. This is
very good; SMTP has no authentication at all, and it is this
"free-for-all" feature that spammers abuse.
The whole point is that I want to be able to use the wavetable
synthesis features of the card. Newpcm (or oldpcm, for that matter)
provides NO support for the AWE device whatsoever, as you can see
from your dmesg below.
It makes little sense to me that PnP functionality should be tied
down to a
Mike Pritchard wrote:
I have a panic that I can duplicate with a 24 hour old "make world"
and a 4 hour old -current kernel.
If you use the linux module, make sure it's in sync with the kernel. If
that doesn't help, either follow Matt's advice or use ktrace/truss.
--
Marcel Moolenaar
:Brian Somers wrote in message ID
:[EMAIL PROTECTED]:
: I think it's up to the ISP what default policies they have, and I
: also think that this sort of policy is a good default... but only as
: long as the ISP allows exceptions. As a paying subscriber with a
: clean record I *must* be
Alex Zepeda wrote in message ID
Pine.BSF.4.10.9909261017060.367-10@localhost:
No, the real problem is the ISPs who can't fund decent servers and provide
decent service. If they could take care of spam and provide a 99%
reliable service, I'd have very few problems with using their
"Donald J . Maddox" wrote in message ID
[EMAIL PROTECTED]:
Ummm... I'm not screaming anything, Gary. The intent of my message is
just to let the authors of this code know that it is *not* equal in
functionality to what was removed. As I said in my original message, it
would be nice to see
Sigh. Again, I didn't demand anything.
I simply pointed out that functionality had been lost. If I
was the author of this code, I would *want* feedback on how
it was working out for people out here in userland. I assume
that the authors in question _do_ want such feedback.
Actually, in
On Sun, Sep 26, 1999 at 10:51:59AM -0700, Mike Smith wrote:
Sigh. Again, I didn't demand anything.
I simply pointed out that functionality had been lost. If I
was the author of this code, I would *want* feedback on how
it was working out for people out here in userland. I assume
I couldn't get my PnP Creative AWE64G to work with the new PnP
code, so I tried compiling a kernel with pcm instead. All I get is:
unknown0: Audio at port 0x220-0x22f,0x330-0x331,0x388-0x38b irq 5 drq 1,5 on isa0
unknown1: Game at port 0x200-0x207 on isa0
unknown2: WaveTable at port 0x620-0x623
On Sun, Sep 26, 1999 at 10:51:59AM -0700, Mike Smith wrote:
Sigh. Again, I didn't demand anything.
I simply pointed out that functionality had been lost. If I
was the author of this code, I would *want* feedback on how
it was working out for people out here in userland. I
On Sun, 26 Sep 1999 09:00:50 +0930, Greg Lehey wrote:
I've been trying for the last 24 hours solid to make a new world. The
latest problem is:
:-(
/src/PANIC/src/lib/libwrap/../../contrib/tcp_wrappers/hosts_access.c:245:
syntax error before `'
Hi Greg,
I was the last person to touch
On Sun, Sep 26, 1999 at 11:41:14AM -0700, Mike Smith wrote:
PnP is an infrastructure facility used by drivers to detect and
configure hardware. The side-effect you were relying on was that the
old code would indiscriminately configure any and all PnP hardware
regardless of whether
On Sun, Sep 26, 1999 at 11:59:33AM -0700, Mike Smith wrote:
On Sun, Sep 26, 1999 at 11:41:14AM -0700, Mike Smith wrote:
PnP is an infrastructure facility used by drivers to detect and
configure hardware. The side-effect you were relying on was that the
old code would
Hi, there.
We wrote experimental ACPI driver for 4.0-CURRENT.
This was just one week work so its functionallity is very very poor :-)
but I think it is good idea to start with this for developping ACPI
driver for FreeBSD because it is enough small to understand it.
I'm not sure this is
This is only partially related, but I still can't even boot a kernel with
the pnp0 controller enabled. It just hangs after probing the soundcard.
On Sun, 26 Sep 1999, Mike Smith wrote:
Sigh. Again, I didn't demand anything.
I simply pointed out that functionality had been lost. If I
This is only partially related, but I still can't even boot a kernel with
the pnp0 controller enabled. It just hangs after probing the soundcard.
You seem to have accidentally deleted all of the details related to
this bug report from your email before sending it. Please try again.
--
\\
Greg Lehey schrieb:
I've been trying for the last 24 hours solid to make a new world. The
latest problem is:
=== libwrap
cc -nostdinc -O -pipe -DFACILITY=LOG_AUTH -DHOSTS_ACCESS -DNETGROUP
-DDAEMON_UMASK=022 -DREAL_DAEMON_DIR=\"/usr/libexec\" -DPROCESS_OPTIONS
-DSEVERITY=LOG_INFO
"Donald J . Maddox" schrieb:
Is the new PnP code really so smart that it has no use for user intervention
ever? My experience indicates that it is not.
It would be very nice if the architects of the new PnP code would add back
this lost functionality.
My (QD) solution for this problem:
Thanks. That is exactly what I have done. The AWE device cannot
work this way, but everything else is functional if I remove the
PnP controller from my kernel...
On Sun, Sep 26, 1999 at 10:04:38PM +0200, D. Rock wrote:
"Donald J . Maddox" schrieb:
Is the new PnP code really so smart that it
Thanks again, Daniel... I'll take a look. If the ID isn't in there,
I'll submit a PR to get it added. (should only take about 10-12
months to actually get it comitted, if experience is a reliable guide :-/)
On Sun, Sep 26, 1999 at 10:09:58PM +0200, D. Rock wrote:
"Donald J . Maddox" schrieb:
"Donald J . Maddox" wrote:
I couldn't get my PnP Creative AWE64G to work with the new PnP
code, so I tried compiling a kernel with pcm instead. All I get is:
unknown0: Audio at port 0x220-0x22f,0x330-0x331,0x388-0x38b irq 5 drq 1,5 o
n isa0
unknown1: Game at port 0x200-0x207 on isa0
From the keyboard of Mike Smith:
I don't think an explanation of how PnP works or how it fits into our
device architecture is feasible at this point, so I'm going to
encourage you to do some research of your own.
An explanation of how PnP works is not necessary, some good books and
papers
From the keyboard of Kenneth Wayne Culver:
This is only partially related, but I still can't even boot a kernel with
the pnp0 controller enabled. It just hangs after probing the soundcard.
Same here for a week or two in which dfr was very helpful to try to find
out what happened.
With new
"Donald J . Maddox" wrote:
Ok, will do. Thanks.
This may be a silly question, but... The old PnP driver recognized
a lot of devices, including my AWE64. Isn't there a list of IDs it
was aware of that should be merged into newPnP ASAP?
The old PnP code was matching on the card vendor ID.
On Mon, Sep 27, 1999 at 05:05:37AM +0800, Peter Wemm wrote:
The old PnP code was matching on the card vendor ID. The new pnp code
treats each logical device on it's own and matches by logical ID..
(It's actually far more useful that way as most cards have their own
manufacturer ID but
On Sun, Sep 26, 1999 at 12:29:46PM -0700, Mike Smith wrote:
But we do have a working driver for the AWE64. Or rather, it worked fine
before the new PnP code was comitted, now it doesn't. It seems to me that
this indicates a deficiency in the new PnP code. Isn't that correct?
On Sun, Sep 26, 1999 at 02:29:43PM -0700, Mike Smith wrote:
Again, thanks for the very helpful and informative answers. I would still
appreciate it if someone could give me a little bit more of a clue as to
what is necessary to add newPnP-awareness to the AWE driver, though.
(Surly
Peter Wemm wrote:
"Donald J . Maddox" wrote:
Ok, will do. Thanks.
This may be a silly question, but... The old PnP driver recognized
a lot of devices, including my AWE64. Isn't there a list of IDs it
was aware of that should be merged into newPnP ASAP?
The old PnP code was
The old PnP code was matching on the card vendor ID. The new pnp code
treats each logical device on it's own and matches by logical ID.
The new architecture sounds like a good thing, but isn't there a way to
fall back to the old method if the logical device ID isn't found?
Perhaps
Vladimir Kushnir wrote:
Hello, here's an output for my Yamaha OPL-SA2 card (it used to work
perfectly all right as css device friends under old Pnp VoxWare, but
now outputs very poor sound through /dev/dsp and no sound at all when
playing audio CD, and of course no midi):
dmesg:
pcm0:
Thanks for replay, but what I am to do? At least, where to start looking?
Card is revognized, so this indeed shouldn't be PnP fault.
Card's 16 bit, but so far the only acceptable sound give esd or mpg123.
On Mon, 27 Sep 1999, Peter Wemm wrote:
Vladimir Kushnir wrote:
Hello, here's an output
Vladimir Kushnir wrote:
Thanks for replay, but what I am to do? At least, where to start looking?
Card is revognized, so this indeed shouldn't be PnP fault.
Card's 16 bit, but so far the only acceptable sound give esd or mpg123.
The person to talk to is Cameron Grant [EMAIL PROTECTED] for
On Sunday, 26 September 1999 at 21:01:17 +0200, Sheldon Hearn wrote:
On Sun, 26 Sep 1999 09:00:50 +0930, Greg Lehey wrote:
I've been trying for the last 24 hours solid to make a new world. The
latest problem is:
:-(
stopping chat on the tech lists is an open research project ;)
jmb
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message
Hi
I'm unable to get the new ATA driver to configure the HPT366 controller
to use busmastering DMA and to make the IBM 22GXP drive run at UDMA66.
Linux HPT366 driver supports busmastering DMA and UDMA66.
Does anybody know how to fix this?
Below is a portion of the output from dmesg:
In message [EMAIL PROTECTED], Mike Smith wrote:
Both Doug Rabson and myself have been tinkering with this, and there's
someone that's been looking at an AML parser/interpreter in the last
couple of weeks. At this point in time, the parser and object manager
are the most vital components.
On Mon, 27 Sep 1999 08:49:59 +0800 (SGT)
[EMAIL PROTECTED] wrote:
Hi
I'm unable to get the new ATA driver to configure the HPT366 controller
to use busmastering DMA and to make the IBM 22GXP drive run at UDMA66.
Linux HPT366 driver supports busmastering DMA and UDMA66.
Does anybody know
Peter Wemm [EMAIL PROTECTED] wrote:
We're not doing this because we enjoy pain and suffering, it's because
it'll be better and more robust in the long run. Unfortunately, there was
no canonical list of logical ID's on the cards we used to recognize.
So I repeat for the list.. If you've
On Sun, 26 Sep 1999, Mike Smith wrote:
This is only partially related, but I still can't even boot a kernel with
the pnp0 controller enabled. It just hangs after probing the soundcard.
You seem to have accidentally deleted all of the details related to
this bug report from your email
Hi, Mike.
# I'm very happy because of your reply :)
We wrote experimental ACPI driver for 4.0-CURRENT.
This was just one week work so its functionallity is very very poor :-)
but I think it is good idea to start with this for developping ACPI
driver for FreeBSD because it is enough
[EMAIL PROTECTED] said:
adams@nightfall(18:06:51)$ su
Password:load: 0.37 cmd: su 381 [ttyin] 0.00u 0.00s 0% 668k
load: 0.37 cmd: su 381 [ttyin] 0.00u 0.00s 0% 668k
load: 0.37 cmd: su 381 [ttyin] 0.00u 0.00s 0% 668k
each "load" line is an enter press.
[snip]
As soon as I get this
I too have encountered the same symptoms. I have no idea why this started
happening, but I have found a couple ways around it. First, two Control-Ds
will act as a Return if you find the status lines appearing. Second, the
stty command will fix it totally. I use `stty status ^T' to remap
Well said.
On Sun, 26 Sep 1999, Donald J . Maddox wrote:
On a more personal note - What *is* your problem, anyway? If you
don't have anything useful to contribute to the conversation, why
reply at all? Peter answered all my questions, and provided lots of
useful information in a single
On Sun, 26 Sep 1999, Mike Smith wrote:
This is only partially related, but I still can't even boot a kernel with
the pnp0 controller enabled. It just hangs after probing the soundcard.
You seem to have accidentally deleted all of the details related to
this bug report from your
Mike Smith wrote in list.freebsd-current:
Can you give me a few hints on what would be necessary to get the old
driver to work with the new PnP?
As has already been explained to you (you _do_ read these messages in
their entirety, right?), the old driver has been obsoleted. You
Peter Wemm [EMAIL PROTECTED] wrote:
Peter Jeremy wrote:
I appear to have two complete copies of gcc - one in src/contrib/gcc
and another in src/contrib/egcs/gcc.
src/contrib/gcc is where gcc used to live. Then along came egcs with a
cygnus-style tree that ended up in src/contrib/egcs (v1.1.1
unsubscribe
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message
unsubscribe freebsd-current
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message
It seems Jason Young wrote:
I looked at this yesterday (we just got one in). The HighPoint controller
has some specific initialization needs, just like the Promise controller.
The Linux code doesn't seem terribly twisted, although I didn't have
enough caffiene handy to try and interpret
59 matches
Mail list logo
