Buffalo NAS-Central Forums

Welcome to the Linkstation Wiki community
It is currently Wed May 23, 2018 2:35 am

All times are UTC+01:00




Post new topic  Reply to topic  [ 10 posts ] 
Author Message
PostPosted: Tue Jan 15, 2008 4:24 pm 
Offline
Site Admin
User avatar

Joined: Sun Jul 17, 2005 4:34 pm
Posts: 5332
Linux 2.6/PPC kernels for Linkstation/KuroBox/HG/HS are available from http://hvkls.dyndns.org/. See the Changelog for details (MSIE > 5.5 is problematic).

PLEASE use the webinstaller to download or install the kernel package, including its variants. Thanks for your cooperation!

Anyone violating the server policy risks to be denied service, if necessary permanently.


Top
   
PostPosted: Thu Jan 24, 2008 9:12 am 
Offline
Newbie

Joined: Sun Oct 30, 2005 4:58 am
Posts: 52
Location: Braunschweig, DE
Hi,

Kernel 2.6.23.14 is running on my HG after I upgraded from 2.6.17.7. My main reason for upgrading was because
I was annoyed from my old setting does not come up again after shutdown. I always had to unplug power, reboot
into stock 2.4 and reboot into 2.6 after renaming try_newkernelHG.running.

Now, this problem slightly changed, as the box is no longer powering down after pressing the button or
doing a "shutdown -h now". It just reboots into this new kernel.

With soft-reboot, my USB UPS did not get registered, I have to phyically replug the USB connector. And lsusb looks strange after this update:
Code:
nas:/etc/init.d# lsusb
Unknown line at line 8015
Unknown line at line 8016
Unknown line at line 8017
Unknown line at line 8018
Unknown line at line 8019
Unknown line at line 8020
Unknown line at line 8021
Unknown line at line 8022
Unknown line at line 8023
Unknown line at line 8024
Unknown line at line 8025
Unknown line at line 8026
Bus 003 Device 001: ID 0000:0000
Bus 002 Device 001: ID 0000:0000
Bus 001 Device 001: ID 0000:0000
nas:/etc/init.d#

Any idea, where to look into ? I thought maybe it's the avr or serial port, but
Code:
echo -n "WWWW" > /dev/ttyS1
turns on the red light.

_________________
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: Thu Jan 24, 2008 2:34 pm 
Offline
Site Admin
User avatar

Joined: Sun Jul 17, 2005 4:34 pm
Posts: 5332
Hmm. I would do this:

rm -r /boot /etc/default/avr_evtd
webinstaller-kernelinst.sh
kernel26.sh

If it doesn't wok, you can try variant-legacy, if it still doesn't work, variant-nfs.

http://hvkls.dyndns.org/downloads/docum ... iants.html


Top
   
PostPosted: Sun Jan 27, 2008 9:33 am 
Offline
Newbie

Joined: Sun Oct 30, 2005 4:58 am
Posts: 52
Location: Braunschweig, DE
Thanks. This cleaned up my /boot folder, where I had some files, I was not sure, if they
are still necessary.

Unfortunately lsusb looks still the same and cold boot gets stuck with Diag LED flashing 6 times.
After replug power, stock kernel is loaded again and I have to do a kernel26.sh again to get back
to the new one.

Code:
******* Product Information *******
----------------------------------
Product Name: HD-HGLAN(IEMITSU)
          VER: 2.06
         Date: 2005/8/3 9:32:3
----------------------------------
....
Linux version 2.4.20_mvl31-ppc_linkstation (root@yabutar) (gcc version 2.95.3 20010315 (release/MontaVista)) #2 2005
....
Warning: loading /boot/loaderHG.o will taint theloader module loaded
 kernel: forced kernel=/boot/vmlinux.bin
 load
   See httpcmdline=root=/dev/hda1
