Show Posts

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.


Topics - lwfitz

Pages: [1] 2 3
1
General Support / (SOLVED) Nitrogen and dual monitors
« on: May 27, 2017, 06:21:18 PM »
Please forgive me if this has been addressed but I couldnt find it anywhere

It appears, unless I have completely lost it, that I am unable to set a wallpaper for an individual monitor with nitrogen.



I have an nVidia 1060 card using the nVidia driver so maybe that is causing it?


2
VSIDO Installation Help / Nvidia Install Problems
« on: October 26, 2016, 03:09:25 AM »
Here is my hardware:

Motherboard

https://www.asus.com/us/Motherboards/M5A99FX_PRO_R20/

CPU (AMD 8370

http://www.newegg.com/Product/Product.aspx?Item=N82E16819113374

RAM

32gb DDR3 2133 (PC3 17000)

Video Card

https://www.asus.com/Graphics-Cards/TURBO-GTX1060-6G/

Storage

http://www.corsair.com/en-us/force-series-ls-60gb-sata-3-6gb-s-ssd

two 1tb Seagate 7200rpm storage drives

Power Supply

CORSAIR CX series CX750 750W


I have two issues.

1) This is a new MB and I cannot boot up with a live disk to install. Everything seems to load fine and then the screen goes black and my monitor goes to sleep. I had this with the old MB and I was able to use the onboard video to get it installed, install the Nvidia driver and then use my video card.
Unfortunately this board doesnt have onboard video. Without using a different card to install with does anyone have any ideas how to get installed?

2) Every time I install for the last few releases, grub wont boot my system. I boot up and before I get to the grub screen I get a flashing cursor and thats it. I end up having to use a dirrent distro, install on a seperate disk, use that distro to boot VSIDO and from there purge grub and reinstall it (sometimes more than once) and finally I can boot up.

To make things even weirder, I can boot up just fine when booting in uefi mode and this video card. Just not in bios mode

