The Linux Community Forum

Support => Ubuntu => Topic started by: Degsy on October 08, 2014, 11:50:25 am

Title: Problem with 14.04 (Solved)
Post by: Degsy on October 08, 2014, 11:50:25 am
Hi Guys,
I have a desktop(self build) that was originally running 12.04 LTS, I have installed peppermint 5 to run alongside this with out any problems. I decided to upgrade from 12.04 to 14.04, the upgrade seemed to go alright except that now the computer "locks up" on booting to Ubuntu 14.04.
On switch on I am offered the choices for Ubuntu or Peppermint 5, if I choose Peppermint the computer boots up and I have no problem.
If I choose Ubuntu, then the computer boots up as normal, goes to the password entry screen, as normal, I enter password and then the boot up fails, I have had a blank type screen with Ubuntu 14.04 LTS in the bottom left corner but nothing else and no mouse or keyboard. If I press the reset button the computer reboots, offers me the options again, choose Ubuntu and got to the password screen, this time loaded the desktop but with the following message in the top left corner:
System program problem detected
Do you want to report the problem now?
Cancel        Report Problem

No mouse or keyboard operating.
Any help would be appreciated.
Please note I have tried loading Ubuntu 14.04 from a CD and get the same problem, though the disk is fine as I have loaded 14.04 onto a Laptop from the same disk.


Help.


Degsy
Title: Re: Problem with 14.04
Post by: chemicalfan on October 08, 2014, 12:47:30 pm
When you get to the password screen, can you drop to a terminal with Ctrl-Alt-F1?

If you can, try to login to the terminal with your username and password, then run:
Code: [Select]
sudo apt-get update && sudo apt-get dist-upgrade && sudo reboot
This will fully update your system, then reboot it. Try to load Ubuntu again and post results back here (including if you got any errors in the terminal)
Title: Re: Problem with 14.04
Post by: Degsy on October 08, 2014, 01:25:17 pm
Ok, thanks  Chemicalfan, did as you suggested, did not see any errors reported in Terminal but on reboot still same, no mouse or keyboard activity with error message as before in top left of screen, then screen went black.. Reset and rebooted to Peppermint 5, no probs still with that.
Any other suggestions please.
Ps learned something anyway as wasn't aware could get to a Terminal like that, so thanks too for that info.


Degsy
Title: Re: Problem with 14.04
Post by: chemicalfan on October 08, 2014, 01:42:53 pm
Ok, we need to go back into the terminal, and after logging in, note down the result of:
Code: [Select]
cat /var/log/Xorg.0.log|grep "EE"

Also, from Peppermint, can you post up the output of:
Code: [Select]
sudo lsblk
Slightly nervous of how this dual boot has been set up
Title: Re: Problem with 14.04
Post by: Degsy on October 08, 2014, 02:01:17 pm
How do I get the symbol between log and grep to display, please?


Degsy
Title: Re: Problem with 14.04
Post by: Degsy on October 08, 2014, 02:11:20 pm
Ok found that, will report back shortly.


Degsy
Title: Re: Problem with 14.04
Post by: Degsy on October 08, 2014, 02:21:42 pm
Ok here is the output, first from Peppermint:

NAME   MAJ:MIN RM   SIZE RO TYPE MOUNTPOINT
sda      8:0    0 149.1G  0 disk
├─sda1   8:1    0  94.8G  0 part
├─sda2   8:2    0     1K  0 part
├─sda5   8:5    0   1.8G  0 part [SWAP]
└─sda6   8:6    0  52.5G  0 part /
sr0     11:0    1  1024M  0 rom 
 
now for the other one;
cat  /var/log/Xorg.0.log|grep "EE"
(ww) warning, (EE) error, (NI) not implemented,  (??) unknown
[  23.569] Initializing built-in extension MIT-SCREEN-SAVER
[  23.848] (EE) Failed to load module "nvidia" (module does not exist, 0)
[  23.880] (EE) Failed to load module "nvidia" (module does not exist, 0)


Hope this means something.

Thanks again for your help,


Degsy
Title: Re: Problem with 14.04
Post by: chemicalfan on October 08, 2014, 02:56:01 pm
Ugh, so it looks like Peppermint & Ubuntu are sharing a partition, unless I'm mistaken?

The second output was from Ubuntu, right?
Title: Re: Problem with 14.04
Post by: Degsy on October 08, 2014, 04:25:33 pm
Hi, yes the second output was from Ubuntu.
The desktop originally ran only 12.04 LTS, then I installed Peppermint 5, I used a Cd that I had prepared for the installation and chose (from memory) install alongside Ubuntu. The two (12.04 and Peppermint) ran happily alongside each other with no problem until the update to 14.04.
I am offered other options from the boot up screen, including Advanced options for Ubuntu if that is any help.


Cheers,
Degsy
Title: Re: Problem with 14.04
Post by: chemicalfan on October 08, 2014, 04:40:56 pm
It's possible there's a conflict somewhere between the two, so I'd like to make sure of the situation.

