Buffalo NAS-Central Forums

Welcome to the Linkstation Wiki community
It is currently Sat Aug 18, 2018 3:48 am

All times are UTC+01:00




Post new topic  Reply to topic  [ 743 posts ]  Go to page Previous 145 46 47 48 49 50 Next
Author Message
PostPosted: Fri Jan 15, 2010 6:24 pm 
Offline
Newbie

Joined: Sat Jun 09, 2007 4:27 pm
Posts: 16
happy new year to the whole forum!!!

deb: i installed your new compiled kernel; thanks I am using your kernels from last yoear and i do not have any problems.

now with your 2.6.32.2, I am trying to update udev.
Could you remove from your kernel CONFIG_SYSFS_DEPRECATED ?

thanks
immiimmi

Quote:
Preparing to replace udev 146-5 (using .../archives/udev_150-2_armel.deb) ...
Since release 150, udev requires that support for the CONFIG_SYSFS_DEPRECATED
feature is disabled in the running kernel.

Please upgrade your kernel before or while upgrading udev.

AT YOUR OWN RISK, you can force the installation of this version of udev
WHICH DOES NOT WORK WITH YOUR RUNNING KERNEL AND WILL BREAK YOUR SYSTEM
AT THE NEXT REBOOT by creating the /etc/udev/kernel-upgrade file.
There is always a safer way to upgrade, do not try this unless you
understand what you are doing!

dpkg: error processing /var/cache/apt/archives/udev_150-2_armel.deb (--unpack):


Top
   
PostPosted: Sat Jan 16, 2010 6:47 am 
Offline
Newbie

Joined: Wed Feb 27, 2008 12:42 am
Posts: 66
Hi Immiimmi,

This is not a help to you but I might experiment compiling (if I acquire the proper skill) from the source if you could explain what
Quote:
udev
is all about and why it should be worthy of our attention (In embedded arm and/or Intel). In plain english please becuase I'm not a c programmer, just a simple net admin. I wiki'ed it but no help.


Thanks,
Tek


Top
   
PostPosted: Sun Jan 17, 2010 6:57 pm 
Offline
Newbie

Joined: Wed Feb 27, 2008 12:42 am
Posts: 66
Thanks all. It worked. I now have an updated kernel (deb). :up: Thanks ARES. And thank you so much Davy_Gravy :D


__________sudZUZ#Z#XZo=___________DDDD___EEEEEE_BBBB___IIIIII____AAAA___NN___NN
_______jmZZ2!!~---~!!X##wa_________DD'''DD__EE_____BB_BB____II___AA__AA__NNN__NN
___.<wdP~~____________-!YZL,______DD__DD_EEEEE__BBBBB____II___AAAAAA__NNNN_NN
__.mX2_________%aaa_______XZ[.___DD_DD__EE_____BB__BB___II___AA__AA__NN_NNNN
__oZ[_______jdXY!~?S#wa___]Xb;_____DDDD___EEEEEE_BBBBB__IIIIII_AA__AA__NN___NN
__#e______.]X2(_____~Xw|__)XXc
.2Z`______]X[._______xY|__]oZ(____Linux Version 2.6.32.2
.2#;______)3k;______s!~___jXf`____Compiled #1 Sun Dec 20 05:34:54 EST 2009
_1Z>______-]Xb/____~______#2(____One_ARM_Feroceon_rev_0_(v5l)_Processor,_128M_RAM
_-Zo;_______+!4ZwaaaauZZXY_______266.24_Bogomips_Total
__*#[,________~-?!!!!!!-~___________ls-gl.nubee.com
___XUb;.
____)YXL,,
______+3#bc,
________-)SSL,,
___________~~~~~

Debian GNU/Linux 5.0 Lenny
tek@ls-gl:~$ uname -a
Linux ls-gl.nubee.com 2.6.32.2 #1 Sun Dec 20 05:34:54 EST 2009 armv5tel GNU/Linux

:D

BTW. I liked the logo. What file is it again? How can I import it to my other Debian?

Thanks
Tek


Top
   
PostPosted: Mon Jan 25, 2010 11:31 am 
Offline
Newbie

Joined: Sun Jan 17, 2010 2:14 pm
Posts: 5
Hi Everyone,

First a big thanks to everyone for this project, I've been running Davy_Gravy's Armel build (3.2 stock) for a few months & all has been good :D

However after installing cups and doing a reboot my system will not boot into Debian it is defaulting to a TFTP boot. I've been banging my head trying to work out what is going on. The file systems seem to be okay on both sda1 and sda2, but U-Boot doesn't seem to be able to read /initrd.buffalo. Below is the boot sequence from my serial console:
Code:
Orion1   CPU =  Low 

=== BUFFALO LS-GL U-Boot. ===
 ** LOADER **
 ** BUFFALO BOARD: BUFFALO_BOARD_LS_GL LE (CFG_ENV_ADDR=fffff000)


U-Boot 1.1.1 (Apr 18 2007 - 18:35:44) Marvell version: 1.12.1 - TINY

DRAM CS[0] base 0x00000000   size 128MB
DRAM Total size 128MB
[256kB@fffc0000] [0kB@f8000000] ## Unknown FLASH at f8000000: Size = 0x00000000 = 0 MB
Flash: 256 kB
Addresses 20M - 0M are saved for the U-Boot usage.
Mem malloc Initialization (20M - 16M): Done

Soc: 88F5182 A2
CPU: ARM926 (Rev 0) running @ 400Mhz
Orion 1 streaming disabled
SysClock = 200Mhz , TClock = 166Mhz


USB 0: host mode
USB 1: host mode
PCI 0: PCI Express Root Complex Interface
PCI 1: Conventional PCI, speed = 33000000
Net:   egiga0 [PRIME]
Using 88E1118 phy

Marvell Serial ATA Adapter
Integrated Sata device found
  Device 0: OK
Model: SAMSUNG HD501LJ                          Firm: CR100-12 Ser#: S0MUJ1KQ115597     
            Type: Hard Disk
            Supports 48-bit addressing
            Capacity: 476940.0 MB = 465.7 GB (976773168 x 512)

Using device ide0, partition 1

Loading from block device ide device 0, partition 1: Name: hda1
  Type: U-Boot  File:/initrd.buffalo

0 bytes read
Using device ide1, partition 1
** Bad partition 1 **
Lost all init_rd
hit any key to switch tftp boot.
Hit any key to stop autoboot:  3  2  1  0


This is what the file system looks like on sda1:
Code:
foonas-em$ ls -ln
-rw-r--r--    1 0        0         1011256 Jan 25 00:05 System.map-2.6.29.1
-rw-r--r--    1 0        0           60034 Jan 25 00:05 config-2.6.29.1
-rw-r--r--    1 0        0         2322728 Jan 25 00:05 initrd.buffalo
drwx------    2 0        0           16384 Jan 24 16:09 lost+found
-rw-r--r--    1 0        0              29 Jan 25 00:05 rootfs_ok
-rw-r--r--    1 0        0         2331216 Jan 25 00:05 uImage
-rw-r--r--    1 0        0         2331216 Jan 25 00:05 uImage-2.6.29.1
-rw-r--r--    1 0        0         5407280 Jan 25 00:05 uImage_em
-rw-r--r--    1 0        0         6496566 Jan 25 00:05 vmlinux-2.6.29.1


and this is what the flash boot variables look like:
Code:
foonas-em$ fooboot -n
     ...current env var values for uBoot:

bootargs=$(bootargs_base) $(bootargs_root)
baudrate=115200
loads_echo=0
ipaddr=192.168.11.150
serverip=192.168.11.1
rootpath=/nfs/arm
cpuName=926
CASset=min
MALLOC_len=4
bootargs_end=:::DB88FXX81:eth0:none
ethact=egiga0
ethaddr=00:16:01:C5:A4:14
stdin=serial
stdout=serial
stderr=serial
enaMonExt=no
enaFlashBuf=yes
enaCpuStream=no
ethprime=egiga0
buffalo_ver=BOOTVER=1.10
buffalo_minor_ver=BOOT_MINOR_VER=1.00
build_time=18:35:39
initrd=initrd.buffalo
kernel=uImage.buffalo
bootargs_base=console=ttyS0,115200
bootargs_root=root=/dev/sda2 rw initrd=0x00800040,15M panic=5
def_tftp=tftp 0x00100000 $(kernel);tftp 0x00800000 $(initrd);setenv bootargs $(bootargs_base) $(bootargs_root) $(buffalo_ver) tftpboot=yes;bootm 0x00100000 0x00800000
bootdelay=3
disaMvPnp=no
overEthAddr=no
usb0Mode=host
usb1Mode=host
bootcmd=ide reset ; ext2load ide 0:1 0x00100000 /uImage ; setenv bootargs netconsole=6666@192.168.11.150/,@192.168.11.149/ root=/dev/sda2 rw ; bootm 0x00100000


Once again thanks for a great site & I hope I'm not wasting peoples time with something really obvious. V


Top
   
PostPosted: Thu Jan 28, 2010 7:59 am 
Offline
Newbie

Joined: Fri Jan 19, 2007 8:05 pm
Posts: 17
modules-2.6.32.4.tar.gz is good. I should click the Download Source button to d/l it. That button is on the right-up corner of the page.
http://github.com/deb/Current-stable-ke ... nt_kernel/

I used a wrong uImage-2.6.32.4(got it by http), after reboot, the ls-gl keep tftp-booting and beeping.
I just took the harddrive out, hooked it to a linux pc with a SATA-USB
sudo cp the correct uImage-2.6.32.4 to /sda2/Boot/ and /sda1
Now 2.6.32.4 is running well.

FUSE in this lenny Debian 2.6.29.1 works well. It was my fault, massed up the modules /lib/modules/2.6.29.1/modules.dep
Sorry for the noise.


Last edited by fastness on Sat Feb 06, 2010 7:34 am, edited 1 time in total.

Top
   
PostPosted: Thu Feb 04, 2010 4:52 am 
Offline
Newbie

Joined: Mon May 25, 2009 4:11 pm
Posts: 30
fastness wrote:
Is that the modules-2.6.32.4.tar.gz broken. It is marked as 4453.636 kb, but I can got 5.4 KB (5521 bytes) only.
http://github.com/deb/Current-stable-ke ... 2.4.tar.gz

It seems the FUSE in this lenny Debian doesn't work, I can't mount a Maxor 750GB OneTouch 4 pro at NTFS, even the dmesg shows well.



That's odd. You could use the previous kernel in the git repository....
I can't reach github atm, there seems to be a server issue. I am compiling 2.6.32.7 now so i wouldn't worry too much.

I haven't used fuse in a while now. It shouldn't be broken though. If you could provide more information, we can look into it. ("it doesn't work" isn't very helpful).


Top
   
PostPosted: Fri Feb 05, 2010 9:07 pm 
Offline
Newbie

Joined: Sat Jun 09, 2007 4:27 pm
Posts: 16
fastness wrote:
Is that the modules-2.6.32.4.tar.gz broken. It is marked as 4453.636 kb, but I can got 5.4 KB (5521 bytes) only.
http://github.com/deb/Current-stable-ke ... 2.4.tar.gz

It seems the FUSE in this lenny Debian doesn't work, I can't mount a Maxor 750GB OneTouch 4 pro at NTFS, even the dmesg shows well.



no the file is not broken:
if you want to download with webbrowser you should refer to the so called raw:
http://github.com/deb/Current-stable-ke ... 2.4.tar.gz

i prefer to use the command >> /usr/bin/git clone http://github.com/deb/Current-stable-ke ... nt_kernel/

immi


Top
   
PostPosted: Sat Feb 20, 2010 11:15 pm 
Offline
Newbie

Joined: Fri Jan 11, 2008 11:55 am
Posts: 7
Hi all,

hopefully some of the main contributors to this thread are still reading this...
Yesterday in installed the latest lenny image and kernel from davy_gravy (thanks!) succesfully. After power cycling everything came up nice and shiny.
After installation, I configured my network, created mount points for my extra partitions and did an apt-get update && apt-get upgrade

All went fine.

Then I powered it down, and powered it up again. Now the led indicator for booting kept on blinking, so it could not finish the boot process apparently.
I made several attempts, always the same result. After a couple of minutes, a beeping sound could be heared, and the red error led started blinking. 4 times, than a short pause. This means there are problems with the fan, and indeed, the fan is not working...

When i sniff the network, I see the kernel booting output passing by. In it, i can see that the root fs is mounted, that is about the end of the logging.

Now i wonder: Is it because the boot process is not continuing that the fan is not running after 5 minutes? Or is it because the fan is not working that booting also fails?

My first guess (to be verified tomorrow) would be that the apt-get upgrade installed an initrd which is not valid or something. Does that make sense?

Any suggestions are most welcome!

Luksedj


Top
   
PostPosted: Sun Feb 21, 2010 3:39 pm 
Offline
Regular Member

Joined: Mon Apr 09, 2007 9:48 pm
Posts: 130
Hi guys, how long !
I see that you guys never rest , davy you always keep kernels up to date :)
well , any way , i am about to buy a LS-XHL [need i little more RAM ]and i'd like to know if freelink works on it. Anyone knows ? Can i just swap my HDD from the LSPRO v2 and it will work ? Recompile kernel needed ? [probably]


