[FAIL] in boot sequence related to alsactl / Intel audio hardware

Hey,
I get the following [FAIL] during the boot sequence: http://codepad.org/gzKZaEyF
Although the sound seems to be working afterwards. Any ideas ?

I too have occassionally encountered alsactl issues upon booting after an upgrade. It seems on occassion the asound.state file gets corrupted during an update of some kind.
The solution is simple. Re-create your asound.state file.
# alsamixer
Re-set your default volume levels.
# alsactl -f /var/lib/alsa/asound.state store
Settings have now been saved.
# alsactl -f /var/lib/alsa/asound.state restore
Tests to ensure the file is valid and can be loaded.
Providing you do not get any errors here, all should now be well!
Cheers.

Similar Messages

Mac Book fails to boot properly after EFI Firmware 27 update

hi
I have a strange boot issue having (tried) to install EFI 2.7 update.
When I restart the laptop, it 'chimes', displays a grey screen ... then chimes, displays a grey screen , ... for ever
I hit the bower (off) button for 5 secs or thereabouts, and restart ... same thing
I do this 4 times and finally it reboots.
But the EFI update still appears as needing to be installed (software update tells me it is not installed). Update history shows however that it IS installed.
I can go through this process any number of times ... I now have Software Update history showing quite a few installs opf the EFI 2.7 update.
If I just do a restart WITHOUT installing, I also go through the same fail to restart / fail to start / ... / eventually restart sequence.
So it seems now that the laptop will only start after 4 failed restarts and finally it starts ...
After starting it all appears to be perfectly fine.
Nothing strange in the console logs that I can see. The failed reboots don't seem to register in the console logs - I suspect that the failure to restart is pretty early on in the boot sequence, well before it tries to load any semblance of the OSX kernel. It is almost as if it is trying to boot from someplace other than the disk ... until eventually it gives up and tries the disk. (I have tried booting with and without network cable - no difference) I don't know enough about mac bootup sequences to know if there is some config/setting that is screwed up causing this odd behaviour. I sirt of feel it must be setup/software related, but could be wrong.
Odd.
Any ideas?
- chris

I have a MC721LL/A early 2011 15.4" MacBook Pro i7. After I installed this firmware update my Mail would not load saying the version I was trying to start was not compatible with the OSX version (not sure whether this was an OSX update issue which I think I did at the same time). But the biggest problem I have is that I cannot boot my machine. It boots to the Apple logo and then emits 3 beeps repeatedly. I am on vacation in Osaka, Japan and the Apple Store here told me after running some analytics that the logic board is not seeing the RAM. After reseating the RAM multiple times (both original and replacement DIMMS), it still won't boot. The Genius Bar guy said very nicely that it is out of warranty and needs a new logic board, costing over $500 and taking a week at the factory. He recommended spending the money on a new MacBook instead. Since my machine is 15 months old, I am not very happy about this. The machine was absolutely fine before the firmware upgrade. I will wait till I get back to the US and get a second opinion from my local Apple Store. I can't accept that a 15 month old MacBook Pro very lightly used can develop such a catastrophic failure.

New Windows server 2003 Hyper-V guest fails to boot

