[Qemu-devel] Unknown PCI Bridge

[Qemu-devel] Unknown PCI Bridge

[Chris Bagwell]

Hi all,

I upgraded to current CVS (0.8.1 plus a couple of patches like acpi).  
Last time I upgraded was about 1 week ago.

When I ran this version with a win98 guest, windows detected a new 
device called "PCI Bridge".  It was unable to find a driver for this on 
the win98 CD and placed it as not working in the "other devices" section 
of device manager.

Doesn't seem to harm anything.  I was guessing it had something to do 
with the acpi patches but haven't verified.  Any ideas?

Chris

Re: [Qemu-devel] Unknown PCI Bridge

[Fabrice Bellard]

Chris Bagwell wrote:
> Hi all,
> 
> I upgraded to current CVS (0.8.1 plus a couple of patches like acpi).  
> Last time I upgraded was about 1 week ago.
> 
> When I ran this version with a win98 guest, windows detected a new 
> device called "PCI Bridge".  It was unable to find a driver for this on 
> the win98 CD and placed it as not working in the "other devices" section 
> of device manager.
> 
> Doesn't seem to harm anything.  I was guessing it had something to do 
> with the acpi patches but haven't verified.  Any ideas?

Yes, ACPI adds a new PCI device so it is normal. I am interested by any 
regression found using the current CVS with ACPI...

Fabrice.

[Qemu-devel] Re: Unknown PCI Bridge

[Sven Köhler]

