New IT forum
27 June 2022, 06:07:09 am *
Welcome, %1$s. Please login or register.

: CubieBoard 2 and Cubietruck both now in stock.
 
Pages: [1] 2

Author Topic: boot stop on debian dreamplug  (Read 16269 times)

piratebab

  • Full Member
  • ***
  • Posts: 124
boot stop on debian dreamplug
« on: 31 March 2013, 10:46:47 am »

Hello
dreamplug model: 003-DS2001
debian wheezy

My dreamplug works very well for monts (even years) as a car computer, and I tried to reduce boot time. Bad idea.
Now the boot get stuck at
Quote
Bluetooth: RFCOMM TTY layer initialized
Bluetooth: RFCOMM socket layer initialized
Bluetooth: RFCOMM ver 1.11


what is it suppose to start after that ?
If someone can paste the boot sequence of a debian , It can help be to understand where is the problem.
« Last Edit: 31 March 2013, 01:20:24 pm by piratebab »
Logged

NewIT_Malcolm

  • Administrator
  • Jr. Member
  • *****
  • Posts: 65
Re: boot stop on debian dreamplug
« Reply #1 on: 02 April 2013, 08:25:21 am »

Here is the bootlog from a standard Dreamplug

http://www.newit.co.uk/forum/index.php/topic,3519.0.html
Logged

Ralph Houston

  • New IT customer
  • Full Member
  • *
  • Posts: 136
Re: boot stop on debian dreamplug
« Reply #2 on: 02 April 2013, 04:01:30 pm »

Aargh!
Have just got my DreamPlug to boot Debian Wheezy from a USB stick and I see I've been beaten to it!
Good luck
Ralph
Logged

piratebab

  • Full Member
  • ***
  • Posts: 124
Re: boot stop on debian dreamplug
« Reply #3 on: 02 April 2013, 06:48:13 pm »

Thank you malcolm, but I did not recognize by boot sequence in your example!
mine is more like this one
http://www.newit.co.uk/forum/index.php?action=printpage;topic=3241.0

or this one
http://www.plugcomputer.org/plugforum/index.php?topic=4885.5;wap2

so it seems that it is stuck before this step
Quote
Bluetooth: RFCOMM ver 1.11
Logged

Confusticated

  • New IT customer
  • Hero Member
  • *
  • Posts: 663
Re: boot stop on debian dreamplug
« Reply #4 on: 02 April 2013, 09:44:01 pm »

Post the output of
Code: [Select]
ls -l  /etc/rcS.d /etc/rc$(awk -F: '/initdefault/  {print$2}' /etc/inittab).d
Logged
Advocatus Diaboli - My agenda is not to give you the answer, but to guide your thoughts so you derive it for yourself!

Ralph Houston

  • New IT customer
  • Full Member
  • *
  • Posts: 136
Re: boot stop on debian dreamplug
« Reply #5 on: 03 April 2013, 08:56:04 am »

So maybe I haven't wasted my time. Is your sequence any more like this, which is from my Dreamplug booting from a USB stick containing NewIT-Dreamplug-Debian-Wheezy-2Gb-31Aug11.img:

Code: [Select]
Uncompressing Linux... done, booting the kernel.
Initializing cgroup subsys cpu
Linux version 2.6.38.8 ([email protected]) (gcc version 4.5.3 (PlugComputer G++ 20110530) ) #7 PREEMPT Sat Jun 25 18:13:16 MDT 201
CPU: Feroceon 88FR131 [56251311] revision 1 (ARMv5TE), cr=00053977
CPU: VIVT data cache, VIVT instruction cache
Machine: Marvell GuruPlug Reference Board
Memory policy: ECC disabled, Data cache writeback
Built 1 zonelists in Zone order, mobility grouping on.  Total pages: 130048
Kernel command line: console=ttyS0,115200 root=/dev/sdc2 panic=10 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: 512MB = 512MB total
Memory: 513716k/513716k available, 10572k reserved, 0K highmem
Virtual kernel memory layout:
    vector  : 0xffff0000 - 0xffff1000   (   4 kB)
    fixmap  : 0xfff00000 - 0xfffe0000   ( 896 kB)
    DMA     : 0xffc00000 - 0xffe00000   (   2 MB)
    vmalloc : 0xe0800000 - 0xfe800000   ( 480 MB)
    lowmem  : 0xc0000000 - 0xe0000000   ( 512 MB)
    modules : 0xbf000000 - 0xc0000000   (  16 MB)
      .init : 0xc0008000 - 0xc002e000   ( 152 kB)
      .text : 0xc002e000 - 0xc04e66d8   (4834 kB)
      .data : 0xc04e8000 - 0xc0517f78   ( 192 kB)
