old serial RS-232 pccard and wi driver.
Hello, I encounter a strange problem with an old rs-232 serial pccard on current (just cvsup'ed). The card works quite well on 5.0-RELEASE, but it it is detected as a wlan card on current, and the system attempts to run the wi driver. This calls ther debugger, and the (continue) command reboot the machine, and that at boot, or after any card insertion. I don't know if the machine is very relevant but ... DELL Inspiron 8000 laptop.. The acpi is loaded, and seems to work. An Adaptec apa-1460 pccard works well too, (the IRQ (11) is correctly handled). Here is the message at boot: pccard1: CIS checksum failed. wi0: "Socket Communications Low Power wlan card" at port 0x100-0x107 irq 11= fun1 wi0 init failed. panic block: (sleep mutex" wi0 not locked @ /usr/src-current/src/sys/devwi/= if_w3 debugger (panic) stopped at: debugger+0x54: xchgl %ebx,in_debugger.0. Sorry if I have forgotten something. Best regards raoul [EMAIL PROTECTED] To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
pcmcia card not detected properly
Hi all, I just upgraded Current. In a Dell Inspiron 8000 laptop a pcmcia card is not detected properly. Some lines from dmesg: FreeBSD 5.1-CURRENT #13: Thu Aug 28 21:06:05 CEST 2003 Preloaded elf module "/boot/kernel/acpi.ko" at 0xc071d280. ... acpi0: on motherboard pcibios: BIOS version 2.10 Using $PIR table, 10 entries at 0xc00fbc20 Timecounter "ACPI-fast" frequency 3579545 Hz quality 1000 acpi_timer0: <24-bit timer at 3.579545MHz> port 0x808-0x80b on acpi0 acpi_cpu0: port 0x530-0x537 on acpi0 acpi_tz0: port 0x530-0x537 on acpi0 acpi_acad0: on acpi0 acpi_cmbat0: on acpi0 acpi_cmbat1: on acpi0 acpi_lid0: on acpi0 acpi_button0: on acpi0 acpi_button1: on acpi0 pcib0: port 0xcf8-0xcff on acpi0 pci0: on pcib0 cbb0: at device 15.0 on pci2 cardbus0: on cbb0 pccard0: <16-bit PCCard bus> on cbb0 pcib2: slot 15 INTA is routed to irq 11 cbb1: at device 15.1 on pci2 cardbus1: on cbb1 pccard1: <16-bit PCCard bus> on cbb1 ... CIS is too long -- truncating pccard0: Card has no functions! cbb0: PC Card card activation failed The card works fine. It was detected before upgrading. It is an Adaptec APA-1460. Thanks in advance for your help. Raoul [EMAIL PROTECTED] ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "[EMAIL PROTECTED]"
usb flashkey disk copy error
Hello all, I have a copy error between hdd and a flashkey 1gig usb (easydisk) on Current dated August 28. Here is in short: mount -t msdos /dev/da2s1 /flashkey cp myfile /flashkey/ diff myfile /flashkey/myfile (ok). umount /flashkey mount (flashkey) diff myfile /flashkey/myfile (Binary file differ)! It is not a flashkey disk error, it works on XP. Note that this error occurs on FreeBSD 4.8 too. Please, can you tell me how to deal with that? And in an other hand can you tell me how to obtain the exact map of the flashkey to verify the writing on the disk. Thanks in advance for this newbie question. [EMAIL PROTECTED] ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: usb flashkey disk copy error
John-Mark Gurne wrote this message on Sun, Sep 07, 2003 at 08:45 +0200: raoul.megelas wrote: > I have a copy error between hdd and a flashkey 1gig usb (easydisk) > on Current dated August 28. Here is in short: > > mount -t msdos /dev/da2s1 /flashkey > cp myfile /flashkey/ > diff myfile /flashkey/myfile > (ok). > could you try a fsync /flashkey/myfile before the umount? > umount /flashkey > > mount (flashkey) > diff myfile /flashkey/myfile > (Binary file differ)! > > It is not a flashkey disk error, it works on XP. > Note that this error occurs on FreeBSD 4.8 too. > > Please, can you tell me how to deal with that? > And in an other hand can you tell me how to obtain the exact map of the flashkey > to verify the writing on the disk. > Thanks in advance for this newbie question. > You're the second person that has reported corruption with USB umass > devices. I am interested in tracking down this problem, but it's a > bit difficult since I haven't seen it myself. > (I currently don't quite have a test bed box to play with, but I will > in the next week.) > John-Mark Gurney Voice: +1 415 225 5579 > "All that I will do, has been done, All that I have, has not." You have found the trick, fsync after cp works fine. Thanks very much. But why the fsync is not automatically done by umount on umass? (note) if you need to test against flashkey i can do that if you want.) raoul [EMAIL PROTECTED] ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "[EMAIL PROTECTED]"
usb flashkey error
Hello all, in a precedent message, i reported an error using a flashkey. I must add the following: as one can see in the dmesg below, the controller is NOT the ohci but uhci. The error occurs on writing not reading I tested the file written to the flashkey, without fsync and after unmount applied; The file looks garbage. In this case, as suggested by John-Mark Gurney, the fsync made the trick. Best regards. uhci0: port 0xbce0-0xbcff irq 11 at device 31.2 on pci0 usb0: 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 uhub1: Philips Semiconductors hub, class 9/0, rev 1.10/1.10, addr 2 uhub1: 4 ports with 4 removable, self powered umass0: GENERIC USB Mass Storage, rev 1.10/1.00, addr 3 GEOM: create disk da2 dp=0xc2714c50 da2 at umass-sim0 bus 0 target 0 lun 0 da2: Removable Direct Access SCSI-2 device da2: 1.000MB/s transfers da2: 1000MB (2048000 512 byte sectors: 64H 32S/T 1000C) ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "[EMAIL PROTECTED]"
re: usb flashkey
hello all, I tested the flashkey with and without fsync. Infortunately the result is the same in all cases: a random write fault for one byte at each time, repeated at random places. With a 32Mb (old model i think) flashkey, all is correct and repeated writes are ok. Reading operations are correct (a bad file is always bad for current and for XP. The flashkey runs quite well on XP (verifyed a big number of times on writing). errors occur at any place on the flashkey (msdos-sys) as attested by a partial copy of the flashkey done by dd: (bootmbr fats directory, and of file). Writing errors are not systematic, and sometimes all goes fine. At my sense, it looks like a time problem or as mentionned by Bruce Evans or an interrupt problem. Hope this can help. Best regards. raoul [EMAIL PROTECTED] ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "[EMAIL PROTECTED]"
