Well, i have a wpi card too, and have similar problem. Is there any update
about this?

Regards,







Pierre Pronchery wrote:
> 
> 	Hi,
> 
> Having a T60 too,
> 
> NetBSD syn 4.0_BETA2 NetBSD 4.0_BETA2 (GENERIC.MPACPI) #2: Fri Jan  5
> 05:15:48 CET 2007
> khorben@syn:/usr/obj/sys/arch/i386/compile/GENERIC.MPACPI i386
> 
> Holger Weiss wrote:
>> If I try to use an Orinoco 11b PCMCIA card instead, I run into the
>> problem described in kern/32328 (while ex(4) at cardbus(4) works fine).
>> Using RBUS_IO_BASE=0xa00 and RBUS_IO_SIZE=0x0ff as suggested by Michael
>> in the most recent comment to the PR doesn't fix the problem for me.
> 
> I have the same problem, and initially thought the card was at fault, so
> I did not try the fix yet.
> 
>>> "X -configure;<mv config file in place>;xinit" works, but on exiting
>>> the text consoles are messed up (large font, only part of the screen
>>> is showing).
>> 
>> I haven't seen this problem, my text consoles are fine after exiting X.
>> Using the ATI driver, switching to a text console using 'Ctrl-Alt-F<n>'
>> won't work, though.  The system simply switches back to the VT running X
>> after a second or two.  Using VESA, switching back and forth between the
>> text consoles and X works fine.
> 
> I am using the vesa driver with xorg from pkgsrc (I don't think it's
> possible to get the fglrx driver to work with xorg). When I switch back
> to text console:
> - without framebuffer I get two cursors (one blinking _ and staying at
> top left and the regular block)
> - with framebuffer (vesafb) I apparently lose the cursor
> 
>>> I disabled the trackpad in the bios and the trackpoint and 3 buttons
>>> work fine.
> 
> In my bios I have both enabled, and while the touchpad always works the
> trackpoint most of the time does not.
> 
>>> The big problem is wm0.
> 
> I have to force it to 100BaseTX, otherwise works fine.
> 
>>> The cbb0 errors below are mysterious.
> 
> Here I get:
> ppb5 at pci0 dev 30 function 0: Intel 82801BAM Hub-PCI Bridge (rev. 0xe2)
> pci6 at ppb5 bus 21
> pci6: i/o space enabled
> cbb0 at pci6 dev 0 function 0: Texas Instruments PCI1510 PCI-CardBus
> Bridge (rev. 0x00)
> cbb0: can't map socket base address 0xe4300000
> pci_io_find: expected type i/o, found mem
> cbb0: can't map socket base address 0xc1c5bb80: io mode
> cbb0: interrupting at ioapic0 pin 16 (irq 11)
> cardslot0 at cbb0 slot 0 flags 0
> cardbus0 at cardslot0: bus 22
> pcmcia0 at cardslot0
> 
>>> I haven't played with audio, bluetooth
>> 
>> azalia(4) seems to work fine for me.  Switching on bluetooth gives me:
> 
> I need this in mixerctl.conf for the volume to scale properly:
> outputs.lineout=255
> outputs.lineout.source=dac03
> 
>> | ubt0 at uhub3 port 1 configuration 1 interface 0
>> | ubt0: Broadcom Corp BCM2045B, rev 2.00/1.00, addr 3
>> 
>> However, I haven't tried actually using it.
> 
> I never tried bluetooth either.
> 
>> wpi(4) behaves mysteriously.  I downloaded and installed the firmware
>> file as documented in the man page.  Now, if I (re)boot NetBSD a few
>> times, I get two different results: wpi(4) sometimes works and sometimes
>> doesn't.  In both cases, wpi0 is detected correctly.  Then,
> 
> The behaviour of wpi is totally different here:
> - the firmware always loads correctly;
> - the firmware crashes every time I send a command via ifconfig;
> - the firmware randomly crashes during operation
> - the more networks/users the more it crashes (I could not determine if
> any particular packet triggered that, it seems more like a timing issue)
> - monitor mode works (with kismet) if I keep ifup'ing the interface
> 
> I was in contact for a while with Jean-Baptiste Campesato to try to fix
> this, compared the code to the Linux driver, but to no success. I still
> have to try to boot OpenBSD to see if it's better with the original
> driver.
> 
>> I haven't played with SpeedStep or ACPI stuff so far.  My kernel and X
>> configuration as well as my dmesg(s) are at:
>> 
>> 	ftp://ftp.in-berlin.de/pub/users/weiss/netbsd/t60/
> 
> If you actually are in Berlin, we could probably gather up some time and
> see if we can fix some stuff.
> 
> HTH,
> -- 
> khorben
> 
> 
> 

-- 
View this message in context: http://www.nabble.com/Thinkpad-T60-mostly-works---trouble-with-wm%284%29-tf2149197.html#a12919560
Sent from the port-i386 mailing list archive at Nabble.com.