On Fri, Nov 19, 2021 at 9:22 AM Kent West <[email protected]> wrote: > On Fri, Nov 19, 2021 at 7:43 AM Kent West <[email protected]> wrote: > >> Wanting to see what the Hurd looks like... >> >> I did: >> >> $ wget >> http://cdimage.debian.org/cdimage/ports/11.0/hurd-i386/debian-hurd.img.tar.xz >> $ tar xJf debian-hurd.img.tar.xz >> >> followed by >> >> $ aptitude install qemu-system-x86-64 >> >> followed by >> >> $ kvm -m 1G -drive file=$(echo debian-hurd*.img),cache=writeback,format=raw & >> >> This got me to a QEMU window, with a GRUB screen ready to boot the Hurd. >> At this point, the keyboard works. When I select the default selection, >> eventually I get to a login prompt, but the keyboard is non-responsive. If >> I click my mouse inside the window and move it around a bit, I finally get >> a message saying the mouse queue is full. >> >> If, instead of booting into the default selection in GRUB, I select the >> Advanced option and then the Recovery option, I can get to a login, where >> the keyboard works, and I can log in and do some command-line things. When >> I type "exit", it finishes booting (I assume, as if I had selected the >> default setting in GRUB), and again, once I get to the login prompt, the >> keyboard is dead. >> >> I do see some errors on the screen. Here's what I see on-screen: >> >> ==== >> >> Timeout reached while wating [sic] for return value >> /bin/console: Could not receive return value from daemon process: >> Connection timed out >> Starting enhanced syslogd: rsyslogdrsyslogd: could not load module >> 'imklog', errors: trying to load module >> /usr/lib/i386-gnu/rsyslog/imklog.so: /user/lib/i386-gnu/rsyslog/imklog.so: >> undefined symbol: klogWillRunPrePrivDrop [v.8.39.0 try >> http://www.rsyslog.com/e/2066 ] >> . >> ==== >> >> > If I boot into Advance/Recovery and log in, and then run > "/etc/rc2.d/S01hurd-console start", I can duplicate the failed keyboard > response and error messages. > > I'll look through that script, but knowing next to nothing about Hurd, I > don't feel a lot of confidence that I'll figure out what's going on. > > -- > Kent West <")))>< > Westing Peacefully - http://kentwest.blogspot.com >
I tried it on a different PC (a Dell laptop, about three years old, running bookworm/sid), and the Hurd booted fine, and the keyboard worked. I did notice that the login prompt appeared twice on the screen, which I perceived to be some sort of minor glitch in the display routines. So when I got back to my desktop Dell today, I tried a different terminal window, and a different Debian GNU/Linux user, and a different X session, and a different window manager, but with the same keyboard-failure problem when trying the Hurd. Then I thought to do an "aptitude update && aptitude full-upgrade"; first time hung (very, very odd), and I had to kill the actual Terminal (Gnome Terminal) window; a few other minor little glitches in X made me wary of something going on under the hood, and rather than trouble-shoot it, I just rebooted the computer (it's not a server; it's just a user desktop PC, so I took the easy route). After rebooting, I again aptitude update/full-upgraded, which updated a few things (didn't pay much attention), and now when I try running the Hurd, it works! (Kinda wish now I had paid attention to what got upgraded.) I get that same video glitch I get on the laptop (where the login prompt appears both high and low in the terminal window). TLDR: upgraded my Linux system; don't know what I upgraded; but now the Hurd works past this keyboard failure issue -- Kent West <")))>< Westing Peacefully - http://kentwest.blogspot.com
