[Qemu-devel] More Solaris QEMU hosting weirdness

[Qemu-devel] More Solaris QEMU hosting weirdness

[Ben Taylor]

I'm seeing some strangeness in QEMU hosted on Solaris 10
(qemu 0.6.2, around march 23, with some patches from
Juergen Kiel which are not in cvs yet)

1) Ocassionally, when I switch from monitor mode back
to the console (specifically, I see this in guested Solaris
Express instances in console mode, not GUI), the
console repeats the "1" key, as if when I hit 
<ctrl><alt><1>, the keyboard driver in qemu is
repeating the key. (which is odd, because key repeat
as a feature in the guested OS, in this instance, 
does not repeat if I hold down a character).

2) Using the windows media player on XPHome (9, I haven't
upgraded this one to 10 yet), I get the following errors
from the sb.c module.  I'm using the OSS sound
drivers, so I'm wondering if there's a bit of
an incompatibility here.  Note, the sound does
work, though I hear some clicking and such when
trying to play audio:

sb16: attempt to write mixer[0x88] <- 0xfc
sb16: attempt to write mixer[0x8b] <- 0x3c
sb16: attempt to write mixer[0x8b] <- 0
sb16: warning: command 0xf,1 is not trully understood yet
sb16: warning: command 0xe,2 is not trully understood yet
sb16: attempt to write mixer[0xff] <- 0x20
sb16: attempt to write mixer[0x8e] <- 0xfe
sb16: attempt to write mixer[0x8e] <- 0xff
sb16: attempt to write mixer[0x8e] <- 0xff
sb16: attempt to write mixer[0x90] <- 0xef
sb16: attempt to write mixer[0x90] <- 0xff
sb16: attempt to write mixer[0x90] <- 0xdf
sb16: attempt to write mixer[0x90] <- 0xff
sb16: attempt to write mixer[0x90] <- 0xff
sb16: attempt to write mixer[0x90] <- 0x7f
sb16: attempt to write mixer[0x90] <- 0xff
sb16: attempt to write mixer[0x90] <- 0xbf
sb16: attempt to write mixer[0x90] <- 0xff
sb16: attempt to write mixer[0x90] <- 0xfe
sb16: attempt to set DMA register 8bit 1, 16bit 5 (val=0x22)
sb16: warning: command 0xf,1 is not trully understood yet
sb16: warning: command 0xe,2 is not trully understood yet
sb16: warning: command 0xf,1 is not trully understood yet
sb16: warning: command 0xe,2 is not trully understood yet
sb16: warning: command 0xf,1 is not trully understood yet
sb16: warning: command 0xe,2 is not trully understood yet
sb16: warning: command 0xf,1 is not trully understood yet
sb16: warning: command 0xe,2 is not trully understood yet
sb16: warning: command 0xf,1 is not trully understood yet
sb16: warning: command 0xe,2 is not trully understood yet
sb16: warning: command 0xf,1 is not trully understood yet
sb16: warning: command 0xe,2 is not trully understood yet
sb16: warning: command 0xf,1 is not trully understood yet
sb16: warning: command 0xe,2 is not trully understood yet
sb16: warning: command 0xf,1 is not trully understood yet
sb16: warning: command 0xe,2 is not trully understood yet
sb16: warning: command 0xf,1 is not trully understood yet
sb16: warning: command 0xe,2 is not trully understood yet
sb16: warning: command 0xf,1 is not trully understood yet
sb16: warning: command 0xe,2 is not trully understood yet
sb16: warning: command 0xf,1 is not trully understood yet
sb16: warning: command 0xe,2 is not trully understood yet
sb16: warning: command 0xf,1 is not trully understood yet
sb16: warning: command 0xe,2 is not trully understood yet
sb16: warning: command 0xf,1 is not trully understood yet
sb16: warning: command 0xe,2 is not trully understood yet
sb16: warning: command 0xf,1 is not trully understood yet
sb16: warning: command 0xe,2 is not trully understood yet
sb16: warning: command 0xf,1 is not trully understood yet
sb16: warning: command 0xe,2 is not trully understood yet
sb16: warning: command 0xf,1 is not trully understood yet
sb16: warning: command 0xe,2 is not trully understood yet
sb16: warning: command 0xf,1 is not trully understood yet
sb16: warning: command 0xe,2 is not trully understood yet
sb16: warning: command 0xf,1 is not trully understood yet
sb16: warning: command 0xe,2 is not trully understood yet
sb16: warning: command 0xf,1 is not trully understood yet
sb16: warning: command 0xe,2 is not trully understood yet
sb16: warning: command 0xf,1 is not trully understood yet
sb16: warning: command 0xe,2 is not trully understood yet
sb16: warning: command 0xf,1 is not trully understood yet
sb16: warning: command 0xe,2 is not trully understood yet
sb16: warning: command 0xf,1 is not trully understood yet
sb16: warning: command 0xe,2 is not trully understood yet
sb16: warning: command 0xf,1 is not trully understood yet
sb16: warning: command 0xe,2 is not trully understood yet
sb16: warning: command 0xf,1 is not trully understood yet
sb16: warning: command 0xe,2 is not trully understood yet
sb16: warning: command 0xf,1 is not trully understood yet
sb16: warning: command 0xe,2 is not trully understood yet
sb16: warning: command 0xf,1 is not trully understood yet
sb16: warning: command 0xe,2 is not trully understood yet
sb16: warning: command 0xf,1 is not trully understood yet
sb16: warning: command 0xe,2 is not trully understood yet
sb16: warning: command 0xf,1 is not trully understood yet
sb16: warning: command 0xe,2 is not trully understood yet
sb16: warning: command 0xf,1 is not trully understood yet
sb16: warning: command 0xe,2 is not trully understood yet
sb16: warning: command 0xf,1 is not trully understood yet
sb16: warning: command 0xe,2 is not trully understood yet
sb16: attempt to write mixer[0x8e] <- 0xff
sb16: attempt to write mixer[0x8e] <- 0xfe
sb16: attempt to write mixer[0x8e] <- 0xff
sb16: attempt to write mixer[0x88] <- 0xff
sb16: attempt to write mixer[0x88] <- 0xff
sb16: attempt to write mixer[0x88] <- 0xff

