On Tuesday 17 January 2006 09:48, Rainer Peter Feller wrote:
> are all ipw-2.4-*.fw files present in your firmware dir?
Yes, they are.
Searching in the www, I found a bug-message
"http://lists.debian.org/debian-kernel/2005/03/msg00233.html"; . Somebody
wrote down the log for the event, the ipw
On Mon, 2006-01-16 at 18:23 -0500, David Fix wrote:
> You know, you could probably just download the latest firmware from the card
> and flash it using a boot floppy, too. ;)
>
> Dave
eh ... I think that THIS firmware files are not to flash, but runtime firmware
...
so no, they can't and s
On Mon, 2006-01-16 at 23:18 +0100, Dr. Edgar Alwers wrote:
> On Monday 16 January 2006 20:06, Andrew Benton wrote:
> After a new reboot dmesg changed into:
>
> ipw2200: Intel PRO/Wireless 2200/2915 Network Driver, 1.0.8
> ipw2200 Copyright...
> ACPI: PCI Interrupt Link [LNKG] enab
> No, of course I had not. No one instruction has told me.to
> do. I am really
> _getting_mad ! I am used to work on research and
> development., but this is a
> very hard case of try and error approach. Nevertheless,
> please continue
> helping, I will return efforts writing a hint for this
> ter
On Monday 16 January 2006 20:06, Andrew Benton wrote:
> Have you added a rule to /etc/udev/rules.d/25-lfs.rules to call the
> firmware_helper to load the firmware? Something like
>
> ACTION=="add", SUBSYSTEM=="firmware", RUN+="/sbin/firmware_helper"
>
No, of course I had not. No one instruction ha
Dr. Edgar Alwers wrote:
On Sunday 15 January 2006 10:31, Andrew Benton wrote:
If you want udev to load firmware, you'll need the firmware_helper.
Compile udev with
make EXTRAS="extras/firmware"
make EXTRAS="extras/firmware" install
OK, I did so. But nothing special happens: the /EXTRA=extra/fi
On Sun, 2006-01-15 at 22:45 +0100, Dr. Edgar Alwers wrote:
> OK, I did so. But nothing special happens: the /EXTRA=extra/firmware
> directory
> is empty. "lsmod" shows ipw2200 but nothing about an firmware. Also, there
> are not error messages. Is that OK ? How can I see if the firmware was
>
On Sunday 15 January 2006 10:31, Andrew Benton wrote:
> If you want udev to load firmware, you'll need the firmware_helper.
> Compile udev with
> make EXTRAS="extras/firmware"
> make EXTRAS="extras/firmware" install
OK, I did so. But nothing special happens: the /EXTRA=extra/firmware directory
is
Dr. Edgar Alwers wrote:
On Friday 13 January 2006 17:05, Rainer Peter Feller wrote:
make sure you compiled/installed udev with
EXTRAS="extras/firmware extras/run_directory"
No,according with LFS instructions, I did "make EXTRAS=extras/run_directory"
is that not correct ? ( udev-071 )
If you w
On Friday 13 January 2006 17:05, Rainer Peter Feller wrote:
> I use hotplug
>
-> me too
> check if udevd is running (udevd --daemon)
-> it is
>
On Fri, 13 Jan 2006 23:12:02 +0100, <[EMAIL PROTECTED]> wrote:
> After all that, I got a significant changed behaviour: a lot of messages of
> the kind
> "Jan 13 portable udevd-event[8701]: run_program: exec of program
> '/sbin/udev_run_devd' failed.
> What could this mean ?
udev_run_devd is in
On Thursday 12 January 2006 05:22, Jim Gifford wrote:
> Another issues is that you don't have the firmware_helper installed from
> udev, you have to add it in by using
> make EXTRAS="extras/firmware" to compile. make EXTRAS="extras/firmware"
> install to install it.
Well, I did this
>
> If you are
On Sun, 2006-01-08 at 22:49 +0100, Dr. Edgar Alwers wrote:
> On Saturday 07 January 2006 23:03, Gabe Yoder wrote:
> > I'm still using one of the 2.6.14.x kernels, but I don't think that should
> > make any difference (and I have an ipw2100 instead of an ipw2200). When
> > you installed hotplug, it
On Thu, 2006-01-12 at 22:59 +0100, Dr. Edgar Alwers wrote:
> I thought, that the ability of the system to recognize the behaviour of a
> device on the fly, was exactly what we describe as "hot plug", that means
> plugging in or out a device in a "hot" system. Is that really not true ?
Similar id
Dr. Edgar Alwers wrote:
On Thursday 12 January 2006 04:18, Alexander E. Patrakov wrote:
This is not hotplug. Hotplug is working if you can pull and push the
card, not the cable.
just for the sake of learning: if I take of the cable out of my eth0-card from
the PC, I get inmediately the mes
Dr. Edgar Alwers wrote:
On Thursday 12 January 2006 05:22, Jim Gifford wrote:
All in the nutshell, I have the impression, that Linux-Intel PRO/Wireless
2200BG is still in a very early state of development ? Would it not be a
good idea to include some instructions in the BLFS-Book ?
I hav
> just for the sake of learning: if I take of the cable out of
> my eth0-card from
> the PC, I get inmediately the message: "eth0: link down".Or after
> reconnecting, "eth0: link up, 100Mbps, full duplex, lpa 0x41E1". Up
> to now, I thought, that the ability of the system to recognize the
> behavi
On Thursday 12 January 2006 04:18, Alexander E. Patrakov wrote:
> This is not hotplug. Hotplug is working if you can pull and push the
> card, not the cable.
just for the sake of learning: if I take of the cable out of my eth0-card from
the PC, I get inmediately the message: "eth0: link down".Or
On Thursday 12 January 2006 05:22, Jim Gifford wrote:
> This is a bug in the 2.6.15 kernel, some of the wireless scripts use a
> /sys/class/net/eth0/wireless variable to detect things, so that may be
> one issue.
OK, I really think, that 2.6.15 still may have some problems with Wireless
issues, as
Simon Geard wrote:
do
you envisage this configuration appearing in standard LFS any time soon?
Not this configuration, but something similar
http://linuxfromscratch.org/pipermail/lfs-dev/2006-January/055038.html
Andy
--
http://linuxfromscratch.org/mailman/listinfo/blfs-support
FAQ: http://ww
On Wed, 2006-01-11 at 20:22 -0800, Jim Gifford wrote:
> If you are using the 2.6.15 code, you may want to try using the new udev
> rules my cross-lfs team has come up with. I can say the do work on
> wireless since that's one of the test platforms we had during their
> development. These scripts
This is a bug in the 2.6.15 kernel, some of the wireless scripts use a
/sys/class/net/eth0/wireless variable to detect things, so that may be
one issue.
Another issues is that you don't have the firmware_helper installed from
udev, you have to add it in by using
make EXTRAS="extras/firmware" t
Dr. Edgar Alwers wrote:
Following http://ipw2200.sourceforge.net/index.php#issues I changed also the
hotplug timeout to 100, but withouth results. Btw., hotplug is working, as I
can confirm plugging and unplugging the eth0 cable.
This is not hotplug. Hotplug is working if you can pull and push
On Monday 09 January 2006 00:14, Gabe Yoder wrote:
> It sounds like you should try following Andrew's suggestion and build the
> driver as a module and not build it directly into the kernel
I did it and I still get problems. Here the results of dmesg:
--
ipw2200: Intel(R) PRO/Wireless 220
On Sunday 08 January 2006 16:49, Dr. Edgar Alwers wrote:
> On Saturday 07 January 2006 23:03, Gabe Yoder wrote:
> > I'm still using one of the 2.6.14.x kernels, but I don't think that
> > should make any difference (and I have an ipw2100 instead of an ipw2200).
> > When you installed hotplug, it s
On Saturday 07 January 2006 23:03, Gabe Yoder wrote:
> I'm still using one of the 2.6.14.x kernels, but I don't think that should
> make any difference (and I have an ipw2100 instead of an ipw2200). When
> you installed hotplug, it should have made a directory /etc/hotplug and put
> a bunch of *.a
Dr. Edgar Alwers wrote:
I am trying to put in operation an Intel Pro/Wireless 2200BG WLAN centrino
laptop. I did compile a 2.6.15 kernel, which is supposed to support WLAN.
So far, I also downloaded the firmware ipw2200-fw-2.4 from Intel, and here my
problem starts: I did unpack the firmware ipw
I'm still using one of the 2.6.14.x kernels, but I don't think that should
make any difference (and I have an ipw2100 instead of an ipw2200). When you
installed hotplug, it should have made a directory /etc/hotplug and put a
bunch of *.agent files in there. One of those is firmware.agent. Min
28 matches
Mail list logo
