Unable to install edgy as keyboard doesn't work

Hello Noiano,
if you boot the LiveCD there comes up a start screen with some choices. Have you seen at the bottom of the screen the F-keys? There is the possibility adjust the language, keyboard layout and screen resolution (if your resolution doesn't appear get the highest possible for your hardware). Have you configured this setting before you go on to boot the LiveCD?

Mr Canis

Yes, I did set language and keyboard layout but it hasn't work many times. In the end i succeeded to install kubuntu and now I am writing from kubuntu. I have modified the xorg.conf as told by a friend of mine. There are two weird things I would like to tell you:

1. The keyboard still works only sometimes. When it doesn't I reboot and I keep attention on turn <Num Lock> off because doing this the keyboard works in many cases....why???

2. When, using kde, I select "turn computer off" after few moments what i get is the monitor turned off and nothing more...the computer seems frozen. If I end the session before and after I choose "turn pc off" then the shutdown is successfully.

Here is my xorg.conf http://www.filefactory.com/file/e7a7da/ you will find two files xorg.conf and xorg.conf.back which is the original file. I have edited line 50 and another line near there.

Thanks for your help

Hello Noiano,
that sounds for me like a acpi problem. Have you tried the following
boot parameter:

- acpi=off
- pci=noacpi
- pci=nobios

No all at once, one after one. You can do this by doing the following:

- Start your computer
- at the first screen quickly move to that kernel entry whom you usually use
- type 'e' you get a new screen, go to the kernel entry type 'e' again
- now you are in edit mode
- go at the end of the line and delete all parameter except the parameter ro
- now type one of the suggested parameter
- press return
- type 'b'
- now the system should boot

after every boot save the kernel messages in a separate file. You can do
this with: dmesg > FILENAME_NR.txt
You can then post this files. Make a notice which parameter produced
which kernel messages.
I hope that was understandable. If not, feel free to ask.

Mr Canis

___________________________________________________________
All New Yahoo! Mail � Tired of Vi@gr@! come-ons? Let our SpamGuard protect you. http://uk.docs.yahoo.com/nowyoucan.html

Before all let me say tank you so much for your time, your patience your being so kind to help me. Your isructions were clear enough. That's what I did:
I have saved the dmesg output to different files in this way:

dmesg_first refers to acpi=off
dmesg_second refers to pci=noacpi
dmesg_third refers to pci=nobios

Let's start:

1. acpi=off
As told i removed all parameters save for ro: this was the kernel command line root=/dev/sdb3 ro acpi=off..is this correct? if I had removed root=/dev/sdb3/ I think the system wouldn't have booted, right?

The keyboard worked but there were some strange things
- On kde's logout windows new item appeared there were these buttons:
 -end current session
 -turn off computer
 -restart computer
 - suspend computer
 -hibernate computer (the new one)

- If I click on turn off computer there is no need to end the session because no black screen appears. However the pc doesn't turn off...this lines are displayed:
 bla bla bla
 terminating all remaining processes
 will now halt
 [1130,682209] system halted

and that's it...no power down...if i choose restart the system is restarted.
PS: no progress bar, no splash screen and the system seems to be a little slower in responses

2. pci=noacpi
Kernel command line: root=/dev/sdb3 ro pci=noacpi
The kde's logout windows has the usual buttons:
 -end current session
 -turn off computer
 -restart computer
 - suspend computer

Reboot ok, i haven't tried the shutdown, is that important?

3. pci=nobios
Kernel command line: root=/dev/sdb3 ro pci=nobios
On kde's logout windows new item appeared again there were these buttons:
 -end current session
 -turn off computer
 -restart computer
 - suspend computer
 -hibernate computer (the new one)
shutdown ok.

After these trials i have booted 3 times with the normal parameters and keyboard didn't work even deactiving num lock. Then i have tried again the latest setting and noting...then i tried the first and here i am...

Thanks so much

ops i forgot the files...here they are http://www.filefactory.com/file/fbc6e0/

Hello Noiano,
please can you do a normal boot. After the graphical login appears press CTRL+ALT+F1. You are now on the first console. Login with your user name and password and type:

dmesg > dmesg_normal.txt

and post the output.

To your questions: You did all right.
For now I would say that your keyboard isn't recognize. The kernel recognized it as AT keyboard but you have a PS2 keyboard. So it could be very simple: Try this:

- Start your computer
- press ESC or F1 to launch the bios settings
- And then have a look for a entry usb keyborad emulation or something like that, turn them on
- Exit and save

Perhaps after that all works. If you have problems, feel free to ask.
If that not helps please post your hardware description (Mainboard, Processor etc.)
That is important to compare what the kernel recognized and what hardware is really there.

Thanks,
Mr Canis

http://www.filefactory.com/file/e72c0b/ this is dmesg_normal
(i had to reboot 6 times before the damn keyboard worked)

I have looked in the bios for something related to the keyboard but i found nothing important. Just 3 setting for the typing speed and the num lock...nothing related to emulation or something like that.

I will now give you a list of the installed hardware:

motherboard: asus p4pe
processor: intel pentium IV 3.06 Ghz HT
RAM: 1 GB
storage media: 2 maxtor sata hard disk 120GB each connected through a promise satatx2 controller (pci)
MOUSE: microsoft intellimouse optical usb
Video card: ati radeon 9500pro
Audio card: integrated in the motherboard
Network interface: integrated in the motherboard
Optical devices: pioneed dvdrw dvr107d
                         teac cdrw w552e

I hope this help to find a solution to this problem...

Hello Noiano,
the main problem is the acpi. This code is buggy, because the developer haven't use the intel compiler but the MS. That's a problem in a lot main board especially in laptops. That to fix isn't simple.
I would suggest the following:
- try kernel parameter atkbd.set=3 . That should select the PS/2 code in the kernel. And if that works, try a combination of this parameter with one of the above mentioned parameter and then remember the best result. The next step would be to make this parameter permanent. But first I would recommend to try this out.

To your question earlier: Yes it is correct that you haven't a progress bar or splash screen this feature had we disabled, because we wanted see what happend. But if we found a work around we can simple switch this feature on. It's the parameter splash.

Thanks for your patience,
Mr Canis

before i try that parameter i would like you to check the xorg.conf because a friend of mine told me to modify that file in order to solve the keyboard problem...could this modify give problems?
http://www.filefactory.com/file/9c2d3b/

PS: in the file you will find also the original xorg.conf...the just check the line 50 (marked by a #) and the keyboard driver named "keyboard" instead of kbd

PPS: if i choose the parameter acpi=off and i press the power button on my pc case the pc turns off immediately with no power down session...

Hello Noiano,
have you tried your changed xorg.conf? What is the result?
But I have you so understand, that the keyboard doesn't works at all, not on the console and not in the desktop. The changes in the xorg.conf have only effect in the desktop.

To your question: Yes you can try both parameter.

The following configuration looks for me good:

Section "InputDevice"
 Identifier "Generic Keyboard"
 Driver "kbd"
 Option "CoreKeyboard"
 Option "XkbRules" "xorg"
 Option "XkbModel" "pc105"
 Option "XkbLayout" "it"
 Option "XkbOptions" "lv3:ralt_switch"
EndSection

To test follow this order:
Boot with my suggested kernel parameter and the original xorg.conf. After the graphical login press CTRL+ALT+F1 that should you bring to the first console. If that not works, boot in recovery mode, take in mind that you first edit this entry. After you have edit this entry the parameters should be 'ro atkbd.set=3 single' . In that mode the graphic don't start and you can see whether the kernel parameter have any effect or not. You should first have a working keyboard on the console and then we take care of the graphic.

Sorry for the delay, but I had a other trouble shooting session. Computer are only humans too. ~;)

Mr Canis

I think you need some explanations to help me in my problem: when i installed kubuntu i was unable to use the kde because the keyboard didn't work. So i was unable to select the consolle through the ctrl+alt+F1. I could only use the mouse and select "consolle login" but even in the consollle login the keyboard didn't work. Before asking your help i call a friend of mine who told me to modify the xorg.conf because he had though it was only a grafic server problem. To modify the xorg.conf I used the recovery mode and using this the keyboard has always worked...no need to modify the boot parameters! So far nothing has changed! If i boot with the "normal kernel" most of times the keyboard doesn't work, if I boot in recovery mode the keyboard doesn't work.
Modifying the xorg.conf changed nothing in the end.

I have tried the 'ro atkbd.set=3 single' using the normal kernel but the graphic server doesn't start....seems like having chosen the recovery mode because i get a root consolle and no request of login.

Hello Noiano,

-- Quote begin
To modify the xorg.conf I used the recovery mode and using this the keyboard has always worked...no need to modify the boot parameters! So far nothing has changed! If i boot with the "normal kernel" most of times the keyboard doesn't work, if I boot in recovery mode the keyboard doesn't work.
-- Quote end

In recovery mode works or doesn't work?

My thought was, if the parameter atkbd.set=3 works, than it had like to be working in the graphic. But if it in recovery mode works without any changes than it is a xserver problem.
Now you have tried the recovery entry (the parameter single indicates that). That's ok that the graphic server doesn't start in that mode. Have the parameter any effect?

Mr Canis

Hello mr canis and thanks again for your patience

-- Quote begin
In recovery mode works or doesn't work?
-- Quote end

Yes it works, it has always worked with any changes. When I tried the new parameter i didn't know that "single" indicates recovery mode so when i got the same consolle i get using recovery mode(root consolle to be precise) so i though to have made a mistake and i reboot. Then i choose with more attention the "normal" entry and I modified the parameter: same result. Seems like the two entries normal and recovery have the same "effect" using the parameter (with single)you suggested.
However I also tried the parameter without "single" and the keyb worked also with the xserver.

Using the recovery mode the parameter is unuseful, in my opinion, because the keyboard works always, every time, no exception with no changes to parameters (which are /boot/vmlinuz-2.6.17-10-generic root=/dev/sdb3 ro single)

The fact that maybe a xserver problem was told to me by the person who advised me to modify the xorg.conf: as you know the changes didn't solve the problem otherwise I wouldn't have opened this ticket.

Thanks again!

Hello Noiano,

-- Quote begin
However I also tried the parameter without "single" and the keyb worked also with the xserver.
-- Quote end

Then the problem is solved. Now the last step is to make this settings permanent. For that you must edit /boot/grub/menu.lst. Change the line

# defoptions=quit splash

to

# defoptions=atkbd.set=3 quit splash

Now run the command

update-grub

That's all. Now should your system boot with this parameter.

Mr Canis

Hello Noiano,
that makes me happy to hear. Sometimes it's a difficulty birth.

If you have problems again, feel free to ask.

Mr Canis

Hello,
I have been having a similar problem. But the problem is that my mouse is not detected. My keyboard also had the same problem, but I fixed that using the advice given here.

My mouse is a logitech ps/2 mouse. It got detected once when I tried reconfiguring the xserver but am unable to do it now.

Is there a kernel option similar to atkbd.set=3 for a mouse? Or can xserver be reconfigured to get it right?

Hello donatello,
first you should open a new request. You can do it by clicking on the left upper menu 'request support'. But what I just read in Documentation/kernel-parameters.txt was this:

 psmouse.proto= [HW,MOUSE] Highest PS2 mouse protocol extension to
   probe for; one of (bare|imps|exps|lifebook|any).
 psmouse.rate= [HW,MOUSE] Set desired mouse report rate, in reports
   per second.
 psmouse.resetafter= [HW,MOUSE]
   Try to reset the device after so many bad packets
   (0 = never).
 psmouse.resolution=
   [HW,MOUSE] Set desired mouse resolution, in dpi.
 psmouse.smartscroll=
   [HW,MOUSE] Controls Logitech smartscroll autorepeat.
   0 = disabled, 1 = enabled (default).

I would try the first one: psmouse.proto=any

But I assume that this doesn't solve the problem, but perhaps you have luck. If it doesn't work please open a new ticket, how mentioned above.

Thanks,
             Mr Canis