Re: [leaf-user] Bewan drivers

[<da...@la...>]

Thanks Jacques,

I'll give this a try - might take a while as I'm currently struggling on dial up and a very slow webmail from my isp.

A couple of questions though - over the last day I've compiled on a stock redhat 7.3 (2.4.18) It compiled first time, no problems. Is the only difference between this and what you suggest the Bering config file? Or does compiling a bering kernel previously in the same source tree really make a difference to what my kernel modules pick up. If I did get the same problem (do_BUG not found) what options are there for fixing this in Bering (e.g. I could do a depmod on a standard linux box) I had a good mess around with compile and link options to see if I could affect this, but no luck.

thanks
Dave

jn...@us... wrote:
> Le Samedi 21 Septembre 2002 22:21, da...@la... a crit :
> > Hi,
> >
> > I am upgrading to the latest version of the bewan adsl pci card drivers
> > (http://www.bewan.com/bewan/drivers/bapst-0.3.4.tar.gz)
> >
> > I have setup up the debian/slink virtual uml and compiled the driver, but
> > when I try and load the module I get
> >
> > # insmod unicorn_atm
> > Using /lib/modules/unicorn_atm.o
> > insmod: unresolved symbol do_BUG
> Dave:
> You should not use slink to compile kernel related stuff
> In Bering kernel and modules are compiled with gcc 2.95 from debian Potatoe 
> up to rc3 and from debian Woody now. But you can use a more recent compiler 
> if you wish (the 2.95 leads to the smaller footprint though)
> My advice would be for you to compile your own Bering kernelon whatever Linux 
> developement box you have. You do not need to apply Bering kernel patches if 
> you not not need them (but **DO** use the Bering kernel config file) and then 
> compile bewan pci stuff out of your kernel tree
> In the process you will be able to get rid of modules.lrp :-)
> Jacques
>