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)
O' rly ? Ya rly Oo
I hadn't gotten around to checking the syslinux.cfg.pacnew file, so I've been using the old one. One of the interesting differences between them is in the INITRD line:
So it appears to me that cybertorture's observations could be related.
Last edited by skottish (2012-02-11 03:22:03)
Still having this issue, but i found out it's only on cold boot. Not that much of a problem since i usually suspend anyway...
I have this on my netbook with pretty much every syslinux and/or kernel version. I chalked it up to being another of the many, many quirks of this crazy machine and switched to grub because of it. Boot hangs, I turn off the machine and immediately turn it back on, boot works. Initramfs or no initramfs (using a custom kernel that doesn't require it), doesn't make a difference. Interesting to know I'm not the only one being hit by this.