Buffalo NAS-Central Forums

Welcome to the Linkstation Wiki community
It is currently Tue Feb 20, 2018 6:33 pm

All times are UTC+01:00




Post new topic  Reply to topic  [ 120 posts ]  Go to page Previous 13 4 5 6 7 8 Next
Author Message
PostPosted: Tue Aug 18, 2009 4:41 am 
Offline
Newbie

Joined: Sun Aug 05, 2007 4:15 am
Posts: 36
Bauldrick,

I though you missed "tftp ..." step and programmed junk into your flash. :-)

You don't need to have the exactly network setting as mine but you need to use the same subnet 192.168.1.*. Normal netcat can't handle broadcast traffic so you need to compile ncb from U-Boot. Here's the procedures:

Code:
shihsung@suse-kde:~> cd /tmp
shihsung@suse-kde:/tmp> tar xfj ~/Documents/download/u-boot-2009.06.tar.bz2
shihsung@suse-kde:/tmp> cd u-boot-2009.06/
shihsung@suse-kde:/tmp/u-boot-2009.06> make tools/ncb
cc     tools/ncb.c   -o tools/ncb
shihsung@suse-kde:/tmp/u-boot-2009.06> mkdir ~/bin
shihsung@suse-kde:/tmp/u-boot-2009.06> cp tools/ncb ~/bin
shihsung@suse-kde:/tmp/u-boot-2009.06> vi ~/bin/nc
#!/bin/sh

[ $# = 1 ] || { echo "Usage: $0 target-ip" >&2; exit 1; }
TARGET_IP=$1

stty -icanon -echo intr ^T
ncb &
netcat -u ${TARGET_IP} 6666

stty icanon echo intr ^C
kill 0
shihsung@suse-kde:/tmp/u-boot-2009.06> chmod +x ~/bin/nc
shihsung@suse-kde:/tmp/u-boot-2009.06> ~/bin/nc 192.168.1.200


Your box doesn't shut down after 25 seconds any more? What did you do to fix it? Do you have J2 jumper installed?

Can you please do "md 0xb8050008 1" at the U-Boot prompt:

Code:
HD-HLAN# md 0xb8050008 1
b8050008: 00003ff3    .?..
HD-HLAN#


I'm very curious what value you have on GPIO pin 8. It should be 1 is you don't have J2 jumper installed and 0 otherwise.


Davy_gravy,

My U-Boot doesn't auto-boot by default. Here's the default configuration:

Code:
HD-HLAN# print
bootdelay=3
baudrate=115200
ipaddr=192.168.1.200
serverip=192.168.1.1
silent=1
stdin=nc
stdout=nc
stderr=nc
ethact=rc32434-eth

Environment size: 127/65532 bytes
HD-HLAN#


Top
   
PostPosted: Tue Aug 18, 2009 1:50 pm 
Offline
Betatester
User avatar

Joined: Thu Jul 14, 2005 4:38 pm
Posts: 941
Location: England
:up: :up: :up:

matt@Compaq-Laptop:/bin$ nc-uboot 192.168.1.200
rc32434-eth
HD-HLAN# d 0xb8050008 1
b8050008: 00003ffb .?..
HD-HLAN#


I guess the way I installed your uboot over LNI's uboot caused some kind of conflict? Which is a shame I guess, as the 'run upgrade' from uboot prompt seems much less scary to me :p

Anyway, thanks.. for getting my box back talking to me, but more for the work you've put in on the kernel and uboot.

Got to change settings back to previous uboot's now without getting locked out and losing it again.... :lol:


Top
   
PostPosted: Wed Aug 19, 2009 5:28 am 
Offline
Newbie

Joined: Sun Aug 05, 2007 4:15 am
Posts: 36
Bauldrick,

Hmm, I don't know what setting in the U-Boot environment variables can cause the repeated shut down you have experienced. Well, I should have asked you to dump the flash sector 0xbfc30000 - 0xbfc3ffff before you erased it with "eraseall /dev/mtd0" from Linux. But, I'm glad you got your system back under control now. :-)


Top
   
PostPosted: Wed Aug 19, 2009 6:25 pm 
Offline
Site Admin
User avatar

Joined: Mon Aug 28, 2006 1:15 am
Posts: 2606
tftp booting works w/the Lenny image & the kernel supplied it it... just untar Lenny or the em-image in my downloads on a USB stick, adjust to your network settings, place a copy of the 2.6.30.5 kernel in your tftp root dir and rename it and it vmlinuz-2.6.30.5-em, and then while in uboot do:

Code:
tftp 82000000 vmlinuz-2.6.30.5-em
set bootargs 'root=/dev/sdb1 rw rootdelay=10 netconsole=6666@192.168.11.150/,@192.168.11.149/'
bootm


It will work to install it w/ a USB stick, but it is not the easiest way...

_________________
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 Aug 20, 2009 6:05 pm 
Offline
Site Admin
User avatar

Joined: Mon Aug 28, 2006 1:15 am
Posts: 2606
Installing Lenny on the LS2 using foonas-em.

-1. :) Do not skip steps or reading. Make sure that you understand that the old kernel (2.4 & 2.6.22.19) had a custom (non-mainline) rtc driver that was "nonstandard". The new kernel uses the mainline driver for the rtc chip, but setting the hwclock in one kernel and then booting into the other kernel can cause some problems. These problems can easily be avoided if you do the workarounds. Don't skip those workarounds. Read and understand. Then do. If you don't understand, ask first, or maybe read again. :)

