[Solved] Unable to identify laptop webcam

Hi all!
I bought my computer some months ago but never really needed the webcam untill now. I went to check the website of the shop that built and sold me the computer but was unable to find out what kind of webcam there is on my computer (I sent an e-mail).
I tried lsusb, lspci and lshw. Here are the output of lsusb and lspci:
Bus 004 Device 002: ID 8087:8000 Intel Corp.
Bus 004 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 003 Device 002: ID 8087:8008 Intel Corp.
Bus 003 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 001 Device 003: ID 8087:07dc Intel Corp.
Bus 001 Device 002: ID 090c:1000 Silicon Motion, Inc. - Taiwan (formerly Feiya Technology Corp.) Flash Drive
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
00:00.0 Host bridge: Intel Corporation Xeon E3-1200 v3/4th Gen Core Processor DRAM Controller (rev 06)
00:01.0 PCI bridge: Intel Corporation Xeon E3-1200 v3/4th Gen Core Processor PCI Express x16 Controller (rev 06)
00:02.0 VGA compatible controller: Intel Corporation 4th Gen Core Processor Integrated Graphics Controller (rev 06)
00:03.0 Audio device: Intel Corporation Xeon E3-1200 v3/4th Gen Core Processor HD Audio Controller (rev 06)
00:14.0 USB controller: Intel Corporation 8 Series/C220 Series Chipset Family USB xHCI (rev 05)
00:16.0 Communication controller: Intel Corporation 8 Series/C220 Series Chipset Family MEI Controller #1 (rev 04)
00:1a.0 USB controller: Intel Corporation 8 Series/C220 Series Chipset Family USB EHCI #2 (rev 05)
00:1b.0 Audio device: Intel Corporation 8 Series/C220 Series Chipset High Definition Audio Controller (rev 05)
00:1c.0 PCI bridge: Intel Corporation 8 Series/C220 Series Chipset Family PCI Express Root Port #1 (rev d5)
00:1c.1 PCI bridge: Intel Corporation 8 Series/C220 Series Chipset Family PCI Express Root Port #2 (rev d5)
00:1c.2 PCI bridge: Intel Corporation 8 Series/C220 Series Chipset Family PCI Express Root Port #3 (rev d5)
00:1c.3 PCI bridge: Intel Corporation 8 Series/C220 Series Chipset Family PCI Express Root Port #4 (rev d5)
00:1d.0 USB controller: Intel Corporation 8 Series/C220 Series Chipset Family USB EHCI #1 (rev 05)
00:1f.0 ISA bridge: Intel Corporation HM86 Express LPC Controller (rev 05)
00:1f.2 SATA controller: Intel Corporation 8 Series/C220 Series Chipset Family 6-port SATA Controller 1 [AHCI mode] (rev 05)
00:1f.3 SMBus: Intel Corporation 8 Series/C220 Series Chipset Family SMBus Controller (rev 05)
03:00.0 Unassigned class [ff00]: Realtek Semiconductor Co., Ltd. RTS5229 PCI Express Card Reader (rev 01)
04:00.0 Network controller: Intel Corporation Wireless 7260 (rev 73)
05:00.0 Unassigned class [ff00]: Realtek Semiconductor Co., Ltd. Device 5289 (rev 01)
05:00.2 Ethernet controller: Realtek Semiconductor Co., Ltd. RTL8111/8168/8411 PCI Express Gigabit Ethernet Controller (rev 0a)
A grep on hwinfo also gave that:
video: /devices/LNXSYSTM:00/LNXSYBUS:00/PNP0A08:00/LNXVIDEO:01
input device: bus = acpi, bus_id = LNXVIDEO:01 driver = video
P: Phys=LNXVIDEO/video/input0
E: DRIVER=video
E: PHYS="LNXVIDEO/video/input0"
E: LIBINPUT_DEVICE_GROUP=LNXVIDEO/video
video 24576 1 i915, Live 0xffffffffa00b7000
Thank you for any advice,
Last edited by flying_squirrel (2015-05-29 16:23:16)

Post the output of
v4l2-ctl --all
(from v4l-utils) This is going to show us if your camera is being recognized as such, and if yes, which driver is in use, and what it can do. Your output will ideally be similar to this:
Driver Info (not using libv4l2):
Driver name : uvcvideo
Card type : Integrated Camera
Bus info : usb-0000:00:1d.0-1.8
Driver version: 4.0.4
Capabilities : 0x84200001
Video Capture
Streaming
Extended Pix Format
Device Capabilities
Device Caps : 0x04200001
Video Capture
Streaming
Extended Pix Format
Priority: 2
Video input : 0 (Camera 1: ok)
Format Video Capture:
Width/Height : 640/480
Pixel Format : 'YUYV'
Field : None
Bytes per Line: 1280
Size Image : 614400
Colorspace : SRGB
Flags :
Crop Capability Video Capture:
Bounds : Left 0, Top 0, Width 640, Height 480
Default : Left 0, Top 0, Width 640, Height 480
Pixel Aspect: 1/1
Streaming Parameters Video Capture:
Capabilities : timeperframe
Frames per second: 30.000 (30/1)
Read buffers : 0
brightness (int) : min=0 max=255 step=1 default=128 value=128
contrast (int) : min=0 max=255 step=1 default=32 value=32
saturation (int) : min=0 max=100 step=1 default=64 value=64
hue (int) : min=-180 max=180 step=1 default=0 value=0
white_balance_temperature_auto (bool) : default=1 value=1
gamma (int) : min=90 max=150 step=1 default=120 value=120
power_line_frequency (menu) : min=0 max=2 default=1 value=1
white_balance_temperature (int) : min=2800 max=6500 step=1 default=4000 value=4000 flags=inactive
sharpness (int) : min=0 max=7 step=1 default=2 value=2
backlight_compensation (int) : min=0 max=2 step=1 default=1 value=1
exposure_auto (menu) : min=0 max=3 default=3 value=3
exposure_absolute (int) : min=4 max=1250 step=1 default=333 value=333 flags=inactive
exposure_auto_priority (bool) : default=0 value=1
brightness (int) : min=0 max=255 step=1 default=128 value=128
contrast (int) : min=0 max=255 step=1 default=32 value=32
saturation (int) : min=0 max=100 step=1 default=64 value=64
hue (int) : min=-180 max=180 step=1 default=0 value=0
white_balance_temperature_auto (bool) : default=1 value=1
gamma (int) : min=90 max=150 step=1 default=120 value=120
power_line_frequency (menu) : min=0 max=2 default=1 value=1
white_balance_temperature (int) : min=2800 max=6500 step=1 default=4000 value=4000 flags=inactive
sharpness (int) : min=0 max=7 step=1 default=2 value=2
backlight_compensation (int) : min=0 max=2 step=1 default=1 value=1
Last edited by 2ion (2015-05-29 15:23:31)

