Re: lint errors in stable/11
On Thu, May 10, 2018 at 11:27 AM Ian Lepore <i...@freebsd.org> wrote: > On Thu, 2018-05-10 at 14:40 +0000, Rick Miller wrote: > > On Thu, May 10, 2018 at 8:23 AM Dimitry Andric <d...@freebsd.org> wrote: > > > > > > > > On 10 May 2018, at 12:47, Rick Miller <vrwmil...@gmail.com> wrote: > > > > > > > > > > > > On Thu, May 10, 2018 at 6:35 AM Rick Miller <vrwmil...@gmail.com> > wrote: > > > ... > > > > > > > > > > > > > > Performing a release build via release/release.sh in r331337 of > > > stable/11 > > > > > > > > > > > > > > errors citing the lack of lint. It’s understood lint was removed > from > > > > > stable/11 so src.conf includes WITHOUT_LINT, but errors persist. > As the > > > > > code review alludes to[1], lint is irrelevant here. It seems > > > WITHOUT_LINT > > > > > > > > > > > > > > may not be the only thing I’m looking for. What is the best > approach for > > > > > mitigating these errors? > > > > > > > > > > > > > > Here’s the error w/o email munging: > > > > > > > > ===> usr.bin/xlint/xlint (all) > > > > /data/dists/11.1.9.0-amd64-md/usr/src/contrib/apr/atomic/uni > > > > x/builtins.c:71:53: > > > > warning: passing 'const void *' to parameter of type 'volatile void > *' > > > > discards > > > > qualifiers [-Wincompatible-pointer-types-discards-qualifiers] > > > > > > > >return (void*) __sync_val_compare_and_swap(mem, cmp, with); > > > > > > > >^~~ > > > > > > > > 1 warning generated. > > > > > > > > ===> usr.bin/xlint/llib (all) > > > > > > > > sh: lint: not found > > > Are you building on a -CURRENT host? If so, see the previous mail > > > thread about this: > > > > > > > > > > https://lists.freebsd.org/pipermail/freebsd-stable/2017-November/088092.html > > > > > > and https://bugs.freebsd.org/223892. > > > > > > No, the build system is stable/11 r331337 building releng/11.1. The > build > > system doesn’t include ‘lint’: > > > > # echo $PATH > > /sbin:/bin:/usr/sbin:/usr/bin:/usr/local/sbin:/usr/local/bin:/root/bin > > # which lint > > lint: Command not found. > > > > The mail thread and bug refer to building stable/11 on current where this > > case is building releng/11.1 on stable/11. They also do not appear to > > provide actionable information on mitigating errors though the code > > commit[1] suggests installing a lint will resolve. Ports doesn’t seem to > > contain a suitable replacement however. Can lint still be installed on > the > > build system from the stable/11 source? If so, how is that accomplished? > > > > Do WITH/WITHOUT_LINT have any impact here? The source has been built with > > WITH_LINT and WITHOUT_LINT to the same result except that xlint either > > builds or doesn’t depending on the option. > > > > This all seems to originate with llib’s dependency on lint as described > in > > the email thread. It is in building llib where the error occurs. > > > > [1] https://reviews.freebsd.org/D13799 > > > > -Rick > > Releng/11.1 is cast in stone; as I understand it, only security fixes > can get merged into release branches, so the fix I did that added > WITH/WITHOUT_LINT isn't on that branch and never will be. That means > lint has to exist on the build system. If your build system is 11- > stable, then add WITH_LINT=yes to your /etc/src.conf, build and install > world, then that 11-stable system should be able to build the releng > branch. Unfortunately, no such option exists for people trying to build > on 12, because lint was removed completely (although it might be > possible to install a lint port, I'm not sure about that). > Thanks for the information! src.conf now includes WITH_LINT=“YES” and buildworld succeeds and produces the ‘xlint’ that ultimately is installed via installworld: # grep LINT /etc/src.conf WITH_LINT="YES" # pwd /usr/obj/usr/src/usr.bin # find . -name '*lint' -type f ./xlint/xlint/xlint # Observe below in this error where ‘xlint’ is installed as /usr/bin/lint, but installworld still fails citing lint is not found. Creating symlink /usr/bin/lint to /usr/bin/true seemed to have no impact on results. ===> usr.bin/xlint (install) ===> usr.bin/xlint/lint1 (install)
Re: lint errors in stable/11
On Thu, May 10, 2018 at 8:23 AM Dimitry Andric <d...@freebsd.org> wrote: > On 10 May 2018, at 12:47, Rick Miller <vrwmil...@gmail.com> wrote: > > > > On Thu, May 10, 2018 at 6:35 AM Rick Miller <vrwmil...@gmail.com> wrote: > ... > >> Performing a release build via release/release.sh in r331337 of > stable/11 > >> errors citing the lack of lint. It’s understood lint was removed from > >> stable/11 so src.conf includes WITHOUT_LINT, but errors persist. As the > >> code review alludes to[1], lint is irrelevant here. It seems > WITHOUT_LINT > >> may not be the only thing I’m looking for. What is the best approach for > >> mitigating these errors? > >> > >> > > Here’s the error w/o email munging: > > > > ===> usr.bin/xlint/xlint (all) > > /data/dists/11.1.9.0-amd64-md/usr/src/contrib/apr/atomic/uni > > x/builtins.c:71:53: > > warning: passing 'const void *' to parameter of type 'volatile void *' > > discards > > qualifiers [-Wincompatible-pointer-types-discards-qualifiers] > > > >return (void*) __sync_val_compare_and_swap(mem, cmp, with); > > > >^~~ > > > > 1 warning generated. > > > > ===> usr.bin/xlint/llib (all) > > > > sh: lint: not found > > Are you building on a -CURRENT host? If so, see the previous mail > thread about this: > > > https://lists.freebsd.org/pipermail/freebsd-stable/2017-November/088092.html > > and https://bugs.freebsd.org/223892. > > No, the build system is stable/11 r331337 building releng/11.1. The build system doesn’t include ‘lint’: # echo $PATH /sbin:/bin:/usr/sbin:/usr/bin:/usr/local/sbin:/usr/local/bin:/root/bin # which lint lint: Command not found. The mail thread and bug refer to building stable/11 on current where this case is building releng/11.1 on stable/11. They also do not appear to provide actionable information on mitigating errors though the code commit[1] suggests installing a lint will resolve. Ports doesn’t seem to contain a suitable replacement however. Can lint still be installed on the build system from the stable/11 source? If so, how is that accomplished? Do WITH/WITHOUT_LINT have any impact here? The source has been built with WITH_LINT and WITHOUT_LINT to the same result except that xlint either builds or doesn’t depending on the option. This all seems to originate with llib’s dependency on lint as described in the email thread. It is in building llib where the error occurs. [1] https://reviews.freebsd.org/D13799 -Rick -- Take care Rick Miller ___ freebsd-stable@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
Re: lint errors in stable/11
On Thu, May 10, 2018 at 6:35 AM Rick Miller <vrwmil...@gmail.com> wrote: > Hi all, > > > > Performing a release build via release/release.sh in r331337 of stable/11 > errors citing the lack of lint. It’s understood lint was removed from > stable/11 so src.conf includes WITHOUT_LINT, but errors persist. As the > code review alludes to[1], lint is irrelevant here. It seems WITHOUT_LINT > may not be the only thing I’m looking for. What is the best approach for > mitigating these errors? > > Here’s the error w/o email munging: ===> usr.bin/xlint/xlint (all) /data/dists/11.1.9.0-amd64-md/usr/src/contrib/apr/atomic/uni x/builtins.c:71:53: warning: passing 'const void *' to parameter of type 'volatile void *' discards qualifiers [-Wincompatible-pointer-types-discards-qualifiers] return (void*) __sync_val_compare_and_swap(mem, cmp, with); ^~~ 1 warning generated. ===> usr.bin/xlint/llib (all) sh: lint: not found --- llib-lposix.ln --- *** [llib-lposix.ln] Error code 127 make[5]: stopped in /data/dists/11.1.9.0-amd64-md/usr/src/usr.bin/xlint/llib 1 error make[5]: stopped in /data/dists/11.1.9.0-amd64-md/usr/src/usr.bin/xlint/llib > [1] https://reviews.freebsd.org/D13799?id=37644 > -- Take care Rick Miller ___ freebsd-stable@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
lint errors in stable/11
Hi all, Performing a release build via release/release.sh in r331337 of stable/11 errors citing the lack of lint. It’s understood lint was removed from stable/11 so src.conf includes WITHOUT_LINT, but errors persist. As the code review alludes to[1], lint is irrelevant here. It seems WITHOUT_LINT may not be the only thing I’m looking for. What is the best approach for mitigating these errors? ===> usr.bin/xlint/xlint (all) /data/dists/11.1.9.0-amd64-md/usr/src/contrib/apr/atomic/unix/builtins.c:71:53: warning: passing 'const void *' to parameter of type 'volatile void *' discards qualifiers [-Wincompatible-pointer-types-discards-qualifiers] return (void*) __sync_val_compare_and_swap(mem, cmp, with); ^~~ 1 warning generated. ===> usr.bin/xlint/llib (all) sh: lint: not found --- llib-lposix.ln --- *** [llib-lposix.ln] Error code 127 make[5]: stopped in /data/dists/11.1.9.0-amd64-md/usr/src/usr.bin/xlint/llib 1 error make[5]: stopped in /data/dists/11.1.9.0-amd64-md/usr/src/usr.bin/xlint/llib [1] https://reviews.freebsd.org/D13799?id=37644 -- Take care Rick Miller ___ freebsd-stable@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
Re: FreeBSD 11.x fails to boot w/ SAS3 4Kn HDD and LSISAS3008 on SuperMicro X10DRH-iT
As it turns out, it seems EFI must be specified as the boot environment as opposed to legacy or BIOS+EFI. Setting the boot environment to EFI only resulted in successful system boot. Thanks for the replies. The answer came from Allan Jude on Twitter. On Mon, Mar 12, 2018 at 6:18 PM Rick Miller <vrwmil...@gmail.com> wrote: > Hi all, > > Thanks in advance to anyone that might be able to help. I subscribed to > freebsd-geom@ so that the list did not need to "reply-all". Having > trouble getting FreeBSD 11-STABLE @ r329011 to boot from SAS3 4Kn HDDs via > LSISAS 3008 HBA on a SuperMicro X10DRH-iT motherboard after an apparent > installation. All internal media (including all other disks attached to the > HBA) were removed to eliminate other storage being the reason the system > won't boot. This occurs specifically in CSM mode, but the preference is to > boot via UEFI mode instead. > > Anyway...booting the machine via the memstick image demonstrates the > LSISAS 3008 controller attaching via mpr(4) (whose manpage describes the > controller being supported[1]): > > mpr0@pci0:3:0:0: class=0x010700 card=0x080815d9 chip=0x00971000 rev=0x02 > hdr=0x00 > vendor = 'LSI Logic / Symbios Logic' > device = 'SAS3008 PCI-Express Fusion-MPT SAS-3' > class = mass storage > subclass = SAS > > The only inserted disk attaches as da0 as illustrated by dmesg: > > ses0: pass0,da0: Elemne t descriptor: 'Slot00' > da0 at mpr0 bus 0 scbus0 target 8 lun 0 > ses0: pass0,da0: SAS Device Slot Element: 1 Phys at Slot 0 > ses0: phy 0: SAS device type 1 id 0 > ses0: phy 0: protocols: initiator( None ) Target( SSP ) > ses0: phy 0: parent 500304801e870bff addr 5000c500a012814d > da0: Fixed Direct Access SPC-4 SCSI device > da0: Serial Number $serial_number > da0: 1200.000MB/s transfers > da0: Command queueing enabled > da0: 1907729MB (488378648 4096 byte sectors) > > The original goal was to boot via zfs root, but when that failed, > subsequent installations used the "Auto (UFS) option" to partition the > disk. For example, the first installation gpart'd the disk as: > > # gpart show da0 > =>6 488378635 da0 GPT (1.8T) > 6 128 1 freebsd-boot (512K) > 134 487325568 2 freebsd-ufs (1.8T) > 487325702 1048576 3 freebsd-swap (4.0G) > 4883742784363 - free - (17M) > > The result was a reboot loop. When the system reached the point of reading > the disk, it just rebooted and continued doing so. There was no loader or > beastie menu. Thus, thinking that it could be the partition layout > requirements of the 4Kn disks, it was gpart'd like the below[2][3]. This > was done by exiting to the shell during the partition phase of bsdinstall > and manually gpart'ing the disk according to the below, mounting da0p2 at > /mnt and placing an fstab at /tmp/bsdinstall_etc/fstab that included mount > entries for /dev/da0p2 at / and /dev/da0p3 as swap. > > # gpart show da0 > =>6 488378635 da0 GPT (1.8T) > 634 - free - (136K) > 40 512 1 freebsd-boot (2.0M) > 552 419430400 2 freebsd-ufs (1.6T) > 419430952 1048576 3 freebsd-swap (4.0G) > 42047952867899113 - free - (259G) > > When configured as such, the system rebooted at the completion of the > install and appeared to roll through the boot order, which specifies the > HDD first, then CD/DVD, then network. It did attempt to boot via network, > but is irrelevant here. > > All the hardware is alleged to be supported by FreeBSD as best I can tell > and OS installation apparently works. I'm at a loss as to why the OS won't > boot. Does someone have feedback or input that may expose why it doesn't > boot? > > FWIW, a RHEL7 install was also attempted, which also does not boot. > > [1] > https://www.freebsd.org/cgi/man.cgi?query=mpr=0=4=FreeBSD+11.1-RELEASE=default=html > [2] > https://lists.freebsd.org/pipermail/freebsd-hardware/2013-September/007380.html > [3] http://www.wonkity.com/~wblock/docs/html/disksetup.html > > -- > Take care > Rick Miller > -- Take care Rick Miller ___ freebsd-stable@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
FreeBSD 11.x fails to boot w/ SAS3 4Kn HDD and LSISAS3008 on SuperMicro X10DRH-iT
Hi all, Thanks in advance to anyone that might be able to help. I subscribed to freebsd-geom@ so that the list did not need to "reply-all". Having trouble getting FreeBSD 11-STABLE @ r329011 to boot from SAS3 4Kn HDDs via LSISAS 3008 HBA on a SuperMicro X10DRH-iT motherboard after an apparent installation. All internal media (including all other disks attached to the HBA) were removed to eliminate other storage being the reason the system won't boot. This occurs specifically in CSM mode, but the preference is to boot via UEFI mode instead. Anyway...booting the machine via the memstick image demonstrates the LSISAS 3008 controller attaching via mpr(4) (whose manpage describes the controller being supported[1]): mpr0@pci0:3:0:0: class=0x010700 card=0x080815d9 chip=0x00971000 rev=0x02 hdr=0x00 vendor = 'LSI Logic / Symbios Logic' device = 'SAS3008 PCI-Express Fusion-MPT SAS-3' class = mass storage subclass = SAS The only inserted disk attaches as da0 as illustrated by dmesg: ses0: pass0,da0: Elemne t descriptor: 'Slot00' da0 at mpr0 bus 0 scbus0 target 8 lun 0 ses0: pass0,da0: SAS Device Slot Element: 1 Phys at Slot 0 ses0: phy 0: SAS device type 1 id 0 ses0: phy 0: protocols: initiator( None ) Target( SSP ) ses0: phy 0: parent 500304801e870bff addr 5000c500a012814d da0: Fixed Direct Access SPC-4 SCSI device da0: Serial Number $serial_number da0: 1200.000MB/s transfers da0: Command queueing enabled da0: 1907729MB (488378648 4096 byte sectors) The original goal was to boot via zfs root, but when that failed, subsequent installations used the "Auto (UFS) option" to partition the disk. For example, the first installation gpart'd the disk as: # gpart show da0 =>6 488378635 da0 GPT (1.8T) 6 128 1 freebsd-boot (512K) 134 487325568 2 freebsd-ufs (1.8T) 487325702 1048576 3 freebsd-swap (4.0G) 4883742784363 - free - (17M) The result was a reboot loop. When the system reached the point of reading the disk, it just rebooted and continued doing so. There was no loader or beastie menu. Thus, thinking that it could be the partition layout requirements of the 4Kn disks, it was gpart'd like the below[2][3]. This was done by exiting to the shell during the partition phase of bsdinstall and manually gpart'ing the disk according to the below, mounting da0p2 at /mnt and placing an fstab at /tmp/bsdinstall_etc/fstab that included mount entries for /dev/da0p2 at / and /dev/da0p3 as swap. # gpart show da0 =>6 488378635 da0 GPT (1.8T) 634 - free - (136K) 40 512 1 freebsd-boot (2.0M) 552 419430400 2 freebsd-ufs (1.6T) 419430952 1048576 3 freebsd-swap (4.0G) 42047952867899113 - free - (259G) When configured as such, the system rebooted at the completion of the install and appeared to roll through the boot order, which specifies the HDD first, then CD/DVD, then network. It did attempt to boot via network, but is irrelevant here. All the hardware is alleged to be supported by FreeBSD as best I can tell and OS installation apparently works. I'm at a loss as to why the OS won't boot. Does someone have feedback or input that may expose why it doesn't boot? FWIW, a RHEL7 install was also attempted, which also does not boot. [1] https://www.freebsd.org/cgi/man.cgi?query=mpr=0=4=FreeBSD+11.1-RELEASE=default=html [2] https://lists.freebsd.org/pipermail/freebsd-hardware/ 2013-September/007380.html [3] http://www.wonkity.com/~wblock/docs/html/disksetup.html -- Take care Rick Miller ___ freebsd-stable@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
Re: stable/10 release.sh fails during mkisoimages-uefi.sh
On Wed, Apr 27, 2016 at 5:37 PM, Slawa Olhovchenkov <s...@zxy.spb.ru> wrote: > On Wed, Apr 27, 2016 at 01:00:19PM -0400, Rick Miller wrote: > > > Hi all, > > > > Building stable/10@r298482 errors when executing newfs_msdos on > > uefi-disc1.iso as shown below. It is being built on a system running a > > 10.2 version of stable/10. I believe this problem could be due to either > > the attempt to compile newer stable/10 code on an older 10.2 version of > > stable/10 or something in the code is broke. Can you shed some light on > > the error below? > > This issuse (makefs: error: The Disk Label must be at most 32 > characters long) present always. > Best way is fix makefs to shrink label to 32 characters and conver > this error to warning Thanks. This is resolved with this patch: diff --git a/release/amd64/mkisoimages-uefi.sh b/release/amd64/mkisoimages-uefi.sh index 9526ad7..0441dac 100644 --- a/release/amd64/mkisoimages-uefi.sh +++ b/release/amd64/mkisoimages-uefi.sh @@ -50,7 +50,7 @@ if [ $# -lt 3 ]; then exit 1 fi -LABEL=`echo $1 | tr '[:lower:]' '[:upper:]'`; shift +LABEL=`echo $1 | tr '[:lower:]' '[:upper:]' | cut -c 1-32`; shift NAME=$1; shift publisher="The FreeBSD Project. http://www.FreeBSD.org/; and PR 210463 was opened. -- Take care Rick Miller ___ freebsd-stable@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
stable/10 release.sh fails during mkisoimages-uefi.sh
Hi all, Building stable/10@r298482 errors when executing newfs_msdos on uefi-disc1.iso as shown below. It is being built on a system running a 10.2 version of stable/10. I believe this problem could be due to either the attempt to compile newer stable/10 code on an older 10.2 version of stable/10 or something in the code is broke. Can you shed some light on the error below? sh /usr/src/release/amd64/mkisoimages-uefi.sh -b 10_3_STABLE_20160427_amd64_UEFICD uefi-disc1.iso disc1 200+0 records in 200+0 records out 819200 bytes transferred in 0.003004 secs (272717981 bytes/sec) newfs_msdos: cannot get number of sectors per track: Operation not supported newfs_msdos: cannot get number of heads: Operation not supported newfs_msdos: trim 25 sectors to adjust to a multiple of 63 /dev/md0: 1532 sectors in 1532 FAT12 clusters (512 bytes/cluster) BytesPerSec=512 SecPerClust=1 ResSectors=1 FATs=2 RootDirEnts=512 Sectors=1575 Media=0xf8 FATsecs=5 SecPerTrack=63 Heads=1 HiddenSecs=0 makefs: error: The Disk Label must be at most 32 characters long usage: makefs [-t fs-type] [-o fs-options] [-d debug-mask] [-B endian] [-S sector-size] [-M minimum-size] [-m maximum-size] [-R roundup-size] [-s image-size] [-b free-blocks] [-f free-files] [-F mtree-specfile] [-xZ] [-N userdb-dir] image-file directory | manifest [extra-directory ...] sh /usr/src/release/amd64/mkisoimages-uefi.sh -b 10_3_STABLE_20160427_amd64_UEFIBO uefi-bootonly.iso bootonly 200+0 records in 200+0 records out 819200 bytes transferred in 0.003031 secs (270293725 bytes/sec) newfs_msdos: cannot get number of sectors per track: Operation not supported newfs_msdos: cannot get number of heads: Operation not supported newfs_msdos: trim 25 sectors to adjust to a multiple of 63 /dev/md0: 1532 sectors in 1532 FAT12 clusters (512 bytes/cluster) BytesPerSec=512 SecPerClust=1 ResSectors=1 FATs=2 RootDirEnts=512 Sectors=1575 Media=0xf8 FATsecs=5 SecPerTrack=63 Heads=1 HiddenSecs=0 makefs: error: The Disk Label must be at most 32 characters long usage: makefs [-t fs-type] [-o fs-options] [-d debug-mask] [-B endian] [-S sector-size] [-M minimum-size] [-m maximum-size] [-R roundup-size] [-s image-size] [-b free-blocks] [-f free-files] [-F mtree-specfile] [-xZ] [-N userdb-dir] image-file directory | manifest [extra-directory ...] make -C /usr/src/release release-done touch release true mkdir -p /R cp -a ftp /R/ cp -p disc1.iso /R/FreeBSD-10.3-STABLE-20160427-amd64-disc1.iso cp -p bootonly.iso /R/FreeBSD-10.3-STABLE-20160427-amd64-bootonly.iso cp -p memstick.img /R/FreeBSD-10.3-STABLE-20160427-amd64-memstick.img cp -p mini-memstick.img /R/FreeBSD-10.3-STABLE-20160427-amd64-mini-memstick.img cp -p uefi-memstick.img /R/FreeBSD-10.3-STABLE-20160427-amd64-uefi-memstick.img cp -p uefi-mini-memstick.img /R/FreeBSD-10.3-STABLE-20160427-amd64-uefi-mini-memstick.img cp -p uefi-disc1.iso /R/FreeBSD-10.3-STABLE-20160427-amd64-uefi-disc1.iso cp: uefi-disc1.iso: No such file or directory *** Error code 1 Stop. make: stopped in /usr/src/release -- Take care Rick Miller ___ freebsd-stable@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
Re: Installing packages from 9.2 Release DVD
On Tue, Oct 8, 2013 at 5:29 AM, Teske, Devin devin.te...@fisglobal.comwrote: [ snip ] Another problem is there is no any available information about this subject in the Handbook installation pages ( at least I could not find any one one ) . bsdconfig was just born in 9.2-R. Nobody has gotten around to documenting it. I'll be doing the first presentation on it at the vBSDcon [un]Conference coming up in a couple weeks (Oct 25-27th in Reston, VA; hosted by Verisign). Looking forward to this presentation, Devin! Devin's spot will be from 2PM - 3PM on October 26th. More information on vBSDcon can be found at http://www.vbsdcon.com/. Online registrations are available through October 23 and on-site registrations will be available through the entirety of the conference. The registration fee is USD$75. -- Take care Rick Miller ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to freebsd-stable-unsubscr...@freebsd.org
Re: Booting FreeBSD with Syslinux
On Wed, Jul 31, 2013 at 9:38 AM, Daniel O'Connor docon...@gsoft.com.au wrote: Hi, I am trying to make a FreeBSD 9.2 hybrid image (ie ISO USB from the same file) and as part of that I need to use syslinux. Unfortunately I can't get Syslinux's mboot.c32 to run the kernel or loader as suggested at http://www.syslinux.org/wiki/index.php/Mboot.c32 - it reports Invalid Multiboot image: neither ELF header nor a.out kludge found. I suspect I would be able to use memdisk as I have used that in the past with syslinux (for 7.x) however this was seems a lot cleaner and easier to generate. Has anyone had any success with this? I have not worked with Syslinux, but I do load a customized FreeBSD 8.x bootonly ISO via memdisk. I have not done similar with 9.x yet, but anticipate doing so with 9.2-RELEASE. I touch on it briefly in a blog post at http://blog.hostileadmin.com/2013/04/11/installing-freebsd-via-cobbler/ if you're interested. -- Take care Rick Miller ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to freebsd-stable-unsubscr...@freebsd.org
Re: Generating ISO With Pre-Installed Packages
On Fri, May 10, 2013 at 9:55 AM, Shawn Webb latt...@gmail.com wrote: Hey All, I'm looking to generate a FreeBSD 9-stable (and maybe 10-current) ISO that has certain packages pre-installed. I'd like to create my own installation media that will have certain things installed, like a web management UI that I'm actively working on. It'd be like what pfSense does. I did do a little googling and found pfSense's build documentation for spinning a custom build of pfSense. I'll be spending the weekend looking over their work. But in the meantime, does anyone know of the steps involved in such a process? Is the process documented somewhere? You're looking for package-split.py, a python script that generates packages. The blog post below may be of some use. It explains modifying the script and generating a release. http://blog.hostileadmin.com/2012/10/08/building-freebsd-media-with-custom-packages/ -- Take care Rick Miller ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to freebsd-stable-unsubscr...@freebsd.org
buildworld fails for stable/9
Hi all, I checked out stable/9 this morning to generate a release. buildworld fails with the following: /usr/src/lib/libc/gen/stringlist.c:108: error: conflicting types for 'sl_find' /usr/src/lib/libc/../../include/stringlist.h:54: error: previous declaration of 'sl_find' was here *** [stringlist.o] Error code 1 Stop in /usr/src/lib/libc. *** [lib/libc__L] Error code 1 Stop in /usr/src. *** [libraries] Error code 1 Stop in /usr/src. *** [_libraries] Error code 1 Stop in /usr/src. *** [buildworld] Error code 1 Stop in /usr/src. Is this an indication of conflicting libraries? -- Take care Rick Miller ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to freebsd-stable-unsubscr...@freebsd.org
Re: buildworld fails for stable/9
On Fri, Apr 26, 2013 at 8:12 AM, Tom Evans tevans...@googlemail.com wrote: This was the result of a bad MFC, Glen Barber just mailed the list to say he has corrected this so perhaps up and try again. Yep, I just saw his email and thought that it may be related. just checked out stable/9 again and am running buildworld! Thanks! -- Take care Rick Miller ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to freebsd-stable-unsubscr...@freebsd.org
Re: 9.1-RELEASE
On Mon, Nov 26, 2012 at 5:25 PM, Bas Smeelen b.smee...@ose.nl wrote: Hi Just modify newvers.sh to 9.1-RELEASE recompile and your on RELEASE :) Who has a no non-release policy, management? It's not just management, but also software engineers, architects, and business folks. When a company runs a service whose production SLA is 100%, many tend to be less forgiving. There's a lot riding on running a development branch in production, even if it is a Release Candidate. -- Take care Rick Miller ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to freebsd-stable-unsubscr...@freebsd.org
Re: FreeBSD 9.1 stability/robustness?
Someone asked about getting The DL360 G8 to boot to their intel branded pci NIC, but I cannot find that email :( At any rate, we removed the Broadcom daughterboard from the system and insured that the intel PCI NIC (i350) was bootable in the BIOS. On Sat, Nov 3, 2012 at 9:56 PM, Rick Miller vmil...@hostileadmin.com wrote: I have a blog post at http://blog.hostileadmin.com/2012/06/14/freebsd-on-hp-proliant-dl360p-g8-servers/ which touches on this. I heard as recently as today that the fixes for the BCM5719 and 5720 were recently committed to -CURRENT. It's too late for them to be rolled into 9.1. Not sure if they'll be committed to to stable/8 or not, but if so they could make it into 8.4-R. -- Take care Rick Miller ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to freebsd-stable-unsubscr...@freebsd.org
Re: FreeBSD 9.1 stability/robustness?
On Sun, Nov 4, 2012 at 12:28 PM, Rainer Duffner rai...@ultra-secure.de wrote: Oh - will were be an 8.4 release? That would be interesting. History shows that every release, since 4.x has gone to at least .4. I'd be willing to bet we will see an 8.4. The branch is still being developed. http://en.wikipedia.org/wiki/FreeBSD#Timeline -- Take care Rick Miller ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to freebsd-stable-unsubscr...@freebsd.org
Re: FreeBSD 9.1 stability/robustness?
On Fri, Nov 2, 2012 at 4:10 AM, Rainer Duffner rai...@ultra-secure.de wrote: Am Thu, 1 Nov 2012 20:14:51 -0600 (MDT) schrieb Brett Glass br...@lariat.net: I need to build up a few servers and routers, and am wondering how FreeBSD 9.1 is shaping up. Will it be likely to be more stable and robust than 9.0-RELEASE? Are there issues that will have to wait until 9.2-RELEASE to be fixed? Opinions welcome. If I'm not mistaken, the bge-stuff that makes the default NICs ins HP G8 servers (360+380) actually run will not make it back into 9.1. Intel cards work much better anyway... I have a blog post at http://blog.hostileadmin.com/2012/06/14/freebsd-on-hp-proliant-dl360p-g8-servers/ which touches on this. I heard as recently as today that the fixes for the BCM5719 and 5720 were recently committed to -CURRENT. It's too late for them to be rolled into 9.1. Not sure if they'll be committed to to stable/8 or not, but if so they could make it into 8.4-R. -- Take care Rick Miller ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to freebsd-stable-unsubscr...@freebsd.org
Re: bge problems in RELENG_9, bge0: watchdog timeout -- resetting
Hi Anders I've not had good luck with the BCM5719 in stable/8 either. Not sure if the driver has been updated in 9 or not, but I have a blog post explaining my woes with the BCM5719 at http://blog.hostileadmin.com/ On 7/3/12, Anders Nordby and...@freebsd.org wrote: Hi, I'm having lots of difficulties with BCM5719, which is the default network card of HP Proliant DL 360 G8 servers. I can get a few ping replies before I get a couple of these: bge0: watchdog timeout -- resetting bge0: watchdog timeout -- resetting Then everything hangs. Can not log in using ssh. I'm running: FreeBSD-9.0-RELENG_9-20120701-JPSNAP-amd64 Info about the NIC: # devinfo -rv | grep phy brgphy0 pnpinfo oui=0x1be9 model=0x22 rev=0x0 at phyno=1 brgphy1 pnpinfo oui=0x1be9 model=0x22 rev=0x0 at phyno=2 brgphy2 pnpinfo oui=0x1be9 model=0x22 rev=0x0 at phyno=3 brgphy3 pnpinfo oui=0x1be9 model=0x22 rev=0x0 at phyno=4 # grep bge /var/run/dmesg.boot bge0: Broadcom unknown BCM5719, ASIC rev. 0x5719001 mem 0xf6bf-0xf6bf, 0xf6be-0xf6be,0xf6bd-0xf6bd irq 32 at device 0.0 on pci3 bge0: CHIP ID 0x05719001; ASIC REV 0x5719; CHIP REV 0x57190; PCI-E miibus0: MII bus on bge0 bge0: Ethernet address: 2c:76:8a:54:08:14 bge1: Broadcom unknown BCM5719, ASIC rev. 0x5719001 mem 0xf6bc-0xf6bc, 0xf6bb-0xf6bb,0xf6ba-0xf6ba irq 36 at device 0.1 on pci3 bge1: CHIP ID 0x05719001; ASIC REV 0x5719; CHIP REV 0x57190; PCI-E miibus1: MII bus on bge1 bge1: Ethernet address: 2c:76:8a:54:08:15 bge2: Broadcom unknown BCM5719, ASIC rev. 0x5719001 mem 0xf6b9-0xf6b9, 0xf6b8-0xf6b8,0xf6b7-0xf6b7 irq 32 at device 0.2 on pci3 bge2: CHIP ID 0x05719001; ASIC REV 0x5719; CHIP REV 0x57190; PCI-E miibus2: MII bus on bge2 bge2: Ethernet address: 2c:76:8a:54:08:16 bge3: Broadcom unknown BCM5719, ASIC rev. 0x5719001 mem 0xf6b6-0xf6b6, 0xf6b5-0xf6b5,0xf6b4-0xf6b4 irq 36 at device 0.3 on pci3 bge3: CHIP ID 0x05719001; ASIC REV 0x5719; CHIP REV 0x57190; PCI-E miibus3: MII bus on bge3 bge3: Ethernet address: 2c:76:8a:54:08:17 Searching other bug reports and posts, I've tried: hw.bge.allow_asf=0 hw.pci.enable_msi=0 But it didn't help. Any ideas? If I don't use the loader.conf settings above, I also get (before the watchdog timeouts): bge0: 2 link states coalesced bge0: 2 link states coalesced bge0: 2 link states coalesced Best regards, -- Anders. ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to freebsd-stable-unsubscr...@freebsd.org -- Sent from my mobile device Take care Rick Miller ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to freebsd-stable-unsubscr...@freebsd.org
FreeBSD 8-STABLE on R620 w/ X520-DA2/Intel 82599
Hi All, I have 2 hosts, HP DL360 G8 and Dell R620. Both have the X520-DA2/Intel 82599 10G Fiber NIC. Both also have the same FreeBSD 8-STABLE image. The Dell displays the following in dmesg and we are unable to configure the ix0 or ix1 interfaces where the HP works just fine. Wondering if anyone else has experienced this? pci4: network, ethernet at device 0.0 (no driver attached) pci4: network, ethernet at device 0.1 (no driver attached) -- Take care Rick Miller ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to freebsd-stable-unsubscr...@freebsd.org
Re: FreeBSD 8-STABLE on R620 w/ X520-DA2/Intel 82599
On Fri, Jun 29, 2012 at 11:56 AM, Gary Palmer gpal...@freebsd.org wrote: On Fri, Jun 29, 2012 at 10:50:52AM -0400, Rick Miller wrote: Hi All, I have 2 hosts, HP DL360 G8 and Dell R620. Both have the X520-DA2/Intel 82599 10G Fiber NIC. Both also have the same FreeBSD 8-STABLE image. The Dell displays the following in dmesg and we are unable to configure the ix0 or ix1 interfaces where the HP works just fine. Wondering if anyone else has experienced this? pci4: network, ethernet at device 0.0 (no driver attached) pci4: network, ethernet at device 0.1 (no driver attached) Please see http://lists.freebsd.org/pipermail/freebsd-net/2012-June/032579.html it may be of some assistance. It looks like adding the Dell specific PCI IDs may be all thats required. Hrmm, very interesting indeed. How do I identify if/when/where the source has been updated? -- Take care Rick Miller ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to freebsd-stable-unsubscr...@freebsd.org
Re: FreeBSD 8-STABLE on R620 w/ X520-DA2/Intel 82599
On Fri, Jun 29, 2012 at 11:56 AM, Gary Palmer gpal...@freebsd.org wrote: On Fri, Jun 29, 2012 at 10:50:52AM -0400, Rick Miller wrote: Hi All, I have 2 hosts, HP DL360 G8 and Dell R620. Both have the X520-DA2/Intel 82599 10G Fiber NIC. Both also have the same FreeBSD 8-STABLE image. The Dell displays the following in dmesg and we are unable to configure the ix0 or ix1 interfaces where the HP works just fine. Wondering if anyone else has experienced this? pci4: network, ethernet at device 0.0 (no driver attached) pci4: network, ethernet at device 0.1 (no driver attached) Please see http://lists.freebsd.org/pipermail/freebsd-net/2012-June/032579.html it may be of some assistance. It looks like adding the Dell specific PCI IDs may be all thats required. We removed an Intel branded equivalent from the DL360 and tried it in the R620. It detected it no problem. Only problem was we could not see it in the BIOS, not a huge deal to us. -- Rick Miller ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to freebsd-stable-unsubscr...@freebsd.org
Re: Intel X520-DA2 Supported in stable/8?
On Fri, Jun 22, 2012 at 7:23 PM, Jack Vogel jfvo...@gmail.com wrote: Would probably be good to take care of the storm threshold if you haven't, set it to 0 and you disable the check, that's what we do internally. As for the queues and number of descriptors, that's kind of up to you, different work loads and environments work best with different setups. Hopefully, when you get rid of the rx ring setup failure you will get things working. Thanks, Jack. I did get rid of the rx ring failure. Link status still shows no carrier. I think everything looks right from the host's perspective. -- Take care Rick Miller ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to freebsd-stable-unsubscr...@freebsd.org
Re: Intel X520-DA2 Supported in stable/8?
Turns out the gbic in the switch was bad...I didn't think there was a problem on the host, but you all still gave me some good info. I appreciate it! On 6/25/12, Rick Miller vmil...@hostileadmin.com wrote: On Fri, Jun 22, 2012 at 7:23 PM, Jack Vogel jfvo...@gmail.com wrote: Would probably be good to take care of the storm threshold if you haven't, set it to 0 and you disable the check, that's what we do internally. As for the queues and number of descriptors, that's kind of up to you, different work loads and environments work best with different setups. Hopefully, when you get rid of the rx ring setup failure you will get things working. Thanks, Jack. I did get rid of the rx ring failure. Link status still shows no carrier. I think everything looks right from the host's perspective. -- Take care Rick Miller -- Sent from my mobile device Take care Rick Miller ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to freebsd-stable-unsubscr...@freebsd.org
Intel X520-DA2 Supported in stable/8?
Hi All, Wondering if the Intel X520-DA2 10G Fibre NIC is supported in stable/8. Hardware notes don't specify it, but I have a system up and the interfaces appear to be loaded by the ix driver. However, status indicates no carrier. -- Take care Rick Miller ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to freebsd-stable-unsubscr...@freebsd.org
Re: Intel X520-DA2 Supported in stable/8?
On Fri, Jun 22, 2012 at 3:13 PM, Rick Miller vmil...@hostileadmin.com wrote: Hi All, Wondering if the Intel X520-DA2 10G Fibre NIC is supported in stable/8. Hardware notes don't specify it, but I have a system up and the interfaces appear to be loaded by the ix driver. However, status indicates no carrier. Ok, brain fart. Please forgive my ineptitude. I once sent an email inquiring about the Intel 82599, which is this NIC. Responses to that mail say it's supported by the ixgbe driver. My stable/8 installation (5/21/2012) probes it with an ix driver that I cannot find any info on. The ixgbe manage indicates it only supports 82598 based controllers. Not sure what to think here... ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to freebsd-stable-unsubscr...@freebsd.org
Re: Intel X520-DA2 Supported in stable/8?
On Fri, Jun 22, 2012 at 3:54 PM, Andrew Boyer abo...@averesystems.com wrote: The ixgbe driver creates devices named ix0, etc. I believe you need to run 'ifconfig ix0 up' before it will attempt to get link. Thanks for clarifying that tidbit. At least I know the driver loading is the correct driver :) I did try ifup'ing the interface...it shows the interface up, status is still no carrier. I've had confirmation that the cable itself is good. I wonder if it matters that the upstream switch has VLAN tagging enabled? ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to freebsd-stable-unsubscr...@freebsd.org
Re: Intel X520-DA2 Supported in stable/8?
dmesg and ifconfig output below... On Fri, Jun 22, 2012 at 4:02 PM, Rick Miller vmil...@hostileadmin.com wrote: On Fri, Jun 22, 2012 at 3:54 PM, Andrew Boyer abo...@averesystems.com wrote: The ixgbe driver creates devices named ix0, etc. I believe you need to run 'ifconfig ix0 up' before it will attempt to get link. Thanks for clarifying that tidbit. At least I know the driver loading is the correct driver :) I did try ifup'ing the interface...it shows the interface up, status is still no carrier. I've had confirmation that the cable itself is good. I wonder if it matters that the upstream switch has VLAN tagging enabled? ix0: Intel(R) PRO/10GbE PCI-Express Network Driver, Version - 2.4.5 port 0x7000-0x701f mem 0xf6b8-0xf6bf,0xf6b7-0xf6b73fff irq 40 at device 0.0 on pci7 ix0: Using MSIX interrupts with 9 vectors ix0: RX Descriptors exceed system mbuf max, using default instead! ix0: [ITHREAD] ix0: [ITHREAD] ix0: [ITHREAD] ix0: [ITHREAD] ix0: [ITHREAD] ix0: [ITHREAD] ix0: [ITHREAD] ix0: [ITHREAD] ix0: [ITHREAD] ix0: Ethernet address: 90:e2:ba:15:e2:60 ix0: PCI Express Bus: Speed 5.0Gb/s Width x8 ix1: Intel(R) PRO/10GbE PCI-Express Network Driver, Version - 2.4.5 port 0x7020-0x703f mem 0xf6a8-0xf6af,0xf6a7-0xf6a73fff irq 44 at device 0.1 on pci7 ix1: Using MSIX interrupts with 9 vectors ix1: RX Descriptors exceed system mbuf max, using default instead! ix1: [ITHREAD] ix1: [ITHREAD] ix1: [ITHREAD] ix1: [ITHREAD] ix1: [ITHREAD] ix1: [ITHREAD] ix1: [ITHREAD] ix1: [ITHREAD] ix1: [ITHREAD] ix1: Ethernet address: 90:e2:ba:15:e2:61 ix1: PCI Express Bus: Speed 5.0Gb/s Width x8 ix0: flags=8843UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST metric 0 mtu 1500 options=401bbRXCSUM,TXCSUM,VLAN_MTU,VLAN_HWTAGGING,JUMBO_MTU,VLAN_HWCSUM,TSO4,VLAN_HWTSO ether 90:e2:ba:XX:XX:XX inet 10.1.2.50 netmask 0xfe00 broadcast 10.1.3.255 media: Ethernet autoselect status: no carrier ix1: flags=8802BROADCAST,SIMPLEX,MULTICAST metric 0 mtu 1500 options=401bbRXCSUM,TXCSUM,VLAN_MTU,VLAN_HWTAGGING,JUMBO_MTU,VLAN_HWCSUM,TSO4,VLAN_HWTSO ether 90:e2:ba:XX:XX:XX media: Ethernet autoselect status: no carrier -- Take care Rick Miller ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to freebsd-stable-unsubscr...@freebsd.org
Re: Intel X520-DA2 Supported in stable/8?
On Fri, Jun 22, 2012 at 5:21 PM, Jack Vogel jfvo...@gmail.com wrote: Increase your system mbuf pool size, you do not want that failure to happen. Thanks, Jack. I saw a thread where you discussed this. You are referring to kern.ipc.nmbclusters, correct? Should I also adjust the following? hw.ixgbe.rxd hw.ixgbe.txd hw.ixgbe.num_queues hw.intr_storm_threshold ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to freebsd-stable-unsubscr...@freebsd.org
Re: Kernel trap with stable/8 on DL360p G8 w/ BCM5719
On Wed, Jun 13, 2012 at 12:07 PM, Philipp Wuensche cryx-free...@h3q.com wrote: Rick Miller wrote: Hi all, I am attempting to build stable/8 (as of 21 May 2012) on a DL360p G8 with a BCM5719. I receive a kernel panic very similar to the one at this URL: http://freebsd.1045724.n5.nabble.com/Fatal-trap-19-Stopped-at-bge-init-locked-and-bge-booting-problems-td5504461.html When booting 9.0-RELEASE on the exact same machine everything is fine, until I set an interface to UP which has an active link. I can install stable/8 from physical media, but like you, I get the panic under the same circumstances. -- Take care Rick Miller ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to freebsd-stable-unsubscr...@freebsd.org
Kernel trap with stable/8 on DL360p G8 w/ BCM5719
Hi all, I am attempting to build stable/8 (as of 21 May 2012) on a DL360p G8 with a BCM5719. I receive a kernel panic very similar to the one at this URL: http://freebsd.1045724.n5.nabble.com/Fatal-trap-19-Stopped-at-bge-init-locked-and-bge-booting-problems-td5504461.html . The hardware notes don't specify that the BCM5719 is supported, but the bge manpage appears to indicate it is supported. Is there a definitive answer whether or not it is supported? -- Take care Rick Miller ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to freebsd-stable-unsubscr...@freebsd.org
Re: Ports from a particular date in the past... Re: Why Are You NOT Using FreeBSD?
I, for one, appreciate you changing the subject because I didn't know this either and its an important function in my use case where point in time snapshots are important to the architects and ops folks! On 6/6/12, grenville armitage garmit...@swin.edu.au wrote: On 06/07/2012 00:16, Chris Rees wrote: On 6 June 2012 14:12, Ericherichfreebsdl...@ovitrap.com wrote: [..] is my English really this bad? From the handbook: '. In particular, use only tag=. for the ports-* collections.' Your English is fine, but being told to use tag=. != tag=. is the only tag that exists. Another data point: In Erich's defense, I'd say his interpretation is quite understandable. ...use only tag=. for the ports-* collections also left me with the distinct impression (some many moons in the past) that there are no other meaningful (or safe) tags when csup'ing the Ports tree. In 12 years of using FreeBSD I've never really sought out Erich's use case (viz. roll back /usr/ports to some past known-good version), I just assumed it wasn't possible. So this thread has taught at least one person (me) a new thing -- I never fully grokked that adding date= to the supfile could achieve this desired result when csup'ing the Ports tree. Now I know, and I've changed the Subject line of this email in the hope it helps some future soul googling for the answer. cheers, gja ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to freebsd-stable-unsubscr...@freebsd.org -- Sent from my mobile device Take care Rick Miller ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to freebsd-stable-unsubscr...@freebsd.org
Support for Intel 82599ES?
Hi All, I did not see the Intel 82599ES chipset in the hardware release notes for 8.3 or 9.0. Are these controllers supported at this time? -- Take care Rick Miller ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to freebsd-stable-unsubscr...@freebsd.org
Re: Support for Intel 82599ES?
Thanks, Jack! Also another support question for the listsIs the Broadcom BCM5719 supported? I can find neither in the hardware notes for 8.3 nor 9.0. On Fri, Jun 1, 2012 at 12:49 PM, Jack Vogel jfvo...@gmail.com wrote: Yes, it is supported in the ixgbe driver. Jack On Fri, Jun 1, 2012 at 8:36 AM, Rick Miller vmil...@hostileadmin.com wrote: Hi All, I did not see the Intel 82599ES chipset in the hardware release notes for 8.3 or 9.0. Are these controllers supported at this time? -- Take care Rick Miller ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to freebsd-stable-unsubscr...@freebsd.org -- Take care Rick Miller ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to freebsd-stable-unsubscr...@freebsd.org
Re: Support for Intel 82599ES?
Thanks, Michael! I took a look at the manpage and it does appear that it is supported by the bge driver. It also states that the 572x controller is also supported, but I heard a rumor stating that the BCM5720 in particular did not work even though the manpage indicates it is supported. I was unable to verify this, but that's why I was asking for clarification. I will assume it works at this point. On Fri, Jun 1, 2012 at 1:25 PM, Michael Butler i...@protected-networks.net wrote: On 06/01/12 13:06, Rick Miller wrote: Thanks, Jack! Also another support question for the listsIs the Broadcom BCM5719 supported? I can find neither in the hardware notes for 8.3 nor 9.0. man bge -- Take care Rick Miller ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to freebsd-stable-unsubscr...@freebsd.org
