From owner-freebsd-current@FreeBSD.ORG Sat Apr 20 23:42:04 2013 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by hub.freebsd.org (Postfix) with ESMTP id E8A8993A for ; Sat, 20 Apr 2013 23:42:04 +0000 (UTC) (envelope-from jrisom@gmail.com) Received: from mail-ie0-x22c.google.com (mail-ie0-x22c.google.com [IPv6:2607:f8b0:4001:c03::22c]) by mx1.freebsd.org (Postfix) with ESMTP id BC85012FB for ; Sat, 20 Apr 2013 23:42:04 +0000 (UTC) Received: by mail-ie0-f172.google.com with SMTP id c12so1933980ieb.17 for ; Sat, 20 Apr 2013 16:42:04 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=x-received:message-id:date:from:user-agent:mime-version:to:subject :references:in-reply-to:content-type:content-transfer-encoding; bh=FenOy4nP96lAkxCXoFfHDNBdxn8Sa+byQFlPshkhXHc=; b=oLOwyNCwRgNJr7RGbvsz8hNYKXwkDVbq6LqGJNonigOO1irYcDt32BrJCq7IqNTlAI nSbzrnPTZPZn2BM1vf7PAv5eWkJ/Flt5yzbWy9X9Pu4dxoe5xxdA3voOx6Ocl2QWI0B8 qtkXm5kbfzleYsWGI52wtIPBLKi1AA3Us+fEmKfAoEY6gqjgJQaNf8ysZbvWSU6+HtC6 kSZtBrJwMCMn3dDSQXj8lDjSuqfyv7jbTa8eKb/jNhoFY7FXG5u/al/nHWE6vj0nZ9qo oV+8rw2bTMu88XYtqkAGumd+Zazgf6fCzaMS6fl3nKSKzqnPYbDNfElXFwA5uU4d3ANU bipg== X-Received: by 10.50.100.201 with SMTP id fa9mr17712732igb.28.1366501324459; Sat, 20 Apr 2013 16:42:04 -0700 (PDT) Received: from [192.168.1.34] (c-98-212-197-211.hsd1.il.comcast.net. [98.212.197.211]) by mx.google.com with ESMTPSA id qn10sm9317503igc.6.2013.04.20.16.42.02 for (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Sat, 20 Apr 2013 16:42:03 -0700 (PDT) Message-ID: <517327C5.5050305@gmail.com> Date: Sat, 20 Apr 2013 18:41:57 -0500 From: Joshua Isom User-Agent: Mozilla/5.0 (Windows NT 6.2; WOW64; rv:17.0) Gecko/20130328 Thunderbird/17.0.5 MIME-Version: 1.0 To: freebsd-current@freebsd.org Subject: Re: Booting an alternative kernel from loader prompt fails the first time only References: <625362A8116D4B43AF4912773F478CB9@multiplay.co.uk> <5172C699.8020708@smeets.im> <5172CF44.1050309@gwdg.de> <201304201741.r3KHfrJe001805@pozo.com> In-Reply-To: <201304201741.r3KHfrJe001805@pozo.com> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 20 Apr 2013 23:42:05 -0000 On 4/20/2013 12:41 PM, Manfred Antar wrote: > At 10:24 AM 4/20/2013, Rainer Hurling wrote: >> On 20.04.2013 18:47 (UTC+2), Florian Smeets wrote: >>> On 20.04.13 18:05, Steven Hartland wrote: >>>> When trying to boot an alternative kernel from the loader prompt >>>> it fails the first time the command is run but succeeds the second >>>> time. >>>> >>>> Type '?' for a list of commands, 'help' for more detailed help. >>>> OK boot kernel.generic >>>> Booting... >>>> don't know how to load module '/boot/kernel.generic/kernel' >>>> OK boot kernel.generic >>>> Booting... >>>> /boot/kernel.generic/kernel text=0xd21288 data=...... >>>> >>> >>> Yes, I've been seeing the same thing for about 6-12 months maybe more. >>> None of the people I asked were able to confirm, so I'm happy that I'm >>> not imagining it :) >> >> I also can confirm this behaviour for month now (on 10.0-CURRENT amd64 >> with clang). >> >> Rainer >> > > Have you tried: > OK boot /boot/kernel.generic/kernel > > Use full path name always works for me > Manfred > I couldn't get any other method to work. I can also confirm this. While working with Adrian testing ath changes, I frequently had to reboot into an old kernel(/boot/ATH/kernel, full path seemed required) to regain networking unless I physically moved the computer to add ethernet. Also, it's really annoying when I would have to manually kldload each module in order, especially opensolaris.ko and zfs.ko, and making sure I loaded /boot/ATH/if_ath.ko before /boot/ATH/if_ath_pci.ko or else the loader would load from /boot/kernel instead of /boot/ATH and I'd end up with broken networking even though the kernel was right. I'd really love it if there were a way for modules to be bundled with the kernel file and loaded from the kernel instead of the filesystem, especially since many modules can't be compiled in. As a side note, my /boot/loader is from -STABLE, mod time of January 24 this year. This could be an issue on -STABLE also.