F17 -> F18 upgrade with fedup cannot boot

[phavar]

I have just finished the update with the fedup utility (it took about 1 hour).
After the laptop was rebooted, I selected the following entry from the GRUB menu: 3.7.2-201.fc18x86_64

After selecting the aforementioned kernel there was an error/warning about dracut-cmdline[65] and some deprecated commands (KEYTABLE, SYSFONT).

Unfortunately the laptop could not boot and the capslk indicator was blinking !!!!

In order to boot the machine I had no other option but to select the FC17 kernel from the GRUB menu.

Can you help me with that? What is going wrong with the FC18 kernel?[COLOR="Silver"]

---------- Post added at 09:38 PM ---------- Previous post was at 08:39 PM ----------

The aforementioned FC17 kernel is : 3.6.11-1.fc17.x86_64. In order to understand what is going wrong, is it possible to start the kernel in text mode?

[rickfoosusa]

Having the same problem on a libvirt kvm. Fedup succeeds, boot kernel selected.

Two warning messages:
dracut-cmdline [66]: Warning: Kernel command line option 'KEYTABLE' is deprecated

dracut-cmdline[66]: Warning: Kernel command line option 'SYSFONT' is deprecated

----
I had this bug in my fedup
https://github.com/omeid/fedup/commit/2687ba2
global name po not defined

SOLVED:
1) Stop boot, and boot single user mode.
1a) Edit fedup/callback.py per above bug fix.
2) Start netwoking manually. /etc/init.d/network start
3) fedup --network 18 --debuglog fedupdebugxxx.log
3a) edit /etc/default/grub
- make sure KEYTABLE and SYSFONT are not defined in GRUB_CMDLINE_LINUX
- make sure GRUB_TIMEOUT=5 so you have a chance to press e and edit the kernel lines.
3b) grub2-mkconfig
4) reboot
5) edit kernel line (e)
- remove KEYTABLE and SYSTFONT items if present.
- add rd.upgrade.debugshell to the end of the kernel boot arguments.
6) boot (cntl-x)
7) press esc to see the running log, or cntl-F2 for dracut.

(There needs to be an update to fedup to get the bug fix in)

[pjoh]

may want to check /etc/default/grub and make sure KEYTABLE and SYSFONT are not defined in GRUB_CMDLINE_LINUX entry so that problem doesn't come back when grub2-mkconfig is run