SPYRIDON, RE: the modem seems to be connected but I can't use my browser. Most commonly, this is due to other COMM channels being open, which blocks DNS services to the new ppp0 channel Do $ ifconfig if any COMM channel but loopback (lo) is show, say eth0, shut it down: $ sudo ifconfig eth0 down check again with $ ifconfig Then after a new dialout, DNS services should be fine. More generally, read Jacques' Postinstall Howto at http://linmodems.technion.ac.il/ MarvS On Dec 9, 2007 9:09 PM, SPYRIDON MOYSIS <moysis.spyridon@xxxxxxxxx> wrote: > Mr. Marvin Stodolsky, > Thanks for your help about the installation of my modem. > Just tonight I made my modem works according to your guide info you sent me. > I have connected now with the "wvdial" in a Shell konsole (and I > replay to your e-mail now). > Also I made the connection using the "Kppp" only as a root user. I > can't connect as a default user and also I can't connect with the "K > network Manager". > When I choose the dial up connection I hear the dialing, the > handshaking the modem seems to be connected but I can't use my > browser. > Anyway thanks again for your help. > Spyros > > > > > > On Dec 6, 2007 3:01 AM, Marvin Stodolsky <marvin.stodolsky@xxxxxxxxx> wrote: > > SPYRIDON > > > > For > > > > Class 0703: 10b9:5457 Modem: ALi Corporation M5457 AC'97 Modem Controller > > Primary PCI_id 10b9:5457 > > Subsystem PCI_id 103c:0850 > > Softmodem codec or chipset from diagnostics: > > from Archives: CXT, a Conexant type, > > > > At http://www.linuxant.com/drivers/hsf/full/downloads-suse-x86.php?PHPSESSID=f70ad59a0ec21d76e736a92e5ff90416 > > download hsfmodem-7.68.00.04full_k2.6.22.13_0.3_default-1suse.i586.rpm.zip > > Under SuSE: > > $ unzip hsf*.zip > > $ su root > > # rpm -i hsf*.rpm > > will run the install. > > > > Afterward the modem should be found by > > # wvdialconf /etc/wvdial.conf > > If successful, edit in your personal info with: > > # gedit /etc/wvdial.conf > > removing the ; and < > symbols > > > > Then try a dial out with > > # wvdial > > > > Report back at this point. > > > > MarvS > > > > > > On Dec 5, 2007 7:33 PM, SPYRIDON MOYSIS <moysis.spyridon@xxxxxxxxx> wrote: > > > I'm new Linux user, I don't now command line and I need help to make > > > my modem works. > > > The text below is taken from "ModemData.txt" Thanks for your time. > > > > > > -------------------------------------------------------------------------------------------------------------------------------------------------------------- > > > Only plain text email is forwarded by the Discuss@xxxxxxxxxxxxx List Server, > > > as HTML can contain viruses. Use as the email Subject Line: > > > YourName, YourCountry > > > Welcome to openSUSE 10.3 (i586) - Kernel kernel 2.6.22.13-0.3-default > > > With this Subject Line cogent experts will be alerted, and useful > > > case names left in the Archive. > > > YourCountry will enable Country specific guidance. Your contry's > > > local Linux experts > > > can be found through: http://www.linux.org/groups/index.html > > > Responses from Discuss@xxxxxxxxxxxxx are sometimes blocked by an > > > Internet Provider mail filters. > > > So in a day, also check the Archived responses at http://www.linmodems.org > > > -------------------------- System information ---------------------------- > > > CPU=i686, > > > Welcome to openSUSE 10.3 (i586) - Kernel > > > Linux version 2.6.22.13-0.3-default (geeko@buildhost) (gcc version > > > 4.2.1 (SUSE Linux)) #1 SMP 2007/11/19 15:02:58 UTC > > > scanModem update of: 2007-20-07 > > > > > > > > > There are no blacklisted modem drivers in /etc/modprobe* files > > > ---ALSA bootup diagnostics --- > > > > > > The Advanced Linux Sound Architecture (ALSA) packages providing audio > > > support on your System, > > > also includes drivers for some modems. High Definition Audio (HDA) > > > cards can themselves host > > > a softmodem chipset, with both audio+modem supported by a snd-hda-intel driver. > > > The ALSA diagnostics are written during bootup to /proc/asound/ folders. > > > > > > > > > Modem not detected though HDA card diagnostics, though not excluding > > > a possible Conexant modem chip impervious to ALSA diagnostics. > > > Proceeding through alternative possibilties. > > > > > > Summary card and chipset information is in: > > > /proc/asound/cards: > > > 0 [A5451 ]: ALI5451 - ALI 5451 > > > ALI 5451 at 0x1000, irq 5 > > > > > > /proc/asound/pcm: > > > 00-00: ALI 5451 : ALI 5451 : playback 32 : capture 1 > > > > > > A copy of /proc/asound had been copied to Modem/ALSAroot.tgz > > > USB modem not detected by lsusb > > > > > > For candidate card, firmware information and bootup diagnostics are: > > > > > > PCI slot PCI ID SubsystemID Name > > > ---------- --------- --------- -------------- > > > 00:08.0 10b9:5457 103c:0850 Modem: ALi Corporation M5457 > > > AC'97 Modem Controller > > > > > > Modem interrupt assignment and sharing: > > > 10: 117469 XT-PIC-XT uhci_hcd:usb1, uhci_hcd:usb2, > > > eth1, ohci1394, radeon@pci:0000:01:05.0, eth0 > > > --- Bootup diagnostics for card in PCI slot 00:08.0 ---- > > > PCI: Enabling device 0000:00:08.0 (0000 -> 0003) > > > ACPI: PCI Interrupt 0000:00:08.0[A] -> Link [LNK6] -> GSI 10 (level, > > > low) -> IRQ 10 > > > 0000:00:08.0: ttyS0 at I/O 0x1428 (irq = 10) is a 8250 > > > 0000:00: 08.0: ttyS2 at I/O 0x1440 (irq = 10) is a 8250 > > > 0000:00:08.0: ttyS3 at I/O 0x1450 (irq = 10) is a 8250 > > > Couldn't register serial port 0000:00:08.0: -28 > > > > > > === Finished modem firmware and bootup diagnostics section. === > > > === Next deducing cogent software === > > > > > > A candidate driver could not be identified. > > > > > > There is candidate modem software. > > > > > > For candidate modem in PCI bus: 00:08.0 > > > Class 0703: 10b9:5457 Modem: ALi Corporation M5457 AC'97 Modem Controller > > > Primary PCI_id 10b9:5457 > > > Subsystem PCI_id 103c:0850 > > > Softmodem codec or chipset from diagnostics: > > > from Archives: CXT, a Conexant type, > > > CXT is a generic for all CXTnumbers, with Linuxant hsfmodem > > > software support. > > > > > > Lacking a dsp (digital signal processing) chip, the modem is a software > > > intensive or "softmodem" type. Its primary controller manages the traffic > > > with the CPU. But the software needed is specified in the Subsystem. > > > ----------------------------------------- > > > Support type needed or chipset: hsfmodem > > > > > > > > > For owners of a Dell PCs with Conexant HSF modems, a driver source > > > package with full speed enabled is available, but requires driver > > > compiling. Read Conexant.txt > > > > > > The hsfmodem package serves a great variety of Conexant chipset modems. > > > Start at http://www.linuxant.com/drivers/hsf for > > > eventually download of a hsfmodem-SomeVersion.zip package with > > > SomeVersion containing your kernel_version 2.6.22.13-0.3-default in > > > the filename if possible. > > > These packages have compiled drivers. Otherwise download the generic > > > hsfmodem-Version.tar.gz package. Its usage will require compiling. > > > > > > Read Conexant.txt > > > > > > Writing Conexant.txt > > > > > > > > > Completed candidate modem analyses. > > > > > > The base of the UDEV device file system is: /dev/.udev > > > > > > Versions adequately match for the compiler installed: 4.2.1 > > > and the compiler used in kernel assembly: 4.2.1 > > > > > > linux-headers-2.6.22.13-0.3-default resources needed for compiling > > > are not manifestly ready! > > > > > > If compiling is necessary packages must be installed, providing: > > > kernel-source-2.6.22.13-0.3-default > > > > > > > > > If a driver compilation fails, with message including some lack of > > > some FileName.h (stdio.h for example), then > > > Some additional kernel-header files need installation to /usr/include. > > > The minimal additional packages are libc6-dev > > > and any of its dependents, under Ubuntu linux-libc-dev > > > > > > If an alternate ethernet connection is available, > > > $ apt-get update > > > $ apt-get -s install linux-kernel-devel > > > will install needed pacakage > > > For Debian/Ubuntu related distributions, run the following command to > > > display the needed package list: > > > > > > Otherwise packages have to be found through http://packages.ubuntu.com > > > Once downloaded and transferred into a Linux partition, > > > they can be installed alltogether with: > > > $ sudo dpkg -i *.deb > > > > > > > > > Checking pppd properties: > > > -rwxr-xr-x 1 root dialout 298784 2007-09-22 02:41 /usr/sbin/pppd > > > > > > In case of an "error 17" "serial loopback" problem, see: > > > http://phep2.technion.ac.il/linmodems/archive-sixth/msg02637.html > > > > > > To enable dialout without Root permission do: > > > $ su - root (not for Ubuntu) > > > chmod a+x /usr/sbin/pppd > > > or under Ubuntu related Linuxes > > > chmod a+x /usr/sbin/pppd > > > > > > Checking settings of: /etc/ppp/options > > > noipdefault > > > noauth > > > crtscts > > > lock > > > modem > > > asyncmap 0 > > > nodetach > > > lcp-echo-interval 30 > > > lcp-echo-failure 4 > > > lcp-max-configure 60 > > > lcp-restart 2 > > > idle 600 > > > noipx > > > file /etc/ppp/filters > > > > > > In case of a message like: > > > Warning: Could not modify /etc/ppp/pap-secrets: Permission denied > > > see http://linmodems.technion.ac.il/bigarch/archive-sixth/msg04656.html > > > > > > Read Modem/YourSystem.txt concerning other COMM channels: eth0 eth1 > > > Which can interfere with Browser naviagation. > > > > > > Don't worry about the following, it is for the experts > > > should trouble shooting be necessary. > > > ========================================================== > > > > > > Checking for modem support lines: > > > -------------------------------------- > > > /device/modem symbolic link: > > > slmodemd created symbolic link /dev/ttySL0: > > > Within /etc/udev/ files: > > > /etc/udev/rules.d/77- network.rules:SUBSYSTEM=="net", > > > ENV{INTERFACE}=="ppp*|ippp*|isdn*|plip*|lo*|irda*|dummy*|ipsec*|tun*|tap*|bond*|vlan*|modem*|dsl*", > > > GOTO="skip_ifup" > > > /etc/udev/rules.d/50-udev-default.rules:KERNEL== "mwave", > > > NAME="modems/%k", GROUP="uucp" > > > Within /etc/modprobe.conf files: > > > /etc/modprobe.conf:# Linux ACP modem (Mwave) > > > Within any ancient /etc/devfs files: > > > > > > Within ancient kernel 2.4.n /etc/module.conf files: > > > > > > --------- end modem support lines ------- > > > > > >
