From owner-freebsd-current@freebsd.org Thu May 31 07:35:23 2018 Return-Path: Delivered-To: freebsd-current@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 1B5B5FC9C2A for ; Thu, 31 May 2018 07:35:23 +0000 (UTC) (envelope-from johalun0@gmail.com) Received: from mail-wm0-x244.google.com (mail-wm0-x244.google.com [IPv6:2a00:1450:400c:c09::244]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 8822E753D3; Thu, 31 May 2018 07:35:22 +0000 (UTC) (envelope-from johalun0@gmail.com) Received: by mail-wm0-x244.google.com with SMTP id r15-v6so24463822wmc.1; Thu, 31 May 2018 00:35:22 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=kxemJCt05hBAKntgVopK5ZTZJy2E0aL0EejUpztx/sc=; b=Me2c4woBggdO13tDEKuPVH+AwpqMGQ4/OazHc3b5wwVq2cspTNEOKv00t0UI0HhbqM nQ7hjrsdwfOR/deb0Xg46m83QhnoVJUvOOs8ed0YFzC4MUMF/pJI8pwGVtcqfsplztVi EMAwn+vEEJYyRrj1d+5X1LS6qGupdUOXW7svkVrN2R++RH5vBcJcz91P1vhGc00Yxt+O LA4dKQDtTRKcvFgb10PCf6XJbTpw3I/p3yPiiA0rIKbSCdFoHPPFyFV7fb3fgVgGoWqy Q0mVTlC+0qdvRm1XVsbPY8DJaV4Mp09lNKj5zbHFj6DEJiQl+uSjKq00NhnPyt8TgZLi hIZA== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=kxemJCt05hBAKntgVopK5ZTZJy2E0aL0EejUpztx/sc=; b=pDg0M7xfPCtFSM33b3uFaju4bafrW+eWdwnaRdB4pyGDElORialHSjkQhG6WxsG4EY Tp4GyY6dxwgmFWK3C52Vw1GD1KFuy8esQMx+Gy8MdCRLa0fpdqTlH3N67wGE0HguclnV Ed1On7CSNJ95SE4RALDWXhl+ncRLQd9xbk+e4UNyK+JaDZNWKhQmlGAZL6v1SevUQlQX YaaumqUgmWWWk+78YtTtUcnfIiBax+yIiGyfN3uoj2fi+8AsILz2Fqgn1u8bccb/A0c/ 99t912EugB6WWGPHsIrRxZxZuUwJ6NdsHDTDHbFrisKeBstuhTUZldI4z/DHHV47FNeJ dRqg== X-Gm-Message-State: ALKqPwczLdbtXf4iZG5kgaB4EwE2/kmta2rA+4xwSYSiJzy9OCd54TYW T0ikzQDVBvd2VUF7/ovpVzQEU3/+YGKOTq419CM= X-Google-Smtp-Source: ADUXVKIM6oAuQDjPYXGDbGZAscWxP+FLBkMy5eJPWi0TAbTDgf3wysUpkWS7COsDMwDkDbGSAF1CSCHHphmoqIeDTbQ= X-Received: by 2002:a1c:f714:: with SMTP id v20-v6mr3686910wmh.73.1527752121335; Thu, 31 May 2018 00:35:21 -0700 (PDT) MIME-Version: 1.0 References: <20180524160234.GD68014@FreeBSD.org> <201805241610.w4OGAAGY041280@pdx.rh.CN85.dnsmgr.net> <20180530235156.310870d0@thor.intern.walstatt.dynvpn.de> In-Reply-To: <20180530235156.310870d0@thor.intern.walstatt.dynvpn.de> From: Johannes Lundberg Date: Thu, 31 May 2018 08:34:44 +0100 Message-ID: Subject: Re: [RFC] Deprecation and removal of the drm2 driver To: ohartmann@walstatt.org Cc: freebsd-rwg@pdx.rh.cn85.dnsmgr.net, gjb@freebsd.org, Philip Homburg , "K. Macy" , AWilcox@wilcox-tech.com, freebsd-current , Ed Maste Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable X-Content-Filtered-By: Mailman/MimeDel 2.1.26 X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.26 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 31 May 2018 07:35:23 -0000 On Wed, May 30, 2018 at 10:57 PM O. Hartmann wrote= : > -----BEGIN PGP SIGNED MESSAGE----- > Hash: SHA512 > > Am Thu, 24 May 2018 09:10:10 -0700 (PDT) > "Rodney W. Grimes" schrieb: > > > -- Start of PGP signed section. > > > On Thu, May 24, 2018 at 08:22:12AM -0700, Rodney W. Grimes wrote: > > > > > On Wed, May 23, 2018 at 11:48:38AM +0200, Philip Homburg wrote: > > > > > > >Also as the Moore's law curve flattens expect the life of thes= e > > > > > > >older, but not so old, machines to live quiet some time. I > > > > > > >believe we are talking sandy bridge and earlier? If that is > > > > > > >corret Sandy bridge is still a very viable system. > > > > > > > > > > > > I noticed this lack of love for older systems recently. > > > > > > > > > > > > I wanted to use an older Dell server to test the 11.2 BETAs and > RCs. > > > > > > > > > > > > Turns out, you can't install FreeBSD using a USB stick image > because the > > > > > > BIOS only support MBR. No idea why MBR support was dropped for > the USB images. > > > > > > > > > > > > In the end I had to find a CD burner, and after a couple of > tries managed to > > > > > > install from CD. > > > > > > > > > > > > After that, my ansible playbooks started failing because > /boot/loader.conf > > > > > > is absent if you boot from zfs in combination with MBR. > > > > > > > > > > > > Pity. This older server hardware is great for trying out new > releases, play > > > > > > with zfs, etc. > > > > > > > > > > The disc1.iso (as well as bootonly.iso and dvd1.iso) images are n= ow > > > > > built as hybrid images, supporting both MBR and GPT, as well as > being > > > > > written to a flash drive (like memstick.img) as well as a CD. > > > > > > > > To clarify a minor point here, are the amd64 disc1.iso images or > > > > both the amd64 and i386 disk1.iso images being built as "hybrid"? > > > > > > > > > > Only amd64. i386 does not have UEFI-/GPT-related boot issues. > > > > Here is a data point: > > > > Test system is Dell R710, > > First attempt is with BIOS in Boot mode: Bios > > Second attempt is with BIOS in Boot mode: UEFI > > > > Attemtped to boot amd64 version: > > Screen goes white background, text appears (yes, way indented) > > BTX version is 1.02 > > Consoles: internal video/keyboard > > _ > > > > That last _ is a blinking cursor, system is hung, does repsond to C-A-d= el > > > > > > Second attempt: > > Works properly > > > > > > I am going after Ed Maste's posted build image in the other thread now.= .. > > > > > > > > > > > As this is what I see on my system: > > > > root@x230a:/home/ISO/x # file FreeBSD-11.2-BETA2-* > > > > FreeBSD-11.2-BETA2-amd64-disc1.iso: DOS/MBR boot sector; partition = 1 > : ID=3D0xee, > > > > start-CHS (0x0,0,2), end-CHS (0x3ff,255,63), startsector 1, 1472695 > sectors > > > > FreeBSD-11.2-BETA2-i386-disc1.iso: ISO 9660 CD-ROM filesystem data > > > > '11_2_BETA2_I386_CD' (bootable) > > > > > MBR support was initially removed from the memstick installer, as > it is > > > > > not compatible with some UEFI implementations. (Or, at least tha= t > is my > > > > > understanding, based on my limited intimate knowledge of UEFI.) > > > > > > > > > > > Glen > > > > > -- End of PGP section, PGP failed! > > > > Today, I tried to eliminate FreeBSD's native KMS drm2 by installing > graphics/drm-stable-kmod (ports tree at revision 471172) on CURRENT > (FreeBSD 12.0-CURRENT > #46 r334401: Wed May 30 23:32:45 CEST 2018 amd64, CUSTOM kernel). > > The hardware is a presumably UEFI capable ASROCK Z77-Pro4M (latest > firmware available > from late 2013) equipted with a XEON IvyBridge: > > CPU: Intel(R) Xeon(R) CPU E3-1245 V2 @ 3.40GHz (3400.09-MHz K8-class CPU) > Origin=3D"GenuineIntel" Id=3D0x306a9 Family=3D0x6 Model=3D0x3a Step= ping=3D9 > > Features=3D0xbfebfbff > > Features2=3D0x7fbae3ff > AMD Features=3D0x28100800 > AMD Features2=3D0x1 > Structured Extended Features=3D0x281 > XSAVE Features=3D0x1 > VT-x: PAT,HLT,MTF,PAUSE,EPT,UG,VPID > TSC: P-state invariant, performance statistics > real memory =3D 17179869184 (16384 MB) > avail memory =3D 16295137280 (15540 MB) > Event timer "LAPIC" quality 600 > ACPI APIC Table: > FreeBSD/SMP: Multiprocessor System Detected: 8 CPUs > > > The box isn't capable of booting FreeBSD in UEFI (while Linux and Windows > seems to work). > So I'm stuck with BIOS. > > Loading i915kms.ko/drm2.ko on the system put the console in a > high-resolution mode > instead of this crap 80x25 ancient console immediately. > > Loading graphics/drm-stable-kmod as requested (via rc.conf.local) ends up > in a trap > 12/crash. Very nice for such an old hardware. graphics/drm-next-kmod does > load without > crashing the system - but the console is stuck in the clumsy 80x25 mode. > > So why should I vote for non-working drivers to replace perfectly working > ones? > > oh > > We're not replacing anything. We are moving the older drm1 and drm2 from kernel to ports to make it easier for the majority of the users to load the correct driver without conflicts. We have updated drm-stable-kmod so that it now works on some older amd64 system also covered by drm2 but as always, ymmv. drm2 will later be available as drm-legacy-kmod or something like that (name to be announced later). Simply use/install the one that works best for you. > > - -- > O. Hartmann > > Ich widerspreche der Nutzung oder =C3=9Cbermittlung meiner Daten f=C3=BCr > Werbezwecke oder f=C3=BCr die Markt- oder Meinungsforschung (=C2=A7 28 Ab= s. 4 BDSG). > -----BEGIN PGP SIGNATURE----- > > iLUEARMKAB0WIQQZVZMzAtwC2T/86TrS528fyFhYlAUCWw8c/AAKCRDS528fyFhY > lBl7Af0R7ymOzkWp7GcqymhUiOgfy3qvTSmHYgbTzYxsD54GEIfoAMvH1pHFp4yL > b0NYx9HR+BU3d6GAf0Xq0sq78kMFAf9KUhDMLUHf06+ASJkS2uPyr+jZBZeBlTRc > IsE0PaxErbYy8YLJhWXgrSYCM1KHIZisBNUOLGckcCIgTvu0MRsQ > =3DyFzW > -----END PGP SIGNATURE----- > _______________________________________________ > freebsd-current@freebsd.org mailing list > https://lists.freebsd.org/mailman/listinfo/freebsd-current > To unsubscribe, send any mail to "freebsd-current-unsubscribe@freebsd.org= " >