Search results

yes.. finally it works tried some other sticks 1st which got me to this point. camcontrol doesnt work cause pass0 disabled in this kernconf but device came up as /dev/da0s1, 1st time it gave me a slice file -s da0s1 gave good info, then mount_msdosfs /dev/da0s1 /mnt which works. wow..what are...

ok..the stick works fine in all windows machines, yes its msdosfs, but last night after posting i noticed the camcontrol devlist see's this as da0 and pass0, nothing in other message's that states the device as pass0. so after reading other forum users with similar problems, i'm think'n there's...

ok..wow had some errors while tryin to rebuild kernel: note to self " don't try to master vi in any conf file". ok.. device comes up as da0 now, dmesg is: da0 at umass-sim0 bus 0 lun 0 and the other 2 identifying lines, /var/log/messages: umass0:BBB reset failed, IOERROR then some bulk_in and...

ok.. 1: 6.0-release-p5 2: i'd have to retype everything from other computer, its not online yet cause the modem drivers are on that dam usb stick.. hahaha the linux drivers didn't come with the cd. 3: yes, your right, my custom kernel config has next line blocked out # device da # Direct...

ah..tail /var/log/messages tells me its pass0 at umass0 and also its a scsi-2 device, it still comes up as pass0 not any da0, cam.1 already present in kernel, and any mount command comes up with Block device required...

ok..got freeBSD 6 on another machine, this device comes up as pass0 can't seem to find a pass.ko to load into kernel. Camcontrol sees it and says unit is ready, mount_msdosfs /dev/pass0 /mnt comes up with Block device required. Cant'seem to find out a fix for that yet, thus the post. Or do i...