From Peppermint (for ease), please can you post up the output from:
Code: [Select]
sudo fdisk -l
Title: Re: Problem with 14.04
Post by: Degsy on October 08, 2014, 04:45:33 pm
Hi, here is the output from Peppermint
derek@derek-System-Product-Name ~ $ sudo fdisk -l
[sudo] password for derek:

Disk /dev/sda: 160.0 GB, 160041885696 bytes
255 heads, 63 sectors/track, 19457 cylinders, total 312581808 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: 0x0002e2d3

   Device Boot      Start         End      Blocks   Id  System
/dev/sda1   *        2048   198829040    99413496+  83  Linux
/dev/sda2       198830078   312580095    56875009    5  Extended
/dev/sda5       308914176   312580095     1832960   82  Linux swap / Solaris
/dev/sda6       198830080   308914175    55042048   83  Linux

Partition table entries are not in disk order

Degsy
Title: Re: Problem with 14.04
Post by: Mark Greaves (PCNetSpec) on October 08, 2014, 07:16:46 pm
Was this output from the Ubuntu command line ?
Quote
cat  /var/log/Xorg.0.log|grep "EE"
(ww) warning, (EE) error, (NI) not implemented,  (??) unknown
[  23.569] Initializing built-in extension MIT-SCREEN-SAVER
[  23.848] (EE) Failed to load module "nvidia" (module does not exist, 0)
[  23.880] (EE) Failed to load module "nvidia" (module does not exist, 0)
Title: Re: Problem with 14.04
Post by: Degsy on October 08, 2014, 07:21:17 pm
Hi Mark,
Yes that was taken from the Terminal in Ubuntu.
Obviously it means nothing to me.


Cheers,
Degsy

could I hazard a guess and say a graphic driver problem?
Title: Re: Problem with 14.04
Post by: chemicalfan on October 09, 2014, 08:35:50 am
It's possible...you could try removing the nvidia driver from Ubuntu from the terminal.

Code: [Select]
dpkg -l '*nvidia*'
Will give you the package names (depends on which version of the nvidia driver you have)

Post up that result, then I'll post back the removal syntax  :)

Edit: Scrub this, follow Mark below...
 ;)
Title: Re: Problem with 14.04
Post by: Mark Greaves (PCNetSpec) on October 09, 2014, 10:25:43 am
From the Ubuntu console, try running:
Code: [Select]
sudo apt-get remove --purge nvidia*
then (if exists) rename xorg.conf
Code: [Select]
sudo mv -v /etc/X11/xorg.conf /etc/X11/xorg.conf.old
then reboot
Code: [Select]
sudo shutdown -r now
Title: Re: Problem with 14.04
Post by: Degsy on October 09, 2014, 11:30:21 am
Hi Guys,
Followed Mark's instructions, after the second command the reply was " no such file or directory"
After the last command the system rebooted to a screen with just Ubuntu 14.04 LTS in the bottom left corner, the mouse cursor was present. After a couple of minutes the screen went black and the mouse cursor has frozen.

What next?

Degsy
Title: Re: Problem with 14.04
Post by: chemicalfan on October 09, 2014, 11:39:24 am
Hmm, what's the output from:
Code: [Select]
locate xorg.conf
Title: Re: Problem with 14.04
Post by: Degsy on October 09, 2014, 12:04:45 pm
Hi here is the output:
/etc/X11/xorg.conf.failsafe
/user/share/X11/xorg.conf.d
/use/share/X11/xxorg.conf.d/10-evdev.conf
/user/share/X11/xorg.conf.d/11-evaded-quirks.conf
/use/share/X11/xorg.conf.d/11-em dev-track point.conf
/user/share/X11/xorg.conf.d/50-Synoptics.conf
/user/share/X11/xorg.conf.d/50-mouse.conf
/usr/share/X11/xorg.conf.d/50-Wacom.conf
/user/share/X11/xorg.conf.d/51-Synoptics-quirks.conf
/user/share/man/man5/xorg.conf.5.gz
/user/share/man/man5/xorg.conf.d.5.gz
Hope this is helpful

Degsy
Title: Re: Problem with 14.04
Post by: Degsy on October 09, 2014, 12:12:18 pm
Don't know if this is of any relevance but if I go to Ubuntu advanced options select that then the recovery mode option, after a lot of writing on the screen it says resume normal boot, click this and the system does boot though it still shows the error in the top left that I mentioned in an earlier post.


Degsy
Title: Re: Problem with 14.04
Post by: chemicalfan on October 09, 2014, 12:51:16 pm
Do you mean the system is fully functional, or does it still black screen & lock up?
Title: Re: Problem with 14.04
Post by: Degsy on October 09, 2014, 12:53:29 pm
No it did not lock up or black screen, was able to connect to Internet, Firefox on it.

Degsy
Title: Re: Problem with 14.04
Post by: chemicalfan on October 09, 2014, 03:34:33 pm
Hmm, so it'll load fine in recovery mode, but not on a regular boot....weird.

