Syslinux 4.05-1 + linux 3.2.5-1 = no boot

Just as a warning to others: i just had a non-booting system with syslinux 4.05-1 and linux 3.2.5-1, hanging on the syslinux line right after it tries to load the initramfs. I had to chroot in to fix. I'm in a bit of a hurry today so i didn't check out which one is at fault, but downgrading both fixed things.

core/linux 3.2.5-1 (base) [installed]
core/syslinux 4.05-1 [installed]
Everythig works booth on i686 and x64
funny thing is that i can not find any changelog for 4.05 but still problem may lay in type of boot partition maybe?
btw syslinux do not update boot image file "ldlinux.sys" so ehn you update you still use old one.
edit: i found out that updating that file make it appear in /boot rather than old place /boot/syslinux so a little edit on path will be required.
Last edited by cybertorture (2012-02-09 16:20:26)

Similar Messages

After Linux installation my notebook can not boot up properly

OK so I installed Linux ubunto and I was double booting with my standard version of Win when me and my friend tried to just go back to Windows we restored it back to the original with the backup disk only problem is that now the program (GRUB) that loads when you choose your operating system is still on the computer.
It gives me an error 22 message every time... I was told I need to reset the master boot record or something like that but I do not know how so if someone plz could help me?
That would be greatly appreciated!

Your MBR (Master Boot Record) contains GRUB loader. You must recover its original contents.
For win95/98/me you use "fdisk /mbr" with a startup disk.
With win2000/xp you boot into the recovery console using the installation CD and type fixmbr
Albert

Oracle Linux 6.1 guest fails to boot on VM 3.0.2

Hi,
I've been using the templates to create vm guests successfully, so time to push the boundary again!
I've created a Linux 6.1 PVM guest and, after a little trial and error to get the install boot working, I managed to run through the Linux install process. I then changed the boot in VM Manger to remove the Network boot option and restarted the VM guest and it failed to start. I checked the ovs-agent.log on the server and it has this error message.
failed (1): Error: (2, 'Invalid kernel', "elf_xen_note_check: ERROR: Not a Xen-ELF image: No ELF notes or '__xen_guest' section found.")
I'm not sure if its relevant but the grub.conf file looks like this:
title Oracle VM Server-ovs (xen-4.0.0 2.6.32.21-38ovs)
root (hd0,0)
kernel /xen.gz dom0_mem=544M
module /vmlinuz-2.6.32.21-38xen ro root=UUID=32f4fe8e-cc96-43db-9125-4097ec18024d
module /initrd-2.6.32.21-38xen.img
title Oracle VM Server-ovs serial console (xen-4.0.0 2.6.32.21-38ovs)
root (hd0,0)
kernel /xen.gz console=com1,vga com1=57600,8n1 dom0_mem=544M
module /vmlinuz-2.6.32.21-38xen ro root=UUID=32f4fe8e-cc96-43db-9125-4097ec18024d console=tty0 console=ttyS0,57600n8
module /initrd-2.6.32.21-38xen.img
Has anyone got ideas why it is failing for me ?
Thanks

Mark C wrote:
I've created a Linux 6.1 PVM guest and, after a little trial and error to get the install boot working, I managed to run through the Linux install process. I then changed the boot in VM Manger to remove the Network boot option and restarted the VM guest and it failed to start. I checked the ovs-agent.log on the server and it has this error message.That's the grub.conf from your Oracle VM Server, not from your guest. If it's from your guest, you installed Oracle VM, not Oracle Linux 6.

Installing Arch Linux on USB key: error while booting

Hello,
first of all, I must say I've followed the steps from this article on arch wiki to install archlinux on my USB key: https://wiki.archlinux.org/index.php/In … _a_USB_key
So what I did is to use one of my 2 usb keys to INSTALL linux, and the second one to RUN linux. I used dd to write on the 1st usb, eveything worked fine when booting, then I do install arch on the my second usb following the stept from the link above, everything works until I get this error while booting (at the middle):
Waiting 10 seconds for device /dev/sdc/
Root device '/dev/sdc' doesn't exist. Attempting to create it.
ERROR: Unable to determine major/minor number of root device '/dev/disk/by-uuid/lotsofnumbers'
You are being dropped to a recovery shell
Type 'exit' to try and continue booting
/bin/sh: Can't contact tty; job control turned off
[ramfs /]#
To summarize I'll show you my conf files that could help you to resolve my problem:
/etc/fstab.conf
/dev/sdc1 /boot ext2 defaults 0 1
/dev/sdc2 / ext3 defaults 0 1
/dev/sdc3 /home ext3 defaults 0 1
So here I've sdc1 boot 32MB partition; sdc2 root 3GB partition; sdc3 home 978MB partition for a total of 4GB USB key~
I didn't make a swap partition as in the tutorial they are writing it's unnecessary for some kind of reasons.
/etc/mkinitcpio.conf
HOOKS="base udev usb autodetect pata scsi sata filesystems"
I've added to here, "usb" to the hooks
installed GRUB on my sdc, here is the menu.ist:
# (0) Arch Linux
title Arch Linux (USB)
root (hd0,0)
kernel /vmlinuz26 root=/dev/sdc ro vga=773
initrd /kernel26.img
So, I boot GRUB without problems, start Arch Linux, but then I got this error above.
I've searched alot on some forums and read many stuffs, but sitll can't fix it and it seems complicated.
I've tried to boot with UUID, also, but didn't make difference. I tried to remove some parameter from the hooks, but unfortunately this wasn't working still. I've read somewhere to use chroot, but I didn't catch on how to do that and what was the use of chroot, I'm still noob user of arch linux and currently learning. Maybe it's the problem, as some forum were talking about creating a new image, but I still don't know how to make it. By the way, I'm not sure this could have fixed my current problem. I've also read somewhere it could be due to my lack of space, but I wrote you how I did partition my USB key, let me know if you have any suggestion please.

1. What I did is re-installing entirely from my installation disk or USB to test out different setting in my config files, because I don't know how to edit my .conf as I can't really finish to boot to the end and get in terminal mode? If there is a quicker way to edit files from any terminal to go into my current USB sdc to modify directly my file from there, I'd enjoy probably. So rebuilding the initpio, no, I just re-installed to test out different configs.
2. Yes, same error.
3. Tested out by-id/by-path and uuid = no difference
4. Didn't know about larch, it seems to be a nice tool, I'll check it out

[SOLVED]Arch Linux, and Windows 8.1 Dual Boot issue

Hi guys. I recently bought a new laptop, and decided to run Arch Linux and Windows 8.1. I installed Windows 8.1 first as recommended by the beginners guide, and then installed Arch Linux. I made sure UEFI was enabled in my BIOS, and made sure everything was on a GPT partition. The install itself went fine. My laptop loads grub, and Arch Linux shows up and boots, but there is no option to boot into Windows 8.1. The only way I can boot into Windows 8.1 is by accessing my motherboard, and choosing to launch the windows boot manager instead of the grub launcher. How can I get Windows 8.1 to show up in grub? Thanks in advance guys.
Last edited by Painguy (2014-08-20 20:19:37)

Painguy wrote:
-----------Edit------------------
Yeah just ran this after installing os prober
grub-mkconfig -o /boot/grub/grub.cfg
and it works now. Sorry for the crazy posts guys. Thanks for the suggestions and help.
Yeah I'm sure I'm doing something wrong lol. I did not install OS-Prober. I think that's where the issue is. I'm missing the menu entry in grub.cfg right? Do I just run os prober or do I have to manually edit grub.cfg.
If that's not the case then here is what I did up until now. What I did was start with a blank SSD drive. I used cgdisk to make the disk use a GPT partitioning scheme. I installed windows 8.1 and checked in windows to make sure it boots into UEFI-GPT mode and it does. I then installed arch linux using the beginners guide. I made sure to use cgdisk to create any extra partitions, and installed GRUB to the efi partition that windows had created ( I did not format this partition ). I then finished the installation and rebooted, and Grub only shows arch linux. I don't think I'm dealing with anything MBR related. I made sure I used the GPT partitioning scheme....i think lol.
All you need to do is run os-prober then run grub-mkconfig. It should pick up Windows at that point.

How to install Linux from a distro instead of booting a live cd?

Suppose you have Arch Linux installed in sda and you want to install a new copy in sdc, can you do it from your distro instead of booting with the installation cd?
Here's my sdc (75 GB):
/dev/sdc1 ntfs 100 MB
/dev/sdc2 ntfs 40 GB
those partitions are used by Windows 7, so there's another 35 GB for Linux.
Now here's the the problem: this latest Arch Linux install media is kinda complicated because it does not provide the AIF anymore. Also, the installation method differs a little from the old ones. Until 2011.08.19 I would partition the remaining space like this:
/dev/sdc3 extended 35 GB
/dev/sdc5 ext2 100 MB /boot
/dev/sdc6 swap 1 GB swap
/dev/sdc7 ext4 15 GB /
/dev/sdc8 ext4 19 GB /home
However this guide http://ebalaskas.gr/wiki/archlinux/netinstall shows a different (suposedly recommended) partition table for the new method.
So,
1) Is it possible to install Arch Linux from an already installed distro, including GRUB2?
2) Is it possible to use the partiton table style I provided?
And how to do it of course.
Thanks!

Check this article out
https://wiki.archlinux.org/index.php/In … ting_Linux
Note that it says it is out of date because of pacman. Really all you need to know is that pacman uses signed packages now, so it is now necessary to run the pacman-key stuff. Or set SigLevel = Never in pacman.conf
Edit: IMHO the first method is preferred because it more closely resembles a regular install. Ergo, you will be able to semi follow the beginners guide for config and such.
Last edited by WonderWoofy (2012-08-17 03:42:12)

Oracle Linux VM setting time wrong on boot

I have a newly built Oracle Linux 5.7 vm running on OVM 3.0.3. Every time it boots the clock goes back 6 hours. I have the vm set up to use ntp which is successfully getting time from ntp pool servers. The OVM servers are configured to get their time from OVM manager.
I am in Eastern time which is 5 hours behind UTC so I don't think it is confusion between EST and UTC since the clock is losing 6 hours.
The OVM users guide advises to set "xen.independent_wallclock = 1" in /etc/sysctl.conf, but does not specify if this is done on the OVM servers or the guest vms. I have it set this way in both environments right now, but this behavior remains the same whether the setting is 0 or 1.
The Linux guest has been fully updated from ULN and has the oracle-validated packages installed.
The oracle-validated package updated the kernel boot parameters to include "clocksource=pit nohpet noptimer".
Any ideas?
Thx

