No module loaded when booting

I installed a new program and added its daemon to rc.conf. But after reboot, the kernel modules disappeared, none of them loaded. I hurried to delete the daemon from rc.conf, however, no change happened. How should I do?
arch 0.7

aufgeist wrote: I hurried to delete the daemon from rc.conf, however, no change happened.
You lost me on that.
When you add the daemons to rc.conf in the array() it tells the system to load that module during boot thats all.
To see if the module is running do:ls /var/run/daemons
But, you say it hasn't loaded. If the above yields no module, do: /etc/rc.d/nameofmodule start. The other options are stop and restart. Thats how you load daemons manually in arch.
If you get an error message doing the above it may just be a configuration file that needs attention.  To better help us, which daemon is it?

Similar Messages

  • Daemons and modules loaded at boot problem

    Hi all, i have a problem with my booting time and modules / daemons loaded at boot
    This is my bootchart:
    [IMG=http://img195.imageshack.us/img195/4701/bootchartpw.th.png][/IMG]
    This is my rc.conf
    # /etc/rc.conf - Main Configuration for Arch Linux
    # LOCALIZATION
    # LOCALE: available languages can be listed with the 'locale -a' command
    # HARDWARECLOCK: set to "UTC" or "localtime"
    # USEDIRECTISA: use direct I/O requests instead of /dev/rtc for hwclock
    # TIMEZONE: timezones are found in /usr/share/zoneinfo
    # KEYMAP: keymaps are found in /usr/share/kbd/keymaps
    # CONSOLEFONT: found in /usr/share/kbd/consolefonts (only needed for non-US)
    # CONSOLEMAP: found in /usr/share/kbd/consoletrans
    # USECOLOR: use ANSI color sequences in startup messages
    LOCALE="it_IT.utf8"
    HARDWARECLOCK="localtime"
    USEDIRECTISA="no"
    TIMEZONE="Europe/Rome"
    KEYMAP="it"
    CONSOLEFONT=
    CONSOLEMAP=
    USECOLOR="yes"
    # HARDWARE
    # MOD_AUTOLOAD: Allow autoloading of modules at boot and when needed
    # MOD_BLACKLIST: Prevent udev from loading these modules
    # MODULES: Modules to load at boot-up. Prefix with a ! to blacklist.
    # NOTE: Use of 'MOD_BLACKLIST' is deprecated. Please use ! in the MODULES array.
    MOD_AUTOLOAD="yes"
    #MOD_BLACKLIST=() #deprecated
    MODULES=(lib80211_crypt_tkip wl !snd-pcsp !pcspkr)
    # Scan for LVM volume groups at startup, required if you use LVM
    USELVM="no"
    # NETWORKING
    # HOSTNAME: Hostname of machine. Should also be put in /etc/hosts
    HOSTNAME="neplero"
    # Use 'ifconfig -a' or 'ls /sys/class/net/' to see all available interfaces.
    # Interfaces to start at boot-up (in this order)
    # Declare each interface then list in INTERFACES
    # - prefix an entry in INTERFACES with a ! to disable it
    # - no hyphens in your interface names - Bash doesn't like it
    # DHCP: Set your interface to "dhcp" (eth0="dhcp")
    # Wireless: See network profiles below
    #Static IP example
    #eth0="eth0 192.168.0.2 netmask 255.255.255.0 broadcast 192.168.0.255"
    eth0="dhcp"
    INTERFACES=(eth0)
    # Routes to start at boot-up (in this order)
    # Declare each route then list in ROUTES
    # - prefix an entry in ROUTES with a ! to disable it
    gateway="default gw 192.168.0.1"
    ROUTES=(!gateway)
    # Enable these network profiles at boot-up. These are only useful
    # if you happen to need multiple network configurations (ie, laptop users)
    # - set to 'menu' to present a menu during boot-up (dialog package required)
    # - prefix an entry with a ! to disable it
    # Network profiles are found in /etc/network.d
    # This now requires the netcfg package
    #NETWORKS=(main)
    # DAEMONS
    # Daemons to start at boot-up (in this order)
    # - prefix a daemon with a ! to disable it
    # - prefix a daemon with a @ to start it up in the background
    DAEMONS=(syslog-ng netfs crond hal !dbus !bluetooth @alsa)
    How can i modify my modules loaded and daemons to lower some boot time.
    And why is that bluetooth is still loaded even if it's !bluetooth? And is it possible to background ntfs-3g?
    Thanks all for advices!

    Please clarify what you mean. If the bluetooth service is started, then there is a bug or something very very odd. IF on the contrary you mean that the bluetooth-related modules are loaded by udev, this is perfectly normal: udev autoloads modules according to your hardware, not to your services. You need to blacklist the loaded bluetooth-related kernel modules (check them with 'lsmod') and to blacklist them in the MODULES array.
    Last edited by patroclo7 (2010-01-30 19:14:51)

  • Lsmod and modules loaded on boot

    Hi all, i hope i'm in the right section of the forum
    this is my lsmod output, i'm seeing that some modules are used by nobody (i guess the 0 means that...) so i was wondering if you think it's better if i unload them and blacklist on rc.conf
    lsmod
    ┌─[smau @ neplero]-[~/Torrents]
    └─[11:33:52]-[ $ ]> lsmod
    Module Size Used by
    ipv6 282582 16
    tun 13261 2
    cpufreq_ondemand 8085 0
    freq_table 2395 1 cpufreq_ondemand
    fuse 58564 4
    snd_hda_codec_intelhdmi 15636 1
    snd_hda_codec_idt 52475 1
    arc4 1354 2
    ecb 2017 2
    b43 174524 0
    ssb 45271 1 b43
    snd_hda_intel 22642 1
    mac80211 171772 1 b43
    i915 291818 2
    snd_hda_codec 68413 3 snd_hda_codec_intelhdmi,snd_hda_codec_idt,snd_hda_intel
    uvcvideo 60298 0
    snd_pcm_oss 39107 0
    drm_kms_helper 23753 1 i915
    uhci_hcd 21684 0
    lib80211_crypt_tkip 8357 0
    snd_pcm 70222 3 snd_hda_intel,snd_hda_codec,snd_pcm_oss
    i2c_i801 8550 0
    videodev 38395 1 uvcvideo
    drm 160140 3 i915,drm_kms_helper
    i2c_algo_bit 4999 1 i915
    snd_mixer_oss 17107 1 snd_pcm_oss
    snd_hwdep 6244 1 snd_hda_codec
    usbhid 38631 0
    btusb 11500 0
    snd_timer 19213 1 snd_pcm
    r8169 34925 0
    ehci_hcd 34938 0
    lib80211 3942 1 lib80211_crypt_tkip
    usb_storage 42489 0
    st 36975 0
    mmc_core 51748 2 b43,ssb
    psmouse 53142 0
    serio_raw 4536 0
    joydev 9800 0
    cfg80211 126658 2 b43,mac80211
    i2c_core 17842 6 i915,drm_kms_helper,i2c_i801,videodev,drm,i2c_algo_bit
    video 18746 1 i915
    hid 75973 1 usbhid
    snd 57203 11 snd_hda_codec_intelhdmi,snd_hda_codec_idt,snd_hda_intel,snd_hda_codec,snd_pcm_oss,snd_pcm,snd_mixer_oss,snd_hwdep,snd_timer
    snd_page_alloc 7097 2 snd_hda_intel,snd_pcm
    iTCO_wdt 9157 0
    pcmcia 29850 2 b43,ssb
    bluetooth 50955 1 btusb
    mii 3834 1 r8169
    evdev 8852 18
    rfkill 15396 2 cfg80211,bluetooth
    v4l1_compat 15610 2 uvcvideo,videodev
    wmi 5957 0
    v4l2_compat_ioctl32 10417 1 videodev
    soundcore 6223 1 snd
    speedstep_lib 3383 0
    shpchp 31236 0
    thermal 12079 0
    iTCO_vendor_support 1873 1 iTCO_wdt
    fan 3314 0
    pcmcia_core 29736 1 pcmcia
    led_class 2609 1 b43
    output 1916 1 video
    usbcore 144604 7 uvcvideo,uhci_hcd,usbhid,btusb,ehci_hcd,usb_storage
    pci_hotplug 26754 1 shpchp
    button 4746 1 i915
    acpi_memhotplug 4138 0
    processor 29639 2
    battery 9612 0
    ac 3091 0
    intel_agp 28089 1
    rtc_cmos 8990 0
    rtc_core 14439 1 rtc_cmos
    rtc_lib 1842 1 rtc_core
    ext4 329882 1
    mbcache 5658 1 ext4
    jbd2 75681 1 ext4
    crc16 1273 1 ext4
    sd_mod 26984 5
    ahci 35111 4
    libata 154643 1 ahci
    scsi_mod 94729 4 usb_storage,st,sd_mod,libata
    rc.conf
    MODULES=(ac acpi_memhotplug battery button processor video btusb intel-agp speedstep-lib drm_kms_helper drm i915 hid i2c-algo-bit i2c-i801 i2c-core evdev joydev !pcspkr !snd-pcsp psmouse serio_raw uvcvideo v4l1-compat v4l2-compat-ioctl32 videodev mmc_core pci_hotplug shpchp wmi rtc-cmos rtc-core rtc-lib !ssb output iTCO_vendor_support iTCO_wdt snd-mixer-oss snd-pcm-oss snd-hwdep snd snd-page-alloc snd-pcm snd-timer snd-hda-codec snd-hda-intel soundcore scsi_mod ahci mii r8169 bluetooth rfkill lib80211_crypt_tkip b43 !wl !lib80211 pcmcia_core pcmcia usbhid usbcore usb-storage ehci-hcd uhci-hcd sd_mod st)

    lsmod | grep " 0 " would have given a cleaner output.
    How do you expect it to help your situation if you're unloading those modules? In my experience neither power consumption nor boot time get reduced by doing so. All you'll have are a few less modules which will have to be loaded again in case they are needed by certain hardware.
    So, imho blacklisting modules should only be done if there is a conflict between modules or if you just don't want a certain function. For instance if the module pcspkr get's in the way of snd-hda-intel like it is (was?) with some intel systems. Or if you have two ethernet cards and they get confused by your system.
    Regards,
    demian
    Last edited by demian (2010-04-15 07:09:39)

  • IPod Touch 3rd Generation stuck loading when booting

    when i try to reboot my ipod, it gets stuck. it first gets the apple logo then after a while it gets the loading sign then after a while with the loading sign, the ipod turns off and turns on by itself.
    HOW DO I FIX THIS!!!
    -ipod is not jailbroken

    Try:
    - iOS: Not responding or does not turn on
    - Also try DFU mode after try recovery mode
    How to put iPod touch / iPhone into DFU mode « Karthik's scribblings
    - If not successful and you can't fully turn the iOS device fully off, let the battery fully drain. After charging for an least an hour try the above again.
    - If still not successful that usually indicates a hardware problem and an appointment at the Genius Bar of an Apple store is in order.
    Apple Retail Store - Genius Bar       

  • How does udev decide to load oss or alsa when boot up?

    Since Skottish has told me I do not need to blacklist alsa in MODULES in order to use oss.
    I assume that udev will choose oss rather than alsa to load when booting up, then I am wondering how does udev choose which one to load, alsa or oss?
    And suppose one day, I want to use alsa again, how can I make udev to choose alsa instead of oss?
    Also by the way, will there be any conflict to load both alsa and oss together?
    Thanks, guys.:)

    Ok, so udev actually look at what is DAEMON to decide what to load?
    I didn't know this.. I thought when boot up, udev will load alsa by default, then why did the OSS Wiki said we need to put !soundcore in MODULES to blacklist Alsa?
    Last edited by yingwuzhao (2009-03-15 22:58:59)

  • System boot occasionally hangs at module loading

    Since I installed Arch, about 43% of the time that I have attempted to boot my computer the boot process hangs at module loading. I assumed that the problem may have been that I was autoloading my modules. I tried turning autoloading off and manually loading them instead but that did not help. Then (as a shot in the dark) I tried having autoloading on, with my modules still defined in rc.conf, but that only made things worse (understandably, I did not think that this would help, but I figured that it couldn't hurt to try).
    Here is my /etc/rc.conf
    # /etc/rc.conf - Main Configuration for Arch Linux
    # LOCALIZATION
    # LOCALE: available languages can be listed with the 'locale -a' command
    # HARDWARECLOCK: set to "UTC" or "localtime", any other value will result
    # in the hardware clock being left untouched (useful for virtualization)
    # TIMEZONE: timezones are found in /usr/share/zoneinfo
    # KEYMAP: keymaps are found in /usr/share/kbd/keymaps
    # CONSOLEFONT: found in /usr/share/kbd/consolefonts (only needed for non-US)
    # CONSOLEMAP: found in /usr/share/kbd/consoletrans
    # USECOLOR: use ANSI color sequences in startup messages
    LOCALE="en_US.UTF-8"
    HARDWARECLOCK="UTC"
    TIMEZONE="America/New_York"
    KEYMAP="us"
    CONSOLEFONT=
    CONSOLEMAP=
    USECOLOR="yes"
    # HARDWARE
    # MOD_AUTOLOAD: Allow autoloading of modules at boot and when needed
    # MOD_BLACKLIST: Prevent udev from loading these modules
    # MODULES: Modules to load at boot-up. Prefix with a ! to blacklist.
    # NOTE: Use of 'MOD_BLACKLIST' is deprecated. Please use ! in the MODULES array.
    MOD_AUTOLOAD="no"
    #MOD_BLACKLIST=() #deprecated
    MODULES=(ac battery button processor thermal video cdrom intel-agp tpm_bios tpm tpm_tis tpm_tis tpm_tis drm_kms_helper drm i915 hid i2c-algo-bit i2c-i801 i2c-core evdev joydev pcspkr psmouse serio_raw uvcvideo v4l1-compat v4l2-compat-ioctl32 videodev pci_hotplug shpchp wmi rtc-cmos rtc-core rtc-lib output iTCO_vendor_support iTCO_wdt snd-mixer-oss snd-pcm-oss snd-hwdep snd snd-page-alloc snd-pcm snd-timer snd-hda-codec snd-hda-intel soundcore scsi_mod ahci atl1e mac80211 rfkill iwlagn iwlcore cfg80211 usb-storage usbhid usbcore ehci-hcd uhci-hcd sd_mod sr_mod st)
    # Scan for LVM volume groups at startup, required if you use LVM
    USELVM="no"
    # NETWORKING
    # HOSTNAME: Hostname of machine. Should also be put in /etc/hosts
    HOSTNAME="foster.laptop"
    # Use 'ifconfig -a' or 'ls /sys/class/net/' to see all available interfaces.
    # Interfaces to start at boot-up (in this order)
    # Declare each interface then list in INTERFACES
    # - prefix an entry in INTERFACES with a ! to disable it
    # - no hyphens in your interface names - Bash doesn't like it
    # DHCP: Set your interface to "dhcp" (wlan0="dhcp")
    # Wireless: See network profiles below
    #Static IP example
    #eth0="eth0 192.168.0.2 netmask 255.255.255.0 broadcast 192.168.0.255"
    #wlan0="dhcp"
    INTERFACES=(!wlan0)
    # Routes to start at boot-up (in this order)
    # Declare each route then list in ROUTES
    # - prefix an entry in ROUTES with a ! to disable it
    gateway="default gw 192.168.0.1"
    ROUTES=(!gateway)
    # Enable these network profiles at boot-up. These are only useful
    # if you happen to need multiple network configurations (ie, laptop users)
    # - set to 'menu' to present a menu during boot-up (dialog package required)
    # - prefix an entry with a ! to disable it
    # Network profiles are found in /etc/network.d
    # This now requires the netcfg package
    #NETWORKS=(main)
    # DAEMONS
    # Daemons to start at boot-up (in this order)
    # - prefix a daemon with a ! to disable it
    # - prefix a daemon with a @ to start it up in the background
    DAEMONS=(@alsa @syslog-ng @network dbus hal networkmanager @cups @netfs @crond @laptopmode)
    Last edited by nothinggoespast (2010-06-28 00:47:01)

    I have the same problem on my thinkpad T500 after I upgrade the wireless card (intel wifi link 5300).
    For a long time I didn't understand the why of this behavior, but some weeks ago I realise that the problem can solve it hard-locking the wireless card and unlocking after the step: "loading modules".
    For more information this is the complete thread on thinkpad forum that I wrote when I try to solve this issue: http://lnv.lithium.com/t5/T400-T500-and … 870#M26238
    I apologize if you do not understand what I mean, the problem is that I have some difficulties to express myself in English

  • [SOLVED] Virtualbox module "vboxdrv" - loading at boot

    I can manualy boot the "vboxdrv" module using
    sudo modprobe vboxdrv
    and this works every time - I can use Virtual box withouth problems. I would really like to load this module at boot time using the "/boot/syslinux/syslinux.cfg" file and then recompile the image using mkinitcpio -p. I edited the file like this, but the module doesn't get loaded.
    LABEL arch
    MENU LABEL Linux (Arch)
    LINUX ../vmlinuz-linux
    APPEND root=/dev/sda3 rw init=/usr/lib/systemd/systemd vboxdrv
    INITRD ../initramfs-linux.img
    I have seen that people useing "modeprobe.****=*****" command or something similar in this file to load modules. How should I use this to load vboxdrv module?
    Last edited by 71GA (2014-04-13 11:48:36)

    halimbo wrote:
    I don't see the problem in adding vboxdrv to the initramfs, when he clearly wants to have it loaded anytime he boots.
    For the graphics drivers it's supposed in the wiki, too.
    So I don't see a problem in adding the driver for virtualbox. but that's just me, i see.
    When i follow your argumentation, there is no reason to add graphics drivers in /etc/mkinitcpio.conf because the drivers are not needed to mount the initial filesystem.
    It's not only about mounting the real root it's about ensuring a succesfull bootup of the whole system and having graphics modules loaded early helps to do that. On my laptop for example there is a race condition with X11, which wants to start before udev figured out the appropriate graphics driver module to load. So it would boot into terminal and the display manager service would report "failed" as status otherwise.
    Last edited by blackout23 (2014-04-13 18:45:14)

  • When booting 7 64bit on HP Pavilion, I get a window saying loading "Trayapp.msi" .

    When booting 7 64bit on HP Pavilion,  I get a window saying loading "Trayapp.msi" It asks for a CD containing such. What can I do I have no CD? This new Desktop has Windows loaded from the Internet.

    This means part of the hp printer software was not deleted properly. (Windows detected something is missing and tried to repair the installation). You should be able to find it in the downloaded hp printer software. If not, try download and install the hp printer software.
    Use the uninstaller to remove installed software/driver, to avoid issues like this.
    ======================================================================================
    * I am an HP employee. *
    ** Make it easier for other people to find solutions, by marking my answer with "Accept as Solution" if it solves your issue. **
    ***Click on White “Kudos” STAR to say thanks!***

  • I continue to have an Adobe error when booting up my computer. It reads:   this specific module could not be found.    \AppData\local\diagnostics\tlfpizv.dll

    I continue to have an Adobe error when booting up my computer. It reads:   this specific module could not be found.    \AppData\local\diagnostics\tlfpizv.dll
    Please tell me there is a fix that does not involve buying a computer clean sweep program.

    Hi brigitta2,
    You might be getting the error message because of any of the following reasons:
    .dll files are corrupt or missing
    Attack of malware or other spyware
    Incorrect installation of applications
    Damaged Windows registry
    Old Windows device drivers that need to be updated
    The problem can be sorted if you know the exact reason behind the same. Please let me know the exact error message that appears on your screen.
    If the issue is with damaged files then you might need to replace them or if it is a system issue, then please take your laptop to an expert who can deal with system issues.
    Regards,
    Anubha

  • Boot-time module-loading trouble

    Recently, I've noticed a fair bit of documentation discouraging the use of /etc/modules-load.d/ , as most modules are auto-loaded by udev. While that's true, I'm still seeing some need to force-load some modules that surprises me, and I was wondering if others see these problems as well.
    - "alsactl restore" is sometimes run (from alsactl-restore.service) before my sound drivers are loaded, causing it to fail with 'load_state:1696: No soundcards found...'
    - netcfg tries to start my network before my ethernet driver is loaded, causing it to fail with 'Cannot find device "eth0"'
    I've worked around these race conditions by listing these modules in /etc/modules-load.d/ , which makes them load earlier than udev would do it, making me win the race. It doesn't feel like a good answer, though.
    - udev doesn't autoload powernow-k8 for me, which is surprising since CPU autoscaling driver are supposed to be autoloaded since kernel 3.4

    65kid wrote:
    bart_b wrote:
    Just put your 'alsactl restore' command  in /etc/rc.local
    alsactl -f /var/lib/alsa/asound.state restore
    and 'alsactl store' in /etc/rc.local.shutdown
    alsactl -f /var/lib/alsa/asound.state store
    no, rc.local{,.shutdown} should not be used anymore.
    btw, there is also a udev rule for "alsactl restore" ( /usr/lib/udev/rules.d/90-alsa-restore.rules ). That makes me wonder why there even is a service file for this as well.
    Are the alsa settings actually not restored or are they restored by the udev rule and it is just the service that is failing?
    A good question. I never noticed that udev rule, and I never checked if the settings were right after I saw the service fail - I always just restored manually before using the sound.

  • Kernel modules not loading at boot.

    ~]$ systemctl status systemd-modules-load.service
    systemd-modules-load.service - Load Kernel Modules
    Loaded: loaded (/usr/lib/systemd/system/systemd-modules-load.service; static)
    Active: failed (Result: exit-code) since Tue 2014-03-11 18:34:06 CDT; 4min 53s ago
    Docs: man:systemd-modules-load.service(8)
    man:modules-load.d(5)
    Process: 137 ExecStart=/usr/lib/systemd/systemd-modules-load (code=exited, status=1/FAILURE)
    Main PID: 137 (code=exited, status=1/FAILURE)
    Mar 11 18:34:06 arch-m systemd-modules-load[137]: Failed to insert 'vboxguest...
    Mar 11 18:34:06 arch-m systemd-modules-load[137]: Failed to insert 'vboxsf': ...
    Mar 11 18:34:06 arch-m systemd-modules-load[137]: Inserted module 'vboxvideo'
    Mar 11 18:34:06 arch-m systemd-modules-load[137]: Inserted module 'vboxdrv'
    Mar 11 18:34:06 arch-m systemd-modules-load[137]: Inserted module 'vboxnetadp'
    Mar 11 18:34:06 arch-m systemd-modules-load[137]: Failed to find module 'vbox...
    Mar 11 18:34:06 arch-m systemd[1]: systemd-modules-load.service: main proce...RE
    Mar 11 18:34:06 arch-m systemd[1]: Failed to start Load Kernel Modules.
    Mar 11 18:34:06 arch-m systemd[1]: Unit systemd-modules-load.service entere...e.
    Warning: Journal has been rotated since unit was started. Log output is incomplete or unavailable.
    Hint: Some lines were ellipsized, use -l to show in full.
    Does any one know how to fix this? AFter a while it became annoying.

    More importantly, the modules are built for a specific kernel version.  So if the kernel gets updated and the virtualbox modules get overlooked somehow, then they are not going to work.  You can always rebuild them with makepkg and ABS though.

  • [solved] no sound when booting with webcam attached

    Hi everybody,
    hopefully this is the right section to post since I'm not quite sure if the problem is related to KDE or a general hardware thing. ;-)
    Anyway, the problem that I have is that I don't have any sound at all when booting my system while my webcam, a logitech 9000 pro, is attached to the USB port.
    Even when unplugging the webcam afterwards the sound does not work. I need to reboot my system first with the webcam detached and than it'll work again. I also did already manually insert the modules in /etc/rc.conf but no change. Every time it seems that the webcams audio interface will be recognized as the primary audio device.
    When not having the camera plugged in and plugging it in while KDE is up, everything works like a charm.
    But of course it bothers me quite big time to unplug the webcam every time after using it and rebooting the system again after I forgot to unplug it.
    I also checked for other modules to be loaded automatically (compared the output of lsmod before and after plugging in the webcam) but there was no change.
    So does anyone have an idea what to do in order to get the order of the audio devices right?
    Thank you!...
    Last edited by kurisutian (2009-11-23 19:34:10)

    In your /etc/rc.d/modprobe.d/modprobe.conf try to put zero index for your audio driver, so it will load first. In my case it's this line:
    options snd-hda-intel index=0

  • Iwl3945 module loading problem (with workaround)

    I've been experiencing problems with my intel wireless card (iwl3945) not loading at boot time. The problem arose after a fresh install from a Chakra (kdemod) live CD after I got a new harddrive for my notebook. It worked fine from the live CD and immediately post-install but when I upgraded the system with "pacman -Syu" (the kernel was upgraded as part of this) the card no longer loaded during boot (i.e. wlan0 would not show up under "ifconfig -a").
    I checked some threads on the iwl3945 (e.g. http://bbs.archlinux.org/viewtopic.php? … 18#p638618 and http://bbs.archlinux.org/viewtopic.php?id=73876) but couldn't find quite the same behaviour so decided to start a new thread.
    It's also similar to this thread (http://bbs.archlinux.org/viewtopic.php?id=82357), but this is not for the iwl3945.
    The following is a log of the problem:
    $ ifconfig -a
    eth0 Link encap:Ethernet HWaddr 00:15:C5:46:C6:6A
    UP BROADCAST RUNNING 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:17
    lo Link encap:Local Loopback
    inet addr:127.0.0.1 Mask:255.0.0.0
    inet6 addr: ::1/128 Scope:Host
    UP LOOPBACK RUNNING MTU:16436 Metric:1
    RX packets:24 errors:0 dropped:0 overruns:0 frame:0
    TX packets:24 errors:0 dropped:0 overruns:0 carrier:0
    collisions:0 txqueuelen:0
    RX bytes:1240 (1.2 Kb) TX bytes:1240 (1.2 Kb)
    $ ifconfig wlan0 up
    wlan0: unknown interface: No such device
    $ lsmod | grep iwl
    iwl3945 89020 0
    iwlcore 107100 1 iwl3945
    mac80211 155532 2 iwl3945,iwlcore
    led_class 4000 3 sdhci,iwl3945,iwlcore
    cfg80211 90428 3 iwl3945,iwlcore,mac80211
    $ dmesg | grep iwl
    iwl3945: Intel(R) PRO/Wireless 3945ABG/BG Network Connection driver for Linux, 1.2.26ks
    iwl3945: Copyright(c) 2003-2009 Intel Corporation
    iwl3945 0000:0c:00.0: PCI INT A -> GSI 17 (level, low) -> IRQ 17
    iwl3945 0000:0c:00.0: setting latency timer to 64
    iwl3945 0000:0c:00.0: Tunable channels: 13 802.11bg, 23 802.11a channels
    iwl3945 0000:0c:00.0: Detected Intel Wireless WiFi Link 3945ABG
    iwl3945 0000:0c:00.0: irq 28 for MSI/MSI-X
    iwl3945 0000:0c:00.0: Failed to register hw (error -2)
    iwl3945 0000:0c:00.0: PCI INT A disabled
    iwl3945: probe of 0000:0c:00.0 failed with error -2
    Here is my rc.conf
    # /etc/rc.conf - Main Configuration for Arch Linux
    # LOCALIZATION
    # LOCALE: available languages can be listed with the 'locale -a' command
    # HARDWARECLOCK: set to "UTC" or "localtime", any other value will result
    # in the hardware clock being left untouched (useful for virtualization)
    # TIMEZONE: timezones are found in /usr/share/zoneinfo
    # KEYMAP: keymaps are found in /usr/share/kbd/keymaps
    # CONSOLEFONT: found in /usr/share/kbd/consolefonts (only needed for non-US)
    # CONSOLEMAP: found in /usr/share/kbd/consoletrans
    # USECOLOR: use ANSI color sequences in startup messages
    LOCALE="en_GB.utf8"
    HARDWARECLOCK="localtime"
    TIMEZONE="Europe/Dublin"
    KEYMAP="uk"
    CONSOLEFONT=
    CONSOLEMAP=
    USECOLOR="yes"
    # HARDWARE
    # MOD_AUTOLOAD: Allow autoloading of modules at boot and when needed
    # MOD_BLACKLIST: Prevent udev from loading these modules
    # MODULES: Modules to load at boot-up. Prefix with a ! to blacklist.
    # NOTE: Use of 'MOD_BLACKLIST' is deprecated. Please use ! in the MODULES array.
    MOD_AUTOLOAD="yes"
    #MOD_BLACKLIST=() #deprecated
    MODULES=(b44 mii !ipw3945 iwlcore pcspkr snd-mixer-oss snd-pcm-oss snd-hwdep snd-page-alloc snd-pcm snd-timer snd snd-hda-codec snd-hda-intel soundcore)
    # Scan for LVM volume groups at startup, required if you use LVM
    USELVM="no"
    # NETWORKING
    # HOSTNAME: Hostname of machine. Should also be put in /etc/hosts
    HOSTNAME="alex-xps"
    # Use 'ifconfig -a' or 'ls /sys/class/net/' to see all available interfaces.
    # Interfaces to start at boot-up (in this order)
    # Declare each interface then list in INTERFACES
    # - prefix an entry in INTERFACES with a ! to disable it
    # - no hyphens in your interface names - Bash doesn't like it
    eth0="dhcp"
    # Wireless: See network profiles below
    wlan0="dhcp"
    #Static IP example
    #eth0="eth0 134.226.144.162 netmask 255.255.0.0 broadcast 134.226.255.255"
    INTERFACES=(!eth0 !eth1 !wlan0)
    # Routes to start at boot-up (in this order)
    # Declare each route then list in ROUTES
    # - prefix an entry in ROUTES with a ! to disable it
    gateway="default gw 192.168.0.1"
    ROUTES=(!gateway)
    # Enable these network profiles at boot-up. These are only useful
    # if you happen to need multiple network configurations (ie, laptop users)
    # - set to 'menu' to present a menu during boot-up (dialog package required)
    # - prefix an entry with a ! to disable it
    # Network profiles are found in /etc/network.d
    # This now requires the netcfg package
    #NETWORKS=(main)
    # DAEMONS
    # Daemons to start at boot-up (in this order)
    # - prefix a daemon with a ! to disable it
    # - prefix a daemon with a @ to start it up in the background
    DAEMONS=(syslog-ng hal !network wicd !networkmanager avahi-daemon avahi-dnsconfd alsa cdemud kdm)
    I read somewhere that there was an issue with kill switches and that rfkill may help so I installed it from AUR. However, there didn't seem to be any block:
    $ rfkill list
    1: hci0: Bluetooth
    Soft blocked: no
    Hard blocked: no
    2: dell-wifi: Wireless LAN
    Soft blocked: no
    Hard blocked: no
    3: dell-bluetooth: Bluetooth
    Soft blocked: no
    Hard blocked: no
    I also tried creating a modprobe.conf file as suggested in some quarters (/etc/modprobe.d/iwl3945.conf):
    alias wlan0 iwl3945
    options iwl3945 disable_hw_scan=1
    Sadly still no luck on a reboot.
    After much pulling of hair the following workaround finally did it for me. Basically even though the module doesn't load during boot I can remove it and then modprobe it manually and it then works so that I can bring up the interface:
    # rmmod iwl3945
    # modprobe iw3945
    # ifconfig wlan0 up
    # ifconfig -a
    eth0 Link encap:Ethernet HWaddr 00:15:C5:46:C6:6A
    UP BROADCAST RUNNING 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:17
    lo Link encap:Local Loopback
    inet addr:127.0.0.1 Mask:255.0.0.0
    inet6 addr: ::1/128 Scope:Host
    UP LOOPBACK RUNNING MTU:16436 Metric:1
    RX packets:24 errors:0 dropped:0 overruns:0 frame:0
    TX packets:24 errors:0 dropped:0 overruns:0 carrier:0
    collisions:0 txqueuelen:0
    RX bytes:1240 (1.2 Kb) TX bytes:1240 (1.2 Kb)
    wlan0 Link encap:Ethernet HWaddr 00:18:DE:1E:7B:46
    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)
    wmaster0 Link encap:UNSPEC HWaddr 00-18-DE-1E-7B-46-00-00-00-00-00-00-00-00-00-00
    UP RUNNING MTU:0 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)
    I can then use wicd to connect to my router at home (networkmanager doesn't seem to work for me with the same settings).
    Hopefully this may be of some use to someone with the same issue and to any kernel gurus that may be scanning this section of the forum.

    I tinkered with the rfkill module as suggested.
    First checked what the default behaviour was
    $ lsmod | grep rfkill
    rfkill 19728 3 bluetooth,dell_laptop,cfg80211
    Then blacklisted rfkill in rc.conf using "!rfkill" in the modules line
    $ lsmod | grep rfkill
    rfkill 19728 1 cfg80211
    Unfortunately I still had to manually remove and reload iwl3945 as before.
    I tried inserting the options in modprobe.conf suggested by you in your other post
    # /etc/modprobe.d/modprobe.conf (for v2.6 kernels)
    options bluetooth rfkill=0
    options dell_laptop rfkill=0
    After a reboot still no wireless activity and checking rfkill module gives same as for blacklisting in rc.conf, i.e. ...
    $ lsmod | grep rfkill
    rfkill 19728 1 cfg80211
    So still manually un/reloading as before. At least the workaround is not too labour intensive.

  • MAX shows PXI card when booted into Windows but not in Hypervisor mode

    Hello again all you helpful forum-goers!
    I'm having some difficulties with a Hypervisor system seeing the two Pickering 6 channel programmable resistor cards that are loaded into the PXI chassis.  When I boot into Windows mode, MAX sees them under the My System just fine.  When I then run the Hypervisor configuration software, I see them both listed, and have them assigned to the Real-Time OS.  However, when I then boot into Hypervisor mode, MAX does not see them under the Remote Systems -> Hypervisor Target -> Chassis (or anywhere else), and the drivers report not seeing any modules either when I debug my code running on the real-time system.
    Does anyone have any idea what setting or configuration I might have incorrect?  Is there any other information I can provide that would be relevant or useful to answer this question?  I'm not the main hardware guy, he just got married and so isn't available, so I'm out of my comfort zone.  ;-)  I write the software that runs on the system, though, so I'm not completely clueless.  I know we just replaced the controller in the main chassis with a faster one (unfortunately I don't have the number on hand, the simulator is down in the lab), but I also know we are using that same controller and Pickering card on a different simulator and it is working just fine.
    Any ideas?  I very much appreciate your time!
    -Joe
    Solved!
    Go to Solution.

    Nevermind, the answer turned out to be that I did not have the drivers fully installed on the real-time system.  Apparently that caused it to not recognize the cards.  I never did figure out / remember exactly how to install the Pickering drivers on the real-time side, but fortunately I was able to just copy all the files that had "Pickering" in their name from the C:\ni-rt\system folder of the real-time file directory from another simulator to this one.  ;-)
    Cheers!

  • Snd_sb16 module loading problem

    Every time I boot Arch, I have to manually load the snd_sb16 module. It works great while loaded with modprobe snd_sb16, but when rebooting, it won't load. I tried adding the module to /etc/modprobe.conf, but I get an error when rebooting. Perhaps the syntax is wrong?
    Where else should I add the module so it will get loaded at boot?
    Thanks.
    m

    multios wrote:Every time I boot Arch, I have to manually load the snd_sb16 module. It works great while loaded with modprobe snd_sb16, but when rebooting, it won't load. I tried adding the module to /etc/modprobe.conf, but I get an error when rebooting. Perhaps the syntax is wrong?
    Where else should I add the module so it will get loaded at boot?
    Thanks.
    m
    In /etc/rc.conf, you'll find MODULES section. Put that module to here.

Maybe you are looking for