> In both cases, the entry is INcorrect. Juraj is correct. The swap entry is
> missing sw
> IOW the line MUST read as:
> /dev/gpt/Sea1-18noneswapsw 0 0
> or
> /dev/gpt/Sea1-18noneswapsw,trimonce 0 0
> as appropriate for the media referenced.
I updated a FreeBSD-current to the newest FreeBSD-current/14, buildworld took
11:15 (hours:minutes), buildkernel was also successful, I even appeared to be
successful with "dhclient re0".
UPDATING file says to boot single-user after buildkernel and installkernel, but
then mount -u / or mount -u
I updated a FreeBSD-current to the newest FreeBSD-current/14, buildworld took
11:15 (hours:minutes), buildkernel was also successful, I even appeared to be
successful with "dhclient re0".
UPDATING file says to boot single-user after buildkernel and installkernel, but
then mount -u / or mount -u
from Kurt Jaeger:
> Hi!
> > > On May 25, 2021, at 8:53 PM, jake h wrote:
> > > I have recently received several pieces of spam mail, apparently sent via
> > > this mailing list. These pieces of mail are the usual spam formula; Your
> > > phone has a virus, Ads, Fake blackmail, so on and s
Good morning!
> I regularly sync my FreeBSD source tree with the central repository using svn
> update. I use a one-lis script to synchonize, which sends the output of svn
> to a file, and also copies to the console. This list contained - according to
> the 'svn help update' - one line
> It is in the mini primer I wrote, along with how to bisect and other useful
> things. This will migrate into the handbook once the doc tree converts to
> asciidoc (happening this weekend).
> https://github.com/bsdimp/freebsd-git-docs/blob/main/mini-primer.md
> Warner
I looked at your mini-p
> > Does that mean CURRENT is now 14.0? I must have missed the
> > announcement.
> That is correct, 13-stable has been branched from 13-current which has now
> been bumped to 14-current.
> Because it's a major version change going from 13 to 14, pkg is a bit
> agitated regarding the ABI.
> > > D
> Disclaimer: I just started to learn git, never used it before.
> If I do understand it correctly, the switch from svn to git comes with a loss
> of continuously increasing revision numbers. Correct? If so I wonder how
> future security advisories and errata notices will be composed. Will there
> stable/11 as well as the releng branches for as long as the project has
> them under support. I wrote the code to replay commits into subversion for
> the convenience of our users on those branches. The 12.x releases will be
> built out of Subversion to preserve $FreeBSD$ expansion and other obsc
> Yes. I was answering the first question asked about FreeBSD and git...
> The clincher for me was that git is better supported by third party tools
> and has gotten quite good at 'recovery from oops' which mercurial is still
> lacking in both areas. I too have used both, and I had to re clone my
> > I hope we don't have to start signing all commits. saltstack/salt has
> > that policy, and it's extremely annoying.
> Have to? Not currently. As with all process changes, there will be
> community discussion around the different points.
> Warner
I hope not!
Signatures, at least in email me
from tech-lists:
> As subject - what will there be in base to interact with the new git repo?
> I mean, right now, for svn there is svnlite. What for git?
> Shouldn't it be in base before the move to git?
Good question, and I hope the developers and others in charge are reading your
post.
You
from Warner Losh and my last message:
> > Thanks for the information, but if you feel the need to send me a
> > not-quite-CC, please don't send me the multipart/alternative version when
> > you send the plain-text version to the list.
> > I hate multipart/alternative!
> I must apologize.
> Subversion is the source of truth for FreeBSD today.
> In the near future, likely early next month, we'll move our operations over
> to git. Git will be the source of truth after the flag day. All developer
> operations will be in git: committing to current, and MFCing will all be
> d
from tech-lists:
> As subject - is svn still canonical for -current or is it git now?
> If it's not git now, when roughly is the intended switch?
I recently updated FreeBSD doc, ports, src (current), and src12 (12-stable)
using svn (not svnup or svnlite).
But I read some time before that, FreeB
> I am seeing a problem since I moved to current on my laptop this week. It's
> odd as it is linked to the keyboard. As long as the keyboard is active,
> everything is fine, but if the keyboard is not used, after a few minutes,
> it locks up and gets very hot. The system may be busy or idle. The sy
from Kevin Oberman:
> > So I am abandoning FreeBSD 12.x .
> > Hopefully I could update 13-current from within 13-current where I have no
> > internet access but could use git from NetBSD, where I also have svn.
> > Tom
> Not really much different from subversion. .svn in /usr/sys is a
from Ed Maste:
> > Any guidance on amount of diskspace and how long it takes to clone the repo
> > ?
> I see just over 3GB in my clone, including about 2.5GB in the .git directory.
> If you have only one checkout git will require a bit more disk space
> than svn. However, if you have two or mor
from Andrey Fesenko:
> bsdinstall script, work in 2019
PARTITIONS="$DISKSLICE GPT { 512K freebsd-boot, 1M efi, auto freebsd-ufs / }
#!/bin/sh -x
# Make diskname independante
gpart modify -l freebsd-boot -i 1 ada0
gpart modify -l efi -i 2 ada0
gpart modify -l root -i 3 ada0
# Make EFI happy
from Neel Chauhan:
> For me, the following code is still necessary for me (HP Spectre x360
> 2018), which is the remaining parts of the patches not committed if you
> are using a recent kernel. I don't know about you all ThinkPad users, it
> should still apply as it's Intel in general not just
from Gleb Smirnoff:
> I'd like to commit a sweeping change over all NIC drivers,
> details can be found here:
> https://reviews.freebsd.org/D21943
> The stack changes froim the review are already committed,
> only a bunch of drivers are left. You can browse them as
> individual commits here:
>
from Niclas Zeising and my previous post:
> > On 6/22/2019 20:16, Thomas Mueller wrote:
> > > I am trying to set up UEFI to boot my FreeBSD and NetBSD installations,
> > > and later, Linux.
> > Easy. Refind should do that and allow selection from a menu.
>
from Karl Denninger and my previous post:
> > This is scary (Bitlocker), sent me to Wikipedia to look up Bitlocker.
> > Can you turn Bitlocker off after turning it on and get your system back?
> You SHOULD (better have!) kept the recovery key. If you have it, you
> can boot with it. Then turn
from Karl Denninger:
> On 6/22/2019 14:05, Rebecca Cran wrote:
> > On 2019-06-22 12:59, Karl Denninger wrote:
> >> I use Refind for this sort of thing and it has (thus far!) survived
> >> upgrades. The only "gotcha" is that I had a Windows 10 "Feature"
> >> upgrade that reset the default boot in
from Niclas Zeising:
So now I wonder why I failed four times straight building current. One
definition of insanity is doing the same thing repeatedly and expecting a
different result.
Maybe the build host, 11.1-STABLE from July 30, 2017, was too old? I wouldn't
have thought it was too old.
from Niclas Zeising:
> I run a build WITH_CLANG_EXTRAS, and that worked, on current, last weekend, if
> that's what you're asking about.
> This won't take away the need for llvm ports in certain ports builds, however,
> such as firefox and mesa.
So now I wonder why I failed four times straight
> In general, WITH_CLANG_EXTRAS controls the building of extra tools such
> as a disassembler, and tools for working on clang itself such as bug
> reporting tools. I don't have a really detailed answer because I've
> never enabled the option. I've always perceived it as being something
> most peo
What do most FreeBSD users who rebuild system from source do regarding
WITH_CLANG_EXTRAS in /etc/src.conf ?
I have WITH_CLANG_EXTRAS=yes in /etc/src.conf and wonder if that could be
screwing my build.
Build seems to stumble on the llvm stuff, and llvm has really bloated in recent
times.
But t
from tech-lists:
> What do you do before buildworld?
> I'll rm -rf /usr/obj and /var/cache/ccache [1], create them again, then in
> /usr/src I'll do this:
> make -j32 cleanworld && make -j32 cleandir && make -j32 clean
> before make buildworld. it's probably overkill but it'll f
> Hi Tom,
> Are you using any nonstandard build options/modes?
> Cheers!
> -Enji
I don't think I am using any nonstandard build options/modes.
/etc/src.conf is
WITHOUT_SVNLITE=yes
WITHOUT_PORTSNAP=yes
#WITHOUT_MANCOMPRESS=yes
#WITHOUT_DOCCOMPRESS=yes
WITHOUT_SENDMAIL=yes
WITH_CLANG_EXTRAS=ye
I have failed in three attempts over the past week to build FreeBSD-current
amd64, error message is about the same each time.
Build host uname -a shows
FreeBSD amelia 11.1-STABLE FreeBSD 11.1-STABLE #4: Sun Jul 30 17:28:39 UTC 2017
root@amelia2:/usr/obj/BETA1/usr/src11/sys/SANDY11NC amd64
I may need to buy parts for a new computer because of malfunctions on current
motherboard and CPU (Intel Sandy Bridge dating to May 2011).
Question is whether I am better off, regarding open-source-friendliness of
graphics chips for running Xorg, with AMD Ryzen or the newer Intel chipsets. I
k
I just submitted /var/run/dmesg.boot from my current NetBSD and from FreeBSD
11.1-STABLE.
I was surprised to see some other BSD OSes listed, including 5 dmesg reports
from Bitrig and 3 from RetroBSD.
I had been tracking three bitrig trees from https://github.com/bitrig : bitrig,
bitrig-xenocar
I can submit a dmesg even if I'm in NetBSD at the time: mount the FreeBSD
partition and get the latest /mount-point/var/run/dmesg.boot .
Question is what about those devices that don't work in FreeBSD but work in
NetBSD, or which work in neither FreeBSD nor NetBSD? I'm thinking of re, where
on
Excerpt from Oliver Pinter:
> Let's do some more step backwards, and see how the graphics driver
> developments works from the corporation side.
> They not bother about any of the BSDs, they focus only to Windows and
> Linux. If you want to use a recent (haha recent, something after 2014) you
> a
> Wow, this blew up quite a lot bigger than I anticipated. I'll try to
> summarize the discussion a bit below and then suggest a way forward.
> The primary reasons we want to do this is because there are conflicts between
> the new drm drivers in ports, and the drm drivers in base, since they con
from Ngie Cooper:
> > On Oct 28, 2017, at 18:09, Gordon Tetlow wrote:
> > I have an Intel NUC that uses an Intel 8260 wireless driver. This works
> > flawlessly if I load the module if_iwm via the loader or the rc.conf
> > kld_list directive.
> > Do we know if the iwm driver not being in GENERI
from Allan Jude:
> > Anyone has any recommendations or experience about how to use native 4K
> > disks with FreeBSD?
> > --HPS
> It is not possible in legacy/BIOS mode, because the BIOS calls do not
> let you specify a sector size.
> However, you SHOULD be able to boot from the 4k devi
What is the status of lang/gcc6-aux and lang/gcc5-aux regarding buildability in
FreeBSD-current?
I read about these packages not building on current subsequent to ino64, but
there was no BROKEN notice in the Makefiles.
I tried and failed on both: gcc5-aux directly and gcc6-aux as a dependency o
from Adrian Chadd:
> valgrind broke as part of the ino64 work :(
Valgrind was not on my mind! Your post sent me to
ls -d /usr/ports/*/val*
to find valgrind, and then read the pkg-descr.
One less tool for getting debugging information when something crashes?
Tom
> Maybe not, but I think so. synth(8) requires the ada compiler which means
> lang/gcc6-aux or lang/gcc5-aux and those DID require work to install on
> ino64. I believe that this is now resolved, but I would seriously consider
> simply installing synth from the package. It has no run or lib depends
On Fri, Jun 23, 2017 at 4:12 PM, Thomas Mueller wrote:
> > I remember some ports on FreeBSD-current were rendered nonbuildable by the
> > introduction of 64-bit inodes (ino64).
> > What is the progress on resolving those snags?
> > I haven't heard anything re
I remember some ports on FreeBSD-current were rendered nonbuildable by the
introduction of 64-bit inodes (ino64).
What is the progress on resolving those snags?
I haven't heard anything recently and was unable to find anything on
wiki.freebsd.org.
So how do I know the current status?
I am par
>From Simon J. Gerraty:
>> Bug occurs when building or configuring ports, syntax error in
>> /BETA1/usr/share/mk/bsd.compiler.mk line 52
>This is of course specific to your particular arrangement
>if you'd mounted /BETA1/usr/ports on /usr/ports, it would function as
>you wish, or if /BETA1/
>From Simon J. Gerraty:
> Thomas Mueller wrote:
> > I go into /BETA1/usr/ports/ports-mgmt/synth , run
> > env MAKESYSPATH make all-depends-list
> I assume you mean MAKESYSPATH=something? otherwise env itself should
> vomit
When I did those last examples, that last
>From Simon J. Gerraty:
> > Thomas Mueller wrote:
> > For building the system, MAKESYSPATH should be $SRCDIR/share/mk , to be in
> > sync.
> > I tried "make -V MAKESYSPATH" from several SRCDIRs, and that's what
> > happened.
> Yes. If you l
>From Simon J. Gerraty:
> Thomas Mueller wrote:
> > It seems to me that MAKESYSPATH should match the host building system
> > FreeBSD version.
> Which would only be correct if building the same version of FreeBSD as
> is running on the host.
> Many folk work
> On Sun, May 21, 2017 at 1:54 AM, Thomas Mueller wrote:
> > I tried building ports, starting with ports-mgmt/synth, on HEAD
> > (12-current) and ran into difficulties with syntax error in bsd.compiler.mk
> > .
> > With PORTSDIR on another partition, mounted as
from O. Hartmann:
> Just for my curiosity: do you have "options FLOWTABLE" defined in your kernel
> config?
I was not even aware of "options FLOWTABLE", having not seen it in GENERIC
kernel config.
I had to look in $SRCDIR/sys/conf/NOTES to find it.
What would I get by adding "options FLOWTAB
from YongHyeon PYUN:
> [removed stable@ from CC]
> > I recently updated my 10.1-STABLE to 11.0-STABLE and find I can no longer
> > connect with the Ethernet.
> > dhclient re0 produces
> > DHCPDISCOVER on re0 to 255.255.255.255 port 67 interval 4
> > DHCPDISCOVER on re0 to 255.255.255.255 port
I tried building ports, starting with ports-mgmt/synth, on HEAD (12-current)
and ran into difficulties with syntax error in bsd.compiler.mk .
With PORTSDIR on another partition, mounted as /BETA1, I got these errors, but
not when I null-mounted /BETA1/usr/ports as /usr/ports.
I shouldn't have t
Who is the maintainer, if any, for re(4) Ethernet driver that is again giving
me trouble on Intel Ivy Bridge computer with MSI Z77 MPOWER motherboard?
I remember Kevin Lo, but have checked the web archives for freebsd-current and
freebsd-net, and find Kevin Lo's last posts were during October 20
I recently updated my 10.1-STABLE to 11.0-STABLE and find I can no longer
connect with the Ethernet.
dhclient re0 produces
DHCPDISCOVER on re0 to 255.255.255.255 port 67 interval 4
DHCPDISCOVER on re0 to 255.255.255.255 port 67 interval 11
DHCPDISCOVER on re0 to 255.255.255.255 port 67 interval
I remember having problems with Realtek 8111E Ethernet on this Intel Ivy Bridge
computer a couple years ago, and now the problem has resurfaced.
I am fresh from updating FreeBSD to 11-STABLE and HEAD on two partitions, and
in both cases can not connect with onboard Ethernet.
>From NetBSD 7.99.1
> vt(4) is not a pleasant thing to look at. I am not implying that it is bad
> code or badly done. I am just saying that it is pretty gnarly and is not
> the sort of thing most enjoy dealing with. I got the distinct feeling that
> ray@ found the job much uglier than he anticipated when he took th
This raises the question, how much diskspace is required or advised for a full
FreeBSD installation if both the base system and ports are built from source?
Some messages in this thread have raised the possibility of needing 49 to over
100 GB, which is much more than I have allotted.
Also, what
If I want to keep up with FreeBSD-current with new graphics drivers, is it
sufficient to keep only the freebsd-base-graphics source tree to avoid the
redundancy of keeping the regular src tree as well?
I notice some things are not updated as frequently in the freebsd-base-graphics
tree; "git pu
Is the newcons nonsupport for console screensaver related to the nonsupport for
newcons splash screen?
Situation is the same in NetBSD 7.0_RELEASE and STABLE, and current/head, no
support for screensaver. DRMKMS is NetBSD's equivalent/counterpart of
FreeBSD's newcons. Boot to console comes up
I don't really know what to quote here, but the documentation is not clear.
There ought to be something in UPDATING.
Issue is building and installing more than one kernel. I tried once, and it
didn't work right. I had to go back to one kernel at a time and NO_MODULES=yes
on second and subseq
from Glen Barber:
> As many know, work has been in progress for quite some time to provide
> the ability to package and upgrade the FreeBSD base system using pkg(8).
> The majority of the initial implementation has provided much of the core
> functionality to make this possible, however much work
> > root@amelia:~ # pkg info -f xserver
> > Shared object "libssl.so.7" not found, required by "pkg"
> > What happened here? Bug in new FreeBSD?
> This is explained by the UPDATING entry of October 2015:
> 20151030:
> The OpenSSL has been upgraded to 1.0.2d. Any binaries requiring
>
Thanks for helpful advice, too much to quote, and I am too tired anyway after a
sleepless night and day, was up too late with the HP LaserJet printer.
It looks like I might have to rebuild all ports except for portmaster and pkg,
already done; update perl to perl5.22, check the list of ports for
Has there recently been a version bump in the shared libraries? I saw no
warning on this in the src or ports UPDATING files.
I can no longer startx and can no longer run many other ports, getting errors
like
Shared object "libcrypto.so.7" not found, required by "X"
xinit: giving up
xinit: unab
I just updated FreeBSD-current to r294248, and can no longer startx.
Error message is
xauth: file /home/arlene/.serverauth.1177 does not exist
Shared object "libcrypto.so.7" not found, required by "X"
xinit: giving up
xinit: unable to connect to X server: Connection refused
xinit: server error
> > It looks like a problem with WITHOUT_MANCOMPRESS.
> > I am looking into it.
> A fix is now committed. It has been broken since June.
> Regards,
> Bryan Drewery
Thanks for the fix, computer is now busy with NetBSD update from 6.99.44 (16
months old) to 7.99.21 for both amd64 and i386, but
> > It looks like a problem with WITHOUT_MANCOMPRESS.
> > I am looking into it.
> A fix is now committed. It has been broken since June.
> Regards,
> Bryan Drewery
Thanks for the fix, computer is now busy with NetBSD update from 6.99.44 (16
months old) to 7.99.21 for both amd64 and i386, but
I was trying to test the new i915 graphics driver but got stuck in building and
installing the userland:
/usr/share/man/man2/mknodat.2 -> /usr/share/man/man2/mknod.2
/usr/share/man/man2/munlock.2 -> /usr/share/man/man2/mlock.2
/usr/share/man/man2/munlockall.2 -> /usr/share/man/man2/mlockall.2
/us
from Jeffrey Bouquet:
> I'd installworld in single user mode... sorry for no backstory. Worked here.
Sure, I used single user mode, as advised in UPDATING file.
from Sergey Kandauro:
> This looks like if you would try to installworld on newer sources and older
> objs without doing buildworld f
I was trying to test the new i915 graphics driver but got stuck in building and
installing the userland:
/usr/share/man/man2/mknodat.2 -> /usr/share/man/man2/mknod.2
/usr/share/man/man2/munlock.2 -> /usr/share/man/man2/mlock.2
/usr/share/man/man2/munlockall.2 -> /usr/share/man/man2/mlockall.2
/us
> > set hint.rsu.0.disabled="1"
> This isn't sufficient. This leaves the device named rsu0 but disables it
> without
> letting other drivers attach to it. You need to remove the rsu driver
> entirely
> or use devctl to force the driver to ndis.
> John Baldwin
I can try on the slight chance t
> If you haven't ever successfully run ndis before on this hardware, then
> testing
> the patch is quite useless :( Since we don't have a working reference point.
> Sorry for waisting your time.
> Totus tuus, Glebius.
I remember trying ndis from a USB-stick installation of FreeBSD 9.2-STABLE, b
> If you haven't ever successfully run ndis before on this hardware, then
> testing
> the patch is quite useless :( Since we don't have a working reference point.
> Sorry for waisting your time.
> Totus tuus, Glebius.
I remember trying ndis from a USB-stick installation of FreeBSD 9.2-STABLE, b
> T> Thinking I might have used the wrong syntax with ifconfig, I tried again
> with rsu0 instead of ndis0 or other failed attempts, and was successful
> connecting to Internet.
> AFAIU, if you got rsu(4) driver in your kernel it will attach to the hardware,
> and the ndis(4) driver won't be abl
UPDATE: I was successful with buildworld and kernel with the patch, both the
custom kernel with ndis and the GENERIB kernel without ndis.
GENERIB differs from GENERIC by eliminating some old devices like SCSI cards
and ISA EThernet cards, but I add some wi-fi drivers like urtw, urtwn and rsu.
U
> I've build a small nanobsd image (for i386 arch) that include this patch:
> http://dev.bsdrp.net/FreeBSD/GLEBWIFI-0.2-full-i386-vga.img.xz
> You can install it on a small (128MB USB flash) for testing it without
> re-installing your system.
> Installation instruction for copying this image into
I did the update a little before your last message.
svn revert
by itself doesn't work, I get an error message, then run
svn help revert
and that gets me on the right track.
I did the update and patch from NetBSD, which I believe works the same as it
would from FreeBSD, subsequently booted int
You sent a patch, net80211.diff.bz2 .
Before I extract and apply the patch, how does that differ from D2655.diff ?
Is it an updated version, does it include ndis or only FreeBSD-native drivers?
Do you want me to test Hiro H50191 with native rsu, or ndis, or both separately?
I guess I need to d
> I ended with doing the aforementioned 2 changes as one.
> The diff is living here:
> https://reviews.freebsd.org/D2655
> It spans the net80211 layer and converts (almost) all 802.11 drivers
> to new KPI. Now it also converts if_ndis, and this is the change I
> am asking you to test.
> Unlike
> I ended with doing the aforementioned 2 changes as one.
> The diff is living here:
> https://reviews.freebsd.org/D2655
> It spans the net80211 layer and converts (almost) all 802.11 drivers
> to new KPI. Now it also converts if_ndis, and this is the change I
> am asking you to test.
> Unlike
> I ended with doing the aforementioned 2 changes as one.
> The diff is living here:
> https://reviews.freebsd.org/D2655
> It spans the net80211 layer and converts (almost) all 802.11 drivers
> to new KPI. Now it also converts if_ndis, and this is the change I
> am asking you to test.
> Unlike
> I need to make couple of non-functional but rather large changes
> to the if_ndis driver and will appreciate if anyone signs up to
> test my changes. Please contact me if you can provide help.
> Totus tuus, Glebius.
I have two possible candidates for testing:
Hiro H50191 USB wi-fi adapter
> As part of the "opaque ifnet project" [1], we are doing some code shake
> with all IEEE802.11 (read WiFi) drivers. The drivers, that provide a parent
> interface for the wlan(4) interface.
> The core idea is that parent device loses its ifnet(9) structure. The
> code is already complete for
Excerpt from Baptiste Daroussin:
- Initial support for OS X
- Initial support for NetBSD/EdjeBSD
How would pkg-1.5.0 integrate with NetBSD pkgsrc?
I didn't think there were any plans to port FreeBSD ports to NetBSD. Or is
such a plan in the works?
EdjeBSD should be EdgeBSD. A little spelling
> On Thu, Feb 26, 2015 at 10:08:40PM -0500, Michael Butler wrote:
> M> The recent changes which served to hide "struct ifaddr" have broken
> M> net-snmp:
> I know and slowly working on that:
> https://lists.freebsd.org/pipermail/svn-src-head/2015-February/068674.html
> Totus tuus, Glebius.
How
On Mon, Sep 22, 2014 at 11:15 AM, Thomas Mueller
wrote:
> I was successful on make buildworld and kernel, but make installworld failed
> on a missing file somewhere:
>
> /usr/share/man/man3/pmclog_read.3.gz -> /usr/share/man/man3/pmclog.3.gz
> ===> lib/libproc (install)
&g
I was successful on make buildworld and kernel, but make installworld failed on
a missing file somewhere:
/usr/share/man/man3/pmclog_read.3.gz -> /usr/share/man/man3/pmclog.3.gz
===> lib/libproc (install)
install -C -o root -g wheel -m 444 libproc.a /usr/lib
install -C -o root -g wheel -m 444
I want to build a kernel with debugging for a specific device, rather than for
everything.
Device of interest is re (Ethernet driver), also rsu (USB wlan adapter).
I looked in Makefiles, also NOTES files, found some DEBUG options but
nothing really general that could be applied to any desir
> You need to install sysutils/udfclient. Your cd is in UDF format, that isn't
> covered by standard mount_udf.
--
> Regards,
> Ruslan
Let me also say, one of the MASTER_SITES listed in the Makefile is no good
(NXDOMAIN):
http://www.13thmonkey.org/udfclient/releases
I just tried and failed, got
> You need to install sysutils/udfclient. Your cd is in UDF format, that isn't
> covered by standard mount_udf.
--
> Regards,
> Ruslan
I just tried and failed, got error messages but still got fusefs-libs which
could prove useful:
cc -O2 -pipe -fno-strict-aliasing -I/usr/local/include -D_FILE
I have a DVD, a data DVD rather than movie or music, from Seagate Business
Storage 2-bay NAS, that is mountable with mount_cd9660 but not readable in
FreeBSD and NetBSD, using current amd64 versions of FreeBSD and NetBSD.
ls /cdrom showed nothing; ls -al /cdrom showed
total 6
dr-xr-xr-x 2 roo
My Internet connection on this computer is very iffy at best, not running as I
type this.
Motherboard is MSI Z77 MPOWER.
Ethernet is Realtek (re): good with NetBSD, Linux and Haiku, (Free,Open and
DragonFly)BSD bug out.
Only Internet connection for FreeBSD is Hiro H50191 USB-stick wireless a
> Possibly increase the timing variables under:
> sysctl hw.usb.timings
> If they are not there, possibly the USB_DEBUG option has been removed from the
> kernel config. Can you check that?
--HPS
What are the units for sysctl.hw.usb.timings? Seconds? Milliseconds?
I ran sysctl hw.usb.timing
from Adrian Chadd:
> Buy a mini-pcie atheros wifi card.
How do I know this would work with FreeBSD and/or NetBSD?
I could switch the hard drives between the two computers, or put one hard drive
in a Sabrent enclosure: IDE and SATA inside, USB 2.0 and eSATA outside
interface.
I could also buy
from Adrian Chadd:
> please bug freebsd-usb@ about flakey usb devices.
> I have a couple that i need to chase up hans about. they used to be less
> flakey.
Flaky USB devices in FreeBSD, also NetBSD, are not limited to wireless adapters.
I get console messages about keyboard and mouse l
from Idwer Vollering :
> I'm on 10-STABLE r267049, with a local change to
> sys/dev/usb/wlan/if_rsu.c that reverts EW7622UMN back to RTL8192SU_3.
> > At least my adapter is working a bit more stable now :-)
> Mine seems to get stuck in "rsu_calib_task: running calibration task" often.
> HTH,
>
> Yes, please apply by hand. I'll see if I can do some testing myself. I happen
> to have one of these adapters too and the link is very unstable :-)
>
--HPS
Sometimes Hiro H50191 USB-stick wireless adapter
from Idwer Vollering :
I have a patch for that:
Index: head/sys/dev/usb/wlan/if_rsu.c
===
--- head/sys/dev/usb/wlan/if_rsu.c (revision 266970)
+++ head/sys/dev/usb/wlan/if_rsu.c (working copy)
@@ -69,11 +69,13 @@
#include
I sent this message, without this top part, over an hour ago, and notice wlan0
is still up. I intended but forgot to CC to freebsd-current. But I am in
newcons, having not started X so far this boot session. Maybe something rotten
with Xorg, or interaction between rsu and X, or rsu and Firefo
I had two crashes, or more accurately, freezes, when web-browsing.
First was with Firefox on an easy National Weather Service page, I was
scrolling down with down-arrow key, and system suddenly froze, no response to
keyboard or mouse, display stayed (until I hit Reset).
uname -a shows
FreeBSD
> I'm using the -current -- FreeBSD valfenda 11.0-CURRENT FreeBSD
> 11.0-CURRENT #16 r263202: Sat Mar 15 00:23:05 BRT 2014
> root@:/usr/obj/usr/src/sys/VALFENDA amd64
>and the gnash don't work to me. I'm not using the flash plugin (from
> linux emulator) because I think different about this
1 - 100 of 198 matches
Mail list logo
