Re: Re: Re: Re: [XFree86] XFree86-4.4.0 Build On Solaris-8/SPARC [Configuration Problem]
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`) still crashes your system. The `mmapw` is very important here. Its effect is to tell your PCI bridge to ignore most PCI errors that occur on its secondary bus segment.
Marc, still the system seems to crashing for the mmapr. I have executed first mampw followed by mmapr. I confirmed this beahviour by trying twice. Is there any way that I could confirm my mmapw of 0x7c is successfull using? Will this work mmapr -b /dev/fbs/aperture 0x01FE01002864. If so were can I
To verify that the value was correctly written, you can pipe mmapr's stdout into /usr/bin/od, i.e. ...
mmapr -b /dev/fbs/aperture 0x01FE01002864 | /usr/bin/od -t x1
There is a typo here. This should have been ...
mmapr -b /dev/fbs/aperture 0x01FE01002864 1 | /usr/bin/od -t x1
... i.e. with the length of the area specified.
I should, at some point, change mmapr to optionally pretty-print its output.
At this point, I need to ask you to install an adapter into one of the machine's PCI slots. Any adapter will do, as long as it's PCI of course. It doesn't even need to be a video adapter. The intent is to put an adapter behind the PCI bridge. If after installing this adapter, the command ...
mmapr /dev/fbs/aperture 0x01FE0101 4 /dev/null
... no longer crashes the system, then please send me the pci5.dat2 that results from ...
mmapr /dev/fbs/aperture 0x01FE01002800 256 pci5.dat2
... and I'll compare that with the pci5.dat you've previously sent. I'll also need to see the updated `prtconf -Ppv` output.
Actually, come to think of it, the prtconf output would be useful whether or not installing the extra adapter crashes the system on the mmapr command.
Marc even after adding the PCI card, still the system crashing. I had Permedia card which I wanted to finally test with XFree86 in sparc. After placing the new card in PCI slot I have taken the prtconf -Ppv output, Please refer the attached log logPci.txt.
Still I have doubt with the mmapw of 0x7C. Because when I read back I am getting octal value of 0. Following is the sequence of comamnd I have executed in the shell.
bash-2.03# mmapw -b /dev/fbs/aperture 0x01FE01002864 0x7C
bash-2.03#
bash-2.03# mmapr -b /dev/fbs/aperture 0x01FE01002864 | /usr/bin/od -t x1
mmapr [-{bwlqL}] file offset length
endianness flags:
-b output one byte at a time
-w output up to two aligned bytes at a time
-l output up to four aligned bytes at a time (default)
-q output up to eight aligned bytes at a time
-L same as -l
000
bash-2.03# mmapr /dev/fbs/aperture 0x01FE0101 4 /dev/null
-- System hanged here -
Is the second mmapr is as expected or not ?
See above.
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 memory. There seems to be some type mismatch for the fourth parameter.
domain.pci = (char *)sparcMapAperture(-1, VIDMEM_MMIO,
pci_addr + PCI_MAKE_TAG(domain.bus_min, 0, 0),
PCI_MAKE_TAG(domain.bus_max - domain.bus_min + 1, 0, 0)) -
PCI_MAKE_TAG(domain.bus_min, 0, 0);
ie there seems to be one extra bracket closed before the -. Is this the way the final expreessions needs to be. I am not sure. Can you look into it.
PCI_MAKE_TAG(domain.bus_max - domain.bus_min + 1, 0, 0)) -
^
^
Another Issue that I came across was that printing using xf86MsgVerb behaves abnormally. I am having this issue whne I have more than one prameter for xf86MsgVerb. Trying to do folloiwng has issue.
data1 = 0x0;
data2 = 0x200;
xf86MsgVerb (Value data1 = 0x%x data2 = 0x%x \n, data1, data2)
Given the system still hangs, even after installing an adapter, I have requested access to such a machine here on campus so that I can explore this problem more thouroughly. I'll get back to you.
Marc.
Thanks for your effort. I am also parallely working on this. Let me give you more inputs in course.
Thanks.
ASIF IQBAL
+--+---+
| Marc Aurele La France | work: 1-780-492-9310 |
| Computing and Network Services | fax: 1-780-492-1729 |
| 352 General Services Building | email: [EMAIL PROTECTED] |
| University of Alberta +---+
| Edmonton, Alberta| |
| T6G 2H1 | Standard disclaimers apply |
| CANADA | |
+--+---+
XFree86 developer and VP. ATI driver and X
Re: Re: Re: Re: [XFree86] XFree86-4.4.0 Build On Solaris-8/SPARC [Configuration Problem]
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 memory. There seems to be some type mismatch for the fourth parameter. domain.pci = (char *)sparcMapAperture(-1, VIDMEM_MMIO, pci_addr + PCI_MAKE_TAG(domain.bus_min, 0, 0), PCI_MAKE_TAG(domain.bus_max - domain.bus_min + 1, 0, 0)) - PCI_MAKE_TAG(domain.bus_min, 0, 0); ie there seems to be one extra bracket closed before the -. Is this the way the final expreessions needs to be. I am not sure. Can you look into it. PCI_MAKE_TAG(domain.bus_max - domain.bus_min + 1, 0, 0)) - ^ That not-so-extra parenthesis ends the arguments to be passed to sparcMapAperture(). Another Issue that I came across was that printing using xf86MsgVerb behaves abnormally. I am having this issue whne I have more than one prameter for xf86MsgVerb. Trying to do folloiwng has issue. data1 = 0x0; data2 = 0x200; xf86MsgVerb (Value data1 = 0x%x data2 = 0x%x \n, data1, data2) Look at the prototype for that function in common/xf86.h. Marc. +--+---+ | Marc Aurele La France | work: 1-780-492-9310 | | Computing and Network Services | fax:1-780-492-1729 | | 352 General Services Building | email: [EMAIL PROTECTED] | | University of Alberta +---+ | Edmonton, Alberta | | | T6G 2H1 | Standard disclaimers apply| | CANADA | | +--+---+ XFree86 developer and VP. ATI driver and X server internals. ___ XFree86 mailing list [EMAIL PROTECTED] http://XFree86.Org/mailman/listinfo/xfree86
Re: Re: Re: [XFree86] XFree86-4.4.0 Build On Solaris-8/SPARC [Configuration Problem]
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 here. Its effect is to tell your
PCI bridge to ignore most PCI errors that occur on its secondary bus
segment.
Marc, still the system seems to crashing for the mmapr. I have executed
first mampw followed by mmapr. I confirmed this beahviour by trying twice.
Is there any way that I could confirm my mmapw of 0x7c is successfull
using? Will this work mmapr -b /dev/fbs/aperture 0x01FE01002864. If so
were can I
To verify that the value was correctly written, you can pipe mmapr's stdout
into /usr/bin/od, i.e. ...
mmapr -b /dev/fbs/aperture 0x01FE01002864 | /usr/bin/od -t x1
There is a typo here. This should have been ...
mmapr -b /dev/fbs/aperture 0x01FE01002864 1 | /usr/bin/od -t x1
... i.e. with the length of the area specified.
I should, at some point, change mmapr to optionally pretty-print its
output.
At this point, I need to ask you to install an adapter into one of the
machine's PCI slots. Any adapter will do, as long as it's PCI of course.
It doesn't even need to be a video adapter. The intent is to put an
adapter behind the PCI bridge. If after installing this adapter, the
command ...
mmapr /dev/fbs/aperture 0x01FE0101 4 /dev/null
... no longer crashes the system, then please send me the pci5.dat2 that
results from ...
mmapr /dev/fbs/aperture 0x01FE01002800 256 pci5.dat2
... and I'll compare that with the pci5.dat you've previously sent. I'll
also need to see the updated `prtconf -Ppv` output.
Actually, come to think of it, the prtconf output would be useful whether
or not installing the extra adapter crashes the system on the mmapr
command.
Marc even after adding the PCI card, still the system crashing. I had
Permedia card which I wanted to finally test with XFree86 in sparc. After
placing the new card in PCI slot I have taken the prtconf -Ppv output,
Please refer the attached log logPci.txt.
Still I have doubt with the mmapw of 0x7C. Because when I read back I am
getting octal value of 0. Following is the sequence of comamnd I have
executed in the shell.
bash-2.03# mmapw -b /dev/fbs/aperture 0x01FE01002864 0x7C
bash-2.03#
bash-2.03# mmapr -b /dev/fbs/aperture 0x01FE01002864 | /usr/bin/od -t x1
mmapr [-{bwlqL}] file offset length
endianness flags:
-b output one byte at a time
-w output up to two aligned bytes at a time
-l output up to four aligned bytes at a time (default)
-q output up to eight aligned bytes at a time
-L same as -l
000
bash-2.03# mmapr /dev/fbs/aperture 0x01FE0101 4 /dev/null
-- System hanged here -
Is the second mmapr is as expected or not ?
See above.
Given the system still hangs, even after installing an adapter, I have
requested access to such a machine here on campus so that I can explore this
problem more thouroughly. I'll get back to you.
Marc.
+--+---+
| Marc Aurele La France | work: 1-780-492-9310 |
| Computing and Network Services | fax:1-780-492-1729 |
| 352 General Services Building | email: [EMAIL PROTECTED] |
| University of Alberta +---+
| Edmonton, Alberta | |
| T6G 2H1 | Standard disclaimers apply|
| CANADA | |
+--+---+
XFree86 developer and VP. ATI driver and X server internals.
___
XFree86 mailing list
[EMAIL PROTECTED]
http://XFree86.Org/mailman/listinfo/xfree86
Re: Re: Re: [XFree86] XFree86-4.4.0 Build On Solaris-8/SPARC [Configuration Problem]
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 0x01FE0101 4 /dev/null
... (as root) should consistently crash the system. Does it?
Marc you are right. The system is crashed after the execution of the command. I have confirmed this behaviour by repeating twice.
Also, please do as root after a fresh reboot ...
mmapr /dev/fbs/aperture 0x01FE01002800 256 pci5.dat
... and send me 'pci5.dat' as an attachment. This is a dump of the PCI bridge's configuration space (i.e. binary data), which hopefully will tell me what needs to be done to prevent the crash.
I have attached the pci5.dat binary as requested which is got by executing the mmap command. And this didn't have any effect (ie. no system crash). Can you elaborate the significance of the address for mmapr function.
`mmapr /dev/fbs/aperture` reads the CPU's physical address space. This address space is divided into various sub-areas (system memory, PCI configuration, PCI I/O, PCI memory, to name a few). In your case, PCI configuration space resides at displacement 0x01FE0100 within this address space for a total length of 128KB. But, for some reason we are hopefully about to determine, the top 64K of this space is not accessible, and it should be.
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 here. Its effect is to tell your PCI bridge to ignore most PCI errors that occur on its secondary bus segment.
Marc, still the system seems to crashing for the mmapr. I have executed first mampw followed by mmapr. I confirmed this beahviour by trying twice. Is there any way that I could confirm my mmapw of 0x7c is successfull using? Will this work mmapr -b /dev/fbs/aperture 0x01FE01002864. If so were can I
To verify that the value was correctly written, you can pipe mmapr's stdout into /usr/bin/od, i.e. ...
mmapr -b /dev/fbs/aperture 0x01FE01002864 | /usr/bin/od -t x1
I should, at some point, change mmapr to optionally pretty-print its output.
see the read value ? In the console or else. I will stay today overnight so that I can try the steps suggested by you and reply you immedieatly. Please confirm me if you need, so that we can complete this issue and will allow me to proceed furter.
At this point, I need to ask you to install an adapter into one of the machine's PCI slots. Any adapter will do, as long as it's PCI of course. It doesn't even need to be a video adapter. The intent is to put an adapter behind the PCI bridge. If after installing this adapter, the command ...
mmapr /dev/fbs/aperture 0x01FE0101 4 /dev/null
... no longer crashes the system, then please send me the pci5.dat2 that results from ...
mmapr /dev/fbs/aperture 0x01FE01002800 256 pci5.dat2
... and I'll compare that with the pci5.dat you've previously sent. I'll also need to see the updated `prtconf -Ppv` output.
Actually, come to think of it, the prtconf output would be useful whether or not installing the extra adapter crashes the system on the mmapr command.
Marc even after adding the PCI card, still the system crashing. I had Permedia card which I wanted to finally test with XFree86 in sparc. After placing the new card in PCI slot I have taken the prtconf -Ppv output, Please refer the attached log logPci.txt.
Still I have doubt with the mmapw of 0x7C. Because when I read back I am getting octal value of 0. Following is the sequence of comamnd I have executed in the shell.
bash-2.03# mmapw -b /dev/fbs/aperture 0x01FE01002864 0x7C
bash-2.03#
bash-2.03# mmapr -b /dev/fbs/aperture 0x01FE01002864 | /usr/bin/od -t x1
mmapr [-{bwlqL}] file offset length
endianness flags:
-b output one byte at a time
-w output up to two aligned bytes at a time
-l output up to four aligned bytes at a time (default)
-q output up to eight aligned bytes at a time
-L same as -l
000
bash-2.03# mmapr /dev/fbs/aperture 0x01FE0101 4 /dev/null
-- System hanged here -
Is the second mmapr is as expected or not ?
Regards
ASIF IQBAL
System Configuration: Sun Microsystems sun4u
Memory size: 256 Megabytes
System Peripherals (PROM Nodes):
Node 0xf0029b10
boot-retained-page:
energystar-v3:
idprom:
01830003.ba0cd77b.03ba.0cd77b82....
scsi-initiator-id: 0007
reset-reason: 'POR'
breakpoint-trap: 007f
#size-cells: 0002
model: 'SUNW,375-0096'
name: 'SUNW,Sun-Blade-100'
clock-frequency: 04fca6ea
banner-name: 'Sun Blade 100 (UltraSPARC-IIe)'
device_type: 'upa'
stick-frequency:
Re: Re: [XFree86] XFree86-4.4.0 Build On Solaris-8/SPARC [Configuration Problem]
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 consistently crash the system. Does it? Marc you are right. The system is crashed after the execution of the command. I have confirmed this behaviour by repeating twice. Also, please do as root after a fresh reboot ... mmapr /dev/fbs/aperture 0x01FE01002800 256 pci5.dat ... and send me 'pci5.dat' as an attachment. This is a dump of the PCI bridge's configuration space (i.e. binary data), which hopefully will tell me what needs to be done to prevent the crash. I have attached the pci5.dat binary as requested which is got by executing the mmap command. And this didn't have any effect (ie. no system crash). Can you elaborate the significance of the address for mmapr function. `mmapr /dev/fbs/aperture` reads the CPU's physical address space. This address space is divided into various sub-areas (system memory, PCI configuration, PCI I/O, PCI memory, to name a few). In your case, PCI configuration space resides at displacement 0x01FE0100 within this address space for a total length of 128KB. But, for some reason we are hopefully about to determine, the top 64K of this space is not accessible, and it should be. 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 here. Its effect is to tell your PCI bridge to ignore most PCI errors that occur on its secondary bus segment. Marc, still the system seems to crashing for the mmapr. I have executed first mampw followed by mmapr. I confirmed this beahviour by trying twice. Is there any way that I could confirm my mmapw of 0x7c is successfull using? Will this work mmapr -b /dev/fbs/aperture 0x01FE01002864. If so were can I To verify that the value was correctly written, you can pipe mmapr's stdout into /usr/bin/od, i.e. ... mmapr -b /dev/fbs/aperture 0x01FE01002864 | /usr/bin/od -t x1 I should, at some point, change mmapr to optionally pretty-print its output. see the read value ? In the console or else. I will stay today overnight so that I can try the steps suggested by you and reply you immedieatly. Please confirm me if you need, so that we can complete this issue and will allow me to proceed furter. At this point, I need to ask you to install an adapter into one of the machine's PCI slots. Any adapter will do, as long as it's PCI of course. It doesn't even need to be a video adapter. The intent is to put an adapter behind the PCI bridge. If after installing this adapter, the command ... mmapr /dev/fbs/aperture 0x01FE0101 4 /dev/null ... no longer crashes the system, then please send me the pci5.dat2 that results from ... mmapr /dev/fbs/aperture 0x01FE01002800 256 pci5.dat2 ... and I'll compare that with the pci5.dat you've previously sent. I'll also need to see the updated `prtconf -Ppv` output. Actually, come to think of it, the prtconf output would be useful whether or not installing the extra adapter crashes the system on the mmapr command. Thanks. Marc. +--+---+ | Marc Aurele La France | work: 1-780-492-9310 | | Computing and Network Services | fax:1-780-492-1729 | | 352 General Services Building | email: [EMAIL PROTECTED] | | University of Alberta +---+ | Edmonton, Alberta | | | T6G 2H1 | Standard disclaimers apply| | CANADA | | +--+---+ XFree86 developer and VP. ATI driver and X server internals. ___ XFree86 mailing list [EMAIL PROTECTED] http://XFree86.Org/mailman/listinfo/xfree86
Re: Re: [XFree86] XFree86-4.4.0 Build On Solaris-8/SPARC [Configuration Problem]
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 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 hour or so never ending, until I killed the process using Ctrl-c. 2) When I tried connecting remotely to the sparc, it never gave me a consistent output. The best last few lines that I could get are given below (and is got through the visual observation only). pciGenFindNext: pciDeviceTag = 0x100f800, devid = 0x pciGenFindNext: pciBusNum 256 pciGenFindNext: pciFuncNum 0 pciReadLong(0x100f800, 0) pciGenFindNext: next bus pciGenFindNext: pciBusInfo[257] = 0x891b0 pciGenFindNext: [257, 0, 0] pciReadLong(0x101, 0) This I got with a slight delay placed in pciReadLong () function within the if condition. This delay was added by me to breath for some time to place the log output in the console. 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 consistently crash the system. Does it? Marc you are right. The system is crashed after the execution of the command. I have confirmed this behaviour by repeating twice. Also, please do as root after a fresh reboot ... mmapr /dev/fbs/aperture 0x01FE01002800 256 pci5.dat ... and send me 'pci5.dat' as an attachment. This is a dump of the PCI bridge's configuration space (i.e. binary data), which hopefully will tell me what needs to be done to prevent the crash. Note that I'm assumning `mmapr` is in your $PATH. It should have been installed as '/usr/X11R6/bin/mmapr'. Be very careful with this utility. Typographical errors in its use can be disastrous. I have attached the pci5.dat binary as requested which is got by executing the mmap command. And this didn't have any effect (ie. no system crash). Can you elaborate the significance of the address for mmapr function. `mmapr /dev/fbs/aperture` reads the CPU's physical address space. This address space is divided into various sub-areas (system memory, PCI configuration, PCI I/O, PCI memory, to name a few). In your case, PCI configuration space resides at displacement 0x01FE0100 within this address space for a total length of 128KB. But, for some reason we are hopefully about to determine, the top 64K of this space is not accessible, and it should be. 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 here. Its effect is to tell your PCI bridge to ignore most PCI errors that occur on its secondary bus segment. Marc, still the system seems to crashing for the mmapr. I have executed first mampw followed by mmapr. I confirmed this beahviour by trying twice. Is there any way that I could confirm my mmapw of 0x7c is successfull using ? Will this work mmapr -b /dev/fbs/aperture 0x01FE01002864. If so were can I see the read value ? In the console or else. I will stay today overnight so that I can try the steps suggested by you and reply you immedieatly. Please confirm me if you need, so that we can complete this issue and will allow me to proceed furter. If this works, i.e. no crash, I can then change the X server's (and scanpci's) bus scan to do the same thing and this problem will be solved. Thanks. Marc. +--+---+ | Marc Aurele La France | work: 1-780-492-9310 | | Computing and Network Services | fax: 1-780-492-1729 | | 352 General Services Building | email: [EMAIL PROTECTED] | | University of Alberta +---+ | Edmonton, Alberta| | | T6G 2H1 | Standard disclaimers apply | | CANADA | | +--+---+ XFree86 developer and VP. ATI driver and X server internals.
Re: Re: Re: [XFree86] XFree86-4.4.0 Build On Solaris-8/SPARC [Configuration Problem]
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 as specified in README. And also after reboot I confirmed the existence of /dev/fbs/aperture in the system. Then I issued the command to configure XFree86 using XFree86 -configure which resulted in a system hang. I power-cycled the system and checked the /var/log/messages, couldn't see any messages. How can I confirm that my aperture driver is working fine ? And I am not getting the reason for system hang when I ran XFree86 -configure. Am I missing any other configuration ?... Also, if you used gcc to generate the aperture driver, ensure its version is 3.2 or later. Earlier gcc's simply won't work. My gcc version is 3.4.2 and version details are bash-2.03# gcc -v Reading specs from /usr/local/lib/gcc/sparc-sun-solaris2.8/3.4.2/specs Configured with: ../configure --with-as=/usr/ccs/bin/as --with-ld=/usr/ccs/bin/ld --disable-nls Thread model: posix gcc version 3.4.2 My system configuration is $uname -a SunOS testhost 5.8 Generic_108528-13 sun4u sparc SUNW,Sun-Blade-100 The only possible explanation for this behaviour that I can think of right now is that this system contains one or more SBUS or UPA display adapter(s). Only PCI display adapters are known to work in the UltraSPARC/SunOS port. Although I'm working to correct that, that code just isn't ready yet. Move /usr/X11R6/lib/modules/drivers/sun*_drv.o elsewhere, and retry `XFree86 -configure` Marc. +--+---+ | Marc Aurele La France | work: 1-780-492-9310 | | Computing and Network Services | fax:1-780-492-1729 | | 352 General Services Building | email: [EMAIL PROTECTED] | | University of Alberta +---+ | Edmonton, Alberta | | | T6G 2H1 | Standard disclaimers apply| | CANADA | | +--+---+ XFree86 developer and VP. ATI driver and X server internals. ___ XFree86 mailing list [EMAIL PROTECTED] http://XFree86.Org/mailman/listinfo/xfree86
Re: Re: [XFree86] XFree86-4.4.0 Build On Solaris-8/SPARC [Configuration Problem]
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 step when I tried once again, XFree86 -configure the system hangs. The last line of then console output as follows. (==) Log file: /var/log/XFree86.0.log, Time: Fri Nov 26 16:50:37 2004 Then I restarted the system, and when I checked XFree86.0.log, I could not see any messages. Am I missing still any configuration steps. Can this error be associated with (WW) xf86LinearVidMem: linear memory access disabled. Can you explain possible reasons for this error. Did I miss any specific configuration during building. Regards Asif Iqbal. 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 #define BuildXFree86OnSparcSunOS YES #define ThreadedX NO in xc/programs/Xserver/hw/xfree86/etc/bindist/Solaris/host.def 2. Copy host.def as cp xc/programs/Xserver/hw/xfree86/etc/bindist/Solaris/host.def xc/config/cf/ 3. vi config/imake/Makefile.ini change CC = gcc PREPROCESS_CMD = gcc -E 4. make World World.log 21 tail -f World.log During building i got the error in xc/programs/glxinfo/ directory that __eprintf: symbol referencing error. for that change CC=g++ in Makefile of glxinfo directory. then again i build it with just make. got an error of png.h not found. For that install libpng and build once again. After building, i installed the binaries by the command make install then while i try to configure by XFree86 -configure i got the following error log. can anybody give me the solution for this?... [...] (WW) xf86LinearVidMem: failed to open /dev/fbs/aperture (No such file or directory) (WW) xf86LinearVidMem: either /dev/fbs/aperture or /dev/xsvc device driver required (WW) xf86LinearVidMem: linear memory access disabled Read these. Then follow that up with README.Solaris. Marc. +--+---+ | Marc Aurele La France | work: 1-780-492-9310 | | Computing and Network Services | fax: 1-780-492-1729 | | 352 General Services Building | email: [EMAIL PROTECTED] | | University of Alberta +---+ | Edmonton, Alberta| | | T6G 2H1 | Standard disclaimers apply | | CANADA | | +--+---+ XFree86 developer and VP. ATI driver and X server internals. ___ XFree86 mailing list [EMAIL PROTECTED] http://XFree86.Org/mailman/listinfo/xfree86
Re: Re: [XFree86] XFree86-4.4.0 Build On Solaris-8/SPARC [Configuration Problem]
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 #define BuildXFree86OnSparcSunOS YES #define ThreadedX NO in xc/programs/Xserver/hw/xfree86/etc/bindist/Solaris/host.def 2. Copy host.def as cp xc/programs/Xserver/hw/xfree86/etc/bindist/Solaris/host.def xc/config/cf/ 3. vi config/imake/Makefile.ini change CC = gcc PREPROCESS_CMD = gcc -E 4. make World World.log 21 tail -f World.log During building i got the error in xc/programs/glxinfo/ directory that __eprintf: symbol referencing error. for that change CC=g++ in Makefile of glxinfo directory. then again i build it with just make. got an error of png.h not found. For that install libpng and build once again. After building, i installed the binaries by the command make install then while i try to configure by XFree86 -configure i got the following error log. can anybody give me the solution for this?... [...] (WW) xf86LinearVidMem: failed to open /dev/fbs/aperture (No such file or directory) (WW) xf86LinearVidMem: either /dev/fbs/aperture or /dev/xsvc device driver required (WW) xf86LinearVidMem: linear memory access disabled Read these. Then follow that up with README.Solaris. 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 step when I tried once again, XFree86 -configure the system hangs. The last line of then console output as follows. (==) Log file: /var/log/XFree86.0.log, Time: Fri Nov 26 16:50:37 2004 Then I restarted the system, and when I checked XFree86.0.log, I could not see any messages. Am I missing still any configuration steps. Can this error be associated with (WW) xf86LinearVidMem: linear memory access disabled. Can you explain possible reasons for this error. Did I miss any specific configuration during building. 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. Check /var/log/messages. Also, if you used gcc to generate the aperture driver, ensure its version is 3.2 or later. Earlier gcc's simply won't work. Marc. +--+---+ | Marc Aurele La France | work: 1-780-492-9310 | | Computing and Network Services | fax:1-780-492-1729 | | 352 General Services Building | email: [EMAIL PROTECTED] | | University of Alberta +---+ | Edmonton, Alberta | | | T6G 2H1 | Standard disclaimers apply| | CANADA | | +--+---+ XFree86 developer and VP. ATI driver and X server internals. ___ XFree86 mailing list [EMAIL PROTECTED] http://XFree86.Org/mailman/listinfo/xfree86
Re: Re: Re: [XFree86] XFree86-4.4.0 Build On Solaris-8/SPARC [Configuration Problem]
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 also after reboot I confirmed the existence of /dev/fbs/aperture in the system. Then I issued the command to configure XFree86 using XFree86 -configure which resulted in a system hang. I power-cycled the system and checked the /var/log/messages, couldn't see any messages. How can I confirm that my aperture driver is working fine ? And I am not getting the reason for system hang when I ran XFree86 -configure. Am I missing any other configuration ?... Also, if you used gcc to generate the aperture driver, ensure its version is 3.2 or later. Earlier gcc's simply won't work. My gcc version is 3.4.2 and version details are bash-2.03# gcc -v Reading specs from /usr/local/lib/gcc/sparc-sun-solaris2.8/3.4.2/specs Configured with: ../configure --with-as=/usr/ccs/bin/as --with-ld=/usr/ccs/bin/ld --disable-nls Thread model: posix gcc version 3.4.2 My system configuration is $uname -a SunOS testhost 5.8 Generic_108528-13 sun4u sparc SUNW,Sun-Blade-100 Regards Asif Iqbal. On Sat, 27 Nov 2004 Marc Aurele La France wrote : 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 #define BuildXFree86OnSparcSunOS YES #define ThreadedX NO in xc/programs/Xserver/hw/xfree86/etc/bindist/Solaris/host.def 2. Copy host.def as cp xc/programs/Xserver/hw/xfree86/etc/bindist/Solaris/host.def xc/config/cf/ 3. vi config/imake/Makefile.ini change CC = gcc PREPROCESS_CMD = gcc -E 4. make World World.log 21 tail -f World.log During building i got the error in xc/programs/glxinfo/ directory that __eprintf: symbol referencing error. for that change CC=g++ in Makefile of glxinfo directory. then again i build it with just make. got an error of png.h not found. For that install libpng and build once again. After building, i installed the binaries by the command make install then while i try to configure by XFree86 -configure i got the following error log. can anybody give me the solution for this?... [...] (WW) xf86LinearVidMem: failed to open /dev/fbs/aperture (No such file or directory) (WW) xf86LinearVidMem: either /dev/fbs/aperture or /dev/xsvc device driver required (WW) xf86LinearVidMem: linear memory access disabled Read these. Then follow that up with README.Solaris. 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 step when I tried once again, XFree86 -configure the system hangs. The last line of then console output as follows. (==) Log file: /var/log/XFree86.0.log, Time: Fri Nov 26 16:50:37 2004 Then I restarted the system, and when I checked XFree86.0.log, I could not see any messages. Am I missing still any configuration steps. Can this error be associated with (WW) xf86LinearVidMem: linear memory access disabled. Can you explain possible reasons for this error. Did I miss any specific configuration during building. 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. Check /var/log/messages. Also, if you used gcc to generate the aperture driver, ensure its version is 3.2 or later. Earlier gcc's simply won't work. Marc. +--+---+ | Marc Aurele La France | work: 1-780-492-9310 | | Computing and Network Services | fax: 1-780-492-1729 | | 352 General Services Building | email: [EMAIL PROTECTED] | | University of Alberta +---+ | Edmonton, Alberta| | | T6G 2H1 | Standard disclaimers apply | | CANADA | | +--+---+ XFree86 developer and VP. ATI driver and X server internals. ___ XFree86 mailing list [EMAIL PROTECTED] http://XFree86.Org/mailman/listinfo/xfree86
