I'm building an i7 based machine and I've been looking at kernel optimizations for it. One kernel option that I'm sketchy on and haven't been able to find a good resource for is for MAXIMUM NUMA NODES. The default is 6, but I'm not sure if this is best for my particular hardware or not and I'm not exactly sure what this is all about.
View 6 RepliesMy main computer (HP Pavilion 510n) only allows 512 meg ram.I've never built a kernel for Slackware.I'm running 13.0 :2.6.29.6 #1 Mon Dec 7 16:34:06 CST 2009 i686 Intel(R) Celeron(TM)CPU 1200MHz GenuineIntel GNU/Linux.Would there be any advantage to build a new kernel for 512 megs ram maximum? I do basic stuff with this: browse, email, video clips, music.
View 5 Replies View RelatedI use Slackware 13.0. I just upgraded from 2.6.32 to 2.6.35. On 2.6.35, the kernel supplying strange non-existant node like hda* and many symlink like cdr cdr0 cdrom cdrom0 etc. Well, i use libata and disable the old ATA driver, so my HDD should only be displayed as sd**. Also, i've checked all the udev rules, and i don't see any SYMLINK entries that would produce that cdr cdr0 links. My 2.6.32 and 2.6.35 config are identical. Everything were working normally on 2.6.32. Btw, i've tried to upgrade to 13.1. Then boot the standard huge.smp kernel. The same problem occured too. And with other problem i get with 13.1, i decided to downgrade to 13.0.
View 2 Replies View Relatedrunning current on a Lenovo S10
the b43 driver craps out every few minutes.
so i decided to try the sta driver.
i downloaded the slackbuild but it crashes with the following see attached
I am using the 13.1 build scripts from slackbuilds.org. I modified the scripts to build 3.2.12 rather than 3.2.10.
In 13.1 the main VirtualBox 3.2.12 OSE package built and installed without errors. The VirtualBox GUI starts without errors.
Running the virtualbox-kernel-mksrctarball.sh script built a kernel source package without errors.
Yet the VirtualBox kernel module won't build. I receive the following error:
Code:
]*** Building 'vboxdrv' module ***
make[1]: Entering directory `/dev/shm/virtualbox-kernel-3.2.12/vboxdrv'
make KBUILD_VERBOSE= -C /lib/modules/2.6.33.11-smp-2/build SUBDIRS=/dev/shm/virtualbox-kernel-3.2.12/vboxdrv SRCROOT=/dev/shm/virtualbox-kernel-3.2.12/vboxdrv modules
[Code].....
I am working with linux-source-2.6.30 from squeeze.
The only changes I made in the config file were the processor type, and I disabled CONFIG_SYSFS_DEPRECATED_V2 to avoid some warnings from udev.
When I tried to build the kernel package, this is what I get:
(The bottom bit is from 'time').
Searching for this error turned up a plethora of results, none of which seemed relevant.
I see that it tells me to file a bug report, but I'm not sure if that is meant for the Debian kernel team or upstream.
I used make-kpkg to build the 3.0.0 source debian wheezy on a dual 3.4GHz Xeon/L1-16k/L2-1mb/800Mhz bus with 4GB PC2-3200 ECC ram and Ultra 320 SCSI, using CONCURRENCY_LEVEL=4 (2 hyperthreading cpus=4 cores). The build was slower than molasses in January! Top reported cpu usage total between 10% and 25%. Why won't the build use the amount of machine it has available. One footnote: I wasn't using swap space. It literally took over an hour to build the deb kernel package.
My notebook from 2003 is at least three times faster building the 3.0.0 debian kernel source. Is it possible that this might cause improvement: make -j4 KDEB_PKGVERSION=version deb-pkg
over
CONCURRENCY_LEVEL=4 make-kpkg --initrd --revision=123x kernel_image?
Could amd64 vs. i386 have some influence? Could the small processor caches on the XEON cpus have an effect. The 64-bit machine absolutely flies doing everything else. I'm miffed! I've used debian since woody, although I am not an expert, but I'm no slouch!
I had an issue with the module build for vbox 3.1.2 breaking on the latest kernel ( /etc/rc.d/rc.vboxdrv setup ). Apparently the issue is that a kernel header (autoconf.h ) has changed its location in the module tree and hence the issue.
2 options:
1. upgrade to 3.1.4
2. create a symlink as follows
cd /usr/src/linux/include/linux
ln -s ../generated/autoconf.h autoconf.h
If others are have the problem of VirtualBox failing to build the kernel modules with kernel 2.6.32 try this :-
1. Install VirtualBox and watch as the kernel modules fail to compile.
2. Change the line
Code:
KFLAGS += -DRT_ARCH_AMD64
TO
Code:
KFLAGS += -DRT_ARCH_X86_64
In the following files :-
Code:
Line 231 /opt/VirtualBox/src/vboxdrv/Makefile
Line 170 /opt/VirtualBox/src/vboxnetadp/Makefile
Line 174 /opt/VirtualBox/src/vboxnetflt/Makefile
3. Run /etc/rc.d/rc.vboxdrv setup
You will now have a working VirtualBox setup. NB This is written purely from the standpoint of using the Closed source version of VB not the OSE version.
I started slax in cli mode and tried to install nvidia driver before running X but it won't install. My log:
Code:
nvidia-installer log file '/var/log/nvidia-installer.log'
creation time: Sun Jan 10 04:21:14 2010
option status:
license pre-accepted : false
Update : false
Force update : false
Expert : false
uninstall : false
Driver info : false ....
ERROR: Unable to build the NVIDIA kernel module.
ERROR: Installation has failed. Please see the file '/var/log/nvidia-installer.log' for details.
I just rebuild the kernel for slackware 13, everything works, but root file system which is ext3 is mounted as ext2. Normally I've build ext3, ext4 and so on as modules, not in the kernel... but if I do this, then the kernel mounts the file system as ext2, which is build in the kernel. I also modified rc.modules so I can make sure that ext3,ext4,jbd are loaded, but it doesnt work.
View 2 Replies View RelatedI am building a minimized 6.2.2 linux kernel using slackware on a dinosaur of a computer: AMD Athlon +1700 Single Core processor, 1gig of DDR SDRAM. This is my first time compiling a linux kernel, so before I make any major mistakes, I could use some help in determining which filesystems I absolutely must enable support for. Ext2 is allready in.
View 4 Replies View RelatedAre there any prerequisites which much be met in order for udev to create /dev/usb/hiddev* nodes?
I have two Slack 13.0 systems, each connected to a APC UPS via USB, one of which creates a hiddev0 node and the other doesn't. apcupsd can't find the UPS unless this node is present.
The "working" system has been stable in its current configuration for so long that I honestly can't remember if I had to tweak anything in this regard. I've verified that it doesn't use any local udev rules to create this node, and to the best of my knowledge there are no external scripts or processes which would create it either.
The non-working system has a similar configuration - no local rules and/or scripts which touch usb devices or nodes.
Trying to install SW 13.1 (on DVD) on the following system: M/B Intel: DX38BT Processor Intel Core 2 Quad Q6700 - 2.66GHz, 8MB Cache, 1066MHz FSB, Socket 775 Memory Corsair Dual Channel 8192MB PC10600 DDR3 1333MHz Memory (4x2048MB) Graphics Diamond Radeon HD 3850 Video Card - Viper, 512MB GDDR3, PCI Express 2.0 P/S Ultra 1000W
My goal is to install the i386 build on one partition and the 64-bit build on another. I have been away from Linux for a while and am sick to death of Win7, want to come home. :-}
Booted on i386 side of DVD, system freezes after a couple of lines that start with ATA2. Does not respond to 3 finger salute, ctrl-c, nothing. Have to press reset. I have tried both huge.s and hugesmp.s kernels
Booted on 64-bit side, comes up fine. I performed the install, selected for automatic lilo install. Lilo install hung but I was able to reboot. I booted off the 64-bit side again, entered the following: huge.s root=/dev/sde3 rdinit= ro It booted fully to the login prompt but the keyboard does not work, no input.
I have gone through all the kernel config options repeatedly, but everytime I get the same error after running my configured kernel.
To begin with, after unpacking the kernel I get Undefined video mode numer: 305 and then a selection of video modes appears.
Why are the standard settings in my lilo 1024x768x256 (vga 773) not accepted?
VFS: Cannot open root device "808" or unknown block(8,8) Please append a correct "root"=" boot option; here are the available partitions: Kernel panic- not syncing :VFS: Unable to mount root fs on unknown block(8,8)
My partitions are ext2, and this format (as well as other formats) are compiled in the kernel.
I recently did a fresh install of current and once I had it up and running I compiled a fresh 2.6.33 kernel using my old config file, but now I get this warning durning boot, specifically during module loading WARNING: All config files need .conf: /etc/modprobe.d/sound, it will be ignored in a future release. This doesn't seem to be causing any problems but I am curious to know what the message meams? I checked /etc/modprobe but everything looks normal.
View 1 Replies View RelatedThe login screen is always at maximum screen resolution, how can i change this?
View 2 Replies View RelatedWhat is the maximum number of virtual network interfaces possible?I would like to create around 300 or so. This is needed to simulate a 300 node network.
View 6 Replies View RelatedI have done nothing with the system, but starting this morning, i experienced a strange condition on my desktop. I'm unable to open any applications at all. It will close instantly.
When i tried to run from terminal, it will give me an error like this:
Quote:
I checked using
Code:
And i got around 234 which is too much that it takes almost all of the open files allowed. Logging out to text and brings back X will solve the problem, but it's only a temporary solution until X opens more sockets again. I'm running -Current (32 bit)
It seems that there's a hackish solution in here: [url]. Dunno whether it's a nice solution or not, but i'm willing to try it.
I've got 4 identical 1 TB drives and would like to use them in a software RAID configuration on my home server. I'm running Debian Linux using 'mdadm' utility to manage the software RAID. I don't know how much I've read is fact or dated or even false so I decided I would ask here to get help from people who know more about this than I do. This is essentially just a file server machine to store all my data so being that I've got four identical SATA hard drives, I was thinking about doing RAID level 5. I guess I'll start here and ask if that is the recommended level of RAID. I think RAID level 5 will be fine for my general server usage. My second issue is partitioning the four individual drives to get maximum performance / space from them. Basically just asking here how would you or you recommend I partition the drives? I was thinking about doing three seperate partitions per drive:
/dev/sda1 = 4 GB (swap)/dev/sda2 = 1 GB (/boot)/dev/sda3 = 995 GB (/Now from that partition schema above, obviously all the types will be 'fd' for RAID and the partition for /boot is going to be bootable. My confusion is that I read Grub doesn't support booting from RAID 5 since Grub can't handle disk assembly. If /dev/sdx2 (sda2, sdb2, sdc2, sdd2) are partitioned for /boot (bootable), how would you guys configure this RAID to match up equally? I don't think I do a RAID level 1 on 4 identical partitions, right?
I use rtorrent in slackware. I already tried to use deluge 1.2.3 and even 1.3rc1 and 1.3rc2 but I find them a little unstable. Witch is your favorite? For lot of torrents and maximum encryption?
View 14 Replies View RelatedWhen I run ardour sound editing I get this message , but it starts ok Your system has a limit for maximum amount of locked memory! This might cause Ardour to run out of memory before your system runs out of memory. You can view the memory limit with 'ulimit -l', and it is normally controlled by /etc/security/limits.conf
bash-4.1$ ulimit -l
64
my limits.conf is like this
audio - rtprio 99
@audio - memlock 250000
[Code]...
I downloaded from http://ftp.nluug.nl/os/Linux/distr/s...ce/n/net-snmp/ source and I build new package and works ok no errors. If I change net-snmp.SlackBuild and add CFLAGS --with-mib-modules=ucd-snmp/lmSensors --with-ldflags=-lsensors while I need lmsensors support in net-snmp. But the package compiling ends with error:
[Code]...
I tried to build several packages designed for slackware 13 at slackbuilds. Those was a simple apps like ardour, audacity for example.
[Code]...
My CPU is AMD Phenom 9550 Quad core. It supports 64 bit. My os is slackware 13_64. What do I need to change in slackbuild to create a txz package for those apps?
I'm trying to install slackware 32 bit 13.1.After loading kernel it asks for keyboard configuration, but keyboard (usb wireless) doesn't work.
Keyboard works on the old 13.0 installation, on bios and also in the boot options of 13.1 installation cd.
I've tried removing legacy usb support and changing usb2.0 speed from high to full. Nothing changed.
Anybody with this strange problem? (kernel of setup seems also to detect it correctly as a trust keyboard).
I am trying to compile the kernel version 2.6.20-15 on my Linux 10.10 with 2.6.35-22 kernel. Additionally, this is my assignment.After I download kernel, extract it and create a new .config file for the new kernel I am trying to command;make-kpkg clean fakeroot make-kpkg --initrd --append-to-version=-custom kernel_image kernel_headers.after the second command I get an error an it says "nothing to be done" but I expect to have some .deb files for the new kernel. In addition this I have added a new system call to the kernel 2.6.20-15.
View 1 Replies View RelatedI will like to build a Linux Kernel, how easy is it to build one?
View 9 Replies View Relatedmy server are acting weird, how to build a new kernel ?
View 8 Replies View Relatedthe correct way to remove custom kernels? I was trying to install a driver and only got it half way right and I want to wipe the slate clean and try again.Here's the original:Debian GNU/Linux, kernel 2.6.26-2-amd64root(hd0,4)kernel/boot/vmlinuz-2.6.26-2-amd64 root=UUID=64dcc531-f5b0-47e8-99c4-abeecfab9353 ro quietinitrd/boot/initrd.img-2.6.26-2-amd64
View 2 Replies View RelatedJust like title.can i disable mmu, and build it? how to do that?
View 4 Replies View Related