Top
   
PostPosted: Thu Mar 04, 2010 11:46 pm 
Offline
Total Newbie

Joined: Fri Mar 21, 2008 8:35 pm
Posts: 4
Hi deb, and thanks for the kernels!

I upgraded from 2.6.31.1 to your 2.6.32.7 (both using davy's rootfs from back on page 1). Now my NFS server no longer works. This is what I get when it tries to start:

Quote:
jls:~# /etc/init.d/nfs-kernel-server start
Not starting NFS kernel daemon: no support in current kernel. (warning).


I ran 'depmod -a' again just to be sure, but that didn't help. The NFS server works perfectly when I boot 31.1. Did I miss something in the 47 pages of posts?

Thanks,
lightning9


Top
   
PostPosted: Sat Mar 06, 2010 5:40 pm 
Offline
Regular Member

Joined: Mon Apr 09, 2007 9:48 pm
Posts: 130
lightning9 wrote:
Hi deb, and thanks for the kernels!

I upgraded from 2.6.31.1 to your 2.6.32.7 (both using davy's rootfs from back on page 1). Now my NFS server no longer works. This is what I get when it tries to start:

Quote:
jls:~# /etc/init.d/nfs-kernel-server start
Not starting NFS kernel daemon: no support in current kernel. (warning).


I ran 'depmod -a' again just to be sure, but that didn't help. The NFS server works perfectly when I boot 31.1. Did I miss something in the 47 pages of posts?

Thanks,
lightning9


Comment the following lines in /etc/init.d/nfs-kernel-server and it will work [i had the same problem]
# See if our running kernel supports the NFS kernel server
#if [ -f /proc/kallsyms ] && ! grep -qE 'init_nf(sd| )' /proc/kallsyms; then
# log_warning_msg "Not starting $DESC: no support in current kernel."
# exit 0
#fi


Top
   
PostPosted: Sun Mar 07, 2010 2:13 am 
Offline
Newbie

Joined: Mon May 25, 2009 4:11 pm
Posts: 30
nfs-server not starting on the 2.6.32 kernel is a known bug - http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=554508

Also, I would appreciate it if some one else tried to compile a 2.6.33 kernel using my script from my git repository and the config from the 2.6.32.7 kernel. I managed to hit a few module compilation bugs and some one on the kernel mailing list think my device might have bad ram. It is probably a gcc error and is triggered / picked up while building kernel modules.


http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=572653
http://lkml.org/lkml/2010/3/6/25


Top
   
PostPosted: Sun Mar 07, 2010 4:30 am 
Offline
Regular Member

Joined: Mon Oct 15, 2007 5:21 am
Posts: 144
@deb:
compiling 2.6.33, a linkstation live, v2.
debian lenny armel , completely up-to-date (my own armel rootfs, not Davy-Gravy's or yours, if you also made one.) :
Compiled fs/afs/super.c using your 2.6.32.7 config (after a make oldconfig with default choices)

make zImage modules
no problems when afs module is compiled.
Quote:

LD fs/afs/built-in.o
CC [M] fs/afs/callback.o
CC [M] fs/afs/cell.o
CC [M] fs/afs/cmservice.o
CC [M] fs/afs/dir.o
CC [M] fs/afs/file.o
CC [M] fs/afs/flock.o
CC [M] fs/afs/fsclient.o
CC [M] fs/afs/inode.o
CC [M] fs/afs/main.o
CC [M] fs/afs/misc.o
CC [M] fs/afs/mntpt.o
CC [M] fs/afs/proc.o
CC [M] fs/afs/rxrpc.o
CC [M] fs/afs/security.o
CC [M] fs/afs/server.o
CC [M] fs/afs/super.o
CC [M] fs/afs/netdevices.o
CC [M] fs/afs/vlclient.o
CC [M] fs/afs/vlocation.o
CC [M] fs/afs/vnode.o
CC [M] fs/afs/volume.o
CC [M] fs/afs/write.o
LD [M] fs/afs/kafs.o


Quote:
HS-DHGLCC8:/usr/src# gcc -v
Using built-in specs.
Target: arm-linux-gnueabi
Configured with: ../src/configure -v --with-pkgversion='Debian 4.3.2-1.1' --with-bugurl=file:///usr/share/doc/gcc-4.3/README.Bugs --enable-languages=c,c++,fortran,objc,obj-c++ --prefix=/usr --enable-shared --with-system-zlib --libexecdir=/usr/lib --without-included-gettext --enable-threads=posix --enable-nls --with-gxx-include-dir=/usr/include/c++/4.3 --program-suffix=-4.3 --enable-clocale=gnu --enable-libstdcxx-debug --enable-objc-gc --enable-mpfr --disable-libssp --disable-sjlj-exceptions --enable-checking=release --build=arm-linux-gnueabi --host=arm-linux-gnueabi --target=arm-linux-gnueabi
Thread model: posix
gcc version 4.3.2 (Debian 4.3.2-1.1)
HS-DHGLCC8:/usr/src#



got a few warnings so far:
Quote:
arch/arm/kernel/return_address.c:61:2: warning: #warning "TODO: return_address should use unwind tables"
arch/arm/kernel/return_address.c:61:2: warning: #warning "TODO: return_address should use unwind tables"


Quote:
kernel/sched.c: In function ‘wake_up_new_task’:
kernel/sched.c:2650: warning: unused variable ‘cpu’


Quote:
fs/ecryptfs/messaging.c: In function ‘ecryptfs_process_response’:
fs/ecryptfs/messaging.c:276: warning: ‘daemon’ may be used uninitialized in this function



Quote:
CC [M] crypto/xor.o
include/asm-generic/xor.h:696: warning: ‘xor_block_8regs_p’ defined but not used
include/asm-generic/xor.h:704: warning: ‘xor_block_32regs_p’ defined but not used


Quote:
drivers/net/wireless/p54/main.c: In function ‘p54_register_common’:
drivers/net/wireless/p54/main.c:596: warning: unused variable ‘priv’
drivers/net/wireless/p54/main.c: In function ‘p54_unregister_common’:
drivers/net/wireless/p54/main.c:638: warning: unused variable ‘priv’


The build seemed successful, though I did not test the result.

maybe you do have bad ram?

note this linkstation is running debian lenny armel with a 2.6.16 rebuilt buffalo kernel I built a long time ago.
Quote:
HS-DHGLCC8:/usr/src# uname -r
2.6.16.57-lsp_eabi-dh_v4
HS-DHGLCC8:/usr/src#

(this older kernel needs lenny's udev to be held back at an older version)
(I run 2.6.33 on a kurobox pro)


Last edited by duncan_h on Sun Mar 07, 2010 6:58 pm, edited 1 time in total.

Top
   
PostPosted: Sun Mar 07, 2010 5:53 pm 
Offline
Newbie

Joined: Sun Feb 22, 2009 5:14 pm
Posts: 24
I too have attempted to compile 2.6.33 using make oldconfig on your 2.6.32.7 config file.

Compiled successfully, but it doesn't boot; not getting anything through netcat even.

Mind you, I also attempted to compile 2.6.32.9 using your 32.7 config and had exactly the same result. Not sure if it's something I have set up wrong, I've never had any trouble simply installing the kernels you've built.

What I do is:

cp yourconifgconfig /newkernel/.config
make oldconfig
make uImage
make modules
sudo make modules_install
sudo cp /newkernel/arch/arm/boot/uImage /boot/uImage-2.6.33
sudo ln -s -f uImage-2.6.33 uImage

My uImage is a similar size and I symlink it in the same way. Modules installed in the right place.

Not sure what I'm missing really. Happy to test if you can help!

Cheers.


Top
   
PostPosted: Sun Mar 07, 2010 6:51 pm 
Offline
Regular Member

Joined: Mon Oct 15, 2007 5:21 am
Posts: 144
@mipmapped

you say you did
"make uImage"

Perhaps you don't realize that to make a uImage for Linkstation Pro/live or kurobox pro
you need to add a special string to the top of the uImage needed for the Linkstation to recognize the uImage.
(If I remember correctly, different strings are needed for the Linkstations and the Kurobox Pro)

you need to "make zImage", then use the native
"mkimage" in a special way to create a working uImage.

You can find instructions in the wiki.
I believe that deb's build script has this step included. Look at it to see what to
do , even if you don't use his script.


Top
   
Display posts from previous:  Sort by  
Post new topic  Reply to topic  [ 743 posts ]  Go to page Previous 145 46 47 48 49 50 Next

All times are UTC+01:00


Who is online

Users browsing this forum: No registered users and 3 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:
Powered by phpBB® Forum Software © phpBB Limited