Re: Boots into emergency mode. How to analyze?

2015-06-26 Thread Nick T.
I have regained access to several debian 8 vms using this method, Yes, 
it still works.


On 06/26/2015 03:33 PM, The Wanderer wrote:

On 06/26/2015 at 07:55 AM, Nick T. wrote:


On 06/26/2015 12:55 PM, to...@tuxteam.de wrote:


well and good until you find yourself in the situation this very
thread is about: your root filesystem is broken and you can only
log in as root. Then you need your root password.


Ubuntu and debian can boot into recovery mode from the grub menu,
from there it asks for the root password IF there is one, if not it
just gives you a root shell.


Are you sure Debian still does this? Looking at the bug report which
Sven Joachim filed (linked from his post in this thread), it seems to me
as if the patch which added this functionality was lost when an
important binary was moved to another package.




--
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org 
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org

Archive: https://lists.debian.org/558d4a64.2080...@ncktsp.com



Re: Boots into emergency mode. How to analyze?

2015-06-26 Thread Nick T.



On 06/26/2015 04:12 PM, Matthijs Wensveen wrote:

Not the case. Even in rescue mode I needed to supply the root login. I
could use init=/bin/sh but I couln't find anything in the logs in
/var/log, so I'm guessing systemd and journalctl keeps the journal in
some other place (probably some binary format hidden in a database or
something).

Matthijs




I actually just tried it,
sulogin: root account is locked, starting shell
it works on jessie at least

- Nick


--
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org 
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org

Archive: https://lists.debian.org/558d551c.6040...@ncktsp.com



Re: Boots into emergency mode. How to analyze?

2015-06-26 Thread Nick T.

On 06/26/2015 12:55 PM, to...@tuxteam.de wrote:

well and good until you find yourself in the situation
this very thread is about: your root filesystem is broken and you
can only log in as root. Then you need your root password.


Ubuntu and debian can boot into recovery mode from the grub menu, from 
there it asks for the root password IF there is one, if not it just 
gives you a root shell.


- Nick


--
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org 
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org

Archive: https://lists.debian.org/558d3da9.9030...@ncktsp.com



Re: Boots into emergency mode. How to analyze?

2015-06-26 Thread Nick T.


On 06/26/2015 03:59 PM, The Wanderer wrote:

