cd /usr/src
<...>
&& rm -r /usr/share/man &&
rm -r /usr/share/doc && rm -r /usr/share/examples &&\
make installworld && \
make cleandir && make cleandir && \
rm -rf /usr/obj && \
mergemaster && \
Well, that explains it. I'm not sure mergemaster should depend on a unclean
tree.
--
Sent from: h
Thank you for reply.
Files install fine, it's from mergemaster.
--
Sent from: http://freebsd.1045724.x6.nabble.com/freebsd-stable-f3932046.html
___
freebsd-stable@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-stable
To un
*** Creating the temporary root environment in /var/tmp/temproot
*** /var/tmp/temproot ready for use
*** Creating and populating directory structure in /var/tmp/temproot
[Creating objdir /usr/obj/usr/src/amd64.amd64...]
[Creating objdir /usr/obj/usr/src/amd64.amd64/etc...]
cd: /usr/src/share/zon
That was very helpful, thank you very much :)
--
Sent from: http://freebsd.1045724.x6.nabble.com/freebsd-stable-f3932046.html
___
freebsd-stable@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any
Is there a way to restore it? I liked the old behaviour better, it was useful
info for me.
--
Sent from: http://freebsd.1045724.x6.nabble.com/freebsd-stable-f3932046.html
___
freebsd-stable@freebsd.org mailing list
https://lists.freebsd.org/mailman/lis
Exactly, I would still use X, just with a frugal wm (dwm).
--
Sent from: http://freebsd.1045724.x6.nabble.com/freebsd-stable-f3932046.html
___
freebsd-stable@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscr
Since switch to obligatory rust, I've found Firefox to be very fragile build.
My recent attempt
with llvm from ports was succesful though.
--
Sent from: http://freebsd.1045724.x6.nabble.com/freebsd-stable-f3932046.html
___
freebsd-stable@freebsd.org ma
On the other hand, I'm having tremendous increases in Unixbench scores
comparing to
11-STABLE in the April (same machine, clang 4 then, clang 5 now) (about
40%).
I have never seen something like that, and I'm running Unixbench on -STABLE
since
2008.
--
Sent from: http://freebsd.1045724.x6.nabb
Hello,
I have
WITHOUT_DEBUG_FILES=true
WITHOUT_ASSERT_DEBUG=true
WITHOUT_KERNEL_SYMBOLS=true
in src.conf.
Nonetheless, in the last two updates I had files removed from
/usr/lib/debug/ upon make-delete-old.
--
Sent from: http://freebsd.1045724.x6.nabble.com/freebsd-stable-f3932046.html
Oh, and WITH_SVN= in src.conf installs svnlite as svn.
--
View this message in context:
http://freebsd.1045724.x6.nabble.com/SVN-UPDATE-not-respected-by-usr-ports-Makefile-tp6164511p6169002.html
Sent from the freebsd-stable mailing list archive at Nabble.com.
___
Don't know about manfile of make.conf (since SVN client IS included in base
now)
system, but maybe https://www.freebsd.org/doc/handbook/svn.html will help
you.
I don't use svn for ports, but you should probably start with an empty
directory.
--
View this message in context:
http://freebsd.1045
awk -f /usr/src/sys/tools/makeobjops.awk
/usr/src/sys/dev/hyperv/vmbus/vmbus_if.m -h
cc -target x86_64-unknown-freebsd11.0 --sysroot=/usr/obj/usr/src/tmp
-B/usr/obj/usr/src/tmp/usr/bin -c -x assembler-with-cpp -DLOCORE -O2 -pipe
-fno-strict-aliasing -march=native -g -nostdinc -I. -I/usr/src/sys
-I
I just now successfully copied 38G (second data set) to the same HDD
via USB (after it has passed extended SMART), both with UFS2 and FAT32
fs (6 CAM write errors in the second case, but as far as I can see, data
is ok). I think I hit something unrelated above, and as I've said, cannot
replicate
To sum up, looks like I cannot replicate original problem (corruption)
with the USB dual card reader any more, and the HDD via USB thing is
something different (maybe hardware related as it's exactly the same
with UFS/FAT).
--
View this message in context:
http://freebsd.1045724.x6.nabble.com
OK, I just have successfully wrote both problematic cards in the same USB
card
reader/port as the USB HDD above, using the same data set. The only CAM
errors
were at the same time as cards have run out of space.
Now testing cping between them, but as they are on the same dual card
reader/USB
po
I would think so, if only I would not clone the disk/system via the same USB
port mere weeks ago.
Moreover, sysutils/f3 fully writes and validates (checksums) 30G+ memory
cards via the same port without problems.
--
View this message in context:
http://freebsd.1045724.x6.nabble.com/FreeBSD-11-0
I'm not sure if it's the same thing. Most of the times the corruption was
silent
then.
Nonetheless, the outcome was the same after newfs HDD with UFS2-
http://www.pastebin.ca/3762661
I would 'blame' USB now, if only I did not migrate/clone the whole system to
SSD
via dump/the same USB not very
Yes, HDD and card reader was USB mounted.
This time, I've copied about 12G from 38G from internal SSD (UFS2) to
HDD via USB (FAT32), then system panicked with CAM errors.
http://pastebin.ca/3762654
Apart from that, there are no corrupted files in the way there were with
card reader. I will new
Moreover, sysutils/f3 was reading and writing with this memory card
configuration
fine. Which is why I don't _blame_ fs, I only know that FAT + cp -r
consistently
gave me problems, for one reason or another.
--
View this message in context:
http://freebsd.1045724.x6.nabble.com/FreeBSD-11-0-STA
Yes, it has happened also with another device. Which was not a card reader
(HDD
mounted by USB), and I have used the same card reader configuration to copy
the memory card content with iMac.
--
View this message in context:
http://freebsd.1045724.x6.nabble.com/FreeBSD-11-0-STABLE-0-r310265-am
As it shows your interest, I appreciate your answer very much.
I was a bit let down then, I had to (using the same card reader),
cp -r using borrowed Apple iMac. It worked as it should.
It was FreeBSD 11.0-STABLE #0 r310265 amd64 as in subject,
I will reconsider retesting now and filling a PR,
Great! Thanks for the MFC, should have checked HEAD too though, sorry about
that.
--
View this message in context:
http://freebsd.1045724.x6.nabble.com/Cannot-buildworld-r310779-on-FreeBSD-11-0-STABLE-0-r310265-amd64-tp6155011p6155058.html
Sent from the freebsd-stable mailing list archive at Na
Hello,
I'm quite puzzled. Emptied /usr/obj, make cleandir and
# make buildworld && make buildkernel... svn st is clear.
<...>
===> usr.bin/dtc (all)
echo dtc: /usr/obj/usr/src/tmp/usr/lib/libc.a >> .depend
echo dtc: /usr/obj/usr/src/tmp/usr/lib/libc++.a >> .depend
c++ -O2 -pipe -march=native
Hello,
I've recently tried to make a switch to a bigger memory card in some
device; what I've discovered, is that FreeBSD is cp-ing garbage to a
mounted FAT32 fs after first 10-20 GB (depending on luck).
What I mean by garbage are non removable 'files' with random names
which cannot be escape
See straightforward guide:
https://www.freebsd.org/doc/handbook/disks-adding.html
Additional reading:
http://www.wonkity.com/~wblock/docs/html/ssd.html
http://www.wonkity.com/~wblock/docs/html/disksetup.html
--
View this message in context:
http://freebsd.1045724.x6.nabble.com/bsdconfig-
I've overwrote the disk with zeroes- storms ceased. But as soon as you gpart
create
mbr/gpt scheme it starts. It has nothing to do with fs.
--
View this message in context:
http://freebsd.1045724.x6.nabble.com/Huge-hpet0-interrupt-storm-but-only-if-HGST-HTS721010A9E630-HDD-is-present-at-the-bo
Hello,
FreeBSD 11.0-STABLE #0 r309991 here, if I use -S 4096 the mount_msdosfs
complains about "mount_msdosfs: /dev/ada1s1: Invalid argument".
Is this expected?
See example:
$ sudo newfs_msdos -F32 -S 4096 /dev/ada1s1
Password:
newfs_msdos: trim 3 sectors to adjust to
No change after a # gpart destroy -F , like something permanently changed
after
first writes to disk.
--
View this message in context:
http://freebsd.1045724.x6.nabble.com/Huge-hpet0-interrupt-storm-but-only-if-HGST-HTS721010A9E630-HDD-is-present-at-the-boot-and-formatted-tp6151041p6151798.htm
Additionally, HGST HTS721010A9E630 was already RMAd once, either it's got
a replacement new logic board, or I've got another 'refurbished' one (it's
stamped
as such), however it did not change a thing. It's firmware is the latest I
think.
--
View this message in context:
http://freebsd.104572
Hello, I would like to share symptoms I've encountered
to hopefully spare somebody the headache I have now.
HGST HTS721010A9E630 (HGST Travelstar 7K1000) is good
value now, it's a 1TB 2,5" 7200 rpm HDD with 100 MB/s+
reads and writes. I've hoped to use it as a SSD backup.
Environment:
FreeBSD
...it's a Penryn, so looks like it's unsupported (one year too old).
Oh well. Thanks for all replies, very informative nonetheless.
--
View this message in context:
http://freebsd.1045724.x6.nabble.com/Bogus-turbo-mode-with-Intel-R-Core-TM-2-Duo-CPU-P9700-2-80GHz-tp6147461p6147683.html
Sent f
Nice! Will give it a shot next time I will have cpuctl module around :)
--
View this message in context:
http://freebsd.1045724.x6.nabble.com/Bogus-turbo-mode-with-Intel-R-Core-TM-2-Duo-CPU-P9700-2-80GHz-tp6147461p6147681.html
Sent from the freebsd-stable mailing list archive at Nabble.com.
___
I've found that the original technology was called Intel Dynamic
Acceleration,
though it should be only utilized if not all cores working?
I'm ok with overclocking, as you've said, it's not too hot and only 30C when
idle, just wanted to know what exactly is going on under the hood (as in
freque
it by ACPI. If your ACPI table exposes the turbo boost frequency but
doesn't implement it on the backend, FreeBSD doesn't know. We just
obey what we're told. :)
-a
On 25 November 2016 at 20:16, Jakub Lach <jakub_l...@mailplus.pl> wrote:
Hello,
Sinc
Hello,
Since I'm running this CPU, I've noticed there is additional
field in supported frequency (under heavy load)-
dev.cpu.0.cx_supported: C1/1/1 C2/2/1 C3/3/57
dev.cpu.0.freq_levels: 2801/35000 2800/35000 2450/30625 2133/23888
1866/20902 1600/15000 1400/13125 1200/11250 1000/9375 800/12000 70
$ moused -d -i all -p /dev/psm0
moused: proto params: f8 80 00 00 8 00 ff
/dev/psm0 ps/2 sysmouse Synaptics Touchpad
--
View this message in context:
http://freebsd.1045724.x6.nabble.com/moused-touchpad-issue-after-updating-to-FreeBSD-11-0-STABLE-0-r307755-
It looks to me, that something in this commit-
https://svnweb.freebsd.org/base?view=revision&revision=307576
forced me to explicitly set extended synaptics support-
hw.psm.synaptics_support: 1
to use normal tapping. It works now, albeit with all additional
synaptics extensions.
--
View thi
I'm going afk for a couple days, all I've got so far from moused
is-
/dev/psm0 ps/2 sysmouse generic
moused: proto params: f8 80 00 00 8 00 ff
The laptop in question is Thinkpad T400.
--
View this message in context:
http://freebsd.1045724.x6.nabble.com/moused-touchpad-issue-after-updating-
Namely, the touchpad ceased to simulate mouse buttons (doesn't respond
to tapping). Any pointers? It must be recent, source from few days ago
worked ok.
--
View this message in context:
http://freebsd.1045724.x6.nabble.com/moused-touchpad-issue-after-updating-to-FreeBSD-11-0-STABLE-0-r307755-am
Yes, when going from FreeBSD 6 to 7 on a UP system. The latter was
a little slower.
--
View this message in context:
http://freebsd.1045724.n5.nabble.com/Benchmarks-results-for-FreeBSD-11-tp6123994p6124925.html
Sent from the freebsd-stable mailing list archive at Nabble.com.
___
Unixbench is slower for me since switching to 11-STABLE from 10-STABLE,
due to triple drop of 'Pipe Throughput'. Rest looks the same or better.
That's all I know.
--
View this message in context:
http://freebsd.1045724.n5.nabble.com/Benchmarks-results-for-FreeBSD-11-tp6123994p6124304.html
Sen
Ok, missed UPDATING entry about 'video' group :)
--
View this message in context:
http://freebsd.1045724.n5.nabble.com/After-10-STABLE-to-11-STABLE-source-upgrade-user-has-lost-acces-to-drm-Intel-GM45-tp6123382p6123383.html
Sent from the freebsd-stable mailing list archive at Nabble.com.
__
e.g.
libGL error: failed to open drm device: Permission denied
libGL error: failed to load driver: i965
.drirc:
Any pointers how to fix that?
--
View thi
The kernel had just the same date, though the system was running
for a long time and I'm not sure what I could have done as I was
focused on something quite attention consuming then, but I don't think
it could be possible for me to update kernel w/o modules (I do scripted
updates).
This module
Hello again,
After a rebuild (so also powercycling), I've loaded the module just fine.
I wonder what state the system was before, but now works.
Thanks!
--
View this message in context:
http://freebsd.1045724.n5.nabble.com/What-are-current-dependencies-of-cd9660-kernel-module-tp6109797p6109
I build only needed modules, though as we can see it's not the
most robust approach. Sorry for divided reply, I somehow didn't
register your full message.
I think I was geetting by without CAM just fine.
--
View this message in context:
http://freebsd.1045724.n5.nabble.com/What-are-current-d
Sorry, should have said it's the same version. Thanks for reply.
--
View this message in context:
http://freebsd.1045724.n5.nabble.com/What-are-current-dependencies-of-cd9660-kernel-module-tp6109797p6109817.html
Sent from the freebsd-stable mailing list archive at Nabble.com.
__
Something changed in 10-STABLE, I had the same config for modules
for a long time, and I cannot load cd9660 now,
kernel: KLD cd9660.ko: depends on kernel - not available or version mismatch
kernel: linker_load_file: Unsupported file type
/boot/kernel $ ls -a
. geom_md.ko linke
Hello.
As of now, I have-
FreeBSD clang version 3.4.1 (tags/RELEASE_34/dot1-final 208032) 20140512
on FreeBSD 10.2-STABLE #0 r289058, I wouldn't have taken notice, if mesa
related
things didn't recently wish for llvm36 available; digging in CURRENT, I've
saw
that MFC of 3.5.0 was planed after o
This thread has wonderful bike shed potential.
--
View this message in context:
http://freebsd.1045724.n5.nabble.com/9-2-PRE-switch-off-that-stupid-Nakatomi-Socrates-tp5845622p5847358.html
Sent from the freebsd-stable mailing list archive at Nabble.com.
FWIW, I've meant "tribute" not orb.
--
View this message in context:
http://freebsd.1045724.n5.nabble.com/9-2-PRE-switch-off-that-stupid-Nakatomi-Socrates-tp5845622p5845814.html
Sent from the freebsd-stable mailing list archive at Nabble.com.
___
free
To be honest, I had my "They did whaaat?" moment when I initially saw
booting after that update, nonetheless when I've got reference I decided
that it was all in good spirit and appropriate even... I was definitely
disappointed that it was backed down in the end.
Now I have orb manually set up t
Why would you want to have valid ones closed?
--
View this message in context:
http://freebsd.1045724.n5.nabble.com/Some-PR-never-seen-to-delete-tp5840405p5840455.html
Sent from the freebsd-stable mailing list archive at Nabble.com.
___
freebsd-stable
Apart from it, clang looks _very_ c++ capable, as in building
boost and rebuilding os (itself) normally, so it doesn't look broken
from this point.
Just after some rebuild of OS (1-2 weeks ago?) This on git project
started to fail upon linking.
--
View this message in context:
http://freebsd
Hello,
I'm not sure if this is right list, but has anything recently changed which
could
explain why cmake c++ project (http://sourceforge.net/projects/gemrb/)
started to fail upon linking stage (looking like libstdc++ is not included
/usr/include/c++/4.2/)?
It works normally if passed gcc48 as
Actually libreoffice builds with base clang and gcc47 from ports.
I don't know about status of base gcc compiler.
--
View this message in context:
http://freebsd.1045724.n5.nabble.com/Why-can-t-gcc-4-2-1-build-usable-libreoffice-tp5786977p5788485.html
Sent from the freebsd-stable mailing list
Why they are showing up if they are not valid? It looks slightly
fishy to me. I would try to contact driver author and/or
-multimedia.
--
View this message in context:
http://freebsd.1045724.n5.nabble.com/And-for-our-next-trick-Audio-problems-Envy24HT-driver-tp5787415p5787868.html
Sent from the
As far as I remember, there is no apic option in amd64 kernel,
because it's always included.
--
View this message in context:
http://freebsd.1045724.n5.nabble.com/9-1-RELEASE-AMD64-crash-under-VBox-4-2-6-when-IO-APIC-is-disabled-tp5785747p5786129.html
Sent from the freebsd-stable mailing list
Does not apply cleanly for me on 9-STABLE.
I've tried svn patch acp(...) and patch http://freebsd.1045724.n5.nabble.com/acpi-resume-related-patch-tp5780721p5783166.html
Sent from the freebsd-stable mailing list archive at Nabble.com.
___
freebsd-stable@f
...should be fixed, as it is already reverted.
--
View this message in context:
http://freebsd.1045724.n5.nabble.com/kernel-s-make-fails-in-ath-module-stable9-tp579p5777864.html
Sent from the freebsd-stable mailing list archive at Nabble.com.
___
See tinderbox log, my -wirelesss mail etc.
I'm waiting for a fix too.
--
View this message in context:
http://freebsd.1045724.n5.nabble.com/kernel-s-make-fails-in-ath-module-stable9-tp579p5777859.html
Sent from the freebsd-stable mailing list archive at Nabble.com.
There were no changes in releng/9.1 since tagging...
--
View this message in context:
http://freebsd.1045724.n5.nabble.com/9-1-file-content-tp5773668p5773676.html
Sent from the freebsd-stable mailing list archive at Nabble.com.
___
freebsd-stable@free
Well, now there is release, but -STABLE is still pre, while -STABLE
code is already well past release builds ;)
Eh, imperfect world...
--
View this message in context:
http://freebsd.1045724.n5.nabble.com/9-1-minimal-ram-requirements-tp5771583p5773408.html
Sent from the freebsd-stable mailing
And setting "incorrect" CPUTYPE?=native is arguably better than
blindly forcing march flags for whole base build... There are plenty
of parts that don't want any march stuff.
--
View this message in context:
http://freebsd.1045724.n5.nabble.com/FreeBSD-9-amd64-buildworld-stage-4-2-fails-with
I have no problems with CPUTYPE?=native with clang and 9-STABLE,
on Penryn but I only use it for base. There is no correct CPUTYPE
which would correspond to my CPU anyway.
--
View this message in context:
http://freebsd.1045724.n5.nabble.com/FreeBSD-9-amd64-buildworld-stage-4-2-fails-with-cla
e.g. Penryn CPU:
$ cc -march=native -E -v - &1 | grep cc1
"/usr/bin/cc" -cc1 -triple x86_64-unknown-freebsd9.0 -E -disable-free
-main-file-name - -mrelocation-model static -mdisable-fp-elim -masm-verbose
-mconstructor-aliases -munwind-tables -target-cpu penryn
-momit-leaf-frame-pointer -v -resour
Humph, so it's not supported, then it's working then it's not supported
again.
How come it's working for most (I'm not being sarcastic, genuinely
concerned, as setting to native is handy)?
--
View this message in context:
http://freebsd.1045724.n5.nabble.com/FreeBSD-9-amd64-buildworld-stage-4-
http://wiki.freebsd.org/Git
--
View this message in context:
http://freebsd.1045724.n5.nabble.com/9-1-RC3-xorg-input-mouse-xfce4-panel-tp5772549p5772798.html
Sent from the freebsd-stable mailing list archive at Nabble.com.
___
freebsd-stable@freebsd.o
xorg trunk repo predates SVN for ports.
--
View this message in context:
http://freebsd.1045724.n5.nabble.com/9-1-RC3-xorg-input-mouse-xfce4-panel-tp5772549p5772797.html
Sent from the freebsd-stable mailing list archive at Nabble.com.
___
freebsd-stab
1.8.1 is in staging area (dev trunk). It will be not in packages distributed
with 9.1. They were just apps which happened to be in ports tree
at packages building for release time. There is only one branch of ports.
hal is less and less used/supported and it was never meant to be
used with Allow
Is ORAC some kind of patchset? Unless you see flow of tinderbox errors,
-STABLE is buildable almost always.
--
View this message in context:
http://freebsd.1045724.n5.nabble.com/FreeBSD-9-1-PRERELEASE-tp5772515p5772627.html
Sent from the freebsd-stable mailing list archive at Nabble.com.
There is nothing going into "release" what was not in ports
tree. (There is no release packages at all, apart from ports
that's just happened to be in regular tree at release time.
Followed by port tree slush.)
xf86-input-mouse-1.8.1 is in dev trunk xorg tree. (see -x11).
--
View this messag
http://www.freebsd.org/cgi/query-pr.cgi?pr=174671
--
View this message in context:
http://freebsd.1045724.n5.nabble.com/9-1-minimal-ram-requirements-tp5771583p5771862.html
Sent from the freebsd-stable mailing list archive at Nabble.com.
___
freebsd-st
Guys, I've heard about some absurd RAM requirements
for 9.1, has anybody tested it?
e.g.
http://forums.freebsd.org/showthread.php?t=36314
--
View this message in context:
http://freebsd.1045724.n5.nabble.com/9-1-minimal-ram-requirements-tp5771583.html
Sent from the freebsd-stable mailing lis
I'm guilty of skipping reboots and just running one mergemaster on
the end of update... But I update _very_ often.
However, I was lucky, because while I was prepared that my usual
script will fail (I read UPDATING after all), that was not the case,
as luckily I've already had said audit user fro
Prerelease was using -STABLE packages.
Magic of enviroment variables...
http://www.freebsd.org/doc/handbook/packages-using.html
--
View this message in context:
http://freebsd.1045724.n5.nabble.com/portupgrade-problem-after-upgrading-to-9-1-PRE-RELEASE-tp5770666p5770897.html
Sent from the fre
MODULES_OVERRIDE=ath ath_pci wlan ...
or
WITHOUT_MODULES= ...
in make.conf traditionally, but should be possible with .include
also.
--
View this message in context:
http://freebsd.1045724.n5.nabble.com/Question-regarding-etc-src-conf-tp5769677p5769711.html
Sent from the freebsd-stable maili
This is revision of svn repository as whole when checkout was made.
Not release branch.
--
View this message in context:
http://freebsd.1045724.n5.nabble.com/svn-revision-in-uname-tp5769581p5769591.html
Sent from the freebsd-stable mailing list archive at Nabble.com.
__
#missing-hw-float
There is no longer npx option in 9 GENERIC
i386 kernel, so there is nothing to delete
accidentally.
Traces of npx on my system (amd64) are:
$ locate npx
/usr/src/share/man/man4/man4.i386/npx.4
/usr/src/sys/i386/include/npx.h
/usr/src/sys/i386/isa/npx.c
/usr/src/sys/pc98/inclu
After _following_ recommendations (0600) in #xconsole-failure, there
is xterm error as well as xconsole one still. So definitely something is
amiss.
On the side note, revisited "What security features are present in &os;"
should mention ProPolice.
--
View this message in context:
http://freeb
#xfree86-root There is no Xwrapper (x11/wrapper) in ports tree. (Port is
expired, whole
answer outdated.)
#xconsole-failure Indeed xconsole throws such error, but not xterm -C.
--
View this message in context:
http://freebsd.1045724.n5.nabble.com/Help-review-the-FAQ-tp5762326p5769225.html
Sen
#uninstall-kerberos
Uh? Reinstalling base will delete kerberos? I don't get this answer.
I thought kerberos was part of base?
--
View this message in context:
http://freebsd.1045724.n5.nabble.com/Help-review-the-FAQ-tp5762326p5769224.html
Sent from the freebsd-stable mailing list archive at Na
I think HAST (hastd) is faq-worthy, as since release
9, it covers area previously vocally missed by some.
--
View this message in context:
http://freebsd.1045724.n5.nabble.com/Help-review-the-FAQ-tp5762326p5768880.html
Sent from the freebsd-stable mailing list archive at Nabble.com.
___
Exactly, I assumed mss.c was history already, because I looked
only in modules, while there is plenty isa stuff in
src/sys/dev/sound/isa still!
/usr/src/sys/dev/sound/isa $ ls -a
. ad1816.h mss.c sb16.csndbuf_dma.c
.. ess.c mss.h sb8.c
ad1816.c
1) This wrong list, it should be asked on -questions or -chat,
if at all.
2) Your message is too long, and looks like on the first look
like nigerian scam (sorry), most people will not take time
to read it whole.
3) This is not free tech support, this is list about development
of open source sys
Ok, but it doesn't change current primary reason of silent devices
(wrong pinout) :)
--
View this message in context:
http://freebsd.1045724.n5.nabble.com/Help-review-the-FAQ-tp5762326p5768088.html
Sent from the freebsd-stable mailing list archive at Nabble.com.
___
Closest now would be ancient snd_ad1816, maybe it could be
usable with it but it's pure speculation, good luck with finding
hardware and testing that :)
--
View this message in context:
http://freebsd.1045724.n5.nabble.com/Help-review-the-FAQ-tp5762326p5767810.html
Sent from the freebsd-stabl
Just FYI, "Microsoft Sound System Specification" probably
was meant to be Windows Sound System (?), severely
obsolete standard...
"WSS was based on Analog Devices AD1848 codec chip
with Yamaha OPL3 (YMF262-M) FM synthesis sound chip."
Probably already axed, it was supported by
dev/sound/isa/mss
#sound-card-support
First part is fine, assuming man pages will be up to date etc. Not sure
about
support for MIDI cards/MPU-401. Is this covered by uart? Don't know whatever
was "Microsoft® Sound System specification".
#es1370-silent-pcm
That's one thing, but most often silent device is caus
...so needless to say, I prefer one provided by developer (in this case
Adrian's),
even if it is laconic.
--
View this message in context:
http://freebsd.1045724.n5.nabble.com/Will-we-get-a-RELEASE-9-1-for-Christmas-tp5767716p5767789.html
Sent from the freebsd-stable mailing list archive at Na
This is good answer for end users, not so much when
somebody is genuinely concerned if there were some
unforeseen issues.
--
View this message in context:
http://freebsd.1045724.n5.nabble.com/Will-we-get-a-RELEASE-9-1-for-Christmas-tp5767716p5767785.html
Sent from the freebsd-stable mailing lis
Relevant bit is-
/usr/src/sys/kern/subr_devstat.c:295:2: error: implicit declaration of
function
'DTRACE_DEVSTAT_BIO_START' is invalid in C99
[-Werror,-Wimplicit-function-declaration]
DTRACE_DEVSTAT_BIO_START();
^
/usr/src/sys/kern/subr_devstat.c:390:2: error: implicit declar
While it's very, very minute detail, I think that in #officesuite
there should be "Apache OpenOffice" not "Apache Open Office"
as they were very careful even bureaucratic [*] if I reckon correctly,
when choosing new branding.
[*] They have "branding initiative guidelines" and held vote-
https://b
Are there any plans to stop hw.dri.0.info.i915_ringbuffer_data
from spamming sysctl?
You know, that you can actually use 'sysctl -a'.
Since some time, there is no longer /var/log/messages spam
for which I'm grateful.
--
View this message in context:
http://freebsd.1045724.n5.nabble.com/KMS-
officesuite is good, just change OO.org to Apache OpenOffice
convert-back-from-pkgng, make-kernel, release-candidate (I think that even
major releases are technically cut from -STABLE, as fresh -STABLE branch is
made from -CURRENT prior to -RELEASE, but that's minor detail) reread-rc,
use-beastie
If it is really mandatory on i386, why there is option at all?
According to man, while apic is mandatory on amd64 there
is no corresponding config or NOTES entry.
--
View this message in context:
http://freebsd.1045724.n5.nabble.com/Help-review-the-FAQ-tp5762326p5764584.html
Sent from the fr
This may be request for new questions, or this can be supplemented
partially in hardware ones I think;
- new default partition layout and it's justification (single partition
nowadays, I believe?)
- default block size and it's justification (is it 4K? why?)
- NCQ support with ada/ahci
- ahci p
Thanks!
Regarding FAQ, some info about journalling should be added to
"Chapter 9 Disks, File Systems, and Boot Loaders", especially now,
when SU+J is default.
--
View this message in context:
http://freebsd.1045724.n5.nabble.com/Help-review-the-FAQ-tp5762326p5764360.html
Sent from the freebs
As a reminder, this isn't a contest in kernel size :)
More useful would be if somebody would check GENERIC
on i386/amd64 for FAQ update.
--
View this message in context:
http://freebsd.1045724.n5.nabble.com/Help-review-the-FAQ-tp5762326p5764353.html
Sent from the freebsd-stable mailing list a
Again, sorry for confusion :)
ls -la /boot/kernel/kernel
-r-xr-xr-x 1 root wheel 5842267 25 lis 18:32 /boot/kernel/kernel
Yes, it could be artificially smaller still, but delegating to modules
things
I would load witch each startup would be absurd.
First size was whole directory with module
1 - 100 of 159 matches
Mail list logo