Also, remember that the current version of foonas-em has the older kernel which uses the ide driver (/dev/hda), while the kernel that is used by default in the Lenny tarballs uses the pata driver (/dev/sda).


0. It is assumed that you have uboot (preferably LNI's LS2 uboot, for now) installed on your LS2 and you know how to communicate w/ it via netcat/netconsole. It is also assumed that you are using a static ip of 192.168.150 for both foonas-em and Lenny on your LS2.


1. Get a tftp server up and running at 192.168.11.149. If you choose another ip for your server, read the docs and adjust accordingly.


2. Download this special beta foonas-em-beta :
vmlinuz.gz-ext4_tune2fs_fw-setwrite. Rename it vmlinuz.gz.
Either tftp-boot it or hdd boot it, following the directions in the links below (replace vmlinuz.gz in the commands w/ vmlinuz-tunext4fw.gz
Boot into foonas-em, either by tftp, by booting it from a file on an hdd partition, or from flash.
http://foonas.org/index.php/Foonas-em:TFTPBoot-lsmipsel
http://foonas.org/index.php/Foonas-em:H ... l-lsmipsel

tftp-booting for me looked like this:
Code:
U-Boot 1.1.4 LiSt V2 (mips) 1.0.1 (Sep 20 2007 - 00:42:23)
stdin :   nc
stdout:   nc
stderr:   nc
IDE:    Bus 0: OK Bus 1: OK
  Device 0: Model: Maxtor 5T020H2 Firm: TAH71DP0 Ser#: 2TRH6MCG
            Type: Hard Disk
            Capacity: 19073.4 MB = 18.6 GB (39062500 x 512)
Boot in 05 seconds ('s' to stop)...s

=> tftp 82000000 vmlinuz.gz
tftp 82000000 vmlinuz.gz
Using rc32434_eth device
TFTP from server 192.168.11.149; our IP address is 192.168.11.150
Filename 'vmlinuz.gz'.
Load address: 0x82000000
Loading: #################################################################
    #################################################################
    #################################################################
    #################################################################
    #################################################################
    #################################################################
    #################################################################
    #################################################################
    #################################################################
    #################################################################
    ############################
done
Bytes transferred = 3466830 (34e64e hex)
=> setenv bootargs netconsole=6666@192.168.11.150/,@192.168.11.149/ root=/dev/ram0 rw
setenv bootargs netconsole=6666@192.168.11.150/,@192.168.11.149/ root=/dev/ram0 rw
=> bootm 82000000
bootm 82000000



3. Connect from telnet, with root password hydr0g3n. (I'm assuming that it comes up at 192.168.11.150 - you will probably have to use a scanner to find it...)


Code:
davygravy@DuoBuntu:~$ telnet 192.168.11.150
Trying 192.168.11.150...
Connected to 192.168.11.150.
Escape character is '^]'.

   ______ _____ _____ __   __  _____  ______
  |   ___|     |     |   \|  |/  _  \|   ___|
 _|   ___|  -  |  -  |       |   _   |\   \
| |__|   |_____|_____|__|\___|__| |__|_\   \
|___________________________________________|

foonas-em for lsmipsel - http://foonas.org

lsmipsel login: root
Password: hydr0g3n



4. Set the date in foonas-em and the hardware clock:
Code:
date MMDDhhmmyyyy
hwclock -w

Hint: Always set your date when booting into another kernel (ie., into a kernel that uses a different rtc driver), otherwise, you will see some strange dates.



5. Set up your hdd on the LS2.
Code:
fdisk /dev/sda 

and follow the prompts to set up your hdd so that you have partition like this (adjust to your needs):
Code:
Disk /dev/sda: 300.0 GB, 300090728448 bytes
255 heads, 63 sectors/track, 36483 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes

   Device Boot      Start         End      Blocks  Id System
/dev/sda1               1         609     4891761  83 Linux
/dev/sda2             610         672      506047+ 82 Linux swap
/dev/sda3             673       36483   287651857+ 83 Linux



6. Set up filesystems and swap.
Code:
mkfs.ext3 -I 128 /dev/sda1
mkfs.ext3 -I 128 /dev/sda3 
mkswap /dev/sda2
swapon /dev/sda2


You may also try using mkfs.ext4, but I have not tested this. Also, note the the -I 128 option is now necessary since ext2 revision 1 is in effect for e2fsprogs 1.40.5 and later. Older uboot ports (like LNI's) can only read ext2/3 systems w/ inode sizes =128.

7. Don't skip this step - crucial! Tune your partitions so that any rtc discprepancies will not trigger an automatic fsck at boot time.
Code:
tune2fs /dev/sda1 -i 0 -c 0
tune2fs /dev/sda3 -i 0 -c 0



8. Mount /dev/sda1 to /mnt, and cd to /mnt
Code:
mount -t ext3 /dev/sda1 /mnt
cd /mnt



9. Download the image & kernel upgrade onto /mnt (which is really /dev/sda1, your new rootfs partition).
Code:
wget http://downloads.buffalo.nas-central.org/Users/davy_gravy/lsmipsel%20images/lsmipsel-lenny-v4.tar.gz
wget http://downloads.buffalo.nas-central.org/Users/davy_gravy/kernelpackages/lsmipsel_kernel-mod_packages/kernelupgrade2.6.30.5v2.tar.gz



10. Untar the tarball at /mnt, upgrade the kernel, and make any modifications necessary to network related files in etc:
Code:
gunzip  lsmipsel-lenny-v4.tar.gz
tar xvf lsmipsel-lenny-v4.tar
## delete the old modules & upgrade to the newest ones
cd /mnt/lib/modules
rm -r 2.6.30.5/
cd /mnt
gunzip kernelupgrade2.6.30.5v2.tar
tar xvf kernelupgrade2.6.30.5v2.tar

##  edit your network interfaces file & resolv.conf as you like.
vi /mnt/etc/network/interfaces
vi /mnt/etc/resolv.conf

##(You may change your network values, but adjust accordingly. In particular, pay attention to the nameserver and search values in resolv.conf)


11. Unmount /dev/sda1 & run fsck (to avoid any chance of the cyclic reboot problem), and then reboot.
Code:
cd /
umount /dev/sda1
fsck.ext3 /dev/sda1
fsck.ext3 /dev/sda3


Press the Power Button twice and the box will start to reboot.


12. Halt uboot at the prompt and set your env vars for the new kernel:
Code:
set bootargs 'root=/dev/sda1 rw netconsole=6666@192.168.11.150/,@192.168.11.149/'
set hdfile boot/vmlinuz
save
boot



13. Log in to Lenny on your lsmipsel with root password "lsmipsel". (this assumes that you have set a static ip of 192.168.11.150 in /etc/network/interfaces)
Code:
ssh root@192.168.11.150



14. Set your date and then the hwclock:
Code:
date MMDDhhmmyyyy
hwclock -w

You may have to repeat the "hwclock -w" several times until it returns without an error. If it works the first time, don't worry, everything is probably OK, too.

15. Move to /lib/modules/2.6.30.5 and run depmod:
Code:
cd  /lib/modules/2.6.30.5
depmod -a


16. At this point you can run apt-get update and install whatever Debian packages you wish.
The simplest way of ridding yourself of the ugly perl messages is to:
Code:
apt-get update
apt-get install locales-all


You should also configure your time zone and install the ntpd.
Code:
apt-get install ntp
dpkg-reconfigure tzdata


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

Optional:
If you don't have foonas-em in flash, you can boot it from the hdd, since the initramfs image is in /boot-em/vmlinuz.gz.
While in uboot, set your env vars & save:
Code:
set bootcmd2 run bootemhdd
set bootemhdd 'ext2load ide 0:1 82000000 /boot-em/vmlinuz.gz ; setenv bootargs=root=/dev/ram0 ; bootm 82000000'
save

To boot into foonas-em from the hdd image, simply run (from uboot netconsole)
Code:
run bootemhdd

You can also simply choose two red flashes from the minicom.

Also, I have flashed this image to my ROM and it works fine. Read about it here : viewtopic.php?f=12&t=20753&p=132527&hilit=+foonas+em+beta+#p132527

_________________
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: Sat Aug 22, 2009 3:37 am 
Offline
Site Admin
User avatar

Joined: Mon Aug 28, 2006 1:15 am
Posts: 2606
I've now tested this kernel with:
nfs
samba
build-essentials (building various packages)
perl & cpan (rebuilt cpan from within cpan ... works fine)
usb storage

shihsung, anything else you'd like us to test? :)

_________________
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: Sat Aug 22, 2009 5:58 pm 
Offline
Site Admin
User avatar

Joined: Mon Aug 28, 2006 1:15 am
Posts: 2606
davy_gravy wrote:
I've now tested this kernel with...
perl & cpan (rebuilt cpan from within cpan ... works fine)


OK, I missed something... I think. EDIT: maybe this is all just a perl problem, rather than a kernel problem?

While I was able to rebuild cpan from w/i cpan, I am sometimes now seeing "Killed" message in the kern.log.

Quote:
Aug 22 11:51:46 localhost kernel: select 1 (init), adj 0, size 114, to kill
Aug 22 11:51:46 localhost kernel: select 587 (rsyslogd), adj 0, size 174, to kill
Aug 22 11:51:46 localhost kernel: select 664 (bash), adj 0, size 211, to kill
Aug 22 11:51:46 localhost kernel: select 724 (bash), adj 0, size 291, to kill
Aug 22 11:51:46 localhost kernel: select 1369 (cpan), adj 0, size 12684, to kill
Aug 22 11:51:46 localhost kernel: send sigkill to 1369 (cpan), adj 0, size 12684


Also, I'm seeing some other messages concerning some processes respawning...
Quote:
Aug 22 11:21:29 localhost init: Id "3" respawning too fast: disabled for 5 minutes
Aug 22 11:21:29 localhost init: Id "1" respawning too fast: disabled for 5 minutes
Aug 22 11:21:30 localhost init: Id "4" respawning too fast: disabled for 5 minutes
Aug 22 11:21:30 localhost init: Id "5" respawning too fast: disabled for 5 minutes
Aug 22 11:21:30 localhost init: Id "2" respawning too fast: disabled for 5 minutes
Aug 22 11:21:30 localhost init: Id "6" respawning too fast: disabled for 5 minutes
Aug 22 11:24:17 localhost kernel: select 1 (init), adj 0, size 120, to kill
Aug 22 11:24:17 localhost kernel: select 587 (rsyslogd), adj 0, size 184, to kill
Aug 22 11:24:17 localhost kernel: select 724 (bash), adj 0, size 225, to kill
Aug 22 11:24:17 localhost kernel: select 1105 (cpan), adj 0, size 12809, to kill
Aug 22 11:24:17 localhost kernel: send sigkill to 1105 (cpan), adj 0, size 12809
Aug 22 11:28:11 localhost init: Id "3" respawning too fast: disabled for 5 minutes
Aug 22 11:28:11 localhost init: Id "1" respawning too fast: disabled for 5 minutes
Aug 22 11:28:12 localhost init: Id "2" respawning too fast: disabled for 5 minutes
Aug 22 11:28:12 localhost init: Id "4" respawning too fast: disabled for 5 minutes
Aug 22 11:28:12 localhost init: Id "6" respawning too fast: disabled for 5 minutes
Aug 22 11:28:12 localhost init: Id "5" respawning too fast: disabled for 5 minutes
Aug 22 11:34:52 localhost init: Id "3" respawning too fast: disabled for 5 minutes
Aug 22 11:34:52 localhost init: Id "1" respawning too fast: disabled for 5 minutes
Aug 22 11:34:54 localhost init: Id "4" respawning too fast: disabled for 5 minutes
Aug 22 11:34:54 localhost init: Id "5" respawning too fast: disabled for 5 minutes
Aug 22 11:34:54 localhost init: Id "2" respawning too fast: disabled for 5 minutes
Aug 22 11:34:54 localhost init: Id "6" respawning too fast: disabled for 5 minutes
Aug 22 11:41:35 localhost init: Id "3" respawning too fast: disabled for 5 minutes
Aug 22 11:41:35 localhost init: Id "1" respawning too fast: disabled for 5 minutes
Aug 22 11:41:36 localhost init: Id "4" respawning too fast: disabled for 5 minutes
Aug 22 11:41:36 localhost init: Id "2" respawning too fast: disabled for 5 minutes
Aug 22 11:41:36 localhost init: Id "5" respawning too fast: disabled for 5 minutes
Aug 22 11:41:36 localhost init: Id "6" respawning too fast: disabled for 5 minutes
Aug 22 11:48:17 localhost init: Id "3" respawning too fast: disabled for 5 minutes
Aug 22 11:48:17 localhost init: Id "1" respawning too fast: disabled for 5 minutes
Aug 22 11:48:18 localhost init: Id "4" respawning too fast: disabled for 5 minutes
Aug 22 11:48:18 localhost init: Id "5" respawning too fast: disabled for 5 minutes
Aug 22 11:48:18 localhost init: Id "6" respawning too fast: disabled for 5 minutes
Aug 22 11:48:18 localhost init: Id "2" respawning too fast: disabled for 5 minutes
Aug 22 11:51:46 localhost kernel: select 1 (init), adj 0, size 114, to kill
Aug 22 11:51:46 localhost kernel: select 587 (rsyslogd), adj 0, size 174, to kill
Aug 22 11:51:46 localhost kernel: select 664 (bash), adj 0, size 211, to kill
Aug 22 11:51:46 localhost kernel: select 724 (bash), adj 0, size 291, to kill
Aug 22 11:51:46 localhost kernel: select 1369 (cpan), adj 0, size 12684, to kill
Aug 22 11:51:46 localhost kernel: send sigkill to 1369 (cpan), adj 0, size 12684
Aug 22 11:54:58 localhost init: Id "3" respawning too fast: disabled for 5 minutes
Aug 22 11:54:58 localhost init: Id "1" respawning too fast: disabled for 5 minutes
Aug 22 11:55:00 localhost init: Id "4" respawning too fast: disabled for 5 minutes
Aug 22 11:55:00 localhost init: Id "2" respawning too fast: disabled for 5 minutes
Aug 22 11:55:00 localhost init: Id "5" respawning too fast: disabled for 5 minutes
Aug 22 11:55:00 localhost init: Id "6" respawning too fast: disabled for 5 minutes

_________________
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 Aug 23, 2009 8:19 am 
Offline
Newbie

Joined: Sun Aug 05, 2007 4:15 am
Posts: 36
Hi Davy_gravy,

No, I can't think of anything in particular to test at this point. However, I have been working on tuning the Ethernet driver performance and will probably release a new version 0.3 Ethernet driver soon. :-)

Quote:
Aug 22 11:51:46 localhost kernel: select 1 (init), adj 0, size 114, to kill
Aug 22 11:51:46 localhost kernel: select 587 (rsyslogd), adj 0, size 174, to kill
Aug 22 11:51:46 localhost kernel: select 664 (bash), adj 0, size 211, to kill
Aug 22 11:51:46 localhost kernel: select 724 (bash), adj 0, size 291, to kill
Aug 22 11:51:46 localhost kernel: select 1369 (cpan), adj 0, size 12684, to kill
Aug 22 11:51:46 localhost kernel: send sigkill to 1369 (cpan), adj 0, size 12684


I searched the kernel source tree for the messages above, and found they were printed from the drivers/staging/android/lowmemorykiller.c. Basically, the kernel try to prevent system crash due to lack of memory by selecting the best candidate to kill with least damage and max memory freed. It selected cpan because it was using 12684 pages which is more than 48 MB out of 64 MB total.

Quote:
Aug 22 11:21:29 localhost init: Id "3" respawning too fast: disabled for 5 minutes
Aug 22 11:21:29 localhost init: Id "1" respawning too fast: disabled for 5 minutes
Aug 22 11:21:30 localhost init: Id "4" respawning too fast: disabled for 5 minutes
Aug 22 11:21:30 localhost init: Id "5" respawning too fast: disabled for 5 minutes
Aug 22 11:21:30 localhost init: Id "2" respawning too fast: disabled for 5 minutes
Aug 22 11:21:30 localhost init: Id "6" respawning too fast: disabled for 5 minutes


The messages above are due to getty been re-spawned repeated on non-existent virtual terminals. To fix the problem, just comment out the lines below in your /etc/inittab. I found the problem late and forgot to add the step on my "Convert to Lenny" procedure. :-)

Code:
#1:2345:respawn:/sbin/getty 38400 tty1
#2:23:respawn:/sbin/getty 38400 tty2
#3:23:respawn:/sbin/getty 38400 tty3
#4:23:respawn:/sbin/getty 38400 tty4
#5:23:respawn:/sbin/getty 38400 tty5
#6:23:respawn:/sbin/getty 38400 tty6


Top
   
PostPosted: Sun Aug 23, 2009 5:46 pm 
Offline
Site Admin
User avatar

Joined: Mon Aug 28, 2006 1:15 am
Posts: 2606
awesome analysis, will try these fixes... :)
in regard to the androidlowmemorykiller... I should have seen that one coming... I guess there is a reason those sorts of things are in "staging"...

_________________
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 Aug 25, 2009 4:14 am 
Offline
Site Admin
User avatar

Joined: Mon Aug 28, 2006 1:15 am
Posts: 2606
I've built a slightly wider version of foonas-em that has
- tune2fs (for disabling date & mount counts for fsck @ startup)
- limited mkfs.ext4 support

I will test this again a bit more & post it, & link it to the install guide.
The new kernel is now in foonas git repo (acks to you, shihsung). http://git.foonas.org/?p=openembedded.git;a=commit;h=c89f01e562b41967be189cb9d2e9d2be505fb283

I'm struggling with getting the new kernel to be bootable when I build it in uclibc. Building in the foonas fork of OE w/ glibc is no problem - the kernel works perfectly there. I'm still not sure what the problem is with uclibc.

Once this problem is solved, I can then build an image that has complete ext4 support & the new pata driver.

EDIT: There seems to be a conspicuous absence of any mips-linux-x86-uclibc here http://ftp.denx.de/pub/eldk/ or anywhere else. Maybe you know of a uclibc-based crosscompiler (other than the OE setup) that I could try? Perhaps whatever problem I'm missing while I try it in OE would be more visible in a more basic crosscompiler?

Maybe uclibc Buildroot is my only off-the-shelf option? http://buildroot.uclibc.org/

_________________
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 Aug 25, 2009 5:32 am 
Offline
Newbie

Joined: Sun Aug 05, 2007 4:15 am
Posts: 36
I just posted a new patch http://sites.google.com/site/shihsung/l ... edirects=0

The main difference is the improved Ethernet driver performance. The other changes are minor clean up and include NLS CP 437, CS ISO 8859-1, and CS UTF-8 as built-in in default config.

Interesting. I have never tried MIPS toolchains with uClibc.


Top
   
PostPosted: Tue Aug 25, 2009 5:52 am 
Offline
Site Admin
User avatar

Joined: Mon Aug 28, 2006 1:15 am
Posts: 2606
Thanks for your efforts on the Ethernet Driver, I will try it out. :)

We like the uclibc builds for cramming lots of nice stuff into flash/ROM. ;)

