From geo at pulsar.bg Thu May 1 09:39:56 2008 From: geo at pulsar.bg (Georgi Iovchev) Date: Thu May 1 09:40:03 2008 Subject: is there driver for (Bearlake) HECI Controller for releng_7 (or 7_0_0) Message-ID: <422521026.20080501122436@pulsar.bg> Hello lists Intel G33 motherboard (Intel DG33FB) with FreeBSD 7 AMD64 (7.0-RELEASE-p1) one thing is missing: [root@asterisk ~]# pciconf -lv | grep -A3 none none0@pci0:0:3:0: class=0x078000 card=0x50448086 chip=0x29c48086 rev=0x02 hdr=0x00 vendor = 'Intel Corporation' device = '(Bearlake) HECI Controller' class = simple comms Actually I dont know if I really need this (machine will be used for asterisk voip solution), but for completeness is there a driver for this piece of hardware? 10x in advance From shaun.bsd at gmail.com Thu May 1 18:02:37 2008 From: shaun.bsd at gmail.com (Shaun Sabo) Date: Thu May 1 18:02:41 2008 Subject: FreeBSD 7.0 SATA Controller Message-ID: Im trying to install FreeBSD 7.0 on a Dell XPS 600 desktop machine and im having a lot of trouble with this. First I could not use USB keyboards with the installer program (which is fine, i dont mind switching to PS2). then once i got into the sysinstaller it does not detect my Hard Disks. i also tried installing an old 6.2 cd that i had sitting around and remaking world and kernel but when i installed the kernel and restarted to go into single user mode the system could not mount the root filesystem. the motherboard im using is a nvidia nforce4 with Serial ATA hard disks. Does anyone know how to get FreeBSD 7.0 to recognize my hard drives? From koitsu at freebsd.org Thu May 1 18:23:26 2008 From: koitsu at freebsd.org (Jeremy Chadwick) Date: Thu May 1 18:23:28 2008 Subject: FreeBSD 7.0 SATA Controller In-Reply-To: References: Message-ID: <20080501182325.GA62281@eos.sc1.parodius.com> On Thu, May 01, 2008 at 01:34:53PM -0400, Shaun Sabo wrote: > Im trying to install FreeBSD 7.0 on a Dell XPS 600 desktop machine and im > having a lot of trouble with this. First I could not use USB keyboards with > the installer program (which is fine, i dont mind switching to PS2). then > once i got into the sysinstaller it does not detect my Hard Disks. i also > tried installing an old 6.2 cd that i had sitting around and remaking world > and kernel but when i installed the kernel and restarted to go into single > user mode the system could not mount the root filesystem. the motherboard im > using is a nvidia nforce4 with Serial ATA hard disks. Does anyone know how > to get FreeBSD 7.0 to recognize my hard drives? Re: USB keyboard: USB support on FreeBSD is spotty. That said, I've never run into problems getting FreeBSD to detect and use a USB keyboard (other USB devices are a different story). You'd need to provide some dmesg(8) output to verify, but I know that's going to be difficult until you can get FreeBSD installed. Re: SATA disks: I can assure you that FreeBSD works fine with SATA disks connected to an nForce 4 chipset, because I've used them myself with no issue. Chances are there's a BIOS setting that's causing mayhem, or you may be using a RAID array of some sort (since the XPS700 is one of those "gamer lozlozlz" systems). The manual for this system is here: http://support.dell.com/support/edocs/systems/xps700/ Screenshots of the BIOS are here: http://www.bit-tech.net/hardware/2006/09/04/Dell_XPS_700_review/5 Are you using RAID at all on this system? If so, chances are that's why it doesn't see your array. Finally, if available, I'd try a BIOS update. Googling for results shows that system has quite a large number of issues with its BIOSes, and Dell has been fairly good about providing updates to fix problems. -- | Jeremy Chadwick jdc at parodius.com | | Parodius Networking http://www.parodius.com/ | | UNIX Systems Administrator Mountain View, CA, USA | | Making life hard for others since 1977. PGP: 4BD6C0CB | From shaun.bsd at gmail.com Thu May 1 19:04:31 2008 From: shaun.bsd at gmail.com (Shaun Sabo) Date: Thu May 1 19:04:33 2008 Subject: FreeBSD 7.0 SATA Controller In-Reply-To: <20080501182325.GA62281@eos.sc1.parodius.com> References: <20080501182325.GA62281@eos.sc1.parodius.com> Message-ID: I checked to make sure that the hard disks are not in raid configuration and there are not. i also checked and my bios are at the latest version available (A11). also this is an XPS 600 not 700 and i have the correct users manual in paper and digital formats. how would you like the dmesg to be presented? i dont think i have any way to writing it to a thumb drive or such devices from the installer. should i just take digital pictures? On Thu, May 1, 2008 at 2:23 PM, Jeremy Chadwick wrote: > On Thu, May 01, 2008 at 01:34:53PM -0400, Shaun Sabo wrote: > > Im trying to install FreeBSD 7.0 on a Dell XPS 600 desktop machine and > im > > having a lot of trouble with this. First I could not use USB keyboards > with > > the installer program (which is fine, i dont mind switching to PS2). > then > > once i got into the sysinstaller it does not detect my Hard Disks. i > also > > tried installing an old 6.2 cd that i had sitting around and remaking > world > > and kernel but when i installed the kernel and restarted to go into > single > > user mode the system could not mount the root filesystem. the > motherboard im > > using is a nvidia nforce4 with Serial ATA hard disks. Does anyone know > how > > to get FreeBSD 7.0 to recognize my hard drives? > > Re: USB keyboard: USB support on FreeBSD is spotty. That said, I've > never run into problems getting FreeBSD to detect and use a USB keyboard > (other USB devices are a different story). You'd need to provide some > dmesg(8) output to verify, but I know that's going to be difficult until > you can get FreeBSD installed. > > Re: SATA disks: I can assure you that FreeBSD works fine with SATA disks > connected to an nForce 4 chipset, because I've used them myself with no > issue. Chances are there's a BIOS setting that's causing mayhem, or > you may be using a RAID array of some sort (since the XPS700 is one of > those "gamer lozlozlz" systems). > > The manual for this system is here: > > http://support.dell.com/support/edocs/systems/xps700/ > > Screenshots of the BIOS are here: > > http://www.bit-tech.net/hardware/2006/09/04/Dell_XPS_700_review/5 > > Are you using RAID at all on this system? If so, chances are that's why > it doesn't see your array. > > Finally, if available, I'd try a BIOS update. Googling for results > shows that system has quite a large number of issues with its BIOSes, > and Dell has been fairly good about providing updates to fix problems. > > -- > | Jeremy Chadwick jdc at parodius.com | > | Parodius Networking http://www.parodius.com/ | > | UNIX Systems Administrator Mountain View, CA, USA | > | Making life hard for others since 1977. PGP: 4BD6C0CB | > > From koitsu at freebsd.org Thu May 1 20:41:58 2008 From: koitsu at freebsd.org (Jeremy Chadwick) Date: Thu May 1 20:42:01 2008 Subject: FreeBSD 7.0 SATA Controller In-Reply-To: References: <20080501182325.GA62281@eos.sc1.parodius.com> Message-ID: <20080501204157.GA67015@eos.sc1.parodius.com> On Thu, May 01, 2008 at 03:04:28PM -0400, Shaun Sabo wrote: > I checked to make sure that the hard disks are not in raid configuration and > there are not. i also checked and my bios are at the latest version > available (A11). also this is an XPS 600 not 700 and i have the correct > users manual in paper and digital formats. how would you like the dmesg to > be presented? i dont think i have any way to writing it to a thumb drive or > such devices from the installer. should i just take digital pictures? Digital pictures would be fine, unless you want to try the serial console route (chances are you don't have this sort of environment set up, so it's probably more effective to take photos). One thing: does Linux detect your disks on this system? I'd recommend downloading one of the recent RELENG_7 snapshot CDs, specifically the "livefs" one, and boot it. dmesg doesn't come with the standard installation disc (disc1), hence why I'm recommending livefs. The snapshots are available here: ftp://ftp.freebsd.org/pub/FreeBSD/snapshots/200804 You probably want one of these two: ftp://ftp.freebsd.org/pub/FreeBSD/snapshots/200804/7.0-STABLE-200804-amd64-livefs.iso ftp://ftp.freebsd.org/pub/FreeBSD/snapshots/200804/7.0-STABLE-200804-i386-livefs.iso dmesg should show some ATA stuff at the end, assuming you're familiar with FreeBSD's kernel output. Something like this, assuming the physical disks are detected: ad4: 190782MB at ata2-master SATA150 ad6: 476940MB at ata3-master SATA300 ad8: 476940MB at ata4-master SATA300 ad10: 476940MB at ata5-master SATA300 You'll need to work backwards to figure out what is connected to what, e.g.: $ dmesg | grep ata2 ata2: on atapci1 ata2: [ITHREAD] ad4: 190782MB at ata2-master SATA150 $ dmesg | grep atapci1 atapci1: port 0x30e8-0x30ef,0x30dc-0x30df,0x30e0-0x30e7,0x30d8-0x30db,0x30b0-0x30bf mem 0xe8600400-0xe86007ff irq 19 at device 31.2 on pci0 atapci1: [ITHREAD] atapci1: AHCI Version 01.10 controller with 4 ports detected ata2: on atapci1 ata3: on atapci1 ata4: on atapci1 ata5: on atapci1 Otherwise, if none of this works, you'll need to somehow provide the full output of "pciconf -lv", which will be many screen fulls of data. You'll probably have to pipe it through "more", take a shot, hit spacebar, take another shot, etc... Please post URLs to the photos, rather than attaching them. The mailing list software does not take kindly to large attachments. -- | Jeremy Chadwick jdc at parodius.com | | Parodius Networking http://www.parodius.com/ | | UNIX Systems Administrator Mountain View, CA, USA | | Making life hard for others since 1977. PGP: 4BD6C0CB | From shaun.bsd at gmail.com Fri May 2 02:18:51 2008 From: shaun.bsd at gmail.com (Shaun Sabo) Date: Fri May 2 02:18:54 2008 Subject: FreeBSD 7.0 SATA Controller In-Reply-To: <20080501204157.GA67015@eos.sc1.parodius.com> References: <20080501182325.GA62281@eos.sc1.parodius.com> <20080501204157.GA67015@eos.sc1.parodius.com> Message-ID: since it is not 7-stable im interested in shouldnt i use the 7.0-RELEASE livefs? On Thu, May 1, 2008 at 4:41 PM, Jeremy Chadwick wrote: > On Thu, May 01, 2008 at 03:04:28PM -0400, Shaun Sabo wrote: > > I checked to make sure that the hard disks are not in raid configuration > and > > there are not. i also checked and my bios are at the latest version > > available (A11). also this is an XPS 600 not 700 and i have the correct > > users manual in paper and digital formats. how would you like the dmesg > to > > be presented? i dont think i have any way to writing it to a thumb drive > or > > such devices from the installer. should i just take digital pictures? > > Digital pictures would be fine, unless you want to try the serial > console route (chances are you don't have this sort of environment set > up, so it's probably more effective to take photos). > > One thing: does Linux detect your disks on this system? > > I'd recommend downloading one of the recent RELENG_7 snapshot CDs, > specifically the "livefs" one, and boot it. dmesg doesn't come with the > standard installation disc (disc1), hence why I'm recommending livefs. > The snapshots are available here: > > ftp://ftp.freebsd.org/pub/FreeBSD/snapshots/200804 > > You probably want one of these two: > > > ftp://ftp.freebsd.org/pub/FreeBSD/snapshots/200804/7.0-STABLE-200804-amd64-livefs.iso > > ftp://ftp.freebsd.org/pub/FreeBSD/snapshots/200804/7.0-STABLE-200804-i386-livefs.iso > > dmesg should show some ATA stuff at the end, assuming you're familiar > with FreeBSD's kernel output. Something like this, assuming the > physical disks are detected: > > ad4: 190782MB at ata2-master SATA150 > ad6: 476940MB at ata3-master SATA300 > ad8: 476940MB at ata4-master SATA300 > ad10: 476940MB at ata5-master SATA300 > > You'll need to work backwards to figure out what is connected to what, > e.g.: > > $ dmesg | grep ata2 > ata2: on atapci1 > ata2: [ITHREAD] > ad4: 190782MB at ata2-master SATA150 > > $ dmesg | grep atapci1 > atapci1: port > 0x30e8-0x30ef,0x30dc-0x30df,0x30e0-0x30e7,0x30d8-0x30db,0x30b0-0x30bf mem > 0xe8600400-0xe86007ff irq 19 at device 31.2 on pci0 > atapci1: [ITHREAD] > atapci1: AHCI Version 01.10 controller with 4 ports detected > ata2: on atapci1 > ata3: on atapci1 > ata4: on atapci1 > ata5: on atapci1 > > Otherwise, if none of this works, you'll need to somehow provide the > full output of "pciconf -lv", which will be many screen fulls of data. > You'll probably have to pipe it through "more", take a shot, hit > spacebar, take another shot, etc... > > Please post URLs to the photos, rather than attaching them. The mailing > list software does not take kindly to large attachments. > > -- > | Jeremy Chadwick jdc at parodius.com | > | Parodius Networking http://www.parodius.com/ | > | UNIX Systems Administrator Mountain View, CA, USA | > | Making life hard for others since 1977. PGP: 4BD6C0CB | > > From shaun.bsd at gmail.com Fri May 2 02:46:56 2008 From: shaun.bsd at gmail.com (Shaun Sabo) Date: Fri May 2 02:46:59 2008 Subject: FreeBSD 7.0 SATA Controller In-Reply-To: References: <20080501182325.GA62281@eos.sc1.parodius.com> <20080501204157.GA67015@eos.sc1.parodius.com> Message-ID: i tried both the 7-stable and 7.0-RELEASE livefs disks and when i went into fixit then to CD/DVD livefs it would ask me for the livefs cd (which i had in the drive and which i booted from) it looks like i cant even mount the image of the livefs disk from the cd-rom drive. also iv noticed that when i reboot after booting into the sysinstaller the bios gets about 2/3 of the way booted and stops and i have to hold the power and reboot to get back into opensuse/vista. On Thu, May 1, 2008 at 10:18 PM, Shaun Sabo wrote: > since it is not 7-stable im interested in shouldnt i use the 7.0-RELEASE > livefs? > > > On Thu, May 1, 2008 at 4:41 PM, Jeremy Chadwick > wrote: > > > On Thu, May 01, 2008 at 03:04:28PM -0400, Shaun Sabo wrote: > > > I checked to make sure that the hard disks are not in raid > > configuration and > > > there are not. i also checked and my bios are at the latest version > > > available (A11). also this is an XPS 600 not 700 and i have the > > correct > > > users manual in paper and digital formats. how would you like the > > dmesg to > > > be presented? i dont think i have any way to writing it to a thumb > > drive or > > > such devices from the installer. should i just take digital pictures? > > > > Digital pictures would be fine, unless you want to try the serial > > console route (chances are you don't have this sort of environment set > > up, so it's probably more effective to take photos). > > > > One thing: does Linux detect your disks on this system? > > > > I'd recommend downloading one of the recent RELENG_7 snapshot CDs, > > specifically the "livefs" one, and boot it. dmesg doesn't come with the > > standard installation disc (disc1), hence why I'm recommending livefs. > > The snapshots are available here: > > > > ftp://ftp.freebsd.org/pub/FreeBSD/snapshots/200804 > > > > You probably want one of these two: > > > > > > ftp://ftp.freebsd.org/pub/FreeBSD/snapshots/200804/7.0-STABLE-200804-amd64-livefs.iso > > > > ftp://ftp.freebsd.org/pub/FreeBSD/snapshots/200804/7.0-STABLE-200804-i386-livefs.iso > > > > dmesg should show some ATA stuff at the end, assuming you're familiar > > with FreeBSD's kernel output. Something like this, assuming the > > physical disks are detected: > > > > ad4: 190782MB at ata2-master SATA150 > > ad6: 476940MB at ata3-master SATA300 > > ad8: 476940MB at ata4-master SATA300 > > ad10: 476940MB at ata5-master SATA300 > > > > You'll need to work backwards to figure out what is connected to what, > > e.g.: > > > > $ dmesg | grep ata2 > > ata2: on atapci1 > > ata2: [ITHREAD] > > ad4: 190782MB at ata2-master SATA150 > > > > $ dmesg | grep atapci1 > > atapci1: port > > 0x30e8-0x30ef,0x30dc-0x30df,0x30e0-0x30e7,0x30d8-0x30db,0x30b0-0x30bf mem > > 0xe8600400-0xe86007ff irq 19 at device 31.2 on pci0 > > atapci1: [ITHREAD] > > atapci1: AHCI Version 01.10 controller with 4 ports detected > > ata2: on atapci1 > > ata3: on atapci1 > > ata4: on atapci1 > > ata5: on atapci1 > > > > Otherwise, if none of this works, you'll need to somehow provide the > > full output of "pciconf -lv", which will be many screen fulls of data. > > You'll probably have to pipe it through "more", take a shot, hit > > spacebar, take another shot, etc... > > > > Please post URLs to the photos, rather than attaching them. The mailing > > list software does not take kindly to large attachments. > > > > -- > > | Jeremy Chadwick jdc at parodius.com | > > | Parodius Networking http://www.parodius.com/ | > > | UNIX Systems Administrator Mountain View, CA, USA | > > | Making life hard for others since 1977. PGP: 4BD6C0CB | > > > > > From koitsu at freebsd.org Fri May 2 02:56:58 2008 From: koitsu at freebsd.org (Jeremy Chadwick) Date: Fri May 2 02:57:01 2008 Subject: FreeBSD 7.0 SATA Controller In-Reply-To: References: <20080501182325.GA62281@eos.sc1.parodius.com> <20080501204157.GA67015@eos.sc1.parodius.com> Message-ID: <20080502025657.GA82058@eos.sc1.parodius.com> On Thu, May 01, 2008 at 10:46:53PM -0400, Shaun Sabo wrote: > i tried both the 7-stable and 7.0-RELEASE livefs disks and when i went into > fixit then to CD/DVD livefs it would ask me for the livefs cd (which i had > in the drive and which i booted from) it looks like i cant even mount the > image of the livefs disk from the cd-rom drive. I'd recommend you burn one of the snapshot livefs images to a CD and boot it. This is what I was implying the first time around. It should give you a live FreeBSD system with common utilities. > also iv noticed that when i > reboot after booting into the sysinstaller the bios gets about 2/3 of the > way booted and stops and i have to hold the power and reboot to get back > into opensuse/vista. I don't understand what this means. "When I reboot after booting into the sysinstaller". Are you talking about FreeBSD sysinstall? Otherwise, any situation where the BIOS does not boot your hard disks sounds more like a BIOS or system problem and definitely has nothing to do with FreeBSD. -- | Jeremy Chadwick jdc at parodius.com | | Parodius Networking http://www.parodius.com/ | | UNIX Systems Administrator Mountain View, CA, USA | | Making life hard for others since 1977. PGP: 4BD6C0CB | From shaun.bsd at gmail.com Fri May 2 03:03:18 2008 From: shaun.bsd at gmail.com (Shaun Sabo) Date: Fri May 2 03:03:23 2008 Subject: FreeBSD 7.0 SATA Controller In-Reply-To: <20080502025657.GA82058@eos.sc1.parodius.com> References: <20080501182325.GA62281@eos.sc1.parodius.com> <20080501204157.GA67015@eos.sc1.parodius.com> <20080502025657.GA82058@eos.sc1.parodius.com> Message-ID: but then why does it not complain in freebsd 6.2, linux, or windows but it does in 7.0? and why i mean by the freebsd sysinstaller is the screen you get when you boot a freebsd disk or when you type sysinstall at a command line in a bsd system. i had the problem where it would only boot 2/3 of the way into the bios once before when i used debian, it was because debian was still on the 2.4 linux kernel and didnt support my mobo yet so it tried to detect it and you had to completely power off the system to get it to boot again, which seems like what is happening here. im going to try re-flashing the bios just to make sure that nothing is wrong with them. And also i tried both the 7.0-RELEASE and 7-STABLE livefs disks and both of them cannot mount the livefs image. On Thu, May 1, 2008 at 10:56 PM, Jeremy Chadwick wrote: > On Thu, May 01, 2008 at 10:46:53PM -0400, Shaun Sabo wrote: > > i tried both the 7-stable and 7.0-RELEASE livefs disks and when i went > into > > fixit then to CD/DVD livefs it would ask me for the livefs cd (which i > had > > in the drive and which i booted from) it looks like i cant even mount > the > > image of the livefs disk from the cd-rom drive. > > I'd recommend you burn one of the snapshot livefs images to a CD and > boot it. This is what I was implying the first time around. It should > give you a live FreeBSD system with common utilities. > > > also iv noticed that when i > > reboot after booting into the sysinstaller the bios gets about 2/3 of > the > > way booted and stops and i have to hold the power and reboot to get back > > into opensuse/vista. > > I don't understand what this means. "When I reboot after booting into > the sysinstaller". Are you talking about FreeBSD sysinstall? > > Otherwise, any situation where the BIOS does not boot your hard disks > sounds more like a BIOS or system problem and definitely has nothing to > do with FreeBSD. > > -- > | Jeremy Chadwick jdc at parodius.com | > | Parodius Networking http://www.parodius.com/ | > | UNIX Systems Administrator Mountain View, CA, USA | > | Making life hard for others since 1977. PGP: 4BD6C0CB | > > From shaun.bsd at gmail.com Fri May 2 03:17:15 2008 From: shaun.bsd at gmail.com (Shaun Sabo) Date: Fri May 2 03:17:18 2008 Subject: FreeBSD 7.0 SATA Controller In-Reply-To: References: <20080501182325.GA62281@eos.sc1.parodius.com> <20080501204157.GA67015@eos.sc1.parodius.com> <20080502025657.GA82058@eos.sc1.parodius.com> Message-ID: re-flashed bios with latest version from dell's website. it was the same version but i re-flashed anyways and im still seeing the same behavior where i cant mount any disks to install or use the livefs. On Thu, May 1, 2008 at 11:03 PM, Shaun Sabo wrote: > but then why does it not complain in freebsd 6.2, linux, or windows but it > does in 7.0? and why i mean by the freebsd sysinstaller is the screen you > get when you boot a freebsd disk or when you type sysinstall at a command > line in a bsd system. i had the problem where it would only boot 2/3 of the > way into the bios once before when i used debian, it was because debian was > still on the 2.4 linux kernel and didnt support my mobo yet so it tried to > detect it and you had to completely power off the system to get it to boot > again, which seems like what is happening here. im going to try re-flashing > the bios just to make sure that nothing is wrong with them. And also i tried > both the 7.0-RELEASE and 7-STABLE livefs disks and both of them cannot mount > the livefs image. > > On Thu, May 1, 2008 at 10:56 PM, Jeremy Chadwick > wrote: > > > On Thu, May 01, 2008 at 10:46:53PM -0400, Shaun Sabo wrote: > > > i tried both the 7-stable and 7.0-RELEASE livefs disks and when i went > > into > > > fixit then to CD/DVD livefs it would ask me for the livefs cd (which i > > had > > > in the drive and which i booted from) it looks like i cant even mount > > the > > > image of the livefs disk from the cd-rom drive. > > > > I'd recommend you burn one of the snapshot livefs images to a CD and > > boot it. This is what I was implying the first time around. It should > > give you a live FreeBSD system with common utilities. > > > > > also iv noticed that when i > > > reboot after booting into the sysinstaller the bios gets about 2/3 of > > the > > > way booted and stops and i have to hold the power and reboot to get > > back > > > into opensuse/vista. > > > > I don't understand what this means. "When I reboot after booting into > > the sysinstaller". Are you talking about FreeBSD sysinstall? > > > > Otherwise, any situation where the BIOS does not boot your hard disks > > sounds more like a BIOS or system problem and definitely has nothing to > > do with FreeBSD. > > > > -- > > | Jeremy Chadwick jdc at parodius.com | > > | Parodius Networking http://www.parodius.com/ | > > | UNIX Systems Administrator Mountain View, CA, USA | > > | Making life hard for others since 1977. PGP: 4BD6C0CB | > > > > > From koitsu at freebsd.org Fri May 2 03:25:26 2008 From: koitsu at freebsd.org (Jeremy Chadwick) Date: Fri May 2 03:25:28 2008 Subject: FreeBSD 7.0 SATA Controller In-Reply-To: References: <20080501182325.GA62281@eos.sc1.parodius.com> <20080501204157.GA67015@eos.sc1.parodius.com> <20080502025657.GA82058@eos.sc1.parodius.com> Message-ID: <20080502032525.GA83155@eos.sc1.parodius.com> On Thu, May 01, 2008 at 11:03:15PM -0400, Shaun Sabo wrote: > but then why does it not complain in freebsd 6.2, linux, or windows but it > does in 7.0? FreeBSD 6.2 is very different than 7.0. :-) And you later state that Linux had the same problem as FreeBSD. And chances are, Dell has tested their system thoroughly on Windows, not Linux or FreeBSD, so device support under Windows is going to be quite solid. > and why i mean by the freebsd sysinstaller is the screen you > get when you boot a freebsd disk or when you type sysinstall at a command > line in a bsd system. I don't see what this has to do with your machine stalling 2/3rds of the way through its boot-up process. The only thing I can think of is that some kind of ATA request is causing the nF4 to lock up, and the BIOS isn't properly resetting it upon a soft reboot. > i had the problem where it would only boot 2/3 of the > way into the bios once before when i used debian, it was because debian was > still on the 2.4 linux kernel and didnt support my mobo yet so it tried to > detect it and you had to completely power off the system to get it to boot > again, which seems like what is happening here. Okay, so this is useful knowledge. It means that Linux has also exhibited the same behaviour as FreeBSD, at least in the past, which means there may be some incompatibility with the devices on the motherboard. It would be useful to know what the Linux folks did to work around the problem. Since I know the nForce 4 works on FreeBSD, the only thing I can think of which might be causing chaos is ACPI, and there are many board manufacturers who release incorrect ACPI tables within in their BIOS. If you try booting either 7.0-RELEASE or 7.0-STABLE with ACPI disabled (it's one of the bootup menu items), does it help? > im going to try re-flashing > the bios just to make sure that nothing is wrong with them. And also i tried > both the 7.0-RELEASE and 7-STABLE livefs disks and both of them cannot mount > the livefs image. You're burning the livefs ISO image to a CD and booting it, correct? What is the exact error you get from FreeBSD when trying to boot the livefs CD? -- | Jeremy Chadwick jdc at parodius.com | | Parodius Networking http://www.parodius.com/ | | UNIX Systems Administrator Mountain View, CA, USA | | Making life hard for others since 1977. PGP: 4BD6C0CB | From rick-freebsd at kiwi-computer.com Fri May 2 19:11:32 2008 From: rick-freebsd at kiwi-computer.com (Rick C. Petty) Date: Fri May 2 19:11:35 2008 Subject: FreeBSD 7.0 SATA Controller In-Reply-To: References: <20080501182325.GA62281@eos.sc1.parodius.com> <20080501204157.GA67015@eos.sc1.parodius.com> <20080502025657.GA82058@eos.sc1.parodius.com> Message-ID: <20080502184449.GA21226@keira.kiwi-computer.com> On Thu, May 01, 2008 at 11:03:15PM -0400, Shaun Sabo wrote: > line in a bsd system. i had the problem where it would only boot 2/3 of the > way into the bios once before when i used debian, it was because debian was What do you mean by 2/3 of the way into the BIOS? Are you saying it only completes 2/3 of the POST? If so, it's not even getting to the point where it boots the CD. Or are you talking about 2/3 of the way through the kernel probes? If so, that's a problem I've seen a lot with Dells. In fact on a newly-purchased Dell 755, I couldn't get halfway through the POST about 75% of the time. Clearing the CMOS/RTC helped, and still about half of the time I boot into the FreeBSD kernel (7-STABLE) it would hang for no reason. Hitting the power button triggered an ACPI event to properly shutdown and restart, but it's damn annoying. > the bios just to make sure that nothing is wrong with them. And also i tried > both the 7.0-RELEASE and 7-STABLE livefs disks and both of them cannot mount > the livefs image. What do you mean by mointing the livefs image? Are you booting a different CD? It was recommended that you burn the livefs CD and then boot *it*. That should also take care of the mounting. -- Rick C. Petty From shaun.bsd at gmail.com Sat May 3 02:09:23 2008 From: shaun.bsd at gmail.com (Shaun Sabo) Date: Sat May 3 02:09:26 2008 Subject: FreeBSD 7.0 SATA Controller In-Reply-To: <20080502184449.GA21226@keira.kiwi-computer.com> References: <20080501182325.GA62281@eos.sc1.parodius.com> <20080501204157.GA67015@eos.sc1.parodius.com> <20080502025657.GA82058@eos.sc1.parodius.com> <20080502184449.GA21226@keira.kiwi-computer.com> Message-ID: What happens with the bios is i start with the machine off. turn it on. boot into any freebsd 7 based disk. ill exit the disk and tell it to reboot the system. the system shuts down and it goes to turn on again. when you turn on a dell computer a progress bar will fill and then it will go to the boot loader/active partition, i believe that it initializes the bios settings. what happens after i reboot out of the freebsd 7 based disks is the progress bar hangs at about 2/3 full. i can boot into a cd or operating system fine if i turn the machine completely off but something isnt re-settting when i reboot out of freebsd. this used to happen when i tried using debian linux because debian was still on the 2.4 kernel which did not have support for my motherboard so i couldnt even boot the debian installer cd. i also tried booting the freebsd installer disks without apic but the same problem occurs so i dont think its hanging because of the power managment. as for the livefs. i downloaded both the 7-STABLE and 7.0-RELEASE livefs cds. when i boot them up it gets to the sysinstall program like all of the other disks do. to use the livefs functions you have to go into fixit and then choose the CD/DVD option. what this does is it mounts the filesystem kept on the cd so that you can switch to the virtual terminal 4 (alt+f4) and use the system as a recovery disk or for dmesg and such. the error i get is "could not mount the livefs cd. try again?" for some reason i cannot mount any sort of media in freebsd 7 systems. the computer handles the booting of the cd's fine but freebsd cannot for some reason handle the mounting of disks. the next step im going to take is installing 6.2 and remaking the world but adding device aptic to the kernel. On Fri, May 2, 2008 at 2:44 PM, Rick C. Petty < rick-freebsd@kiwi-computer.com> wrote: > On Thu, May 01, 2008 at 11:03:15PM -0400, Shaun Sabo wrote: > > line in a bsd system. i had the problem where it would only boot 2/3 of > the > > way into the bios once before when i used debian, it was because debian > was > > What do you mean by 2/3 of the way into the BIOS? Are you saying it only > completes 2/3 of the POST? If so, it's not even getting to the point > where > it boots the CD. Or are you talking about 2/3 of the way through the > kernel probes? If so, that's a problem I've seen a lot with Dells. In > fact on a newly-purchased Dell 755, I couldn't get halfway through the > POST > about 75% of the time. Clearing the CMOS/RTC helped, and still about half > of the time I boot into the FreeBSD kernel (7-STABLE) it would hang for no > reason. Hitting the power button triggered an ACPI event to properly > shutdown and restart, but it's damn annoying. > > > the bios just to make sure that nothing is wrong with them. And also i > tried > > both the 7.0-RELEASE and 7-STABLE livefs disks and both of them cannot > mount > > the livefs image. > > What do you mean by mointing the livefs image? Are you booting a > different > CD? It was recommended that you burn the livefs CD and then boot *it*. > That should also take care of the mounting. > > -- Rick C. Petty > From koitsu at freebsd.org Sat May 3 02:42:41 2008 From: koitsu at freebsd.org (Jeremy Chadwick) Date: Sat May 3 02:42:43 2008 Subject: FreeBSD 7.0 SATA Controller In-Reply-To: References: <20080501182325.GA62281@eos.sc1.parodius.com> <20080501204157.GA67015@eos.sc1.parodius.com> <20080502025657.GA82058@eos.sc1.parodius.com> <20080502184449.GA21226@keira.kiwi-computer.com> Message-ID: <20080503024240.GA28006@eos.sc1.parodius.com> On Fri, May 02, 2008 at 10:09:20PM -0400, Shaun Sabo wrote: > What happens with the bios is i start with the machine off. turn it on. boot > into any freebsd 7 based disk. ill exit the disk and tell it to reboot the > system. the system shuts down and it goes to turn on again. when you turn on > a dell computer a progress bar will fill and then it will go to the boot > loader/active partition, i believe that it initializes the bios settings. > what happens after i reboot out of the freebsd 7 based disks is the progress > bar hangs at about 2/3 full. i can boot into a cd or operating system fine > if i turn the machine completely off but something isnt re-settting when i > reboot out of freebsd. this used to happen when i tried using debian linux > because debian was still on the 2.4 kernel which did not have support for my > motherboard so i couldnt even boot the debian installer cd. i also tried > booting the freebsd installer disks without apic but the same problem occurs > so i dont think its hanging because of the power managment. APIC != ACPI. If you disabled the APIC, you'd be changing the method of interrupt routing used by FreeBSD, which won't affect power management. Additionally, you need to understand that ACPI isn't used for just power management. It's used to define system parameters via a series of tables which are stored in the BIOS. There are a lot of motherboard manufacturers who have improper ACPI tables stored in their BIOS (read: BIOS bugs), and by disabling ACPI, one can sometimes work around odd problems with devices not working correctly, or odd system hangs. Finally, the behaviour you're experiencing with your machine (re: the progress bar stalling 2/3rds of the way through) sounds almost as if the hard disks aren't spinning up quick enough after a soft reset from within FreeBSD or Linux 2.4. If there's a BIOS option to "delay hard disk startup", I would recommend setting that to 1-2 seconds and see what happens. Otherwise, this really sounds like a BIOS bug, and much less like a FreeBSD or Linux bug. I realise it may not happen with Linux 2.6, but possibly their reboot method changed. FreeBSD has a couple sysctls you can change which adjust the reboot method used. One disabled ACPI during the reboot phase, which can sometimes cause the system to hang/lock before the reboot is complete. Another uses ACPI itself to do the rebooting, vs. (I believe) an older system reboot method. These are the sysctls and their default values: hw.acpi.disable_on_reboot: 0 hw.acpi.handle_reboot: 0 > as for the livefs. i downloaded both the 7-STABLE and 7.0-RELEASE livefs > cds. when i boot them up it gets to the sysinstall program like all of the > other disks do. to use the livefs functions you have to go into fixit and > then choose the CD/DVD option. what this does is it mounts the filesystem > kept on the cd so that you can switch to the virtual terminal 4 (alt+f4) and > use the system as a recovery disk or for dmesg and such. the error i get is > "could not mount the livefs cd. try again?" Okay, you're confusing two things. livefs != fixit. What it sounds to me like you're doing is booting a CD of "disc1" and then going into the Fixit menu. If you do this then insert a livefs CD, it's not going to work. When you boot a CD burnt with "livefs", the FreeBSD kernel will start, and you'll be immediately dropped into a shell with a whole ton of available utilities. It's basically a working FreeBSD system on a CD, which is why it's called livefs. > for some reason i cannot mount any sort of media in freebsd 7 systems. > the computer handles the booting of the cd's fine but freebsd cannot > for some reason handle the mounting of disks. the next step im going > to take is installing 6.2 and remaking the world but adding device > aptic to the kernel. I think you mean "device apic" to the kernel? Please see the first paragraph above; I think you're misunderstanding ACPI vs. APIC. You should follow the standard devices listed in the GENERIC configuration. This includes support for APICs, as well as SMP. Look at /sys/i386/conf/GENERIC, or /sys/amd64/conf/GENERIC (depending on if you went i386 or amd64). -- | Jeremy Chadwick jdc at parodius.com | | Parodius Networking http://www.parodius.com/ | | UNIX Systems Administrator Mountain View, CA, USA | | Making life hard for others since 1977. PGP: 4BD6C0CB | From freebsd at sopwith.solgatos.com Sat May 3 03:33:11 2008 From: freebsd at sopwith.solgatos.com (Dieter) Date: Sat May 3 03:33:14 2008 Subject: FreeBSD 7.0 SATA Controller In-Reply-To: Your message of "Fri, 02 May 2008 19:42:40 PDT." <20080503024240.GA28006@eos.sc1.parodius.com> Message-ID: <200805030331.DAA29798@sopwith.solgatos.com> > Finally, the behaviour you're experiencing with your machine (re: the > progress bar stalling 2/3rds of the way through) sounds almost as if the > hard disks aren't spinning up quick enough after a soft reset from > within FreeBSD or Linux 2.4. The disks should have spun up long before a reset gets issued. > > for some reason i cannot mount any sort of media in freebsd 7 systems. > > the computer handles the booting of the cd's fine but freebsd cannot > > for some reason handle the mounting of disks. It is the firmware (and maybe a bootstrap) that boots a CD. Once control is handed over to the FreeBSD kernel, then the kernel has to be able to talk to the disks. It is the FreeBSD 7 kernel that is having the problem. > > the next step im going > > to take is installing 6.2 and remaking the world but adding device > > aptic to the kernel. > > I think you mean "device apic" to the kernel? No, it is "device aptic". It was in 6 but removed from 7. I had to add aptic to get my nforce4-ultra board to boot 7. Given that 6 runs on Shaun's machine and 7 doesn't, adding aptic is a useful thing to try. From shaun.bsd at gmail.com Sat May 3 03:53:07 2008 From: shaun.bsd at gmail.com (Shaun Sabo) Date: Sat May 3 03:53:10 2008 Subject: FreeBSD 7.0 SATA Controller In-Reply-To: <20080503024240.GA28006@eos.sc1.parodius.com> References: <20080501204157.GA67015@eos.sc1.parodius.com> <20080502025657.GA82058@eos.sc1.parodius.com> <20080502184449.GA21226@keira.kiwi-computer.com> <20080503024240.GA28006@eos.sc1.parodius.com> Message-ID: the livefs cds do not drop you into a shell. they drop you into the same screen you see when you insert an installation cd. try it on qemu or another virtualization program or even boot one up if you have a spare cd rom. in order to access the livefs shell you need to navigate to the fixit menu and then go to the livefs CD/DVD option. as for the apic vc acpi that was a typo due to exhaustion, sorry bout that. On Fri, May 2, 2008 at 10:42 PM, Jeremy Chadwick wrote: > On Fri, May 02, 2008 at 10:09:20PM -0400, Shaun Sabo wrote: > > What happens with the bios is i start with the machine off. turn it on. > boot > > into any freebsd 7 based disk. ill exit the disk and tell it to reboot > the > > system. the system shuts down and it goes to turn on again. when you > turn on > > a dell computer a progress bar will fill and then it will go to the boot > > loader/active partition, i believe that it initializes the bios > settings. > > what happens after i reboot out of the freebsd 7 based disks is the > progress > > bar hangs at about 2/3 full. i can boot into a cd or operating system > fine > > if i turn the machine completely off but something isnt re-settting when > i > > reboot out of freebsd. this used to happen when i tried using debian > linux > > because debian was still on the 2.4 kernel which did not have support > for my > > motherboard so i couldnt even boot the debian installer cd. i also tried > > booting the freebsd installer disks without apic but the same problem > occurs > > so i dont think its hanging because of the power managment. > > APIC != ACPI. If you disabled the APIC, you'd be changing the method of > interrupt routing used by FreeBSD, which won't affect power management. > Additionally, you need to understand that ACPI isn't used for just power > management. It's used to define system parameters via a series of > tables which are stored in the BIOS. There are a lot of motherboard > manufacturers who have improper ACPI tables stored in their BIOS (read: > BIOS bugs), and by disabling ACPI, one can sometimes work around odd > problems with devices not working correctly, or odd system hangs. > > Finally, the behaviour you're experiencing with your machine (re: the > progress bar stalling 2/3rds of the way through) sounds almost as if the > hard disks aren't spinning up quick enough after a soft reset from > within FreeBSD or Linux 2.4. If there's a BIOS option to "delay hard > disk startup", I would recommend setting that to 1-2 seconds and see > what happens. Otherwise, this really sounds like a BIOS bug, and much > less like a FreeBSD or Linux bug. I realise it may not happen with > Linux 2.6, but possibly their reboot method changed. > > FreeBSD has a couple sysctls you can change which adjust the reboot > method used. One disabled ACPI during the reboot phase, which can > sometimes cause the system to hang/lock before the reboot is complete. > Another uses ACPI itself to do the rebooting, vs. (I believe) an older > system reboot method. These are the sysctls and their default values: > > hw.acpi.disable_on_reboot: 0 > hw.acpi.handle_reboot: 0 > > > as for the livefs. i downloaded both the 7-STABLE and 7.0-RELEASE livefs > > cds. when i boot them up it gets to the sysinstall program like all of > the > > other disks do. to use the livefs functions you have to go into fixit > and > > then choose the CD/DVD option. what this does is it mounts the > filesystem > > kept on the cd so that you can switch to the virtual terminal 4 (alt+f4) > and > > use the system as a recovery disk or for dmesg and such. the error i get > is > > "could not mount the livefs cd. try again?" > > Okay, you're confusing two things. livefs != fixit. What it sounds to > me like you're doing is booting a CD of "disc1" and then going into the > Fixit menu. If you do this then insert a livefs CD, it's not going to > work. > > When you boot a CD burnt with "livefs", the FreeBSD kernel will start, > and you'll be immediately dropped into a shell with a whole ton of > available utilities. It's basically a working FreeBSD system on a CD, > which is why it's called livefs. > > > for some reason i cannot mount any sort of media in freebsd 7 systems. > > the computer handles the booting of the cd's fine but freebsd cannot > > for some reason handle the mounting of disks. the next step im going > > to take is installing 6.2 and remaking the world but adding device > > aptic to the kernel. > > I think you mean "device apic" to the kernel? Please see the first > paragraph above; I think you're misunderstanding ACPI vs. APIC. > > You should follow the standard devices listed in the GENERIC > configuration. This includes support for APICs, as well as SMP. Look > at /sys/i386/conf/GENERIC, or /sys/amd64/conf/GENERIC (depending on if > you went i386 or amd64). > > -- > | Jeremy Chadwick jdc at parodius.com | > | Parodius Networking http://www.parodius.com/ | > | UNIX Systems Administrator Mountain View, CA, USA | > | Making life hard for others since 1977. PGP: 4BD6C0CB | > > From rick-freebsd at kiwi-computer.com Sat May 3 04:02:08 2008 From: rick-freebsd at kiwi-computer.com (Rick C. Petty) Date: Sat May 3 04:02:11 2008 Subject: FreeBSD 7.0 SATA Controller In-Reply-To: References: <20080501182325.GA62281@eos.sc1.parodius.com> <20080501204157.GA67015@eos.sc1.parodius.com> <20080502025657.GA82058@eos.sc1.parodius.com> <20080502184449.GA21226@keira.kiwi-computer.com> Message-ID: <20080503040206.GA26564@keira.kiwi-computer.com> On Fri, May 02, 2008 at 10:09:20PM -0400, Shaun Sabo wrote: > What happens with the bios is i start with the machine off. turn it on. boot > into any freebsd 7 based disk. ill exit the disk and tell it to reboot the > system. the system shuts down and it goes to turn on again. when you turn on > a dell computer a progress bar will fill and then it will go to the boot > loader/active partition, i believe that it initializes the bios settings. > what happens after i reboot out of the freebsd 7 based disks is the progress > bar hangs at about 2/3 full. i can boot into a cd or operating system fine > if i turn the machine completely off but something isnt re-settting when i > reboot out of freebsd. this used to happen when i tried using debian linux This sounds like a BIOS bug. FreeBSD has no control over what happens while the BIOS is doing a cold restart, until the initial boot record is read and then executed. AFAIR, there are two ways FreeBSD initiates a warm restart.. via a BIOS call or using ACPI. In either case, the hardware and the firmware controlling said hardware (which we call the BIOS) is responsible for ensuring everything gets initialized correctly. There's not much that FreeBSD can do, although you could try with and without ACPI and see if one works better than another. This situation reinforces my belief that Dell has problems with their BIOS firmware. I've yet to see a Dell behave as well as any system I've built myself. > as for the livefs. i downloaded both the 7-STABLE and 7.0-RELEASE livefs > cds. when i boot them up it gets to the sysinstall program like all of the > other disks do. Then I don't believe you are using the livecd. If you're hitting sysinstall, you must be using the bootonly, disc1, or fixit CDs. > to use the livefs functions you have to go into fixit and > then choose the CD/DVD option. what this does is it mounts the filesystem > kept on the cd so that you can switch to the virtual terminal 4 (alt+f4) and > use the system as a recovery disk or for dmesg and such. the error i get is > "could not mount the livefs cd. try again?" Then that rules out fixit CD. I thought even the bootonly & disk1 images had a minimal (i.e. useless) image and that this step is always successful. > for some reason i cannot mount any sort of media in freebsd 7 systems. I assume you mean from a freebsd 7.0-RELEASE CD image? Otherwise that's a pretty bold statement. If true, then this may be a driver issue that I've never heard of. > the computer handles the booting of > the cd's fine but freebsd cannot for some reason handle the mounting of > disks. What is the name of the image you downloaded, perhaps the full URL you grabbed it from? It was suggested that you try a post-7.0 livecd. I've had very good luck with these, both using and creating them. > the next step im going to take is installing 6.2 and remaking the > world but adding device aptic to the kernel. What is this "aptic" device? I can't seem to find it on any 6.x or 7.x system. Perhaps it is a typo? Please explain. -- Rick C. Petty From rick-freebsd at kiwi-computer.com Sat May 3 04:09:31 2008 From: rick-freebsd at kiwi-computer.com (Rick C. Petty) Date: Sat May 3 04:09:35 2008 Subject: FreeBSD 7.0 SATA Controller In-Reply-To: References: <20080501204157.GA67015@eos.sc1.parodius.com> <20080502025657.GA82058@eos.sc1.parodius.com> <20080502184449.GA21226@keira.kiwi-computer.com> <20080503024240.GA28006@eos.sc1.parodius.com> Message-ID: <20080503040930.GB26564@keira.kiwi-computer.com> On Fri, May 02, 2008 at 11:53:04PM -0400, Shaun Sabo wrote: > the livefs cds do not drop you into a shell. they drop you into the same > screen you see when you insert an installation cd. try it on qemu or another > virtualization program or even boot one up if you have a spare cd rom. in > order to access the livefs shell you need to navigate to the fixit menu and > then go to the livefs CD/DVD option. Please explain where you obtained said "livefs" CD. Every livefs CD I've tried (in qemu) has dropped me to a shell. Every "fixit" CD I've tried brings me to sysinstall and from there I drop to the shell after navigating the menus. > as for the apic vc acpi that was a typo > due to exhaustion, sorry bout that. Sure, but which one do you mean? I assume you mean booting with or without ACPI, which is an option in the boot loader. > > > motherboard so i couldnt even boot the debian installer cd. i also tried > > > booting the freebsd installer disks without apic but the same problem > > occurs > > > so i dont think its hanging because of the power managment. ACPI isn't just power management-- it's advanced _configuration_ and power interface. My understanding is that if present, FreeBSD talks to the ACPI on the BIOS to allocate IRQs and other resources. There have been bugs in the past when dealing with ACPI which caused the FreeBSD devs to include a boot option to disable it. If your system breaks w/o ACPI, then there's certainly a BIOS firmware problem. Have you tried the following test? Cold boot (from power off) to FreeBSD CD, disable ACPI from the menu, boot the kernel, then do a warm reboot and see if the problem exists. My sense is that if your first attempt from a cold start has ACPI enabled, the problem will persist for every subsequent warm reboot. -- Rick C. Petty From koitsu at freebsd.org Sat May 3 04:25:41 2008 From: koitsu at freebsd.org (Jeremy Chadwick) Date: Sat May 3 04:25:45 2008 Subject: FreeBSD 7.0 SATA Controller In-Reply-To: <200805030331.DAA29798@sopwith.solgatos.com> References: <20080503024240.GA28006@eos.sc1.parodius.com> <200805030331.DAA29798@sopwith.solgatos.com> Message-ID: <20080503042540.GA32245@eos.sc1.parodius.com> On Fri, May 02, 2008 at 08:31:35PM +0100, Dieter wrote: > > Finally, the behaviour you're experiencing with your machine (re: the > > progress bar stalling 2/3rds of the way through) sounds almost as if the > > hard disks aren't spinning up quick enough after a soft reset from > > within FreeBSD or Linux 2.4. > > The disks should have spun up long before a reset gets issued. Not necessarily. It ultimately depends on what the system is engineered to do during a soft reboot. The disks themselves may be powering down briefly, may take a long time to initialise, or maybe there's a bug in the drive firmware. My personal guess is that it's a BIOS bug. > > > for some reason i cannot mount any sort of media in freebsd 7 systems. > > > the computer handles the booting of the cd's fine but freebsd cannot > > > for some reason handle the mounting of disks. > > It is the firmware (and maybe a bootstrap) that boots a CD. > Once control is handed over to the FreeBSD kernel, then the > kernel has to be able to talk to the disks. It is the FreeBSD 7 > kernel that is having the problem. Again, not necessarily. I think I've provided enough evidence of where BIOS settings can affect FreeBSD's behaviour when it comes to disk controllers. My RAID question was one such example. > > > the next step im going > > > to take is installing 6.2 and remaking the world but adding device > > > aptic to the kernel. > > > > I think you mean "device apic" to the kernel? > > No, it is "device aptic". It was in 6 but removed from 7. I had to add > aptic to get my nforce4-ultra board to boot 7. Given that 6 runs on > Shaun's machine and 7 doesn't, adding aptic is a useful thing to try. There is no "aptic" device on RELENG_6. I just did a grep -ri "aptic" /usr/src on our RELENG_6 box and found absolutely no trace of said device. You are thinking of "apic". -- | Jeremy Chadwick jdc at parodius.com | | Parodius Networking http://www.parodius.com/ | | UNIX Systems Administrator Mountain View, CA, USA | | Making life hard for others since 1977. PGP: 4BD6C0CB | From freebsd at sopwith.solgatos.com Sat May 3 06:04:45 2008 From: freebsd at sopwith.solgatos.com (Dieter) Date: Sat May 3 06:04:49 2008 Subject: FreeBSD 7.0 SATA Controller In-Reply-To: Your message of "Fri, 02 May 2008 21:25:40 PDT." <20080503042540.GA32245@eos.sc1.parodius.com> Message-ID: <200805030603.GAA23115@sopwith.solgatos.com> > > > > the next step im going > > > > to take is installing 6.2 and remaking the world but adding device > > > > aptic to the kernel. > > > > > > I think you mean "device apic" to the kernel? > > > > No, it is "device aptic". It was in 6 but removed from 7. I had to add > > aptic to get my nforce4-ultra board to boot 7. Given that 6 runs on > > Shaun's machine and 7 doesn't, adding aptic is a useful thing to try. > > There is no "aptic" device on RELENG_6. I just did a grep -ri "aptic" > /usr/src on our RELENG_6 box and found absolutely no trace of said > device. You are thinking of "apic". Typo. Should be "device atpic". From shaun.bsd at gmail.com Sat May 3 14:46:14 2008 From: shaun.bsd at gmail.com (Shaun Sabo) Date: Sat May 3 14:46:17 2008 Subject: FreeBSD 7.0 SATA Controller In-Reply-To: <20080503040930.GB26564@keira.kiwi-computer.com> References: <20080502025657.GA82058@eos.sc1.parodius.com> <20080502184449.GA21226@keira.kiwi-computer.com> <20080503024240.GA28006@eos.sc1.parodius.com> <20080503040930.GB26564@keira.kiwi-computer.com> Message-ID: the livefs cd links are 7.0-RELEASE ftp://ftp.freebsd.org/pub/FreeBSD/ISO-IMAGES-i386/7.0/7.0-RELEASE-i386-livefs.iso 7-STABLE ftp://ftp.freebsd.org/pub/FreeBSD/snapshots/200804/7.0-STABLE-200804-i386-livefs.iso i tried these in vmware and on another computer and neither one drops me into a shell. they both put me in the sysinstall program and i have to activate the livefs from the fixit menu then go to virtual terminal 4 (alt+f4). problem is i cant get the livefs shell to start on my system. works fine in vmware, qemu, and my sisters computer so i know there isnt something wrong with the cds. Im really not too concerned about the bios bug. i just figured it might be a side effect of freebsd not being able access the disks. just out of curiosity though, before i upgrade 6.2 to 7.0 again, what is the atpic device supposed to do? as for not being able to mount any media from any freebsd 7.0 system. this includes when i rebuilt the kernel and world from 6.2 to 7.0 with the generic kernel. when i tried booting it was not able to find the root partition. the install and livefs cds can also not find the hard disks nor can you use the livefs utilities as stated above. On Sat, May 3, 2008 at 12:09 AM, Rick C. Petty < rick-freebsd@kiwi-computer.com> wrote: > On Fri, May 02, 2008 at 11:53:04PM -0400, Shaun Sabo wrote: > > the livefs cds do not drop you into a shell. they drop you into the same > > screen you see when you insert an installation cd. try it on qemu or > another > > virtualization program or even boot one up if you have a spare cd rom. > in > > order to access the livefs shell you need to navigate to the fixit menu > and > > then go to the livefs CD/DVD option. > > Please explain where you obtained said "livefs" CD. Every livefs CD I've > tried (in qemu) has dropped me to a shell. Every "fixit" CD I've tried > brings me to sysinstall and from there I drop to the shell after > navigating > the menus. > > > as for the apic vc acpi that was a typo > > due to exhaustion, sorry bout that. > > Sure, but which one do you mean? I assume you mean booting with or > without > ACPI, which is an option in the boot loader. > > > > > motherboard so i couldnt even boot the debian installer cd. i also > tried > > > > booting the freebsd installer disks without apic but the same > problem > > > occurs > > > > so i dont think its hanging because of the power managment. > > ACPI isn't just power management-- it's advanced _configuration_ and power > interface. My understanding is that if present, FreeBSD talks to the ACPI > on the BIOS to allocate IRQs and other resources. There have been bugs in > the past when dealing with ACPI which caused the FreeBSD devs to include a > boot option to disable it. If your system breaks w/o ACPI, then there's > certainly a BIOS firmware problem. > > Have you tried the following test? Cold boot (from power off) to FreeBSD > CD, disable ACPI from the menu, boot the kernel, then do a warm reboot and > see if the problem exists. My sense is that if your first attempt from a > cold start has ACPI enabled, the problem will persist for every subsequent > warm reboot. > > -- Rick C. Petty > From freebsd at sopwith.solgatos.com Sat May 3 16:05:18 2008 From: freebsd at sopwith.solgatos.com (Dieter) Date: Sat May 3 16:05:21 2008 Subject: FreeBSD 7.0 SATA Controller In-Reply-To: Your message of "Sat, 03 May 2008 10:46:11 EDT." Message-ID: <200805031603.QAA03668@sopwith.solgatos.com> > Im really not too concerned about the bios bug. i just figured it might be a > side effect of freebsd not being able access the disks. just out of > curiosity though, before i upgrade 6.2 to 7.0 again, what is the atpic > device supposed to do? My understanding is that atpic is the old way of mapping interrupts, and apic is the new way. If apic doesn't work for whatever reason, you need atpic. I was was getting lots of errors like Could not allocate irq attach returned 6 no driver attached Can't map interrupt -> can't attach driver -> can't talk to disks -> can't mount root From koitsu at freebsd.org Sat May 3 17:34:08 2008 From: koitsu at freebsd.org (Jeremy Chadwick) Date: Sat May 3 17:34:12 2008 Subject: FreeBSD 7.0 SATA Controller In-Reply-To: <200805030603.GAA23115@sopwith.solgatos.com> References: <20080503042540.GA32245@eos.sc1.parodius.com> <200805030603.GAA23115@sopwith.solgatos.com> Message-ID: <20080503173408.GA58602@eos.sc1.parodius.com> On Fri, May 02, 2008 at 11:03:16PM +0100, Dieter wrote: > > > > > the next step im going > > > > > to take is installing 6.2 and remaking the world but adding device > > > > > aptic to the kernel. > > > > > > > > I think you mean "device apic" to the kernel? > > > > > > No, it is "device aptic". It was in 6 but removed from 7. I had to add > > > aptic to get my nforce4-ultra board to boot 7. Given that 6 runs on > > > Shaun's machine and 7 doesn't, adding aptic is a useful thing to try. > > > > There is no "aptic" device on RELENG_6. I just did a grep -ri "aptic" > > /usr/src on our RELENG_6 box and found absolutely no trace of said > > device. You are thinking of "apic". > > Typo. Should be "device atpic". Ah yes. That would be the classic AT-style PIC used for interrupt handling. That makes much more sense. :-) -- | Jeremy Chadwick jdc at parodius.com | | Parodius Networking http://www.parodius.com/ | | UNIX Systems Administrator Mountain View, CA, USA | | Making life hard for others since 1977. PGP: 4BD6C0CB | From shaun.bsd at gmail.com Sun May 4 01:15:31 2008 From: shaun.bsd at gmail.com (Shaun Sabo) Date: Sun May 4 01:15:33 2008 Subject: FreeBSD 7.0 SATA Controller In-Reply-To: <20080503173408.GA58602@eos.sc1.parodius.com> References: <20080503042540.GA32245@eos.sc1.parodius.com> <200805030603.GAA23115@sopwith.solgatos.com> <20080503173408.GA58602@eos.sc1.parodius.com> Message-ID: so does that mean i need to disable the apic? and are we talking about apic now or acpi? im getting all these devices confused now. i realize that acpi is dissabled when you press number 2 at the boot menu but are we talking about that or apic? On Sat, May 3, 2008 at 1:34 PM, Jeremy Chadwick wrote: > On Fri, May 02, 2008 at 11:03:16PM +0100, Dieter wrote: > > > > > > the next step im going > > > > > > to take is installing 6.2 and remaking the world but adding > device > > > > > > aptic to the kernel. > > > > > > > > > > I think you mean "device apic" to the kernel? > > > > > > > > No, it is "device aptic". It was in 6 but removed from 7. I had to > add > > > > aptic to get my nforce4-ultra board to boot 7. Given that 6 runs on > > > > Shaun's machine and 7 doesn't, adding aptic is a useful thing to > try. > > > > > > There is no "aptic" device on RELENG_6. I just did a grep -ri "aptic" > > > /usr/src on our RELENG_6 box and found absolutely no trace of said > > > device. You are thinking of "apic". > > > > Typo. Should be "device atpic". > > Ah yes. That would be the classic AT-style PIC used for interrupt > handling. That makes much more sense. :-) > > -- > | Jeremy Chadwick jdc at parodius.com | > | Parodius Networking http://www.parodius.com/ | > | UNIX Systems Administrator Mountain View, CA, USA | > | Making life hard for others since 1977. PGP: 4BD6C0CB | > > From koitsu at freebsd.org Sun May 4 01:34:30 2008 From: koitsu at freebsd.org (Jeremy Chadwick) Date: Sun May 4 01:34:33 2008 Subject: FreeBSD 7.0 SATA Controller In-Reply-To: References: <20080503042540.GA32245@eos.sc1.parodius.com> <200805030603.GAA23115@sopwith.solgatos.com> <20080503173408.GA58602@eos.sc1.parodius.com> Message-ID: <20080504013429.GA74129@eos.sc1.parodius.com> On Sat, May 03, 2008 at 09:15:24PM -0400, Shaun Sabo wrote: > so does that mean i need to disable the apic? and are we talking about apic > now or acpi? im getting all these devices confused now. i realize that acpi > is dissabled when you press number 2 at the boot menu but are we talking > about that or apic? ACPI: Commonly used for system configuration data (stored/controlled by BIOS), power management, and a couple other things. Unrelated to APIC and ATPIC. APIC: Advanced interrupt routing IC; more or less used to extend interrupt limitations of old PIC-based interrupts. Originally there were 16 IRQs, most taken up by system necessities. An APIC extends that to 256 IRQs, providing each device with its own IRQ, assuming the OS supports APICs, otherwise it'll resort to classic 16 IRQ behaviour (sharing of IRQs, etc.) http://en.wikipedia.org/wiki/Advanced_Programmable_Interrupt_Controller ATPIC: Classic 8259 PIC ("AT PIC"), 16 IRQ limitation, etc. http://en.wikipedia.org/wiki/8259 Hope this clears things up for you. I've never seen a system made in the past 7-8 years which demands the use of atpic. Most present-day systems, even uni-processor systems, have an APIC, and most of the time those work without issue. If you want to disable the APIC, you can do so by booting FreeBSD in "safe mode". It should be a menu item; I forget which number. "Safe mode" will disable the following things: * Disable use of ACPI * Disable APIC * Disable DMA capability on ATA devices (does not apply to SATA) * Disable DMA capability on ATAPI device (CD/DVD-ROMs, etc.) * Disabled hard disk write caching * Disables kbdmux(4) * Does something with hw.eisa_slots, which I don't quite understand. Only "easy" reference I can find is to old Adaptec controllers requiring hw.eisa_slots="12". -- | Jeremy Chadwick jdc at parodius.com | | Parodius Networking http://www.parodius.com/ | | UNIX Systems Administrator Mountain View, CA, USA | | Making life hard for others since 1977. PGP: 4BD6C0CB | From jhs at berklix.org Sun May 4 16:16:44 2008 From: jhs at berklix.org (Julian Stacey) Date: Sun May 4 16:16:49 2008 Subject: FreeBSD 7.0 SATA Controller In-Reply-To: Your message "Sat, 03 May 2008 18:34:29 PDT." <20080504013429.GA74129@eos.sc1.parodius.com> Message-ID: <200805041541.m44FfNU0097633@fire.js.berklix.net> > "Safe mode" will disable the following things: A while back I searched source about what "Safe" did, & how to achieve finer control via loader.conf, & made notes: http://www.berklix.com/~jhs/hardware/laptops/#bootsafekey That was on 7.0BETA3 & prerelease, not sure if up to release. Julian -- Julian Stacey: BSDUnixLinux C Prog Admin SysEng Consult Munich www.berklix.com Mail just Ascii plain text. HTML & Base64 text are spam. From shaun.bsd at gmail.com Tue May 6 19:26:43 2008 From: shaun.bsd at gmail.com (Shaun Sabo) Date: Tue May 6 19:26:46 2008 Subject: FreeBSD 7.0 SATA Controller In-Reply-To: <200805041541.m44FfNU0097633@fire.js.berklix.net> References: <20080504013429.GA74129@eos.sc1.parodius.com> <200805041541.m44FfNU0097633@fire.js.berklix.net> Message-ID: I think that there is a serious driver problem with my motherboard and freebsd 7.0 and im not sure if its worth putting too much more work into trying to get it to run. I think that im going to use the 6.3 release for now and maybe when 7.1 is released the driver problem will have worked its way out. On Sun, May 4, 2008 at 11:41 AM, Julian Stacey wrote: > > "Safe mode" will disable the following things: > > A while back I searched source about what "Safe" did, & how to achieve > finer control via loader.conf, & made notes: > http://www.berklix.com/~jhs/hardware/laptops/#bootsafekey > That was on 7.0BETA3 & prerelease, not sure if up to release. > > Julian > -- > Julian Stacey: BSDUnixLinux C Prog Admin SysEng Consult Munich > www.berklix.com > Mail just Ascii plain text. HTML & Base64 text are spam. > _______________________________________________ > freebsd-hardware@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-hardware > To unsubscribe, send any mail to "freebsd-hardware-unsubscribe@freebsd.org > " > From wkk at wkk.com Tue May 6 20:35:15 2008 From: wkk at wkk.com (WKK) Date: Tue May 6 20:35:19 2008 Subject: industrial computer flash performance issues Message-ID: <4820B7EC.5040705@wkk.com> I have a Nagasaki IPC industrial computer that has an 8 GB flash drive on a 44 pin ATA connector. I have booted FreeBSD 6.2 and 7.0 via a USB CD drive and I am getting very bad read performance. dd if=/dev/ad0 of=/dev/null bs=128k count=100 is only showing about 4MB/s. I have also tried a CF via a PCMCIA adapter and I am also seeing about the same performance. The same CF device connected with a USB adapter (/dev/da0) gets about 16MB/s so it seems like some type of ATA driver issue. >From dmesg: atapci0: port ?. ?. ad0: 7765MB at ata0-master PIO4 atacontrol cap ad0 shows that dma and overlap is not supported and all the features are no. Does anyone have any suggestions for improving performance? From bsd at fluffles.net Sat May 10 17:07:39 2008 From: bsd at fluffles.net (fluffles.net) Date: Sat May 10 17:07:44 2008 Subject: industrial computer flash performance issues In-Reply-To: <4820B7EC.5040705@wkk.com> References: <4820B7EC.5040705@wkk.com> Message-ID: <4825D208.5010402@fluffles.net> WKK wrote: > I have a Nagasaki IPC industrial computer that has an 8 GB flash drive > on a 44 pin ATA connector. I have booted FreeBSD 6.2 and 7.0 via a USB > CD drive and I am getting very bad read performance. No wonder, your flash is incapable of DMA mode, at least on FreeBSD it seems. You are using PIO mode to transfer data. This degrades a modern pc to something like pre-pentium age. So unless you are able to get it working in DMA mode (UDMA33 will be fine, the slowest setting) you won't see any good performance and interrupt cpu usage will be extremely high. It will degrade your whole system. > The same CF device connected with a USB adapter (/dev/da0) gets about > 16MB/s In that case it is using DMA and not PIO. Maybe the USB adapter takes care of that? To have good flash performance you need an SSD with advanced controller chip. One example is Mtron Mobi/PRO Serial ATA SSD, which is pricey. Samsung and Transcend have new offerings too, but may offer less performance. SLC flash is better than MLC flash, but more expensive. And i suspect your flash device without controller chip to lack support of wear leveling technique, causing your flash to be weared out in just a couple of months of operation with a lot of writes in /var/log. You may enable soft updates with long update setting to delay this wearing effect. Regards, Veronica fluffles.net From ralph at imada.sdu.dk Sat May 10 20:36:58 2008 From: ralph at imada.sdu.dk (Ralph Zitz) Date: Sat May 10 20:37:23 2008 Subject: FreeBSD 7.0 SATA Controller Message-ID: <482600E4.1020809@imada.sdu.dk> I can confirm the problems mentioned originally by Shaun Sabo. I'm running FreeBSD-current on a Asus A8N-SLI Deluxe motherboard in i386 mode. Since I run "current" I'm used to certain side effects that require a livefs to undo some damage :-) I have SATA disks in raid mode which work just fine. Also I have a SATA dvdburner, which although able to boot either the install cd's and livefs cds, is not able to mount the fixit livefs ("fixit" prompt) mentioned in the previous posts. I need to attach my old ide cdrom drive to be able to do that. I'm pretty much used to this annoyance by now, but maybe it is a driver thing that needs to be looked into? Ralph Zitz. From gergely.czuczy at harmless.hu Sun May 11 10:22:09 2008 From: gergely.czuczy at harmless.hu (CZUCZY Gergely) Date: Sun May 11 10:22:13 2008 Subject: FreeBSD 7.0 SATA Controller In-Reply-To: <482600E4.1020809@imada.sdu.dk> References: <482600E4.1020809@imada.sdu.dk> Message-ID: <20080511120837.4e149721@mort.in.publishing.hu> This might not be relevant to this issue, but how is the AHCI support? Is AHCI support in 7 or -CURRENT at all? On Sat, 10 May 2008 22:09:08 +0200 Ralph Zitz wrote: > I can confirm the problems mentioned originally by Shaun Sabo. I'm > running FreeBSD-current on a Asus A8N-SLI Deluxe motherboard in i386 > mode. Since I run "current" I'm used to certain side effects that > require a livefs to undo some damage :-) I have SATA disks in raid > mode which work just fine. Also I have a SATA dvdburner, which > although able to boot either the install cd's and livefs cds, is not > able to mount the fixit livefs ("fixit" prompt) mentioned in the > previous posts. I need to attach my old ide cdrom drive to be able to > do that. I'm pretty much used to this annoyance by now, but maybe it > is a driver thing that needs to be looked into? > > Ralph Zitz. > > > _______________________________________________ > freebsd-hardware@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-hardware > To unsubscribe, send any mail to > "freebsd-hardware-unsubscribe@freebsd.org" -- Sincerely, Gergely CZUCZY, Harmless Digital mailto: gergely.czuczy@harmless.hu Legacy software is software that works. -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 187 bytes Desc: not available Url : http://lists.freebsd.org/pipermail/freebsd-hardware/attachments/20080511/483a0f7b/signature.pgp From pisymbol at gmail.com Sun May 11 13:21:26 2008 From: pisymbol at gmail.com (Alexander Sack) Date: Sun May 11 13:21:29 2008 Subject: FreeBSD 7.0 SATA Controller In-Reply-To: <20080511120837.4e149721@mort.in.publishing.hu> References: <482600E4.1020809@imada.sdu.dk> <20080511120837.4e149721@mort.in.publishing.hu> Message-ID: <3c0b01820805110554g4dbc748fu46ac0e6ae2ad536f@mail.gmail.com> On Sun, May 11, 2008 at 6:08 AM, CZUCZY Gergely wrote: > This might not be relevant to this issue, but how is the AHCI support? > Is AHCI support in 7 or -CURRENT at all? AHCI support is in 7 and -CURRENT fully working for me. What error messages if any do you see on the console? -aps From koitsu at freebsd.org Sun May 11 13:28:24 2008 From: koitsu at freebsd.org (Jeremy Chadwick) Date: Sun May 11 13:28:28 2008 Subject: FreeBSD 7.0 SATA Controller In-Reply-To: <20080511120837.4e149721@mort.in.publishing.hu> References: <482600E4.1020809@imada.sdu.dk> <20080511120837.4e149721@mort.in.publishing.hu> Message-ID: <20080511132824.GA61250@eos.sc1.parodius.com> On Sun, May 11, 2008 at 12:08:37PM +0200, CZUCZY Gergely wrote: > This might not be relevant to this issue, but how is the AHCI support? > Is AHCI support in 7 or -CURRENT at all? AHCI support is in RELENG_6 and RELENG_7. AHCI support, in at least RELENG_7, is "generic" in the sense that it should work with most AHCI implementations (such as ATI AHCI, I believe). We use AHCI on our ICH7-based systems, running both RELENG_6 and RELENG_7, without issues. -- | Jeremy Chadwick jdc at parodius.com | | Parodius Networking http://www.parodius.com/ | | UNIX Systems Administrator Mountain View, CA, USA | | Making life hard for others since 1977. PGP: 4BD6C0CB | From ralph at imada.sdu.dk Sun May 11 17:09:39 2008 From: ralph at imada.sdu.dk (Ralph Zitz) Date: Sun May 11 17:09:42 2008 Subject: FreeBSD 7.0 SATA Controller In-Reply-To: <3c0b01820805110554g4dbc748fu46ac0e6ae2ad536f@mail.gmail.com> References: <482600E4.1020809@imada.sdu.dk> <20080511120837.4e149721@mort.in.publishing.hu> <3c0b01820805110554g4dbc748fu46ac0e6ae2ad536f@mail.gmail.com> Message-ID: <4827284A.2000207@imada.sdu.dk> The exact same error as the original poster. When choosing the fixit option in the sysinstaller and then choosing CDROM/DVD to mount the livfs it fails. It works with my old ide cdrom drive however. The sysinstaller keeps on asking for the livefs cdrom to be inserted - as if it cannot "find" it. This system uses an nforce controller not ICH. > AHCI support is in 7 and -CURRENT fully working for me. What error > messages if any do you see on the console? > > -aps > From ralph at imada.sdu.dk Sun May 11 17:14:34 2008 From: ralph at imada.sdu.dk (Ralph Zitz) Date: Sun May 11 17:14:41 2008 Subject: FreeBSD 7.0 SATA Controller In-Reply-To: <4827284A.2000207@imada.sdu.dk> References: <482600E4.1020809@imada.sdu.dk> <20080511120837.4e149721@mort.in.publishing.hu> <3c0b01820805110554g4dbc748fu46ac0e6ae2ad536f@mail.gmail.com> <4827284A.2000207@imada.sdu.dk> Message-ID: <48272973.1080805@imada.sdu.dk> I might add that various Linux distributions install just fine from the sata cd drive. Ralph Zitz wrote: > The exact same error as the original poster. When choosing the fixit > option in the sysinstaller and then choosing CDROM/DVD to mount the > livfs it fails. It works with my old ide cdrom drive however. The > sysinstaller keeps on asking for the livefs cdrom to be inserted - as > if it cannot "find" it. > > This system uses an nforce controller not ICH. > >> AHCI support is in 7 and -CURRENT fully working for me. What error >> messages if any do you see on the console? >> >> -aps >> > > _______________________________________________ > freebsd-hardware@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-hardware > To unsubscribe, send any mail to > "freebsd-hardware-unsubscribe@freebsd.org" From vinnix.bsd at gmail.com Tue May 13 15:59:19 2008 From: vinnix.bsd at gmail.com (=?ISO-8859-1?Q?Vin=EDcius_Abrah=E3o?=) Date: Tue May 13 15:59:26 2008 Subject: Modem GPRS USB Message-ID: <1e31c7980805130830w15aa90a0jfe19a279a4e6a628@mail.gmail.com> Hi People, First, sorry about my poor english. I have modem usb: hsdpa/edge/gprs, but I don't know how to make this work. This is the description about the device: umass0: on uhub2 cd0 at umass-sim0 bus 0 target 0 lun 0 cd0: Removable CD-ROM SCSI-2 device cd0: 1.000MB/s transfers cd0: cd present [4623 x 2048 byte records] GEOM_LABEL: Label for provider cd0 is iso9660/ONDAMODEM At my kernel configuration file we find: device ugen # Generic device ucom # Modem UCOM device ugencom # Modem CDMA MSM device umodem # Modem COM Thanks in advice for any light. Best regards, Vinnix From rpaulo at FreeBSD.org Wed May 14 10:43:47 2008 From: rpaulo at FreeBSD.org (Rui Paulo) Date: Wed May 14 10:43:51 2008 Subject: Modem GPRS USB In-Reply-To: <1e31c7980805130830w15aa90a0jfe19a279a4e6a628@mail.gmail.com> References: <1e31c7980805130830w15aa90a0jfe19a279a4e6a628@mail.gmail.com> Message-ID: <482ABC29.9030002@FreeBSD.org> Vin?cius Abrah?o wrote: > Hi People, > > First, sorry about my poor english. > I have modem usb: hsdpa/edge/gprs, but I don't know how to > make this work. This is the description about the device: > > umass0: addr 2> on uhub2 > cd0 at umass-sim0 bus 0 target 0 lun 0 > cd0: Removable CD-ROM SCSI-2 device > cd0: 1.000MB/s transfers > cd0: cd present [4623 x 2048 byte records] > GEOM_LABEL: Label for provider cd0 is iso9660/ONDAMODEM > > At my kernel configuration file we find: > device ugen # Generic > device ucom # Modem UCOM > device ugencom # Modem CDMA MSM > device umodem # Modem COM > > Thanks in advice for any light. Since we don't have yet a way to unplug these modems from umass, you should remove umass, ugen, ucom, etc. from your kernel config file and build it as modules. I have a similar modem, and what I did was: 1) Don't have umass.ko loaded. 2) Wait a few seconds. The device will disconnect. 3) ubsa(4) should support these modems, so have it loaded, or load it now. Hope this works, -- Rui Paulo From aryeh.friedman at gmail.com Thu May 15 13:50:19 2008 From: aryeh.friedman at gmail.com (Aryeh M. Friedman) Date: Thu May 15 13:50:26 2008 Subject: software null modems Message-ID: <482C3875.1050509@gmail.com> -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 I need a null modem and all I can find is straight through db25 cables and I want to avoid the paper clip trick if I can. So is there any way to create a null modem in software only? -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.9 (FreeBSD) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iEYEARECAAYFAkgsOHUACgkQk8GFzCrQm4DC6ACeIBuAv4wzgGLCipX8G4AydvrO /Y0AoM+vRkfYelTFgwCDnYOfXXyiu/vf =bwkS -----END PGP SIGNATURE----- From aryeh.friedman at gmail.com Thu May 15 13:58:34 2008 From: aryeh.friedman at gmail.com (Aryeh M. Friedman) Date: Thu May 15 13:58:40 2008 Subject: software null modems In-Reply-To: <2403.1210859601@critter.freebsd.dk> References: <2403.1210859601@critter.freebsd.dk> Message-ID: <482C4179.3010006@gmail.com> -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Poul-Henning Kamp wrote: | In message <482C3875.1050509@gmail.com>, "Aryeh M. Friedman" writes: |> -----BEGIN PGP SIGNED MESSAGE----- |> Hash: SHA1 |> |> I need a null modem and all I can find is straight through db25 cables |> and I want to avoid the paper clip trick if I can. So is there any way |> to create a null modem in software only? | | Man 4 nmdm | Perhaps I am just dense but it seems the nmdm creates the null modem completely in software and thus can not be used across a real cable. What I mean is it seems to serve only as a way to test console i/o via a simulated null modem. What I am doing is I have a old sun sparc station 20 but no monitor and the manual says it can be configured via a null modem which implies I need a null modem between my PC and it and nmdm seems to be 100% virtual thus useless. -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.9 (FreeBSD) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iEYEARECAAYFAkgsQXgACgkQk8GFzCrQm4BAIgCcCPyMUZZnh9KQpkOMN5SmChZe KH8AniZCFjpbHdQhtGUZFfej/vuqAzVj =HR0b -----END PGP SIGNATURE----- From phk at phk.freebsd.dk Thu May 15 14:14:29 2008 From: phk at phk.freebsd.dk (Poul-Henning Kamp) Date: Thu May 15 14:14:32 2008 Subject: software null modems In-Reply-To: Your message of "Thu, 15 May 2008 09:19:49 -0400." <482C3875.1050509@gmail.com> Message-ID: <2403.1210859601@critter.freebsd.dk> In message <482C3875.1050509@gmail.com>, "Aryeh M. Friedman" writes: >-----BEGIN PGP SIGNED MESSAGE----- >Hash: SHA1 > >I need a null modem and all I can find is straight through db25 cables >and I want to avoid the paper clip trick if I can. So is there any way >to create a null modem in software only? Man 4 nmdm -- Poul-Henning Kamp | UNIX since Zilog Zeus 3.20 phk@FreeBSD.ORG | TCP/IP since RFC 956 FreeBSD committer | BSD since 4.3-tahoe Never attribute to malice what can adequately be explained by incompetence. From phk at phk.freebsd.dk Thu May 15 14:31:08 2008 From: phk at phk.freebsd.dk (Poul-Henning Kamp) Date: Thu May 15 14:31:11 2008 Subject: software null modems In-Reply-To: Your message of "Thu, 15 May 2008 09:58:17 -0400." <482C4179.3010006@gmail.com> Message-ID: <2473.1210860073@critter.freebsd.dk> In message <482C4179.3010006@gmail.com>, "Aryeh M. Friedman" writes: >|> I need a null modem and all I can find is straight through db25 cables >|> and I want to avoid the paper clip trick if I can. So is there any way >|> to create a null modem in software only? >| >| Man 4 nmdm >| >Perhaps I am just dense but it seems the nmdm creates the null modem >completely in software and thus can not be used across a real cable. No, you can't do that. -- Poul-Henning Kamp | UNIX since Zilog Zeus 3.20 phk@FreeBSD.ORG | TCP/IP since RFC 956 FreeBSD committer | BSD since 4.3-tahoe Never attribute to malice what can adequately be explained by incompetence. From freebsd at sopwith.solgatos.com Thu May 15 16:52:51 2008 From: freebsd at sopwith.solgatos.com (Dieter) Date: Thu May 15 16:52:56 2008 Subject: software null modems In-Reply-To: Your message of "Thu, 15 May 2008 09:19:49 EDT." <482C3875.1050509@gmail.com> Message-ID: <200805151556.PAA05959@sopwith.solgatos.com> > I need a null modem and all I can find is straight through db25 cables > and I want to avoid the paper clip trick if I can. So is there any way > to create a null modem in software only? Google can find lots of them, 25 pin or 9 pin, dongle or cable, ... http://www.google.com/products?as_q=&num=30&scoring=p&btnG=Search+Products&as_epq=null+modem&as_oq=&as_eq=&price1=&price2=&as_occt=any&show=dd&safe=active Products Results 1 - 30 of about 4,711 for "null modem" $1.68 and up. There is more than one null modem pinout, be sure to get the one you need. For a software solution to work, the pins would need to be bidirectional. I doubt that anyone makes a RS-232 chip with bidirectional pins. From vinnix.bsd at gmail.com Fri May 16 15:32:42 2008 From: vinnix.bsd at gmail.com (=?ISO-8859-1?Q?Vin=EDcius_Abrah=E3o?=) Date: Fri May 16 15:32:51 2008 Subject: Modem GPRS USB In-Reply-To: <482ABC29.9030002@FreeBSD.org> References: <1e31c7980805130830w15aa90a0jfe19a279a4e6a628@mail.gmail.com> <482ABC29.9030002@FreeBSD.org> Message-ID: <1e31c7980805160832j7aac492v77469255f483490f@mail.gmail.com> Hi Rui Pablo, thanks for your help: with usbsa(4) (and without umass, ugen, etc) my modem is working normaly (both: pcmcia[huawei] and usb[qualcomm3]). But now I have one other problem that need your help if possible? When I connect I recive this: May 16 12:17:08 vinnix ppp[1262]: tun0: Warning: 0.0.0.0: Change route failed: errno: No such process May 16 12:17:08 vinnix ppp[1262]: tun0: Warning: ff02:5::: Change route failed: errno: Network is unreachable The PPP fails to get a default route, after connect. Can you help-me with this? Thanks again!!! Best regards, Vinnix On Wed, May 14, 2008 at 11:17 AM, Rui Paulo wrote: > Vin?cius Abrah?o wrote: > >> Hi People, >> >> First, sorry about my poor english. >> I have modem usb: hsdpa/edge/gprs, but I don't know how to >> make this work. This is the description about the device: >> >> umass0: > 1.10/0.00, >> addr 2> on uhub2 >> cd0 at umass-sim0 bus 0 target 0 lun 0 >> cd0: Removable CD-ROM SCSI-2 device >> cd0: 1.000MB/s transfers >> cd0: cd present [4623 x 2048 byte records] >> GEOM_LABEL: Label for provider cd0 is iso9660/ONDAMODEM >> >> At my kernel configuration file we find: >> device ugen # Generic >> device ucom # Modem UCOM >> device ugencom # Modem CDMA MSM >> device umodem # Modem COM >> >> Thanks in advice for any light. >> > > Since we don't have yet a way to unplug these modems from umass, you should > remove umass, ugen, ucom, etc. from your kernel config file and build it as > modules. > > I have a similar modem, and what I did was: > 1) Don't have umass.ko loaded. > 2) Wait a few seconds. The device will disconnect. > 3) ubsa(4) should support these modems, so have it loaded, or load it now. > > Hope this works, > -- > Rui Paulo > From dwhess at banishedsouls.org Sat May 17 14:10:11 2008 From: dwhess at banishedsouls.org (David W. Hess) Date: Sat May 17 14:10:15 2008 Subject: software null modems In-Reply-To: <482C3875.1050509@gmail.com> References: <482C3875.1050509@gmail.com> Message-ID: On Thu, 15 May 2008 09:19:49 -0400, "Aryeh M. Friedman" wrote: >I need a null modem and all I can find is straight through db25 cables >and I want to avoid the paper clip trick if I can. So is there any way >to create a null modem in software only? Unless you have some really unusual hardware on at least one side, this will not be possible. With rare exceptions that occasionally show up in embedded systems, hardware UARTs all have fixed function I/O pins. This is even more the case with RS-232 (or RS-422) because signal level translation from and to logic levels is needed. It is not difficult to modify an existing cable as long as you do not need hardware flow control. Just swap pins 2 and 3. From freebsd-hardware at nedharvey.com Sat May 17 14:47:44 2008 From: freebsd-hardware at nedharvey.com (Edward Harvey) Date: Sat May 17 14:47:48 2008 Subject: Strange cardbus problem Message-ID: <006901c8b828$ecdda350$c698e9f0$@com> I am running FreeBSD pfSense.local 6.2-RELEASE-p11 FreeBSD 6.2-RELEASE-p11 On a laptop, with pcmcia network card. During bootup, the card fails to initialize (details below). But if I wait till it finishes booting, and then I yank it out and shove it back in ... then it works. Maybe there's a simple way for me to solve this problem, like some command that will disable and re-enable the cardbus? Anyway, here are the full gory details: Compaq nc6120 In BIOS: disable as much as I can, which ain't much. Usb legacy, pointing device, WLAN. In BIOS: parallel port set to "standard" which is as close to "disable" as I can get. Cardbus: D-Link 10/100 DFE-690TXD During boot, I get this: cbb0: mem 0xd0001000-0xd0001fff irq 10 at device 6.0 on pci2 cardbus0: on cbb0 pccard0: <16-bit PCCard bus> on cbb0 cbb1: mem 0xd0002000-0xd0002fff irq 10 at device 6.1 on pci2 cardbus1: on cbb1 pccard1: <16-bit PCCard bus> on cbb1 cbb alloc res fail cardbus0: Can't get memory for IO ports cbb alloc res fail rl0: couldn't map ports/memory cbb alloc res fail rl0: couldn't map ports/memory cardbus0: at device 0.0 (no driver attached) Obviously, if I attempt to do anything with the network card, it is not present. If I simply yank out the card and shove it back in, I get this: rl0: port 0x4000-0x40ff mem 0xd0011000-0xd00111ff irq 10 at device 0.0 on cardbus0 miibus1: on rl0 rlphy0: Has anyone tried this motherboard? With 7.0 boot-only disk, I haven't been able to get as far sa "Mounting root filesystem". In fact it stops just before (after probing acd0). As a matter of fact this board doesn't seem to boot FreeBSD 6.3 either, nor 5.4. (Even an old Gentoo 1.4 gets stuck pretty soon in the boot process.) So I thought there might be some BIOS trick I should try before ditching the board. Any help is welcome. -- walter pelissero http://www.pelissero.de From venture37 at hotmail.com Mon May 19 11:01:16 2008 From: venture37 at hotmail.com (Sevan / Venture37) Date: Mon May 19 11:01:48 2008 Subject: VIA EX15000G In-Reply-To: <18481.21748.522109.722808@zaphod.home.loc> References: <18481.21748.522109.722808@zaphod.home.loc> Message-ID: as a test try a daily snapshot Sevan / Venture37 _________________________________________________________________ http://clk.atdmt.com/UKM/go/msnnkmgl0010000007ukm/direct/01/ From whizzter at gmail.com Mon May 19 12:04:10 2008 From: whizzter at gmail.com (Jonas Lund) Date: Mon May 19 12:04:14 2008 Subject: VIA EX15000G In-Reply-To: <18481.21748.522109.722808@zaphod.home.loc> References: <18481.21748.522109.722808@zaphod.home.loc> Message-ID: <436c7eda0805190436r713834ecw90a9920741f72720@mail.gmail.com> I have an EN12000eg machine, running 6.2 on it. At the start however i had some crappy fake-raid card installed. If any disks were attached to it the boot would just hang. (Don't remember exactly but i think it died already in the bootloader) I think i have turned off the SW raid built into the board. no memory as to if that affected the machine however. A small note also, check that the bios reports the same amount of memory that you have installed. If it's halved then there's a bug in the chipsets that made atleast my board to use half the memory if the stick had chips with 128MB on it. If you can get a stick with 64MB chips it'll work. See www.mini-itx.com for a hopefully better description :) I'm quite happy with it now. using gmirror, 2x 3.5" disks and a silent machine that only uses 49 watts. / Jonas Lund 2008/5/19, Walter C. Pelissero : > Has anyone tried this motherboard? > > With 7.0 boot-only disk, I haven't been able to get as far sa > "Mounting root filesystem". In fact it stops just before (after > probing acd0). > > As a matter of fact this board doesn't seem to boot FreeBSD 6.3 > either, nor 5.4. (Even an old Gentoo 1.4 gets stuck pretty soon in > the boot process.) So I thought there might be some BIOS trick I > should try before ditching the board. > > Any help is welcome. > > > -- > walter pelissero > http://www.pelissero.de > _______________________________________________ > freebsd-hardware@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-hardware > To unsubscribe, send any mail to "freebsd-hardware-unsubscribe@freebsd.org" > From walter at pelissero.de Mon May 19 12:04:56 2008 From: walter at pelissero.de (Walter C. Pelissero) Date: Mon May 19 12:05:03 2008 Subject: VIA EX15000G In-Reply-To: References: <18481.21748.522109.722808@zaphod.home.loc> Message-ID: <18481.27748.848866.54513@zaphod.home.loc> Sevan / Venture37 writes: > > as a test try a daily snapshot Just tried 8.0 of May 2008. Same thing. BTW, Gentoo 1.4 eventually boots, disabling the USB disks legacy support in the BIOS. (As far as I understand, it's an emulation that lets primiteve OSs see the USB disks as IDE disks, or something like that.) This doesn't help FreeBSD, though. -- walter pelissero http://www.pelissero.de From walter at pelissero.de Mon May 19 13:08:48 2008 From: walter at pelissero.de (Walter C. Pelissero) Date: Mon May 19 13:09:02 2008 Subject: VIA EX15000G In-Reply-To: References: <18481.21748.522109.722808@zaphod.home.loc> Message-ID: <18481.31685.747754.960974@zaphod.home.loc> Christer Solskogen writes: > Have you tried updating the BIOS (if it's available)? As far as I can tell my BIOS is 1.04, while VIA, for the EX boards, provides an "upgrade" to 1.01: http://www.via.com.tw/en/products/mainboards/downloads.jsp?motherboard_id=450 I'm not sure this is funny. -- walter pelissero http://www.pelissero.de From walter at pelissero.de Mon May 19 13:27:46 2008 From: walter at pelissero.de (Walter C. Pelissero) Date: Mon May 19 13:27:51 2008 Subject: VIA EX15000G In-Reply-To: <436c7eda0805190436r713834ecw90a9920741f72720@mail.gmail.com> References: <18481.21748.522109.722808@zaphod.home.loc> <436c7eda0805190436r713834ecw90a9920741f72720@mail.gmail.com> Message-ID: <18481.32827.595664.724170@zaphod.home.loc> Jonas Lund writes: > I have an EN12000eg machine, running 6.2 on it. At the start however i > had some crappy fake-raid card installed. If any disks were attached > to it the boot would just hang. (Don't remember exactly but i think it > died already in the bootloader) No additional card. > I think i have turned off the SW raid built into the board. no memory > as to if that affected the machine however. I'm not aware of any RAID implemented in the motherboard's chipset. > A small note also, check that the bios reports the same amount of > memory that you have installed. If it's halved then there's a bug in > the chipsets that made atleast my board to use half the memory if the > stick had chips with 128MB on it. If you can get a stick with 64MB > chips it'll work. See www.mini-itx.com for a hopefully better > description :) I've installed a 1GB stick. It looks as it is seen correctly (real memory = 958MB, avail memory = 922MB). > I'm quite happy with it now. using gmirror, 2x 3.5" disks and a silent > machine that only uses 49 watts. I was quite happy with an M6000 as well. -- walter pelissero http://www.pelissero.de From freebsd at sopwith.solgatos.com Tue May 20 18:29:15 2008 From: freebsd at sopwith.solgatos.com (Dieter) Date: Tue May 20 18:29:20 2008 Subject: Open Graphics Project is now taking pre-orders Message-ID: <200805201826.SAA25413@sopwith.solgatos.com> The Open Graphics Project is now taking pre-orders for the OGD1 development board. This PCI-X board has 2 FPGA chips and video outputs (2 heads). List price is $1500, the first 100 orders get a $100 discount. There are developer discounts available, so someone writing a BSD device driver, or working on X11 support, etc. could get a board for $700-1000. There is a variety of development work that needs to be done. Profits from the OGD1 board will be used to bootstrap other FLOSS friendly hardware projects (not limited to graphics). If you are tired of undocumented hardware, here is a chance to do something about it. The product info page: http://www.traversaltech.com/products.phtml The FAQ: http://www.traversaltech.com/ogd1p_faq2.phtml The order page: http://www.traversaltech.com/store.phtml For a developer discount, contact the Open Hardware Foundation: http://www.openhardwarefoundation.org/ From violentsense at gmail.com Thu May 22 14:24:52 2008 From: violentsense at gmail.com (Nifty) Date: Thu May 22 14:24:58 2008 Subject: SATA dvd-r/rw drives on ICH9R/ICH9R doesn't work in FreeBSD 7/8 Message-ID: <000001c8bc13$be9d27b0$1801a8c0@hellfire> Hi! I have two PC's with ICH8R and ICH9R sata controllers. Controller mode set to sata, no AHCI or RAID. Two SATA dvd-r/rw drivers present, SONY-NEC Optiarc AD-7170S, AD-7203S If I try to install FreeBSD 7.0R or FreeBSD 8.0 CURRENT from CD - when kernel boot and try to use CD, I see messages like this: ------------------------------------------------------ acd1: TIMEOUT - READ_BIG retrying (1 retries left) acd1: TIMEOUT - READ_BIG retrying (0 retries left) acd1: TIMEOUT - READ_BIG retrying (repeated two times) ------------------------------------------------------ And then nothing - installation can't recognize CD disk in drive, and I can't install FreeBSD. Regards, Alexandr. From maciej at suszko.eu Thu May 22 19:40:40 2008 From: maciej at suszko.eu (Maciej Suszko) Date: Thu May 22 19:40:48 2008 Subject: SATA dvd-r/rw drives on ICH9R/ICH9R doesn't work in FreeBSD 7/8 In-Reply-To: <000001c8bc13$be9d27b0$1801a8c0@hellfire> References: <000001c8bc13$be9d27b0$1801a8c0@hellfire> Message-ID: <20080522211355.77d66de3@suszko.eu> "Nifty" wrote: > Hi! > > I have two PC's with ICH8R and ICH9R sata controllers. Controller > mode set to sata, no AHCI or RAID. > Two SATA dvd-r/rw drivers present, SONY-NEC Optiarc AD-7170S, AD-7203S > If I try to install FreeBSD 7.0R or FreeBSD 8.0 CURRENT from CD - when > kernel boot and try to use CD, I see > messages like this: > > ------------------------------------------------------ > acd1: TIMEOUT - READ_BIG retrying (1 retries left) > acd1: TIMEOUT - READ_BIG retrying (0 retries left) > acd1: TIMEOUT - READ_BIG retrying > > (repeated two times) > ------------------------------------------------------ > > And then nothing - installation can't recognize CD disk in drive, and > I can't install FreeBSD. Have you tried to wait few minutes? I noticed similar errors but within few minutes the installer started and I had no problems installing 7.0R (motherboard with ICH9, some noname PATA DVD-R drive) -- regards, Maciej Suszko. From solarux at hotmail.com Fri May 23 07:55:01 2008 From: solarux at hotmail.com (Rick Nekus) Date: Fri May 23 07:55:05 2008 Subject: Open Graphics Project is now taking pre-orders In-Reply-To: <200805201826.SAA25413@sopwith.solgatos.com> References: <200805201826.SAA25413@sopwith.solgatos.com> Message-ID: Hi, I'm just curious here, but why PCI-X, why not PCI-EXpress ? or is this obviously for development reasons. > To: freebsd-drivers@freebsd.org; freebsd-hardware@freebsd.org; freebsd-multimedia@freebsd.org> Date: Tue, 20 May 2008 11:26:31 +0100> From: freebsd@sopwith.solgatos.com> CC: > Subject: Open Graphics Project is now taking pre-orders> > The Open Graphics Project is now taking pre-orders for> the OGD1 development board. This PCI-X board has 2 FPGA chips> and video outputs (2 heads). List price is $1500, the> first 100 orders get a $100 discount. There are developer> discounts available, so someone writing a BSD device driver,> or working on X11 support, etc. could get a board for $700-1000.> There is a variety of development work that needs to be done.> Profits from the OGD1 board will be used to bootstrap other FLOSS> friendly hardware projects (not limited to graphics). If you are> tired of undocumented hardware, here is a chance to do something> about it.> > The product info page:> http://www.traversaltech.com/products.phtml> > The FAQ:> http://www.traversaltech.com/ogd1p_faq2.phtml> > The order page:> http://www.traversaltech.com/store.phtml> > For a developer discount, contact the Open Hardware Foundation:> http://www.openhardwarefoundation.org/> _______________________________________________> freebsd-multimedia@freebsd.org mailing list> http://lists.freebsd.org/mailman/listinfo/freebsd-multimedia> To unsubscribe, send any mail to "freebsd-multimedia-unsubscribe@freebsd.org" _________________________________________________________________ If you like crossword puzzles, then you'll love Flexicon, a game which combines four overlapping crossword puzzles into one! http://g.msn.ca/ca55/208 From freebsd at sopwith.solgatos.com Fri May 23 15:22:45 2008 From: freebsd at sopwith.solgatos.com (Dieter) Date: Fri May 23 15:22:57 2008 Subject: Open Graphics Project is now taking pre-orders In-Reply-To: Your message of "Fri, 23 May 2008 07:43:01 -0000." Message-ID: <200805231515.PAA10055@sopwith.solgatos.com> > I'm just curious here, but why PCI-X, why not PCI-EXpress ? > or is this obviously for development reasons. According to the FAQ, While most graphics cards now fit in PCI Express slots, PCI is more popular with users of FPGA kits. We have identified the parts necessary to support PCI Express, so if there is demand, we can build them. In the mean time, we need to sell the PCI version OGD1 to bootstrap our efforts. PCI-X is backward compatible with your 32-bit 33MHz PCI slots, and OGD1 has been tested with several PC motherboards. Note that some PC motherboards may position components so that they interfere with the "extended" part of the PCI card edge for some slots. OGD1 is 6.875in long and 4.2in wide (17.46cm x 10.67cm). Some small form-factor systems do not provide enough room in one or both dimensions. There is a development advantage to PCI. PCI is a bus, so it is easy to sniff the bus if things aren't working. There has been some discussion about writing software to turn the OGD1 into a PCI bus sniffer, for developing other boards. If you are interested in buying a PCIe version of OGD1, OGP needs to hear about it. From koitsu at FreeBSD.org Fri May 23 15:39:37 2008 From: koitsu at FreeBSD.org (Jeremy Chadwick) Date: Fri May 23 15:39:45 2008 Subject: Open Graphics Project is now taking pre-orders In-Reply-To: <200805231515.PAA10055@sopwith.solgatos.com> References: <200805231515.PAA10055@sopwith.solgatos.com> Message-ID: <20080523153937.GA40374@eos.sc1.parodius.com> On Fri, May 23, 2008 at 08:15:53AM +0100, Dieter wrote: > > I'm just curious here, but why PCI-X, why not PCI-EXpress ? > > or is this obviously for development reasons. > > According to the FAQ, > > While most graphics cards now fit in PCI Express slots, > PCI is more popular with users of FPGA kits. We have > identified the parts necessary to support PCI Express, > so if there is demand, we can build them. In the mean > time, we need to sell the PCI version OGD1 to bootstrap > our efforts. > > PCI-X is backward compatible with your 32-bit 33MHz PCI slots, > and OGD1 has been tested with several PC motherboards. Note > that some PC motherboards may position components so that they > interfere with the "extended" part of the PCI card edge for > some slots. OGD1 is 6.875in long and 4.2in wide > (17.46cm x 10.67cm). Some small form-factor systems do not > provide enough room in one or both dimensions. > > There is a development advantage to PCI. PCI is a bus, so it is easy > to sniff the bus if things aren't working. There has been some > discussion about writing software to turn the OGD1 into a PCI bus > sniffer, for developing other boards. > > If you are interested in buying a PCIe version of OGD1, OGP needs to > hear about it. I think what people (not just here, but folks on Slashdot as well) want to know is: is the PCI-X choice *purely* for development reasons, e.g. will the retail/non-development version (read: transistor-based, no FPGA) of the card be PCIe? If the manufacturer plans on keeping everything PCI-X -- dev cards and commercial/retail cards -- they are making a *huge* mistake. -- | Jeremy Chadwick jdc at parodius.com | | Parodius Networking http://www.parodius.com/ | | UNIX Systems Administrator Mountain View, CA, USA | | Making life hard for others since 1977. PGP: 4BD6C0CB | From freebsd at sopwith.solgatos.com Fri May 23 16:54:58 2008 From: freebsd at sopwith.solgatos.com (Dieter) Date: Fri May 23 16:55:05 2008 Subject: Open Graphics Project is now taking pre-orders In-Reply-To: Your message of "Fri, 23 May 2008 08:39:37 PDT." <20080523153937.GA40374@eos.sc1.parodius.com> Message-ID: <200805231652.QAA05864@sopwith.solgatos.com> > I think what people (not just here, but folks on Slashdot as well) want > to know is: is the PCI-X choice *purely* for development reasons, e.g. > will the retail/non-development version (read: transistor-based, no > FPGA) of the card be PCIe? > > If the manufacturer plans on keeping everything PCI-X -- dev cards and > commercial/retail cards -- they are making a *huge* mistake. The plan, as I understand it, is: Develop GPU logic using OGD1 boards. Sell as many OGD1 boards as possible to raise money needed (estimated at US$2M) to fabricate ASIC. Probably do other FLOSS friendly hardware projects to raise money for ASIC. (Ideas welcome) Build OGC boards with ASIC, no FPGA. The ASICs are expected to sell in *much* larger quantities than the FPGA boards. I'm 99.9% sure that the ASIC based OGC boards will be available as PCIe. Possibly PCI or PCI-X and AGP as well, and the bare ASIC chips will be available for embedded applications (PDAs, kiosks, etc.). The big hurdle is raising the US$2M needed to fab the ASIC. From gpalmer at freebsd.org Fri May 23 17:11:25 2008 From: gpalmer at freebsd.org (Gary Palmer) Date: Fri May 23 17:11:31 2008 Subject: Open Graphics Project is now taking pre-orders In-Reply-To: <20080523153937.GA40374@eos.sc1.parodius.com> References: <200805231515.PAA10055@sopwith.solgatos.com> <20080523153937.GA40374@eos.sc1.parodius.com> Message-ID: <20080523171124.GB1142@in-addr.com> On Fri, May 23, 2008 at 08:39:37AM -0700, Jeremy Chadwick wrote: > On Fri, May 23, 2008 at 08:15:53AM +0100, Dieter wrote: > > > I'm just curious here, but why PCI-X, why not PCI-EXpress ? > > > or is this obviously for development reasons. > > > > According to the FAQ, > > > > While most graphics cards now fit in PCI Express slots, > > PCI is more popular with users of FPGA kits. We have > > identified the parts necessary to support PCI Express, > > so if there is demand, we can build them. In the mean > > time, we need to sell the PCI version OGD1 to bootstrap > > our efforts. > > > > PCI-X is backward compatible with your 32-bit 33MHz PCI slots, > > and OGD1 has been tested with several PC motherboards. Note > > that some PC motherboards may position components so that they > > interfere with the "extended" part of the PCI card edge for > > some slots. OGD1 is 6.875in long and 4.2in wide > > (17.46cm x 10.67cm). Some small form-factor systems do not > > provide enough room in one or both dimensions. > > > > There is a development advantage to PCI. PCI is a bus, so it is easy > > to sniff the bus if things aren't working. There has been some > > discussion about writing software to turn the OGD1 into a PCI bus > > sniffer, for developing other boards. > > > > If you are interested in buying a PCIe version of OGD1, OGP needs to > > hear about it. > > I think what people (not just here, but folks on Slashdot as well) want > to know is: is the PCI-X choice *purely* for development reasons, e.g. > will the retail/non-development version (read: transistor-based, no > FPGA) of the card be PCIe? > > If the manufacturer plans on keeping everything PCI-X -- dev cards and > commercial/retail cards -- they are making a *huge* mistake. This is answered on their website. The reason they chose PCI-X was that they can slap a PCIe to PCI-X bridge on it without having to choose new FPGAs and respin the boards (which would delay things even more) http://wiki.opengraphics.org/tiki-index.php?page=OGPN20#PCIe (amongst many others) http://www.google.com/search?q=site%3Awiki.opengraphics.org+pcie Regards, Gary P.S. isn't this thread violating the crossposting rules? From derek.graham at att.net Tue May 27 09:07:17 2008 From: derek.graham at att.net (Derek Graham) Date: Tue May 27 09:07:21 2008 Subject: Microsoft LifeCam VX-1000 Support Message-ID: <200805270340.06728.derek.graham@att.net> I got suckered into grabbing this cheap webcam and now that I am back in a non-windows environment I am wondering if there is any hope for drivers for a MS product? :p Any advice on a webcam that wont give me too much grief and not cost too much either? Also I wanted to see on external usb dvd burners i saw a LG External USB DVD Writer and a HP External USB DVD Writer. What would you guys recommend for that? From koitsu at FreeBSD.org Tue May 27 09:10:46 2008 From: koitsu at FreeBSD.org (Jeremy Chadwick) Date: Tue May 27 09:10:52 2008 Subject: Microsoft LifeCam VX-1000 Support In-Reply-To: <200805270340.06728.derek.graham@att.net> References: <200805270340.06728.derek.graham@att.net> Message-ID: <20080527091046.GA35640@eos.sc1.parodius.com> On Tue, May 27, 2008 at 03:40:06AM -0500, Derek Graham wrote: > I got suckered into grabbing this cheap webcam and now that I am back in a > non-windows environment I am wondering if there is any hope for drivers for a > MS product? :p I don't believe FreeBSD has support for this device. Linux, on the other hand, does: http://mxhaard.free.fr/spca5xx.html -- | Jeremy Chadwick jdc at parodius.com | | Parodius Networking http://www.parodius.com/ | | UNIX Systems Administrator Mountain View, CA, USA | | Making life hard for others since 1977. PGP: 4BD6C0CB | From dean at fragfest.com.au Wed May 28 01:20:10 2008 From: dean at fragfest.com.au (Dean Hamstead) Date: Wed May 28 01:20:15 2008 Subject: Microsoft LifeCam VX-1000 Support In-Reply-To: <200805270340.06728.derek.graham@att.net> References: <200805270340.06728.derek.graham@att.net> Message-ID: <483C9618.9050907@fragfest.com.au> 260 webcams supported and counting. http://mxhaard.free.fr/index.html not sure if you can launch from there to find freebsd support Dean Derek Graham wrote: > I got suckered into grabbing this cheap webcam and now that I am back in a > non-windows environment I am wondering if there is any hope for drivers for a > MS product? :p Any advice on a webcam that wont give me too much grief and > not cost too much either? Also I wanted to see on external usb dvd burners i > saw a LG External USB DVD Writer and a HP External USB DVD Writer. What would > you guys recommend for that? > _______________________________________________ > freebsd-hardware@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-hardware > To unsubscribe, send any mail to "freebsd-hardware-unsubscribe@freebsd.org" > -- http://fragfest.com.au From samflanker at gmail.com Thu May 29 11:46:40 2008 From: samflanker at gmail.com (sam) Date: Thu May 29 11:46:50 2008 Subject: error messages dmesg/acpi on Message-ID: <483E9793.6080409@gmail.com> dmesg output ================================================== # cat /var/run/dmesg.boot Copyright (c) 1992-2008 The FreeBSD Project. Copyright (c) 1979, 1980, 1983, 1986, 1988, 1989, 1991, 1992, 1993, 1994 The Regents of the University of California. All rights reserved. FreeBSD is a registered trademark of The FreeBSD Foundation. FreeBSD 7.0-STABLE #0: Wed May 21 18:24:33 MSD 2008 root@stone:/usr/obj/usr/src/sys/STONE Timecounter "i8254" frequency 1193182 Hz quality 0 CPU: Intel(R) Pentium(R) III CPU family 1400MHz (1396.45-MHz 686-class CPU) Origin = "GenuineIntel" Id = 0x6b1 Stepping = 1 Features=0x383fbff real memory = 1610350592 (1535 MB) avail memory = 1568567296 (1495 MB) ACPI APIC Table: FreeBSD/SMP: Multiprocessor System Detected: 2 CPUs cpu0 (BSP): APIC ID: 3 cpu1 (AP): APIC ID: 0 MADT: Forcing active-low polarity and level trigger for SCI ioapic0 irqs 0-15 on motherboard ioapic1 irqs 16-31 on motherboard lapic3: Forcing LINT1 to edge trigger kbd1 at kbdmux0 acpi0: on motherboard ACPI Warning (dswload-0794): Type override - [DEB_] had invalid type (Integer) for Scope operator, changed to (Scope) [20070320] ACPI Warning (dswload-0794): Type override - [MLIB] had invalid type (Integer) for Scope operator, changed to (Scope) [20070320] ACPI Warning (dswload-0794): Type override - [DATA] had invalid type (String) for Scope operator, changed to (Scope) [20070320] ACPI Warning (dswload-0794): Type override - [SIO_] had invalid type (String) for Scope operator, changed to (Scope) [20070320] ACPI Warning (dswload-0794): Type override - [SB__] had invalid type (String) for Scope operator, changed to (Scope) [20070320] ACPI Warning (dswload-0794): Type override - [PM__] had invalid type (String) for Scope operator, changed to (Scope) [20070320] ACPI Warning (dswload-0794): Type override - [ICNT] had invalid type (String) for Scope operator, changed to (Scope) [20070320] ACPI Warning (dswload-0794): Type override - [ACPI] had invalid type (String) for Scope operator, changed to (Scope) [20070320] ACPI Warning (dswload-0794): Type override - [LEDP] had invalid type (String) for Scope operator, changed to (Scope) [20070320] ACPI Warning (dswload-0794): Type override - [WUES] had invalid type (String) for Scope operator, changed to (Scope) [20070320] ACPI Warning (dswload-0794): Type override - [WUSE] had invalid type (String) for Scope operator, changed to (Scope) [20070320] ACPI Warning (dswload-0794): Type override - [CSB5] had invalid type (String) for Scope operator, changed to (Scope) [20070320] ACPI Warning (dswload-0794): Type override - [PM__] had invalid type (String) for Scope operator, changed to (Scope) [20070320] ACPI Warning (dswload-0794): Type override - [BIOS] had invalid type (Integer) for Scope operator, changed to (Scope) [20070320] ACPI Warning (dswload-0794): Type override - [CMOS] had invalid type (Integer) for Scope operator, changed to (Scope) [20070320] acpi0: [ITHREAD] ACPI Error (evxfevnt-0288): Could not enable GlobalLock event [20070320] ACPI Warning (evxface-0235): Could not enable fixed event 1 [20070320] ACPI Error (evmisc-0487): No response from Global Lock hardware, disabling lock [20070320] acpi0: Power Button (fixed) Timecounter "ACPI-safe" frequency 3579545 Hz quality 850 acpi_timer0: <32-bit timer at 3.579545MHz> port 0x508-0x50b on acpi0 cpu0: on acpi0 cpu1: on acpi0 pcib0: port 0xcf8-0xcff on acpi0 pci0: on pcib0 atapci0: port 0x1400-0x1407,0x1408-0x140b,0x1410-0x1417,0x140c-0x140f,0x1440-0x147f mem 0xfe7a0000-0xfe7bffff irq 19 at device 2.0 on pci0 atapci0: [ITHREAD] ata2: on atapci0 ata2: [ITHREAD] ata3: on atapci0 ata3: [ITHREAD] fxp0: port 0x1480-0x14bf mem 0xfe790000-0xfe790fff,0xfe760000-0xfe77ffff irq 21 at device 3.0 on pci0 miibus0: on fxp0 inphy0: PHY 1 on miibus0 inphy0: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, auto fxp0: Ethernet address: 00:03:47:a5:6e:c9 fxp0: [ITHREAD] fxp1: port 0x14c0-0x14ff mem 0xfe750000-0xfe750fff,0xfe720000-0xfe73ffff irq 20 at device 4.0 on pci0 miibus1: on fxp1 inphy1: PHY 1 on miibus1 inphy1: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, auto fxp1: Ethernet address: 00:03:47:a5:6e:cb fxp1: [ITHREAD] vgapci0: port 0x1000-0x10ff mem 0xfd000000-0xfdffffff,0xfe7f0000-0xfe7f0fff irq 18 at device 12.0 on pci0 isab0: at device 15.0 on pci0 isa0: on isab0 atapci1: port 0x1f0-0x1f7,0x3f6,0x170-0x177,0x376,0x3a0-0x3af,0x410-0x413 at device 15.1 on pci0 ata0: on atapci1 ata0: [ITHREAD] ata1: on atapci1 ata1: [ITHREAD] pcib1: on acpi0 pci1: on pcib1 pcib2: on acpi0 pci2: on pcib2 atkbdc0: port 0x60,0x64 irq 1 on acpi0 atkbd0: irq 1 on atkbdc0 kbd0 at atkbd0 atkbd0: [GIANT-LOCKED] atkbd0: [ITHREAD] sio0: <16550A-compatible COM port> port 0x3f8-0x3ff irq 4 flags 0x10 on acpi0 sio0: type 16550A sio0: [FILTER] sio1: <16550A-compatible COM port> port 0x2f8-0x2ff irq 3 on acpi0 sio1: type 16550A sio1: [FILTER] pmtimer0 on isa0 orm0: at iomem 0xc0000-0xc7fff,0xc8000-0xd07ff,0xe4000-0xe7fff pnpid ORM0000 on isa0 sc0: at flags 0x100 on isa0 sc0: VGA <16 virtual consoles, flags=0x300> vga0: at port 0x3c0-0x3df iomem 0xa0000-0xbffff on isa0 Timecounters tick every 1.000 msec ad4: 114473MB at ata2-master UDMA100 ad6: 114473MB at ata3-master UDMA100 ar0: 114440MB status: READY ar0: disk0 READY (master) using ad4 at ata2-master ar0: disk1 READY (mirror) using ad6 at ata3-master lapic0: Forcing LINT1 to edge trigger SMP: AP CPU #1 Launched! Trying to mount root from ufs:/dev/ar0s1a ================================================== part of kenv output ================================================== smbios.bios.reldate="10/18/2001" smbios.bios.vendor="Intel Corporation" smbios.bios.version="SCB20.86B.0013.P02.0110181617 " smbios.chassis.maker=" " smbios.chassis.serial=" " smbios.chassis.tag=" " smbios.chassis.version=" " smbios.planar.maker="Intel" smbios.planar.product="SCB2A" smbios.planar.serial="KKC115000476" smbios.planar.version="A46043-607" smbios.socket.enabled="2" smbios.socket.populated="2" smbios.system.maker="Intel" smbios.system.product="SCB20" ================================================== /Vladimir Ermakov From derek.graham at att.net Thu May 29 19:32:08 2008 From: derek.graham at att.net (Derek Graham) Date: Thu May 29 19:32:14 2008 Subject: Microsoft LifeCam VX-1000 Support kldload gspca (gspca.ko: No such file or directory) In-Reply-To: <483C9618.9050907@fragfest.com.au> References: <200805270340.06728.derek.graham@att.net> <483C9618.9050907@fragfest.com.au> Message-ID: <200805291431.40246.derek.graham@att.net> on Tuesday 27 May 2008Tuesday 27 May 2008 Dean Hamstead Dean Hamstead wrote: > 260 webcams supported and counting. > > http://mxhaard.free.fr/index.html > > not sure if you can launch from there to find freebsd support > > Dean > > Derek Graham wrote: > > I got suckered into grabbing this cheap webcam and now that I am back in > > a non-windows environment I am wondering if there is any hope for drivers > > for a MS product? :p Any advice on a webcam that wont give me too much > > grief and not cost too much either? Also I wanted to see on external usb > > dvd burners i saw a LG External USB DVD Writer and a HP External USB DVD > > Writer. What would you guys recommend for that? > > _______________________________________________ > > freebsd-hardware@freebsd.org mailing list > > http://lists.freebsd.org/mailman/listinfo/freebsd-hardware > > To unsubscribe, send any mail to > > "freebsd-hardware-unsubscribe@freebsd.org" Ok thanks I tried it but got these errors: Mulder# kldstat Id Refs Address Size Name 1 25 0xc0400000 64bf3c kernel 2 1 0xc0a4c000 85e4 linprocfs.ko 3 6 0xc0a55000 29868 linux.ko 4 1 0xc0a7f000 8a4c snd_es137x.ko 5 1 0xc0a88000 80dcf8 nvidia.ko 6 1 0xc1296000 4cb0 atapicam.ko 8 1 0xc133d000 6a2b4 acpi.ko 9 1 0xc4898000 e000 fuse.ko 10 1 0xc4b50000 9000 vmmon_up.ko 11 1 0xc4b59000 2000 vmnet.ko 12 1 0xc4b5b000 5000 if_tap.ko 13 1 0xc4b69000 2000 rtc.ko Mulder# kldxref -v /boot/modules/ /boot/modules/nvidia.ko kldxref: /boot/modules/nvidia.ko: 82017 REL entries /boot/modules/gspca.ko kldxref: /boot/modules/gspca.ko: 3828 REL entries /boot/modules/pwc.ko kldxref: /boot/modules/pwc.ko: 388 REL entries /boot/modules/lhint.eyS8fW kldxref: elf_open(/boot/modules/lhint.eyS8fW): Inappropriate file type or format Mulder# kldload /boot/modules/gspca.ko kldload: can't load /boot/modules/gspca.ko: No such file or directory Mulder# kldload gspca kldload: can't load gspca: No such file or directory Mulder# kldload gspca.ko kldload: can't load gspca.ko: No such file or directory Sincerely, Derek A. Graham From derek.graham at att.net Thu May 29 19:58:48 2008 From: derek.graham at att.net (Derek Graham) Date: Thu May 29 19:58:52 2008 Subject: Microsoft LifeCam VX-1000 Support kldload gspca (gspca.ko: No such file or directory) In-Reply-To: <483C9618.9050907@fragfest.com.au> References: <200805270340.06728.derek.graham@att.net> <483C9618.9050907@fragfest.com.au> Message-ID: <200805291431.40246.derek.graham@att.net> on Tuesday 27 May 2008Tuesday 27 May 2008 Dean Hamstead Dean Hamstead wrote: > 260 webcams supported and counting. > > http://mxhaard.free.fr/index.html > > not sure if you can launch from there to find freebsd support > > Dean > > Derek Graham wrote: > > I got suckered into grabbing this cheap webcam and now that I am back in > > a non-windows environment I am wondering if there is any hope for drivers > > for a MS product? :p Any advice on a webcam that wont give me too much > > grief and not cost too much either? Also I wanted to see on external usb > > dvd burners i saw a LG External USB DVD Writer and a HP External USB DVD > > Writer. What would you guys recommend for that? > > _______________________________________________ > > freebsd-hardware@freebsd.org mailing list > > http://lists.freebsd.org/mailman/listinfo/freebsd-hardware > > To unsubscribe, send any mail to > > "freebsd-hardware-unsubscribe@freebsd.org" Ok thanks I tried it but got these errors: Mulder# kldstat Id Refs Address Size Name 1 25 0xc0400000 64bf3c kernel 2 1 0xc0a4c000 85e4 linprocfs.ko 3 6 0xc0a55000 29868 linux.ko 4 1 0xc0a7f000 8a4c snd_es137x.ko 5 1 0xc0a88000 80dcf8 nvidia.ko 6 1 0xc1296000 4cb0 atapicam.ko 8 1 0xc133d000 6a2b4 acpi.ko 9 1 0xc4898000 e000 fuse.ko 10 1 0xc4b50000 9000 vmmon_up.ko 11 1 0xc4b59000 2000 vmnet.ko 12 1 0xc4b5b000 5000 if_tap.ko 13 1 0xc4b69000 2000 rtc.ko Mulder# kldxref -v /boot/modules/ /boot/modules/nvidia.ko kldxref: /boot/modules/nvidia.ko: 82017 REL entries /boot/modules/gspca.ko kldxref: /boot/modules/gspca.ko: 3828 REL entries /boot/modules/pwc.ko kldxref: /boot/modules/pwc.ko: 388 REL entries /boot/modules/lhint.eyS8fW kldxref: elf_open(/boot/modules/lhint.eyS8fW): Inappropriate file type or format Mulder# kldload /boot/modules/gspca.ko kldload: can't load /boot/modules/gspca.ko: No such file or directory Mulder# kldload gspca kldload: can't load gspca: No such file or directory Mulder# kldload gspca.ko kldload: can't load gspca.ko: No such file or directory Sincerely, Derek A. Graham From gmarkley at greatbaysoftware.com Fri May 30 16:07:14 2008 From: gmarkley at greatbaysoftware.com (Gabriel Markley) Date: Fri May 30 16:07:19 2008 Subject: Intel integrated RAID for the SR2500ALLXR freebsd support Message-ID: <4840239E.2020607@greatbaysoftware.com> Hello, I am a systems engineer for Great Bay Software we are looking to move our servers over to freebsd. I am having trouble finding any documentation on using freebsd with Intel integrated RAID for the SR2500ALLXR. I need to find out if there is a driver available? And can I pull status of the raid from it? i.e. H.D. failure and any other possible problems... Other then look in the bios and or look at the front plane to see if a drive has failed. I am going to add the detailed specs that I was given below: Active Mid-plane with SAS /SAS RAID Support The active mid-plane is used to provide SAS / SAS RAID support. It has integrated on to it an Intel IOP80333 IO processor and an LSI* LSLSAS1068 3Gb/s SAS controller. Together they provide support for up to six SAS drives in this chassis. By default, this mid-plane option provides software RAID levels 0, 1, and 10 utilizing Intel? Embedded RAID Technology II. With the installation of optional RAID enablement devices, the mid-plane can support hardware RAID levels 0, 1, 5, 10, and 50. The mid-plane attaches to the hot-swap backplane by two card edge connectors which eliminates the need for any hard drive cables. The following sub-sections describe the board level SAS / SAS RAID functionality. We use the RAID activation key with dedicated memory and battery backup to provide HW RAID level 10 Any help would be great. Again thank you for taking the time to point me in the right direction. -- Gabriel Markley Systems Engineer Great Bay Software, Inc. v: 603.766.6146 | m: 603.498-3513 | f: 603.430.0713 | e: gmarkley@GreatBaySoftware.com From koitsu at FreeBSD.org Fri May 30 16:12:50 2008 From: koitsu at FreeBSD.org (Jeremy Chadwick) Date: Fri May 30 16:13:01 2008 Subject: Intel integrated RAID for the SR2500ALLXR freebsd support In-Reply-To: <4840239E.2020607@greatbaysoftware.com> References: <4840239E.2020607@greatbaysoftware.com> Message-ID: <20080530161249.GA46028@eos.sc1.parodius.com> On Fri, May 30, 2008 at 11:56:14AM -0400, Gabriel Markley wrote: > I am a systems engineer for Great Bay Software we are looking to move our > servers over to freebsd. > I am having trouble finding any documentation on using freebsd with Intel > integrated RAID for the SR2500ALLXR. > I need to find out if there is a driver available? > And can I pull status of the raid from it? i.e. H.D. failure and any other > possible problems... > Other then look in the bios and or look at the front plane to see if a > drive has failed. > > I am going to add the detailed specs that I was given below: > Active Mid-plane with SAS /SAS RAID Support > The active mid-plane is used to provide SAS / SAS RAID support. It has > integrated on to it an > Intel IOP80333 IO processor and an LSI* LSLSAS1068 3Gb/s SAS controller. This would probably fall under the mpt(4) or mfi(4) driver. I don't know if either of those drivers have support for that exact model of LSI controller, however. Best bet would be to get a FreeBSD livefs or bootonly CD and then see what is (or is not) detected. -- | Jeremy Chadwick jdc at parodius.com | | Parodius Networking http://www.parodius.com/ | | UNIX Systems Administrator Mountain View, CA, USA | | Making life hard for others since 1977. PGP: 4BD6C0CB | From jhb at freebsd.org Fri May 30 16:26:32 2008 From: jhb at freebsd.org (John Baldwin) Date: Fri May 30 16:26:34 2008 Subject: Microsoft LifeCam VX-1000 Support kldload gspca (gspca.ko: No such file or directory) In-Reply-To: <200805291431.40246.derek.graham@att.net> References: <200805270340.06728.derek.graham@att.net> <483C9618.9050907@fragfest.com.au> <200805291431.40246.derek.graham@att.net> Message-ID: <200805301200.50190.jhb@freebsd.org> On Thursday 29 May 2008 03:31:39 pm Derek Graham wrote: > on Tuesday 27 May 2008Tuesday 27 May 2008 Dean Hamstead Dean Hamstead wrote: > > > 260 webcams supported and counting. > > > > http://mxhaard.free.fr/index.html > > > > not sure if you can launch from there to find freebsd support > > > > Dean > > > > Derek Graham wrote: > > > I got suckered into grabbing this cheap webcam and now that I am back in > > > a non-windows environment I am wondering if there is any hope for drivers > > > for a MS product? :p Any advice on a webcam that wont give me too much > > > grief and not cost too much either? Also I wanted to see on external usb > > > dvd burners i saw a LG External USB DVD Writer and a HP External USB DVD > > > Writer. What would you guys recommend for that? > > > _______________________________________________ > > > freebsd-hardware@freebsd.org mailing list > > > http://lists.freebsd.org/mailman/listinfo/freebsd-hardware > > > To unsubscribe, send any mail to > > > "freebsd-hardware-unsubscribe@freebsd.org" > Ok thanks I tried it but got these errors: > Mulder# kldstat > Id Refs Address Size Name > 1 25 0xc0400000 64bf3c kernel > 2 1 0xc0a4c000 85e4 linprocfs.ko > 3 6 0xc0a55000 29868 linux.ko > 4 1 0xc0a7f000 8a4c snd_es137x.ko > 5 1 0xc0a88000 80dcf8 nvidia.ko > 6 1 0xc1296000 4cb0 atapicam.ko > 8 1 0xc133d000 6a2b4 acpi.ko > 9 1 0xc4898000 e000 fuse.ko > 10 1 0xc4b50000 9000 vmmon_up.ko > 11 1 0xc4b59000 2000 vmnet.ko > 12 1 0xc4b5b000 5000 if_tap.ko > 13 1 0xc4b69000 2000 rtc.ko > > Mulder# kldxref -v /boot/modules/ > /boot/modules/nvidia.ko > kldxref: /boot/modules/nvidia.ko: 82017 REL entries > /boot/modules/gspca.ko > kldxref: /boot/modules/gspca.ko: 3828 REL entries > /boot/modules/pwc.ko > kldxref: /boot/modules/pwc.ko: 388 REL entries > /boot/modules/lhint.eyS8fW > kldxref: elf_open(/boot/modules/lhint.eyS8fW): Inappropriate file type or format > > Mulder# kldload /boot/modules/gspca.ko > kldload: can't load /boot/modules/gspca.ko: No such file or directory > Mulder# kldload gspca > kldload: can't load gspca: No such file or directory > Mulder# kldload gspca.ko > kldload: can't load gspca.ko: No such file or directory Check dmesg, you may be missing some symbol (some other needed module isn't loaded?) and in that case the error will be in the the message buffer. -- John Baldwin