-current64 install hangs at keyboard map select (pressing Return or 1 just hangs)
by forkosh from LinuxQuestions.org on (#4Q8GA)
The box is an older VivoPC VM62N-G050R, https://www.amazon.com/Asus-VM62N-G0.../dp/B00QKH1KMO And I'd already successfully installed slackware -- twice: first 14.1x64 (which was the most recent stable when I bought the box), and much more recently -current64 (current as of March 20, 2019). And everything was running fine until a few days ago...
...then, suddenly, nothing booted, not even the original pre-installed win8.1 that was dual-booting with both slacks. Turned out the hard drive had worked loose from its sata connector. I'd vertically installed the small box on back of an hdtv, and plugged its video into one of the tv's hdmi inputs. And unknown to me, until I opened the box, that vertical orientation has the disk hanging down from its sata connector. So I reseated the disk, and added a shim between its bottom and the case to prevent a recurrence. But when I booted, win8.1 came up, despite slackware having been set as first in the uefi boot order.
Rebooting and going into the bios showed no more slackwares. They'd disappeared and nothing I tried could recover them. So I decided to reinstall, and the usb install stick seemed to boot fine. But then, as per the Subject, it printed the keyboard map select message, and then hung. That happened several times, with several different slackware install usb sticks.
I had a spare sata drive lying around, and swapped that in. Then I successfully booted a gparted usb stick to reinit that disk, new partition table (msdos this time, no uefi) and new partitions. And gparted worked just fine. But then the slackware install did the same darn thing all over again. And I'd flipped the bios to legacy/csm, and made sure secure boot was off.
So at this point I'm at a loss what to try next. As mentioned above, I'd successfully installed slackware, and had been running it for ~4 years with no problems. Why would the install suddenly behave like this? -- both with the original uefi disk, and with a "clean" disk. Could that original disk working itself loose have damaged something, hard or soft?...
My best guess was that reseating the disk caused the bios to reset, and then I somehow missed some bios setting that needs to be changed. But I easily got slackware booting originally. And I carefully went through everything again, several times, and even flipped various things several ways just to experiment. Nothing works, always hangs at that keyboard map select. Any suggestions, either bios-wise or otherwise??? Thanks,
John
...then, suddenly, nothing booted, not even the original pre-installed win8.1 that was dual-booting with both slacks. Turned out the hard drive had worked loose from its sata connector. I'd vertically installed the small box on back of an hdtv, and plugged its video into one of the tv's hdmi inputs. And unknown to me, until I opened the box, that vertical orientation has the disk hanging down from its sata connector. So I reseated the disk, and added a shim between its bottom and the case to prevent a recurrence. But when I booted, win8.1 came up, despite slackware having been set as first in the uefi boot order.
Rebooting and going into the bios showed no more slackwares. They'd disappeared and nothing I tried could recover them. So I decided to reinstall, and the usb install stick seemed to boot fine. But then, as per the Subject, it printed the keyboard map select message, and then hung. That happened several times, with several different slackware install usb sticks.
I had a spare sata drive lying around, and swapped that in. Then I successfully booted a gparted usb stick to reinit that disk, new partition table (msdos this time, no uefi) and new partitions. And gparted worked just fine. But then the slackware install did the same darn thing all over again. And I'd flipped the bios to legacy/csm, and made sure secure boot was off.
So at this point I'm at a loss what to try next. As mentioned above, I'd successfully installed slackware, and had been running it for ~4 years with no problems. Why would the install suddenly behave like this? -- both with the original uefi disk, and with a "clean" disk. Could that original disk working itself loose have damaged something, hard or soft?...
My best guess was that reseating the disk caused the bios to reset, and then I somehow missed some bios setting that needs to be changed. But I easily got slackware booting originally. And I carefully went through everything again, several times, and even flipped various things several ways just to experiment. Nothing works, always hangs at that keyboard map select. Any suggestions, either bios-wise or otherwise??? Thanks,
John