Buffalo NAS-Central Forums

Welcome to the Linkstation Wiki community
It is currently Fri Jul 20, 2018 5:47 am

All times are UTC+01:00




Post new topic  Reply to topic  [ 43 posts ]  Go to page Previous 1 2 3 Next
Author Message
PostPosted: Fri Oct 12, 2007 9:37 am 
Offline
Newbie

Joined: Thu Aug 17, 2006 3:13 pm
Posts: 63
I succesfully flashed the HG. Then I ran the webinstaller, which installed 2.6 presumable just fine. I then ran kernel26.sh, the HG rebooted, and when I logged in again, I was presented with kernel 2.4.20_mvl31-ppc_Linkstation! Pretty strange. It is consistent with my previous results though, except that now the 2.4 kernel works again. Any idea how to debug this?


Top
   
PostPosted: Fri Oct 12, 2007 1:56 pm 
Offline
Site Admin
User avatar

Joined: Sun Jul 17, 2005 4:34 pm
Posts: 5332
cat /boot/versionPPC
ls -l /boot/
df -h


Top
   
PostPosted: Fri Oct 12, 2007 5:43 pm 
Offline
Newbie

Joined: Thu Aug 17, 2006 3:13 pm
Posts: 63
These are the results right after running kernel26.sh and logging back in with SSH after the reboot:

black:~# cat /boot/versionPPC
v84
black:~# ls -l /boot/
total 4576
-rw-r--r-- 1 root root 18011 Jun 1 2006 COPYING
lrwxrwxrwx 1 root root 19 Oct 12 04:28 System.map -> /boot/System.mapPPC
lrwxrwxrwx 1 root root 13 Oct 12 04:27 System.mapHG -> System.mapPPC
lrwxrwxrwx 1 root root 13 Oct 12 04:27 System.mapKB -> System.mapPPC
lrwxrwxrwx 1 root root 13 Oct 12 04:27 System.mapKG -> System.mapPPC
lrwxrwxrwx 1 root root 13 Oct 12 04:27 System.mapKO -> System.mapPPC
lrwxrwxrwx 1 root root 13 Oct 12 04:27 System.mapLS -> System.mapPPC
-rw-r--r-- 1 root root 780447 Sep 27 04:06 System.mapPPC
lrwxrwxrwx 1 root root 13 Oct 12 04:27 System.mapTS -> System.mapPPC
lrwxrwxrwx 1 root root 9 Oct 12 04:27 config -> configPPC
lrwxrwxrwx 1 root root 9 Oct 12 04:27 configHG -> configPPC
lrwxrwxrwx 1 root root 9 Oct 12 04:27 configKB -> configPPC
lrwxrwxrwx 1 root root 9 Oct 12 04:27 configKG -> configPPC
lrwxrwxrwx 1 root root 9 Oct 12 04:27 configKO -> configPPC
lrwxrwxrwx 1 root root 9 Oct 12 04:27 configLS -> configPPC
-rw-r--r-- 1 root root 52676 Sep 27 04:06 configPPC
lrwxrwxrwx 1 root root 9 Oct 12 04:27 configTS -> configPPC
-rw-r--r-- 1 root root 4862 Aug 4 03:38 loaderHG.o
-rw-r--r-- 1 root root 8164 Aug 29 10:58 loaderII.o
-rw-r--r-- 1 root root 4938 Aug 4 03:38 loaderKB.o
-rw-r--r-- 1 root root 5135 Aug 4 03:38 loaderKG.o
-rw-r--r-- 1 root root 5135 Aug 4 03:38 loaderKO.o
-rw-r--r-- 1 root root 5075 Aug 4 03:38 loaderLS.o
-rw-r--r-- 1 root root 4862 Jun 29 03:24 loaderTS.o
-rw-r--r-- 1 root root 13 Oct 12 12:31 try_new_kernelHG.running
-rw-r--r-- 1 root root 13 Oct 12 12:31 try_new_kernelII
-rw-r--r-- 1 root root 13 Oct 12 12:31 try_new_kernelKB
-rw-r--r-- 1 root root 13 Oct 12 12:31 try_new_kernelKG
-rw-r--r-- 1 root root 13 Oct 12 12:31 try_new_kernelKO
-rw-r--r-- 1 root root 13 Oct 12 12:31 try_new_kernelLS
-rw-r--r-- 1 root root 13 Oct 12 12:31 try_new_kernelTS
lrwxrwxrwx 1 root root 10 Oct 12 04:27 versionHG -> versionPPC
lrwxrwxrwx 1 root root 10 Oct 12 04:27 versionKB -> versionPPC
lrwxrwxrwx 1 root root 10 Oct 12 04:27 versionKG -> versionPPC
lrwxrwxrwx 1 root root 10 Oct 12 04:27 versionKO -> versionPPC
lrwxrwxrwx 1 root root 10 Oct 12 04:27 versionLS -> versionPPC
-rw-r--r-- 1 root root 4 Sep 27 05:46 versionPPC
lrwxrwxrwx 1 root root 10 Oct 12 04:27 versionTS -> versionPPC
lrwxrwxrwx 1 root root 14 Oct 12 04:27 vmlinux.binHG -> vmlinux.binPPC
lrwxrwxrwx 1 root root 14 Oct 12 04:27 vmlinux.binKB -> vmlinux.binPPC
lrwxrwxrwx 1 root root 14 Oct 12 04:27 vmlinux.binKG -> vmlinux.binPPC
lrwxrwxrwx 1 root root 14 Oct 12 04:27 vmlinux.binKO -> vmlinux.binPPC
lrwxrwxrwx 1 root root 14 Oct 12 04:27 vmlinux.binLS -> vmlinux.binPPC
-rwxr-xr-x 1 root root 3760262 Sep 27 05:46 vmlinux.binPPC
lrwxrwxrwx 1 root root 14 Oct 12 04:27 vmlinux.binTS -> vmlinux.binPPC
black:~# df -h
Filesystem Size Used Avail Use% Mounted on
/dev/hda1 365M 226M 121M 66% /
tmpfs 63M 0 63M 0% /lib/init/rw
tmpfs 63M 4.0K 63M 1% /dev/shm
/dev/root.old 9.5M 4.8M 4.8M 50% /initrd
/dev/hda3 275G 51G 224G 19% /mnt


