niXforums Forum Index
 FAQFAQ   SearchSearch   MemberlistMemberlist   UsergroupsUsergroups   RegisterRegister 
 ProfileProfile   PreferencesPreferences   Log in to check your private messagesLog in to check your private messages   Log inLog in 
·  nixdoc.net ·  man pages ·  Linux HOWTOs ·  FreeBSD Tips ·  Forums
navigation Forum index » *nix » Linux » Setup
unresolved symbols and other problems
Post new topic   Reply to topic Page 2 of 2 [22 Posts] View previous topic :: View next topic
Goto page:  Previous  1, 2
Author Message
chuck@nil.car
*nix forums Guru Wannabe


Joined: 23 Aug 2005
Posts: 100

PostPosted: Wed Jul 12, 2006 10:47 pm    Post subject: Re: unresolved symbols and other problems Reply with quote

Unruh <unruh-spam@physics.ubc.ca> wrote in
news:e91iol$1t2$1@nntp.itservices.ubc.ca:

Quote:
chuckcar <chuck@nil.car> writes:

Unruh <unruh-spam@physics.ubc.ca> wrote in
news:e919rt$sfj$3@nntp.itservices.ubc.ca:

Norman Elliott <nelliott@uklinux.net> writes:

chuckcar wrote:
Norman Elliott <nelliott@uklinux.net> wrote in
news:12b4h6fm9866o05@corp.supernews.com:


Hi,
I have posted similar messages to this this in several groups as I
haven't a clue as to what exactly is causing the problem.

I have an old laptop - Fujitsu Lifebook 780Tx which I want to use
as an X terminal to my main PC.
It came with win98 on it an I shrank it to about 1Gig ( the disc
is 3.2Gig ) and installed vector 5.1 standard ( a slackware based
small distro ) It gives me to choice of kernel 2.4.29 and 2.6.12
at boot up.

Now if I boot the 2.4.29 kernel then X starts okay and I can use
it with icewm but I cannot use my pcmcia network card an Asus
WL-107G so I cannot access my main PC.

Before setting up with ndiswrapper I run depmod -a I and get a
series of 'unresolved symbols' errors relating to wlan.o,
wlan_acl.o etc ath_hal ath_pci.o etc so don't set up the driver
with ndiswrapper.

I downloaded the 2.4.29 source and compiled it and ran

make clean && make dep && make && make modules && make
modules_install but it still complains.

If I boot the 2.6.12 kernel I get no unresolved symbol errors so I
can use the network card with ndiswrapper

but if I start X then the mouse goes crazy and menu's appear and
disappear at will. so it is unusable.

I am running version 6.8.2 of X and trying to use the same
xorg.conf file in each case.

I would prefer to use 2.6.12 but 2.4.29 would be fine if I can
have network and X

So, the problem you have is a mouse problem. What kind of "mouse"
(touchpad, jogglestick) do you have?
Check to see if it was correctly recognised by the setup routing in
/etc/X11/xorg.conf.
Or buy a usb mouse and use that instead.


How do you propose for a mouse not recognised by the kernel be
recognised by X? That's like trying to print a test page to a parallel
port printer when your computer has no parallel port!


What he said was
"but if I start X then the mouse goes crazy and menu's appear and
disappear at will. so it is unusable."

so the mouse is recognised but unuseable. It is the mouse problem that
needs to be solved, not a kernel recompile.
So, first we need to know what kind of mouse he has. Then perhaps
solutions can be found. Recompiling a kernel to fix a mouse problem is
the last thing he should do. And most distros come with almost all
mouse drivers the kernel can carry anyway, simply because they do not
want the user to find the distro unseable because the mouse does not
work.

Just recompiling the kernel with no idea as to what needs to be fixed
is not a good idea.



--
(setq (chuck nil) car(chuck) )

The problem *resulted* from *compiling* the kernel in the *first* place.
Re-read the OP if you even give a hoot STEVE.

--
(setq (chuck nil) car(chuck) )
Back to top
Norman Elliott
*nix forums beginner


