gine to be on the safe side */
if (request->flags & ATA_R_DMA) {
--
Thomas Mueller [EMAIL PROTECTED]
___
[EMAIL PROTECTED] mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to "[EMAIL PROTECTED]"
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
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
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 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 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
> 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
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
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
> 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
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
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 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 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 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 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 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
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
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
> 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
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
> 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
> 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
> 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
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 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
> 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
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
> 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
> 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
> > 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
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
> > 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 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
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
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
> > 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
>
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
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
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
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
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
> 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
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
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
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 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
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
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
> 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 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
>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:
> > 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:
>> 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/
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
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
> 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
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
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
> I have successfully installed FreeBSD-9.0-BETA2 to an amd64 bit
> machine, I have used the ports to install xfce and xorg. When I type
> startx, I get a screen with a bunch of colors no mouse, no keyboard,
> just colors. The machine has nvidia onboard graphics. I am trying to
> get kernel sour
Some more ideas on the new bsdinstaller cross my mind.
Since the way the bsdinstaller would make partitions is unpredictable, at least
to the uninitiated, and in all likelihood at variance with how much space the
user wants to allocate, it might be better to offer a roadmap to help guide the
us
><"Thomas Mueller
There was a typo on my part that I failed to correct, missing > at the end of
From: "Thomas Mueller" and others on the boot
partition:
So the 64 KB boot partition, nonbootable on my computer, is for legacy BIOS and
no good on UEFI?
But I was able
>From "Matthew D. Fuller" :
> I've been meaning to mention this, but we really should document
> somewhere that it has a _MAXIMUM_ size.
> I setup a system a few weeks back with GPT, and figured I'd just make
> the first 'real' partition start at the 1 meg mark. And make
> everything before tha
More concerns and questions onthe new bsdinstall:
There is no upgrade function. How will a user be able to upgrade to BETA3 (or
RC1?) without wiping out BETA2 installation?
For instance, user might have built many software applications from ports and
not want to rebuild everything.
Other issu
>From Brett Glass :
> Unfortunately, due to past history, /usr is mixed-use. It normally
> contains both configuration information -- e.g. /usr/local/etc --
> and more volatile data such as users' home directories. This
> prevents /usr/local/etc, which also contains mission-critical
> configuratio
I see a thread, "FreeBSD 9-Beta3 on X300 problems." and now am curious about
what is the current beta?
I looked at ftp://ftp.freebsd.org/pub/FreeBSD/releases/
and found a BETA3 but only for some platforms not including i386 and amd64.
Maybe the burncd problem, not working on SATA, is a temporar
I looked at ftp://ftp.freebsd.org/pub/FreeBSD/releases/
and found a BETA3 but only for some platforms not including i386 and amd64, but
that was yesterday.
I looked later during the day and found the BETA3 for i386 and amd64.
Now the question is how to update without trashing the BETA2 install
> Hi all,
> I've committed this to -head.
> I'd appreciate it if csup users would give this a thorough testing and
> report back to the list with results.
> I won't submit this as a merge candidate this to stable/9 without a
> whole lot of testing. :)
> Thanks,
> Adrian
I am now in 9.0-
> cvsup is a port, so you would need to install that to have cvsup. csup
> and cvsup are totally different code bases in different languages.
> (csup is C and cvsup is Modula-3.) You probably want to install cvsup
> as a package as installing the port also requires building all of the
> Modula-3 co
One issue that has not come up on the emailing list is that dd, designed to
work with memsticks of various capacities, can not make the backup gpt at the
end of the memstick.
Partition is just big enough to hold the data, and I ran out of inodes at times
due to the installer writing to /tmp on
> MHO different OS releases (Unix or not) are usually at the state of
> FreeBSD current regarding stability. FreeBSD late BETA and early RC
> are usually very stable. Therefore the approximate one month period
> between the first beta and the release is adequate time.
I see your point, especially
I just finished the upgrade from source from 9.0-BETA2 to RC1, and I find two
problems.
First, I lost my users; nonroot user names are not recognized, if for instance
I type
passwd arlene
I already tried to login as arlene with old password, no good.
I copied the /etc directory to a backup on
from Tom Evans :
I have had this happen before, the PEBKAC. When running mergemaster,
> it will prompt you to install new passwd, master.passwd and group
> files - if you have added local users you must not say yes to this,
> you must either merge the changes in or keep your local one.
> If you
from Tom Evans :
I have had this happen before, the PEBKAC. When running mergemaster,
> it will prompt you to install new passwd, master.passwd and group
> files - if you have added local users you must not say yes to this,
> you must either merge the changes in or keep your local one.
> If you
> pwd_mkdb -p /etc/master.passwd
Cheers,
Matthew
> Dr Matthew J Seaman MA, D.Phil.
That did it! Now I can login as nonroot and startx.
I found pwd_mkdb in my searching, but would not have known to use '-p'. I
might have done
pwd_mkdb /etc/master.passwd
from Do
> If you would like to use csup/cvsup mechanisms to access the source
> tree the branch tag to use is now "RELENG_9_0", if you use "." (head)
> you will get 10-CURRENT. If you would like to access the source tree
> via SVN it is "svn://svn.freebsd.org/base/releng/9.0/". We still have
> the nit th
> On 18/11/2011 10:53, Thomas Mueller wrote:
> > *default release=cvs tag=RELENG_9
> > Am I screwed, am I OK, or do I simply have to rerun csup with RELENG_9_0
> > instead of RELENG_9 ?
> Not screwed, but you'll be running 9.0-PRERELEASE rather than 9.0-RC2.
> In the old days home was typically a separate partition that was
> mounted on /home. If you didn't have a partition the installer would
> create /usr/home and symlink /home to it. The root was also typically
> an independent partition, so it made sense not to clutter it up with
> home directori
> On 11/27/11, Lowell Gilbert wrote:
> > "b. f." writes:
> >>> > > What is the role of "options atapicam" and "device ATA_CAM" in kernel
> >>> > > config file?
> >>> > > Are they redundant? Kernel will build with both these options, but
> >>> > > will it make things go awry? Is ATA_CAM deprec
According to ugen man page, ugen can be compiled into the kernel with
device ugen
in config file.
I tried that in the kernel config when upgrading from FreeBSD 9.0-RC1 to RC2,
but the kernel build stopped quickly with the message that ugen was not valid.
After removing that line from kernel con
> On Wednesday 30 November 2011 11:24:39 Thomas Mueller wrote:
> > According to ugen man page, ugen can be compiled into the kernel with
> > device ugen
> > in config file.
> > I tried that in the kernel config when upgrading from FreeBSD 9.0-RC1 to
> > RC2, but
^ What version of FreeBSD do you run? Do you not have a ugen manpage? Can you
run "man ugen"?
^ I have the manpages for ugen, and "man usb", also "man 4 usb", but no diff as
such.
^ I guess ugen manpage failed to reflect becoming part of usb.
^ Tom
> There is:
> share/man/man4/ugen.4
>
>From Mehmet Erol Sanliturk :
> Supplying only a console-mode FreeBSD as a release is making FreeBSD
> unusable for
> peoples who they are not computing experts .
> To allow less experienced people to use FreeBSD easily , it is necessary to
> include a
> selected ports/packages into release di
I can't get cdrtools (cdrecord or readcd) to work on FreeBSD 9.0-RC2, and now I
see RC3 is available.
I tried "options ATA_CAM" in kernel config, removing "device atapicam", but
still
readcd -scanbus or
cdrecord -scanbus
refuses to work, running as root.
"camcontrol devlist" shows my DVD driv
from my last message:
I can't get cdrtools (cdrecord or readcd) to work on FreeBSD 9.0-RC2, and now I
see RC3 is available.
I tried "options ATA_CAM" in kernel config, removing "device atapicam", but
still
readcd -scanbus or
cdrecord -scanbus
refuses to work, running as root.
"camcontrol dev
> Recompile the port; the CAM ioctl numbers have changed.
> Cheers
> Michiel
When did these CAM ioctl numbers change? Was it before or after I built and
installed cdrtools?
Running ls -rtl /var/db/pkg/cdrtools-3.00_1 produces
total 48
-rw-r--r-- 1 root wheel 17550 Sep 26 09:20 +MTREE_DIRS
--- On Fri, 12/9/11, Marius Strobl wrote:
> +0000, Thomas Mueller wrote:
> > > Recompile the port; the CAM ioctl numbers have
> changed.
> Cheers
> > > Michiel
> > When did these CAM ioctl numbers change? Was it
> before or after I built and installed cdr
--- On Sat, 12/10/11, Marius Strobl wrote:
> > > I'm not sure what CAM IOCTL number change others
> are
> > > referring to but
> > > you certainly need to rebuild libcam consumers
> after
> > > r225950, which
> > > was merged to stable/9 in r226067 on October 6
> 2011.
> > > Marius
> > Than
> [-- Attachment #1 --]
> [-- Type: text/plain, Encoding: base64, Size: 49K --]
> Help
> - Reply message -
> From: freebsd-current-requ...@freebsd.org
> To:
> Subject: freebsd-current Digest, Vol 465, Issue 5
> Date: Thu, Sep 13, 2012 8:00 am
(and much more)
This looks like something th
> Hello there.
> I have problem here, and don't know if it's bug or "feature" :)
> If I prerare boot media (hdd, sd card,usb, etc) with FreeBSD, and NOT
> create there fstab, I see such behavior:
> 1. I need enter manually where from mount root (e.g. ufs:ada0s1a or
> ufs:ada0s1a rw)
> 2. If I ent
from Brett :
> Just an observation: a few years ago when I got sick of Linux's "headlong
> rush" development model, I subscribed to various BSD mailing lists to see what
> +else was out there. I considered FreeBSD at the time - there was a
> neverending avalanche of "[head tinderbox] failure" m
> On Tue, 1 Jan 2013 10:55:58 -0800
> Tim Kientzle wrote:
> > On Jan 1, 2013, at 8:12 AM, Brett Wynkoop wrote:
> > > Greeting-
> > > The driver is working much better than the driver currently in
> > > head. I have maintained an ssh connection to the BeagleBone for
> > > more than 24 hours!
>
Excerpt from Andrey Fesenko :
> And other problems.
> 1) wi-fi
> standart rtl8192cu - not work
> change AR5B95 - work n-mode (thanks Adrian Chadd :) need hack BIOS
> dev.acpi_ibm.0.wlan: 1 <- read only
> hardware switch work, not send mesage
What did you try to make rtl8192cu work? Did you try N
>From Andrey Fesenko :
> NDIS failed to raise working version. Win driver terrible ~5 firmware and
> other.
> urtwn such as usb devices and no porting FreeBSD only dirty hack
> http://lists.freebsd.org/pipermail/freebsd-wireless/2012-November/002539.html
> just wanted to get wi-fi n-mode :) act
1 - 100 of 198 matches
Mail list logo
