headers
Ming Zhang | 1 Apr 2006 02:51
Picon
Favicon

Re: Core-iSCSi/Nokia770 bits

On Fri, 2006-03-31 at 14:37 -0800, Nicholas A. Bellinger wrote:
> Greetings Ming!
> 
> On Thu, 2006-03-30 at 14:29 -0500, ming.zhang.china <at> gmail.com wrote:
> > 
> > ps, u work on that Nokia 770 is cool! Though I have no extra money to
> > buy one and play with. ;)
> > 
> > ps2, I saw u release note claim iSNS support. What is the status?
> > completed?
> > 

i checked out u latest code and saw that. nice work.

> 
> core-iscsi-tools comes with iSNS code/scripts that allow for automatic
> registration/deregistration as well as listing nodes within the
> discovery domain the initiator node is a member of, as well as listing
> only target nodes + network portals that is useful for an initiator
> node.
> 
> Some of the scripting work that is left related to iSNS involves
> presenting a list of target nodes + network portals returned via iSNS,
> allowing the SAN admin of establishing sessions into these discovered
> nodes along with authentication information, comparing the discovered
> node list form iSNS against the current active or configuration defined
> with the option to make iSNS discovery data persistent.
> 
> In the context of small devices like the Nokia 770, I imagine the iSNS
> information to appear much like wireless information appears:  A list of
(Continue reading)

Permalink | Reply | 0 comments |
headers
Teemu Harju | 1 Apr 2006 05:44
Picon
Gravatar

Re: WLAN and bluetooth modem on at the same time?

I've tried both 'nat' and 'NAT' and the result is the same.

I checked the kernel config file and it does not have CONFIG_IP_NF_NAT=y line there so I guess the NAT is not enabled by the Kernel. Do I have to make new kernel image of could I just compile NAT support as module and use that only? I checked the Maemo wiki Kernel compilation how-to, but it did not explain much about compiling kernel modules. How could I compile the NAT module?

Regards,

- Teemu

2006/4/1, Michael Wiktowy <michael.wiktowy <at> gmail.com>:
On 3/30/06, Teemu Harju <teemu.harju <at> gmail.com > wrote:
When trying to enable NAT using iptables I got the following error...

"iptables v1.2.11: can't initialize iptables table `NAT': Table does not exist (do you need to insmod?)"

So is the nat kernel module missing or something? How could I get it? Or is it something else?

It would be nice if this would work and even nicer if it could be done using the UI.


Are the table names case-sensitive? Try just 'nat' vs. 'NAT'.

/Mike





--
Teemu Harju
http://www.teemuharju.net 
_______________________________________________
maemo-developers mailing list
maemo-developers <at> maemo.org
https://maemo.org/mailman/listinfo/maemo-developers
Permalink | Reply | 0 comments |
headers
Kimmo Hämäläinen | 1 Apr 2006 14:17
Picon

Re: Trying to install a different version of Xserver on Maemo

On Fri, 2006-03-31 at 20:00, ext vasant kanchan wrote:
> Hi,
> 
> I disabled dsmetool on the Nokia. Then I tested my
> Xserver from the connected serial console. I ran some
> tests to verify that Xserver is working. I installed
> this Xserver on the device. I also modified
> x-server.sh to invoke this server instead of Xomap. I
> renabled dsmetool and rebooted the Nokia. I notice
> that Xserver starts up but the Nokia goes into
> repeated reboot.
> 
> How do I install my version of xserver ?. It would be
> usefull to provide some info on system startup and the
> role that dsmetool plays.

dsmetool can be used to provide a watchdog/lifeguard for the started
process. It you get a reboot loop, it means that the process always
crashes (or forks and the parent exits) and dsmetool reboots the device.
(It has command line help, and there are some examples in
/etc/osso-af-init directory.) If you don't want the watchdog, you can
start the process without dsmetool, or with the '-o' option of dsmetool.

BR; Kimmo

> 
> Regards
> Vasant Kanchan
> _______________________________________________
> maemo-developers mailing list
> maemo-developers <at> maemo.org
> https://maemo.org/mailman/listinfo/maemo-developers
Permalink | Reply | 0 comments |
headers
Crazy Boy | 1 Apr 2006 16:32
Picon
Favicon

Hi..."Xephyr" is not running and opening in my system

Hi,

I am using SuSe Linux 9.3 with kernel 2.6 version. I am feeling very happy to work with the Nokia 770 device.

I would like to install the Maemo SDK but I got stuck with the "Xephyr" installation.

The tutorial says
"Xephyr is pre-installed in the rootsrap, so just to make starting up Xephyr easier, create this kind of "start-xephyr.sh" script. Change the name of the target to the one you are using, here "SDK_PC":"

But I can't find it anywhere. I also did not manage to install it myself it should be in the Xserver package, but that is installed already?

After execution of the "start-xephyr.sh" file at prompt(outside of scratchbox), It is showing the below error:
: invalid option.

After execution of the "af-sb-init.sh start" command in the scratchbox console, it is showing the below error:

[sbox-SDK_PC: ~] > export DISPLAY=:2
[sbox-SDK_PC: ~] > af-sb-init.sh start
<sbox-SDK_PC]: ~]>af-sb-init.sh start

Note: For Remote X connections DISPLAY should contains host name!
Sample files present.
Starting Maemo Launcher: maemo-launcher
maemo-launcher[7199]: GLIB CRITICAL ** Gdk - gdk_display_close: assertion 'GDK_IS_DISPLAY (display)' failed
.
Starting DBUS system bus
Starting D-BUS session bus daemon
Starting Sapwood image server
Starting Matchbox window manager
Starting keyboard
Starting MAEMO AF Desktop
<sbox-SDK_PC]: ~]>matchbox-wm: can't open display! check your DISPLAY variable
sapwood-server[7243]: GLIB WARNING ** Gdk - can't open display: (null)
maemo_af_desktop[7280]: GLIB WARNING ** Gtk - can't open display:
hildon-input-method[7268]: GLIB WARNING ** Gtk - can't open display:

What I have to do to solve my problem? Please do needful. I will be waiting for your reply.

Thank you.

With best regards,
Chandra.

New Yahoo! Messenger with Voice. Call regular phones from your PC for low, low rates.
<div>
<p>Hi,<br><br>I am using SuSe Linux 9.3 with kernel 2.6 version. I am feeling very happy to work with the Nokia 770 device.<br><br>I would like to install the Maemo SDK but I got stuck with the "Xephyr" installation. <br><br>The tutorial says <br>"Xephyr is pre-installed in the rootsrap, so just to make starting up Xephyr easier, create this kind of "start-xephyr.sh" script. Change the name of the target to the one you are using, here "SDK_PC":" <br><br>But I can't find it anywhere. I also did not manage to install it myself it should be in the Xserver package, but that is installed already?<br><br>After execution of the "start-xephyr.sh" file at prompt(outside of scratchbox), It is showing the below error:<br>: invalid option.<br><br>After execution of the "af-sb-init.sh start" command in the scratchbox console, it is showing the below error:<br><br>[sbox-SDK_PC: ~] &gt; export DISPLAY=:2<br>[sbox-SDK_PC: ~] &gt; af-sb-init.sh start<br>&lt;sbox-SDK_PC]: ~]&gt;af-sb-init.sh
 start<br><br>Note: For Remote X connections DISPLAY should contains host name!<br>Sample files present.<br>Starting Maemo Launcher: maemo-launcher<br>maemo-launcher[7199]: GLIB CRITICAL ** Gdk - gdk_display_close: assertion 'GDK_IS_DISPLAY (display)' failed<br>.<br>Starting DBUS system bus<br>Starting D-BUS session bus daemon<br>Starting Sapwood image server<br>Starting Matchbox window manager<br>Starting keyboard<br>Starting MAEMO AF Desktop<br>&lt;sbox-SDK_PC]: ~]&gt;matchbox-wm: can't open display! check your DISPLAY variable<br>sapwood-server[7243]: GLIB WARNING ** Gdk - can't open display: (null)<br>maemo_af_desktop[7280]: GLIB WARNING ** Gtk - can't open display:<br>hildon-input-method[7268]: GLIB WARNING ** Gtk - can't open display:<br><br>What I have to do to solve my problem? Please do needful. I will be waiting for your reply.<br><br>Thank you.<br><br>With best regards,<br>Chandra.<br></p>
<p>
		</p>New <a href="http://us.rd.yahoo.com/mail_us/taglines/postman4/*http://us.rd.yahoo.com/evt=39666/*http://beta.messenger.yahoo.com">Yahoo! Messenger with Voice.</a> Call regular phones from your PC for low, low rates.</div>
Permalink | Reply | 2 comments |
headers
Phil Cowans | 1 Apr 2006 22:24
Picon
Picon
Favicon

Input Method Documentation

Hi all,

I just thought you might be interested in some notes I made on the IM
framework having spent an afternoon figuring out how it works:

http://www.inference.phy.cam.ac.uk/pjc51/hildon_im.txt

Hope it's useful,

Phil
Permalink | Reply | 7 comments |
headers
Neil Jerram | 2 Apr 2006 00:28

Re: Input Method Documentation

"Phil Cowans" <pjc51 <at> cam.ac.uk> writes:

> Hi all,
>
> I just thought you might be interested in some notes I made on the IM
> framework having spent an afternoon figuring out how it works:
>
> http://www.inference.phy.cam.ac.uk/pjc51/hildon_im.txt
>
> Hope it's useful,

Well I'm not working in this area myself, but judging by recent
conversations on this list I expect this will be very useful for
the people who were having those conversations.

Does this also mean that we may be getting a port of Dasher for the
770 soon?  I really hope so!

My understanding is that when your team last tried to port Dasher,
there were two issues.  (1) was that the Hildon IM framework wasn't
open; but I presume that is solved (or in the process of being solved)
by the analysis that you have posted.  (2) was that Dasher's CPU
requirement was too much for the 770 - do you have a solution for this
now as well?

