[Slackbuilds-users] Updates - 20070822
alan at lizella.net
Sun Aug 26 01:35:16 UTC 2007
Martin Lefebvre wrote:
>> root at robin:/home/alan/qemu# qemu-img create -f qcow slack.img 10G
>> Formating 'slack.img', fmt=qcow, size=10485760 kB
>> root at robin:/home/alan/qemu#
>> root at robin:/home/alan/qemu# qemu -cdrom /dev/cdrom -hda slack.img \
>> -m 256 -boot d
>> Could not open '/dev/kqemu' - QEMU acceleration layer not activated
>> At this point, the entire screen is taken up by qemu (though only about
>> a third of it is in use at the time) and the keys have been re-mapped.
>> I was of course, attempting to boot the Slackware 12.0 install cd, and
>> did so successfully, minus the whole key-map problem.
>> I played around with it a little more just now and determined that <F12>
>> was <TAB> and <j> was <ENTER>. Go figure. Even attempting to set a
>> different keymap in the Slackware installer didn't help.
I should have pointed out that I have not had this problem when running
Slackware 11.0 as the host operating system and 11.0 as the guest
> well, I couldn't boot my slack cd (i need a new cdrom badly) so I booted a
> DSL iso, and apart from switching from dvorak on the host to qwerty on the
> guest, no changes in keymap here. it did go to a 1024x768 window, but not
> full screen.
Can anyone else try this and see if they can duplicate this problem?
Perhaps it is something odd with my hardware?
It is better to hear the rebuke of the wise,
Than for a man to hear the song of fools.
-------------- next part --------------
A non-text attachment was scrubbed...
Size: 189 bytes
Desc: OpenPGP digital signature
Url : http://lists.slackbuilds.org/pipermail/slackbuilds-users/attachments/20070825/7d234670/attachment-0002.bin
More information about the Slackbuilds-users