BIOS kernel option in -stable you might try, but no
> guarantees. I wonder if Toshiba has a program floating around to toggle
> the PnP bit anyway since it would preclude anything but Windows from
> running on the machine.
>
> --
I could try that only problem is that I ha
On Mon, 22 Sep 2003, Bruce Mackay wrote:
> > Most BIOSen with PnP support have an option to clear the device config and
> > force a PCI/PnP resource reconfiguration on next boot.
> >
>
>
> Laugh, it's actually a toshiba POS. I wish I had realised that
> the BIOS was so feeble. One of the
On Mon, 22 Sep 2003 09:27:52 -0700 (PDT)
Doug White <[EMAIL PROTECTED]> wrote:
> On Mon, 22 Sep 2003, Bruce Mackay wrote:
>
> > Yeah the only thing I can change in this stupid BIOS is the time.
> > PnP cannot be turned off through the BIOS apparently. What do you mean
> > by wiping the devic
On Mon, 22 Sep 2003, Bruce Mackay wrote:
> Yeah the only thing I can change in this stupid BIOS is the time.
> PnP cannot be turned off through the BIOS apparently. What do you mean
> by wiping the device configuration? Maybe I'll try doing that anyway
> and see what happens.
Is this some
oading them
> > as modules with no success. I was reading somewhere that I may need
> > hw.pci.enable_io_modes = 1 to use my sound card. However I cannot boot
> > unless I set hw.pci.enable_io_modes = 0. Any ideas on how I can get
> > around this? Or if this will even help..
io_modes = 1 to use my sound card. However I cannot boot
> unless I set hw.pci.enable_io_modes = 0. Any ideas on how I can get
> around this? Or if this will even help...
You might check that your BIOS has PnP OS set to No, and try wiping the
device configuration. You may just b
| FreeBSD: The Power to Serve
> [EMAIL PROTECTED] | www.FreeBSD.org
I actually tried hw.pci.allow_unsupported_io_range = 1 to no avail. I've
tried building pcm into my kernel, I've tried loading them as modules with no success.
I was reading somewh
On Sat, 20 Sep 2003, Bruce Mackay wrote:
>
> Hey all,
>
> I get the following hang up when I try booting up, here's the problem area...
>
> pcm0: at device 31.5 on pci0
> pcm0: unable to map IO port space
> device_probe_and_attach: pcm0 attach returned 6
>
> I'm running a CVSUP -curr
Hey all,
I get the following hang up when I try booting up, here's the problem area...
pcm0: at device 31.5 on pci0
pcm0: unable to map IO port space
device_probe_and_attach: pcm0 attach returned 6
I'm running a CVSUP -current from Thu Sep 18 12:34:00 EDT 2003, I have a
Yama
Hello,
On Fri, Aug 22, 2003 at 11:30:45AM -0400, Matt Gostick wrote:
> On Wed, 2003-08-20 at 17:04, Szilveszter Adam wrote:
> > What does 'cat /dev/sndstat' say?
>
> # cat /dev/sndstat
> FreeBSD Audio Driver (newpcm)
> Installed devices:
> pcm0: at io 0x220 irq 7 drq 0 bufsz 4096d (1p/1r/0v
> c
On Wed, 2003-08-20 at 17:04, Szilveszter Adam wrote:
> Hello,
>
> On Wed, Aug 20, 2003 at 03:20:55PM -0400, Matt Gostick wrote:
> > I have a SND Blaster 16 in my computer. I was using FreeBSD 4.8 and
> > 'device pcm' in my kernel config file, worked great. I've completely
> > re-installed with 5
Hello,
On Wed, Aug 20, 2003 at 03:20:55PM -0400, Matt Gostick wrote:
> I have a SND Blaster 16 in my computer. I was using FreeBSD 4.8 and
> 'device pcm' in my kernel config file, worked great. I've completely
> re-installed with 5.1R and recompiled my kernel with 'device pcm'.
> Unfortunately
I have a SND Blaster 16 in my computer. I was using FreeBSD 4.8 and
'device pcm' in my kernel config file, worked great. I've completely
re-installed with 5.1R and recompiled my kernel with 'device pcm'.
Unfortunately sound doesn't work.
I no longer have a /dev/snd0 device - I think I had one b
From: "David W. Chapman Jr." <[EMAIL PROTECTED]>
Subject: Re: ESS sound card support on laptop
Date: Sat, 15 Jun 2002 18:11:35 -0500
Message-ID: <[EMAIL PROTECTED]>
dwcjr> The rumor I heard is that their english isn't that good so that I
dwcjr> might not
"David W. Chapman Jr." wrote:
> > That was kind of my point to David: blaming MS doesn't make FreeBSD
> > work. At some point, you have to accept that the problem is yours,
> > rather than being caused by some outside agency.
>
> I'm not sure I understand if you're referring to me. I haven't
>
On Sat, Jun 15, 2002 at 05:07:53PM -0600, M. Warner Losh wrote:
> In message: <[EMAIL PROTECTED]>
> "David W. Chapman Jr." <[EMAIL PROTECTED]> writes:
> : > We write it. It isn't in the BIOS anymore. Usually with ACPI.
> : Now that msmith left, do we have any acpi gurus?
>
> There a
In message: <[EMAIL PROTECTED]>
"David W. Chapman Jr." <[EMAIL PROTECTED]> writes:
: I'm not sure I understand if you're referring to me. I haven't
: blamed MS or even mentioned MS. If I understand warner correctly, it
: can be solved by working on ACPI.
Partially solved by workin
In message: <[EMAIL PROTECTED]>
Terry Lambert <[EMAIL PROTECTED]> writes:
: That was kind of my point to David: blaming MS doesn't make FreeBSD
: work. At some point, you have to accept that the problem is yours,
: rather than being caused by some outside agency.
Actually, it was cau
In message: <[EMAIL PROTECTED]>
"David W. Chapman Jr." <[EMAIL PROTECTED]> writes:
: > We write it. It isn't in the BIOS anymore. Usually with ACPI.
: Now that msmith left, do we have any acpi gurus?
There are many japanese that are expert at this. I had plans on
taking up at least
> That was kind of my point to David: blaming MS doesn't make FreeBSD
> work. At some point, you have to accept that the problem is yours,
> rather than being caused by some outside agency.
>
I'm not sure I understand if you're referring to me. I haven't
blamed MS or even mentioned MS. If I
"M. Warner Losh" wrote:
> : > FreeBSD should, but isn't, assign resources to PCI devices. In the
> : > past, the BIOS has done this, but MS has migrated this functionality
> : > into the OS. That's why you see a lot of these sorts of failures with
> : > various kludges in the FreeBSD tree. That
> We write it. It isn't in the BIOS anymore. Usually with ACPI.
>
Now that msmith left, do we have any acpi gurus?
--
David W. Chapman Jr.
[EMAIL PROTECTED] Raintree Network Services, Inc.
[EMAIL PROTECTED] FreeBSD Committer
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsu
In message: <[EMAIL PROTECTED]>
Terry Lambert <[EMAIL PROTECTED]> writes:
: "M. Warner Losh" wrote:
: > In message: <[EMAIL PROTECTED]>
: > "David W. Chapman Jr." <[EMAIL PROTECTED]> writes:
: > : pcm0: irq 5 at device 14.0 on pci0
: > : pcm0: unable to map register space
> past, the BIOS has done this, but MS has migrated this functionality
> into the OS. That's why you see a lot of these sorts of failures with
> various kludges in the FreeBSD tree. That's part of what I was
> talking about in the developers conference when I said we needed to
> make PCI work ag
"M. Warner Losh" wrote:
> In message: <[EMAIL PROTECTED]>
> "David W. Chapman Jr." <[EMAIL PROTECTED]> writes:
> : pcm0: irq 5 at device 14.0 on pci0
> : pcm0: unable to map register space
> : device_probe_and_attach: pcm0 attach returned 6
>
> FreeBSD should, but isn't, assign resou
In message: <[EMAIL PROTECTED]>
"David W. Chapman Jr." <[EMAIL PROTECTED]> writes:
: pcm0: irq 5 at device 14.0 on pci0
: pcm0: unable to map register space
: device_probe_and_attach: pcm0 attach returned 6
FreeBSD should, but isn't, assign resources to PCI devices. In the
past, the
> > vendor = 'ESS Technology'
> > device = 'ES1978 Maestro-2E Audiodrive, ES1970 Canyon3D'
> > class= multimedia
> > subclass = audio
> >
> > --
> > David W. Chapman Jr.
> > [EMAIL PROTECTED] Raintree Network Services, Inc.
> > [EMAIL PROTECTED] FreeBSD Committer
On Sat, Jun 15, 2002 at 01:52:16PM -0600, Scott Long wrote:
> On Sat, Jun 15, 2002 at 02:52:33PM -0500, David W. Chapman Jr. wrote:
> > I have the following sound card on my laptop, does anyone know how
> > hard it would be to add this card to the pcm driver.
> >
On Sat, Jun 15, 2002 at 02:52:33PM -0500, David W. Chapman Jr. wrote:
> I have the following sound card on my laptop, does anyone know how
> hard it would be to add this card to the pcm driver.
>
> none2@pci0:14:0:class=0x040100 card=0x2550107b chip=0x1978125d rev=0x1
I have the following sound card on my laptop, does anyone know how
hard it would be to add this card to the pcm driver.
none2@pci0:14:0:class=0x040100 card=0x2550107b chip=0x1978125d rev=0x10
hdr=0x00
vendor = 'ESS Technology'
device = 'ES1978 Maestro-2E Aud
> says: pcm1: at port
> 0x534-0x537,0x388-0x38b,0x220-0x22f irq 5 drq 1,0 on
> isa0
you have a bogus device pcm0. you probably have a mistake in your hints
file.
-cg
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message
On Thu, Feb 22, 2001 at 04:31:30PM -0800, Liu Siwei wrote:
> Hello, My question is:
> My sound card is CS423X, FreeBSD supports it. It
> says: pcm1: at port
> 0x534-0x537,0x388-0x38b,0x220-0x22f irq 5 drq 1,0 on
> isa0
> . But my system is FreeBSD-current, the /dev file
>
On 23-Feb-01 Liu Siwei wrote:
> Hello, My question is:
> My sound card is CS423X, FreeBSD supports it. It
> says: pcm1: at port
> 0x534-0x537,0x388-0x38b,0x220-0x22f irq 5 drq 1,0 on
> isa0
> . But my system is FreeBSD-current, the /dev file
> system I can't w
Hello, My question is:
My sound card is CS423X, FreeBSD supports it. It
says: pcm1: at port
0x534-0x537,0x388-0x38b,0x220-0x22f irq 5 drq 1,0 on
isa0
. But my system is FreeBSD-current, the /dev file
system I can't write, can't use sh MAKEDEV snd0, and
all software to look for /
This is on a -current system when loading snd_maestro some time after boot.
pcm0: port 0x1400-0x14ff irq 5 at device 8.0 on pci0
pcm0: chn_init() for (play:0) failed
pcm0: offset 0xfef7a000 exceeds limit. pcm0: chn_init() for (play:1) failed
pcm0: offset 0xfefa9000 exceeds limit. pcm0: chn_init
My system can recognize my VIA AC97 on board sound card. I can use cat /dev/sndstat to
see my sound card information. But why i cann't play any sound ?
N
'²æìr¸zǧvf¢Ú&j:+v¨· è® "¶§²æìr¸yúÞy» rêëz{bØ^nr¡ûazg¬±¨
System is : FreeBSD -current 11,2000
I compile my system and kernel with device pcm, the system say message
when I run cat /dev/sndstat:
FreeBSD Audio Driver (newpcm) Nov 2 2000 17:31:39
Installed devices:
pcm0: at io 0xdc00 irq 5 (1p/1r channels duplex)
but when i play sound, the sound is ve
I managed to find a little more info on this chip in my new soundcard. It
is slightly different from a regular es1371... and in linux it even get's
some of its own #defines:
CT5880REV_CT5880_C is it's revision. (or 0x02) and the chip says CT5880 on
it. I'm assuming it's not much different, but so
Alright, this just bit me in the ass... I just bought a card today
that says "Creative Ensoniq AudioPCI" on the box. Well, as far as I can
tell this card uses the es1371 chip. Well, I did a little digging because
apparently the card's pci device id wasn't in the es137x.c file. So what I
did was I
On Tue, 15 Feb 2000, Peter Wemm was heard blurting out:
> Ron 'The InSaNe One' Rosson wrote:
> > On Sun, 13 Feb 2000, MIHIRA Yoshiro was heard blurting out:
> >
> > > [EMAIL PROTECTED] wrote:
> > >
> > > >> Ron 'The InSaNe One'
Ron 'The InSaNe One' Rosson wrote:
> On Sun, 13 Feb 2000, MIHIRA Yoshiro was heard blurting out:
>
> > [EMAIL PROTECTED] wrote:
> >
> > >> Ron 'The InSaNe One' Rosson wrote:
> > >> > Under 3.3-RELEASE with PA
On Sun, 13 Feb 2000, MIHIRA Yoshiro was heard blurting out:
> [EMAIL PROTECTED] wrote:
>
> >> Ron 'The InSaNe One' Rosson wrote:
> >> > Under 3.3-RELEASE with PAO the sound card work with this entry in the
> >> > config file:
> >> >
[EMAIL PROTECTED] wrote:
>> Ron 'The InSaNe One' Rosson wrote:
>> > Under 3.3-RELEASE with PAO the sound card work with this entry in the
>> > config file:
>> >
>> >device pcm0 at isa? port ? tty irq 5 drq 1 flags 0x0
>> >
&
Ron 'The InSaNe One' Rosson wrote:
> Under 3.3-RELEASE with PAO the sound card work with this entry in the
> config file:
>
> device pcm0 at isa? port ? tty irq 5 drq 1 flags 0x0
>
> Here is what the dmesg output looked like with that entry:
>
>
Under 3.3-RELEASE with PAO the sound card work with this entry in the
config file:
device pcm0 at isa? port ? tty irq 5 drq 1 flags 0x0
Here is what the dmesg output looked like with that entry:
pcm0 at 0x220 irq 5 drq 1 on isa
ESS1879 (rev 11, native mode)
Now under
At 04:52 AM 1/1/00 +, Cameron Grant wrote:
> > Donn> "ba ba ba ba ba ba ba ba ba ba ba ba ba ba". I have the ESS
> > Donn> 1868, of course. Well, I (wisely) saved my old kernel as
> > Donn> /kernel.good and just booted into that.
> >
> > Donn> Could you also say what was fixed if you get aro
> Donn> "ba ba ba ba ba ba ba ba ba ba ba ba ba ba". I have the ESS
> Donn> 1868, of course. Well, I (wisely) saved my old kernel as
> Donn> /kernel.good and just booted into that.
>
> Donn> Could you also say what was fixed if you get around to it? I'd
> Donn> to learn a little more about the
On Wed, 29 Dec 1999 20:38:48 -0500,
Donn Miller <[EMAIL PROTECTED]> said:
Donn> I just recently did another cvsup, and now newpcm is broken
Donn> again. When I try to play a clip with mpg123, I hear a very
Donn> short burst of the beginning of the clip repeated indefinitely,
Donn> like so:
Do
Seigo Tanimura wrote:
>
> On Mon, 27 Dec 1999 16:08:01 +0900,
> Seigo Tanimura <[EMAIL PROTECTED]> said:
>
> Seigo> Another fix was made on feeding and sucking pcm data. Now chn_wrfeed()
> Seigo> and the other functions do not attempt excessive feeding during DMA
> Seigo> transfer to eat up th
Hi,
On Thu, Dec 09, 1999 at 11:16:58PM +0300, Dmitrij Tejblum wrote:
> > Good luck using it under current.
> >
> > First site you hit quits netscape without reasons...
... yes. I built the port for the first time just yesterday and made
the same experience.
> > ...until you drop out of X and se
> Hi ..
>
> Under current the flash plugin works with the linux version of
> Netscape and the linuxelator ... Sound etc, everything works ok ...
> except for the odd crash of netscape which is normal :)
Hmmm. The developers of mozilla are dying to get bug reports
http://www.mozilla.org 8)
Some
Hi ..
Under current the flash plugin works with the linux version of
Netscape and the linuxelator ... Sound etc, everything works ok ...
except for the odd crash of netscape which is normal :)
Just get the linux netscape and the linux flash plugin.
Reinier
> [again subject changes]
>
> -On [1
> Good luck using it under current.
>
> First site you hit quits netscape without reasons...
>
> ...until you drop out of X and see a __sh_getcontext IIRC warning on
> your console.
If you can hack on the flash plugin's Makefile, try add -fno-exceptions
there.
Dima
To Unsubscribe: send m
On Thu, Dec 09, 1999 at 08:32:05PM +0100, Jeroen Ruigrok/Asmodai wrote:
> [again subject changes]
>
> -On [19991209 16:00], Donn Miller ([EMAIL PROTECTED]) wrote:
> >On Thu, 9 Dec 1999, Motoyuki Konno wrote:
> >
> >> Please see Netscape plugin port (ports/www/flashplugin) to find
> >> out why we
[again subject changes]
-On [19991209 16:00], Donn Miller ([EMAIL PROTECTED]) wrote:
>On Thu, 9 Dec 1999, Motoyuki Konno wrote:
>
>> Please see Netscape plugin port (ports/www/flashplugin) to find
>> out why we still have to need a.out support.
>
>Wow -- there's a flash plugin for Netscape? That
sites. Also, I hope to contribute in some way to broaden
FreeBSD's sound card support.
I have the ESS 1868. I just made a printout of the data sheets for this
particular sound card. If anyone out there needs the pdf version of the
ESS 1868 datasheet/specs, just email me and I can send you
Since the new sound code has been committed, my cheapo Opti931
sound card hasn't been working. Hopefully with the dmesg and
pnpinfo output which is attached, somebody can add the proper
vendor IDs. Much appreciated.
Neal
Checking for Plug-n-Play devices...
Card assigned CSN #1
Vend
According to Doug Rabson:
> Can I see your kernel config and dmesg lines both from an old (working)
> kernel and from the new kernel.
To add positive note to this, I just rebooted my dual PPro with newpcm and the
sound card was recognised and is working.
-=-=-
unknown0: on isa0
pcm0: a
After i got 1.117 everything went back to normal.
Arthur H. Johnson II
http://www.linuxberg.com
Linuxberg Manager
[EMAIL PROTECTED]
On Sat, 4 Sep 1999, Doug Rabson wrote:
> On Sat, 4 Sep 1999, Arthur H. Johnson II wrote:
>
> > Done, and I have pci.c 1.117. When did it get broken then fixed?
On Sat, 4 Sep 1999, Arthur H. Johnson II wrote:
> Done, and I have pci.c 1.117. When did it get broken then fixed? I ran
> make update and make world just thursday.
The bug in pci.c 1.116 only affected pnp cards so perhaps you have another
problem. If so, you need to try to work with Cameron G
ote:
>
> > +[ Doug Rabson ]-
> > | On Sat, 4 Sep 1999, Andrew Kenneth Milton wrote:
> > |
> > | > +[ Arthur H. Johnson II ]-----
> > | > | I fixed the sound card problem I
On Sun, 5 Sep 1999, Andrew Kenneth Milton wrote:
> +[ Doug Rabson ]-
> | On Sat, 4 Sep 1999, Andrew Kenneth Milton wrote:
> |
> | > +[ Arthur H. Johnson II ]-
> | > | I fixed the
ton wrote:
>
> > +[ Arthur H. Johnson II ]-
> > | I fixed the sound card problem I was having. I just commented out the pnp
> > | driver. I know I will run into problems later if I ever get pnp devices,
> > | but its
+[ Doug Rabson ]-
| On Sat, 4 Sep 1999, Andrew Kenneth Milton wrote:
|
| > +[ Arthur H. Johnson II ]-
| > | I fixed the sound card problem I was having. I just commented out the pnp
| > | d
On Sat, 4 Sep 1999, Andrew Kenneth Milton wrote:
> +[ Arthur H. Johnson II ]-
> | I fixed the sound card problem I was having. I just commented out the pnp
> | driver. I know I will run into problems later if I ever get pnp devices,
>
+[ Arthur H. Johnson II ]-
| I fixed the sound card problem I was having. I just commented out the pnp
| driver. I know I will run into problems later if I ever get pnp devices,
| but its a temporary fix.
Pcm doesn't work for me anymore wi
"Andrew Reilly" wrote:
> On Fri, Sep 03, 1999 at 09:08:59PM +0100, Doug Rabson wrote:
> > This is no longer necessary (in fact it causes much confusion for the
> > driver). The correct declaration for a pnp soundcard is 'device pcm0'.
>
> How do you set flags for particular cards, now? I used to
On Fri, Sep 03, 1999 at 09:08:59PM +0100, Doug Rabson wrote:
> This is no longer necessary (in fact it causes much confusion for the
> driver). The correct declaration for a pnp soundcard is 'device pcm0'.
How do you set flags for particular cards, now? I used to have
to use the flags option to
Arthur H. Johnson II
http://www.linuxberg.com
Linuxberg Manager
[EMAIL PROTECTED]
On Fri, 3 Sep 1999, Doug Rabson wrote:
> On Fri, 3 Sep 1999, Arthur H. Johnson II wrote:
>
> > Okay.
> >
> > Arthur H. Johnson II
> > http://www.linuxberg.com
> > Linuxberg Manager
> > [EMAIL PROTECTED]
>
> No
On Fri, 3 Sep 1999, Ollivier Robert wrote:
> According to Arthur H. Johnson II:
> > I fixed the sound card problem I was having. I just commented out the pnp
> > driver. I know I will run into problems later if I ever get pnp devices,
> > but its a temporary fix.
>
>
On Fri, 3 Sep 1999, Arthur H. Johnson II wrote:
> Okay.
>
> Arthur H. Johnson II
> http://www.linuxberg.com
> Linuxberg Manager
> [EMAIL PROTECTED]
Now I'm really confused. It looks like you have an explicit line for the
soundcard in your config (e.g. "device pcm0 at isa? port ? ...") but the
c
Okay.
Arthur H. Johnson II
http://www.linuxberg.com
Linuxberg Manager
[EMAIL PROTECTED]
On Fri, 3 Sep 1999, Doug Rabson wrote:
> On Fri, 3 Sep 1999, Arthur H. Johnson II wrote:
>
> > Well, I got rid of the old Voxware drivers and went with the pnp drivers
> > and still nothing. Here is the dm
I tried using snd1.
Arthur H. Johnson II
http://www.linuxberg.com
Linuxberg Manager
[EMAIL PROTECTED]
On Fri, 3 Sep 1999, Ollivier Robert wrote:
> According to Arthur H. Johnson II:
> > I fixed the sound card problem I was having. I just commented out the pnp
> > driver. I
According to Arthur H. Johnson II:
> I fixed the sound card problem I was having. I just commented out the pnp
> driver. I know I will run into problems later if I ever get pnp devices,
> but its a temporary fix.
Something to remember: if you have both pcm0 and pnp, then it will be
On Fri, 3 Sep 1999, Arthur H. Johnson II wrote:
> Well, I got rid of the old Voxware drivers and went with the pnp drivers
> and still nothing. Here is the dmesg:
> --
> pcm0: at port 0x220-0x22f irq 5 drq 5 flags 0x15 on isa0
> unknown0: on isa0
> unknown1: at port 0x240-0x24f,0x300-0x301,0x
Well, i recompiled with the Voxware drivers and commented out the pnp0
device, and now it works.
Arthur H. Johnson II
http://www.linuxberg.com
Linuxberg Manager
[EMAIL PROTECTED]
On Fri, 3 Sep 1999, Mike Hoskins wrote:
> On Fri, 3 Sep 1999, Arthur H. Johnson II wrote:
>
> > That didnt work. W
On Fri, 3 Sep 1999, Arthur H. Johnson II wrote:
> That didnt work. When I ran mpg123 it said can't access /dev/dsp but the
> mixer worked. And yes, i did run makedev.
What are the permissions on /dev/dsp*? Are other deamons running that are
attempting to access /dev/dsp? As an example, I ran
That didnt work. When I ran mpg123 it said can't access /dev/dsp but the
mixer worked. And yes, i did run makedev.
Arthur H. Johnson II
http://www.linuxberg.com
Linuxberg Manager
[EMAIL PROTECTED]
On Fri, 3 Sep 1999, Sheldon Hearn wrote:
>
>
> On Fri, 03 Sep 1999 11:27:55 -0400, "Arthur H.
On Fri, 03 Sep 1999 11:27:55 -0400, "Arthur H. Johnson II" wrote:
> Well, I got rid of the old Voxware drivers and went with the pnp drivers
> and still nothing. Here is the dmesg:
What does "still nothing" mean? I can't see anything in your e-mail
message which indicates what you're doing to
I fixed the sound card problem I was having. I just commented out the pnp
driver. I know I will run into problems later if I ever get pnp devices,
but its a temporary fix.
Arthur H. Johnson II
http://www.linuxberg.com
Linuxberg Manager
[EMAIL PROTECTED]
To Unsubscribe: send mail to [EMAIL
Well, I got rid of the old Voxware drivers and went with the pnp drivers
and still nothing. Here is the 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 #
On Fri, 3 Sep 1999, Nick Hibma wrote:
>
> What about documenting what you do here? It's not quite obvious to me
> why the dev is not the parent of the child in some cases.
It may be a great-grandchild. For instance in this case, the child is
isab0, the grandchild is isa0 and the great-grandchil
What about documenting what you do here? It's not quite obvious to me
why the dev is not the parent of the child in some cases.
Cheers,
Nick
> pcicfgregs *cfg = &dinfo->cfg;
> +int passthrough = (device_get_parent(child) != dev);
> int map = 0;
--
ISIS/STA, T.P.270, Joint Re
On Thu, 2 Sep 1999, Ollivier Robert wrote:
> According to Doug Rabson:
> > changing over to the pcm driver. Since your card is a PnP one, you should
> > be able to put just "device pcm0" in your kernel config.
>
> Even for ISA ones ? I though only PCI sound cards let you use the shorter
> form..
On Thu, 2 Sep 1999, Luoqi Chen wrote:
> > That's exactly what I have. This is just so weird. I am now reading the
> > debug register chapter of intel's manual, it is virtually impossible to
> > pinpoint the location by single-stepping through the code...
> >
> The debug register trick worked, an
> That's exactly what I have. This is just so weird. I am now reading the
> debug register chapter of intel's manual, it is virtually impossible to
> pinpoint the location by single-stepping through the code...
>
The debug register trick worked, and the discovery was quite unexpected:
because the
According to Doug Rabson:
> changing over to the pcm driver. Since your card is a PnP one, you should
> be able to put just "device pcm0" in your kernel config.
Even for ISA ones ? I though only PCI sound cards let you use the shorter
form...
--
Ollivier ROBERT -=- FreeBSD: The Power to Serve! -
> > I too have problems with my on board CS4236 sound chip and it is of a very
> > strange nature: in the new isa pnp code, function isa_assign_resources()
> > mysteriously overwrites the isa_device structure and sets logical_id to 0,
> > and as a result subsequent probe would not recognize it any
On Thu, 2 Sep 1999, Luoqi Chen wrote:
> > Could you send the output of dmesg. It could be that your BIOS has
> > rearranged the irq settings and has put another card on that IRQ. Is the
> > sound card PNP? If not, could you check that the card's IRQ is marked as
On Thu, 2 Sep 1999, Arthur H. Johnson II wrote:
> here it is:
> sb0 at port 0x220 irq 5 drq 1 on isa0
> snd0:
> sbxvi0 at port 0x drq 5 on isa0
> isa_compat: didn't get ports for sbxvi
> snd0:
> WARNING: "snd" is usurping "snd"'s cdevsw[]
> unknown0: on isa0
> unknown1: at port 0x
> Could you send the output of dmesg. It could be that your BIOS has
> rearranged the irq settings and has put another card on that IRQ. Is the
> sound card PNP? If not, could you check that the card's IRQ is marked as
> legacy in the BIOS?
>
> Nick
>
> > My sou
Manager
[EMAIL PROTECTED]
On Thu, 2 Sep 1999, Nick Hibma wrote:
>
> Could you send the output of dmesg. It could be that your BIOS has
> rearranged the irq settings and has put another card on that IRQ. Is the
> sound card PNP? If not, could you check that the card's IRQ is marke
Could you send the output of dmesg. It could be that your BIOS has
rearranged the irq settings and has put another card on that IRQ. Is the
sound card PNP? If not, could you check that the card's IRQ is marked as
legacy in the BIOS?
Nick
> My sound card used to work, and with a backu
My sound card used to work, and with a backup kernel it still did ( I lost
it ) but after doing a make update world yesturday I came to the
realization that it no longer works. Did someone break the sb drivers? I
get a drq / irq conflict error, but they are set to the sound card's
set
Dose anybody install sound card Diamond Monster Sound II (based on Aurel
VORTEX chipset) and make it propertly work ?
Tell me how you did it, pls!
--
Mike Ju. Volkov AKA Commander
Greetings,
I also have a Creative Labs Sound Blaster PCI128 installed, and though I
followed your instructions below I am not havine what I would call
promising results.
At 12:21 PM 1/10/99 +0100, Luigi Rizzo wrote:
>you need a -current system with the "pcm" device, then
I am running 3.1-STAB
Is the SB PCI 128 supported yet in -current. I new a new sound card and I
really would like a 'real' Sound balster.
On Fri, 15 Jan 1999, Satoshi Asami wrote:
> * From: br...@worldcontrol.com
>
> * So I am now mostly back the square 1. I'm still using an old GUS MAX
entral Computer www.centralcomputer.com.
> They are close to where I work.
>
>AXRA 16 Yamaha 719 3D Sound...$15.95
>J-Bond MF-719 Yamaha 3D OPL-3 w Midi..$36
> ESS 16 IDE 3D Sound Card..$14
>Television:TeleSound
> Eventhough, Voxware was reinstated, I diligently went about finding
> a "Luigi-Approved" sound card.
>
> After weeks of research I came to the conclusion that the
> 'Aopen AW 37 Pro' was the card of choice.
...
> And I have no idea what modern card wil
* From: br...@worldcontrol.com
* So I am now mostly back the square 1. I'm still using an old GUS MAX,
* which at the whim of FreeBSD-core may suddenly stop working.
Just one point -- the axing of voxware was *not* approved by
FreeBSD-core, and that's why it has been brought back.
Satoshi
T
1 - 100 of 101 matches
Mail list logo
