MSDOSFS_LARGE option -- problem solved
Hello, My problem with mounting a FAT32 80GB disk disappeared after I removed from my kernel config file option MSDOSFS_LARGE and replaced it with option MSDOSFS Thanks to those who responded to my earlier post. Brian ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
msdosfs fat32 disk size limit in FreeBSD?
Hello, Is there an upper limit to the size of a FAT32 file system in the FreeBSD msdosfs code? I put in an 80GB drive recently and there have been problems. There is no problem with small FAT32 file systems on floppies or flash memory cards. Any useful comments before I go back to the (working) 60GB drive configuration? Thanks, Brian ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: msdosfs fat32 disk size limit in FreeBSD?
Yeah, I already had MSDOSFS_LARGE turned on, and I realize that it's supposed to be an issue if you have bigger than 128GB drives. I'm running 6.0-CURRENT. I'll keep looking... Brian Kevin Kinsey wrote: Brian M. Kincaid wrote: Hello, Is there an upper limit to the size of a FAT32 file system in the FreeBSD msdosfs code? I put in an 80GB drive recently and there have been problems. There is no problem with small FAT32 file systems on floppies or flash memory cards. Any useful comments before I go back to the (working) 60GB drive configuration? Thanks, Brian IANAE, but I think there is; IIRC, though, it's 128 GB unless you have compiled MSDOSFS_LARGE* into your custom kernel, so I can't address your problem with an 80GB disk What system are you on (`uname -a`)? Kevin Kinsey *Or something like that ... check release notes on 5.3, again, that's if I recall correctly ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: msdosfs fat32 disk size limit in FreeBSD?
Maybe I should turn MSDOSFS_LARGE **OFF** ? I'll keep you posted. Brian Kevin Kinsey wrote: Brian M. Kincaid wrote: Hello, Is there an upper limit to the size of a FAT32 file system in the FreeBSD msdosfs code? I put in an 80GB drive recently and there have been problems. There is no problem with small FAT32 file systems on floppies or flash memory cards. Any useful comments before I go back to the (working) 60GB drive configuration? Thanks, Brian IANAE, but I think there is; IIRC, though, it's 128 GB unless you have compiled MSDOSFS_LARGE* into your custom kernel, so I can't address your problem with an 80GB disk What system are you on (`uname -a`)? Kevin Kinsey *Or something like that ... check release notes on 5.3, again, that's if I recall correctly ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
emergent msdosfs problems, errors
Hello FreeBSD Collective Consciousness, I run a dual-boot FreeBSD 6.0-Current/WinXP Pro system. The FreeBSD NTFS driver can't write files, and can only read files less than 2GB in size, so I have been using a FAT32 disk (Drive D:) mounted using mount_msdosfs successfully for several years for file transfer between the FreeBSD and WinXP personalities of my system. Just recently, after some hardware changes in my machine (new SATA disks for the FreeBSD personality) and rebuilding of world and kernel, the MSDOS file system has become unreliable, with directories and files mixed up, and find . broken with various error messages. Also, fsck_msdosfs complains about bad signatures in the boot block. After a clean reboot, doing find . on the FAT32 disk works without errors. Running tar to try to create a backup of the FAT32 disk fails, though, and after that find . returns errors find: fts_read: No such file or directory and files and directories on the FAT32 disk appear to be mixed up or corrupted. In the WinXP world, the FAT32 disk is just fine, thank you. All this is new behavior, things have been working for several years. I think the FreeBSD msdosfs driver is failing somehow. Any suggestions? Thanks, Brian ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: emergent msdosfs problems, errors
Hello again, Ah Hah! I noticed the following in the dmesg output: atapci0: Promise PDC20375 SATA150 controller port 0xdc00-0xdc7f,0xdca0-0xdcaf, 0xdcc0-0xdcff mem 0xff7c-0xff7d,0xff7ff000-0xff7f irq 3 at device 7. 0 on pci2 atapci0: failed: rid 0x20 is memory, requested 4 Can anyone tell me what the failed: message means? Thanks, Brian ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Dual booting w/ two disks
I have been running a dual boot system with Windows and FreeBSD on separate disks for several years. I use just the basic FreeBSD MBR boot program, installed using the procedure described in the Handbook. http://www.freebsd.org/doc/en_US.ISO8859-1/books/handbook/boot-blocks.html Windows XP needs to be on the first disk (Disk 0) and you can put FreeBSD on the other disk. Windows installation will clobber the FreeBSD boot block, so you need to write over it with the Handbook procedure. Brian ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Dual booting w/ two disks
Yup, Windows needs to be the first disk. gabriel wrote: In my case, freebsd is on the master and windows is on the slave, you mean that it should be the other way around? On Mon, 24 Jan 2005 08:45:44 -0800, Brian M. Kincaid [EMAIL PROTECTED] wrote: I have been running a dual boot system with Windows and FreeBSD on separate disks for several years. I use just the basic FreeBSD MBR boot program, installed using the procedure described in the Handbook. http://www.freebsd.org/doc/en_US.ISO8859-1/books/handbook/boot-blocks.html Windows XP needs to be on the first disk (Disk 0) and you can put FreeBSD on the other disk. Windows installation will clobber the FreeBSD boot block, so you need to write over it with the Handbook procedure. Brian ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Dual booting w/ two disks
Gabriel: What I would do is make sure that you can get Windows to boot up as the master disk before doing any further modifications to the boot blocks. If you get this far, then the FreeBSD Handbook procedure will handle the rest. If you can't get Windows to boot, there are several possible causes, and you need to use Google to address them. I have probably made every possible configuration mistake in setting up dual boot systems, and my recommendation is to take things one step at a time and verify that you haven't clobbered something. Assume nothing, trust no one, and always check! Brian ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Radeon 9800XT fails on FreeBSD with XFree86-4.4.0
Does anyone have a Radeon 9800XT graphics card working with FreeBSD? If so, what's the trick? Thanks, Brian ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Two NICs, two ISPs, how to configure interfaces and mail?
I have two NICs, connecting to two completely separate ISPs, with two different IP addresses and DNS names. I would like to find out what to put into rc.conf to configure the two interfaces, and how to arrange for localhost to use one of the interfaces and mail (postfix) to use the other. Thanks in advance, Brian ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
[no subject]
---BeginMessage--- Hi, You are listed as the maintainer of the ports /usr/ports/security/avmailgate. The Makefile lacks a COMMENT= line, and breaks the make index function. The fix is trivial, but you have to do it. Thanks, Brian -- Brian M. Kincaid PGP Key: http://wwwkeys.pgp.net:11371/pks/lookup?op=getsearch=0x33656401 ---End Message--- Brian M. Kincaid PGP Key: http://wwwkeys.pgp.net:11371/pks/lookup?op=getsearch=0x33656401 ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: ATAPI Zip Drive. Please Help!
Hi,
1) Google search iomega zip freebsd
2) pick SCSI Iomega ZIP drives under FreeBSD link
3) read page
4) use slice 4 as indicated
Good luck,
Brian
In message [EMAIL PROTECTED], Bryan Cassidy wr
ites:
OK This is really annoying.. I know I've already asked this questions
before but got nothing and really want to get this working so maybe
someone could help me out here. I am trying to mount my zip drive in
FreeBSD 4.6.2 I am having NO luck what so ever. Here is the output
from dmesg about my Zip Drive
afd0: 239MB IOMEGA ZIP 250 ATAPI [239/64/32] at ata1-slave PIO3
I have tried almost everything I can think of off the top of my head
to mount this damn thing but get this error everytime
mount_msdos: /dev/afd0: Invalid argument
YES! I have tried /dev/afd0a b c d e f and so on. I get
nothing.lol. Well, maybe someone wouldn't mind helping me out here
cause so far this is the only hardware problem I am having.
-
E-Mail: Bryan Cassidy [EMAIL PROTECTED]
Gaim: bsdsys
Yahoo Messenger: bsdsys
Screenshot ~~~
http://deskmod.org/?state=viewskin_id=18160
I have put alot of time in setting up my mail filters. Please do not
simply Reply-To: Bryan Cassidy [EMAIL PROTECTED] unless
stated to do so. Please reply to my e-mails using the appropriate
mailing lists.
To Unsubscribe: send mail to [EMAIL PROTECTED]
with unsubscribe freebsd-questions in the body of the message
--
Brian M. Kincaid
PGP Key: http://wwwkeys.pgp.net:11371/pks/lookup?op=getsearch=0x33656401
To Unsubscribe: send mail to [EMAIL PROTECTED]
with unsubscribe freebsd-questions in the body of the message
Re: A curious dmesg output entry
Hi, Have a look at the PCI vendor list at: http://www.yourvote.com/pci/ Your card is made by VIA Technologies Inc 1045 Mission Court Fremont CA 94539 510-683-3300 Chip Number: VT82C686A Description: ACPI Power Management Controller Brian In message [EMAIL PROTECTED], Wayne Lubin wr ites: Hi, I have this line in my dmesg output pci0: unknown card (vendor=0x1106, dev=0x3057) at 7.4 but the only cards that I have is one ethernet pci card, and my video card that is in the AGP slot. And they are being properly detected. Can this unknown card be some functionality built into the mother bord that wants to access the pci buss? Because all of my pci cards are physicaly plugged into the pci slots are accounted for. Thanks, Wayne __ Do you Yahoo!? Faith Hill - Exclusive Performances, Videos More http://faith.yahoo.com To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-questions in the body of the message -- Brian M. Kincaid PGP Key: http://wwwkeys.pgp.net:11371/pks/lookup?op=getsearch=0x33656401 To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-questions in the body of the message
