Linux - Laptop and NetbookHaving a problem installing or configuring Linux on your laptop? Need help running Linux on your netbook? This forum is for you. This forum is for any topics relating to Linux and either traditional laptops or netbooks (such as the Asus EEE PC, Everex CloudBook or MSI Wind).
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
Have laptop [Itronix GoBook VR2] which can switch hard drives.
When used it just for Linux had no problem, but after switched in Windows [7 & 10] would no longer start any Linux OS hard drive.
On some got notice that had no NT?? something; on the present Debian version 2.02 beta 3-5 got messages:: ACPI Error: Unsupported address space: 0x86 (20160831/hwregs-151).
ACPI Exception: AE_SUPPORT, could not create GPE Block 0 (20160831/evgpeinit-143)
Anyone with experience with this problem? Is there a fix?
but after switched in Windows [7 & 10] would no longer start any Linux OS hard drive.
Does that mean you added a physical hard drive with some release of Debian on it? How are you trying to boot it? Did you change the Boot priority in the BIOS to the Linux drive?
Is one of the messages no ntldr file found? that would be an attempt to boot some Legacy install of windows.
Can you boot off of any live linux cd/usb flash drive? If not, your windows hard drive/installation may have set the uefi/bios to secure boot which is incompatible with your linux installation. You can check your bios setup and see if there is some type of compatibility mode rather than secure boot.
Yes, I inserted a hard drive with Debian installed on it. I checked bios and the linux hard drive is listed as set to boot [Hitachi HTS5etc. 120 GB -- is debian].
When use recovery mode at boot get: ACPI: Dynamic OEM Table Load:
ACPI: SSDT 0xFFFF925EFA68D8400000 (v01 PmRef Cpu1Cst 0000300DINTL20051117)
ACPI: EC: EC startup
ACPI: EC: interrupt blocked
If you set Windows 10 to hibernate or suspend it could be blocking the booting of other OS's. There is some way to clear that but usually boot to windows 10 and do full shutdown.
Both windows 7 & 10 fully shut down. Regards advanced settings, only options are: 1. Hard Disk Controller Config; Config Mode AHCI; with Master [Hitachi/Debian] Slave [TEAC DV-W28E-R]
2. I/O Device Config: Serial Port A: Enabled
Base I/O Address: <3F87>
Interrupt: <IRQ47>
Enabled: OnBoard COM Port is functional: Allows for user-config settings
Disabled: Disables OnBoard COM Port's functionality
The debian boot has an option for trying 'recovery' mode and when used has different response to not booting and so different message.
Will have to get a 'live' os to try out.
I think you are saying it gets to grub menu?
If so you may have an issue where naming is wrong. That somehow this drive is now not correctly mentioned in boot.
The live boot is always a good test and should be one of the first things one tries to see what the system state is.
Missing NTLDR
Means it can't find Windows boot files. So it's either looking at the wrong MBR or the Debian MBR was changed by Windows or something. Try removing the Windows disk.
EDIT: Then chroot in from the Debian install disk recovery mode to reinstall grub or select that option from the menu.
Thank you Brains as this looks encouraging [definitely think that NTLDR is core of matter].
Was no chroot in edit section, but changed 'set root='hd0,msdos' to: set root='reinstall grub' , but didn't work.
Trying command line, of commands available there was a 'ntldr' so tried that, but said needed to add a file name, and Debian didn't work and don't know what else to try; any suggestions?
It just so happens I downloaded the latest Debian Testing Net Install CD yesterday.
Did a trial rescue in VMWare.
Boot the install CD, select Advanced options, select Graphical Rescue Mode, answer the questions, it'll seem as if it's getting ready to install, don't sweat. It'll come to ask "Enter a device as root etc." select the installed root partition. It'll then ask if it should mount the EFI system partition if it is EFI, hit radio button yes.
Then you will be presented with the following options:
Execute a shell in /dev/your-selected-root ---> this will put you in chroot
Execute a shell in the installer version ---> If you don't know your root partition, choose this, issue command fdisk -l | less (less to scroll up/down) to check then exit to come back here
Reinstall Grub ---> need to make sure system partition mounted
Force Grub to removable path
Choose different root ---> If you choose wrong partition, exit and it'll bring you back to this menu to select another
Reboot
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.
