[SOLVED] DELL Vostro doesnt finish boot process with HDMI pluged in

I am using Xorg 1.16.1, when I try to boot my machine with a external monitor (HDMI) plugged in, X does not start.
Here is what dmesg says:
[ 7.368666] brcmsmac bcma0:0: wl0: brcms_c_d11hdrs_mac80211: txop exceeded phylen 137/256 dur 1602/1504
[ 7.390077] brcmsmac bcma0:0: wl0: brcms_c_d11hdrs_mac80211: txop exceeded phylen 157/256 dur 1762/1504
[ 7.528043] brcmsmac bcma0:0: brcms_ops_bss_info_changed: arp filtering: 1 addresses (implement)
[ 11.048888] [drm:ibx_irq_handler] *ERROR* PCH transcoder A FIFO underrun
[ 27.815808] [drm:ibx_irq_handler] *ERROR* PCH transcoder A FIFO underrun
when I pull the HDMI cable out, X starts properly:
[ 53.849688] fuse init (API version 7.23)
This is what lspci says:
00:02.0 VGA compatible controller: Intel Corporation Core Processor Integrated Graphics Controller (rev 18)
Has anybody an idea, what could be wrong with my system?
regards
Last edited by ifelseforeach (2014-10-06 16:35:40)

Yea I m using light-dm.
Ok, I just did another reboot to check the log files in the plugged-in/out case and I discoverd, that the boot process can not be completed as long as the HDMI cable is plugged in. (So my first Headline was unintentional right : ) )
I checked dmesg I both cases and they only differ only in the last few lines:
PluggedIN case dmesg:
[ 7.411395] brcmsmac bcma0:0: wl0: brcms_c_d11hdrs_mac80211: txop exceeded phylen 137/256 dur 1602/1504
[ 7.429694] brcmsmac bcma0:0: wl0: brcms_c_d11hdrs_mac80211: txop exceeded phylen 157/256 dur 1762/1504
[ 7.520580] brcmsmac bcma0:0: brcms_ops_bss_info_changed: arp filtering: 1 addresses (implement)
[ 60.760060] [drm:ibx_irq_handler] *ERROR* PCH transcoder A FIFO underrun
[ 67.101403] fuse init (API version 7.23)
As you can see at the time stamps, the boot process stops as line 3 and only continues at line 4 when I pull out the cable.
PluggedOUT case dmesg:
[ 7.325765] brcmsmac bcma0:0: wl0: brcms_c_d11hdrs_mac80211: txop exceeded phylen 137/256 dur 1602/1504
[ 7.347581] brcmsmac bcma0:0: wl0: brcms_c_d11hdrs_mac80211: txop exceeded phylen 157/256 dur 1762/1504
[ 7.515908] brcmsmac bcma0:0: brcms_ops_bss_info_changed: arp filtering: 1 addresses (implement)
[ 14.652575] fuse init (API version 7.23)
Last edited by ifelseforeach (2014-10-04 21:26:20)