Similar Messages

  • Troubleshooting 6th gen ipod nano "unable to identify ipod"

    Just this evening I plugged my ipod in to my laptop and I continually recieve the message that says something along the lines of "unable to identify ipod". I ran through the trouble shooting tips on the support website, including new usb port, restart, uninstall-reinstall, and turning off my anti-virus. Is there something else I can do to get my computer to recognize my device? Thanks in advance for your replies.

    Your problem is completely different from the original post. The OP could not run the correct version of iTunes on their older computer. You're much more likely to get the help you need by starting your own thread with a properly descriptive subject line.
    If you need instructions on how to start a new thread, see this link:
    http://discussions.apple.com/ann.jspa?annID=650
    Best of luck.

  • Why Unable to identify a user for 802.1X authentication (0x50001)?

    Hello, 
      We are trying to set up wifi single-sign-on. When logging to a laptop get a message
    "Connecting to Pivot_Users" and after some time "Unable to connect to Pivot_Users" and after that we are logged in to a laptop and successfully connected to Pivot_Users wifi network.
    Server: windows server 2003 (with all updates)
    laptop: windows 7 professional SP1 (with all updates)
    When looking to event log i found this error:
    Log Name:      Security
    Source:        Microsoft-Windows-Security-Auditing
    Date:          2012-10-10 10:38:01
    Event ID:      5632
    Task Category: Other Logon/Logoff Events
    Level:         Information
    Keywords:      Audit Failure
    User:          N/A
    Computer:      sba01-nb
    Description:
    A request was made to authenticate to a wireless network.
    Subject:
    Security ID:                
    Account Name:                -
    Account Domain:                -
    Logon ID:                0x0
    Network Information:
    Name (SSID):                Pivot_Users
    Interface GUID:                {64773f24-bf8b-4e91-bbd7-eb199e3c2c5e}
    Local MAC Address:        C4:85:08:12:77:44
    Peer MAC Address:        00:24:97:83:8E:61
    Additional Information:
    Reason Code:                Unable to identify a user for 802.1X authentication (0x50001)
    Error Code:                0x525
    EAP Reason Code:        0x0
    EAP Root Cause String:        
    EAP Error Code:                0x0
    Event Xml:
      <System>
        <Provider Name="Microsoft-Windows-Security-Auditing" Guid="{54849625-5478-4994-A5BA-3E3B0328C30D}" />
        <EventID>5632</EventID>
        <Version>1</Version>
        <Level>0</Level>
        <Task>12551</Task>
        <Opcode>0</Opcode>
        <Keywords>0x8010000000000000</Keywords>
        <TimeCreated SystemTime="2012-10-10T07:38:01.093305500Z" />
        <EventRecordID>37791</EventRecordID>
        <Correlation />
        <Execution ProcessID="760" ThreadID="2224" />
        <Channel>Security</Channel>
        <Computer>sba01-nb</Computer>
        <Security />
      </System>
      <EventData>
        <Data Name="SSID">Pivot_Users</Data>
        <Data Name="Identity">
        </Data>
        <Data Name="SubjectUserName">-</Data>
        <Data Name="SubjectDomainName">-</Data>
        <Data Name="SubjectLogonId">0x0</Data>
        <Data Name="PeerMac">00:24:97:83:8E:61</Data>
        <Data Name="LocalMac">C4:85:08:12:77:44</Data>
        <Data Name="IntfGuid">{64773F24-BF8B-4E91-BBD7-EB199E3C2C5E}</Data>
        <Data Name="ReasonCode">0x50001</Data>
        <Data Name="ReasonText">Unable to identify a user for 802.1X authentication</Data>
        <Data Name="ErrorCode">0x525</Data>
        <Data Name="EAPReasonCode">0x0</Data>
        <Data Name="EapRootCauseString">
        </Data>
        <Data Name="EAPErrorCode">0x0</Data>
      </EventData>
    </Event>
    Thank you for answer and help.
    Regards, 
      Tadas

    Hi,
    Thanks for your post.
    Have you configured the client to only use user authentication for 802.1X? If so, I would like to inform you that this is expected when you configure the 802.1X to user only authentication.
    Here is the process that is followed.
    1. As soon as client is connected to the network the Authenticator (switch) periodically sends EAP request packet/frame to the client/supplicant.
    2. The client has to respond back with an identify and if its configured only for User authentication then it will send blank identity.
    3. The Authenticator cannot validate and the authentication would fail.
    4. Windows client is configured for a block time of 20 min. So, once the authentication fails the NIC card will go in block time for 20 min until there is a change in credentials. So, even if the authenticatior(swithch) is periodically sending EAP request
    it will just ignore them
    5. You will see event 15506 after the event 15514.
    Here’s the technet that you we can refer for the reason code : Reason: 0x50001 that we see in the event 15514
    http://technet.microsoft.com/en-us/library/cc727747(WS.10).aspx
    0x50001 = Dec 327681
    Reason code:  327681   Event log message:  The 802.1X module was unable to identify a set of credentials to be used. [An example is when the authentication mode is set to “User” but no user is logged on.]   # def name: 
    ONEX_UNABLE_TO_IDENTIFY_USER
    Best Regards,
    Aiden
    Aiden Cao
    TechNet Community Support

  • Sorry we've been unable to identify this hotspot

    This error within this app has been going on for years, and it's still not sorted
    I've got my laptop connected to my a BT Wifi Fon connection.
    Right next to it, I've got my Android Tab, again picking up the Fon signal, 
    Right next to that I've got my phone, that gives me the error message:
    "sorry we've been unable to identify this hotspot"
    At other times the phone will connect but not the tab, and again on other days the Android devices connect, but not the laptop.
    Frustratingly, some days i have absolutely no problems connecting at all.
    PS, this all takes place in the same location, 

    BTWifi- Fon hotspots are not guaranteed to work. This is because they are dependant on the owner of the hotspot to have their Homehub turned on. It is also possible that the owner of the hotspot is using the available bandwidth and as it is their Homehub they have precedence over other users.
    It could also be that the Homehub is needing a reset. That is up to the owner of the hotspot who is under no obligation to do that and it can not be done by BT.

  • Unable to identify the exchange protocol of the message (sync AS2 MDN)

    Hi,
    We got the following error:
    Description: Unable to identify the exchange protocol of the message
    StackTrace:
    Error -: AIP-50080: Exchange protocol identification error
         at oracle.tip.adapter.b2b.engine.Engine.processIncomingMessage(Engine.java:1367)
         at oracle.tip.adapter.b2b.msgproc.Request.postTransmit(Request.java:2370)
         at oracle.tip.adapter.b2b.msgproc.Request.outgoingRequestPostColab(Request.java:1813)
         at oracle.tip.adapter.b2b.msgproc.Request.outgoingRequest(Request.java:968)
         at oracle.tip.adapter.b2b.engine.Engine.processOutgoingMessage(Engine.java:1152)
         at oracle.tip.adapter.b2b.xmlgwIntg.XMLGWIntegration.raiseOutboundMessage(XMLGWIntegration.java:168)
         at oracle.tip.adapter.b2b.xmlgwIntg.Outbound.onMessage(Outbound.java:297)
         at oracle.jms.AQjmsListenerWorker.dispatchOneMsg(AQjmsListenerWorker.java:316)
         at oracle.jms.AQjmsListenerWorker.run(AQjmsListenerWorker.java:129)
         at java.lang.Thread.run(Thread.java:534)
    Here is the Wire message (sync MDN)
    =======================
    Message-ID=<23033756.391232032071968.JavaMail.SYSTEM@INUBITTEST>
    Subject=Your ORDERS AS2
    [email protected]
    Content-Length=1347
    MIME-Version=1.0
    Server=Apache
    Date=Thu, 15 Jan 2009 15:07:52 GMT
    Content-Type=multipart/mixed;      boundary="----=_Part_53998_23619909.1232032071968"
    [email protected]
    ------=_Part_53998_23619909.1232032071968
    Content-Type: text/plain; charset=UTF-8; name=test.txt
    Content-Transfer-Encoding: 7bit
    Content-Disposition: attachment; filename=test.txt
    Message-ID: <17080722.371232032071906.JavaMail.SYSTEM@INUBITTEST>
    MIME-Version: 1.0
    Content-Type: multipart/report; report-type=disposition-notification;
         boundary="----=_Part_53997_14786767.1232032071906"
    AS2-Version: 1.1
    AS2-From: test_AS2
    AS2-To: as2me
    ------=_Part_53997_14786767.1232032071906
    Content-Type: text/plain; charset=us-ascii
    Content-Transfer-Encoding: 7bit
    MDN for Message ID: <33156:4:0:137@as2me>
    From: as2me
    To: test_AS2
    Received on: Thu, 15 Jan 2009 16:07:51 +0100
    Status: processed
    Comment: This is not a guarantee that the message has
    been completely processed or unterstood.
    ------=_Part_53997_14786767.1232032071906
    Content-Type: message/disposition-notification
    Content-Transfer-Encoding: 7bit
    Reporting-UA: inubit Integration Server
    Original-Recipient: rfc822; test_AS2
    Final-Recipient: rfc822; test_AS2
    Original-Message-ID: <33156:4:0:137@as2me>
    Disposition: automatic-action/MDN-sent-automatically; processed
    Received-Content-MIC: 5kFOLMXOUurpm6DUTA8IMRj5gcs=, sha1
    ------=_Part_53997_14786767.1232032071906--
    ------=_Part_53998_23619909.1232032071968--
    ============================
    The communication with our TP is going well, we are able to send, receive messages over AS2 and send back MDN, but we are not able
    to receive their MDN.
    Edit:
    It seems that after the latest MLR patch, the error changed to [IPT_HttpSendError] HTTP encounters send error :. Premature EOF encounter but the roots seem to lead to the problem with MDN as B2B is sending the message a couple of times now and gives the mentioned EOF error.
    Please advise,
    Thank you
    Edited by: Kamil Zadora on Jan 30, 2009 3:44 AM

    Hi Ramesh,
    Yes, agreement uses AS2 IDentifiers. Incoming messages are recognized correctly, and we send back sync MDN that is correctly received by our TP. They also recieve our messages correctly although Oracle B2B does not recognize the MDN from them. I think that this causes that, now after applying the latest MLR patch, B2B tries to send it around 6 times and gives the Unexpected EOF error.
    Thank you for your help in advance,
    Kind regards,

  • Unable to view this webcam in Safari

    Hi ,
    Does anyone know why I am unable to view this webcam in Safari?
    http://www.cam1.carvoeiro.com/
    It appears fine in Firefox & IE but I only really want one browser on my computer.
    Many thanks for any help on this on,
    Dave

    I've just posted a message on the Webcam's own forum, asking if any mac users out there can see the webcam. I've just had a reply from a Powerbook G4 user using Safari that say's he can see it perfectly.
    It must be some setting on my Mac (although I have tried it under another users name with no luck also) can anyone else out there see it?
    http://www.cam1.carvoeiro.com/
    or
    http://www.cam1.carvoeiro.com/wcshow.php?img=_current
    Thanks,
    Dave

  • QTP unable to identify objects in a flex application

    Hi,
    I am having an application that runs on flex 3.6 SDK. I am trying to automate the same using QTP 10.0, but, I am unable to identify the objects. I have installed the Flex 4.5 add-in, but still unable to recognize objects.
    Upon browsing some forums, i found that I need to compile the files "automation.swc, automation_agent.swc, automation_dmv.swc, qtp.swc, automation_flashflexkit.swc" by including them in <include-libraries> ...</include-libraries>  tags in "flex-config.xml" file present under "C:\Program Files\Adobe\Flex Builder 3 Plug-in\sdks\3.6.0\frameworks". We did that, but still, not able to identify objects.
    It would be of great help to me if any some one could tell if I am missing out anything ?

    hello,
    not only need the objects be enclosed by their parent frame, but they also need to be "on top of it" ... meaning if you imagine your report layout as a set of layers that you look at from the side, your "layout surface" would be the bottom most layer and then all objects would be layered on top of each other. in this view, only objects that are in layers above a particular frame can become its children. after that the relationship is determined whether or not an object is inside a frame or not.
    you might want to check your object navigator to see whether or not the particular objects are actually in the right place in the hierarchy.
    thanks,
    ph.

  • Siebel database Configuration wizard unable to identify index tablespace

    Hi,
    I'm installing Siebel CRM 8.1.1 on AIX platform. We have RAC enabled database at backend and in that two tablespace has been created, one for data and another one for index. Now in the database configuration wizrd where we have to provide the name of both tablespaces; we provide the name of data tablespae in the Table Tablespace filed and index tablespace in the index tablespace filed of the configuration wizard. Now when we click on the next button. The configuration wizrd gives error of unable to identify index tablespace.
    Why is this happening as index tablespace is properly created in the database. Please help me in this. You quick respance will be highly appriciated.
    Regards,
    Abbasi

    I thought it might be. grantuser.sql generally needs to be modified to suit the underlying database configuration. Glad you got it working.

  • Codedui: Unable To Identify Objects Inside The Virtual Machine

    Hi
    We are unable to identify objects inside the virtual machine. We want to perform some tasks inside the virtual machine. The virtual machine object is getting identified as image. So when we perform tasks like creating a folder or opening any application
    inside that virtual machine, all actions are recorded as image.Need help on this ASAP.
    Thanks

    Hi Haripriya78,
    Thank you for posting in MSDN forum.
    >>Codedui: Unable To Identify Objects Inside The Virtual Machine
    Based on your issue, could you please tell me what operation you do and then get the error message?
    Whether you record and run this coded UI test and then get the error message?
    If possible, please tell me more detailed message about this issue.
    Generally, I know that if you want to identify objects for coded UI test, I know that the
    recorder needs to be present in the machine on which you are trying to record actions.
    For more information, please refer the Vinoth's suggestion to check this issue.
    https://social.msdn.microsoft.com/Forums/vstudio/en-US/1b7a328d-a9b6-48a6-9cb9-8ff8ac7dd435/codedui-unable-to-identify-objects-inside-the-virtual-machine?forum=vsautotest
    If I misunderstanding your issue, please tell me more message about your issue so that we will further help you support this issue.
    Best Regards,
    We are trying to better understand customer views on social support experience, so your participation in this interview project would be greatly appreciated if you have time. Thanks for helping make community forums a great place.
    Click
    HERE to participate the survey.

  • Unable to view external webcam content.  I'm using IE11 with Windows 7 64 bit.  I've tried deactivating Activex control, tried different browsers etc, tweeked the tools for trusted sites etc, but am totally stuck. I know the cams are working as i can view

    Unable to view external webcam content.  I'm using IE11 with Windows 7 64 bit.  I've tried deactivating Activex control, tried different browsers etc, tweeked the tools for trusted sites etc, but am totally stuck. I know the cams are working as i can view them on mobile phone via puffin browser.  I can play Youtube videos etc just fine. So why not the webcam?

    First, confirm that ActiveX Filtering is configured to allow Flash content:
    https://forums.adobe.com/thread/867968
    Internet Explorer 11 introduces a number of changes both to how the browser identifies itself to remote web servers, and to how it processes JavaScript intended to target behaviors specific to Internet Explorer. Unfortunately, this means that content on some sites will be broken until the content provider changes their site to conform to the new development approach required by modern versions of IE.
    You can try to work around these issues by using Compatibility View:
    http://windows.microsoft.com/en-us/internet-explorer/use-compatibility-view#ie=ie-11
    If that is too inconvenient, using Google Chrome may be a preferable alternative.

  • [SOLVED] Unable to connect via an ftp cable with my acer Laptop

    Hello there everyone!
    I can't connect to the internet.Although i installed via ftp the packages and i could successfully ping google.After i installed gnome 3 i can't ping anything.
    I need your help!I have Laptop connected to my router with an ftp cable,my desktop ubuntu pc works fine with the internet,but after reading again and again this two guides :
    https://wiki.archlinux.org/index.php/Be … cessary.29
    https://wiki.archlinux.org/index.php/Network
    nothing seems to work!Could someone please help me?
    Last edited by sepuku (2011-06-04 01:22:46)

    You should check settings in NetworkManager as well, since your settings broke after installing Gnome 3 that seems like a possible culprit.
    Generally off topic:
    Just as a small note, there is such a thing as a FTP cable, though it is also sometimes written as F/UTP due to newer standards names. Basically it is a TP cable where the cables in it are wrapped in foil, hence the name Foiled Twisted Pair. This gives shielding from interference like magnetic fields unlike a UTP cable which is an Unshielded TP cable. There are also several other cable shielding standard names.
    http://en.wikipedia.org/wiki/Twisted_pa … _shielding

  • [Solved] Unable to set bluetooth stick on laptop

    Hi everyone.
    I am trying to set my bluetooth usb device, as it is sad in the wiki, but I am not able to get it run.
    When I plug my bluetooth stick, I got that in my /var/log/messages.log
    Jul 7 14:38:34 tangra usbcore: registered new interface driver hci_usb
    and this is what I have in my /var/log/messages.log when I start the bluetooth daemon:
    Jul 7 14:38:24 tangra usb 2-2: new full speed USB device using uhci_hcd and address 2
    Jul 7 14:38:34 tangra usb 2-2: configuration #1 chosen from 1 choice
    Jul 7 14:38:34 tangra Bluetooth: Core ver 2.11
    Jul 7 14:38:34 tangra NET: Registered protocol family 31
    Jul 7 14:38:34 tangra Bluetooth: HCI device and connection manager initialized
    Jul 7 14:38:34 tangra Bluetooth: HCI socket layer initialized
    Jul 7 14:38:34 tangra Bluetooth: HCI USB driver ver 2.9
    Jul 7 14:38:34 tangra usbcore: registered new interface driver hci_usb
    Jul 7 14:41:51 tangra hcid[4165]: Bluetooth HCI daemon
    This is what I have, when I write lsusb:
    Bus 004 Device 001: ID 1d6b:0002
    Bus 005 Device 001: ID 1d6b:0001
    Bus 003 Device 001: ID 1d6b:0001
    Bus 002 Device 002: ID 1131:1001 Integrated System Solution Corp. KY-BT100 Bluetooth Adapter
    Bus 002 Device 001: ID 1d6b:0001
    Bus 001 Device 001: ID 1d6b:0001
    After I plug the device, I am running /etc/rc.d/bluetooth start, and everything seems to be in order, but when I type "hcitool dev" I got nothing displayed. I red the wiki, and I have bluez installed. Where is my mistake. Do I need some software, or... I do not know what. It is my first time when I am using bluetooth in my life.
    Regards.
    Last edited by Gruntz (2008-07-07 12:43:44)

    Hi
    I solved the problem. You need to "hciconfig hci0 up", before run "hcitool dev" and see the device, or "hcitool scan" to scan for bluetooth devices in range.
    Do you know how to brows the files on my mobile phone. I have no gnome or kde.
    Regards.
    Last edited by Gruntz (2008-07-07 12:44:48)

  • [SOLVED] Unable to determine major/minor number of root device - USB

    I installed Arch on a USB harddrive of mine from within VirtualBox with the intention of running the installation (via the drive) on a laptop in my house. I passed through the drive through by creating a special vmdk (here - it's for "expert users only". ) and installed Arch on it by booting off the Arch 2011.08.19 iso and following the instructions. I do recall the installer complaining because /sbin/mkinitcpio was missing, so I copied over the one from the host (which is also an up-to-date Arch system). After that, everything worked and I was able to boot the drive within virtualbox.
    Then I went and plugged it in to another laptop in the house and, surprisingly (for me at least), it got past GRUB. My joy was short-lived, because it failed just a bit later:
    :: Running Hook [udev]
    :: Triggering uevents...done.
    ERROR: Unable to determine major/minor number of root device 'Waiting 10 seconds
    for device /dev/disk/by-uuid/[the uuid] ...
    /dev/disk/by-uuid/(the uuid)'.
    You are being dropped to a recovery shell
    Type 'exit' to try and continue booting
    sh: can't access tty: job control turned off
    [ramfs /]#
    So I googled around for a while and plugged it back in to my computer, booted it up in virtualbox, and added "usb" to the HOOKS array right after udev in /etc/mkinitcpio.conf. Then I rebuilt the initramfs:
    # mkinitcpio -p linux
    So I plugged it back into the laptop, booted it, and got the same error.
    Later, in an attempt to isolate the problem, I removed "sata" from HOOKS, ran the same mkinitcpio command again, and rebooted the VM. I got what looked like the same error as the one above. yay. So I guess the usb hook isn't being loaded or something like that. (I've since added the "sata" hook back and rebuilt the initramfs so I can mess around in the VM )
    I've tried removing autodetect from HOOKS (saw that in some threads) and trying different USB ports on the laptop, but nothing seems to be working. I also checked to see if virtualbox was providing a bogus uuid or something, but the one it's specifying seems to be correct - I looked in my computer's /dev/disk/by-uuid and it matched.
    Info on the drive (first partition is /boot, second is swap (derp!), third is /, and fourth is /home):
    # sudo fdisk -l /dev/sdg
    Disk /dev/sdg: 500.1 GB, 500107861504 bytes
    255 heads, 63 sectors/track, 60801 cylinders, total 976773167 sectors
    Units = sectors of 1 * 512 = 512 bytes
    Sector size (logical/physical): 512 bytes / 512 bytes
    I/O size (minimum/optimal): 512 bytes / 512 bytes
    Disk identifier: 0x00016b3d
    Device Boot Start End Blocks Id System
    /dev/sdg1 * 63 208844 104391 83 Linux
    /dev/sdg2 208845 4417874 2104515 82 Linux swap / Solaris
    /dev/sdg3 4417875 209230559 102406342+ 83 Linux
    /dev/sdg4 209230560 976768064 383768752+ 83 Linux
    Screengrab of my VirtualBox storage setup (just for giggles):
    My /etc/mkinitcpio.conf:
    # vim:set ft=sh
    # MODULES
    # The following modules are loaded before any boot hooks are
    # run. Advanced users may wish to specify all system modules
    # in this array. For instance:
    # MODULES="piix ide_disk reiserfs"
    MODULES=""
    # BINARIES
    # This setting includes any additional binaries a given user may
    # wish into the CPIO image. This is run first, so it may be used to
    # override the actual binaries used in a given hook.
    # (Existing files are NOT overwritten if already added)
    # BINARIES are dependency parsed, so you may safely ignore libraries
    BINARIES=""
    # FILES
    # This setting is similar to BINARIES above, however, files are added
    # as-is and are not parsed in any way. This is useful for config files.
    # Some users may wish to include modprobe.conf for custom module options
    # like so:
    # FILES="/etc/modprobe.d/modprobe.conf"
    FILES=""
    # HOOKS
    # This is the most important setting in this file. The HOOKS control the
    # modules and scripts added to the image, and what happens at boot time.
    # Order is important, and it is recommended that you do not change the
    # order in which HOOKS are added. Run 'mkinitcpio -H <hook name>' for
    # help on a given hook.
    # 'base' is _required_ unless you know precisely what you are doing.
    # 'udev' is _required_ in order to automatically load modules
    # 'filesystems' is _required_ unless you specify your fs modules in MODULES
    # Examples:
    ## This setup specifies all modules in the MODULES setting above.
    ## No raid, lvm2, or encrypted root is needed.
    # HOOKS="base"
    ## This setup will autodetect all modules for your system and should
    ## work as a sane default
    # HOOKS="base udev autodetect pata scsi sata filesystems"
    ## This is identical to the above, except the old ide subsystem is
    ## used for IDE devices instead of the new pata subsystem.
    # HOOKS="base udev autodetect ide scsi sata filesystems"
    ## This setup will generate a 'full' image which supports most systems.
    ## No autodetection is done.
    # HOOKS="base udev pata scsi sata usb filesystems"
    ## This setup assembles a pata mdadm array with an encrypted root FS.
    ## Note: See 'mkinitcpio -H mdadm' for more information on raid devices.
    # HOOKS="base udev pata mdadm encrypt filesystems"
    ## This setup loads an lvm2 volume group on a usb device.
    # HOOKS="base udev usb lvm2 filesystems"
    # Tried this line instead -- didn't work either
    #HOOKS="base udev usb autodetect pata scsi sata filesystems usbinput"
    HOOKS="base udev usb sata filesystems"
    # COMPRESSION
    # Use this to compress the initramfs image. With kernels earlier than
    # 2.6.30, only gzip is supported, which is also the default. Newer kernels
    # support gzip, bzip2 and lzma. Kernels 2.6.38 and later support xz
    # compression.
    #COMPRESSION="gzip"
    #COMPRESSION="bzip2"
    #COMPRESSION="lzma"
    #COMPRESSION="xz"
    #COMPRESSION="lzop"
    # COMPRESSION_OPTIONS
    # Additional options for the compressor
    #COMPRESSION_OPTIONS=""
    My GRUB menu.lst:
    # Config file for GRUB - The GNU GRand Unified Bootloader
    # /boot/grub/menu.lst
    # DEVICE NAME CONVERSIONS
    # Linux Grub
    # /dev/fd0 (fd0)
    # /dev/sda (hd0)
    # /dev/sdb2 (hd1,1)
    # /dev/sda3 (hd0,2)
    # FRAMEBUFFER RESOLUTION SETTINGS
    # +-------------------------------------------------+
    # | 640x480 800x600 1024x768 1280x1024
    # ----+--------------------------------------------
    # 256 | 0x301=769 0x303=771 0x305=773 0x307=775
    # 32K | 0x310=784 0x313=787 0x316=790 0x319=793
    # 64K | 0x311=785 0x314=788 0x317=791 0x31A=794
    # 16M | 0x312=786 0x315=789 0x318=792 0x31B=795
    # +-------------------------------------------------+
    # for more details and different resolutions see
    # https://wiki.archlinux.org/index.php/GRUB#Framebuffer_resolution
    # general configuration:
    timeout 5
    default 0
    color light-blue/black light-cyan/blue
    # boot sections follow
    # each is implicitly numbered from 0 in the order of appearance below
    # TIP: If you want a 1024x768 framebuffer, add "vga=773" to your kernel line.
    # (0) Arch Linux
    title Arch Linux
    root (hd0,0)
    kernel /vmlinuz-linux root=/dev/disk/by-uuid/b4a677d0-cb0d-4acd-bb09-2dc2f4b9501f ro
    initrd /initramfs-linux.img
    # (1) Arch Linux
    title Arch Linux Fallback
    root (hd0,0)
    kernel /vmlinuz-linux root=/dev/disk/by-uuid/b4a677d0-cb0d-4acd-bb09-2dc2f4b9501f ro
    initrd /initramfs-linux-fallback.img
    # (2) Windows
    #title Windows
    #rootnoverify (hd0,0)
    #makeactive
    #chainloader +1
    Last edited by UncleNinja (2011-12-02 15:33:21)

    UncleNinja wrote:
    skunktrader wrote:https://bugs.archlinux.org/task/27385
    Perfect! Thank you!
    Would it be safe to copy over the version from HEAD into my mkinitcpio?
    EDIT: nevermind, derp derp the package is updated
    EDIT again: Actually, it's not.
    I copied over the init_functions in HEAD into /lib/initcpio/init_functions and rebuilt the initramfs. It worked!
    Thanks guys!
    Last edited by UncleNinja (2011-12-02 15:35:20)

  • [Solved] Unable to find root device

    Hi guys,
    it's been three days now that my laptop refuses to boot with a message from systemd like this:
    ERROR: device 'UUID=xxx...' not found. Skipping fsck.
    ERROR: Unable to find root device 'UUID=xxx...'.
    You are being dropped to a recovery shell.
    That said, keep in mind that I'm saying "three days" just because it's in the past two days that I've spent most of the time searching in the Internet for a solution of what seems just to be a well-known, very common problem, especially when it arises after a kernel upgrade (as in my case).
    But believe me, I've been trying this and that through the live Arch Linux environment, but without the slightest improvement: regeneration of the initramfs, regeneration of /etc/fstab, reconfiguration of GRUB (although this was clearly unhelpful, since the problem arises when the kernel has already been booted), small changes in the hooks in /etc/mkinitcpio.conf, small changes to some modules loaded at boot, downgrading linux... Nothing works.
    I'm now writing from another computer, so I cannot post the entire output of useful commands now, but if you need to know something I will give you the necessary information.
    In the meanwhile, notice that I use Linux LVM partition with logical volumes formatted with Btrfs, without encryption.
    It's strange that even with the dowgrade from Linux 3.18.3 (the one after whose installation the system was unusable) to 3.18.2 the problem still remains.
    However, the only thing I managed to take from my system is the output of dmesg, obtained from the recovery shell, after having set the debug settings for systemd in the kernel command line before booting.
    [ 0.000000] Initializing cgroup subsys cpuset
    [ 0.000000] Initializing cgroup subsys cpu
    [ 0.000000] Initializing cgroup subsys cpuacct
    [ 0.000000] Linux version 3.18.4-1-ARCH (builduser@tobias) (gcc version 4.9.2 20141224 (prerelease) (GCC) ) #1 SMP PREEMPT Tue Jan 27 20:45:02 CET 2015
    [ 0.000000] Command line: BOOT_IMAGE=/vmlinuz-linux root=UUID=345f6168-2ff7-41fd-bf0e-050d4dd6795d systemd.log_level=debug systemd.log_target=kmsg log_buf_len=1M rw quiet
    [ 0.000000] e820: BIOS-provided physical RAM map:
    [ 0.000000] BIOS-e820: [mem 0x0000000000000000-0x00000000000913ff] usable
    [ 0.000000] BIOS-e820: [mem 0x0000000000091400-0x000000000009ffff] reserved
    [ 0.000000] BIOS-e820: [mem 0x00000000000e0000-0x00000000000fffff] reserved
    [ 0.000000] BIOS-e820: [mem 0x0000000000100000-0x00000000c8c6cfff] usable
    [ 0.000000] BIOS-e820: [mem 0x00000000c8c6d000-0x00000000dae8cfff] reserved
    [ 0.000000] BIOS-e820: [mem 0x00000000dae8d000-0x00000000daeb6fff] ACPI data
    [ 0.000000] BIOS-e820: [mem 0x00000000daeb7000-0x00000000db802fff] ACPI NVS
    [ 0.000000] BIOS-e820: [mem 0x00000000db803000-0x00000000dbafffff] reserved
    [ 0.000000] BIOS-e820: [mem 0x00000000dd000000-0x00000000df1fffff] reserved
    [ 0.000000] BIOS-e820: [mem 0x00000000f8000000-0x00000000fbffffff] reserved
    [ 0.000000] BIOS-e820: [mem 0x00000000fec00000-0x00000000fec00fff] reserved
    [ 0.000000] BIOS-e820: [mem 0x00000000fed00000-0x00000000fed03fff] reserved
    [ 0.000000] BIOS-e820: [mem 0x00000000fed1c000-0x00000000fed1ffff] reserved
    [ 0.000000] BIOS-e820: [mem 0x00000000fee00000-0x00000000fee00fff] reserved
    [ 0.000000] BIOS-e820: [mem 0x00000000ff000000-0x00000000ffffffff] reserved
    [ 0.000000] BIOS-e820: [mem 0x0000000100000000-0x000000021edfffff] usable
    [ 0.000000] NX (Execute Disable) protection: active
    [ 0.000000] SMBIOS 2.8 present.
    [ 0.000000] DMI: Dell Inc. Latitude E5550/0YM97J, BIOS A03 10/30/2014
    [ 0.000000] e820: update [mem 0x00000000-0x00000fff] usable ==> reserved
    [ 0.000000] e820: remove [mem 0x000a0000-0x000fffff] usable
    [ 0.000000] AGP: No AGP bridge found
    [ 0.000000] e820: last_pfn = 0x21ee00 max_arch_pfn = 0x400000000
    [ 0.000000] MTRR default type: uncachable
    [ 0.000000] MTRR fixed ranges enabled:
    [ 0.000000] 00000-9FFFF write-back
    [ 0.000000] A0000-BFFFF uncachable
    [ 0.000000] C0000-FFFFF write-protect
    [ 0.000000] MTRR variable ranges enabled:
    [ 0.000000] 0 base 0000000000 mask 7E00000000 write-back
    [ 0.000000] 1 base 0200000000 mask 7FE0000000 write-back
    [ 0.000000] 2 base 00E0000000 mask 7FE0000000 uncachable
    [ 0.000000] 3 base 00DE000000 mask 7FFE000000 uncachable
    [ 0.000000] 4 base 00DD000000 mask 7FFF000000 uncachable
    [ 0.000000] 5 base 021F000000 mask 7FFF000000 uncachable
    [ 0.000000] 6 base 021EE00000 mask 7FFFE00000 uncachable
    [ 0.000000] 7 disabled
    [ 0.000000] 8 disabled
    [ 0.000000] 9 disabled
    [ 0.000000] x86 PAT enabled: cpu 0, old 0x7040600070406, new 0x7010600070106
    [ 0.000000] e820: update [mem 0xdd000000-0xffffffff] usable ==> reserved
    [ 0.000000] e820: last_pfn = 0xc8c6d max_arch_pfn = 0x400000000
    [ 0.000000] found SMP MP-table at [mem 0x000fda70-0x000fda7f] mapped at [ffff8800000fda70]
    [ 0.000000] Scanning 1 areas for low memory corruption
    [ 0.000000] Base memory trampoline at [ffff88000008b000] 8b000 size 24576
    [ 0.000000] Using GB pages for direct mapping
    [ 0.000000] init_memory_mapping: [mem 0x00000000-0x000fffff]
    [ 0.000000] [mem 0x00000000-0x000fffff] page 4k
    [ 0.000000] BRK [0x01b36000, 0x01b36fff] PGTABLE
    [ 0.000000] BRK [0x01b37000, 0x01b37fff] PGTABLE
    [ 0.000000] BRK [0x01b38000, 0x01b38fff] PGTABLE
    [ 0.000000] init_memory_mapping: [mem 0x21ec00000-0x21edfffff]
    [ 0.000000] [mem 0x21ec00000-0x21edfffff] page 2M
    [ 0.000000] BRK [0x01b39000, 0x01b39fff] PGTABLE
    [ 0.000000] init_memory_mapping: [mem 0x21c000000-0x21ebfffff]
    [ 0.000000] [mem 0x21c000000-0x21ebfffff] page 2M
    [ 0.000000] init_memory_mapping: [mem 0x200000000-0x21bffffff]
    [ 0.000000] [mem 0x200000000-0x21bffffff] page 2M
    [ 0.000000] init_memory_mapping: [mem 0x00100000-0xc8c6cfff]
    [ 0.000000] [mem 0x00100000-0x001fffff] page 4k
    [ 0.000000] [mem 0x00200000-0x3fffffff] page 2M
    [ 0.000000] [mem 0x40000000-0xbfffffff] page 1G
    [ 0.000000] [mem 0xc0000000-0xc8bfffff] page 2M
    [ 0.000000] [mem 0xc8c00000-0xc8c6cfff] page 4k
    [ 0.000000] init_memory_mapping: [mem 0x100000000-0x1ffffffff]
    [ 0.000000] [mem 0x100000000-0x1ffffffff] page 1G
    [ 0.000000] log_buf_len: 1048576 bytes
    [ 0.000000] early log buf free: 519600(99%)
    [ 0.000000] RAMDISK: [mem 0x3539c000-0x369c5fff]
    [ 0.000000] ACPI: Early table checksum verification disabled
    [ 0.000000] ACPI: RSDP 0x00000000000EF280 000024 (v02 DELL )
    [ 0.000000] ACPI: XSDT 0x00000000DAE960A8 0000CC (v01 DELL CBX3 01072009 AMI 00010013)
    [ 0.000000] ACPI: FACP 0x00000000DAEA9C60 00010C (v05 DELL CBX3 01072009 AMI 00010013)
    [ 0.000000] ACPI: DSDT 0x00000000DAE96200 013A5B (v02 DELL CBX3 01072009 INTL 20120913)
    [ 0.000000] ACPI: FACS 0x00000000DB800F80 000040
    [ 0.000000] ACPI: APIC 0x00000000DAEA9D70 000084 (v03 DELL CBX3 01072009 AMI 00010013)
    [ 0.000000] ACPI: FPDT 0x00000000DAEA9DF8 000044 (v01 DELL CBX3 01072009 AMI 00010013)
    [ 0.000000] ACPI: FIDT 0x00000000DAEA9E40 00009C (v01 DELL CBX3 01072009 AMI 00010013)
    [ 0.000000] ACPI: MCFG 0x00000000DAEA9EE0 00003C (v01 DELL CBX3 01072009 MSFT 00000097)
    [ 0.000000] ACPI: HPET 0x00000000DAEA9F20 000038 (v01 DELL CBX3 01072009 AMI. 00000005)
    [ 0.000000] ACPI: SSDT 0x00000000DAEA9F58 0004B5 (v01 SataRe SataTabl 00001000 INTL 20120913)
    [ 0.000000] ACPI: UEFI 0x00000000DAEAA410 000042 (v01 00000000 00000000)
    [ 0.000000] ACPI: SSDT 0x00000000DAEAA458 000C7D (v02 Ther_R Ther_Rvp 00001000 INTL 20120913)
    [ 0.000000] ACPI: ASF! 0x00000000DAEAB0D8 0000A0 (v32 INTEL HCG 00000001 TFSM 000F4240)
    [ 0.000000] ACPI: SSDT 0x00000000DAEAB178 00051F (v02 PmRef Cpu0Ist 00003000 INTL 20120913)
    [ 0.000000] ACPI: SSDT 0x00000000DAEAB698 000B74 (v02 CpuRef CpuSsdt 00003000 INTL 20120913)
    [ 0.000000] ACPI: SSDT 0x00000000DAEAC210 0001C7 (v02 PmRef LakeTiny 00003000 INTL 20120913)
    [ 0.000000] ACPI: SSDT 0x00000000DAEAC3D8 0003A5 (v02 CppcTa CppcTabl 00001000 INTL 20120913)
    [ 0.000000] ACPI: PCCT 0x00000000DAEAC780 00006E (v05 PcctTa PcctTabl 00001000 INTL 20120913)
    [ 0.000000] ACPI: SSDT 0x00000000DAEAC7F0 000AC4 (v02 Cpc_Ta Cpc_Tabl 00001000 INTL 20120913)
    [ 0.000000] ACPI: SSDT 0x00000000DAEAD2B8 0041AC (v02 SaSsdt SaSsdt 00003000 INTL 20120913)
    [ 0.000000] ACPI: SSDT 0x00000000DAEB1468 004508 (v01 DptfTa DptfTabl 00001000 INTL 20120913)
    [ 0.000000] ACPI: SLIC 0x00000000DAEB5970 000176 (v03 DELL CBX3 01072009 MSFT 00010013)
    [ 0.000000] ACPI: MSDM 0x00000000DAEB5AE8 000055 (v03 DELL CBX3 06222004 AMI 00010013)
    [ 0.000000] ACPI: DMAR 0x00000000DAEB5B40 0000B0 (v01 INTEL BDW 00000001 INTL 00000001)
    [ 0.000000] ACPI: Local APIC address 0xfee00000
    [ 0.000000] No NUMA configuration found
    [ 0.000000] Faking a node at [mem 0x0000000000000000-0x000000021edfffff]
    [ 0.000000] NODE_DATA(0) allocated [mem 0x21ecfa000-0x21ecfdfff]
    [ 0.000000] [ffffea0000000000-ffffea00087fffff] PMD -> [ffff880216800000-ffff88021e3fffff] on node 0
    [ 0.000000] Zone ranges:
    [ 0.000000] DMA [mem 0x00001000-0x00ffffff]
    [ 0.000000] DMA32 [mem 0x01000000-0xffffffff]
    [ 0.000000] Normal [mem 0x100000000-0x21edfffff]
    [ 0.000000] Movable zone start for each node
    [ 0.000000] Early memory node ranges
    [ 0.000000] node 0: [mem 0x00001000-0x00090fff]
    [ 0.000000] node 0: [mem 0x00100000-0xc8c6cfff]
    [ 0.000000] node 0: [mem 0x100000000-0x21edfffff]
    [ 0.000000] Initmem setup node 0 [mem 0x00001000-0x21edfffff]
    [ 0.000000] On node 0 totalpages: 1997309
    [ 0.000000] DMA zone: 64 pages used for memmap
    [ 0.000000] DMA zone: 21 pages reserved
    [ 0.000000] DMA zone: 3984 pages, LIFO batch:0
    [ 0.000000] DMA32 zone: 12786 pages used for memmap
    [ 0.000000] DMA32 zone: 818285 pages, LIFO batch:31
    [ 0.000000] Normal zone: 18360 pages used for memmap
    [ 0.000000] Normal zone: 1175040 pages, LIFO batch:31
    [ 0.000000] Reserving Intel graphics stolen memory at 0xdd200000-0xdf1fffff
    [ 0.000000] ACPI: PM-Timer IO Port: 0x1808
    [ 0.000000] ACPI: Local APIC address 0xfee00000
    [ 0.000000] ACPI: LAPIC (acpi_id[0x01] lapic_id[0x00] enabled)
    [ 0.000000] ACPI: LAPIC (acpi_id[0x02] lapic_id[0x02] enabled)
    [ 0.000000] ACPI: LAPIC (acpi_id[0x03] lapic_id[0x01] enabled)
    [ 0.000000] ACPI: LAPIC (acpi_id[0x04] lapic_id[0x03] enabled)
    [ 0.000000] ACPI: LAPIC_NMI (acpi_id[0x01] high dfl lint[0xe4])
    [ 0.000000] ACPI: NMI not connected to LINT 1!
    [ 0.000000] ACPI: LAPIC_NMI (acpi_id[0x02] dfl edge lint[0x35])
    [ 0.000000] ACPI: NMI not connected to LINT 1!
    [ 0.000000] ACPI: LAPIC_NMI (acpi_id[0x03] dfl edge lint[0x4b])
    [ 0.000000] ACPI: NMI not connected to LINT 1!
    [ 0.000000] ACPI: LAPIC_NMI (acpi_id[0x04] high edge lint[0x59])
    [ 0.000000] ACPI: NMI not connected to LINT 1!
    [ 0.000000] ACPI: IOAPIC (id[0x02] address[0xfec00000] gsi_base[0])
    [ 0.000000] IOAPIC[0]: apic_id 2, version 32, address 0xfec00000, GSI 0-39
    [ 0.000000] ACPI: INT_SRC_OVR (bus 0 bus_irq 0 global_irq 2 dfl dfl)
    [ 0.000000] ACPI: INT_SRC_OVR (bus 0 bus_irq 9 global_irq 9 high level)
    [ 0.000000] ACPI: IRQ0 used by override.
    [ 0.000000] ACPI: IRQ9 used by override.
    [ 0.000000] Using ACPI (MADT) for SMP configuration information
    [ 0.000000] ACPI: HPET id: 0x8086a701 base: 0xfed00000
    [ 0.000000] smpboot: Allowing 4 CPUs, 0 hotplug CPUs
    [ 0.000000] PM: Registered nosave memory: [mem 0x00000000-0x00000fff]
    [ 0.000000] PM: Registered nosave memory: [mem 0x00091000-0x00091fff]
    [ 0.000000] PM: Registered nosave memory: [mem 0x00092000-0x0009ffff]
    [ 0.000000] PM: Registered nosave memory: [mem 0x000a0000-0x000dffff]
    [ 0.000000] PM: Registered nosave memory: [mem 0x000e0000-0x000fffff]
    [ 0.000000] PM: Registered nosave memory: [mem 0xc8c6d000-0xdae8cfff]
    [ 0.000000] PM: Registered nosave memory: [mem 0xdae8d000-0xdaeb6fff]
    [ 0.000000] PM: Registered nosave memory: [mem 0xdaeb7000-0xdb802fff]
    [ 0.000000] PM: Registered nosave memory: [mem 0xdb803000-0xdbafffff]
    [ 0.000000] PM: Registered nosave memory: [mem 0xdbb00000-0xdcffffff]
    [ 0.000000] PM: Registered nosave memory: [mem 0xdd000000-0xdf1fffff]
    [ 0.000000] PM: Registered nosave memory: [mem 0xdf200000-0xf7ffffff]
    [ 0.000000] PM: Registered nosave memory: [mem 0xf8000000-0xfbffffff]
    [ 0.000000] PM: Registered nosave memory: [mem 0xfc000000-0xfebfffff]
    [ 0.000000] PM: Registered nosave memory: [mem 0xfec00000-0xfec00fff]
    [ 0.000000] PM: Registered nosave memory: [mem 0xfec01000-0xfecfffff]
    [ 0.000000] PM: Registered nosave memory: [mem 0xfed00000-0xfed03fff]
    [ 0.000000] PM: Registered nosave memory: [mem 0xfed04000-0xfed1bfff]
    [ 0.000000] PM: Registered nosave memory: [mem 0xfed1c000-0xfed1ffff]
    [ 0.000000] PM: Registered nosave memory: [mem 0xfed20000-0xfedfffff]
    [ 0.000000] PM: Registered nosave memory: [mem 0xfee00000-0xfee00fff]
    [ 0.000000] PM: Registered nosave memory: [mem 0xfee01000-0xfeffffff]
    [ 0.000000] PM: Registered nosave memory: [mem 0xff000000-0xffffffff]
    [ 0.000000] e820: [mem 0xdf200000-0xf7ffffff] available for PCI devices
    [ 0.000000] Booting paravirtualized kernel on bare hardware
    [ 0.000000] setup_percpu: NR_CPUS:128 nr_cpumask_bits:128 nr_cpu_ids:4 nr_node_ids:1
    [ 0.000000] PERCPU: Embedded 30 pages/cpu @ffff88021ea00000 s82880 r8192 d31808 u524288
    [ 0.000000] pcpu-alloc: s82880 r8192 d31808 u524288 alloc=1*2097152
    [ 0.000000] pcpu-alloc: [0] 0 1 2 3
    [ 0.000000] Built 1 zonelists in Node order, mobility grouping on. Total pages: 1966078
    [ 0.000000] Policy zone: Normal
    [ 0.000000] Kernel command line: BOOT_IMAGE=/vmlinuz-linux root=UUID=345f6168-2ff7-41fd-bf0e-050d4dd6795d systemd.log_level=debug systemd.log_target=kmsg log_buf_len=1M rw quiet
    [ 0.000000] PID hash table entries: 4096 (order: 3, 32768 bytes)
    [ 0.000000] xsave: enabled xstate_bv 0x7, cntxt size 0x340 using standard form
    [ 0.000000] AGP: Checking aperture...
    [ 0.000000] AGP: No AGP bridge found
    [ 0.000000] Calgary: detecting Calgary via BIOS EBDA area
    [ 0.000000] Calgary: Unable to locate Rio Grande table in EBDA - bailing!
    [ 0.000000] Memory: 7760140K/7989236K available (5479K kernel code, 908K rwdata, 1720K rodata, 1160K init, 1184K bss, 229096K reserved)
    [ 0.000000] SLUB: HWalign=64, Order=0-3, MinObjects=0, CPUs=4, Nodes=1
    [ 0.000000] Preemptible hierarchical RCU implementation.
    [ 0.000000] RCU dyntick-idle grace-period acceleration is enabled.
    [ 0.000000] Dump stacks of tasks blocking RCU-preempt GP.
    [ 0.000000] RCU restricting CPUs from NR_CPUS=128 to nr_cpu_ids=4.
    [ 0.000000] RCU: Adjusting geometry for rcu_fanout_leaf=16, nr_cpu_ids=4
    [ 0.000000] NR_IRQS:8448 nr_irqs:728 0
    [ 0.000000] Console: colour dummy device 80x25
    [ 0.000000] console [tty0] enabled
    [ 0.000000] allocated 32505856 bytes of page_cgroup
    [ 0.000000] please try 'cgroup_disable=memory' option if you don't want memory cgroups
    [ 0.000000] hpet clockevent registered
    [ 0.000000] tsc: Fast TSC calibration using PIT
    [ 0.000000] tsc: Detected 2593.984 MHz processor
    [ 0.000025] Calibrating delay loop (skipped), value calculated using timer frequency.. 5190.13 BogoMIPS (lpj=8646613)
    [ 0.000028] pid_max: default: 32768 minimum: 301
    [ 0.000032] ACPI: Core revision 20140926
    [ 0.020437] ACPI: All ACPI Tables successfully acquired
    [ 0.021107] Security Framework initialized
    [ 0.021114] Yama: becoming mindful.
    [ 0.021531] Dentry cache hash table entries: 1048576 (order: 11, 8388608 bytes)
    [ 0.023288] Inode-cache hash table entries: 524288 (order: 10, 4194304 bytes)
    [ 0.024091] Mount-cache hash table entries: 16384 (order: 5, 131072 bytes)
    [ 0.024099] Mountpoint-cache hash table entries: 16384 (order: 5, 131072 bytes)
    [ 0.024297] Initializing cgroup subsys memory
    [ 0.024302] Initializing cgroup subsys devices
    [ 0.024304] Initializing cgroup subsys freezer
    [ 0.024305] Initializing cgroup subsys net_cls
    [ 0.024307] Initializing cgroup subsys blkio
    [ 0.024325] CPU: Physical Processor ID: 0
    [ 0.024326] CPU: Processor Core ID: 0
    [ 0.024329] ENERGY_PERF_BIAS: Set to 'normal', was 'performance'
    [ 0.024329] ENERGY_PERF_BIAS: View and update with x86_energy_perf_policy(8)
    [ 0.025227] mce: CPU supports 7 MCE banks
    [ 0.025238] CPU0: Thermal monitoring enabled (TM1)
    [ 0.025247] Last level iTLB entries: 4KB 1024, 2MB 1024, 4MB 1024
    [ 0.025247] Last level dTLB entries: 4KB 1024, 2MB 1024, 4MB 1024, 1GB 4
    [ 0.025334] Freeing SMP alternatives memory: 20K (ffffffff81a07000 - ffffffff81a0c000)
    [ 0.026009] ftrace: allocating 20921 entries in 82 pages
    [ 0.033432] dmar: Host address width 39
    [ 0.033434] dmar: DRHD base: 0x000000fed90000 flags: 0x0
    [ 0.033442] dmar: IOMMU 0: reg_base_addr fed90000 ver 1:0 cap c0000020660462 ecap f0101a
    [ 0.033443] dmar: DRHD base: 0x000000fed91000 flags: 0x1
    [ 0.033447] dmar: IOMMU 1: reg_base_addr fed91000 ver 1:0 cap d2008c20660462 ecap f010da
    [ 0.033448] dmar: RMRR base: 0x000000db9ee000 end: 0x000000db9fcfff
    [ 0.033449] dmar: RMRR base: 0x000000dd000000 end: 0x000000df1fffff
    [ 0.033571] IOAPIC id 2 under DRHD base 0xfed91000 IOMMU 1
    [ 0.033572] HPET id 0 under DRHD base 0xfed91000
    [ 0.033573] Queued invalidation will be enabled to support x2apic and Intr-remapping.
    [ 0.033573] Your BIOS is broken and requested that x2apic be disabled.
    [ 0.033573] This will slightly decrease performance.
    [ 0.033573] Use 'intremap=no_x2apic_optout' to override BIOS request.
    [ 0.033713] Enabled IRQ remapping in xapic mode
    [ 0.033713] x2apic not enabled, IRQ remapping is in xapic mode
    [ 0.034335] ..TIMER: vector=0x30 apic1=0 pin1=2 apic2=-1 pin2=-1
    [ 0.067359] smpboot: CPU0: Intel(R) Core(TM) i5-4310U CPU @ 2.00GHz (fam: 06, model: 45, stepping: 01)
    [ 0.067366] TSC deadline timer enabled
    [ 0.067387] Performance Events: PEBS fmt2+, 16-deep LBR, Haswell events, full-width counters, Intel PMU driver.
    [ 0.067404] ... version: 3
    [ 0.067405] ... bit width: 48
    [ 0.067406] ... generic registers: 4
    [ 0.067407] ... value mask: 0000ffffffffffff
    [ 0.067407] ... max period: 0000ffffffffffff
    [ 0.067408] ... fixed-purpose events: 3
    [ 0.067409] ... event mask: 000000070000000f
    [ 0.090846] x86: Booting SMP configuration:
    [ 0.090848] .... node #0, CPUs: #1
    [ 0.105028] NMI watchdog: enabled on all CPUs, permanently consumes one hw-PMU counter.
    [ 0.111723] #2 #3
    [ 0.146545] x86: Booted up 1 node, 4 CPUs
    [ 0.146548] smpboot: Total of 4 processors activated (20760.53 BogoMIPS)
    [ 0.149839] devtmpfs: initialized
    [ 0.151742] PM: Registering ACPI NVS region [mem 0xdaeb7000-0xdb802fff] (9748480 bytes)
    [ 0.152488] pinctrl core: initialized pinctrl subsystem
    [ 0.152525] RTC time: 14:27:35, date: 01/29/15
    [ 0.152613] NET: Registered protocol family 16
    [ 0.163220] cpuidle: using governor ladder
    [ 0.176565] cpuidle: using governor menu
    [ 0.176604] ACPI FADT declares the system doesn't support PCIe ASPM, so disable it
    [ 0.176606] ACPI: bus type PCI registered
    [ 0.176607] acpiphp: ACPI Hot Plug PCI Controller Driver version: 0.5
    [ 0.176682] PCI: MMCONFIG for domain 0000 [bus 00-3f] at [mem 0xf8000000-0xfbffffff] (base 0xf8000000)
    [ 0.176684] PCI: MMCONFIG at [mem 0xf8000000-0xfbffffff] reserved in E820
    [ 0.176776] PCI: Using configuration type 1 for base access
    [ 0.176783] dmi type 0xB1 record - unknown flag
    [ 0.190254] ACPI: Added _OSI(Module Device)
    [ 0.190257] ACPI: Added _OSI(Processor Device)
    [ 0.190258] ACPI: Added _OSI(3.0 _SCP Extensions)
    [ 0.190259] ACPI: Added _OSI(Processor Aggregator Device)
    [ 0.195406] ACPI: Executed 16 blocks of module-level executable AML code
    [ 0.527048] ACPI: Dynamic OEM Table Load:
    [ 0.527056] ACPI: SSDT 0xFFFF88021322C800 0003D3 (v02 PmRef Cpu0Cst 00003001 INTL 20120913)
    [ 0.540534] ACPI: Dynamic OEM Table Load:
    [ 0.540541] ACPI: SSDT 0xFFFF8802131E2000 0005AA (v02 PmRef ApIst 00003000 INTL 20120913)
    [ 0.553725] ACPI: Dynamic OEM Table Load:
    [ 0.553731] ACPI: SSDT 0xFFFF8802131DD200 000119 (v02 PmRef ApCst 00003000 INTL 20120913)
    [ 0.607146] ACPI: Interpreter enabled
    [ 0.607157] ACPI Exception: AE_NOT_FOUND, While evaluating Sleep State [\_S1_] (20140926/hwxface-580)
    [ 0.607166] ACPI Exception: AE_NOT_FOUND, While evaluating Sleep State [\_S2_] (20140926/hwxface-580)
    [ 0.607184] ACPI: (supports S0 S3 S4 S5)
    [ 0.607185] ACPI: Using IOAPIC for interrupt routing
    [ 0.607218] PCI: Using host bridge windows from ACPI; if necessary, use "pci=nocrs" and report a bug
    [ 0.608649] ACPI: Power Resource [PG00] (on)
    [ 0.620317] ACPI: Power Resource [PG01] (on)
    [ 0.640702] ACPI: Power Resource [PG02] (on)
    [ 1.401836] ACPI: Power Resource [FN00] (off)
    [ 1.401913] ACPI: Power Resource [FN01] (off)
    [ 1.401986] ACPI: Power Resource [FN02] (off)
    [ 1.402057] ACPI: Power Resource [FN03] (off)
    [ 1.402127] ACPI: Power Resource [FN04] (off)
    [ 1.403037] ACPI: PCI Root Bridge [PCI0] (domain 0000 [bus 00-3e])
    [ 1.403043] acpi PNP0A08:00: _OSC: OS supports [ExtendedConfig ASPM ClockPM Segments MSI]
    [ 1.403622] acpi PNP0A08:00: _OSC: OS now controls [PCIeHotplug PME AER PCIeCapability]
    [ 1.404193] PCI host bridge to bus 0000:00
    [ 1.404195] pci_bus 0000:00: root bus resource [bus 00-3e]
    [ 1.404196] pci_bus 0000:00: root bus resource [io 0x0000-0x0cf7]
    [ 1.404198] pci_bus 0000:00: root bus resource [io 0x0d00-0xffff]
    [ 1.404199] pci_bus 0000:00: root bus resource [mem 0x000a0000-0x000bffff]
    [ 1.404200] pci_bus 0000:00: root bus resource [mem 0xdf200000-0xfeafffff]
    [ 1.404207] pci 0000:00:00.0: [8086:0a04] type 00 class 0x060000
    [ 1.404286] pci 0000:00:02.0: [8086:0a16] type 00 class 0x030000
    [ 1.404296] pci 0000:00:02.0: reg 0x10: [mem 0xf7800000-0xf7bfffff 64bit]
    [ 1.404301] pci 0000:00:02.0: reg 0x18: [mem 0xe0000000-0xefffffff 64bit pref]
    [ 1.404305] pci 0000:00:02.0: reg 0x20: [io 0xf000-0xf03f]
    [ 1.404376] pci 0000:00:03.0: [8086:0a0c] type 00 class 0x040300
    [ 1.404383] pci 0000:00:03.0: reg 0x10: [mem 0xf7e3c000-0xf7e3ffff 64bit]
    [ 1.404461] pci 0000:00:04.0: [8086:0a03] type 00 class 0x118000
    [ 1.404471] pci 0000:00:04.0: reg 0x10: [mem 0xf7e30000-0xf7e37fff 64bit]
    [ 1.404565] pci 0000:00:14.0: [8086:9c31] type 00 class 0x0c0330
    [ 1.404580] pci 0000:00:14.0: reg 0x10: [mem 0xf7e20000-0xf7e2ffff 64bit]
    [ 1.404631] pci 0000:00:14.0: PME# supported from D3hot D3cold
    [ 1.404674] pci 0000:00:14.0: System wakeup disabled by ACPI
    [ 1.404707] pci 0000:00:16.0: [8086:9c3a] type 00 class 0x078000
    [ 1.404725] pci 0000:00:16.0: reg 0x10: [mem 0xf7e46000-0xf7e4601f 64bit]
    [ 1.404787] pci 0000:00:16.0: PME# supported from D0 D3hot D3cold
    [ 1.404856] pci 0000:00:19.0: [8086:15a2] type 00 class 0x020000
    [ 1.404870] pci 0000:00:19.0: reg 0x10: [mem 0xf7e00000-0xf7e1ffff]
    [ 1.404876] pci 0000:00:19.0: reg 0x14: [mem 0xf7e43000-0xf7e43fff]
    [ 1.404882] pci 0000:00:19.0: reg 0x18: [io 0xf080-0xf09f]
    [ 1.404937] pci 0000:00:19.0: PME# supported from D0 D3hot D3cold
    [ 1.445821] pci 0000:00:19.0: System wakeup disabled by ACPI
    [ 1.445873] pci 0000:00:1b.0: [8086:9c20] type 00 class 0x040300
    [ 1.445892] pci 0000:00:1b.0: reg 0x10: [mem 0xf7e38000-0xf7e3bfff 64bit]
    [ 1.445956] pci 0000:00:1b.0: PME# supported from D0 D3hot D3cold
    [ 1.446016] pci 0000:00:1b.0: System wakeup disabled by ACPI
    [ 1.446062] pci 0000:00:1c.0: [8086:9c10] type 01 class 0x060400
    [ 1.446146] pci 0000:00:1c.0: PME# supported from D0 D3hot D3cold
    [ 1.446197] pci 0000:00:1c.0: System wakeup disabled by ACPI
    [ 1.446246] pci 0000:00:1c.3: [8086:9c16] type 01 class 0x060400
    [ 1.446328] pci 0000:00:1c.3: PME# supported from D0 D3hot D3cold
    [ 1.446379] pci 0000:00:1c.3: System wakeup disabled by ACPI
    [ 1.446423] pci 0000:00:1c.4: [8086:9c18] type 01 class 0x060400
    [ 1.446505] pci 0000:00:1c.4: PME# supported from D0 D3hot D3cold
    [ 1.446555] pci 0000:00:1c.4: System wakeup disabled by ACPI
    [ 1.446601] pci 0000:00:1d.0: [8086:9c26] type 00 class 0x0c0320
    [ 1.446621] pci 0000:00:1d.0: reg 0x10: [mem 0xf7e42000-0xf7e423ff]
    [ 1.446711] pci 0000:00:1d.0: PME# supported from D0 D3hot D3cold
    [ 1.446770] pci 0000:00:1d.0: System wakeup disabled by ACPI
    [ 1.446812] pci 0000:00:1f.0: [8086:9c43] type 00 class 0x060100
    [ 1.446999] pci 0000:00:1f.2: [8086:282a] type 00 class 0x010400
    [ 1.447014] pci 0000:00:1f.2: reg 0x10: [io 0xf0d0-0xf0d7]
    [ 1.447021] pci 0000:00:1f.2: reg 0x14: [io 0xf0c0-0xf0c3]
    [ 1.447027] pci 0000:00:1f.2: reg 0x18: [io 0xf0b0-0xf0b7]
    [ 1.447034] pci 0000:00:1f.2: reg 0x1c: [io 0xf0a0-0xf0a3]
    [ 1.447041] pci 0000:00:1f.2: reg 0x20: [io 0xf060-0xf07f]
    [ 1.447048] pci 0000:00:1f.2: reg 0x24: [mem 0xf7e41000-0xf7e417ff]
    [ 1.447087] pci 0000:00:1f.2: PME# supported from D3hot
    [ 1.447164] pci 0000:00:1f.3: [8086:9c22] type 00 class 0x0c0500
    [ 1.447177] pci 0000:00:1f.3: reg 0x10: [mem 0xf7e40000-0xf7e400ff 64bit]
    [ 1.447196] pci 0000:00:1f.3: reg 0x20: [io 0xf040-0xf05f]
    [ 1.449196] pci 0000:01:00.0: [1217:8520] type 00 class 0x080501
    [ 1.449218] pci 0000:01:00.0: reg 0x10: [mem 0xf7d01000-0xf7d01fff]
    [ 1.449231] pci 0000:01:00.0: reg 0x14: [mem 0xf7d00000-0xf7d007ff]
    [ 1.449369] pci 0000:01:00.0: PME# supported from D3hot D3cold
    [ 1.449400] pci 0000:01:00.0: System wakeup disabled by ACPI
    [ 1.457648] pci 0000:00:1c.0: PCI bridge to [bus 01]
    [ 1.457653] pci 0000:00:1c.0: bridge window [mem 0xf7d00000-0xf7dfffff]
    [ 1.458041] pci 0000:02:00.0: [8086:095a] type 00 class 0x028000
    [ 1.458129] pci 0000:02:00.0: reg 0x10: [mem 0xf7c00000-0xf7c01fff 64bit]
    [ 1.458420] pci 0000:02:00.0: PME# supported from D0 D3hot D3cold
    [ 1.458511] pci 0000:02:00.0: System wakeup disabled by ACPI
    [ 1.462692] pci 0000:00:1c.3: PCI bridge to [bus 02]
    [ 1.462697] pci 0000:00:1c.3: bridge window [mem 0xf7c00000-0xf7cfffff]
    [ 1.462787] pci 0000:00:1c.4: PCI bridge to [bus 03]
    [ 1.464747] acpi PNP0A08:00: Disabling ASPM (FADT indicates it is unsupported)
    [ 1.547152] ACPI: PCI Interrupt Link [LNKA] (IRQs 3 4 5 6 10 *11 12 14 15)
    [ 1.547202] ACPI: PCI Interrupt Link [LNKB] (IRQs 3 4 5 6 10 11 12 14 15) *0, disabled.
    [ 1.547250] ACPI: PCI Interrupt Link [LNKC] (IRQs 3 4 5 6 10 11 12 14 15) *0, disabled.
    [ 1.547296] ACPI: PCI Interrupt Link [LNKD] (IRQs 3 4 5 6 *10 11 12 14 15)
    [ 1.547342] ACPI: PCI Interrupt Link [LNKE] (IRQs 3 4 *5 6 10 11 12 14 15)
    [ 1.547388] ACPI: PCI Interrupt Link [LNKF] (IRQs 3 *4 5 6 10 11 12 14 15)
    [ 1.547434] ACPI: PCI Interrupt Link [LNKG] (IRQs *3 4 5 6 10 11 12 14 15)
    [ 1.547480] ACPI: PCI Interrupt Link [LNKH] (IRQs 3 4 5 6 10 11 12 14 15) *0, disabled.
    [ 1.613841] ACPI: Enabled 3 GPEs in block 00 to 7F
    [ 1.613905] ACPI : EC: GPE = 0x27, I/O: command/status = 0x934, data = 0x930
    [ 1.614013] vgaarb: setting as boot device: PCI:0000:00:02.0
    [ 1.614016] vgaarb: device added: PCI:0000:00:02.0,decodes=io+mem,owns=io+mem,locks=none
    [ 1.614019] vgaarb: loaded
    [ 1.614020] vgaarb: bridge control possible 0000:00:02.0
    [ 1.614099] PCI: Using ACPI for IRQ routing
    [ 1.615308] PCI: pci_cache_line_size set to 64 bytes
    [ 1.615344] e820: reserve RAM buffer [mem 0x00091400-0x0009ffff]
    [ 1.615345] e820: reserve RAM buffer [mem 0xc8c6d000-0xcbffffff]
    [ 1.615346] e820: reserve RAM buffer [mem 0x21ee00000-0x21fffffff]
    [ 1.615428] NetLabel: Initializing
    [ 1.615429] NetLabel: domain hash size = 128
    [ 1.615429] NetLabel: protocols = UNLABELED CIPSOv4
    [ 1.615438] NetLabel: unlabeled traffic allowed by default
    [ 1.615467] hpet0: at MMIO 0xfed00000, IRQs 2, 8, 0, 0, 0, 0, 0, 0
    [ 1.615471] hpet0: 8 comparators, 64-bit 14.318180 MHz counter
    [ 1.617497] Switched to clocksource hpet
    [ 1.621576] pnp: PnP ACPI init
    [ 1.621752] system 00:00: [io 0x0680-0x069f] has been reserved
    [ 1.621755] system 00:00: [io 0xffff] has been reserved
    [ 1.621756] system 00:00: [io 0xffff] has been reserved
    [ 1.621758] system 00:00: [io 0xffff] has been reserved
    [ 1.621759] system 00:00: [io 0x1800-0x18fe] could not be reserved
    [ 1.621761] system 00:00: [io 0x164e-0x164f] has been reserved
    [ 1.621763] system 00:00: Plug and Play ACPI device, IDs PNP0c02 (active)
    [ 1.621806] pnp 00:01: Plug and Play ACPI device, IDs PNP0b00 (active)
    [ 1.621837] system 00:02: [io 0x1854-0x1857] has been reserved
    [ 1.621839] system 00:02: Plug and Play ACPI device, IDs INT3f0d PNP0c02 (active)
    [ 1.621908] pnp 00:03: Plug and Play ACPI device, IDs PNP0303 (active)
    [ 1.621927] pnp 00:04: Plug and Play ACPI device, IDs DLL062c PNP0f13 (active)
    [ 1.774372] pnp 00:05: Plug and Play ACPI device, IDs PNP0401 (disabled)
    [ 1.774526] system 00:06: [mem 0xfed1c000-0xfed1ffff] has been reserved
    [ 1.774529] system 00:06: [mem 0xfed10000-0xfed17fff] has been reserved
    [ 1.774530] system 00:06: [mem 0xfed18000-0xfed18fff] has been reserved
    [ 1.774532] system 00:06: [mem 0xfed19000-0xfed19fff] has been reserved
    [ 1.774534] system 00:06: [mem 0xf8000000-0xfbffffff] has been reserved
    [ 1.774536] system 00:06: [mem 0xfed20000-0xfed3ffff] has been reserved
    [ 1.774538] system 00:06: [mem 0xfed90000-0xfed93fff] could not be reserved
    [ 1.774539] system 00:06: [mem 0xfed45000-0xfed8ffff] has been reserved
    [ 1.774541] system 00:06: [mem 0xff000000-0xffffffff] has been reserved
    [ 1.774543] system 00:06: [mem 0xfee00000-0xfeefffff] could not be reserved
    [ 1.774545] system 00:06: [mem 0xf7fe0000-0xf7feffff] has been reserved
    [ 1.774547] system 00:06: [mem 0xf7ff0000-0xf7ffffff] has been reserved
    [ 1.774549] system 00:06: Plug and Play ACPI device, IDs PNP0c02 (active)
    [ 1.774927] system 00:07: Plug and Play ACPI device, IDs PNP0c02 (active)
    [ 2.001167] pnp: PnP ACPI: found 8 devices
    [ 2.007535] pci 0000:00:1c.0: PCI bridge to [bus 01]
    [ 2.007540] pci 0000:00:1c.0: bridge window [mem 0xf7d00000-0xf7dfffff]
    [ 2.007546] pci 0000:00:1c.3: PCI bridge to [bus 02]
    [ 2.007549] pci 0000:00:1c.3: bridge window [mem 0xf7c00000-0xf7cfffff]
    [ 2.007555] pci 0000:00:1c.4: PCI bridge to [bus 03]
    [ 2.007564] pci_bus 0000:00: resource 4 [io 0x0000-0x0cf7]
    [ 2.007566] pci_bus 0000:00: resource 5 [io 0x0d00-0xffff]
    [ 2.007567] pci_bus 0000:00: resource 6 [mem 0x000a0000-0x000bffff]
    [ 2.007568] pci_bus 0000:00: resource 7 [mem 0xdf200000-0xfeafffff]
    [ 2.007570] pci_bus 0000:01: resource 1 [mem 0xf7d00000-0xf7dfffff]
    [ 2.007571] pci_bus 0000:02: resource 1 [mem 0xf7c00000-0xf7cfffff]
    [ 2.007594] NET: Registered protocol family 2
    [ 2.007754] TCP established hash table entries: 65536 (order: 7, 524288 bytes)
    [ 2.007894] TCP bind hash table entries: 65536 (order: 8, 1048576 bytes)
    [ 2.008082] TCP: Hash tables configured (established 65536 bind 65536)
    [ 2.008100] TCP: reno registered
    [ 2.008108] UDP hash table entries: 4096 (order: 5, 131072 bytes)
    [ 2.008140] UDP-Lite hash table entries: 4096 (order: 5, 131072 bytes)
    [ 2.008195] NET: Registered protocol family 1
    [ 2.008208] pci 0000:00:02.0: Video device with shadowed ROM
    [ 2.024532] PCI: CLS 64 bytes, default 64
    [ 2.024577] Unpacking initramfs...
    [ 2.341540] Freeing initrd memory: 22696K (ffff88003539c000 - ffff8800369c6000)
    [ 2.341564] PCI-DMA: Using software bounce buffering for IO (SWIOTLB)
    [ 2.341567] software IO TLB [mem 0xc4c6d000-0xc8c6d000] (64MB) mapped at [ffff8800c4c6d000-ffff8800c8c6cfff]
    [ 2.341712] RAPL PMU detected, hw unit 2^-14 Joules, API unit is 2^-32 Joules, 4 fixed counters 655360 ms ovfl timer
    [ 2.341757] microcode: CPU0 sig=0x40651, pf=0x40, revision=0x1c
    [ 2.341762] microcode: CPU1 sig=0x40651, pf=0x40, revision=0x1c
    [ 2.341766] microcode: CPU2 sig=0x40651, pf=0x40, revision=0x1c
    [ 2.341771] microcode: CPU3 sig=0x40651, pf=0x40, revision=0x1c
    [ 2.341822] microcode: Microcode Update Driver: v2.00 <[email protected]>, Peter Oruba
    [ 2.341843] Scanning for low memory corruption every 60 seconds
    [ 2.342043] futex hash table entries: 1024 (order: 4, 65536 bytes)
    [ 2.342061] Initialise system trusted keyring
    [ 2.342314] HugeTLB registered 2 MB page size, pre-allocated 0 pages
    [ 2.343277] zpool: loaded
    [ 2.343280] zbud: loaded
    [ 2.343434] VFS: Disk quotas dquot_6.5.2
    [ 2.343457] Dquot-cache hash table entries: 512 (order 0, 4096 bytes)
    [ 2.343557] msgmni has been set to 15200
    [ 2.343599] Key type big_key registered
    [ 2.343749] Block layer SCSI generic (bsg) driver version 0.4 loaded (major 252)
    [ 2.343779] io scheduler noop registered
    [ 2.343781] io scheduler deadline registered
    [ 2.343802] io scheduler cfq registered (default)
    [ 2.343967] pcieport 0000:00:1c.0: irq 42 for MSI/MSI-X
    [ 2.344096] pcieport 0000:00:1c.3: irq 43 for MSI/MSI-X
    [ 2.344214] pcieport 0000:00:1c.4: irq 44 for MSI/MSI-X
    [ 2.344282] pcieport 0000:00:1c.0: Signaling PME through PCIe PME interrupt
    [ 2.344283] pci 0000:01:00.0: Signaling PME through PCIe PME interrupt
    [ 2.344286] pcie_pme 0000:00:1c.0:pcie01: service driver pcie_pme loaded
    [ 2.344296] pcieport 0000:00:1c.3: Signaling PME through PCIe PME interrupt
    [ 2.344297] pci 0000:02:00.0: Signaling PME through PCIe PME interrupt
    [ 2.344300] pcie_pme 0000:00:1c.3:pcie01: service driver pcie_pme loaded
    [ 2.344310] pcieport 0000:00:1c.4: Signaling PME through PCIe PME interrupt
    [ 2.344312] pcie_pme 0000:00:1c.4:pcie01: service driver pcie_pme loaded
    [ 2.344325] pci_hotplug: PCI Hot Plug PCI Core version: 0.5
    [ 2.344337] pciehp: PCI Express Hot Plug Controller Driver version: 0.4
    [ 2.344362] vesafb: mode is 1920x1080x32, linelength=7680, pages=0
    [ 2.344363] vesafb: scrolling: redraw
    [ 2.344364] vesafb: Truecolor: size=8:8:8:8, shift=24:16:8:0
    [ 2.344382] vesafb: framebuffer at 0xe0000000, mapped to 0xffffc90004f80000, using 8128k, total 8128k
    [ 2.492136] Console: switching to colour frame buffer device 240x67
    [ 2.639261] fb0: VESA VGA frame buffer device
    [ 2.639278] intel_idle: MWAIT substates: 0x11142120
    [ 2.639279] intel_idle: v0.4 model 0x45
    [ 2.639280] intel_idle: lapic_timer_reliable_states 0xffffffff
    [ 2.639471] GHES: HEST is not enabled!
    [ 2.639520] Serial: 8250/16550 driver, 4 ports, IRQ sharing disabled
    [ 2.639854] Linux agpgart interface v0.103
    [ 2.639890] rtc_cmos 00:01: RTC can wake from S4
    [ 2.640003] rtc_cmos 00:01: rtc core: registered rtc_cmos as rtc0
    [ 2.640027] rtc_cmos 00:01: alarms up to one month, y3k, 242 bytes nvram, hpet irqs
    [ 2.640037] Intel P-state driver initializing.
    [ 2.640149] ledtrig-cpu: registered to indicate activity on CPUs
    [ 2.640415] TCP: cubic registered
    [ 2.640635] NET: Registered protocol family 10
    [ 2.641104] NET: Registered protocol family 17
    [ 2.641809] Loading compiled-in X.509 certificates
    [ 2.641841] registered taskstats version 1
    [ 2.642839] Magic number: 15:558:486
    [ 2.642991] rtc_cmos 00:01: setting system clock to 2015-01-29 14:27:38 UTC (1422541658)
    [ 2.643157] PM: Hibernation image not present or could not be loaded.
    [ 2.645133] Freeing unused kernel memory: 1160K (ffffffff818e5000 - ffffffff81a07000)
    [ 2.645137] Write protecting the kernel read-only data: 8192k
    [ 2.649298] Freeing unused kernel memory: 652K (ffff88000155d000 - ffff880001600000)
    [ 2.651088] Freeing unused kernel memory: 328K (ffff8800017ae000 - ffff880001800000)
    [ 2.656604] random: systemd-tmpfile urandom read with 6 bits of entropy available
    [ 2.656683] systemd-tmpfiles[60]: /dev/mapper created successfully.
    [ 2.656691] systemd-tmpfiles[60]: /dev/fuse created successfully.
    [ 2.656696] systemd-tmpfiles[60]: /dev/mapper/control created successfully.
    [ 2.656700] systemd-tmpfiles[60]: /dev/loop-control created successfully.
    [ 2.656704] systemd-tmpfiles[60]: /dev/cuse created successfully.
    [ 2.656707] systemd-tmpfiles[60]: /dev/btrfs-control created successfully.
    [ 2.657455] systemd-udevd[61]: starting version 218
    [ 2.657462] systemd-udevd[61]: hwdb.bin does not exist, please run udevadm hwdb --update
    [ 2.657510] systemd-udevd[61]: Load module index
    [ 2.657562] systemd-udevd[61]: Created link configuration context.
    [ 2.657568] systemd-udevd[61]: timestamp of '/usr/lib/udev/rules.d' changed
    [ 2.657608] systemd-udevd[61]: Reading rules file: /usr/lib/udev/rules.d/10-dm.rules
    [ 2.657685] systemd-udevd[61]: Reading rules file: /usr/lib/udev/rules.d/11-dm-initramfs.rules
    [ 2.657695] systemd-udevd[61]: Reading rules file: /usr/lib/udev/rules.d/11-dm-lvm.rules
    [ 2.657733] systemd-udevd[61]: Reading rules file: /usr/lib/udev/rules.d/13-dm-disk.rules
    [ 2.657763] systemd-udevd[61]: Reading rules file: /usr/lib/udev/rules.d/50-udev-default.rules
    [ 2.657871] systemd-udevd[61]: Reading rules file: /usr/lib/udev/rules.d/60-persistent-storage.rules
    [ 2.657981] systemd-udevd[61]: Reading rules file: /usr/lib/udev/rules.d/64-btrfs.rules
    [ 2.657999] systemd-udevd[61]: Reading rules file: /usr/lib/udev/rules.d/69-dm-lvm-metad.rules
    [ 2.658057] systemd-udevd[61]: Reading rules file: /usr/lib/udev/rules.d/80-drivers.rules
    [ 2.658080] systemd-udevd[61]: Reading rules file: /usr/lib/udev/rules.d/95-dm-notify.rules
    [ 2.658089] systemd-udevd[61]: rules contain 24576 bytes tokens (2048 * 12 bytes), 4834 bytes strings
    [ 2.658091] systemd-udevd[61]: 641 strings (8077 bytes), 378 de-duplicated (3507 bytes), 264 trie nodes used
    [ 2.658106] systemd-udevd[61]: chmod '/dev/fuse' 0666
    [ 2.658188] systemd-udevd[61]: Unload module index
    [ 2.658212] systemd-udevd[61]: Unloaded link configuration context.
    [ 2.658262] systemd-udevd[62]: set children_max to 16
    [ 2.660408] systemd-udevd[62]: seq 678 queued, 'add' 'module'
    [ 2.660490] systemd-udevd[62]: seq 678 forked new worker [67]
    [ 2.660575] systemd-udevd[67]: seq 678 running
    [ 2.660618] systemd-udevd[67]: no db file to read /run/udev/data/+module:raid6_pq: No such file or directory
    [ 2.660644] systemd-udevd[67]: passed -1 bytes to netlink monitor 0x7f4fb498c310
    [ 2.660651] systemd-udevd[67]: seq 678 processed with 0
    [ 2.714860] raid6: sse2x1 9342 MB/s
    [ 2.771561] raid6: sse2x2 11848 MB/s
    [ 2.828260] raid6: sse2x4 13887 MB/s
    [ 2.884943] raid6: avx2x1 18356 MB/s
    [ 2.941655] raid6: avx2x2 21230 MB/s
    [ 2.998344] raid6: avx2x4 24583 MB/s
    [ 2.998345] raid6: using algorithm avx2x4 (24583 MB/s)
    [ 2.998346] raid6: using avx2x2 recovery algorithm
    [ 2.998547] xor: automatically using best checksumming function:
    [ 2.998570] systemd-udevd[62]: seq 679 queued, 'add' 'module'
    [ 2.998603] systemd-udevd[62]: passed 124 bytes to netlink monitor 0x7f4fb497f0d0
    [ 2.998639] systemd-udevd[67]: seq 679 running
    [ 2.998659] systemd-udevd[67]: no db file to read /run/udev/data/+module:xor: No such file or directory
    [ 2.998678] systemd-udevd[67]: passed -1 bytes to netlink monitor 0x7f4fb498c310
    [ 2.998684] systemd-udevd[67]: seq 679 processed with 0
    [ 3.031698] avx : 25444.800 MB/sec
    [ 3.034144] systemd-udevd[62]: Validate module index
    [ 3.034177] systemd-udevd[62]: Check if link configuration needs reloading.
    [ 3.034204] systemd-udevd[62]: seq 680 queued, 'add' 'module'
    [ 3.034228] systemd-udevd[62]: passed 126 bytes to netlink monitor 0x7f4fb497f0d0
    [ 3.034249] systemd-udevd[67]: seq 680 running
    [ 3.034275] systemd-udevd[67]: no db file to read /run/udev/data/+module:btrfs: No such file or directory
    [ 3.034299] systemd-udevd[67]: passed -1 bytes to netlink monitor 0x7f4fb498c310
    [ 3.034308] systemd-udevd[67]: seq 680 processed with 0
    [ 3.034899] systemd-udevd[62]: seq 681 queued, 'add' 'module'
    [ 3.034927] systemd-udevd[62]: passed 133 bytes to netlink monitor 0x7f4fb497f0d0
    [ 3.034945] systemd-udevd[67]: seq 681 running
    [ 3.034964] systemd-udevd[67]: no db file to read /run/udev/data/+module:crc32c_intel: No such file or directory
    [ 3.034979] systemd-udevd[67]: passed -1 bytes to netlink monitor 0x7f4fb498c310
    [ 3.034986] systemd-udevd[67]: seq 681 processed with 0
    [ 3.035051] systemd-udevd[62]: seq 682 queued, 'add' 'module'
    [ 3.035070] systemd-udevd[62]: passed 135 bytes to netlink monitor 0x7f4fb497f0d0
    [ 3.035087] systemd-udevd[67]: seq 682 running
    [ 3.035101] systemd-udevd[67]: no db file to read /run/udev/data/+module:crc32c_generic: No such file or directory
    [ 3.035113] systemd-udevd[67]: passed -1 bytes to netlink monitor 0x7f4fb498c310
    [ 3.035118] systemd-udevd[67]: seq 682 processed with 0
    [ 3.035756] systemd-udevd[62]: seq 683 queued, 'add' 'slab'
    [ 3.035776] systemd-udevd[62]: passed 135 bytes to netlink monitor 0x7f4fb497f0d0
    [ 3.035790] systemd-udevd[67]: seq 683 running
    [ 3.035795] systemd-udevd[62]: seq 684 queued, 'add' 'slab'
    [ 3.035810] systemd-udevd[67]: no db file to read /run/udev/data/+slab:btrfs_inode: No such file or directory
    [ 3.035830] systemd-udevd[67]: passed -1 bytes to netlink monitor 0x7f4fb498c310
    [ 3.035834] systemd-udevd[67]: seq 683 processed with 0
    [ 3.035903] systemd-udevd[62]: seq 684 forked new worker [75]
    [ 3.035934] systemd-udevd[62]: seq 685 queued, 'add' 'slab'
    [ 3.035948] systemd-udevd[62]: passed 135 bytes to netlink monitor 0x7f4fb497f0d0
    [ 3.035961] systemd-udevd[67]: seq 685 running
    [ 3.035968] systemd-udevd[62]: seq 686 queued, 'add' 'slab'
    [ 3.035981] systemd-udevd[67]: no db file to read /run/udev/data/+slab::at-0000144: No such file or directory
    [ 3.035981] systemd-udevd[75]: seq 684 running
    [ 3.035999] systemd-udevd[67]: passed -1 bytes to netlink monitor 0x7f4fb498c310
    [ 3.036004] systemd-udevd[67]: seq 685 processed with 0
    [ 3.036010] systemd-udevd[75]: no db file to read /run/udev/data/+slab::at-0000176: No such file or directory
    [ 3.036027] systemd-udevd[75]: passed -1 bytes to netlink monitor 0x7f4fb49879e0
    [ 3.036031] systemd-udevd[75]: seq 684 processed with 0
    [ 3.036065] systemd-udevd[62]: seq 686 forked new worker [76]
    [ 3.036107] systemd-udevd[62]: seq 687 queued, 'add' 'slab'
    [ 3.036128] systemd-udevd[62]: passed 135 bytes to netlink monitor 0x7f4fb497f0d0
    [ 3.036146] systemd-udevd[62]: seq 688 queued, 'add' 'slab'
    [ 3.036165] systemd-udevd[76]: seq 686 running
    [ 3.036166] systemd-udevd[62]: passed 135 bytes to netlink monitor 0x7f4fb497f0d0
    [ 3.036180] systemd-udevd[75]: seq 688 running
    [ 3.036182] systemd-udevd[62]: seq 689 queued, 'add' 'slab'
    [ 3.036199] systemd-udevd[75]: no db file to read /run/udev/data/+slab::at-0000088: No such file or directory
    [ 3.036206] systemd-udevd[76]: no db file to read /run/udev/data/+slab::at-0000064: No such file or directory
    [ 3.036212] systemd-udevd[75]: passed -1 bytes to netlink monitor 0x7f4fb49879e0
    [ 3.036215] systemd-udevd[75]: seq 688 processed with 0
    [ 3.036227] systemd-udevd[76]: passed -1 bytes to netlink monitor 0x7f4fb49883b0
    [ 3.036231] systemd-udevd[76]: seq 686 processed with 0
    [ 3.036257] Btrfs loaded
    [ 3.036289] systemd-udevd[62]: seq 689 forked new worker [77]
    [ 3.036329] systemd-udevd[62]: seq 690 queued, 'add' 'slab'
    [ 3.036351] systemd-udevd[62]: passed 135 bytes to netlink monitor 0x7f4fb497f0d0
    [ 3.036370] systemd-udevd[62]: seq 691 queued, 'add' 'slab'
    [ 3.036378] systemd-udevd[77]: seq 689 running
    [ 3.036390] systemd-udevd[62]: passed 135 bytes to netlink monitor 0x7f4fb497f0d0
    [ 3.036407] systemd-udevd[62]: seq 692 queued, 'add' 'slab'
    [ 3.036413] systemd-udevd[77]: no db file to read /run/udev/data/+slab::at-0000280: No such file or directory
    [ 3.036434] systemd-udevd[77]: passed -1 bytes to netlink monitor 0x7f4fb498a250
    [ 3.036439] systemd-udevd[77]: seq 689 processed with 0
    [ 3.036457] systemd-udevd[76]: seq 691 running
    [ 3.036474] systemd-udevd[76]: no db file to read /run/udev/data/+slab::at-0000304: No such file or directory
    [ 3.036493] systemd-udevd[76]: passed -1 bytes to netlink monitor 0x7f4fb49883b0
    [ 3.036498] systemd-udevd[76]: seq 691 processed with 0
    [ 3.036513] systemd-udevd[62]: seq 692 forked new worker [78]
    [ 3.036548] systemd-udevd[62]: seq 693 queued, 'add' 'slab'
    [ 3.036563] systemd-udevd[62]: passed 135 bytes to netlink monitor 0x7f4fb497f0d0
    [ 3.036576] systemd-udevd[76]: seq 693 running
    [ 3.036579] systemd-udevd[62]: seq 694 queued, 'add' 'slab'
    [ 3.036596] systemd-udevd[76]: no db file to read /run/udev/data/+slab::at-0000096: No such file or directory
    [ 3.036597] systemd-udevd[62]: passed 135 bytes to netlink monitor 0x7f4fb497f0d0
    [ 3.036615] systemd-udevd[76]: passed -1 bytes to netlink monitor 0x7f4fb49883b0
    [ 3.036616] systemd-udevd[62]: seq 695 queued, 'add' 'slab'
    [ 3.036619] systemd-udevd[76]: seq 693 processed with 0
    [ 3.036637] systemd-udevd[77]: seq 694 running
    [ 3.036649] systemd-udevd[78]: seq 692 running
    [ 3.036655] systemd-udevd[77]: no db file to read /run/udev/data/+slab::at-0000040: No such file or directory
    [ 3.036672] systemd-udevd[77]: passed -1 bytes to netlink monitor 0x7f4fb498a250
    [ 3.036676] systemd-udevd[77]: seq 694 processed with 0
    [ 3.036678] systemd-udevd[78]: no db file to read /run/udev/data/+slab::at-0000160: No such file or directory
    [ 3.036694] systemd-udevd[78]: passed -1 bytes to netlink monitor 0x7f4fb498f600
    [ 3.036698] systemd-udevd[78]: seq 692 processed with 0
    [ 3.036721] systemd-udevd[62]: seq 695 forked new worker [80]
    [ 3.036773] systemd-udevd[62]: seq 696 queued, 'add' 'misc'
    [ 3.036801] systemd-udevd[80]: seq 695 running
    [ 3.036826] systemd-udevd[80]: no db file to read /run/udev/data/+slab::at-0000080: No such file or directory
    [ 3.036832] systemd-udevd[62]: passed 192 bytes to netlink monitor 0x7f4fb497f0d0
    [ 3.036843] systemd-udevd[80]: passed -1 bytes to netlink monitor 0x7f4fb49913d0
    [ 3.036848] systemd-udevd[80]: seq 695 processed with 0
    [ 3.036859] systemd-udevd[76]: seq 696 running
    [ 3.036904] systemd-udevd[76]: no db file to read /run/udev/data/c10:234: No such file or directory
    [ 3.036916] systemd-udevd[76]: handling device node '/dev/btrfs-control', devnum=c10:234, mode=0600, uid=0, gid=0
    [ 3.036922] systemd-udevd[76]: preserve permissions /dev/btrfs-control, 020600, uid=0, gid=0
    [ 3.036930] systemd-udevd[76]: creating symlink '/dev/char/10:234' to '../btrfs-control'
    [ 3.036959] systemd-udevd[76]: created empty file '/run/udev/data/c10:234' for '/devices/virtual/misc/btrfs-control'
    [ 3.036987] systemd-udevd[76]: passed -1 bytes to netlink monitor 0x7f4fb49883b0
    [ 3.036992] systemd-udevd[76]: seq 696 processed with 0
    [ 3.037009] systemd-udevd[67]: seq 687 running
    [ 3.037027] systemd-udevd[67]: no db file to read /run/udev/data/+slab::at-0000152: No such file or directory
    [ 3.037044] systemd-udevd[67]: passed -1 bytes to netlink monitor 0x7f4fb498c310
    [ 3.037048] systemd-udevd[67]: seq 687 processed with 0
    [ 3.037063] systemd-udevd[75]: seq 690 running
    [ 3.037079] systemd-udevd[75]: no db file to read /run/udev/data/+slab::at-0000424: No such file or directory
    [ 3.037093] systemd-udevd[75]: passed -1 bytes to netlink monitor 0x7f4fb49879e0
    [ 3.037097] systemd-udevd[75]: seq 690 processed with 0
    [ 3.037372] udevadm[79]: calling: trigger
    [ 3.037397] udevadm[79]: device 0x7fbf103cd230 has devpath '/module/vt'
    [ 3.037403] udevadm[79]: device 0x7fbf103cd230 has devpath '/module/xor'
    [ 3.037408] udevadm[79]: device 0x7fbf103cd230 has devpath '/module/8250'
    [ 3.037412] udevadm[79]: device 0x7fbf103cd230 has devpath '/module/tcp_cubic'
    [ 3.037417] udevadm[79]: device 0x7fbf103cd230 has devpath '/module/acpi'
    [ 3.037421] udevadm[79]: device 0x7fbf103cd230 has devpath '/module/ipv6'
    [ 3.037425] udevadm[79]: device 0x7fbf103cd230 has devpath '/module/cpuidle'
    [ 3.037428] udevadm[79]: device 0x7fbf103cd230 has devpath '/module/rcutree'
    [ 3.037432] udevadm[79]: device 0x7fbf103cd230 has devpath '/module/block'
    [ 3.037436] udevadm[79]: device 0x7fbf103cd230 has devpath '/module/btrfs'
    [ 3.037440] udevadm[79]: device 0x7fbf103cd230 has devpath '/module/sysrq'
    [ 3.037444] udevadm[79]: device 0x7fbf103cd230 has devpath '/module/zswap'
    [ 3.037448] udevadm[79]: device 0x7fbf103cd230 has devpath '/module/crc32c_generic'
    [ 3.037453] udevadm[79]: device 0x7fbf103cd500 has devpath '/module/firmware_class'
    [ 3.037457] udevadm[79]: device 0x7fbf103cd500 has devpath '/module/workqueue'
    [ 3.037461] udevadm[79]: device 0x7fbf103cd500 has devpath '/module/crc32c_intel'
    [ 3.037465] udevadm[79]: device 0x7fbf103cd500 has devpath '/module/spurious'
    [ 3.037469] udevadm[79]: device 0x7fbf103cd500 has devpath '/module/raid6_pq'
    [ 3.037473] udevadm[79]: device 0x7fbf103cd500 has devpath '/module/configfs'
    [ 3.037477] udevadm[79]: device 0x7fbf103cd500 has devpath '/module/netpoll'
    [ 3.037481] udevadm[79]: device 0x7fbf103cd500 has devpath '/module/pci_slot'
    [ 3.037486] udevadm[79]: device 0x7fbf103cd500 has devpath '/module/kernel'
    [ 3.037490] udevadm[79]: device 0x7fbf103cd500 has devpath '/module/acpiphp'
    [ 3.037494] udevadm[79]: device 0x7fbf103cd500 has devpath '/module/pciehp'
    [ 3.037498] udevadm[79]: device 0x7fbf103cd500 has devpath '/module/printk'
    [ 3.037502] udevadm[79]: device 0x7fbf103cd500 has devpath '/module/pstore'
    [ 3.037507] udevadm[79]: device 0x7fbf103cd500 has devpath '/module/dynamic_debug'
    [ 3.037511] udevadm[79]: device 0x7fbf103cd500 has devpath '/module/xz_dec'
    [ 3.037515] udevadm[79]: device 0x7fbf103cd500 has devpath '/module/pcie_aspm'
    [ 3.037522] udevadm[79]: device 0x7fbf103cd500 has devpath '/module/rcupdate'
    [ 3.037526] udevadm[79]: device 0x7fbf103cd500 has devpath '/module/intel_idle'
    [ 3.037530] udevadm[79]: device 0x7fbf103cd500 has devpath '/module/keyboard'
    [ 3.037534] udevadm[79]: device 0x7fbf103cd500 has devpath '/module/pci_hotplug'
    [ 3.037548] udevadm[79]: device 0x7fbf103cd500 has devpath '/bus/cpu'
    [ 3.037552] udevadm[79]: device 0x7fbf103cd500 has devpath '/bus/pci'
    [ 3.037556] udevadm[79]: device 0x7fbf103cd500 has devpath '/bus/pnp'
    [ 3.037559] udevadm[79]: device 0x7fbf103cd500 has devpath '/bus/spi'
    [ 3.037563] udevadm[79]: device 0x7fbf103cd500 has devpath '/bus/xen'
    [ 3.037567] udevadm[79]: device 0x7fbf103cd500 has devpath '/bus/acpi'
    [ 3.037571] udevadm[79]: device 0x7fbf103cd500 has devpath '/bus/node'
    [ 3.037575] udevadm[79]: device 0x7fbf103cd500 has devpath '/bus/clocksource'
    [ 3.037579] udevadm[79]: device 0x7fbf103cd500 has devpath '/bus/machinecheck'
    [ 3.037583] udevadm[79]: device 0x7fbf103cd500 has devpath '/bus/event_source'
    [ 3.037587] udevadm[79]: device 0x7fbf103cd500 has devpath '/bus/workqueue'
    [ 3.037591] udevadm[79]: device 0x7fbf103cd500 has devpath '/bus/container'
    [ 3.037595] udevadm[79]: device 0x7fbf103cd500 has devpath '/bus/memory'
    [ 3.037599] udevadm[79]: device 0x7fbf103cd500 has devpath '/bus/pci_express'
    [ 3.037603] udevadm[79]: device 0x7fbf103cd500 has devpath '/bus/platform'
    [ 3.037607] udevadm[79]: device 0x7fbf103cd500 has devpath '/bus/clockevents'
    [ 3.037611] udevadm[79]: device 0x7fbf103cd500 has devpath '/bus/xen-backend'
    [ 3.037628] udevadm[79]: device 0x7fbf103cd500 has devpath '/bus/pci/drivers/xen-platform-pci'
    [ 3.037633] udevadm[79]: device 0x7fbf103cd500 has devpath '/bus/pci/drivers/pcieport'
    [ 3.037638] udevadm[79]: device 0x7fbf103cd500 has devpath '/bus/pci/drivers/ioapic'
    [ 3.037642] udevadm[79]: device 0x7fbf103cd500 has devpath '/bus/pci/drivers/serial'
    [ 3.037653] udevadm[79]: device 0x7fbf103cd500 has devpath '/bus/pnp/drivers/rtc_cmos'
    [ 3.037658] udevadm[79]: device 0x7fbf103cd500 has devpath '/bus/pnp/drivers/serial'
    [ 3.037662] udevadm[79]: device 0x7fbf103cd500 has devpath '/bus/pnp/drivers/system'
    [ 3.037675] udevadm[79]: device 0x7fbf103cd500 has devpath '/bus/acpi/drivers/ec'
    [ 3.037680] udevadm[79]: device 0x7fbf103cd500 has devpath '/bus/acpi/drivers/hpet'
    [ 3.037685] udevadm[79]: device 0x7fbf103cd500 has devpath '/bus/acpi/drivers/intel_smart_connect'
    [ 3.037691] udevadm[79]: device 0x7fbf103cd500 has devpath '/bus/acpi/drivers/hardware_error_device'
    [ 3.037716] udevadm[79]: device 0x7fbf103cd500 has devpath '/bus/pci_express/drivers/aer'
    [ 3.037721] udevadm[79]: device 0x7fbf103cd500 has devpath '/bus/pci_express/drivers/pcie_pme'
    [ 3.037726] udevadm[79]: device 0x7fbf103cd500 has devpath '/bus/pci_express/drivers/pciehp'
    [ 3.037735] udevadm[79]: device 0x7fbf103cd500 has devpath '/bus/platform/drivers/alarmtimer'
    [ 3.037739] udevadm[79]: device 0x7fbf103cd500 has devpath '/bus/platform/drivers/efi-framebuffer'
    [ 3.037744] udevadm[79]: device 0x7fbf103cd500 has devpath '/bus/platform/drivers/vesa-framebuffer'
    [ 3.037748] udevadm[79]: device 0x7fbf103cd500 has devpath '/bus/platform/drivers/serial8250'
    [ 3.037753] udevadm[79]: device 0x7fbf103cd500 has devpath '/bus/platform/drivers/syscon'
    [ 3.037760] udevadm[79]: device 0x7fbf103cd500 has devpath '/bus/platform/drivers/clk-lpt'
    [ 3.037842] systemd-udevd[62]: seq 697 queued, 'add' 'bus'
    [ 3.037860] systemd-udevd[62]: passed 119 bytes to netlink monitor 0x7f4fb497f0d0
    [ 3.037890] systemd-udevd[67]: seq 697 running
    [ 3.037891] systemd-udevd[62]: seq 698 queued, 'add' 'drivers'
    [ 3.037906] systemd-udevd[62]: seq 699 queued, 'add' 'drivers'
    [ 3.037909] systemd-udevd[67]: no db file to read /run/udev/data/+bus:acpi: No such file or directory
    [ 3.037921] systemd-udevd[62]: seq 700 queued, 'add' 'drivers'
    [ 3.037923] systemd-udevd[67]: passed -1 bytes to netlink monitor 0x7f4fb498c310
    [ 3.037925] systemd-udevd[67]: seq 697 processed with 0
    [ 3.037941] systemd-udevd[62]: seq 701 queued, 'add' 'drivers'
    [ 3.037963] systemd-udevd[62]: passed 134 bytes to netlink monitor 0x7f4fb497f0d0
    [ 3.037985] systemd-udevd[62]: passed 153 bytes to netlink monitor 0x7f4fb497f0d0
    [ 3.037988] systemd-udevd[67]: seq 698 running
    [ 3.037999] systemd-udevd[62]: passed 136 bytes to netlink monitor 0x7f4fb497f0d0
    [ 3.038001] systemd-udevd[67]: no db file to read /run/udev/data/+drivers:ec: No such file or directory
    [ 3.038011] systemd-udevd[62]: passed 151 bytes to netlink monitor 0x7f4fb497f0d0
    [ 3.038013] systemd-udevd[67]: passed -1 bytes to netlink monitor 0x7f4fb498c310
    [ 3.038015] systemd-udevd[67]: seq 698 processed with 0
    [ 3.038031] systemd-udevd[62]: seq 702 queued, 'add' 'bus'
    [ 3.038053] systemd-udevd[62]: passed 126 bytes to netlink monitor 0x7f4fb497f0d0
    [ 3.038076] systemd-udevd[67]: seq 702 running
    [ 3.038079] systemd-udevd[62]: seq 703 queued, 'add' 'bus'
    [ 3.038088] systemd-udevd[67]: no db file to read /run/udev/data/+bus:clockevents: No such file or directory
    [ 3.038094] systemd-udevd[62]: passed 126 bytes to netlink monitor 0x7f4fb497f0d0
    [ 3.038102] systemd-udevd[67]: passed -1 bytes to netlink monitor 0x7f4fb498c310
    [ 3.038106] systemd-udevd[67]: seq 702 processed with 0
    [ 3.038111] systemd-udevd[62]: seq 704 queued, 'add' 'bus'
    [ 3.038113] systemd-udevd[78]: seq 703 running
    [ 3.038126] systemd-udevd[62]: passed 124 bytes to netlink monitor 0x7f4fb497f0d0
    [ 3.038134] systemd-udevd[78]: no db file to read /run/udev/data/+bus:clocksource: No such file or directory
    [ 3.038143] systemd-udevd[80]: seq 704 running
    [ 3.038145] systemd-udevd[62]: seq 705 queued, 'add' 'bus'
    [ 3.038152] systemd-udevd[78]: passed -1 bytes to netlink monitor 0x7f4fb498f600
    [ 3.038156] systemd-udevd[62]: passed 118 bytes to netlink monitor 0x7f4fb497f0d0
    [ 3.038158] systemd-udevd[78]: seq 703 processed with 0
    [ 3.038163] systemd-udevd[80]: no db file to read /run/udev/data/+bus:container: No such file or directory
    [ 3.038175] systemd-udevd[62]: seq 706 queued, 'add' 'bus'
    [ 3.038177] systemd-udevd[80]: passed -1 bytes to netlink monitor 0x7f4fb49913d0
    [ 3.038179] systemd-udevd[80]: seq 704 processed with 0
    [ 3.038188] systemd-udevd[62]: passed 127 bytes to netlink monitor 0x7f4fb497f0d0
    [ 3.038192] systemd-udevd[67]: seq 705 running
    [ 3.038201] systemd-udevd[78]: seq 706 running
    [ 3.038206] systemd-udevd[62]: seq 707 queued, 'add' 'bus'
    [ 3.038209] systemd-udevd[67]: no db file to read /run/udev/data/+bus:cpu: No such file or directory
    [ 3.038218] systemd-udevd[62]: passed 127 bytes to netlink monitor 0x7f4fb497f0d0
    [ 3.038224] systemd-udevd[78]: no db file to read /run/udev/data/+bus:event_source: No such file or directory
    [ 3.038225] systemd-udevd[67]: passed -1 bytes to netlink monitor 0x7f4fb498c310
    [ 3.038228] systemd-udevd[67]: seq 705 processed with 0
    [ 3.038234] systemd-udevd[62]: seq 708 queued, 'add' 'bus'
    [ 3.038243] systemd-udevd[80]: seq 707 running
    [ 3.038243] systemd-udevd[78]: passed -1 bytes to netlink monitor 0x7f4fb498f600
    [ 3.038246] systemd-udevd[78]: seq 706 processed with 0
    [ 3.038254] systemd-udevd[76]: seq 700 running
    [ 3.038261] systemd-udevd[80]: no db file to read /run/udev/data/+bus:machinecheck: No such file or directory
    [ 3.038272] systemd-udevd[80]: passed -1 bytes to netlink monitor 0x7f4fb49913d0
    [ 3.038275] systemd-udevd[80]: seq 707 processed with 0
    [ 3.038276] systemd-udevd[76]: no db file to read /run/udev/data/+drivers:hpet: No such file or directory
    [ 3.038306] systemd-udevd[76]: passed -1 bytes to netlink monitor 0x7f4fb49883b0
    [ 3.038310] systemd-udevd[76]: seq 700 processed with 0
    [ 3.038325] systemd-udevd[75]: seq 699 running
    [ 3.038343] systemd-udevd[75]: no db file to read /run/udev/data/+drivers:hardware_error_device: No such file or directory
    [ 3.038360] systemd-udevd[75]: passed -1 bytes to netlink monitor 0x7f4fb49879e0
    [ 3.038364] systemd-udevd[75]: seq 699 processed with 0
    [ 3.038405] systemd-udevd[77]: seq 701 running
    [ 3.038419] systemd-udevd[77]: no db file to read /run/udev/data/+drivers:intel_smart_connect: No such file or directory
    [ 3.038429] systemd-udevd[77]: passed -1 bytes to netlink monitor 0x7f4fb498a250
    [ 3.038432] systemd-udevd[77]: seq 701 processed with 0
    [ 3.038531] systemd-udevd[62]: seq 708 forked new worker [81]
    [ 3.038591] systemd-udevd[62]: seq 709 queued, 'add' 'bus'
    [ 3.038612] systemd-udevd[62]: passed 119 bytes to netlink monitor 0x7f4fb497f0d0
    [ 3.038623] systemd-udevd[81]: seq 708 running
    [ 3.038627] systemd-udevd[67]: seq 709 running
    [ 3.038631] systemd-udevd[62]: seq 710 queued, 'add' 'bus'
    [ 3.038640] systemd-udevd[62]: passed 118 bytes to netlink monitor 0x7f4fb497f0d0
    [ 3.038648] systemd-udevd[67]: no db file to read /run/udev/data/+bus:node: No such file or directory
    [ 3.038653] systemd-udevd[75]: seq 710 running
    [ 3.038655] systemd-udevd[81]: no db file to read /run/udev/data/+bus:memory: No such file or directory
    [ 3.038657] systemd-udevd[62]: seq 711 queued, 'add' 'drivers'
    [ 3.038666] systemd-udevd[67]: passed -1 bytes to netlink monitor 0x7f4fb498c310
    [ 3.038671] systemd-udevd[62]: seq 712 queued, 'add' 'drivers'
    [ 3.038671] systemd-udevd[67]: seq 709 processed with 0
    [ 3.038676] systemd-udevd[81]: passed -1 bytes to netlink monitor 0x7f4fb49945b0
    [ 3.038678] systemd-udevd[75]: no db file to read /run/udev/data/+bus:pci: No such file or directory
    [ 3.038682] systemd-udevd[81]: seq 708 processed with 0
    [ 3.038693] systemd-udevd[62]: seq 713 queued, 'add' 'drivers'
    [ 3.038695] systemd-udevd[75]: passed -1 bytes to netlink monitor 0x7f4fb49879e0
    [ 3.038700] systemd-udevd[75]: seq 710 processed with 0
    [ 3.038710] systemd-udevd[62]: seq 714 queued, 'add' 'drivers'
    [ 3.038721] systemd-udevd[62]: passed 137 bytes to netlink monitor 0x7f4fb497f0d0
    [ 3.038732] systemd-udevd[62]: passed 139 bytes to netlink monitor 0x7f4fb497f0d0
    [ 3.038734] systemd-udevd[67]: seq 711 running
    [ 3.038753] systemd-udevd[76]: seq 713 running
    [ 3.038753] systemd-udevd[67]: no db file to read /run/udev/data/+drivers:ioapic: No such file or directory
    [ 3.038779] systemd-udevd[67]: passed -1 bytes to netlink monitor 0x7f4fb498c310
    [ 3.038782] systemd-udevd[76]: no db file to read /run/udev/data/+drivers:serial: No such file or directory
    [ 3.038784] systemd-udevd[67]: seq 711 processed with 0
    [ 3.038797] systemd-udevd[75]: seq 712 running
    [ 3.038799] systemd-udevd[76]: passed -1 bytes to netlink monitor 0x7f4fb49883b0
    [ 3.038803] systemd-udevd[76]: seq 713 processed with 0
    [ 3.038810] systemd-udevd[62]: passed 137 bytes to netlink monitor 0x7f4fb497f0d0
    [ 3.038815] systemd-udevd[75]: no db file to read /run/udev/data/+drivers:pcieport: No such file or directory
    [ 3.038823] systemd-udevd[62]: passed 147 bytes to netlink monitor 0x7f4fb497f0d0
    [ 3.038841] systemd-udevd[75]: passed -1 bytes to netlink monitor 0x7f4fb49879e0
    [ 3.038845] systemd-udevd[75]: seq 712 processed with 0
    [ 3.038849] systemd-udevd[77]: seq 714 running
    [ 3.038856] systemd-udevd[62]: seq 715 queued, 'add' 'bus'
    [ 3.038864] systemd-udevd[77]: no db file to read /run/udev/data/+drivers:xen-platform-pci: No such file or directory
    [ 3.038871] systemd-udevd[62]: passed 126 bytes to netlink monitor 0x7f4fb497f0d0
    [ 3.038876] systemd-udevd[77]: passed -1 bytes to netlink monitor 0x7f4fb498a250
    [ 3.038878] systemd-udevd[77]: seq 714 processed with 0
    [ 3.038891] systemd-udevd[62]: seq 716 queued, 'add' 'drivers'
    [ 3.038915] systemd-udevd[62]: seq 717 queued, 'add' 'drivers'
    [ 3.038928] systemd-udevd[62]: seq 718 queued, 'add' 'drivers'
    [ 3.038941] systemd-udevd[62]: seq 719 queued, 'add' 'bus'
    [ 3.038953] systemd-udevd[62]: passed 123 bytes to netlink monitor 0x7f4fb497f0d0
    [ 3.038976] systemd-udevd[75]: seq 719 running
    [ 3.038977] systemd-udevd[62]: seq 720 queued, 'add' 'drivers'
    [ 3.038990] systemd-udevd[75]: no db file to read /run/udev/data/+bus:platform: No such file or directory
    [ 3.038991] systemd-udevd[62]: seq 721 queued, 'add' 'drivers'
    [ 3.039001] systemd-udevd[75]: passed -1 bytes to netlink monitor 0x7f4fb49879e0
    [ 3.039004] systemd-udevd[75]: seq 719 processed with 0
    [ 3.039005] systemd-udevd[62]: seq 722 queued, 'add' 'drivers'
    [ 3.039034] systemd-udevd[62]: seq 723 queued, 'add' 'drivers'
    [ 3.039046] systemd-udevd[62]: passed 146 bytes to netlink monitor 0x7f4fb497f0d0
    [ 3.039070] systemd-udevd[75]: seq 720 running
    [ 3.039078] systemd-udevd[76]: seq 721 running
    [ 3.039081] systemd-udevd[75]: no db file to read /run/udev/data/+drivers:alarmtimer: No such file or directory
    [ 3.039092] systemd-udevd[75]: passed -1 bytes to netlink monitor 0x7f4fb49879e0
    [ 3.039094] systemd-udevd[75]: seq 720 processed with 0
    [ 3.039101] systemd-udevd[76]: no db file to read /run/udev/data/+drivers:clk-lpt: No such file or directory
    [ 3.039128] systemd-udevd[76]: passed -1 bytes to netlink monitor 0x7f4fb49883b0
    [ 3.039133] systemd-udevd[76]: seq 721 processed with 0
    [ 3.039146] systemd-udevd[67]: seq 715 running
    [ 3.039162] systemd-udevd[67]: no db file to read /run/udev/data/+bus:pci_express: No such file or directory
    [ 3.039177] systemd-udevd[67]: passed -1 bytes to netlink monitor 0x7f4fb498c310
    [ 3.039181] systemd-udevd[67]: seq 715 processed with 0
    [ 3.039188] systemd-udevd[62]: passed 143 bytes to netlink monitor 0x7f4fb497f0d0
    [ 3.039200] systemd-udevd[62]: passed 151 bytes to netlink monitor 0x7f4fb497f0d0
    [ 3.039221] systemd-udevd[62]: passed 146 bytes to netlink monitor 0x7f4fb497f0d0
    [ 3.039224] systemd-udevd[77]: seq 722 running
    [ 3.039235] systemd-udevd[78]: seq 723 running
    [ 3.039244] systemd-udevd[77]: no db file to read /run/udev/data/+drivers:efi-framebuffer: No such file or directory
    [ 3.039244] systemd-udevd[62]: seq 724 queued, 'add' 'drivers'
    [ 3.039255] systemd-udevd[78]: no db file to read /run/udev/data/+drivers:serial8250: No such file or directory
    [ 3.039257] systemd-udevd[62]: passed 142 bytes to netlink monitor 0x7f4fb497f0d0
    [ 3.039263] systemd-udevd[77]: passed -1 bytes to netlink monitor 0x7f4fb498a250
    [ 3.039267] systemd-udevd[77]: seq 722 processed with 0
    [ 3.039269] systemd-udevd[62]: passed 147 bytes to netlink monitor 0x7f4fb497f0d0
    [ 3.039273] systemd-udevd[78]: passed -1 bytes to netlink monitor 0x7f4fb498f600
    [ 3.039277] systemd-udevd[78]: seq 723 processed with 0
    [ 3.039284] systemd-udevd[75]: seq 717 running
    [ 3.039288] systemd-udevd[76]: seq 718 running
    [ 3.039298] systemd-udevd[75]: no db file to read /run/udev/data/+drivers:pcie_pme: No such file or directory
    [ 3.039306] systemd-udevd[76]: no db file to read /run/udev/data/+drivers:pciehp: No such file or directory
    [ 3.039309] sys

    Guys, I think I've found the strange thing.
    First, in the recovery shell, when I type "lvm lvscan", it prints:
    WARNING: lvmetad is running but disabled. Restart lvmetad before enabling it!
    and then it says that all four my logical volumes root,boot,home and var are inactive.
    So I tried to set them up manually, with "lvm vgchange -a y", and guess what happened: I was able to boot!
    I still haven't managed to understand the real causes of this problem, but basically it seems that I have the same problem explained here: https://bbs.archlinux.org/viewtopic.php?id=184340.
    The only difference is that there the OP says to have solved the problem with an upgrade to Linux 3.15.7, while it appeared to me with the upgrade to 3.18.3, and as I said it doesn't go away neither with a downgrade nor with another upgrade to version 3.18.4
    Last edited by rdm (2015-01-29 21:55:44)

  • [Solved] Unable to boot after install

    Forgive me for the lack of code tags, having to write this on my phone.
    I am unable to boot after installation. I receive an error wich has the incorrect UDID string. It doesn't even exist. I will update with error after posting so I can give grub config generation error first
    When I run:
    grub-mkconfig -o /boot/grub/grub.cfg
    I get this:
    Found Linux image : /boot/vmlinuz-linux
    Found initd image: /boot/initramfs-linux.img
    Warning: failed to connect to lvmetad: no such file or directory. falling back to internal scanning.
    No volume groups found
    [ 279.601712] SQUASHFS error: can't find a SQUASHFS superblock on sda3
    [ 279.604502] EXT4-fs (sda3):unable to read superblock
    [ 279.607266] EXT4-fs (sda3):unable to read superblock
    [ 279.609928] EXT4-fs (sda3):unable to read superblock
    Found Windows 7 (loader) on /dev/sda1
    Done
    Sda3 is an extended volume
    Edit: I just deleted the old .cfg and recreated a new one by re running the above command, uncounted and rebooted and it booted into CLI. 3rd time a charm after all. Marking this one solved
    Last edited by Kirito (2013-05-15 07:55:31)

    Oh, looking at your setup, it would seem that your system is likely still configured to boot to /dev/sdd (the windows drive).
    As a user with numerous drives, you should be aware that using /dev/sdXY to identify your disks is a bad idea.  There is no gaurantee that Arch will be /dev/sde every time, nor that windows will be /dev/sdd.  You should use either filesystem labels (LABEL= or /dev/disk/by-label) or UUIDs (UUID= or /dev/disk/by-uuid).  Though if you are using GPT, there is also the option of the PARTLABEL as well (which are the labels you create within the partitioner).

