eRacks Forums

eRacks Forums » compatibility

1. joe
   Moderator

   Following is a post of the delivery report of a recent custom installation we did of FreeBSD 6.2 on our Toshiba-based eRacks/TABLET:

   - - - - -

   Basic FreeBSD 6.2 Installation:

   - Shrank the main Windows partition (there appear to be three windoze
   partitions, total, presumably one for hibernation), and used the
   remaining space for the FreeBSD partition. Set up the BSD slices using
   "auto". The Windows instalation can still be completed if you wish,
   although it complains about the disk being resized; it should recover
   itself and finish installing if you want it to, or just reformat it if
   you want the space - perhaps you could share the hibernate partition.

   - It's installed with the FreeBSD Boot Loader, press F4 to get to the
   FreeBSD boot screen (it remembers the last default, as well).

   - Installed numerous packages from the ports tree, including X, Gnome,
   and many Gnome addons such as 'fifth toe'. X Windows required tweaking
   to get to work, see more below.

   - Start X and Gnome with the 'gdb' command from the comandline prompt.
   (startx will start twm, FWIW).

   - em0 is now working, but did NOT work at the basic install, it required
   a boot loader / sysctl config regarding nonstandard BIOS memory maps,
   IIRC. Also, it whines about firmware being unavailble at bootup (in the
   dmesg), but works anyway. This is common with Intel NICs that require a
   firmware blob.

   - Wifi (Intel ipw3945/abg) is now working, albeit with an "experimental"
   driver - the one I installed is based on the OpenBSD non-blob driver, IIRC.

   I downloaded (but did not install) the blob-based intel-sanctioned
   driver, but I prefer non-blob drivers if I can help it, there are fewer
   security surprises that way, and they often work better than the
   manufacturer-"Approved" ones :-)

   - Tablet/pen is now working, but did NOT work in the basic install.
   Required habd-editing of xorg.conf to add the x and y extent parms.
   Pressure sensitivity is not enabled or qualified yet.

   - Sound is not working. Although I found a driver that correctly
   recognized the sound hardware (Intel High Def Audio), and installs
   correctly, at boot, I get no sound. The hardware is OK, and works under
   Ubuntu Linux (see below). More research required.

   - ST-Micro Thumbprint security recognizer - is recognized by the kernel,
   and there is a module for it in the ports tree, and a HOWTO available on
   the web (it should also be in your bookmarks already).

   There are several excellent HOWTOs and other resources on FreeBSD,
   Tablets, and the various chipsets, all in the history and bookmarks
   inside the Epiphany browser, which is the default installed under the
   Gnome Desktop on your tablet.

   In general, the various chipsets are recognized and supported, and
   should be supported by the FreeBSD community either now or in the near
   future.

   I also noticed that many of the chipsets were already reported as
   working in the 7.0-CURRENT version of FreeBSD, FWIW.

   Still to do:

   1) Pressure sensitivity in the tablet

   2) further research to get the sound working

   3) blob-based wifi driver, if desired.

   4) TI-based SD/MMC card recognition / mount

   5) Thumbprint recognition and security integration.

   6) Work on full 1400x1050 resolution - even though the Xorg.log file
   shows it as recognized at 1400x1050, it only initialized it into
   1280x1024 mode. It may need more tweaking of the refresh rates (I tried
   some, but no success). Ubuntu did the same thing.

   7) Suspend/resume, and/or hibernate

   I would love to hear about any of your successes with this and what we
   would need to offer this as a fully FreeBSD-qualified model.

   Also, we tested and qualified Ubuntu on it - under Ubuntu Linux 7.04,
   almost everything works "Out of the box", although we had to do some
   tweaking, here's the report, for your help and information:

   - eth0 - works

   - ipw3945abg - works, autoinstalls restricted (blob-based) driver

   - X - works, 1280x1024

   - Tablet/Pen - works, no tweaking required (but no pressure sensitivity)

   - Sound - works

   - Toshiba Extensions / Fn Keys - once the acpitool and fnfxd was
   installed, even the little Fn-volume and brightness could be adjusted.

   - Suspend-to-RAM (S3) - works, resumes fine, but kills existing windows
   for some reason (using acpitool)

   - Hibernate / Suspend-to-disk (S4) - not tested, since we booted from a
   "Live" CD, and no Linux Swap partition was defined.

   - ST-Micro Biometric Coprocessor - recognized, no further qual done on this.

   - SD/MMC card - recognized, driver loads, but not mountable. More
   research required, although looks likely to be working soon via the
   community support for it. Ubuntu Gutsy Gibbon will probably work, and
   may already.

   So that's my report - let me know what successes you have, and if you
   have any further questions we can help you with.

   Posted 2 years ago #

2. Alan
   Member

   The only question I have is about wireless. What does blob mean in this context? It seems to work, but it logs a bunch of messages. I will probably recompile without those messages.

   Thanks! This looks good. --Alan

   Posted 2 years ago #

3. joe
   Moderator

   > The only question I have is about wireless. What does blob mean in this
   > context?

   Unfortunately, some hardware manufacturers, in an effort to try to show
   they are "contributing" to the open source community, are displaying a
   disturbing trend -

   They supply a binary-only file which requires installation, in order
   for their "open source" driver to work.

   In earlier drivers (Atheros, and earlier Intel drivers), this used to be
   called "Firmware", in the sense that it was downloaded and kept in the
   device - now, more recently, it's just a file which is required in order
   for the OSS driver to work (Which raises the question of whether the
   earlier files were ever really "Firmware").

   In reality, this is just the portion of their code that they don't want
   to release as open-source - so it's subject to all the usual problems -
   inexperienced coders, full of bugs, buffer overflows / security vulns,
   etc - plus, it creates a whole new surface-area of API calls that now
   need to be written and maintained to talk to the (non-standard) 'Blob'.

   Players doing this, include Intel, Atheros, Broadcom (IIRC), nVidia, and
   others.

   Notably, Atheros (one of the earliest pioneers, and who started this
   trend, IIRC), claims the FCC insists that the actual peeks and pokes
   remain in the binary-only component so that users cannot boost their
   Wifi 802.11 power above the FCC-mandated power limit.

   Although plausible, this sounds a little thin..

   Anyway, this is what a 'Blob-required' driver refers to, and why I like
   blob-free drivers. The OBSD guys are great at reverse-engrng these,
   (usually, when they get the proverbial round tuit.)

   > It seems to work, but it logs a bunch of messages. I will
   > probably recompile without those messages.

   Or just google around for a newer version, or ask teh original author -
   also, check FreeBSD 7.0-CURRENT to see if there is a backported driver,
   perhaps..

   > Thanks! This looks good. --Alan

   Glad you're happy - spread the word, and keep us posted on what other
   successes you have with it!

   Posted 2 years ago #

4. Alan
   Member

   I thought I'd give you an update. After some false starts, I finally got 1400x1050 working on my laptop. I read that it's supported in Xorg 7.2, so I re-installed xorg from ports and updated it to 7.2. But the Xserver is still only 1.2, not 1.4 which is the 7.2 server that supports 1400x1050. However, some more searching found this code snippet for linux called 915resolution. Apparently the bios out of the box does not have a 1400x1050 resolution in it, even though it's a native resolution of the laptop screen. But you can replace one of the existing resolutions (in my case 1024x768), and presto! It works. This code is what got moved into the i810 driver for the new Xorg server.

   FYI, here's a link to 915resolution:

   http://www.geocities.com/stomljen/

   The wifi adapter is still kind of flakey. If I let it idle too long, it seems to gets lost and I have to either restart wpa_supplicant or the interface using ifconfig. But it's good enough.

   i found an updated wpi driver, but it doesn't compile under FreeBSD 6.2 release. I sent a note to the author, but I don't know if he meant for it to compile under 6.2 release. Apparently, they've re-arranged the if code a lot for FreeBSD 7.0, so unless I want to completely rebuild my system, I think I'll wait and see if the wpi author has any helpful hints.

   My next goal is to get portrait mode working. I actually haven't tried it since I got 1400x1050 working, but since then, I've discovered xrandr. It claims it can rotate my screen, but when I try, it fails. It may be because I have accelerators turned on. Before I found xrandr, I was trying to rotate it in xorg.conf, but the pen didn't quite map to the cursor correctly.

   Anyway, so that's where I'm at. Thanks again for setting up my computer. It would have been much harder for me without your help! --Alan

   Posted 2 years ago #

5. Alan
   Member

   I was wondering if you knew anything about the memory card reader on the the toshiba laptop?

   I don't see anything that looks like it in the devices listed at boot time. Do you know of any drivers that know about it? Thanks. --Alan

   Posted 2 years ago #