It cuts the size down appreciably...

_________________
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 Aug 26, 2009 2:41 am 
Offline
Site Admin
User avatar

Joined: Mon Aug 28, 2006 1:15 am
Posts: 2606
for the record, I successfully compiled and booted a kernel made w/ the uclibc Buildroot toolchain. The kernel panic that it displays at the end is not an error, since there simply was not rootfs present for it to mount.
Code:
Linux version 2.6.302.6.30.5 (davygravy@DuoBuntu) (gcc version 4.3.3 (GCC) ) #1 Tue Aug 25 19:53:11 CDT 2009
console [early0] enabled
CPU revision is: 0001800a (MIPS 4Kc)
RC32434: GPIO controller initialized
HD-HLAN: GPIO pins initialized
Determined physical RAM map:
 memory: 04000000 @ 00000000 (usable)
Initrd not found or empty - disabling initrd
Zone PFN ranges:
  Normal   0x00000000 -> 0x00004000
Movable zone start PFN for each node
early_node_map[1] active PFN ranges
    0: 0x00000000 -> 0x00004000
Linux version 2.6.302.6.30.5 (davygravy@DuoBuntu) (gcc version 4.3.3 (GCC) ) #1 Tue Aug 25 19:53:11 CDT 2009
console [early0] enabled
CPU revision is: 0001800a (MIPS 4Kc)
RC32434: GPIO controller initialized
Built 1 zonelists in Zone order, mobility grouping on.  Total pages: 16256
HD-HLAN: GPIO pins initialized
Kernel command line: root=/dev/sdb1 rw rootdelay=15 netconsole=6666@192.168.11.150/,@192.168.11.149/ console=
Primary instruction cache 8kB, VIPT, 4-way, linesize 16 bytes.
Determined physical RAM map:
Primary data cache 8kB, 4-way, VIPT, no aliases, linesize 16 bytes
NR_IRQS:168
RC32434: Interrupt controller initialized
 memory: 04000000 @ 00000000 (usable)
