Reply
Thread Tools
Posts: 72 | Thanked: 8 times | Joined on Jan 2007
#1
Ok, so I'm an idiot. Can anyone help me fix my N800

Was working on USB Networking. The instructions I found included a script by Michael Mlivoncic which loaded a module from /mnt/initfs/lib/modules/current. The problem was that current was a symbolic link to /lib/modules/2.6.18-omap1, which didn't exist. /mnt/initfs/lib/modules/2.6.18-omap1, however, DID exist.

I'm not going to try to justify what I did, but I deleted current and attempted to remake it using
Code:
# ln -s 2.6.18-omap1 current
ln: current: No space left on device
Now the device reboot loops in production mode. If I set the no-lifeguard-reset flag and enter R&D mode it boots, but no wifi. "lsmod" shows only g_file_storage and both SD Card slots work fine, but doesn't release to the computer when I plug in USB instead complaining "memory card is in use"

I removed the /etc/init.d/usbnet script even though it was never set to run automatically, but it still reboot loops in production mode.

Can I replace the current link without reflashing? If not, will it be the same as it was when I bought it after a reflash, does Nokia include extra "proprietary" stuff that isn't available in the maemo.org download?

I'd much rather NOT have to go through all of the setup process over again (installed a LOT of stuff) but I realize I may not have a choice.

Last edited by bobpaul; 2007-01-27 at 01:16. Reason: Solved
 
Posts: 72 | Thanked: 8 times | Joined on Jan 2007
#2
ok... I couldn't wait till morning for an answer... I used the Windows flasher from Nokia's website. Worked, even saw the backup on my sdcard and offered to restore. now, however, it won't update the package lis. It always fails, even if I disable all but the main Nokia repo...
 
Posts: 2,102 | Thanked: 1,309 times | Joined on Sep 2006
#3
Try using "apt-get update" (I think that's the correct command) and see whether you get any useful output on the command line.

I also thought that there was a log window in the package manager app (though may be wrong), does this show anything?


Si
 
Posts: 72 | Thanked: 8 times | Joined on Jan 2007
#4
Originally Posted by lardman View Post
I also thought that there was a log window in the package manager app (though may be wrong), does this show anything?
Oh, logs are handy! Application manager still thinks it should need privoxy, even though I uninstalled it and turned off the proxy in the network connections manager. The whole thing looks like this:
Code:
osso-application-installer 4.42, UI version 2
E: Failed to fetch http://catalogue.tableteer.nokia.com/certified/dists/bora/Release.gpg  Could not connect to 127.0.0.1:8118 (127.0.0.1). - connect (111 Co$
"apt-get update" refreshes the list, though, but it'd be nice to get the gui working again... weird. Gui installs apps fine, just won't refresh the list.
 
Posts: 72 | Thanked: 8 times | Joined on Jan 2007
#5
Alright. To fix this I saved a backup, then reflashed AGAIN. After reflashing I saved another backup of just "Settings" to a separate backup location. I copied both backups off my memory card to my PC. I noticed the backups are just *.zip files full of the directory structure and the files that are backed up.

After running a search, I found only file referencing the 127.0.0.1 was "/etc/osso-af-init/gconf-dir/system/osso/connectivity/IAP/Yosemite/%gconf.xml"
where Yosemite is the name of the access point I use to connect.

I tried manually editing the file, but that failed to work, so instead I replaced this file only with the one from my "fresh install" backup of settings.

In both files, the "proxytype" field was set to NONE, and this was expressed in the Connectivity GUI as the proxy options were unchecked. However, the entries defining the proxy still existed (also shown in the gui). It seems the "Application Installer" app still tries to use the proxy even if it is disabled. Removing the following entries will solve the problem:

Code:
        <entry name="ipv4_address" mtime="1169495695" type="string">
                <stringvalue>0.0.0.0</stringvalue>
        </entry>
        <entry name="ipv4_netmask" mtime="1169495695" type="string">
                <stringvalue>0.0.0.0</stringvalue>
        </entry>
        <entry name="ipv4_gateway" mtime="1169495695" type="string">
                <stringvalue>0.0.0.0</stringvalue>
        </entry>
        <entry name="ipv4_autodns" mtime="1169495695" type="bool" value="true">
        </entry>
        <entry name="ipv4_dns1" mtime="1169495695" type="string">
                <stringvalue>0.0.0.0</stringvalue>
        </entry>
        <entry name="ipv4_dns2" mtime="1169495695" type="string">
                <stringvalue>0.0.0.0</stringvalue>
        </entry>
        <entry name="proxy_http" mtime="1169495695" type="string">
                <stringvalue>127.0.0.1</stringvalue>
        </entry>
        <entry name="proxy_http_port" mtime="1169495695" type="int" value="8118">
        </entry>
        <entry name="proxy_https" mtime="1169495695" type="string">
                <stringvalue>127.0.0.1</stringvalue>
        </entry>
        <entry name="proxy_https_port" mtime="1169495695" type="int" value="8118">
        </entry>
        <entry name="proxy_ftp" mtime="1169495695" type="string">
                <stringvalue></stringvalue>
        </entry>
        <entry name="proxy_ftp_port" mtime="1169495695" type="int" value="0">
        </entry>
        <entry name="proxy_rtsp" mtime="1169495695" type="string">
                <stringvalue></stringvalue>
        </entry>
        <entry name="proxy_rtsp_port" mtime="1169495695" type="int" value="0">
        </entry>
        <entry name="omit_proxy" mtime="1169495695" type="list" ltype="string">
        </entry>
        <entry name="autoconf_url" mtime="1169495695" type="string">
                <stringvalue></stringvalue>
        </entry>
This is essentially the top half of the file AFTER <gconf> and BEFORE the <entry name="type... WLAN_INFRA...</entry>

I'm going to continue looking at this to see if this is only an issue when installing from backups, or if this can express itself more frequently, and if there is an easier work around.

Edit: While submitting bug 998, I noticed one can simply delete the offending access point and re-connecting to it.

Last edited by bobpaul; 2007-01-30 at 17:39.
 
Reply

Thread Tools

 
Forum Jump


All times are GMT. The time now is 15:35.