Author Topic: 2012.2 install went fine. But  (Read 5036 times)

Offline Grandpa

  • Hero Member
  • *****
  • Posts: 810
Re: 2012.2 install went fine. But
« Reply #15 on: February 24, 2012, 11:41:18 AM »
Don't know if I should start a new thread or not.  But there is also a problem with shutting down.  The computer does not finish shutting down.  The last three lines in the verbose of shutdown are
unmounting proc file system
halting system
system halted.
It wasn't a big deal for me to manual press the on/off button.  But after searching for help.  I found that could cause trouble.  Pressing the Esc key does nothing.
Life is short, Break the rules, Forgive quickly, Kiss slowly, Love truly, Laugh uncontrollably, And never regret anything that made you smile.

Offline pags

  • Hero Member
  • *****
  • Posts: 2519
  • Keep it clean.
Re: 2012.2 install went fine. But
« Reply #16 on: February 24, 2012, 11:43:31 AM »
Don't know if I should start a new thread or not.  But there is also a problem with shutting down.  The computer does not finish shutting down.  The last three lines in the verbose of shutdown are
unmounting proc file system
halting system
system halted.
It wasn't a big deal for me to manual press the on/off button.  But after searching for help.  I found that could cause trouble.  Pressing the Esc key does nothing.

Once you see the "system halted" message, it is OK to power off the machine.  This sounds like an ACPI issue...

Offline AS

  • Hero Member
  • *****
  • Posts: 4111
  • Have a nice ... night!
Re: 2012.2 install went fine. But
« Reply #17 on: February 24, 2012, 11:58:24 AM »
Don't know if I should start a new thread or not.  But there is also a problem with shutting down.  The computer does not finish shutting down.  The last three lines in the verbose of shutdown are
unmounting proc file system
halting system
system halted.
It wasn't a big deal for me to manual press the on/off button.  But after searching for help.  I found that could cause trouble.  Pressing the Esc key does nothing.

Once you see the "system halted" message, it is OK to power off the machine.  This sounds like an ACPI issue...

+1, possibly self inflicted ...

was wondering about this line, captured from the Xorg.0.log previously posted on pastebin ...
Quote
[    27.603] Kernel command line: apm=off acpi=off mce=off barrier=off ide=nodma idewait=50 i8042.nomux psmouse.proto=bare irqpoll pci=nommconf BOOT_IMAGE=PClinuxOS_2012.2 root=UUID=9b10f7c2-e1ce-4d55-bc27-e900b6849be2 splash=verbose nokmsboot vmalloc=256M pci=nommconf acpi=on resume=UUID
[    27.603] Build Date: 22 September 2011  10:12:37PM
[    27.603] 

 ???

Offline Grandpa

  • Hero Member
  • *****
  • Posts: 810
Re: 2012.2 install went fine. But
« Reply #18 on: February 24, 2012, 02:52:28 PM »
Well maybe I didn't understand you correctly AS.  But this is what I did.  When the boot screen came up I pressed "f3", then "safeboot".  In the line that appeared I deleted "quiet" and typed in it place "splash=verbose".  After that 2012.2 would boot.  As you later suggested I edited the boot menu list the same way.  I deleted "quiet" and added "splash=verbose.  Now should I now change "acpi" to equal "off"? 
Life is short, Break the rules, Forgive quickly, Kiss slowly, Love truly, Laugh uncontrollably, And never regret anything that made you smile.

Offline Grandpa

  • Hero Member
  • *****
  • Posts: 810
Re: 2012.2 install went fine. But
« Reply #19 on: February 24, 2012, 03:10:46 PM »
On further checking that should be "safe settings" not safeboot",sorry.  But anyway "acpi" does equal "on" both in safe settings and in the "menu list" file.
Life is short, Break the rules, Forgive quickly, Kiss slowly, Love truly, Laugh uncontrollably, And never regret anything that made you smile.

Offline Grandpa

  • Hero Member
  • *****
  • Posts: 810
