DOCSIS 1.1 Upstream Speed config problem

Helllo,
I am trying to configure a UBR7246 with IOS 12.3(23)BC4 to run 16QAM upstream channels with the intention of providing up to 3.Mbps of upstream bandwidth to my users.  Everything is working fine with 16QAM, minislot size of 4, and the "show cable modem QOS" command shows the upstream bandwidth and burst settings I have used in my modem config files.  I am using max burst of 4000 and max concatenated burst of 4000.
The problem is that I still cannot get over 2.10Mbps on an upstream with only 1 test modem on it and under 20% utilization on my 45Mbps connection to the Internet.  This is not an over-subscription issue or anything and I am wondering if I have something configured wrong.
Can anyone help me with how to get higher upstream bandwidth?  I know the theoretical max for this profile is 7.6Mbps, and I only want to do 3.0Mbps.  I know this is utilization depend, etc., but I only have one modem on the upstream.
I am only using cable upstream 3 for this and have edited out other parts of the config.
CMTS config items of interest:
interface Cable1/0
ip address x.x.x.x 255.255.255.192 secondary
ip address 10.203.240.1 255.255.248.0
ip access-group 110 in
ip access-group 110 out
no cable packet-cache
cable downstream channel-id 0
cable downstream annex B
cable downstream modulation 64qam
cable downstream interleave-depth 32
cable downstream frequency 117000000
no cable downstream rf-shutdown
cable downstream rf-power 50
cable upstream 3 frequency 28000000
cable upstream 3 docsis-mode tdma
cable upstream 3 channel-width 3200000
cable upstream 3 minislot-size 2
cable upstream 3 modulation-profile 9
no cable upstream 3 shutdown
cable arp filter request-send 3 2
cable arp filter reply-accept 3 2
cable source-verify dhcp
cable dhcp-giaddr policy
cable helper-address x.x.x.x
CMTS#show cable modem x.x.x.x qos
Sfid  Dir Curr  Sid   Sched  Prio MaxSusRate  MaxBrst   MinRsvRate  Throughput
          State       Type
15831 US  act   1083  BE     0    3000000     4000      0           2832
8810  US  act   1080  BE     4    0           3044      0           0
15838 DS  act   N/A   BE     0    10000000    1522      0           43
15850 DS  act   N/A   BE     4    0           3044      0           0
show cable modulation-profile:
9    request 16qam 128 no   0x0  0x10 0x152  0   8     no   yes   384   16qam na                        
9    initial 16qam 256 no   0x5  0x22 0x152  0   48    no   yes   256   16qam na
9    station 16qam 256 no   0x5  0x22 0x152  0   48    no   yes   256   16qam na
9    short   16qam 144 no   0x5  0x4C 0x152  7   8     yes  yes   368   16qam na
9    long    16qam 160 no   0x8  0xE7 0x152  0   8     yes  yes   352   16qam na
Modem config:
/* Style Definitions */
table.MsoNormalTable
{mso-style-name:"Table Normal";
mso-tstyle-rowband-size:0;
mso-tstyle-colband-size:0;
mso-style-noshow:yes;
mso-style-priority:99;
mso-style-qformat:yes;
mso-style-parent:"";
mso-padding-alt:0in 5.4pt 0in 5.4pt;
mso-para-margin:0in;
mso-para-margin-bottom:.0001pt;
mso-pagination:widow-orphan;
font-size:11.0pt;
font-family:"Calibri","sans-serif";
mso-ascii-font-family:Calibri;
mso-ascii-theme-font:minor-latin;
mso-fareast-font-family:"Times New Roman";
mso-fareast-theme-font:minor-fareast;
mso-hansi-font-family:Calibri;
mso-hansi-theme-font:minor-latin;
mso-bidi-font-family:"Times New Roman";
mso-bidi-theme-font:minor-bidi;}
        UsServiceFlow
                UsServiceFlowRef 1;
                QosParamSetType 7;
                MaxRateSustained 3000000;
                MaxTrafficBurst 4000;
                MaxConcatenatedBurst 4000;
                SchedulingType 2;
Thanks,
Bill

Thanks for the excellent responses!  I did resolve the problem and ended up using a combination of CMTS configuration and modem changes.  I did the following:
1.  Increased the upstream "max burst" and "max concatenated burst".  I tested with settings between 4000 and 16000.  The higher setting provided the largest bandwidth increase, (in the modem config), when coupled with a higher mini-slot setting.
2.  I used the "cable default phy burst" setting on the CMTS. made sure fragmentation was set at 2000, and turned off rate limiting on the upstream interface.
This is a small MSO with less than 5000 subscribers, and they are not prepared to move to DOCSIS 2 or 3.  I was able to use "mixed mode" for the modulation profile and provided them with upstream speeds of up-to 3.0Mbps.  (You can go to over 7Mbps if you want, but there are trade-offs in doing this.)
The new upstream speed tier is for a limited amout of customers and the MSO is quite happy now.
Let me know if anyone needs more info on this and I would be glad to provide it.  I imagine most folks have moved on to DOCSIS 2 and 3, but a lot of small MSO's cannot afford to do this.
Cheers,
Bill