Hello,
I'm currently doing some virtualization experiments on my new server hardware. The host hardware is:
IBM x3650 M4
x2 Xeon E5-2609
32GB RAM
x2 480 GB SSDs
Server OS: Windows server 2012
I'd like to test some legacy app virtualization. I've configured a VM and have installed Windows server 2003. The install is done via DVD. The issue at hand is that after the initial installation, the server fails to boot. The VM goes into a reboot loop
and so far the only error logging I'm able to find is in the hosts event log.
Log Name: Microsoft-Windows-Hyper-V-Worker-Admin
Source: Microsoft-Windows-Hyper-V-Worker
Date: 7/8/2014 2:14:48 PM
Event ID: 18560
Task Category: None
Level: Critical
Keywords:
User: NT VIRTUAL MACHINE\A0D20FA4-B27B-4B58-85C1-87D74B0ADD2D
Computer: CCSTS1.cnet2k.cornerstonecredit.net
Description:
'LegacyTS' was reset because an unrecoverable error occurred on a virtual processor that caused a triple fault. If the problem persists, contact Product Support. (Virtual machine ID A0D20FA4-B27B-4B58-85C1-87D74B0ADD2D)
Event Xml:
<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
<System>
<Provider Name="Microsoft-Windows-Hyper-V-Worker" Guid="{51DDFA29-D5C8-4803-BE4B-2ECB715570FE}" />
<EventID>18560</EventID>
<Version>0</Version>
<Level>1</Level>
<Task>0</Task>
<Opcode>0</Opcode>
<Keywords>0x8000000000000000</Keywords>
<TimeCreated SystemTime="2014-07-08T21:14:48.544007000Z" />
<EventRecordID>159</EventRecordID>
<Correlation />
<Execution ProcessID="1512" ThreadID="3536" />
<Channel>Microsoft-Windows-Hyper-V-Worker-Admin</Channel>
<Computer>CCSTS1.cnet2k.cornerstonecredit.net</Computer>
<Security UserID="S-1-5-83-1-2698121124-1264104059-3615998341-769460811" />
</System>
<UserData>
<VmlEventLog xmlns:auto-ns2="http://schemas.microsoft.com/win/2004/08/events" xmlns="http://www.microsoft.com/Windows/Virtualization/Events">
<VmName>LegacyTS</VmName>
<VmId>A0D20FA4-B27B-4B58-85C1-87D74B0ADD2D</VmId>
<Rax>0x0</Rax>
<Rbx>0x0</Rbx>
<Rcx>0x0</Rcx>
<Rdx>0x0</Rdx>
<Rsp>0x804de00c</Rsp>
<Rbp>0x0</Rbp>
<Rsi>0x0</Rsi>
<Rdi>0x0</Rdi>
<R8>0x0</R8>
<R9>0x0</R9>
<R10>0x0</R10>
<R11>0x0</R11>
<R12>0x0</R12>
<R13>0x0</R13>
<R14>0x0</R14>
<R15>0x0</R15>
<Rip>0x80547c7c</Rip>
<Rflags>0x10046</Rflags>
<FpControlStatus>7F030000000000000000000000000000</FpControlStatus>
<XmmControlStatus>0000000000000000801F0000FFFF0000</XmmControlStatus>
<Cr0>0x8001003d</Cr0>
<Cr2>0x804ddffc</Cr2>
<Cr3>0xa02000</Cr3>
<Cr4>0x20</Cr4>
<Cr8>0xf</Cr8>
<Xfem>0x1</Xfem>
<Dr0>0x0</Dr0>
<Dr1>0x0</Dr1>
<Dr2>0x0</Dr2>
<Dr3>0x0</Dr3>
<Dr6>0xffff0ff0</Dr6>
<Dr7>0x400</Dr7>
<Es>0000000000000000FFFFFFFF2300F3C0</Es>
<Cs>0000000000000000FFFFFFFF08009BC0</Cs>
<Ss>0000000000000000FFFFFFFF100093C0</Ss>
<Ds>0000000000000000FFFFFFFF2300F3C0</Ds>
<Fs>00F0DFFF00000000FF1F0000300093C0</Fs>
<Gs>0000000000000000FFFFFFFF00000000</Gs>
<Ldtr>00000000000000000000000000000000</Ldtr>
<Tr>90685580000000006800000050008B00</Tr>
<Idtr>000000000000FF0700F4038000000000</Idtr>
<Gdtr>000000000000FF0300F0038000000000</Gdtr>
<Tsc>0x148e4294</Tsc>
<ApicBase>0xfee00900</ApicBase>
<SysenterCs>0x0</SysenterCs>
<SysenterEip>0x0</SysenterEip>
<SysenterEsp>0x0</SysenterEsp>
</VmlEventLog>
</UserData>
</Event>
My VM config
<?xml version="1.0" encoding="UTF-16" standalone="yes"?>
<configuration>
<_24984ed0-bdad-4b90-82b2-5d59f874e91e_>
<ChannelInstanceGuid type="string">{E4E9CD0E-4BBF-4C1B-B655-715781690655}</ChannelInstanceGuid>
</_24984ed0-bdad-4b90-82b2-5d59f874e91e_>
<_7d80d3db-61ee-4879-8879-5609f1100ad0_>
<address type="string">5353,00000000,00</address>
<version type="integer">1</version>
</_7d80d3db-61ee-4879-8879-5609f1100ad0_>
<_83f8638b-8dca-4152-9eda-2ca8b33039b4_>
<controller0>
<drive0>
<pathname type="string">E:\Hyper-V\VHD\LegacyTS.vhdx</pathname>
<pool_id type="string"></pool_id>
<type type="string">VHD</type>
</drive0>
<drive1>
<pathname type="string"></pathname>
<type type="string">NONE</type>
</drive1>
</controller0>
<controller1>
<drive0>
<pathname type="string">SCSI\CDROM&VEN_IBM_SATA&PROD_DEVICE_81Y3681\4&1864BF9E&0&010000</pathname>
<pool_id type="string"></pool_id>
<type type="string">ISO</type>
</drive0>
<drive1>
<pathname type="string"></pathname>
<type type="string">NONE</type>
</drive1>
</controller1>
<version type="integer">5</version>
</_83f8638b-8dca-4152-9eda-2ca8b33039b4_>
<_8e3a359f-559a-4b6a-98a9-1690a6100ed7_>
<port0>
<connection type="string"></connection>
</port0>
<port1>
<connection type="string"></connection>
</port1>
<version type="integer">2</version>
</_8e3a359f-559a-4b6a-98a9-1690a6100ed7_>
<_8f0d2762-0b00-4e04-af4f-19010527cb93_>
<controller0>
<drive0>
<pathname type="string"></pathname>
<type type="string">VFD</type>
</drive0>
</controller0>
<version type="integer">1</version>
</_8f0d2762-0b00-4e04-af4f-19010527cb93_>
<_a80e9c62-750a-4a6b-9548-d46677e806be_>
<ChannelInstanceGuid type="string">{23c9c636-93de-4aec-9bef-220766177a24}</ChannelInstanceGuid>
<Connection>
<AltPortName type="string">Dynamic Ethernet Switch Port</AltPortName>
<AltSwitchName type="string">Intel(R) I350 Gigabit Network Connection - Virtual Switch</AltSwitchName>
<AuthorizationScope type="string"></AuthorizationScope>
<ChimneyOffloadWeight type="integer">0</ChimneyOffloadWeight>
<Feature_C885BFD1-ABB7-418F-8163-9F379C9F7166>
<DisplayName type="string"></DisplayName>
<Flags type="integer">0</Flags>
<Setting_97274751-A1EC-4DC2-941D-B7F9A1AED814>
<Data type="bytes">AAIAAGQAAAAAAAAAAQAAAAAAAAA=
</Data>
<Version type="integer">256</Version>
</Setting_97274751-A1EC-4DC2-941D-B7F9A1AED814>
<Settings>
<Id type="string">97274751-A1EC-4DC2-941D-B7F9A1AED814</Id>
</Settings>
</Feature_C885BFD1-ABB7-418F-8163-9F379C9F7166>
<Features>
<Id type="string">C885BFD1-ABB7-418F-8163-9F379C9F7166</Id>
</Features>
<HostResources>
<HostResource type="string">8758EB1A-9687-41FC-9319-AE867D46BA5C</HostResource>
</HostResources>
<PoolId type="string"></PoolId>
<PreventIPSpoofing type="bool">False</PreventIPSpoofing>
<TestReplicaPoolId type="string"></TestReplicaPoolId>
<TestReplicaSwitchName type="string"></TestReplicaSwitchName>
</Connection>
<FriendlyName type="string">Network Adapter</FriendlyName>
<IsConnected type="bool">True</IsConnected>
<MacAddress type="string">00-15-5D-01-18-02</MacAddress>
<MacAddressIsStatic type="bool">False</MacAddressIsStatic>
<PortName type="string">E7F02418-A1EB-4FF9-84F8-BF461B2D00C6</PortName>
<SwitchName type="string">8758EB1A-9687-41FC-9319-AE867D46BA5C</SwitchName>
<VpciInstanceGuid type="string">{E9444985-111B-404A-82FE-48608A397676}</VpciInstanceGuid>
</_a80e9c62-750a-4a6b-9548-d46677e806be_>
<_ac6b8dc1-3257-4a70-b1b2-a9c9215659ad_>
<base_board>
<serial_number type="string">9595-3600-2199-6834-7686-3927-30</serial_number>
</base_board>
<bios_guid type="string">{B54BE7B5-05A4-4C4A-A2BD-D63272C7CCCD}</bios_guid>
<bios_serial_number type="string">9595-3600-2199-6834-7686-3927-30</bios_serial_number>
<boot>
<device0 type="string">Optical</device0>
<device1 type="string">HardDrive</device1>
<device2 type="string">Network</device2>
<device3 type="string">Floppy</device3>
</boot>
<chassis>
<asset_tag type="string">8437-8592-0329-9603-9215-1886-12</asset_tag>
<serial_number type="string">9595-3600-2199-6834-7686-3927-30</serial_number>
</chassis>
<num_lock type="bool">False</num_lock>
<version type="integer">2</version>
</_ac6b8dc1-3257-4a70-b1b2-a9c9215659ad_>
<_db8b9818-b4bb-4725-b99d-b4612716b6b4_>
<version type="integer">0</version>
</_db8b9818-b4bb-4725-b99d-b4612716b6b4_>
<global_settings>
<devices>
<allow_reduced_fc_redundancy type="bool">False</allow_reduced_fc_redundancy>
<generation_id type="string">883d11122d9b7b2c521be0c045ef3760</generation_id>
<storage_allow_full_scsi_command_set type="bool">False</storage_allow_full_scsi_command_set>
</devices>
<disk_merge_pending type="bool">False</disk_merge_pending>
<metrics>
<devicetype>
<deviceinstance>
<guid type="string">B637F346-6A0E-4DEC-AF52-BD70CB80A21D</guid>
<metric>
<enabled type="bool">False</enabled>
<lastcomputedtime type="integer">0</lastcomputedtime>
<peaktime type="integer">0</peaktime>
<poolid type="string"></poolid>
<resourcetypeid type="string">B637F347-6A0E-4DEC-AF52-BD70CB80A21D</resourcetypeid>
<starttime type="integer">0</starttime>
<typecode type="string">3F6F1051-C8FC-47EF-9821-C07240848748;0</typecode>
<value type="integer">0</value>
</metric>
</deviceinstance>
<guid type="string">B637F346-6A0E-4DEC-AF52-BD70CB80A21D</guid>
</devicetype>
<devicetype>
<deviceinstance>
<guid type="string">4764334D-E001-4176-82EE-5594EC9B530E</guid>
<metric>
<enabled type="bool">False</enabled>
<lastcomputedtime type="integer">0</lastcomputedtime>
<peaktime type="integer">0</peaktime>
<poolid type="string"></poolid>
<resourcetypeid type="string">4764334E-E001-4176-82EE-5594EC9B530E</resourcetypeid>
<starttime type="integer">0</starttime>
<typecode type="string">394DCE66-458F-4895-AE56-41D7C9602A49</typecode>
<value type="integer">0</value>
</metric>
<metric>
<enabled type="bool">False</enabled>
<lastcomputedtime type="integer">0</lastcomputedtime>
<peaktime type="integer">0</peaktime>
<poolid type="string"></poolid>
<resourcetypeid type="string">4764334E-E001-4176-82EE-5594EC9B530E</resourcetypeid>
<starttime type="integer">0</starttime>
<typecode type="string">FF85EA46-9933-4436-BE5D-C96827399966</typecode>
<value type="integer">0</value>
</metric>
<metric>
<enabled type="bool">False</enabled>
<lastcomputedtime type="integer">0</lastcomputedtime>
<peaktime type="integer">0</peaktime>
<poolid type="string"></poolid>
<resourcetypeid type="string">4764334E-E001-4176-82EE-5594EC9B530E</resourcetypeid>
<starttime type="integer">0</starttime>
<typecode type="string">04BDF59E-580D-4441-8828-FFFE44472D2D</typecode>
<value type="integer">0</value>
</metric>
</deviceinstance>
<guid type="string">4764334D-E001-4176-82EE-5594EC9B530E</guid>
</devicetype>
<devicetype>
<deviceinstance>
<guid type="string">83F8638B-8DCA-4152-9EDA-2CA8B33039B4</guid>
<metric>
<enabled type="bool">False</enabled>
<lastcomputedtime type="integer">0</lastcomputedtime>
<peaktime type="integer">0</peaktime>
<poolid type="string"></poolid>
<resourcetypeid type="string">70BB60D2-A9D3-46AA-B654-3DE53004B4F8</resourcetypeid>
<starttime type="integer">0</starttime>
<typecode type="string">AD29978B-AAB6-44AE-81CD-0609BF929F18;0\0\L</typecode>
<value type="integer">0</value>
</metric>
</deviceinstance>
<guid type="string">83F8638B-8DCA-4152-9EDA-2CA8B33039B4</guid>
</devicetype>
</metrics>
<owner>
<sid type="string">S-1-5-21-1940488291-1951097212-1584025624-1392</sid>
</owner>
<power>
<host_shutdown>
<action type="integer">1</action>
</host_shutdown>
<host_startup>
<action type="integer">1</action>
</host_startup>
</power>
<snapshots>
<list>
<size type="integer">0</size>
</list>
</snapshots>
<unexpected_termination>
<action type="integer">1</action>
</unexpected_termination>
<vhd_path_acled type="bool">True</vhd_path_acled>
</global_settings>
<manifest>
<size type="integer">11</size>
<vdev001>
<device type="string">58f75a6d-d949-4320-99e1-a2a2576d581c</device>
<flags type="integer">1</flags>
<instance type="string">58F75A6D-D949-4320-99E1-A2A2576D581C</instance>
<name type="string">Microsoft Synthetic Mouse</name>
</vdev001>
<vdev002>
<device type="string">197f74e3-b84b-46de-8ae6-82f1cd181cdc</device>
<flags type="integer">1</flags>
<instance type="string">197F74E3-B84B-46DE-8AE6-82F1CD181CDC</instance>
<name type="string">Microsoft Synthetic Keyboard</name>
</vdev002>
<vdev003>
<device type="string">f3cf6965-e8d3-44a9-9b7d-a04245ea7525</device>
<flags type="integer">1</flags>
<instance type="string">F3CF6965-E8D3-44A9-9B7D-A04245EA7525</instance>
<name type="string">Microsoft Synthetic Video</name>
</vdev003>
<vdev004>
<device type="string">84eaae65-2f2e-45f5-9bb5-0e857dc8eb47</device>
<flags type="integer">1</flags>
<instance type="string">84EAAE65-2F2E-45F5-9BB5-0E857DC8EB47</instance>
<name type="string">Microsoft Heartbeat Component</name>
</vdev004>
<vdev005>
<device type="string">2a34b1c2-fd73-4043-8a5b-dd2159bc743f</device>
<flags type="integer">1</flags>
<instance type="string">2A34B1C2-FD73-4043-8A5B-DD2159BC743F</instance>
<name type="string">Microsoft Key-Value Pair Exchange Component</name>
</vdev005>
<vdev006>
<device type="string">9f8233ac-be49-4c79-8ee3-e7e1985b2077</device>
<flags type="integer">1</flags>
<instance type="string">9F8233AC-BE49-4C79-8EE3-E7E1985B2077</instance>
<name type="string">Microsoft Shutdown Component</name>
</vdev006>
<vdev007>
<device type="string">2497f4de-e9fa-4204-80e4-4b75c46419c0</device>
<flags type="integer">1</flags>
<instance type="string">2497F4DE-E9FA-4204-80E4-4B75C46419C0</instance>
<name type="string">Microsoft Time Synchronization Component</name>
</vdev007>
<vdev008>
<device type="string">5ced1297-4598-4915-a5fc-ad21bb4d02a4</device>
<flags type="integer">1</flags>
<instance type="string">5CED1297-4598-4915-A5FC-AD21BB4D02A4</instance>
<name type="string">Microsoft VSS Component</name>
</vdev008>
<vdev009>
<device type="string">6c5addb9-a11a-4e8e-84cb-e6208201db63</device>
<flags type="integer">1</flags>
<instance type="string">6C5ADDB9-A11A-4E8E-84CB-E6208201DB63</instance>
<name type="string">Microsoft RDV Component</name>
</vdev009>
<vdev010>
<device type="string">2fc216b0-d2e2-4967-9b6d-b8a5c9ca2778</device>
<flags type="integer">1</flags>
<instance type="string">A80E9C62-750A-4A6B-9548-D46677E806BE</instance>
<name type="string">Synthetic Ethernet Port</name>
</vdev010>
<vdev011>
<device type="string">d422512d-2bf2-4752-809d-7b82b5fcb1b4</device>
<flags type="integer">1</flags>
<instance type="string">24984ED0-BDAD-4B90-82B2-5D59F874E91E</instance>
<name type="string">Synthetic SCSI Controller</name>
</vdev011>
<version type="integer">260</version>
</manifest>
<properties>
<global_id type="string">B37E54CD-FFBB-44DA-8B7C-322B922EAD72</global_id>
<highly_available type="bool">False</highly_available>
<last_powered_off_time type="integer">130493284127496105</last_powered_off_time>
<last_powered_on_time type="integer">130493284065876653</last_powered_on_time>
<last_state_change_time type="integer">130493284127496105</last_state_change_time>
<name type="string">LegacyTS</name>
<notes type="string"></notes>
<type_id type="string">Virtual Machines</type_id>
<version type="integer">1024</version>
</properties>
<settings>
<global>
<logical_id type="string">B37E54CD-FFBB-44DA-8B7C-322B922EAD72</logical_id>
</global>
<memory>
<bank>
<dynamic_memory_enabled type="bool">True</dynamic_memory_enabled>
<limit type="integer">1048576</limit>
<priority type="integer">5000</priority>
<reservation type="integer">512</reservation>
<size type="integer">4096</size>
<target_memory_buffer type="integer">20</target_memory_buffer>
</bank>
<vnuma>
<max_size_per_node type="integer">14770</max_size_per_node>
</vnuma>
</memory>
<processors>
<count type="integer">1</count>
<features>
<limit type="bool">False</limit>
</features>
<limit type="integer">100000</limit>
<limit_cpuid type="bool">False</limit_cpuid>
<reservation type="integer">0</reservation>
<vnuma>
<count_per_node>
<max type="integer">4</max>
</count_per_node>
<node_per_socket>
<max type="integer">1</max>
</node_per_socket>
</vnuma>
<weight type="integer">100</weight>
</processors>
<stopped_at_host_shutdown type="bool">False</stopped_at_host_shutdown>
<vnuma>
<enabled type="bool">False</enabled>
</vnuma>
</settings>
</configuration>
If its relevant, the host is not yet activated license wise. I downloaded the demo version so I could test my idea before making a purchase to go ahead with full implementation.
As it stands right now I'm not sure how to troubleshoot this. Many searches on google have not turned up any helpful info. Does anyone have any ideas?
Thanks,
D

