Gentoo Logo
Gentoo Spaceship




Note: Due to technical difficulties, the Archives are currently not up to date. GMANE provides an alternative service for most mailing lists.
c.f. bug 424647
List Archive: gentoo-laptop
Navigation:
Lists: gentoo-laptop: < Prev By Thread Next > < Prev By Date Next >
Headers:
To: gentoo-laptop@g.o
From: Ian K <omega_2_1@...>
Subject: Re: Panasonic Toughbook of Doom
Date: Mon, 06 Jun 2005 23:25:17 +0000
Ian K wrote:

>Jordi Molina wrote:
>
>  
>
>>Hi!
>>
>>On 6/1/05, Ian K <omega_2_1@...> wrote:
>> 
>>
>>    
>>
>>>Jordi Molina wrote:
>>>
>>>   
>>>
>>>      
>>>
>>>>Hi,
>>>>
>>>>On 5/24/05, Ian K <omega_2_1@...> wrote:
>>>>
>>>>
>>>>     
>>>>
>>>>        
>>>>
>>>>>Hi guys at gentoo laptop.
>>>>>I sent this to the general mailing list but got little response.
>>>>>Can you guys help?
>>>>>Thanks!
>>>>>
>>>>>
>>>>>
>>>>>       
>>>>>
>>>>>          
>>>>>
>>>>>>Hi there,
>>>>>>
>>>>>>
>>>>>>         
>>>>>>
>>>>>>            
>>>>>>
>>>>>>>>I have recently set up Gentoo on my friend's laptop,
>>>>>>>>a Panasonic toughbook cf-37. I am currently having difficulty
>>>>>>>>with sound use, but more importantly, his PCMCIA slot(?).
>>>>>>>>When I put his wireless card (which he needs working) into
>>>>>>>>the laptop, and do a dmesg, the following is appended:
>>>>>>>>
>>>>>>>>
>>>>>>>>
>>>>>>>>             
>>>>>>>>
>>>>>>>>                
>>>>>>>>
>>>>Can you send also the output of lspci and of lsmod?
>>>>
>>>>
>>>>     
>>>>
>>>>        
>>>>
>>>I dont have lspci on the computer, but I do have LSHW:
>>>
>>>(Because of lengthy typing, I will post what I believe is relevant, as well
>>>as the categories of everything else.)
>>>
>>>*-cpu
>>>*-cache:0
>>>*-cache:1
>>>*-memory:0
>>>*-memory:1
>>>*-memory:2
>>>*-memory:3
>>>*-memory:4
>>>*-pci
>>>*-multimedia
>>>*-display
>>>*-pcmcia
>>>         description: CardBus Bridge
>>>         product: RL5c475
>>>         vendor: Ricoh Co Ltd
>>>         physical id: 3
>>>         bus info: pci@00:03.0
>>>         version: 80
>>>         clock: 33MHz
>>>         capabilities: pcmcia bus_master cap_list
>>>         configuration: driver=yenta_cardbus
>>>         resources: Very long, I will provide upon request.
>>>*-isa
>>>         description: ISA bridge
>>>         product: 82440MX ISA Bridge
>>>         vendor: Intel corp.
>>>         physical id: 7
>>>         bus info: pci@00:07.0
>>>         version: 01
>>>         clock: 33MHz
>>>         capabilities: isa bus_master
>>>*-ide
>>>         description: IDE interface
>>>         product: 82440MX EIDE Controller
>>>         vendor: Intel Corp.
>>>         physical id: 7.1
>>>         bus info: pci@00:07.1
>>>         version: 00
>>>         clock: 33MHz
>>>         capabilities: ide bus_master
>>>         configuration: driver=uhci_hcd
>>>         resources: ioport:fcc0-fcdfr irq:10
>>>*-bridge
>>>         description: Bridge
>>>         product: 8240MX Power Management Controller
>>>         vendor: Intel Corp.
>>>         physical id: 7.3
>>>         bus info: pci@00:07.3
>>>         version: 00
>>>         clock: 33 MHz
>>>
>>>lsmod shows no modules loaded (at startup)
>>>
>>>   
>>>
>>>      
>>>
>>>>It would be great to have also a filtered output of dmesg for Cardbus
>>>>and/or pcmcia.
>>>>Do it before you plug the card so we can see if the PCMCIA is set up properly.
>>>>
>>>>
>>>>     
>>>>
>>>>        
>>>>
>>># dmesg | grep -i "pcmcia"
>>>Databook TCIT-2 PCMCIA probe: not found.
>>>
>>># dmesg | grep -i "cardbus"
>>>Options: [pci] [cardbus] [pm]
>>>Yenta: CardBus bridge found at 0000:00:03.0 [10f7:832f]
>>>
>>>Also, at bootup, I saw this:
>>>* PCMCIA support detected.
>>>* Starting pcmcia...
>>>cardmgr[5386]: watching 1 socket
>>>cardmgr[5386]: starting, version is
>>>3.2.5                                                     [ ok ]
>>>
>>>   
>>>
>>>      
>>>
>>>>     
>>>>
>>>>        
>>>>
>>>>>>>>cs: IO port probe 0xc00-0xcff: clean
>>>>>>>>cs: IO port probe 0x800-0x8ff: clean
>>>>>>>>cs: IO port probe 0x100-0x4ff: clean
>>>>>>>>cs: IO port probe 0xa00-0xaff: clean
>>>>>>>>cs: pcmcia_socket0: unable to apply power.
>>>>>>>>
>>>>>>>>
>>>>>>>>             
>>>>>>>>
>>>>>>>>                
>>>>>>>>
>>>>from what I understand here, the powemanagement thing is not working
>>>   
>>>
>>>      
>>>
>>>>properly on the device.
>>>>
>>>>
>>>>
>>>>     
>>>>
>>>>        
>>>>
>>>>>>>>irq 9: nobody cared!
>>>>>>>>[<c013d88a>] __report_bad_irq+0x2a/0xa0
>>>>>>>>[<c012d200>] handle_IRQ_event+0x30/0x70
>>>>>>>>[<c013d990>] note_interrupt+0x70/0xb0
>>>>>>>>[<c013d367>] __do_IRQ+0x127/0x130
>>>>>>>>[<c0105772>] do_IRQ+0x52/0x80
>>>>>>>>=================
>>>>>>>>[<c0103c1e>] common_interrupt+0x1a/0x20
>>>>>>>>[<c012007b>] do_exit+0xcb/0x380
>>>>>>>>[<c0122836>] __do_softirq+0x46/0xd0
>>>>>>>>[<c01058a9>] do_softirq+0x69/0x70
>>>>>>>>=================
>>>>>>>>[<c012299b>] irq_exit+0x3b/0x40
>>>>>>>>[<c0105779>] do_IRQ+0x59/0x80
>>>>>>>>[<c0103c1e>] common_interrupt+0x1a/0x20
>>>>>>>>[<c02ee68d>] acpi_processor_idle+0x126/0x262
>>>>>>>>[<c01010ff>] cpu_idle+0x5f/0x70
>>>>>>>>[<c05e1988>] start_kernel+0x158/0x180
>>>>>>>>[<c05e1390>] unknown_bootoption+0x0/0x1e0
>>>>>>>>handlers:
>>>>>>>>[<c02d2b10>] (acpi_irq+0x0/0x16)
>>>>>>>>[<c03960f0>] (yenta_interrupt+0x0/0x40)
>>>>>>>>[<c03fd230>] (snd_intel8x0_interrupt+0x0/0x220)
>>>>>>>>Disabling IRQ #9
>>>>>>>>
>>>>>>>>So thats the output. What does it mean? Am I on the right track?
>>>>>>>>
>>>>>>>>
>>>>>>>>             
>>>>>>>>
>>>>>>>>                
>>>>>>>>
>>>>Im sorry to say that maybe... not.
>>>>
>>>>
>>>>
>>>>     
>>>>
>>>>        
>>>>
>>>>>>>>If so, does anyone know if his wireless card works under Linux?
>>>>>>>>Its a D-Link Airplus DWL-650+
>>>>>>>>
>>>>>>>>
>>>>>>>>             
>>>>>>>>
>>>>>>>>                
>>>>>>>>
>>>>Not really, but you can have a look at the opensource driver project
>>>>for this card:
>>>>http://acx100.sourceforge.net/
>>>>
>>>>I recommend you downloading the tarball with the source and then
>>>>reading the entire documentation.
>>>>
>>>>
>>>>
>>>>     
>>>>
>>>>        
>>>>
>>>>>>>>Thanks!
>>>>>>>>
>>>>>>>>
>>>>>>>>             
>>>>>>>>
>>>>>>>>                
>>>>>>>>
>>>>No prob!
>>>>
>>>>
>>>>
>>>>     
>>>>
>>>>        
>>>>
>>>>>       
>>>>>
>>>>>          
>>>>>
>>>>     
>>>>
>>>>        
>>>>
>>>So what do you think?
>>>Thanks very much!
>>>Ian
>>>
>>>
>>>
>>>
>>>   
>>>
>>>      
>>>
>>Cool, you've the same PCMCIA than me (I owe an Acer TM370, just for info).
>>
>>I had tons of problems for making it work, since, one day, it just
>>worked. Anyway, in your case it seems to be detected...
>>
>>Did you check the webpage i sent on the previous mail with the project
>>of the driver?
>>
>>
>>cheers
>>
>> 
>>
>>    
>>
>Hey.
>So does that mean based on the output that after I compile these
>drivers, it will work?
>And I probably will need some help with that.... (Not good at hardware
>tweakage.)
>
>Thanks again though!
>Ian
>  
>
Hi again,
Perhaps I didn't send it right but I haven't gotten a reply to this thread
in a very long time (which seems strange). I have been messing around with
my client and maybe something got turned around, but if you have replied
past this, do you mind sending the reply to me again?

