Showing posts with label after. Show all posts
Showing posts with label after. Show all posts
Monday, September 18, 2017
Uncapped ADSL after hours weekends for only R59 per month
Uncapped ADSL after hours weekends for only R59 per month
I discovered this deal from @lantic.net that offers �Bolt-on� uncapped ADSL (after hours) for only R59 per month (month 2 month).
That means after 18h00 each weekday you will get free bandwidth until 6am the next morning, plus on weekends from Friday 18h00 until Monday 06h00.
All of this for only R59 per month � there is a once-off setup fee of R50 for the bolt-on uncapped ADSL plus R50 once-off setup fee for the basic home ADSL package (called Gig4Gig) which includes 1GB free per month (and WiFi HotSpot access of 100MB/month and 25 free SMSs per month) (R15 per GB topup thereafter).
So, to recap: pay your setup fees of R50 + R50 = R100, and subscribe for the monthly after-hours bolt-on uncapped ADSL for R59 per month and there you have it: uncapped after hours for R59 per month.
The freebies:
25 free SMSs per month 
Login on the SMS portal here: http://sms.lantic.net/Log-In.aspx
and WiFi HotSpot access of 100Mb/Month.
Speed test local (SA) on 1MB line using @Lantic capped Gig4Gig account: 
Speed test (International) on 1MB line using @Lantic capped Gig4Gig account:
download file now
Tuesday, September 12, 2017
Ubuntu 14 04 not booting after error message tmp could not be mounted
Ubuntu 14 04 not booting after error message tmp could not be mounted
If you installed Ubuntu 14.04 using WUBI and after installation when it booted it showed an error:
Serious errors were found while checking the disk drive for /.
There were three options:
press [I] to ignore, press [S] to skip mounting and press [M] to mount manually.
After pressed I, it showed
/tmp could not be mounted and my Ubuntu isnt booting.Lot of people will get or got this kind of error after installing Ubuntu 14.04.I also got same error but after some modification i fixed it.
Please Follow This Step
- In Windows Boot Manager, select Ubuntu.
- Press any key and enter GNU Grub2 menu.
- You can press "e" to edit GRUB2 boot entry.
You need to change the GRUB2 boot entry from "ro" to "rw",
e.g.
linux /boot/vmlinuz-3.13.0-24-generic root=UUID=AAC884AC1F144321 loop=/ubuntu/disks/root.disk ro quiet splash $vt_handoff
to
linux /boot/vmlinuz-3.13.0-24-generic root=UUID=AAC884AC1F144321 loop=/ubuntu/disks/root.disk rw quiet splash $vt_handoff
Press F10, you can boot in Ubuntu 14.04.
and you can fix GRUB2 boot entry:
sudo vi /etc/grub.d/10_lupin
Change the line:
linux ${rel_dirname}/${basename} root=${LINUX_HOST_DEVICE} loop=${loop_file_relative} ro ${args}
to:
linux ${rel_dirname}/${basename} root=${LINUX_HOST_DEVICE} loop=${loop_file_relative} rw ${args}
Regenerate GRUB2 boot entry:(type in terminal)
sudo update-grub
After this all step surely you can use your new ubuntu So enjoy!!!!!!!!!!!!!!!!!!!!!!
download file now
Saturday, September 9, 2017
Ubuntu 12 04 Black Screen After Logout
Ubuntu 12 04 Black Screen After Logout
There were lots of suggestions and answers I found regarding this matter but the one that worked on my end was a very simple one. It was all about the screen display resolution. My laptop has a standard 1366 x 768 (16:9) resolution. For some reason this was changed to 1360 x 768.
The change is very minor but this, in fact, was the cause on why I get a black/blank screen when I logout. After restoring to the original resolution, everything is now back to normal and working as it should be.
Go To System Setting
download file now
Friday, September 8, 2017
Ubuntu Graphics Session Fix after botched Kernel Upgrade
Ubuntu Graphics Session Fix after botched Kernel Upgrade
Overview
This post is about restoring graphics to your Linux Desktop session if you install some kernel updates that dont go so well. Particularly, ones that fail with your graphics drivers.
Quick Steps
If you get error message (when trying to upgrade kernel packages or kernel drivers): "Skipping (driver build) at this time because kernel-source is missing." Try the following steps:
Note: `uname -r` is a commandline option which will auto-substitute your kernel version and architecture into the install command. If installing via a GUI, just use the info output from running the console command `uname -r`.
sudo apt-get install linux-source-`uname -r` linux-headers-`uname -r`If this does not automatically cause your nvidia drivers to compile, cause a manual install with:
sudo apt-get install nvidia-currentIf that still doesnt work, try uninstalling and reinstalling nvidia-current.
Background
Today I noticed there were some kernel updates in Ubuntu, but they had been kept back. So I decided to manually install them, since they did not appear to be causing any package conflicts. I do updates from command line with apt-get (because Im awesome that way *wink*). While installing the held-back packages, being kernel updates, it tried to accommodate my Nvidia graphics drivers.
Apparently, this failed. I noticed the error on the console, and immediately downgraded my kernel back to the previous versions. But alas, it did no good. I rebooted and was confronted with a text-only machine. Now, Im fine with this, since I spend a lot of time on console. (Screen, vim, ssh, and elinks are usually all I need for most rescue operations. Sometimes rtorrent, wget, and curl are handy too.)
After trying to get the packages to jive well together, I gave up trying to juggle the kernel packages and instead focused on the Nvidia drivers. I tried installing the nvidia-current package provided by the Ubuntu repositories. (I was running a later version from a PPA.). This failed, but triggered the same error.
"Skipping (driver build) at this time because kernel-source is missing." Now, Ive seen this error before. So I quickly installed the linux-source-`uname -r` package. This did not quite do the trick, and I have been around long enough to know that the source-packages often require the header packages as well. So I install linux-headers-`uname -r` package.
Once installed that, I didnt even have to do anything. The system automatically compiled the missing nvidia drivers and installed them for me. A quick reboot later, and now I am blogging about this simple solution.
download file now
Wednesday, September 6, 2017
Tyk Dashboard crashed after setting the portal domain
Tyk Dashboard crashed after setting the portal domain
So I set the portal domain to be as the same with the dashboard. Later, I was instructed that it is not permitted to have the portal domain same as the dashboard.
However, now I am left with the below error which does not simply disappear when I reconfigure Tyk.
panic: http: multiple registrations for dashboard.tyk-local.com:3000/
goroutine 1 [running]:
panic(0xa60f80, 0xc820370be0)
/usr/local/go/src/runtime/panic.go:464 +0x3e6
net/http.(*ServeMux).Handle(0xc820356d50, 0xc82036f7e0, 0x1d, 0x7f5a221595d8, 0xc82027af20)
/usr/local/go/src/net/http/server.go:1926 +0x297
main.GenerateRoutes()
/home/tyk/go/src/github.com/lonelycode/tyk-analytics/Main.go:733 +0x41b7
main.main()
/home/tyk/go/src/github.com/lonelycode/tyk-analytics/Main.go:750 +0x59
I basically had to drop the Mongo table, and then reconfigure Tyk to get everything back in place.
In Mongo shell:
> use tyk_analytics
switched to db tyk_analytics
> db.dropDatabase();
{ "dropped" : "tyk_analytics", "ok" : 1 }
download file now
Tuesday, August 29, 2017
Unable to see the LOGIN Screen after Startup
Unable to see the LOGIN Screen after Startup
If you are also facing the same problem , following is the solution.
1. Go to Advanced options for Ubuntu.
 |
