Re: svn commit: r259016 - in head/sys: conf dev/drm2 dev/drm2/i915 dev/drm2/radeon dev/fb dev/vt kern modules/drm2/i915kms modules/drm2/radeonkms sparc64/sparc64 sys teken

From: Aleksandr Rybalko <ray_at_ddteam.net>
Date: Tue, 10 Dec 2013 01:49:26 +0200
On Mon, 9 Dec 2013 19:48:44 +0200
Markiyan Kushnir <markiyan.kushnir_at_gmail.com> wrote:

> 2013/12/9 Aleksandr Rybalko <ray_at_ddteam.net>:
> > On Mon, 9 Dec 2013 10:59:14 +0200
> > Markiyan Kushnir <markiyan.kushnir_at_gmail.com> wrote:
> >
> >> Hello,
> >>
> >> I'm on rev. 259102 and hitting drm not being able to attach to fbd
> >> device at X startup (X freezing).
> >>
> >> Attaching /var/log/messages, pciconf output and kern.conftxt.
> >> Please let me know if there is something I'm missing here. Posting
> >> in this thread since I thought it might be relevant to this commit?
> >>
> >> Thanks,
> >> Markiyan
> >>
> >>
> >> 2013/12/8 Marc UBM <ubm.freebsd_at_googlemail.com>:
> >> > Hiho! :-)
> >> >
> >> > Thanks a lot for working on this!
> >> >
> >> > As soon as X is started, things work fine. Before that (as soon
> >> > as vt is initialized after the boot menu), output on all ttys is
> >> > flickering, resolution is at 640x480 (guessing here) and
> >> > changing anything via vidcontrol fails with "inappropriate ioctl
> >> > for device". Also, screen output starts overlapping, but a
> >> > "clear" command fixes that temporarily. The "Alt-Gr" key does
> >> > nothing, manually entering ascii keycodes via alt+number (e.g.
> >> > alt-124 for |) works.
> >> >
> >> > Relevant pciconf output:
> >> >
> >> > vgapci0_at_pci0:0:2:0:     class=0x030000 card=0x40011297
> >> > chip=0x2e328086 rev=0x03 hdr=0x00 vendor     = 'Intel
> >> > Corporation' device     = '4 Series Chipset Integrated Graphics
> >> > Controller' class      = display
> >> >     subclass   = VGA
> >> >
> >> > vgapci1_at_pci0:0:2:1:     class=0x038000 card=0x40011297
> >> > chip=0x2e338086 rev=0x03 hdr=0x00 vendor     = 'Intel
> >> > Corporation' device     = '4 Series Chipset Integrated Graphics
> >> > Controller' class      = display
> >> >
> >> > Best regards,
> >> > Marc
> >> >
> >> >
> > [[CUT]]
> >> >
> >> >
> >> > --
> >> > Marc "UBM" Bocklet <eternal.ubm_at_gmail.com>
> >> > _______________________________________________
> >> > freebsd-current_at_freebsd.org mailing list
> >> > http://lists.freebsd.org/mailman/listinfo/freebsd-current
> >> > To unsubscribe, send any mail to
> >> > "freebsd-current-unsubscribe_at_freebsd.org"
> >
> > Hi Markiyan!
> >
> > According to attached kernel config you run system with syscons
> > (device sc).
> >
> > If you want to test it with vt (newcons), follow instructions on the
> > wiki page.
> > https://wiki.freebsd.org/Newcons
> >
> 
> Ah, thanks! I'll give it a try. I simply was curious of testing X
> running on a Radeon card on CURRENT. Testing vt is a bit different
> thing, and I will try it separately as well. Yet how about this error
> with drm_fb_helper_single_fb_probe? Does it mean I cannot use the old
> sc and vga devices now?

It is not fatal in syscons case. We decide to mark this message as
error, to get more attention when run with newcons. For newcons it
indicate that vt will not be able to draw into framebuffer(memory
region which contain image you see on display).
But it have no impact on sc (syscons).

> 
> 
> 
> > Thanks.
> >
> > WBW
> > --
> > Aleksandr Rybalko <ray_at_ddteam.net>

Thanks!
-- 
Aleksandr Rybalko <ray_at_ddteam.net>
Received on Mon Dec 09 2013 - 22:57:00 UTC

This archive was generated by hypermail 2.4.0 : Wed May 19 2021 - 11:40:45 UTC