-
Notifications
You must be signed in to change notification settings - Fork 9
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Wifi not working #14
Comments
It works for me. So now you would have to report the iwconfig information of the network you're trying to connect to, otherwise 'Wifi not working' is too generic (as for other users it's working). Also, errors in dmesg |
Sorry for not replying. I can't get the iwconfig information since I don't have a linux device connected to wifi. I have the ifconfig information though. I have the dmesg as well |
Fiddled around with this a bit yesterday and can confirm that the whiite-ez-wifi-config script creates an invalid config - the interface is wlan1, not wlan0 (which can be confirmed with "ip link"). Run the script again and edit the /etc/network/interfaces and replace every "wlan0" with "wlan1", save and bring up the network with "ifup wlan1".
|
Thank you. Wifi now works for me. |
Does this happen only to users that also have a ethernet dongle? Or it's unrelated? |
It's unrelated, if I had one I would be using it. |
I also don't have an Ethernet dongle. |
Can confirm, it's also wlan1 for me. |
Exact same senario for me, fixed it by changing wlan0 to wlan1 in the script |
This issue is still happening without an ethernet dongle, is everyone using wlan1 or is it just some models? |
I have a question: I don't want to so change the encryption on my main network. So can I instead use my phone to host a networking with my mobile data (I don't know the English word) wich is open because I can't change the encryption type on my phone. So basicly how do I confic my interfaces file so that it works with open networks? |
i had to edit whiite-linux-ez-config to use wlan1 instead of wlan0 Is it just that wifi is slow (arround ~400KB when torrenting) we got 25 Mb plan (yes I know the difference between megabit and megabyte) or is it the wii that is slow too (I know we arent getting exactly 25Mb but still) (I know this part is unrelated to the github issue) |
yes, the Wii's wifi is horrible for today's standards. Compare it to the Old3DS which released 2011 and only can do about 700 KB/s. |
would the wii be that slow with ethernet adapter (I tried one and it only worked once (then would need to reboot to use it again)), I use my wii for torrenting, downloading youtube videos (must be an ocd thing or something, I know I have autism) |
I find the adapter slower than using WiFi but I've not tried using a newer kernel yet to see if that helps. |
Necro-bumping this but thanks!, indeed the interface had to be renamed to wlan1 and it works perfectly! thanks! So just change where it says |
Thx so much |
Hate to necropost, but i already did the fix with 'wlan1' instead of 'wlan0' and the wii does now connect to my router. But it can't do anything wifi related. 'apt-get update', 'wget ' ... etc. doesnt work. Any ideads whats causing this? |
the problem is that for today (May 2023) that distro is really old so apt-get keys are expired so it will just not work; wget should work though and basic internet connectivity but package management will not work. The bigger problem is that the wii is a PPC 32 bit architecture and pretty much the support is gone from the distros that used to support it. |
Thx for the quick answer lol. |
there was an attempt to make FreeBSD (or OpenBSD? cant remember) to boot linux in the wii; I havent checked it out with more detail, but I think that would be the last resource. if you find anything useful to do with it let us know! |
I think there is Linux distro out there focusing on ppc support. It is maintained by one guy though so idk how well it is doing. Also you probably would need to make the kernel modules compatible with the distro. Idk the detail as I'm not a distro dev. |
[ Upstream commit 9af31d6 ] There is an use-after-free problem reported by KASAN: ================================================================== BUG: KASAN: use-after-free in ubi_eba_copy_table+0x11f/0x1c0 [ubi] Read of size 8 at addr ffff888101eec008 by task ubirsvol/4735 CPU: 2 PID: 4735 Comm: ubirsvol Not tainted 6.1.0-rc1-00003-g84fa3304a7fc-dirty neagix#14 Hardware name: QEMU Standard PC (i440FX + PIIX, 1996), BIOS 1.14.0-1.fc33 04/01/2014 Call Trace: <TASK> dump_stack_lvl+0x34/0x44 print_report+0x171/0x472 kasan_report+0xad/0x130 ubi_eba_copy_table+0x11f/0x1c0 [ubi] ubi_resize_volume+0x4f9/0xbc0 [ubi] ubi_cdev_ioctl+0x701/0x1850 [ubi] __x64_sys_ioctl+0x11d/0x170 do_syscall_64+0x35/0x80 entry_SYSCALL_64_after_hwframe+0x46/0xb0 </TASK> When ubi_change_vtbl_record() returns an error in ubi_resize_volume(), "new_eba_tbl" will be freed on error handing path, but it is holded by "vol->eba_tbl" in ubi_eba_replace_table(). It means that the liftcycle of "vol->eba_tbl" and "vol" are different, so when resizing volume in next time, it causing an use-after-free fault. Fix it by not freeing "new_eba_tbl" after it replaced in ubi_eba_replace_table(), while will be freed in next volume resizing. Fixes: 801c135 ("UBI: Unsorted Block Images") Signed-off-by: Li Zetao <lizetao1@huawei.com> Reviewed-by: Zhihao Cheng <chengzhihao1@huawei.com> Signed-off-by: Richard Weinberger <richard@nod.at> Signed-off-by: Sasha Levin <sashal@kernel.org> Signed-off-by: Ulrich Hecht <uli+cip@fpond.eu>
Wifi doesn't work for me. The wifi setup script just reports it couldn't connect. Knowing how WPA2 doesn't work I made sure to change it to WPA. WEP isn't an option. The wifi works fine for the system menu. I'm using the newest stable release.
The text was updated successfully, but these errors were encountered: