Long ago Redhat and early Fedora versions had the option of pressing the letter i at boot to have it request for loading of the individual kernel options.
Used it long ago, but haven't seen it for a long time, and search show the old one, but not how it was done, or if it was something only on the redhat.
Have a project that I have handled since 2004, and it works fine using kernel.org source code to build on versions up to my current Fedora 28 system.
Have an user with an IBM Thinkpad t440p and it freezes with all 5 of the kernels that are included, plus with safe mode options, and debug options. Originally, the last message was about ata8 device. Built a special kernel with all ata modules removed, and lock just showed a different last message, so am thinking it is what loads next that is freezing.
Looked thru the kernel options, and don't see anything about an interactive option.
Just wondering if someone might know how that interactive boot process was done.
Thanks.
+------------------------------------------------------------+ Michael D. Setzer II - Computer Science Instructor (Retired) mailto:mikes@guam.net mailto:msetzerii@gmail.com Guam - Where America's Day Begins G4L Disk Imaging Project maintainer http://sourceforge.net/projects/g4l/ +------------------------------------------------------------+
http://setiathome.berkeley.edu (Original) Number of Seti Units Returned: 19,471 Processing time: 32 years, 290 days, 12 hours, 58 minutes (Total Hours: 287,489)
BOINC@HOME CREDITS
ROSETTA 66255811.060917 | ABC 16613838.513356 SETI 109742178.651890 | EINSTEIN 141783847.999240
On Thu, 13 Dec 2018 02:45:33 +1000 Michael D. Setzer II wrote:
Long ago Redhat and early Fedora versions had the option of pressing the letter i at boot to have it request for loading of the individual kernel options.
Can't help you, but I do remember kernels that would mention pressing 'i' to do that. I tried pressing 'i' many many times to see what it did, and nothing different ever happened, so perhaps they removed the 'i' option, but not the message until several years later :-).
When it did work, it was like when you to the Ctrl-Esc to watch the boot process where it now mostly just shows OK at each item. But with the i option, it would have you enter Y or N to decide for each option.
On 12 Dec 2018 at 12:44, Tom Horsley wrote:
Date sent: Wed, 12 Dec 2018 12:44:35 -0500 From: Tom Horsley horsley1953@gmail.com To: users@lists.fedoraproject.org Subject: Re: OT: Fedora Interactive boot option... Send reply to: Community support for Fedora users users@lists.fedoraproject.org
On Thu, 13 Dec 2018 02:45:33 +1000 Michael D. Setzer II wrote:
Long ago Redhat and early Fedora versions had the option of pressing the letter i at boot to have it request for loading of the individual kernel options.
Can't help you, but I do remember kernels that would mention pressing 'i' to do that. I tried pressing 'i' many many times to see what it did, and nothing different ever happened, so perhaps they removed the 'i' option, but not the message until several years later :-). _______________________________________________ users mailing list -- users@lists.fedoraproject.org To unsubscribe send an email to users-leave@lists.fedoraproject.org Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/users@lists.fedoraproject.org
+------------------------------------------------------------+ Michael D. Setzer II - Computer Science Instructor (Retired) mailto:mikes@guam.net mailto:msetzerii@gmail.com Guam - Where America's Day Begins G4L Disk Imaging Project maintainer http://sourceforge.net/projects/g4l/ +------------------------------------------------------------+
http://setiathome.berkeley.edu (Original) Number of Seti Units Returned: 19,471 Processing time: 32 years, 290 days, 12 hours, 58 minutes (Total Hours: 287,489)
BOINC@HOME CREDITS
ROSETTA 66262272.802084 | ABC 16613838.513356 SETI 109744303.173395 | EINSTEIN 141794097.999240
Allegedly, on or about 12 December 2018, Tom Horsley sent:
I do remember kernels that would mention pressing 'i' to do that. I tried pressing 'i' many many times to see what it did, and nothing different ever happened
I found it hit and miss whether it worked. I thought it might be that it wanted a capital I, perhaps. I seem to recall that you often had to stab madly at the keyboard before that moment, to get your foot in the door.
If you had a USB keyboard, it could well be that the system wasn't in a state to pay attention to the keyboard, at that time, either.
On Thu, 13 Dec 2018 02:45:33 +1000 "Michael D. Setzer II" mikes@guam.net wrote:
Long ago Redhat and early Fedora versions had the option of pressing the letter i at boot to have it request for loading of the individual kernel options.
Perhaps that was LILO or original grub? I don't remember that feature, but those seem more likely than it being in grub2.
Michael D. Setzer II wrote:
Long ago Redhat and early Fedora versions had the option of pressing the letter i at boot to have it request for loading of the individual kernel options.
Used it long ago, but haven't seen it for a long time, and search show the old one, but not how it was done, or if it was something only on the redhat.
Have a project that I have handled since 2004, and it works fine using kernel.org source code to build on versions up to my current Fedora 28 system.
Have an user with an IBM Thinkpad t440p and it freezes with all 5 of the kernels that are included, plus with safe mode options, and debug options. Originally, the last message was about ata8 device. Built a special kernel with all ata modules removed, and lock just showed a different last message, so am thinking it is what loads next that is freezing.
Looked thru the kernel options, and don't see anything about an interactive option.
Just wondering if someone might know how that interactive boot process was done.
AFAIK, the interactive boot mode was part of the SysV init. I don't know if anything similar is available with systemd init.
Here's an old thread from this list about it:
https://lists.fedoraproject.org/archives/list/users@lists.fedoraproject.org/...
Maybe that will provide a starting point for where to look in the systemd options.
On 12 Dec 2018 at 14:03, Todd Zullinger wrote:
Date sent: Wed, 12 Dec 2018 14:03:10 -0500 From: Todd Zullinger tmz@pobox.com To: users@lists.fedoraproject.org Subject: Re: OT: Fedora Interactive boot option... Send reply to: Community support for Fedora users users@lists.fedoraproject.org
Michael D. Setzer II wrote:
Long ago Redhat and early Fedora versions had the option of pressing the letter i at boot to have it request for loading of the individual kernel options.
Used it long ago, but haven't seen it for a long time, and search show the old one, but not how it was done, or if it was something only on the redhat.
Have a project that I have handled since 2004, and it works fine using kernel.org source code to build on versions up to my current Fedora 28 system.
Have an user with an IBM Thinkpad t440p and it freezes with all 5 of the kernels that are included, plus with safe mode options, and debug options. Originally, the last message was about ata8 device. Built a special kernel with all ata modules removed, and lock just showed a different last message, so am thinking it is what loads next that is freezing.
Looked thru the kernel options, and don't see anything about an interactive option.
Just wondering if someone might know how that interactive boot process was done.
AFAIK, the interactive boot mode was part of the SysV init. I don't know if anything similar is available with systemd init.
Here's an old thread from this list about it:
https://lists.fedoraproject.org/archives/list/users@lists.fedoraproject.org/...
Maybe that will provide a starting point for where to look in the systemd options.
Thanks for the info. Know that Fedora now uses systemd, but my project just boots from the iso using syslinux 6.03 and the kernels built from source at kernel.org. So, don't believe systemd is involved. Even with loglevel=15 no message gets reported. Did find a message with this model having a problem with ubuntu and a bios downgrade fixed the problem??
Thanks again.
-- Todd
I got stopped by a cop the other day. He said, "Why'd you run that stop sign?" I said, "Because I don't believe everything I read." -- Stephen Wright
+------------------------------------------------------------+ Michael D. Setzer II - Computer Science Instructor (Retired) mailto:mikes@guam.net mailto:msetzerii@gmail.com Guam - Where America's Day Begins G4L Disk Imaging Project maintainer http://sourceforge.net/projects/g4l/ +------------------------------------------------------------+
http://setiathome.berkeley.edu (Original) Number of Seti Units Returned: 19,471 Processing time: 32 years, 290 days, 12 hours, 58 minutes (Total Hours: 287,489)
BOINC@HOME CREDITS
ROSETTA 66262272.802084 | ABC 16613838.513356 SETI 109744303.173395 | EINSTEIN 141794097.999240
On Wed, Dec 12, 2018 at 02:03:10PM -0500, Todd Zullinger wrote:
AFAIK, the interactive boot mode was part of the SysV init. I don't know if anything similar is available with systemd init.
This feature was never at the kernel level, though -- it was about starting services once the kernel had booted and started init.
On 18-12-19 17:59:38, Matthew Miller wrote:
On Wed, Dec 12, 2018 at 02:03:10PM -0500, Todd Zullinger wrote:
AFAIK, the interactive boot mode was part of the SysV init. I don't know if anything similar is available with systemd init.
This feature was never at the kernel level, though -- it was about starting services once the kernel had booted and started init.
I see a hack:
https://unix.stackexchange.com/questions/362234/systemd-serialize-boot
-
Matthew Miller -
Michael D. Setzer II -
Michael D. Setzer II -
stan -
Tim -
Todd Zullinger -
Tom Horsley -
Tony Nelson