kernel 2.6.19 + Cisco 350 Wireless adapter needs manual config - Debian

This is a discussion on kernel 2.6.19 + Cisco 350 Wireless adapter needs manual config - Debian ; hello, after upgrading from sarge to etch and switching from kernel 2.6.10 to self-compiled 2.6.19 my wireless cisco card is not working properly, because I need to configure it manually at every reboot: # iwconfig eth2_rename essid "*******" # iwconfig ...

+ Reply to Thread
Results 1 to 18 of 18

Thread: kernel 2.6.19 + Cisco 350 Wireless adapter needs manual config

  1. kernel 2.6.19 + Cisco 350 Wireless adapter needs manual config

    hello,
    after upgrading from sarge to etch and switching from kernel 2.6.10 to
    self-compiled 2.6.19 my wireless cisco card is not working properly, because
    I need to configure it manually at every reboot:
    # iwconfig eth2_rename essid "*******"
    # iwconfig eth2_rename key s:*******
    Besides, I would like to know a way to change the interface name
    from "eth2_rename" to a normal "eth2"...(It was configured as "eth1" in sarge
    and worked flawlessy).
    I am using the kernel cisco driver and the yenta-socket module in a sony vaio
    FX-802; the following is what the kernel says at boot-up:
    airo(): Finished probing for PCI adapters
    pcmcia: request for exclusive IRQ could not be fulfilled.
    pcmcia: the driver needs updating to supported shared IRQ lines.
    airo(eth2): cmd:111 status:7f11 rsp0:2 rsp1:0 rsp2:0
    airo(eth2): Doing fast bap_reads
    airo(eth2): WPA unsupported (only firmware versions 5.30.17 and greater
    support WPA. Detected 5.02.19)
    airo(eth2): MAC enabled 0:f:f8:4e:0:43
    eth2: index 0x05: , Vpp 5.0, irq 10, io 0x0100-0x013f

    I don't know why, but after that ifconfig reports only an "eth2_rename"
    wireless interface.

    --
    On this laptop no Windows system survives and LINUX POWER reigns UNLIMITED.
    Successfully Microsoft free since December 2002.


    --
    To UNSUBSCRIBE, email to debian-laptop-REQUEST@lists.debian.org
    with a subject of "unsubscribe". Trouble? Contact listmaster@lists.debian.org

  2. Re: kernel 2.6.19 + Cisco 350 Wireless adapter needs manual config

    Hi,

    On Don, 11 Jän 2007, Mauro Darida wrote:

    > after upgrading from sarge to etch and switching from kernel 2.6.10 to
    > self-compiled 2.6.19 my wireless cisco card is not working properly, because
    > I need to configure it manually at every reboot:
    > # iwconfig eth2_rename essid "*******"
    > # iwconfig eth2_rename key s:*******


    thats clearly a bug of UDEV. I suggest you purge
    ifrename
    udev
    and delete the /etc/udev /etc/hotplug
    (a backup is always nice)
    and then make a fresh reinstall of udev.

    and .. for laptops the network-manager is really nice addon.

    > Besides, I would like to know a way to change the interface name
    > from "eth2_rename" to a normal "eth2"...(It was configured as "eth1" in sarge
    > and worked flawlessy).
    > I am using the kernel cisco driver and the yenta-socket module in a sony vaio
    > FX-802; the following is what the kernel says at boot-up:
    > airo(): Finished probing for PCI adapters
    > pcmcia: request for exclusive IRQ could not be fulfilled.
    > pcmcia: the driver needs updating to supported shared IRQ lines.
    > airo(eth2): cmd:111 status:7f11 rsp0:2 rsp1:0 rsp2:0
    > airo(eth2): Doing fast bap_reads
    > airo(eth2): WPA unsupported (only firmware versions 5.30.17 and greater
    > support WPA. Detected 5.02.19)
    > airo(eth2): MAC enabled 0:f:f8:4e:0:43
    > eth2: index 0x05: , Vpp 5.0, irq 10, io 0x0100-0x013f
    >
    > I don't know why, but after that ifconfig reports only an "eth2_rename"
    > wireless interface.


    --
    Florian Reitmeir

  3. Re: kernel 2.6.19 + Cisco 350 Wireless adapter needs manual config

    On Friday 12 January 2007 18:41, Florian Reitmeir wrote:
    > thats clearly a bug of UDEV. I suggest you purge
    > ifrename
    > udev
    > and delete the /etc/udev /etc/hotplug
    > (a backup is always nice)
    > and then make a fresh reinstall of udev.

    ifrename it is not installed on my system; I did what you suggested and now my
    card is not recognised at all. Tried also modprobe airo with no results.
    Noticed the following message at boot-up:
    udev_rules_init:
    /etc/udev/rules.d/z99_hal.rules: no such file or directory

    Any suggestion?
    --
    On this laptop no Windows system survives and LINUX POWER reigns UNLIMITED.
    Successfully Microsoft free since December 2002.


    --
    To UNSUBSCRIBE, email to debian-laptop-REQUEST@lists.debian.org
    with a subject of "unsubscribe". Trouble? Contact listmaster@lists.debian.org

  4. Re: kernel 2.6.19 + Cisco 350 Wireless adapter needs manual config

    On Fri, Jan 12, 2007 at 22:13:44 +0100, Mauro Darida wrote:
    > On Friday 12 January 2007 18:41, Florian Reitmeir wrote:
    > > thats clearly a bug of UDEV. I suggest you purge
    > > ifrename
    > > udev
    > > and delete the /etc/udev /etc/hotplug
    > > (a backup is always nice)
    > > and then make a fresh reinstall of udev.

    > ifrename it is not installed on my system; I did what you suggested and now my
    > card is not recognised at all. Tried also modprobe airo with no results.
    > Noticed the following message at boot-up:
    > udev_rules_init:
    > /etc/udev/rules.d/z99_hal.rules: no such file or directory
    >
    > Any suggestion?


    It is normally not a good idea to start deleting directories in /etc,
    unless you know exactly what you are doing. I think you should first
    restore /etc/udev and /etc/hotplug. If you did not make backups you will
    have to reinstall all packages which are supposed to have files in these
    directories. (z99_hal.rules comes from package "hal", for example.)

    The following two commands should give you a list of all packages which
    you have to reinstall:

    dpkg -S etc/udev/ | cut -d: -f1 | sed 's/, /\n/g' | sort -u
    dpkg -S etc/hotplug/ | cut -d: -f1 | sed 's/, /\n/g' | sort -u

    Reboot after you have reinstalled all the packages. Then we have to
    check your network interface naming rules. For a start we need the
    output of the following two commands:

    ip link
    cat /etc/udev/rules.d/z25_persistent-net.rules

    --
    Regards,
    Florian


    --
    To UNSUBSCRIBE, email to debian-laptop-REQUEST@lists.debian.org
    with a subject of "unsubscribe". Trouble? Contact listmaster@lists.debian.org

  5. Re: kernel 2.6.19 + Cisco 350 Wireless adapter needs manual config

    Hi,

    On Fre, 12 Jän 2007, Mauro Darida wrote:

    > On Friday 12 January 2007 18:41, Florian Reitmeir wrote:
    > > thats clearly a bug of UDEV. I suggest you purge
    > > ifrename
    > > udev
    > > and delete the /etc/udev /etc/hotplug
    > > (a backup is always nice)
    > > and then make a fresh reinstall of udev.

    > ifrename it is not installed on my system; I did what you suggested and now my
    > card is not recognised at all. Tried also modprobe airo with no results.
    > Noticed the following message at boot-up:
    > udev_rules_init:
    > /etc/udev/rules.d/z99_hal.rules: no such file or directory
    >
    > Any suggestion?


    you really did a
    dpkg --purge udev
    dpkg --purge ifrename
    dpkg --purge hotplug
    ?

    if you did correctly and reinstalled udev everything should work normally
    and the files should not missing anymore.

    ok here .. in commands ..

    apt-get --purge remove udev ifrename hotplug
    rm -Rf /etc/udev
    apt-get install udev hald



    --
    Florian Reitmeir

  6. Re: kernel 2.6.19 + Cisco 350 Wireless adapter needs manual config

    Florian Reitmeir wrote:
    > Hi,
    >
    > On Fre, 12 Jän 2007, Mauro Darida wrote:
    >
    >> On Friday 12 January 2007 18:41, Florian Reitmeir wrote:
    >>> thats clearly a bug of UDEV. I suggest you purge
    >>> ifrename
    >>> udev
    >>> and delete the /etc/udev /etc/hotplug
    >>> (a backup is always nice)
    >>> and then make a fresh reinstall of udev.

    >> ifrename it is not installed on my system; I did what you suggested and now my
    >> card is not recognised at all. Tried also modprobe airo with no results.
    >> Noticed the following message at boot-up:
    >> udev_rules_init:
    >> /etc/udev/rules.d/z99_hal.rules: no such file or directory
    >>
    >> Any suggestion?

    >
    > you really did a
    > dpkg --purge udev
    > dpkg --purge ifrename
    > dpkg --purge hotplug
    > ?
    >
    > if you did correctly and reinstalled udev everything should work normally
    > and the files should not missing anymore.
    >
    > ok here .. in commands ..
    >
    > apt-get --purge remove udev ifrename hotplug
    > rm -Rf /etc/udev
    > apt-get install udev hald
    >
    >
    >

    I do not know if this will help but I get a slightly older kernel
    running with this adapter.
    I have to admit even if I'm not yet under 2.6.19, I'm currently under
    Etch 2.6.18-7.
    Anyhow I faced to a very annoying issue with a HP Laptop Omnibook900 and
    exactly the same Cisco 350 Wireless adapter.
    When using the Debian package linux-image package (2.6.18-7) from Debian
    the pcmcia card is configured an work like a charm.

    But when I do use my own compiled kernel I have always the same problem
    (I have tried many .config w/o any success):
    - The card is recognized in both cases (Yenta CardBus Bridge) and I do
    have equivalent tons of kprintf messages with my compiled airo module I
    always have the following:

    airo(eth0): BAP error 4000 0
    airo(eth0): Bad size 2630
    airo(eth0): BAP error 4000 0
    airo(eth0): Bad size 2636
    airo(eth0): airo: BAP setup error too many retries
    ....

    I look at any possible Google tips prior getting here asking stupid
    questions. At cisco web side it's all now protected and inaccessible the
    other available driver on sourceforge project page seems to have been
    abandoned.
    I'm alone in that case? Anyone could assist me with a working suggestion?

    Or may be I'm just facing to one of the numerous licensing issue Debian
    could have with Cisco/Aironet?

    Thanks in anticipation,
    JL


    --
    To UNSUBSCRIBE, email to debian-laptop-REQUEST@lists.debian.org
    with a subject of "unsubscribe". Trouble? Contact listmaster@lists.debian.org

  7. Re: kernel 2.6.19 + Cisco 350 Wireless adapter needs manual config

    On Saturday 13 January 2007 15:08, Florian Reitmeir wrote:
    > you really did a
    > dpkg --purge udev
    > dpkg --purge ifrename
    > dpkg --purge hotplug
    > ?
    >
    > if you did correctly and reinstalled udev everything should work normally
    > and the files should not missing anymore.
    >
    > ok here .. in commands ..
    >
    > apt-get --purge remove udev ifrename hotplug
    > rm -Rf /etc/udev
    > apt-get install udev hald

    Yes, I did. Please note ifrename was not installed and hotplug was not
    installed, too, because it conflicts with udev.
    So I just did aptitude purge udev and removed /etc/udev. Then I purged hal
    (not hald, there is no package named "hald") and reinstalled it to
    rigenerate /etc/udev/rules.d/z99_hal.rules.
    I think, as a last resort, I will try to install debian kernel 2.6.18
    pre-compiled.
    --
    On this laptop no Windows system survives and LINUX POWER reigns UNLIMITED.
    Successfully Microsoft free since December 2002.


    --
    To UNSUBSCRIBE, email to debian-laptop-REQUEST@lists.debian.org
    with a subject of "unsubscribe". Trouble? Contact listmaster@lists.debian.org

  8. Re: kernel 2.6.19 + Cisco 350 Wireless adapter needs manual config

    On Monday 15 January 2007 10:30, Jean-Louis Crouzet wrote:
    > Or may be I'm just facing to one of the numerous licensing issue Debian
    > could have with Cisco/Aironet?

    I do not think so. I don't know what was your previous kernel, but, if that
    can help, I think in my case the problem is that the pcmcia setting has been
    completely changed after kernel 2.6.15, which uses udev and a new pcmcia
    module which supersedes the old pcmcia-cs package setting. This is why my
    aironet 350 cisco is not recognised anymore. The cisco kernel module should
    be the same.
    The problem (for me) is that I cannot retrive _any_ useful information on this
    new pcmcia setting.
    I have only found a new "pcmcia howto" which is of no help, talking about
    a "resource database" (what is a resource database?) and an "udev rule"
    (which one?).
    --
    On this laptop no Windows system survives and LINUX POWER reigns UNLIMITED.
    Successfully Microsoft free since December 2002.


    --
    To UNSUBSCRIBE, email to debian-laptop-REQUEST@lists.debian.org
    with a subject of "unsubscribe". Trouble? Contact listmaster@lists.debian.org

  9. Re: kernel 2.6.19 + Cisco 350 Wireless adapter needs manual config

    On Saturday 13 January 2007 12:10, Florian Kulzer wrote:
    > ip link
    > cat /etc/udev/rules.d/z25_persistent-net.rules

    ifi:~# ip link
    -su: ip: command not found
    ifi:~# cat /etc/udev/rules.d/z25_persistent-net.rules
    # This file was automatically generated by the /lib/udev/write_net_rules
    # program, probably run by the persistent-net-generator.rules rules file.
    #
    # You can modify it, as long as you keep each rule on a single line.
    # MAC addresses must be written in lowercase.

    SUBSYSTEM=="net", DRIVERS=="?*", ATTRS{address}=="08:00:46:90:dc:aa",
    NAME="eth0"

    SUBSYSTEM=="net", DRIVERS=="?*", ATTRS{address}=="08:00:46:03:01:4c:3e:40",
    NAME="eth1"

    SUBSYSTEM=="net", DRIVERS=="?*", ATTRS{address}=="00:0f:f8:4e:00:43",
    NAME="eth2_rename"

    --
    On this laptop no Windows system survives and LINUX POWER reigns UNLIMITED.
    Successfully Microsoft free since December 2002.


    --
    To UNSUBSCRIBE, email to debian-laptop-REQUEST@lists.debian.org
    with a subject of "unsubscribe". Trouble? Contact listmaster@lists.debian.org

  10. Re: kernel 2.6.19 + Cisco 350 Wireless adapter needs manual config

    On Mon, 15 Jän 2007, Mauro Darida wrote:

    > On Saturday 13 January 2007 15:08, Florian Reitmeir wrote:
    > > you really did a
    > > dpkg --purge udev
    > > dpkg --purge ifrename
    > > dpkg --purge hotplug
    > > ?
    > >
    > > if you did correctly and reinstalled udev everything should work normally
    > > and the files should not missing anymore.
    > >
    > > ok here .. in commands ..
    > >
    > > apt-get --purge remove udev ifrename hotplug
    > > rm -Rf /etc/udev
    > > apt-get install udev hald

    > Yes, I did. Please note ifrename was not installed and hotplug was not
    > installed, too, because it conflicts with udev.
    > So I just did aptitude purge udev and removed /etc/udev. Then I purged hal
    > (not hald, there is no package named "hald") and reinstalled it to
    > rigenerate /etc/udev/rules.d/z99_hal.rules.
    > I think, as a last resort, I will try to install debian kernel 2.6.18
    > pre-compiled.


    then i'm sorry, i believe UDEV is the problem. So in doubt please make a bug
    report against it (before reinstall).


    --
    Florian Reitmeir

  11. Re: kernel 2.6.19 + Cisco 350 Wireless adapter needs manual config

    On Mon, Jan 15, 2007 at 23:09:48 +0100, Mauro Darida wrote:
    > On Saturday 13 January 2007 12:10, Florian Kulzer wrote:
    > > ip link
    > > cat /etc/udev/rules.d/z25_persistent-net.rules

    > ifi:~# ip link
    > -su: ip: command not found


    Then try

    /sbin/ifconfig

    > ifi:~# cat /etc/udev/rules.d/z25_persistent-net.rules
    > # This file was automatically generated by the /lib/udev/write_net_rules
    > # program, probably run by the persistent-net-generator.rules rules file.
    > #
    > # You can modify it, as long as you keep each rule on a single line.
    > # MAC addresses must be written in lowercase.
    >
    > SUBSYSTEM=="net", DRIVERS=="?*", ATTRS{address}=="08:00:46:90:dc:aa",
    > NAME="eth0"
    >
    > SUBSYSTEM=="net", DRIVERS=="?*", ATTRS{address}=="08:00:46:03:01:4c:3e:40",
    > NAME="eth1"
    >
    > SUBSYSTEM=="net", DRIVERS=="?*", ATTRS{address}=="00:0f:f8:4e:00:43",
    > NAME="eth2_rename"


    --
    Regards,
    Florian


    --
    To UNSUBSCRIBE, email to debian-laptop-REQUEST@lists.debian.org
    with a subject of "unsubscribe". Trouble? Contact listmaster@lists.debian.org

  12. Re: kernel 2.6.19 + Cisco 350 Wireless adapter needs manual config

    On Tuesday 16 January 2007 12:13, Florian Kulzer wrote:
    > Then try
    >
    > /sbin/ifconfig

    ifi:~# /sbin/ifconfig
    eth0 Link encap:Ethernet HWaddr 08:00:46:90C:AA
    UP BROADCAST MULTICAST MTU:1500 Metric:1
    RX packets:0 errors:0 dropped:0 overruns:0 frame:0
    TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
    collisions:0 txqueuelen:1000
    RX bytes:0 (0.0 b) TX bytes:0 (0.0 b)
    Interrupt:10 Base address:0x8800

    lo Link encap:Local Loopback
    inet addr:127.0.0.1 Mask:255.0.0.0
    UP LOOPBACK RUNNING MTU:16436 Metric:1
    RX packets:16 errors:0 dropped:0 overruns:0 frame:0
    TX packets:16 errors:0 dropped:0 overruns:0 carrier:0
    collisions:0 txqueuelen:0
    RX bytes:800 (800.0 b) TX bytes:800 (800.0 b)

    --
    On this laptop no Windows system survives and LINUX POWER reigns UNLIMITED.
    Successfully Microsoft free since December 2002.


    --
    To UNSUBSCRIBE, email to debian-laptop-REQUEST@lists.debian.org
    with a subject of "unsubscribe". Trouble? Contact listmaster@lists.debian.org

  13. Re: kernel 2.6.19 + Cisco 350 Wireless adapter needs manual config

    On Thu, Jan 18, 2007 at 20:07:59 +0100, Mauro Darida wrote:
    > On Tuesday 16 January 2007 12:13, Florian Kulzer wrote:
    > > Then try
    > >
    > > /sbin/ifconfig

    > ifi:~# /sbin/ifconfig
    > eth0 Link encap:Ethernet HWaddr 08:00:46:90C:AA
    > UP BROADCAST MULTICAST MTU:1500 Metric:1
    > RX packets:0 errors:0 dropped:0 overruns:0 frame:0
    > TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
    > collisions:0 txqueuelen:1000
    > RX bytes:0 (0.0 b) TX bytes:0 (0.0 b)
    > Interrupt:10 Base address:0x8800
    >
    > lo Link encap:Local Loopback
    > inet addr:127.0.0.1 Mask:255.0.0.0
    > UP LOOPBACK RUNNING MTU:16436 Metric:1
    > RX packets:16 errors:0 dropped:0 overruns:0 frame:0
    > TX packets:16 errors:0 dropped:0 overruns:0 carrier:0
    > collisions:0 txqueuelen:0
    > RX bytes:800 (800.0 b) TX bytes:800 (800.0 b)


    [ It would help if you kept the other relevant information in the
    thread. How are people supposed to help you if they do not know the
    context of this message? ]

    I assume that eth0 is not the Cisco wireless adapter. Check if you can
    see the Cisco adapter with "ls -l /sys/class/net/". If no device is
    created even after you do "modprobe airo" then something is probably
    broken with your udev. Did you restore /etc/udev and /etc/hotplug like I
    suggested in my earlier mail?

    --
    Regards,
    Florian


    --
    To UNSUBSCRIBE, email to debian-laptop-REQUEST@lists.debian.org
    with a subject of "unsubscribe". Trouble? Contact listmaster@lists.debian.org

  14. Re: kernel 2.6.19 + Cisco 350 Wireless adapter needs manual config

    On Thursday 18 January 2007 21:48, Florian Kulzer wrote:
    > On Thu, Jan 18, 2007 at 20:07:59 +0100, Mauro Darida wrote:
    > > On Tuesday 16 January 2007 12:13, Florian Kulzer wrote:
    > > > Then try
    > > >
    > > > /sbin/ifconfig

    > >
    > > ifi:~# /sbin/ifconfig
    > > eth0 Link encap:Ethernet HWaddr 08:00:46:90C:AA
    > > UP BROADCAST MULTICAST MTU:1500 Metric:1
    > > RX packets:0 errors:0 dropped:0 overruns:0 frame:0
    > > TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
    > > collisions:0 txqueuelen:1000
    > > RX bytes:0 (0.0 b) TX bytes:0 (0.0 b)
    > > Interrupt:10 Base address:0x8800
    > >
    > > lo Link encap:Local Loopback
    > > inet addr:127.0.0.1 Mask:255.0.0.0
    > > UP LOOPBACK RUNNING MTU:16436 Metric:1
    > > RX packets:16 errors:0 dropped:0 overruns:0 frame:0
    > > TX packets:16 errors:0 dropped:0 overruns:0 carrier:0
    > > collisions:0 txqueuelen:0
    > > RX bytes:800 (800.0 b) TX bytes:800 (800.0 b)

    >
    > [ It would help if you kept the other relevant information in the
    > thread. How are people supposed to help you if they do not know the
    > context of this message? ]
    >
    > I assume that eth0 is not the Cisco wireless adapter. Check if you can
    > see the Cisco adapter with "ls -l /sys/class/net/". If no device is
    > created even after you do "modprobe airo" then something is probably
    > broken with your udev. Did you restore /etc/udev and /etc/hotplug like I
    > suggested in my earlier mail?

    Yes, for udev. I repeat that hotplug is not installable because it conflicts
    with udev. If I install hotplug it removes udev and vice-versa.
    Further testing reveals that the debian kernel 2.6.18-3 gives the same results
    and the cisco card remains idle and no device is created even after modprobe
    airo.
    I managed to make the cisco card to work, as previously said, only with my
    2.6.19.1 enabling the deprecated ioctl pcmcia interface, which gives the odd
    device name "eth2_rename" (after some minutes) which then I need to configure
    manually, which is unsatisfactory.
    If the ioctl pcmcia is not enabled, then no device is created.

    --
    On this laptop no Windows system survives and LINUX POWER reigns UNLIMITED.
    Successfully Microsoft free since December 2002.


    --
    To UNSUBSCRIBE, email to debian-laptop-REQUEST@lists.debian.org
    with a subject of "unsubscribe". Trouble? Contact listmaster@lists.debian.org

  15. Re: kernel 2.6.19 + Cisco 350 Wireless adapter needs manual config

    On Fri, Jan 19, 2007 at 00:05:59 +0100, Mauro Darida wrote:
    > On Thursday 18 January 2007 21:48, Florian Kulzer wrote:
    > > On Thu, Jan 18, 2007 at 20:07:59 +0100, Mauro Darida wrote:
    > > > On Tuesday 16 January 2007 12:13, Florian Kulzer wrote:
    > > > > Then try
    > > > >
    > > > > /sbin/ifconfig
    > > >
    > > > ifi:~# /sbin/ifconfig
    > > > eth0 Link encap:Ethernet HWaddr 08:00:46:90C:AA
    > > > UP BROADCAST MULTICAST MTU:1500 Metric:1
    > > > RX packets:0 errors:0 dropped:0 overruns:0 frame:0
    > > > TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
    > > > collisions:0 txqueuelen:1000
    > > > RX bytes:0 (0.0 b) TX bytes:0 (0.0 b)
    > > > Interrupt:10 Base address:0x8800
    > > >
    > > > lo Link encap:Local Loopback
    > > > inet addr:127.0.0.1 Mask:255.0.0.0
    > > > UP LOOPBACK RUNNING MTU:16436 Metric:1
    > > > RX packets:16 errors:0 dropped:0 overruns:0 frame:0
    > > > TX packets:16 errors:0 dropped:0 overruns:0 carrier:0
    > > > collisions:0 txqueuelen:0
    > > > RX bytes:800 (800.0 b) TX bytes:800 (800.0 b)

    > >
    > > [ It would help if you kept the other relevant information in the
    > > thread. How are people supposed to help you if they do not know the
    > > context of this message? ]
    > >
    > > I assume that eth0 is not the Cisco wireless adapter. Check if you can
    > > see the Cisco adapter with "ls -l /sys/class/net/". If no device is
    > > created even after you do "modprobe airo" then something is probably
    > > broken with your udev. Did you restore /etc/udev and /etc/hotplug like I
    > > suggested in my earlier mail?

    > Yes, for udev. I repeat that hotplug is not installable because it conflicts
    > with udev. If I install hotplug it removes udev and vice-versa.


    I did not say that you should reinstall hotplug, I suggested that you
    should reinstall all currently installed packages which are supposed to
    have files in /etc/hotplug. You stated in an earlier email that you had
    followed the advice of someone else who had told you to delete /etc/udev
    and /etc/hotplug. I can only repeat that I think it is important to get
    all those files back if you want udev to work as expected. In my earlier
    mail I have proposed a method to find out which packages were affected
    and hence need to be reinstalled. I think it is not enough to just
    reinstall udev and hal.

    > Further testing reveals that the debian kernel 2.6.18-3 gives the same results
    > and the cisco card remains idle and no device is created even after modprobe
    > airo.
    > I managed to make the cisco card to work, as previously said, only with my
    > 2.6.19.1 enabling the deprecated ioctl pcmcia interface, which gives the odd
    > device name "eth2_rename" (after some minutes) which then I need to configure
    > manually, which is unsatisfactory.
    > If the ioctl pcmcia is not enabled, then no device is created.


    I cannot comment on the specific issues of the Cisco hardware, but I
    think that once the device is recognized you should be able to change
    its name (after the next reboot) by modifying this stanza in your
    /etc/udev/rules.d/z25_persistent-net.rules:

    SUBSYSTEM=="net", DRIVERS=="?*", ATTRS{address}=="00:0f:f8:4e:00:43",
    NAME="eth2_rename"

    You have to check if 00:0f:f8:4e:00:43 is really the mac address of the
    Cisco card. See also /usr/share/doc/udev/writing_udev_rules/index.html.

    --
    Regards,
    Florian


    --
    To UNSUBSCRIBE, email to debian-laptop-REQUEST@lists.debian.org
    with a subject of "unsubscribe". Trouble? Contact listmaster@lists.debian.org

  16. Re: kernel 2.6.19 + Cisco 350 Wireless adapter needs manual config:SOLVED

    On Friday 19 January 2007 10:38, Florian Kulzer wrote:
    > On Fri, Jan 19, 2007 at 00:05:59 +0100, Mauro Darida wrote:
    > > On Thursday 18 January 2007 21:48, Florian Kulzer wrote:
    > > > On Thu, Jan 18, 2007 at 20:07:59 +0100, Mauro Darida wrote:
    > > > > On Tuesday 16 January 2007 12:13, Florian Kulzer wrote:
    > > > > > Then try
    > > > > >
    > > > > > /sbin/ifconfig
    > > > >
    > > > > ifi:~# /sbin/ifconfig
    > > > > eth0 Link encap:Ethernet HWaddr 08:00:46:90C:AA
    > > > > UP BROADCAST MULTICAST MTU:1500 Metric:1
    > > > > RX packets:0 errors:0 dropped:0 overruns:0 frame:0
    > > > > TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
    > > > > collisions:0 txqueuelen:1000
    > > > > RX bytes:0 (0.0 b) TX bytes:0 (0.0 b)
    > > > > Interrupt:10 Base address:0x8800
    > > > >
    > > > > lo Link encap:Local Loopback
    > > > > inet addr:127.0.0.1 Mask:255.0.0.0
    > > > > UP LOOPBACK RUNNING MTU:16436 Metric:1
    > > > > RX packets:16 errors:0 dropped:0 overruns:0 frame:0
    > > > > TX packets:16 errors:0 dropped:0 overruns:0 carrier:0
    > > > > collisions:0 txqueuelen:0
    > > > > RX bytes:800 (800.0 b) TX bytes:800 (800.0 b)
    > > >
    > > > [ It would help if you kept the other relevant information in the
    > > > thread. How are people supposed to help you if they do not know the
    > > > context of this message? ]
    > > >
    > > > I assume that eth0 is not the Cisco wireless adapter. Check if you can
    > > > see the Cisco adapter with "ls -l /sys/class/net/". If no device is
    > > > created even after you do "modprobe airo" then something is probably
    > > > broken with your udev. Did you restore /etc/udev and /etc/hotplug like
    > > > I suggested in my earlier mail?

    > >
    > > Yes, for udev. I repeat that hotplug is not installable because it
    > > conflicts with udev. If I install hotplug it removes udev and vice-versa.

    >
    > I did not say that you should reinstall hotplug, I suggested that you
    > should reinstall all currently installed packages which are supposed to
    > have files in /etc/hotplug. You stated in an earlier email that you had

    The directory /etc/hotplug is present only with hotplug installed. If hotplug
    is not installed because udev and hal are installed, then
    only /etc/hotplug.d/ exists.
    > followed the advice of someone else who had told you to delete /etc/udev
    > and /etc/hotplug. I can only repeat that I think it is important to get
    > all those files back if you want udev to work as expected. In my earlier
    > mail I have proposed a method to find out which packages were affected
    > and hence need to be reinstalled. I think it is not enough to just
    > reinstall udev and hal.
    >
    > > Further testing reveals that the debian kernel 2.6.18-3 gives the same
    > > results and the cisco card remains idle and no device is created even
    > > after modprobe airo.
    > > I managed to make the cisco card to work, as previously said, only with
    > > my 2.6.19.1 enabling the deprecated ioctl pcmcia interface, which gives
    > > the odd device name "eth2_rename" (after some minutes) which then I need
    > > to configure manually, which is unsatisfactory.
    > > If the ioctl pcmcia is not enabled, then no device is created.

    >
    > I cannot comment on the specific issues of the Cisco hardware, but I
    > think that once the device is recognized you should be able to change
    > its name (after the next reboot) by modifying this stanza in your
    > /etc/udev/rules.d/z25_persistent-net.rules:
    >
    > SUBSYSTEM=="net", DRIVERS=="?*", ATTRS{address}=="00:0f:f8:4e:00:43",
    > NAME="eth2_rename"

    It is not only a matter of interface naming, it also makes me to reconfigure
    the card manually, which is annoying.
    > You have to check if 00:0f:f8:4e:00:43 is really the mac address of the
    > Cisco card. See also /usr/share/doc/udev/writing_udev_rules/index.html.

    Yes, it is.
    I found that I cannot reproduce the "eth2_rename" spit out of udev. If I
    recompile the kernel with udev and hal installed, now no interface is
    created, even with ioctl pcmcia selected.
    After many errors and trials, I found that purging udev and hal and installing
    hotplug (I found that pcmcia-cs was left installed after the upgrade: a trial
    with no pcmcia-cs present to see whether it interfered with pcmciautils or
    something else proved to be insignificant) is the solution to my problem and
    the card works as previously with sarge and 2.6.10.
    I believe this is just my old setting with sarge, that's why it works; the new
    one with udev, hal and pcmciautils just does not work. I believe udev is
    somewhat broken, but I am no kernel expert, so I could not file a bug about
    it.
    Thank for replying to all.
    > --
    > Regards,
    > Florian


    --
    On this laptop no Windows system survives and LINUX POWER reigns UNLIMITED.
    Successfully Microsoft free since December 2002.


    --
    To UNSUBSCRIBE, email to debian-laptop-REQUEST@lists.debian.org
    with a subject of "unsubscribe". Trouble? Contact listmaster@lists.debian.org

  17. Re: kernel 2.6.19 + Cisco 350 Wireless adapter needs manual config:SOLVED


    Mauro Darida wrote (Sun 2007-Jan-21 22:05:36 +0100):

    > On Friday 19 January 2007 10:38, Florian Kulzer wrote:

    ...
    > > I did not say that you should reinstall hotplug, I suggested that you
    > > should reinstall all currently installed packages which are supposed to
    > > have files in /etc/hotplug. You stated in an earlier email that you had

    > The directory /etc/hotplug is present only with hotplug installed...


    mcg@coach:~$ dpkg -S /etc/hotplug
    kcontrol, libgphoto2-2, alsa-base: /etc/hotplug


    Cheers, Marcus

    --
    Marcus C. Gottwald http://www.inf.fu-berlin.de/~gottwald/


    --
    To UNSUBSCRIBE, email to debian-laptop-REQUEST@lists.debian.org
    with a subject of "unsubscribe". Trouble? Contact listmaster@lists.debian.org

  18. Re: kernel 2.6.19 + Cisco 350 Wireless adapter needs manual config:SOLVED

    On Son, 21 Jän 2007, Mauro Darida wrote:

    > I believe this is just my old setting with sarge, that's why it works; the new
    > one with udev, hal and pcmciautils just does not work. I believe udev is
    > somewhat broken, but I am no kernel expert, so I could not file a bug about
    > it.
    > Thank for replying to all.


    please simple do report a bug at
    http://bugs.debian.org/udev
    or just write your knowledge to:
    http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=405845

    just write your problem, and your solution, so maybe someone in the future
    will correct udev.

    --
    Florian Reitmeir

+ Reply to Thread