PID hash table entries: 256 (order: 8, 1024 bytes)
Initrd not found or empty - disabling initrd
HD-HLAN: CPU frequency detected at 400 MHz
RC32434: periodic timer initialized
Zone PFN ranges:
Dentry cache hash table entries: 8192 (order: 3, 32768 bytes)
Inode-cache hash table entries: 4096 (order: 2, 16384 bytes)
  Normal   0x00000000 -> 0x00004000
Memory: 61736k/65536k available (2454k kernel code, 3728k reserved, 382k data, 156k init, 0k highmem)
Movable zone start PFN for each node
Calibrating delay loop... 398.33 BogoMIPS (lpj=796672)
early_node_map[1] active PFN ranges
Mount-cache hash table entries: 512
net_namespace: 492 bytes
    0: 0x00000000 -> 0x00004000
NET: Registered protocol family 16
Linux version 2.6.302.6.30.5 (davygravy@DuoBuntu) (gcc version 4.3.3 (GCC) ) #1 Tue Aug 25 19:53:11 CDT 2009
RC32434: PCI controller initialized
Built 1 zonelists in Zone order, mobility grouping on.  Total pages: 16256
bio: create slab <bio-0> at 0
SCSI subsystem initialized
Kernel command line: root=/dev/sdb1 rw rootdelay=15 netconsole=6666@192.168.11.150/,@192.168.11.149/ console=
pci 0000:00:04.0: PME# supported from D0 D1 D2 D3hot
console [early0] enabled
pci 0000:00:04.0: PME# disabled
Primary instruction cache 8kB, VIPT, 4-way, linesize 16 bytes.
pci 0000:00:04.1: PME# supported from D0 D1 D2 D3hot
CPU revision is: 0001800a (MIPS 4Kc)
pci 0000:00:04.1: PME# disabled
Primary data cache 8kB, 4-way, VIPT, no aliases, linesize 16 bytes
pci 0000:00:04.2: PME# supported from D0 D1 D2 D3hot
NR_IRQS:168
pci 0000:00:04.2: PME# disabled
Switched to NOHz mode on CPU #0
NET: Registered protocol family 2
RC32434: Interrupt controller initialized
IP route cache hash table entries: 1024 (order: 0, 4096 bytes)
TCP established hash table entries: 2048 (order: 2, 16384 bytes)
PID hash table entries: 256 (order: 8, 1024 bytes)
TCP bind hash table entries: 2048 (order: 1, 8192 bytes)
HD-HLAN: CPU frequency detected at 400 MHz
TCP: Hash tables configured (established 2048 bind 2048)
TCP reno registered
RC32434: periodic timer initialized
NET: Registered protocol family 1
msgmni has been set to 120
io scheduler noop registered
Dentry cache hash table entries: 8192 (order: 3, 32768 bytes)
io scheduler cfq registered (default)
Inode-cache hash table entries: 4096 (order: 2, 16384 bytes)
Serial: 8250/16550 driver, 8 ports, IRQ sharing disabled
serial8250.0: ttyS0 at MMIO 0x18058000 (irq = 104) is a 16550A
Memory: 61736k/65536k available (2454k kernel code, 3728k reserved, 382k data, 156k init, 0k highmem)
RC32434: GPIO controller initialized
brd: module loaded
loop: module loaded
Calibrating delay loop... 398.33 BogoMIPS (lpj=796672)
HD-HLAN: GPIO pins initialized
Driver 'sd' needs updating - please use bus_type methods
pata_it821x: controller in pass through mode.
Determined physical RAM map:
Mount-cache hash table entries: 512
scsi0 : pata_it821x
scsi1 : pata_it821x
 memory: 04000000 @ 00000000 (usable)
