Re: BCM v90 chip on 2.6 kernels (u dont hav to reply to this)

[Jacques Goldberg <Jacques.Goldberg@xxxxxxx>]

I suppose that you know what you are doing by selecting "OpenSuse". With 
more than 15 years of Linux behind me, this would be about my last choice.

If your modems are sufficiently old, you can fetch the relevant 
information (PCI vendor and PCI id) under Windows.
You can either open a dumb terminal (a modem connection without defining 
a modem) where you give the commands ATI 1 , ATI 2 , ... , ATI 12, until 
one reports the desired information, but this will fail if you have more 
than one modem in the box when doing this test.
Or you can use the System control icon to reach all of the details about 
hardware including modems and thei PCI identification.

Jacques

D. C. wrote:
> WOW, you guys are AWESOME. I have a geteway box with 5 PCI slots sitting 
> around. This week I'll install OpenSuse on it, pop in the modems (all 
> PCI by the way) and email you what comes up. Thankx. (unless you have a 
> Win32 scanmodem version i dont know about, in which case I can do it today.
>
> THANK YOU, i thought i was th only guy in North America with a Dial-up 
> connection and a 2.6 kernel!
>
>
> Jacques Goldberg wrote:
> > Dear D.C. aka someone23:
> >
> > The very FIRST thing which you should do is to pick up the most recent 
> > version of scanModem.gz at http://linmodems.technion.ac.il/packages
> > which is fresh from TODAY mind you, rather than your antique obsolete 
> > version of  2006_November_07 . Run scanModem for your BCM modem, from 
> > file ModemData.txt it is possible to know if the modem is supported 
> > and which driver should be used.
> >
> > The next thing which you should do is to tell us if your modems are 
> > internal or external, PCI cards, old ISA cards, external box connected 
> > through the 9 pins D-shaped connector at the back of your PC, or to a 
> > USB connector, and even perhaps PCMCIA card if your PC is a laptop.
> >
> > How can we guess that?
> >
> > Now, for each of your modems which is a PCI modem, you should run 
> > scanModem and store with different names the file ModemData.txt which 
> > every run of scanModem and see in each ModemData.txt if your modem is 
> > supported and by which driver.
> >
> > If you do not understand these output files Modem Data.txt, send them 
> > to us and THEM only, none of the other informative files written for 
> > you in the same directory.
> >
> > Jacques
> >
> > D. C. wrote:
> > > Hello, I am currently working on fixing the following:
> > >
> > > Only plain text email is forwarded by the DISCUSS@xxxxxxxxxxxxx List 
> > > Server.
> > > Do use the following as the email Subject Line:
> > > SomeName, YourCountry Ubuntu 6.10 kernel 2.6.17-10-generic
> > > This will alert cogent experts, and distinguish cases in the Archives.
> > > YourCountry will enable Country Code guidance.
> > > Occassionally responses are blocked by an Internet Provider mail 
> > > filters.
> > > So in a day, also check the Archived responses at 
> > > http://www.linmodems.org .
> > > Local Linux experts can be found through: 
> > > http://www.linux.org/groups/index.html
> > > -------------------------- System information 
> > > ----------------------------
> > > Ubuntu 6.10
> > > Linux version 2.6.17-10-generic (root@vernadsky) (gcc version 4.1.2 
> > > 20060928 (prerelease) (Ubuntu 4.1.1-13ubuntu5)) #2 SMP Fri Oct 13 
> > > 18:45:35 UTC 2006 (Ubuntu 2.6.17-10.33-generic)
> > > scanModem update of: 2006_November_07
> > >
> > >
> > > USB modem not detected by lsusb
> > >
> > > Modem or host audio card candidates have firmware information:
> > >
> > > PCI slot PCI ID SubsystemID Name
> > > ---------- --------- --------- --------------
> > > 02:01.0 14e4:4212 1028:0001 Modem: Broadcom Corporation BCM4212 v.90 
> > > 56k modem
> > >
> > > Modem interrupt assignment and sharing:
> > >
> > > --- Bootup diagnositcs for card in PCI slot 02:01.0 ----
> > > [17179574.436000] ACPI: PCI Interrupt 0000:02:01.0[A] -> GSI 22 
> > > (level, low) -> IRQ 169
> > >
> > > === Finished modem firmware and bootup diagnostics section. ===
> > > === Next deducing cogent software ===
> > >
> > > Completed candidate modem analyses.
> > >
> > > The base of the UDEV device file system is: /dev/.udev
> > >
> > > Versions adequately match for the compiler installed: 4.1.2
> > > and the compiler used in kernel assembly: 4.1.2
> > >
> > >
> > >
> > > Compiling resources appear complete:
> > > make utility - /usr/bin/make
> > > Compiler version 4.1
> > > kernel_headers base folder /lib/modules/2.6.17-10-generic/build
> > >
> > >
> > > Checking pppd properties:
> > > -rwsr-xr-- 1 root dip 260920 2006-07-10 19:13 /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)
> > > sudo chmod a+x /usr/sbin/pppd
> > > or under Ubuntu related Linuxes
> > > sudo chmod a+x /usr/sbin/pppd
> > >
> > > Checking settings of: /etc/ppp/options
> > > asyncmap 0
> > > auth
> > > crtscts
> > > lock
> > > hide-password
> > > modem
> > > proxyarp
> > > lcp-echo-interval 30
> > > lcp-echo-failure 4
> > > noipx
> > >
> > > Read Modem/YourSystem.txt concerning other COMM channels: eth0
> > > 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/60-symlinks.rules:# Create /dev/modem symlink
> > > /etc/udev/rules.d/60-symlinks.rules:KERNEL=="ttyLTM[0-9]*", 
> > > SYMLINK+="modem"
> > > Within /etc/modprobe.conf files:
> > > /etc/modprobe.d/alsa-base:options snd-atiixp-modem index=-2
> > > /etc/modprobe.d/alsa-base:options snd-via82xx-modem index=-2
> > > /etc/modprobe.d/blacklist-modem:# Uncomment these entries in order to 
> > > blacklist unwanted modem drivers
> > > /etc/modprobe.d/blacklist-modem:# blacklist snd-atiixp-modem
> > > /etc/modprobe.d/blacklist-modem:# blacklist snd-via82xx-modem
> > > Within any ancient /etc/devfs files:
> > >
> > > Within ancient kernel 2.4.n /etc/module.conf files:
> > >
> > > --------- end modem support lines --------
> > >
> > >
> > > my modem is BCM4212 KRL
> > > any suggestions?
> > >
> > >
> > > I ALSO HAVE ABOUT FIVE MODEMS THAT I HAVE COMPLETELY GIVEN UP ON, 
> > > INCLUDING ROCKWELL, 2 AGERE MODEMS, 1 LUCENT MODEM A SMARTLINK AND A 
> > > CONEXANT. If this dosent work, which should I stuggle with next?
> > >
> > > THANK YOU FOR YOUR HELP.