Regards,
        Neil
Permalink | Reply | 5 comments |
headers
John Meacham | 2 Apr 2006 00:37
Favicon

Re: Input Method Documentation

On Sat, Apr 01, 2006 at 09:24:09PM +0100, Phil Cowans wrote:
> Hi all,
> 
> I just thought you might be interested in some notes I made on the IM
> framework having spent an afternoon figuring out how it works:
> 
> http://www.inference.phy.cam.ac.uk/pjc51/hildon_im.txt
> 
> Hope it's useful,

Sweet. this is just the information I was looking for.

        John

--

-- 
John Meacham - ⑆repetae.net⑆john⑈
Permalink | Reply | 0 comments |
headers
Neil Jerram | 2 Apr 2006 00:39

Re: Building deb packages for the Nokia 770 is very easy

"Ian" <vern <at> riseup.net> writes:

> disse  --> Neil Jerram
> Thx for these explanations,you are helping me out a lot.
> I am not sure about the difference between Build-Depends and Depends :
>
> originais -> Build-Depends: debhelper (>= 4.0.0)
>
> originais -> Depends: maemo

I'm not 100% sure either, but I believe "Build-Depends" is only
relevant when someone wants to rebuild your package from its source:
it tells that person what they need to have installed in order to do
the build.  "Depends" on the other hand lists the requirements for the
binary package installation to work.

> I know Nokia recommends only depending on maemo but can I depend on
> something else if it is already packaged for the 770 ?

Here I would agree with the answers that Kalle and Michael have
already given.

> I mean how would this work on the actual device. I am not with my
> 770 at the moment so I cannot look at its /etc/apt/sources.list but
> will i find some maemo repositories when i do?. The application
> installer is what then... some Hildonised front end to apt?

I believe it's currently much simpler than that.  Currently there are
no repositories for application installer (=> 3rd party) packages,
just individual .debs on people's websites.  (The repository that the
maemo.org pages speak about is the one used to manage the 770's base
filesystem + program set, not application installer packages.)

Regards,
        Neil
Permalink | Reply | 0 comments |
headers
Nicholas A. Bellinger | 2 Apr 2006 05:22

Core-iSCSI/Nokia770 binaries released!

Greetings all,

A Maemo formatted .deb binary for Core-iSCSI/Nokia770 has been released
on the wiki-homepage at linux-iscsi.org:

http://www.linux-iscsi.org/index.php/Core-iSCSI/Nokia_770

The files can be located directly at:

http://www.linux-iscsi.org/files/core-iscsi-maemo/core-iscsi-maemo-v10_arm.deb
http://www.linux-iscsi.org/files/core-iscsi-maemo/README

The only two requirements that currently exist (as listed in the README)
are 1) bash, and 2) obtaining superuser privledges on the device to be
able to load kernel modules, mount iSCSI LUNs, etc.

The only two limitiations that currently exist are 1) Authentication is
not supported in this release and 2) the 2.6.12.3-omap1 for the 770 does
NOT ship with CONFIG_SCSI_MULTI_LUN=y, and hence we are only able to
detect LUN 0 for each iSCSI Target Node.  Unfortuately scsi_mod is
complied directly the 2.6.12.3-omap1 kernel and the only method to get
around this is recompiling the kernel.  I would like to see scsi_mod
built as a module in future kernel releases for the Nokia 770, and
preferably with CONFIG_SCSI_MULTI_LUN=y enabled.

Also, now that the Core-iSCSI/Nokia770 project has made the first binary
release, its now time to start discussion what the plans are for the
iSCSI UI on the Nokia770.  I will be writing down some ideas for this on
the wiki homepage, and would be interested in getting some feedback on
some of the possibilies for making iSCSI easy to use on small devices.

Have fun!

--

-- 
Nicholas A. Bellinger <nab <at> kernel.org>
Permalink | Reply | 4 comments |
headers
Patrick Mansfield | 2 Apr 2006 05:53
Picon
Favicon

Re: Core-iSCSI/Nokia770 binaries released!

Hi -

On Sat, Apr 01, 2006 at 07:22:22PM -0800, Nicholas A. Bellinger wrote:

> not supported in this release and 2) the 2.6.12.3-omap1 for the 770 does
> NOT ship with CONFIG_SCSI_MULTI_LUN=y, and hence we are only able to
> detect LUN 0 for each iSCSI Target Node.  Unfortuately scsi_mod is
> complied directly the 2.6.12.3-omap1 kernel and the only method to get
> around this is recompiling the kernel.  I would like to see scsi_mod
> built as a module in future kernel releases for the Nokia 770, and
> preferably with CONFIG_SCSI_MULTI_LUN=y enabled.

You should be able to override that via 

	scsi_mod.max_luns=512

Or does it have a fixed boot command line?

-- Patrick Mansfield
Permalink | Reply | 0 comments |

Gmane