I have just recently (a few days ago) ordered the card (BeWAN ADSL PCI
st). This was before I heard of any troubles with its 2.6 support or
lack of driver development.
The card should arrive within a week or two, at which point I will
attempt to make it work with the 2.6.7 kernel without a hitch. If I am unsuccessful within a week, I will have to try and find a way to get a refund, or sell the card onwards.
If I am successful, I will be in a position to do something about the outdated unicorn-source package.
On Sat, Aug 14, 2004 at 06:51:04PM +0300, Nuutti Kotivuori wrote:
I have just recently (a few days ago) ordered the card (BeWAN ADSL
PCI st). This was before I heard of any troubles with its 2.6
support or lack of driver development.
This is all wrong, i have not had time for proper maintenance, but
will fix the build problem next week. I don't have x86 box anymore,
and had to borrow one to do the build on it.
The card should arrive within a week or two, at which point I will
attempt to make it work with the 2.6.7 kernel without a hitch. If I
am unsuccessful within a week, I will have to try and find a way to
get a refund, or sell the card onwards.
Upstream (Bewan) provide drivers that build on 2.6.
It is just the fact that i lost my x86 hardware which stopped me
from uploading the package. Well, this and more important work that
passed first in other parts of debian (like being part of the new
kernel team, and bringing you 2.6 kernels that work in the first
place.
If I am successful, I will be in a position to do something about
the outdated unicorn-source package.
I would welcome a co-maintainer with x86 hardware.
Sven Luther wrote:
On Sat, Aug 14, 2004 at 06:51:04PM +0300, Nuutti Kotivuori wrote:
I have just recently (a few days ago) ordered the card (BeWAN ADSL
PCI st). This was before I heard of any troubles with its 2.6
support or lack of driver development.
This is all wrong, i have not had time for proper maintenance, but
will fix the build problem next week. I don't have x86 box anymore,
and had to borrow one to do the build on it.
I understand - I read your latest comment on the matter.
The card should arrive within a week or two, at which point I will
attempt to make it work with the 2.6.7 kernel without a hitch. If I
am unsuccessful within a week, I will have to try and find a way to
get a refund, or sell the card onwards.
Upstream (Bewan) provide drivers that build on 2.6.
It looks like that - but just recently, this happened:
,----[ http://www.linuxdsl.co.uk/ ]
| 11 August 2004 - This website is no longer maintained.
|
| The BeWAN ADSL PCI used to be the best supported PCI ADSL modem for
| Linux. This, unfortunately, is no longer the case. Since the
| introduciton of the 2.6 kernel BeWAN have ceased supporting Linux as a
| platform. My guess is they did not have the resources to carry on. The
| card still works wonderfully under the 2.4 kernel (using the 0.8.1
| drivers). If all you want is a rock solid internet gateway then I
| would highly recommend Debian 3.0r2 or Smoothwall (v2.0) together with
| a BeWAN card and the 0.8.1 drivers.
|
| The old site has been archived and can be downloaded as a gzipped tar
| by following this link: archived website (it contains a working
| install guide, drivers and a version of pppd that understands
| PPPoATM).
`----
So, I am not certain what information to trust.
It is just the fact that i lost my x86 hardware which stopped me
from uploading the package. Well, this and more important work that
passed first in other parts of debian (like being part of the new
kernel team, and bringing you 2.6 kernels that work in the first
place.
Yeah, I know. And kudos on your work there, I and a lot of others,
appreciate that.
If I am successful, I will be in a position to do something about
the outdated unicorn-source package.
I would welcome a co-maintainer with x86 hardware.
We shall see what comes out of this when my hardware finally arrives.
Thank you for the reply,
Sven Luther wrote:
[...]
This is pure bullshit. The current drivers : 0.8.7 add support for
2.6 kernels, and it did happen in part due to my and other debian's
users request. The driver can be downloaded at :
http://www.bewan.fr/bewan/utilisateurs/telechargement/download.php?id=81
And, as the debian unicorn maintainer, i have some serious doubt
about the debian-quality of a debian woody install with self
compiled modules or something such, since the right way to do this
in debian is to build a module .udeb.
Okay, well that eases my worries a bit. I hope good support is the way
it will remain as well.
We shall see what comes out of this when my hardware finally
arrives.
In any case, don't hesitate to ask me about this. I will also try to
make prebuilt modules for both the 2.6.8 and 2.4.27 kernels that
where just uploaded.
My hardware arrived today, just a couple hours ago. I will be
compiling a new kernel and testing it tonight. I am wondering if you
already have a pre-release unicorn-source packaging of 0.8.7 drivers somewhere where I could download it? If not, I will be doing the
packaging temporarily for myself.
In any case, I can now betatest and debug packages if needed.
It would be great to get the prebuilt drivers for recent kernels
accepted and the installation as streamlined as possible - ADSL PCI
cards that work well with Linux are hard to come by.
I have something, but it is not yet perfect. Attached here
though. The problem is that it doesn't tie in well with the 2.6
build stuff.
Sven Luther wrote:
I have something, but it is not yet perfect. Attached here
though. The problem is that it doesn't tie in well with the 2.6
build stuff.
Thank you. I was able to compile the source package, but the resulted
debian package did not have any .ko files. I will head home now to
install the card and to try and actually get a module out of the
thing.
In any case, it's much easier to work on top of this, than the old
package.
On Mon, Aug 16, 2004 at 05:30:07PM +0300, Nuutti Kotivuori wrote:
Sven Luther wrote:
I have something, but it is not yet perfect. Attached here
though. The problem is that it doesn't tie in well with the 2.6
build stuff.
Thank you. I was able to compile the source package, but the
resulted debian package did not have any .ko files. I will head
home now to install the card and to try and actually get a module
out of the thing.
In any case, it's much easier to work on top of this, than the old
package.
Indeed. The real problem is that it isn't adapted to the 2.6 build
manner.
So, now I have supposedly have the modules, but I get a problem when insmoding them:
unicorn_pci_atm: Unknown symbol set_cpus_allowed
Kernel version is 2.6.7. Digging further in now.
Nuutti Kotivuori wrote:
So, now I have supposedly have the modules, but I get a problem when insmoding them:
unicorn_pci_atm: Unknown symbol set_cpus_allowed
Kernel version is 2.6.7. Digging further in now.
Found it, was bloody obvious but took me half an hour.
EXPORT_SYMBOL_GPL(set_cpus_allowed);
^^^
Now that I, ehum, fixed this problem as a test, the module loads and
seems to operate atleast somewhat. Next step is trying to get the
actual ADSL line to work with it, but that will require configuration.
Sven Luther wrote:
On Mon, Aug 16, 2004 at 10:41:02PM +0300, Nuutti Kotivuori wrote:
Nuutti Kotivuori wrote:
So, now I have supposedly have the modules, but I get a problem
when insmoding them:
unicorn_pci_atm: Unknown symbol set_cpus_allowed
Kernel version is 2.6.7. Digging further in now.
Found it, was bloody obvious but took me half an hour.
EXPORT_SYMBOL_GPL(set_cpus_allowed);
^^^
Which file was that in ?
Allow me to be a bit more verbose. This snippet is in unicorn sources:
,----[ unicorn/msw/linrapi.c ]
| #ifdef CONFIG_SMP
| // Hack to try to make it work on SMP !!!!
| // Lock the threads to CPU #0
| set_cpus_allowed(k->thread,1UL << 0);
| #endif
`----
Now, the file unicorn_pcidrv.c has license "Proprietary", so the
created module cannot use the GPL only symbol.
And the reason this probably didn't show up for you anywhere is that I
happen to have a SMP machine using the card. That comment doesn't give
much trust in the workings though...
Now that I, ehum, fixed this problem as a test, the module loads
and seems to operate atleast somewhat. Next step is trying to get
the actual ADSL line to work with it, but that will require
configuration.
Configuration is quite easy, i had not much trouble with it.
Me neither, in the end. Modprobing module, making a new ppp peer and
editing /etc/network/interfaces - works like a dream.
I am now testing my link so I know that it works well.
Yes, this is some sick situation with the linux kernel, having no
trouble with binary only modules for some stuff, but not for
others. This may be one point where the rumors about Bewan leaving
the linux market may come from.
Now, next step is to make the package build in the debian way, you
didn't do this yet, right ?
Sven Luther wrote:
Now, next step is to make the package build in the debian way, you
didn't do this yet, right ?
No, not really. I hacked it together with a few ugly local hacks.
As far as I could tell, the module installation was the only visible
problem, and that was caused by modules_install not honoring the
DESTDIR, not that DESTDIR would have even been passed on to it, so
it ends up creating /lib/modules/2.6.7/extra/* instead of $(DESTDIR)/lib/modules/2.6.7-with-appendages/extra/*.
Nuutti Kotivuori wrote:
Sven Luther wrote:
Now, next step is to make the package build in the debian way, you
didn't do this yet, right ?
No, not really. I hacked it together with a few ugly local hacks.
As far as I could tell, the module installation was the only visible problem, and that was caused by modules_install not honoring the
DESTDIR, not that DESTDIR would have even been passed on to it, so
it ends up creating /lib/modules/2.6.7/extra/* instead of $(DESTDIR)/lib/modules/2.6.7-with-appendages/extra/*.
The Makefiles inside unicorn_pci and unicorn_usb seem to just call the
kernel Makefile to do the compiling and the installation for 2.6. I
made a small diff that changes debian/rules to call directly into the
kernel Makefile to do the compiling and installation, with suitable arguments.
As a result, I got a decently building package. I am not sure if one
wishes to bypass the unicorn makefiles, and I am not certain about the EXTRAV_ARG vs. KPKG_EXTRAV_ARG difference in this rules file.
But, I'm attaching the diff if it happens to be of some assistance.
Sven Luther wrote:
We need to make sure this builds on both 2.6 and 2.4 kernels though.
Yes. I believe the package should be almost ready for 2.4 already. All
the changes are within 2.6 only sections.
[...]
Yes, that is the right thing to do, i believe. Will be testing on
this lended x86 box, and keep you informed. Can you test it with a
2.4 kernel too ?
I'm afraid the box I'm using it on is my home router and it is used by
other people as well. I'd rather not boot it too often.
We need to make sure this builds on both 2.6 and 2.4 kernels though.
Yes, that is the right thing to do, i believe. Will be testing on
this lended x86 box, and keep you informed. Can you test it with a
2.4 kernel too ?
| Sysop: | Keyop |
|---|---|
| Location: | Huddersfield, West Yorkshire, UK |
| Users: | 715 |
| Nodes: | 16 (2 / 14) |
| Uptime: | 47:47:03 |
| Calls: | 12,112 |
| Calls today: | 3 |
| Files: | 15,010 |
| Messages: | 6,518,503 |