Buffalo NAS-Central Forums

Welcome to the Linkstation Wiki community
It is currently Sun Jan 21, 2018 2:06 am

All times are UTC+01:00




Post new topic  Reply to topic  [ 51 posts ]  Go to page 1 2 3 4 Next
Author Message
PostPosted: Fri Apr 17, 2009 4:45 am 
Offline
Site Admin
User avatar

Joined: Mon Aug 28, 2006 1:15 am
Posts: 2606
Image
Etch and Lenny tarballs for LS1/KuroBox and LS-HG/KuroBoxHG ... Available for use and testing: I've tested them and found no problems, but if you find anything wrong please post back and I'll try to fix it.


Downloads :
LS1 : Etch 2.6.28.8 + 2.4.37 legacy
LS1 : Lenny 2.6.28.8

LS-HG : Etch 2.6.28.8 + 2.4.37 legacy
LS-HG : Lenny 2.6.28.8


Features:
    the 2.4 and 2.6 uImage kernels require u-boot with ftd support (our 1.2.0 version posted in downloads will do fine for this, but a new custom uboot w/ a variety of built-in scripts for easy use is under testing and on its way)
    the 2.4 vmlinux.bin kernel _may_ be bootable with the stock bootloader - if this is the case, then we may be able to install Etch with the LSUpdater Windows app.
    fw_printenv and fw_setenv, ie. uboot-utils, already installed
    avr-evtd
    mtd* and mtdblock* already in /dev
    ssh & scp for access ( root password is "debian" )
    default standard 192.168.11.150 ip address, with dhcp fallback network setup
    default 2.6.28.8 uImage kernel w/ support for ext4
    default /etc/fstab setup is a simple root=sda1, swap=sda2, mnt=sda3 scheme
    /etc/inittab is preslugged with commented-out ttySn lines for serial access (decomment according to kernel to enable)
    fix_ext2_magic included (in /usr/local/sbin)
    Etch tarballs also contain:
      2.4.37 uImage kernel + modules, and matching uloader.o for UBoot RAM build testing
      /etc/fstab-2.4 for quick changeover to 2.4 booting


To install:
    1. tftpboot your LS1 with firmimg.bin or foonas-em
    2. set up your hdd : sda1 as ext3 root, sda2 as swap, and sda3 as ext3/4 /mnt
    3. untar the tarball on sda1
    4. reboot

==============================================================================

(April 16, 2009)
The Sarge tarball we have out there as "FreeLink" for PPC boxes seems a bit long in the tooth...
I'm currently debootstrapping for my LS1, and once I make an image for it will post it... I would like to make the following:

LS1:
Etch w/ 2.6.29.1 (default kernel) & 2.4.37 (legacy kernel), for uBoot equipt boxes (will include /etc/fstab-2.4.37 preslugged for)
Lenny w/ 2.6.29.1+, for uBoot equipped boxes

LS-HG:
... the same as above...

Can anyone think of anything else that must go in? What am I forgetting?

1. I will stick to the default schemes that we had set up before,
2. and add in everything that andre had in his upgradehelper... (avr_evtd, correct mtd device nodes, ...)
3. + fw_printenv & fw_setenv + fw_env.config
4. What about the line in /etc/inittab for serial console access? should it look like this?
Code:
T0:23:respawn:/sbin/getty -L ttyS0 57600
I'm not sure about the baud rate on these boxes... ?
5. ssh, but not telnet?
scp ?
ntpdate ?
udev ? (or maybe leave udev out ... the user can install this and we avoid the udev network rules problem that sometimes locks one out of networking)

6. How about an on hdd setup of /boot-em/ with 2.6 and 2.4 EM utilities installed there already? with a custom uboot that already has scripts built in for EM booting into 2.4 or 2.6, via hdd and tftp? The scripts are easy to hard-code into the uboot environment.
7. Debian ASCII-art login splash screen?
8. Purging packages in the cache to reduce size of the tarball.
9. Removing anything from udev rules that gets added in to the networking? (we saw this on the lenny image - udev added in a device that key upon the MAC addy and it effectively lock up networking... so this must be removed before final tar-up).
10. For Etch 2.6, does this fstab look suitable?

