21 replies to this topic

[réjean]

Hi all!
I have installed Mint on /sda5 (hd0,4). The bootloader must be on the /root partition because when I reboot I get the PCLinuxOS (zen) bootloader.. So I edited /boot/grub/menu.lst and added the following entry;

title Linux Mint
root (hd0,4)
make active
chainloader +1

Unfortunately it doesn't work. I know that it doesn't have the same grub that I am used to but I managed to find a 'initrd.img-3.2.0-23-generic'  and a 'vmlinuz-3.2.0-23-generic' in /boot.
How can I edit PCLinuxOS bootloader so that I could start Mint?

So I tried;

title Linux Mint
kernel (hd0,4)/boot/vmlinuz-3.2.0-23-generic BOOT_IMAGE=mint root=(hd0,4) quiet nokmsboot  vmalloc=256M acpi=on
initrd (hd0,4)/boot/initrd.img-3.2.0-23-generic

Edited by réjean, 06 August 2012 - 01:52 PM.

[burninbush]

réjean, on 06 August 2012 - 01:38 PM, said:

Hi all!

So I tried;

title Linux Mint
kernel (hd0,4)/boot/vmlinuz-3.2.0-23-generic BOOT_IMAGE=mint root=(hd0,4) quiet nokmsboot  vmalloc=256M acpi=on
initrd (hd0,4)/boot/initrd.img-3.2.0-23-generic

Hi rejean ... where you have root=(hd0,4) above on the kernel line, I'd change that to root=/dev/sda5.  For what it's worth, I don't think you need [for now] the items you have on the rest of that line [quiet, etc.]

[V.T. Eric Layton]

burninbush is correct, réjean. Here's my Linux Mint menu.lst (GRUB legacy) entry:

# (6) Linux Mint 12-64
title linux mint (t3)
root  (hd2,9)
kernel  /boot/vmlinuz-3.0.0-12-generic root=/dev/sdb10 ro
initrd  /boot/initrd.img-3.0.0-12-generic

This is a direct boot of the kernel and initrd (my preferred method of booting) not a chainload.

[réjean]

Thanks guys! I can login now. The main thing to do next is to get access to xorg. I can go in a terminal, login as rejean and su but everything I tried failed. I tried everything from 'dpkg-reconfigure xserver-xorg' to 'xorgconfig', from 'XFdrake' to the old 'XFree86-configure' via 'dpkg-reconfigure xserver-xfree86' and 'xorgsetup' to no avail.
Any suggestion?

[réjean]

So I managed to get a graphic by pressing F3 at boot time and choosing NO ACPI. Then I had to change the ownership of /home to myself 'rejean'. Now I have to install NVIDIA except that I cannot  open Synaptic for some strange reason. I can open a terminal and 'su' and I could do a 'apt-get install' but I don't know what file to get for my GeForce Fx5500.
What do you suggest?

[réjean]

I have downloaded NVIDIA-Linux-x86-173.14.35-pkg1.run and I'll go and see if Bruno had any tip about installing it.

According to his tip I was supposed to;

rejean@rejean-desktop ~ $ su
Password:
rejean-desktop rejean # gedit /etc/inittab

but I got;

(gedit:2851): EggSMClient-WARNING **: Failed to connect to the session manager: None of the authentication protocols specified are supported


** (gedit:2851): WARNING **: Could not connect to session bus
rejean-desktop rejean # 

Edited by réjean, 07 August 2012 - 11:24 AM.

[securitybreach]

That part is not needed on LM: http://forums.linuxm...hp?t=96260&f=42

[crp]

réjean, on 07 August 2012 - 11:13 AM, said:

So I managed to get a graphic by pressing F3 at boot time and choosing NO ACPI. Then I had to change the ownership of /home to myself 'rejean'. [...]

That sounds very wrong. What is the gui creating that lead you to redo the ownership of /home?

[réjean]

crp, on 07 August 2012 - 11:45 AM, said:

That sounds very wrong. What is the gui creating that lead you to redo the ownership of /home?

My guess would be that instead of creating a new /home I chose one that already existed. I don't think I will be doing that again because in doing so I lost my PCLinuxOS /home which I had been using for the last 4 months or so and I am now using an older one . What I will do from now on when I install a new distro is create a new /home and than copy the content of the one I am actually using into it.

securitybreach, on 07 August 2012 - 11:33 AM, said:

That part is not needed on LM: http://forums.linuxm...hp?t=96260&f=42

Thanks Josh! I'll follow the instructions to the letter probably later this evening.

[securitybreach]

réjean, on 07 August 2012 - 12:25 PM, said:

Thanks Josh! I'll follow the instructions to the letter probably later this evening.

No problem

This may also help: Nvidia Drivers Collection for Ubuntu 12.10 Quantal/Ubuntu 12.04 Precise/Ubuntu 11.10 Oneiric/Ubuntu 11.04 Natty/Ubuntu 10.04/Linux Mint 13/12/11/10/9

