Page 1 of 2 12 LastLast
Results 1 to 10 of 11

Thread: Slackware 12 + ALC268 + Alsa-driver 1.0.18 = ALSA Error =No Sound (Tried erverything)

  1. #1
    Just burned his ISO
    Join Date
    Nov 2008
    Posts
    13

    Default Slackware 12 + ALC268 + Alsa-driver 1.0.18 = ALSA Error =No Sound (Tried erverything)

    Hi,

    here, almost crazy, I am, after googling, reading, searching and testing to
    get my sound working. Sorry, but I decided to Post because I don't know what to try.

    This is a laptop Dell Vostro 1510. The scenario is in the subject and now I'll give you mor information about it:

    Code:
    !!Linux Distribution
    !!------------------
    Slackware 12.0
    
    !!Kernel Information
    !!------------------
    Kernel release:    2.6.21.5
    Operating System:  GNU/Linux
    Architecture:      i686
    Processor:         Intel(R) Core(TM)2 Duo CPU     T8100  @ 2.10GHz
    SMP Enabled:       Yes
    
    !!ALSA Version
    !!------------
    Driver version:     1.0.18
    Library version:    1.0.18
    Utilities version:  1.0.18
    
    !!Soundcards recognised by ALSA
    !!-----------------------------
     0 [Intel          ]: HDA-Intel - HDA Intel
                          HDA Intel at 0xf8500000 irq 16
    
    
    !!PCI Soundcards installed in the system
    !!--------------------------------------
    
    00:1b.0 Audio device: Intel Corporation 82801H (ICH8 Family) HD Audio Controller (rev 03)
    
    
    !!Advanced information - PCI Vendor/Device/Susbsystem ID's
    !!--------------------------------------------------------
    
    00:1b.0 0403: 8086:284b (rev 03)
    	Subsystem: 1028:0273
    
    
    !!Modprobe options (Sound related)
    !!--------------------------------
    
    snd-hda-intel: model=Dell
    
    
    !!Loaded sound module options
    !!--------------------------
    
    !!Module: snd_hda_intel
    enable : N
    id : <NULL>
    index : -1
    model : <NULL>
    position_fix : 0
    probe_mask : -1
    single_cmd : N
    
    
    !!HDA-Intel Codec information
    !!---------------------------
    --startcollapse--
    
    Codec: Realtek ID 268
    Address: 0
    Vendor Id: 0x10ec0268
    Subsystem Id: 0x10280273
    Revision Id: 0x100003
    Default PCM:
        rates [0x560]: 44100 48000 96000 192000
        bits [0xe]: 16 20 24
        formats [0x1]: PCM
    ...
         0x18* 0x19 0x1a 0x1c 0x14 0x15 0x13
    --endcollapse--
    
    
    !!ALSA Device nodes
    !!-----------------
    
    crw-rw---- 1 root audio 116,   0 Nov 10 00:58 /dev/snd/controlC0
    ...
    crw-rw---- 1 root audio 116, 119 Nov 10 00:58 /dev/snd/pcmC3D7p
    crw-rw---- 1 root audio 116,  33 Nov 10 00:58 /dev/snd/timer
    
    
    !!Aplay/Arecord output
    !!------------
    
    APLAY
    
    **** List of PLAYBACK Hardware Devices ****
    card 0: Intel [HDA Intel], device 0: HDA Generic [HDA Generic]
      Subdevices: 1/1
      Subdevice #0: subdevice #0
    
    ARECORD
    
    **** List of CAPTURE Hardware Devices ****
    card 0: Intel [HDA Intel], device 0: HDA Generic [HDA Generic]
      Subdevices: 1/1
      Subdevice #0: subdevice #0
    
    !!Amixer output
    !!-------------
    
    !!-------Mixer controls for card 0 [Intel]
    
    Card hw:0 'Intel'/'HDA Intel at 0xf8500000 irq 16'
      Mixer name	: 'Realtek ID 268'
      Components	: 'HDA:10ec0268'
      Controls      : 2
      Simple ctrls  : 2
    Simple mixer control 'Master',0
      Capabilities: pvolume
      Playback channels: Front Left - Front Right
      Limits: Playback 0 - 64
      Mono:
      Front Left: Playback 52 [81%] [-12.00dB]
      Front Right: Playback 52 [81%] [-12.00dB]
    Simple mixer control 'PCM',0
      Capabilities: pvolume
      Playback channels: Front Left - Front Right
      Limits: Playback 0 - 255
      Mono:
      Front Left: Playback 255 [100%] [0.00dB]
      Front Right: Playback 255 [100%] [0.00dB]
    
    
    !!Alsactl output
    !!-------------
    
    --startcollapse--
    state.Intel {
    	control.1 {
    		comment.access 'read write'
    		comment.type INTEGER
    		comment.count 2
    		comment.range '0 - 64'
    		comment.dbmin -6400
    		comment.dbmax 0
    		iface MIXER
    		name 'Master Playback Volume'
    		value.0 52
    		value.1 52
    	}
    	control.2 {
    		comment.access 'read write user'
    		comment.type INTEGER
    		comment.count 2
    		comment.range '0 - 255'
    		comment.tlv '0000000100000008ffffec1400000014'
    		comment.dbmin -5100
    		comment.dbmax 0
    		iface MIXER
    		name 'PCM Playback Volume'
    		value.0 255
    		value.1 255
    	}
    }
    --endcollapse--
    
    
    !!All Loaded Modules
    !!------------------
    
    Module
    vboxdrv
    i915
    drm
    snd_mixer_oss
    pcmcia
    pcmcia_core
    capability
    commoncap
    fuse
    lp
    parport_pc
    parport
    pcspkr
    psmouse
    arc4
    ecb
    iwl3945
    mac80211
    cfg80211
    r8169
    intel_agp
    sg
    agpgart
    sdhci
    serio_raw
    mmc_core
    snd_hda_intel
    snd_hda_codec
    snd_pcm
    snd_timer
    snd
    shpchp
    soundcore
    ata_generic
    i2c_i801
    evdev
    snd_page_alloc
    Of course, I tried versions 14,15 and 16 of driver and utilities. Ran alsaconf but at the end appeared:

    Code:
    Loading driver...
    Starting sound driver: snd-hda-intel done
    Starting sound driver: snd-hda-intel done
    Unknown hardware: "HDA-Intel" "Realtek ALC268" "HDA:10ec0268,10280273,00100003" "" ""
    Hardware is initialized using a guess method
    /usr/sbin/alsactl: set_control:1266: failed to obtain info for control #6 (Invalid argument)
    Setting default volumes...
    amixer: Mixer default load error: Invalid argument

    This is my /etc/modprobe.d/sound:

    Code:
    alias snd-card-0 snd-hda-intel
    alias sound-slot-0 snd-hda-intel
    I tried adding options line like:

    Code:
    options snd-hda-intel model=dell
    Now, this is the result: when I boot Sound mixer is at 0% and when I set it at 100% I can hear perfectly
    the init sesion theme. Afer 2 minutes more or less syslog returns:

    Code:
    Nov 12 15:29:34 (none) kernel: Call Trace:
    Nov 12 15:29:34 (none) kernel:  [<f9177950>] snd_hda_codec_amp_read+0x30/0x60 [s
    nd_hda_intel]
    Nov 12 15:29:34 (none) kernel:  [<f9177ad4>] snd_hda_mixer_amp_switch_get+0x64/0
    xc0 [snd_hda_intel]
    Nov 12 15:29:34 (none) kernel:  [<f914b16f>] snd_mixer_oss_get_volume1_sw+0xaf/0
    x110 [snd_mixer_oss]
    Nov 12 15:29:34 (none) kernel:  [<f914b47a>] snd_mixer_oss_get_volume1+0xaa/0x11
    0 [snd_mixer_oss]
    Nov 12 15:29:34 (none) kernel:  [<f914b3d0>] snd_mixer_oss_get_volume1+0x0/0x110                                                                                                   [snd_mixer_oss]
    Nov 12 15:29:34 (none) kernel:  [<f914a4d1>] snd_mixer_oss_ioctl1+0x341/0x760 [s                                                                                                  nd_mixer_oss]
    Nov 12 15:29:34 (none) kernel:  [<c01307b0>] autoremove_wake_function+0x0/0x40
    Nov 12 15:29:34 (none) kernel:  [<c0654530>] sock_aio_write+0x0/0x140
    Nov 12 15:29:34 (none) kernel:  [<f914a950>] snd_mixer_oss_ioctl+0x0/0x10 [snd_m                                                                                                  ixer_oss]
    Nov 12 15:29:34 (none) kernel:  [<c016c9ff>] do_ioctl+0x1f/0x70
    Nov 12 15:29:34 (none) kernel:  [<c016e51c>] sys_select+0x16c/0x1b0
    Nov 12 15:29:34 (none) kernel:  [<c016caa0>] vfs_ioctl+0x50/0x2c0
    Nov 12 15:29:34 (none) kernel:  [<c016cd72>] sys_ioctl+0x62/0x90
    Nov 12 15:29:34 (none) kernel:  [<c0102a90>] syscall_call+0x7/0xb
    Nov 12 15:29:34 (none) kernel:  =======================
    Nov 12 15:29:34 (none) kernel: Code: 66 90 66 8b 42 06 66 83 f8 ff 74 12 25 ff f                                                                                                  f 00 00 8d 14 c1 3b 1a 75 ea 89 d0 5b 5e 5f c3 8d 86 80 00 00 00 e8 29 ff ff ff                                                                                                   89 c2 <89> 18 66 c7 40 04 00 00 66 8b 04 7e 66 89 42 06 66 c7 04 7e ff
    Nov 12 15:29:34 (none) kernel: EIP: [<f9175c99>] get_alloc_hash+0x49/0x70 [snd_h                                                                                                  da_intel] SS:ESP 0068:f64dbe34
    sound crashes, shell hangs and when I run alsaconf or alsasound restart, sound crashes and shell
    hangs but alsasound status returns:

    Code:
    ALSA sound driver loaded.
    and

    Code:
    Morphy Alsa-1.0.18 # rmmod snd-hda-intel
    ERROR: Module snd_hda_intel is in use

  2. #2
    Senior Member
    Join Date
    Aug 2007
    Posts
    916

    Default

    You should notify alsa rather than backtrack as this is not really backtrack related.

    Have you tried other distros and have had success?

  3. #3
    Just burned his ISO
    Join Date
    Nov 2008
    Posts
    13

    Default Sorry

    I'm using Bactrack 3. Thought somebody had same problem. I'll post in alsa too.

  4. #4
    Member
    Join Date
    Feb 2007
    Posts
    229

    Default

    Im aboard with this problem. Seems that since BT is rather specialized with its kernel patches for wireless it doesn't keep up with hardware changes as well as other distros. I'm wondering if all these patches can be made into modules and recompiled for each kernel - that way it may be easier to keep up with the Slax distros as they come, as well as offer more interoperability.

  5. #5
    Developer
    Join Date
    Mar 2007
    Posts
    6,126

    Default

    Quote Originally Posted by RageLtMan View Post
    Im aboard with this problem. Seems that since BT is rather specialized with its kernel patches for wireless it doesn't keep up with hardware changes as well as other distros. I'm wondering if all these patches can be made into modules and recompiled for each kernel - that way it may be easier to keep up with the Slax distros as they come, as well as offer more interoperability.
    Are you serious? Do you want to be in charge of all the backtrack kernel patches for every single kernel? A lot of the wireless stuff doesnt work with the newer kernels yet. Anyway there are a few things wrong here. 1) who gives a f**k about sound! A penetration test does not require any sound 2) Backtrack is not a beginner distro

  6. #6
    Junior Member Amlord1's Avatar
    Join Date
    Nov 2008
    Posts
    78

    Default

    Quote Originally Posted by pureh@te View Post
    Are you serious? Do you want to be in charge of all the backtrack kernel patches for every single kernel? A lot of the wireless stuff doesnt work with the newer kernels yet. Anyway there are a few things wrong here. 1) who gives a f**k about sound! A penetration test does not require any sound 2) Backtrack is not a beginner distro

    lol, That's about what I was going to say. I'm new to the forums, and am interested in getting into pen testing as a career. But seriously.. Its pretty easy to expect that a new distribution of a software will have issues.. (My current job is as a software tester.. I deal with ALOT of bugs...)

    And, if pureh@te hasn't made it clear enough.. your doing pen testing.. Not listening to a safe... Sound isn't really that important.

  7. #7
    Just burned his ISO
    Join Date
    Nov 2008
    Posts
    13

    Default

    Ok guys, I like the discussions that lead to some point and I ensure you that controversy was/is NOT my aim. Sorry if I get it.

    I'll try to pass on tiptoe on the discussion, however I would jot down a couple of issues:
    1) who gives a f**k about sound! A penetration test does not require any sound 2) Backtrack is not a beginner distro
    a)This was already treated here:
    Code:
    hxxp://forums.remote-exploit.org/showthread.php?t=18323
    b)I might not even be mature in GNU-Linux but as you could see this is not my first distro. I think that my post doesn't deserve that lightly coarse tone, it seems that I should apologize for having a hardware config problem. I thought that this was a forum, and the word forum is supposed to designate the place where everybody can share their experiences proving a benefit of the whole community and post their threads whenever conform to the forum rules. It's not my habit to post without investigate before, and in my opinion mine is not an intuitive issue.

    Sorry and thanks again.

  8. #8
    Junior Member Amlord1's Avatar
    Join Date
    Nov 2008
    Posts
    78

    Default

    I apologize if i came across as harsh.. It is an error, but there are going to be plenty of them. My guess is that no one knows how to fix it yet. Play around, but remember to take notes. If you fix it, you will have a pretty juice tech help post. Good Luck.

  9. #9
    Developer
    Join Date
    Mar 2007
    Posts
    6,126

    Default

    I apologize if you took my post personally

  10. #10
    Just burned his ISO
    Join Date
    Nov 2008
    Posts
    13

    Default

    Don't worry about it, no problem at all. I've posted in 5 forums besides alsa and I can't get it working. As far as I get reach, I get sound for 1 minute +/-. After this it crashes and reports what you can see in my 1st post.

    Thanks

Page 1 of 2 12 LastLast

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •