Linux - NewbieThis Linux forum is for members that are new to Linux.
Just starting out and have a question?
If it is not in the man pages or the how-to's this is the place!
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Introduction to Linux - A Hands on Guide
This guide was created as an overview of the Linux Operating System, geared toward new users as an exploration tour and getting started guide, with exercises at the end of each chapter.
For more advanced trainees it can be a desktop reference, and a collection of the base knowledge needed to proceed with system and network administration. This book contains many real life examples derived from the author's experience as a Linux system and network administrator, trainer and consultant. They hope these examples will help you to get a better understanding of the Linux system and that you feel encouraged to try out things on your own.
Click Here to receive this Complete Guide absolutely free.
Alright, got a dual boot working just fine with Windows XP with Fedora Core. Everything works just fine, except for my dial up connection. Yes, shocking, dialup, I know. When I tell Fedora to autodetect the modem, it can't find it. I then tried quering the modem manualy, but it couldn't find it.
Any thoughts on why this is happening, and how would we set this up?
I didn't think of trying that. Here's the info that printed.
00:001.0 PCI bridge: VIA Technologies, Inc. VT8235 PCI Bridge
00:0b.0 Multimedia audio controller: Creative Labs SB Audigy (rev 04)
00:0b.1 Input device controller: Creative Labs SB Audigy MIDI/Game port (rev 04)
00:0b.2 Firewire (IEEE 1394): Creative Labs SB Audigy FireWire port (rev 04)
00:0d.0 Firewire (IEEE 1394): Texas Instruments TSB12LV26 IEEE-1394 Controller (Link)
00:0e.0 Communication controller: Conexant HCF 56k Data/Fax/Voice Modem (Worldwide) (rev 08)
00:10.0 USB Controller: VIA Technologies, Inc. VT82xxxxx UHCI USB 1.1 Controller (rev 80)
00:10.1 USB Controller: VIA Technologies, Inc. VT82xxxxx UHCI USB 1.1 Controller (rev 80)
00:10.2 USB Controller: VIA Technologies, Inc. VT82xxxxx UHCI USB 1.1 Controller (rev 80)
00:10.3 USB Controller: VIA Technologies, Inc. USB 2.0 (rev 82)
00:11.0 ISA bridge: VIA Technologies, Inc. VT825 ISA Bridge
00:11.1 IDE interface: VIA Technologies, Inc. VT82C586A/B/VT82C686/A/B/VT823x/A/C PIPC Bus Master IDE (rev 06)
00:12.0 Ethernet controller: VIA Technologies, Inc. VT6102 [Rhine-IT] (rev 74)
01:00.0 VGA compatible controller: ATI Technologies Inc RV350 AP [Radeon 9600]
01:00.0 Display Controller: ATI Technologies Inc RV350 AP [Radeon 9600] (Secondary)
You probably don't need all of that, but I figured I'd post it all just in case. I also ran a script I had found at linmodems.technion.ac.il called scanModem.gz. The information I got from that is listed below.
FYI, I'm also running Fedora 3.
Providing detail for device at 00:0e.0 with
Class 0780: 14fl:1059 Communication controller: Conexant HCF 56k Data/Fax/Voice Modem (Worldwide) (rev 08)
Subsystem 148d:1634 Digicom Systems, Inc. : Unknown device 1634
Flags: bus master, medium devsel, latency 2, IRQ 11
Last edited by brokenglassltd; 06-14-2006 at 11:05 PM.
We got it working. When you go to http://linmodems.technion.ac.il/first.html they'll give you a script called scanModem. That will print out information about your modem's chipset and what drivers you need to get for it. The one that I needed was available at Linuxant.com.
I wouldn't have even had to post here if I had just read through all the documentation that printed out from the script. But now anyone else who reads this will know where to go for a solution, and I found a good forum. :P