so the question becomes why does eth0
appear under ifconfig on my laptop with net.eth0 stopped and the cable
unplugged?
I thought it could be wicd on my laptop but I shut down the daemon
with no change.
Try disabling the daemon from starting at boot 'rc-update delete wicd'
and reboot,
On Wednesday 03 Aug 2011 17:39:50 Grant wrote:
so the question becomes why does eth0
appear under ifconfig on my laptop with net.eth0 stopped and the cable
unplugged?
I thought it could be wicd on my laptop but I shut down the daemon
with no change.
Try disabling the daemon from
so the question becomes why does eth0
appear under ifconfig on my laptop with net.eth0 stopped and the cable
unplugged?
I thought it could be wicd on my laptop but I shut down the daemon
with no change.
Try disabling the daemon from starting at boot 'rc-update delete wicd'
and
On 2011-08-01 20:35, Grant wrote:
Does anyone know if this is the case? Doesn't seem very Gentoo-like,
although it should minimize package management for the devs which is
good.
I assume they're just following kernel.org; since the kernel devs (at
least the ones that have to deal with
# ls /sys/bus/pci/devices/:04:00.0
broken_parity_status device irq msi_bus reset
resource2_wc subsystem_device vpd
class dma_mask_bits local_cpulist net
resource resource4 subsystem_vendor
config driver
IIRC
'ifconfig -a' will show interfaces that are physically present, and
the driver available.
'ifconfig' will only show those interfaces that are also activated or
up, which means configured up - nothing to do with link.
OK, with net.eth0 stopped and the cable unplugged, eth0 does appear
so the question becomes why does eth0
appear under ifconfig on my laptop with net.eth0 stopped and the cable
unplugged?
I thought it could be wicd on my laptop but I shut down the daemon
with no change.
Try disabling the daemon from starting at boot 'rc-update delete wicd'
and reboot, then
On Sat, Jul 30, 2011 at 7:05 PM, Grant emailgr...@gmail.com wrote:
I remembered that i also had started having a problem with my intel
wireless card, and it looks like both the intel and realtek firmwares
are now in linux-firmware so try emerging that.
That fixed it. Thank you very much.
I'm guessing that radeon-ucode and rt61-firmware and all the others
are being deprecated in favour of linux-firmware, but i don't recall
seeing an elog on it.
Does anyone know if this is the case? Doesn't seem very Gentoo-like,
although it should minimize package management for the devs which
On Mon, Aug 1, 2011 at 2:35 PM, Grant emailgr...@gmail.com wrote:
That's odd. Does that box still have the failed loading firmware
error? Perhaps missing firmware stops eth0 from being created. I'd try
installing linux-fireware and trying again (assuming you havent
already).
I didn't have
...
Setting up some peristent udev rules keyed on a NIC's MAC address will
help keep things orderly for you.
I deleted the persistent-net.rules file and rebooted and everything
came up properly numbered. eth0 was being renamed to eth1 previously
because I had used that hard drive on a
On Mon, Aug 1, 2011 at 3:04 PM, Grant emailgr...@gmail.com wrote:
My laptop's
r8169 eth0 appears under ifconfig even when there's no ethernet cable
attached. That's the expected behavior isn't it?
Sure; ifconfig will even tell you if the link is up or down. Just
because the link is down
My laptop's
r8169 eth0 appears under ifconfig even when there's no ethernet cable
attached. That's the expected behavior isn't it?
Sure; ifconfig will even tell you if the link is up or down. Just
because the link is down doesn't mean the interface isn't there. :)
I see eth0 under
On Mon, Aug 1, 2011 at 4:13 PM, Grant emailgr...@gmail.com wrote:
# ls /sys/bus/pci/devices/:04:00.0
broken_parity_status device irq msi_bus reset
resource2_wc subsystem_device vpd
class dma_mask_bits local_cpulist net
resource
IIRC
'ifconfig -a' will show interfaces that are physically present, and
the driver available.
'ifconfig' will only show those interfaces that are also activated or
up, which means configured up - nothing to do with link.
I'm not sure what RUNNING means... perhaps that indicates link (for
That fixed it. Thank you very much. I'm a little puzzled because I
don't get the unable to apply firmware patch messages on my desktop
which also uses the r8169 driver and doesn't have linux-firmware
installed.
Maybe you have an older firmware installed from a different package?
Run
Maybe you have an older firmware installed from a different package?
Run emerge -p linux-firmware on that box to see if there's a blocker.
linux-firmware is blocked by radeon-ucode and rt61-firmware,
I'm guessing that radeon-ucode and rt61-firmware and all the others
are being deprecated in
I remembered that i also had started having a problem with my intel
wireless card, and it looks like both the intel and realtek firmwares
are now in linux-firmware so try emerging that.
My laptop's Realtek Semiconductor Co., Ltd. RTL8111/8168B PCI Express
Gigabit Ethernet controller uses the r8169 driver. On kernel 2.6.36
it works fine, but on 2.6.38 and 2.6.39 it doesn't work and
continuously outputs eth0: unable to apply firmware patch to dmesg.
I found this workaround:
I remembered that i also had started having a problem with my intel
wireless card, and it looks like both the intel and realtek firmwares
are now in linux-firmware so try emerging that.
That fixed it. Thank you very much. I'm a little puzzled because I
don't get the unable to apply firmware
That fixed it. Thank you very much. I'm a little puzzled because I
don't get the unable to apply firmware patch messages on my desktop
which also uses the r8169 driver and doesn't have linux-firmware
installed.
Maybe you have an older firmware installed from a different package?
Run emerge
21 matches
Mail list logo