Similar Messages

  • I've erased all my content and settings but back up doesnt finish the process to set it up. What can i do ?

    I've erased all my content and settings but back up doesnt finish the process to set it up. What can i do ?

    You have two choices. You can select another backup. I believe that your three most recent backups should be presented as choices. If for some reason you only have one backup and it will not restore, you have to restore as new.
    Do you see other backups when you are at that step in the activation process?

  • Boot process with votes messages:[vxclust]: [ID local0.error] master_vote:1

    Hi Gurus.
    I have two node cluster (node1 and node2) when we boot the cluster check the message (boot process):
    Jan 23 14:47:23 node2 ID [vxclust]: [ID 821894 local0.error] Selecting master ...
    Jan 23 14:47:23 node2 ID [vxclust]: [ID 696243 local0.error] count:0
    Jan 23 14:47:23 node2 ID [vxclust]: [ID 246593 local0.error] mvotes[count]:0
    Jan 23 14:47:23 node2 ID [vxclust]: [ID 843298 local0.error] votes[mvotes[count]]:1
    Jan 23 14:47:23 node2 ID [vxclust]: [ID 938531 local0.error] master_vote:1
    Jan 23 14:47:23 node2 ID [vxclust]: [ID 696243 local0.error] count:0
    Jan 23 14:47:23 node2 ID [vxclust]: [ID 941912 local0.error] votes[count]:1
    Jan 23 14:47:23 node2 ID [vxclust]: [ID 759296 local0.error] value:0
    Jan 23 14:47:23 node2 ID [vxclust]: [ID 696244 local0.error] count:1
    Jan 23 14:47:23 node2 ID [vxclust]: [ID 941911 local0.error] votes[count]:0
    Jan 23 14:47:23 node2 ID [vxclust]: [ID 759297 local0.error] value:1
    Jan 23 14:47:23 node2 ID [vxclust]: [ID 696245 local0.error] count:2
    Jan 23 14:47:23 node2 ID [vxclust]: [ID 941911 local0.error] votes[count]:0
    Jan 23 14:47:23 node2 ID [vxclust]: [ID 759297 local0.error] value:1
    Jan 23 14:47:23 node2 ID [vxclust]: [ID 696246 local0.error] count:3
    Jan 23 14:47:23 node2 ID [vxclust]: [ID 941911 local0.error] votes[count]:0
    Jan 23 14:47:23 node2 ID [vxclust]: [ID 759297 local0.error] value:1
    Jan 23 14:47:23 node2 ID [vxclust]: [ID 696247 local0.error] count:4
    Jan 23 14:47:23 node2 ID [vxclust]: [ID 941911 local0.error] votes[count]:0
    Jan 23 14:47:23 node2 ID [vxclust]: [ID 759297 local0.error] value:1
    Jan 23 14:47:23 node2 ID [vxclust]: [ID 696248 local0.error] count:5
    Jan 23 14:47:23 node2 ID [vxclust]: [ID 941911 local0.error] votes[count]:0
    Jan 23 14:47:23 node2 ID [vxclust]: [ID 759297 local0.error] value:1
    Jan 23 14:47:23 node2 ID [vxclust]: [ID 696249 local0.error] count:6
    Jan 23 14:47:23 node2 ID [vxclust]: [ID 941911 local0.error] votes[count]:0
    Jan 23 14:47:23 node2 ID [vxclust]: [ID 759297 local0.error] value:1
    Jan 23 14:47:23 node2 ID [vxclust]: [ID 696250 local0.error] count:7
    Jan 23 14:47:23 node2 ID [vxclust]: [ID 941911 local0.error] votes[count]:0
    Jan 23 14:47:23 node2 ID [vxclust]: [ID 759297 local0.error] value:1
    Jan 23 14:47:23 node2 ID [vxclust]: [ID 696251 local0.error] count:8
    Jan 23 14:47:23 node2 ID [vxclust]: [ID 941911 local0.error] votes[count]:0
    Jan 23 14:47:23 node2 ID [vxclust]: [ID 759297 local0.error] value:1
    Jan 23 14:47:23 node2 ID [vxclust]: [ID 696252 local0.error] count:9
    Jan 23 14:47:23 node2 ID [vxclust]: [ID 941911 local0.error] votes[count]:0
    Jan 23 14:47:23 node2 ID [vxclust]: [ID 759297 local0.error] value:1
    Jan 23 14:47:23 node2 ID [vxclust]: [ID 641765 local0.error] count:10
    Jan 23 14:47:23 node2 ID [vxclust]: [ID 941911 local0.error] votes[count]:0
    Jan 23 14:47:23 node2 ID [vxclust]: [ID 759297 local0.error] value:1
    Jan 23 14:47:23 node2 ID [vxclust]: [ID 641766 local0.error] count:11
    Jan 23 14:47:23 node2 ID [vxclust]: [ID 941911 local0.error] votes[count]:0
    Jan 23 14:47:23 node2 ID [vxclust]: [ID 759297 local0.error] value:1
    Jan 23 14:47:23 node2 ID [vxclust]: [ID 641767 local0.error] count:12
    Jan 23 14:47:23 node2 ID [vxclust]: [ID 941911 local0.error] votes[count]:0
    Jan 23 14:47:23 node2 ID [vxclust]: [ID 759297 local0.error] value:1
    Jan 23 14:47:23 node2 ID [vxclust]: [ID 641768 local0.error] count:13
    Jan 23 14:47:23 node2 ID [vxclust]: [ID 941911 local0.error] votes[count]:0
    Jan 23 14:47:23 node2 ID [vxclust]: [ID 759297 local0.error] value:1
    Jan 23 14:47:23 node2 ID [vxclust]: [ID 641769 local0.error] count:14
    Jan 23 14:47:23 node2 ID [vxclust]: [ID 941911 local0.error] votes[count]:0
    Jan 23 14:47:23 node2 ID [vxclust]: [ID 759297 local0.error] value:1
    Jan 23 14:47:23 node2 ID [vxclust]: [ID 641770 local0.error] count:15
    Jan 23 14:47:23 node2 ID [vxclust]: [ID 941911 local0.error] votes[count]:0
    Jan 23 14:47:23 node2 ID [vxclust]: [ID 759297 local0.error] value:1
    Jan 23 14:47:23 node2 ID [vxclust]: [ID 641771 local0.error] count:16
    Jan 23 14:47:23 node2 ID [vxclust]: [ID 941911 local0.error] votes[count]:0
    Jan 23 14:47:23 node2 ID [vxclust]: [ID 759297 local0.error] value:1
    Jan 23 14:47:23 node2 ID [vxclust]: [ID 641772 local0.error] count:17
    Jan 23 14:47:23 node2 ID [vxclust]: [ID 941911 local0.error] votes[count]:0
    Jan 23 14:47:23 node2 ID [vxclust]: [ID 759297 local0.error] value:1
    Jan 23 14:47:23 node2 ID [vxclust]: [ID 641773 local0.error] count:18
    Jan 23 14:47:23 node2 ID [vxclust]: [ID 941911 local0.error] votes[count]:0
    Jan 23 14:47:23 node2 ID [vxclust]: [ID 759297 local0.error] value:1
    Jan 23 14:47:23 node2 ID [vxclust]: [ID 641774 local0.error] count:19
    Jan 23 14:47:23 node2 ID [vxclust]: [ID 941911 local0.error] votes[count]:0
    Jan 23 14:47:23 node2 ID [vxclust]: [ID 759297 local0.error] value:1
    Jan 23 14:47:23 node2 ID [vxclust]: [ID 762324 local0.error] count:20
    Jan 23 14:47:23 node2 ID [vxclust]: [ID 941911 local0.error] votes[count]:0
    Jan 23 14:47:23 node2 ID [vxclust]: [ID 759297 local0.error] value:1
    Jan 23 14:47:23 node2 ID [vxclust]: [ID 762325 local0.error] count:21
    Jan 23 14:47:23 node2 ID [vxclust]: [ID 941911 local0.error] votes[count]:0
    Jan 23 14:47:23 node2 ID [vxclust]: [ID 759297 local0.error] value:1
    Jan 23 14:47:23 node2 ID [vxclust]: [ID 762326 local0.error] count:22
    Jan 23 14:47:23 node2 ID [vxclust]: [ID 941911 local0.error] votes[count]:0
    Jan 23 14:47:23 node2 ID [vxclust]: [ID 759297 local0.error] value:1
    Jan 23 14:47:23 node2 ID [vxclust]: [ID 762327 local0.error] count:23
    Jan 23 14:47:23 node2 ID [vxclust]: [ID 941911 local0.error] votes[count]:0
    Jan 23 14:47:23 node2 ID [vxclust]: [ID 759297 local0.error] value:1
    Jan 23 14:47:23 node2 ID [vxclust]: [ID 762328 local0.error] count:24
    Jan 23 14:47:23 node2 ID [vxclust]: [ID 941911 local0.error] votes[count]:0
    Jan 23 14:47:23 node2 ID [vxclust]: [ID 759297 local0.error] value:1
    Jan 23 14:47:23 node2 ID [vxclust]: [ID 762329 local0.error] count:25
    Jan 23 14:47:23 node2 ID [vxclust]: [ID 941911 local0.error] votes[count]:0
    Jan 23 14:47:23 node2 ID [vxclust]: [ID 759297 local0.error] value:1
    Jan 23 14:47:23 node2 ID [vxclust]: [ID 762330 local0.error] count:26
    Jan 23 14:47:23 node2 ID [vxclust]: [ID 941911 local0.error] votes[count]:0
    Jan 23 14:47:23 node2 ID [vxclust]: [ID 759297 local0.error] value:1
    Jan 23 14:47:23 node2 ID [vxclust]: [ID 762331 local0.error] count:27
    Jan 23 14:47:23 node2 ID [vxclust]: [ID 941911 local0.error] votes[count]:0
    Jan 23 14:47:23 node2 ID [vxclust]: [ID 759297 local0.error] value:1
    Jan 23 14:47:23 node2 ID [vxclust]: [ID 762332 local0.error] count:28
    Jan 23 14:47:23 node2 ID [vxclust]: [ID 941911 local0.error] votes[count]:0
    Jan 23 14:47:23 node2 ID [vxclust]: [ID 759297 local0.error] value:1
    Jan 23 14:47:23 node2 ID [vxclust]: [ID 762333 local0.error] count:29
    Jan 23 14:47:23 node2 ID [vxclust]: [ID 941911 local0.error] votes[count]:0
    Jan 23 14:47:23 node2 ID [vxclust]: [ID 759297 local0.error] value:1
    Jan 23 14:47:23 node2 ID [vxclust]: [ID 624920 local0.error] count:30
    Jan 23 14:47:23 node2 ID [vxclust]: [ID 941911 local0.error] votes[count]:0
    Jan 23 14:47:23 node2 ID [vxclust]: [ID 759297 local0.error] value:1
    Jan 23 14:47:23 node2 ID[vxclust]: [ID 624921 local0.error] count:31
    Jan 23 14:47:23 node2 ID[vxclust]: [ID 941911 local0.error] votes[count]:0
    Jan 23 14:47:23 node2 ID[vxclust]: [ID 759297 local0.error] value:1
    Jan 23 14:47:23 node2 ID[vxclust]: [ID 385272 local0.error] Selected master:0
    Jan 23 14:47:23 node2 ID[vxclust]: [ID 874465 local0.error] New assignment :0 node2
    Jan 23 14:47:23 node2 ID[vxclust]: [ID 151115 local0.error] New assignment :1 node1
    ===================
    If this is a problem how can we solve?
    Many Thanks
    Regards

    You did not give a lot of information in order to know which Sun Cluster version you are using and if you are using Oracle RAC together with CVM.
    To me it looks you have enabled CVM (VxVM with the cluster feature enabled) in order to use a shared diskgroup.
    This is only allowd in combination with Oracle RAC. If this is what you are trying to use, have a look at http://docs.sun.com/app/docs/doc/819-2981/6n58037s2?a=view.
    So those messages are CVM specific, and I guess they show the selection process of which node is going to be the master node for the shared diskgroup - in your case node2.
    Greets
    Thorsten

  • [SOLVED] "Filesystem check failed" during boot process

    I was using XFCE on my netbook recently and clicked "shutdown".  It logged out to the command prompt and nothing happened.  Assuming that I'd clicked "logout" by mistake, I typed "pacman -Syu" to run an update...  And moments later it suddenly started the shutdown process.
    Now, whenever I boot up, I see the message below.  I tried booting from a GParted CD to check the filesystems for errors, but none were detected.
    Can anyone suggest what I might need to do to fix the problem?
    rootfs: clean, 11026/246512 files, 477083/984576 blocks
    home: clean, 4386/527280 files, 237183/2105344 blocks
    /dev/sdb2 is mounted. e2fsck: Cannot continue, aborting.
    ************* FILESYSTEM 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
    (or type Control-D to continue):
    Last edited by esuhl (2012-03-27 01:20:07)

    Thank you all for your replies :-)
    hadrons123 wrote:What happens when you do try the suggestion given by it?
    I don't exactly know how I should "repair manually"...  I thought a filesystem check in GParted would have been enough...
    lijpbasin wrote:You can boot the system using a archlinux live cd, and run fsck manually on every linux partition in the old system with options.
    DON'T mount any of the filesystems before running fsck, or your data will probably be lost. If you want to check the partition information first, run fdisk -l with root privileges.
    Thanks.  I tried booting from an ArchBang live CD last night and ran "e2fsck -pcv" on each partition.  The check completed, but the problem persists...  I just tried again using "fsck" as you suggested and got the following output (but the machine still fails to boot with the same error as before):
    fsck from util-linux 2.20.1
    e2fsck 1.41.14 (22-Dec-2010)
    usr was not cleanly unmounted, check forced.
    Pass 1: Checking inodes, blocks, and sizes
    Pass 2: Checking directory structure
    Pass 3: Checking directory connectivity
    Pass 4: Checking reference counts
    Pass 5: Checking group summary information
    usr: 115811/458752 files (1.7% non-contiguous), 783161/1834496 blocks
    Gcool wrote:
    /dev/sdb2 is mounted. e2fsck: Cannot continue, aborting.
    As mentioned already, the reason it's failing is because the /dev/sdb2 partition is mounted before it can be fsck'd. What is this partition exactly (which filesystem, what's on it, mountpoint,...)?
    I'm not overly familiar with the Linux boot process, but why would it suddenly be mounting this partition before fsck-ing it?  Even if it was mounted when the netbook shutdown, surely the boot process starts with all partitions unmounted...?  Anyway, the partition details from /etc/fstab are below.
    <file system> <dir> <type> <options> <dump> <pass>
    tmpfs /tmp tmpfs nodev,nosuid 0 0
    /dev/sda1 / ext2 defaults,noatime 0 1
    /dev/sdb1 /home ext2 defaults,noatime,user_xattr 0 1
    /dev/sdb2 /usr ext2 defaults,noatime 0 1
    I'm (now) aware that mounting /usr as a separate partition is a bad idea and (having read the "Error when booting with the new initscripts" thread), I have told pacman to ignore updates to the initscripts package (until I figure out how best to work round or fix that issue).
    Shark wrote:Write umount /dev/sdb2 in konsole or unmount partition in gparted by right click on problematic partition and click unmount. Than proced.
    If I type "umount /dev/sdb2" at the prompt, I get the following error:
    umount: /usr: device is busy.
    (In some cases useful info about processes that use
    the device is found by lsof(8) or fuser(1))
    I tried "umount -l /dev/sdb2" to unmount when the device becomes free... but it never does.
    I also booted into GParted, but there is no option to "unmount" /dev/sdb2.  There is a "mount" option in the menu, but it is greyed out.  If I open a terminal window from the GParted Live environment and type "sudo umount /dev/sdb2" I get the following message:
    umount: /dev/sdb2: not mounted
    DSpider wrote:Are you mounting the root drive with "ro" (read only) in fstab?
    No (as shown above).  I don't *think* I've messed anything up with fstab or any other config files -- everything was working perfectly till the netbook shutdown whilst pacman was running.

  • Boot Process with active EFI Firmware Password

    I have a MacMini with Linux installed (for an embedded application) on the internal hard drive, and Mac OS X 10.5.6 available on an external Firewire / USB drive. The machine is a 1.83 MHz 2008 production unit with EFI version MM21.009A.B00 firmware installed (no later update is reported as available via the OS X Software Updater).
    The system normally boots from the internal (Linux) disk without user interaction when first powered up.
    In order to restrict users from starting the system from alternate devices, we activated an EFI firmware password. After doing so with the Open Firmware Password application on the OS X installer DVD (booted with option key and selecting the DVD icon, or with the C-key held), the system no longer automatically boots either of the two available hard disk devices. Rather a flashing file folder icon with question mark appears when the machine is powered up without any user interaction.
    With the EFI password active, it is necessary to hold the option key down, enter the password, and then select the desired disk device icon (either internal Linux or external OS X device) in order to boot the system. It appears that the system can no longer automatically select a boot device when started up, even if only one is available. This requires that every user of the embedded system must know the EFI password in order to start the system. This seriously compromises the protections that a user would expect to achieve by using the EFI password capability.
    Is this the expected performance of the firmware after the EFI password has been activated, or is this performance the result of a design flaw in the EFI code when the firmware password is active (i.e. is this a"feature" or a bug)?

    Welcome to Apple Discussions!
    The EFI firmware protection is there for people who work in environments where their machines must be secure from intruders, and secures information in event the machine gets stolen. If that sort of protection is too much for your needs, just setup your security and account preferences to log out when energy saver and/or screen saver is activated, and automatic log on is disabled. That's pretty good unless a person who steals your machine or has access to your machine has the original discs which came with the Mac, or newer retail operating system (up to the limits of the machine's hardware). So consider how much security you need, and you can ask the system to be that secure.

  • [SOLVED] Using Apple's UEFI boot menu with Arch

    Hello,
          I've successfully installed arch on my mid-2012 (5,1) 11" Macbook Air, and now I'm trying to get an entry in apple's boot menu (the one that shows when you hold 'option' when starting the computer).  From the author of rEFInd's install instructions (http://www.rodsbooks.com/refind/installing.html#osx) it sounds like I can just add some files to `/dev/sda1` (a vfat directory that contains the stuff needed to boot macos), and then run apple's `bless` command and we're good to go.  Unfortunately I've tried this a bunch of different ways, to no avail.  I think some of my failure is simply because of a misunderstanding of UEFI, here are some questions I (partially) don't understand and my current understanding of them:
    1. Do I even need a bootloader on a pure GPT/UEFI system?  It seems like the answer is no, and I can just use the UEFI firmware and the linux kernel to load Arch (per: https://wiki.archlinux.org/index.php/UE … ux_Kernel).  Note: I'd like to have as little software between the firmware and the os, for speed and simplicity.  However, I'd still like to dual boot, but it sounds like the firmware can handle showing me a menu as long as there are entries pointing to parts of each OS.
    2. Will grub/rEFInd/syslinux do some of the work for me initially/on a kernel update?  I think the answer is yes, which would be motivation (esp when I need to update the kernel) to just use a multibootloader and have it handle arch and the firmware pass control to either that or MacOS
    3. Will `efibootmgr` brick my mac?  https://wiki.archlinux.org/index.php/UE … FI_systems says it will, but I think the `grub-install` command uses `efibootmgr`, so should I not try grub on here (this package: https://www.archlinux.org/packages/core … fi-x86_64/ ).  Also some of the other packages (like rEFInd-efi) depend on efibootmgr, so does that mean any kind of an install from them (a command from the package, not the `pacman -S pkg` command) will also brick my system? (see rEFInd-efi dependencies: https://www.archlinux.org/packages/extr … efind-efi/ )
    I've been searching a bunch of different things, output of the `bless` commands I've been running, and have found the following:
    * https://bbs.archlinux.org/viewtopic.php?id=148647
    * Using OSX to install rEFInd manually (moving the files around and using OSXs `bless` command) http://www.rodsbooks.com/refind/installing.html#osx , I used the rEFInd files from Archs repos: https://www.archlinux.org/packages/extr … efind-efi/ )
    * The Wiki docs on rEFInd https://wiki.archlinux.org/index.php/UE … ing_rEFInd
    To summarize, I'm trying to set up a dual boot between MacOS (installed) and Arch (also installed, there's just no way to boot it on my system yet) using Apple's built in menu that deals with the EFI partition on /dev/sda1 .  Thanks in advance for any help!
    end
    Last edited by enduser (2013-03-18 12:00:17)

    enduser wrote:I've successfully installed arch on my mid-2012 (5,1) 11" Macbook Air, and now I'm trying to get an entry in apple's boot menu (the one that shows when you hold 'option' when starting the computer).  From the author of rEFInd's install instructions (http://www.rodsbooks.com/refind/installing.html#osx) it sounds like I can just add some files to `/dev/sda1` (a vfat directory that contains the stuff needed to boot macos), and then run apple's `bless` command and we're good to go.
    Not quite. That makes a boot loader bootable, but it doesn't add an entry to Apple's boot manager menu. There's a blog post somewhere by Matthew Garrett that describes the steps necessary to add something to Apple's boot manager, but I couldn't find it in a quick Web search. Maybe you'll have better luck, or be able to track down the same information somewhere else. As I recall, it involves using a separate HFS+ volume, creating two or three dummy files, and using "bless" in OS X.
    1. Do I even need a bootloader on a pure GPT/UEFI system?
    Yes, you do need a boot loader. It's important to distinguish between a boot loader and a boot manager, though. The former is a program that loads a kernel, and perhaps associated data, into memory and transfers control to the kernel. A boot manager presents a user interface that enables you to select which OS (or which boot loader) to launch. A boot manager is not strictly necessary, and Apple's EFI implementation includes its own simple boot manager, which is what you've been unsuccessful in configuring.
    Note: I'd like to have as little software between the firmware and the os, for speed and simplicity.  However, I'd still like to dual boot, but it sounds like the firmware can handle showing me a menu as long as there are entries pointing to parts of each OS.
    Many people make do with the firmware's own boot manager, but this can be rather inflexible. I'm not even sure if Apple's boot manager can handle passing options to Linux kernels' EFI stub loaders. This ability is not absolutely required, but without it you must compile your options into your kernel at compile time, which greatly reduces flexibility since you can't modify the options on a per-boot basis -- say, to boot into single-user mode if this is required.
    2. Will grub/rEFInd/syslinux do some of the work for me initially/on a kernel update?
    The usual Arch Linux method of handling kernel updates is to overwrite an old kernel with a new one, so no boot loader/boot manager changes are required. If you want to keep numbered kernels around (as most other distributions do), GRUB provides scripts that can help automate changes, but they are required in the grub.cfg file. rEFInd can auto-detect boot loaders, and if you're using the EFI stub loader, that means that the kernel is its own boot loader, and with a proper configuration, rEFInd can detect new kernels without changing its configuration file.
    SYSLINUX has some very early and very experimental EFI support. The one and only time I tried it (about a month ago), it wouldn't compile for me. (I don't know of a precompiled binary available on the Web -- the support is that new!) I don't recommend trying it unless somebody who's gotten it to work offers to help you personally.
    3. Will `efibootmgr` brick my mac?  https://wiki.archlinux.org/index.php/UE … FI_systems says it will, but I think the `grub-install` command uses `efibootmgr`, so should I not try grub on here (this package: https://www.archlinux.org/packages/core … fi-x86_64/ ).
    There were reports of efibootmgr damaging Mac firmware several months ago (I believe over a year ago). Since then I've seen claims that this problem has been fixed with recent kernels (3.0 and later, IIRC), but I've seen no substantiation one way or the other. Overall, I recommend caution....
    Also some of the other packages (like rEFInd-efi) depend on efibootmgr, so does that mean any kind of an install from them (a command from the package, not the `pacman -S pkg` command) will also brick my system? (see rEFInd-efi dependencies: https://www.archlinux.org/packages/extr … efind-efi/ )
    On a Mac, I recommend installing rEFInd (or any other EFI boot loader) from OS X rather than from Linux. (Note that I'm rEFInd's maintainer, so that's an official recommendation from the software's developer.) Offhand, I don't know if the Arch package for rEFInd runs efibootmgr automatically on boot or just has it as a dependency because efibootmgr is the usual way to register a boot loader on UEFI systems. If the latter, it should be safe to install the Arch package for rEFInd, copy its files, and then reboot to OS X to run bless on it. It would be just as easy, if not easier, to install it completely from OS X, though.

  • Dell Vostro New System Questions

    I was looking into purchasing a Dell Vostro system for video editing with the Production Premium.
    I heard that the XPS systems are made more specifically for video editing, but the Vostro I was looking into seems to have comparable specs to an XPS system.
    Here are the main specs:
    Intel Core 2 Quad Proc Q6600 (2.40GHz,8MB L2Cache,1066FSB)
    4 GB DDR2 NON-ECC SDRAM 800MHz (4 DIMMs)
    256MB NVIDIA GeForce 8600M GT
    500 GB SATA Hard Drive (7200 RPM) (I know I may have to add another hd).
    Has anyone had any experiences with the Vostro or would know if this should work well?
    Thanks!

    >Vostro's have (at least mine has) room for only one additional hard drive.
    I'd pass by any prebuilt computer that doesn't allow you to have at least 5 total internal hard drives and two optical drives, or allow you to change out the power supply, or add in or otherwise change the GPU and sound card. Those features are pretty much standard with any decent case, and all prebuilt computers should have such a case.

  • DELL VOSTRO 3750 with Windows 7 64 bit BOSD

    Hello:
    I have been dealing with BSOD for the last 8 months, but my hardware appears fine.  I thought the problem was related to some wrong DELL drivers for my DELL VOSTRO 3750 with Windows 7 64 bit.  Tried for a few months to solve the problem with DELL
    customer service.  My warranty ran out May 31, 2014.  I had DELL come and replace the network card and the fan because I was having overheating issues and some of the indications from the bluescreen messages seemed to point at the network card.  A
    month after warranty ran out, I was still getting BSOD so I tried uninstalling and reinstalling original drivers from DELL.  Worked fine for a couple of months. Then the BSODs came back again everyday or 2.
    Is there anyone in the Microsoft world that can help? 
    https://www.dropbox.com/s/0ze9z2yduzdnh5u/MEMORY.DMP?dl=0
    Really appreciated,
    Tim

    Hi,
    I checked the link again and it still stay unavailable.
    Please recheck and upload the files again.
    For resolving Blue Screen Errors in Widnows 7, please first take a look at the following article:
    Resolving stop (blue screen) errors in Windows 7
    Best regards
    Michael Shao
    TechNet Community Support

  • [Solved] Boot process hangs for installed Arch and installation usb

    Hi. I've been using Arch Linux for around 6 months now and I'm in love with it. It is now my primary OS. However, I might have done something or performed some update, and I can no longer boot into Arch. The boot process hangs right before it should show the login screen (I'm using Gnome 3.6 with GDM). I see the following messages on the screen:
    Loading Linux core repo kernel ...
    Loading initial ramdisk ...
    /dev/sda3: recovering journal
    /dev/sda3: clean, 330610/1749664 files, 5585671/6996827 blocks
    And then it hangs right there. I have to hard-reboot after this.
    I then tried to boot using the Arch Linux Installation USB (archlinux-2012.12.01-dual.img), which also hangs at a particular point, before it should show me the prompt. I took a picture of the screen where it hangs: Screen Capture. This is an issue with just my laptop, because the USB boots just fine on another laptop I tried.
    I also have Windows 7 and Ubuntu 12.10 installed on my system, and I'm able to boot into both of them.
    I have 2 hard drives: /dev/sda is a 120GB SSD, and /dev/sdb is a 500GB hard disk. My partitions are as follows:
    sda1 - Windows 7 100MB System Reserved Partition (boot flag enabled)
    sda2 - Windows 7 OS
    sda3 - ArchLinux (boot flag enabled)
    sdb1 - Ubuntu 12.10 (boot flag enabled)
    sdb2 - Just data
    I ran bootinfoscript and below is the output:
    Boot Info Script 0.61 [1 April 2012]
    ============================= Boot Info Summary: ===============================
    => Grub2 (v1.99) is installed in the MBR of /dev/sda and looks at sector 1 of
    the same hard drive for core.img. core.img is at this location and looks
    in partition 99 for .
    => Grub2 (v1.99) is installed in the MBR of /dev/sdb and looks at sector 1 of
    the same hard drive for core.img. core.img is at this location and looks
    in partition 99 for .
    sda1: __________________________________________________________________________
    File system: ntfs
    Boot sector type: Windows Vista/7: NTFS
    Boot sector info: No errors found in the Boot Parameter Block.
    Operating System:
    Boot files: /bootmgr /Boot/BCD
    sda2: __________________________________________________________________________
    File system: ntfs
    Boot sector type: Windows Vista/7: NTFS
    Boot sector info: No errors found in the Boot Parameter Block.
    Operating System: Windows 7
    Boot files: /Windows/System32/winload.exe
    sda3: __________________________________________________________________________
    File system: ext4
    Boot sector type: -
    Boot sector info:
    Mounting failed: mount: /dev/sda3 already mounted or sda3 busy
    sdb1: __________________________________________________________________________
    File system: ext4
    Boot sector type: -
    Boot sector info:
    Operating System: Ubuntu 12.10
    Boot files: /boot/grub/grub.cfg /etc/fstab
    sdb2: __________________________________________________________________________
    File system: ntfs
    Boot sector type: Windows Vista/7: NTFS
    Boot sector info: No errors found in the Boot Parameter Block.
    Operating System:
    Boot files:
    ============================ Drive/Partition Info: =============================
    Drive: sda _____________________________________________________________________
    Disk /dev/sda: 120.0 GB, 120034123776 bytes
    255 heads, 63 sectors/track, 14593 cylinders, total 234441648 sectors
    Units = sectors of 1 * 512 = 512 bytes
    Sector size (logical/physical): 512 bytes / 512 bytes
    Partition Boot Start Sector End Sector # of Sectors Id System
    /dev/sda1 * 2,048 206,847 204,800 7 NTFS / exFAT / HPFS
    /dev/sda2 206,848 178,466,084 178,259,237 7 NTFS / exFAT / HPFS
    /dev/sda3 * 178,466,085 234,440,703 55,974,619 83 Linux
    Drive: sdb _____________________________________________________________________
    Disk /dev/sdb: 500.1 GB, 500107862016 bytes
    255 heads, 63 sectors/track, 60801 cylinders, total 976773168 sectors
    Units = sectors of 1 * 512 = 512 bytes
    Sector size (logical/physical): 512 bytes / 512 bytes
    Partition Boot Start Sector End Sector # of Sectors Id System
    /dev/sdb1 * 63 20,948,759 20,948,697 83 Linux
    /dev/sdb2 20,964,824 976,771,071 955,806,248 7 NTFS / exFAT / HPFS
    "blkid" output: ________________________________________________________________
    Device UUID TYPE LABEL
    /dev/mmcblk0p1 6665-3162 vfat
    /dev/sda1 CA6A20CC6A20B75B ntfs System Reserved
    /dev/sda2 1EE242D5E242B137 ntfs
    /dev/sda3 65db0c59-9f04-46f1-975d-8a4c28132137 ext4
    /dev/sdb1 bb9818db-ce7c-43a4-8ad5-8d3702001aed ext4
    /dev/sdb2 3C2E3A4E2E3A0206 ntfs
    ================================ Mount points: =================================
    Device Mount_Point Type Options
    /dev/mmcblk0p1 /media/dhaval/6665-3162 vfat (rw,nosuid,nodev,uid=1000,gid=1000,shortname=mixed,dmask=0077,utf8=1,showexec,flush,uhelper=udisks2)
    /dev/sdb1 / ext4 (rw,errors=remount-ro)
    =========================== sdb1/boot/grub/grub.cfg: ===========================
    # DO NOT EDIT THIS FILE
    # It is automatically generated by grub-mkconfig using templates
    # from /etc/grub.d and settings from /etc/default/grub
    ### BEGIN /etc/grub.d/00_header ###
    if [ -s $prefix/grubenv ]; then
    set have_grubenv=true
    load_env
    fi
    set default="0"
    if [ x"${feature_menuentry_id}" = xy ]; then
    menuentry_id_option="--id"
    else
    menuentry_id_option=""
    fi
    export menuentry_id_option
    if [ "${prev_saved_entry}" ]; then
    set saved_entry="${prev_saved_entry}"
    save_env saved_entry
    set prev_saved_entry=
    save_env prev_saved_entry
    set boot_once=true
    fi
    function savedefault {
    if [ -z "${boot_once}" ]; then
    saved_entry="${chosen}"
    save_env saved_entry
    fi
    function recordfail {
    set recordfail=1
    if [ -n "${have_grubenv}" ]; then if [ -z "${boot_once}" ]; then save_env recordfail; fi; fi
    function load_video {
    if [ x$feature_all_video_module = xy ]; then
    insmod all_video
    else
    insmod efi_gop
    insmod efi_uga
    insmod ieee1275_fb
    insmod vbe
    insmod vga
    insmod video_bochs
    insmod video_cirrus
    fi
    if [ x$feature_default_font_path = xy ] ; then
    font=unicode
    else
    insmod part_msdos
    insmod ext2
    set root='hd1,msdos1'
    if [ x$feature_platform_search_hint = xy ]; then
    search --no-floppy --fs-uuid --set=root --hint-bios=hd1,msdos1 --hint-efi=hd1,msdos1 --hint-baremetal=ahci1,msdos1 bb9818db-ce7c-43a4-8ad5-8d3702001aed
    else
    search --no-floppy --fs-uuid --set=root bb9818db-ce7c-43a4-8ad5-8d3702001aed
    fi
    font="/usr/share/grub/unicode.pf2"
    fi
    if loadfont $font ; then
    set gfxmode=auto
    load_video
    insmod gfxterm
    set locale_dir=$prefix/locale
    set lang=en_US
    insmod gettext
    fi
    terminal_output gfxterm
    if [ "${recordfail}" = 1 ]; then
    set timeout=-1
    else
    set timeout=10
    fi
    ### END /etc/grub.d/00_header ###
    ### BEGIN /etc/grub.d/05_debian_theme ###
    set menu_color_normal=white/black
    set menu_color_highlight=black/light-gray
    if background_color 13,37,73; then
    clear
    fi
    ### END /etc/grub.d/05_debian_theme ###
    ### BEGIN /etc/grub.d/10_linux ###
    function gfxmode {
    set gfxpayload="${1}"
    if [ "${1}" = "keep" ]; then
    set vt_handoff=vt.handoff=7
    else
    set vt_handoff=
    fi
    if [ "${recordfail}" != 1 ]; then
    if [ -e ${prefix}/gfxblacklist.txt ]; then
    if hwmatch ${prefix}/gfxblacklist.txt 3; then
    if [ ${match} = 0 ]; then
    set linux_gfx_mode=keep
    else
    set linux_gfx_mode=text
    fi
    else
    set linux_gfx_mode=text
    fi
    else
    set linux_gfx_mode=keep
    fi
    else
    set linux_gfx_mode=text
    fi
    export linux_gfx_mode
    if [ "${linux_gfx_mode}" != "text" ]; then load_video; fi
    menuentry 'Ubuntu' --class ubuntu --class gnu-linux --class gnu --class os $menuentry_id_option 'gnulinux-simple-bb9818db-ce7c-43a4-8ad5-8d3702001aed' {
    recordfail
    gfxmode $linux_gfx_mode
    insmod gzio
    insmod part_msdos
    insmod ext2
    set root='hd1,msdos1'
    if [ x$feature_platform_search_hint = xy ]; then
    search --no-floppy --fs-uuid --set=root --hint-bios=hd1,msdos1 --hint-efi=hd1,msdos1 --hint-baremetal=ahci1,msdos1 bb9818db-ce7c-43a4-8ad5-8d3702001aed
    else
    search --no-floppy --fs-uuid --set=root bb9818db-ce7c-43a4-8ad5-8d3702001aed
    fi
    linux /boot/vmlinuz-3.5.0-21-generic root=UUID=bb9818db-ce7c-43a4-8ad5-8d3702001aed ro quiet splash acpi_osi=Linux acpi_backlight=vendor $vt_handoff
    initrd /boot/initrd.img-3.5.0-21-generic
    submenu 'Advanced options for Ubuntu' $menuentry_id_option 'gnulinux-advanced-bb9818db-ce7c-43a4-8ad5-8d3702001aed' {
    menuentry 'Ubuntu, with Linux 3.5.0-21-generic' --class ubuntu --class gnu-linux --class gnu --class os $menuentry_id_option 'gnulinux-3.5.0-21-generic-advanced-bb9818db-ce7c-43a4-8ad5-8d3702001aed' {
    recordfail
    gfxmode $linux_gfx_mode
    insmod gzio
    insmod part_msdos
    insmod ext2
    set root='hd1,msdos1'
    if [ x$feature_platform_search_hint = xy ]; then
    search --no-floppy --fs-uuid --set=root --hint-bios=hd1,msdos1 --hint-efi=hd1,msdos1 --hint-baremetal=ahci1,msdos1 bb9818db-ce7c-43a4-8ad5-8d3702001aed
    else
    search --no-floppy --fs-uuid --set=root bb9818db-ce7c-43a4-8ad5-8d3702001aed
    fi
    echo 'Loading Linux 3.5.0-21-generic ...'
    linux /boot/vmlinuz-3.5.0-21-generic root=UUID=bb9818db-ce7c-43a4-8ad5-8d3702001aed ro quiet splash acpi_osi=Linux acpi_backlight=vendor $vt_handoff
    echo 'Loading initial ramdisk ...'
    initrd /boot/initrd.img-3.5.0-21-generic
    menuentry 'Ubuntu, with Linux 3.5.0-21-generic (recovery mode)' --class ubuntu --class gnu-linux --class gnu --class os $menuentry_id_option 'gnulinux-3.5.0-21-generic-recovery-bb9818db-ce7c-43a4-8ad5-8d3702001aed' {
    recordfail
    insmod gzio
    insmod part_msdos
    insmod ext2
    set root='hd1,msdos1'
    if [ x$feature_platform_search_hint = xy ]; then
    search --no-floppy --fs-uuid --set=root --hint-bios=hd1,msdos1 --hint-efi=hd1,msdos1 --hint-baremetal=ahci1,msdos1 bb9818db-ce7c-43a4-8ad5-8d3702001aed
    else
    search --no-floppy --fs-uuid --set=root bb9818db-ce7c-43a4-8ad5-8d3702001aed
    fi
    echo 'Loading Linux 3.5.0-21-generic ...'
    linux /boot/vmlinuz-3.5.0-21-generic root=UUID=bb9818db-ce7c-43a4-8ad5-8d3702001aed ro recovery nomodeset
    echo 'Loading initial ramdisk ...'
    initrd /boot/initrd.img-3.5.0-21-generic
    menuentry 'Ubuntu, with Linux 3.2.0-29-generic' --class ubuntu --class gnu-linux --class gnu --class os $menuentry_id_option 'gnulinux-3.2.0-29-generic-advanced-bb9818db-ce7c-43a4-8ad5-8d3702001aed' {
    recordfail
    gfxmode $linux_gfx_mode
    insmod gzio
    insmod part_msdos
    insmod ext2
    set root='hd1,msdos1'
    if [ x$feature_platform_search_hint = xy ]; then
    search --no-floppy --fs-uuid --set=root --hint-bios=hd1,msdos1 --hint-efi=hd1,msdos1 --hint-baremetal=ahci1,msdos1 bb9818db-ce7c-43a4-8ad5-8d3702001aed
    else
    search --no-floppy --fs-uuid --set=root bb9818db-ce7c-43a4-8ad5-8d3702001aed
    fi
    echo 'Loading Linux 3.2.0-29-generic ...'
    linux /boot/vmlinuz-3.2.0-29-generic root=UUID=bb9818db-ce7c-43a4-8ad5-8d3702001aed ro quiet splash acpi_osi=Linux acpi_backlight=vendor $vt_handoff
    echo 'Loading initial ramdisk ...'
    initrd /boot/initrd.img-3.2.0-29-generic
    menuentry 'Ubuntu, with Linux 3.2.0-29-generic (recovery mode)' --class ubuntu --class gnu-linux --class gnu --class os $menuentry_id_option 'gnulinux-3.2.0-29-generic-recovery-bb9818db-ce7c-43a4-8ad5-8d3702001aed' {
    recordfail
    insmod gzio
    insmod part_msdos
    insmod ext2
    set root='hd1,msdos1'
    if [ x$feature_platform_search_hint = xy ]; then
    search --no-floppy --fs-uuid --set=root --hint-bios=hd1,msdos1 --hint-efi=hd1,msdos1 --hint-baremetal=ahci1,msdos1 bb9818db-ce7c-43a4-8ad5-8d3702001aed
    else
    search --no-floppy --fs-uuid --set=root bb9818db-ce7c-43a4-8ad5-8d3702001aed
    fi
    echo 'Loading Linux 3.2.0-29-generic ...'
    linux /boot/vmlinuz-3.2.0-29-generic root=UUID=bb9818db-ce7c-43a4-8ad5-8d3702001aed ro recovery nomodeset
    echo 'Loading initial ramdisk ...'
    initrd /boot/initrd.img-3.2.0-29-generic
    ### END /etc/grub.d/10_linux ###
    ### BEGIN /etc/grub.d/20_linux_xen ###
    ### END /etc/grub.d/20_linux_xen ###
    ### BEGIN /etc/grub.d/20_memtest86+ ###
    menuentry "Memory test (memtest86+)" {
    insmod part_msdos
    insmod ext2
    set root='hd1,msdos1'
    if [ x$feature_platform_search_hint = xy ]; then
    search --no-floppy --fs-uuid --set=root --hint-bios=hd1,msdos1 --hint-efi=hd1,msdos1 --hint-baremetal=ahci1,msdos1 bb9818db-ce7c-43a4-8ad5-8d3702001aed
    else
    search --no-floppy --fs-uuid --set=root bb9818db-ce7c-43a4-8ad5-8d3702001aed
    fi
    linux16 /boot/memtest86+.bin
    menuentry "Memory test (memtest86+, serial console 115200)" {
    insmod part_msdos
    insmod ext2
    set root='hd1,msdos1'
    if [ x$feature_platform_search_hint = xy ]; then
    search --no-floppy --fs-uuid --set=root --hint-bios=hd1,msdos1 --hint-efi=hd1,msdos1 --hint-baremetal=ahci1,msdos1 bb9818db-ce7c-43a4-8ad5-8d3702001aed
    else
    search --no-floppy --fs-uuid --set=root bb9818db-ce7c-43a4-8ad5-8d3702001aed
    fi
    linux16 /boot/memtest86+.bin console=ttyS0,115200n8
    ### END /etc/grub.d/20_memtest86+ ###
    ### BEGIN /etc/grub.d/30_os-prober ###
    menuentry 'Windows 7 (loader) (on /dev/sda1)' --class windows --class os $menuentry_id_option 'osprober-chain-CA6A20CC6A20B75B' {
    insmod part_msdos
    insmod ntfs
    set root='hd0,msdos1'
    if [ x$feature_platform_search_hint = xy ]; then
    search --no-floppy --fs-uuid --set=root --hint-bios=hd0,msdos1 --hint-efi=hd0,msdos1 --hint-baremetal=ahci0,msdos1 CA6A20CC6A20B75B
    else
    search --no-floppy --fs-uuid --set=root CA6A20CC6A20B75B
    fi
    chainloader +1
    ### END /etc/grub.d/30_os-prober ###
    ### BEGIN /etc/grub.d/30_uefi-firmware ###
    ### END /etc/grub.d/30_uefi-firmware ###
    ### BEGIN /etc/grub.d/40_custom ###
    # This file provides an easy way to add custom menu entries. Simply type the
    # menu entries you want to add after this comment. Be careful not to change
    # the 'exec tail' line above.
    ### END /etc/grub.d/40_custom ###
    ### BEGIN /etc/grub.d/41_custom ###
    if [ -f ${config_directory}/custom.cfg ]; then
    source ${config_directory}/custom.cfg
    elif [ -z "${config_directory}" -a -f $prefix/custom.cfg ]; then
    source $prefix/custom.cfg;
    fi
    ### END /etc/grub.d/41_custom ###
    =============================== sdb1/etc/fstab: ================================
    # /etc/fstab: static file system information.
    # Use 'blkid' to print the universally unique identifier for a
    # device; this may be used with UUID= as a more robust way to name devices
    # that works even if disks are added and removed. See fstab(5).
    # <file system> <mount point> <type> <options> <dump> <pass>
    proc /proc proc nodev,noexec,nosuid 0 0
    # / was on /dev/sdb1 during installation
    UUID=bb9818db-ce7c-43a4-8ad5-8d3702001aed / ext4 errors=remount-ro 0 1
    =================== sdb1: Location of files loaded by Grub: ====================
    GiB - GB File Fragment(s)
    4.564525127 = 4.901121536 boot/grub/grub.cfg 1
    5.130507946 = 5.508840960 boot/initrd.img-3.2.0-29-generic 2
    5.851592541 = 6.283099648 boot/initrd.img-3.5.0-21-generic 2
    6.317649364 = 6.783524352 boot/vmlinuz-3.2.0-29-generic 1
    4.965751171 = 5.331934720 boot/vmlinuz-3.5.0-21-generic 2
    5.851592541 = 6.283099648 initrd.img 2
    5.851592541 = 6.283099648 initrd.img.old 2
    4.965751171 = 5.331934720 vmlinuz 2
    4.965751171 = 5.331934720 vmlinuz.old 2
    I tried adding nomodeset and acpi=off to the boot parameters, but the boot process still hangs. Please let me know if I should provide any other information.
    Last edited by dhavalparmar (2012-12-30 11:45:25)

    Ok.. So my Arch Linux randomly decided to work. I'm sure I didn't do anything between my last "not working" state and my current "working" state. Below are a few things I tried:
    I thought of trying an earlier build of ArchLinux, and downloaded archlinux-2012.11.01-dual.iso and made a bootable USB out of it. It still hung.
    I was getting error messages during Arch boot that the last access time for the disks was at a future date. I found out that Ubuntu was using localtime instead of UTC and screwing up my hardware clock. I fixed it, and thought maybe the time issues were causing the boot problem. But fixing time didn't solve my problem.
    I chrooted into Arch from my Ubuntu install, ran 'sudo pacman -Syyu' and updated my Arch install.
    I thought maybe GDM isn't starting up. I re-enabled the service using 'systemctl enable gdm.service'.
    I removed OpenNTPd and installed NTPd. Enabled the daemon using 'systemctl enable ntpd'
    None of the above solved the problem, and rebooting to Arch still hung the system. So I stopped fiddling with it yesterday. Today, as usual, I just tried logging into Arch.. And it just worked out of the blue. The solution to me is as mysterious as the problem.
    I told this to my friend who introduced me to Arch, and this is what he said:
    Damn it computers, you were supposed to be deterministic!

  • [SOLVED] Imapd does not start (only during boot process)

    I'm running a courier-imap server.
    A few days ago I noticed I did not receive any mails anymore. Then I found my imapd daemon was not running anymore.
    I then stopped the daemon process together with the xinetd daemon (which lets me connect to my imap server via my local network).
    I restart from a terminal both daemons (imapd an xinetd) and ... everything is up and running ! Note that I have to stop xinetd too because only stopping imapd and restarting doesn't help.
    I reboot my PC ... again no imapd anymore. During the boot process I do not get any error message though ...
    I'm completely puzzled
    The problem started when I upgraded to the linux 3.0.1 kernel ...
    Last edited by Strider (2011-08-14 07:59:41)

    I managed to get the problem solved by removing and re-installing the courier-imap package. Don't know why that solved it though ...
    Last edited by Strider (2011-08-14 07:59:05)

  • Dell Vostro 1400 laptop will not boot Zen imaging

    Got a new Dell Vostro 1400 laptop today to find it has problems with
    ZENworks imaging.
    I can pxe boot the laptop and it will attempt to install the imaging
    software from
    the server but fail and present me with the Linuxrc screen.
    Navigating through the options results in a DHCP configuration failed
    error.
    Can anyone point me in the right direction?
    Is there a hotfix available?
    thanks.
    zen_padawan

    zendude;2862314 Wrote:
    > Try to load the driver tg3.ko and see if it works with this driver and
    > you boot from the cd (pxe will not work because you can't get out of
    > linuxrc, actually you might be able to do it, but I found the menu to
    > be really confusing. Go It looks like is a broadcom 59xx series.>
    Code:
    > > # modprobe tg3
    > >
    > If the driver tg3 works then you need to add the newid option in the
    > append section of the isolinux.cfg or linuxrc.config. Check the
    > forums for more info about newid option.
    I have loaded this driver and added the newid=0x14e4 0x1713 but still
    no luck. Still can not ping the Zenworks server or do anything. The
    Network lights stay lit when it tries to obtain an IP address for eth0.
    I read on another site that you need to update the initrd with the new
    tg3.ko driver. I will try this later tonight and see what happens.
    Cheers
    Chadinsky

  • Hi, can iMovie give pronlems during the boot process from my iMac Mine. I have often after working with iMovie that i get during the boot Psi SDXH pause so the boot process stops

    hi,
    can iMovie give problems during the boot process from my iMac Mini?
    I have often, after working with iMovie that i get during the boot Psi SDXH pause
    so the boot process stops at this point
    I have often reinstall OSX Mavericks
    regards,
    HenkfromWinterswijk
    Netherlands

    Hello Federico,
    Your EliteBook is a Business model.  Your issue would be best answered on the HP Enterprise Business Community Forum
    Good luck!
    ↙-----------How do I give Kudos?| How do I mark a post as Solved? ----------------↓

  • New P7N SLI Platinum Boot Issue with PS/2 Keyboard [Solved but RAID problem now]

    This issue taken me back !!!! Never thought I might face issue with a PS/2 Keyboard.
    Here it is.. I just assembled my new system...
    P7N SLI Platinum Motherboard
    E8400 CPU
    EVGA 256-P2-N751-TR GeForce 8600 GT Video Card
    Creative Soundblaster Audio Card
    So, before I boot, I connected good old PS/2 Keyboard. The POST Screen comes up that says Press DEL to enter BIOS Setup... but then, it reboots.. indefinitely... I have no idea why it does that. However, if I boot the PC with no PS/2 Keyboard connected, POST screen comes up and that's it.. (no reboot). So, you see, I cannot proceed further in anyway.... I cannot go beyond POST without a keyboard, but then with the keyboard it reboots indefinitely... kinda catch 22 situation
    Any suggestion / ideas that anyone can offer here???

    Hello Folks... it took long time to "solve the issue that had to begin with"....
    I purchased a cheapo Celeron processor to get into  the BIOS and update it... but it didn't even work... I couldn't boot at all. So, I called MSI and they asked me to RMA it. They replaced my MOBO with the latest BIOS - which was good news
    So, now, I'm able to boot  - good news...
    Now, this is an upgrade for me.... from my previous MOBO. My boot drive was RAIDed (RAID 0). So, now, I will have to RAID my drives again and run Win XP repair. I was able to RAID my drives and all good... now, I went into Windows installation and did F6 to install NVIDIA Raid.... but, here is my problem, when the prompt asks me to input the floppy drive, and when I did it.... it re-prompts me to put the floppy drive again... I see that the floppy drive is read... but, for some reason it doesn't detect the files in there properly....  I downloaded nVidia C72+MCP55 SATA RAID / AHCI Driver (For floppy driver) for windows xp 32-bit and copied the sataraid folder contents into the floppy. Now, here I am stuck again....
    Anybody experienced this problem?

  • There is always a blue screen appears after the Apple logo during the booting process. And then everything is back to normal. What is this thing? Is there something wrong with my screen or something?

    There is always a blue screen appears after the Apple logo during the booting process. And then everything is back to normal. What is this thing? Is there something wrong with my screen or something?

    Nah - that's just the normal boot process.
    Clinton

  • [Solved/Broken DPM] Hang at boot when switching modes with radeon

    When I tried to boot into Arch about a week ago after cleaning some dust out of my case I was met with a nasty surprise, it wouldn't boot properly! Once my system got to the point where it would usually change resolutions (KMS kicks in) my displays (1 DVI, 1 DVI -> VGA) would just shut off (presumably not getting any signal from my GPU a Radeon 5770) and either my keyboards lights (caps/scroll/num) would either be stuck on or be able to be toggled but I don't believe anything was happening in the boot process.
    Now me being the inquisitive kind of guy I decided I would be right on the case and ignore Arch until I got bored. I tried out an old Ubuntu 12.04 based distro and everything worked fine, but that's no way to live so I decided to install Debian testing. The install went fine, everything was happy, and I even made it to a tty! But during the boot I noticed a message saying I didn't have the non-free firmware I'd need for my GPU, so I installed that and rebooted.
    Much to my pleasure the same issue didn't happen! Instead of only (presumably) locking up my GPU fans were going very fast and loud blowing a bit of extra dust out of my case for me. How convenient! At this point I decided the problem was probably the fault of the firmware, but why did it just start happening now? Perhaps I updated my system before I opened it up; I don't remember if that is the case or not however.
    Anyways, Debian testing was a bust so I decided I'd reinstall Arch, so I booted up my trusty flash drive and.... the same thing happened. While I considered the possibility of hardware failure, Windows works the same as it always has and the old distro didn't have any issues aside from generally being old and terrible and my computer is yet to catch on fire. I also ran a small memory test to make sure everything seemed normal enough.
    tl;dr Boot fails when KMS initiates (?) / Hardware seems fine / Maybe a problem with new kernel or firmware
    Anyone else have issues or a solution?
    EDIT: Disabling DPM fixed my issues, but of course I don't have dpm now
    Last edited by jmad980 (2014-07-28 10:07:25)

    You can try building the kernel from git. There is an AUR package.
    Or try the drm-fixes-3.16 branch from git://people.freedesktop.org/~agd5f/linux (http://cgit.freedesktop.org/~agd5f/linux/)
    For me (HD6870) it fixes the power management. But i had other symptoms: https://bugzilla.kernel.org/show_bug.cgi?id=68571

Maybe you are looking for