Ubuntu.... what a POS

N

nekrosoft13

[H]ard|Gawd
Joined
Jan 4, 2005
Messages
1,581
Its been many years since I used linux, so I decided to give it a try.

Installed Ubuntu, and tried to install nvidia drivers from nvidia.com, so finally after struggling with terminal I got them installed.

After reboot I got greeted with /dev/sda2: Clean, bunch of numbers....

When I googled that, it says to press shift to enter recovery terminal... tried holding shift, tried rapidly pressing it, nothing works.

so after that I decided to just reinstall ubuntu and try again. pressing alt-ctrl-del works, PC reboots, but it won't boot from CD, I can't enter bios (del key does nothing), F12 (boot selection) doesn't do anything.

None of the keys in bios splash screen work....

all I get is /dev/sda2: Clean, bunch of numbers....


Ubuntu what POS....
 
Last edited:
once i'm on this screen /dev/sda2: Clean, bunch of numbers.... I press alt+ctrl+del and PC reboots

When I get the BIOS/UEFI plash screen nothing works, Del, F12, F9, ESC, nothing works.
 
nekrosoft13 said:
once i'm on this screen /dev/sda2: Clean, bunch of numbers.... I press alt+ctrl+del and PC reboots

When I get the BIOS/UEFI plash screen nothing works, Del, F12, F9, ESC, nothing works.
Click to expand...

That's something with your hardware then. Anything that has to do with the operating system happens after post. Have you tried f2?
 
nekrosoft13 said:
tried F2, its a gigabyte motherboard, it calls for DEL
Click to expand...

Change the keyboard USB to the front panel port and try again.

Or try a ps2 keyboard if you have one sitting around. I had a few gigabyte boards that had the same problem. Especially with a few USB early model mech keyboards. There and option in the bios to load USB on post that helps once you actually make it into the bios.
 
Component failure coinciding with a new OS install is just some bad luck.

Ubuntu is lame for an OS but I am pretty sure it wont kill your hardware. I have run various versions in the past on metal and in a VM with no ill affects.
 
Not being able to switch to your bios has nothing to do with any OS. Check your connections, check your MB bat ect. (as stupid as it sounds make sure your bios key f2/f8/delete which ever is working.... not saying it applies to you but I have seen a few people smash on their keyboard a bit in frustration before. ;) )

If you do manage to get ubuntu on.... do not go and download the driver from nvidia. Search Nvidia driver ubuntu ppa... that is the best method for installing nvidia non-free drivers in ubuntu. (I don't want to get confusing but it sounds like you managed to install the nvidia kernel driver but had not blacklisted the free kernel driver so you got a black screen, it could well be fixable by booting into runmode 3 which would give you a command line, and then blacklisting nouveou and rebooting, could also just be easier if your new to reinstall if you can get into your bios)

Nvidia provides a generic kernel mode driver installer... which means you have to run it from a terminal and in most distros blacklist the free kernel driver so they don't conflict. Very few distros suggest using the Nvidia installer.... most have user friendly ways to install them. (the only "major" distro that suggests using the nvidia installer is OpenSuse tumbleweed)

If you decide to try again with another distro... and want "ubuntu" I would suggest getting Mint which will allow you to install with the Nvidia non-free driver from the start. I believe Ubuntu-mate does the same. Other good options that allow you to install with the Nvidia driver as the default are Manjaro and Antergos (both based on Arch).
 
try what Alt said. there might be a usb port next to the ps2 too. or use the very top ones on the I/o panel. no os can bork your bios, something else is going on.
 
ChadD said:
Not being able to switch to your bios has nothing to do with any OS. Check your connections, check your MB bat ect. (as stupid as it sounds make sure your bios key f2/f8/delete which ever is working.... not saying it applies to you but I have seen a few people smash on their keyboard a bit in frustration before. ;) )

If you do manage to get ubuntu on.... do not go and download the driver from nvidia. Search Nvidia driver ubuntu ppa... that is the best method for installing nvidia non-free drivers in ubuntu. (I don't want to get confusing but it sounds like you managed to install the nvidia kernel driver but had not blacklisted the free kernel driver so you got a black screen, it could well be fixable by booting into runmode 3 which would give you a command line, and then blacklisting nouveou and rebooting, could also just be easier if your new to reinstall if you can get into your bios)

Nvidia provides a generic kernel mode driver installer... which means you have to run it from a terminal and in most distros blacklist the free kernel driver so they don't conflict. Very few distros suggest using the Nvidia installer.... most have user friendly ways to install them. (the only "major" distro that suggests using the nvidia installer is OpenSuse tumbleweed)

If you decide to try again with another distro... and want "ubuntu" I would suggest getting Mint which will allow you to install with the Nvidia non-free driver from the start. I believe Ubuntu-mate does the same. Other good options that allow you to install with the Nvidia driver as the default are Manjaro and Antergos (both based on Arch).
Click to expand...

once I get this POS running again, will try that, I need the nvidia drivers because I need CUDA support to get that application to run.

yeah at this rate, YEAR OF LINUX will never happen.
 
BulletDust said:
Secure boot that's locked to Windows is my guess...

I love how it's Linux that's instantly at fault before any logical form of troubleshooting has even started!
Click to expand...

I wouldn't put it past Secure Boot, either, and I am all for Secure Boot.
 
nekrosoft13 said:
once I get this POS running again, will try that, I need the nvidia drivers because I need CUDA support to get that application to run.

yeah at this rate, YEAR OF LINUX will never happen.
Click to expand...

I am among one of the few in the Linux forum that regularly complains about Linux. With that out of the way, I will say it has come leaps and bounds and works pretty much as well as Windows in every day applications.
 
nekrosoft13 said:
yeah at this rate, YEAR OF LINUX will never happen.
Click to expand...

Which is Microsoft's fault, secure boot is yet another method MS are using to lock PC's into Windows and 'Windows only'.

http://www.pcworld.com/article/2951...l-linux-on-a-pc-with-secure-boot-enabled.html

There is one catch here. While Microsoft does sign Linux boot loaders with a Microsoft key, these boot loaders are signed with a separate key from the one Microsoft uses to sign Windows. PC manufacturers aren’t required to include the Microsoft key for third-party UEFI applications as part of the Secure Boot specification, which means that these Linux distributions may not actually work on all Secure Boot PCs. But, in practice, most PC manufacturers do install this Microsoft key.
Click to expand...

In practice, as a tech, I've found that quite a number of manufacturers don't supply the Microsoft key for use with other operating systems.
 
If you don't want to use secure boot, just turn it off. I don't see the issue here.
 
AltTabbins said:
If you don't want to use secure boot, just turn it off. I don't see the issue here.
Click to expand...

Some UEFI's don't provide the option to turn it off, many UEFI's provide the option, but it doesn't turn off.

I deal with this shit on a daily basis.

Furthermore, the process to turn it off is becoming more and more hidden and convoluted.
 
BulletDust said:
Some UEFI's don't provide the option to turn it off, many UEFI's provide the option, but it doesn't turn off.

I deal with this shit on a daily basis.

Furthermore, the process to turn it off is becoming more and more hidden and convoluted.
Click to expand...

I haven't had any issue turning it off, although I also don't service any pc's other than my own. AND I assume it turns off when I choose that option lol
 
auntjemima said:
I haven't had any issue turning it off, although I also don't service any pc's other than my own. AND I assume it turns off when I choose that option lol
Click to expand...

OEM machines are the issue, it's rarely an issue with self built machines with the exception of those not using strictly 'enthusiast' motherboards.

I understand the way secure boot is sold to the people, I also understand it's real purpose. Furthermore, there's absolutely no denying that as a tech it makes my life a whole lot harder.

If we lived in a world where the interests of the people was the actual interest as opposed to the profit of certain companies, than secure boot would be a great idea - Sadly, faced with the harsh realities of the world around us, realities that are without a doubt getting worse, secure boot is a pain in the arse.
 
nekrosoft13 said:
this is the only reason why i'm trying to get this to run https://github.com/junyanz/interactive-deep-colorization
Click to expand...

Cool program and free too. If you dont find any solution here, you should really e-mail the developers since they recommend "Ubuntu" and OSX as the go to Os's. I guess ubunto cant be a pos, since it was developed and runs on it for the guys that made the program. Take it a lil easy and eventually it will work.

I never considered secureboot but looks like thats the first place you should look after using a port that your lkeyboard likes.

Thanks for the head up, guess I have another project on my list of things to do(try).
 
nekrosoft13 did you blacklisted the open-source graphic driver nouveau ? That often cause trouble is not kicked off the system. Also I have my system always booting in text mode as in case of nV driver updates I don't struggle to get X complete stopped. its a bit inconvenient but given that I don't often need to reboot its a good compromise (on a side note: I use that method on my CentOS; but sure it should work with Ubuntu too)
 
The OP probably made the mistake of thinking like a windows user. On Ubuntu Nvidia drivers are usually offered automatically for you after the first boot. You don't do it like windows where you have to download the drivers from Nvidia and install them. Ubuntu has a section called 'additional drivers' which lists drivers that are compatible with your current hardware. That's where you install the nvidia drivers, with one click.

If it's not offered automatically for you, find Software & Updates under System Settings and select the driver version form the Additional Drivers tab, then select the driver and click Apply Changes and restart.

If the driver version listed in the additional drivers is not new enough for you, you can set up a source for the latest drivers by copypasting a couple of lines to the terminal shell:

sudo add-apt-repository ppa:graphics-drivers/ppa
sudo apt update
 
Last edited:
B00nie said:
The OP probably made the mistake of thinking like a windows user. On Ubuntu Nvidia drivers are usually offered automatically for you after the first boot. You don't do it like windows where you have to download the drivers from Nvidia and install them. Ubuntu has a section called 'additional drivers' which lists drivers that are compatible with your current hardware. That's where you install the nvidia drivers, with one click.

If it's not offered automatically for you, find Software & Updates under System Settings and select the driver version form the Additional Drivers tab, then select the driver and click Apply Changes and restart.

If the driver version listed in the additional drivers is not new enough for you, you can set up a source for the latest drivers by copypasting a couple of lines to the terminal shell:

sudo add-apt-repository ppa:graphics-drivers/ppa
sudo apt update
Click to expand...

Totally agree. Although logically, this comment by the OP has me stuffed:

nekrosoft13 said:
once i'm on this screen /dev/sda2: Clean, bunch of numbers.... I press alt+ctrl+del and PC reboots

When I get the BIOS/UEFI plash screen nothing works, Del, F12, F9, ESC, nothing works.
Click to expand...

Usually, the first thing I'd say is "swap to USB 2.0 ports, don't use USB 3.0 ports", but the OP can [crtl], [alt] & [del]....So the keyboard is at least partially working?

Secure boot has to have forced the UEFI into lockdown?
 
B00nie said:
The OP probably made the mistake of thinking like a windows user. On Ubuntu Nvidia drivers are usually offered automatically for you after the first boot. You don't do it like windows where you have to download the drivers from Nvidia and install them. Ubuntu has a section called 'additional drivers' which lists drivers that are compatible with your current hardware. That's where you install the nvidia drivers, with one click.

If it's not offered automatically for you, find Software & Updates under System Settings and select the driver version form the Additional Drivers tab, then select the driver and click Apply Changes and restart.

If the driver version listed in the additional drivers is not new enough for you, you can set up a source for the latest drivers by copypasting a couple of lines to the terminal shell:

sudo add-apt-repository ppa:graphics-drivers/ppa
sudo apt update
Click to expand...

This isn't thinking like a Windows user. It's thinking like 99% of the world does when looking for drivers. I fail to see why going to the Nvidia site, selecting Linux as your OS and downloading the driver provided is so crazy to you. You act like the OP made a cardinal sin by going to the manufacturer and installing their driver.

I really hate the "well duh, you should have KNOWN to disable X driver", or "well, obviously it asks you after the first reboot lolol". These are uncommon, especially for a new user.

BulletDust said:
Totally agree. Although logically, this comment by the OP has me stuffed:



Usually, the first thing I'd say is "swap to USB 2.0 ports, don't use USB 3.0 ports", but the OP can [crtl], [alt] & [del]....So the keyboard is at least partially working?

Secure boot has to have forced the UEFI into lockdown?
Click to expand...

I think that once Ubuntu loads, even if it's to a command prompt, it has likely loaded him some drivers. I don't think you're far off suggesting either a usb2.0 or ps2 options.
 
auntjemima said:
This isn't thinking like a Windows user. It's thinking like 99% of the world does when looking for drivers. I fail to see why going to the Nvidia site, selecting Linux as your OS and downloading the driver provided is so crazy to you. You act like the OP made a cardinal sin by going to the manufacturer and installing their driver.

I really hate the "well duh, you should have KNOWN to disable X driver", or "well, obviously it asks you after the first reboot lolol". These are uncommon, especially for a new user.
Click to expand...

Considering that the OS has a built in feature offering the drivers to you (and should even request you to activate the drivers on first boot) yes.

The number 1 problem when switching OSes is to get stuck to the old way of thinking. Other OSes often work with a different logic alltogether and sometimes by doing something that's a no brainer in Windows (such as resetting ownership and permissions on the system disk) can make the entire OS malfunction if you do it on linux or OSX.
 
  • Like
Reactions: naib
like this
B00nie said:
Considering that the OS has a built in feature offering the drivers to you (and should even request you to activate the drivers on first boot) yes.

The number 1 problem when switching OSes is to get stuck to the old way of thinking. Other OSes often work with a different logic alltogether and sometimes by doing something that's a no brainer in Windows (such as resetting ownership and permissions on the system disk) can make the entire OS malfunction if you do it on linux or OSX.
Click to expand...

Whether it's offered or not, if the hardware manufacturer has a driver offered for download for your distro, it should be fine to download. AND should a person decide to do so, they shouldn't be berated as if they are some idiot who didn't use the built in feature.

Understand?
 
auntjemima said:
Whether it's offered or not, if the hardware manufacturer has a driver offered for download for your distro, it should be fine to download. AND should a person decide to do so, they shouldn't be berated as if they are some idiot who didn't use the built in feature.

Understand?
Click to expand...

No, since the manufacturers driver most likely won't even work if the user tries to install it using the instructions on the site.
 
B00nie said:
No, since the manufacturers driver most likely won't even work if the user tries to install it using the instructions on the site.
Click to expand...

So, wouldn't you say that's the idiocy of Nvidia, not the end user here?
 
auntjemima said:
So, wouldn't you say that's the idiocy of Nvidia, not the end user here?
Click to expand...

Nobody was accused of idiocy. I stated that different OSes have different approaches to things and the user must learn out of being limited to Windows functionality.

As what goes to Nvidia, Linus Torvalds sent these greetings to the Nvidia team:

23e874e75679a902b71cdc09355f76a00f087d0bb9e3e54c3d5c71a2b1bc4652.jpg
 
NVidia doesn't always play nice with the Linux community. The driver downloads on their site are more a way for distro developers to download a package they can integrate into their packages.

I wouldn't blame a user for thinking... go to site download driver. Cause sure I guess that is pretty common for anyone that has used windows for a long time.

Pretty much every mainstream distro around though does make it pretty clear how to install Nvidia drivers. Some like Ubuntu pop up an additional driver install first boot. Some do it during the install. The number of "major" new user focused distros that don't have a one click Nvidia non-free driver install these days is about zero, and they all do a pretty good job imo of making it clear how to install them before people have a fully working system.

I think what happened here is the OP was looking at a specific program more then the OS... and seemed to jump into installing an OS based on that alone. I'm not sure if this is a secure boot issue or a simple improper boot img with the Nouveou driver still built or what. I think the OP should have enough info now to figure that out though and move forward.
 
For me the problem in the past was often that CUDA was missing in distributions ... and I tried several sources back in those days. They all failed the one or other time at me (even more when I had to downgrade driver).

The nV version with a workflow working for never failed in last 3-5 years (or had other issues like cutting edge kernel etc).
 
ChristianVirtual said:
For me the problem in the past was often that CUDA was missing in distributions ... and I tried several sources back in those days. They all failed the one or other time at me (even more when I had to downgrade driver).

The nV version with a workflow working for never failed in last 3-5 years (or had other issues like cutting edge kernel etc).
Click to expand...

The *buntu PPA method of installing drivers and then keeping them updated is fantastic, I never have a problem installing Nvidia drivers and can do it faster than under any other OS.
 
BulletDust said:
The *buntu PPA method of installing drivers and then keeping them updated is fantastic, I never have a problem installing Nvidia drivers and can do it faster than under any other OS.
Click to expand...
I might give it another chance once Ubuntu changed their front end ... [but that gets offtopic]
 
This is the distro watch top 10 right now.....

1 Mint (Offers Install with NV non-free driver)
2 Debian (Additional driver one-click option)
3 Manjaro (Offers Install with NV non-free driver)
4 Ubuntu (Additional driver one-click option offered at first boot)
5 Antergos (Offers Install with NV non-free driver)
6 openSUSE (Additional driver one-click option for new user focused leap.... Tumbleweed not aimed at new users)
7 deepin (Additional driver one-click option)
8 Fedora (Additional driver one-click option)
9 Zorin (Additional driver one-click option)
10 elementary (Additional driver one-click option)

If you go through the top 100 even I only see a couple anymore that would require someone to use the Nvidia .sh script.
 
So basically the user didn't make use of the package manage to provide the drivers and then somehow blamed the OS for bios issues.

Buy a mac
 
He upset the User Emotion and Fury Identifier enough to lock it when he hit the computer in rage after the nvidia drivers locked it.
 
You must log in or register to reply here.
Back
Top