Checking Filesystem: Could not open -a
Hi,
I just noticed a problem during the filesystem check at boot time, a message like the following floats by (are the initscript messages logged somewhere?):
::Checking Filesystems
Could not open -a
/dev/sda2: clean ....
Could not open -a
Then the boot continues. I tracked it down to the fsck in /etc/rc.sysinit, line 263.
The scenery is:
kernel26 2.6.34-2
initscripts 2010.06-2
/dev/sda2 is my /boot partition
my root partition is on /dev/sda4 and is a btrfs one
/home is a subvol of the btrfs partition but of course has its own entry in /etc/fstab
I do have another partition using LVM, but that is currently not used (and not in fstab)
Has anybody else seen this?
Could the btrfs stuff be a problem?
I recently went back to ext3 (dropping all btrfs partitions) for various reasons, which also solved this problem.
Similar Messages
-
I am getting the following error when I open my Safari Browser.the proceedure entry point sqlite3_wal_ check point could not be located in the dynamic link library SQLITE3.DLL
Try going back to a restore point > System Restore - Microsoft Windows
-
[SOLVED] Pacman - could not open file
After being forced to downgrade my firmware in this thread I get the following error in pacman...
:: Starting full system upgrade...
resolving dependencies...
[b]error: could not open file /var/lib/pacman/local/linux-firmware-20120227-2/desc: No such file or directory[/b]
looking for inter-conflicts...
Any idea how I stop this?
Last edited by Swarfega (2012-05-17 09:03:10)Yeah thanks. Just done that and get the following
[root@xv5-ln01 andrewp]# pacman -S linux-firmware
warning: linux-firmware-20120227-2 is up to date -- reinstalling
resolving dependencies...
looking for inter-conflicts...
error: could not open file /var/lib/pacman/local/linux-firmware-20120227-2/desc: No such file or directory
Targets (1): linux-firmware-20120227-2
Total Installed Size: 38.73 MiB
Proceed with installation? [Y/n] y
(1/1) checking package integrity [###########################################################################] 100%
(1/1) loading package files [###########################################################################] 100%
(1/1) checking for file conflicts [###########################################################################] 100%
error: failed to commit transaction (conflicting files)
linux-firmware: /usr/lib/firmware/GPL-3 exists in filesystem
linux-firmware: /usr/lib/firmware/TDA7706_OM_v2.5.1_boot.txt exists in filesystem
linux-firmware: /usr/lib/firmware/TDA7706_OM_v3.0.2_boot.txt exists in filesystem
linux-firmware: /usr/lib/firmware/agere_ap_fw.bin exists in filesystem
linux-firmware: /usr/lib/firmware/agere_sta_fw.bin exists in filesystem
linux-firmware: /usr/lib/firmware/ar7010.fw exists in filesystem
linux-firmware: /usr/lib/firmware/ar7010_1_1.fw exists in filesystem
linux-firmware: /usr/lib/firmware/ar9170-1.fw exists in filesystem
linux-firmware: /usr/lib/firmware/ar9170-2.fw exists in filesystem
linux-firmware: /usr/lib/firmware/ar9271.fw exists in filesystem
linux-firmware: /usr/lib/firmware/ath3k-1.fw exists in filesystem
linux-firmware: /usr/lib/firmware/atmsar11.fw exists in filesystem
linux-firmware: /usr/lib/firmware/bnx2x-e1-4.8.53.0.fw exists in filesystem
linux-firmware: /usr/lib/firmware/bnx2x-e1-5.2.13.0.fw exists in filesystem
linux-firmware: /usr/lib/firmware/bnx2x-e1-5.2.7.0.fw exists in filesystem
linux-firmware: /usr/lib/firmware/bnx2x-e1h-4.8.53.0.fw exists in filesystem
linux-firmware: /usr/lib/firmware/bnx2x-e1h-5.2.13.0.fw exists in filesystem
linux-firmware: /usr/lib/firmware/bnx2x-e1h-5.2.7.0.fw exists in filesystem
linux-firmware: /usr/lib/firmware/dvb-fe-xc5000-1.6.114.fw exists in filesystem
linux-firmware: /usr/lib/firmware/dvb-usb-dib0700-1.20.fw exists in filesystem
linux-firmware: /usr/lib/firmware/dvb-usb-terratec-h5-drxk.fw exists in filesystem
linux-firmware: /usr/lib/firmware/emi62/bitstream.fw exists in filesystem
linux-firmware: /usr/lib/firmware/emi62/loader.fw exists in filesystem
linux-firmware: /usr/lib/firmware/emi62/midi.fw exists in filesystem
linux-firmware: /usr/lib/firmware/ene-ub6250/ms_init.bin exists in filesystem
linux-firmware: /usr/lib/firmware/ene-ub6250/ms_rdwr.bin exists in filesystem
linux-firmware: /usr/lib/firmware/ene-ub6250/msp_rdwr.bin exists in filesystem
linux-firmware: /usr/lib/firmware/ene-ub6250/sd_init1.bin exists in filesystem
linux-firmware: /usr/lib/firmware/ene-ub6250/sd_init2.bin exists in filesystem
linux-firmware: /usr/lib/firmware/ene-ub6250/sd_rdwr.bin exists in filesystem
linux-firmware: /usr/lib/firmware/ess/maestro3_assp_kernel.fw exists in filesystem
linux-firmware: /usr/lib/firmware/ess/maestro3_assp_minisrc.fw exists in filesystem
linux-firmware: /usr/lib/firmware/f2255usb.bin exists in filesystem
linux-firmware: /usr/lib/firmware/htc_7010.fw exists in filesystem
linux-firmware: /usr/lib/firmware/htc_9271.fw exists in filesystem
linux-firmware: /usr/lib/firmware/i2400m-fw-usb-1.4.sbcf exists in filesystem
linux-firmware: /usr/lib/firmware/i2400m-fw-usb-1.5.sbcf exists in filesystem
linux-firmware: /usr/lib/firmware/i6050-fw-usb-1.5.sbcf exists in filesystem
linux-firmware: /usr/lib/firmware/intelliport2.bin exists in filesystem
linux-firmware: /usr/lib/firmware/isci/Makefile exists in filesystem
linux-firmware: /usr/lib/firmware/isci/README exists in filesystem
linux-firmware: /usr/lib/firmware/isci/create_fw.c exists in filesystem
linux-firmware: /usr/lib/firmware/isci/create_fw.h exists in filesystem
linux-firmware: /usr/lib/firmware/isci/isci_firmware.bin exists in filesystem
linux-firmware: /usr/lib/firmware/isci/probe_roms.h exists in filesystem
linux-firmware: /usr/lib/firmware/iwlwifi-100-5.ucode exists in filesystem
linux-firmware: /usr/lib/firmware/iwlwifi-1000-3.ucode exists in filesystem
linux-firmware: /usr/lib/firmware/iwlwifi-1000-5.ucode exists in filesystem
linux-firmware: /usr/lib/firmware/iwlwifi-105-6.ucode exists in filesystem
linux-firmware: /usr/lib/firmware/iwlwifi-135-6.ucode exists in filesystem
linux-firmware: /usr/lib/firmware/iwlwifi-2000-6.ucode exists in filesystem
linux-firmware: /usr/lib/firmware/iwlwifi-2030-6.ucode exists in filesystem
linux-firmware: /usr/lib/firmware/iwlwifi-3945-2.ucode exists in filesystem
linux-firmware: /usr/lib/firmware/iwlwifi-4965-2.ucode exists in filesystem
linux-firmware: /usr/lib/firmware/iwlwifi-5000-1.ucode exists in filesystem
linux-firmware: /usr/lib/firmware/iwlwifi-5000-2.ucode exists in filesystem
linux-firmware: /usr/lib/firmware/iwlwifi-5000-5.ucode exists in filesystem
linux-firmware: /usr/lib/firmware/iwlwifi-5150-2.ucode exists in filesystem
linux-firmware: /usr/lib/firmware/iwlwifi-6000-4.ucode exists in filesystem
linux-firmware: /usr/lib/firmware/iwlwifi-6000g2a-5.ucode exists in filesystem
linux-firmware: /usr/lib/firmware/iwlwifi-6000g2b-5.ucode exists in filesystem
linux-firmware: /usr/lib/firmware/iwlwifi-6000g2b-6.ucode exists in filesystem
linux-firmware: /usr/lib/firmware/iwlwifi-6050-4.ucode exists in filesystem
linux-firmware: /usr/lib/firmware/iwlwifi-6050-5.ucode exists in filesystem
linux-firmware: /usr/lib/firmware/kaweth/new_code.bin exists in filesystem
linux-firmware: /usr/lib/firmware/kaweth/new_code_fix.bin exists in filesystem
linux-firmware: /usr/lib/firmware/kaweth/trigger_code.bin exists in filesystem
linux-firmware: /usr/lib/firmware/kaweth/trigger_code_fix.bin exists in filesystem
linux-firmware: /usr/lib/firmware/keyspan/mpr.fw exists in filesystem
linux-firmware: /usr/lib/firmware/keyspan/usa18x.fw exists in filesystem
linux-firmware: /usr/lib/firmware/keyspan/usa19.fw exists in filesystem
linux-firmware: /usr/lib/firmware/keyspan/usa19qi.fw exists in filesystem
linux-firmware: /usr/lib/firmware/keyspan/usa19qw.fw exists in filesystem
linux-firmware: /usr/lib/firmware/keyspan/usa19w.fw exists in filesystem
linux-firmware: /usr/lib/firmware/keyspan/usa28.fw exists in filesystem
linux-firmware: /usr/lib/firmware/keyspan/usa28x.fw exists in filesystem
linux-firmware: /usr/lib/firmware/keyspan/usa28xa.fw exists in filesystem
linux-firmware: /usr/lib/firmware/keyspan/usa28xb.fw exists in filesystem
linux-firmware: /usr/lib/firmware/keyspan/usa49w.fw exists in filesystem
linux-firmware: /usr/lib/firmware/keyspan/usa49wlc.fw exists in filesystem
linux-firmware: /usr/lib/firmware/keyspan_pda/Makefile exists in filesystem
linux-firmware: /usr/lib/firmware/keyspan_pda/keyspan_pda.S exists in filesystem
linux-firmware: /usr/lib/firmware/keyspan_pda/keyspan_pda.fw exists in filesystem
linux-firmware: /usr/lib/firmware/keyspan_pda/xircom_pgs.S exists in filesystem
linux-firmware: /usr/lib/firmware/keyspan_pda/xircom_pgs.fw exists in filesystem
linux-firmware: /usr/lib/firmware/korg/k1212.dsp exists in filesystem
linux-firmware: /usr/lib/firmware/lbtf_usb.bin exists in filesystem
linux-firmware: /usr/lib/firmware/lgs8g75.fw exists in filesystem
linux-firmware: /usr/lib/firmware/libertas/cf8381.bin exists in filesystem
linux-firmware: /usr/lib/firmware/libertas/cf8381_helper.bin exists in filesystem
linux-firmware: /usr/lib/firmware/libertas/cf8385.bin exists in filesystem
linux-firmware: /usr/lib/firmware/libertas/cf8385_helper.bin exists in filesystem
linux-firmware: /usr/lib/firmware/libertas/gspi8682.bin exists in filesystem
linux-firmware: /usr/lib/firmware/libertas/gspi8682_helper.bin exists in filesystem
linux-firmware: /usr/lib/firmware/libertas/gspi8686_v9.bin exists in filesystem
linux-firmware: /usr/lib/firmware/libertas/gspi8686_v9_helper.bin exists in filesystem
linux-firmware: /usr/lib/firmware/libertas/gspi8688.bin exists in filesystem
linux-firmware: /usr/lib/firmware/libertas/gspi8688_helper.bin exists in filesystem
linux-firmware: /usr/lib/firmware/libertas/lbtf_sdio.bin exists in filesystem
linux-firmware: /usr/lib/firmware/libertas/sd8385.bin exists in filesystem
linux-firmware: /usr/lib/firmware/libertas/sd8385_helper.bin exists in filesystem
linux-firmware: /usr/lib/firmware/libertas/sd8682.bin exists in filesystem
linux-firmware: /usr/lib/firmware/libertas/sd8682_helper.bin exists in filesystem
linux-firmware: /usr/lib/firmware/libertas/sd8686_v8.bin exists in filesystem
linux-firmware: /usr/lib/firmware/libertas/sd8686_v8_helper.bin exists in filesystem
linux-firmware: /usr/lib/firmware/libertas/sd8686_v9.bin exists in filesystem
linux-firmware: /usr/lib/firmware/libertas/sd8686_v9_helper.bin exists in filesystem
linux-firmware: /usr/lib/firmware/libertas/sd8688.bin exists in filesystem
linux-firmware: /usr/lib/firmware/libertas/sd8688_helper.bin exists in filesystem
linux-firmware: /usr/lib/firmware/libertas/usb8388_olpc.bin exists in filesystem
linux-firmware: /usr/lib/firmware/libertas/usb8388_v5.bin exists in filesystem
linux-firmware: /usr/lib/firmware/libertas/usb8388_v9.bin exists in filesystem
linux-firmware: /usr/lib/firmware/libertas/usb8682.bin exists in filesystem
linux-firmware: /usr/lib/firmware/matrox/g200_warp.fw exists in filesystem
linux-firmware: /usr/lib/firmware/matrox/g400_warp.fw exists in filesystem
linux-firmware: /usr/lib/firmware/mrvl/sd8787_uapsta.bin exists in filesystem
linux-firmware: /usr/lib/firmware/mts_cdma.fw exists in filesystem
linux-firmware: /usr/lib/firmware/mts_edge.fw exists in filesystem
linux-firmware: /usr/lib/firmware/mts_gsm.fw exists in filesystem
linux-firmware: /usr/lib/firmware/mts_mt9234mu.fw exists in filesystem
linux-firmware: /usr/lib/firmware/mts_mt9234zba.fw exists in filesystem
linux-firmware: /usr/lib/firmware/mwl8335_duplex.fw exists in filesystem
linux-firmware: /usr/lib/firmware/mwl8k/fmimage_8366.fw exists in filesystem
linux-firmware: /usr/lib/firmware/mwl8k/fmimage_8366_ap-1.fw exists in filesystem
linux-firmware: /usr/lib/firmware/mwl8k/fmimage_8366_ap-2.fw exists in filesystem
linux-firmware: /usr/lib/firmware/mwl8k/fmimage_8687.fw exists in filesystem
linux-firmware: /usr/lib/firmware/mwl8k/helper_8366.fw exists in filesystem
linux-firmware: /usr/lib/firmware/mwl8k/helper_8687.fw exists in filesystem
linux-firmware: /usr/lib/firmware/myri10ge_eth_z8e.dat exists in filesystem
linux-firmware: /usr/lib/firmware/myri10ge_ethp_z8e.dat exists in filesystem
linux-firmware: /usr/lib/firmware/myri10ge_rss_eth_z8e.dat exists in filesystem
linux-firmware: /usr/lib/firmware/myri10ge_rss_ethp_z8e.dat exists in filesystem
linux-firmware: /usr/lib/firmware/myricom/lanai.bin exists in filesystem
linux-firmware: /usr/lib/firmware/ositech/Xilinx7OD.bin exists in filesystem
linux-firmware: /usr/lib/firmware/phanfw.bin exists in filesystem
linux-firmware: /usr/lib/firmware/ql2100_fw.bin exists in filesystem
linux-firmware: /usr/lib/firmware/ql2200_fw.bin exists in filesystem
linux-firmware: /usr/lib/firmware/ql2300_fw.bin exists in filesystem
linux-firmware: /usr/lib/firmware/ql2322_fw.bin exists in filesystem
linux-firmware: /usr/lib/firmware/ql2400_fw.bin exists in filesystem
linux-firmware: /usr/lib/firmware/ql2500_fw.bin exists in filesystem
linux-firmware: /usr/lib/firmware/qlogic/1040.bin exists in filesystem
linux-firmware: /usr/lib/firmware/qlogic/12160.bin exists in filesystem
linux-firmware: /usr/lib/firmware/qlogic/1280.bin exists in filesystem
linux-firmware: /usr/lib/firmware/qlogic/isp1000.bin exists in filesystem
linux-firmware: /usr/lib/firmware/qlogic/sd7220.fw exists in filesystem
linux-firmware: /usr/lib/firmware/r128/r128_cce.bin exists in filesystem
linux-firmware: /usr/lib/firmware/radeon/BARTS_mc.bin exists in filesystem
linux-firmware: /usr/lib/firmware/radeon/BARTS_me.bin exists in filesystem
linux-firmware: /usr/lib/firmware/radeon/BARTS_pfp.bin exists in filesystem
linux-firmware: /usr/lib/firmware/radeon/BTC_rlc.bin exists in filesystem
linux-firmware: /usr/lib/firmware/radeon/CAICOS_mc.bin exists in filesystem
linux-firmware: /usr/lib/firmware/radeon/CAICOS_me.bin exists in filesystem
linux-firmware: /usr/lib/firmware/radeon/CAICOS_pfp.bin exists in filesystem
linux-firmware: /usr/lib/firmware/radeon/CAYMAN_mc.bin exists in filesystem
linux-firmware: /usr/lib/firmware/radeon/CAYMAN_me.bin exists in filesystem
linux-firmware: /usr/lib/firmware/radeon/CAYMAN_pfp.bin exists in filesystem
linux-firmware: /usr/lib/firmware/radeon/CAYMAN_rlc.bin exists in filesystem
linux-firmware: /usr/lib/firmware/radeon/CEDAR_me.bin exists in filesystem
linux-firmware: /usr/lib/firmware/radeon/CEDAR_pfp.bin exists in filesystem
linux-firmware: /usr/lib/firmware/radeon/CEDAR_rlc.bin exists in filesystem
linux-firmware: /usr/lib/firmware/radeon/CYPRESS_me.bin exists in filesystem
linux-firmware: /usr/lib/firmware/radeon/CYPRESS_pfp.bin exists in filesystem
linux-firmware: /usr/lib/firmware/radeon/CYPRESS_rlc.bin exists in filesystem
linux-firmware: /usr/lib/firmware/radeon/JUNIPER_me.bin exists in filesystem
linux-firmware: /usr/lib/firmware/radeon/JUNIPER_pfp.bin exists in filesystem
linux-firmware: /usr/lib/firmware/radeon/JUNIPER_rlc.bin exists in filesystem
linux-firmware: /usr/lib/firmware/radeon/PALM_me.bin exists in filesystem
linux-firmware: /usr/lib/firmware/radeon/PALM_pfp.bin exists in filesystem
linux-firmware: /usr/lib/firmware/radeon/R100_cp.bin exists in filesystem
linux-firmware: /usr/lib/firmware/radeon/R200_cp.bin exists in filesystem
linux-firmware: /usr/lib/firmware/radeon/R300_cp.bin exists in filesystem
linux-firmware: /usr/lib/firmware/radeon/R420_cp.bin exists in filesystem
linux-firmware: /usr/lib/firmware/radeon/R520_cp.bin exists in filesystem
linux-firmware: /usr/lib/firmware/radeon/R600_me.bin exists in filesystem
linux-firmware: /usr/lib/firmware/radeon/R600_pfp.bin exists in filesystem
linux-firmware: /usr/lib/firmware/radeon/R600_rlc.bin exists in filesystem
linux-firmware: /usr/lib/firmware/radeon/R700_rlc.bin exists in filesystem
linux-firmware: /usr/lib/firmware/radeon/REDWOOD_me.bin exists in filesystem
linux-firmware: /usr/lib/firmware/radeon/REDWOOD_pfp.bin exists in filesystem
linux-firmware: /usr/lib/firmware/radeon/REDWOOD_rlc.bin exists in filesystem
linux-firmware: /usr/lib/firmware/radeon/RS600_cp.bin exists in filesystem
linux-firmware: /usr/lib/firmware/radeon/RS690_cp.bin exists in filesystem
linux-firmware: /usr/lib/firmware/radeon/RS780_me.bin exists in filesystem
linux-firmware: /usr/lib/firmware/radeon/RS780_pfp.bin exists in filesystem
linux-firmware: /usr/lib/firmware/radeon/RV610_me.bin exists in filesystem
linux-firmware: /usr/lib/firmware/radeon/RV610_pfp.bin exists in filesystem
linux-firmware: /usr/lib/firmware/radeon/RV620_me.bin exists in filesystem
linux-firmware: /usr/lib/firmware/radeon/RV620_pfp.bin exists in filesystem
linux-firmware: /usr/lib/firmware/radeon/RV630_me.bin exists in filesystem
linux-firmware: /usr/lib/firmware/radeon/RV630_pfp.bin exists in filesystem
linux-firmware: /usr/lib/firmware/radeon/RV635_me.bin exists in filesystem
linux-firmware: /usr/lib/firmware/radeon/RV635_pfp.bin exists in filesystem
linux-firmware: /usr/lib/firmware/radeon/RV670_me.bin exists in filesystem
linux-firmware: /usr/lib/firmware/radeon/RV670_pfp.bin exists in filesystem
linux-firmware: /usr/lib/firmware/radeon/RV710_me.bin exists in filesystem
linux-firmware: /usr/lib/firmware/radeon/RV710_pfp.bin exists in filesystem
linux-firmware: /usr/lib/firmware/radeon/RV730_me.bin exists in filesystem
linux-firmware: /usr/lib/firmware/radeon/RV730_pfp.bin exists in filesystem
linux-firmware: /usr/lib/firmware/radeon/RV770_me.bin exists in filesystem
linux-firmware: /usr/lib/firmware/radeon/RV770_pfp.bin exists in filesystem
linux-firmware: /usr/lib/firmware/radeon/SUMO2_me.bin exists in filesystem
linux-firmware: /usr/lib/firmware/radeon/SUMO2_pfp.bin exists in filesystem
linux-firmware: /usr/lib/firmware/radeon/SUMO_me.bin exists in filesystem
linux-firmware: /usr/lib/firmware/radeon/SUMO_pfp.bin exists in filesystem
linux-firmware: /usr/lib/firmware/radeon/SUMO_rlc.bin exists in filesystem
linux-firmware: /usr/lib/firmware/radeon/TURKS_mc.bin exists in filesystem
linux-firmware: /usr/lib/firmware/radeon/TURKS_me.bin exists in filesystem
linux-firmware: /usr/lib/firmware/radeon/TURKS_pfp.bin exists in filesystem
linux-firmware: /usr/lib/firmware/rt2561.bin exists in filesystem
linux-firmware: /usr/lib/firmware/rt2561s.bin exists in filesystem
linux-firmware: /usr/lib/firmware/rt2661.bin exists in filesystem
linux-firmware: /usr/lib/firmware/rt2860.bin exists in filesystem
linux-firmware: /usr/lib/firmware/rt2870.bin exists in filesystem
linux-firmware: /usr/lib/firmware/rt3070.bin exists in filesystem
linux-firmware: /usr/lib/firmware/rt3071.bin exists in filesystem
linux-firmware: /usr/lib/firmware/rt3090.bin exists in filesystem
linux-firmware: /usr/lib/firmware/rt73.bin exists in filesystem
linux-firmware: /usr/lib/firmware/rtl_nic/rtl8105e-1.fw exists in filesystem
linux-firmware: /usr/lib/firmware/rtl_nic/rtl8168d-1.fw exists in filesystem
linux-firmware: /usr/lib/firmware/rtl_nic/rtl8168d-2.fw exists in filesystem
linux-firmware: /usr/lib/firmware/rtl_nic/rtl8168e-1.fw exists in filesystem
linux-firmware: /usr/lib/firmware/rtl_nic/rtl8168e-2.fw exists in filesystem
linux-firmware: /usr/lib/firmware/rtl_nic/rtl8168e-3.fw exists in filesystem
linux-firmware: /usr/lib/firmware/rtl_nic/rtl8168f-1.fw exists in filesystem
linux-firmware: /usr/lib/firmware/rtl_nic/rtl8168f-2.fw exists in filesystem
linux-firmware: /usr/lib/firmware/rtl_nic/rtl8402-1.fw exists in filesystem
linux-firmware: /usr/lib/firmware/rtl_nic/rtl8411-1.fw exists in filesystem
linux-firmware: /usr/lib/firmware/rtlwifi/rtl8192cfw.bin exists in filesystem
linux-firmware: /usr/lib/firmware/rtlwifi/rtl8192cufw.bin exists in filesystem
linux-firmware: /usr/lib/firmware/rtlwifi/rtl8192defw.bin exists in filesystem
linux-firmware: /usr/lib/firmware/rtlwifi/rtl8192sefw.bin exists in filesystem
linux-firmware: /usr/lib/firmware/rtlwifi/rtl8712u.bin exists in filesystem
linux-firmware: /usr/lib/firmware/s2250.fw exists in filesystem
linux-firmware: /usr/lib/firmware/s2250_loader.fw exists in filesystem
linux-firmware: /usr/lib/firmware/sb16/alaw_main.csp exists in filesystem
linux-firmware: /usr/lib/firmware/sb16/ima_adpcm_capture.csp exists in filesystem
linux-firmware: /usr/lib/firmware/sb16/ima_adpcm_init.csp exists in filesystem
linux-firmware: /usr/lib/firmware/sb16/ima_adpcm_playback.csp exists in filesystem
linux-firmware: /usr/lib/firmware/sb16/mulaw_main.csp exists in filesystem
linux-firmware: /usr/lib/firmware/slicoss/gbdownload.sys exists in filesystem
linux-firmware: /usr/lib/firmware/slicoss/gbrcvucode.sys exists in filesystem
linux-firmware: /usr/lib/firmware/slicoss/oasisdbgdownload.sys exists in filesystem
linux-firmware: /usr/lib/firmware/slicoss/oasisdownload.sys exists in filesystem
linux-firmware: /usr/lib/firmware/slicoss/oasisrcvucode.sys exists in filesystem
linux-firmware: /usr/lib/firmware/sun/cassini.bin exists in filesystem
linux-firmware: /usr/lib/firmware/sxg/saharadbgdownloadB.sys exists in filesystem
linux-firmware: /usr/lib/firmware/sxg/saharadownloadB.sys exists in filesystem
linux-firmware: /usr/lib/firmware/tehuti/bdx.bin exists in filesystem
linux-firmware: /usr/lib/firmware/ti-connectivity/TIInit_7.2.31.bts exists in filesystem
linux-firmware: /usr/lib/firmware/ti-connectivity/wl1271-fw-2.bin exists in filesystem
linux-firmware: /usr/lib/firmware/ti-connectivity/wl1271-fw-ap.bin exists in filesystem
linux-firmware: /usr/lib/firmware/ti-connectivity/wl1271-fw.bin exists in filesystem
linux-firmware: /usr/lib/firmware/ti-connectivity/wl1271-nvs.bin exists in filesystem
linux-firmware: /usr/lib/firmware/ti-connectivity/wl127x-fw-3.bin exists in filesystem
linux-firmware: /usr/lib/firmware/ti-connectivity/wl127x-fw-plt-3.bin exists in filesystem
linux-firmware: /usr/lib/firmware/ti-connectivity/wl127x-nvs.bin exists in filesystem
linux-firmware: /usr/lib/firmware/ti-connectivity/wl128x-fw-3.bin exists in filesystem
linux-firmware: /usr/lib/firmware/ti-connectivity/wl128x-fw-ap.bin exists in filesystem
linux-firmware: /usr/lib/firmware/ti-connectivity/wl128x-fw-plt-3.bin exists in filesystem
linux-firmware: /usr/lib/firmware/ti-connectivity/wl128x-fw.bin exists in filesystem
linux-firmware: /usr/lib/firmware/ti-connectivity/wl128x-nvs.bin exists in filesystem
linux-firmware: /usr/lib/firmware/ti-connectivity/wl12xx-nvs.bin exists in filesystem
linux-firmware: /usr/lib/firmware/ti_3410.fw exists in filesystem
linux-firmware: /usr/lib/firmware/ti_5052.fw exists in filesystem
linux-firmware: /usr/lib/firmware/tigon/tg3.bin exists in filesystem
linux-firmware: /usr/lib/firmware/tigon/tg3_tso.bin exists in filesystem
linux-firmware: /usr/lib/firmware/tigon/tg3_tso5.bin exists in filesystem
linux-firmware: /usr/lib/firmware/tlg2300_firmware.bin exists in filesystem
linux-firmware: /usr/lib/firmware/tr_smctr.bin exists in filesystem
linux-firmware: /usr/lib/firmware/ttusb-budget/dspbootcode.bin exists in filesystem
linux-firmware: /usr/lib/firmware/ueagle-atm/930-fpga.bin exists in filesystem
linux-firmware: /usr/lib/firmware/ueagle-atm/CMV4p.bin.v2 exists in filesystem
linux-firmware: /usr/lib/firmware/ueagle-atm/CMV9i.bin exists in filesystem
linux-firmware: /usr/lib/firmware/ueagle-atm/CMV9p.bin exists in filesystem
linux-firmware: /usr/lib/firmware/ueagle-atm/CMVei.bin exists in filesystem
linux-firmware: /usr/lib/firmware/ueagle-atm/CMVeiWO.bin exists in filesystem
linux-firmware: /usr/lib/firmware/ueagle-atm/CMVep.bin exists in filesystem
linux-firmware: /usr/lib/firmware/ueagle-atm/CMVepES.bin exists in filesystem
linux-firmware: /usr/lib/firmware/ueagle-atm/CMVepES03.bin exists in filesystem
linux-firmware: /usr/lib/firmware/ueagle-atm/CMVepFR.bin exists in filesystem
linux-firmware: /usr/lib/firmware/ueagle-atm/CMVepFR04.bin exists in filesystem
linux-firmware: /usr/lib/firmware/ueagle-atm/CMVepFR10.bin exists in filesystem
linux-firmware: /usr/lib/firmware/ueagle-atm/CMVepIT.bin exists in filesystem
linux-firmware: /usr/lib/firmware/ueagle-atm/CMVepWO.bin exists in filesystem
linux-firmware: /usr/lib/firmware/ueagle-atm/DSP4p.bin exists in filesystem
linux-firmware: /usr/lib/firmware/ueagle-atm/DSP9i.bin exists in filesystem
linux-firmware: /usr/lib/firmware/ueagle-atm/DSP9p.bin exists in filesystem
linux-firmware: /usr/lib/firmware/ueagle-atm/DSPei.bin exists in filesystem
linux-firmware: /usr/lib/firmware/ueagle-atm/DSPep.bin exists in filesystem
linux-firmware: /usr/lib/firmware/ueagle-atm/adi930.fw exists in filesystem
linux-firmware: /usr/lib/firmware/ueagle-atm/eagleI.fw exists in filesystem
linux-firmware: /usr/lib/firmware/ueagle-atm/eagleII.fw exists in filesystem
linux-firmware: /usr/lib/firmware/ueagle-atm/eagleIII.fw exists in filesystem
linux-firmware: /usr/lib/firmware/ueagle-atm/eagleIV.fw exists in filesystem
linux-firmware: /usr/lib/firmware/usbdux/Makefile_dux exists in filesystem
linux-firmware: /usr/lib/firmware/usbdux/README.dux exists in filesystem
linux-firmware: /usr/lib/firmware/usbdux/fx2-include.asm exists in filesystem
linux-firmware: /usr/lib/firmware/usbdux/usbdux_firmware.asm exists in filesystem
linux-firmware: /usr/lib/firmware/usbdux/usbduxfast_firmware.asm exists in filesystem
linux-firmware: /usr/lib/firmware/usbdux/usbduxsigma_firmware.asm exists in filesystem
linux-firmware: /usr/lib/firmware/usbdux_firmware.bin exists in filesystem
linux-firmware: /usr/lib/firmware/usbduxfast_firmware.bin exists in filesystem
linux-firmware: /usr/lib/firmware/usbduxsigma_firmware.bin exists in filesystem
linux-firmware: /usr/lib/firmware/v4l-cx231xx-avcore-01.fw exists in filesystem
linux-firmware: /usr/lib/firmware/v4l-cx23418-apu.fw exists in filesystem
linux-firmware: /usr/lib/firmware/v4l-cx23418-cpu.fw exists in filesystem
linux-firmware: /usr/lib/firmware/v4l-cx23418-dig.fw exists in filesystem
linux-firmware: /usr/lib/firmware/v4l-cx23885-avcore-01.fw exists in filesystem
linux-firmware: /usr/lib/firmware/v4l-cx23885-enc.fw exists in filesystem
linux-firmware: /usr/lib/firmware/v4l-cx25840.fw exists in filesystem
linux-firmware: /usr/lib/firmware/vicam/firmware.fw exists in filesystem
linux-firmware: /usr/lib/firmware/vntwusb.fw exists in filesystem
linux-firmware: /usr/lib/firmware/vxge/X3fw-pxe.ncf exists in filesystem
linux-firmware: /usr/lib/firmware/vxge/X3fw.ncf exists in filesystem
linux-firmware: /usr/lib/firmware/whiteheat.fw exists in filesystem
linux-firmware: /usr/lib/firmware/whiteheat_loader.fw exists in filesystem
linux-firmware: /usr/lib/firmware/yam/1200.bin exists in filesystem
linux-firmware: /usr/lib/firmware/yam/9600.bin exists in filesystem
linux-firmware: /usr/lib/firmware/yamaha/ds1_ctrl.fw exists in filesystem
linux-firmware: /usr/lib/firmware/yamaha/ds1_dsp.fw exists in filesystem
linux-firmware: /usr/lib/firmware/yamaha/ds1e_ctrl.fw exists in filesystem
linux-firmware: /usr/lib/firmware/yamaha/yss225_registers.bin exists in filesystem
linux-firmware: /usr/share/licenses/linux-firmware/LICENCE.Marvell exists in filesystem
linux-firmware: /usr/share/licenses/linux-firmware/LICENCE.OLPC exists in filesystem
linux-firmware: /usr/share/licenses/linux-firmware/LICENCE.agere exists in filesystem
linux-firmware: /usr/share/licenses/linux-firmware/LICENCE.atheros_firmware exists in filesystem
linux-firmware: /usr/share/licenses/linux-firmware/LICENCE.broadcom_bcm43xx exists in filesystem
linux-firmware: /usr/share/licenses/linux-firmware/LICENCE.chelsio_firmware exists in filesystem
linux-firmware: /usr/share/licenses/linux-firmware/LICENCE.ene_firmware exists in filesystem
linux-firmware: /usr/share/licenses/linux-firmware/LICENCE.i2400m exists in filesystem
linux-firmware: /usr/share/licenses/linux-firmware/LICENCE.iwlwifi_firmware exists in filesystem
linux-firmware: /usr/share/licenses/linux-firmware/LICENCE.mwl8335 exists in filesystem
linux-firmware: /usr/share/licenses/linux-firmware/LICENCE.myri10ge_firmware exists in filesystem
linux-firmware: /usr/share/licenses/linux-firmware/LICENCE.phanfw exists in filesystem
linux-firmware: /usr/share/licenses/linux-firmware/LICENCE.qla2xxx exists in filesystem
linux-firmware: /usr/share/licenses/linux-firmware/LICENCE.ralink-firmware.txt exists in filesystem
linux-firmware: /usr/share/licenses/linux-firmware/LICENCE.rtlwifi_firmware.txt exists in filesystem
linux-firmware: /usr/share/licenses/linux-firmware/LICENCE.tda7706-firmware.txt exists in filesystem
linux-firmware: /usr/share/licenses/linux-firmware/LICENCE.ti-connectivity exists in filesystem
linux-firmware: /usr/share/licenses/linux-firmware/LICENCE.ueagle-atm4-firmware exists in filesystem
linux-firmware: /usr/share/licenses/linux-firmware/LICENCE.via_vt6656 exists in filesystem
linux-firmware: /usr/share/licenses/linux-firmware/LICENCE.xc5000 exists in filesystem
linux-firmware: /usr/share/licenses/linux-firmware/LICENSE.dib0700 exists in filesystem
linux-firmware: /usr/share/licenses/linux-firmware/LICENSE.radeon_rlc exists in filesystem
linux-firmware: /usr/share/licenses/linux-firmware/WHENCE exists in filesystem
Errors occurred, no packages were upgraded.
Last edited by Swarfega (2012-05-17 08:59:31) -
InfoSpoke fails with message "Could not open file on application server"
BW Experts,
I created an InfoSpoke that is configured to extract to a flat file. The name of the file is specified using a logical filename. During extraction, the infospoke reports the error message "Could not open file on application server" adnd marks the extraction process as red(failed). I have tried to run the InfoSpoke in background mode and in dialog mode and the same error appears. After i run in dialog mode, i checked SU53 for authorization errors and did not find any. I also tried changing the Logical filename setup in transaction FILE to a more "friendly" directory in which i'm sure i have authorizations (e.g. my UNIX home directory) and im still getting errors.
Can you please share your thoughts on this? Any help will greatly appreciated. I also promise to award points.Hi Nagesh,
Thanks for helping out.
If i configure the InfoSpoke to download to a file using "File Name" option and also check the "Application server" checkbox, the extract works correctly (extraction to the defualt SAP path and filename=infospoke name). If i configure the InfoSpoke to download to the local workstation, the InfoSpoke also works correctly. It's only when i configure it to download to the application server and use the "Logical filename" option, that i encounter a failed extract.
Here are the messages is the Open Hub Monitor:
(red icon) Request No.147515
0 Data Records
Runtime 1 sec.
(red icon)Run No. 1
0 Data Records
Runtime 1 sec.
Messages for Run
Extraction is running RSBO 305
Could not open file on application server RSBO 214
Request 147515 was terminated before extraction RSBO 326
Request 1475151: Error occured RSBO 322
If i clink on the error message, no messages nor clues are displayed. Note, this is a new InfoSpoke that is currently in the dev system.
Please help. -
I attempted to update itunes to the newest upgrade, and the upgrade was unsucceful, and now this error comes up everytime i try to open itunes (it wont open at all). the error says
Could not open key:
HKEYLOCALMACHINE\Software\Classes\.wav\OpenWithList\iTunes.exe.
Verify that you have sufficent access to that key, or contact your support personnel.
This makes no sense since this is on my home PChmmm. okay, if you're currently just getting the "itunes has encountered an error ..." let's try the following technique.
preliminaries
download and save a fresh copy of the itunes 6.0.1.3 installer to your hard drive. (eventually we're going to run the install from there rather than online.)
iTunes 6.0.1.3 Installer
switch off any antivirus and antispyware applications prior to any uninstalls, installs or repair installs.
uninstall
use the complete uninstall instructions given in the following document to remove your existing itunes and quicktime:
Troubleshooting iTunes, iPod Software, and QuickTime installation on Windows
... and if you run into problems on the uninstall, try using the Installer Cleanup utility:
Description of the Windows Installer CleanUp Utility
reboot after uninstalling.
reinstall
remember to switch off your antivirus and antispyware.
reinstall itunes using the 6.0.1.3 installer you downloaded previously.
if you get the "itunes has encountered a problem ..." error message again after that install, first check to see if your Quicktime will launch. if you get an error message when you try to launch quicktime, try using the following technique:
iTunes 6 for Windows unexpectedly quits when opened
keep us posted on your progress.
love, b -
Adobe Photoshop CS6 Extended
"Could not open a scratch file because the file is locked, you do not have necessary access permissions, or another program is using the file."
I've tried finding and checking and fixing permissions but no success.
This happened from one day to the next. I think it has to do with the sn attached to the disk rather then the motherboard. I have the suite co-installed with Symphony 5.05. I've tried reinstalling.
What's to b done? The rest of the Creative Suite 6 (AE, AI etc.) works fine.
Anyone...?
LouiHave you tried restoring the Preferences yet?
-
Adobe Reader could not open 'A9R7D1F.tmp'
Greetings~
I have seen others with this issue, but none of their solutions have been able to fix my problem.
When attempting to open a PDF document from a web site, I receive the following error:
"Adobe Reader could not open 'A9R7D1F.tmp' because it is either not a supported file type of because the file has been damaged (for example, it was sent as an email attachment and wasn't correctly decoded)."
This is limited to a specific set of computers. Others within the organization function appropriately. As such, it is not a web server or network problem. Here are the specifics of the offending machine(s): Windows 7, Internet Explorer 8, Adobe Reader 9.3.2. Note that other machines with this same specs function appropriately. I have confirmed there are no differing group policies and all are within the same subnet.
Here is what I have tried. After each item, the browser was closed and/or system rebooted. Everyone of these tests resulted with the same error.
Deleted all history in IE (cookies, temporary files, history, etc.).
Uninstalll Reader, reboot, re-install Reader, reboot.
Saved the PDF to the local desktop and tried to open that way.
Installed an older version of Reader.
Ensured the following Reader settings are selected: Display PDF in Browser, Allow Fast Web View, Allow Speculative Downloading in the background (which match machines that are successful).
Ensure IE browser settings are configured to "Automatically" check for newer versions of stored pages.
Ensure PDF document is smaller than allowable disk space limit within IE.
Can anyone help me with this? I am out of ideas!
Thank you.If you are generating files with anything before %PDF, these files are faulty. It's never been allowed, but Reader used to tolerate it for compatibility with an obscure Mac format.
-
I am getting multiple authentication prompts when I try to open or create a new .docx or .xslx document from SharePoint 2010.
I tried this on different machines and on different browsers (IE and Firefox) and see the same behavior. I am the site collection administrator. I see the same behavior on other sites also. Other users are also seeing the same behavior.
If I download the document, I can open it without any issues.
The Web Application IIS authentication settings is NTLM and Client Integration is enabled.Hi shankze,
According to your description, my understanding is that you could not open the documents because of the authentications.
Go to IIS, make sure that the Security TokenServiceApplication pool is started.
Please do as the followings, and compare the result:
Add your site to the Trusted Sites Internet Zone.
Go to Internet Options - Security - Highlight the Trusted Sites Check Mark - click on custom level - scroll to the bottom and in the user authentication section select "Automatic logon with current username and password."
Also, you can do via group policy in DC server.
More information, please refer to the link:
http://www.networkadminsecrets.com/2011/08/sharepoint-2010-authentication-prompts.html
I hope this helps.
Thanks,
Wendy
Wendy Li
TechNet Community Support -
Can't access CD Drive: Could not open CD handler, 32.
My CD drive isn't showing up in iTunes, so I ran the diagnostic tool. Everything checked out except that I got "Unable to access audio CD" with a red dot next to it.
This is the output of the diagnostic tool, has anyone else encountered this Could not open CD handler, 32 issue?
Microsoft Windows 7 x64 Business Edition Service Pack 1 (Build 7601)
LENOVO 4313CTO
iTunes 11.2.2.3
QuickTime not available
FairPlay 2.6.12
Apple Application Support 3.0.3
iPod Updater Library 11.1f5
VoiceOver Kit 1.4.2 (222093/222742)
CD Driver 2.2.3.0
CD Driver DLL 2.1.3.1
Apple Mobile Device 7.1.1.3
Apple Mobile Device Driver 1.64.0.0
Bonjour 3.0.0.10 (333.10)
Gracenote SDK 1.9.6.502
Gracenote MusicID 1.9.6.115
Gracenote Submit 1.9.6.143
Gracenote DSP 1.9.6.45
iTunes Serial Number 0040B50812948A28
Current user is not an administrator.
The current local date and time is 2014-06-13 12:19:35.
iTunes is not running in safe mode.
WebKit accelerated compositing is enabled.
HDCP is supported.
Core Media is supported.
Video Display Information
NVIDIA, NVIDIA NVS 3100M
Intel Corporation, Intel(R) HD Graphics
**** External Plug-ins Information ****
No external plug-ins installed.
Genius ID: 2c11483344b4160ef38c549044196dd7
iPodService 11.2.2.3 (x64) is currently running.
iTunesHelper 11.2.2.3 is currently running.
Apple Mobile Device service 3.3.0.0 is currently running.
**** CD/DVD Drive Tests ****
No drivers in LowerFilters.
UpperFilters: GEARAspiWDM (2.2.3.0),
E: HL-DT-ST DVDRAM GT30N, Rev LT10
Audio CD in drive.
Could not open CD handler, 32. There is a problem with the installation of the drive in Windows or the drive contains a copy protected CD.
Audio CD reading succeeded.
Get drive speed succeeded.
The drive CDR speeds are: 10 16 24.
The drive CDRW speeds are: 10.
The drive DVDR speeds are: 10.
The drive DVDRW speeds are: 10.
Error Correction is turned on for importing audio CDs.
Writing CD text is turned on in the preferences. If you’re having problems burning CDs, try turning this preference off.
Force Optical Power Calibration before burn is turned on in the preferences.Hi, Mathew -
Here is a method that should work provided your G4 is an (AGP) model or later -
Restart. Immediately press the Option key, keep it held down until Startup Manager displays.
Article #106178 - Startup Manager: How to Select a Startup Volume
Once Startup Manager is up, press the Command-. (Command-period) keys. That should open the tray for the optical drive.
If the drive has a disk in it now, there's an additional technique - boot the machine, immediately press and hold down the mouse button, keep it held down. That's a hardware-based command to eject all removable media.
If the drive has a button on the door, you can also try restarting, then immediately begin pushing the button - there's a point during the first part of startup where the drive is energized but has not yet begun to spin up, and it should respond to the button push at that time.
If all attempts fail, it's time to consider whether the drive has failed, or if its cable connections have worked loose. -
I am having a problem upgrading from iTunes 9.0.07 to 9.0.2. I've been trying to use the 64-bit installer and have tried disabling my anti-virus software.
I had this same problem when I was running Windows Vista Home Premium SP2 64-bit on this same computer.
At first, when I would download, I had to Download Only and then install.
When I tried to install iTunes manually, it would load very slowly at Copying Files and then say it was Rolling Back Action. After that, it would say that, "The installer encountered errors before iTunes could be configured."
I tried everything people suggested on help forums, the discussions here, and the Trouble installing iTunes or QuickTime for Windows help article in Support.
After uninstalling iTunes, making a backup of my iTunes music from Documents and getting rid of anything else iTunes, QuickTime or Apple related, I tried downloading again from the website (using Firefox). I had the problem that iTunes said it couldn't be downloaded without QuickTime. Okay, easy fix, right? I tried downloading and installing QuickTime and these errors came up:
Could not open key:
UNKNOWN\Components\69413F169B198734FA40BC8B73511DB0\108B43C0CEA676640B35306AE7D2 4051.
Verify that you have sufficient access to that key, or contact your support personnel.
and
Could not open key:
UNKNOWN\Components\9C4307835821FFF47864EE6DABC09AA9\EA2C92A1FBE18F42A12C111C5AAD DDA.
Verify that you have sufficient access to that key, or contact your support personnel.
So then I tried doing what jnd73 said in a different discussion: http://discussions.apple.com/thread.jspa?threadID=2151409&tstart=0&messageID=102 87668#10287668
And I found I couldn't do half of what jnd73 said. Either because it already knows I'm the admin, or because I don't have sufficient access to the key. I can't even get another admin user to download iTunes successfully. I don't know if it's a permissions issue.
The "The installer encountered errors before iTunes could be configured." problem started when I moved from Windows XP Home Edition SP3 32-bit to Windows Vista Home Premium SP1 (Had to update to SP2) 64-bit. I moved from a separate computer (Toshiba Satellite L35-S2151) to this one. I had to move all of my files from my last backup and re-download applications. I think what I did was I moved all of my old iTunes Program Files along with everything instead of just the iTunes folder in My Documents. So, when I downloaded the new iTunes, it didn't make new folders and used the old ones. I was able to make iTunes recognize all of the music I didn't buy through iTunes after I manually found the files, but iTunes never updated correctly.
I'd think now that I got rid of all of the old folders that now I'd be able to install without any problems.
Can anyone help?I was having the same problem, but I found the solution to the problem.
First, click on Start and search "regedit" without the quotations. Open it up, click on "Edit: in the drop down menu. Next, click "Find" and search for your folder components, not the key component, which is in your case: 69413F169B198734FA40BC8B73511DB0
and
9C4307835821FFF47864EE6DABC09AA9
They should be folders, and inside the folders, there should be a key with the name of that 2nd key. Example, inside the 69413F169B198734FA40BC8B73511DB0 folder should be a key named 108B43C0CEA676640B35306AE7D24051, and the same for the other folder.
Now, to gain permissions for these keys, right-click on the folders, and select "Permissions". Where it says "Groups or User Names", click "Add". Then select "Advanced". Next, select "Find Now" and select the "Everyone" user. Click OK, then OK again, and you should be on the permissions window. For "Groups of User Names", select Everyone and select the "Full Control" check box for Everyone. Then click OK.
Do the same for the other folder. Be careful; for me, there was 3 folders with the same key name, and I repeated the steps above for all 3 in order to make it work. Just check the folders under your folder to see if it has the same name, and if it does, repeat the steps on that folder.
This method worked for me after trying a million different solutions. Hopefully, it works for you too. If it doesn't work, feel free to reply back. And if does work, please reply back, just so I know it did work.
Good luck =] -
During a standard iTunes upgrade to the latest version (11.1.4 for Windows Vista), the installation failed with the following error message: Could not open key: HKEY_CURRENT_USER\SOFTWARE\Apple Inc.\Internet Services. Does anyone have any advice as to how I can fix this and reinstall iTunes? When I try to open iTunes I get the following message: iTunes.exe. This application has failed to start because MSCVR80.dll was not found. Re-installing the application may fix this problem. When I try to run the installer I get the above error so I'm going round in circles!
Solved: I had somehow lost permission to access the HKEY above (or rather, its parent key HKEY_CURRENT_USER\SOFTWARE\Apple Inc.) so I went to the registry editor and checked the 'Full Control' box for the key and the installer now works.
I used this site to fix the MSCVR80.dll error: http://pcsupport.about.com/od/findbyerrormessage/a/msvcr80-dll-not-found-missing -error.htm -
Telnet not working i need help : Could not open connection to the host !!
hello all im back today with big problem with telnet i dont know why !!
i have to computers one of them in my home and the other one in my office both of them use windows 7 so
home PC internet IP : 82.205.100.161
office PC internet IP : 82.102.237.175
so i go to control panel and then to windows features and i check Telnet Client and Telnet server
then i turn off my firewall
then i start telnet service
then i execute netstat -ab to know telnet port :
[tlntsvr.exe]
TCP [::]:135 Hacker-HP:0 LISTENING
is there anythink i need to do to get that damn connection over internet NOT LAN !! pleaze help me i still get this sucks error : Could not open connection to the host
peace
Dr.BL@CKDeaTHHi,
Telnet server use TCP port 23 by default.
Here is a screenshot of my lab server,
To verify if the TCP port 23 has been opened, we can use the portqry tool.
Here is the download link,
http://www.microsoft.com/en-us/download/details.aspx?id=17148
Best Regards.
Steven Lee
TechNet Community Support -
Hi,
Fed up with seeing the spinning beach ball I decided to reformat my MacBook Pro...
After backing up everything on an external hard drive I put in the OSX install DVD, restarted the machine and held down 'C'.
I followed the install prcedure, clicking next a few times etc...
I then went into Utilities > Disk Utility. I chose 7-Pass to erase the Macintosh HD and set it off erasing.
I checked the process an hour in and message on screen read:
Secure disk erase failed with the error:
could not open disk
The internal hard drive no longer exists in the disk utility so I cant retry erasing it.
The only thing that appears in disk utility is the OSX install DVD.
I can't even shut down the mac as everything under the apple tab is greyed out!
I'm guessing this means my hard drive is broken right?
If anyone has any other ideas of what to try I'd really appreciate that.
How do I turn the machine off?
If my hard drive is gone then should I consider getting an SSD drive?
Any recommendations for such a drive would be great.
Hope you can help!Did you partition the drive?
Extended Hard Drive Preparation
1. Open Disk Utility in your Utilities folder. If you need to reformat your startup volume, then you must boot from your OS X Installer Disc. After the installer loads select your language and click on the Continue button. When the menu bar appears select Disk Utility from the Installer menu (Utilities menu for Tiger or Leopard.)
2. After DU loads select your hard drive (this is the entry with the mfgr.'s ID and size) from the left side list. Note the SMART status of the drive in DU's status area. If it does not say "Verified" then the drive is failing or has failed and will need replacing. SMART info will not be reported on external drives. Otherwise, click on the Partition tab in the DU main window.
3. Click on the Options button, set the partition scheme to GUID (only required for Intel Macs) then click on the OK button. Set the number of partitions from the dropdown menu (use 1 partition unless you wish to make more.) Set the format type to Mac OS Extended (Journaled.) Click on the Partition button and wait until the volume(s) mount on the Desktop.
4. Select the volume you just created (this is the sub-entry under the drive entry) from the left side list. Click on the Erase tab in the DU main window.
5. Set the format type to Mac OS Extended (Journaled.) Click on the Options button, check the button for Zero Data and click on OK to return to the Erase window.
6. Click on the Erase button. The format process can take up to several hours depending upon the drive size.
Steps 4-6 are optional but should be used on a drive that has never been formatted before, if the format type is not Mac OS Extended, if the partition scheme has been changed, or if a different operating system (not OS X) has been installed on the drive. -
Could not open DVD with libdvdcss
I installed vlc, xine-lib, xine-ui, mplayer, libdvdcss, libdvdnav, libdvdread.
I also installed "codecs" with packer.
I'm trying to play two different DVDs and the following is what I get (even putting the disk into /dev/sr0 or using another DVD won't change):
$ vlc /dev/sr1
VLC media player 2.1.5 Rincewind (revision 2.1.4-49-gdab6cb5)
[0x95b1220] pulse audio output error: PulseAudio server connection failure: Connection refused
[0x952a8f8] main libvlc: VLC wird mit dem Standard-Interface ausgeführt. Benutzen Sie 'cvlc', um VLC ohne Interface zu verwenden.
libdvdnav: Using dvdnav version 4.2.1
libdvdread: Could not open /dev/sr1 with libdvdcss.
libdvdread: Can't open /dev/sr1 for reading
libdvdnav: vm: failed to open/read the DVD
[0xb20a5e48] filesystem access error: read error: Input/output error
[0xb39a6e10] main stream error: cannot pre fill buffer
libdvdnav: Using dvdnav version 4.2.1
libdvdread: Could not open /dev/sr1 with libdvdcss.
libdvdread: Can't open /dev/sr1 for reading
libdvdnav: vm: failed to open/read the DVD
libdvdread: Could not open /dev/sr1 with libdvdcss.
libdvdread: Can't open /dev/sr1 for reading
[0xb1abe3f8] dvdread demux error: DVDRead cannot open source: /dev/sr1
[0xb5a03700] main input error: open of `dvd:///dev/sr1' failed
$ mplayer /dev/sr1
MPlayer SVN-r37224 (C) 2000-2014 MPlayer Team
210 audio & 441 video codecs
Playing /dev/sr1.
File not found: '/dev/sr1'
Failed to open /dev/sr1.
Exiting... (End of file)
$ xine /dev/sr1
Dies ist xine (X11 gui) - Ein freier Video-Player v0.99.8-[DEBUG].
(c) 2000-2010 The xine Team.
videowin: display is using xinerama with 1 screens
videowin: going to assume we are using the first screen.
videowin: size of the first screen is 1024x768.
videowin: Xinerama fullscreen parameters: X_origin=0 Y_origin=0 Width=1024 Height=768
pixel_aspect: 0.997627
Failed to open VDPAU backend libvdpau_nouveau_vieux.so: Kann die Shared-Object-Datei nicht öffnen: Datei oder Verzeichnis nicht gefunden
vo_vdpau: Can't create vdp device : No vdpau implementation.
xv_set_property: property=1, value=0
xine: could not connect to socket
xine: Datei oder Verzeichnis nicht gefunden
this is my video card
01:00.0 VGA compatible controller: NVIDIA Corporation NV11 [GeForce2 MX200] (rev b2) (prog-if 00 [VGA controller])
Subsystem: CardExpert Technology Device 0001
Flags: bus master, 66MHz, medium devsel, latency 64, IRQ 16
Memory at d6000000 (32-bit, non-prefetchable) [size=16M]
Memory at d8000000 (32-bit, prefetchable) [size=128M]
Expansion ROM at d7ff0000 [disabled] [size=64K]
Capabilities: [60] Power Management version 2
Capabilities: [44] AGP version 2.0
Kernel driver in use: nouveau
Kernel modules: nouveau
these commands were asked me on freenode's #archlinux channel:
$ stat /dev/sr0
Datei: „/dev/sr0“
Größe: 0 Blöcke: 0 EA Block: 4096 blockorientierte Spezialdatei
Gerät: 5h/5d Inode: 6351 Verknüpfungen: 1 Gerätetyp: b,0
Zugriff: (0660/brw-rw----) Uid: ( 0/ root) Gid: ( 93/ optical)
Zugriff : 2014-07-12 22:52:20.959057344 +0200
Modifiziert: 2014-07-12 22:52:20.959057344 +0200
Geändert : 2014-07-12 22:52:20.959057344 +0200
Geburt : -
$ getfacl /dev/sr0
# file: dev/sr0
# owner: root
# group: optical
user::rw-
user:christian:rw-
group::rw-
mask::rw-
other::---
$ loginctl show-session $XDG_SESSION_ID -p Active
Active=yes
I feel like some other driver is missing...
Last edited by leonixyz (2014-07-12 21:58:01)dodo3773 wrote:Can you test a regular video file and it works fine in vlc?
ok, one step toward the solution:
I've scp-ed an .mp4 and an .mpg from my laptop, chmod 777 them and finally I can play them
dodo3773 wrote:
Also, do you get any output from this command?:
dmesg | grep CD
$ dmesg | grep CD
[ 1.227637] scsi 0:0:0:0: CD-ROM HL-DT-ST CD-RW GCE-8320B 1.02 PQ: 0 ANSI: 5
[ 1.238061] scsi 0:0:1:0: CD-ROM LG DVD-ROM DRD8160B 1.01 PQ: 0 ANSI: 5
[ 1.458996] cdrom: Uniform CD-ROM driver Revision: 3.20
[ 1.459461] sr 0:0:0:0: Attached scsi CD-ROM sr0
[ 1.471069] sr 0:0:1:0: Attached scsi CD-ROM sr1
[ 1286.396790] sr 0:0:1:0: [sr1] CDB:
[ 1286.426850] sr 0:0:1:0: [sr1] CDB:
$ pacman -Qi vlc
Name : vlc
Version : 2.1.5-1
Beschreibung : A multi-platform MPEG, VCD/DVD, and DivX player
Architektur : i686
URL : http://www.videolan.org/vlc/
Lizenzen : LGPL2.1 GPL2
Gruppen : Nichts
Stellt bereit : Nichts
Hängt ab von : a52dec libdvbpsi libxpm libdca qt4 libproxy sdl_image libdvdnav libtiger
lua libmatroska zvbi taglib libmpcdec ffmpeg faad2 libupnp libshout libmad
libmpeg2 xcb-util-keysyms libtar libxinerama
Optionale Abhängigkeiten: avahi: for service discovery using bonjour protocol[Installiert]
libnotify: for notification plugin[Installiert]
ncurses: for ncurses interface support[Installiert]
libdvdcss: for decoding encrypted DVDs[Installiert]
lirc-utils: for lirc plugin[Installiert]
libavc1394: for devices using the 1394ta AV/C
libdc1394: for IEEE 1394 plugin
kdelibs: KDE Solid hardware integration
libva-vdpau-driver: vdpau back-end for nvidia[Installiert]
libva-intel-driver: back-end for intel cards
libbluray: for Blu-Ray support[Installiert]
flac: for Free Lossless Audio Codec plugin[Installiert]
portaudio: for portaudio support
twolame: for TwoLAME mpeg2 encoder plugin
projectm: for ProjectM visualisation plugin
libcaca: for colored ASCII art video output[Installiert]
libgme: for libgme plugin
librsvg: for SVG plugin[Installiert]
gnome-vfs: for GNOME Virtual File System support
libgoom2: for libgoom plugin
vcdimager: navigate VCD with libvcdinfo
aalib: for ASCII art plugin[Installiert]
libmtp: for MTP devices support
smbclient: for SMB access plugin[Installiert]
libcdio: for audio CD playback support[Installiert]
ttf-freefont: for subtitle font
ttf-dejavu: for subtitle font
opus: for opus support[Installiert]
libssh2: for sftp support[Installiert]
lua-socket: for http interface
Benötigt von : Nichts
Optional für: Nichts
Konflikt mit : vlc-plugin
Ersetzt : vlc-plugin
Installationsgröße: 44319,00 KiB
Packer : Giovanni Scafora <[email protected]>
Erstellt am : Mi 09 Jul 2014 15:14:36 CEST
Installiert am : Sa 12 Jul 2014 21:15:04 CEST
Installationsgrund : Ausdrücklich installiert
Installations-Skript : Ja
Verifiziert durch: Signatur -
Could not open location 'file:///home/geoff'
I'm using Gnome and after the last update today ( I always do pacman -Syu everyday and accept whatever it gives me in my noobidity ):(
Now I find that when I go to Places--Home Folder and Places--Desktop I get this message.
Could not open location 'file:///home/geoff' (or 'file:///home/geoff/Desktop')
There was an error launching the default action command associated with this location
Have I done something stupid in accepting all updates without question? Or is it something else?
Can you put me on the right learning curve and fix this.
ThanksI think that the latest udev upgrade has caused the problem. Correct me if I'm wrong.
I did the same upgrade on my laptop and got the same fault.
Apart from the faults in my previous message if I open a terminal over any page I'm looking at, like this for instance, it will not stay "above" the page when the box "only on this workspace" is checked. I have to check "always on top" to make it stay so I can cut and paste things.
When the terminal is minimized in the bottom panel and I click on it, it comes up but the moment I move the mouse pointer to the terminal screen it disappears back to being minimized.
I've never had this weird behavior before.
Hoping someone can help
thanks
Maybe you are looking for
-
hi is there any problem in creating a select view directly in sql? thanks in advanced best regards
-
I am working on FLEX 4.6 SDK it provides 35 components with built in accessibility support. My Application contains some components which have no built in accessibility support but I need to provide accessibility support for those components too. I h
-
New Smart Album problems PSE9 Mac OSX
I am running PSE9 on a Macbook Pro and an Imac, both using Mac OSX. Creating a new Smart Album on the Macbook works perfectly but on the Imac it is unworkable. When I try to create a new Smart Album I just get a spinning ball and everything stops. I
-
Networking 3 Macs with 2 on Airport and 1 hardwired
I have a cable modem going into a non-wireless router. Out of the router I have a cable going to a mac mini hard wired (does not have a wireless card). I also have a cable going to an airport express which 2 other macs run off of. Here's the question
-
Getting error "SQL error in the database when accessing a table."
Hi All, We are getting Dump Error SQL error in the database when accessing a table for the batch job EISSD/REQUISITION 14 / which includes program AQ20FD==========A2============. Please reply. The Dump error details are as follows Short text SQL