Basically, I am having an issue with the driver once downloaded.

I did install those drivers (/configure // make).
I am now actually following the instructional guide
here:


Here is the problem: (Quoth the guide:)
Identifying Your Device
 You must first determine that you have a device that
contains a chipset that is compatible with the
acx100/111 driver and this guide. Understand that due
to continuing unfortunate and ill-advised model naming
by some device manufacturers, there is a lot of
confusion about this issue, please verify your chipset
as instructed, and do not trust the model number on
your device. Chipsets internal to these devices have
and will change unannounced, you must verify before
continuing in order to save yourself the headache of
trying to use the wrong driver with your device.
Having said that, it's time to identify your device.
To do that you'll need to run lspci -n with your PCI
card installed and/or your CardBus card plugged in.
Successful output looks similar to this: 

# lspci -n
00:00.0 Class 0600: 8086:7192 (rev 02)
00:02.0 Class 0607: 104c:ac16 (rev 02)
00:02.1 Class 0607: 104c:ac16 (rev 02)
00:03.0 Class 0300: 10c8:0004 (rev 01)
00:07.0 Class 0680: 8086:7110 (rev 01)
00:07.1 Class 0101: 8086:7111 (rev 01)
00:07.2 Class 0c03: 8086:7112 (rev 01)
00:07.3 Class 0680: 8086:7113 (rev 01)
05:00.0 Class 0280: 104c:8400

 That listing is taken from running lspci -n on my
ThinkPad 600 with my SMC 2435w CardBus card plugged
in. Out of those 9 lines listed, we're only interested
in that last one: 

05:00.0 Class 0280: 104c:8400

because it contains one of the 3 combinations listed
below at it's end:
104c:8400 (acx100 CardBus)
104c:8401 (acx100 PCI)
104c:9066 (acx111 Cardbus/PCI)

-----------------------------------------------------

Heres the thing, nothing in those combinations is
listed when I do lspci -n.
Here is my list:

Class 0600: 8086:7194 (rev 01)
Class 0401: 8086:7195
Class 0300: 126f:0710 (rev a3)
Class 0607: 1180:0475 (rev 80)
Class 0601: 8086:7198 (rev 01)
Class 0101: 8086:7199
Class 0c03: 8086:719a
Class 0680: 8086:719b
Class 0780: 10b7:1006

Im misunderstanding something,
like, the website said that the DWL-650+
will work with this driver. Why is this
not working???

Thanks for all of the help.
Ian



Attachment:
omega_2_1.vcf (Vcard)
Replies:
Re: Panasonic Toughbook of Doom
-- Jordi Molina
References:
Panasonic Toughbook of Doom
-- Ian K
Re: Panasonic Toughbook of Doom
-- Jordi Molina
Re: Panasonic Toughbook of Doom
-- Ian K
Re: Panasonic Toughbook of Doom
-- Jordi Molina
Re: Panasonic Toughbook of Doom
-- Ian K
Navigation:
Lists: gentoo-laptop: < Prev By Thread Next > < Prev By Date Next >
Previous by thread:
Re: Panasonic Toughbook of Doom
Next by thread:
Re: Panasonic Toughbook of Doom
Previous by date:
Just a test message
Next by date:
Re: Panasonic Toughbook of Doom


Updated Jun 17, 2009

Summary: Archive of the gentoo-laptop mailing list.

Donate to support our development efforts.

Copyright 2001-2013 Gentoo Foundation, Inc. Questions, Comments? Contact us.