Kurobox NAS-Central Forums

Welcome to the Kuro Community
It is currently Fri Jul 20, 2018 8:28 am

All times are UTC-06:00




Forum locked  This topic is locked, you cannot edit posts or make further replies.  [ 97 posts ]  Go to page 1 2 3 4 57 Next
Author Message
PostPosted: Wed Jan 03, 2007 6:29 pm 
Offline

Joined: Sat Jul 15, 2006 8:49 am
Posts: 219
Location: Virginia
I just wanted to thank Infinoid for his work on a new wiki page documenting the use of the standard 2.6 kernel on the kurobox.

Thanks! :D

russK


Top
   
 Post subject:
PostPosted: Wed Jan 03, 2007 7:13 pm 
Offline

Joined: Thu Jun 23, 2005 12:24 pm
Posts: 287
I was going to make the jump as soon as I can find a few free hours. Hopefully this weekend. Lets not all start bricking our kuros now, please.


Top
   
 Post subject:
PostPosted: Thu Jan 04, 2007 6:50 am 
Offline

Joined: Fri Oct 29, 2004 6:00 am
Posts: 91
Location: UK
Yes, good work - I spotted the wiki page yesterday.

My Kuro HG-WR just arrived (literally a few minutes ago) and I planned to go down the U-Boot / 2.6.x kernel / Gentoo route.

Dave Taylor wrote:
Lets not all start bricking our kuros now, please.

Is the new 2.6.20-rcX kernel (along with the necessary fdt-compatible updated U-Boot) too recent for mere mortals to be using?

I don't see much point in flashing the linuxnotincluded U-Boot so I can use a 2.6.19 kernel, then flashing again for 2.6.20 soon after. I would rather flash just once if Infinoid's method is sound.

Matthew


Top
   
 Post subject:
PostPosted: Thu Jan 04, 2007 8:14 am 
Offline

Joined: Thu Jun 23, 2005 12:24 pm
Posts: 287
obviously Infinoid has made this work. There was a wave of bricks (mine included) when U-Boot first came out. I suspect most were caused by user error. There was at least one case where a user followed a misinstruction in the wiki page and made a brick.

I would suggest waiting until a user or two who have JTAG access install this to make sure the instructions are complete and nothing has been overlooked. I suspect russK, myself (I happen to need a new kernel and headers so I can build a module for my wireless G dongle, sound card, and WinTV-PVR2), and a few others will test it out very soon. If we brick our kuros we have the equipment to repair them.


Top
   
 Post subject:
PostPosted: Thu Jan 04, 2007 8:29 am 
Offline

Joined: Fri Oct 29, 2004 6:00 am
Posts: 91
Location: UK
Dave Taylor wrote:
obviously Infinoid has made this work. There was a wave of bricks (mine included) when U-Boot first came out. I suspect most were caused by user error. There was at least one case where a user followed a misinstruction in the wiki page and made a brick.

I would suggest waiting until a user or two who have JTAG access install this to make sure the instructions are complete and nothing has been overlooked. I suspect russK, myself (I happen to need a new kernel and headers so I can build a module for my wireless G dongle, sound card, and WinTV-PVR2), and a few others will test it out very soon. If we brick our kuros we have the equipment to repair them.


You're right, of course! (I'm just too impatient)

I think I'll wait until someone has uploaded a fdt-compliant U-Boot to the downloads area! ;-)


Top
   
 Post subject:
PostPosted: Fri Jan 05, 2007 9:01 pm 
Offline

Joined: Thu Jun 23, 2005 12:24 pm
Posts: 287
lyakh built and sent the files for my kuro standard and I sintalled them.

This won't brick your Kuro, but it doesn't work yet. There is a problem with the serial port mapping. We are working on this and will make a post as soon as we get it to work on the KURO STANDARD.

I'll eventually rebuild u-boot with my personal defaults. In the mean time, here is a copy of the console:

