Re: Driver Floppy implementation (Re: make release breakage -dokern.sh patch 2)
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 compilation directories, did you?). I've done "cd /usr/src/modules; make clean" under -current buildtree to remove them. You say that I should always run "make clean" under all source code directory since somebody causes a mistake to use /usr/src for object? Maybe it's O.K., but before I'm doing, the committer who breaks the policy should be blamed :-) BTW, I've not received your email; are you busy working? -- - Makoto `MAR' MATSUSHITA To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: Driver Floppy implementation (Re: make release breakage - dokern.sh patch 2)
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 morning. I'm Sorry. I wanted to test it on my machine with Celeron 300MHz. 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 compilation directories, did you?). I've done "cd /usr/src/modules; make clean" under -current buildtree to remove them. You say that I should always run "make clean" under all source code directory since somebody causes a mistake to use /usr/src for object? Maybe it's O.K., but before I'm doing, the committer who breaks the policy should be blamed :-) I understood the situation. I'll look into the Makefile's under src/sys. -- Tatsumi Hosokawa [EMAIL PROTECTED] http://www.sm.rim.or.jp/~hosokawa/ To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: Driver Floppy implementation (Re: make release breakage -dokern.sh patch 2)
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. I'll look into the Makefile's hosokawa under src/sys. Uncutted logfile of Nov/01/2000 may also helps you. You can fetch it from URL:ftp://current.jp.FreeBSD.org/pub/FreeBSD/snapshots/i386/log/. However, this problem (use /usr/src/sys/modules for compilation) is disappeared already according to the logfile of Nov/02/2000. -- - Makoto `MAR' MATSUSHITA go to lunch right now... To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: Driver Floppy implementation (Re: make release breakage -dokern.sh patch 2)
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 === 3dfx Warning: Object directory not changed from original /usr/src/sys/modules/3dfx Maybe it doesn't occur before, and today's make release is also failed. cd ../../modules env MAKEOBJDIRPREFIX=/usr/src/sys/compile/BOOTMFS/modules KMDDIR= make install === 3dfx install -c -o root -g wheel -m 555 3dfx.ko /R/stage/kernels install: 3dfx.ko: No such file or directory -- - Makoto `MAR' MATSUSHITA To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: Driver Floppy implementation (Re: make release breakage -dokern.sh patch 2)
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 compilation.
-- -
Makoto `MAR' MATSUSHITA
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message
Re: Driver Floppy implementation (Re: make release breakage -dokern.sh patch 2)
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 moment as I don't have a STABLE box (will have once the first RC comes out of JKH factories). Nick On Mon, 30 Oct 2000, Takanori Watanabe wrote: 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 also more installation devices. Just FYI: If usb itself is module-ifed, USB ether modules cannot be load until MODULE_DEPEND,MODULE_VERSION is defined. Takanori Watanabe a href="http://www.planet.sci.kobe-u.ac.jp/~takawata/key.html" Public Key/a Key fingerprint = 2C 51 E2 78 2C E1 C5 2D 0F F1 20 A3 11 3A 62 2A -- Qube Software, Ltd. Private: [EMAIL PROTECTED] [EMAIL PROTECTED] [EMAIL PROTECTED] http://www.qubesoft.com/ http://www.etla.net/~n_hibma/ To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: Driver Floppy implementation (Re: make release breakage - dokern.sh patch 2)
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 moment as I don't have a STABLE box (will have once the first RC comes out of JKH factories). I usually do the following: # kldload usb (probes USB controllers) # kldload miibus # kldload if_aue # usbd -f /dev/usb0 If the device has already been plugged in, starting usbd will cause it to be probed/attached by the aue driver. If not, it will be detected when it's plugged in later. -Bill To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: Driver Floppy implementation (Re: make release breakage - dokern.sh patch 2)
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 "make release" takes about 8 hours on my machine. Anyway, I'll fix this bug as soon as possible. -- Tatsumi Hosokawa [EMAIL PROTECTED] http://www.sm.rim.or.jp/~hosokawa/ To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: Driver Floppy implementation (Re: make release breakage - dokern.sh patch 2)
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 enviroment. I'm debugging this problem, but it'll take hours and hours because testing "make release" takes about 8 hours on my machine. Anyway, I'll fix this bug as soon as possible. Hmm. Binaries on current.freebsd.org seems to be successfuly compiled. I'm not guilty :-). % gzip kern-20001028.flp kern-20001101.flp (got from current.freebsd.org) % ls -l kern-20001* -rw-r--r-- 1 hosokawa hosokawa 1330551 11/ 2 13:53 kern-20001028.flp.gz -rw-r--r-- 1 hosokawa hosokawa 1245853 11/ 2 13:50 kern-20001101.flp.gz Maybe it's current.jp.freebsd.org's problem and I'll talk with the administrator of this host. -- Tatsumi Hosokawa [EMAIL PROTECTED] http://www.sm.rim.or.jp/~hosokawa/ To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: Driver Floppy implementation (Re: make release breakage - dokern.sh patch 2)
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 also more installation devices. Just FYI: If usb itself is module-ifed, USB ether modules cannot be load until MODULE_DEPEND,MODULE_VERSION is defined. Takanori Watanabe a href="http://www.planet.sci.kobe-u.ac.jp/~takawata/key.html" Public Key/a Key fingerprint = 2C 51 E2 78 2C E1 C5 2D 0F F1 20 A3 11 3A 62 2A To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Driver Floppy implementation (Re: make release breakage - dokern.sh patch 2)
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 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 also more installation devices. I've put the patche and the binary images of *.flp at, http://people.freebsd.org/~hosokawa/driver-floppy/ I've tested these floppies on my machine with Intel PRO/100+ fxp network card. Sysinstall loads if_fxp.ko from mfsroot.flp, and listed it as network installation media (Alt-F2 shows debug messages). -- Tatsumi Hosokawa [EMAIL PROTECTED] http://www.sm.rim.or.jp/~hosokawa/ To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
