View unanswered posts | View active topics It is currently Thu Mar 21, 2019 12:07 pm



Reply to topic  [ 32 posts ]  Go to page Previous  1, 2, 3, 4  Next
 Utilite Value won't boot; just black screen 
Author Message

Joined: Sun Jul 13, 2014 6:16 pm
Posts: 23
Location: Queens, New York City
Post Re: Utilite Value won't boot; just black screen
Thanks for the reply, Chewi. I'm glad the last one is the most promising, since that's using the OS I want to use! Where can I get a newer version of the kernel for this architecture? Do I need to download the source and build one? If I can get the Utilite Linux running using a TTY shell, would I be able to build it there and copy it to the SD card for Arch?

I did post a question and introduce myself in the Arch Linux forum, so we'll see what happens, but you seem quite knowledgeable, and I already have your attention! :)

Cheers!


Fri Dec 29, 2017 5:18 pm
Profile

Joined: Tue Jan 07, 2014 12:07 am
Posts: 138
Location: Edinburgh, Scotland
Post Re: Utilite Value won't boot; just black screen
As I said, a vanilla kernel will work now, at least well enough to get it booted. If the userspace graphics drivers don't match then that can be dealt with afterwards. I see that you've had a reply from WarheadsSE so you should let them know about this.

It is useful to understand that back when that old kernel was released, kernel images could only be built for specific ARM boards. Now generic images can be built that will work with just about any supported ARM board, with the help of device trees.

In the meantime, you could perhaps try the generic Arch armv7 kernel image. I see it includes imx6q-utilite-pro.dtb, which is needed to make the image work on this particular board. Since you're booting the SSD, I'm not sure how you'll get files onto there, short of using a working SD card.

The real bad news is that this kernel is not provided in uImage format. Your U-Boot is super ancient and probably doesn't accept the zImage + DTB approach that is preferred these days. Again, you'll need a working system but I highly recommend that you update U-Boot somehow. Beware though, this is device-bricking territory.

Once you have things working, the system could be put back onto SD card if done properly but I'm not sure why you'd want to, the SSD is way faster and more reliable. You can also boot off a USB-connected external drive, this is what I currently do.

Sorry if this all seems very tedious. Linux on obscure devices isn't for the faint-hearted but it can still be very rewarding. My Utilite is now responsible for a variety of things.


Fri Dec 29, 2017 9:12 pm
Profile

Joined: Sun Jul 13, 2014 6:16 pm
Posts: 23
Location: Queens, New York City
Post Re: Utilite Value won't boot; just black screen
I just ran an ethernet cable for a different device to the same location as my Utilite, so I'll see if I can get the a Utilite Linux up and running and update U-Boot. I'd changed the kernel environment variable without checking what it was first. Do you know what I should restore it to or if I have to?


Fri Dec 29, 2017 11:18 pm
Profile

Joined: Tue Jan 07, 2014 12:07 am
Posts: 138
Location: Edinburgh, Scotland
Post Re: Utilite Value won't boot; just black screen
I'm not able to reboot my Utilite to check right now but I gather that "env default" can be used to reset variables back to their defaults. "env default -a" will reset everything and you can check the result before saving. Be careful, there may be some unique values currently in there like MAC addresses. Try "help env" for more information.


Fri Dec 29, 2017 11:26 pm
Profile

Joined: Sun Jul 13, 2014 6:16 pm
Posts: 23
Location: Queens, New York City
Post Re: Utilite Value won't boot; just black screen
Good news! I got Utilite Linux booting again! I did have to reset the value of kernel to uimage-cm-fx6. The ethernet connection works, and I was able to wget a random HTML page. More updates to come tomorrow.


Sat Dec 30, 2017 6:44 am
Profile