I was confused, too, until I set BIOS clocks (RTC) on my 2 servers to UTC time and installed both servers with "Server uses UTC" option enabled and same timezone, during OVM setup.
Also make sure OVM manager has correct RTC, time zone, utc settings BEFORE starting up OVM servers, as this also might get you in trouble.
To ensure bios clock (RTC) is set corretly on OVM servers, do - after tweaking /dev/rtc ("ln -s /dev/rtc0 /dev/rtc" in 3.0.3) make sure you have correct system time on server and issue "hwclock --systohc".
When everything is fine (at the end) you should configure/check ntpd is running everywhere - check this link http://blogs.oracle.com/virtualization/entry/configuring_ntp_services_for_oracle.
If even after this you will experience trouble with domU times- configure nptd also in all domUs, but remember to first set in every domU independence of dom0 time - "echo 1 > /proc/sys/xen/independent_wallclock".
:j

Linux-based Live-CDs Not Booting

I have Toshiba Satellite M45-S169 that known good (working in other computers) Live-CDs will not boot. While other Live Cd's will boot on the Toshiba laptop. Has anyone found a fix for this?
CloneZilla Live-CD will not boot on the Toshiba, but does on other computers.
SystemRescueCD Live-CD will not boot on the Toshiba, but will on other computers
Bart-PE Windows XP Live-CD Boots on the Toshiba, and other computers.
All of these CDs are Linux-based, which may or may not mean anything. The one that works on the Toshiba is the oldest, so maybe it has to do with what basic Linux Kernel is being used.
I really want to get CloneZilla to work on this so I can make a backup image. The version of CloneZilla is their i486 one that claims to run on any i386 processor.
The Toshiba has Windows XP-Home with Service Pack 3. It works well, but would feel better if I had a backup. It has an Intel Celeron M processor reported to be 1.60 GHz with 1.43 GB RAM.
Thanks,
Jim

Jerry,
Thanks for the reply - you are correct; I was mistaken about Bart-PE. Don't know what I was thinking.
I have worked around my Linux problem by installing Marium Reflect. I wanted a way to create a backup image of the Toshiba C: drive and believed CloneZilla or other Linux-based software was the only answer. But found the Reflect free edition that worked. So my ultimate goal is achieved (without getting Linux to boot). I now have a saved image of the hard disk and Win-PE based rescue disk that can be used to restore that image. I feel safer now. Hopefully I will never need it.
It is disappointing that Linux wont run on this computer. I might investigate that further when I have the time. I just found another tool that wont run on this computer - Speccy from Piriform.

Windows 8 is not booting when i tried to install Debain (Linux) . Now no OS can boot

Error showing " No bootable device-- insert boot disk and press any key " . and when i am inserting bootable usb drive then again error " disk error press any key to restart". I tried one more option that i put recovery file in bootable use so after that some option are comming to refresh and restore windows 8 but . I can't get my window back error is bit locker key. but i never put any security key on windows drive( C: ) , but they are asking bit locker key...

Hello KnackJ,
I see that while trying to install Linux, you've lost the Windows 8 OS that was on your notebook.
As you're getting an error with bit locker key, I would recommend contacting support for further assistance with this issue.
HP Technical Support, North America 1-800-474-6836. For all other regions click here.
Thank you for posting on the HP Forums.
I worked on behalf of HP.

Linode with latest Arch Linux never brings networking online at boot?

Hello, I use Linode for my primary VPS related stuff. On it, I usually use Arch Linux. Recently however, I've faced a pretty big issue. If I spin up a new linode, do a pacman -Syu and then reboot it, it will not setup networking when it starts up.
I have to manually login with their Lish out-of-band access to login and start networking manually (ie, by doing dhcpcd eth0). I've filed a support ticket with them, but they said it was basically out of their control and pointed me here. I've never had this issue until recently.
I've already tried setting up netctl and such for defaults, but it still ends up with no DHCP lease upon boot, and I'm not sure why. Anyone know of this issue and/or how to fix it?

