On 2/25/19 9:06 PM, Chris Murphy wrote:
On Mon, Feb 25, 2019 at 4:25 PM Chris Murphy
lists@colorremedies.com wrote:
On Mon, Feb 25, 2019 at 3:59 PM pmkellly@frontier.com pmkellly@frontier.com wrote:
Testing Fedora 30 Workstation potential beta drop 0224:
The ISO was down loaded and checked against the CHECKSUM file and passed. The ISO was burned to a DVD and the DVD check sum passed. The DVD was used to boot the bare metal test system (Lenovo M58p with E8400 processor). The system booted normally and Anaconda started and the
disk
settings of Delete all and Reclaim space were selected. The
installation
completed with no problems.
Notable results:
The media check did not run after boot before Anaconda started
OK I can't reproduce this with either
-rw-rw-r--. 1 chris chris 658505728 Feb 25 18:21 Fedora-Server-netinst-x86_64-30-20190224.n.0.iso -rw-rw-r--. 1 chris chris 1944256512 Feb 25 18:20 Fedora-Workstation-Live-x86_64-30-20190224.n.0.iso
Both of them go through the media check, I see the usual % status, and then the report that it passes. For whatever reason the Workstation-Live media is slow.
I just booted to the live install disk a few more times and didn't see any sign of the media check running. I watched the CD and hard disk activity lights closely and though I couldn't see the screen come up with the choices to check and boot, just boot, or troubleshoot I got the impression that the software was running and it would operate according to the selection. When I had it run with the media check the activity seemed credible. It maybe possible that the menu and subsequent media test are running, but just not showing up on the screen. The first thing that shows up on the screen is the long scrolling list of messages during boot. From that point on everything seems normal. This might be an issue with a display parameter. This is supported by another experiment I tried. I used the same F30 Workstation Live 0224 drop DVD to boot an AMD machine. On the AMD machine the menu showed up and the media check could be seen running. My test machine that doesn't display these items is a Lenovo M58p with an Intel E8400 processor. All the monitors here are Samsung and haven't shown problems.
I don't see a grub screen so I don't have any luck trying to press an 'e' to get to the editor. I thought about trying to edit /etc/grub2-efi.cfg, but I can't think of how to make that work. By the time I can open a shell and edit the file I think it's all over. Also, I believe it's not an editable file in the live environment. Given the above this may be mute.
Have a Great Day!
Pat (tablepc)
On Mon, Feb 25, 2019 at 8:49 PM pmkellly@frontier.com pmkellly@frontier.com wrote:
I just booted to the live install disk a few more times and didn't see any sign of the media check running. I watched the CD and hard disk activity lights closely and though I couldn't see the screen come up with the choices to check and boot, just boot, or troubleshoot I got the impression that the software was running and it would operate according to the selection.
I can't explain that.
My test machine that doesn't display these items is a Lenovo M58p with an Intel E8400 processor. All the monitors here are Samsung and haven't shown problems.
Does this same behavior happen with the final release for Fedora 29? There are some GRUB and kernel changes since Fedora 29 related to, I think, flicker free boot. What you're describing is perhaps text mode for GRUB and early kernel boot not working on this Lenovo so tracking that down would be a good idea.
Maybe Hans has an idea.
On 2/26/19 12:02 AM, Chris Murphy wrote:
On Mon, Feb 25, 2019 at 8:49 PM pmkellly@frontier.com pmkellly@frontier.com wrote:
I just booted to the live install disk a few more times and didn't see any sign of the media check running. I watched the CD and hard disk activity lights closely and though I couldn't see the screen come up with the choices to check and boot, just boot, or troubleshoot I got the impression that the software was running and it would operate according to the selection.
I can't explain that.
Well, I've made some progress. I Have other Lenovo M58p PCs with the same processor and display chip. These PCs have both VGA and Display Port display interfaces.
I tried using my 0224 DVD to boot one of the other PCs The media check menu displayed fine and I could watch the media test run. The difference between this PC and my test PC is the model of Samsung display. Both PCs have the display connected using HDMI cables with Display Port adapters plugged into the PC.
Now it's important to note that once the install is done with the media check that all following display items work fine including such things as Gnome, terminal, librioffice, and watching video.
Then I changed the display connection on my test machine from HDMI to VGA. With that connection the media check menu and the media check progress could be seen fine.
Though the Samsung monitor on my test machine is a different model, it is a current one about 3 years old (22 inches instead of the 27 inch on the deployed machines. I am wondering if the media check software might be using an HDMI protocol, setting, or... that might be deprecated, or one of those "not guaranteed to be implemented on all manufacturer's models".
Have a Great Day!
Pat (tablepc)
My test machine that doesn't display these items is a Lenovo M58p with an Intel E8400 processor. All the monitors here are Samsung and haven't shown problems.
Does this same behavior happen with the final release for Fedora 29? There are some GRUB and kernel changes since Fedora 29 related to, I think, flicker free boot. What you're describing is perhaps text mode for GRUB and early kernel boot not working on this Lenovo so tracking that down would be a good idea.
Maybe Hans has an idea.
On Tue, 2019-02-26 at 08:13 -0500, pmkellly@frontier.com wrote:
Though the Samsung monitor on my test machine is a different model, it is a current one about 3 years old (22 inches instead of the 27 inch on the deployed machines. I am wondering if the media check software might be using an HDMI protocol, setting, or... that might be deprecated, or one of those "not guaranteed to be implemented on all manufacturer's models".
I'm pretty sure that everything is actually *happening* the same - the media check is running - you're just not *seeing* it. For whatever reason, the early boot phase is not being successfully displayed on the monitor. It sounds like your system's firmware cannot output on this monitor for some reason, but once the Linux kernel takes over video output duties from the firmware, it can. That's why you only see output showing up once the system has made it through early boot - it's showing up at the point where the kernel takes over from the firmware.