cardmgr & pcmcia_cs problem - Portable
This is a discussion on cardmgr & pcmcia_cs problem - Portable ; hi
i am currently working on BlueZ project in a Mandrake 9.1. My Project is
in initial stage. I am facing big big problems.. i tried my best but i
am now about to surrender. The problem is... i am ...
-
cardmgr & pcmcia_cs problem
hi
i am currently working on BlueZ project in a Mandrake 9.1. My Project is
in initial stage. I am facing big big problems.. i tried my best but i
am now about to surrender. The problem is... i am trying to use BlueZ as
a module, i have a 3COM bluetooth card v2.0 and its driver name is
"bt3c_cs" i have all necessary lines in my modules.conf file. THe
problem is, modules are not loading at startup automatically and "bluez"
is not binding itself automatically with "bt3c_cs"I have to do it
manually each and every time when i restart the machine.
I know that the problem is not bluez module. Its cardmgr because when
pcmcia script starts to bring up
the modules it starts: pcmcia_core, yenta_socket (instead of i82365) and
ds. My bluez modules dont load because cardmgr detect a Serial or Modem.
Because of that cardmgr loads the module serial_cs instead of bt3c_cs.
(And bluez modules load in memory when modprobe detect that bt3c_cs need
them)
Someone knows why cardmgr doesnt detect my 3COM card? I have changed
/etc/pcmcia/config with:
device "bt3c_cs" module "bt3c_cs"
card "3Com Bluetooth PC Card" version "3COM","*","Bluetooth PC Card"
bind "bt3c_cs"
And this is the my system information:
[root@ip-27-195 pcmcia]# uname -ra
Linux ip-27-195.dyn.lut.fi 2.4.21-0.13mdk #1 Fri Mar 14 15:08:06 EST
2003 i686
unknown unknown GNU/Linux
[root@ip-27-195 pcmcia]# lsmod
Module Size Used by Not tainted
serial_cs 6000 0 (unused)
ds 8456 1 [serial_cs]
yenta_socket 13056 1
pcmcia_core 57184 0 [serial_cs ds yenta_socket]
usbmouse 2936 0 (unused)
keybdev 2720 0 (unused)
mousedev 5268 1
hid 20900 0 (unused)
input 5664 0 [usbmouse keybdev mousedev hid]
usb-uhci 24652 0 (unused)
usbcore 72992 1 [usbmouse hid usb-uhci]
binfmt_misc 7020 1
parport_pc 25096 1 (autoclean)
lp 8096 0 (autoclean)
parport 34176 1 (autoclean) [parport_pc lp]
snd-seq-oss 31104 0 (unused)
snd-seq-midi-event 5640 0 [snd-seq-oss]
snd-seq 42608 2 [snd-seq-oss snd-seq-midi-event]
snd-seq-device 5832 0 [snd-seq-oss snd-seq]
snd-pcm-oss 43556 1
snd-mixer-oss 14488 0 [snd-pcm-oss]
snd-ali5451 14412 3
snd-pcm 77536 0 [snd-pcm-oss snd-ali5451]
snd-timer 18376 0 [snd-seq snd-pcm]
snd-page-alloc 7732 0 [snd-pcm]
snd-ac97-codec 40160 0 [snd-ali5451]
snd 40868 2 [snd-seq-oss snd-seq-midi-event snd-seq
snd-seq-device snd-pcm-oss snd-mixer-oss snd-ali5451 snd-pcm snd-timer
snd-ac97-codec]
soundcore 6276 0 [snd]
nfsd 74256 8 (autoclean)
af_packet 14952 1 (autoclean)
sr_mod 16920 0 (autoclean)
floppy 55132 0
button 3724 0 (unused)
thermal 8224 0 (unused)
processor 10872 0 [thermal]
fan 2528 0 (unused)
ac 2784 0 (unused)
battery 7008 0 (unused)
natsemi 18752 1 (autoclean)
ntfs 76812 1 (autoclean)
nls_iso8859-1 3516 2 (autoclean)
nls_cp850 4316 1 (autoclean)
vfat 11820 1 (autoclean)
fat 37944 0 (autoclean) [vfat]
supermount 15296 2 (autoclean)
ide-cd 33856 0
cdrom 31648 0 [sr_mod ide-cd]
ide-scsi 11280 0
scsi_mod 103284 2 [sr_mod ide-scsi]
rtc 8060 0 (autoclean)
ext3 59916 2
jbd 38972 2 [ext3]
Oct 23 11:23:12 ip-27-195 kernel: Linux Kernel Card Services Kernel Version
Oct 23 11:23:12 ip-27-195 kernel: options: [pci] [cardbus] [pm]
Oct 23 11:23:12 ip-27-195 kernel: Yenta IRQ list 0098, PCI irq11
Oct 23 11:23:12 ip-27-195 kernel: Socket status: 30000419
Oct 23 11:23:13 ip-27-195 cardmgr[5638]: watching 1 sockets
Oct 23 11:23:13 ip-27-195 kernel: cs: IO port probe 0x0c00-0x0cff: clean.
Oct 23 11:23:13 ip-27-195 kernel: cs: IO port probe 0x0100-0x04ff: excluding
0x200-0x207 0x220-0x22f 0x330-0x337 0x388-0x38f 0x408-0x40f 0x480-0x48f
0x4d0-0x4d7
Oct 23 11:23:13 ip-27-195 kernel: cs: IO port probe 0x0a00-0x0aff: clean.
Oct 23 11:23:13 ip-27-195 cardmgr[5639]: starting, version is 3.2.3
Oct 23 11:23:13 ip-27-195 kernel: cs: memory probe
0xa0000000-0xa0ffffff: clean.
Oct 23 11:23:13 ip-27-195 cardmgr[5639]: socket 0: Serial or Modem
Oct 23 11:23:13 ip-27-195 cardmgr[5639]: executing: 'modprobe serial_cs'
Oct 23 11:23:13 ip-27-195 cardmgr[5639]: executing: './serial start ttyS0'
Oct 23 11:23:13 ip-27-195 kernel: ttyS00 at port 0x03f8 (irq = 3) is a 8250
Oct 23 11:35:33 ip-27-195 kernel: i8253 count too high! resetting..
[root@ip-27-195 sysconfig]# cat pcmcia
PCMCIA=yes
PCIC=yenta_socket
[root@ip-27-195 sysconfig]# cat pcmcia.rpmnew
PCMCIA=yes
PCIC=yenta_socket
PCIC_OPTS=do_scan=0
CORE_OPTS=
CARDMGR_OPTS=-f
Thanks for your help.
Inaki
-
Re: cardmgr & pcmcia_cs problem
inaki wrote:
> i am currently working on BlueZ project in a Mandrake 9.1. My Project is
> in initial stage. I am facing big big problems.. i tried my best but i
> am now about to surrender. The problem is... i am trying to use BlueZ as
> a module, i have a 3COM bluetooth card v2.0 and its driver name is
> "bt3c_cs" i have all necessary lines in my modules.conf file. THe
> problem is, modules are not loading at startup automatically and "bluez"
> is not binding itself automatically with "bt3c_cs"I have to do it
> manually each and every time when i restart the machine.
I haven't really understood your problem,
and also am not an expert,
but what does "cardctl ident" say?
--
Timothy Murphy
e-mail (<80k only): tim /at/ birdsnest.maths.tcd.ie
tel: +353-86-2336090, +353-1-2842366
s-mail: School of Mathematics, Trinity College, Dublin 2, Ireland
-
Re: cardmgr & pcmcia_cs problem
My problem its that cardmgr loads a wrong module to manage my 3Com
Bluetooth card. It must be bt3c_cs and its loads serial_cs because it
thinks my pcmcia card is a Serial or Modem.
when i type /etc/init.d/pcmcia start i can read in /var/log/messages
this:
Oct 23 11:23:12 ip-27-195 kernel: Linux Kernel Card Services Kernel Version
Oct 23 11:23:12 ip-27-195 kernel: options: [pci] [cardbus] [pm]
Oct 23 11:23:12 ip-27-195 kernel: Yenta IRQ list 0098, PCI irq11
Oct 23 11:23:12 ip-27-195 kernel: Socket status: 30000419
Oct 23 11:23:13 ip-27-195 cardmgr[5638]: watching 1 sockets
Oct 23 11:23:13 ip-27-195 kernel: cs: IO port probe 0x0c00-0x0cff: clean.
Oct 23 11:23:13 ip-27-195 kernel: cs: IO port probe 0x0100-0x04ff: excluding
0x200-0x207 0x220-0x22f 0x330-0x337 0x388-0x38f 0x408-0x40f 0x480-0x48f
0x4d0-0x4d7
Oct 23 11:23:13 ip-27-195 kernel: cs: IO port probe 0x0a00-0x0aff: clean.
Oct 23 11:23:13 ip-27-195 cardmgr[5639]: starting, version is 3.2.3
Oct 23 11:23:13 ip-27-195 kernel: cs: memory probe
0xa0000000-0xa0ffffff: clean.
Oct 23 11:23:13 ip-27-195 cardmgr[5639]: socket 0: Serial or Modem
Oct 23 11:23:13 ip-27-195 cardmgr[5639]: executing: 'modprobe serial_cs'
Oct 23 11:23:13 ip-27-195 cardmgr[5639]: executing: './serial start ttyS0'
Oct 23 11:23:13 ip-27-195 kernel: ttyS00 at port 0x03f8 (irq = 3) is a 8250
Oct 23 11:35:33 ip-27-195 kernel: i8253 count too high! resetting..
Instead of "3COM Bluetooth" and modprobe bt3c_cs
When i type "cardctl ident", i have:
Socket 0:
product info:"3COM","?"
manfid: 0x0101,0x0040
function: 2 (serial)
> inaki wrote:
>
>
>>i am currently working on BlueZ project in a Mandrake 9.1. My Project is
>>in initial stage. I am facing big big problems.. i tried my best but i
>>am now about to surrender. The problem is... i am trying to use BlueZ as
>>a module, i have a 3COM bluetooth card v2.0 and its driver name is
>>"bt3c_cs" i have all necessary lines in my modules.conf file. THe
>>problem is, modules are not loading at startup automatically and "bluez"
>>is not binding itself automatically with "bt3c_cs"I have to do it
>>manually each and every time when i restart the machine.
>
>
> I haven't really understood your problem,
> and also am not an expert,
> but what does "cardctl ident" say?
>
-
Re: cardmgr & pcmcia_cs problem
inaki wrote:
> Someone knows why cardmgr doesnt detect my 3COM card? I have changed
> /etc/pcmcia/config with:
> device "bt3c_cs" module "bt3c_cs"
> card "3Com Bluetooth PC Card" version "3COM","*","Bluetooth PC Card"
> bind "bt3c_cs"
In your later post, you say that "cardctl ident" reports:
product info:"3COM","?"
manfid: 0x0101,0x0040
so I would suggest using those manfid codes, rather than the strings
in your config entry, which do not appear to match your card.
-- Dave
-
Re: cardmgr & pcmcia_cs problem
On Thu, 23 Oct 2003 08:48:22 +0000, inaki wrote:
>
> i am currently working on BlueZ project in a Mandrake 9.1. My Project is
> in initial stage. I am facing big big problems
Just one mere suggestion. What happens if you uncomment "exclude IRQ 3" in
/etc/pcmcia/config.opts?
--
Portia
She was not a woman of many words: for, unlike people in general,
she proportioned them to the number of her ideas. --Jane Austen