Thanks Warner, but the problem here is not how to implement KMS, because I really don't care. The problem is, that the version of xorg used on the current PCBSD snapshots, tries to force KMS on my Radeon card, and then falls back to vesa.

Mads

Den 30/05/2012 23.51 skrev "Warner Losh" <imp-uzTCJ5RojNnQT0dZR+AlfA@public.gmane.org>:

On May 30, 2012, at 3:07 PM, Mads Worsøe Duun wrote:

Still have the KMS problem with the new 20120524 snapshot.

Right, but starting off a port of the DFBsd stuff would be a big step backwards in the base support.  Having tried to do a quick port of that in the past, and looking at kib's work, I'd say kib's work is much more functional.  At best, you might be able to cherry-pick some radeon support, but it would need some minor reworking to cope with the differences between the two APIs.

Warner

Mads

Den 24/05/2012 22.12 skrev "Mads Worsøe Duun" <mads-AjN32Cl0S1Zaa/9Udqfwiw@public.gmane.org>:

> Short answer is: no, not really.  The DFBSD work is interesting, but incomplete.  A much more complete set of patches is being circulated and integrated into FreeBSD by kib <at> .
>
> Warner

I know the patches from kip <at> , but as fare I know it's Intel GEM only, and won't help much for eg. Radeon HD, as it needs TTM. My problem with the PCBSD 20120505 snapshot is, that it trys to enable KMS for my Radeon HD 2600 PRO card, and falls back to vesa, even if I try to generate my own xorg.conf file.

Mads Worsøe Duun

_______________________________________________
Testing mailing list
Testing-Fhbtn2kkCAMmbxgs1yVkuA@public.gmane.org
http://lists.pcbsd.org/mailman/listinfo/testing

_______________________________________________
Testing mailing list
Testing-Fhbtn2kkCAMmbxgs1yVkuA@public.gmane.org
http://lists.pcbsd.org/mailman/listinfo/testing

_______________________________________________ Testing mailing list Testing-Fhbtn2kkCAMmbxgs1yVkuA@public.gmane.org http://lists.pcbsd.org/mailman/listinfo/testing

Have you discussed this with anybody on the FreeBSD xorg mailing list?

http://lists.freebsd.org/pipermail/freebsd-x11/

This seems like something the xorg maintainers would be aware of, and possibly have a work-around for.

In freebsd-x11 they told me that libdrm probably is build using WITH_KMS=YES, and that may be a problem on non Intel cards. Today I will try to build xorg with WITH_NEW_XORG=YES and WITH_KMS=YES on a clean FreeBSD, and see what happens. Btw. I guess Dru has told you about the Solaris-like beadm http://forums.freebsd.org/showthread.php?t=31662, http://www.freshports.org/sysutils/beadm/. This is pretty smart for this xorg test, as I can roll back to the previous beadm as if nothing was changed.

Mads Worsøe Duun

_______________________________________________ Testing mailing list Testing-Fhbtn2kkCAMmbxgs1yVkuA@public.gmane.org http://lists.pcbsd.org/mailman/listinfo/testing

Hello!

I would like to know if there is already an easy way to discover the version/type of any particular USB stick after it has been burned but *without* needing to boot it.  Is there a readme file or some other sort of distinguishing feature that could be easily found that would indicate which USB image was burned?

If such a thing does not exist, I would like to suggest a small readme/manifest file that would be in an easily reached location within each USB, right inside / if possible would be difficult to miss.

Thanks!