Olá Piter,

Moro em Portugal e trabalho na TAP com um amigo seu o Marcio Marcenari. Ele
sempre fala de você.

Bem, vamos ao meu problema.

Abaixo o resultado do ifconfig eth0 up depois do modprobe.

root@xxx# ifconfig eth0 up
SIOCSIFFLAGS: Resource temporarily unavailable

Resultado do dmesg

[    8.847390] usb usb4: New USB device found, idVendor=1d6b, idProduct=0001
[    8.847476] usb usb4: New USB device strings: Mfr=3, Product=2,
SerialNumber=1
[    8.847601] usb usb4: Product: UHCI Host Controller
[    8.847682] usb usb4: Manufacturer: Linux 3.10.17-smp uhci_hcd
[    8.847764] usb usb4: SerialNumber: 0000:00:1d.2
[    8.849302] hub 4-0:1.0: USB hub found
[    8.849387] hub 4-0:1.0: 2 ports detected
[    8.909520] input: PS/2 Mouse as /devices/platform/i8042/serio1/input/input7
[    8.928816] input: AlpsPS/2 ALPS GlidePoint as
/devices/platform/i8042/serio1/input/input8
[    8.944685] [drm] Initialized drm 1.1.0 20060810
[    9.174117] ACPI: PCI Interrupt Link [LNKF] enabled at IRQ 5
[    9.174207] PCI: setting IRQ 5 as level-triggered
[    9.197049] tifm_core: MMC/SD card detected in socket 0:0
[    9.301972] ACPI: PCI Interrupt Link [LNKG] enabled at IRQ 9
[    9.336702] cfg80211: Calling CRDA to update world regulatory domain
[    9.355070] firewire_ohci 0000:02:04.2: added OHCI v1.10 device as
card 0, 4 IR + 8 IT contexts, quirks 0x2
[    9.488068] usb 4-1: new full-speed USB device number 2 using uhci_hcd
[    9.581501] yenta_cardbus 0000:02:04.0: CardBus bridge found [104d:818f]
[    9.581607] yenta_cardbus 0000:02:04.0: Enabling burst memory read
transactions
[    9.581732] yenta_cardbus 0000:02:04.0: Using CSCINT to route CSC
interrupts to PCI
[    9.581855] yenta_cardbus 0000:02:04.0: Routing CardBus interrupts to PCI
[    9.581941] yenta_cardbus 0000:02:04.0: TI: mfunc 0x01001b22, devctl 0x64
[    9.589581] lib80211: common routines for IEEE802.11 drivers
[    9.589665] lib80211_crypt: registered algorithm 'NULL'
[    9.677264] usb 4-1: New USB device found, idVendor=044e, idProduct=3007
[    9.677355] usb 4-1: New USB device strings: Mfr=1, Product=2, SerialNumber=0
[    9.677441] usb 4-1: Product: UGX
[    9.677519] usb 4-1: Manufacturer: ALPS
[    9.723277] [drm] Memory usable by graphics device = 128M
[    9.723380] i915 0000:00:02.0: setting latency timer to 64
[    9.725244] [drm] Supports vblank timestamp caching Rev 1 (10.10.2010).
[    9.725335] [drm] Driver supports precise vblank timestamp query.
[    9.725521] vgaarb: device changed decodes:
PCI:0000:00:02.0,olddecodes=io+mem,decodes=io+mem:owns=io+mem
[    9.778030] [drm] GMBUS [i915 gmbus panel] timed out, falling back
to bit banging on pin 3
[    9.790168] [drm] initialized overlay support
[    9.806589] yenta_cardbus 0000:02:04.0: ISA IRQ mask 0x0c98, PCI irq 9
[    9.806675] yenta_cardbus 0000:02:04.0: Socket status: 30000006
[    9.806759] pci_bus 0000:02: Raising subordinate bus# of parent bus
(#02) from #02 to #06
[    9.806891] yenta_cardbus 0000:02:04.0: pcmcia: parent PCI bridge
window: [io  0x3000-0x3fff]
[    9.807035] pcmcia_socket pcmcia_socket0: cs: IO port probe 0x3000-0x3fff:
[    9.808406]  excluding 0x3000-0x303f 0x3400-0x34ff 0x3800-0x38ff
[    9.813080] yenta_cardbus 0000:02:04.0: pcmcia: parent PCI bridge
window: [mem 0xe0200000-0xe02fffff]
[    9.813207] pcmcia_socket pcmcia_socket0: cs: memory probe
0xe0200000-0xe02fffff:
[    9.813331]  excluding 0xe0200000-0xe020ffff
[    9.813484] yenta_cardbus 0000:02:04.0: pcmcia: parent PCI bridge
window: [mem 0x20000000-0x23ffffff pref]
[    9.813612] pcmcia_socket pcmcia_socket0: cs: memory probe
0x20000000-0x23ffffff:
[    9.813751]  excluding 0x20000000-0x23ffffff
[    9.856240] firewire_core 0000:02:04.2: created device fw0: GUID
0800460301d6858b, S400
[    9.858032] libipw: 802.11 data/management/control stack, git-1.1.13
[    9.858117] libipw: Copyright (C) 2004-2005 Intel Corporation
<[email protected]>
[    9.884893] fbcon: inteldrmfb (fb0) is primary device
[   10.249070] pcmcia_socket pcmcia_socket0: cs: IO port probe 0xc00-0xcff:
[   10.249720]  excluding 0xcf8-0xcff
[   10.249787] pcmcia_socket pcmcia_socket0: cs: IO port probe 0x3e0-0x4ff:
[   10.250523]  excluding 0x3f0-0x3f7 0x4d0-0x4d7
[   10.250590] pcmcia_socket pcmcia_socket0: cs: IO port probe 0x100-0x3af:
[   10.252309]  excluding 0x170-0x177 0x1f0-0x1f7 0x320-0x327
0x350-0x357 0x370-0x377
[   10.252377] pcmcia_socket pcmcia_socket0: cs: memory probe 0x0c0000-0x0fffff:
[   10.252400]  excluding 0xc0000-0xc7fff 0xd8000-0xfffff
[   10.252460] pcmcia_socket pcmcia_socket0: cs: memory probe
0x60000000-0x60ffffff:
[   10.252485]  clean.
[   10.252544] pcmcia_socket pcmcia_socket0: cs: memory probe
0xa0000000-0xa0ffffff:
[   10.252569]  clean.
[   10.252635] pcmcia_socket pcmcia_socket0: cs: IO port probe 0xa00-0xaff:
[   10.253315]  clean.
[   10.360696] Console: switching to colour frame buffer device 160x48
[   10.370711] i915 0000:00:02.0: fb0: inteldrmfb frame buffer device
[   10.370804] i915 0000:00:02.0: registered panic notifier
[   10.370984] [drm] Initialized i915 1.6.0 20080730 for 0000:00:02.0 on minor 0
[   10.400952] ipw2200: Intel(R) PRO/Wireless 2200/2915 Network
Driver, 1.2.2kmprq
[   10.401106] ipw2200: Copyright(c) 2003-2006 Intel Corporation
[   10.401558] ipw2200: Detected Intel PRO/Wireless 2200BG Network Connection
[   10.425240] Bluetooth: Core ver 2.16
[   10.425379] NET: Registered protocol family 31
[   10.429133] Bluetooth: HCI device and connection manager initialized
[   10.433209] Bluetooth: HCI socket layer initialized
[   10.436955] Bluetooth: L2CAP socket layer initialized
[   10.440860] Bluetooth: SCO socket layer initialized
[   10.499170] usbcore: registered new interface driver btusb
[   10.517980] i2c /dev entries driver
[   10.766777] ipw2200: Detected geography ZZM (11 802.11bg channels,
0 802.11a channels)
[   11.040841] cfg80211: World regulatory domain updated:
[   11.044489] cfg80211:   (start_freq - end_freq @ bandwidth),
(max_antenna_gain, max_eirp)
[   11.048141] cfg80211:   (2402000 KHz - 2472000 KHz @ 40000 KHz),
(300 mBi, 2000 mBm)
[   11.051771] cfg80211:   (2457000 KHz - 2482000 KHz @ 20000 KHz),
(300 mBi, 2000 mBm)
[   11.055358] cfg80211:   (2474000 KHz - 2494000 KHz @ 20000 KHz),
(300 mBi, 2000 mBm)
[   11.058868] cfg80211:   (5170000 KHz - 5250000 KHz @ 40000 KHz),
(300 mBi, 2000 mBm)
[   11.062342] cfg80211:   (5735000 KHz - 5835000 KHz @ 40000 KHz),
(300 mBi, 2000 mBm)
[   11.765651] Adding 1048572k swap on /dev/sda1.  Priority:-1
extents:1 across:1048572k
[   11.986779] fuse init (API version 7.22)
[   13.391054] EXT4-fs (sda3): re-mounted. Opts: (null)
[   14.254521] ppdev: user-space parallel port driver
[   14.263967] lp: driver loaded but no devices found
[   14.341806] cpufreq-nforce2: No nForce2 chipset.
[   17.659477] EXT4-fs (sda2): mounted filesystem with ordered data
mode. Opts: (null)
[   28.836390] lib80211_crypt: registered algorithm 'TKIP'
[   42.210324] NET: Registered protocol family 10
[  279.001936] e100: Intel(R) PRO/100 Network Driver, 3.5.24-k2-NAPI
[  279.001949] e100: Copyright(c) 1999-2006 Intel Corporation
[  279.036336] e100 0000:02:08.0 eth0: addr 0xe0205000, irq 9, MAC
addr 00:01:4a:24:32:a0


2014-12-13 19:11 GMT+00:00 Piter PUNK <[email protected]>:
>
> Carlos São Paulo wrote:
>
>> Vagner,
>>
>> com o e100 no blacklist o NIC eth0 não aparece mais quando faço ifconfig
>> -a
>>
>> Como faço para experimentar os outros drivers e1000 e e1000e?
>>
>
> Antes de fazer isso tenta:
>
> modprobe -r e100
> modprobe e100
> sleep 10
> ifconfig eth0 up
>
> Depois
>
> dmesg | tail -100
>
> E cola essas 100 linhas aqui.
>
> Piter Punk
>
> --
> GUS-BR - Grupo de Usuários de Slackware Brasil
> http://www.slackwarebrasil.org/
> http://groups.google.com/group/slack-users-br
>
> Antes de perguntar:
> http://www.vivaolinux.com.br/artigo/Como-elaborar-
> perguntas-para-listas-de-discussao
>
> Para sair da lista envie um e-mail para:
> [email protected]
> --- Você está recebendo esta mensagem porque se inscreveu no grupo
> "Slackware Users Group - Brazil" dos Grupos do Google.
> Para cancelar inscrição nesse grupo e parar de receber e-mails dele, envie
> um e-mail para [email protected].
> Para obter mais opções, acesse https://groups.google.com/d/optout.
>

-- 
GUS-BR - Grupo de Usuários de Slackware Brasil
http://www.slackwarebrasil.org/
http://groups.google.com/group/slack-users-br

Antes de perguntar:
http://www.vivaolinux.com.br/artigo/Como-elaborar-perguntas-para-listas-de-discussao

Para sair da lista envie um e-mail para:
[email protected]
--- 
Você está recebendo esta mensagem porque se inscreveu no grupo "Slackware Users 
Group - Brazil" dos Grupos do Google.
Para cancelar inscrição nesse grupo e parar de receber e-mails dele, envie um 
e-mail para [email protected].
Para obter mais opções, acesse https://groups.google.com/d/optout.

Responder a