Re: FYI: Advanced USB compliance testing tool now in the tree (10-current only)
On 08/10/13 23:34, Kevin Oberman wrote: On Fri, Aug 9, 2013 at 1:33 PM, Hans Petter Selasky h...@bitfrost.no wrote: Hi, For those of you that want to make sure your USB mass storage device behaves correctly when using FreeBSD, typically for critical applications, I've just added an advanced USB testing tool to the FreeBSD source tree. It can be used to stress your USB mass storage device in ways that are beyond what bonnie will do. See tools/tools/usbtest or the following commit: http://svnweb.freebsd.org/**changeset/base/254159http://svnweb.freebsd.org/changeset/base/254159 --HPS Looks very nice. While it is now only in head, is there a reason it could not be built and used on a 9.2-BETA system? (I have not tried. Just wondering if I should.) Hi, It can be built and used on 9.2-BETA, given than you checkout the full 10-current sources and build from the directory there. --HPS ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to freebsd-current-unsubscr...@freebsd.org
Re: Fun with nvi
On Sat, Aug 10, 2013 at 10:33:20AM -0700, Peter Wemm wrote: I've been tinkering with the nvi refresh from the GSoC in 2011, aka nvi2. https://www.google-melange.com/gsoc/proposal/review/google/gsoc2011/zy/1 https://github.com/lichray/nvi2 The goal was to update the multibyte handling in nvi-1.79 (the one we have in our tree) in such a way we could import it. Yes, please do something about our base(1) being unable to talk in anything non-ASCII. I'm using editors/nvi-devel now, which was WIDECHAR option, and was wondering why those changes were never imported into the base. How is nvi 1.81.6 (per editors/nvi-devel) is different from nvi2, btw? ./danfe ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to freebsd-current-unsubscr...@freebsd.org
Re: Fun with nvi
On Sun, Aug 11, 2013 at 1:35 AM, Alexey Dokuchaev da...@freebsd.org wrote:
On Sat, Aug 10, 2013 at 10:33:20AM -0700, Peter Wemm wrote:
I've been tinkering with the nvi refresh from the GSoC in 2011, aka nvi2.
https://www.google-melange.com/gsoc/proposal/review/google/gsoc2011/zy/1
https://github.com/lichray/nvi2
The goal was to update the multibyte handling in nvi-1.79 (the one we
have in our tree) in such a way we could import it.
Yes, please do something about our base(1) being unable to talk in anything
non-ASCII. I'm using editors/nvi-devel now, which was WIDECHAR option, and
was wondering why those changes were never imported into the base.
How is nvi 1.81.6 (per editors/nvi-devel) is different from nvi2, btw?
The original reason was that nvi-devel switched from the db-1.x API to
db-3/db-4 which were sleepycat licensed, and are now Oracle. It was a
big chunk of code at the time. eg:
USE_BDB=42+
CONFIGURE_ARGS+=--with-db-prefix=${LOCALBASE}
nvi2 is nvi-1.79 from base with a serious cleanup pass. The
iconv/multibyte code will look quite familiar if you've looked at the
nvi-devel code, along with a cherry-picking of additions from nvi-m17n
for better CJK/non-utf8 support.
nvi2 does not have the same level of sophisticated encoding detection
that nvi-m17n has.
--
Peter Wemm - pe...@wemm.org; pe...@freebsd.org; pe...@yahoo-inc.com; KI6FJV
UTF-8: for when a ' just won\342\200\231t do.
brueffer ZFS must be the bacon of file systems. everything's better with ZFS
___
freebsd-current@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to freebsd-current-unsubscr...@freebsd.org
Re: Fun with nvi
On Sun, Aug 11, 2013 at 02:15:15AM -0700, Peter Wemm wrote:
On Sun, Aug 11, 2013 at 1:35 AM, Alexey Dokuchaev da...@freebsd.org wrote:
Yes, please do something about our base(1) being unable to talk in anything
non-ASCII. I'm using editors/nvi-devel now, which was WIDECHAR option, and
was wondering why those changes were never imported into the base.
Yuck, pardon my typos: it should read base vi(1) and has WIDECHAR option.
How is nvi 1.81.6 (per editors/nvi-devel) is different from nvi2, btw?
The original reason was that nvi-devel switched from the db-1.x API to
db-3/db-4 which were sleepycat licensed, and are now Oracle. It was a
big chunk of code at the time. eg:
USE_BDB=42+
CONFIGURE_ARGS+=--with-db-prefix=${LOCALBASE}
nvi2 is nvi-1.79 from base with a serious cleanup pass. The
iconv/multibyte code will look quite familiar if you've looked at the
nvi-devel code, along with a cherry-picking of additions from nvi-m17n
for better CJK/non-utf8 support.
Understood, thanks for the insight.
nvi2 does not have the same level of sophisticated encoding detection
that nvi-m17n has.
I don't care too much about encoding detection since all sane parts of the
world would have switched to UTF-8 by now. ;-)
./danfe
___
freebsd-current@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to freebsd-current-unsubscr...@freebsd.org
Re: nanobsd-built system doesn't have SVN revision in uname (and it looks like regression)
There's still one problem left ... the svnliteversion test fails
because you are not in the correct directory. This is the patch that
worked for me ...
root@olive:/usr/src # svnlite diff sys/conf/newvers.sh
Index: sys/conf/newvers.sh
===
--- sys/conf/newvers.sh (revision 254187)
+++ sys/conf/newvers.sh (working copy)
@@ -105,7 +105,7 @@
done
if [ -z ${svnversion} ] [ -x /usr/bin/svnliteversion ] ; then
- /usr/bin/svnliteversion $(basename ${0}) /dev/null 21
+ cd ${SYSDIR}/conf /usr/bin/svnliteversion $(basename ${0}) /dev/null
21
if [ $? -eq 0 ]; then
svnversion=/usr/bin/svnliteversion
else
On Sat, 10 Aug 2013, Glen Barber wrote:
On Sat, Aug 10, 2013 at 02:11:52PM -0400, Glen Barber wrote:
On Sat, Aug 10, 2013 at 01:09:20PM -0500, Dan Mack wrote:
It looks like you are doing the first [! -z '${svnversion}' ]
before $svnversion is being set. In the old version, this was
being set via:
if [ -x /usr/bin/svnliteversion ] ; then
svnversion=/usr/bin/svnliteversion
fi
But I'm not sure if that's intentional or not ...
Ugh. No, this was not intentional. I'll have this fixed shortly.
Fixed in r254184. The problem is that I was evaluating ${svnversion}
being set before looking for /usr/bin/svnliteversion; however when
_running_ /usr/bin/svnliteversion, it was being run as
/usr/bin/svnversion by mistake.
Thank you for the reports, and Dan, thank you for your help.
Glen
dan
--
Dan Mack
___
freebsd-current@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to freebsd-current-unsubscr...@freebsd.org
Re: nanobsd-built system doesn't have SVN revision in uname (and it looks like regression)
On Sun, Aug 11, 2013 at 08:25:42AM -0500, Dan Mack wrote: There's still one problem left ... the svnliteversion test fails because you are not in the correct directory. This is the patch that worked for me ... Yep, you are correct. Although, rather than cd(1) to the SYSDIR directory, I think using realpath(1) is better, because that will use the full path to the newvers.sh script. Please try r254217, which should *finally* do the right thing. Glen pgpvNkYENlZyV.pgp Description: PGP signature
Re: nanobsd-built system doesn't have SVN revision in uname (and it looks like regression)
Yeah, I agree with avoiding the 'cd' as well. I'll give it a try shortly. Dan On Sun, 11 Aug 2013, Glen Barber wrote: On Sun, Aug 11, 2013 at 08:25:42AM -0500, Dan Mack wrote: There's still one problem left ... the svnliteversion test fails because you are not in the correct directory. This is the patch that worked for me ... Yep, you are correct. Although, rather than cd(1) to the SYSDIR directory, I think using realpath(1) is better, because that will use the full path to the newvers.sh script. Please try r254217, which should *finally* do the right thing. Glen dan -- Dan Mack ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to freebsd-current-unsubscr...@freebsd.org
buildworld failure
FreeBSD FBSD10 10.0-CURRENT FreeBSD 10.0-CURRENT #78 r253966: Mon Aug 5 14:42:05 CDT 2013 root@FBSD10:/usr/obj/usr/src/sys/MYKERNEL amd64 # svn info Path: . Working Copy Root Path: /usr/src URL: svn://svn.freebsd.org/base/head Relative URL: ^/head Repository Root: svn://svn.freebsd.org/base Repository UUID: ccf9f872-aa2e-dd11-9fc8-001c23d0bc1f Revision: 254218 Node Kind: directory Schedule: normal Last Changed Author: jilles Last Changed Rev: 254218 Last Changed Date: 2013-08-11 09:15:01 -0500 (Sun, 11 Aug 2013) I get the following failure when trying to do buildworld: --- kerberos5/lib__L --- --- inquire_context.So --- cc -fpic -DPIC -O2 -pipe -I/usr/src/kerberos5/lib/libgssapi_ntlm/../../../crypto/heimdal/lib/gssapi -I/usr/src/kerberos5/lib/libgssapi_ntlm/../../../crypto/heimdal/lib/gssapi/gssapi -I/usr/src/kerberos5/lib/libgssapi_ntlm/../../../crypto/heimdal/lib/gssapi/ntlm -I/usr/src/kerberos5/lib/libgssapi_ntlm/../../../crypto/heimdal/lib/krb5 -I/usr/src/kerberos5/lib/libgssapi_ntlm/../../../crypto/heimdal/lib/ntlm -DHAVE_CONFIG_H -I/usr/src/kerberos5/lib/libgssapi_ntlm/../../include -std=gnu99 -Qunused-arguments -fstack-protector -c /usr/src/kerberos5/lib/libgssapi_ntlm/../../../crypto/heimdal/lib/gssapi/ntlm/inquire_context.c -o inquire_context.So --- lib__L --- /usr/src/lib/bind/dns/../../../contrib/bind9/lib/dns/zone.c:14682:11: warning: null character ignored [-Wnull-character] isc_time_ ^ /usr/src/lib/bind/dns/../../../contrib/bind9/lib/dns/zone.c:14682:12: warning: null character ignored [-Wnull-character] isc_time_U+ ^ /usr/src/lib/bind/dns/../../../contrib/bind9/lib/dns/zone.c:14682:13: warning: null character ignored [-Wnull-character] isc_time_U+U+ ^ /usr/src/lib/bind/dns/../../../contrib/bind9/lib/dns/zone.c:14682:14: warning: null character ignored [-Wnull-character] isc_time_U+U+U+ ^ /usr/src/lib/bind/dns/../../../contrib/bind9/lib/dns/zone.c:14682:15: warning: null character ignored [-Wnull-character] isc_time_U+U+U+U+ ^ /usr/src/lib/bind/dns/../../../contrib/bind9/lib/dns/zone.c:14682:16: warning: null character ignored [-Wnull-character] isc_time_U+U+U+U+U+ ^ /usr/src/lib/bind/dns/../../../contrib/bind9/lib/dns/zone.c:14682:17: warning: null character ignored [-Wnull-character] isc_time_U+U+U+U+U+U+ ^ /usr/src/lib/bind/dns/../../../contrib/bind9/lib/dns/zone.c:14682:18: warning: null character ignored [-Wnull-character] isc_time_U+U+U+U+U+U+U+ ^ /usr/src/lib/bind/dns/../../../contrib/bind9/lib/dns/zone.c:14682:19: warning: null character ignored [-Wnull-character] isc_time_U+U+U+U+U+U+U+U+ ^ /usr/src/lib/bind/dns/../../../contrib/bind9/lib/dns/zone.c:14682:20: warning: null character ignored [-Wnull-character] isc_time_U+U+U+U+U+U+U+U+U+ ^ /usr/src/lib/bind/dns/../../../contrib/bind9/lib/dns/zone.c:14682:21: warning: null character ignored [-Wnull-character] isc_time_U+U+U+U+U+U+U+U+U+U+ ^ /usr/src/lib/bind/dns/../../../contrib/bind9/lib/dns/zone.c:14682:22: warning: null character ignored [-Wnull-character] isc_time_U+U+U+U+U+U+U+U+U+U+U+ ... /usr/src/lib/bind/dns/../../../contrib/bind9/lib/dns/zone.c:14682:55: warning: null character ignored [-Wnull-character] isc_time_U+U+U+U+U+U+U+U+U+U+U+U+U+U+U+U+U+U+U+U+U+U+U+U+U+U+U+U+U+U+U+U+U+U+U+U+U+U+U+U+U+U+U+U+ ^ /usr/src/lib/bind/dns/../../../contrib/bind9/lib/dns/zone.c:14682:56: warning: null character ignored [-Wnull-character] isc_time_U+U+U+U+U+U+U+U+U+U+U+U+U+U+U+U+U+U+U+U+U+U+U+U+U+U+U+U+U+U+U+U+U+U+U+U+U+U+U+U+U+U+U+U+U+ ^ /usr/src/lib/bind/dns/../../../contrib/bind9/lib/dns/zone.c:14682:57: warning: null character ignored [-Wnull-character] isc_time_U+U+U+U+U+U+U+U+U+U+U+U+U+U+U+U+U+U+U+U+U+U+U+U+U+U+U+U+U+U+U+U+U+U+U+U+U+U+U+U+U+U+U+U+U+U+ .,,
Anyone looking at Intel Rapid Start?
Howdy, Anyone looking into this? http://software.intel.com/en-us/articles/what-is-intel-rapid-start-technology Best, George ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to freebsd-current-unsubscr...@freebsd.org
ZFS Crashes
In the last 12 hours I've had 4 crashes related to ZFS. total 97 -rw-r--r-- 1 ler ler 136488 Aug 11 11:17 core.txt.1 -rw-r--r-- 1 ler ler 117213 Aug 11 11:17 core.txt.2 -rw-r--r-- 1 ler ler 120357 Aug 11 11:17 core.txt.3 -rw-r--r-- 1 ler ler 71718 Aug 11 11:17 core.txt.4 These are all available at: http://www.lerctr.org/~ler/FreeBSD Any help would be appreciated. -- Larry Rosenman http://www.lerctr.org/~ler Phone: +1 214-642-9640 E-Mail: l...@lerctr.org US Mail: 108 Turvey Cove, Hutto, TX 78634-5688 ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to freebsd-current-unsubscr...@freebsd.org
Re: Fix for sys_munlock(2) with racct
Wiadomość napisana przez Alan Cox a...@rice.edu w dniu 30 lip 2013, o godz. 19:40: On Jul 21, 2013, at 2:50 PM, Jeremie Le Hen wrote: Also, a wired mapping can be destroyed by calling munmap(2) without first calling munlock(2), in which case, RACCT_MEMLOCK will be incorrect. So I think the right way to tackle this is to handle racct in the vm layer rather than at the syscall layer. The VM system already maintains counters equivalent to RACCT_VMEM and RACCT_MEMLOCK. They are map-size and pmap_wired_count(map-pmap). Instead of maintaining duplicate counters, could the resource accounting framework be extended to support callbacks to obtain a value when it's actually needed? That would be rather hard. The way this works is that raccts are hierarchical, and every time resource allocation is done, its respective counter needs to be propagated all the way up. If it hits a limit somewhere, the racct function returns error meaning the resource allocation was denied. In other words, racct wants to know when the counter changes. ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to freebsd-current-unsubscr...@freebsd.org
Re: ZFS Crashes
I'm running zfs on a few systems with recent builds; which version of current were you last stable on ... if you can recall? FWIW I'm so far pretty stable on 254187 (on two systems) and also on r253918 Dan On Sun, 11 Aug 2013, Larry Rosenman wrote: In the last 12 hours I've had 4 crashes related to ZFS. total 97 -rw-r--r-- 1 ler ler 136488 Aug 11 11:17 core.txt.1 -rw-r--r-- 1 ler ler 117213 Aug 11 11:17 core.txt.2 -rw-r--r-- 1 ler ler 120357 Aug 11 11:17 core.txt.3 -rw-r--r-- 1 ler ler 71718 Aug 11 11:17 core.txt.4 These are all available at: http://www.lerctr.org/~ler/FreeBSD Any help would be appreciated. -- Larry Rosenman http://www.lerctr.org/~ler Phone: +1 214-642-9640 E-Mail: l...@lerctr.org US Mail: 108 Turvey Cove, Hutto, TX 78634-5688 ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to freebsd-current-unsubscr...@freebsd.org dan -- Dan Mack ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to freebsd-current-unsubscr...@freebsd.org
Re: ZFS Crashes
On 2013-08-11 12:05, Dan Mack wrote: I'm running zfs on a few systems with recent builds; which version of current were you last stable on ... if you can recall? FWIW I'm so far pretty stable on 254187 (on two systems) and also on r253918 Dan About 3-4 days ago (not sure of the svn rev). -- Larry Rosenman http://www.lerctr.org/~ler Phone: +1 214-642-9640 (c) E-Mail: l...@lerctr.org US Mail: 108 Turvey Cove, Hutto, TX 78634-5688 ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to freebsd-current-unsubscr...@freebsd.org
Re: ZFS Crashes
You seem to be getting a selection of random looking issues bad hardware would be my first guess. Run a memtest and see if it turns up anything. Regards Steve - Original Message - From: Larry Rosenman l...@lerctr.org To: freebsd-current@freebsd.org Sent: Sunday, August 11, 2013 5:20 PM Subject: ZFS Crashes In the last 12 hours I've had 4 crashes related to ZFS. total 97 -rw-r--r-- 1 ler ler 136488 Aug 11 11:17 core.txt.1 -rw-r--r-- 1 ler ler 117213 Aug 11 11:17 core.txt.2 -rw-r--r-- 1 ler ler 120357 Aug 11 11:17 core.txt.3 -rw-r--r-- 1 ler ler 71718 Aug 11 11:17 core.txt.4 These are all available at: http://www.lerctr.org/~ler/FreeBSD Any help would be appreciated. -- Larry Rosenman http://www.lerctr.org/~ler Phone: +1 214-642-9640 E-Mail: l...@lerctr.org US Mail: 108 Turvey Cove, Hutto, TX 78634-5688 ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to freebsd-current-unsubscr...@freebsd.org This e.mail is private and confidential between Multiplay (UK) Ltd. and the person or entity to whom it is addressed. In the event of misdirection, the recipient is prohibited from using, copying, printing or otherwise disseminating it or any information contained in it. In the event of misdirection, illegible or incomplete transmission please telephone +44 845 868 1337 or return the E.mail to postmas...@multiplay.co.uk. ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to freebsd-current-unsubscr...@freebsd.org
Re: ZFS Crashes
On 2013-08-11 12:29, Steven Hartland wrote: You seem to be getting a selection of random looking issues bad hardware would be my first guess. Run a memtest and see if it turns up anything. Regards Steve same hardware was ROCK STABLE till this weekend. -- Larry Rosenman http://www.lerctr.org/~ler Phone: +1 214-642-9640 (c) E-Mail: l...@lerctr.org US Mail: 108 Turvey Cove, Hutto, TX 78634-5688 ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to freebsd-current-unsubscr...@freebsd.org
Re: ZFS Crashes
same hardware was ROCK STABLE till this weekend. Larry, it would help if you had a svn revision #, for what it is worth, I had a machine that was crashing all over the place, after r254141 a fresh svnlite up and new kernel r254196 seems to have fixed my problem atleast... -- Sam Fourman Jr. ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to freebsd-current-unsubscr...@freebsd.org
Re: ZFS Crashes
On 2013-08-11 12:41, Sam Fourman Jr. wrote: same hardware was ROCK STABLE till this weekend. Larry, it would help if you had a svn revision #, for what it is worth, I had a machine that was crashing all over the place, after r254141 a fresh svnlite up and new kernel r254196 seems to have fixed my problem atleast... The SVN rev was AWOL from the uname till this AM. This is still crashing with current HEAD. :( I have a memtest86+ running just on general principles. It's 64G -- It'll take a while :) -- Larry Rosenman http://www.lerctr.org/~ler Phone: +1 214-642-9640 (c) E-Mail: l...@lerctr.org US Mail: 108 Turvey Cove, Hutto, TX 78634-5688 ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to freebsd-current-unsubscr...@freebsd.org
Re: ZFS Crashes
Le 11/08/2013 19:30, Larry Rosenman a écrit : On 2013-08-11 12:29, Steven Hartland wrote: You seem to be getting a selection of random looking issues bad hardware would be my first guess. Run a memtest and see if it turns up anything. Regards Steve same hardware was ROCK STABLE till this weekend. Things goes well until they go down… signature.asc Description: OpenPGP digital signature
Re: ZFS Crashes
The SVN rev was AWOL from the uname till this AM. Oh snap you are right, I didn't even notice uname -a lost the rev # looks like I have some compiling to do :) -- Sam Fourman Jr. ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to freebsd-current-unsubscr...@freebsd.org
Re: ZFS Crashes
On Sun, Aug 11, 2013 at 9:20 AM, Larry Rosenman l...@lerctr.org wrote: In the last 12 hours I've had 4 crashes related to ZFS. total 97 -rw-r--r-- 1 ler ler 136488 Aug 11 11:17 core.txt.1 -rw-r--r-- 1 ler ler 117213 Aug 11 11:17 core.txt.2 -rw-r--r-- 1 ler ler 120357 Aug 11 11:17 core.txt.3 -rw-r--r-- 1 ler ler 71718 Aug 11 11:17 core.txt.4 These are all available at: http://www.lerctr.org/~ler/FreeBSD Any help would be appreciated. -- Larry Rosenman http://www.lerctr.org/~ler Phone: +1 214-642-9640 E-Mail: l...@lerctr.org US Mail: 108 Turvey Cove, Hutto, TX 78634-5688 ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to freebsd-current-unsubscr...@freebsd.org Hi, at least one of your panics seems related to the recent changes in kernel virtual address allocation. (namely, http://www.lerctr.org/~ler/FreeBSD/core.txt.3). You can try revert the revision that introduced them and see if this stabilizes things. Just a guess though. http://svnweb.freebsd.org/base?view=revisionrevision=254025 Thanks, -- Davide There are no solved problems; there are only problems that are more or less solved -- Henri Poincare ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to freebsd-current-unsubscr...@freebsd.org
Notebook, Geforce Gtx 660M and ibtel HD
Hail, I am back to desktoo and FreeBSD, but I cant pass the simple test to make X alive. Xorg -configure detects two vga and two displays, but neither seems to work. On 9.2rc I got to show X, but deadlock soon after. Now I installed head, and cant even get X to work. The nvidia driver refuses to install, tons of errors (not at home now to copy the messages). I have optimus nvidia hardware. Is there any guide to this? Any vga working will do, if capable to play videos and do 2d stuff. Thanks in advance, Matheus We will call you Cygnus, The God of balance you shall be ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to freebsd-current-unsubscr...@freebsd.org
quick hack to support option VIMAGE on USB Ethernet
Hi all, I hope to use option VIMAGE on RaspberryPi. So, I try to make a patch. http://freebsd-current.os-hackers.jp/pub/FreeBSD/snapshots/20130812/raspberry-pi/patch-vimage-r254236.diff #There is a SD image for RaspberryPi at same place. But, I only test it for if_smsc driver on RaspberryPi. I don't test other architectures/devices. Please test my patch and suggest the way to support option VIMAGE on USB devices, if you are interested in. Thanks, --- YAMAMOTO Shigeru shig...@iij.ad.jp ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to freebsd-current-unsubscr...@freebsd.org