Top
   
PostPosted: Fri Oct 12, 2007 8:01 pm 
Offline
Site Admin
User avatar

Joined: Sun Jul 17, 2005 4:34 pm
Posts: 5332
Looks all good to me (except for a cosmetical glitch), strange. Please run

cd /boot
mv try_new_kernelHG.running try_new_kernelHG
/sbin/shutdown -r now


Top
   
PostPosted: Fri Oct 12, 2007 9:37 pm 
Offline
Newbie

Joined: Thu Aug 17, 2006 3:13 pm
Posts: 63
I tried it, but I got the same result for

cat /boot/versionPPC
ls -l /boot/
df -h

as before. Let me know if there's anything else I can try!


Top
   
PostPosted: Sat Oct 13, 2007 12:55 pm 
Offline
Site Admin
User avatar

Joined: Sun Jul 17, 2005 4:34 pm
Posts: 5332
Try variant-legacy (v73a). Failing that, v66 is almost guaranteed to work, as it contained code to disarm the watchdog in the kernel itself. We haven't been able to port this to recent kernels yet, unfortunately.


Top
   
PostPosted: Sun Oct 14, 2007 10:14 am 
Offline
Newbie

Joined: Thu Aug 17, 2006 3:13 pm
Posts: 63
Thanks for the suggestions. I tried touch /boot/variant-legacy, reran webinstaller and rebooted - same result (version was still v84, but I guess that's correct, or should I manually install v73a instead?). Then I downloaded and untarred the four v66 files - again same result.

I might try doing the whole thing again, precisely recording every step, for doumentation purposes. This is really driving me crazy...


Top
   
PostPosted: Sun Oct 14, 2007 3:56 pm 
Offline
Site Admin
User avatar

Joined: Sun Jul 17, 2005 4:34 pm
Posts: 5332
You should have gotten v73a from variant-legacy? (cat /boot/versionHG)

Try v63. If that fails, I'm out of ideas, especially since it used to work, then ceased working.

Have you tried all combinations of shutdown -r r[rh], reboot, halt, and the power buttons?


Top
   
PostPosted: Sun Oct 14, 2007 5:24 pm 
Offline
Newbie

Joined: Thu Aug 17, 2006 3:13 pm
Posts: 63
Downloaded v63, untarred, rebooted - same result. Then, when I looked at /boot/versionHG, it contained 'v66'. Even if I untar the v63 kernel tar file to another directory, versionHG shows v66. Any idea why?

I'll try all reboot options and let you know!


Top
   
PostPosted: Sun Oct 14, 2007 5:32 pm 
Offline
Newbie

Joined: Thu Aug 17, 2006 3:13 pm
Posts: 63
No luck yet... I am wondering though: try_new_kernelHG is renamed to try_new_kernelHG.running (I keep renaming it back whenever I reboot), so something is happening. Is there any way to maybe insert some echo statements in a boot script to see when it fails/switches back to 2.4?


Top
   
PostPosted: Sun Oct 14, 2007 6:23 pm 
Offline
Site Admin
User avatar

Joined: Sun Jul 17, 2005 4:34 pm
Posts: 5332
They exist but don't work. Well. I'm going to release v85, based on Sylver's universal kernel, soon, and will also simplify the kernel loader. Don't know if it helps, but it might be worth waiting, although it's strictly speaking a beta release.


Top
   
PostPosted: Mon Oct 15, 2007 5:52 pm 
Offline
Newbie

Joined: Thu Aug 17, 2006 3:13 pm
Posts: 63
OK, I'm getting somewhere. I reflashed, apt-get update/dist-upgraded, installed v63 and it worked (more details later). It is strange, though, that v63 reports as v66. Could you check your archives to see what's causing this? I'll try updating to more recent versions to see if it breaks. This is the time to experiment, rather then when it's all functioning again...


Top
   
PostPosted: Mon Oct 15, 2007 9:10 pm 
Offline
Site Admin
User avatar

Joined: Sun Jul 17, 2005 4:34 pm
Posts: 5332
v85 is on the way, you might want to give this release a try. Now that you know what to do in the worst case.


Top
   
PostPosted: Mon Oct 15, 2007 10:15 pm 
Offline
Newbie

Joined: Thu Aug 17, 2006 3:13 pm
Posts: 63
I think I got it. I tried the newest webinstaller (v84), which worked fine. Then I changed my apt/sources.conf to include lenny/testing, updated module-init-tools (which conflicts with modutils - there's my '2.4 won't boot anymore' cause) and libc6. Rebooted the HG, and couldn't login anymore.

Before, I had been running lenny/testing for quite some time, and it did initially survive a reboot. But I guess that in the past 6 months or so, it changed so much that it wouldn't boot. Given that I didn't try rebooting for so long, I didn't notice.

In the long run, I would of course like to be able to run lenny/testing, but for now, I guess I'll have to stick to etch/stable. I just hope I can find all the backports that I need... If it is possible to install testing on the HG, I'd be very happy to know!


Top
   
PostPosted: Tue Oct 16, 2007 9:18 am 
Offline
Site Admin
User avatar

Joined: Sun Jul 17, 2005 4:34 pm
Posts: 5332
Long-term Debian experience makes me stick with the stable versions plus few self-compiled additions. If I could help though...


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

All times are UTC+01:00


Who is online

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