Need help solving Centos problem (won't boot) crontab related?

[Sandy (on Knoppix)]

All I know is that this morning, Centos wouldn't boot.
I see where it's hung, and, it's probably my fault.
About six months ago, I hacked out an automatic script to
ping google and other sites to log when the network goes down.

The POST works fine, and the little blue bar at the bottom of
the Centos screen works fine, but, at some point, before booting
is done, I can see my pings showing on the screen - and - for
the life of me, I can't kill that job.

Control-C, escape, control Q, etc, numerous times, just won't
stop it. I'm not sure WHY it's hung - but its running that job.

So, I booted to Knoppix and just want to kill whatever it is that
went wrong.

Any ideas?

PS: I'll post details about the job that is running separately.

[Sandy (Knoppix KNode Emergency Repair)]

Sandy (on Knoppix) wrote:

> All I know is that this morning, Centos wouldn't boot.

> I'll post details about the job that is running separately

Well, looking back, it seems I had changed /etc/rc.local
FROM:
#!/bin/sh
touch /var/lock/subsys/local
TO:
#!/bin/sh
touch /var/lock/subsys/local
/usr/local/bin/pingnet &

Where /usr/local/bin/pingnet was scripted as the following:

#!/bin/bash
# /usr/local/bin/pingnet
# WIP: Need to prevent shutdown from causing bad pings in the log file
LOG='/var/log/pingnet.log'
PING='/bin/ping'
# External and internal hosts to ping
EXTHOST1='www.google.com'
EXTHOST2='sun.iwu.edu'
# INTHOST1='192.168.1.1'
INTHOST1='router'
# INTHOST2='10.0.1.1'
INTHOST2='radio'
# Time to wait between pings (seconds)
# WAITTIME=120
WAITTIME=10
# Added boottime to prevent messages due to booting up w/o network yet
BOOTTIME=30

echo "NETWORK STATUS SCRIPT: Started " `date` >> $LOG
sleep $BOOTTIME
while [ 1=1 ]
do
dater=`date +%Y.%m.%d-%H.%M.%S`
$PING -q -c1 $EXTHOST1
ret=$?
echo "RET: $ret"
if [ $ret -ne 0 ]
then
echo "EXTERNAL_PING(1): outage detected $dater" >> $LOG
fi

dater=`date +%Y.%m.%d-%H.%M.%S`
$PING -q -c1 $EXTHOST2
ret=$?
echo "RET: $ret"
if [ $ret -ne 0 ]
then
echo "EXTERNAL_PING(2): outage detected $dater" >> $LOG
fi

$PING -q -c1 $INTHOST1
ret=$?
echo "RET: $ret"
if [ $ret -ne 0 ]
then
echo "INTERNAL_PING(1): outage detected $dater" >> $LOG
fi

$PING -q -c1 $INTHOST2
ret=$?
echo "RET: $ret"
if [ $ret -ne 0 ]
then
echo "INTERNAL_PING(2): outage detected $dater" >> $LOG
fi

sleep $WAITTIME
done

The result was a /var/log/pingnet.log containing lines such as:
$ tail -f /var/log/network.log
EXTERNAL_PING(1): outage detected 2013.02.15-12.51.28
EXTERNAL_PING(2): outage detected 2013.02.15-12.51.38
NETWORK STATUS SCRIPT: Started Sat Feb 16 08:36:56 PST 2013
EXTERNAL_PING(2): outage detected 2013.02.16-08.37.26
INTERNAL_PING(1): outage detected 2013.02.16-08.37.26
INTERNAL_PING(2): outage detected 2013.02.16-08.37.26
EXTERNAL_PING(1): outage detected 2013.02.16-08.37.56
EXTERNAL_PING(2): outage detected 2013.02.16-08.37.56
INTERNAL_PING(1): outage detected 2013.02.16-08.37.56
INTERNAL_PING(2): outage detected 2013.02.16-08.37.56
EXTERNAL_PING(1): outage detected 2013.02.16-09.05.11
EXTERNAL_PING(2): outage detected 2013.02.16-09.05.36

So, now I just have to figure out WHY this script stopped
working (and started hanging the init) after 8 months of
working just fine.

I think I'll see if I can get Knoppix to delete the line
I added into rc.local, and report back what I find out.

[Sandy (Knoppix KNode Emergency Repair)]

Sandy (Knoppix KNode Emergency Repair) wrote:

> I think I'll see if I can get Knoppix to delete the line
> I added into rc.local, and report back what I find out.

The first problem with using Knoppix to repair a non-booting
Centos is that it's not at all intuitive how to get Knoppix
to actually boot on a Lenovo W510 laptop.

Most of the time, Knoppix 7 just hung after the line:
Booting the kernel ...
until, after much trial and error, I figured out a set of
Knoppix 'cheat codes' that would allow it to boot.

After much trial and error these are the Lenovo W510 options
that seemed to work (I actually don't even know what they
do as all I really wanted was just to boot to Knoppix):

knoppix64 xmodele=nv acpi=off nolapic hpet=off no3d

Now that I'm finally booted to Knoppix, I can run some basic tests.

[Sandy (Knoppix KNode Emergency Repair)]

> These are the Lenovo W510 options that seemed to work

> knoppix64 xmodele=nv acpi=off nolapic hpet=off no3d

> Now ... I can run some basic tests ...

Googling for Knoppix disk mounting tutorials, the first few
steps seem common - but the real problem is the LVM file system!

1. This is the version of Knoppix:
knoppix@Microknoppix:~$ uname -a
Linux Microknoppix 3.6.11-64 #10 SMP PREEMPT Wed Dec 19 23:51:48 CET
2012 x86_64 GNU/Linux

2. This is the problematic video controller card:
knoppix@Microknoppix:~$ !! | grep NV
lspci | grep NV
01:00.0 VGA compatible controller: NVIDIA Corporation GT216 [Quadro FX
880M] (rev a2)

3. Unfortunately, it looks like I have an LVM disk drive:
knoppix@Microknoppix:~$ fdisk -l

Disk /dev/sda: 128.0 GB, 128035676160 bytes
255 heads, 63 sectors/track, 15566 cylinders, total 250069680 sectors
Units = sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disk identifier: 0x5504d700

Device Boot Start End Blocks Id System
/dev/sda1 * 2048 1026047 512000 83 Linux
/dev/sda2 1026048 250068991 124521472 8e Linux LVM

4. The LVM_member file system type shows up here:
knoppix@Microknoppix:~$ cat /etc/fstab
# DEFAULT BASE FSTAB, UNCONFIGURED
proc /proc proc noauto 0 0
sysfs /sys sysfs noauto 0 0
# Added by KNOPPIX
/dev/sda1 /media/sda1 ext4 noauto,users,exec 0 0
# Added by KNOPPIX
/dev/sr0 /media/sr0 iso9660 noauto,users,exec 0 0
# Added by KNOPPIX
/dev/sda2 /media/sda2 LVM2_member noauto,users,exec 0 0

5. Unfortunately, normal mounting won't work for LVM file systems:
knoppix@Microknoppix:~$ su
root@Microknoppix:/home/knoppix# mount /dev/sda1 /mnt/sda1
mount: mount point /mnt/sda1 does not exist

root@Microknoppix:/home/knoppix# ls /mnt
root@Microknoppix:/home/knoppix# ls /
bin etc KNOPPIX mnt modules ramdisk sbin UNIONFS
boot home lib mnt-system opt root sys usr
dev init media mnt-user proc run tmp var

Googling, it looks like I'm going to have to figure out how to
mount an LVM2_member type file system...

[Sandy (Knoppix KNode Emergency Repair)]

> Googling, it looks like I'm going to have to figure out how to
> mount an LVM2_member type file system...

To help others with the LVM file system, here's what I did.

I read the basics of LVM (almost all of which was above my head):
http://www.ibiblio.org/pub/Linux/docs/HOWTO/other-formats/html_single/LVM-HOWTO.html

Apparently you don't mount LVM partitions directly:
http://www.tuxradar.com/answers/148

These are likely the best debugging examples for mounting LVM systems:
http://pissedoffadmins.com/os/mount-unknown-filesystem-type-lvm2_member.html

Which referred to this post on how to mount LVM volumes:
http://www.fedoraforum.org/forum/archive/index.php/t-64964.html

So, I'll try those methods, and report back, so others with
LVM volumes don't have to start from scratch, like I am.

[Sandy (Knoppix Knode User)]

> I think I'll see if I can get Knoppix to delete the line
> I added into rc.local, and report back what I find out.

Deleting the lines I had added to /etc/rc.local (which was a
symbolic link) changed the situation; but didn't solve the problem.

Now, I don't get the pings on my screen as rc.local executes; but
Centos still won't boot. The white line gets 99% drawn to the right
and thats it. It just stays there.

We know rc.local is being executed, but nothing more.

Going into interactive boot mode at the grub screen, it looks like
Centos is hanging at "starting atd" (or maybe just after it).

Googling, I find a TON of people with a similar problem.

For example:
http://www.techpository.com/?page_id=1487
Where the solution was to eliminate the X11 configuration file:
# mv /etc/X11/xorg.conf /etc/X11/xorg.conf.old

This is one way to accomplish that task:
http://fertoledo.wordpress.com/2013/08/30/linux-centos-system-stops-
booting-at-atd-service/

This article implies the Nvidia drivers are the culprit:
http://forums.fedoraforum.org/showthread.php?t=228421

While this article implies yum update was the culprit:
http://scientificlinuxforum.org/index.php?showtopic=1756

And, this article says to disable the NEXT service after atd:
http://www.neowin.net/forum/topic/693590-centos-hangs-starting-up/

So, at this point, there is no dearth of culprits to examine
to find the cause of why Centos doesn't complete booting.

[Thad Floryan]

On 10/5/2013 7:13 PM, Sandy (on Knoppix) wrote:
> All I know is that this morning, Centos wouldn't boot.
> I see where it's hung, and, it's probably my fault.
> About six months ago, I hacked out an automatic script to
> ping google and other sites to log when the network goes down.
>
> The POST works fine, and the little blue bar at the bottom of
> the Centos screen works fine, but, at some point, before booting

> [...]

Might help to reveal what CentOS version you have and what 3rd-party
video software you added (re: "little blue bar at the bottom").

CentOS 6.* draws two concentric white circles while booting. Adding
a 3rd-party nVidia video driver deletes that and draws several colored
lines from left to right at the bottom of the screen when booting as
I recall.

Unless you reveal what you have and all that you've changed from the
default system setup, no one is going to be able to help you.

See these (URL boilerplate from the Yahoo "linux" group) especially
the last one about "smart questions" if you want an answer on Usenet
or any other Linux forum:

http://home.roadrunner.com/~computertaijutsu/linfaq.html
http://linux.sgms-centre.com/misc/netiquette.php
http://howto-pages.org/posting_style
http://www.catb.org/~esr/faqs/smart-questions.html

Thad

[J.O. Aho]

On 06/10/13 08:23, Sandy (Knoppix Knode User) wrote:
>> I think I'll see if I can get Knoppix to delete the line
>> I added into rc.local, and report back what I find out.
>
> Deleting the lines I had added to /etc/rc.local (which was a
> symbolic link) changed the situation; but didn't solve the problem.
>
> Now, I don't get the pings on my screen as rc.local executes; but
> Centos still won't boot. The white line gets 99% drawn to the right
> and thats it. It just stays there.
>
> We know rc.local is being executed, but nothing more.
>
> Going into interactive boot mode at the grub screen, it looks like
> Centos is hanging at "starting atd" (or maybe just after it).

Run the init up in interactive mode, and do not start the atd service
and see if you get further in your boot up sequence.

If you don't manage to enable the interactive init mode, then boot with
the centos install media (select rescue) and disable the service when
you have chrooted.


--

//Aho

[Norman Peelman]

On 10/06/2013 12:38 AM, Sandy (Knoppix KNode Emergency Repair) wrote:
> Sandy (Knoppix KNode Emergency Repair) wrote:
>
>> I think I'll see if I can get Knoppix to delete the line
>> I added into rc.local, and report back what I find out.
>
> The first problem with using Knoppix to repair a non-booting
> Centos is that it's not at all intuitive how to get Knoppix
> to actually boot on a Lenovo W510 laptop.
>

Sounds like Centos is booting to me... just comment out your script
line and reboot. Diagnose your script from the command line after that.


--
Norman
Registered Linux user #461062
AMD64X2 6400+ Ubuntu 10.04 64bit

[Jasen Betts]

Assuming they're all correct the next service after atd is X
and your nvidia drivers were invalidated by a kernel or x11 upgrade
done by yum.

If that's the case the solution is to boot into text-only (or single
user) mode and reinstall the drivers.

