Re: REPOST - Installation Bug - All available versions hang on install
> What makes this system unusual is that it is legacy free and thereby it doesn't have a keyboard controller at all. The system is hanging on boot looking for the keyboard controller itself and not finding one, since it doesn't exist. If someone else is familar enough with the workaround for this issue, and can post it, I could make the changes and build an ISO for you, probably, though my free time for such at the moment is limited. Thank you David. As you surmised, my BIOS does not have the keyboard emulation mode you mention. Before I ask you to build the kernel for me, I'll try to round up a more convertional computer and try to do it myself. Based upon this (and the other) reply, the key seems to be to compile without any legacy keyboard I/O, to prevent the hang. Let me know if your developers have any further suggestions or if anyone has specific tips to help a newbie achive the kernel build. Thor _ Winterize your home with tips from MSN House & Home. http://special.msn.com/home/warmhome.armx ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-hackers To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: REPOST - Installation Bug - All available versions hang on install
> FreeBSD hangs without errors early in the install process on my computer. > What makes this system unusual is that it > is "legacy free" which means it has none of the traditional I/O ports (no > serial, parallel, PS/2 or even floppy interface). All I/O is via one of > the five USB ports on the case. A friend of mine recently ran into this problem on an embeded system. The solution for him on 5.x was to enter the following at the loader prompt to disable the keyboard and floppy probes because they tend to hang: hint.atkbdc.0.disabled=1 hint.atkbd.0.disabled=1 hint.fdc.0.disabled=1 Unfortnaly, you can't do that since you don't have a serial port. The one hack I can think of would be to try to PXE boot the CD image from another machine. You could then modify the loader.conf on the pxe image to force these settings. These drivers are broken and need to be fixed since I'm sure this problem will only become more common. Thanks Brooks. I'll be trying to find a "normal" computer to install FreeBSD. Hopefully with it, I can try to implement some of the suggestions being offered - including a PXE boot. I found the LOADER.CNF file on the CD. If I were to burn the CD to a CDRW, could I edit that file manually and then boot from the CD? Thor _ Cell phone switch rules are taking effect find out more here. http://special.msn.com/msnbc/consumeradvocate.armx ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-hackers To unsubscribe, send any mail to "[EMAIL PROTECTED]"
FreeBSD VFS System?
Are there any good web resources or books on the VFS system that the FreeBSD kernel uses? I'm guessing it might have originated from the 4.4BSD(?) interface. I've been attempting to read through the source code for different system calls (ie mkdir, rmdir, mount/umount) and haven't been able to get very far because of the substantial layers of indirection involved. For this reason I was looking at picking apart the different subsystems involved and was wondering if there was anything any more annotated then the source code itself. Thanks in advance. -- Ryan "leadZERO" Sommers [EMAIL PROTECTED] ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-hackers To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: REPOST - Installation Bug - All available versions hang on install
On Tue, Dec 16, 2003 at 01:01:37AM -0800, Thor Anderson wrote: > >> FreeBSD hangs without errors early in the install process on my > >computer. > > >> What makes this system unusual is that it > >> is "legacy free" which means it has none of the traditional I/O ports > >(no > >> serial, parallel, PS/2 or even floppy interface). All I/O is via one of > >> the five USB ports on the case. > > > >A friend of mine recently ran into this problem on an embeded system. > >The solution for him on 5.x was to enter the following at the loader > >prompt to disable the keyboard and floppy probes because they tend to > >hang: > > > >hint.atkbdc.0.disabled=1 > >hint.atkbd.0.disabled=1 > >hint.fdc.0.disabled=1 > > > >Unfortnaly, you can't do that since you don't have a serial port. The > >one hack I can think of would be to try to PXE boot the CD image from > >another machine. You could then modify the loader.conf on the pxe image > >to force these settings. > > > >These drivers are broken and need to be fixed since I'm sure this > >problem will only become more common. > > Thanks Brooks. > > I'll be trying to find a "normal" computer to install FreeBSD. Hopefully > with it, I can try to implement some of the suggestions being offered - > including a PXE boot. If you've got a linux box, it should be able to do it as well. > I found the LOADER.CNF file on the CD. If I were to burn the CD to a CDRW, > could I edit that file manually and then boot from the CD? With the right tools, you could probably modify the ISO that way, but you can't just copy the files because you need to boot stuff. -- Brooks -- Any statement of the form "X is the one, true Y" is FALSE. PGP fingerprint 655D 519C 26A7 82E7 2529 9BF0 5D8E 8BE9 F238 1AD4 pgp0.pgp Description: PGP signature
Re: FreeBSD VFS System?
On Tue, Dec 16, 2003 at 11:41:33AM -0600, Ryan Sommers wrote: > Are there any good web resources or books on the VFS system that the > FreeBSD kernel uses? I'm guessing it might have originated from the "Recent Filesystem Optimisations in FreeBSD (2002)" Ian Dowse, David Malone http://citeseer.nj.nec.com/dowse02recent.html "The Design and Implementation of the 4.4 BSD Operating System" http://www.aw-bc.com/catalog/academic/product/0,4096,0201549794-TOC,00.html -- Craig Rodrigues http://crodrigues.org [EMAIL PROTECTED] ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-hackers To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: REPOST - Installation Bug - All available versions hang on install
At 17:07 14/12/2003 -0800, Brooks Davis wrote: On Sun, Dec 14, 2003 at 12:57:34PM -0800, Thor Anderson wrote: > The computer is able to boot other operating systems from CD. Testing > shows Microsoft as well as Fedora project Linux boot and install properly. hint.atkbdc.0.disabled=1 hint.atkbd.0.disabled=1 hint.fdc.0.disabled=1 Unfortnaly, you can't do that since you don't have a serial port. The one hack I can think of would be to try to PXE boot the CD image from another machine. You could then modify the loader.conf on the pxe image to force these settings. Given that the system can boot Linux, one option is to install linux, build a minimal FreeBSD filesystem, dd it to the drive, and reboot. If you want to be clever, you could even create a filesystem in a md root, and then run sysinstall over ssh. Colin Percival ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-hackers To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Broadcom 440x
I saw that you had posted a message regarding the Broadcom 440x drivers. I was just wondering if you ever found a driver and if so where at? Thanks for any info Thomas Knight [EMAIL PROTECTED] ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-hackers To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Programmatically test for a DVD drive
I'm trying to figure out the best way to programmatically test to see if a disc device is a DVD device. That is, how can I tell the difference between a CD-[ROM|R|RW] and a DVD-[ROM|R|RW]? Is there a set method for doing this, or should I just try to execute a DVD ioctl, and test to see if it succeeds? Thanks. Joe -- Joe Marcus Clarke FreeBSD GNOME Team :: [EMAIL PROTECTED] FreeNode / #freebsd-gnome http://www.FreeBSD.org/gnome signature.asc Description: This is a digitally signed message part
patch: portable dirhash
can somebody please review/commit this to freebsd? it is most of the
differences to permit openbsd to use the code. it should not change the
code in any functional way.
Index: ufs_dirhash.c
===
RCS file: /home/ncvs/src/sys/ufs/ufs/ufs_dirhash.c,v
retrieving revision 1.17
diff -u -r1.17 ufs_dirhash.c
--- ufs_dirhash.c 11 Jun 2003 06:34:30 - 1.17
+++ ufs_dirhash.c 17 Dec 2003 03:04:58 -
@@ -89,13 +89,28 @@
static doff_t ufsdirhash_getprev(struct direct *dp, doff_t offset);
static int ufsdirhash_recycle(int wanted);
-static uma_zone_t ufsdirhash_zone;
-
/* Dirhash list; recently-used entries are near the tail. */
static TAILQ_HEAD(, dirhash) ufsdirhash_list;
/* Protects: ufsdirhash_list, `dh_list' field, ufs_dirhashmem. */
+#ifdef __FreeBSD__
+static uma_zone_t ufsdirhash_zone;
+#define DIRHASH_ALLOC() uma_zalloc(ufsdirhash_zone, M_WAITOK)
+#define DIRHASH_FREE(v) uma_zfree(ufsdirhash_zone, v)
+
static struct mtx ufsdirhash_mtx;
+#define LOCK(l) mtx_lock(l)
+#define UNLOCK(l) mtx_unlock(l)
+#else
+struct pool ufsdirhash_pool;
+#define DIRHASH_ALLOC() pool_get(&ufsdirhash_pool, PR_WAITOK)
+#define DIRHASH_FREE(v) pool_put(&ufsdirhash_pool, v)
+
+struct rwlock ufsdirhash_mtx;
+#define LOCK(l) rw_enter_write(l, curproc)
+#define UNLOCK(l) rw_exit_write(l)
+#define mtx_assert(l, f)/* nothing */
+#endif
/*
* Locking order:
@@ -156,9 +171,9 @@
memreqd = sizeof(*dh) + narrays * sizeof(*dh->dh_hash) +
narrays * DH_NBLKOFF * sizeof(**dh->dh_hash) +
nblocks * sizeof(*dh->dh_blkfree);
- mtx_lock(&ufsdirhash_mtx);
+ LOCK(&ufsdirhash_mtx);
if (memreqd + ufs_dirhashmem > ufs_dirhashmaxmem) {
- mtx_unlock(&ufsdirhash_mtx);
+ UNLOCK(&ufsdirhash_mtx);
if (memreqd > ufs_dirhashmaxmem / 2)
return (-1);
@@ -168,7 +183,7 @@
/* Enough was freed, and ufsdirhash_mtx has been locked. */
}
ufs_dirhashmem += memreqd;
- mtx_unlock(&ufsdirhash_mtx);
+ UNLOCK(&ufsdirhash_mtx);
/*
* Use non-blocking mallocs so that we will revert to a linear
@@ -176,9 +191,9 @@
*/
MALLOC(dh, struct dirhash *, sizeof *dh, M_DIRHASH, M_NOWAIT | M_ZERO);
if (dh == NULL) {
- mtx_lock(&ufsdirhash_mtx);
+ LOCK(&ufsdirhash_mtx);
ufs_dirhashmem -= memreqd;
- mtx_unlock(&ufsdirhash_mtx);
+ UNLOCK(&ufsdirhash_mtx);
return (-1);
}
MALLOC(dh->dh_hash, doff_t **, narrays * sizeof(dh->dh_hash[0]),
@@ -188,15 +203,18 @@
if (dh->dh_hash == NULL || dh->dh_blkfree == NULL)
goto fail;
for (i = 0; i < narrays; i++) {
- if ((dh->dh_hash[i] = uma_zalloc(ufsdirhash_zone,
- M_WAITOK)) == NULL)
+ if ((dh->dh_hash[i] = DIRHASH_ALLOC()) == NULL)
goto fail;
for (j = 0; j < DH_NBLKOFF; j++)
dh->dh_hash[i][j] = DIRHASH_EMPTY;
}
/* Initialise the hash table and block statistics. */
+#ifdef __FreeBSD__
mtx_init(&dh->dh_mtx, "dirhash", NULL, MTX_DEF);
+#else
+ rw_init(&dh->dh_mtx);
+#endif
dh->dh_narrays = narrays;
dh->dh_hlen = nslots;
dh->dh_nblk = nblocks;
@@ -244,26 +262,26 @@
if (bp != NULL)
brelse(bp);
- mtx_lock(&ufsdirhash_mtx);
+ LOCK(&ufsdirhash_mtx);
TAILQ_INSERT_TAIL(&ufsdirhash_list, dh, dh_list);
dh->dh_onlist = 1;
- mtx_unlock(&ufsdirhash_mtx);
+ UNLOCK(&ufsdirhash_mtx);
return (0);
fail:
if (dh->dh_hash != NULL) {
for (i = 0; i < narrays; i++)
if (dh->dh_hash[i] != NULL)
- uma_zfree(ufsdirhash_zone, dh->dh_hash[i]);
+ DIRHASH_FREE(dh->dh_hash[i]);
FREE(dh->dh_hash, M_DIRHASH);
}
if (dh->dh_blkfree != NULL)
FREE(dh->dh_blkfree, M_DIRHASH);
FREE(dh, M_DIRHASH);
ip->i_dirhash = NULL;
- mtx_lock(&ufsdirhash_mtx);
+ LOCK(&ufsdirhash_mtx);
ufs_dirhashmem -= memreqd;
- mtx_unlock(&ufsdirhash_mtx);
+ UNLOCK(&ufsdirhash_mtx);
return (-1);
}
@@ -278,32 +296,34 @@
if ((dh = ip->i_dirhash) == NULL)
return;
- mtx_lock(&ufsdirhash_mtx);
- mtx_lock(&dh->dh_mtx);
+ LOCK(&ufsdirhash_mtx);
+ LOCK(&dh->dh_mtx);
if (dh->dh_onlist)
TAILQ_REMOVE(&ufsdirhash_list, dh, dh_list);
- mtx_unlock(&dh->dh_mtx);
- mtx_unlock(&ufsdirhash_mtx);
+ UNLOCK(&dh->dh_mtx);
+ U
Re: puc/sio driver - receives but doesn't send
Hi, Just to follow up on this item ... I never did get the other card working. I checked solder joints under a magnifying glass, changed card slots, tried every serial cable configuration known (which is a lot), and still no joy. Finally, getting tired of trying to make the other card work, I bought a different brand of card (Moxa CP-114) via ebay for what I thought was a good price. I just tested it out and it works just fine. Thanks for all the suggestions on the other card - I suspect it was just a bad card as others have reported it works. I'll see if I can return it to where I bought it. -Brian -- Brian Dean [EMAIL PROTECTED] [EMAIL PROTECTED] ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-hackers To unsubscribe, send any mail to "[EMAIL PROTECTED]"
