kernel-2.6.14-1.1653_FC4.netdev.6?

[Nathan Grennan]

I am interested in moving to kernel-2.6.14-1.1653_FC4, and I am 
curious when kernel-2.6.14-1.1653_FC4.netdev.6 will be out.

On a side note I seem to have found another bug in sky2. I have no 
error messages or signs of why, but I found I could no longer ping other 
computers on the network via that interface. I also tested it, and they 
couldn't ping it. I first noticed the problem when trying to go to a web 
server on another machine via that interface and it couldn't connect. I 
checked the link status with ethtool and mii-tool. Both reported the 
link was good. I also tried resetting the switch, but no results. 
Finally I rebooted the computer and it worked again. It so far hasn't 
failed again. Any suggestions of what I can do next time to get some 
useful debugging information that might help track down the problem?

[Dominik 'Rathann' Mierzejewski]

On Wednesday, 14 December 2005 at 18:03, Nathan Grennan wrote:
> I am interested in moving to kernel-2.6.14-1.1653_FC4, and I am 
> curious when kernel-2.6.14-1.1653_FC4.netdev.6 will be out.

Me too. I'm interested in updated ipw2200 driver in particular.

Regards,
R.

[John W. Linville]

On Thu, Dec 15, 2005 at 01:51:52AM +0100, Dominik 'Rathann' Mierzejewski wrote:
> On Wednesday, 14 December 2005 at 18:03, Nathan Grennan wrote:
> > I am interested in moving to kernel-2.6.14-1.1653_FC4, and I am 
> > curious when kernel-2.6.14-1.1653_FC4.netdev.6 will be out.
>
> Me too. I'm interested in updated ipw2200 driver in particular.

Workin' on it...

John

[John W. Linville]

On Wed, Dec 14, 2005 at 08:08:03PM -0500, John W. Linville wrote:
> On Thu, Dec 15, 2005 at 01:51:52AM +0100, Dominik 'Rathann' Mierzejewski wrote:
> > On Wednesday, 14 December 2005 at 18:03, Nathan Grennan wrote:
> > > I am interested in moving to kernel-2.6.14-1.1653_FC4, and I am 
> > > curious when kernel-2.6.14-1.1653_FC4.netdev.6 will be out.
> >
> > Me too. I'm interested in updated ipw2200 driver in particular.
>
> Workin' on it...

kernel-2.6.14-1.1653_FC4.netdev.6 is available now:

http://people.redhat.com/linville/kernels/fedora-netdev/

Thanks!

John

[Dominik 'Rathann' Mierzejewski]

On Thursday, 15 December 2005 at 17:27, John W. Linville wrote:
> On Wed, Dec 14, 2005 at 08:08:03PM -0500, John W. Linville wrote:
> > On Thu, Dec 15, 2005 at 01:51:52AM +0100, Dominik 'Rathann' Mierzejewski wrote:
> > > On Wednesday, 14 December 2005 at 18:03, Nathan Grennan wrote:
> > > > I am interested in moving to kernel-2.6.14-1.1653_FC4, and I am 
> > > > curious when kernel-2.6.14-1.1653_FC4.netdev.6 will be out.
> > >
> > > Me too. I'm interested in updated ipw2200 driver in particular.
> >
> > Workin' on it...
>
> kernel-2.6.14-1.1653_FC4.netdev.6 is available now:
>
> http://people.redhat.com/linville/kernels/fedora-netdev/
>
> Thanks!

Thank you! I'll test and see if I can finally get one Acer Travelmate 8100
running with this.

Oh, BTW: any chance of including something like:
CONFIG_STANDALONE=n
CONFIG_PREVENT_FIRMWARE_BUILD=n
CONFIG_ACPI_CUSTOM_DSDT=y
CONFIG_ACPI_CUSTOM_DSDT_FILE="/lib/firmware/DSDT.hex"
in Fedora kernel config?

This Acer has a really broken ACPI DSDT and I wish I didn't have to rebuild
every new kernel.

Regards,
R.

[John W. Linville]

