On Sun, 19 Dec 2004 Marc Aurele La France wrote :
On Sat, 18 Dec 2004, ASIF IQBAL wrote:
Marc later I identified it and confirmed that ther was no issue with write of 0x7c. In the meantime I was going through the PCI code of XFree86 file sparcPci.c in function sparcPciInit (). I came across the
On Fri, 17 Dec 2004 Marc Aurele La France wrote :
On Mon, 13 Dec 2004, ASIF IQBAL wrote:
As root, please do (_exactly_ as shown) ...
mmapw -b /dev/fbs/aperture 0x01FE01002864 0x7C
mmapr /dev/fbs/aperture 0x01FE0101 4 /dev/null
... and tell me if the second command (the `mmapr`)
On Sat, 18 Dec 2004, ASIF IQBAL wrote:
Marc later I identified it and confirmed that ther was no issue with write
of 0x7c. In the meantime I was going through the PCI code of XFree86 file
sparcPci.c in function sparcPciInit (). I came across the following
expression for mapping the PCI aperture
On Mon, 13 Dec 2004, ASIF IQBAL wrote:
As root, please do (_exactly_ as shown) ...
mmapw -b /dev/fbs/aperture 0x01FE01002864 0x7C
mmapr /dev/fbs/aperture 0x01FE0101 4 /dev/null
... and tell me if the second command (the `mmapr`) still crashes your
system. The `mmapw` is very important
Hi Marc
After marathon attempts I have brought up the XFree86 on the SPARC machine. Many thanks to the Open source. I have understood a lot on the dispaly and frame buffer concepts which seems to be grey for me intially. Still I am not master but a baby. For this valiant growth I have to thanks
ASIF IQBAL wrote:
When I ran Xsun. I had issue with Key board. I have Type 6 USB keyboard
(Layout 33). I didn't face any issue with keyboard during XFree86. I
have gone through the sunKbd.c and sunKbdMap.c. The support for Type 6
is not available. Where can I get the driver for the same. I have
On Sun, 12 Dec 2004 Marc Aurele La France wrote :
On Fri, 10 Dec 2004, ASIF IQBAL wrote:
Excellent. This seems to be implying that the bus scan is crashing the system when it gets around to probing what's behind your PCI bridge. To confirm this, the command ...
mmapr /dev/fbs/aperture
On Fri, 10 Dec 2004, ASIF IQBAL wrote:
Excellent. This seems to be implying that the bus scan is crashing the
system when it gets around to probing what's behind your PCI bridge. To
confirm this, the command ...
mmapr /dev/fbs/aperture 0x01FE0101 4 /dev/null
... (as root) should
On Fri, 10 Dec 2004 Marc Aurele La France wrote :
On Thu, 9 Dec 2004, ASIF IQBAL wrote:
On Thu, 09 Dec 2004 Marc Aurele La France wrote :
On Wed, 8 Dec 2004, ASIF IQBAL wrote:
Some more inputs I gathered on the scanpci issue are as follows:
1) scanpci () crashing is not consistent all the
On Wed, 8 Dec 2004, ASIF IQBAL wrote:
Some more inputs I gathered on the scanpci issue are as follows:
1) scanpci () crashing is not consistent all the time. After removing my
fix, and with the build procedure suggested by you, once it executed
without system crashing, for a longer duration. But
On Thu, 09 Dec 2004 Marc Aurele La France wrote :
On Wed, 8 Dec 2004, ASIF IQBAL wrote:
Some more inputs I gathered on the scanpci issue are as follows:
1) scanpci () crashing is not consistent all the time. After removing my fix, and with the build procedure suggested by you, once it
On Thu, 9 Dec 2004, ASIF IQBAL wrote:
On Thu, 09 Dec 2004 Marc Aurele La France wrote :
On Wed, 8 Dec 2004, ASIF IQBAL wrote:
Some more inputs I gathered on the scanpci issue are as follows:
1) scanpci () crashing is not consistent all the time. After removing my
fix, and with the build procedure
On Fri, 3 Dec 2004, ASIF IQBAL wrote:
On Fri, 03 Dec 2004 Marc Aurele La France wrote :
On Fri, 3 Dec 2004, ASIF IQBAL wrote:
On further debugging I identifed that the last scanned PCI device was ATI
Technologies Inc Rage XL which is our display card and its tag is
0x1009800. Please refer the
Hi Marc
I have connected to the SUN Blade/SPARC server through putty login and when i ran the /usr/X11R6/bin/scanpci, the last two lines that i got are as bellow.
pci bus 0x0100 cardnum 0x13 function 0x00: vendor 0x1002 device 0x4752
ATI Technologies Inc Rage XL.
and can you please elaborate
On Tue, 7 Dec 2004, ASIF IQBAL wrote:
On further debugging I identifed that the last scanned PCI device was
ATI Technologies Inc Rage XL which is our display card and its tag is
0x1009800. Please refer the following log details of tag numbers and the
PCI device details got from the
Hi Marc
sorry for repetation..
I got the following two lines after executing the command
/export/XFree86/XFree86-4.4/xc/programs/Xserver/hw/xfree86/etc/scanpci.
pci bus 0x0100 cardnum 0x13 function 0x00: vendor 0x1002 device 0x4752
ATI Technologies Inc Rage XL
Regards
ASIF IQBAL
On
Hi Marc
Some more inputs I gathered on the scanpci issue are as follows:
1) scanpci () crashing is not consistent all the time. After removing my fix, and with the build procedure suggested by you, once it executed without system crashing, for a longer duration. But it was running for half an
On Wed, 2 Dec 2004, ASIF IQBAL wrote:
I have attached output of the command prtconf in the log file
prtconfLog. Right now I am not working on the scanpci problem because by
scanning idx = 10 it has detected my VGA card in the system. I have exited
from the PCI device scan while loop and allowed
Hi Marc,
Still the system is hanging even after moving the drivers from the directory mv /usr/X11R6/lib/modules/drivers/sun*_drv.o /temp.
On further debugging the code I identified that the system is hanging in function call xf86scanpci () within the while loop while (idx MAX_PCI_DEVICES tag
On Tue, 30 Nov 2004, ASIF IQBAL wrote:
Still the system is hanging even after moving the drivers from the
directory mv /usr/X11R6/lib/modules/drivers/sun*_drv.o /temp.
On further debugging the code I identified that the system is hanging in
function call xf86scanpci () within the while loop
On Sat, 27 Nov 2004, ASIF IQBAL wrote:
If /dev/fbs/aperture still does not exist on your system, then
either you did not do a reconfigure boot (a simple reboot won't
suffice), or it failed for some reason.
After installing the aperture driver I performed touch /reconfigure
followed by a init 6
Hi Marc
Thanks for your valuable information. I am able to install the aperture driver according to README under aperture/README. The driver compiled for 64 bit and there was no issue with adding the driver. I have confirmed the driver installation with modinfo | grep aperture. But after this
On Sat, 27 Nov 2004, ASIF IQBAL wrote:
On Fri, 26 Nov 2004 Marc Aurele La France wrote :
On Fri, 26 Nov 2004, ASIF IQBAL wrote:
i am trying to bring up XFree86-4.4.0 on solaris-8/SPARC. I have
built the XFree86 source on solaris 8/SPARC, during which i have done the
following.
1. Edited
Hi Marc
If /dev/fbs/aperture still does not exist on your system, then
either you did not do a reconfigure boot (a simple reboot won't suffice), or it failed for some reason.
After installing the aperture driver I performed touch /reconfigure followed by a init 6 as specified in README. And
On Fri, 26 Nov 2004, ASIF IQBAL wrote:
i am trying to bring up XFree86-4.4.0 on solaris-8/SPARC. I have built
the XFree86 source on solaris 8/SPARC, during which i have done the
following.
1. Edited
#define BuildXFree86OnSparcSunOS YES
#define ThreadedX NO
in
25 matches
Mail list logo