SLUB: Genslabs=13, HWalign=32, Order=0-3, MinObjects=0, CPUs=1, Nodes=1
Preemptable hierarchical RCU implementation.
        RCU-based detection of stalled CPUs is disabled.
        Verbose stalled-CPUs detection is disabled.
NR_IRQS:114
sched_clock: 32 bits at 200MHz, resolution 5ns, wraps every 21474ms
Console: colour dummy device 80x30
Calibrating delay loop... 1192.75 BogoMIPS (lpj=5963776)
pid_max: default: 32768 minimum: 301
Mount-cache hash table entries: 512
CPU: Testing write buffer coherency: ok
devtmpfs: initialized
NET: Registered protocol family 16
Kirkwood: MV88F6281-A1, TCLK=200000000.
Feroceon L2: Cache support initialised.
bio: create slab <bio-0> at 0
vgaarb: loaded
SCSI subsystem initialized
usbcore: registered new interface driver usbfs
usbcore: registered new interface driver hub
usbcore: registered new device driver usb
Switching to clocksource orion_clocksource
Switched to NOHz mode on CPU #0
FS-Cache: Loaded
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: 4, 65536 bytes)
TCP: Hash tables configured (established 16384 bind 16384)
TCP reno registered
UDP hash table entries: 256 (order: 0, 4096 bytes)
UDP-Lite hash table entries: 256 (order: 0, 4096 bytes)
NET: Registered protocol family 1
RPC: Registered udp transport module.
RPC: Registered tcp transport module.
RPC: Registered tcp NFSv4.1 backchannel transport module.
FS-Cache: Netfs 'nfs' registered for caching
JFS: nTxBlock = 4013, nTxLock = 32107
msgmni has been set to 1003
io scheduler noop registered
io scheduler deadline registered
io scheduler cfq registered (default)
Serial: 8250/16550 driver, 2 ports, IRQ sharing disabled
serial8250.0: ttyS0 at MMIO 0xf1012000 (irq = 33) is a 16550A
console [ttyS0] enabled
brd: module loaded
loop: module loaded
MV-643xx 10/100/1000 ethernet driver version 1.4
mv643xx_eth smi: probed
net eth0: port 0 with MAC address f0:ad:4e:00:7e:15
net eth1: port 0 with MAC address f0:ad:4e:00:7e:16
ehci_hcd: USB 2.0 'Enhanced' Host Controller (EHCI) Driver
orion-ehci orion-ehci.0: Marvell Orion EHCI
orion-ehci orion-ehci.0: new USB bus registered, assigned bus number 1
orion-ehci orion-ehci.0: irq 19, io mem 0xf1050000
orion-ehci orion-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
Initializing USB Mass Storage driver...
usbcore: registered new interface driver usb-storage
USB Mass Storage support registered.
usbcore: registered new interface driver ums-datafab
usbcore: registered new interface driver ums-freecom
usbcore: registered new interface driver ums-jumpshot
usbcore: registered new interface driver ums-sddr09
usbcore: registered new interface driver ums-sddr55
mousedev: PS/2 mouse device common for all mice
rtc-mv rtc-mv: rtc core: registered rtc-mv as rtc0
i2c /dev entries driver
cpuidle: using governor ladder
cpuidle: using governor menu
mv_xor_shared mv_xor_shared.0: Marvell shared XOR driver
mv_xor_shared mv_xor_shared.1: Marvell shared XOR driver
mv_xor mv_xor.0: Marvell XOR: ( xor cpy )
mv_xor mv_xor.1: Marvell XOR: ( xor fill cpy )
mv_xor mv_xor.2: Marvell XOR: ( xor cpy )
mv_xor mv_xor.3: Marvell XOR: ( xor fill cpy )
sdhci: Secure Digital Host Controller Interface driver
sdhci: Copyright(c) Pierre Ossman
mmc0: mvsdio driver initialized, lacking card detect (fall back to polling)
usbcore: registered new interface driver usbhid
usbhid: USB HID core driver
oprofile: hardware counters not available
oprofile: using timer interrupt.
TCP cubic registered
NET: Registered protocol family 17
lib80211: common routines for IEEE802.11 drivers
Registering the dns_resolver key type
registered taskstats version 1
rtc-mv rtc-mv: setting system clock to 2013-04-02 11:45:27 UTC (1364903127)
Waiting for root device /dev/sdc2...
mmc0: new high speed SDIO card at address 0001
usb 1-1: new high speed USB device using orion-ehci and address 2
hub 1-1:1.0: USB hub found
hub 1-1:1.0: 4 ports detected
usb 1-1.1: new high speed USB device using orion-ehci and address 3
scsi0 : usb-storage 1-1.1:1.0
usb 1-1.2: new high speed USB device using orion-ehci and address 4
scsi1 : usb-storage 1-1.2:1.0
usb 1-1.4: new full speed USB device using orion-ehci and address 5
input: C-Media USB Headphone Set   as /devices/platform/orion-ehci.0/usb1/1-1/1-1.4/1-1.4:1.3/input/input0
generic-usb 0003:0D8C:000C.0001: input: USB HID v1.00 Device [C-Media USB Headphone Set  ] on usb-orion-ehci.0-1.4/input3
scsi 0:0:0:0: Direct-Access     Generic  STORAGE DEVICE   9910 PQ: 0 ANSI: 0
sd 0:0:0:0: Attached scsi generic sg0 type 0
scsi 0:0:0:1: Direct-Access     Generic  STORAGE DEVICE   9910 PQ: 0 ANSI: 0
sd 0:0:0:0: [sda] 3842048 512-byte logical blocks: (1.96 GB/1.83 GiB)
sd 0:0:0:1: Attached scsi generic sg1 type 0
sd 0:0:0:0: [sda] Write Protect is off
sd 0:0:0:0: [sda] Assuming drive cache: write through
sd 0:0:0:1: [sdb] Attached SCSI removable disk
sd 0:0:0:0: [sda] Assuming drive cache: write through
 sda: sda1 sda2
