[Solved] Installed 64 bit Mageia 4 - now fails to boot

[mark9117]

I installed the 64-bit version and installed the server kernel. When I rebooted, I hit an error and udev couldn't mount my file systems and the box dropped to a debug shell. I would have pursued that, but I had *no usb keyboard or mouse*.

The lack of input devices is a show stopper. I have no options. Fortunately, the original kernal (don't recall what it is, something really generic) will allow me to boot and operate. By now, I've been struggling with this for hours and I'm exhausted. It's 2:30 in the morning and I'm still downloading initial updates. I'm crossing my fingers and hoping that updates will solve some of this, but it seems like wishful thinking.

I will try to deal with it tomorrow after work, but if anybody has any ideas about how to approach this issue, I'd really appreciate hearing from you.

Thanks.

Mark

[doktor5000]

Why do you want to use the server kernel at all if the original kernel works?

[mark9117]

Why do you want to use the server kernel at all if the original kernel works?

Historically, I've had better memory management with the server kernel.

I should also mention that the desktop 586 kernel fails to boot with the same issue. An incidental issue here is that my kvm switch stopped working when I updated to the 64-bit version (not taking an address according to the journal). I was hoping that a different kernel would resolve that issue.

So, now I have two issues.

I have to quit this and go to bed, but I take it from your reply that I'm stuck with the desktop-3.12.8-2mga kernel forever?

Mark

I'm going to bed now. Really this time. Bed.

[doktor5000]

I take it from your reply that I'm stuck with the desktop-3.12.8-2mga kernel forever?

Well, without more context information, what other reply can I provide? You mentioned that the desktop kernel works, and for the others you have no keyboard input at all.

You don't mention what mainboard you use, what input devices and how they are connected, including the KVM switch ...
Problem probably comes not directly from the kernel at all - you mentioned

When I rebooted, I hit an error and udev couldn't mount my file systems and the box dropped to a debug shell

udev doesn't mount filesystems, it only creates device nodes. If e.g. it can't create any node under /dev or if /dev cannot be mounted then input is probably your least problem.

[mark9117]

Yeah, I think I mentioned it was around 3:00 am here when I posted that. The hour was late, panic was high and I was scrambling to get something, anything, working. I'm rebuilding systems here and my desktop blowing up was the last thing I needed. But it has passed and things seem to be ok. I have to go to work now, but updates have been applied and I'll test kernels when I get back.

At any rate, I agree that failed input was only an item on the list of symptoms and there was more going on. I reseated the cables on the kvm switch and resolved that whole issue. I think this may work out. Will know later. If not, more info will be forthcoming.

Thanks again for the attention. I do appreciate it.

Mark

[mark9117]

Okay, this appears to be fixed. I think I know what happened and it's my fault. I believe the issue resulted from my installing a kernel prior to updating a new installation. Tonight I uninstalled the kernel and reinstalled it after fully updating the system last night and I can now boot that kernel.

Not my most elegant installation by far, but it's working.

Thanks again.

Mark

[jiml8]

I have found that virtual machines eliminate all need for KVM switches.

You need a higher horsepower computer, but that beats having many boxes sitting around sharing monitor and keyboard.

[mark9117]

I have found that virtual machines eliminate all need for KVM switches.

You need a higher horsepower computer, but that beats having many boxes sitting around sharing monitor and keyboard.

Glad that works for you. If I gave up the file server attached to the other side of the Kvm switch in favor of a vm on my desktop, every time the desktop goes down I lose the gateway to my network, media files for my htpc, and the backup desktop I use to get my primary machine back up and running.

Doesn't really seem to work for me. I think I'll stick with the topology I have.

Mark