From: Jan Frederick Eick <j.f.eick@gmx.de>
To: kexec@lists.infradead.org
Subject: Kexec on Macbook Pro 8,1
Date: Tue, 20 Nov 2012 19:19:41 +0100 [thread overview]
Message-ID: <k8ghk2$ms8$1@ger.gmane.org> (raw)
Hi there,
I'm not sure if this is the right place to ask my questions, but I found
very sparse documentation when it comes to solve problems with kexec.
I'm running an arch linux setup on my Macbook Pro 8,1 (Kernel
3.6.7-1-ck) with an i915 vga adapter (Intel HD Graphics 3000) and I try
to use kexec with systemd.
Systemd uses a service file to load the new Kernel image before
executing kexec:
[SNIP]
[Service]
Type=oneshot
ExecStart=/sbin/kexec -l /boot/vmlinuz-linux-ck \
--initrd=/boot/initramfs-linux-ck.img\
--reuse-cmdline
[/SNIP]
I use a system with an encrypted root partition, but I ran into the
exact same issue with my old setup (without encrypted root).
But when I issue the kexec call I can read the line
"Starting new kernel" and then my screen is garbled. I read a lot about
issues with the vga console, so I tried to reach my system by ssh, but
it didn't work.
I uploaded a "screenshot" here: http://imgur.com/UVDT9
Some more info:
[kernel commandline]
BOOT_IMAGE=/vmlinuz-linux-ck root=/dev/mapper/main-root ro
cryptdevice=/dev/sda6:main pcie_aspm=force i915.i915_enable_rc6=1
i915.lvds_downclock=1 i915.i915_enable_fbc=1 elevator=bfq verbose
[mkinitcpio.conf]
[...]
MODULES="ahci libahci ehci-hcd uhci-hcd ext3 ext4 vfat"
BINARIES="kexec"
FILES="/etc/modprobe.d/modprobe.conf"
HOOKS="base udev keymap fsck autodetect pata scsi sata usbinput encrypt
lvm2 uresume filesystems"
Does anyone have a hint how I could "debug" this issue or get kexec to
work on my system?
Kind regards
Jan
_______________________________________________
kexec mailing list
kexec@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/kexec
reply other threads:[~2012-11-20 18:25 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to='k8ghk2$ms8$1@ger.gmane.org' \
--to=j.f.eick@gmx.de \
--cc=kexec@lists.infradead.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox