Hi,
I have some weird display issues between a Radeon HD 7750 (using 4x DP outputs,
2560x1440 each) and a Dell Precision T5820 (Intel C422 chipset, W-2295 CPU,
latest BIOS).
Note: This is primarily about the text console and DRM, not Xorg/Xenocara
(which as a result also has problems of
On Jan 23 21:09:10, h...@stare.cz wrote:
> these are the errors drm reports:
>
> Jan 23 15:03:49 mb /bsd: drm:pid35173:iomfb_poweroff_v12_3 *ERROR*
> dcp_poweroff() done
> Jan 23 15:27:35 mb /bsd: drm:pid35173:iomfb_poweron_v12_3 *ERROR*
> dcp_poweron() starting
> Ja
This is current/arm64 on an M1 MacBook Air;
current dmesg and previous dmesg below.
The biggest difference seems to be drm replacing simplefb (thank you):
-"dcp" at simplebus0 not configured
-"display-subsystem" at simplebus0 not configured
+apldcp0 at simplebus0
+apldrm0 at
Try also with less beer sometime solve.
>It's not you, it's me.
>I configured the wrong switch port. :/
>Should work now.
>Mischa
ell as I'm able to interact with the station.
But just before the disk initialization some DRM message are reported
as diplayed below.
The tail of the dmesg says this:
drm:pid0:drm_dp_dual_mode_detect *ERROR* [drm] *ERROR* Unexpected DP
dual mode adaptor ID 20
inteldrm0: 1920x1080, 32bp
Hello,
I just inserted in my student mini pc
OpenBSD 7.2
a brand new DP(male) to HDMI(female) adapter:
https://amazon.it/dp/B08GFJF7LP/
The adapter runs well as I'm able to interact with the station.
But just before the disk initialization some DRM message are reported
as diplayed
On Sat, Jul 8, 2023, at 20:39, Nick Holland wrote:
> I believe what you are seeing is an informative message about what is
> going on under the covers, not an problem you (as a user) need to
> deal with if everything is working as it should be. However, if things
> are NOT working as they shou
On 7/6/23 01:46, Jonathan Drews wrote:
uname: OpenBSD 7.3 GENERIC.MP#1125 amd64
I get the following error message when my Thinkpad T440 wakes up:
drm:pid73944:intel_dp_aux_wait_done *ERROR* [drm] *ERROR* AUX A/DDI
A/PHY A: did not complete or timeout within 10ms (status 0xa01300e1)
I have
I am also getting this (or a similar) error on a different computer.
Please note that this might be a longer story. I'll put some details
before the dmesg.
drm:pid96852:intel_dp_aux_wait_done *ERROR* [drm] *ERROR* AUX C/DDI C/PHY C:
did not complete or timeout within 10ms (status 0xa023003
uname: OpenBSD 7.3 GENERIC.MP#1125 amd64
I get the following error message when my Thinkpad T440 wakes up:
drm:pid73944:intel_dp_aux_wait_done *ERROR* [drm] *ERROR* AUX A/DDI
A/PHY A: did not complete or timeout within 10ms (status 0xa01300e1)
I have Googled that error message and no fixes
:cpt_set_fifo_underrun_reporting
*ERROR* [drm] *ERROR* uncleared pch fifo underrun on pch transcoder A
Apr 17 14:24:28 grits /bsd: drm:pid7291:intel_pch_fifo_underrun_irq_handler
*ERROR* [drm] *ERROR* PCH transcoder A FIFO underrun
Apr 17 14:24:28 grits /bsd: xhci0: command ring abort timeout
Apr 17 16:03:12 grits /bsd
happen only when hardware acceleration is enabled so this
> might be a good place to start.
>
> --
> Patrick Harper
> paia...@fastmail.com
>
> On Fri, 21 Oct 2022, at 19:56, Mickael Torres wrote:
>
>> Hello,
>>
>> Since upgrading to 7.2, I have X/DRM
llo,
>
> Since upgrading to 7.2, I have X/DRM freezes on one computer (dmesg below).
>
> When it happens, the screen is completely frozen, but I can still ssh
> to the machine.
> It only happened when starting firefox or VLC, for now. Once they are
> started I didn't have any
Hello,
Since upgrading to 7.2, I have X/DRM freezes on one computer (dmesg below).
When it happens, the screen is completely frozen, but I can still ssh to the
machine.
It only happened when starting firefox or VLC, for now. Once they are started I
didn't have any
problem.
When the machi
On 9/8/22 03:07, Jonathan Gray wrote:
Index: sys/dev/pci/drm/i915/i915_drv.c
===
RCS file: /cvs/src/sys/dev/pci/drm/i915/i915_drv.c,v
retrieving revision 1.143
diff -u -p -r1.143 i915_drv.c
--- sys/dev/pci/drm/i915/i915_drv.c 30
On Thu, Sep 08, 2022 at 10:48:26AM +0200, Paul Kelly wrote:
> On 9/8/22 03:07, Jonathan Gray wrote:
> > Index: sys/dev/pci/drm/i915/i915_drv.c
> > ===
> > RCS file: /cvs/src/sys/dev/pci/drm/i915/i915_drv.c,v
&g
ome more DP messages.
> > Used in sys/dev/pci/drm/drm_dp_mst_topology.c
> >
> > Index: sys/dev/pci/drm/drm_print.c
> > =======
> > RCS file: /cvs/src/sys/dev/pci/drm/drm_print.c,v
> > retrieving revision
On 9/7/22 13:05, Jonathan Gray wrote:
If you add "option DRMDEBUG" to your kernel config
there may be some hints in the (large amount of) dmesg output
Also build with this to add some more DP messages.
Used in sys/dev/pci/drm/drm_dp_mst_topology.c
Index: sys/dev/pci/drm/d
s on a Lenovo T440p:
>
> https://www.reddit.com/r/openbsd/comments/ws1j1d/double_displayport_dock/
>
>
> Paul
If you add "option DRMDEBUG" to your kernel config
there may be some hints in the (large amount of) dmesg output
Also buil
Hey Julian,
On 9/4/22 18:18, Julian Huhn wrote:
Moin!
I can reproduce with my X270. With -current it does not work and with
6.9 both external monitors run without problems.
Same problem as I had already mentioned here:
https://marc.info/?l=openbsd-misc&m=166153179211227&w=2
Ah, I'd seen yo
tps://marc.info/?l=openbsd-misc&m=163569235820627&w=2
After deferring a deeper investigation for far too long, I have now
confirmed that the issue appears in my systems after the drm update
that was applied on July 7, 2021:
update drm to linux 5.10.47
hardware support changes includ
https://marc.info/?l=openbsd-misc&m=163569235820627&w=2
After deferring a deeper investigation for far too long, I have now
confirmed that the issue appears in my systems after the drm update that
was applied on July 7, 2021:
update drm to linux 5.10.47
hardware support change
ff against -current should help for some haswell problems,
> but perhaps not the one you are seeing.
>
> https://patchwork.freedesktop.org/patch/395580/?series=82783&rev=1
> https://gitlab.freedesktop.org/drm/intel/-/issues/2024
>
> Index: sys/dev/pci/drm/i915/gt/gen7_rendercl
This diff against -current should help for some haswell problems,
but perhaps not the one you are seeing.
https://patchwork.freedesktop.org/patch/395580/?series=82783&rev=1
https://gitlab.freedesktop.org/drm/intel/-/issues/2024
Index: sys/dev/pci/drm/i915/gt/gen7_renderclear.c
=
Hi,
I've started seeing the following error on my laptop along with
associated temporary freezing of the system:
drm:pid90783:intel_gt_reset *NOTICE* Resetting chip for stopped
heartbeat on rcs0
drm:pid90783:mark_guilty *NOTICE* Xorg[83345] context reset due to GPU
hang
i915_vma_coredum
Hi Jonathan,
Thank you very much for the quick response.
I applied the changes (manually), and they fix all of the hangs
mentioned as well as the two original errors; however, a new error
that I haven't seen before now shows in dmesg:
[drm] *ERROR* CPU pipe B FIFO underrun
This is only
t; to my assumption above:
> [4.6926206] warning:
> /usr/src/sys/external/bsd/drm2/dist/drm/drm_irq.c:1510 vblank wait
> timed out on crtc 0
> [4.7526574] kern error:
> [drm:(/usr/src/sys/external/bsd/drm2/dist/drm/i915/intel_fifo_underrun.c:363)intel_cpu_fifo_underrun_irq_handler]
&
e not, and neither is the latest Ubuntu
20.04 development release.
NetBSD 9.0 repeated the following errors upon boot and is what led me
to my assumption above:
[4.6926206] warning:
/usr/src/sys/external/bsd/drm2/dist/drm/drm_irq.c:1510 vblank wait
timed out on crtc 0
[4.7526574] kern error:
[drm:(/u
Hi again,
Disabling inteldrm has stopped the ERROR messages to show up but of course
OpenBSD will not switch into higher resolution since then.
Regards
Kris
--
Sent from: http://openbsd-archive.7691.n7.nabble.com/openbsd-user-misc-f3.html
OK, will give it a go.
I have already tried to disable drm* and drm0 and that just caused the
laptop to hang during boot.
Will give you a shout what happened when I disable inteldrm.
Cheers
--
Sent from: http://openbsd-archive.7691.n7.nabble.com/openbsd-user-misc-f3.html
/usr/src/sys/arch/i386/compile/GENERIC.MP
> real mem = 3210944512 (3062MB)
> avail mem = 3136659456 (2991MB)
> [SNIP]
> root on sd0a (d3d7274cd817feba.a) swap on sd0b dump on sd0b
> [drm] *ERROR* CPU pipe B FIFO underrun
> [drm] *ERROR* [CRTC:34:pipe ] flip_done timed out
> vblan
se1 at pms0 mux 0
pms0: Synaptics touchpad, firmware 6.2, 0x81a0b1 0x30
pcppi0 at isa0 port 0x61
spkr0 at pcppi0
aps0 at isa0 port 0x1600/31
npx0 at isa0 port 0xf0/16: reported by CPUID; using exception 16
ugen0 at uhub2 port 1 "Broadcom Corp BCM2045B" rev 2.00/1.00 addr 2
vscsi0 at root
Hi Jacek
On Tue, Feb 4, 2020 at 4:42 AM Jacek Kowalczyk wrote:
>
> Hi,
>
> I am running Openbsd 6.6 at ThinkPad R61i with graphic card Intel GMA X3100.
> I am getting errors like in the subject:
> [drm] *ERROR* [CRTC:41:pipe ] flip_done timed out
> [drm] *ERROR*
same happened
as in your case (yet it contains line 34,41 and 54):
[drm] *ERROR* [CRTC:34:pipe ] flip_done timed out
[drm] *ERROR* [CRTC:34 pipe ] flip_done timed out
[drm] *ERROR* [CONNECTOR:54:SVIDEO-] flip_done timed out
[drm] *ERROR* [CRTC:41:pipe ] flip_done timed out
[drm] *ERROR* [CRTC:41
Hi,
I am running Openbsd 6.6 at ThinkPad R61i with graphic card Intel GMA X3100. I
am getting errors like in the subject:
[drm] *ERROR* [CRTC:41:pipe ] flip_done timed out
[drm] *ERROR* [CONNECTOR:51:SVIDEO- ] flip_done timed out
And my laptop is booting quite long time, around 5 minutes
itch.
>
> If this rings a bell with someone and they have a fix, let me know. Could the
> USB keyboard sequences cause this blanking? The KVM switch can be switched
> from the keyboard by pressing caps-lock twice and then a command key. I guess
> this spies the USB bus for caps l
VM switch can be switched
from the keyboard by pressing caps-lock twice and then a command key. I guess
this spies the USB bus for caps lock key presses, does the DRM code or the
attaching of the keyboard set the caps lock key?
Below my signature I'll provide a dmesg from this machine.
Best
thanks for investigation .
With "Legacy BIOS/CSM compatibility is enabled" my dmesg output is
dmesg|grep -i drm
radeondrm0 at pci1 dev 0 function 0 "ATI Radeon HD 8730M" rev 0x00
drm1 at radeondrm0
radeondrm0: msi
inteldrm0 at pci0 dev 2 function 0 "Intel HD Graphi
I had a similar issue when attempting to boot on an 2011 iMac with a
radeon card. I did track down the location of the bug, but I didn't get
around to reporting it.
As far as I can tell the problem is this line (243, in -current) in
dev/pci/drm/radeon/radeon_bios.c, in the fun
-- Forwarded message --
From: dmitry.sensei
Date: Wednesday, February 6, 2019
Subject: drm bug on Dell Inspiron 3721 (6.4release and 6.4 current) -
error: [drm:pid0:radeon_get_bios] *ERROR* Unable to locate a BIOS ROM.
drm:pid0:radeondrm_attachhook *ERROR* Fatal error during GPU
Hi, my PC with ATI Radeon HD 6450 rev 0x00 graphic card works just fine.
Thanks for your work, developpers!
Kenji
tfrohw...@fastmail.com [tfrohw...@fastmail.com] wrote:
>
>
> On September 4, 2018 2:11:11 PM UTC, Maurice McCarthy
> wrote:
> >On 03/09/2018, Thomas de Grivel wrote:
> >
> >> Is there any way to use the DRM drivers without X11 ?
> >
> >Probably no
On September 4, 2018 2:11:11 PM UTC, Maurice McCarthy
wrote:
>On 03/09/2018, Thomas de Grivel wrote:
>
>> Is there any way to use the DRM drivers without X11 ?
>
>Probably not. The X sets in base are an integral part of the whole
>operating system. You install them whe
On 03/09/2018, Thomas de Grivel wrote:
> Is there any way to use the DRM drivers without X11 ?
Probably not. The X sets in base are an integral part of the whole
operating system. You install them whether or not you use X.
Hello misc,
Is there any way to use the DRM drivers without X11 ?
--
Thomas de Grivel
Hello,
OpenBSD doesn't implement some ioctl requests for drm devices, ie DRM_PRIME_*.
Are there any (and surely obvious) reasons for that ?
Nonetheless, is it possible to patch the libdrm headers to keep them undefine,
that way it would lead to straightforward errors, instead of having o
Hello,
In OpenBSD 6.2 the inteldrm driver was updated to code based on Linux 4.4.70 as
in the changelog states.
I'm using OpenBSD 6.1 and with this version the resolution at boot time is set
to 1280x800. But with OpenBSD 6.2 the resolution is set to 840x600 (or
something like that). Is this bec
On Mar 3, 2018 6:59 AM, Jonathan Gray wrote:
>
> On Sat, Mar 03, 2018 at 06:48:21AM -0600, ed...@pettijohn-web.com wrote:
> >
> > On Mar 3, 2018 5:52 AM, Z Ero wrote:
> > >
> > > "libGL error: failed to open drm device: Permission denied
>
On Sat, Mar 03, 2018 at 06:48:21AM -0600, ed...@pettijohn-web.com wrote:
>
> On Mar 3, 2018 5:52 AM, Z Ero wrote:
> >
> > "libGL error: failed to open drm device: Permission denied
> > libGL error: failed to load driver: i965"
> >
> > I can solve it
Hi,
does the xf86 manpage help any? I don't know if the two are related but
when it comes to permissions of the vga card, I think this is a spot to
look.
Regards,
-peter
On 03/03/18 12:52, Z Ero wrote:
> "libGL error: failed to open drm device: Permission denied
> libGL error
On Mar 3, 2018 5:52 AM, Z Ero wrote:
>
> "libGL error: failed to open drm device: Permission denied
> libGL error: failed to load driver: i965"
>
> I can solve it by changing the permissions on /dev/drm0 to rw for users but:
>
> (1) I am not sure if that introduce
"libGL error: failed to open drm device: Permission denied
libGL error: failed to load driver: i965"
I can solve it by changing the permissions on /dev/drm0 to rw for users but:
(1) I am not sure if that introduces a realistic security risk.
(2) The permissions are reverted on reboo
Dear All,
Since i love OBSD, for instance i have it in my panasonic cf-30, dell
precision 690 and a samsung Laptop, i would like to install it in an imac
mid 2011.
The problem is that after install, the first boot always goes blank.
What happened is:
- The install goes as perfect as always.
- Wh
On 2018-01-02, Riccardo Mottola wrote:
> Hi,
>
> On 2018-01-02 14:04:20 +0100 Luca Franchini wrote:
>
>> I have downloaded skl_dmc_ver1.bin from Intel site.
>>
>> Is there a chance to have it loaded?
>> Better power saving?
>> I'm very happy with OpenBSD 6.2 hw support in this laptop (Thinkpad
Hello Riccardo,
# fw_update -i
Installed: uvideo-firmware-1.2p2 iwm-firmware-0.20170105
vmm-firmware-1.10.2p4
Running 'fw_upfdate -a' did not helped
inteldrm was doing well also here:
#dmesg | grep drm
nteldrm0 at pci0 dev 2 function 0 "Intel HD Graphics 530" rev 0x
Hi,
On 2018-01-02 14:04:20 +0100 Luca Franchini wrote:
I have downloaded skl_dmc_ver1.bin from Intel site.
Is there a chance to have it loaded?
Better power saving?
I'm very happy with OpenBSD 6.2 hw support in this laptop (Thinkpad
T460p)
What does running "fw_update" do? I run OpenBSD f
Hi all,
I noticed than in my Skylake laptop using inteldrm driver
firmware is missing
in messages:
inteldrm0 at pci0 dev 2 function 0 "Intel HD Graphics 530" rev 0x06
drm0 at inteldrm0
inteldrm0: msi
error: [drm:pid0:i915_firmware_load_error_print] *ERROR* failed to load
firmware i915/skl_dmc_ve
Hello misc@,
I noticed the following error while running chrome from the shell this
evening:
libGL error: failed to open drm device: Permission denied
libGL error: failed to load driver: i965
Which I think means that I'm not getting accelerated X.
A search of misc archives led me to
What happens if you try jcs' intel_backlight utility?
https://devhub.io/repos/jcs-intel_backlight_fbsd
Take note of the machdep.allowaperture=3 change you need to make to
sysctl.conf (requires a reboot).
On Sat, Jul 22, 2017 at 5:09 PM, Michel Behr wrote:
> Hi - I'm trying to connect my Lenovo
Hi - I'm trying to connect my Lenovo Laptop a monitor via HDMI but I'm
getting no output (below I'm including messages regarding xrandr, dmesg,
and Xorg.0.log).
Any pointing to the right direction would be much appreciated.
Kind regards,
Michel.
$ uname -a
OpenBSD S400 6.1 GENERIC.MP#115 am
Hello Mihai,
On Tue, 21 Mar 2017 00:07:16 +0200
Mihai Popescu wrote:
> What version of OpenBSD are you running?
-current, updated to 03/19 snapshot:
[just22@poseidon]-[0]-[✓]-[~]> dmesg | head -2
OpenBSD 6.1-beta (GENERIC.MP) #38: Sun Mar 19 11:09:01 MDT 2017
dera...@amd64.openbsd.org:/usr
> in the hope that someone clarify the situation.
What version of OpenBSD are you running?
Did you modified /etc/fbtab?
What is 'll' or that command used to show permissions?
Is just22 a custom user, i.e. not created at install time?
Looking at what I have, I think for a normal install it sho
istent with the content of /etc/fbtab, meaning
that if I do the same sequence of operations from a different virtual
terminal, ttyC1 for example, /dev/drm0 ownership is left untouched).
Of cource, when I switch back in X, I'm no more able to get access to drm
device, losing hardware
I think that actual, real job is done by:
aml_evalname(sc, node, "_OFF", 0, NULL,
&res2)
or
aml_evalinteger(sc, node, "_OFF", 0,
NULL, &val2)
inside acpi.c file.
The only good thing about this patch is
that it works for me.
> > +filedev/pci/nvdsbl.c
>
> can you include this file? and any new .h files as well?
I think that this was just for registering a dummy driver
for that Nvidia device. It does nothing useful itself.
# cat /usr/src/sys/dev/pci/nvdsbl.c
/* $OpenBSD: nvdsbl.c,v 0.1 2015/07/28 12:00:01 some
Lampshade wrote:
> This is totally fucked up code, but if you like hazard...
> I mean that I really just called some random ACPI (aml) methods
> not knowing what they should do.
> +#Acer Optimus nvdsbl disable nvidia gpu PCI
> +device nvdsbl
> +attach nvdsbl at pci
> +filedev/pci/nvdsbl.c
This is totally fucked up code, but if you like hazard...
I mean that I really just called some random ACPI (aml) methods
not knowing what they should do.
Additionally this code is for my laptop. I have GEFORCE 620M
GPU, so I added this to pcidevs. Another thing is that patched
code recognizes my
A year ago I have written ugly hack to disable Nvidia GPU year ago
for power saving.
Is this patch available somewhere?
Not a dev, but it may have something to do with pledge. Try to change your
aperture driver (check man xf86) and reboot. Also, try ffplay instead of mpv
just to check if it's not a software specific problem.
I have trimmed lspci output, but actually it was important.
I have not only Intel GPU but also Nvidia GPU.
A year ago I have written ugly hack to disable Nvidia GPU year ago
for power saving.
I am sure that is too ugly to commit to repository and
I am not programming professional so I need a lot o
ow it unfortunately didn't helped.
I chown-ed drm files:
# chown open /dev/drm[0-3]
#
But it didn't helped.
Part of Xorg.0.log:
[ 3005.601] (II) intel(0): SNA initialized with Sandybridge (gen6, gt1)
backend
[ 3005.601] (==) intel(0): Backing store enabled
[ 3005.601] (==) intel(0): Silken
celeration for applications using it?
Yes, on a drm(4) supported device. You could confirm this with the
demo glxgears(1).
Well, things were sorted out.
Looking at that /etc/fbtab file Jonathan Gray pointed out (and yes,
this is not a typo of /etc/fstab like I thought before) I can spot the
/dev/drm0 in that long list of devices prepared for chown at login.
But, that file is filled in for ttyC0 only, the tty that mos
Mon, 28 Dec 2015 00:25:25 +0200 Mihai Popescu
> libGL error: failed to open drm device: Permission denied
> libGL error: failed to load driver: r600
>
> Is it normal, can it be fixed on my side?
Quick and dirty hack around this (if your user is in group wheel):
$ grep chmod .xinitr
> Can you include the output of ls -l /dev/drm0 and
> the contents of /var/log/Xorg.0.log ?
$ ls -l /dev/drm0
crw--- 1 root wheel 87, 0 Dec 11 20:39 /dev/drm0
$ more /var/log/Xorg.0.log
[46.215] (WW) checkDevMem: failed to open /dev/xf86 and /dev/mem
(Operation not permitted
ave to click 2 or 3 times on menu entry to start chrome again. This
>> is not a big deal, maybe a cwm glitch.
>>
>> I went to start chrome from xterm, and I got these errors:
>>
>> $ chrome
>> libGL error: failed to open drm device: Permission denied
>>
. This
> is not a big deal, maybe a cwm glitch.
>
> I went to start chrome from xterm, and I got these errors:
>
> $ chrome
> libGL error: failed to open drm device: Permission denied
> libGL error: failed to load driver: r600
> libGL error: failed to open drm device: Per
got these errors:
$ chrome
libGL error: failed to open drm device: Permission denied
libGL error: failed to load driver: r600
libGL error: failed to open drm device: Permission denied
libGL error: failed to load driver: r600
Is it normal, can it be fixed on my side?
OpenBSD 5.8-current
Hi,
I see these in message log on my ThinkPad T440:
Dec 17 09:58:23 efreet /bsd: error: [drm:pid10071:intel_dp_set_link_train]
*ERROR* Timed out waiting for DP idle patterns
Dec 17 09:58:23 efreet /bsd: error: [drm:pid10071:i915_write32] *ERROR* Unknown
unclaimed register before writing to 6404
quot;Logitech USB
> Receiver" rev 2.00/12.01 addr 2
> uhidev1: iclass 3/1, 8 report ids
> ums0 at uhidev1 reportid 2: 16 buttons, Z dir
> wsmouse2 at ums0 mux 0
> uhid0 at uhidev1 reportid 3: input=4, output=0, feature=0
> uhid1 at uhidev1 reportid 4: input=1, output=0, feat
Xorg.0.log and full dmesg.
Xorg.0.log:
[14.783] (--) checkDevMem: using aperture driver /dev/xf86
[14.801] (--) Using wscons driver on /dev/ttyC4 in pcvt
compatibility mode (version 3.32)
[14.823]
X.Org X Server 1.14.5
Release Date: 2013-12-12
[14.823] X Protocol Version 11, Revisi
Hi, All!
I can't set a fullhd resoulution on my second monitor. I don't see
1920x1080 in xrandr's output, so I used cvt to create a new one, but in
the end I got intel_crct errors in dmesg.
Here are some outputs.
-> cvt 1920 1080
# 1920x1080 59.96 Hz (CVT 2.07M9) hsync: 67.16 kHz; pclk: 173.00 M
uhid5 at uhidev2 reportid 32: input=14, output=14, feature=0
uhid6 at uhidev2 reportid 33: input=31, output=31, feature=0
uhidev3 at uhub1 port 2 configuration 1 interface 0 "Logitech USB-PS/2
Optical Mouse" rev 2.00/11.10 addr 3
uhidev3: iclass 3/1
ums1 at uhidev3: 3 buttons, Z dir
ws
Thank you very much.
Stuart Henderson spacehopper.org> writes:
> Not sure about changing fonts or char size, but you can disable drm:
>
> config -ef /bsd
> disable radeondrm
> quit
On 3/22/2014 at 4:43 PM Stuart Henderson wrote:
|On 2014-03-22, Mike. wrote:
|> I've looked and searched, but I've been unable to find a way
return
|> to the usual 80x25, or even 80x40, screen setup. Is it possible
to
|> change the font in drm? Is it possible to disable drm
On 2014-03-22, Mike. wrote:
> I've looked and searched, but I've been unable to find a way return
> to the usual 80x25, or even 80x40, screen setup. Is it possible to
> change the font in drm? Is it possible to disable drm and get back
> the 80x25 screen?
Not sure about
Yesterday I loaded OpenBSD 5.5-current on an old notebook (ThinkPad
a31p). I had not used OpenBSD on that particular notebook for a few
years. I run OpenBSD in character-based command line mode.
The screen on the notebook is a dense 1600x1200 pixels on 12x9
inches. Something called drm is
On 10/10/13 17:48, RD Thrush wrote:
> I noticed some anomalies in the dmesg on this new system.
>
> 1. error: [drm:pid0:i915_write32] *ERROR* Unknown unclaimed register before
> writing to 10
>
> 2. dhclient doesn't work with the onboard nic (possibly since the lladdr is
> 0:0:0:0:0:0.
>
>
On 10/11/13 03:18, Jonathan Gray wrote:
> On Fri, Oct 11, 2013 at 02:39:30AM -0400, RD Thrush wrote:
>> On 10/11/13 01:05, Jonathan Gray wrote:
>>> On Thu, Oct 10, 2013 at 05:48:43PM -0400, RD Thrush wrote:
I noticed some anomalies in the dmesg on this new system.
1. error: [drm:pid0
On Fri, Oct 11, 2013 at 02:39:30AM -0400, RD Thrush wrote:
> On 10/11/13 01:05, Jonathan Gray wrote:
> > On Thu, Oct 10, 2013 at 05:48:43PM -0400, RD Thrush wrote:
> >> I noticed some anomalies in the dmesg on this new system.
> >>
> >> 1. error: [drm:pid0:i915_write32] *ERROR* Unknown unclaimed re
On 10/11/13 01:05, Jonathan Gray wrote:
> On Thu, Oct 10, 2013 at 05:48:43PM -0400, RD Thrush wrote:
>> I noticed some anomalies in the dmesg on this new system.
>>
>> 1. error: [drm:pid0:i915_write32] *ERROR* Unknown unclaimed register before
>> writing to 10
>>
>> 2. dhclient doesn't work wi
On 10/11/13 01:28, Jonathan Gray wrote:
> On Thu, Oct 10, 2013 at 05:48:43PM -0400, RD Thrush wrote:
>> I noticed some anomalies in the dmesg on this new system.
>>
>> 1. error: [drm:pid0:i915_write32] *ERROR* Unknown unclaimed register before
>> writing to 10
>
> That should be harmless, and
On Thu, Oct 10, 2013 at 05:48:43PM -0400, RD Thrush wrote:
> I noticed some anomalies in the dmesg on this new system.
>
> 1. error: [drm:pid0:i915_write32] *ERROR* Unknown unclaimed register before
> writing to 10
That should be harmless, and will go away when we update to newer
upstream i9
On Thu, Oct 10, 2013 at 05:48:43PM -0400, RD Thrush wrote:
> I noticed some anomalies in the dmesg on this new system.
>
> 1. error: [drm:pid0:i915_write32] *ERROR* Unknown unclaimed register before
> writing to 10
>
> 2. dhclient doesn't work with the onboard nic (possibly since the lladdr
On 10/10/13 19:31, Brett Mahar wrote:
> On Thu, 10 Oct 2013 17:48:43 -0400
> RD Thrush wrote:
>
> | I noticed some anomalies in the dmesg on this new system.
> |
> ...
> |
> | 2. dhclient doesn't work with the onboard nic (possibly since the lladdr is
> 0:0:0:0:0:0.
>
> You could check this b
RD Thrush thrush.com> writes:
> acpiec0 at acpi0: Failed to read resource settings
... among mentioned things.
On Thu, 10 Oct 2013 17:48:43 -0400
RD Thrush wrote:
| I noticed some anomalies in the dmesg on this new system.
|
...
|
| 2. dhclient doesn't work with the onboard nic (possibly since the lladdr is
0:0:0:0:0:0.
You could check this by adding a random lladdr line to your /etc/hostname.re0
lla
that the GPU was shut down by the sleep process before the
driver was ready for this possibility?
To get the intel drm out of this state, I have to reboot.
The beauty of it all:
OpenBSD 5.3-current (GENERIC.MP) #132: Fri Jun 7 13:13:22 MDT 2013
dera...@amd64.openbsd.org:/usr/src/sys/arch/
On 8 June 2013 09:56, Sergey Bronnikov wrote:
> Hello,
>
> I installed latest OpenBSD snapshot yesterday.
> Notebook worked over the night with just started X server and xlock(1).
>
> I have found a lot messages like below in system log on the morning:
> error: [drm:pid9649:drmioctl] *ERROR* can't
Hello,
I installed latest OpenBSD snapshot yesterday.
Notebook worked over the night with just started X server and xlock(1).
I have found a lot messages like below in system log on the morning:
error: [drm:pid9649:drmioctl] *ERROR* can't find authenticator
error: [drm:pid9649:drmioctl] *ERROR* c
1 - 100 of 175 matches
Mail list logo
