CrunchBang Linux

cassidy

New Member

Registered: 2014-10-11

Posts: 7

No Boot even on Live, same for Clean Debian. Alienware14 (PLEASE help)

*EDITED* - Simplified question & answer format for ease of understanding.
- Marked solved as the primary question has been resolved, secondary threads have been open for discussion of the Bumblebee topic, will continue to add to this post in regards to the topics covered below, if I manage to actively be able to continue to use this Distro.
(#!First post!)

Question: Crunchbang will not boot from Live USB, screenshot provided.

Answer: add nomodeset to "Linux" line in the Grub Command Line Interface(Either by pressing the Tab or E key)

Screen -

Question:  Unable to Install Grub or Lilo boot loaders through Installer

Answer(1): Wiki page provides a solution -  How to chroot into #! to install Grub ( See answer(2) for perm. solution )

Answer(2): Need to find this again, give me a few hours. It is a DD Command, this also allowed me to install with LVM & Encryption + Grub, with no rebooting to live session.

Question: Trying to get TLP,Pstate,Thermald, i8kmon, bumblebee nvidia setup, this will fix fan controllers & cpu tempatures, as well as allow the access of Nvidia Optimus.

Answer:

sudo apt-get install i8kutils 

worked fine, for TLP I managed to clone the git and make install, worked 100% perfect. working on the rest.

Link to 2nd post regarding Bumblebee - No Gpu Driver Loaded.

Question: How to Add the Indicator for Cpufreq from Ubuntu.

Answer: Download the .deb Indicator Deb File

Run This

sudo dpkg -i indicator-cpufreq_0.2.2-0ubuntu1_all.deb

Then force the dependencies

sudo apt-get -f install

Add it to start on boot, and voila.

Additional: how to remove conservative/ondemand and fix CPUfreq for newer cpu's. - Will add shortly.

Last edited by cassidy (2014-10-15 23:21:27)

ohnonot

...again

Registered: 2012-05-22

Posts: 1,748

Website

Re: No Boot even on Live, same for Clean Debian. Alienware14 (PLEASE help)

the "assuming drive cache" message is pretty common, not an error.

obviously "bad target number" sticks out, enclosed by a double mention of nouveau.

from that i would deduce that:
maybe try to force the system to use intel graphics (instead of nvidia) via grub kernel command line editing?

that said, if you ever manage to get #! installed, you're going to have to do some kernel backporting at the very least to get your dual graphics working.

edit: first time poster, a warm welcome to #! forums!

Last edited by ohnonot (2014-10-12 06:45:38)

---

how to ask smart questions, and succeed in getting help from others.
moxie marlinspike on privacy  |  history of computer viruses (fun fact)

Head_on_a_Stick

#! Cat

From: A world of pure imagination

Registered: 2014-01-21

Posts: 2,782

Re: No Boot even on Live, same for Clean Debian. Alienware14 (PLEASE help)

Try this (no guarantees though):
At the GRUB menu, press "e" and add "nomodeset" to the kernel command line.
https://wiki.archlinux.org/index.php/Ke … odesetting
You may need to add this to /etc/default/grub & run `update-grub` to make it permanent...

If this works: as @ohnonot says, you will need to update the kernel (`apt-get update && apt-get upgrade`) or try the backported kernel:
http://crunchbang.org/forums/viewtopic.php?id=36896

EDIT: Hello & welcome to #!

Last edited by Head_on_a_Stick (2014-10-11 13:30:27)

---

Using Debian ~ Debian Reference ~ Debian vs. Ubuntu

cassidy

New Member

Registered: 2014-10-11

Posts: 7

Re: No Boot even on Live, same for Clean Debian. Alienware14 (PLEASE help)

Edited to clean thread - see OP for more information.

Last edited by cassidy (2014-10-14 14:57:08)

damo

#! gimpbanger

From: N51.5 W002.8 (mostly)

Registered: 2011-11-24

Posts: 4,441

Re: No Boot even on Live, same for Clean Debian. Alienware14 (PLEASE help)

How to chroot into #! on disk when you can not boot via grub
"Assumption: #! is installed on /dev/sda1 but is not accessible via grub
Goal: reinstall grub in mbr of /dev/sda:"

Ta da...

---

Artwork at deviantArt;  Iceweasel Personas;  SLiM #! Themes;  Openbox themes

cassidy

New Member

Registered: 2014-10-11

Posts: 7

Re: No Boot even on Live, same for Clean Debian. Alienware14 (PLEASE help)

How to chroot into #! on disk when you can not boot via grub
"Assumption: #! is installed on /dev/sda1 but is not accessible via grub
Goal: reinstall grub in mbr of /dev/sda:"

Ta da...

Hey, I should of mentioned I'm using LVM & Luks Encryption on the HDD as well.

I've already spotted that guide since it was ported to the Wiki page, however it lacks the steps for LVM/Encryption, on the second page of the thread, you'll notice some information regarding that, however it's not very direct and hasn't resolved the issue for me .

*Powering off the notebook for 20-30 minutes to let it cool, without the proper applications this thing could fry and egg*
*I copied my password, and logged in on my tablet to the forums incase I get a reply in the mean time*

Last edited by cassidy (2014-10-14 00:05:42)

ohnonot

...again

Registered: 2012-05-22

Posts: 1,748

Website

Re: No Boot even on Live, same for Clean Debian. Alienware14 (PLEASE help)

i know next to nothing about LVM, but it's not necessary to chroot to install grub - so maybe this helps:
start into the live session and issue

sudo update-grub

and see whether it finds your installation. if so,

sudo grub-install /dev/sdX

where "X" is your first hard drive - so usually /dev/sda

edit: now i think of it, i have never done it exactly like that, i usually use a dedicated rescue disk for a task like that (it's called rescatux)

edit2: the overheating is an important issue and has to be sorted out.

Last edited by ohnonot (2014-10-14 07:15:50)

---

how to ask smart questions, and succeed in getting help from others.
moxie marlinspike on privacy  |  history of computer viruses (fun fact)

cassidy

New Member

Registered: 2014-10-11

Posts: 7

Re: No Boot even on Live, same for Clean Debian. Alienware14 (PLEASE help)

i know next to nothing about LVM, but it's not necessary to chroot to install grub - so maybe this helps:
start into the live session and issue

sudo update-grub

and see whether it finds your installation. if so,

sudo grub-install /dev/sdX

where "X" is your first hard drive - so usually /dev/sda

edit: now i think of it, i have never done it exactly like that, i usually use a dedicated rescue disk for a task like that (it's called rescatux)

edit2: the overheating is an important issue and has to be sorted out.

Hey, thanks for stopping by the thread again!

I managed to resolve the Grub Boot Loader fail to install with a secondary method not found on the forums, I'll update my main thread with the DD command once I find it again .

Please see the last question in my first post, as this is now primary concern #1!