Code:
netconsole: local IP 192.168.1.7
netconsole: interface eth0
netconsole: remote port 6666
netconsole: remote IP 192.168.1.1
netconsole: remote ethernet address 00:50:bf:a4:59:71
mpic: Setting up MPIC " EPIC     " version 1.2 at 80040000, max 1 CPUs
mpic: ISU size: 4, shift: 2, mask: 3
mpic: Initializing for 12 sources
PID hash table entries: 256 (order: 8, 1024 bytes)
time_init: decrementer frequency = 24.391680 MHz
time_init: processor frequency   = 196.608000 MHz
Console: colour dummy device 80x25
Dentry cache hash table entries: 8192 (order: 3, 32768 bytes)
Inode-cache hash table entries: 4096 (order: 2, 16384 bytes)
Memory: 61632k/65536k available (2964k kernel code, 3844k reserved, 120k data, 1
01k bss, 140k init)
Calibrating delay loop... 48.74 BogoMIPS (lpj=243712)
Mount-cache hash table entries: 512
NET: Registered protocol family 16
PCI: Probing PCI hardware
PCI: Cannot allocate resource region 1 of device 0000:00:00.0
PCI: Cannot allocate resource region 5 of device 0000:00:0c.0
SCSI subsystem initialized
libata version 2.00 loaded.
usbcore: registered new interface driver usbfs
usbcore: registered new interface driver hub
usbcore: registered new device driver usb
NET: Registered protocol family 2
IP route cache hash table entries: 512 (order: -1, 2048 bytes)
TCP established hash table entries: 2048 (order: 1, 8192 bytes)
TCP bind hash table entries: 1024 (order: 0, 4096 bytes)
TCP: Hash tables configured (established 2048 bind 1024)
TCP reno registered
io scheduler noop registered
io scheduler anticipatory registered (default)
io scheduler deadline registered
io scheduler cfq registered
Serial: 8250/16550 driver $Revision: 1.90 $ 4 ports, IRQ sharing disabled
serial8250.0: ttyS0 at MMIO 0x80004500 (irq = 16) is a 16550A
serial8250.0: ttyS1 at MMIO 0x80004600 (irq = 17) is a 16550A
RAMDISK driver initialized: 2 RAM disks of 8192K size 1024 blocksize
loop: loaded (max 8 devices)
Linux Tulip driver version 1.1.14 (May 11, 2002)
tulip0:  MII transceiver #1 config 1000 status 786d advertising 05e1.
eth0: ADMtek Comet rev 17 at MMIO 0xbffffc00, 00:07:40:FB:54:D4, IRQ 19.
netconsole: device eth0 not up yet, forcing it
netconsole: carrier detect appears untrustworthy, waiting 4 seconds
0000:00:0b.0: tulip_stop_rxtx() failed
eth0: Setting full-duplex based on MII#1 link partner capability of 45e1.
netconsole: network logging started
pata_sil680 0000:00:0c.0: version 0.4.1
sil680: BA5_EN = 1 clock = 00
sil680: BA5_EN = 1 clock = 10
sil680: 133MHz clock.
ata1: PATA max UDMA/133 cmd 0xBFFED0 ctl 0xBFFEDA bmdma 0xBFFEF0 irq 20
ata2: PATA max UDMA/133 cmd 0xBFFEE0 ctl 0xBFFEEA bmdma 0xBFFEF8 irq 20
scsi0 : pata_sil680
ata1.00: ATA-7, max UDMA/100, 586072368 sectors: LBA48
ata1.00: ata1: dev 0 multi count 16
ata1.00: configured for UDMA/100
scsi1 : pata_sil680
ATA: abnormal status 0x7F on port 0xBFFEE7
scsi 0:0:0:0: Direct-Access     ATA      ST3300831A       3.03 PQ: 0 ANSI: 5
SCSI device sda: 586072368 512-byte hdwr sectors (300069 MB)
sda: Write Protect is off
sda: Mode Sense: 00 3a 00 00
SCSI device sda: write cache: enabled, read cache: enabled, doesn't support DPO
or FUA
SCSI device sda: 586072368 512-byte hdwr sectors (300069 MB)
sda: Write Protect is off
sda: Mode Sense: 00 3a 00 00
SCSI device sda: write cache: enabled, read cache: enabled, doesn't support DPO
or FUA
 sda: sda1 sda2 sda3
sd 0:0:0:0: Attached scsi disk sda
sd 0:0:0:0: Attached scsi generic sg0 type 0
physmap platform flash device: 00400000 at ffc00000
physmap-flash.0: Found 1 x16 devices at 0x0 in 8-bit bank
 Amd/Fujitsu Extended Query Table at 0x0040
