I 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 RepliesI would like to switch to Slackware but I know that generally there are problems with the Realtek 8188ce driver with certain flavors of Linux...this is my question. Is it possible to someway build the drivers needed for the wireless during installation so that I will be able to use it? I do not have access to a wired connection or I would just try to get it working that way.
View 6 Replies View RelatedI 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]...
Work I've got 2 slackware 13.1 64 machines, and they work just fine: Basic installation, everything ' bog standard 'When in Dolphin or Konqueror, I can ' click ' on Network Services and all the other MS Window machines pop-up.
@Home I've got 2 slackware 13.1 64 machines, they don't work fine. Basic installation, everything ' bog standard '. When in Dolphin or Konqueror, I can 'click' on Network Services and 'KDE has been build without Zeroconf support' pops up in Konqueror or is displayed in Dolpin..
Is it my netwerk @ Home (with an old Windows Server in it) or is something missing in the installation? Under MS windows (from within a virtualbox, brigded network) both machines can browse the network just perfectly: I even got a XP machine 'joined' in the domain on the windows server). Clueless since a google on the error + slackware give me Zero. Zeroconf in the slackware forum give me some midly related
I have just started to work with BeagleBoard and built the Linux kernel (version 2.6.30.5) and download to the board and it start. I have also connected to the board over serial to Putty terminal.
Now I want to connect to the Beagle Board using USB instead of serial and I am looking for some info on how to do this.
My goal would be to connect to board over USB and then be able to:
* Download my own binary files/programs from PC over USB to BeagleBoard
* Communicate over USB instead of UART/Putty to get log and execute commands
Question:
How do I build the Linux kernel with USB support, meaning what settings should be ticked in menuconfig? Or is it already included?
How do I enable USB OTG in menu config?
I assume I would need some driver on my PC with Windows XP to connect to my BeagleBoard over USB. Were can I find this USB driver?
config file for kernel compilation that will only contain the drivers for the current hardware that are needed for the running kernel?
i.e. I am not 100% sure which drivers I need to compile into the kernel but do not want to compile all of them for my laptop??
Whatever option i specify with ./configure, the summary says :
jack-audio-connection-kit 0.118.0 :
| Build with ALSA support............................... : false
i tried --enable-alsa without success.
My openSUSE 11.2 system has periodic running of fsck disabled for ext4 filesystems (Maximum mount count = -1, Check interval = 0). What is the reason for this? Is it because fsck is not necessary on a periodic basis with ext4, and only necessary when errors are detected? Or is it because fsck has problems working on ext4 filesystems?
The ext3 filesystems do have it set (Maximum mount count = 500, Check interval = 5184000 (2 months)). I would like to know why fsck is not set to be activated for ext4.
I'm building my slackware system from a minimal set of packages. I've got X and fluxbox up and running, and I'm trying to "slack-build" feh which depends on imlib2 to set background wallpapers. The problem is trying to "feh" any image gives the error message:
Code:
feh WARNING: wall2.jpg - No Imlib2 loader for that file format
feh - No loadable images specified.
[code]...
running 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].....
My 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 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'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 Replies View RelatedI 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 use Slackware 13.37 32-bit version on ThinkPad X60s. I compiled two Window Maker dockable applications monitoring the processor temperature, fan speed, and battery status: wmpower (see: [URL]) and wmlenovo (see: [URL]). Both these applications refuse to work.
wmpower displays the messages:
Code:
CPU frequency scaling available
No power management subsystem detected
No power management support...
wmlenovo displays the message:
Code:
No ACPI support in kernel
Did I missed something obvious during the configuration of the system and ACPI doesn't work for me or there's some more serious problem with my system?
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.
View 4 Replies View RelatedI 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 RelatedOMG I think I have installed every MP3 player known Amorak Audacious, Bluemindo, rhythmbox, kaffiene, Listen, VL, CPlay and more. They all require a cpu supporting SSE. This isn't an audio issue it is a graphic issue.
Does anybody know an mp3 player that will run without these graphic issues?
Ubuntu 9.1 800MHZ AMD Duron (with NO SSE)(slot A with a 100mhz bus)
When I try to create a network tunnel, I get ioctl: no such device returned by the terminal. Which modules do I need to ad with insmod to enable tunneling?
View 2 Replies View RelatedTrying 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.
The alternative and minimal installation images do not contain drivers for my EeePC 1101HA's network devices. The module required for the ethernet is atl1c (Atheron AR8132), but the discs contain only atl1 and atl1e. What can I do to install it?
I dug the .ko file out of the live CD (which works fine) and tried to modprobe it in the alternative installer's environment (minimal won't let me mount any storage devices), but modprobe wouldn't accept it as a module. So I gather there's a missing step somewhere.
Also, the alternative image is choking on an error, "Debootstrap error: Failed to determine the codename for the release." So I can't even install from a mounted ISO and figure out how to install the driver on the otherwise working system.
How do I make this work? I'd really like to build an Ubuntu system from the ground up instead of relying on the ready-made desktop live CD.
This is driving me mad, so bear with me. I'm not sure this is a Slackware issue, in fact I'm sure it's not, but you all have helped me in the past so it seems like a good place to start. Also, I don't really know exactly how much of this information will be completely relevant to my problem, but I really can't pin it down.My server is running 64 bit Slackware 13. It was running fine, mainly just serving files on the LAN, with some occasional SSH activity. I was slowly moving hard drives to it from my desktop system (all 1 or 2 terabyte drives). They were previously formatted with NTFS and were filled with files, so it took me a while to move data around, format a drive, and copy the data back. I decided to use ext4, for no particular reason other than it was the newest, so if I end up having to reformat these again, I'm open to using another filesystem. Right now, I've got two 2TB drives and three 1TB drives, but one of those is still NTFS, so it is of no concern at the moment.
At this point, I had just added the two 2TB drives to the system. These happened to be the new WD Advanced Format drives with 4k sectors. I found a way to manipulate fdisk so it would start the partition on the correct cylinder or whatever to take advantage of the new format. I also ended up using GPT instead of MBR because it had more usable space.
two 2TB drives, GPT, ext4, 4k sectors
two 1TB drives, GPT, ext4
one 1TB drive, MBR, NTFS (not important)
This setup was working fine for a few days until I had to take the server down to move some wires around. When I booted the server back up, I discovered the two 2TB drives were missing. They showed up in /dev but wouldn't mount.
I'm trying to find out when QME2572 (Qlogic) card became support by the kernel. We have a RHEL 5.1 system that is moving to new hardware, however the kernel at this release doesn't support the new hardware, due to the Qlogic card change. I tired the Redhat KB and Bugzilla. Is there a Kernel change list etc I can search. Never really played around with the kernel too much so I'm just after some pointers for looking up this information. Offically its not supported until Redhat 5.3, I'm trying trying to research kernel info so I can tell the customer they have to upgrade.
View 3 Replies View RelatedI would like to compile my own kernel. I am familiar with how to do it and have done it in the past so I'm not looking for a how to compile a kernel. In the kernel config are many, many options. In the past when I compiled kernels I always wondered about what is needed and used. What is the best way to determine what is currently used, not set or enabled in the existing config, but actually used by my existing kernel?I have a general idea of what is loaded and could do trial and error, turn this and that off, recompile, etc but is there an easier way?
View 3 Replies View RelatedAs in the title how can I do it? The configure option --enable-so seems default.
View 4 Replies View RelatedI am using the Debian stock kernel. I want a minimal kernel that works on my Pentium 4, 1GB DDR RAM machine. What do I have do to get a less resource hungry OS. Is there already a minimal kernel binary available?
View 2 Replies View RelatedI'm taking a class this semester on Linux and a Fedora 13 DVD came with the book. Just now I've installed Fedora at home and started the updates. I saw a PAE entry in the updates so I went to the Terminal and typed uname -r and I see that the Fedora 13 DVD installed a PAE kernel on my machine that has only 1 GB of RAM.
Why did it do that?
Can I swap out the PAE kernel for a non-PAE kernel? (edit- I'm a Linux noob so I don't know)
Does it really matter?
After the updates I was going to try to install the proprietary Nvidia driver.
Sorry if it is a dumb question (i'm coming from deb/ubuntu and i'm totally new to rpm - installed Smeegol on a Samsung N150). After some try&error i finally got my Broadcom4313 working but underway to that i got lots of new kernels and now i don't understand not so much anymore.
I think the kernel default-devel it was me installing it using the distribution manager to get working make (for trying to install the original Broadcom driver package; i stopped that attempt because i didn't where exactly to move/cp the built driver).