Joined: 17 Jun 2006
Posts: 21

PostPosted: Thu Jul 13, 2006 7:40 am    Post subject: Re: unresolved symbols and other problems Reply with quote

chuckcar wrote:
Quote:

Now if I boot the 2.4.29 kernel then X starts okay and I can use it
with icewm but I cannot use my pcmcia network card an Asus WL-107G so
I cannot access my main PC.

Before setting up with ndiswrapper I run depmod -a I and get a series
of 'unresolved symbols' errors relating to wlan.o, wlan_acl.o etc
ath_hal ath_pci.o etc so don't set up the driver with ndiswrapper.

I downloaded the 2.4.29 source and compiled it and ran

make clean && make dep && make && make modules && make
modules_install but it still complains.

If I boot the 2.6.12 kernel I get no unresolved symbol errors so I
can use the network card with ndiswrapper

Get a copy of the kernel howto from

http://tldp.org/HOWTO/Kernel-HOWTO/index.html

1. cd /usr/src/linux-2.6.12
2. cp .config /root - just to be safe file is probably junk
3. make mrproper
4. make menuconfig

go through every submenu here (you don't have to use the mouse you can
use the arrow, tab and enter keys.) You *do* have to know what hardware
you have on your computer - read: video card, sound card modem. Any
problems reply to me. Ignore unruh *completely* or it will get worse -
trust me, he's been trolling me for 6 months now and he changes his
handle all the time.


Well I don't have time to do any of this just now as I have to catch a boat to the

mainland and will be away for 1 week but just to put you in the picture :

Initially I did not compile the kernel so I did not cause the problem by doing so.

This was the problem from a fresh install with no attempt to alter anything.

The mouse did not work for either kernel until I ran xorgconfig a few times and eventually
chose PS/2 for the mouse type. Then it worked with the 2.4.29 kernel.
Thanks,
Norm
Back to top
chuck@nil.car
*nix forums Guru Wannabe


Joined: 23 Aug 2005
Posts: 100

PostPosted: Thu Jul 13, 2006 11:54 pm    Post subject: Re: unresolved symbols and other problems Reply with quote

Norman Elliott <nelliott@uklinux.net> wrote in
news:12bbtth209drs93@corp.supernews.com:

Quote:
chuckcar wrote:

Now if I boot the 2.4.29 kernel then X starts okay and I can use it
with icewm but I cannot use my pcmcia network card an Asus WL-107G
so I cannot access my main PC.

Before setting up with ndiswrapper I run depmod -a I and get a
series of 'unresolved symbols' errors relating to wlan.o,
wlan_acl.o etc ath_hal ath_pci.o etc so don't set up the driver
with ndiswrapper.

I downloaded the 2.4.29 source and compiled it and ran

make clean && make dep && make && make modules && make
modules_install but it still complains.

If I boot the 2.6.12 kernel I get no unresolved symbol errors so I
can use the network card with ndiswrapper

Get a copy of the kernel howto from

http://tldp.org/HOWTO/Kernel-HOWTO/index.html

1. cd /usr/src/linux-2.6.12
2. cp .config /root - just to be safe file is probably junk
3. make mrproper
4. make menuconfig

go through every submenu here (you don't have to use the mouse you
can use the arrow, tab and enter keys.) You *do* have to know what
hardware you have on your computer - read: video card, sound card
modem. Any problems reply to me. Ignore unruh *completely* or it will
get worse - trust me, he's been trolling me for 6 months now and he
changes his handle all the time.


Well I don't have time to do any of this just now as I have to catch a
boat to the mainland and will be away for 1 week but just to put you
in the picture :

Initially I did not compile the kernel so I did not cause the problem
by doing so.

This was the problem from a fresh install with no attempt to alter
anything.

The mouse did not work for either kernel until I ran xorgconfig a few
times and eventually chose PS/2 for the mouse type. Then it worked
with the 2.4.29 kernel. Thanks,
Norm

