Slackware :: Custom Initrd Splash For Current?
May 18, 2010Need to know how to create a custom initrd boot splash for slack current
it would be nice to have a seperate one for bootup/shutdown
anyone know how-to or where to find good info?
Need to know how to create a custom initrd boot splash for slack current
it would be nice to have a seperate one for bootup/shutdown
anyone know how-to or where to find good info?
I have been using slackware since version 10.1 and really like it. I have never had a problem until lately, version 13.1 has been stable as a rock for me. The first 2 or 3 updates to current ran well but then the problem started. After installation Slackware would get to the splash screen and bring up the first picture of a disk drive then just hang and never go any further. I do have a good burn on the dvd, have checked the md5 and burned at 4x. then slack 13.37 does the same thing. this is on 4 different computers with several different video boards.
View 8 Replies View RelatedJust 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?
After the bunch of updates with current, my custom kernel (2.6.33) can't boot.
The error is:
/sbin/e2fsck: No such file or directory while trying to open /dev/sda6
The superblock could not be read or does not describe a correct ext2
filesystem. If the device is valid and it really contains an ext2
filesystem (and not swap or ufs or something else), then the superblock
is corrupt, and you might try running e2fsck with an alternate
superblock:
e2fsck -b 8193 <device>
The /dev/sda6 is ext4 and is ok since it can boot with official huge smp kernel 2.6.33.
My custom kernel can boot before this bunch of updates in current.
What i missing in kernel?
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.
Is it possible to create a custom bootup splash screen, either a bitmap graphics file or just a simple text file. I'm not talking about the BIOS splash screen nor the boot loader input splash screen, but rather somewhere in between, i.e. when the HDD is detected as the boot drive, a splash screen is shown. I'm trying to make sort of a "rescue disk" that simply boots up to a shell, and I am wondering if I can display a custom message once the PC is booting up from this disk.
View 1 Replies View RelatedI'm looking for a software running under debian to create and resize custom splash images.
I know just GIMP, but maybe there is a special software.
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.
I've always booted Slackware with an initrd until recently. With my new installation of Slack Current (13.37), I didn't bother to create an initrd because of the constantly updating/transient nature of the current branch at the moment.My question is this: when 13.37 does go final in a few days, should I go back to my normal practice of booting with an initrd? Also, I think I understand how the initial ramdisk works, but is it really needed with the more modern kernels?
View 14 Replies View RelatedI've changed for huge kernel to a generic+initrd setup per the instructions in the README.initrd file however my machine fails to boot using that method. I get the following errors:
/boot/initrd.gz: Loading kernel modules from initrd image:
mount: mouting /dev/sda2 on /mnt failed: No such device
ERROR: No /sbin/init found on rootdev (or not mounted)
1. I've created the initrd using the results from /usr/share/mkinitrd/mkinitrd_command_generator.sh
mkinitrd -c -k 2.6.33.1 -f ext4 -r /dev/sda2 -m usbhid:ehci-hcd:ext4 -o /boot/initrd.gz
2. my root fs is ext4 on /dev/sda2
3. I've changed all necessary links in /boot
4. I've changed my /etc/lilo to:
image = /boot/vmlinuz
initrd = /boot/initrd.gz
root = /dev/sda2
label = Linux-Generic
read-only
I've recently updated my Slackware 13.1 system to the Slackware current. Although I have created my "initrd" image without specifying the "-u" option to "mkinitrd" it still starts up "udev".
That is causing me some difficulty because I am using "dmraid" to detect my RAID arrays. I had created my own device names such as "/dev/sdr2" for my root partition. With 13.1 I had no problem, since "udev" was not started by the "initrd" unless the "-u" option was provided. The current version seems to start up "udev" even without that option.
Is there a way to disable "udev" in the "initrd", or is there a way to specify custom "udev" rules for an "initrd"? I tried placing a "10-local.rules" file in the "etc/udev/rules.d" directory of the "initrd-tree" but that file had no effect on the device names generated by "udev" during the "initrd".
Here is my script that creates the "initrd".
Code:
ROOTDEVNAME="/dev/sdr2"# Name of root device
LINUXVER="2.6.35.7-smp"# Linux modules version
CLIBVER="2.12.1"# C library version
ROOTDIR="/boot/initrd-tree"# Location of root filesystm
[code]....
It will be helpful for me to understand "udev" issues related to an "initrd" because I will eventually try to use "mdadm" instead of "dmraid". So far I have only been able to get my system to boot from the RAID array using "dmraid" and I often run into new problems when I update Linux. Still, Slackware has proven to have the best support for booting from my RAID array because of the user community, documentation and flexibility.
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..
I've just installed a Slackware64-13.0 test machine with alienBOB's multilib packages. I'm running the stock kernel generic-2.6.29.6 with an initrd set up using mkinitrd.confEverything is fine except that I cannot build a right initrd for kernels 2.6.30, both the /testing one or a custom build: if I try, it will panic at boot with the "couldn't find a valid RAM disk image" error.On the same hardware, without multilib support, I was able to correctly build and boot 2.6.30 initrds.
View 11 Replies View RelatedLost my wireless keyboard and mouse upgrading slackware current.Boot seems to be normal.I just can't login, cause have no keyboard.
View 2 Replies View Relatedslackware-current kernel 2.6.35.10-smp for instance if i just want to connect to wep ap. i done
[code]...
it says waiting for carrier and it just time out, im wondering why i read somwhere that its not working good with slackware 13.1
I recently upgraded to slackware-current from Slackware 13 via slackroll, and have only encountered one problem. My file manager no longer thumbnails images, and icons (mostly PNG) aren't appearing no matter what GTK theme is set. Running from the command line produces no errors, and when brought up in something else (say feh /path/to/icon.png) it works perfectly. This is the only hitch I have encountered so far. The same thing happens with emoticons in Pidgin. Does anyone know of a fix?
View 5 Replies View RelatedFirst time I've done this in awhile Upgrading my Slackware64 -current VM, following the standard routine that has always worked in the past -
Code:
slackpkg clean-system
slackpkg install-new
The clean-system removed 2 packages -
util-linux-ng
eggdbus
Installpkg will no longer work, complaining that the rev command is not found. The problem hit with the removal of util-linux-ng. I cp'd util-linux to ~/. Extracted with tar and executed the doinstall. Fixed.
after update to slackware current 4 days ago i cant get sound working in wine in starcraf 2 i mean i got sound in instalation but not in game and i get error when i wanna configure sound in winecfg
err:alsa:ALSA_CheckSetVolume Could not find '{PCM,Line} Playback Volume' element
err:alsa:ALSA_CheckSetVolume Could not find '{PCM,Line} Playback Volume' element
err:alsa:wine_snd_pcm_recover underrun occurred
err:alsa:wine_snd_pcm_recover underrun occurred
in game i dont got that error but sound dont work btw my sound card is asus xonar essence stx
I updated my kernel in slackware current but can't install lilo, when i was with my old kernel it gave an error about not finding the sda drives (they were named hda before the upgrade).I booted into the slackware 13.0 dvd and modified fstab and lilo.conf replacing hda with sda but lilo still gives an error of not finding sda drives.How can i install lilo so i can boot into my sistem??
View 14 Replies View RelatedI've upgraded Slackware-13.1 I had installed to Slackware-Current using a local tree I had download with mirror-slackware-current.sh script, but when I rebooted I could not get the graphics to load. I think it's because I've also modified /etc/groups and add an username after audio: and video: group, but I forgot that and had to remove slackware from the machine.
View 4 Replies View RelatedI've tried a few different ways to install the ATI graphics driver "fglrx" to get 3D acceleration.If I try to install using the standard file "ati-driver-installer-10-4-x86.x86_64.run" from the ATI web site it appears to work but then I discover it actually got an error.I saw a reference to ATI requiring 32-bit libraries to install their 64-bit driver. Is there a link or post that explains how to add the 32-bit libraries. Will that solve the problem, or will I just waste more time trying that?
View 6 Replies View RelatedI use Alien Bob's mirror-slackware-current.sh with an excludes.txt to only download the parts of current that I want. Unfortunately it is not working for part of the exclude.txt file and I am at a loss to know why.
The excludes.txt is
Quote:
slackware64/e
slackware64/f
slackware64/kdei/kde-l10n-ar-4.5.5-noarch-3.txt
slackware64/kdei/kde-l10n-ar-4.5.5-noarch-3.txz
[code]...
This ignores e/ f/ y/ testing/ pasture/ source/ and usb-and-pxe-installers/ It also ignores most of kdei/ and /extra It is meant to ignore most of extra/source and just download the source for flash-player-plugin, but it is ignoring all of extra/source/, however the same syntax is working for kdei/ and extra/.
This is not an earth-shattering issue, but, something I've recently noticed with the Chatzilla add-on for Seamonkey in Slackware-current. Maybe it is just my problem.If I add Chatzilla to FF 4.0 everything works as expected, that is, when I launch Chatzilla the default start-up window shows up with a list of IRC servers to click on (freenode being my favourite).
However,when I click on Chatzilla in Seamonkey I get a blank window that shows up, there is no server list. I noticed that the window in Chatzilla went blank for Seamonkey recently after a -current update (maybe a library issue?)
I'm very keen on getting Mumble installed on my slackware -current 64 bit install. I found a slackbuild script for 12.2 here, but changing the version number resulted in failure. I also tried following the build instructions on the Mumble website, which failed with the following.
Code:
neil@slackbox:~/Downloads/mumble/mumble-1.2.2$ qmake -recursive main.pro
Reading /home/neil/Downloads/mumble/mumble-1.2.2/src/mumble11x/mumble11x.pro
WARNING: /home/neil/Downloads/mumble/mumble-1.2.2/src/mumble11x/mumble11x.pro:33: Variable LIBPATH is deprecated; use QMAKE_LIBDIR instead.
WARNING: /home/neil/Downloads/mumble/mumble-1.2.2/src/mumble11x/mumble11x.pro:33: Variable LIBPATH is deprecated; use QMAKE_LIBDIR instead.
[Code]...
I wish to do a fresh install of Slackware without KDE. I could use my Slackware 13.1 DVD but I thought, why not give -current at try? Is there a -current ISO or must I install 13.1, without KDE, and then upgrade to -current? Or, is it possible to remove 'all things KDE' and then upgrade to -current?
View 8 Replies View Relatedi just updated my slackware to current, and every time i try to log in in my kde session my desktop is upside down.i mean literally everything is upside down, the only way i can have a usable desktop is with the "fail-safe session" of kde option on kdm which is what i'm using right now.does anybody know how can i solve this?i would post a snapshot of the upside down desktop but i can't do anything when i'm using it. fonts, windows, panels, icons everything is upside down..i solved this, just reinstalled the nvidia drivers and everything is goood again
View 1 Replies View RelatedI'm running slackware-current in a virtual machine on virtualbox 4, 512 mb ram, 1gb swap.Everything works fine, except the x11 mouse. Xfce will start up fine, and show the 'tips and tricks' dialog, and then freeze. I can't change to a TTY, or click. The mouse moves, but doesn't click.
View 13 Replies View RelatedI am trying to figure out how to load the generic kernel in Grub2.
I have run the /usr/hare/mkinitrd/mkinitrd_command_generator.sh and ran the output:
Code:
Why this will not load.
I downloaded AlienBobs LibreOffice 3.3.1 package [url]. I installed it without any problems.
But when I try to start it, the splash screen shows for a moment and then disappears.
When I strace /usr/lib/libreoffice/program/swriter I get this:
Code:
On my notebook (which unfortunately is broken) the program ran fine. JRE is installed.
I'm trying to take my current windows7 (x64) setup and make it into a dual-boot setup with slackware 13.0 (x32) and am hitting a brickwall. I guess I would like to know if I can salvage the situation without formating my windows drive. I fully intend to, but I had hoped to not do it this month. I'd like to get dual boot going so I can master it and acquire all the files/drivers I'll want and then format and do it 100% right next time.
Currently I have windows setup on a 3x 500gb Raid0 onboard array which itself has been flawless. After I shrunk my current partition size to give me about 25gb of free space I proceeded to setup Linux, and I was unable to perform the cfdisk portion for partitioning the array for Linux.
I tried using cfdisk:
/dev/hdx (a1-a3,b1-b3)
/dev/sdx (a1-a3,b1-b3)
I even attempted to locate with: cat proc/partition and tried using cfdisk on every device it located. It always said it was either an unknown partition table and should I start at zero, or bad partition. I was of course too concerned over my windows setup (which has almost 1tb of stuff I have not backed up) to go any further into the unknown.
PS: I have used Slackware before, back at 8.1, 10, and even a very brief interlude at 12.0, this is my first attempt on this computer however with 13.0, it is currently running fine on my laptop and my PS3 (Laptop is even dual booting 7/Slack13. Albeit without raid)
Phenom 9850
M2N-SLI Deluxe (Nvidia AM2)
4x1gb of 1066 kingston hyperX
3x500gb WD Caviar Black Sata2 3.0