From owner-freebsd-current@FreeBSD.ORG Mon May 9 18:28:22 2005 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id CD21816A500 for ; Mon, 9 May 2005 18:28:19 +0000 (GMT) Received: from vms048pub.verizon.net (vms048pub.verizon.net [206.46.252.48]) by mx1.FreeBSD.org (Postfix) with ESMTP id 6C5AC43D69 for ; Mon, 9 May 2005 18:28:19 +0000 (GMT) (envelope-from david.freebsd@verizon.net) Received: from OSTest ([68.161.118.114])0.04 <0IG8002WYJB1EF11@vms048.mailsrvcs.net> for freebsd-current@freebsd.org; Mon, 09 May 2005 13:28:19 -0500 (CDT) Date: Mon, 09 May 2005 13:30:38 -0400 From: David Gurvich In-reply-to: <20050509164825.GA24749@fit.vutbr.cz> To: freebsd-current@freebsd.org Message-id: <200505091330.38204.david.freebsd@verizon.net> MIME-version: 1.0 Content-type: text/plain; charset=iso-8859-1 Content-transfer-encoding: 7bit Content-disposition: inline References: <200505081828.08055.david.freebsd@verizon.net> <20050509164825.GA24749@fit.vutbr.cz> User-Agent: KMail/1.8 Subject: Re: Using nvidia-driver with 6-x/CURRENT X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 09 May 2005 18:28:22 -0000 If you use burncd instead of cdrecord there is no need for atapicam in the kernel or as a module. It appears you are only using for your CD drives. For simple burning, burncd is enough. On Monday 09 May 2005 12:48, Rudolf Cejka wrote: > David Gurvich wrote (2005/05/08): > > I was able to install v.7174 from the port after modifying nv-freebsd.h. > > This consisted of commenting out the portion where an error is given if > > the freebsd version is greater than 6. > > Hello, thanks for the information. I tried today's current with the new > nvidia driver and here are my first rough experiences: > > - I adjusted Makefile and distinfo from 6113 to 7174, then removed all > patches for 6113 in directory files and put here just one patch for > nv-freebsd.h, which removes above mentioned error. There seems to be > needed more adjustments for the port, but wow - I'm able after very > long time with my NVidia FX5200 to switch between graphics and text mode > again - great. > > - However when updating to the todays -current, I had to disable atapicam > from my kernel, because it stopped my system from booting. It hanged > after acd1 message - here are the last booting lines: > ... > sym0: <875> port 0xd000-0xd0ff mem > 0xfbefec00-0xfbefecff,0xfbefd000-0xfbefdfff irq 5 at device 9.0 on pci2 > sym0: Symbios NVRAM, ID 7, Fast-20, SE, parity checking > sym0: open drain IRQ line driver, using on-chip SRAM > sym0: using LOAD/STORE-based firmware. > sym0: [GIANT-LOCKED] > ... > Timecounters tick every 1.000 msec > IPsec: Initialized Security Association Processing. > ad0: 76319MB at ata0-master UDMA100 > acd0: CDRW at ata1-master UDMA33 > acd1: CDROM at ata1-slave UDMA33 > > When I removed SCSI controller from my computer, I was able to boot > the kernel again, but it paniced shortly. However removing atapicam > from kernel configuration seems to be sufficient. In kernel without > atapicam, kldload atapicam seems that it does nothing, kldunload atapicam > panics the system with current process = 33 (swi2: cambio).