FATAL: Error inserting speakup_sftsyn (/lib/modules/2.6.18speakup/kernel/drivers/char/speakup/speakup_sftsyn.ko): Unknown symbol in module, or unknown parameter

FATAL: Error inserting speakup_sftsyn (/lib/modules/2.6.18speakup/kernel/drivers/char/speakup/speakup_sftsyn.ko): Unknown symbol in module, or unknown parameter

[Jan Buchal]

Hello,

I compiled speakup with 2.6.18-3-amd64 on my Debian. Compillation
finished OK. But if I loaded the speakup modules comes some error:

homer:~# modprobe speakup_sftsyn
WARNING: Error inserting speakupmain (/lib/modules/2.6.18speakup/kernel/drivers/char/speakup/speakupmain.ko): Unknown symbol in module, or unknown parameter (see dmesg)
FATAL: Error inserting speakup_sftsyn (/lib/modules/2.6.18speakup/kernel/drivers/char/speakup/speakup_sftsyn.ko): Unknown symbol in module, or unknown parameter (see dmesg)


speakupmain: Unknown symbol kbd
speakupmain: Unknown symbol k_handler
speakup_sftsyn: Unknown symbol synth_buff_in
speakup_sftsyn: Unknown symbol synth_add
speakup_sftsyn: Unknown symbol synth
speakup_sftsyn: Unknown symbol synth_buff_out
speakup_sftsyn: Unknown symbol synth_release
speakup_sftsyn: Unknown symbol do_synth_init
speakup_sftsyn: Unknown symbol synth_write
speakup_sftsyn: Unknown symbol synth_alive
speakup_sftsyn: Unknown symbol synth_remove
speakup_sftsyn: Unknown symbol synth_done

I used speakup from 1st October 2006 because the latest snapshot is not
possible compiled with kernel 2.6.18


Thanks for help



-- 

Jan Buchal
Tel: (00420) 24 24 86 008
Mob: (00420) 608023021

Re: FATAL: Error inserting speakup_sftsyn (/lib/modules/2.6.18speakup/kernel/drivers/char/speakup/speakup_sftsyn.ko): Unknown symbol in module, or unknown parameter

[Kirk Reiser]

Hi Jan:  Based on that output I'd say that the patching portion of the
checkout failed.  At least, part of it failed but those symbols
indicate it was a lot more than just one patch part.

  Kirk

-- 

Kirk Reiser				The Computer Braille Facility
e-mail: kirk@braille.uwo.ca		University of Western Ontario
phone: (519) 661-3061

Re: FATAL: Error inserting speakup_sftsyn (/lib/modules/2.6.18speakup/kernel/drivers/char/speakup/speakup_sftsyn.ko): Unknown symbol in module, or unknown parameter

[Jan Buchal]

>>>>> "KR" == Kirk Reiser <kirk@braille.uwo.ca> writes:

    KR> Hi Jan: Based on that output I'd say that the patching portion
    KR> of the checkout failed. At least, part of it failed but those
    KR> symbols indicate it was a lot more than just one patch part.
Hi Kirk,

maybe, but I'm not sure. I tried three version of cvs speakup snapshot,
1-st august, 1-st September and 1-st October. All checkouts finished OK
and compilation of kernel too. Here are my steps:

- cd linux
- ../checkout
- make-kpkg --initrd --append_to_version speakup kernel_image

If it not works then:

- rm /usr/src/linux/debian/
- rm /usr/src/linux/drivers/char/speakup/ -rf

and again checkout, make-kpkg ...

The result was identical in every version.

Thanks.


-- 

Jan Buchal
Tel: (00420) 24 24 86 008
Mob: (00420) 608023021

Re: FATAL: Error inserting speakup_sftsyn (/lib/modules/2.6.18speakup/kernel/drivers/char/speakup/speakup_sftsyn.ko): Unknown symbol in module, or unknown parameter

[Kirk Reiser]

Well,  I am not aware of how the debian kernels compile exactly but
what you show looks okay.  The problem is there was no output from the
checkout script to tell if the scripts in fact patched without any
failed parts or hunks.  I can only guess but you should have received
a bunch of output from the checkout script which the only important
bits are the bottom dozen or so lines.

  Kirk

-- 

Kirk Reiser				The Computer Braille Facility
e-mail: kirk@braille.uwo.ca		University of Western Ontario
phone: (519) 661-3061

Re: FATAL: Error inserting speakup_sftsyn (/lib/modules/2.6.18speakup/kernel/drivers/char/speakup/speakup_sftsyn.ko): Unknown symbol in module, or unknown parameter

[Jan Buchal]

>>>>> "KR" == Kirk Reiser <kirk@braille.uwo.ca> writes:

    KR> Well, I am not aware of how the debian kernels compile exactly
    KR> but what you show looks okay. The problem is there was no output
    KR> from the checkout script to tell if the scripts in fact patched
    KR> without any failed parts or hunks. I can only guess but you
    KR> should have received a bunch of output from the checkout script
    KR> which the only important bits are the bottom dozen or so lines.
Right. Here is the output:
homer:/usr/src/linux# ../checkout
Patching version v26
CVSROOT not set.  Enter it below.  Hit enter for anonymous.
CVSROOT> 
Logging in to :pserver:anonymous@linux-speakup.org:2401/usr/src/CVS


[....]

Creating .orig files [] done.
Patching files [ppp1 out of 10 hunks FAILED -- saving rejects to file /usr/src/linux/drivers/char/keyboard.c.rej
pp1 out of 14 hunks FAILED -- saving rejects to file /usr/src/linux/drivers/char/vt.c.rej
ppppp] done.
Copying files [cccccc] done.
homer:/usr/src/linux# 


Thanks.

-- 

