Usb connection doesn't work for hdr-cx260v on my computer

This is a (mostly) on and (sometimes) off issue. I have previously worked with Sony and have occasionally succeeded. Using the 'extra' 16gb card works to connect and load. My problem is when I'm using the video stored in internal memory and using the usb connection. If/when I ever actually load the internal memory data (I actually have already loaded most of it, but not the most current), I intend in the future to use only the 'exernal' memory card. My most recent call to Sony indicated that I don't have any support since the camery is 2+ years old - they send me an e-mail to a site that gave instructions, but the instructions don't seem to solve my problem. I don't seem to have any problem connection other 'devices' to my USB ports.

When I connect the camcorder usb to my desktop pc (using different USB drive connections), my computer does not seem to recognize any of the connections. When I use another usb memory card to the same usb connections, the computer does recognize the drive. There have been a few times when the camcorder has recognized the camcorder connection (most recently about June 12) - but it does not at thie time. If I take the extra 16gb memory card from the camcorder and connect it to the memory card connection, the computer has always recognized it. My problem is trying to get the video from the camcorders internal memory through the USB connection.I expect if/when I can get these files loaded, I intend to no longer use the camcorder's internal memory, and insted always use the extra memory card. Pierre I realize that If I could have the laptop recognize the usb connection, I could manually copy the video files myself, although I believe PMH would also have worked in this case.

Similar Messages

  • Remote/USB debug doesn't work for me in iOS

    I'm trying to debug my app in the iPad, but whenever I use the ipa-debug or ipa-debug-interpreter targets, the app just plain doesn't work. It gets stuck in the first screen and nothing happens, no matter if I use -connect "my-ip" (remote debugging) or if I use -listen myPort (USB debugging). The app just doesn't work.
    If I use ipa-test-interpreter or ipa-ad-hoc, then it does work, but of course I can't debug. This happens in AIR 3.6 and also previous versions as well.
    My command line:
    "c:\Program Files (x86)\Adobe\Adobe Flash CS6\AIR3.6\bin\adt.bat" -package -target ipa-debug-interpreter -connect "192.168.1.11" -provisioning-profile ..\cert\ios\iPad2_01.mobileprovision -storetype pkcs12 -keystore ..\cert\ios\ios_dev.p12 -storepass MyPassword MyApp.ipa MyApp-app.xml -C . MyApp_ios.swf icons\MyApp_icon.png Default-Landscape.png -extdir ..\ane
    Did someone experience the same?

    Can you please report a bug for the same @bugbase.adobe.com with a sample app(source code ,swf, app-xml and assets/ane) with which bug can be reproduced?
    Also you can provide me the sample app(source code ,swf, app-xml and assets/ane) @[email protected] so that I can give it a try.
    Please share the bug number here.
    Thanks,
    Nimisha

  • USB connection doesn't work on Vista?

    Hi all,
    I have a problem that PC Suite just doesn't see the phone via USB under Windows Vista, but it worked just fine under XP. The only difference I see is that PC Suite installed along some "cable drivers" for XP, but for Vista.
    I've seen some people complaining about problems under Vista about a year ago, but that was supposedly fixed in new PC Suite versions. Has anyone heard anything about connectivity problems under Vista?
    I tried the latest PC Suite version, 6.85.12.0,
    my phone is E70, Windows Vista Home Basic
    Andre

    When I connect the camcorder usb to my desktop pc (using different USB drive connections), my computer does not seem to recognize any of the connections. When I use another usb memory card to the same usb connections, the computer does recognize the drive. There have been a few times when the camcorder has recognized the camcorder connection (most recently about June 12) - but it does not at thie time. If I take the extra 16gb memory card from the camcorder and connect it to the memory card connection, the computer has always recognized it. My problem is trying to get the video from the camcorders internal memory through the USB connection.I expect if/when I can get these files loaded, I intend to no longer use the camcorder's internal memory, and insted always use the extra memory card. Pierre I realize that If I could have the laptop recognize the usb connection, I could manually copy the video files myself, although I believe PMH would also have worked in this case.

  • Evdev Doesn't Work for the USB Mouse

    Hey There,
    I'm using xorg.conf because Xorg 7.3 doesn't do several things I need.. (keyboard layouts, nvidia driver, synaptics, etc..)
    Any way, my xorg.conf used to work fine until I upgraded to 7.3 today.. I know that nvidia legacy (96xx) driver doesn't work because of the ABI change in this version, so I'm not mentioning about it..
    The biggest problem I have right now is that my USB mouse doesn't work now with evdev.. I had to change evdev to mouse and protocol to auto instead which confuses and distracts me..
    I think that evdev has some problems recognizing..
    This is my xorg.conf file:
    Section "ServerLayout"
        Identifier     "Xorg Configured"
        Screen      0  "Screen0" 0 0
        InputDevice    "Keyboard0" "CoreKeyboard"
        InputDevice    "Synaptics Touchpad" "CorePointer"
            InputDevice    "USB Mouse" "SendCoreEvents"
    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"
        Load  "synaptics"
    EndSection
    Section "InputDevice"
        Identifier  "Keyboard0"
        Driver      "keyboard"
        Option "XkbRules" "xorg"
        Option "XkbModel" "pc105"
        Option "XkbLayout" "tr,de"
        Option "XkbVariant" ""
        Option "XkbOptions" "grp:alt_shift_toggle"
    EndSection
    Section "InputDevice"
      Identifier   "Synaptics Touchpad"
      Driver       "synaptics"
      Option        "Device"                "/dev/psaux"
      Option        "Protocol"              "auto-dev"
      Option        "LeftEdge"              "120"
      Option        "RightEdge"             "830"
      Option        "TopEdge"               "120"
      Option        "BottomEdge"            "650"
      Option        "FingerLow"             "14"
      Option        "FingerHigh"            "15"
      Option        "MaxTapTime"            "180"
      Option        "MaxTapMove"            "110"
      Option        "EmulateMidButtonTime"  "75"
      Option        "VertScrollDelta"       "34"
      Option        "HorizScrollDelta"      "42"
      Option        "MinSpeed"              "0.9"
      Option        "MaxSpeed"              "1.2"
      Option        "AccelFactor"           "0.01"
      Option        "EdgeMotionMinSpeed"    "15"
      Option        "EdgeMotionMaxSpeed"    "15"
      Option        "UpDownScrolling"       "1"
      Option        "CircularScrolling"     "0"
      Option        "CircScrollDelta"       "0.1"
      Option        "CircScrollTrigger"     "0"
      Option        "SHMConfig"     "on"
    EndSection
    Section "InputDevice"
            Identifier      "USB Mouse"
            Driver          "mouse"
            Option          "Device"                "/dev/input/mice"
            Option          "Protocol"              "auto"
            Option          "ZAxisMapping"          "4 5 7 6"
            Option          "Buttons"               "9"
        Option        "Emulate3Buttons"    "false"
    EndSection
    # Auto-generated by Archie mkxcfg
    Section "Monitor"
        Identifier "Monitor0"
        Option "DPMS" "true"
        HorizSync    49.68
        VertRefresh  60
        #  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
        # 1280x800 @ 60.00 Hz (GTF) hsync: 49.68 kHz; pclk: 83.46 MHz
        Modeline "1280x800"  83.46  1280 1344 1480 1680  800 801 804 828  -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      "nv"
        VendorName  "All"
        BoardName   "All"
        Option       "NvAGP" "1"
        Option       "RenderAccel" "True"
        Option       "NoPowerConnectorCheck"
        #Option       "TripleBuffer" "True"
        #Option       "AddARGBGLXVisuals"
        #Option       "BackingStore" "True"
        #Option       "AllowGLXWithComposite" "true"
    EndSection
    Section "Screen"
        Identifier "Screen0"
        Device     "Card0"
        Monitor    "Monitor0"
        DefaultColorDepth 24
        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 "1280x800" "1024x768" "800x600" "640x480"
        EndSubSection
        SubSection "Display"
            Depth     32
            Modes "1024x768" "800x600" "640x480"
        EndSubSection
        #Option "TwinView" "true"
        #Option "TVOutFormat" "COMPOSITE" #S-VIDEO
        #Option "TVStandard" "NTSC-M" #PAL-B
        #Option "MetaModes" "DFP-0: 1280x800, CRT-0: 1280x800" #; NULL, CRT-0: 1280x800"
        ##Option "MetaModes" "1024x768,1024x768; 800x600,800x600; 640x480,640x480; 512x384,512x384" #TV
        ##Option "ConnectedMonitor" "DFP-0, CRT-0"
        #Option "TwinViewOrientation" "LeftOf" #LeftOf
        #Option "SecondMonitorHorizSync" "31-90" #30-50
        #Option "SecondMonitorVertRefresh" "60-60" #60
    EndSection
    Section "DRI"
        Mode 0666
    EndSection

    Try
    Section "InputDevice"
            Identifier  "Configured Mouse"
            Driver      "evdev"
            Option      "CorePointer"
            Option      "Name" "Logitech USB-PS/2 Optical Mouse"
            Option      "Phys" "usb-0000:00:02.0-1/input0" # optional
    EndSection
    where the Name and Phys-options are found by
    cat /proc/bus/input/devices|grep Name
    cat /proc/bus/input/devices|grep Phys

  • Did an update for my ipad to ios 5 from 3 - now it stopped workig at all - only shows an icon of usb connection to i tunes. Reset didn't help , computer doesn't see an ipad. Befor did an update to i-tunes 10 as it was advised. Please HELP !

    Did an update for my ipad to ios 5 from 3 - now it stopped workig at all - only shows an icon of usb connection to i tunes. Reset didn't help , computer doesn't see an ipad. Befor did an update to i-tunes 10 as it was advised. Please HELP ! Another thing - why it happend ? I think that Apple is totaly responsible for this and where they are ? I even can't send them an e-mail ? What type of company it is ?

    Yes, Apple has caused people to go through massive panic, anxiety and wasted time by not coming out and telling us about this problem. They must know about it. How can we tell them? Now I understand why it took me 50 tries to upgrade to OS5. We all got the same crazy errors that caused us to reinstall iTunes, turn off our firewalls, buy new USB cables and basically waste tons of time and energy, when the solution was very simple. Plug your device into a USB port on your computer.
    After years of using a peripheral USB hub successfully it's no wonder we all started freaking out and thinking it was a major problem. Yes, I'm blowing off some steam, but I've been an Apple fanatic for a long time and I'm not happy about their lack of response to this issue.

  • Microphone doesn't work for Creative Live! Cam Socialize HD AF HD Webcam

    Microphone doesn't work for Creative Live! Cam Socialize HD AF HD Webcam (for Windows 7).
    I have to use external microphone from Logitech now.
    I send few emails to Customer Service. They answered once to check my Device Manager and disappeared after that. I'm really disappointed.
    It looks like the drivers for Windows 7 are wrong.

    hey Killthebeeping,
    if you have the USB Mic connected kindly remove it first then uninstall the audio drivers for your B510.
    let windows install its generic driver.
    once done plugin your usb mic and test it again.
    WW Social Media
    Important Note: If you need help, post your question in the forum, and include your system type, model number and OS. Do not post your serial number.
    Did someone help you today? Press the star on the left to thank them with a Kudo!
    If you find a post helpful and it answers your question, please mark it as an "Accepted Solution"!
    Follow @LenovoForums on Twitter!
    Have you checked out the Community Knowledgebase yet?!
    How to send a private message? --> Check out this article.

  • My mic for my iPhone 4S only works on speaker phone and doesn't work for Siri. What can I do?

    My mic on my 4s only works on speaker phone in calls. It also doesn't work for Siri or voice memos. Is there any way to fix this without having to buy new parts or exchange it?

    Hello there, mbrda92.
    The following Knowledge Base article provides some great, in-depth steps for troubleshooting your issue:
    iPhone: Hardware troubleshooting
    http://support.apple.com/kb/ts2802
    Particularly of note:
    Will not turn on, will not turn on unless connected to power, or unexpected power off
    Verify that the Sleep/Wake button functions. If it does not function, inspect it for signs of damage. If the button is damaged or is not functioning when pressed, seek service.
    Check if a Liquid Contact Indicator (LCI) is activated or there are signs of corrosion. Learn about LCIsand corrosion.
    Connect the iPhone to the iPhone's USB power adapter and let it charge for at least ten minutes.
    After at least 30 minutes, if:
    The home screen appears: The iPhone should be working. Update to the latest version of iOS if necessary. Continue charging it until it is completely charged and you see this battery icon in the upper-right corner of the screen . Then unplug the phone from power. If it immediately turns off, seek service.
    The low-battery image appears, even after the phone has charged for at least 20 minutes: See "iPhone displays the low-battery image and is unresponsive" symptom in this article.
    Something other than the Home screen or Low Battery image appears, continue with this article for further troubleshooting steps.
    If the iPhone did not turn on, reset it while connected to the iPhone USB power adapter.
    If the display turns on, go to step 4.
    If the display remains black, go to next step.
    Connect the iPhone to a computer and open iTunes. If iTunes recognizes the iPhone and indicates that it is in recovery mode, attempt to restore the iPhone. If the iPhone doesn't appear in iTunes or if you have difficulties in restoring the iPhone, see this article for further assistance.
    If restoring the iPhone resolved the issue, go to step 4. If restoring the iPhone did not solve the issue, seek service.
    Thanks for reaching out to Apple Support Communities.
    Cheers,
    Pedro.

  • Wired connection doesn't work if cable is not plugged in at boot time

    Hey all,
    I started using arch a few days ago and I simply love it, but I have a problem. The wired connection doesn't work if the cable is not plugged in at boot time, or if it was plugged in at boot time, then plugged out and in again. Switching it off and on again via the gui has the same effect. I am using NetworkManager with dhcpcd, NetworkManager is started via systemd, dhcpcd is not, I let NetworkManager do that. When I started investigating this problem there were some remnants of netctl, but now NetworkManager is the only networking-related service started at boot time. When the cable is plugged back in, NM-applet shows that it's connected, and an IP address is assigned, but the connection doesn't work.
    Here's some information regarding the system:
    It's a lenovo G50-70 laptop, it uses the r8169 driver for ethernet. (I dualboot it with windows 8.1, but arch is default and all this stuff happens also if i only use arch)
    The router is a Linksys EA2700/N600
    journalctl -u NetworkManager
    aug 26 19:14:33 arch_daboka NetworkManager[527]: <info> NetworkManager (version 0.9.10.1) is starting...
    aug 26 19:14:33 arch_daboka NetworkManager[527]: <info> Read config: /etc/NetworkManager/NetworkManager.conf
    aug 26 19:14:33 arch_daboka NetworkManager[527]: <info> WEXT support is enabled
    aug 26 19:14:35 arch_daboka NetworkManager[527]: <info> Loaded plugin keyfile: (c) 2007 - 2013 Red Hat, Inc. To report bugs please use the NetworkMan
    aug 26 19:14:35 arch_daboka NetworkManager[527]: <info> new connection /etc/NetworkManager/system-connections/Bokros
    aug 26 19:14:35 arch_daboka NetworkManager[527]: <info> new connection /etc/NetworkManager/system-connections/1. vezetékes kapcsolat
    aug 26 19:14:35 arch_daboka NetworkManager[527]: <info> new connection /etc/NetworkManager/system-connections/UPC1838142
    aug 26 19:14:35 arch_daboka NetworkManager[527]: <info> monitoring kernel firmware directory '/usr/lib/firmware'.
    aug 26 19:14:35 arch_daboka NetworkManager[527]: <info> rfkill0: found WiFi radio killswitch (at /sys/devices/pci0000:00/0000:00:1c.3/0000:02:00.0/iee
    aug 26 19:14:35 arch_daboka NetworkManager[527]: <info> rfkill1: found WiFi radio killswitch (at /sys/devices/pci0000:00/0000:00:1f.0/PNP0C09:00/VPC20
    aug 26 19:14:35 arch_daboka NetworkManager[527]: <info> WiFi hardware radio set enabled
    aug 26 19:14:35 arch_daboka NetworkManager[527]: <info> WWAN hardware radio set enabled
    aug 26 19:14:36 arch_daboka NetworkManager[527]: <info> Loaded device plugin: /usr/lib/NetworkManager/libnm-device-plugin-wifi.so
    aug 26 19:14:36 arch_daboka NetworkManager[527]: <info> Loaded device plugin: /usr/lib/NetworkManager/libnm-device-plugin-wwan.so
    aug 26 19:14:36 arch_daboka NetworkManager[527]: <info> Loaded device plugin: /usr/lib/NetworkManager/libnm-device-plugin-adsl.so
    aug 26 19:14:36 arch_daboka NetworkManager[527]: <info> Loaded device plugin: /usr/lib/NetworkManager/libnm-device-plugin-bluetooth.so
    aug 26 19:14:36 arch_daboka NetworkManager[527]: <info> WiFi enabled by radio killswitch; enabled by state file
    aug 26 19:14:36 arch_daboka NetworkManager[527]: <info> WWAN enabled by radio killswitch; enabled by state file
    aug 26 19:14:36 arch_daboka NetworkManager[527]: <info> WiMAX enabled by radio killswitch; enabled by state file
    aug 26 19:14:36 arch_daboka NetworkManager[527]: <info> Networking is enabled by state file
    aug 26 19:14:36 arch_daboka NetworkManager[527]: <info> (lo): link connected
    aug 26 19:14:36 arch_daboka NetworkManager[527]: <info> (lo): carrier is ON
    aug 26 19:14:36 arch_daboka NetworkManager[527]: <info> (lo): new Generic device (driver: 'unknown' ifindex: 1)
    aug 26 19:14:36 arch_daboka NetworkManager[527]: <info> (lo): exported as /org/freedesktop/NetworkManager/Devices/0
    aug 26 19:14:36 arch_daboka NetworkManager[527]: <info> (enp1s0): carrier is OFF
    aug 26 19:14:36 arch_daboka NetworkManager[527]: <info> (enp1s0): new Ethernet device (driver: 'r8169' ifindex: 2)
    aug 26 19:14:36 arch_daboka NetworkManager[527]: <info> (enp1s0): exported as /org/freedesktop/NetworkManager/Devices/1
    aug 26 19:14:36 arch_daboka NetworkManager[527]: <info> (enp1s0): device state change: unmanaged -> unavailable (reason 'managed') [10 20 2]
    aug 26 19:14:36 arch_daboka systemd[1]: Started Network Manager.
    aug 26 19:14:36 arch_daboka NetworkManager[527]: <info> (enp1s0): preparing device
    aug 26 19:14:36 arch_daboka NetworkManager[527]: <info> (wlp2s0): using nl80211 for WiFi device control
    aug 26 19:14:36 arch_daboka NetworkManager[527]: <info> (wlp2s0): driver supports Access Point (AP) mode
    aug 26 19:14:36 arch_daboka NetworkManager[527]: <info> (wlp2s0): new 802.11 WiFi device (driver: 'ath9k' ifindex: 3)
    aug 26 19:14:36 arch_daboka NetworkManager[527]: <info> (wlp2s0): exported as /org/freedesktop/NetworkManager/Devices/2
    aug 26 19:14:36 arch_daboka NetworkManager[527]: <info> (wlp2s0): device state change: unmanaged -> unavailable (reason 'managed') [10 20 2]
    aug 26 19:14:36 arch_daboka NetworkManager[527]: <info> (wlp2s0): preparing device
    aug 26 19:14:36 arch_daboka NetworkManager[527]: <info> use BlueZ version 5
    aug 26 19:14:37 arch_daboka NetworkManager[527]: <info> wpa_supplicant started
    aug 26 19:14:37 arch_daboka NetworkManager[527]: <info> (wlp2s0) supports 4 scan SSIDs
    aug 26 19:14:37 arch_daboka NetworkManager[527]: <info> (wlp2s0): supplicant interface state: starting -> ready
    aug 26 19:14:37 arch_daboka NetworkManager[527]: <info> (wlp2s0): device state change: unavailable -> disconnected (reason 'supplicant-available') [20
    aug 26 19:14:37 arch_daboka NetworkManager[527]: <info> (wlp2s0): supplicant interface state: ready -> disconnected
    aug 26 19:14:37 arch_daboka NetworkManager[527]: <info> (wlp2s0) supports 4 scan SSIDs
    aug 26 19:14:37 arch_daboka NetworkManager[527]: <info> (wlp2s0): supplicant interface state: disconnected -> inactive
    aug 26 19:14:42 arch_daboka NetworkManager[527]: <info> startup complete
    aug 26 19:15:00 arch_daboka NetworkManager[527]: <info> Auto-activating connection 'Bokros'.
    aug 26 19:15:00 arch_daboka NetworkManager[527]: <info> Activation (wlp2s0) starting connection 'Bokros'
    aug 26 19:15:00 arch_daboka NetworkManager[527]: <info> Activation (wlp2s0) Stage 1 of 5 (Device Prepare) scheduled...
    aug 26 19:15:00 arch_daboka NetworkManager[527]: <info> Activation (wlp2s0) Stage 1 of 5 (Device Prepare) started...
    aug 26 19:15:00 arch_daboka NetworkManager[527]: <info> (wlp2s0): device state change: disconnected -> prepare (reason 'none') [30 40 0]
    aug 26 19:15:00 arch_daboka NetworkManager[527]: <info> NetworkManager state is now CONNECTING
    aug 26 19:15:00 arch_daboka NetworkManager[527]: <info> Activation (wlp2s0) Stage 2 of 5 (Device Configure) scheduled...
    aug 26 19:15:00 arch_daboka NetworkManager[527]: <info> Activation (wlp2s0) Stage 1 of 5 (Device Prepare) complete.
    aug 26 19:15:00 arch_daboka NetworkManager[527]: <info> Activation (wlp2s0) Stage 2 of 5 (Device Configure) starting...
    aug 26 19:15:00 arch_daboka NetworkManager[527]: <info> (wlp2s0): device state change: prepare -> config (reason 'none') [40 50 0]
    aug 26 19:15:00 arch_daboka NetworkManager[527]: <info> Activation (wlp2s0/wireless): connection 'Bokros' has security, and secrets exist. No new sec
    aug 26 19:15:00 arch_daboka NetworkManager[527]: <info> Config: added 'ssid' value 'Bokros'
    aug 26 19:15:00 arch_daboka NetworkManager[527]: <info> Config: added 'scan_ssid' value '1'
    aug 26 19:15:00 arch_daboka NetworkManager[527]: <info> Config: added 'key_mgmt' value 'WPA-PSK'
    aug 26 19:15:00 arch_daboka NetworkManager[527]: <info> Config: added 'psk' value '<omitted>'
    aug 26 19:15:00 arch_daboka NetworkManager[527]: <info> Activation (wlp2s0) Stage 2 of 5 (Device Configure) complete.
    aug 26 19:15:00 arch_daboka NetworkManager[527]: <info> Config: set interface ap_scan to 1
    aug 26 19:15:00 arch_daboka NetworkManager[527]: <info> (wlp2s0): supplicant interface state: inactive -> authenticating
    aug 26 19:15:00 arch_daboka NetworkManager[527]: <info> (wlp2s0): supplicant interface state: authenticating -> associated
    aug 26 19:15:00 arch_daboka NetworkManager[527]: <info> (wlp2s0): supplicant interface state: associated -> 4-way handshake
    aug 26 19:15:01 arch_daboka NetworkManager[527]: <info> (wlp2s0): supplicant interface state: 4-way handshake -> completed
    aug 26 19:15:01 arch_daboka NetworkManager[527]: <info> Activation (wlp2s0/wireless) Stage 2 of 5 (Device Configure) successful. Connected to wireles
    aug 26 19:15:01 arch_daboka NetworkManager[527]: <info> Activation (wlp2s0) Stage 3 of 5 (IP Configure Start) scheduled.
    aug 26 19:15:01 arch_daboka NetworkManager[527]: <info> Activation (wlp2s0) Stage 3 of 5 (IP Configure Start) started...
    aug 26 19:15:01 arch_daboka NetworkManager[527]: <info> (wlp2s0): device state change: config -> ip-config (reason 'none') [50 70 0]
    aug 26 19:15:01 arch_daboka NetworkManager[527]: <info> Activation (wlp2s0) Beginning DHCPv4 transaction (timeout in 45 seconds)
    aug 26 19:15:01 arch_daboka NetworkManager[527]: <info> dhcpcd started with pid 3599
    aug 26 19:15:01 arch_daboka NetworkManager[527]: <info> Activation (wlp2s0) Stage 3 of 5 (IP Configure Start) complete.
    aug 26 19:15:01 arch_daboka dhcpcd[3599]: version 6.4.3 starting
    aug 26 19:15:01 arch_daboka NetworkManager[527]: dhcpcd[3599]: version 6.4.3 starting
    aug 26 19:15:01 arch_daboka NetworkManager[527]: <info> (wlp2s0): DHCPv4 state changed nbi -> preinit
    aug 26 19:15:01 arch_daboka dhcpcd[3599]: DUID 00:01:00:01:1b:7c:0d:d6:28:d2:44:7f:89:66
    aug 26 19:15:01 arch_daboka dhcpcd[3599]: wlp2s0: IAID 65:59:c9:b5
    aug 26 19:15:01 arch_daboka NetworkManager[527]: dhcpcd[3599]: DUID 00:01:00:01:1b:7c:0d:d6:28:d2:44:7f:89:66
    aug 26 19:15:01 arch_daboka NetworkManager[527]: dhcpcd[3599]: wlp2s0: IAID 65:59:c9:b5
    aug 26 19:15:01 arch_daboka dhcpcd[3599]: wlp2s0: soliciting an IPv6 router
    aug 26 19:15:01 arch_daboka NetworkManager[527]: dhcpcd[3599]: wlp2s0: soliciting an IPv6 router
    aug 26 19:15:02 arch_daboka dhcpcd[3599]: wlp2s0: rebinding lease of 192.168.1.137
    aug 26 19:15:02 arch_daboka NetworkManager[527]: dhcpcd[3599]: wlp2s0: rebinding lease of 192.168.1.137
    aug 26 19:15:07 arch_daboka dhcpcd[3599]: wlp2s0: leased 192.168.1.137 for 86400 seconds
    aug 26 19:15:07 arch_daboka dhcpcd[3599]: wlp2s0: adding route to 192.168.1.0/24
    aug 26 19:15:07 arch_daboka NetworkManager[527]: dhcpcd[3599]: wlp2s0: leased 192.168.1.137 for 86400 seconds
    aug 26 19:15:07 arch_daboka NetworkManager[527]: dhcpcd[3599]: wlp2s0: adding route to 192.168.1.0/24
    aug 26 19:15:07 arch_daboka NetworkManager[527]: <info> (wlp2s0): DHCPv4 state changed preinit -> reboot
    aug 26 19:15:07 arch_daboka NetworkManager[527]: <info> address 192.168.1.137
    aug 26 19:15:07 arch_daboka NetworkManager[527]: <info> plen 24 (255.255.255.0)
    aug 26 19:15:07 arch_daboka NetworkManager[527]: <info> gateway 192.168.1.1
    aug 26 19:15:07 arch_daboka NetworkManager[527]: <info> server identifier 192.168.1.1
    aug 26 19:15:07 arch_daboka NetworkManager[527]: <info> lease time 86400
    aug 26 19:15:07 arch_daboka NetworkManager[527]: <info> hostname 'arch_daboka'
    aug 26 19:15:07 arch_daboka NetworkManager[527]: <info> nameserver '192.168.1.1'
    aug 26 19:15:07 arch_daboka NetworkManager[527]: <info> domain name 'chello.hu'
    aug 26 19:15:07 arch_daboka NetworkManager[527]: <info> Activation (wlp2s0) Stage 5 of 5 (IPv4 Configure Commit) scheduled...
    aug 26 19:15:07 arch_daboka NetworkManager[527]: <info> Activation (wlp2s0) Stage 5 of 5 (IPv4 Commit) started...
    aug 26 19:15:07 arch_daboka NetworkManager[527]: <info> (wlp2s0): device state change: ip-config -> ip-check (reason 'none') [70 80 0]
    aug 26 19:15:07 arch_daboka NetworkManager[527]: <info> Activation (wlp2s0) Stage 5 of 5 (IPv4 Commit) complete.
    aug 26 19:15:07 arch_daboka NetworkManager[527]: <info> (wlp2s0): device state change: ip-check -> secondaries (reason 'none') [80 90 0]
    aug 26 19:15:07 arch_daboka NetworkManager[527]: <info> (wlp2s0): device state change: secondaries -> activated (reason 'none') [90 100 0]
    aug 26 19:15:07 arch_daboka NetworkManager[527]: <info> NetworkManager state is now CONNECTED_LOCAL
    aug 26 19:15:07 arch_daboka NetworkManager[527]: <info> NetworkManager state is now CONNECTED_GLOBAL
    aug 26 19:15:07 arch_daboka NetworkManager[527]: <info> Policy set 'Bokros' (wlp2s0) as default for IPv4 routing and DNS.
    aug 26 19:15:07 arch_daboka NetworkManager[527]: <info> Writing DNS information to /usr/bin/resolvconf
    aug 26 19:15:07 arch_daboka NetworkManager[527]: <info> Activation (wlp2s0) successful, device activated.
    aug 26 19:15:14 arch_daboka dhcpcd[3599]: wlp2s0: no IPv6 Routers available
    aug 26 19:15:14 arch_daboka NetworkManager[527]: dhcpcd[3599]: wlp2s0: no IPv6 Routers available
    aug 26 19:15:34 arch_daboka NetworkManager[527]: <info> (enp1s0): link connected
    aug 26 19:15:34 arch_daboka NetworkManager[527]: <info> (enp1s0): device state change: unavailable -> disconnected (reason 'carrier-changed') [20 30 4
    aug 26 19:15:34 arch_daboka NetworkManager[527]: <info> Auto-activating connection '1. vezetékes kapcsolat'.
    aug 26 19:15:34 arch_daboka NetworkManager[527]: <info> Activation (enp1s0) starting connection '1. vezetékes kapcsolat'
    aug 26 19:15:34 arch_daboka NetworkManager[527]: <info> Activation (enp1s0) Stage 1 of 5 (Device Prepare) scheduled...
    aug 26 19:15:34 arch_daboka NetworkManager[527]: <info> Activation (enp1s0) Stage 1 of 5 (Device Prepare) started...
    aug 26 19:15:34 arch_daboka NetworkManager[527]: <info> (enp1s0): device state change: disconnected -> prepare (reason 'none') [30 40 0]
    aug 26 19:15:34 arch_daboka NetworkManager[527]: <info> Activation (enp1s0) Stage 2 of 5 (Device Configure) scheduled...
    aug 26 19:15:34 arch_daboka NetworkManager[527]: <info> Activation (enp1s0) Stage 1 of 5 (Device Prepare) complete.
    aug 26 19:15:34 arch_daboka NetworkManager[527]: <info> Activation (enp1s0) Stage 2 of 5 (Device Configure) starting...
    aug 26 19:15:34 arch_daboka NetworkManager[527]: <info> (enp1s0): device state change: prepare -> config (reason 'none') [40 50 0]
    aug 26 19:15:34 arch_daboka NetworkManager[527]: <info> Activation (enp1s0) Stage 2 of 5 (Device Configure) successful.
    aug 26 19:15:34 arch_daboka NetworkManager[527]: <info> Activation (enp1s0) Stage 3 of 5 (IP Configure Start) scheduled.
    aug 26 19:15:34 arch_daboka NetworkManager[527]: <info> Activation (enp1s0) Stage 2 of 5 (Device Configure) complete.
    aug 26 19:15:34 arch_daboka NetworkManager[527]: <info> Activation (enp1s0) Stage 3 of 5 (IP Configure Start) started...
    aug 26 19:15:34 arch_daboka NetworkManager[527]: <info> (enp1s0): device state change: config -> ip-config (reason 'none') [50 70 0]
    aug 26 19:15:34 arch_daboka NetworkManager[527]: <info> Activation (enp1s0) Beginning DHCPv4 transaction (timeout in 45 seconds)
    aug 26 19:15:34 arch_daboka NetworkManager[527]: <info> dhcpcd started with pid 4322
    aug 26 19:15:34 arch_daboka NetworkManager[527]: <info> Activation (enp1s0) Stage 3 of 5 (IP Configure Start) complete.
    aug 26 19:15:34 arch_daboka dhcpcd[4322]: version 6.4.3 starting
    aug 26 19:15:34 arch_daboka dhcpcd[4322]: DUID 00:01:00:01:1b:7c:0d:d6:28:d2:44:7f:89:66
    aug 26 19:15:34 arch_daboka dhcpcd[4322]: enp1s0: IAID 44:7f:89:66
    aug 26 19:15:34 arch_daboka NetworkManager[527]: dhcpcd[4322]: version 6.4.3 starting
    aug 26 19:15:34 arch_daboka NetworkManager[527]: dhcpcd[4322]: DUID 00:01:00:01:1b:7c:0d:d6:28:d2:44:7f:89:66
    aug 26 19:15:34 arch_daboka NetworkManager[527]: dhcpcd[4322]: enp1s0: IAID 44:7f:89:66
    aug 26 19:15:34 arch_daboka NetworkManager[527]: <info> (enp1s0): DHCPv4 state changed nbi -> preinit
    aug 26 19:15:34 arch_daboka dhcpcd[4322]: enp1s0: soliciting an IPv6 router
    aug 26 19:15:34 arch_daboka NetworkManager[527]: dhcpcd[4322]: enp1s0: soliciting an IPv6 router
    aug 26 19:15:34 arch_daboka dhcpcd[4322]: enp1s0: rebinding lease of 192.168.1.138
    aug 26 19:15:34 arch_daboka NetworkManager[527]: dhcpcd[4322]: enp1s0: rebinding lease of 192.168.1.138
    aug 26 19:15:39 arch_daboka dhcpcd[4322]: enp1s0: leased 192.168.1.138 for 86400 seconds
    aug 26 19:15:39 arch_daboka dhcpcd[4322]: enp1s0: adding route to 192.168.1.0/24
    aug 26 19:15:39 arch_daboka NetworkManager[527]: dhcpcd[4322]: enp1s0: leased 192.168.1.138 for 86400 seconds
    aug 26 19:15:39 arch_daboka NetworkManager[527]: dhcpcd[4322]: enp1s0: adding route to 192.168.1.0/24
    aug 26 19:15:39 arch_daboka NetworkManager[527]: <info> (enp1s0): DHCPv4 state changed preinit -> reboot
    aug 26 19:15:39 arch_daboka NetworkManager[527]: <info> address 192.168.1.138
    aug 26 19:15:39 arch_daboka NetworkManager[527]: <info> plen 24 (255.255.255.0)
    aug 26 19:15:39 arch_daboka NetworkManager[527]: <info> gateway 192.168.1.1
    aug 26 19:15:39 arch_daboka NetworkManager[527]: <info> server identifier 192.168.1.1
    aug 26 19:15:39 arch_daboka NetworkManager[527]: <info> lease time 86400
    aug 26 19:15:39 arch_daboka NetworkManager[527]: <info> hostname 'arch_daboka'
    aug 26 19:15:39 arch_daboka NetworkManager[527]: <info> nameserver '192.168.1.1'
    aug 26 19:15:39 arch_daboka NetworkManager[527]: <info> domain name 'chello.hu'
    aug 26 19:15:39 arch_daboka NetworkManager[527]: <info> Activation (enp1s0) Stage 5 of 5 (IPv4 Configure Commit) scheduled...
    aug 26 19:15:39 arch_daboka NetworkManager[527]: <info> Activation (enp1s0) Stage 5 of 5 (IPv4 Commit) started...
    aug 26 19:15:39 arch_daboka NetworkManager[527]: <info> (enp1s0): device state change: ip-config -> ip-check (reason 'none') [70 80 0]
    aug 26 19:15:39 arch_daboka NetworkManager[527]: <info> Activation (enp1s0) Stage 5 of 5 (IPv4 Commit) complete.
    aug 26 19:15:39 arch_daboka NetworkManager[527]: <info> (enp1s0): device state change: ip-check -> secondaries (reason 'none') [80 90 0]
    aug 26 19:15:39 arch_daboka NetworkManager[527]: <info> (enp1s0): device state change: secondaries -> activated (reason 'none') [90 100 0]
    aug 26 19:15:40 arch_daboka NetworkManager[527]: <info> NetworkManager state is now CONNECTED_LOCAL
    aug 26 19:15:40 arch_daboka NetworkManager[527]: <info> NetworkManager state is now CONNECTED_GLOBAL
    aug 26 19:15:40 arch_daboka NetworkManager[527]: <info> Policy set '1. vezetékes kapcsolat' (enp1s0) as default for IPv4 routing and DNS.
    aug 26 19:15:40 arch_daboka NetworkManager[527]: <info> Writing DNS information to /usr/bin/resolvconf
    aug 26 19:15:40 arch_daboka NetworkManager[527]: <info> Activation (enp1s0) successful, device activated.
    aug 26 19:15:47 arch_daboka dhcpcd[4322]: enp1s0: no IPv6 Routers available
    aug 26 19:15:47 arch_daboka NetworkManager[527]: dhcpcd[4322]: enp1s0: no IPv6 Routers available
    ping -c 10 192.168.1.1
    PING 192.168.1.1 (192.168.1.1) 56(84) bytes of data.
    64 bytes from 192.168.1.1: icmp_seq=1 ttl=64 time=4.38 ms
    64 bytes from 192.168.1.1: icmp_seq=2 ttl=64 time=2.79 ms
    64 bytes from 192.168.1.1: icmp_seq=3 ttl=64 time=4.89 ms
    64 bytes from 192.168.1.1: icmp_seq=4 ttl=64 time=5.30 ms
    64 bytes from 192.168.1.1: icmp_seq=5 ttl=64 time=1.59 ms
    64 bytes from 192.168.1.1: icmp_seq=6 ttl=64 time=1.61 ms
    64 bytes from 192.168.1.1: icmp_seq=7 ttl=64 time=4.37 ms
    64 bytes from 192.168.1.1: icmp_seq=8 ttl=64 time=2.40 ms
    64 bytes from 192.168.1.1: icmp_seq=9 ttl=64 time=6.47 ms
    --- 192.168.1.1 ping statistics ---
    10 packets transmitted, 9 received, 10% packet loss, time 9014ms
    rtt min/avg/max/mdev = 1.599/3.759/6.471/1.627 ms
    ping -c 100 8.8.8.8 - it's not completely disconnected, but it's always 8 packets at once that are received
    PING 8.8.8.8 (8.8.8.8) 56(84) bytes of data.
    64 bytes from 8.8.8.8: icmp_seq=20 ttl=46 time=41.7 ms
    64 bytes from 8.8.8.8: icmp_seq=21 ttl=46 time=40.0 ms
    64 bytes from 8.8.8.8: icmp_seq=22 ttl=46 time=38.8 ms
    64 bytes from 8.8.8.8: icmp_seq=23 ttl=46 time=39.3 ms
    64 bytes from 8.8.8.8: icmp_seq=24 ttl=46 time=41.8 ms
    64 bytes from 8.8.8.8: icmp_seq=25 ttl=46 time=38.4 ms
    64 bytes from 8.8.8.8: icmp_seq=26 ttl=46 time=38.4 ms
    64 bytes from 8.8.8.8: icmp_seq=27 ttl=46 time=38.0 ms
    64 bytes from 8.8.8.8: icmp_seq=56 ttl=46 time=43.4 ms
    64 bytes from 8.8.8.8: icmp_seq=57 ttl=46 time=49.8 ms
    64 bytes from 8.8.8.8: icmp_seq=58 ttl=46 time=40.2 ms
    64 bytes from 8.8.8.8: icmp_seq=59 ttl=46 time=44.3 ms
    64 bytes from 8.8.8.8: icmp_seq=60 ttl=46 time=38.5 ms
    64 bytes from 8.8.8.8: icmp_seq=61 ttl=46 time=43.4 ms
    64 bytes from 8.8.8.8: icmp_seq=62 ttl=46 time=39.2 ms
    64 bytes from 8.8.8.8: icmp_seq=63 ttl=46 time=40.5 ms
    64 bytes from 8.8.8.8: icmp_seq=92 ttl=46 time=38.3 ms
    64 bytes from 8.8.8.8: icmp_seq=93 ttl=46 time=43.7 ms
    64 bytes from 8.8.8.8: icmp_seq=94 ttl=46 time=42.3 ms
    64 bytes from 8.8.8.8: icmp_seq=95 ttl=46 time=46.6 ms
    64 bytes from 8.8.8.8: icmp_seq=96 ttl=46 time=44.9 ms
    64 bytes from 8.8.8.8: icmp_seq=97 ttl=46 time=42.9 ms
    64 bytes from 8.8.8.8: icmp_seq=98 ttl=46 time=41.7 ms
    64 bytes from 8.8.8.8: icmp_seq=99 ttl=46 time=37.8 ms
    --- 8.8.8.8 ping statistics ---
    100 packets transmitted, 24 received, 76% packet loss, time 99062ms
    rtt min/avg/max/mdev = 37.886/41.455/49.829/3.000 ms
    cat /etc/dhcpcd.conf - I tried clientid instead of duid and disabling IPv6, but neither of those helped.
    # A sample configuration for dhcpcd.
    # See dhcpcd.conf(5) for details.
    # Inform the DHCP server of our hostname for DDNS.
    hostname
    # Use the hardware address of the interface for the Client ID.
    #clientid
    # or
    # Use the same DUID + IAID as set in DHCPv6 for DHCPv4 ClientID as per RFC4361.
    duid
    # Persist interface configuration when dhcpcd exits.
    persistent
    # Rapid commit support.
    # Safe to enable by default because it requires the equivalent option set
    # on the server to actually work.
    option rapid_commit
    # A list of options to request from the DHCP server.
    option domain_name_servers, domain_name, domain_search, host_name
    option classless_static_routes
    # Most distributions have NTP support.
    option ntp_servers
    # Respect the network MTU.
    # Some interface drivers reset when changing the MTU so disabled by default.
    #option interface_mtu
    # A ServerID is required by RFC2131.
    require dhcp_server_identifier
    # Generate Stable Private IPv6 Addresses instead of hardware based ones
    slaac private
    # A hook script is provided to lookup the hostname if not set by the DHCP
    # server, but it should not be run by default.
    nohook lookup-hostname
    #noipv4ll
    #Disable IPv6
    #noipv6rs
    #noipv6
    cat /etc/NetworkManager/NetworkManager.conf
    [main]
    plugins=keyfile
    dhcp=dhcpcd
    ## Set static hostname
    #[keyfile]
    #hostname=foobar
    ## HTTP-based connectivity check
    #[connectivity]
    #uri=http://nmcheck.gnome.org/check_network_status.txt
    I couldn't find anything else to append, but if there are other log or conf files or anything else, which would help solving the problem, I should put here, please tell me.

    Try to use dhclient perhaps?  Might I also suggest letting systemd deal with the dhcp issue and not NM.  That may seem incongruous but it is possible NM is mis-handling the dhcp hand-off to the network card.  I'm no guru but I got thinking about this when I saw this in your output:
    aug 26 19:15:39 arch_daboka NetworkManager[527]: <info> (enp1s0): device state change: ip-check -> secondaries (reason 'none') [80 90 0]
    aug 26 19:15:39 arch_daboka NetworkManager[527]: <info> (enp1s0): device state change: secondaries -> activated (reason 'none') [90 100 0]
    aug 26 19:15:40 arch_daboka NetworkManager[527]: <info> NetworkManager state is now CONNECTED_LOCAL
    It is very possible that I'm mis-interpreting this information so please take it with a boulder of salt. 

  • [SOLVED] External USB mouse doesn't work

    I've installed Arch on my laptop and today faced with a problem. When I boot with AC off my external USB mouse doesn't work. Also it looks like USB ports don't work. If I detached AC when working mouse works fine.
    I can suppose there is some problem with laptop mode. May be it turns off usb ports to save energy. Anyway quick search doesn't brings any results. If someone give me a hint how to solve this problem I'll be very grateful.
    Last edited by avli (2011-07-14 16:53:15)

    Well, after diving into configs solution has been founded. The point was to disable auto suspend feature in laptop-mode-tools config by setting BATT_SUSPEND_USB variable to 0 in /etc/laptop-mode/conf.d/usb-autosuspend.conf
    Hope this information will be helpful for users who probably faced with the same problem. Thank you!

  • Central Autoreaction Method doesn't work for NW 7.10 in SolMan 7.01

    Hello!
    The central autoreaction method doesn't work for the satellite system
    NW 7.10. For systems with kernel releases 4.6D, 640, 700 this method
    works fine and e-mail alerts are coming.
    The configuration steps I've checked:
    1. Configured SCOT. The mail_send job executes every 5 minutes.
    2. Background dispatching job is released: SAP_CCMS_MONI_BATCH_DP (In
    central CEN/000/DDIC and satellite system SAT/000/DDIC)
    3. Central dispatching job is released: SAP_CCMS_CENSYS_DISPATCHER
    (Only in central system CEN/000/DDIC)
    4. The sapccm4x-agent registered as web service within CEN using
    Create Remote Monitoring for NW 7.10:
    Connection test to SAPCCM4X.<satellite_host>.00 was performed successfully
    5. Created a new autoreaction method by copying method
    CCMS_OnAlert_Email_V2 to the own Z_CCMS_Email_Alert_CEN:
    Function Module - SALO_EMAIL_IN_CASE_OF_ALERT_V2
    Execute Method on Any Server and Only in Central System, triggered by
    CCMS agents
    SENDER (EMAIL_USER) exists in CEN/000 , RECEPIENT - <distr list
    SAP_BASIS in CEN/000>, RECIPIENT-TYPEID - C
    6. Got MTE Classes from NW 7.10 satellite system and assigned this method
    Z_CCMS_Email_Alert_CEN to an MTE-class CCMS_ORAucPSAPSR3 for NW 7.10
    satellite system. The alert is red right now.
    7. The mail_send job doesn't send anything, in SCOT there are no
    sending orders.
    8. Autoreaction status on this alert in CEN in RZ20 - Sent to CEN.
    CEN_CHECKED.
    9. The alert status in RZ20 in CEN - ACTION_REQUIRED. If I execute it
    in manual the alert status changes to ACTIVE, but no email and no
    messages in sending orders in SCOT.
    Please help me to solve this issue.
    Thank you!

    Hi,
    Since you are using RECIPIENT-TYPEID =C i.e. General distribution list, pls ensure to have shared type of list created in SBWP.
    Also pls verify your SCOT configutaion , if apropriate address area i.e. *@abc.com
    Also one point to note that even if you trigger auto reaction method manually via RZ20 , pls check if alert is listed in SOST.
    if yes , that means there is problem in either SCOT configuration or distribution list.
    If alert is not appearing in SOST , that means you need to check auto reaction method parameters;
    Z_CCMS_OnAlert_Email_V2 , here check release section if Auto reaction execution method is checked.
    Regards,
    Rupali

  • The enclosure in RSS feed doesn't work for Itune

    I subscribed to my podcast rss feed to ITune, which was valid and had been tested successfully with other aggregator such as Ipodder, however, it doesn't work for ITune. When I hit "get" button next to my podcast name, I always get "!" sign in front of the name, and when I clicked it, I got error message "There was a problem downloading 'XXXXX'. The network connection could not be made".
    I'm not sure if this problem resulted from the "rewrite" function I used on my podcasting server in order to track the downloading. Here is how it works: When a mp3 file is requested, my web server will redirect the request to another asp.net program to do something and then redirect to the real mp3 file for downloading. Can it be problem in Itune? But I can use this enclosure url to download this mp3, and also the Ipodder works file with this rss feed.
    Any help will be appreciated.
    Leo
      Windows XP  

    Thanks for your reply.
    However, according to the iTune specs as following,
    Tracking Usage
    Please note that iTunes does not provide usage statistics. Some podcasters have created mechanisms for tracking the number of times that each episode has been downloaded. iTunes does not provide support in how to track downloads, but the following notes may be helpful:
    * 302s will be followed to a depth of 5 redirects and will not update the feed URL in the directory.
    * The URL before the GET-style form values (before the first ?) must end in a media file extension (e.g. mp3). To work around this, the feed provider can alter their URL from this:
    http://www.podcaster.com/load.php?f=&Wipeout.php
    to this:
    http://www.podcaster.com/load.mp3?f=&Wipeout.mp3
    Notice how it says load.mp3 instead of load.php. It should be possible to accomplish this via various means, such as web server rewrites. iTunes looks at the extension of the path part of the url, i.e. the part before the”?”.
    The http request redirection is allowed as long as the appropriate file extension such as ".mp3" is used.
    By the way, I tested it with "no redirection" version, which worked fine.
    Leo

  • Every app on my ipod (2nd gen) which requires wifi connection doesn't work although the wifi mark is on. i did try restarting my ipod, resetting network setting, disconnect from wifi and reconnected it but non of them worked.

    every app on my ipod (2nd gen) which requires wifi connection doesn't work although the wifi mark is on. i did try restarting my ipod, resetting network setting, disconnect from wifi and reconnected it but non of them worked.

    This may sound silly but try your date a time setting my ipod had the same problem and i had even checked the the date and time went all the way to the apple store for help and the genius guy just rest the date and time and it worked just fine.

  • Apple usb wired keyboard not working for MBP pro w/ 0 for stop on numeric k

    Just got logic 8 and noticing that it does load up quicker with the new os update.
    I'm going through the first getting started manual and I have a apple usb keyboard attached to my mac book pro.
    When I press 0 on the numeric keypad it doesn't stop the sequencer it just plays this soft like error sound or something. space bar works for stop however.
    Am I in the correct mode or what not? when I press 1, 3, 6 the views change, if there are different modes for the numeric keypad.
    I need to get that 0 key working for stop as it says in the first getting started manual on page 18 under "To start and stop playback:"
    my setup
    [img]http://i100.photobucket.com/albums/m18/rokuez/IMG_0282.jpg[/img]

    The zero button doesn't work for screensets - there are no screensets with a zero in (ie, it goes from 9 to 11, there is no 10).
    If you want your zero key to do something, use the key commands window to assign it to whatever you like.

  • After the OS X Lion installation, my USB modem doesn't work. I already updated the USB drivers, but nothing happened. Any suggestion?

    After the OS X Lion installation, my USB modem doesn't work. I already updated the USB drivers, but nothing happened. Any suggestion?

    You might want to do a search here on the forums re. usb modems - I've seen several threads and the opinion appears to be that faxing is no longer supported (especially since the "Fax" is now missing from the Print Preference Pane in System Preferences). I am faxing with an all-in-one printer which is connected to a landline, but I have to use the printer's control panel - can't use it from the iMac.

  • The wifi at my school isn't very good. And I can't send iMessages through it. It works for some apps like score center and my radar app, but doesn't work for other apps like clash of clans and iMessage. How can I get it to work on that  wifi network

    The wifi at my school isn't very good. And I can't send iMessages through it. It works for some apps like score center and my radar app, but doesn't work for other apps like clash of clans and iMessage. How can I get it to work on my school wifi. I have an iPhone 4S on AT&T and iOS 7.04

    In a roaming network, your "main" router is the device that would require port mapping/forwarding to be configured in order to access the IP camera from the Internet. This router is also the one that would be provide the private IP address for the camera which you will want to be a static one.
    So as you described your network, the IP cameras should be getting an IP address or you assigned it a static one and this is the address that you would enter in the Private IP address (or equivalent depending on the router used) field when setting up port mapping.
    If you are not able to access this camera from the local network, then this should be troubleshot first.

Maybe you are looking for