NetBSD-Bugs archive

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index][Old Index]

port-sparc/41194: console install problems for sparc-5rc3



>Number:         41194
>Category:       port-sparc
>Synopsis:       disappearing keyboard on install
>Confidential:   no
>Severity:       critical
>Priority:       high
>Responsible:    port-sparc-maintainer
>State:          open
>Class:          sw-bug
>Submitter-Id:   net
>Arrival-Date:   Mon Apr 13 02:25:00 +0000 2009
>Originator:     Jon Buller
>Release:        NetBSD 5.0_RC3
>Organization:
        
>Environment:
Cross built on amd64 machine from head of netbsd-5
                branch checked out or updated a day or two before
                the build date.

                This is running on a sun4m system (LX, and SS20)
                with a type5 keyboard.
        
        
System: NetBSD Sunergy 5.0_RC3 NetBSD 5.0_RC3 (GENERIC) #0: Sat Apr 4 05:59:14 
UTC 2009 
jon%xw8200.bullers.net@localhost:/usr/obj/sparc/sys/arch/sparc/compile/GENERIC 
sparc
Architecture: sparc
Machine: sparc
>Description:
        The keyboard becomes useless shortly after beginning the
        install process.
>How-To-Repeat:
        Boot a miniroot filesystem from a swap partition, or go
        through the standard netboot procedures in the install
        document.

        The system will accept keyboard input for the terminal
        type, which is the first use of the keyboard after booting
        the system.  However, the next use is to answer the question
        of Install/Update/Shell/Halt, and there is no response to
        any keypresses.
>Fix:
        It is fixable, but I do not know how.  I manually labeled
        the disks, unpacked the tar files, and configured the system
        to boot, after netbooting the 4.0.1 install files to get
        the system running far enough to do so.

        I made both disks bootable, but I am now in the unusual
        situation where booting from one disk will seemingly freeze
        the system on the first login, although ssh still works.
        Booting the other disk will result in a somewhat working
        system.  (I say somewhat as it appears there are some bugs
        in the video driver as well.)  I have not yet noticed the
        difference in the two configurations.



Home | Main Index | Thread Index | Old Index