--
⚂⚃ 100% natural

--- news://freenews.netfront.net/ - complaints: ne...@netfront.net ---

[Sandy (Knoppix Knode User)]

Thad Floryan wrote:

> Might help to reveal what CentOS version you have and what 3rd-party
> video software you added (re: "little blue bar at the bottom").

Centos 6.4.

I was unaware that the blue/white bootup bar at the bottom of
the power-up screen was actually due to the Nvidia video driver.

The Nvidia driver was installed from the El Repo repository.

[Sandy (Knoppix rescue of Centos)]

Jasen Betts wrote:

> If that's the case the solution is to boot into text-only (or single
> user) mode and reinstall the drivers.

Yes. I will try the following.

1. I will figure out how to boot interactively, and I will say "NO"
to the atd question, and to whatever is the NEXT question after
atd starts.

2. If that doesn't solve the problem, I will manually wipe out
the X configuration file, in case it got screwed up somehow.
This I can do either from Knoppix or, if I can boot after
step 1 above, from Centos 6.

3. And, if it still doesn't work, I will boot to Knoppix and
save my data, and re-install the OS on the hdd.


Googling, I found the interactive boot procedure for Centos,
but, I haven't been able to figure out how to set up a networked
printer in Knoppix yet.

I *tried* the obvious, which was Start->Preferences->Printing
and then, from there, Add->Printer, where it asks for a
password, which is actually "admin" (and not "password" or
blank, which Googling alluded to) by default.

Try as I might, Knoppix wouldn't find my networked printer.
http://postimg.org/image/lv5sxk8x7/

[Sandy (Knoppix rescue of Centos)]

Sandy (Knoppix rescue of Centos) wrote:

> I tried the obvious, which was Start->Preferences->Printing

> and then, from there, Add->Printer, where it asks for a
> password, which is actually "admin" (and not "password" or
> blank, which Googling alluded to) by default.
>
> Try as I might, Knoppix wouldn't find my networked printer.
> http://postimg.org/image/lv5sxk8x7/

So, I typed the IP address of my printer into the Knoppix
GUI and it seemed to find the printer - but - it wants to
have password "authentication" in order to INSTALL the
printer drivers.

The problem is that blank didn't work, "password", and
"admin" (which were all suggested on the net).

So, um, what is the default Knoppix password for the
printer authorization driver installation form?

KNOPPIX NETWORKED PRINTER SETUP:
Step 1: http://postimg.org/image/cuuhr0a5z/
Step 2: http://postimg.org/image/wj2ua1g8n/
Step 3: http://postimg.org/image/xno1erxdd/
Step 4: http://postimg.org/image/3ni2cuaw1/
Step 5: http://postimg.org/image/g3y0yrwrd/
Step 6: http://postimg.org/image/62w6dnl2b/

So, um, what's the password for installing Knoppix printer drivers,
if it's not blank, "root", "admin", or "password"?

[Sandy (Knoppix rescue of Centos)]

Norman Peelman wrote:

> Sounds like Centos is booting to me... just comment out your script
> line and reboot. Diagnose your script from the command line after
that.

I removed the lines from rc.local, and, now Centos no longer
prints to the screen what was previously running in the background.

However, Centos 6 still doesn't boot.

It's stuck at the "starting atd" step (either at the step, or
right after it).

Googling for "starting atd centos", this problem turns out to be
*very* common in Centos, where most solutions involved a Yum
update, or removal of Xorg.conf, or turning off atd (which doesn't
seem to be all that necessary in the first place).

Of course, it could be the step AFTER atd starts up, so, I'll
just have to try to disable it to see what happens (and report
back).

[Sandy (Knoppix rescue of Centos)]

Sandy (Knoppix rescue of Centos) wrote:

> So, um, what's the password for installing Knoppix printer drivers,
> if it's not blank, "root", "admin", or "password"?

Well, that was odd.

While Knoppix repeated denied any password I could come up with
(including a blank password), it actually worked to set up the
printer driver.

So, that's highly unintuitive of Knoppix, but, what the heck.
What do I want for free. :)

http://postimg.org/image/xp551mhsp/

[Sandy]

Jasen Betts wrote:

> If that's the case the solution is to boot into text-only (or single
> user) mode and reinstall the drivers.

I'm having trouble booting into single-user mode on Centos 6
so that I can update the Lenovo W510 to the latest Nvidia driver
as per this instruction set found by googling:

1. sudo yum --enablerepo elrepo-testing remove kmod-nvidia
2. sudo yum --dsablerepo=\* --enablerepo=elrepo-testing remove nvidia-
x11-drv-32-bit nvidia-x11-drv-64-bit
3. sudo reboot
4. sudo yum --disablerepo=\* --enablerepo=elrepo install nvidia-x11-
drv-64bit
5. /usr/bin/nvidia-settings (save results to the X Configuration File)
6. sudo reboot


Googling for how to boot Centos to single-user mode, I find this:
a. Boot the laptop and wait for the grub splash screen
b. Interrupt the boot process by pressing the space bar
c. Interrup that by pressing the "a" key
d. Write your own boot command at the prompt

So, um, what boot command do I enter to boot with nvidia drivers
(and not nouveau default drivers)?

[Aragorn]

On Monday 07 October 2013 18:22, Sandy conveyed the following to
alt.os.linux...

Something like... (assuming /boot is a separate filesystem)

kernel /linux root=/dev/sda2 init=/bin/bash

CentOS is a RedHat clone, and RedHat has switched to systemd now, which
is an entirely different init system than traditional System V init.

--
= Aragorn =
GNU/Linux user #223157 - http://www.linuxcounter.net

[Sandy]

Actually, just to update that statement, I started with this:
knoppix64 xmodule=nv acpi=off nolapic hpet=off no3d

But, this also booted the Lenovo W510 to Knoppix 64-bit:
knoppix64 xmodule=nv acpi=off nolapic hpet=off

And, so did this boot the Lenovo W510 to Knoppx64:
knoppix64 xmodule=nv acpi=off nolapic

By eliminating the last option, one by one, this worked:
knoppix64 xmodule=nv acpi=off

However, this failed to boot the W510 using the Knoppix 7 DVD:
knoppix64 xmodule=nv

[Sandy]

Aragorn wrote:

> Something like... (assuming /boot is a separate filesystem)
> kernel /linux root=/dev/sda2 init=/bin/bash

Thanks. I'll try that command and report back.

I do know that the filesystem is LVM, so I don't think
there is a separate root. It's managed under all sorts
of something else (miserable file system that LVM is).

[Aragorn]

On Monday 07 October 2013 18:59, Sandy conveyed the following to
alt.os.linux...

