On Tue, 12 Oct 1999, Warner Losh wrote:
> In message <[EMAIL PROTECTED]> Doug
>Rabson writes:
> : Due to the nature of the pnp code, it might be probed as ed1 instead of
> : ed0.
>
> I have a SBC here that has an onboard PNP ne2000 chip on it. It comes
> up as ed1 because I have ed0 at a wired
In message <[EMAIL PROTECTED]> Doug Rabson
writes:
: Due to the nature of the pnp code, it might be probed as ed1 instead of
: ed0.
I have a SBC here that has an onboard PNP ne2000 chip on it. It comes
up as ed1 because I have ed0 at a wired address. I don't see ed0 at
all, and it just works,
On Mon, 11 Oct 1999, Doug Rabson wrote:
> I was looking at the Linux driver and I don't think it would be hard to
> use their algorithm to set the memory resource appropriately.
Looks pretty simple.
I'll take a crack at it tomorrow.
--
| Matthew N. Dodd | '78 Datsun 280Z | '75 Volvo 164E | F
On Sun, 10 Oct 1999, Matthew N. Dodd wrote:
> On Sun, 10 Oct 1999, Matthew N. Dodd wrote:
> > On Sun, 10 Oct 1999, Doug Rabson wrote:
> > > Your card is an SMC EtherEZ (8416). I think that needs some special
> > > extra tricks to get it supported. Matt Dodd <[EMAIL PROTECTED]> was
> > > working o
It worked when it was probed non-pnp :-).. As long as I set the params..
DId you get my email with pnpinfo and dmesg?
On Sun, 10 Oct 1999, Doug Rabson wrote:
> On Sun, 10 Oct 1999, Jason DiCioccio wrote:
>
> > Another note :) .. PnP also probes unknown0 on the wrong irq (irq 3) while
> > it sho
On Sun, 10 Oct 1999, Matthew N. Dodd wrote:
> On Sun, 10 Oct 1999, Doug Rabson wrote:
> > Your card is an SMC EtherEZ (8416). I think that needs some special
> > extra tricks to get it supported. Matt Dodd <[EMAIL PROTECTED]> was
> > working on this recently but I don't know if he has it working y
On Sun, 10 Oct 1999, Doug Rabson wrote:
> Your card is an SMC EtherEZ (8416). I think that needs some special
> extra tricks to get it supported. Matt Dodd <[EMAIL PROTECTED]> was
> working on this recently but I don't know if he has it working yet.
I've got uncommitted patches that fix this I be
On Sun, 10 Oct 1999, Jason DiCioccio wrote:
> Another note :) .. PnP also probes unknown0 on the wrong irq (irq 3) while
> it should be on irq 7
Actually, we can put the card on any irq which it supports as long as
there isn't a conflict. Unless you have a sio1 in that box (which normally
uses i
Another note :) .. PnP also probes unknown0 on the wrong irq (irq 3) while
it should be on irq 7
On Sun, 10 Oct 1999, Doug Rabson wrote:
> On Sun, 10 Oct 1999, Jason DiCioccio wrote:
>
> > Sorry I can't get pnpinfo, I can tell you though that dmesg does not even
> > show ed0 being probed at all
On Sun, 10 Oct 1999, Jason DiCioccio wrote:
> Sorry I can't get pnpinfo, I can tell you though that dmesg does not even
> show ed0 being probed at all.. In other words, it does nto even say 'ed0
> not found at 0x240' .. And I am not deleting the device :-).. Are there
> any conditions where this
Sorry I can't get pnpinfo, I can tell you though that dmesg does not even
show ed0 being probed at all.. In other words, it does nto even say 'ed0
not found at 0x240' .. And I am not deleting the device :-).. Are there
any conditions where this would happen?
Thanks
On Sun, 10 Oct 1999, Doug Rabs
On Sun, 10 Oct 1999, Jason DiCioccio wrote:
> I just tried the latest -CURRENT snapshot, 19991009 ,.. Now, on the old
> floppy, I could set the parameters for ed0 and it would find ed0.. now it
> doesn't find ed0 at all although it still finds 'unknown0' .. When you
> fixed this freezing, did thi
I just tried the latest -CURRENT snapshot, 19991009 ,.. Now, on the old
floppy, I could set the parameters for ed0 and it would find ed0.. now it
doesn't find ed0 at all although it still finds 'unknown0' .. When you
fixed this freezing, did this ruin some other detection or something to
that effe
as i've said, because it freezes my machine when it detects it PnP..
And, as you can imagine, I do not want my installation freezing on me :)
On Sun, 10 Oct 1999, Daniel C. Sobral wrote:
> Jason DiCioccio wrote:
> >
> > I use visual_userconfig set ed0 to 0x240 and irq 7 and it detects it
> >
Jason DiCioccio wrote:
>
> I use visual_userconfig set ed0 to 0x240 and irq 7 and it detects it
> I dont need the PnP probe on ISA bus.
Well, I don't need C, I could program in assembly language, but I
still think using C is easier.
I'm asking why do you *object* to your card being recognized
I shall try again :)
On Sat, 9 Oct 1999, Doug Rabson wrote:
> On Sat, 9 Oct 1999, Jason DiCioccio wrote:
>
> >
> > Yes yes.. Long subject, but anyhow.. The problem I am having is that 4.0
> > insists on detecting my ethernet card PnP at installation even though Id
> > ont want it to.. When it
I use visual_userconfig set ed0 to 0x240 and irq 7 and it detects it
I dont need the PnP probe on ISA bus.
On Sat, 9 Oct 1999, Daniel C. Sobral wrote:
> Jason DiCioccio wrote:
> >
> > Yes yes.. Long subject, but anyhow.. The problem I am having is that 4.0
> > insists on detecting my ethernet
Jason DiCioccio wrote:
>
> Yes yes.. Long subject, but anyhow.. The problem I am having is that 4.0
> insists on detecting my ethernet card PnP at installation even though Id
> ont want it to.. When it does, it freezes up, and its much easier for me
> just to input the settings manually info the
On Sat, 9 Oct 1999, Jason DiCioccio wrote:
>
> Yes yes.. Long subject, but anyhow.. The problem I am having is that 4.0
> insists on detecting my ethernet card PnP at installation even though Id
> ont want it to.. When it does, it freezes up, and its much easier for me
> just to input the settin
Yes yes.. Long subject, but anyhow.. The problem I am having is that 4.0
insists on detecting my ethernet card PnP at installation even though Id
ont want it to.. When it does, it freezes up, and its much easier for me
just to input the settings manually info the visual config.. I need to
disable
On Tue, 14 Sep 1999, Erik H. Bakke wrote:
> With the recent changes to the if_ed driver, it refuses to initialize my
> card.
> It reports:
> unknown0 at isa0
>
> >From debugging the probing it seems that the driver fails in
> ed_alloc_ports() returning ENOENT.
>
> Switching the BIOS settings to
With the recent changes to the if_ed driver, it refuses to initialize my
card.
It reports:
unknown0 at isa0
>From debugging the probing it seems that the driver fails in
ed_alloc_ports() returning ENOENT.
Switching the BIOS settings to and from PnP aware OS did not help.
Any suggestions?
The c
> 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
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
>> # pcm: Luigi's sound driver
>> #device pcm0 at isa? port ? irq 5 drq 1 flags 0x0
>> device pcm0
>> now, although pcm0 shows up in dmesg, i get
>> % xmix
>> Error opening mixer device /dev/mixer: Device not configured
>> and similar whinging. xmix wo
At 01:49 PM 09/07/99 -0700, Randy Bush wrote:
>i am in a similar position. so i did as you say.
>
> controller pnp0# PnP support for ISA
> ...
> # pcm: Luigi's sound driver
> #device pcm0 at isa? port ? irq 5 drq 1 flags 0x0
> device
On Tue, 7 Sep 1999, Randy Bush wrote:
> % xmix
> Error opening mixer device /dev/mixer: Device not configured
>
> and similar whinging. xmix worked before the change.
Did you remake your snd0 devices?
David
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-cu
>> 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 0x330 port2 0x388 irq0 5 drq0 1 drq1 5
[...]
> > What can I do in order to reenable my soundcard?
> >
> > Any help is appreciated!
>
> Please try using the new pcm driver if you are not already. You should be
> able to do this by having these lines in your kernel config:
>
> controller pnp0
> device pcm0
>
> Note that
On Mon, 6 Sep 1999, Thomas Schuerger wrote:
> Hi!
>
> 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
Hi!
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 0x330 port2 0x388 irq0 5 drq0 1 drq1 5
pnp 1 2 o
31 matches
Mail list logo