[réjean]

I tried just about everything from the thread that josh recommended and more and I still get the following when I go to System tools->Administration->NVIDIA X Server Settings;



If I open a console as 'su' and do the following;

rejean@rejean-desktop ~ $ su
Password:
rejean-desktop rejean # nvidia-xconfig

Using X configuration file: "/etc/X11/xorg.conf".
Backed up file '/etc/X11/xorg.conf' as '/etc/X11/xorg.conf.backup'
New X configuration file written to '/etc/X11/xorg.conf'

rejean-desktop rejean #

and then try;

rejean-desktop rejean # kwrite /etc/X11/xorg.conf
The program 'kwrite' is currently not installed.  You can install it by typing:
apt-get install kwrite
rejean-desktop rejean # apt-get install kwrite
Reading package lists... Done
Building dependency tree	  
Reading state information... Done
The following NEW packages will be installed:
  kwrite
0 upgraded, 1 newly installed, 0 to remove and 349 not upgraded.
Need to get 70.4 kB of archives.
After this operation, 279 kB of additional disk space will be used.
Get:1 http://archive.ubuntu.com/ubuntu/ precise-updates/main kwrite i386 4:4.8.4-0ubuntu0.1 [70.4 kB]
Fetched 70.4 kB in 0s (89.3 kB/s)
Selecting previously unselected package kwrite.
(Reading database ... 154457 files and directories currently installed.)
Unpacking kwrite (from .../kwrite_4%3a4.8.4-0ubuntu0.1_i386.deb) ...
Processing triggers for desktop-file-utils ...
Processing triggers for bamfdaemon ...
Rebuilding /usr/share/applications/bamf.index...
Processing triggers for gnome-menus ...
Setting up kwrite (4:4.8.4-0ubuntu0.1) ...
rejean-desktop rejean # kwrite /etc/X11/xorg.conf

(process:2104): GConf-WARNING **: Client failed to connect to the D-BUS daemon:
Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken.

(process:2104): GConf-WARNING **: Client failed to connect to the D-BUS daemon:
Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken.

(process:2104): GConf-WARNING **: Client failed to connect to the D-BUS daemon:
Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken.
QGtkStyle was unable to detect the current GTK+ theme.
Qt: Session management error: None of the authentication protocols specified are supported
kwrite(2104)/kdeui (kdelibs): Session bus not found
To circumvent this problem try the following command (with Linux and bash)
export $(dbus-launch)
KCrash: Application 'kwrite' crashing...
KCrash: Attempting to start /usr/lib/kde4/libexec/drkonqi from kdeinit
sock_file=/root/.kde/socket-rejean-desktop/kdeinit4__0
Warning: connect() failed: : No such file or directory
KCrash: Attempting to start /usr/lib/kde4/libexec/drkonqi directly

(process:2107): GConf-WARNING **: Client failed to connect to the D-BUS daemon:
Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken.

(process:2107): GConf-WARNING **: Client failed to connect to the D-BUS daemon:
Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken.

(process:2107): GConf-WARNING **: Client failed to connect to the D-BUS daemon:
Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken.
QGtkStyle was unable to detect the current GTK+ theme.
drkonqi(2107)/kdeui (kdelibs): Session bus not found
To circumvent this problem try the following command (with Linux and bash)
export $(dbus-launch)
rejean-desktop rejean #

I did open synaptic from a console as 'su' (doing it from System Tools wont work) and downloaded and installed nvidia current with nvidia-settings but it didn't change much so I replaced nvidia current with nvidia 173 and still the same message.
What more can I do?

[V.T. Eric Layton]

Rejean,

You don't need Kwrite. It's just an editor. When you see commands like that the others have posted for you to follow, you can use the editor of your choice... Gedit, mousepad, leafpad, whatever. You didn't need to install Kwrite. just remove it and follow the command using whatever editor you have available.

[réjean]

V.T. Eric Layton, on 07 August 2012 - 04:21 PM, said:

Rejean,

You don't need Kwrite. It's just an editor. When you see commands like that the others have posted for you to follow, you can use the editor of your choice... Gedit, mousepad, leafpad, whatever. You didn't need to install Kwrite. just remove it and follow the command using whatever editor you have available.

the reason I installed kwrite is because I had tried to open '/etc/X11/xorg.conf'' is because it wouldn't open with gedit (which was already installed but not working) so I uninstalled 'kwrite' and marked 'gedit' for reinstallation and I can at least see what's in  '/etc/X11/xorg.conf''.

# nvidia-xconfig: X configuration file generated by nvidia-xconfig
# nvidia-xconfig:  version 302.17  (buildmeister@swio-display-x86-rhel47-07.nvidia.com)  Tue Jun 12 19:45:36 PDT 2012


