I have installed Slack 13.37 for test on VMware. I installed just all - also all avalible distro. kernel imiges:
Code:
vmlinuz-generic-2.6.37.6
vmlinuz-generic-smp-2.6.37.6-smp
vmlinuz-huge-2.6.37.6
vmlinuz-huge-smp-2.6.37.6-smp
and the default is vmlinuz-huge-smp-2.6.37.6-smp.
Im trying to switch to vmlinuz-generic-2.6.37.6 So, what I did:
One thing I always do is switch to the vmlinuz-generic(-smp) kernel in /etc/lilo.conf and build an initrd (see /boot/README.initrd for details). The "huge" kernel used by default is only meant for installing and not recommended for everyday use. It has a lot of drivers you don't need built-in and uses more RAM than the "generic" kernels.
still trying to find my feet and get to know Slackware. In one of my previous threads, 'things to do after installing' i was told the above message. When i installed, it used the huge kernel, but i'm unsure if that was the one that got installed. when i start slackware up, above the login screen it say, �wecome to Linux 2.6.37.6-smp (tty1)� I was wondering how to swich to the generic smp kernel, do I just change the vmlinuz to the desired, in lilo?
I am trying to install fltk-2.0.x-alpha-r8570 on Ubuntu 10.04, I get following error during make process
Code:
root@programmer-desktop:/opt/fltk-2.0.x-r7680# make === making src === Makefile:223: makedepend: No such file or directory Compiling add_idle.cxx... add_idle.cxx:1: error: bad value (generic) for -mtune= switch
Using slackware current and I'm really digging KDE 4.4.3. It's been way more stable on my machine than 4.3.x and it performs MUCH better. I think slackware 13.1 is going to be a really good release. Much better than 13.0. Looking forward to upgrading all of my hosts though it will probably take me a few months given how many I manage.
I've started using the huge.s kernel and when i try to compile packages slackware complains about kernel headers but all i see is the smp header files on the slackware discs ?
I am a long time (1.something) slackware user and maintainer of a mirror site.I'm suddenly having problems with my favorite distro. (1) I've been mainly running Slackware64. When I was experiencing recent problems on a Slackware (32) 13.1 system, I discovered the huge-smp kernel does not support more than 4G of RAM. This is an obvious bug, and I am shocked that there is no fix out yet. Surely I can't be the only Slackware 32 user with >4G of RAM. I've verified it on a 12G i7 system and an 8G Athlon64-X2 system.
I'm booting with Slackware 13.1 x64 My MB is GA-X58A-UD5 rev. 2 but I cant boot. My HD which is connected to the SATA3 port 6 and 7 is not getting detected. It is a Marvell SE9128
How can I tell the Huge.s to load the drivers of this controller?
I'm trying to decide which kernel to install in my Slackware 13.37 installation. What is the difference between huge.s and the hugemps.s kernels ? Does one do something the other does not ? I'm installing Slackware because I've read it has no Pulsemedia baked into it. I hope neither kernel has any of that stuff.
Does anyone notice that Slackware's user/groups is cluttered with things no one will ever need, do you need be to be part of the slocate group? like really? Why doesn't every program just have its own group then, I look at my distro (LFS built), SuSE and some others and I can't help but notice the huge amount of groups in slackware, if you going to add groups for everything then why in the universe do we even need sudo for? Just make the binary you want to work a group and change its ownership..... wtf is Pat and the rest of Slackware doing?
how to create the huge.s kernel files on the slackware disks? or at least direct me to a post if there is the same question. I currently rsync my files to Alien BOB's script, and i use syslinux to install from my usb stick. i was wanting to install using a later kernel just for testing purposes. (i.e 2.6.34-rc3 as of this writing)
Where can I get a copy of the 2.6.33.4 config that comes with Slackware? Also, can I get a binary of the kernel, the one that comes with Slackware 13.1?
I'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 am going to change my hardware soon, just a new motherboard and cpu, same sound card,gfx card and other stuff. Will it boot and run ok ( like a live cd/dvd) until I have time to do a reinstall or does it have specific ports the hardware is installed on now?
I was interested in the idea of the btrfs subvolumes, so I made a virtual machine and installed Slackware as per the instructions here: [URL] It all went very well, but when I tried to switch from the huge kernel to the generic kernel and use the initrd.gz generated from step 29 (except that I used 2.6.37.4-smp instead of whatever's there) in lilo.conf, it failed to boot. I also noticed that in the instructions themselves, the poster doesn't actually add the initrd.gz to lilo.conf, so I'm guess the huge kernel has everything it needs to boot properly.
I've installed Slackware64 on a Toshiba Qosmio laptop (booting with ext4, SAMSUNG HM500JI HDD, 3 GB Ram, Intel Core 2 Duo Processor, Intel chipset and graphics).The system boots the huge kernel just fine. But after booting with the generic kernel AND after having prepared a mkinitrd with the mkinitrd generator, the boot process crashes at ~4sec with a panic.
lately I compiled the 2.6.35 kernel and met the following problem: the kernel I get it is a generic kernel so I have two generic kernels. I want to have a possibility to boot both kernels: the new and the old one. I cannot resolve the problem of a creating initrd as mkinitrd run for the new kernel would overwrite the initrd.gz generated for the old kernel. So , I make a new directory where I put this new kernel. Is there a way to have both kernels together in /boot ?
My Slackware boots using the huge kernel. I am not using LILO; I am using GRUB from the extras directory on the DVD. I followed the tutorial @ [URL] up to the point where it discusses modifying LILO. My /boot/grub/menu.lst reads, in part:
# Linux bootable partition config begins title Slackware Linux on (/dev/sda7) root (hd0,6) kernel /boot/vmlinuz root=/dev/sda7 ro vga=normal # Linux bootable partition config ends
This boots the huge kernel. What changes must I make to the above menu.lst entry to boot using the generic kernel?
i'm attempting to configure the vmware server on the above mentioned system,without luck.i can't get the vmmon to compile. I have tried this out-dated guide [URL] but no luck. I have setup made the necessary links as explained in this guide [URL] I haven't managed to try out the any-any patch since no link to the patch is alive anymore.Since slack 13.37 is using 2.6.37.3 kernel I wonder if anyone has found a way to compile the vmware modules on these recent kernels.
I just did a full install of Slackware64 on my netbook. Everything was sweet until I tried switching to the generic kernel. Even before this, I noticed when I ran the mount command it listed not sda3, which really is the root partition, but /dev/root as the root partition. This also appears in mtab, but not fstab. So yeah, here are the errors when I try booting into the generic kernel:
Code: mounting /dev/sda3 on /mnt failed: No such device No /sbin/init found on rootdev (or not mounted) bin/sh: cant access tty: job control turned off
I've tried rebuilding the mkinitrd_command_generator.sh script several times, as well as lilo.conf. But no success I've looked at some similar old threadss here but most of them are related to slackware 12 and older, so I don't know if these issues are related or not.
I'm currently trying to setup Slackware 13.7 on a server, using software RAID 1. I'm using the README_RAID.TXT document at the root of the Slackware disc as a reference. Anyway, here's what I have so far.
[root@raymonde:~] # fdisk -l /dev/sd{a,b} Disk /dev/sda: 41.1 GB, 41110142976 bytes 255 heads, 63 sectors/track, 4998 cylinders, total 80293248 sectors Units = sectors of 1 * 512 = 512 bytes
[code]....
I created an initrd image using mkinitrd -F, added an according stanza to /etc/lilo.conf and ran 'lilo' after that. Now I can boot on the vanilla huge kernel all right. But I can't seem to boot on the generic kernel. Whenever I try to do this, the boot process stops short on the following error message:
Code:
mount: mounting /dev/md3 on /mnt failed: Device or resource busy ERROR: no /sbin/init found on rootdev
I recently installed slackware and while I was in the process of installing video drivers, I noticed something odd. "init 3" (or init anything) doesn't seem to work for me. While working in XFCE, when I do "init 3", nothing happens. But then, when I do "who -r" it says I am in runlevel 3 even though I am still in XFCE.
I suspect a few people will eventually run into this problem, and while it's easy to get around for the more experienced users (the ones that *should* be running -current), we all know that everyone isn't in that group
I have a ThinkPad T60 with the AR5008 chipset. I am using a Madwifi driver that I complied from source (this is a fixed driver related to a bug report on this chipset). My Thinkpad has a hardware switch on the front.My problem is that the wireless works whether or not the radio switch is in the on position.I have not been able to figure out how to make the wifi radio turn on and off with the switch.Note that the bluetooth does respect the switch.
I upgraded to current, and x won't start... I suspect it's probably an issue with the Nvidia drivers (I forgot to swith my xorg to the nv drivers; I knew I'd be getting a new kernel). Anyway, it leaves me with an unusable computer. Is there anyway I can get into a console before x tries to start. BTW, the ctrl-alt-f1 hotkey isn't working.
I turned my wifi switch off because I was on a plane, and wanted to save battery, but now Slackware isn't recognizing that it's being turned back on. I toggle the switch in XP, and the light goes from orange to blue, like normal, but no matter what I do in Slackware, the light stays orange. Wicd just tells me there are now wireless networks in range. My wireless card doesn't show up in ifconfig, but lspci shows it fine
I am running Slackware 12.2. I have checked the file like /etc/rc.d/rc.inet1.conf, and the command 'ip' or 'ifconfig', but still can not figure out how to write a script to switch between two network configurations easily.
Suppose that one configuration uses DHCP server to dynamically give the ip address, and uses a Default Gateway 1.1.1.1, a net mask 1.0.0.0, a DNS server 1.1.1.0; and in another configuration the Ip address is fixed, and use a Default Gateway 2.2.2.2, a net mask 2.0.0.0, a DNS server 2.2.2.0; Anyone would like to give me a hint on how to write one (or two separate) script(s) to switch between these two settings?
Since 13.37 I notice that vi needs the 'home' key to switch from input to command mode. I think this is only when I connect via Putty to the machine. When I am on local console it is still ESCape like it used to be. Does anyone know how to set it so that vi will switch from input to command mode using the ESCAPE key when using Putty?
Another vi question : When you edit htm files, vi goes automagically into some sort of html display mode. Ofcourse I never want that since all I do is edit the html in vi. So I need to go to command mode and type :normal everytime I want to edit html files. Where can you configure that vi (or vim) default to normal mode always?
<I see that vi links to elvis : > # ls -al /usr/bin/vi lrwxrwxrwx 1 root root 5 Oct 3 2009 /usr/bin/vi -> elvis*