(Please don't top-post.)

On 06/26/2015 at 08:49 AM, Nick T. wrote:


On 06/26/2015 03:33 PM, The Wanderer wrote:


On 06/26/2015 at 07:55 AM, Nick T. wrote:



Ubuntu and debian can boot into recovery mode from the grub
menu, from there it asks for the root password IF there is one,
if not it just gives you a root shell.


Are you sure Debian still does this? Looking at the bug report
which Sven Joachim filed (linked from his post in this thread), it
seems to me as if the patch which added this functionality was lost
when an important binary was moved to another package.


I have regained access to several debian 8 vms using this method,
Yes, it still works.


How recently? What versions of sysvinit/sysvinit-core and util-linux
were installed on the systems in question?

It's not impossible that this functionality could be unrelated to the
patch from bug 326678 (which is referenced from the new bug 789950), but
having reviewed both of those bugs, I'd be surprised if it were.



Just tested it on one of the systems I am currently configuring, works 
like a charm



$ dpkg -l | grep sysvinit
ii sysvinit-utils 2.88dsf-59 amd64 System-V-like utilities



$ dpkg -l | grep util-lin
ii util-linux 2.25.2-6 amd64 Miscellaneous system utilities
ii util-linux-locales 2.25.2-6 all Locales files for util-linux


- Nick


--
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org 
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org

Archive: https://lists.debian.org/558d52a8.1090...@ncktsp.com



Re: Unable to install nVidia driver on Debian 6 LTS - was - Re: How to boot without GUI

2015-06-10 Thread Nick T.
Try adding nomodeset to the boot command if its not already there, I had 
to add that to make the driver work.


- Nick

On 06/10/2015 10:45 PM, Bret Busby wrote:

On 11/06/2015, Nick T. n...@ncktsp.com wrote:

Oops, forgot to cc in the mailing list.

- Nick

On 06/10/2015 09:19 PM, Nick T. wrote:

Install build-essential it should contain all the packages necessary
to install the driver.
Also you might want to install dkms if you don't want to reinstall the
driver after every kernel update.

- Nick




Thank you for that.

The driver installation appears to have subsequently succeeded.

However, after rebooting, the system still does not see the external
monitor (using System - Preferences - Monitors), and


:~# lspci -nn | grep VGA
00:02.0 VGA compatible controller [0300]: Intel Corporation Device
[8086:0416] (rev 06)


So, the driver appears to be installed, but not implemented.




--
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org 
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org

Archive: https://lists.debian.org/55789536.3070...@ncktsp.com



Re: Unable to install nVidia driver on Debian 6 LTS - was - Re: How to boot without GUI

2015-06-10 Thread Nick T.
Edit /etc/default/grub as root and append nomodeset to 
GRUB_CMDLINE_LINUX_DEFAULT save exit and run update-grub as root.


- Nick

On 06/10/2015 10:55 PM, Bret Busby wrote:

On 11/06/2015, Nick T. n...@ncktsp.com wrote:

Try adding nomodeset to the boot command if its not already there, I had
to add that to make the driver work.



This will probably make me seem even more stupid than I probably
already appear, but, how do I do that?

Thank you in anticipation.




--
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org 
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org

Archive: https://lists.debian.org/55789739.8040...@ncktsp.com



Re: Unable to install nVidia driver on Debian 6 LTS - was - Re: How to boot without GUI

2015-06-10 Thread Nick T.

nomodeset goes inside the quotes derp :P

GRUB_CMDLINE_LINUX_DEFAULT=quiet nomodeset

- Nick

On 06/10/2015 11:23 PM, Bret Busby wrote:

On 11/06/2015, Nick T. n...@ncktsp.com wrote:

Edit /etc/default/grub as root and append nomodeset to
GRUB_CMDLINE_LINUX_DEFAULT save exit and run update-grub as root.

- Nick

On 06/10/2015 10:55 PM, Bret Busby wrote:

On 11/06/2015, Nick T. n...@ncktsp.com wrote:

Try adding nomodeset to the boot command if its not already there, I had
to add that to make the driver work.



This will probably make me seem even more stupid than I probably
already appear, but, how do I do that?

Thank you in anticipation.



After appending, the file is thus;


:~# cat /etc/default/grub
# If you change this file, run 'update-grub' afterwards to update
# /boot/grub/grub.cfg.

GRUB_DEFAULT=0
GRUB_TIMEOUT=5
GRUB_DISTRIBUTOR=`lsb_release -i -s 2 /dev/null || echo Debian`
GRUB_CMDLINE_LINUX_DEFAULT=quiet nomodeset
GRUB_CMDLINE_LINUX=

# Uncomment to enable BadRAM filtering, modify to suit your needs
# This works with Linux (no patch required) and with any kernel that obtains
# the memory map information from GRUB (GNU Mach, kernel of FreeBSD ...)
#GRUB_BADRAM=0x01234567,0xfefefefe,0x89abcdef,0xefefefef

# Uncomment to disable graphical terminal (grub-pc only)
#GRUB_TERMINAL=console

# The resolution used on graphical terminal
# note that you can use only modes which your graphic card supports via VBE
# you can see them in real GRUB with the command `vbeinfo'
#GRUB_GFXMODE=640x480

# Uncomment if you don't want GRUB to pass root=UUID=xxx parameter to Linux
#GRUB_DISABLE_LINUX_UUID=true

# Uncomment to disable generation of recovery mode menu entries
#GRUB_DISABLE_LINUX_RECOVERY=true

# Uncomment to get a beep at grub start
#GRUB_INIT_TUNE=480 440 1


And, in running thence, update-grub, I get this;


:~# update-grub
/etc/default/grub: 7: nomodeset: not found


Sould I have entered the string nomodeset, differently?




--
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org 
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org

Archive: https://lists.debian.org/55789d99.9060...@ncktsp.com



Re: Unable to install nVidia driver on Debian 6 LTS - was - Re: How to boot without GUI

2015-06-10 Thread Nick T.

Oops, forgot to cc in the mailing list.

- Nick

On 06/10/2015 09:19 PM, Nick T. wrote:
Install build-essential it should contain all the packages necessary 
to install the driver.
Also you might want to install dkms if you don't want to reinstall the 
driver after every kernel update.


- Nick

On 06/10/2015 09:00 PM, Bret Busby wrote:

On 11/06/2015, Lisi Reisz lisi.re...@gmail.com wrote:

On Wednesday 10 June 2015 16:52:50 Bret Busby wrote:

ERROR: Unable to find the development tool `cc` in your path; please
make sure that you have the package 'gcc' installed.  If gcc is
installed on your system, then please check that `cc` is in your PATH.

Have you done this?

Start with:
# aptitude search gcc

and if necessary

# aptitude install gcc

If you already have gcc, then check your PATH as suggested.

Lisi


Okay.

So, I installed gcc, using apt-get, then tried again.

Then, got the same error regarding make.

So, I installed make, then tried again, and got two further errors.

See log file below.

And, some may wonder why I prefer software (like hardware drivers)
that can be installed using a package manager that takes care of all
such problems...



:~# cat /var/log/nvidia-installer.log
nvidia-installer log file '/var/log/nvidia-installer.log'
creation time: Thu Jun 11 01:48:43 2015
installer version: 346.72

PATH: /sbin:/usr/sbin:/bin:/usr/bin

nvidia-installer command line:
 ./nvidia-installer

Using: nvidia-installer ncurses user interface
- Detected 8 CPUs online; setting concurrency level to 8.
- License accepted.
- Installing NVIDIA driver version 346.72.
- Performing CC sanity check with CC=/usr/bin/cc.
- The CC version check failed:

The compiler used to compile the kernel (gcc 4.3) does not exactly
match the current compiler (gcc 4.4).  The Linux 2.6 kernel module
loader rejects kernel modules built with a version of gcc that does
not exactly match that of the compiler used to build the running
kernel.

If you know what you are doing you can either ignore the CC version
check and continue installation, or abort installation, set the CC
environment variable to the name of the compiler used to compile your
kernel, and restart installation. (Answer: Ignore CC version check)
ERROR: Unable to find the kernel source tree for the currently running
kernel.  Please make sure you have installed the kernel source files
for your kernel and that they are properly configured; on Red Hat
Linux systems, for example, be sure you have the 'kernel-source' or
'kernel-devel' RPM installed.  If you know the correct kernel source
files are installed, you may specify the kernel source path with the
'--kernel-source-path' command line option.
ERROR: Installation has failed.  Please see the file
'/var/log/nvidia-installer.log' for details.  You may find suggestions
on fixing installation problems in the README available on the Linux
driver download page at www.nvidia.com.


I do not know why the hardware manufacturers make getting their
hardware operational, so difficult.







--
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org 
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org

Archive: https://lists.debian.org/55788078.3010...@ncktsp.com