Section "ServerLayout"
	Identifier	 "Default Layout"
	Screen		 "Default Screen" 0 0
	InputDevice	"Keyboard0" "CoreKeyboard"
	InputDevice	"Mouse0" "CorePointer"
EndSection

Section "InputDevice"

	# generated from default
	Identifier	 "Keyboard0"
	Driver		 "keyboard"
EndSection

Section "InputDevice"

	# generated from default
	Identifier	 "Mouse0"
	Driver		 "mouse"
	Option		 "Protocol" "auto"
	Option		 "Device" "/dev/psaux"
	Option		 "Emulate3Buttons" "no"
	Option		 "ZAxisMapping" "4 5"
EndSection

Section "Monitor"
	Identifier	 "Configured Monitor"
EndSection

Section "Device"
	Identifier	 "Configured Video Device"
	Driver		 "nvidia"
EndSection

Section "Screen"
	Identifier	 "Default Screen"
	Device		 "Configured Video Device"
	Monitor		"Configured Monitor"
	SubSection	 "Display"
		Modes	  "nvidia-auto-select"
	EndSubSection
EndSection 

Should I replace  " Driver "nvidia" " with nv or something. I would like to get more than 800 X 600 for resolution.

[securitybreach]

Have you tried opening nvidia-settings as root and configuring it that way? You should not have to manually do this. That is how you are supposed to configure nvidia based systems.

[réjean]

There is definitely something wrong with this installation even if the SHA256sum was good. Maybe I'll try again installing the -64 bit instead of the -32 bit.
If I try to switch user and login in as 'root' I am being ignore and rejean eventually is the one that gets in. If I try;

rejean@rejean-desktop ~ $ su
Password:
rejean-desktop rejean # nvidia-settings
rejean-desktop rejean #

I get the same message and windows that I posted.

I am replying from LinuxMint so it does work somehow. Meanwhile it took me about 2 hours to install OpenSUSE 12.1 -64 bit, to update and upgrade and to install NVIDIA using zypper.This is more the kind of OS that I like.
I haven't given up on Linux Mint yet.

Edited by réjean, 07 August 2012 - 08:48 PM.

[V.T. Eric Layton]

Josh is right. You shouldn't have to be manually editing xorg.conf. Linux Mint is one of the most automagic distros out there. Just click and go, usually.

If you have a 64 bit processor, you should DEFINITELY be installing the 64 bit version or everything.

[sunrat]

I think the main reason your gedit and kwrite commands aren't working is you need to use sudo; su won't open programs in X by itself.
Also the best way to install nvidia drivers is through the package manager. SB's link in post #10 gives this which is all you should need to do:

sudo apt-add-repository ppa:ubuntu-x-swat/x-updates
sudo apt-get update
sudo apt-get install nvidia-current

Even there it seems strange that it is in a PPA, in Debian it is in the standard non-free repos.

[réjean]

sunrat, on 07 August 2012 - 09:59 PM, said:

I think the main reason your gedit and kwrite commands aren't working is you need to use sudo; su won't open programs in X by itself.
Also the best way to install nvidia drivers is through the package manager. SB's link in post #10 gives this which is all you should need to do:

sudo apt-add-repository ppa:ubuntu-x-swat/x-updates
sudo apt-get update
sudo apt-get install nvidia-current

Even there it seems strange that it is in a PPA, in Debian it is in the standard non-free repos.

I might not have been clear but I had also tried that and it didn't change anything. Thanks for the tip about the difference between su and sudo btw.

[réjean]

rejean-desktop rejean # sudo apt-get install nvidia-current
Reading package lists... Done
Building dependency tree	  
Reading state information... Done
nvidia-current is already the newest version.
nvidia-current set to manually installed.
0 upgraded, 0 newly installed, 0 to remove and 349 not upgraded.
rejean-desktop rejean #
rejean-desktop rejean # sudo nvidia-settings
rejean-desktop rejean # sudo nvidia-xconfig

Using X configuration file: "/etc/X11/xorg.conf".
Backed up file '/etc/X11/xorg.conf' as '/etc/X11/xorg.conf.backup'
New X configuration file written to '/etc/X11/xorg.conf'

rejean-desktop rejean #

and yet;

[saturnian]

sunrat, on 07 August 2012 - 09:59 PM, said:

I think the main reason your gedit and kwrite commands aren't working is you need to use sudo; su won't open programs in X by itself.

In the Ubuntu-based Linux Mint versions, at least, for graphical apps it'll be like in Ubuntu. So, gksu gedit and kdesu kwrite. Check out the "Graphical sudo" section here: https://help.ubuntu....munity/RootSudo

According to that, I guess you could also use gksudo and kdesudo, but in Ubuntu and Mint I've always just used gksu and kdesu for gedit and kwrite, respectively.

[réjean]

Thank saturnian! I'll give it a try.

[sunrat]

Thanks saturnian. I actually use sux so not so familiar with *buntuz. Still, what I said about su is still valid (I think ).