Date: Mon, 16 Aug 2004 11:39:50 +0200 (CEST) From: Hanspeter Roth <hampi@rootshell.be> To: FreeBSD-gnats-submit@FreeBSD.org Subject: i386/70525: boot0cfg: -o packet not effective Message-ID: <200408160939.i7G9dolN000981@goofy.here> Resent-Message-ID: <200408160940.i7G9eAvX066300@freefall.freebsd.org>
next in thread | raw e-mail | index | archive | help
>Number: 70525 >Category: i386 >Synopsis: boot0cfg: -o packet not effective >Confidential: no >Severity: serious >Priority: medium >Responsible: freebsd-i386 >State: open >Quarter: >Keywords: >Date-Required: >Class: sw-bug >Submitter-Id: current-users >Arrival-Date: Mon Aug 16 09:40:10 GMT 2004 >Closed-Date: >Last-Modified: >Originator: Hanspeter Roth >Release: FreeBSD 5.2-CURRENT i386 >Organization: >Environment: System: FreeBSD goofy.here 5.2-CURRENT FreeBSD 5.2-CURRENT #2: Sat Aug 14 16:52:51 CEST 2004 uesr@goofy.here:/usr/src/sys/i386/compile/F5 i386 >Description: After running `boot0cfg -Bv -o packet /dev/ad0' the slices beyond the 1024th cylinder will be displayed but are no more accessible by the boot selector. Using an older boot0cfg (from 5.2-RC2) does work. >How-To-Repeat: >Fix: Since my FreeBSD slice is beyond the 1024th cylinder I have to boot a 5.2-RC2 rescue CD and perform boot0cfg. It works whether boot0 is taken from 5.2-RC2 or from 5.2-CURRENT (Aug 7th). The only difference is that the one from 5.2-CURRENT beeps when the menu is displayed which makes sense. >Release-Note: >Audit-Trail: >Unformatted:
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?200408160939.i7G9dolN000981>