1) In the press was published that 2.6.29 would include the rt2860 WIFI driver. However, in 2.6.29-rc2 one find nowhere this driver. rt2x00 don't work, at least ifconfig ra0 up gives a error message. and to compile it from source code, works with 2.6.26.X but not with 2.6.29-rc2 (plenty error messages) What's the situation of the rt2860 driver ?? The only senseful criterion for inclusion of a driver in the kernel is not the maturity of the code, but the number of sellings of that hardware in the shops, and that driver is necessary for msi wind notebooks, so it should be included into the kernel.
2) With 2.6.29-rc2 (and msi wind), compiz starts but quickly crashs. In 2.6.26.X it was stable. That should be verified / corrected (regression)
3) eth cards don't work more since 2.6.27 . ifconfig eth0 successful, but no connection. I suppose that's a problem of the kernel config (because on other compilations/configurations it works) -- perhaps of the iptables, package treatment, or routing, not of the eth drivers themselves. However, although searching long time, I don't find out the reason. This should be checked, and removed from the kernel config such options which potentially turn networking not longer working.
[email protected]
Linux SYS
mirror: ftp://ftp5.gwdg.de/pub/linux/install/sys/
ftp://ftp.uni-siegen.de/pub/sys-linux
On Saturday 17 January 2009 14:30:01 We La wrote:
> 1) In the press was published that 2.6.29 would include the rt2860 WIFI
> driver. However, in 2.6.29-rc2 one find nowhere this driver. rt2x00 don't
> work, at least ifconfig ra0 up gives a error message. and to compile it
> from source code, works with 2.6.26.X but not with 2.6.29-rc2 (plenty error
> messages) What's the situation of the rt2860 driver ?? The only senseful
> criterion for inclusion of a driver in the kernel is not the maturity of
> the code, but the number of sellings of that hardware in the shops, and
> that driver is necessary for msi wind notebooks, so it should be included
> into the kernel.
It's in the kernel. You need to enable CONFIG_STAGING which is Greg's option
for "these drivers aren't as good quality as normal Linux drivers but we're
providing them anyway for early adopters". Exactly your argument, I think.
Device Drivers -> Staging drivers
Exclude Staging drivers from being built -> n
Ralink 2860 wireless support (NEW)
Hope this helps.
--
Cheers,
Alistair.
On Sat, Jan 17, 2009 at 06:30:01AM -0800, We La wrote:
> 3) eth cards don't work more since 2.6.27 . ifconfig eth0
> successful, but no connection. I suppose that's a problem of the
> kernel config (because on other compilations/configurations it
> works) -- perhaps of the iptables, package treatment, or routing,
> not of the eth drivers themselves. However, although searching long
> time, I don't find out the reason. This should be checked, and
> removed from the kernel config such options which potentially turn
> networking not longer working.
That's not a useful bug report. "eth0" is the name given to a large
number of different ethernet drivers. For example on my X61 laptop,
running 2.6.29-rc1, eth0 works just fine --- and it refers to the
e1000e driver. i.e., from my boot-time dmesg:
[ 1.383904] e1000e: Intel(R) PRO/1000 Network Driver - 0.3.3.3-k6
[ 1.384002] e1000e: Copyright (c) 1999-2008 Intel Corporation.
[ 1.384165] e1000e 0000:00:19.0: PCI INT A -> GSI 20 (level, low) -> IRQ 20
[ 1.384285] e1000e 0000:00:19.0: setting latency timer to 64
[ 1.384536] e1000e 0000:00:19.0: irq 27 for MSI/MSI-X
[ 1.590106] 0000:00:19.0: eth0: (PCI Express:2.5GB/s:Width x1) 00:16:d3:cc:a4:27
[ 1.590236] 0000:00:19.0: eth0: Intel(R) PRO/1000 Network Connection
[ 1.590370] 0000:00:19.0: eth0: MAC: 5, PHY: 6, PBA No: ffffff-0ff
On my Lenovo S10 netbook, eth0 refers to the Broadcom Tigon3 (tg3)
driver. From my boot-time dmesg: (this happens to be a 2.6.28 kernel
since I was testing a reported ext4 problem at the time, but
2.6.29-rc1 also works just fine)
[ 1.962792] tg3.c:v3.94 (August 14, 2008)
[ 1.962979] tg3 0000:02:00.0: PCI INT A -> GSI 16 (level, low) -> IRQ 16
[ 1.963149] tg3 0000:02:00.0: setting latency timer to 64
[ 2.193004] eth0: Tigon3 [partno(BCM95906) rev c002 PHY(5906)] (PCI Express) 10/100Base-TX Ethernet 00:1e:68:f0:94:f8
[ 2.193187] eth0: RXcsums[1] LinkChgREG[0] MIirq[0] ASF[0] WireSpeed[0] TSOcap[0]
[ 2.193356] eth0: dma_rwctrl[76180000] dma_mask[64-bit]
As for why it doesn't work on your system, we really need to know what
device driver is involved. If you send the dmesg output right after
your system booted on 2 6.27 system, where your ethernet device
worked, and a dmesg output after your system booted on a 2.6.28
kernel, where you are having trouble, and your kernel .config from
2.6.28, we probably can help you. At a guess you probably didn't
configure the right network driver, or maybe for some reason the
ethernet device didn't come up correctly (does ifconfig -a show the
eth0 device?), or some other user/configuration error. It certainly
isn'ta problem with all "eth cards", as you seem to suggest.
Regards,
- Ted
On Sat, Jan 17, 2009 at 06:30:01AM -0800, We La wrote:
> 1) In the press was published that 2.6.29 would include the rt2860
> WIFI driver. However, in 2.6.29-rc2 one find nowhere this driver.
> rt2x00 don't work, at least ifconfig ra0 up gives a error message.
> and to compile it from source code, works with 2.6.26.X but not with
> 2.6.29-rc2 (plenty error messages) What's the situation of the rt2860
> driver ?? The only senseful criterion for inclusion of a driver in
> the kernel is not the maturity of the code, but the number of sellings
> of that hardware in the shops, and that driver is necessary for msi
> wind notebooks, so it should be included into the kernel.
It is there, and I have gotten reports of it working properly. What
problems have you had with it?
thanks,
greg k-h