Re: Installing modem
> I disabled com1 & com2 hardware ports in the BIOS and booted into Linux the > dmesg log concerning the serial ports is as follows: > > Serial driver version 5.05c (2001-07-08) with MANY_PORTS SHARE_IRQ > SERIAL_PCI enabled > Redundant entry in serial pci_table. Please send the output of > lspci -vv, this message (12b9,1008,12b9,00d3) > and the manufacturer and name of serial board or modem board > to [EMAIL PROTECTED] > ttyS04 at port 0xd000 (irq = 19) is a 16550A > > I noticed while in BIOS the only IRQ1 thru 14 are listed. Does this matter? > > After extracting dmesg, I returned to command line and issued the following: > echo "ADTD3633070" > /dev/ttyS3 > echo "ADTD3633070" > /dev/ttyS4 > > Niether command resulted in any sound from the modem and no errors were > reported. > > Regards; > Hoyt Have you tried resetting your BIOS? Have you tried using another kernel as well? Try also running the ppp scripts where you will see output, I don't think echoing into the devices will out put anything unless you are watching the ttyS's. You might have to be dumping the ttyS* output using cat or something similiar in order to see any errors. Aaron Hsu -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: Installing modem.
> What program generated the connection between the modem's 8 I/O lines > d000-d007 and /dev/ttyS3 and what would happen if I rm /dev/ttyS4 and maybe > /dev/ttyS3 as well and remade, with MAKEDEV, ttyS3 and then run the program > that makes the original connection. > Regards; > Hoyt Alright, I am wondering, did you diff the dmesg before you put your modem in with the one after? That might help in figuring out some things. I think you can go ahead and remake the ttyS3 and 4 devices, and try again. I am also a little confused, when you dial out, do you hear the dial tone and the phone number being dialed, then it cuts out; or do you just get a "modem not responding" error? What I am asking is, exactly where does the initialization and dialing begin to fail? Instead of using ATDT###- you might want to look at some of the scripts and try running some of the modem scripts, assuming your modem is that far along, and see what happens. It would be really nice to see the exact errors that are happening, i.e.-the output from the modem commands. There is a program that allows you to manually enter a shell like interface and run modem commands, you should be able to see the output. I only used this on OpenBSD a while ago though, so I don't know what the program is. You can also try WVDial, which is essentially like kppp and some of the others, in that it auto-detects and is pretty smart about getting things right; I found that it is a nice program for debugging and general use, it's also console based. ;-) Aaron Hsu -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: Installing modem.
> > 1. Use /dev/MAKEDEV to make the ttyS4 device in /dev, as your kernel > > will normally not make it for you. > > > > 2. The device should now be available under that name, and you should > > be able to use it freely in any system, you should probably also > > symlink it to /dev/modem so that some dialer programs will work > > properly. > > . . . > You are on target however there is some question, in my mind at least, where > the modem is installed in linux. KDE says it is d000-d007 others say it > should be ttyS04 and ttyS4 my system seems to list ttyS? as TTYS??. Windows > XP installed it on com4, which impilys that it should be probably on TTYS03. > Perhaps I'm just confused because I dont know enough. Thanks for your input > I'll keep it in mind. > Regards; > Hoyt To find out what device you should be using, I recomend this method, which worked for me. If you are using a PCI modem, then it is almost guaranteed that your device will be something like ttyS4. To find out what you should use in /dev/MAKEDEV, just dmesg | grep tty or whatever happens to bring up the relevant lines about your modem. Should it say something like ttyS05, then you should MAKEDEV ttyS5. In my case, I saw ttyS04, so I think [it has been a while] I ran "/dev/MAKEDEV /dev/ttyS4" and it created the device properly and the modem responded. The thing that confused me back then was that I thought the modem device was already created, since I already had ttyS0-3, but I didn't realize that I had to make another device for ttyS04 that the dmesg reported. I hope this helps. Aaron -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: G550 and 3D acceleration
Hmmm, alright, here's what it looks like to me . . . What you are seeing with the framebuffer stuff is for the console. That's what allows your console to print its text. When you load X it is not loading the modules or it can't find them. To find out whether there is support in the kernel, you really need to install the source and take a look at it. In my 2.4.22 kernel source, I find Matrox G400 drivers that claim to also work with the G450. I am not sure if they will also work with your G550, but perhaps it will. In order to use them, if the kernel image you are using right now does not offer a module of it, or it is not compiled in [most likely not]; the best thing I can recomend to you is to try those modules and compile the drivers as modules with your new kernel. I don't know if you have compiled kernels or not before, but it isn't too bad. If that doesn't work, http://www.matrox.com has a listing of 3rd party driver providers, and there are some commercial drivers available from XIG [I think the URI is http://www.xig.com] but they should offer free evaluation copies. There are other sites offering drivers, so I would check out the matrox site and see what you can find there as well if recompiling the kernel with matrox drivers does not help. I hope this helps, Aaron Hsu -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: Installing modem.
I have come into this thread pretty late, but from what I understand, you are trying to get a modem to work. It's a PCI modem, and you can see it mentioned in the kernel as ttyS04. The problem, as I see it, is that you can't get the modem to respond to any calls from any programs? If I understand this all correctly, I had a horrible time with this a while back with another computer, where I could get the PCI modem automatically recognized and used in RedHat, but in Debian I could get nothing out of it. Some wise user showed me how to fix this: 1. Use /dev/MAKEDEV to make the ttyS4 device in /dev, as your kernel will normally not make it for you. 2. The device should now be available under that name, and you should be able to use it freely in any system, you should probably also symlink it to /dev/modem so that some dialer programs will work properly. I hope this helps, tell me if I misunderstand what you are trying to do, and sorry if this was OT. Aaron Hsu -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
