linuxconsole-dev

Re: Re: secondary graphic card has no memory

[Johannes G. <joh...@gm...>]

Ludovic Pollet wrote:
>Maybe you can enable your mga manually with lspci/setpci :
>the idea is to use the config set by the i386 kernel,
>on the amd64 one...
>
>You can create a dump of your matrox pci configuration on your
>i386 kernel, assuming the busid of the mga is 00:0a.a
>       lspci -x -s 00:0a.0 > mga.pci
>
>You will need to transform it into a setpci command line,
>by piping it into this perl script :
>
>#!/usr/bin/perl
>$line=<STDIN>;
>$i = 0;
>while($line = <STDIN>) {
>        $line=~s/^[0-9a-fA-F][0-9a-fA-F]://;
>        while($line=~m/^ ([0-9a-fA-F][0-9a-fA-F])(.*)$/) {
>                $line = $2;
>                print sprintf(" %x.b=$1",$i);
>                $i++;
>        }
>}
>print "\n";
>
>It will give you something looking like :
>  0.b=2b 1.b=10 2.b=1a 3.b=05 4.b=87  ...
>
>Then on the amd64 kernel, issue the setpci command with
>the registers values :
>       setpci -s XX:XX.X 0.b=2b 1.b=10 2.b=1a 3.b=05 4.b=87
>
>If it works, your mga should be enabled in lspci...
>
>Beware that if the memory/IRQ ressources used on i386
>are not available on x86-64,
>it will certainly just crash your box.

Thanks a lot, I tried in both cases:
1) when the MGA is the primary display adapter I performed
above procedure with the NVidia
2) when the NVidia is the primary display adapter I performed
above procedure with the MGA.
The result in both cases is the same: according to
lspci -v the secondary display adapter has no memory.
Anyway it did not crash my computer.

Up to now only one configuration has some promising results:
MGA is primary, NVidia secondary, i386 kernel:
In this case I can start the first XServer on the NVidia (vt7),
and then a second Xserver on the MGA (vt17). Both Xservers
have the prefbusid patch.
After starting the second XServer I still see an image on the
NVidia, I can move the curser, but the keyboard is dead
(no reaction whatever key I press, no leds).
After stopping the second XServer with <Ctrl-Alt-Backspace>
on the second keyboard I must reboot the computer.

When I use x86_64 kernel the secondary graphic card
(MGA or NVidia, whatever) has no memory.
When I use i386 kernel with MGA as secondary
graphic card the memory on the MGA is disabled and I cannot
start an XServer on the MGA.

Johannes Gajdosik

Re: secondary graphic card has no memory

[ludovic p. <pl...@nn...>]

Hello...

Le vendredi 24 Septembre 2004 00:46, Johannes Gajdosik a =E9crit :
> The result in both cases is the same: according to
> lspci -v the secondary display adapter has no memory.
> Anyway it did not crash my computer.

That is strange... Maybe the normal way of configuring pci devices doesn'=
t=20
work on amd64 kernel.=20
That was my problem (due to the hackvideo thing), and in this case, X rep=
orts=20
no errors but silently fails to set the pci configuration...
Can you try the same setpci command with the swithch -H1 ? It asks setpci=
 to=20
bypass the kernel when accessing the pci bus.

> Up to now only one configuration has some promising results:
> MGA is primary, NVidia secondary, i386 kernel:
> In this case I can start the first XServer on the NVidia (vt7),
> and then a second Xserver on the MGA (vt17). Both Xservers
> have the prefbusid patch.

That looks like a virtual console problem...=20
If the MGA is primay, I suppose it is used for the vga console display. I=
n=20
this case you should start the MGA x server on vt7, and NVidia on vt17.
Appart from the keyboard problem, is the first server really dead ?=20
(ie does it respond to mouse click ... ) If not, you can try killing the =
X=20
server with the SIGUSR1 signal.

And are you sure that the prefbusid is correctly set ? I think it is deci=
mal,=20
while lspci reports hexadecimal bus id...

Ludovic Pollet
--=20
If it happens once, it's a bug.
If it happens twice, it's a feature.
If it happens more than twice, it's a design philosophy.

Re: secondary graphic card has no memory

[Aivils <ai...@un...>]

On Friday 24 September 2004 09:17, ludovic pollet wrote:
> Hello...
>=20
> Le vendredi 24 Septembre 2004 00:46, Johannes Gajdosik a =E9crit :
> > The result in both cases is the same: according to
> > lspci -v the secondary display adapter has no memory.
> > Anyway it did not crash my computer.
>=20
> That is strange... Maybe the normal way of configuring pci devices doesn'=
t=20
> work on amd64 kernel.=20
> That was my problem (due to the hackvideo thing), and in this case, X rep=
orts=20
> no errors but silently fails to set the pci configuration...

Hack cannot be a hack if Your X fails with screamy cry.
Agree , usage of hackvideo is a bit lightminded, but may make
life easily for John Doe. During development my X uses pci configuration
very, very rarely, which featrure seems is device driver depended.

> Can you try the same setpci command with the swithch -H1 ? It asks setpci=
 to=20
> bypass the kernel when accessing the pci bus.
>=20
> > Up to now only one configuration has some promising results:
> > MGA is primary, NVidia secondary, i386 kernel:
> > In this case I can start the first XServer on the NVidia (vt7),
> > and then a second Xserver on the MGA (vt17). Both Xservers
> > have the prefbusid patch.
>=20
> That looks like a virtual console problem...=20
> If the MGA is primay, I suppose it is used for the vga console display. I=
n=20
> this case you should start the MGA x server on vt7, and NVidia on vt17.
> Appart from the keyboard problem, is the first server really dead ?=20
> (ie does it respond to mouse click ... ) If not, you can try killing the =
X=20
> server with the SIGUSR1 signal.
>=20
> And are you sure that the prefbusid is correctly set ? I think it is deci=
mal,=20
> while lspci reports hexadecimal bus id...

Wow! Bug.

Aivils