New remaster test in Virtualbox and keyboard fails at matchbox window (Solved)

[melodie]

Hi,

I remastered a 2.6 Gb install and got an ISO 702 MB large. When trying it in Virtualbox, I can't go after the stage where it is possible to choose a keyboard and hit "next". I am using a laptop, but can't use it's original keyboard actually, I have to change it, and I use a USB Logitch keyboard, as well as a Logitech mouse. I tried them plugged in the usb hub, or directly plugged in the connectors, same.

Does someone have any trick such as a boot option I could try, in order to try to go throught this ?

In the meanwhile, I installed it to a USB stick and will try it on the machine where I did the remaster, to see if the problem is repeated.

If you have knowledge or other ideas about what can cause this event, I'm opened to suggestions.

Thanks,
Mélodie

PS: in another machine also with USB keyboard, the problem is the same. Thanks for suggests...
PS-2 : it's a fully up to date system, with kernel 2.6.38.8.pclos1.bfs

[menotu]

Hi melodie,

You could try selecting your VM and go to Settings > System > Motherboard

and tick (or untick) the Enable IO APIC setting

as that can have an affect on booting.



or/and again in Settings > System > Processor

try ticking/unticking the Enable PAE/NX feature

[melodie]

Hi Menotu,

I said in PS it's also true in another machine : I meant a real machine. I booted from Live USB and I'm still blocked at keyboard choice : mouse and keyboard don't respond.

The problem is in the system where I pulled the iso from. If I knew what kernel options I can try before going further, that would be interesting.

Thanks,
Mélodie

[melodie]

Menotu,

I tried your configurations in Vbox as well, it doesn't better. I guess I'll try to redo the iso...

PS: I have a message at the boot time, in the system source : "VIRTUALBOX: AUTOINSTALL not set in it's dkms.conf."

What can be the problems caused by this "not set" option in the dkms.conf file ? Is it likely to cause problems on the isos ?

[Linuxera]

I'm having the same problem with my most recent ISO created in VBox on one system, and trying to boot it in VBox on another system.  I haven't figured out what the problem is and I'm using PS2 mouse and keyboard fwiw.   

[Tuxfriend]

Remastering outside a VM doesn't help either: you see the keyboard choosing screen, but can't move mouse/touchpad and can't use the keyboard.

[Linuxera]

Correct.. I just tried the livecd on an actual system outside of VBox and it got to language selection... no kb or mouse.  

Oh oh!!  Look, new initrc and iomanager in the repos... maybe this will be the fix... (me is hoping so!!)

[melodie]

We once met with the same issue while building the Openbox Bonsai version, and it appeared that it was caused by portreserve needing an update on the repos. This program was a dependency to the printing packages. (the one in the isos available online had been patched by hand, probably long ago... and this is one of the people testing who found out the solution, then Texstar updated the package). The result of the unpatched package made the services be started in the wrong order : the important ones were messagebus and haldaemon, so I just looked into the system that I pulled the iso from (I'm starting the 3rd now) and the order seems correct, messagebus at position 53 and haldaemon just after at 54 (they must not be at the end and messagebus, which is dbus, must be started before, so that it starts hal).

For now I don't have any idea what causes this trouble. I just try something else and redo an iso.

[Linuxera]

I downgraded the X11 mouse driver to the previous one to begin with, and backed down to the 2.6.32.24 kernel.. I had no problems remastering with the 2.3.38.2 kernel, but when I upgraded to .6 and .8 the stuff began to hit the fan..  So, I don't know either. I'm remastering now and hopefully it will not end up being a frizbee.. 

[uggy]

Hi Melodie,

same problem here, just created mylivecd, confirmed burn etc, etc.

First line of text seen while booting is "acpi aborted because no cpio magic".

When i get to kb select, kb or mouse no work?

[AS]

Hi,

I'm  experiencing the same behavior, no keyboard, no mouse. FYI, booting at runlevel 3 the keyboard works...

AS

[menotu]

Last one I created was on 31-May-2011 which would of had the 2.6.38.7 kernel and mine is booting okay. Has x.org 1.9.5

I'm using udev 156-5 (not the updated 168.6 one) as that was causing issues with mouse and keyboard in my main systems so I dropped back to 156 and this solved it.

[She_Devil]

Nice find!!!  Thanks for sharing..

[Linuxera]

I had to look around, but Indiana hadn't caught up, so I was able to force the older version of udev... we shall see!!

[melodie]

Last one I created was on 31-May-2011 which would of had the 2.6.38.7 kernel and mine is booting okay. Has x.org 1.9.5

I'm using udev 156-5 (not the updated 168.6 one) as that was causing issues with mouse and keyboard in my main systems so I dropped back to 156 and this solved it.

Ok, I force the install of udev 156-5, the kernel is the 2.6.38.8 and I rebooted before doing anything else, once done. After reboot, no more keyboard or mouse working in the installed system. I could go to tty by using SysRq (with r option).

I won't try further with this couple udev/kernel, this is not the right solution. I might try to downgrade the kernel with the same udev still there...

Anyone else tested something that works ? (with recent packages)