| Fig. 1 |
2. Select the recovery mode.
 |
| Fig. 2 |
3.Select the root option from the recovery menu.
 |
| Fig. 3 |
4.After selecting the root option you will get the command line. Enter the following commands:
$ sudo dpkg-reconfigure lightdm
After running the above command you may get either the fig. 5 screen or fig. 4 screen followed by screen 5.
 |
| Fig. 4 |
 |
| Fig. 5 |
Now one more issue you can face when you select lightdm or any of the display manager.
If you get the following error run the following command else restart the system:
"Read-only file system error while selecting any of the display manager."
For that, you can run the following command :
$ mount -o remount /
and then again run the following command:
$ sudo dpkg-reconfigure lightdm
5.And then run the exit command. Restart the system. You will get the login screen.
6. Now one more issue may arise: It may be possible that you get the login screen but you may not be able to login into your system. It may be possible even after entering the correct username and password you get only the login screen. For that you need to follow the below steps:
Press Ctrl+Alt+F3 and login into the shell.Now runls -lah. If in the output the line-rw------- 1 root root 53 Nov 29 10:19 .Xauthoritythen you need to dochown username:username .Xauthorityand try logging in.Else, dols -ld /tmp. Check for the first 10 letters in the left: they should read exactly so:drwxrwxrwt.drwxrwxrwt 15 root root 4096 Nov 30 04:17 /tmpElse, you need to dosudo chmod a+wt /tmpand check again.If not both, Id recommend you either
dpkg-reconfigure lightdm- or uninstall, reinstall it.
Now press Alt+-> until you reach the login screen again, and restart.
In case if you need any assistance just put up the comment and I will look into it.
References:
http://askubuntu.com/questions/223501/ubuntu-gets-stuck-in-a-login-loop
http://askubuntu.com/questions/139491/how-to-i-change-from-gdm-to-lightdm
download file now
Subscribe to:
Comments (Atom)