There's a few posts on askubuntu about 12.04 exhibiting this kind of behaviour (e.g. http://askubuntu.com/questions/231324/can-only-boot-into-recovery-mode-on-asus-eee-pc-1005pe (http://askubuntu.com/questions/231324/can-only-boot-into-recovery-mode-on-asus-eee-pc-1005pe)), and the only suggestions are a bug in grub (unlikely, as Peppermint would probably also suffer, plus it would have been patched by now), or a BIOS update is required. This might be worth a try, unless Mark or someone else has other suggestions?
Title: Re: Problem with 14.04
Post by: Degsy on October 09, 2014, 04:13:09 pm
OK here is some more info, not sure if this is helpful but I have been "playing around" and this is what happens:
If , when presented with the boot screen, I select "Advanced Options" I am presented with the following:
Ubuntu, with Linux 3.13.0-36-generic  if I try this it will boot but freezes at the desktop, no cursor movement.
as above but (recovery mode), this seems to boot OK, no freezing.
Ubuntu, with Linux 3.2.0-64-generic, if I use this it boots and appears OK, however I do get a box containing the following message in the top left corner of the screen:  System program problem detected
              Do you want to report the problem now?
              Cancel             Report Problem
if I cancel, the box re=appears in the centre of the screen, cancel again and it disappears.
Next option,
Ubuntu, with Linux 3.0.0-24-generic, if I use this this also boots exactly as the previous one.
Last option,
Ubuntu, with Linux 2.6.38-8-generic, booting with this boots but there is a problem as the screen appears to be in a mirror state, ie the writing is backwards, as though viewed through a mirror..
Each of the above options are also offered witha recovery mode, except for the first one haven't tried using the recovery mode.

Does this info give you guys any further clues?


Many thanks for your time,

Degsy
Title: Re: Problem with 14.04
Post by: chemicalfan on October 09, 2014, 04:25:30 pm
What happens if you hit "Report Problem"? If it generates a report file, can you post it here?

Also, what is the result of:
Code: [Select]
sudo lshw -C display
Title: Re: Problem with 14.04
Post by: Degsy on October 09, 2014, 04:31:55 pm
Here is the output:

derek@derek-System-Product-Name:~$ sudo lshw -C display
[sudo] password for derek:
  *-display               
       description: VGA compatible controller
       product: C61 [GeForce 7025 / nForce 630a]
       vendor: NVIDIA Corporation
       physical id: d
       bus info: pci@0000:00:0d.0
       version: a2
       width: 64 bits
       clock: 66MHz
       capabilities: pm msi vga_controller bus_master cap_list rom
       configuration: driver=nouveau latency=0
       resources: irq:22 memory:de000000-deffffff memory:c0000000-cfffffff memory:dd000000-ddffffff memory:dffc0000-dffdffff
derek@derek-System-Product-Name:~$
Will check if anything happens if I hit the Report Problem key.

Degsy
Title: Re: Problem with 14.04
Post by: Degsy on October 09, 2014, 04:33:03 pm
If I hit the Report Problem button the sign disappears, nothing is generated.

Degsy
Title: Re: Problem with 14.04
Post by: chemicalfan on October 09, 2014, 04:51:55 pm
So if you boot Linux 3.2.0-64-generic in normal mode, it will function correctly apart from the warning message?

That is a really old kernel, we can probably do better than that but it's a bit fiddly for this time of the day lol
Title: Re: Problem with 14.04
Post by: Degsy on October 09, 2014, 04:57:23 pm
So is this going to be a Kernel problem then? No problems about the time of day, I appreciate your efforts, just get back to me whenever you can with your suggestions for a more recent kernel.
Just as an aside the last 2 replies were both done from the desktop running Ubuntu through that old Kernel.

Once again many thanks for your kind help, look forward to your further suggestions.

Cheers,
Degsy
Title: Re: Problem with 14.04
Post by: SeZo on October 09, 2014, 07:50:02 pm
Have you tried the suggestions in this thread?
http://linuxforums.org.uk/index.php?topic=11915.msg95636#msg95636 (http://linuxforums.org.uk/index.php?topic=11915.msg95636#msg95636)
Title: Re: Problem with 14.04
Post by: chemicalfan on October 10, 2014, 08:41:47 am
As Sezo says, might be worth following the steps in the linked thread to cover all bases.

There is a revised version of the proper 14.04 kernel out (linux-image-3.13.0-37-generic), might be worth trying. Just run this in a terminal:
Code: [Select]
sudo apt-get update && sudo apt-get dist-upgrade
.

I doubt this will work though, so I'll keep looking at how to easily install an older kernel (but newer than 3.2!)
Title: Re: Problem with 14.04
Post by: Degsy on October 10, 2014, 09:01:54 am
Thanks, will let you know how any of this progresses.

Degsy
Title: Re: Problem with 14.04
Post by: Mark Greaves (PCNetSpec) on October 10, 2014, 11:43:55 am
Yeah, try booting with the xforcevesa boot parameter .. then installing the nvidia drivers again.
Title: Re: Problem with 14.04
Post by: chemicalfan on October 10, 2014, 12:17:52 pm
The latest nvidia drivers I can get on Mint 17 (same base as Ubuntu 14.04) is the package called nvidia-331, so to install:
Code: [Select]
sudo apt-get install nvidia-331

