On 07/01/2014 18:28, Steven Chamberlain wrote:
I'm guessing, initially, there will be some cutoff between older/newer
cards, older cards having the regression you described, and newer cards
falling back in the convenient way I describe, with the potential to
get KMS working easily.
I may
On 07/01/2014 02:35, Steven Chamberlain wrote:
On 07/01/14 00:46, Steven Chamberlain wrote:
It is most interesting that your HD 2400 / RV610 isn't falling back in
the same way as described above.
We might only need to disable older cards in radeonkms, I would guess
all before Evergreen;
On 07/01/2014 01:46, Steven Chamberlain wrote:
On 06/01/14 22:26, Robert Millan wrote:
The proper fix (running the actual initialization before sysctl_init) is not
so easy, as the codepaths are too separate (and this separation is even
exposed
to userland).
Really strangely, if the
On 18:04, Robert Millan wrote:
On 07/01/2014 01:46, Steven Chamberlain wrote:
Really strangely, if the firmware is not found for my card, it isn't
registering the sysctl. Xorg detects this and falls back to a usable
vesa desktop, fixed at 1280x1024 (no xrandr) cloned on both monitors.
On 18:05, Robert Millan wrote:
On 07/01/2014 02:35, Steven Chamberlain wrote:
We might only need to disable older cards in radeonkms, I would guess
all before Evergreen; just the Rxxx, RVxxx, RSxxx series.
https://wiki.freebsd.org/Graphics#Video_cards
You mean because of note 2? It
On 07/01/2014 18:17, Steven Chamberlain wrote:
It is most interesting that your HD 2400 / RV610 isn't falling back in
the same way as described above.
I haven't tried my patch on RV610 yet. I didn't look at the logs though, only
that output is deterministically garbled when firmware is not
On 24/12/2013 16:44, Robert Millan wrote:
2- The radeonkms module still enables the sysctls even if firmware load
failed.
My proposal was to disable #1 (i.e. remove the module). However if the
module is still useful there are many ways in which #2 can be changed to
adhere to our needs.
On 06/01/14 22:26, Robert Millan wrote:
The proper fix (running the actual initialization before sysctl_init) is not
so easy, as the codepaths are too separate (and this separation is even
exposed
to userland).
Really strangely, if the firmware is not found for my card, it isn't
registering
On 07/01/14 00:46, Steven Chamberlain wrote:
It is most interesting that your HD 2400 / RV610 isn't falling back in
the same way as described above.
We might only need to disable older cards in radeonkms, I would guess
all before Evergreen; just the Rxxx, RVxxx, RSxxx series.
On 20/12/2013 13:23, Robert Millan wrote:
This situation seems completely unworkable. Unless someone has a better
idea, I'll remove radeonkms from the Debian package.
RC3 is due out soon. Is there any objection to removal of radeonkms?
If users want the non-free module, they can still install
Robert Millan r...@debian.org writes:
On 20/12/2013 13:23, Robert Millan wrote:
This situation seems completely unworkable. Unless someone has a better
idea, I'll remove radeonkms from the Debian package.
RC3 is due out soon. Is there any objection to removal of radeonkms?
If users want the
Hi,
On 24/12/13 12:28, Robert Millan wrote:
RC3 is due out soon. Is there any objection to removal of radeonkms?
If we're not doing any automatic module loading yet, I don't think there
will be any functional change from doing this? Do we gain anything by
removing it or do you suggest it only
Hi Steven,
I'm glad you brought this up... please bear with my reordering of your
reply, which makes it easier to make my point:
On 24/12/2013 14:33, Steven Chamberlain wrote:
I seem to think the patch to the Xorg driver (#732514) is the riskiest
change, at which point radeon will stop
On 24/12/2013 14:23, Christoph Egger wrote:
AFAIK VESA still only gives a 1024x768 display?
Depends on the vga bios.
I have been running
radeon (without kms) on my old Thinkpad Z61m (ATI x1400) to get full
screen resolution -- there's a huge difference between getting 1680x1080
and
Package: kfreebsd-image-10.0-0-amd64
Version: 10.0~svn259404-1
Severity: important
Loading radeonkms (without non-free firmware) in my Radeon HD 2400 PRO
(RV610 chip, PCI id 0x1002 / 0x94c3) results in unusable screen, full
of color noise.
It seems that while this doesn't apply to all the cards,
15 matches
Mail list logo