Re: /dev/shm
On Monday 07 July 2003 02:41, Thomas E. Dickey wrote: On Mon, 7 Jul 2003, Christopher Vance wrote: On Sun, Jul 06, 2003 at 08:14:44PM -0400, Thomas Dickey wrote: : On Mon, Jul 07, 2003 at 01:58:19AM +0200, Marcin Dalecki wrote: : Myron J. Mayfield wrote: : start it. It gives me an error saying cant find /dev/shm. I tried : adding this to /dev but was unable to. Does anyone have any : : For some unexcused reason there is the trend in Linux to represent : everything as kind of a wired half finished pseudo file system. /proc : pipe devicefs sysctl and so on... The list is really long. Even : shared memmory is mapped to ehrm a filesystem. This is : expected to be mounted at /dev/shm by the system. You can't expect : FreeBSD to follow this path... : : Linux isn't the only system that does this (learn a little, criticize : less). If you're talking about Plan 9 or Inferno, they at least have a history of finishing their filesystems and understanding why it's done that way. If Linux attempts to copy without understanding, and doesn't complete the job, it doesn't imply that the original idea was a Bad Thing, only that the implementation sucks. Better, apparently to copy (not actually), rather than to whine in the background... Still - your response is equally ignorant (Plan 9 is well known - even to students), since it offers no useful information. The /proc stuff is used in real Unix's such as Solaris. Just checking, I see that FreeBSD implements procfs, which is along the same lines. (still waiting for FreeBSD to complete a sysinstall program that doesn't look as if it was an assignment for high-school interns). What's the matter with sysinstall ? I very much like sysinstall as it is now. :) See you. -- JFRH ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: My computer gets stalled when I try to exec the X window system(It was can't compile Nvidia driver)
I've fixed this problem changing the jumpers of the motherboard. I've changed 2 jumpers: 1. On-board VGA = off 2. IRQ assigned by motherboard (or something like that) = off And now I've got the Nvidia driver working fine. Thanks!!! On Friday 20 June 2003 12:35, Juan Rodriguez Hervella wrote: Hello again: It doesn't matter if either I use the /usr/x11/nvidia-driver or I use the normal nv driver, when I run X or kdm or xf86cfg my computer hangs completely. I've got the Nvidia RIVA TNT 64M PCI (I made a question here a cuople of days ago). My computer has an ASUS-SP97 motherboard with a SIS5597 vga chipset and it doesn't have AGP, only PCI and ISA slots. I upgraded my BIOS to make it work with hard-disk bigger than 8G, and also to allow to switch off the onboard VGA chipset. With Linux and Windows it works nice :( I've tried with XFree86-4.2 and XFree86-4.3, but no success. Sometimes, when I lauch X, I see on the screen as if the computer had reboot, I mean that I see the information about the NVidia vga card that I usually see when I switch on the computer for the first time. It's very strange because I've been working with my NVidia card on 5.0-DP1, both with the nv driver and with a driver for FreeBSD-5.0 before nvidia released his own driver. I don't know what I've done during this 2 weeks, but now I don't have X system any more (lol). Im really fed up with this because I was getting used to using KDE (lol again :) If anybody can help meI will give my computer away to him, I swear Thanks :( -- JFRH ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to [EMAIL PROTECTED]
My computer gets stalled when I try to exec the X window system (Itwas can't compile Nvidia driver)
Hello again: It doesn't matter if either I use the /usr/x11/nvidia-driver or I use the normal nv driver, when I run X or kdm or xf86cfg my computer hangs completely. I've got the Nvidia RIVA TNT 64M PCI (I made a question here a cuople of days ago). My computer has an ASUS-SP97 motherboard with a SIS5597 vga chipset and it doesn't have AGP, only PCI and ISA slots. I upgraded my BIOS to make it work with hard-disk bigger than 8G, and also to allow to switch off the onboard VGA chipset. With Linux and Windows it works nice :( I've tried with XFree86-4.2 and XFree86-4.3, but no success. Sometimes, when I lauch X, I see on the screen as if the computer had reboot, I mean that I see the information about the NVidia vga card that I usually see when I switch on the computer for the first time. It's very strange because I've been working with my NVidia card on 5.0-DP1, both with the nv driver and with a driver for FreeBSD-5.0 before nvidia released his own driver. I don't know what I've done during this 2 weeks, but now I don't have X system any more (lol). Im really fed up with this because I was getting used to using KDE (lol again :) If anybody can help meI will give my computer away to him, I swear Thanks :( -- JFRH ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to [EMAIL PROTECTED]
NVidia kernel driver support for FreeBSD-5.1
Hello: I've got a PCI-NVidia Riva TNT 64 video card at home, and I've tried to compile the drivers but it doesn't work, and after changing the source to let the compilation progress, when the module is loaded I've received a kernel panic. Im using FreeBSD-5.1 with XFree86-4.3, what can I do to solve this issue ? I can not run the X system using the nv driver, my computer hangs up. Any help will be useful, thanks! -- JFRH ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: NVidia kernel driver support for FreeBSD-5.1
On Wednesday 18 June 2003 16:05, Kenneth Culver wrote: #pciconf -l -v [EMAIL PROTECTED]:12:0:class=0x03 card=0x chip=0x002d10de rev=0x15 hdr=0x00 vendor = 'NVIDIA Corporation' device = 'NV5 TNT2 Model 64 / TNT2 Model 64 Pro' This is my video card, which sounds just like yours. I have it working fine with the native XFree 'nv' module, but two caveats: The nv module won't support 3d acceleration. IF you want 3d accel, you have to use nvidia's binary driver. Hello! I've got exactly that video card :) So...the best way is using the ports collection, do I still have to delete options INVARIANT and recompile the kernel ? It's very painful for me to compile things because I've got an old computer (Pentium MMX 200Mhz) and it takes long time to compile the kernel, so if I can still use both the kernel with INVARIANTS and install the nvidia-port, I'd be delighted. I'm not at home yet :( Thanks! First, once you have installed the driver from NVidia, your /usr/X11 tree will contain files that prevent the native 'nv' module from working. I was never able to figure out which files were responsible so I finally deleted the entire /usr/X11 tree and reinstalled everything from scratch. Second, you must be very careful which modules you load in your XF86Config. There is at least one module which will prevent everything from working-- unfortuneately I can't remember which one :0( Section Module Load extmod Load xie Load pex5 Load dbe Load record Load xtrap Load speedo # Load glx Load type1 Load freetype EndSection Notice that I have 'glx' commented out -- I think that's the reason I did that, but it was a long time ago. You did it because the nvidia binary drivers require you to. Ken ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to [EMAIL PROTECTED] -- JFRH ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to [EMAIL PROTECTED]
Why doesn't background fsck work ?
Hello!: I tried to make my Nvidia video card work yesterday, and everytime I launched the X system my computer hang up. So I had to make a hard reboot. (I think I will fix the Xs problem this night at home) But I've got another weird problem. :) The fsck of my partitions is always made on the foregroud, although I've heard about something like a delayed/background file system checker. Why is it always made on the foreground ? -- JFRH ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Why doesn't background fsck work ?
On Wednesday 18 June 2003 17:39, Bernd Walter wrote: On Wed, Jun 18, 2003 at 04:54:44PM +0200, Juan Rodriguez Hervella wrote: Hello!: I tried to make my Nvidia video card work yesterday, and everytime I launched the X system my computer hang up. So I had to make a hard reboot. (I think I will fix the Xs problem this night at home) But I've got another weird problem. :) The fsck of my partitions is always made on the foregroud, although I've heard about something like a delayed/background file system checker. Why is it always made on the foreground ? No softupdates enabled? yes, you've got it ! I haven't got softupdates enabled, but I didn't want to enable it, because I've heard that it isn't 100% reliable and I didn't want to lose data Do you recommend me to switch it on ? Thanks! -- JFRH ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to [EMAIL PROTECTED]
Keyboard not responding on X
Hello: I copy here an extract of the output of kdm.log, but I don't understand what can be happening, any comment is allowed, thankx: -- JFRHFree86 Version 4.3.0 Release Date: 27 February 2003 X Protocol Version 11, Revision 0, Release 6.6 Build Operating System: FreeBSD 4.8 i386 [ELF] Build Date: 09 May 2003 Before reporting problems, check http://www.XFree86.Org/ to make sure that you have the latest version. Module Loader present Markers: (--) probed, (**) from config file, (==) default setting, (++) from command line, (!!) notice, (II) informational, (WW) warning, (EE) error, (NI) not implemented, (??) unknown. (==) Log file: /var/log/XFree86.0.log, Time: Wed May 28 10:29:16 2003 (==) Using config file: /usr/X11R6/lib/X11/XF86Config expected keysym, got XF86_Switch_VT_1: line 8 of xfree86 expected keysym, got XF86_Switch_VT_2: line 11 of xfree86 expected keysym, got XF86_Switch_VT_3: line 14 of xfree86 expected keysym, got XF86_Switch_VT_4: line 17 of xfree86 expected keysym, got XF86_Switch_VT_5: line 20 of xfree86 expected keysym, got XF86_Switch_VT_6: line 23 of xfree86 expected keysym, got XF86_Switch_VT_7: line 26 of xfree86 expected keysym, got XF86_Switch_VT_8: line 29 of xfree86 expected keysym, got XF86_Switch_VT_9: line 32 of xfree86 expected keysym, got XF86_Switch_VT_10: line 35 of xfree86 expected keysym, got XF86_Switch_VT_11: line 38 of xfree86 expected keysym, got XF86_Switch_VT_12: line 41 of xfree86 expected keysym, got XF86_Ungrab: line 45 of xfree86 expected keysym, got XF86_ClearGrab: line 48 of xfree86 expected keysym, got XF86_Next_VMode: line 51 of xfree86 expected keysym, got XF86_Prev_VMode: line 54 of xfree86 The XKEYBOARD keymap compiler (xkbcomp) reports: Warning: Multiple interpretations of NoSymbol+AnyOfOrNone(all) Using last definition for duplicate fields Warning: Multiple interpretations of NoSymbol+AnyOfOrNone(all) Using last definition for duplicate fields Warning: Multiple interpretations of NoSymbol+AnyOfOrNone(all) Using last definition for duplicate fields Warning: Multiple interpretations of NoSymbol+AnyOfOrNone(all) Using last definition for duplicate fields expected keysym, got XF86_Switch_VT_1: line 51 of pc/pc expected keysym, got XF86_Switch_VT_2: line 55 of pc/pc expected keysym, got XF86_Switch_VT_3: line 59 of pc/pc expected keysym, got XF86_Switch_VT_4: line 63 of pc/pc expected keysym, got XF86_Switch_VT_5: line 67 of pc/pc expected keysym, got XF86_Switch_VT_6: line 71 of pc/pc expected keysym, got XF86_Switch_VT_7: line 75 of pc/pc expected keysym, got XF86_Switch_VT_8: line 79 of pc/pc expected keysym, got XF86_Switch_VT_9: line 83 of pc/pc expected keysym, got XF86_Switch_VT_10: line 87 of pc/pc expected keysym, got XF86_Switch_VT_11: line 91 of pc/pc expected keysym, got XF86_Switch_VT_12: line 95 of pc/pc expected keysym, got XF86_Ungrab: line 135 of pc/pc expected keysym, got XF86_ClearGrab: line 141 of pc/pc expected keysym, got XF86_Prev_VMode: line 147 of pc/pc expected keysym, got XF86_Next_VMode: line 157 of pc/pc expected keysym, got SunFA_Acute: line 40 of pc/es expected keysym, got SunFA_Diaeresis: line 40 of pc/es expected keysym, got SunFA_Grave: line 41 of pc/es expected keysym, got SunFA_Circum: line 41 of pc/es Errors from xkbcomp are not fatal to the X server ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to [EMAIL PROTECTED]