ideas?

Ben

Re: [Qemu-devel] More Solaris QEMU hosting weirdness

[malc]

On Thu, 7 Apr 2005, Ben Taylor wrote:

> I'm seeing some strangeness in QEMU hosted on Solaris 10
> (qemu 0.6.2, around march 23, with some patches from
> Juergen Kiel which are not in cvs yet)
>
<snip>
>
> 2) Using the windows media player on XPHome (9, I haven't
> upgraded this one to 10 yet), I get the following errors
> from the sb.c module.  I'm using the OSS sound
> drivers, so I'm wondering if there's a bit of
> an incompatibility here.  Note, the sound does
> work, though I hear some clicking and such when
> trying to play audio:
>
> sb16: attempt to write mixer[0x88] <- 0xfc
<snip>
> sb16: attempt to write mixer[0x88] <- 0xff
>
> ideas?

This is normal. Almost all writes to mixer are silenetly ignored,
and as for not understood, well they are, and i wasn't able to
find any documentation.

-- 
mailto:malc@pulsesoft.com

Re: [Qemu-devel] More Solaris QEMU hosting weirdness

[Jonas Maebe]

On 7 apr 2005, at 16:30, malc wrote:

> This is normal. Almost all writes to mixer are silenetly ignored,
> and as for not understood, well they are, and i wasn't able to
> find any documentation.

Does DosBox also not support them? (http://dosbox.sourceforge.net) 
dosbox/src/hardware/sblaster.cpp contains a lot of mixer-related stuff 
at least.


Jonas

Re: [Qemu-devel] More Solaris QEMU hosting weirdness

[malc]

On Thu, 7 Apr 2005, Jonas Maebe wrote:

>
> On 7 apr 2005, at 16:30, malc wrote:
>
>> This is normal. Almost all writes to mixer are silenetly ignored,
>> and as for not understood, well they are, and i wasn't able to
>> find any documentation.
>
> Does DosBox also not support them? (http://dosbox.sourceforge.net) 
> dosbox/src/hardware/sblaster.cpp contains a lot of mixer-related stuff at 
> least.

Do you want VM to modify your hardware mixer settings(volume for instance)
behind your back? SBPRO stereo mode is controlled by a write to a mixer
register, apart from that everything can be safely ignored.

-- 
mailto:malc@pulsesoft.com

Re: [Qemu-devel] More Solaris QEMU hosting weirdness

[Jonas Maebe]

(sending again, just got a "user unknown" error message stating that 
the address "qemu-devel@nongnu.org" does not exist)

On 7 apr 2005, at 16:55, malc wrote:

>> Does DosBox also not support them? (http://dosbox.sourceforge.net) 
>> dosbox/src/hardware/sblaster.cpp contains a lot of mixer-related 
>> stuff at least.
>
> Do you want VM to modify your hardware mixer settings(volume for 
> instance)
> behind your back?

No, that's why if it is supported, the mixer should be emulated.

> SBPRO stereo mode is controlled by a write to a mixer
> register, apart from that everything can be safely ignored.

Possibly, I'm not a mixer expert at all.


Jonas