I installed gentoo on my old wii, so I can use it as a shitty PC, the problem is that the networkdoesnt start up, I changed /etc/wpa_supplicant.conf with the proper settings for my network, but I get this error from OpenRC:
INSTALL GENTOO (wii edition)
Based OP
Maybe try connman and/or iwd instead.
How do I emerge iwd without internet?
Some comands are stupid because I confuse between keyboards.
What's netmount?
Use wpa_cli
The switch can run linux, right?
Wonder if it could also run gentoo
How do you know the ramdisk you're booted into even has the right drivers? Does the Wii have Ethernet?
wpa_supplicant, wpa_passphrase and dhcpcd
>Does the Wii have Ethernet?
No, it doesn't
My network interfaces are wlan0 and lo.
You're probably fucked then unless you have a USB wifi dongle and the drivers in linux to use it (similar to what one might do with a raspberry pi)
The NIC is probably running proprietary drivers, you might need to write your own.
It's associated? Is the password correct? Can you run 'route' or 'ip a' or something?
Does your output of "ifconfig" show anything at all that starts with "wlp"?
I had this problem before, and I just ended up going aroung the problem by installing NetworkManager. I booted back into the USB, mounted the root partition in /mnt/gentoo, and then chrooted into it. You will probably need to run "ifconfig" and then "net-setup " in the installation again. Then, assuming that your installation media found anything other than wlan0 and lo, install NetworkManager. I used the use flags "-dhclient dhcpcd", rebooted, and then followed the OpenRC configuration on the Gentoo wiki page for NetworkManager and rebooted again.
You can then log in as root and run "nmtui" to setup NetworkManager, or if you are using a regular user, run "sudo nmtui" (will have needed to installed "sudo" beforehand).
how did you install gentoo or wpa_supplicant in the first place w/o internet?
anyway, you may have to install sys-kernel/linux-firmware if it's not installed already
after that, make sure all networking services are kill and try it manually
wpa_supplicant -i wlan0 -c /etc/wpa_supplicant.conf
if it says CTRL-EVENT-CONNECTED, it's a success
you can ctrl+z and type bg to put the process in the background
then start your dhcp client like
dhclient wlan0 or dhcpcd wlan0, depending on which one you have
ping gentoo.org and see if it works
You should've made a Youtube video of this, that's pretty cool
You need to start dhcpcd as well as wpa_supplicant.
Check both of their man pages; there's a setting on one of them (wpa_supplicant IIRC) that allows it to get the interface details from the other automatically.
Also this script works.
#!/bin/bash
# Ensure you set these variables to the right values
export WIFI_INTERFACE=wlan0
export WIFI_CONFIG_FILE=/path/to/wpa_supplicant.conf
export WAIT_TIME_SEC=5
# Connect to wifi using wpa_supplicant
killall wpa_supplicant
wpa_supplicant -Dnl80211,wext -i$WIFI_INTERFACE -c$WIFI_CONFIG_FILE -B
sleep $WAIT_TIME_SEC
# Lease an IP address with dhcpcd
dhcpcd --waitip=4 -4 -N $WIFI_INTERFACE
sleep $WAIT_TIME_SEC
There's an official USB to ethernet adapter for it.
Probably handled by the IOS.
Well, you've obviously got some way to transfer files onto this thing. I haven't used gentoo in ages but I'm pretty sure there's an option to pre-download the tarballs for a package and all its deps, so you can transfer them to another machine via sneakernet and build the packages there
It came preinstalled in the stage i used
Of course I do, conecting the SD card to my computer.
Wired internet would be the option, but I recall the Wii didn't have that.
Use emerge -f or equivalent elsewhere and then just drop the packages in by microSD or USB.
(cont'd)
BTW you can of course also see what emerge would resolve to on the Wii and then download the packages off any Gentoo mirror on another machine. Or any variant of this (for example, dump the URLs to a file that you then use). As you prefer.
One more thing that came to mind, if you somehow never got WLAN working directly, you could use these SD WLAN network share cards to push files on the contained microSD. But that may not be necessary.
Anothe tty.
Did it working?
ifconfig -a ?
It seems the WFC is there. Output of "ip a"?
The problem is I have to download the packages from a x86_64 system onto a PPC system, Will it be a problem them?
Also, yes I'm using gentoo on my PC, but a much newer version.
Good.
You still need dhcp but maybe ip works
"ping 89.16.167.134" (www-bytemark-v4v6.gentoo.org)
It was me who killed wlan0 but only to do what the other annon told me.
> Will it be a problem them?
Not on the packages, but maybe it resolves to a different version, so I guess you first run something like this on the target machine:
emerge -fvp iwd connman dhcpcd
or
emerge -fvp iwd connman dhcpcd > packages.txt
Surely not the most clever variant ever of this, but it should work.
You connected fine in that first screenshot.
Just need to get dhcp request working to configure your ip/mask/route/dns... or do it manually...
Maybe you have busybox... try
busybox udhcpc --help
What's the command to download the packages' source from my computer and how do I do to install it them back on the wii?
>8 year old tree
You can abandon that tactic right now, those packages won't be in the repos.
See if you have busybox, it will let you configure your network just fine.
good, your wifi works
you just need to install dhcpcd
Download the URLs with your browser, wget, whatever way you like. The files then go into /usr/portage/distfiles/ on the wii.
BUT is right, if you had busybox that might come with a dhcp client and you might have a connection then even if the other two obvious clients are somehow absent? Try that first.
Need two -, its --help not -help
I concur with user. Didn't see that before but your portage tree is ancient as fuck for some reason; the usual method won't work.
What the fuck was the dhcp client they expected to use back then, I wonder?
Somehow | less doesn't work fine.
You can try shift+pgup to scroll up in the framebuffer.
Or it may be easier to just use udhcp.busybox.net
I've never done such thing before, can you intruduce me a bit onto what to type?
They had dhcp in the stages back then, the guy that made this wii image probably just wanted to make it as small as possible, i.e. wpa_supplicant and busybox and nothing else for network shit.
Its a readme, pretty straight forward, the -i option lets you specify your interface, in this case its going to be wlan0
I haven't used it before so I figured it would be quicker for you to just read it.
Might just need to type busybox udhcpc -i wlan0
(after you connect with wpa_supplicant)
I would recommend you try a different distro but I seriously doubt any other ones would even work on it so good luck.
You should probably look in to if there is even a working xorg driver for the wii because if there isn't this is going to be kind of useless other than for messing around.
You were already connected, just type
(wpa_supplicant -i wlan0 -c /etc/wpa_supplicant.conf&)
If it is still not working, it may be dhcpcd
can't you put dhcpcd onto s usb stick or something and install it from there?
Done?
can you ping gentoo.org?
Looks like it worked, if you run ipconfig -a it should show an ip address for your wlan0 interface.
Try to ping google, if it doesn't work you need to create an /etc/resolv.conf with the line nameserver 192.168.1.1
Or whatever your default dns server is.
No.
so
echo "nameserver 192.168.1.1" > /etc/resolv.conf
also going to leave, tired and you probably are far enough to get it working with this
I didn't actually see that the nameserver or router necessarily is 192.168.1.1.
That's a google public nameserver, it should still work but of course 8.8.8.8 needs to be reachable.
>8.8.8.8 needs to be reachable
well is it?
try ping 8.8.8.8
?
Check your other computer or smartphone to see if that's actually running a nameserver.
It's a typical configuration for home WLAN AP / router things, but not at all the only possible configuration.
is wpa_supplicant running in the background?
I guest yes.
doubt
How to check?
Also, found that:
wiitoo.sourceforge.net
And that:
quadpoint.org
pgrep wpa
if you don't get a number, it means it's not running
if it's not running, start it like so
wpa_supplicant -i wlan0 -c /etc/wpa_supplicant.conf -B
-B at the end there will make it start in the background
cmon op fix it
I wanna install it on mine as well!!!!
I get numbers.
there should only be one number
you've spawned it multiple times
killall wpa_supplicant
or kill -9 2564; kill -9 2571
then run
wpa_supplicant -i wlan0 -c /etc/wpa_supplicant.conf -B
and try to ping 8.8.8.8
and ping gentoo.org or something after that
ok, try ping
Try it yourselv, let's see if it works for you.
Shit. I really wonder what is going on here.
Maybe dmesg complains about something? Or maybe "route" makes no sense?
Any ideas?
Well, is 192.168.1.1 ping-able as the AP, from the rest of the network? Because that would then be basically no connection right to the AP.
Ya, shit. It somehow didn't, uh, connect properly. [This is definitely exact jargon].
Do you have iwconfig? Maybe you could run wpa_supplicant with -dd or -d to get more output?
If you want to manually update portage tree you could download the portage-latest.tar.xz snapshot, move that to wii and extract and replace your current /usr/portage dir with that.
Updating any packages however requires the source files themselves and they are by default stored in /usr/portage/distfiles (might be a good idea to move that directory outside with DISTDIR="/usr/portage_distfiles" in make.conf). Those files can be get with your desktop ("emerge -e --fetchonly @system dhcpcd wpa_supplicant" should get more than enough to get everything up to date) and manually moved over
I'll caution that if this ancient monstrosity is as old as I think it is, you might get a Portage tree where the ebuilds contained have a newer EAPI than the installed portage version supports.
There was some way to deal with that, but I don't remember it right now.
>portage-latest.tar.xz
In the mirrors, which dir is it?
>portage-latest.tar.xz
Is it this one?
ftp.rnl.tecnico.ulisboa.pt
releases/snapshots/current but I would take this caution seriously. The first upgrade to make would be portage itself but even the oldest version in the current tree uses EAPI=5 which is from 2012 and if the "8 years ago" is accurate then the portage installed currently on wii couldn't handle it
Just got through updating to 4.19.23 today and remembered this time to protect the sources so they don't get removed by a depclean. Since I last upgraded the kernel and forgot to do that, all new package upgrades and stuff were complaining about it. Slowly learning and getting more to grips with it.
I really should spend some effort to make my gui look better because mine looks like shit. Some of the screens people post look pretty nice.
>NetworkManager
Should I try anyway?
This looked really promising. Can you post ifconfig after that and log onto your wifi-router to see if also sees the wii?
>Should I try anyway?
I would read the net init scripts to figure out if they do anything else to set the connections. You are manually invoking both wpa_supplicant and bb dhcpc after all
I think that wlan0 line should show adress the inet addr. Is it possible that the udhcpc is just self selecting the .1.132? or if it is correctly getting the address then some route setting needs to be done after the fact
So?
step one check if this file exists /lib/netifrc/sh/udhcpc-hook.sh? if it does then kill whatever udhcpc is running now and try with this instead:
busybox udhcpc -i wlan0 -s /lib/netifrc/sh/udhcpc-hook.sh -p /run/udhcpc-wlan0.pid -n
?
Well what? ifconfig && ping 4channel.org to see if things work now
umm? you do have the wpa_supplicant running first like you did earlier in the thread, right? so the whole process to manually setup networking would be:
# wpa_supplicant -B -c /etc/wpa_supplicant.conf -i wlan0
# busybox udhcpc -i wlan0 -s /lib/netifrc/sh/udhcpc-hook.sh -p /run/udhcpc-wlan0.pid -n