Hi
On 3/16/06, Dominique Goncalves [EMAIL PROTECTED] wrote:
Hi,
I'm trying to use a Wireless USB Adapter DWL G122 on RELENG_6 but it
is not detected and no ural0 interface is created, this device is
listed in the hardware section of ural(4).
$ uname -a
FreeBSD freebsd 6.1-PRERELEASE
Your device is not supported by ural(4).
The ural driver supports adapters based on Ralink first
generation 802.11b/g wireless USB adapters (RT2500USB).
Your adapter is based on the new RT2501USB chipset which
requires a new driver because the MAC/BBP is very different.
Damien
- Original
On Friday, 17 March 2006 at 22:13:05 +0100, Wilko Bulte wrote:
On Fri, Mar 17, 2006 at 03:35:39PM -0500, Kris Kennaway wrote..
On Fri, Mar 17, 2006 at 03:03:27PM -0500, Mike Tancsa wrote:
At 01:34 PM 17/03/2006, Peter van Heusden wrote:
Ok, but the machine is not stable enough to run
Well, I don't know weather it is supposed to be like this, but absolute
paths in libmap.conf don't work on my machine. I always have to make
entries relative to /usr/lib .
signature.asc
Description: OpenPGP digital signature
Hi,
I've been searching for the functionality of telling mdmfs (in my case
via fstab) not to do newfs on my file-backed mfs. Browsing the cvs I can
see that -P, doing exactly what I and many others have wanted, has been
added :)
It seems it's only been added to the current/main though, and
On Wed, Mar 15, 2006 at 02:28:55PM -0500, Mike Jakubik wrote:
+ Pawel Jakub Dawidek wrote:
+ Hi.
+
+ Here you can find patches with changes to gmirror(8) and graid3(8):
+
+ http://people.freebsd.org/~pjd/patches/gmirror.7.patch
+ http://people.freebsd.org/~pjd/patches/graid3.patch
+
+
I managed to get a backtrace from a panic that occurred during bgfsck:
dev = ar0s1f, block = 22958088, fs = /usr
panic: ffs_blkfree: freeing free frag
cpuid = 0
KDB: stack backtrace:
kdb_backtrace() at kdb_backtrace+0x37
panic() at panic+0x1d1
ffs_blkfree() at ffs_blkfree+0x43f
sysctl_ffs_fsck()
On Sat, Mar 18, 2006 at 05:12:12PM -0600, Jason Harmening wrote:
I managed to get a backtrace from a panic that occurred during bgfsck:
dev = ar0s1f, block = 22958088, fs = /usr
panic: ffs_blkfree: freeing free frag
cpuid = 0
KDB: stack backtrace:
kdb_backtrace() at kdb_backtrace+0x37
Hi,
We are planning to upgrade a NFS server from 5.x to 6.x. However,
we found there is a show stopper of 6.1 about NFS data corruption.
From the todo page, it says this item is worked in progress. Is this
has been fixed already or not yet? From the description, it is found
by running fsx (in
On Sun, Mar 19, 2006 at 12:19:04AM -0500, Rong-En Fan wrote:
Hi,
We are planning to upgrade a NFS server from 5.x to 6.x. However,
we found there is a show stopper of 6.1 about NFS data corruption.
From the todo page, it says this item is worked in progress. Is this
has been fixed already
10 matches
Mail list logo