Skip to contentSkip to conversation

2.6.0test3 problems on Acer TravelMate 260 (ALSA,ACPIvsSynaptics,yenta)

DISCUSSION Santiago Garcia Mantinan 4 participants 8 messages Aug 11, 2003 – Aug 12, 2003

lore
Share & tools
lore
#0 lore raw

Hi!

I've been evaluating kernel 2.6.0test3 on my Acer TravelMate 260 Laptop, it is a PIII Movile at 1GHz with intel chipset (i82801+i830M) 256 Megs of RAM.

There are some weird old problems, like the yenta problem, the problem with the cardbus interface is that you have to insert the card twice so that it notices the card is in, everything else seems ok, on 2.4 there is the same problem, so I'm using the pcmcia-cs i82365 driver which is working perfectly. This is what the 2.6 yenta driver says on startup:

Yenta: CardBus bridge found at 0000:01:09.0 [1025:1024] Yenta IRQ list 02b8, PCI irq10
Socket status: 30000007

This is what lspci tells about the cardbus interface:

01:09.0 CardBus bridge: O2 Micro, Inc. OZ6912 Cardbus Controller
Subsystem: Acer Incorporated [ALI]: Unknown device 1024
Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr-
Stepping+ SERR- FastB2B-
Status: Cap+ 66Mhz- UDF- FastB2B- ParErr- DEVSEL=slow >TAbort-
<TAbort- <MAbort- >SERR- <PERR-

        Latency: 168
        Interrupt: pin A routed to IRQ 10
        Region 0: Memory at 10001000 (32-bit, non-prefetchable) [size=4K]
        Bus: primary=01, secondary=02, subordinate=05, sec-latency=176
        Memory window 0: 10400000-107ff000 (prefetchable)
        Memory window 1: 10800000-10bff000
        I/O window 0: 00001000-000010ff
        I/O window 1: 00001400-000014ff
        BridgeCtl: Parity- SERR- ISA- VGA- MAbort- >Reset- 16bInt+ PostWrite+
        16-bit legacy interface ports at 0001

00: 17 12 72 69 87 00 10 04 00 00 07 06 00 a8 02 00 10: 00 10 00 10 a0 00 00 02 01 02 05 b0 00 00 40 10 20: 00 f0 7f 10 00 00 80 10 00 f0 bf 10 01 10 00 00 30: fd 10 00 00 01 14 00 00 fd 14 00 00 0a 01 80 05 40: 25 10 24 10 01 00 00 00 00 00 00 00 00 00 00 00 50: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 60: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 70: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00

The ALSA problem is new, ALSA for 2.4 (0.9.4) is working perfectly, but the 2.6.0 driver doesn't allow me to hear the beeper sound, the pcm sounds seem ok, but no matter what I do with the mixer, ALSA doesn't seem to drive the beeper sound to the speakers. The card driver is the snd_intel8x0 with its associated snd_ac97_codec, alsamixer says this about it:
Card: Intel 82801CA-ICH3
Chip: Cirrus Logic CS4299 rev 4
And this is what lspci says:

00:1f.5 Multimedia audio controller: Intel Corp. 82801CA/CAM AC'97 Audio (rev 02)
Subsystem: Acer Incorporated [ALI]: Unknown device 1024
Control: I/O+ Mem- BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr-
Stepping- SERR- FastB2B-
Status: Cap- 66Mhz- UDF- FastB2B+ ParErr- DEVSEL=medium >TAbort-
<TAbort- <MAbort- >SERR- <PERR-

        Latency: 0
        Interrupt: pin B routed to IRQ 10
        Region 0: I/O ports at a000 [size=256]
        Region 1: I/O ports at a400 [size=64]

00: 86 80 85 24 05 00 80 02 02 00 01 04 00 00 00 00 10: 01 a0 00 00 01 a4 00 00 00 00 00 00 00 00 00 00 20: 00 00 00 00 00 00 00 00 00 00 00 00 25 10 24 10 30: 00 00 00 00 00 00 00 00 00 00 00 00 0a 02 00 00