://www.tux.org/lkml/#export-tainted for information about tainted modules
KERNELBASE=c0000000 (r6=75c571c r7=75c572a) r3=0 (r4=0 r5=0)
---cmdline=root=/dev/hda1
Linux version 2.6.23.14 (root@ls) (gcc version 4.1.2 20061115 (prerelease) (Debian 4.1.1-21)) #52 Tue Jan 15 14:32:00 CET 2008
Early serial console at MMIO 0x80004600 (options '57600n8')
console [uart0] enabled
....
Console: colour dummy device 80x25
console handover: boot [uart0] -> real [tty0]

After this point, the serial console switches to another baud rate. Is there a way, to avoid changing of baudrate, so the /dev/ttyS0
remains console output ?

I'll also try kernel variants.

_________________
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: Sun Jan 27, 2008 11:55 am 
Offline
Site Admin
User avatar

Joined: Sun Jul 17, 2005 4:34 pm
Posts: 5332
There is no way, since Buffalo has switched /dev/ttyS[01] and the upstream kernel uses the correct order.

What do your files /etc/default/boot_new.sh* look like? Have you altered these or /etc/default/avr_evtd in any way? Do you have the appropriate softlinks in /etc/rc?.d/ (Frellink) or /etc/rc.d/rc?.d/ (Openlink)?

EDIT: I took a look at my development HG/uboot and saw I found the following modifications necessary:

-------/etc/init.d/halt----------
#! /bin/sh
#
# halt Execute the halt command.
#
# Version: @(#)halt 2.75 19-May-1998 miquels@cistron.nl
#

PATH=/sbin:/bin:/usr/sbin:/usr/bin

# See if we need to cut the power.
if [ -x /etc/init.d/ups-monitor ]
then
/etc/init.d/ups-monitor poweroff
fi

# AB
# echo -n 'EEEE' > /dev/ttyS1
# code borrowed from /etc/init.d/avr_etvd
DAEMON=/usr/sbin/avr_evtd
if [ -x $DAEMON ] ; then
DEVICE=/dev/ttyS0
# Search for valid port address
PORT_ADDRESS=`$DAEMON -i -d /dev/ttyS1`
if [ $PORT_ADDRESS -eq 80004500 ] ; then DEVICE=/dev/ttyS1 ; fi
fi
echo -n 'EEEE' > $DEVICE
# /AB
halt -d -f -i -p
-------/etc/init.d/halt----------

-------/usr/local/sbin/halt----------
#! /bin/sh
/sbin/shutdown -h now
-------/usr/local/sbin/halt----------


Top
   
PostPosted: Mon Jan 28, 2008 2:11 pm 
Offline
Newbie

Joined: Sun Oct 30, 2005 4:58 am
Posts: 52
Location: Braunschweig, DE
Hmm, I found ppc_uartd was still started, so I removed with
Code:
update-rc.d -f ppc_uartd remove 
, but no change.
Every cold boot stucks a few seconds after the console died :cry:
Code:
Console: colour dummy device 80x25
console handover: boot [uart0] -> real [tty0]
��������������������������������

If I restart from stock kernel with kernel26.sh, it's working. You mentioned the halt-script, do you think the AVR could be left in a state, where tainting the stock kernel is not working any more ? For me it seems like there are more commands running after the console died and the system got stuck at a later stage. As I'm newbie, do you have a hint, how I can find out this point of no return ? I thought there was an article in the wiki on LS boot sequences, but I couldn't find so far.

So this is for reference (Freelink):
Code:
nas:~# ls /etc/rc0.d/
K10boot_new.sh  K20dbus-1   K20ssh         K79nfs-common         K89hotplug-net  S20sendsigs      S35networking
K11cron         K20exim4    K20webmin      K80nfs-kernel-server  K89klogd        S30urandom       S36ifupdown
K19nis          K20inetd    K25hwclock.sh  K86ppp                K90sysklogd     S31umountnfs.sh  S40umountfs
K19samba        K20makedev  K75hdparm      K89atd                K95avr_evtd     S32portmap       S90halt
nas:~# ls /etc/rc2.d/
K88twonky                  S11klogd     S18portmap  S20dbus-1  S20makedev            S20ssh         S89atd        S99stop-bootlogd
S01bootloader-linkstation  S12avr_evtd  S19nis      S20exim4   S20nfs-kernel-server  S20webmin      S89cron       S99twonky
S10sysklogd                S14ppp       S20apservd  S20inetd   S20samba              S21nfs-common  S99rmnologin
nas:~# ls /etc/rc6.d/
K10boot_new.sh  K20dbus-1   K20ssh         K79nfs-common         K89hotplug-net  S20sendsigs      S35networking
K11cron         K20exim4    K20webmin      K80nfs-kernel-server  K89klogd        S30urandom       S36ifupdown
K19nis          K20inetd    K25hwclock.sh  K86ppp                K90sysklogd     S31umountnfs.sh  S40umountfs
K19samba        K20makedev  K75hdparm      K89atd                K95avr_evtd     S32portmap       S90reboot
nas:~#     


In /etc/default/avr_evtd I only altered "DEBUG=ON":
Code:
# Sample avr_evtd daemon configuration file
# PLEASE EDIT THIS FILE TO SUIT
LOG=/var/log
DEBUG=ON
# Set to YES to enable the EM-Mode feature, default no
EMMODE=NO
#
# Timed shutdown flag (ON enables timed power down/up only
# or use days of the week MONWEDSAT etc
# if SHUTDOWN and POWERON are also specified)
TIMER=OFF
# To override the device scan, specify the desired
# serial port connection to the AVR below and remove the
# comment
DEVICE=/dev/ttyS1
# MACRO day/group switching ON/OFF times in 24hr HH:MM
# MON=ON=08:00,OFF=21:00,ON=23:30
# TUE=OFF=02:30,ON=09:00,OFF=21:45
SUN=ON=07:30,OFF=22:50
WED-FRI=ON=08:00,OFF=18:10,ON=18:20,OFF=19:10,ON=19:20
SAT=ON=07:30,OFF=08:30
# SUN=ON=08:00,OFF=21:55
# Shutdown (default) time specified in 24hr format HH:MM
SHUTDOWN=
# Power on (default) time specified in 24hr format HH:MM
POWERON=
# Disk check, set to OFF or a value (0-100) specifying a
# percentage used at which the disk LED will illuminate
DISKCHECK=90
# Disk/AVR refresh rate (seconds), default 40
REFRESH=40
# Hold time (seconds) for button power-off, default 3
HOLD=3
# Enable/disable continous disk full messages, default off
DISKNAG=OFF
# Fan stationary fault timer (seconds), default 30
FANSTOP=30


I did not change boot_new.sh
Code:
# bootloader for kernel 2.6 on Buffalo Linkstation family and Terastation machines
# written by André Berger (c)2006-2007 <https://hvkls.dyndns.org/contact.html>
#
# # bootloader uses loader.o to load a modified kernel into a Linkstation or Terastation
#
# NO_START controls the bootloader (0=activated, 1=deactived)
NO_START="0"

# IF YOU NEED CUSTOM SETUP, AND KNOW WHAT YOU'RE DOING, EDIT /etc/default/boot_new.sh_local


also no change in boot_new.sh_local
Code:
# bootloader for kernel 2.6 on Buffalo Linkstation family and Terastation machines
# written by André Berger (c)2006-2007 <https://hvkls.dyndns.org/contact.html>
#
# # bootloader uses loader.o to load a modified kernel into a Linkstation or Terastation
#
# STOCK_KERNEL is the flashrom kernel (use uname -r to find out what it is)
STOCK_KERNELHG="2.4.20_mvl31-ppc_linkstation"
STOCK_KERNELII="2.4.20_mipsel_linkstation"
STOCK_KERNELKB="2.4.17_kuro-box"
STOCK_KERNELKG="2.4.20_mvl21"
STOCK_KERNELKO="2.4.17_mvl21"
STOCK_KERNELLS="2.4.17_mvl21-sandpoint"
STOCK_KERNELTS="2.4.20_mvl31-ppc_terastation"
STOCK_KERNELUB="2.4.33.3-list.mg.2-v3"

# *DO NOT TOUCH* unless you know what you're doing

# For the Tera booting from /dev/hdb1, set $DISK_MNT, $DISK_MNT, $BOOTLOADERARGS

# YOU CANNOT CONFIGURE THE OPTION kernel= WITH $BOOTLOADERARGS!
#BOOTLOADERARGS=' cmdline="root=/dev/hdb1" '
#DISK="/dev/hdb1" # must be set up in /etc/fstab, mounting to $DISK_MNT, and match $BOOTLOADERARGS
#DISK_MNT="/mnt/kernel" # no trailing slashes; "/boot" is appended automatically to $DISK_MNT

#MIPS24_HACK="1" # set to "1" to activate

_________________
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: Mon Jan 28, 2008 2:43 pm 
Offline
Site Admin
User avatar

Joined: Sun Jul 17, 2005 4:34 pm
Posts: 5332
It's the same system I have got, but mine is on OpenLink.

I wouldn't have removed the ppc_uartd startup scripts if I were you, see my upgradehelper advice.

The console handover msg looks like this here on my HG:

console handover: boot [uart0] -> real [ttyS0]
serial8250.1: ttyS1 at MMIO 0x80004500 (irq = 25) is a 16550A

Are there any peripherals connected? Disconnect them!


Top
   
PostPosted: Wed Jan 30, 2008 3:30 pm 
Offline
Newbie

Joined: Sun Oct 30, 2005 4:58 am
Posts: 52
Location: Braunschweig, DE
No peripherals connected, still no success. I went through couple of scripts, and found probably
an anomalie:
Code:
nas:~# ll /sbin/avr_evtd
-rwxr-xr-x  1 root staff 12704 2006-11-05 06:04 /sbin/avr_evtd
nas:~# /sbin/avr_evtd
Linkstation/Kuro AVR daemon Version 1.7.2


nas:~# ll /usr/local/sbin/avr_evtd*
-rwxr-xr-x  1 root root 12468 2006-08-04 13:13 /usr/local/sbin/avr_evtd
nas:~# /usr/local/sbin/avr_evtd
Linkstation/Kuro AVR daemon Version 1.6.2


Two versions looks strange to me. I renamed one, but still no success. I played a little with /etc/init.d/avr_evtd around
and set CONSOLE=ON. avr_evtd is not started, but console output is still on. Unfortunately only if I boot into
Stockkernel....

I still cannot find out, why the cold boot of kernel26 is crashing and warmboot of kernel26 works.

_________________
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: Sun Feb 03, 2008 2:44 am 
Offline
Newbie

Joined: Sun Oct 30, 2005 4:58 am
Posts: 52
Location: Braunschweig, DE
Hi Andre,

thank you very much for your kind help. I guess, I have to dig more into the scripts of my HG to find the reason for its coldboot behaviour. I don't think it's related to this kernel release. Maybe I start over from the scratch with stock-firmware, freelink 1.11 and your latest kernel - or I try uboot.

BR, ja1uyn

_________________
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: Sun Feb 03, 2008 12:26 pm 
Offline
Site Admin
User avatar

Joined: Sun Jul 17, 2005 4:34 pm
Posts: 5332
Why not... Have you tried usbreset already?


Top
   
Display posts from previous:  Sort by  
Post new topic  Reply to topic  [ 10 posts ] 

All times are UTC+01:00


Who is online

Users browsing this forum: Baidu [Spider] and 1 guest


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