sd 0:0:0:0: [sda] Assuming drive cache: write through
sd 0:0:0:0: [sda] Attached SCSI removable disk
scsi 1:0:0:0: Direct-Access     Verbatim STORE N GO       0.00 PQ: 0 ANSI: 2
sd 1:0:0:0: Attached scsi generic sg2 type 0
sd 1:0:0:0: [sdc] 3913728 512-byte logical blocks: (2.00 GB/1.86 GiB)
sd 1:0:0:0: [sdc] Write Protect is off
sd 1:0:0:0: [sdc] Assuming drive cache: write through
sd 1:0:0:0: [sdc] Assuming drive cache: write through
 sdc: sdc1 sdc2
sd 1:0:0:0: [sdc] Assuming drive cache: write through
sd 1:0:0:0: [sdc] Attached SCSI removable disk
EXT3-fs: barriers not enabled
kjournald starting.  Commit interval 5 seconds
EXT3-fs (sdc2): using internal journal
EXT3-fs (sdc2): mounted filesystem with writeback data mode
VFS: Mounted root (ext3 filesystem) on device 8:34.
Freeing init memory: 152K
INIT: version 2.88 booting
Using makefile-style concurrent boot in runlevel S.
.udev/ already exists on the static /dev! ... (warning).
Starting the hotplug events dispatcher: udevdudevd[659]: can not read '/etc/udev/rules.d/75-persistent-net-generator.rules'

.
Synthesizing the initial hotplug events...udevd[660]: can not read '/etc/udev/rules.d/75-persistent-net-generator.rules'

