[Qemu-devel] Re: NE2K PCI and Windows 98SE & Cirrus Logic

[Qemu-devel] Re: NE2K PCI and Windows 98SE & Cirrus Logic

[Mike Nordell]

Fabrice Bellard wrote:

> If no one sees severe problems with -pci, I propose it is the
> default in 0.5.6.

There is a problem in Windows 2000 guest. In the Device Manager it displays
the first IDE controller as connected to (and belonging to) the PCI chipset.
However, the second IDE controller shows up as being unrelated - like a
plain ol' ISA controller (occupying IRQ 15).
(In Windows-speak the first channel is displayed as "Primary IDE Channel",
hanging off the "82371SB PCI Bus Master IDE Controller". The second one is
listed as top-level "Standard IDE/ESDI Hard Disk Controller").

Also, there seems to be a problem with the Cirrus emulation. While the PCI
config did display it had reserved 32MB of address space for the chip, the
amount of RAM presented in e.g. Display Properties is only 256KB, allowing a
maximum of 800x600x4bpp (making gfx output not only limited, but also quite
slow).

/Mike

Re: [Qemu-devel] Re: NE2K PCI and Windows 98SE & Cirrus Logic

[Leigh Dyer]

On Mon, 2004-06-07 at 22:45 +0200, Mike Nordell wrote:
> Fabrice Bellard wrote:
> 
> > If no one sees severe problems with -pci, I propose it is the
> > default in 0.5.6.
> 
> There is a problem in Windows 2000 guest. In the Device Manager it displays
> the first IDE controller as connected to (and belonging to) the PCI chipset.
> However, the second IDE controller shows up as being unrelated - like a
> plain ol' ISA controller (occupying IRQ 15).
> (In Windows-speak the first channel is displayed as "Primary IDE Channel",
> hanging off the "82371SB PCI Bus Master IDE Controller". The second one is
> listed as top-level "Standard IDE/ESDI Hard Disk Controller").
> 

I've now completed a successful Win2k install in PCI mode (not sure when
that started working :) ), and I've seen this issue with the IDE
controllers too. Everything seems to be working regardless though. I can
also confirm that the 4Mb video RAM patch committed a couple of hours
ago fixes the Cirrus Logic video with Win2k - it detected the card at
install and seems to be running quite happily with the standard driver
that ships with Win2k.

Thanks
Leigh

> Also, there seems to be a problem with the Cirrus emulation. While the PCI
> config did display it had reserved 32MB of address space for the chip, the
> amount of RAM presented in e.g. Display Properties is only 256KB, allowing a
> maximum of 800x600x4bpp (making gfx output not only limited, but also quite
> slow).
> 
> /Mike
> 
> 
> 
> _______________________________________________
> Qemu-devel mailing list
> Qemu-devel@nongnu.org
> http://lists.nongnu.org/mailman/listinfo/qemu-devel

[Qemu-devel] NE2K PCI and Windows 98SE & Cirrus Logic

[Hetz Ben Hamo]

Hi,

I just started to use the -pci switch with win98 as a guest..

everything detected correctly and cirrus logic graphics seems much 
faster then with the old graphics driver - however there are paiting 
bugs (see screenshot URL at the bottom of this page)

The Network card is being detected correctly, but it seems I cannot get 
an IP. All I get from Windows "winipcfg" after clicking "renew is": 
Error DHCP Server Unavailable: Renewing adapter "" (and the IP remains: 
169.254.123.23)

I tried with and without Renzo's patch, doesn't seem to change anything. 
I'm using QEMU CVS from tonight...

URL for the screenshot: http://www.dad-answers.com/qemu/win98-net-bug.png

Any suggestions?

Thanks,
Hetz

[Qemu-devel] Re: NE2K PCI and Windows 98SE & Cirrus Logic

[Fabrice Bellard]

Hetz Ben Hamo wrote:
> I just started to use the -pci switch with win98 as a guest..
> 
> everything detected correctly and cirrus logic graphics seems much 
> faster then with the old graphics driver - however there are paiting 
> bugs (see screenshot URL at the bottom of this page)

It should work better now.

If no one sees severe problems with -pci, I propose it is the default in 
0.5.6.

Cirrus VGA seems to work with both Win 95 and 98 without any additionnal 
drivers, so it is likely to be the default config.

There are still issues with Bochs VESA VBE (you cannot use it 
simultaneously with Cirrus VGA yet). Moreover, the Cirrus VGA driver is 
not optimized (the video memory writes are extremely slow compared to 
what could be possible and the blitter operations could be at least 
twice as fast).

Fabrice.