LinuxQuestions.org
Share your knowledge at the LQ Wiki.
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 02-16-2003, 12:57 AM   #1
slackfan
LQ Newbie
 
Registered: Jan 2003
Distribution: slackware
Posts: 20

Rep: Reputation: 0
pcmcia not in 2.4.20 source tree?


Greetings,
Originally had pcmcia / orinoco support compiled in the driver... with 2.4.20 (everything was working great with pcmcia and wifi) and recently decided to use as modules so during recompiliation in xconfig I changed from compiling in kernel to use in modules:
[PCMCIA/ Cardbus support]
Hermes chipset 802.11b support
[Wireless PCMCIA Cards support]
Hermes PCMCIA card support

[PCMCIA network device support]
NE2000 compatible PCMCIA support
AT&T / Lucent / Waveland wireless support

during make zimage/ bzImage
it errors out with
"ld: cannot open drivers/char/pcmcia/pcmcia_char.o"
"make: *** [vmlinux] Error 1"


... is this because in xconfig I said yes to PCMCIA wireless lan ?
I did a search on google and I have read of buggy source trees, though 2.4.20 is said to be stable so I am guessing it something I am crossing in xconfig...

I even rm'd my current /usr/src/linux source tree and downloaded a new one from kernel.org decompressed and rebuilt and got the same error...

Thanks for your help I will update if I find something along the way...
 
Old 02-16-2003, 09:05 AM   #2
Excalibur
Senior Member
 
Registered: Jun 2002
Location: Northern VA, USA
Distribution: Ubuntu
Posts: 1,180

Rep: Reputation: 46
I have seen similar problems with other drivers I have attempted to enable, either kernel build or as modules. I reviewed the makefile for the object file in question and the source files are present for the 2.4.20 kernel. It has been my experience that the make system is not processing the directory. In your case, since it is the drivers/char/pcmcia device tree, it is most likely something else needs to be enabled to process the parent directory (drivers/char). So you might try enabling some generic devices that are not specificly pcmcia related, like the Generic/Standard serial device support.

Hope it helps.
 
Old 02-16-2003, 02:47 PM   #3
slackfan
LQ Newbie
 
Registered: Jan 2003
Distribution: slackware
Posts: 20

Original Poster
Rep: Reputation: 0
Thanks again Excalibur!
Last night I read something somewhat similar here:
http://www.uwsg.iu.edu/hypermail/lin...01.0/1233.html
Quote:
On Sat, 6 Jan 2001, Jochen Friedrich wrote:


> Hi,
>
> problem is that CONFIG_PCMCIA_NETCARD=y, although all drivers are
> compiled as modules, so there's no drivers/net/pcmcia/pcmcia_net.o...


This should fix it.


--- drivers/net/Makefile% Fri Jan 5 15:10:11 2001
+++ drivers/net/Makefile Sat Jan 6 23:48:28 2001
@@ -26,7 +26,7 @@
obj-$(CONFIG_ISDN) += slhc.o
endif


-subdir-$(CONFIG_PCMCIA) += pcmcia
+subdir-$(CONFIG_NET_PCMCIA) += pcmcia
subdir-$(CONFIG_TULIP) += tulip
subdir-$(CONFIG_IRDA) += irda
subdir-$(CONFIG_TR) += tokenring


The problem is that CONFIG_PCMCIA is M, therefore drivers/net/pcmcia is
not entered during "make vmlinux". The patch fixes this and will produce
an (empty) pcmcia_net.o


And, yes, the directory will also be entered when doing "make modules",
because pcmcia is in $(mod-subdirs).
I will fiddle more with xconfig and try out these suggestions, and will of course post any positive findings.
 
Old 02-16-2003, 03:09 PM   #4
Excalibur
Senior Member
 
Registered: Jun 2002
Location: Northern VA, USA
Distribution: Ubuntu
Posts: 1,180

Rep: Reputation: 46
If I am understanding the context of what you posted corectly, then the issue could be that pcmcia support and all pcmcia devices will need to be module or kernel built. But not some of both. Makes sense, but kind of difficult when changing. The pcmcia devices are spread out all through the kernel config. In addition to the parent device support might also be modules or kernel built as well.

My experience was mainly with scsi support drivers, but I didn't think modules had anything to do with the issue because I had disabled modules.

Good luck, gives me a headache trying to comprehend it. Sounds like kernel builds may be hit or miss for a while.
 
Old 02-17-2003, 12:16 AM   #5
slackfan
LQ Newbie
 
Registered: Jan 2003
Distribution: slackware
Posts: 20

Original Poster
Rep: Reputation: 0
ok we are looking good now

Ok after beating my head for half a Sunday on this I have come to a pleasant resolve

1] I created a config file (with make xconfig) that had NO pcmcia support

2 I recompiled the kernel successfully without pcmcia support, where previously it was not compiling because I was trying to modularize the pcmcia support.

3 I created a config file based off 1's config file (noted above) and just added PCMCIA support modularized and nothing more, saved config file and recompiled the kernel... success no errors at all!

4 I noticed that I was previously not running make modules_install in my kernel compiliation process thus I was missing /lib/modules/2.4.20 which was no good for me in what I needed to do in patching the modules... so I added this step after searching more of the forums (this step was not documented in the slack essentials book online at slackware.com, nor in the oreilly's running linux ... so now my kernel compiliation process looks like this::::

a. cd /usr/src/linux
b. make mrproper
c. make xconfig (x rocks)
d. make dep
e. make clean
f. make zImage (always hoping to have a smaller kernel)
g. make bzImage (because my kernel is too big)
h. make modules
i. make modules_install

then i have created a test.bsh since i seem to be compiling the kernel at least around 20 times a day in my current experimental stage ... which is:
Code:
#!/bin/bash
# slackfan's lazy script
# i have already ln -s config-test config
cp /usr/src/linux/.config /boot/config-test
# i have already ln -s System.map-test System.map
cp /usr/src/linux/System.map /boot/System.map-test
#
cp /usr/src/linux/arch/i386/boot/bzImage /boot/bzImage-test
# I already /etc/lilo.config  image = /boot/bzImage-test
# and have it optional 
lilo -v 
# end
... so now i feel this issue has been resolved!!! Thanks again Excalibur, hopefully my information will help others that travel this path!
 
  


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
how to integrate driver source into kernel source tree zhchang Linux - Software 5 11-23-2005 12:34 AM
where is linux source build directory/kernel source tree? webazoid Linux - Software 2 07-01-2004 08:37 PM
no kernel source tree?? adambeazley Linux - Wireless Networking 3 04-22-2004 05:25 PM
/usr/source/ missing source tree swingert Linux - Newbie 2 07-19-2003 08:48 PM
Source tree appler Slackware 2 06-20-2003 12:20 PM

LinuxQuestions.org > Forums > Linux Forums > Linux - Distributions > Slackware

All times are GMT -5. The time now is 08:28 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
Open Source Consulting | Domain Registration