Steven M. Bellovin | 1 Feb 01:03 2006

Re: npx0 not attaching with ACPI

In message <68127C07-04BC-48A1-9E55-53E00E716915 <at> dtcc.edu>, Chris Tribo writes:
>
>Now I get:
>
>npx0 at acpi0 (PNP0C02-31)
>npx0: io 0x10-0x1f,0x24-0x25,0x28-0x29,0x2c-0x2d, 
>0x30-0x31,0x34-0x35,-0x38-0x39.......
>npx0: unable to find irq resource
>
>

Very strange.  I checked five different machines, using four different 
motherboards.  Three are running 3.0; two are running -current.  All 
showed

$ dmesg|grep npx
npx0 at acpi0 (PNP0C04)
npx0: io 0xf0-0xff irq 13
npx0: using exception 16

		--Steven M. Bellovin, http://www.cs.columbia.edu/~smb

Rui Paulo | 1 Feb 01:11 2006
Picon

Re: npx0 not attaching with ACPI

Chris Tribo <ctribo <at> dtcc.edu> writes:

> Now I get:
>
> npx0 at acpi0 (PNP0C02-31)
> npx0: io 0x10-0x1f,0x24-0x25,0x28-0x29,0x2c-0x2d,
> 0x30-0x31,0x34-0x35,-0x38-0x39.......
> npx0: unable to find irq resource

Ok, that's clearly not the correct one. :-)
I don't think you will be able to use npx at acpi, but I could be
wrong.
Do you have Windows installed ? If so, is it able to find npx at ACPI
?

--

-- 
Rui Paulo - rpaulo <at> fnop.net

Ian Zagorskih | 1 Feb 01:12 2006

Re: npx0 not attaching with ACPI

> Not having an fpu is killing awk, which is kinda a big deal :)
> Any idea why it works fine for non ACPI kernels?
>
> atapibus0 at atabus1: 2 targets
> cd0 at atapibus0 drive 0: <VMware Virtual IDE CDROM Drive,
> 1000000000000000000, 0000000> cdrom removable
> cd0: 32-bit data port
> cd0: drive supports PIO mode 4, DMA mode 2, Ultra-DMA mode 2 (Ultra/33)
> cd0(piixide0:1:0): using PIO mode 4, Ultra-DMA mode 2 (Ultra/33)
> (using DMA)

Are you running it under VMware? Probably here's the root of problem?

// wbr

Chris Tribo | 1 Feb 01:18 2006

Re: npx0 not attaching with ACPI

Yes it's VMware 5.5 which mostly emulates a Intel 443BX motherboard.  
What does the math coprocessor have to do with the ide controller?

On Jan 31, 2006, at 7:12 PM, Ian Zagorskih wrote:

>> Not having an fpu is killing awk, which is kinda a big deal :)
>> Any idea why it works fine for non ACPI kernels?
>>
>> atapibus0 at atabus1: 2 targets
>> cd0 at atapibus0 drive 0: <VMware Virtual IDE CDROM Drive,
>> 1000000000000000000, 0000000> cdrom removable
>> cd0: 32-bit data port
>> cd0: drive supports PIO mode 4, DMA mode 2, Ultra-DMA mode 2  
>> (Ultra/33)
>> cd0(piixide0:1:0): using PIO mode 4, Ultra-DMA mode 2 (Ultra/33)
>> (using DMA)
>
> Are you running it under VMware? Probably here's the root of problem?
>
> // wbr
>
> !DSPAM:43dffd0b198646314088078!
>
>
>

Hisashi T Fujinaka | 1 Feb 01:19 2006

Re: current isn't building for me (part of the byte swap thing)

On Tue, 31 Jan 2006, David Laight wrote:

> On Mon, Jan 30, 2006 at 09:20:06PM -0800, Hisashi T Fujinaka wrote:
>> I think this is part of the byte swap thing.
> ....
>> /usr/src/common/lib/libc/gen/bswap64.c: In function `bswap64':
>> /usr/src/common/lib/libc/gen/bswap64.c:41: warning: implicit declaration of
>> function `__byte_swap_long'
>
> I committed a few more header files this morning - they probably fixed this.
> Certainly i386 and amd64 builds succeed in my local tree.

Thanks. Now I have to figure out why XEN0 is barfing on me. :)

--

-- 
Hisashi T Fujinaka - htodd <at> twofifty.com
BSEE(6/86) + BSChem(3/95) + BAEnglish(8/95) + MSCS(8/03) + $2.50 = latte

Rui Paulo | 1 Feb 01:15 2006
Picon

Re: npx0 not attaching with ACPI

Ian Zagorskih <ianzag <at> megasignal.com> writes:

