Bug #507
closedSingle user mode keyboard garbage and unexpected softupdate inconsistency
0%
Description
Hi,
Ive been encountering a strange bug. When I get to single user mode and
when it asks about hitting enter to choose /bin/sh as shell, upon
hitting enter i get garbage on the screen, this is not just the enter
key but all keys including Esc produce different garbage making the
single user mode utterly useless.
My keyboard is:
ukbd0: Logitech USB Receiver, rev 1.10/30.07, addr 3, iclass 3/1
kbd1 at ukbd0
Another problem ive been encountering is how often unexpected softupdate
inconsistency happens. For some reason it always happens on /tmp (1gb
large) during the "pull-the-plug" test. all other have consistent
softupdates
Cheers,
Petr
Updated by dillon almost 18 years ago
I have a vague memory of the system having to do some sort of translation
or put the keyboard into some sort of translation mode in order for it
to work properly.
At some point in the past we had a similar 'garbage from USB keyboards'
issue and I remember it being resolved, but I don't remember exactly what
the issue turnde out to be. This sounds like the same thing.
-Matt
Updated by sepherosa almost 18 years ago
http://lists.freebsd.org/pipermail/freebsd-usb/2006-October/002596.html
Will this be useful to you?
Best Regards,
sephe
Updated by bastyaelvtars almost 18 years ago
On Sat, 06 Jan 2007 10:18:21 +1100
Petr Janda <elekktretterr@exemail.com.au> wrote:
I usually use a USB keyboard to administer different servers running DragonFly an it works for me. I had issues with 1.6, though.
Updated by elekktretterr almost 18 years ago
Are you sure it works in single user mode?
I have a vague memory that my usb keyboard used to work too. :S
Petr
Updated by tuxillo about 15 years ago
Can you please confirm that this issue still appears on HEAD?
Updated by tuxillo almost 10 years ago
- Description updated (diff)
- Category set to Other
- Status changed from New to Closed
- Assignee deleted (
0) - Target version set to 4.2
Hi,
- Many updates could have solved this already (new USB stack, sh updates, etc)
- There has been quite some work to fix bugs with soft-updates too.
So closing. Feel free to open a new one if it still persists.
Cheers,
Antonio Huete