done.
Waiting for /dev to be fully populated...uap_probe: vendor=0x02DF device=0x9104 class=0 function=1
sata_mv sata_mv.0: version 1.28
sata_mv sata_mv.0: slots 32 ports 1
scsi2 : sata_mv
ata1: SATA max UDMA/133 irq 21
Bluetooth: Core ver 2.15
NET: Registered protocol family 31
Bluetooth: HCI device and connection manager initialized
Bluetooth: HCI socket layer initialized
UAP FW is active
ata1: SATA link down (SStatus 0 SControl F300)
usbcore: registered new interface driver snd-usb-audio
Bluetooth: vendor=0x2df, device=0x9105, class=255, fn=2
done.
Activating swap...done.
Cleaning up ifupdown....
Setting up networking....
Loading kernel modules...done.
Activating lvm and md swap...done.
Checking file systems...fsck from util-linux-ng 2.17.2
done.
Mounting local filesystems...done.
Activating swapfile swap...done.
Cleaning up temporary files....
Configuring network interfaces...Internet Systems Consortium DHCP Client 4.1.1-P1
Copyright 2004-2010 Internet Systems Consortium.
All rights reserved.
For info, please visit https://www.isc.org/software/dhcp/

Listening on LPF/eth0/f0:ad:4e:00:7e:15
Sending on   LPF/eth0/f0:ad:4e:00:7e:15
Sending on   Socket/fallback
DHCPDISCOVER on eth0 to 255.255.255.255 port 67 interval 4
DHCPDISCOVER on eth0 to 255.255.255.255 port 67 interval 4
DHCPDISCOVER on eth0 to 255.255.255.255 port 67 interval 5
DHCPDISCOVER on eth0 to 255.255.255.255 port 67 interval 8
DHCPDISCOVER on eth0 to 255.255.255.255 port 67 interval 8
DHCPDISCOVER on eth0 to 255.255.255.255 port 67 interval 11
DHCPDISCOVER on eth0 to 255.255.255.255 port 67 interval 12
DHCPDISCOVER on eth0 to 255.255.255.255 port 67 interval 9
No DHCPOFFERS received.
No working leases in persistent database - sleeping.
Internet Systems Consortium DHCP Client 4.1.1-P1
Copyright 2004-2010 Internet Systems Consortium.
All rights reserved.
For info, please visit https://www.isc.org/software/dhcp/

Listening on LPF/eth1/f0:ad:4e:00:7e:16
Sending on   LPF/eth1/f0:ad:4e:00:7e:16
Sending on   Socket/fallback
DHCPDISCOVER on eth1 to 255.255.255.255 port 67 interval 6
DHCPDISCOVER on eth1 to 255.255.255.255 port 67 interval 7
DHCPDISCOVER on eth1 to 255.255.255.255 port 67 interval 11
DHCPDISCOVER on eth1 to 255.255.255.255 port 67 interval 13
DHCPDISCOVER on eth1 to 255.255.255.255 port 67 interval 13
DHCPDISCOVER on eth1 to 255.255.255.255 port 67 interval 7
DHCPDISCOVER on eth1 to 255.255.255.255 port 67 interval 4
No DHCPOFFERS received.
No working leases in persistent database - sleeping.
done.
Cleaning up temporary files....
Setting kernel variables ...done.
INIT: Entering runlevel: 2
Using makefile-style concurrent boot in runlevel 2.
Starting enhanced syslogd: rsyslogd.
Generating SSH keysStarting periodic command scheduler: cron.
Starting system message bus: dbus.
Starting NTP server: ntpd.
Bluetooth: L2CAP ver 2.15
Bluetooth: L2CAP socket layer initialized
NET: Registered protocol family 10
ADDRCONF(NETDEV_UP): eth0: link is not ready
ADDRCONF(NETDEV_UP): eth1: link is not ready
Bluetooth: BNEP (Ethernet Emulation) ver 1.3
Bluetooth: RFCOMM TTY layer initialized
Bluetooth: RFCOMM socket layer initialized
Bluetooth: RFCOMM ver 1.11
Bridge firewalling registered
Starting bluetooth: bluetoothd.
Bluetooth: SCO (Voice Link) ver 0.6
Bluetooth: SCO socket layer initialized
Starting very small Busybox based DHCP server: Starting /usr/sbin/udhcpd...
udhcpd.
sshd (1261): /proc/1261/oom_adj is deprecated, please use /proc/1261/oom_score_adj instead.
Starting OpenBSD Secure Shell server: sshdCould not load host key: /etc/ssh/ssh_host_rsa_key
Could not load host key: /etc/ssh/ssh_host_dsa_key
.
Creating SSH2 RSA key; this may take some time ...
Creating SSH2 DSA key; this may take some time ...
Restarting OpenBSD Secure Shell server: sshd.
update-rc.d: using dependency based boot sequencing
ADDRCONF(NETDEV_UP): uap0: link is not ready
SSID setting successful
BSS started!
Starting very small Busybox based DHCP server: Starting /usr/sbin/udhcpd...
udhcpd.

