Announcement

Collapse
No announcement yet.

Need guidance on solving 'no network connectivity' problem

Collapse
This topic is closed.
X
X
 
  • Filter
  • Time
  • Show
Clear All
new posts

    #31
    Re: Need guidance on solving 'no network connectivity' problem

    Originally posted by XEyedBear

    my suspicions are that a Kubuntu update has fatally wounded my system
    You could test that theory by booting your Live CD (if you still have it).

    I remember building a system on an Asus motherboard a couple years ago, and it might have been that Marvel Gigabit NIC. I remember *buntu would not automatically load a kernel module for it, and it turned out I would have had to compile a driver to use it. Here's what Google shows today:

    http://fixunix.com/ubuntu/375470-mar...n-drivers.html

    http://manpages.ubuntu.com/manpages/....4freebsd.html

    Comment


      #32
      Re: Need guidance on solving 'no network connectivity' problem

      If you really believe that the problem lies with Kubuntu not properly recognizing your networking device (I'm not convinced this is the problem) , you could very easily install an inexpensive networking card that is known to be supported.

      Comment


        #33
        Re: Need guidance on solving 'no network connectivity' problem

        Originally posted by Detonate
        If you really believe that the problem lies with Kubuntu not properly recognizing your networking device (I'm not convinced this is the problem) , you could very easily install an inexpensive networking card that is known to be supported.
        How would this explain that the system ran OK from the first availability of Kubuntu 10.4 (and with 9.x before it) until about 6 weeks ago - during which time I think there were 3 kernel updates and many other component updates? That is, I think it ran OK for about 9 months with Kubuntu 64.

        To be precise, I meant to say (if I didn't) that I think it is a Kubuntu update of some sort that has disabled my system; I do not think that Kubuntu 'is not properly recognising [my} networking device'. Furthermore I beleive - at this time and lacking any evidence to support my belief - that the problem is not in some defective piece of code somwhere, but a process error in installing an update. It 'feels' like there is something missing - as if a .dll (in a Windows analogy) has been deleted in error.

        I know there are no facts to support this, but I wonder if it gives any clue as to how to get the system working again?

        Comment


          #34
          Re: Need guidance on solving 'no network connectivity' problem

          Originally posted by dibl
          Originally posted by XEyedBear

          my suspicions are that a Kubuntu update has fatally wounded my system
          You could test that theory by booting your Live CD (if you still have it).

          I remember building a system on an Asus motherboard a couple years ago, and it might have been that Marvel Gigabit NIC. I remember *buntu would not automatically load a kernel module for it, and it turned out I would have had to compile a driver to use it. Here's what Google shows today:

          http://fixunix.com/ubuntu/375470-mar...n-drivers.html

          http://manpages.ubuntu.com/manpages/....4freebsd.html

          OK, thanks for the guidance. Sadly I never did have a live CD for Kubuntu. I think that means a re-install - which I won't do beacuse of all the other faffing around associated with that.

          The referenced discussion you pointed me to was interesting - especially because of the obvious personality clash that it illustrated. I would like to comment on that - but here is not the place. What the discussion did for me was to create the impression that my Marvell Yukon capability IS supported by Kubuntu, and supported well (and for at least 9 months that was my experience). What is maybe not supported so well is the discrete NIC manufactured by Marvell. I do not have that - I have an integrated networking capability, designed by Asus, incorporating Marvelll technology.

          The question of re-compiling anything in Linux is O U T!.

          In spite of my proven and demonstrable inability to solve this problem, my experience of computing in general began in 1958. In the 60's and 70's I built a reasonable amount of code. In the 80's I had responsibility for end-user support for a supplier. Our logs showed that printing was the most difficult job in all IT; it always has been; it always will be.

          A VERY close second is successfully completing a compile in Linux. Relying on my experience of 40 years ago, I started (in about 2004, with Fedora) to attempt to compile the kernel to support my sound card. In 6 years of tryiing I never successfully completed a single compile without some sort of problem. Exactly the same picture as trying to get an error-free print.

          I could write a very boring and bitchy paper about the reasons for compilation being so fragile and error prone. But nobody would be interested. The very act of compiling is what separates the men from the mice in the Linux worl, isn't it? That's a game that I find terminally lacking in satisfaction.

          Comment

          Working...
          X