Re: 2012.2 install went fine. But
« Reply #20 on: February 24, 2012, 03:24:06 PM »
Also in PCC > setup boot system.  Both "enable acpi and enable local apci" are checked.
Life is short, Break the rules, Forgive quickly, Kiss slowly, Love truly, Laugh uncontrollably, And never regret anything that made you smile.

Offline AS

  • Hero Member
  • *****
  • Posts: 4111
  • Have a nice ... night!
Re: 2012.2 install went fine. But
« Reply #21 on: February 24, 2012, 06:00:16 PM »
Well maybe I didn't understand you correctly AS.  But this is what I did.  When the boot screen came up I pressed "f3", then "safeboot".  In the line that appeared I deleted "quiet" and typed in it place "splash=verbose".  After that 2012.2 would boot.  As you later suggested I edited the boot menu list the same way.  I deleted "quiet" and added "splash=verbose.  Now should I now change "acpi" to equal "off"? 


That's is, safeboot, that allow you to successfully boot: safeboot imply that most features are disabled, possibly reducing conflicts between hardware and kernel, but safeboot is an emergency/rescue choice, not a definitive setup.

As I wrote before, it was a bit strange that only changing splash=verbose and removing quiet solved your issue ...
http://www.pclinuxos.com/forum/index.php/topic,102836.msg877649.html#msg877649

The idea was about to boot "normal/default settings" with exceptions of "quiet" and "splash=verbose", kernel should however crash but you should be able to view at which point is crashing, instead of crashing in the darkness.

I understand this is going to be annoying, but really no one other than you can report about what is going on, therefore I'm asking you to repeat the trial:

at grub screen, press F3, select "default", remove "quiet", add splash=verbose, press ENTER and report back as much info as possible.

AS

Offline Grandpa

  • Hero Member
  • *****
  • Posts: 810
Re: 2012.2 install went fine. But
« Reply #22 on: February 25, 2012, 01:00:57 AM »
OK!  I did as you asked "at grub screen, press F3, select "default", remove "quiet", add splash=verbose, press ENTER and report back as much info as possible"  and I got a kernel panic. BTW quiet was not there and splash=verbose was.
Here are the last 15 lines shown as it was booting.
waiting for device sda5 to appear (timeout 1 min)
waiting for device sda6 to appear (timeout 1 min)
could not find resume device(uuid=4d65bcd3-0be1-49e9-bd5-9fb0f474a5)
could not resolve resume device(uuid=4d65bcd3-0be1-49e9-bd59fb0f47a5)
creating boot device
mounting root filesystem
mount: could not finf file system '/dev/root'
kernel panic - not syncing: attempted to kill init !
pid:, comm: init not tainted 2.6.38.8-pclos3.bfs #1
call trace:
[<c0439408>] ? panic+0x66/0161
[<c0140f3e>] ? do_exit+0x74e/0x750
[<c01416e>] ? do_group_exit+0x33e/0xa0
[<c0141e8>] ? sys_exitgroup+0x18/0x20
[<043c9b8>] ? syscall_call+0x7/0xb
Hope I do not have to many typos.

To be sure you understand in order to boot I press f3, select safe settings.  Safe settings has been edited by removing "quiet" and adding "splash=verbose".

 
« Last Edit: February 25, 2012, 01:13:20 AM by Grandpa »
Life is short, Break the rules, Forgive quickly, Kiss slowly, Love truly, Laugh uncontrollably, And never regret anything that made you smile.

Offline Grandpa

  • Hero Member
  • *****
  • Posts: 810
Re: 2012.2 install went fine. But
« Reply #23 on: February 25, 2012, 01:09:10 AM »
Here is my menu.lst
file:///boot/grub/menu.lsttimeout 10
color black/cyan yellow/cyan
gfxmenu (hd0,4)/boot/gfxmenu
default 0

