hsfconfig fails when attempting to build modules for 2.6.37 kernel. Reproducible: Always Steps to Reproduce: 1.boot in 2.6.37 kernel 2.hsfconfig 3. Actual Results: See attached log. Expected Results: Normal hsfconfig module build.
Created attachment 259386 [details] Emerge info
Created attachment 259387 [details] hsfconfig
I have not tried this, yet, but the patch for kqemu in http://bugs.gentoo.org/show_bug.cgi?id=350746 might work here, too (or the same idea, at least).
Just reporting that after doing autoconf.h and utsrelease.h workaround symlinks (mentioned in bug #308865), I experience same problem (using gentoo-sources-2.6.38).
Created attachment 286987 [details, diff] hsfmodem driver patch 7.80.02.06 Thanks to Chris Vine's patch, posted in hsflinux mailing list (http://www.linuxant.com/pipermail/hsflinux/2011q3/002491.html), I was finally able to use hsfconfig against kernel 3.0.1 successfully. If anyone else is interested in using it, I attached the patch I used - the file being an (edited) aggregate of gentoo's and the above mentioned Chris' patch. In order to use the it, just bump official gentoo net-dialup/hsfmodem ebuild to version 7.80.02.06 (being also the latest version of Linuxant HSF driver) and put the patch into net-dialup/hsfmodem/files directory of your local portage repository. I also intend to test the patch against the latest stable 3.0.4 kernel and will report back when done. As a side note - while there seems to be some kind of 'small movement' at the official Linuxant front of supporting newer versions of Linux kernel, personally, I wouldn't put too much hope on that happening in a very near future: http://www.linuxant.com/pipermail/hsflinux/2011q3/002501.html
To keep my promise - the patch seems to be working alright with kernel 3.0.4 also.
Reading: http://ubuntuforums.org/showthread.php?t=1903439 Looks like its porting to new kernels is being done by some users and a lot of work will be needed to keep this in good shape on every kernel bump. If nobody volunteers to proxy maintain this (with patches and fixes), we will need to treeclean this http://www.gentoo.org/proj/en/qa/proxy-maintainers/index.xml
Hey guys, I read about this bug 351225 in Pacho's recent profile masking entry. A pity I didn't found it many months ago. I've been privately patching and updating this ebuild since january 2011, when the compiling problems started and so volunteer to keep this ebuild up-to-date, since I would do it anyway. I also tried a few times to contact the Linuxant people... all I got was a standard reply like "keep tuned! A new version will be available real soon!" (June 2011). They didn't even bother to upload to their website an updated alsa-kernel-patch I sent them. Anyway, tell me what to do to become the maintainer of this package. I attach 1) The alsa-kernel-patch for newer kernels (alsa-driver-1.0.26.patch) 2) The ebuild I use for the hsfmodem-7.80.02.06 ebuild 3) All required patches for the above mentioned ebuild (patches.zip) Tell me if it doesn't work for you.
Created attachment 331212 [details, diff] The alsa-kernel-patch Works with the 3.5.7-gentoo-sources. Required for compiling the hsfmodem-drivers when building the ebuild
Created attachment 331214 [details] The ebuild with the necessary patch-entries Put this on your local portage overlay (f.e. /usr/local/portage/net-dialup/hsfmodem/)
Created attachment 331216 [details] The patches references in my ebuild The gentoo-patch found in the official portage overlay is still required! Put that file (hsfmodem-7.80.02.06-gentoo.patch), together with the ones found in this tar.gz in your own files-directory (f.e. /usr/local/portage/net-dialup/hsfmodem/files).
Nice! Thanks a lot, please check: http://www.gentoo.org/proj/en/qa/proxy-maintainers/index.xml I also CC proxy-maint team to follow this and know if they are willing to proxy maintain you
(In reply to comment #12) > Nice! Thanks a lot, please check: > http://www.gentoo.org/proj/en/qa/proxy-maintainers/index.xml > > I also CC proxy-maint team to follow this and know if they are willing to > proxy maintain you Any news on this?
(In reply to comment #13) > (In reply to comment #12) > > Nice! Thanks a lot, please check: > > http://www.gentoo.org/proj/en/qa/proxy-maintainers/index.xml > > > > I also CC proxy-maint team to follow this and know if they are willing to > > proxy maintain you > > Any news on this? Absolutely nothing. Not even in my Spam folder.
(In reply to comment #14) > (In reply to comment #13) > > (In reply to comment #12) > > > Nice! Thanks a lot, please check: > > > http://www.gentoo.org/proj/en/qa/proxy-maintainers/index.xml > > > > > > I also CC proxy-maint team to follow this and know if they are willing to > > > proxy maintain you > > > > Any news on this? > > Absolutely nothing. Not even in my Spam folder. I guess I can proxy maintain you directly, are you ok? Anyway, please check if you are able to get it still working with latest (3.7) kernel, otherwise wouldn't have much advantage on keeping it a bit more if will break again so soon :S Thanks
(In reply to comment #13) > (In reply to comment #12) > > Nice! Thanks a lot, please check: > > http://www.gentoo.org/proj/en/qa/proxy-maintainers/index.xml > > > > I also CC proxy-maint team to follow this and know if they are willing to > > proxy maintain you > > Any news on this? please give us some time. Our backlog is quite big so it takes sometime to catch up. But again, feel free to proxy him directly if we don't find time to review this in time
As the original reporter for this problem, I only want to say "thanks" to all who have contributed to resolving it. Looking forward to it becoming maintained and stable.
> I guess I can proxy maintain you directly, are you ok? Anyway, please check > if you are able to get it still working with latest (3.7) kernel, otherwise > wouldn't have much advantage on keeping it a bit more if will break again so > soon :S > > Thanks I will give it a try and further patch if necessary. I'll get back to you. Happy new year
(In reply to comment #18) > > I guess I can proxy maintain you directly, are you ok? Anyway, please check > > if you are able to get it still working with latest (3.7) kernel, otherwise > > wouldn't have much advantage on keeping it a bit more if will break again so > > soon :S > > > > Thanks > > I will give it a try and further patch if necessary. I'll get back to you. > > Happy new year Miquel, any updates on this regarding support with kernel-3.7?
Hey everybody, have been busy with college, that's why this is moving so slow. I just tried to compile the driver against gentoo-sources-3.7.6, and only some minor further patching was required. The new alsa-kernel-patch follows this post. Also, if you happen to use kmod, please note that "modproble -l" is not available anymore. Since the hsfmodem-driver depended on this, I replaced that functionality with a find-based command. Works as intended. In summary: 1) For gentoo-sources-3.7.6 apply alsa-driver-1.0.27.patch against those kernel-sources 2) When using kmod, apply kmod.patch as part of your emerge-process Sorry this is taking so long. I haven't also been able to try it on other kernel-versions. Give me some weeks, I will be having more time by then
Created attachment 338516 [details, diff] alsa-kernel-patch for kernel 3.7.6
Created attachment 338518 [details, diff] Patch for kmod-compatibility
Hi guys, I'm not getting hsfmodem to work with newer implementations of kmod's depmod. Since hsfmodem requires the modules.pcimap file and depmod doesn't generate it anymore ("depmod -m" is deprecated), I see no way of fulfilling that requirement. Any ideas?
It's not clear to me what it needs to be fixed here because there are so many attachments so I am not sure what to review
I think attachments from comment #10 to the end, no? :/
What is the status of this with recent kernels and updated systems? (we need to tag old patches as "obsolete" :S)
(In reply to Pacho Ramos from comment #26) > What is the status of this with recent kernels and updated systems? (we need > to tag old patches as "obsolete" :S) The actual status is describen in comment #23. I pretty much gave up hope because of the mentioned problem
I think we should finally remove this cruft as it needs a ton of changes every month :|
(In reply to Pacho Ramos from comment #28) > I think we should finally remove this cruft as it needs a ton of changes > every month :| Sad but true. Away with it. If only Linuxant made this open source...
(In reply to Miguel Sanjurjo from comment #29) > (In reply to Pacho Ramos from comment #28) > > I think we should finally remove this cruft as it needs a ton of changes > > every month :| > > Sad but true. Away with it. > If only Linuxant made this open source... What solution, then, for actually using built-in laptop modems?
(In reply to Willard Dawson from comment #30) > What solution, then, for actually using built-in laptop modems? I assume we have only two ways here: 1) use old kernels; 2) ask upstream about status of support for new kernels.
removed
