Gentoo Websites Logo
Go to: Gentoo Home Documentation Forums Lists Bugs Planet Store Wiki Get Gentoo!
Bug 309187 - PS/2 connected keyboard stops working when booting from install-alpha-minimal-20100227.iso
Summary: PS/2 connected keyboard stops working when booting from install-alpha-minimal...
Status: RESOLVED FIXED
Alias: None
Product: Gentoo Release Media
Classification: Unclassified
Component: InstallCD (show other bugs)
Hardware: Alpha Linux
: High normal (vote)
Assignee: Gentoo Release Team
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2010-03-12 21:13 UTC by Eric Nichols
Modified: 2011-06-19 14:42 UTC (History)
1 user (show)

See Also:
Package list:
Runtime testing required: ---


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Eric Nichols 2010-03-12 21:13:54 UTC
I have an AlphaServer 1200 with PS/2 keyboard which works perfectly using my installed system (older version of gentoo), and in the SRM console, etc.. but as soon as it boots from the CDROM using install-alpha-minimal-20100227.iso the keyboard goes dead.

Reproducible: Always

Steps to Reproduce:
1. boot from the aforementioned iso using the cdrom drive (i.e. 'boot dka500 -flags 0' from SRM)
2. wait until you get keyboard layout prompt or the # prompt.
3. observe that the keyboard is not working at either point.

Actual Results:  
The keyboard goes dead.

Expected Results:  
The keyboard should be working.

I tried using the interactive boot in SRM and passed a 'nousb' parameter in addition to the defaults (my machine does not have USB), but it had no effect.

I also tried booting with the keyboard unplugged and then plugging it in after, and simply unplugging and plugging back in... neither of which had any effect.

My next plan is to try using serial, but I have to get a usb adapter because my laptops don't have serial ports.
Comment 1 Eric Nichols 2010-03-15 15:18:14 UTC
The system works fine via serial, but so far I have been unsuccessful in attempts to re-enable the keyboard from a serial console.

I have noticed by repeatedly toggling numlock during the boot sequence that the keyboard stops working after it begins scanning/loading modules from the initrd. They all go by too quickly to tell which one it is, but it seems to be in the first screen-full or so.  If I boot with the 'nodetect' flag, the keyboard will work fine, but no modules are loaded of course.

I am examining the scripts in the initrd to see how the modules are loaded, and then I'm going to try testing them one at a time on the alpha to see where the keyboard stops working.
Comment 2 Eric Nichols 2010-03-16 12:26:03 UTC
I don't know what is going on... I went to interactive boot, did nodetect, and then started loading modules one at a time from the shell, in the same order that the init script would do it, and none of them caused the keyboard to stop working even though I went a long way past where the keyboard stops working during the "normal" boot.
Comment 3 Angelo Brigante, Jr. 2010-03-16 18:30:18 UTC
(In reply to comment #0)
> Steps to Reproduce:
> 1. boot from the aforementioned iso using the cdrom drive (i.e. 'boot dka500
> -flags 0' from SRM)
> 2. wait until you get keyboard layout prompt or the # prompt.
> 3. observe that the keyboard is not working at either point.
> 
> Actual Results:  
> The keyboard goes dead.
> 

I had the same exact issue with a Personal Workstation 500au using a PS/2
keyboard while booting the install-alpha-minimal-20100227.iso image.

Comment 4 Eric Nichols 2010-03-16 21:01:50 UTC
I ended up messing with the initramfs to add a pause between each module load and then rebuilt a new iso image which was otherwise identical to the one mentioned in the initial description. 

Long story short:  pata_qdi is the source of my pain.

From the SRM console I did 'boot dka500 -fl i' to get interactive mode, and then copied the default boot command and appended 'noload=pata_qdi' as an extra paramter at the end and the CD booted all the way to the # prompt with the keyboard still working!

I am not sure what the best way to resolve this bug is... but I do have a work around that works for me.  I can't tell what pata_qdi is for so I don't know if it would be appropriate to leave it out of the iso entirely or not (perhaps for some alphas it is needed?).

Comment 5 Tobias Klausmann (RETIRED) gentoo-dev 2010-03-16 21:54:09 UTC
After discussing this on IRC, we (the alpha team with our trusty sidekick Matt) decided to dump the QDI driver in future install media - it's a VLB (yes VESA Local Bus) card and there isn't any relevant Alpha with that bus. We'll also clean up any other remaining VLB-only drivers.
Comment 6 Tobias Klausmann (RETIRED) gentoo-dev 2011-06-19 14:42:39 UTC
This has been fixed for a while and there have been no new bug reports.