net_namespace: 492 bytes
ata1: PATA max UDMA/133 cmd 0x18200010 ctl 0x18200020 bmdma 0x18200000 irq 146
ata2: PATA max UDMA/133 cmd 0x18200018 ctl 0x18200024 bmdma 0x18200008 irq 146
Initrd not found or empty - disabling initrd
NET: Registered protocol family 16
RC32434: Ethernet controller initialized
Zone PFN ranges:
netconsole: local port 6666
RC32434: PCI controller initialized
netconsole: local IP 192.168.11.150
  Normal   0x00000000 -> 0x00004000
netconsole: interface eth0
bio: create slab <bio-0> at 0
SCSI subsystem initialized
pci 0000:00:04.0: PME# supported from D0 D1 D2 D3hot
pci 0000:00:04.0: PME# disabled
pci 0000:00:04.1: PME# supported from D0 D1 D2 D3hot
pci 0000:00:04.1: PME# disabled
pci 0000:00:04.2: PME# supported from D0 D1 D2 D3hot
pci 0000:00:04.2: PME# disabled
Movable zone start PFN for each node
Switched to NOHz mode on CPU #0
NET: Registered protocol family 2
early_node_map[1] active PFN ranges
IP route cache hash table entries: 1024 (order: 0, 4096 bytes)
    0: 0x00000000 -> 0x00004000
