Return to BSD News archive
Path: euryale.cc.adfa.oz.au!newshost.anu.edu.au!harbinger.cc.monash.edu.au!news.rmit.EDU.AU!news.unimelb.EDU.AU!munnari.OZ.AU!news.hawaii.edu!ames!agate!howland.reston.ans.net!newsxfer.itd.umich.edu!news.mathworks.com!tank.news.pipex.net!pipex!usenet1.news.uk.psi.net!uknet!usenet2.news.uk.psi.net!uknet!dispatch.news.demon.net!demon!jraynard.demon.co.uk!not-for-mail From: james@jraynard.demon.co.uk (James Raynard) Newsgroups: comp.unix.bsd.freebsd.misc Subject: Re: 2.2-current /sys/vm/vm_fault.c Date: 7 Jun 1996 16:49:41 -0000 Organization: A FreeBSD Box Lines: 66 Message-ID: <4p9mj5$1tm@jraynard.demon.co.uk> References: <4p453i$k58@news.clinet.fi> NNTP-Posting-Host: localhost.demon.co.uk X-NNTP-Posting-Host: jraynard.demon.co.uk In article <4p453i$k58@news.clinet.fi>, Mika Ruohotie <mickey@zetor.clinet.fi> wrote: > >the said file seems to be really broken... anyone got over it? the >file i'm talking about is the last one i've seen... it got updated >during last weekend time, i forgot the exact dates and am not able to >check right now, but anyway... > >i wish i could get my kernel to compile... I haven't seen any problems with this file, and I've been re-compiling -current every day for at least the last two weeks. Here's the latest version Id:- $Id: vm_fault.c,v 1.48 1996/06/01 20:50:57 dyson Exp $ >also, i have probs with hitachi 4x ide cdrom... it's connected into >gigabyte pentium board, secondary ide, only drive... > >as far as i know the kernel configuration is right, i have both ATAPI >lines, and the device line, and the secondary ide line, but when i boot >the drive is not found... > >machine does spend time looking for it while it probes the secondary ide, >i was wondering if anyone else has probs with it... > >and, also, i compiled the kernel with psm0, but again the probing fails, >it's not found from the 0x60 (was this the address, i have a bad memory)... > >*shrug* > >any of those work for someone? what am i doing wrong? I've seen them being discussed on the mailing list (I didn't follow the discussions as I don't have the hardware in question, sorry). You really should subscribe to the -current mailing list if you're running -current, as it's the only way to keep in touch with what's happening there. And if you have any questions or problems, it's the best place to find people who can help. >(been running freebsd from version 1.1.5.1 so i didnt just start, but >wont claim i'm a total pro yet, mostly i lack the c-knowledge) OK, you don't need to be a C wizard, but you do need a little patience for the times when -current misbehaves slightly (which, like all code in the process of development, it does now and again). Maybe if you try again in a few days things will work better for you - I won't recommend right now as a lot of VM changes have just gone in and there are still one or two bugs being squeezed out, but I think they should be gone in a couple of days. If you want to have fairly up-to-date code, but not have too much grief, perhaps the "snapshot" releases may be the answer? Especially as they're now available on CD. >question, last time i got my kernel all compiled, like a month ago, the >adaptec pci code was broken, so i couldnt use it, does it work now? Yep, it works fine for me with a 2940. -- James Raynard, Edinburgh, Scotland | http://freefall.freebsd.org/~jraynard/ james@jraynard.demon.co.uk | jraynard@freebsd.org