I have been having lots of fun with LEAF-Bering (thanks guys), but there still
remains one small issue I have not been able to resolve.
I have configured the system to send emails on ping failure and space check
but they do not seem to be sent.
If I run the 'mail' command manually with
mail -
I am interested in evaluating WISP-Dist, but do not at present have a computer
with a Flash Card reader. I have tried (unsuccessfully) to load it from CD by
adapting the instructions for Bering.
Has anyone managed to get it booting from CD or multiple floppies?
Thanks
derek
---
On Tuesday 24 Sep 2002 5:00 pm, you wrote:
> I have been having lots of fun with LEAF-Bering (thanks guys), but there
> still remains one small issue I have not been able to resolve.
>
> I have configured the system to send emails on ping failure and space check
> but they do not seem to be sent.
> > I have been having lots of fun with LEAF-Bering (thanks guys), but
> > there still remains one small issue I have not been able to resolve.
> >
> > I have configured the system to send emails on ping failure and
> > space check but they do not seem to be sent.
> >
> > If I run the 'mail' c
Hi
It is probably me doing something idiotic, but I am having trouble running
Bering_1.0-stable_img_bering_1680.bin in the linuxuml-2.4.18-45 Virtual
environment.
I have followed Jacques Nilo's instructions, and can successfully create the
Bering_fs file system, but when I run my startuml scrip
rds,
> Eric Kiser
>
>
>
> -Original Message-
> From: [EMAIL PROTECTED]
> [mailto:[EMAIL PROTECTED]]On Behalf Of Derek
> Jennings
> Sent: Wednesday, December 04, 2002 7:08 PM
> To: [EMAIL PROTECTED]
> Subject: [leaf-user] Unable to run linuxuml Virtual Rout
I am trying to get the prism2_usb module working with Wisp Rel 2397 without
much luck. The usb usb-uhci driver is working OK, but if I insmod prism2_usb
I get
# insmod prism2_usb
insmod: /lib/modules/2.4.18: No such file or directory
Using /modules/prism2_usb.o
insmod: unresolved symbol p80211ne
Thanks for the great information Brad. insmodding the p80211 module got rid of the
unresolvedsymbols.
My Actiontec usb wireless adapter is now detected. It comes up as wlan0, but the MAC
address is vacant and iwconfig does not detect it, although I can assign an IP
address, and ping it. WISP
I am getting so close to getting this thing work I can smell it.
With WISP-2397 I can load the prism2_usb and p80211 modules (from Bering 1.0)
and using a configuration script from the wlan-ng site I can start and stop
the usb wireless adapter.
The usb adapter syncs up with the access point, a
0200
To: [EMAIL PROTECTED]
Subject: Re: [leaf-user] Prism2_usb Kernel Panics - WISP
>
> I know that Bering-1.0 kernel modules are not compatible with WISP-Dist.
>
> I suggest that you download WISP-Dist kernel source and compile your
> modules against it.
>
> Derek Jenning
0200
To: [EMAIL PROTECTED]
Subject: Re: [leaf-user] Prism2_usb Kernel Panics - WISP
>
> I know that Bering-1.0 kernel modules are not compatible with WISP-Dist.
>
> I suggest that you download WISP-Dist kernel source and compile your
> modules against it.
>
> Derek Jenning
0200
To: [EMAIL PROTECTED]
Subject: Re: [leaf-user] Prism2_usb Kernel Panics - WISP
>
> I know that Bering-1.0 kernel modules are not compatible with WISP-Dist.
>
> I suggest that you download WISP-Dist kernel source and compile your
> modules against it.
>
> Derek Jenning
0200
To: [EMAIL PROTECTED]
Subject: Re: [leaf-user] Prism2_usb Kernel Panics - WISP
>
> I know that Bering-1.0 kernel modules are not compatible with WISP-Dist.
>
> I suggest that you download WISP-Dist kernel source and compile your
> modules against it.
>
> Derek Jenning
I am so pleased at getting this working :-)
Previous attempts at getting the atmelwlandriver working with the 2.4.18 kernel were
unsuccesful due I now realise to a kernel bug.
But with the latest WISP-2469 I was able to compile the usbvnetr ver 2.1.1 driver from
http://atmelwlandriver.source
I am currently taking a look at how to guarantee that multple Wireless USB
adapters will be recognised with their correct device name, and concluded the
easiest method is to read their MAC address and then use the 'ip' command to
set the appropriate device name.
To start with I have been tryin
ar form in
> http://leaf.sourceforge.net/devel/hzdrus/files/cfs-src.tar.gz
>
> Derek Jennings wrote:
> > I am currently taking a look at how to guarantee that multple Wireless
> > USB adapters will be recognised with their correct device name, and
> > concluded the easiest method is to
16 matches
Mail list logo
