Garrett Wollman <[EMAIL PROTECTED]> writes:
> The ``can't assign resources'' messages indicate that the devices are
> legacy ISA devices for which a non-PnP-aware driver is compiled into
> the kernel.
Wrong.
> If it didn't say ``can't assign resources'', then *and only then* is
> the device in q
In message <[EMAIL PROTECTED]> Garrett Wollman writes:
: < said:
:
: > Actually, it is a bug. The drivers in the tree should grok these pnp
: > ids.
:
: Actually, no, it is not a bug. The FreeBSD drivers for these devices
: manage their resources differently from the way the Windows drivers
:
> < said:
>
> > Actually, it is a bug. The drivers in the tree should grok these pnp
> > ids.
>
> Actually, no, it is not a bug. The FreeBSD drivers for these devices
> manage their resources differently from the way the Windows drivers
> do, and the result is not unexpected if you look closel
< said:
> Actually, it is a bug. The drivers in the tree should grok these pnp
> ids.
Actually, no, it is not a bug. The FreeBSD drivers for these devices
manage their resources differently from the way the Windows drivers
do, and the result is not unexpected if you look closely at the dump
in
> < said:
>
> > This is not a bug. This is an FAQ. So much that it's actually
> > documented in (*gasp!*) the FAQ:
>
> Unfortunately, the A in the FAQ is wrong.
>
> The ``can't assign resources'' messages indicate that the devices are
> legacy ISA devices for which a non-PnP-aware driver is c
In message <[EMAIL PROTECTED]> John Baldwin writes:
:
: On 25-Apr-01 Warner Losh wrote:
: > In message <[EMAIL PROTECTED]> Dima Dorfman
: > writes:
: >: Riccardo Torrini <[EMAIL PROTECTED]> writes:
: >: > pca1: at port 0x61 on isa0
: >: > WARNING: Driver mistake: repeat make_dev("pcaudio")
:
On 25-Apr-01 Warner Losh wrote:
> In message <[EMAIL PROTECTED]> Dima Dorfman
> writes:
>: Riccardo Torrini <[EMAIL PROTECTED]> writes:
>: > pca1: at port 0x61 on isa0
>: > WARNING: Driver mistake: repeat make_dev("pcaudio")
>: > WARNING: Driver mistake: repeat make_dev("pcaudioctl")
>:
>
In message <[EMAIL PROTECTED]> Dima Dorfman writes:
: Riccardo Torrini <[EMAIL PROTECTED]> writes:
: > pca1: at port 0x61 on isa0
: > WARNING: Driver mistake: repeat make_dev("pcaudio")
: > WARNING: Driver mistake: repeat make_dev("pcaudioctl")
:
: As it says, this is a driver mistake. It
<
said:
> This means that I can remove this lines? Sure?
> device atkbdc 1
No, I said nothing of the sort.
-GAWollman
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message
On 25-Apr-01 (01:31:59/GMT) Garrett Wollman wrote:
> The ``can't assign resources'' messages indicate that the
> devices are legacy ISA devices for which a non-PnP-aware
> driver is compiled into the kernel. These include devices
> such as keyboard...
This means that I can remove this lines? S
[Followups to -questions, please.]
<
said:
> unknown: can't assign resources
Keyboard controller.
> unknown: can't assign resources
PS/2 mouse port.
> unknown: can't assign resources
Serial port whose settings conflict with one of your configured serial
ports.
> unknown: can't assign
< said:
> This is not a bug. This is an FAQ. So much that it's actually
> documented in (*gasp!*) the FAQ:
Unfortunately, the A in the FAQ is wrong.
The ``can't assign resources'' messages indicate that the devices are
legacy ISA devices for which a non-PnP-aware driver is compiled into
the k
On 24-Apr-01 (23:19:59/GMT) Dima Dorfman wrote:
>> WARNING: Driver mistake: repeat make_dev("pcaudio")
>> WARNING: Driver mistake: repeat make_dev("pcaudioctl")
> As it says, this is a driver mistake. It's a bug.
Ok. It happens from first days of devfs. I'm looking into
gnats but there i
Riccardo Torrini <[EMAIL PROTECTED]> writes:
> pca1: at port 0x61 on isa0
> WARNING: Driver mistake: repeat make_dev("pcaudio")
> WARNING: Driver mistake: repeat make_dev("pcaudioctl")
As it says, this is a driver mistake. It's a bug. I don't know if
it's new or not since I don't have an
-On [2119 08:00], Warner Losh ([EMAIL PROTECTED]) wrote:
>In message <[EMAIL PROTECTED]> Chris Piazza writes:
>: I *thought* I noticed it was different. I actually find this pretty
>: annoying because it wraps almost all of the lines and makes it difficult
>: to read dmesg.
>
>I don't mind th
> On Wed, Jan 19, 2000 at 12:28:09AM +0100, Poul-Henning Kamp wrote:
> > fxp0: port 0xc400-0xc43f mem
>0xefe0-0xefef,0xe000-0xefff irq 9 at device 14.0 on pci0
>
> Agreed. For a PCI card all I want to know is what it is, and what IRQ it
> was assigned. A single line should be
On Wed, 19 Jan 2000, David Scheidt wrote:
> On Wed, 19 Jan 2000, Andrzej Bialecki wrote:
>
> >
> > I did some hacks a while ago on a tool which could be called "devinfo". It
> > simply traversed the dev/bus tree and displayed tons of info about each
> > node.
> >
> > Perhaps something like tha
On Wed, 19 Jan 2000, Andrzej Bialecki wrote:
>
> I did some hacks a while ago on a tool which could be called "devinfo". It
> simply traversed the dev/bus tree and displayed tons of info about each
> node.
>
> Perhaps something like that could be useful instead of full-blown FS?
This is somet
On Tue, 18 Jan 2000, Matthew N. Dodd wrote:
> On Wed, 19 Jan 2000, Poul-Henning Kamp wrote:
> > fxp0: port 0xc400-0xc43f mem
>0xefe0-0xefef,0xe000-0xefff irq 9 at device 14.0 on pci0
> >
> > Is this level of verbosity really helping anybody ?
>
> Its consistant, but I need to
> The IRQ is useful to me at least, since the ISA/PCI irq distribution is
> rather hackish and non-trivial to get right at times.
Note that I'm not saying that IRQ is not useful - I'm just asking whether it's
important to see when bootverbose == 0.
To Unsubscribe: send mail to [EMAIL PROTECT
In message <[EMAIL PROTECTED]>, Matthew
Jacob writes:
>
>
>> On Wed, Jan 19, 2000 at 12:28:09AM +0100, Poul-Henning Kamp wrote:
>> > fxp0: port 0xc400-0xc43f mem
>0xefe0-0xefef,0xe000-0xefff irq 9 at device 14.0 on pci0
>>
>> Agreed. For a PCI card all I want to know is what i
In message <[EMAIL PROTECTED]> Chris Piazza writes:
: I *thought* I noticed it was different. I actually find this pretty
: annoying because it wraps almost all of the lines and makes it difficult
: to read dmesg.
I don't mind them, but wouldn't object to a generic wrapping
mechanism.
Warner
On Tue, 18 Jan 2000, David O'Brien wrote:
> On Tue, Jan 18, 2000 at 06:10:00PM -0800, Matthew Jacob wrote:
> > > Agreed. For a PCI card all I want to know is what it is, and what IRQ it
> > > was assigned. A single line should be suffient.
> >
> > Do you even need to know what IRQ it was assig
>
> What would be nice would be to have the normal version displayed and
> the verbose stuff go to a seperate buffer and logged seperatly..
>
> ie so you don't clutter your boot screen with junk, but if you have a
> problem you can get at the verbose info :)
>
> .. and no I don't have any patc
On Tue, Jan 18, 2000 at 06:10:00PM -0800, Matthew Jacob wrote:
> > Agreed. For a PCI card all I want to know is what it is, and what IRQ it
> > was assigned. A single line should be suffient.
>
> Do you even need to know what IRQ it was assigned? It seems to me that IRQ,
With wacky PC hardwar
On 19-Jan-00 Matthew Jacob wrote:
> Do you even need to know what IRQ it was assigned? It seems to me
> that IRQ,
> like IO-PORT, is only needed if you're either interested in such
> stuff or to
> catch conflicts (both are under bootverbose)
What would be nice would be to have the normal ve
> On Wed, Jan 19, 2000 at 12:28:09AM +0100, Poul-Henning Kamp wrote:
> > fxp0: port 0xc400-0xc43f mem
>0xefe0-0xefef,0xe000-0xefff irq 9 at device 14.0 on pci0
>
> Agreed. For a PCI card all I want to know is what it is, and what IRQ it
> was assigned. A single line should b
On Wed, Jan 19, 2000 at 12:28:09AM +0100, Poul-Henning Kamp wrote:
> fxp0: port 0xc400-0xc43f mem
>0xefe0-0xefef,0xe000-0xefff irq 9 at device 14.0 on pci0
Agreed. For a PCI card all I want to know is what it is, and what IRQ it
was assigned. A single line should be suffient.
>
> fxp0: port 0xc400-0xc43f mem
>0xefe0-0xefef,0xe000-0xefff irq 9 at device 14.0 on pci0
>
> Is this level of verbosity really helping anybody ?
>
> I thought we printed out the port/mem stuff for ISA because it is
> usually jumpered by the admin, but for dynamic allocation
On Wed, Jan 19, 2000 at 12:28:09AM +0100, Poul-Henning Kamp wrote:
>
> fxp0: port 0xc400-0xc43f mem
>0xefe0-0xefef,0xe000-0xefff irq 9 at device 14.0 on pci0
>
> Is this level of verbosity really helping anybody ?
I *thought* I noticed it was different. I actually find this p
On Wed, 19 Jan 2000, Poul-Henning Kamp wrote:
> fxp0: port 0xc400-0xc43f mem
>0xefe0-0xefef,0xe000-0xefff irq 9 at device 14.0 on pci0
>
> Is this level of verbosity really helping anybody ?
Its consistant, but I need to unify all the resource printing stuff since
theres about
31 matches
Mail list logo
