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/126.96.36.199-smp kernel modules tree found for kernel "188.8.131.52-smp"
I tried to look into the directory and there was only modules under 184.108.40.206. So I tried to change the command into: Quote: mkinitrd -c -k 220.127.116.11 -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-18.104.22.168 pkg. Rebooted, and got the same error?
I booted again with the dvd, mounted the partition, and navigated to /lib/modules - no 22.214.171.124 in there!
it's possible to compile the 2.6.37 kernel patched with the autogroup patch on a Slackware 13.1 system running 126.96.36.199-smp with 188.8.131.52 headers? I just compiled and installed the 2.6.37-autogroup kernel from AUR on my ARCH setup and I like it especially when using firefox with lots of tabs open and other background apps also running. I did notice a speed and smothness difference in my ARCH testing setup with this kernel patch and I can get same results in 13.1??
I'm trying to bring my Slackware system back to life as my XP HDD is dying... I've got everything working except for my audio. I got a new motherboard (ASRock P43DE3) and it has a VIA VT1708S as the onboard audio. Is there any way I can get this working without rebuilding the kernel?
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??
I'm currently trying to install unRaid on Slackware following this tutorial :[URL].. I'm new to Linux and after many hours, i finally managed to build the new kernel for unRAID (184.108.40.206). But audio on HDMI port doesn't work I tried alsaconf without success. HDMI sound works when i boot into the old kernel.
For some reason, it seems that 13.37 isn't loading the modules I need for cpu frequency scaling. I've edited /etc/rc.d/rc.modules so that CPUFREQ is set to on. On 13.1, this would mean the powernow-k8 module would be loaded for my AMD cpu, and the subsequent "ondemand" governor would be loaded. However, for some reason this isn't being done during the boot process. I've tried it using both the generic kernel and the huge kernel (I'd been using huge for a long time before without realizing it.) Has anything changed in 13.37 with regards to CPU frequency scaling?
I've done a clean install of Slackware 13.37 64-bit and am having trouble with building the Perl modules for Bugzilla 4.x.x (downloaded yesterday with bzr). This same problem exists with both Bugzilla stable and 4.1.2+.Executing checksetup.pl results in
Code: checksetup.pl * This is Bugzilla 4.1.2+ on perl 5.12.3
I just installed slack 13.37. I was poking around a little and I noticed that I have all these modules loaded... yet when I open up /etc/rc.d/rc.modules almost everything is commented out. how are these modules being loaded at boot time?
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?
My cli php is missing modules as regular user but not as root. In particular, mysql is missing... which is how I came across this issue. I'm running Slack 12.2 w/ php 5.2.14, standard Slack packages. As a normal unprivileged user:
-> whoami ; php -v ; php -m |wc -l ; php -m |grep mysql jerry PHP 5.2.14 (cli) (built: Aug 25 2010 15:17:31) Copyright (c) 1997-2010 The PHP Group
I've tried reinstalling php and it made no difference. php.ini is not to blame. I've Google'd this to death, no luck.
I have a system using a Linksys WUSB54B usb wifi adapter that needs the rt2x00/rt2500 modules. Using the fresh install kernel, 18.104.22.168-smp, the modules are there and I get my interface up.
But, when I configure my own kernel, not an smp system, I cannot find the .config option in the menu for rt2x00 network adapter support and the modules are not in /lib/modules/vmlinuz-22.214.171.124-first directory tree after a "make modules_install".
I looked through the configuration menu, but could find no reference to the rt2x00 drivers.
With the latest Freenode changes SSL connection is now possible which presents no problem, particularly with rworkman's ca-certificates slackbuild, But configuring sasl for the password to nickserv presents a bit more of a challenge as 3 perl modules are required: Crypt::OpenSSL::Bignum, Crypt::DH, Crypt::Blowfish and Math::BigInt. I have not packaged perl modules for slackware before and I guess there is always a first time but can I ask if anybody has already neatly packaged up the required perl modules? I suspect they will be very popular with Freenode slackware irc users...
I installed a fresh copy of Slackware 13.1 (stable) on one of my media servers and I am experiencing something strange.... When I power up the machine, I see the kernel booting, no errors, until it gets to the point where it says:
And then randomly freeze there.... Well the machine is not totally frozen because the cursor still blinks. But it will never continue... Like I said, this happens on a random basis... After a reset, it might go through or simply stall at the same spot.
I remember after installing Slack 13.1, I rebooted the machine but forgot to remove the DVD from the player, so the install routine started up, and froze at the same point when it was loading the kernel for the setup programs...
My mobo is a MSI k9N platinum.
I never had this problem before.... (well I never used 13.1 before). Since I got this machine, I used slack 12.2 and slack 13-current with success.
This problem makes the machine extremely unreliable because I intent to use it as a backup and media server, so chances I will WOL the machine and use it remotely... if that happens.
I have one machine where I have several versions installed on different partitions. The base partition (/dev/hda1) is Slack 12.1. On a spare partition (/dev/hdc4) I had installed Slackware64-current. Last week I slackpkg upgraded and installed the 126.96.36.199 kernel, and now that partition will not boot. I know that with the new kernels the hd* designation has been removed, and have already redone that fstab (accessing it from a different boot) to reflect the sd*. Here is the slack64 section of my lilo.conf:
Code: # Linux bootable partition config begins image = /other/spare4/boot/vmlinuz
I am running a server with a GRSecurity patched Kernel 188.8.131.52. I've tried to optimize the kernel as much as I can and know it (removing options, not needed drivers and so on) and compiled the modules into the kernel (no loadable modules anymore). I've started with Slackware 13.0 and the default config for 184.108.40.206-huge. Still I am not sure what to remove/optimize further now.
My question: Is there a way to boot with a kernel with loadable modules, check which modules are really needed for this hardware, (do something like lsmod) and save the running configuration modules for a next kernel compile to be the default .config instead of writing them down by hand and search for the appropriate names in .config or during menuconfig? (Note: zcat /proc/config.gz > .config is NOT the way I want, as it gives me just the current kernel config)
I have been given the task to install slackware 13.1 over windows. I have downloaded and copied slackware 13.1 on to a disk, and rebooted the computer, but i am not getting what all the tutorials have shown. I have been looking for tutorials that specifically instruct me as to how to install slackware 13.1 on to a windows xp. I am not trying to dual run I just simply want to run slackware and slackware only.
Dan Rosenberg has issued another Linux Kernel Exploit with PoC described in LWN [URL] I have tested that this exploit is not working on -Current (custom kernel, 220.127.116.11), which is good sign that Slackware is already immune of those problems.