I want to boot the iso generated here from usb. I tried
sudo dd if=myos.iso of=/dev/sdb count=1
Doesn't work. What should I do?
(This image boots in virtualbox)
Related
I am using Emacs on a Raspberry Pi device, and I’m connecting to the device over SSH. Is it possible to enable 24-bit color with using Emacs over this connection?
I was able to get this working. I’m using Blink shell to connect to a Raspberry Pi device with Emacs 26.1 installed over SSH. This explicitly does NOT work for the release version of Mosh, as Mosh doesn’t 24-bit true color support yet. However, you can build Mosh from source to get this working over a Mosh connection, details are here.
The Emacs FAQ has the full instructions, but I found that I had to use:
$ export TERM=xterm-24bits
instead of
$ export TERM=xterm-24bit
to set the terminal to use 24-bit color.
With that done, I have 24-bit colors when starting Emacs as I normally would:
$ emacs
I am working on vxworks 5.5.1 and Tornado 2.2.1 porting a BSP for an Intel atom board.
I have set the options (memory, console (serial) and other options) and produced a bootrom and vxworks image.
my development host is a 32-bit XP and I created a boot floppy image using mkboot a: bootrom
Then I used HDD raw copy to copy the image to a USB.
When I boot the atom board with the USB, all I see is the display "1.6+++++++++++++++++++++++++++++++++++++++++++++++++++++++".
Since I compiled serial code into the bootrom (and there is a Rs-232 on the board), I was expecting to see some output on the Tornado COM1 console running in my environment.
It does not look like the bootrom is talking to serial port on the board at all.
Does anyone have any clues on where to look?
Thanks,
RK
Ever since I have upgraded my laptop (Click here for hardware specs.) my screen usually freezes. Mostly in chrome or Firefox browser. I am pretty sure this is a Nvidia driver problem but I can't seem to find the solution. I am running a Nvidia Quadro K2100M.
I am currently running Nvidia 361.42. I have tried using open source Xorg server without any luck.
The only solution I have found so far is forcefully turning off the computer by holding down the power button.
Things that I have tried:
I got keyboard input
I cannot switch to another terminal to restart lightdm
This problem came to me occasionally, making me really annoyed.
As illustrated in many blogs, this may be caused by graphic driver problem. For me, my desktop has a NVIDIA video card, you can run lspci | grep VGA to see what type of your video type, in my case, it returned:
02:00.0 VGA compatible controller: NVIDIA Corporation G98 [GeForce 8400 GS Rev. 2] (rev a1)
I followed the instruction on jiakai zhang's blog to reinstall proper drivers for the desktop, hope this will help you.
The key steps in [1] are to reinstall the ubuntu desktop and nvidia drivier by:
$ sudo su
$ apt-get update
$ apt-get install --reinstall ubuntu-desktop
$ apt-get install unity
$ apt-get remove --purge nvidia*
$ reboot
$ sudo apt-get install nvidia-current
$ sudo reboot
Updating the grub settings worked for me! Do the following:
1. Open the GRUB configuration
sudo vi /etc/default/grub
2. Change the value of GRUB_CMDLINE_LINUX_DEFAULT from "quiet splash" to
GRUB_CMDLINE_LINUX_DEFAULT="quiet splash intel_idle.max_cstate=1"
and save the file.
3. Update & Reboot
sudo update-grub
sudo reboot
More info:
This is a bug in the processor, known as the c-state bug. It causes total freezes when the CPU tries to enter an unsupported sleep state. It's a problem for many Bay Trail devices especially with newer (4.*) kernels. There is a simple workaround until it gets properly fixed upstream. You just need to pass a kernel boot parameter and the random freezing stops completely. The parameter may increase battery consumption slightly, but it will give you a usable system. You do this by editing the configuration file for GRUB as described above.
GRUB - boot loader package from the GNU Project, which provides a user the choice to boot one of multiple operating systems
installed on a computer or select a specific kernel configuration available on a particular operating system's partitions;
Intel Bay Trail - new Atom Processors from Intel. Atom is Intel's family of x86 and x86-64 processors that are optimized
for small computing devices, such as smartphones and mobile Internet devices;
C-States - used to optimize optimize or reduce power consumption in idle mode (i. e. when no code is executed) - (C0 to C8)
Reference: here.
I have since fixed this problem by re-installing Ubuntu 16.04 and not switching from the nouveau video driver. I also disable updates and everything been working good for about 2 months now.
Gaming is pretty good but I usually play steam games so doesn't push any kinda hard core graphics
Well, I had the same problem: My PC was freezing randomly. I tried Ubuntu 16, 17 and 18.04 and everything was the same. I tried several drivers and didn't get a solution. I tried several solutions that I found in the forums (including this) and got bad and harmful results.
My solution was: I stopped using the graphical nvidia card, removed it and now I'm using the integrated Intel HD graphics card (Intel® HD Graphics 530 card (Skylake GT2)) and all the problems were solved!
I fixed mine using a few commands from #Qoros solution above. i just ran apt-get update, apt-get install nvidia-current, and sudo reboot. cheers to #Qoros btw!
For me, none of the approaches described in rest of the answers worked.
I was opening multiple terminal tabs running some heavy processes and ubuntu used to freeze when I had 6-7 tabs. I tried monitoring the resources used while I was starting my processes in terminal tabs. You can do it by opening System Monitor app and going to Resources tab.
What I noticed is that when my RAM(8GB) and my swap space(1GB) were completely used up, ubuntu would freeze.
As a solution, I increased my swap space and made it 16GB. After this memory never gets used completely and ubuntu doesn't freeze.
https://askubuntu.com/questions/178712/how-to-increase-swap-space decsibes how to increase swap space.
I'm trying to install gentoo from usb. I'm using windows7 I downloaded the amd64 in: iso ( install-cd on this page: https://www.gentoo.org/main/en/where.xml then used Unetbooting to burn it on my usb. For some reason in the choices of distributions gentoo does not appear so I don't select any distribution. It worked before but now when I select the default option after reboot it says the iso is corrupt. I tried on another usb key, tried with lili usb creator, win32diskimage, universal-usb-installer, yumi, sardux64 and none of these work.
You can try just copy byte-to-byte liveDVD iso to you flash drive. Use dd command for this (under Win you can find some analogs).
The good article about Gentoo on USB: https://wiki.gentoo.org/wiki/LiveUSB/HOWTO
I was able to use UNetbootin.
First select the Diskimage radio button. Next push the three dots button to select the iso install-amd64-minimal-20140828.iso. Next select the usb drive and push the ok button.
Your machine should be using legacy bios to boot the usb. On my dell I push F12 on the bios screen for a boot menu and then select usb to start.
Once grub comes up select gentoo to use the usb drive.
The minimal install cd has worked great but any live disk can be used. The live disk is only used to connect to the internet, prepare the disks, copy the stage 3, and chroot into the disks. Most distributions have live disks that can do this.
I've got a board with an old VxWorks 6.5 boot loader loading an image over ftp. If I put a new image on ftp built for VxWroks 6.7 (or higher) should that work. My tests so far seem to indicate no. However, I don't yet trust that my new kernel's are good.
EDIT:
To troubleshoot I built a VxWorks 6.7 boot loader and made a new boot floppy. The first problem I have is that my VxWorks image is crashing somewhere in the board support package (BSP). I've not gotten to the part where I tweak the configuration to load it with a 6.5 boot loader. It looks like I'll be troubleshooting the BSP that came with the board for a while.
I know that a 6.5 Bootloader works just fine with a 6.7 VxWorks image.
However, you have to make sure that the settings for the vxWorks image match the settings for the bootloader. The main ones being:
RAM settings: RAM_HIGH/RAM_LOW, etc...
sysPhysMemTop(),
BOOTLINE address
Matching RAM configuration is important if you use the ED&R framework.