I am trying to setup Slacware 13.1 x86_64 to a encrypted partition. I used the README_CRYPT.TXT howto : [URL] At the step when I create an initrd.gz I get this error: Quote: ERROR: No /lib/modules/184.108.40.206-smp kernel modules tree found for kernel "220.127.116.11-smp"
I tried to look into the directory and there was only modules under 18.104.22.168. So I tried to change the command into: Quote: mkinitrd -c -k 22.214.171.124 -m ext3 -f ext3 -r cryptroot -C /dev/sda2
This command was successful, but I don't know if this is alright. I made the changes in lilo.conf, add initrd = initrd.gz. This is all on unencrypted /boot partition. The boot=/dev/sda1 I also set for the unencrypted boot partition. When I boot the system I get a kernel panic:
i want to do is dual boot windows, Slackware, and Debian. I don't care if i use lilo or grub, they are both equally familiar to me, just above nort. i have made attempts at editing the lilo.conf file, which said it had warnings but i didn't know how to view the warnings. It made it so i could select it, but when i did it booted the slack kernel with debian with no modules. get slack, debian and windows all running on my machine the way they're intended?
I upgraded to the latest -current just like always. I do the kernel packages last. This time, the machine failed to boot, telling me that it could not find the kernel modules. Well, rats.
I booted with a slackware dvd, passed the huge.s kernel, and booted into /dev/sda7, which is my main partition. I mounted /dev/sda7, and installed the kernel-modules-126.96.36.199 pkg. Rebooted, and got the same error?
I booted again with the dvd, mounted the partition, and navigated to /lib/modules - no 188.8.131.52 in there!
This has got me stumped. I expected to do /etc/init.d/vboxdrv setup after the upgrade from 11.3 to 11.4 but the command fails. The log is (it seems to repeat so I only quote the final bits to make it fit into the wordcount limit):
Code: make KBUILD_VERBOSE=1 -C /lib/modules/184.108.40.206-1.2-desktop/build SUBDIRS=/tmp/vbox.0 SRCROOT=/tmp/vbox.0 modules
I was trying to install VirtualBox through the YaST > Software Management but it is not working, someone in the forum told me that I have to download the OSE version and do it manual way. Finally I am able to start up VB but not able to use the network connection. Thus I am trying to do this:
/etc/init.d/vboxdrv setup. I get this error:
When I type dmesg, it shows me a bunch of info which I don't know what should look for. When I type modprobe vboxnetflt, I get the error: FATAL: Error inserting vboxnetflt (/lib/modules/220.127.116.11-1.2-default/updates/vboxnetflt.ko): Invalid module format. what should I do in order to get my VB to be able to connect to the internet?
Recently I downloaded the latest 2.6.33 kernel from kernel.org. I had earlier 2.6.29 kernel version installed through Fedora 11 Leonardos.I followed simple steps through url.html and it went fine.I could see new Kernel during grub.conf splash display during dual-boot option.But there are few doubts like as shown below:
can I upgrade the kernel on my slack 12.2 to the version 2.6.29 or higher?I need the kernel must support the KMS mechanism.Why I need KMS? I want to define virtual screen of size greater than 2048 x 2048. Why I need so huge virtual screen?To run two-display configuration on my dual-head Intel graphic card. At the moment I can set max 2048 x 2048 virtual screen which is not enough for my two displays:LCD of notebook has 1400 x 1050 resolution, and external LCD panel 1280 x 1024. At this moment a part of desktop is on both displays. Small part but causes some problems, and at this moment only awesome (really awesome) window manager can handle this configuration.
I was running 2.6.35 without any errors. I decided to upgrade to .4 today, used the same config. After i rebooted into the newly compiled kernel i got these errors on boot..
Code: Mounting non-root local filesystems: ntfs-3g: Failed to access volume '/dev/sdc1': No such file or directory ntfs-3g 2010.3.6 integrated FUSE 27 - Third Generation NTFS Driver Configuration type 1, XATTRS are on, POSIX ACLS are off Copyright (C) 2005-2007 Yura Pakhuchiy
I did a complete disk check and it appears to be fine. Then i booted in the default kernel that comes with slackware 13.1 and walla..No errors! What could be the problem? Did someone experience the same issue?
How you doing all? I've my Slackware 13 box. Recently, I have upgraded to -current, and while the upgrade I noticed that my connection went down while it was downloading the new kernel. I had doubts that it got damaged.
Code: slackpkg upgrade-all and found every thing is up to date. While upgrading, the system asked me to run lilo, and I did. But after rebooting, I got the (Kernel Panic) error. I logged back in using setup disk, and the chroot to my original system root directory. I removed the current Kernels, and now I need to re-install it.. there I'm stuck. Slackpkg isn't working because the box is not connecting to the internet. or links is more than appreciated since I'm not geek enough to sort it by my own. Also few googling didn't set me up with a solution so far.
I noticed that slapt-get excludes a lot of package titles based on aaa, glibc, and kernel. I've been wondering why, and haven't been able to find any definitive answers... Anyone here have any ideas on why that is? My Slackware installation is currently kernel 18.104.22.168 (I think) and the newest available on the official repositories is 22.214.171.124 (or something like that).
When I put in slapt-get --upgrade it spits out about 15 packages that are excluded that it won't upgrade. Now, I know I can remove the exclusions by editing the slapt-get configuration file, but I don't want to if it's going to screw something up. So my question is: Is there a reason those are excluded? Is it unsafe to upgrade the kernel with slapt-get?
I cannot upgrade to 10.4, because my EEE 901 has a too small "system disk", 4GB. However, I do have enough space on my slower 16GB SSD disk. Can I move some recommended system directory there temporarily and symlink from the root disk? Would the upgrade data itself be a good candidate, perhaps? The work around would be to do a clean install of the new version, but I rather not, as I have some tweaking to do afterwards in that case. As it is now, I have 700MB of free space, and need about 1.4GB, if I'm not mistaken.
I have a zyxel dsl (usb) moden, which needs a firmware portion to work, called cxacru-fw.bin.
I have been using this modem using with at least two different slackware distributions, even when the atm drivers were not included in the kernel.
Presently I am using slackware 13.0, with the vmlinuz-huge-smp-126.96.36.199-smp kernel.
I downlowded the 2.6.34 kernel, because I need it for a new webcam, compiled and installed it, and oops! the modem does not work anymore.
I am pretty sure I have configured the kernel correctly; dmesg tells me the modem is recognized by the kernel, as it is with the previous one, but the firmware is not loaded, because the DSL led remains off.
I attach the kernel configuration lines:
I have tried forcing the kernel to load the firmware, using but it didn't work either.
I have changed kernel to 2.6.33. After that ifconfig command shows only my ethernet card, wireless card have disappeared. What is wrong. In the old kernel everything works fine. I am sure that i have installed wi-fi stuff with kernel.
I have just compiled a new kernel. When I boot into this new kernel and do an lsmod it is only running two modules. The only thing I changed in the configuration file was to compile ext4 file system into the kernel. My computer is an HP Pavilion dv4. The two modules are lirc_ene0100 and lirc_dev. I am running Ubuntu 10.04. The new kernel is 188.8.131.52+drm33.5. The kernel seems to work fine but I need to know why and how it can only be running two modules.
I'm trying to install VMWare server on my Kubuntu box and it's telling me there are 3 "kernel modules" that it needs me to remove (apparently they were installed previously and VMWare isn't liking that).How do I remove them? Never messed with the kernel modules before.
I recently updated the kernel from SLES 11 to SLES 11 SP1 .However my kernel modules are not getting loaded and they throw an error such as shown below:"Errornserting mii : Unknown symbol in module, or unknown parameter (see dmesg)"
I am writing a kernel module which need to do something at some interval. Now this problem can be solved by using a user process, which will send signal to the kernel and the kernel would do accordingly. But it would be nice, i could do it within the kernel module itself. Is there any way to use SIGNALs inside the kernel module?
I am trying to write kernel modules. And am running Ubuntu 10.04 x64. I have downloaded both kernel source and headers. Unpacked kernel source and made a /usr/src/linux symbolic link pointing to the src. Here is the output of running make:
How do I get modules in the Kernel to load automatically at boottime? I''m specifically trying to get i810fb to load during the boot process. In Ubuntu, I just had to edit a file and update my initramfs. How do I do this in Fedora?
The new kernel upgrade on Fedora 14 will not boot. lib/modules do not exist is the message. Grub was adjusted to match the old kernel, and the new kernel when booting says lib/modules do not exist. The old kernel has twice as many modules as the new kernel in lib/modules. How do I get the new modules to install so I can boot with the new kernel then? Should I reinstall the new kernel?
I am having some issues compiling kernel modules against the pre-built OpenSUSE kernel. Whenever I compile a module and try to load it, I get something like:
Code: insmod fs/smbfs/smbfs.ko insmod: error inserting 'fs/smbfs/smbfs.ko': -1 Invalid module format It doesn't actually matter what the module is, they all do the same thing. I have tried the above mentioned smbfs, I've also tried:vmware kernel module