Gentoo Archives: gentoo-laptop

From: Ian K <omega_2_1@×××××.ca>
To: gentoo-laptop@l.g.o
Subject: Re: [gentoo-laptop] Panasonic Toughbook of Doom
Date: Tue, 07 Jun 2005 05:22:03
Message-Id: 42A4DB5D.8080109@yahoo.ca
In Reply to: Re: [gentoo-laptop] Panasonic Toughbook of Doom by Ian K
1 Ian K wrote:
2
3 >Jordi Molina wrote:
4 >
5 >
6 >
7 >>Hi!
8 >>
9 >>On 6/1/05, Ian K <omega_2_1@×××××.ca> wrote:
10 >>
11 >>
12 >>
13 >>
14 >>>Jordi Molina wrote:
15 >>>
16 >>>
17 >>>
18 >>>
19 >>>
20 >>>>Hi,
21 >>>>
22 >>>>On 5/24/05, Ian K <omega_2_1@×××××.ca> wrote:
23 >>>>
24 >>>>
25 >>>>
26 >>>>
27 >>>>
28 >>>>
29 >>>>>Hi guys at gentoo laptop.
30 >>>>>I sent this to the general mailing list but got little response.
31 >>>>>Can you guys help?
32 >>>>>Thanks!
33 >>>>>
34 >>>>>
35 >>>>>
36 >>>>>
37 >>>>>
38 >>>>>
39 >>>>>
40 >>>>>>Hi there,
41 >>>>>>
42 >>>>>>
43 >>>>>>
44 >>>>>>
45 >>>>>>
46 >>>>>>
47 >>>>>>>>I have recently set up Gentoo on my friend's laptop,
48 >>>>>>>>a Panasonic toughbook cf-37. I am currently having difficulty
49 >>>>>>>>with sound use, but more importantly, his PCMCIA slot(?).
50 >>>>>>>>When I put his wireless card (which he needs working) into
51 >>>>>>>>the laptop, and do a dmesg, the following is appended:
52 >>>>>>>>
53 >>>>>>>>
54 >>>>>>>>
55 >>>>>>>>
56 >>>>>>>>
57 >>>>>>>>
58 >>>>>>>>
59 >>>>Can you send also the output of lspci and of lsmod?
60 >>>>
61 >>>>
62 >>>>
63 >>>>
64 >>>>
65 >>>>
66 >>>I dont have lspci on the computer, but I do have LSHW:
67 >>>
68 >>>(Because of lengthy typing, I will post what I believe is relevant, as well
69 >>>as the categories of everything else.)
70 >>>
71 >>>*-cpu
72 >>>*-cache:0
73 >>>*-cache:1
74 >>>*-memory:0
75 >>>*-memory:1
76 >>>*-memory:2
77 >>>*-memory:3
78 >>>*-memory:4
79 >>>*-pci
80 >>>*-multimedia
81 >>>*-display
82 >>>*-pcmcia
83 >>> description: CardBus Bridge
84 >>> product: RL5c475
85 >>> vendor: Ricoh Co Ltd
86 >>> physical id: 3
87 >>> bus info: pci@00:03.0
88 >>> version: 80
89 >>> clock: 33MHz
90 >>> capabilities: pcmcia bus_master cap_list
91 >>> configuration: driver=yenta_cardbus
92 >>> resources: Very long, I will provide upon request.
93 >>>*-isa
94 >>> description: ISA bridge
95 >>> product: 82440MX ISA Bridge
96 >>> vendor: Intel corp.
97 >>> physical id: 7
98 >>> bus info: pci@00:07.0
99 >>> version: 01
100 >>> clock: 33MHz
101 >>> capabilities: isa bus_master
102 >>>*-ide
103 >>> description: IDE interface
104 >>> product: 82440MX EIDE Controller
105 >>> vendor: Intel Corp.
106 >>> physical id: 7.1
107 >>> bus info: pci@00:07.1
108 >>> version: 00
109 >>> clock: 33MHz
110 >>> capabilities: ide bus_master
111 >>> configuration: driver=uhci_hcd
112 >>> resources: ioport:fcc0-fcdfr irq:10
113 >>>*-bridge
114 >>> description: Bridge
115 >>> product: 8240MX Power Management Controller
116 >>> vendor: Intel Corp.
117 >>> physical id: 7.3
118 >>> bus info: pci@00:07.3
119 >>> version: 00
120 >>> clock: 33 MHz
121 >>>
122 >>>lsmod shows no modules loaded (at startup)
123 >>>
124 >>>
125 >>>
126 >>>
127 >>>
128 >>>>It would be great to have also a filtered output of dmesg for Cardbus
129 >>>>and/or pcmcia.
130 >>>>Do it before you plug the card so we can see if the PCMCIA is set up properly.
131 >>>>
132 >>>>
133 >>>>
134 >>>>
135 >>>>
136 >>>>
137 >>># dmesg | grep -i "pcmcia"
138 >>>Databook TCIT-2 PCMCIA probe: not found.
139 >>>
140 >>># dmesg | grep -i "cardbus"
141 >>>Options: [pci] [cardbus] [pm]
142 >>>Yenta: CardBus bridge found at 0000:00:03.0 [10f7:832f]
143 >>>
144 >>>Also, at bootup, I saw this:
145 >>>* PCMCIA support detected.
146 >>>* Starting pcmcia...
147 >>>cardmgr[5386]: watching 1 socket
148 >>>cardmgr[5386]: starting, version is
149 >>>3.2.5 [ ok ]
150 >>>
151 >>>
152 >>>
153 >>>
154 >>>
155 >>>>
156 >>>>
157 >>>>
158 >>>>
159 >>>>>>>>cs: IO port probe 0xc00-0xcff: clean
160 >>>>>>>>cs: IO port probe 0x800-0x8ff: clean
161 >>>>>>>>cs: IO port probe 0x100-0x4ff: clean
162 >>>>>>>>cs: IO port probe 0xa00-0xaff: clean
163 >>>>>>>>cs: pcmcia_socket0: unable to apply power.
164 >>>>>>>>
165 >>>>>>>>
166 >>>>>>>>
167 >>>>>>>>
168 >>>>>>>>
169 >>>>>>>>
170 >>>>from what I understand here, the powemanagement thing is not working
171 >>>
172 >>>
173 >>>
174 >>>
175 >>>>properly on the device.
176 >>>>
177 >>>>
178 >>>>
179 >>>>
180 >>>>
181 >>>>
182 >>>>
183 >>>>>>>>irq 9: nobody cared!
184 >>>>>>>>[<c013d88a>] __report_bad_irq+0x2a/0xa0
185 >>>>>>>>[<c012d200>] handle_IRQ_event+0x30/0x70
186 >>>>>>>>[<c013d990>] note_interrupt+0x70/0xb0
187 >>>>>>>>[<c013d367>] __do_IRQ+0x127/0x130
188 >>>>>>>>[<c0105772>] do_IRQ+0x52/0x80
189 >>>>>>>>=================
190 >>>>>>>>[<c0103c1e>] common_interrupt+0x1a/0x20
191 >>>>>>>>[<c012007b>] do_exit+0xcb/0x380
192 >>>>>>>>[<c0122836>] __do_softirq+0x46/0xd0
193 >>>>>>>>[<c01058a9>] do_softirq+0x69/0x70
194 >>>>>>>>=================
195 >>>>>>>>[<c012299b>] irq_exit+0x3b/0x40
196 >>>>>>>>[<c0105779>] do_IRQ+0x59/0x80
197 >>>>>>>>[<c0103c1e>] common_interrupt+0x1a/0x20
198 >>>>>>>>[<c02ee68d>] acpi_processor_idle+0x126/0x262
199 >>>>>>>>[<c01010ff>] cpu_idle+0x5f/0x70
200 >>>>>>>>[<c05e1988>] start_kernel+0x158/0x180
201 >>>>>>>>[<c05e1390>] unknown_bootoption+0x0/0x1e0
202 >>>>>>>>handlers:
203 >>>>>>>>[<c02d2b10>] (acpi_irq+0x0/0x16)
204 >>>>>>>>[<c03960f0>] (yenta_interrupt+0x0/0x40)
205 >>>>>>>>[<c03fd230>] (snd_intel8x0_interrupt+0x0/0x220)
206 >>>>>>>>Disabling IRQ #9
207 >>>>>>>>
208 >>>>>>>>So thats the output. What does it mean? Am I on the right track?
209 >>>>>>>>
210 >>>>>>>>
211 >>>>>>>>
212 >>>>>>>>
213 >>>>>>>>
214 >>>>>>>>
215 >>>>Im sorry to say that maybe... not.
216 >>>>
217 >>>>
218 >>>>
219 >>>>
220 >>>>
221 >>>>
222 >>>>
223 >>>>>>>>If so, does anyone know if his wireless card works under Linux?
224 >>>>>>>>Its a D-Link Airplus DWL-650+
225 >>>>>>>>
226 >>>>>>>>
227 >>>>>>>>
228 >>>>>>>>
229 >>>>>>>>
230 >>>>>>>>
231 >>>>Not really, but you can have a look at the opensource driver project
232 >>>>for this card:
233 >>>>http://acx100.sourceforge.net/
234 >>>>
235 >>>>I recommend you downloading the tarball with the source and then
236 >>>>reading the entire documentation.
237 >>>>
238 >>>>
239 >>>>
240 >>>>
241 >>>>
242 >>>>
243 >>>>
244 >>>>>>>>Thanks!
245 >>>>>>>>
246 >>>>>>>>
247 >>>>>>>>
248 >>>>>>>>
249 >>>>>>>>
250 >>>>>>>>
251 >>>>No prob!
252 >>>>
253 >>>>
254 >>>>
255 >>>>
256 >>>>
257 >>>>
258 >>>>
259 >>>>>
260 >>>>>
261 >>>>>
262 >>>>>
263 >>>>
264 >>>>
265 >>>>
266 >>>>
267 >>>So what do you think?
268 >>>Thanks very much!
269 >>>Ian
270 >>>
271 >>>
272 >>>
273 >>>
274 >>>
275 >>>
276 >>>
277 >>>
278 >>Cool, you've the same PCMCIA than me (I owe an Acer TM370, just for info).
279 >>
280 >>I had tons of problems for making it work, since, one day, it just
281 >>worked. Anyway, in your case it seems to be detected...
282 >>
283 >>Did you check the webpage i sent on the previous mail with the project
284 >>of the driver?
285 >>
286 >>
287 >>cheers
288 >>
289 >>
290 >>
291 >>
292 >>
293 >Hey.
294 >So does that mean based on the output that after I compile these
295 >drivers, it will work?
296 >And I probably will need some help with that.... (Not good at hardware
297 >tweakage.)
298 >
299 >Thanks again though!
300 >Ian
301 >
302 >
303 Hi again,
304 Perhaps I didn't send it right but I haven't gotten a reply to this thread
305 in a very long time (which seems strange). I have been messing around with
306 my client and maybe something got turned around, but if you have replied
307 past this, do you mind sending the reply to me again?
308
309 Basically, I am having an issue with the driver once downloaded.
310
311 I did install those drivers (/configure // make).
312 I am now actually following the instructional guide
313 here:
314
315
316 Here is the problem: (Quoth the guide:)
317 Identifying Your Device
318 You must first determine that you have a device that
319 contains a chipset that is compatible with the
320 acx100/111 driver and this guide. Understand that due
321 to continuing unfortunate and ill-advised model naming
322 by some device manufacturers, there is a lot of
323 confusion about this issue, please verify your chipset
324 as instructed, and do not trust the model number on
325 your device. Chipsets internal to these devices have
326 and will change unannounced, you must verify before
327 continuing in order to save yourself the headache of
328 trying to use the wrong driver with your device.
329 Having said that, it's time to identify your device.
330 To do that you'll need to run lspci -n with your PCI
331 card installed and/or your CardBus card plugged in.
332 Successful output looks similar to this:
333
334 # lspci -n
335 00:00.0 Class 0600: 8086:7192 (rev 02)
336 00:02.0 Class 0607: 104c:ac16 (rev 02)
337 00:02.1 Class 0607: 104c:ac16 (rev 02)
338 00:03.0 Class 0300: 10c8:0004 (rev 01)
339 00:07.0 Class 0680: 8086:7110 (rev 01)
340 00:07.1 Class 0101: 8086:7111 (rev 01)
341 00:07.2 Class 0c03: 8086:7112 (rev 01)
342 00:07.3 Class 0680: 8086:7113 (rev 01)
343 05:00.0 Class 0280: 104c:8400
344
345 That listing is taken from running lspci -n on my
346 ThinkPad 600 with my SMC 2435w CardBus card plugged
347 in. Out of those 9 lines listed, we're only interested
348 in that last one:
349
350 05:00.0 Class 0280: 104c:8400
351
352 because it contains one of the 3 combinations listed
353 below at it's end:
354 104c:8400 (acx100 CardBus)
355 104c:8401 (acx100 PCI)
356 104c:9066 (acx111 Cardbus/PCI)
357
358 -----------------------------------------------------
359
360 Heres the thing, nothing in those combinations is
361 listed when I do lspci -n.
362 Here is my list:
363
364 Class 0600: 8086:7194 (rev 01)
365 Class 0401: 8086:7195
366 Class 0300: 126f:0710 (rev a3)
367 Class 0607: 1180:0475 (rev 80)
368 Class 0601: 8086:7198 (rev 01)
369 Class 0101: 8086:7199
370 Class 0c03: 8086:719a
371 Class 0680: 8086:719b
372 Class 0780: 10b7:1006
373
374 Im misunderstanding something,
375 like, the website said that the DWL-650+
376 will work with this driver. Why is this
377 not working???
378
379 Thanks for all of the help.
380 Ian

Attachments

File name MIME type
omega_2_1.vcf text/x-vcard

Replies

Subject Author
Re: [gentoo-laptop] Panasonic Toughbook of Doom Jordi Molina <warp3r@×××××.com>