Hello,
I'm on FreeBSD 12.0-STABLE #0 r344261 amd64.
I've rebuilt all ports after clang 7 import to 12-STABLE.
Now I get with mplayer
ld-elf.so.1: /lib/libc.so.7: Undefined symbol "__progname"
--
Sent from: http://freebsd.1045724.x6.nabble.com/freebsd-current-f3875308.html
_
How far it's supposed to support legacy CPUs
on FreeBSD?
x86info
Found 2 identical CPUs
Extended Family: 0 Extended Model: 1 Family: 6 Model: 23 Stepping: 10
Type: 0 (Original OEM)
CPU Model (x86info's best guess): Unknown model.
Processor name string (BIOS programmed): Intel(R) Core(TM)2 Duo CPU
I can't help noticing your signature, so clean installation is always a good
start.
--
Sent from: http://freebsd.1045724.x6.nabble.com/freebsd-current-f3875308.html
___
freebsd-current@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo
I saw this few weeks ago with -STABLE.
It's only recently that make delete-old delete debug
files, so it might started a lot earlier that we think.
--
Sent from: http://freebsd.1045724.x6.nabble.com/freebsd-current-f3875308.html
___
freebsd-current@f
The definition of a MINIMAL used is a specific one- it does not contain
anything which can be loaded by modules.
It could be a starting point to something else, but then, it still contains
other things you probably not need. If I get the point, I would probably
try to boot MINIMAL on a new hardw
> Maybe ... but this is one of those things that (in my
> experience) either Just Work or Go Horribly Wrong.
That's why I would go at least (latest) -RELEASE to
-STABLE before going -STABLE to -CURRENT, if you
must.
Why trying your luck with big jumps?
--
Sent from: http://freebsd.1045724.x6
I use 11-STABLE with Intel. Some time ago, there was a switch
to drm2 here.
Iirc I had to add kld_list="i915kms.ko to rc.conf and ensure
that drm2/drm2 and drm2/i915kms are built (which should
be default).
Are you sure you are not using drm2 already? I would check
with kldstat. The message in
> In other words, if a user has some WITHOUT_* set in src.conf,
> specific files are not installed by installworld, but not removed
> by remove-old, which I try to fix.
Please carry on, I saw quite a few times that this behaviour was
assumed by new users, only it is not (yet), to their surprise :
Are there any problems with MFC?
--
View this message in context:
http://freebsd.1045724.n5.nabble.com/newcons-and-beeping-X-tp5906883p5916170.html
Sent from the freebsd-current mailing list archive at Nabble.com.
___
freebsd-current@freebsd.org maili
Hello,
as of FreeBSD 10.0-STABLE #0 r266216 I still have
a mute console in X (which isn't surprising, as there
was no MFC)
--
View this message in context:
http://freebsd.1045724.n5.nabble.com/newcons-and-beeping-X-tp5906883p5913086.html
Sent from the freebsd-current mailing list archive at
By choppy I've also meant it's noticeably slower
than syscons, but I think it's already known.
The shell was a shells/mksh.
I think I may switch to newcons permanently
after a merge of bell patch thing.
--
View this message in context:
http://freebsd.1045724.n5.nabble.com/newcons-and-beepin
I've used attached script for making usable kbd.
I'm aware of another problem though (and can
clarify it now).
If I use any other character than a basic latin set, my
prompt is not preserved.
e. g.
Kuba@Thinkpad:/usr/home/Kuba $ abcdefghi
Kuba@Thinkpad:/usr/home/Kuba $
Kuba@Thinkpad:/usr/
Thanks for reply, that helped me somehow.
--
View this message in context:
http://freebsd.1045724.n5.nabble.com/newcons-and-beeping-X-tp5906883p5908076.html
Sent from the freebsd-current mailing list archive at Nabble.com.
___
freebsd-current@freebs
As far as I can tell, the situation is the same on
FreeBSD 10.0-STABLE #0 r265185 amd64.
newcons uses my X font (terminus), albeit it produces
no polish letters (some random glyphs are produced),
bell is working but initila terminal offset is wrong-
I can "overwrite" my terminal prompt, X is mu
I think that newcons used somehow my
terminus font from X (?) and there were
no polish characters.
I had/have in rc.conf
font8x14=iso02-8x14
font8x16=iso02-8x16
font8x8=iso02-8x8
but it made no difference.
It was on 10-STABLE, somewhat
early after merge. I may try it
again later today.
--
V
newcons beeping in X and no localised font in system console
is why I've dropped newcons.
Thanks for submission.
--
View this message in context:
http://freebsd.1045724.n5.nabble.com/newcons-and-beeping-X-tp5906883p5907856.html
Sent from the freebsd-current mailing list archive at Nabble.com.
There is info feed also
http://opensslrampage.org/
Too early to say what will come out of it, but has some
promising qualities certainly.
--
View this message in context:
http://freebsd.1045724.n5.nabble.com/OpenSSL-vs-LibreSSL-OpenBSD-tp5906272p5906317.html
Sent from the freebsd-current mail
You got me for a moment :)
On a serious note...
OpenBSD is reportedly having some
success on a desktop- is using -CURRENT
on dev's desktop religiously (so I've
heard) something related?
(e.g. working sound out of the box)
I have sound with www/firefox without
pulseaudio, albeit firefox 28 seg
Hello.
I've tried to use vt on 10-STABLE, but had my own problems and
abandoned it. From what I've heard, no support for vidcontrol(*)
is expected at this point.
* https://wiki.freebsd.org/Newcons
--
View this message in context:
http://freebsd.1045724.n5.nabble.com/Newcons-with-Nvidia-tp589
Hello,
Unfortunately, this is the case with *zips from Dropbox (Download
as .zip) directory option.
$ /usr/bin/unzip file.zip
Archive: file.zip
unzip: skipping non-regular entry ''
unzip: skipping non-regular entry 'A B C D.pdf'
archivers/unzip manages this case t
Fuse is now the only way to mount ntfs. That's all. Regarding Gnome,
Avahi or hald, I use none of it so really I have nothing to compare.
Speaking of ports, did you really cleanly rebuild all of them?
When you are speaking of ports linked against port libconv, I'm
suspicious (old libtool?).
I'm using a T400 with exact same GM45 and besides "error:
[drm:pid861:intel_lvds_enable] *ERROR* timed out waiting for panel to power
off" I don't experience errors with FreeBSD 10.0-STABLE #0 r261219 amd64,
xorg trunk.
--
View this message in context:
http://freebsd.1045724.n5.nabble.com/no-su
Regarding ports, since I've converted to pkng earlier, for most part I've
just removed /usr/local/* and hit portmaster -af
--
View this message in context:
http://freebsd.1045724.n5.nabble.com/Lessons-learned-from-source-upgrade-from-FreeBSD-i386-9-2-Stable-to-FreeBSD-i386-10-0-Release-tp587889
Could you elaborate? Are those ntfs pendrives? ntfs support by ntfs.ko and
mount_ntfs was removed in 10 tree. There is fuse kernel module and a port
for ntfs in place of it (haven't tested but I'm told it works). Regarding
fat (msdosfs) pendrives, I've just mounted one created under 8-CURRENT.
-
Unfortunately, I think there is measurable penalty going to
BSD licensed tools, same system:
http://pastebin.com/BNfhevBa
--
View this message in context:
http://freebsd.1045724.n5.nabble.com/Lessons-learned-from-source-upgrade-from-FreeBSD-i386-9-2-Stable-to-FreeBSD-i386-10-0-Relea
I've made a switch early.
What gave me some bumps:
- removal of ntfs module
- vorbis-tools-1.4.0_6,3 with ogg123 missing (??)
- ports built on db42
- malloc.conf
- gcc48 entries in libmap.conf (my fault)
- subversion-static looks broken a bit, nls problems
e.g.
$ sudo svn up
Password:
Service u
I plan to stay some time on 9.2-STABLE (already pkgng and clangfied) waiting
maybe till next release from 10-STABLE tree, however 10-STABLE will be where
I will be eventually heading, so notes in this spirit are valuable reminders
at least, I appreciate it.
--
View this message in context:
http
I was surprised initially, but haven't thought about it much since.
--
View this message in context:
http://freebsd.1045724.n5.nabble.com/PACKAGESITE-spam-tp5870583p5870666.html
Sent from the freebsd-current mailing list archive at Nabble.com.
___
fre
That's very nice, but I still prefer pkg_cleanup as you don't have
to go one by one.
--
View this message in context:
http://freebsd.1045724.n5.nabble.com/Re-Plugins-support-in-pkgng-tp5739664p5858340.html
Sent from the freebsd-current mailing list archive at Nabble.com.
__
I have similar views. There is abundance of be-everything-for-everybody
Linuxes
and not enough lean and mean Unix-style kits...
--
View this message in context:
http://freebsd.1045724.n5.nabble.com/rcs-tp5850096p5850951.html
Sent from the freebsd-current mailing list archive at Nabble.com.
__
Sorry for being so sparse, but I was just talking about
general impression from few tries I gave it.
/proc wasn't main problem, usually I didn;t have any use
for it.
Basically it wasn't for me what it aimed to be- a frugal
replacement for DE. Half of things didn't work, other half
worked erra
Last time I've checked lxde was unfortunately not worth hassle.
e.g. it depends on /proc
--
View this message in context:
http://freebsd.1045724.n5.nabble.com/Can-t-compile-lxpanel-tp5817985p5818153.html
Sent from the freebsd-current mailing list archive at Nabble.com.
___
Nifty thing, waiting for MFC!
--
View this message in context:
http://freebsd.1045724.n5.nabble.com/PATCH-USB-power-usage-reporting-tp5786928p5786988.html
Sent from the freebsd-current mailing list archive at Nabble.com.
___
freebsd-current@freebsd.or
This is good moment to bring that around,
https://wiki.freebsd.org/PortsAndClang
"Help we don't want:
Submitting ports PR without fixes. We're not yet at the point
where it can help."
Is not exactly encouraging.
--
View this message in context:
http://freebsd.1045724.n5.nabble.com/7-days-o
or rather hw.dri.0.info.i915_ringbuffer_data
--
View this message in context:
http://freebsd.1045724.n5.nabble.com/sysctl-a-causes-kernel-trap-12-tp5775646p5786337.html
Sent from the freebsd-current mailing list archive at Nabble.com.
___
freebsd-curr
If you were thinking about the same as me, is
there some switch to curb hw.dri.0.info.i915_gem_hws output?
--
View this message in context:
http://freebsd.1045724.n5.nabble.com/sysctl-a-causes-kernel-trap-12-tp5775646p5786336.html
Sent from the freebsd-current mailing list archive at Nabble.co
Actually there _is_ reference to mtune in doc, so probably only your first
choice of mtune itanium2 would work, sorry for the noise.
--
View this message in context:
http://freebsd.1045724.n5.nabble.com/7-days-of-dogfood-tp5785452p5786250.html
Sent from the freebsd-current mailing list archive
Hi Anton, I recognize you from your
usual struggle with ia64 :)
Hope your work/environment really have a good
justification for keeping them around...
I would actually set only -march= because it should
set mtune to the same value by default too.
Moreover, I suspect mckinley is an alias for
I've ran 8-CURRENT amd64 desktop which evolved to 8-STABLE and
9-STABLE now, without real deal breakers.
All rougher edges I reckon from -CURRENT days gradually went away,
but system was very usable then too.
--
View this message in context:
http://freebsd.1045724.n5.nabble.com/7-days-of-dog
Closest would be
http://www.freebsd.org/news/status/report-2008-01-2008-03.html#ProPolice-support-for-FreeBSD
but port part it was not committed.
--
View this message in context:
http://freebsd.1045724.n5.nabble.com/CLANG-and-fstack-protector-tp5784739p5784992.html
Sent from the freebsd-cur
While it is only remotely related, it looks like MFC of 3.2 for STABLE
should be around the corner?
--
View this message in context:
http://freebsd.1045724.n5.nabble.com/LLVM-3-2-official-stable-port-is-still-LLVM-3-1-Basesystem-missing-important-LLVM-pieces-tp5775141p5775300.html
Sent from the
I'm on -STABLE, I was referring to editors/libreoffice and I've just
used already available option in Makefile, just commenting out
testcase.
Accidentally, I'm forcing gcc47 for ports usually, but that's different
story, handled here by ports.conf inclusion in make.conf.
I've heard there is som
To clear up confusion, I'm very well aware that that 3.2 is not
yet in -STABLE at this time, that's why I'm reporting that it could be
not import that broke LibreOffice.
Currently, after icu bump people on -STABLE were recompiling
libreoffice, and it turned out, this is no longer possible with ba
It looks clang/libreoffice has been broken a bit earlier (before import).
Currently building libreoffice on -STABLE with gcc47.
--
View this message in context:
http://freebsd.1045724.n5.nabble.com/HEADS-UP-Imported-llvm-clang-3-2-RC2-into-head-tp5766354p5771689.html
Sent from the freebsd-curr
Have you tested 9-STABLE?
I see there some 2860 bits-
http://svnweb.freebsd.org/base/stable/9/sys/dev/ral/
There are some updates in head, they should
go to -STABLE after a usual while (TM).
FYI, current wifi development and discussion takes
place in freebsd-wireless too.
--
View this messa
If there is indeed some problem with libreoffice, I will report back
after MFC :)
--
View this message in context:
http://freebsd.1045724.n5.nabble.com/HEADS-UP-Imported-llvm-clang-3-2-RC2-into-head-tp5766354p5766507.html
Sent from the freebsd-current mailing list archive at Nabble.com.
__
True, but info about state of project is correct, yes?
--
View this message in context:
http://freebsd.1045724.n5.nabble.com/UTF-8-console-tp5761405p5761662.html
Sent from the freebsd-current mailing list archive at Nabble.com.
___
freebsd-current@fre
http://wiki.freebsd.org/SysconsUnicodeProject
--
View this message in context:
http://freebsd.1045724.n5.nabble.com/UTF-8-console-tp5761405p5761407.html
Sent from the freebsd-current mailing list archive at Nabble.com.
___
freebsd-current@freebsd.org
Good luck with employing full discombobulation!
I think this is the main requirement for _cloud computing_.
--
View this message in context:
http://freebsd.1045724.n5.nabble.com/cvsup-csup-servers-stale-tp5761290p5761389.html
Sent from the freebsd-current mailing list archive at Nabble.com.
What about cases when something is broken, but not for everybody?
If only GENERIC build, how does that differ from existing tinderboxing?
--
View this message in context:
http://freebsd.1045724.n5.nabble.com/Simple-check-if-current-is-broken-tp5760481p5760700.html
Sent from the freebsd-current
> I do not loathe ULE, but I also do not use ULE.
Maybe my wording wasn't exactly suitable, but that was the
point I was trying to make. ULE is default for quite some
time (and boasted impressive benchmarks upon introduction too),
yet in reality 4BSD is far from being superseded for many.
--
Thanks for replies.
"* Finally, default values for many things on 64-bit machines
have been adjusted upward significantly to make proper use
of available resources"
Well that one should be fast to test, if it really makes so much
difference.
"* Scheduler rewrite"
They threw out old scheduler
I'm not at all up to date with DragonFly, so does anybody know
what did they change so spectacularly between 3.0/3.2?
--
View this message in context:
http://freebsd.1045724.n5.nabble.com/Re-new-DragonFly-3-2-scheduler-and-PostgreSQL-comparision-with-FreeBSD-9-1-RC1-tp5751589p5751733.html
Sent
> The LibreOffice package doesn't compile with the system's CLANG, so it
> is installed whenever LibreOffice is installed.
FWIW, it's using base clang and it does compile if ${OSVERSION} >= 900014
--
View this message in context:
http://freebsd.1045724.n5.nabble.com/FreeBSD-10-0-CURRENT-CLANG
> That's normally the case, yes, but not here.
Are you saying that if using journal, inconsistencies
in 'clean' fs are expected?
Basically I'm saying that apparently here journal
does nothing after enabling it.
Usually after really hard power dip, I need
to manually fsck as all symptoms of uncl
Yes, if I would answer 'yes' to using journal, there would be unexpected
free inodes (?) or something like that in syslog and inconsistencies if full
fsck
would be performed.
Basically if I have answered 'yes' to using journal, fs would always be
marked
'clean' regardless of state.
--
View th
If I were you, I would try regular fsck, as here
(9-STABLE) using journal has left me with fs
inconsistencies.
--
View this message in context:
http://freebsd.1045724.n5.nabble.com/UFS-journal-error-on-10-0-CURRENT-tp5739231p5739274.html
Sent from the freebsd-current mailing list archive at
>> Sometimes it would be enough just to
>> test if the port compiles before committing it (I'm talking about
>> libreoffice here which is broken)
Yeah right... Like updating libreoffice without testing
would be actually possible at all...
Are you familiar with http://redports.org/ ?
Just a
The same one I had problems earlier. I heard
that you shouldn't have boost* ports installed
prior, but when I had problems I didn't.
--
View this message in context:
http://freebsd.1045724.n5.nabble.com/Re-Why-Are-You-NOT-Using-FreeBSD-tp5714183p5716943.html
Sent from the freebsd-current mailin
I just have successfully (*) build LibreOffice by just typing
# make build in editors/libreoffice...
* Without any manually removed hiccups. Dependencies
build with clang fine too, as graphics/vigra is updated.
--
View this message in context:
http://freebsd.1045724.n5.nabble.com/Re-Why-Are-Y
*misplaced :)
--
View this message in context:
http://freebsd.1045724.n5.nabble.com/Re-Why-Are-You-NOT-Using-FreeBSD-tp5714253p5714978.html
Sent from the freebsd-current mailing list archive at Nabble.com.
___
freebsd-current@freebsd.org mailing list
ht
I saw LibreOffice as "cleaning-up" *office effort, maybe my hopes
were displaced, maybe not.
I personally do not care if it will be LibreOffice or Apache OpenOffice
as long as it's working and not pulling in KDE4/QT4/GTK (most people/linux
distros are abandoning OO for Libre though it appears),
I'm not (only) pointing finger and whining, but
maybe PC-BSD could relegate someone permanently
to help you with libreoffice, if indeed desktop is
so important to them?
I'm not sure how exactly PC-BSD and iXsystems are
related (I know that iXystems provided you with build
system at some point), b
> just the base system is
> the only part that needs to be unified, everything else can be
> installed from source.
You really don't know what you are talking about, do you?
--
View this message in context:
http://freebsd.1045724.n5.nabble.com/Re-Why-Are-You-NOT-Using-FreeBSD-tp5714253p5714654
Hmm... Speaking of libreoffice
ERROR: error 65280 occurred while making
/usr/obj/usr/ports/editors/libreoffice/work/libreoffice-core-3.5.2.2/vcl/prj
?
--
View this message in context:
http://freebsd.1045724.n5.nabble.com/Re-Why-Are-You-NOT-Using-FreeBSD-tp5714253p5714383.html
Sent from the free
I'm pro improving completeness, as most people are
really surprised when after setting WITHOUT* they
are left with old cruft from first install, what's more
important- it's getting left "as is" with all possible
(security) bugs.
Just be careful, as after recent expansion it looked
here like setti
Nice!
Is 9-STABLE also planned to be cleaned up?
--
View this message in context:
http://freebsd.1045724.n5.nabble.com/HEADS-UP-As-of-r233419-head-should-compile-cleanly-with-clang-tp5591742p5592266.html
Sent from the freebsd-current mailing list archive at Nabble.com.
_
As I said before, it's not related, because your
problem is X/ hal related, and I was speaking
of syscons.
Can you set language in X by x11/setxkbmap?
You are using hald, and xorg.conf is probably
ignored. If you insist on keeping hal,
http://www.freebsd.org/doc/en_US.ISO8859-1/books/handboo
Or you could use x11/setxkbmap each time you login.
--
View this message in context:
http://freebsd.1045724.n5.nabble.com/bsdinstall-kbdmap-tp5119535p5120743.html
Sent from the freebsd-current mailing list archive at Nabble.com.
___
freebsd-curr
That's not related at all.
For X you need something like
" Option "XkbLayout" "es""
in xorg.conf, and I complained about
syscons settings after installation.
--
View this message in context:
http://freebsd.1045724.n5.nabble.com/bsdinstall-kbdmap-tp5119535p5120710.html
Sent from the freebsd-cur
Is vidfont invoked during installation at all?
--
View this message in context:
http://freebsd.1045724.n5.nabble.com/bsdinstall-kbdmap-tp5119535p5119548.html
Sent from the freebsd-current mailing list archive at Nabble.com.
___
freebsd-current@freebsd
Is it working correctly?
e.g. Choosing "Polish ISO-8859-2"
results in just
keymap="pl_PL.ISO8859-2.kbd"
added to rc.conf, while to have fully
working polish fonts you need
font8x14=iso02-8x14
font8x16=iso02-8x16
font8x8=iso02-8x8
keymap=pl_PL.ISO8859-2
--
View this message in context:
ht
> But I have not found what it was, and switched to build i386 images only
> yet.
Indeed, only amd64 has this problem.
--
View this message in context:
http://freebsd.1045724.n5.nabble.com/9RC2-amd64-Can-t-work-out-which-disk-we-are-booting-from-tp5006547p5011412.html
Sent from the freebsd-curr
...and booting dvd rc2 iso works. I actually installed
from it to the usbdisk, just booting usb is broken.
On the side note, bsdinstall is OK, missing maybe
space/enter mapped action reminder, and certainly
"back" button.
--
View this message in context:
http://freebsd.1045724.n5.nabble.com/9RC
Blaze Drive"
but it's recognised as store 'n go)
best regards,
- Jakub Lach
--
View this message in context:
http://freebsd.1045724.n5.nabble.com/9RC2-amd64-Can-t-work-out-which-disk-we-are-booting-from-tp5006547p5006547.html
Sent
e, I'm happy it's working at all for
me.
best regards,
- Jakub Lach
--
View this message in context:
http://freebsd.1045724.n5.nabble.com/WITHOUT-GCC-for-build-target-system-without-base-gcc-9RC1-tp4951986p4952372.html
Sent from the freebsd-current
-Cposix /usr/src/usr.bin/xlint/llib/llib-lposix
llib-lposix:
lint: cannot exec /usr/obj/usr/src/tmp/usr/bin/cc: No such file or directory
*** Error code 1
best regards,
- Jakub Lach
PS. If I'm doing something retarded, feel free to point out.
I'm just feeling that 3 compilers on one sys
Or "just" extend hplip section in handbook.
http://www.freebsd.org/doc/handbook/printing-lpd-alternatives.html
It could be roughly based upon this:
http://freebsd.kde.org/howtos/hplip.php
--
View this message in context:
http://freebsd.1045724.n5.nabble.com/Freebsd-9-amd64-USB-HPLIP-what-s-th
It would be nice, If somebody would write updated
manual documenting whole process of setting up hplip.
In past, I could only get it to the point of printing
test pages (sigh...)
Before release preferably?
--
View this message in context:
http://freebsd.1045724.n5.nabble.com/Freebsd-9-amd64-U
20110331:
ath(4) has been split into bus- and device- modules. if_ath contains
the HAL, the TX rate control and the network device code. if_ath_pci
contains the PCI bus glue. For Atheros MIPS embedded systems,
if_ath_ahb
contains the AHB glue. Users need to load both
FreeBSD 9.0-BETA2 #0 r225641 amd64
$ echo |grep -q '^'; echo $?
0
$ echo |grep -qv '^'; echo $?
1
$ echo |bsdgrep -q '^'; echo $?
1
$ echo |bsdgrep -qv '^'; echo $?
0
--
View this message in context:
http://freebsd.1045724.n5.nabble.com/
After filling sticks with zeros,
and writing data again on them,
cannot replicate.
Maybe usb sticks were to blame.
One was brand new, possibly loaded
with some "helpful" software, and other
contained broken OpenBSD install.
Thanks for attention.
best regards,
- Jakub Lach
--
ommon
Intel 82801I (ICH9 Family).
As I think of it, maybe I don't need uhci
after all, but I suspected I used it with
usb/ums mouse.
regards,
- Jakub Lach
--
View this message in context:
http://freebsd.1045724.n5.nabble.com/kldload-uhci-system-grinds-to-halt-tp4723962p4724430.html
Sen
system was 8-STABLE, this configuration
worked fine.
regards,
-Jakub Lach
--
View this message in context:
http://freebsd.1045724.n5.nabble.com/kldload-uhci-system-grinds-to-halt-tp4723962p4723962.html
Sent from the freebsd-current mailing list archive at Nabble.com
it's marked
BROKEN on 9, but apparently make config
has the same symptoms.
that is,
- pressing return ends dialog
Any ideas what I have screwed up
(starting from scratch not counting)
?
best regards,
- Jakub Lach
--
View this message in context:
http://freebsd.1045724.n5.nabble.com
ed.
>
>
> --
> Vinícius Zavam
> profiles.google.com/egypcio
>
Apparently -march=native would equal -march=core2
with 65nm generation Core2s, this is not the case with
Penryns.. But there are none in the test?
However, I agree that testing with -march=native
would be simpler an
"Core i7 based procesors run slower with -march=core2 (new option) on the
system
compiler than with -march=nocona"
Sorry for double mail, isn't CPUTYPE=core2 just alias to nocona with base
compiler?
--
View this message in context:
http://old.nabble.com/FreeBSD-Compiler-Benchmark%3A-gcc-base-
Thanks for starting this interesting
comparison.
Maybe using -march=native would be
simpler and more meaningful? I'm thinking
about penryns especially.
regards,
- Jakub Lach
--
View this message in context:
http://old.nabble.com/FreeBSD-Compiler-Benchmark%3A-gcc-base-vs.-gcc-por
: 36 DMA cnt: 35 got really: 36 (System says: RDMA cnt: 36 resid -1)
--> Wanted 36 bytes, got it - DMA overrun not blocked.
--> Wanted 35 bytes, got (36)
--> Libscg says 35 bytes but got (36)
--> SCSI DMA overrun test FAILED
--> SCSI tr
In spirit of Brandon Gooch's mail (although I have lurked whole time) , I'm
currently on FreeBSD 8.1-STABLE #0 r215179 amd64, and I'm also willing to
test any relevant patches, preferably after consensus is reached.
regards,
- Jakub Lach
--
View this message in context:
http:/
mily SMBus Controller working fine with
> http://download.cnet.com/Chipset-Driver-Inte (8086)'
>
+1, since I'm the one[1] with (well, not the only one, ICH9 should be quite
popular)
"http://download.cnet.com/Chipset-Driver-Inte"; device.
best regards,
- Jakub Lach
[1
Rui Paulo-3 wrote:
>
>
> On 13 Jun 2010, at 12:40, Jakub Lach wrote:
>
>> Rui Paulo-3 wrote:
>>>
>>> On 13 Jun 2010, at 04:23, Jakub Lach wrote:
>>>
>>>> Hello.
>>>>
>>>> Is update of wpa_supplicant
Rui Paulo-3 wrote:
>
> On 13 Jun 2010, at 04:23, Jakub Lach wrote:
>
>> Hello.
>>
>> Is update of wpa_supplicant planned?
>
>
> I'll likely work on this soon.
>
> --
> Rui Paulo
>
That's splendid, thanks for fast reply.
I
Hello.
Is update of wpa_supplicant planned?
Current version in STABLE as well as CURRENT
(v0.6.8) is suffering from CTRL-EVENT-SCAN-RESULTS
log spam.
If it's the same problem, looks like it's fixed in v0.6.10
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=539915
best regar
94 matches
Mail list logo