I had this same issue. I fixed it by (via Lish) systemctl enabling and starting dhcpcd.service, and (if that didn't fix ssh) restarting sshd.service.
I also found this interesting:
[root@sandbox ~]# cat /usr/lib/systemd/network/10-dhcp.network
[Match]
Name=eth0
[Network]
DHCP=yes
Is networkd supposed to be handling network configuration, and if so, shouldn't that be "ef*" rather than eth0?
Is there a better solution that should be put in place to fix this? How does Arch normally do DHCP on Ethernet right now?
Last edited by STUART (2014-08-05 12:23:04)

Installing Linux, but keeping windows for VM boot?

Hello,
I'm thinking about buying a new thinkpad. I'd like to install linux and wide the recovery partition, but I'd also like to be able to make a Virtual Box vm from the licence of windows 7 that comes with purchase.
Does anybody know if that will be possible from the recovery cds?
Thanks

jdonato wrote:
Hello,
I'm thinking about buying a new thinkpad. I'd like to install linux and wide the recovery partition, but I'd also like to be able to make a Virtual Box vm from the licence of windows 7 that comes with purchase.
Does anybody know if that will be possible from the recovery cds?
If you mean using recovery cd's in a virtual machine? It wont work that way since the they check for a BIOS identifier during the first boot.
Cheers and regards,
• » νιנαｿѕαяα∂нι ѕαмανє∂αм ™ « •
●๋•کáŕádhí'ک díáŕý ツ
I am a volunteer here. I don't work for Lenovo

Installing Arch Linux after Windows 7 64bit dual boot

Total noob here ^^
Im trying to install Arch Linux after my installation of Windows 7, without fucking up that one...
I freed up 50GB and removed it from my Windows boot partition, so Arch can be installed there, I have almost absolutely no experience with this kind of stuff since I've only used Ubuntu and Kali Linux before.
I've got a working arch image on my usb stick and i somehow can't figure out, how to install it without touching the existing partitions.
Is it possible to create a working dual boot, without changing my windows configuration?

yes its possible. What research have you done in order to install Arch. We do not hand hold here in this community. Go read up the appropriate wiki pages and ask specific questions with details in case you get stuck.
Start with the Beginners Guide.

Arch linux installed on LVM won't boot

My hard disk has only 1 partition.
I created 1 volume group and 1 logical volume on it.
my fstab looks like this:
# /etc/fstab: static file system information
# <file system> <dir> <type> <options> <dump> <pass>
tmpfs /tmp tmpfs nodev,nosuid 0 0
# UUID=7e4cc742-0eda-4a69-8357-4b769cd51520
/dev/mapper/vg000-lv000 / ext4 rw,relatime,data=ordered 0 2
I configured /etc/mkinitcpio.conf as following and ran mkinitcpio -p linux again:
MODULES="dm_mod"
HOOKS="base udev usb lvm2 filesystems"
After installation, I rebooted the system, selected the 1st entry in grub menu, the screen shows:
Loading Linux core repo kernel ...
Loading initial ramdisk ...
then the following errors occured:
ERROR:device '/dev/mapper/vg000-lv000' not found. Skipping fsck.
ERROR:Unable to find root device 'dev/mapper/vg000-lv000'
Could anybody please help?
PS: I then rebooted to arch-linux using cd, I noticed that /dev/mapper/vg000-lv000 was not there. I had to use vgchange -ay vg000 to make it appear. Could this be related to the ERRORS?
Last edited by whudwl (2012-11-23 08:14:47)

Is your hard disk attached via usb? If not, you did not have the proper modules for the intramfs to access the hard disk itself. You had it set up so that it could boot from a usb device, but not an internal device. You should have read the comments for each of those examples. It explains pretty cearly what each example would be used for.
Edit: I use lvm and my mkinitcpio.conf HOOKS line looks like this:
HOOKS="base udev autodetect sata lvm2 filesystems fsck timestamp"
My SSD's are connected via SATA III, the lvm2 hook is obvious, the filesystems load the ext4 module (all filesystems are ext4), fsck adds fsck and fsck.ext4, timestamp makes 'systemd-analyze' able to tell you how long it takes the initramfs and kernel to load individually instead of together. base should always be there, and first (unless you really really know what you are doing), udev adds... udev, and autodetect tries its best to strip everything you don't need for your particular system.
For info on a paritcular hook, use the -H option with mkinitcpio. (ie. 'mkinipcio -H lvm2'). There is also a fantasticlly informative wiki page about mkinitcpio.
Last edited by WonderWoofy (2012-11-26 03:44:40)

[SOLVED] Cannot boot with linux-3.5.3

Edit: Solved, as explained here.
Hello,
after upgrading to linux-3.5.3-1 my boot stopped at
:: running early hook [udev]
I tried upgrading to grub-bios-2.00, removing any customization I had in modprobe.conf and /etc/modules-load.d as well as removing the only module (radeon) from /etc/mkinitcpio.conf (obviously followed by mkinitcpio -p linux), which made me go on to
:: waiting for udev uevents to be processed [BUSY]
I'm not sure it's an actual progress.
My /etc/udev/rules.d is empty and /usr/lib/udev/rules.d only contains pacman-tracked stuff.
I enabled some debugging as described here but couldn't get anything useful - is there any way for such messages to be logged somewhere, so they can be pasted here?
I ended up downgrading to linux-3.4.9, which boots fine.
Any idea to troubleshoot this?
cat /etc/rc.conf
# /etc/rc.conf - configuration file for initscripts
# Most of rc.conf has been replaced by various other configuration
# files. See archlinux(7) for details.
# For more details on rc.conf see rc.conf(5).
DAEMONS=(!hwclock ntpd syslog-ng !network netfs crond dbus @networkmanager kdm @cpufreq sshd @cups @supervisor)
# Storage
# USEDMRAID="no"
# USELVM="no"
# Network
# interface=
# address=
# netmask=
# gateway=
cat /etc/mkinitcpio.conf
# vim:set ft=sh
# MODULES
# The following modules are loaded before any boot hooks are
# run. Advanced users may wish to specify all system modules
# in this array. For instance:
# MODULES="piix ide_disk reiserfs"
MODULES=""
# BINARIES
# This setting includes any additional binaries a given user may
# wish into the CPIO image. This is run last, so it may be used to
# override the actual binaries included by a given hook
# BINARIES are dependency parsed, so you may safely ignore libraries
BINARIES=""
# FILES
# This setting is similar to BINARIES above, however, files are added
# as-is and are not parsed in any way. This is useful for config files.
# Some users may wish to include modprobe.conf for custom module options
# like so:
# FILES="/etc/modprobe.d/modprobe.conf"
FILES=""
# HOOKS
# This is the most important setting in this file. The HOOKS control the
# modules and scripts added to the image, and what happens at boot time.
# Order is important, and it is recommended that you do not change the
# order in which HOOKS are added. Run 'mkinitcpio -H <hook name>' for
# help on a given hook.
# 'base' is _required_ unless you know precisely what you are doing.
# 'udev' is _required_ in order to automatically load modules
# 'filesystems' is _required_ unless you specify your fs modules in MODULES
# Examples:
## This setup specifies all modules in the MODULES setting above.
## No raid, lvm2, or encrypted root is needed.
# HOOKS="base"
## This setup will autodetect all modules for your system and should
## work as a sane default
# HOOKS="base udev autodetect pata scsi sata filesystems"
## This is identical to the above, except the old ide subsystem is
## used for IDE devices instead of the new pata subsystem.
# HOOKS="base udev autodetect ide scsi sata filesystems"
## This setup will generate a 'full' image which supports most systems.
## No autodetection is done.
# HOOKS="base udev pata scsi sata usb filesystems"
## This setup assembles a pata mdadm array with an encrypted root FS.
## Note: See 'mkinitcpio -H mdadm' for more information on raid devices.
# HOOKS="base udev pata mdadm encrypt filesystems"
## This setup loads an lvm2 volume group on a usb device.
# HOOKS="base udev usb lvm2 filesystems"
## NOTE: If you have /usr on a separate partition, you MUST include the
# usr, fsck and shutdown hooks.
HOOKS="base udev autodetect pata scsi sata resume filesystems usbinput fsck"
# COMPRESSION
# Use this to compress the initramfs image. By default, gzip compression
# is used. Use 'cat' to create an uncompressed image.
#COMPRESSION="gzip"
#COMPRESSION="bzip2"
#COMPRESSION="lzma"
#COMPRESSION="xz"
#COMPRESSION="lzop"
# COMPRESSION_OPTIONS
# Additional options for the compressor
#COMPRESSION_OPTIONS=""
pacman -Qo /usr/lib/udev/rules.d/*
/usr/lib/udev/rules.d/10-dm.rules is owned by device-mapper 2.02.97-1
/usr/lib/udev/rules.d/10-vboxdrv.rules is owned by virtualbox 4.1.20-2
/usr/lib/udev/rules.d/11-dm-lvm.rules is owned by lvm2 2.02.97-1
/usr/lib/udev/rules.d/13-dm-disk.rules is owned by device-mapper 2.02.97-1
/usr/lib/udev/rules.d/40-gphoto.rules is owned by libgphoto2 2.4.14-1
/usr/lib/udev/rules.d/40-hpet-permissions.rules is owned by jack2 1.9.8-2
/usr/lib/udev/rules.d/40-usb-media-players.rules is owned by media-player-info 17-1
/usr/lib/udev/rules.d/42-usb-hid-pm.rules is owned by systemd-tools 188-2
/usr/lib/udev/rules.d/50-udev-default.rules is owned by systemd-tools 188-2
/usr/lib/udev/rules.d/53-sane.rules is owned by sane 1.0.23-1
/usr/lib/udev/rules.d/60-cdrom_id.rules is owned by systemd-tools 188-2
/usr/lib/udev/rules.d/60-pcmcia.rules is owned by pcmciautils 018-4
/usr/lib/udev/rules.d/60-persistent-alsa.rules is owned by systemd-tools 188-2
/usr/lib/udev/rules.d/60-persistent-input.rules is owned by systemd-tools 188-2
/usr/lib/udev/rules.d/60-persistent-serial.rules is owned by systemd-tools 188-2
/usr/lib/udev/rules.d/60-persistent-storage-tape.rules is owned by systemd-tools 188-2
/usr/lib/udev/rules.d/60-persistent-storage.rules is owned by systemd-tools 188-2
/usr/lib/udev/rules.d/60-persistent-v4l.rules is owned by systemd-tools 188-2
/usr/lib/udev/rules.d/60-rfkill.rules is owned by rfkill 0.4-5
/usr/lib/udev/rules.d/61-accelerometer.rules is owned by systemd-tools 188-2
/usr/lib/udev/rules.d/61-gnome-bluetooth-rfkill.rules is owned by gnome-bluetooth 3.4.2-1
/usr/lib/udev/rules.d/64-md-raid.rules is owned by mdadm 3.2.5-2
/usr/lib/udev/rules.d/65-kvm.rules is owned by qemu 1.1.1-1
/usr/lib/udev/rules.d/69-cd-sensors.rules is owned by colord 0.1.21-2
/usr/lib/udev/rules.d/69-libmtp.rules is owned by libmtp 1.1.4-1
/usr/lib/udev/rules.d/70-infrared.rules is owned by v4l-utils 0.8.8-1
/usr/lib/udev/rules.d/70-power-switch.rules is owned by systemd-tools 188-2
/usr/lib/udev/rules.d/70-uaccess.rules is owned by systemd-tools 188-2
/usr/lib/udev/rules.d/70-udev-acl.rules is owned by consolekit 0.4.6-4
/usr/lib/udev/rules.d/71-seat.rules is owned by systemd-tools 188-2
/usr/lib/udev/rules.d/73-seat-late.rules is owned by systemd-tools 188-2
/usr/lib/udev/rules.d/75-net-description.rules is owned by systemd-tools 188-2
/usr/lib/udev/rules.d/75-probe_mtd.rules is owned by systemd-tools 188-2
/usr/lib/udev/rules.d/75-tty-description.rules is owned by systemd-tools 188-2
/usr/lib/udev/rules.d/77-nm-olpc-mesh.rules is owned by networkmanager 0.9.4.0-6
/usr/lib/udev/rules.d/78-sound-card.rules is owned by systemd-tools 188-2
/usr/lib/udev/rules.d/80-drivers.rules is owned by systemd-tools 188-2
/usr/lib/udev/rules.d/80-udisks.rules is owned by udisks 1.0.4-5
/usr/lib/udev/rules.d/80-udisks2.rules is owned by udisks2 1.94.0-2
/usr/lib/udev/rules.d/85-usbmuxd.rules is owned by usbmuxd 1.0.8-1
/usr/lib/udev/rules.d/90-alsa-restore.rules is owned by alsa-utils 1.0.25-3
/usr/lib/udev/rules.d/90-libgpod.rules is owned by libgpod 0.8.2-6
/usr/lib/udev/rules.d/90-pulseaudio.rules is owned by pulseaudio 2.1-1
/usr/lib/udev/rules.d/95-cd-devices.rules is owned by colord 0.1.21-2
/usr/lib/udev/rules.d/95-dm-notify.rules is owned by device-mapper 2.02.97-1
/usr/lib/udev/rules.d/95-keyboard-force-release.rules is owned by systemd-tools 188-2
/usr/lib/udev/rules.d/95-keymap.rules is owned by systemd-tools 188-2
/usr/lib/udev/rules.d/95-udev-late.rules is owned by systemd-tools 188-2
/usr/lib/udev/rules.d/95-upower-battery-recall-dell.rules is owned by upower 0.9.17-2
/usr/lib/udev/rules.d/95-upower-battery-recall-fujitsu.rules is owned by upower 0.9.17-2
/usr/lib/udev/rules.d/95-upower-battery-recall-gateway.rules is owned by upower 0.9.17-2
/usr/lib/udev/rules.d/95-upower-battery-recall-ibm.rules is owned by upower 0.9.17-2
/usr/lib/udev/rules.d/95-upower-battery-recall-lenovo.rules is owned by upower 0.9.17-2
/usr/lib/udev/rules.d/95-upower-battery-recall-toshiba.rules is owned by upower 0.9.17-2
/usr/lib/udev/rules.d/95-upower-csr.rules is owned by upower 0.9.17-2
/usr/lib/udev/rules.d/95-upower-hid.rules is owned by upower 0.9.17-2
/usr/lib/udev/rules.d/95-upower-wup.rules is owned by upower 0.9.17-2
/usr/lib/udev/rules.d/97-bluetooth-hid2hci.rules is owned by bluez 4.101-1
/usr/lib/udev/rules.d/99-systemd.rules is owned by systemd-tools 188-2
cat /var/log/pacman.log
[2012-08-28 12:27] Running 'pacman -Sy'
[2012-08-28 12:27] synchronizing package lists
[2012-08-28 14:51] Running 'pacman -S -u'
[2012-08-28 14:51] starting full system upgrade
[2012-08-28 14:53] upgraded gc (7.2.c-1 -> 7.2.d-1)
[2012-08-28 14:53] >>> Updating module dependencies. Please wait ...
[2012-08-28 14:53] >>> Generating initial ramdisk, using mkinitcpio. Please wait...
[2012-08-28 14:53] ==> Building image from preset: 'default'
[2012-08-28 14:53] -> -k /boot/vmlinuz-linux -c /etc/mkinitcpio.conf -g /boot/initramfs-linux.img
[2012-08-28 14:53] ==> Starting build: 3.5.3-1-ARCH
[2012-08-28 14:53] -> Running build hook: [base]
[2012-08-28 14:53] -> Running build hook: [udev]
[2012-08-28 14:53] -> Running build hook: [autodetect]
[2012-08-28 14:53] -> Running build hook: [pata]
[2012-08-28 14:53] -> Running build hook: [scsi]
[2012-08-28 14:53] -> Running build hook: [sata]
[2012-08-28 14:53] -> Running build hook: [resume]
[2012-08-28 14:53] -> Running build hook: [filesystems]
[2012-08-28 14:53] -> Running build hook: [usbinput]
[2012-08-28 14:53] -> Running build hook: [fsck]
[2012-08-28 14:53] ==> Generating module dependencies
[2012-08-28 14:53] ==> Creating gzip initcpio image: /boot/initramfs-linux.img
[2012-08-28 14:53] ==> Image generation successful
[2012-08-28 14:53] ==> Building image from preset: 'fallback'
[2012-08-28 14:53] -> -k /boot/vmlinuz-linux -c /etc/mkinitcpio.conf -g /boot/initramfs-linux-fallback.img -S autodetect
[2012-08-28 14:53] ==> Starting build: 3.5.3-1-ARCH
[2012-08-28 14:53] -> Running build hook: [base]
[2012-08-28 14:53] -> Running build hook: [udev]
[2012-08-28 14:53] -> Running build hook: [pata]
[2012-08-28 14:53] -> Running build hook: [scsi]
[2012-08-28 14:53] -> Running build hook: [sata]
[2012-08-28 14:53] -> Running build hook: [resume]
[2012-08-28 14:53] -> Running build hook: [filesystems]
[2012-08-28 14:53] -> Running build hook: [usbinput]
[2012-08-28 14:53] -> Running build hook: [fsck]
[2012-08-28 14:53] ==> Generating module dependencies
[2012-08-28 14:53] ==> Creating gzip initcpio image: /boot/initramfs-linux-fallback.img
[2012-08-28 14:53] ==> Image generation successful
[2012-08-28 14:53] upgraded linux (3.4.9-1 -> 3.5.3-1)
[2012-08-28 14:53] upgraded lirc-utils (1:0.9.0-22 -> 1:0.9.0-26)
[2012-08-28 14:53] In order to use the new version, reload all virtualbox modules manually.
[2012-08-28 14:53] upgraded virtualbox-modules (4.1.20-1 -> 4.1.20-3)
[2012-08-28 14:59] Running 'pacman -U /tmp/yaourt-tmp-dp/PKGDEST.3fb/google-chrome-21.0.1180.81-1-x86_64.pkg.tar.xz'
[2012-08-28 14:59] upgraded google-chrome (21.0.1180.57-1 -> 21.0.1180.81-1)
[2012-08-28 15:00] Running 'pacman -U /tmp/yaourt-tmp-dp/PKGDEST.MgI/tunlr-0.1.5-1-any.pkg.tar.xz'
[2012-08-28 15:00] Running 'pacman -Sy'
[2012-08-28 15:00] synchronizing package lists
[2012-08-28 15:01] Running 'pacman -U /tmp/yaourt-tmp-dp/PKGDEST.Vic/tunlr-0.1.5-1-any.pkg.tar.xz'
[2012-08-28 15:01] upgraded tunlr (0.1.4-1 -> 0.1.5-1)
[2012-08-28 17:34] Running 'pacman -S extra/kdeedu-kmplot'
[2012-08-28 17:34] installed kdeedu-kmplot (4.9.0-1)
[2012-08-29 10:20] Running 'pacman -Syu'
[2012-08-29 10:20] synchronizing package lists
[2012-08-29 10:20] starting full system upgrade
[2012-08-29 11:07] Running 'pacman -S grub-bios'
[2012-08-29 11:07] removed grub (0.97-21)
[2012-08-29 11:07] Generating grub.cfg.example config file...
[2012-08-29 11:07] This may fail on some machines running a custom kernel.
[2012-08-29 11:08] done.
[2012-08-29 11:08] installed grub-common (2.00-1)
[2012-08-29 11:08] installed grub-bios (2.00-1)
[2012-08-29 11:48] Running 'pacman -Sy'
[2012-08-29 11:48] synchronizing package lists
[2012-08-29 11:48] starting full system upgrade
[2012-08-29 12:11] Running 'pacman -Sy'
[2012-08-29 12:11] synchronizing package lists
[2012-08-29 12:11] starting full system upgrade
[2012-08-29 12:11] Running 'pacman -S -u'
[2012-08-29 12:11] starting full system upgrade
[2012-08-29 12:15] upgraded firefox (14.0.1-1 -> 15.0-1)
[2012-08-29 12:15] upgraded firefox-i18n-it (14.0.1-1 -> 15.0-1)
[2012-08-29 12:15] upgraded gsmartcontrol (0.8.7-1 -> 0.8.7-2)
[2012-08-29 12:15] upgraded libwbclient (3.6.7-1 -> 3.6.7-2)
[2012-08-29 12:15] upgraded smbclient (3.6.7-1 -> 3.6.7-2)
[2012-08-29 12:15] upgraded samba (3.6.7-1 -> 3.6.7-2)
[2012-08-29 12:15] upgraded sane (1.0.22-9 -> 1.0.23-1)
[2012-08-29 12:15] upgraded syslinux (4.05-6 -> 4.05-7)
[2012-08-29 12:15] upgraded thunderbird (14.0-1 -> 15.0-1)
[2012-08-29 12:15] upgraded thunderbird-i18n-it (14.0-1 -> 15.0-1)
[2012-08-29 12:15] -> You can now set custom file descriptor ulimits for Tor in
[2012-08-29 12:15] -> "/etc/conf.d/tor" using the "TOR_MAX_FD" variable.
[2012-08-29 12:15] upgraded tor (0.2.2.37-1 -> 0.2.2.38-1)
[2012-08-29 12:56] Running 'pacman -U /tmp/yaourt-tmp-root/PKGDEST.K10/downgrade-3.0-1-any.pkg.tar.xz'
[2012-08-29 12:56] installed downgrade (3.0-1)
[2012-08-29 12:57] Running 'pacman -U /var/cache/pacman/pkg/linux-3.4.9-1-x86_64.pkg.tar.xz'
[2012-08-29 13:04] Running 'pacman -U /var/cache/pacman/pkg/virtualbox-modules-4.1.20-1-x86_64.pkg.tar.xz'
[2012-08-29 13:05] Running 'pacman -U /var/cache/pacman/pkg/linux-3.4.9-1-x86_64.pkg.tar.xz'
[2012-08-29 13:05] Running 'pacman -R virtualbox-modules'
[2012-08-29 13:05] Running 'pacman -Rd virtualbox-modules'
[2012-08-29 13:05] Running 'pacman -Rdd virtualbox-modules'
[2012-08-29 13:06] removed virtualbox-modules (4.1.20-3)
[2012-08-29 13:06] Running 'pacman -U /var/cache/pacman/pkg/linux-3.4.9-1-x86_64.pkg.tar.xz'
[2012-08-29 13:06] >>> Updating module dependencies. Please wait ...
[2012-08-29 13:06] >>> Generating initial ramdisk, using mkinitcpio. Please wait...
[2012-08-29 13:06] ==> Building image from preset: 'default'
[2012-08-29 13:06] -> -k /boot/vmlinuz-linux -c /etc/mkinitcpio.conf -g /boot/initramfs-linux.img
[2012-08-29 13:06] ==> Starting build: 3.4.9-1-ARCH
[2012-08-29 13:06] -> Running build hook: [base]
[2012-08-29 13:06] -> Running build hook: [udev]
[2012-08-29 13:06] -> Running build hook: [autodetect]
[2012-08-29 13:06] -> Running build hook: [pata]
[2012-08-29 13:06] -> Running build hook: [scsi]
[2012-08-29 13:06] -> Running build hook: [sata]
[2012-08-29 13:06] -> Running build hook: [resume]
[2012-08-29 13:06] -> Running build hook: [filesystems]
[2012-08-29 13:06] -> Running build hook: [usbinput]
[2012-08-29 13:06] -> Running build hook: [fsck]
[2012-08-29 13:06] ==> Generating module dependencies
[2012-08-29 13:06] ==> Creating gzip initcpio image: /boot/initramfs-linux.img
[2012-08-29 13:06] ==> Image generation successful
[2012-08-29 13:06] ==> Building image from preset: 'fallback'
[2012-08-29 13:06] -> -k /boot/vmlinuz-linux -c /etc/mkinitcpio.conf -g /boot/initramfs-linux-fallback.img -S autodetect
[2012-08-29 13:06] ==> Starting build: 3.4.9-1-ARCH
[2012-08-29 13:06] -> Running build hook: [base]
[2012-08-29 13:06] -> Running build hook: [udev]
[2012-08-29 13:06] -> Running build hook: [pata]
[2012-08-29 13:06] -> Running build hook: [scsi]
[2012-08-29 13:07] -> Running build hook: [sata]
[2012-08-29 13:07] -> Running build hook: [resume]
[2012-08-29 13:07] -> Running build hook: [filesystems]
[2012-08-29 13:07] -> Running build hook: [usbinput]
[2012-08-29 13:07] -> Running build hook: [fsck]
[2012-08-29 13:07] ==> Generating module dependencies
[2012-08-29 13:07] ==> Creating gzip initcpio image: /boot/initramfs-linux-fallback.img
[2012-08-29 13:07] ==> Image generation successful
[2012-08-29 13:07] upgraded linux (3.5.3-1 -> 3.4.9-1)
[2012-08-29 14:47] Running 'pacman -Sy'
[2012-08-29 14:47] synchronizing package lists
[2012-08-29 14:49] Running 'pacman -S -u'
[2012-08-29 14:49] starting full system upgrade
Last edited by thujone (2012-09-19 12:18:51)

because the report opener said that those freezes fixed with the 'futex' patch (included in 3.14-5).
As he says:
for those who have again problems despite the patch it means probably that there are another bugs further in the source code of kernel 3.14, bugs who are not necessarily related to the "futex problem"
i will try a clean profile, thanks.
Last edited by tritonas00 (2014-04-16 13:22:51)

[SOLVED] How to dual boot windows on separate drive with syslinux

I'm trying to follow the directions from the arch syslinux wiki to add a windows dual boot option to my current syslinux.
I have two hard drives: sda (windows MBR) and sdc (arch linux GPT). My BIOS is set to boot sdc, and syslinux is currently installed fine to boot arch linux off of sdc. I would like to add an entry to boot windows.
I added an entry to /boot/syslinux/syslinux.cfg that looks like
LABEL windows
MENU LABEL Windows
COM32 chain.c32
APPEND mbr:0xf00f1fd3 # my actual identifier for sda from fdisk is here
When I rebooted, I saw the new entry in the syslinux menu. When I went to arch linux, it booted fine. When I rebooted again and selected windows, it hung with a blinking underscore. The next time I rebooted, it didn't even get to the syslinux menu and just hung with a blinking underscore.
I booted from my rescue arch usb drive. In fdisk, sdc's partition table now mirrored sda's! In other words, it looked like I had windows partitions on my linux drive, and it had the same MBR identifier even though it was supposed to be GPT. I ran gdisk /dev/sdc, it detected both GPT and MBR, and I asked it to use the GPT table and wrote out the partitions, and my drive looked normal again. I ran arch-chroot, syslinux-install_update, and everything was fine the next time I booted.
Any advice on how I can set up windows dual boot with syslinux?
Last edited by mikemintz (2013-08-17 18:25:46)

I am assuming that you use Bios and not UEFI (I am not that quite familiar with UEFI).
1) You must configure the Bios to boot from the disk where syslinux is installed, having a correct mbr and with syslinux correctly installed.
2) The disk where windows reside must be bootable by itself with a valid mbr.
It may be possible that windows try to boot from the linux disk (and of course fails), try to add the swap option to the chain command.
To check if Windows is correctly installed, try to boot it directly from the Bios.
The mbr of the syslinux disk should be gptmbr.bin:
dd if=/usr/lib/syslinux/gptmbr.bin of=/dev/sd<letter of the linux disk> bs=440 count=1
Warning: Be very careful with what you do with dd, it is very easy to destroy all your data!
Last edited by olive (2013-08-17 08:31:44)

Syslinux 4.05-1 + linux 3.2.5-1 = no boot

Similar Messages

Maybe you are looking for