hosokawa Maybe it's current.jp.freebsd.org's problem
I don't think so. It's a mismatch that all object files are created
under /usr/src/modules but make install assumes that these are under
(maybe) /usr/obj. Maybe it's a fault of some Makefiles (sorry I dunno
who change the policy of module
At Fri, 03 Nov 2000 12:05:46 +0900,
Makoto MATSUSHITA [EMAIL PROTECTED] wrote:
BTW, I've not received your email; are you busy working?
Last night, I tested "make release" on my machine, and failed twice
because of unloaded vn driver (this causes last trouble). It
successfly finished this
hosokawa Last night, I tested "make release" on my machine, and
hosokawa failed twice because of unloaded vn driver (this causes last
hosokawa trouble). It successfly finished this morning. I'm Sorry.
'vn' device is a great pitfall of "make release" :-)
hosokawa I understood the situation.
matusita However, this problem (use /usr/src/sys/modules for compilation) is
matusita disappeared already according to the logfile of Nov/02/2000.
Hmm, sorry, it is not yet fixed.
cd ../../modules env MAKEOBJDIRPREFIX=/usr/src/sys/compile/BOOTMFS/modules KMODIR=
make obj all
=== 3dfx
===
Forget to note:
matusita Warning: Object directory not changed from original /usr/src/sys/modules/3dfx
dinosaur % pwd
${CHROOT_DIRECTORY_FOR_CURRENT}/usr/src/sys/modules
dinosaur % ls */*.o
3dfx/setdef0.o 3dfx/setdef1.o 3dfx/tdfx_pci.o
Only 3dfx module uses /usr/src/sys/modules for
I'm not sure whether the problem of loading secondary usb modules is a
problem in 4.x but it is easy to try.
Boot a machine without usb support compiled in. after login, kldload
usb, then the miibus and then the if_aue modules. If that works, you
should be ok.
I cannot test this as at the
I'm not sure whether the problem of loading secondary usb modules is a
problem in 4.x but it is easy to try.
Boot a machine without usb support compiled in. after login, kldload
usb, then the miibus and then the if_aue modules. If that works, you
should be ok.
I cannot test this as at the
My driver-floppy patch broke "make release" on current.jp.freebsd.org
(ftp://current.jp.FreeBSD.org/pub/FreeBSD/snapshots/i3865.0-CURRENT-20001101-JPSNAP.log).
Of course "make boot.flp" works very well on my enviroment.
I'm debugging this problem, but it'll take hours and hours because
testing
At Thu, 02 Nov 2000 10:34:03 +0900,
Tatsumi Hosokawa [EMAIL PROTECTED] wrote:
My driver-floppy patch broke "make release" on current.jp.freebsd.org
(ftp://current.jp.FreeBSD.org/pub/FreeBSD/snapshots/i3865.0-CURRENT-20001101-JPSNAP.log).
Of course "make boot.flp" works very well on my
In message [EMAIL PROTECTED], Tatsumi Hosokawa さんいわく:
I moved PCI/PCCARD/USB if_xx.ko driver to mfsroot.flp, and I've got
100KB of free blocks in the first floppy. If we move more drivers to
mfsroot.flp or coming drivers.flp, we can get not only free blocks in
the first floppy, but
Hi!
In "make release breakage" discussion, I said that I'll write a patch
to load kernel module from sysinstall to get more free space in the
first floppy. This is my implementation. I'll commit this patch to
-current if there's no objection.
I moved PCI/PCCARD/USB if_xx.ko driver to
11 matches
Mail list logo