Just to clairify, From your previous post to me:

Quote:


You *did* run make menuconfig before you ran make clean dep... right?
otherwise, you just got the defaults and compiling the kernel is
pointless.

Sorry, no, I ran make oldconfig guess tha may be the problem!!!!



*that* is compiling the kernel. I don't know if you're deeper into linux
then you wanted, or the conflict is too much or what, but just try
removing the /usr/src/linux-2.6.xx directory and then reinstalling that
kernel and then doing a make modules modules_install from that directory
and then a depmod -a and reboot. and that might do it, if not - you have
to compile the kernel for 2.6 to work end of story. You might also check
that your /etc/modules.conf is loading modules that exist in
/lib/modules/2.6... and they don't have completely different names in
lib/modules/2.4...

(If I'm wrong about the modules subdir's for kernel versions - someone
correct me and my apologies).


--
(setq (chuck nil) car(chuck) )
Back to top
Norman Elliott
*nix forums beginner


Joined: 17 Jun 2006
Posts: 21

PostPosted: Mon Jul 17, 2006 10:20 pm    Post subject: Re: unresolved symbols and other problems Reply with quote

Quote:
Now if I boot the 2.4.29 kernel then X starts okay and I can use it
with icewm but I cannot use my pcmcia network card an Asus WL-107G
so I cannot access my main PC.

Before setting up with ndiswrapper I run depmod -a I and get a
series of 'unresolved symbols' errors relating to wlan.o,
wlan_acl.o etc ath_hal ath_pci.o etc so don't set up the driver
with ndiswrapper.

I downloaded the 2.4.29 source and compiled it and ran

make clean && make dep && make && make modules && make
modules_install but it still complains.






Quote:
If I boot the 2.6.12 kernel

I get no unresolved symbol errors so I use the network card with ndiswrapper
Quote:


This was the problem from a fresh install with no attempt to alter
anything.

The mouse did not work for either kernel until I ran xorgconfig a few
times and eventually chose PS/2 for the mouse type. Then it worked
with the 2.4.29 kernel. Thanks,
Norm



Sorry, no, I ran make oldconfig guess tha may be the problem!!!!

I mean't I may not have made some configuration changes using make oldconfig


as opposed to using make menucinfig.
Quote:

*that* is compiling the kernel.


I don't know if you're deeper into linux
Quote:
then you wanted, or the conflict is too much or what,

Not at all, I will go on until I find out what is wrong even if I end up trashing all of
this because i want to learn and understand.

Atfer all if I just wanted to shell out money for poor proprietry softwoare I could have
bought MS and never learned anything except how to disinfect and re-install it.

but just try
Quote:
removing the /usr/src/linux-2.6.xx directory and then reinstalling that
kernel and then doing a make modules modules_install from that directory
and then a depmod -a and reboot. and that might do it, if not - you have
to compile the kernel for 2.6 to work end of story. You might also check
that your /etc/modules.conf is loading modules that exist in
/lib/modules/2.6... and they don't have completely different names in
lib/modules/2.4...
But I have no problems with depmod -a and the 2.6.12 kernel without doing any of this so

how would it change anything?
Quote:


Norm
Back to top
chuck@nil.car
*nix forums Guru Wannabe


Joined: 23 Aug 2005
Posts: 100

PostPosted: Tue Jul 18, 2006 12:00 am    Post subject: Re: unresolved symbols and other problems Reply with quote

Norman Elliott <nelliott@uklinux.net> wrote in
news:12bo32l5nbpmr3e@corp.supernews.com:

Quote:
but just try
removing the /usr/src/linux-2.6.xx directory and then reinstalling
that kernel and then doing a make modules modules_install from that
directory and then a depmod -a and reboot. and that might do it, if
not - you have to compile the kernel for 2.6 to work end of story.
You might also check that your /etc/modules.conf is loading modules
that exist in /lib/modules/2.6... and they don't have completely
different names in lib/modules/2.4...
But I have no problems with depmod -a and the 2.6.12 kernel without
doing any of this so how would it change anything?


