lspci -v显示芯片信息如下，请帮忙看看我应该用哪个驱动（modem）

yeahlang

在哪里有下啊？我找了N久了，都不知道怎么用！～
系统FC2英文版

yeahlang

00:00.0 Host bridge: VIA Technologies, Inc. VT8366/A/7 [Apollo KT266/A/333]
        Subsystem: Giga-byte Technology: Unknown device 5000
        Flags: bus master, 66Mhz, medium devsel, latency 0
        Memory at d0000000 (32-bit, prefetchable)
        Capabilities: [a0] AGP version 2.0
        Capabilities: [c0] Power Management version 2

00:01.0 PCI bridge: VIA Technologies, Inc. VT8366/A/7 [Apollo KT266/A/333 AGP] (prog-if 00 [Normal decode])
        Flags: bus master, 66Mhz, medium devsel, latency 0
        Bus: primary=00, secondary=01, subordinate=01, sec-latency=0
        Memory behind bridge: e8000000-e9ffffff
        Prefetchable memory behind bridge: d8000000-e7ffffff
        Capabilities: [80] Power Management version 2

00:0b.0 Ethernet controller: Realtek Semiconductor Co., Ltd. RTL-8139/8139C/8139C+ (rev 10)
        Subsystem: Realtek Semiconductor Co., Ltd. RT8139
        Flags: bus master, medium devsel, latency 32, IRQ 11
        I/O ports at d000
        Memory at eb400000 (32-bit, non-prefetchable) [size=256]
        Capabilities: [50] Power Management version 2

00:0d.0 Communication controller: Intel Corp. 536EP Data Fax Modem
        Subsystem: Intel Corp.: Unknown device 1000
        Flags: bus master, medium devsel, latency 32, IRQ 10
        Memory at eb000000 (32-bit, non-prefetchable)
        Capabilities: [e0] Power Management version 2

00:10.0 USB Controller: VIA Technologies, Inc. VT82xxxxx UHCI USB 1.1 Controller (rev 80) (prog-if 00 [UHCI])
        Subsystem: Giga-byte Technology GA-7VAX Mainboard
        Flags: bus master, medium devsel, latency 32, IRQ 10
        I/O ports at d400
        Capabilities: [80] Power Management version 2

00:10.1 USB Controller: VIA Technologies, Inc. VT82xxxxx UHCI USB 1.1 Controller (rev 80) (prog-if 00 [UHCI])
        Subsystem: Giga-byte Technology GA-7VAX Mainboard
        Flags: bus master, medium devsel, latency 32, IRQ 10
        I/O ports at d800
        Capabilities: [80] Power Management version 2

00:10.2 USB Controller: VIA Technologies, Inc. VT82xxxxx UHCI USB 1.1 Controller (rev 80) (prog-if 00 [UHCI])
        Subsystem: Giga-byte Technology GA-7VAX Mainboard
        Flags: bus master, medium devsel, latency 32, IRQ 11
        I/O ports at dc00
        Capabilities: [80] Power Management version 2

00:10.3 USB Controller: VIA Technologies, Inc. USB 2.0 (rev 82) (prog-if 20 [EHCI])
        Subsystem: Giga-byte Technology GA-7VAX Mainboard
        Flags: bus master, medium devsel, latency 32, IRQ 11
        Memory at eb401000 (32-bit, non-prefetchable)
        Capabilities: [80] Power Management version 2

00:11.0 ISA bridge: VIA Technologies, Inc. VT8235 ISA Bridge
        Subsystem: Giga-byte Technology GA-7VAX Mainboard
        Flags: bus master, stepping, medium devsel, latency 0
        Capabilities: [c0] Power Management version 2

00:11.1 IDE interface: VIA Technologies, Inc. VT82C586A/B/VT82C686/A/B/VT823x/A/C PIPC Bus Master IDE (rev 06) (prog-if 8a [Master SecP PriP])
        Subsystem: Giga-byte Technology GA-7VAX Mainboard
        Flags: bus master, medium devsel, latency 32, IRQ 10
        I/O ports at e000
        Capabilities: [c0] Power Management version 2

00:11.5 Multimedia audio controller: VIA Technologies, Inc. VT8233/A/8235/8237 AC97 Audio Controller (rev 50)
        Subsystem: Giga-byte Technology GA-7VAX Onboard Audio (Realtek ALC650)
        Flags: medium devsel, IRQ 11
        I/O ports at e400
        Capabilities: [c0] Power Management version 2

