Can't see command prompt (CLI) when X is shut down.

[frenchiveruti]

EASY EXPLANATION:
https://youtu.be/chawd1yC1jY (Short ~3minute video explaining the issue I have)
https://youtu.be/I47fDfU9d28 (a little longer ~5min video with more detail on my actions)


REGULAR, INCOMPREHENSIBLE EXPLANATION:
Hello Everyone, my issue is simple yet at the same time very complicated.
We all know this beauty:
https://i.imgur.com/tJPBmSW.jpg
Well, it turns out that this beauty is on "top" of the "command prompt" layer of the screen, so to speak, lets say that when I do "ALT+CTRL+F2" I go to another of those so called "tty" where I can see the command prompt that runs without the Xserver.
(To be extremely clear, you can get to this screen by going to "MENU --> EXIT --> Exit to Prompt")

Well, it turns out that I only see the "loading" screen depicted before:
https://i.imgur.com/tJPBmSW.jpg

I'm really confused because I don't know what causes this issue, and it started a few days ago, but I didn't touch anything around the boot sequence I have:
(By the way, the Xserver works fine, I didn't touch anything around it nor I updated any drivers, I really don't know what could be broken, besides my hearth)
Finally, both the command prompt and the tty worked before, this is a new issue I've encountered.

Code: Select all

find --set-root --ignore-floppies --ignore-cd /frenchtahr/initrd.gz
  kernel /frenchtahr/vmlinuz psubdir=frenchtahr pmedia=usbflash pfix=copy pkeys=es
  initrd /frenchtahr/initrd.gz

Can someone give me a hand on this issue? I really need to run a few commands with X turned off but I can't do it If I can't see what's happening.

EDIT:
Ok, so here's my pup info:

• Tahrpup
• 64bits
• 6.0.5
• SaveFolder
• FRUGAL Install (the one that loads on ram and saves to a savefolder)
• EXT4 filesystem, only one partition under /dev/sda1

Here's what it works:

• Nvidia Propiertary graphics Xserver
• Window manager
• EXIT options, even the one that says EXIT TO PROMTP works
• Menus
• Browser
• General user experience.

Here's what doesn't work:

• User interface based on text that you can access by killing X via either by CTRL+ALT+BACKSPACE or via the Menu steps I said before.
  When I kill X I get this: https://i.imgur.com/tJPBmSW.jpg

If I go into RAM mode, the TTY WORKS AS INTENDED. So my issue is around my savefolder on some command that goes between the module load and the x launch.[/b][/list][/list]

[trapster]

If you don't want to boot into X, try pfix=nox on the kernel line.
I'm not sure if it will work on a full install

[bigpup]

MENU --> EXIT -->
Other options working OK?

The program file for the MENU --> EXIT --> is logout_gui

It is located in /usr/sbin

Could try replacing it with the one you can find in the original Tahrpup iso package.
It will be in the Tahrpup sfs

Or just replace the Tahrpup sfs in the install, with the one from the Tahrpup iso.

Can also look in the tahrpupsave and make sure there is no logout_gui in /usr/sbin
If there is. It is not suppose to be there.
Should be nothing in the save about logout_gui

[frenchiveruti]

Hi guys thanks for the replies.
I blame myself that I forgot to post more info on what pup I'm running and what works and what does not.
I updated the post so its clearer.

[frenchiveruti]

So, I decided to try and made a video sorry for my broken english:
https://youtu.be/chawd1yC1jY
I hope that clears that out!

[bigpup]

look in the tahrpupsave and make sure there is no logout_gui in /usr/sbin
If there is. It is not suppose to be there.
Should be nothing in the save about logout_gui

Get Tahrpup booted in ram mode not using the save.
In Rox file manager.
Go to the Tahrsave and left click on it to open.
Go to /usr/sbin in the save.

What happens????

[musher0]

Good old < Ctrl-Alt-Backspace > doesn't work? That's impossible.

The only way it is possible is if your keyboard is not configured properly. If the keyboard
file for your language is missing or is in the wrong place, for some reason --.or you
tampered with it accidentally, or something like that.

BFN.

[frenchiveruti]

Ok guys I'll post a video again because it seems I can't make myself clear, please hold on a little.

[frenchiveruti]

Ok, here's a new video explaining the issue, I believe it's a little better. It's 5 minutes long but It shows what happens very well:
https://youtu.be/I47fDfU9d28
Thanks for anything you find on it

[bigpup]

I understand, using the save it does what you keep talking about and have shown us.

Easy fix is to use the good copy of the save you made at some point.
Oh, you did make a copy of the save so it would be easy to recover?

Can check this.
.jwm is a hidden directory. In Rox file manager click on the eye icon so you can see hidden stuff.
/root/.jwm/jwmrc-personal
Right click on jwmrc-personal and select open as text.

Anything in it look like it could be causing this?

[frenchiveruti]

I understand, using the save it does what you keep talking about and have shown us.

Easy fix is to use the good copy of the save you made at some point.
Oh, you did make a copy of the save so it would be easy to recover?

Can check this.
.jwm is a hidden directory. In Rox file manager click on the eye icon so you can see hidden stuff.
/root/.jwm/jwmrc-personal
Right click on jwmrc-personal and select open as text.

Anything in it look like it could be causing this?

I have a copy that's absurdly old, but I would like to know what causes this to be able to fix it either via a comparision between files between each save or at least something that points to where the problem could be.

I have checked .jwm as you asked me to do. There's nothing weird in it, and I think it shouldn't have any impact as the window manager gets killed when I kill X, and I have to type xwin in order to "make it start" again. Right?

[theru]

It's quite puzzling that f2 and f3 give the same screen as f1. Are tty2 and tty3 active? You can check that by checking the output of ps in a terminal window.

The last time I had the command prompt acting up like that was when I launched midnight commander in the background by mistake. My workaround at that time was typing exit until I got logged out and logged in again (happens automatically at tty1). It did affect the shutdown procedure but when I typed xwin again it loaded the necessary scripts and shut down normally afterwards. What happens if you boot to command prompt by using the boot option pfix=nox?

The screen seems to go black around the time that the nvidia driver gets loaded and the screen changes resolution. What happens if you fall back to xvesa?

[Sailor Enceladus]

[frenchiveruti]

Ok guys, this issue is under Nvidia:
https://devtalk.nvidia.com/default/topi ... shutdown/5
It's ironic I can't update the driver because I can't read the console.
I'll deal with this when Xenial comes out as I will start A fresh linux experience.

Thanks for the feedback.

[bigpup]

If you do a normal bootup.
Use PPM(Puppy Package Manager) uninstall to uninstall the Nvidia driver.
Reboot.
Should be using the supplied Nouveau driver that comes with Puppy.

Go get the newer Nvidia driver run package and install it.

[frenchiveruti]

If you do a normal bootup.
Use PPM(Puppy Package Manager) uninstall to uninstall the Nvidia driver.
Reboot.
Should be using the supplied Nouveau driver that comes with Puppy.

Go get the newer Nvidia driver run package and install it.

Sadly I installed the Nvidia driver from that same provided ".run" file, so I can't really "uninstall" from PPM

[bigpup]

OK try this:
Bootup.
Use Pfind.
Do a search for Nvidia.
Delete in Rox file manager all that Pfind finds.
Reboot.

That should make it boot not using the Nvidia driver.

Getnvidia program is a good way to install the driver.
Along with installing the driver. It also gives option to make a pet and or a sfs package of the driver.

this explains how to use Getnvidia program and link for program download.
http://www.murga-linux.com/puppy/viewtopic.php?t=110611

[frenchiveruti]

Yeah my issue with GetNvidia (as great as it is) is that disables Nouveau (that needs to be disabled in order to install Nvidia Driver) and then closes X, but when it closes X it happens the issue with the CLI that isn't visible, so I can't install Nvidia. And the Drivers and the entire puppy goes nuts like this:


I thank you a lot for the help, but I think is a major issue than the one I can grasp on.

I'll leave this here in case someone someday runs into the same problem.

[theru]

Let's see if I get this right:

- The problem happens with an older nvidia driver, not with the latest version or another driver.
- You want to update to the latest version but you can't because of this problem.

First thing to try is using the bootmanager to temporarily blacklist the nvidia driver and reboot. Puppy will most likely fall back to the standard vesa driver. If this makes the console usable again you can use xorgwizard to switch to a driver that at least allows you to use tools like getnvidia.

If blacklisting the nvidia driver does mess up the boot process you can undo the blacklist by going to /etc/rc.d/MODULESCONFIG and change the SKIPLIST entry.

It also doesn't happen on first boot. This is good news because I have experimented with a way to avoid using nouveau on first boot allowing you to install and test nvidia without needing to reboot.

- Boot without a savefile and with the option nouveau.modeset=0
- After bootup type the command rmmod nouveau

The first command still loads the nouveau module but doesn't actually use it allowing it to be unloaded with the rmmod command. The latter is important because otherwise the nvidia installer will complain and abort the installation.

Once you have done these 2 things you can use sfs load to load the devx and the kernel sources. Once that's done you should be able to run getnvidia to build the nvidia driver and, more importantly, the pet file and sfs module.

When you've done that and verified that the new nvidia driver works correctly you should be able to reboot with your savefile and replace the existing driver.

If you had no problems with an older driver it may help checking the archive: http://www.nvidia.com/drivers/beta

As for your icons problem you may be able to solve it by replacing /root/Choices/ROX-Filer/globicons with the one from your puppy sfs file.