physmap-flash.0: Swapping erase regions for broken CFI table.
number of CFI chips: 1
cfi_cmdset_0002: Disabling erase-suspend-program due to code brokenness.
cmdlinepart partition parsing not available
RedBoot partition parsing not available
Using physmap partition information
Creating 6 MTD partitions on "physmap-flash.0":
0x00000000-0x00300000 : "mtd_firmimg"
0x00300000-0x00370000 : "mtd_bootcode"
0x00370000-0x00380000 : "mtd_status"
0x00380000-0x00400000 : "mtd_conf"
0x00000000-0x00400000 : "mtd_allflash"
0x00310000-0x00400000 : "mtd_data"
usbmon: debugfs is not available
ehci_hcd 0000:00:0e.2: EHCI Host Controller
ehci_hcd 0000:00:0e.2: new USB bus registered, assigned bus number 1
ehci_hcd 0000:00:0e.2: irq 21, io mem 0xbfffcf00
ehci_hcd 0000:00:0e.2: USB 2.0 started, EHCI 1.00, driver 10 Dec 2004
usb usb1: configuration #1 chosen from 1 choice
hub 1-0:1.0: USB hub found
hub 1-0:1.0: 5 ports detected
ohci_hcd: 2006 August 04 USB 1.1 'Open' Host Controller (OHCI) Driver (PCI)
ohci_hcd 0000:00:0e.0: OHCI Host Controller
ohci_hcd 0000:00:0e.0: new USB bus registered, assigned bus number 2
ohci_hcd 0000:00:0e.0: irq 21, io mem 0xbfffe000
usb usb2: configuration #1 chosen from 1 choice
hub 2-0:1.0: USB hub found
hub 2-0:1.0: 3 ports detected
ohci_hcd 0000:00:0e.1: OHCI Host Controller
ohci_hcd 0000:00:0e.1: new USB bus registered, assigned bus number 3
ohci_hcd 0000:00:0e.1: irq 21, io mem 0xbfffd000
usb 1-2: new high speed USB device using ehci_hcd and address 2
usb usb3: configuration #1 chosen from 1 choice
hub 3-0:1.0: USB hub found
hub 3-0:1.0: 2 ports detected
usb 1-2: configuration #1 chosen from 1 choice
hub 1-2:1.0: USB hub found
hub 1-2:1.0: 4 ports detected
usb 1-2.1: new full speed USB device using ehci_hcd and address 3
usb 1-2.1: configuration #1 chosen from 1 choice
usb 1-2.2: new high speed USB device using ehci_hcd and address 4
usb 1-2.2: configuration #1 chosen from 1 choice
usbcore: registered new interface driver usbserial
drivers/usb/serial/usb-serial.c: USB Serial Driver core
drivers/usb/serial/usb-serial.c: USB Serial support registered for FTDI USB Seri
al Device
usbcore: registered new interface driver ftdi_sio
drivers/usb/serial/ftdi_sio.c: v1.4.3:USB FTDI Serial Converters Driver
mice: PS/2 mouse device common for all mice
i2c /dev entries driver
rs5c372 0-0032: chip found, driver version 0.3
rs5c372 0-0032: rtc core: registered rs5c372 as rtc0
TCP cubic registered
NET: Registered protocol family 1
NET: Registered protocol family 17
rs5c372 0-0032: setting the system clock to 2007-01-06 02:48:15 (1168051695)
linkstation: disarming the AVR watchdog:
kjournald starting.  Commit interval 5 seconds
EXT3-fs: mounted filesystem with ordered data mode.
VFS: Mounted root (ext3 filesystem) readonly.
Freeing unused kernel memory: 140k init
INIT: version 2.86 booting

Gentoo Linux; http://www.gentoo.org/
 Copyright 1999-2006 Gentoo Foundation; Distributed under the GPLv2

 * Mounting proc at /proc ...                                             [ ok ]
 * Mounting sysfs at /sys ...                                             [ ok ]
 * Mounting /dev for udev ...                                             [ ok ]
 * Seeding /dev with needed nodes ...                                     [ ok ]
 * Setting up proper hotplug agent ...
 *   Using netlink for hotplug events...
                                                                          [ ok ]
 * Starting udevd ...                                                     [ ok ]
 * Populating /dev with existing devices through uevents ...              [ ok ]
 * Letting udev process events ...                                        [ ok ]
 * Finalizing udev configuration ...                                      [ ok ]
 * Mounting devpts at /dev/pts ...                                        [ ok ]
 * Activating (possible) swap ...                                         [ ok ]
 * Initializing the Kurobox AVR ...ààààààààààààààààààààààààààààààààààààààààààààà