01:00.0 VGA compatible controller: nVidia Corporation NV17 [GeForce4 MX 440] (rev a3) (prog-if 00 [VGA])
        Flags: bus master, 66Mhz, medium devsel, latency 32, IRQ 10
        Memory at e8000000 (32-bit, non-prefetchable)
        Memory at d8000000 (32-bit, prefetchable) [size=128M]
        Memory at e0000000 (32-bit, prefetchable) [size=512K]
        Capabilities: [60] Power Management version 2
        Capabilities: [44] AGP version 2.0

[root@localhost root]#
＝＝＝＝＝＝＝＝＝＝＝＝＝＝＝＝＝＝＝＝＝＝＝＝＝＝＝
还有就是声卡不知道怎么搞的，我用XMMS听MP3,声音小得不行，几本上没有声音，用aumix命令调为最大，还是很小，如果不调就根本没有声音？哪位大虾帮帮忙看看！～谢谢先！～

dragonnapalm

注意看 Communication controller那一栏：
Intel Corp. 536EP Data Fax Modem
驱动在这里：
http://linmodems.technion.ac.il/ ... el536-460-1-R90.tgz
包里面应该有README

或者看看这一帖：
http://www.linuxsir.cn/forum.php?mod=viewthread&tid=38329

yeahlang

内核2.6.5，这个驱动是相对2.4内核的
这个驱动在FC2下怎么用呢？dragonnapalm兄
难道一定要重新编译内核吗？

dragonnapalm

刚才使了一下我提供的地址发现不能连接，真是抱歉，这个就是Intel的官方驱动了，兄弟看看：
http://aiedownload.intel.com/df- ... 536ep-460-tle50.tgz
我把里面的ReadME帖出来：

ReadMe file for the
Intel?536EP V.92 chipset Linux driver

contents:
1.  License
2.  Release Notes
3.  Installation
4.  File Descriptions
5.  International Users
6.  Beta Tester appreciation
7.  Security issues
8.  Compilation issues
    a. Instructions for Debian Users
    b. Kernel Source
9.  What is the Hamregistry?
10. what's v92 and v44?
11. The Hamregistry tool (for persistance)
12. Known Bugs/Issues
13. Comments, ideas, problems, fixes

-------------------------------------------------------------------------------
1. LICENSE

IMPORTANT - read the file "LICENSE.txt" for the INTEL SOFTWARE LICENSE
AGREEMENT BEFORE COPYING, INSTALLING OR USING.

-------------------------------------------------------------------------------
2. Release Notes

      This release supports 2.4.x kernels.

      This release is not compatible with kernels prior to 2.4.

      The 536EP corecode binary was compiled with gcc version 3.2

      v92 support added:  modem on hold AT command set,
      PCM upstream, v44, and quick connect are implemented.                         

      Linux Compatability tests are performed on the latest or previous
      versions of the following distributions: Mandrake, RedHat, and SuSE

-------------------------------------------------------------------------------
3.  INSTALLATION

Prerequisites:
   1. root access
   2. bash shell to run install scripts
   3. a 536EP modem
   4. KERNEL SOURCE HEADERS FOR THE KERNEL YOU ARE RUNNING.
      and programming development tools installed as well

6 steps to install
   1. login as ROOT
   2. extract the archive into a directory with "tar -zxvf <archivename>.tgz"
   3. cd into the directory it created.
   4. Type: make clean
   5. Type: make 536ep
   6. Type: make install


Please examine the 536ep-inst script if you have a different distribution.

The driver is split in two.  A serial driver and core driver.
The core driver must be loaded first since the serial driver depends on it.
The serial driver registers itself as character device
   major number 240, minor number 1.


