[maemo-developers] [maemo-developers] Compiling own kernels and using the wlan module

[From: Peter.Hagg at tietoenator.com]

Hi, 

the inifinite loop is caused by the kernel and initfs not matching each other. We are working on making the kernel re-buildable flashable for Maemo 1.1 final release.

Regards, 

- Pete -

-----Original Message-----
From: maemo-developers-bounces at maemo.org on behalf of Ilkka Poutanen
Sent: Wed 12/7/2005 4:24 PM
To: maemo-developers at maemo.org
Subject: [maemo-developers] Compiling own kernels and using the wlan module
 
Hello,

I'm also trying to build a working IPv6 kernel for F5 hw, but I get
stuck in a boot loop. This is what appears in the serial console:

> Unable to open frame buffer device /dev/fb0
> Unable to initialize. Exiting
> Unable to open frame buffer device /dev/fb0
> Unable to initialize. Exiting

etc. Then later,

> Starting DNS forwarder and DHCP server: dnsmasq. 
> open(/dev/fb0): No such file or directory
> Starting system message bus: dbus-1.
> Error opening /dev/fb0: No such file or directory
> 
> Fatal server error:
> no screens found
> DSME: process '/usr/bin/Xomap           -mouse /dev/input/event0          -dpi dwith return value: 1
> DSME: '/usr/bin/Xomap           -mouse /dev/input/event0          -dpi 96 ' exid with RESET policy -> reset

After this it reboots, and so on ad infinitum.

Everything I've added to the kernel gets built in, so I shouldn't have
to worry about initrd, right? All I did after building the kernel was
flash the new zImage into the device. If I put back the zImage from an
official FIASCO image the reboot behavior goes away.

Any and all pointers appreciated.


-- 
Ilkka Poutanen, research assistant
Tampere University of Technology Institute of Software Systems

_______________________________________________
maemo-developers mailing list
maemo-developers at maemo.org
https://maemo.org/mailman/listinfo/maemo-developers