Active Topics
-
List of well performing apps on Leste (35)
to Maemo 7 / Leste by smatkovi - 1 day, 6 hrs ago -
Porting apps to Leste (43)
to Maemo 7 / Leste by teroyk - 1 day, 13 hrs ago -
Sailfish OS for the Motorola Moto G7 Power (XT1955-5) - (ocean) (13)
to SailfishOS by edp17 - 2 days, 4 hrs ago -
Sailfish OS for the Samsung Galaxy Note 4 (SM-N910C) - (treltexx) (79)
to SailfishOS by edp17 - 2 days, 4 hrs ago -
U-Boot for Nokia RX-51 with BootMenu (updated version 2012.10-rc3-1) (843)
to Alternatives by Arno_11 - 2 days, 10 hrs ago -
Maemo repository (5)
to Community by dredlok706 - 5 days, 5 hrs ago -
Re-commissioning N9 in 2018 (127)
to MeeGo / Harmattan by smatkovi - 5 days, 8 hrs ago - more...
 |
|
2009-03-31
, 16:50
|
|
Posts: 844 |
Thanked: 521 times |
Joined on Jan 2009
@ UK southampton
|
#2
|
Try
"ifconfig wlan0 down"
then
"ifconfig wlan0 up"
You could also try
"iwlist wlan0 scan"
This will scan from the command line for available AP's.
"ifconfig wlan0 down"
then
"ifconfig wlan0 up"
You could also try
"iwlist wlan0 scan"
This will scan from the command line for available AP's.
|
|
2009-03-31
, 17:08
|
|
Posts: 1,224 |
Thanked: 1,763 times |
Joined on Jul 2007
|
#3
|
Are you sure the network is available? Did you try to reboot? Sometimes the network gets stuck in non working state.
Starting a particular connection is only possible for already setup connections. It works by sending commands to the connection manager, so it will probably not work if the connection manager does not work.
The command is:
dbus-send --type=method_call --system --dest=com.nokia.icd /com/nokia/icd com.nokia.icd.connect string:$1 uint32:0
where $1 is replaced by the id of the connection (find it by running the command:
gconftool-2 -R /system/osso/connectivity/IAP | less
Starting a particular connection is only possible for already setup connections. It works by sending commands to the connection manager, so it will probably not work if the connection manager does not work.
The command is:
dbus-send --type=method_call --system --dest=com.nokia.icd /com/nokia/icd com.nokia.icd.connect string:$1 uint32:0
where $1 is replaced by the id of the connection (find it by running the command:
gconftool-2 -R /system/osso/connectivity/IAP | less
 |
|
2009-03-31
, 19:11
|
|
Moderator |
Posts: 7,109 |
Thanked: 8,820 times |
Joined on Oct 2007
@ Vancouver, BC, Canada
|
#4
|
I remember this. This sounds a bit like what happened to me when trying to upgrade Diablo with apt-get. The install process (using apt-get instead of the Application Manager) runs out of space, and leaves the tablet in a broken state, with more packages to install, but unable to connect to the Internet to finish the upgrade.
But this might not be the same thing at all; I've never heard of anyone upgrading from Chinook to Diablo via the command line.
But this might not be the same thing at all; I've never heard of anyone upgrading from Chinook to Diablo via the command line.
__________________
qole.org --- twitter --- Easy Debian wiki page
Please don't send me a private message, post to the appropriate thread.
Thank you all for your donations!
qole.org --- twitter --- Easy Debian wiki page
Please don't send me a private message, post to the appropriate thread.
Thank you all for your donations!
|
|
2009-04-01
, 01:32
|
|
Posts: 5 |
Thanked: 0 times |
Joined on Mar 2009
|
#5
|
Originally Posted by casper27
This brought up wlan0, but did not associate an IP address with it
Try
"ifconfig wlan0 down"
then
"ifconfig wlan0 up"
Originally Posted by casper27
The "iwlist" is not found.
You could also try
"iwlist wlan0 scan"
This will scan from the command line for available AP's.
[QUOTE=Matan;276108]Are you sure the network is available?[QUOTE]yes.
Did you try to reboot? Sometimes the network gets stuck in non working state.
Starting a particular connection is only possible for already setup connections. It works by sending commands to the connection manager, so it will probably not work if the connection manager does not work.
The command is:
dbus-send --type=method_call --system --dest=com.nokia.icd /com/nokia/icd com.nokia.icd.connect string:$1 uint32:0
where $1 is replaced by the id of the connection
(find it by running the command:
gconftool-2 -R /system/osso/connectivity/IAP | less
Originally Posted by qole
Well, I had to run "dpkg --configure -a" to complete things, but there was only 2 unresolved packages ("osso-bookmark-user-rx44" and "initfs-flasher"). These don't seem relevant to networking, however.
I remember this. This sounds a bit like what happened to me when trying to upgrade Diablo with apt-get. The install process (using apt-get instead of the Application Manager) runs out of space, and leaves the tablet in a broken state, with more packages to install, but unable to connect to the Internet to finish the upgrade.
But this might not be the same thing at all; I've never heard of anyone upgrading from Chinook to Diablo via the command line.
I seem to be able to connect to the USB (not the network connection). So, I suppose, if worse comes to worse, I could flash it.
I think my next step is going to be to create a "/etc/network/interfaces" entry specifically for my wireless AP so that the above "ifconfig" might work.
|
|
2009-04-01
, 02:03
|
|
Moderator |
Posts: 7,109 |
Thanked: 8,820 times |
Joined on Oct 2007
@ Vancouver, BC, Canada
|
#6
|
I like you, robertb.
You're hardcore.
You're hardcore.
__________________
qole.org --- twitter --- Easy Debian wiki page
Please don't send me a private message, post to the appropriate thread.
Thank you all for your donations!
qole.org --- twitter --- Easy Debian wiki page
Please don't send me a private message, post to the appropriate thread.
Thank you all for your donations!
|
|
2009-04-01
, 09:25
|
|
Posts: 1,224 |
Thanked: 1,763 times |
Joined on Jul 2007
|
#7
|
Originally Posted by robertb
Of course it is relevant to networking. initfs is where the wireless driver is (along with a few programs that are also important for wireless network to work). You now have incompatible kernel and initfs, so it is surprising that your system actually boots.
Well, I had to run "dpkg --configure -a" to complete things, but there was only 2 unresolved packages ("osso-bookmark-user-rx44" and "initfs-flasher"). These don't seem relevant to networking, however.
If your post is an April fool's post, please ignore my message.
Surprisingly, it didn't completely break, but there is one big problem: I can no longer connect to a network. (It sits there saying "Searching" and never finds my connection.)
Does anyone know how to start a particular connection via the command line (from OSSO xterm)? Then, maybe I could have a fighting chance of getting this working again.
Thanks.