Similar Messages

  • Upstream pkg-config Depend and Installed Version Descrepancies

    Hi,
    I'm attempting to update the AUR package for gnome-gmail-notifier to agree to the latest release upstream. The problem is, that the upstream configure script checks for the dependancy libsoup-2.2 using pkg-config. In an up to date Arch install however, there does not exist a libsoup-2.2.pc file. Instead, we have libsoup-2.4.pc.
    In this case, the dependancy is technically met, but the configure script fails anyways. In the Arch Linux world, how is this discrepancy properly handled? Upstream? Is there something to handle this in the context of the PKGBUILD file?
    I know how to fix this for myself, on this machine. I'm more curious how the folks of Arch that want to make a proper package would handle this.
    Cheers,
    ~djc

    Just to not leave this thread hanging, I decided to use sed to edit the configure.ac file in the PKGBUILD build() function. Does the trick, but I'm not sure it's the proper way. I do see sed being used for many modifications in other packages, however, so I'll run with this solution for now

  • Motorola - SURFboard DOCSIS 3.0 High-Speed Cable Modem - Silver

    can you use a Motorola - SURFboard DOCSIS 3.0 High-Speed Cable Modem - Silver and a router instead of the modem/router that they provide?

    I'm not sure if you're asking about DSL or FiOS service.
    DSL service requires a DSL modem, not a DOCSIS modem.
    FiOS does not use modems, just routers.  FiOS routers do have a MoCA (coax) port to talk to the ONT and set-top-boxes.  You can use non-Verizon routers with FiOS, but it requires an Ethernet connection from the ONT instead of MoCA.  If FiOS TV is used, a Verizon router must be in the mix.
    So, the short answer is there is no Verizon service that uses DOCSIS.  Cable-modems are not used with Verizon services.
    Good Luck.
    If a forum member gives an answer you like, give them the Kudos they deserve. If a member gives you the answer to your question, mark the answer as Accepted Solution so others can see the solution to the problem.

  • Pathetic Upstream speeds - 64kbps

    Recent intermittent connection drops with my upstream sync speed resting at a feeble 64kbps.  A BT engineer visited yesterday.  I did report occasional noise on the line, but they couldn't actually find any fault between the house and the cabinet but they replaced cables outside of the house in the street as well as my master socket regardless.
    Being at the distance limits from the exchange, engineer's tests showed that I can achieve approx 1800 Down / 448 Up (which is in line with my expectations).  After he left, I left the router plugged straight into the test socket (no extension wiring connected) and also with no phone connected.
    Initial connection stats on Netgear DGN1000 was :
    Downstream: 1920kbps
    Upstream: 448kbps
    Line Attenuation (Down/Up): 61.5dB / 31.5 dB
    Noise Margin (Down/Up): 12.5dB / 11.0dB
    I come back home in the evening and the stats were:
    Downstream: 2208 kbps
    Upstream: 64kbps
    Line Attenuation (Down/Up): 61.5dB / 31.5 dB
    Noise Margin (Down/Up): 12.5dB / 2.0dB
    Checked again this morning - the same.  My Downstream is fine (and seems to be connecting at higher than its ever done), just the Upstream is really slow and it seems to have settled at 64kbps.
    Does anybody have any ideas as to what's going on here?

    gigloo99
    Please do not start new posts on the same subjects as it will only cause confusion and you may miss the answer to your question Stuart one of the forum mods has already replied to you offering help have you replied to him
    incase you cannot find your original post hre is a link to it http://community.bt.com/t5/BB-Speed-Connection-Issues/Pathetic-Upstream-speeds-64kbps/m-p/343453
    If you want to say thanks for a helpful answer,please click on the Ratings star on the left-hand side If the reply answers your question then please mark as ’Mark as Accepted Solution’

  • Audio Config" problem after upgrading to 7.6

    I have only had my ipod one week. It is working beautifully. My problem is that I can no longer charge it or add songs to it because I can not open itunes. The previous version worked beautifully on my computer. After I upgraded to 7.6, it stopped working and I get an Audio Config. problem everytime I try to open it. I have tried uninstalling and reinstalling the program but it does not help. What do I need to do to fix this problem?

    I have had my ipod a few weeks - but have nothing but problems letting itunes run the syncing, sometime it works and sometimes it does not. I had to reset my ipod 2 times already just to keep song on here, should have gone with Zune or Sonys (what my wife has) they are not having a single issue...
    I would like to add my voice to his - I upgraded to 7.6, it stopped working and I get an Audio Config. problem everytime I try to open it. I have tried uninstalling and reinstalling the program but it does not help. What do I need to do to fix this problem ! ! ! ! ?

  • [SOLVED]Xorg.conf, mouse config problem

    The Rapoo M765 mouse can not work properly under normal mouse configuration.
    The mouse goes beyond controll when config as below:
    hacksign@XSign [14:13:13] : ~
    >> cat /etc/X11/xorg.conf.d/50-mouse-acceleration.conf
    #Section "InputClass"
    # Identifier "Mouse2"
    # MatchProduct "RAPOO RAPOO 2.4G Remote Mouse"
    # MatchIsPointer "yes"
    # MatchDevicePath "/dev/input/event*"
    # Driver "mouse"
    # Option "Protocol" "auto"
    # Option "Emulate3Buttons" "no"
    # Option "Buttons" "7"
    # Option "ButtonMapping" "1 2 3 6 7"
    #EndSection
    When there is no any configuration, the mouse can work abnormally. Movement and right/left click work fine, but I can not use scroll wheel,and the "go forward"&"go backward" mouse key can not work too.
    (I know Option "ZAxisMapping" "4 5" is the configuration of scroll wheel emulation.)
    The real problem is 'mouse beyond controll',the cursor goes crazyly on screen ....
    I guess it is something wrong of ButtonMapping option. But when I tried to get button number from command xev,when scroll wheel scrolles, I get something below(the scroll wheel movement is identified as a key event~):
    //left click
    ButtonPress event, serial 34, synthetic NO, window 0x4a00001,
    root 0x264, subw 0x0, time 3766452, (135,143), root:(2287,595),
    state 0x0, button 1, same_screen YES
    ButtonRelease event, serial 34, synthetic NO, window 0x4a00001,
    root 0x264, subw 0x0, time 3766588, (135,143), root:(2287,595),
    state 0x100, button 1, same_screen YES
    //right click
    ButtonPress event, serial 34, synthetic NO, window 0x4a00001,
    root 0x264, subw 0x0, time 3767716, (135,143), root:(2287,595),
    state 0x0, button 3, same_screen YES
    ButtonRelease event, serial 34, synthetic NO, window 0x4a00001,
    root 0x264, subw 0x0, time 3767852, (135,143), root:(2287,595),
    state 0x400, button 3, same_screen YES
    //mouse scroll, identified as keyboard event(?)
    KeyRelease event, serial 34, synthetic NO, window 0x4a00001,
    root 0x264, subw 0x0, time 3769332, (135,143), root:(2287,595),
    state 0x0, keycode 123 (keysym 0x1008ff13, XF86AudioRaiseVolume), same_screen YES,
    XLookupString gives 0 bytes:
    XFilterEvent returns: False
    KeyPress event, serial 34, synthetic NO, window 0x4a00001,
    root 0x264, subw 0x0, time 3769332, (135,143), root:(2287,595),
    state 0x0, keycode 122 (keysym 0x1008ff11, XF86AudioLowerVolume), same_screen YES,
    XLookupString gives 0 bytes:
    XmbLookupString gives 0 bytes:
    XFilterEvent returns: False
    here is some Information(I dont know why the mouse is identified as 'type:KEYBOARD'):
    hacksign@XSign [14:55:03] : ~
    >> xinput
    ⎡ Virtual core pointer id=2 [master pointer (3)]
    ⎜ ↳ Virtual core XTEST pointer id=4 [slave pointer (2)]
    ⎜ ↳ RAPOO RAPOO 2.4G Remote Mouse id=13 [slave pointer (2)]
    ⎜ ↳ SynPS/2 Synaptics TouchPad id=15 [slave pointer (2)]
    ⎜ ↳ TPPS/2 IBM TrackPoint id=16 [slave pointer (2)]
    ⎣ Virtual core keyboard id=3 [master keyboard (2)]
    ↳ Virtual core XTEST keyboard id=5 [slave keyboard (3)]
    ↳ Power Button id=6 [slave keyboard (3)]
    ↳ Video Bus id=7 [slave keyboard (3)]
    ↳ Sleep Button id=8 [slave keyboard (3)]
    ↳ Heng Yu Technology Poker Pro S id=9 [slave keyboard (3)]
    ↳ Heng Yu Technology Poker Pro S id=10 [slave keyboard (3)]
    ↳ Integrated Camera id=11 [slave keyboard (3)]
    ↳ RAPOO RAPOO 2.4G Remote Mouse id=12 [slave keyboard (3)]
    ↳ AT Translated Set 2 keyboard id=14 [slave keyboard (3)]
    ↳ ThinkPad Extra Buttons id=17 [slave keyboard (3)]
    hacksign@XSign [14:55:06] : ~
    >> xinput list-props 13
    Device 'RAPOO RAPOO 2.4G Remote Mouse':
    Device Enabled (142): 1
    Coordinate Transformation Matrix (144): 1.000000, 0.000000, 0.000000, 0.000000, 1.000000, 0.000000, 0.000000, 0.000000, 1.000000
    Device Accel Profile (270): 0
    Device Accel Constant Deceleration (271): 1.000000
    Device Accel Adaptive Deceleration (272): 1.000000
    Device Accel Velocity Scaling (273): 10.000000
    Device Product ID (260): 9390, 8192
    Device Node (261): "/dev/input/event8"
    Evdev Axis Inversion (274): 0, 0
    Evdev Axes Swap (276): 0
    Axis Labels (277): "Rel X" (152), "Rel Y" (153), "Rel Horiz Wheel" (267), "Rel Dial" (268), "Rel Vert Wheel" (269)
    Button Labels (278): "Button Left" (145), "Button Middle" (146), "Button Right" (147), "Button Wheel Up" (148), "Button Wheel Down" (149), "Button Horiz Wheel Left" (150), "Button Horiz Wheel Right" (151), "Button Side" (265), "Button Extra" (266), "Button Unknown" (263), "Button Unknown" (263), "Button Unknown" (263), "Button Unknown" (263)
    Evdev Scrolling Distance (279): 1, 1, 1
    Evdev Middle Button Emulation (280): 0
    Evdev Middle Button Timeout (281): 50
    Evdev Third Button Emulation (282): 0
    Evdev Third Button Emulation Timeout (283): 1000
    Evdev Third Button Emulation Button (284): 3
    Evdev Third Button Emulation Threshold (285): 20
    Evdev Wheel Emulation (286): 0
    Evdev Wheel Emulation Axes (287): 0, 0, 4, 5
    Evdev Wheel Emulation Inertia (288): 10
    Evdev Wheel Emulation Timeout (289): 200
    Evdev Wheel Emulation Button (290): 4
    Evdev Drag Lock Buttons (291): 0
    hacksign@XSign [14:55:14] : ~
    >> grep -i rapoo /var/log/Xorg.0.log
    [ 29.102] (II) config/udev: Adding input device RAPOO RAPOO 2.4G Remote Mouse (/dev/input/event7)
    [ 29.102] (**) RAPOO RAPOO 2.4G Remote Mouse: Applying InputClass "evdev keyboard catchall"
    [ 29.102] (II) Using input driver 'evdev' for 'RAPOO RAPOO 2.4G Remote Mouse'
    [ 29.102] (**) RAPOO RAPOO 2.4G Remote Mouse: always reports core events
    [ 29.102] (**) evdev: RAPOO RAPOO 2.4G Remote Mouse: Device: "/dev/input/event7"
    [ 29.102] (--) evdev: RAPOO RAPOO 2.4G Remote Mouse: Vendor 0x24ae Product 0x2000
    [ 29.102] (--) evdev: RAPOO RAPOO 2.4G Remote Mouse: Found keys
    [ 29.102] (II) evdev: RAPOO RAPOO 2.4G Remote Mouse: Configuring as keyboard
    [ 29.102] (II) XINPUT: Adding extended input device "RAPOO RAPOO 2.4G Remote Mouse" (type: KEYBOARD, id 12)
    [ 29.103] (II) config/udev: Adding input device RAPOO RAPOO 2.4G Remote Mouse (/dev/input/event8)
    [ 29.103] (**) RAPOO RAPOO 2.4G Remote Mouse: Applying InputClass "evdev pointer catchall"
    [ 29.103] (**) RAPOO RAPOO 2.4G Remote Mouse: Applying InputClass "evdev keyboard catchall"
    [ 29.103] (II) Using input driver 'evdev' for 'RAPOO RAPOO 2.4G Remote Mouse'
    [ 29.103] (**) RAPOO RAPOO 2.4G Remote Mouse: always reports core events
    [ 29.103] (**) evdev: RAPOO RAPOO 2.4G Remote Mouse: Device: "/dev/input/event8"
    [ 29.103] (--) evdev: RAPOO RAPOO 2.4G Remote Mouse: Vendor 0x24ae Product 0x2000
    [ 29.103] (--) evdev: RAPOO RAPOO 2.4G Remote Mouse: Found 9 mouse buttons
    [ 29.103] (--) evdev: RAPOO RAPOO 2.4G Remote Mouse: Found scroll wheel(s)
    [ 29.103] (--) evdev: RAPOO RAPOO 2.4G Remote Mouse: Found relative axes
    [ 29.103] (--) evdev: RAPOO RAPOO 2.4G Remote Mouse: Found x and y relative axes
    [ 29.103] (--) evdev: RAPOO RAPOO 2.4G Remote Mouse: Found absolute axes
    [ 29.103] (II) evdev: RAPOO RAPOO 2.4G Remote Mouse: Forcing absolute x/y axes to exist.
    [ 29.103] (--) evdev: RAPOO RAPOO 2.4G Remote Mouse: Found keys
    [ 29.103] (II) evdev: RAPOO RAPOO 2.4G Remote Mouse: Configuring as mouse
    [ 29.103] (II) evdev: RAPOO RAPOO 2.4G Remote Mouse: Configuring as keyboard
    [ 29.103] (II) evdev: RAPOO RAPOO 2.4G Remote Mouse: Adding scrollwheel support
    [ 29.103] (**) evdev: RAPOO RAPOO 2.4G Remote Mouse: YAxisMapping: buttons 4 and 5
    [ 29.103] (**) evdev: RAPOO RAPOO 2.4G Remote Mouse: EmulateWheelButton: 4, EmulateWheelInertia: 10, EmulateWheelTimeout: 200
    [ 29.103] (II) XINPUT: Adding extended input device "RAPOO RAPOO 2.4G Remote Mouse" (type: KEYBOARD, id 13)
    [ 29.104] (II) evdev: RAPOO RAPOO 2.4G Remote Mouse: initialized for relative axes.
    [ 29.104] (WW) evdev: RAPOO RAPOO 2.4G Remote Mouse: ignoring absolute axes.
    [ 29.104] (**) RAPOO RAPOO 2.4G Remote Mouse: (accel) keeping acceleration scheme 1
    [ 29.104] (**) RAPOO RAPOO 2.4G Remote Mouse: (accel) acceleration profile 0
    [ 29.104] (**) RAPOO RAPOO 2.4G Remote Mouse: (accel) acceleration factor: 2.000
    [ 29.104] (**) RAPOO RAPOO 2.4G Remote Mouse: (accel) acceleration threshold: 4
    [ 29.104] (II) config/udev: Adding input device RAPOO RAPOO 2.4G Remote Mouse (/dev/input/mouse0)
    hacksign@XSign [14:59:47] : ~
    >> yaourt -Q|grep -i 'input-'
    local/xf86-input-evdev-trackpoint 2.9.1-1
    extra/xf86-input-keyboard 1.8.0-3 (xorg-drivers xorg)
    extra/xf86-input-mouse 1.9.1-1 (xorg-drivers xorg)
    extra/xf86-input-synaptics 1.8.1-1 (xorg-drivers xorg)
    Last edited by Hacksign (2015-01-14 02:22:51)

    Thanks for reply !
    change Driver 'mouse' to Driver 'evdev',solved cursor goes beyond controll problem.
    but I still can not use scroll button and 'go forward'&'go backward' button.
    (BTW:evdev_drv.so is from local/xf86-input-evdev-trackpoint, and local/xf86-input-evdev-trackpoint package is from AUR)
    I think, maybe something wrong with my button number mapping, but I still can not get scroll button number with 'xev' command....
    below is my configuration:
    hacksign@XSign [17:15:19] : /var/log
    >> cat /etc/X11/xorg.conf.d/50-mouse-acceleration.conf
    Section "InputClass"
    Identifier "Mouse2"
    MatchProduct "RAPOO RAPOO 2.4G Remote Mouse"
    MatchIsPointer "yes"
    MatchDevicePath "/dev/input/event*"
    Driver "evdev"
    Option "Protocol" "auto"
    Option "Emulate3Buttons" "no"
    Option "ZAxisMapping" "4 5"
    Option "Buttons" "9"
    Option "ButtonMapping" "1 2 3 6 7 8 9 4 5"
    EndSection
    and here is Xorg.0.log
    [ 11357.287] (**) RAPOO RAPOO 2.4G Remote Mouse: Applying InputClass "evdev keyboard catchall"
    [ 11357.287] (II) Using input driver 'evdev' for 'RAPOO RAPOO 2.4G Remote Mouse'
    [ 11357.287] (**) RAPOO RAPOO 2.4G Remote Mouse: always reports core events
    [ 11357.287] (**) evdev: RAPOO RAPOO 2.4G Remote Mouse: Device: "/dev/input/event7"
    [ 11357.287] (--) evdev: RAPOO RAPOO 2.4G Remote Mouse: Vendor 0x24ae Product 0x2000
    [ 11357.287] (--) evdev: RAPOO RAPOO 2.4G Remote Mouse: Found keys
    [ 11357.287] (II) evdev: RAPOO RAPOO 2.4G Remote Mouse: Configuring as keyboard
    [ 11357.287] (**) Option "config_info" "udev:/sys/devices/pci0000:00/0000:00:1d.0/usb2/2-1/2-1.2/2-1.2:1.0/0003:24AE:2000.0003/input/input8/event7"
    [ 11357.288] (II) XINPUT: Adding extended input device "RAPOO RAPOO 2.4G Remote Mouse" (type: KEYBOARD, id 12)
    [ 11357.288] (**) Option "xkb_rules" "evdev"
    [ 11357.288] (**) Option "xkb_model" "pc104"
    [ 11357.288] (**) Option "xkb_layout" "us"
    [ 11357.288] (II) config/udev: Adding input device RAPOO RAPOO 2.4G Remote Mouse (/dev/input/event8)
    [ 11357.288] (**) RAPOO RAPOO 2.4G Remote Mouse: Applying InputClass "evdev pointer catchall"
    [ 11357.288] (**) RAPOO RAPOO 2.4G Remote Mouse: Applying InputClass "evdev keyboard catchall"
    [ 11357.288] (**) RAPOO RAPOO 2.4G Remote Mouse: Applying InputClass "Mouse2"
    [ 11357.288] (II) Using input driver 'evdev' for 'RAPOO RAPOO 2.4G Remote Mouse'
    [ 11357.288] (**) RAPOO RAPOO 2.4G Remote Mouse: always reports core events
    [ 11357.288] (**) evdev: RAPOO RAPOO 2.4G Remote Mouse: Device: "/dev/input/event8"
    [ 11357.288] (**) evdev: RAPOO RAPOO 2.4G Remote Mouse: ButtonMapping '1 2 3 6 7 8 9 4 5'
    [ 11357.288] (--) evdev: RAPOO RAPOO 2.4G Remote Mouse: Vendor 0x24ae Product 0x2000
    [ 11357.288] (--) evdev: RAPOO RAPOO 2.4G Remote Mouse: Found 9 mouse buttons
    [ 11357.288] (--) evdev: RAPOO RAPOO 2.4G Remote Mouse: Found scroll wheel(s)
    [ 11357.288] (--) evdev: RAPOO RAPOO 2.4G Remote Mouse: Found relative axes
    [ 11357.288] (--) evdev: RAPOO RAPOO 2.4G Remote Mouse: Found x and y relative axes
    [ 11357.288] (--) evdev: RAPOO RAPOO 2.4G Remote Mouse: Found absolute axes
    [ 11357.288] (II) evdev: RAPOO RAPOO 2.4G Remote Mouse: Forcing absolute x/y axes to exist.
    [ 11357.288] (--) evdev: RAPOO RAPOO 2.4G Remote Mouse: Found keys
    [ 11357.288] (II) evdev: RAPOO RAPOO 2.4G Remote Mouse: Configuring as mouse
    [ 11357.288] (II) evdev: RAPOO RAPOO 2.4G Remote Mouse: Configuring as keyboard
    [ 11357.288] (II) evdev: RAPOO RAPOO 2.4G Remote Mouse: Adding scrollwheel support
    [ 11357.288] (**) Option "Emulate3Buttons" "no"
    [ 11357.288] (**) evdev: RAPOO RAPOO 2.4G Remote Mouse: YAxisMapping: buttons 4 and 5
    [ 11357.288] (**) evdev: RAPOO RAPOO 2.4G Remote Mouse: EmulateWheelButton: 4, EmulateWheelInertia: 10, EmulateWheelTimeout: 200
    [ 11357.288] (**) Option "config_info" "udev:/sys/devices/pci0000:00/0000:00:1d.0/usb2/2-1/2-1.2/2-1.2:1.1/0003:24AE:2000.0004/input/input9/event8"
    [ 11357.288] (II) XINPUT: Adding extended input device "RAPOO RAPOO 2.4G Remote Mouse" (type: KEYBOARD, id 13)
    [ 11357.288] (**) Option "xkb_rules" "evdev"
    [ 11357.288] (**) Option "xkb_model" "pc104"
    [ 11357.288] (**) Option "xkb_layout" "us"
    [ 11357.288] (II) evdev: RAPOO RAPOO 2.4G Remote Mouse: initialized for relative axes.
    [ 11357.288] (WW) evdev: RAPOO RAPOO 2.4G Remote Mouse: ignoring absolute axes.
    [ 11357.289] (**) RAPOO RAPOO 2.4G Remote Mouse: (accel) keeping acceleration scheme 1
    [ 11357.289] (**) RAPOO RAPOO 2.4G Remote Mouse: (accel) acceleration profile 0
    [ 11357.289] (**) RAPOO RAPOO 2.4G Remote Mouse: (accel) acceleration factor: 2.000
    [ 11357.289] (**) RAPOO RAPOO 2.4G Remote Mouse: (accel) acceleration threshold: 4
    [ 11357.289] (II) config/udev: Adding input device RAPOO RAPOO 2.4G Remote Mouse (/dev/input/mouse0)
    [ 11357.289] (II) No input driver specified, ignoring this device.
    [ 11357.289] (II) This device may have been added with another device file.
    olive wrote:In the config file you mentioned, all is commented; do you mean that you have problems when you have uncommented it? You should not use the mouse driver (old deprecated driver) but evdev. Try to remove xf86-input-mouse and xf86-input-keyboard (same as before, this is deprecated and handled by evdev) and remove also a "joystick" driver if you have it (I have had problem with it conflicting with the evdev driver).
    Last edited by Hacksign (2015-01-13 09:27:06)

  • "Speed bump" problem: when previewing on the iPad, the first page of each new chapter or section sticks and loads slowly.  How can I fix it?

    I am building a book with text and photographs in iBooks Author, basing the design on my publisher's layout for the hard copy version.  Whenever I introduce a new section or chapter, I hit a "speed bump" when previewing on the iPad.  As you read, the first page of the new chapter or section is very hard to turn and sticks as it loads.  Within each section the pages flow very easily, but when you reach the next section you hit another speed bump. I have experimented with many possible solutions to no avail.  It does not seem to matter whether the new section has images or just text; the speed bump occurs regardless.

    Joel Pickford wrote:
    However, I am finding that using fewer sections with more content in them minimizes the problem (i.e. fewer section-transions means fewer speed bumps).  This is contarary to the support page's suggestion of keeping chapters and sections smaller.  I am not having any problem within each section, even with lots of full page photos.
    That recommendation was made, presumably, to reduce the length of the delay for each chapter. More content in the chapter means more delay when changing chapters. Of course, if you have lots of little chapters, the delay can still be annoying because, even if only four or five pages in a chapter, the delay is still noticable. Just pick something that works for your book and don't worry too much about the delay. Your readers will be familiar with it if they've seen more than one IBA book.
    Will the choice of color space, s-rgb or Adobe rgb 1998, affect file size?
    Should I try to compress them more- say, level 5 or level 4 in Save For Web?
    Should I size the images for the iPad 2 instead of the iPad 3 retina display, since there are more 2s out there?
    Which color space you use does not affect file size. Apple recommend to use sRGB, so I would stick with that. As to compression and sizing, only you can decide. Try and borrow an iPad 2 to make a judgement at what level of compression and resolution you think the images start too look bad. Your high-rez images for the new iPad will be down-sampled for display on the older models, which will introduce additional artifacts.
    For my book, I simply used images at 1024 x 768 resolution. When viewed on a new iPad, they look just fine. The lower resolution is basically unnoticeable (at least for my purposes). You can view a sample of my book here: "Djembe Construction: A Comprehensive Guide". If you think the images there are good enough for your purposes, you could down-size your images to half their resolution, which will reduce file size about around a factor of three.
    Michi.

  • ATI Prop. Drivers - config problem:

    Hey all,
    First off, I'm a new Arch user, coming off a basic Gentoo install - like the forums here - everyone seems very helpful!
    Pleased with how setting up Arch is going - basic desktop install.  I'm having problems though with the ATI drivers.  I'm trying to get the proprietary driverrs working, and having problems running the aticonfig program.  Here's the problem:
    [root@myhost X11]# aticonfig --initial --input=/etc/X11/xorg.conf
    Uninitialised file found, configuring.
    Using /etc/X11/xorg.conf
    Saved back-up to /etc/X11/xorg.conf.original-0
    *** glibc detected *** aticonfig: munmap_chunk(): invalid pointer: 0xbfe10c25 ***
    Then it prints a backtrace and memory map and aborts:
    ======= Backtrace: =========
    /lib/libc.so.6[0xb7d085e6]
    aticonfig[0x805c5c7]
    aticonfig[0x805c875]
    aticonfig[0x8054528]
    aticonfig[0x804985e]
    aticonfig[0x80496cb]
    /lib/libc.so.6(__libc_start_main+0xe0)[0xb7cb8970]
    aticonfig[0x8049601]
    ======= Memory map: ========
    08048000-08067000 r-xp 00000000 08:13 111078 /usr/bin/aticonfig
    08067000-0806a000 rw-p 0001e000 08:13 111078 /usr/bin/aticonfig
    0806a000-0808b000 rw-p 0806a000 00:00 0 [heap]
    b7c95000-b7c96000 rw-p b7c95000 00:00 0
    b7c96000-b7c98000 r-xp 00000000 08:13 2366 /lib/libdl-2.6.so
    b7c98000-b7c9a000 rw-p 00001000 08:13 2366 /lib/libdl-2.6.so
    b7c9a000-b7c9e000 r-xp 00000000 08:13 32630 /usr/lib/libXdmcp.so.6.0.0
    b7c9e000-b7c9f000 rw-p 00003000 08:13 32630 /usr/lib/libXdmcp.so.6.0.0
    b7c9f000-b7ca1000 r-xp 00000000 08:13 32611 /usr/lib/libXau.so.6.0.0
    b7ca1000-b7ca2000 rw-p 00001000 08:13 32611 /usr/lib/libXau.so.6.0.0
    b7ca2000-b7ca3000 rw-p b7ca2000 00:00 0
    b7ca3000-b7dcd000 r-xp 00000000 08:13 2355 /lib/libc-2.6.so
    b7dcd000-b7dce000 r--p 0012a000 08:13 2355 /lib/libc-2.6.so
    b7dce000-b7dd0000 rw-p 0012b000 08:13 2355 /lib/libc-2.6.so
    b7dd0000-b7dd3000 rw-p b7dd0000 00:00 0
    b7dd3000-b7df5000 r-xp 00000000 08:13 2344 /lib/libm-2.6.so
    b7df5000-b7df7000 rw-p 00021000 08:13 2344 /lib/libm-2.6.so
    b7df7000-b7edf000 r-xp 00000000 08:13 32950 /usr/lib/libX11.so.6.2.0
    b7edf000-b7ee3000 rw-p 000e7000 08:13 32950 /usr/lib/libX11.so.6.2.0
    b7ee3000-b7ef0000 r-xp 00000000 08:13 33724 /usr/lib/libXext.so.6.4.0
    b7ef0000-b7ef1000 rw-p 0000c000 08:13 33724 /usr/lib/libXext.so.6.4.0
    b7ef1000-b7ef8000 r-xp 00000000 08:13 34374 /usr/lib/libXrender.so.1.3.0
    b7ef8000-b7ef9000 rw-p 00006000 08:13 34374 /usr/lib/libXrender.so.1.3.0
    b7ef9000-b7efe000 r-xp 00000000 08:13 35188 /usr/lib/libXrandr.so.2.1.0
    b7efe000-b7eff000 rw-p 00004000 08:13 35188 /usr/lib/libXrandr.so.2.1.0
    b7eff000-b7f00000 rw-p b7eff000 00:00 0
    b7f0a000-b7f14000 r-xp 00000000 08:13 8375 /usr/lib/libgcc_s.so.1
    b7f14000-b7f15000 rw-p 00009000 08:13 8375 /usr/lib/libgcc_s.so.1
    b7f15000-b7f16000 rw-p b7f15000 00:00 0
    b7f16000-b7f17000 r-xp b7f16000 00:00 0 [vdso]
    b7f17000-b7f31000 r-xp 00000000 08:13 2328 /lib/ld-2.6.so
    b7f31000-b7f32000 r--p 00019000 08:13 2328 /lib/ld-2.6.so
    b7f32000-b7f33000 rw-p 0001a000 08:13 2328 /lib/ld-2.6.so
    bfdfc000-bfe12000 rw-p bfdfc000 00:00 0 [stack]
    Aborted
    I haven't been able to find much on this invalid pointer problem - any suggestions?  Below is my original xorg.conf:
    Regards,
    Mike
    # File generated by xorgconfig.
    # Copyright 2004 The X.Org Foundation
    # Permission is hereby granted, free of charge, to any person obtaining a
    # copy of this software and associated documentation files (the "Software"),
    # to deal in the Software without restriction, including without limitation
    # the rights to use, copy, modify, merge, publish, distribute, sublicense,
    # and/or sell copies of the Software, and to permit persons to whom the
    # Software is furnished to do so, subject to the following conditions:
    # The above copyright notice and this permission notice shall be included in
    # all copies or substantial portions of the Software.
    # THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR
    # IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY,
    # FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL
    # The X.Org Foundation BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY,
    # WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF
    # OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE
    # SOFTWARE.
    # Except as contained in this notice, the name of The X.Org Foundation shall
    # not be used in advertising or otherwise to promote the sale, use or other
    # dealings in this Software without prior written authorization from
    # The X.Org Foundation.
    # Refer to the xorg.conf(5) man page for details about the format of
    # this file.
    # Module section -- this section is used to specify
    # which dynamically loadable modules to load.
    Section "Module"
    # This loads the DBE extension module.
    Load "dbe" # Double buffer extension
    # This loads the miscellaneous extensions module, and disables
    # initialisation of the XFree86-DGA extension within that module.
    SubSection "extmod"
    Option "omit xfree86-dga" # don't initialise the DGA extension
    EndSubSection
    # This loads the font modules
    # Load "type1"
    Load "freetype"
    # Load "xtt"
    # This loads the GLX module
    # Load "glx"
    # This loads the DRI module
    # Load "dri"
    EndSection
    # Files section. This allows default font and rgb paths to be set
    Section "Files"
    # The location of the RGB database. Note, this is the name of the
    # file minus the extension (like ".txt" or ".db"). There is normally
    # no need to change the default.
    # RgbPath "/usr/share/X11/rgb"
    # Multiple FontPath entries are allowed (which are concatenated together),
    # as well as specifying multiple comma-separated entries in one FontPath
    # command (or a combination of both methods)
    FontPath "/usr/share/fonts/misc"
    FontPath "/usr/share/fonts/100dpi:unscaled"
    FontPath "/usr/share/fonts/75dpi:unscaled"
    # FontPath "/usr/share/fonts/TTF"
    # FontPath "/usr/share/fonts/Type1"
    # FontPath "/usr/lib/X11/fonts/local/"
    # FontPath "/usr/lib/X11/fonts/misc/"
    # FontPath "/usr/lib/X11/fonts/75dpi/:unscaled"
    # FontPath "/usr/lib/X11/fonts/100dpi/:unscaled"
    # FontPath "/usr/lib/X11/fonts/Speedo/"
    # FontPath "/usr/lib/X11/fonts/Type1/"
    # FontPath "/usr/lib/X11/fonts/TrueType/"
    # FontPath "/usr/lib/X11/fonts/freefont/"
    # FontPath "/usr/lib/X11/fonts/75dpi/"
    # FontPath "/usr/lib/X11/fonts/100dpi/"
    # The module search path. The default path is shown here.
    # ModulePath "/usr/lib/modules"
    EndSection
    # Server flags section.
    Section "ServerFlags"
    # Uncomment this to cause a core dump at the spot where a signal is
    # received. This may leave the console in an unusable state, but may
    # provide a better stack trace in the core dump to aid in debugging
    # Option "NoTrapSignals"
    # Uncomment this to disable the <Ctrl><Alt><Fn> VT switch sequence
    # (where n is 1 through 12). This allows clients to receive these key
    # events.
    # Option "DontVTSwitch"
    # Uncomment this to disable the <Ctrl><Alt><BS> server abort sequence
    # This allows clients to receive this key event.
    # Option "DontZap"
    # Uncomment this to disable the <Ctrl><Alt><KP_+>/<KP_-> mode switching
    # sequences. This allows clients to receive these key events.
    # Option "Dont Zoom"
    # Uncomment this to disable tuning with the xvidtune client. With
    # it the client can still run and fetch card and monitor attributes,
    # but it will not be allowed to change them. If it tries it will
    # receive a protocol error.
    # Option "DisableVidModeExtension"
    # Uncomment this to enable the use of a non-local xvidtune client.
    # Option "AllowNonLocalXvidtune"
    # Uncomment this to disable dynamically modifying the input device
    # (mouse and keyboard) settings.
    # Option "DisableModInDev"
    # Uncomment this to enable the use of a non-local client to
    # change the keyboard or mouse settings (currently only xset).
    # Option "AllowNonLocalModInDev"
    EndSection
    # Input devices
    # Core keyboard's InputDevice section
    Section "InputDevice"
    Identifier "Keyboard1"
    Driver "kbd"
    # For most OSs the protocol can be omitted (it defaults to "Standard").
    # When using XQUEUE (only for SVR3 and SVR4, but not Solaris),
    # uncomment the following line.
    # Option "Protocol" "Xqueue"
    Option "AutoRepeat" "500 30"
    # Specify which keyboard LEDs can be user-controlled (eg, with xset(1))
    # Option "Xleds" "1 2 3"
    # Option "LeftAlt" "Meta"
    # Option "RightAlt" "ModeShift"
    # To customise the XKB settings to suit your keyboard, modify the
    # lines below (which are the defaults). For example, for a non-U.S.
    # keyboard, you will probably want to use:
    # Option "XkbModel" "pc105"
    # If you have a US Microsoft Natural keyboard, you can use:
    # Option "XkbModel" "microsoft"
    # Then to change the language, change the Layout setting.
    # For example, a german layout can be obtained with:
    # Option "XkbLayout" "de"
    # or:
    # Option "XkbLayout" "de"
    # Option "XkbVariant" "nodeadkeys"
    # If you'd like to switch the positions of your capslock and
    # control keys, use:
    # Option "XkbOptions" "ctrl:swapcaps"
    # These are the default XKB settings for Xorg
    # Option "XkbRules" "xorg"
    # Option "XkbModel" "pc105"
    # Option "XkbLayout" "us"
    # Option "XkbVariant" ""
    # Option "XkbOptions" ""
    # Option "XkbDisable"
    Option "XkbRules" "xorg"
    Option "XkbModel" "pc104"
    Option "XkbLayout" "us"
    EndSection
    # Core Pointer's InputDevice section
    Section "InputDevice"
    # Identifier and driver
    Identifier "Mouse1"
    Driver "mouse"
    Option "Protocol" "Auto" # Auto detect
    Option "Device" "/dev/input/mice"
    # When using XQUEUE, comment out the above two lines, and uncomment
    # the following line.
    # Option "Protocol" "Xqueue"
    # Mouse-speed setting for PS/2 mouse.
    # Option "Resolution" "256"
    # Baudrate and SampleRate are only for some Logitech mice. In
    # almost every case these lines should be omitted.
    # Option "BaudRate" "9600"
    # Option "SampleRate" "150"
    # Mouse wheel mapping. Default is to map vertical wheel to buttons 4 & 5,
    # horizontal wheel to buttons 6 & 7. Change if your mouse has more than
    # 3 buttons and you need to map the wheel to different button ids to avoid
    # conflicts.
    Option "ZAxisMapping" "4 5 6 7"
    # Emulate3Buttons is an option for 2-button mice
    # Emulate3Timeout is the timeout in milliseconds (default is 50ms)
    # Option "Emulate3Buttons"
    # Option "Emulate3Timeout" "50"
    # ChordMiddle is an option for some 3-button Logitech mice
    # Option "ChordMiddle"
    EndSection
    # Other input device sections
    # this is optional and is required only if you
    # are using extended input devices. This is for example only. Refer
    # to the xorg.conf man page for a description of the options.
    # Section "InputDevice"
    # Identifier "Mouse2"
    # Driver "mouse"
    # Option "Protocol" "MouseMan"
    # Option "Device" "/dev/mouse2"
    # EndSection
    # Section "InputDevice"
    # Identifier "spaceball"
    # Driver "magellan"
    # Option "Device" "/dev/cua0"
    # EndSection
    # Section "InputDevice"
    # Identifier "spaceball2"
    # Driver "spaceorb"
    # Option "Device" "/dev/cua0"
    # EndSection
    # Section "InputDevice"
    # Identifier "touchscreen0"
    # Driver "microtouch"
    # Option "Device" "/dev/ttyS0"
    # Option "MinX" "1412"
    # Option "MaxX" "15184"
    # Option "MinY" "15372"
    # Option "MaxY" "1230"
    # Option "ScreenNumber" "0"
    # Option "ReportingMode" "Scaled"
    # Option "ButtonNumber" "1"
    # Option "SendCoreEvents"
    # EndSection
    # Section "InputDevice"
    # Identifier "touchscreen1"
    # Driver "elo2300"
    # Option "Device" "/dev/ttyS0"
    # Option "MinX" "231"
    # Option "MaxX" "3868"
    # Option "MinY" "3858"
    # Option "MaxY" "272"
    # Option "ScreenNumber" "0"
    # Option "ReportingMode" "Scaled"
    # Option "ButtonThreshold" "17"
    # Option "ButtonNumber" "1"
    # Option "SendCoreEvents"
    # EndSection
    # Monitor section
    # Any number of monitor sections may be present
    Section "Monitor"
    Identifier "My Monitor"
    # HorizSync is in kHz unless units are specified.
    # HorizSync may be a comma separated list of discrete values, or a
    # comma separated list of ranges of values.
    # NOTE: THE VALUES HERE ARE EXAMPLES ONLY. REFER TO YOUR MONITOR'S
    # USER MANUAL FOR THE CORRECT NUMBERS.
    HorizSync 31.5 - 64.3
    # HorizSync 30-64 # multisync
    # HorizSync 31.5, 35.2 # multiple fixed sync frequencies
    # HorizSync 15-25, 30-50 # multiple ranges of sync frequencies
    # VertRefresh is in Hz unless units are specified.
    # VertRefresh may be a comma separated list of discrete values, or a
    # comma separated list of ranges of values.
    # NOTE: THE VALUES HERE ARE EXAMPLES ONLY. REFER TO YOUR MONITOR'S
    # USER MANUAL FOR THE CORRECT NUMBERS.
    VertRefresh 50-70
    EndSection
    # Graphics device section
    # Any number of graphics device sections may be present
    # Standard VGA Device:
    Section "Device"
    Identifier "Standard VGA"
    VendorName "Unknown"
    BoardName "Unknown"
    # The chipset line is optional in most cases. It can be used to override
    # the driver's chipset detection, and should not normally be specified.
    # Chipset "generic"
    # The Driver line must be present. When using run-time loadable driver
    # modules, this line instructs the server to load the specified driver
    # module. Even when not using loadable driver modules, this line
    # indicates which driver should interpret the information in this section.
    Driver "vga"
    # The BusID line is used to specify which of possibly multiple devices
    # this section is intended for. When this line isn't present, a device
    # section can only match up with the primary video device. For PCI
    # devices a line like the following could be used. This line should not
    # normally be included unless there is more than one video device
    # intalled.
    # BusID "PCI:0:10:0"
    # VideoRam 256
    # Clocks 25.2 28.3
    EndSection
    # Device configured by xorgconfig:
    Section "Device"
    Identifier "* Generic VESA compatible"
    Driver "vesa"
    #VideoRam 131072
    # Insert Clocks lines here if appropriate
    EndSection
    # Screen sections
    # Any number of screen sections may be present. Each describes
    # the configuration of a single screen. A single specific screen section
    # may be specified from the X server command line with the "-screen"
    # option.
    Section "Screen"
    Identifier "Screen 1"
    Device "* Generic VESA compatible"
    Monitor "My Monitor"
    DefaultDepth 24
    Subsection "Display"
    Depth 8
    Modes "1280x1024" "1024x768" "800x600" "640x480"
    ViewPort 0 0
    EndSubsection
    Subsection "Display"
    Depth 16
    Modes "1280x1024" "1024x768" "800x600" "640x480"
    ViewPort 0 0
    EndSubsection
    Subsection "Display"
    Depth 24
    Modes "1280x1024" "1024x768" "800x600" "640x480"
    ViewPort 0 0
    EndSubsection
    EndSection
    # ServerLayout sections.
    # Any number of ServerLayout sections may be present. Each describes
    # the way multiple screens are organised. A specific ServerLayout
    # section may be specified from the X server command line with the
    # "-layout" option. In the absence of this, the first section is used.
    # When now ServerLayout section is present, the first Screen section
    # is used alone.
    Section "ServerLayout"
    # The Identifier line must be present
    Identifier "Simple Layout"
    # Each Screen line specifies a Screen section name, and optionally
    # the relative position of other screens. The four names after
    # primary screen name are the screens to the top, bottom, left and right
    # of the primary screen. In this example, screen 2 is located to the
    # right of screen 1.
    Screen "Screen 1"
    # Each InputDevice line specifies an InputDevice section name and
    # optionally some options to specify the way the device is to be
    # used. Those options include "CorePointer", "CoreKeyboard" and
    # "SendCoreEvents".
    InputDevice "Mouse1" "CorePointer"
    InputDevice "Keyboard1" "CoreKeyboard"
    EndSection
    # Section "DRI"
    # Mode 0666
    # EndSection

    Tried hwd -xa, here's the xorg.conf it generated.  Didn't work - went to black, blank screen when it went to KDM at startup.  Thoughts?  Did I do something wrong changing the driver?  I modprobe'd fglrx, I get no output - normal?
    Section "ServerLayout"
    Identifier "Xorg Configured"
    Screen 0 "Screen0" 0 0
    InputDevice "Keyboard0" "CoreKeyboard"
    InputDevice "PS/2 Mouse" "CorePointer"
    # Serial Mouse not detected
    # USB Mouse not detected
    EndSection
    Section "ServerFlags"
    Option "AllowMouseOpenFail" "true"
    EndSection
    Section "Files"
    RgbPath "/usr/share/X11/rgb"
    ModulePath "/usr/lib/xorg/modules"
    FontPath "/usr/share/fonts/misc:unscaled"
    FontPath "/usr/share/fonts/misc"
    FontPath "/usr/share/fonts/75dpi:unscaled"
    FontPath "/usr/share/fonts/75dpi"
    FontPath "/usr/share/fonts/100dpi:unscaled"
    FontPath "/usr/share/fonts/100dpi"
    FontPath "/usr/share/fonts/PEX"
    # Additional fonts: Locale, Gimp, TTF...
    FontPath "/usr/share/fonts/cyrillic"
    # FontPath "/usr/share/lib/X11/fonts/latin2/75dpi"
    # FontPath "/usr/share/lib/X11/fonts/latin2/100dpi"
    # True type and type1 fonts are also handled via xftlib, see /etc/X11/XftConfig!
    FontPath "/usr/share/fonts/Type1"
    FontPath "/usr/share/fonts/ttf/western"
    FontPath "/usr/share/fonts/ttf/decoratives"
    FontPath "/usr/share/fonts/truetype"
    FontPath "/usr/share/fonts/truetype/openoffice"
    FontPath "/usr/share/fonts/truetype/ttf-bitstream-vera"
    FontPath "/usr/share/fonts/latex-ttf-fonts"
    FontPath "/usr/share/fonts/defoma/CID"
    FontPath "/usr/share/fonts/defoma/TrueType"
    EndSection
    Section "Module"
    Load "ddc" # ddc probing of monitor
    Load "dbe"
    Load "dri"
    Load "extmod"
    Load "glx"
    Load "bitmap" # bitmap-fonts
    Load "type1"
    Load "freetype"
    Load "record"
    EndSection
    Section "InputDevice"
    Identifier "Keyboard0"
    Driver "keyboard"
    Option "CoreKeyboard"
    Option "XkbRules" "xorg"
    Option "XkbModel" "pc105"
    Option "XkbLayout" ""
    Option "XkbVariant" ""
    EndSection
    Section "InputDevice"
    Identifier "Serial Mouse"
    Driver "mouse"
    Option "Protocol" "Microsoft"
    Option "Device" "/dev/ttyS0"
    Option "Emulate3Buttons" "true"
    Option "Emulate3Timeout" "70"
    Option "SendCoreEvents" "true"
    EndSection
    Section "InputDevice"
    Identifier "PS/2 Mouse"
    Driver "mouse"
    Option "Protocol" "auto"
    Option "ZAxisMapping" "4 5"
    Option "Device" "/dev/psaux"
    Option "Emulate3Buttons" "true"
    Option "Emulate3Timeout" "70"
    Option "SendCoreEvents" "true"
    EndSection
    Section "InputDevice"
    Identifier "USB Mouse"
    Driver "mouse"
    Option "Device" "/dev/input/mice"
    Option "SendCoreEvents" "true"
    Option "Protocol" "IMPS/2"
    Option "ZAxisMapping" "4 5"
    Option "Buttons" "5"
    EndSection
    # Auto-generated by Archie mkxcfg
    Section "Monitor"
    Identifier "Monitor0"
    Option "DPMS" "true"
    # HorizSync 28.0 - 78.0 # Warning: This may fry very old Monitors
    HorizSync 28.0 - 96.0 # Warning: This may fry old Monitors
    VertRefresh 50.0 - 75.0 # Very conservative. May flicker.
    # VertRefresh 50.0 - 62.0 # Extreme conservative. Will flicker. TFT default.
    # Default modes distilled from
    # "VESA and Industry Standards and Guide for Computer Display Monitor
    # Timing", version 1.0, revision 0.8, adopted September 17, 1998.
    # $XFree86: xc/programs/Xserver/hw/xfree86/etc/vesamodes,v 1.4 1999/11/18 16:52:17 tsi Exp $
    # 640x350 @ 85Hz (VESA) hsync: 37.9kHz
    ModeLine "640x350" 31.5 640 672 736 832 350 382 385 445 +hsync -vsync
    # 640x400 @ 85Hz (VESA) hsync: 37.9kHz
    ModeLine "640x400" 31.5 640 672 736 832 400 401 404 445 -hsync +vsync
    # 720x400 @ 85Hz (VESA) hsync: 37.9kHz
    ModeLine "720x400" 35.5 720 756 828 936 400 401 404 446 -hsync +vsync
    # 640x480 @ 60Hz (Industry standard) hsync: 31.5kHz
    ModeLine "640x480" 25.2 640 656 752 800 480 490 492 525 -hsync -vsync
    # 640x480 @ 72Hz (VESA) hsync: 37.9kHz
    ModeLine "640x480" 31.5 640 664 704 832 480 489 491 520 -hsync -vsync
    # 640x480 @ 75Hz (VESA) hsync: 37.5kHz
    ModeLine "640x480" 31.5 640 656 720 840 480 481 484 500 -hsync -vsync
    # 640x480 @ 85Hz (VESA) hsync: 43.3kHz
    ModeLine "640x480" 36.0 640 696 752 832 480 481 484 509 -hsync -vsync
    # 800x600 @ 56Hz (VESA) hsync: 35.2kHz
    ModeLine "800x600" 36.0 800 824 896 1024 600 601 603 625 +hsync +vsync
    # 800x600 @ 60Hz (VESA) hsync: 37.9kHz
    ModeLine "800x600" 40.0 800 840 968 1056 600 601 605 628 +hsync +vsync
    # 800x600 @ 72Hz (VESA) hsync: 48.1kHz
    ModeLine "800x600" 50.0 800 856 976 1040 600 637 643 666 +hsync +vsync
    # 800x600 @ 75Hz (VESA) hsync: 46.9kHz
    ModeLine "800x600" 49.5 800 816 896 1056 600 601 604 625 +hsync +vsync
    # 800x600 @ 85Hz (VESA) hsync: 53.7kHz
    ModeLine "800x600" 56.3 800 832 896 1048 600 601 604 631 +hsync +vsync
    # 1024x768i @ 43Hz (industry standard) hsync: 35.5kHz
    ModeLine "1024x768" 44.9 1024 1032 1208 1264 768 768 776 817 +hsync +vsync Interlace
    # 1024x768 @ 60Hz (VESA) hsync: 48.4kHz
    ModeLine "1024x768" 65.0 1024 1048 1184 1344 768 771 777 806 -hsync -vsync
    # 1024x768 @ 70Hz (VESA) hsync: 56.5kHz
    ModeLine "1024x768" 75.0 1024 1048 1184 1328 768 771 777 806 -hsync -vsync
    # 1024x768 @ 75Hz (VESA) hsync: 60.0kHz
    ModeLine "1024x768" 78.8 1024 1040 1136 1312 768 769 772 800 +hsync +vsync
    # 1024x768 @ 85Hz (VESA) hsync: 68.7kHz
    ModeLine "1024x768" 94.5 1024 1072 1168 1376 768 769 772 808 +hsync +vsync
    # 1152x864 @ 75Hz (VESA) hsync: 67.5kHz
    ModeLine "1152x864" 108.0 1152 1216 1344 1600 864 865 868 900 +hsync +vsync
    # 1280x960 @ 60Hz (VESA) hsync: 60.0kHz
    ModeLine "1280x960" 108.0 1280 1376 1488 1800 960 961 964 1000 +hsync +vsync
    # 1280x960 @ 85Hz (VESA) hsync: 85.9kHz
    ModeLine "1280x960" 148.5 1280 1344 1504 1728 960 961 964 1011 +hsync +vsync
    # 1280x1024 @ 60Hz (VESA) hsync: 64.0kHz
    ModeLine "1280x1024" 108.0 1280 1328 1440 1688 1024 1025 1028 1066 +hsync +vsync
    # 1280x1024 @ 75Hz (VESA) hsync: 80.0kHz
    ModeLine "1280x1024" 135.0 1280 1296 1440 1688 1024 1025 1028 1066 +hsync +vsync
    # 1280x1024 @ 85Hz (VESA) hsync: 91.1kHz
    ModeLine "1280x1024" 157.5 1280 1344 1504 1728 1024 1025 1028 1072 +hsync +vsync
    # 1600x1200 @ 60Hz (VESA) hsync: 75.0kHz
    ModeLine "1600x1200" 162.0 1600 1664 1856 2160 1200 1201 1204 1250 +hsync +vsync
    # 1600x1200 @ 65Hz (VESA) hsync: 81.3kHz
    ModeLine "1600x1200" 175.5 1600 1664 1856 2160 1200 1201 1204 1250 +hsync +vsync
    # 1600x1200 @ 70Hz (VESA) hsync: 87.5kHz
    ModeLine "1600x1200" 189.0 1600 1664 1856 2160 1200 1201 1204 1250 +hsync +vsync
    # 1600x1200 @ 75Hz (VESA) hsync: 93.8kHz
    ModeLine "1600x1200" 202.5 1600 1664 1856 2160 1200 1201 1204 1250 +hsync +vsync
    # 1600x1200 @ 85Hz (VESA) hsync: 106.3kHz
    ModeLine "1600x1200" 229.5 1600 1664 1856 2160 1200 1201 1204 1250 +hsync +vsync
    # 1792x1344 @ 60Hz (VESA) hsync: 83.6kHz
    ModeLine "1792x1344" 204.8 1792 1920 2120 2448 1344 1345 1348 1394 -hsync +vsync
    # 1792x1344 @ 75Hz (VESA) hsync: 106.3kHz
    ModeLine "1792x1344" 261.0 1792 1888 2104 2456 1344 1345 1348 1417 -hsync +vsync
    # 1856x1392 @ 60Hz (VESA) hsync: 86.3kHz
    ModeLine "1856x1392" 218.3 1856 1952 2176 2528 1392 1393 1396 1439 -hsync +vsync
    # 1856x1392 @ 75Hz (VESA) hsync: 112.5kHz
    ModeLine "1856x1392" 288.0 1856 1984 2208 2560 1392 1393 1396 1500 -hsync +vsync
    # 1920x1440 @ 60Hz (VESA) hsync: 90.0kHz
    ModeLine "1920x1440" 234.0 1920 2048 2256 2600 1440 1441 1444 1500 -hsync +vsync
    # 1920x1440 @ 75Hz (VESA) hsync: 112.5kHz
    ModeLine "1920x1440" 297.0 1920 2064 2288 2640 1440 1441 1444 1500 -hsync +vsync
    # Additional modelines
    ModeLine "1800x1440" 230 1800 1896 2088 2392 1440 1441 1444 1490 +HSync +VSync
    ModeLine "1800x1440" 250 1800 1896 2088 2392 1440 1441 1444 1490 +HSync +VSync
    # Extended modelines with GTF timings
    # 640x480 @ 100.00 Hz (GTF) hsync: 50.90 kHz; pclk: 43.16 MHz
    ModeLine "640x480" 43.16 640 680 744 848 480 481 484 509 -HSync +Vsync
    # 768x576 @ 60.00 Hz (GTF) hsync: 35.82 kHz; pclk: 34.96 MHz
    ModeLine "768x576" 34.96 768 792 872 976 576 577 580 597 -HSync +Vsync
    # 768x576 @ 72.00 Hz (GTF) hsync: 43.27 kHz; pclk: 42.93 MHz
    ModeLine "768x576" 42.93 768 800 880 992 576 577 580 601 -HSync +Vsync
    # 768x576 @ 75.00 Hz (GTF) hsync: 45.15 kHz; pclk: 45.51 MHz
    ModeLine "768x576" 45.51 768 808 888 1008 576 577 580 602 -HSync +Vsync
    # 768x576 @ 85.00 Hz (GTF) hsync: 51.42 kHz; pclk: 51.84 MHz
    ModeLine "768x576" 51.84 768 808 888 1008 576 577 580 605 -HSync +Vsync
    # 768x576 @ 100.00 Hz (GTF) hsync: 61.10 kHz; pclk: 62.57 MHz
    ModeLine "768x576" 62.57 768 816 896 1024 576 577 580 611 -HSync +Vsync
    # 800x600 @ 100.00 Hz (GTF) hsync: 63.60 kHz; pclk: 68.18 MHz
    ModeLine "800x600" 68.18 800 848 936 1072 600 601 604 636 -HSync +Vsync
    # 1024x768 @ 100.00 Hz (GTF) hsync: 81.40 kHz; pclk: 113.31 MHz
    ModeLine "1024x768" 113.31 1024 1096 1208 1392 768 769 772 814 -HSync +Vsync
    # 1152x864 @ 60.00 Hz (GTF) hsync: 53.70 kHz; pclk: 81.62 MHz
    ModeLine "1152x864" 81.62 1152 1216 1336 1520 864 865 868 895 -HSync +Vsync
    # 1152x864 @ 85.00 Hz (GTF) hsync: 77.10 kHz; pclk: 119.65 MHz
    ModeLine "1152x864" 119.65 1152 1224 1352 1552 864 865 868 907 -HSync +Vsync
    # 1152x864 @ 100.00 Hz (GTF) hsync: 91.50 kHz; pclk: 143.47 MHz
    ModeLine "1152x864" 143.47 1152 1232 1360 1568 864 865 868 915 -HSync +Vsync
    # 1280x960 @ 72.00 Hz (GTF) hsync: 72.07 kHz; pclk: 124.54 MHz
    ModeLine "1280x960" 124.54 1280 1368 1504 1728 960 961 964 1001 -HSync +Vsync
    # 1280x960 @ 75.00 Hz (GTF) hsync: 75.15 kHz; pclk: 129.86 MHz
    ModeLine "1280x960" 129.86 1280 1368 1504 1728 960 961 964 1002 -HSync +Vsync
    # 1280x960 @ 100.00 Hz (GTF) hsync: 101.70 kHz; pclk: 178.99 MHz
    ModeLine "1280x960" 178.99 1280 1376 1520 1760 960 961 964 1017 -HSync +Vsync
    # 1280x1024 @ 100.00 Hz (GTF) hsync: 108.50 kHz; pclk: 190.96 MHz
    ModeLine "1280x1024" 190.96 1280 1376 1520 1760 1024 1025 1028 1085 -HSync +Vsync
    # 1400x1050 @ 60.00 Hz (GTF) hsync: 65.22 kHz; pclk: 122.61 MHz
    ModeLine "1400x1050" 122.61 1400 1488 1640 1880 1050 1051 1054 1087 -HSync +Vsync
    # 1400x1050 @ 72.00 Hz (GTF) hsync: 78.77 kHz; pclk: 149.34 MHz
    ModeLine "1400x1050" 149.34 1400 1496 1648 1896 1050 1051 1054 1094 -HSync +Vsync
    # 1400x1050 @ 75.00 Hz (GTF) hsync: 82.20 kHz; pclk: 155.85 MHz
    ModeLine "1400x1050" 155.85 1400 1496 1648 1896 1050 1051 1054 1096 -HSync +Vsync
    # 1400x1050 @ 85.00 Hz (GTF) hsync: 93.76 kHz; pclk: 179.26 MHz
    ModeLine "1400x1050" 179.26 1400 1504 1656 1912 1050 1051 1054 1103 -HSync +Vsync
    # 1400x1050 @ 100.00 Hz (GTF) hsync: 111.20 kHz; pclk: 214.39 MHz
    ModeLine "1400x1050" 214.39 1400 1512 1664 1928 1050 1051 1054 1112 -HSync +Vsync
    # 1600x1200 @ 100.00 Hz (GTF) hsync: 127.10 kHz; pclk: 280.64 MHz
    ModeLine "1600x1200" 280.64 1600 1728 1904 2208 1200 1201 1204 1271 -HSync +Vsync
    EndSection
    # Auto-generated by Archie mkxcfg
    Section "Device"
    Identifier "Card0"
    Driver "fglrx"
    VendorName "All"
    BoardName "All"
    EndSection
    Section "Screen"
    Identifier "Screen0"
    Device "Card0"
    Monitor "Monitor0"
    DefaultColorDepth 16
    SubSection "Display"
    Depth 1
    Modes "1024x768" "800x600" "640x480"
    EndSubSection
    SubSection "Display"
    Depth 4
    Modes "1024x768" "800x600" "640x480"
    EndSubSection
    SubSection "Display"
    Depth 8
    Modes "1024x768" "800x600" "640x480"
    EndSubSection
    SubSection "Display"
    Depth 15
    Modes "1024x768" "800x600" "640x480"
    EndSubSection
    SubSection "Display"
    Depth 16
    Modes "1024x768" "800x600" "640x480"
    EndSubSection
    SubSection "Display"
    Depth 24
    Modes "1024x768" "800x600" "640x480"
    EndSubSection
    SubSection "Display"
    Depth 32
    Modes "1024x768" "800x600" "640x480"
    EndSubSection
    EndSection
    Section "DRI"
    Mode 0666
    EndSection

  • Freetalk-1200 Connect.Me speed dial problem

    Just received my long awaited Connect.Me and it's been working just as I expected. The only problem I encountered was that I couldn't assing speed dial numbers to 2 of my contacts. Others work perfectly, when I click them, box of information appears to the middle of the screen, but when I click one of the two with the problem, nothing happens.
    I have tried everything like resetting from the button and from the web UI, deleting and adding them again to my contacts but nothing helps. Adding new contacts works fine. I would not rather create a new Skype account for my self - nor ask these two friends to make a new account for themselves - just because of this problem. Any kind of advice is welcome
    Cheers from Finland!

    Skype hasn't supported speed dials in it's software for some time.  It's considered a legacy feature. The use of speed dials is configured through the Freetalk Connect Me web interface, not the Skype client.  You need to sign into your Connect Me device via your web browser and click on "Contacts and Speed Dials".  Once there all your contacts will be listed on the left pane.  Select any one of those contacts and click "ADD TO SPEED DIAL".  It will assign a speed dial number incrementally on the right pane.  You can change that number to a number of your choosing (0-99) at any time.  That's all it takes to set up.  If you recently add a contact it my not show on that list.  If it doesn't sign off the client in which you added the contact or contact changes, then power cycle the Connect Me box and log back in.  It should update.  If it does not, the only other alternative is to do a factory reset on the unit so that it will purge the list and updated it with the latest copy.  Below I attached an image of the screen, though it may take some time until it gets approved and displayed to the general public.

  • FTP Adapter config problem (again :/ )

    Hello all.
    I know that this topic was discussed few times before but i still cant setup my FTP adapter.
    My OS is Win XP. I downloaded free ftp server (XLight FTP Server) and setup my oc4j-ra.xml in following way:
         <connector-factory location="eis/Ftp/FtpAdapter" connector-name="Ftp Adapter">
         <config-property name="host" value="10.172.201.57"/>
         <config-property name="port" value="210"/>
         <config-property name="username" value="szeryf"/>
         <config-property name="password" value="szeryf"/>
         </connector-factory>
    where shown ip address is my computer address. I also created user szeryf/szeryf at my local FTP server and tried to connect to that server using some ftp client - with success. Then i created some simple BPEL process to upload file to FTP server. Each time i try i get fault that connection to server failed.
    Maybe someone experienced such a thing and could help me with that problem?
    Regards,
    Chris

    Are you sure your ftp server is on port 210? It seems odd.
    And is there a reason you are editing oc4j-ra.xml directly? Why not make a partner link and get that working first?

  • Visa config. problem

    Hi, everyone
    I connect my device at COM1, but I cannot find that com port in serial config.
    It means I cannot find any connection with my device in system manager.
    I only want to use labview to control my device, even not use dll.
    Anybody can figure out what problems in my situation ?
    # I use vb.net to do the same thing, and it works. So I think my deivce have no problems.
    Certified LabVIEW Developer

    Hi, RavensFan
    Com1 shows in windows device manager, but it not show my device name.
    Like this picture.
    So visa resource name not show "Com1".
    I didn't install MAX, and I will try later and reinstall my visa driver.
    thank for your reply.
    Certified LabVIEW Developer

  • Config problem when transport

    Hi Experts,
    I created a Z output type in NACE in Dev system 200 client. and with this i create a process code to for my inbound IDOC partner profile. Along with this we created IDOC segments and other stuff. Now after transport I am not getting these changes reflected in TST System
    How can we confirm about thr TR request number in whic TR the changes saved.
    I think the possible problems are:
    1. May be saved in any other TR or
    2. Because of config changes are done in 200 client instead of 100 client.
    I have no idea about config related things.
    Can anyone please tell me about the problem and its solution
    Regards,
    Nik

    Hi John,
    Thanks for your reply. The thing is,
    I dont remember, when i created the Process code for inbound IDOC did it asked for the TR, ya it must ask, but i forget the TR number. Can you please help me how to get which TR it is saved. Also the thing is when i treed creating new Process Code it is not asking me any TR. So the Posibilities i think may be it dont ask for the TR or a TR is not Transported thats y it is not asking me for the new TR.
    In menu i am not getting any button which tell me about the TR in which the process code saved.
    For NACE issue, i am bit confused regarding the client. Can u please explain me to add an output type in NACE, which client i have to use (100 client ?).For a new output type I used the cleint i usually work on i.e 200. and things are working fine in DEV, But when i transported all my requests to TST server, i am not able to see the output type there in TST system.
    DO I NEED TO DO BOTH THINGS PROCESS CODE & NACE IN CONFIG CLIENT ??
    Regards,
    Nik

  • LMS 4.1 multiserver config problem

    I m facing a problem in multiserver configuration, in making master-slave servers.
    Master server config is done, certificates are imported, SSO is also configured and all the pre-requisites given in the multiserver-config doc of lms4.1.
    While making slave server from stand-alone, getting errors like "cetrificate expired" and "certificte not installed" in two different ways, putting master-server IP as master address and putting master-server domain name respectively, both snapshots are attached. My Domain name is DNS resolvable.
    Anyone can help me out on this...?

    You can add your custom prompts into /opt/CSCOpx/objects/cmf/data/TacacsPrompts.ini. No restart of LMS is required for the addition to be recognized.

  • Strange download speed / latency problem

    Hi all,
    I've lately been having problems with only my download speed and latency when gaming online. Sometimes I'm getting my normal full 10MB connection and other times it randomally drops down to between 0.1 and 4MB, it doesn't matter if it is peak hours or not it is very random. When I am getting my full speed all websites/gaming online work perfectly but when the speed drops even to 4MB or so everything requires constant refreshing and my gaming online becomes impossible.
    I've noticed that sometimes when the phone rings the broadband will disconnect, and my upload speed appears to be unaffected.
    I have tried a quiet line test and it was clear so I'm not sure what is going on.
    I have tried different routers/cables/filters and have also tried restarting the router.
    I read about packet loss and thought it was maybe an issue to do with that, and so when doing a pathping to BT.net i've noticed that when the speed is high and everything appears to be working I get no packet loss, but when it is slow and things don't want to load I get some (as shown below). I have no idea if this is related but I will link as much information as i can to see if it is any help.
    Trace complete.
    Tracing route to bt.net [193.113.211.125]
    over a maximum of 30 hops:
      0  User1-PC.home [192.168.1.64]
      1  api.home [192.168.1.254]
      2  217.32.141.132
      3  217.32.141.174
      4  213.120.161.74
      5  217.41.222.50
      6  217.41.222.182
      7  acc2-10GigE-0-0-0-4.bm.21cn-ipp.bt.net [109.159.248.194]
      8  109.159.248.140
      9  core1-pos6-1.manchester.ukcore.bt.net [62.172.103.73]
     10  core1-pos9-0.glasgow.ukcore.bt.net [194.74.16.174]
     11  vhsaccess1-gig1-0.glasgow.fixed.bt.net [217.32.170.146]
     12  ftip002676159.vhsaccess1.glasgow.fixed-nte.bt.net [213.121.156.38]
     13     *        *        *
    Computing statistics for 300 seconds...
                Source to Here   This Node/Link
    Hop  RTT    Lost/Sent = Pct  Lost/Sent = Pct  Address
      0                                           User1-PC.home [192.168.1.64]
                                    0/ 100 =  0%   |
      1    2ms     0/ 100 =  0%     0/ 100 =  0%  api.home [192.168.1.254]
                                    2/ 100 =  2%   |
      2   12ms     4/ 100 =  4%     2/ 100 =  2%  217.32.141.132
                                    0/ 100 =  0%   |
      3   13ms     2/ 100 =  2%     0/ 100 =  0%  217.32.141.174
                                    0/ 100 =  0%   |
      4   16ms     4/ 100 =  4%     2/ 100 =  2%  213.120.161.74
                                    0/ 100 =  0%   |
      5  ---     100/ 100 =100%    98/ 100 = 98%  217.41.222.50
                                    0/ 100 =  0%   |
      6   15ms     7/ 100 =  7%     5/ 100 =  5%  217.41.222.182
                                    0/ 100 =  0%   |
      7   15ms     6/ 100 =  6%     4/ 100 =  4%  acc2-10GigE-0-0-0-4.bm.21cn-ipp.bt
    .net [109.159.248.194]
                                    0/ 100 =  0%   |
      8   22ms    22/ 100 = 22%    20/ 100 = 20%  109.159.248.140
                                    0/ 100 =  0%   |
      9   23ms    32/ 100 = 32%    30/ 100 = 30%  core1-pos6-1.manchester.ukcore.bt.
    net [62.172.103.73]
                                    0/ 100 =  0%   |
     10   37ms     4/ 100 =  4%     2/ 100 =  2%  core1-pos9-0.glasgow.ukcore.bt.net
     [194.74.16.174]
                                    0/ 100 =  0%   |
     11   34ms    30/ 100 = 30%    28/ 100 = 28%  vhsaccess1-gig1-0.glasgow.fixed.bt
    .net [217.32.170.146]
                                    0/ 100 =  0%   |
     12   35ms     2/ 100 =  2%     0/ 100 =  0%  ftip002676159.vhsaccess1.glasgow.f
    ixed-nte.bt.net [213.121.156.38]
    Link Information
    Uptime:
    0 days, 17:50:48
    Modulation:
    G.992.5 annex A
    Bandwidth (Up/Down) [kbps/kbps]:
    920 / 12,917
    Data Transferred (Sent/Received) [MB/MB]:
    343.16 / 603.15
    Output Power (Up/Down) [dBm]:
    12.0 / 22.5
    Line Attenuation (Up/Down) [dB]:
    20.0 / 38.5
    SN Margin (Up/Down) [dB]:
    5.0 / 4.0
    Vendor ID (Local/Remote):
    TMMB / TSTC
    Loss of Framing (Local/Remote):
    0 / 0
    Loss of Signal (Local/Remote):
    1 / 0
    Loss of Power (Local/Remote):
    0 / 0
    Loss of Link (Remote):
    0
    Error Seconds (Local/Remote):
    35,052 / 0
    FEC Errors (Up/Down):
    0 / 0
    CRC Errors (Up/Down):
    0 / 854,020
    HEC Errors (Up/Down):
    0 / 492,945
    Line Profile:
    Fast

    check you exchange for any problems  http://usertools.plus.net/exchanges/mso.php
    http://usertools.plus.net/exchanges/?
    http://btbusiness.custhelp.com/app/service_status
    If you like a post, or want to say thanks for a helpful answer, please click on the Ratings star on the left-hand side of the post.
    If someone answers your question correctly please let other members know by clicking on ’Mark as Accepted Solution’.

  • E65 Speed dial problem

    Just got a new E65 after dumping my i-mate SP5 Windows Mobile device. I seem to have a bug/problem with the speed dial functionality. The speed dials work fine when using the kepad long press method, but if I select from the on screen application I just get "Invalid phone number". Can anyone help

    I managed to resolve this myself throguh trial and error. It seems that the speed dial application doesn't like spaces and brackets in the phone number (as often happens when the number is first entered in Outlook for example), whilst the long key press method doesn't care about this sort of number punctuation. Using +country-code doesn't seem to be a problem in either mode. So I just edited my stored numbers and it works fine.
    Also note that the same problem exists with the number used for conference calls, and using the hot key for conference call dialing.

