You wrote:
> Try
> 1:da(3,a)/boot/loader
Maybe I'm a bit boring but it does not work ! :(
After some tests, these are the results:
1:da(0 to 3,a)/boot/loader
Invalid label
Invalid label
No /boot/loader
2:da(0 to 3,a)/boot/loader (NEXTSTEP disk)
LBA error (don't remember correctly)
You wrote:
> If
>
> 1:da(1,a)/boot/loader
>
> does not work, what is in the /boot directory on da1?
rey:/usr/home/mirko> list /boot
total 514
drwxr-xr-x 3 root wheel 512 Apr 7 02:02 ./
drwxr-xr-x 27 root wheel1024 Apr 7 11:29 ../
-r--r--r-- 1 root wheel 512 Apr 7 02:02
If
1:da(1,a)/boot/loader
does not work, what is in the /boot directory on da1?
Is the FreeBSD root directory on da1s1a? What does 'mount' show?
tomdean
# ls -l /boot
total 1
-r--r--r-- 1 root wheel 512 Apr 4 11:23 boot0
-r--r--r-- 1 root wheel 512 Apr 4 11:23 boot1
-r--r--r--
You wrote:
> Try 1:da(1,a)/boot/loader
>
>
> :(,)
>1 da 1 a/boot/loader
It does not work:
Invalid label
Invalid label
No /boot/loader
FYI I have an AHA 2940UW with 2 hd:
- ID 0: NEXTSTEP
- ID 1: FreeBSD and others
To boot FreeBSD I change the boot ID in t
Try 1:da(1,a)/boot/loader
:(,)
1 da 1 a/boot/loader
tomdean
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message
On Fri, 7 Apr 2000, "Thomas D. Dean" wrote:
> It was caused by my booting the kernel directly.
>
> 0:da(0,a)/kernel
>
> Using
>
> 0:da(0,a)/boot/loader
>
> cures the symptoms.
But here it doesn't seem to work... :(
0:da(1,a)/boot/loader
loaded...
ok boot
can't load 'kernel'
no bootable kerne
Thomas D. Dean wrote:
>
> I had this problem a week ago.
>
> It was caused by my booting the kernel directly.
>
> 0:da(0,a)/kernel
>
> Using
>
> 0:da(0,a)/boot/loader
>
> cures the symptoms.
There's a PR on it, including a patch. See
http://www.FreeBSD.org/cgi/query-pr.cgi?pr=17422
Th
On Fri, 7 Apr 2000, Thomas D. Dean wrote:
> I had this problem a week ago.
>
> It was caused by my booting the kernel directly.
>
> 0:da(0,a)/kernel
>
> Using
>
> 0:da(0,a)/boot/loader
>
> cures the symptoms.
Ohhh!!
This explains why i get the same top: nlist failed error in 5.0.
I had this problem a week ago.
It was caused by my booting the kernel directly.
0:da(0,a)/kernel
Using
0:da(0,a)/boot/loader
cures the symptoms.
tomdean
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message
You wrote:
> > rey:/usr/home/mirko> top
> > top: nlist failed
> > rey:/usr/home/mirko> vmstat
> > vmstat: undefined symbols:
> > _cp_time _kmemstatistics _bucket _zlist
>
> I heard rumors that this problem occurs when you doesn't use /boot/loader to
> boot your
> kernel. If so, it is bad practi
[EMAIL PROTECTED] wrote:
> Ciao!
>
> I've upgraded my system from 3.4 to 4.0-stable last night, with new /dev
> and new /etc but now I'm getting these errors:
>
> rey:~/Sources/gnustep/core/base> uname -a
> FreeBSD rey.procom2.it 4.0-STABLE FreeBSD 4.0-STABLE #0: Fri Apr 7 01:02:03
> CEST 2000
>
Ciao!
I've upgraded my system from 3.4 to 4.0-stable last night, with new /dev
and new /etc but now I'm getting these errors:
rey:~/Sources/gnustep/core/base> uname -a
FreeBSD rey.procom2.it 4.0-STABLE FreeBSD 4.0-STABLE #0: Fri Apr 7 01:02:03
CEST 2000
[EMAIL PROTECTED]:/mnt/amy/lpub/free
12 matches
Mail list logo