Well, if you don't install modules and *then* do a depmod, it's still
using the old modules were there by default - if they're not all there -
problems. You have to understand *why* the kernel is compiled. It's not
just to match the hardware to the computer, it's to write it in stone so
to speak. You specify (in your case I would use modules whenever
possible) what processor/graphics/sound and other pci cards you have in
the make menuconfig, make the dependencies so the compile doesn't get
confused do the compile - make bzImage, run make bzlilo to install the
kernel and link it to the lilo loader and I *always* run make bzdisk so
I have a backup disk if the boot sector gets fouled up. *Read* the
kernel HOWTO, you are at a point where you *need* to understand what it
says. Wait until you understand it *before* you try again with the
kernel. I knew 8086 and several languages and was building my own
computers when I first compiled my kernel in linux - and I didn't get it
right the first time and took a *while* to figure out what I did wrong
and this was an 386 ISA machine with just a sound card and a vga card in
it. It's tough, no doubt, but it's a hurdle you have to get past if you
want to be able to maintain and run a linux system period.


Quote:

Norm




--
(setq (chuck nil) car(chuck) )
Back to top
Norman Elliott
*nix forums beginner


Joined: 17 Jun 2006
Posts: 21

PostPosted: Tue Jul 18, 2006 7:50 pm    Post subject: Re: unresolved symbols and other problems Reply with quote

chuckcar wrote:
Quote:
Norman Elliott <nelliott@uklinux.net> wrote in
news:12bo32l5nbpmr3e@corp.supernews.com:


but just try

removing the /usr/src/linux-2.6.xx directory and then reinstalling
that kernel and then doing a make modules modules_install from that
directory and then a depmod -a and reboot. and that might do it, if
not - you have to compile the kernel for 2.6 to work end of story.
You might also check that your /etc/modules.conf is loading modules
that exist in /lib/modules/2.6... and they don't have completely
different names in lib/modules/2.4...

But I have no problems with depmod -a and the 2.6.12 kernel without
doing any of this so how would it change anything?


Well, if you don't install modules and *then* do a depmod, it's still
using the old modules were there by default - if they're not all there -
problems. You have to understand *why* the kernel is compiled. It's not
just to match the hardware to the computer, it's to write it in stone so
to speak. You specify (in your case I would use modules whenever
possible) what processor/graphics/sound and other pci cards you have in
the make menuconfig, make the dependencies so the compile doesn't get
confused do the compile - make bzImage, run make bzlilo to install the
kernel and link it to the lilo loader and I *always* run make bzdisk so
I have a backup disk if the boot sector gets fouled up. *Read* the
kernel HOWTO, you are at a point where you *need* to understand what it
says. Wait until you understand it *before* you try again with the
kernel. I knew 8086 and several languages and was building my own
computers when I first compiled my kernel in linux - and I didn't get it
right the first time and took a *while* to figure out what I did wrong
and this was an 386 ISA machine with just a sound card and a vga card in
it. It's tough, no doubt, but it's a hurdle you have to get past if you
want to be able to maintain and run a linux system period.
Okay,

So if I understand this correctly, the mouse module which came with the
install for 2.6.12 kernel either has some corruption or is buggy.

If I clear everything out, download the needed sources and do the
compile etc i.e give it the full works,then there is some chance that,
if it is corrupt, the module will then work.

However, I need to find out what is in the laptop regarding graphics card etc.
When I installed new kernels for slackware in the past I had only done so for a desktop
machine and just opened up the case, got a magnifying glass out and had a look at chipsets
etc. This is a whole new ball game.
Norm
Back to top
chuck@nil.car
*nix forums Guru Wannabe


Joined: 23 Aug 2005
Posts: 100

PostPosted: Tue Jul 18, 2006 10:35 pm    Post subject: Re: unresolved symbols and other problems Reply with quote

Norman Elliott <nelliott@uklinux.net> wrote in
news:12bqeki98th1q5e@corp.supernews.com:

