Hi, thank you for the reply. I'll give it a try tomorrow. But I assume this is not a kernel - configuration problem. Because the development board that came with the dnp9200 was running well with the same kernel 2.6.10 + same configuration. So it must be a hardware problem that linux can't handle. I assume it can't handle some noise on the bus lines, but I really don't have a clue - that's just my "feeling". Ole On Mon, 09 Mar 2009 21:00:22 +0100, Thomas Rega <mail@xxxxxxxxxx> wrote: > hi > > did you check your initial console? > > what do you get on kernel 2.4 when you say: > > cat /proc/cmdline > > May be the name for your initial console changed > from ttyS0 (2.4) to ttySMX0 (2.6) or some thing similar. > Probably you will find the name for it in > drivers/serial/the_driver_which_is_used_for_your_board.c > > It is just an assumption ... > > TR > > > > > > > Am Montag, den 09.03.2009, 20:38 +0100 schrieb Ole Loots: >> Hello there, >> >> we are developing an board for the dnp9200 SOC >> (http://www.dilnetpc.com/dnp0069.htm). >> >> We got kernel 2.4.27 running with the board, boots fine, serial port is >> working, ethernet is working, everything is good. >> but when i try to boot kernel 2.6.10, it hangs. >> >> What could be the cause? io pin reset states? Bus pin reset states? >> >> >> this is how far kernel 2.6.10 boots: >> Loading Ramdisk at 101f8c3c - 1039e29b, to 20408000 - 205ad65f ... OK >> >> Starting kernel ... >> [hang] >> >> My question: how could i debug the boot process? In which files could I >> put >> some printk's to see where the kernel hangs? >> >> >> Greets and regards, >> >> Ole >> >> -- >> To unsubscribe from this list: send an email with >> "unsubscribe kernelnewbies" to ecartis@xxxxxxxxxxxx >> Please read the FAQ at http://kernelnewbies.org/FAQ >> >> -- To unsubscribe from this list: send an email with "unsubscribe kernelnewbies" to ecartis@xxxxxxxxxxxx Please read the FAQ at http://kernelnewbies.org/FAQ
