Hi,
The problem is that proliant 3000 is old and requires use of pcibios to
detect all devices. You should try the following:
Edit arch/i386/Kconfig in your Linux build directory: look for ‘config
PCI_BIOS’.
Two lines below you’ll see ‘depends on !(X86_VISWS || X86_XEN) && ...’
Change this to ‘depends on !X86_VISWS && ...’
Now rebuild your Linux kernel. Ensure that after the build there is a file
arch/i386/pci/pcbios.o in your build tree (this will show that your config
change worked and the pcibios code was compiled).
Try running this new kernel and cross your fingers. :-)
If this works for you we may consider adding this support for domain0. Our
fear is that the somewhat different environment of domain0 (compared with
native) could cause PCIBIOS probing to cause some machines to fail to boot
that would otherwise work fine. One option for us is to require you to force
the BIOS to be probed by adding an explicit kernel boot parameter.
-- Keir
On 29/1/07 09:16, "İsmet Sönmez" <isonmez@bek.org.tr> wrote:
> Hi Kier,
>
> I try manual config 8139too in xen kernel but not show cart.
>
> Thanks for reply
>
> Ismet Sonmez
>>
>>
>> -----Original Message-----
>> From: Keir Fraser [mailto:Keir.Fraser@cl.cam.ac.uk]
>> Sent: Sunday, January 28, 2007 11:26 AM
>> To: İ smet S ö nmez; xen-devel@lists.xensource.com
>> Subject: Re: [Xen-devel] How is fix bug 539?
>>
>> Post lspci output from a Xen kernel and native kernel of the same
version.
>> Also post boot output (dmesg) from both kernels.
>>
>> -- Keir
>>
>> On 27/1/07 9:40 pm, "İsmet Sönmez"
<isonmez@bek.org.tr> wrote:
>>
>>
>>> Hi
>>>
>>> I use proliant 3000
>>> Yes.lspci not show any network cart.
>>> How is fix this bug.
>>>
>>> Thanks.
>>>
>>> Ismet Sönmez
>>>
>>>
>>>
>>>
>>> _______________________________________________
>>> Xen-devel mailing list
>>> Xen-devel@lists.xensource.com
>>> http://lists.xensource.com/xen-devel
>>
>
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xensource.com
http://lists.xensource.com/xen-devel