When you run SAKC in “turbo mode”, you get ONLY the modules that are loaded!!!
Is that really what you wanted? Since you appear to want to be spoon fed, the
answer is “NO”.
While running kernel 3.7.1, and in the kernel 3.8 source directory, run the
command ‘zcat /proc/config.gz > .config’ (there is a period before config) and
then “make -jX”, where X is the number of CPUs + 1. You will be asked some
questions when make starts. It will be OK to take the default answer, except
for the question about rtl8723. Answer “m” for that. When the build finishes,
then “sudo make modules_install install”. The scripts will do the right thing,
and there will be a new entry in the GRUB/GRUB2 menu.
As I am a volunteer on both this list and for adding the Realtek drivers to the
kernel, I am not at all pleased with your attitude, and if it continues, I will
ignore any further postings. Without my contributions, you would be forced to
get your driver from the Realtek web site, and you would need to figure out how
to patch it to build under kernel 3.7.
Thank you my friend, wifi works fine now after following your latest instructions for kernel-impaired newbies!
Again, many thanks for your contributions to the Suse project.
On 02/02/2013 04:36 PM, stuartn wrote:
>
> Thank you my friend, wifi works fine now after following your latest
> instructions for kernel-impaired newbies!
> Again, many thanks for your contributions to the Suse project.
You are welcome. Some things can be quite difficult and we try to make them as
easy as possible. For example, downloading the tarball for kernel 3.8-rc6 would
have taken a lot less disk space than the SAKC method did; however, you now have
the advantage of updating to 3.8-rc7 and future versions by the simple command
‘git pull’.
In the end the rtl8723ae driver has proven highly unreliable in many ways. After massive perseverance for a week and ultimate frustration, I have finally blacklisted it pending the release of a Suse o/s (Beta, RC or whatever) with the applicable kernel and firmware for the rtl8723ae. For now in Suse I am using an old usb wifi (rt2800usb), which I just plugged in and it worked straight away although physically it is a bit inconvenient. In Windows 8 (dual boot) I continue to smoothly use the rtl8723. The problems with the rtl8723ae are (a) it seems to constantly fall to low power with warnings issued (b) something seems to fall asleep inside, even when showing connected full power there is often no internal connection to applications (like Firefox) (c) sometimes waiting a few minutes can lead to a connection that lasts from one or two seconds to an hour or more (d) other devices connected to my router (eg an iPad and a wifi radio) are constantly interrupted when the rtl8723ae starts playing around with the connection. This behaviour doesn’t occur with other computers, the rt2800usb or when using the rtl8723ae with Windows 8 (e) I notice the rtl8723ae reports as connecting at 150Mb/s, which is obviously wrong. The rt2800usb connects at the usual 52Mb/s. If this cannot be sorted out for the final release of Suse 12.3 then my backup plan is to replace the Realtek hardware with something that does work. I appreciate the community’s difficulties in getting all wifi drivers to work and dearly hope it will not be too long before this long used device will behave properly.
On 02/07/2013 05:46 PM, stuartn wrote:
>
> In the end the rtl8723ae driver has proven highly unreliable in many
> ways. After massive perseverance for a week and ultimate frustration, I
> have finally blacklisted it pending the release of a Suse o/s (Beta, RC
> or whatever) with the applicable kernel and firmware for the rtl8723ae.
> For now in Suse I am using an old usb wifi (rt2800usb), which I just
> plugged in and it worked straight away although physically it is a bit
> inconvenient. In Windows 8 (dual boot) I continue to smoothly use the
> rtl8723. The problems with the rtl8723ae are (a) it seems to constantly
> fall to low power with warnings issued (b) something seems to fall
> asleep inside, even when showing connected full power there is often no
> internal connection to applications (like Firefox) (c) sometimes waiting
> a few minutes can lead to a connection that lasts from one or two
> seconds to an hour or more (d) other devices connected to my router (eg
> an iPad and a wifi radio) are constantly interrupted when the rtl8723ae
> starts playing around with the connection. This behaviour doesn’t occur
> with other computers, the rt2800usb or when using the rtl8723ae with
> Windows 8 (e) I notice the rtl8723ae reports as connecting at 150Mb/s,
> which is obviously wrong. The rt2800usb connects at the usual 52Mb/s. If
> this cannot be sorted out for the final release of Suse 12.3 then my
> backup plan is to replace the Realtek hardware with something that does
> work. I appreciate the community’s difficulties in getting all wifi
> drivers to work and dearly hope it will not be too long before this
> long used device will behave properly.
There is no wifi connection art 52 Mbps. Do you mean 54? In 802.11n, there can
be connections up to 300 Mbps. A connection at 150 Mbps is definitely one of them.
This device is not long used. It is a new one whose driver is undergoing many
revisions. Your experiences are not unusual for early adopters. In addition,
itis not at all clear what driver you were using. The in-kernel version is only
available with kernel 3.8. That kernel will not be available as a standard
version until 13.1.
I have no idea what is causing your difficulties; however, my testing of this
driver showed connections that were maintained for several days with no
interference with other devices. That condition was required (by me) before I
submitted the driver to the kernel.