On 2021-05-31 00:26, karu.pruun wrote:
> I could not replicate the problem on my old i915 laptop.
>
> Can you open a bug on the bugs.dragonflybsd.org (if you don't have an
> account ask on irc) and attach the drm.debug=0x777 outputs of both 5.8
> and 6.0 there? Comparing them might help find the
I could not replicate the problem on my old i915 laptop.
Can you open a bug on the bugs.dragonflybsd.org (if you don't have an
account ask on irc) and attach the drm.debug=0x777 outputs of both 5.8
and 6.0 there? Comparing them might help find the problem.
Peeter
--
On Sat, May 29, 2021 at
fb_info = { width = 1366, height = 768, stride = 5504, depth = 32 }
So at least the dimensions are the same.
Now that I know to use buildkernel, not quickkernel, I'll try putting
in some traces. One thing I noticed is that there are a number of calls
to set the framebuffer for a plane,
On 2021-05-28 01:05, karu.pruun wrote:
Hello
Can you see if the fb info has changed between 5.8 and 6.0? Insert
these lines
Doesn't look like it. I tried that debug trace in both 5.8 and 6.0
kernels and they both printed:
fb_info = { width = 1366, height = 768, stride = 5504, depth =
I worked on troubleshooting this, but didn't get very far.
For both 5.8 and 6.0, I set drm.debug to 0x777, booted the system, and
then kldloaded i915. I captured dmesg to a file in both cases for later
perusal. They are somewhat different: 6.0 does print more stuff and it
has couple warning
The kern.kms_console is set to 1 by default, you can remove it from
loader.conf. There is a man page for drm (see 'man drm') and also for
the drivers, i915 and radeon.
I checked my intel (i7 skylake) machine, I get the same errors and
messages, but drm/i915 and xorg/xfce work fine.
Just to
https://man.dragonflybsd.org/?command=syscons=ANY
Heh, I never managed to stumble across that. Thanks!
On Thu, 20 May 2021 11:54:29 -0700
Chuck Musser wrote:
> That's correct: if the i915 module isn't loaded, then the console works
> normally. I tried loading the driver by hand after booting and the
> console becomes frozen: nothing new is displayed. But, yes, the system
> is still running. I've
That's correct: if the i915 module isn't loaded, then the console works
normally. I tried loading the driver by hand after booting and the
console becomes frozen: nothing new is displayed. But, yes, the system
is still running. I've always been able to SSH when the console is
frozen. The console
So I am I right to think that you can get the console fine but loading
i915 gives a frozen screen? To test this is true, remove automatic
loading of i915 from /etc/rc.conf and see if you get to the login
prompt. Then try manually loading i915 on console, as root do 'kldload
i915'. You can get more
I tried the following, which did change things but did not result in a
working console at the end of the boot:
- added "gop set 2" in /boot/loader.conf. mode 2 was 1024x768 and seemed
to display fine in the loader prompt
- moved the i915_load="YES" to /etc/rc.conf and removed drm_load="YES"
Hello
You can try setting a different mode at the loader: get to the prompt
(press 9) and play with 'gop list', 'gop set ' and 'gop get'. Maybe
you can find a resolution that works fine?
If yes, try loading i915 in /etc/rc.conf, that's the recommended
procedure. Loading i915 too early may blow
Related (maybe) to this are these messages in dmesg:
vgapci0: port 0x5000-0x503f mem
0xe000-0xefff,0xf000-0xf03f irq 16 at device 2.0 on pci0
[drm] pdev: vendor=0x8086 device=0x0126 rev=0x09
[drm] svendor=0x17aa sdevice=0x21da irq=17
WARN_ON(domain->wake_count ==
A while ago I switched to using UEFI boot mode on my x220 using DFly
5.8, so I could use rEFInd to multi-boot my system. This required some
additional config in /boot/loader.conf to fix a garbled console. This is
the config I'd added:
dm_load="YES"
vfs.root.mountfrom="hammer2:serno/W0Q0E1PL.s5d"
14 matches
Mail list logo
