After many unsuccessful tries with 16.10, I started trying 17.04 and succeeded but what I learned probably works for 16.10 as well, too.
First I did a clean install of version 17.04 and it loaded ok, same as 16.1 but it wouldn't boot either so I then went to: http://www.rodsbooks.com/refind/index.html
I downloaded the program - rEFInd onto a rebootable USB drive and booted. Then I selected the Shell terminal and followed the instructions that were offered at: http://gnu-linux.org/how-to-permanently-add-linux-entry-in-uefi-menu.html
The whole process is well explained. After I was successfully booted, I re-ran that eEFInd program and it made settings to the sda1 boot partition.
My new Acer with the new generation processor and no legacy firmware option is booting and running 17.04 quite well now.
RTFM! This is a simple system configuration setting, to instruct the system to restart on power-on. If you can't figure it out by yourself, you should not be doing what you are trying to do! Google will help...
I recently built a crypto currency miner and I'm using Linux Mint as my OS for the miner. I manually turn on the miner by navigating to ~/Desktop/claymore and running ./start_only_eth.bash and my miner starts mining. So i palced this line ./home/ethereum/Desktop/claymore/start_only_eth.bash in the /etc/init.d/rc.local file but I don't think it's running. When I type ps or ps -aux | grep /home neither ps command shows that my miner is running. What am I doing wrong with my auto startup stript?
Also, how can I setup my miner so that the computer will always be on? Meaning, if the power goes off and is restored it will turn itself back on as long as there is power without me having to maunally push the button? Thanks all.
OK, it's time to bring something onto the table. It's this.
Not all distros run on all machines.
I have this Intel NUC with some dual core Intel and a good 8 out 10 distros either didn't run from the SSD or failed in various ways. In the end I went with what ran and today might try it again as it's been about 8 months and distros advance. I'm not into fixing a distro today.
Another thing. Any "Signature PC" and I'm advising to never do this.
My latest attempt is I've installed a brand new harddrive and then booted with the 64 bit version of Ubuntu 16.1 and it booted ok with the 'try without installing' option. Then I've installed that 16.1 ok. Afterwards, I still could not boot. I then booted again with the installation USB to "try without installing" option, then loaded Boot-Repair and ran the recommended repair. Afterwards, I still cannot boot. This machine seems to be UEFI only. I have the firmware security 'off'. My Boot-Repair URL is http://past2.org/M4t2nLBF and I've sent that URL to Boot-Repair address and started a thread about this problem on the Ubuntu forum as well.
OK, the blinking cursor and can't get to the BIOS would have me unplugging ALL storage devices. No HDD, SSD, ODD, flippy, floppy and sticks. Now a CMOS reset and try for the BIOS. If the BIOS comes up, then I set date/time and what settings I wanted THEN I save, reboot and make sure I can get to the BIOS screen again.
With that out of the way I can connect up my USB bootable Linux to see that work. No other devices yet.
OK, we're up and time to add the SSD and try again.
Just tried a Debian iso image instead of an Xubuntu image and I had a similar problem. I got an erro while while it was creating the partitions. It said something about how that the partition had been created but that the Kernal didn't know about it and that I should reboot before making any changes. The it asked if I wanted to Cancel or Ignore, I chose ignore and the partition creation didn't give me any more errors but it progress bar stopped in one spot and would not move any further.
I just tried with another live usb and a whole new SSD and now when I boot up the computer a blue screen that says "Xubuntu" comes up and just when I think it's about to start the installation process the screen goes black and I see the following messages in white on the screen.
[ *** ] A start job is running for Ubuntu live CD installer ($COUNTER MIN SEC / no limit)
[ OK ] Started Network Manager Script Dispatcher Service.
I haven't check the chucksum but I have used several different images so I'M doubting that it's a corrupt iso file. Both images that I'v treid were from the Ubuntu website. Also, there is no dvd or cd drive.
Hello. I am a newcomer to Daniweb and need some advice. I've been using Ubuntu regularily on several PCs and note books installing without problems until now. I have just purchased an Acer Aspire ES 11 (ES1-132-CONU) that is using an Intel Celeron Quad Core 3450 processor launced Q3'16 possibly from the Kaby Lake 7th gen batch.
Installation USB /CDs for versions 14.04 and 16.04 won't boot. Version 16.1 will boot and I can go thru the 'try without installing' and without any problem. Then after adjusting the Windows 10 partition, etc. and installing Ubuntu 16.1, can only boot to Windows 10 with Windows Boot Loader. I can boot with the Ubuntu installation USB again, run 'try without installation' then download 'Boot-Repair' and repair/install Grub. Still no success.
This machine doesn't have the firmware Legacy option for an old BIOS setup. I've configured the machine's UEFI firmware to many combinations. I've even removed the original harddrive and installed a new harddrive then installed Ubuntu 16.1 but still won't boot. I even cloned the orginal harddrive with Windows 10 and using that clone, have done some serious modifications to Windows while attempting to load Ubuntu. The whole adventure seems like Windows 10 'only' is designed for that processor like it has it's UUID or product code now burned into Acer's firmware memory. I even unplugged the battery and removed the CMOS battery overnight thinking I would clear some Windows identity but without success.
Try using a live DVD instead of USB drive. That way, any faulty software on the live image can't break the media. Also, I am guessing that the ISO you built your live image from is faulty. Have you run a checksum on it and compared that to what is on the system you got it from? Also, did you get it from the Ubuntu web site, or somewhere else?
A while back I built a computer with an Asus motherboard, a SSD, and two milk creates for a cheap case, and I had Xubuntu installed on it. I have tried to install Xubuntu on it again several times today but it always fails to create the partitions. I keep getting an error -> 'Creation in partitoin # x (0,0,0) failed' or something like that. Then after this happens the computer will not even boot back into the live USB Ubuntu again or even the BIOS, all I get there after is a black screen with a blinking white cursor at the top left of the screen. If I want to boot the computer back into Xubuntu again I have to write a new usb image, that thumb drive on which the installation fails will not work again. Also I've tried two different Xubuntu images so I doubt that it's a currupt image file. Any ideas? Thanks.
To continue: these same issues are relevant to SSDs (solid-state discs).
It is my understanding that SSDs are built to much higher standards such that they can be refreshed several order of magnitudes more times before failing. Also, SSDs have extra space, over and above the allocated space, so that spare sections can be allocated to replace the failed sections.
Having said that, I do regular backups of ALL my hard driv es, SSD or otherwise.
To continue: these same issues are relevant to SSDs (solid-state discs). They are really fast, but they should ONLY be used for read-mostly operations, such as operating system boot, system libraries and configuration files, etc. For your working data, use a standard disc, or risk losing everything very unexpectedly. This also applies to log files which are very much write-only data.
What rproffitt said. In addition, FYI, pen/thumb drives (and sd cards) have a limited number of write cycles for each sector (512+ bytes). As that number is approached, the write time slows down, and then that sector is no longer accessible. There is more recent software that will attemp to wear-balance these behaviors so that the drive lasts longer, but unlike "spinning rust" (standard hard drives) when these solid state devices fail, they are done - period. This is why they are called "write once, read mostly" devices. They can be read pretty much forever, but only written to a limited number of times.
Hi. I wasn't sure which topic this falls under as it sort of concerns both OS and this is, I'm sure, a really noob (I want to start learning linux) question but can i use one pen drive between the 2 different OS's?
Earlier I was using my pen drive which is a SanDisk Cruzer Pop 4GB between my Windows 8.1 laptop and my recently installed Ubuntu 14.04 laptop and it was going well. On both laptops I safely removed the pen drive before unplugging it but now the pen drive can't be detected. I've tried it on both laptops and 2 other PCs and its undetected.
If i was suppose to format it somehow to make it compatible to both OS's, well I didn't know so I didn't do so. So basically I just want to know if its broken, is there a way to fix it if it is broken and maybe a kind soul could point me into the right direction so this doesn't happen to my other pen drives (formatting for compatibility perhaps).
Sorry if this seems like a really stupid question. Anyway, thanks in advance!
Hi All, I Need LAN Computers (X lite Client) to be able to VoIP Server (Asterisk). How can i configure the proxy server for this purpose.my diagram is in link.can you help to connect X lite client to VoIP server.
Following are the Configuration.
LAN - X Lite Client
need to connct to example.com:5060 to register client
Proxy Server - Centos 7
etho0 - 192.168.1.250 /connect to ADSL Router ,Masquerade zone disable
etho1 - 192.168.1.0/24 connect to LAN , DHCP Server enable
On item 7, recording streaming. I did have a fellow sorely confused about this. Settings for recording streaming are not the same as recording from the inputs so they burned on that. Eventually they settled on 2 apps. One for the hardware input and the other for streaming recording.
That is, it was too much for them to jot down how to configure for one or the other type recording.
Now it's working!
1) I switched from line input to microphone input.
2) In PulseAudio Volume Control I adjusted the volume of the Front Mic (which I'm using) so that the Silence meter is set as low as possible.
Then I got rid of that annoying noise in the speakers.. :-)
3) Then I started QJackCtrl-panel, started the Jack Server and choose the Audio tab.
4) There I found "system" under both "Readable Clients/Output ports" and "Writeable Clients/Input Ports". When I expand both of them I found the following:
Readable Clients/Output ports:
Writeable Clients/Input ports:
5) By connecting capture_1 with playback_1 and playback_2 I got the sound out of my speakers AND I was able to record the sound in Audacity. :-)
6) The settings in Audacity was straightforward:
JACK Audio Connection Kit
2 (Stereo Recording Channels)
7) But I lost the ability to record from streaming output like i.e. Spotify or YouTube. Any suggestions ?
I have a pretty modern desktop PC with both input and output lines so the hardware should be good enough.
Since I've managed to get the sound through from my cassette player/recorder to my speakers there might be a hope that I could fix the rest as well. I'll dive into both PulseAudio and JACK documentation to see what I can get out of it.
I've been using Audacity to record from Spotify, YouTube and other sources in the past so I know the program pretty well. But I have never succeeded in recording using line in as source.
Line in/line out seems like it would be line in/line out regardless of what the input is (cassette player/CD Player/Microphone/speakers/musical instrument/whatever). The cassette player is going to produce analog output. You should have a line/microphone in jack on your computer.
The software you use would largely be user preference. I have Adobe Audition for stuff like this, but it should all work, including Audacity or whatever free software is bundled with your computer or plain old Sound Recorder. Input and output should be largely independent. Depending on your computer, you may not have both an input jack AND an output jack. On my laptop, for example, it is one jack so I can't have a line in and play it to external speakers at the same time without adding some hardware, though I can play it to my built-in speakers.
Hardware's never been my limitation. Figuring out the software is the bottleneck for me. I generally just go down to the local Junior College and wander around looking as helpless as possible till some freshman music student takes pity on me and helps me out with the task. You'll have to restrain yourself from strangling them when they ask you "What's a cassette player?" though.