6. admin
   Key Master

   Regarding the SD/MMC card, it is indeed recognized by the kernel, and the driver loads, but for some reason it was not mountable.

   I would check the dmesg for the exact chipset manufacturer (and perhaps locate the PCI IDs, I think it's the "pcitweak" command, IIRC), and google around for it.

   Also, Ubuntu Gutsy Gibbon will probably work, and may already; do the Ubuntu forums may shed some light on it, too.

   If you post your dmesg here, we will help you look.

   Posted 2 years ago #

7. Alan
   Member

   Hi. I don't see anything obvious in the dmesg. It's probably one of the USB devices. However, if I insert a card into the slot, I don't see any log messages, either. When I attach or remove a USB key drive I see a log message. Here's the dmesg:

   


   C

   Posted 2 years ago #

8. Alan
   Member

   Hmm. That didn't work. Trying again:<br><br>

   
Copyright (c) 1992-2007 The FreeBSD Project.
Copyright (c) 1979, 1980, 1983, 1986, 1988, 1989, 1991, 1992, 1993, 1994
The Regents of the University of California. All rights reserved.
FreeBSD is a registered trademark of The FreeBSD Foundation.
FreeBSD 6.2-RELEASE #0: Sat Sep 1 17:40:38 PDT 2007
alan@poire:/usr/obj/usr/src/sys/GENERIC
ACPI APIC Table: <TOSHIB A003C >
Timecounter "i8254" frequency 1193182 Hz quality 0
CPU: Intel(R) Core(TM)2 CPU T5600 @ 1.83GHz (1828.77-MHz 686-class CPU)
Origin = "GenuineIntel" Id = 0x6f2 Stepping = 2
Features=0xbfebfbff<FPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,CLFLUSH,DTS,ACPI,MMX,FXSR,SSE,SSE2,SS,HTT,TM,PBE>
Features2=0xe3bd<SSE3,RSVD2,MON,DS_CPL,VMX,EST,TM2,<b9>,CX16,<b14>,<b15>>
AMD Features=0x20000000<LM>
AMD Features2=0x1<LAHF>
Cores per package: 2
real memory = 2138374144 (2039 MB)
avail memory = 2087571456 (1990 MB)
ioapic0: Changing APIC ID to 1
ioapic0 <Version 2.0> irqs 0-23 on motherboard
kbd1 at kbdmux0
ath_hal: 0.9.17.2 (AR5210, AR5211, AR5212, RF5111, RF5112, RF2413, RF5413)
acpi0: <TOSHIB A003C> on motherboard
acpi_bus_number: can't get _ADR
acpi_bus_number: can't get _ADR
acpi0: Power Button (fixed)
Timecounter "ACPI-fast" frequency 3579545 Hz quality 1000
acpi_timer0: <24-bit timer at 3.579545MHz> port 0xd808-0xd80b on acpi0
cpu0: <ACPI CPU> on acpi0
pcib0: <ACPI Host-PCI bridge> port 0xcf8-0xcff on acpi0
pci0: <ACPI PCI bus> on pcib0
agp0: <Intel 82945GM (945GM GMCH) SVGA controller> port 0xcff8-0xcfff mem 0xffd80000-0xffdfffff,0xe0000000-0xefffffff,0xffd40000-0xffd7ffff irq 16 at device 2.0 on pci0
agp0: detected 7932k stolen memory
agp0: aperture size is 256M
pci0: <display> at device 2.1 (no driver attached)
pcm0: <Intel 82801G High Definition Audio Controller> at device 27.0 on pci0
init 0xc644a680
init 0xc6495100
pcm0: Output Streams: 4, Input Streams: 4, Bidirectional Streams: 0
pcm0: CORB Size: 256, RIRB Size: 256
pcib1: <ACPI PCI-PCI bridge> irq 17 at device 28.0 on pci0
pci1: <ACPI PCI bus> on pcib1
em0: <Intel(R) PRO/1000 Network Connection Version - 6.2.9> port 0xbfe0-0xbfff mem 0xffce0000-0xffcfffff irq 16 at device 0.0 on pci1
em0: Ethernet address: 00:15:b7:33:12:f1
pcib2: <ACPI PCI-PCI bridge> irq 18 at device 28.2 on pci0
pci2: <ACPI PCI bus> on pcib2
pci2: <network> at device 0.0 (no driver attached)
uhci0: <UHCI (generic) USB controller> port 0xafe0-0xafff irq 23 at device 29.0 on pci0
uhci0: [GIANT-LOCKED]
usb0: <UHCI (generic) USB controller> on uhci0
usb0: USB revision 1.0
uhub0: Intel UHCI root hub, class 9/0, rev 1.00/1.00, addr 1
uhub0: 2 ports with 2 removable, self powered
uhci1: <UHCI (generic) USB controller> port 0xaf80-0xaf9f irq 19 at device 29.1 on pci0
uhci1: [GIANT-LOCKED]
usb1: <UHCI (generic) USB controller> on uhci1
usb1: USB revision 1.0
uhub1: Intel UHCI root hub, class 9/0, rev 1.00/1.00, addr 1
uhub1: 2 ports with 2 removable, self powered
uhci2: <UHCI (generic) USB controller> port 0xaf60-0xaf7f irq 18 at device 29.2 on pci0
uhci2: [GIANT-LOCKED]
usb2: <UHCI (generic) USB controller> on uhci2
usb2: USB revision 1.0
uhub2: Intel UHCI root hub, class 9/0, rev 1.00/1.00, addr 1
uhub2: 2 ports with 2 removable, self powered
uhci3: <UHCI (generic) USB controller> port 0xaf40-0xaf5f irq 16 at device 29.3 on pci0
uhci3: [GIANT-LOCKED]
usb3: <UHCI (generic) USB controller> on uhci3
usb3: USB revision 1.0
uhub3: Intel UHCI root hub, class 9/0, rev 1.00/1.00, addr 1
uhub3: 2 ports with 2 removable, self powered
ehci0: <Intel 82801GB/R (ICH7) USB 2.0 controller> mem 0xffd3fc00-0xffd3ffff irq 23 at device 29.7 on pci0
ehci0: [GIANT-LOCKED]
usb4: EHCI version 1.0
usb4: companion controllers, 2 ports each: usb0 usb1 usb2 usb3
usb4: <Intel 82801GB/R (ICH7) USB 2.0 controller> on ehci0
usb4: USB revision 2.0
uhub4: Intel EHCI root hub, class 9/0, rev 2.00/1.00, addr 1
uhub4: 8 ports with 8 removable, self powered
pcib3: <ACPI PCI-PCI bridge> at device 30.0 on pci0
pci3: <ACPI PCI bus> on pcib3
cbb0: <PCI-CardBus Bridge> at device 11.0 on pci3
cardbus0: <CardBus bus> on cbb0
pccard0: <16-bit PCCard bus> on cbb0
fwohci0: <1394 Open Host Controller Interface> at device 11.1 on pci3
fwohci0: OHCI version 1.10 (ROM=1)
fwohci0: No. of Isochronous channels is 4.
fwohci0: EUI64 00:00:39:00:00:af:6e:65
fwohci0: Phy 1394a available S400, 3 ports.
fwohci0: Link S400, max_rec 2048 bytes.
firewire0: <IEEE1394(FireWire) bus> on fwohci0
fwe0: <Ethernet over FireWire> on firewire0
if_fwe0: Fake Ethernet address: 02:00:39:af:6e:65
fwe0: Ethernet address: 02:00:39:af:6e:65
fwe0: if_start running deferred for Giant
sbp0: <SBP-2/SCSI over FireWire> on firewire0
fwohci0: Initiate bus reset
fwohci0: node_id=0xc000ffc0, gen=1, CYCLEMASTER mode
firewire0: 1 nodes, maxhop <= 0, cable IRM = 0 (me)
firewire0: bus manager 0 (me)
pci3: <mass storage> at device 11.2 (no driver attached)
pci3: <base peripheral> at device 11.3 (no driver attached)
isab0: <PCI-ISA bridge> at device 31.0 on pci0
isa0: <ISA bus> on isab0
atapci0: <Intel ICH7 UDMA100 controller> port 0x1f0-0x1f7,0x3f6,0x170-0x177,0x376,0xaf10-0xaf1f irq 18 at device 31.1 on pci0
ata0: <ATA channel 0> on atapci0
ata1: <ATA channel 1> on atapci0
atapci1: <Intel ICH7M SATA300 controller> port 0xaf08-0xaf0f,0xaf04-0xaf07,0xaef8-0xaeff,0xaef4-0xaef7,0xaee0-0xaeef mem 0xffd3f800-0xffd3fbff irq 19 at device 31.2 on pci0
atapci1: AHCI Version 01.10 controller with 4 ports detected
ata2: <ATA channel 0> on atapci1
ata3: <ATA channel 1> on atapci1
ata4: <ATA channel 2> on atapci1
ata5: <ATA channel 3> on atapci1
acpi_lid0: <Control Method Lid Switch> on acpi0
battery0: <ACPI Control Method Battery> on acpi0
battery1: <ACPI Control Method Battery> on acpi0
acpi_button0: <Power Button> on acpi0
acpi_acad0: <AC Adapter> on acpi0
acpi_tz0: <Thermal Zone> on acpi0
atkbdc0: <Keyboard controller (i8042)> port 0x60,0x64 irq 1 on acpi0
atkbd0: <AT Keyboard> irq 1 on atkbdc0
kbd0 at atkbd0
atkbd0: [GIANT-LOCKED]
psm0: <PS/2 Mouse> irq 12 on atkbdc0
psm0: [GIANT-LOCKED]
psm0: model GlidePoint, device ID 0
sio0 port 0x338-0x33f irq 4 flags 0x10 on acpi0
sio0: type 16550A
pmtimer0 on isa0
orm0: <ISA Option ROMs> at iomem 0xc0000-0xcffff,0xd4000-0xdbfff,0xe0000-0xeffff on isa0
ppc0: parallel port not found.
sc0: <System console> at flags 0x100 on isa0
sc0: VGA <16 virtual consoles, flags=0x300>
sio1: configured irq 3 not in bitmap of probed irqs 0
sio1: port may not be enabled
vga0: <Generic ISA VGA> at port 0x3c0-0x3df iomem 0xa0000-0xbffff on isa0
ugen0: STMicroelectronics Biometric Coprocessor, rev 1.00/0.01, addr 2
Timecounter "TSC" frequency 1828765246 Hz quality 800
Timecounters tick every 1.000 msec
acd0: DVDR <MATSHITADVD-RAM UJ-842S/1.40> at ata0-master UDMA33
ad4: 95396MB <TOSHIBA MK1032GSX AS022M> at ata2-master SATA150
pcm0: node 2 type 0 cap d0401
pcm0: node 3 type 1 cap 1d0541
pcm0: node 4 type 1 cap 140311
pcm0: node 5 type 0 cap 40211
pcm0: node 6 type f cap f30201
pcm0: node 7 type 3 cap 300901
pcm0: node 8 type 4 cap 430681
pcm0: node 9 type 4 cap 400301
pcm0: node 10 type 3 cap 30090d
pcm0: node 11 type 3 cap 300105
pcm0: node 12 type 3 cap 30010d
pcm0: node 13 type 4 cap 400181
pcm0: node 14 type 4 cap 400181
pcm0: node 15 type 4 cap 400181
pcm0: node 16 type 4 cap 400181
pcm0: node 17 type 4 cap 400104
pcm0: node 18 type 4 cap 400001
pcm0: node 19 type 2 cap 200100
pcm0: node 20 type 7 cap 70000c
pcm0: Cap 1d0541 sf 0 st 0
pcm0: Set 0:3 10
pcm0: Cap 140311 sf e0160 st 5
pcm0: Set 0:4 20
Trying to mount root from ufs:/dev/ad4s4a


   Posted 2 years ago #

9. joe
   Moderator

   Hmm... I don't see the SD/MMC card in the dmesg you send.

   Two things we can do, next:

   1) List the PCI bus details with "pciconf -lv" and/or pcitweak, and look for the SD/MMC card or the 'unknown' entries

   2) Boot up from a Ubuntu Gutsy Gibbon Live CD, and read the dmesg (and post it here!), and see if it possibly is recognized and works under Gutsy.

   Posted 2 years ago #

