Driver sd needs updating eth Lina mark reallifecam com

6854933580_2c8b688306_z

b44: eth1: link is up at 100 mpbs, full duplex b44: eth1: flow control is off for tx and off for rx b44: eth1: powering down phy b44: eth1: link is up at 100 mpbs, full duplex b44: eth1: flow control is off for tx and off for rxmy harddrive is partitioned so var, tmp, home, boot, / and usr is separated. infront of gateway my looks like this:eth0="dhcp"INTERFACES=(eth0)gateway="default gw 192.168.1.1"routes=(gateway)when i run /etc/rc.d/network restart i get::: stopping network SIOCDELRT: no such process [FAIL]:: starting network SIOCADDRT: no such process [FAIL]notice that the interface is no longer eth1 but eth0, because i also rebooted, and the NIC's are randomly called either eth0 or eth1...... If what you have here is accurate the problem is that the IP of the gateway does not match the real IP in your network. it's brand new and i just took it for granted that ping worked on every router but everything else works.don't know if it's because root doesn't have access or something, but here's a copy of my fstab:/etc/fstab:none /dev/pts devpts defaults 0 0 none /dev/shm tmpfs rw,noexec,nosuid,nodev 0 0 /dev/sda10 /home ext4 rw,suid,exec,auto,nouser,async 0 2 /dev/sda2 /boot ext4 defaults 1 2 /dev/sda7 / ext4 defaults 0 1 /dev/sda5 swap swap defaults 0 0 /dev/sda6 /var ext4 defaults 0 1 /dev/sda8 /tmp ext4 loop,rw,noexec,nosuid,nodev 0 0 /dev/sda9 /usr ext4 defaults 0 1to sum it up: i have access to my lan, but can't get outside. tried dhcpcd eth1 and /etc/rc.d/network restart a few times also.. Doesn't your DHCP server provide you with a default route? never tried that all the other stuff worked when ping doesn't. really don't understand what's going on here. You have now gateway="default gw 192.168.1.1" but it should be gateway="default gw 192.168.0.1"R. i'm too much a geek to think it could be such a simple solution.

