Skip site navigation (1)Skip section navigation (2)
Date:      Sat, 04 Oct 2014 17:31:39 +0200
From:      =?windows-1252?Q?Jean-S=E9bastien_P=E9dron?= <dumbbell@FreeBSD.org>
To:        freebsd-stable@freebsd.org, Nathan Whitehorn <nwhitehorn@freebsd.org>
Subject:   Re: Removal of legacy X.Org (aka non-WITH_NEW_XORG) [NVIDIA vs. powerpc64 for vt console switching; Radeon X1950 not working for powerpc64 Xorg generally]
Message-ID:  <543012DB.2040208@FreeBSD.org>
In-Reply-To: <2C74DFEC-D943-4237-8988-B9657240EC21@dsl-only.net>
References:  <2C74DFEC-D943-4237-8988-B9657240EC21@dsl-only.net>

next in thread | previous in thread | raw e-mail | index | archive | help
This is an OpenPGP/MIME signed message (RFC 4880 and 3156)
--jG6xNJSTm4AHl3vomptVJ3lthF9NLiAAH
Content-Type: text/plain; charset=windows-1252
Content-Transfer-Encoding: quoted-printable

On 04.10.2014 02:38, Mark Millard wrote:
> NVIDIA 7800 GT in that type of PowerMac G5: Nearly black text on
> black background problems for vt console switching from Xorg/xfce4
> but normal text display for sc...

It looks like the backlight of your screen isn't turned on when
switching to a console window.

Could you please connect from a remote computer to your Power Mac G5 and
run the following command as root?
    truss -fd -o truss-$(sysctl -n kern.vty).txt /usr/local/bin/Xorg

Wait a couple seconds and hit Control-C to stop the X server.

Please do this for both vt(4) and syscons. Then post both truss-vt.txt
and truss-sc.txt files to this list. This will help us to determine if
vt(4) lacks an ioctl, compared to syscons.

> For 10.1-BETA3 the boot-time vt console display works for 1920x1200=20
> but not (usefully/readably) for 2560x1440. So the following notes
> are for a 1920x1200 context. (10.1-BETA2 had different behavior and
> was usable for 2560x1440 despite a temporary display oddity during
> booting. But I'm not going down this path here. I'm pointing out a
> different XOrg issue.)

Could you please post pictures of this screen with both -BETA2 and
-BETA3? I'd like to understand this regression on your side.

> My attempt to test a Radeon X1950 in such a PowerMac G5 shows that=20
> XOrg does not get very far:

If you have some time, could you please test my "kms-drm-update-38",
available on GitHut?
https://github.com/dumbbell/freebsd/tree/kms-drm-update-38

Just build a kernel from that checkout (no need to build world). This
branch enables the Radeon kernel module on PowerPC. Then, you can play
with xf86-video-ati (the KMS-only driver). Hopefully, the kernel driver
provides better support for the card.

> My attempt to side step this with use of xf86-video-scfb and a=20
> matching xorg.conf did not work either (note also the 'depth (32)'
> below vs. the 'depth (24)' above, not just the 'Weight given (000)'
> below)
>=20
> [   321.133] (II) LoadModule: "scfb"
> [   321.134] (II) Loading /usr/local/lib/xorg/modules/drivers/scfb_drv.=
so
> [   321.134] (II) Module scfb: vendor=3D"X.Org Foundation"
> [   321.134]    compiled for 1.12.4, module version =3D 0.0.4
> [   321.134]    ABI class: X.Org Video Driver, version 12.1
> [   321.134] (II) scfb: driver for wsdisplay framebuffer: scfb
> [   321.154] (--) Using syscons driver with X support (version 85952293=
51.252)
> [   321.154] (--) using VT number 9
>=20
> [   321.154] (WW) Falling back to old probe method for scfb
> [   321.154] scfb trace: probe start
> [   321.154] (II) scfb(0): using default device
> [   321.154] scfb trace: probe done
> [   321.154] (WW) VGA arbiter: cannot open kernel arbiter, no multi-car=
d support
> [   321.154] scfb: PreInit 0
> [   321.154] (II) scfb(0): Using: depth (32),   width (1920),    height=
 (1200)
> [   321.154] (**) scfb(0): Depth 32, (--) framebuffer bpp 32
> [   321.154] (EE) scfb(0): Weight given (000) is inconsistent with the =
depth (32)
> [   321.154] (II) UnloadModule: "scfb"
> [   321.154] (EE) Screen(s) found, but none have a usable configuration=
=2E
> [   321.154]=20
> Fatal server error:
> [   321.154] no screens found

Nathan (CC'd), do you have an idea about what's going on here?

--=20
Jean-S=E9bastien P=E9dron


--jG6xNJSTm4AHl3vomptVJ3lthF9NLiAAH
Content-Type: application/pgp-signature; name="signature.asc"
Content-Description: OpenPGP digital signature
Content-Disposition: attachment; filename="signature.asc"

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2

iQJ8BAEBCgBmBQJUMBLgXxSAAAAAAC4AKGlzc3Vlci1mcHJAbm90YXRpb25zLm9w
ZW5wZ3AuZmlmdGhob3JzZW1hbi5uZXQ2NzA4N0ZEMUFFQUUwRTEyREJDNkE2RjAz
OUU5OTc2MUE1RkQ5NENDAAoJEDnpl2Gl/ZTMJ18P/AwQyfwiLQ+BC/WJgChT2bWR
fBIWJoZ0jzKWV5obGb2yciTjwpWcQqu1ijjQNVa64afG6YZ0bWhQBsKCezd9HbAp
QUkBGI/1x80ruU7Lc4KumCeB+cb/GGCCyzUciA9vxwsodWgJsLFwebGcS3cXje1d
p8cLJTcRX1kmZN8d9r5i+aM+LWyoEu3KhPbLZLQIyFBLjb2IvYw8q+rhBBSrfUHI
fYG3aCP9pSuoJdXZ3MxMvMZZf5ekoFvesCLqCHpYvgYUVucL+H5qWClb1RD9JjrS
k1/QErnhoj8A2ZQpojIU3RjYhnRCmGEFAV0c7Ff+lmc+p4XJEjz8N4DWvJ6e6fx8
dFDTD+3rmhwpFkYJSyauIh0g9aJiGxeA07eF0yGjpl/2HY55jL4il+A2MEtYNCxa
WVbP7xSQY2/ndEO//D5Q6/RR5cUYztVITiy1YSSO+g9Mf7GQ7iBHDYU7l40If+Yo
dmGi8gj1L9PwP0FKGmDG+6iiOvCNEUkZanQLkkUSxvnzF2PcKn0kzCsYZzAtKSlb
JDsgPyf7ygtZV04vyAqYfF3XH8Z52upnN5R5rkUOCdSRR2R0J9Sthqh9Tx9NS301
7MnPjOka+MG9GscR9m5zvv5GPjPk5KDzH91PafhUcarAR8luRWtVWhxtbzlWvi8E
pE3zsQdK8iq1oLozWvuv
=2A8S
-----END PGP SIGNATURE-----

--jG6xNJSTm4AHl3vomptVJ3lthF9NLiAAH--



Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?543012DB.2040208>