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

[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

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

[Leigh Dyer]

On Mon, 2004-06-07 at 01:49 +0300, Hetz Ben Hamo wrote:
> 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)
> 
I've seen these problem too. As a work-around, you can turn off video
card acceleration, under the Performance tab in the Advanced settings
section of the Display Properties dialog. This cleans up all of the
video corruption for me, though of course it just masks the bug rather
than fixing it.

I don't unfortunately have any work-around for the network problems.
I've also tried a manual network setup using the tun/tap device, but it
doesn't work any better.

Thanks
Leigh

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

[Tim]

> I don't unfortunately have any work-around for the network problems.
> I've also tried a manual network setup using the tun/tap device, but it
> doesn't work any better.

For the most part, network has been working fine for me.  I have used
the linux bridging module, across a real ethernet device and tun0, and
it worked ok.  I am now routing across my host OS (which I have done
before), and it is also working ok.  However, I have noticed that from
time to time my pings time out.  Typically the first one or two pings
when I ping a given host.  After that, it usually works fine for
subsequent pings, though sometimes re-surfaces.  Could it be a timing
issue with the virtual device?  Probably not the problems you are
experiencing Hetz, though worth mentioning.


I am using the most recent CVS (at least, as of this afternoon), and the
following command line:

qemu -pci -m 256 -cdrom win2k-install-cd.img -hda win2k-cow.img -boot c -n "$TUN_SCRIPT"

with the contents of $TUN_SCRIPT being:

sudo ifconfig tun0 192.168.19.1 netmask 255.255.255.0 broadcast 192.168.19.255
sudo sh -c 'echo 1 > /proc/sys/net/ipv4/ip_forward'


I am quite impressed with the momentum this project has had thus far.  I
tell all of my friends about it.  Keep up the good work!

tim

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

[Tim]

> For the most part, network has been working fine for me.  I have used
> the linux bridging module, across a real ethernet device and tun0, and
> it worked ok.  I am now routing across my host OS (which I have done
> before), and it is also working ok.  However, I have noticed that from
> time to time my pings time out.  Typically the first one or two pings
> when I ping a given host.  After that, it usually works fine for
> subsequent pings, though sometimes re-surfaces.  Could it be a timing
> issue with the virtual device?  Probably not the problems you are
> experiencing Hetz, though worth mentioning.

Forgot to mention, I am running Windows 2000 Professional.

tim

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

[Leigh Dyer]

On Sun, 2004-06-06 at 22:24 -0700, Tim wrote:
> > I don't unfortunately have any work-around for the network problems.
> > I've also tried a manual network setup using the tun/tap device, but it
> > doesn't work any better.
> 
> For the most part, network has been working fine for me.  I have used
> the linux bridging module, across a real ethernet device and tun0, and
> it worked ok.  I am now routing across my host OS (which I have done
> before), and it is also working ok.  However, I have noticed that from
> time to time my pings time out.  Typically the first one or two pings
> when I ping a given host.  After that, it usually works fine for
> subsequent pings, though sometimes re-surfaces.  Could it be a timing
> issue with the virtual device?  Probably not the problems you are
> experiencing Hetz, though worth mentioning.
> 

It's been fine for me in Linux (PCI or ISA mode), and in ISA mode in
both Windows 98 and 2000, but Win98 seems to trip up in PCI mode. 

> 
> I am using the most recent CVS (at least, as of this afternoon), and the
> following command line:
> 
> qemu -pci -m 256 -cdrom win2k-install-cd.img -hda win2k-cow.img -boot c -n "$TUN_SCRIPT"
> 
You're running Windows 2000 with PCI enabled? I didn't think this worked
yet - certainly all of my attempts so far to get this running have
failed. Did you have to do anything special to get PCI mode working with
Windows 2000?

Thanks
Leigh

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

[Tim]

> > I am using the most recent CVS (at least, as of this afternoon), and the
> > following command line:
> > 
> > qemu -pci -m 256 -cdrom win2k-install-cd.img -hda win2k-cow.img -boot c -n "$TUN_SCRIPT"
> > 
> You're running Windows 2000 with PCI enabled? I didn't think this worked
> yet - certainly all of my attempts so far to get this running have
> failed. Did you have to do anything special to get PCI mode working with
> Windows 2000?

Nope, not really.  I always rip my install media to files, and install
from there, but other than that, nothing extraordinary.  In fact, I
installed with the same exact line above off a fairly recent CVS, with
only the boot option changed to `d'.  My host system is Debian unstable,
using a custom 2.6.6 kernel, based on Debian's kernel source. 
The NIC in windoze detects as a 
"Realtek RTL8029 (AS)-based PCI Ethernet Adapter".   

One quirk though... when I first did the install the other night, I had
forgotten to set up my network startup script.  Windows installed fine,
detected the NIC even, and let me configure it.  From then on, ipconfig
from the command line reported the proper network configuration,
however, the GUI interface for changing the TCP/IP settings was not
configured as I had done during install.  Even after I changed the
settings manually and "rebooted", the win2k guest OS wouldn't update the
TCP/IP config.  (This is even after I got the network tun0 script
working). 

Later, I re-installed, with the network script operational, and haven't
yet ran into the same difficulties (though, I haven't extensively
tested).  The GUI interface in win2k does report the proper network
config though.


On the downside I have not been able to install SP4 yet.  No matter
which install method I use, I always get "An error occured", and then it
quits.  Thanks so much for your verbosity Microshaft...

hope that helps,
tim

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

[Leigh Dyer]

On Sun, 2004-06-06 at 23:28 -0700, Tim wrote:
> > > I am using the most recent CVS (at least, as of this afternoon), and the
> > > following command line:
> > > 
> > > qemu -pci -m 256 -cdrom win2k-install-cd.img -hda win2k-cow.img -boot c -n "$TUN_SCRIPT"
> > > 
> > You're running Windows 2000 with PCI enabled? I didn't think this worked
> > yet - certainly all of my attempts so far to get this running have
> > failed. Did you have to do anything special to get PCI mode working with
> > Windows 2000?
> 
> Nope, not really.  I always rip my install media to files, and install
> from there, but other than that, nothing extraordinary.  In fact, I
> installed with the same exact line above off a fairly recent CVS, with
> only the boot option changed to `d'. 
*snip*

I haven't had much luck at all yet with Windows 2000 and PCI mode. Every
time I try to install it, the intstaller stops about half-way through
the hardware probe and refuses to go any further, though the machine is
still active (I can click in and move the virtual mouse, etc.). Trying
to boot a Win2k machine that I installed in ISA mode fails with an
INACCESSIBLE_BOOT_DEVICE error, presumably because it can't find the ISA
hard-drive controller it was installed using.

I'm giving it another go now - if I have any luck, I'll let the list
know.

Thanks
Leigh

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

[Antony T Curtis]

On Sun, 2004-06-06 at 23:49, Hetz Ben Hamo wrote:
> 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)

I have had the same problem... It appears that the videotovideo
patterncopy doesn't work... (that is the code it gets to)

Turning off acceleration fixes it but of course it makes it no faster
than the previous driver.
-- 
Antony T Curtis <antony.t.curtis@ntlworld.com>

[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.

[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