macsat.com OpenWrt and ASUS WL Forum
January 08, 2009, 15:14:25 PM *
Welcome, Guest. Please login or register.
Did you miss your activation email?
Login with username, password and session length
News: Back to macsat.com
 
   Home   Help Search Login Register  
Pages: 1 [2]   Go Down
  Print  
Author Topic: Booting a new kernel with 'monte'  (Read 17684 times)
0 Members and 1 Guest are viewing this topic.
sanecyclist
Newbie
*
Offline Offline

Posts: 45


View Profile
« Reply #15 on: April 25, 2007, 19:33:56 PM »

Remenber. Network interfaces does not respond if they are not bridged.
Alright. Why is that?

Quote
Now I have a serial port in the whd  Smiley
Nice. Did you have to get out the soldering iron?
Logged
pagano
Jr. Member
**
Offline Offline

Posts: 61


View Profile
« Reply #16 on: April 25, 2007, 23:41:29 PM »

Remenber. Network interfaces does not respond if they are not bridged.
Alright. Why is that?
I don't known. r6040 (network driver) is a binary module in our source.
I have tested and it works while is bridged. You can bridge br0 and br1 for eth1 and wl0 (or change names)

Quote
Now I have a serial port in the whd  Smiley
Nice. Did you have to get out the soldering iron?
And a notebook with serial port  Grin

Advances in monte. I have added a lot of debug lines in kmonte.c
1) Restarting system in 2 secconds (this is a original debug msg)
2) No return point. ok.
3) Disable PCI. ok
4) Bussines begins (check) .ok
5) Ligths OFF just before the assembler long jump (interrupts disabled)... ok.

But no kernel messages after jump to memory adress.  Huh
Like it's not a firmware change, i am mixing amit recovery jump (in arch/i386/boot/setup.S) with kmonte.c
Since monte works perfect in my PC with 2.4.28 kernel, i think it's a device feature  Sad
Patch 2.4.17 in kernel source (and flash) is needed to work with it.
The file arch/i386/kernel/setup.c needs some "human" help to apply the patch but is easy.

With kexec, the same wall. Reboot PC routines does not work in our device. (it also works in PC with 2.4.28 kernel)
Debug messages in kexec show a "I'm in purgatory" text before freezes. But i have not compile kexec-tools from sources.
Logged
sanecyclist
Newbie
*
Offline Offline

Posts: 45


View Profile
« Reply #17 on: April 26, 2007, 12:29:55 PM »

Great effort, pagano, shame it doesn't work easily. There's a load of custom hardware on the chip, and any of it, particularly the bus and memory controllers, might stop the reboot from working. Perhaps a diff between the MGB100 kernel and vanilla kernel sources could provide some clues? You've probably seen the R8610 datasheet.

Shame the bootloader seems to be totally closed. Is there any delay between switching the device on and the first kernel boot messages appearing? If it's RedBoot, sending Ctrl-C during that period might bring up a boot prompt. Any other keys might be worth trying too. Or perhaps the bootloader uses a different baud rate from the kernel.

On the other hand, OpenWRT and Debian do work with the current kernel anyway, so perhaps we should just stick with that ...

Logged
pagano
Jr. Member
**
Offline Offline

Posts: 61


View Profile
« Reply #18 on: May 26, 2007, 11:57:59 AM »

> perhaps we should just stick with that ...

You're right. Is better to stop before brick our WHD Smiley
Logged
Pages: 1 [2]   Go Up
  Print  
 
Jump to:  

English Steel 1.6 © Saxon North Technologies
Powered by MySQL Powered by PHP Powered by SMF 1.1.7 | SMF © 2006-2008, Simple Machines LLC
Joomla Bridge by JoomlaHacks.com
Valid XHTML 1.0! Valid CSS!
Page created in 0.256 seconds with 24 queries.