On Wed, Feb 17, 2016 at 09:19:07PM +0900, SAITOH Masanobu wrote:
> > Very long shot: maybe try "options NO_PCI_EXTENDED_CONFIG" ?
>
> He said he was using 7.0. The PCI extende configration support
> for x86 is only in -curret.
Right I did not find an option like that. May be I should file a PR.
On 2016/02/17 20:04, Patrick Welche wrote:
> On Wed, Feb 17, 2016 at 07:55:57AM +0530, Mayuresh wrote:
>> On Mon, Feb 15, 2016 at 10:10:16PM +0530, Mayuresh wrote:
>>> I realize, with acpi enabled even ethernet interface wasn't getting
>>> created either, which got created with acpi disabled.
>>
>>
On Wed, Feb 17, 2016 at 07:55:57AM +0530, Mayuresh wrote:
> On Mon, Feb 15, 2016 at 10:10:16PM +0530, Mayuresh wrote:
> > I realize, with acpi enabled even ethernet interface wasn't getting
> > created either, which got created with acpi disabled.
>
> Request some inputs on this.
>
> How should o
On Wed, Feb 17, 2016 at 07:55:57AM +0530, Mayuresh wrote:
> On Mon, Feb 15, 2016 at 10:10:16PM +0530, Mayuresh wrote:
> > I realize, with acpi enabled even ethernet interface wasn't getting
> > created either, which got created with acpi disabled.
>
> Request some inputs on this.
We need an x86 e
On Mon, Feb 15, 2016 at 10:10:16PM +0530, Mayuresh wrote:
> I realize, with acpi enabled even ethernet interface wasn't getting
> created either, which got created with acpi disabled.
Request some inputs on this.
How should one go about this when some hardware does not work with acpi
(other than
On Sun, Feb 14, 2016 at 11:14:42AM +0530, Mayuresh wrote:
> I have an old laptop where I am trying out NetBSD 7.0 i386.
>
> Get the following information about the wifi device:
>
> #dmesg | grep ath0
> ath0 at pci2 dev 0 function 0: Atheros 5424/2424
> ath0: cannot map register space
>
> Interfa
