> > lets see if this msg gets out now. > > > > > Well geez, where to start. Not sure where things went wrong or how, but > they > > are pretty screwed up. > > So, first problem I noticed is I lost the nic, yeah, gone no telnet etc., > > but it had been working. > > So, tried modprobe via-rhine and got an error that stated in short that > the > > via-rhine module was a kernel version missmatch. > > So, I tried all kinds of stuff from recompiling the kernel to blowing the > > whole tree away and starting with a new fresh tree with no luck. Now I > even > > tried renaming the module directory and no luck there. > > > > So, next problem is the alsa drivers are not loading either, but they did > > compile fine. > > > > Now the questions I have is this, what could I do about the via-rhine > > module. Doesn't these modules get created when you run make modules and > > modules_install? What would cause the sound card modules to not load when > I > > hadn't changed anything at all. > > > > Lastly I put together a router and was intending to use this with the dsl > > connection, but in the mean time until hellatlantic gets out and corrects > > the loop problem I wanted to still dial out on the current box until I get > > the modem connected to the router and dialup setup as a backup to the dsl > > connection. > > In any case when I dial out now fetchmail complains about a temporary name > > server which I thought I had fixed. > > So, I tried route add default ppp0 and that didn't help either. > > > > Yeah, several problems, but seems that they all happend at once. I haven't > > any clue about the modules being I only compiled the kernel once to just > fix > > one item and changed nothing else. > > > > I doubt all these issues are tied together, but they all happend about the > > same time. I hadn't made any changes other than running netconfig to setup > > the address on my box and I really can't see how that would have broken my > > kernel, but then nor recompiling the kernel should have caused all these > > problems. > > So, anyone got any ideas as to where I should start looking with respect > to > > either issue, please let me know. I can't get speakfreely to run either so > > this all ties into the networking problem. > > Of course will fix one problem at a time, but like to get enough info to > > have on hand in order to attack both problems. > > > > tnx > > > > > > > >
