Linux - NewbieThis Linux forum is for members that are new to Linux.
Just starting out and have a question?
If it is not in the man pages or the how-to's this is the place!
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
I am trying to install Sabayon 16.07 KDE on my laptop and nothing seems to work.
I have a Sager Gaming Laptop with an Intel I7-6700HQ and a NVIDIA Geforce GTX970M with 16gb ram.
If it helps, Kernel is 4.6.3
The installed Bios menu is Aptio Setup Utility Version 2.17.1254
I have tried everything from enabling and disabling Secure Boot to enabling and disabling UEFI Boot with Boot option filter UEFI, Legacy and both.
Even tried Network Stack.
I notice it says Secure Boot is not enabled on the Sabayon boot menu even though I have it enabled on the BIOS itself.
I think that might be a factor considering it loads, then takes me to a black screen which doesn't boot.
Sometimes, it will say No Booting Medium is found and just won't boot.
-::-IF you have another os on that machine you will have to shrink it's partition for your Sabayon install.-::-
Sabayon uses proprietary drivers by default. Problem with that is that the kernel can set no mode.
So the first time you use the liveCD, you have to select "run in safe mode" from the grub menu. https://forum.level1techs.com/t/saba...l-issues/53725
Yeah, I still get that same message.
I am using a 64gb Sandisk USB Drive.
I plan on just overwriting the Bodhi portion of the drive considering I rarely used Bodhi.
I want to get rid of Windows 10, however I want to make sure I enjoy Sabayon entirely.
I've had it loaded on a pc before if that is what you mean.
If you mean something else, lemme know how to check that?
I still have to do the steps.
No, I mean something else.
Did you check the "md5sum <name of .iso>" in the terminal?
If the signature matches with the signature on the page you downloaded Sabayon than the .iso is safe.
If the signatures don't match, bash will complain.
I used UneBOOTIN and Universal USB when I was testing it a couple days prior, but this time, I have the Rufus install of Sabayon on my USB stick.
If I do any work, Would I have to reinstall the Sabayon ISO on my Bodhi partition on my laptop and do it that way?
You should be good with Rufus.
You shouldn't have to reinstall Sabayon unless you can't get it to boot. (might be a Nvidia issue if it won't boot)
Installing the Sabayon ISO on your Bodhi partition will wipe out Bodhi unless you resize it.
If it were my laptop I would use the partition manager that comes with Sabayon and delete the old Bodhi partition and use the free space to perform a fresh install of Sabayon. Than do a fresh install of Bodhi:-
You might want to include a picture of all of the partitions on your machine so we can look at all of the partitions.
For that you can use g-parted and take a screenshot and post it.
If the md5sum doesn't match, bash does not complain. The md5sum is just different than what it's supposed be.
Lately all of the md5's that I've checked have been different than what it was supposed to be.
However, in the past (years ago) bash did complain that the signatures didn't match.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.