Salix OS

As recently there have been the one or other problem for some users especially with newer hardware like wireless chips, I decided to build some new kernel packages.

I've uploaded them in the repository here:
http://people.salixos.org/shador/kernels/i486/ (i486)
http://people.salixos.org/shador/kernels/x86_64/ (x86_64)

All source and build files are here:
http://gaia.homelinux.org/salix/miscpac ... nux/3.3.6/

Adding the repository (not compulsory)
You can either download the package files directly or you can add the repository like this to your /etc/slapt-get/slapt-getrc:

Code: Select all

SOURCE=http://people.salixos.org/shador/kernels/i486/:CUSTOM

Or 64Bit accordingly:

Code: Select all

SOURCE=http://people.salixos.org/shador/kernels/x86_64/:CUSTOM

Base kernel packages (minimal)
Some Information regarding the installation. I renamed the packages/kernel as far as possible (for kernel-headers and kernel-firmware that's not possible) so you can install them alongside with the stock Slackware 13.37 kernel. You need to at least install kernel modules and the kernel itself. Just smp and huge kernels are available as they are almost exclusively used by Salix users.
For 32Bit the package names are:

kernel-huge-recent-smp
kernel-modules-recent-smp

For 64Bit:

kernel-huge-recent
kernel-modules-recent

After installing those two packages the /boot/vmlinuz symlink is changed to point at the new kernel. Therefor it's enough to update your lilo bootloader with this command:

Code: Select all

lilo -c -v

For Grub a simple line like this should be enough:

Code: Select all

update-grub

If you want to change the symlink back you can of course do that manually or just reinstall the stock kernel package. You can also add another entry to the bootloader for Salix with the other kernel so you can boot that one if the new one fails. Just duplicate the current entry and adapt the image and label line.

Additional kernel packages:
For wireless you probably need to update the kernel-firmware package too. It conflicts with the radeon_ucode package because it contains that firmware too.

If you need them, an updated kernel-headers and a separate kernel-source-recent package are available. The latter one also changes the symlink /usr/src/linux to point at the new kernel sources. Again you can just reinstall the old kernel-source package or revert it manually.

Other hints
A short note regarding loopback: That functionality has been moved to a module (instead of builtin) with slackware current. For me that module wasn't autoloaded so resulted in mount failures at first. I recommend you add such a line to your /etc/rc.d/rc.modules in any case:

Code: Select all

modprobe loopback

It's not compulsory of course. So if you have very specific needs you don't need to load it. But otherwise I would. Just makes your life easier.

Apart from that you might want to update your /etc/rc.d/rc.modules symlink to point at the new rc.modules-3.3.6-recent file. But that's absolutely not necessary, unless you feel you need it.

Version information
The currently available versions are:

3.3.6

Those packages are working fine here for a while. As they're compiled natively on 13.37 installing the NVIDIA driver or VirtualBox is no problem as with the stock packages.
I hope that short guide makes it easier for you. If you have any questions or notice any problem, you're welcome to post here.

Good idea Shador

Also I can confirm that 3.3.6 works on my PC, too. I'm even using the BFS (scheduler).

Thanks for all the work you've done on these, Shador.

One small thing to change in the post .

Shador wrote:
I've uploaded them in the repository here:
http://people.salixos.org/shador/kernels/i486/ (i486)
http://people.salixos.org/shador/kernels/i486/ (x86_64)

Should be:

http://people.salixos.org/shador/kernels/i486/ (i486)
http://people.salixos.org/shador/kernels/x86_64/ (x86_64)

then for x86_64:

Code: Select all

SOURCE=http://people.salixos.org/shador/kernels/x86_64/:CUSTOM

Shador wrote:
After installing those two packages the /boot/vmlinuz symlink is changed to point at the new kernel.

I pointed my boot loader to /boot/vmlinuz and booted Salix with your new kernel.

Thanks again, Shador.

I installed
* kernel-firmware-20120520git-noarch-1ab.txz
* kernel-headers-3.3.6-x86-1ab.txz
* kernel-huge-recent-smp-3.3.6_smp-i686-1ab.txz
* kernel-modules-recent-smp-3.3.6_smp-i686-1ab.txz
but kernel-modules 2.6.37.6...

I installed kernel-huge-recent and kernel-modules-recent and saw the same thing the first time I booted.

"Running /etc/rc.d/rc.modules -> rc.modules-2.6.37.6:"

However I don't see it here

Code: Select all

Wed May 23 12:37:33 2012: Bootlogd started (this is the first boot message that appears in /var/log/boot).
Wed May 23 12:37:33 2012: INIT: Entering runlevel: 4
Wed May 23 12:37:33 2012: 
Wed May 23 12:37:33 2012: ^[[01;33mGoing to multi user mode.^[[00m
Wed May 23 12:37:34 2012: ^[[9;15]^[[14;60]Starting sysklogd daemons:  /usr/sbin/syslogd /usr/sbin/klogd -c 3 -x
Wed May 23 12:37:34 2012: Triggering udev events:  /sbin/udevadm trigger --type=failed 
Wed May 23 12:37:34 2012: Polling for DHCP server on interface eth0:
Wed May 23 12:37:34 2012: dhcpcd[1959]: version 5.2.12 starting
Wed May 23 12:37:34 2012: dhcpcd[1959]: eth0: waiting for carrier
Wed May 23 12:37:36 2012: dhcpcd[1959]: eth0: carrier acquired
Wed May 23 12:37:36 2012: dhcpcd[1959]: eth0: broadcasting for a lease
Wed May 23 12:37:36 2012: dhcpcd[1959]: eth0: offered 192.168.2.4 from 192.168.2.1
Wed May 23 12:37:36 2012: dhcpcd[1959]: eth0: acknowledged 192.168.2.4 from 192.168.2.1
Wed May 23 12:37:36 2012: dhcpcd[1959]: eth0: checking for 192.168.2.4
Wed May 23 12:37:41 2012: dhcpcd[1959]: eth0: leased 192.168.2.4 for infinity
Wed May 23 12:37:41 2012: dhcpcd[2190]: eth0: eth0: MTU set to 1492
Wed May 23 12:37:41 2012: dhcpcd[1959]: forked to background, child pid 2211
Wed May 23 12:37:42 2012: Starting ACPI daemon:  /usr/sbin/acpid
Wed May 23 12:37:42 2012: Starting system message bus:  /usr/bin/dbus-uuidgen --ensure ; /usr/bin/dbus-daemon --system
Wed May 23 12:37:42 2012: Starting ConsoleKit daemon:  /usr/sbin/console-kit-daemon
Wed May 23 12:37:42 2012: Starting HAL daemon:  /usr/sbin/hald --daemon=yes
Wed May 23 12:37:44 2012: Starting ntpd...
Wed May 23 12:37:44 2012: 
Wed May 23 12:37:44 2012: ^[[01;37mStarting the print spooling system:^[[00m
Wed May 23 12:37:44 2012: cups: started scheduler.0;39m]
Wed May 23 12:37:44 2012: ^[[01;37mStarting the cron scheduling daemon:^[[00m
Wed May 23 12:37:44 2012: ^[[01;37mStarting the at scheduling daemon:^[[00m
Wed May 23 12:37:44 2012: ^[[01;37mConfiguring ALSA:^[[00m
Wed May 23 12:37:45 2012: Loading OSS compatibility modules for ALSA.
Wed May 23 12:37:45 2012: Loading ALSA mixer settings:  /usr/sbin/alsactl restore
Wed May 23 12:37:45 2012: ^[[01;37mLoading default keyboard map:^[[00m
Wed May 23 12:37:45 2012: Loading /usr/share/kbd/keymaps/i386/qwerty/us.map.gz
Wed May 23 12:37:45 2012: ^[[01;34mRunning System V scripts.^[[00m
Wed May 23 12:37:45 2012: Starting ConsoleKit daemon:  /usr/sbin/console-kit-daemon
Wed May 23 12:37:45 2012: ^[%G^[[01;34mRunning local startup commands.^[[00m
Wed May 23 12:37:45 2012: ^[[01;32mStarting up X11 session manager...^[[00m

or here

I happens right after "creating /etc/mtab" when bootlogd hasn't started yet.

I created a new link /etc/rc.d/rc.modules pointing to /etc/rc.d/rc.modules-3.3.6-recent.
Seems to have fixed it for me.

Thanks for reporting it. I'm going to look into it as soon as possible. But I'm quite busy otherswise atm and this is actually mostly cosmetic.

Thanks Tim for your other report too. It's corrected. I also added another note about loopback towards the bottom, which I initially forgot.

I also remember some still open issues with broadcom drivers et all. It would be great if you can refer those here. Not sure whether I can catch them all.

Tim CowChip wrote:"Running /etc/rc.d/rc.modules -> rc.modules-2.6.37.6:"

That should not matter, there is not much in this rc file anyway and usually it is the same for most kernel versions.

@thenktor good to know. thanks.

@shador I was wondering if the new kernel could be substituted for the for the huge 2.2.37.6 kernel on an installation usb stick. It would make it easier to install Salix on a machine with nothing but wifi, since one can't use slapt-get without an internet connection.

Salix OS

Newer kernel packages for 13.37

Newer kernel packages for 13.37

Re: Newer kernel packages for 13.37

Re: Newer kernel packages for 13.37

Re: Newer kernel packages for 13.37

Re: Newer kernel packages for 13.37

Re: Newer kernel packages for 13.37

Re: Newer kernel packages for 13.37

Re: Newer kernel packages for 13.37

Re: Newer kernel packages for 13.37

Re: Newer kernel packages for 13.37