public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Adam Belay <ambx1@neo.rr.com>
To: Adrian Bunk <bunk@fs.tum.de>
Cc: Kernel Mailing List <linux-kernel@vger.kernel.org>, perex@suse.cz
Subject: Re: 2.5.73: ALSA ISA pnp_init_resource_table compile errors
Date: Tue, 15 Jul 2003 22:47:32 +0000	[thread overview]
Message-ID: <20030715224732.GA31942@neo.rr.com> (raw)
In-Reply-To: <20030704121124.GB12633@fs.tum.de>

On Fri, Jul 04, 2003 at 02:11:24PM +0200, Adrian Bunk wrote:
> On Thu, Jul 03, 2003 at 07:03:04PM +0000, Adam Belay wrote:
> > Some of my recent patches may correct this issue.  If not, it may be
> > an unresolvable resource conflict.  Try catting
>
> the dmesg output looks better, but it still doesn't work:

Hi Adrian,

Sorry for the delayed response.

> Advanced Linux Sound Architecture Driver Version 0.9.4 (Mon Jun 09 12:01:18 2003 UTC).
> request_module: failed /sbin/modprobe -- snd-card-0. error = -16specify port
> pnp: the driver 'ad1816a' has been registered
> pnp: match found with the PnP device '01:01.00' and the driver 'ad1816a'
> pnp: match found with the PnP device '01:01.01' and the driver 'ad1816a'
> pnp: Device 01:01.00 activated.
> pnp: Device 01:01.01 activated.
> ALSA device list:
>   No soundcards found.
>
> <--  snip  -->
>
> This problem is hopefully not unresolvable, the card works fine
> with ISAPNP with both kernel 2.4 and kernel 2.5 <= 2.5.72 .

Because activation was successful, it looks like its a bug instead of a
conflict.

>
> # cat /sys/bus/pnp/devices/01\:01.01/options

> # cat /sys/bus/pnp/devices/01\:01.01/resources

Could I see the output for 01:01.00/options and 01:01.00/resources also,
perhaps it will provide some insight.  I'm guessing the resources may be
incorrect in that node.

Thanks,
Adam

  reply	other threads:[~2003-07-16  3:03 UTC|newest]

Thread overview: 32+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-06-22 18:53 Linux 2.5.73 Linus Torvalds
2003-06-22 20:06 ` Alex Goddard
2003-06-22 20:15   ` Andrew Morton
2003-06-22 22:53     ` Greg KH
2003-06-22 23:31       ` Andrew Morton
2003-06-22 20:46 ` Florin Iucha
2003-06-22 21:17   ` Alex Goddard
2003-06-22 21:45     ` Alex Goddard
2003-06-22 21:58     ` Alex Goddard
2003-06-23  2:52       ` Greg KH
2003-06-22 23:44 ` 2.5.73: ALSA ISA pnp_init_resource_table compile errors Adrian Bunk
2003-06-23  0:08   ` Adam Belay
2003-07-03  2:53     ` Adrian Bunk
2003-07-03 19:03       ` Adam Belay
2003-07-04 12:11         ` Adrian Bunk
2003-07-15 22:47           ` Adam Belay [this message]
2003-07-16 18:22             ` Adrian Bunk
2003-07-16 18:43               ` Adam Belay
2003-07-19 22:03                 ` Adrian Bunk
2003-07-20  5:59                 ` Jochen Hein
2003-08-09 20:40                 ` Adrian Bunk
2003-06-23  0:31 ` 2.5.73: acorn.c compile error Adrian Bunk
2003-06-23 10:13 ` Linux 2.5.73 - Won't compile using oldconfig - config attached vlad
2003-07-02 14:31   ` John Covici
2003-07-02 16:38     ` Greg KH
2003-06-23 20:32 ` Linux 2.5.73 - keyboard failure, repost no. 3 Terje Fåberg
2003-06-26 20:45   ` Vojtech Pavlik
2003-06-27 14:22     ` Terje Fåberg
2003-06-27 19:03       ` Vojtech Pavlik
2003-06-28  9:11         ` Terje Fåberg
2003-06-28  9:37           ` Vojtech Pavlik
2003-06-28 11:40             ` Terje Fåberg

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20030715224732.GA31942@neo.rr.com \
    --to=ambx1@neo.rr.com \
    --cc=bunk@fs.tum.de \
    --cc=linux-kernel@vger.kernel.org \
    --cc=perex@suse.cz \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox