[kentiger]

many thanks for your comments, i need to check with the guy
here is the patch link , you can also have a look on it...many thanks
https://www.mediafire.com/?sagwp77nk81ik4t

now i have got the patch , need to change wext into nl80211 inside the patch also, but the guy who made the patch does not know how to compile it, shall i send you the patch, and then you can compile it and have one new upgrading file.
tks again.

Let me start with; How on earth can someone make a patch, but don't know how to compile

Secondly; the 2.6.34.x kernel does not support nl80211. The wifi driver has some >2.6.37 <2.6.39 support if needed, but you really should go up to 2.6.39. As we are using 2.6.34.14 (or 15), patching the driver to nl80211 is not doing you any good.

Actually, we stepped away from the in-xbmc way of configuring the network and instead, implemented the more "normal" linux way using NetworkManager (wext based) and the a bit older NetworkManager xbmc plugin.

Anyway, if it is a ETV, it should just work on the same CUS driver.

[dhead]

@j1nx

Did Amlogic released 2.6.39 ? I can only find 2.6.34.14.

I'm building now an update image for f16ref based on Corey's Buildroot tree, will see how this goes.

[kentiger]

latest is 3.0.1, even more higher....

@j1nx

Did Amlogic released 2.6.39 ? I can only find 2.6.34.14.

I'm building now an update image for f16ref based on Corey's Buildroot tree, will see how this goes.

---

@dhead
sorry, not note for M3 board,

[j1nx]

many thanks for your comments, i need to check with the guy
here is the patch link , you can also have a look on it...many thanks
https://www.mediafire.com/?b4aj5wjf57w6ac2

Didn't download it, but the filename says enough.


@dhead

No Amlogic only released 2.6.34 and 3.0.8

3.0.8 originally was released for the MX and in the early days it contained M3 code. A little bird told me, a newer 3.0.8 with the proper M3 code is comming.

Anyway, doesn't change the fact that 2.6.34 on WEXT is doing what it should be doing. It still remains an embedded realtek chip, but with proper positioning and not to far of the router should give the needed performance for HD streaming.

[kentiger]

today tried tlbb version 1.1.2, failed, can not show wifi choices

[dhead]

@j1nx

Are the RTL8XXX_CU drivers broken on your develop branch of buildroot-linux-kernel-m3 ?
The Network Manager addon doesn't show any w-hotspots.
With the kernel used in your last beta I do see the hotspots (but failed to connect).

For both I'm using Corey's Buildroot tree.

http://xbmclogs.com/show.php?id=142336

[j1nx]

No, use the CU driver within the TLBB firmware as well.

Is networkmanager running properly?

[dhead]

I haven't checked if networkmanager running but when trying "# ip link set wlan0 up" I'm getting

ADDRCONF(NETDEV_UP): wlan0: link is not ready

so I guessed something is wrong with the drivers.

[dhead]

I've tried again, now building from scratch.
No change at all, when booting I'm getting the same message on dmesg

ADDRCONF(NETDEV_UP): wlan0: link is not ready

Network manager does works

[root@M3 /root]# nmcli dev
DEVICE TYPE STATE
wlan0 802-11-wireless unavailable

[root@M3 /root]# nmcli nm
RUNNING STATE WIFI-HARDWARE WIFI WWAN-HARDWARE WWAN
running disconnected enabled enabled enabled disabled

I'll will look a little bit more on TLBB configs.
Here are mine:
Kernel: https://github.com/MakakLabs/buildroot-l..._defconfig
Buildroot (needs some adjustments): https://github.com/MakakLabs/buildroot-m..._defconfig

@j1nx are you using now buildroot-M3-MX repository with TLBB-M3 ?

[j1nx]

@j1nx are you using now buildroot-M3-MX repository with TLBB-M3 ?

Yes, this is the current buildroot we use;
https://github.com/J1nx-Hackable-Gadgets...root-M3-MX

Easiest is to take this config and migrate to a GBox one;
https://github.com/J1nx-Hackable-Gadgets..._defconfig

Most important to change are;

For obvious reasons.
BR2_TARGET_GENERIC_HOSTNAME="TLBB"
BR2_TARGET_GENERIC_ISSUE="Welcome to The Little Black Box - XBMC/Linux"

The overlay, maybe corey's is more general at this point.
BR2_ROOTFS_OVERLAY="board/amlogic/TLBB-M3/overlay"
BR2_PACKAGE_BUSYBOX_CONFIG="board/amlogic/TLBB-M3/busybox.config"

The kernel.
BR2_LINUX_KERNEL_CUSTOM_GIT=y
BR2_LINUX_KERNEL_CUSTOM_REPO_URL="https://github.com/J1nx-Hackable-Gadgets/buildroot-linux-kernel-m3.git"
BR2_LINUX_KERNEL_CUSTOM_REPO_VERSION="1b48458d3e670a7d2f2cd968e9ae7387887469a8"
BR2_LINUX_KERNEL_DEFCONFIG="meson_reff16_tlbb"

To change the splashes, advancedsettings, remotes etc.
BR2_XBMC_ADV_SETTINGS="tlbb_advancedsettings"
BR2_XBMC_GUI_SETTINGS="tlbb_guisettings"
BR2_XBMC_DEFAULT_SKIN="tlbb"
BR2_XBMC_SPLASH="tlbb_splash"
BR2_XBMC_STARTING_FB="tlbb_starting"
BR2_XBMC_STOPPING_FB="tlbb_stopping"
BR2_XBMC_COMPLETE_FB="tlbb_complete"
BR2_PACKAGE_TLBB=y (<- You can remove this skin)

BR2_TARGET_ROOTFS_RECOVERY_AML_UPDATE_ZIP_NAME_CUSTOM_STRING="M3_LINUX_TLBB-M3"
BR2_TARGET_ROOTFS_RECOVERY_AML_LOGO="fs/recovery_aml/logos/tlbb_logo.img"
BR2_TARGET_ROOTFS_RECOVERY_RECOVERY_IMG="board/amlogic/TLBB-M3/recovery.img" ( <- You probably want to remove this)

[Jackhari]

I've tried again, now building from scratch.
No change at all, when booting I'm getting the same message on dmesg

ADDRCONF(NETDEV_UP): wlan0: link is not ready

Network manager does works

[root@M3 /root]# nmcli dev
DEVICE TYPE STATE
wlan0 802-11-wireless unavailable

[root@M3 /root]# nmcli nm
RUNNING STATE WIFI-HARDWARE WIFI WWAN-HARDWARE WWAN
running disconnected enabled enabled enabled disabled

I'll will look a little bit more on TLBB configs.
Here are mine:
Kernel: https://github.com/MakakLabs/buildroot-l..._defconfig
Buildroot (needs some adjustments): https://github.com/MakakLabs/buildroot-m..._defconfig

@j1nx are you using now buildroot-M3-MX repository with TLBB-M3 ?

Hi mate,
I have same m3 box as urs with new wifi module and can't use wifi using j1nx linux build.
Can u please provide me the build once u are successful.appreciate a lot.
Cheers

[kentiger]

correct patch
https://www.mediafire.com/?sagwp77nk81ik4t

[dhead]

After setting my kernel defconfig to match almost exactly to TLBB-M3 I still got no result.
Reverting the RTL8XXX_CU drivers to tag 0.2.1 got me a result, I can see the w-hotspot via Network Manager addon but can't connect.

I will play a little with the drivers and try to find the culprit (there aren't too many).

@j1nx can it be the the issue may be related to the board file board-m3-reff16.c ? (I already reverted to board-m3-reff16-gbox.c).

[dhead]

Alright, it's definitely the CONFIG_IOCTL_CFG80211 fault.
Now I need to figure out why it's working with TLBB-M3, maybe it's related to the board*.c files.

[Jackhari]

Alright, it's definitely the CONFIG_IOCTL_CFG80211 fault.
Now I need to figure out why it's working with TLBB-M3, maybe it's related to the board*.c files.

Hi mate,
Do u have a test build that u want me to test in my m3 box with new wifi?
Cheers