Buffalo NAS-Central Forums

Welcome to the Linkstation Wiki community
It is currently Wed Aug 15, 2018 10:31 am

All times are UTC+01:00




Post new topic  Reply to topic  [ 43 posts ]  Go to page Previous 1 2 3
Author Message
PostPosted: Sat Nov 21, 2009 8:41 am 
Offline
Site Admin
User avatar

Joined: Sun Jul 17, 2005 4:34 pm
Posts: 5332
According to /etc/default/boot_new.sh_local

STOCK_KERNELKB="2.4.17_kuro-box"

'loaderKB.o' is the module of choice.

Please try and load the variant-latest kernel manually. At http://hvkls.dyndns.org/downloads/tmp/ you can find a more recent kernel. If any of them works, the answer to your .dtb question is 'yes'. We shall see.


Top
   
PostPosted: Tue Nov 24, 2009 5:42 am 
Offline
Newbie

Joined: Tue Nov 10, 2009 4:58 am
Posts: 10
Location: San Jose, CA
loaderKB.o (as well as any of the others that will load at all) indicates that 'init_module: Cannot allocate memory'

I am not sure what that implies (whether no memory can be allocated or if the specific request cannot be satisfied because some amount or type of memory cannot be allocated).

In either case, it does not get very far.

I am looking into updating the original loader.o (for which I have found the apparent source) using the mechanism for loading a kernel with a .dtb file used in U-Boot.

Do you still have archived any of the older kernels (ideally something 2.6.18.5-2.6.18.8)?

That is the version that I need for the XTables Additions for the firewall.


Top
   
PostPosted: Tue Nov 24, 2009 6:10 am 
Offline
Site Admin
User avatar

Joined: Sun Jul 17, 2005 4:34 pm
Posts: 5332
I would love to have a static loader version too. It would solve all problems.

You can find older versions of the kernel, e.g. *-nfs-v14*, in my archive directory.


Top
   
PostPosted: Tue Nov 24, 2009 1:27 pm 
Offline
Site Admin
User avatar

Joined: Mon Aug 28, 2006 1:15 am
Posts: 2606
andre, a question for you, for whatever box you are running 2.6.30.1 on ...

What mtd partitions do you see? Have they changed for you?

avtobiff (maintainer of a Debian package) is asking about something that relates to the default mtd partition structure. To me it looks like it has changed ... do you see the old mtd0, mtd1, mtd2, mtd3, etc., or just mtd0, in these newer kernels?

_________________
LS1 (foonas, nfs, Tranmission & p910nd print server, Firefly for my Roku)
LS-HG500 (Lenny)
Various LS-Pros v1,v2 (unbricked w/ serial & jtag)
KuroPro, LS2 & KuroHG (foonas)
Working on davysweather.dyndns.org lately...

=> wooohooo!
wooohooo!
Unknown command 'wooohooo!' - try 'help'


Top
   
PostPosted: Wed Nov 25, 2009 4:46 pm 
Offline
Site Admin
User avatar

Joined: Sun Jul 17, 2005 4:34 pm
Posts: 5332
I'm on 2.6.31.6 (the latest stable upstream kernel) and haven't seen any mtd devices since 2.6.29!


Top
   
PostPosted: Wed Nov 25, 2009 4:46 pm 
Offline
Site Admin
User avatar

Joined: Sun Jul 17, 2005 4:34 pm
Posts: 5332
I'm on 2.6.31.6 (the latest stable upstream kernel) and haven't seen any mtd devices since 2.6.29!


Top
   
PostPosted: Wed Nov 25, 2009 10:13 pm 
Offline
Site Admin
User avatar

Joined: Mon Aug 28, 2006 1:15 am
Posts: 2606
OK, that agrees with what both shihsung (steven shih, ported linux 2.6.30.5 to the mipsel LS2) and lyakh (did the same for vanilla on the PPC LS's). I can't remember exactly when those partitions disappeared, but .29 sounds about right.

They have both pointed out to me that those partitions can be defined at the kernel command line just before booting.

I guess this is something that avtobiff needs to be aware of ... seeing Linux documentation that spells out the change (like in the changelog) would be nice. I looked for it a bit, but never saw the official notice of a change in how it would be handled.

_________________
LS1 (foonas, nfs, Tranmission & p910nd print server, Firefly for my Roku)
LS-HG500 (Lenny)
Various LS-Pros v1,v2 (unbricked w/ serial & jtag)
KuroPro, LS2 & KuroHG (foonas)
Working on davysweather.dyndns.org lately...

=> wooohooo!
wooohooo!
Unknown command 'wooohooo!' - try 'help'


Top
   
PostPosted: Thu Nov 26, 2009 6:18 am 
Offline
Site Admin
User avatar

Joined: Sun Jul 17, 2005 4:34 pm
Posts: 5332
The change was rather from .28 to .29 than from .29 to .30. Remember the kernel you sent me when I was in uboot trouble? That was the last one that worked for me. So I think the answer is in the 2.6.29 Changelog?


Top
   
PostPosted: Fri Nov 27, 2009 9:47 am 
Offline
Total Newbie

Joined: Fri Nov 27, 2009 9:27 am
Posts: 2
Hello,

I tried updating my kernel a few days before. My system was a old sarge system. The webinstaller bricked my box (box was in em mode). I moved the hard disk to a second box. This bricked my second box too :-( .

I reinstalled FreeLink 1.11 successfully. Because there are no debian sarge repositories available, I switched to etch. Everythink works fine, BUT:

I can't load the 2.6-kernel. I have no idea why. Below my install log which is written by me during the installation. Me little research show the following situation:

Code:
/usr/local/sbin/kernel26.sh


Boots the box, but not to 2.6 kernel. But no boot.log is written to /boot . Trying to load the kern by hand fails:

Code:
root@LinkStation:/# /boot/insmod.ppc -f  /boot/loaderLS.o kernel=/boot/vmlinux.bin
Warning: loading /boot/loaderLS.o will taint the kernel: forced load
  See http://www.tux.org/lkml/#export-tainted for information about tainted modules
/boot/loaderLS.o: init_module: Cannot allocate memory
Hint: insmod errors can be caused by incorrect module parameters, including invalid IO or IRQ parameters.
      You may find more information in syslog or the output from dmesg




root@LinkStation:/# dmesg

loader module loaded
kernel=/boot/vmlinux.bindms
cmdline=root=/dev/hda1

root@LinkStation:/# tail /var/log/messages


Nov 27 04:09:20 LinkStation kernel: loader module loaded
Nov 27 04:09:20 LinkStation kernel: kernel=/boot/vmlinux.bin
Nov 27 04:09:20 LinkStation kernel: cmdline=root=/dev/hda1



root@LinkStation:/# ldd /boot/insmod.ppc
   libc.so.6 => /lib/libc.so.6 (0x0fea9000)
   /lib/ld.so.1 (0x30000000)
root@LinkStation:/#


Who can help me ?

Installation log:
Code:
# Switching to etch
###################
root@LinkStation:/# vi /etc/apt/sources.list

#deb http://mirrors.kernel.org/debian/ stable main
deb http://mirrors.kernel.org/debian/ etch main
#deb-src http://mirrors.kernel.org/debian/ stable main
deb-src http://mirrors.kernel.org/debian/ etch main

#deb http://security.debian.org/ stable/updates main
deb http://security.debian.org/ etch/updates main



root@LinkStation:/var/cache/apt# apt-get update
# root@LinkStation:/var/cache/apt# ####apt-get upgrade
root@LinkStation:/var/cache/apt# apt-get dist-upgrade





Debian Configuration                                                           
 ��������������������������Ĵ Configuring debconf ��������������������������Ŀ   
 � Packages that use debconf for configuration share a common look and       � 
 � feel. You can select the type of user interface they use.                 � 
 �                                                                           � 
 � The dialog frontend is a full-screen, character based interface, while    � 
 � the readline frontend uses a more traditional plain text interface, and   � 
 � both the gnome and kde frontends are modern X interfaces, fitting the     � 
 � respective desktops (but may be used in any X environment). The editor    � 
 � frontend lets you configure things using your favorite text editor. The   � 
 � noninteractive frontend never asks you any questions.                     � 
 �                                                                           � 
 � Interface to use:                                                         � 
 �                                                                           � 
 �                             Dialog                                       � 
 �                             Readline          #                           � 
 �                             Gnome                                        � 
 �                                                                           � 
 �                                                                           � 
 �                    <Ok>                        <Cancel>                   � 
 �                                                                           � 
 ����������������������������������������������������������������������������   
                                                                               
       Dialog                                                                         


Debian Configuration                                                           
                                                                               
                                                                               
                                                                               
                                                                               
                                                                               
                �����������Ĵ Configuring debconf ������������Ŀ                 
                � Ignore questions with a priority less than:  �               
                �                                              �               
                �                   critical                   �               
                �                   high                       �               
                �                   medium                     �               
                �                   low                        �               
                �                                              �               
                �                                              �               
                �          <Ok>              <Cancel>          �               
                �                                              �               
                �����������������������������������������������                 
                                                                               
                                                                               
               medium                                                                 
                                                                               
                                                                               
                                                                               











Do you want to upgrade glibc now? [Y/n] Y

Do you wish to restart services? [Y/n]

*** halt (Y/I/N/O/D/Z) [default=N] ? N

*** reboot (Y/I/N/O/D/Z) [default=N] ? N

root@LinkStation:/var/cache/apt# uname -a
Linux LinkStation 2.4.17_mvl21-sandpoint #997 2005ǯ 2�� 25�� ������ 19:29:09 JST ppc GNU/Linux

root@LinkStation:/# reboot




# Install 26 kernel
###################


root@LinkStation:/# wget http://hvkls.dyndns.org/downloads/latest-webinstaller.tar.gz
root@LinkStation:/# tar -C / -xvzf latest-webinstaller.tar.gz


###/usr/local/sbin/webinstaller-kernelinst-dryrun.sh





/usr/local/sbin/webinstaller-kernelinst.sh


/usr/local/sbin/fix_moduleinittools.sh
--> Remember to configure /etc/default/avr_evtd according to
--> http://hvkls.dyndns.org/downloads/documentation/README-upgradehelper.html

/usr/local/sbin/fix_moduleinittools.sh
root@LinkStation:/# apt-get --reinstall install wget diff modutils module-init-tools


Do you want to continue [Y/n]? Y
Install these packages without verification [y/N]? y

root@LinkStation:/# /usr/local/sbin/webinstaller-kernelinst.sh

root@LinkStation:/# /usr/local/sbin/kernel26.sh


root@LinkStation:/# /boot/insmod.ppc -f  /boot/loaderLS.o kernel=/boot/vmlinux.bin
Warning: loading /boot/loaderLS.o will taint the kernel: forced load
  See http://www.tux.org/lkml/#export-tainted for information about tainted modules
/boot/loaderLS.o: init_module: Cannot allocate memory
Hint: insmod errors can be caused by incorrect module parameters, including invalid IO or IRQ parameters.
      You may find more information in syslog or the output from dmesg




root@LinkStation:/# dmesg

loader module loaded
kernel=/boot/vmlinux.bindms
cmdline=root=/dev/hda1

root@LinkStation:/# tail /var/log/messages


Nov 27 04:09:20 LinkStation kernel: loader module loaded
Nov 27 04:09:20 LinkStation kernel: kernel=/boot/vmlinux.bin
Nov 27 04:09:20 LinkStation kernel: cmdline=root=/dev/hda1



root@LinkStation:/# ldd /boot/insmod.ppc
   libc.so.6 => /lib/libc.so.6 (0x0fea9000)
   /lib/ld.so.1 (0x30000000)
root@LinkStation:/#




Top
   
PostPosted: Fri Nov 27, 2009 4:44 pm 
Offline
Site Admin
User avatar

Joined: Sun Jul 17, 2005 4:34 pm
Posts: 5332
This thread is about troubleshooting v118. Use variant-legacy until then:

touch /boot/variant-legacy
webinstaller-kernelinst.sh

You should definitely reboot after apt-get dist-upgrading the system prior to that!

However,

root@LinkStation:/# dmesg
loader module loaded
kernel=/boot/vmlinux.bindms
cmdline=root=/dev/hda1

indicates a misconfiguration, it should be "kernel=/boot/vmlinux.bin".


Top
   
PostPosted: Fri Nov 27, 2009 9:30 pm 
Offline
Total Newbie

Joined: Fri Nov 27, 2009 9:27 am
Posts: 2
Thank you for quick response.

Yes sure, this is a discussion about the latest kernel, which I tried to install. Maybe I understood somethink wrong ? What would be the best place for my question ?

Yes, I rebooted the box after dist-upgrade and before i running your nice webinstaller.

Yes, the legacy variant is working. Thank you.

I tried again installing the latest variant, with no success. No bootlog, only the file try_new_kernel.running.

Do you have any ideas, what could be wrong ?


Top
   
PostPosted: Sat Dec 26, 2009 11:18 am 
Offline
Newbie

Joined: Sun Oct 30, 2005 4:58 am
Posts: 52
Location: Braunschweig, DE
Hi,
yesterday I've tried webinstaller to update from an rather old kernel version "Linux version 2.6.23.14" to this one. My Freelink was still on sarge, so I'm afraid, I missed some important steps. I followed instructions

Code:
--> You need to take care of that yourself:
/usr/local/sbin/fix_moduleinittools.sh
apt-get --reinstall install wget diff modutils module-init-tools # pre-Lenny systems
apt-get --reinstall install wget diff module-init-tools # Lenny systems
apt-get --reinstall install lm-sensors # Tera only
--> Then re-run the webinstaller.


but "modutils" ran into an error. After freeing some disk space, it was on track again, I thought. However, webinstaller was finishing asking for a reboot. Unfortunately, this leads now in "Kernel Panic":

Code:
Bootcode Ver.1.11 for [HGLAN]
Build:May 12 2005 [14:53:32]
DID_RTL8110S
DID_IT8211F(12)
DID_720101_U1
DID_720101_U2
******* Product Information *******
----------------------------------
Product Name: HD-HGLAN(IEMITSU)
          VER: 2.06
         Date: 2005/8/3 9:32:3
----------------------------------
Firmware check:done.
>>root=/dev/hda1
hit any key to boot EM mode.

Now Loading...done.
Now Booting
KERNELBASE=c0000000 r6=900030 r7=90003e
cmd_line=root=/dev/hda1
--- cmd=root=/dev/hda1
Memory BAT mapping: BAT2=128Mb, BAT3=0Mb, residual: 0Mb

Linux version 2.4.20_mvl31-ppc_linkstation (root@yabutar) (gcc version 2.95.3 20010315 (release/MontaVista)) #2 2005ǯ 8�� 3�� ������ 09:31:46 JST
BUFFALO Network Attached Storage Series
(C) 2002-2005 BUFFALO INC.
On node 0 totalpages: 32768
[...........]
Found: ST M29W324DB
linkstation_flash: Found 1 x16 devices at 0x0 in 8-bit mode
number of JEDEC chips: 1
Using physmap partition definition
Creating 5 MTD partitions on "linkstation_flash":
0x00000000-0x00300000 : "mtd0"
0x00300000-0x00370000 : "mtd1"
0x00370000-0x00380000 : "mtd2"
0x00380000-0x00400000 : "mtd3"
0x00000000-0x00400000 : "mtd4"
usb.c: registered new driver usbdevfs
usb.c: registered new driver hub
ehci_hcd 00:0e.2: PCI device 1033:00e0
ehci_hcd 00:0e.2: irq 19, pci mem c9002f00
usb.c: new USB bus registered, assigned bus number 1
PCI: 00:0e.2 PCI cache line size set incorrectly (0 bytes) by BIOS/FW, correcting to 32
ehci_hcd 00:0e.2: USB 2.0 enabled, EHCI 1.00, driver 2003-Dec-29/2.4
hub.c: USB hub found
hub.c: 5 ports detected
usb-ohci.c: USB OHCI at membase 0xc9004000, IRQ 19
usb-ohci.c: usb-00:0e.0, PCI device 1033:0035
usb.c: new USB bus registered, assigned bus number 2
hub.c: USB hub found
hub.c: 3 ports detected
usb-ohci.c: USB OHCI at membase 0xc9006000, IRQ 19
usb-ohci.c: usb-00:0e.1, PCI device 1033:0035
usb.c: new USB bus registered, assigned bus number 3
hub.c: USB hub found
hub.c: 2 ports detected
usb.c: registered new driver usblp
printer.c: v0.13: USB Printer Device Class driver
Initializing USB Mass Storage driver...
usb.c: registered new driver usb-storage
USB Mass Storage support registered.
NET4: Linux TCP/IP 1.0 for NET4.0
IP Protocols: ICMP, UDP, TCP, IGMP
IP: routing cache hash table of 1024 buckets, 8Kbytes
TCP: Hash tables configured (established 8192 bind 8192)
NET4: Unix domain sockets 1.0/SMP for Linux NET4.0.
NET4: AppleTalk 0.18a for Linux NET4.0
RAMDISK: Compressed image found at block 0
Freeing initrd memory: 1999k freed
EXT2-fs warning: checktime reached, running e2fsck is recommended
VFS: Mounted root (ext2 filesystem).
kjournald starting.  Commit interval 5 seconds
EXT3-fs: mounted filesystem with ordered data mode.
VFS: Mounted root (ext3 filesystem) readonly.
Trying to move old root to /initrd ... okay
Freeing unused kernel memory: 76k init
FATAL: kernel toKernel panic: Attempted to kill init!
o old
 <0>Rebooting in 180 seconds..


I'm wondering, why it is still booting the "old 2.4" Kernel. This happend before from time to time, but I didn't ran into a kernel panic. I just logged in and did a "kernel26.sh". Maybe the "webinstaller" moved them somewhere else, as in /boot I could only find System.map, config and vmlinux for the new 2.6.30.1.

Does someone have a hint, where I could start over ? Maybe flashing u-boot ? Or adding old 2.4 Kernel files ?

_________________
LS HD-HG250LAN Freelink 1.11, Kernel 2.6, NFS
TS HS-DH2.0TGL, RAID-5, Stock-FW, NFS
UPS APC ES 500


Top
   
PostPosted: Sat Jan 02, 2010 4:08 pm 
Offline
Newbie

Joined: Sun Oct 30, 2005 4:58 am
Posts: 52
Location: Braunschweig, DE
Okay, after some more investigations on my system I couldn't figure out, how to repair, so I decided to start over from the scratch with Freelink 1.11.
I'll now try to apply uboot, debian lenny and kernel 2.6 again.

_________________
LS HD-HG250LAN Freelink 1.11, Kernel 2.6, NFS
TS HS-DH2.0TGL, RAID-5, Stock-FW, NFS
UPS APC ES 500


Top
   
Display posts from previous:  Sort by  
Post new topic  Reply to topic  [ 43 posts ]  Go to page Previous 1 2 3

All times are UTC+01:00


Who is online

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