>> Not having an fpu is killing awk, which is kinda a big deal :)
>> Any idea why it works fine for non ACPI kernels?
>>
>> atapibus0 at atabus1: 2 targets
>> cd0 at atapibus0 drive 0: <VMware Virtual IDE CDROM Drive,
>> 1000000000000000000, 0000000> cdrom removable
>> cd0: 32-bit data port
>> cd0: drive supports PIO mode 4, DMA mode 2, Ultra-DMA mode 2 (Ultra/33)
>> cd0(piixide0:1:0): using PIO mode 4, Ultra-DMA mode 2 (Ultra/33)
>> (using DMA)
>
> Are you running it under VMware? Probably here's the root of problem?

Oh, my eyes didn't catch this..
Yup., I guess you will be unable to use npx at acpi under vmware but
there's no harm in using npx at isa or pnpbios.

--

-- 
Rui Paulo - rpaulo <at> fnop.net

Ian Zagorskih | 1 Feb 01:22 2006

Re: npx0 not attaching with ACPI

> Yes it's VMware 5.5 which mostly emulates a Intel 443BX motherboard.
> What does the math coprocessor have to do with the ide controller?
>

Really don't know, probably it does not emulates your hdw well enough, who 
knows. Can you boot same NetBSD on this machine in a real environment?

// wbr

Chris Tribo | 1 Feb 01:41 2006

Re: npx0 not attaching with ACPI

Hmm, I just looked at what windows does, and all the legacy ISA stuff  
shows up as children of this:

PNP0A05 [Generic ACPI Bus] at acpi0 not configured

Specifically com1, com2, lpt1, the fdc and fd, but anyway, thanks for  
looking.

On Jan 31, 2006, at 7:15 PM, Rui Paulo wrote:

> Ian Zagorskih <ianzag <at> megasignal.com> writes:
>
>>> Not having an fpu is killing awk, which is kinda a big deal :)
>>> Any idea why it works fine for non ACPI kernels?
>>>
>>> atapibus0 at atabus1: 2 targets
>>> cd0 at atapibus0 drive 0: <VMware Virtual IDE CDROM Drive,
>>> 1000000000000000000, 0000000> cdrom removable
>>> cd0: 32-bit data port
>>> cd0: drive supports PIO mode 4, DMA mode 2, Ultra-DMA mode 2  
>>> (Ultra/33)
>>> cd0(piixide0:1:0): using PIO mode 4, Ultra-DMA mode 2 (Ultra/33)
>>> (using DMA)
>>
>> Are you running it under VMware? Probably here's the root of problem?
>
> Oh, my eyes didn't catch this..
> Yup., I guess you will be unable to use npx at acpi under vmware but
> there's no harm in using npx at isa or pnpbios.
>
(Continue reading)

NetBSD source update | 1 Feb 01:42 2006
Picon

triweekly CVS update output


Updating release-1-6 src tree (netbsd-1-6):

Running the SUP scanner:
SUP Scan for release-1-6 starting at Wed Feb  1 00:09:32 2006
SUP Scan for release-1-6 completed at Wed Feb  1 00:10:10 2006

Updating release-2-0 src tree (netbsd-2-0):

Running the SUP scanner:
SUP Scan for release-2-0 starting at Wed Feb  1 00:17:17 2006
SUP Scan for release-2-0 completed at Wed Feb  1 00:18:33 2006

Updating release-2-1 src tree (netbsd-2-1):

Running the SUP scanner:
SUP Scan for release-2-1 starting at Wed Feb  1 00:30:11 2006
SUP Scan for release-2-1 completed at Wed Feb  1 00:31:53 2006

Updating release-3-0 src tree (netbsd-3-0):
U src/doc/CHANGES-3.0.1
P src/sys/arch/hp300/stand/common/ite_dv.c
P src/sys/arch/hp300/stand/common/ite_gb.c
P src/sys/arch/hp300/stand/common/ite_hy.c
P src/sys/arch/hp300/stand/common/ite_rb.c
P src/sys/arch/hp300/stand/common/ite_tc.c

Running the SUP scanner:
SUP Scan for release-3-0 starting at Wed Feb  1 00:41:18 2006
SUP Scan for release-3-0 completed at Wed Feb  1 00:42:55 2006
(Continue reading)

Quentin Garnier | 1 Feb 02:10 2006
Picon

Re: npx0 not attaching with ACPI

On Tue, Jan 31, 2006 at 07:41:56PM -0500, Chris Tribo wrote:
> Hmm, I just looked at what windows does, and all the legacy ISA stuff  
> shows up as children of this:
> 
> PNP0A05 [Generic ACPI Bus] at acpi0 not configured
> 
> Specifically com1, com2, lpt1, the fdc and fd, but anyway, thanks for  
> looking.

Our current ACPI implementation consider the ACPI namespace flat, it has
no knowledge of the ACPI device tree (*sigh*).

Can you post the DSDT?  Or point me to a site where people already
extracted VMWare's DSDT?

--

-- 
Quentin Garnier - cube <at> cubidou.net - cube <at> NetBSD.org
"When I find the controls, I'll go where I like, I'll know where I want
to be, but maybe for now I'll stay right here on a silent sea."
KT Tunstall, Silent Sea, Eye to the Telescope, 2004.

Gmane