On Thu, Dec 15, 2005 at 10:59:52PM +0100, Dominik 'Rathann' Mierzejewski wrote:
> Oh, BTW: any chance of including something like:
> CONFIG_STANDALONE=n
> CONFIG_PREVENT_FIRMWARE_BUILD=n

I'm not sure what these would buy for us?  Looks like we would just
be cutting-out support for some drivers...?
> CONFIG_ACPI_CUSTOM_DSDT=y
> CONFIG_ACPI_CUSTOM_DSDT_FILE="/lib/firmware/DSDT.hex"
> in Fedora kernel config?

These probably send shudders up the spines of anyone involved w/
supporting Fedora kernels.  I would not expect to see them enabled
in any "official" Fedora kernels anytime soon.
> This Acer has a really broken ACPI DSDT and I wish I didn't have to rebuild
> every new kernel.

You may wish to look here:

http://people.redhat.com/linville/kernels/dsdt/
    http://people.redhat.com/linville/kernels/fc4/

Please note that the FC4.jwltest kernels do _not_ have the collection
of upstream networking fixes that are in the FC4.netdev series.
Also, don't blame me if you laptop explodes...ha-ha, only serious.

John

[Dominik 'Rathann' Mierzejewski]

On Friday, 16 December 2005 at 14:12, John W. Linville wrote:
> On Thu, Dec 15, 2005 at 10:59:52PM +0100, Dominik 'Rathann' Mierzejewski wrote:
> > Oh, BTW: any chance of including something like:
> > CONFIG_STANDALONE=n
> > CONFIG_PREVENT_FIRMWARE_BUILD=n
>
> I'm not sure what these would buy for us?  Looks like we would just
> be cutting-out support for some drivers...?

AFAIR without them the following are inactive.
> > CONFIG_ACPI_CUSTOM_DSDT=y
> > CONFIG_ACPI_CUSTOM_DSDT_FILE="/lib/firmware/DSDT.hex"
> > in Fedora kernel config?
>
> These probably send shudders up the spines of anyone involved w/
> supporting Fedora kernels.  I would not expect to see them enabled
> in any "official" Fedora kernels anytime soon.

ACK. Note to myself: tell everyone NOT to buy Acer laptops if you want
Linux on it.
> > This Acer has a really broken ACPI DSDT and I wish I didn't have to rebuild
> > every new kernel.
>
> You may wish to look here:
>
> http://people.redhat.com/linville/kernels/dsdt/
>    http://people.redhat.com/linville/kernels/fc4/

Thanks.
> Please note that the FC4.jwltest kernels do _not_ have the collection
> of upstream networking fixes that are in the FC4.netdev series.
> Also, don't blame me if you laptop explodes...ha-ha, only serious.

:)
Anyway, until "DSDT in initrd" patch becomes part of FC kernels, I might
as well stick to what I do, because changing a few config params is far
less invasive and time consuming than applying a patch to released kernels.

Regards,
R.

[Dominik 'Rathann' Mierzejewski]

On Friday, 16 December 2005 at 23:56, Dominik 'Rathann' Mierzejewski wrote:
> On Friday, 16 December 2005 at 14:12, John W. Linville wrote:

[...]
> > Please note that the FC4.jwltest kernels do _not_ have the collection
> > of upstream networking fixes that are in the FC4.netdev series.
> > Also, don't blame me if you laptop explodes...ha-ha, only serious.
>
> :)
> Anyway, until "DSDT in initrd" patch becomes part of FC kernels, I might
> as well stick to what I do, because changing a few config params is far
> less invasive and time consuming than applying a patch to released kernels.

I tested the DSDT in initrd patch and it seems to be working fine with
netdev.6 kernel. However, my ipw2200 is still inoperable. Where do I submit
a bugreport?

Presently, even though I have all firmwares from 2.2 to 2.4, it still
fails with

ieee80211_crypt: registered algorithm 'NULL'
ieee80211: 802.11 data/management/control stack, git-1.1.7
ieee80211: Copyright (C) 2004-2005 Intel Corporation 
ipw2200: Intel(R) PRO/Wireless 2200/2915 Network Driver, git-1.0.8
ipw2200: Copyright(c) 2003-2005 Intel Corporation
ACPI: PCI Interrupt 0000:05:03.0[A] -> Link [LNKD] -> GSI 11 (level, low) -> IRQ 11
ipw2200: Detected Intel PRO/Wireless 2915ABG Network Connection
ipw2200: Failed to send TX_POWER: Command timed out.
ipw2200: Failed to send TX_POWER: Command timed out.
ipw2200: Failed to send TX_POWER: Command timed out.
ipw2200: Failed to send TX_POWER: Command timed out.
ipw2200: Failed to send TX_POWER: Command timed out.
ipw2200: Unable to initialize device after 5 attempts.
ipw2200: failed to register network device
ACPI: PCI interrupt for device 0000:05:03.0 disabled
ipw2200: probe of 0000:05:03.0 failed with error -5
ieee80211_crypt: unregistered algorithm 'NULL'

lspci -nv snippet:
05:03.0 Class 0280: 8086:4223 (rev 05)
        Subsystem: 8086:1001
        Flags: medium devsel, IRQ 11
        Memory at c8214000 (32-bit, non-prefetchable) [size=4K]
        Capabilities: [dc] Power Management version 2

Additionally, I can't turn on debugging. modprobe ipw2200 debug=0xffff
output is no more verbose than without the debug option.

Regards,
R.

[Peter Jones]

On Mon, 2005-12-19 at 23:43 +0100, Dominik 'Rathann' Mierzejewski wrote:
> Additionally, I can't turn on debugging. modprobe ipw2200 debug=0xffff
> output is no more verbose than without the debug option.

With which kernel?  I turned CONFIG_IPW_DEBUG back on several days
ago...

[John W. Linville]

On Tue, Dec 20, 2005 at 12:01:17PM -0500, Peter Jones wrote:
> On Mon, 2005-12-19 at 23:43 +0100, Dominik 'Rathann' Mierzejewski wrote:
> > Additionally, I can't turn on debugging. modprobe ipw2200 debug=0xffff
> > output is no more verbose than without the debug option.
>
> With which kernel?  I turned CONFIG_IPW_DEBUG back on several days
> ago...

The corresponding CONFIG_IPW2100_DEBUG and CONFIG_IPW2200_DEBUG are
probably off in the netdev.6 kernel, iirc.

John

[Peter Jones]

On Tue, 2005-12-20 at 14:55 -0500, John W. Linville wrote:
> On Tue, Dec 20, 2005 at 12:01:17PM -0500, Peter Jones wrote:
> > On Mon, 2005-12-19 at 23:43 +0100, Dominik 'Rathann' Mierzejewski wrote:
> > > Additionally, I can't turn on debugging. modprobe ipw2200 debug=0xffff
> > > output is no more verbose than without the debug option.
> >
> > With which kernel?  I turned CONFIG_IPW_DEBUG back on several days
> > ago...
>
> The corresponding CONFIG_IPW2100_DEBUG and CONFIG_IPW2200_DEBUG are
> probably off in the netdev.6 kernel, iirc.

They're probably worth turning back on there, as well.  They don't
change any behavior unless you use the debug= option or
modify /sys/bus/pci/drivers/ipw*/debug_level , and it's basically
impossible to figure out if something is going wrong in the driver
without doing so.

(and the driver is still relatively young, so often that kind of
diagnosis is needed)

[Dominik 'Rathann' Mierzejewski]

On Tuesday, 20 December 2005 at 18:01, Peter Jones wrote:
> On Mon, 2005-12-19 at 23:43 +0100, Dominik 'Rathann' Mierzejewski wrote:
> > Additionally, I can't turn on debugging. modprobe ipw2200 debug=0xffff
> > output is no more verbose than without the debug option.
>
> With which kernel?  I turned CONFIG_IPW_DEBUG back on several days
> ago...

John's. And he already said it's disabled in his. *sigh* I guess it's
recompile time again. ;)

R.

[Nathan Grennan]

John W. Linville wrote:
> kernel-2.6.14-1.1653_FC4.netdev.6 is available now:
>
> http://people.redhat.com/linville/kernels/fedora-netdev/

Thanks, seems to be working great so far.