Ok, got the new lappy this afternoon! Getting the hardware registered through Asus for the warranty, and creating a backup...
Downloading the iso and hope to be up and running shortly!
Downloading the iso and hope to be up and running shortly!
This section allows you to view all posts made by this member. Note that you can only see posts made in areas you currently have access to.
#62
General Support / Wine on VSIDO?
March 19, 2013, 11:45:13 PM
OK, so I'll finally break down and ask...
I want Wine. I haven't been able to install Wine. Looking through the vast amount of sites "CLAIMING" to be How To sites is daunting/frustrating as ___(insert expletive here!). I have a 64-bit Linux system obviously. VSIDO to be exact. Do I need the 32-bit multiarch part of it installed? I don't plan on using any 32-bit stuff. How many frigging dependencies and in what order do you install them? What version of Wine for that matter? Synaptic/Aptitude is hopeless. Downloading is also vague when it comes to the .debs. Again, which ones and in which order? Did I already ask about the version? Oh yeah...
Anyone? Is this getting through? Anyone feel my pain? This is why I don't use Windows. Way to much ache involved. I would just like to play some games I have, or games I may want to download and try. Dying to try Portal. Oh yeah, you need Wine. Grrrrrrrrrrrrrrrrrrr
As to the "common-sense" to install Wine? Well I thought I had some 'sense' but it evidently isn't too 'common'! I really tried to do it and to no avail. Am I just too mentally deficient? (I'll answer that, yes I must be.) Will I always be a newb? How many years does this take? Should I just pour some lighter fluid on the new lappy and strike a match? I'm about ready...
PS, I'm thinking of changing my nick to Winey or Whiney! That way when I'm on the forums or irc, everyone can be like, shhhh, it's that idiot that's never been able to install Wine! Don't stare, it's impolite...
I want Wine. I haven't been able to install Wine. Looking through the vast amount of sites "CLAIMING" to be How To sites is daunting/frustrating as ___(insert expletive here!). I have a 64-bit Linux system obviously. VSIDO to be exact. Do I need the 32-bit multiarch part of it installed? I don't plan on using any 32-bit stuff. How many frigging dependencies and in what order do you install them? What version of Wine for that matter? Synaptic/Aptitude is hopeless. Downloading is also vague when it comes to the .debs. Again, which ones and in which order? Did I already ask about the version? Oh yeah...
Anyone? Is this getting through? Anyone feel my pain? This is why I don't use Windows. Way to much ache involved. I would just like to play some games I have, or games I may want to download and try. Dying to try Portal. Oh yeah, you need Wine. Grrrrrrrrrrrrrrrrrrr
As to the "common-sense" to install Wine? Well I thought I had some 'sense' but it evidently isn't too 'common'! I really tried to do it and to no avail. Am I just too mentally deficient? (I'll answer that, yes I must be.) Will I always be a newb? How many years does this take? Should I just pour some lighter fluid on the new lappy and strike a match? I'm about ready...
PS, I'm thinking of changing my nick to Winey or Whiney! That way when I'm on the forums or irc, everyone can be like, shhhh, it's that idiot that's never been able to install Wine! Don't stare, it's impolite...
#63
VSIDO Discussions / Partitioning Advice
February 22, 2013, 07:38:25 AM
When installing VSIDO (or any distro for that matter) todays hard-drives have an immense amount of space. I have been installing and using Linux since the days when an 800Mb hdd was huge!
Today I received a new laptop with the following configuration for disks. The primary is a 120Gb Samsung SSD drive, and the secondary drive is a 1Tb (5400 rpm) SATA hdd.
My plea for advice regards sizes of different partitions. The 120Gb SSD will be solely used for VSIDO, and for testing new iso's as they become available. On this drive I foresee a scheme like the following;
1st partition - / (root for main OS) of 25Gb.
2nd partition - / (root for test install 1) of 25Gb.
3rd partition - / (root for test install 2) of 25Gb.
4th partition - / (root for test install 3) of 25Gb.
That would basically take care of the SSD drive.
On the 1Tb hdd, I would put /home. However, I've also heard it's a good idea to have partitions for /tmp, /usr, and /var. For those 3 partitions which I'd place on the 1Tb drive, how big for each, and is it really beneficial to have them partitioned that way. I would then use the remainder of the drive for /home.
With 32Gb of Ram, is there a need for a /swap partition? With a Tb of space it wont be missed, (the space) but is it truly necessary?
These questions are mainly because I want to get as much life out of the SSD as possible. I'll also be utilizing the GPT partitioning scheme to take advantage of UEFI. Thanks everyone for the advice...
Today I received a new laptop with the following configuration for disks. The primary is a 120Gb Samsung SSD drive, and the secondary drive is a 1Tb (5400 rpm) SATA hdd.
My plea for advice regards sizes of different partitions. The 120Gb SSD will be solely used for VSIDO, and for testing new iso's as they become available. On this drive I foresee a scheme like the following;
1st partition - / (root for main OS) of 25Gb.
2nd partition - / (root for test install 1) of 25Gb.
3rd partition - / (root for test install 2) of 25Gb.
4th partition - / (root for test install 3) of 25Gb.
That would basically take care of the SSD drive.
On the 1Tb hdd, I would put /home. However, I've also heard it's a good idea to have partitions for /tmp, /usr, and /var. For those 3 partitions which I'd place on the 1Tb drive, how big for each, and is it really beneficial to have them partitioned that way. I would then use the remainder of the drive for /home.
With 32Gb of Ram, is there a need for a /swap partition? With a Tb of space it wont be missed, (the space) but is it truly necessary?
These questions are mainly because I want to get as much life out of the SSD as possible. I'll also be utilizing the GPT partitioning scheme to take advantage of UEFI. Thanks everyone for the advice...
#64
How To's / Network Setup In VSIDO
February 11, 2013, 11:43:32 PM
This was formerly the "How To - Setting up wireless with ceni" thread. Due to recent changes in how "SID" behaves, this has become a general network howto for VSIDO...
For those of you using wired connections, /etc/network/interfaces and /etc/resolv.conf in VSIDO will handle your Internet connection OOTB as long as your device is eth0 (which it probably no longer is for new users using the latest ISO's of VSIDO). Therefore:
FOR CENI -
If your just trying out VSIDO using a 'Live Session', here is a pretty simple way to get VSIDO to see your network. Open a terminal, and type in;
This gives you the name of your network devices. For example, what used to be 'eth0' may now be something like 'enp0s3'. While the terminal is still open, type in;
This gets you to a 'root' prompt. Type in;
Your network device should be listed. For wireless connections, the below directions for 'ceni' should still get you through. For 'wired' connections your network device should already be highlighted, and if not, press the "Tab" key to get to it and press "Enter". You should see the next screen which will be the "Network settings for enp0sXX". Most home networks are 'dhcp' so tab to the box and select 'dhcp' using your "Space" bar. "Tab" to the next box (Class) and select "Auto". "Tab" to the 'Accept' button and hit "Enter". If all went well, you should see some text fly by quickly then return you to the "Do you want to exit" box. "Tab" to the 'Yes' selection, press "Enter", and your done.
FOR WICD -
(Use the above method to discover your network device names, 'ifconfig -a')
For users using 'wicd' which comes by default with VSIDO, you should see an icon representing 'wicd' at the top right of your screen. Click this icon. A new window will open. This is the 'wicd' gui. At the top right of the 'wicd' window you'll see an arrow pointing down. Click on the arrow and select "Preferences". Another window will open. You'll immediately see the "Network Interfaces" at the top of the window. Replace the selections with the results you received using the 'ifconfig -a' command in your terminal. (from the directions at the top of this 'how to') (If your using a wireless connection, you can click on the "Adanced Settings" tab and towards the bottom you'll find a place to enter you access point password.) Once you've done this press or click on "OK". You'll be returned to the original window for the 'wicd' gui. Once again, click on the down arrow at the top right and click on "Refresh". Your 'network device should now be selected. Click on "Connect" beneath the correct device for your computer and presto, you should be good to go! Close the 'wicd' gui and your done.
These settings should remain after a reboot if your doing this after installing VSIDO. If your doing all this from a 'Live Session', you'll need to repeat these steps after every reboot...
Ceni for WiFi
Start Ceni in terminal with 'ceni'
Enter the su password for your system.
You should see the following screen. Be sure to select the correct device and press 'Enter';
Next (assuming your setting up your wireless) select scan;
Next, select the correct wifi network in the list;
Next, be sure the correct selections are made, and enter your "Preshared Key" (your wireless access point password);
Next, tab to the "Accept" button and hit enter;
At this point your almost done! You should see the following screen where you need to tab to the "Class" box, highlight the 'auto' selection, press the space-bar to select it, then tab to the "Accept" button and hit enter;
Last step, is to exit the ceni config tool;
Thats it! Enjoy your wireless network!
Profit!
For those of you using wired connections, /etc/network/interfaces and /etc/resolv.conf in VSIDO will handle your Internet connection OOTB as long as your device is eth0 (which it probably no longer is for new users using the latest ISO's of VSIDO). Therefore:
FOR CENI -
If your just trying out VSIDO using a 'Live Session', here is a pretty simple way to get VSIDO to see your network. Open a terminal, and type in;
Code Select
ifconfig -aThis gives you the name of your network devices. For example, what used to be 'eth0' may now be something like 'enp0s3'. While the terminal is still open, type in;
Code Select
sudo suThis gets you to a 'root' prompt. Type in;
Code Select
CeniYour network device should be listed. For wireless connections, the below directions for 'ceni' should still get you through. For 'wired' connections your network device should already be highlighted, and if not, press the "Tab" key to get to it and press "Enter". You should see the next screen which will be the "Network settings for enp0sXX". Most home networks are 'dhcp' so tab to the box and select 'dhcp' using your "Space" bar. "Tab" to the next box (Class) and select "Auto". "Tab" to the 'Accept' button and hit "Enter". If all went well, you should see some text fly by quickly then return you to the "Do you want to exit" box. "Tab" to the 'Yes' selection, press "Enter", and your done.
FOR WICD -
(Use the above method to discover your network device names, 'ifconfig -a')
For users using 'wicd' which comes by default with VSIDO, you should see an icon representing 'wicd' at the top right of your screen. Click this icon. A new window will open. This is the 'wicd' gui. At the top right of the 'wicd' window you'll see an arrow pointing down. Click on the arrow and select "Preferences". Another window will open. You'll immediately see the "Network Interfaces" at the top of the window. Replace the selections with the results you received using the 'ifconfig -a' command in your terminal. (from the directions at the top of this 'how to') (If your using a wireless connection, you can click on the "Adanced Settings" tab and towards the bottom you'll find a place to enter you access point password.) Once you've done this press or click on "OK". You'll be returned to the original window for the 'wicd' gui. Once again, click on the down arrow at the top right and click on "Refresh". Your 'network device should now be selected. Click on "Connect" beneath the correct device for your computer and presto, you should be good to go! Close the 'wicd' gui and your done.
These settings should remain after a reboot if your doing this after installing VSIDO. If your doing all this from a 'Live Session', you'll need to repeat these steps after every reboot...
Ceni for WiFi
Start Ceni in terminal with 'ceni'
Enter the su password for your system.
You should see the following screen. Be sure to select the correct device and press 'Enter';
Next (assuming your setting up your wireless) select scan;
Next, select the correct wifi network in the list;
Next, be sure the correct selections are made, and enter your "Preshared Key" (your wireless access point password);
Next, tab to the "Accept" button and hit enter;
At this point your almost done! You should see the following screen where you need to tab to the "Class" box, highlight the 'auto' selection, press the space-bar to select it, then tab to the "Accept" button and hit enter;
Last step, is to exit the ceni config tool;
Thats it! Enjoy your wireless network!
Profit!
#65
Feedback & Suggestions / Installation Feedback
February 06, 2013, 04:06:16 PM
Sorry for the tardiness of this, just haven't been able to 'geek' much the last few days.
I installed the newest iso this morning with no issues. None. However, you can read on if you want a little more info than that...
Used wget to grab the new VSIDO iso then installed this morning. Install went without a single issue. Logged into Xfce, perfection, logged out and then into OB, perfection again. Logged back out, jumped to tty1 and as 'sudo su' ran smxi for the first time. I always do it using 'sudo su' because I always have. smxi, no issues, everything did its thing, quit the script, rebooted, no issues. Logged into OB, did a 'apt-get update' and a 'dist-upgrade', no issues. Then installed the public key for Bumblebee, added the Bumblebee info to the /etc/apt/sources.list, ran update/dist-upgrade again, got Bumblebee installed/configured no issues. Rebooted, tested Bumblebee with the following successful results. (see pic of Bumblebee improvement of video running 'glxgears'.)
Noticed that the Kernel updated to
Next pic, 'inxi -F'
Runs perfect, no issues! (I know I said that at the beginning)
I installed the newest iso this morning with no issues. None. However, you can read on if you want a little more info than that...
Used wget to grab the new VSIDO iso then installed this morning. Install went without a single issue. Logged into Xfce, perfection, logged out and then into OB, perfection again. Logged back out, jumped to tty1 and as 'sudo su' ran smxi for the first time. I always do it using 'sudo su' because I always have. smxi, no issues, everything did its thing, quit the script, rebooted, no issues. Logged into OB, did a 'apt-get update' and a 'dist-upgrade', no issues. Then installed the public key for Bumblebee, added the Bumblebee info to the /etc/apt/sources.list, ran update/dist-upgrade again, got Bumblebee installed/configured no issues. Rebooted, tested Bumblebee with the following successful results. (see pic of Bumblebee improvement of video running 'glxgears'.)
Noticed that the Kernel updated to
Code Select
Linux vsido 3.7-trunk-amd64 #1 SMP Debian 3.7.3-1~experimental.1 x86_64 GNU/Linux All this took perhaps a half-hour total.Next pic, 'inxi -F'
Runs perfect, no issues! (I know I said that at the beginning)
#66
VSIDO News & Announcements / Initial release of VSIDO well received!
January 27, 2013, 11:00:58 AM
Just to update everyone, a collaborative decision was made to make the official release of VSIDO reported on jedsdesk.com on Jan. 17th 2013. Since that time, the article has been 'viewed' over 4,300 times! So we are definitely getting the word out there. This has also been linked to other tech related blog sites, which I can't keep a number on as to views.
Thanks to falldown for his efforts with the Facebook page! It is also getting views, so the news is definitely getting around! Compared to some Distro's that have been around for a good long time, we are moving along at a quite rapid pace. Keep telling your friends, co-workers, and fellow Linux lovers about VSIDO!
We've come a very long way, in a very short amount of time, which says a lot about VastOne's abilities to build a quality, stable Distro.
Awesome work everyone!!!
Thanks to falldown for his efforts with the Facebook page! It is also getting views, so the news is definitely getting around! Compared to some Distro's that have been around for a good long time, we are moving along at a quite rapid pace. Keep telling your friends, co-workers, and fellow Linux lovers about VSIDO!
We've come a very long way, in a very short amount of time, which says a lot about VastOne's abilities to build a quality, stable Distro.
Awesome work everyone!!!
#67
Feedback & Suggestions / Libreoffice Application Menu Not Visible
January 14, 2013, 11:25:24 PM
Logged into Xfce, my LO menus are also invisible. Using the link above, I followed the suggestions but no joy. I am hardly ever in Xfce anymore, so this isn't really an issue to me as it doesn't appear to be an issue in OB. For an Xfce user though, I can see where they might consider this an annoyance. I'm going to play around with the gtkrc file and see if I can come up with a fix. Don't hold your breath anyone! The file to fix (I think) is found at ~/.themes/SlicknesS/gtk-2.0/gtkrc
OK, heres the fix busprof's! Took me and VastOne over an hour to figure this one out. In the end it was pretty simple actually. First, you have to go to your /home/YOURUSERNAMEHERE/.themes/SlicknesS/gtk-2.0. Next find the file called gtkrc. Open it with your favorite text editor. Click on the find button and look for style "default". In that section look for the following and make the appropriate changes as indicated below;
Change to the following;
Your LO menus should all be visible now.
Using something like gcolor2, you can change a couple of those settings to fix that as well. I just did and changed them to a very nice VSIDO blue!
Quote from: VastOneOK... I have 2 fixes, one definite and one a maybe.
First edit this ~/.themes/SlicknesS/gtk-2.0/gtkrc file do this
In gtkrc file at line 1256 (style "menu" section) changeCode Selectbg[NORMAL] = "#d9d9d9" (Or whatever is there)Second one is here and it appears this has been an issue for 5 years.. http://www.rebelzero.com/fixes/openofficeorg-dark-theme-workaround-with-ubuntu-804/8
to
bg[NORMAL] = "#000000" (I have also used #000001)
I think it may be the second one needed to correct this
OK, heres the fix busprof's! Took me and VastOne over an hour to figure this one out. In the end it was pretty simple actually. First, you have to go to your /home/YOURUSERNAMEHERE/.themes/SlicknesS/gtk-2.0. Next find the file called gtkrc. Open it with your favorite text editor. Click on the find button and look for style "default". In that section look for the following and make the appropriate changes as indicated below;
Code Select
fg[NORMAL] = "#000000"
fg[ACTIVE] = "#000000"
fg[PRELIGHT] = "#000000"
fg[SELECTED] = "#000000"
fg[INSENSITIVE] = "#747474"Change to the following;
Code Select
fg[NORMAL] = "#FFFFFF"
fg[ACTIVE] = "#FFFFFF"
fg[PRELIGHT] = "#FFFFFF"
fg[SELECTED] = "#FFFFFF"
fg[INSENSITIVE] = "#747474"Your LO menus should all be visible now.
Quote from: VastOneBe aware that with this fix makes tabs,windows and menus in other areas of Xfce4 washed out. A good example is what it does to the Appearance menu system under Settings/Appearance
If I had to use LibreOffice in Xfce4, I would find another theme...
Using something like gcolor2, you can change a couple of those settings to fix that as well. I just did and changed them to a very nice VSIDO blue!
#68
Feedback & Suggestions / New Debian Kernel 3.7.1-1~experimental.2 x86_64
January 14, 2013, 10:56:33 PM
What can I say if it goes perfectly? I did a dd to a USB drive, rebooted, installed to sda8 (a testing partition). Install took maybe 6 and a half minutes!!! Then re-booted, opened up Wicd, added the wlan0 setting on the first Wicd screen, told it to "Display Notification status messages", clicked on the refresh, connected to my wireless, ran the post install script that automatically started when I logged in the first time. That took 15 min 27 seconds for a total install time of appx 22 minutes! VastOne, you've developed a real fine distro here!!! Below are two scrots of the install.
Again, no issues at all. What I'd call a perfect install experience. Anyone could do this!!! VSIDO Rocks...
Again, no issues at all. What I'd call a perfect install experience. Anyone could do this!!! VSIDO Rocks...
#69
General Support / Re: Updating problem - 02 Jan 2013
January 14, 2013, 10:07:26 PMQuote from: VastOneI have just done an update and saw this:Code Select#697147 - libqt4-dbus: Fails to upgrade from 4:4.8.2+dfsg-6
Merged with: 697159
Summary:
libqtdbus4(1 bug)
Are you sure you want to install/upgrade the above packages? [Y/n/?/...]
I answered Y(es)
and everything worked, the upgrade and no issues with libqt4-dbus
I did an UP and it seemed to go fine, though I did get this error at the end.
This was also in the terminal output;
Code Select
Preparing to replace libqt4-designer:amd64 4:4.8.2+dfsg-6 (using .../libqt4-designer_4%3a4.8.2+dfsg-7_amd64.deb) ...
Unpacking replacement libqt4-designer:amd64 ...
Selecting previously unselected package libqtdbus4:amd64.
Unpacking libqtdbus4:amd64 (from .../libqtdbus4_4%3a4.8.2+dfsg-7_amd64.deb) ...
dpkg: error processing /var/cache/apt/archives/libqtdbus4_4%3a4.8.2+dfsg-7_amd64.deb (--unpack):
trying to overwrite '/usr/lib/x86_64-linux-gnu/libQtDBus.so.4.8.2', which is also in package libqt4-dbus:amd64 4:4.8.2+dfsg-6
dpkg-deb: error: subprocess paste was killed by signal (Broken pipe)
Preparing to replace libqt4-script:amd64 4:4.8.2+dfsg-6 (using .../libqt4-script_4%3a4.8.2+dfsg-7_amd64.deb) ...
Code Select
Errors were encountered while processing:
/var/cache/apt/archives/libqtdbus4_4%3a4.8.2+dfsg-7_amd64.deb
Code Select
E: Sub-process /usr/bin/dpkg returned an error code (1)
Should I be alarmed?
Quote from: VastOnerunCode Selectsudo apt-get install -f
Problem solved
#70
VSIDO Discussions / Awesome Install
January 14, 2013, 08:49:36 PMOk, most awesome install ever! Less than 20 minutes flat! Hardest bit was typing in "ifup wlan0" to get wireless going. Real toughy! Tweaking now, and I have NOT installed Bumblebee. For those who would use this distro in an Optimus environment, a tip in the HowTo instructing them to use the Tab key at the initial boot to edit the boot process. (it evidently hates the Nouveau driver) I had to add 'acpi=noirq' before 'quiet' and 'no splash' after 'quiet' in the boot line in grub. Once installed, edited the grub file, update-grub to make it stick and presto! I gotta say this was a lot less painful than the last time I tried Sid on my own. Adding a couple of letters seems to have taken all the work out of it! (VSIDO) I also notice my transparency is a lot better now. And, Sector11, I'm using OpenBox! Shout it to the masses!
I was going to get this all done before VastOne went to bed but got tied up with life as usual. You'd think by waiting till everyone was in bed, I'd have the pleasure of some alone time with Sid. (VSIDO) VastOne, you definitely have a "present" headed your way! Remember to get me an addy to send it to!
VSIDO absolutely ROCKS! I still have some tweaking to do like I said, but this was a definite "No Complaints" install. Working on Conky and Tint2 now of course, but that is also rocking right along! Many Many Many Thanks VastOne!
Jed
(yeah I know it didn't happen till you all see the screenshot! Coming soon I promise!)
#71
Introductions / Hello from Detachment 7
January 14, 2013, 07:52:00 PM
My quick "Hello World"! Glad to be here. Got a 'tip' from "The Legend" this was the new distro! Downloading now and will have installed shortly. As with all of VastOne's work, I'm sure this will exceed my expectations!
Jed
Jed
#72
How To's / How To - Bumblebee on VSIDO
January 14, 2013, 07:49:07 PM
Had trouble with Optimus? Have a hybrid graphics card? This HowTo will get you up, and running, using the Debian Sid experimental Kernel, Linux *hostname* 3.6-trunk-amd64 #1 SMP Debian 3.6.9-1~experimental.1 x86_64 GNU/Linux
The whole point of this little HowTo is to inform people that Bumblebee is not working on the current Liquorix Kernels. As I'll probably mention numerous times, as of this writing the Liquorix Kernel is at least version 3.7.0-1.dmz.2-liquorix-amd64. I had no success getting it (Bumblebee) to work with Liquorix. Debian experimental Kernel to the rescue.
To be really specific about my laptop, I'm running a nice little distro called VSIDO which is based on Debian Sid. This HowTo should apply to anyone using Debian in an "Experimental" environment. To learn more about VSIDO, and when it will be released to the "General Public" you can go to the VSIDO Forums website.
The title will hopefully make your search from Google (or wherever you got here from) end a lot quicker! My search took a lot longer than yours, believe it. So here's how you do it; I WROTE THIS BECAUSE I WAS UNABLE TO MAKE BUMBLEBEE WORK WITH THE LATEST LIQUORIX KERNEL! (actually the last several!) Again, at the time of this writing, that is Kernel 3.7.0-1.dmz.2-liquorix-amd64
1) If you've reached this point, you already know your hardware is Optimus technology from nvidia. Telling you how to figure out your hardware without me looking over your shoulder is beyond the scope of this little HowTo. It also assumes, that you've got the latest Debian experimental Kernel installed and booting with no issues. If you need help in getting the latest Debian experimental Kernel installed, the "Search Engines" are your friend! Got you to this point right?
2) Add archive key to apt keyring. Run as root:
wget -O - http://suwako.nomanga.net/suwako.asc | apt-key add -
Once the key is taken care of, either add the following to /etc/apt/sources.list, or to a new file at /etc/apt/sources.list.d/
deb http://suwako.nomanga.net/debian sid main contrib
deb-src http://suwako.nomanga.net/debian sid main
3) Run sudo apt-get update
4) Run sudo apt-get install bbswitch-dkms bumblebee-nvidia (this will also install Bumblebee, as it will see it as a dependency)
5 Run sudo groupadd bumblebee (by default it should have been added with the install if all went well. If not this will do it for you.)
6) Run usermod -a -G bumblebee "yourusername" (without the quotes, this adds your user id to the bumblebee Group)
7) Re-boot at this point, log back in, and check to see if it worked by first running "glxspheres" from the terminal. Examine your frame-rate. Close "glxspheres". Run "optirun glxspheres". Examine your frame-rate.
Wow!!! That should do it!
(Disclaimer) This site will not be held responsible if you totally muck up your system following the instructions above, so do this at your own risk! This could result in your system being totally unable to boot, and possibly to never even turn on again. (It may even have smoke rolling out of it in the end) If it causes any swelling to the face tongue or neck, or excessive prespiring in the arm-pits, or serious pain in the brain, or constant and continuous constrictions in the bowel area, terrible anxiety, unpleasant odor or taste, excessive farting and or burping, please discontinue use immediately and consult with a bona-fide Linux guru; You can find Linus Torvalds email address with a simple search of the net.
The whole point of this little HowTo is to inform people that Bumblebee is not working on the current Liquorix Kernels. As I'll probably mention numerous times, as of this writing the Liquorix Kernel is at least version 3.7.0-1.dmz.2-liquorix-amd64. I had no success getting it (Bumblebee) to work with Liquorix. Debian experimental Kernel to the rescue.
To be really specific about my laptop, I'm running a nice little distro called VSIDO which is based on Debian Sid. This HowTo should apply to anyone using Debian in an "Experimental" environment. To learn more about VSIDO, and when it will be released to the "General Public" you can go to the VSIDO Forums website.
The title will hopefully make your search from Google (or wherever you got here from) end a lot quicker! My search took a lot longer than yours, believe it. So here's how you do it; I WROTE THIS BECAUSE I WAS UNABLE TO MAKE BUMBLEBEE WORK WITH THE LATEST LIQUORIX KERNEL! (actually the last several!) Again, at the time of this writing, that is Kernel 3.7.0-1.dmz.2-liquorix-amd64
1) If you've reached this point, you already know your hardware is Optimus technology from nvidia. Telling you how to figure out your hardware without me looking over your shoulder is beyond the scope of this little HowTo. It also assumes, that you've got the latest Debian experimental Kernel installed and booting with no issues. If you need help in getting the latest Debian experimental Kernel installed, the "Search Engines" are your friend! Got you to this point right?
2) Add archive key to apt keyring. Run as root:
wget -O - http://suwako.nomanga.net/suwako.asc | apt-key add -
Once the key is taken care of, either add the following to /etc/apt/sources.list, or to a new file at /etc/apt/sources.list.d/
deb http://suwako.nomanga.net/debian sid main contrib
deb-src http://suwako.nomanga.net/debian sid main
3) Run sudo apt-get update
4) Run sudo apt-get install bbswitch-dkms bumblebee-nvidia (this will also install Bumblebee, as it will see it as a dependency)
5 Run sudo groupadd bumblebee (by default it should have been added with the install if all went well. If not this will do it for you.)
6) Run usermod -a -G bumblebee "yourusername" (without the quotes, this adds your user id to the bumblebee Group)
7) Re-boot at this point, log back in, and check to see if it worked by first running "glxspheres" from the terminal. Examine your frame-rate. Close "glxspheres". Run "optirun glxspheres". Examine your frame-rate.
Wow!!! That should do it!
(Disclaimer) This site will not be held responsible if you totally muck up your system following the instructions above, so do this at your own risk! This could result in your system being totally unable to boot, and possibly to never even turn on again. (It may even have smoke rolling out of it in the end) If it causes any swelling to the face tongue or neck, or excessive prespiring in the arm-pits, or serious pain in the brain, or constant and continuous constrictions in the bowel area, terrible anxiety, unpleasant odor or taste, excessive farting and or burping, please discontinue use immediately and consult with a bona-fide Linux guru; You can find Linus Torvalds email address with a simple search of the net.