Joined: Sun Jul 13, 2014 6:16 pm
Posts: 23
Location: Queens, New York City
Post Re: Utilite Value won't boot; just black screen
So, good news and bad news. I followed the instructions to update U-Boot, and that seems to have worked. However, when I try to boot to Utilite Linux, one of two things happens. Either I get a message saying, "Trying to boot from MMC" that never finishes, or if I remove the SD card, power up the Utilite, insert the SD card, and type boot, I get the Ubuntu login prompt, but cannot type anything over TTY. (Sometimes, the OS does boot on powering up, but I still can't type anything over TTY.)

Code:
CM-FX6 # boot
switch to partitions #0, OK
mmc2 is current device
reading boot.scr
** Unable to read file boot.scr **
reading uImage-cm-fx6
4348356 bytes read in 218 ms (19 MiB/s)
Booting from mmc ...
## Booting kernel from Legacy Image at 10800000 ...
   Image Name:   Linux-3.0.35-cm-fx6-6.3
   Image Type:   ARM Linux Kernel Image (uncompressed)
   Data Size:    4348292 Bytes = 4.1 MiB
   Load Address: 10008000
   Entry Point:  10008000
   Verifying Checksum ... OK
   Loading Kernel Image ... OK

Starting kernel ...

Linux version 3.0.35-cm-fx6-6.3 (val@devel) (gcc version 4.5.2 (Sourcery G++ Lite 2011.03-41) ) #82 SMP Wed Dec 17 10:01:46 IST 2014
CPU: ARMv7 Processor [412fc09a] revision 10 (ARMv7), cr=10c5387d
CPU: VIPT nonaliasing data cache, VIPT aliasing instruction cache
Machine: Compulab CM-FX6
Memory policy: ECC disabled, Data cache writealloc
CPU identified as i.MX6DL/SOLO, silicon rev 1.1
PERCPU: Embedded 7 pages/cpu @cbc05000 s5504 r8192 d14976 u32768
Built 1 zonelists in Zone order, mobility grouping on.  Total pages: 113664
Kernel command line: console=ttymxc3,115200 root=/dev/mmcblk0p2 rw rootwait
PID hash table entries: 2048 (order: 1, 8192 bytes)
Dentry cache hash table entries: 65536 (order: 6, 262144 bytes)
Inode-cache hash table entries: 32768 (order: 5, 131072 bytes)
Memory: 448MB = 448MB total
Memory: 445652k/445652k available, 78636k reserved, 0K highmem
Virtual kernel memory layout:
    vector  : 0xffff0000 - 0xffff1000   (   4 kB)
    fixmap  : 0xfff00000 - 0xfffe0000   ( 896 kB)
    DMA     : 0xf4600000 - 0xffe00000   ( 184 MB)
    vmalloc : 0xe0800000 - 0xf2000000   ( 280 MB)
    lowmem  : 0xc0000000 - 0xe0000000   ( 512 MB)
    pkmap   : 0xbfe00000 - 0xc0000000   (   2 MB)
    modules : 0xbf000000 - 0xbfe00000   (  14 MB)
      .init : 0xc0008000 - 0xc0048000   ( 256 kB)
      .text : 0xc0048000 - 0xc07b8b60   (7619 kB)
      .data : 0xc07ba000 - 0xc0810120   ( 345 kB)
       .bss : 0xc0810144 - 0xc085a300   ( 297 kB)
Hierarchical RCU implementation.
   RCU dyntick-idle grace-period acceleration is enabled.
NR_IRQS:624
MXC GPIO hardware
sched_clock: 32 bits at 3000kHz, resolution 333ns, wraps every 1431655ms
Set periph_clk's parent to pll2_pfd_400M!
arm_max_freq=1GHz
MXC_Early serial console at MMIO 0x21f0000 (options '115200')
bootconsole [ttymxc3] enabled
Console: colour dummy device 80x30
Calibrating delay loop... 1581.05 BogoMIPS (lpj=7905280)
pid_max: default: 32768 minimum: 301
Security Framework initialized
Mount-cache hash table entries: 512
CPU: Testing write buffer coherency: ok
hw perfevents: enabled with ARMv7 Cortex-A9 PMU driver, 7 counters available
Brought up 1 CPUs
SMP: Total of 1 processors activated (1581.05 BogoMIPS).
devtmpfs: initialized
print_constraints: dummy:
NET: Registered protocol family 16
print_constraints: vddpu: 725 <--> 1300 mV at 1150 mV fast normal
print_constraints: vddcore: 725 <--> 1300 mV at 1150 mV fast normal
print_constraints: vddsoc: 725 <--> 1300 mV at 1175 mV fast normal
print_constraints: vdd2p5: 2000 <--> 2775 mV at 2400 mV fast normal
print_constraints: vdd1p1: 800 <--> 1400 mV at 1100 mV fast normal
print_constraints: vdd3p0: 2625 <--> 3400 mV at 3000 mV fast normal
cpu regulator mode:ldo_enable
hw-breakpoint: found 6 breakpoint and 1 watchpoint registers.
hw-breakpoint: 1 breakpoint(s) reserved for watchpoint single-step.
hw-breakpoint: maximum watchpoint size is 4 bytes.
L310 cache controller enabled
l2x0: 16 ways, CACHE_ID 0x410000c8, AUX_CTRL 0x32450000, Cache size: 524288 B
bio: create slab <bio-0> at 0
mxs-dma mxs-dma-apbh: initialized
print_constraints: ads7846_vcc: 3300 mV
print_constraints: vmmc: 3300 mV
vgaarb: loaded
SCSI subsystem initialized
spi_imx imx6q-ecspi.0: probed
spi_imx imx6q-ecspi.1: probed
usbcore: registered new interface driver usbfs
usbcore: registered new interface driver hub
usbcore: registered new device driver usb
Freescale USB OTG Driver loaded, $Revision: 1.55 $
imx-ipuv3 imx-ipuv3.0: IPU DMFC NORMAL mode: 1(0~1), 5B(4,5), 5F(6,7)
Advanced Linux Sound Architecture Driver Version 1.0.24.
Bluetooth: Core ver 2.16
NET: Registered protocol family 31
Bluetooth: HCI device and connection manager initialized
Bluetooth: HCI socket layer initialized
Bluetooth: L2CAP socket layer initialized
Bluetooth: SCO socket layer initialized
cfg80211: Calling CRDA to update world regulatory domain
Switching to clocksource mxc_timer1
NET: Registered protocol family 2
IP route cache hash table entries: 4096 (order: 2, 16384 bytes)
TCP established hash table entries: 16384 (order: 5, 131072 bytes)
TCP bind hash table entries: 16384 (order: 5, 131072 bytes)
TCP: Hash tables configured (established 16384 bind 16384)
TCP reno registered
UDP hash table entries: 256 (order: 1, 8192 bytes)
UDP-Lite hash table entries: 256 (order: 1, 8192 bytes)
NET: Registered protocol family 1
RPC: Registered named UNIX socket transport module.
RPC: Registered udp transport module.
RPC: Registered tcp transport module.
RPC: Registered tcp NFSv4.1 backchannel transport module.
_regulator_get: etb supply vcore not found, using dummy regulator
_regulator_get: etm.0 supply vcore not found, using dummy regulator
Static Power Management for Freescale i.MX6
wait mode is enabled for i.MX6
cpaddr = e0820000 suspend_iram_base=e08ac000
PM driver module loaded
IMX usb wakeup probe
add wake up source irq 75
IMX usb wakeup probe
i.MXC CPU frequency driver
JFFS2 version 2.2. (NAND) © 2001-2006 Red Hat, Inc.
msgmni has been set to 870
Block layer SCSI generic (bsg) driver version 0.4 loaded (major 252)
io scheduler noop registered
io scheduler deadline registered
io scheduler cfq registered (default)
imx-sdma imx-sdma: loaded firmware 1.1
imx-sdma imx-sdma: initialized
Serial: IMX driver
brd: module loaded
loop: module loaded
at24 2-0050: 256 byte at24 EEPROM, writable, 16 bytes/write
m25p80 spi0.0: found sst25vf016b, expected m25p80
m25p80 spi0.0: sst25vf016b (2048 Kbytes)
Creating 3 MTD partitions on "spi_flash":
0x000000000000-0x0000000c0000 : "uboot"
0x0000000c0000-0x000000100000 : "uboot environment"
0x000000100000-0x000000200000 : "reserved"
No NAND device found.
Chip scan failed
GPMI NAND driver registered. (IMX)
vcan: Virtual CAN interface driver
CAN device driver interface
flexcan netdevice driver
flexcan imx6q-flexcan.0: device registered (reg_base=e08f0000, irq=142)
FEC Ethernet Driver
fec_enet_mii_bus: probed
ehci_hcd: USB 2.0 'Enhanced' Host Controller (EHCI) Driver
fsl-ehci fsl-ehci.0: Freescale On-Chip EHCI Host Controller
fsl-ehci fsl-ehci.0: new USB bus registered, assigned bus number 1
fsl-ehci fsl-ehci.0: irq 75, io base 0x02184000
fsl-ehci fsl-ehci.0: USB 2.0 started, EHCI 1.00
hub 1-0:1.0: USB hub found
hub 1-0:1.0: 1 port detected
add wake up source irq 72
fsl-ehci fsl-ehci.1: Freescale On-Chip EHCI Host Controller
fsl-ehci fsl-ehci.1: new USB bus registered, assigned bus number 2
fsl-ehci fsl-ehci.1: irq 72, io base 0x02184200
fsl-ehci fsl-ehci.1: USB 2.0 started, EHCI 1.00
hub 2-0:1.0: USB hub found
hub 2-0:1.0: 1 port detected
usbcore: registered new interface driver cdc_wdm
Initializing USB Mass Storage driver...
usbcore: registered new interface driver usb-storage
USB Mass Storage support registered.
ARC USBOTG Device Controller driver (1 August 2005)
mousedev: PS/2 mouse device common for all mice
=======snvs_pwrkey_probe() lp_cr 0x20
=======snvs_pwrkey_probe() lp_cr 0x20
input: snvs_power_key as /devices/virtual/input/input0
i.MX6 powerkey probe
i2c-core: driver [isl29023] using legacy suspend method
i2c-core: driver [isl29023] using legacy resume method
i2c /dev entries driver
at24 3-0050: 256 byte at24 EEPROM, writable, 16 bytes/write
CM-FX6: Detected SB-FX6m (Utilite) base board
rtc-em3027 3-0056: rtc core: registered rtc-em3027 as rtc0
iMX6 PCIe PCIe RC mode imx_pcie_pltfm_probe entering.
usb 2-1: new high speed USB device number 2 using fsl-ehci
hub 2-1:1.0: USB hub found
hub 2-1:1.0: 4 ports detected
PCIE: imx_pcie_pltfm_probe start link up.
link up failed, DB_R0:0x00f9a600, DB_R1:0x08200000!
IMX PCIe port: link down!
imx-uart.0: ttymxc0 at MMIO 0x2020000 (irq = 58) is a IMX
imx-uart.3: ttymxc3 at MMIO 0x21f0000 (irq = 61) is a IMX
console [ttymxc3] enabled, bootconsole disabled
console [ttymxc3] enabled, bootconsole disabled
imx-uart.1: ttymxc1 at MMIO 0x21e8000 (irq = 59) is a IMX
imx-uart.4: ttymxc4 at MMIO 0x21f4000 (irq = 62) is a IMX
i2c i2c-0: Added multiplexed i2c bus 3
i2c i2c-0: Added multiplexed i2c bus 4
gpio-i2cmux gpio-i2cmux: 2 port mux on imx-i2c adapter
Linux media interface: v0.10
lirc_dev: IR Remote Control driver registered, major 250
IR NEC protocol handler initialized
IR RC5(x) protocol handler initialized
IR RC6 protocol handler initialized
IR JVC protocol handler initialized
IR Sony protocol handler initialized
IR RC5 (streamzap) protocol handler initialized
IR LIRC bridge handler initialized
Linux video capture interface: v2.00
imx2-wdt imx2-wdt.0: IMX2+ Watchdog Timer enabled. timeout=60s (nowayout=1)
sdhci: Secure Digital Host Controller Interface driver
sdhci: Copyright(c) Pierre Ossman
mmc0: SDHCI controller on platform [sdhci-esdhc-imx.0] using ADMA
mmc1: SDHCI controller on platform [sdhci-esdhc-imx.2] using ADMA
VPU initialized
mxc_asrc registered
Thermal calibration data is 0x5b85325f
Thermal sensor with ratio = 191
Anatop Thermal registered as thermal_zone0
anatop_thermal_probe: default cooling device is cpufreq!
caam caam.0: device ID = 0x0a16010000000100
caam caam.0: job rings = 2, qi = 0
caam caam.0: authenc-hmac-md5-cbc-aes-caam
caam caam.0: authenc-hmac-sha1-cbc-aes-caam
caam caam.0: authenc-hmac-sha224-cbc-aes-caam
caam caam.0: authenc-hmac-sha256-cbc-aes-caam
caam caam.0: authenc-hmac-md5-cbc-des3_ede-caam
caam caam.0: authenc-hmac-sha1-cbc-des3_ede-caam
caam caam.0: authenc-hmac-sha224-cbc-des3_ede-caam
caam caam.0: authenc-hmac-sha256-cbc-des3_ede-caam
caam caam.0: authenc-hmac-md5-cbc-des-caam
caam caam.0: authenc-hmac-sha1-cbc-des-caam
caam caam.0: authenc-hmac-sha224-cbc-des-caam
caam caam.0: authenc-hmac-sha256-cbc-des-caam
caam caam.0: cbc-aes-caam
caam caam.0: ecb-aes-caam
caam caam.0: cbc-3des-caam
caam caam.0: cbc-des-caam
platform caam_jr.0: registering rng-caam
usbcore: registered new interface driver usbhid
usbhid: USB HID core driver
mxc_spdif mxc_spdif.0: MXC SPDIF Audio
_regulator_get: 2-001a supply AVDD not found, using dummy regulator
_regulator_get: 2-001a supply HPVDD not found, using dummy regulator
_regulator_get: 2-001a supply DCVDD not found, using dummy regulator
_regulator_get: 2-001a supply DBVDD not found, using dummy regulator
imx_wm8731_init: success
asoc: wm8731-hifi <-> imx-ssi.1 mapping ok
asoc: mxc-spdif <-> imx-spdif-dai.0 mapping ok
ALSA device list:
  #0: wm8731-audio
  #1: imx-spdif
NET: Registered protocol family 26
nf_conntrack version 0.5.0 (6963 buckets, 27852 max)
IPVS: Registered protocols (TCP, UDP, SCTP, AH, ESP)
IPVS: Connection hash table configured (size=4096, memory=32Kbytes)
IPVS: Creating netns size=1176 id=0
IPVS: ipvs loaded.
IPVS: [rr] scheduler registered.
IPVS: [wrr] scheduler registered.
IPVS: [lc] scheduler registered.
IPVS: [wlc] scheduler registered.
IPVS: [lblc] scheduler registered.
IPVS: [lblcr] scheduler registered.
IPVS: [dh] scheduler registered.
IPVS: [sh] scheduler registered.
IPVS: [sed] scheduler registered.
IPVS: [nq] scheduler registered.
TCP cubic registered
NET: Registered protocol family 10
Mobile IPv6
IPv6 over IPv4 tunneling driver
NET: Registered protocol family 17
Bridge firewalling registered
can: controller area network core (rev 20090105 abi 8)
NET: Registered protocol family 29
can: raw protocol (rev 20090105)
can: broadcast manager protocol (rev 20090105 t)
Bluetooth: RFCOMM TTY layer initialized
Bluetooth: RFCOMM socket layer initialized
Bluetooth: RFCOMM ver 1.11
Bluetooth: BNEP (Ethernet Emulation) ver 1.3
Bluetooth: BNEP filters: protocol multicast
Bluetooth: HIDP (Human Interface Emulation) ver 1.2
lib80211: common routines for IEEE802.11 drivers
HDMI CEC initialized
mxc_vdoa mxc_vdoa: i.MX Video Data Order Adapter(VDOA) driver probed
mxc_sdc_fb mxc_sdc_fb.0: register mxc display driver hdmi
mxc_hdmi mxc_hdmi: Detected HDMI controller 0x13:0x1a:0xa0:0xc1
imx-ipuv3 imx-ipuv3.0: IPU DMFC DP HIGH RESOLUTION: 1(0,1), 5B(2~5), 5F(6,7)
mmc1: host does not support reading read-only switch. assuming write-enable.
mmc1: new high speed SDHC card at address 0007
mmcblk0: mmc1:0007 SD04G 3.67 GiB
mmcblk0: p1 p2
Console: switching to colour frame buffer device 240x67
mxc_sdc_fb mxc_sdc_fb.1: register mxc display driver dvi
_regulator_get: get() with no identifier
mxc_hdmi_soc mxc_hdmi_soc.0: MXC HDMI Audio
asoc: mxc-hdmi-soc <-> imx-hdmi-soc-dai.0 mapping ok
VFP support v0.3: implementor 41 architecture 3 part 30 variant 9 rev 4
Registering SWP/SWPB emulation handler
Bus freq driver module loaded
Bus freq driver Enabled
mxc_dvfs_core_probe
DVFS driver module loaded
regulator_init_complete: ads7846_vcc: incomplete constraints, leaving on
rtc-em3027 3-0056: setting system clock to 2017-12-30 16:31:38 UTC (1514651498)
EXT3-fs (mmcblk0p2): error: couldn't mount because of unsupported optional features (240)
EXT2-fs (mmcblk0p2): error: couldn't mount because of unsupported optional features (244)
EXT4-fs (mmcblk0p2): recovery complete
EXT4-fs (mmcblk0p2): mounted filesystem with ordered data mode. Opts: (null)
VFS: Mounted root (ext4 filesystem) on device 179:2.
devtmpfs: mounted
Freeing init memory: 256K

Ubuntu 12.04.3 LTS (Compulab: utilite-2) utilite-desktop ttymxc3

utilite-desktop login:


Sat Dec 30, 2017 4:36 pm
Profile

Joined: Tue Jan 07, 2014 12:07 am
Posts: 138
Location: Edinburgh, Scotland
Post Re: Utilite Value won't boot; just black screen
I've never tried booting from SD card. In fact, I avoid plugging SD cards into mine at all as the card never seems to actually find its way into the slot.

That outcome is quite odd. If you didn't see the login prompt at all then it would suggest that agetty was not configured for the serial console. I don't know what would cause it to only work one way.

Can you put Arch onto the SD card at this point? Booting with a zImage and DTB is slightly different to a uImage. I don't know whether Arch normally uses an initramfs but you probably won't need one in any case. You need to load both the zImage and DTB into memory and then run "bootz foo - bar" where foo and bar are the memory locations. I use 0x10800000 for the kernel and 0x15000000 for the DTB.


Sat Dec 30, 2017 6:37 pm
Profile

Joined: Sun Jul 13, 2014 6:16 pm
Posts: 23
Location: Queens, New York City
Post Re: Utilite Value won't boot; just black screen
Hey, Chewi. Thanks for all of the help so far. There are a whole bunch of environment variables with the new U-Boot that were overriding my setting kernel to uimage, so I modified setboottypem from:
Code:
setboottypem=setenv kernel uImage-cm-fx6;setenv doboot bootm ${loadaddr};setenv doloadfdt false;

to:
Code:
setboottypem=setenv kernel uimage;setenv doboot bootm ${loadaddr};setenv doloadfdt false;


This gets me up to FATAL: kernel too old.

What do I do with the .pkg.tar.gz file? Is it a package for a package manager?

By the way, I also have the same problem with the SD card slot. I've gotten pretty good at getting the cards in and out. I actually use a toothpick to push the card into the spring-loaded mechanism!


Sat Dec 30, 2017 9:07 pm
Profile

Joined: Tue Jan 07, 2014 12:07 am
Posts: 138
Location: Edinburgh, Scotland
Post Re: Utilite Value won't boot; just black screen
The link I provided above has a .pkg.tar.xz file rather than.pkg.tar.gz but either way, you can just extract these with tar.

Code:
tar Jxf linux-armv7-4.14.10-1-armv7h.pkg.tar.xz


If you have Arch on an SD card then you could just extract the whole archive and that will put everything in place, including the kernel modules. Then you need to load zImage and imx6q-utilite-pro.dtb into memory with U-Boot. The bootm command you pasted above won't work here. It needs to be bootz in the form I mentioned. I would paste my own U-Boot environment but it's heavily customised.


Sat Dec 30, 2017 10:42 pm
Profile

Joined: Tue Jan 07, 2014 12:07 am
Posts: 138
Location: Edinburgh, Scotland
Post Re: Utilite Value won't boot; just black screen
Actually I wondered where that "doloadfdt" variable came from and it seems that the newer default environment already has handling for device trees and bootz. I guess I never saw the new default. By the look of it, if you provide zImage-cm-fx6 and cm-fx6.dtb instead of uImage-cm-fx6 then it will just work.


Sat Dec 30, 2017 10:52 pm
Profile
Display posts from previous:  Sort by  
Reply to topic   [ 32 posts ]  Go to page Previous  1, 2, 3, 4  Next

Who is online

Users browsing this forum: No registered users and 1 guest


You cannot post new topics in this forum
You cannot reply to topics in this forum
You cannot edit your posts in this forum
You cannot delete your posts in this forum
You cannot post attachments in this forum

Search for:
Jump to:  
Powered by phpBB © 2000, 2002, 2005, 2007 phpBB Group.
Designed by STSoftware for PTF.