àààààààààààààààààààààààààààààààààààààààààààààààààààààààààààààààààààààààààààààààà
àààààààààààààààààààààààààààààààààààààààààààààààààààààààààààààààààààààààààààààààà
àààààààààààààààààààààààààààààààààààààààààààààààààààààààààààààààààààààààààààààààà
àààààààààààààààààààààààààààààààààààààààààààààààààààààààààààààààààààààààààààààààà
àààààààààààààààààààààààààààààààààààààààààààààààààààààààààààààààààààààààààààààààà
àààààààààààààààààààààààààààààààààààààààààààààààààààààààààààààààààààààààààààààààà
àààààààààààààààààààààààààààààààààààààààààààààààààààààààààààààààààààààààààààààààà
àààààààààààààààààààààààààààààààààààààààààààààààààààààààààààààààààààààààààààààààà
àààààààààààààààààààààààààààààààààààààààààààààààààààààààààààààààààààààààààààààààà
àààààààààààààààààààààààààààààààààààààààààààààààààààààààààààààààààààààààààààààààà
àààààààààààààààààààààààààààààààààààààààààààààààààààààààààààààààààààààààààààààààà
àààààààààààààààààààààààààààààààààààààààààààààààààààààààààààààààààààààààààààààààà
àààààààààààààààààààààààààààààààààààààààààààààààààààààààààààààààààààààààààààààààà
àààààààààààààààààààààààààààààààààààààààààààààààààààààààààààààààààààààààààààààààà
àààààààààààààààààààààààààààààààààààààààààààààààààààààààààààààààààààààààààààààààà
àààààààààààààààààààààààààààààààààààààààààààààààààààààààààààààààààààààààààààààààà
àààààààààààààààààààààààààààààààààààààààààààààààààààààààààààààààààààààààààààààààà
àààààààààààààààààààààààààààààààààààààààààààààààààààààààààààààààààààààààààààààààà
ààààààààààààààààààààààààà

U-Boot 1.1.4-gf7b190d3-dirty (Jan  5 2007 - 21:02:23) LinkStation / KuroBox

CPU:   MPC8245 Revision 1.4 at 196.608 MHz: 16 kB I-Cache 16 kB D-Cache
DRAM:  64 MB
FLASH:  4 MB
        00  0b  1317  0985  0200  ff
        00  0c  1095  0680  0101  ff
        00  0e  1033  0035  0c03  ff
        00  0e  1033  0035  0c03  ff
        00  0e  1033  00e0  0c03  ff
Net:   COMET#0
stdin :   serial
stdout:   serial
stderr:   serial
IDE:   Bus 0: OK
  Device 0: Model: ST3300831A Firm: 3.03 Ser#: 3NF01G7P
            Type: Hard Disk
            Supports 48-bit addressing
            Capacity: 286168.1 MB = 279.4 GB (586072368 x 512)
Boot in 03 seconds ('s' to stop)...
[/code]


Top
   
 Post subject:
PostPosted: Fri Jan 05, 2007 9:15 pm 
Offline

Joined: Thu Jun 23, 2005 12:24 pm
Posts: 287
Started my kuro in christmas tree mode and waited. I figured without the watchdog to shut it down because the AVR wasn't initialized I could just wait a few minutes for it to finish booting. All I saw on the serial console was data sent to the AVR, but there was a different story all together on the SSH console"

Code:
localhost ~ # uname -a
Linux localhost 2.6.20-rc3 #1 Fri Jan 5 00:31:36 CET 2007 ppc 82xx Linkstation I/Kurobox(HG) GNU/Linux
localhost ~ #


Top
   
 Post subject:
PostPosted: Fri Jan 05, 2007 10:23 pm 
Offline

Joined: Thu Jun 23, 2005 12:24 pm
Posts: 287
edited /etc/inittab and /etc/init.d/kuro-avr-init and swapped the serial ports and it booted without losing the serial console. still getting data from kuroevtd on the serial console. I guess I should upgrade to avr-evtd and this will go away too.


Top
   
 Post subject: 2.6.20(-rcX) on kuros
PostPosted: Sat Jan 06, 2007 4:16 am 
Offline