title PClinuxOS 2012.2
kernel (hd0,4)/boot/vmlinuz BOOT_IMAGE=PClinuxOS_2012.2 root=UUID=9b10f7c2-e1ce-4d55-bc27-e900b6849be2 splash=verbose nokmsboot vmalloc=256M pci=nommconf acpi=on resume=UUID=4d65bcd3-0be1-49e9-b9d5-9fb09f4749a5 vga=788
initrd (hd0,4)/boot/initrd.img

title linux-nonfb
kernel (hd0,4)/boot/vmlinuz BOOT_IMAGE=linux-nonfb root=UUID=9b10f7c2-e1ce-4d55-bc27-e900b6849be2 quiet nokmsboot vmalloc=256M pci=nommconf acpi=on resume=UUID=4d65bcd3-0be1-49e9-b9d5-9fb09f4749a5
initrd (hd0,4)/boot/initrd.img

title failsafe
kernel (hd0,4)/boot/vmlinuz BOOT_IMAGE=failsafe root=UUID=9b10f7c2-e1ce-4d55-bc27-e900b6849be2 quiet nokmsboot failsafe vmalloc=256M pci=nommconf acpi=on
initrd (hd0,4)/boot/initrd.img

title windows
root (hd0,0)
makeactive
chainloader +1

title memtest-4.20
kernel (hd0,4)/boot/memtest-4.20 BOOT_IMAGE=memtest-4.20
Life is short, Break the rules, Forgive quickly, Kiss slowly, Love truly, Laugh uncontrollably, And never regret anything that made you smile.

Online pinoc

  • Global Moderator
  • Hero Member
  • *****
  • Posts: 2848
    • other projects...
Re: 2012.2 install went fine. But
« Reply #24 on: February 25, 2012, 03:51:43 AM »
Hi Grandpa,

your menu.lst looks a bit strange to me, can you change the beginning of it to look like this:

timeout 10
color black/cyan yellow/cyan
gfxmenu (hd0,4)/boot/gfxmenu
default 0

title linux
kernel (hd0,4)/boot/vmlinuz BOOT_IMAGE=linux root=UUID=9b10f7c2-e1ce-4d55-bc27-e900b6849be2 quiet vmalloc=256M acpi=on resume=UUID=4d65bcd3-0be1-49e9-b9d5-9fb09f4749a5 splash=verbose vga=788
initrd (hd0,4)/boot/initrd.img


and then keep your remaining entries:
title PClinuxOS 2012.2
kernel (hd0,4)/boot/vmlinuz BOOT_IMAGE=PClinuxOS_2012.2 root=UUID=9b10f7c2-e1ce-4d55-bc27-e900b6849be2 splash=verbose nokmsboot vmalloc=256M pci=nommconf acpi=on resume=UUID=4d65bcd3-0be1-49e9-b9d5-9fb09f4749a5 vga=788
initrd (hd0,4)/boot/initrd.img
....


then save the file and reboot, choosing the first entry in the boot-menu, should be pre-selected, and see what happens. If it doesn't work you can still choose one from your previous boot entries.
good luck,
-p.

edit: please note that each boot entry in /boot/grub/menu.lst has 3 lines, starting with
title
kernel
initrd

 
I have no idea how in your original menu.lst you got  BOOT_IMAGE=PClinuxOS_2012.2 that can not work, did you edit this like that?
« Last Edit: February 25, 2012, 04:23:57 AM by pinoc »

Offline Old-Polack

  • Administrator
  • Super Villain
  • *****
  • Posts: 11591
  • ----IOFLU----
Re: 2012.2 install went fine. But
« Reply #25 on: February 25, 2012, 06:59:38 AM »

I have no idea how in your original menu.lst you got  BOOT_IMAGE=PClinuxOS_2012.2 that can not work, did you edit this like that?

The initial installation process from the liveCD does that. The BOOT_IMAGE=<whatever the title is> that one chooses when editing the grub installation entries, before they are ever written to the installation's /boot/grub/menu.lst. Not only do they work fine as they are shown, removing them entirely has no effect on the actual boot process.

Example from this installation on my machine:

