I think this livecd has installed all software you need to set up this modem, It's a pity that some modules(not firmware) are missed in the kernel. Could you add these modules to the livecd kernel? speedtch firmware_class usb_atm hci_usb Then you alwais need the firmware, but in this way you avoid to compile the kernel Reproducible: Always Steps to Reproduce: 1. 2. 3.
What kernel options enable those modules?
(In reply to comment #1) > What kernel options enable those modules? See "Kernel Config" at http://forums.gentoo.org/viewtopic-t-327025-highlight-speedtouch.html
So we should be using the kernel modules rather than the speedtouch ebuild? What would we need for the ebuild to work? Unfortunately, I know nothing of speedtouch hardware, and don't have one, so I need exact specifics if this is to make it onto the 2005.1 release.
(In reply to comment #3) > So we should be using the kernel modules rather than the speedtouch ebuild? For kernel >= 2.6.10, yes. Kernel 2.6.10 added functionality which makes the "speedtouch" package's executables obsolete (and indeed breaks the "modem_run" executable, meaning that the kernel's method must be used). > What would we need for the ebuild to work? For kernel >= 2.6.10: /etc/init.d/speedtouch should not call modem_run to load the firmware - the firmware will be loaded by hotplug.
So I need to drop the ebuild if I go with the in-kernel modules, correct? Sorry for being so dense on this, I just want to make sure it is correct.
(In reply to comment #5) > So I need to drop the ebuild if I go with the in-kernel modules, correct? The problem with the ebuild is that it is currently broken for kernel >= 2.6.10, although I *think* that the most important fix (to /etc/init.d/speedtouch) is pretty trivial. I'll re-install it and check. I suppose the answer to your question depends on: * Whether the next LiveCD will include any kernels < 2.6.10? * Whether the speedtouch ebuild will be made compatible with kernel >= 2.6.10 in time for the next LiveCD. If the LiveCD only contains kernel >= 2.6.10, and the speedtouch ebuild is not fixed in time, then it would be better to drop the broken ebuild - instructions can be added to the wiki as to how to get a Speedtouch modem working easily, as long as the in-kernel modules are available.
Since the ebuild focuses so much on the configuration of modem_run, I think it would be better to replace the ebuild (for kernel >= 2.6.10) with setup instructions on a wiki. Should I create http://gentoo-wiki.com/HOWTO_Speedtouch_modem ? So, leaping to conclusions, my proposal is: * Add the mentioned modules to the LiveCD ( >= 2.6.10 ) kernel. * Mark the speedtouch ebuild as being "not applicable" for kernel >= 2.6.10 (if that's possible), and instead point the user at the wiki article. * I'll populate the wiki article.
We're using 2.6.12 on most arches. I've removed the ebuild from my build templates for the release. If you wrote up a howto on using a speedtouch device, we would either want to link to it, or even better, incorporate it into the Handbook so everyone can benefit form it (and it'll be on the CD itself for those with only one machine and a speedtouch modem, since they won't be able to get online to read the wiki doc) Sound good?
(In reply to comment #8) > Sound good? Sure does. It's a slight shame that a user will need to get online to download the official firmware for the modem. I've made a start on the wiki.
Agreed. Without knowing the legal nature of the firmware, though, I am reluctant to include it on the CD.
(In reply to comment #10) > Agreed. Without knowing the legal nature of the firmware, though, I am > reluctant to include it on the CD. FYI, here's the legal agreement for the official firmware: http://www.speedtouch.com/driver_upgrade_lx_3.0.1.2.htm I don't think that the open-source version of the firmware will work with kernel >= 2.6.10.
*** Bug 99328 has been marked as a duplicate of this bug. ***
The wiki entry is "finished": http://gentoo-wiki.com/HOWTO_Speedtouch_modem
Docs-team: is there any way we can get the wiki information for speedtouch incorporated into the "Getting Connected" section of the Handbook?
Sorry to disappoint you, but the text is quite difficult for users; adding all this just for a single device is major overkill and generally not done for the handbook. Better would be to have a script available that does this or make the process easier.
I'll see if I can add it to the txt I sent you previously though
Don't worry about it... we'll just add it to the release notes for now...
Hi folks. I've been using a Speedtouch modem under Linux for a very long time and was the author of the first (now rather crufty) 2.6 guide in the Gentoo forums. I agree that it is still too difficult to get these things working from the point of view of someone who has not done it before. I'm posting here for two reasons (1) I too am interested in having it "officially" supported on the LiveCD in some capacity (2) I'm planning on proposing a revamped speedtouch ebuild which makes the process as easy as possible. To that extent I intend to add several improvements such as: * Automatic integration of required firmware (probably with fetch restriction; perhaps this fetch support could be vetoed by the "livecd" USE flag to avoid complications when rolling LiveCD release?) * More intelligent init scripts. Simple hardware detection routine to choose correct firmware out of the 2 firmware dumps available upstream automatically (a la Debian) unless overridden by user. * Proper PPPoATM pppd example configuration and instructions/documentation/manpages. * Maybe add ebuild config support if it makes sense. * Clear and informative ebuild post-install "einfo" to help get a new user oriented. The level of work required to achieve this is fairly modest I believe. The way I see it, there are two issues to contend with at the moment: * The new methodology of uploading firmware to hotplugged devices. I think it would be silly at this point to constrain users to >=2.6.10 kernels and am concerned that this approach might be less flexible (and less well understood at this point in time) that the modem_run approach. Currently testing the waters here. * I have no experience with PPPoE but wouldn't want for these users to be left out in the dark. Also, there are one or two very minor mistakes in the wiki document. For example, when opting for the modular approach it is only necessary to insert "pppoatm" in the modules.autoload.d/kernel-2.6 file (and "speedtch" but only if one is not using the coldplug init script). Also, the comment above suggesting that 2.6.10 "adds features which breaks the modem_run executable" is simply not correct. I've used modem_run since 2.4, through the entire 2.6 series (including some early release candidates) and am currently still using it without any problems on 2.6.12. But there may be some concerns that I am not yet aware of. Paul, if you have the time I'd very much like to hear more about that and am also wondering if you're interested in the work I intend to do on the ebuild?
I agree that the wiki entry is a little overenthusiastic with the word "must" - it was done in the interests of simplicity, given that there's quite a few steps in it already. Feel free to to edit the wiki entry, and/or add to its "talk" entry. I never managed to get modem_run working under kernel >=2.6.10 - however, looking back, that was probably caused by the speedtouch kernel module conflicting with it (or conflicting with the open-source firmware). I hadn't heard of anyone using modem_run with such a kernel. Does the current speedtouch ebuild work for you, using the *open-source* firmware? It would be great to remove the catch-22 situation of getting the modem to work without the prerequisite of a working Internet connection to download (and prepare) the redistribution-restricted official firmware files. Yes, I'm interested in collaborating to improve the speedtouch ebuild. I haven't worked on ebuilds before.
Oops, a complete open-source speedtouch firmware doesn't exist. I was confused by my vague remembrance of the user-space vs kernel-space methods, vs the current kernel module, and "driver" vs "firmware" vs "microcode", and the 3 official firmware versions, and the modem's "boot code" vs "main firmware code" :-)
This should be resolved with 2005.1