TCP established hash table entries: 2048 (order: 2, 16384 bytes)
Built 1 zonelists in Zone order, mobility grouping on.  Total pages: 16256
TCP bind hash table entries: 2048 (order: 1, 8192 bytes)
Kernel command line: root=/dev/sdb1 rw rootdelay=15 netconsole=6666@192.168.11.150/,@192.168.11.149/ console=
TCP: Hash tables configured (established 2048 bind 2048)
TCP reno registered
NET: Registered protocol family 1
msgmni has been set to 120
io scheduler noop registered
Primary instruction cache 8kB, VIPT, 4-way, linesize 16 bytes.
io scheduler cfq registered (default)
Primary data cache 8kB, 4-way, VIPT, no aliases, linesize 16 bytes
Serial: 8250/16550 driver, 8 ports, IRQ sharing disabled
NR_IRQS:168
serial8250.0: ttyS0 at MMIO 0x18058000 (irq = 104) is a 16550A
brd: module loaded
loop: module loaded
Driver 'sd' needs updating - please use bus_type methods
pata_it821x: controller in pass through mode.
scsi0 : pata_it821x
scsi1 : pata_it821x
pci 0000:00:04.1: PME# disabled
ata1: PATA max UDMA/133 cmd 0x18200010 ctl 0x18200020 bmdma 0x18200000 irq 146
pci 0000:00:04.2: PME# supported from D0 D1 D2 D3hot
ata2: PATA max UDMA/133 cmd 0x18200018 ctl 0x18200024 bmdma 0x18200008 irq 146
pci 0000:00:04.2: PME# disabled
RC32434: Ethernet controller initialized
Switched to NOHz mode on CPU #0
netconsole: local port 6666
NET: Registered protocol family 2
netconsole: local IP 192.168.11.150
IP route cache hash table entries: 1024 (order: 0, 4096 bytes)
netconsole: interface eth0
TCP established hash table entries: 2048 (order: 2, 16384 bytes)
TCP bind hash table entries: 2048 (order: 1, 8192 bytes)
netconsole: remote port 6666
netconsole: remote IP 192.168.11.149
netconsole: remote ethernet address ff:ff:ff:ff:ff:ff
netconsole: device eth0 not up yet, forcing it
netconsole: carrier detect appears untrustworthy, waiting 4 seconds
netconsole: remote port 6666
ata1.00: ATA-7: Maxtor 6L300R0, BAJ41G20, max UDMA/133
ata1.00: 586114704 sectors, multi 0: LBA48
ata1.00: configured for UDMA/133
netconsole: remote IP 192.168.11.149
scsi 0:0:0:0: Direct-Access     ATA      Maxtor 6L300R0   BAJ4 PQ: 0 ANSI: 5
sd 0:0:0:0: [sda] 586114704 512-byte hardware sectors: (300 GB/279 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
netconsole: remote ethernet address ff:ff:ff:ff:ff:ff
 sda: sda1 sda2 sda3
sd 0:0:0:0: [sda] Attached SCSI disk
console [netcon0] enabled
netconsole: network logging started
physmap platform flash device: 00400000 at 1fc00000
physmap-flash.0: Found 1 x16 devices at 0x0 in 8-bit bank
netconsole: device eth0 not up yet, forcing it
 Amd/Fujitsu Extended Query Table at 0x0040
physmap-flash.0: Swapping erase regions for broken CFI table.
number of CFI chips: 1
cfi_cmdset_0002: Disabling erase-suspend-program due to code brokenness.
netconsole: carrier detect appears untrustworthy, waiting 4 seconds
ata1.00: ATA-7: Maxtor 6L300R0, BAJ41G20, max UDMA/133
netconsole: remote port 6666
ata1.00: 586114704 sectors, multi 0: LBA48
netconsole: remote IP 192.168.11.149
ata1.00: configured for UDMA/133
netconsole: remote ethernet address ff:ff:ff:ff:ff:ff
scsi 0:0:0:0: Direct-Access     ATA      Maxtor 6L300R0   BAJ4 PQ: 0 ANSI: 5
netconsole: device eth0 not up yet, forcing it
sd 0:0:0:0: [sda] 586114704 512-byte hardware sectors: (300 GB/279 GiB)
netconsole: carrier detect appears untrustworthy, waiting 4 seconds
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
RedBoot partition parsing not available
sd 0:0:0:0: [sda] Attached SCSI disk
console [netcon0] enabled
netconsole: network logging started
physmap platform flash device: 00400000 at 1fc00000
ata1.00: ATA-7: Maxtor 6L300R0, BAJ41G20, max UDMA/133
physmap-flash.0: Found 1 x16 devices at 0x0 in 8-bit bank
ata1.00: 586114704 sectors, multi 0: LBA48
 Amd/Fujitsu Extended Query Table at 0x0040
ata1.00: configured for UDMA/133
physmap-flash.0: Swapping erase regions for broken CFI table.
scsi 0:0:0:0: Direct-Access     ATA      Maxtor 6L300R0   BAJ4 PQ: 0 ANSI: 5
number of CFI chips: 1
cfi_cmdset_0002: Disabling erase-suspend-program due to code brokenness.
RedBoot partition parsing not available
sd 0:0:0:0: [sda] 586114704 512-byte hardware sectors: (300 GB/279 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
console [netcon0] enabled
netconsole: network logging started
physmap platform flash device: 00400000 at 1fc00000
physmap-flash.0: Found 1 x16 devices at 0x0 in 8-bit bank
 Amd/Fujitsu Extended Query Table at 0x0040
physmap-flash.0: Swapping erase regions for broken CFI table.
number of CFI chips: 1
RedBoot partition parsing not available
RC32434: SPI controller initialized
RC32434: SPI controller initialized
RC32434: SPI controller initialized
rtc-rs5c348 spi0.2: chip found, driver version 0.2
rtc-rs5c348 spi0.2: chip found, driver version 0.2
rtc-rs5c348 spi0.2: spiclk 1000 KHz.
rtc-rs5c348 spi0.2: spiclk 1000 KHz.
rtc-rs5c348 spi0.2: chip found, driver version 0.2
rtc-rs5c348 spi0.2: spiclk 1000 KHz.
rtc-rs5c348 spi0.2: rtc core: registered rtc-rs5c348 as rtc0
rtc-rs5c348 spi0.2: rtc core: registered rtc-rs5c348 as rtc0
rtc-rs5c348 spi0.2: rtc core: registered rtc-rs5c348 as rtc0
TCP cubic registered
TCP cubic registered
TCP cubic registered
NET: Registered protocol family 10
NET: Registered protocol family 10
NET: Registered protocol family 10
IPv6 over IPv4 tunneling driver
IPv6 over IPv4 tunneling driver
IPv6 over IPv4 tunneling driver
NET: Registered protocol family 17
NET: Registered protocol family 17
NET: Registered protocol family 17
RPC: Registered udp transport module.
RPC: Registered udp transport module.
RPC: Registered tcp transport module.
RPC: Registered tcp transport module.
RPC: Registered udp transport module.
turn off boot console early0
turn off boot console early0
RPC: Registered tcp transport module.
turn off boot console early0
rtc-rs5c348 spi0.2: setting system clock to 2009-08-25 20:00:16 UTC (1251230416)
rtc-rs5c348 spi0.2: setting system clock to 2009-08-25 20:00:16 UTC (1251230416)
rtc-rs5c348 spi0.2: setting system clock to 2009-08-25 20:00:16 UTC (1251230416)
Waiting 15sec before mounting root device...
Waiting 15sec before mounting root device...
Waiting 15sec before mounting root device...
Root-NFS: No NFS server available, giving up.
Root-NFS: No NFS server available, giving up.
VFS: Unable to mount root fs via NFS, trying floppy.
VFS: Unable to mount root fs via NFS, trying floppy.
Root-NFS: No NFS server available, giving up.
List of all partitions:
List of all partitions:
VFS: Unable to mount root fs via NFS, trying floppy.
0800       293057352 sda driver: sd
0800       293057352 sda driver: sd
  0801         4891761 sda1
  0801         4891761 sda1
  0802          506047 sda2
  0802          506047 sda2
  0803       287651857 sda3
List of all partitions:
  0803       287651857 sda30800       293057352 sda
No filesystem could mount root, tried:  driver: sd

No filesystem could mount root, tried:   0801         4891761 sda1

Kernel panic - not syncing: VFS: Unable to mount root fs on unknown-block(2,0)
Kernel panic - not syncing: VFS: Unable to mount root fs on unknown-block(2,0)
  0802          506047 sda2
  0803       287651857 sda3
No filesystem could mount root, tried:
Kernel panic - not syncing: VFS: Unable to mount root fs on unknown-block(2,0)


There was no rootfs for it to boot, so of course it panicked...

:)

_________________
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: Fri Aug 28, 2009 2:19 am 
Offline
Site Admin
User avatar

Joined: Mon Aug 28, 2006 1:15 am
Posts: 2606
I've posted a new foonas-em special initramfs, courtesy of timtimred's original setup and my addition of a few things:
http://downloads.buffalo.nas-central.or ... next4fw.gz
- still uses the original ide driver
- has some limited (not fully tested) support for ext4
- has tune2fs binary...
- do not flash to ROM - the image is too large
- fine for booting from hdd or via tftp

This is a bridge EM image that has the tools needed for proper installation of the new kernel. It is not for flashing into ROM.

It is referenced in the HOW TO for Lenny lsmipsel installation: viewtopic.php?f=12&t=20753&p=132251#p132251



The kernel compiles fine for me in uclibc-BuildRoot, but not in uclibc-OpenEmbedded... still digging for the problem there ...... ???

Once we get it compiling in OE as it should, we can think about issuing a new flash-ROM foonas-EM image.

_________________
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: Sat Aug 29, 2009 4:30 am 
Offline
Site Admin
User avatar

Joined: Mon Aug 28, 2006 1:15 am
Posts: 2606
Finally got an all-uClibc kernel + rootfs to boot ...

Quote:
Trying 192.168.11.150...
Connected to 192.168.11.150.
Escape character is '^]'.

______ _____ _____ __ __ _____ ______
| ___| | | \| |/ _ \| ___|
_| ___| - | - | | _ |\ \
| |__| |_____|_____|__|\___|__| |__|_\ \
|___________________________________________|

foonas-em for lsmipsel - http://foonas.org

lsmipsel login: root
Password:
foonas-em$ uname -a
Linux lsmipsel 2.6.30.5 #1 Fri Aug 28 21:57:44 CDT 2009 mips unknown
foonas-em$ cd /lib
foonas-em$ ls
config libdl.so.0 libresolv-0.9.29.so
ld-uClibc-0.9.29.so libm-0.9.29.so libresolv.so.0
ld-uClibc.so.0 libm.so.0 librt-0.9.29.so
libc.so.0 libnsl-0.9.29.so librt.so.0
libcrypt-0.9.29.so libnsl.so.0 libuClibc-0.9.29.so
libcrypt.so.0 libpthread-0.9.29.so modules
libdl-0.9.29.so libpthread.so.0


This was not done using an initramfs image - instead it was done with a (full) foonas uClibc kernel + a uClibc foonas-em rootfs on USB pen drive... so know we know the toolchain is probably not the culprit.

EDIT:

strangeness abounds... the very .config that works fine in Buildroot yields an unbootable kernel in OE... ???

_________________
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
   
Display posts from previous:  Sort by  
Post new topic  Reply to topic  [ 120 posts ]  Go to page Previous 13 4 5 6 7 8 Next

All times are UTC+01:00


Who is online

Users browsing this forum: No registered users and 2 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