title Test64-sdc5
kernel (hd2,4)/boot/vmlinuz BOOT_IMAGE=Test64-sdc5 root=LABEL=test64 nokmsboot acpi=on resume=LABEL=swap2000 splash=verbose vga=791
initrd (hd2,4)/boot/initrd.img

title Test64-sdc5-nonfb
kernel (hd2,4)/boot/vmlinuz BOOT_IMAGE=Test64-sdc5-nonfb root=LABEL=test64 nokmsboot acpi=on resume=LABEL=swap2000 splash=verbose
initrd (hd2,4)/boot/initrd.img


This is consistent with every PCLinuxOS installation I currently have, and all that I can remember from the past. Here's one from a 2008 MiniMe installation.

title 750_MiniMe
kernel (hd1,7)/boot/vmlinuz BOOT_IMAGE=750_MiniMe root=LABEL=750mm acpi=on resume=LABEL=swap750 splash=verbose vga=791
initrd (hd1,7)/boot/initrd.img


It still boots right up, and runs fine, as it always has.
« Last Edit: February 25, 2012, 07:22:13 AM by Old-Polack »
Old-Polack

Of what use be there for joy, if not for the sharing thereof?



Lest we forget...

Offline AS

  • Hero Member
  • *****
  • Posts: 4111
  • Have a nice ... night!
Re: 2012.2 install went fine. But
« Reply #26 on: February 25, 2012, 07:27:59 AM »
OK!  I did as you asked "at grub screen, press F3, select "default", remove "quiet", add splash=verbose, press ENTER and report back as much info as possible"  and I got a kernel panic. BTW quiet was not there and splash=verbose was.
Here are the last 15 lines shown as it was booting.
waiting for device sda5 to appear (timeout 1 min)
waiting for device sda6 to appear (timeout 1 min)
could not find resume device(uuid=4d65bcd3-0be1-49e9-bd5-9fb0f474a5)
could not resolve resume device(uuid=4d65bcd3-0be1-49e9-bd59fb0f47a5)

creating boot device
mounting root filesystem
mount: could not finf file system '/dev/root'
kernel panic - not syncing: attempted to kill init !
pid:, comm: init not tainted 2.6.38.8-pclos3.bfs #1
call trace:
[<c0439408>] ? panic+0x66/0161
[<c0140f3e>] ? do_exit+0x74e/0x750
[<c01416e>] ? do_group_exit+0x33e/0xa0
[<c0141e8>] ? sys_exitgroup+0x18/0x20
[<043c9b8>] ? syscall_call+0x7/0xb
Hope I do not have to many typos.

To be sure you understand in order to boot I press f3, select safe settings.  Safe settings has been edited by removing "quiet" and adding "splash=verbose".

about the errors, marked in red:
- inability to find the resume device, which is the swap partition - this is not a fatal error.
- inability to mount the root partition - this is a fatal error - causing kernel panic.

Your system does boot when using safe settings...

Here is my menu.lst
file:///boot/grub/menu.lst
timeout 10
color black/cyan yellow/cyan
gfxmenu (hd0,4)/boot/gfxmenu
default 0

title PClinuxOS 2012.2
kernel (hd0,4)/boot/vmlinuz BOOT_IMAGE=PClinuxOS_2012.2 root=UUID=9b10f7c2-e1ce-4d55-bc27-e900b6849be2 splash=verbose nokmsboot vmalloc=256M pci=nommconf acpi=on resume=UUID=4d65bcd3-0be1-49e9-b9d5-9fb09f4749a5 vga=788
initrd (hd0,4)/boot/initrd.img

title linux-nonfb
kernel (hd0,4)/boot/vmlinuz BOOT_IMAGE=linux-nonfb root=UUID=9b10f7c2-e1ce-4d55-bc27-e900b6849be2 quiet nokmsboot vmalloc=256M pci=nommconf acpi=on resume=UUID=4d65bcd3-0be1-49e9-b9d5-9fb09f4749a5
initrd (hd0,4)/boot/initrd.img