Maybe you are looking for

  • 3500 songs in iTunes with exlamation points - iTunes can't locate files but they are there!

    Hi, Since a few weeks, 3500 of my 10000 iTunes songs have exclamation points. When I try to play a song, I get an error message stating that iTunes can't find the song. If I search for it, it's on my Mac. So the files are on my hard drive, except tha

  • App Not Launching, Problem Reported, Dev (F84Games) Not Responding, Refund?

    Hi all, I really need help with the 'Railroad Madness' app purchased for my son's ipad (from F84Games in Los Angeles). When he tried to play/launch it the game just crashes immediately after the splash screen. Reporting the problem to Apple (through

  • N9 - Can not swipe down till the end of Launcher P...

    Hi,, I have already posted this problem in another discussion but could not find any solution. I have tried to mention the exact in this topics. Events Screen is Ok there are lots of notifications from Facebook, Mails and I can to the end of the Mess

  • Problem with .war files

              I have created a .war file with my servlets in           /WEB-INF/classes directory and all other classes jared into a single jar file           in /WEB-INF/lib,but on calling the servlet only those classes that the servlet           uses d

  • CRM ABAP Development aproach

    Hi Experts, Can any body tell me the difference in the approachs of development between CRM ABAP and ABAP. or only the CRM ABAP development approach. jaffer vali shaik