Skip site navigation (1)Skip section navigation (2)
Date:      Fri, 09 Nov 2007 00:39:59 +0900
From:      Watanabe Kazuhiro <CQG00620@nifty.ne.jp>
To:        freebsd-mobile <freebsd-mobile@freebsd.org>
Subject:   Re: PCMCIA RS232 card
Message-ID:  <20071108153959.8FFAD12308@mail.asahi-net.or.jp>
In-Reply-To: <200711081008.11798.root@solink.ru>
References:  <200711081008.11798.root@solink.ru>

next in thread | previous in thread | raw e-mail | index | archive | help
At Thu, 8 Nov 2007 10:08:11 +0600,
Bachilo Dmitry wrote:
> > > I wonder if there can something be done to make the subject work.
> > > When I plug it in it says:
> > > cardbus0: <simple comms, UART> at device 0.0 (no driver attached)
> > > As far as I know, FreeBSD supports this type of cards (with puc drive=
r?),
> > > but I've tried hard and got nowhere. It is an "STlab RS232 Serial
> > > adapter". What additional information from me is required?
> >
> > Does your kernel includes the puc(4) driver? e.g.:
> > | % kldstat -v | grep puc
> > |                 71 pci/puc
> > |                 72 cardbus/puc
> > |                 76 puc/sio
> > |                 164 puc/ppc
> > | %
>=20
> I have this:
>=20
> %kldstat -v | grep puc
>  6    1 0xc3a9e000 7000     puc.ko
>                 423 cardbus/puc
>                 424 pci/puc
>                 425 pccard/puc
> %
>=20
> I've no SIO, what that's supposed to mean? No com-port support even if ca=
rd is=20
> recognized?

You load the puc(4) driver as a kernel module, and the sio(4) driver
is *not* loaded as a kernel module, is it?

If so, there are two choices that you can make.

(1) If you want to load the puc(4) driver as a kernel module, you
    should load the sio(4) driver module as well.  By default the
    sio(4) driver is kernel builtin.  So you should remove "device
    sio" from your kernel configulation file and rebuild/install the
    kernel.  Then you should add the following lines to
    /boot/loader.conf:

    sio_load=3D"YES"
    puc_load=3D"YES"

(2) If you don't want to load the puc(4) driver as a kernel module,
    you should add "device puc" to your kernel configulation file and
    rebuild/install the kernel.

See my another post:
http://lists.freebsd.org/pipermail/freebsd-questions/2007-November/162080.h=
tml


> > By default the driver is not included in the GENERIC kernel.
>=20
> I know that, I've tried to kldload it and to compile it in - all the same.

Hmm.. Did your kernel have the sio(4) driver? e.g.:

| % kldstat -v | grep sio
|                 74 pci/sio
|                 75 cardbus/sio
|                 76 puc/sio
|                 165 isa/sio
|                 166 acpi/sio
| %=20


