Re: RH9 -- The Good, The Bad, & The Ugly

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 




Colburn wrote:
I do wish he would give us some info on the modem. Is it internal or external?
He hasn't said. ISA or PCI? again we don't know.


Actually, I stated that it is an internal modem (no one makes ISA's
anymore that I am aware of, so it has to be PCI), and that it is
marketed as tested ready for Linux Kernel 2.4.x.

I guess I missed that. It could also be integrated in the chipset instead of an addin card, and it could use an AMR card.


So what does 'lspci -v' show for it them?

What was broken from RH8 to RH9 that would cause what is supposed to be
a superior version of RH to fail to recognize a Linux-ready piece of
hardware that the older/lesser version successfully recognized?

How are we to know? If I knew how it was configured, driver, IO, IRQ, etc., in RHL8 and which kernels, then what RHL9 shows for it, I might have some idea. But currently I know nothing aboput the modem.


Or, given that it now seems to repeatedly recognize the modem (at least
for the moment), what has changed that would cause the interface to the
ISP to fail post-hardware-handshake?

Again, not much infor given. Any thing in /var/log/messages relating to the connection? First the modem dials. Once the two modems are talking, login information is passed. Once that is done, the ppp tunnel is setup and network parameters are configured.


There are way to debug each of these phases. but you haven't said which is failing or what the failure is. Are you logging in correctly? Is the ppp channel setup? Do the network parameters get returned to pppd?

Fortunately (or unfortunately depending on your point of view) modem based networking is handled by several seperate components in linix, so you can debug each as needed. But you have to work a little to figure out which is failing.

There is an option, that goes in /etc/sysconfig/network-scripts/ifcfg-ppp0 that enables some verbose debug info too. edit that file and set DEBUG=yes. That should get us some more information on what's going wrong, so it can be straightened out. With out that, we're all just guessing.

-Thomas





[Index of Archives]     [Fedora Users]     [Centos Users]     [Kernel Development]     [Red Hat Install]     [Red Hat Watch]     [Red Hat Development]     [Red Hat Phoebe Beta]     [Yosemite Forum]     [Fedora Discussion]     [Gimp]     [Stuff]     [Yosemite News]

  Powered by Linux