Hi Michael
Michael wrote:
did so. Still get a black screen. Before going black, I am able to see a
"failed".
Also, it hangs, because if I wait some time I can't login remotely (left
dhcp on).
This is odd, but it's a data point at least.
Before trying to recompile the kernel once again, I
Hi John & Michael,
since I borrowed the monitor of my workstation to do tests for
radeonfb I also thougt to take the time and test what the radeondrm
would do with an external monitor!
set
bool radeon_pci_ignore_r100_r200 = false;
and recompile (commenting out radeonfb* just not to
On Thu 30 May 2024 at 10:44:10 -0400, Michael wrote:
> Does Xorg run with a radeon driver on any OS at all? If so, could you
> send me the xorg.0.log from such a thing? That should give at least a
> hint on what we get wrong.
With NetBSD 9 I used to run my amd64 machine with Driver "radeon" and
Hello,
On Thu, 23 May 2024 09:11:17 +
Riccardo Mottola wrote:
> Michael wrote:
> > Did it crash or did if continue booting? If it continued to boot
> > radeonfb likely got the wiring of outputs to displays wrong.
> > With that, please try with options RADEONFB_BIOS_INIT, which adds code
> >
Hi,
John D. Baker wrote:
Interesting that this works for you. I have several machines with the
ATI ES1000 rev. 0x02 (RN50) video device: HP DL380G5, HP ML310G4, IBM
x3650, Dell PowerEdge 2850 and they all exhibit the "almost-black-on-black"
video problem when booting a kernel built with the
Hi Martin,
Martin Neitzel wrote:
A zillion thanks to John Baker for mailing this! I changed this
on my old HP Proliant DL360 G6 with its ATI ES1000 (RV100) onboard
graphics two weeks ago and --voila-- instant karma!
I envy you! I have a newer chip but it still doesn't like to run :)
JDB> Interesting that this works for you. I have several machines with the
JDB> ATI ES1000 rev. 0x02 (RN50) video device: HP DL380G5, HP ML310G4, IBM
JDB> x3650, Dell PowerEdge 2850 and they all exhibit the "almost-black-on-black"
JDB> video problem when booting a kernel built with the patch
On Thu, 23 May 2024, Martin Neitzel wrote:
> Another late responder, a happy one, though:
>
> > > The following patch (against -current from about 4 years ago) will
> > > enable matching R100/R200 devices:
> > >
> > > +Index: sys/external/bsd/drm2/radeon/radeon_pci.c
> > > [...]
> > > + /* Set
Another late responder, a happy one, though:
> > The following patch (against -current from about 4 years ago) will
> > enable matching R100/R200 devices:
> >
> > +Index: sys/external/bsd/drm2/radeon/radeon_pci.c
> > [...]
> > + /* Set this to false if you want to match R100/R200 */
> > +-bool
Hi John
sorry for the late reply... needed some NetBSD hack time
to find to patch and recompile the kernel.
John D. Baker wrote:
> On Tue, 7 May 2024, Riccardo Mottola wrote:
>
> That looks like the same description of the radeon device in my T42
> ThinkPad:
IN some sense the T43 is successor
Hi,
Michael wrote:
> Did it crash or did if continue booting? If it continued to boot
> radeonfb likely got the wiring of outputs to displays wrong.
> With that, please try with options RADEONFB_BIOS_INIT, which adds code
> to scan the BIOS for output info. This is not enabled by default
>
Hello,
On Wed, 8 May 2024 10:14:55 +
Riccardo Mottola wrote:
> Hi,
>
> Michael wrote:
> >> How do I enable radeonfb? Can I do it through configurations or do I
> >> need to compile my own kernel to try?
> > radeonfb* at pci?
> >
>
> I copied that line from ALL to my custom kernel
On Tue, 7 May 2024, Riccardo Mottola wrote:
> John D. Baker wrote:
> > As you have seen, the "radeon*" and "radeondrmkmsfb*" drivers do not
> > attach on "r100" class devices. They have been explicitly excluded
> > because early in the DRMKMS integration in NetBSD, they exhibited the
> >
Hi,
Michael wrote:
>> How do I enable radeonfb? Can I do it through configurations or do I
>> need to compile my own kernel to try?
> radeonfb* at pci?
>
I copied that line from ALL to my custom kernel build which I did for
iwi debug.
I just get a big black screen... no text, no white cursor.
Hi,
John D. Baker wrote:
> As you have seen, the "radeon*" and "radeondrmkmsfb*" drivers do not
> attach on "r100" class devices. They have been explicitly excluded
> because early in the DRMKMS integration in NetBSD, they exhibited the
> "(almost) black-on-black" video problem described in:
I
As you have seen, the "radeon*" and "radeondrmkmsfb*" drivers do not
attach on "r100" class devices. They have been explicitly excluded
because early in the DRMKMS integration in NetBSD, they exhibited the
"(almost) black-on-black" video problem described in:
Hi Michael,
Michael wrote:
>
> Yeah, I fixed a few problems there, xrender support was broken for r1xx>
> Sun's xvr-100 card is a rebadged rv100...
Wonderful... eager to test.
>> How do I enable radeonfb? Can I do it through configurations or do I
>> need to compile my own kernel to try?
>
>
Hello,
On Tue, 7 May 2024 08:19:33 +
Riccardo Mottola wrote:
> > Radeonfb should Just Work(tm) - it's used mainly on macppc and sparc64
> > but I'm pretty sure it's been run on at least some little endian hw
> > before.
>
> according to radeon manpage, mine would have an R100, the
Hi Michael,
Michael wrote:
> Radeonfb should Just Work(tm) - it's used mainly on macppc and sparc64
> but I'm pretty sure it's been run on at least some little endian hw
> before.
according to radeon manpage, mine would have an R100, the earliest
supported on X11.
How do I enable radeonfb? Can
Hello,
On Mon, 6 May 2024 23:17:12 +
Riccardo Mottola wrote:
> X11, which appears to run fine, reports it as:
> [ 646.096] (II) VESA(0): VESA VBE Total Mem: 16320 kB
> [ 646.096] (II) VESA(0): VESA VBE OEM: ATI MOBILITY RADEON 7500
> [ 646.096] (II) VESA(0): VESA VBE OEM Software Rev:
Hi,
I notice that on 10.0 (but was the same on 9.x too) my old ThinkPad T30
runs in VGA text.
Is there a specific limitaiton for the embedded videocard? a choice? or
something I can try enabling?
dmesg reports it as:
[ 1.005536] acpivga0 at acpi0 (VID): ACPI Display Adapter
[ 1.005536]
21 matches
Mail list logo