title failsafe
kernel (hd0,4)/boot/vmlinuz BOOT_IMAGE=failsafe root=UUID=9b10f7c2-e1ce-4d55-bc27-e900b6849be2 quiet nokmsboot failsafe vmalloc=256M pci=nommconf acpi=on
initrd (hd0,4)/boot/initrd.img

title windows
root (hd0,0)
makeactive
chainloader +1

title memtest-4.20
kernel (hd0,4)/boot/memtest-4.20 BOOT_IMAGE=memtest-4.20

I have never seen the option pci=nommconf in standard PCLOS menu.lst entries ... in fact this is sometimes used as a workaround for buggy BIOS ...

Is there any specific reason for that entry in your menu.lst ?

Can you provide further info about your hardware ?  Please post (on pastebin.com) the content of /var/log/dmesg.

AS

Online pinoc

  • Global Moderator
  • Hero Member
  • *****
  • Posts: 2848
    • other projects...
Re: 2012.2 install went fine. But
« Reply #27 on: February 25, 2012, 07:36:30 AM »

I have no idea how in your original menu.lst you got  BOOT_IMAGE=PClinuxOS_2012.2 that can not work, did you edit this like that?

The initial installation process from the liveCD does that. The BOOT_IMAGE=<whatever the title is> that one chooses when editing the grub installation entries, before they are ever written to the installation's /boot/grub/menu.lst. Not only do they work fine as they are shown, removing them entirely has no effect on the actual boot process.

Example from this installation on my machine:

title Test64-sdc5
kernel (hd2,4)/boot/vmlinuz BOOT_IMAGE=Test64-sdc5 root=LABEL=test64 nokmsboot acpi=on resume=LABEL=swap2000 splash=verbose vga=791
initrd (hd2,4)/boot/initrd.img

title Test64-sdc5-nonfb
kernel (hd2,4)/boot/vmlinuz BOOT_IMAGE=Test64-sdc5-nonfb root=LABEL=test64 nokmsboot acpi=on resume=LABEL=swap2000 splash=verbose
initrd (hd2,4)/boot/initrd.img


This is consistent with every PCLinuxOS installation I currently have, and all that I can remember from the past. Here's one from a 2008 MiniMe installation.

title 750_MiniMe
kernel (hd1,7)/boot/vmlinuz BOOT_IMAGE=750_MiniMe root=LABEL=750mm acpi=on resume=LABEL=swap750 splash=verbose vga=791
initrd (hd1,7)/boot/initrd.img


It still boots right up, and runs fine, as it always has.


with all respect, I disagree  ;D
Just installed 2012.02 and my boot entry is as I outlined it before. The fact that Grandpa has 3 things I have never seen in there: BOOT_IMAGE=PClinuxOS_2012.2, pci=nommconf, and nokmsboot  makes me think he edited menu/lst himself. Another indication for this assumption is the fact that BOOT_IMAGE=PClinuxOS_2012.2 only appears once and is not present for the entry linux-nonfb in his original menu.lst. Let's see what he has to say about that ...  ;)
-p.

Offline Old-Polack

  • Administrator
  • Super Villain
  • *****
  • Posts: 11591
  • ----IOFLU----
Re: 2012.2 install went fine. But
« Reply #28 on: February 25, 2012, 08:41:48 AM »

I have no idea how in your original menu.lst you got  BOOT_IMAGE=PClinuxOS_2012.2 that can not work, did you edit this like that?

The initial installation process from the liveCD does that. The BOOT_IMAGE=<whatever the title is> that one chooses when editing the grub installation entries, before they are ever written to the installation's /boot/grub/menu.lst. Not only do they work fine as they are shown, removing them entirely has no effect on the actual boot process.

Example from this installation on my machine:

title Test64-sdc5
kernel (hd2,4)/boot/vmlinuz BOOT_IMAGE=Test64-sdc5 root=LABEL=test64 nokmsboot acpi=on resume=LABEL=swap2000 splash=verbose vga=791
initrd (hd2,4)/boot/initrd.img