Also new is the problem that ACPI is causing on the Synaptics touchpad, the touchpad driver is loosing sync all the time, and I have discovered that only disabling ACPI this gets solved, there was no problem with ACPI as of 2.4, but there was also no kernel Synaptics driver, however normal driver with the XFree Driver didn't have this problems. Without ACPI the touchpad driver works perfectly. I don't know what data can I provide to help tracking this down :-(

I don't have any problem to test patches or try to provide more info on any of this things.

Regards...

Signature · 1 line
Manty/BestiaTester -> http://manty.net
#1 lore raw
Quoted 9 lines · Santiago Garcia Mantinan

There are some weird old problems, like the yenta problem, the problem with the cardbus interface is that you have to insert the card twice so that it notices the card is in, everything else seems ok, on 2.4 there is the same problem, so I'm using the pcmcia-cs i82365 driver which is working perfectly. This is what the 2.6 yenta driver says on startup:

Yenta: CardBus bridge found at 0000:01:09.0 [1025:1024] Yenta IRQ list 02b8, PCI irq10
Socket status: 30000007

Please supply the following information:

- does 2.6.0-test3 detect the card at boot ?
- if not, what are the complete kernel messages ?

- does 2.6.0-test3 detect it at every insertion after the first "insert remove insert" cycle, or does it always need an even number of insertions for it to be recognised?

- does 2.4 and 2.6-test3 yenta find the same IRQs ?

- which version of pcmcia-cs are you using with 2.4 ?

- which IRQ(s) does 2.4 i82365 use ?

Signature · 2 lines
Russell King ([email protected])                The developer of ARM Linux
             http://www.arm.linux.org.uk/personal/aboutme.html
#2 lore raw

Hey, what a quick reply, here goes the info you asked for, if you need any more just ask for it.

Quoted 2 lines

- does 2.6.0-test3 detect the card at boot ?
- if not, what are the complete kernel messages ?

Yes and no, I mean, it detects a card, but not the card it has in, it tries to load memory_cs when I have a wireless card in, the card should load hostap_cs, in fact if after booting I remove it and insert it twice, it recognices the card well and tries to load hostap_cs.

Here are the messages it outputs:

Linux Kernel Card Services 3.1.22
options: [pci] [cardbus] [pm]
PCI: IRQ 10 for device 0000:01:09.0 doesn't match PIRQ mask - try pci=usepirqmask
PCI: Found IRQ 11 for device 0000:01:09.0
PCI: Sharing IRQ 11 with 0000:00:1d.1
IRQ routing conflict for 0000:01:09.0, have irq 10, want irq 11
Yenta: CardBus bridge found at 0000:01:09.0 [1025:1024] Yenta IRQ list 02b8, PCI irq10
Socket status: 30000811
cs: memory probe 0x0c0000-0x0fffff: excluding 0xc0000-0xcffff 0xdc000-0x103fff

Quoted 3 lines

- does 2.6.0-test3 detect it at every insertion after the first "insert remove insert" cycle, or does it always need an even number of insertions for it to be recognised?

It always needs an even number of insertions.

Quoted 1 line

- does 2.4 and 2.6-test3 yenta find the same IRQs ?

Seems so, these are the messages for yenta on 2.4.21:

Linux Kernel Card Services 3.1.22
options: [pci] [cardbus] [pm]
PCI: Found IRQ 11 for device 01:09.0
PCI: Sharing IRQ 11 with 00:1d.1
IRQ routing conflict for 01:09.0, have irq 10, want irq 11 Yenta IRQ list 00b8, PCI irq10
Socket status: 30000007
cs: memory probe 0x0c0000-0x0fffff: excluding 0xc0000-0xcbfff 0xe0000-0xfffff

Quoted 1 line

- which version of pcmcia-cs are you using with 2.4 ?

3.2.2

Quoted 1 line

- which IRQ(s) does 2.4 i82365 use ?

The same ones as yenta, here you have the messages I get with it just in case:

Linux PCMCIA Card Services 3.2.2
kernel build: 2.4.21 #1 Sat Jun 14 19:43:14 CEST 2003
options: [pci] [cardbus] [apm]
Intel ISA/PCI/CardBus PCIC probe:
PCI: Found IRQ 11 for device 01:09.0
PCI: Sharing IRQ 11 with 00:1d.1
IRQ routing conflict for 01:09.0, have irq 10, want irq 11
O2Micro OZ6912 rev 00 PCI-to-CardBus at slot 01:09, mem 0x10001000
host opts [0]: [pci/way] [pci irq 10] [lat 32/176] [bus 2/5] ISA irqs (default) = 3,4,5,7 PCI status changes

Hope this helps, if you need anything else, just ask for it.

Regards...

Signature · 1 line
Manty/BestiaTester -> http://manty.net
#3 lore raw
Quoted 21 lines · Santiago Garcia Mantinan

Seems so, these are the messages for yenta on 2.4.21:

Linux Kernel Card Services 3.1.22
options: [pci] [cardbus] [pm]
PCI: Found IRQ 11 for device 01:09.0
PCI: Sharing IRQ 11 with 00:1d.1
IRQ routing conflict for 01:09.0, have irq 10, want irq 11 Yenta IRQ list 00b8, PCI irq10
Socket status: 30000007
cs: memory probe 0x0c0000-0x0fffff: excluding 0xc0000-0xcbfff 0xe0000-0xfffff

Quoted 1 line

- which version of pcmcia-cs are you using with 2.4 ?

3.2.2

Quoted 1 line

- which IRQ(s) does 2.4 i82365 use ?

The same ones as yenta, here you have the messages I get with it just in case:

Quoted 10 lines

Linux PCMCIA Card Services 3.2.2
kernel build: 2.4.21 #1 Sat Jun 14 19:43:14 CEST 2003
options: [pci] [cardbus] [apm]
Intel ISA/PCI/CardBus PCIC probe:
PCI: Found IRQ 11 for device 01:09.0
PCI: Sharing IRQ 11 with 00:1d.1
IRQ routing conflict for 01:09.0, have irq 10, want irq 11
O2Micro OZ6912 rev 00 PCI-to-CardBus at slot 01:09, mem 0x10001000
host opts [0]: [pci/way] [pci irq 10] [lat 32/176] [bus 2/5] ISA irqs (default) = 3,4,5,7 PCI status changes

I'm fighting this same O2Micro (HP Pavilion ze4400). I could not get yenta to do squat with it under 2.4 which means a lot of fudging configs around to even try to get it working on 2.6. i82365 works on 2.4 (with IRQ routing complaints) but refuses to acknowlege it's existance on 2.6. Could you post or send me your PCIC=yenta config file? (Debian /etc/default/pcmcia. I don't know where on other distros.)

TIA,
mwa

Signature · 2 lines
Mark W. Alexander
[email protected]
#4 lore raw
Quoted 2 lines

existance on 2.6. Could you post or send me your PCIC=yenta config file? (Debian /etc/default/pcmcia. I don't know where on other distros.)

I'm running Debian unstable here but I do not have anything special on that file, just the defaults changing the driver into yenta_socket, and even this is not necesary if you happen to have just yenta compiled.

# Defaults for pcmcia (sourced by /etc/init.d/pcmcia) PCMCIA=yes
PCIC=yenta_socket
PCIC_OPTS=
CORE_OPTS=
CARDMGR_OPTS=

Regards...

Signature · 1 line
Manty/BestiaTester -> http://manty.net
#5 lore raw
Quoted 7 lines · Santiago Garcia Mantinan
Quoted 2 lines

existance on 2.6. Could you post or send me your PCIC=yenta config file? (Debian /etc/default/pcmcia. I don't know where on other distros.)

I'm running Debian unstable here but I do not have anything special on that file, just the defaults changing the driver into yenta_socket, and even this is not necesary if you happen to have just yenta compiled.

Quoted 6 lines

# Defaults for pcmcia (sourced by /etc/init.d/pcmcia) PCMCIA=yes
PCIC=yenta_socket
PCIC_OPTS=
CORE_OPTS=
CARDMGR_OPTS=

Crap, I was afraid of that. That means my problem is probably BIOS related.

Just in case, would you mind sending me your 2.4 config off-list?

Thanks,
mwa

Signature · 2 lines
Mark W. Alexander
[email protected]
#6 lore raw
In reply to Santiago Garcia Mantinan

At Mon, 11 Aug 2003 12:22:36 +0200,

Quoted 9 lines · Santiago Garcia Mantinan

The ALSA problem is new, ALSA for 2.4 (0.9.4) is working perfectly, but the 2.6.0 driver doesn't allow me to hear the beeper sound, the pcm sounds seem ok, but no matter what I do with the mixer, ALSA doesn't seem to drive the beeper sound to the speakers. The card driver is the snd_intel8x0 with its associated snd_ac97_codec, alsamixer says this about it:
Card: Intel 82801CA-ICH3
Chip: Cirrus Logic CS4299 rev 4
And this is what lspci says:

perhaps CONFIG_INPUT_PCSPKR is set off?

Signature · 2 lines
Takashi Iwai <[email protected]>		SuSE Linux AG - www.suse.de
ALSA Developer				ALSA Project - www.alsa-project.org
#7 lore raw
Quoted 3 lines
Quoted 2 lines

The ALSA problem is new, ALSA for 2.4 (0.9.4) is working perfectly, but the 2.6.0 driver doesn't allow me to hear the beeper sound, the pcm sounds seem

perhaps CONFIG_INPUT_PCSPKR is set off?

Yes, sorry about this one, I didn't knew this option, which is also quite hidden under INPUT_MISC, and also I thought the beeper was an output device, not input :-??? Anyway, it was that and after activating it, it works ok.

Thanks!

Signature · 1 line
Manty/BestiaTester -> http://manty.net