I just did a new install of Ubuntu 10.04 (64 bit) on a system with multiple older versions of Ubuntu already installed. There was a dpkg error during the install with no useful information provided, otherwise the install completed normally. When I rebooted, the old grub2 ran and presented my old boot menu. When I mounted the 10.04 partition to see what was there, I found that /boot/grub/ was empty and /boot/initrd.img was missing. The other boot files were present.
I need to install Ubuntu on approximately 50-60 netbooks. None of them have CD drives, and I don't want to have to install them individually, walking around with a USB stick. I figured the fastest way to install on so many machines is to use a combination of apt-cacher (http://www.debuntu.org/how-to-set-up...ith-apt-cacher) and netbooting. I have successfully booted one machine to test, but as soon as the kernel comes up, support for the network interface is gone. Specifically, the "atl1c" module is not included on the netboot initrd image. Also, I would like to try to use preseeding, and I need to get that onto the initrd as well.
So, to summarize my question: How can I create a custom install kernel and initrd? I have a feeling it's related to the "debian-installer" category in the package repository, but I have not found any good documentation about doing this.
If you can access Suse Studio here is thlink to the buildLFS Host - SUSE GalleryGoogle hasn't been friendly and neither has a search on these forums, I don't know which man to read so a finger in the right dirrection (preferably not the middle) would be nice as far as that goesRight now the yast live installer trips up at %84 while saving the boot loader configuration and displays a popup that says �An error occurred during initrd creation. /sbin/mkinitrd: illegal optionI then press enter to acknowledge the message and the installation continues without a hitch.
When I go to boot up (no other os installed) grub says it cant find the file initrd-2.6.34.7-0.5-defaultIf you boot the live cd again you can mount the boot partition and you�ll find a broken symlink called initrd that islooking for the missing file above.Like I said above, if it an obvious fix, all I need is some direction, I don't mind reading. (been doing that all day)If you need more specifics Id be happy to supply, I'm just not sure whats relevant and don't want to bloat the post.
When I compile a custom kernel with this command: make-kpkg --initrd kernel_image kernel_headers and then install the .deb, there's no initrd in /boot and I have to create it manually. I've thought that the --initrd option should take care about this, but somehow it doesn't.
It behaves like this for about two years at least (since I've compiled my first kernel). Of course, it's no big deal to create it manually, I was just wondering whether do I do anything wrong or whether should I fill a bug report..
Just spent three whole days barking up the wrong tree, solving Fedora 11 and Fedora 12 boot failures because the correct hypothesis was illogical: installation did not update/modify the initrd.
The first couple of times I installed Fedora 11 on the HighPoint Technologies RocketRaid 2640x4, the installation inserted my "custom" driver module (rr26xx) into the initrd, permanently, so that the system booted off the controller card for which the custom driver was inserted. (I yelled about this success in this thread: [url]
My most recent installs of BOTH F11 and F12 on the RocketRaid failed to properly set up the boot. It turns out that the "rr2640" module I "slipstreamed" into the installation process was *NOT* permanently added to the initrd by anaconda. (F12 gave me "no root device found boot has failed, sleeping forever", on boot; F11 hung also, without such error, I presume, during the init script execution). Because of limited resources and time, I only know for sure the module was missing from the F11 initrd, and am ASSUMING the same was the case with F12.
The only difference between the successful installs and the ones with failed boot is that the successful installs were made on a single-drive (JBOD) mode on the controller; whereas, the failed ones were placed on RAID 5. But, AFAIK, the created logical device for the card is "/dev/sda", in both cases, and the kernel can not distinguish between the two cases (or can it?). Thus, the inconsistency cost me a lot of time, and is still inexplicable to me.
Question: What is the best way to deal with custom drivers, today? There are custom spins, and many tools, like isomaster. Stupid question: Is there a way to modify the initrd inside an installer ISO -- be it for CD/DVD/USBboot drive -- beefing the init RAM disk with whatever modules you'd like, for the boot process (using, say, isomaster)?
And what makes anaconda understand that a module must be added to the initrd ? How can one force anaconda to do so?
How does moving to dracut as the initrd tool affect any/all of the above?
What command do I need to use to view the /casper/initrd.lz file on a live USB? Here's what I know about initrd.img in /boot on standard installations:
Code: zcat /boot/initrd.img-2.6.xx.xx-generic | cpio -iv Now, what's the equivalent for initrd.lz files?
I have an encrypted root and encrypted boot drive... To avoid entering a passphrase multiple times I'd like to add a keyfile for my root drive to my initrd... I've done this in Arch and it was relatively simple but I've hit a road block in debian finding the analog processes...
Code: Select all#Part 1) Generate the keyfile, give it suitable permissions and add it as a LUKS key:
I have compiled the linux kernel. My bzImage is 1,14 mb big
Anyway. It's only 2 programs i need and it's Python and Busybox. I have compiled python and busybox and put them together in a folder. Busybox is 146 kb and pyton is 4,4 mb.
But how do i make an initrd file of them? Or should a make an initrd file of them?
I get this error when a runt with a compiled busybox to gz format as initrd, and without initrd.
Quote:
VFS: Cannot open root device "sda1" or unknow-block(0,0) Please append a correct "root=" boot option; here are the available partions: Kernel panic - not syncing: VFS: Unable to mount root fs on unknown-block(0,0)Pid: 1, comm: swapper Not tainted 2.6.38.3 #1
I am attempting to PXE boot Redhat 5.4 and load the OS into RAM. Here is how far I have gotten so far:
I have successfully configured my DHCP, TFTP, and PXE servers. The PC that is booting up Redhat 5.4 is able to get a DHCP IP address from the server, grab the kernel and initrd from the TFTP server, and boot up from there. I have this setup working if I store the root file system on a NFS share on the server and use the kernel's NFSROOT parameter. Long story short, I now need to get this same setup working without using NFS if possible. I have spent several hours google searching how to create a RAM disk (initrd) that also contains the root file system. I must be searching the wrong keywords. Anyway, based on what I have read so far, I need to do the following:
1. I need to pass different kernel parameters. It needs to look something like:
2. It seems like newer versions of initrd are created using the cpio tool. So would this simply be a matter of booting to my hard drive that has Redhat 5.4 loaded on it and running:
To create the RAM disk with a root file system attached to it? I have a feeling it has to be more complicated than that but I just cannot find any sites that specifically explain what would be involved with creating an initrd file that can also be used as the root file system.
3. Would I need to modify the init script (many sites call it "linuxrc") at all in order to accomplish what I want to do? For example, I found this site:[url]
My understanding of this page is that you have to create a linuxrc script that basically does the work of decompressing the file system into /dev/ram0 and mounting it to /root. Is something like this actually needed?
4. The kernel must have certain parameters set such as enabling RAM disk support.
I have most of this setup working. I just need to figure out how to basically store the contents of the OS on the TFTP server and then tell the kernel to load that OS into memory. Based on what I have read, this should be possible (otherwise, how do Live CD's work?).
I have a mount command that I want executed every single time the computer reboots so that the folder is always mounted when I need it. What file would I have to edit in order to accomplish this?
this i am sure is a very newbie question i have been using linux for a while now Fedora 14 and am still stuck on one issue even though i have trolled the internet for hours. i want to install the 7300 gs driver however when i go to terminal and type: sh NVIDIA-Linux-x86-260.19.12.run i get the error you must be root. so simple i type su --login add my password then when typing the run command i get the error that the file is not located in root and can not run. so my question is how do i do it. if i cd to home i loose root permissions if i try sudo sh file.run i get the error it is not one of the sudoes.
When ever I extract a file from a .tar or whatever, it isn't detected. I notice this mainly when i'm using xampp. I copy zip up all my files on one computer, load ubuntu on another, extract the files to the web folder (htdocs) and then I get nothing. However, when I manually create the files directly on my computer as opposed to extracting them, they appear.
Is there something I need to do in order to have these files appear? Is there some sort of file system refresh? Or am I being a complete idiot?
suppose i have two file with same name fstab one file is located in /etc and the other is located in /root/ If i make a change in /etc/fstab file the changes has to reflect in /root/fstab . Is there any command to do this?
In the gmd3 greeter.conf-defaults file its tells me the themes are located /desktop/gnome/interface/gtk_theme, but wheres that directory actually at, like how I can find it?
Btw, I know I can go back to gdm, but I'd rather understand how to theme this, before. I might just.I'm using compiz, btw, if that makes any difference.
Is it possible to locate the Firefox file that retains "Search" history (not particularly "Browser" history)?I have lost a hardcopy list of authors and titles of books/ebooks that I search the web for. However, most of the time when I would enter a name or title a drop down list would have that entry I wanted, and I could just click on it. That drop down list is what I am calling "Search" history.
I heard somewhere that by creating custom initrd image and default compiled kernel image, we can do PXE linux installation. can anyone please guide me 'what content will be placed inside initrd?'I know the process of creating custom initrd file .
i upgraded from 11.1 to 11.2. Unfortunately the new kernel does not work with my sata/southbridge (i googled and figured its a known issue). So i tried to boot a 11.1 64bit rescue system to install the older kernel and the corresponding initrd. The problem is, that i cant find the kernel and initrd on the rescue system.
I am working with Ubuntu for the first time since school and it was an intro class. I am trying to setup a file server for part of a school project. I installed x11vnc and am trying to set the password. However everywhere I look says the file would be located at ~/.vnc/passwd. However when I ls from the home directory .vnc does not exist. When I type out vncpasswd ~/.vnc/passwd I get returned a message The program 'vncpasswd' can be found in the following packages:
* tightvncserver * vnc4server
how I can get this setup? Am I using old information that is no longer accurate or am i messing this up somewhere?
This is what I tried to do:>cd ~/Desktop >sudo sh ati-driver-installer-10-1-x86.x86_64.run --extract.After entering my password, this appeared: >sh: Can't open ati-driver-installer-10-1-x86.x86_64.run.What am I doing wrong? It apparently worked in this thread.
how do I extract a pgp file on Ubuntu? I have the file and a passphrase. On Windows I have Kleoptra so I can right click the file and click 'decrypt'. Is there an easy way to do this on Ubuntu?
I am using grub4dos 0.44 but can't boot directly into Kubuntu. The bootup freezes at the step of reading the initrd. Can't copy 'n paste the exact bootup-message but it looks similar to this one, I found on another forum-thread:
Code: Filesystem type is fat, partition type 0x06 [Linux-bzImage, setup=0x1400, size=0xcff87] Unlike the guy who posted the two lines above, I installed Kubuntu on an ext3-partition (hd0,5), (which is /dev/sda6 in Ubuntu) and without an own bootloader, since I wanna use grub4dos instead of grub2. The installation is fresh - the initrd-file shouldn't be broken. My menu.lst looks like this:
I do not find any initramfs-2.6.33.5-112.fc13.i686.PAE.img in my /boot folder after I updated Fedora 13 after a fresh installation. The vmlinuz file is present in the /boot folder.he grub.conf file does not show any initrd entry too.
Where can I find a list of changes/fixes after a regular Ubuntu update has already been installed? Are the changes/fixes recorded somewhere within the system?
A fault in my USB key killed the contents of the /boot partition. I could restore grub, and got back kernel files by extracting kernel-desktop-2.6.31.14-0.4.1.i586.rpm, but now I miss initrd! (I have currently no means to make it.)Would someone having this one be kind enough to e-mail it to me? (It's around 6 MB so it should be OK.) I'll PM you my e-mail address.