> > If you load the puc(4) driver as a kernel module (puc.ko), would you
> > try to include the driver into the kernel instead of loading the
> > kernel module?
>=20
> see below. It does not recognize the card in both cases.
>=20
> > And will you show me the output of "pciconf -lv"?
>=20
> When I was on 7.0-PRE, I was able to see a normal output, but now somethi=
ng=20
> strange comes out, look:
>=20
> %pciconf -lv
> none0@pci0:0:0: class=3D0x060000 card=3D0x009f1025 chip=3D0x59501002 rev=
=3D0x10=20
> hdr=3D0x00
>     vendor     =3D 'ATI Technologies Inc.'
>     device     =3D 'RS480 Host Bridge'
>     class      =3D bridge
>     subclass   =3D HOST-PCI
> -1013113760@pci0:0:0:   class=3D0x02103f card=3D0x01000100 chip=3D0x009f1=
025=20
> rev=3D0x5a hdr=3D0x00
>     vendor     =3D 'Acer Incorporated'
>     class      =3D network
> 6Z86032452@pci0:0:0:    class=3D0x021050 card=3D0x00000000 chip=3D0x01000=
400=20
> rev=3D0x59 hdr=3D0x00
>     class      =3D network
> PY7Z0@pci96:28:157:     class=3D0x000500 card=3D0x00000000 chip=3D0x00000=
000=20
> rev=3D0x01 hdr=3D0xc3
>     class      =3D old
> none1@pci68:192:32:     class=3D0x000000 card=3D0xc39d1c60 chip=3D0x00000=
000=20
> rev=3D0x00 hdr=3D0x05
>     class      =3D old
>     subclass   =3D non-VGA display device
> none2@pci0:0:0: class=3D0x000000 card=3D0x0520c044 chip=3D0xc39d1c60 rev=
=3D0x00=20
> hdr=3D0x00
>     class      =3D old
>     subclass   =3D non-VGA display device
> none3@pci0:0:0: class=3D0x601c9d card=3D0x00000000 chip=3D0x0520c044 rev=
=3D0xc3=20
> hdr=3D0x00
> `=9D=81=C31131548674@pci0:192:221:     class=3D0x44c020 card=3D0x00000000=
 chip=3D0x00000000=20
> rev=3D0x05 hdr=3D0xc2
> D=81=C0 `=9D=81=C310424357@pci12:5:0:       class=3D0x000000 card=3D0xc2d=
dc000 chip=3D0x00000000=20
> rev=3D0x00 hdr=3D0x83
>     class      =3D old
>     subclass   =3D non-VGA display device
> none4@pci2:16:118:      class=3D0x000000 card=3D0x80820101 chip=3D0xc2ddc=
000=20
> rev=3D0x00 hdr=3D0x43
>     class      =3D old
>     subclass   =3D non-VGA display device
> none5@pci37:16:159:     class=3D0x00c0dd card=3D0x437b1002 chip=3D0x01000=
304=20
> rev=3D0xc2 hdr=3D0x00
>     class      =3D old
> none6@pci0:20:3:        class=3D0x060100 card=3D0x009f1025 chip=3D0x43771=
002=20
> rev=3D0x80 hdr=3D0x00
>     vendor     =3D 'ATI Technologies Inc.'
>     device     =3D 'IXP SB400 PCI-ISA Bridge'
>     class      =3D bridge
>     subclass   =3D PCI-ISA
> =80-1013113760@pci0:0:0:  class=3D0x021071 card=3D0x01041400 chip=3D0x000=
00000=20
> rev=3D0x43 hdr=3D0x00
>     class      =3D network
> "86032452@pci0:0:0:     class=3D0x000000 card=3D0x00000000 chip=3D0x00001=
800=20
> rev=3D0x00 hdr=3D0x00
>     vendor     =3D 'Virtual IP group Inc'
>     class      =3D old
>     subclass   =3D non-VGA display device
> none7@pci96:28:157:     class=3D0x001801 card=3D0x00000000 chip=3D0x00000=
000=20
> rev=3D0x00 hdr=3D0xc3
>     class      =3D old
> none8@pci68:192:32:     class=3D0x000000 card=3D0xc39d1c60 chip=3D0x00000=
000=20
> rev=3D0x00 hdr=3D0x05
>     class      =3D old
>     subclass   =3D non-VGA display device
> none9@pci0:0:0: class=3D0x000000 card=3D0x0520c044 chip=3D0xc39d1c60 rev=
=3D0x00=20
> hdr=3D0x00
>     class      =3D old
>     subclass   =3D non-VGA display device
> none10@pci0:0:0:        class=3D0x601c9d card=3D0x00000000 chip=3D0x0520c=
044=20
> rev=3D0xc3 hdr=3D0x00
> `=9D=81=C3-2126966548@pci0:192:221:    class=3D0x44c020 card=3D0x00000000=
 chip=3D0x00000000=20
> rev=3D0x05 hdr=3D0xc2
> D=81=C0 `=9D=81=C368686952@pci2:0:0:        class=3D0x000000 card=3D0xc2d=
dc000 chip=3D0x00000000=20
> rev=3D0x00 hdr=3D0x10
>     class      =3D old
>     subclass   =3D non-VGA display device
> none11@pci140:22:26:    class=3D0x000000 card=3D0x01000002 chip=3D0xc2ddc=
000=20
> rev=3D0x00 hdr=3D0x00
>     class      =3D old
>     subclass   =3D non-VGA display device
> none12@pci37:16:159:    class=3D0x00c0dd card=3D0x14121524 chip=3D0x10000=
706=20
> rev=3D0xc2 hdr=3D0x00
>     class      =3D old
> none13@pci6:4:1:        class=3D0x050100 card=3D0x009f1025 chip=3D0x05301=
524=20
> rev=3D0x01 hdr=3D0x00
>     vendor     =3D 'ENE Technology Inc'
>     device     =3D 'PCI Memory Stick Card Reader Controller'
>     class      =3D memory
>     subclass   =3D flash
> -1013113760@pci0:0:0:   class=3D0x241550 card=3D0x00020406 chip=3D0x009f1=
025=20
> rev=3D0x05 hdr=3D0x00
>     vendor     =3D 'Acer Incorporated'
> $ 86032452@pci0:0:0:    class=3D0x25109f card=3D0x00000000 chip=3D0x00030=
406=20
> rev=3D0x00 hdr=3D0x00
> %=20

That's odd just as you say... why?
---
Watanabe Kazuhiro (CQG00620@nifty.ne.jp)



Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20071108153959.8FFAD12308>