Re: Unresolved symbols potato and kernel 2.0.36

2000-03-23 Thread markm
On Tue, Mar 21, 2000 at 12:34:53PM -0500, Jonathan Markevich wrote: > > Not sure if you know this but you can't compile 2.0.x modules with > > 2.2.x kernel. Just get the 2.2.x version of *everything* and you > > should be right. > > It's more specifically gcc you need. I used gcc272 and all was >

Re: Unresolved symbols potato and kernel 2.0.36

2000-03-22 Thread Jonathan Markevich
On Mon, Mar 20, 2000 at 04:29:21PM +, David Wright wrote: Out of everyone that got and read my message, you're the *only* one that took offense. Well, that responded anyways. It seems most realized what I said was extreme frustration and not a personal attack. Please accept my messages in t

Re: Unresolved symbols potato and kernel 2.0.36

2000-03-21 Thread Jonathan Markevich
On Mon, Mar 20, 2000 at 02:12:33PM +0100, Antonio Fiol Bonnín wrote: > I don't know nearly anything about this, but... did you activate module > support in your kernel? It sounds like there has to be such a silly little > thing that breaks it all. No kidding, that's what I'm hoping for. And yes,

Re: Unresolved symbols potato and kernel 2.0.36

2000-03-21 Thread markm
On Sun, Mar 19, 2000 at 09:25:58AM -0500, Jonathan Markevich wrote: > Well I have to use 2.0.36. 2.2 doesn't work for me, remember? And I use > stock kernels because it avoids another level of confusion and Huh? you should have no trouble with 2.2. Not sure if you know this but you can't compil

Re: Unresolved symbols potato and kernel 2.0.36

2000-03-21 Thread Nathan E Norman
> So I have tried to replace it... reinstalling, trying other kernel versions > (including this new-fangled kernel 2.2.x thing which is apparently the > greatest thing since sliced bread, but won't run on a computer with THREE > SERIAL PORTS!!! Ever heard of a machine so unusual? I mean a shared

Re: Unresolved symbols potato and kernel 2.0.36

2000-03-20 Thread Antonio Fiol Bonnín
I don't know nearly anything about this, but... did you activate module support in your kernel? It sounds like there has to be such a silly little thing that breaks it all. If you compile the kernel properly (at least it happened ok to me when I had 2.0.36), i.e. (make dep; make clean; make zImage

Re: Unresolved symbols potato and kernel 2.0.36

2000-03-20 Thread Jonathan Markevich
> Don't upgrade unless you have to. I always have to remind myself of that > - if my machine is working and I can do the tasks I need to do, even > though there is a new fangled a super-cool version of my software, I don't > have to install it. I still need to remind myself. It's not just super-

Re: Unresolved symbols potato and kernel 2.0.36

2000-03-19 Thread Percival
Don't upgrade unless you have to. I always have to remind myself of that - if my machine is working and I can do the tasks I need to do, even though there is a new fangled a super-cool version of my software, I don't have to install it. I still need to remind myself. That said, I just instal

Unresolved symbols potato and kernel 2.0.36

2000-03-19 Thread Jonathan Markevich
I suppose it's the height of naivite to expect an answer about Debian around here, but here goes... Once again... I upgraded to Potato. Yes, stupid, but I'm really really tired of waiting. The upgrade thought it a great idea to remove my working alsa-modules package and replace it with... NOT