Re: Linux is considering dropping x32.
:))) On Wed, Dec 12, 2018 at 12:56 AM Nathan Whitehorn wrote: > > > On 12/11/18 1:04 PM, Kris Moore wrote: > > On 12/11/18 4:01 PM, Alexandre C. Guimarães wrote: > >> Hi. > >> > >> This is just informative. > >> > >> Apparently Linux is considering deprecate x32 support: > >> > >> https://lkml.org/lkml/2018/12/10/1151 > >> > >> Cheers! > >> > > Hey that's great! Now that the precedent is set, we start the timer to > > deprecate on FreeBSD in roughly 10 years now :) > > > > Or maybe we are ahead of the game since we never supported x32 in the > first place? > -Nathan > ___ > freebsd-current@freebsd.org mailing list > https://lists.freebsd.org/mailman/listinfo/freebsd-current > To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org" > ___ freebsd-current@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"
Re: update of graphics/drm-next-kmod to Linux 4.11 level for recent CURRENT and 11-STABLE
Hey Pete, Thanks for the help, updated to newer revision (r330133) and it resolved the problem :) On Thu, Mar 1, 2018 at 2:41 AM, Pete Wright wrote: > > > On 2/28/18 2:47 PM, Hadi Rezaee wrote: > > Thanks Pete, i’ll try your solution. But just wanted to report back > > the system current revision: r329639 > > > > > sounds great, let me know how it looks. > > i suggest we move the rest of this discussion to the > freebsd-...@freebsd.org list so we don't SPAM the -current list. > > cheers! > -pete > > -- > Pete Wright > p...@nomadlogic.org > 310.309.9298 > > ___ freebsd-current@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"
Re: update of graphics/drm-next-kmod to Linux 4.11 level for recent CURRENT and 11-STABLE
Thanks Pete, i’ll try your solution. But just wanted to report back the system current revision: r329639 On Wed, Feb 28, 2018 at 11:42 PM Pete Wright wrote: > > > On 2/28/18 2:30 PM, Hadi Rezaee wrote: > > Hello Pete, sorry I’m on trip so i cannot output the logs in proper > > way. About i915 kernel module please refer to screen shot. > > > > I can confirm that i915 module is not getting loaded normaly at system > > startup, so kldstat shows nothing. > > > > Yes, the user is already in video group. (Generally didnt changed > > anything on system config, just updated pkg and this happend) > > thanks for posting the screen shot - it looks like your kernel and world > may not be recent enough to load the kld. i'd suggest pulling the > latest code from svn or git for 12-CURRENT then removing and > reinstalling the drm-next-kmod pkg after you have booted into this fresh > checkout. > > that's the first thing that comes to my mind when seeing that your > kernel is unable to handle these modules. you also may want to remove > the drm-next-kmod package and ensure there are no artifacts left behind > in /boot/modules/ that were installed via the pkg, then re-install from > the upstream pkg servers. > > hope this helps, > -pete > > -- > Pete Wright > p...@nomadlogic.org > 310.309.9298 > > ___ freebsd-current@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"
Re: update of graphics/drm-next-kmod to Linux 4.11 level for recent CURRENT and 11-STABLE
Hello there, My laptop is running FreeBSD-12 CURRENT, and i hadnt any problem with my graphic before upgrading drm-next (g20180117_3 -> 4.11.g20180224). But now it getting failed. Tried to build from source, but same result. Laptop model: Lenovo E470 On Wed, Feb 28, 2018 at 5:56 PM Jan Bramkamp wrote: > On 25.02.18 16:48, Johannes M Dieterich wrote: > > Dear all, > > > > Please CC me as I am not subscribed. > > > > On behalf of the FreeBSDDesktop team and thanks to the tireless efforts > > of Johannes Lundberg and Hans Petter Selasky (hselasky), I am pleased to > > report that the graphics/drm-next-kmod port just received an update to > > Linux level 4.11 KMS/DRM for amdgpu, radeon, and i915 for both recent > > CURRENT and 11-STABLE. > > > > We have tested this on a range of hardware ourselves: > > * Haswell > > * Broadwell > > * Skylake > > * Evergreen > > * Kaveri (both radeon and amgpu KMS) > > * Carrizo > > * Polaris > > > > Needless to say, the possible space of hardware this could run on is > > significantly larger. Hence, if you find issues and/or want to propose > > patches, please do so at our development github: > > > > https://github.com/FreeBSDDesktop/kms-drm > > > > We absolutely do welcome contributions! > > > > Johannes > > Thx for your hard work. The drm-next-kmod port enabled me to finally > replace my ageing Thinkpad X220 with newer hardware. > > The latest update (g20180117_3 -> 4.11.g20180224) to the drm-next-kmod > port introduced a regression which causes Xorg on my T470s running > 12-current from a few days ago to fail at startup stating that it didn't > find any screen. > ___ > freebsd-current@freebsd.org mailing list > https://lists.freebsd.org/mailman/listinfo/freebsd-current > To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org" > ___ freebsd-current@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"
Re: r328032 broke service
Yea actually wanted to report this as soon as i fix the problem on laptop ^^ On Tue, Jan 16, 2018 at 11:54 PM Kyle Evans wrote: > On Tue, Jan 16, 2018 at 5:00 PM, Oleg Ginzburg wrote: > > Looks like > https://svnweb.freebsd.org/base?view=revision&revision=r328032 > > breaks any other arguments except '-j' for service(8) > > Apologies, fixed in r328060 =( > ___ > freebsd-current@freebsd.org mailing list > https://lists.freebsd.org/mailman/listinfo/freebsd-current > To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org" > ___ freebsd-current@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"
