Ubuntu
linux package

rt2500 doesn't build with current hardy / module-assistant

Bug #183818 reported by Kjell Braden on 2008-01-17

Affects		Status	Importance	Assigned to	Milestone
	Linux	Unknown	Unknown	sf #2219522
	linux (Ubuntu)	Won't Fix	Low	Unassigned

Bug Description

Binary package hint: rt2500

module-assistant in current hardy fails to build the rt2500 module:

sudo m-a build rt2500

gives those error messages:
/usr/src/modules/rt2500/rtmp_main.c: In function 'RT2500_probe':
/usr/src/modules/rt2500/rtmp_main.c:254: error: implicit declaration of function 'SET_MODULE_OWNER'

The whole buildlog is attached.

I'm using ubuntu hardy i386, module-assistant 0.10.11 and rt2500-source 1:1.1.0-b4+cvs20070924-2

Revision history for this message

Kjell Braden (afflux) wrote on 2008-01-17:

buildlog from module-assistant Edit (1.8 KiB, text/plain)

Revision history for this message

Stéphane Maniaci (stephh) wrote on 2008-03-28:

I can confirm this on 64 bits Beta Hardy release.

Revision history for this message

McFry (timo-latecrew) wrote on 2008-04-22:

i too can confirm this. this is quite critical, as the rt2500 module that ships with hardy rc1 has a serious bug which limits rate to 1Mbps, see bug https://bugs.launchpad.net/ubuntu/+source/linux-ubuntu-modules-2.6.24/+bug/190515
This bug will most likely not be fixed in the final release, so users need to build their rt2500-source if they want to use that card.

Revision history for this message

McFry (timo-latecrew) wrote on 2008-04-22:

It seems SET_MODULE_OWNER() is obsolete and was removed from the kernel. I could not find when it got removed, but in the 2.6.24 changelog there are entries where it got removed from other netdrivers, see http://www.kernel.org/pub/linux/kernel/v2.6/ChangeLog-2.6.24

Removing line 254 in rtmp_main.c the compilation succeeds. I've down little testing with the rt2500 driver (after blacklisting rt2500pci) and it seems to work fine now on hardy-rc. However, i am no kernel dev, and it only works for me as a workaround.

Revision history for this message

jan (jan-ubuntu-h-i-s) wrote on 2008-11-04:

Way to fix this: use hourly tarball from
http://rt2x00.serialmonkey.com/wiki/index.php/Downloads
that one compiles OK.

Who could re-create this package, based on the tarball ?

jan (jan-ubuntu-h-i-s) on 2008-11-04

Changed in rt2500:
status:	New → Confirmed

Revision history for this message

Mogens Dybæk Christensen (mdc) wrote on 2008-11-11:

rt2500-cvs-daily.tar.gz Edit (251.5 KiB, application/x-tar)

I can confirm, that jan's method works.

After upgrading from 7.10 to 8.04 I lost acces to the card. The new rt2500pci driver never worked with my WPA setup. This is kernel 2.6.24-21-generic.

Then I downloaded the from the same link, compiled, installed and blacklisted rt2500pci. After reboot my wireless network worked again with the old settings.

Since I am unsure how stable the tarball is, I will attach the one I used.

Revision history for this message

Thomas Hotz (thotz-deactivatedaccount) wrote on 2012-10-09:

Can you reproduce this problem in Ubuntu 10.04 LTS or above? Thank you!

Changed in rt2500 (Ubuntu):
status:	Confirmed → Incomplete

Thomas Hotz (thotz-deactivatedaccount) on 2013-05-02

Changed in rt2500 (Ubuntu):
status:	Incomplete → Confirmed

Revision history for this message

penalvch (penalvch) wrote on 2014-12-11:

Kjell Braden, thank you for reporting this bug to Ubuntu. Hardy Desktop reached EOL on May 12, 2011.
See this document for currently supported Ubuntu releases: https://wiki.ubuntu.com/Releases

Is this an issue in a supported release? If so, could you please execute the following command, as it will automatically gather debugging information, in a terminal:
apport-collect 183818

affects:	rt2500 (Ubuntu) → linux (Ubuntu)
Changed in linux (Ubuntu):
importance:	Undecided → Low
status:	Confirmed → Incomplete

Revision history for this message

Po-Hsu Lin (cypressyew) wrote on 2019-10-03:

Closing this bug with Won't fix as this kernel / release is no longer supported.
Please feel free to open a new bug report if you're still experiencing this on a newer release (Bionic 18.04.3 / Disco 19.04)
Thanks!