In that case, the kernel to boot should be spelled out as /boot/vmlinuz
(or whatever the file's name is), and you should of course also use the
correct designation for the root filesystem.

[Sandy]

Aragorn wrote:

> the kernel to boot should be spelled out as /boot/vmlinuz
> (or whatever the file's name is),

This is what the normal boot command appears to be:
<E=us rd_NO_DM crashkernel=auto nouveau.modeset=0 rdblacklist=nouveau

I tried putting " single" at the end of that, but it failed to boot.
Does anything above make sense to anyone?

Note: Nouveau, from googling, is the default video driver; but
my question is mostly how to change that line above so that the
Lenovo W510 doesn't run the atd command while booting.

[Sandy]

Aragorn wrote:

> In that case, the kernel to boot should be spelled out as
/boot/vmlinuz
> (or whatever the file's name is), and you should of course also use
the
> correct designation for the root filesystem.

Pressing "a" at the boot selection gave the following line:
grub append>
ro
root=/dev/mapper/vg_burns_lv_root
rd_NO_LUKS
LANG=en_US.UTF-8
rd_LVM_LV=vg_burns/lv_swap
rd_NO_MD
rd_LVM_LV=vg_burns/lv_root
SYSFONT=latarcyrheb_sun16
rhgb
quiet
KEYBOARDTYPE=pc
KEYTABLE=us
rd_NO_DM
crashkernel=auto

Pressing "e" at the boot selection gave the following lines:
GNU GRUB version 0.97 (634K lower / 3073520K upper memory)
----
root (hd0,0)
kernel /vmlinuz-2.6.32-358.14.1.el6.x86_64 {huge line above}
initrd /initramfs-2.6.32-358.14.1.el6.x86_64.img

Can you advise me what command line I would use to get diagnostic
information as to why Centos will boot to the command line,
but, stops either at atd or X (which is after atd)?

[Sandy]

J.O. Aho wrote:
h

> Run the init up in interactive mode,
> and do not start the atd service

I'd love to do that, if I knew what it meant to
"run the init up in interactive mode".

Googling for that phrase, I found this on Centos.org:

- On an x86 system using GRUB, use the following steps
to boot into single-user mode:
- At the GRUB splash screen at boot time, press any key
to enter the GRUB interactive menu.
- Select Red Hat Enterprise Linux with the version of
the kernel that you wish to boot and type a to append the line.
- Go to the end of the line and type single as a separate word
(press the Spacebar and then type single).
- Press Enter to exit edit mode.

So, I changed THIS LINE by substituting "single" for "rhgb"
and I removed the "quiet" and then booted to a command line:

grub append>
ro
root=/dev/mapper/vg_burns_lv_root
rd_NO_LUKS
LANG=en_US.UTF-8
rd_LVM_LV=vg_burns/lv_swap
rd_NO_MD
rd_LVM_LV=vg_burns/lv_root
SYSFONT=latarcyrheb_sun16

rhgb <==== I changed this to "single"
quiet <==== I removed this
KEYBOARDTYPE=pc
KEYTABLE=us
rd_NO_DM
crashkernel=auto

At that command line, I removed the Xorg.conf file and rebooted
but that didn't change anything:
# cd /etc/X11
# mv xorg.cong xorg.conf.bad
# reboot

I also removed the NVIDIA drivers (since I suspect them somewhow):
# yum --enablerepo elrepo-testing remove kmod-nvidia
# yum --disablerepo=\* --enablerepo=elrepo-testing remove nvidia-x11-
drv-32bit
# reboot

Unfortunately, that resulted in the entire boot screen hanging
at the exact same point as before (with the long white & blue
Centos 6.4 bar at the bottom of the screen, only the entire screen
was 1/16th the size of the real screen, tucked up in the top left
corner of the screen).

When I tried to re-install the NVIDIA drivers, I realized that
the command-line mode doesn't have any networking, so it failed:
# yum --enablerepo elrepo install kmod-nvidia
# yum --disablerepo=\* --enablerepo=elrepo install nvidia-x11-
drv-32bit
# reboot

But, nothing has resulted in those efforts, other than that the
command line mode now only takes up a tiny portion of the top
left corner of the screen.

Is there a way to boot to a prompt where I can turn off atd
and possibly X (which comes after atd)?

[Aragorn]

On Tuesday 08 October 2013 04:47, Sandy conveyed the following to
alt.os.linux...

Try adding "nosplash" to the kernel boot options. That way you should
be able to see what service fails. On the other hand, systemd does
parallel starting of services, so the information it throws out on the
screen may not actually related to the hang...

[sandy]

Aragorn wrote:
> Try adding "nosplash" to the kernel boot options.

Thanks for sticking with me.

I'm about ready to give up as it really shouldn't be
all this hard to simply get Centos to ask me what
services it wants to start so that I could turn
off atd to see if that is the problem or not.

This is what has been there all along:

grub append> ro root=/dev/mapper/vg_burns_lv_root rd_NO_LUKS
LANG=en_US.UTF-8 rd_LVM_LV=vg_burns/lv_swap rd_NO_MD
rd_LVM_LV=vg_burns/lv_root SYSFONT=latarcyrheb_sun16 rhgb quiet
KEYBOARDTYPE=pc KEYTABLE=us rd_NO_DM crashkernel=auto

I'll add "nosplash" to the end of this line
(and I'll remove the "quiet"):

grub append> ro root=/dev/mapper/vg_burns_lv_root rd_NO_LUKS
LANG=en_US.UTF-8 rd_LVM_LV=vg_burns/lv_swap rd_NO_MD
rd_LVM_LV=vg_burns/lv_root SYSFONT=latarcyrheb_sun16 rhgb

KEYBOARDTYPE=pc KEYTABLE=us rd_NO_DM crashkernel=auto
nosplash

And, I'll let you know what happens in a few minutes
(it takes me a while to boot back to Knoppix and then
to set up the nntp client all over again).

[sandy]

sandy wrote:

> I'll add "nosplash" to the end of this line
> (and I'll remove the "quiet"):
>
> grub append> ro root=/dev/mapper/vg_burns_lv_root rd_NO_LUKS
> LANG=en_US.UTF-8 rd_LVM_LV=vg_burns/lv_swap rd_NO_MD
> rd_LVM_LV=vg_burns/lv_root SYSFONT=latarcyrheb_sun16 rhgb
> KEYBOARDTYPE=pc KEYTABLE=us rd_NO_DM crashkernel=auto
> nosplash

By adding the nosplash & removing the quiet, the same thing
happened that the booting bar stopped at the same point as
before, but, a new additional error finally showed up:

ADDRCONF(NETDEV_CHANGE): wlan0: link becomes ready
padlock: VIA PadLock not detected.

Googling, I find ...

FOR THE ADDRCONF error:
It seems that it's just a wireless configuration message.

FOR THE PADLOCK ERROR:
If encryption is enabled on the boot device during system
installation, the following message will be logged during
system boot: padlock: VIA PadLock not detected.
This message can safely be ignored.

Neither one seems to be all that important (I could be wrong,
so that's why I report them both).

Isn't there just a way to one-by-one say yes or no to the
services as Centos 6.4 boots?

[J.O. Aho]

On 08/10/13 04:59, Sandy wrote:
> J.O. Aho wrote:
> h
>> Run the init up in interactive mode,
>> and do not start the atd service
>
> I'd love to do that, if I knew what it meant to
> "run the init up in interactive mode".
>

> Unfortunately, that resulted in the entire boot screen hanging
> at the exact same point as before (with the long white & blue
> Centos 6.4 bar at the bottom of the screen, only the entire screen
> was 1/16th the size of the real screen, tucked up in the top left
> corner of the screen).

You need to have the verbose mode enabled when you boot, the one showing
all the text while booting, think you can do that just by pressing the
key 'v' and should be mentioned in the redhat manual.

> But, nothing has resulted in those efforts, other than that the
> command line mode now only takes up a tiny portion of the top
> left corner of the screen.
>
> Is there a way to boot to a prompt where I can turn off atd
> and possibly X (which comes after atd)?

You will see a message telling you that you can press 'i' to enter the
interactive mode, you need to be fast here or else you don't.

--

//Aho

[J.O. Aho]

On 07/10/13 18:35, Aragorn wrote:

> CentOS is a RedHat clone, and RedHat has switched to systemd now, which
> is an entirely different init system than traditional System V init.

RedHat uses systemd only in Fedora, no RHEL/CentOS which is based on
Fedora 15 or later, so they do not use systemd yet, maybe with the
RHEL7/CentOS7 release it may change.

--

//Aho

[Aragorn]

On Tuesday 08 October 2013 07:40, J.O. Aho conveyed the following to
alt.os.linux...

Well, it will, eventually. "We are RedHat. Common sense is futile.
You will be assimilated."

[sandy]

J.O. Aho wrote:

> You need to have the verbose mode enabled

> think you can do that just by pressing the
> key 'v'

I haven't seen this message, but, I will add "verbose" to
the boot instructions (plus I've been removing "quiet") and
see what happens.

> You will see a message telling you that you can press 'i'

> to enter interactive mode

I haven't seen that message yet, so I'll be poised over the i
key and see if I can get to the all-important interactive mode.

[sandy]

On Tue, 08 Oct 2013 06:47:06 +0200, J.O. Aho wrote:
> You will see a message telling you that you can press 'i' to enter the
> interactive mode, you need to be fast here or else you don't.

I never saw the "i" prompt, but, I hit the "i" key a dozen times
while it was booting from grub. I was hitting the "i" key a whole
bunch of times *before* and *after* I had pressed the spacebar
to halt grub.

Somehow, I got into an interactive mode ...
Here's what it says on the screen:
Welcome to CentOS
Starting udev: udevd[626]: unknown key 'PHYSDEVBUS' in /etc/udev/rules.d/80-hasp.rules:6
[OK]
Setting hostname sandy: [OK]
Setting up Logical Volume Management: 3 logical volume(s) in volume group "vg_burns" now active.
[OK]
Checking filesystems
/dev/mapper/vg_burns-lv_root: clean 246491/1281120 files, 2359700/5120000 blocks
/dev/sda1; clean, 63/128016 files, 140551/512000 blocks
/dev/mapper/vg_burns-lv_home: clean, 103792/5349376 files, 19077657/21385216 blocks
[OK]
Remounting root filesystem in read-write mode [OK]
Mounting local filesystems: [OK]
Enabling local filesystem quotas: [OK]
Enabling /etc/fstab swaps: [OK]
Entering interactive startup
---

Here's where I can interact with the boot sequence
Start service systat (Y)es/(N)o/(C)ontinue? [Y]
Calling the system activity data collector (sadc):
Start service lvm2-monitor (Y)es/(N)o/(C)ontinue? [Y]
Starting monitoring for VG vg_burns: 3 logical volume(s) in group "vg_burns" monitored
Start service cygconfig (Y)es/(N)o/(C)ontinue? [Y]
Starting cygconfig service: [OK]
Start service iscid (Y)es/(N)o/(C)ontinue? [Y]
Start service ip6tables (Y)es/(N)o/(C)ontinue? [Y]
ip6tables: Applying firewall rules [OK]
ip6tables: Loading additional modules: nf_conntrack_netbios[OK]
Start service iptables (Y)es/(N)o/(C)ontinue? [Y]
iptables: Applying firewall rules [OK]
iptables: Loading additional modules: nf_conntrack_netbios[OK]
Start service network (Y)es/(N)o/(C)ontinue? [Y]
Bringing up loopback interface [OK]
Start service auto_WIRELESS_SSID (Y)es/(N)o/(C)ontinue? [Y]
Bringing up interface auto_WIRELESS_SSID: Device does not seem to be present, delaying initialization
[FAILED]
Start service auditd (Y)es/(N)o/(C)ontinue? [Y]
Starting auditd
Start service portreserve (Y)es/(N)o/(C)ontinue? [Y]
Starting portreserve: [OK]
Start service rsyslog (Y)es/(N)o/(C)ontinue? [Y]
Starting system logger [OK]
Start service cpuspeed (Y)es/(N)o/(C)ontinue? [Y]
Enabling ondemand cpu frequency scaling [OK]
Start service irqbalance (Y)es/(N)o/(C)ontinue? [Y]
Starting irqbalance [OK]
Start service iscsi (Y)es/(N)o/(C)ontinue? [Y]
Start service rpcbind (Y)es/(N)o/(C)ontinue? [Y]
Starting rpcbind [OK]
Start service mdmonitor (Y)es/(N)o/(C)ontinue? [Y]
Start service messagebus (Y)es/(N)o/(C)ontinue? [Y]
Starting system message bus [OK]
Start service NetworkManager (Y)es/(N)o/(C)ontinue? [Y]
Setting network parameters... [ok]
Starting NetworkManager daemon: [OK]
Start service avahi-daemon(Y)es/(N)o/(C)ontinue? [Y]
Starting Avahi daemon...[OK]
Start service nfslock (Y)es/(N)o/(C)ontinue? [Y]
Starting NFS statd[OK]
Start service openvpn (Y)es/(N)o/(C)ontinue? [Y]
Starting openvpn [FAILED]
Start service rpcgssd (Y)es/(N)o/(C)ontinue? [Y]
Start service rpcidmapd (Y)es/(N)o/(C)ontinue? [Y]
Starting rpcidmapd [OK]
Start service blk-availability (Y)es/(N)o/(C)ontinue? [Y]
Start service cups (Y)es/(N)o/(C)ontinue? [Y]
Starting cups [OK]
Start service acpid (Y)es/(N)o/(C)ontinue? [Y]
Starting acpi daemon:[OK]
Start service haldaemon (Y)es/(N)o/(C)ontinue? [Y]
Starting HAL daemon: [OK]
Start service lm_sensors (Y)es/(N)o/(C)ontinue? [Y]
Starting lm_sensors: loading module coretemp [OK]
Start service udev-post (Y)es/(N)o/(C)ontinue? [Y]
Retrigger failed udev events [OK]
Start service askusbd (Y)es/(N)o/(C)ontinue? [Y]
Starting AKSUSB daemon: [OK]
Starting WINEHASP daemon: [OK]
Starting HASPLM daemon: [OK]
Start service autofs (Y)es/(N)o/(C)ontinue? [Y]
Loading autofs4: [OK]
Starting automount: [OK]
Start service ncsd (Y)es/(N)o/(C)ontinue? [Y]
Starting ncsd: [OK]
Start service stunnel (Y)es/(N)o/(C)ontinue? [Y]
Starting stunnel services:[OK]
Start service bluetooth (Y)es/(N)o/(C)ontinue? [Y]
Enabling bluetooth devices:[OK]
Start service sshd (Y)es/(N)o/(C)ontinue? [Y]
Starting sshd: [OK]
Start service spice-vdagentd (Y)es/(N)o/(C)ontinue? [Y]
Start service postfix (Y)es/(N)o/(C)ontinue? [Y]
Starting postfix: [OK]
Start service abrt-ccpp (Y)es/(N)o/(C)ontinue? [Y]
Start service abrtd (Y)es/(N)o/(C)ontinue? [Y]
Starting abrt daemon: [OK]
Start service abrt-oops (Y)es/(N)o/(C)ontinue? [Y]
Start service ksm (Y)es/(N)o/(C)ontinue? [Y]
Starting ksm: [OK]
Start service ksmtuned (Y)es/(N)o/(C)ontinue? [Y]
Start service qpidd (Y)es/(N)o/(C)ontinue? [Y]
Starting Qpid AMQP daemon: [OK]
Start service nasd (Y)es/(N)o/(C)ontinue? [Y]
Start service crond (Y)es/(N)o/(C)ontinue? [Y]
Starting crond: [OK]
Start service atd (Y)es/(N)o/(C)ontinue? [Y]
Starting atd: [OK]
Start service libvirt-guests (Y)es/(N)o/(C)ontinue? [Y]
Start service local (Y)es/(N)o/(C)ontinue? [Y]
THIS HUNG forever ... forcing a reboot.

So, I will try again, only this time, I won't start
the two failed services (auto_WIRELESS_SSID, openvpn)
and I won't start "local" (whatever that is).

BTW, when it asks Yes/No/Continue, what does the
continue actually do?

[sandy]

On Tue, 08 Oct 2013 17:17:53 +0000, sandy wrote:

> Start service atd (Y)es/(N)o/(C)ontinue? [Y]
> Starting atd: [OK]
> Start service libvirt-guests (Y)es/(N)o/(C)ontinue? [Y]
> Start service local (Y)es/(N)o/(C)ontinue? [Y]
> THIS HUNG forever ... forcing a reboot.

It's interesting to note that atd does seem to work,
but, it fails to boot soon thereafter.

I again booted to grub and pressed 'i' a zillion times
until it put me into interactive mode.

I said (N)o to the two prior failed services:
auto_WIRELESS_SSID, openvpn
and, I said (N)o to the "local" service (whatever that is).

But, it hung whether I pressed Y or N.

> BTW, when it asks Yes/No/Continue, what does the
> continue actually do?

Hmm. Next time, I'll press Continue for the "local" service.

[sandy]

On Tue, 08 Oct 2013 17:26:16 +0000, sandy wrote:

> Hmm. Next time, I'll press Continue for the "local" service.

Well, it immediately went to the CentOS 6 splash screen
(the one with the multicolored boxes to the left and the
words "Community ENTerprise Operating System" underneath).

But, nothing else happened.
So Centos is hung.

I'm going to try again, saying No to every service that
I don't know what it does & report back.

[sandy]

On Tue, 08 Oct 2013 17:31:54 +0000, sandy wrote:

> I'm going to try again, saying No to every service that
> I don't know what it does & report back.

Saying no to every service, including "local", resulted
in a bunch of lines saying:

init: prefdm main process (2122) terminated with status 1
init: prefdm main process ended, respawning

It respawned ten times, and then reported:

init: prefdm main process (2122) terminated with status 1
init: prefdm respawning too fast, stopped

So, that was a bust.

[Aragorn]

On Tuesday 08 October 2013 19:39, sandy conveyed the following to
alt.os.linux...

> On Tue, 08 Oct 2013 17:31:54 +0000, sandy wrote:
>
>> I'm going to try again, saying No to every service that
>> I don't know what it does & report back.
>
> Saying no to every service, including "local", resulted
> in a bunch of lines saying:

The "local" service is probably just rc.local or its equivalent, which
is used for adding custom services, which get executed after all other
services initialization has completed.

> init: prefdm main process (2122) terminated with status 1
> init: prefdm main process ended, respawning
>
> It respawned ten times, and then reported:

I could be wrong, but I believe that prefdm is a service which starts
the default display manager, whichever that one is. In CentOS, this
would probably be GDM (GNOME Display Manager).

The display manager, in layman's terms, is the graphical login screen.
It makes sense that it would attempt to respawn upon failure, but
eventually, it will indeed be respawning too fast if the error was not a
transient one, and then it will be temporarily disabled.

> init: prefdm main process (2122) terminated with status 1
> init: prefdm respawning too fast, stopped

Status 1 indicates an error of some sorts. Success is 0.

[David W. Hodgins]

On Tue, 08 Oct 2013 13:39:42 -0400, sandy <sa...@is.invalid> wrote:

> init: prefdm main process (2122) terminated with status 1
> init: prefdm respawning too fast, stopped
>
> So, that was a bust.

Try just appending " 3" (without the quotes) to the kernel options
to get a text login.

Regards, Dave Hodgins

--
Change nomail.afraid.org to ody.ca to reply by email.
(nomail.afraid.org has been set up specifically for
use in usenet. Feel free to use it yourself.)

[Robert Newson]

On 08/10/13 18:17, sandy wrote:
...

> BTW, when it asks Yes/No/Continue, what does the
> continue actually do?

IIRC:

Y - Yes: do the action
N - No: don't do the action
C - Continue with no more prompts (like a normal non-interactive boot).

[sandy]

David W. Hodgins wrote:

> Try just appending " 3" (without the quotes) to the
> kernel options to get a text login.

Hi Dave,
I appreciate the advice.

This really should not be all this difficult.

I'm not sure how that's different though from using "single"
in the boot options (which also gets me to the command prompt).

Since it boots fine to the command prompt, my guess is that
the window system is hosed.

I'm trying to figure out how to get back to a known-good
X-configuration file and default drivers for the Lenovo W510.

But, I may just give up and reinstall the OS, as, there seems
to be a dearth of diagnostic capabilities in Centos.

[sandy]

Aragorn wrote:

> The "local" service is probably just rc.local or its equivalent, which
> is used for adding custom services, which get executed after all other
> services initialization has completed.

Do you think it prudent then to just boot to the command line
and delete rc.local?

Or is it required for the window system to work?

[Bit Twister]

On Wed, 09 Oct 2013 10:31:57 +0000, sandy wrote:
>
> Do you think it prudent then to just boot to the command line
> and delete rc.local?

You could just rename it.
mv rc.local broke_rc.local

> Or is it required for the window system to work?

Not required.

[sandy]

Aragorn wrote:

> I could be wrong, but I believe that prefdm is a service which starts
> the default display manager, whichever that one is. In CentOS, this
> would probably be GDM (GNOME Display Manager).

This makes sense since it appears that the preferred display manager
(GNOME) just isn't coming up.

My suspicions are on the xorg.conf file in combination with the
nvidia drivers.

Perhaps the Centos was auto-updated out from under me, which hosed
the display. They really shouldn't do that - but - this 'is' Linux
which is like the wild west of operating systems where anything goes.

So, it's up to me to recover from the damage.

The biggest problem here is that I do not have any good idea HOW
to recover when the operating system is auto-updated out from
under me.

Like a good citizen, my nvidia drivers came from the ElRepo
repository, which is "supposed" to be tested, so, now I'm the
one stuck with an unbootable display manager.

As a last-ditch effort before I simply wipe out the operating
system and start fresh with a different OS, do you have any
advice for how to return the display manager back to where it
belongs?

At this point, I suspect the xorg.conf file and the nvidia drivers.

[Aragorn]

On Wednesday 09 October 2013 12:36, sandy conveyed the following to
alt.os.linux...

> Aragorn wrote:
>
>> I could be wrong, but I believe that prefdm is a service which starts
>> the default display manager, whichever that one is. In CentOS, this
>> would probably be GDM (GNOME Display Manager).
>
> This makes sense since it appears that the preferred display manager
> (GNOME) just isn't coming up.
>
> My suspicions are on the xorg.conf file in combination with the
> nvidia drivers.

I don't think that the xorg.conf file would be bad, but I do think that
the nvidia drivers might be problematic. The nVidia developers haven
been removing some features from the latest drivers so as to be on par
with Windows, which doesn't have those features. This may have broken
things in your particular setup.

> Perhaps the Centos was auto-updated out from under me, which hosed
> the display.

Never allow for automatic updates. You never know what packages your
system is pulling in.

> They really shouldn't do that - but - this 'is' Linux which is like
> the wild west of operating systems where anything goes.

That's nonsense. Microsoft is a lot worse in that regard, and at least
in GNU/Linux, you can choose to update what you want. But of course, if
you allow it to update itself automatically, then you're asking for
trouble.

> So, it's up to me to recover from the damage.

Yes.

> The biggest problem here is that I do not have any good idea HOW
> to recover when the operating system is auto-updated out from
> under me.

Disabling automatic updates should be your first priority.

> Like a good citizen, my nvidia drivers came from the ElRepo
> repository, which is "supposed" to be tested, so, now I'm the
> one stuck with an unbootable display manager.

There are other display managers than GDM. Just because RedHat (and by
consequence CentOS) prefers GDM doesn't mean you have to use that. You
can just as easily use XDM or KDM.

I myself don't even use any display manager. I start X11 manually after
login from a character mode virtual console.

> As a last-ditch effort before I simply wipe out the operating
> system and start fresh with a different OS, do you have any
> advice for how to return the display manager back to where it
> belongs?

GDM is something I wouldn't touch with a pole, so I'm afraid the answer
is "no". :-/

> At this point, I suspect the xorg.conf file and the nvidia drivers.

The xorg.conf is probably fine. The drivers... I guess it depends on
what graphics adapter you have in that system. If all else fails, try
getting the nouveau drivers back to work. They may not offer you all
the bells and whistles of the proprietary drivers, but at least they do
work.

[J.O. Aho]

On 09/10/13 12:36, sandy wrote:

> The biggest problem here is that I do not have any good idea HOW
> to recover when the operating system is auto-updated out from
> under me.

Time to learn, you can always revert to older version of packages.

> Like a good citizen, my nvidia drivers came from the ElRepo
> repository, which is "supposed" to be tested, so, now I'm the
> one stuck with an unbootable display manager.

you can always uninstall it and it will not stuck there, you can do as
many others and start X manually at need.

I recommend you see to have always two kernel versions installed, the
current one and the previous one, this way you know that the previous
one did work with it's driver without issues and can fall back if the
new one don't work properly. No, I still don't use RedHat, left that
behind me a long time ago and using a distribution which allows me to
administrate which kernel versions should be installed and part of the
boot manager options.
I do know from a previous employment that CentOS5 line does keep older
kernels, not sure about how it's in CentOS6.

> As a last-ditch effort before I simply wipe out the operating
> system and start fresh with a different OS

I guess you mean like microsoft windows? We got a hell of trouble at
work where one set of patches together changed behaivour on a specific
date and this wasn't documented in the patch deskcription, we managed to
find some help at symantic.

> At this point, I suspect the xorg.conf file and the nvidia drivers.

If you have a broken xorg.conf, you most likely end up in console mode.
Sure broken nvidia driver could cause the issue, but just boot into
single mode or use the centos install media and boot into recovery, you
can check the Xorg.0.log and see what went wrong.


--

//Aho

[Eef Hartman]

sandy <sa...@is.invalid> wrote:
> The biggest problem here is that I do not have any good idea HOW
> to recover when the operating system is auto-updated out from
> under me.
>
> Like a good citizen, my nvidia drivers came from the ElRepo
> repository, which is "supposed" to be tested, so, now I'm the
> one stuck with an unbootable display manager.

IF you're using the proprietary NVidia drivers (and not Nouveau or nv,
which are built-into the kernel itself): after _every_ kernel update
you must rebuilt the kernel driver (nvidia.ko).
This is done most easily by booting to runlevel "3" (which is full
multi-user but _without_ starting the graphics "X" system), logging
in as root and executing:
/etc/init.d/nvidia setup
which will build a new driver for the current kernel and then start
X
If you're more comfortable with the system, you can enable DKMS (Dynamic
Kernel Management System), which will auto-rebuild all non-kernel
supplied drivers which have been identifeid in its config - this is
not trivial to setup, but will prevent your problem from happening
again.

I concur with the others that normally you shouldn't use auto-update,
when you hand-update you _know_ what has been changed in the system and
especially kernel updates are always to be wary of.
BTW: CentOS normally _keeps_ the last few kernels around, so from grub
you should be able to boot into those previous (and probably working)
kernels.
--
*****************************************************************
** Eef Hartman, Delft University of Technology, dept. EWI/CE **
** e-mail: E.J.M....@tudelft.nl - phone: +31-15-27 82525 **
*****************************************************************

[sandy]

On Tue, 08 Oct 2013 21:28:31 +0100, Robert Newson wrote:

> Y - Yes: do the action
> N - No: don't do the action
> C - Continue with no more prompts (like a normal non-interactive boot).

Ahhhh.

It never occurred to me that the "Continue" had anything to do with
future questions.

Basically, what you're saying Continue does is it is really enters
a YES to that question, PLUS a YES to all other future questions!

So, the Continue is like a super-duper Yes command.

This concept had not occurred to me.
Thank you for clarifying it.

Now that I know what it is, it's "intuitive" moving forward!

[David W. Hodgins]

On Wed, 09 Oct 2013 06:31:57 -0400, sandy <sa...@is.invalid> wrote:

> Aragorn wrote:
>
>> The "local" service is probably just rc.local or its equivalent, which
>> is used for adding custom services, which get executed after all other
>> services initialization has completed.
>
> Do you think it prudent then to just boot to the command line
> and delete rc.local?

Given that you can boot to the command line, you can stop worrying
about atd or rc.local. They are not the cause of the problem, as
they have both completed ok, by time the login prompt is shown.

> Or is it required for the window system to work?

Not related. Now try booting with the kernel option xdriver=vesa.
Note, do not include the " 3".

If that works, use whatever tools are used in centos, to reinstall
the graphics module.

[billy]

Eef Hartman wrote:

> F you're using the proprietary NVidia drivers (and not Nouveau or nv,

> which are built-into the kernel itself): after every kernel update

> you must rebuilt the kernel driver (nvidia.ko).

Yikes. OK. Well, I'm not using Nvidia drivers because I feel like it.
I'm using them because the other drivers didn't work.

However, I *may* be able to at least boot using the Nouveau driver.

Is there a way to boot to the Nouveau driver instead of to the
Nvidia driver?

> This is done most easily by booting to runlevel "3" (which is full

> multi-user but without starting the graphics "X" system), logging

> in as root and executing:
> /etc/init.d/nvidia setup

Googling for how to boot to runlevel 3, I find this reference:
http://www.brunolinux.com/05-Configuring_Your_System/Grub_boot_runlevel-3.html

Based on that, I will simply append a "3" to the end of the
grub boot line and let you know if the nvidia.setup exists and works.

Much appreciate the advice, as I'm out of my league.

> I concur with the others that normally you shouldn't use auto-update,

> when you hand-update you know what has been changed in the system and

> especially kernel updates are always to be wary of.

How can I tell if I am using auto-update?
I 'think' I'm using it (since I didn't manually upgrade from Centos
6.3 to 6.4) but how can I tell?

> BTW: CentOS normally keeps the last few kernels around, so from grub

> you should be able to boot into those previous (and probably working)
> kernels.

So *that* is why there are five or six grub lines!
I never knew what they were doing there!

I'll write down what they say and report back.

[billy]

David W. Hodgins wrote:

> Not related. Now try booting with the kernel option xdriver=vesa.
> Note, do not include the " 3".

I'll try this and report back.
This makes sense as it should just use a default driver.

[sandy]

On Tue, 08 Oct 2013 16:27:49 -0400, David W. Hodgins wrote:

> Try just appending " 3" (without the quotes) to the kernel options
> to get a text login.

That is the greatest suggestion of them all!

The beauty of the "3" (over the "i") is that both booted to the command
line, but, the 3 had networking!

Woo hoo!

Once I have networking, I can install the nvidia drivers from elrepo.
Let me try that, and report back!

[Eef Hartman]

In alt.os.linux sandy <sa...@is.invalid> wrote:
> That is the greatest suggestion of them all!
>
> The beauty of the "3" (over the "i") is that both booted to the command
> line, but, the 3 had networking!

Runlevels in most Linux distributions:
1 (or single), single user level, only the console is active.
limited startup, often without login at all
3 full multi-user level, with networking and all
just without starting up the graphical subsystem/login
5 ?DM-based login, X11 graphics server started, further the same as 3

2 is mostly a more limited multi-user system, 4 often isn't used
at all (but in Slackware is what 5 is in others, slackware thus
doesn't use 5).

[sandy]

On Wed, 09 Oct 2013 22:22:56 +0000, sandy wrote:

> Once I have networking, I can install the nvidia drivers from elrepo.
> Let me try that, and report back!

Drat!

Once booted to the command line with networking (i.e., init 3),
I ran "yum update" and it modified 89 packages.

It didn't help to try to boot to the older kernels which were
changed by the "yum update" from:
5. CentOS (2.6.32-358.18.1.el6.x86_64)
4. CentOS (2.6.32-358.6.2.el6.x86_64)
3. CentOS (2.6.32-358.2.1.el6.x86_64)
2. CentOS (2.6.32-279.19.1.el6.x86_64)
1. CentOS (2.6.32-279.5.2.el6.x86_64)

To add this kernel:
5. CentOS (2.6.32-358.14.1.el6.x86_64)

Rebooting didn't solve anything, but I had noticed an error with
openvpn, so I ran "yum remove openvpn"; but that didn't solve
the problem either.

Then I ran "yum --enablerepo elrepo install kmod-nvidia" which
also installed the dependency "nvidia-x11-drv.x86_64 0:325.15-1".

Still no boot at init 5.

Then I tried to modify the grub line (using "a") to remove
"quiet" and add "xdriver=vesa"; but that didn't work, other
than to report the error:

ADDRCONF(NETDEV_CHANGE): wlan0: link becomes ready

Intel AES-NI Instructions are not detected.

Then, I tried booting by removing 'quiet' and replacing it
with "nomodeset"; but got exactly the same error as above.

Then I tried arbitrary combinations of the grub line, removing
items that seemed unnecessary, all to no avail.

(I wish there was a minimum grub line somewhere.)

So, at this point, I can easily boot to the command line,
but I have absolutely no idea WHY the graphical environment
won't come up.

But, at least I have networking at the command line.
Any suggestions?

[unruh]

On 2013-10-09, Eef Hartman <E.J.M....@tudelft.nl> wrote:
> In alt.os.linux sandy <sa...@is.invalid> wrote:
>> That is the greatest suggestion of them all!
>>
>> The beauty of the "3" (over the "i") is that both booted to the command
>> line, but, the 3 had networking!
>
> Runlevels in most Linux distributions:
> 1 (or single), single user level, only the console is active.
> limited startup, often without login at all
> 3 full multi-user level, with networking and all
> just without starting up the graphical subsystem/login
> 5 ?DM-based login, X11 graphics server started, further the same as 3

I thought that Debian had a very different numbering scheme for the
runlevels just like slackware does as you point out below. It would be
really nice if they all agreed on this, but I guess that is too much to
ask. I guess an anticompetitive barrier to switching distros.

[sandy]

Eef Hartman wrote:

> 1 (or single), single user level,

> 3 full multi-user level, with networking

> 5 X11 graphics server started

So, given I can easily boot to run level 3, is there a standard
diagnostic sequence to follow to figure out why one can't get
from run level 3 to run level 5?

[sandy]

Bit Twister wrote:

> You could just rename it.
> mv rc.local broke_rc.local

> Not required.

I'm going to move it.
At this point, the entire OS is hosed anyway, so, there's not
much more I can do to it.

If I can't fix it soon, I'm going to have to give up, and
re-install some other-than-CentOS OS, because this is crazy.

I'll let you know what happens when I remove the rc.local
and reboot (I'm on Knoppix now so it's a pain switching
back and forth and setting everything up in Knoppix just to
lose it again).

[John Hasler]

unruh writes:
> I thought that Debian had a very different numbering scheme for the
> runlevels just like slackware does as you point out below.

Debian has no default numbering system for the runlevels. They leave
that for the admin. You can set them up however you wish.
--
John Hasler
jha...@newsguy.com
Dancing Horse Hill
Elmwood, WI USA

[David W. Hodgins]

On Wed, 09 Oct 2013 18:29:27 -0400, Eef Hartman <E.J.M....@tudelft.nl> wrote:

> In alt.os.linux sandy <sa...@is.invalid> wrote:
>> That is the greatest suggestion of them all!
>>
>> The beauty of the "3" (over the "i") is that both booted to the command
>> line, but, the 3 had networking!
>
> Runlevels in most Linux distributions:
> 1 (or single), single user level, only the console is active.
> limited startup, often without login at all
> 3 full multi-user level, with networking and all
> just without starting up the graphical subsystem/login
> 5 ?DM-based login, X11 graphics server started, further the same as 3
>
> 2 is mostly a more limited multi-user system, 4 often isn't used
> at all (but in Slackware is what 5 is in others, slackware thus
> doesn't use 5).

For everyone running a systemd boot, it will accept run level numbers
in the kernel options, but will translate them as follows ..
lrwxrwxrwx 1 root root 15 Sep 22 14:56 /lib/systemd/system/runlevel0.target -> poweroff.target
lrwxrwxrwx 1 root root 13 Sep 22 14:56 /lib/systemd/system/runlevel1.target -> rescue.target
lrwxrwxrwx 1 root root 17 Sep 22 14:56 /lib/systemd/system/runlevel2.target -> multi-user.target
lrwxrwxrwx 1 root root 17 Sep 22 14:56 /lib/systemd/system/runlevel3.target -> multi-user.target
lrwxrwxrwx 1 root root 17 Sep 22 14:56 /lib/systemd/system/runlevel4.target -> multi-user.target
lrwxrwxrwx 1 root root 16 Sep 22 14:56 /lib/systemd/system/runlevel5.target -> graphical.target
lrwxrwxrwx 1 root root 13 Sep 22 14:56 /lib/systemd/system/runlevel6.target -> reboot.target

[unruh]

run
startx 2>/tmp/X
If it does not start up, then do
alt-ctrl-bksp
and read /tmp/X for hints as to what went wrong.

[Eef Hartman]

In alt.os.linux sandy <sa...@is.invalid> wrote:

> So, at this point, I can easily boot to the command line,
> but I have absolutely no idea WHY the graphical environment
> won't come up.

Did you already into the server logfile:
/var/log/Xorg.0.log
(assuming your X-server is in the normal :0 configuration)
to see which errors (flagged with (EE), all-caps) are logged in there?

[Sandy]

Sandy (Knoppix KNode Emergency Repair) wrote:

> So, I'll try those methods, and report back,
> so others with LVM volumes don't have to start
> from scratch, like I am.

-------------------------------------------------------------------------
I booted to the Centos command line with networking by adding a "3"
to the end of the grub boot line and was able to run:
Centos# startx >& /tmp/startx.log

But, then, I needed to access that Centos log file in a graphical
user environment, by booting to Knoppix & mounting that file system.
-------------------------------------------------------------------------
Apparently, you can't just mount the root file system conventionally.
Notice that the fstab indicates sda2 is of type "LVM2_member".
-------------------------------------------------------------------------
root@Microknoppix:~# cat /etc/fstab
# DEFAULT BASE FSTAB, UNCONFIGURED
proc /proc proc noauto 0 0
sysfs /sys sysfs noauto 0 0
# Added by KNOPPIX
/dev/sr0 /media/sr0 iso9660 noauto,users,exec 0 0
# Added by KNOPPIX
/dev/sda1 /media/sda1 ext4 noauto,users,exec 0 0
# Added by KNOPPIX
/dev/sda2 /media/sda2 LVM2_member noauto,users,exec 0 0
-------------------------------------------------------------------------
Here is an example of a conventional file system mount:
-------------------------------------------------------------------------
root@Microknoppix:~# ls /mnt
root@Microknoppix:~# mkdir /mnt/test
root@Microknoppix:~# mount /dev/sda1 /mnt/test
-------------------------------------------------------------------------
Yet, for the LVM volumes, conventional methods fail:
-------------------------------------------------------------------------
root@Microknoppix:~# mount /dev/sda2 /mnt/test
=> mount: unknown filesystem type 'LVM2_member'
-------------------------------------------------------------------------
To identify your hard disk drive partitions, run fdisk:
-------------------------------------------------------------------------
root@Microknoppix:~# fdisk -l

Disk /dev/sda: 128.0 GB, 128035676160 bytes
255 heads, 63 sectors/track, 15566 cylinders, total 250069680 sectors
Units = sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disk identifier: 0x5504d700

Device Boot Start End Blocks Id System
/dev/sda1 * 2048 1026047 512000 83 Linux
/dev/sda2 1026048 250068991 124521472 8e Linux LVM
-------------------------------------------------------------------------
Run an lvm2 tools disk scan to identify the LVM physical volume:
-------------------------------------------------------------------------
root@Microknoppix:~# lvmdiskscan
/dev/ram0 [ 97.66 MiB]
/dev/ram1 [ 97.66 MiB]
/dev/sda1 [ 500.00 MiB]
/dev/ram2 [ 97.66 MiB]
/dev/sda2 [ 118.75 GiB] LVM physical volume
/dev/ram3 [ 97.66 MiB]
/dev/ram4 [ 97.66 MiB]
/dev/ram5 [ 97.66 MiB]
/dev/ram6 [ 97.66 MiB]
/dev/ram7 [ 97.66 MiB]
/dev/ram8 [ 97.66 MiB]
/dev/ram9 [ 97.66 MiB]
/dev/ram10 [ 97.66 MiB]
/dev/ram11 [ 97.66 MiB]
/dev/ram12 [ 97.66 MiB]
/dev/ram13 [ 97.66 MiB]
/dev/ram14 [ 97.66 MiB]
/dev/ram15 [ 97.66 MiB]
0 disks
17 partitions
0 LVM physical volume whole disks
1 LVM physical volume
-------------------------------------------------------------------------
Obtain the LV Name and VG Name using lvdisplay:
-------------------------------------------------------------------------
root@Microknoppix:~# lvdisplay
--- Logical volume ---
LV Path /dev/vg_burns/lv_root
LV Name lv_root
VG Name vg_burns
LV UUID Z9mslg-XoNW-VxRj-Ox0P-FeDC-WQgb-gh3aP3
LV Write Access read/write
LV Creation host, time ,
LV Status NOT available
LV Size 19.53 GiB
Current LE 5000
Segments 1
Allocation inherit
Read ahead sectors auto

--- Logical volume ---
LV Path /dev/vg_burns/lv_swap
LV Name lv_swap
VG Name vg_burns
LV UUID TVNW8l-ywHp-f3hi-JoxS-JAsH-0y2O-goucnH
LV Write Access read/write
LV Creation host, time ,
LV Status NOT available
LV Size 17.64 GiB
Current LE 4516
Segments 1
Allocation inherit
Read ahead sectors auto

--- Logical volume ---
LV Path /dev/vg_burns/lv_home
LV Name lv_home
VG Name vg_burns
LV UUID MIu3wF-RtiS-bhLY-ofcb-0rEh-8jXu-3Z0SIQ
LV Write Access read/write
LV Creation host, time ,
LV Status NOT available
LV Size 81.58 GiB
Current LE 20884
Segments 1
Allocation inherit
Read ahead sectors auto
-------------------------------------------------------------------------
Doublecheck your results with vgdisplay:
-------------------------------------------------------------------------
root@Microknoppix:~# vgdisplay
--- Volume group ---
VG Name vg_burns
System ID
Format lvm2
Metadata Areas 1
Metadata Sequence No 4
VG Access read/write
VG Status resizable
MAX LV 0
Cur LV 3
Open LV 0
Max PV 0
Cur PV 1
Act PV 1
VG Size 118.75 GiB
PE Size 4.00 MiB
Total PE 30400
Alloc PE / Size 30400 / 118.75 GiB
Free PE / Size 0 / 0
VG UUID If3sRy-kA8d-KdQo-vQQj-GTQU-pKIk-LvIHZR
-------------------------------------------------------------------------
You can't mount the file system yet with only this information:
-------------------------------------------------------------------------
root@Microknoppix:~# mkdir /mnt/root
root@Microknoppix:~# mount /dev/vg_burns/lv_root /mnt/root
=> mount: special device /dev/vg_burns/lv_root does not exist
-------------------------------------------------------------------------
You need to check the active/inactive status of the LVM file systems:
-------------------------------------------------------------------------
root@Microknoppix:~# lvscan
inactive '/dev/vg_burns/lv_root' [19.53 GiB] inherit
inactive '/dev/vg_burns/lv_swap' [17.64 GiB] inherit
inactive '/dev/vg_burns/lv_home' [81.58 GiB] inherit
-------------------------------------------------------------------------
If inactive, you need to make them active:
-------------------------------------------------------------------------
root@Microknoppix:~# modprobe dm-mod
root@Microknoppix:~# vgchange -ay
3 logical volume(s) in volume group "vg_burns" now active
-------------------------------------------------------------------------
Now an lvscan will show them to be active:
-------------------------------------------------------------------------
root@Microknoppix:~# lvscan
ACTIVE '/dev/vg_burns/lv_root' [19.53 GiB] inherit
ACTIVE '/dev/vg_burns/lv_swap' [17.64 GiB] inherit
ACTIVE '/dev/vg_burns/lv_home' [81.58 GiB] inherit
-------------------------------------------------------------------------
Now that they're active, you can mount them:
-------------------------------------------------------------------------
root@Microknoppix:~# mkdir /mnt/root
root@Microknoppix:~# mount /dev/vg_burns/lv_root /mnt/root
root@Microknoppix:~# ls /mnt/root
root@Microknoppix:~# mkdir /mnt/home
root@Microknoppix:~# mount /dev/vg_burns/lv_home /mnt/home
root@Microknoppix:~# mkdir /mnt/swap
root@Microknoppix:~# mount /dev/vg_burns/lv_swap /mnt/swap
=> /dev/mapper/vg_burns-lv_swap looks like swapspace - not mounted
=> mount: you must specify the filesystem type
-------------------------------------------------------------------------
And, now that root is mounted, I can finally find the desired text
files:
root@Microknoppix:/mnt/root/tmp# ls *txt
=> centos.txt startx1.txt startx2.txt traceroute.centos.org.txt
-------------------------------------------------------------------------
I'll append those text file separately (where they were requested).
This howto is posted so that we can all benefit from the effort.
-------------------------------------------------------------------------

[Sandy]

Eef Hartman wrote:

> Did you already into the server logfile:
> /var/log/Xorg.0.log
> (assuming your X-server is in the normal :0 configuration)
> to see which errors (flagged with (EE), all-caps) are logged in there?

I apologize it took me so long to get you this data.

My problem was that I could boot to Centos command line,
but I couldn't access any Centos files from Knoppix to
send you the results.

I had to figure out how to mount LVM file systems (yuck).

Now that I'm booted to Knoppix with the Centos LVM root partition
mounted, I can get to the Centos /mnt/root/var/log/Xorg.0.log on
Knoppix to show you using Knode.

Here are all the lines with EE in them:

$ grep EE Xorg.0.log
(WW) warning, (EE) error, (NI) not implemented, (??) unknown.
[ 11129.233] Initializing built-in extension MIT-SCREEN-SAVER
[ 11131.278] (EE) PreInit returned 8 for "HDA Intel Headphone"
[ 11131.278] (EE) config/hal: NewInputDeviceRequest failed (8)
[ 11131.298] (EE) PreInit returned 8 for "HDA Intel Dock Headphone"
[ 11131.298] (EE) config/hal: NewInputDeviceRequest failed (8)
[ 11131.468] (EE) PreInit returned 8 for "HDA NVidia HDMI/DP,pcm=3"
[ 11131.468] (EE) config/hal: NewInputDeviceRequest failed (8)
[ 11131.500] (EE) PreInit returned 8 for "HDA NVidia HDMI/DP,pcm=7"
[ 11131.500] (EE) config/hal: NewInputDeviceRequest failed (8)
[ 11131.536] (EE) PreInit returned 8 for "HDA NVidia HDMI/DP,pcm=8"
[ 11131.536] (EE) config/hal: NewInputDeviceRequest failed (8)
[ 11131.564] (EE) PreInit returned 8 for "HDA NVidia HDMI/DP,pcm=9"
[ 11131.564] (EE) config/hal: NewInputDeviceRequest failed (8)

Do you think these errors are the reason that Centos won't boot
to the graphical user environment?

[Sandy]

unruh wrote:

> run
> startx 2>/tmp/X
> If it does not start up, then do
> alt-ctrl-bksp
> and read /tmp/X for hints as to what went wrong.

Sorry it took me so long to respond.

The problem I had was that I could run the command on
the Centos command line, but, I couldn't access the
Centos /tmp while in Knoppix in order to send you the
results.

It wasn't easy, but I figured out how to mount LVM
file systems on Knoppix, so, with that, I was able
to access the Centos /tmp on Knoppix as a mounted
file system /mnt/root/tmp

Running these two commands at the init 3 for Centos
created the same log file:
# startx >& /tmp/startx.log1
# startx 2> /tmp/startx.log2

In both cases, the screen flashed the Nvidia logo
momentarily, and then flashed back to the command line.

Here's the content of the log file:
I see a FATAL error below.

---- begin starx log file ----
xauth: creating new authority file /root/.serverauth.3192


X.Org X Server 1.13.0
Release Date: 2012-09-05
X Protocol Version 11, Revision 0
Build Operating System: c6b7 2.6.32-220.el6.x86_64
Current Operating System: Linux sandy 2.6.32-358.18.1.el6.x86_64 #1 SMP Wed
Aug 28 17:19:38 UTC 2013 x86_64
Kernel command line: ro root=/dev/mapper/vg_burns-lv_root rd_NO_LUKS
LANG=en_US.UTF-8 rd_LVM_LV=vg_burns/lv_swap rd_NO_MD
rd_LVM_LV=vg_burns/lv_root SYSFONT=latarcyrheb-sun16 rhgb quiet
KEYBOARDTYPE=pc KEYTABLE=us rd_NO_DM crashkernel=130M@0M 3
Build Date: 22 February 2013 11:30:37AM
Build ID: xorg-x11-server 1.13.0-11.el6.centos
Current version of pixman: 0.26.2
Before reporting problems, check
http://wiki.centos.org/Documentation
to make sure that you have the latest version.
Markers: (--) probed, (**) from config file, (==) default setting,
(++) from command line, (!!) notice, (II) informational,

(WW) warning, (EE) error, (NI) not implemented, (??) unknown.

(==) Log file: "/var/log/Xorg.0.log", Time: Wed Oct 9 20:55:33 2013
(==) Using config file: "/etc/X11/xorg.conf"
Initializing built-in extension Generic Event Extension
Initializing built-in extension SHAPE
Initializing built-in extension MIT-SHM
Initializing built-in extension XInputExtension
Initializing built-in extension XTEST
Initializing built-in extension BIG-REQUESTS
Initializing built-in extension SYNC
Initializing built-in extension XKEYBOARD
Initializing built-in extension XC-MISC
Initializing built-in extension XINERAMA
Initializing built-in extension XFIXES
Initializing built-in extension RENDER
Initializing built-in extension RANDR
Initializing built-in extension COMPOSITE
Initializing built-in extension DAMAGE
Initializing built-in extension MIT-SCREEN-SAVER
Initializing built-in extension DOUBLE-BUFFER
Initializing built-in extension RECORD
Initializing built-in extension DPMS
Initializing built-in extension X-Resource
Initializing built-in extension XVideo
Initializing built-in extension XVideo-MotionCompensation
Initializing built-in extension SELinux
Initializing built-in extension XFree86-VidModeExtension
Initializing built-in extension XFree86-DGA
Initializing built-in extension XFree86-DRI
Initializing built-in extension DRI2
Loading extension GLX
FATAL: Error inserting nvidia (/lib/modules/2.6.32-358.18.1.el6.x86_64/weak-
updates/nvidia/nvidia.ko): No such device

Fatal server error:
no screens found
(EE)
Please consult the CentOS support
at http://wiki.centos.org/Documentation
for help.
(EE) Please also check the log file at "/var/log/Xorg.0.log" for additional
information.
(EE)
Server terminated with error (1). Closing log file.
giving up.
xinit: Connection refused (errno 111): unable to connect to X server
xinit: No such process (errno 3): Server error.

[unruh]

On 2013-10-11, Sandy <Sa...@is.invalid> wrote:
> Eef Hartman wrote:
>
>> Did you already into the server logfile:
>> /var/log/Xorg.0.log
>> (assuming your X-server is in the normal :0 configuration)
>> to see which errors (flagged with (EE), all-caps) are logged in there?
>
> I apologize it took me so long to get you this data.
>
> My problem was that I could boot to Centos command line,
> but I couldn't access any Centos files from Knoppix to
> send you the results.

USB stick? Mount the Knopix files under Centos? send it to anther
computer via internet?

>
> I had to figure out how to mount LVM file systems (yuck).
>
> Now that I'm booted to Knoppix with the Centos LVM root partition
> mounted, I can get to the Centos /mnt/root/var/log/Xorg.0.log on
> Knoppix to show you using Knode.
>
> Here are all the lines with EE in them:

>
> $ grep EE Xorg.0.log

You could just have sent the file.

> (WW) warning, (EE) error, (NI) not implemented, (??) unknown.
> [ 11129.233] Initializing built-in extension MIT-SCREEN-SAVER
> [ 11131.278] (EE) PreInit returned 8 for "HDA Intel Headphone"
> [ 11131.278] (EE) config/hal: NewInputDeviceRequest failed (8)
> [ 11131.298] (EE) PreInit returned 8 for "HDA Intel Dock Headphone"
> [ 11131.298] (EE) config/hal: NewInputDeviceRequest failed (8)
> [ 11131.468] (EE) PreInit returned 8 for "HDA NVidia HDMI/DP,pcm=3"
> [ 11131.468] (EE) config/hal: NewInputDeviceRequest failed (8)
> [ 11131.500] (EE) PreInit returned 8 for "HDA NVidia HDMI/DP,pcm=7"
> [ 11131.500] (EE) config/hal: NewInputDeviceRequest failed (8)
> [ 11131.536] (EE) PreInit returned 8 for "HDA NVidia HDMI/DP,pcm=8"
> [ 11131.536] (EE) config/hal: NewInputDeviceRequest failed (8)
> [ 11131.564] (EE) PreInit returned 8 for "HDA NVidia HDMI/DP,pcm=9"
> [ 11131.564] (EE) config/hal: NewInputDeviceRequest failed (8)
>
> Do you think these errors are the reason that Centos won't boot
> to the graphical user environment?

Looks like problems with sound.

Did you try what I suggested?
startx 2>/tmp/X
and if it fails look in /tmp/X

>
>
>

[unruh]

On 2013-10-11, Sandy <Sa...@is.invalid> wrote:

...

> Initializing built-in extension DRI2
> Loading extension GLX
> FATAL: Error inserting nvidia (/lib/modules/2.6.32-358.18.1.el6.x86_64/weak-
> updates/nvidia/nvidia.ko): No such device

Does /lib/modules/2.6.32-358.18.1.el6.x86_64/weak-updates/nvidia/nvidia.ko

exist? I do not run nvidia so have no idea what it thinks is missing.

But this certainly seems like the problem.

[Sandy]

unruh wrote:

> Does /lib/modules/2.6.32-358.18.1.el6.x86_64/
> weak-updates/nvidia/nvidia.ko exist?

Booted to Knoppix, I have to mount the Centos root partition
to see if that file exists.

bootcommand: knoppix32 xmodule=nv acpi=off

root@Microknoppix:~# modprobe dm-mod
root@Microknoppix:~# vgchange -ay

==> 3 logical volume(s) in volume group "vg_burns" now active
root@Microknoppix:~# lvscan
==> ACTIVE '/dev/vg_burns/lv_root' [19.53 GiB] inherit
==> ACTIVE '/dev/vg_burns/lv_swap' [17.64 GiB] inherit
==> ACTIVE '/dev/vg_burns/lv_home' [81.58 GiB] inherit

root@Microknoppix:~# mkdir /mnt/root
root@Microknoppix:~# mount /dev/vg_burns/lv_root /mnt/root

And, now that Centos root is mounted on Knoppix, I can look for that file:
root@Microknoppix:~# file /mnt/root/lib/modules/2.6.32-358.18.1.el6.x86_64/weak-updates/nvidia/nvidia.ko
==> /mnt/root/lib/modules/2.6.32-358.18.1.el6.x86_64/weak-updates/nvidia/nvidia.ko: broken symbolic link to
`/lib/modules/2.6.32-358.el6.x86_64/extra/nvidia/nvidia.ko'

Hmm... so the file exists; but it's a link to a file that doesn't
exist (but that link may only be broken on Knoppix becasue of the
fact I'm mounting the Centos file system).

Looking for that file, it seems to exist:
root@Microknoppix:~# updatedb

$ locate nvidia.ko
/mnt/root/lib/modules/2.6.32-279.19.1.el6.x86_64/weak-updates/nvidia/nvidia.ko
/mnt/root/lib/modules/2.6.32-358.14.1.el6.x86_64/weak-updates/nvidia/nvidia.ko
/mnt/root/lib/modules/2.6.32-358.18.1.el6.x86_64/weak-updates/nvidia/nvidia.ko
/mnt/root/lib/modules/2.6.32-358.2.1.el6.x86_64/weak-updates/nvidia/nvidia.ko
/mnt/root/lib/modules/2.6.32-358.6.2.el6.x86_64/weak-updates/nvidia/nvidia.ko
/mnt/root/lib/modules/2.6.32-358.el6.x86_64/extra/nvidia/nvidia.ko

[George Westerbrook]

Here is some more informatoin about the error ...


knoppix@Microknoppix:~/Desktop/portable/tor-browser_en-US$ script
/tmp/foo.txt
Script started on Wed 16 Oct 2013 03:55:39 AM UTC

knoppix@Microknoppix:~$ cd ~/Desktop/portable/tor-browser_en-US

knoppix@Microknoppix:~/Desktop/portable/tor-browser_en-US$ uname -m
x86_64

knoppix@Microknoppix:~/Desktop/portable/tor-browser_en-US$
./App/vidalia
-rwxrwxrwx 1 knoppix knoppix 6234920 Oct 15 16:27 ./App/vidalia

knoppix@Microknoppix:~/Desktop/portable/tor-browser_en-US$
./App/vidalia
not a dynamic executable

knoppix@Microknoppix:~/Desktop/portable/tor-browser_en-US$
./App/vidalia
./App/vidalia: ELF 64-bit LSB executable, x86-64, version 1 (SYSV),
dynamically linked (uses shared libs), for GNU/Linux 2.6.18,
BuildID[sha1]=0x98bf0995b1cabbe1f955a8064421e400906e50e5, stripped

knoppix@Microknoppix:~/Desktop/portable/tor-browser_en-US$
./App/vidalia
bash: ./App/vidalia: No such file or directory

knoppix@Microknoppix:~/Desktop/portable/tor-browser_en-US$ exit
exit

Script done on Wed 16 Oct 2013 03:56:09 AM UTC