SliTaz Forum

Guest

Guest

"requesting events from kernel" waits forever

From http://forum.slitaz.org/topic/trying-to-install-slitaz-under-24mb-ram/page/2 i've been able to install Slitaz on the hard drive by taken the hd to another machine.

Now it loads perfect until i get the message "requesting events from kernel"... it waits forever. I tried to install it again on the machine with pluggin a highest ram (256) and i get the same message.

The strange thing is that i've been able (before, Slitaz 3.0 but i could not see the hard drive - now that image doesn't boot neither) to load Slitaz on that machine (Compaq Presario 1220)... could it be an error in the ISO? The only thing i've done to the machine is remove the screen that originally comes with the laptop (it was almost dead) and now i use an external monitor, could be THAT the problem? it's an oddissey to remove/put it but if it's what makes my system hangs ill do it.

What do you think?

BTW: Slitaz rules, it flies on my Compaq 1220 (when i was able to try it

mojo

Administrator

Registered: 2011-03-29

Posts: 2,174

Re: "requesting events from kernel" waits forever

There is a bug report for  "requesting events from kernel"...

http://bugs.slitaz.org/issue1

http://bugs.slitaz.org/issue33

Same error frequently kills boot on one of my computers running slitaz-blending.iso

I have to use udev or the soundcard isn't detected so I can't comment it out in /etc/init.d/rcS

Guest

Guest

Re: "requesting events from kernel" waits forever

Sorry to ask again, but you don't think that the removal of the screen has nothing to do with it? Could it be that something was missing when i re-assembled the laptop and because of that i'm not able ANYMORE to load Slitaz?

I'm kind of "i don't know what to do" here...

Thanks for the pointing mojo

flexdream

Member

Registered: 2012-04-20

Posts: 1

Re: "requesting events from kernel" waits forever

I ran Slitaz 3 in Virtual Box fine. When I tried Slitaz 4 in Virtual Box I got stuck on 'requesting events from kernel'. Increasing the Virtual Box settings for memory from 128MB to 256MB fixed it for me.