On 08/16/2014 06:49 AM, Richard Melville wrote:
On 15 August 2014 19:49, Dan McGhee <[email protected]
<mailto:[email protected]>> wrote:
I apologize in advance for any ranting I might do. If it weren't
for iTunes, I wouldn't use Windows.
I installed a BIOS update from HP and then followed up with an
upgrade from Windows 8 to Windows 8.1. Upon reboot, I went right
to Windows instead of getting my gummiboot screen. No problem:
ESC then F9 during re-boot gave me my linux boot options.
Everything started normally, but then the booting stopped. The
following are the last three lines of the screen:
sh: cannot set terminal process group (-1): Inappropriate ioctl
for device
sh: no job control in this shell
sh-4.2# [with a blinking cursor]
The rest of the screen output told me that the kernel had begun to
boot normally: there were four penguins so "it saw" all the cores
on my processor, devtempfs had been mounted, all of my partitions
had been identified and the the three lines before what I typed
above had to do with freeing unused kernel memory and write
protecting read only data. There is one line that got my
attention and could point to the problem:
I left in the above to "keep the problem in view."
I think I have two situations. First, Windows over wrote the
bootloader--in retrospect I know that is "normal" behavior--and
I'm sure I can fix it once I can boot into linux. Second, and I'm
only guessing here, I need to recompile the kernel because of the
BIOS update. I don't know why, but that's what my intuition is
telling me.
I don't think it's a kernel issue. I'd check your disk
assignment/UUIDs in the BIOS and grub to make sure the correct
partitions are being called. Of course, I could be wrong.
No, Richard, you weren't wrong, but part of the problem was the kernel.
When I moved from Windows 8 to Windows 8.1, the update added another
partition AFTER the EFI Boot Partition. Therefore, all the following
partitions were raised by one number. My LFS partitions moved from
/dev/sda6 to /dev/sda7. This, because I use the kernel efi stubs to
boot, necessitated a reconfigured kernel because I pass "root=/dev/sdax,
ro" in the kernel. After I got Ubuntu installed, I reconfigured in
chroot, but still had the problem. But I've found some additional
information about the "ioctl" error.
I "googled" the exact error and found numerous reports on a number of
different fora. Those that were indicated as [SOLVED] included some
corruption or elimination of bootscripts from /sbin/init to the scripts
in /etc/rc.d/init.d and inittab. I checked and found that I had
everything from the installation of sysvinit--LFS-7.4--through the
LFS-Bootscripts.
I was trying to run commands in the shell I had when I booted and could
run only some of the basic built-ins: cd, pwd, etc. But I could not list
anything. I began to wonder if I was even in the right partition. I
had changed the command line options in the new kernel, but then I
remembered that gummiboot also passes commands to the kernel just like
grub can. Then I tried to boot again, and, low and behold, the kernel
was reporting "ext4-fs (sda6)...."!! Sure enough, back in Ubuntu I
discovered that I had forgotten to change the commands passed to the
kernel by gummiboot. I did this and now I have my LFS system back. What
a relief.
This is a good case for Bruce's thoughts on why he likes grub. I like it
too, for the same reasons, because it makes recovery from situations
like this easier. When I built LFS-7.4, I was on a steep learning curve
with UEFI and interfacing with Microsoft's doggy-do-do. I know more
now, and when I get to that part in my LFS-7.5 build--maybe I should
wait until 7.6 now--I want to get grub to work without going to legacy
boot on my hardware. The beauty of LFS, and a real downside to Ubuntu,
is that the grub.config stays constant because LFS teaches not to run
"update-grub." Each time there's an Ubuntu kernel update, grub.config
is regeneraged. But I know how to get around that. :)
Anyway, I'm up and running again and hate Windows even the more.
Dan
--
http://lists.linuxfromscratch.org/listinfo/lfs-support
FAQ: http://www.linuxfromscratch.org/blfs/faq.html
Unsubscribe: See the above information page
