From owner-freebsd-net@freebsd.org Sat Jun 22 08:21:21 2019 Return-Path: Delivered-To: freebsd-net@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id F20A515CF918 for ; Sat, 22 Jun 2019 08:21:20 +0000 (UTC) (envelope-from mueller6722@twc.com) Received: from dnvrco-cmomta02.email.rr.com (dnvrco-outbound-snat.email.rr.com [107.14.73.231]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "Client", Issuer "CA" (not verified)) by mx1.freebsd.org (Postfix) with ESMTPS id 1E3066E7F1 for ; Sat, 22 Jun 2019 08:21:17 +0000 (UTC) (envelope-from mueller6722@twc.com) Received: from localhost ([96.28.161.151]) by cmsmtp with ESMTP id ebGlhCWwliYm2ebGnh2lZG; Sat, 22 Jun 2019 08:21:10 +0000 Date: Sat, 22 Jun 2019 08:20:54 +0000 From: "Thomas Mueller" To: freebsd-net@freebsd.org Subject: Re: Working around unsupported Ethernet card with PXE or UEFI? References: <20190621023301.CRCA7107.dnvrco-fep06.email.rr.com@dnvrco-cmimta20> <39143.1561086356@segfault.tristatelogic.com> X-CMAE-Envelope: MS4wfClppO9FVsVgNyg4AqgDOm1BGWKs0Zulrn/DtEWmGN66mAAhUqGiYEUwE4RDsoSjEGXSm3RCKuBIs5PtY6x9gOfPYdUc6evqzm3r9rDRr5O1j0ceV5bg PGcDa6kJhBcmbwvkqZIbUOLcf1fVd5+I4kTYWmIC6lsvBSFPOYRI/3Pv X-Rspamd-Queue-Id: 1E3066E7F1 X-Spamd-Bar: -- Authentication-Results: mx1.freebsd.org; spf=pass (mx1.freebsd.org: domain of mueller6722@twc.com designates 107.14.73.231 as permitted sender) smtp.mailfrom=mueller6722@twc.com X-Spamd-Result: default: False [-2.52 / 15.00]; ARC_NA(0.00)[]; NEURAL_HAM_MEDIUM(-0.99)[-0.987,0]; FROM_HAS_DN(0.00)[]; R_SPF_ALLOW(-0.20)[+ip4:107.14.73.0/24]; FREEMAIL_FROM(0.00)[twc.com]; MIME_GOOD(-0.10)[text/plain]; MIME_TRACE(0.00)[0:+]; TO_DN_NONE(0.00)[]; RCPT_COUNT_ONE(0.00)[1]; NEURAL_HAM_LONG(-0.98)[-0.980,0]; MISSING_MID(2.50)[]; TO_MATCH_ENVRCPT_ALL(0.00)[]; MX_GOOD(-0.01)[dnvrco-cmedge02.email.rr.com,dnvrco-cmedge01.email.rr.com]; NEURAL_HAM_SHORT(-0.84)[-0.840,0]; RCVD_IN_DNSWL_NONE(0.00)[231.73.14.107.list.dnswl.org : 127.0.5.0]; IP_SCORE(-2.91)[ip: (-7.90), ipnet: 107.14.73.0/24(-3.65), asn: 7843(-2.92), country: US(-0.06)]; RCVD_TLS_LAST(0.00)[]; DMARC_NA(0.00)[twc.com]; FROM_EQ_ENVFROM(0.00)[]; RECEIVED_SPAMHAUS_PBL(0.00)[151.161.28.96.zen.spamhaus.org : 127.0.0.10]; R_DKIM_NA(0.00)[]; ASN(0.00)[asn:7843, ipnet:107.14.73.0/24, country:US]; SUBJECT_ENDS_QUESTION(1.00)[]; FREEMAIL_ENVFROM(0.00)[twc.com]; RCVD_COUNT_TWO(0.00)[2] X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: Networking and TCP/IP with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 22 Jun 2019 08:21:21 -0000 from Ronald F. Guilmette: > "Thomas Mueller" wrote: > >Is it possible to build and install FreeBSD so as to be bootable and access > >the internet with an Ethernet card that doesn't work in FreeBSD? > You're question doesn't make a lot of sense on the face of it. > Why on earth would you either WANT or NEED to install FreeBSD on a system > with no ethernet adapter? > If it's a matter of money, I have at least a half dozen old 10/100 cards > lying around collecting dust. If you send me your address and if it is > in North America, I'll send you one via snail-mail. Or you can probably > get one faster off eBay for about a buck and a half. You should have read more carefully, system has an ethernet adapter that worked on some past installations of FreeBSD, and works on NetBSD, System Rescue CD (Linux) and Haiku R1Alpha4 from November 2012. I use subversion built on NetBSD from pkgsrc to update FreeBSD src, ports and doc trees. Using GPT, UFS and no traditional BSD disklabels, FreeBSD and NetBSD can read and write to each other's partitions. I managed to boot FreeBSD 12-stable on this computer in UEFI mode and apparently get internet access with "dhclient re0". Then "host news.individual.net" worked correctly. Running ifconfig re0 up ifconfig re0 inet 192.168.0.2/24 route add default 192.168.0.1 seemed to connect, but then "host news.individual.net" failed (strange). Now to try on FreeBSD-current with UEFI, using dhclient? from Zaphod Beeblebrox: > I suppose he could be asking, in his way, about a type of universal driver > (not unlike ndis used to be). Not knowing anything about the UEFI > environment, but recalling that PXE requires one of the more restrictive > processor modes ... would make that quite a challenge for a universal > driver. > ... but yeah... USB ports are pretty ubiquitous. PXE boot could be done in BIOS mode as well as UEFI mode, but if selected from boot menu, would figure to be in UEFI mode. Hopefully I would be using the motherboard's support for the onboard ethernet rather than FreeBSD's support. But I am not sure if it would work like that. Tom