10. Alan
    Member

    Hi. I'm afraid I'm completely ignorant about Linux. Where can I get a bootable Ubuntu CD? Do they sell these shrinkwrapped, like at Fry's or Computer Center?

    Meanwhile, here is output from pciconf -lv:

    
hostb0@pci0:0:0: class=0x060000 card=0x00011179 chip=0x27a08086 rev=0x03 hdr=0x00
vendor = 'Intel Corporation'
class = bridge
subclass = HOST-PCI
agp0@pci0:2:0: class=0x030000 card=0x00011179 chip=0x27a28086 rev=0x03 hdr=0x00
vendor = 'Intel Corporation'
class = display
subclass = VGA
none0@pci0:2:1: class=0x038000 card=0x00011179 chip=0x27a68086 rev=0x03 hdr=0x00
vendor = 'Intel Corporation'
class = display
pcm0@pci0:27:0: class=0x040300 card=0x00011179 chip=0x27d88086 rev=0x02 hdr=0x00
vendor = 'Intel Corporation'
device = '82801G (ICH7 Family) High Definition Audio'
class = multimedia
pcib1@pci0:28:0: class=0x060400 card=0x00000040 chip=0x27d08086 rev=0x02 hdr=0x01
vendor = 'Intel Corporation'
device = '82801G (ICH7 Family) PCI Express Root Port'
class = bridge
subclass = PCI-PCI
pcib2@pci0:28:2: class=0x060400 card=0x00000040 chip=0x27d48086 rev=0x02 hdr=0x01
vendor = 'Intel Corporation'
device = '82801G (ICH7 Family) PCI Express Root Port'
class = bridge
subclass = PCI-PCI
uhci0@pci0:29:0: class=0x0c0300 card=0x00011179 chip=0x27c88086 rev=0x02 hdr=0x00
vendor = 'Intel Corporation'
device = '82801G (ICH7 Family) USB Universal Host Controller'
class = serial bus
subclass = USB
uhci1@pci0:29:1: class=0x0c0300 card=0x00011179 chip=0x27c98086 rev=0x02 hdr=0x00
vendor = 'Intel Corporation'
device = '82801G (ICH7 Family) USB Universal Host Controller'
class = serial bus
subclass = USB
uhci2@pci0:29:2: class=0x0c0300 card=0x00011179 chip=0x27ca8086 rev=0x02 hdr=0x00
vendor = 'Intel Corporation'
device = '82801G (ICH7 Family) USB Universal Host Controller'
class = serial bus
subclass = USB
uhci3@pci0:29:3: class=0x0c0300 card=0x00011179 chip=0x27cb8086 rev=0x02 hdr=0x00
vendor = 'Intel Corporation'
device = '82801G (ICH7 Family) USB Universal Host Controller'
class = serial bus
subclass = USB
ehci0@pci0:29:7: class=0x0c0320 card=0x00011179 chip=0x27cc8086 rev=0x02 hdr=0x00
vendor = 'Intel Corporation'
device = '82801G (ICH7 Family) USB 2.0 Enhanced Host Controller'
class = serial bus
subclass = USB
pcib3@pci0:30:0: class=0x060401 card=0x00000050 chip=0x24488086 rev=0xe2 hdr=0x01
vendor = 'Intel Corporation'
device = '82801BAM/CAM/DBM (ICH2-M/3-M/4-M) Hub Interface to PCI Bridge'
class = bridge
subclass = PCI-PCI
isab0@pci0:31:0: class=0x060100 card=0x00011179 chip=0x27b98086 rev=0x02 hdr=0x00
vendor = 'Intel Corporation'
device = '82801GBM (ICH7-M) LPC Interface Controller'
class = bridge
subclass = PCI-ISA
atapci0@pci0:31:1: class=0x01018a card=0x00011179 chip=0x27df8086 rev=0x02 hdr=0x00
vendor = 'Intel Corporation'
device = '82801G (ICH7 Family) Ultra ATA Storage Controller'
class = mass storage
subclass = ATA
atapci1@pci0:31:2: class=0x010601 card=0x0f001179 chip=0x27c58086 rev=0x02 hdr=0x00
vendor = 'Intel Corporation'
device = '82801GB Mobile I/O Controller Hub SATA cc=AHCI'
class = mass storage
em0@pci1:0:0: class=0x020000 card=0x00011179 chip=0x109a8086 rev=0x00 hdr=0x00
vendor = 'Intel Corporation'
class = network
subclass = ethernet
wpi0@pci2:0:0: class=0x028000 card=0x10408086 chip=0x42228086 rev=0x02 hdr=0x00
vendor = 'Intel Corporation'
class = network
cbb0@pci3:11:0: class=0x060700 card=0x00011179 chip=0x8039104c rev=0x00 hdr=0x02
vendor = 'Texas Instruments (TI)'
class = bridge
subclass = PCI-CardBus
fwohci0@pci3:11:1: class=0x0c0010 card=0x00011179 chip=0x803a104c rev=0x00 hdr=0x00
vendor = 'Texas Instruments (TI)'
class = serial bus
subclass = FireWire
none1@pci3:11:2: class=0x018000 card=0x00011179 chip=0x803b104c rev=0x00 hdr=0x00
vendor = 'Texas Instruments (TI)'
class = mass storage
none2@pci3:11:3: class=0x080501 card=0x00011179 chip=0x803c104c rev=0x00 hdr=0x00
vendor = 'Texas Instruments (TI)'
class = base peripheral


    And here is output from pcitweak -l:

    