3
General Support / Kernel / Grub Boot issue <SOLVED>
« on: September 04, 2016, 04:18:27 AM »
So, for maybe the last 4-5 months (I think) I have had an issue where every time I reboot I have to wait 1:30 with a warning that a start job is running for ............ (enter uuid #). The uuid numbers are anything other than my root partition. Including home.

Thinking it might be a hard drive issue I tried a reinstall from the latest ISO and had the same issue. Then I ran a dist-upgrade and all hell broke loose. I got an error regarding initramfs-tools and linux-image-4.6.0-1-amd64.

Finally I got those packages repaired and installed properly. I ran apt-get update & apt-get dist-upgrade and everything came back clean. No errors.

When I rebooted I got to the normal grub screen, hit enter, and was greeted with a lovely flashing cursor. If I boot normally the flashing cursor lasts about 2 minutes, then it goes past and finally hangs without booting up all the way.
If I boot into recovery mode I get the flashing cursor but after two minutes it will go past and get to the emergency mode warning and I can hit ctrl/D and bypass. Once Im booted and logged in Im fine but it takes 2-5 minutes to boot and its annoying.

Any ideas?


SOLUTION

This worked for me




4
I've Got a Life / I Fish From Time To Time
« on: July 22, 2014, 05:35:12 AM »
Ok the title is a bit of a lie. Fishing is a bit of an addiction for me. In fact, if I could I would fish every day.

Heres just a few of my recent catches:















Just a couple months till it will slow down here and I can then be present on here again  :D

5
How To's / Triple boot VSIDO, OSX and Windows 7
« on: March 30, 2014, 02:50:10 AM »
Last week I went out and wasted my money on a new Macbook Pro 13". First thought I had was, how do I get VSIDO installed?

Now I know there very well may be a better way to go about getting this done but heres how I did it:

I started from a completely fresh install of OS X. First thing I did was delete the OS X recovery partition since from earlier attempts I found that it becomes useless once the new bootloader is installed.

Wait to create additional partitions until after Windows is installed (unless your not going to install windows. In which case you can skip all my rambling). Go into Launchpad and select bootcamp assistant. From there you can partition for Windows and download the drivers that will be needed once Windows is installed.
Once the bootcamp partitioning is done go ahead and boot to your Windows disk or usb and start the install. When given the choice you will choose custom install and then select the partition labeled "BOOTCAMP". You will have to format the partition and then you can run the install.

After your Windows install finishes go ahead and boot back into OS X and put the bootcamp drivers onto a a dvd or usb drive. Go back into launchpad and select other and then disk utility. Now you can create your partition for VSIDO. I suggest just shrinking the OS X install drive and waiting to do any formatting until your booted with the VSIDO live session.

At this point go ahead and download the rEFInd bootloader

http://sourceforge.net/projects/refind/files/?source=navbar

Download the cd version of the latest release (as of this post its 0.7.8 ) and once installed extract the .zip file and mount the ISO. Navigate in the mounted ISO  to "install.sh" and copy the file using command+c. Once copied go back into launchpad and click on other and then terminal. Paste the "install.sh" into the terminal (it will paste the file path) and hit enter. Enter your password and let rEFInd bootloader install.

Once your new bootloader is installed go ahead and boot to your VSIDO install cd or usb. Once booted up run the install. I attempted to install with swap but swap wasnt recognized (I believe because of gpt) so I canceled and restarted the install script without swap.
This is the point where you will format your VSIDO install partition. In my case I chose to use only one partition for root and home but I dont see any reason why have two partitions would be an issue. When prompted you will tell VSIDO to install grub to the "root partition".  And then run the install.

The install took about 4 min for me and once done I rebooted and was presented with the rEFInd boot menu with options for OS X, Windows and my VSIDO install.

If all went well you will not have a triple booting mac with OS X, Windows and VSIDO.

I should not the after I installed VSIDO my Windows 7 install didnt boot the first time. I had to go back into OS X disk utility and repair my Windows partiton (dont delete just repair). Everything then booted perfectly.


Additionally, fluxbox is obviously a pain with no right click so I went with KDE.
OS X only supports reading ntfs drives so if your wanting to write to your windows install from OS X you will have to install a ntfs-3g driver. I chose to go with paragon-ntfs as ive used it in the past and it works perfectly.

Edit:

I just updated my OS X install to 10.9.2 and no longer had an rEFInd boot menu and had to re-run the "install.sh" rEFInd install script and then all was good again.

For anyone worried about removing the OS X recovery partition, as long as you have an OS X install disk or usb you can use that for recovery if your machine decides to melt down. For machines (2010 and newer) with the latest firmware you can use the Apple Internet Recovery by holding command+Option+r at startup.

Ran dist-upgrade today and my keyboard backlight stopped working. The script found here

http://www.mabishu.com/blog/2010/06/24/macbook-pro-keyboard-backlight-keys-on-ubuntu-gnulinux/

works perfect


Update:

I spent the last couple hours trying to get things reinstalled after upgrading to a ssd and adding a 500gb 7200rpm drive where the dvd superdrive was. For some reason I got all kinds of errors including but not limited to....

Code: [Select]
Calling: Test-Built in
Error reading /Lib/Udev/Hwdb.bin no such file or directory
Load module index
Unload module index


Code: [Select]
Probing EDD (edd=off to disable) ....

The only way I was able to get past these errors was to add

Code: [Select]
edd=off nomodeset
to the kernel parameters. Do not even try to boot in failsafe mode as it will error and just frustrate you as it did me.

Also, I was having an issue with slow boot times. After enabling readahead all is good. That can be done by running

Code: [Select]
sudo systemctl enable systemd-readahead-collect systemd-readahead-replay;2D

6
Feedback & Suggestions / A quick thank you
« on: March 13, 2014, 12:26:52 AM »
So I spent the last few days testing out a number of other distros (to dual boot) and have found that I am completely spoiled by VSIDO. Thank you for all the hard work that you have put in VasOne.

Thats all  ;D

7
General Support / Intel Wimax
« on: January 08, 2014, 08:18:16 PM »
The wireless card that I have has Wimax capabilities but I I am unable to get it functioning properly.

I ran

Code: [Select]
sudo apt-get install firmware-intelwimax which then made the wimax portion of the card recognizable but still not functionable.

Code: [Select]
ifconfig
only showed

Code: [Select]
luke@vsido-asus:~$ ifconfig
eth0      Link encap:Ethernet  HWaddr 20:cf:30:66:f9:f8 
          UP BROADCAST MULTICAST  MTU:1500  Metric:1
          RX packets:0 errors:0 dropped:0 overruns:0 frame:0
          TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:1000
          RX bytes:0 (0.0 B)  TX bytes:0 (0.0 B)

lo        Link encap:Local Loopback 
          inet addr:127.0.0.1  Mask:255.0.0.0
          inet6 addr: ::1/128 Scope:Host
          UP LOOPBACK RUNNING  MTU:65536  Metric:1
          RX packets:29 errors:0 dropped:0 overruns:0 frame:0
          TX packets:29 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:0
          RX bytes:3278 (3.2 KiB)  TX bytes:3278 (3.2 KiB)

wlan0     Link encap:Ethernet  HWaddr 00:23:15:36:d8:68 
          inet addr:192.168.0.116  Bcast:192.168.0.255  Mask:255.255.255.0
          inet6 addr: fe80::223:15ff:fe36:d868/64 Scope:Link
          UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
          RX packets:22806 errors:0 dropped:0 overruns:0 frame:0
          TX packets:15119 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:1000
          RX bytes:29532032 (28.1 MiB)  TX bytes:1620948 (1.5 MiB)   

but I could see it recognized

iwconfig
Code: [Select]
wmx0      no wireless extensions.

eth0      no wireless extensions.

lo        no wireless extensions.

wlan0     IEEE 802.11abgn  ESSID:"Wils Sport And Tackle" 
          Mode:Managed  Frequency:2.462 GHz  Access Point: 58:6D:8F:55:3B:B4   
          Bit Rate=130 Mb/s   Tx-Power=15 dBm   
          Retry  long limit:7   RTS thr:off   Fragment thr:off
          Power Management:off
          Link Quality=70/70  Signal level=-40 dBm 
          Rx invalid nwid:0  Rx invalid crypt:0  Rx invalid frag:0
          Tx excessive retries:2809  Invalid misc:94   Missed beacon:0


So I ran

Code: [Select]
sudo ifconfig wmx0 up
iwconfig
Code: [Select]
wmx0      no wireless extensions.

eth0      no wireless extensions.

lo        no wireless extensions.

wlan0     IEEE 802.11abgn  ESSID:"Wils Sport And Tackle" 
          Mode:Managed  Frequency:2.462 GHz  Access Point: 58:6D:8F:55:3B:B4   
          Bit Rate=130 Mb/s   Tx-Power=15 dBm   
          Retry  long limit:7   RTS thr:off   Fragment thr:off
          Power Management:off
          Link Quality=70/70  Signal level=-40 dBm 
          Rx invalid nwid:0  Rx invalid crypt:0  Rx invalid frag:0
          Tx excessive retries:2809  Invalid misc:94   Missed beacon:0

Which gave me


ifconfig

Code: [Select]
eth0      Link encap:Ethernet  HWaddr 20:cf:30:66:f9:f8 
          UP BROADCAST MULTICAST  MTU:1500  Metric:1
          RX packets:0 errors:0 dropped:0 overruns:0 frame:0
          TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:1000
          RX bytes:0 (0.0 B)  TX bytes:0 (0.0 B)

lo        Link encap:Local Loopback 
          inet addr:127.0.0.1  Mask:255.0.0.0
          inet6 addr: ::1/128 Scope:Host
          UP LOOPBACK RUNNING  MTU:65536  Metric:1
          RX packets:29 errors:0 dropped:0 overruns:0 frame:0
          TX packets:29 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:0
          RX bytes:3278 (3.2 KiB)  TX bytes:3278 (3.2 KiB)

wlan0     Link encap:Ethernet  HWaddr 00:23:15:36:d8:68 
          inet addr:192.168.0.116  Bcast:192.168.0.255  Mask:255.255.255.0
          inet6 addr: fe80::223:15ff:fe36:d868/64 Scope:Link
          UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
          RX packets:23374 errors:0 dropped:0 overruns:0 frame:0
          TX packets:15571 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:1000
          RX bytes:30155199 (28.7 MiB)  TX bytes:1682334 (1.6 MiB)

wmx0      Link encap:Ethernet  HWaddr 64:d4:da:04:95:fc 
          UP NOARP  MTU:1400  Metric:1
          RX packets:0 errors:0 dropped:0 overruns:0 frame:0
          TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:20
          RX bytes:0 (0.0 B)  TX bytes:0 (0.0 B)


iwconfig

Code: [Select]
wmx0      no wireless extensions.

eth0      no wireless extensions.

lo        no wireless extensions.

wlan0     IEEE 802.11abgn  ESSID:"Wils Sport And Tackle" 
          Mode:Managed  Frequency:2.462 GHz  Access Point: 58:6D:8F:55:3B:B4   
          Bit Rate=130 Mb/s   Tx-Power=15 dBm   
          Retry  long limit:7   RTS thr:off   Fragment thr:off
          Power Management:off
          Link Quality=70/70  Signal level=-40 dBm 
          Rx invalid nwid:0  Rx invalid crypt:0  Rx invalid frag:0
          Tx excessive retries:2809  Invalid misc:94   Missed beacon:0

but still no wireless capabilities with wmx0.

My guess is that like in Windows when wifi is enabled then wimax is disabled. So my question is how would I disable wifi and enable wimax?


Code: [Select]
sudo rfkill list wimax
gives me

Code: [Select]
luke@vsido-asus:~$ sudo rfkill list wimax
1: asus-wimax: WiMAX
        Soft blocked: yes
        Hard blocked: no
3: i2400m-usb:1-1.1:1.0: WiMAX
        Soft blocked: yes
        Hard blocked: no

so as you can see wimax is blocked for some reason.

Any ideas?

8
I've Got a Life / Me have a life? Unpossible!
« on: December 07, 2013, 06:53:57 AM »
Well, I dont know the last time I posted a facebook status update and I most certainly have never tweeted what I had for breakfast but I thought Id share a little about myself with those of you who dont know me.

I dont have a wife or kids but I do have a very hard working (mostly self employed) family that I work and spend most of my time with.

My mother has owned a toy store for almost 25 years and about two years ago she went into business with my brother and opened a tackle shop. I myself own a contract I.T company that was just voted best computer services for the area that I live in.
My family is pretty special in that most of us work together and enjoy each other. Kinda rare now days I think.

So if the 7 day work week isnt enough I am also grateful to be able to play Santa Clause for our town. I get to be in our Christmas parade and go all around town during the month of December and make kids smile. Its a lot of work and sometimes stressful but totally worth it. My Uncle Jim got to do this for about 17 years so when I got asked to take his place when he passed I felt pretty honored.

The link below is for a local new station but the santa clause they show is me and the woman they interview is my mom.

http://abclocal.go.com/kabc/story?id=9344307

9
General Support / Install Issues
« on: November 05, 2013, 03:24:13 AM »
Once again I had issues with my install.

Since the release of VSIDO ll I have noticed issues with gpu lockup and kernel panics while trying to get the live disk booted.

Until today adding

Code: [Select]
nouveau.modeset=o
or
nvidia.modeset=0

to the boot commands would get me booted up and able to install but none of that worked today. In fact booting up in failsafe
didnt do it and the only way I could get booted up was to remove "quiet" from the boot commands and then it took like 5 min to boot up.

Once I got booted up I was able to install just fine and then rebooted. At reboot I found myself stairing at a blinking white cursor that then froze and I had to force shutdown.
Adding

Code: [Select]
nouveau.modeset=0

got me booted up this time and then I was able to install nVidia drivers via smxi.

Normally when installing nVidia drivers (if nouveau is installed) I would have to reboot and then re-run the installer to get the drivers to install. Since I have had this issue
I do not have to reboot and nouveau module gets removed the first time even though its supposed to be running.

So my guess is that this some compatibility between my GPU and nouveau and causing nouneau to not load properly.

Has anyone else seen this issue?

I have three machines that I run VSIDO on regularly. The other two are ATI and have no issues at all.

This machine is running a

Code: [Select]
01:00.0 VGA compatible controller: NVIDIA Corporation GK107 [GeForce GTX 650] (rev a1)

10
General Support / ia32-libs not installing with smxi <SOLVED>
« on: October 29, 2013, 06:46:33 PM »
Hey guys this is just so that all of us with this issue can track it.

Two nights ago I noticed that I wasnt able to install the nVidia drivers via smxi because ia32-libs could not be installed. So, just assuming I broke something, I downloaded the newest ISO and installed but had the same outcome.
Last night I went onto IRC and addressed this issue with Jedi, VastOne and a few others and have found that this seesm to be a SMXI issue.

Here is a link with more info if your interested

http://techpatterns.com/forums/about1129-250.html



11
General Support / Nvidia issue (I think)
« on: October 14, 2013, 07:37:53 AM »
If you look at the scrot below you will see what Im talking about. When I move a window I get an outline of that window that stays where it originally was. Sometimes this will happen more than others but as far as I can tell theres no particular time that it does it more than another


12
General Support / Volumeicon issue <SOLVED>
« on: October 09, 2013, 04:47:04 AM »
So I installed volumeicon on my new install just like I always have but this time when I use my volume up and down keys I get this



rather than the normal volume bar. My guess is I need to install something but I have no clue what that might be. Ive tried different icon themes but that didnt seem to make a difference.

13
Feedback & Suggestions / Fresh install W/ VSIDO ll
« on: October 05, 2013, 05:01:12 AM »
I finally just went and purchased an Xbox360 so I could play Tiger Woods PGA Tour........ That left me no more excuses for having a native Windows install.

The initial live disk boot errored just like last time but adding
Code: [Select]
nouveau.modeset=0
(thanks again Jedi) got me booted up properly so I could install. Install went flawlessly and the initial boot was perfect. I rebooted at least one more time and then all of a sudden I started getting kernel panics and/or the boot process would freeze with a nouveau/nvidia not accesible warning.
This time adding to the grub line didnt work so I booted into recovery and was able to run smxi from there and install the Liquorix kernel, reboot and install Nvidia. 

Once all that was done I was good and could enjoy my fresh VSIDO install  8) 8)