Hi ,
First , please refer to the supported guest OS of windows 2012 hyper-v :
http://technet.microsoft.com/library/hh831531.aspx
2003/R2 should be with sp2 and max 2 virtual processors .
"'LegacyTS' was reset because an unrecoverable error occurred on a virtual processor that caused a triple fault."
If the issue is not due to the above items , you can try to check the "CPU compatibility " in that VM settings for troubleshooting:
Hope it helps
Best Regards
Elton Ji
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.

[SOLVED] Arch Linux Duke (2007) Fails to Boot

Folks, I have a unique and challenging problem that has exhausted my Arch Linux skills, and so I am now turning to you.
I have a vintage Pentium Pro 200 system (that’s 200 MHz folks! – 200 MHz 686 architecture – the original 686!), two CPUs, running a dual boot between Windows NT 4.0 and Arch Linux Duke (2007). It has 512 MB of RAM and a 120 GB hard drive, partitioned up between Windows NT and Linux. I built this system new in 2007, hence the dated version of Arch. It has run like a charm all these years, granted not getting that much use. After about a year of no use at all, I fired the system up last week to help with a little research for a blog post I was writing on networking Windows NT 4.0 and Mac OS 8.6. Windows NT 4.0 fired right up with no issue, and after I was done testing what needed to be tested I tried to boot over to Arch.
After a year of disuse, Arch unexpectedly and stubbornly refused to boot. The boot process started up just fine, but towards the end, it declared that it could not mount the root file system on the root device and took a kernel panic and stopped. My Arch skills have gotten a bit rusty in the last few years, but I dusted them off and went to work. My guess was a file system or superblock error. Arch wouldn’t boot, but I dragged out my trusty RIPLinux 2.9 Rescue Live CD and fired it up. It came right up and ran, and I was able to mount the Arch partition and view all the files… everything seemed to be there; it just wouldn’t boot. Windows NT 4.0 AND RIPLinux both boot and run on the machine, so the hardware is fine as well.
A little information on the disk layout. Windows NT 4.0 is in the first partition on the hard drive. The extended partition has a second Windows NT 4.0 partition (sort of a /home partition for Windows NT 4.0), followed by the main Arch partition (the one I am trying to boot), followed by a swap partition and then the largest partition, which I use to share data between Arch and Windows NT 4.0 (I have loaded an ext2/3 driver into Windows NT 4.0 and it happily accesses the Linux partitions on the box).
RIPLinux’s e2fsck did find some issues with the Arch partition and I had it repair them all. I checked again afterwards that all the files were still there, and they were. With the partition now known to be clean, and the superblock repaired from one of the backups, all should have been well. However, Arch still wouldn’t (and still won’t) boot.
RIPLinux has a kind of a chain loader function, so I had it attempt to start up Arch for me. However, this was flummoxed by the fact that Arch addresses all my hard drive partitions as /dev/sdax and RIPLinux addresses them as /dev/hdax. Hence, without a common language, it was hard to get the one to start the other. Still, using this function, I have been able to get a crippled version of Arch running on the machine again. No modules had been loaded, and so it couldn’t do almost anything, but there it was (and is), Arch Linux Duke, at the CLI level. From there, I can see all the files, I can move freely in and out of my user account and the root account, but I can’t make the thing actually boot properly.
If you have read this far, you are a trooper. Summarizing what I know, the hardware is good, the file system is clean, the superblock is good, I can mount it cleanly from a live CD and I can chain load a crippled version of Arch. Here is the boot process blow-by-blow. When I try to do a normal boot, the Windows NT 4.0 loader passes control to the Lilo boot sector I have placed on hda1 (sda1 in Duke’s parlance). Lilo takes over, present a menu and when I select Duke, takes off. Arch Linux Duke starts to boot. It gets a good long way along, all the way along to:
:: Loading udev events [Pass]
:: Mount root Read-only
:: Checking file systems
This is where it stops.
The next thing I see is:
/dev/sda6
The superblock could not be read or does not describe a correct ext2 filesystem. If the device is valid and it really contains an ext2 filesystem (and not swap or ufs or something else) then the superblock is corrupt and you might try running e2fsck with an alternate superblock:
E2fsck –b 8193 <device>
I then get a sort of character based splash screen that says
**********FILE SYSTEM CHECK FAILED ****************************
* Please repair manually and reboot. Note that the root file system
* is currently mounted read-only. To remount it read-write, type:
* mount –n –o remount,rw /. When you exit the maintenance
* shell, the system will reboot automatically
Give root password for maintenance
At this point, I give the root password and enter the maintenance shell as root. I typed in “mount” and the first entry I got back is
/dev/sda6 on / type ext3 (rw)
This is exactly the root partition that the start up complains about. It is clearly there. I can see it, I can walk around it… it is clearly there. Why won’t it boot? Despite the message, the superblock is fine – it passes every test e2fsck can throw at it.
At this point, I did a “e2fsck /dev/hda6 (which is how RIPLinux would have passed it into Arch” and it says it is “clean”. I suspect that the Superblock message is because Arch sees root as sda6, while RIP passed it in as hda6...
Deciding to see what Arch would be seeing as it tried to set things up in the boot sequence, I tried the following next:
# mknod “/dev/root2” b 3 6
(“3” because RIPLinux refers to my hard drive as IDE, while Arch refers to it by major number “8”, which is SCSI. By the way, it IS an IDE drive – not sure why Arch insists on using the sdx nomenclature instead of hdx)
Then I entered “mount /dev/root2 /mnt/hda6” and “ls /mnt/hda6”
All was well. I can make the node, I can mount it, and I can see the contents. All is clearly well, but something is clearly wrong enough that Arch can’t boot.
I am totally out of ideas. I have tried every trick I know and am out of tricks. I would welcome any insights as to what I could try to get this venerable Arch installation back on its legs.
By the way, the key section of the /etc/lilo.conf file (lest anyone want to know) is:
image = /boot/vmlinuz26
root = /dev/sda6
label = ArchLinux-Duke
initrd = /boot/kernel26.img
read-only
I am stumped. Thanks in advance for any and all pointers you may be able to offer.
Last edited by mac57 (2014-06-02 17:42:21)

Folks, thanks for all your helpful comments, and I wanted to report back to you that I finally overcame the issue, and ArchLinux-Duke (2007) is once again executing flawlessly on my old Pentium Pro 200 system. I won't bother reporting here all the blind allies I went down as I tried to figure out what was wrong, but in the end, literally moments before I was about to give up and overwrite my Arch installation with a new Linux variant (antiX seemed well suited for such old and low power hardware), my attention was drawn to a note I had made in my files back in 2007 about a problem with similar symptoms. In that case, I had just deleted ZenWalk Linux from the hard drive (both Arch and Zen had been on the drive), and merged several partitions to make use of the newly free space. This had changed Arch's view of the drive lettering, and what had been its /dev/sddx root device was now /dev/sdcx. Arch failed to boot, throwing off the same errors I was seeing now. I wish I had recalled that note a month or so ago! It would have saved me a lot of work and a lot of frustration.
At any rate, as a last step, and testing the idea that maybe the drive lettering had changed for some reason, I repeatedly manually booted Arch, specifying root=/dev/sda6, then /dev/sdb6, then /dev/sdd6, and finally, /dev/sdc6. Eureka! Arch now considered itself to be on /dev/sdc6 whereas previously it had been on /dev/sda6. This got me part way there, but the boot failed at the filesystem check stage and threw me into root. I disabled the file system check in /etc/rc.sysinit and got farther. Then I cleaned up /etc/fstab to agree with the new sdc naming, and I was back on the air fully.
So, what had happened was that Arch had changed its view of the drive it was on from sda6 to sdc6. While I could not understand why this "sudden" change had occurred, at least I had a solution, and had Arch back up and running.
Trolling through the rest of my notes, I found the answer. In 2012, the Tekram SCSI card in the machine failed, and I ultimately replaced it with an Adaptec card. The Tekram card did not have a BIOS segment on it. The Adaptec card did. My guess is that this caused the two internal SCSI devices I have built into the system (Iomega ZIP and Jaz respectively) to be enumerated first, claiming the "sda" and "sdb". device names. That left "sdc" for the root device, and that is where Arch went next. This is my guess anyway.
I should have caught this issue back in 2012, at the time, but from my notes, I can see that I tested the new card thoroughly using the Windows NT 4.0 side of the machine, but never thought to bring up Arch as well. Hence, this problem lay dormant for two years, before I attempted to fire up Arch last month and blundered right into it.
It has not all been bad. I have learned more about the ext2 and ext3 file systems and superblocks in the intervening time than I will ever need to use. I have learned how to manually boot Linux on a machine whose BIOS is so old that it cannot address the disk cylinder that the kernel is on and I have completely refreshed the many general Linux skills that used to just flow from my finger tips. It has been a frustrating experience, but ultimately a successful and useful one.
Just wanted to let everyone know that this is now [SOLVED]. I would mark the post as such, but I don't see any obvious way to do that. Thanks again everyone.

Compaq Notebook CQ-45 137TX fails to boot

Hello,
I own a Compaq CQ-45 137TX (Intel Core 2 Duo P7350, 3 GB RAM, 320GB HDD, nVidia GeForce 9200M GS, Windows 7(upgraded from Vista)) with a broken LCD Screen. Since repairing the screen made no sense for such an old laptop, I started using it as a desktop by attaching an external monitor and input devices. The computer worked fine for the past few months.
Upon restarting the computer after a hiatus of a week or so, the computer failed to boot and display anything on the external monitor. I think it is failing POST.
The laptop gives out multiple beeps continually (not continuous, multiple beeps that don't end).
I thought that the RAM is faulty and tried to reboot the machine by trying one RAM stick at a time (since the laptop has two). It didn't work for either of the two sticks tried in both slots individually.
I think both the RAM sticks may be faulty, however, I am unable to borrow a RAM stick to test on it.
Before buying a new one, I would like someone to clarify or point out other hardware that may faulty in this laptop. I have had people tell me that my Graphic Card may have given up.
Thank you for your assistance.

Hello @root123 ,
Welcome to the HP Forums!
I understand you're unable to boot up your CQ-45 notebook.
It's unlikely to be RAM if neither card worked in either of the two DIMM slots. It is possible that both cards or slots have failed, but highly unlikely.
The beeping should tell you exactly what the error is. Try looking through this document which should help you identify the error: Computer Does Not Start and the LEDs Blink or the Computer Beeps.
You may also want to try this document as well: Troubleshooting Black Screen Displays with No Error Messages During Startup or Boot.
Let me know if you're able to identify the failure with the beep code and we'll go from there.
Please click the "Kudos, Thumbs Up" at the bottom of this post if you want to say "Thanks" for helping!
Please click "Accept as Solution" if you feel my post solved your issue, it will help others find the solution.
The Great Deku Tree
I work on behalf of HP.

Arch fails to boot after installation (BIOS mode)

I finished my Arch installation, following the Beginner's Guide, and once I unmounted the partitions and rebooted, GRUB failed to boot into Arch. I'm not exactly sure what the problem is though. Basically what happens is I power on the machine, the Dell splash screen comes up, GRUB loads, I choose
Arch Linux, with Linux core repo kernel
the kernel and ramdisk attempt to load, then some message about "recovering journal" appears, and then I return back to the Dell splash screen. The same thing happens even if I choose the second option
Arch Linux, with Linux core repo kernel (Fallback initramfs)
However, when I choose to boot Win XP everything boots just fine. My apologies for the quality of the videos and pictures.
Here's a video of what happens:
http://youtu.be/uC96kX6iTjI
I suspect this has to do with this error I got when I generated the "grub.cfg". Although I'm not entirely sure because my understanding is that this error would affect booting Win XP which in fact boots perfectly fine.
Error (and no I'm not using any lvm volumes)
http://imgur.com/qqxpoGG
I believe these are the portions of the "grub.cfg" that load Arch and Win XP. I got these by pressing "e" while on their menu entry in the GRUB bootloader.
Arch (I had to scroll down to see the rest, hence two pictures)
http://imgur.com/79dBw2C
http://imgur.com/qusEfL0
Win XP
http://imgur.com/oLnLlT0
Any idea how I can fix this? Any help is greatly appreciated and please be patient, I know, I'm a noob.
* I'm not sure if this is of any significance but I had a problem very similar to this when trying to get the Arch install to boot via usb (this computer doesn't have CD/DVD drive). I solved it by following this excerpt from the Beginner's Guide.
Troubleshooting boot problems
If you are using an Intel video chipset and the screen goes blank during the boot process, the problem is likely an issue with Kernel Mode Setting. A possible workaround may be achieved by rebooting and pressing
e
over the entry that you are trying to boot (i686 or x86_64). At the end of the string type
nomodeset
and press
Enter
Here's a video of what it looked like:
http://youtu.be/vXRcbU0zdto
The computer specs:
OS: Windows XP Professional 32 bit Version 2002 Service Pack 3
CPU: Intel Pentium 4 @ 3.00 GHz
RAM: 2 GB DDR2
HDD: 80 GB

Hi,
why did you not try adding nomodeset with the regular boot? During the net-install no video drivers will be installed;
you have to install them after reboot after installing xorg. The (video)problem you had with booting from usb is still
present.

Connecting to the LOB system has failed. A network-related or instance-specific error occurred while establishing a connection to SQL Server. The server was not found or was not accessible. Verify that the instance name is correct and that SQL Server is

hi ,
when generate the schema , i got the below error, please any one put your inputs:
Connecting to the LOB system has failed. A network-related or instance-specific error occurred while establishing a connection to SQL Server. The server was not found or was not accessible. Verify that the instance name is correct and that SQL Server
is configured to allow remote connections. (provider: Named Pipes Provider, error: 40 - Could not open a connection to SQL Server).

thaks shanky,
but facing another , after generate schema from WCF_SQL, im unable get elements in my schema.
this is schema generate from storeprocduer , but thru WCF-sql im unable get the elements like
id, name
<xsd:schema targetNamespace="urn:schemas-microsoft-com:sql:SqlRowSet2" xmlns:schema="urn:schemas-microsoft-com:sql:SqlRowSet2" xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns:sqltypes="http://schemas.microsoft.com/sqlserver/2004/sqltypes" elementFormDefault="qualified">
<xsd:import namespace="http://schemas.microsoft.com/sqlserver/2004/sqltypes" schemaLocation="http://schemas.microsoft.com/sqlserver/2004/sqltypes/sqltypes.xsd" />
<xsd:element name="Test.dbo.sample">
<xsd:complexType>
<xsd:sequence>
<xsd:element name="id" type="sqltypes:int" minOccurs="0" />
<xsd:element name="name" minOccurs="0">
<xsd:simpleType>
<xsd:restriction base="sqltypes:nvarchar" sqltypes:localeId="1033" sqltypes:sqlCompareOptions="IgnoreCase IgnoreKanaType IgnoreWidth" sqltypes:sqlSortId="52">
<xsd:maxLength value="1000" />
</xsd:restriction>
</xsd:simpleType>
</xsd:element>
</xsd:sequence>
</xsd:complexType>
</xsd:element>
</xsd:schema>
<Test.dbo.sample xmlns="urn:schemas-microsoft-com:sql:SqlRowSet2">
<id>18</id>
<name>BIRADAR</name>
</Test.dbo.sample>
<Test.dbo.sample xmlns="urn:schemas-microsoft-com:sql:SqlRowSet2">
<id>18</id>
<name>BIRADAR</name>
</Test.dbo.sample>
<Test.dbo.sample xmlns="urn:schemas-microsoft-com:sql:SqlRowSet2">
<id>19</id>
<name>sw</name>
</Test.dbo.sample>
<Test.dbo.sample xmlns="urn:schemas-microsoft-com:sql:SqlRowSet2">
<id>18</id>
<name>BIRADAR</name>
</Test.dbo.sample>
<Test.dbo.sample xmlns="urn:schemas-microsoft-com:sql:SqlRowSet2">
<id>14</id>
<name>swe</name>
</Test.dbo.sample>
<Test.dbo.sample xmlns="urn:schemas-microsoft-com:sql:SqlRowSet2">
<id>13</id>
<name>se</name>
</Test.dbo.sample>

Z68A-GD65 (G3) fails to boot with new Gigabyte Radeon HD 7950 OC

Hi,
I have a problem with my new Gigabyte AMD Radeon HD 7950 (GV-R795WF3-3GD):
My system fails to boot with this GPU, with the old Radeon HD 4850 everything works fine.
Here are my system specs:
MSI Z68A-GD65 (G3)
CPU: Intel Core i5-2500K
RAM: 8Gb DDR3-RAM (Corsair)
power supply: be quiet! Pure Power L7 530W
What I have already tried to fix the problem:
-CMOS Reset
-other PCI-e slot
-other power supply (old 750W)
Nothing worked.
Do I need a Bios update? My current version is V23.7, but I'm not sure whether I can use the latest versions because my CPU is a SandyBridge...

We can't help you woth your vga as it is no MSI product. You can try latest bios for your board (http://www.msi.com/product/mb/Z68A-GD65--G3-.html#/?div=BIOS) because the latest bios versions for G3 boards are working well with Sandy and Ivy. If latest bios should not help and you like to downgrade the bios we can give you the needed files if you ask here.

Z87-GD65 fails to boot when I enable X.M.P.

Guys, Looking for any advise out there. I have two systems with new Z87-GD65 with an Intel 4770K and 16GB ADATA RAM and one of the systems fails to boot whenever I enable X.M.P. I've switched out the RAM from one system to the other and everything is fine on one and same thing on the other. I've tried clearing out the CMOS and booting from both sets of bios. I have OC turned off. Everything is fine until I enable X.M.P. I'm at a loss any ideas?
Thanks,
Frank

Thanks for the help Froggy. Here is the information you asked for:
MSI z87-GD65 running Bios 1.3
Memory:
DDR3-2400G PC3-19200 8GB x 2 CL11-13-13-35 1.65V CAS 11
Broken System CPU-Z Screenshots:
CPU
Memory
SPD Slot 2
SPD Slot 4
Working System CPU-Z Screenshots:
CPU
Memory
SPD Slot 2
SPD Slot 4
Thanks for all your help.

Mountain Lion hangs during boot sequence after reinstall

I am running Mountain Lion on a late-2012 Mac Mini (the newest one at this writing), and my system got messed up after I tried to reset my primary uid to 501 (I know, first mistake) after having migrated the system from an older Mac Mini. This worked partially, but I continued to have issues accessing some files and got tired of resetting the permissions manually.
I tried reinstalling Mountain Lion and since then, the system fails to boot completely. I can get as far as seeing the desktop, Finder menu, Dock, etc., but then one or more error windows pop up relating to specific resources (I think Calendar Agent was one of them, I can't remember because I then saw the spinning disk icon and the system stopped responding). I tried restarting by turning the computer off and then on again, but continue to get similar errors after it gets almost all the way through booting.
Although I have much of my data on the hard drive backed up to an external Seagate drive on my home network, I had not been able to do a complete backup because I have many old (pre-OS X) files that contain slashes or other characters no longer allowed in filenames, and it has proven too cumbersome to update all the filenames to make it worthwhile. Thus, I am not able to wipe the hard drive and start from scratch.
I know how to boot in Single-User mode, which does work, but don't know enough BSD/Darwin to pinpoint the source of this problem and fix it.
Any advice about how to diagnose and/or solve this problem? I would like to be able to correct any uid and gid conflicts that may be causing this, which I believe would work, but am not sure how to do this. I am writing this from Safari after booting in Recovery mode.
Thanks for any help with this. - Klingon725

Back up all data.
This procedure will unlock all your user files (not system files) and reset their ownership and access-control lists to the default. If you've set special values for those attributes on any of your files, they will be reverted. In that case, either stop here, or be prepared to recreate the settings if necessary. Do so only after verifying that those settings didn't cause the problem. If none of this is meaningful to you, you don't need to worry about it.
Step 1
If you have more than one user account, and the one in question is not an administrator account, then temporarily promote it to administrator status in the Users & Groups preference pane. To do that, unlock the preference pane using the credentials of an administrator, check the box marked Allow user to administer this computer, then reboot. You can demote the problem account back to standard status when this step has been completed.
Triple-click the following line to select it. Copy the selected text to the Clipboard (command-C):
{ sudo chflags -R nouchg,nouappnd ~ $TMPDIR.. ; sudo chown -Rh $UID:staff ~ $_ ; sudo chmod -R u+rwX ~ $_ ; chmod -R -N ~ $_ ; } 2> /dev/null
Launch the Terminal application in any of the following ways:
☞ Enter the first few letters of its name into a Spotlight search. Select it in the results (it should be at the top.)
☞ In the Finder, select Go ▹ Utilities from the menu bar, or press the key combination shift-command-U. The application is in the folder that opens.
☞ Open LaunchPad. Click Utilities, then Terminal in the icon grid.
Paste into the Terminal window (command-V). You'll be prompted for your login password, which won't be displayed when you type it. You may get a one-time warning not to screw up. If you don’t have a login password, you’ll need to set one before you can run the command. If you see a message that your username "is not in the sudoers file," then you're not logged in as an administrator.
The command will take a noticeable amount of time to run. Wait for a new line ending in a dollar sign (“$”) to appear, then quit Terminal.
Step 2 (optional)
The first step should give you usable permissions in your home folder. This step will restore special attributes set by OS X on some user folders to protect them from unintended deletion or renaming. You can skip this step if you don't consider that protection to be necessary.
Boot into Recovery by holding down the key combination command-R at startup. Release the keys when you see a gray screen with a spinning dial.
When the OS X Utilities screen appears, select
Utilities ▹ Terminal
from the menu bar. A Terminal window will open.
In the Terminal window, type this:
resetpassword
That's one word, all lower case, with no spaces. Then press return. A Reset Password window will open. You’re not going to reset a password.
Select your boot volume ("Macintosh HD," unless you gave it a different name) if not already selected.
Select your username from the menu labeled Select the user account if not already selected.
Under Reset Home Directory Permissions and ACLs, click the Reset button.
Select
 ▹ Restart
from the menu bar.

IMac shuts down on 1/3 of boot sequence

Hello,
My 20 inch 2007 iMac suddenly started shutting down on 1/3 of boot sequence. This happened after the mac just shut down while i was working on it, since this happened the mac will not boot. The Apple logo appears, the loading bar appears, it gets to 1/3 off the bar, then it disappears, and the mac shuts down. I already used the disk utility to check the disk, there seems to be no problem. Also, i already re-installed MacOS, this did not have any effect as well.
Does anyone know how to fix this problem?
Mac info:
iMac 7,1 20 inch
Processor: Intel core 2 duo, 2.4 ghz
4GB of Ram.

Reinstalling OS X Without Erasing the Drive
Boot to the Recovery HD: Restart the computer and after the chime press and hold down the COMMAND and R keys until the menu screen appears. Alternatively, restart the computer and after the chime press and hold down the OPTION key until the boot manager screen appears. Select the Recovery HD and click on the downward pointing arrow button.
Reinstalling OS X Without Erasing the Drive
Repair the Hard Drive and Permissions: Upon startup select Disk Utility from the main menu. Repair the Hard Drive and Permissions as follows.
When the recovery menu appears select Disk Utility and press the Continue button. After Disk Utility loads select the Macintosh HD entry from the the left side list. Click on the First Aid tab, then click on the Repair Disk button. If Disk Utility reports any errors that have been fixed, then re-run Repair Disk until no errors are reported. If no errors are reported click on the Repair Permissions button. Wait until the operation completes, then quit Disk Utility and return to the main menu.
Reinstall OS X: Select Reinstall OS X and click on the Continue button.
Note: You will need an active Internet connection. I suggest using Ethernet if possible because it is three times faster than wireless.
Also see:
Reinstall OS X Without Erasing the Drive
Choose the version you have installed now:
OS X Yosemite- Reinstall OS X
OS X Mavericks- Reinstall OS X
OS X Mountain Lion- Reinstall OS X
OS X Lion- Reinstall Mac OS X
Note: You will need an active Internet connection. I suggest using Ethernet
if possible because it is three times faster than wireless.

[SOLVED] Luks with /arch/setup installation , fails at boot

Hi all,
So I tried to install arch on virtualbox with encrypted partitions (root /, /home/ and swap), but it fails at boot.
/dev/sda1 is /boot
/dev/sda2 is swap
/dev/sda3 is /
/dev/sda4 is /home
The root partition seems to be loading fine because it asks for my password, then the boot sequence goes on, until the /home/ (apparently) :
:: Bringing up loopback interface
:: Unlocking encrypted volumes: chome..Usage: cryptsetup [-?vyrq] (...all the options...can't copy paste with virtualbox)
/sbin/cryptsetup: Unknown action
failed [FAIL]
/dev/mapper/croot: clean, 27576/457856 files, 166316/1830898 blocks
fsck.ext4: No such file or directory while trying to open /dev/mapper/chome
Possibly non-existent device?
/dev/sda1: clean,29/24096 files, 20790/96356 blocks
[FAIL]
It seems that it tries to open /dev/mapper/chome but it's not mounted yet
In my /etc/crypttab, I added the lines :
chome /dev/sda4 none luks
cswap /dev/sda2 none luks
/etc/fstab (I didn't change anything, /arch/setup configured it that way) :
/dev/mapper/chome /home ext4 defaults 0 1
/dev/mapper/croot / ext4 defaults 0 1
/dev/mapper/cswap swap swap defaults 0 0
/dev/sda1 /boot ext2 defaults 0 1
And grub :
title Arch Linux
root (hd0,0)
kernel /vmlinuz-linux root=/dev/mapper/croot cryptdevice=/dev/sda3:croot ro
initrd /initramfs-linux.img
What I wanted to do was to have swap,root and home encrypted partitions mounted at boot, but maybe it is not possible?
I tried a lot of configurations for /etc/fstab and /etc/crypttab according to what I could find on the net but nothing worked. I read the whole tutorial https://wiki.archlinux.org/index.php/Sy … _with_LUKS but there is no config for fstab or crypttab or grub when installing with /arch/setup
Thanks for any help !
Last edited by John0000 (2012-04-12 12:50:18)

Indeed you have a point, putting password in plaintext isn't very safe.
There is a good alternative though: https://wiki.archlinux.org/index.php/Sy … _a_Keyfile
the reason why you don't have a passphrase for root in a file somewhere is that you provide this passphrase during boot-time.
Somewhere during boot you get the option to unlock you root device by typing in a passphrase... right?
ro means that the volume is mounted read only http://linux.die.net/man/8/mount

Kernels 3.10.6 and 3.10.7 fail to boot with EFI stub

Been using rEFInd for some time now. Current installed version is 0.7.1. Kernels 3.10.5 and earlier would boot without incident. Yesterday I upgraded to 3.10.6 and boot failed. As a workaround, I copied the Liquorix kernel and initramfs from my Kubuntu partition; to my mild surprise, this worked. My next test was to install the 3.10.7 Zen kernel from heftig's repository. This kernel boots fine (I added a version number string to the name of the kernel image and the initramfs so that rEFInd would automatically match them). After that, I enabled Arch testing and updated the Arch kernel to 3.10.7; this also fails to boot just like the 3.10.6 kernel did.
I'm a fan of boot text, so I've configured rEFInd in text mode only. Here's my refind.conf, with almost no changes from defaults:
timeout 20
textonly 1
use_graphics_for
scan_all_linux_kernels
And my /boot/refind_linux.conf:
"Boot to X" "ro root=/dev/sda3 nox2apic nmi_watchdog=0 elevator=noop acpi_osi=Linux pcie_aspm=force raid=noautodetect systemd.unit=graphical.target"
"Boot to single user" "ro root=/dev/sda3 nox2apic nmi_watchdog=0 elevator=noop acpi_osi=Linux pcie_aspm=force raid=noautodetect systemd.unit=multi-user.target"
# "Boot to recovery" "ro root=/dev/sda3 nox2apic nomodeset systemd.unit=rescue.target"
Finally, details abot my laptop -- a ThinkPad T520:
steve@t520 ~ $ inxi -xxSMCGDp
System: Host: t520 Kernel: 3.10.7-1-zen x86_64 (64 bit, gcc: 4.8.1)
Desktop: KDE 4.11.00 (Qt 4.8.5) dm: kdm Distro: Arch Linux
Machine: System: LENOVO product: 423926U version: ThinkPad T520 Chassis: type: 10
Mobo: LENOVO model: 423926U Bios: LENOVO version: 8AET63WW (1.43 ) date: 05/08/2013
CPU: Dual core Intel Core i7-2620M CPU (-HT-MCP-) cache: 4096 KB flags: (lm nx sse sse2 sse3 sse4_1 sse4_2 ssse3 vmx) bmips: 10769.3
Clock Speeds: 1: 1188.00 MHz 2: 1809.00 MHz 3: 1809.00 MHz 4: 1080.00 MHz
Graphics: Card: NVIDIA GF119M [Quadro NVS 4200M] bus-ID: 01:00.0 chip-ID: 10de:1057
X.Org: 1.14.2 driver: nvidia Resolution: [email protected]
GLX Renderer: NVS 4200M/PCIe/SSE2 GLX Version: 4.3.0 NVIDIA 325.15 Direct Rendering: Yes
Drives: HDD Total Size: 1256.3GB (8.2% used)
1: id: /dev/sda model: M4 size: 256.1GB serial: 000000001140031E608A temp: 0C
2: id: /dev/sdb model: HGST_HTS721010A9 size: 1000.2GB serial: JG40006PG61HKC temp: 43C
Partition: ID: / size: 108G used: 37G (37%) fs: ext4
ID: /boot/efi size: 511M used: 3.1M (1%) fs: vfat
ID: /mnt/kubuntu size: 118G used: 59G (53%) fs: ext4
ID: swap-1 size: 9.64GB used: 0.00GB (0%) fs: swap
Last edited by steveriley (2013-08-19 05:27:15)

Steve, your picture is far too large for these forums. You are going to want to put it in some kind of a picture sharing/hosting site and link back to it. Otherwise it will end up disappeared (likely via black magic) from your post. I don't think that it provides any useful information anyway. If you want to post your kernel command line that is great. But posting a picture of a frozen screen with no output... doesn't really do much good.
Efistub has been a bit shaky since 3.6 actually. There is a monster thread about this already, the title of which references 3.6, but the content continues on through several kernel releases. Still people continually report this as being an issue. What I do is I keep a normal efi bootloader (one that doesn't rely on efistub) at the ready all the time. My choice was elilo, but since [testing] started including syslinux-efi in the syslinxu package, I have started using that... though I still have elilo set up.
Can you boot with efistub from the UEFI Shell or gummiboot? I prefer gummiboot, but I have had this problem in the past, and when I did, I was able to boot with rEFInd... which was strange. Some people even report that simply having a direct efibootmgr entry in their firmware causes it to magically work. Though there should be to reasonable explanation for this, it was confirmed by several people in the mentioned thread.

MSI P31 Neo-F V2 - Fails to Boot

I've got an MSI P31 Neo-F V2 motherboard that I've had for about about 16 months now. Unfortunately today it's just started failing to boot correctly.
I turned the machine on and was greeted with a red error message just after the usb controller was initalized. The message said "Warning !!! The previous performance of overclocking is failed and the system is restored to the default settings. Press any key except "DEL" to enter SETUP......."
I haven't overclocked the machine (don't know how) so I'm not quite sure why that error message was coming up. Anyway, I pressed space, that prompted me to restore settings which I did, then took me to setup where I saved and exited. Then tried to restart the machine. From this point on (about 30 restarts) I've had that message twice. Normally it does one of the following:
a) Powers up, no bleeps, no video output. Sits there waiting.
b) Powers up for a few seconds, then powers straight back down. Waits about 10 seconds, then repeats. Eventually after enough retries it will reach the some point as (a).
I've tried disconnecting power, I've tried taking the CMOS battery out. The last time I got to the error message my USB keyboard wouldn't even work so I couldn't do anything but restart. If anyone has any suggestions on what to do then fire away, as I'm really stuck now
I don't know what version of the BIOS I'm running as I can't get that far anymore. Apart from the CPU which I'm not sure is important? (Intel Duo 3Ghz) I'm not sure on much more info on my system.
Thanks.
Ian

Ok, I've managed to find an old photo of the Bios.
Bios: A7392IMS V2.1 080608 is the number top left.
CPU : Intel Core 2 Duo E8400 3.0Ghz
Gfx : 512Mb NiVidia GeForce 9800GTX+
Mem: 2 X 2GB DDR 2 800 MHz (will try and find out brand).
H/D : 2 * 160Gb drives. One is Seagate, the other Western Digital, both SATA 2.
OS : XP not that it's really relevant...
PSU : 800W. Don't know brand and DC current output. Will try to get these.

Z68-GD65 G3 + i5 3570k fails to boot.

Hi
I just bought the Z68A-GD65 G3 mainboard and it fails to boot. The system wont even go to bios and nothing happens on my screen. When i press the power on it only lasts for 3-7 seconds until the system turns off again. It might try to boot a few times until it stops doing it. I have i5 3570k processor and OCZ agility SSD where my windows is installed and a HDD as a 2nd drive (have tried booting without this on too). I heard that the original BIOS on the mainboard doesn't support Ivy Bridge, so is there any way for me to install a new version of bios that supports Ivy Bridge when i have no Sandy Bridge processor to boot it up with on the first place? Can't remember the exact specs on HDD since im at work computer atm. I have also tried to boot without the GPU as the processor should have integrated GPU.
GPU is GTX 560 Ti phantom 2
OCZ Agility 3 120 GB 2.5" SSD SATA III
Kingston HyperX 4 GB DDR3 1600 MHz CL9 Red Limited x2
Intel Core i5 3570K 3.4 GHz LGA1155

Quote from: NovJoe on 09-May-12, 11:01:22
Jooga,
Is your problem solved or the issue remains?
I believe he found that his mainboards UEFI/BIOS version needs an update to support the Ivy CPU.
https://forum-en.msi.com/index.php?topic=157236.0

[FAIL] in boot sequence related to alsactl / Intel audio hardware

Similar Messages

Maybe you are looking for