Very strange startup of 05/26/21 current...
by FTIO from LinuxQuestions.org on (#5JD47)
I got the latest the other day and installed it since I had finally got my HDD back from a WD RMA (I'd bought a brand new, sealed, 1TB WD Black, and in one use it died. WD sent me a *NEW*, sealed *3TB* HDD for my troubles! Nice of them I thought!).
The install went well and is so easy I think even Windows users could do it, heh heh.
Anyway, today something made me look at which ffmpeg is installed with this current, and I *thought* I saw ffmpeg 3<something>. So I hie myself to Slackbuilds.com and start building all the 'extras' ffmpeg would sure like to see and use to build *it*. It's a loooong list and time consuming because of the dependencies here and there.
On *almost* all the 'extras' I was building and installing for ffmpeg to see, I got the latest version of the program I could find, *not* what was called for with the 14.2 build. This meant I had to constantly change the SlackBuild file and sometimes had to add or subtract things to get the latest to work in this current.
Of all the list for ffmpeg to see before it's built, these I couldn't get to build for the life of me:
Decklink
libflite
libgsm
rtmpdump
tesseract
transcode
None of those I find vital in any way, so I didn't worry about them not building or being installed.
Then, before I got to the point of building ffmpeg4, I was looking at the installed packages again for something and happened to see that ffmpeg4 *IS* installed, so I'd seen incorrectly the version. Oh well, at least all those things are in here for Motion to work better, heh.
Then, I decided I wanted to install CUDA, so I looked at what it needed for dependencies, and figured I would give the NVIDIA blob a chance instead of building the nvidia kernel and the nvidia driver builds.
I download the Nvidia 465.31 for x86_64, and before installing it, I get the nouveau-blacklist txz file and install it, then reboot the system to get to init 3 to install the nvidia blob.
Here's where it got weird/strange...the system booted to the two lines showing init and image then just hung there. I waited a few minutes and thought maybe it needed to try again, so I rebooted once again (ctrl-alt-del on the keyboard worked!). It booted fine up to those two small, short lines and again hung there, the rest of the screen remaining blank.
I figure I'll give it longer this time, so I wait about 30 minutes and the screen is still unchanged.
So, knowing that for some reason the keyboard is working, I entered root and then roots password (remember now, unable to see *anything* on the screen other than those two small lines still in the upper left corner), I then cd to where I remember downloading the nvidia file to, and installed it as I would normally. I would wait about 30 seconds and then hit the enter key on the keyboard. I did this three or four times I think. Then, hoping for the best, I *typed* Code:reboot...and, the system started to do so!
Again though, it stopped at those two short lines and just hangs there. So this time I login as the user (unable to see anything again) and type Code:startx in the hopes something might happen. It did! It booted to the users desktop!
I opened krusader as root and changed inittab to 4 instead of 3, restarted the system, and it's getting me to the login screen and everything is working normally.
So, does anyone have any idea why I couldn't see the regular init 3 screen like I was used to? Could it be the nouveau-blacklist file that I installed? It just was really strange and hopefully something I did and not a bug of some kind for Pat and the rest of the Slackware fixer-uppers to look into and 'fix'.
The install went well and is so easy I think even Windows users could do it, heh heh.
Anyway, today something made me look at which ffmpeg is installed with this current, and I *thought* I saw ffmpeg 3<something>. So I hie myself to Slackbuilds.com and start building all the 'extras' ffmpeg would sure like to see and use to build *it*. It's a loooong list and time consuming because of the dependencies here and there.
On *almost* all the 'extras' I was building and installing for ffmpeg to see, I got the latest version of the program I could find, *not* what was called for with the 14.2 build. This meant I had to constantly change the SlackBuild file and sometimes had to add or subtract things to get the latest to work in this current.
Of all the list for ffmpeg to see before it's built, these I couldn't get to build for the life of me:
Decklink
libflite
libgsm
rtmpdump
tesseract
transcode
None of those I find vital in any way, so I didn't worry about them not building or being installed.
Then, before I got to the point of building ffmpeg4, I was looking at the installed packages again for something and happened to see that ffmpeg4 *IS* installed, so I'd seen incorrectly the version. Oh well, at least all those things are in here for Motion to work better, heh.
Then, I decided I wanted to install CUDA, so I looked at what it needed for dependencies, and figured I would give the NVIDIA blob a chance instead of building the nvidia kernel and the nvidia driver builds.
I download the Nvidia 465.31 for x86_64, and before installing it, I get the nouveau-blacklist txz file and install it, then reboot the system to get to init 3 to install the nvidia blob.
Here's where it got weird/strange...the system booted to the two lines showing init and image then just hung there. I waited a few minutes and thought maybe it needed to try again, so I rebooted once again (ctrl-alt-del on the keyboard worked!). It booted fine up to those two small, short lines and again hung there, the rest of the screen remaining blank.
I figure I'll give it longer this time, so I wait about 30 minutes and the screen is still unchanged.
So, knowing that for some reason the keyboard is working, I entered root and then roots password (remember now, unable to see *anything* on the screen other than those two small lines still in the upper left corner), I then cd to where I remember downloading the nvidia file to, and installed it as I would normally. I would wait about 30 seconds and then hit the enter key on the keyboard. I did this three or four times I think. Then, hoping for the best, I *typed* Code:reboot...and, the system started to do so!
Again though, it stopped at those two short lines and just hangs there. So this time I login as the user (unable to see anything again) and type Code:startx in the hopes something might happen. It did! It booted to the users desktop!
I opened krusader as root and changed inittab to 4 instead of 3, restarted the system, and it's getting me to the login screen and everything is working normally.
So, does anyone have any idea why I couldn't see the regular init 3 screen like I was used to? Could it be the nouveau-blacklist file that I installed? It just was really strange and hopefully something I did and not a bug of some kind for Pat and the rest of the Slackware fixer-uppers to look into and 'fix'.