Re: Delay in 14.0-RELEASE cycle and blocking items
Am 2023-05-03 10:59, schrieb Mina Galić: Is there a chance to get pkgbase into 14.0? If not it will take another X years to have it in 15.0... PkgBase *is* in 14, like it is in 13. The question is just if re@ has the resources (people, time, Hardware) to provide a Repository. Mina Galić Fingers crossed that the resources are available!
Re: Delay in 14.0-RELEASE cycle and blocking items
Am 2023-05-01 20:14, schrieb Glen Barber: According to the 14.0-RELEASE schedule, the code slush in main and the freeze to the KBI for 14.0 was scheduled for April 25, 2023. As some of you may have noticed, that did not happen. First, and most importantly for 14.0, is the status of the OpenSSL update to version 3. This in itself is reason to delay the schedule until some tangible progress has been made. Yes, some have expressed interest in helping in this area, however at this moment, this is the key blocker. Second is the status of the branch and how it pertains to the recent upstream merge from OpenZFS. Although block_cloning is disabled by default, there have been other regressions discovered (and fixed), but as a whole, I do not feel that we have a solid understanding of the regressions about which we do not know. There is no feasible way we are going to make the branch point of stable/14 in time, with that scheduled for May 12, 2023 with the above points. That said, this is not an all-inclusive list, but the more major items on our radar at the moment. A more up-to-date schedule for the 14.0 release will be published in the near future, though nothing is yet set in stone. Thank you for your patience, and for any help in getting us through these outstanding items. Glen On behalf of: re@ Is there a chance to get pkgbase into 14.0? If not it will take another X years to have it in 15.0...
Re: Pkg repository is broken...
On Wed, Mar 04, 2020 at 03:16:14PM +1100, Greg 'groggy' Lehey wrote: > On Monday, 2 March 2020 at 17:58:01 +, marco wrote: > > On Sun, Mar 01, 2020 at 04:50:59PM -0500, you (Brennan Vincent) sent the > > following to [freebsd-current] : > >> Apparently something has its ABI erroneously listed as FreeBSD:13.0:amd64 > >> instead of FreeBSD:13:amd64. > >> > >> ``` > >> $ sudo pkg update -f > >> Updating FreeBSD repository catalogue... > >> Fetching meta.conf: 100%163 B 0.2kB/s00:01 > >> Fetching packagesite.txz: 100%6 MiB 6.4MB/s00:01 > >> Processing entries: 72% > >> pkg: wrong architecture: FreeBSD:13.0:amd64 instead of FreeBSD:13:amd64 > >> pkg: repository FreeBSD contains packages with wrong ABI: > >> FreeBSD:13.0:amd64 > >> Processing entries: 100% > >> Unable to update repository FreeBSD > >> Error updating repositories! > > > > Ran into this very same problem today too. > > Just learned on #freebsd that the repos are temporarily borked and > > people are working hard to fix it. > > Any workarounds in the meantime? This must affect a lot of people, > including those who use 12-: > > pkg: wrong architecture: FreeBSD:12.0:amd64 instead of FreeBSD:12:amd64 > pkg: repository FreeBSD contains packages with wrong ABI: FreeBSD:12.0:amd64 Still broken for me on 12.1. ___ freebsd-current@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"
Re: Lenovo X1 Carbon or T460s
On Mon, Nov 14, 2016 at 11:25:24AM -0800, K. Macy wrote: > On Monday, November 14, 2016, Lars Engels wrote: > > > On Sun, Nov 13, 2016 at 01:56:45PM -0800, K. Macy wrote: > > > On Saturday, November 12, 2016, Mark Heily > > wrote: > > > > > > > On Fri, Nov 11, 2016 at 11:41 PM, Kevin Oberman > > > > > > wrote: > > > > > > > > > > > > > > In regard to video, have you installed and are you using vaapi? > > > > > > > > > > > > > vaapi appears to be preinstalled, however when I run "vainfo" it is > > unable > > > > to find a driver. > > > > > > > > The underlying problem is that Intel Skylake graphics are not fully > > > > supported under FreeBSD yet; see https://wiki.freebsd.org/Graphics > > > > > > > > > Actually don't. > > > > > > Refer to the -X11 and -current archives. I've already discussed this > > > multiple times. UXA and full offload work fine. The problem is trueos is > > > using the modesetting driver and Glamor acceleration doesn't fully work > > yet > > > without artifacts. This is more an issue of ease of development for the > > > configuration tool on trueos than fundamental limitation. > > > > > > The code currently in tree doesn't support anything newer than Haswell. > > > Support for Broadwell, Skylake, and Kaby Lake is out of tree. However, > > that > > > is what trueos is using. > > > > When can we expect your graphics work in HEAD? :) > > > > The core kernel changes will probably happen by the end of the year now > that a number of committers have Skylake and Kaby Lake laptops. Once those > are done the drivers themselves can be made in to ports. Adrian, Alexander > Motin, and Conrad have all expressed an interest in moving this along. > Sounds very good, thank you! pgpejUillQYmu.pgp Description: PGP signature
Re: Lenovo X1 Carbon or T460s
On Sun, Nov 13, 2016 at 01:56:45PM -0800, K. Macy wrote: > On Saturday, November 12, 2016, Mark Heily wrote: > > > On Fri, Nov 11, 2016 at 11:41 PM, Kevin Oberman > > wrote: > > > > > > > > In regard to video, have you installed and are you using vaapi? > > > > > > > vaapi appears to be preinstalled, however when I run "vainfo" it is unable > > to find a driver. > > > > The underlying problem is that Intel Skylake graphics are not fully > > supported under FreeBSD yet; see https://wiki.freebsd.org/Graphics > > > Actually don't. > > Refer to the -X11 and -current archives. I've already discussed this > multiple times. UXA and full offload work fine. The problem is trueos is > using the modesetting driver and Glamor acceleration doesn't fully work yet > without artifacts. This is more an issue of ease of development for the > configuration tool on trueos than fundamental limitation. > > The code currently in tree doesn't support anything newer than Haswell. > Support for Broadwell, Skylake, and Kaby Lake is out of tree. However, that > is what trueos is using. When can we expect your graphics work in HEAD? :) pgpfseSYcc8Dk.pgp Description: PGP signature
Re: FreeBSD 11.0-BETA4 Now Available
On Mon, Aug 08, 2016 at 10:15:07AM -0700, Devin Teske wrote: > > > On Aug 8, 2016, at 8:02 AM, Lars Engels wrote: > > > > On Mon, Aug 08, 2016 at 02:44:05PM +, Glen Barber wrote: > >> On Mon, Aug 08, 2016 at 10:48:30AM +0200, Lars Engels wrote: > >>> On Sat, Aug 06, 2016 at 09:05:26PM +, Glen Barber wrote: > >>>> -BEGIN PGP SIGNED MESSAGE- > >>> > >>>> o The new system hardening options have been fixed to avoid overwriting > >>>> other options selected during install time. > >>> > >>> Can those options also get added to "bsdconfig"? > >> > >> You would have to ask the bsdconfig maintainer(s). > >> > > > > Cc'ing dteske. > > > > What aspects of bsdconfig need updating? bsdinstall has a new "hardening" module. AFAIK bsdinstall and bsdconfig share a lot of code, so bsdconfig should probably also offer the "hardening" module. pgpG3LDevrZoQ.pgp Description: PGP signature
Re: FreeBSD 11.0-BETA4 Now Available
On Mon, Aug 08, 2016 at 02:44:05PM +, Glen Barber wrote: > On Mon, Aug 08, 2016 at 10:48:30AM +0200, Lars Engels wrote: > > On Sat, Aug 06, 2016 at 09:05:26PM +, Glen Barber wrote: > > > -BEGIN PGP SIGNED MESSAGE- > > > > > o The new system hardening options have been fixed to avoid overwriting > > > other options selected during install time. > > > > Can those options also get added to "bsdconfig"? > > You would have to ask the bsdconfig maintainer(s). > Cc'ing dteske. pgphzR28U4r9O.pgp Description: PGP signature
Re: FreeBSD 11.0-BETA4 Now Available
On Sat, Aug 06, 2016 at 09:05:26PM +, Glen Barber wrote: > -BEGIN PGP SIGNED MESSAGE- > o The new system hardening options have been fixed to avoid overwriting > other options selected during install time. Can those options also get added to "bsdconfig"? pgpDIfHtky6GL.pgp Description: PGP signature
Re: FreeBSD-11.0-BETA1-amd64-disc1.iso is too big for my 700MB CD-r
On Tue, Jul 12, 2016 at 12:09:09PM +0200, Ronald Klop wrote: > On Mon, 11 Jul 2016 23:24:10 +0200, Conrad Meyer wrote: > > > DVD-R dates to 1997; cheap USB flash devices are now pervasive. Maybe > > it's time to move on from CD. > > Becoming anecdotal now, but my fairly old computer has a (BIOS) bug which > brakes booting from USB devices. It hangs when it boots with a USB stick > in it. > With the bootonly ISO I upgraded it from 9.3-PRERELEASE to 11-BETA1. By > just copying /boot/kernel from the CD to the harddisk. :-) I know I have > to do more for a proper upgrade, but the ZFS version on disk was to new > for the 9.3 kernel, by a human mistake. LOL I've never tried it, but Plop Boot Manager allows to boot from USB on PCs without BIOS USB support (or in your case, where that support is broken): https://www.plop.at/en/bootmanagers.html pgpCK2TS6HekT.pgp Description: PGP signature
Re: no smtp service after upgrade
On Wed, Apr 27, 2016 at 05:08:47PM +0300, Chagin Dmitry wrote:
> On Wed, Apr 27, 2016 at 04:34:29PM +0300, Boris Samorodov wrote:
> > Hi All,
> >
> > There is no smtp service after recent update:
> > -
> > % sockstat -4l
> > USER COMMANDPID FD PROTO LOCAL ADDRESS FOREIGN
> > ADDRESS
> > root sshd 879 4 tcp4 *:22 *:*
> > root syslogd663 7 udp4 *:514 *:*
> > -
> >
> > I use (almost) default mail configuration.
> > -
> > % grep mail /etc/rc.conf{,.local}
> > %
> > -
> >
> > I've notice a huge etc updates at update. Seems they may be related.
> >
> the same here, chmod +x /etc/rc.d/sendmail
I wonder why the sendmail rc script gets installed with mode 444.
When I run "make install" in src/etc/rc.d all other scripts get
installed with mode 555. The relevant part of the Makefile is
.if ${MK_SENDMAIL} != "no"
FILESGROUPS+= SMRCD
SMRCD= sendmail
.endif
SMRCDDIR= /etc/rc.d
SMRCDDIRMODE= ${BINMODE}
SMRCDPACKAGE= sendmail
${BINMODE} is used for all scripts, so I can't see why it is different
for sendmail.
pgpFTvG6t5D19.pgp
Description: PGP signature
Re: New rc.d scripts on current
On Mon, Apr 25, 2016 at 09:31:32AM -0300, Otacílio wrote:
> Em 25/04/2016 06:50, Maurizio Vairani escreveu:
> > 2016-04-24 21:26 GMT+02:00 Lars Engels :
> >
> >> On Sun, Apr 24, 2016 at 08:33:11AM -0700, Manfred Antar wrote:
> >>> Updated /etc yesterday via mergemaster.
> >>> Now I’m getting this on reboot. Everything seems to be working alright.
> >>>
> >>> eval: disk: not found
> >>> eval: disk: not found
> >>> eval: ${GELI ...}: Bad substitutio
> >>> FreeBSD/amd64 (pozo.com) (ttyu0)
> >>>
> >>> login:
> >>>
> >>> Not sure if it is error or new feature.
> >>>
> >>> Manfred
> >> It was my fault. the geli2 rc script had the description text in the
> >> "name" variable.
> >>
> > I am receiving this message too:
> >
> > /etc/rc.d/ccd: descConcatenated disks setup:not found
> >
> > Regards,
> > Maurizio
> > ___
> > freebsd-current@freebsd.org mailing list
> > https://lists.freebsd.org/mailman/listinfo/freebsd-current
> > To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"
> I'm receiving
>
> eval: disk: not found
> eval: disk: not found
>
> on beaglebone black also. r298522
The fix was r298550
But you can just rename the second "name" variable definition with
"desc".
pgpJE85MpMCbt.pgp
Description: PGP signature
Re: New rc.d scripts on current
On Mon, Apr 25, 2016 at 11:50:53AM +0200, Maurizio Vairani wrote:
> 2016-04-24 21:26 GMT+02:00 Lars Engels :
>
> > On Sun, Apr 24, 2016 at 08:33:11AM -0700, Manfred Antar wrote:
> > > Updated /etc yesterday via mergemaster.
> > > Now I’m getting this on reboot. Everything seems to be working alright.
> > >
> > > eval: disk: not found
> > > eval: disk: not found
> > > eval: ${GELI ...}: Bad substitutio
> > > FreeBSD/amd64 (pozo.com) (ttyu0)
> > >
> > > login:
> > >
> > > Not sure if it is error or new feature.
> > >
> > > Manfred
> >
> > It was my fault. the geli2 rc script had the description text in the
> > "name" variable.
> >
>
> I am receiving this message too:
>
> /etc/rc.d/ccd: descConcatenated disks setup:not found
That was also fixed yesterday.
pgptcEKpGwVF_.pgp
Description: PGP signature
Re: New rc.d scripts on current
On Sun, Apr 24, 2016 at 08:33:11AM -0700, Manfred Antar wrote:
> Updated /etc yesterday via mergemaster.
> Now I’m getting this on reboot. Everything seems to be working alright.
>
> eval: disk: not found
> eval: disk: not found
> eval: ${GELI ...}: Bad substitutio
> FreeBSD/amd64 (pozo.com) (ttyu0)
>
> login:
>
> Not sure if it is error or new feature.
>
> Manfred
It was my fault. the geli2 rc script had the description text in the
"name" variable.
pgpnoNGomKfo8.pgp
Description: PGP signature
Re: [CFT] packaging the base system with pkg(8)
On Tue, Apr 19, 2016 at 12:18:00PM +0300, dan_partelly wrote: > > be as terse as possible. You guys seen the "Add remove programs" > in Windows control panel ? Thats sane. Even now the default output > of pkg borders insane, when you have many packages installed. 99% of my > time > I dont really care about lib-rtyum546.78.9. I care only less than 1% of my > time when something > goes wrong. Don't use "pkg info" then. Use "pkg leaf": % pkg info | wc -l 249 % pkg leaf | wc -l 25 "leaf" is an alias for: pkg 'query -e "%a == 0" "%n-%v"' And to everyone complaining about the number of packages: How many of you have actually used the packaged base? pgpBUdMf8hTH6.pgp Description: PGP signature
Re: D3702: add support for Bluetooth Magic Mouse
On Mon, Apr 04, 2016 at 10:22:30PM -0600, Warren Block wrote: > Is anyone working on Bluetooth stuff? https://reviews.freebsd.org/D3702 > adds support for the Apple Magic Mouse, and has been tested and reported > working: > https://lists.freebsd.org/pipermail/freebsd-bluetooth/2016-April/002053.html > > Could someone please review and commit this? Thanks! Sobomax@ (cc'ed) is the most likely person to review this. pgpjtTcxHUOeI.pgp Description: PGP signature
Re: question on support processor Intel Atom Z3735F
On Thu, Mar 24, 2016 at 10:06:05PM +0300, Владимир wrote: > Hello, please tell me whether the FreeBSD operating system Intel Atom > Z3735F? Which distribution I need to download? The CPU supports amd64 but AFAIK the Baytrail architecture only supports a 32-bit UEFI. So you need to create your own boot medium. pgpq8VrBBHKLV.pgp Description: PGP signature
Re: nic ral0 not created
On Mon, Mar 21, 2016 at 12:12:40AM -0300, Nilton Jose Rizzo wrote: > > > > Hi all, > > I'm download a least memstick image (20160308) and > my notebook create a ral0 interface. > > look at this photo > http://ibin.co/2XJ6CoBE6t2a > > The sistem reconise as a RT2790 Ralink but when I run > the ifconfig command it's not showed. > >Have someone any idea? Wireless devices no longer show up in ifconfig's output. You should see the device when you run sysctl net.wlan.devices Then you can create a wlan0 device: ifconfig wlan0 create wlandev ral0 and use the wlan0 device. pgpZLYEObu5xw.pgp Description: PGP signature
Re: Touchscreen support (was Re: new computer, strange usb messages at boot)
On Mon, Feb 22, 2016 at 11:39:12AM -0500, Anthony Jenkins wrote: > > > On 02/22/2016 02:11 AM, Hans Petter Selasky wrote: > > On 02/22/16 03:16, Anthony Jenkins wrote: > >> Yes. I have an eGalax touchscreen and it's doing the same thing. The > >> number of items it's reporting is 256 (according to my preliminary > >> debugging), causing the warning. I think these things are a special > >> subclass of HID for multitouch touchscreens which we don't support > >> (yet). > > > > /usr/ports/multimedia/webcamd will most likely attach if invoked > > manually, to this device and provide an event device for you! > > > > --HPS > > Okay that's /amazing/, and not at all intuitive! I mean I'd expect > multimedia/webcamd to only attach to "video" devices, but lo and behold > I get a /dev/input/event0 device which spits out gibberish when > cat(1)'ed and I touch the screen! I might be about time to re-name webcamd to something else. pgppTw7gHrGpY.pgp Description: PGP signature
Re: libXO-ification - Why - and is it a symptom of deeper issues?
On Wed, Nov 18, 2015 at 04:56:21PM -0500, Ed Maste wrote: > On 18 November 2015 at 15:46, Luigi Rizzo wrote: > > i was going to suggest doing ldd on the binaries or a grep on the > > Makefile but the latter returns a surprisingly low number > > of matches. > > That's because it's usually added via LIBADD=xo. > > My grep turns up these: bin/df, bin/ls, bin/ps, sbin/savecore, > usr.bin/iscsictl, usr.bin/netstat, usr.bin/procstat, usr.bin/w, > usr.bin/wc, usr.bin/xo Thanks! Unfortenately only a part of them mention --libxo in its manpage. pgp7Fi_afO6Vw.pgp Description: PGP signature
Re: libXO-ification - Why - and is it a symptom of deeper issues?
On Sun, Nov 15, 2015 at 01:14:57PM -0500, Allan Jude wrote: > You can setup an atexit() call to call xo_finish automatically when the > program exits. The original changes to uptime had a few other issues, > which I fixed. > Is there a list of tools that can already output via libxo? Neither "uptime -h", nor its manpage or "apropros libxo" doesn't reveal anything. pgp4PSFfghaC1.pgp Description: PGP signature
Re: ramblings.. or not
On Thu, Aug 27, 2015 at 02:31:21PM -0700, Craig Rodrigues wrote: > On Wed, Aug 26, 2015 at 8:44 PM, Julian Elischer wrote: > > > > We should also do a better job of productising and incorporating GSOC > > work.. > > > > > Definitely! It's sad to see people put a lot of working into something via > GSOC, > and then have the work die on the vine once the summer is over. There's a lack of communication. Every year we have GSOC students working on a part of FreeBSD, but after GSOC is over nothing happens. Some code goes into base quietly, some good code may be lurking in an external repository but nobody knows. My proposal is that every student and mentor should write a short summary of the work done and if was already committed to the tree or why it hasn't been committed. pgpVTZCPhkeGd.pgp Description: PGP signature
Re: What to do about RCS/OpenRCS
On Sat, May 09, 2015 at 11:27:57AM -0700, Jos Backus wrote: > Maybe off-topic, but functionality-wise it might make much more sense to > import Fossil. RCS has too many limitations this day and age when better > tools are available. Of course, this would require people to learn > something new, which I know can be a challenge. I really like fossil. But it's still under development, so it would soon be outdated. It's better installed from ports/packages. pgpdrB812fhDT.pgp Description: PGP signature
Re: Call For Testers: Synaptics touchpads
On Fri, Apr 10, 2015 at 07:52:07PM +0200, Jan Kokemüller wrote: > > > But it would be aweseome to have both enabled. Could someone > > investigate? > > I've written a patch for this: > > https://lists.freebsd.org/pipermail/freebsd-x11/2014-November/015673.html > > With this, I can have both > > hw.psm.synaptics_support="1" > hw.psm.trackpoint_support="1" > > in my /boot/loader.conf. I can control trackpoint settings such as speed > or sensitivity while having the touchpad also enabled. > > The patch might need some cleanup to land in the tree, but I've been > happily using this for at least a year now :) Sounds great! I'll test this later. :) Lars pgpH04SlmCrd_.pgp Description: PGP signature
Re: Call For Testers: Synaptics touchpads
On Fri, Apr 10, 2015 at 09:10:14AM -0700, Rui Paulo wrote: > On Friday 10 April 2015 14:22:00 Lars Engels wrote: > > On Thu, Apr 09, 2015 at 05:05:09PM -0700, Rui Paulo wrote: > > > > On Apr 9, 2015, at 14:03, Lars Engels wrote: > > > >> On Thu, Apr 09, 2015 at 01:14:18PM -0700, Rui Paulo wrote: > > > >>> On Thursday 09 April 2015 15:41:59 Lars Engels wrote: > > > >>> But it would be aweseome to have both enabled. Could someone > > > >>> investigate? > > > >> > > > >> I don't know how that can work since every time I run the > > > >> enable_trackpoint() routine on my psm device, it cannot complete the > > > >> initialisation routine. Maybe there's a special command when mixing > > > >> synaptics with trackpoint, but I don't know what it is. > > > > > > > > Maybe the Linux folks found a way? > > > > > > Do you have time to investigate? I'm a bit busy with other stuff. > > > > No, sorry. I don't have the knowledge to investigate. > > OK, but does your trackpoint not work? It works fine in my case, but you > just > lose the sysctl settings to control it. Yes, it does work. Actually I don't need the touchpad at all, so I'm fine having only trackpoint with its sysctls enabled, but other people might use both. pgp_UQuozHcc8.pgp Description: PGP signature
Re: Call For Testers: Synaptics touchpads
On Thu, Apr 09, 2015 at 01:14:18PM -0700, Rui Paulo wrote: > On Thursday 09 April 2015 15:41:59 Lars Engels wrote: > > But it would be aweseome to have both enabled. Could someone > > investigate? > > I don't know how that can work since every time I run the enable_trackpoint() > routine on my psm device, it cannot complete the initialisation routine. > Maybe there's a special command when mixing synaptics with trackpoint, but I > don't know what it is. Maybe the Linux folks found a way? pgp5kpP_3QTzv.pgp Description: PGP signature
Re: Call For Testers: Synaptics touchpads
On Thu, Apr 09, 2015 at 01:14:49PM +0200, David Demelier wrote: > Le 08/04/2015 09:19, Rui Paulo a écrit : > > Hi, > > > > The attached patch adds support for newer touchpad features and implements > > two > > finger scrolling. This is such a common feature these days that I think we > > should enable it by default and disable edge scrolling. I've implemented > > some > > detection code to keep edge scrolling enabled when the touchpad has a > > dedicated area for scrolling. > > Thank you very much, I always wondered why this was not supported in > FreeBSD. I also wonder if it will be tunable with the appropriate > GNOME/KDE (or just the synclient tool) settings to disable this > two-finger scroll at runtime. > > > > > Please test it and report back your experience. To enable synaptics > > support, > > you need: > > > > hw.psm.synaptics_support=1 > > I strongly suggest to enable this by default, it will prevent lot of > users having headaches seeking why their touchpads do not work by > default. We also added sound support by default, why not the touchpad ? :-). While this is generally a good idea it would prevent the use of hw.psm.trackpoint_support=1 But it would be aweseome to have both enabled. Could someone investigate? pgpvW4A6XmKqL.pgp Description: PGP signature
Re: Dual booting FreeBSD and Win95
On Wed, Apr 08, 2015 at 03:30:41PM -0400, Ryan Stone wrote: > No, this isn't a late April Fools joke. :( > > I find myself in a situation where I need to integrate my employer's > manufacturing process with a third-party OEM's process. My employer's > hardware tests are all FreeBSD-based while the OEM is Windows 95 based. I > need to come up with a way to integrate them together. > > We're looking at dual-booting FreeBSD and Win95. We're thinking of booting > into Win95, the OEM can do their thing, switch to booting FreeBSD, run our > tests and produce a .csv file with the results, and then boot back into > Win95 for them to finish up. Ideally we would like to switch the boot > slice without human interaction. > > I've been playing around with trying to set one only slice as active to > make the loader boot it, but it appears that doesn't actually work. > boot0cfg would cover half of the use case (switching from FreeBSD back to > Win95), but I'm not sure how I could do the original switch from Win95 to > FreeBSD. > > We've discussed just switching hard drives, but we really want to shoot for > a 100% automated process. Anybody have any ideas? Maybe you can make use of the GAG boot manager? I don't know if you can make changes what partition gets booted next out of a running OS. http://gag.sourceforge.net pgp1fwj1srlGc.pgp Description: PGP signature
Re: Call For Testers: Synaptics touchpads
On Wed, Apr 08, 2015 at 01:32:06PM -0400, Shawn Webb wrote: > On Wed, 2015-04-08 at 09:19 -0700, Rui Paulo wrote: > > On Wednesday 08 April 2015 09:13:51 Shawn Webb wrote: > > > On Wed, 2015-04-08 at 00:19 -0700, Rui Paulo wrote: > > > > Hi, > > > > > > > > The attached patch adds support for newer touchpad features and > > > > implements > > > > two finger scrolling. This is such a common feature these days that I > > > > think we should enable it by default and disable edge scrolling. I've > > > > implemented some detection code to keep edge scrolling enabled when the > > > > touchpad has a dedicated area for scrolling. > > > > > > > > Please test it and report back your experience. To enable synaptics > > > > support, you need: > > > > > > > > hw.psm.synaptics_support=1 Did you add this to loader.conf? > > It's not working in the slightest to me. Looking at the patch, you > expose additional sysctls. None of those sysctls are visible to me. Is > there something I need to do besides apply the patch and recompile my > kernel? If not, then the patch doesn't work in the slightest. Does "grep -i synaptics /var/run/dmesg.boot" show anything? pgpTFD8vuVLex.pgp Description: PGP signature
Re: Battery life with the latest drm
On Thu, Feb 05, 2015 at 09:22:49PM +0100, Jan Kokemüller wrote: > > On 04.02.2015 21:27, Lars Engels wrote: > > By the way on the X230 (IvyBridge i7) the loader.conf setting > > "drm.i915.enable_rc6=7" makes a huge difference. > > For some other reason I removed it from loader.conf and > > hw.acpi.battery.time showed 160 minutes. After re-adding it battery time > > went up to 230 minutes. > > I've been using the same setting for a while now and can confirm the > increase of battery life. It also makes a huge difference in fan noise > on my T420. > > Can you suspend/resume with rc6 on? I had to patch around a deadlock in > i915_irq.c: https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=183859 > I haven't checked yet if this still occurs after the recent drm import. Yes, I can suspend and resume several times. I haven't seen a broken s/r cycle since the latest drm import. pgp3h18nmOxnP.pgp Description: PGP signature
Battery life with the latest drm
Just a quick report that from my completely unscientific observations it seems that battery life is extended with the latest drm import on my Thinkpad X230. I should probably get some numbers first, but my gut feeling is that it is better. By the way on the X230 (IvyBridge i7) the loader.conf setting "drm.i915.enable_rc6=7" makes a huge difference. For some other reason I removed it from loader.conf and hw.acpi.battery.time showed 160 minutes. After re-adding it battery time went up to 230 minutes. Lars pgp2m6qMcA0XV.pgp Description: PGP signature
Re: HP 2B19WM PCI-E SD Reader
On Wed, Feb 04, 2015 at 12:04:21AM +, Gavin Atkinson wrote: > On Mon, 2 Feb 2015, R0B_ROD wrote: > > Thank you for the time you took to help. > > > > According to: > >http://lists.freebsd.org/pipermail/ \ > >\ freebsd-current/2013-July/042788.html > >\ freebsd-questions/2014-August/259843.html > > > > Is the Realtek RTS5229 PCI-E SD Card Reader > > supported yet??? > > Unfortunately, we don't have a driver for this card reader yet. It is > worth checking to make sure that you do indeed have this drvice though. > Can you give the output of both "pciconf -lv" and "usbconfig list" please? > Wouldn't it be possible to pass the PCI device to a bhyve VM running Linux like Shawn did here with his wireless card? http://0xfeedface.org/2014/12/11/FreeBSD-Intel-wifi-via-bhyve.html And then share the Filesystem with CIFS or NFS... :) pgpmFRefKSzd0.pgp Description: PGP signature
Re: drm2 regression: backlight adjustment on ivybridge no longer works
On Sun, Feb 01, 2015 at 11:23:47AM +0100, Lars Engels wrote: > On 1. Februar 2015 11:20:26 MEZ, Alexandr Krivulya > wrote: > >01.02.2015 12:12, Lars Engels пишет: > >> On Sun, Feb 01, 2015 at 10:41:25AM +0100, Lars Engels wrote: > >>> On Sun, Feb 01, 2015 at 03:35:15AM -0600, Andrew Wilcox wrote: > >>>> Lars Engels sent: 01 February 2015 03:18: > >>>>> With acpi_video I get some interesting sysctl: > >>>>> hw.acpi.video.lcd0.levels: 100 100 0 1 2 3 4 5 6 7 8 9 10 11 12 13 > >14 15 > >>>>> 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 > >38 39 > >>>>> 40 41 42 43 44 45 46 47 48 49 50 51 52 53 54 55 56 57 58 59 60 61 > >62 63 > >>>>> 64 65 66 67 68 69 70 71 72 73 74 75 76 77 78 79 80 81 82 83 84 85 > >86 87 > >>>>> 88 89 90 91 92 93 94 95 96 97 98 99 100 > >>>>> > >>>>> I guess it should not be 100 100 0 ... 100? > >>>> Actually, the "standard" internal ACPI brightness level struct > >(BRTN in the DSDT) is laid out as: > >>>> > >>>> * "Full power" value (one byte, the value at which the brightness > >should be set on AC by default) > >>>> * "Economy" value (one byte, the value at which the brightness > >should be set on battery by default) > >>>> * Actual values (N bytes, up to Max but frequently not) > >>>> > >>>> So, no, that value indeed sounds correct. On my laptop the value > >is: > >>>> 80 47 0 7 13 20 27 33 40 47 53 60 67 73 80 87 93 100 > >>> Thank you for the explanation. > >>> FWIW, here is the full output from sysctl hw.acpi.video.lcd0: > >>> > >>> hw.acpi.video.lcd0.active: 1 > >>> hw.acpi.video.lcd0.brightness: 11 > >>> hw.acpi.video.lcd0.fullpower: 100 > >>> hw.acpi.video.lcd0.economy: 100 > >>> hw.acpi.video.lcd0.levels: 100 100 0 1 2 3 4 5 6 7 8 9 10 11 12 13 > >14 15 > >>> 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38 > >39 > >>> 40 41 42 43 44 45 46 47 48 49 50 51 52 53 54 55 56 57 58 59 60 61 62 > >63 > >>> 64 65 66 67 68 69 70 71 72 73 74 75 76 77 78 79 80 81 82 83 84 85 86 > >87 > >>> 88 89 90 91 92 93 94 95 96 97 98 99 100 > >>> hw.acpi.video.crt0.active: 1 > >>> hw.acpi.video.ext0.active: 1 > >>> hw.acpi.video.ext1.active: 1 > >>> hw.acpi.video.ext2.active: 1 > >>> hw.acpi.video.ext3.active: 1 > >>> hw.acpi.video.ext4.active: 1 > >>> hw.acpi.video.ext5.active: 1 > >>> > >>>> What revision of -CURRENT are you running? What is the outcome of > >>>> trying the patch posted Saturday morning (UTC) from Elizabeth Myers > >>>> (message ID <54cc5311.9070...@interlinked.me>)? > >>>> > >>> I'm currently running r277858 and haven't tried the patch, yet. But > >will > >>> do now and report back. > >>> > >> So now I have a new sysctl hw.dri.0.i915_backlight. But no matter > >what > >> value I pass to it, the brightness doesn't change. > >> > >> It's a Ivy Brigde notebook where drm shows some errors in dmesg. > >Please > >> see: http://pastie.org/9877917 > >> > >> > > > >Please try to boot with acpi_ibm and without acpi_video. This way all > >works for me. > > That‘s already what I do. Also tried it with acpi_video without luck. For the records: With r278102 brightness controls are working again. Thanks all for helping. pgpRxf8xrTJKt.pgp Description: PGP signature
Re: drm2 regression: backlight adjustment on ivybridge no longer works
On 1. Februar 2015 11:20:26 MEZ, Alexandr Krivulya wrote: >01.02.2015 12:12, Lars Engels пишет: >> On Sun, Feb 01, 2015 at 10:41:25AM +0100, Lars Engels wrote: >>> On Sun, Feb 01, 2015 at 03:35:15AM -0600, Andrew Wilcox wrote: >>>> Lars Engels sent: 01 February 2015 03:18: >>>>> With acpi_video I get some interesting sysctl: >>>>> hw.acpi.video.lcd0.levels: 100 100 0 1 2 3 4 5 6 7 8 9 10 11 12 13 >14 15 >>>>> 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 >38 39 >>>>> 40 41 42 43 44 45 46 47 48 49 50 51 52 53 54 55 56 57 58 59 60 61 >62 63 >>>>> 64 65 66 67 68 69 70 71 72 73 74 75 76 77 78 79 80 81 82 83 84 85 >86 87 >>>>> 88 89 90 91 92 93 94 95 96 97 98 99 100 >>>>> >>>>> I guess it should not be 100 100 0 ... 100? >>>> Actually, the "standard" internal ACPI brightness level struct >(BRTN in the DSDT) is laid out as: >>>> >>>> * "Full power" value (one byte, the value at which the brightness >should be set on AC by default) >>>> * "Economy" value (one byte, the value at which the brightness >should be set on battery by default) >>>> * Actual values (N bytes, up to Max but frequently not) >>>> >>>> So, no, that value indeed sounds correct. On my laptop the value >is: >>>> 80 47 0 7 13 20 27 33 40 47 53 60 67 73 80 87 93 100 >>> Thank you for the explanation. >>> FWIW, here is the full output from sysctl hw.acpi.video.lcd0: >>> >>> hw.acpi.video.lcd0.active: 1 >>> hw.acpi.video.lcd0.brightness: 11 >>> hw.acpi.video.lcd0.fullpower: 100 >>> hw.acpi.video.lcd0.economy: 100 >>> hw.acpi.video.lcd0.levels: 100 100 0 1 2 3 4 5 6 7 8 9 10 11 12 13 >14 15 >>> 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38 >39 >>> 40 41 42 43 44 45 46 47 48 49 50 51 52 53 54 55 56 57 58 59 60 61 62 >63 >>> 64 65 66 67 68 69 70 71 72 73 74 75 76 77 78 79 80 81 82 83 84 85 86 >87 >>> 88 89 90 91 92 93 94 95 96 97 98 99 100 >>> hw.acpi.video.crt0.active: 1 >>> hw.acpi.video.ext0.active: 1 >>> hw.acpi.video.ext1.active: 1 >>> hw.acpi.video.ext2.active: 1 >>> hw.acpi.video.ext3.active: 1 >>> hw.acpi.video.ext4.active: 1 >>> hw.acpi.video.ext5.active: 1 >>> >>>> What revision of -CURRENT are you running? What is the outcome of >>>> trying the patch posted Saturday morning (UTC) from Elizabeth Myers >>>> (message ID <54cc5311.9070...@interlinked.me>)? >>>> >>> I'm currently running r277858 and haven't tried the patch, yet. But >will >>> do now and report back. >>> >> So now I have a new sysctl hw.dri.0.i915_backlight. But no matter >what >> value I pass to it, the brightness doesn't change. >> >> It's a Ivy Brigde notebook where drm shows some errors in dmesg. >Please >> see: http://pastie.org/9877917 >> >> > >Please try to boot with acpi_ibm and without acpi_video. This way all >works for me. That‘s already what I do. Also tried it with acpi_video without luck. ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"
Re: drm2 regression: backlight adjustment on ivybridge no longer works
On Sun, Feb 01, 2015 at 10:41:25AM +0100, Lars Engels wrote: > On Sun, Feb 01, 2015 at 03:35:15AM -0600, Andrew Wilcox wrote: > > Lars Engels sent: 01 February 2015 03:18: > > > With acpi_video I get some interesting sysctl: > > > hw.acpi.video.lcd0.levels: 100 100 0 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 > > > 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38 39 > > > 40 41 42 43 44 45 46 47 48 49 50 51 52 53 54 55 56 57 58 59 60 61 62 63 > > > 64 65 66 67 68 69 70 71 72 73 74 75 76 77 78 79 80 81 82 83 84 85 86 87 > > > 88 89 90 91 92 93 94 95 96 97 98 99 100 > > > > > > I guess it should not be 100 100 0 ... 100? > > > > Actually, the "standard" internal ACPI brightness level struct (BRTN in the > > DSDT) is laid out as: > > > > * "Full power" value (one byte, the value at which the brightness should be > > set on AC by default) > > * "Economy" value (one byte, the value at which the brightness should be > > set on battery by default) > > * Actual values (N bytes, up to Max but frequently not) > > > > So, no, that value indeed sounds correct. On my laptop the value is: > > 80 47 0 7 13 20 27 33 40 47 53 60 67 73 80 87 93 100 > > Thank you for the explanation. > FWIW, here is the full output from sysctl hw.acpi.video.lcd0: > > hw.acpi.video.lcd0.active: 1 > hw.acpi.video.lcd0.brightness: 11 > hw.acpi.video.lcd0.fullpower: 100 > hw.acpi.video.lcd0.economy: 100 > hw.acpi.video.lcd0.levels: 100 100 0 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 > 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38 39 > 40 41 42 43 44 45 46 47 48 49 50 51 52 53 54 55 56 57 58 59 60 61 62 63 > 64 65 66 67 68 69 70 71 72 73 74 75 76 77 78 79 80 81 82 83 84 85 86 87 > 88 89 90 91 92 93 94 95 96 97 98 99 100 > hw.acpi.video.crt0.active: 1 > hw.acpi.video.ext0.active: 1 > hw.acpi.video.ext1.active: 1 > hw.acpi.video.ext2.active: 1 > hw.acpi.video.ext3.active: 1 > hw.acpi.video.ext4.active: 1 > hw.acpi.video.ext5.active: 1 > > > > > What revision of -CURRENT are you running? What is the outcome of > > trying the patch posted Saturday morning (UTC) from Elizabeth Myers > > (message ID <54cc5311.9070...@interlinked.me>)? > > > > I'm currently running r277858 and haven't tried the patch, yet. But will > do now and report back. > So now I have a new sysctl hw.dri.0.i915_backlight. But no matter what value I pass to it, the brightness doesn't change. It's a Ivy Brigde notebook where drm shows some errors in dmesg. Please see: http://pastie.org/9877917 pgpfUaEvmaEn_.pgp Description: PGP signature
Re: drm2 regression: backlight adjustment on ivybridge no longer works
On Sun, Feb 01, 2015 at 03:35:15AM -0600, Andrew Wilcox wrote: > Lars Engels sent: 01 February 2015 03:18: > > With acpi_video I get some interesting sysctl: > > hw.acpi.video.lcd0.levels: 100 100 0 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 > > 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38 39 > > 40 41 42 43 44 45 46 47 48 49 50 51 52 53 54 55 56 57 58 59 60 61 62 63 > > 64 65 66 67 68 69 70 71 72 73 74 75 76 77 78 79 80 81 82 83 84 85 86 87 > > 88 89 90 91 92 93 94 95 96 97 98 99 100 > > > > I guess it should not be 100 100 0 ... 100? > > Actually, the "standard" internal ACPI brightness level struct (BRTN in the > DSDT) is laid out as: > > * "Full power" value (one byte, the value at which the brightness should be > set on AC by default) > * "Economy" value (one byte, the value at which the brightness should be set > on battery by default) > * Actual values (N bytes, up to Max but frequently not) > > So, no, that value indeed sounds correct. On my laptop the value is: > 80 47 0 7 13 20 27 33 40 47 53 60 67 73 80 87 93 100 Thank you for the explanation. FWIW, here is the full output from sysctl hw.acpi.video.lcd0: hw.acpi.video.lcd0.active: 1 hw.acpi.video.lcd0.brightness: 11 hw.acpi.video.lcd0.fullpower: 100 hw.acpi.video.lcd0.economy: 100 hw.acpi.video.lcd0.levels: 100 100 0 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38 39 40 41 42 43 44 45 46 47 48 49 50 51 52 53 54 55 56 57 58 59 60 61 62 63 64 65 66 67 68 69 70 71 72 73 74 75 76 77 78 79 80 81 82 83 84 85 86 87 88 89 90 91 92 93 94 95 96 97 98 99 100 hw.acpi.video.crt0.active: 1 hw.acpi.video.ext0.active: 1 hw.acpi.video.ext1.active: 1 hw.acpi.video.ext2.active: 1 hw.acpi.video.ext3.active: 1 hw.acpi.video.ext4.active: 1 hw.acpi.video.ext5.active: 1 > > What revision of -CURRENT are you running? What is the outcome of > trying the patch posted Saturday morning (UTC) from Elizabeth Myers > (message ID <54cc5311.9070...@interlinked.me>)? > I'm currently running r277858 and haven't tried the patch, yet. But will do now and report back. pgpb9IVfFB_TI.pgp Description: PGP signature
Re: drm2 regression: backlight adjustment on ivybridge no longer works
On Sat, Jan 31, 2015 at 07:11:23AM +, Miguel Clara wrote: > On the laptop I'm running current, if relevant > > Loading acpi_video doesn't do much I don't see any sysctl related to > "lcd0" or "birightness", this is one of those computers with "hybrid" > graphics, intel + ATI card, so not sure if that's somewhat related. > > > Anyway, I've just tested the drm patches (both) and intelbacklight ( > https://github.com/grembo/intel_backlight_fbsd) compiles, installs and runs > fine! > > So thanks both for the patches. On my X230 I also lost the ability to control brightness with Fn+F8 / Fn+F9. With acpi_video I get some interesting sysctl: hw.acpi.video.lcd0.levels: 100 100 0 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38 39 40 41 42 43 44 45 46 47 48 49 50 51 52 53 54 55 56 57 58 59 60 61 62 63 64 65 66 67 68 69 70 71 72 73 74 75 76 77 78 79 80 81 82 83 84 85 86 87 88 89 90 91 92 93 94 95 96 97 98 99 100 I guess it should not be 100 100 0 ... 100? Changing brightness with hw.acpi.video.lcd0.brightness doesn't work. pgpimanfO7tsz.pgp Description: PGP signature
Re: Suspend/resume with i915.
On Fri, Jan 30, 2015 at 11:12:48PM +0100, Edward Tomasz Napierała wrote: > On 0123T1040, Konstantin Belousov wrote: > > On Thu, Jan 22, 2015 at 12:02:01PM +0100, Edward Tomasz Napiera??a wrote: > > > I'm trying to fix resume on my T61, broken by some change several > > > months ago; according to pciconf it's 'Mobile GM965/GL960 Integrated > > > Graphics Controller (primary)'. It's running current CURRENT and > > > up to date packages. > > > > > > Suspend and resume makes Xorg do something weird - there is screen > > > corruption, or rather window corruption. The GNOME 3 desktop looks > > > pretty normal, except that gnome-terminal (launched before suspend) > > > window looks as if the buffer layout changed underneath it; for example, > > > instead of one flashing cursor there are several, horizontally, across > > > the window. New windows are simply black. No segv. > > > > > > Setting kern.vt.suspendswitch=0 makes the behaviour disappear, replaced > > > by segmentation faults of gnome-shell. With stock gdb it looks like this: > > > > At least one big known issue with suspend is that userspace activity > > is not stopped, which makes the driver suspend code operating on the > > non-steady state of devices. > > > > I committed the facility to stop userspace before suspend, and avg promised > > to integrate this into suspend path, but he did not. You might try to > > search mailing lists for reference to his earlier patch. > > Unfortunately stuff was committed before I could test it. Fortunately, > it's all fixed now, and works perfectly, on 11-CURRENT. Thanks! :-) I can add that suspend/resume now works reliable again on my X230. pgpw1QMIBPQqG.pgp Description: PGP signature
Re: HOWTO articles for migrating from Linux to FreeBSD, especially for pkg?
On Tue, Oct 21, 2014 at 02:34:13PM -0400, Mason Loring Bliss wrote: > On Tue, Oct 21, 2014 at 09:14:07AM +0100, David Chisnall wrote: > > > I agree that this would be useful, but it requires someone familiar with > > both systems to write. > > Doing this stuff professionally, I could probably come up with equivalences > for a number of Unices. What would be a reasonable path to getting write > privs on the wiki? > Thanks for volunteering! :) Please register with your realname and I can give you the needed rights. I just created a first draft comparing pkg, ports and apt / dpkg: https://wiki.freebsd.org/PackageManagerRosettaStone Feel free to edit and add things as needed. pgpTxArBNVmpM.pgp Description: PGP signature
Re: Voxer using FreeBSD, BSDNow.tv interview
On Mon, Oct 20, 2014 at 07:18:45PM -0400, Philip M. Gollucci wrote: > Not true, you can roll your own omnibus chef builds with this fixed. Can we get this off advocacy@ please? pgp6sj87TQSAd.pgp Description: PGP signature
Re: FreeBSD laptop compatibility list web page?
On Thu, Oct 02, 2014 at 05:26:06PM +0800, Erich Dollansky wrote: > Hi, > > On Thu, 2 Oct 2014 01:48:39 -0700 > Craig Rodrigues wrote: > > > Hi, > > > > I e-mailed Lukas Ertl about > > I think that you to the wrong URL. The university of vienna is here: > > http://www.univie.ac.at > The Laptop Compability list was first created by Lukas and hosts at the University of Vienna. When it wasn't maintained any longer some people of bsdgroup.de were allowed to host and maintain the page on their domain. Unfortunately, bsdgroup.de isn't active for years, so eventually the Laptop Compability List disappeared. Given that it is outdated for a long time, we should probably let it rest in peace and use https://wiki.freebsd.org/Laptops as a new reference. IIRC the old list was flooded by spammers, so at least that problem is solved as the FreeBSD Wiki is only for registered people who have been nodded through by FreeBSD developers. pgpQK_d1p1Llm.pgp Description: PGP signature
Re: WiFi 802.11/ac PCIe supported adaptor
On Sat, Sep 27, 2014 at 02:38:30PM +0200, O. Hartmann wrote: > > I'm looking for a replacemnt for my 802.11g WiFi PCIe adaptor card and want > to replace it > with an 802.11ac adaptor. > > Since I made very bad experiences with CURRENT and support of modest modern > hardware > (Haswell CPU/Intel 7260 DualBand WiFi NIC), I'd like to ask here first. > > I found this PCIe adaptor card attractive: > > GigaByte Gigabyte GC-WB867D-I > > I can not find ad hoc the WLAN chip used on that specific card, but maybe > someone has > experiences with that litte board. FreeBSD doensn't support 802.11ac, yet. pgpUz4vndmrSY.pgp Description: PGP signature
Re: [HEADSUP] pkg(8) is now the only package management tool
On Wed, Sep 03, 2014 at 05:17:48PM +0200, Michelle Sullivan wrote: > Mathieu Arnold wrote: > > +--On 3 septembre 2014 16:36:29 +0200 Michelle Sullivan > > wrote: > > | Mathieu Arnold wrote: > > |> I still don't see what you have to say about what EOL mean, it's *End Of > > |> Life* meaning after, it is dead, and won't exist any more. > > |> > > |> > > | Ahh so all those Windows XP servers are dead and don't work anymore... > > > > Not at all, but you don't update them any more. > > > > > Actually you do, but it does nothing... just like freebsd-update on any > EOL release... > > Microsoft didn't release a patch that would change the base system so > you can no longer install any software... They just stopped providing > updates, then later stopped providing security updates. Same for FreeBSD and pkg_*. Stay with status quo, use pkg_* with the last tagged version of the ports tree that works with pkg_* or switch to pkg and be happy like the rest of us. pgpMARKbSgqVb.pgp Description: PGP signature
Re: [CFT] Installer Enhancement -- dpv
On Tue, Sep 02, 2014 at 12:18:15PM -0700, dte...@freebsd.org wrote: > > > > -Original Message- > > From: Garrett Cooper [mailto:yaneurab...@gmail.com] > > Sent: Tuesday, September 2, 2014 12:17 PM > > To: dte...@freebsd.org > > Cc: freebsd-current; Julian Elischer; Nathan Whitehorn > > Subject: Re: [CFT] Installer Enhancement -- dpv > > > > On Tue, Sep 2, 2014 at 12:11 PM, wrote: > > > Hi all, > > > > > > I've completed a significant enhancement to bsdinstall's distextract. > > > > Hi Devin, > > Can you please post this patch up on reviews.freebsd.org? > > Oooo, yes... the phabricator stuff. I was learning about that from > sbruno at August's BAFUG meeting. > > Can you e-mail me on the side and walk a phabricator new-comer > through the process of getting an account and slurping this in? Intro is here: https://wiki.freebsd.org/CodeReview pgpPYtMYFJ1gs.pgp Description: PGP signature
Re: android bsd connectivity tools etc ?
On Thu, Aug 14, 2014 at 08:29:37AM +0200, Per olof Ljungmark wrote: > On 08/14/14 01:47, Julian H. Stacey wrote: > > Hi, > > Any tips for Android / FreeBSD BSD tools for connectivity etc ? > > > > I just got a Samsung Galaxy Note 3, with Android 4.4.2 kernel 3.4.0 > > > > It directs me to > > https://www.android.com/filetransfer/ > > which seems binary for mac > > > > I recall I will need current for IP tethering > > > > http://www.freebsd.org/doc/en_US.ISO8859-1/books/handbook/network-usb-tethering.html > > > > http://www.freebsd.org/doc/en_US.ISO8859-1/books/handbook/network-aggregation.html#networking-lagg-wired-and-wireless > > > > I'll build a current from a 10.0-RELEASE partition, > > but now looking with 9.2-RELEASE I see: > > > > /dev/ > > lrwxr-xr-x 1 root wheel9 Aug 14 00:01 ugen1.5@ -> usb/1.5.0 > > crw--- 1 root operator 0x7a Aug 14 00:00 usb/1.5.0 > > crw--- 1 root operator 0x8f Aug 14 00:00 usb/1.5.1 > > crw--- 1 root operator 0x90 Aug 14 00:00 usb/1.5.2 > > > > devd .conf will need: > >match "vendor""0x04e8"; > >match "product" "0x6860"; > >match "devclass" "0x00"; > >match "devsubclass" "0x00"; > >match "sernum""6758498c"; > >match "release" "0x0400"; > > I've no idea what to do for attach > > > > http://www.freebsd.org/cgi/ports.cgi?query=android&stype=all > > has just > > /usr/ports/devel/android-tools-adb/pkg-descr > > & these for cross compiling later: > > /usr/ports/lang/*gnatdroid*/pkg-descr > > > > I also found > > ports/ > > deskutils/tine20 > > net/crtmpserver > > net/linphone > > https://source.android.com/source/index.html > > > > Any URLs, tips, comments welcome, Thanks > > > > Cheers, > > Julian > > > > I gave up on using mass storage and turned to this instead: > > https://play.google.com/store/apps/details?id=lutey.FTPServer&hl=en > > Works very well. > > For tethering I have no idea, sorry. There's also Airdroid [1]. After installing the App on the phone you can connect to it with your PC's browser, up- and download files, send messages, etc. [1] https://play.google.com/store/apps/details?id=com.sand.airdroid pgpNjlvpZjFYr.pgp Description: PGP signature
Re: Several minor annoyances on Current
On Sat, Jul 26, 2014 at 03:18:27PM +0200, Stefan Esser wrote: > Am 26.07.2014 um 13:24 schrieb Lars Engels: > > On Sat, Jul 26, 2014 at 02:03:09AM -0700, Beeblebrox wrote: > >> @ Ian: I added your code and rebuilt the kernel. > >> /boot/loader.conf also has vfs.nfs.bootp_disable="YES" Previously > >> described problem persists. > >> > >> SEPARATE KBD_KEYMAP ISSUE: The keymap for keyboard fails to be > >> set from rc.conf with keymap="fr.iso.kbd" Boot message shows this > >> but there is no record of the message in log files/dmesg: > >> "Configuring syscons: keymapkbdcontrol: keymap file "fr.iso.kbd" > >> not found: No such file or directory" Keymap gets set when I > >> change rc.conf entry to: > >> keymap="/usr/share/syscons/keymaps/fr.iso.kbd" > > > > Yes, I also stumbled upon this. Usually the following worked: > > > > # kbdcontrol -l german.iso # kbdcontrol -l german.iso.kbd # > > kbdcontrol -l /usr/share/syscons/keymaps/german.iso.kbd > > > > In the last few months on HEAD only the latest invocation works. > > Please retry with kbdcontrol as of SVN revision 269120. > > With this change, "kbdcontrol -l" looks at up to 4 places for > keyboard map definitions: > > 1) Under the path found in the environment variable KEYMAP_PATH > 2) Under the full path name specified as parameter to -l > 3) Under the newcons-specific path (/usr/share/vt/keymaps) (***) > 4) Under the old path used for syscons (/usr/share/syscons/keymaps) > > (***) Only if using newcons as reported by sysctl kern.vty > > For newcons, there was no case 4), it only looked into vt/keymaps. > But many keymaps are identical for syscons and newcons and only a > few have been converted and placed into /usr/share/vt/keymaps. > > Regards, STefan Thanks, that revision works for me. pgpZ8AJdE4jFu.pgp Description: PGP signature
Re: Several minor annoyances on Current
On Sat, Jul 26, 2014 at 02:03:09AM -0700, Beeblebrox wrote: > @ Ian: > I added your code and rebuilt the kernel. > /boot/loader.conf also has vfs.nfs.bootp_disable="YES" > Previously described problem persists. > > SEPARATE KBD_KEYMAP ISSUE: > The keymap for keyboard fails to be set from rc.conf with > keymap="fr.iso.kbd" > Boot message shows this but there is no record of the message in log > files/dmesg: "Configuring syscons: keymapkbdcontrol: keymap file > "fr.iso.kbd" not found: No such file or directory" > Keymap gets set when I change rc.conf entry to: > keymap="/usr/share/syscons/keymaps/fr.iso.kbd" Yes, I also stumbled upon this. Usually the following worked: # kbdcontrol -l german.iso # kbdcontrol -l german.iso.kbd # kbdcontrol -l /usr/share/syscons/keymaps/german.iso.kbd In the last few months on HEAD only the latest invocation works. pgpwzACgGt9XY.pgp Description: PGP signature
Re: [PATCHES] Extend service(8) and rc(8) was: Re: HOWTO articles for migrating from Linux to FreeBSD, especially for pkg?
On Sat, Jul 19, 2014 at 12:56:42PM -0700, Adrian Chadd wrote: > Hi! > > I like it! It's a useful command line API. > > Eventually people will realise there needs to be a more formal method > for describing/controlling the underlying framework, but I leave that > up to bapt to figure out and .. well, push people to do. :) > > Thanks! > > > > -a > [CC trimmed] I added a -s flag to allow the usage of /etc/rc.conf.d/$script for use with puppet, etc. https://phabric.freebsd.org/D451 pgpCJKyU5Wu9p.pgp Description: PGP signature
Re: Future of pf / firewall in FreeBSD ? - does it have one ?
On Sun, Jul 20, 2014 at 12:18:54PM +0100, krad wrote: > all of that is true, but you are missing the point. Having two versions of > pf on the bsd's at the user level, is a bad thing. It confuses people, > which puts them off. Its a classic case of divide an conquer for other > platforms. I really like the idea of the openpf version, that has been > mentioned in this thread. It would be awesome if it ended up as a supported > linux thing as well, so the world could be rid of iptables. However i guess > thats just an unrealistic dream And you don't seem to get the point that _someone_ has to do the work. No one has stepped up so far, so nothing is going to change. pgpUUxw9Z8IbB.pgp Description: PGP signature
[PATCHES] Extend service(8) and rc(8) was: Re: HOWTO articles for migrating from Linux to FreeBSD, especially for pkg?
On Fri, Jul 18, 2014 at 12:10:34PM -0700, Adrian Chadd wrote:
> Hi!
>
>
> On 18 July 2014 07:28, Lars Engels wrote:
> > On Thu, Jul 17, 2014 at 10:21:17PM +0200, Andreas Nilsson wrote:
> >> On Thu, Jul 17, 2014 at 10:15 PM, Navdeep Parhar wrote:
> >>
> >> > On 07/17/14 13:12, Adrian Chadd wrote:
> >> > > On 17 July 2014 13:03, Alberto Mijares wrote:
> >> > >> On Thu, Jul 17, 2014 at 2:58 PM, Adrian Chadd
> >> > wrote:
> >> > >>> Hi!
> >> > >>>
> >> > >>> 3) The binary packages need to work out of the box
> >> > >>> 4) .. which means, when you do things like pkg install apache, it
> >> > >>> can't just be installed and not be enabled, because that's a bit of a
> >> > >>> problem;
> >> > >>
> >> > >>
> >> > >> No. Please NEVER do that! The user must be able to edit the files and
> >> > >> start the service by himself.
> >> > >
> >> > > Cool, so what's the single line command needed to type in to start a
> >> > > given package service?
> >> >
> >> > Aren't sysrc(8) and service(8) for this kind of stuff?
> >> >
> >>
> >> They sure are.
> >>
> >> Well, pkg install $service ; sysrc ${service}_enable="YES" would do.
> >> Although some services have different names than the packge, which is sort
> >> of annoying.
> >
> > I hacked up a solution for service(8):
> >
> > http://bsd-geek.de/FreeBSD/service.sh.enable-disable.patch
> >
> > The patch adds the following directives to service(8):
> >
> > enable: Grabs an rc script's rcvar value and runs "sysrc foo_enable=YES"
> > disable: The opposite of enable
> > rcdelete: Deletes an rc script's rcvar value from /etc/rc.conf using
> > "sysrc -x foo_enable"
> >
> > The nice thing about is that you can use one of the new directives on
> > one line with the old ones, as long as the new are the first argument:
> >
> > # service syslogd enable
> > # service apache24 disable stop
> > # service apache24 rcdelete stop
> > # service nginx enable start
> >
> >
> > So after installing a package, to start and enable a daemon permanently
> > all you have to run is
> > # service foo enable start
> >
> > Lars
> >
> > P.S.: Thansk to Devin for his hard work on sysrc!
>
> Having a way for sysrc and service to know what particular options and
> services are exposed by a given package or installed "thing" would be
> nice. Right now the namespace is very flat and it's not obvious in all
> instances what needs to happen to make it useful and what the options
> are.
>
> "Oh, hm, I'd like to know what options there are for controlling the
> installed apache24 package, let's see"...
>
> I remember IRIX having that command to list services, stop them and
> start them, configure them enabled and disabled. Solaris grew
> something like that with Solaris 10 and after the initial learning
> curve it was great. Hving something like that would be 100% awesome.
I've updated the patch and extended it a little:
https://phabric.freebsd.org/D451
It can now print the rc options for a service.
It needs however to have the options listed as comments between the
KEYWORDS section and the sourcing of /etc/rc.subr.
And I've made some changes to rc.subr itself:
https://phabric.freebsd.org/D452
So now you can use
# service sshd describe
Secure Shell Daemon
and
# service sshd extracommands
configtest keygen reload
Sorry for the mess in phabricator's SUMMARY. I will learn the markup
syntax later...
Lars
pgp7uIZ9L4onn.pgp
Description: PGP signature
Re: HOWTO articles for migrating from Linux to FreeBSD, especially for pkg?
On Thu, Jul 17, 2014 at 10:21:17PM +0200, Andreas Nilsson wrote:
> On Thu, Jul 17, 2014 at 10:15 PM, Navdeep Parhar wrote:
>
> > On 07/17/14 13:12, Adrian Chadd wrote:
> > > On 17 July 2014 13:03, Alberto Mijares wrote:
> > >> On Thu, Jul 17, 2014 at 2:58 PM, Adrian Chadd
> > wrote:
> > >>> Hi!
> > >>>
> > >>> 3) The binary packages need to work out of the box
> > >>> 4) .. which means, when you do things like pkg install apache, it
> > >>> can't just be installed and not be enabled, because that's a bit of a
> > >>> problem;
> > >>
> > >>
> > >> No. Please NEVER do that! The user must be able to edit the files and
> > >> start the service by himself.
> > >
> > > Cool, so what's the single line command needed to type in to start a
> > > given package service?
> >
> > Aren't sysrc(8) and service(8) for this kind of stuff?
> >
>
> They sure are.
>
> Well, pkg install $service ; sysrc ${service}_enable="YES" would do.
> Although some services have different names than the packge, which is sort
> of annoying.
I hacked up a solution for service(8):
http://bsd-geek.de/FreeBSD/service.sh.enable-disable.patch
The patch adds the following directives to service(8):
enable: Grabs an rc script's rcvar value and runs "sysrc foo_enable=YES"
disable: The opposite of enable
rcdelete: Deletes an rc script's rcvar value from /etc/rc.conf using
"sysrc -x foo_enable"
The nice thing about is that you can use one of the new directives on
one line with the old ones, as long as the new are the first argument:
# service syslogd enable
# service apache24 disable stop
# service apache24 rcdelete stop
# service nginx enable start
So after installing a package, to start and enable a daemon permanently
all you have to run is
# service foo enable start
Lars
P.S.: Thansk to Devin for his hard work on sysrc!
pgpbRbppx85QX.pgp
Description: PGP signature
Re: HOWTO articles for migrating from Linux to FreeBSD, especially for pkg?
On Fri, Jul 18, 2014 at 02:10:25PM +0200, Lars Engels wrote: > On Thu, Jul 17, 2014 at 01:00:03PM -0700, Adrian Chadd wrote: > > On 17 July 2014 12:57, Andreas Nilsson wrote: > > > > > > > > > > > > On Thu, Jul 17, 2014 at 9:28 PM, Adrian Chadd wrote: > > >> > > >> Hi! > > >> > > >> 3) The binary packages need to work out of the box > > >> 4) .. which means, when you do things like pkg install apache, it > > >> can't just be installed and not be enabled, because that's a bit of a > > >> problem; > > > > > > I disagree on this. For network services on linux ( apart from ssh ), I > > > want > > > that started very seldom. But I do want the package installed so that > > > when I > > > need it, it is there. Having it autostart as part of being installed is > > > breaking KISS and in some way unix philosophy: I asked for something to be > > > installed, not installed and autostarted. > > > > That's cool. We can disagree on that. But the fact that you have to > > edit a file to enable things and hope you get the right start entry in > > /etc/rc.conf or /usr/local/etc/rc.conf, or wherever you put it is, is > > a pain. > > No, Sir! No need to edit anything: > > root@testjail: # pkg install apache24 > Updating repository catalogue > The following 5 packages will be installed: > > Installing pcre: 8.33 > Installing gdbm: 1.10 > Installing db42: 4.2.52_5 > Installing apr: 1.4.8.1.5.3 > Installing apache24: 2.4.6_1 > > The installation will require 47 MB more space > > 5 MB to be downloaded > > Proceed with installing packages [y/N]: y > gdbm-1.10.txz 100% 83KB 83.2KB/s 83.2KB/s 00:00 > db42-4.2.52_5.txz 100% 1457KB 1.4MB/s 1.4MB/s 00:00 > apr-1.4.8.1.5.3.txz 100% 390KB 389.5KB/s 389.5KB/s 00:00 > apache24-2.4.6_1.txz 100% 3649KB 3.6MB/s 3.6MB/s 00:00 > Checking integrity... done > [1/5] Installing pcre-8.33... done > [2/5] Installing gdbm-1.10... done > [3/5] Installing db42-4.2.52_5... done > [4/5] Installing apr-1.4.8.1.5.3... done > [5/5] Installing apache24-2.4.6_1...===> Creating users and/or groups. > Using existing group 'www'. > Using existing user 'www'. > /usr/local/share/examples/apache24/httpd.conf -> > /usr/local/etc/apache24/httpd.conf > done > To run apache www server from startup, add apache24_enable="yes" > in your /etc/rc.conf. Extra options can be found in startup script. > > Your hostname must be resolvable using at least 1 mechanism in > /etc/nsswitch.conf typically DNS or /etc/hosts or apache might > have issues starting depending on the modules you are using. > > root@testjail: # sysrc apache24_enable=yes > apache24_enable: -> yes > > root@testjail: # service apache24 start > Performing sanity check on apache24 configuration: > AH00557: httpd: apr_sockaddr_info_get() failed for testjail > AH00558: httpd: Could not reliably determine the server's fully > qualified domain name, using 127.0.0.1. Set the 'ServerName' directive > globally to suppress this message > Syntax OK > Starting apache24. > AH00557: httpd: apr_sockaddr_info_get() failed for testjail > AH00558: httpd: Could not reliably determine the server's fully > qualified domain name, using 127.0.0.1. Set the 'ServerName' directive > globally to suppress this message > root@testjail: # > > > That's 3 commands to enter. Admittedly 2 more than on some OS that > blindly starts any service you install, but 2 steps more logical and > even a newbie can do this. > > What could be done is that pkg looks for rc scripts in a package, > extracts the enable line and prints a message how to enable the script / > daemon permanently. > > Like: > - To start the script "apache24" once run "service apache24 onestart". > - To start the script "apache24" at boot time run "sysrc apache24_enable=yes" > - The script "apache24" has the following optional settings for /etc/rc.conf: > apache24_profiles (str): Set to "" by default. > Define your profiles here. > apache24limits_enable (bool):Set to "NO" by default. > Set it to yes to run `limits $limits_args` > just before apache starts. > apache24_flags (str):Set to "" by default. > Extra flags passed to start command. > apache24limits_args (str): Default to "-e -C daemon" > Arguments of pre-start limits run. > apache24_http_accept_enable (bool): Set to "NO" by default. > Set to yes to check for accf_http kernel > module on start up and load if not loaded. > apache24_fib (str): Set an altered default network view for apache > > > Sorry for no reading the whole thread first. This was already suggested in another part of the thread. pgp5P8SX3W5nE.pgp Description: PGP signature
Re: HOWTO articles for migrating from Linux to FreeBSD, especially for pkg?
On Thu, Jul 17, 2014 at 01:00:03PM -0700, Adrian Chadd wrote: > On 17 July 2014 12:57, Andreas Nilsson wrote: > > > > > > > > On Thu, Jul 17, 2014 at 9:28 PM, Adrian Chadd wrote: > >> > >> Hi! > >> > >> 3) The binary packages need to work out of the box > >> 4) .. which means, when you do things like pkg install apache, it > >> can't just be installed and not be enabled, because that's a bit of a > >> problem; > > > > I disagree on this. For network services on linux ( apart from ssh ), I want > > that started very seldom. But I do want the package installed so that when I > > need it, it is there. Having it autostart as part of being installed is > > breaking KISS and in some way unix philosophy: I asked for something to be > > installed, not installed and autostarted. > > That's cool. We can disagree on that. But the fact that you have to > edit a file to enable things and hope you get the right start entry in > /etc/rc.conf or /usr/local/etc/rc.conf, or wherever you put it is, is > a pain. No, Sir! No need to edit anything: root@testjail: # pkg install apache24 Updating repository catalogue The following 5 packages will be installed: Installing pcre: 8.33 Installing gdbm: 1.10 Installing db42: 4.2.52_5 Installing apr: 1.4.8.1.5.3 Installing apache24: 2.4.6_1 The installation will require 47 MB more space 5 MB to be downloaded Proceed with installing packages [y/N]: y gdbm-1.10.txz 100% 83KB 83.2KB/s 83.2KB/s 00:00 db42-4.2.52_5.txz 100% 1457KB 1.4MB/s 1.4MB/s 00:00 apr-1.4.8.1.5.3.txz 100% 390KB 389.5KB/s 389.5KB/s 00:00 apache24-2.4.6_1.txz 100% 3649KB 3.6MB/s 3.6MB/s 00:00 Checking integrity... done [1/5] Installing pcre-8.33... done [2/5] Installing gdbm-1.10... done [3/5] Installing db42-4.2.52_5... done [4/5] Installing apr-1.4.8.1.5.3... done [5/5] Installing apache24-2.4.6_1...===> Creating users and/or groups. Using existing group 'www'. Using existing user 'www'. /usr/local/share/examples/apache24/httpd.conf -> /usr/local/etc/apache24/httpd.conf done To run apache www server from startup, add apache24_enable="yes" in your /etc/rc.conf. Extra options can be found in startup script. Your hostname must be resolvable using at least 1 mechanism in /etc/nsswitch.conf typically DNS or /etc/hosts or apache might have issues starting depending on the modules you are using. root@testjail: # sysrc apache24_enable=yes apache24_enable: -> yes root@testjail: # service apache24 start Performing sanity check on apache24 configuration: AH00557: httpd: apr_sockaddr_info_get() failed for testjail AH00558: httpd: Could not reliably determine the server's fully qualified domain name, using 127.0.0.1. Set the 'ServerName' directive globally to suppress this message Syntax OK Starting apache24. AH00557: httpd: apr_sockaddr_info_get() failed for testjail AH00558: httpd: Could not reliably determine the server's fully qualified domain name, using 127.0.0.1. Set the 'ServerName' directive globally to suppress this message root@testjail: # That's 3 commands to enter. Admittedly 2 more than on some OS that blindly starts any service you install, but 2 steps more logical and even a newbie can do this. What could be done is that pkg looks for rc scripts in a package, extracts the enable line and prints a message how to enable the script / daemon permanently. Like: - To start the script "apache24" once run "service apache24 onestart". - To start the script "apache24" at boot time run "sysrc apache24_enable=yes" - The script "apache24" has the following optional settings for /etc/rc.conf: apache24_profiles (str): Set to "" by default. Define your profiles here. apache24limits_enable (bool):Set to "NO" by default. Set it to yes to run `limits $limits_args` just before apache starts. apache24_flags (str):Set to "" by default. Extra flags passed to start command. apache24limits_args (str): Default to "-e -C daemon" Arguments of pre-start limits run. apache24_http_accept_enable (bool): Set to "NO" by default. Set to yes to check for accf_http kernel module on start up and load if not loaded. apache24_fib (str): Set an altered default network view for apache pgpd7Che1W7iN.pgp Description: PGP signature
Re: [patch] USB after second suspend/resume on ThinkPads.
On Mon, Jun 16, 2014 at 09:21:55PM +0200, Edward Tomasz Napierała wrote: > Hi. Patch below should fix a problem where USB stops working after > _second_ suspend/resume, which happens on various ThinkPad models. > Please test, and report both success stories and failures. If nothing > comes up, I'll commit it in a week or so. > > (Btw, has anyone encountered the problem on hardware other than ThinkPads?) You, Sir, are officially my hero of the month! I applied the patch and it works flawlessly on my Thinkpad X200 (4 resumes so far). Thanks a lot! Lars pgp0wJKMMXJGm.pgp Description: PGP signature
Re: Leaving the Desktop Market
On Wed, Apr 02, 2014 at 10:22:32AM +0100, David Chisnall wrote: > On 1 Apr 2014, at 23:10, Kevin Oberman wrote: > > > Audio output is pretty system dependent, but I had little problem getting > > my audio to auto-switch to headphones when I plugged them in. The setup is > > a bit ugly,but I only had to check the available PINs (ugly, ugly) and set > > up stuff once. It just works. If you want my example set-up, I can post it > > somewhere or you can look in the archives for it as I have posted it in the > > past. > > It would be good to have this in the handbook (and to see what we can > do to improve it). FreeBSD audio typically works out of the box and > it's great when it does[1], but it can be underdocumented black magic > to make it work when it doesn't. For example, I believe it's possible > to tell pcm that when it receives a stereo stream it should redirect > the left channel to the front and rear left, and the right channel to > the front and rear right, but I haven't yet worked out how to do this > - I'd have thought it was the kind of default that we'd want to have. > > The use case that PulseAudio was [over]designed to fix was plugging in > USB headphones (or connecting a Bluetooth headset) and having existing > audio streams redirected there. This should be possible with the > existing sound stack, but there are some bits of plumbing missing. We > already do in-kernel mixing and resampling, which are the hard bits. > Duplicating streams and redirecting them are trivial by comparison. > > David > > [1] Although I had a slightly embarrassing moment when I spent an hour > hunting for docs to tell me how to configure my media centre box do > 5.1 output and then decided to just try it and found it worked out of > the box. AFAIK we already can configure HDA's sound output and input in many ways using sysctl(8). What's still missing is a user-friendly way to configure sound. There are some things that can be handled in one little program / script / TUI / GUI / CLI: - Default sound unit (hw.snd.default_unit) - Use the last inserted sound device as default? (hw.snd.default_auto) - PIN Routing (dev.hdaa.%d.config) - Mixer settings Putting it all together in something called sndcontrol should not be too hard. It just takes someone(TM) to do it pgpm1Mkt0Pad2.pgp Description: PGP signature
Re: Leaving the Desktop Market
On Tue, Apr 01, 2014 at 07:52:13AM -0700, dte...@freebsd.org wrote: > > > > -Original Message- > > From: Lars Engels [mailto:lars.eng...@0x20.net] > > Sent: Tuesday, April 1, 2014 2:41 AM > > To: Jordan Hubbard > > Cc: Eitan Adler; hack...@freebsd.org; curr...@freebsd.org; freebsd- > > advoc...@freebsd.org > > Subject: Re: Leaving the Desktop Market > > > > On Tue, Apr 01, 2014 at 12:11:19PM +0500, Jordan Hubbard wrote: > > > > > > On Apr 1, 2014, at 10:46 AM, Eitan Adler wrote: > > > > > > > That is why on this date I propose that we cease competing on the > > > > desktop market. FreeBSD should declare 2014 to be "year of the > [snip] > > > I'm a happy FreeBSD desktop user since 4.7. There are some edges, but I > > really like that I can can create a desktop the way _I_ want it and my mail > > client even allows me to break lines at 80 chars. Eat that, Apple Mail! ;-) > > What e-mail client do you use? Evolution? No, mutt, with vim as mail composer. :) pgpSJwTsqAsgD.pgp Description: PGP signature
Re: Leaving the Desktop Market
On Tue, Apr 01, 2014 at 12:11:19PM +0500, Jordan Hubbard wrote: > > On Apr 1, 2014, at 10:46 AM, Eitan Adler wrote: > > > That is why on this date I propose that we cease competing on the > > desktop market. FreeBSD should declare 2014 to be "year of the Linux > > desktop" and start to rip out the pieces of the OS not needed for > > server or embedded use. > > > > Some of you may point to PCBSD and say that we have a chance, but I > > must ask you: how does one flavor stand up to the thousands in the > > Linux world? > > The fact that this posting comes out on April 1st makes me wonder if > it’s just an elaborate April Fool’s joke, but then the notion of *BSD > (or Linux, for that matter) on the Desktop is just another > long-running April fool’s joke, so I’m willing to postulate that two > April Fools jokes would simply cancel each other out and make this > posting a serious one again. :-) > > I’ll choose to be serious and say what I’m about to say in spite of > the fact that I work for the primary sponsor of PC-BSD and actually > like the fact that it has created some interesting technologies like > PBIs, the Jail Warden, Life-preserver and a ZFS boot environment menu. > > There is no such thing as a desktop market for *BSD or Linux. There > never has been and there never will be. Why do you think we chose > “the power to serve” as FreeBSD’s first marketing slogan? It makes a > fine server OS and it’s easy to defend its role in the server room. > It’s also becoming easier to defend its role as an embedded OS, which > is another excellent niche to pursue and I am happy to see all the > recent developments there. > > A desktop? Unless you consider Mac OS X to be “BSD on the desktop” > (and while they share some common technologies, it’s increasingly a > stretch to say that), it’s just never going to happen for (at least) > the following reasons: > > 1. Power. As you point out, being truly power efficient is a complete > top-to-bottom engineering effort and it takes a lot more than just > trying to idle the processor whenever possible to achieve that. You > need to optimize all of the hot-spot routines in the system for power > efficiency (which actually involves a fair amount of micro > architecture knowledge), you need a kernel scheduler that is power > management aware, you need a process management system that runs as > few things as possible and knows how to schedule things during package > wake-up intervals, you need timers to be coalesced at the level where > applications consume them, the list just goes on and on. It’s a lot > of engineering work, and to drive that work you also need a lot of > telemetry data and people with big sticks running around hitting > people who write power-inefficient code. FreeBSD has neither. > > 2. Multimedia. A real end-user’s desktop is basically one big UI for > watching things, listening to things, and running apps. A decent > audio / video subsystem is just one part of the picture, and one that > has always been really weak - entire engineering teams can spend years > working on codecs, performance optimizations, low and guaranteed > latency support for audio I/O, etc. What’s worse, the bar is only > being raised. You want to be part of the next wave of folks who can > author and edit content for the new 4K video standard? Not on FreeBSD > or Linux, you’re not. > > 3. Applications. A desktop without real and useful applications is > not a desktop, it’s just an empty display surface. Sure, there are > users out there who are happy with just a mail client, a web browser > and maybe a calendaring app, but those users are also arguably even > better candidates for Chrome or other simplified environments where > all of that simply happens in a fancy web browser and you get things > like “software updates” and cloud integration essentially for free > since it’s all just one cohesive picture there. The ability to solve > those user’s needs very simply makes them ripe targets for the web > application delivery platforms. > > For the other folks who want to do fancier stuff like mix audio, edit > videos or even just play mainstream 3D games that were actually > published sometime in the last year, they’ll use a real desktop OS and > won't even bother looking at one of the free ones because guess what, > the free ones just can’t do those things, or do them badly enough that > their users feel like they’re perpetually living in a kind of > self-selected ghetto. Metaphorically speaking, sleeping on the floor > in a sleeping bag in your one-room apartment is fine when you’re > young, but as you get older, you want to be more comfortable and have > a real bed in a real house! > > Those are just three reasons. There are lots more, not least of which > among them is the fact that it’s damn hard even just to *create* > significant applications with the weak-ass APIs that *BSD and Linux > provide. You have to stitch together some Frankenstein collec
Re: A proposal
On Sat, Mar 29, 2014 at 06:11:10AM -0700, Steve Kargl wrote: > On Sat, Mar 29, 2014 at 10:29:23AM +0100, Lars Engels wrote: > > On Fri, Mar 28, 2014 at 10:52:49PM -0700, Steve Kargl wrote: > >> On Sat, Mar 29, 2014 at 01:46:15AM -0400, Joe Nosay wrote: > >>> On Sat, Mar 29, 2014 at 1:43 AM, Allan Jude wrote: > >>> > >>>> On 2014-03-29 01:22, Joe Nosay wrote: > >>>>> I have noticed that options VPS, VIMAGE, and MROUTING are not standard > >>>> for > >>>>> the kernel with a base install. Is there any way that these can be made > >>>>> a > >>>>> part of the normal kernel so that jail(s) would get the full benefit > >>>>> without a kernel recompile? > >>>>> > >>>> > >>>> VIMAGE has some problems with PF. Martin Matu ska said at AsiaBSDCon > >>>> that he had a patch that solves the issue. > >>> > >>> Really, you say? That's good news. > >>> So, will those options soon be standard for a first time install? > >> > >> Certainly, hope not. I don't use any of options. > > > > So you use all the other devices and options of the GENERIC kernel? > > Of course, not. Not sure how you inferred such a thing. > > IMHO, GENERIC should contain only those devices and options > that are required to get FreeBSD booted on new hardware. > VIMAGE and MROUTING aren't needed, and can be configured by > the user after installation. As for VPS, AFAICT, there isn't > an option/device named VPS; at least 'find /sys/ -type f | xargs > grep VPS' wasn't too enlightening. IMHO common use scenarios should be included in GENERIC if they're stable and mature. E.g. I don't know why IPSEC still isn't in GENERIC. pgpbdbYRYczJw.pgp Description: PGP signature
Re: A proposal
On Fri, Mar 28, 2014 at 10:52:49PM -0700, Steve Kargl wrote: > On Sat, Mar 29, 2014 at 01:46:15AM -0400, Joe Nosay wrote: > > On Sat, Mar 29, 2014 at 1:43 AM, Allan Jude wrote: > > > > > On 2014-03-29 01:22, Joe Nosay wrote: > > > > I have noticed that options VPS, VIMAGE, and MROUTING are not standard > > > for > > > > the kernel with a base install. Is there any way that these can be made > > > > a > > > > part of the normal kernel so that jail(s) would get the full benefit > > > > without a kernel recompile? > > > > ___ > > > > freebsd-current@freebsd.org mailing list > > > > http://lists.freebsd.org/mailman/listinfo/freebsd-current > > > > To unsubscribe, send any mail to " > > > freebsd-current-unsubscr...@freebsd.org" > > > > > > > > > > VIMAGE has some problems with PF. Martin Matu ska said at AsiaBSDCon > > > that he had a patch that solves the issue. > > > > Really, you say? That's good news. > > So, will those options soon be standard for a first time install? > > Certainly, hope not. I don't use any of options. So you use all the other devices and options of the GENERIC kernel? pgpDFWhHRjTdf.pgp Description: PGP signature
Re: Using of Dragonfly Mail Agent -- what should be permissions on dma.conf and auth.conf?
On Mon, Mar 24, 2014 at 07:05:10AM -0600, Ian Lepore wrote: > On Mon, 2014-03-24 at 07:16 -0500, Mark Felder wrote: > > On 2014-03-24 06:53, Lev Serebryakov wrote: > > > Hello, Freebsd-current. > > > > > > I've tried "440" with owner 25:25 and "mail l...@serebryakov.spb.ru" > > > complains, that it could not access them. > > > > > > Also, what is proper way to attach dma into system instead of senndmal > > > now? > > > > > > I'm not sure what the permissions of those files should really be, but > > this is likely what you want in mailer.conf: > > > > sendmail/usr/libexec/dma > > send-mail /usr/libexec/dma > > mailq /usr/libexec/dma > > > > and rc.conf: > > > > sendmail_enable="NO" > > sendmail_submit_enable="NO" > > sendmail_outbound_enable="NO" > > sendmail_msp_queue_enable="NO" > > > > Shorthand for that is: sendmail_enable="NONE" Which is deprecated, AFAIK. pgpRw10OGQmJV.pgp Description: PGP signature
Re: (more) screen distortion with intel GPU / xorg on recent -HEAD?
On Sun, Mar 23, 2014 at 06:41:05PM -0700, Adrian Chadd wrote: > No, this isn't a "the buffer is messed up", this is a "everything is > and stays messed up." > > Starting new applications odes'nt fix it. > > Minimising/maximising the applications again doesn't fix it. > > This is a "the framebuffer config seems busted", not "the contents of > that 2d rectaugular area got messed up." Normally when there's > distortions triggering some kind of change in that area (ie: not a > redraw) is enough to fix it. > Oh okay, then I didn't encounter it, yet. I can provide a screenshot of what I am seeing, the next time it happens. pgpDL9F7c7o9Y.pgp Description: PGP signature
Re: (more) screen distortion with intel GPU / xorg on recent -HEAD?
On Sun, Mar 23, 2014 at 01:36:29PM -0700, Adrian Chadd wrote: > Less information-poor response: > > * when it happens, the FB will resume correctly for a little bit, then > once everything comes back, it flips to being distorted. So, it's > likely something is misconfiguring stuff during resume. > * I can flip to VTs fine; I can login and do things fine; > * When I flip back to xorg, things still remain distorted; > * If I ctrl-C xorg and start it again, it starts back up correctly. Setting a new wallpaper and / or restarting the distorted windows un-distorts them. pgpjV3j2WcNhv.pgp Description: PGP signature
Re: freebsd-update
Am 2014-01-29 22:51, schrieb Colin Percival: On 01/29/14 12:51, Lars Engels wrote: On Sat, Jan 25, 2014 at 09:11:04AM -0600, Mark Felder wrote: On Sat, Jan 25, 2014, at 5:32, Lars Engels wrote: Also using freebsd-update behind a proxy is really slow. Even with a very fast internet connection (normally download rates ca. 3 MBytes / s) downloading all the tiny binary diff files took more than 8 hours. Maybe freebsd-update's backend could create a tarball of all those diffs and provide this? Even streaming the tar instead of waiting for the freebsd-update server to produce the tarball would be an improvement. I have no experience doing that over a WAN but I don't see why it would be unreliable. Colin, what do you think? Is it possible? Anything is *possible*, but given that the number of patches available is typically at least 10x the number being fetched this doesn't seem like it would be very efficient. FWIW, the performance problems with proxies are limited to HTTP proxies which don't speak HTTP/1.1. Are you sure? I just tried it manually with telnet: # telnet proxyserver 8080 Trying ... Connected to proxyserver. CONNECT www.heise.de:80 HTTP/1.1 Proxy-Authorization:Basic blahblahblahbase64 HTTP/1.1 200 Connection established GET / HTTP/1.1 HTTP/1.1 400 Bad Request IIUC the proxy itself supports HTTP/1.1 but not the webserver behind the proxy? That's the same proxy that takes hours to download the patches with httpget. ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"
Re: freebsd-update
On Sat, Jan 25, 2014 at 09:11:04AM -0600, Mark Felder wrote: > > > On Sat, Jan 25, 2014, at 5:32, Lars Engels wrote: > > > > > > Also using freebsd-update behind a proxy is really slow. Even with a > > very fast internet connection (normally download rates ca. 3 MBytes / s) > > downloading all the tiny binary diff files took more than 8 hours. > > Maybe freebsd-update's backend could create a tarball of all those diffs > > and provide this? > > Even streaming the tar instead of waiting for the freebsd-update server > to produce the tarball would be an improvement. I have no experience > doing that over a WAN but I don't see why it would be unreliable. Colin, what do you think? Is it possible? pgpcfAO3phOfE.pgp Description: PGP signature
Re: freebsd-update
On Fri, Jan 24, 2014 at 02:40:44PM -0500, Allan Jude wrote: > On 2014-01-21 15:42, Kevin Oberman wrote: > > On Tue, Jan 21, 2014 at 8:49 AM, John Baldwin wrote: > > > >> On Tuesday, January 21, 2014 10:46:37 am David Chisnall wrote: > >>> On 21 Jan 2014, at 07:13, Antonio Olivares > >> wrote: > On Tue, Jan 21, 2014 at 7:49 AM, Ivan Voras > >> wrote: > > Hi, > > > > Is there any way I can avoid manually resolving hundreds of merge > > conflicts of the following type while using freebsd-update ? > > > > 1 <<< current version > > > > > > 2 # $FreeBSD: release/9.0.0/etc/csh.cshrc 50472 1999-08-27 23:37:10Z > > peter $ > > > > 3 === > > > > > > 4 # $FreeBSD: release/10.0.0/etc/csh.cshrc 50472 1999-08-27 23:37:10Z > > peter $ > > > > 5 >>> 10.0-RELEASE > > > > > > > > ? > > > > I can't be the only one seeing those...? > > > Yes, One has to manually go one by one to fix these :( > I tried at one point a sed command like sed -i "" '' to fix > these, but it did not work correctly. I see errrors when booting when > I don't correct these :( > >>> I thought this was fixed already (I didn't see these in the 9.2->10-RC3 > >> upgrade). Doesn't freebsd-update pass -F (If the files differ only by VCS > >> Id > >> ($FreeBSD) install the new file) to mergemaster? > >> > >> AFAIK it doesn't use mergemaster? I thought it used its own tool? I > >> really > >> want to figure out a way to let it use etcupdate instead since it handles > >> this case even for locally modified files cleanly. > >> > > Having just gone through this on a 10.0-rc5 to 10.0-RELEASE run, I can > > assure you that it is not completely fixed. One huge part is fixed... every > > file's ID line is no longer is changed on every release. OTOH, for files > > that are modified, thy still show up. It hit many of the sendmail .cf > > files. Annoying as I don't even use sendmail. > > > > Not sure if there was a good reason Colin re-invented the wheel on this. It > > does not use mergemaster or even a reasonable differences editor such as > > the one mergemaster uses. Just going to the mergemaster code for handling > > diffs would be a HUGE win. I am getting really tired of > > "/3n". > > I discussed this a bit with Colin on Wednesday during our interview with > him for BSDNow.tv > > He had some problems with mergemaster so wrote his own tool. In 10 it > ignores the $Id tags, but there are still other changes that have to > either be merged or the file replaced with the new one. > > I am all for further improvement here. Also using freebsd-update behind a proxy is really slow. Even with a very fast internet connection (normally download rates ca. 3 MBytes / s) downloading all the tiny binary diff files took more than 8 hours. Maybe freebsd-update's backend could create a tarball of all those diffs and provide this? pgpIndNjzE60b.pgp Description: PGP signature
Re: iwn(4) hangs after r257133
Am 11.11.2013 09:18, schrieb Stefan Farfeleder: On Sun, Nov 10, 2013 at 02:01:12PM -0800, Adrian Chadd wrote: Yes. So one of the.. unfortunately broken things in iwn is the ampdu tx code doesn't do retransmits. So if amrr picks a rate that fails to transmit everything, the driver doesn't retransmit them. It frees them. Now when amrr is enabled the hardware will retry at lower rates until something succeeds. But it still doesn't retransmit things. I believe it should be. So yes its more broken with Mrr disabled. But enabling mrr doesn't fix it. It just makes it less broken. Someone needs to implement ampdu retransmit. The latest iwn code in head at least tells the rate selection code that a total ampdu tx failure occured. This BTW is one of the hangs I fixed - if you hit a point where you never successfully transmitted an ampdu at a rate the rate would never be decreased. Now to be clear. I won't be in implementing ampdu retransmit. I'll maybe fix last multi rate retry once the new hardware support is in. I would really appreciate help here with these. Everyone with iwn hardware will appreciate it :) In the mean time, wouldn't it make sense to disable ampdu tx in iwn then? Or to disallow the combination Mrr + ampdu? Yes, please. I'm also encountering this. ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"
Re: [CFT] Kernel-Selection Enhancemnt to Boot Menu
Am 05.11.2013 18:06, schrieb Kurt Lidl: Well, I'd probably be in support of this change - it sure beats having to interrupt the normal boot sequence and typing: unload load /boot/kernel.old/kernel load /boot/kernel.old/opensolaris.ko load /boot/kernel.old/zfs.ko boot To load an older kernel I always just type boot kernel.old Doesn't that unload the currently loaded kernel automatically? ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"
Re: Panic in arptimer on r255764
On Sun, Sep 22, 2013 at 05:11:30AM -0700, Davide Italiano wrote: > On Sun, Sep 22, 2013 at 2:25 AM, Lars Engels wrote: > > On Sat, Sep 21, 2013 at 11:23:47PM -0700, Tim Kientzle wrote: > >> I'm seeing this panic pretty consistently when I try to do a buildworld on > >> r255764 (i386): > >> > >> http://people.freebsd.org/~kientzle/r255764%20panic%202013-09-21%20at%209.27.09%20PM.png > >> > >> I'm not seeing it on r255602, so I suspect it's a recent problem. > >> > >> Running on VMWare Fusion 6. This was about as vanilla a build as you > >> can get: no local code changes, no custom config, no src.conf or > >> make.conf, no ports installed, etc. > >> > > > > +1 > > > > I also see this on yesterday's HEAD: > > > > http://bsd-geek.de/pics/IMG_20130922_100936.jpg > > > > The only difference is that I don''t need to run a buildworld, just > > going into multi user and wait a few seconds. > > I don't see this in single user mode, though. > > > Try this: > http://people.freebsd.org/~davide/review/lc_calloutfix.diff > I'll commit as soon as I'll receive OK from re@. Yes, that seems to help. I am running it for a few minutes now which is a few minutes more that without the patch. ;-) Thanks! P.S.: Fortunately I migrated the system to ZFS with Boot Environments, so I could boot the old world and kernel without any hassle! \o/ pgpE7WRGgSZwa.pgp Description: PGP signature
Re: Panic in arptimer on r255764
On Sat, Sep 21, 2013 at 11:23:47PM -0700, Tim Kientzle wrote: > I'm seeing this panic pretty consistently when I try to do a buildworld on > r255764 (i386): > > http://people.freebsd.org/~kientzle/r255764%20panic%202013-09-21%20at%209.27.09%20PM.png > > I'm not seeing it on r255602, so I suspect it's a recent problem. > > Running on VMWare Fusion 6. This was about as vanilla a build as you > can get: no local code changes, no custom config, no src.conf or > make.conf, no ports installed, etc. > +1 I also see this on yesterday's HEAD: http://bsd-geek.de/pics/IMG_20130922_100936.jpg The only difference is that I don''t need to run a buildworld, just going into multi user and wait a few seconds. I don't see this in single user mode, though. pgpICQ8dP_pDV.pgp Description: PGP signature
Re: how to make a option in menuconfig as new feature
On Mon, Aug 26, 2013 at 05:22:51PM +0500, Yasir hussan wrote: > Hi, > > I want to add up a kernel module to my linux kernel,currently i am mannuly > changing .config file to include my new module but i want to add it as > option in menuconfig from where i choose it where it should be included or > not... > > Thanks Hi, wrong mailing list, wrong operating system. FreeBSD is not Linux. :) pgpYZAfkVOLl4.pgp Description: PGP signature
Re: Problems with usb bluetooth device
On Sat, Mar 28, 2009 at 11:00:32AM +0100, Hans Petter Selasky wrote: > On Saturday 28 March 2009, Lars Engels wrote: > > Hi all, > > > > yesterday I bought a shiny new hama usb bluetooth dongle but I am having > > some problems using it: > > > > before loading ng_ubt: > > usb2_alloc_device:1480: set address 2 failed (ignored) > > usb2_alloc_device:1516: getting device descriptor at addr 2 failed! > > usb2_req_re_enumerate:1421: addr=2, set address failed! (ignored) > > usb2_req_re_enumerate:1434: getting device descriptor at addr 2 failed! > > usb2_req_re_enumerate:1421: addr=2, set address failed! (ignored) > > usb2_req_re_enumerate:1434: getting device descriptor at addr 2 failed! > > ugen0.2: <> at usbus0 (disconnected) > > after loading ng_ubt: > > uhub_reattach_port:413: could not allocate new device! > > ubt0: > 2.00/1.00, addr 2> on usbus2 ^^ > > internal bluetooth device > > WARNING: attempt to net_add_domain(bluetooth) after domainfinalize() > > WARNING: attempt to net_add_domain(netgraph) after domainfinalize() > > ugen0.2: at usbus0 > > ubt1: > 2.00/48.39, addr 2> on usbus0 ubt1: ubt_bulk_read_callback:837: bulk-in > > transfer failed: USB_ERR_STALLED ubt1: ubt_intr_read_callback:741: > > interrupt transfer failed: USB_ERR_STALLED ubt1: at uhub0, port 1, addr 2 > > (disconnected) > > ugen0.2: at usbus0 (disconnected) > > device re-inserted: > > usb2_alloc_device:1480: set address 2 failed (ignored) > > usb2_alloc_device:1516: getting device descriptor at addr 2 failed! > > usb2_req_re_enumerate:1421: addr=2, set address failed! (ignored) > > usb2_req_re_enumerate:1434: getting device descriptor at addr 2 failed! > > usb2_req_re_enumerate:1421: addr=2, set address failed! (ignored) > > usb2_req_re_enumerate:1434: getting device descriptor at addr 2 failed! > > ugen0.2: <> at usbus0 (disconnected) > > uhub_reattach_port:413: could not allocate new device! > > > > So the device is no longer recognized after I re-connect it. usbconfig does > > not show it: ugen0.1: at usbus0, cfg=0 md=HOST > > spd=FULL (12Mbps) pwr=ON ugen1.1: at usbus1, cfg=0 > > md=HOST spd=FULL (12Mbps) pwr=ON ugen2.1: at usbus2, > > cfg=0 md=HOST spd=FULL (12Mbps) pwr=ON ugen3.1: at > > usbus3, cfg=0 md=HOST spd=FULL (12Mbps) pwr=ON ugen4.1: > Intel> at usbus4, cfg=0 md=HOST spd=HIGH (480Mbps) pwr=ON ugen2.2: > Bluetooth 2.0 plus EDR Broadcom Corp> at usbus2, cfg=0 md=HOST spd=FULL > > (12Mbps > > pwr=ON > > > > It only lists the internal device... > > > > My CURRENT was compiled two days ago, so I should be up-to-date. > > Does it work when you use an external USB HUB? > > Does this device have some kind of autoinstall on it? > > You could try enabling uhci/ehci debugging. > sysctl hw.usb2.uhci.debug = 15 > > Then we would know the exact cause of the error. Just for your info: Aug 10 15:21:45 milhouse kernel: ubt1: on usbus3 Aug 10 15:21:45 milhouse devd: Executing '/etc/rc.d/bluetooth quietstart ubt1' After 4 years, the device now works without an external hub. ;-)) Lars pgptpC7GOmMki.pgp Description: PGP signature
Re: 802.1X: dhclient started before the auth. process ends
On Mon, Jul 29, 2013 at 04:00:44PM +0200, Jean-Sébastien Pédron wrote: > On 29.07.2013 15:34, Adrian Chadd wrote: > > I think you were lucky. > > I think you're right. > > It works perfectly on FreeBSD 9.1, because wpa_supplicant finishes the > auth process really quickly, ie. before dhclient receives an answer from > dhcpd from the unauthenticated network: > > Jul 29 15:39:46 - kernel: bge0: link state changed to UP > Jul 29 15:39:46 - dhclient[46150]: DHCPREQUEST on bge0 to > 255.255.255.255 port 67 > Jul 29 15:39:47 - wpa_supplicant[46119]: CTRL-EVENT-EAP-STARTED EAP > authentication started > ... > Jul 29 15:39:47 - wpa_supplicant[46119]: CTRL-EVENT-EAP-SUCCESS EAP > authentication completed successfully > Jul 29 15:39:48 - dhclient[46150]: DHCPREQUEST on bge0 to > 255.255.255.255 port 67 > Jul 29 15:39:48 - dhclient[46150]: DHCPACK from 192.168.200.224 > Jul 29 15:39:48 - dhclient: New IP Address (bge0): 192.168.200.91 > Jul 29 15:39:48 - dhclient: New Subnet Mask (bge0): 255.255.255.0 > Jul 29 15:39:48 - dhclient: New Broadcast Address (bge0): 192.168.200.255 > Jul 29 15:39:48 - dhclient: New Routers (bge0): 192.168.200.254 > > On -CURRENT, wpa_supplicant is started more than 10 seconds after the > interface is UP and dhclient sent its request > (http://pastebin.com/ZHcbHLQZ). Therefore, a lease from the > unauthenticated network arrives first. It was working with a previous > -CURRENT (buildworld from around April if memory serves). AFAIK rpaulo@ imported a new version of wpa_supplicant into -CURRENT. > > > dhclient shouldn't start running until wpa_supplicant has completed > > authentication. > > Damn, I always thought it worked this way on FreeBSD and happily laughed > at "Linux co-workers" who use some kind of rc.local script to work > around this issue :-) In fact, we're all in the same boat! > > I may take a look at the issue. I guess the place to fix this is in the > rc scripts. Does someone have a hint? pgph6bZA_QFU9.pgp Description: PGP signature
Re: 802.1X: dhclient started before the auth. process ends
On Mon, Jul 29, 2013 at 04:00:44PM +0200, Jean-Sébastien Pédron wrote: > On 29.07.2013 15:34, Adrian Chadd wrote: > > I think you were lucky. > > I think you're right. > > It works perfectly on FreeBSD 9.1, because wpa_supplicant finishes the > auth process really quickly, ie. before dhclient receives an answer from > dhcpd from the unauthenticated network: > > Jul 29 15:39:46 - kernel: bge0: link state changed to UP > Jul 29 15:39:46 - dhclient[46150]: DHCPREQUEST on bge0 to > 255.255.255.255 port 67 > Jul 29 15:39:47 - wpa_supplicant[46119]: CTRL-EVENT-EAP-STARTED EAP > authentication started > ... > Jul 29 15:39:47 - wpa_supplicant[46119]: CTRL-EVENT-EAP-SUCCESS EAP > authentication completed successfully > Jul 29 15:39:48 - dhclient[46150]: DHCPREQUEST on bge0 to > 255.255.255.255 port 67 > Jul 29 15:39:48 - dhclient[46150]: DHCPACK from 192.168.200.224 > Jul 29 15:39:48 - dhclient: New IP Address (bge0): 192.168.200.91 > Jul 29 15:39:48 - dhclient: New Subnet Mask (bge0): 255.255.255.0 > Jul 29 15:39:48 - dhclient: New Broadcast Address (bge0): 192.168.200.255 > Jul 29 15:39:48 - dhclient: New Routers (bge0): 192.168.200.254 > > On -CURRENT, wpa_supplicant is started more than 10 seconds after the > interface is UP and dhclient sent its request > (http://pastebin.com/ZHcbHLQZ). Therefore, a lease from the > unauthenticated network arrives first. It was working with a previous > -CURRENT (buildworld from around April if memory serves). AFAIK rui@ imported a new version of wpa_supplicant into -CURRENT. > > > dhclient shouldn't start running until wpa_supplicant has completed > > authentication. > > Damn, I always thought it worked this way on FreeBSD and happily laughed > at "Linux co-workers" who use some kind of rc.local script to work > around this issue :-) In fact, we're all in the same boat! > > I may take a look at the issue. I guess the place to fix this is in the > rc scripts. Does someone have a hint? pgpoXUQ0_TnHn.pgp Description: PGP signature
Re: 802.1X: dhclient started before the auth. process ends
On Fri, Jul 26, 2013 at 02:34:51PM +0200, Jean-Sébastien Pédron wrote: > Hi! > > At $WORK, we use 802.1X to authenticate computers on the network. > Authenticated computers receive a lease in the 192.168.X.X/24 network. > Unauthenticated ones receive a lease in the 172.16.X.X/24 network. > > Today, I upgraded one computer running 10-CURRENT to latest HEAD and it > seems that the interface is brought up to early now: dhclient is started > before wpa_supplicant finishes. This was working perfectly before the > upgrade. > > I don't have logs of the working case, but here are the logs of the > non-working one: > http://pastebin.com/ZHcbHLQZ > > Was I lucky with wpa_supplicant/dhclient timing? Or is there a real > issue here? > CC'ed wireless@, that's probably the proper list for the issue. pgpTg7Tk0CF6e.pgp Description: PGP signature
Re: [HEADSUP] No more pkg_install on HEAD by default
On Mon, Jul 15, 2013 at 11:52:26AM -0500, Mark Felder wrote: > On Mon, 15 Jul 2013 11:48:18 -0500, Teske, Devin > wrote: > > I think Mark was saying that libfetch doesn't yet support http proxy. > > Now that I've googled, I was referring to this PR > http://www.freebsd.org/cgi/query-pr.cgi?pr=180253 > > I thought it was complete missing functionality, not just that bug. libfetch supports proxies even with authentication using HTTP_PROXY_AUTH environment variable pgpwNwIYXocDX.pgp Description: PGP signature
Re: Ports with daemons on uninstall...
On Mon, Jul 15, 2013 at 01:46:03PM +, Walter Hurry wrote: > On Mon, 15 Jul 2013 08:34:05 -0500, Mark Felder wrote: > > > As long as this behavior only happens during pkg installs and never with > > ports, I'm OK. The worst is when a coworker forgets that the mysql port > > stops the daemon and my coworker upgrades with portmaster... the daemon > > is off the entire time mysql slowly compiles... > > I'm not familiar with portmaster, since I use portupgrade. That does the > build first, then the deinstall old/install new. Seems a sensible > approach anyway, in case the build fails. Doesn't portmaster work > similarly? Yes. PM builds, creates a backup package, deinstalls the old packages, installs the new one. pgp2inH11AJYo.pgp Description: PGP signature
Re: FreeBSD-head hang when shutdown by ACPI with Intel GPU and new Xorg and SandyBridge
On Fri, Jul 12, 2013 at 11:26:06AM +0100, David Chisnall wrote: > On 12 Jul 2013, at 10:01, "Lundberg, Johannes" > wrote: > > >> As the KMS code does not switch the display mode back, once X with KMS > > starts, you can't get a console back. > > > > Is there any solution for this in the works? > > Yes. ray@ is currently being funded by the FreeBSD Foundation to > improve Newcons compatibility with KMS. The Newcons framework is > designed to improve layering in the console. The machine-dependent > part simply provides a framebuffer interface, the machine-independent > part provides the terminal emulator (this also means things like > unicode in the console will work, as will higher-resolution consoles). > It's currently used on a few non-x86 platforms, but it wasn't a > priority for x86 because the PC BIOS text console mostly works and > people who want a better terminal can just run X. It's now become a > priority because of the KMS integration with X.org. Once this work is > completed, we will switch to a new X.org by default and will use the > KMS interface within the kernel for selecting the video mode. Is there a rough ETA for this great improvement? pgpMtvFbLgogf.pgp Description: PGP signature
Re: No SD card Reader support
On Wed, Jul 03, 2013 at 10:25:18AM +, Miguel Clara wrote: > Looking into the INI and readme files I see: " Realtek USB 2.0 Card Reader > ". so its connected via USB 2.0 > > To be honest I never used usbconfig more than "usbconfig list". > > is there anything I can try with usbconfig that would help me get the card > reader to work? Then it should be shown with usbconfig if not, your best chance is to ask on u...@freebsd.org for help. pgpcBxW5tvZK6.pgp Description: PGP signature
Re: error: unknown warning group '-Wcpp', ignored (#pragma GCC)
On Sat, May 25, 2013 at 12:14:03PM +0200, Niclas Zeising wrote: > On 05/25/13 12:09, O. Hartmann wrote: > > With CLANG on FreeBSD 10.0-CURRENT r250968, I get this error message in > > a source I try to port. > > > > I did not find any suitable "official" workaround and I'd like to avoid > > patching all files containing those #pragma statements. Is there a > > geenral solution on FreeBSD to overcome this? > > > > error: unknown warning group '-Wcpp', ignored > > [-Werror,-Wunknown-pragmas] > > # pragma GCC diagnostic ignored "-Wcpp" > > > > You could always remove -Werror or -Wunknown-pragmas from CFLAGS. Or > add -Wno-unknown-pragmas if -Wunknown-pragmas is turned on by -Wall or > something like that. > Regards! Just build with -DNO_WERROR. pgpASaZU1PVUw.pgp Description: PGP signature
Re: head && auditdistd
On Tue, May 14, 2013 at 10:24:52AM +0200, Matthias Apitz wrote: > El día Tuesday, May 14, 2013 a las 10:05:59AM +0200, Gary Jennejohn escribió: > > > > 2013/5/14 Matthias Apitz > > > > > > > > > > > # pw useradd -n auditdistd -g audit -c "Auditdistd unprivileged user" -d > > > > /var/empty -s /usr/sbin/nologin > > > > > > > > Can someone bring a bit light into this? Thanks in advance > > > > > > > > auditdistd:*:78:77:Auditdistd unprivileged user:/var/empty:/usr/sbin/nologin > > > > Just copy this line and paste it using vipw. > > Gary, > You have given already known information; can you guve some background, > for example for what the user is used for? thx > https://wiki.freebsd.org/auditdistd pgplB87AweXCe.pgp Description: PGP signature
Re: ipfilter(4) needs maintainer
On Sun, Apr 14, 2013 at 07:55:21PM +0100, Joe Holden wrote: > wishmaster wrote: > > > --- Original message --- > > From: "Gary Palmer" > > Date: 14 April 2013, 19:06:59 > > > > > >> On Sun, Apr 14, 2013 at 09:48:33AM -0600, Warren Block wrote: > >>> Is it possible to move ipfilter into a port? > >> That may work short term, but the ENOMAINTAINER problem will quickly creep > >> up again as kernel APIs change. If the author has lost interest in > >> maintaining the FreeBSD port of ipfilter then unless someone steps forward > >> to carry on the work, I don't see much of a future for ipfilter in > >> FreeBSD > >> > >> Do we honestly need three packet filters? > > > > Yes! This is the most clever thought in this thread. Why we need > > 3 firewalls? Two packet filters it's excess too. > > We have two packet filters: one with excellent syntax and > > functionality but with outdated bandwidth control mechanism > > (aka ALTQ); another - with nice traffic shaper/prioritization > > (dummynet)/classification (diffused) but with complicated > > implementation in not trivial tasks. > > May be the next step will be discussion about one packet filter in the > > system?.. > > > > Cheers, > For non-nat ipfw is still superior in every way, numbered rules (think: > scripts), dummynet, much faster than pf, syntax is a lot nicer and > predictable... > > Does anyone even use ipf? it doesn't even work on Linux anymore, junk it > and keep pf+ipfw, job done. m0n0wall uses ipfilter: http://m0n0.ch/wall/facts.php pgpHApUzGDDwu.pgp Description: PGP signature
Re: system 20% busy at all times?
On Tue, Feb 19, 2013 at 12:12:32PM +, Eggert, Lars wrote: > Hi, > > thanks for looking into this! > > On Feb 19, 2013, at 12:14, Andriy Gapon wrote: > > Please try to run the following DTrace script (dtrace -s script-file) and > > capture its output. > > I get this error: > > # dtrace -s x > dtrace: failed to compile script x: "/usr/lib/dtrace/psinfo.d", line 90: > failed to resolve type kernel`struct thread * for identifier curthread: > Module is no longer loaded > > (New to dtrace, so no clue what this means.) You need to recompile your Kernel to use DTrace: https://wiki.freebsd.org/DTrace The other Lars :) pgpcWfuHeIgaQ.pgp Description: PGP signature
Re: 7+ days of dogfood
On Mon, Feb 11, 2013 at 01:17:41PM +0100, Fabian Keil wrote: > Erich Dollansky wrote: > > > On Mon, 11 Feb 2013 11:48:11 +0100 > > Fabian Keil wrote: > > > > It's unfortunate that the builworld time roughly trippled since > > > 2010 but I guess that's progress and a more powerful system > > > should fix it. I certainly welcome clang in general, though. > > > > > Trippled? Are you sure? I have the feeling it is much worse than this. > > I'm sure it depends on lots of factors and our worlds probably > don't even match. > > I intend to eventually plot the numbers I've collected over the years > (mainly to have a baseline for ZFS tuning) but so far I haven't and > just looked at the first and last ones: > > -- > >>> Kernel build for ZOEY completed on Mon May 31 17:18:12 CEST 2010 > -- > > real10m42.935s > user8m16.834s > sys 1m22.951s > -- > >>> World build completed on Mon May 31 18:38:59 CEST 2010 > -- > > real71m16.524s > user51m55.771s > sys 12m24.944s > > # FreeBSD r500.local 10.0-CURRENT FreeBSD 10.0-CURRENT #543 r+b74c91e: Sun > Feb 3 17:17:03 CET 2013 fk@r500.local:/usr/obj/usr/src/sys/ZOEY amd64 > -- > >>> World build completed on Tue Feb 5 21:33:55 CET 2013 > -- > > real 261m25.904s > user 189m2.690s > sys 22m46.777s > > # FreeBSD r500.local 10.0-CURRENT FreeBSD 10.0-CURRENT #547 r+21d959a: Sun > Feb 10 16:00:14 CET 2013 fk@r500.local:/usr/obj/usr/src/sys/ZOEY amd64 > -- > >>> Kernel build for ZOEY completed on Sun Feb 10 21:41:31 CET 2013 > -- > > real 18m34.822s > user 12m13.900s > sys 2m14.028s > > fk@r500 ~ $expr 261 / 71 > 3 > > I agree that it "feels" worse, though. > > Disclaimer: These aren't "benchmark" results, I didn't create them in > single-user mode and various relevant factors vary. I also didn't run > the numbers through ministat and don't intend to either. > > > Was it in 2009 when I could compile world in a few minutes on my quad > > core. The same machine takes now hours despite having more memory. > > I'm using a Core(TM)2 Duo CPU T5870 @ 2.00GHz and don't remember > ever being able to compile world in a few minutes. The bottle > neck on my system seems to be the puny 2 GB of RAM the linker > has to share with ZFS. > > At least I can still buildworld without first attaching an USB > stick for additional swap space which is necessary for Firefox ... I also dislike that src build times increased over the years since I run CURRENT on my notebooks (starting 7-CURRENT, now 10-CURRENT). Wouldn't it be possible to add a DO_NOT_BUILD_CLANG_AND_GCC_IF_NOTHING_CHANGED= yes switch to src.conf? Building clang takes ages and gcc is also pretty big... pgpcnKaD8bz2Q.pgp Description: PGP signature
Re: mounting ntfs partition
On Mon, Oct 22, 2012 at 12:50:36AM +0100, Attilio Rao wrote: > On Sun, Oct 21, 2012 at 11:10 PM, Raoul MEGELAS wrote: > > On Sun, 21 Oct 2012 22:58:00 +0100 > > Attilio Rao wrote: > > > > On Sun, Oct 21, 2012 at 10:55 PM, Raoul MEGELAS wrote: > >> On Sun, 21 Oct 2012 22:07:36 +0100 > >> Attilio Rao wrote: > >> > >>>On 10/21/12, Raoul MEGELAS wrote: > On Sun, 21 Oct 2012 14:04:46 +0100 > Attilio Rao wrote: > Hi Attilio, > > > > On Sun, Oct 21, 2012 at 12:53 PM, Raoul wrote: > > Hi, > >> > >> Trying to mount a partition from type ntfs > >> with the following conditions i get: > >> > >> R241700, with fusefs-libs in sync. > >> > >> kldload fuse > >> fuse loaded > >> mount -t ntfs /dev/daXsX > >> not supported! > >> mount_ntfs /dev/daXsX > >> no such file or directory! > >> > >> in the second case, truss will report: > >>sysctl "", ... > >> which mean that the path is empty of course. > >> > >> Perhaps i miss something??? > > > >Try > > > > ntfs-3g /dev/daXsX /mnt/ntfs/ > > ntfs-3g crashes in the following environment: > mac x86/64 hardware, running an external usb drive with a freebsd > partition > (da0s3; > da1s1 da1s2 = ntfs partitions. > and even if it mounts fine the first read/rwrite panic. > > >> > >> > and now i investigated a little more. > >>> > >>> BTW, are you using the imported new FUSE module from stock kernel? > >>>I think that fusefs-ntfs will install fusefs-kmod port which must not > >>>happen now. > >> > >> > >>>Please make sure to use the stock FUSE support present in -CURRENT > >>>(which means reinstalling kernel and world appropriately). > >> > >> if CURRENT R241700 has the good one as UPDATING said, i have it. > >> > >> mount.c is dated October 18. > >> other files in the same directory: February. > > > >> Yes but did you rebuild world and install it? > >> Is your kernel using FUSE support from the kernel config? (and not > >> from the fusefs-kmod port) > > > > yes: > > deinstall fusefs-ntfs > > deinstall fusefs-kmod > > > > svn update > > make buildworld > > no error > > build kernel > > no error > > mergemaster! > > all this on October 18: R241700 > > > > i rebuilt mount from /usr/src/head/sbin/mount just now, and mount_ntfs, > > with the same result. > > mount_ntfs has no play here. It is a remnant of the in-kernel support > for NTFS and it is not used at all. > You need to install fusefs-ntfs and use ntfs-3g the way I showed you. Can mount_ntfs print a warning to use ntfs-3g if it's called in CURRENT? pgpyzRWBb1KnX.pgp Description: PGP signature
Re: FreeBSD in Google Code-In 2012? You can help too!
On Tue, Oct 23, 2012 at 03:59:07PM -0400, Eitan Adler wrote: > On 23 October 2012 12:54, David Magda wrote: > > On Tue, October 23, 2012 10:39, Fbsd8 wrote: > >> > >> The subject is Google Code-In and all the posted tasks are directed at > >> creating documentation. Not one deals with coding any programs. If I was > >> 15-17 years old I sure would not be interested in writing documentation. > >> I would want to use and develop my coding skills. To that end there a > >> lot of simple PR's waiting for attention. This is an target area that > >> young coders would find more interesting. > > > > It would depend on what one's interests were. > > Google code-in is aimed at *coders* and there is an expectation of > people writing *code*. > > The biggest complaint for GCI last year was "not enough coding tasks" What about creating a new port? That is some kind of coding. If we can find some software that isn't ported, yet and not too hard to port (e.g. the wanted ports page in the wiki) we could make a task proposal of it. And one generic "create a port for a piece of software that hasn't been ported, yet". Feel free to add me as a mentor for such a task. pgpt88V1lHWFb.pgp Description: PGP signature
Re: Clang as default compiler November 4th
On Wed, Sep 12, 2012 at 04:15:20AM -0500, Mark Linimon wrote: > On Tue, Sep 11, 2012 at 11:27:50AM +0200, Lars Engels wrote: > > At the moment the ports maintainers don't give much about if their ports > > build with CLANG or not because they're not forced to. > > I think this is a mis-representation. > > Adding the requirement "your ports must work on clang" is adding an > ex-post-facto requirement. This creates the following matrix of what > we are implicitly asking maintainers to do: > > (FreeBSD 7|8|9|10) * (amd64|arm|i386|powerpc|sparc64) * (base gcc|base clang) > > It is completely insane to expect anyone to be able to test in all of those > environments, or even a tiny subset of them. This isn't what most people > sign up for when they sign up to maintain ports. No, I didn't mean it that way. I only meant that the people / maintainers running CURRENT will actually see that their ports don't work and if they want to keep on using them on CURRENT they need to fix them. e.g. two of the ports I maintain don't build with CLANG, yet. I just checked that on the wiki page [1]. I had to look that up manually, but would have experienced that if I my CURRENT box was building with CLANG by default. :) It's clear that we cannot expect our maintainers to check all possible combinations of FreeBSD, architecture and compiler. > > > Those who don't run CURRENT won't notice, but those who do will have to > > get their butts up and fix the ports > > I think it's foolish to assume that maintainres don't have their butts in > gear as it is. Please note, we have nearly 1300 PRs, hundreds of ports with > build errors and/or PRs, and hundreds that fail on -current only. I try to > advertise all these things the best I know how. Adding the hundreds that > fail on -clang only and then blaming the maintainers is simply going to be > counter-productive. [1] http://wiki.freebsd.org/PortsAndClang pgpYzIi4erNuX.pgp Description: PGP signature
Re: Clang as default compiler November 4th
On Mon, Sep 10, 2012 at 10:54:04PM -0700, Doug Barton wrote: > As of last week, 4,680 ports out of 23,857 failed to build with clang on > 9-amd64. That's almost a 20% failure rate. Until we have better support > for either building ports with clang, or have better support for the > idea of a "ports compiler," this change is premature. The ports are an > important part of the FreeBSD Operating _System_, and pulling the > trigger on the default compiler before the ports problems are addressed > robustly seems like a big fat FU. > > That said, I agree that this issue needs to be addressed. In fact, 9 > months before the release of 9.0 I said on the internal committers list > that there was no point in making a new release until we had thoroughly > addressed both the default compiler for the base, and resolving the > "ports compiler" issue. While there has been some movement on the > former, there has been nothing done on the latter for years now, even > though everyone agrees that it is an important issue. > > I'd like to request that rather than moving the default compiler > prematurely that you call for volunteers to address the problems with > the ports. Both the issues of fixing more ports to build correctly with > clang, and the issue of defining a "ports compiler" version of gcc (and > appropriate infrastructure) for those that can't. Once those issues are > resolved there would not be any further obstacles to moving the default. > Until they are, the change is premature. > > Doug Doug, as you can already use CLANG instead of GCC now, you will be able to use GCC instead of CLANG after November 4th. At the moment the ports maintainers don't give much about if their ports build with CLANG or not because they're not forced to. Those who don't run CURRENT won't notice, but those who do will have to get their butts up and fix the ports, so 10.0 can have 99% of all ports build with CLANG and even 8.x and 9.x can already profit from having the broken ports fixed now. pgpUPRRZ1NomD.pgp Description: PGP signature
Re: Script to monitor battery status on X220
On Fri, Jul 20, 2012 at 10:04:59AM +0700, Erich Dollansky wrote: > Hi, > > I forget yesterday to share these two scripts: > > http://www.alogreentechnologies.com/freebsd/checkbattery > > checks the battery status of an X220 and shuts the machine down when the > battery falls to 2% or below. > > The status is checked every minute. > > It calls the following script to shut the machine down: > > http://www.alogreentechnologies.com/freebsd/poweroff > > You must run the first script as root to enable it to power the machine off > at the end. > > I found that the battery life of my machine was higher using a simple window > manager like blackbox compared to things like GNOME or KDE. This might depend > on the usage pattern. > > Erich Is it necessary to poll? Usually devd generates an event when the battery status and/or percentage changes. Just read the events from /var/run/devd.pipe. pgpRm1QE6KzxZ.pgp Description: PGP signature
Re: PAM passwdqc, strict aliasing, and WARNS
On Sun, Jul 15, 2012 at 12:09:17AM +0200, Dag-Erling Smørgrav wrote: > "Justin T. Gibbs" writes: > > Someone who has yet to confess added -Werror to the global CFLAGS > > (via /etc/make.conf) for one of our systems at work. Before I > > figured out that this was the cause of builds failing, I hacked up > > pam_passwdc to resolve the problem. This gets the module to > > WARNS=2, but to go farther, the "logically const" issues with this > > code will need to be sorted out. > > > > Is this change worth committing? Is this the best way to resolve > > the strict aliasing issues in this code? > > I really don't like that sort of game. If you look at other PAM > consumer code, you'll see that the common idiom is what Jilles > suggested, i.e. use a temporary variable of the appropriate type. > > That being said, pam_passwdqc should probably be either updated or > removed. The version we have is ten years old. But it still works... pgpHVgPH4UfGi.pgp Description: PGP signature
Re: Reproducible panic on "kldunload i915kms" as of r236822
On Mon, Jun 11, 2012 at 12:19:08PM +0300, Konstantin Belousov wrote: > On Sun, Jun 10, 2012 at 10:00:09AM -0400, Ed Maste wrote: > > I'm running CURRENT as of r236822 on my Thinkpad X220 and am starting > > to experiment with the i915 kms driver. All packages are from the > > pkgbeta repo; I haven't rebuilt anything yet. I have > > xorg-server-1.7.7_5,1 and the vesa driver gets used. In this > > configuration I have a reproducible panic unloading i915kms.ko. > > > > Reproduction steps: > > > > 1. kldload i915kms && startx > > 2. switch back to the text console > > 3. ^C the x server > > 4. kldunload i915kms > > Yes, unloading of i915kms does not work. There is much more issues > then what you reported. I do not consider this very critical, and > have more urgent items to handle, sorry. If that's a known error maybe kldunload should return ENODEV to prevent a user from unnecessarily panicking his system? pgpfJIZLkuHHd.pgp Description: PGP signature
Re: 9-stable regression: 'cbb0: Warning: Bus reset timeout'
On Fri, May 25, 2012 at 09:52:15AM -0700, Adrian Chadd wrote: > To respond to my own mail again: > > * should the cardbus slot peripherals be detached and reattached upon > resume? Or should it be just suspend/resumed? > * here's what I see during suspend: > > > wlan1: link state changed to DOWN > [100741]: ieee80211_reset_bss: iv_bss=0xc969e000, new iv_bss=0xc96a5000 > [100480] cbb0: Opening memory: > [100480] ath1: detached > pci0:21:0:0: Transition from D0 to D2 > [100480] pci21: failed to set ACPI power state D2 on > \\_SB_.PCI0.PCI1.CDBS: AE_BAD_PARAMETER > [100480] vga0: saving 4612 bytes of video state > [100480] vga0: saving color palette > [100480] pci0: failed to set ACPI power state D2 on \\_SB_.PCI0.EXP0: > AE_BAD_PARAMETER > [100480] pci0: failed to set ACPI power state D2 on \\_SB_.PCI0.EXP1: > AE_BAD_PARAMETER > [100480] pci0: failed to set ACPI power state D2 on \\_SB_.PCI0.EXP2: > AE_BAD_PARAMETER > [100480] pci0: failed to set ACPI power state D2 on \\_SB_.PCI0.EXP3: > AE_BAD_PARAMETER > > .. would someone with some ACPI clue please help me figure out how > broken the ACPI code in my T60 BIOS is? :) I am also seeing this on my Thinkpad X200 running 10-CURRENT amd64: pci0: failed to set ACPI power state D2 on \\_SB_.PCI0.EXP0: AE_BAD_PARAMETER pci0: failed to set ACPI power state D2 on \\_SB_.PCI0.EXP1: AE_BAD_PARAMETER pci0: failed to set ACPI power state D2 on \\_SB_.PCI0.EXP3: AE_BAD_PARAMETER CPU0: local APIC error 0x40 pgpYyZNyHj5VO.pgp Description: PGP signature
Re: Status on X220
On Thu, Apr 19, 2012 at 08:17:55PM -0700, Kevin Oberman wrote: > > Minor note. Sound card seems to work OK through the speakers, but I > have failed to find the magic to make the headphone jack work. This is the same for my x200, but you can make it work: On 9.0-RELEASE you have to configure through device.hints(5), in CURRENT you can configure it on thy fly. See snd_hda(4) how to do this. pgpcTuFJtlc4C.pgp Description: PGP signature
Re: [HEADSUP] pkgng 1.0-beta9 please test
On Fri, Mar 30, 2012 at 11:12:42AM +0200, Baptiste Daroussin wrote: > Hi, > > On behalf of pkgng crew, I'm happy to announce pkg 1.0-beta9 > [...] > Please note that normally this will be the last beta version, So we can expect an official package repository with the first RC? pgptOzA777NGx.pgp Description: PGP signature
Re: [PATCH] ACPI object refcount fix
Andreas Tobler schrieb: On 28.03.12 00:13, Jung-uk Kim wrote: > The upstream maintainer just e-mailed me a possible fix for the > problem and it looks very promising. Please try the attached patch. > Note the patch reverts r233555 and applies the fix. This patch is > also available from here: > > http://people.freebsd.org/~jkim/acpi_refcnt.diff > > Thanks! Thank you very much, T60 is up and running! Gruss, Andreas Yup, works for me, too. Thanks a lot :-) ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"
[ACPI] panic on battery insertion since last ACPI update
With yesterday's CURRENT (r233364) the system panics when I insert the battery
into the notebook.
milhouse.bsd-geek.de dumped core - see /var/crash/vmcore.0
Sat Mar 24 22:26:15 CET 2012
FreeBSD milhouse.bsd-geek.de 10.0-CURRENT FreeBSD 10.0-CURRENT #1 r233364M: Fri
Mar 23 17:48:19 CET 2012
l...@milhouse.bsd-geek.de:/usr/obj/usr/src/sys/GENERIC amd64
panic: from debugger
GNU gdb 6.1.1 [FreeBSD]
Copyright 2004 Free Software Foundation, Inc.
GDB is free software, covered by the GNU General Public License, and you are
welcome to change it and/or distribute copies of it under certain conditions.
Type "show copying" to see the conditions.
There is absolutely no warranty for GDB. Type "show warranty" for details.
This GDB was configured as "amd64-marcel-freebsd"...
Unread portion of the kernel message buffer:
Fatal trap 9: general protection fault while in kernel mode
cpuid = 0; apic id = 00
instruction pointer = 0x20:0x80320160
stack pointer = 0x28:0xff8116346690
frame pointer = 0x28:0xff81163466b0
code segment= base 0x0, limit 0xf, type 0x1b
= DPL 0, pres 1, long 1, def32 0, gran 1
processor eflags= interrupt enabled, resume, IOPL = 0
current process = 2488 (hald)
Uptime: 31s
Dumping 350 out of 3970 MB:
Loaded symbols for /boot/kernel/ext2fs.ko
#0 doadump (textdump=1) at /usr/src/sys/kern/kern_shutdown.c:268
268 if (textdump && textdump_pending) {
(kgdb) #0 doadump (textdump=1) at /usr/src/sys/kern/kern_shutdown.c:268
#1 0x8086e2bf in kern_reboot (howto=260)
at /usr/src/sys/kern/kern_shutdown.c:454
#2 0x8086e797 in panic (fmt=0x0)
at /usr/src/sys/kern/kern_shutdown.c:642
#3 0x80328c67 in db_panic (addr=Variable "addr" is not available.
)
at /usr/src/sys/ddb/db_command.c:482
#4 0x80329071 in db_command (last_cmdp=0x811560a0,
cmd_table=dwarf2_read_address: Corrupted DWARF expression.
) at /usr/src/sys/ddb/db_command.c:449
#5 0x803292c0 in db_command_loop ()
at /usr/src/sys/ddb/db_command.c:502
#6 0x8032b3f9 in db_trap (type=Variable "type" is not available.
) at /usr/src/sys/ddb/db_main.c:229
#7 0x808a4b58 in kdb_trap (type=9, code=0, tf=0xff81163465e0)
at /usr/src/sys/kern/subr_kdb.c:629
#8 0x80b6729d in trap_fatal (frame=0xff81163465e0, eva=Variable
"eva" is not available.
)
at /usr/src/sys/amd64/amd64/trap.c:833
#9 0x80b67825 in trap (frame=0xff81163465e0)
at /usr/src/sys/amd64/amd64/trap.c:597
#10 0x80b5224f in calltrap ()
at /usr/src/sys/amd64/amd64/exception.S:228
#11 0x80320160 in AcpiOsAcquireObject (Cache=0xfe00028c9940)
at /usr/src/sys/contrib/dev/acpica/components/utilities/utcache.c:319
#12 0x80322f62 in AcpiUtAllocateObjectDescDbg (
ModuleName=0x80c0c2c0 "exoparg2", LineNumber=398,
ComponentId=Variable "ComponentId" is not available.
)
at /usr/src/sys/contrib/dev/acpica/components/utilities/utobject.c:437
#13 0x80322fc1 in AcpiUtCreateInternalObjectDbg (
ModuleName=0x80c0c2c0 "exoparg2", LineNumber=398,
ComponentId=128, Type=20)
at /usr/src/sys/contrib/dev/acpica/components/utilities/utobject.c:112
#14 0x8030fbb8 in AcpiExOpcode_2A_1T_1R (WalkState=0xfe0002d1dc00)
at /usr/src/sys/contrib/dev/acpica/components/executer/exoparg2.c:398
#15 0x80306453 in AcpiDsExecEndOp (WalkState=0xfe0002d1dc00)
at /usr/src/sys/contrib/dev/acpica/components/dispatcher/dswexec.c:475
#16 0x80319f1c in AcpiPsParseLoop (WalkState=0xfe0002d1dc00)
at /usr/src/sys/contrib/dev/acpica/components/parser/psloop.c:1249
#17 0x8031aa6d in AcpiPsParseAml (WalkState=0xfe0002d1dc00)
at /usr/src/sys/contrib/dev/acpica/components/parser/psparse.c:525
#18 0x8031b74d in AcpiPsExecuteMethod (Info=0xfe0049063600)
at /usr/src/sys/contrib/dev/acpica/components/parser/psxface.c:368
#19 0x80315012 in AcpiNsEvaluate (Info=0xfe0049063600)
at /usr/src/sys/contrib/dev/acpica/components/namespace/nseval.c:193
#20 0x80318511 in AcpiEvaluateObject (Handle=0xfe0002c6f040,
Pathname=0x80c198db "_BST", ExternalParams=0x0,
ReturnBuffer=0xff8116346920)
at /usr/src/sys/contrib/dev/acpica/components/namespace/nsxfeval.c:289
#21 0x803407ad in acpi_cmbat_get_bst (arg=Variable "arg" is not
available.
)
at /usr/src/sys/dev/acpica/acpi_cmbat.c:258
#22 0x80340ab8 in acpi_cmbat_bst (dev=0xfe0002cf6800,
bstp=0xfe00132bbc00) at /usr/src/sys/dev/acpica/acpi_cmbat.c:419
#23 0x8078a1cb in devfs_ioctl_f (fp=0xfe0049257140,
com=3231990289, data=Variable "data" is not available.
) at /usr/src/sys/fs/devfs/devfs_vnops.c:757
#24 0x808b7e75 in kern_ioctl (td=Variable "td" is not available.
) at file.h:287
#25 0x808b80ad in sys_ioctl (td=0xf
Re: -CURRENT is broken?
On Tue, Mar 06, 2012 at 12:50:43AM -0600, Doug Barton wrote: > On 3/5/2012 1:53 PM, Lars Engels wrote: > > Yes, I have this in libmap.conf: > > libpcre.so.0 libpcre.so.1 > > It would be much better to just put the old pcre.0 in > /usr/local/lib/compat/pkg until you've updated everything linked to it. Yes, I know, but I forgot the -w option to portmaster. :) pgpxXwWFcJfiw.pgp Description: PGP signature
Re: -CURRENT is broken?
On Mon, Mar 05, 2012 at 12:20:38PM -0800, Jos Backus wrote: > On Mon, Mar 5, 2012 at 12:07 PM, Konstantin Belousov > wrote: > > The following change fixes ld-elf.so.1 with the present libmap.conf for me. > [snip] > > Thanks Kostik, I'm running a `make world' with your patch now. It > didn't apply cleanly but it was clear that the idea was to replace all > calls to isspace() with the added isspace1() macro and not use > ctypes.h. Had the same problem applying the patch, but after manual editing and buildworld, installworld worked fine. Problem fixed, thanks a lot. :) pgpHkJd46QaF4.pgp Description: PGP signature
Re: -CURRENT is broken?
On Mon, Mar 05, 2012 at 09:51:19PM +0200, Konstantin Belousov wrote:
> On Mon, Mar 05, 2012 at 08:43:15PM +0100, Lars Engels wrote:
> > On Mon, Mar 05, 2012 at 09:27:49PM +0200, Konstantin Belousov wrote:
> > > On Mon, Mar 05, 2012 at 08:16:22PM +0100, Lars Engels wrote:
> > > > On Mon, Mar 05, 2012 at 09:12:11PM +0200, Konstantin Belousov wrote:
> > > > > On Mon, Mar 05, 2012 at 10:41:01AM -0800, Jos Backus wrote:
> > > > > > On Mon, Mar 5, 2012 at 10:10 AM, Lars Engels
> > > > > > wrote:
> > > > > > > On Mon, Mar 05, 2012 at 07:41:32PM +0400, Alex Keda wrote:
> > > > > > >> On 05.03.2012 19:39, Alex Keda wrote:
> > > > > > >> > I have 2 machine, i386 and amd64
> > > > > > >> > world rebuild tonight all work. all applications crash with
> > > > > > >> > core dump...
> > > > > > >> read as "world rebuild tonight not work" =))
> > > > > >
> > > > > > I noticed the same thing. My `make world' dies right after
> > > > > > installing
> > > > > > the new runtime linker. I was able to recover by copying
> > > > > > ld-elf.so.1.old using /rescue/{chflags,cp}. Oddly enough, when I
> > > > > > manually build and install the runtime linker, it works. Maybe
> > > > > > that's
> > > > > > a clue as to what's wrong.
> > > > >
> > > > > I just did full buildworld on pristine sources at r232541 and amd64
> > > > > machine
> > > > > booted fine.
> > > > >
> > > > > Can somebody put the faulting ld-elf.so.1 somewhere so I can download
> > > > > it ?
> > > >
> > > > http://bsd-geek.de/FreeBSD/ld-elf.so.1
> > >
> > > It works for me :(.
> > >
> > > Since your rtld is not stripped, try to link any binary using this
> > > interpreter,
> > > i.e. supply -Wl,-I, to cc link command.
> > > Then run the program, get core dump, load it into gdb and do "bt all".
> >
> > "bt all" gives "No symbol table is loaded. Use the "file" command."
> >
> > But just "bt" gives:
> >
> > http://bsdpaste.bsdgroup.de/130927
> Hm, so do you have libmap.conf ?
>
> Yeah, it faults immediately.
> I suspect I know what is going on.
>
Yes, I have this in libmap.conf:
libpcre.so.0 libpcre.so.1
pgpwPr3bJ2JBt.pgp
Description: PGP signature
Re: -CURRENT is broken?
On Mon, Mar 05, 2012 at 09:27:49PM +0200, Konstantin Belousov wrote:
> On Mon, Mar 05, 2012 at 08:16:22PM +0100, Lars Engels wrote:
> > On Mon, Mar 05, 2012 at 09:12:11PM +0200, Konstantin Belousov wrote:
> > > On Mon, Mar 05, 2012 at 10:41:01AM -0800, Jos Backus wrote:
> > > > On Mon, Mar 5, 2012 at 10:10 AM, Lars Engels
> > > > wrote:
> > > > > On Mon, Mar 05, 2012 at 07:41:32PM +0400, Alex Keda wrote:
> > > > >> On 05.03.2012 19:39, Alex Keda wrote:
> > > > >> > I have 2 machine, i386 and amd64
> > > > >> > world rebuild tonight all work. all applications crash with core
> > > > >> > dump...
> > > > >> read as "world rebuild tonight not work" =))
> > > >
> > > > I noticed the same thing. My `make world' dies right after installing
> > > > the new runtime linker. I was able to recover by copying
> > > > ld-elf.so.1.old using /rescue/{chflags,cp}. Oddly enough, when I
> > > > manually build and install the runtime linker, it works. Maybe that's
> > > > a clue as to what's wrong.
> > >
> > > I just did full buildworld on pristine sources at r232541 and amd64
> > > machine
> > > booted fine.
> > >
> > > Can somebody put the faulting ld-elf.so.1 somewhere so I can download it ?
> >
> > http://bsd-geek.de/FreeBSD/ld-elf.so.1
>
> It works for me :(.
>
> Since your rtld is not stripped, try to link any binary using this
> interpreter,
> i.e. supply -Wl,-I, to cc link command.
> Then run the program, get core dump, load it into gdb and do "bt all".
"bt all" gives "No symbol table is loaded. Use the "file" command."
But just "bt" gives:
http://bsdpaste.bsdgroup.de/130927
pgp1td2CR7bZX.pgp
Description: PGP signature
Re: -CURRENT is broken?
On Mon, Mar 05, 2012 at 09:12:11PM +0200, Konstantin Belousov wrote:
> On Mon, Mar 05, 2012 at 10:41:01AM -0800, Jos Backus wrote:
> > On Mon, Mar 5, 2012 at 10:10 AM, Lars Engels wrote:
> > > On Mon, Mar 05, 2012 at 07:41:32PM +0400, Alex Keda wrote:
> > >> On 05.03.2012 19:39, Alex Keda wrote:
> > >> > I have 2 machine, i386 and amd64
> > >> > world rebuild tonight all work. all applications crash with core
> > >> > dump...
> > >> read as "world rebuild tonight not work" =))
> >
> > I noticed the same thing. My `make world' dies right after installing
> > the new runtime linker. I was able to recover by copying
> > ld-elf.so.1.old using /rescue/{chflags,cp}. Oddly enough, when I
> > manually build and install the runtime linker, it works. Maybe that's
> > a clue as to what's wrong.
>
> I just did full buildworld on pristine sources at r232541 and amd64 machine
> booted fine.
>
> Can somebody put the faulting ld-elf.so.1 somewhere so I can download it ?
http://bsd-geek.de/FreeBSD/ld-elf.so.1
pgpGqc7aLvfsp.pgp
Description: PGP signature
Re: Can't boot with geom_part_(gpt|mbr|bsd|ebr)
On Fri, Mar 02, 2012 at 12:10:21PM +0400, Pavel Timofeev wrote: > "Kernel can't boot" is a common idea. > I did the tests for each geom_part and described it in PR. > > Some transcription: > boot stops (on usb detect) - boot stops, not hangs, you can push > Pause/Break and surf through system boot messages. > http://img-fotki.yandex.ru/get/5606/16519813.0/0_83860_a4bf85d_orig > > can't mount fs: > http://img-fotki.yandex.ru/get/6201/16519813.0/0_83861_e809a6e3_orig > > I'm sorry for bad photos. Obtained from 9.0R i386 I can confirm this. About 2 or 3 weeks ago I played around with a minimal kernel config and added the geom_*_load="YES" lines to loader.conf and had the same issue like Pavel. pgp5DriCvEoFA.pgp Description: PGP signature
