Date: Thu, 31 May 2018 13:16:43 +0300 From: Konstantin Belousov <kostikbel@gmail.com> To: Johannes Lundberg <johalun0@gmail.com> Cc: freebsd-current <freebsd-current@freebsd.org> Subject: Re: [RFC] Deprecation and removal of the drm2 driver Message-ID: <20180531101643.GV3789@kib.kiev.ua> In-Reply-To: <CAECmPwvFkO6Qc_7kZowCHdSEVQwV12ZomsbTe4=X=sp7pW=7Kg@mail.gmail.com> References: <20180524160234.GD68014@FreeBSD.org> <201805241610.w4OGAAGY041280@pdx.rh.CN85.dnsmgr.net> <20180530235156.310870d0@thor.intern.walstatt.dynvpn.de> <CAECmPwvFkO6Qc_7kZowCHdSEVQwV12ZomsbTe4=X=sp7pW=7Kg@mail.gmail.com>
next in thread | previous in thread | raw e-mail | index | archive | help
On Thu, May 31, 2018 at 08:34:44AM +0100, Johannes Lundberg wrote: > On Wed, May 30, 2018 at 10:57 PM O. Hartmann <ohartmann@walstatt.org> wrote: > > > -----BEGIN PGP SIGNED MESSAGE----- > > Hash: SHA512 > > > > Am Thu, 24 May 2018 09:10:10 -0700 (PDT) > > "Rodney W. Grimes" <freebsd-rwg@pdx.rh.CN85.dnsmgr.net> 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 these > > > > > > > >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 now > > > > > > 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-del > > > > > > > > > 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=0xee, > > > > > 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 that > > 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="GenuineIntel" Id=0x306a9 Family=0x6 Model=0x3a Stepping=9 > > > > Features=0xbfebfbff<FPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,CLFLUSH,DTS,ACPI,MMX,FXSR,SSE,SSE2,SS,HTT,TM,PBE> > > > > Features2=0x7fbae3ff<SSE3,PCLMULQDQ,DTES64,MON,DS_CPL,VMX,SMX,EST,TM2,SSSE3,CX16,xTPR,PDCM,PCID,SSE4.1,SSE4.2,x2APIC,POPCNT,TSCDLT,AESNI,XSAVE,OSXSAVE,AVX,F16C,RDRAND> > > AMD Features=0x28100800<SYSCALL,NX,RDTSCP,LM> > > AMD Features2=0x1<LAHF> > > Structured Extended Features=0x281<FSGSBASE,SMEP,ERMS> > > XSAVE Features=0x1<XSAVEOPT> > > VT-x: PAT,HLT,MTF,PAUSE,EPT,UG,VPID > > TSC: P-state invariant, performance statistics > > real memory = 17179869184 (16384 MB) > > avail memory = 16295137280 (15540 MB) > > Event timer "LAPIC" quality 600 > > ACPI APIC Table: <ALASKA A M I> > > 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. You do understand that you increase your maintainence load by this move. dev/drm and dev/drm2 use KPIs which cannot be kept stable even in stable branches, so you will need to chase these updates. > > 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 ??bermittlung meiner Daten f??r > > Werbezwecke oder f??r die Markt- oder Meinungsforschung (?? 28 Abs. 4 BDSG). > > -----BEGIN PGP SIGNATURE----- > > > > iLUEARMKAB0WIQQZVZMzAtwC2T/86TrS528fyFhYlAUCWw8c/AAKCRDS528fyFhY > > lBl7Af0R7ymOzkWp7GcqymhUiOgfy3qvTSmHYgbTzYxsD54GEIfoAMvH1pHFp4yL > > b0NYx9HR+BU3d6GAf0Xq0sq78kMFAf9KUhDMLUHf06+ASJkS2uPyr+jZBZeBlTRc > > IsE0PaxErbYy8YLJhWXgrSYCM1KHIZisBNUOLGckcCIgTvu0MRsQ > > =yFzW > > -----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" > > > _______________________________________________ > 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"
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20180531101643.GV3789>