General NAS-Central Forums

Welcome to the NAS community
It is currently Mon Sep 25, 2017 2:44 am

All times are UTC




Post new topic Reply to topic  [ 24 posts ]  Go to page 1, 2  Next
Author Message
PostPosted: Mon Aug 12, 2013 2:29 pm 
Offline

Joined: Thu Jan 28, 2010 6:13 pm
Posts: 35
Hello all,
i am using lenny (ubuntu 5.0) on my nsa-220 but i have only one "complain" , i can't write on NTFS partition.
i have installed ntfs-3g and libfuse2 but i got the error :
Quote:
WARNING: Deficient Linux kernel detected. Some driver features are
not available (swap file on NTFS, boot from NTFS by LILO), and
unmount is not safe unless it's made sure the ntfs-3g process
naturally terminates after calling 'umount'. If you wish this
message to disappear then you should upgrade to at least kernel
version 2.6.20, or request help from your distribution to fix
the kernel problem. The below web page has more information:
http://ntfs-3g.org/support.html#fuse26

the lenny buid for nsa-220 uses the kernle 2.6.18.6 so i need your help to create a custom kernel 2.6.26 or 2.6.32 that will boot nsa-220 .
i've read the post regarding kernel build (viewtopic.php?f=131&t=4561) ... but this is the same kenel 2.6.18.6 (ftp://opensource.zyxel.com/NSA-220/3.24.update.Apr.08/) so it will not write on NTFS.
i have build 2 or 3 kernels (2.6.26, 2.6.32) from sources but they are not booting tht nsa-220 box (so i think i didn't set up somethink well) .
i'm not verry good at linux... and i don't know how this works ...i think the initramfs (symlink to initrd) has to be the same (and small to be loaded) as the zImage, also i think we have to have some reloaded-"kernel-versionb".ko in the /boot .
i will apreciate all your help to solve this "problem"

regards refe


Top
 Profile  
 
PostPosted: Tue Aug 13, 2013 9:58 am 
Offline

Joined: Mon Jun 16, 2008 10:45 am
Posts: 6039
It's not an error, it's a warning. Are you suffering from any of the problems the warning is stating?

Quote:
i have build 2 or 3 kernels (2.6.26, 2.6.32) from sources but they are not booting tht nsa-220 box
Do you have a bootlog?


Top
 Profile  
 
PostPosted: Wed Aug 14, 2013 6:49 am 
Offline

Joined: Thu Jan 28, 2010 6:13 pm
Posts: 35
Hello Mijzelf
Mijzelf wrote:
It's not an error, it's a warning. Are you suffering from any of the problems the warning is stating?

no i'm not suffering but, i can't write on the stick/hdd if i want to.
i even try mount -t ntfs-3g -o rw /dev/sdd1 /mnt/ntfs it's still mounting in read only

Mijzelf wrote:
Do you have a bootlog?

no i have no bootlog, i will try to create a serial console or something to see what's happening viewtopic.php?f=131&t=21
i 've compiled all the kernels on the nsa-220 box (2.6.18.6 , 2.6.26 , 2.6.32), with the config that KeyCat gave me, i was able to create and boot a zImage (from zyxel sources kernel - 2.6.18.6 ).
i've made symlinks between zImage build by the new kernel > zImage and the and /lib/modules/ 2.6.18.6.buid.by.new.kernel and 2.6.18.6-cs and the kernel booted, but still not NTFS write support .
actually right now (with a USB stick formated NTFS) ..i can't acces the mount point /mnt/ntfs ..the shell just freeze when i do cd /mnt/ntfs , but the system it's accesible if i do another ssh to the box
i'm not very good at programing ...or scripting... and i did not understand well how the lenny it's booted from the usb drive
i'll keep on reading how lenny works on nsa-220


Top
 Profile  
 
PostPosted: Wed Aug 14, 2013 9:21 am 
Offline

Joined: Mon Jun 16, 2008 10:45 am
Posts: 6039
refe wrote:
i can't write on the stick/hdd if i want to.
i even try mount -t ntfs-3g -o rw /dev/sdd1 /mnt/ntfs it's still mounting in read only
Really? Strange that that possibility isn't stated in the warning. Have a look in dmesg to see if some clear (and hopefully solvable) problem is mentioned.

Quote:
i 've compiled all the kernels on the nsa-220 box, whit the config that KeyCat gave me, i was able to create and boot a kernel.
When I remember well, the original kernel had a /proc/config.gz, containing the .config which build that kernel. Maybe you'll have to load config.ko for that.

Quote:
i did not understand well how the lenny it's booted from the usb drive
i'll keep on reading how lenny works on nsa-220
Actually it's quite simple. A special kernel module (reload.ko) is loaded in the stock kernel, causing the kernel to be replaced by another provided kernel, which boots 'normally'. Also an initrd is provided, which mounts the Lenny stick, and switches root to the root of the Lenny installation, where init is called. Done.

BTW, I can think of 2 obvious reasons why a newer kernel doesn't boot on your box. On forum.dsmg600.info I read somewhere that reload.ko wasn't able to boot a newer kernel. (That was for a DNS323, but the reload.ko for the 220 is almost identical). That is several years ago, so I think it was a 2.6.30 kernel or something like that. BTW, as far as I remember no-one confirmed that, so it might just be a false alarm.
The 2nd is the machtype which is provided with the reboot. This type is used by the kernel to call the right setup. By default 859 is used, as I remember well. This machtype is also used by the stock kernel. However, the 220 has no official machtype, so a vanilla kernel won't recognize it, and I think it will error out with 'unsupported hardware'. You could include support for a comparable box in your kernel (the DNS323?) and provide it's machtype in the reload command line (machtype=nnn). Of course you can also compile in all supported Orion devices, and try all their machtypes. (A list of machtypes is somewhere in the arch/arm directory).
BTW, do *not* try to do anything with the flash (mtd partitions) when running an nsa220 unaware kernel.


Top
 Profile  
 
PostPosted: Fri Aug 16, 2013 1:41 pm 
Offline

Joined: Thu Jan 28, 2010 6:13 pm
Posts: 35
hello,
right now i'm trying to put support for mv88fxx81 in source kernel 2.6.21
so i copied the folder arch-mv88fxx81 from original sources and place it in linux-2.6.21/include/asm-arm/(arch-mv88fxx81)
also copied mach-mv88fxx81 from original sources in linux-2.6.21/arch/arm/(mach-mv88fxx81)
i've made also modifcation to the file linux-2.6.21/arch/arm/Kconfig , adding
Quote:
config ARCH_MV88fxx81
bool "mv88fxx81"
select PCI
source "arch/arm/mach-mv88fxx81/LSP/Kconfig"

now when i do make menuconfig i can select at System type > ARM system type (mv88fxx81) but i have nothing on Processor Type, if i select ARM Ltd. Versatile family i have at Processor Type > Support ARM926T processor . so i think i've mist something... something that should enable on the mv88fxx81 profile to add support for CPU ARM926T.


Top
 Profile  
 
PostPosted: Fri Aug 16, 2013 9:24 pm 
Offline

Joined: Mon Jun 16, 2008 10:45 am
Posts: 6039
I wish I was skilled enough to tell you what the problem is.
Did you do a 'make clean ; make menuconfig' after changing that Kconfig file?

Starting with 2.6.25 the vanilla kernel support Orion SoCs,

You have now 2.6.16, and need 2.6.20. Theoretically you can download and apply all patches to get from 16 to 20, and hope the adjustments from Marvel and ZyXEL don't interfere with it.


Top
 Profile  
 
PostPosted: Sat Aug 17, 2013 6:52 am 
Offline

Joined: Thu Jan 28, 2010 6:13 pm
Posts: 35
Hi Mijzelf,
thanks for the links, i'll read them and try both ways ..
1. to compile a kernel 2.6.26 that supports Orion SoC
2. to patch kernel 2.6.18-6 up to 2.6.20

yes I did 'make clean ; make menuconfig' after I modified Kconfig file.

it's strange that I can't find patches newer (>) than 2.6.13 on https://www.kernel.org/pub/linux/kernel/v2.6/


Top
 Profile  
 
PostPosted: Sat Aug 17, 2013 12:37 pm 
Offline

Joined: Mon Jun 16, 2008 10:45 am
Posts: 6039
refe wrote:
it's strange that I can't find patches newer (>) than 2.6.13 on https://www.kernel.org/pub/linux/kernel/v2.6/
You are right, and so are the changelogs. I have done some googling, and can't find them either. Strange.
Of course it's possible to create them yourself by doing a diff, but I suppose that will bring much noise, and drift away from the original problem.


Top
 Profile  
 
PostPosted: Sat Aug 17, 2013 3:16 pm 
Offline

Joined: Thu Jan 28, 2010 6:13 pm
Posts: 35
Mijzelf wrote:
refe wrote:
it's strange that I can't find patches newer (>) than 2.6.13 on https://www.kernel.org/pub/linux/kernel/v2.6/
You are right, and so are the changelogs. I have done some googling, and can't find them either. Strange.
Of course it's possible to create them yourself by doing a diff, but I suppose that will bring much noise, and drift away from the original problem.

found them here http://mirror.linux.org.au/linux/kernel/v2.6/ , i'll give a try next week


Top
 Profile  
 
PostPosted: Thu Sep 19, 2013 9:49 am 
Offline

Joined: Thu Jan 28, 2010 6:13 pm
Posts: 35
refe wrote:
Hi Mijzelf,
thanks for the links, i'll read them and try both ways ..
1. to compile a kernel 2.6.26 that supports Orion SoC
2. to patch kernel 2.6.18-6 up to 2.6.20
yes I did 'make clean ; make menuconfig' after I modified Kconfig file.
it's strange that I can't find patches newer (>) than 2.6.13 on https://www.kernel.org/pub/linux/kernel/v2.6/

so i'm back with news about what I did :
0 .I manage to create a serial console for my Zyxel NSA 220 (I've used MAX 3232 with schematics from this post viewtopic.php?f=131&t=21)
2. I've patch kernel 2.6.18-6 up to 2.6.20 ...didn't work or I didn't do it right
1. I've compiled a newer kernel 2.6.32 from Ubuntu squeeze sources but I got the error from serial console (the log is bigger but I couldn't post it on the forum):

Uncompressing Linux... done, booting the kernel.
Error: unrecognized/unsupported machine ID (r1 = 0x0000035b).
Available machine support:
ID (hex) NAME
0000054e Marvell Orion-2 Development Board
000005e4 Marvell Orion-NAS Reference Design
00000631 Buffalo Linkstation Pro/Live
000005e5 Buffalo/Revogear Kurobox Pro
00000630 Buffalo Terastation Pro II/Live
00000742 Buffalo Linkstation Mini
00000606 D-Link DNS-323
0000061d QNAP TS-109/TS-209
00000641 QNAP TS-409
00000661 Linksys WRT350N v2
00000674 Technologic Systems TS-78xx SBC
0000069d HP Media Vault mv2120
000006dc LaCie Ethernet Disk mini V2
000008eb LaCie Big Disk Network
000008ea LaCie d2 Network
00000926 LaCie 2Big Network
000006e6 Maxtor Shared Storage II
00000709 Netgear WNR854T
00000714 Marvell Orion-VoIP GE Reference Design
0000071a Marvell Orion-VoIP FXO Reference Design
00000766 Marvell Orion-1-90 AP GE Reference Design

Please check your kernel config and/or bootloader.

right now i'm looking for a way to add machine id 0000035b to kernel support (if possible)


Top
 Profile  
 
PostPosted: Thu Sep 19, 2013 2:25 pm 
Offline

Joined: Mon Jun 16, 2008 10:45 am
Posts: 6039
You are loading this kernel using reloaded.ko? In that case you can simply provide a different machtype:
Code:
insmod reloaded.ko kernel=whatever machtype=1358
will 'emulate' the Orion-2 Development Board.


Top
 Profile  
 
PostPosted: Thu Sep 19, 2013 2:48 pm 
Offline

Joined: Thu Jan 28, 2010 6:13 pm
Posts: 35
Mijzelf wrote:
You are loading this kernel using reloaded.ko? In that case you can simply provide a different machtype:
Code:
insmod reloaded.ko kernel=whatever machtype=1358
will 'emulate' the Orion-2 Development Board.

Hello Mijzelf,
i think i'm using reloaded.ko to boot this kernel (i've made symlink of zImage.2.6.32 to zImage , also made symlink between /lib/modules/2.6.32 and /lib/modules/2.6.18-6-cs)
but i don't know where can i provide a differet machtype
Code:
insmod reloaded.ko kernel=whatever machtype=1358

i don't know where to put this line, in which script ? in the kernel?


Top
 Profile  
 
PostPosted: Thu Sep 19, 2013 2:52 pm 
Offline

Joined: Mon Jun 16, 2008 10:45 am
Posts: 6039
This is in the script which does the actual reloading. (reload.sh? It's a looong time ago)


Top
 Profile  
 
PostPosted: Thu Sep 19, 2013 2:59 pm 
Offline

Joined: Thu Jan 28, 2010 6:13 pm
Posts: 35
i've made the modification in /boot/reload.sh
Code:
/sbin/insmod ${RELOADED_KO} kernel=zImage initrd=initrd machtype=1358 cmdline="$

added one by one
machtype=1358 for Marvell Orion-2 Development Board
machtype=1508 for Marvell Orion-NAS Reference Design
machtype=1542 for D-Link DNS-323
unfortunatly ..when i put machtype in the command for reload new kernel the box booted in Zyxel enviroment

i'll make more tests today


Top
 Profile  
 
PostPosted: Mon Sep 23, 2013 12:11 pm 
Offline

Joined: Mon Jun 16, 2008 10:45 am
Posts: 6039
? That's weird. Do you have a serial log of the moment of reloading? I guess the kernel is not 100% compatible, which causes some kernel panic, which reboots the box. But why doesn't it get in a loop, then?


Top
 Profile  
 
Display posts from previous:  Sort by  
Post new topic Reply to topic  [ 24 posts ]  Go to page 1, 2  Next

All times are UTC


Who is online

Users browsing this forum: No registered users and 5 guests


You cannot post new topics in this forum
You cannot reply to topics in this forum
You cannot edit your posts in this forum
You cannot delete your posts in this forum
You cannot post attachments in this forum

Search for:
Jump to:  
Powered by phpBB® Forum Software © phpBB Group