I'm using syslinux for my bootloader. I'm using BIOS, not UEFI, on a 32-bit system. After updating syslinux 5.10-3 -> 6.01-1 the modules' symlinks in /boot/syslinux didn't get updated and still point to /usr/lib/syslinux/ instead of to /usr/lib/syslinux/bios e.g. menu.c32 -> /usr/lib/syslinux/menu.c32 which prevents the syslinux menu from appearing on boot (modules not found). Running '# /usr/bin/syslinux-install_update -i -a -m' doesn't help.
Should I remove all the symlinks from /boot/syslinux and only copy the needed files back? I didn't install syslinux manually so i don't know why should I have to do this. Did I miss / misunderstand something?
Am 05.07.2013 20:24, schrieb Karol Blazewicz:
I'm using syslinux for my bootloader. I'm using BIOS, not UEFI, on a 32-bit system. After updating syslinux 5.10-3 -> 6.01-1 the modules' symlinks in /boot/syslinux didn't get updated and still point to /usr/lib/syslinux/ instead of to /usr/lib/syslinux/bios e.g. menu.c32 -> /usr/lib/syslinux/menu.c32 which prevents the syslinux menu from appearing on boot (modules not found). Running '# /usr/bin/syslinux-install_update -i -a -m' doesn't help.
Should I remove all the symlinks from /boot/syslinux and only copy the needed files back? I didn't install syslinux manually so i don't know why should I have to do this. Did I miss / misunderstand something?
The install script needs an update. Just remove the .c32 and ln -s /usr/lib/syslinux/bios/*.c32 .
On Fri, 05 Jul 2013 20:26:53 +0200, Thomas Bächler wrote:
Am 05.07.2013 20:24, schrieb Karol Blazewicz:
I'm using syslinux for my bootloader. I'm using BIOS, not UEFI, on a 32-bit system. After updating syslinux 5.10-3 -> 6.01-1 the modules' symlinks in /boot/syslinux didn't get updated and still point to /usr/lib/syslinux/ instead of to /usr/lib/syslinux/bios e.g. menu.c32 -> /usr/lib/syslinux/menu.c32 which prevents the syslinux menu from appearing on boot (modules not found). Running '# /usr/bin/syslinux-install_update -i -a -m' doesn't help.
Should I remove all the symlinks from /boot/syslinux and only copy the needed files back? I didn't install syslinux manually so i don't know why should I have to do this. Did I miss / misunderstand something?
The install script needs an update. Just remove the .c32 and ln -s /usr/lib/syslinux/bios/*.c32 .
And if you have a custom syslinux.cfg, you need to restore than from syslinux.cfg.pacsave.
So many ways to break your boot ....
On Fri, Jul 5, 2013 at 8:26 PM, Thomas Bächler thomas@archlinux.org wrote:
Am 05.07.2013 20:24, schrieb Karol Blazewicz:
I'm using syslinux for my bootloader. I'm using BIOS, not UEFI, on a 32-bit system. After updating syslinux 5.10-3 -> 6.01-1 the modules' symlinks in /boot/syslinux didn't get updated and still point to /usr/lib/syslinux/ instead of to /usr/lib/syslinux/bios e.g. menu.c32 -> /usr/lib/syslinux/menu.c32 which prevents the syslinux menu from appearing on boot (modules not found). Running '# /usr/bin/syslinux-install_update -i -a -m' doesn't help.
Should I remove all the symlinks from /boot/syslinux and only copy the needed files back? I didn't install syslinux manually so i don't know why should I have to do this. Did I miss / misunderstand something?
The install script needs an update. Just remove the .c32 and ln -s /usr/lib/syslinux/bios/*.c32 .
Thanks for a very fast answer :-) Should I open a bug report? If you don't plan on fixing it immediately, please post a message on arch-dev-public, because not everyone is reading arch-general even though this seems to be only an annoyance, not a system-breaking bug.
Am 05.07.2013 21:22, schrieb Karol Blazewicz:
Should I open a bug report? If you don't plan on fixing it immediately, please post a message on arch-dev-public, because not everyone is reading arch-general even though this seems to be only an annoyance, not a system-breaking bug.
This should be fixed before it moves to core. It is already being worked on.
On Fri, Jul 5, 2013 at 9:26 PM, Thomas Bächler thomas@archlinux.org wrote:
Am 05.07.2013 21:22, schrieb Karol Blazewicz:
Should I open a bug report? If you don't plan on fixing it immediately, please post a message on arch-dev-public, because not everyone is reading arch-general even though this seems to be only an annoyance, not a system-breaking bug.
This should be fixed before it moves to core. It is already being worked on.
I meant the message on arch-dev-public as a heads-up for other [testing] users :-)
BTW, I thought I just fscked something up with my syslinux config during the update, but I now see what happened https://projects.archlinux.org/svntogit/packages.git/commit/trunk?h=packages... ;P
On 5 July 2013 23:56, Thomas Bächler thomas@archlinux.org wrote:
Am 05.07.2013 20:24, schrieb Karol Blazewicz:
I'm using syslinux for my bootloader. I'm using BIOS, not UEFI, on a 32-bit system. After updating syslinux 5.10-3 -> 6.01-1 the modules' symlinks in /boot/syslinux didn't get updated and still point to /usr/lib/syslinux/ instead of to /usr/lib/syslinux/bios e.g. menu.c32 -> /usr/lib/syslinux/menu.c32 which prevents the syslinux menu from appearing on boot (modules not found). Running '# /usr/bin/syslinux-install_update -i -a -m' doesn't help.
Should I remove all the symlinks from /boot/syslinux and only copy the needed files back? I didn't install syslinux manually so i don't know why should I have to do this. Did I miss / misunderstand something?
The install script needs an update. Just remove the .c32 and ln -s /usr/lib/syslinux/bios/*.c32 .
I have uploaded the* *updated syslinux-install_update script to https://gist.github.com/the-ridikulus-rat/5940114 . Please check it. You can check the changes made by going to https://gist.github.com/the-ridikulus-rat/5940114/revisions .
Best Regards.
Keshav Padram
Am 05.07.2013 20:46, schrieb Jonathan Hudson:
And if you have a custom syslinux.cfg, you need to restore than from syslinux.cfg.pacsave.
So many ways to break your boot ....
That has already been fixed.
On 6 July 2013 20:21, Keshav Padram the.ridikulus.rat@gmail.com wrote:
On 5 July 2013 23:56, Thomas Bächler thomas@archlinux.org wrote:
Am 05.07.2013 20:24, schrieb Karol Blazewicz:
I'm using syslinux for my bootloader. I'm using BIOS, not UEFI, on a 32-bit system. After updating syslinux 5.10-3 -> 6.01-1 the modules' symlinks in /boot/syslinux didn't get updated and still point to /usr/lib/syslinux/ instead of to /usr/lib/syslinux/bios e.g. menu.c32 -> /usr/lib/syslinux/menu.c32 which prevents the syslinux menu from appearing on boot (modules not found). Running '# /usr/bin/syslinux-install_update -i -a -m' doesn't help.
Should I remove all the symlinks from /boot/syslinux and only copy the needed files back? I didn't install syslinux manually so i don't know why should I have to do this. Did I miss / misunderstand something?
The install script needs an update. Just remove the .c32 and ln -s /usr/lib/syslinux/bios/*.c32 .
I have uploaded the* *updated syslinux-install_update script to https://gist.github.com/the-ridikulus-rat/5940114 . Please check it. You can check the changes made by going to https://gist.github.com/the-ridikulus-rat/5940114/revisions .
Best Regards.
Keshav Padram
I have made the changes pyther has mentioned at https://mailman.archlinux.org/pipermail/arch-general/2013-July/033769.html in my script at https://gist.github.com/the-ridikulus-rat/5940114 .
Best Regards.
Keshav Padram
arch-general@lists.archlinux.org