Last night, after running the -current updates, I forgot to run lilo after editing lilo.conf and making a new initrd. No biggie, right?

I insert an install disk and use huge.s to boot to my partition. So far, so good. Everything looks normal. The problem now is I have no keyboard or mouse at the login prompt. Tried again to insure no typos and same result.

Booting the install disk without huge.s and I have keyboard and mouse support. I simply mounted my partition and used chroot to be able to run lilo.

I'm just wondering why huge.s didn't work. That would have saved me a couple of steps. The install disk was from 5/18/2018. Making a new one from -current now.

Sorry, I don't have an answer, but I just wanted to say that it can't be solved if there's no answer as to why huge.s didn't work and that while it is marked as solved you may never get an answer.

212 people have viewed this thread. That means that 212 probable Slackware users have no idea why huge.s did not provide usb keyboard and mouse support. The installer disk being used as a rescue disk loaded an initrd. Why would an initrd be necessary for a huge kernel?

The thread was marked solved because I don't have a problem - I fixed it using a different method, I was just curious about using a Slackware disk to boot the system. The disk itself tells you what to do, it just didn't work.

I tried a Slackware disk from 7-26-16. Wasn't even close to trying to boot. I'm guessing its because I do not have the original kernel that came with the disk. I think that is the only way the disk will boot as a rescue disk. I'm going to try again using the disk from the -current update I did yesterday. Back in a few.


Back now. It booted just fine from the new disk created yesterday. No network, but I could have started that manually. I think I would have to keep the kernel modules from the original install to make it work as a rescue disk.

I'm pretty sure it's because for huge.s the config sets all usb stuff modules.(see http://slackware.uk/slackware/slackw.../huge.s/config)

Sorry, I just wanted to help you get an answer.

1 members found this post helpful.

I may have answered my own question, just did not receive any confirmation on my theory. It does not matter since I can solve this another way. Been using lilo for years. That's only the second time I've failed to run lilo. Sorry if I came off like a yard biscuit.

1 members found this post helpful.

Only the second? Wish I could say that. <grin> It's been a while though since my last brain misfire; with lilo anyway. LOL

2 members found this post helpful.

I remembered after today's updates! lol