Slackware :: 64 13.0 And Realtime Kernel Works, But Cannot Set Priorities?
Jan 25, 2010
I succeeded with the 2.6.31.12-rt20 on the Slackware 64 13.0.Kernel config seems fine, i use PAM.I can launch jackd as user with the realtime flag, BUT...Using top and htop, i can see that /etc/security/limits.conf or /etc/security/limits.d/limits.conf or wherever i put this file, priorities and nice are not set.Of course i added this to this file :
i need to use the realtime kernel because i use jack audio connection kit so i tried to install the realtime kernel from the install/remove software program. I've found 2 kernels : Kernel-trace and kernel-rt i tried both of 'em but i cannot boot up suse. The first one gets to 3/4 of the loading bar , i hear the welcome sound and then it won't do anything else. The second won't do anything, black screen.
Just got Studio 9.10 running and the RT kernel installed. I have a Prescott P4 3.2ghz (hyperthreading) and i encountered what looks like a common freeze problem. I am guessing my cpu will not be supported in the RT kernel since it is pretty old now.I added nosmp acpi=off during boot at the Grub2 menu and it booted fine and I was able to capture some video great.
My questions is, if I remove the smp support by using the nosmp option, do I still benefit from the RT kernel or would I do just as well with the generic kernel I have installed?Eventually I will upgrade do a new system board and processor but for now I just got some life back in this one by switching to Linux
I am trying to install vmware server on CentOS: In vmware installation guide it says before intalling:
Before you begin, read the following notes and make adjustments to your host system: The realtime clock function must be compiled in your Linux kernel. The parallel port PCstyle hardware option (CONFIG_PARPORT_PC) must be built and loaded as a kernel module (that is, it must be set to m when the kernel is compiled).
I've got a problem in doing sudo working for mounting things (e.g. usb pen or optic discs). Details:The OS: Slackware 13.0The response to sudo -l command:
Code: User user1 may run the following commands on this host: root) /sbin/shutdown -h now, /sbin/shutdown -r now
The 486 kernel works just fine, and while I have only 1GB of RAM at the moment I hope to have 2GB someday and would like to take advantage of the dual core CPU, so I would like to configure grub to run the 686 kernel by default. For whatever reason, it runs the 486 right now and the 686 fails in a major way: there is no network connectivity at all. It could be plugged into my cable modem router and it shows no wired connections. The fact that one works and the other doesn't puzzles me since I haven't touched either since the install and a few rounds of upgrades.
I should mention I'm newbie but getting better; I managed to install debian on this x60, yet while preserving the factory install rescue & recovery partition and preserving the factory install MBR so that ibm-specific hardware functions (thinkvantage button, etc.) still work. This required me to use dd to copy the first 512 bytes of my debian partition to a file in the windows partition, etc., and modifying the windows bootloader. (I wish I had learned dd long ago--it rocks). I did this because if I ever resell the X60, the fact is most people use MS Windows and having that partition adds a perception of value to some potential buyers; not to mention I paid $ for it (I was young & stupid) so why should I delete it. I also backed up the recovery partition on another drive using dd over NFS in case the hd ever heads south.
Anyway, I've never been comfy with messing with the kernel. I did once recompile a module for ALSA because it had a bug in it for an old Yamaha integrated sound card on an old PIII and the newer version worked [alsa fails on this x60 too but I think I found a post on here that has a solution I will try later]. But I'm clueless as to networking modules, not to mention the correct module is installed already from Intel for this chipset. So what is there to do?
Here's a clue: the ifconfig output is radically different from the 686 and 486 kernels. Looks like hardware is not being detected since eth0 fails to show:
I would show the diff output below if it weren't so long--and not allowed--upon 2 text files, the first holding the output of modprobe -l under the 486 kernel and the second under the 686 kernel.
i just updated my mainboard, because of a failure in the grafic chip. Now I have a icore 7-2600K CPU with 16GB memory.The system will not boot with the latest kernel version Kernel 2.6.38.11 - Kernel 2.6.38.10 . It crashed and resets the system.
But when I am using Kernel 2.6.35.30, then it works, as you can see. As well the kubuntu 64bit CDROM does not work. Crashed as well.
I'd be interested in your views on this. Background: After many hours of trying to configure a particularly recalcitrant graphics card as posted here, I eventually resorted to trying Mandriva 2009, which, with the 2.6.27-desktop 586-0.rc8.2mnb kernel, solved the terrible problem of slow, hit-and-miss booting with Debian and also random freezes with Ubuntu.However, when updating to Mandriva 2010, the problems with booting, and also a wrong screen resolution were back so, for the time being, I settled for the 2009 release.
My question is: Having found out that the Mandriva kernel worked, does anyone know if would it be possible to finally bring this laptop to heel with Debian + a 2.6.27 kernel and following the time-honoured adage of "if it ain't broke, don't fix it" leave such a kernel in place without updating to a newer one?
I have a small question about the repository priorities in 11.2. A couple of months ago I got a new laptop but have noticed that the laptop has not been updating KDE 4.3 whenever I select "Package -> All Packages -> Update if newer version available". I do get some software updates however - it just seems that the KDE repo is being ignored by YAST.
For example, if I search for (say) kde4-greeter I can see in the versions that I have 4.3.5-02.1-x86_64 installed from openSUSE-11.2-update (priority 10).
But kde4-greeter version 4.3.5-18.5-x86_64 from Index of /repositories/KDE:/KDE4:/STABLE:/Desktop/openSUSE_11.2 (priority 1) is available. It's just not being selected automatically when I do the "Update if newer versions available".
The same thing applies to any software in the KDE repo - they're all being ignored even though that repo has a more important priority. Unless of course I've got it totally wrong and 10 is more important than 1? Dont think so though..
It's not incredibly important - everything is running very nicely here.. But I'm just wondering if I'm missing any security updates or new toys because the KDE repo is being ignored..
For info - all repos are up to date and enabled. I even removed the KDE repo and added it again with a different priority but am still experiencing the same behaviour.
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 know that you can modify the nice value of a particular process as follows:renice 19 -p 4567However, now I would be interested to set the renice value of ALL active processes.I am coming from the Win world so what I tried warenice 19 -p *Of course it is not working... Anyone a quick solution how to do that in Linux?
I am trying to install the RPMForge Repository. I am following the instructions at : [URL]. After installing yum-priorities and *before* adding the RPMForge repository - I went into /etc/yum.repos.d/CentOS-Base.repo and added priority=1 to [extras] [updates] and [addons].
Then, when I run 'yum check-update' it says there are packages being excluded. I would have thought that before I had installed the 3rd party repo - that nothing should be excluded? Especially with everything set to the same priority. On a side note - this is a Xen VPS that we are renting... and the providors have commented out the [base] section (#[base])... I'm assuming this is is OK and is for my own protection.
I'm trying to install yum-priorities plugin on a 5.3 box. Reading the wiki, I understand that this packages is available in the Extras repository. I have Extras enabled in my Centos-Base.repo file. Here is the relevant section:
#additional packages that may be useful [extras] name=CentOS-$releasever - Extras mirrorlist=http://mirrorlist.centos.org/?release=$releasever&arch=$basearch&repo=extras #baseurl=http://mirror.centos.org/centos/$releasever/extras/$basearch/
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 2.6.32.2 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
Red Hat Desktop 5.5 I think I was successful in screwing up my yum configuration, I might have removed a few repo files too many. I wanted to add rpmforge to my repositories and wanted to install yum-priorities and it is telling me "No package yum-priorities available".
As I am sure it exists and my machine is not finding it it only leaves operator error/screw-up. What are the default repo files for Red Hat desktop and where can I get them?
Basically I'm looking for an application that can organize documents into groups and give priorities to certain documents. The reason is that I have so many documents I have to read and I just want to divide them into groups and give certain documents priorities over others so I can read them first and the rest later. For now, I'm using naming conventions such as 1_1stdoc.doc 2.2_seconddoc.pdf 2.4_thirddoc.pdf 2.45_4th.pdf 3_5th.pdf etc. Pretty sloppy isn't it? But it works. But it gets really tiring when the collection gets big... Does anyone know of an application that can do such thing?
I'm using several 3rd party repos for Centos - RPMforge, ATrpms, EPEL, REMI. Is there some way I can set the priorities for these repos in a bash script, using a YUM command? I cannot find anything in the YUM man page, or the yum-utils package.
Smart PM has a command to set channel priorities from the command line. Wondered if I can do the same for YUM repos?
it's possible to compile the 2.6.37 kernel patched with the autogroup patch on a Slackware 13.1 system running 2.6.33.4-smp with 2.6.33.4 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?
Now the issue is about the openSUSE 11.4 Updates repo (priority 99). It shows newer packages version than the KR46 repos for some packages, therefore I'm not sure if I have to push Updates repo up in priorities or just forget its update messages an keep the KDE repos as first source.
The latest release of VirtualBox (3.1.6) corrects most of the problems that I had with Slackware and KDE. If you have been avoiding VirtualBox or KDE because of those issues you might want to take another look.The only problem that I'm having now is that I have to click somewhere on the desktop to get a proper display when switching VirtualBox into "seamless" mode. The rest of the window display issues appear to be fixed and full screen mode also works correctly.
I got hold of the 3 cds needed to install full 32 bit Slackware 13.37 It installed perfectly and all is configured and running very smoothly. I have 4gb of RAM in my laptop so compiled the 2.6.38.4 kernel with PAE support and slackware sees 4gb of RAM. It will really be mission for me to get hold of the 64bit ISO as I do not have have uncapped bandwith (3g - UMTS).Will I really benefit by installing the 64bit version, and if so how?
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 (2.6.32.9). But audio on HDMI port doesn't work I tried alsaconf without success. HDMI sound works when i boot into the old kernel.
I have an Intel i7 with CentOS x64 installed, with the intention of using it as the host O/S with VMWare Workstation to run a number of virtual machines. I had this all working until the kernel was updated to 2.6.18-164.11.1.el5, Now I can no longer start any VMs. I have tried reinstalling CentOS, updating it first, then installing VMWare Workstation - no different. I have tried running as root - no different.
Is anyone else aware of this problem? Does anyone else run VMWare on CentOS x64?