Code:
# <fs>                  <mountpoint>    <type>          <opts>                       <dump/pass>
/dev/sda1               /               ext3            noauto,noatime,nodiratime    1 2
/dev/sda2               none            swap            sw                           0 0
/dev/sda3               /mnt            ext3            noatime,nodiratime           0 1
proc                    /proc           proc            defaults                     0 0
none                    /dev/pts        devpts          gid=5,mode=20                0 0


11. Specify /etc/apt/sources.list
12. Hostname = LS1-Debian , root passwd = debian
13. ??

100. purge /var/cache/blaahblaah before final tar-up?

_________________
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: Sun Apr 19, 2009 7:08 am 
Offline
Site Admin
User avatar

Joined: Sun Jul 17, 2005 4:34 pm
Posts: 5332
Thank you very much for all your work!!

davy_gravy wrote:
5. ssh, but not telnet?
scp ?
ntpdate ?
udev ? (or maybe leave udev out ... the user can install this and we avoid the udev network rules problem that sometimes locks one out of networking)

6. How about an on hdd setup of /boot-em/ with 2.6 and 2.4 EM utilities installed there already? with a custom uboot that already has scripts built in for EM booting into 2.4 or 2.6, via hdd and tftp? The scripts are easy to hard-code into the uboot environment.


Yes to all of the above. Don't forget to include fix_ext2_magic.

davy_gravy wrote:

10. For Etch 2.6, does this fstab look suitable?

Code:
# <fs>                  <mountpoint>    <type>          <opts>                       <dump/pass>
/dev/sda1               /               ext3            noauto,noatime,nodiratime    1 2
/dev/sda2               none            swap            sw                           0 0
/dev/sda3               /mnt            ext3            noatime,nodiratime           0 1
proc                    /proc           proc            defaults                     0 0
none                    /dev/pts        devpts          gid=5,mode=20                0 0




I'm not sure why it's not

Code:
/dev/sda1               /               ext3           defaults,noatime,nodiratime    1 1
/dev/sda2               none            swap            sw                           0 0
/dev/sda3               /mnt            ext3            defaults,noatime,nodiratime   0 2
proc                    /proc           proc            defaults                     0 0
none                    /dev/pts        devpts          gid=5,mode=20                0 0


man fstab suggests the rootfs should be checked first.

davy_gravy wrote:

11. Specify /etc/apt/sources.list



Definitely. Pointing to the named release, not stable etc.

davy_gravy wrote:

13. ??



/etc/network/interfaces:

Code:
# we always want the loopback interface
#
auto lo
iface lo inet loopback

# LS standard address
#
auto eth0
iface eth0 inet static
  address 192.168.11.150
  network 192.168.11.0
  netmask 255.255.11.255
  broadcast 192.168.11.255
  #gateway 0.0.0.0

# default dynamic setup (no adjustment necessary)
#auto eth0:1
iface eth0:1 inet dhcp
  hostname `hostname`


plus "dhcpcd" as the client on etch!!

On including the upgradehelper, were the modified files in /etc/init.d/ also included, as intended?


Top
   
PostPosted: Sun Apr 19, 2009 5:06 pm 
Offline
Site Admin
User avatar

Joined: Mon Aug 28, 2006 1:15 am
Posts: 2606
andre, that helps a lot ...

1. the default 150 ip is a good idea ... I'd missed that ...


2. also, I'll tweak fstab based on what you said regarding checking the rootfs ...

3. I do have fix_ext2_magic included ... sitting at /usr/local/sbin IIRC

4. Does this part below require a 2.6 kernel (like udev?)? In particular the iface eth0:1 inet dhcp?
Code:
# LS standard address
#
auto eth0
iface eth0 inet static
  address 192.168.11.150
  network 192.168.11.0
  netmask 255.255.11.255
  broadcast 192.168.11.255
  #gateway 0.0.0.0

# default dynamic setup (no adjustment necessary)
#auto eth0:1
iface eth0:1 inet dhcp
  hostname `hostname`

I'm guessing there is something superior about dhcpd vs dhcpclient?

5. I'm also having a look at /dev and nodes ... I want to make sure everything is populated in such a way that it will work w/ the older and newer kernels, and with udev.

If possible I'd like to build the tarballs so that udev is not included... since this is something that needs to be able to run in both 2.4 and 2.6, I want to minimize the footprint, too.

_________________
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: Sun Apr 19, 2009 5:34 pm 
Offline
Site Admin
User avatar

