RE: Using int 13 while BSD is running
Point well taken. -Jason -Original Message- From: Erik Trulsson [mailto:[EMAIL PROTECTED] Sent: Wednesday, March 10, 2004 9:24 AM To: Jason Dictos Cc: 'Sergey 'DoubleF' Zaharchenko'; Dan Nelson; ''[EMAIL PROTECTED]' ' Subject: Re: Using int 13 while BSD is running On Wed, Mar 10, 2004 at 08:49:17AM -0800, Jason Dictos wrote: > > > > To Jason: take care not to *write* anything to the disk via int 13h. > > I still don't think I understand why you are using FreeBSD for this > specific purpose. Why if you just >spend time escaping from the OS? > > We actually _like_ protected mode, it allows us to be more flexible > and our code doesn't have to be bastardized with 16 dos compilers ;). > However in dos we have garanteed hard drive support via int13 (Well > almost garanteed, but if an os can boot of the computer, we can access > the disk), and I'm looking for the same sorta garantee in BSD. People > will be using this with raid controllers, scsi hard disks, and ide > drives (Server recovery), so there will be many times when the > hardware running the hd requires specific support, which BSD may or > may not have, point is we dont' want to manage that. > > Make sense? Just because you can boot from the disk does not mean that the BIOS can read the whole disk. As an example I have an old computer running FreeBSD with a 1GB disk. The BIOS in this computer cannot handle disks larger than 512MB (which was a quite common limitation in older BIOSs). I can however boot from this disk since all the files needed for booting reside below the 512MB mark. Once I have booted FreeBSD I can access the whole disk precisely because FreeBSD does *not* use the BIOS, but use its own routines. -- Erik Trulsson [EMAIL PROTECTED] __ This email has been scanned by the MessageLabs Email Security System. For more information please visit http://www.messagelabs.com/email __ __ This email has been scanned by the MessageLabs Email Security System. For more information please visit http://www.messagelabs.com/email __ ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
RE: Using int 13 while BSD is running
> To Jason: take care not to *write* anything to the disk via int 13h. > I still don't think I understand why you are using FreeBSD for this specific purpose. Why if you just >spend time escaping from the OS? We actually _like_ protected mode, it allows us to be more flexible and our code doesn't have to be bastardized with 16 dos compilers ;). However in dos we have garanteed hard drive support via int13 (Well almost garanteed, but if an os can boot of the computer, we can access the disk), and I'm looking for the same sorta garantee in BSD. People will be using this with raid controllers, scsi hard disks, and ide drives (Server recovery), so there will be many times when the hardware running the hd requires specific support, which BSD may or may not have, point is we dont' want to manage that. Make sense? -Jason -Original Message- From: Sergey 'DoubleF' Zaharchenko [mailto:[EMAIL PROTECTED] Sent: Wednesday, March 10, 2004 5:51 AM To: Jason Dictos Cc: Dan Nelson; ''[EMAIL PROTECTED]' ' Subject: Re: Using int 13 while BSD is running On Tue, 9 Mar 2004 22:12:31 -0800 Jason Dictos <[EMAIL PROTECTED]> probably wrote: > Aren't the nodes "/dev/ad[0-9] (ide) or /dev/da[0-9] (scsi/usb)" > created by their device drivers, i.e. protected mode device drives? > That would mean that I would have to make sure that the hardware is > supported by a device driver, whereas if I had raw int 13 access I > would be garanteed access to the drive the system booted from, and any > other bios addressable device, without having to load any driver for the hardware. > > -Jason Argh, I didn't get your point first. I thought your hardware wasn't supported by int 13h, and you were trying to get FreeBSD drivers to work for you in real mode... Any real HDD's out there not supported by FreeBSD but supported by BIOS'en? Somewere around then Dan Nelson <[EMAIL PROTECTED]> probably replied: > I guess it's possible, since you have to use the bios to make VESA > video calls, and they work. /sys/i386/isa/vesa.c has most of the > stuff you would need. Also see the i386_vm86() userland function; you > may not even need to mess around inside the kernel. That's v86 mode, not real mode. Sometimes it makes a difference. It depends on how that particular BIOS was written. To Jason: take care not to *write* anything to the disk via int 13h. I still don't think I understand why you are using FreeBSD for this specific purpose. Why if you just spend time escaping from the OS? -- DoubleF All I ask is a chance to prove that money can't make me happy. __ This email has been scanned by the MessageLabs Email Security System. For more information please visit http://www.messagelabs.com/email __ ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
RE: Using int 13 while BSD is running
DD's great and all, but I'm not talking about which method to use, I'm talking about a guaranteed way to access a device without having to rely on any device drivers. Take a look at this: http://sourceforge.net/projects/lrmi/ This provides a dpmi style interface for linux and bsd, thats exactly what I was looking for. Thanks, -Jason -Original Message- From: Jerry McAllister [mailto:[EMAIL PROTECTED] Sent: Wednesday, March 10, 2004 8:14 AM To: [EMAIL PROTECTED] Cc: [EMAIL PROTECTED]; [EMAIL PROTECTED] Subject: Re: Using int 13 while BSD is running > > --Signature=_Wed__10_Mar_2004_08_12_00_+0300_m3U9Vu7vS=cMcNXd > Content-Type: text/plain; charset=US-ASCII > Content-Disposition: inline > Content-Transfer-Encoding: 7bit > > On Tue, 9 Mar 2004 14:03:34 -0800 > Jason Dictos <[EMAIL PROTECTED]> probably wrote: > > > The situation is > > this, currently we licenses Caldera DOS for a program we wrote which > > uses the int13 extensions to manipulate the systems hard drive (i.e. > > to recover partition tables and what not). This forces our > > application to be written in 16 bit mode, but it does allows us to > > not have to worry about loading any driver which would be hardware > > specific to access the hard drive. > > Through the /dev/ad[0-9] (ide) or /dev/da[0-9] (scsi/usb) you can get > access to any byte in you harddrive. They `look like' ordinary files > to most programs. Just seek the appropriate number of bytes and read > what you want (0-512 is the mbr, for example). You don't even need to > write a line in assembly for that, just plain C (or even shell-script, > if you prefer that). Gee whiz, just let dd(1) do it for you. It can seek to any position and read any number of bytes of a disk.If it gets ornery, set the block size to 1 byte - a little slow and efficient, but then it won't have trouble with other block arrangements. jerry > > > Is there > > any way to write a driver for BSD which would put the processor into > > real mode, therefore allowing us to use the int 13 api of the bios > > to read and write hard drives? > > Putting the cpu back into real mode is kind of perversion. And I don't > think FreeBSD provides any real mode interface. Whatever you would see > in real mode, you can bet it isn't a FreeBSD driver for your harddrive. > > -- > DoubleF > Romeo wasn't bilked in a day. > -- Walt Kelly, "Ten Ever-Lovin' Blue-Eyed Years With > Pogo" > > --Signature=_Wed__10_Mar_2004_08_12_00_+0300_m3U9Vu7vS=cMcNXd > Content-Type: application/pgp-signature > > -BEGIN PGP SIGNATURE- > Version: GnuPG v1.2.4 (FreeBSD) > > iD8DBQFATqOrwo7hT/9lVdwRAinPAJ9rsC9Tzum5970w88Ze0o+skKwbTgCbBE0S > 6bUkIwtlJePcYTsq1Ja/0gU= > =F4fi > -END PGP SIGNATURE- > > --Signature=_Wed__10_Mar_2004_08_12_00_+0300_m3U9Vu7vS=cMcNXd-- > > __ This email has been scanned by the MessageLabs Email Security System. For more information please visit http://www.messagelabs.com/email __ __ This email has been scanned by the MessageLabs Email Security System. For more information please visit http://www.messagelabs.com/email __ ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
RE: Using int 13 while BSD is running
The goal here is simply this: To be able to write to a systems hard drive with just bios support. I dont' want to have to deal with bundling every known ide/scsi/raid adapter driver in a bsd kernel. Here's something that I found though that may be exactly what I have been looking for: http://sourceforge.net/projects/lrmi/ I'll be doing some tests with this to see how it works out. Thanks, -Jason -Original Message- From: Sergey 'DoubleF' Zaharchenko [mailto:[EMAIL PROTECTED] Sent: Wednesday, March 10, 2004 5:51 AM To: Jason Dictos Cc: Dan Nelson; ''[EMAIL PROTECTED]' ' Subject: Re: Using int 13 while BSD is running On Tue, 9 Mar 2004 22:12:31 -0800 Jason Dictos <[EMAIL PROTECTED]> probably wrote: > Aren't the nodes "/dev/ad[0-9] (ide) or /dev/da[0-9] (scsi/usb)" > created by their device drivers, i.e. protected mode device drives? > That would mean that I would have to make sure that the hardware is > supported by a device driver, whereas if I had raw int 13 access I > would be garanteed access to the drive the system booted from, and any > other bios addressable device, without having to load any driver for the hardware. > > -Jason Argh, I didn't get your point first. I thought your hardware wasn't supported by int 13h, and you were trying to get FreeBSD drivers to work for you in real mode... Any real HDD's out there not supported by FreeBSD but supported by BIOS'en? Somewere around then Dan Nelson <[EMAIL PROTECTED]> probably replied: > I guess it's possible, since you have to use the bios to make VESA > video calls, and they work. /sys/i386/isa/vesa.c has most of the > stuff you would need. Also see the i386_vm86() userland function; you > may not even need to mess around inside the kernel. That's v86 mode, not real mode. Sometimes it makes a difference. It depends on how that particular BIOS was written. To Jason: take care not to *write* anything to the disk via int 13h. I still don't think I understand why you are using FreeBSD for this specific purpose. Why if you just spend time escaping from the OS? -- DoubleF All I ask is a chance to prove that money can't make me happy. __ This email has been scanned by the MessageLabs Email Security System. For more information please visit http://www.messagelabs.com/email __ ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
RE: Using int 13 while BSD is running
Aren't the nodes "/dev/ad[0-9] (ide) or /dev/da[0-9] (scsi/usb)" created by their device drivers, i.e. protected mode device drives? That would mean that I would have to make sure that the hardware is supported by a device driver, whereas if I had raw int 13 access I would be garanteed access to the drive the system booted from, and any other bios addressable device, without having to load any driver for the hardware. -Jason -Original Message- From: Sergey 'DoubleF' Zaharchenko To: Jason Dictos Cc: '[EMAIL PROTECTED]' Sent: 3/9/2004 9:12 PM Subject: Re: Using int 13 while BSD is running On Tue, 9 Mar 2004 14:03:34 -0800 Jason Dictos <[EMAIL PROTECTED]> probably wrote: > The situation is > this, currently we licenses Caldera DOS for a program we wrote which > uses the int13 extensions to manipulate the systems hard drive (i.e. > to recover partition tables and what not). This forces our application > to be written in 16 bit mode, but it does allows us to not have to > worry about loading any driver which would be hardware specific to > access the hard drive. Through the /dev/ad[0-9] (ide) or /dev/da[0-9] (scsi/usb) you can get access to any byte in you harddrive. They `look like' ordinary files to most programs. Just seek the appropriate number of bytes and read what you want (0-512 is the mbr, for example). You don't even need to write a line in assembly for that, just plain C (or even shell-script, if you prefer that). > Is there > any way to write a driver for BSD which would put the processor into > real mode, therefore allowing us to use the int 13 api of the bios to > read and write hard drives? Putting the cpu back into real mode is kind of perversion. And I don't think FreeBSD provides any real mode interface. Whatever you would see in real mode, you can bet it isn't a FreeBSD driver for your harddrive. -- DoubleF Romeo wasn't bilked in a day. -- Walt Kelly, "Ten Ever-Lovin' Blue-Eyed Years With Pogo" __ This email has been scanned by the MessageLabs Email Security System. For more information please visit http://www.messagelabs.com/email __ ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
RE: Using int 13 while BSD is running
Hello again, I did a some googling and I found this source forge project which strives to emulate a DPMI style interface for linux/bsd. Here's a link: http://sourceforge.net/projects/lrmi/ Anyone know if this thing works? I'm going to try it and find out. Thanks, -Jason -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Jason Dictos Sent: Tuesday, March 09, 2004 2:04 PM To: '[EMAIL PROTECTED]' Subject: Using int 13 while BSD is running Hello, I'm investigating what resources are out there for accessing bios addressable devices while BSD is up and running. The situation is this, currently we licenses Caldera DOS for a program we wrote which uses the int13 extensions to manipulate the systems hard drive (i.e. to recover partition tables and what not). This forces our application to be written in 16 bit mode, but it does allows us to not have to worry about loading any driver which would be hardware specific to access the hard drive. Is there any way to write a driver for BSD which would put the processor into real mode, therefore allowing us to use the int 13 api of the bios to read and write hard drives? That way we could package a stripped down BSD kernel which loaded our driver and gave our application access to hard disks without having to load any device driver. Apologies in advance if this is the wrong mailing list, -Jason __ This email has been scanned by the MessageLabs Email Security System. For more information please visit http://www.messagelabs.com/email __ ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]" __ This email has been scanned by the MessageLabs Email Security System. For more information please visit http://www.messagelabs.com/email __ __ This email has been scanned by the MessageLabs Email Security System. For more information please visit http://www.messagelabs.com/email __ ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Using int 13 while BSD is running
Hello, I'm investigating what resources are out there for accessing bios addressable devices while BSD is up and running. The situation is this, currently we licenses Caldera DOS for a program we wrote which uses the int13 extensions to manipulate the systems hard drive (i.e. to recover partition tables and what not). This forces our application to be written in 16 bit mode, but it does allows us to not have to worry about loading any driver which would be hardware specific to access the hard drive. Is there any way to write a driver for BSD which would put the processor into real mode, therefore allowing us to use the int 13 api of the bios to read and write hard drives? That way we could package a stripped down BSD kernel which loaded our driver and gave our application access to hard disks without having to load any device driver. Apologies in advance if this is the wrong mailing list, -Jason __ This email has been scanned by the MessageLabs Email Security System. For more information please visit http://www.messagelabs.com/email __ ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
RE: stop the desktops' upgrades
We must continually move to the future! Upgrades can never end! NEVER!!! -Jason -Original Message- From: .VWV. [mailto:[EMAIL PROTECTED] Sent: Wednesday, October 29, 2003 5:01 PM To: [EMAIL PROTECTED] Hello to all. I'm happy for the new release. Otherwise, in my opinion it is necessary to stop this unuseful adoption of the endless upgrades of KDE and GNOME monsters. They still are much better than WIN. There is no stable standard for applications' developers, under such environments. After the failure of Motif, I always suggest the adoption of the stable Tcl/Tk for the most important projects. It is necessary a bit of 'peace'. ¡Stop upgrading, keep a working desktop - stop the fashion system! With my best regards VITTORI ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]" This email has been scanned for all viruses by the MessageLabs Email Security System. For more information on a proactive email security service working around the clock, around the globe, visit http://www.messagelabs.com This email has been scanned for all viruses by the MessageLabs Email Security System. For more information on a proactive email security service working around the clock, around the globe, visit http://www.messagelabs.com ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
How to view kmail stored email from console
Hi All, I have FreeBSD 5.1 with KDE 3 running kmail. Kmail pulls from the local mailbox into its mail archive. I'd like to figure out a way to reading kmail email from the console. Is that possible? I can already read mail in my mailbox via the console by using mutt, however when kmail reads messages from the mailbox it deletes them and stores them in its own special file. So what I'm trying to do is read that file via a console program. Thanks, -Jason This email has been scanned for all viruses by the MessageLabs Email Security System. For more information on a proactive email security service working around the clock, around the globe, visit http://www.messagelabs.com ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Bug in ports howto question
How does one formally submit a ports bug report? -Jason This email has been scanned for all viruses by the MessageLabs Email Security System. For more information on a proactive email security service working around the clock, around the globe, visit http://www.messagelabs.com ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Auto thumbnail/index.html generation program in ports?
Is there a program that will auto rezise large .jpg images into smaller ones, while making index.html pages which have links to the large images with the smaller thumbnail ones as links? thanks, -Jason ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Crash in gui
Hi All, Today my machine has locked up twice within the span of an hour, and both times it locked up when I clicked on a link in Gaim. The lock is hard, and there's no message in /var/log/messages that I can see, so my question is how can I debug such a problem? Where even the caps lock button no longer reponds? I'm using 5.1 + all security patches -Jason ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
How to get shipping version of 5.1 from cvsup branch?
Hi All, I know how to get current, and I know how to get stable, but how do you specify in a cvsup file to get the "code that ships on a 5.1 distribution" cd? Thanks, -Jason ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Searching contents of files
Hi All, I've always used grep text /*/*/* to recursivly search directories for files with the specified text string in them, however this method doesn't always work very well (sometimes it bails out halfway through with error "Argument list too long"). Is there a more effective way to search the contents of files? Thanks, -Jason ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: Regarding spam
Hey Gary, Before you or anyone else on this lists continues to waste time with a n00b like me, I'm going to first educate myself by reading /usr/share/sendmail/cf/README (paying special attention to ANTI-SPAM CONFIGURATION) :P Thanks! -Jason On Tuesday 21 October 2003 19:10, Gary wrote: > Hi Jason, > > On Tue, 21 Oct 2003 06:44:13 -0700 GMT (10/21/2003, 8:44 AM +0500 GMT my > time), jason dictos wrote: > > j>I run my own mailsever, and I just wanna know its possible for > someone to j> send an email to my mail box, but yet have no one specified > in the TO or CC j> fields. I guess those fields are probably optional, but > how can I adjust my j> mailserver to reject messages sent to someones > mailbox without their name j> being in the TO or CC fields? > > If it isn't too much trouble, would you mind specifying just the basics, > like what MTA you are using? A null sender is authorized by the RFCs and > this is for bounces. We need a lot more info. Do you run / use DNS, do you > have a backup MX, etc.. > > j> P.S. My mailserver is a CLOSED relay. > > As it should be, and how do you know? > > -- > Gary > > A snooze button is a poor substitute for no alarm clock at all. > > ___ > [EMAIL PROTECTED] mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-questions > To unsubscribe, send any mail to > "[EMAIL PROTECTED]" ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Regarding spam
Hi All, I run my own mailsever, and I just wanna know its possible for someone to send an email to my mail box, but yet have no one specified in the TO or CC fields. I guess those fields are probably optional, but how can I adjust my mailserver to reject messages sent to someones mailbox without their name being in the TO or CC fields? P.S. My mailserver is a CLOSED relay. Thanks, -Jason ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
RE: Help with NV driver - More information part 2 - SOLVED
Hi All, After setting the sysctl machdep.disable_mtrrs="1" in loader.conf I was able to re-use the nvidia.ko module without it hosing my server! Thanks, -Jason -Original Message----- From: Jason Dictos [mailto:[EMAIL PROTECTED] Sent: Tuesday, October 21, 2003 9:30 AM To: 'Nicolai P Guba'; [EMAIL PROTECTED] Well, I've tried ranges too with the same results -Jason -Original Message- From: Nicolai P Guba [mailto:[EMAIL PROTECTED] Sent: Tuesday, October 21, 2003 3:40 AM To: [EMAIL PROTECTED] On Tuesday 21 October 2003 04:49, Jason Dictos wrote: > Section "Monitor" > Identifier "NEC2080UX" > HorizSync 74.9 > VertRefresh 59.9 > EndSection Hmmm, are you sure this is correct? Shouldn't they rather be _ranges_ ? Just a stab in the dark... -- =NPG= ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]" This email has been scanned for all viruses by the MessageLabs Email Security System. For more information on a proactive email security service working around the clock, around the globe, visit http://www.messagelabs.com This email has been scanned for all viruses by the MessageLabs Email Security System. For more information on a proactive email security service working around the clock, around the globe, visit http://www.messagelabs.com ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]" This email has been scanned for all viruses by the MessageLabs Email Security System. For more information on a proactive email security service working around the clock, around the globe, visit http://www.messagelabs.com This email has been scanned for all viruses by the MessageLabs Email Security System. For more information on a proactive email security service working around the clock, around the globe, visit http://www.messagelabs.com ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
RE: Help with NV driver - More information part 2
Well, I've tried ranges too with the same results -Jason -Original Message- From: Nicolai P Guba [mailto:[EMAIL PROTECTED] Sent: Tuesday, October 21, 2003 3:40 AM To: [EMAIL PROTECTED] On Tuesday 21 October 2003 04:49, Jason Dictos wrote: > Section "Monitor" > Identifier "NEC2080UX" > HorizSync 74.9 > VertRefresh 59.9 > EndSection Hmmm, are you sure this is correct? Shouldn't they rather be _ranges_ ? Just a stab in the dark... -- =NPG= ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]" This email has been scanned for all viruses by the MessageLabs Email Security System. For more information on a proactive email security service working around the clock, around the globe, visit http://www.messagelabs.com This email has been scanned for all viruses by the MessageLabs Email Security System. For more information on a proactive email security service working around the clock, around the globe, visit http://www.messagelabs.com ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
RE: Help with NV driver - More information part 2
x000c - 0x000e (0x3) MX[B]
[7] -1 0 0x - 0x0009 (0xa) MX[B]
[8] -1 0 0xf3903000 - 0xf3903fff (0x1000) MX[B]E
[9] -1 0 0xf3902000 - 0xf3902fff (0x1000) MX[B]E
[10] -1 0 0xf300 - 0xf37f (0x80) MX[B]E
[11] -1 0 0xf3901000 - 0xf3901fff (0x1000) MX[B]E
[12] -1 0 0xf380 - 0xf38f (0x10) MX[B]E
[13] -1 0 0xf390 - 0xf3900fff (0x1000) MX[B]E
[14] -1 0 0xd000 - 0xcfff (0x0) MX[B]EO
[15] -1 0 0xe800 - 0xe807 (0x8) MX[B](B)
[16] -1 0 0xe000 - 0xe7ff (0x800) MX[B](B)
[17] -1 0 0xf000 - 0xf0ff (0x100) MX[B](B)
[18] 0 0 0x000a - 0x000a (0x1) MS[B](OprD)
[19] 0 0 0x000b - 0x000b7fff (0x8000) MS[B](OprD)
[20] 0 0 0x000b8000 - 0x000b (0x8000) MS[B](OprD)
[21] -1 0 0x - 0x (0x1) IX[B]
[22] -1 0 0x - 0x00ff (0x100) IX[B]
[23] -1 0 0xe800 - 0xe8ff (0x100) IX[B]E
[24] -1 0 0xe400 - 0xe4ff (0x100) IX[B]E
[25] -1 0 0xe000 - 0xe0ff (0x100) IX[B]E
[26] -1 0 0xdc00 - 0xdcff (0x100) IX[B]E
[27] -1 0 0xd800 - 0xd8ff (0x100) IX[B]E
[28] -1 0 0xd400 - 0xd4ff (0x100) IX[B]E
[29] -1 0 0xd000 - 0xd0ff (0x100) IX[B]E
[30] 0 0 0x03b0 - 0x03bb (0xc) IS[B](OprU)
[31] 0 0 0x03c0 - 0x03df (0x20) IS[B](OprU)
(==) NV(0): Write-combining range (0xf000,0x100) was already clear
(==) NV(0): Write-combining range (0xe000,0x800)
(==) NV(0): Write-combining range (0xa,0x1) was already clear
(II) NV(0): Using XFree86 Acceleration Architecture (XAA)
Screen to screen bit blits
Solid filled rectangles
8x8 mono pattern filled rectangles
Solid Lines
Offscreen Pixmaps
Setting up tile and stipple cache:
32 128x128 slots
32 256x256 slots
16 512x512 slots
(==) NV(0): Backing store disabled
(==) NV(0): Silken mouse enabled
(==) RandR enabled
Symbol __glXActiveScreens from module
/usr/X11R6/lib/modules/extensions/libdri.a is unresolved!
Symbol __glXActiveScreens from module
/usr/X11R6/lib/modules/extensions/libdri.a is unresolved!
(II) Initializing built-in extension MIT-SHM
(II) Initializing built-in extension XInputExtension
(II) Initializing built-in extension XTEST
(II) Initializing built-in extension XKEYBOARD
(II) Initializing built-in extension LBX
(II) Initializing built-in extension XC-APPGROUP
(II) Initializing built-in extension SECURITY
(II) Initializing built-in extension XINERAMA
(II) Initializing built-in extension XFree86-Bigfont
(II) Initializing built-in extension RENDER
(II) Initializing built-in extension RANDR
(EE) [GLX]: Failed to add GLX extension (NVIDIA XFree86 driver not found)
(==) Mouse1: Protocol: "Auto"
(**) Option "CorePointer"
(**) Mouse1: Core Pointer
(**) Option "Device" "/dev/sysmouse"
(**) Option "Buttons" "3"
(**) Mouse1: Emulate3Buttons, Emulate3Timeout: 50
(**) Option "ZAxisMapping" "4 5"
(**) Mouse1: ZAxisMapping: buttons 4 and 5
(**) Mouse1: Buttons: 5
(II) Keyboard "Keyboard1" handled by legacy driver
(II) XINPUT: Adding extended input device "Mouse1" (type: MOUSE)
(II) Mouse1: SetupAuto: hw.iftype is 4, hw.model is 0
(II) Mouse1: SetupAuto: protocol is SysMouse
Could not init font path element /usr/X11R6/lib/X11/fonts/artwiz-fonts,
removing from list!
-Jason
-Original Message-
From: Jason Dictos [mailto:[EMAIL PROTECTED]
Sent: Monday, October 20, 2003 8:45 PM
To: '[EMAIL PROTECTED]'
I just noticed that if I connect the DVI cable to the second DVI port and
reboot the machine, when I start X it loads a screen full of garble (tons of
lines going everywhere) but when I check the monitors diag, it says it is at
1600x1200 70h 60v
Is anyone else using a Geforce ti 4600 Gainward Golden Sample (The only dual
DVI geforce I know of)?
-Jason
-Original Message-
From: Jason Dictos [mailto:[EMAIL PROTECTED]
Sent: Monday, October 20, 2003 8:35 PM
To: '[EMAIL PROTECTED]'
Hi,
I'm having difficulty getting the nv driver to work properly on my
FreeBSD 5.1 box. Recently, the nvidia driver started causing my kernel to
crash consistently, so I decided to move to the non-glx enabled NV driver.
Whenever that driver starts using the SAME config as the one used for the
nvidia driver, the screen goes blank with "unsupported resolution" but you
can hear the gui initializing in the background. I'm using the DVI port on
the Geforce (it has dual DVI), and I know for a fact that the horizontal and
vertical refresh rates are to the spec (74.9, 59.9 respectively).
-Jason
This email has been scanned for all viruses by the MessageLabs Email
Security System. For more information on a proactive email security service
working around the clock, around the globe, visit http://www.messagelabs.com
___
[EMAIL PROTECTED] mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to "[EMAIL PROTECTED]"
This email has been scanned for all viruses by the MessageLabs Email
Security System. For more information on a proactive email security service
working around the clock, around the globe, visit http://www.messagelabs.com
This email has been scanned for all viruses by the MessageLabs Email
Security System. For more information on a proactive email security service
working around the clock, around the globe, visit http://www.messagelabs.com
___
[EMAIL PROTECTED] mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to "[EMAIL PROTECTED]"
This email has been scanned for all viruses by the MessageLabs Email
Security System. For more information on a proactive email security service
working around the clock, around the globe, visit http://www.messagelabs.com
This email has been scanned for all viruses by the MessageLabs Email
Security System. For more information on a proactive email security
service working around the clock, around the globe, visit
http://www.messagelabs.com
___
[EMAIL PROTECTED] mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to "[EMAIL PROTECTED]"
RE: Help with NV driver - More information
I just noticed that if I connect the DVI cable to the second DVI port and reboot the machine, when I start X it loads a screen full of garble (tons of lines going everywhere) but when I check the monitors diag, it says it is at 1600x1200 70h 60v Is anyone else using a Geforce ti 4600 Gainward Golden Sample (The only dual DVI geforce I know of)? -Jason -Original Message- From: Jason Dictos [mailto:[EMAIL PROTECTED] Sent: Monday, October 20, 2003 8:35 PM To: '[EMAIL PROTECTED]' Hi, I'm having difficulty getting the nv driver to work properly on my FreeBSD 5.1 box. Recently, the nvidia driver started causing my kernel to crash consistently, so I decided to move to the non-glx enabled NV driver. Whenever that driver starts using the SAME config as the one used for the nvidia driver, the screen goes blank with "unsupported resolution" but you can hear the gui initializing in the background. I'm using the DVI port on the Geforce (it has dual DVI), and I know for a fact that the horizontal and vertical refresh rates are to the spec (74.9, 59.9 respectively). -Jason This email has been scanned for all viruses by the MessageLabs Email Security System. For more information on a proactive email security service working around the clock, around the globe, visit http://www.messagelabs.com ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]" This email has been scanned for all viruses by the MessageLabs Email Security System. For more information on a proactive email security service working around the clock, around the globe, visit http://www.messagelabs.com This email has been scanned for all viruses by the MessageLabs Email Security System. For more information on a proactive email security service working around the clock, around the globe, visit http://www.messagelabs.com ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Help with NV driver
Hi, I'm having difficulty getting the nv driver to work properly on my FreeBSD 5.1 box. Recently, the nvidia driver started causing my kernel to crash consistently, so I decided to move to the non-glx enabled NV driver. Whenever that driver starts using the SAME config as the one used for the nvidia driver, the screen goes blank with "unsupported resolution" but you can hear the gui initializing in the background. I'm using the DVI port on the Geforce (it has dual DVI), and I know for a fact that the horizontal and vertical refresh rates are to the spec (74.9, 59.9 respectively). -Jason This email has been scanned for all viruses by the MessageLabs Email Security System. For more information on a proactive email security service working around the clock, around the globe, visit http://www.messagelabs.com ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Best place to start a misc program at bootup
Hello again, So there's /etc/rc, and etc/rc.local, and then there's the fancy rc.conf scripts which stat programs. /etc/rc and /etc/rc.local don't appear to be "designated" places for starting up misc. programs, so where do we put these misc programs which we want to run at startup? Thanks, -Jason ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Weird usb keyboard problem
Hi All, I have a logitech wireless keyboard, plugged into the onboard usb on my Tyan dual pIII motherboard running a Via chipset. Whenever I use the keyboard and type at a normal rate, it seems like the usb driver or whatever detects more ekeys then I've pressed. Here is san example of fwhat thappens when nI tytpe at ta normal r ate on nmy u sb k eybobard with hFreeBSD 5.1. How can I debug this?? When I use a PS/2 keyboard, the problem does not occur. Needless to say it is very annoying to type slowly constantly. Any help would be appreciated!! -Jason ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Drivers for leadtek winfast tv 2000 xp?
Are there drivers in FreeBSD for TV Input tuner cards such as the winfast tv 2000 xp? (This may be an ATI oem board). -Jason ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Weird usb keyboard problem
Hi All, I have a logitech wireless keyboard, plugged into the onboard usb on my Tyan dual pIII motherboard running a Via chipset. Whenever I use the keyboard and type at a normal rate, it seems like the usb driver or whatever detects more ekeys then I've pressed. Here is san example of fwhat thappens when nI tytpe at ta normal r ate on nmy u sb k eybobard with hFreeBSD 5.1. How can I debug this?? When I use a PS/2 keyboard, the problem does not occur. Needless to say it is very annoying to type slowly constantly. Any help would be appreciated!! -Jason ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Best 6.1 channel sound card for FreeBSD?
Whats the best 6.1 channel sound card for FreeBSD (i.e. what one has the most open source support behind it)? Thanks, -Jason ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
apache 1.3.27 with mod_php4 crashes
Hi All,
I recently re-compiled mod_php4 with the following options:
CONFIGURE_ARGS+=--with-zlib
LIB_DEPENDS+= mcrypt.8:${PORTSDIR}/security/libmcrypt
CONFIGURE_ARGS+=--with-mcrypt=${LOCALBASE}
LIB_DEPENDS+= c-client4.8:${PORTSDIR}/mail/cclient
CONFIGURE_ARGS+=--with-imap=${LOCALBASE}
CONFIGURE_ARGS+=--with-imap-ssl=${LOCALBASE}
LIB_DEPENDS+= mysqlclient.10:${PORTSDIR}/databases/mysql323-client
CONFIGURE_ARGS+=--with-mysql=${LOCALBASE}
LIB_DEPENDS+= ldap.2:${PORTSDIR}/net/openldap20
LIB_DEPENDS+= lber.2:${PORTSDIR}/net/openldap20
CONFIGURE_ARGS+=--with-ldap=${LOCALBASE}
USE_OPENSSL=yes
CONFIGURE_ARGS+=--with-openssl=${OPENSSLBASE}
LIB_DEPENDS+= expat.4:${PORTSDIR}/textproc/expat2
CONFIGURE_ARGS+=--with-expat-dir=${LOCALBASE}
CONFIGURE_ARGS+=--with-xmlrpc
LIB_DEPENDS+= xml2.5:${PORTSDIR}/textproc/libxml2
CONFIGURE_ARGS+=--with-dom=${LOCALBASE}
CONFIGURE_ARGS+=--enable-ftp
CONFIGURE_ARGS+=--with-curl=${LOCALBASE}
BUILD_DEPENDS+= ${LOCALBASE}/lib/libcurl.a:${PORTSDIR}/ftp/curl
LIB_DEPENDS+= intl.4:${PORTSDIR}/devel/gettext
CONFIGURE_ARGS+=--with-gettext=${LOCALBASE}
LIB_DEPENDS+= iconv.3:${PORTSDIR}/converters/libiconv
CONFIGURE_ARGS+=--with-iconv=${LOCALBASE}
And now if I have the mod_php4 module listed in the httpd.conf file, apache
will crash out and dump the core:
Oct 11 22:21:17 ahab kernel: pid 2428 (httpd), uid 0: exited on signal 11
(core dumped)
I tried starting httpd with GDB in the hops that I could look at the call
stack and somehow make a guess as to why it is crashing, but gdb doesn't
appear to be catching the signal:
(gdb) handle 11
SignalStop Print Pass to program Description
SIGSEGV Yes Yes Yes Segmentation fault
Yet it appears to be handling it. Here's what happens when I do a run through
gdb:
(gdb) r
Starting program: /usr/local/sbin/httpd
(no debugging symbols found)...(no debugging symbols found)...(no debugging
symbols found)...
(no debugging symbols found)...(no debugging symbols found)...(no debugging
symbols found)...
(no debugging symbols found)...(no debugging symbols found)...(no debugging
symbols found)...
(no debugging symbols found)...(no debugging symbols found)...(no debugging
symbols found)...
(no debugging symbols found)...(no debugging symbols found)...(no debugging
symbols found)...
(no debugging symbols found)...(no debugging symbols found)...(no debugging
symbols found)...
(no debugging symbols found)...(no debugging symbols found)...(no debugging
symbols found)...
(no debugging symbols found)...(no debugging symbols found)...(no debugging
symbols found)...
(no debugging symbols found)...(no debugging symbols found)...(no debugging
symbols found)...
(no debugging symbols found)...(no debugging symbols found)...(no debugging
symbols found)...
(no debugging symbols found)...(no debugging symbols found)...(no debugging
symbols found)...
(no debugging symbols found)...(no debugging symbols found)...(no debugging
symbols found)...
Program exited normally.
(gdb)
Says the program exited normally??
Ideas?
Thanks,
-Jason
___
[EMAIL PROTECTED] mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Can't run a port right after an install
Hi All, I've been noticing that whenever I install a port, I can't ever run the executable right off the bat, instead I have to close a consoel and re-open one in order to get the program to be in my (I am guessing) search path. Why is that? Is there any way around that? Thanks, -Jason ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Beep when tab cannot incomplete
Hello, Where's the "disable beep when I can't complete the tab" setting? -Jason ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Good reading for SSH pop3 setup?
Hello yet again, Can you guys point me to some invaluable reading in regards to setting up encrypted email servers/clients to work over SSH and use PGP encryption with public keys and what not? I remember following a tutorial on setting up POP3/IMAP over ssh, but it wasn't very up to date. Thanks, -Jason ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
dhcpd output to root console
Hi Guys, Whenever I boot up, dhcpd always splurges out stuff to roots console screen and /var/log/messages. Is there anyway I can disable it from spewing messages to the console and to only spew out messages to /var/log/message? -Jason ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Oct 11 10:09:54 ahab inetd[644]: ftp/tcp: bind: Address already in use
Oct 11 10:09:54 ahab inetd[644]: ftp/tcp: bind: Address already in use Oct 11 10:19:54 ahab inetd[644]: ftp/tcp: bind: Address already in use Oct 11 10:29:54 ahab inetd[644]: ftp/tcp: bind: Address already in use Oct 11 10:39:54 ahab inetd[644]: ftp/tcp: bind: Address already in use Oct 11 10:49:54 ahab inetd[644]: ftp/tcp: bind: Address already in use Oct 11 10:59:54 ahab inetd[644]: ftp/tcp: bind: Address already in use Oct 11 11:09:54 ahab inetd[644]: ftp/tcp: bind: Address already in use Anyone know what these mean? I assume there's some deamon that inetd is continually trying to re-start? Here's my ftp line: ftp stream tcp nowait root/usr/local/libexec/proftpd proftpd Ideas? -Jason ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
#1 reason why mplayer is choppy?
-Jason ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
