LinuxQuestions.org
View the Most Wanted LQ Wiki articles.
Go Back   LinuxQuestions.org > Forums > Linux Forums > Linux - Distributions > Slackware
User Name
Password
Slackware This Forum is for the discussion of Slackware Linux.

Notices



Reply
 
Search this Thread
Old 05-10-2007, 04:12 PM   #1
Zmyrgel
Senior Member
 
Registered: Dec 2005
Location: Finland
Distribution: Slackware, CentOS, RHEL, OpenBSD
Posts: 1,006

Rep: Reputation: 36
ipw3945 worries in slack


Just installed Slackware-current and installed the ipw3945 packages from Alien's repository. I build them with the Slackbuild.

Now when I try to load the module I get following:
Code:
root@Chimaera:/home/zmyrgel# modprobe ipw3945
WARNING: Error inserting firmware_class (/lib/modules/2.6.21.1-smp/kernel/drivers/base/firmware_class.ko): Invalid module format
Any idea what's causing that and how to get my wireless working?
 
Old 05-10-2007, 05:21 PM   #2
Tino27
Member
 
Registered: Aug 2003
Location: Akron, OH
Distribution: SuSE 8.2, Slackware current, OpenBSD 3.5-3.8, Fedora Core 2
Posts: 400

Rep: Reputation: 30
You have to make sure that the correct version of the firmware is installed for the driver module you are trying to load into the kernel. Did the packages you installed from Alien's repository also install the firmware, too? And, if so, did it put it in the correct spot (/lib/firmware, I believe)?
 
Old 05-10-2007, 05:30 PM   #3
erklaerbaer
Member
 
Registered: Mar 2006
Posts: 381

Rep: Reputation: 30
Quote:
NOTE TO USERS OF THE NON SMP KERNELS:

Sorry to shout. :-)

By default, the kernel in Slackware supports SMP. With as common as
multicore CPUs and SMP boards have become, this seemed like the
obvious choice. The kernels are probably better for single CPU
machines, too, if they will run them.

If you have to use one of the non SMP kernels (huge.s or generic.s),
then you will need to reconfigure your kernel sources to build any
additional kernel modules. In order to compile outside kernel
modules and such, you will need to build your kernel once with a
non-SMP .config. The process is much the same:

cat config-generic-2.6.21.1 > /usr/src/linux-2.6.21.1/.config

make oldconfig
make bzImage
make clean
rm .version

At this point if you are running huge.s or generic.s, you should have
no problems building kernel modules.

Have fun! :-)
config-generic-2.6.21.1 is in /boot
 
Old 05-11-2007, 02:05 AM   #4
Zmyrgel
Senior Member
 
Registered: Dec 2005
Location: Finland
Distribution: Slackware, CentOS, RHEL, OpenBSD
Posts: 1,006

Original Poster
Rep: Reputation: 36
I used the SMP-kernel so it basicly should have worked straight away but I got it working after I made a custom kernel... patched with Beyond-sources.

And now to get my hands dirty configuring the rest of the system with the aid of the internet
 
  


Reply


Thread Tools Search this Thread
Search this Thread:

Advanced Search

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

BB code is On
Smilies are On
[IMG] code is Off
HTML code is Off


Similar Threads
Thread Thread Starter Forum Replies Last Post
Slack 11 lilo -v worries bgeddy Slackware 3 10-18-2006 09:34 AM
Worries about updates okok Linux - Newbie 14 05-03-2006 04:33 AM
telnet worries dannyk1 Linux - Security 6 12-13-2004 02:36 AM
telnet worries dannyk1 Linux - Software 0 12-07-2004 06:02 AM
worries about upgrades wedgeworth Linux - Software 3 04-15-2004 12:03 PM


All times are GMT -5. The time now is 12:18 AM.

Main Menu
Advertisement
My LQ
Write for LQ
LinuxQuestions.org is looking for people interested in writing Editorials, Articles, Reviews, and more. If you'd like to contribute content, let us know.
Main Menu
Syndicate
RSS1  Latest Threads
RSS1  LQ News
Twitter: @linuxquestions
identi.ca: @linuxquestions
Facebook: linuxquestions Google+: linuxquestions
Open Source Consulting | Domain Registration