Orinoco wifi driver fails load on startup but can load it manually - Help

This is a discussion on Orinoco wifi driver fails load on startup but can load it manually - Help ; I have a Dell Inspiron 7500 running Mandrake 10.1. I have a netprofile setup for a Linksys wireless NIC that uses the Orinoco drivers. The NIC was detected on setup so it's not an issue of the OS not seeing ...

+ Reply to Thread
Results 1 to 3 of 3

Thread: Orinoco wifi driver fails load on startup but can load it manually

  1. Orinoco wifi driver fails load on startup but can load it manually

    I have a Dell Inspiron 7500 running Mandrake 10.1. I have a netprofile
    setup for a Linksys wireless NIC that uses the Orinoco drivers. The NIC
    was detected on setup so it's not an issue of the OS not seeing the
    hardware.

    On startup I select the wireless netprofile which loads the orinoco,
    orinoco_cs and ds modules when pcmcia runs. What doesn't get loaded is a
    module called yenta_socket.

    If I rmmod the orinoco modules then /etc/init.d/pcmcia restart all modules
    get loaded correctly including the yenta_socket. I can then run the
    /etc/init.d/network script and get an IP via DHCP.

    What I can't figure out is why yenta_socket isn't getting loaded on
    startup (cold or warm boot).

    Here's a list of the modules loaded when everything is working;

    [root@i7500l ]# lsmod
    Module Size Used by
    orinoco_cs 6760 1
    orinoco 38028 1 orinoco_cs
    ds 17572 5 orinoco_cs
    yenta_socket 18624 1
    nfsd 189408 8
    exportfs 4736 1 nfsd
    lockd 58344 2 nfsd
    sunrpc 127652 2 nfsd,lockd
    md5 3584 1
    ipv6 230916 10
    maestro 34440 1
    soundcore 7008 2 maestro
    af_packet 16072 6
    usbhid 41088 0
    floppy 55088 0
    pcmcia_core 59972 3 orinoco_cs,ds,yenta_socket
    hermes 7712 2 orinoco_cs,orinoco
    ide-cd 37280 0
    cdrom 37724 1 ide-cd
    loop 12520 0
    nls_iso8859-1 3680 1
    ntfs 147964 1
    supermount 34804 1
    intel-agp 19584 1
    agpgart 27752 1 intel-agp
    evdev 7648 0
    uhci-hcd 28752 0
    usbcore 103172 4 usbhid,uhci-hcd
    genrtc 7444 0
    ext3 120680 5
    jbd 49080 1 ext3


  2. Re: Orinoco wifi driver fails load on startup but can load it manually

    Bill Cattell wrote:
    > I have a Dell Inspiron 7500 running Mandrake 10.1. I have a netprofile
    > setup for a Linksys wireless NIC that uses the Orinoco drivers. The NIC
    > was detected on setup so it's not an issue of the OS not seeing the
    > hardware.
    >
    > On startup I select the wireless netprofile which loads the orinoco,
    > orinoco_cs and ds modules when pcmcia runs. What doesn't get loaded is a
    > module called yenta_socket.
    >
    > If I rmmod the orinoco modules then /etc/init.d/pcmcia restart all modules
    > get loaded correctly including the yenta_socket. I can then run the
    > /etc/init.d/network script and get an IP via DHCP.
    >
    > What I can't figure out is why yenta_socket isn't getting loaded on
    > startup (cold or warm boot).
    >
    > Here's a list of the modules loaded when everything is working;
    >
    > [root@i7500l ]# lsmod
    > Module Size Used by
    > orinoco_cs 6760 1
    > orinoco 38028 1 orinoco_cs
    > ds 17572 5 orinoco_cs
    > yenta_socket 18624 1
    > nfsd 189408 8
    > exportfs 4736 1 nfsd
    > lockd 58344 2 nfsd
    > sunrpc 127652 2 nfsd,lockd
    > md5 3584 1
    > ipv6 230916 10
    > maestro 34440 1
    > soundcore 7008 2 maestro
    > af_packet 16072 6
    > usbhid 41088 0
    > floppy 55088 0
    > pcmcia_core 59972 3 orinoco_cs,ds,yenta_socket
    > hermes 7712 2 orinoco_cs,orinoco
    > ide-cd 37280 0
    > cdrom 37724 1 ide-cd
    > loop 12520 0
    > nls_iso8859-1 3680 1
    > ntfs 147964 1
    > supermount 34804 1
    > intel-agp 19584 1
    > agpgart 27752 1 intel-agp
    > evdev 7648 0
    > uhci-hcd 28752 0
    > usbcore 103172 4 usbhid,uhci-hcd
    > genrtc 7444 0
    > ext3 120680 5
    > jbd 49080 1 ext3
    >



    Your PCMCIA hot plug system isn't working. If you google "yenta_socket
    not loaded" you'll find some hints. I haven't used mandrake in a while
    and don't have a system up to check (switched to Slackware ages ago!) to
    see which script in your startup may need to be checked.

    Note:

    http://qa.mandrakesoft.com/show_bug.cgi?id=9442


    bgmilne@mandrake.org changed:

    What |Removed |Added
    ----------------------------------------------------------------------------
    Component|booting |program
    Product|kernel |harddrake
    Version|2.6.6-3mdk |10-54mdk


    ------- Additional Comments From narfi@cs.wisc.edu 2004-07-18 23:57 -------
    Created an attachment (id=1747)
    --> (http://qa.mandrakesoft.com/attachmen...47&action=view)
    The file /root/drakx/report.bug.gz

    This bug may not be a kernel bug, but then it should just be moved to the
    appropriate place. The bug still exists and is valid.
    I just installed 10.1 alpha1 on my laptop. During the installation, the
    PCMCIA
    slot worked just fine. On the first boot-up, I had to modprobe
    yenta_socket in
    order to use the PCMCIA slot.
    Solving the problem permanently required me to put
    yenta_socket
    in /etc/modprobe.preload.

    Since the installation scripts can figure out how to get the PCMCIA slot
    working, they should also be able to create permanent setup for it.

    Attached: report.bug.gz from the installation of 10.1 alpha 1

    ------- Additional Comments From bgmilne@mandrake.org 2004-07-19 10:35
    -------
    AFAIK, turning the harddrake boot service off fixes this issue. So,
    maybe it's a
    harddrake bug.

    --
    Configure bugmail: http://qa.mandrakesoft.com/userprefs.cgi?tab=email
    ------- You are receiving this mail because: -------
    You are on the CC list for the bug, or are watching someone who is.


    ------- Reminder: -------
    assigned_to: kernel@mandrakesoft.com
    status: UNCONFIRMED
    creation_date:
    description:
    On my Toshiba Tecra 8000 Laptop, the yenta_socket module is not loaded
    on bootup.
    It is necessary to put an entry in /etc/modprobe.preload to get it to load.
    I am using 2.6.3.7 kernel.
    Pcmcia services do not work until the yenta_socket module is loaded manually
    (followed by cardmgr -o) or else it is manually inserted in the
    /etc/modprobe_preload file.

    Dj.

  3. Re: Orinoco wifi driver fails load on startup but can load it manually

    On Thu, 24 Mar 2005 22:30:15 -0700, Beowulf wrote:

    > Bill Cattell wrote:
    >> I have a Dell Inspiron 7500 running Mandrake 10.1. I have a netprofile
    >> setup for a Linksys wireless NIC that uses the Orinoco drivers. The NIC
    >> was detected on setup so it's not an issue of the OS not seeing the
    >> hardware.
    >>
    >> On startup I select the wireless netprofile which loads the orinoco,
    >> orinoco_cs and ds modules when pcmcia runs. What doesn't get loaded is a
    >> module called yenta_socket.
    >>
    >> If I rmmod the orinoco modules then /etc/init.d/pcmcia restart all modules
    >> get loaded correctly including the yenta_socket. I can then run the
    >> /etc/init.d/network script and get an IP via DHCP.
    >>
    >> What I can't figure out is why yenta_socket isn't getting loaded on
    >> startup (cold or warm boot).
    >>
    >> Here's a list of the modules loaded when everything is working;
    >>
    >> [root@i7500l ]# lsmod
    >> Module Size Used by
    >> orinoco_cs 6760 1
    >> orinoco 38028 1 orinoco_cs
    >> ds 17572 5 orinoco_cs
    >> yenta_socket 18624 1
    >> nfsd 189408 8
    >> exportfs 4736 1 nfsd
    >> lockd 58344 2 nfsd
    >> sunrpc 127652 2 nfsd,lockd
    >> md5 3584 1
    >> ipv6 230916 10
    >> maestro 34440 1
    >> soundcore 7008 2 maestro
    >> af_packet 16072 6
    >> usbhid 41088 0
    >> floppy 55088 0
    >> pcmcia_core 59972 3 orinoco_cs,ds,yenta_socket
    >> hermes 7712 2 orinoco_cs,orinoco
    >> ide-cd 37280 0
    >> cdrom 37724 1 ide-cd
    >> loop 12520 0
    >> nls_iso8859-1 3680 1
    >> ntfs 147964 1
    >> supermount 34804 1
    >> intel-agp 19584 1
    >> agpgart 27752 1 intel-agp
    >> evdev 7648 0
    >> uhci-hcd 28752 0
    >> usbcore 103172 4 usbhid,uhci-hcd
    >> genrtc 7444 0
    >> ext3 120680 5
    >> jbd 49080 1 ext3
    >>

    >
    >
    > Your PCMCIA hot plug system isn't working. If you google "yenta_socket
    > not loaded" you'll find some hints. I haven't used mandrake in a while
    > and don't have a system up to check (switched to Slackware ages ago!) to
    > see which script in your startup may need to be checked.
    >
    > Note:
    >
    > http://qa.mandrakesoft.com/show_bug.cgi?id=9442
    >
    >
    > bgmilne@mandrake.org changed:
    >
    > What |Removed |Added
    > ----------------------------------------------------------------------------
    > Component|booting |program
    > Product|kernel |harddrake
    > Version|2.6.6-3mdk |10-54mdk
    >
    >
    > ------- Additional Comments From narfi@cs.wisc.edu 2004-07-18 23:57 -------
    > Created an attachment (id=1747)
    > --> (http://qa.mandrakesoft.com/attachmen...47&action=view)
    > The file /root/drakx/report.bug.gz
    >
    > This bug may not be a kernel bug, but then it should just be moved to the
    > appropriate place. The bug still exists and is valid.
    > I just installed 10.1 alpha1 on my laptop. During the installation, the
    > PCMCIA
    > slot worked just fine. On the first boot-up, I had to modprobe
    > yenta_socket in
    > order to use the PCMCIA slot.
    > Solving the problem permanently required me to put
    > yenta_socket
    > in /etc/modprobe.preload.
    >
    > Since the installation scripts can figure out how to get the PCMCIA slot
    > working, they should also be able to create permanent setup for it.
    >
    > Attached: report.bug.gz from the installation of 10.1 alpha 1
    >
    > ------- Additional Comments From bgmilne@mandrake.org 2004-07-19 10:35
    > -------
    > AFAIK, turning the harddrake boot service off fixes this issue. So,
    > maybe it's a
    > harddrake bug.


    Appreciate the input - I'll start digging into it.

    Bill

+ Reply to Thread