I have a Intel 64-bit machine running Linux mint 18.1 . On this machine, when I run the following command
sudo debootstrap --arch ia64 wheezy rootfs http://ftp.us.debian.org/debian
with the following errors :
W: cannot check release signature; keyring file not available /usr/share/keyrings/debian-archive-keyring.gpg
I: Failed to retrieve InRelease
Now, I have a second machine with exactly similar hardware configurations, running Ubuntu 16.04. On this machine, I get the same error but it still continues and downloads the rootfs correctly.
What could be the reason? I tried copying the keyrings from the working machine to the failing machine, still no luck. Both the devices are sitting in the same network with same network configurations
I tried what you did with the LinuxMint 18.1 LiveCD, and deboostrap fails not on the message you quote, but on the chroot step.
You should use --arch amd64 instead of --arch ia64.
Related
I am trying to run the XV6 OS on ubuntu image in a docker container (on windows).
I succeed in building the image, running it and accessing the docker container.
But inside the container cmd when I try to use the make qemu-nox command it crashes and gives the following error:
SeaBIOS (version 1.13.0-1ubuntu1)
iPXE (http://ipxe.org) 00:03.0 CA00 PCI2.10 PnP PMM+1FF8CA10+1FECCA10 CA00
Booting from Hard Disk...
Boot failed: not a bootable disk
No bootable device.
I am following the instructions here: https://github.com/anton-christensen/xv6-docker
I am not sure what causes this.
The other commands such as make, make clean qemu does work without error.
I have installed the Ubuntu in virtualbox for months.
After I upgrade the Linux kernal, I cannot boot Ubuntu with normal mode.
But it can success boot in recovery mode
I occurred some error:
floppy0: no floppy controllers found. => this will let me wait a few minutes, and it will go through.
intel_rapl: no valid rapl domains found in package 0 =>the boot process stuck at this error
I don't know whether it's a problem whit kernal 4.72 or not.
Linux kernal: 4.72 lowlatency amd64
virtualbox version: 5.14
physic cpu: x86_64
I solved the problem by myself.
Below is my method:
1.Enter recovery mode.
2.Install generic version kernel
3.Purge all of the lowlatency kernels
But I still don't know why virtualbox can't run with lowlatency version kernel.
And the error (or normal boot process),"intel_rapl: no vaild rapl domains found in package 0", is still showed when boot, but it dosen't let the boot process stop.
I have a CentOS Linux release 7.2.1511 (Core).
I want to build some kernel code for currently running kernel.
My uname -r says 3.10.0-327.10.1.el7.x86_64, but ls -l /usr/src/kernels/
shows only 3.10.0-327.13.1.el7.x86_64. Why do I have sources of not current kernel on my filesystem(vanilla fresh provisioned Digitalocean box)?
Why does yum install kernel-devel does not install headers for currently running kernel?
uname is a system call to the kernel to get information. It's telling you what's running on that machine. What's physically present on the hard drive can be anything that anyone has installed. Someone may have downloaded the wrong package or you may have multiple kernels installed etc. But, the one that's running is what uname is telling you.
When I run "sudo sh VBoxLinuxAdditions.run" just like on Ubuntu or CentOS, TinyCore throws errors and failed, and the /var/log/vboxadd-install.log shows that:
/tmp/vbox.0/Makefile.include.header:97: *** Error:
unable to find the sources of your current Linux kernel.
Specify KERN_DIR=<directory> and run Make again. Stop.
I have used tce tools installed some packets such as gcc, make, linux-kernel-sources-env.tcz, linux-3.16.2_api_headers.tcz, and then the VBoxLinuxAdditions.run can get the KERN_DIR, but no KERN_INC at this time.
If anybody has done this before could you please give me some points? I really don't know which packages should be installed in TinyCore to make VBoxAdditions work. My VBox and TinyCore is up to date. Thanks.
Found a repo for this issue, but have yet to verify:
https://github.com/MSumulong/vmware-tools-on-tiny-core-linux
Prior to that, I attempted to follow this tutorial, but it is incomplete:
https://www.gilesorr.com/blog/tcl641-guest-additions.html
Prior to that, attempted to build the kernel headers (/lib/modules/5.15.10-tinycore) with no luck.
Copying the Guest Additions to home folder and running sudo VBoxLinuxAdditions.run returns "Kernel headers not found for target kernel 5.15.10-tinycore. Please install them and execute /sbin/rcvboxadd setup"
Basically you have to install the package linux-headers-${kernel_version}
# apt-get install linux-headers-3.16.0-4-amd64
This solved my problem on Debian linux.
To check the version of your kernel, you should run the command:
# uname -a
# Linux debian 3.16.0-4-amd64 # SMP Debian
I need to install Ubuntu 64-bit on Windows 7 64-bit using Oracle VM Virtual Box.
I downloaded Ubuntu Desktop iso file, opened the settings of VM and selected the disk image of Ubuntu.
After this the following error message appears. How to solve this issue?
UPDATE: I tried both 34-bit and 64-bit Ubunto. Both fail.
Either your ISO is broken or you selected the wrong OS when creating the virtual machine. Try to redownload the file from the Ubuntu home page and mount it again.
You can follow the steps from here. Eventhough its for Ubuntu 14.04, the steps will not change.