Re: Skipping F1 FreeBSD prompt on boot
On 5/17/07, Pieter de Goeje [EMAIL PROTECTED] wrote: On Thursday 17 May 2007, David Landgren wrote: ok, for extra bonus points, what/where is the code that makes the two annoying BEEPs on shutdown? If I could compile that out, my life would be complete :) Hmm, I've never heard any beeps on shutdown... how do you shutdown your system? When I type 'halt -p' it just powers off after synching the disks, no beep whatsoever. Using the default KDE shutdown command (which just halts the system without turning off the power, curiously enough), I also get these two beeps. Using 6.2-RELEASE. -- Victor Engmark Quidquid latine dictum sit, altum videtur - What is said in Latin, sounds profound ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Can't upgrade ports collection
Hi, I'm getting reports that some of the packages I've installed have vulnerabilities when running portaudit -Fda I've tried to update the ports tree running cd /usr/ports portsnap update , but it tells me the tree is already up to date. I've also tried removing everything from /usr/ports (even the dot files), and then running portsnap fetch portsnap extract portsnap update portupgrade -a (portsnap update should be redundant, but just to be sure), but nothing is upgraded, and portaudit still complains. What am I doing wrong? -- Victor Engmark Quidquid latine dictum sit, altum videtur - What is said in Latin, sounds profound ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Can't upgrade ports collection
On 5/15/07, Karol Kwiatkowski [EMAIL PROTECTED] wrote: Victor Engmark wrote: I'm getting reports that some of the packages I've installed have vulnerabilities when running portaudit -Fda I've tried to update the ports tree running cd /usr/ports portsnap update , but it tells me the tree is already up to date. I've also tried removing everything from /usr/ports (even the dot files), and then running portsnap fetch portsnap extract portsnap update portupgrade -a (portsnap update should be redundant, but just to be sure), but nothing is upgraded, and portaudit still complains. What am I doing wrong? Nothing, the ports tree is frozen right know - virtually nothing will be updated until xorg 7.2 gets tested and imported[1]. Cool stuff, but do you recommend I uninstall the problematic packages? Also, aren't security patches normally shipped quickly to the ports tree? -- Victor Engmark Quidquid latine dictum sit, altum videtur - What is said in Latin, sounds profound ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Dell D610 touchpad configuration
On 4/27/07, Victor Engmark [EMAIL PROTECTED] wrote: I'm attempting to configure my laptop properly for X.org, and the only device which doesn't work properly now is the touchpad. The tutorials I've seen so far seem to assume that all touchpads use the Synaptic driver, but this is the information I get at boot time, and which I assume is the touchpad: $ dmesg | grep psm0 psm0: PS/2 Mouse irq 12 on atkbdc0 psm0: [GIANT-LOCKED] psm0: model GlidePoint, device ID 0 Finally, I got a working setup with both mice working at the same time. Turns out I had to ditch the synaptics driver. In case someone else needs it, here goes... xorg.conf relevant sections (with #comments): Section ServerLayout Identifier Dell Latitude D610 Screen 0 Dell Latitude D610 screen 0 0 InputDeviceAlps GlidePoint Touchpad InputDeviceDell USB mouse InputDeviceDell Latitude D610 keyboard EndSection # Don't load synaptics in the Module section Section InputDevice Identifier Alps GlidePoint Touchpad Driver mouse # Don' Option CorePointer # This makes X.org startup fail if the device can't be initialized Option Device/dev/psm0 # This may be different on other *nixes Option Protocol PS/2 # Using GlidePoint gave some weird behavior # The following options are not mandatory, as far as I can see Option LeftEdge 1700 Option RightEdge 5300 Option TopEdge 1700 Option BottomEdge4200 Option FingerLow 25 Option FingerHigh30 Option MaxTapTime180 Option MaxTapMove220 Option VertScrollDelta 100 Option HorizScrollDelta 100 Option MinSpeed 0.06 Option MaxSpeed 0.06 Option AccelFactor 0.0010 Option ScrollButtonRepeat100 Option UpDownScrolling on Option UpDownRepeat on Option LeftRightScrollingon Option LeftRightRepeat on Option SHMConfig on Option Emulate3Buttons off EndSection Section InputDevice Identifier Dell USB mouse Driver mouse Option AlwaysCore on Option Device /dev/sysmouse Option Protocolauto Option Buttons 5 Option ZAxisMapping4 5 # Scroll wheel Option Emulate3Buttons off EndSection -- Victor Engmark Quidquid latine dictum sit, altum videtur - What is said in Latin, sounds profound ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Dell D610 touchpad configuration
On 5/15/07, Victor Engmark [EMAIL PROTECTED] wrote: Driver mouse # Don' Sorry, Gmail got hold of the email with a stray CTRL sequence. The comment was just supposed to be: Don't use synaptics, contrary to different tutorials / forum posts it won't work. Also, AlwaysCore is necessary for the secondary mouse to make sure events from it (movement, clicks) are picked up by X. It is equivalent to SendCoreEvents, according to man xorg.conf No moused settings are necessary with this setup. -- Victor Engmark Quidquid latine dictum sit, altum videtur - What is said in Latin, sounds profound ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: font problems in firefox, thunderbird,.. gtk?
On 5/6/07, Jan Zach [EMAIL PROTECTED] wrote: after system and ports upgrade I have problems with fonts in some apps - firefox, thunderbird, gthumb, liferea and so on. It is probably related to the underlying toolkit - gtk2? The problem is that sometimes (not regularly) the app system fonts are not that expected ones but they are proportional and blurred - almost unreadable. Usually it helps to restart the app, sometimes more than once. I was searching the Internet, experimenting with xorg.conf and installed fonts, font cache etc. but got no results. With my previous installation I have had similar problems but really seldom not on regular basis as now. Have you used the handbook section regarding fontshttp://www.freebsd.org/doc/en_US.ISO8859-1/books/handbook/x-fonts.html, especially the part regarding editing /usr/X11R6/etc/fonts/local.conf? For the most part it works. If you have, could you post a (small) screenshot with an example? -- Victor Engmark Quidquid latine dictum sit, altum videtur - What is said in Latin, sounds profound ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: How to find HorizSync / VertRefresh rates?
On 5/4/07, Ted Mittelstaedt [EMAIL PROTECTED] wrote: [mailto:[EMAIL PROTECTED] Behalf Of Victor Engmark It works in the sense that I get the correct dimensions, Then it is working. Your done, quit diddling with it. but I'm unsure as to whether I risk frying the card or screen You cannot fry either. An LCD panel has a computer that will take a specified range of vert and horz sync frequencies. As I already mentioned these sync frequencies are meaningless with an LCD, since the display chip merely converts them to what the LCDs in the panel actually need. It is more expensive to make a display chip that takes extremely high frequencies and since they aren't needed for LCD that is why the display chips in the panels do not accept as high frequencies as a really high quality crt will. Alright, I'll take your word for it. Thanks to everybody who contributed! -- Victor Engmark Quidquid latine dictum sit, altum videtur - What is said in Latin, sounds profound ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: How to find HorizSync / VertRefresh rates?
On 5/2/07, Dag-Erling Smørgrav [EMAIL PROTECTED] wrote: Victor Engmark [EMAIL PROTECTED] writes: I'm trying to create a pristine xorg.conf, but I've been unable to find proper values for HorizSync and VertRefresh for my Dell Latitude D610. These parameters are meaningless for an LCD panel. Leave them out, and X.org will DTRT. The wrong values will *not* fry your panel. OK, I'll settle for that one. But then, why do I get a warning that the default HorizSync rate is out of the DDC rates for my screen? I assume that the screen will report a bogus value when queried about the rate if it's not applicable. X.org should be able to detect such values, to avoid any false warnings. Anyone else think this warrants a bug report? -- Victor Engmark Quidquid latine dictum sit, altum videtur - What is said in Latin, sounds profound ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: How to find HorizSync / VertRefresh rates?
On 5/3/07, Greg 'groggy' Lehey [EMAIL PROTECTED] wrote: On Tuesday, 1 May 2007 at 9:28:27 +0200, Victor Engmark wrote: On 5/1/07, Greg 'groggy' Lehey [EMAIL PROTECTED] wrote: On Monday, 30 April 2007 at 11:02:54 +0200, Victor Engmark wrote: 1: Try XFree86. Maybe that will work better. I'm a bit reluctant to straying away from the recommended setup on my work machine. Even if the recommended setup doesn't work? Note that we have both in the ports collection, so the definition of recommended sounds more like default to me. It works in the sense that I get the correct dimensions, but I'm unsure as to whether I risk frying the card or screen by using the current values, and whether I can somehow establish which values would be optimal for my card and screen. Besides, isn't the code base for this and X.org still very similar? Yes, but there have been many edge cases where one works and the other doesn't. In general, X.org brings better results, but it's worth a try. Alright, thanks. I'll see about it. Get hold of the latest Knoppix CD from http://www.knoppix.org/, burn it to CD, boot from it and see if that works. Knoppix is a Linux distribution that runs from CD, so it's good for this kind of test. I still don't understand how it will provide the values I'm looking for. I note that none of the other messages that have gone by in this thread have addressed what I consider to be the crucial point: you have a BIOS mapping issue. It would be interesting to know what version of FreeBSD you're running. 6.2-RELEASE. -- Victor Engmark Quidquid latine dictum sit, altum videtur - What is said in Latin, sounds profound ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: How to find HorizSync / VertRefresh rates?
On 5/3/07, Greg 'groggy' Lehey [EMAIL PROTECTED] wrote: On Thursday, 3 May 2007 at 9:25:54 +0200, Victor Engmark wrote: On 5/3/07, Greg 'groggy' Lehey [EMAIL PROTECTED] wrote: On Tuesday, 1 May 2007 at 9:01:26 +0200, Victor Engmark wrote: On 4/30/07, Erik Osterholm [EMAIL PROTECTED] wrote: Could you post your Xorg.0.log and xorg.conf? When Theory != Practice, it's often helpful to have information like this to help determine what went wrong, so that in the future, Theory can == Practice. Here you go: /etc/X11/xorg.conf and /var/log/Xorg.0.log from this morning. I don't see the Xorg.0.log. Also, it would be interesting to see how the xorg.conf differs from the one you got from X -configure. The xorg.conf differs quite a lot. And how? Does it work? For the currently applicable definition of work, no. I get a warning message from X.org every time I boot. I used xorgconfig instead of X -configure , but xorgconfig doesn't autodetect any of the ranges, so there were none in the original file. Here's a cut'n'paste of the Xorg.0.log sent earlier: You didn't send it. According to Gmail, I did. I copied the file from the email I sent :) This is a pre-release version of the X server from The X.Org Foundation. It is not supported in any way. Bugs may be filed in the bugzilla at http://bugs.freedesktop.org/. Select the xorg product for bugs you find in this release. Before reporting bugs in pre-release versions please check the latest version in the X.Org Foundation CVS repository. See http://wiki.x.org/wiki/CvsPage for CVS access instructions. X Window System Version 6.8.99.903 (6.9.0 RC 3) Release Date: 03 December 2005 + cvs Where did you get this from? 6.2-RELEASE used 6.9.0 release. Try rebuilding from the Ports Collection. I burned the 6.2-RELEASE CD from freebsd.org. After installing a lot of software, I ran portupgrade -a . Surely, I should have the same or newer than the release by then? Also, pkg_version -vIL= right now doesn't list X.org. -- Victor Engmark Quidquid latine dictum sit, altum videtur - What is said in Latin, sounds profound ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: How to find HorizSync / VertRefresh rates?
On 5/3/07, Greg 'groggy' Lehey [EMAIL PROTECTED] wrote: On Thursday, 3 May 2007 at 11:16:04 +0200, Victor Engmark wrote: On 5/3/07, Greg 'groggy' Lehey [EMAIL PROTECTED] wrote: On Thursday, 3 May 2007 at 9:25:54 +0200, Victor Engmark wrote: On 5/3/07, Greg 'groggy' Lehey [EMAIL PROTECTED] wrote: On Tuesday, 1 May 2007 at 9:01:26 +0200, Victor Engmark wrote: On 4/30/07, Erik Osterholm [EMAIL PROTECTED] wrote: Could you post your Xorg.0.log and xorg.conf? When Theory != Practice, it's often helpful to have information like this to help determine what went wrong, so that in the future, Theory can == Practice. Here you go: /etc/X11/xorg.conf and /var/log/Xorg.0.log from this morning. I don't see the Xorg.0.log. Also, it would be interesting to see how the xorg.conf differs from the one you got from X -configure. The xorg.conf differs quite a lot. And how? Does it work? For the currently applicable definition of work, no. I get a warning message from X.org every time I boot. OK. Either you give me information on what happens, or I'll drop the case. What warning message? Please read the rest of the thread. I'm getting a warning that the HorizSync rate is outside the capabilities of my current hardware, whether I use the default (none), the values from MonitorsDB, or what other people have posted in their xorg.conf files for other Dell Latitude D610s. Why when you boot? Because I run KDE at boot. From /etc/ttys: ttyv8 /usr/local/bin/kdm -nodaemon xterm on secure What does the screen look like? Fine. That's not the issue, as stated several times in this thread. What does the Xorg.0.log look like? I've sent it twice. What else do you want to know? I used xorgconfig instead of X -configure , but xorgconfig doesn't autodetect any of the ranges, so there were none in the original file. Here's a cut'n'paste of the Xorg.0.log sent earlier: You didn't send it. According to Gmail, I did. Here's what arrived here: Here you go: /etc/X11/xorg.conf and /var/log/Xorg.0.log from this morning. ... [-- Attachment #2: xorg.conf --] [-- Type: application/octet-stream, Encoding: base64, Size: 6.0K --] [-- application/octet-stream is unsupported (use 'v' to view this part) --] [-- Attachment #3 --] [-- Type: text/plain, Encoding: 7bit, Size: 0.2K --] I copied the file from the email I sent :) Is it also in the mail you received? It's definitely not here. I only see the version which was sent by Gmail. It collates my emails when I receive one I sent myself. Maybe the attachment was too big for the list, but I didn't receive any error messages or warnings. Here are the headers for the attachment: --=_Part_133278_20384899.1178002886715 Content-Type: text/x-log; name=Xorg.0.log; charset=ANSI_X3.4-1968 Content-Transfer-Encoding: base64 X-Attachment-Id: f_f160abdg Content-Disposition: attachment; filename=Xorg.0.log This is a pre-release version of the X server from The X.Org Foundation. It is not supported in any way. Where did you get this from? 6.2-RELEASE used 6.9.0 release. Try rebuilding from the Ports Collection. I burned the 6.2-RELEASE CD from freebsd.org. After installing a lot of software, From where? Official FreeBSD mirrors. I don't know where to find the settings, but I used the first Swiss mirror in sysinstall. I ran portupgrade -a . Surely, I should have the same or newer than the release by then? Based on your statements, it's hard to say. Based on me installing from an official CD, and using the default settings for portupgrade? In that case, I don't understand why. Also, pkg_version -vIL= right now doesn't list X.org. This suggests that you installed it from elsewhere. As I said, I installed from the official FreeBSD mirrors. Try rebuilding from the Ports Collection. I've already done a portupgrade -a since I installed. -- Victor Engmark Quidquid latine dictum sit, altum videtur - What is said in Latin, sounds profound ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: How to find HorizSync / VertRefresh rates?
On 5/3/07, Dag-Erling Smørgrav [EMAIL PROTECTED] wrote: Victor Engmark [EMAIL PROTECTED] writes: OK, I'll settle for that one. But then, why do I get a warning that the default HorizSync rate is out of the DDC rates for my screen? I can't tell unless you show me the log. /var/log/Xorg.0.log has been posted twice in this thread. If you mean another log, then please specify. -- Victor Engmark Quidquid latine dictum sit, altum videtur - What is said in Latin, sounds profound ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: How to find HorizSync / VertRefresh rates?
On 5/2/07, Ted Mittelstaedt [EMAIL PROTECTED] wrote: I feel the need to remind folks that the concept of refresh rates is completely meaningless with LCD panels. Flatpanels do not have a single scan gun that draws lines at a specific time and rate of speed across a phosphor. Well, the rates are both related to the video card, not the display. I'm not sure how the card feeds the image to an LCD display, but I guess that would depend on the enforced horizontal sync and vertical refresh rates. In any case, it's useful to have these rates if I should ever have the need to attach the card to an external CRT display. The computer in the LCD panel takes the video input at a range of refresh rates, and converts it to a bitmapped image that is fed to the display crystals. You can use whatever horizontal and vertical refresh rates you want, as long as they are in the table that the LCD panel's computer can decode, the resulting output is the same. Even though LCD displays don't flicker, it's useful to set the refresh as high as the panel is able to display, to get smooth transitions. I also will remind people that the pixel counts as resolution on flatpanels also have no meaning. A flat panel has a fixed natural resolution. Any other resolution that you feed to it is either dithered up or dithered down to match the actual resolution by the display computer in the flat panel. I'm well aware of that, but I would still like my video card and screen to perform to the best of their abilities, in order to display the biggest amount of data per second possible, without frying. Anything else is a waste of resources. -- Victor Engmark Quidquid latine dictum sit, altum videtur - What is said in Latin, sounds profound ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: How to find HorizSync / VertRefresh rates?
On 5/2/07, Ted Mittelstaedt [EMAIL PROTECTED] wrote: [mailto:[EMAIL PROTECTED] Behalf Of Victor Engmark On 5/2/07, Ted Mittelstaedt [EMAIL PROTECTED] wrote: The computer in the LCD panel takes the video input at a range of refresh rates, and converts it to a bitmapped image that is fed to the display crystals. You can use whatever horizontal and vertical refresh rates you want, as long as they are in the table that the LCD panel's computer can decode, the resulting output is the same. Even though LCD displays don't flicker, it's useful to set the refresh as high as the panel is able to display, to get smooth transitions. Try different rates, I think you will find that once you get above 70 Hz you won't be able to see any difference. But then my card / screen may be fried. And the human eye cannot see distinct pictures at refresh rates beyond about 30-40 frames per second. You may see flicker, but the human eye cannot even distinguish that, much beyond 65-70Hz. http://www.100fps.com/how_many_frames_can_humans_see.htm - Interesting reading in that respect. Screens still have a long way to go. The rest of the mail looks like trolling, so I'll just leave those parts alone. I only need one of the following three: - Reference documentation where the capabilities of my screen is explained. - A working method for finding this information on my own. - A good explanation for why I should ignore the X.org warnings. -- Victor Engmark Quidquid latine dictum sit, altum videtur - What is said in Latin, sounds profound ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: How to find HorizSync / VertRefresh rates?
On 4/30/07, Erik Osterholm [EMAIL PROTECTED] wrote: On Mon, Apr 30, 2007 at 08:33:03PM +0200, Victor Engmark wrote: On 4/30/07, J65nko [EMAIL PROTECTED] wrote: Follow the FBSD handbook to do a 'Xorg -configure' and a test run of X with the generated Xorg.conf file. I did. Then have a look at your your '/var/log/Xorg.0.log'. You will find a log of X using DDC to interrogate your LCD screen for it's capabilities and the acceptable modelines Nope. Already tried that, and the capabilities were /not/ listed in the log, the way it was described in several tutorials. rantThis is starting to look like one of the most common problems in F/OSS: Theory != Practice. In theory, any one of the methods already tried and suggested here should work. In practice, the documentation (MonitorsDB) is wrong (at least according to x.org), and none of the quoted methods work the way they should. An interesting result is that there are several fundamentally different tutorials for several closely related *nixes, all of which work only on a small subset of installations./rant Could you post your Xorg.0.log and xorg.conf? When Theory != Practice, it's often helpful to have information like this to help determine what went wrong, so that in the future, Theory can == Practice. Here you go: /etc/X11/xorg.conf and /var/log/Xorg.0.log from this morning. -- Victor Engmark Quidquid latine dictum sit, altum videtur - What is said in Latin, sounds profound xorg.conf Description: Binary data ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
How to find HorizSync / VertRefresh rates?
Hi all, I'm trying to create a pristine xorg.conf, but I've been unable to find proper values for HorizSync and VertRefresh for my Dell Latitude D610. I've tried the values presented in MonitorsDB http://sources.gentoo.org/viewcvs.py/gentoo/src/hwdata/MonitorsDB?view=markup for Dell 1400x1050 Laptop Display Panel, which are HorizSync 31.5-90.0 and VertRefresh 59.0-75.0, but I get a warning in /var/log/Xorg.0.log for both of them saying they are not within DDC ranges. I've tried looking around the Dell web pages, but I haven't found any pages mentioning these parameters (not too surprising, really). I've tried to leave these settings out, but even then I get a warning: (WW) I810(0): config file hsync range 60-66.3158kHz not within DDC hsync ranges. I'm wondering if this has anything to do with the other warnings I get during startup: (WW) I810(0): Bad V_BIOS checksum and (WW) I810(0): Extended BIOS function 0x5f05 failed. It seems that a DDC (or, apparently, DDS) query should be able to determine these numbers, but cd /usr/ports make search name=ddc make search name=dds doesn't give any tools to deal with this. The relevant part of /etc/X11/xorg.conf: Section Monitor Identifier Dell Latitude D610 monitor VendorName SEC ModelName3450 # From Xorg.0.log DisplaySize 286 214 Option DPMS EndSection -- Victor Engmark Quidquid latine dictum sit, altum videtur - What is said in Latin, sounds profound ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Dell D610 touchpad configuration
On 4/27/07, Matt Kosht [EMAIL PROTECTED] wrote: On 4/27/07, Victor Engmark [EMAIL PROTECTED] wrote: I'm attempting to configure my laptop properly for X.org, and the only device which doesn't work properly now is the touchpad. The tutorials I've seen so far seem to assume that all touchpads use the Synaptic driver, but this is the information I get at boot time, and which I assume is the touchpad: $ dmesg | grep psm0 psm0: PS/2 Mouse irq 12 on atkbdc0 psm0: [GIANT-LOCKED] psm0: model GlidePoint, device ID 0 Apropos, dmesg | grep -i synapt gives no output, and dmesg | grep -i mouse only shows the PS/2 + the USB mouse. I have a Dell Latitude D820 (uses same synaptics touchpad as your) with the same issue as you. There is another change required by the driver to work correctly. you need to add this line in your /boot/loader.conf hw.psm.synaptics_support=1 This didn't make it work for me, but I would be curious if it did for you and I can try to duplicate what you are doing. Sorry, I didn't mention this - I already added it (without the quotes; I guess they are not significant): $ grep synaptics /boot/loader.conf hw.psm.synaptics_support=1 -- Victor Engmark Quidquid latine dictum sit, altum videtur - What is said in Latin, sounds profound ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
OpenGL in KDE only on top 420 pixels
Hi all, I'm currently running KDE 3.5.6 on 6.2-RELEASE, and I've tested OpenGL with the screen savers from the OpenGL Screen Sav... [sic] category. The results so far: - KRotation doesn't work at all, but I don't get any error messages, and `grep -iR krotation /var/log/*` doesn't give any results. - KPendulum and Space work and are centered on the screen. - All the others (Bitmap Flag, Euphoria, Fireworks 3D, Flux, Gravity, Particle Fountain, and Solar Winds) use only the top 420 pixels of the screen. It looks as though the graphics has been displaced, because it doesn't look like it's been scaled to fit the area, and it also doesn't look like the bottom 630 px (my screen is 1400x1050 px) have been cropped. Searching Google and the KDE http://bugs.kde.org/ and x.orghttps://bugs.freedesktop.org/bug databases didn't produce any results which seem related. Any tips? Here are the relevant parts of my /etc/X11/xorg.conf: Section Monitor Identifier Dell Latitude D610 monitor VendorName SEC ModelName3450 DisplaySize 285.7 214.3 Option DPMS EndSection Section Device Identifier Intel 915GM Driver i810 VendorName Intel Corporation BoardName Mobile 915GM/GMS/910GML Express Graphics Controller BusID PCI:0:2:0 EndSection Section Screen Identifier Dell Latitude D610 screen Device Intel 915GM Monitor Dell Latitude D610 monitor DefaultDepth 24 SubSection Display Depth 1 Modes 1400x1050 1024x768 EndSubSection SubSection Display Depth 4 Modes 1400x1050 1024x768 EndSubSection SubSection Display Depth 8 Modes 1400x1050 1024x768 EndSubSection SubSection Display Depth 15 Modes 1400x1050 1024x768 EndSubSection SubSection Display Depth 16 Modes 1400x1050 1024x768 EndSubSection SubSection Display Depth 24 Modes 1400x1050 1024x768 EndSubSection EndSection Section DRI Mode 0666 EndSection Also, I use the following to enable the native resolution: $ tail -1 /etc/rc.d/local /usr/local/bin/915resolution 3c 1400 1050 -- Victor Engmark Quidquid latine dictum sit, altum videtur - What is said in Latin, sounds profound ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: How to find HorizSync / VertRefresh rates?
On 4/30/07, [EMAIL PROTECTED] [EMAIL PROTECTED] wrote: On Mon, 30 Apr 2007, Victor Engmark wrote: I'm trying to create a pristine xorg.conf, but I've been unable to find proper values for HorizSync and VertRefresh for my Dell Latitude D610. I've tried the values presented in MonitorsDB http://sources.gentoo.org/viewcvs.py/gentoo/src/hwdata/MonitorsDB?view=markup for Dell 1400x1050 Laptop Display Panel, which are HorizSync 31.5-90.0 and VertRefresh 59.0-75.0, but I get a warning in /var/log/Xorg.0.log for both of them saying they are not within DDC ranges. I've tried looking around the Dell web pages, but I haven't found any pages mentioning these parameters (not too surprising, really). I've tried to leave these settings out, but even then I get a warning: (WW) I810(0): config file hsync range 60-66.3158kHz not within DDC hsync ranges. I'm wondering if this has anything to do with the other warnings I get during startup: (WW) I810(0): Bad V_BIOS checksum and (WW) I810(0): Extended BIOS function 0x5f05 failed. It seems that a DDC (or, apparently, DDS) query should be able to determine these numbers, but cd /usr/ports make search name=ddc make search name=dds doesn't give any tools to deal with this. The relevant part of /etc/X11/xorg.conf: Section Monitor Identifier Dell Latitude D610 monitor VendorName SEC ModelName3450 # From Xorg.0.log DisplaySize 286 214 Option DPMS EndSection Get the info off any labels you might find on your monitor and go to: www.monitorworld.com You might get lucky Thanks, but no luck. There are no labels (it's a laptop screen), and the Dell product pagehttp://accessories.us.dell.com/sna/productdetail.aspx?sku=R6313doesn't provide any useful information. Too bad MonitorWorld doesn't allow indexing http://monitorworld.com/robots.txt, or it would actually be searchable (their search sucks). -- Victor Engmark Quidquid latine dictum sit, altum videtur - What is said in Latin, sounds profound ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: How to find HorizSync / VertRefresh rates?
On 4/30/07, John Murphy [EMAIL PROTECTED] wrote: Victor Engmark wrote: I'm trying to create a pristine xorg.conf, but I've been unable to find proper values for HorizSync and VertRefresh for my Dell Latitude D610. I've tried the values presented in MonitorsDB http://sources.gentoo.org/viewcvs.py/gentoo/src/hwdata/MonitorsDB?view=markup for Dell 1400x1050 Laptop Display Panel, which are HorizSync 31.5-90.0 and VertRefresh 59.0-75.0, but I get a warning in /var/log/Xorg.0.log for both of them saying they are not within DDC ranges. I've tried looking around the Dell web pages, but I haven't found any pages mentioning these parameters (not too surprising, really). I've tried to leave these settings out, but even then I get a warning: (WW) I810(0): config file hsync range 60-66.3158kHz not within DDC hsync ranges. I'm wondering if this has anything to do with the other warnings I get during startup: (WW) I810(0): Bad V_BIOS checksum and (WW) I810(0): Extended BIOS function 0x5f05 failed. It seems that a DDC (or, apparently, DDS) query should be able to determine these numbers, but cd /usr/ports make search name=ddc make search name=dds doesn't give any tools to deal with this. The relevant part of /etc/X11/xorg.conf: Section Monitor Identifier Dell Latitude D610 monitor VendorName SEC ModelName3450 # From Xorg.0.log DisplaySize 286 214 Option DPMS EndSection Not sure if this will help, but there's some good information from a Linux Dell D610 user who seems to have a good xorg.conf which should be roughly the same for FreeBSD: http://www.kcore.org/?menumain=4menusub=2 The xorg.conf there doesn't define HorizSync or VertRefresh. He mentions a video BIOS patch called '915resolution'. There's a FreeBSD version at: http://www.freebsd.org/cgi/url.cgi?ports/sysutils/915resolution/pkg-descr More information on the hack here: http://www.geocities.com/stomljen/ I'm already using this. It's listed at the end of my email. In case my message was unclear, I've already managed to get the native resolution. I'm only looking for the proper HorizSync / VertRefresh rates, to avoid frying my graphics card or screen, and to get the maximum out of my hardware at the same time. I've already tried rates from several articles, but all of them result in warnings that the rates are outside the DDC spec, and none of them document where the numbers are from. The only reference I've found so far, MonitorsDB, is wrong, and Dell doesn't list the information I need. -- Victor Engmark Quidquid latine dictum sit, altum videtur - What is said in Latin, sounds profound ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: How to find HorizSync / VertRefresh rates?
On 4/30/07, Tom Evans [EMAIL PROTECTED] wrote: On Mon, 2007-04-30 at 11:02 +0200, Victor Engmark wrote: I'm trying to create a pristine xorg.conf, but I've been unable to find proper values for HorizSync and VertRefresh for my Dell Latitude D610. Don't bother trying. If it works when you leave them unspecified, don't think any more about it. I'd rather not have to replace my laptop after a few weeks... If it still doesn't work however, the easiest way is to construct a valid modeline specific to your monitor. Xorg can actually tell you what to put into your xorg.conf, see section 5.4.3.2 of the FreeBSD Handbook [1] It works, but the issue is rather having the /correct/ configuration in order to utilize the hardware as well as possible without frying it. I've tried the method proposed, but I don't find the information mentioned. -- Victor Engmark Quidquid latine dictum sit, altum videtur - What is said in Latin, sounds profound ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: How to find HorizSync / VertRefresh rates?
On 4/30/07, J65nko [EMAIL PROTECTED] wrote: On 4/30/07, Victor Engmark [EMAIL PROTECTED] wrote: I'm trying to create a pristine xorg.conf, but I've been unable to find proper values for HorizSync and VertRefresh for my Dell Latitude D610. I've tried the values presented in MonitorsDB http://sources.gentoo.org/viewcvs.py/gentoo/src/hwdata/MonitorsDB?view=markup for Dell 1400x1050 Laptop Display Panel, which are HorizSync 31.5-90.0 and VertRefresh 59.0-75.0, but I get a warning in /var/log/Xorg.0.log for both of them saying they are not within DDC ranges. [snip] (WW) I810(0): config file hsync range 60-66.3158kHz not within DDC hsync ranges. [snip] It seems that a DDC (or, apparently, DDS) query should be able to determine these numbers, but [snip] I don't understand why people still configure X the old ancient way. Follow the FBSD handbook to do a 'Xorg -configure' and a test run of X with the generated Xorg.conf file. I did. Then have a look at your your '/var/log/Xorg.0.log'. You will find a log of X using DDC to interrogate your LCD screen for it's capabilities and the acceptable modelines Nope. Already tried that, and the capabilities were /not/ listed in the log, the way it was described in several tutorials. rantThis is starting to look like one of the most common problems in F/OSS: Theory != Practice. In theory, any one of the methods already tried and suggested here should work. In practice, the documentation (MonitorsDB) is wrong (at least according to x.org), and none of the quoted methods work the way they should. An interesting result is that there are several fundamentally different tutorials for several closely related *nixes, all of which work only on a small subset of installations./rant -- Victor Engmark Quidquid latine dictum sit, altum videtur - What is said in Latin, sounds profound ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Dell D610 touchpad configuration
Hi all, I'm attempting to configure my laptop properly for X.org, and the only device which doesn't work properly now is the touchpad. The tutorials I've seen so far seem to assume that all touchpads use the Synaptic driver, but this is the information I get at boot time, and which I assume is the touchpad: $ dmesg | grep psm0 psm0: PS/2 Mouse irq 12 on atkbdc0 psm0: [GIANT-LOCKED] psm0: model GlidePoint, device ID 0 Apropos, dmesg | grep -i synapt gives no output, and dmesg | grep -i mouse only shows the PS/2 + the USB mouse. I've tried a lot of tutorials, restarting whenever I change something, but I always end up with the following problem: $ grep ^\(EE\) /var/log/Xorg.0.log (EE) Synaptics Touchpad Found no Synaptics, found Mouse model 1 instead (EE) Synaptics Touchpad no synaptics touchpad detected and no repeater device (EE) Synaptics Touchpad Unable to query/initialize Synaptics hardware. (EE) PreInit failed for input device Synaptics Touchpad Another command which might shed some light over the situation: $ cat /dev/psm0 cat: /dev/psm0: Resource temporarily unavailable Relevant sections from /etc/X11/xorg.conf: Section ServerFlags Option DefaultServerLayout Dell Latitude D610 EndSection Section ServerLayout Identifier Dell Latitude D610 Screen 0 Dell Latitude D610 screen 0 0 InputDeviceDell USB mouse CorePointer InputDeviceSynaptics Touchpad AlwaysCore InputDeviceDell Latitude D610 keyboard CoreKeyboard EndSection Section Module ... Load synaptics # Ran this first: cd /usr/ports/x11-servers/synaptics make install ... EndSection Section InputDevice Identifier Synaptics Touchpad Driver synaptics Option AlwaysCore Option Device/dev/psm0 Option Protocol psm #Option SendCoreEventson Option LeftEdge 1700 Option RightEdge 5300 Option TopEdge 1700 Option BottomEdge4200 Option FingerLow 25 Option FingerHigh30 Option MaxTapTime180 Option MaxTapMove220 Option VertScrollDelta 100 Option HorizScrollDelta 100 Option MinSpeed 0.06 Option MaxSpeed 0.06 Option AccelFactor 0.0010 Option ScrollButtonRepeat100 Option UpDownScrolling on Option UpDownRepeat on Option LeftRightScrollingon Option LeftRightRepeat on Option SHMConfig on EndSection Section InputDevice Identifier Dell USB mouse Driver mouse Option CorePointer Option Device /dev/sysmouse Option Protocol auto Option ZAxisMapping 4 5 6 7 EndSection For the record, the USB mouse, keyboard, and graphical settings work fine. -- Victor Engmark Quidquid latine dictum sit, altum videtur - What is said in Latin, sounds profound ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: FBSD RSS feed
On 4/20/07, [EMAIL PROTECTED] [EMAIL PROTECTED] wrote: Why the RSS feed of the security advisories does not work with Fire Fox? http://www.freebsd.org/security/advisories.rdf This XML file does not appear to have any style information associated with it. The document tree is shown below. That file is not an RSS feed, just a plain XML file. It's also served with the MIME type text/xml. -- Victor Engmark Quidquid latine dictum sit, altum videtur - What is said in Latin, sounds profound ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Configuring Network In FreeBSD 6.2 Release
On 4/18/07, Dhananjaya hiremath [EMAIL PROTECTED] wrote: We have problem with how to configure the internet in FreeBSD 6.2 RELEASE and how to usr internet in this OS.Please guide us sir, The excellent FreeBSD Handbook should provide the information you need: http://www.freebsd.org/doc/en_US.ISO8859-1/books/handbook/config-network-setup.html You can also find the handbook in other languages: ftp://ftp.freebsd.org/pub/FreeBSD/doc/ -- Victor Engmark Quidquid latine dictum sit, altum videtur - What is said in Latin, sounds profound ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: I like Ubuntu
On 4/13/07, Claude Menski [EMAIL PROTECTED] wrote: Why is freebsd better then ubuntu? More useful documentation (the Handbook is great) and easier to debug than any Linux distribution I've ever tried (including Mandrake, Ubuntu, Kubuntu, SUSE 6.3, SLED, Debian, SLC, and MEPIS). There's also a good chance an answer, tutorial, or howto from 1999 is still applicable, unlike for Linux. -- Victor Engmark Quidquid latine dictum sit, altum videtur - What is said in Latin, sounds profound ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: FreeBSD 6.2-RELEASE install boot halts
On 4/4/07, Victor Engmark [EMAIL PROTECTED] wrote: I've downloaded and burned the boot CD for the i386 6.2-RELEASE. I've used the CD to install a very well running system on my laptop, but it halts during boot when I try to install with the same CD on my desktop PC. The last line it outputs before halting is the following: acd0: DVDR PLEXTOR DVDR PX-708A/1.12 at ata1-master UDMA33 The install doesn't actually crash - I can still enable / disable Num Lock, Caps Lock, and Scroll Lock, and the Ctrl-Alt-Space shortcut works. It just never seems to continue (unless I actually have to wait for several minutes). This drive is the only CD/DVD drive, and, hence, the one which the boot CD is in. The drive works in both Windows and SUSE. Taking out the CD after the boot image has been loaded doesn't help. I've tried to boot in safe mode and with ACPI disabled, but I get the same result. Some other things noted during boot: $PIR: No matching entry for 0.1.INTA $PIR: No matching entry for 0.2.INTA $PIR: No matching entry for 0.2.INTB $PIR: No matching entry for 0.2.INTC $PIR: No matching entry for 0.4.INTA $PIR: No matching entry for 0.5.INTA $PIR: No matching entry for 0.6.INTA $PIR: No matching entry for 0.13.INTA [...] ♠ptable-probe: MPConfig Table has bad signature: [yes, the first character is a spade] [...] unknown: PNP0303 can't assign resources (port) unknown: PNP0c01 can't assign resources (memory) [...] Correcting nForce2 C1 CPU disconnect hangs [that would be my ASUS [...] pci0: memory,RAM at device 0.1 (no driver attached) pci0: memory,RAM at device 0.2 (no driver attached) pci0: memory,RAM at device 0.3 (no driver attached) pci0: memory,RAM at device 0.4 (no driver attached) pci0: memory,RAM at device 0.5 (no driver attached) More information from SUSE: # lspci 00:00.0 Host bridge: nVidia Corporation nForce2 AGP (different version?) (rev a2) 00:00.1 RAM memory: nVidia Corporation nForce2 Memory Controller 1 (rev a2) 00:00.2 RAM memory: nVidia Corporation nForce2 Memory Controller 4 (rev a2) 00:00.3 RAM memory: nVidia Corporation nForce2 Memory Controller 3 (rev a2) 00:00.4 RAM memory: nVidia Corporation nForce2 Memory Controller 2 (rev a2) 00:00.5 RAM memory: nVidia Corporation nForce2 Memory Controller 5 (rev a2) 00:01.0 ISA bridge: nVidia Corporation nForce2 ISA Bridge (rev a3) 00:01.1 SMBus: nVidia Corporation nForce2 SMBus (MCP) (rev a2) 00:02.0 USB Controller: nVidia Corporation nForce2 USB Controller (rev a3) 00:02.1 USB Controller: nVidia Corporation nForce2 USB Controller (rev a3) 00:02.2 USB Controller: nVidia Corporation nForce2 USB Controller (rev a3) 00:04.0 Ethernet controller: nVidia Corporation nForce2 Ethernet Controller (rev a1) 00:05.0 Multimedia audio controller: nVidia Corporation nForce Audio Processing Unit (rev a2) 00:06.0 Multimedia audio controller: nVidia Corporation nForce2 AC97 Audio Controler (MCP) (rev a1) 00:08.0 PCI bridge: nVidia Corporation nForce2 External PCI Bridge (rev a3) 00:09.0 IDE interface: nVidia Corporation nForce2 IDE (rev a2) 00:0d.0 FireWire (IEEE 1394): nVidia Corporation nForce2 FireWire (IEEE 1394) Controller (rev a3) 00:1e.0 PCI bridge: nVidia Corporation nForce2 AGP (rev a2) 01:07.0 Multimedia video controller: Brooktree Corporation Bt878 Video Capture (rev 11) 01:07.1 Multimedia controller: Brooktree Corporation Bt878 Audio Capture (rev 11) 02:00.0 VGA compatible controller: ATI Technologies Inc Radeon R300 NE [Radeon 9500 Pro] 02:00.1 Display controller: ATI Technologies Inc Radeon R300 [Radeon 9500 Pro] (Secondary) # lsusb Bus 002 Device 001: ID : Bus 001 Device 003: ID 046d:c041 Logitech, Inc. Bus 001 Device 001: ID : Bus 003 Device 003: ID 1058:0901 Western Digital Technologies, Inc. Bus 003 Device 004: ID 05ac:1260 Apple Computer, Inc. Bus 003 Device 001: ID : Does anyone have any tips for what might be wrong? Do you need more information? Some clarification: - I've used the DVD drive on Windows and Linux (in the same machine) for years, and it still works with those. - I was able to install FreeBSD 6.0-RELEASE or 6.1-RELEASE using the same drive. -- Victor Engmark Quidquid latine dictum sit, altum videtur - What is said in Latin, sounds profound ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Should sudo be used?
Hi all, I thought it would be a good idea to use sudo on my FreeBSD laptop, but I'm having doubts after checking the handbook (it's not mentioned at all) and Google (most of the articles were obscure and / or old). Are you using sudo? If not, why? -- Victor Engmark ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
What is the default firewall setup in 6.2?
Hi all, My goal is to set up a Subversion (v1.4, running on Apache 2.2 and available only through SSL) and SSH server, available to the world. I've managed to make it work locally; i.e., # svn list https://localhost/svn/repos/repository_namehttps://localhost/svn/repos/repos_name and # ssh [EMAIL PROTECTED] work fine. However, I'm having problems accessing these from other hosts. My machine is connected to the internet. I'm able to SSH to other machines, and use the web. Therefore, I believe the problem is that the machine is discarding packets. However, I can't find any record of the connection attempts in /var/log (grepping for the host name or IP of the other machine gives no results, and even ping doesn't work), and it seems that, according to the FreeBSD handbook chapter 26, there is no firewall installed by default. Why would FreeBSD be dropping packets, without recording it, when there are processes listening on the ports (see below), and no firewall? # netstat -an | grep 22 gives (among other lines): tcp4 0 0 *.22 *.* LISTEN According to tcpdump port 22 , the packets are arriving at my machine. /etc/rc.conf contains the following: hostname=[removed] ifconfig_bge0=dhcp keymap=us.dvorak linux_enable=YES sshd_enable=YES usbd_enable=YES apache2_enable=YES network_interfaces=bge0 I haven't changed anything in /etc/defaults/rc.conf. It contains firewall_enable=NO , which should be enough to avoid having any firewall. In addition, pf_enable=NO and ipfilter_enable=NO are in the defaults, so I'm completely stumped as to what is blocking the traffic. Is FreeBSD by default dropping any incoming connections (it should be, but I can't find mention of it in the firewall chapter)? Any help would be appreciated. -- Victor Engmark ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: What is the default firewall setup in 6.2?
On 4/4/07, Javier Henderson [EMAIL PROTECTED] wrote: Can SSH clients on your local network connect to your system? You say packets are arriving at your machine, can you elaborate on this further? Assuming a SYN packet arrives from a host, so you see a SYN+ACK go out, etc? Actually, it turns out I was wrong - The packets I saw in tcpdump were just the console updates from the server I was connected to, in order to connect back to myself :) Also, the local network uses VPN and NAT, which is why an ordinary connection doesn't work. That just leaves the mystery of why my setup worked on SUSE. I'll be using my home PC as the server instead - Much less hassle. Thanks anyway! -- Victor Engmark ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
FreeBSD 6.2-RELEASE install boot halts
Hi all, I've downloaded and burned the boot CD for the i386 6.2-RELEASE. I've used the CD to install a very well running system on my laptop, but it halts during boot when I try to install with the same CD on my desktop PC. The last line it outputs before halting is the following: acd0: DVDR PLEXTOR DVDR PX-708A/1.12 at ata1-master UDMA33 The install doesn't actually crash - I can still enable / disable Num Lock, Caps Lock, and Scroll Lock, and the Ctrl-Alt-Space shortcut works. It just never seems to continue (unless I actually have to wait for several minutes). This drive is the only CD/DVD drive, and, hence, the one which the boot CD is in. The drive works in both Windows and SUSE. Taking out the CD after the boot image has been loaded doesn't help. I've tried to boot in safe mode and with ACPI disabled, but I get the same result. Some other things noted during boot: $PIR: No matching entry for 0.1.INTA $PIR: No matching entry for 0.2.INTA $PIR: No matching entry for 0.2.INTB $PIR: No matching entry for 0.2.INTC $PIR: No matching entry for 0.4.INTA $PIR: No matching entry for 0.5.INTA $PIR: No matching entry for 0.6.INTA $PIR: No matching entry for 0.13.INTA [...] ♠ptable-probe: MPConfig Table has bad signature: [yes, the first character is a spade] [...] unknown: PNP0303 can't assign resources (port) unknown: PNP0c01 can't assign resources (memory) [...] Correcting nForce2 C1 CPU disconnect hangs [that would be my ASUS [...] pci0: memory,RAM at device 0.1 (no driver attached) pci0: memory,RAM at device 0.2 (no driver attached) pci0: memory,RAM at device 0.3 (no driver attached) pci0: memory,RAM at device 0.4 (no driver attached) pci0: memory,RAM at device 0.5 (no driver attached) More information from SUSE: # lspci 00:00.0 Host bridge: nVidia Corporation nForce2 AGP (different version?) (rev a2) 00:00.1 RAM memory: nVidia Corporation nForce2 Memory Controller 1 (rev a2) 00:00.2 RAM memory: nVidia Corporation nForce2 Memory Controller 4 (rev a2) 00:00.3 RAM memory: nVidia Corporation nForce2 Memory Controller 3 (rev a2) 00:00.4 RAM memory: nVidia Corporation nForce2 Memory Controller 2 (rev a2) 00:00.5 RAM memory: nVidia Corporation nForce2 Memory Controller 5 (rev a2) 00:01.0 ISA bridge: nVidia Corporation nForce2 ISA Bridge (rev a3) 00:01.1 SMBus: nVidia Corporation nForce2 SMBus (MCP) (rev a2) 00:02.0 USB Controller: nVidia Corporation nForce2 USB Controller (rev a3) 00:02.1 USB Controller: nVidia Corporation nForce2 USB Controller (rev a3) 00:02.2 USB Controller: nVidia Corporation nForce2 USB Controller (rev a3) 00:04.0 Ethernet controller: nVidia Corporation nForce2 Ethernet Controller (rev a1) 00:05.0 Multimedia audio controller: nVidia Corporation nForce Audio Processing Unit (rev a2) 00:06.0 Multimedia audio controller: nVidia Corporation nForce2 AC97 Audio Controler (MCP) (rev a1) 00:08.0 PCI bridge: nVidia Corporation nForce2 External PCI Bridge (rev a3) 00:09.0 IDE interface: nVidia Corporation nForce2 IDE (rev a2) 00:0d.0 FireWire (IEEE 1394): nVidia Corporation nForce2 FireWire (IEEE 1394) Controller (rev a3) 00:1e.0 PCI bridge: nVidia Corporation nForce2 AGP (rev a2) 01:07.0 Multimedia video controller: Brooktree Corporation Bt878 Video Capture (rev 11) 01:07.1 Multimedia controller: Brooktree Corporation Bt878 Audio Capture (rev 11) 02:00.0 VGA compatible controller: ATI Technologies Inc Radeon R300 NE [Radeon 9500 Pro] 02:00.1 Display controller: ATI Technologies Inc Radeon R300 [Radeon 9500 Pro] (Secondary) # lsusb Bus 002 Device 001: ID : Bus 001 Device 003: ID 046d:c041 Logitech, Inc. Bus 001 Device 001: ID : Bus 003 Device 003: ID 1058:0901 Western Digital Technologies, Inc. Bus 003 Device 004: ID 05ac:1260 Apple Computer, Inc. Bus 003 Device 001: ID : Does anyone have any tips for what might be wrong? Do you need more information? -- Victor Engmark Quidquid latine dictum sit, altum videtur - What is said in Latin, sounds profound ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
