hello
with opensuse 13.1
when i do
su
init 3
i get this prined on the screen
“Reached target Graphical Interface”
and no terminal and the keyboard does not respond
i do i reach text mode with network
jean pierre aubry
Hi,
init is deprecated on 13.x so you can checkout this link.
http://www.freedesktop.org/wiki/Software/systemd/FrequentlyAskedQuestions/
That should work unless you have some issues with graphics/video drivers.
Systemd is in charge now, so perhaps that is confusing the behaviour for you
https://en.opensuse.org/openSUSE:Systemd_tips
This reference might be useful too
https://activedoc.opensuse.org/book/opensuse-reference/chapter-8-the-systemd-daemon#sec.boot.systemd.targets
For reference:
ls -l /usr/lib/systemd/system/runlevel*.target
lrwxrwxrwx 1 root root 15 Jun 18 2014 /usr/lib/systemd/system/runlevel0.target -> poweroff.target
lrwxrwxrwx 1 root root 13 Jun 18 2014 /usr/lib/systemd/system/runlevel1.target -> rescue.target
lrwxrwxrwx 1 root root 17 Jun 18 2014 /usr/lib/systemd/system/runlevel2.target -> multi-user.target
lrwxrwxrwx 1 root root 17 Jun 18 2014 /usr/lib/systemd/system/runlevel3.target -> multi-user.target
lrwxrwxrwx 1 root root 17 Jun 18 2014 /usr/lib/systemd/system/runlevel4.target -> multi-user.target
lrwxrwxrwx 1 root root 16 Jun 18 2014 /usr/lib/systemd/system/runlevel5.target -> graphical.target
lrwxrwxrwx 1 root root 13 Jun 18 2014 /usr/lib/systemd/system/runlevel6.target -> reboot.target
thanks all, but
i am very sorry but typing
systemctl isolate multi-user.target
produces the same screen output as typing init 3
which by the way does the job on my other computer
and i want to set to this run level to execute a nividia driver as my graphic card does not behave as on the others computers
Sorry, but this doesn’t make sense to me. Can you clarify further?
Are you trying to explain that your nvidia driver install is not working? (ie you can’t get a working X-server?)
After you init 3
Just use Ctrl-Alt-F2 or trl-Alt-F1
to get the console, both 13.1 and 13.2 has this problem.
On 2015-01-12 10:36, jetchisel wrote:
> Hi,
>
> init is deprecated on 13.x so you can checkout this link.
No, it is not.
Telcontar:~ # which init
/sbin/init
Telcontar:~ # l /sbin/init
lrwxrwxrwx 1 root root 26 Jun 25 2014 /sbin/init -> ../usr/lib/systemd/systemd*
Telcontar:~ #
It is a symllink to systemd, so it absolutely knows what to do when invoked.
–
Cheers / Saludos,
Carlos E. R.
(from 13.1 x86_64 “Bottle” at Telcontar)
On 2015-01-12 10:06, dedalus2 wrote:
>
> hello
>
> with opensuse 13.1
> when i do
> su
> init 3
> i get this prined on the screen
> “Reached target Graphical Interface”
> and no terminal and the keyboard does not respond
Correct procedure is:
Log out from graphical session.
Switch to text mode, via pressing ctrl-alt-f1.
Log-in as root⁽¹⁾.
Issue “init 3”.
Then do whatever other work you need.
(1) In text mode, it makes no sense to log-in as user, then su. Just
log-in directly as root. However, if for whatever reason you insist on
using “su”, don’t use plain “su”, but “su -”.
–
Cheers / Saludos,
Carlos E. R.
(from 13.1 x86_64 “Bottle” at Telcontar)
On Mon 12 Jan 2015 10:16:02 AM CST, dedalus2 wrote:
thanks all, but
i am very sorry but typing
systemctl isolate multi-user.target
produces the same screen output as typing init 3
which by the way does the job on my other computer
and i want to set to this run level to execute a nividia driver as my
graphic card does not behave as on the others computers
Hi
If you use set-default;
systemctl set-default multi-user.target
systemctl reboot
<run nvidia setup>
systemctl set-default graphical.target
systemctl reboot
–
Cheers Malcolm °¿° LFCS, SUSE Knowledge Partner (Linux Counter #276890)
SUSE Linux Enterprise Desktop 12 GNOME 3.10.1 Kernel 3.12.28-4-default
If you find this post helpful and are logged into the web interface,
please show your appreciation and click on the star below… Thanks!
thanks to all who answered this thread
i am now able to connect as i want
init works OK if one type Cltrl+alt+F1 as pointed out by conram
but this did not solve at all the NVIDIA issue
which i solved after a few hours of headache
which made me discover a few issues
i made un update with the dvd inserted and YAST decided by itself that it was time to kill a few
apps like midori, mplayer2, and a few dozen of others
i am getting a bit tired with YAST behavior getting worse and worse since a few years
On 2015-01-12 18:16, dedalus2 wrote:
> which made me discover a few issues
> i made un update with the dvd inserted and YAST decided by itself that
> it was time to kill a few
> apps like midori, mplayer2, and a few dozen of others
“Kill” in Linux means “forcefully stopping a running program”.
Did YaST do that, are you absolutely sure? Only the kernel does that,
when there is not enough RAM, so save the system from crashing. Its an
emergency measure.
Or do you mean something different?
Please explain.
–
Cheers / Saludos,
Carlos E. R.
(from 13.1 x86_64 “Bottle” at Telcontar)
It is just a symlink yes, so not deprecated 
right for the word kill, i used the wrong word
i meant uninstall
for example in the package list on running the update midori was checked as to be removed
(in red if remember well) and i could not uncheck it
in addition the midori settings in $HOME./config/midori were all cleared
and i had to reinstall it with all the bookmarks lost
an this is the same for a number of apps which i have to probably discover yet
i believe this never happen in before 13.x versions (my first SuSE install was in 1995, 4.5)
i had the same thing happening in an update from 13.1 to 13.2 but much worse in that case
i have several computer and a few other disks for some of them so i can experiment with the install
i am trying to keep safe my working one
my last tests, install settings and running LAN, settings graphics show that opensuse is loosing its edge over the other one these days
Yast will not uninstall anything unless you tell it to. I have never seen it do otherwise. You should not have the DVD an active repo normally unless you are getting stuff from it.
On 2015-01-13 17:06, gogalthorp wrote:
>
> Yast will not uninstall anything unless you tell it to. I have never
> seen it do otherwise. You should not have the DVD an active repo
> normally unless you are getting stuff from it.
When internet is slow, it makes sense to keep it.
–
Cheers / Saludos,
Carlos E. R.
(from 13.1 x86_64 “Bottle” at Telcontar)
On 2015-01-13 08:16, dedalus2 wrote:
> right for the word kill, i used the wrong word
> i meant uninstall
> for example in the package list on running the update midori was checked
> as to be removed
> (in red if remember well) and i could not uncheck it
> in addition the midori settings in $HOME./config/midori were all cleared
In red?
Maybe that means that the repo that should contain it was not
accessible, and it had to do weird things to find a solution. You should
have aborted.
But YaST could not delete home configs, that has to be done by the
package itself, via install/uninstall scripts. And I don’t remember ever
seeing it.
> and i had to reinstall it with all the bookmarks lost
> an this is the same for a number of apps which i have to probably
> discover yet
>
>
> i believe this never happen in before 13.x versions (my first SuSE
> install was in 1995, 4.5)
>
>
> i had the same thing happening in an update from 13.1 to 13.2 but much
> worse in that case
If you are doing a system upgrade with the DVD, as it does not contain
all the packages, it can replace or remove things that it can not find,
like packman.
–
Cheers / Saludos,
Carlos E. R.
(from 13.1 x86_64 “Bottle” at Telcontar)
Not active You always have to put the install disk in any time you do any software install/removal operations. And the DVD has no where the amount of software that is not auto installed then the repos. Maybe if you have no internet. Also the DVD by definition has old unpatched versions.
On 2015-01-13 21:46, gogalthorp wrote:
>
> robin_listas;2688971 Wrote:
>> On 2015-01-13 17:06, gogalthorp wrote:
>>>
>>> Yast will not uninstall anything unless you tell it to. I have never
>>> seen it do otherwise. You should not have the DVD an active repo
>>> normally unless you are getting stuff from it.
>>
>> When internet is slow, it makes sense to keep it.
> Not active You always have to put the install disk in any time you do
> any software install/removal operations. And the DVD has no where the
> amount of software that is not auto installed then the repos. Maybe if
> you have no internet. Also the DVD by definition has old unpatched
> versions.
As I had to download the DVD at some time, I just need to tell YaST to
add the ISO file of the DVD somewhere as a repo, instead of the external
DVD. As I keep the DVD image in the HD in case it is needed for another
install, it doesn’t hurt to add it as a permanent source, and YaST never
has to ask me to insert the disk, externally.
There are packages that are not updated in months: the other day I
installed one for 13.1, that came from the DVD. A year after release…
–
Cheers / Saludos,
Carlos E. R.
(from 13.1 x86_64 “Bottle” at Telcontar)