Joined: Sun Mar 12, 2006 4:26 am
Posts: 74
Nice, Dave, thanks for testing.

Great that it worked from the first shot - in (semi-)dark. What's even more remarkable, is that the kernel I gave you is the same as what's running on my HG - you can see the compilation date. So, yesterday I've just compiled new U-boot binaries for HG, written a HG device-tree spec, compiled it and sent you together with my kernel. So, we did prove it that the same kernel will run on various linkstation variants.

As for the UARTs - I knew they'd be swapped. As I already mentioned several times - I use the traditional ppc-Linux UART numbering for 8245 and similar SOCs. It's the original manufacturer who swapped them in 2.4 kernel and then it has been done similarly for 2.6. But, 1) you shouldn't NEED any daemon with this kernel - provided HG has the same watchdog-off, reset, and power-off commands. The kernel issues these itself. So, you can boot, it will work without been resetted by the AVR watchdog, and you'll be able to issue reboot / halt as usual. Only if you want to use buttons / control LEDs, the fan, monitore temperature, only then do you need a daemon. 2) You can recognise which of the ttyS0 / ttyS1 you have to use from an application automatically by reading the /proc/tty/driver/serial. 3) More elegant would be writing a udev rule to let it create links like /dev/serial/avr and /dev/serial/console. Then you just open them in your apps.

What interests me more is if all your PCI devices work: USB, IDE (now controlled by PATA / SCSI), ETH. From your posts looks like eth and ide work. That's already good. What about USB? You might find it ammusing to look at /proc/interrupts - they are completely different now. They are virtual now, without any "real" meaning.

Have I forgotten to check anything? Yes - rtc, does it work (hwclock)?

If everything works, I'll submit HG's .dts (device tree source) for the next kernel release together with the configuration extension and a minor modification to linkstation.c.

Thanks
Guennadi


Top
   
 Post subject: device-tree
PostPosted: Sat Jan 06, 2007 4:49 am 
Offline

Joined: Sun Mar 12, 2006 4:26 am
Posts: 74
Addendum: you might also find it entertaining to browse /proc/device-tree or do
Code:
cd /proc/device-tree
lsprop | less

As for your note about rebuilding your own u-boot - you, probably, don't need to - just modify the variables and save your environment. Is there anything that's not covered?

Thanks
Guennadi


Top
   
 Post subject:
PostPosted: Sat Jan 06, 2007 10:10 am 
Offline

Joined: Thu Jun 23, 2005 12:24 pm
Posts: 287
also needed to edit /etc/secutetty to allow login on ttyS1.

Playing with the device tree now. Will keep you all posted, but so far, Lyakh (for making this work and documenting it) and Infinoid (absolutely no relation to the dead russian spy, for wikifying it) get huge props for this effort.

I like it. I like it a lot.

tampa-kuroguy


Last edited by Dave Taylor on Sat Jan 06, 2007 10:54 am, edited 2 times in total.

Top
   
 Post subject:
PostPosted: Sat Jan 06, 2007 10:36 am 
Offline

Joined: Thu Jun 23, 2005 12:24 pm
Posts: 287
Code:
localhost device-tree # lsprop | less
name             ""
#size-cells      00000001
#address-cells   00000001
compatible       "linkstation"
model            "KuroboxHD"
linux,phandle    00001000 (4096)

chosen:
linux,stdout-path "/soc10x/serial@80004600"
bootargs         "root=/dev/sda1 console=ttyS1,57600 netconsole=@192.168.1.7/eth
0,@192.168.1.1/00:50:BF:A4:59:71 rtc-rs5c372.probe=0,0x32 debug"
name             "chosen"
linux,platform   00000600 (1536)

soc10x:
name             "soc10x"
ranges           80000000 80000000 70000000 fc000000 fc000000
                 00100000 fe000000 fe000000 00c00000 fec00000
                 fec00000 00300000 fef00000 fef00000 00100000
reg              80000000 00100000
store-gathering  00000000
compatible       "mpc10x"
device_type      "soc"
#interrupt-cells 00000002
#size-cells      00000001
#address-cells   00000001
linux,phandle    00004000 (16384)

soc10x/pci@fec00000:
name             "pci"
interrupt-map    00005800 00000000 00000000 00000001
                 00004400 00000000 00000001 00005800
                 00000000 00000000 00000002 00004400
                 00000001 00000001 00005800 00000000
                 00000000 00000003 00004400 00000002
                 00000001 00005800 00000000 00000000
                 00000004 00004400 00000003 00000001
                 00006000 00000000 00000000 00000001
                 [336 bytes total]
