NetBSD-Bugs archive

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

port-i386/45596: i386 -current cd-rom image unable to boot into sysinst



>Number:         45596
>Category:       port-i386
>Synopsis:       i386 -current cd-rom image unable to boot into sysinst
>Confidential:   no
>Severity:       serious
>Priority:       high
>Responsible:    port-i386-maintainer
>State:          open
>Class:          sw-bug
>Submitter-Id:   net
>Arrival-Date:   Thu Nov 10 09:05:00 +0000 2011
>Originator:     Havard Eidnes
>Release:        NetBSD 5.1
>Organization:
        
>Environment:
        
        
System: NetBSD -current from about a week ago (Nov 1st'ish)
Architecture: i386
Machine: i386
>Description:
        A few days ago I tried to get a NetBSD-current snapshot CD-ROM
        image to boot properly on a new Lenovo T420s laptop.  That met
        with failure on a couple of fronts, but what I'm focussing here
        is the failure of the CD-ROM image to boot into the installer.

        I noticed that the boot process did not print "loading
        miniroot.kmod" before the NetBSD boot/autoconf messages were
        displayed, contrary to what the NetBSD 5.1 image does.

        I also noticed that it claimed that the boot media was "cd0", but
        it failed to mount cd0a, leaving NetBSD prompting for the root
        file system.  Apparently, the keyboard on this laptop is USB-
        based, and therefore unresponsive at that particular point in the
        boot process -- at least it *was* unresponsive, leaving me "dead
        in the water".

        So...  Somewhere along the road it appears that the CD-ROM boot
        image build got severely broken.

>How-To-Repeat:
        Try to boot a snapshot cd-rom image, watch it fail.
>Fix:
        Sorry, don't know.

>Unformatted:
        
        


Home | Main Index | Thread Index | Old Index