Re: apachectl gracefult causes Signal 11 crash after 6.3 to 7.0 upgrade [SOLVED]
Many people have reported that the *order* of the extensions in extensions.ini has adverse (positive) effects on PHP segfaults on FreeBSD. I myself haven't ever run into extension ordering issues like those described (and we've done hosting for years), but I don't doubt those who have experienced such. Yes Jeremy, I known. I also don't doubt your words, but in my case the order of the extensions seems not any effect. The only solution has been comment the mentioned mbash extension. -- Thanks, Jordi Espasa Clofent ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: Adesso AKB-430UG keyboard on 7.0
Gavin Atkinson wrote:
On Thu, 2008-06-12 at 05:41 -0500, Greg Miller wrote:
Gavin Atkinson wrote:
On Thu, 2008-06-12 at 03:22 -0500, Greg Miller wrote:
I'm using an AKB-430UG USB keyboard ("Win-Touch Pro") on FreeBSD
7.0-release-p1, or trying to. The keyboard works fine in Windows, but
with FreeBSD I get the same sort of problems people have described
previous with the Genius SlimStar Pro: the keys behave as if CTRL is
always pressed.
Can you try the following patch please?
With this patch, it works great as a keyboard. However, the GlidePoint
touchpad isn't being detected as a USB mouse and the data is being
interpreted as keystrokes.
Can you confirm that the GlidePoint was working correctly before the
patch?
No. Connecting the keyboard generates a console message indicating the
ukbd device attached, but doesn't generate a ums attach message, so I'm
thinking that it doesn't work with or without the patch.
--
http://www.velocityvector.com/ | http://www.classic-games.com/
I'd rather hunt with Dick Cheney than ride with Ted Kennedy.
___
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "[EMAIL PROTECTED]"
ZFS version 8 on stable?
Hello everyone, I know -stable is supposed to be, well, stable, but I seem to be in a bit of a pickle. I'm trying to import my zfs file system from a Macintosh machine. It was created at version 8. Being new to zfs, I did not realise that FreeBSD would be running at a lower version; I thought zfs was zfs! Of course, trying to import my zpool fails, complaining that the version is too new. freebsd# zpool import bigstore cannot import 'bigstore': pool is formatted using a newer ZFS version So either I want to downgrade the zpool, or upgrade zfs on FreeBSD. Does anyone know if I'll be able to import zfs v8, or am I wasting my time? I'd prefer to follow -stable, but if I must follow -current, then golly goshkins, I'll have no choice! Kind regards, Timothy. ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: ZFS version 8 on stable?
On Fri, Jun 13, 2008 at 06:40:22PM +1000, Timothy Wilson wrote: > Hello everyone, > > I know -stable is supposed to be, well, stable, but I seem to be in a > bit of a pickle. > > I'm trying to import my zfs file system from a Macintosh machine. It > was created at version 8. Being new to zfs, I did not realise that > FreeBSD would be running at a lower version; I thought zfs was zfs! Of > course, trying to import my zpool fails, complaining that the version > is too new. > > freebsd# zpool import bigstore > cannot import 'bigstore': pool is formatted using a newer ZFS version > > So either I want to downgrade the zpool, or upgrade zfs on FreeBSD. > Does anyone know if I'll be able to import zfs v8, or am I wasting my > time? I'd prefer to follow -stable, but if I must follow -current, > then golly goshkins, I'll have no choice! I don't know what the current migration status is of ZFS on FreeBSD to a newer version. I don't think -CURRENT/HEAD has a newer ZFS either, so I think you're out of luck with regards to an "easy" migration. If I was in your shoes, I would not downgrade the pool -- I would simply stop using ZFS and use a filesystem that is fully compatible between OS X and FreeBSD. *cue someone chiming in with the usual "ZFS is experimental on FreeBSD, blah blah blah" rhetoric* :-) Summary: you're out of luck. -- | Jeremy Chadwickjdc at parodius.com | | Parodius Networking http://www.parodius.com/ | | UNIX Systems Administrator Mountain View, CA, USA | | Making life hard for others since 1977. PGP: 4BD6C0CB | ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: ZFS version 8 on stable?
Timothy Wilson wrote: Hello everyone, I know -stable is supposed to be, well, stable, but I seem to be in a bit of a pickle. I'm trying to import my zfs file system from a Macintosh machine. It was created at version 8. Being new to zfs, I did not realise that FreeBSD would be running at a lower version; I thought zfs was zfs! Of course, trying to import my zpool fails, complaining that the version is too new. freebsd# zpool import bigstore cannot import 'bigstore': pool is formatted using a newer ZFS version So either I want to downgrade the zpool, or upgrade zfs on FreeBSD. Does anyone know if I'll be able to import zfs v8, or am I wasting my time? I'd prefer to follow -stable, but if I must follow -current, then golly goshkins, I'll have no choice! It is planned to update to a newer ZFS release in HEAD, but this has not happened yet (let alone in 7.x). I don't know if it is possible to downgrade a pool - you should check the ZFS documentation/support materials. Kris ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: ZFS version 8 on stable?
>> So either I want to downgrade the zpool, or upgrade zfs on FreeBSD. >> Does anyone know if I'll be able to import zfs v8, or am I wasting my >> time? I'd prefer to follow -stable, but if I must follow -current, >> then golly goshkins, I'll have no choice! > > I don't know what the current migration status is of ZFS on FreeBSD to a > newer version. I don't think -CURRENT/HEAD has a newer ZFS either, so I > think you're out of luck with regards to an "easy" migration. > > If I was in your shoes, I would not downgrade the pool -- I would simply > stop using ZFS and use a filesystem that is fully compatible between OS > X and FreeBSD. *cue someone chiming in with the usual "ZFS is > experimental on FreeBSD, blah blah blah" rhetoric* :-) I tried to create a zfs-pool on Solaris and was unable to import it to FreeBSD. So there are still some issues in relation to OS-platform-migrations. But other than that is this not a somewhat pessimistic approach not to try things out? :-) Many years ago (os x 10.0 or 10.1 I think) I tried to create an UFS-volume on os x but this was not recognized by FreeBSD (ver. 4.x). What other fs-type will work between os x and FreeBSD? FAT comes to my mind. -- regards Claus When lenity and cruelty play for a kingdom, the gentlest gamester is the soonest winner. Shakespeare ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: ZFS version 8 on stable?
Timothy Wilson wrote: > I'm trying to import my zfs file system from a Macintosh machine. It > was created at version 8. Being new to zfs, I did not realise that > FreeBSD would be running at a lower version; I thought zfs was zfs! Of > course, trying to import my zpool fails, complaining that the version > is too new. Have you tried to send a snapshot on you Mac and receive that snapshot on your FreeBSD machine? -- Dick Hoogendijk -- PGP/GnuPG key: F86289CE ++ http://nagual.nl/ | SunOS 10u5 05/08 ++ ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
boot0 is hanging...
Hi, I just did two different installations of 7.0-stable on a new machine and I have some issues with the boot0 boot loader. I have two identical drives on that machine. The first two slices on the drives are supposed to be bootable and they are mirrored with gmirror: gmirror label -v -h -b load boot1 ad4s1a ad6s1a gmirror label -v -h -b load boot2 ad6s2a ad4s2a The problem I have is that I can only boot the second slice from ad6, not from ad4. boot0 does nothing when I press F2 from the menu for the first drive. I don't get any error message. It does nothing until I select another item in the menu. I can boot the first slice from either ad4 or ad6. I have tried rebuilding the raid and changing the priority of the drive with gmirror, but it didn't change anything. I also tried to remove ad6s2a from the mirror, but it didn't fix it either. To install boot0, I used: sysctl kern.geom.debugflags=16 boot0cfg -B -m 0x3 -s 1 ad4 boot0cfg -B -m 0x3 -s 1 ad6 What could be causing this exactly? Thank you! ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: ZFS version 8 on stable?
There's nothing you can do right now except for wait. By default the zfs implementation on osx will create a zfs version 6 zpool (to retain compat with the read-only kext that ships with 10.5) but once you've upgraded you can't go back. There is a newer version of zfs for freebsd but it hasn't been commited yet. See http://kerneltrap.org/FreeBSD/BSDCan_2008_ZFS_Internals Your only option is to wait until this is committed or patches are offered at least. pjd is the man so it shouldn't be too long :-) Timothy Wilson wrote: Hello everyone, I know -stable is supposed to be, well, stable, but I seem to be in a bit of a pickle. I'm trying to import my zfs file system from a Macintosh machine. It was created at version 8. Being new to zfs, I did not realise that FreeBSD would be running at a lower version; I thought zfs was zfs! Of course, trying to import my zpool fails, complaining that the version is too new. freebsd# zpool import bigstore cannot import 'bigstore': pool is formatted using a newer ZFS version So either I want to downgrade the zpool, or upgrade zfs on FreeBSD. Does anyone know if I'll be able to import zfs v8, or am I wasting my time? I'd prefer to follow -stable, but if I must follow -current, then golly goshkins, I'll have no choice! Kind regards, Timothy. ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]" ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: 80 Mb / enough for 7.x? OK to delete /stand/ and /modules/ ?
On Thu, 12 Jun 2008, fbsd2 wrote: Given recent EOL announcements, I'm trying to upgrade an ancient machine from 5.5 to 7. It has 80 Mb total in the root partition, /home/, /var/, /usr/, and /tmp/ on other partitions, and NFS mounts /usr/src, /usr/obj, and /usr/ports from a slightly newer/faster box. I've seen http://www.freebsd.org/releases/7.0R/relnotes.html and http://marc.info/?l=freebsd-stable&m=121278826119286&w=2 which seem to suggest that even with INSTALL_NODEBUG during buildkernel, 7 might not fit in an 80 Mb /. Must I partition a new disk to give more space to /, or can I find more space by deleting /stand/, /modules/, and possibly /rescue/ to shoehorn a custom 7.x kernel in the available space? TIA My Kerberos server runs 7-STABLE and has a 93M root with 25M free. It's a bit tight -- I have to remember to disable the installation of debugging symbols for the kernel and modules, for example. However, it does work fine, and that's even with modules installed. The bigger problem is my old /var now that I have audit enabled. Robert N M Watson Computer Laboratory University of Cambridge ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: ZFS version 8 on stable?
On Jun 13, 2008, at 09:54, Dillon Kass wrote: Your only option is to wait until this is committed or patches are offered at least. pjd is the man so it shouldn't be too long :-) Another option could be to see if you can help with the coding. :) ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: [7-STABLE] ping -s 4000 with ipsec panic
Le Fri, 13 Jun 2008 01:57:35 +0200, Kris Kennaway <[EMAIL PROTECTED]> a écrit : Hello, [...] > > #17 0xc0700746 in crypto_invoke (cap=0x8, crp=0xd61a0950, > > hint=-1616994916) at cryptodev_if.h:53 > > Previous frame inner to this frame (corrupt stack?) > > (kgdb) > > Unfortunately the trace is bogus. Try to rebuild with -O instead of > -O2 and reproduce the panic. Hmm, i've got no luck with -O. I made few tests and the panic occurs with a -s of 3989 bytes. ping -s 3988 => ok ping -s 3989 => panic The coredump seems to be ok. http://user.lamaiziere.net/patrick/coredump.txt I will try with a kernel and DEBUG_REDZONE and INVARIANT. --- Unread portion of the kernel message buffer: Fatal trap 12: page fault while in kernel mode fault virtual address = 0x9350ef1e fault code = supervisor read, page not present instruction pointer = 0x20:0xc05a0579 stack pointer = 0x28:0xd61635cc frame pointer = 0x28:0xd61635d0 code segment= base 0x0, limit 0xf, type 0x1b = DPL 0, pres 1, def32 1, gran 1 processor eflags= interrupt enabled, resume, IOPL = 0 current process = 1101 (ping) trap number = 12 panic: page fault Uptime: 7m47s Physical memory: 503 MB Dumping 88 MB: 73 57 41 25 9 #0 doadump () at pcpu.h:195 in pcpu.h (kgdb) bt #0 doadump () at pcpu.h:195 #1 0xc0556273 in boot (howto=260) at /usr/src/sys/kern/kern_shutdown.c:418 #2 0xc055646f in panic (fmt=) at /usr/src/sys/kern/kern_shutdown.c:572 #3 0xc079b91c in trap_fatal (frame=0xd616358c, eva=2471554846) at /usr/src/sys/i386/i386/trap.c:899 #4 0xc079bba0 in trap_pfault (frame=0xd616358c, usermode=0, eva=2471554846) at /usr/src/sys/i386/i386/trap.c:812 #5 0xc079c529 in trap (frame=0xd616358c) at /usr/src/sys/i386/i386/trap.c:490 #6 0xc0789f2b in calltrap () at /usr/src/sys/i386/i386/exception.s:139 #7 0xc05a0579 in mb_dupcl (n=0xc2b02000, m=0xc2b02d00) at /usr/src/sys/kern/uipc_mbuf.c:293 #8 0xc05a157a in m_copym (m=0xc2b02d00, off0=2980, len=3, wait=1) at /usr/src/sys/kern/uipc_mbuf.c:570 #9 0xc0614055 in ip_fragment (ip=0xc2e5a038, m_frag=0xd61636d0, mtu=1500, if_hwassist_flags=7, sw_csum=0) at /usr/src/sys/netinet/ip_output.c:728 #10 0xc0614d38 in ip_output (m=0xc2b02600, opt=0x0, ro=0xd6163694, flags=2, imo=0x0, inp=0x0) at /usr/src/sys/netinet/ip_output.c:567 #11 0xc06acd9d in ipsec_process_done (m=0xc2b02600, isr=0xc2bacd80) at /usr/src/sys/netipsec/ipsec_output.c:177 #12 0xc06bbf5c in esp_output_cb (crp=0xc2e5c708) at /usr/src/sys/netipsec/xform_esp.c:965 #13 0xc06ff730 in crypto_done (crp=0xc2e5c708) at /usr/src/sys/opencrypto/crypto.c:1148 #14 0xc0702afe in swcr_process (dev=0xc29cf380, crp=0xc2e5c708, hint=0) at /usr/src/sys/opencrypto/cryptosoft.c:975 #15 0xc0700746 in crypto_invoke (cap=0xc29cf380, crp=0xc2e5c708, hint=0) at cryptodev_if.h:53 #16 0xc070118c in crypto_dispatch (crp=0xc2e5c708) at /usr/src/sys/opencrypto/crypto.c:798 #17 0xc06bc5c6 in esp_output (m=0xc2b02600, isr=0xc2bacd80, mp=0x0, skip=20, protoff=9) at /usr/src/sys/netipsec/xform_esp.c:875 #18 0xc06ad112 in ipsec4_process_packet (m=0xc2b02600, isr=0xc2bacd80, flags=32, tunalready=0) at /usr/src/sys/netipsec/ipsec_output.c:491 #19 0xc0612f95 in ip_ipsec_output (m=0xd6163b04, inp=0xc2e07870, flags=0xd6163b10, error=0xd6163ae4, ro=0xd6163b0c, iproute=0xd6163ac8, dst=0xd6163ae0, ia=0xd6163adc, ifp=0xd6163aec) at /usr/src/sys/netinet/ip_ipsec.c:331 #20 0xc0614ab9 in ip_output (m=0xc2b02600, opt=0x0, ro=0xd6163ac8, flags=32, imo=0x0, inp=0xc2e07870) at /usr/src/sys/netinet/ip_output.c:420 #21 0xc0615e1b in rip_output (m=0xc2b02600, so=0xc2ddfad4, dst=352430272) at /usr/src/sys/netinet/raw_ip.c:336 #22 0xc0615efc in rip_send (so=0xc2ddfad4, flags=0, m=0xc2b02600, nam=0xc29f9800, control=0x0, td=0xc2b77000) at /usr/src/sys/netinet/raw_ip.c:806 #23 0xc05a97f5 in sosend_generic (so=0xc2ddfad4, addr=0xc29f9800, uio=0xd6163be8, top=0xc2b02600, control=0x0, flags=0, td=0xc2b77000) at /usr/src/sys/kern/uipc_socket.c:1240 #24 0xc05a580f in sosend (so=0xc2ddfad4, addr=0xc29f9800, uio=0xd6163be8, top=0x0, control=0x0, flags=0, td=0xc2b77000) at /usr/src/sys/kern/uipc_socket.c:1286 #25 0xc05abf16 in kern_sendit (td=0xc2b77000, s=3, mp=0xd6163c64, flags=0, control=0x0, segflg=UIO_USERSPACE) at /usr/src/sys/kern/uipc_syscalls.c:789 #26 0xc05af031 in sendit (td=0xc2b77000, s=3, mp=0xd6163c64, flags=0) at /usr/src/sys/kern/uipc_syscalls.c:730 #27 0xc05af148 in sendto (td=0xc2b77000, uap=0xd6163cfc) at /usr/src/sys/kern/uipc_syscalls.c:841 #28 0xc079bef5 in syscall (frame=0xd6163d38) at /usr/src/sys/i386/i386/trap.c:1035 #29 0xc0789f90 in Xint0x80_syscall () at /usr/src/sys/i386/i386/exception.s:196 #30 0x0033 in ?? () (kgdb) quit -- Thanks, regards. ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/free
Unusually large directory - 2.0 peta bytes
While preparing to upgrade to latest stable, I ran some scripts to verify that the target was OK and found something that I think I need to fix but have no clue to how. This is the essence of what I found: # ls /usr/local/lib/perl5/site_perl/5.8.8/mach/auto/APR/PerlIO/* autosplit.ix # ls -la /usr/local/lib/perl5/site_perl/5.8.8/mach/auto/APR/PerlIO/* ls: : No such file or directory ls: autosplit.ix: No such file or directory total 8 drwxr-xr-x 2 root wheel 2251799813685760 Jun 14 04:06 . drwxr-xr-x 2 root wheel 2251799813685760 Jun 14 04:06 . drwxr-xr-x 24 root wheel 512 Mar 29 10:33 .. drwxr-xr-x 24 root wheel 512 Mar 29 10:33 .. # stat /usr/local/lib/perl5/site_perl/5.8.8/mach/auto/APR/PerlIO 163 5229427 drwxr-xr-x 2 root wheel 20894350 2251799813685760 "Jun 14 07:07:43 2008" "Jun 14 04:06:44 2008" "Jun 14 04:06:44 2008" "Mar 29 10:33:10 2008" 4096 4 0 /usr/local/lib/perl5/site_perl/5.8.8/mach/auto/APR/PerlIO # stat /usr/local/lib/perl5/site_perl/5.8.8/mach/auto/APR/PerlIO/autosplit.ix stat: /usr/local/lib/perl5/site_perl/5.8.8/mach/auto/APR/PerlIO/autosplit.ix: stat: No such file or directory # od -c /usr/local/lib/perl5/site_perl/5.8.8/mach/auto/APR/PerlIO | more 000s 313 O \0 \f \0 004 001 . \0 \0 \0 1 313 O \0 020 364 001 004 002 . . \0 \0 t 313 O \0 024 \0 \b \t 040P e r l I O . s o \0 217 300 u 313 O \0 060 324 001 \b \t P e r l I O . b s \0 217 300 100 \0 \0 \0 \0 \0 \0 \0 \0 \0 \0 \0 \0 \0 \0 \0 \0 * 0001000 \0 \0 \0 \0 \0 002 \0 \0 \0 \0 \0 \0 \0 \0 \0 \0 0001020 \0 \0 \0 \0 \0 \0 \0 \0 \0 \0 \0 \0 \0 \0 \0 \0 * 0002000 \0 \0 \0 \0 \0 002 \0 \0 \0 \0 \0 \0 \0 \0 \0 \0 0002020 \0 \0 \0 \0 \0 \0 \0 \0 \0 \0 \0 \0 \0 \0 \0 \0 * 0003000 \0 \0 \0 \0 \0 002 \0 \0 \0 \0 \0 \0 \0 \0 \0 \0 0003020 \0 \0 \0 \0 \0 \0 \0 \0 \0 \0 \0 \0 \0 \0 \0 \0 * 0004000v 313 O \0 \f \0 004 001 . \0 \0 \0 335 312 O \0 0004020 \f \0 004 002 . . \0 \0 w 313 O \0 350 001 \b \f 0004040a u t o s p l i t . i x \0 231 - 351 0004060 \0 \0 \0 \0 \0 \0 \0 \0 \0 \0 \0 \0 \0 \0 \0 \0 * 0005000 \0 \0 \0 \0 \0 002 \0 \0 \0 \0 \0 \0 \0 \0 \0 \0 0005020 \0 \0 \0 \0 \0 \0 \0 \0 \0 \0 \0 \0 \0 \0 \0 \0 * 0006000 \0 \0 \0 \0 \0 002 \0 \0 \0 \0 \0 \0 \0 \0 \0 \0 0006020 \0 \0 \0 \0 \0 \0 \0 \0 \0 \0 \0 \0 \0 \0 \0 \0 * 0007000 \0 \0 \0 \0 \0 002 \0 \0 \0 \0 \0 \0 \0 \0 \0 \0 0007020 \0 \0 \0 \0 \0 \0 \0 \0 \0 \0 \0 \0 \0 \0 \0 \0 * 001 177 E L F 001 001 001 \t \0 \0 \0 \0 \0 \0 \0 \0 0010020 003 \0 003 \0 001 \0 \0 \0 240 \t \0 \0 4 \0 \0 \0 0010040 330 025 \0 \0 \0 \0 \0 \0 4 \0 \0 003 \0 ( \0 This does not look like a directory, it looks like a shared library, PerlIO.so, that somehow got the directory bit set. First, am I correct in my analysis? Second, how do I remove the directory bit so I can delete the file? Host info, dmesg.boot attached: # uname -a FreeBSD balder.glz.hidden-powers.com 6.3-STABLE FreeBSD 6.3-STABLE #1: Thu Feb 28 02:14:05 CET 2008 [EMAIL PROTECTED]:/usr/obj/usr/src/sys/BALDER i386 Cheers, Göran ... the future isMobile Goran Lowkrantz <[EMAIL PROTECTED]> System Architect, isMobile AB Sandviksgatan 81, PO Box 58, S-971 03 Luleå, Sweden Mobile: +46(0)70-587 87 82 http://www.ismobile.com ... dmesg.boot Description: Binary data ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: Texas Instruments Card Reader.
In message: <[EMAIL PROTECTED]> Da Rock <[EMAIL PROTECTED]> writes: : : On Sun, 2008-03-30 at 09:18 -0300, Carlos A. M. dos Santos wrote: : > On Sun, Mar 30, 2008 at 3:58 AM, M. Warner Losh <[EMAIL PROTECTED]> wrote: : > > In message: <[EMAIL PROTECTED]> : > > Da Rock <[EMAIL PROTECTED]> writes: : > > : Did anyone end up getting this to work? I'm suffering the same woes... : > > : > > Which device is this, specifically? : > > : > > Warner : > : > It is an SD, MS/Pro, MMC, SM and XD card reader. It is recognized by : > the Linux "sdhci" driver. There was an email thread some time ago : > discussing an homonymous driver for FreeBSD: : > : > http://lists.freebsd.org/pipermail/freebsd-drivers/2006-September/000243.html : > http://lists.freebsd.org/pipermail/freebsd-drivers/2006-September/000248.html : > : : Thats right- I believe you were working with a ricoh card reader though. : Is there any update to this project? A todo journal maybe? I've a working card reader for ricoh that I've not been able to adapt to TI so I've never committed from a couple of difference sources... I should find time to fix that... Warner ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