interrupt-map-mask 0000f800 00000000 00000000 00000007
interrupt-parent 00004400 (17408)
clock-frequency  07f28155 (133333333)
bus-range        00000000 000000ff
ranges           01000000 00000000 00000000 fe000000 00000000 00c00000
                 02000000 00000000 80000000 80000000 00000000 70000000
reg              fec00000 00400000
compatible       "mpc10x-pci"
device_type      "pci"
#interrupt-cells 00000001
#size-cells      00000002
#address-cells   00000003
linux,phandle    00004500 (17664)

soc10x/pic@80040000:
name             "pic"
built-in       
reg              80040000 00040000
interrupt-controller
compatible       "chrp,open-pic"
device_type      "open-pic"
#address-cells   00000000
#interrupt-cells 00000002
linux,phandle    00004400 (17408)

soc10x/serial@80004600:
name             "serial"
interrupt-parent 00004400 (17408)
interrupts       0000000a 00000000
current-speed    0000e100 (57600)
clock-frequency  05d08d88 (97553800)
reg              80004600 00000008
compatible       "ns16550"
device_type      "serial"
linux,phandle    00004512 (17682)

soc10x/serial@80004500:
name             "serial"
interrupt-parent 00004400 (17408)
interrupts       00000009 00000002
current-speed    00002580 (9600)
clock-frequency  05d08d88 (97553800)
reg              80004500 00000008
compatible       "ns16550"
device_type      "serial"
linux,phandle    00004511 (17681)

soc10x/i2c@80003000:
name             "i2c"
interrupt-parent 00004400 (17408)
interrupts       00000005 00000002
reg              80003000 00001000
compatible       "fsl-i2c"
device_type      "i2c"
linux,phandle    00004300 (17152)

memory:
name             "memory"
reg              00000000 04000000
device_type      "memory"
linux,phandle    00003000 (12288)

cpus:
name             "cpus"
#size-cells      00000000
#address-cells   00000001
#cpus            00000001
linux,phandle    00002000 (8192)

cpus/PowerPC,603e:
name             "PowerPC,603e"
d-cache-size     00004000 (16384)
i-cache-size     00004000 (16384)
d-cache-line-size 00000000
i-cache-line-size 00000000
bus-frequency    00000000
timebase-frequency 01743000 (24391680)
clock-frequency  0bb80000 (196608000)
reg              00000000
device_type      "cpu"
linux,boot-cpu 
linux,phandle    00002100 (8448)


Top
   
 Post subject:
PostPosted: Mon Jan 08, 2007 4:42 pm 
Offline

Joined: Fri Dec 17, 2004 3:46 pm
Posts: 209
Hi. is there anything I could do to give you the necessary information for building a KuroBoxHD (Linkstation HD) compatible version of the dts file included in the kernel rc?


Top
   
 Post subject:
PostPosted: Mon Jan 08, 2007 5:00 pm 
Offline

Joined: Sun Mar 12, 2006 4:26 am
Posts: 74
mephisto wrote:
Hi. is there anything I could do to give you the necessary information for building a KuroBoxHD (Linkstation HD) compatible version of the dts file included in the kernel rc?

Thanks for the offer, but as you can see we've managed to get a version for HDs running. That's where the device tree listing in this thread comes from. So far no problems are known, but more testing is always good. I plan to submit it for the next stable kernel version (2.6.21). The last ppc platform left, AFAICS, is the Terastation.

Thanks
Guennadi


Top
   
 Post subject:
PostPosted: Mon Jan 08, 2007 7:26 pm 
Offline

Joined: Fri Dec 17, 2004 3:46 pm
Posts: 209
That's great. Is there any way you could provide me/us with the necessary patches to test it on the HD? The wiki still talks about the showstopper for standard Kurobox owners.


Top
   
Display posts from previous:  Sort by  
Forum locked  This topic is locked, you cannot edit posts or make further replies.  [ 97 posts ]  Go to page 1 2 3 4 57 Next

All times are UTC-06:00


Who is online

Users browsing this forum: No registered users and 2 guests


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:  
cron
Powered by phpBB® Forum Software © phpBB Limited