![]() Your imgargs line does tell the installer to boot into the live environment. You might rewrite the line into ipxe format like this kernel initrd imgargs vmlinuz initrd=initrd.img nst.stage2= ip=dhcp Menu label ^Install Fedora 28 ( Minimal Image )Īppend initrd=f28/initrd.img inst.stage2= ip=dhcp ks= That shows the pxelinux configuration of label linuxĪppend initrd=f28/initrd.img inst.stage2= ip=dhcp Specifically the section labeled “Configuring client bootloaders” I have been scouring for documentation or any reference online to a working iPXE entry for Fedora but they all basically look like what I have.Īny help would be greatly appreciated, Thanks I would suspect it has to do with the root=live portion of my entry, but its almost identical for CentOS and that starts to the installer as expected. Here is the menu entry: kernel initrd imgargs vmlinuz initrd=initrd.img root=live: ip=dhcp repo= splash quiet A reboot effectively destroys the environment as it was running in memory. I do not however have any options to install to disk. When I select my option from the iPXE menu to install Fedora it boots up to basically the Live CD instead, giving me a desktop, letting me pick some of the post install options (like data collection and creating a user). I'm sure there is a better way to find the devices but I don't know what it is.Trying this on a physical host, a Dell 3620 in UEFI and in BIOS modes. If you loose your touch/stylus devices and don't want to reboot, there is an ugly workaround: as root (sudo did not work for me) run "sudo echo s2idle > /sys/power/mem_sleep", suspend, wake the laptop up, run sudo echo deep > /sys/power/mem_sleep" to restore S3 suspend. It works better (maybe even reliably) with "systemctl hybrid-sleep" instead of "systemctl suspend". With the patch, the sleep works but I have one issue: when the laptop wakes up, it does not see stylus or finger touch devices. The original patch gave me some compiling errors, the shorter one may work right away, but I am not sure which version worked in the end (one of the reasons for linking the whole discussion). There is also a thread with discussion here: The post also has a link to a shorter patch (that may or may not be specific for Yoga). There is a patch for DSDT tables that allows for S3 sleep at the following link It seems that Lenovo says the two are incompatible and refuses to create a BIOS that allows a choice between the two. Lenovo's BIOS does not include S3 suspend, instead it has S0i3 version needed by newer Windows. The first thing that was suggested in those instructions was to modify some option in the BIOS which ended up slowing down the boot time by 10 minutes, so I immediately reverted that. I read about having to fiddle to active S3 deep sleep, but I am wondering if I need to do that. ![]() And the time problem, I couldn't find anybody with this problem yet. I read about similar issues, yet not quite the same as in many of those cases the laptop does not even enter suspend mode when the lid is closed, while in my case everything "seems" to work. To fix the time problem I need to either restart the laptop or fiddle with Date/Time settings by disabling and re-enabling back NTP and automatic timezone. Also, the time goes forward by two hours, which I think has to do with my timezone given that I am in GMT+2. When I reopen the lid though I notice that the battery is suprisingly quite warm, and it lost quite some charge while it was in suspend mode. The little red light that's part of the ThinkPad logo starts blinking, which seems to indicate suspend mode is on. ![]() Everything works pretty well, besides suspending when I close the lid, which is quite important when working from a laptop. I have recently installed Fedora 28 workstation on my brand new X1 Yoga ( 3rd generation).
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |