You're very much welcome and thank you for the excellent work. So "the same thing" actually means at the point in the guide where you need to run setup you just can't. Key presses are not properly registered as described in the original post. That seemed like the weirdest thing. I was worried it could have been my new keyboard but it seemed easier to at least try to run setup in the second virtual console rather than actually fetching another keyboard. It worked so I simply went on with the tutorial and forgot about it until I came across this post (searching answers to a different question) and figured I might know something worth mentioning.

1 members found this post helpful.

Thanks. I have tested with this myself and found no issues. I'm wondering if it's due to selecting a specific keyboard map which is causing problems. Which keyboard map are you specifying?

I go with default choice English US keymap.

1 members found this post helpful.

Since I figured it would be easier for me than for you to investigate the issue I went on and reinstalled Slackware with a different keyboard plugged in and had no issue. I then rebooted with my new keyboard plugged in and managed to reproduce the problem so definitely a keyboard thing.

My new keyboard is a HHKB Hybrid Silent. I did some research and found there is a bug in the mcba_usb driver. If we can confirm M0M0's keyboard uses the same chip then you can probably have this marked as solved.

https://www.mail-archive.com/debian-...msg124617.html

1 members found this post helpful.

I'm pretty sure my keyboard does not use the same chip: I have an original IBM model M. However, to connect it to the Raspberry Pi I have to use a PS2 to USB converter, that might add another point of failure. It works fine on all other machines though.

1 members found this post helpful.

As a matter of fact, I too used a PS2 to USB adapter for my test so at least we know it can work with one.

1 members found this post helpful.

That's what I selected to test with initially. Then I also tried IT, FR, and DE keyboard maps. All worked as expected.

Have you tried with the default US keyboard map initially and then selecting the correct one after running 'setup'? If so, does it make any difference?

OK noted. The main issue with problems like these is they cannot be reproduced without identical hardware. Still, thank you VERY much for taking the time to do some testing - it saves me spending time on trying to fix something that's not broken. It'll also be the reason why I can't find any problem(s).

The thing is with my new keyboard I can not run setup because I can not type setup before I press return. Some key presses are not registered so the command syntax is incorrect. I can work around the issue (by either switching to virtual console 2 or rebooting and using a different keyboard). After Slackware is installed and configured my keyboard works fine (with US keyboard map as it is my keyboard's mapping).

You're much welcome. I'm happy to help as I know your time is much better spent elsewhere. Hopefully M0M0 is able to use my ALT-F2 workaround to complete the install and enjoy his favorite keyboard with Slackware on Raspberry Pi as I do.

1 members found this post helpful.

I have a similar problem with HDMI, which is why I mentioned trying to connect over a remote shell, or by serial connection. For testing purposes for aarch64. I have not taken into account the arm32 port.

When I boot with an HDMI monitor plugged in, the boot process is normal except for having to switch tty1 to tty2 (or any of the other terminals). At that point I can run "setup".

It's important to note that this only happens on the Raspberry Pi 3. The raspberry pi 4 did exhibit this issue, but does not have this behavior anymore. It is important to also note that when connected to a serial adapter or a remote shell none of this is apparent.

I suspect there are two issues here:
1. the keyboard ps2 to usb adapter is making it difficult to type
2. switching to a different terminal allows for shell

#2 isn't as obvious for the Pi 3. I assume most people boot them headless. My second Pi 3 is broken, so I am unable to reproduce on other hardware. It clearly is not a boot loader problem. It is present with u-boot and native loaders.

Thanks. You've made this problem very clear and now I'm aware of what I need to do in order to reproduce it. Although I won't be spending any time doing so, this hiccup may be worth including in the sarpi installer guide for users who experience the same issue(s). First I'll wait until Stuart releases the new versions of Slackware ARM and AArch64 and see what's what before updating and/or revising any existing content. It may be that the sarpi project becomes redundant and superfluous, and then I'd be wasting even more of my time needlessly. Free time to play around is something I don't have a lot of these days. Sadly.

I had the installer puke the same way when I installed to a Raspberry Pi 400. Since I've installed Slackware many, MANY times, with all sorts of digital vomit at times, I automatically tried Alt-F2, and then Alt-F3, having rebooted the install initrd.gz a couple times until I was happy. I advise folks to look into chrooting their install session, just to make SURE everything is satisfactory before they attempt booting for any serious work.



I'm currently building some sbopkgs to get some favorite amenities in place. Once I'm happy with the system I've made, I'll probably dd it to my server RAID, then copy it for another RPi 4 I got for my daughter via her grandad's generosity.



How many 6 yr old girls have SARPis tailored to them for Christmas? I delight in teaching mine that its GREAT to HACK and SLACK!

2 members found this post helpful.

If you have a spare Micro SD card, can you xzcat the Slackware AArch64 Installer to it, and try booting on the Rpi?

ftp://ftp.arm.slackware.com/slackwar...15.14_1.img.xz

SA64 isn't released so you can't install the OS, I'm just curious if the display issues exist.

My 11yr old has agreed to follow the Slackware AArch64 installation docs for the RPi and do the installation guide video for it!

3 members found this post helpful.

I gave this image a quick test last night and used HDMI mode (enabling console=tty1, networking, etc.) and it boots very well. I'll try to find time to look deeper into it over the coming weekend because I was logging in remotely over SSH and when I was using 'cfdisk' to setup partitions there was no selection highlight visible on my screen in the TUI. You know the one where you use the cursor keys to select [ new ] or [ type ] at the bottom, and the list of partitions at the top, and the function is highlighted by black text with a white background? That's what I mean was missing. It worked perfectly but I had to guess what was selected from the screen info, with a bit of trial and error. Not sure if that's something I have caused or not. In any case, I got to the installation media dialog and setup worked extremely well, and as expected, up to that point.

Throwing your daugter in at the deep end, huh? Hehe. I'm sure she'll have little trouble in doing it with a few pointers from Dad. I think it's a brilliant idea and will look forward to seeing this Slackware AArch64 video install guide.

You do not need to change any settings - it works with Linux Virtual Consoles (HDMI), UART and SSH (assuming it's got an IP) automatically.