[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: RH 4.1 and IBM Token Ring
On Fri, 20 Jun 1997, Navratilova, Viktorie wrote:
> Ok, so there's this circus gorilla, this nun, this priest, and this
> rabbi, and they all walk into a bar.
> The priest goes up to the bartender and the bartender goes "what's a
> matta you?"
> and the priest goes:
> "well, ya see my son, it's like this: I installed redhat 4.1 on my
> computer, and I compiled token ring support into my kernel (2.0.27), and
> I used the GUI
> Metro-X control panel Network Manager (sic) to add support for both an
> ethernet and token ring cards, with the ethernet set to inactive and the
> token ring set to active. So the pope says I gotta run Windows 95 on my
> other partition because it's his computer, so I gotta worry about that
> too. The first token card I put in works beautifully under Linux, which
> has no problem detecting it. But it don't work under Win 95, so I gots
> to switch to an older, slightly shittier card, which works fine under
> Win 95, but which causes me some heartache under Linux. When I boot
> into Linux with this card, Linux detects it (This is from the dmesg:
> tr0: ISA adapter found using IRQ7, PIOaddr a20
> tr0: Hardware address:00:03:0F:80:34:5C)
> Hallelujah!
> But then it immediately starts spouting this message to all consoles
> every three seconds, continually flooding the screen, as if there were
> some sort of daemon inside my computer!
> tr0: unknown command 21 in arb
> What to do? What to do? The token ring mini-how-to is dreadfully old
> and doesn't address this situation.
> Anyone have any ideas on how I can gain salvation under Linux again?"
>
> And the rabbi opens his mouth and says:
> <insert pithy advice here>
>
The Rabbi answers:
1. I know nothing about token ring but I have solved this type of problem
before.
2. The way to solve the problem is to search the newsgroups for "in arb"
and "token ring unknow command". If you don't find anything helpfull,
3. grep through the sources of the device driver for "unknown command" or
"in arb".
4. Determine if the message has any critical significance. It could be
that you can ignore it - i.e. comment it out, rebuild the driver and
go on your merry way.
5. If the above doesn't work, try another Rabbi.
6. Peace be unto thee sister,
- yba
EE 77 7F 30 4A 64 2E C5 83 5F E7 49 A6 82 29 BA ~. .~ TclTek Ltd.
=}-------------------------------------------------ooO--U--Ooo-----------{=
- benavrhm@tcltek.co.il - tel: +972.52.670.353, http://www.tcltek.co.il -
References: