On 01/-10/-28163 20:59, Ken Smith wrote:
The freebsd-update(8) utility supports binary upgrades of i386 and amd64
systems running earlier FreeBSD releases. Systems running 8.0-RELEASE,
8.1-RELEASE, 8.2-BETA1, 8.2-RC1 or 8.2-RC2 can upgrade as follows:
# freebsd-update upgrade -r 8.2-RC3
While
On 02/06/2011 10:30, Thomas Steen Rasmussen wrote:
On 03.02.2011 23:38, Jan Henrik Sylvester wrote:
On 01/-10/-28163 20:59, Ken Smith wrote:
The freebsd-update(8) utility supports binary upgrades of i386 and amd64
systems running earlier FreeBSD releases. Systems running 8.0-RELEASE,
8.1
On 01/-10/-28163 20:59, Renato Botelho wrote:
On Tue, Feb 22, 2011 at 11:04 AM, Svein Skogen wrote:
I'm in the process of setting up a small network of FreeBSD
installations. My plan (this time) is to keep them on branches available
to freebsd-update, instead of depending on source being checke
On 07/17/2012 05:38, Ken Smith wrote:
The first test build of the 9.1-RELEASE release cycle is now available
on the FTP servers for amd64, i386, powerpc64, and sparc64. The
What about freebsd-update -- is it going to be available for this BETA1?
Cheers,
Jan Henrik
I have got problems with GSSAPI authentication to OpenLDAP:
ldap_sasl_interactive_bind_s: Other (e.g., implementation specific)
error (80)
additional info: SASL(-1): generic failure: GSSAPI Error: No
credentials were supplied, or the credentials were unavailable or
inaccessible. (unkno
On 01/-10/-28163 20:59, Matthias Andree wrote:
Am 01.09.2010 18:33, schrieb Jan Henrik Sylvester:
I have got problems with GSSAPI authentication to OpenLDAP:
ldap_sasl_interactive_bind_s: Other (e.g., implementation specific)
error (80)
additional info: SASL(-1): generic failure
On 09/02/2010 13:50, Jeremy Chadwick wrote:
On Wed, Sep 01, 2010 at 06:33:03PM +0200, Jan Henrik Sylvester wrote:
I have got problems with GSSAPI authentication to OpenLDAP:
ldap_sasl_interactive_bind_s: Other (e.g., implementation specific)
error (80)
additional info: SASL(-1
On 09/02/2010 14:30, Reko Turja wrote:
--
From: "Jan Henrik Sylvester"
Sent: Wednesday, September 01, 2010 7:33 PM
To: "stable-list freebsd"
Subject: GSSAPI (for OpenLDAP) on FreeBSD 8?
Does anyone have OpenLDAP+GSSAPI
I just upgraded my main laptop from 8.1-RELEASE (GENERIC, amd64) to
8.2-BETA1 and added aesni_load="YES" to my /boot/loader.conf.
(If my interpretation is correct:) With aesni loaded, I see many files
corrupted on my geli encrypted volume. Without aesni loaded, they are ok.
I have got a journ
On 12/12/2010 15:26, Mike Tancsa wrote:
On 12/12/2010 3:43 AM, Kostik Belousov wrote:
Please try this patch on the latest HEAD or RELENG_8.
I tried both on i386 and amd64 and all looks good! I did 1000
iterations of
cryptotest -c -z -t 10
without issue! Thanks for the quick fix!
I redid
Oliver wrote:
> I bought a LevelOne WPC-0301 11g Wireless CardBus Adapter
> today. According to the box it is "v6". The ral(4) man-
> page mentions only v2, but that one is ancient and can't
> be bought anymore.
I do not know about the WPC-0301, but I since I bought a wrong WNC-0301
(PCI versi
Short version: Is there any chance to get iwn working on 7.1-RC1
reliably? I have got one problem with the initial perforce version and
the backport from gavin always crashes. Long version:
I have been using the initial perforce version of iwn on 7-STABLE for a
few month now, since the next ve
During boot I see: link_elf: symbol cp_time undefined
I have realized it now with RC2, but looking at my logs, I have had that
message during boot since upgrading this machine from 7.0-RELEASE to
7.1-RC1 via freebsd-update a at Dec-8. (I did recompile kernel modules
from ports: fusefs-kmod and
Garrett Cooper wrote:
On Dec 25, 2008, at 3:44, Jan Henrik Sylvester wrote:
During boot I see: link_elf: symbol cp_time undefined
I have realized it now with RC2, but looking at my logs, I have had
that message during boot since upgrading this machine from 7.0-RELEASE
to 7.1-RC1 via
Garrett Cooper wrote:
On Dec 25, 2008, at 17:36, Jan Henrik Sylvester wrote:
Garrett Cooper wrote:
On Dec 25, 2008, at 3:44, Jan Henrik Sylvester wrote:
During boot I see: link_elf: symbol cp_time undefined
I have realized it now with RC2, but looking at my logs, I have had
that message
I found a 7.1-RELEASE manpage stating "first appeared in FreeBSD 8.0". A
little bit of grepping revealed a few more:
setfib(1) setfib(2) ffs(3) ffsl(3) ffsll(3) fls(3) flsl(3) flsll(3)
memchr(3) memrchr(3) malo(4) crashinfo(8) savecore(8)
Some others are correctly stating "7.1" for example te
Da Rock wrote:
On Sun, 2009-01-18 at 14:17 -0600, Brandon Gooch wrote:
I have a working driver for the Intel 4965, aka iwn(4), loaded on my
Lenovo X300 running FreeBSD 7.1-RELEASE (amd64).
This driver is a slightly-modified version of the iwn(4) driver
backported from 8.0-CURRENT by Gavin Atkin
Torfinn Ingolfsen wrote:
On Sun, 18 Jan 2009 14:17:39 -0600
Brandon Gooch wrote:
I have a working driver for the Intel 4965, aka iwn(4), loaded on my
Lenovo X300 running FreeBSD 7.1-RELEASE (amd64).
FWIW, I am using the latest perforce version of the iwn driver as
documented here[1] on a Thi
On 01/-10/63 19:59, Dominic Fandrey wrote:
The if_wpi driver is all kinds of broken. The reported problems
I have had trouble with all Intel drivers, ipw, iwi, wpi, and iwn. (As
an exception, recently, iwn was very stable on 8-STABLE.) For most
notebooks, I bought Atheros based MiniPCI(e) car
On 09/18/2012 18:14, Marcelo Gondim wrote:
I installed the package ntfs-fusefs on two different servers and both
causes kernel panic when trying to copy anything.
I got panics, too, but found some patch that I attached to ports/169165.
Unfortunately, the maintainer of sysutils/fusefs-kmod (Cce
On 08/15/2015 20:47, Chris Anderson wrote:
> just upgraded from 10.1-RELEASE-p16 to 10.2-RELEASE using freebsd-update.
>
> after the upgrade, I began getting errors because pam_opie.so.5 has an
> unsatisfied link to libopie.so.7 (my system only has libopie.so.8).
>
> I notice a fresh install of 1
On 08/16/2015 19:47, Kimmo Paasiala wrote:
> On Sun, Aug 16, 2015 at 8:40 PM, Jan Henrik Sylvester wrote:
>> On 08/15/2015 20:47, Chris Anderson wrote:
>>> just upgraded from 10.1-RELEASE-p16 to 10.2-RELEASE using freebsd-update.
>>>
>>> after the upg
Vladimir Botka wrote:
> Can anybody help me please with usb mouse? There is uhid driver
> attached. Keyboard works fine.
When I once tried a Microsoft cordless USB mouse, I only got an uhid0,
too. After some research, the best answer I found was this:
http://lists.freebsd.org/pipermail/freebsd
I upgraded an old machine from 6.2-RELEASE-p7 to 6.3-BETA1 (via
freebsd-update).
Now every ten seconds I get:
acpi_tz0: _TMP value is absurd, ignored (-13.4C)
At the same time, I have:
hw.acpi.thermal.tz0.temperature: -273.2C
The machine has a Gigabyte GA-686BX board with Intel 82440 BX chip
I tried to rollback the freebsd-update 6.2-R -> 6.3-B1.
(The reason was to freebsd-update to 6.3-B2 with the possibility of
doing a rollback to 6.2-R.)
It printed quite a few lines of
/libexec/ld-elf.so.1: grep: Undefined symbol "__sbmaskrune"
and
/libexec/ld-elf.so.1: sort: Undefined symbo
Colin Percival wrote:
Jan Henrik Sylvester wrote:
I tried to rollback the freebsd-update 6.2-R -> 6.3-B1.
To confirm that I understand what you're saying here: You upgraded
from FreeBSD 6.2-RELEASE to 6.3-BETA1, then you ran "freebsd-update
rollback" to move back to F
Colin Percival wrote:
Jan Henrik Sylvester wrote:
Colin Percival wrote:
I believe that your system is now 6.3-BETA1 with a few shared libraries
from 6.2-RELEASE mixed in. If you can get a copy of /lib/*.so.* and
/usr/lib/*.so.* from a 6.3-BETA1 system and install those into place
(in fact
Colin Percival wrote:
Depending on the UpdateIfUnmodified option in freebsd-update.conf, it will
either update files to "clean" new versions or print a warning message and
not touch them.
There's also an IgnorePaths directive which you can use to tell FreeBSD
Update not to touch some files (even
After reading that someone had problems with 802.11i/WPA2, I tested my
iwi device, too. 802.11i (as client) works, but disconnects about every
five minutes briefly, which is nothing new -- I had the same issue with
6.2-RELEASE.
In contrast to 6.2-RELEASE, monitor does not work. Kismet does
not
On 09/27/2016 12:16, Borja Marcos wrote:
> I have noticed that the GENERIC kernel in 11-STABLE includes the PCI_HP
> option, and the
> hotplug bits seem to be present in the kernel, but I don’t see any userland
> support for it.
>
> Is it somewhat complete and in that case am I missing something
On 09/27/2016 17:51, Eric van Gyzen wrote:
> In the case of Jan's USB 3.0 ExpressCard, it's possible that one or all
> of the USB controller drivers (xhci, ehci, uhci) didn't cope with the
> surprise removal of the controller. Before removing the card, try
> detaching the driver(s) with "devctl de
On 6.2-RELEASE using fusefs-kmod-0.3.0_4, fusefs-libs-2.6.2, and
fusefs-ntfs-0.20070207RC1, I can mount my existing (Windows XP) NTFS
partition with 'ntfs-3g /dev/ad0s1 /mnt/ad0s1'.
The following error messages about missing /proc/filesystems and
modprobe can be ignored, since defaults are ass
Hi!
I have got a RT2561 based card (not deliberately, wanted RT2500):
ral0: mem 0xd800-0xd8007fff irq 10 at
device 10.0 on pci0
ral0: MAC/BBP RT 2661B, RF RT2527
ral0: Ethernet address: 00:80:5a:38:XX:XX
Some searching led me to: http://samodelkin.net/~fjoe/if_ral.diff --
which compiles
Hello!
Before the last freebsd-update, I had a GENERIC kernel installed.
Now 'uname -v -i' gives me:
FreeBSD 6.2-RELEASE-p2 #0: Tue Feb 27 22:56:09 UTC 2007
[EMAIL PROTECTED]:/usr/obj/usr/src/sys/SMP SMP-GENERIC
Did something go wrong?
Does SMP have any negative side effects (Pentium M)?
Colin Percival wrote:
> Jan Henrik Sylvester wrote:
> > Before the last freebsd-update, I had a GENERIC kernel installed.
>
> Are you sure? :-)
I was... since I "always" had one, but looking at my old logs, I found:
FreeBSD 6.2-RELEASE #0: Fri Jan 12 11:05:30 UTC 2007
[
35 matches
Mail list logo