from "gateway" in ROUTES, after making sure the gateway entry actually matches your real gateway. infront of gateway my looks like this:eth0="dhcp"INTERFACES=(eth0)gateway="default gw 192.168.1.1"routes=(gateway)when i run /etc/rc.d/network restart i get::: stopping network SIOCDELRT: no such process [FAIL]:: starting network SIOCADDRT: no such process [FAIL]notice that the interface is no longer eth1 but eth0, because i also rebooted, and the NIC's are randomly called either eth0 or eth1...... i just noticed that when i ping a site i also get its ip. I tried bringing it down and back up again but nothing.I tried to solve the problem by using either dhcp or static options but it didn't work.Hereafter some further information: sudo lshw -C network *-network description: Ethernet interface product: 3c940 10/100/1000Base-T [Marvell] vendor: 3Com Corporation physical id: 5 bus info: [email protected] logical name: eth1 version: 12 serial: 00:0c:6e:40:4c:04 size: 10MB/s capacity: 1GB/s width: 32 bits clock: 66MHz capabilities: pm vpd bus_master cap_list ethernet physical tp 10bt 10bt-fd 100bt 100bt-fd 1000bt-fd autonegotiation configuration: autonegotiation=on broadcast=yes driver=skge driverversion=1.13 duplex=half firmware=N/A latency=64 link=yes maxlatency=31 mingnt=23 module=skge multicast=yes port=twisted pair speed=10MB/s *-network DISABLED description: Ethernet interface physical id: 1 logical name: pan0 serial: 3a:e1:6c:84:2d:e2 capabilities: ethernet physical configuration: broadcast=yes driver=bridge driverversion=2.3 firmware=N/A link=yes multicast=yes ifconfig eth1 Link encap: Ethernet HWaddr 00:0c:6e:40:4c:04 inet6 addr: fe80::20c:6eff:fe40:4c04/64 Scope: Link UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 RX packets:7 errors:0 dropped:0 overruns:0 frame:0 TX packets:23 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:1000 RX bytes:458 (458.0 B) TX bytes:3848 (3.8 KB) Interrupt:22lo Link encap: Local Loopback inet addr:127.0.0.1 Mask:255.0.0.0 inet6 addr: ::1/128 Scope: Host UP LOOPBACK RUNNING MTU:16436 Metric:1 RX packets:848 errors:0 dropped:0 overruns:0 frame:0 TX packets:848 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:0 RX bytes:67488 (67.4 KB) TX bytes:67488 (67.4 KB) dmesg | grep eth [ 1.739081] Driver 'sd' needs updating - please use bus_type methods [ 1.739098] Driver 'sr' needs updating - please use bus_type methods [ 3.818844] skge eth0: addr 00:0c:6e:40:4c:04 [ 9.771834] udev: renamed network interface eth0 to eth1 [ 32.913429] skge eth1: enabling interface [ 32.917093] ADDRCONF(NETDEV_UP): eth1: link is not ready [ 35.180253] skge eth1: Link is up at 10 Mbps, half duplex, flow control none [ 35.180454] ADDRCONF(NETDEV_CHANGE): eth1: link becomes ready [ 45.480009] eth1: no IPv6 routers present cat /etc/network/interfaces auto lo iface lo inet loopback auto dsl-provider iface dsl-provider inet ppp pre-up /sbin/ifconfig eth1 up # line maintained by pppoeconf provider dsl-provider auto eth1 iface eth1 inet manual cat /etc/Network Manager/[main] plugins=ifupdown,keyfile [ifupdown] managed=true Thanks I'm still a couple of versions behind, so dunno if Jaunty is using /etc/network/interfaces file differently.The manual Method This method may be used to define interfaces for which no configuration is done by default.When i did lspci -vv it doesn't said anything about Kernel driver in use for my ethernet controller. I want to know the Vendor and Device IDs of your network card so I can grep the kernel for them_________________Regards, Neddy Seagoon Computer users fall into two groups:- those that do backups those that have never had a hard drive fail./etc/init.d/net.eth0 exists. I compiled it into the kernel, not as a module, so that can't be the fault. By the way I found this, which answers you dmesg..a workaround to get rid of those warning msg, but i understood they are harmless ..i were you i wouldnt bother with warnings..im a terrible person who dont care bout warnings https://bugs.gentoo.org/213431_________________~x86 p5k-se Intel Core 2 Duo Nvidia GT200 Host bridge: Intel Corporation Mobile PM965/GM965/GL960 Memory Controller Hub (rev 03) .0 VGA compatible controller: Intel Corporation Mobile GM965/GL960 Integrated Graphics Controller (rev 03) .1 Display controller: Intel Corporation Mobile GM965/GL960 Integrated Graphics Controller (rev 03) 00:1a.0 USB Controller: Intel Corporation 82801H (ICH8 Family) USB UHCI Controller #4 (rev 04) 00:1a.1 USB Controller: Intel Corporation 82801H (ICH8 Family) USB UHCI Controller #5 (rev 04) 00:1a.7 USB Controller: Intel Corporation 82801H (ICH8 Family) USB2 EHCI Controller #2 (rev 04) 00:1b.0 Audio device: Intel Corporation 82801H (ICH8 Family) HD Audio Controller (rev 04) 00:1c.0 PCI bridge: Intel Corporation 82801H (ICH8 Family) PCI Express Port 1 (rev 04) 00:1c.1 PCI bridge: Intel Corporation 82801H (ICH8 Family) PCI Express Port 2 (rev 04) 00:1c.2 PCI bridge: Intel Corporation 82801H (ICH8 Family) PCI Express Port 3 (rev 04) 00:1d.0 USB Controller: Intel Corporation 82801H (ICH8 Family) USB UHCI Controller #1 (rev 04) 00:1d.1 USB Controller: Intel Corporation 82801H (ICH8 Family) USB UHCI Controller #2 (rev 04) 00:1d.2 USB Controller: Intel Corporation 82801H (ICH8 Family) USB UHCI Controller #3 (rev 04) 00:1d.7 USB Controller: Intel Corporation 82801H (ICH8 Family) USB2 EHCI Controller #1 (rev 04) 00:1e.0 PCI bridge: Intel Corporation 82801 Mobile PCI Bridge (rev f4) 00:1f.0 ISA bridge: Intel Corporation 82801HEM (ICH8M) LPC Interface Controller (rev 04) 00:1f.1 IDE interface: Intel Corporation 82801HBM/HEM (ICH8M/ICH8M-E) IDE Controller (rev 04) 00:1f.2 IDE interface: Intel Corporation 82801HBM/HEM (ICH8M/ICH8M-E) SATA IDE Controller (rev 04) 00:1f.3 SMBus: Intel Corporation 82801H (ICH8 Family) SMBus Controller (rev 04) .0 Ethernet controller: Broadcom Corporation Net Link BCM5787M Gigabit Ethernet PCI Express (rev 02) .0 Network controller: Broadcom Corporation BCM4312 802.11b/g (rev 01) 0f:06.0 Card Bus bridge: Texas Instruments PCIxx12 Cardbus Controller 0f:06.1 Fire Wire (IEEE 1394): Texas Instruments PCIxx12 OHCI Compliant IEEE 1394 Host Controller 0f:06.2 Mass storage controller: Texas Instruments 5-in-1 Multimedia Card Reader (SD/MMC/MS/MS PRO/x D) 0f:06.3 SD Host controller: Texas Instruments PCIxx12 SDA Standard Compliant SD Host Controller .0 0600: 8086:2a00 (rev 03) .0 0300: 8086:2a02 (rev 03) .1 0380: 8086:2a03 (rev 03) 00:1a.0 0c03: 8034 (rev 04) 00:1a.1 0c03: 8035 (rev 04) 00:1a.7 0c03: 803a (rev 04) 00:1b.0 0403: 804b (rev 04) 00:1c.0 0604: 803f (rev 04) 00:1c.1 0604: 8041 (rev 04) 00:1c.2 0604: 8043 (rev 04) 00:1d.0 0c03: 8030 (rev 04) 00:1d.1 0c03: 8031 (rev 04) 00:1d.2 0c03: 8032 (rev 04) 00:1d.7 0c03: 8036 (rev 04) 00:1e.0 0604: 8048 (rev f4) 00:1f.0 0601: 8015 (rev 04) 00:1f.1 0101: 8050 (rev 04) 00:1f.2 0101: 8028 (rev 04) 00:1f.3 0c05: 803e (rev 04) .0 0200: 14e93 (rev 02) .0 0280: 14e15 (rev 01) 0f:06.0 0607: 104c:8039 0f:06.1 0c00: 104c:803a 0f:06.2 0180: 104c:803b 0f:06.3 0805: 104c:803c returns ./include/linux/pci_ids.h:#define PCI_DEVICE_ID_TIGON3_5787M 0x1693 among other things. That tells that 2.6.29-r1 knows your network card as belonging to tg3. If you cannot produce that result on your kernel, you need a later kernel.

You must have an account to comment. Please register or login here!