My Dear Steven - what you tell me here is sheer nonsense: > They were unable to get to terms with it because you did not > provide the (full) information they needed to diagnoze it.
The question was, as I again did put it here: "What is there to do if the modem is moved from com2, irq 3 to com4, irq 7", and the best anser in that long list thread over there was, "use 'setserial /dev/ttyS3 irq 7'" - and this does not work. Provenly. Period. And the diatribe you run here is _precisely_ of the kind that puts off for good anyone who isn't a Linux-idolatric by birth; a la: 'what stupid question, don't you KNOW that you have to check [43 or more, and these other 13 config] files before you dare to ask such a dumb question ?!' On top of it, to indignatetedly ask about "what type of UART" is so completely off the issue that I's rather prefer some Douglas Adam quip. I did put that question over there at the other list because it was a question from a "newbie" (whom I wanted to move over to Linux) put to me; and I had made the exact same experience before, and had found the only solution, namely to re-install the whole "system" (or more precisely, the distro's kernel) anew: because it's a design fault which makes that it is difficult to alter the IRQ setting associated with commports _after_ the kernel is installed. (Go to the endless threads about this in various kernel groups which resulted in no change yet of that condition either.) You are utterly wrong if you pose as an answer to the question put, that "PPP doesn't care about IRQs." Which would be about as relevant for my taste of beer as would be the colour of my greatgrandmother's mustache. (Sure "PPP" - I suppose you meant "pppd" - doesn't care and need not to, because the kernel _does_ work only with those precise IRQs assigned to the various commport addresses; and it _does_ need the _correct_ IRQ to drive the modem.) And, aha, you haven't _got_ the "man" for "setserial ? So go and look it up there <g> and what is says about the "-G" argument. BTW, that was a long thread in that newbie-list too, and I _did_ give all information I could find on/in my "system" (or rather, that of the "newbie"). You quote from that thread in a dishonest way. Now, I do not take this fact for calling _you_ dishonest; I take it as an indicator of "system-blindness", an inability to look beyond a rigid set of terminologies and a given grid these are fixed in. The problem is - and I find so much of this in the Linux literature and even "man" writings - that this doesn't help anyone who doesn't know all of it beforehand (and for the exquisite few, it's at best a feelgood exercise.) </BTW> Anway, my demand for an explanation why Kppp _could_ work around the problem while Setserial would _not_ solve it was never answered in that thread on that other list. So please, Steven, don't walk us here again into the same dead-end street. And, BTW2, it's just irrelevant if the script [sic] to launch pppd is "ifup", "pon", or "p-on"; just nothing in there, or called from there, has anything to do with the crucial - and wrong - IRQ setting the kernel uses. It's the latter which has to be changed _after_ a hardware change [i.e., the physical placing of the modem on a different commport with a specified, different IRQ. Been there, done this.] So back to square one and my question: WHY can Kppp do what Setserial cannot achieve what it's supposed to do for the whole "system" ? And what could be a remedy ? // Heimo Claasen // <hammer at revobild dot net> // Brussels 2003-01-18 The WebPlace of ReRead - and much to read ==> http://www.revobild.net * Belief is no substitute for arithmetic. - Henry Spencer * To unsubscribe from SURVPC send a message to [EMAIL PROTECTED] with unsubscribe SURVPC in the body of the message. Also, trim this footer from any quoted replies. More info can be found at; http://www.softcon.com/archives/SURVPC.html
