Le Vendredi 31 Mai 2002 17:43, vous avez �crit :
> Hello,
> I was wondering if you could help me out with a little
> problem i'm having with initializing my PCMCIA card in
> Bering. The computer is a compaq deskpro p2 400mhz (not sure
> of the model #), with 256MB RAM, a 3Com 3c905 NIC, a ISA to
> PCMCIA (Vadem VG-469) adapter, and a Lucent Technologies
> orinoco SILVER card, with flash version 6.06. I downloaded
> the pcmcia_orinoco package and successfully got it to
> initialize. /var/log/syslog reports that the PCMCIA card is
> an Intersil Prism2 card, but then goes on to report that it
> "Looks like a Lucent/Agere firmware version 6.06". I'm
> assuming that the driver is being initialized correctly
> since syslog also reports that IBSS ad-hoc is supported
> under the card. When cardmgr tries to start the network
> ("executing ./network start eth1") it reports "/sbin/ifup:
> interface eth1 already configured" I added the base address
> # in /etc/default/pcmcia, but that did not help either.
This probably means that you have an auto eth1 in your interfaces file.
Read the doc:
http://leaf.sourceforge.net/devel/jnilo/buwireless.html#AEN1230
>My
> next step was going to be trying to initialize wavelan2_cs
> and see if maybe it is the driver. By the way, the computer
> beeps twice upon initialization of the card, the beeps being
> about 5 sec apart. What does this signify? iwconfig reports
> "Warning: Device eth1 has been compiled with version 12 of
> Wireless Extension, while we are using version 13. Some
> things may be broken..."
Two beeps are fine is they are on the same tone. If the second tone is lower
you have got a problem
>From
http://pcmcia-cs.sourceforge.net/ftp/doc/PCMCIA-HOWTO-4.html
"The cardmgr daemon is responsible for monitoring PCMCIA sockets, loading
client drivers when needed, and running user-level scripts in response to
card insertions and removals. It records its actions in the system log, but
also uses beeps to signal card status changes. The tones of the beeps
indicate success or failure of particular configuration steps. Two high beeps
indicate that a card was identified and configured successfully. A high beep
followed by a low beep indicates that a card was identified, but could not be
configured for some reason. One low beep indicates that a card could not be
identified."
> p.s. sorry if this is a repeat, i sent it to your
> sourceforge email address as well.
Please post your support request to the leaf-user list.
Jacques
_______________________________________________________________
Don't miss the 2002 Sprint PCS Application Developer's Conference
August 25-28 in Las Vegas -- http://devcon.sprintpcs.com/adp/index.cfm
------------------------------------------------------------------------
leaf-user mailing list: [EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/leaf-user
SR FAQ: http://leaf-project.org/pub/doc/docmanager/docid_1891.html
