Uli Kunitz wrote:
> Could you send us a more complete log from plugging in the device
> until the error happens?
Here is it:
--- /var/log/kern.log --
May 8 11:38:33 mybox kernel: usb 3-6: USB disconnect, address 3
May 8 11:43:45 mybox kernel: usb 3-6: new high speed USB device u
Am 07.05.2007 um 22:10 schrieb Daniel Drake:
> Lucio Crusca wrote:
>> Alle 19:19, lunedì 7 maggio 2007, Lucio Crusca ha scritto:
>>> # ifconfig eth5 up
>>> SIOCSIFFLAGS: Connection timeout
>>> but this should be the first thing to do before doing anything
>>> else. I'm
>>> stuck. iwevent output
Daniel wrote:
> Please file a bug for this at http://bugzilla.kernel.org
Thank you very much indeed for the clarification. I've filed bug #8447,
however I've realized that the bug is present only when using a 686 kernel on
a Pentium4 hardware. Recompiling the kernel and having it Pentium4 optimiz
Lucio Crusca wrote:
> ifconfig $WLESS_IF up
> iwconfig $WLESS_IF mode managed
> iwconfig $WLESS_IF rate 2Mb
> iwconfig $WLESS_IF essid "videokernel"
> ifconfig $WLESS_IF 192.168.1.22 netmask 255.255.255.0
> route add default gw 192.168.1.1 dev $WLESS_IF
> wpa_supplicant -Bw -c /etc/wpa_supplicant/w
Lucio Crusca wrote:
> Alle 19:19, lunedì 7 maggio 2007, Lucio Crusca ha scritto:
>> # ifconfig eth5 up
>> SIOCSIFFLAGS: Connection timeout
>> but this should be the first thing to do before doing anything else. I'm
>> stuck. iwevent output is plain silence.
>
> I've forgotten the relevant kern.lo
I've dug a bit through the kernel sources.
The timeout is set to one second (zd_usb.c) and it's being honoured like it
should; the "time ifconfig eth5 up" command reports
real0m1.004s
So the reported error is the actual reason for the failure. The device is
expected to reply to something
Alle 19:19, lunedì 7 maggio 2007, Lucio Crusca ha scritto:
> # ifconfig eth5 up
> SIOCSIFFLAGS: Connection timeout
> but this should be the first thing to do before doing anything else. I'm
> stuck. iwevent output is plain silence.
I've forgotten the relevant kern.log
May 7 19:07:36 Acaja-Tour
Daniel Drake wrote:
> Feel free to volunteer.
Tried. Posted. It doesn't work. And now?
> Personally I'm more than happy with my distro's
> network configuration scripts and don't feel the need to reinvent the
> wheel.
Maybe in your case is like reinventing the wheel, but in other cases it seems
Lucio Crusca wrote:
> Ok then. Why don't we put on the website a minimal script to bring up an
> interface with zd1211rw? Seems to me that, if distro scripts cause a lot of
> problems, we would make a lot of users happy...
Feel free to volunteer. Personally I'm more than happy with my distro's
I (Lucio Crusca) wrote:
> Ok then. Why don't we put on the website a minimal script to bring up an
> interface with zd1211rw? Seems to me that, if distro scripts cause a lot of
> problems, we would make a lot of users happy...
Here is my script (static ip):
8x--
#!/bin/bash -x
PAT
Alle 17:14, lunedì 7 maggio 2007, hai scritto:
> I don't think iwevent prints those messages.
Er... you are right... it had to be the kernel printk. iwevent was silent.
> Nevertheless, this is
> implying that dhclient brings the network interface down.
Ok, I trust you and the logs, but I still c
Lucio Crusca wrote:
> While dhclient is trying to get in touch with the AP, iwevent
> says:
>
> May 7 15:22:15 Acaja-Tour kernel: zd1211rw 3-5:1.0: zd_usb_enable_int()
> May 7 15:22:15 Acaja-Tour kernel: zd1211rw 3-5:1.0: zd_usb_enable_int()
> submit urb e86d1e40
> May 7 15:22:15 Acaja-Tour ke
Daniel Drake wrote:
> There are no errors in your logs, but association did not complete. You
> should now enable softmac debug messages, and also run "iwevent" in
> another console while attempting to connect.
>
> Daniel
I've enabled softmac debug messages (and also 802.11 stack debug messages).
Lucio Crusca wrote:
> I run 2.6.21.1 vanilla, with .config "oldconfigured" from Debian 2.6.18, and
> zd1211 debugging turned
> on. Here is what it says when I plug the adapter:
There are no errors in your logs, but association did not complete. You
should now enable softmac debug messages, and
Hi all,
I've just bought a new GigaFast WF748-CUI. I already had three of those adapter
and they were 0ACE:1211.
But now this last one is 0ACE:1215. Although the chipset should be supported, I
can't manage to make
the thing work. I use the following commands to configure the interface:
ifconf
15 matches
Mail list logo
