I'm running Slack64 13.1 and I'm in good shape with the 33.4 kernel, but if I upgrade the kernel to 35.x what do I need to do to get it working with my Nvidia 7300GT? I have the nvidia installer, NVIDIA-Linux-x86_64-260.19.12.run. Do I just do from the stable repo
Code: slackpkg upgrade then boot to run level 3 and run NVIDIA-Linux-x86_64-260.19.12.run? Thanks for your help.
According to security manual i need to incorporate following changes into kernal parameter but i m not sure when and how these changes will be implemented.
Code:
net.ipv4.conf.all.accept_source_route must be set to "0" net.ipv4.ip_forward must be set to "0" (zero) icmp_echo_ignore_broadcasts must be set to "1" net.ipv4.tcp_syncookies must be set to "1"
I have not dug into Ubuntu for almost a year now (Since Jaunty, really). I am trying to come to grips with Grub2, but have just now encountered it in Lucid. I am having a terrible time with the graphics chipset, and it may well be that Ubuntu cannot be used on this computer (an older laptop with the dreaded Intel 82845G graphics chip). There are a number of older bug reports that it is unsupported, but some success in more recent versions.
Anyway, one suggestion has been to add i915.nomodset=1 to the kernel boot line. Now, this was a cinch in Legacy Grub, but I have been reading Grub2 wikis and tutorials for two days now, and I know about the config files, but I cannot find anything which tells me specifically how to add a parameter to the kernel boot line.
I recently enabled noapic on my laptop because it was experiencing strange input freezes on several distros that I tried.Ok, so it does not use the ioapics. My question is, what does this mean for the system? If it used apics before, what happens now? I am a freshly graduated computer science major, and I have worked with basics pics on projects before, but I am curious how this effects the running system.
I have a "Chicony 1.3M UVC Webcam (Asus G1S notebooks)" webcam, which is supported by Linux UVC [1]. However I'm unable to find the kernel parameter that I should select to compile my kernel to support this device.
Is there any Kernel parameter available for interrupts handling, In the case of busy server how we can tune the kernel to handle interrupts effectively.
It's documented in the howto's that you need to have the nomodeset kernel parameter specified if you want to run the proprietary Nvidia driver. But I read in certain posts that this is only required for "older" graphics cards.Can someone shed some light on this? Is the parameter ALWAYS required when running the nvidia driver, or only for certain graphic cards?
I've done the usual edit of /etc/sysctl.conf to include the parameter, but it just tosses errors. I haven't had to tune a kernel in a very long time, what's different about it nowadays (or have I simply forgotten how)?
edit: Added "kernel.semmni = 2048" to the tail of /etc/sysctl.conf and then ran "sysctl -p". End result is an unknown key error (apparently kernel.semmni isn't the valid name anymore?).
Hey,everyone! I've got Ubuntu 10.10 , when loading I see the following message: "atk: Resources not safely usable due to acpi_enforce_resources kernel parameter" What does it mean and do I need to fix it?
I am trying to do a fsck on my ext3 partition, but so far failed to let the system come up in single user mode and having the partition mounted read only. It says in the kernel parameter that it is read only (RO) but still mounts it RW. A remount with mount -o remount,ro does not work, since / is always busy. what to do to get a fsck done? I don't want to boot into a rescue system, this should be possible on a running system (like Windows does it, when rebooting)
I'm trying to install Oracle DB on OpenSuse (is it smart, because it's not certified for that OS?)..and I've set oracle parameters using oracle script, but when I'm runnign through oracle installation, kernel parameters check reports that parametersa are 'n/a', like oracle OS account cannot access those parameters..
After setting the "nomodeset" kernel parameter, to install the nVidia proprietary driver in OpenSuSE 11.3 (I need to do CUDA development), my Sansa Clip+ is no longer recognized. When I turn the "nomodeset" option off, I can see it with $(fdisk -l).
I have an issue that is fixed by changing the lpfc driver to run using MSI interrupts. This is done by adding "options lpfc lpfc_use_msi=2" /etc/modprobe.conf.local file.
Is there a way to make this change using kernel boot parameters?
I got the following modprobe scripts modprobe -k -q streams what does the -k parameter mean?. is it exist in older modprobe? I don't see -k parameter in recent modprobe.
I'm finally getting around to configuring my Xfce desktop environment and I'm having a lot of trouble having applications remember their last position. I did some Googling and found this is either not a supported feature or it depends on the application if they want to support it or not.
I'm trying to make my default terminal start in the center of the screen.
I found that you can add the command line parameter
Code:
For example and it should open at a 70x20 size in the 20+30 position. I added that to my panel launcher's command and ended up with
Code:
However the terminal isn't opening at all.
After further reading, I discovered the default launchers use your preferred applications so I just used replaced the launch command with the following and it worked perfectly:
I'm looking for recommendations on how to increase the nofile limit for a daemon running as other than root. Does anyone else do this? It'd be nice if I could employ /etc/security/limits.conf.
I'm on a CentOS server and for the past hours I have been trying to unsuccessfully make a script that will start a binary and keep it running if anything goes wrong with it.
Hybernate does not work on my laptop. I receive the following error in the log: Running hook /usr/lib/pm-utils/sleep.d/30s2disk-check hibernate hibernate:
INFO: checking for suspend-to-disk prerequisites... ERROR: no resume parameter on kernel commandline, can not suspend
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 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
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?
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.