On 08/09/20 19:30, Mark Johnston wrote:
> On Tue, Sep 08, 2020 at 07:24:38PM +0200, Guido Falsi wrote:
>> On 08/09/20 10:01, Guido Falsi wrote:
>>> Hi,
>>>
>>> I'm trying to update to recent head, but I can't boot my system with the
>>> compiled kernel.
>>>
>>> The system has ZFS on root and was
On 08/09/20 19:30, Mark Johnston wrote:
> On Tue, Sep 08, 2020 at 07:24:38PM +0200, Guido Falsi wrote:
>> On 08/09/20 10:01, Guido Falsi wrote:
>>> Hi,
>>>
>>> I'm trying to update to recent head, but I can't boot my system with the
>>> compiled kernel.
>>>
>>> The system has ZFS on root and was
On Tue, Sep 08, 2020 at 07:24:38PM +0200, Guido Falsi wrote:
> On 08/09/20 10:01, Guido Falsi wrote:
> > Hi,
> >
> > I'm trying to update to recent head, but I can't boot my system with the
> > compiled kernel.
> >
> > The system has ZFS on root and was working with previous kernel (before
> > Op
On 08/09/20 10:01, Guido Falsi wrote:
> Hi,
>
> I'm trying to update to recent head, but I can't boot my system with the
> compiled kernel.
>
> The system has ZFS on root and was working with previous kernel (before
> OpenZFS migration).
>
> I'm trying to boot r365437.
>
> I load zfs from loade
Hi,
I'm trying to update to recent head, but I can't boot my system with the
compiled kernel.
The system has ZFS on root and was working with previous kernel (before
OpenZFS migration).
I'm trying to boot r365437.
I load zfs from loader with zfs_load="YES" as usual and get this error
message at
iginal Message -
> From: "Mike Smith" <[EMAIL PROTECTED]>
> To: "Douglas Kuntz" <[EMAIL PROTECTED]>
> Cc: <[EMAIL PROTECTED]>
> Sent: Friday, November 26, 1999 3:32 AM
> Subject: Re: Boot error
>
>
> >
> > First things
(or worse)
half the time, and I have to remember when to talk/type normally.
Doug
- Original Message -
From: "Mike Smith" <[EMAIL PROTECTED]>
To: "Douglas Kuntz" <[EMAIL PROTECTED]>
Cc: <[EMAIL PROTECTED]>
Sent: Friday, November 26, 1999 3:32 AM
Subje
First things first; try using English for your problem reports. A large
slice of the community that might be able to answer your questions don't
use it as their first language, and by using leet-speek you immediately
eliminate them as a source of help.
> Before I go do a fresh SNAP install,
Before I go do a fresh SNAP install, I wanted to see if there was an easier
way to fix this problem...
My -current box was a celeron...I had to switch the celeron and mboard to my
windoze machine to get a vidcard werkin...I recompiled the kernel to 486,
586, and 686, and moved the HD, the cards, e
Ayan George wrote:
> Ever since installing 4.0-CURRENT, I've gotten the following
> message when I boot FreeBSD:
>
> Disk error 0x1 (lba=0x12007f)
> No /boot/loader
>
> >> FreeBSD/i386 BOOT
> Default: 0:wd(0,a)kernel
>
> boot:
>
>
> If I type:
>
> wd(0,a)/boot/loader
>
> at the boot p
Ayan George wrote:
>
> Ever since installing 4.0-CURRENT, I've gotten the following
What were you running before? How did you make the upgrade?
--
Daniel C. Sobral(8-DCS)
d...@newsguy.com
d...@freebsd.org
"Well, Windows works, using a loose definition of 'works'.
All,
Ever since installing 4.0-CURRENT, I've gotten the following
message when I boot FreeBSD:
Disk error 0x1 (lba=0x12007f)
No /boot/loader
>> FreeBSD/i386 BOOT
Default: 0:wd(0,a)kernel
boot:
If I type:
wd(0,a)/boot/loader
at the boot prompt, it claims it cant find the file but I k
12 matches
Mail list logo