On Thu, 2 Jan 2003, Scott Long wrote:
> It looks like sys/filedesc.h needs to be included in nv-freebsd.h
This got me up and running again on -current compiled 12/31. Thanks Scott!
Now that I'm used to the better performance of the nvidia drivers, it's
really noticable when it's not there.
Doug
Hi all,
On Sat, 4 Jan 2003 17:55:25 +
Trent Nelson <[EMAIL PROTECTED]> wrote:
> No. However, it happened to me today shorty after I issued a sysctl
> -w hw.acpi.cpu.economy_speed=8. (Why does it default to 4 anyway?)
It reminded me of my tiny local patch.
--- src/sys/dev/acpica/acp
On Fri, Jan 03, 2003 at 11:16:57AM -0800, Nate Lawson wrote:
> Sounds like an atkbd or syscons problem.
> Did you suspend the laptop and resume before this happens?
No. However, it happened to me today shorty after I issued a sysctl
-w hw.acpi.cpu.economy_speed=8. (Why does it default
Jake Burkholder <[EMAIL PROTECTED]> writes:
> Apparently, On Wed, Jan 08, 2003 at 11:25:12PM +,
> Mike Barcroft said words to the effect of;
> > --
> > >>> Kernel build for GENERIC started on Wed Jan 8 22:16:49 GMT 2003
> >
Apparently, On Wed, Jan 08, 2003 at 11:25:12PM +,
Mike Barcroft said words to the effect of;
> Tinderbox FAQ: http://people.FreeBSD.org/~mike/tinderbox.html
>
> --
> >>> Rebuilding the temporary build tree
> -
Tinderbox FAQ: http://people.FreeBSD.org/~mike/tinderbox.html
--
>>> Rebuilding the temporary build tree
--
>>> stage 1: bootstrap tools
-
On Wednesday, 8 January 2003 at 13:29:06 -0800, Darryl Okahata wrote:
> "Willem Jan Withagen" <[EMAIL PROTECTED]> write:
>
>> Vinum is running fine here on 5.0 for already quite some time.
>>
>> the trick is most likely:
>>
>> newfs -T ufs /dev/vinum/vinum0
>
> Nope. No joy:
>
>
On Wednesday, 8 January 2003 at 10:00:59 -0800, Darryl Okahata wrote:
> Hi,
>
> Has anyone gotten vinum to work using the 5.0RC2 ISO distribution?
> I've tried creating a raid5, a "raid10", and (finally) a basic,
> one-drive volume, and newfs fails for all cases, with:
>
> # newfs -U /d
Jeff Walters wrote:
> I was also getting these same repetitive page fault panics on 5.0-RC2
> related to fsck_ufs running after a hard crash. Booting single user
> and doing a manual fsck resolved it until the next system crash, then
> they normally occurred again.
>
> Don't know if this would app
I was also getting these same repetitive page fault panics on 5.0-RC2
related to fsck_ufs running after a hard crash. Booting single user
and doing a manual fsck resolved it until the next system crash, then
they normally occurred again.
Don't know if this would apply to you, but in my case re
Harald Schmalzbauer wrote:
Hello all,
I'm using 5.0-RC2 and after disconnecting a firewire HD and unclean shutdown
the system is panicing after reboot (I can login) and a few minutes with the
following message:
[...]
Please tell me if I can provide more infos, but I'm not subscribed so please
Darryl Okahata wrote:
"Willem Jan Withagen" <[EMAIL PROTECTED]> write:
Vinum is running fine here on 5.0 for already quite some time.
the trick is most likely:
newfs -T ufs /dev/vinum/vinum0
Nope. No joy:
# newfs -T ufs /dev/vinum/myvol
newfs: /dev/vinum/myvol:
"Willem Jan Withagen" <[EMAIL PROTECTED]> write:
> Vinum is running fine here on 5.0 for already quite some time.
>
> the trick is most likely:
>
> newfs -T ufs /dev/vinum/vinum0
Nope. No joy:
# newfs -T ufs /dev/vinum/myvol
newfs: /dev/vinum/myvol: can't figure out f
Vinum is running fine here on 5.0 for already quite some time.
the trick is most likely:
newfs -T ufs /dev/vinum/vinum0
building a raid5 in vinum goes spectactular easy:
vinum raid5 /dev/ad4s1h /dev/ad5s1h /dev/ad6s1h /dev/ad7s1h
vinum init vinum0.p0
--WjW
> Has a
Hello all,
I'm using 5.0-RC2 and after disconnecting a firewire HD and unclean shutdown
the system is panicing after reboot (I can login) and a few minutes with the
following message:
Fatal trap 12: page fault while in kernel mode
fault virtual address = 0x4e1
fault code =
On a -current cvsuped on Jan2-2003
uname -a
FreeBSD k7.jibe.net 5.0-CURRENT FreeBSD 5.0-CURRENT #0:
Wed Jan 8 09:21:54 MST 2003
[EMAIL PROTECTED]:/usr/obj/usr/src/sys/GENERIC i386
To reproduce error...
cd /somedir
where somedir has a valid floppy image file like kern.flp
Then...
dd if=kern.
Here is an updated patch for dc. Can you try it?
* Remove bogus locking
* Move intr setup, ether_ifattach to end
* add proper resource freeing to a case that missed it (!mac)
* update resource freeing for error cases after intr move
-Nate
Index: if_dc.c
=
"Bjoern A. Zeeb" wrote:
> after following src/UPDATING for an update from 4.7-REL to RELENG_5_0
> this afternoon on a test machine I recognized that there still is a
> /usr/bin/perl afterwards.
>
> Now I ask myself if there is a cleaner way to update from 4 to 5
> (apart from reinstalling) to get
Hi,
after following src/UPDATING for an update from 4.7-REL to RELENG_5_0
this afternoon on a test machine I recognized that there still is a
/usr/bin/perl afterwards.
Now I ask myself if there is a cleaner way to update from 4 to 5
(apart from reinstalling) to get an almost mere 5_0 ?
Any shell
Hi,
Has anyone gotten vinum to work using the 5.0RC2 ISO distribution?
I've tried creating a raid5, a "raid10", and (finally) a basic,
one-drive volume, and newfs fails for all cases, with:
# newfs -U /dev/vinum/myvol
newfs: /dev/vinum/myvol: can't figure out file system part
Tinderbox FAQ: http://people.FreeBSD.org/~mike/tinderbox.html
--
>>> Rebuilding the temporary build tree
--
>>> stage 1: bootstrap tools
-
On Tue, Jan 07, 2003 at 11:41:33AM -0500, John Baldwin wrote:
> Your 3rd party registered a lock somehow? Does it do mtx_init() and not
> do mtx_destroy() when being unloaded?
Gah! You hit this one right on the head. I thought I had equivalent
mtx_destroy calls for every mtx_init, but t
bleh, okay then, if I have to ;)
sorry guys, not the best introduction to the list.. but yeah, hey.
-luke
-Original Message-
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]]
Sent: 08 January 2003 15:45
To: Luke Marsden
Subject: Re: subscribe
No. Subscibe yourself.
:)
Send an e-m
subscribe
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message
Tinderbox FAQ: http://people.FreeBSD.org/~mike/tinderbox.html
--
>>> Rebuilding the temporary build tree
--
>>> stage 1: bootstrap tools
-
Hi Michael,
Regarding your linux clock issue:
There was a rather lively discussion at forums.gentoo.org about drastic
clock sync loss caused by KDE. I don't know if it has been resolved in
the 3.1 line, but if you were running linux KDE, you might take a look
at that as a cause for the linux
Hi,
a recently cvsupped copy of the RELENG_5_0 branch breaks in usr.bin/kdump:
===> usr.bin/kdump
sh /usr/src/usr.bin/kdump/mkioctls /usr/obj/usr/src/i386/usr/include >
ioctl.c
/usr/src/usr.bin/kdump/mkioctls: awk: Argument list too long
/usr/src/usr.bin/kdump/mkioctls: awk: Argument list too lo
27 matches
Mail list logo
