Why do I always get the weird problems?

so, the info first:

if I chroot to $LFS I suddenly cant use the key "i" in my keyboard!!
I also cant copy paste any "i" in my screen!!

yesterday i could chroot without issues!

if I chroot to / my keyboard works fine...
I am not sure why chrooting to that specific folder mess up with my keyboard!

the real command that i have been using is:

Which as i said I could use without troubles before today.
I also got a strange problem that vlc would play music but no videos, so something went off in my pc but im not sure what was it (i fixed vlc)

Any hints on this one?

nobody has any idea?
nothing?

Hi,

My only Idea is that you should have something like /etc and /mnt/lfs/etc/ (For chrooting)
Maybe something changed at update in /etc and didnt change in /mnt/lfs/etc?

Thinking in that Direction it should be something like this I bet. (Could be also something if you changed Kernel...)

I am guessing that because of .

Hope that helps you

GL!
Legine

Is it possible someone messed with the directory you are chrooting to? I'm thinking maybe your keyboard is getting remapped as a result of the chroot. The only reason I mention someone messing with the directory is a friend of mine had a prank pulled on him years ago involving his keyboard getting remapped.

Yeah, this sounds like shell mischief, caused by some errant keyboard-map. Is "i" the only key that doesn't work? Does it fail-to-work when shifted, Ctrl, etcetera?

Hi guys,

thanks for the pointers...

> Is it possible someone messed with the directory you are chrooting to?

myself probably, since this is a Linux from Scratch root and I did modify some things, but the problem appeared when i tried to boot the system... I am having a Kernel Panic, and since then when i chroot in $LFS i get this issue with the "i".

I can use "shift-i"~ and "CAPS-i"

but if I do "ls" and try to copy "/lib" and when i paste it I get "/lb", so I cannot even copy/paste it.

I am not sure if there is a problem with the keyboard map... how do i check on it?

You can check the current keymap with loadkeys. If you are having a kernel panic the problem may well be that the kernel console driver is messed up.

thanks for the hint, yesterday I fixed the kernel issue, it was a sata driver missing, but when the LFS system finished loading i got the same problem with the 'i', I will check what loadkeys does for me.

i did a dumpkeys and this is what i got:

keycode 23 = i

I also did a dumpkeys in my slackware machine and it is the same... so basically the i IS mapped correctly, but i dont get it why it doesnt work, and it doesnt allow me to copy paste it either!!

hi Raptor,

i am sure you are aware of this resource - but just in case you are not then
http://en.wikipedia.org/wiki/Chroot

explains a lot - much of which is certainly new to me.

Thanks for the link, it was a good reading, learning new things always feels good.

But it did not help in this particular case, since basically chroot is working fine... it seems to be a problem with the keyboard map as far as we have been pointing out but i dont seem to get it right since the keys are mapped in chroot the same way as in my slackware host...

I also tried loading the default keys and it came up with "Cannot find defkeymap.kmap" but again dumpkeys mentions that key 23 = i so I think it IS loading a default keyboard somewhere over the rainbow.

Just for giggles...
if you do an ls /lib do you actually get the right listing. I know the 'i' won't show up but if you get the right listing regardless then the problem is on the output/display side rather than in the input/keyboard side.

Just noticed that you said that dumpkeys shows an 'i'. Is this under the chroot condition?

one more test:

# echo -e "\151"
i

since you are forcing an 'i' to be displayed by ascii code (in octal) the output side is completely isolated from the input side.

I guess thats where the problem is!
thanks for pointing this one out... now what can i do about it?

EDIT
actually none of the ascii codes that i pass works...