ATTENTION:  if the driver compiles but the script just wont work for you.
   Here are the bare minimum steps to get your modem to work.

   0.  log in as root.
   1.  insmod -f 536epcore.o
   2.  insmod -f 536ep.o
   2a. you can start "hamregistry" at this point if you wish.
   3.  rm /dev/536ep
   4.  mknod /dev/536ep c 240 1   (note "240" is the default, if it does not
       work see what /proc/devices says 536ep's major number is)
   5.  ln -s /dev/536ep /dev/modem
   6.  start a comm application like minicom and use the modem.
   7.  see section 3 (International Users) for info on setting the correct
       country settings.


-------------------------------------------------------------------------------
4.  FILE DESCRIPTIONS

536ep-inst installation script to install 536ep modules and supporting files


files copied to /lib/modules/(kernel-version)/misc
   536epcore.o        driver core code module
   536ep.o        pseudo serial driver for 536ep, depends on 536epcore.o

files copied to  /etc/rc.d/...  (path differes per distribution)
   536ep-boot                boot scrip to start and stop 536ep modules

files copied to /usr/sbin
   hamregistry        hamregistry is the "registry" like tool that the modem uses to
   get and store persistant data such as county info and profile strings.

files copied to /etc
   hamregistry.bin        file that stores the initial persistant data for modem.


-------------------------------------------------------------------------------
5.  INTERNATIONAL USERS

hamregistry will store the last country setting you
set in the modem.

in minicom (or equivalent comm application)
the commmand to change country setting is "AT+GCI="
the command takes a t.35 country code in hexadecimal.
below is a list of currently supported t.35 country codes.
you can also put this "AT" command in the init string of
the comm application you are using.

if you are a CTR-21 country I think you should be able to
choose a CTR-21 country on the list and be ok.  but
that's no guarantee.
The same goes for countries that are "USA" compatable.
(this table also exist in the source file wwh_dflt.c that
ships with the 536epcore driver)

inspect the wwh_dflt.c file provided to find out what your country's t.35 code is.

-------------------------------------------------------------------------------
6.  Thanks to the following beta testers for their valuable input and
    suggestions during the HaM 333 beta test between January 2 - 26, 2001

Dorian S. Araneda
Sean Walbran
Rob Clark
Marvin Stodolsky
Dominique Duval
Roman Krais
Ulrich Guenther
Marcelino Viana Pinheiro
Thomas S. Iversen
Jospeh Teichman
Michel Bartolone (MED)
Ramon Gonzalez Montoiro
Ryoji Kawagishi
Torsten Vogel
"jandro"
Ian Carr-de Avelon
Helga Weindl
Ed Casas
Bernhard Hoelcker
Alexander "Sasha" Voytov
Albert Woo
Peter Hirschmann

and all of the helpful Linux HaM users
around the world and at www.linmodems.org

-------------------------------------------------------------------------------
7. Security issues

the 536ep-inst and 536ep-boot file install the files and device nodes as
root for the owner and group.  
this will cause problems for those who want to user the modem to dialout
using an account other than root.

In SuSE, "dialout" is the group used to install the files and device node.
This way, anyone belonging to the "dialout" group can use the modem to dialout.
(take a look at /etc/group)

I did not want the script to allow full access of the modem to everyone without
"root" knowing.

Edit the 536ep-boot and 536ep-inst scripts to fit your needs.

-------------------------------------------------------------------------------
8. Compile issues
   a. this driver will now compile with the this path:
   /lib/modules/<kernel version>/build/include
   the 2.4.4+ kernels says to copy the /boot/vmlinuz.version.h
   over to the kernel build path.  I have the makefile do this
   if this file exists.  You must install the kernel source
   code anyways.  It should be on your distribution's CD.


-------------------------------------------------------------------------------
9.  What is the Hamregistry?
   The hamregistery is an application that stores data for the 536ep driver onto
   the disk.  hamregistry stores information from the driver that needs to
   persist from reboot to reboot such as you current country setting.
      The 536ep-inst install script and the 536ep-boot script start this utility
      automatically for you.
   If this tool is not present when the driver gets used your profile,
   quickconnect, and current country setting will not be saved but the driver
   should still work fine.        The only step that would need to be done is to
   make sure that the driver is set to the correct country with
   at+gci= (see section 5)


-------------------------------------------------------------------------------
10. What's v92 and v44?  

   a. modem on hold: (ISP and your ISP dialer must also support this)
      This will allow you to pause your ppp connection to answer an incoming
      call. You will need call waiting, dialer, and ISP support for this to
      work.  When you are done with the call you can resume your ppp connection
      without having to reconnect.  The AT command set for this feature exist
      in the driver.

   b, pcm upstream:
      (ISP must also support this, as of version 4.32 I
       dont know any ISP's that do)
      This will allow faster upload speeds.
      to enable: at+pig=0
      to disable: at+pig=1

   c. quickconnect:
      Once you make a call to a v92 modem, your phoneline characteristics are
      stored.  Whenever you make a new v92 connection it will use this data
      to make the call negotiation  quicker (approx 10 seconds).
      to enable: at+pqc=0  at+pss=0
      to disable: at+pss=2

   d. v44: (ISP must also support this)
      A better compression protocol than v42 which can give you better transfer
      speeds.

-------------------------------------------------------------------------------
11. The Hamregistry tool
   
   The hamregistry tool is used to provide persistance of settings across
   reboots.  The haminst and hamboot scripts automatically setup and start
   the hamregistry background task for the modem to use.
   The hamregistry tool has command line arguments for those who wish to
   customize persistant settings.  To use these command lines
   you must first stop the driver with "bash hamboot stop".
   Once the driver has been stopped you may run hamregistry with one of these
   arguments to store into the /etc/hamregistry.bin persistance file:
   (supply value for items in < >)
      -mfg <Modem manufactures name>
      -mod <Modem model name>
      -hookflash  <0,1,2>
        hookflash method:  0=(default)without tone  1=with tone  2=reserved
      -v92rptopt  <0,1>
        control v92 reporting:   0=PCM upsteam only       1=(default) all v92
      -gpio_lpohd <0,1>
        Handset Hook detection:  0=not supported          1=(default)supported
      -currentcountry <t.35 code>

   This info is written to the /etc/hamregistry.bin file.
   If hamregistry.bin exists along with the installation files, haminst will
   copy it to /etc/hamregistry.bin when installing the modem.

-------------------------------------------------------------------------------
12. Known Bugs/Issues

   a. If you see this message
      "536ep:rs_open: DSP did not reset. try again or restart computer"
      and you KNOW you have a HaM modem installed
      Disable "NP OS" in your bios.  There is a problem with the driver and
      linux PNP.  After a time, Linux PNP will disable the card and the driver
      currently can not reenable itself.
   b. Be aware that the build replaces your
      /lib/module/<kernver>//build/include/linux/version.h file with
      /boot/vmlinuz.version.h
      (this is what Linus T. told me to do with a compiler error)
   c. There may be an incompatibility with DevFS. The 536ep device may be located
      in /dev/tts/536ep
      instead of /dev/536ep.  Be aware of this and link /dev/modem to the 536ep
      device that corresponds to your setup.
   e. Incase you are having problems making a ppp connection try using wvidal
      with this information below. execute the script and it will have wvdial
      make the ppp connection

   ------my script----------------------
   #! /bin/sh
   /usr/sbin/pppd -detach lock asyncmap 00000000 \
      defaultroute debug /dev/modem 57600 \
      ipparam ppp0 linkname ppp0 \
      noauth \
      connect "/usr/bin/wvdial --chat bellsouth"

   ------my /etc/wvdial.conf section ---
   [Dialer bellsouth]
   Modem = /dev/modem
   Baud = 57600
   Init1 = ATZ
   Inti2 = ATQ0 V1 E1 S0=0 &C1 &D2
   Dial Command = ATDT
   Phone = 6859500
   Username = myloginname
   Password = mysecretpassword
   #Ask Password = 1
   Stupid Mode = 0
   ------------------


-------------------------------------------------------------------------------
13. Comments, ideas, problems, fixes? please contact:

Linux Voice Band Modems (VBM) of Intel Residential Access Division (RAD)

vbm.linux@intel.com
http://developer.intel.com/design/modems/

To restrict email volume, please email only development related issues that are
needed to fix a bug or improve the driver. General questions on how to use the
Linux may not be responed to.

Other resources and information on Linux controllerless modems can be found on
these usefull sites

http://www.linmodems.org
        and
http://linmodems.technion.ac.il

dragonnapalm

不需编译内核，先按照ReadME里面的试试看

yeahlang

真是个大好人
我以前也下了个intel536-4.68.tgz在官方网站下的，发现不行
我待会再试试看，感激不尽啊！～

yeahlang

2. Release Notes

This release supports 2.4.x kernels.

This release is not compatible with kernels prior to 2.4.
The 536EP corecode binary was compiled with gcc version 3.2

v92 support added: modem on hold AT command set,
PCM upstream, v44, and quick connect are implemented.

Linux Compatability tests are performed on the latest or previous
versions of the following distributions: Mandrake, RedHat, and SuSE



编译不了，有错误！~

yeahlang

有没有2.6.5 kelnel的驱动啊？

ltkun

用猫的还是乖乖地用它说的内核吧