[-- Attachment #1: Type: text/plain, Size: 735 bytes --]

> Yes, ACPI adds a new PCI device so it is normal. I am interested by any
> regression found using the current CVS with ACPI...

I think, this answer is fairly useless for the OP.
So perhaps the OP wanted to ask: how do i tell my Win2k to properly use
the new PCI device?

I'm especially interested in this question: is qemu's current ACPI PCI
device so normal, that it would be recognized and properly used by a
newly installed Win2k?


qemu's ACPI PCI device doesn't seem to be _that_ normal/known. At least
a recent Knoppix lists it as "Bridge: Intel Corp.: Inknown device 7013".


BTW: how can i test ACPI with Linux?
At least "cat /proc/acpi/info" works fine and shows:
version: 20050309

Greetings
  Sven


[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 254 bytes --]

Re: [Qemu-devel] Re: Unknown PCI Bridge

[malc]

[-- Attachment #1: Type: TEXT/PLAIN, Size: 712 bytes --]

On Fri, 5 May 2006, Sven K?hler wrote:

>> Yes, ACPI adds a new PCI device so it is normal. I am interested by any
>> regression found using the current CVS with ACPI...
>
> I think, this answer is fairly useless for the OP.
> So perhaps the OP wanted to ask: how do i tell my Win2k to properly use
> the new PCI device?
>
> I'm especially interested in this question: is qemu's current ACPI PCI
> device so normal, that it would be recognized and properly used by a
> newly installed Win2k?
>
>
> qemu's ACPI PCI device doesn't seem to be _that_ normal/known. At least
> a recent Knoppix lists it as "Bridge: Intel Corp.: Inknown device 7013".
>

Wrong device id, should be 0x7113.

--
mailto:malc@pulsesoft.com

[-- Attachment #2: Type: TEXT/PLAIN, Size: 557 bytes --]

Index: hw/acpi.c
===================================================================
RCS file: /cvsroot/qemu/qemu/hw/acpi.c,v
retrieving revision 1.1
diff -u -r1.1 acpi.c
--- hw/acpi.c	3 May 2006 22:02:44 -0000	1.1
+++ hw/acpi.c	5 May 2006 12:25:49 -0000
@@ -234,7 +234,7 @@
     pci_conf[0x00] = 0x86;
     pci_conf[0x01] = 0x80;
     pci_conf[0x02] = 0x13;
-    pci_conf[0x03] = 0x70;
+    pci_conf[0x03] = 0x71;
     pci_conf[0x08] = 0x00; // revision number
     pci_conf[0x09] = 0x00;
     pci_conf[0x0a] = 0x80; // other bridge device

[Qemu-devel] Re: Unknown PCI Bridge

[Sven Köhler]

[-- Attachment #1: Type: text/plain, Size: 596 bytes --]

>> qemu's ACPI PCI device doesn't seem to be _that_ normal/known. At least
>> a recent Knoppix lists it as "Bridge: Intel Corp.: Inknown device 7013".
> 
> Wrong device id, should be 0x7113.

Hmmm, i looked it up, and i think i know why the author "preferred" 7013
instead of 7113.

7113 is 82371AB/EB/MB PIIX4 ACPI, but all the other qemu-hardware is
only PIIX3 - afaik.

So using 7113 would mean, that the PIIX4 stuff gets mixed with PIIX3
stuff. I don't know, how odd that might seem to some OS.

Beside that, a PIIX3-ACPI-device doesn't seem to exist in the
pciid-database.


[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 251 bytes --]

Re: [Qemu-devel] Re: Unknown PCI Bridge

[malc]

On Fri, 5 May 2006, Sven K?hler wrote:

>>> qemu's ACPI PCI device doesn't seem to be _that_ normal/known. At least
>>> a recent Knoppix lists it as "Bridge: Intel Corp.: Inknown device 7013".
>>
>> Wrong device id, should be 0x7113.
>
> Hmmm, i looked it up, and i think i know why the author "preferred" 7013
> instead of 7113.
>
> 7113 is 82371AB/EB/MB PIIX4 ACPI, but all the other qemu-hardware is
> only PIIX3 - afaik.

It makes zero difference, 7013 is something that does not exist at all
and 7113 makes OSes dance a happy dance.

>
> So using 7113 would mean, that the PIIX4 stuff gets mixed with PIIX3
> stuff. I don't know, how odd that might seem to some OS.

It's irrelevant to any OS that i know of.

>
> Beside that, a PIIX3-ACPI-device doesn't seem to exist in the
> pciid-database.

Huh?

-- 
mailto:malc@pulsesoft.com

[Qemu-devel] Re: Unknown PCI Bridge

[Sven Köhler]

[-- Attachment #1: Type: text/plain, Size: 758 bytes --]

>> So using 7113 would mean, that the PIIX4 stuff gets mixed with PIIX3
>> stuff. I don't know, how odd that might seem to some OS.
> 
> It's irrelevant to any OS that i know of.

;-)

>> Beside that, a PIIX3-ACPI-device doesn't seem to exist in the
>> pciid-database.
> 
> Huh?

# cat /usr/share/misc/pci.ids|grep -i PIIX3
        7000  82371SB PIIX3 ISA [Natoma/Triton II]
        7010  82371SB PIIX3 IDE [Natoma/Triton II]
        7020  82371SB PIIX3 USB [Natoma/Triton II]
# cat /usr/share/misc/pci.ids|grep -i PIIX4
        7110  82371AB/EB/MB PIIX4 ISA
        7111  82371AB/EB/MB PIIX4 IDE
        7112  82371AB/EB/MB PIIX4 USB
        7113  82371AB/EB/MB PIIX4 ACPI


See? No PIIX3 ACPI device. That's all i tried to say.



[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 251 bytes --]

Re: [Qemu-devel] Re: Unknown PCI Bridge

[malc]

On Fri, 5 May 2006, Sven K?hler wrote:

>>> So using 7113 would mean, that the PIIX4 stuff gets mixed with PIIX3
>>> stuff. I don't know, how odd that might seem to some OS.
>>
>> It's irrelevant to any OS that i know of.
>
> ;-)
>
>>> Beside that, a PIIX3-ACPI-device doesn't seem to exist in the
>>> pciid-database.
>>
>> Huh?
>
> # cat /usr/share/misc/pci.ids|grep -i PIIX3
>        7000  82371SB PIIX3 ISA [Natoma/Triton II]
>        7010  82371SB PIIX3 IDE [Natoma/Triton II]
>        7020  82371SB PIIX3 USB [Natoma/Triton II]
> # cat /usr/share/misc/pci.ids|grep -i PIIX4
>        7110  82371AB/EB/MB PIIX4 ISA
>        7111  82371AB/EB/MB PIIX4 IDE
>        7112  82371AB/EB/MB PIIX4 USB
>        7113  82371AB/EB/MB PIIX4 ACPI
>
>
> See? No PIIX3 ACPI device. That's all i tried to say.

Ok.

More to the point, no machines i have in my vicinity has a PCI device
dedicated to the ACPI. QEMU(old chipsets?) needed it to simplify
delivery of SCI (which must support sharing and be level sensetive)
having PCI device simplifies this somewhat (even though i believe QEMU
does it wrong currently)

There is zero functionality in 7113 or whatnot, it is/was simply a
convenience feature.

--
mailto:malc@pulsesoft.com

[Qemu-devel] Re: Unknown PCI Bridge

[Anthony Liguori]

On Thu, 04 May 2006 20:17:04 +0200, Fabrice Bellard wrote:

> Chris Bagwell wrote:
>> Hi all,
>> 
>> I upgraded to current CVS (0.8.1 plus a couple of patches like acpi).
>> Last time I upgraded was about 1 week ago.
>> 
>> When I ran this version with a win98 guest, windows detected a new
>> device called "PCI Bridge".  It was unable to find a driver for this on
>> the win98 CD and placed it as not working in the "other devices" section
>> of device manager.
>> 
>> Doesn't seem to harm anything.  I was guessing it had something to do
>> with the acpi patches but haven't verified.  Any ideas?
> 
> Yes, ACPI adds a new PCI device so it is normal. I am interested by any
> regression found using the current CVS with ACPI...

Win2k and Linux 2.6 (w/o kqemu) seem to work fine.

with -kernel-kqemu and 2.6.15, I get:

Uncompressing Linux... Ok, booting the kernel.
BIOS bug, local APIC #0 not detected!
IOAPIC[0]: Invalid reference to IRQ 0
IOAPIC[0]: Invalid reference to IRQ 0
PCI PIIX3: Enabling Passive Release on 0000:00:01.0
ALERT! /dev/hda1 does not exist. Dropping to a shell!

Regards,

Anthony Liguori

> Fabrice.

[Qemu-devel] Re: Unknown PCI Bridge

[Sven Köhler]

> Win2k and Linux 2.6 (w/o kqemu) seem to work fine.

have you reinstalled Win2k?

Or did you somehow manage, to turn an already installed Win2k from a
"Standard PC" into a "ACPI PC" (as the hardware-manager calls it)?