Maybe you are looking for

  • List installed apps

    I've searched for what I'm after many times with no luck. Simply put, I would like a list of the apps in my iTunes library and alongside each app, I'd like to see whether or not it is installed on my iPhone or iPad. I can get all of the information s

  • HT4009 I cant get my store to open on sims free play???? Any help

    I'm playing sims free play n want to add more money to my sims n my city but can't get store to open in game. I did the latest update n still not working I want to uninstall app n start over if I have to so it may work. But can't even uninstall don't

  • JDBC Driver 10.1.0.5 to 10.2.0.3 Upgrade Exception: Socket is not connected

    Environment - Oracle TopLink 10g Release 3 (10.1.3.3.0) (Build 070620) Oracle 10g Release 3 (10.1.3) Application Server Oracle Database 10g Enterprise Edition Release 10.2.0.2.0 - 64bit Production JDBC Driver: 10.2.0.3 Problem - I am trying a simple

  • Cost Element Creation against COGM & COGS

    Dear Experts, Some person suggest that while creating COGS GL Codes in FS00 cost element should not be assigned. According to him if this is done then COGS will flow to COPA and thus COPA profitability report will be wrong. Can you please tell whethe

  • Function in to_date format...

    Hi I have one function which retun value in mm/dd/yyyy format. inside select clause iwant compare this function with mm/yyyy format. but function can not come with to_date format. need help to work wround due to this select query out put getting gene