Threaded Mode | Linear Mode

CPUnltd · (This post was last modified: 01-25-2010 04:26 PM by CPUnltd.)

been trying to boot tinyme in vbox and on my Aspire Revo and in both cases, I seem to get some type of dvorak keyboard setting... my T is a Y, my R is a P and my O is an R, so when I try to login on the livecd, instead of typing root, I type prry......
in order to actually login I have to type "ossk" which equals "root" for my keyboard and I have NO clue as to why... unfortunately, I am not in the mood to learn this dvorak setup just to install tinyme and change it back to standard (if I can)... this happens after multiple reboots, so it's not a fluke or random occurance... can anyone offer insight or help? or for that matter, a boot option to force US keyboard settings?

EDIT: I've spotted the exact moment the layout changes... when in verbose, just as the "welcome to Unity Linux" line appears, the layout switches... before that, it is [qwerty]... afterwards it's [',.py]. What kind of layout is that???

EDIT2: modified subject to attract others with same/similar issue

***KDulcimer*** · 01-24-2010, 08:44 PM

I know some people have reported this issue, but I can't seem to replicate it. I honestly don't know why the keyboard layout is changing itself.

CPUnltd · 01-24-2010, 08:50 PM

well, that makes life difficult... I can't seem to find any info on keyboard layouts changing during boot anywhere online... so I've got nothing to base it off atm...

CPUnltd · 01-24-2010, 10:26 PM

whatever this issue is, it's happening on a tty level... I had my vbox install working just fine till I uninstalled the guest additions so I could install the new ones (seems they won't just upgrade like software is supposed to) and after reboot (cause just uninstalling wasn't good enough, it had to clear out what I was using as well) I was dropped to shell in vbox and stuck with the same dvorak madness... hey KD, try booting into it in vbox and switching to a tty after it finishes booting (or for that matter, switch to verbose and see if your layout is screwed up)... you have to find a way to reproduce this issue, I have had it happen on my laptop, desktop and vbox laptop install... that's too many places for this to not be reproducable...

***gettinther*** · 01-25-2010, 01:57 AM

I wonder if the livecd process fails to remove keyboard information during the iso creation. Kd uses a dvorak keyboard afaik so he won't get the issue. That needs to be fixed in mklivecd I think because this should never be a problem. I'll see if I can figure this one out.

CPUnltd · 01-25-2010, 02:07 AM

ok, I have better tracked the actual issue, but I am still unable to pinpoint... it seems what I have coined "Dvorak Madness" only affects tty-level usability. I experienced an interesting scenario when working on a tinyme vm...

needed to update guest additions to get rid of "wrong guest additions" error... in doing so, I subsequently eliminated the gui altogether. This is where I experienced DM in the tinyme vm. Prior to this, I was fine (because guest additions took care of video drivers, so DM never showed up). after that, I booted normally and was introduced to DM at the commandline login in my vm just as it was on my livecd for my nettop (which requires NV prop drivers to get any sort of gui). Needless to say, I was "!@#$^". Standard boot put me in DM, as well as Vesa boot. So I went for Safe boot. I got DM while I was booting (in verbose, DM would go in and out), but once safe mode was done loading and was at the prompt, my keyboard was normal??? So, I manually mounted the guest additions iso and installed guest additions. I was prompted with a message that told me that old guest additions were still in the system (even though I removed them via smart before this) so I opted to force the install of the new drivers which forced the uninstall of whatever old drivers were supposedly left behind. So I carefully watch as the installer proptly removed vboxfs, vboxvideo and vboxadd... what really struck me as odd was that it was removing versions 2.2.4! This leads me to wonder if KD and Gett should look into that a bit more in-depth... as that COULD be something screwy going on with both Unity and TinyMe. So, the "upgrade" goes through without a hitch and I reboot... behold, I have a gui now!!! ...and slim loads just fine. And when I go to type the username... my DM problem has been cured!!! ... my keyboard layout is back to normal and I can use the computer just fine. In conclusion, Dvorak Madness seems to only occur during actual boot (console boot or verbose activated during normal boot) and when in console/tty mode. Does not affect grub or safe mode. So now I am back functional and I have come to the conclusion that I will have to install and remaster tinyme in vbox with prop nv drivers installed in order to get my Revo nettop running again... Fun times ahead for all! Big Grin

Granted this is not a solve for DM, just a breakdown of where tinyme is affected. Can't recall if Unity is affected by DM as well, but will probably test that out and post here and over at the other forum if it is... But I don't think it is, as I had to install the NV drivers via commandline when I installed Unity on the nettop not long ago. We shall see. I am under the impression that this will probably affect any system that would normally get a blank screen at login (vs getting an actual gui) as well. But that is purely speculation.

CPUnltd · (This post was last modified: 01-25-2010 02:11 AM by CPUnltd.)

[quote author=gettinther link=topic=851.msg3495#msg3495 date=1264384651]
I wonder if the livecd process fails to remove keyboard information during the iso creation. Kd uses a dvorak keyboard afaik so he won't get the issue. That needs to be fixed in mklivecd I think because this should never be a problem. I'll see if I can figure this one out.
[/quote]

if that is KD's custom Dvorak, that would explain why it looks so off... not that KD is off, but that it is a custom dvorak setup. ;D though KD is a little off... but that's off-topic Tongue

isn't there a grub option for keyboard layout?

***KDulcimer*** · 01-25-2010, 03:44 AM

Gettinther,

I installed TinyMe inside VBox, and inside the VM the keyboard was QWERTY. Are you saying that I don't get this error because my host machine is Dvorak?

CPUnltd · 01-25-2010, 06:52 AM

It is quite possible that you having Dvorak might be protecting you from catching DM... can't say for sure... do you have a non-dvorak bare-metal that you can test with?

***gettinther*** · 01-25-2010, 02:42 PM

Actually the vbox drivers do pick up information from the host system. I just didn't know it did it for the keyboard as well.
What makes it even more difficult to troubleshoot is that it seems to be only a one way issue. You don't seem to be getting the issue if the iso was built from a system using a qwerty keyboard and installed on a system with a dvorak keyboard.