Quote:
chuckcar wrote:
Norman Elliott <nelliott@uklinux.net> wrote in
news:12bo32l5nbpmr3e@corp.supernews.com:


but just try

removing the /usr/src/linux-2.6.xx directory and then reinstalling
that kernel and then doing a make modules modules_install from that
directory and then a depmod -a and reboot. and that might do it, if
not - you have to compile the kernel for 2.6 to work end of story.
You might also check that your /etc/modules.conf is loading modules
that exist in /lib/modules/2.6... and they don't have completely
different names in lib/modules/2.4...

But I have no problems with depmod -a and the 2.6.12 kernel without
doing any of this so how would it change anything?


Well, if you don't install modules and *then* do a depmod, it's still
using the old modules were there by default - if they're not all
there - problems. You have to understand *why* the kernel is
compiled. It's not just to match the hardware to the computer, it's
to write it in stone so to speak. You specify (in your case I would
use modules whenever possible) what processor/graphics/sound and
other pci cards you have in the make menuconfig, make the
dependencies so the compile doesn't get confused do the compile -
make bzImage, run make bzlilo to install the kernel and link it to
the lilo loader and I *always* run make bzdisk so I have a backup
disk if the boot sector gets fouled up. *Read* the kernel HOWTO, you
are at a point where you *need* to understand what it says. Wait
until you understand it *before* you try again with the kernel. I
knew 8086 and several languages and was building my own computers
when I first compiled my kernel in linux - and I didn't get it right
the first time and took a *while* to figure out what I did wrong and
this was an 386 ISA machine with just a sound card and a vga card in
it. It's tough, no doubt, but it's a hurdle you have to get past if
you want to be able to maintain and run a linux system period.
Okay,
So if I understand this correctly, the mouse module which came with
the install for 2.6.12 kernel either has some corruption or is buggy.

If I clear everything out, download the needed sources and do the
compile etc i.e give it the full works,then there is some chance that,
if it is corrupt, the module will then work.

However, I need to find out what is in the laptop regarding graphics
card etc. When I installed new kernels for slackware in the past I had
only done so for a desktop machine and just opened up the case, got a
magnifying glass out and had a look at chipsets etc. This is a whole
new ball game. Norm

Try using lspci -v|more to tell you what pci devices you have - will

tell you say Intel 810 instead of I810 <brand-name> video card, and
such, but you need to know the chips anyways mostly not the brand name.

--
(setq (chuck nil) car(chuck) )
Back to top
Google

Back to top
Display posts from previous:   
Post new topic   Reply to topic Page 2 of 2 [22 Posts] Goto page:  Previous  1, 2
View previous topic :: View next topic
The time now is Sat Nov 22, 2008 9:45 am | All times are GMT
navigation Forum index » *nix » Linux » Setup
Jump to:  

Similar Topics
Topic Author Forum Replies Last Post
No new posts Winbind problems for ADS authentication nlinley networking 1 Tue Sep 19, 2006 9:22 am
No new posts problems using oddmuse with mod_perl2 inside apache2.2 pe... Fergus McMenemie Perl 0 Fri Jul 21, 2006 9:48 am
No new posts Problems with make-kpkg and skas patch Todd A. Jacobs Debian 0 Fri Jul 21, 2006 12:30 am
No new posts Problems with relay control Félix Martos Trenado Postfix 3 Thu Jul 20, 2006 3:33 pm
No new posts again a newbie... :( compiler problems Thorsten Kaben C++ 18 Thu Jul 20, 2006 2:52 am

Loans | Loan | Debt Consolidation | Loans | Property Search
Copyright © 2004-2005 DeniX Solutions SRL
 
Other DeniX Solutions sites: Unix/Linux blog |  electronics forum |  medicine forum |  science forum | 
Privacy Policy


Powered by phpBB © 2001, 2005 phpBB Group
[ Time: 0.4812s ][ Queries: 16 (0.3450s) ][ GZIP on - Debug on ]