Upgrade problem - Version obsolete

[mystik]

I'm trying to upgrade my (rather old) Neuros OSD, version 3.20-0.20 is installed.

Using the File browser / Upgrade firmware option, I get 2 popups, one being "Not official neuros package", the other, "Cannot upgrade, version obsolete".
Versions tried: 3.25-0.23, 3.25-0.27 and the latest 3.31-1.24, all returned the same error.

Card type: MS PRO DUO (4 GB)

I also tried the r3.upk thing in the /newpackage/ directory, and rebooting afterwards. Didn't do anything.

Has it something to do with the card type ? Not supported in the installed version ?

[greyback]

I also tried the r3.upk thing in the /newpackage/ directory, and rebooting afterwards. Didn't do anything.

Has it something to do with the card type ? Not supported in the installed version ?

This option only works if you use a SD or CompactFlash card.

I'm surprised that you're not able to upgrade even from such an old firmware version. This is a poor show from a user's point of view.

Unfortunately, I do believe that you'll have to try the above with either a SD or CF card
I hope you have one handy.
-G

[mystik]

Ok.. going to reply on my own post.

Luckily I have a mobile phone that uses a Micro SD card, including a MicroSD > SD adapter. So I tried that one.. worked.

Thanks for listening

[greyback]

Yay!
May you enjoy the OSD! If you're interested, there are beta firmware releases available, revealing much of the functionality that is in the pipeline.

You can view these work-in-progress releases by visiting Settings->Firmware Upgrade on your OSD (note, it needs to be networked to download them).
-G

[mystik]

Yeah, I instantly tried out the beta firmware. Very nice. OSD ui has come along way since the initial version

The Youtube app is excellent..

Just looking at the smbclient code now, since when I try to access the smb shares, it asks me for a password, but the smbd is configured to allow guest/anonymous access.

[greyback]

Just looking at the smbclient code now, since when I try to access the smb shares, it asks me for a password, but the smbd is configured to allow guest/anonymous access.

It looks to me that the smbclient code does include for the case of anonymous access. If you just press ok on the username/password dialog, does that work?

Essentially, if you look at smbclient.c at the function MountShare, you want to pass it NULL for both password & username.
-G

[mystik]

Yeah, I also found that part of the code.

But when I use the same command line on my linux (Debian) box, it asks for a password.

So I tried using the parameter     -o username=guest,password=guest   and it mounted the smb share without asking for a password.

But when I tried it on the OSD itself (telnet), it returned,

Code:

~ # mount -t cifs //192.168.1.10/filearchive /media/network/DELIVERANCE/filearchive -o username=guest,password=guest
mount: Mounting //192.168.1.10/filearchive on /media/network/DELIVERANCE/filearchive failed: Input/output error

Samba version: 3.0.23d (Debian testing)

Will do some additional debugging / tracing.

I tried attaching / uploading smb.conf, but SMF / the forum returns an "upload path not found" error.

[greyback]

Hmmm, I/O error? Could you try the mount command with a "--verbose" switch and see if you get any better error messages?

Thanks for the heads up on the Upload File error, shall have it fixed
-G

[mystik]

Well, that's part of the problem.. the Busybox mount doesn't include verbose logging
The flag is just ignored as far as I checked (busybox svn)

So, enabled debugging on the server, and gave me following log,

Code:

[2007/08/10 16:58:06, 3] smbd/oplock.c:init_oplocks(862)
  open_oplock_ipc: initializing messages.
[2007/08/10 16:58:06, 3] smbd/oplock_linux.c:linux_init_kernel_oplocks(260)
  Linux kernel oplocks enabled
[2007/08/10 16:58:06, 3] smbd/process.c:process_smb(1110)
  Transaction 0 of length 51
[2007/08/10 16:58:06, 3] smbd/process.c:switch_message(914)
  switch message SMBnegprot (pid 3985) conn 0x0
[2007/08/10 16:58:06, 3] smbd/sec_ctx.c:set_sec_ctx(241)
  setting sec ctx (0, 0) - sec_ctx_stack_ndx = 0
[2007/08/10 16:58:06, 3] smbd/negprot.c:reply_negprot(487)
  Requested protocol [NT LM 0.12]
[2007/08/10 16:58:06, 3] smbd/negprot.c:reply_nt1(350)
  not using SPNEGO
[2007/08/10 16:58:06, 3] smbd/negprot.c:reply_negprot(580)
  Selected protocol NT LM 0.12
[2007/08/10 16:58:07, 3] smbd/process.c:timeout_processing(1359)
  timeout_processing: End of file from client (client has disconnected).
[2007/08/10 16:58:07, 3] smbd/sec_ctx.c:set_sec_ctx(241)
  setting sec ctx (0, 0) - sec_ctx_stack_ndx = 0
[2007/08/10 16:58:07, 3] smbd/connection.c:yield_connection(69)
  Yielding connection to
[2007/08/10 16:58:07, 3] smbd/server.c:exit_server_common(675)
  Server exit (normal exit)
[2007/08/10 16:59:20, 3] smbd/oplock.c:init_oplocks(862)
  open_oplock_ipc: initializing messages.
[2007/08/10 16:59:20, 3] smbd/oplock_linux.c:linux_init_kernel_oplocks(260)
  Linux kernel oplocks enabled
[2007/08/10 16:59:20, 3] smbd/process.c:process_smb(1110)
  Transaction 0 of length 51
[2007/08/10 16:59:20, 3] smbd/process.c:switch_message(914)
  switch message SMBnegprot (pid 3988) conn 0x0
[2007/08/10 16:59:20, 3] smbd/sec_ctx.c:set_sec_ctx(241)
  setting sec ctx (0, 0) - sec_ctx_stack_ndx = 0
[2007/08/10 16:59:20, 3] smbd/negprot.c:reply_negprot(487)
  Requested protocol [NT LM 0.12]
[2007/08/10 16:59:20, 3] smbd/negprot.c:reply_nt1(350)
  not using SPNEGO
[2007/08/10 16:59:20, 3] smbd/negprot.c:reply_negprot(580)
  Selected protocol NT LM 0.12
[2007/08/10 16:59:20, 3] smbd/process.c:timeout_processing(1359)
  timeout_processing: End of file from client (client has disconnected).
[2007/08/10 16:59:20, 3] smbd/sec_ctx.c:set_sec_ctx(241)
  setting sec ctx (0, 0) - sec_ctx_stack_ndx = 0
[2007/08/10 16:59:20, 3] smbd/connection.c:yield_connection(69)
  Yielding connection to
[2007/08/10 16:59:20, 3] smbd/server.c:exit_server_common(675)
  Server exit (normal exit)

The weird thing is that using the smbclient 'shell' works without any problems, I can access all smb shared files through the smbclient shell.