Debian GNU/Linux 6.0 debian ttyS0

debian login: Agent registered

If not, which image did you load?

I assume your device doesn't actually boot any more.

Regards
Ralph
Logged

piratebab

  • Full Member
  • ***
  • Posts: 124
Re: boot stop on debian dreamplug
« Reply #6 on: 03 April 2013, 07:22:06 pm »

confusticated, the device does not give be the possibility to enter any command, the boot sequence does not go to the end.
Ralph, i dont remember exactly the image I installed, it was many months ago. I suppose it was the official one as a basis, but I made many modification
http://code.google.com/p/dreamplug/downloads/list

Here are a parts of my boot sequence (I can not capture the complete one)
I got many udev errors, then
Quote
udevd[675]: SYSFS{}= will be removed in a future udev version, please use ATTR{}= to match the event device, or ATTRS{}= to match a parent device, in /etc/udev/rules.d/z60_xserver-xorg-input-wacom.rules:78

sata_mv sata_mv.0: version 1.28
sata_mv sata_mv.0: slots 32 ports 1
input: e2i Technology, Inc. USB Touchpanel as /devices/platform/orion-ehci.0/usb1/1-1/1-1.3/1-1.3.3/1-1.3.3:1.0/input/input1
scsi2 : sata_mv
ata1: SATA max UDMA/133 irq 21
usbcore: registered new interface driver usbtouchscreen
cfg80211: Calling CRDA to update world regulatory domain
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
ata1: SATA link down (SStatus 0 SControl F300)
udlfb: DisplayLink MIMO - serial #1070001576
udlfb: vid_17e9&pid_0335&rev_0115 driver's dlfb_data struct at df035000
Bluetooth: vendor=0x2df, device=0x9105, class=255, fn=2
libertas_sdio: Libertas SDIO driver
libertas_sdio: Copyright Pierre Ossman
udlfb: console enable=0
udlfb: fb_defio enable=1
udlfb: vendor descriptor length:23 data:23 5f 01 0021 00 04 04 07 00 01
udlfb: DL chip limited to 1500000 pixel modes
udlfb: allocated 4 65024 byte urbs
udlfb: 800x480 valid mode
udlfb: Reallocating framebuffer. Addresses will change!
udlfb: 800x480 valid mode
udlfb: set_par mode 800x480
udlfb: DisplayLink USB device /dev/fb0 attached. 800x480 resolution. Using 1504K framebuffer memory
usbcore: registered new interface driver udlfb
libertas: 00:24:23:39:0b:24, fw 10.38.1p25, cap 0x00000303
libertas: wlan0: Marvell WLAN 802.11 adapter
usbcore: registered new interface driver snd-usb-audio
EXT3-fs: barriers not enabled
EXT3-fs (sdb1): warning: maximal mount count reached, running e2fsck is recommended
kjournald starting.  Commit interval 5 seconds
EXT3-fs (sdb1): using internal journal
EXT3-fs (sdb1): recovery complete
EXT3-fs (sdb1): mounted filesystem with writeback data mode
done.
Setting parameters of disc: (none).
fuse init (API version 7.16)
Activating swap...done.
mount: can't find /run in /etc/fstab or /etc/mtab
mount: can't find /run/shm in /etc/fstab or /etc/mtab
Cleaning up ifupdown....
Loading kernel modules...done.
Activating lvm and md swap...done.
Checking file systems...fsck from util-linux 2.19.1
done.
Setting kernel variables ...done.
Mounting local filesystems...mount: mount point /dev/shm does not exist
mount: mount point /dev/pts does not exist
mount: sysfs already mounted or /sys busy
mount: special device /dev/sdb1 does not exist
failed.
Activating swapfile swap...done.
Cleaning up temporary files....
Mounting emergency tmpfs on /tmp...done.
Setting up networking....
Configuring network interfaces...done.
Cleaning up temporary files.../lib/init/bootclean.sh: 139: cannot create /dev/null: File exists
.
Setting up ALSA...warning: 'alsactl restore' failed with error message 'alsactl: load_state:1610: No soundcards found...'...Invalid card number.
Usage: amixer <options> [command]

