[SOLVED] Ardour - could not reconnect to audio/MIDI engine

I have a problem with Ardour:
when I am tryng to create a session it is telling me that it "could not reconnect to audio/MIDI engine.
I don't really know where to go from here.. Can anyone please help me with this?
Let me know if there is any information I should post to help solving this?
Thanks in advance!
Last edited by AlexanderHolmgaard (2015-02-07 16:29:56)

Have you add your user to audio group?

Similar Messages

  • Could not reconnect all network drives

    I have several drives mapped on different Windows 7 boxes in my office.  Just about every time I boot up one of these systems I receive the message "Could not reconnect all network drives" in the system tray.
    I should note that merely clicking the drive inside Windows Explorer will restore the connection.  I store the server logon credentials in Control Panel / Credential Manager then just map the network paths to drive letters.  I'm pretty sure the
    problem doesn't stem from any credentials type of problem though, because I have the exact same situation when connecting to only open shares.  I have noticed that a couple applications will restore the connection themselves when trying to access information
    on a share.  Most applications however will give an error and time out trying to access the shares unless I go and manually click each drive letter in Explorer.  For instance if I place Firefox bookmarks on a share and open Firefox, Firefox will
    display no bookmarks until I click the drive in Explorer and reopen Firefox.
    One thing I can do to fix the problem is hard code my IP address. I never receive the message if a computer has fixed IP address.  My router hands out IPs on the LAN dynamically, so I switch it to another router and tried a using a Linux based dhcp-server
    as well.  Neither fixed the problem.
    I'm a long time user of batch files and realize I could place use one as a band aid for this issue, but I don't want to go that route.

    Hello marstech,
    According to the research, the mapped drive lost issue may be caused by the several possible reasons:
    Possible reason1. The problematic client doesn't reconnect to the target share at logon.
    Please follow the steps to re-configure the mapped driver on the client and then check if the issue will re-occur.
    Steps:
    a. Open "My Computer"
    b. Click on "Tools" and then select "Map Network Driver"
    c. input the \\ipaddressofserver\sharename to give the path of the share
    d. Check "Reconnect at logon"
    e. Drive gets mapped
    f. Double click on the drive to check.
    Possible Reason 2. Antivirus software or Windows Firewall may block the SMB protocol on clients.
    Please check if there is any Antivirus software and the Windows Firewall is enabled on the problematic client. If so, please disable them to check if the issue can be resolved.
    Possible Reason3. Fast Logon Optimization is enabled on the clients. 
    The fast logon feature may affect the display and drive letter assignment of a mapped network drive. As a result, the drive may have been mapped; however, the user on client cannot see it in Windows Explorer. He may recognize it as a failed network drive mapping.
    This is the reason why we usually suggest you to disable fast logon on the clients via a GPO, and please check if the mapped network drive will be occur under this circumstance.
    Please also configure the following group policy setting to disable Fast Logon Optimization to see if the issue still exists on the problematic clients.
    Computer Configuration\Administrative Templates\System\Logon\Always wait for the network at computer startup and logon
    When this policy is enabled, a Windows XP client behaves in the same manner as a Windows 2000 client at both system startup and at user logon.
    Please note: As this is a computer configuration, please run "Gpupdate /force" and then reboot the problematic clients to make it take into effect.
    For more information about Fast Logon Optimization feature, please check the following KB article.
    305293 Description of the Windows XP Professional Fast Logon Optimization feature
    http://support.microsoft.com/?id=305293
    831998 Mapped network drive shows no drive letter or will not allow you to create new long-named files or folders
    http://support.microsoft.com/kb/831998
    297684 Mapped Drive Connection to Network Share May Be Lost
    http://support.microsoft.com/kb/297684
    If the issue still exists on the problematic clients, please also try adding the following registry subkey on the problematic client to check it works.
    Steps:
    a. Click Start, click Run, type REGEDIT, and then click OK.
    b. Locate and click the following registry subkey:
    HKEY_LOCAL_MACHINE\Software\Microsoft\Windows\CurrentVersion\NetCache
    c. Click Edit, point to New, and then click DWORD Value.
    d. Type SilentForcedAutoReconnect , and then press ENTER to name the value.
    e. Double-click SilentForcedAutoReconnect .
    f. In the Value data box, type 1, and then click OK.
    Please feel free to let me know if you have any concen.
    Hope the information can be helpful for you.
    Thanks and Regards
    Scorpio_Milo
    MCTS: Windows Vista | Exchange Server 2007
    MCITP: Enterprise Support Technician
    MCITP: Server & Enterprise Administrator
    Microsoft Infrastructure Consultant
    Enterprise Service: Solution Architect
    Microsoft Storage Team - File Cabinet Blog
    My Blog

  • CWSI 2.4; Could not reconnect to osagent

    Hi,
    the cwsi-start failes with the message: "could not reconnect to osagent". The Installation contains the following Software: WindowsNT4-Server (SP6a), HP Network-Node-Manager 6.2, RME2.2 / CWSI 2.4. The information from osfind.exe is: osagent works on port 14000. But the default port should be 42342. I had no success with the change of the registry-values from 42342 to 14000.
    What can I do?
    Regards.
    Volker Janusch

    yesterday did I reinitdb. But there was the same failure again. Now I restarted the deamon manager - and the CWSI works. After an reboot occures the same failure again. If I restrart the deamon manager: It works. I will put in operation again this customer-server with this workaround. If you have any other ideas ..... :-))
    I know, this an obsolete Version, but the customer don`t want to upgrade at this time.
    Thanks.

  • "Could not get the audio data from the file" error

    Hi
    I get a lot of "Could not get the audio data from the file" errors when opening a project. Sometimes they crash Premiere Pro CC 7.01 (Mac). But if not Premiere works as usual, with the audio.
    I tried to convert the audio files (coming from Audition) from 32 to 16 bit. It worked while opening a project once, but not the following times.
    Where can it come from ?
    Edit: I also get this error when importing audio: "Error: Premiere Pro version 7.0 is not compatible with the Premiere Pro Plug-in version 5.7.4". Maybe it is connected.

    Got it! It was the Smartsound plugin making trouble. Got rid of it and no more errors.

  • Just downloaded Yosemite on my Mac and the Yosemite update for Garage Band.  Now when I open an existing Garage Band project and click on a vocal track, a message window says, "Could not find General Audio 10" and have no smart controls.  Help?

    Just downloaded Yosemite on my Mac and the Yosemite update for Garage Band.  Now when I open an existing Garage Band project and click on a vocal track, a message window says, "Could not find General Audio 10" and have no smart controls for that track (reverb, etc.)  Help?

    Try this fix posted by Robinson Collins:
    Re: I downloaded Garage Band 2x and the same note appears: there is no General Audio 10. Please advise. Thank you.
    Try this: Go to your menu bar, select "Garageband" and then "Restore Sound Library..."
    It can take awhile to download as it's a pretty big library. You might need to also select "Update Sound Library..." after the restore is done.

  • Could not find supported audio device in AA3

    okay so i know its not a good idea to use AA3 with Vista...but other people are doing it so why can't I? I've seen the topic posted before but the threads are pretty much dead and I still have no helpful info. I've scoured this thing with no affective solution. I've installed AA3 on several systems in the past and never had this much trouble--if any. This problem has gone on for over 2 months now!
    Since I installed AA3 on my new computer all i can get and all i have ever gotten is the "AA could not find a supported audio device. Please check device settings" dialog--
    press okay (or x) and Audition closes---never getting past the loading window --during "initalizing required components"
    I have 3 audio devices/ with up to date drivers which all my other audio programs recognize (Audition 1.5, Sonor, Cubase + more) with no problem whatsoever--
    AA3
    Windows Vista SP1 64 bit
    Realtek HD Audio
    + Presonus FP10 digital firewire interface/preamp (kind of unrelated but aa3 still wont recognize it either apparently)
    I have installed all updates including the 64-bit SP1 fix for AA3.
    I've read the Realtek HD issue solutions and made sure my drivers are fine.
    IM DESPERATE----PLEASE!!!
    I'm having a recording studio built right now & AA3 is my main DAW so this is rather dire.---All the other DAW's i've tried suck compared to AA3 (with the exception of stability). hehe AA3 is always crashing on me and yet i still prefer it over other DAW's.

    I put the PreSonus StudiLive 16.4.2 plus Adobe Audition 3 setup instructions into a short write-up on my blog: Live Event Multitrack Audio Capture
    Here is a photo showing how to set up the Firewire channels for input and output
    I hope this helps:
    Ron Fredericks
    LectureMaker, LLC

  • [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)

  • [SOLVED] "warning: could not find /bin/bash, starting /bin/sh instead"

    Hello all.
    I've just installed arch, despite very little knowledge of linux (i had ubuntu for a short while before this), but I like a challenge so i thought i'd throw myself in at the deep end.
    The installation went reasonably smoothly, but now i've got it up and running (with a minimal KDE install) but when I open up the konsole, I get the message
    "Warning: Could not find '/bin/bash/', starting '/bin/sh' instead. Please check your profile settings."
    and subsequently I cannot "su jake" (jake being my username, obviously). It requests my password, but when i press return I get the response
    su: /bin/bash/: Not a directory
    which means i've obviously done something wrong, but I cant make head nor tail of the archwiki on Bash, and from googling, I cant find anyone with a similar issue. I can run from root, but it's not ideal.
    Thanks for any response as to why this might be happening, and how to fix it.
    Last edited by hansolo128 (2012-04-24 08:55:37)

    @oxyd
    sh-4.2$ cat /etc/shells
    # /etc/shells
    /bin/sh
    /bin/bash
    # End of file
    root:x:0:0:root:/root:/bin/bash
    jake:x:1000:100::/home/jake:/bin/bash/
    the output of /etc/passwd is
    root:x:0:0:root:/root:/bin/bash
    bin:x:1:1:bin:/bin:/bin/false
    daemon:x:2:2:daemon:/sbin:/bin/false
    mail:x:8:12:mail:/var/spool/mail:/bin/false
    ftp:x:14:11:ftp:/srv/ftp:/bin/false
    http:x:33:33:http:/srv/http:/bin/false
    nobody:x:99:99:nobody:/:/bin/false
    dbus:x:81:81:System message bus:/:/bin/false
    jake:x:1000:100::/home/jake:/bin/bash/
    usbmux:x:140:140:usbmux user:/:/sbin/nologin
    mysql:x:89:89::/var/lib/mysql:/bin/false
    kdm:x:135:135::/var/lib/kdm:/bin/false
    avahi:x:84:84:avahi:/:/bin/false
    moving my home directory from /bin/bash/ to /bin/bash on the line of my username now allows me to su jake, but it doesnt solve the warning that /bin/bash/ doesnt exist.

  • [SOLVED] "Superblock could not be read" error on install

    I've been trying desperatly to install Arch Linux on my main computer but this error almost always shows up after 1 or two reboots (usually when I'm finished installing base system and about to install Xorg):
    :: Checking Filesystems
    /dev/sdc3:
    The superblock could not be read or does not describe a correct ext2 filesystem. If the device is valid and it really contains an ext2 filesystem (and not swap or ufs or something else), then the superblock is corrupt, and you might try running e2fsck with an alternative superblock: e2fsck -b 8193 <device>
    I installed Arch by following the install guide and choosing Auto-prepare partitioning where I chose EXT4 as FS for /home and / I believe, so Im guessing the filessytems are set-up properly.
    I have no idea why this error keeps coming back reinstall after reinstall (with complete format of HD in each reinstall). First I thought the HD might have gone bad so I tried installing arch to another HD and the error still shows.
    Sometimes if I reboot enough times the error doesn't show and sometimes it just doesn't go away, seems like it's kind of random.
    The harddisk I am installing to is a 30GB IDE Maxtor harddisk (a couple of years old) and I also tried with a 40GB Seagate IDE harddisk both with no success. When I installed I had 2 other harddisks in my system; a 60GB OCZ agility SSD and a 640GB Wester Digital both on SATA channels, but they are unplugged now.
    I'm really lost as what to do here, I love Arch Linux and have used it for some time on my laptop but I never had any kind of problems like this.
    Here's output from 'fdisk -l' run from the "maintanence mode" I get into when the error shows "Give root password for maintenance".
    I find it weird that Arch tells me the error is on "/dev/sdc3:" when my harddisk is /dev/sda (my other two harddisks are unplugged, but it shows the error both with and without them so I guess it doesnt matter):
    fdisk -l
    Device        Boot    Start         End          Blocks                Id       System
    /dev/sda1      *        1             13            104422             83       Linux
    /dev/sda2               14            587          4610655            82      Linus swap /Solaris
    /dev/sda3              588           1544         7687102+         83      Linux
    /dev/sda4              1545         3738         17623305          83      Linux
    Regards,
    John
    Last edited by johnrl (2010-01-28 14:42:15)

    How many hard drives you have installed at the moment?
    Atm I have 3 HDs installed; my Arch HD, my OCZ agility and my Western Digital.
    Peasantoid wrote:
    PirateJonno wrote:To find your UUID look in /dev/disk/by-uuid and use readlink to find the equivalent sdXX.
    ...or use `blkid`.
    Thanks, I used blkid and set-up UUID in /etc/fstab and it seems to be working now.
    Can anyone explain how come that the /dev/sdx assignments seems to be randomly distributed among my HDs on each reboot - is this normal? I tried using 'blkid' on a few reboots and noticed that the problem occured everytime the HD arch is installed on was NOT assigned to /dev/sdc, but when it was assigned to /dev/sdc (which was in fstab) it worked fine.
    Isn't it weird that Arch seems to assign a different /dev/sdx number to each harddisk on reboots? I mean, if this is normal, why doesn't Arch use UUIDs by default? At first I thought the different /dev/sdx assignments was caused by changing boot order in the BIOS, but the assignments seem to change even when I don't enter the BIOS and just reboot without touching a thing - one reboot it works and one it doesn't (due to differnet /dev/sdx assignment to my Arch hd).
    EDIT:
    I found the answer to my question on http://wiki.archlinux.org/index.php/Per … ice_naming - Arch randomly assigns device nodes so it seems the UUID fix is the way to avoid unbootable systems.
    Is it possible to make Arch use UUIDs in the install so I don't have to configure it manually afterwards? (Why doesn't it use UUIDs by default?)
    Thanks for the answers,
    John
    Last edited by johnrl (2010-01-27 15:20:12)

  • How can I solve the "could not sign in iTunes Store: An unknown error has occurred." problem

    after finishing watching a movie (paid movie), I tried renting another one but the "Could not sign in " error stopped me from doing that.  I have restarted the Apple TV many times, turned it off, restarted my cable modem, and much more. However, I am still getting this error. I would appreciate if anyone could give me a possible solution to this problem.
    Thanks.

    after finishing watching a movie (paid movie), I tried renting another one but the "Could not sign in " error stopped me from doing that.  I have restarted the Apple TV many times, turned it off, restarted my cable modem, and much more. However, I am still getting this error. I would appreciate if anyone could give me a possible solution to this problem.
    Thanks.

  • [Solved] error could not open file /var/lib/pacman/sync/core.db

    I am trying to install Arch but when I type "pacstrap /mnt base base-devel"  I keep on getting this error "error could not open file /var/lib/pacman/sync/core.db unrecognized archive format".
    I have tried:
    # rm -R /var/lib/pacman/sync/
    # pacman -Syuf
    I have also tried pacman -Syy with no luck.
    What more is there to do besides installing ubuntu?
    Last edited by johane (2012-08-11 08:22:07)

    johane wrote:
    I am trying to install Arch but when I type "pacstrap /mnt base base-devel"  I keep on getting this error "error could not open file /var/lib/pacman/sync/core.db unrecognized archive format".
    I have tried:
    # rm -R /var/lib/pacman/sync/
    Pacstrap was telling you it couldn't open a file, so you just deleted the entire directory tree? Did it appear to be downloading the database files correctly before this? Did you try running pacstrap again after you deleted everything?
    And then you tried to run pacman with the -f (force) option? What happened? "no luck" doesn't tell us anything.
    What more is there to do besides installing ubuntu?
    There are many things you can do. You can give us more information about what you did and what happened. Did you follow all the steps in the Beginners Guide up to the pacstrap step? Did you get any errors or warnings before that step? Are you sure you had a working network connection? Did you interrupt the pacstrap process at any time? Did you try running it again after you deleted /var/lib/pacman/sync?
    Did you check the sha1sum of the iso you downloaded before you put it on a usb stick?
    https://wiki.archlinux.org/index.php/Be … oaded_file
    How did you put it on the usb stick?
    When you got the error, did you do
    ls /var/lib/pacman/sync
    to see what (if anything) was there?
    Last edited by 2ManyDogs (2012-08-06 23:38:27)

  • [SOLVED] error: could not open file /var/lib/pacman/local/qt-4.5.2-4/

    Hi all,
    So there I was, running pacman -Syu on all my Arch machines, and I get to my desktop PC at work, and half way through X decides to crash and kick me back to the CLI. Fair enough
    Now when I try and use pacman, I get a whole bunch of errors about a missing 'depends' directory:
    root ~ # pacman -S amarok
    resolving dependencies...
    error: could not open file /var/lib/pacman/local/qt-4.5.2-4/depends: No such file or directory
    error: could not open file /var/lib/pacman/local/qt-4.5.2-4/depends: No such file or directory
    error: could not open file /var/lib/pacman/local/qt-4.5.2-4/depends: No such file or directory
    error: could not open file /var/lib/pacman/local/qt-4.5.2-4/depends: No such file or directory
    error: could not open file /var/lib/pacman/local/qt-4.5.2-4/depends: No such file or directory
    error: could not open file /var/lib/pacman/local/qt-4.5.2-4/depends: No such file or directory
    error: could not open file /var/lib/pacman/local/qt-4.5.2-4/depends: No such file or directory
    error: could not open file /var/lib/pacman/local/qt-4.5.2-4/depends: No such file or directory
    error: could not open file /var/lib/pacman/local/qt-4.5.2-4/depends: No such file or directory
    error: could not open file /var/lib/pacman/local/qt-4.5.2-4/depends: No such file or directory
    error: could not open file /var/lib/pacman/local/qt-4.5.2-4/depends: No such file or directory
    error: could not open file /var/lib/pacman/local/qt-4.5.2-4/depends: No such file or directory
    error: could not open file /var/lib/pacman/local/qt-4.5.2-4/depends: No such file or directory
    error: could not open file /var/lib/pacman/local/qt-4.5.2-4/depends: No such file or directory
    error: could not open file /var/lib/pacman/local/qt-4.5.2-4/depends: No such file or directory
    error: could not open file /var/lib/pacman/local/qt-4.5.2-4/depends: No such file or directory
    error: could not open file /var/lib/pacman/local/qt-4.5.2-4/depends: No such file or directory
    error: could not open file /var/lib/pacman/local/qt-4.5.2-4/depends: No such file or directory
    error: could not open file /var/lib/pacman/local/qt-4.5.2-4/depends: No such file or directory
    error: could not open file /var/lib/pacman/local/qt-4.5.2-4/depends: No such file or directory
    error: could not open file /var/lib/pacman/local/qt-4.5.2-4/depends: No such file or directory
    error: could not open file /var/lib/pacman/local/qt-4.5.2-4/depends: No such file or directory
    error: could not open file /var/lib/pacman/local/qt-4.5.2-4/depends: No such file or directory
    error: could not open file /var/lib/pacman/local/qt-4.5.2-4/depends: No such file or directory
    error: could not open file /var/lib/pacman/local/qt-4.5.2-4/depends: No such file or directory
    error: could not open file /var/lib/pacman/local/qt-4.5.2-4/depends: No such file or directory
    error: could not open file /var/lib/pacman/local/qt-4.5.2-4/depends: No such file or directory
    error: could not open file /var/lib/pacman/local/qt-4.5.2-4/depends: No such file or directory
    error: could not open file /var/lib/pacman/local/qt-4.5.2-4/depends: No such file or directory
    error: could not open file /var/lib/pacman/local/qt-4.5.2-4/depends: No such file or directory
    error: could not open file /var/lib/pacman/local/qt-4.5.2-4/depends: No such file or directory
    error: could not open file /var/lib/pacman/local/qt-4.5.2-4/depends: No such file or directory
    error: could not open file /var/lib/pacman/local/qt-4.5.2-4/depends: No such file or directory
    error: could not open file /var/lib/pacman/local/qt-4.5.2-4/depends: No such file or directory
    error: could not open file /var/lib/pacman/local/qt-4.5.2-4/depends: No such file or directory
    error: could not open file /var/lib/pacman/local/qt-4.5.2-4/depends: No such file or directory
    looking for inter-conflicts...
    error: could not open file /var/lib/pacman/local/qt-4.5.2-4/depends: No such file or directory
    error: could not open file /var/lib/pacman/local/qt-4.5.2-4/depends: No such file or directory
    error: could not open file /var/lib/pacman/local/qt-4.5.2-4/depends: No such file or directory
    error: could not open file /var/lib/pacman/local/qt-4.5.2-4/depends: No such file or directory
    error: could not open file /var/lib/pacman/local/qt-4.5.2-4/depends: No such file or directory
    error: could not open file /var/lib/pacman/local/qt-4.5.2-4/depends: No such file or directory
    error: could not open file /var/lib/pacman/local/qt-4.5.2-4/depends: No such file or directory
    error: could not open file /var/lib/pacman/local/qt-4.5.2-4/depends: No such file or directory
    error: could not open file /var/lib/pacman/local/qt-4.5.2-4/depends: No such file or directory
    error: could not open file /var/lib/pacman/local/qt-4.5.2-4/depends: No such file or directory
    error: could not open file /var/lib/pacman/local/qt-4.5.2-4/depends: No such file or directory
    error: could not open file /var/lib/pacman/local/qt-4.5.2-4/depends: No such file or directory
    error: could not open file /var/lib/pacman/local/qt-4.5.2-4/depends: No such file or directory
    error: could not open file /var/lib/pacman/local/qt-4.5.2-4/depends: No such file or directory
    error: could not open file /var/lib/pacman/local/qt-4.5.2-4/depends: No such file or directory
    error: could not open file /var/lib/pacman/local/qt-4.5.2-4/depends: No such file or directory
    error: could not open file /var/lib/pacman/local/qt-4.5.2-4/depends: No such file or directory
    error: could not open file /var/lib/pacman/local/qt-4.5.2-4/depends: No such file or directory
    error: could not open file /var/lib/pacman/local/qt-4.5.2-4/depends: No such file or directory
    It still asks me to continue with installing the new package, but I'd rather get this fixed first in case it buggers it up worse
    Last edited by fukawi2 (2009-07-30 05:44:25)

    Once again my saviour Allan -- I had to -Sf it due to file already existing, but seems to be good now

  • [Solved] irexec: could not connect to socket

    I am trying to start irexec via .xinitrc which has worked fine for me pre-systemd, but now I am getting the following error:
    irexec: could not connect to socket
    irexec: no such file or directory
    Lirc is running fine, remote works in mythtv.
    Here's my .xinitrc
    cat ~/.xinitrc
    #!/bin/sh
    # ~/.xinitrc
    # Executed by startx (run your window manager from here)
    # exec gnome-session
    # exec startkde
    # exec startxfce4
    # ...or the Window Manager of your choice
    #exec xterm
    #start irexec
    irexec &
    #exec /usr/bin/xbmc &
    #turn off screensaver
    xset s off -dpms
    #start xfce4
    exec startxfce4
    and my lirc
    cat /usr/lib/systemd/system/lirc.service
    [Unit]
    Description=Linux Infrared Remote Control
    [Service]
    ExecStartPre=/usr/bin/ln -sf /run/lirc/lircd /dev/lircd
    ExecStart=/usr/sbin/lircd --pidfile=/run/lirc/lircd.pid
    Type=forking
    PIDFile=/run/lirc/lircd.pid
    [Install]
    WantedBy=multi-user.target
    and my /etc/conf.d/lircd.conf
    cat /etc/conf.d/lircd.conf
    # Parameters for lirc daemon
    LIRC_DEVICE="/dev/lirc0"
    LIRC_DRIVER=""
    LIRC_EXTRAOPTS=""
    LIRC_CONFIGFILE=""
    I tried starting irexec via systemd, too, but that did not work either:
    sudo systemctl status irexec.service
    irexec.service - IR Exec
    Loaded: loaded (/usr/lib/systemd/system/irexec.service; enabled)
    Active: inactive (dead) since Sun 2013-04-21 20:17:11 CST; 1s ago
    Process: 459 ExecStart=/usr/bin/irexec --daemon (code=exited, status=0/SUCCESS)
    Apr 21 20:17:11 frontend systemd[1]: Starting IR Exec...
    Apr 21 20:17:11 frontend systemd[1]: Started IR Exec.
    cat /usr/lib/systemd/system/irexec.service
    [Unit]
    Description=IR Exec
    After=lirc.service
    Wants=lirc.service
    [Service]
    ExecStart=/usr/bin/irexec --daemon
    Type=forking
    [Install]
    WantedBy=multi-user.target
    Any help or pointers will be much appreciated.
    Last edited by dafrizz (2013-06-08 23:58:25)

    Thanks for your help so far. I thought it was the other way around, my mistake,
    Still no luck, now I get the following:
    sudo systemctl start irexec
    Job for irexec.service failed. See 'systemctl status irexec.service' and 'journalctl -xn' for details.
    sudo systemctl status irexec
    irexec.service - IR Exec
    Loaded: loaded (/etc/systemd/system/irexec.service; enabled)
    Active: failed (Result: timeout) since Sat 2013-06-08 16:16:17 CST; 10s ago
    Process: 11748 ExecStart=/usr/bin/irexec (code=killed, signal=TERM)
    Jun 08 16:14:47 frontend systemd[1]: Starting IR Exec...
    Jun 08 16:16:17 frontend systemd[1]: irexec.service operation timed out. Terminating.
    Jun 08 16:16:17 frontend systemd[1]: Failed to start IR Exec.
    Jun 08 16:16:17 frontend systemd[1]: Unit irexec.service entered failed state.
    sudo journalctl -xn
    -- Logs begin at Sat 2013-04-20 18:36:51 CST, end at Sat 2013-06-08 16:16:44 CST. --
    Jun 08 16:15:41 frontend sudo[11759]: pam_unix(sudo:session): session closed for user root
    Jun 08 16:16:17 frontend systemd[1]: irexec.service operation timed out. Terminating.
    Jun 08 16:16:17 frontend systemd[1]: Failed to start IR Exec.
    -- Subject: Unit irexec.service has failed
    -- Defined-By: systemd
    -- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel
    -- Documentation: http://www.freedesktop.org/wiki/Software/systemd/catalog/be02cf6855d2428ba40df7e9d022f03d
    -- Unit irexec.service has failed.
    -- The result is failed.
    Jun 08 16:16:17 frontend systemd[1]: Unit irexec.service entered failed state.
    Jun 08 16:16:17 frontend sudo[11745]: pam_unix(sudo:session): session closed for user root

  • [SOLVED] Java could not find or load main class

    I just tried to run a Java program using Swing components from the terminal, but I always get this error message:
    $ java VisualTest
    Error: Could not find or load main class VisualTest
    The strange thing is that it runs flawlessly from within Eclipse.
    I created VisualTest.java using the (old) Visual Editor, it's contents are:
    package visual1;
    import javax.swing.SwingUtilities;
    //import java.awt.BorderLayout;
    import javax.swing.JPanel;
    import javax.swing.JFrame;
    public class VisualTest extends JFrame {
    private static final long serialVersionUID = 1L;
    private JPanel jContentPane = null;
    * @param args
    public static void main(String[] args) {
    // TODO Auto-generated method stub
    SwingUtilities.invokeLater(new Runnable() {
    public void run() {
    VisualTest thisClass = new VisualTest();
    thisClass.setDefaultCloseOperation(JFrame.EXIT_ON_CLOSE);
    thisClass.setVisible(true);
    * This is the default constructor
    public VisualTest() {
    super();
    initialize();
    * This method initializes this
    * @return void
    private void initialize() {
    this.setSize(300, 200);
    this.setDefaultCloseOperation(JFrame.EXIT_ON_CLOSE);
    this.setContentPane(getJContentPane());
    this.setTitle("JFrame");
    * This method initializes jContentPane
    * @return javax.swing.JPanel
    private JPanel getJContentPane() {
    if (jContentPane == null) {
    jContentPane = new JPanel();
    jContentPane.setLayout(null);
    return jContentPane;
    As you can see, there is a class named VisualTest and it contains a main function.
    My CLASSPATH variable contains a dot, like
    .:/home/mk/.java/deployment/ext/*
    I just updated my Java from JDK 7u67 to JDK 8u20 (the Oracle one, in AUR), but I can't imagine this is related (however, I haven't run Java programs from the terminal for a long time).
    Strangely enough, a simple HelloWorld.java
    public class HelloWorld {
    public static void main(String[] args) {
    System.out.println("Hello World!");
    runs flawlessly from within the terminal.
    Last edited by Marcel- (2014-09-26 12:44:35)

    As intended by my institution, I said to Eclipse that it should store sources and class files in the same directory. Let's do ls and test:
    [~/workspace]$ ls
    total 12K
    drwxr-xr-x 4 mk mk 4.0K Sep 23 18:23 visualtest/
    -rw-r--r-- 1 mk mk 426 Sep 24 15:45 HelloWorld.class
    -rw-rw-r-- 1 mk mk 111 Sep 24 15:44 HelloWorld.java
    [~/workspace]$ java HelloWorld
    Hello World!
    vs.
    [~/workspace/visualtest/visual1]$ ls
    total 12K
    -rw-r--r-- 1 mk mk 528 Sep 24 15:38 VisualTest$1.class
    -rw-r--r-- 1 mk mk 1.1K Sep 24 15:38 VisualTest.class
    -rw-r--r-- 1 mk mk 1.2K Sep 24 00:32 VisualTest.java
    [~/workspace/visualtest/visual1]$ java VisualTest
    Error: Could not find or load main class VisualTest
    I also tested this with another project that runs fine in Eclipse, but it gives the same error message when trying to issue `java StemOpPartijFrame`.
    EDIT:
    One difference between the two OSs though is that Linux progresses.  The other decays..
    Two? I count many! And I don't think something like OpenBSD decays. ;-)
    Last edited by Marcel- (2014-09-24 16:54:12)

  • Could not start instance on J2EE engine

    Could someone tell me what could be the issue from this install error. It is NetWeaver04 Java system install on a standalone server. Actually i selected the NetWeaver->JavaSystem->Standalone->custom install. I installed oracle 9i database as well as part of the install and i did not understand what it is pointing ABAP database is not available from these message. Can someone educate me and identify my error.
    INFO       2006-10-19 09:46:03
               CJSlibModule::writeInfo_impl()
    Output of /usr/sap/SDN/SYS/exe/run/startsap 'all' 'JC09' 'n1aa1' is written to the logfile start_SDN_JC09.log.
    WARNING    2006-10-19 09:46:37
               CJSlibModule::writeWarning_impl()
    Execution of the command "/usr/sap/SDN/SYS/exe/run/startsap 'all' 'JC09' 'n1aa1'" finished with return code 5. Output:
    Checking SDN Database
    ABAP Database is not available via R3trans
    Checking SDN Database
    Starting SAP-Collector Daemon
    09:46:06 19.10.2006   LOG: Effective User Id is root
    This is Saposcol Version COLL 20.87 640 - V3.50 64Bit
    Usage:  saposcol -l: Start OS Collector
            saposcol -k: Stop  OS Collector
            saposcol -d: OS Collector Dialog Mode
            saposcol -s: OS Collector Status
    The OS Collector (PID 7301) is already running .....
    saposcol already running
    Running /usr/sap/SDN/SYS/exe/run/startj2eedb
    Trying to start SDN database ...
    Log file: /export/home/sdnadm/startdb.log
    /usr/sap/SDN/SYS/exe/run/startj2eedb completed successfully
    Starting SAP Instance JC09
    Startup-Log is written to /export/home/sdnadm/startsap_JC09.log
    Startup of Instance failed
    See /export/home/sdnadm/startsap_JC09.log for details
    ERROR      2006-10-19 09:46:37
               CJSlibModule::writeError_impl()
    CJS-20022  Could not start instance 'JC09' of SAP system SDN.
    Thanks,
    Ram

    Hello Eric,
    Thank you for quick response. Here is the log.
    cat /export/home/sdnadm/startsap_JC09.log
    Trace of system startup/check of SAP System SDN on Thu Oct 19 11:29:57 PDT 2006
    Called command: /usr/sap/SDN/SYS/exe/run/startsap
    Starting SAP Instance JC09
    SAP-R/3-Startup Program Rel 640 V1.8 (2003/04/24)
    Starting at 2006/10/19 11:29:57
    Startup Profile: "/usr/sap/SDN/SYS/profile/START_JC09_jhos1"
    (13395) SETENV LD_LIBRARY_PATH=/usr/sap/SDN/JC09/j2ee/os_libs:/usr/sap/SDN/SYS/exe/run:/usr/sap/SDN/SYS/exe/run:/usr/sap/SDN/SYS/exe/run:/tmp/sapinst_exe.11094.1161276232
    Setup Environment Variables
    (13395) SETENV SHLIB_PATH=/usr/sap/SDN/JC09/j2ee/os_libs:
    (13395) SETENV LIBPATH=/usr/sap/SDN/JC09/j2ee/os_libs:
    Execute Pre-Startup Commands
    (13395) Local: rm -f jc.sapSDN_JC09
    (13395) Local: ln -s -f /usr/sap/SDN/JC09/j2ee/os_libs/jcontrol jc.sapSDN_JC09
    Starting Programs
    (13400) Starting: local jc.sapSDN_JC09 pf=/usr/sap/SDN/SYS/profile/SDN_JC09_jhost1
    (13395) Waiting for Child Processes to terminate.
    (13395) **** 2006/10/19 11:29:58 Child 13400 terminated with Status 0 . ****
    (13395) **** No more Child Processes to wait for.
    (13395) Parent Shutdown at 2006/10/19 11:29:58
    Execute Post-Shutdown Commands
    (13395) Exiting with Return-Code 3. (No more child processes)
    Startup of Instance failed
    Thanks,
    Ram

Maybe you are looking for

  • HP Smart Web Printing 4.6 is incompatible with Firefox 4.0.1.

     Are there any updates to HP Smart Web Printing?

  • Issue in using the OATS

    Hello I have recently installed the OATS into my system , we have the application developed in Oracle 10g , it have several forms we linked it to Java applet and to access this we have java imitator so that we can use it as web based application. At

  • ITunes download site not working....

    Hi guys, i've been trying to download and install the new version of iTunes for the past 2 days now.  Since 07.30 yesterday morning to be exact.  Yesterday i got to about 99% and then the download crashed completely and wouldn't restart when I tried

  • After installing Lion, Safari is Not Working

    Problem:     Trying to access my website  http://www.johnrollow.com I get this error message.    Not Found    The requested URL / was not found on this server    Apache Server at www.johnrollow.com Port 80 I get the same error message from  both Safa

  • Can we access 2 iCloud accounts on same iPad2 that we share?

    we have iPad2 that me and my husband share. We have our own iCloud settings and iPhone 4's. iPad2 is synced to my PC (where also I sync my phone) and my iTunes account. My husband syncs his phone on his PC - home and work. Because we both travel occa