Jan Buchal
Tel: (00420) 24 24 86 008
Mob: (00420) 608023021

Re: FATAL: Error inserting speakup_sftsyn (/lib/modules/2.6.18speakup/kernel/drivers/char/speakup/speakup_sftsyn.ko): Unknown symbol in module, or unknown parameter

[Luke Yelavich]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

On Thu, Jan 25, 2007 at 07:44:31AM EST, Jan Buchal wrote:
> Creating .orig files [] done.
> Patching files [ppp1 out of 10 hunks FAILED -- saving rejects to file /usr/src/linux/drivers/char/keyboard.c.rej
> pp1 out of 14 hunks FAILED -- saving rejects to file /usr/src/linux/drivers/char/vt.c.rej

Thatindeed failed to patch cleanly. The word failed should give it away 
for a start.

Looks like the keyboard and vt patches didn't apply cleanly, which 
explains the unknown symbols related to the keyboard.
- -- 
Luke Yelavich
GPG key: 0xD06320CE 
	 (http://www.themuso.com/themuso-gpg-key.txt)
Email & MSN: themuso@themuso.com
Jabber: themuso@jabber.org.au
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.3 (GNU/Linux)

iD8DBQFFt8z5jVefwtBjIM4RAmcTAKCZLFT38BzXDkPMGi3Yj1GV40pZIgCdH7DV
SXanNkS8i8lWhSUTgHGIYfQ=
=6Xtf
-----END PGP SIGNATURE-----

Re: FATAL: Error inserting speakup_sftsyn (/lib/modules/2.6.18speakup/kernel/drivers/char/speakup/speakup_sftsyn.ko): Unknown symbol in module, or unknown parameter

[Jan Buchal]

>>>>> "LY" == Luke Yelavich <themuso@themuso.com> writes:

    LY> On Thu, Jan 25, 2007 at 07:44:31AM EST, Jan Buchal wrote:
    >> Creating .orig files [] done. Patching files [ppp1 out of 10
    >> hunks FAILED -- saving rejects to file
    >> /usr/src/linux/drivers/char/keyboard.c.rej pp1 out of 14 hunks
    >> FAILED -- saving rejects to file
    >> /usr/src/linux/drivers/char/vt.c.rej

    LY> Thatindeed failed to patch cleanly. The word failed should give
    LY> it away for a start.

    LY> Looks like the keyboard and vt patches didn't apply cleanly,
    LY> which explains the unknown symbols related to the keyboard. --
Yes, and what I can do?

Best

-- 

Jan Buchal
Tel: (00420) 24 24 86 008
Mob: (00420) 608023021

Re: FATAL: Error inserting speakup_sftsyn (/lib/modules/2.6.18speakup/kernel/drivers/char/speakup/speakup_sftsyn.ko): Unknown symbol in module, or unknown parameter

[Gregory Nowak]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

In the procedures you described, I haven't seen you saying you ran

make mrproper clean,

so I would do that first, after backing up your .config file of
course. Better yet, untar a fresh source tree. If that still doesn't
help, then confirm you're using a cvs version that actually supports
2.6.18.x kernels. The best way to do that is through the speakup
changelog, or what I use is the cvs mailing list archives. 

Finally, when I was patching a 2.6.18.x, and 2.6.19 kernel a while ago,
I noticed that linux-speakup.org, and fl.linux-speakup.org weren't in
sync. The latest cvs from linux-speakup.org contained a version
compatible with 2.6.19, while the latest cvs from fl.linux-speakup.org
contained the previous version, still compatible with 2.6.18.x. Like
I've said though, this was a while ago, so the mirror might have been
synced with the main server since that time.

Hth, and good luck.

Greg

 

On Wed, Jan 24, 2007 at 10:39:41PM +0100, Jan Buchal wrote:
> Yes, and what I can do?
> 
> Best
> 
> -- 
> 
> Jan Buchal
> Tel: (00420) 24 24 86 008
> Mob: (00420) 608023021
> 
> 
> _______________________________________________
> Speakup mailing list
> Speakup@braille.uwo.ca
> http://speech.braille.uwo.ca/mailman/listinfo/speakup

- -- 
web site: http://www.romuald.net.eu.org
gpg public key: http://www.romuald.net.eu.org/pubkey.asc
skype: gregn1
(authorization required, add me to your contacts list first)

- --
Free domains: http://www.eu.org/ or mail dns-manager@EU.org
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.6 (GNU/Linux)

iD8DBQFFt9no7s9z/XlyUyARAth1AJ9isVsl4YwExm8CfwKmL0fPCPBV0ACguof5
QWyfU2bpZGiWo5UqYIs2ITI=
=lUWz
-----END PGP SIGNATURE-----

Re: FATAL: Error inserting speakup_sftsyn (/lib/modules/2.6.18speakup/kernel/drivers/char/speakup/speakup_sftsyn.ko): Unknown symbol in module, or unknown parameter

[Jan Buchal]

>>>>> "GN" == Gregory Nowak <greg@romuald.net.eu.org> writes:

    GN> In the procedures you described, I haven't seen you saying you
    GN> ran make mrproper clean,
Yes I did it now.


    GN> so I would do that first, after backing up your .config file of
    GN> course. Better yet, untar a fresh source tree. If that still
    GN> doesn't help, then confirm you're using a cvs version that
    GN> actually supports 2.6.18.x kernels. The best way to do that is
    GN> through the speakup changelog, or what I use is the cvs mailing
    GN> list archives.

Speakup works now. However I don't know why. :-) In the same time I made
'make mrproper' and changed the update date to 1-st November in checkout
skript and forgot delete the driver/char/speakup directory.

Thanks to all


-- 

Jan Buchal
Tel: (00420) 24 24 86 008
Mob: (00420) 608023021