2009/4/21 Gunther Furtado <[email protected]>

> Oi,
>
> terça, 21 de abril de 2009,
> tombs <[email protected]> escreveu:
>
> [...]
>
> >Manhattan:~# modprobe snd_hda_intel
> >WARNING: All config files need .conf: /etc/modprobe.d/display_class,
> >it will be ignored in a future release.
> >WARNING: All config files need .conf: /etc/modprobe.d/blacklist, it
> >will be ignored in a future release.
> >WARNING: All config files
> >need .conf: /etc/modprobe.d/nvidia-kernel-nkc, it will be ignored in a
> >future release. WARNING: All config files
> >need .conf: /etc/modprobe.d/pnp-hotplug, it will be ignored in a
> >future release. WARNING: All config files
> >need .conf: /etc/modprobe.d/display_class, it will be ignored in a
> >future release. WARNING: All config files
> >need .conf: /etc/modprobe.d/blacklist, it will be ignored in a future
> >release. WARNING: All config files
> >need .conf: /etc/modprobe.d/nvidia-kernel-nkc, it will be ignored in a
> >future release. WARNING: All config files
> >need .conf: /etc/modprobe.d/pnp-hotplug, it will be ignored in a
> >future release. WARNING: All config files
> >need .conf: /etc/modprobe.d/display_class, it will be ignored in a
> >future release. WARNING: All config files
> >need .conf: /etc/modprobe.d/blacklist, it will be ignored in a future
> >release. WARNING: All config files
> >need .conf: /etc/modprobe.d/nvidia-kernel-nkc, it will be ignored in a
> >future release. WARNING: All config files
> >need .conf: /etc/modprobe.d/pnp-hotplug, it will be ignored in a
> >future release. Manhattan:~# modprobe soundcore
> >WARNING: All config files need .conf: /etc/modprobe.d/display_class,
> >it will be ignored in a future release.
> >WARNING: All config files need .conf: /etc/modprobe.d/blacklist, it
> >will be ignored in a future release.
> >WARNING: All config files
> >need .conf: /etc/modprobe.d/nvidia-kernel-nkc, it will be ignored in a
> >future release. WARNING: All config files
> >need .conf: /etc/modprobe.d/pnp-hotplug, it will be ignored in a
> >future release.
> >
>
> Quanto a estes avisos, basta adicionar [.conf] ao final dos nomes de todos
> arquivos no diretório /etc/modprobe.d/ que eles somem.
>
> >E no lsmod fica:
> >
> >Manhattan:~# lsmod
> >Module                  Size  Used by
> >snd_hda_intel          22696  0
> >snd_hda_codec          59136  1 snd_hda_intel
> >snd_hwdep               6340  1 snd_hda_codec
> >snd_pcm_oss            33344  0
> >snd_mixer_oss          12832  1 snd_pcm_oss
> >snd_pcm                63460  3 snd_hda_intel,snd_hda_codec,snd_pcm_oss
> >snd_seq_dummy           2756  0
> >snd_seq_oss            26400  0
> >snd_seq_midi            5728  0
> >snd_rawmidi            18688  1 snd_seq_midi
> >snd_seq_midi_event      6432  2 snd_seq_oss,snd_seq_midi
> >snd_seq                42032  6
> >snd_seq_dummy,snd_seq_oss,snd_seq_midi,snd_seq_midi_event
> >snd_timer              17896  2 snd_pcm,snd_seq
> >snd_seq_device          6572  5
> >snd_seq_dummy,snd_seq_oss,snd_seq_midi,snd_rawmidi,snd_seq
> >snd                    47332  12
>
> >snd_hda_intel,snd_hda_codec,snd_hwdep,snd_pcm_oss,snd_mixer_oss,snd_pcm,snd_seq_dummy,snd_seq_oss,snd_rawmidi,snd_seq,snd_timer,snd_seq_device
> >soundcore               6368  1 snd
> >snd_page_alloc          7816  2 snd_hda_intel,snd_pcm
> >binfmt_misc             7528  1
> >ipv6                  235364  20
> >sbp2                   18572  0
> >loop                   12748  0
> >arc4                    1824  2
> >ecb                     2624  2
> >crypto_blkcipher       15236  1 ecb
> >p54pci                  8864  0
> >p54common               9888  1 p54pci
> >firmware_class          6816  1 p54pci
> >mac80211              139712  2 p54pci,p54common
> >i2c_viapro              6836  0
> >cfg80211               21576  1 mac80211
> >i2c_core               19828  1 i2c_viapro
> >shpchp                 25528  0
> >pci_hotplug            23460  1 shpchp
> >pcspkr                  2432  0
> >usbhid                 35904  0
> >hid                    33184  1 usbhid
> >ff_memless              4392  1 usbhid
> >button                  6096  0
> >evdev                   8000  4
> >ext3                  105512  3
> >jbd                    39444  1 ext3
> >mbcache                 7108  1 ext3
> >sd_mod                 22200  5
> >usb_storage            77024  0
> >uhci_hcd               18672  0
> >sata_via                6980  4
> >ehci_hcd               28396  0
> >ata_generic             4676  0
> >ide_pci_generic         3908  0 [permanent]
> >via_rhine              18664  0
> >mii                     4896  1 via_rhine
> >via82cxxx               6948  0 [permanent]
> >libata                140416  2 sata_via,ata_generic
> >usbcore               118224  5 usbhid,usb_storage,uhci_hcd,ehci_hcd
> >scsi_mod              129324  4 sbp2,sd_mod,usb_storage,libata
> >dock                    8304  1 libata
> >ohci1394               24944  0
> >ieee1394               75800  2 sbp2,ohci1394
> >via_agp                 7744  1
> >agpgart                28776  1 via_agp
> >ide_cd_mod             27652  0
> >cdrom                  30176  1 ide_cd_mod
> >thermal                15228  0
> >processor              32544  1 thermal
> >fan                     4164  0
> >thermal_sys            10856  3 thermal,processor,fan
> >ide_generic             2464  0 [permanent]
> >ide_core               96136  4
> >ide_pci_generic,via82cxxx,ide_cd_mod,ide_generic
> >
>
> Uma dica, como o problema é com som, a saída do comando
>
> # lsmod | grep snd
>
> seria melhor.


Realmente...valeu a dica :)

>
>
> >
> >Mas mesmo assim.......
> >
> >Manhattan:~# alsaconf
> >bash: alsaconf: command not found
> >
>
> Aqui também não tenho alsaconf, mas qual é o efeito do comando seguinte
>
> # alsa reload


Manhattan:~# alsa reload
Unloading ALSA sound driver modules: (none loaded).
Loading ALSA sound driver modules: (none to reload).


>
>
> >Manhattan:~# alsamixer
> >
> >alsamixer: function snd_ctl_open failed for default: No such file or
> >directory
> >Manhattan:~#
>
>
> Abraço,
>
> --
> Gunther Furtado
> [email protected]
>
>
> --
> To UNSUBSCRIBE, email to [email protected]
> with a subject of "unsubscribe". Trouble? Contact
> [email protected]
>
>

Responder a