Re: CURRENT and HD3000: i915 failing badly

2018-02-01 Thread O. Hartmann 
On Thu, 1 Feb 2018 07:55:32 -0800
Cy Schubert  wrote:

> My laptop, a 2012 vintage Acer with HD3000, has had no such issues under
> -CURRENT. Though the LCD started to display colored vertical lines last year;
> replacing it with a new LCD resolved it.
> 
> Can you describe the problem further? Maybe a picture of the distortion you
> describe? What apps are you trying to run. Can you post dmesg, kldstat, and
> Xorg.0 outputs? What does your xorg.conf look like?
> 
> ---
> Sent using a tiny phone keyboard.
> Apologies for any typos and autocorrect.
> Also, this old phone only supports top post. Apologies.
> 
> Cy Schubert
>  or 
> The need of the many outweighs the greed of the few.
> ---
> 
> -Original Message-
> From: O. Hartmann
> Sent: 01/02/2018 04:07
> To: freebsd-current
> Subject: CURRENT and HD3000: i915 failing badly
> 
> Hello out there,
> 
> I got my hands on a Fujitsu Lifebook E751 manufactured 8/2011. The CPU is
> a Core i5-2520M, 4GB RAM and QM67 chipset, with an integrated HD3000 graphics.
> The display is on this model a Non-Glare HD+ display (1920x1080, I guess).
> 
> Neither FreeBSD 11.1-RELENG from USB flash nor 12-CURRENT as of 25th January
> work with the display: after the kernel has booted, I see only distortion and
> garbage on the screen. I checked with a recent Ubuntu and the Linux system is
> capable of showing nice and fancy graphics - but FreeBSD seems to be incapable
> to produce any serious console picture on this 6+ years old HD3000 chipset.
> What is the special case on this HD3000 and why isn't FreeBSD supporting it
> properly - or am I doing something wrong?
> 
> Kind regards,
> oh
> ___
> 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"

Hello all.

First: big apologize.

Me stupid used a set of oldish and outdated FreeBSD boot images and I thought I
had the right ones at hand. They were 10.X and 11.1. Recent CURRENT as of 25th
January as well as most recent CURRENT compiled by myself works without
problems.

Kind regards

Oliver

p.s. Thanks for all the answers.
___
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: buildkernel with PORTS_MODULES fails: Variable OBJTOP is recursive

2018-02-01 Thread O. Hartmann 
On Thu, 1 Feb 2018 12:10:30 +0300
Vladimir Zakharov  wrote:

> Hello!
> 
> For some time (about a week) building and installing kernel fails with
> the error "Variable OBJTOP is recursive." when going to build/install
> module from ports.
> 
> Last successful build was at r328426. Next build at r328527 failed and
> still broken at r328649.
> 
> Without PORTS_MODULES building and installing kernel succeeds. Another
> workaround: ignore error and build/install module directly from ports.
> 
> # cat /etc/make.conf
> MALLOC_PRODUCTION=yes
> KERNCONF=GENERIC-NODEBUG GENERIC
> #KERNCONF= GENERIC-NODEBUG
> CPUTYPE?=native
> #PORTS_MODULES = gPORTS_MODULES raphics/drm-next-kmod
> emulators/virtualbox-ose-kmod PORTS_MODULES = graphics/drm-next-kmod 
> 
> DOC_LANG = en_US.ISO8859-1 ru_RU.KOI8-R 
> 
> WITH_DEBUG_PORTS = mail/neomutt
> 
> WITH_CCACHE_BUILD=yes
> CCACHE_DIR=/home/ccache
> 
> #DEVELOPER=yes
> 
> ...
> Building /home/obj/usr/src/amd64.amd64/sys/GENERIC-NODEBUG/kernel.full
> --- kernel.full ---
> linking kernel.full
> ctfmerge -L VERSION -g -o kernel.full ...
>   text  data   bssdec hex   filename
>   22584632   1376209   474   28709729   0x1b61361   kernel.full
> Building /home/obj/usr/src/amd64.amd64/sys/GENERIC-NODEBUG/kernel.debug
> Building /home/obj/usr/src/amd64.amd64/sys/GENERIC-NODEBUG/kernel
> --- all ---
> ===> Ports module graphics/drm-next-kmod (all)  
> cd ${PORTSDIR:-/usr/ports}/graphics/drm-next-kmod; env  -u CC  -u CXX
> -u CPP  -u MAKESYSPATH  MAKEFLAGS="-j 4 -J 15,16 -j 4 -J 15,16 -D
> NO_MODULES_OBJ .MAKE.LEVEL.ENV=MAKELEVEL KERNEL=kernel TARGET=amd64
> TARGET_ARCH=amd64"  SYSDIR=/usr/src/sys
> PATH=
> SRC_BASE=/usr/src  OSVERSION=1200056
> WRKDIRPREFIX=/home/obj/usr/src/amd64.amd64/sys/GENERIC-NODEBUG make -B
> clean build
> ===>  Cleaning for drm-next-kmod-g20180117
> ===>  License BSD2CLAUSE MIT GPLv2 accepted by the user
> ===>   drm-next-kmod-g20180117 depends on file: /usr/local/sbin/pkg - found
> ===> Fetching all distfiles required by drm-next-kmod-g20180117 for building
> ===>  Extracting for drm-next-kmod-g20180117
> => SHA256 Checksum OK for FreeBSDDesktop-kms-drm-g20180117-622fdd1_GH0.tar.gz.
> ===>  Patching for drm-next-kmod-g20180117
> ===>   drm-next-kmod-g20180117 depends on file: /usr/local/bin/ccache - found
> ===>  Configuring for drm-next-kmod-g20180117
> ===>  Building for drm-next-kmod-g20180117
> ===> drm (all)  
> Variable OBJTOP is recursive.
> 
> make[6]: stopped in 
> *** Error code 2
> 
> Stop.
> make[5]: stopped in 
> ===> Compilation failed unexpectedly.  
> Try to set MAKE_JOBS_UNSAFE=yes and rebuild before reporting the failure to
> the maintainer.
> *** Error code 1
> 
> Stop.
> make[4]: stopped in /home/ports/graphics/drm-next-kmod
> *** Error code 1
> 
> Stop.
> make[3]: stopped in /home/ports/graphics/drm-next-kmod
> *** [all] Error code 1
> ...
> 

I have had the very same issue!

You need to perform a "installworld" first (just comment out the PORTS_MODULES=
parts of /etc/src.conf or /etc/make.conf, buildworld and buildkernel (maybe not
a full buildworld, but I do not know the state of your source tree) and perform
a regular installation of the world.  It could be something easier by direkctly
install-only the mk-portions, but recently, some changes to world (LLVM) made
it worth anyway to buildworld.

As recommended by others earlier on this list according to this subject, this
procedure makes the problem go away.

Kind regards,

Oliver
___
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"

Lenovo T470s Questions

2018-02-01 Thread Bridger Dyson-Smith 
Hi list and Michael -

I received a T470s at work and decided to jump into the CURRENT end of the
FreeBSD pool. I have a weird acpi_ibm issue and I'm not sure where to start
trying to diagnose the issue.

# uname -a
FreeBSD spanner 12.0-CURRENT FreeBSD 12.0-CURRENT #0 r328126: Thu Jan 18
15:25:44 UTC 2018 r...@releng3.nyi.freebsd.org:/
usr/obj/usr/src/amd64.amd64/sys/GENERIC  amd64

I've loaded acpi_ibm via /boot/loader.conf:
acpi_ibm_load="YES"

and the module shows as being loaded:
# kldstat | grep acpi_ibm
81 0x8278e000 7570 acpi_ibm.ko

However, I don't have any of the sysctl knobs available; e.g.
# sysctl -a | grep acpi_ibm
#

or
 # sysctl dev.acpi_ibm.0.fan_speed
sysctl: unknown oid 'dev.acpi_ibm.0.fan_speed'

I've (tried) to look through the commit messages on svn-src-head, but I'm
not seeing anything specifically related to acpi work, or I just don't know
what I'm looking at (a definite possibility).

Would someone be able to provide a bit of debugging direction here?
Reviewing `dmesg -a` doesn't tell me anything specific about acpi_ibm.

Thanks in advance for your time and trouble.
Bridger
___
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: Build failes cause of padlock_cipher.c:90 / commit: bbd1562a4992

2018-02-01 Thread Stefan Hagen 

Dimitry Andric wrote:
Make sure your source tree is at least at r328090, and run at least
"make buildworld" or "make kernel-toolchain" before attempting to build
the kernel.


Excellent! This works. And I learned about the the kernel-toolchain target.
Thank you.

Best Regards,
Stefan
___
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: CURRENT and HD3000: i915 failing badly

2018-02-01 Thread Guido Falsi 
On 02/01/18 09:30, O. Hartmann wrote:
> Hello out there,
> 
> I got my hands on a Fujitsu Lifebook E751 manufactured 8/2011. The CPU is
> a Core i5-2520M, 4GB RAM and QM67 chipset, with an integrated HD3000 graphics.
> The display is on this model a Non-Glare HD+ display (1920x1080, I guess).
> 
> Neither FreeBSD 11.1-RELENG from USB flash nor 12-CURRENT as of 25th January
> work with the display: after the kernel has booted, I see only distortion and
> garbage on the screen. I checked with a recent Ubuntu and the Linux system is
> capable of showing nice and fancy graphics - but FreeBSD seems to be incapable
> to produce any serious console picture on this 6+ years old HD3000 chipset.
> What is the special case on this HD3000 and why isn't FreeBSD supporting it
> properly - or am I doing something wrong?
> 

As others have told you you need to load the kms driver, you could
preload it via loader prompt.

otherwise to get to the console I've had luck with the "mode" command at
the loader prompt. mode 0 or mode 2 usually, you can try a few.

I can't find a list of modes to point you to, but it should be a
standard group of vesa modes.

This can be fixed later forcing the console to use the vt driver and
loading the appropriate module.

-- 
Guido Falsi 
___
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: CURRENT and HD3000: i915 failing badly

2018-02-01 Thread Cy Schubert 
My laptop, a 2012 vintage Acer with HD3000, has had no such issues under 
-CURRENT. Though the LCD started to display colored vertical lines last year; 
replacing it with a new LCD resolved it.

Can you describe the problem further? Maybe a picture of the distortion you 
describe? What apps are you trying to run. Can you post dmesg, kldstat, and 
Xorg.0 outputs? What does your xorg.conf look like?

---
Sent using a tiny phone keyboard.
Apologies for any typos and autocorrect.
Also, this old phone only supports top post. Apologies.

Cy Schubert
 or 
The need of the many outweighs the greed of the few.
---

-Original Message-
From: O. Hartmann
Sent: 01/02/2018 04:07
To: freebsd-current
Subject: CURRENT and HD3000: i915 failing badly

Hello out there,

I got my hands on a Fujitsu Lifebook E751 manufactured 8/2011. The CPU is
a Core i5-2520M, 4GB RAM and QM67 chipset, with an integrated HD3000 graphics.
The display is on this model a Non-Glare HD+ display (1920x1080, I guess).

Neither FreeBSD 11.1-RELENG from USB flash nor 12-CURRENT as of 25th January
work with the display: after the kernel has booted, I see only distortion and
garbage on the screen. I checked with a recent Ubuntu and the Linux system is
capable of showing nice and fancy graphics - but FreeBSD seems to be incapable
to produce any serious console picture on this 6+ years old HD3000 chipset.
What is the special case on this HD3000 and why isn't FreeBSD supporting it
properly - or am I doing something wrong?

Kind regards,
oh
___
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: CURRENT and HD3000: i915 failing badly

2018-02-01 Thread Greg 

On 02/01, O. Hartmann wrote:

Hello out there,

I got my hands on a Fujitsu Lifebook E751 manufactured 8/2011. The CPU is
a Core i5-2520M, 4GB RAM and QM67 chipset, with an integrated HD3000 graphics.
The display is on this model a Non-Glare HD+ display (1920x1080, I guess).

Neither FreeBSD 11.1-RELENG from USB flash nor 12-CURRENT as of 25th January
work with the display: after the kernel has booted, I see only distortion and
garbage on the screen. I checked with a recent Ubuntu and the Linux system is
capable of showing nice and fancy graphics - but FreeBSD seems to be incapable
to produce any serious console picture on this 6+ years old HD3000 chipset.
What is the special case on this HD3000 and why isn't FreeBSD supporting it
properly - or am I doing something wrong?


Hi.

FreeBSD doesn't load graphics drivers automatically by default. This 
looks like a vga/vesa/efi issue. Are you booting with legacy BIOS or 
UEFI?


Try loading i915kms blindly (i.e. on the USB installer, pressing Right 
and Enter to pick Shell and then running kldload i915kms).

___
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"

buildkernel with PORTS_MODULES fails: Variable OBJTOP is recursive

2018-02-01 Thread Vladimir Zakharov 
Hello!

For some time (about a week) building and installing kernel fails with
the error "Variable OBJTOP is recursive." when going to build/install
module from ports.

Last successful build was at r328426. Next build at r328527 failed and
still broken at r328649.

Without PORTS_MODULES building and installing kernel succeeds. Another
workaround: ignore error and build/install module directly from ports.

# cat /etc/make.conf
MALLOC_PRODUCTION=yes
KERNCONF=GENERIC-NODEBUG GENERIC
#KERNCONF= GENERIC-NODEBUG
CPUTYPE?=native
#PORTS_MODULES = graphics/drm-next-kmod emulators/virtualbox-ose-kmod
PORTS_MODULES = graphics/drm-next-kmod 

DOC_LANG = en_US.ISO8859-1 ru_RU.KOI8-R 

WITH_DEBUG_PORTS = mail/neomutt

WITH_CCACHE_BUILD=yes
CCACHE_DIR=/home/ccache

#DEVELOPER=yes

...
Building /home/obj/usr/src/amd64.amd64/sys/GENERIC-NODEBUG/kernel.full
--- kernel.full ---
linking kernel.full
ctfmerge -L VERSION -g -o kernel.full ...
  text  data   bssdec hex   filename
  22584632   1376209   474   28709729   0x1b61361   kernel.full
Building /home/obj/usr/src/amd64.amd64/sys/GENERIC-NODEBUG/kernel.debug
Building /home/obj/usr/src/amd64.amd64/sys/GENERIC-NODEBUG/kernel
--- all ---
===> Ports module graphics/drm-next-kmod (all)
cd ${PORTSDIR:-/usr/ports}/graphics/drm-next-kmod; env  -u CC  -u CXX
-u CPP  -u MAKESYSPATH  MAKEFLAGS="-j 4 -J 15,16 -j 4 -J 15,16 -D
NO_MODULES_OBJ .MAKE.LEVEL.ENV=MAKELEVEL KERNEL=kernel TARGET=amd64
TARGET_ARCH=amd64"  SYSDIR=/usr/src/sys
PATH=
SRC_BASE=/usr/src  OSVERSION=1200056
WRKDIRPREFIX=/home/obj/usr/src/amd64.amd64/sys/GENERIC-NODEBUG make -B
clean build
===>  Cleaning for drm-next-kmod-g20180117
===>  License BSD2CLAUSE MIT GPLv2 accepted by the user
===>   drm-next-kmod-g20180117 depends on file: /usr/local/sbin/pkg - found
===> Fetching all distfiles required by drm-next-kmod-g20180117 for building
===>  Extracting for drm-next-kmod-g20180117
=> SHA256 Checksum OK for FreeBSDDesktop-kms-drm-g20180117-622fdd1_GH0.tar.gz.
===>  Patching for drm-next-kmod-g20180117
===>   drm-next-kmod-g20180117 depends on file: /usr/local/bin/ccache - found
===>  Configuring for drm-next-kmod-g20180117
===>  Building for drm-next-kmod-g20180117
===> drm (all)
Variable OBJTOP is recursive.

make[6]: stopped in 
*** Error code 2

Stop.
make[5]: stopped in 
===> Compilation failed unexpectedly.
Try to set MAKE_JOBS_UNSAFE=yes and rebuild before reporting the failure to
the maintainer.
*** Error code 1

Stop.
make[4]: stopped in /home/ports/graphics/drm-next-kmod
*** Error code 1

Stop.
make[3]: stopped in /home/ports/graphics/drm-next-kmod
*** [all] Error code 1
...

-- 
Regards, | "In theory there is no difference between theory
  Vladimir Zakharov  | and practice. In practice there is."- Yogi Berra
___
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"

CURRENT and HD3000: i915 failing badly

2018-02-01 Thread O. Hartmann 
Hello out there,

I got my hands on a Fujitsu Lifebook E751 manufactured 8/2011. The CPU is
a Core i5-2520M, 4GB RAM and QM67 chipset, with an integrated HD3000 graphics.
The display is on this model a Non-Glare HD+ display (1920x1080, I guess).

Neither FreeBSD 11.1-RELENG from USB flash nor 12-CURRENT as of 25th January
work with the display: after the kernel has booted, I see only distortion and
garbage on the screen. I checked with a recent Ubuntu and the Linux system is
capable of showing nice and fancy graphics - but FreeBSD seems to be incapable
to produce any serious console picture on this 6+ years old HD3000 chipset.
What is the special case on this HD3000 and why isn't FreeBSD supporting it
properly - or am I doing something wrong?

Kind regards,
oh
___
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"