PCLOS 2010 remaster - keyboard not recognised

[Jankers]

HI all,

Unable to find any previous report on this error.

I made a remaster, and burned to cd, all procceses worked fine; (mylivecd --lzma --nodir=^/home/jasper)

On booting from cdrom the package proceeds but i noticed a "failed" against "starting Hal Deamon" during the boot prosess; this has happened on several attempts to produce a remaster iso.

Then, on the Language screen, the cursor will not respond, either from the keyboard (up/down and return fail to operate), or from the mouse; a total freeze. Neither control-alt-backspace or cont-alt-del work; the keyboard is  not recognised at all.

Just to confuse things though, it is recognised at the beginning of the boot process, it does respond at the menu stage and also later when the num-lock lights up during the boot sequence; the num lock continues to operate for a short while thereafter.

Tried it under vbox (ose from repro) and got same response.
The total package is 2.2gb, (i have Open office included) and am using kernel  2.6.32.11-pclos2.bfs.

anyone any ideas?

J.

[siddhx]

I am also facing a similar issues .

But by logging using the "3" as addtional parameter in grub at startup ., I was able to login at console .

Then
using the command , "/etc/init.d/haldaemon on"

and using startx ..
resolved the issue .

Issue is related to the starting of services of avahi daemon and haldameon ..

Somebody help ... as we are trying to create a remaster but the problem keeps creeping in .

This solution is for technical fellows but not for noobs whom we want the remaster to use .

Kindly help.

[Jankers]

I am also facing a similar issues .

But by logging using the "3" as addtional parameter in grub at startup ., I was able to login at console .

Then
using the command , "/etc/init.d/haldaemon on"

and using startx ..
resolved the issue .

Hum, tried this (my keyboard allowed me to select "consul" from the menu) and found the "on" element of haldaemon not to work, used several of the options, then startx which brought me to the desktop but still no mouse or keyboard working.
Several attempts using etc/init.d/haldaemon start/restart/condrestart all produced the same error message-"failed"

J.

[pags]

Had you changed any of the default services, prior to doing your re-master (such as haldaemon, for instance)?  Might want to check against one the Live-CDs to see what is running, and make sure you have those enabled to start at boot, so they'll be running in your re-master...

[Jankers]

Hi Pags,

A good point.

I did change some settings, the ones Texstar mentioned in another post, bit the haldeamon is still set to run at boot.

It is very odd, the keyboard responds in the early stages of boot, and the num-lock is switched on during the process.
I am about to reconfigure the machine when a new hard drive arrives and will take the opportunity to load the 2010.1 version
rather than the 2010 original (subsequently updated) currently running, and see if that solves the problem.

J.

[Sleepy]

I am also facing a similar issues .

But by logging using the "3" as addtional parameter in grub at startup ., I was able to login at console .

Then
using the command , "/etc/init.d/haldaemon on"

and using startx ..
resolved the issue .

Issue is related to the starting of services of avahi daemon and haldameon ..

Somebody help ... as we are trying to create a remaster but the problem keeps creeping in .

This solution is for technical fellows but not for noobs whom we want the remaster to use .

Kindly help.

Are there any fresh ideas with this problem as I'm experiencing the same?
However,my keyboard and mouse wont function after 'startx'.

[johnmart]

Hi all...
I can't offer specific help toward your various issues, but I experienced unusual remasters when I excluded my /home. My intent was to create a remaster with a desktop closer to the original iso. But the remasters resulted in strange desktop appearance. I figured that excluding home, skipped some important hidden files. (I could be wrong about that)

I created a guest user, & ran mylivecd from there. From there on I got consistent good results.

Again, this may be of no help to you, but since my experience with excluding /home produced unusual results I thought to mention my experience.
btw, are you fully updated? I noticed an updated mylivecd in a recent update.