Re: Resolution problem with i810 and Xorg 7.2
On Mon, 13 Aug 2007 09:35:59 -0500 Doug Poland [EMAIL PROTECTED] wrote: Just a follow-up for the archives... I loaded the 915resolution port and configured my rc.conf accordingly: i915resolution_enable=YES i915resolution_modes=3c 4d 5c i915resolution_width=1680 i915resolution_height=1050 Xorg still failed... snip (II) I810(0): detected 7932 kB stolen memory. (II) I810(0): Kernel reported 0 total, 0 used (II) I810(0): I830CheckAvailableMemory: 0 kB available (WW) I810(0): /dev/agpgart is either not available, or no memory is available for allocation. Using pre-allocated memory only. (II) I810(0): Monitoring connected displays enabled (--) I810(0): Pre-allocated VideoRAM: 7932 kByte (--) I810(0): VideoRAM: 7932 kByte snip (--) I810(0): Xv is disabled because it needs 2D accel and AGPGART. (II) I810(0): Allocated 128 kB for the ring buffer at 0x0 (II) I810(0): Allocating at least 136 scanlines for pixmap cache (II) I810(0): Initial framebuffer allocation size: 11920 kByte (EE) I810(0): Failed to allocate framebuffer. Is your VideoRAM set too low ?? Fatal server error: AddScreen/ScreenInit failed for driver 0 However, when I changed the driver in /etc/X11/xorg.conf from i810 to vesa: Identifier Card0 #Driver i810 Driver vesa VendorName Intel Corporation BoardName Mobile 945GM/GMS/940GML Express Integrated Graphics Controller BusID PCI:0:2:0 Now Xorg starts fine. I'm not sure why it worked but I'm glad it does. I'll go with the VESA driver unless I get any feedback or more info on getting i810 driver to work. Thanks for you help. -- Regards, Doug I was searching couple weeks before on some compiz problems, when i ran into a post which looked similar. The person used an option in xorg.conf to enlarge the framebuffer. I just don't have the link anymore. Try and search with the framebuffer error as keyword, you might find some info. -- Regards, Ghirai. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Resolution problem with i810 and Xorg 7.2
On Mon, 13 Aug 2007 18:26:10 +0300 Ghirai [EMAIL PROTECTED] wrote: (EE) I810(0): Failed to allocate framebuffer. Is your VideoRAM set too low ?? I had this error on my laptop, and solved it by running 6-STABLE. It seems to be related to the agp module which refuses to load on 6.2-RELEASE (hardware too recent, probably). ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Resolution problem with i810 and Xorg 7.2
Gabriel Linder wrote: On Mon, 13 Aug 2007 18:26:10 +0300 Ghirai [EMAIL PROTECTED] wrote: (EE) I810(0): Failed to allocate framebuffer. Is your VideoRAM set too low ?? I had this error on my laptop, and solved it by running 6-STABLE. It seems to be related to the agp module which refuses to load on 6.2-RELEASE (hardware too recent, probably). H... I'm running on a -STABLE kernel compiled on July 20. The agp module does load, but Xorg doesn't see it. -- Regards, Doug ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Resolution problem with i810 and Xorg 7.2
On Sat, Aug 11, 2007 at 12:12:58AM +0300, Ghirai wrote: On Fri, 10 Aug 2007 12:26:46 -0500 (CDT) Doug Poland [EMAIL PROTECTED] wrote: Hello, I've got a Compaq nx7400 running on 6.2-STABLE with Xorg 7.2. Despite my best efforts, I'm unable to get the screen into 1680x1050 resolution. I have followed the instructions in the handbook but the issue appears to be getting /dev/agpgart recognized. Here's some relevant data... snip So all I get out of this flat panel is 1280x1024, which distorts the shape horribly because of the different aspect ratio. Any hints, clues, pointers are very welcome! After you install 915resolutions, you would: #915resolution 5c 1680 1050 Also check the rc startups. I suggest you leave the xorg.conf as it was generated by default, once you patch and start KDE/gnome/whatever, you should get the proper resolution. Just a follow-up for the archives... I loaded the 915resolution port and configured my rc.conf accordingly: i915resolution_enable=YES i915resolution_modes=3c 4d 5c i915resolution_width=1680 i915resolution_height=1050 Xorg still failed... snip (II) I810(0): detected 7932 kB stolen memory. (II) I810(0): Kernel reported 0 total, 0 used (II) I810(0): I830CheckAvailableMemory: 0 kB available (WW) I810(0): /dev/agpgart is either not available, or no memory is available for allocation. Using pre-allocated memory only. (II) I810(0): Monitoring connected displays enabled (--) I810(0): Pre-allocated VideoRAM: 7932 kByte (--) I810(0): VideoRAM: 7932 kByte snip (--) I810(0): Xv is disabled because it needs 2D accel and AGPGART. (II) I810(0): Allocated 128 kB for the ring buffer at 0x0 (II) I810(0): Allocating at least 136 scanlines for pixmap cache (II) I810(0): Initial framebuffer allocation size: 11920 kByte (EE) I810(0): Failed to allocate framebuffer. Is your VideoRAM set too low ?? Fatal server error: AddScreen/ScreenInit failed for driver 0 However, when I changed the driver in /etc/X11/xorg.conf from i810 to vesa: Identifier Card0 #Driver i810 Driver vesa VendorName Intel Corporation BoardName Mobile 945GM/GMS/940GML Express Integrated Graphics Controller BusID PCI:0:2:0 Now Xorg starts fine. I'm not sure why it worked but I'm glad it does. I'll go with the VESA driver unless I get any feedback or more info on getting i810 driver to work. Thanks for you help. -- Regards, Doug ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Resolution problem with i810 and Xorg 7.2
On Fri, August 10, 2007 16:02, Jonathan Horne wrote: On Friday 10 August 2007 14:19:00 Doug Poland wrote: nope im 99% sure thats where your solution will lie. Thanks, I'll give that a try... -- Regards, Doug ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Resolution problem with i810 and Xorg 7.2
Hello, I've got a Compaq nx7400 running on 6.2-STABLE with Xorg 7.2. Despite my best efforts, I'm unable to get the screen into 1680x1050 resolution. I have followed the instructions in the handbook but the issue appears to be getting /dev/agpgart recognized. Here's some relevant data... host% kldstat Id Refs AddressSize Name 1 20 0xc040 729b34 kernel 21 0xc0b2a000 597c vesa.ko 31 0xc0b3 1d684linux.ko 41 0xc0b4e000 129e0snd_hda.ko 52 0xc0b61000 23e38sound.ko 61 0xc0b85000 16db0agp.ko 71 0xc0b9c000 5d6b0acpi.ko /etc/X11/xorg.conf Section Module snip Load dri snip EndSection Section Monitor #DisplaySize 330 210 # mm Identifier Monitor0 VendorName LPL ModelName1279 Modeline 1680x1050 122.00 1680 1712 1776 1904 1050 1051 1054 1066 -hsync -vsync Option DPMS EndSection Section Device Identifier Card0 Driver i810 VendorName Intel Corporation BoardName Mobile 945GM/GMS/940GML Express Integrated Graphics Controller BusID PCI:0:2:0 EndSection Section Screen Identifier Screen0 Device Card0 MonitorMonitor0 SubSection Display Viewport 0 0 Depth 24 Modes 1680x1050 EndSubSection EndSection /var/log/Xorg.0.log snip (II) I810(0): VESA BIOS detected (II) I810(0): VESA VBE Version 3.0 (II) I810(0): VESA VBE Total Mem: 7872 kB (II) I810(0): VESA VBE OEM: Intel(r) 82945GM Chipset Family Graphics Chip Accelerated VGA BIOS (II) I810(0): VESA VBE OEM Software Rev: 1.0 (II) I810(0): VESA VBE OEM Vendor: Intel Corporation (II) I810(0): VESA VBE OEM Product: Intel(r) 82945GM Chipset Family Graphics Controller (II) I810(0): VESA VBE OEM Product Rev: Hardware Version 0.0 (II) I810(0): Integrated Graphics Chipset: Intel(R) 945GM (--) I810(0): Chipset: 945GM (--) I810(0): Linear framebuffer at 0xE000 (--) I810(0): IO registers at addr 0xF440 (==) I810(0): Write-combining range (0xf440,0x8) was already clear (II) I810(0): 2 display pipes available. (II) I810(0): detected 7932 kB stolen memory. (II) I810(0): Kernel reported 0 total, 0 used (II) I810(0): I830CheckAvailableMemory: 0 kB available (WW) I810(0): /dev/agpgart is either not available, or no memory is available for allocation. Using pre-allocated memory only. (II) I810(0): Monitoring connected displays enabled (--) I810(0): Pre-allocated VideoRAM: 7932 kByte (--) I810(0): VideoRAM: 7932 kByte (==) I810(0): video overlay key set to 0x101fe (**) I810(0): page flipping disabled (==) I810(0): Using gamma correction (1.0, 1.0, 1.0) (II) I810(0): BIOS Build: 1305 (==) I810(0): Device Presence: disabled. (==) I810(0): Display Info: enabled. (II) I810(0): Broken BIOSes cause the system to hang here. If you encounter this problem please add Option DisplayInfo FALSE (II) I810(0): Display Info: CRT: attached: FALSE, present: TRUE, size: (1280,1024) (II) I810(0): Display Info: TV: attached: FALSE, present: TRUE, size: (1024,768) (II) I810(0): Display Info: DFP (digital flat panel): attached: FALSE, present: FALSE, size: (0,2059) (II) I810(0): Display Info: LFP (local flat panel): attached: TRUE, present: TRUE, size: (1680,1050) (II) I810(0): Display Info: Second (second CRT): attached: FALSE, present: FALSE, size: (0,2059) (II) I810(0): Display Info: TV2 (second TV): attached: FALSE, present: FALSE, size: (0,2059) (II) I810(0): Size of device LFP (local flat panel) is 1680 x 1050 (II) I810(0): No active displays on Pipe A. (II) I810(0): Currently active displays on Pipe B: (II) I810(0): LFP (local flat panel) (II) I810(0): Lowest common panel size for pipe B is 1680 x 1050 (==) I810(0): Display is using Pipe B (--) I810(0): HW Cursor disabled because it needs agpgart memory. (--) I810(0): Maximum frambuffer space: 7784 kByte (II) I810(0): VESA VBE PanelID read successfully (II) I810(0): PanelID returned panel resolution : 1680x1050 to the Device section of your XF86Config file. snip (II) I810(0): Supported additional Video Mode: (II) I810(0): clock: 122.0 MHz Image Size: 331 x 207 mm (II) I810(0): h_active: 1680 h_sync: 1712 h_sync_end 1776 h_blank_end 1904 h_border: 0 (II) I810(0): v_active: 1050 v_sync: 1051 v_sync_end 1054 v_blanking: 1066 v_border: 0 (II) I810(0): LGPhilipsLCD (II) I810(0): LP154W02-B1K5 (II) I810(0): EDID (in hex): (II) I810(0): 0000320c7912 (II) I810(0): 000f0102802115780abca59554528c27 (II) I810(0): 2350540001010101010101010101 (II) I810(0): 010101010101a82f90e0601a10402040 (II) I810(0): 13004bcf1019 (II) I810(0): 00fe004c (II) I810(0): 475068696c6970734c43440a00fe (II) I810(0): 004c503135345730322d42314b3500b2 (II) I810(0): Printing DDC gathered Modelines: (II) I810(0): Modeline 1680x1050 122.00 1680 1712 1776 1904 1050 1051 1054 1066 -hsync
Re: Resolution problem with i810 and Xorg 7.2
On Friday 10 August 2007 12:26:46 Doug Poland wrote: Hello, I've got a Compaq nx7400 running on 6.2-STABLE with Xorg 7.2. Despite my best efforts, I'm unable to get the screen into 1680x1050 resolution. I have followed the instructions in the handbook but the issue appears to be getting /dev/agpgart recognized. Here's some relevant data... ...[snip] were you using the sysutils/915resolution ? -- Jonathan Horne http://dfwlpiki.dfwlp.org [EMAIL PROTECTED] ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Resolution problem with i810 and Xorg 7.2
On Fri, August 10, 2007 14:08, Jonathan Horne wrote: On Friday 10 August 2007 12:26:46 Doug Poland wrote: Hello, I've got a Compaq nx7400 running on 6.2-STABLE with Xorg 7.2. Despite my best efforts, I'm unable to get the screen into 1680x1050 resolution. I have followed the instructions in the handbook but the issue appears to be getting /dev/agpgart recognized. Here's some relevant data... ...[snip] were you using the sysutils/915resolution ? nope -- Regards, Doug ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Resolution problem with i810 and Xorg 7.2
On Friday 10 August 2007 14:19:00 Doug Poland wrote: nope im 99% sure thats where your solution will lie. http://www.geocities.com/stomljen/ cheers, -- Jonathan Horne http://dfwlpiki.dfwlp.org [EMAIL PROTECTED] ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Resolution problem with i810 and Xorg 7.2
On Fri, 10 Aug 2007 12:26:46 -0500 (CDT) Doug Poland [EMAIL PROTECTED] wrote: Hello, I've got a Compaq nx7400 running on 6.2-STABLE with Xorg 7.2. Despite my best efforts, I'm unable to get the screen into 1680x1050 resolution. I have followed the instructions in the handbook but the issue appears to be getting /dev/agpgart recognized. Here's some relevant data... snip So all I get out of this flat panel is 1280x1024, which distorts the shape horribly because of the different aspect ratio. Any hints, clues, pointers are very welcome! -- Regards, Doug After you install 915resolutions, you would: #915resolution 5c 1680 1050 Also check the rc startups. I suggest you leave the xorg.conf as it was generated by default, once you patch and start KDE/gnome/whatever, you should get the proper resolution. -- Regards, Ghirai. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Resolution Problem
On 2/20/06, Kyle Addis [EMAIL PROTECTED] wrote: Dear FreeBSD, I installed freebsd with kde as my environment, but when I start kde, through the kdm command, my resolution is stuck at 640x320 or something like that, when I go into the desktop configure menu, in kde. My laptop can do up to 1600x1400. Is there anything I can do to make my resolution go higher. Dear Userland :-) I don't use KDE, but resolutions can be changed by editing /etc/X11/xorg.conf. Please, read its manpage or find a good guide. I have this in my screen section: Section Screen Identifier Screen0 Device Card0 MonitorMonitor0 DefaultDepth 24 SubSection Display Viewport 0 0 Depth24 Modes1280x1024 EndSubSection EndSection If anything goes wrong (or have already) you can look at error messages in /var/log/Xorg.0.log ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Resolution Problem
Dear FreeBSD, I installed freebsd with kde as my environment, but when I start kde, through the kdm command, my resolution is stuck at 640x320 or something like that, when I go into the desktop configure menu, in kde. My laptop can do up to 1600x1400. Is there anything I can do to make my resolution go higher. Thank You, Kyle Addis ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
FBSD 5.2.1 - video card resolution problem
Greetings: I am running bsd 5.2.1 and I installed the nvidia driver from the ports for the follwoing video card. dmesg nvidia0: GeForce2 MX 100/200 mem 0xc000-0xc7ff,0xce00-0xceff irq 5 at device 0.0 on pci1 pciconf results: class=0x03 card=0x chip=0x00de rev=0xb2 hdr=0x00 vendor = 'NVIDIA Corporation' device = 'GeForce2 MX 100/200 (DDR) [NV11DDR]' class= display subclass = VGA The installation went good, the card was recognized. The problem is the resolution doesn't get to my desired setting. .. Section Monitor Identifier Monitor0 VendorName SUN ModelName 574 HorizSync 30-70 VertRefresh 50-120 Option DPMS EndSection .. Section Screen Identifier Screen0 Device Card0 Monitor Monitor0 DefaultDepth 24 SubSection Display Depth 24 Modes 1152x864 1024x768 800x600 640x480 EndSubSection EndSection Above are my XF86Config settings but all I get is a resolution of 640x480. Is there a way to get a higher resolution with this card? Thanks, Brian ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: FBSD 5.2.1 - video card resolution problem
On Fri, 16 Apr 2004, Brian Henning wrote: Greetings: I am running bsd 5.2.1 and I installed the nvidia driver from the ports for the follwoing video card. dmesg nvidia0: GeForce2 MX 100/200 mem 0xc000-0xc7ff,0xce00-0xceff irq 5 at device 0.0 on pci1 pciconf results: class=0x03 card=0x chip=0x00de rev=0xb2 hdr=0x00 vendor = 'NVIDIA Corporation' device = 'GeForce2 MX 100/200 (DDR) [NV11DDR]' class= display subclass = VGA The installation went good, the card was recognized. The problem is the resolution doesn't get to my desired setting. .. Section Monitor Identifier Monitor0 VendorName SUN ModelName 574 HorizSync 30-70 VertRefresh 50-120 Option DPMS EndSection .. Section Screen Identifier Screen0 Device Card0 Monitor Monitor0 DefaultDepth 24 SubSection Display Depth 24 Modes 1152x864 1024x768 800x600 640x480 EndSubSection EndSection Above are my XF86Config settings but all I get is a resolution of 640x480. Is there a way to get a higher resolution with this card? Take a look at /var/log/XFree86.0.log; it contains a rather voluminous log written by XFree86. You may find a reason there why modes other than 640x480 are excluded. Regards Konrad Heuer ([EMAIL PROTECTED]) ___ ___ GWDG / __/__ ___ / _ )/ __/ _ \ Am Fassberg / _// __/ -_) -_) _ |\ \/ // / 37077 Goettingen /_/ /_/ \__/\__//___// Germany ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Nvidia resolution problem
I cannot get the resolution for X above 800x600 (although I'm not sure, it could be one smaller than that). The main problem is I can't see all the dialogs for KDE; they won't fit on the screen. I've upgraded the box to FreeBSD 4.8 release. I've uninstalled and reinstalled XFree86 to the latest ports (the overall port is XFree86-4.3.0,1). I'm using the driver from the ports. the Display section has the following modes: 1024x768 800x600 640x480 Any ideas on how to increase the resolution? Thanks, ~Rik ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Nvidia resolution problem
Does your monitor support higher resolutions? If you have an old monitor, did you put proper values in the monitor section of your XF86Config? Ken On Tue, 17 Jun 2003, Rik Scarborough wrote: I cannot get the resolution for X above 800x600 (although I'm not sure, it could be one smaller than that). The main problem is I can't see all the dialogs for KDE; they won't fit on the screen. I've upgraded the box to FreeBSD 4.8 release. I've uninstalled and reinstalled XFree86 to the latest ports (the overall port is XFree86-4.3.0,1). I'm using the driver from the ports. the Display section has the following modes: 1024x768 800x600 640x480 Any ideas on how to increase the resolution? Thanks, ~Rik ___ [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]
Re: Nvidia resolution problem
On Tue, 17 Jun 2003, Kenneth Culver wrote: Does your monitor support higher resolutions? If you have an old monitor, did you put proper values in the monitor section of your XF86Config? It's a new flat screen monitor. I've pretty much ignored that, taking the values from the setup and concentrated on the driver. I'll take a look at that. ~Rik On Tue, 17 Jun 2003, Rik Scarborough wrote: I cannot get the resolution for X above 800x600 (although I'm not sure, it could be one smaller than that). The main problem is I can't see all the dialogs for KDE; they won't fit on the screen. I've upgraded the box to FreeBSD 4.8 release. I've uninstalled and reinstalled XFree86 to the latest ports (the overall port is XFree86-4.3.0,1). I'm using the driver from the ports. the Display section has the following modes: 1024x768 800x600 640x480 Any ideas on how to increase the resolution? Thanks, ~Rik ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Nvidia resolution problem
On Tue, 17 Jun 2003, Rik Scarborough wrote: On Tue, 17 Jun 2003, Kenneth Culver wrote: Does your monitor support higher resolutions? If you have an old monitor, did you put proper values in the monitor section of your XF86Config? It's a new flat screen monitor. I've pretty much ignored that, taking the values from the setup and concentrated on the driver. I'll take a look at that. Another thing, what do you have your default depth at? you should add the resolutions you want to the default depth: Section Screen Identifier Screen0 Device Card0 MonitorMonitor0 DefaultDepth 16 SubSection Display Depth 1 EndSubSection SubSection Display Depth 4 EndSubSection SubSection Display Depth 8 EndSubSection SubSection Display Depth 15 EndSubSection SubSection Display Depth 16 Modes 1280x1024 1152x864 1024x768 800x600 640x480 EndSubSection SubSection Display Depth 24 EndSubSection EndSection Ken ~Rik On Tue, 17 Jun 2003, Rik Scarborough wrote: I cannot get the resolution for X above 800x600 (although I'm not sure, it could be one smaller than that). The main problem is I can't see all the dialogs for KDE; they won't fit on the screen. I've upgraded the box to FreeBSD 4.8 release. I've uninstalled and reinstalled XFree86 to the latest ports (the overall port is XFree86-4.3.0,1). I'm using the driver from the ports. the Display section has the following modes: 1024x768 800x600 640x480 Any ideas on how to increase the resolution? Thanks, ~Rik ___ [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]
Re: localhost name resolution problem
Hello! # host localhost localhost.my.domain is a nickname for my.domain my.domain has address 202.x.x.x Someone suggested I check localhost.: # host localhost. Host not found. AFAIK the host command doesn't use /etc/hosts. No matter what is specified in /etc/host.conf, the host command always uses DNS. I got bitten by the same thing a couple of weeks ago. To check whether localhost resolves to 127.0.0.1, try for example 'ping localhost' Given the contents of your hosts file, you should be OK. -- Toomas Aas | [EMAIL PROTECTED] | http://www.raad.tartu.ee/~toomas/ * Do infants enjoy infancy as much as adults enjoy adultery? ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: localhost name resolution problem
From: Ryan Merrick [EMAIL PROTECTED] W. Sierke wrote: hosts contains ::1 localhost.my.domain localhost 127.0.0.1 localhost.my.domain localhost 192.168.100.1 this_machine.my.domain this_machine 192.168.100.2 another_machine.my.domain another_machine ... Your #/etc/hosts file should read for IPv4 localhost 127.0.0.1localhost.Your_local_domain.com localhost There should be another line in #/etc/hosts your host 192.168.100.1My_host.Your_local_domain.com My_host You can add as many lines as you want. with IP address, hostname, nickname. Indeed, but despite the presence of the (IPv4) localhost entry, sendmail was resolving localhost to my internet IP address, rather than 127.0.0.1. It was suggested to me that the name resolution method that sendmail uses would not use /etc/hosts anyway and since that matched my own experience I'm inclined to think it's true, that's why I resorted to adding bind to the system. After further investigation I've seen two approaches to resolving this issue, one to substitute 127.0.0.1 in place of 'localhost' in the sendmail config files[1], the other to add the sendmail config file /etc/mail/service.switch with the line hosts files dns. But now I'm curious about why these options aren't used in the default installation of sendmail on FreeBSD, given that my situation doesn't appear to be unusual. Does sendmail not use the hosts file by default as a security measure? In any case it just feels dirty to me to have to circumvent this issue on a case-by-case basis - i.e. my thinking at the moment is that a dns facility should resolve 'localhost' correctly. Is that a shared sentiment? Or am I just barking up the wrong tree altogether? Thanks, Wayne [1] - by having FEATURE(`msp', `[127.0.0.1]') in submit.mc ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
localhost name resolution problem
Hi, In the course of trying to resolve a problem with sendmail (refusing to deliver even local mail), I saw a note in the sendmail configuration docs which says host localhost must resolve to 127.0.0.1. However, when I checked my system I instead found (details obscured): # host localhost localhost.my.domain is a nickname for my.domain my.domain has address 202.x.x.x Someone suggested I check localhost.: # host localhost. Host not found. I'm not (wasn't) running a nameserver, my host.conf contains the entries hosts and bind in that order, resolv.conf has a single, automatic (from PPPoE) nameserver entry which works, hostname is set to this_machine.my.domain. hosts contains ::1 localhost.my.domain localhost 127.0.0.1 localhost.my.domain localhost 192.168.100.1 this_machine.my.domain this_machine 192.168.100.2 another_machine.my.domain another_machine ... The domain I'm using is one serviced by dyndns.org, and I have a dynamic IP address. I've now installed bind and have got to the point where localhost again resolves to 127.0.0.1 (and sendmail appears to be happy again). Notably in the process of doing this I've changed my domain name from something.fictitious to my.domain. Now, however, (in part): # host -v localhost Trying domain my.domain rcode = 3 (Non-existent domain), ancount=0 Trying domain domain rcode = 0 (Success), ancount=1 The following answer is not authoritative: The following answer is not verified as authentic by the server: localhost.domain 66929 INA 127.0.0.1 # host -v localhost. rcode = 3 (Non-existent domain), ancount=0 Host not found. Even though I've overcome my initial problem, I'm not happy and rather feel as though I've begun creating a monster (and that's the last thing I wanted to be doing when moving to FreeBSD). For example, I feel somewhat uncomfortable that localhost is now resolving from domain instead of my.domain. I'm also confused about how I should be configuring bind when dyndns.org handles the dns for my domain (and whether I should really be running it at all). But I've exhausted my pitiful knowledge and searching capabilities for the moment. The handbook doesn't appear to be complete (following its example doesn't appear to help with the localhost resolution issue) and all of the material I've trawled up from the 'net is either too hard to follow or too old. Thanks, Wayne ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: localhost name resolution problem
W. Sierke wrote: Hi, In the course of trying to resolve a problem with sendmail (refusing to deliver even local mail), I saw a note in the sendmail configuration docs which says host localhost must resolve to 127.0.0.1. However, when I checked my system I instead found (details obscured): # host localhost localhost.my.domain is a nickname for my.domain my.domain has address 202.x.x.x Someone suggested I check localhost.: # host localhost. Host not found. I'm not (wasn't) running a nameserver, my host.conf contains the entries hosts and bind in that order, resolv.conf has a single, automatic (from PPPoE) nameserver entry which works, hostname is set to this_machine.my.domain. hosts contains ::1 localhost.my.domain localhost 127.0.0.1 localhost.my.domain localhost 192.168.100.1 this_machine.my.domain this_machine 192.168.100.2 another_machine.my.domain another_machine ... Your #/etc/hosts file should read for IPv4 localhost 127.0.0.1localhost.Your_local_domain.com localhost There should be another line in #/etc/hosts your host 192.168.100.1My_host.Your_local_domain.com My_host You can add as many lines as you want. with IP address, hostname, nickname. -Ryan ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
KDE Resolution Problem
Hello , I have problems with my X windows I can't do more than 800x600 ot 16 bits Witch is the tool for changeing this ! On my Windows OS i can do 1024x768 32 Bits My Viedocard is Voodoo 3 2000 and my monitor is Aoc Spectrum 5 Vlr Can somebody help me! Thank you in advance! To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-questions in the body of the message
Re: KDE Resolution Problem
Hello , Hi! I have problems with my X windows I can't do more than 800x600 ot 16 bits Witch is the tool for changeing this ! On my Windows OS i can do 1024x768 32 Bits My Viedocard is Voodoo 3 2000 and my monitor is Aoc Spectrum 5 Vlr You can edit /etc/X11/XF86Config and modify the lines as showed on XFree website (or try to understand how it works.. it's not that har5d) or run : XFree86 -configure which actually creates a default config file for your hardware Cya To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-questions in the body of the message
KDE Resolution problem
i dont have /etc/XF86Config file but i fount my config file in (==) Using config file: /usr/X11R6/lib/X11/XF86Config This is my Screen Section -- Section Screen Identifier Screen0 Device Card0 MonitorMonitor0 SubSection Display Depth 24 Modes 800x600 EndSubSection EndSection and the result is (==) Using config file: /usr/X11R6/lib/X11/XF86Config (EE) TDFX(0): No Display subsection in Screen section Screen0 for depth/fbbpp 8/8 (EE) Screen(s) found, but none have a usable configuration. Fatal server error: no screens found When reporting a problem related to a server crash, please send the full server output, not just the last messages. This can be found in the log file /var/log/XFree86.0.log. Please report problems to [EMAIL PROTECTED] X connection to :0.0 broken (explicit kill or server shutdown). Anyone with idea Thnk you! To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-questions in the body of the message
Re: KDE Resolution problem
Anyone with idea Yes create a default config file with 'XFree86 -configure' If it doesn't work, you'll want to upgrade to XFree 4.X.X instead of 3.X.X Cya To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-questions in the body of the message