The welcome script worked just as it was supposed to (although I didnt use it) and my initial boot up memory was under 100mb (saw on my first boot).

The only things I would change would be to add Samba, gvfs-backends and libbluetooth3....... Oh and Thunar (I know I know).

All in all, great work as always VatOne!

14
Feedback & Suggestions / VSIDO ll Velociraptor
« on: September 17, 2013, 10:15:23 PM »
I have been plagued with bad download after bad download due to one.com/lwfitz incompatibility but thanks to VastOne (once again) I was able to download from a special super secret location and finally got to do some testing.

I DD'ed to my handy dandy usb but was teased with a blinking cursor and a black screen. So, I dug deep withing the depths of my desk (actually they were right next to me)  and I grabbed a dvd to burn the image to, and that did the trick............ So I thought!

I selected to boot to a live session and got a warning that blah blah blah nouveau wasnt found or couldnt be located and then I got this screen



Thats when JedsDesk stepped in and gave me some ideas that included but were not limited to adding

Code: [Select]
nouveau.modeset=0
to the initial bootup and that got me booted properly but at a horrible resolution.

Finally I was able to install and everything from there on went just as expected until I was installing Nvidia via smxi.
The normal Nvidia install will error and then a reboot and reinstall of Nvidia is necessary because of nouveau being installed. This time it didnt error. Why would that be? Is that the reason behind my boot issues? Maybe something from nouveau is missing? Just an idea.

Once I got fully updated with the right drivers I restored my backed up Xorg.conf and installed what I needed installed. Boot up with  Velociraptor/Liquorix is as fast as original VSIDO was with systemd. Memory usage  with Nvidia installed is right around 150mb and cpu idles at 0-1% with the latest Liquorix kernel.


From there I went to my laptop ( Asus G73JH) with ATI and installed without a single issue at all.

As always, VSIDO just gets better and better. Keep up the amazing work VastOne!

Edit:

Did I say I love it? I DO I DO!

15
Artwork & Screenshots / September 2013 Screenshots
« on: September 03, 2013, 06:35:19 AM »
Great scrots throughout August! Keep up the amazing work guys.....


Pages: [1] 2 3