kudos1uk | # 61 | 2008-07-04, 17:53 | Report

Count me in, it no longer works for me in Diablo, as the rest of you no "wired" appearing.

I'm pinning my hopes on jolouis fixing the scripts.

jolouis | # 62 | 2008-07-05, 01:37 | Report

Hey All,

Okay well I stayed away from upgrading to Diablo as I've been busy and I always like to give everyone a few months to get the bugs sorted before jumping over, but thanks to Benson's info I'll see what I can do to work around this and get things working again; keep an eye out for updated information soon.

Thanks!
-Rob

xopher_mc | # 63 | 2008-08-08, 23:38 | Report

Just wanted to see if there was any news on this?

Looking at it myself, I wondered if \system\osso\connectivity\network_type needs a Dummy entry.

Is anyone running chinook who can check to see if such an entry exists and if so what it contains.

Thanks!

jolouis | # 64 | 2008-08-11, 16:13 | Report

The problem is that Nokia changed the wireless connectivity manager and they goofed and left out the "dummy" option... it's there, but it won't display in the list of available connections. There's an open bug for it but eta for fixing is unknown last time I checked. I've been meaning to get working on a fix for it but have not had time yet; so far I'm trying to figure out if it's possible to just gconf/some kind of CLI to actually manually force a connection instead of having to choose it from the connection manager, since that would solve it an eliminate the need for selecting "wired" all the time anyways...

-Rob

xopher_mc | # 65 | 2008-08-11, 18:56 | Report

I wonder what the system does to check that it has a wifi connection? And how you would give it a false result.

At least I can still ssh using the usb networking!

I know this shows how little I know, but the \system\osso\connectivity\network_type\ entries all point to the kernel modules to use. Could one not add the dummy module and then add an entry in gconf (copying from chinook)? Or is it a problem with how the network manager has been compiled?

hallgreng | # 66 | 2008-08-13, 06:48 | Report

i did a little check and this works for me in diablo running the update that came out today:

1. go into host mode
2. connect usb nic, wait for it to finish complaining
3. put/get ip address on eth0:
#udhcpd eth0
4. UNLOAD THE WLAN MODULE:
#rmmod cx3110x
5. open web browser, it works

i dont know if the gconftool...DUMMY command is necessary for this to work, but i did do that prior to all of this.

the wlan icon blinks endlessly, but everything seems to work fine.

i cant seem to reload the cx3110 module with modprobe. any way i try, it complains about being unable to parse modules.dep, which doesnt seem to exist on my n810. because of this, to get wlan back i simply reboot -a small price to pay =]

fanoush | # 67 | 2008-08-13, 07:36 | Report

that's not needed, if you want to save power run
# ifconfig wlan0 down

This worked before latest update and is known workaround since the time they broke dummy connections last time (in OS2007)

qwerty12 | # 68 | 2008-08-13, 08:23 | Report

You have to use insmod. If you want to modprobe, run depmod to generate the modules.dep (sse2.net/depmod)

(Thanks jott!)

fanoush | # 69 | 2008-08-13, 10:13 | Report

And then don't forget to run
# chroot /mnt/initfs wlan-cal
to reload wi-fi chip with MAC address and other stuff. ifconfig down is less 'destructive' than rmmod cx3110x

xopher_mc | # 70 | 2008-08-13, 23:54 | Report

ok,

Tried the ifconfig wlan0 down. It didn't seem to work.

But I think I've stumbled upon the neatest solution. The way to solve it is to stop the icd2 service. When this is stopped it stop asking for connection and just uses the usb one. Seems neater then unloading modules too.

to disable the service as root type:

/etc/init.d/icd2 stop

to start again when you've finished

/etc/init.d/icd2 start

---

Last edited by xopher_mc; 2008-08-13 at 23:57.