This might land you in the same boat as your started in (needed to crash into a terminal with Ctrl-Alt-F1), but you can follow the process detailed earlier in this thread to recover.

Let us know if this still leaves you with problems, as I've found a way to install a couple of newer kernels that might be worth a stab (Mark - using debs from the mainline that are "longterm" according to kernel.org; it's ok not to use synaptic/apt, right?)
Title: Re: Problem with 14.04
Post by: Mark Greaves (PCNetSpec) on October 10, 2014, 02:43:18 pm
Quote
(Mark - using debs from the mainline that are "longterm" according to kernel.org; it's ok not to use synaptic/apt, right?)

Not sure what you're asking here .. do you mean is it OK to install the vanilla kernel in .deb format with dpkg ?

I doubt if this is a kernel issue .. Peppermint 5 will be using the same kernel as 14.04 and that's working fine .. I think this is either
a) a graphics driver issue
b) an xorg issue (possibly still using the 12.04 xorg version, with the new kernel)
c) just sommat in the users home folder

I think the way forward is to
i) see if it boots with the xforcevesa kernel boot parameter
ii) if it does .. re-install the nvidia drivers through "Additional Drivers"
iii) if it still won't boot .. create a new user (and home folder) from the commandline, adding it to the correct groups .. with sommat like:
Code: [Select]
sudo useradd -m testuser -G adm,tty,disk,lp,dialout,fax,cdrom,floppy,tape,sudo,audio,dip,backup,video,plugdev,syslog,fuse,lpadmin,nopasswdlogin,netdev,ssh,sambashare
then set the password for the new "testuser" account with:
Code: [Select]
sudo passwd testuser
Then logging into the new "testuser" account at the login screen



You can get a list of the current groups with:
Code: [Select]
groups
and adjust the "useradd" command accordingly
Title: Re: Problem with 14.04
Post by: chemicalfan on October 10, 2014, 03:15:28 pm
Quote
(Mark - using debs from the mainline that are "longterm" according to kernel.org; it's ok not to use synaptic/apt, right?)

Not sure what you're asking here .. do you mean is it OK to install the vanilla kernel in .deb format with dpkg ?

Not vanilla as such, I meant the Ubuntu mainline, but yes - installing the deb files using dpkg. I wasn't sure how you get on with updates (whether Update Manager would automagically apply new versions of the 3.10 or 3.12 or whatever kernel)
Title: Re: Problem with 14.04
Post by: Mark Greaves (PCNetSpec) on October 10, 2014, 04:17:47 pm
yeah it (dpkg -i blah blah) will install them and make them available at the GRUB boot menu, but it won't set an earlier kernel as the default to boot into .. you'd have to select it at GRUB, them manually set it as the default in grub.cfg .. once set as the default it will remain as default even across updates.
(ie. you'll still be getting the kernel updates, but GRUB will always boot the one you selected as the default .. if no default is set, GRUB always boots the most recent)

Make sense ?
Title: Re: Problem with 14.04
Post by: Degsy on October 10, 2014, 04:47:29 pm
Hi Guys,
Having problems getting to the options to try the xforcevesa thing, tried left shift and F6 but I just end up back in the Grub screen, any suggestions?

Degsy
Title: Re: Problem with 14.04
Post by: Mark Greaves (PCNetSpec) on October 10, 2014, 08:12:00 pm
Whilst at the GRUB menu

(http://linuxforums.org.uk/MGalleryItem.php?id=1361)

Select the 'default' Ubuntu kernel  and rather than pressing enter, press E to edit.

You will be presented with a screen SIMILAR to this:

(http://linuxforums.org.uk/MGalleryItem.php?id=1152)

Press DOWN ARROW until you get to the line that starts with:

Quote
linux /boot


and press the END key to position the cursor at the end of the that line... it *usually* ends with “quiet splash”.

Now you can enter additional kernel boot options... so add xforcevesa .. so it now reads:

Quote
quiet splash xforcevesa

(doesn't matter if it moves down a line, as long as there is a space between splash and xforcevesa)

Now hit Ctrl+X to boot.
Title: Re: Problem with 14.04
Post by: Degsy on October 11, 2014, 10:44:29 am
Hi Guys,
OK tried your last suggestion Mark, the line didn't end with quiet splash, it actually ended with this "$vt-handoff"  I tried adding the xforcevesa after this, then deleting this and adding after the quiet splash, then finally after quiet splash and before the $vt=handoff.
The outcome was "best with this last attempt, it booted to the desktop, I thought it had worked, there was even a mouse cursor! The mouse moved and allowed me to click on Firefox, the circle went round a couple of times then stopped, froze up, no mouse movement, no keyboard, then the screen went black.
No idea if this tells you anything but that is what happened.
Any further thoughts please?


Thank you for your time,

Degsy
Title: Re: Problem with 14.04
Post by: SeZo on October 11, 2014, 12:22:39 pm
I think you meant to do and not actually use it:
Yeah, try booting with the xforcevesa boot parameter .. then installing the nvidia drivers again.
Title: Re: Problem with 14.04
Post by: chemicalfan on October 13, 2014, 09:01:20 am
Maybe we could try re-installing xorg:

Code: [Select]
sudo apt-get update && sudo apt-get --reinstall install xorg
A bit make or break though  :-\
Title: Re: Problem with 14.04
Post by: Degsy on October 13, 2014, 01:55:15 pm
Hi Chemicalfan, sorry only just seen your post. Did try your suggestion but no joy I am afraid. Still boots OK to the old Kernel, it is a strange occurence isn't it?

Many thanks for your continued help, it is appreciated.

Cheers,
Degsy
Title: Re: Problem with 14.04
Post by: chemicalfan on October 13, 2014, 02:29:10 pm
Even more strange! So, at the moment, are the nvidia drivers installed? Or are you running the nouveau xorg drivers?

It's strange that the older kernel works  ???

I think that you should try an older kernel that's newer than 3.2, see at what point it stopped working. I can't remember if you're running 32 or 64bit, but see below for code:

For 32bit:
Code: [Select]
mkdir ~/temp && cd ~/temp && wget http://kernel.ubuntu.com/~kernel-ppa/mainline/v3.12.30-trusty/linux-image-3.12.30-031230-generic_3.12.30-031230.201410081535_i386.deb && dpkg -i *.deb

For 64bit:
Code: [Select]
mkdir ~/temp && cd ~/temp && wget http://kernel.ubuntu.com/~kernel-ppa/mainline/v3.12.30-trusty/linux-image-3.12.30-031230-generic_3.12.30-031230.201410081535_amd64.deb && dpkg -i *.deb

As stated by Mark, these won't update GRUB's default entry, so when the machine boots, you'll have to select the new one manually (remember the version number, 3.12.30)
Title: Re: Problem with 14.04
Post by: Mark Greaves (PCNetSpec) on October 13, 2014, 03:52:51 pm
Still not convinced this is a kernel problem, or Peppermint 5 would also be affected (same kernel).

We need to know if the nvidia drivers have been reinstalled yet .. Degsy hasn't furnished this info yet ??

Boot Ubuntu with the old kernel, then what's the output from:
Code: [Select]
dpkg -l | grep nvidia
and
Code: [Select]
sudo lshw -C display
Title: Re: Problem with 14.04
Post by: chemicalfan on October 13, 2014, 03:58:15 pm
Just a thought.... Degsy, can you run the same in Peppermint and post that up too?

Edit: Mark, I don't think it's a kernel problem either, but the fact the old kernel works suggests a compatibility issue somewhere with the new kernel. Maybe the old kernel has forced something else into some kind of fallback mode, which works? I was going with the "let's get the newest kernel possible working, then call it a day"
Title: Re: Problem with 14.04
Post by: Mark Greaves (PCNetSpec) on October 13, 2014, 04:16:00 pm
I'm getting the feeling that the nvidia drivers haven't been reinstalled yet, but for some reason the "neuoueveouiouxe" drivers just work better with the old kernel.
(as they needed xforcevesa in his other topic)

An older kernel only really makes sense if he's going to stick with "new-voe" drivers.. but sure can't hurt anything :)

BTW, you may have noticed I hate the name "nouveau" and not being French can never remember how to spell the damn thing  ::)
Title: Re: Problem with 14.04
Post by: Degsy on October 13, 2014, 05:16:27 pm
Hi Gents,
Sorry for the delay in responding, Monday is grandchildren pick up day.
Right here is the output Mark asked for from Ubuntu:

derek@derek-System-Product-Name:~$ dpkg -l | grep nvidia
derek@derek-System-Product-Name:~$ sudo lshw -C display
[sudo] password for derek:
  *-display               
       description: VGA compatible controller
       product: C61 [GeForce 7025 / nForce 630a]
       vendor: NVIDIA Corporation
       physical id: d
       bus info: pci@0000:00:0d.0
       version: a2
       width: 64 bits
       clock: 66MHz
       capabilities: pm msi vga_controller bus_master cap_list rom
       configuration: driver=nouveau latency=0
       resources: irq:21 memory:de000000-deffffff memory:c0000000-cfffffff memory:dd000000-ddffffff memory:dffc0000-dffdffff
derek@derek-System-Product-Name:~$

Will do the output from Peppermint ina minute.

Degsy
Title: Re: Problem with 14.04
Post by: Degsy on October 13, 2014, 05:20:34 pm
And from peppermint:

derek@derek-System-Product-Name ~ $ dpkg -l | grep nvidia
derek@derek-System-Product-Name ~ $ sudo lshw -C display
[sudo] password for derek:
  *-display               
       description: VGA compatible controller
       product: C61 [GeForce 7025 / nForce 630a]
       vendor: NVIDIA Corporation
       physical id: d
       bus info: pci@0000:00:0d.0
       version: a2
       width: 64 bits
       clock: 66MHz
       capabilities: pm msi vga_controller bus_master cap_list rom
       configuration: driver=nouveau latency=0
       resources: irq:43 memory:de000000-deffffff memory:c0000000-cfffffff memory:dd000000-ddffffff memory:dffc0000-dffdffff
derek@derek-System-Product-Name ~ $
 Degsy
Title: Re: Problem with 14.04
Post by: Mark Greaves (PCNetSpec) on October 13, 2014, 06:11:09 pm
OK, boot to Ubuntu using the xforcevesa kernel boot parameter (not the old kernel), then go to "Additional Drivers" and install the nvidia drivers it's offering you (331 from updates).

Once that's done (and it may take a few minutes), reboot.

Does Ubuntu work properly now ?
Title: Re: Problem with 14.04
Post by: Degsy on October 13, 2014, 08:16:30 pm
Hi Mark,
Have tried to do as you suggest but there is nothing happening once I click the nvidia driver box and then click update, the progress bar just sits there with about a half centimetre of orange and doesn't go any further.
I am getting to the point now where maybe this is time to call it a day with this, what do you think?


Regards,
Degsy
Title: Re: Problem with 14.04
Post by: Emegra on October 13, 2014, 09:27:27 pm
Hi Degsy

You may not be giving it enough time to update, I had a similar issue a while ago and it must have took fully 25 minutes to install the nvidia driver

Just a thought



Graeme
Title: Re: Problem with 14.04
Post by: Mark Greaves (PCNetSpec) on October 13, 2014, 10:05:36 pm
What Emegra said .. sometimes it appears to hang for quite some time before completing.

How long have you given it to complete ?
Title: Re: Problem with 14.04
Post by: Degsy on October 13, 2014, 10:43:26 pm
A couple of hours and it hadn't moved at all.

Degsy
Title: Re: Problem with 14.04
Post by: Mark Greaves (PCNetSpec) on October 13, 2014, 11:19:43 pm
OK, try this

first you MUST be booted into the latest kernel, not an earlier kernel.

Now open a terminal and run:
Code: [Select]
sudo apt-get install linux-headers-generic build-essential dkms synaptic
once that lot's done .. CLOSE the terminal

Open the Synaptic Package Manager, and search for the nvidia-331-updates package, and install it.

Once installed, close Synaptic .. now go to "Additional Drivers" and see if it'll activate the 331 "updates" driver.
Title: Re: Problem with 14.04
Post by: Degsy on October 13, 2014, 11:46:49 pm
First of all, I am unable to boot into the latest kernel and get an active mouse or keyboard, if I use Recovery mode then I can boot in, however once in the terminal with the requested command running I am asked to insert the "Ubuntu 14.04 LTS disc into the media drive. I do this but there is no response on pressing enter.

Sorry,

Degsy
Title: Re: Problem with 14.04
Post by: Mark Greaves (PCNetSpec) on October 14, 2014, 12:47:13 am
I thought you said you could boot from recovery mode > low graphics mode ?

or with xforcevesa as a kernel boot parameter ?



If necessary try the same thing from the old kernel .. then reboot
Title: Re: Problem with 14.04
Post by: Degsy on October 14, 2014, 11:32:24 am
Hi Mark,
I tried your last suggestion using the old Kernel and the result was as before, I was asked to insert the 14.04 disc in the drive and press enter, this I did but nothing further happens, the request is just repeated ad nauseam.
I really don't know where I am up to with this any more as there have been so many suggestions ( thank you all very much, they are much appreciated) of things to try out. There was an occasion when I did manage to boot into the new kernel using xforcevesa but that doesn't happen any more. It somehow feels as if the whole installation is not right somehow, would it be easier to go back and start again or even just reinstall Peppermint 5 on its own using the whole of the hard drive rather than dual boot?

Regards and many thanks,

Degsy
Title: Re: Problem with 14.04
Post by: chemicalfan on October 14, 2014, 11:55:28 am
That's a call you have to make - do you like Unity, and do you wish to keep the facility to use both desktop enviroments?
If you're not too fussed about Unity, then you could just delete the Ubuntu partition, and expand the Peppermint one to fill the space after backing up your stuff (no need to reinstall Peppermint)

If you want to keep both, it may well be simpler to reinstall Ubuntu over the top of the existing (being very careful with which partition you are targetting!). I fear some of these issues may have been caused by the upgrade process, as although Canonical advocate it as safe, isn't without these kind of risks.
Title: Re: Problem with 14.04
Post by: Degsy on October 14, 2014, 01:02:10 pm
Thanks Chemicalfan. I have to say I am not fussed about Unity, the whole hing has been a real odd saga from beginning to end, if I can just recap, I have a laptop which was running Pep 4 and the desktop running originally Ubuntu 12.04, tried to install Pep 5 on the laptop and it would not run, even from a live Dvd, tried it in the desktop and it was fine, so nothing wrong with the disc. Tried to run 14.04 on the desktop and that would not run, tried it on the a Laptop and it was fine, so I ended up installing 14.04 on my laptop and it's running fine. Then put Oeppermint 5 on the desktop alongside 12.04 which is also fine. I then tried the update route which has lead to the trouble I have now.
If I decide, which is likely, to ditch the 14.04 on the desktop, can you give me the "idiots guide" to removing the partition and expanding Pep 5 into the who.e of the hard drive?

Regards,
Degsy
Title: Re: Problem with 14.04
Post by: Mark Greaves (PCNetSpec) on October 14, 2014, 02:25:36 pm
Is there anything on the Ubuntu partition you need to keep ?  ... if not it'll probably be easier to remove Ubuntu and reinstall it from scratch.



I'm gonna guess it keeps asking for the 14.04 Disk because it's set as an active repository in your sources.

What's the contents of:
Code: [Select]
gedit /etc/apt/sources.list

Can you also confirm that you can connect to the internet when booted to the old kernel ?
Title: Re: Problem with 14.04
Post by: Degsy on October 14, 2014, 04:13:45 pm
Here is the output
derek@derek-System-Product-Name:~$ gedit /etc/apt/sources.list

(gedit:2471): Gtk-WARNING **: GtkScrolledWindow 0x8f0b3b8 is mapped but visible child GtkScrollbar 0x8f0d7c8 is not mapped

(gedit:2471): Gtk-WARNING **: GtkScrolledWindow 0x8f0b3b8 is mapped but visible child GtkScrollbar 0x8f0d950 is not mapped

(gedit:2471): Gtk-WARNING **: GtkScrolledWindow 0x8f0b3b8 is mapped but visible child GtkScrollbar 0x8f0d7c8 is not mapped

(gedit:2471): Gtk-WARNING **: GtkScrolledWindow 0x8f0b3b8 is mapped but visible child GtkScrollbar 0x8f0d950 is not mapped
# deb cdrom:[Ubuntu 11.04 _Natty Narwhal_ - Release i386 (20110427.1)]/ natty main restricted

# See http://help.ubuntu.com/community/UpgradeNotes (http://help.ubuntu.com/community/UpgradeNotes) for how to upgrade to
# newer versions of the distribution.
deb cdrom:[Ubuntu 14.04 LTS _Trusty Tahr_ - Release i386 (20140417)]/ trusty main restricted
deb http://gb.archive.ubuntu.com/ubuntu/ (http://gb.archive.ubuntu.com/ubuntu/) trusty main restricted
deb-src http://gb.archive.ubuntu.com/ubuntu/ (http://gb.archive.ubuntu.com/ubuntu/) trusty main restricted

## Major bug fix updates produced after the final release of the
## distribution.
deb http://gb.archive.ubuntu.com/ubuntu/ (http://gb.archive.ubuntu.com/ubuntu/) trusty-updates main restricted
deb-src http://gb.archive.ubuntu.com/ubuntu/ (http://gb.archive.ubuntu.com/ubuntu/) trusty-updates main restricted

## N.B. software from this repository is ENTIRELY UNSUPPORTED by the Ubuntu
## team. Also, please note that software in universe WILL NOT receive any
## review or updates from the Ubuntu security team.
deb http://gb.archive.ubuntu.com/ubuntu/ (http://gb.archive.ubuntu.com/ubuntu/) trusty universe
deb-src http://gb.archive.ubuntu.com/ubuntu/ (http://gb.archive.ubuntu.com/ubuntu/) trusty universe
deb http://gb.archive.ubuntu.com/ubuntu/ (http://gb.archive.ubuntu.com/ubuntu/) trusty-updates universe
deb-src http://gb.archive.ubuntu.com/ubuntu/ (http://gb.archive.ubuntu.com/ubuntu/) trusty-updates universe

## N.B. software from this repository is ENTIRELY UNSUPPORTED by the Ubuntu
## team, and may not be under a free licence. Please satisfy yourself as to
## your rights to use the software. Also, please note that software in
## multiverse WILL NOT receive any review or updates from the Ubuntu
## security team.
deb http://gb.archive.ubuntu.com/ubuntu/ (http://gb.archive.ubuntu.com/ubuntu/) trusty multiverse
deb-src http://gb.archive.ubuntu.com/ubuntu/ (http://gb.archive.ubuntu.com/ubuntu/) trusty multiverse
deb http://gb.archive.ubuntu.com/ubuntu/ (http://gb.archive.ubuntu.com/ubuntu/) trusty-updates multiverse
deb-src http://gb.archive.ubuntu.com/ubuntu/ (http://gb.archive.ubuntu.com/ubuntu/) trusty-updates multiverse

## Uncomment the following two lines to add software from the 'backports'
## repository.
## N.B. software from this repository may not have been tested as
## extensively as that contained in the main release, although it includes
## newer versions of some applications which may provide useful features.
## Also, please note that software in backports WILL NOT receive any review
## or updates from the Ubuntu security team.
# deb http://gb.archive.ubuntu.com/ubuntu/ (http://gb.archive.ubuntu.com/ubuntu/) natty-backports main restricted universe multiverse
# deb-src http://gb.archive.ubuntu.com/ubuntu/ (http://gb.archive.ubuntu.com/ubuntu/) natty-backports main restricted universe multiverse

deb http://security.ubuntu.com/ubuntu (http://security.ubuntu.com/ubuntu) trusty-security main restricted
deb-src http://security.ubuntu.com/ubuntu (http://security.ubuntu.com/ubuntu) trusty-security main restricted
deb http://security.ubuntu.com/ubuntu (http://security.ubuntu.com/ubuntu) trusty-security universe
deb-src http://security.ubuntu.com/ubuntu (http://security.ubuntu.com/ubuntu) trusty-security universe
deb http://security.ubuntu.com/ubuntu (http://security.ubuntu.com/ubuntu) trusty-security multiverse
deb-src http://security.ubuntu.com/ubuntu (http://security.ubuntu.com/ubuntu) trusty-security multiverse

## Uncomment the following two lines to add software from Canonical's
## 'partner' repository.
## This software is not part of Ubuntu, but is offered by Canonical and the
## respective vendors as a service to Ubuntu users.
# deb http://archive.canonical.com/ubuntu (http://archive.canonical.com/ubuntu) natty partner
# deb-src http://archive.canonical.com/ubuntu (http://archive.canonical.com/ubuntu) natty partner

## This software is not part of Ubuntu, but is offered by third-party
## developers who want to ship their latest software.
deb http://extras.ubuntu.com/ubuntu (http://extras.ubuntu.com/ubuntu) trusty main
deb-src http://extras.ubuntu.com/ubuntu (http://extras.ubuntu.com/ubuntu) trusty main
This has been posted using the old kernel, so yes Internet is connected.

Thanks,
Degsy
Title: Re: Problem with 14.04
Post by: Mark Greaves (PCNetSpec) on October 14, 2014, 06:38:16 pm
Run:
Code: [Select]
sudo cp -v /etc/apt/sources.list /etc/apt/sources.list.original
then
Code: [Select]
sudo gedit /etc/apt/sources.list
and comment out the line:-

deb cdrom:[Ubuntu 14.04 LTS _Trusty Tahr_ - Release i386 (20140417)]/ trusty main restricted

so it now reads:

# deb cdrom:[Ubuntu 14.04 LTS _Trusty Tahr_ - Release i386 (20140417)]/ trusty main restricted

SAVE the file and exit gedit.

Back in the terminal run:
Code: [Select]
sudo apt-get update
then
Code: [Select]
sudo apt-get install linux-headers-generic build-essential dkms synaptic nvidia-331-updates
When finished, close the terminal and go to "Additional Drivers" and see if it will let you activate the nvidia 331 updates driver.
Title: Re: Problem with 14.04
Post by: Degsy on October 14, 2014, 07:31:42 pm
Yeeeeeeeeeesssssssss!!!!!!!!!

Thank you Mark and everybody else who has been offering their help, the last advice worked, booted into straight away without problem, sending this from Ubuntu 14.04 using the latest kernel

Thanks again everybody, so sorry this has been such a long drawn out road but you have get me there.
Just wish i understood everything that I had done following your advice.


Cheers,
Degsy
Title: Re: Problem with 14.04
Post by: Degsy on October 14, 2014, 07:52:56 pm
I now notice that the Software updater is offering updates, is it safe for me to run the Updater and update the system?
I feel sure it is but just want to check, dont want to b$ll$x the system after all the help I have had to get it up and running.


Degsy
Title: Re: Problem with 14.04
Post by: Mark Greaves (PCNetSpec) on October 14, 2014, 09:57:28 pm
Well you'll have to update some time .. so yeah, let em rip and let us know how it goes :)

If it updates without issue, can you also remember to mark this topic (SOLVED) .. TIA :)
Title: Re: Problem with 14.04
Post by: Degsy on October 14, 2014, 11:16:14 pm
Carried out the updates and rebooted, no problems encountered so have marked the topic solved.

Once again many thanks to all those who have helped with this.

Cheers,
Degsy
Title: Re: Problem with 14.04 (Solved)
Post by: Mark Greaves (PCNetSpec) on October 14, 2014, 11:47:45 pm
For my part, you're welcome :)
Title: Re: Problem with 14.04 (Solved)
Post by: chemicalfan on October 15, 2014, 08:34:10 am
Glad to see you got it sorted  ;D

Guess the nouveau driver isn't the "safe pair of hands" I've always thought it to be!
(every day is a school day!)
Title: Re: Problem with 14.04 (Solved)
Post by: Degsy on October 15, 2014, 09:34:49 am
This is probably not a question that is easy to answer but it appears to me ( and I know little) that by inserting the # and commenting out that line the system was able to update and allow me to get the proprietary drivers, so how did that line that needed the # get there in the first place?


Regards,
Degsy
Title: Re: Problem with 14.04 (Solved)
Post by: chemicalfan on October 15, 2014, 01:09:41 pm
I'm not 100% sure, it could be a bug in the upgrade process that inserted it?
SimplePortal 2.3.3 © 2008-2010, SimplePortal