Re: What is evdev and autoloading?

2019-02-18 Thread Warner Losh
On Mon, Feb 18, 2019 at 9:50 AM Steve Kargl < s...@troutmask.apl.washington.edu> wrote: > On Mon, Feb 18, 2019 at 09:11:14AM -0700, Warner Losh wrote: > > > > You do know these constant complaints about people trying to make things > > better is demoralizing and counter

Re: What is evdev and autoloading?

2019-02-18 Thread Warner Losh
On Mon, Feb 18, 2019 at 9:50 AM Rodney W. Grimes < freebsd-...@pdx.rh.cn85.dnsmgr.net> wrote: > > On Mon, Feb 18, 2019 at 9:12 AM Rodney W. Grimes < > > freebsd-...@pdx.rh.cn85.dnsmgr.net> wrote: > > > > > > On Mon, Feb 18, 2019 at 07:12:24AM -0800, Rodney W. Grimes wrote: > > > > > > On 2/18/19

Re: What is evdev and autoloading?

2019-02-18 Thread Warner Losh
On Sun, Feb 17, 2019 at 3:52 PM Steve Kargl < s...@troutmask.apl.washington.edu> wrote: > Anyone have insight into what evdev is? There appears to > be no manual page. When I reboot a system with custom > kernel, the system is autoloading evdev.ko, uhid.ko, and > wmt.ko. I do not need nor what

Re: What is evdev and autoloading?

2019-02-18 Thread Warner Losh
On Mon, Feb 18, 2019 at 9:12 AM Rodney W. Grimes < freebsd-...@pdx.rh.cn85.dnsmgr.net> wrote: > > On Mon, Feb 18, 2019 at 07:12:24AM -0800, Rodney W. Grimes wrote: > > > > On 2/18/19 12:06 PM, Stefan Blachmann wrote: > > > > > On 2/18/19, Vladimir Kondratyev wrote: > > > > >> On 2019-02-17

Re: What is evdev and autoloading?

2019-02-18 Thread Warner Losh
On Mon, Feb 18, 2019 at 8:33 AM Rodney W. Grimes < freebsd-...@pdx.rh.cn85.dnsmgr.net> wrote: > > On 2/18/19 12:06 PM, Stefan Blachmann wrote: > > > On 2/18/19, Vladimir Kondratyev wrote: > > >> On 2019-02-17 21:03, Steve Kargl wrote: > > >>> Anyone have insight into what evdev is? > > >>

Re: problem building dev/e1000

2019-02-16 Thread Warner Losh
On Sat, Feb 16, 2019 at 9:16 AM Rodney W. Grimes < freebsd-...@pdx.rh.cn85.dnsmgr.net> wrote: > > > > > On Feb 15, 2019, at 11:47, Robert Huff wrote: > > > > > > Lev Serebryakov writes: > > > > > >>> My question would be: why? If some drivers have a new > > >>> dependency on iflib, why isn't

Re: problem building dev/e1000

2019-02-15 Thread Warner Losh
On Fri, Feb 15, 2019 at 12:54 PM Ian Lepore wrote: > On Fri, 2019-02-15 at 12:32 -0700, Warner Losh wrote: > > On Fri, Feb 15, 2019 at 12:17 PM Ian Lepore wrote: > > > > > On Fri, 2019-02-15 at 10:53 -0800, Enji Cooper wrote: > > > > > [...] > &g

Re: problem building dev/e1000

2019-02-15 Thread Warner Losh
On Fri, Feb 15, 2019 at 12:17 PM Ian Lepore wrote: > On Fri, 2019-02-15 at 10:53 -0800, Enji Cooper wrote: > > > On Feb 15, 2019, at 10:46, Eric Joyner wrote: > > > > > > ifdi_if.h is a system generated interface file that network drivers > > > that depend on iflib use. It's generated from

Re: kernel build dies with "unknown option"

2019-02-13 Thread Warner Losh
On Wed, Feb 13, 2019, 4:31 PM Robert Huff > On a system running: > > FreeBSD 13.0-CURRENT r343080 16 Jan 2019 amd64 > > I updated the source tree as of midnight US Eastern time, then > ran buildworld. That completed successfully. > Then: > > huff@jerusalem> make

Re: timed restoral until deleter makes a port

2019-01-24 Thread Warner Losh
On Thu, Jan 24, 2019 at 5:03 PM Rodney W. Grimes < freebsd-...@pdx.rh.cn85.dnsmgr.net> wrote: > > On Thu, Jan 24, 2019 at 4:13 PM Julian H. Stacey > wrote: > > > > > Current box here is now about 10 seconds ahead, since timed was > deleted, > > > still waiting for the code vandal who removed

Re: timed restoral until deleter makes a port

2019-01-24 Thread Warner Losh
On Thu, Jan 24, 2019 at 4:13 PM Julian H. Stacey wrote: > Current box here is now about 10 seconds ahead, since timed was deleted, > still waiting for the code vandal who removed timed from src/ > without proper discussion in advance, to move timed from src/ to ports/ > > timed absence will bite

Re: Multiport serial card Exsys EX-44388, where are the devices ?

2019-01-20 Thread Warner Losh
On Sun, Jan 20, 2019 at 5:09 PM Warner Losh wrote: > > > On Sun, Jan 20, 2019, 4:41 PM Kurt Jaeger >> Hi! >> >> > Well no longer needed as puc0 has found and allocated the >> > device(s) which would of shown up had you done this before >> >

Re: Multiport serial card Exsys EX-44388, where are the devices ?

