Re: modesetting feature status

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



2008/9/11 Dave Airlie <airlied@xxxxxxxxxx>:
>
> I'm 100% interested in the output doesn't light up kinda bugs.
>
> If anyone encounters these what would be useful is to over ssh
>
> boot with nomodeset 3 - go to no X runlevel.
> rmmod radeon drm
> modprobe drm debug=1
> modprobe radeon modeset=1
>
> and attach dmesg to a bug, also add an xorg log from a nomodeset boot
>
> Next on the list are oops and crashes.
>
> If I can solve the crashers and modeset not starting I can start on the
> artifacts, rendering speed regressions and 3D bits.
>
> but from the beta release I'd feel free to file any bugs against it.
>
> Dave.

Tried it but without ssh there is nothing in /var/log/messages after
restart. Only the following
 [drm] Module unloaded
 [drm] Initialized drm 1.1.0 20060810
 imklog 3.18.1, log source = /proc/kmsg started.
 After modprobe radeon modeset=1  everything freezes - no display,
touchpad, keyboard, only hardware reset helps. This way I cannot
extract /proc/kmsg. Is there another way to help with debugging? My
bug https://bugzilla.redhat.com/show_bug.cgi?id=461545

-- 
fedora-devel-list mailing list
fedora-devel-list@xxxxxxxxxx
https://www.redhat.com/mailman/listinfo/fedora-devel-list

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[Index of Archives]     [Fedora Announce]     [Fedora Kernel]     [Fedora Testing]     [Fedora Formulas]     [Fedora PHP Devel]     [Kernel Development]     [Fedora Legacy]     [Fedora Maintainers]     [Fedora Desktop]     [PAM]     [Red Hat Development]     [Gimp]     [Yosemite News]
  Powered by Linux