title Test64-sdc5-nonfb
kernel (hd2,4)/boot/vmlinuz BOOT_IMAGE=Test64-sdc5-nonfb root=LABEL=test64 nokmsboot acpi=on resume=LABEL=swap2000 splash=verbose
initrd (hd2,4)/boot/initrd.img


This is consistent with every PCLinuxOS installation I currently have, and all that I can remember from the past. Here's one from a 2008 MiniMe installation.

title 750_MiniMe
kernel (hd1,7)/boot/vmlinuz BOOT_IMAGE=750_MiniMe root=LABEL=750mm acpi=on resume=LABEL=swap750 splash=verbose vga=791
initrd (hd1,7)/boot/initrd.img


It still boots right up, and runs fine, as it always has.


with all respect, I disagree  ;D
Just installed 2012.02 and my boot entry is as I outlined it before. The fact that Grandpa has 3 things I have never seen in there: BOOT_IMAGE=PClinuxOS_2012.2, pci=nommconf, and nokmsboot  makes me think he edited menu/lst himself. Another indication for this assumption is the fact that BOOT_IMAGE=PClinuxOS_2012.2 only appears once and is not present for the entry linux-nonfb in his original menu.lst. Let's see what he has to say about that ...  ;)
-p.

Also with all due respect, you can disagree until the cows come home, but it won't change the fact that what I said above is true. ;D ;D ;D

Each entry that will appear on the boot menu is editable during the installation process. Grandpa edited the first to get a title that would differentiate it from any other installation, rather than leave the default linux title. I do the same for every installation. I also edit the second nonfb title, replacing the default linux with <my title>-nonfb, for consistency with the first stanza, but it seems that Grandpa did not. As these items are purely optional, that's his choice.

The BOOT_IMAGE= entry for that stanza will then be the <title of that stanza>-nonfb If unedited, it will be the default linux-nonfb.

Repeating, this all takes place during the initial installation process, grub install sequence, before grub and its menu.lst stanza entries are written to the hard drive. I also edit out all the entries for all found "other OS" because they are almost always misnamed, unneeded, and produce unnecessary clutter. The UUID of the resume= also gets deleted and replaced with LABEL=swap<whatever> at this time, with all my installations.

After first boot, I directly edit my /boot/grub/nenu.lst to remove the UUID from the root= entry of each stanza and replace it with the proper LABEL=<whatever> for that partition. I also remove the quiet entry from the boot stanzas and add a splash=verbose entry. That, and possibly the default vga=788 being changed to vga=791, is the only editing done directly into the file at this time. All other edits have already been done during the installation.
Old-Polack

Of what use be there for joy, if not for the sharing thereof?



Lest we forget...

Offline Grandpa

  • Hero Member
  • *****
  • Posts: 810
Re: 2012.2 install went fine. But
« Reply #29 on: February 25, 2012, 09:01:15 AM »
Hi everyone, thanks for your replies.  Yes I did edit my menu list as I stated before.  The first time was during the install.  You can "modify" the title.  I changed it from "linux" to "PClinuxOS 2012.2".  That is all I changed.  Old-Polack you are right.  In fact I may have gotten the idea from you.
 Later AS said  "Anyway, yes, you can apply the changes permanently by editing the file /boot/grub/menu.lst, there you will find the boot stanza with the same option you edited while pressing F3. You need to be root to edit that file. Also, use a text editor i.e. kwrite, not a word processor."  Again all I did was remove "quiet" and add "splash=verbose".
Now I had nothing to do with "pci=nommconf".  I did not add it, or edit it.  The install put it there.
My hardware is just a stock Gateway DX4720-03.  It has "Nvidia GeForce 7100 onboard video.  Intel Pentium E5200 Dual-Core processor and 4 gib ram.  I am dual booting with Win 7 updated from Vista.
AS I will post my /var/log/dmesg. on pastebin.com.  But first I need some coffee.
 
Life is short, Break the rules, Forgive quickly, Kiss slowly, Love truly, Laugh uncontrollably, And never regret anything that made you smile.