2019-01-20 Thread Warner Losh
On Sun, Jan 20, 2019, 4:41 PM Kurt Jaeger Hi! > > > Well no longer needed as puc0 has found and allocated the > > device(s) which would of shown up had you done this before > > you fixed puc0 to find them. > > The problem is that the found 4 uarts are not 8 uarts, and they do not > seem to work

Re: GPT boot has less features than legacy MBR-based one (Was: UEFI, loader.efi and /boot.config)

2019-01-20 Thread Warner Losh
On Sun, Jan 20, 2019, 9:29 AM Lev Serebryakov Hello Rebecca, > > Sunday, January 20, 2019, 7:27:56 AM, you wrote: > > > Ultimately, UEFI doesn't care about disks and partitions: it only really > knows > > about ESPs -- FAT12/16/32 formatted partitions that contain the EFI > directory > >

Re: GPT boot has less features than legacy MBR-based one (Was: UEFI, loader.efi and /boot.config)

2019-01-19 Thread Warner Losh
On Sat, Jan 19, 2019 at 9:32 AM Rodney W. Grimes < freebsd-...@pdx.rh.cn85.dnsmgr.net> wrote: > > On Sat, Jan 19, 2019 at 9:00 AM Rodney W. Grimes < > > freebsd-...@pdx.rh.cn85.dnsmgr.net> wrote: > > > > > > > > > > On January 19, 2019 at 2:52:28 AM, Lev Serebryakov (l...@freebsd.org > > >

Re: Multiport serial card Exsys EX-44388, where are the devices ?

2019-01-19 Thread Warner Losh
On Sat, Jan 19, 2019 at 2:52 AM Kurt Jaeger wrote: > Hi! > > > uart is the new thing. sio info should be ignored. > > > > Chances are good that this device doesn't have the proper entries in the > > puc driver. Do you have any pci devices that show up as unclaimed? > > In a different box, I got

Re: GPT boot has less features than legacy MBR-based one (Was: UEFI, loader.efi and /boot.config)

2019-01-19 Thread Warner Losh
On Sat, Jan 19, 2019 at 9:00 AM Rodney W. Grimes < freebsd-...@pdx.rh.cn85.dnsmgr.net> wrote: > > > > On January 19, 2019 at 2:52:28 AM, Lev Serebryakov (l...@freebsd.org > (mailto:l...@freebsd.org)) wrote: > > > > > I have never seen such item in BIOS Setup. I've checked two MoBos now > (one is

Re: Multiport serial card Exsys EX-44388, where are the devices ?

2019-01-18 Thread Warner Losh
On Fri, Jan 18, 2019 at 2:53 PM Kurt Jaeger wrote: > Hi! > > Trying to get a 8-port serial PCIe card into operation (Exsys EX-44388). > After reboot, dmesg shows: > > uart2: <16550 or compatible> port 0x3e8-0x3ef irq 10 on acpi0 > > and /dev/ has cuau2* devices. It's unclear, which of the 8

Re: GPT boot has less features than legacy MBR-based one (Was: UEFI, loader.efi and /boot.config)

2019-01-18 Thread Warner Losh
On Fri, Jan 18, 2019 at 2:11 PM Emmanuel Vadot wrote: > On Fri, 18 Jan 2019 22:50:31 +0300 > Lev Serebryakov wrote: > > > On 18.01.2019 22:35, Rodney W. Grimes wrote: > > > > >>> errm.. you press a key and enter device and or loader path. if it is > not working - the code is there to be fixed.

Re: GPT boot has less features than legacy MBR-based one (Was: UEFI, loader.efi and /boot.config)

2019-01-18 Thread Warner Losh
On Fri, Jan 18, 2019 at 11:27 AM Lev Serebryakov wrote: > On 18.01.2019 21:14, Toomas Soome wrote: > > > errm.. you press a key and enter device and or loader path. if it is not > working - the code is there to be fixed. > And loader looks to "bootme" attribute and try to boot from partition >

Re: UEFI, loader.efi and /boot.config

2019-01-18 Thread Warner Losh
On Fri, Jan 18, 2019 at 8:55 AM Lev Serebryakov wrote: > On 18.01.2019 17:10, Kyle Evans wrote: > > > There's some UEFI var that's supposed to serve the same kind of > > purpose as /boot.config -- early boot parameters. I think we had > > discussed implementing this at some point, but this

Re: UEFI, loader.efi and /boot.config

2019-01-18 Thread Warner Losh
On Fri, Jan 18, 2019 at 8:27 AM Rodney W. Grimes < freebsd-...@pdx.rh.cn85.dnsmgr.net> wrote: > > On Fri, Jan 18, 2019, 12:49 AM Kurt Jaeger > > > > Hi! > > > > > > > With a recent change I made for UEFI, we now install loader.efi onto > the > > > ESP and don???t run boot1. That means that

Re: UEFI, loader.efi and /boot.config

2019-01-18 Thread Warner Losh
On Fri, Jan 18, 2019, 12:49 AM Kurt Jaeger Hi! > > > With a recent change I made for UEFI, we now install loader.efi onto the > ESP and don???t run boot1. That means that /boot.config is no longer read, > and so console settings need to be put in /boot/loader.conf > > Which change is that ? >

Re: UEFI, loader.efi and /boot.config

2019-01-17 Thread Warner Losh
On Thu, Jan 17, 2019, 7:33 PM Rebecca Cran > With a recent change I made for UEFI, we now install loader.efi onto the > ESP and don’t run boot1. That means that /boot.config is no longer read, > and so console settings need to be put in /boot/loader.conf. > I was wondering if people will expect

Re: buildworld falure: truncated or malformed archive

2019-01-02 Thread Warner Losh
On Wed, Jan 2, 2019, 1:42 PM John Baldwin On 12/31/18 12:08 PM, Warner Losh wrote: > > On Mon, Dec 31, 2018, 1:36 PM Ryan Stone > > >> Does this mean that it's currently impossible to build a world with > >> debug symbols? > >> > > > > Yes. Cla

Re: buildworld falure: truncated or malformed archive

2018-12-31 Thread Warner Losh
On Mon, Dec 31, 2018, 1:36 PM Ryan Stone Does this mean that it's currently impossible to build a world with > debug symbols? > Yes. Clang is simply too big until 64 bit offset support goes in. Warner > ___ freebsd-current@freebsd.org mailing list

Re: efibootmgr: Cannot translate unix loader path xxx\xxx\xxx to UEFI: No error: 0

2018-12-28 Thread Warner Losh
On Fri, Dec 28, 2018, 5:45 AM O. Hartmann On Thu, 27 Dec 2018 08:38:20 -0700 > Warner Losh wrote: > > > On Dec 27, 2018 7:42 AM, "O. Hartmann" wrote: > > > > -BEGIN PGP SIGNED MESSAGE- > > Hash: SHA256 > > > > Am Thu, 27

Re: buildworld falure: truncated or malformed archive

2018-12-27 Thread Warner Losh
On Thu, Dec 27, 2018, 5:29 PM Ed Maste On Thu, 27 Dec 2018 at 14:35, Ryan Stone wrote: > > > > I seem to recall something about libarchive or ar having a bug > > creating archives > 4GB, > > Indeed, FreeBSD's bespoke ar does not support the /SYM64/ format > needed for offsets >4GB. imp@ also ran

Re: buildworld falure: truncated or malformed archive

2018-12-27 Thread Warner Losh
On Thu, Dec 27, 2018, 2:36 PM Ryan Stone I'm trying to update an old (~May 2018) -head system to the latest, > but I'm getting a persistent error during buildworld: > > ld: error: /usr/obj/usr/src/amd64.amd64/lib/clang/libclang/libclang.a: > could not get the member for symbol > >

Re: efibootmgr: Cannot translate unix loader path xxx\xxx\xxx to UEFI: No error: 0

2018-12-27 Thread Warner Losh
On Dec 27, 2018 7:42 AM, "O. Hartmann" wrote: -BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Am Thu, 27 Dec 2018 13:29:44 +0100 "Hartmann, O." schrieb: > Updated Fujitsu Celsius M740 to its lates UEFI firmware today. > After this update, the box won't boot FreeBSD 12-STABLE anymore! With >

Re: ctm(1) deprecation in the FreeBSD base system?

2018-12-23 Thread Warner Losh
On Sun, Dec 23, 2018 at 12:27 AM Stefan Esser wrote: > Am 23.12.18 um 02:39 schrieb Montgomery-Smith, Stephen: > > On 12/21/18 10:03 PM, Julian H. Stacey wrote: > >>> The port Makefile that I have prepared is attached below for reference. > >>> Regards, STefan > >> > >> Thanks Stefan, > >> I

Re: workaround for VMware WS NAT bug triggered by OpenSSH 7.8p1 changes

2018-12-22 Thread Warner Losh
On Sat, Dec 22, 2018, 11:03 AM Yuri Pankov Mark Peek wrote: > > On Fri, Dec 21, 2018 at 9:30 PM Enji Cooper > wrote: > > > >> > >>> On Dec 21, 2018, at 17:48, Yuri Pankov wrote: > >>> > >>> Mark Peek wrote: > Thanks for the cc:. I forwarded the original report on to an internal >

Re: workaround for VMware WS NAT bug triggered by OpenSSH 7.8p1 changes

2018-12-21 Thread Warner Losh
I've been hit by this as well. At least two others on IRC have had the same issue. Warner On Fri, Dec 21, 2018 at 5:10 PM Enji Cooper wrote: > > > On Dec 21, 2018, at 3:55 PM, Yuri Pankov wrote: > > > > Hi, > > > > There's apparently a bug in VMware Workstation NAT implementation, made > >

Re: The future of ZFS in FreeBSD

2018-12-20 Thread Warner Losh
On Thu, Dec 20, 2018 at 1:49 PM Allan Jude wrote: > I am to give a big thanks to Matt Ahrens for organizing the monthly > OpenZFS Leadership meeting, and the OpenZFS developer summit, and to > Brian Behlendorf for being so helpful, and willing to work to make > OpenZFS better for everyone. >

Re: The future of ZFS in FreeBSD

2018-12-20 Thread Warner Losh
Matt, This is a fairly comprehensive plan. Kudos for putting it together. The big question here is do you have a complete list of FreeBSD-specific changes that will be lost in the cut-over? We've heard about TRIM support and maybe NFSv4, but are there others that can be identified? Once you

Re: WITH_CTF breaks CD loader: "File too big"

2018-12-03 Thread Warner Losh
On Mon, Dec 3, 2018 at 11:14 AM Yuri Pankov wrote: > Warner Losh wrote: > > On Mon, Dec 3, 2018 at 9:56 AM Yuri Pankov wrote: > > > >> Yuri Pankov wrote: > >>> Warner Losh wrote: > >>>> On Mon, Dec 3, 2018 at 8:10 AM Warner Losh wrote: >

Re: WITH_CTF breaks CD loader: "File too big"

2018-12-03 Thread Warner Losh
On Mon, Dec 3, 2018 at 9:56 AM Yuri Pankov wrote: > Yuri Pankov wrote: > > Warner Losh wrote: > >> On Mon, Dec 3, 2018 at 8:10 AM Warner Losh wrote: > >> > >>> > >>> On Mon, Dec 3, 2018 at 12:24 AM Baptiste Daroussin > >>> wro

Re: WITH_CTF breaks CD loader: "File too big"

2018-12-03 Thread Warner Losh
On Mon, Dec 3, 2018 at 8:10 AM Warner Losh wrote: > > On Mon, Dec 3, 2018 at 12:24 AM Baptiste Daroussin > wrote: > >> On Sun, Dec 02, 2018 at 06:08:34PM +0300, Yuri Pankov wrote: >> > Hi, >> > >> > Building disc1.iso using `make release` and having

Re: WITH_CTF breaks CD loader: "File too big"

2018-12-03 Thread Warner Losh
On Mon, Dec 3, 2018 at 12:24 AM Baptiste Daroussin wrote: > On Sun, Dec 02, 2018 at 06:08:34PM +0300, Yuri Pankov wrote: > > Hi, > > > > Building disc1.iso using `make release` and having WITH_CTF set in > > src.conf leads to "File too big" displayed when booting the image. > > > > Would it make

Re: SCSI and dmesg

2018-11-29 Thread Warner Losh
On Thu, Nov 29, 2018 at 8:09 AM Alan Somers wrote: > On Mon, Nov 26, 2018 at 3:57 PM Warner Losh wrote: > >> On Mon, Nov 26, 2018 at 3:32 PM Maxim Sobolev >> wrote: >> >> > Somebody needs to make collection/submission automatic and make a port >> out

Re: SCSI and dmesg

2018-11-26 Thread Warner Losh
only when there's a material change... And I'd rather we get more nuanced data than dmesg can provide if we were to do the data collection. The admonition to submit to this site was one of expedience... Warner > -Max > > On Mon, Nov 26, 2018 at 2:08 PM Yuri Pankov wrote: > > > Yuri P

Re: Devd / devmatch(8) -- netif race 12-RC1

2018-11-22 Thread Warner Losh
On Wed, Nov 21, 2018, 11:43 PM Dan Partelly wireless lagg initialization is broken in this scenario, all-right. The > init/rc system as it is now can’t cope easily with a modern asynchronous > initialization sequence. Sure you could probably find an order which works, > only to find yourself in

Re: Devd / devmatch(8) -- netif race 12-RC1

2018-11-19 Thread Warner Losh
On Mon, Nov 19, 2018 at 7:48 PM Dan Partelly wrote: > Hello, > > Today I tried a simple wireless failover on a machine running free-bsd. > After reboot the system cannot complete the initialization sequence OK with > devmatcher. > The devd/devmatch(8) combo correctly identified the wireless

Re: UEFI GOP: screen goes blank during boot after loader is finished

2018-11-15 Thread Warner Losh
On Thu, Nov 15, 2018 at 12:10 PM Rebecca Cran wrote: > On Wednesday, 14 November 2018 19:56:56 MST Warner Losh wrote: > > > What is the ConOut evifar look like? We set serial when the UEFI env says > > to do so. > > Booting with: > > sudo bhyve -A -P -c 2 -H -m 4G

Re: UEFI GOP: screen goes blank during boot after loader is finished

2018-11-14 Thread Warner Losh
On Wed, Nov 14, 2018 at 4:00 PM Kyle Evans wrote: > On Wed, Nov 14, 2018 at 4:55 PM Subbsd wrote: > > > > On Thu, Nov 15, 2018 at 1:33 AM Kyle Evans wrote: > > > > > > On Wed, Nov 14, 2018 at 4:30 PM Kyle Evans wrote: > > > > > > > > On Wed, Nov 14, 2018 at 4:23 PM Subbsd wrote: > > > > > >

Re: Hole-punching, TRIM, etc

2018-11-13 Thread Warner Losh
On Tue, Nov 13, 2018 at 3:52 PM Conrad Meyer wrote: > Geom devices have the DIOCGDELETE ioctl, which translates into > BIO_DELETE (which is TRIM, as I understand it). > Correct. TRIM is both the catch-all term people use, as well as the name of a specific DSM (data set management) command in

Re: Hole-punching, TRIM, etc

2018-11-13 Thread Warner Losh
On Tue, Nov 13, 2018 at 3:10 PM Alan Somers wrote: > Hole-punching has been discussed on these lists before[1]. It basically > means to turn a dense file into a sparse file by deallocating storage for > some of the blocks in the middle. There's no standard API for it. Linux > uses

Re: drm changes and updating to 12.0

2018-11-05 Thread Warner Losh
On Mon, Nov 5, 2018 at 10:23 AM Robert Huff wrote: > > Warner Losh writes: > > > I'm curious where 2013 comes from. I know that Intel Sandy Bridge > graphics > > is supported with VAAPI acceleration by drm-stable-kmod, since it i > working > >

Re: drm changes and updating to 12.0

2018-11-05 Thread Warner Losh
On Sun, Nov 4, 2018 at 10:52 PM Kevin Oberman wrote: > On Sun, Nov 4, 2018 at 12:15 PM Niclas Zeising > wrote: > > > On 11/4/18 8:29 PM, Robert Huff wrote: > > > > > > I have a set of older machines (e.g. AMD Phenom II, Radeon HD3300 > > > gpu) which will be updated from 11. to 12.0 once

Re: UEFI: How to go about updating the ESP with loader.efi during installworld

2018-11-04 Thread Warner Losh
On Sun, Nov 4, 2018 at 4:10 PM Rebecca Cran wrote: > On Sunday, 4 November 2018 15:56:25 MST Warner Losh wrote: > > > I think that's a really really bad idea. We should *NEVER* create them by > > default. We are only sliding by on the coat-tails of compatibility by > using &

Re: UEFI: How to go about updating the ESP with loader.efi during installworld

2018-11-04 Thread Warner Losh
On Sun, Nov 4, 2018 at 2:27 PM Allan Jude wrote: > On 2018-11-04 16:20, Rebecca Cran wrote: > > I'm currently working on creating and updating the ESP (EFI System > Partition) > > for UEFI booting during installation and installworld. > > > > During installation, with my changes it gets mounted

Re: UEFI: How to go about updating the ESP with loader.efi during installworld

2018-11-04 Thread Warner Losh
On Sun, Nov 4, 2018 at 2:43 PM Rebecca Cran wrote: > On Sunday, 4 November 2018 14:36:13 MST Toomas Soome wrote: > > > it is reasonable to have efi/freebsd directory, the efi/boot/bootx64.efi > is > > hard one of course. But then again, it is problem only when we can not > > setup EFI

Re: armv7 BETA3 panics when usb-disk inserted

2018-11-04 Thread Warner Losh
On Sun, Nov 4, 2018 at 12:55 AM Poul-Henning Kamp wrote: > With the 12.0-BETA3 BEAGLEBONE image, I very often see this panic > when I plug a USB attached SSD disk in. > ... >umass0 on uhub0 > umass0: > on usbus1 > umass0: SCSI over Bulk-Only; quirks = 0x8100 >

Re: UEFI boot hangs after loader

2018-10-28 Thread Warner Losh
On Sun, Oct 28, 2018, 10:39 AM Yuri Pankov wrote: > Jung-uk Kim wrote: > > On 18. 10. 24., Warner Losh wrote: > >> On Wed, Oct 24, 2018 at 10:33 AM Harry Newton wrote: > >> > >>> gryphon# efivar -N --hex $(efivar | grep Boot0002) > >>> 00

Re: UEFI boot hangs after loader

2018-10-26 Thread Warner Losh
I've recreated something like this in efivar as well... I need to study the code for how to improve it to have sanity limits... I hope to have a patch soon... Thanks for this data point. I think I'm on the right track. Warner On Fri, Oct 26, 2018 at 3:47 PM Harry Newton wrote: > So patching

Re: 12-BETA1 contains warning about non-PNP ISA device

2018-10-25 Thread Warner Losh
On Thu, Oct 25, 2018 at 10:46 AM Warner Losh wrote: > > > On Thu, Oct 25, 2018 at 10:26 AM Rebecca Cran > wrote: > >> On 10/25/18 10:20 AM, Rebecca Cran wrote: >> >> > >> > uart0 pnpinfo _HID=AMDI0020 _UID=0 at handle=\_SB_.FUR0 >> >

Re: 12-BETA1 contains warning about non-PNP ISA device

2018-10-25 Thread Warner Losh
On Thu, Oct 25, 2018 at 10:26 AM Rebecca Cran wrote: > On 10/25/18 10:20 AM, Rebecca Cran wrote: > > > > > uart0 pnpinfo _HID=AMDI0020 _UID=0 at handle=\_SB_.FUR0 > > uart1 pnpinfo _HID=AMDI0020 _UID=1 at handle=\_SB_.FUR1 > > uart2 pnpinfo _HID=AMDI0020 _UID=2 at handle=\_SB_.FUR2 >

Re: pkg problem on FreeBSD 13.0-CURRENT

2018-10-25 Thread Warner Losh
On Thu, Oct 25, 2018 at 10:17 AM Kurt Jaeger wrote: > Hi! > > > On 10/25/18 5:19 PM, Sean Bruno wrote: > > > pkg-static install -f pkg > > > > It works better now, but there are some complaints. > > If it's only the certificate issue, try this: > > cd /usr/local/etc > cp pkg.conf.sample pkg.conf

Re: 12-BETA1 contains warning about non-PNP ISA device

2018-10-25 Thread Warner Losh
On Thu, Oct 25, 2018 at 10:16 AM Rebecca Cran wrote: > On 10/25/18 10:00 AM, Warner Losh wrote: > > > > > I suspect you can just lose those hints in the hints file and be fine. > The > > uart should attach via acpi. The keyboard won't, however, since it isn't > &

Re: 12-BETA1 contains warning about non-PNP ISA device

2018-10-25 Thread Warner Losh
On Thu, Oct 25, 2018 at 9:35 AM Rebecca Cran wrote: > On 10/25/18 5:02 AM, Rodney W. Grimes wrote: > > > Can you please reply with the specific device. > > If you have seen one it may be an issue to removing it, > > especially if this is on a "new AMD" system. > > > This is a new Ryzen system.

Re: 12-BETA1 contains warning about non-PNP ISA device

2018-10-25 Thread Warner Losh
On Thu, Oct 25, 2018 at 8:10 AM Eric van Gyzen wrote: > On 10/25/18 6:57 AM, Rodney W. Grimes wrote: > >>> I noticed a warning on a new AMD system running 12-BETA1: > >>> > >>> non-PNP ISA device will be removed from GENERIC in FreeBSD 12. > >> Can you please reply with the specific device. > >>

Re: UEFI boot hangs after loader

2018-10-24 Thread Warner Losh
On Wed, Oct 24, 2018 at 11:47 AM Jung-uk Kim wrote: > On 18. 10. 24., Warner Losh wrote: > > On Wed, Oct 24, 2018 at 10:33 AM Harry Newton wrote: > > > >> gryphon# efivar -N --hex $(efivar | grep Boot0002) > >> : 01 00 00 00 98 00 55 00 45 00 46 00 49 00 3

Re: UEFI boot hangs after loader

2018-10-24 Thread Warner Losh
00 30 00 31 00 2e 00 30 00 30 00 00 00 > 00e0: 7f ff 04 00 00 00 42 4f > gryphon# > Perfect. I'll decode this and see if I can figure out where we're going AFU. Warner > On 24 October 2018 at 15:09, Warner Losh wrote: > >> >> >> On Wed, Oct 24, 2018 at 7:05 A

Re: UEFI boot hangs after loader

2018-10-24 Thread Warner Losh
On Wed, Oct 24, 2018 at 9:36 AM Toomas Soome wrote: > > > > On 24 Oct 2018, at 00:51, Kyle Evans wrote: > > > > Hi, > > > > I suspect 4th vs. lua has no impact here, given the output shown -- > > can you throw one of the installer images [0] on some removable media > > and give that a shot for

Re: UEFI boot hangs after loader

2018-10-24 Thread Warner Losh
On Wed, Oct 24, 2018 at 7:05 AM Harry Newton wrote: > Booted with the installer image makes efibootmgr to work as you said: > > gryphon# efibootmgr -v > BootCurrent: 0002 > Timeout : 2 seconds > BootOrder : 0001, 0002 > Boot0001* UEFI OS > >

Re: build is broken

2018-10-23 Thread Warner Losh
Konstantin fixed it a few minutes ago. Warner On Tue, Oct 23, 2018, 6:09 PM Martin Wilke wrote: > as of rev: 339671 > > build fails > > https://dpaste.de/NCeV/raw > > - Miwi > -- > +-oOO--(_)--OOo-+ > With best Regards, > Martin Wilke

Re: ctm(1) deprecation in the FreeBSD base system?

2018-10-23 Thread Warner Losh
On Tue, Oct 23, 2018 at 2:13 PM Rodney W. Grimes < freebsd-...@pdx.rh.cn85.dnsmgr.net> wrote: > > A cost(=time)/benefit look on moving ctm from src/ to ports/ : > > - No tangible architecture benefit (its not like purging an old driver > > to makes kernel support simpler, or avoiding clashing

Re: ctm(1) deprecation in the FreeBSD base system?

2018-10-23 Thread Warner Losh
On Tue, Oct 23, 2018, 12:18 PM Stefan Esser wrote: > Am 23.10.18 um 19:06 schrieb Warner Losh: > > > > > > On Tue, Oct 23, 2018 at 10:44 AM Stefan Esser > <mailto:s...@freebsd.org>> wrote: > > > > Am 23.10.18 um 17:27 schrieb Montgomery-Smith,

Re: ctm(1) deprecation in the FreeBSD base system?

2018-10-23 Thread Warner Losh
On Tue, Oct 23, 2018 at 10:44 AM Stefan Esser wrote: > Am 23.10.18 um 17:27 schrieb Montgomery-Smith, Stephen: > > I have no problem turning ctm into a port. But I would appreciate > > advice on whether there is a standard or easy process for converting > > software from the FreeBSD base to a

Re: loader lsdev crashes loader (Was: head -r338804 boots threadripper 1950X fine; head -r338810+ do not; -r338807 seems implicated)

2018-10-23 Thread Warner Losh
On Tue, Oct 23, 2018 at 5:54 AM Toomas Soome wrote: > > > On 23 Oct 2018, at 13:53, Lev Serebryakov wrote: > > > > On 22.10.2018 12:27, Toomas Soome wrote: > > > >> It would help to get output from loader lsdev -v command. > > current loader crashes on "lsdev" for me: > >

Re: ctm(1) deprecation in the FreeBSD base system?

2018-10-22 Thread Warner Losh
On Mon, Oct 22, 2018 at 2:40 PM Rodney W. Grimes < freebsd-...@pdx.rh.cn85.dnsmgr.net> wrote: > > > > In message <201810221957.w9mjvdxx012...@pdx.rh.cn85.dnsmgr.net>, > "Rodney W. Gri > > mes" writes: > > > > >I do not know that other than I do know that I have seen > > >one data point

Re: head -r338804 boots threadripper 1950X fine; head -r338810+ do not; -r338807 seems implicated

2018-10-22 Thread Warner Losh
On Mon, Oct 22, 2018 at 6:39 AM Mark Millard wrote: > On 2018-Oct-22, at 4:07 AM, Toomas Soome wrote: > > > On 22 Oct 2018, at 13:58, Mark Millard wrote: > >> > >> On 2018-Oct-22, at 2:27 AM, Toomas Soome wrote: > >>> > >>>> On 22 Oct

Re: head -r338804 boots threadripper 1950X fine; head -r338810+ do not; -r338807 seems implicated

2018-10-21 Thread Warner Losh
On Sun, Oct 21, 2018 at 9:28 PM Warner Losh wrote: > > > On Sun, Oct 21, 2018 at 8:57 PM Mark Millard via freebsd-stable < > freebsd-sta...@freebsd.org> wrote: > >> [I built based on WITHOUT_ZFS= for other reasons. But, >> after installing the build, H

Re: head -r338804 boots threadripper 1950X fine; head -r338810+ do not; -r338807 seems implicated

2018-10-21 Thread Warner Losh
On Sun, Oct 21, 2018 at 8:57 PM Mark Millard via freebsd-stable < freebsd-sta...@freebsd.org> wrote: > [I built based on WITHOUT_ZFS= for other reasons. But, > after installing the build, Hyper-V based boots are > working.] > > On 2018-Oct-20, at 2:09 AM, Mark Millard wrote: > > > On

Re: DRM: radeonkms … can not be unloaded (kernel panic)) …

2018-10-21 Thread Warner Losh
On Sun, Oct 21, 2018, 2:29 AM Kevin Oberman wrote: > On Sat, Oct 20, 2018 at 1:28 AM Hans Petter Selasky > wrote: > > > On 10/20/18 3:10 AM, Graham Perrin wrote: > > > On 20/10/2018 00:01, Graham Perrin wrote: > > > > > >> kldunload radeonkms > > >> > > >> – results in a kernel panic. > > > > >

Re: head -r339076's boot loader fails to boot threadripper 1950X system (BTX halted); an earlier version works [ -r336532 broke it ]

2018-10-21 Thread Warner Losh
On Sat, Oct 20, 2018 at 11:04 PM Mark Millard wrote: > [I found what change lead to the 1950X boot crashing > with BTX halted.] > > On 2018-Oct-20, at 12:44 PM, Mark Millard wrote: > > > [Adding some vintage information for a loader > > that allowed a native boot.] > > > > On 2018-Oct-20, at

SCSI and dmesg

2018-10-20 Thread Warner Losh
Greetings a few weeks ago I pointed people to the nycbug dmesg service. I said I was looking at data to drive SCSI retirement. I've gatherd some preliminary data, which I've uploaded to https://github.com/bsdimp/device-data/blob/master/cam.md along with some preliminary notions of disposition for

Re: vm_fault on boot with NVMe/nda

2018-10-15 Thread Warner Losh
At Netflix we have our OCA firmware based on FreeBSD -current (we take a snapshot every 5 weeks or so). We've been booting thousands of machines off nda for over a year... It absolutely works and is one of the things that lets us deliver the content we do... I have some patches in my queue

Re: drm confusion / xorg / AMD RX580 GPU

2018-10-08 Thread Warner Losh
On Mon, Oct 8, 2018 at 7:32 AM Hans Petter Selasky wrote: > On 10/8/18 3:06 PM, Warner Losh wrote: > > You need "/boot/kernel/amdgpu.ko" here > > > > Warner > > Or did you mean: > > /boot/modules/amdgpu.ko > Doh! You're right. You need the one ins

Re: dmesg submission service -- please submit today

2018-10-08 Thread Warner Losh
On Mon, Oct 8, 2018 at 1:37 AM Thomas Mueller wrote: > I just submitted /var/run/dmesg.boot from my current NetBSD and from > FreeBSD 11.1-STABLE. > > I was surprised to see some other BSD OSes listed, including 5 dmesg > reports from Bitrig and 3 from RetroBSD. > > I had been tracking three

Re: drm confusion / xorg / AMD RX580 GPU

2018-10-08 Thread Warner Losh
On Mon, Oct 8, 2018 at 6:47 AM tech-lists wrote: > Hi, > > context: 12-alpha8, amd64, xorg, AMD rx580 card > > As per /usr/ports/UPDATING, I have installed graphics/drm-kmod which has > installed drm-next-kmod-4.11.g20180822 > > As per pkg message, it's loaded with this line in /etc/rc.conf: > >

Re: dmesg submission service -- please submit today

2018-10-07 Thread Warner Losh
On Sun, Oct 7, 2018 at 3:49 AM Konstantin Belousov wrote: > On Sat, Oct 06, 2018 at 11:40:36PM -0600, Warner Losh wrote: > > On Sat, Oct 6, 2018 at 12:48 PM Warner Losh wrote: > > > > > Greetings, > > > > > > As you can tell, the project is looking to c

Re: dmesg submission service -- please submit today

2018-10-07 Thread Warner Losh
On Sun, Oct 7, 2018 at 2:16 AM Dhananjay Balan wrote: > On Sat, Oct 06, 2018 at 11:40:36PM -0600, Warner Losh wrote: > > On Sat, Oct 6, 2018 at 12:48 PM Warner Losh wrote: > > > > > Greetings, > > > > > > As you can tell, the project is looking to c

Re: dmesg submission service -- please submit today

2018-10-07 Thread Warner Losh
On Sat, Oct 6, 2018 at 12:48 PM Warner Losh wrote: > Greetings, > > As you can tell, the project is looking to clear some of the deadwood from > its driver lists. One problem is that we have to guess what's in used based > on our personal experience. This has proven to be les

dmesg submission service -- please submit today

2018-10-06 Thread Warner Losh
Greetings, As you can tell, the project is looking to clear some of the deadwood from its driver lists. One problem is that we have to guess what's in used based on our personal experience. This has proven to be less reliable than hoped in the 10/100 discussions that are going on now. So, to

Re: drm-kmod, drm-next-kmod, radeonkms.ko, suspend and resume

2018-10-06 Thread Warner Losh
On Sat, Oct 6, 2018 at 10:22 AM Kevin Oberman wrote: > Due to lack of space on /var, I am unable to get a dump. (I'll get that > fixed soon, but shuffling partitions take more time than I have right now. > You can run savecore after you boot the system and direct its output to another

Re: AMD RAID support?

2018-10-04 Thread Warner Losh
On Thu, Oct 4, 2018 at 10:37 AM Allan Jude wrote: > On 2018-10-04 12:29, Zaphod Beeblebrox wrote: > > Are there any plans to support AMD RAID? > > > > AMD RAID is _like_ Intel RAID, but has a number of differences. One is > > that it requires UEFI (without UEFI it does not boot, at least). It

Re: UEFI Loader problems in CURRENT

2018-09-29 Thread Warner Losh
swell if there were a cheap to obtain box that exhibits this problem. Warner On Sat, Sep 29, 2018 at 6:14 PM Warner Losh wrote: > Sadly both of these bugs are thin on detail beyond it doesn't work. Makes > it hard to even look into it. > > Warner > > On Sat, Sep 29, 2018, 6

Re: UEFI Loader problems in CURRENT

2018-09-29 Thread Warner Losh
Sadly both of these bugs are thin on detail beyond it doesn't work. Makes it hard to even look into it. Warner On Sat, Sep 29, 2018, 6:00 PM Yuri wrote: > See: > > * https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=230090 > > * https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=219957 > > >

Re: drm2 in base

2018-09-28 Thread Warner Losh
On Fri, Sep 28, 2018 at 2:02 PM Steve Kargl < s...@troutmask.apl.washington.edu> wrote: > On Fri, Sep 28, 2018 at 02:47:39PM -0500, Matthew D. Fuller wrote: > > On Fri, Sep 28, 2018 at 11:00:02AM -0700 I heard the voice of > > Steve Kargl, and lo! it spake thus: > > > > > > I have a radeon HD

Re: drm2 in base

2018-09-28 Thread Warner Losh
On Fri, Sep 28, 2018 at 12:01 PM Steve Kargl < s...@troutmask.apl.washington.edu> wrote: > > At the risk of raising the ire of others, but with the pending > branching for FreeBSD 12, I respectfully request that drm2 > remain in head after the branch. The current plans, which are still being

Re: FreeBSD-12-ALPHA6: Network not starting at boot & can't start Plasma 5

2018-09-23 Thread Warner Losh
On Sun, Sep 23, 2018, 6:11 AM Graham Perrin wrote: > No problem with Plasma here with > FreeBSD 12.0-ALPHA7 r338892 GENERIC-NODEBUG > built and installed a few hours ago. > > Prior to that I used an alpha from … probably mid-August. No problem with > networking after startup, and no post-startup

Re: building head -r338675 with devel/amd64-gcc: /usr/local/x86_64-unknown-freebsd12.0/bin/ld: warning: -z ifunc-noplt ignored

2018-09-21 Thread Warner Losh
On Fri, Sep 21, 2018 at 9:59 PM Rebecca Cran wrote: > On 9/21/18 9:57 PM, Warner Losh wrote: > > > Hmmm, what does make -V LINKER_TYPE and make -V LINKER_FEATURES say? > > > > They look good for me, but the only way you get this error is if they > > are wrong

Re: building head -r338675 with devel/amd64-gcc: /usr/local/x86_64-unknown-freebsd12.0/bin/ld: warning: -z ifunc-noplt ignored

2018-09-21 Thread Warner Losh
s from the host as well, even though we rebuild them... Warner On Fri, Sep 21, 2018 at 9:38 PM Rebecca Cran wrote: > On 9/21/18 9:35 PM, Warner Losh wrote: > > > > I meant to add, can you give a few lines before the error is spewed > > here in email? My IRC computer died before

Re: building head -r338675 with devel/amd64-gcc: /usr/local/x86_64-unknown-freebsd12.0/bin/ld: warning: -z ifunc-noplt ignored

2018-09-21 Thread Warner Losh
On Fri, Sep 21, 2018 at 9:34 PM Warner Losh wrote: > > > On Fri, Sep 21, 2018 at 9:30 PM Rebecca Cran wrote: > >> On 9/21/18 9:09 PM, Warner Losh wrote: >> >> > On Fri, Sep 21, 2018 at 9:02 PM Rebecca Cran via freebsd-toolchain < >> > freebsd-toolch

Re: building head -r338675 with devel/amd64-gcc: /usr/local/x86_64-unknown-freebsd12.0/bin/ld: warning: -z ifunc-noplt ignored

2018-09-21 Thread Warner Losh
On Fri, Sep 21, 2018 at 9:30 PM Rebecca Cran wrote: > On 9/21/18 9:09 PM, Warner Losh wrote: > > > On Fri, Sep 21, 2018 at 9:02 PM Rebecca Cran via freebsd-toolchain < > > freebsd-toolch...@freebsd.org> wrote: > > > >> On 9/21/18 4:06 PM, Mark Johnston w

Re: building head -r338675 with devel/amd64-gcc: /usr/local/x86_64-unknown-freebsd12.0/bin/ld: warning: -z ifunc-noplt ignored

2018-09-21 Thread Warner Losh
On Fri, Sep 21, 2018 at 9:02 PM Rebecca Cran via freebsd-toolchain < freebsd-toolch...@freebsd.org> wrote: > On 9/21/18 4:06 PM, Mark Johnston wrote: > > > > https://reviews.freebsd.org/D17279 for anyone else that would like to > > review. > > > Is that possibly related to the error I'm getting

Re: FreeBSD EFI projects

2018-09-19 Thread Warner Losh
On Wed, Sep 19, 2018 at 4:33 PM Rebecca Cran wrote: > Oh, that's a really good point - thanks! I happen to have a Minnowboard > Turbot currently sitting unused. > One other idea, unrelated to the 32-bit UEFI to boot 64-bit kernel, is to see about mining tsoome@'s port of FreeBSD boot loader to

Re: FreeBSD EFI projects

2018-09-17 Thread Warner Losh
On Sun, Sep 16, 2018 at 11:29 PM Rebecca Cran wrote: > On 9/16/18 9:32 PM, Warner Losh wrote: > > > > > What did you have in mind working on? I have a few things that are in > > various stages of completeness around this issue that I've not had > > time to polish o

Re: FreeBSD EFI projects

2018-09-16 Thread Warner Losh
On Sun, Sep 16, 2018 at 4:31 PM Rebecca Cran wrote: > I'm just getting back into FreeBSD development, and I'm trying to focus > on (U)EFI work. > > It seems there are various things that people would like to have done, > some of which are listed on >

  1   2   3   4   5   6   7   8   9   10   >