Nur rauschen....

Dieses Thema im Forum "Gentoo" wurde erstellt von GendoIkari, 29.01.2007.

  1. #1 GendoIkari, 29.01.2007
    GendoIkari

    GendoIkari Routinier

    Dabei seit:
    04.12.2006
    Beiträge:
    336
    Zustimmungen:
    0
    Ort:
    Dort wo die Sonne aufgeht...
    Hallo hab ein 64bit kernel und versuche schon seit ner Ewigkeit den sound richtig ein zu richten. (A8N-Sli ASUS Board, AC'97 soundchip)
    Erst hab ich die Teribei emerg'd und dann die mixer, wie "kmix" und "alsa mixer gui" jetzt hab ich zwar ein rauschen, das ich ein und aus schalten kann oder bei dem ich die lautstärke regeln kann, aber das war es dann auch schon.
    Der Realplayer gibt mir das als Antwort auf ein abspielversuch

    >>> "Cannot open the audio device. Another application may be using it." <<<

    und der amarok das,wenn ich xine und autodetect eingestellt habe:

    >>> "xine konnte keine Audio-Treiber initialisieren." <<<

    und wenn ich xine und "file" als ausgabe-modul einstell spielt er zwar die mp3'z ab aber man hört nix auser rauschen...

    hab keine idee was man da machen könnte ;(

    (im kernel hab ich auch den audio support eingestell und oss hab ich auch ausprobiert konnte ich aber bei amarok nicht auswählen , immer nur xine )
     
  2. Anzeige

    Schau dir mal diese Kategorie an. Dort findest du bestimmt etwas.
    Registrieren bzw. einloggen, um diese und auch andere Anzeigen zu deaktivieren
  3. #2 Bloodsurfer, 30.01.2007
    Bloodsurfer

    Bloodsurfer Gentoo-User

    Dabei seit:
    15.10.2005
    Beiträge:
    243
    Zustimmungen:
    0
    Ich glaub du hast gleichzeitig die Treiber im Kernel und extern emerged.
    Das kann nicht gehen. Entweder du nutzt die Kernel-internen Treiber (und emergest nichts) oder du emergest sie.
    Ich persönlich nutze die externen - dann musst du im Kernel alles abschalten bis auf den reinen Sound Support (Alsa, oss, alles raus!9) und die alsa-drivers dann emergen. Vorher natürlich deine Soundkarte in der make.conf festhalten.
     
  4. #3 liquidnight, 04.02.2007
    liquidnight

    liquidnight Routinier

    Dabei seit:
    16.04.2005
    Beiträge:
    430
    Zustimmungen:
    0
    existiert das problem noch ? wenn ja, gibst du uns mal ein lspci ? und vielleicht noch ein dmesg. steht dort etwas verdächtiges in der nähe der zeichenfolge ac97 ?
     
  5. #4 GendoIkari, 06.02.2007
    Zuletzt bearbeitet: 06.02.2007
    GendoIkari

    GendoIkari Routinier

    Dabei seit:
    04.12.2006
    Beiträge:
    336
    Zustimmungen:
    0
    Ort:
    Dort wo die Sonne aufgeht...
    das emergen hat nix gebracht. Wenn ich emerge -av alsa-driver mach finde ich meinen soundchip auch gar nicht aufgelistet. der kmix findet den gar nix mehr, unter der alsa-mix findet die karte noch. ansonsten hat sich aber nix geändert.

    #######################################################
    # lspci
    00:00.0 Memory controller: nVidia Corporation CK804 Memory Controller (rev a3)
    00:01.0 ISA bridge: nVidia Corporation CK804 ISA Bridge (rev a3)
    00:01.1 SMBus: nVidia Corporation CK804 SMBus (rev a2)
    00:02.0 USB Controller: nVidia Corporation CK804 USB Controller (rev a2)
    00:02.1 USB Controller: nVidia Corporation CK804 USB Controller (rev a3)
    00:04.0 Multimedia audio controller: nVidia Corporation CK804 AC'97 Audio Controller (rev a2)
    00:06.0 IDE interface: nVidia Corporation CK804 IDE (rev f2)
    00:09.0 PCI bridge: nVidia Corporation CK804 PCI Bridge (rev a2)
    00:0a.0 Bridge: nVidia Corporation CK804 Ethernet Controller (rev a3)
    00:0b.0 PCI bridge: nVidia Corporation CK804 PCIE Bridge (rev a3)
    00:0c.0 PCI bridge: nVidia Corporation CK804 PCIE Bridge (rev a3)
    00:0d.0 PCI bridge: nVidia Corporation CK804 PCIE Bridge (rev a3)
    00:0e.0 PCI bridge: nVidia Corporation CK804 PCIE Bridge (rev a3)
    00:18.0 Host bridge: Advanced Micro Devices [AMD] K8 [Athlon64/Opteron] HyperTransport Technology Configuration
    00:18.1 Host bridge: Advanced Micro Devices [AMD] K8 [Athlon64/Opteron] Address Map
    00:18.2 Host bridge: Advanced Micro Devices [AMD] K8 [Athlon64/Opteron] DRAM Controller
    00:18.3 Host bridge: Advanced Micro Devices [AMD] K8 [Athlon64/Opteron] Miscellaneous Control
    01:00.0 VGA compatible controller: nVidia Corporation GeForce 7300 GS (rev a1)
    05:06.0 Multimedia video controller: Brooktree Corporation Bt878 Video Capture (rev 11)
    05:06.1 Multimedia controller: Brooktree Corporation Bt878 Audio Capture (rev 11)
    05:08.0 Ethernet controller: Realtek Semiconductor Co., Ltd. RTL-8029(AS)
    05:0c.0 Ethernet controller: Marvell Technology Group Ltd. 88E8001 Gigabit Ethernet Controller (rev 13)
    ##########################################################
    >>>>
    # dmesg
    Linux version 2.6.19-gentoo-r4 (root@Kanotix) (gcc-Version 4.1.1 (Gentoo 4.1.1-r3)) #10 SMP Tue Feb 6 21:49:49 CET 2007
    Command line: root=/dev/hdb4
    BIOS-provided physical RAM map:
    BIOS-e820: 0000000000000000 - 000000000009f800 (usable)
    BIOS-e820: 000000000009f800 - 00000000000a0000 (reserved)
    BIOS-e820: 00000000000f0000 - 0000000000100000 (reserved)
    BIOS-e820: 0000000000100000 - 000000003fff0000 (usable)
    BIOS-e820: 000000003fff0000 - 000000003fff3000 (ACPI NVS)
    BIOS-e820: 000000003fff3000 - 0000000040000000 (ACPI data)
    BIOS-e820: 00000000e0000000 - 00000000f0000000 (reserved)
    BIOS-e820: 00000000fec00000 - 0000000100000000 (reserved)
    Entering add_active_range(0, 0, 159) 0 entries of 3200 used
    Entering add_active_range(0, 256, 262128) 1 entries of 3200 used
    end_pfn_map = 1048576
    DMI 2.3 present.
    ACPI: RSDP (v000 Nvidia ) @ 0x00000000000f7d30
    ACPI: RSDT (v001 Nvidia AWRDACPI 0x42302e31 AWRD 0x00000000) @ 0x000000003fff3040
    ACPI: FADT (v001 Nvidia AWRDACPI 0x42302e31 AWRD 0x00000000) @ 0x000000003fff30c0
    ACPI: SSDT (v001 PTLTD POWERNOW 0x00000001 LTP 0x00000001) @ 0x000000003fff9900
    ACPI: SRAT (v001 AMD HAMMER 0x00000001 AMD 0x00000001) @ 0x000000003fff9a40
    ACPI: MCFG (v001 Nvidia AWRDACPI 0x42302e31 AWRD 0x00000000) @ 0x000000003fff9b40
    ACPI: MADT (v001 Nvidia AWRDACPI 0x42302e31 AWRD 0x00000000) @ 0x000000003fff9840
    ACPI: DSDT (v001 NVIDIA AWRDACPI 0x00001000 MSFT 0x0100000e) @ 0x0000000000000000
    SRAT: PXM 0 -> APIC 0 -> Node 0
    SRAT: Node 0 PXM 0 0-a0000
    Entering add_active_range(0, 0, 159) 0 entries of 3200 used
    SRAT: Node 0 PXM 0 0-40000000
    Entering add_active_range(0, 0, 159) 1 entries of 3200 used
    Entering add_active_range(0, 256, 262128) 1 entries of 3200 used
    NUMA: Using 63 for the hash shift.
    Bootmem setup node 0 0000000000000000-000000003fff0000
    Zone PFN ranges:
    DMA 0 -> 4096
    DMA32 4096 -> 1048576
    Normal 1048576 -> 1048576
    early_node_map[2] active PFN ranges
    0: 0 -> 159
    0: 256 -> 262128
    On node 0 totalpages: 262031
    DMA zone: 56 pages used for memmap
    DMA zone: 1947 pages reserved
    DMA zone: 1996 pages, LIFO batch:0
    DMA32 zone: 3527 pages used for memmap
    DMA32 zone: 254505 pages, LIFO batch:31
    Normal zone: 0 pages used for memmap
    Nvidia board detected. Ignoring ACPI timer override.
    If you got timer trouble try acpi_use_timer_override
    ACPI: PM-Timer IO Port: 0x4008
    ACPI: Local APIC address 0xfee00000
    ACPI: LAPIC (acpi_id[0x00] lapic_id[0x00] enabled)
    Processor #0 (Bootup-CPU)
    ACPI: LAPIC (acpi_id[0x01] lapic_id[0x01] disabled)
    ACPI: LAPIC_NMI (acpi_id[0x00] high edge lint[0x1])
    ACPI: LAPIC_NMI (acpi_id[0x01] high edge lint[0x1])
    ACPI: IOAPIC (id[0x02] address[0xfec00000] gsi_base[0])
    IOAPIC[0]: apic_id 2, address 0xfec00000, GSI 0-23
    ACPI: INT_SRC_OVR (bus 0 bus_irq 0 global_irq 2 dfl dfl)
    ACPI: BIOS IRQ0 pin2 override ignored.
    ACPI: INT_SRC_OVR (bus 0 bus_irq 9 global_irq 9 high level)
    ACPI: INT_SRC_OVR (bus 0 bus_irq 14 global_irq 14 high edge)
    ACPI: INT_SRC_OVR (bus 0 bus_irq 15 global_irq 15 high edge)
    ACPI: IRQ9 used by override.
    ACPI: IRQ14 used by override.
    ACPI: IRQ15 used by override.
    Setting APIC routing to flat
    Using ACPI (MADT) for SMP configuration information
    Nosave address range: 000000000009f000 - 00000000000a0000
    Nosave address range: 00000000000a0000 - 00000000000f0000
    Nosave address range: 00000000000f0000 - 0000000000100000
    Allocating PCI resources starting at 50000000 (gap: 40000000:a0000000)
    PERCPU: Allocating 33984 bytes of per cpu data
    Built 1 zonelists. Total pages: 256501
    Kernel command line: root=/dev/hdb4
    Initializing CPU#0
    PID hash table entries: 4096 (order: 12, 32768 bytes)
    Console: colour VGA+ 80x25
    Dentry cache hash table entries: 131072 (order: 8, 1048576 bytes)
    Inode-cache hash table entries: 65536 (order: 7, 524288 bytes)
    Checking aperture...
    CPU 0: aperture @ 208000000 size 32 MB
    Aperture too small (32 MB)
    No AGP bridge found
    Memory: 1023816k/1048512k available (4076k kernel code, 24308k reserved, 2587k data, 352k init)
    Calibrating delay using timer specific routine.. 4435.85 BogoMIPS (lpj=8871702)
    Mount-cache hash table entries: 256
    CPU: L1 I Cache: 64K (64 bytes/line), D cache 64K (64 bytes/line)
    CPU: L2 Cache: 1024K (64 bytes/line)
    CPU 0/0 -> Node 0
    SMP alternatives: switching to UP code
    Freeing SMP alternatives: 44k freed
    ACPI: Core revision 20060707
    Using local APIC timer interrupts.
    result 12593973
    Detected 12.593 MHz APIC timer.
    Brought up 1 CPUs
    testing NMI watchdog ... OK.
    time.c: Using 3.579545 MHz WALL PM GTOD PIT/TSC timer.
    time.c: Detected 2216.539 MHz processor.
    PM: Adding info for No Bus:platform
    NET: Registered protocol family 16
    ACPI: bus type pci registered
    PCI: Using MMCONFIG at e0000000
    PCI: No mmconfig possible on device 00:18
    pci_get_subsys() called while pci_devices is still empty
    pci_get_subsys() called while pci_devices is still empty
    pci_get_subsys() called while pci_devices is still empty
    pci_get_subsys() called while pci_devices is still empty
    pci_get_subsys() called while pci_devices is still empty
    pci_get_subsys() called while pci_devices is still empty
    pci_get_subsys() called while pci_devices is still empty
    pci_get_subsys() called while pci_devices is still empty
    pci_get_subsys() called while pci_devices is still empty
    pci_get_subsys() called while pci_devices is still empty
    pci_get_subsys() called while pci_devices is still empty
    pci_get_subsys() called while pci_devices is still empty
    pci_get_subsys() called while pci_devices is still empty
    pci_get_subsys() called while pci_devices is still empty
    pci_get_subsys() called while pci_devices is still empty
    pci_get_subsys() called while pci_devices is still empty
    pci_get_subsys() called while pci_devices is still empty
    pci_get_subsys() called while pci_devices is still empty
    pci_get_subsys() called while pci_devices is still empty
    pci_get_subsys() called while pci_devices is still empty
    pci_get_subsys() called while pci_devices is still empty
    pci_get_subsys() called while pci_devices is still empty
    pci_get_subsys() called while pci_devices is still empty
    pci_get_subsys() called while pci_devices is still empty
    pci_get_subsys() called while pci_devices is still empty
    pci_get_subsys() called while pci_devices is still empty
    pci_get_subsys() called while pci_devices is still empty
    pci_get_subsys() called while pci_devices is still empty
    pci_get_subsys() called while pci_devices is still empty
    pci_get_subsys() called while pci_devices is still empty
    pci_get_subsys() called while pci_devices is still empty
    pci_get_subsys() called while pci_devices is still empty
    pci_get_subsys() called while pci_devices is still empty
    pci_get_subsys() called while pci_devices is still empty
    ACPI: Interpreter enabled
    ACPI: Using IOAPIC for interrupt routing
    PM: Adding info for acpi:acpi
    ACPI: PCI Root Bridge [PCI0] (0000:00)
    PCI: Probing PCI hardware (bus 00)
    PM: Adding info for No Bus:pci0000:00
    PCI: Transparent bridge - 0000:00:09.0
    Boot video device is 0000:01:00.0
    ACPI: PCI Interrupt Routing Table [\_SB_.PCI0._PRT]
    PM: Adding info for pci:0000:00:00.0
    PM: Adding info for pci:0000:00:01.0
    PM: Adding info for pci:0000:00:01.1
    PM: Adding info for pci:0000:00:02.0
    PM: Adding info for pci:0000:00:02.1
    PM: Adding info for pci:0000:00:04.0
    PM: Adding info for pci:0000:00:06.0
    PM: Adding info for pci:0000:00:09.0
    PM: Adding info for pci:0000:00:0a.0
    PM: Adding info for pci:0000:00:0b.0
    PM: Adding info for pci:0000:00:0c.0
    PM: Adding info for pci:0000:00:0d.0
    PM: Adding info for pci:0000:00:0e.0
    PM: Adding info for pci:0000:00:18.0
    PM: Adding info for pci:0000:00:18.1
    PM: Adding info for pci:0000:00:18.2
    PM: Adding info for pci:0000:00:18.3
    PM: Adding info for pci:0000:05:06.0
    PM: Adding info for pci:0000:05:06.1
    PM: Adding info for pci:0000:05:08.0
    PM: Adding info for pci:0000:05:0c.0
    PM: Adding info for pci:0000:01:00.0
    ACPI: PCI Interrupt Routing Table [\_SB_.PCI0.HUB0._PRT]
    ACPI: PCI Interrupt Link [LNK1] (IRQs *3 4 5 7 9 10 11 12 14 15)
    ACPI: PCI Interrupt Link [LNK2] (IRQs 3 4 5 7 9 10 *11 12 14 15)
    ACPI: PCI Interrupt Link [LNK3] (IRQs 3 4 *5 7 9 10 11 12 14 15)
    ACPI: PCI Interrupt Link [LNK4] (IRQs 3 4 5 7 9 10 11 12 14 15) *0, disabled.
    ACPI: PCI Interrupt Link [LNK5] (IRQs 3 4 5 7 9 10 11 12 14 15) *0, disabled.
    ACPI: PCI Interrupt Link [LUBA] (IRQs *3 4 5 7 9 10 11 12 14 15)
    ACPI: PCI Interrupt Link [LUBB] (IRQs 3 4 5 7 9 10 11 12 14 15) *0, disabled.
    ACPI: PCI Interrupt Link [LMAC] (IRQs 3 4 *5 7 9 10 11 12 14 15)
    ACPI: PCI Interrupt Link [LACI] (IRQs 3 4 5 7 9 10 *11 12 14 15)
    ACPI: PCI Interrupt Link [LMCI] (IRQs 3 4 5 7 9 10 11 12 14 15) *0, disabled.
    ACPI: PCI Interrupt Link [LSMB] (IRQs 3 4 *5 7 9 10 11 12 14 15)
    ACPI: PCI Interrupt Link [LUB2] (IRQs 3 4 5 7 9 10 *11 12 14 15)
    ACPI: PCI Interrupt Link [LIDE] (IRQs 3 4 5 7 9 10 11 12 14 15) *0, disabled.
    ACPI: PCI Interrupt Link [LSID] (IRQs 3 4 5 7 9 10 11 12 14 15) *0, disabled.
    ACPI: PCI Interrupt Link [LFID] (IRQs 3 4 5 7 9 10 11 12 14 15) *0, disabled.
    ACPI: PCI Interrupt Link [LPCA] (IRQs 3 4 5 7 9 10 11 12 14 15) *0, disabled.
    ACPI: PCI Interrupt Link [APC1] (IRQs 16) *0, disabled.
    ACPI: PCI Interrupt Link [APC2] (IRQs 17) *0, disabled.
    ACPI: PCI Interrupt Link [APC3] (IRQs 18) *0, disabled.
    ACPI: PCI Interrupt Link [APC4] (IRQs 19) *0, disabled.
    ACPI: PCI Interrupt Link [APC5] (IRQs *16), disabled.
    ACPI: PCI Interrupt Link [APCF] (IRQs 20 21 22 23) *0, disabled.
    ACPI: PCI Interrupt Link [APCG] (IRQs 20 21 22 23) *0, disabled.
    ACPI: PCI Interrupt Link [APCH] (IRQs 20 21 22 23) *0, disabled.
    ACPI: PCI Interrupt Link [APCJ] (IRQs 20 21 22 23) *0, disabled.
    ACPI: PCI Interrupt Link [APCK] (IRQs 20 21 22 23) *0, disabled.
    ACPI: PCI Interrupt Link [APCS] (IRQs 20 21 22 23) *0, disabled.
    ACPI: PCI Interrupt Link [APCL] (IRQs 20 21 22 23) *0, disabled.
    ACPI: PCI Interrupt Link [APCZ] (IRQs 20 21 22 23) *0, disabled.
    ACPI: PCI Interrupt Link [APSI] (IRQs 20 21 22 23) *0, disabled.
    ACPI: PCI Interrupt Link [APSJ] (IRQs 20 21 22 23) *0, disabled.
    ACPI: PCI Interrupt Link [APCP] (IRQs 20 21 22 23) *0, disabled.
    Linux Plug and Play Support v0.97 (c) Adam Belay
    pnp: PnP ACPI init
    PM: Adding info for No Bus:pnp0
    pnp: ACPI device : hid PNP0A08
    PM: Adding info for pnp:00:00
    pnp: ACPI device : hid PNP0C02
    PM: Adding info for pnp:00:01
    pnp: ACPI device : hid PNP0C02
    PM: Adding info for pnp:00:02
    pnp: ACPI device : hid PNP0200
    PM: Adding info for pnp:00:03
    pnp: ACPI device : hid PNP0B00
    PM: Adding info for pnp:00:04
    pnp: ACPI device : hid PNP0800
    PM: Adding info for pnp:00:05
    pnp: ACPI device : hid PNP0C04
    PM: Adding info for pnp:00:06
    pnp: ACPI device : hid PNP0700
    PM: Adding info for pnp:00:07
    pnp: ACPI device : hid PNP0501
    PM: Adding info for pnp:00:08
    pnp: ACPI device : hid PNP0401
    PM: Adding info for pnp:00:09
    pnp: ACPI device : hid PNP0F13
    PM: Adding info for pnp:00:0a
    pnp: ACPI device : hid PNPB006
    PM: Adding info for pnp:00:0b
    pnp: ACPI device : hid PNPB02F
    PM: Adding info for pnp:00:0c
    pnp: ACPI device : hid PNP0C02
    PM: Adding info for pnp:00:0d
    pnp: ACPI device : hid PNP0C01
    PM: Adding info for pnp:00:0e
    pnp: PnP ACPI: found 15 devices
    SCSI subsystem initialized
    libata version 2.00 loaded.
    usbcore: registered new interface driver usbfs
    usbcore: registered new interface driver hub
    usbcore: registered new device driver usb
    PCI: Using ACPI for IRQ routing
    PCI: If a device doesn't work, try "pci=routeirq". If it helps, post a report
    Bluetooth: Core ver 2.11
    PM: Adding info for platform:bluetooth
    NET: Registered protocol family 31
    Bluetooth: HCI device and connection manager initialized
    Bluetooth: HCI socket layer initialized
    PCI-DMA: Disabling IOMMU.
    pnp: the driver 'system' has been registered
    pnp: match found with the PnP device '00:01' and the driver 'system'
    pnp: 00:01: ioport range 0x4000-0x407f could not be reserved
    pnp: 00:01: ioport range 0x4080-0x40ff has been reserved
    pnp: 00:01: ioport range 0x4400-0x447f has been reserved
    pnp: 00:01: ioport range 0x4480-0x44ff could not be reserved
    pnp: 00:01: ioport range 0x4800-0x487f has been reserved
    pnp: 00:01: ioport range 0x4880-0x48ff has been reserved
    pnp: match found with the PnP device '00:02' and the driver 'system'
    pnp: match found with the PnP device '00:0d' and the driver 'system'
    pnp: match found with the PnP device '00:0e' and the driver 'system'
    PCI: Bridge: 0000:00:09.0
    IO window: c000-cfff
    MEM window: c3000000-c4ffffff
    PREFETCH window: c5000000-c50fffff
    PCI: Bridge: 0000:00:0b.0
    IO window: disabled.
    MEM window: disabled.
    PREFETCH window: disabled.
    PCI: Bridge: 0000:00:0c.0
    IO window: disabled.
    MEM window: disabled.
    PREFETCH window: disabled.
    PCI: Bridge: 0000:00:0d.0
    IO window: disabled.
    MEM window: disabled.
    PREFETCH window: disabled.
    PCI: Bridge: 0000:00:0e.0
    IO window: disabled.
    MEM window: c0000000-c2ffffff
    PREFETCH window: b0000000-bfffffff
    PCI: Setting latency timer of device 0000:00:09.0 to 64
    PCI: Setting latency timer of device 0000:00:0b.0 to 64
    PCI: Setting latency timer of device 0000:00:0c.0 to 64
    PCI: Setting latency timer of device 0000:00:0d.0 to 64
    PCI: Setting latency timer of device 0000:00:0e.0 to 64
    NET: Registered protocol family 2
    IP route cache hash table entries: 32768 (order: 6, 262144 bytes)
    TCP established hash table entries: 131072 (order: 9, 2097152 bytes)
    TCP bind hash table entries: 65536 (order: 8, 1048576 bytes)
    TCP: Hash tables configured (established 131072 bind 65536)
    TCP reno registered
    audit: initializing netlink socket (disabled)
    audit(1170800964.396:1): initialized
    Total HugeTLB memory allocated, 0
    Installing knfsd (copyright (C) 1996 okir@monad.swb.de).
    NTFS driver 2.1.27 [Flags: R/W DEBUG].
    JFS: nTxBlock = 7998, nTxLock = 63991
    SGI XFS with large block/inode numbers, no debug enabled
    io scheduler noop registered
    io scheduler deadline registered
    io scheduler cfq registered (default)
    PCI: Linking AER extended capability on 0000:00:0b.0
    PCI: Found HT MSI mapping on 0000:00:0b.0 with capability disabled
    PCI: Found HT MSI mapping on 0000:00:00.0 with capability enabled
    PCI: Linking AER extended capability on 0000:00:0c.0
    PCI: Found HT MSI mapping on 0000:00:0c.0 with capability disabled
    PCI: Found HT MSI mapping on 0000:00:00.0 with capability enabled
    PCI: Linking AER extended capability on 0000:00:0d.0
    PCI: Found HT MSI mapping on 0000:00:0d.0 with capability disabled
    PCI: Found HT MSI mapping on 0000:00:00.0 with capability enabled
    PCI: Linking AER extended capability on 0000:00:0e.0
    PCI: Found HT MSI mapping on 0000:00:0e.0 with capability disabled
    PCI: Found HT MSI mapping on 0000:00:00.0 with capability enabled
    PCI: Setting latency timer of device 0000:00:0b.0 to 64
    pcie_portdrv_probe->Dev[005d:10de] has invalid IRQ. Check vendor BIOS
    assign_interrupt_mode Found MSI capability
    Allocate Port Service[0000:00:0b.0:pcie00]
    PM: Adding info for pci_express:0000:00:0b.0:pcie00
    Allocate Port Service[0000:00:0b.0:pcie03]
    PM: Adding info for pci_express:0000:00:0b.0:pcie03
    PCI: Setting latency timer of device 0000:00:0c.0 to 64
    pcie_portdrv_probe->Dev[005d:10de] has invalid IRQ. Check vendor BIOS
    assign_interrupt_mode Found MSI capability
    Allocate Port Service[0000:00:0c.0:pcie00]
    PM: Adding info for pci_express:0000:00:0c.0:pcie00
    Allocate Port Service[0000:00:0c.0:pcie03]
    PM: Adding info for pci_express:0000:00:0c.0:pcie03
    PCI: Setting latency timer of device 0000:00:0d.0 to 64
    pcie_portdrv_probe->Dev[005d:10de] has invalid IRQ. Check vendor BIOS
    assign_interrupt_mode Found MSI capability
    Allocate Port Service[0000:00:0d.0:pcie00]
    PM: Adding info for pci_express:0000:00:0d.0:pcie00
    Allocate Port Service[0000:00:0d.0:pcie03]
    PM: Adding info for pci_express:0000:00:0d.0:pcie03
    PCI: Setting latency timer of device 0000:00:0e.0 to 64
    pcie_portdrv_probe->Dev[005d:10de] has invalid IRQ. Check vendor BIOS
    assign_interrupt_mode Found MSI capability
    Allocate Port Service[0000:00:0e.0:pcie00]
    PM: Adding info for pci_express:0000:00:0e.0:pcie00
    Allocate Port Service[0000:00:0e.0:pcie03]
    PM: Adding info for pci_express:0000:00:0e.0:pcie03
    Real Time Clock Driver v1.12ac
    Non-volatile memory driver v1.2
    Linux agpgart interface v0.101 (c) Dave Jones
    PM: Adding info for platform:vesafb.0
    PM: Adding info for platform:vga16fb.0
    vga16fb: initializing
    vga16fb: mapped to 0xffff8100000a0000
    fb0: VGA16 VGA frame buffer device
    ACPI: Power Button (FF) [PWRF]
    ACPI: Power Button (CM) [PWRB]
    ACPI: Fan [FAN] (on)
    ACPI: Getting cpuindex for acpiid 0x1
    ACPI: Thermal Zone [THRM] (40 C)
    Serial: 8250/16550 driver $Revision: 1.90 $ 4 ports, IRQ sharing enabled
    PM: Adding info for platform:serial8250
    serial8250: ttyS0 at I/O 0x3f8 (irq = 4) is a 16550A
    pnp: the driver 'serial' has been registered
    pnp: match found with the PnP device '00:08' and the driver 'serial'
    00:08: ttyS0 at I/O 0x3f8 (irq = 4) is a 16550A
    Floppy drive(s): fd0 is 1.44M
    FDC 0 is a post-1991 82077
    PM: Adding info for platform:floppy.0
    RAMDISK driver initialized: 16 RAM disks of 4096K size 1024 blocksize
    loop: loaded (max 8 devices)
    Intel(R) PRO/1000 Network Driver - version 7.2.9-k4-NAPI
    Copyright (c) 1999-2006 Intel Corporation.
    e100: Intel(R) PRO/100 Network Driver, 3.5.17-k2-NAPI
    e100: Copyright(c) 1999-2006 Intel Corporation
    ACPI: PCI Interrupt Link [APC2] enabled at IRQ 17
    ACPI: PCI Interrupt 0000:05:0c.0[A] -> Link [APC2] -> GSI 17 (level, low) -> IRQ 17
    eth0: Yukon Gigabit Ethernet 10/100/1000Base-T Adapter
    PrefPort:A RlmtMode:Check Link State
    forcedeth.c: Reverse Engineered nForce ethernet driver. Version 0.57.
    ACPI: PCI Interrupt Link [APCH] enabled at IRQ 23
    ACPI: PCI Interrupt 0000:00:0a.0[A] -> Link [APCH] -> GSI 23 (level, low) -> IRQ 23
    PCI: Setting latency timer of device 0000:00:0a.0 to 64
    forcedeth: using HIGHDMA
    eth1: forcedeth.c: subsystem: 01043:8141 bound to 0000:00:0a.0
    tun: Universal TUN/TAP device driver, 1.6
    tun: (C) 1999-2004 Max Krasnyansky <maxk@qualcomm.com>
    netconsole: not configured, aborting
    Uniform Multi-Platform E-IDE driver Revision: 7.00alpha2
    ide: Assuming 33MHz system bus speed for PIO modes; override with idebus=xx
    NFORCE-CK804: IDE controller at PCI slot 0000:00:06.0
    NFORCE-CK804: chipset revision 242
    NFORCE-CK804: not 100% native mode: will probe irqs later
    NFORCE-CK804: 0000:00:06.0 (rev f2) UDMA133 controller
    ide0: BM-DMA at 0xf000-0xf007, BIOS settings: hda:DMA, hdb:DMA
    ide1: BM-DMA at 0xf008-0xf00f, BIOS settings: hdc:DMA, hdd:DMA
    Probing IDE interface ide0...
    hda: WDC WD2000JB-00GVC0, ATA DISK drive
    PM: Adding info for No Bus:ide0
    hdb: ST380020A, ATA DISK drive
    ide0 at 0x1f0-0x1f7,0x3f6 on irq 14
    PM: Adding info for ide:0.0
    PM: Adding info for ide:0.1
    Probing IDE interface ide1...
    hdc: TSSTcorpCD/DVDW SH-S182M, ATAPI CD/DVD-ROM drive
    PM: Adding info for No Bus:ide1
    ide1 at 0x170-0x177,0x376 on irq 15
    PM: Adding info for ide:1.0
    pnp: the driver 'ide' has been registered
    hda: max request size: 512KiB
    hda: 390721968 sectors (200049 MB) w/8192KiB Cache, CHS=24321/255/63, UDMA(100)
    hda: cache flushes supported
    hda:hda: dma_intr: status=0x51 { DriveReady SeekComplete Error }
    hda: dma_intr: error=0x84 { DriveStatusError BadCRC }
    ide: failed opcode was: unknown
    hda: dma_intr: status=0x51 { DriveReady SeekComplete Error }
    hda: dma_intr: error=0x84 { DriveStatusError BadCRC }
    ide: failed opcode was: unknown
    hda: dma_intr: status=0x51 { DriveReady SeekComplete Error }
    hda: dma_intr: error=0x84 { DriveStatusError BadCRC }
    ide: failed opcode was: unknown
    hda: dma_intr: status=0x51 { DriveReady SeekComplete Error }
    hda: dma_intr: error=0x84 { DriveStatusError BadCRC }
    ide: failed opcode was: unknown
    hdb: DMA disabled
    ide0: reset: success
    hda: dma_intr: status=0x51 { DriveReady SeekComplete Error }
    hda: dma_intr: error=0x84 { DriveStatusError BadCRC }
    ide: failed opcode was: unknown
    hda: dma_intr: status=0x51 { DriveReady SeekComplete Error }
    hda: dma_intr: error=0x84 { DriveStatusError BadCRC }
    ide: failed opcode was: unknown
    hda: dma_intr: status=0x51 { DriveReady SeekComplete Error }
    hda: dma_intr: error=0x84 { DriveStatusError BadCRC }
    ide: failed opcode was: unknown
    hda: dma_intr: status=0x51 { DriveReady SeekComplete Error }
    hda: dma_intr: error=0x84 { DriveStatusError BadCRC }
    ide: failed opcode was: unknown
    ide0: reset: success
    hda1 hda2 < hda5 >
    hdb: max request size: 128KiB
    hdb: 156301488 sectors (80026 MB) w/2048KiB Cache, CHS=65535/16/63
    hdb: cache flushes not supported
    hdb: hdb1 hdb2 hdb3 < hdb5 > hdb4
    hdc: ATAPI 48X DVD-ROM DVD-R-RAM CD-R/RW drive, 2048kB Cache, UDMA(33)
    Uniform CD-ROM driver Revision: 3.20
    megaraid cmm: 2.20.2.7 (Release Date: Sun Jul 16 00:01:03 EST 2006)
    megaraid: 2.20.4.9 (Release Date: Sun Jul 16 12:27:22 EST 2006)
    megasas: 00.00.03.05 Mon Oct 02 11:21:32 PDT 2006
    Fusion MPT base driver 3.04.02
    Copyright (c) 1999-2005 LSI Logic Corporation
    Fusion MPT SPI Host driver 3.04.02
    Fusion MPT SAS Host driver 3.04.02
    ieee1394: raw1394: /dev/raw1394 device initialized
    ACPI: PCI Interrupt Link [APCL] enabled at IRQ 22
    ACPI: PCI Interrupt 0000:00:02.1 -> Link [APCL] -> GSI 22 (level, low) -> IRQ 22
    PCI: Setting latency timer of device 0000:00:02.1 to 64
    ehci_hcd 0000:00:02.1: EHCI Host Controller
    ehci_hcd 0000:00:02.1: new USB bus registered, assigned bus number 1
    ehci_hcd 0000:00:02.1: debug port 1
    PCI: cache line size of 64 is not supported by device 0000:00:02.1
    ehci_hcd 0000:00:02.1: irq 22, io mem 0xfeb00000
    ehci_hcd 0000:00:02.1: USB 2.0 started, EHCI 1.00, driver 10 Dec 2004
    PM: Adding info for usb:usb1
    PM: Adding info for No Bus:usbdev1.1_ep00
    usb usb1: configuration #1 chosen from 1 choice
    PM: Adding info for usb:1-0:1.0
    hub 1-0:1.0: USB hub found
    hub 1-0:1.0: 10 ports detected
    PM: Adding info for No Bus:usbdev1.1_ep81
    ohci_hcd: 2006 August 04 USB 1.1 'Open' Host Controller (OHCI) Driver (PCI)
    ACPI: PCI Interrupt Link [APCF] enabled at IRQ 21
    ACPI: PCI Interrupt 0000:00:02.0[A] -> Link [APCF] -> GSI 21 (level, low) -> IRQ 21
    PCI: Setting latency timer of device 0000:00:02.0 to 64
    ohci_hcd 0000:00:02.0: OHCI Host Controller
    ohci_hcd 0000:00:02.0: new USB bus registered, assigned bus number 2
    ohci_hcd 0000:00:02.0: irq 21, io mem 0xc5102000
    PM: Adding info for usb:usb2
    PM: Adding info for No Bus:usbdev2.1_ep00
    usb usb2: configuration #1 chosen from 1 choice
    PM: Adding info for usb:2-0:1.0
    hub 2-0:1.0: USB hub found
    hub 2-0:1.0: 10 ports detected
    PM: Adding info for No Bus:usbdev2.1_ep81
    USB Universal Host Controller Interface driver v3.0
    usb 2-2: new full speed USB device using ohci_hcd and address 2
    PM: Adding info for usb:2-2
    PM: Adding info for No Bus:usbdev2.2_ep00
    usb 2-2: configuration #1 chosen from 1 choice
    PM: Adding info for usb:2-2:1.0
    PM: Adding info for No Bus:usbdev2.2_ep81
    PM: Adding info for No Bus:usbdev2.2_ep02
    usb 2-10: new full speed USB device using ohci_hcd and address 3
    PM: Adding info for usb:2-10
    PM: Adding info for No Bus:usbdev2.3_ep00
    usb 2-10: configuration #1 chosen from 1 choice
    PM: Adding info for usb:2-10:1.0
    hub 2-10:1.0: USB hub found
    hub 2-10:1.0: 4 ports detected
    PM: Adding info for No Bus:usbdev2.3_ep81
    usb 2-10.1: new low speed USB device using ohci_hcd and address 4
    PM: Adding info for usb:2-10.1
    PM: Adding info for No Bus:usbdev2.4_ep00
    usb 2-10.1: configuration #1 chosen from 1 choice
    PM: Adding info for usb:2-10.1:1.0
    PM: Adding info for No Bus:usbdev2.4_ep81
    PM: Adding info for usb:2-10.1:1.1
    PM: Adding info for No Bus:usbdev2.4_ep82
    usb 2-10.4: new full speed USB device using ohci_hcd and address 5
    PM: Adding info for usb:2-10.4
    PM: Adding info for No Bus:usbdev2.5_ep00
    usb 2-10.4: configuration #1 chosen from 1 choice
    PM: Adding info for usb:2-10.4:1.0
    PM: Adding info for No Bus:usbdev2.5_ep81
    PM: Adding info for No Bus:usbdev2.5_ep02
    usbcore: registered new interface driver usblp
    drivers/usb/class/usblp.c: v0.13: USB Printer Device Class driver
    Initializing USB Mass Storage driver...
    usbcore: registered new interface driver usb-storage
    USB Mass Storage support registered.
    input: Logitech Logitech Gaming Keyboard as /class/input/input0
    input: USB HID v1.10 Keyboard [Logitech Logitech Gaming Keyboard] on usb-0000:00:02.0-10.1
    input: Logitech Logitech Gaming Keyboard as /class/input/input1
    input: USB HID v1.10 Device [Logitech Logitech Gaming Keyboard] on usb-0000:00:02.0-10.1
    input: G15 Keyboard G15 Keyboard as /class/input/input2
    input: USB HID v1.11 Keypad [G15 Keyboard G15 Keyboard] on usb-0000:00:02.0-10.4
    usbcore: registered new interface driver usbhid
    drivers/usb/input/hid-core.c: v2.6:USB HID core driver
    usbcore: registered new interface driver wacom
    drivers/usb/input/wacom_sys.c: v1.46:USB Wacom Graphire and Wacom Intuos tablet driver
    usbcore: registered new interface driver usblcd
    pnp: the driver 'i8042 kbd' has been registered
    pnp: the driver 'i8042 aux' has been registered
    pnp: match found with the PnP device '00:0a' and the driver 'i8042 aux'
    PNP: PS/2 Controller [PNP0f13:PS2M] at 0x60,0x64 irq 12
    PNP: PS/2 controller doesn't have KBD irq; using default 1
    PM: Adding info for platform:i8042
    serio: i8042 KBD port at 0x60,0x64 irq 1
    serio: i8042 AUX port at 0x60,0x64 irq 12
    PM: Adding info for serio:serio0
    pnp: the driver 'ns558' has been registered
    PM: Adding info for serio:serio1
    pnp: match found with the PnP device '00:0c' and the driver 'ns558'
    gameport: NS558 PnP Gameport is pnp00:0c/gameport0, io 0x201, speed 908kHz
    PM: Adding info for gameport:gameport0
    mice: PS/2 mouse device common for all mice
    device-mapper: ioctl: 4.10.0-ioctl (2006-09-14) initialised: dm-devel@redhat.com
    Bluetooth: HCI USB driver ver 2.9
    usbcore: registered new interface driver hci_usb
    oprofile: using NMI interrupt.
    TCP watch registered (port=0)
    TCP cubic registered
    NET: Registered protocol family 1
    NET: Registered protocol family 10
    IPv6 over IPv4 tunneling driver
    NET: Registered protocol family 17
    powernow-k8: Found 1 AMD Athlon(tm) 64 Processor 3700+ processors (version 2.00.00)
    powernow-k8: 0 : fid 0xe (2200 MHz), vid 0x8
    powernow-k8: 1 : fid 0xc (2000 MHz), vid 0x8
    powernow-k8: 2 : fid 0xa (1800 MHz), vid 0xa
    powernow-k8: 3 : fid 0x2 (1000 MHz), vid 0x12
    input: ImExPS/2 Generic Explorer Mouse as /class/input/input3
    md: Autodetecting RAID arrays.
    md: autorun ...
    md: ... autorun DONE.
    kjournald starting. Commit interval 5 seconds
    EXT3-fs: mounted filesystem with ordered data mode.
    VFS: Mounted root (ext3 filesystem) readonly.
    Freeing unused kernel memory: 352k freed
    Losing some ticks... checking if CPU frequency changed.
    PCI: Enabling device 0000:00:04.0 (0000 -> 0003)
    ACPI: PCI Interrupt Link [APCJ] enabled at IRQ 20
    ACPI: PCI Interrupt 0000:00:04.0[A] -> Link [APCJ] -> GSI 20 (level, low) -> IRQ 20
    PCI: Setting latency timer of device 0000:00:04.0 to 64
    intel8x0_measure_ac97_clock: measured 50401 usecs
    intel8x0: clocking to 44390
    PM: Adding info for ac97:0-0:ALC850
    EXT3 FS on hdb4, internal journal
    Adding 1301256k swap on /dev/hdb2. Priority:-1 extents:1 across:1301256k
    ADDRCONF(NETDEV_UP): eth0: link is not ready
    eth0: network connection down
    eth1: no IPv6 routers present
    warning: many lost ticks.
    Your time source seems to be instable or some driver is hogging interupts
    rip 0x2b3edfea8f20
    #########################################################
    .
    .
    .
    EDIT (autom. Beitragszusammenführung) :
    .

    vieleicht ist die einfach nicht richtig konfiguriert ;)

    ################ make.conf ##################################
    # Host Setting
    # ============
    #
    CHOST="x86_64-pc-linux-gnu"

    # Host and optimization settings
    # ==============================
    #
    # For optimal performance, enable a CFLAGS setting appropriate for your CPU.
    #
    # Please note that if you experience strange issues with a package, it may be
    # due to gcc's optimizations interacting in a strange way. Please test the
    # package (and in some cases the libraries it uses) at default optimizations
    # before reporting errors to developers.
    #
    # -mcpu=<cpu-type> means optimize code for the particular type of CPU without
    # breaking compatibility with other CPUs. GCC 3.4 has deprecated support for
    # -mcpu, so use -mtune instead if using this compiler.
    #
    # -march=<cpu-type> means to take full advantage of the ABI and instructions
    # for the particular CPU; this will break compatibility with older CPUs (for
    # example, -march=athlon-xp code will not run on a regular Athlon, and
    # -march=i686 code will not run on a Pentium Classic.)
    #
    # CPU types supported in gcc-3.2 and higher: athlon-xp, athlon-mp,
    # athlon-tbird, athlon, k6, k6-2, k6-3, i386, i486, i586 (Pentium), i686
    # (PentiumPro), pentium, pentium-mmx, pentiumpro, pentium2 (Celeron),
    # pentium3, and pentium4.
    #
    # Note that Gentoo Linux 1.4 and higher include at least gcc-3.2.
    #
    # amd64 CPU types supported in gcc-3.4: athlon64, opteron, k8
    #
    # CRITICAL WARNINGS: ****************************************************** #
    # K6 markings are deceptive. Avoid setting -march for them. See Bug #24379. #
    # Pentium-M CPU's should not enable sse2 until at least gcc-3.4. Bug 50616. #
    # GCC 3.3 doesnt support an amd64 specific -march setting, use 3.4. #
    # ************************************************************************* #
    #
    # Decent examples:
    #
    #CFLAGS="-mtune=k8 -O2 -pipe"
    CFLAGS="-march=athlon64 -O2 -pipe"

    # If you set a CFLAGS above, then this line will set your default C++ flags to
    # the same settings.
    CXXFLAGS="${CFLAGS}"

    # Advanced Masking
    # ================
    #
    # Gentoo is using a new masking system to allow for easier stability testing
    # on packages. KEYWORDS are used in ebuilds to mask and unmask packages based
    # on the platform they are set for. A special form has been added that
    # indicates packages and revisions that are expected to work, but have not yet
    # been approved for the stable set. '~arch' is a superset of 'arch' which
    # includes the unstable, in testing, packages. Users of the 'x86' architecture
    # would add '~x86' to ACCEPT_KEYWORDS to enable unstable/testing packages.
    # '~ppc', '~sparc' are the unstable KEYWORDS for their respective platforms.
    #
    # Please note that this is not for development, alpha, beta, nor cvs release
    # packages. "Broken" packages will not be added to testing and should not be
    # requested to be added. Alternative routes are available to developers
    # for experimental packages, and it is at their discretion to use them.
    #
    # DO NOT PUT ANYTHING BUT YOUR SPECIFIC ~ARCHITECTURE IN THE LIST.
    # IF YOU ARE UNSURE OF YOUR ARCH, OR THE IMPLICATIONS, DO NOT MODIFY THIS.
    #
    ACCEPT_KEYWORDS="~amd64"

    # Portage Directories
    # ===================
    #
    # Each of these settings controls an aspect of portage's storage and file
    # system usage. If you change any of these, be sure it is available when
    # you try to use portage. *** DO NOT INCLUDE A TRAILING "/" ***
    #
    # PORTAGE_TMPDIR is the location portage will use for compilations and
    # temporary storage of data. This can get VERY large depending upon
    # the application being installed.
    #PORTAGE_TMPDIR=/var/tmp
    #
    # PORTDIR is the location of the portage tree. This is the repository
    # for all profile information as well as all ebuilds. If you change
    # this, you must update your /etc/make.profile symlink accordingly.
    #PORTDIR=/usr/portage
    #
    # DISTDIR is where all of the source code tarballs will be placed for
    # emerges. The source code is maintained here unless you delete
    # it. The entire repository of tarballs for gentoo is 9G. This is
    # considerably more than any user will ever download. 2-3G is
    # a large DISTDIR.
    #DISTDIR=${PORTDIR}/distfiles
    #
    # PKGDIR is the location of binary packages that you can have created
    # with '--buildpkg' or '-b' while emerging a package. This can get
    # upto several hundred megs, or even a few gigs.
    #PKGDIR=${PORTDIR}/packages
    #
    # PORT_LOGDIR is the location where portage will store all the logs it
    # creates from each individual merge. They are stored as NNNN-$PF.log
    # in the directory specified. This is disabled until you enable it by
    # providing a directory. Permissions will be modified as needed IF the
    # directory exists, otherwise logging will be disabled. NNNN is the
    # increment at the time the log is created. Logs are thus sequential.
    #PORT_LOGDIR=/var/log/portage
    #
    # PORTDIR_OVERLAY is a directory where local ebuilds may be stored without
    # concern that they will be deleted by rsync updates. Default is not
    # defined.
    #PORTDIR_OVERLAY=/usr/local/portage

    # Fetching files
    # ==============
    #
    # If you need to set a proxy for wget or lukemftp, add the appropriate "export
    # ftp_proxy=<proxy>" and "export http_proxy=<proxy>" lines to /etc/profile if
    # all users on your system should use them.
    #
    # Portage uses wget by default. Here are some settings for some alternate
    # downloaders -- note that you need to merge these programs first before they
    # will be available.
    #
    # Default fetch command (5 tries, passive ftp for firewall compatibility)
    #FETCHCOMMAND="/usr/bin/wget -t 5 -T 60 --passive-ftp \${URI} -P \${DISTDIR}"
    #RESUMECOMMAND="/usr/bin/wget -c -t 5 -T 60 --passive-ftp \${URI} -P \${DISTDIR}"
    #
    # Using wget, ratelimiting downloads
    #FETCHCOMMAND="/usr/bin/wget -t 5 -T 60 --passive-ftp --limit-rate=200k \${URI} -P \${DISTDIR}"
    #RESUMECOMMAND="/usr/bin/wget -c -t 5 -T 60 --passive-ftp --limit-rate=200k \${URI} -P \${DISTDIR}"
    #
    # Lukemftp (BSD ftp):
    #FETCHCOMMAND="/usr/bin/lukemftp -s -a -o \${DISTDIR}/\${FILE} \${URI}"
    #RESUMECOMMAND="/usr/bin/lukemftp -s -a -R -o \${DISTDIR}/\${FILE} \${URI}"
    #
    # Portage uses GENTOO_MIRRORS to specify mirrors to use for source retrieval.
    # The list is a space separated list which is read left to right. If you use
    # another mirror we highly recommend leaving the default mirror at the end of
    # the list so that portage will fall back to it if the files cannot be found
    # on your specified mirror. We _HIGHLY_ recommend that you change this setting
    # to a nearby mirror by merging and using the 'mirrorselect' tool.
    #GENTOO_MIRRORS="<your_mirror_here> http://distfiles.gentoo.org http://www.ibiblio.org/pub/Linux/distributions/gentoo"
    #
    # Portage uses PORTAGE_BINHOST to specify mirrors for prebuilt-binary packages.
    # The list is a single entry specifying the full address of the directory
    # serving the tbz2's for your system. Running emerge with either '--getbinpkg'
    # or '--getbinpkgonly' will cause portage to retrieve the metadata from all
    # packages in the directory specified, and use that data to determine what will
    # be downloaded and merged. '-g' or '-gK' are the recommend parameters. Please
    # consult the man pages and 'emerge --help' for more information. For FTP, the
    # default connection is passive -- If you require an active connection, affix
    # an asterisk (*) to the end of the host:port string before the path.
    #PORTAGE_BINHOST="http://grp.mirror.site/gentoo/grp/1.4/i686/athlon-xp/"
    # This ftp connection is passive ftp.
    #PORTAGE_BINHOST="ftp://login:pass@grp.mirror.site/pub/grp/i686/athlon-xp/"
    # This ftp connection is active ftp.
    #PORTAGE_BINHOST="ftp://login:pass@grp.mirror.site:21*/pub/grp/i686/athlon-xp/"

    # Synchronizing Portage
    # =====================
    #
    # Each of these settings affects how Gentoo synchronizes your Portage tree.
    # Synchronization is handled by rsync and these settings allow some control
    # over how it is done.
    #
    #
    # SYNC is the server used by rsync to retrieve a localized rsync mirror
    # rotation. This allows you to select servers that are geographically
    # close to you, yet still distribute the load over a number of servers.
    # Please do not single out specific rsync mirrors. Doing so places undue
    # stress on particular mirrors. Instead you may use one of the following
    # continent specific rotations:
    #
    # Default: "rsync://rsync.gentoo.org/gentoo-portage"
    # North America: "rsync://rsync.namerica.gentoo.org/gentoo-portage"
    # South America: "rsync://rsync.samerica.gentoo.org/gentoo-portage"
    # Europe: "rsync://rsync.europe.gentoo.org/gentoo-portage"
    # Asia: "rsync://rsync.asia.gentoo.org/gentoo-portage"
    # Australia: "rsync://rsync.au.gentoo.org/gentoo-portage"
    #SYNC="rsync://rsync.gentoo.org/gentoo-portage"
    #
    # PORTAGE_RSYNC_RETRIES sets the number of times portage will attempt to retrieve
    # a current portage tree before it exits with an error. This allows
    # for a more successful retrieval without user intervention most times.
    #PORTAGE_RSYNC_RETRIES="3"
    #
    # PORTAGE_RSYNC_EXTRA_OPTS can be used to feed additional options to the rsync
    # command used by `emerge --sync`. This will not change the default options
    # which are set by PORTAGE_RSYNC_OPTS (don't change those unless you know
    # exactly what you're doing).
    #PORTAGE_RSYNC_EXTRA_OPTS=""
    #
    # Advanced Features
    # =================
    #
    # EMERGE_DEFAULT_OPTS allows emerge to act as if certain options are
    # specified on every run. Useful options include --ask, --verbose,
    # --usepkg and many others. Options that are not useful, such as --help,
    # are not filtered.
    #EMERGE_DEFAULT_OPTS=""
    #
    # MAKEOPTS provides extra options that may be passed to 'make' when a
    # program is compiled. Presently the only use is for specifying
    # the number of parallel makes (-j) to perform. The suggested number
    # for parallel makes is CPUs+1.
    MAKEOPTS="-j2"
    #
    # PORTAGE_NICENESS provides a default increment to emerge's niceness level.
    # Note: This is an increment. Running emerge in a niced environment will
    # reduce it further. Default is unset.
    #PORTAGE_NICENESS=3
    #
    # AUTOCLEAN enables portage to automatically clean out older or overlapping
    # packages from the system after every successful merge. This is the
    # same as running 'emerge -c' after every merge. Set with: "yes" or "no".
    # This does not affect the unpacked source. See 'noclean' below.
    #
    # Warning: AUTOCLEAN="no" can cause serious problems due to overlapping
    # packages. Do not use it unless absolutely necessary!
    #AUTOCLEAN="yes"
    #
    # PORTAGE_TMPFS is a location where portage may create temporary files.
    # If specified, portage will use this directory whenever possible
    # for all rapid operations such as lockfiles and transient data.
    # It is _highly_ recommended that this be a tmpfs or ramdisk. Do not
    # set this to anything that does not give a significant performance
    # enhancement and proper FS compliance for locks and read/write.
    # /dev/shm is a glibc mandated tmpfs, and should be a reasonable
    # setting for all linux kernel+glibc based systems.
    #PORTAGE_TMPFS="/dev/shm"
    #
    # FEATURES are settings that affect the functionality of portage. Most of
    # these settings are for developer use, but some are available to non-
    # developers as well.
    #
    # 'assume-digests'
    # when commiting work to cvs with repoman(1), assume that all
    # existing SRC_URI digests are correct. This feature also
    # affects digest generation via ebuild(1) and emerge(1) (emerge
    # generates digests only when the 'digest' feature is enabled).
    # 'autoaddcvs' causes portage to automatically try to add files to cvs
    # that will have to be added later. Done at generation times
    # and only has an effect when 'cvs' is also set.
    # 'buildpkg' causes binary packages to be created of all packages that
    # are being merged.
    # 'ccache' enables ccache support via CC.
    # 'confcache' enable confcache support; speeds up autotool based configure
    # calls
    # 'collision-protect'
    # prevents packages from overwriting files that are owned by
    # another package or by no package at all.
    # 'cvs' causes portage to enable all cvs features (commits, adds),
    # and to apply all USE flags in SRC_URI for digests -- for
    # developers only.
    # 'digest' autogenerate digests for packages when running the emerge(1)
    # command. If the 'assume-digests' feature is also enabled then
    # existing SRC_URI digests will be reused whenever they are
    # available.
    # 'distcc' enables distcc support via CC.
    # 'distlocks' enables distfiles locking using fcntl or hardlinks. This
    # is enabled by default. Tools exist to help clean the locks
    # after crashes: /usr/lib/portage/bin/clean_locks.
    # 'fixpackages' allows portage to fix binary packages that are stored in
    # PKGDIR. This can consume a lot of time. 'fixpackages' is
    # also a script that can be run at any given time to force
    # the same actions.
    # 'gpg' enables basic verification of Manifest files using gpg.
    # This features is UNDER DEVELOPMENT and reacts to features
    # of strict and severe. Heavy use of gpg sigs is coming.
    # 'keeptemp' prevents the clean phase from deleting the temp files ($T)
    # from a merge.
    # 'keepwork' prevents the clean phase from deleting the WORKDIR.
    # 'test' causes ebuilds to perform testing phases if they are capable
    # of it. Some packages support this automaticaly via makefiles.
    # 'metadata-transfer'
    # automatically perform a metadata transfer when `emerge --sync`
    # is run.
    # 'noauto' causes ebuild to perform only the action requested and
    # not any other required actions like clean or unpack -- for
    # debugging purposes only.
    # 'noclean' prevents portage from removing the source and temporary files
    # after a merge -- for debugging purposes only.
    # 'nostrip' prevents the stripping of binaries.
    # 'notitles' disables xterm titlebar updates (which contain status info).
    # 'parallel-fetch'
    # do fetching in parallel to compilation
    # 'sandbox' enables sandboxing when running emerge and ebuild.
    # 'strict' causes portage to react strongly to conditions that are
    # potentially dangerous, like missing/incorrect Manifest files.
    # 'userfetch' when portage is run as root, drop privileges to
    # portage:portage during the fetching of package sources.
    # 'userpriv' allows portage to drop root privileges while it is compiling,
    # as a security measure. As a side effect this can remove
    # sandbox access violations for users.
    # 'usersandbox' enables sandboxing while portage is running under userpriv.
    #FEATURES="sandbox buildpkg ccache distcc userpriv usersandbox notitles noclean noauto cvs keeptemp keepwork autoaddcvs"
    #FEATURES="sandbox ccache distcc distlocks autoaddcvs"
    #
    # CCACHE_SIZE sets the space use limitations for ccache. The default size is
    # 2G, and will be set if not defined otherwise and ccache is in features.
    # Portage will set the default ccache dir if it is not present in the
    # user's environment, for userpriv it sets: ${PORTAGE_TMPDIR}/ccache
    # (/var/tmp/ccache), and for regular use the default is /root/.ccache.
    # Sizes are specified with 'G' 'M' or 'K'.
    # '2G' for 2 gigabytes, '2048M' for 2048 megabytes (same as 2G).
    #CCACHE_SIZE="512M"
    #
    # DISTCC_DIR sets the temporary space used by distcc.
    #DISTCC_DIR="${PORTAGE_TMPDIR}/.distcc"

    # logging related variables:
    # PORTAGE_ELOG_CLASSES: selects messages to be logged, possible values are:
    # info, warn, error, log
    # Warning: commenting this will disable elog
    PORTAGE_ELOG_CLASSES="warn error log"

    # PORTAGE_ELOG_SYSTEM: selects the module(s) to process the log messages. Modules
    # included in portage are (empty means logging is disabled):
    # save (saves one log per package in $PORT_LOGDIR/elog,
    # /var/log/portage/elog if $PORT_LOGDIR is unset)
    # custom (passes all messages to $PORTAGE_ELOG_COMMAND)
    # syslog (sends all messages to syslog)
    # mail (send all messages to the mailserver defined
    # in $PORTAGE_ELOG_MAILURI)
    # To use elog you should enable at least one module
    #PORTAGE_ELOG_SYSTEM="save mail"

    # PORTAGE_ELOG_COMMAND: only used with the "custom" logging module. Specifies a command
    # to process log messages. Two variables are expanded:
    # ${PACKAGE} - expands to the cpv entry of the processed
    # package (see $PVR in ebuild(5))
    # ${LOGFILE} - absolute path to the logfile
    # Both variables have to be quoted with single quotes
    #PORTAGE_ELOG_COMMAND="/path/to/logprocessor -p '\${PACKAGE}' -f '\${LOGFILE}'"

    # PORTAGE_ELOG_MAILURI: this variable holds all important settings for the mail
    # module. In most cases listing the recipient address and
    # the receiving mailserver should be sufficient, but you can
    # also use advanced settings like authentication or TLS. The
    # full syntax is:
    # address [[user:passwd@]mailserver[:port]]
    # where
    # address: recipient address
    # user: username for smtp auth (defaults to none)
    # passwd: password for smtp auth (defaults to none)
    # mailserver: smtp server that should be used to deliver the mail (defaults to localhost)
    # port: port to use on the given smtp server (defaults to 25, values > 100000 indicate that starttls should be used on (port-100000))
    # Examples:
    #PORTAGE_ELOG_MAILURI="root@localhost localhost" (this is also the default setting)
    #PORTAGE_ELOG_MAILURI="user@some.domain mail.some.domain" (sends mails to user@some.domain using the mailserver mail.some.domain)
    #PORTAGE_ELOG_MAILURI="user@some.domain user:secret@mail.some.domain:100465" (this is left uncommented as a reader excercise ;)

    # PORTAGE_ELOG_MAILFROM: you can set the from-address of logmails with this variable,
    # if unset mails are sent by "portage" (this default may fail
    # in some environments).
    #PORTAGE_ELOG_MAILFROM="portage@some.domain"

    # PORTAGE_ELOG_MAILSUBJECT: template string to be used as subject for logmails. The following
    # variables are exanded:
    # ${PACKAGE} - see description of PORTAGE_ELOG_COMMAND
    # ${HOST} - FQDN of the host portage is running on
    #PORTAGE_ELOG_MAILSUBJECT="package \${PACKAGE} merged on \${HOST} with notice"
    #########################################################
     
  6. #5 GendoIkari, 10.02.2007
    GendoIkari

    GendoIkari Routinier

    Dabei seit:
    04.12.2006
    Beiträge:
    336
    Zustimmungen:
    0
    Ort:
    Dort wo die Sonne aufgeht...
    Was mir aufgefallen ist, ist dass das Problem nur bei 64bit systemen aufgetreten ist. auch bei suse 64bit hatte ich das selbe problem, bei suse 32bit nicht. da ging es automatisch ohne problem. mein einzieger anhaltspunkt wäre noch, das xine den treiber nicht findet, weil der pfat wie in der 32bit version gesucht wird aber der treiber nach 64bit dateisystem gespeichert wurde. (lib,lib32,lib64) wenn ich das nicht balt hin bekomme werde ich warscheinlich die 32bit gentoo installieren....
     
  7. #6 Bloodsurfer, 11.02.2007
    Bloodsurfer

    Bloodsurfer Gentoo-User

    Dabei seit:
    15.10.2005
    Beiträge:
    243
    Zustimmungen:
    0
    Hast du alsa nach der Installation überhaupt gestartet? Mit einem
    /etc/init.d/alsasound start
    bzw. damit es beim Hochfahren startet
    rc-update add alsasound default

    Wenn ja, erscheinen dann irgendwelche Fehlermeldungen?

    Ausserdem hast du in deiner make.conf so einiges nicht festgelegt, zum Beispiel welche alsa-Treiber überhaupt gebaut werden sollen. Das geht zum Beispiel mit
    ALSA_CARDS=hda_intel
    Generell könntest du mal die Kommentare da entfernen, das macht die Sache etwas übersichtlicher ;)

    Und hast du die Treiber im Kernel auch abgeschaltet? Wie gesagt, wenn du die externen nutzen willst musst du sie aus dem Kernel entfernen, beides zusammen wird nicht funktionieren.
     
  8. #7 GendoIkari, 18.02.2007
    Zuletzt bearbeitet: 18.02.2007
    GendoIkari

    GendoIkari Routinier

    Dabei seit:
    04.12.2006
    Beiträge:
    336
    Zustimmungen:
    0
    Ort:
    Dort wo die Sonne aufgeht...
    nach alsasound start kommt das:

    * Loading ALSA modules ...
    * Loading: snd-card-0 ...
    FATAL: Module snd_mpu401 not found. [ !! ] // Wie sag ich dem wo das mod. is?
    * Loading: snd-seq-oss ... [ ok ]
    * Loading: snd-pcm-oss ... [ ok ]
    * ERROR: Failed to load necessary drivers [ ok ] // ?( die hab ich doch emerge
    * Restoring Mixer Levels ... [ ok ]

    ok die " * ERROR: Failed to load necessary drivers" Meldung kommt nur ,wenn ich im kde alsasound restart mache. An sonsten ,also im text modus nach einem neustart, kommt die Meldung net. Aber der Rest ist gleich.
     
  9. #8 liquidnight, 18.02.2007
    liquidnight

    liquidnight Routinier

    Dabei seit:
    16.04.2005
    Beiträge:
    430
    Zustimmungen:
    0
    /usr/src/linux sollte auf die sourcen des laufenden kernels zeigen. dann emergst du alles was *alsa* heißt nochmal. danach noch ein make modules ; make modules_install

    dann schaust du ob das modul vorhanden ist. wenn nicht, musst du in der kernel-konfiguration gucken ob du das modul anschalten kannst.
     
  10. Anzeige

    Vielleicht findest du HIER Antworten.
    Registrieren bzw. einloggen, um diese und auch andere Anzeigen zu deaktivieren
  11. #9 GendoIkari, 24.02.2007
    GendoIkari

    GendoIkari Routinier

    Dabei seit:
    04.12.2006
    Beiträge:
    336
    Zustimmungen:
    0
    Ort:
    Dort wo die Sonne aufgeht...
    Schön jetzt geht noch weniger.

    ######################################################
    /etc/init.d/alsasound start
    * Loading ALSA modules ...
    * Loading: snd-card-0 ... [ ok ]
    * Loading: snd-seq-oss ...
    WARNING: Error inserting snd_seq (/lib/modules/2.6.19-gentoo-r4/alsa-driver/acore/seq/snd-seq.ko): Unknown symbol in module, or unknown parameter (see dmesg)
    WARNING: Error inserting snd_seq_midi_event (/lib/modules/2.6.19-gentoo-r4/alsa-driver/acore/seq/snd-seq-midi-event.ko): Unknown symbol in module, or unknown parameter (see dmesg)
    FATAL: Error inserting snd_seq_oss (/lib/modules/2.6.19-gentoo-r4/alsa-driver/acore/seq/oss/snd-seq-oss.ko): Unknown symbol in module, or unknown parameter (see dmesg) [ !! ]
    * Loading: snd-mixer-oss ... [ ok ]
    * Loading: snd-seq ...
    FATAL: Error inserting snd_seq (/lib/modules/2.6.19-gentoo-r4/alsa-driver/acore/seq/snd-seq.ko): Unknown symbol in module, or unknown parameter (see dmesg) [ !! ]
    * Loading: snd-seq-midi ...
    WARNING: Error inserting snd_seq (/lib/modules/2.6.19-gentoo-r4/alsa-driver/acore/seq/snd-seq.ko): Unknown symbol in module, or unknown parameter (see dmesg)
    WARNING: Error inserting snd_seq_midi_event (/lib/modules/2.6.19-gentoo-r4/alsa-driver/acore/seq/snd-seq-midi-event.ko): Unknown symbol in module, or unknown parameter (see dmesg)
    FATAL: Error inserting snd_seq_midi (/lib/modules/2.6.19-gentoo-r4/alsa-driver/acore/seq/snd-seq-midi.ko): Unknown symbol in module, or unknown parameter (se [ ok ]
    * Restoring Mixer Levels ...
    ##########################################################
     
  12. #10 GendoIkari, 25.02.2007
    GendoIkari

    GendoIkari Routinier

    Dabei seit:
    04.12.2006
    Beiträge:
    336
    Zustimmungen:
    0
    Ort:
    Dort wo die Sonne aufgeht...
Thema:

Nur rauschen....

Die Seite wird geladen...

Nur rauschen.... - Ähnliche Themen

  1. Hintergrundrauschen bei Aufnahmen

    Hintergrundrauschen bei Aufnahmen: Hallo Allerseits! Ich habe wiedermal ein Problem beim aufnehmen von Sound. Es scheint ganz ähnlich zu sein wie damals bei diesem Thread:...
  2. Hintergrundrauschen/Metallischer klang

    Hintergrundrauschen/Metallischer klang: Hallo, Ich habe momentan ein äusserst seltsames Problem. Wenn ich mit meinem Rechner etwas aufnehme (Git/Mic/Radio)->Mischpult->LineIn dann habe...
  3. Summen und Rauschen auf dem Headset

    Summen und Rauschen auf dem Headset: Hi@all Zwar ist diese Frage nicht Linuxspeziell aber da ich weiß dass hier kluge köpfe sitzen wollte ich euch mal was spezielles fragen....
  4. statisches Rauschen aus den Boxen nach einlegen von CD-R

    statisches Rauschen aus den Boxen nach einlegen von CD-R: Neuerdings habe ich das Problem, dass nach dem Einlegen einer beliebigen CD-R (originale machen kein Problem) in mein DVD Laufwerk (Pioneer DVD...
  5. Rauschen unter X, insbesondere bei Mausbewegungen

    Rauschen unter X, insbesondere bei Mausbewegungen: Hi zusammen, mir ist vor kurzem (als ich mit meinem Notebook mit Kopfhörer Musik hören wollte) aufgefallen, dass mein Ton ne Macke hat. Am...