Joined: Sun Jul 17, 2005 4:34 pm
Posts: 5332
davy_gravy wrote:
4. Does this part below require a 2.6 kernel (like udev?)? In particular the iface eth0:1 inet dhcp?


nope

davy_gravy wrote:

I'm guessing there is something superior about dhcpd vs dhcpclient?



It works 8-) Apart from that, it's probably inferior as it's IPv4-only.


Top
   
PostPosted: Sun Apr 19, 2009 7:41 pm 
Offline
Site Admin
User avatar

Joined: Mon Aug 28, 2006 1:15 am
Posts: 2606
andre wrote:
It works 8-) Apart from that, it's probably inferior as it's IPv4-only.
Thanks for that tip. The "It works" thing is big ... so I changed it and we'll just have to let users upgrade to another dhcp client if they want IPv6. ;)

I'm working on the Lenny tarball now. I added in some more nodes in /dev ... I'll port these /dev contents back to the Etch tarball then, with hda & sda both.

I'm thinking that we can have just one Lenny image for the two PPC box variant (HD, HG) since the kernel is a universal one.
Do you see any problem w/ this approach for Lenny? I have a dead HG here that I need to solder JTAG headers to and revive, once that is done I can test it out on HG, in addition to the LS1.

I'll adjust its hostname to LSPPC-Lenny - users can modify that to their liking.

(The 2.4.37 kernel is box-specific - so this will require two separate 2.4-capable Etch images.)

EDIT : Arrghh! :x I wish they wouldn't included mac-fdisk as the standard hdd manipulation tool ... gnu-fdisk is what I'll switch it to.

_________________
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: Sun Apr 19, 2009 9:09 pm 
Offline
Site Admin
User avatar

Joined: Sun Jul 17, 2005 4:34 pm
Posts: 5332
LS1 and HG might use different /dev/ttyS?, so avr_evtd might get confused?


Top
   
PostPosted: Sun Apr 19, 2009 10:20 pm 
Offline
Site Admin
User avatar

Joined: Tue Mar 21, 2006 9:11 pm
Posts: 658
I thought the only difference between the HG and HD kernel was the ethernet driver. Include both drivers and you have a universal kernel.

_________________
My completely scratch built 832 push-pull tube amplifier with Padauk frame. It matches my custom mini-ITX machine.


Top
   
PostPosted: Sun Apr 19, 2009 11:43 pm 
Offline
Site Admin
User avatar

Joined: Mon Aug 28, 2006 1:15 am
Posts: 2606
I'm thinking that Sylver (or Lyahk ?) unified it ...and automagically so, so that my kernel that I've rolled for the LS1 boots (and works perfectly) with my HG. Or so my experiences have been ...
As far as the Lenny-LSPPC.tar.gz tarball goes though, I guess the proof is in the pudding. I will try it on the HG later this week.

_________________
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: Mon Apr 20, 2009 5:27 am 
Offline
Site Admin
User avatar

Joined: Mon Aug 28, 2006 1:15 am
Posts: 2606
Confirmed to work : the change to booting Etch in 2.4.37 is just a simple 2 stop procedure:
- make a symlink called /etc/fstab to point to /etc/fstab-2.4.37
- change uboot env for ext2load (no dtb file), bootargs stays the same, and just use bootm 800000

Next stuff to fix,add and test ...
    1. a custom uboot in the Etch image that would have scripts for
      A. tftp booting EM both 2.4.33.3 and foonas-em
      B. hdd-based EM booting for the same two
      C. hdd rootfs booting for 2.4.37 and 2.6.28.8+
    2. more testing of the mtd drivers
    3. build a Etch-based tmpimage.gz and an image.dat to be test-installed on a stock system, perhaps with andre's built-in blitzer
    4. try moving back to modutils in Etch since module-init-tools seems to be not backwards-compatible w/ 2.4. Answer : install both packages - details below.
    5. fix locales misconfig in Etch
    6. check to see if we can use the same booting commands for 2.4 as we can for 2.6 ... ie, will the kernel just ignore the unneed (yet loaded) dtb file? Answer = Yes, details below...
    7. confirm that we only need two adjustments for switching between 2.4 and 2.6
      -make /boot/uImage symlink point to the desired /boot/uImage-2.x.y.z kernel
      - make /etc/fstab symlink point to the corresponding /etc/fstab-2.x
    Answer: Yes! as long as modutils and module-init-tools are both installed concurrently - Debian will choose which to run at boot time.


=========================

Answers/Results:
#6. As suggested by lyakh, we indeed can use the exact same commands to boot the old uImage kernels as with the new dtb-dependent kernels. I just booted a uImage-2.4.37 using the same command structure as is used with lyakh's kernel (newer 2.6's) : load kernel & dtb file, set bootargs, bootm 800000-7f0000 ...
Code:
=> ext2load ide 0:1 800000 /boot/uImage-2.4.37v2  
ext2load ide 0:1 800000 /boot/uImage-2.4.37v2

880215 bytes read
=>  ext2load ide 0:1 7f0000 boot/kuroboxHD.dtb 
 ext2load ide 0:1 7f0000 boot/kuroboxHD.dtb

2387 bytes read
=> setenv bootargs root=/dev/hda1
setenv bootargs root=/dev/hda1
=> bootm 800000 - 7f0000
bootm 800000 - 7f0000
## Booting image at 00800000 ...
   Image Name:   Linux-2.4.37
   Image Type:   PowerPC Linux Kernel Image (gzip compressed)
   Data Size:    880151 Bytes = 859.5 kB
   Load Address: 00000000
   Entry Point:  00000000
   Verifying Checksum ... OK
   Uncompressing Kernel Image ... OK
   Booting using flat device tree at 0x7f0000

Code:
Debian GNU/Linux 4.0 Etch
LS1-Etch:~# uname -a
Linux LS1-Etch 2.4.37 #1 Wed Apr 15 20:13:00 CDT 2009 ppc GNU/Linux
LS1-Etch:~#

This simplifies things since we will only have to change a single symlink in boot. uImage can point to either a 2.4 or a 2.6 kernel, and we load kernel and dtb file. The kernel will go ahead and boot even if it does't need the dtb file. Nice and clean, lyakh!


#4. I found this http://kerneltrap.org/node/799 which states near the bottom of page:
Quote:
Are there any special tips for Debian users?
Several readers have pointed towards this article by linmagau.org, though it refers to compiling a 2.4 kernel. At this time, there's a debian package for 2.6.0-test2 here. adds, "A Debian Woody system will have module problems. But people running Debian Sid (and Sarge) can just 'apt-get install module-init-tools'. I was pleased that Debian figures out at boot time whether to use the new module-init-tools or the older modutils, though perhaps all distros do this.".

This seems to say that the two packages can be installed concurrently and will function intelligently, ie. the system will decide whether to use modutils or module-init-tools at boot time. Can anyone confirm this as correct or not? If correct, is it actually robust and reliable? Or is the functionality "breaky"?

I do have both installed now, and they seem to work, but want to know if it is really "trustworthy"...?
Code:
LS1-Etch:~# dpkg -l | grep mod
ii  libnewt0.52            0.52.2-10                            Not Erik's Windowing Toolkit - text mode win
ii  libpam-modules         0.79-5+etch1                         Pluggable Authentication Modules for PAM
ii  module-init-tools      3.3-pre4-2                           tools for managing Linux kernel modules
ii  modutils               2.4.27.0-6                           Linux module utilities

_________________
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: Tue Apr 21, 2009 6:57 pm 
Offline
Developer
User avatar

Joined: Sun Dec 31, 2006 10:40 am
Posts: 434
Location: Scotland
Thanks for the work Davy :)

Any specific things I should be doing to get this to run on my HS? I've installed the Lenny image.... but not got any further than loading the Kernel to a certain point.

Here's what I've done so far:
This unit has u-boot 1.2 installed, with mb's firmimg installed. I did run Freelink, with 2.6 kernel before today.
Standard Partitions hda1,hda2,hda3 (/,swap,storage)

1. Setup my host machine for nc
2. Booted the HS.
3. Stopped the boot process.
4. Botted into EM Mode
Code:
stdin :   nc
stdout:   nc
stderr:   nc
IDE:   Bus 0: .......OK
  Device 0: Model: ST3400633A Firm: 3.AAE Ser#: 4NF29PTM
            Type: Hard Disk
            Supports 48-bit addressing
            Capacity: 381554.0 MB = 372.6 GB (781422768 x 512)
Boot in 09 seconds ('s' to stop)...s

=> run bootcmd3
run bootcmd3
## Booting image at ffc00000 ...

******* Product Information *******
----------------------------------
Product Name: HD-HGLAN(IEMITSU)
         VER: 2.08
        Date: 2006/2/9 12:0:6
----------------------------------
Verifying checksum... OK
Uncompressing kernel...done.
Loading Ramdisk at 0x07C6C000, end 0x07E6E312 ... OK
5. FTP & telneted into the HS.
6. Transfered the Lenny image to hda3.
7. Cleared hda1 & Untarred the image to hda1.
Code:
<snipped>
./boot-em/firmimg.bin
./boot-em/vmlinuxHD.UBoot
./boot-em/vmlinuxHG.UBoot
# ls -l
drwxr-xr-x    2 root     root         4096 Apr 22 02:15 bin
drwxr-xr-x    2 root     root         4096 Apr 22 02:15 boot
drwxr-xr-x    2 root     root         4096 Apr 20 11:26 boot-em
drwxr-xr-x    4 root     root        12288 Apr 22 02:15 dev
drwxr-xr-x   44 root     root         4096 Apr 22 02:15 etc
drwxr-xr-x    2 root     root         4096 Oct 28  2006 home
drwxr-xr-x    2 root     root         4096 Apr 17 09:17 initrd
drwxr-xr-x   11 root     root         4096 Apr 22 02:15 lib
drwxr-xr-x    2 root     root         4096 Apr 22 02:15 lib64
drwx------    2 root     root         4096 Apr 17 09:06 lost+found
drwxr-xr-x    2 root     root         4096 Apr 17 09:17 media
drwxr-xr-x    2 root     root         4096 Oct 28  2006 mnt
drwxr-xr-x    2 root     root         4096 Apr 17 09:17 opt
drwxr-xr-x    2 root     root         4096 Oct 28  2006 proc
drwxr-xr-x    2 root     root         4096 Apr 20 11:18 root
drwxr-xr-x    2 root     root         4096 Apr 22 02:15 sbin
drwxr-xr-x    2 root     root         4096 Sep 16  2008 selinux
drwxr-xr-x    2 root     root         4096 Apr 17 09:17 srv
drwxr-xr-x    2 root     root         4096 Jan  9 15:02 sys
drwxrwxrwt    2 root     root         4096 Apr 20 11:16 tmp
drwxr-xr-x   11 root     root         4096 Apr 20 11:14 usr
drwxr-xr-x   13 root     root         4096 Apr 20 11:12 var
# reboot
#
Broadcast message from root (pts/0) Wed Apr 22 02:30:06 2009...

The system is going down for reboot NOW !!
8. Reboot.
9. Let u-boot do it's thing.
Code:
stdin :   nc
stdout:   nc
stderr:   nc
IDE:   Bus 0: OK
  Device 0: Model: ST3400633A Firm: 3.AAE Ser#: 4NF29PTM
            Type: Hard Disk
            Supports 48-bit addressing
            Capacity: 381554.0 MB = 372.6 GB (781422768 x 512)
Boot in 01 seconds ('s' to stop)...
Loading 0:1:boot/uImage

2310126 bytes read

2387 bytes read
## Booting image at 00800000 ...
   Image Name:   Linux-2.6.28.8
   Image Type:   PowerPC Linux Kernel Image (gzip compressed)
   Data Size:    2310062 Bytes =  2.2 MB
   Load Address: 00000000
   Entry Point:  00000000
   Verifying Checksum ... OK
   Uncompressing Kernel Image ... OK
   Booting using flat device tree at 0x7f0000
ata1: PATA max UDMA/133 cmd 0xbffed0 ctl 0xbffed8 bmdma 0xbffef0 irq 17
ata2: PATA max UDMA/133 cmd 0xbffee0 ctl 0xbffee8 bmdma 0xbffef8 irq 17
ata1.00: ATA-7: ST3400633A, 3.AAE, max UDMA/100
ata1.00: 781422768 sectors, multi 0: LBA48
ata1.00: configured for UDMA/100
scsi 0:0:0:0: Direct-Access     ATA      ST3400633A       3.AA PQ: 0 ANSI: 5
sd 0:0:0:0: [sda] 781422768 512-byte hardware sectors: (400 GB/372 GiB)
sd 0:0:0:0: [sda] Write Protect is off
sd 0:0:0:0: [sda] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA
sd 0:0:0:0: [sda] 781422768 512-byte hardware sectors: (400 GB/372 GiB)
sd 0:0:0:0: [sda] Write Protect is off
sd 0:0:0:0: [sda] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA
 sda: sda1 sda2 sda3
sd 0:0:0:0: [sda] Attached SCSI disk
sd 0:0:0:0: Attached scsi generic sg0 type 0
physmap platform flash device: 00400000 at ffc00000
physmap-flash.0: Found 1 x16 devices at 0x0 in 8-bit bank
 Amd/Fujitsu Extended Query Table at 0x0040
number of CFI chips: 1
cfi_cmdset_0002: Disabling erase-suspend-program due to code brokenness.
cmdlinepart partition parsing not available
RedBoot partition parsing not available
Using physmap partition information
Creating 6 MTD partitions on "physmap-flash.0":
0x00000000-0x00300000 : "mtd_firmimg"
0x00300000-0x00370000 : "mtd_bootcode"
0x00370000-0x00380000 : "mtd_status"
0x00380000-0x00400000 : "mtd_conf"
0x00000000-0x00400000 : "mtd_allflash"
0x00310000-0x00400000 : "mtd_data"
ehci_hcd: USB 2.0 'Enhanced' Host Controller (EHCI) Driver
ehci_hcd 0000:00:0e.2: EHCI Host Controller
ehci_hcd 0000:00:0e.2: new USB bus registered, assigned bus number 1
ehci_hcd 0000:00:0e.2: irq 18, io mem 0xbfffcf00
ehci_hcd 0000:00:0e.2: USB 2.0 started, EHCI 1.00
usb usb1: configuration #1 chosen from 1 choice
hub 1-0:1.0: USB hub found
hub 1-0:1.0: 5 ports detected
usb usb1: New USB device found, idVendor=1d6b, idProduct=0002
usb usb1: New USB device strings: Mfr=3, Product=2, SerialNumber=1
usb usb1: Product: EHCI Host Controller
usb usb1: Manufacturer: Linux 2.6.28.8 ehci_hcd
usb usb1: SerialNumber: 0000:00:0e.2
ohci_hcd: USB 1.1 'Open' Host Controller (OHCI) Driver
ohci_hcd 0000:00:0e.0: OHCI Host Controller
ohci_hcd 0000:00:0e.0: new USB bus registered, assigned bus number 2
ohci_hcd 0000:00:0e.0: irq 18, io mem 0xbfffe000
usb usb2: configuration #1 chosen from 1 choice
hub 2-0:1.0: USB hub found
hub 2-0:1.0: 3 ports detected
usb usb2: New USB device found, idVendor=1d6b, idProduct=0001
usb usb2: New USB device strings: Mfr=3, Product=2, SerialNumber=1
usb usb2: Product: OHCI Host Controller
usb usb2: Manufacturer: Linux 2.6.28.8 ohci_hcd
usb usb2: SerialNumber: 0000:00:0e.0
ohci_hcd 0000:00:0e.1: OHCI Host Controller
ohci_hcd 0000:00:0e.1: new USB bus registered, assigned bus number 3
ohci_hcd 0000:00:0e.1: irq 18, io mem 0xbfffd000
usb usb3: configuration #1 chosen from 1 choice
hub 3-0:1.0: USB hub found
hub 3-0:1.0: 2 ports detected
usb usb3: New USB device found, idVendor=1d6b, idProduct=0001
usb usb3: New USB device strings: Mfr=3, Product=2, SerialNumber=1
usb usb3: Product: OHCI Host Controller
usb usb3: Manufacturer: Linux 2.6.28.8 ohci_hcd
usb usb3: SerialNumber: 0000:00:0e.1
mice: PS/2 mouse device common for all mice
i2c /dev entries driver
rtc-rs5c372 0-0032: rs5c372a found, 24hr, driver version 0.6
rtc-rs5c372 0-0032: rtc core: registered rtc-rs5c372 as rtc0
TCP cubic registered
NET: Registered protocol family 10
NET: Registered protocol family 17
RPC: Registered udp transport module.
RPC: Registered tcp transport module.
rtc-rs5c372 0-0032: setting system clock to 2009-04-21 17:30:35 UTC (1240335035)
linkstation: disarming the AVR watchdog:
kjournald starting.  Commit interval 5 seconds
EXT3-fs: mounted filesystem with ordered data mode.
VFS: Mounted root (ext3 filesystem) readonly.
Freeing unused kernel memory: 188k init
Adding 506036k swap on /dev/sda2.  Priority:-1 extents:1 across:506036k
EXT3 FS on sda1, internal journal
device-mapper: ioctl: 4.14.0-ioctl (2008-04-23) initialised: dm-devel@redhat.com
This is as far as it goes. The disk chunters away for a while, even after about an hour or so, I reset the box, go into em mode, mount the disk & check /mnt/hda1/var/log. Nothing, just the logs that the image was shipped with.

Any ideas?

_________________
LS-500GL - Diskless
LS-250GL - Armel, U-Boot NC Enabled
HS-DH320GL - Stock 1.11_1a
LS-H120LAN(PPC) - Dev (foonas)
LS-H120LAN(PPC) - Freelink - 2.6.23.8
LS-H250LAN(MIPS) - Dev (foonas-em, foonas)
LS-HS400DGL(PPC) - Freelink
Thecus N1200 - Ubuntu 8.10


Top
   
PostPosted: Tue Apr 21, 2009 9:35 pm 
Offline
Site Admin
User avatar

Joined: Sun Jul 17, 2005 4:34 pm
Posts: 5332
fix_ext2_magic? Or my patched "latest" kernel 2.6.25.20?


Top
   
PostPosted: Tue Apr 21, 2009 10:45 pm 
Offline
Site Admin
User avatar

Joined: Mon Aug 28, 2006 1:15 am
Posts: 2606
Hi Kaiten and andre ... (... solved this ... short story is at end... :) )

It is possible that my kernel does not work on the HS/HG. My only HG for testing is bricked and I haven't had time to solder headers and JTAG it (yet...).

Do you think its the kernel? That is my guess...

I'm wondering if indeed trying andre's kernel he mentioned, my 2.6.28.8 for LS-HG or my 2.6.29.1 would make a difference. (I have run my LS-HG kernel in my LS1 (TTBOMK, unless I mixed something up... - maybe I misunderstood and the compatibility either doesn't exist, or is one-way?).

I am assuming you do have sda1=root, sda2=swap (turned on) and sda3=/mnt . ??

Ahhh... are your sda1&3 both of ext3 fs type? Does something look screwy in /etc/fstab?


FWIW, the Lenny image boots immediately on my LS1. (Double-checked it does work fine...)
===========================================================================
... 4hrs later ... I remembered I have a KuroHG boxed up... got it out... indeed it won't boot, even w/ the kernel & that I have my Lenny-HG HomeOffice server running on... (a perfectly good/known working kernel+module set...)

I was sitting thinking of what could be wrong when output from the kernel netconsole started again... I think it may have been running checkfs or checkroot. I found this in /var/log/fsck:
Code:
cat checkfs 
Log of fsck -C -R -A -a
Sat Mar 21 20:22:41 2009

fsck 1.41.3 (12-Oct-2008)
/dev/sda3 has been mounted 29 times without being checked, check forced.
/dev/sda3: /lost+found not found.  CREATED.
/dev/sda3: 14959/12500992 files (0.2% non-contiguous), 2470604/25001156 blocks
fsck died with exit status 1

Sat Mar 21 20:26:34 2009



It did boot for me after all ...

Code:
                              
LSPPC-Lenny:/# cat /proc/cpuinfo
processor   : 0
cpu      : 82xx
clock      : 262.144000MHz
revision   : 1.4 (pvr 8081 1014)
bogomips   : 64.92
timebase   : 32522240
platform   : Buffalo Linkstation
model      : KuroboxHG
vendor      : Buffalo Technology
machine      : Linkstation I/Kurobox(HG)     <<<<<<<<<<<<<<================  Note this line...
Memory      : 128 MB



===============================

Kaiten, I think it is possible that your box was in an fsck run while you heard it "chuntering away". This is what I saw on my KuroHG...

try #1: Lenny-LSPPC-0.1.0.tar.gz on an old sda1 partition... : 2 minutes and it was hanging at
Code:
device-mapper: ioctl: 4.14.0-ioctl (2008-04-23) initialised: dm-devel@redhat.com
just like you said... I killed it

try #2 : I replaced the kernel with another one (probably identical, I now think)... and after about 5-10 minutes it finally completed booting... I thought maybe the original kernel was bad ... the log in /var/log/fsck/checkfs seemed to show that it had run fsck a few times, once unsuccessfully...

try #3 : I deleted everything from sda1, and untarred Lenny-LSPPC-0.1.0.tar.gz on sda1 again. It booted immediately no delay. After all, it seems that the kernel is a universal one, and it works as advertised/suggested.

I'm not sure if we both just happened to hit a limit on the # of boots, and that triggered fsck at bootup...
Do you think it has something to do with /var/log/fsck/* having some non-trivial contents? Or just some weirdness of a partition?
Was this caused by a fstab setting?



Also, thanks for telling me about the logs that I had forgotten to clean out... I will do that in Lenny-LSPPC-0.1.1.tar.gz .

Thanks ;) If there is anything that you can find that needs tweaking, please let me know, and I'll do my best to address it.

_________________
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 Apr 22, 2009 7:16 am 
Offline
Developer
User avatar

Joined: Sun Dec 31, 2006 10:40 am
Posts: 434
Location: Scotland
I'll try again later after work, was out on the beer last night.. not got a head for playing this morning.


Edit.. OK got the better of me,
Code:
Debian GNU/Linux 5.0 Lenny
Last login: Mon Apr 20 02:17:25 2009 from 192.168.11.149
LSPPC-Lenny:~#
Code:
Log of fsck -C -a -t ext3 /dev/sda1 
Wed Apr 22 06:30:08 2009

fsck 1.41.3 (12-Oct-2008)
/dev/sda1 has been mounted 33 times without being checked, check forced.
/dev/sda1: 11412/1224000 files (0.1% non-contiguous), 102839/2443880 blocks
Yep it was fsck :)

Will poke around later :)

_________________
LS-500GL - Diskless
LS-250GL - Armel, U-Boot NC Enabled
HS-DH320GL - Stock 1.11_1a
LS-H120LAN(PPC) - Dev (foonas)
LS-H120LAN(PPC) - Freelink - 2.6.23.8
LS-H250LAN(MIPS) - Dev (foonas-em, foonas)
LS-HS400DGL(PPC) - Freelink
Thecus N1200 - Ubuntu 8.10


Top
   
PostPosted: Wed Apr 22, 2009 12:24 pm 
Offline
Site Admin
User avatar

Joined: Mon Aug 28, 2006 1:15 am
Posts: 2606
:up: hehehe ...

I'm just now testing the 2.4.37 for HG ... will post that soon...

_________________
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 Jun 11, 2009 3:51 pm 
Offline
Newbie

Joined: Wed May 27, 2009 1:33 pm
Posts: 15
I just put the Lenny-LSPPC-0.1.0 to my Kuro-HG (davy_gravy is aware of my uboot and foonas-em installationl ;) Thanks again!)

davy_gravy wrote:
default standard 192.168.11.150 ip address, with dhcp fallback network setup

I do not see the dhcp to be a real fallback. As a fallback I understand if anything does not work use something else automatically. Is it meant to be like that? If so I was not able to ssh into the box connected to a 192.168.1. dhcp network. However I was able to ssh to 192.168.11.150.
I assume the Kuro box usually is used in a headless way, shouldn't the default be to acquire a dynamic address and if this fails fall back to a static set-up?

After altering the /etc/network/interfaces to
Code:
# we always want the loopback interface
#
auto lo
iface lo inet loopback

# LS standard address
#
#auto eth0
#iface eth0 inet static
#  address 192.168.11.150
#  network 192.168.11.0
#  netmask 255.255.0.0
#  broadcast 192.168.11.255
#  gateway 192.168.11.1

# default dynamic setup (no adjustment necessary)
##auto eth0:1
#iface eth0:1 inet dhcp
#  hostname `hostname`

auto eth0
iface eth0 inet dhcp
  hostname `hostname`

I was able to ssh into the box with its dhcp name and could connect to the internet with the box (after changing the name server in /etc/resolve.conf). I may be completely wrong here (as a rookie), maybe I just don't now what's meant by eth0:1 and how to handle it.

Do all the devices in /dev have to be in the image? On my openSuSE system the devices are generated during start-up or when necessary (I think by udev). Just as an idea.

Regards and thanks already for all the work giving me another toy to learn.

Stefan


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

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:
Powered by phpBB® Forum Software © phpBB Limited