On Tue 08 Nov 2016 05:48:56 PM CST, David C. Rankin wrote:
On 11/08/2016 08:27 AM, Malcolm wrote:
Hi Also I had a HP ProBook 4330s that was in that category, I just hacked it with the grub file renamed and popped into /boot/efi/EFI/BOOT (maybe case sensitive?), but just left as a single boot system... The HP ProBook 4440s worked fine.
If push comes to shove, just press F9 and select the efi entry to boot from?
My HP ProBook 455 G1 was a bit funky, wanted CSM to install winX, then would work in Native mode after that for dual booting.
I would look at upgrading the BIOS and you might find changes (check the release notes at the download page as well as any previous releases).
I have a HP Pavilion g6 with win8.1, need to have a play with that once I get some time to clean out the blocked fan...
Yes, this just keeps getting stranger. The windows 10 driver (128G SSD) is MBR and the only boot files on the driver are:
bootmgr BOOTNXT BOOTSECT.BAK BOOTBCD BOOTSTAT.DAT bootvhd.dll en-us bootmgr.exe.mui memtest.ext.mui
That's plane-Jane MBR legacy boot. I'm not worried about dual booting at all, I just take the windows drive out and put it on a shelf. I'm just concerned with getting the box to boot something other than windows.
The only other plausible explanation I've read about is the difficulty some elitebooks have with large drive recognition. The concern SSD's and not normal platter drives, but I haven't run into any reasonably recent bios that doesn't recognize 1T drives.
I'm still completely bewildered by the situation. I've probably done 50-100 installs in the past 16-17 years and I've not run into this situation before.
Thanks you for your suggestions, I'll keep picking at this problem. Other than this boot problem, the rest of the box is working fine. I've done a full plasma/kde install, and am writing this from tbird on the MBR drive -- I just have to boot from USB (one heck of an unintended security feature...)
Hi If you press the F9 key, do you see something like "OS boot Manager"? I tried out the g6, UEFI though, it adds the HDD boot order back, so if wanting single boot would need to create a systemd service to reset the boot order with efibootmgr -n NNNN to it's entry would overcome this. -- Cheers Malcolm °¿° SUSE Knowledge Partner (Linux Counter #276890) openSUSE Leap 42.1|GNOME 3.16.2|4.1.34-33-default up 10 days 7:56, 3 users, load average: 0.27, 0.28, 0.48 CPU AMD Athlon(tm) II X4 635 @ 2.90GHz | GPU Nvidia GeForce 8800 GT -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org