Re: About Siso

[David Montalvo]

Solved that. I didn't pass CROSS_COMPILE to busybox. Also with newer versions of busybox the PREFIX environment variable changed to CONFIG_PREFIX.

Another problem.

I have an ipw2200 Intel Pro Wireless 2200BG Mini PCI card. The kernel support it, but it says I have to install the firmware in order to work. Reading Documentation/networking/README.ipw2200 it states:

****************************
5.Firmware installation
-------------------------------------------------------
The driver requires a firmware image, download it and extract the files under /lib/firmware (or wherever your HOTPLUG'S FIRMWARE.AGENT will look for the firmware files)

*****************************

That means that I have to:
1) enable in the Kernel Support for Hotplugable Devices and allow FIRMWARE Loading (CONFIG_FW_LOAD=1) and remove Prevent Firmware Build.
2) Install hotplug scripts and modify ROOTFS_DIR and modify boot scripts in order to Hotplug to run.

You are using DEVFS that soon will be obsolete. Some suggest to use UDEVD instead.

I have recompiled the kernel (hotplug support, firmware loading, ipw2200 (in kernel and as a module), Installed hotplug scripts. installed firmware files where hotplug's firmware.agent states. But I dont know how to start hotplug. And the driver keeps sending me the following message:

ipw2200: Detected Intel PRO/Wireless 2200BG Network Connection
ipw2200: ipw2200-bss.fw request_firmware failed: Reason -2
ipw2200: Unable to load firmware: -2
ipw2200: failed to register network device
ACPI: PCI interrupt for device 0000:04:02.0 disabled
ipw2200: probe of 0000:04:02.0 failed with error -5

which IPW2200 sourceforge says:

CAUSE: this may be due to any one of the following reasons:
-  firmware in wrong location or wrong firmware version. Follow the

   instructions in the section LOADING FIRMWARE VIA HOT-PLUG above.
-  sysfs may not be mounted. Follow the instructions in the SYSFS section
   above.

Any help will be appreciated. Thanks.

On 10/23/07, Coert Vonk <coert...@gmail.com> wrote:

Hi David,

 

This is where the kernel is done initializing and passes control to busybox.  Two things to check:

• Check that Busybox was compiled with CROSS_COMPILE.
• Libraries may be missing.  Check with "objdump -x busybox | grep NEEDED").  This should reveal that it uses libgcc_s.so.1 and libc.so.0, but no other dependencies.  Make sure these libraries are installed on the target system.

/c

please CC siso-...@googlegroups.com  in your reply so this exchange gets archived

 

---

From: David Montalvo [mailto:efr...@gmail.com]
Sent: Tuesday, October 23, 2007 3:48 PM
To: coert...@gmail.com
Subject: About Siso

Hi.

I'm using your implementation for a x86 Pc like appliance. I'm having some troubles in boot sequence. I can't find the /linurc file and the kernel panics saying no init found. I changed kernel config options in order to enable Virtual terminal and watch messages in my monitor.

Any suggestion what I am missing?

Thanks for any help.

--
Brevity is the soul of wit

--
Brevity is the soul of wit