Ubuntu installation error parsing PCC subspaces from PCCT - ubuntu-14.04

I get an error while trying to install ubuntu in my lenovo thinkpad laptop.
I have made a bootable pen drive of ubuntu iso image [UEFI] using rufus tool.Please help me, to get out from this error. I want to install ubuntu only in single boot.
Here is the image of error given below :

Input/output error is usually caused by damaged HW. These errors
Connect pen drive to another computer and check filesystem by fsck or gnome-disks or some similar utility.
If you found other errors in dmesg it's better to throw the pen drive into the thrash and buy a new one...

Related

How To Debug NoAvailableAdapter for Nannou with Debian running Gnome xOrg?

I tried setting up Nannou following the instructions here.
I am running Debian Buster on a MacBook with an NVIDIA graphics card (GK107M [GeForce GT 750M Mac Edition]).
I tried running the example and get the error
thread 'main' panicked at 'could not build default app window: NoAvailableAdapter'
It seems this is an error when Nannou tries to open a window -- something about its communication with the window manager (Gnome on xOrg), or something about vulcan-tools.
Any ideas for how to debug this?
The issue is that I was using the open-source Nouveau driver for my graphics card (the default on Debian) which does not currently support Vulkan, which is required for Nannou.
By installing the proprietary nvidia graphics driver, the problem was resolved.
I was able to install the nvidia driver by running
apt install nvidia-driver,
and then rebooting my computer,
as described in this tutorial https://linuxconfig.org/how-to-install-nvidia-driver-on-debian-10-buster-linux
Now nannou works :)

Cannot boot computer after installing Ubuntu

I just got a refurbished computer and after installing Ubuntu, computer refuses to boot and instead displays screen with message:
"Insert system disk in drive.
Press any key when ready...."
I tried reinstalling Linux twice (from a usb and from a cd) and the problem persists.
I have a Toshiba Portege R930 which originally had a Windows 7 and I installed Ubuntu 16.04.2
Any suggestions would be appreciated,
Thankyou xx
1) Try changing the boot order so the hard disk is first.
2) Make sure the BIOS supports GRUB signatures.
3) Make sure the ISO is correct for your machine (is it 32-bit like your machine?, etc.)

Black Console after automated Debian UEFI install

I try to build a reproducible automated build environment based on Debian 8.1 Jessie.
I created a boot iso image based on a netinstall image and put a preseed.cfg file in int for automatic installation.
I managed to get it bootable with BIOS and UEFI and can install a KDE Developer Debian in VMWare Workstation 11 fully automated.
I have also a server iso image to install a debian Server with Jenkins, both with BIOS and UEFI Boot.
But after the installation, the Version with UEFI Boot shows a black Screen when started.
I can blindly log in, start the gui with "startx" and see my installed xfce desktop. When i quit xfce the console is usable and visible.
I tried suggested bootparameters "nomodeset" and "vga=Linux" that i found with google to no avail.
I also tried to debug the boot prozess, to find out which command leads to a blank screen, but i did not find the right place to delay the processes at bootup so i can see when the messages dissapear (quiet bootparameter was removed :-)
I also tried to reset the console to no avail.
Can anybode point me to a tool that does the same "switching" like X so the console is useable?
Can anybody give me some hints how to debug the bootprocess to find out which command is causing this behaviour?
I dont want to install X because this should be a headless server system later.
I managed to get my system to boot using the kernel command line modprobe.blacklist=vmwgfx, or placing 'blacklist vmwgfx' in /etc/modprobe.d/*.conf
I assume it is some bug in the vmwgfx module, however as this workaround works for me I have no immediate need to investigate further.

FDT and ATAGS support not compiled in - hanging ### ERROR ### Please RESET the board ###

I'm following the tutorial to install linux on SoCkit by Terasic.
This is my first time building a linux, so I am still learning. I was able to complete all the steps shown in the tutorial but when I try to boot it gives me error saying:
Did not find a cmdline Flattened Device TreeCould not find a valid device tree
Now, I know the .dtb file is on the SD card and I can load it using the fatload command of u-boot. After I load the .dtb file and run bootm command I get the error saying:
FDT and ATAGS support not compiled in - hanging ### ERROR ### Please RESET the board ###
I don't know where/how to enable this support. Could someone please help me with this.
It looks like this particular SD card I am using wasn't getting formatted (partitions file system) properly on a virtual machine. I was running Ubuntu 14 on VirtualBox. I then formatted on a laptop running ubuntu and re-wrote the SD card. It booted up just fine!

Installing software while running bootable usb

I am new to Linux so I have created a bootable usb drive with Linux Mint on it so that I can play around with it for a while before deciding if I want to install Linux on my harddrive.
I have created the pendrive with persistence so that I should have the ability to install software on it. However I can't seem to install anything.
I have downloaded the graphical linux postgresql installation file, given it execution permissions and then get the following error when I try to run it:
There has been an error
Error changing ownership of
/tmp/postgresql_installer_120403f9ba/lib/postgresql to root
I also downloaded the 7zip tar file, extracted it and tried to run the install.sh file. But nothing happens. Im just trying to see if I can get anything to install.
Im guessing either there's something with permissions that im not doing correctly, or it has something to do with the fact that im running linux from a usb drive.
As mentioned, im brand new to linux.
I have figured out what was required. I was trying to double click the install file from the GUI which wasn't working. I had to run it using sudo from the command line. Looks good now.

Resources