Then many alsa errors, and
Quote
mv643xx_eth_port mv643xx_eth_port.0: eth0: link up, 100 Mb/s, full duplex, flow control disabled
NET: Registered protocol family 10
ADDRCONF(NETDEV_UP): eth1: link is not ready
Bluetooth: RFCOMM TTY layer initialized
Bluetooth: RFCOMM socket layer initialized
Bluetooth: RFCOMM ver 1.11

and then, nothing.
i suppose that the following sequence must be
Quote
Bridge firewalling registered
Starting bluetooth: bluetoothd.
Bluetooth: SCO (Voice Link) ver 0.6
Bluetooth: SCO socket layer initialized

but it never appears.
i try booting on an usb stick, it works fine
Logged

Confusticated

  • New IT customer
  • Hero Member
  • *
  • Posts: 663
Re: boot stop on debian dreamplug
« Reply #7 on: 03 April 2013, 08:16:33 pm »

Quote
confusticated, the device does not give be the possibility to enter any command
append the word 'single' to the end of the bootargs variable in u-boot.
If it still goes too far and hangs, append 'init=/bin/bash' instead.
« Last Edit: 03 April 2013, 08:19:11 pm by Confusticated »
Logged
Advocatus Diaboli - My agenda is not to give you the answer, but to guide your thoughts so you derive it for yourself!

Ralph Houston

  • New IT customer
  • Full Member
  • *
  • Posts: 136
Re: boot stop on debian dreamplug
« Reply #8 on: 03 April 2013, 09:52:11 pm »

Indeed, whatever happens between
Quote
Bluetooth: RFCOMM ver 1.11
and
Quote
Bridge firewalling registered
must be the problem.

People ask me why I make so many backups, but this kind of situation is why!

Good luck
Ralph
Logged

piratebab

  • Full Member
  • ***
  • Posts: 124
Re: boot stop on debian dreamplug
« Reply #9 on: 07 April 2013, 06:01:19 pm »

I spend too much time trying to repair this one.
I will install a fresh debian.
Is there still an image from newit ?
Logged

Ralph Houston

  • New IT customer
  • Full Member
  • *
  • Posts: 136
Re: boot stop on debian dreamplug
« Reply #10 on: 07 April 2013, 06:15:17 pm »

They're all still here:
downloadsnewit.co.uk/SD-images/Dreamplug

Sometimes it's simpler to start over!

Bonne chance
Ralph
Logged

piratebab

  • Full Member
  • ***
  • Posts: 124
Re: boot stop on debian dreamplug
« Reply #11 on: 08 April 2013, 06:06:15 pm »

OK, thank you.
They are not very fresh (Aug 2011)
Logged

Ralph Houston

  • New IT customer
  • Full Member
  • *
  • Posts: 136
Re: boot stop on debian dreamplug
« Reply #12 on: 15 April 2013, 08:26:06 pm »

Logged

piratebab

  • Full Member
  • ***
  • Posts: 124
Re: boot stop on debian dreamplug
« Reply #13 on: 30 April 2013, 06:37:24 pm »

Debian is now (re)installed.
I dont use multiboot.
2 points are not solved yet:
- wifi client (see my other thread)
- font size. It seems I have a DPI problem in my Xorg conf

Logged

Ralph Houston

  • New IT customer
  • Full Member
  • *
  • Posts: 136
Re: boot stop on debian dreamplug
« Reply #14 on: 01 May 2013, 06:40:58 am »

Wifi - which other thread? I can't find it.
Please use 'Insert hyperlink':
Code: [Select]
[url]LINK[/url] to point to stuff like this.
Regards
Ralph
Logged
Pages: [1] 2
 
 

Powered by MySQL Powered by PHP SMF 2.0.10 | SMF © 2015, Simple Machines Valid XHTML 1.0! Valid CSS!