FS#35750 - [syslinux] serial console support seems broken
Attached to Project:
Arch Linux
Opened by Dave Reisner (falconindy) - Monday, 10 June 2013, 23:28 GMT
Last edited by Gerardo Exequiel Pozzi (djgera) - Wednesday, 10 July 2013, 22:01 GMT
Opened by Dave Reisner (falconindy) - Monday, 10 June 2013, 23:28 GMT
Last edited by Gerardo Exequiel Pozzi (djgera) - Wednesday, 10 July 2013, 22:01 GMT
|
Details
Seems like serial console no longer works with 5.10. The
menu doesn't display, but after the timeout it uses the
default option to boot from. Downgrading to 5.01 and
rewriting the bootloader restores the expected behavior.
/boot/syslinux/syslinux.cfg attached. |
This task depends upon
Closed by Gerardo Exequiel Pozzi (djgera)
Wednesday, 10 July 2013, 22:01 GMT
Reason for closing: Fixed
Additional comments about closing: 5.11-pre1
Wednesday, 10 July 2013, 22:01 GMT
Reason for closing: Fixed
Additional comments about closing: 5.11-pre1
I don't really understand this. I was aware of the PXE problems, but extlinux hasn't been affected until now. I've been using 5.01 happily on my VMs since it hit [testing].
> Do you test on the same "hardware"?
I've not changed the configuration of any of my VMs -- I'm using a launcher script which ensures that: https://github.com/falconindy/bin-scripts/blob/master/qinit
> Also please test with old qemu, qemu-1.5.0 is a bit buggy.
I've had zero problems with qemu-1.5.0. qemu-1.4.1 with syslinux 5.10 shows the exact same problem (no menu). Really, this needs bisecting in syslinux.
Yes, this is also broken for me in 5.10, while 5.01 (and 5.02-preX) works good. I hit this issue due testing archiso with new syslinux-5.10 using qemu-1.5.0. If you look at git-log of syslinux you can see some fixed around serial-console code.
When I question about hardware is about if you run on the same "hardware" as me (qemu), not if you made some updates/changes to your hardware.
What I tried to say was, that I forgot to report the problem to the serial console, because I gave a lot more importance to the problem with PXE, as I was waiting since 5.02-preX for another version to see if it improved. (but of course this is totally unrelated to this report)
I think we both misunderstood. No worries, all makes sense now. Do you have a link to the upstream bug report/ML post?