[WiP / Orange Pi One] Support for the upcoming Orange Pi One?


Recommended Posts

Armbian is a community driven open source project. Do you like to contribute your code?

Sorry, my fault. It should read "need not" instead of "must not" (see the sprunge.us link above, that's a Mac disk containing backups -- armbianmonitor does no harm to it)

 

And this can be tested on any OPi model als long as some sort of disk is attached (be it HDD or SSD -- thumb drives don't support SMART so testing them is useless)

Link to post
Share on other sites

armbianmonitor doesn't seem to be available? or am I doing something wrong? I just copied "wget" command earlier in topic

 

---response begin---
HTTP/1.1 404 Not Found
Content-Security-Policy: default-src 'none'; style-src 'unsafe-inline'
X-XSS-Protection: 1; mode=block
X-Frame-Options: deny
X-Content-Type-Options: nosniff
Strict-Transport-Security: max-age=31536000
X-GitHub-Request-Id: 17EB2B16:2E30:101968A4:56DF337E
Content-Length: 9
Accept-Ranges: bytes
Date: Tue, 08 Mar 2016 20:18:06 GMT
Via: 1.1 varnish
Connection: keep-alive
X-Served-By: cache-ams4120-AMS
X-Cache: MISS
X-Cache-Hits: 0
Vary: Authorization,Accept-Encoding
Access-Control-Allow-Origin: *
X-Fastly-Request-ID: 2cf8cd3563428ea00d4501e6bcbb477968794885
Expires: Tue, 08 Mar 2016 20:23:06 GMT
Source-Age: 0

Link to post
Share on other sites

Why would you want to do this? The driver should already be included and last commit is 10 days old so it should work with 5.04 out of the box.

 

If there's a problem it would help if you try to explain the problem in a way others can understand/help/fix. Describe which OS image you're using, describe what you're doing, describe what you expect that should happen and what happens in reality. Without providing at least dmesg and lsusb output (using something like pastebin.com!) I fear we can't help at all.

Device used : AC600 ( 7610U chip set)

USB device string  0e8d:7610

Armbian 5.05 has driver 7601. README.md says "# DON'T USE!! This driver is old + buggy - use the official Linux driver instead"

 

Tried the drivers from http://www.mediatek.com/AmazonS3/Downloads/linux/mt7610u_wifi_sta_v3002_dpo_20130916.tar.bz2.

 

Compiled and installed with armbian kernel 3.4.110-sun8i without issue .

 

Here is the quick steps :

 

modprobe -f mt7610u_sta

ifconfig ra0 up

iwpriv ra0 set WirelessMode=Managed

iwpriv ra0 set AuthMode=WPA2PSK

iwpriv ra0 set EncrypType=AES

iwpriv ra0 set SSID=xxxxxxxx

iwpriv ra0 set WPAPSK=xxxxxx

dhclient ra0

 

 root@orangepione:~# iwconfig ra0

ra0       Ralink STA  ESSID:"xxxxxxxx"  Nickname:"MT7610U_STA"

          Mode:Managed  Frequency=2.412 GHz  Access Point: 64:09:80:7B:7E:B6

          Bit Rate=48 Mb/s

          RTS thr:off   Fragment thr:off

          Encryption key:43E2-F2C5-C297-3556-3F48-A7FF-35A9-7B6C   Security mode:restricted   Security mode:open

          Link Quality=73/100  Signal level:-70 dBm  Noise level:-99 dBm

          Rx invalid nwid:0  Rx invalid crypt:0  Rx invalid frag:0

          Tx excessive retries:0  Invalid misc:0   Missed beacon:0

 

root@orangepione:~# ifconfig ra0

ra0       Link encap:Ethernet  HWaddr 80:3f:5d:16:47:a4

          inet addr:192.168.1.115  Bcast:192.168.1.255  Mask:255.255.255.0

          inet6 addr: fe80::823f:5dff:fe16:47a4/64 Scope:Link

          UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1

          RX packets:4182 errors:0 dropped:0 overruns:0 frame:0

          TX packets:241 errors:0 dropped:0 overruns:0 carrier:0

          collisions:0 txqueuelen:1000

          RX bytes:1236394 (1.1 MiB)  TX bytes:31385 (30.6 KiB)

 

root@orangepione:~#

 

Link to post
Share on other sites

Tried Armbian 5.05 and here are some issues I found.

1. The auto mount of USB drive is not working.

2. The eject or umount of USB drive is not working.

3. The HW decode of video using MPV is not working. B.t.w., the MPV preinstalled is old which is 0.6.6 while the newest is 0.14.

4. The Mali400 driver seems to work, but no libmali.so and libEGL.so in /usr/lib.

5. Booting takes a long time even after configured the board type and created user account. Booting time is way slower than the 3.4.39 kernel. It will pause about a minute to boot after pressing reboot.

Link to post
Share on other sites

Care to write a compilation guide?.

Device used : AC600 ( 7610U chip set)

USB device string 0e8d:7610

Armbian 5.05 has driver 7601. README.md says "# DON'T USE!! This driver is old + buggy - use the official Linux driver instead"

Tried the drivers from http://www.mediatek.com/AmazonS3/Downloads/linux/mt7610u_wifi_sta_v3002_dpo_20130916.tar.bz2.

Compiled and installed with armbian kernel 3.4.110-sun8i without issue .

Here is the quick steps :

modprobe -f mt7610u_sta

ifconfig ra0 up

iwpriv ra0 set WirelessMode=Managed

iwpriv ra0 set AuthMode=WPA2PSK

iwpriv ra0 set EncrypType=AES

iwpriv ra0 set SSID=xxxxxxxx

iwpriv ra0 set WPAPSK=xxxxxx

dhclient ra0

 

root@orangepione:~# iwconfig ra0

ra0 Ralink STA ESSID:"xxxxxxxx" Nickname:"MT7610U_STA"

Mode:Managed Frequency=2.412 GHz Access Point: 64:09:80:7B:7E:B6

Bit Rate=48 Mb/s

RTS thr:off Fragment thr:off

Encryption key:43E2-F2C5-C297-3556-3F48-A7FF-35A9-7B6C Security mode:restricted Security mode:open

Link Quality=73/100 Signal level:-70 dBm Noise level:-99 dBm

Rx invalid nwid:0 Rx invalid crypt:0 Rx invalid frag:0

Tx excessive retries:0 Invalid misc:0 Missed beacon:0

root@orangepione:~# ifconfig ra0

ra0 Link encap:Ethernet HWaddr 80:3f:5d:16:47:a4

inet addr:192.168.1.115 Bcast:192.168.1.255 Mask:255.255.255.0

inet6 addr: fe80::823f:5dff:fe16:47a4/64 Scope:Link

UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1

RX packets:4182 errors:0 dropped:0 overruns:0 frame:0

TX packets:241 errors:0 dropped:0 overruns:0 carrier:0

collisions:0 txqueuelen:1000

RX bytes:1236394 (1.1 MiB) TX bytes:31385 (30.6 KiB)

root@orangepione:~#

 

Link to post
Share on other sites

Here are the patches I've prepared for getting I2C and SPI on OrangePiPC under 4.4.4.

 

BTW, Tkaiser, I wouldn't been able to add the last I2C (TWI_R where the PMIC is attached) because lack of PL* pins in the current H3 pinctrl.

I would'nt like start new task for that since the mainline guys already working to have another H3 R_PinCtrl : https://lkml.org/lkml/2016/2/1/150

(quoting my self ...)

While doing some tests on SPI from Python scripts, I figure out that there were bugs in orangepi_PC_gpio_pyH3-master, I've found them and fix them !

Since orangepi_PC_gpio_pyH3-master come from Olimex pyA20, I've decided to look there too, updating my Olimex A20-Micro, rebuild Armbian image, checking SPIs ...

Same bugs, but also same issue of no SPI well defined in DTS for sun7i-a20-olinuxino-micro.dts !

I've some DTS edit, I hope to be able to prepare a patch for that too ..

Link to post
Share on other sites

The libvdpau-sunxi is not working due to the wrong kernel header files. The github source seems using 3.4.39 kernel header files. You can check the files in folder /libvdpau-sunxi/kernel-headers. Where to find the according 3.4.110-sunxi8i header files?

Link to post
Share on other sites

I have tried the new official Jessie Desktop on my OpiPC without any luck.  I booted up the first time with my usb HD plugged in. The PiPc was recongnized as OrangePi2mini. (?) I unplugged the HD and rebooted again; now I get (via ssh)

Attention: It seems the image is running on Orange Pi PC but you're using wrong settings: orangepi2.bin

I have tried to change the Display settings with h3disp, but I can not get any outputvia HDMI...

 

Edit:

Second try  Ihave burned the Image to SD card again, booted without attached Starage Device, the OPPIc is recongnized at first boot, HDMI is working.

 

 

Edit2: USB Storage :http://sprunge.us/ADEU

 

Regards

Link to post
Share on other sites

"deteriorating" proposal:

It would be possible to add a timer menu to manually set the type of board at first run? At least until then, until you manage to solve the automatic detection.

 

My Opi ONE autodetection:

5.04 - sometime Pi 2 mini, sometime Pi+

5.05 - always Opi One

Link to post
Share on other sites

1. "Dumb" USB/2.5" IDE adapter that doesn't provide any S.M.A.R.T. data:

http://sprunge.us/MJWH

 

 

root@cubietruck:~# armbianmonitor -d
+ exec

Examining /dev/sda with GUID BABD6903-42CD-4172-BD3E-E00625A4C22B
Unable to query the disk through S.M.A.R.T.
Please investigate manually using smartctl


Debug output has been collected at the following URL: http://sprunge.us/MJWH
Please post the URL in the Armbian forum where you've been asked for. 

 

 

 

2. JMicron based USB/2.5" IDE + 3.5" IDE + SATA bridge, SATA drive attached

http://sprunge.us/KRLA

 

 

root@cubietruck:~# armbianmonitor -d
+ exec

Examining /dev/sda with GUID 711F8A2C-1FCB-496C-8A00-A0661AB38423
(accessible through S.M.A.R.T.)

Added disk "WDC WD10EADS-00M2B0"/"WDC WD10EADS-00M2B0" to /etc/hddtemp.db using S.M.A.R.T. attribute 194
based on the following available thermal values:
194 Temperature_Celsius     0x0022   122   093   000    Old_age   Always       -       25

hddtemp output: /dev/sda: WDC WD10EADS-00M2B0: S.M.A.R.T. not available

It seems we can not rely on hddtemp to query this disk. Please try smartctl instead

Disk not configured for monitoring. We were able to extract the following
information:
   GUID: 711F8A2C-1FCB-496C-8A00-A0661AB38423
   hddtemp: does not work. Please check with smartctl and adjust config accordingly
   CRC attribute: 199
   LCC Attribute: 193
Proposal for /etc/armbianmonitor/disks.conf:
711F8A2C-1FCB-496C-8A00-A0661AB38423:WDC WD10EADS-00M2B0::FIXME:199:193
You have to figure out how to query the disk for its thermal sensor.
Please check the output of "hddtemp --debug /dev/sda" and smartctl


Debug output has been collected at the following URL: http://sprunge.us/KRLA
Please post the URL in the Armbian forum where you've been asked for.

 

 

 

3. Same bridge, 2.5" IDE drive attached

http://sprunge.us/PaQU

 

 

root@cubietruck:~# armbianmonitor -d
+ exec

Examining /dev/sda with GUID D0702823-E3D0-4178-96D6-660AEF632767
(accessible through S.M.A.R.T.)

Added disk "ST9100824A"/"ST9100824A" to /etc/hddtemp.db using S.M.A.R.T. attribute 190
based on the following available thermal values:
190 Airflow_Temperature_Cel 0x0022   079   046   045    Old_age   Always       -       21 (Min/Max 21/21)
194 Temperature_Celsius     0x0022   021   054   000    Old_age   Always       -       21 (0 16 0 0 0)

hddtemp output: /dev/sda: ST9100824A: S.M.A.R.T. not available

It seems we can not rely on hddtemp to query this disk. Please try smartctl instead

Disk not configured for monitoring. We were able to extract the following
information:
   GUID: D0702823-E3D0-4178-96D6-660AEF632767
   hddtemp: does not work. Please check with smartctl and adjust config accordingly
   CRC attribute: 199
   LCC Attribute: 193
Proposal for /etc/armbianmonitor/disks.conf:
D0702823-E3D0-4178-96D6-660AEF632767:ST9100824A::FIXME:199:193
You have to figure out how to query the disk for its thermal sensor.
Please check the output of "hddtemp --debug /dev/sda" and smartctl


Debug output has been collected at the following URL: http://sprunge.us/PaQU
Please post the URL in the Armbian forum where you've been asked for. 

 

 

 

4. Same bridge, 2.5" SATA drive attached

http://sprunge.us/caSO

 

 

root@cubietruck:~# armbianmonitor -d
+ exec

Examining /dev/sda with GUID 0356A4FB-70C7-47D1-A329-2671AE3DFD15
(accessible through S.M.A.R.T.)

Added disk "WDC WD5000LPVX-00V0TT0"/"WDC WD5000LPVX-00V0TT0" to /etc/hddtemp.db using S.M.A.R.T. attribute 194
based on the following available thermal values:
194 Temperature_Celsius     0x0022   116   102   000    Old_age   Always       -       27

hddtemp output: /dev/sda: WDC WD5000LPVX-00V0TT0: S.M.A.R.T. not available

It seems we can not rely on hddtemp to query this disk. Please try smartctl instead

Disk not configured for monitoring. We were able to extract the following
information:
   GUID: 0356A4FB-70C7-47D1-A329-2671AE3DFD15
   hddtemp: does not work. Please check with smartctl and adjust config accordingly
   CRC attribute: 199
   LCC Attribute: 193
Proposal for /etc/armbianmonitor/disks.conf:
0356A4FB-70C7-47D1-A329-2671AE3DFD15:WDC WD5000LPVX-00V0TT0::FIXME:199:193
You have to figure out how to query the disk for its thermal sensor.
Please check the output of "hddtemp --debug /dev/sda" and smartctl


Debug output has been collected at the following URL: http://sprunge.us/caSO
Please post the URL in the Armbian forum where you've been asked for.

 

 

 

5. JMicron based USB 3.0/SATA bridge

http://sprunge.us/BIhH

 

 

root@cubietruck:~# armbianmonitor -d
+ exec

Examining /dev/sda with GUID 52D3C112-198B-4769-B830-E69406C166DC
(can be queried with "-d sat" through S.M.A.R.T.)

Added disk ""/"WDC WD40EFRX-68WT0N0" to /etc/hddtemp.db using S.M.A.R.T. attribute 194
based on the following available thermal values:
194 Temperature_Celsius     0x0022   125   108   000    Old_age   Always       -       27

hddtemp output: /dev/sda: WDC WD40EFRX-68WT0N0: S.M.A.R.T. not available

It seems we can not rely on hddtemp to query this disk. Please try smartctl instead

Disk not configured for monitoring. We were able to extract the following
information:
   GUID: 52D3C112-198B-4769-B830-E69406C166DC
   QueryMode: -d sat
   hddtemp: does not work. Please check with smartctl and adjust config accordingly
   CRC attribute: 199
   LCC Attribute: 193
Proposal for /etc/armbianmonitor/disks.conf:
52D3C112-198B-4769-B830-E69406C166DC::sat:FIXME:199:193
You have to figure out how to query the disk for its thermal sensor.
Please check the output of "hddtemp --debug /dev/sda" and smartctl


Debug output has been collected at the following URL: http://sprunge.us/BIhH
Please post the URL in the Armbian forum where you've been asked for.

 

 

Link to post
Share on other sites

I connect the ssd to my cubietruck using:

 

 

root@cubietruck:~# dmesg | grep -i ASM
[    4.129952] usb 2-1: Product: ASMT1051
[    4.129962] usb 2-1: Manufacturer: asmedia
[    7.187667] scsi 1:0:0:0: Direct-Access     ASMT     2115             0    PQ: 0 ANSI: 6

 

 

 

The output of armbianmonitor is:

 

 

root@cubietruck:~# armbianmonitor -d
+ exec

Examining /dev/sda with GUID 2A896D94-7E05-4651-9295-45619E10CAB9 
(accessible through S.M.A.R.T.)
Disk not configured for monitoring. We were able to extract the following 
information:
   GUID: 2A896D94-7E05-4651-9295-45619E10CAB9
   hddtemp: will work
   CRC attribute: 199
   LCC Attribute: 
If you want to monitor the disk please add to /etc/armbianmonitor/disks.conf:
2A896D94-7E05-4651-9295-45619E10CAB9:INTENSO SSD 128GB:::199:

Debug output has been collected at the following URL: http://sprunge.us/ChRJ
Please post the URL in the Armbian forum where you've been asked for.

 

 

 

Here is the link: http://sprunge.us/ChRJ

 

 

PS: Any tip on how to boot armbian on this ssd using mainline kernel would be welcomed. I have read tkaiser 's sunxi wiki page regarding ASMEDIA 1051 (here). I can boot with 3.4 kernel. How do I disabled ASM1051 blacklisting in armbian?

Link to post
Share on other sites

http://sprunge.us/cOfQ

+ exec

Examining /dev/sda with GUID F37ED465-C3CE-4DAE-8400-AD98D4643CDE
(accessible through S.M.A.R.T.)
Disk not configured for monitoring. We were able to extract the following
information:
   GUID: F37ED465-C3CE-4DAE-8400-AD98D4643CDE
   hddtemp: will work
   CRC attribute: 199
   LCC Attribute: 193
If you want to monitor the disk please add to /etc/armbianmonitor/disks.conf:
F37ED465-C3CE-4DAE-8400-AD98D4643CDE:WDC WD5000BMVW-11AJGS1:::199:193

Debug output has been collected at the following URL: http://sprunge.us/cOfQ
Please post the URL in the Armbian forum where you've been asked for.
Link to post
Share on other sites

Mainline u-boot 2016.03 was released, so hardcoded u-boot branch in configuration.sh and some u-boot patches should be obsolete.

 

True. And 2016.03 seems to be responsible for broken network with sun7i (tried it with bananapipro and network never came up, reverting to 2016.01 did the job)

Link to post
Share on other sites

I noticed broken network in 2016.03-rc* versions on cubietruck too when was testing tftp boot. Hopefully u-boot devs are aware of this and there will be a fix soon.

 

What about defining 'known to work' versions to use instead of accidentally becoming an early adopter on sunday evening and wasting hours with troubleshooting? Applies to both kernel and u-boot versions IMO.

 

BTW: After I realised that u-boot prevented NFS boot I ran into another strange problem. Unless I used FIXED_IMAGE_SIZE=3000 I always ended up with a corrupted ext4 fs in the image (took ages to realise that since I thought first it's related to FEL boot being work in progress, then made a suspicious SD card responsible when trying it the old way, then had the problem the display always went to sleep too early and woke up too late so the error messages were never shown...) Did you also encounter this?

Link to post
Share on other sites

What about defining 'known to work' versions to use instead of accidentally becoming an early adopter on sunday evening and wasting hours with troubleshooting? Applies to both kernel and u-boot versions IMO.

I thought about bisecting u-boot to see if this can be fixed with a simple patch.

 

BTW: After I realised that u-boot prevented NFS boot I ran into another strange problem. Unless I used FIXED_IMAGE_SIZE=3000 I always ended up with a corrupted ext4 fs in the image (took ages to realise that since I thought first it's related to FEL boot being work in progress, then made a suspicious SD card responsible when trying it the old way, then had the problem the display always went to sleep too early and woke up too late so the error messages were never shown...) Did you also encounter this?

No, but I don't remember when was the last time I tested images on SD. So are all images broken or only some of them for specific device/branch/release?

Link to post
Share on other sites

I thought about bisecting u-boot to see if this can be fixed with a simple patch.

➜  u-boot git:(c32a6fd) % git bisect bad
c32a6fd07b1839e4a45729587ebc8e1c55601a4d is the first bad commit
commit c32a6fd07b1839e4a45729587ebc8e1c55601a4d
Author: Simon Glass <sjg@chromium.org>
Date:   Sun Jan 17 14:51:56 2016 -0700

    net: Don't call board/cpu_eth_init() with driver model

    We should avoid weak functions with driver model. Existing boards that use
    driver model don't need them, so let's kill them off.

    Signed-off-by: Simon Glass <sjg@chromium.org>
    Reviewed-by: Bin Meng <bmeng.cn@gmail.com>
    Acked-by: Joe Hershberger <joe.hershberger@ni.com>

:040000 040000 4f22558a2179bb107edcf599ebd7efef17d72497 8e8c7a6b31c38c3f05737c6eddbccbfea6e52cc4 M      net

Edit: ...but Ethernet support code was refactored a lot, so it's more complicated than it initially looks.

Edit 2: Hm, didn't find this in first attempt.

Link to post
Share on other sites

I just tested it with sun8i, there the switch from 2016.03-rc2 to 2016.03 didn't break anything (already removed the '2016.03-rc2' kludge). So should we stay with 2016.01 for sun7i until this is resolved? More generally speaking maintaining variables that contain the 'known to work' u-boot/kernel version instead of updating the second a new version has been released might be better. Maybe introducing a new variable BLEEDING_EDGE and if set to yes get the branch the normal way (UBOOT_DEFAULT_BRANCH="v"$(git ls-remote ...) but otherwise stay at the version number defined in these new variables?

 

FEL booting works at least with sun8i, hadn't that much luck with A20 but gave up in the meantime (maybe I have to setup my new build host again). So at least the ext4 fs corruption is no general problem...

Link to post
Share on other sites

BTW: Mainline Ethernet driver patch at least applied properly:

 

[ o.k. ] ... OrangePI-15-h3-ethernet-wip.patch [ succeeded ]

 

Testing in a few minutes with 4.4.4

 

Edit: Doesn't work out (as nearly everything today):

 

 

 

ERROR (phandle_references): Reference to non-existent node or label "ahb_rst"

 

ERROR (phandle_references): Reference to non-existent node or label "ahb_rst"

 

ERROR: Input tree has errors, aborting (use -f to force output)

scripts/Makefile.lib:293: recipe for target 'arch/arm/boot/dts/sun8i-h3-orangepi-plus.dtb' failed

make[1]: *** [arch/arm/boot/dts/sun8i-h3-orangepi-plus.dtb] Error 2

make[1]: *** Waiting for unfinished jobs....

ERROR (phandle_references): Reference to non-existent node or label "ahb_rst"

 

ERROR (phandle_references): Reference to non-existent node or label "ahb_rst"

 

ERROR: Input tree has errors, aborting (use -f to force output)

scripts/Makefile.lib:293: recipe for target 'arch/arm/boot/dts/sun8i-h3-orangepi-pc.dtb' failed

make[1]: *** [arch/arm/boot/dts/sun8i-h3-orangepi-pc.dtb] Error 2

arch/arm/Makefile:338: recipe for target 'dtbs' failed

make: *** [dtbs] Error 2

  CHK     include/config/kernel.release

make KBUILD_SRC=

  CHK     include/config/kernel.release

  CHK     include/generated/uapi/linux/version.h

  CHK     include/generated/utsrelease.h

make[3]: 'include/generated/mach-types.h' is up to date.

  CHK     include/generated/bounds.h

  CHK     include/generated/timeconst.h

  CHK     include/generated/asm-offsets.h

  CALL    scripts/checksyscalls.sh

  CHK     include/generated/compile.h

  CHK     kernel/config_data.h

  Kernel: arch/arm/boot/Image is ready

  Kernel: arch/arm/boot/Image is ready

  Kernel: arch/arm/boot/zImage is ready

  DTC     arch/arm/boot/dts/sun8i-h3-orangepi-pc.dtb

ERROR (phandle_references): Reference to non-existent node or label "ahb_rst"

 

ERROR (phandle_references): Reference to non-existent node or label "ahb_rst"

 

ERROR: Input tree has errors, aborting (use -f to force output)

scripts/Makefile.lib:293: recipe for target 'arch/arm/boot/dts/sun8i-h3-orangepi-pc.dtb' failed

make[3]: *** [arch/arm/boot/dts/sun8i-h3-orangepi-pc.dtb] Error 2

arch/arm/Makefile:338: recipe for target 'dtbs' failed

make[2]: *** [dtbs] Error 2

scripts/package/Makefile:97: recipe for target 'bindeb-pkg' failed

make[1]: *** [bindeb-pkg] Error 2

Makefile:1231: recipe for target 'bindeb-pkg' failed

make: *** [bindeb-pkg] Error 2

mv: missing destination file operand after '/var/git/Armbian/output/debs/'

Try 'mv --help' for more information.

[ error ] ERROR in function compile_kernel [ common.sh:261 ]

[ error ] Failed moving kernel DEBs 

[ o.k. ] Process terminated 

 
It seems he still has not rebased the patches: http://moinejf.free.fr/opi2/  :(
 
Link to post
Share on other sites
Guest
This topic is now closed to further replies.