Jump to content

penfield

Members
  • Posts

    20
  • Joined

  • Last visited

penfield's Achievements

New Here

New Here (1/7)

0

Reputation

  1. It's working :D Well to sum up... I googled for that strange message "SIOCSIFFLAGS: function not implemented" and VIA Rhine II kept popping up (thats what I have), so I read a little, and came across this forum: http://www.linuxquestions.org/questions/sh...=&postid=955852 near the bottom someone suggested to check the "force no acpi". I did just that, rebooted... And it worked, with DHCP enabled. Well anyways, thank you so much ianw1974, you have been a great ally on my conquest into the linux world :)
  2. Ok I changed it back to dhcp and did a "dhclient eth0" and the response was: sit0: unknown hardware at address type 776 SIOCSIFFLAGS: function not implemented SIOCSIFFLAGS: function not implemented sit0: unknown hardware at address type 776 Listening on LPF/eth0/00:0a:e6:95:09:d0 Sending on LPF/eth0/00:0a:e6:95:09:d0 Sending on Socket/fallback DHCPDISCOVER on eth0 to 255.255.255.255 port 67 interval 3 send_packet: Network is down the last 2 lines repeat 6 times, and finally it says: No DHCPOFFERS received. No working leases in persistant database - sleeping. ifconfig -a is the same as in the beginning, no address.
  3. I tried to change it back to dhcp, no hassle there, but when I look in /etc/sysconfig/network-scripts/ifcfg-eth0 it shows DEVICE=eth0 BOOTPROTO=DHCP IPADDR=192.168.1.10 NETMASK=255.255.255.0 NETWORK=192.168.1.0 BROADCAST=192.168.1.255 ONBOOT=yes METRIC=10 MII_NOT_SUPPORTED=NO USERCTL=no DHCP_CLIENT=dhclient PEERDNS=yes PEERPYP=no PEERNTPD=no I even did it after a reboot...
  4. When I wrote that post before I was still on static IP (with no connection, I could only ping myself). Right now I am trying out the things you suggested. Just a minute.....
  5. I have a little update. I rebooted the machine, then I tried to ping 192.168.1.10 and it answered. Then I did a config -a and now it says under eth0: inet addr:192.168.1.10 Bcast:192.168.1.255 Mask:255.255.255.0 Which I think is kind of weird, since I have changed nothing.
  6. Ok, when I did "ifconfig eth0 192.168.1.10 up" (that is the IP I chose) it says: SIOCSIFFLAGS: Function not implemented SIOCSIFFLAGS: Function not implemented and "dmesg | grep -i eth0" returns: eth0: VIA Rhine II at 0x1c000, 00:0a:e6:95:09:d0, IRQ 16. eth0: MII PHY found at address 1, status 0x786d advertising 01e1 Link 45e1.
  7. Oh I just figured, I think it enters a new entry into boot.log every time I change the network configuration. Perhaps?
  8. Well I'm kind of new to linux, remeber ;) so I don't know if I'm looking at the right things in /var/log/boot.log but I think this is kind of strange, it says: Shutting down loopback interface: succeeded Setting network parameters: succeeded Bringing up loopback interface: succeeded Bringing up interface eth0: succeeded this repeats 4 times and then right after Bringing up loopback interface: succeeded it says: Sorry, there is already an instance of ifplugd for eth0 running. Bringing up interface eth0: failed now this repeats 2 times and then it finally ends with: Bringing up interface eth0: succeeded Was this informative?
  9. Alright. I really appreciate your help. Thanks :)
  10. It does remember the settings as I entered them last. Both "Network hotplugging" and "Start at boot" is checked on, "Track network card id" is not.
  11. Under Services the network show "running".
  12. The name of the Module is "via-rhine" and it is in the lsmod list, although under 'used by' it just says "0".
  13. The network itself is working smooth. On the computer where I have installed Mandriva, I have just loaded up knoppix from a live CD, and it works just great, internet and everything. When I load the computer up on knoppix the dhcp server assigns it IP 192.168.1.10 so no problem on the actual network (cables and such). The ethernet card is an onboard VT6102 VIA Rhine (which is what was detected and installed during installation).
×
×
  • Create New...