Comments on: Followup on the Belkin F5D8053 and Ubuntu http://blog.delgurth.com/2008/08/17/followup-on-the-belkin-f5d8053-and-ubuntu/ If only a day had 48 hours... Tue, 06 Jan 2009 13:49:10 +0000 http://wordpress.org/?v=2.5.1 By: DelGurth http://blog.delgurth.com/2008/08/17/followup-on-the-belkin-f5d8053-and-ubuntu/#comment-1954 DelGurth Mon, 10 Nov 2008 09:38:28 +0000 http://blog.delgurth.com/?p=45#comment-1954 <blockquote>Brett: Uh, what directory is include/rt2870.h in?</blockquote> <p>If you download the latest version of the driver at <a href="http://www.ralinktech.com.tw/data/drivers/2008_0925_RT2870_Linux_STA_v1.4.0.0.tar.bz2" rel="nofollow">the ralink linux drivers section</a> and extract it, you will get a directory called:</p> <pre>2008_0925_RT2870_Linux_STA_v1.4.0.0</pre>. The include/rt2870.h (and all other paths) are relative from that directory. This latest version still didn't have the Belkin USB id in it, unfortunately.

Brett: Uh, what directory is include/rt2870.h in?

If you download the latest version of the driver at the ralink linux drivers section and extract it, you will get a directory called:

2008_0925_RT2870_Linux_STA_v1.4.0.0

. The include/rt2870.h (and all other paths) are relative from that directory. This latest version still didn’t have the Belkin USB id in it, unfortunately.

]]> By: Brett http://blog.delgurth.com/2008/08/17/followup-on-the-belkin-f5d8053-and-ubuntu/#comment-1941 Brett Sun, 09 Nov 2008 18:01:14 +0000 http://blog.delgurth.com/?p=45#comment-1941 Uh, what directory is include/rt2870.h in? Uh, what directory is include/rt2870.h in?

]]> By: Trying to get the Belkin F5D8053 v3 to work on Ubuntu Hardy without ndiswrapper » It’s all in a day’s work http://blog.delgurth.com/2008/08/17/followup-on-the-belkin-f5d8053-and-ubuntu/#comment-397 Trying to get the Belkin F5D8053 v3 to work on Ubuntu Hardy without ndiswrapper » It’s all in a day’s work Sun, 17 Aug 2008 16:43:01 +0000 http://blog.delgurth.com/?p=45#comment-397 [...] Update: I got it working now, see my new post about it. [...] [...] Update: I got it working now, see my new post about it. [...]

]]>