PCI: Probing config type using method 1
PCI: Config type is 1
PCI: PCI scan (all values are in hex)
PCI: 00:00:0: chip 8086,27a0 card 1179,0001 rev 03 class 06,00,00 hdr 00
PCI: 00:02:0: chip 8086,27a2 card 1179,0001 rev 03 class 03,00,00 hdr 80
PCI: 00:02:1: chip 8086,27a6 card 1179,0001 rev 03 class 03,80,00 hdr 80
PCI: 00:1b:0: chip 8086,27d8 card 1179,0001 rev 02 class 04,03,00 hdr 00
PCI: 00:1c:0: chip 8086,27d0 card 0000,0000 rev 02 class 06,04,00 hdr 81
PCI: 00:1c:2: chip 8086,27d4 card 0000,0000 rev 02 class 06,04,00 hdr 81
PCI: 00:1d:0: chip 8086,27c8 card 1179,0001 rev 02 class 0c,03,00 hdr 80
PCI: 00:1d:1: chip 8086,27c9 card 1179,0001 rev 02 class 0c,03,00 hdr 00
PCI: 00:1d:2: chip 8086,27ca card 1179,0001 rev 02 class 0c,03,00 hdr 00
PCI: 00:1d:3: chip 8086,27cb card 1179,0001 rev 02 class 0c,03,00 hdr 00
PCI: 00:1d:7: chip 8086,27cc card 1179,0001 rev 02 class 0c,03,20 hdr 00
PCI: 00:1e:0: chip 8086,2448 card 0000,0000 rev e2 class 06,04,01 hdr 01
PCI: 00:1f:0: chip 8086,27b9 card 1179,0001 rev 02 class 06,01,00 hdr 80
PCI: 00:1f:1: chip 8086,27df card 1179,0001 rev 02 class 01,01,8a hdr 00
PCI: 00:1f:2: chip 8086,27c5 card 1179,0f00 rev 02 class 01,06,01 hdr 00
PCI: 01:00:0: chip 8086,109a card 1179,0001 rev 00 class 02,00,00 hdr 00
PCI: 02:00:0: chip 8086,4222 card 8086,1040 rev 02 class 02,80,00 hdr 00
PCI: 03:0b:0: chip 104c,8039 card fffc,ffff rev 00 class 06,07,00 hdr 82
PCI: 03:0b:1: chip 104c,803a card 1179,0001 rev 00 class 0c,00,10 hdr 80
PCI: 03:0b:2: chip 104c,803b card 1179,0001 rev 00 class 01,80,00 hdr 80
PCI: 03:0b:3: chip 104c,803c card 1179,0001 rev 00 class 08,05,01 hdr 80
PCI: End of PCI scan


    Posted 2 years ago #

11. Alan
    Member

    Is it one of the none[012] devices listed in pciconf?

    Posted 2 years ago #

12. joe
    Moderator

    Texas Instruments (TI) is vendor 104c, and those devices are 803a, 803b, and 803c.

    According to: http://www.pcidatabase.com/vendor_details.php?id=308,
    the 803c appears to be an SD controller.

    Further searching/googling around for "104c 803c BSD" (or FreeBSD or linux, too) reveals further enlightening info on this, and the starting point for further searches..

    Here's some partial success on Ubuntu Feisty (one release old):
    http://ubuntuforums.org/showthread.php?t=459987

    BTW, to boot from a live Ubuntu Gutsy CD, simply download a CDImage for your platform (i386 first or x86-64 second choice) from http://ubuntu.com and burn it to a blank CD!

    For that matter, they'll even mail you one for free, as I recall..

    Posted 2 years ago #

RSS feed for this topic

Reply

You must log in to post.