I just got done with a fresh install of Gentoo using a stage4 tarball, and after the very first reboot, eth0 thinks it's a wireless interface. When net.eth0 is called, it appears to be trying to look for ESSID settings, and fails with a "Check your conf.d/wireless settings" of sorts.

I've installed Gentoo on my PS3 in the past without ever having this issue. Since the setup is very straightforward, I'm positive I didn't botch anything up there. I used the tutorial located here: http://ps3wiki.qj.net/index.php/Gentoo_-_The_next_step , and aside from copying /etc/resolv.conf, toying with the network isn't even part of the installation.

I'm trying to work remotely over SSH, but SSHD calls net.eth0, which fails because.. it thinks it's now wireless (it's the normal wired ethernet port).

I had to rc-update del net.eth0 default for now so I can at least get SSH up and running, but does anyone have any idea why this is happening now? Was the Stage4 tarball changed?

My conf.d/net file is empty (even tried config_eth0 = { "dhcp" } with no luck), and other than that, I'm really not sure why the system would now think it's wireless. I know there was a wireless patch from Sony last week, but unsure whether or not this is related. Just find it odd that it always worked before, and now out of the blue it think it's wireless.

I can get an IP just fine from my network if I manually call "dhcpcd eth0", so it works in that aspect.

I've also read that the eth0 port, if you're using the new kernel that supports the wifi, is both wired and wireless, so I'm assuming this is the issue.

I just got done with a fresh install of Gentoo using a stage4 tarball, and after the very first reboot, eth0 thinks it's a wireless interface. When net.eth0 is called, it appears to be trying to look for ESSID settings, and fails with a "Check your conf.d/wireless settings" of sorts.

I've installed Gentoo on my PS3 in the past without ever having this issue. Since the setup is very straightforward, I'm positive I didn't botch anything up there. I used the tutorial located here: http://ps3wiki.qj.net/index.php/Gentoo_-_The_next_step , and aside from copying /etc/resolv.conf, toying with the network isn't even part of the installation.

I'm trying to work remotely over SSH, but SSHD calls net.eth0, which fails because.. it thinks it's now wireless (it's the normal wired ethernet port).

I had to rc-update del net.eth0 default for now so I can at least get SSH up and running, but does anyone have any idea why this is happening now? Was the Stage4 tarball changed?

My conf.d/net file is empty (even tried config_eth0 = { "dhcp" } with no luck), and other than that, I'm really not sure why the system would now think it's wireless. I know there was a wireless patch from Sony last week, but unsure whether or not this is related. Just find it odd that it always worked before, and now out of the blue it think it's wireless.

I can get an IP just fine from my network if I manually call "dhcpcd eth0", so it works in that aspect.

I've also read that the eth0 port, if you're using the new kernel that supports the wifi, is both wired and wireless, so I'm assuming this is the issue.

Any help is greatly appreciated!

Yeah, this is going to be a sticky problem to work through. I created those stages you used and added the wireless driver into it (compiled, not as a module). The problem is that the wired and wireless share the same ethX device. So I think this futzes up the network init scripts.

For the interim, you could add a call to dhcpcd -d eth0 to /etc/conf.d/local.start and see if that temporarily resolves the problems. Give me a day or two to see what I can figure out. Also, if you could join us on IRC, it would help so we can debug. In my case, it works just fine. Others, not so._________________-->
rangerpb
<--

I just finished a stage 4 32ul install of Gentoo. I think that i the have the same problem as wonky but i am not sure. I know it sound funny but i traveling with a only a previous knowledge on dos6 makes it hard to identify what the problem is. I can't emerge anything or ping anything. And i have tried {modules=( "!iwconfig" "!wpa_supplicant" "ifconfig" )"}
in /etc /conf.d/net with out any luck.

Now there is no error but still can't get network access. So I have loaded the live cd (where is can access internet and emerge) and run emerger --update --deep -newuse world. Make sure everything is up to date.

Ok Soz about being Newbiee-lishious. I don't know how to identify a server name problem. I have net access when using livecd. Not when I boot normally
My boot up screen is
Starting eth0
Loading networking modules for eth0
For WPA suport (wpa_supplicant) support, emerge net-wireless/wpa_supplicant

After rebooting I did run into the same issue as wonky99 ending up with a dead eth0 interface confusing it with a wireless interface. After adding modules=( "!iwconfig" "!wpa_supplicant" "ifconfig" ) in /etc/cionf.d/net all works fine.