Re: mod_auth_kerb2 broken in 8-STABLE? Or is it heimdal to blame?
On 19/10/2012 02:19 πμ, John Marshall wrote:
On 02/10/2012 02:08, George Mamalakis wrote:
On 04/07/11 14:08, George Mamalakis wrote:
On 06/04/2011 18:29, George Mamalakis wrote:
Dear all,
I installed mod_auth_kerb2 on my FreeBSD 8-STABLE machine and tried
to use it. After the installation (which was successful(?!?)), the
server refused to start giving the error:
# /usr/local/etc/rc.d/apache22 start
Performing sanity check on apache22 configuration:
httpd: Syntax error on line 103 of
/usr/local/etc/apache22/httpd.conf: Cannot load
/usr/local/libexec/apache22/mod_auth_kerb.so into server:
/usr/local/libexec/apache22/mod_auth_kerb.so: Undefined symbol
"gsskrb5_register_acceptor_identity"
Starting apache22.
httpd: Syntax error on line 103 of
/usr/local/etc/apache22/httpd.conf: Cannot load
/usr/local/libexec/apache22/mod_auth_kerb.so into server:
/usr/local/libexec/apache22/mod_auth_kerb.so: Undefined symbol
"gsskrb5_register_acceptor_identity"
/usr/local/etc/rc.d/apache22: WARNING: failed to start apache22
but ldd showed:
# ldd /usr/local/libexec/apache22/mod_auth_kerb.so
/usr/local/libexec/apache22/mod_auth_kerb.so:
libgssapi.so.10 => /usr/lib/libgssapi.so.10 (0x800c0)
libheimntlm.so.10 => /usr/lib/libheimntlm.so.10 (0x800d0a000)
libkrb5.so.10 => /usr/lib/libkrb5.so.10 (0x800e0f000)
libhx509.so.10 => /usr/lib/libhx509.so.10 (0x800f7e000)
libcom_err.so.5 => /usr/lib/libcom_err.so.5 (0x8010be000)
libcrypto.so.6 => /lib/libcrypto.so.6 (0x8011c)
libasn1.so.10 => /usr/lib/libasn1.so.10 (0x801461000)
libroken.so.10 => /usr/lib/libroken.so.10 (0x8015e3000)
libcrypt.so.5 => /lib/libcrypt.so.5 (0x8016f5000)
libc.so.7 => /lib/libc.so.7 (0x800647000)
which showed that everything should have been fine. I googled it a
bit and found this thread regarding my error message:
http://forum.nginx.org/read.php?23,88476 , which started on May 2010,
and pointed to this PR:
http://www.freebsd.org/cgi/query-pr.cgi?pr=147454 , which started on
June 2010. What is stated, is that heimdal-1.1 was broken in FreeBSD,
and that it should be fixed at some moment in the future. (I tested
mod_auth_kerb2 on another machine running heimdal from ports (1.4_1)
and I had exactly the same problem).
I searched to find where this notorious function
(gsskrb5_register_acceptor_identity) was located, and I found its
declaration in: /usr/include/gssapi/gssapi_krb5.h, and its definition
in: /usr/lib/libgssapi_krb5.so.
So, I added -lgssapi_krb5 in KRB5_LDFLAGS variable of
/usr/ports/www/mod_auth_kerb2/work/mod_auth_kerb-5.4/Makefile , since
this where the location of gsskrb5_register_acceptor_identity
originally seemed to be, and reinstalled the port using gmake this
time (inside the port's work directory). After that, the module works
just fine. The initial content of this line was:
KRB5_LDFLAGS = -L/usr/lib -lgssapi -lheimntlm -lkrb5 -lhx509
-lcom_err -lcrypto -lasn1 -lroken -lcrypt
I've sent an analogous email to the port maintainer, but I am not
sure if it is their "fault". Hence, I decided to send this email to
the stable list for two reasons: First, someone else may be having a
similar problem and wants to find a rough solution. Secondly, there
are people reading this list that know heimdal's code, so somebody
may know another (much more elegant) way to fix this bug.
Thank you all for your time in advance,
Regards,
mamalos.
OK,
I spoke with the maintainer who confirmed the problem. He also
suggested to change line 96 of /usb/bin/krb5-config to include
gssapi_krb5 among its libraries. He also gave me the relevant patch,
and asked me to send a PR to FreeBSD. The patch is as follows:
--- /usr/bin/krb5-config.orig 2011-02-17 03:18:57.0 +0100
+++ /usr/bin/krb5-config2011-04-06 23:41:31.0 +0200
@@ -93,7 +93,7 @@
lib_flags="-L${libdir}"
case $library in
gssapi)
- lib_flags="$lib_flags -lgssapi -lheimntlm"
+ lib_flags="$lib_flags -lgssapi -lgssapi_krb5 -lheimntlm"
;;
kadm-client)
lib_flags="$lib_flags -lkadm5clnt"
And the relevant PR is:
http://www.freebsd.org/cgi/query-pr.cgi?pr=156245
Thank you all for your time,
mamalos
Hi all,
I am bringing this matter back again because the same things hold for my
current system too (/usr/bin/krb5-config does not seem to link
gssapi-things properly):
# uname -a
FreeBSD example.com 9.0-STABLE FreeBSD 9.0-STABLE #0: Mon Jun 18
21:04:14 EEST 2012 r...@example.com:/usr/obj/usr/src/sys/FILESRV amd64
# pkg_info -Ix apache kerb
ap22-mod_auth_kerb-5.4_3 An Apache module for authenticating users with
Kerberos v5
apache22-2.2.22_8 Version 2.2.x of Apache web server with prefork MPM.
Should I send a PR or is there something that I've done wrong?
I've seen the same thing on 8.3-RELEASE, 9.1-RC1 and 9.1-RC2. In all
cases, applying your patch (thank you!) to /usr/bin/krb5-config resolved
the issue. I did not need to patch krb5-config for other GSSAPI servers
to wor
Re: Problem reading vitals from Gigabyte H77-DH3H
on 17/10/2012 23:51 Derek Kulinski said the following: > On Wed, Oct 17, 2012 at 11:38:57PM +0300, Andriy Gapon wrote: >> I've found that on quite a few modern systems the ACPI platform advertises >> some >> useless thermal zones, which always return some hardcoded temperatures. >> E.g. I have Asus P8Z77-M PRO near me and it also reports two thermal zones. >> Looking at DSDT (acpidump -dt) I see that the temperatures are hardcoded. >> >> It seems that your motherboard has an ITE Super I/O with hardware monitoring >> function. I am not sure which model though... >> Your best bet would be it(4) driver, but it is not committed yet. >> If you are into some mild hacking (applying patches, building custom kernel), >> then I can point you to the patches. >> Although I can not give a firm guarantee that the driver supports your HWM >> chip, >> since I don't know the model. > > I'm open to experimenting. It's kind of important to me, because I recently > had heating issue (that I hopefully fixed) and I wasn't aware of problems > until my system started freezing. I was fooled by those values thinking > everything was ok. Here is a (quite large) patch: http://people.freebsd.org/~avg/sensors.diff Please note that if affects both kernel and userland code. Read it(4) manual page after upgrading. Note that you will need to add some entries to /boot/device.hints (unless your upgrade procedure would automatically merge the file). >> [...] >> >> These tools from ports are very outdated and thus do not support new >> hardware. > > I never used them before since on my old box hw.acpi.thermal worked fine. > Is there anything in ports that you would recommend? No. I do not know of any good userland tool for recent hardware. -- Andriy Gapon ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
Re: Problem reading vitals from Gigabyte H77-DH3H
on 19/10/2012 16:27 Andriy Gapon said the following: > on 17/10/2012 23:51 Derek Kulinski said the following: [snip] >> I'm open to experimenting. It's kind of important to me, because I recently >> had heating issue (that I hopefully fixed) and I wasn't aware of problems >> until my system started freezing. I was fooled by those values thinking >> everything was ok. > > Here is a (quite large) patch: http://people.freebsd.org/~avg/sensors.diff Forgot to mention - the patch is against recent-ish head. > Please note that if affects both kernel and userland code. > Read it(4) manual page after upgrading. Note that you will need to add some > entries to /boot/device.hints (unless your upgrade procedure would > automatically > merge the file). -- Andriy Gapon ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
Re: FreeBSD 9.1-RC2 Available...
on 19/10/2012 00:07 Alex de Joode said the following: > Updated two 9.1-RC1 machines (both R210, dual GEOM MIRRORED disk) > > > 1 went OK; > 1 went belly up (see attachment) (after the 1st reboot) There is no spoon^Wattachment. Consider sending a link. > - Invalid format > > - BTX halted. > > > Any ideas why ? (need to upgrade more machines without KVM access ) -- Andriy Gapon ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
RE: FreeBSD 9.1-RC2 Available...
https://sabotage.org/FBSD/FBSD-9.1RC2.jpg Screen shot. Basicly the only diff between the two r210 are the disks, one has 2x2TB (works) and the one that has 2x1Tb fails with the above error. Both are sw/ mirrored. No hw/ raid and ACHI sata settings. : -Original Message- : From: Andriy Gapon [mailto:a...@freebsd.org] : Sent: Friday, October 19, 2012 3:30 PM : To: Alex de Joode : Cc: freebsd-stable@freebsd.org : Subject: Re: FreeBSD 9.1-RC2 Available... : : on 19/10/2012 00:07 Alex de Joode said the following: : > Updated two 9.1-RC1 machines (both R210, dual GEOM MIRRORED disk) : > : > : > 1 went OK; : > 1 went belly up (see attachment) (after the 1st reboot) : : There is no spoon^Wattachment. : Consider sending a link. : : > - Invalid format : > : > - BTX halted. : > : > : > Any ideas why ? (need to upgrade more machines without KVM access ) : : : -- : Andriy Gapon ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
Re: 9.1-RC2 - could it be that the installer does not write the MBR?
Guys/girls/etc, I do suggest that someone actually spends some time coming up with a table of "what the current state is", "what we could do", "what would happen if we did that." Right now there's a lot of possibilities (new drive, drive with windows, drive with linux, drive with linux/windows, drive with legacy freebsd MBR, etc) and as an outsider trying to figure out what is actually the "right" sounding behaviour, it's difficult for me to sit down and digest all these emails that chip away at a bit of the problem at a time. So if you'd like to see this fixed, I really do suggest that one of you dumps some time into coming up with a basic table like I said above, work with others who can correct/flesh out the various options to take into account, and then we can come up with a real solution. Then 9.1 can go out the door. Adrian ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
Re: 9.1-RC2 - could it be that the installer does not write the MBR?
On 10/19/2012 1:32 PM, Adrian Chadd wrote: Guys/girls/etc, I do suggest that someone actually spends some time coming up with a table of "what the current state is", "what we could do", "what would happen if we did that." Right now there's a lot of possibilities (new drive, drive with windows, drive with linux, drive with linux/windows, drive with legacy freebsd MBR, etc) and as an outsider trying to figure out what is actually the "right" sounding behaviour, it's difficult for me to sit down and digest all these emails that chip away at a bit of the problem at a time. So if you'd like to see this fixed, I really do suggest that one of you dumps some time into coming up with a basic table like I said above, work with others who can correct/flesh out the various options to take into account, and then we can come up with a real solution. Then 9.1 can go out the door. Adrian In my opinion, I think that the installer should be able to determine whether or not there is an existing partition table, either MBR or GPT, and at that point, ask the user about replacing MBR. But if there is no existing partition map on the drive, then there is no need for prompting about MBR over-writing. Basically: detect if map exists, if not, proceed as usual, if part-table/map is detected, prompt user "Existing partitions detected, Should we replace any existing MBR boot code? Only advanced users who know what they're doing should say "No" here, as this could leave you with an unbootable system: Yes/No (Recommended: Yes)" -- Chuck Burns ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
Re: 9.1-RC2 - could it be that the installer does not write the MBR?
Am Fri, 19 Oct 2012 11:32:49 -0700 schrieb Adrian Chadd : > Guys/girls/etc, > > I do suggest that someone actually spends some time coming up with a > table of "what the current state is", "what we could do", "what would > happen if we did that." > > Right now there's a lot of possibilities (new drive, drive with > windows, drive with linux, drive with linux/windows, drive with legacy > freebsd MBR, etc) and as an outsider trying to figure out what is > actually the "right" sounding behaviour, it's difficult for me to sit > down and digest all these emails that chip away at a bit of the > problem at a time. > > So if you'd like to see this fixed, I really do suggest that one of > you dumps some time into coming up with a basic table like I said > above, work with others who can correct/flesh out the various options > to take into account, and then we can come up with a real solution. > Then 9.1 can go out the door. > If I select the "entire disk" for FreeBSD, I think it's a reasonable assumption that the MBR should replaced, too. Please don't make people install FreeBSD 9.0 first on disks with non-FreeBSD MRRs and then upgrade to 9.1. ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
Re: 9.1-RC2 - could it be that the installer does not write the MBR?
On Fri, Oct 19, 2012 at 10:38:41PM +0200, Rainer Duffner wrote: > Am Fri, 19 Oct 2012 11:32:49 -0700 > schrieb Adrian Chadd : > > > Guys/girls/etc, > > > > I do suggest that someone actually spends some time coming up with a > > table of "what the current state is", "what we could do", "what would > > happen if we did that." > > > > Right now there's a lot of possibilities (new drive, drive with > > windows, drive with linux, drive with linux/windows, drive with legacy > > freebsd MBR, etc) and as an outsider trying to figure out what is > > actually the "right" sounding behaviour, it's difficult for me to sit > > down and digest all these emails that chip away at a bit of the > > problem at a time. > > > > So if you'd like to see this fixed, I really do suggest that one of > > you dumps some time into coming up with a basic table like I said > > above, work with others who can correct/flesh out the various options > > to take into account, and then we can come up with a real solution. > > Then 9.1 can go out the door. > > > > > If I select the "entire disk" for FreeBSD, I think it's a reasonable > assumption that the MBR should replaced, too. > Please don't make people install FreeBSD 9.0 first on disks with > non-FreeBSD MRRs and then upgrade to 9.1. > Can you outline for me in detail what you did when you partitioned your drive during the installation? I have seen your specific issue exactly once, and reliably reproducing the problem has not been successful so far. BTW, what was on the drive before you did the install, if anything? Glen pgpgqmYglawAJ.pgp Description: PGP signature
Re: FreeBSD 9.1-RC2 Available...
On Friday, October 19, 2012 2:26:45 pm Alex de Joode wrote: > https://sabotage.org/FBSD/FBSD-9.1RC2.jpg > > Screen shot. Basicly the only diff between the two r210 are the disks, > one has 2x2TB (works) and the one that has 2x1Tb fails with the above error. > > Both are sw/ mirrored. No hw/ raid and ACHI sata settings. Hummm, somehow we are executing data, not code: 8c 39 00 00 01 82 44 45 4c 4c 20 20 50 45 5f 53 |.9DELL PE_S| That isn't a valid instruction. :( Also, your eip value is not anything that would be normal. Actually, your eip value looks like a pointer into the BIOS (0xf000:bf6a). I bet something in your BIOS had a buffer overrun and trashed the stack or some such. Or it overran an I/O buffer which trashed the return stack of the userland process somehow. -- John Baldwin ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
Re: 9.1-RC2 - could it be that the installer does not write the MBR?
On Fri, Oct 19, 2012 at 10:38:41PM +0200, Rainer Duffner wrote: > Am Fri, 19 Oct 2012 11:32:49 -0700 > schrieb Adrian Chadd : > > > Guys/girls/etc, > > > > I do suggest that someone actually spends some time coming up with a > > table of "what the current state is", "what we could do", "what would > > happen if we did that." > > > > Right now there's a lot of possibilities (new drive, drive with > > windows, drive with linux, drive with linux/windows, drive with legacy > > freebsd MBR, etc) and as an outsider trying to figure out what is > > actually the "right" sounding behaviour, it's difficult for me to sit > > down and digest all these emails that chip away at a bit of the > > problem at a time. > > > > So if you'd like to see this fixed, I really do suggest that one of > > you dumps some time into coming up with a basic table like I said > > above, work with others who can correct/flesh out the various options > > to take into account, and then we can come up with a real solution. > > Then 9.1 can go out the door. > > > > > If I select the "entire disk" for FreeBSD, I think it's a reasonable > assumption that the MBR should replaced, too. I think it should still prompt clearly for permission to splat the boot record. There could be an OS (or multiple OSs) on other disks which the boot loader can reference. Just because you have complete ownership of *one* disk is not indicative of being able to take over the entire boot record. There are probably too many edge cases here to make a reliable automated decision, hence the necessity of a question. > Please don't make people install FreeBSD 9.0 first on disks with > non-FreeBSD MRRs and then upgrade to 9.1. Gary ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
Re: 9.1-RC2 - could it be that the installer does not write the MBR?
Am Fri, 19 Oct 2012 17:11:30 -0400 schrieb Glen Barber : > On Fri, Oct 19, 2012 at 10:38:41PM +0200, Rainer Duffner wrote: > > If I select the "entire disk" for FreeBSD, I think it's a reasonable > > assumption that the MBR should replaced, too. > > Please don't make people install FreeBSD 9.0 first on disks with > > non-FreeBSD MRRs and then upgrade to 9.1. > > > > Can you outline for me in detail what you did when you partitioned > your drive during the installation? I chose "entire disk", then deleted all partitions-suggestions except the first one and created my own partitioning scheme. (/, swap, var, usr, maybe /var/log and /home, too) > I have seen your specific issue exactly once, and reliably reproducing > the problem has not been successful so far. > > BTW, what was on the drive before you did the install, if anything? It had a version of Solaris. Maybe Opensolaris. I don't know exactly. And I don't know if it had zfsroot or not. I created a HW-RAID1 with the HP P400 controller on it. The drives were previously used in another server. I tried to install 9.1RC2 twice on these disks and it always went back to the grub-prompt after reboot. Then I installed 9.0 and it's running now. ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
Re: 9.1-RC2 - could it be that the installer does not write the MBR?
On Sat, Oct 20, 2012 at 02:06:03AM +0200, Rainer Duffner wrote: > Am Fri, 19 Oct 2012 17:11:30 -0400 > schrieb Glen Barber : > > > On Fri, Oct 19, 2012 at 10:38:41PM +0200, Rainer Duffner wrote: > > > If I select the "entire disk" for FreeBSD, I think it's a reasonable > > > assumption that the MBR should replaced, too. > > > Please don't make people install FreeBSD 9.0 first on disks with > > > non-FreeBSD MRRs and then upgrade to 9.1. > > > > > > > Can you outline for me in detail what you did when you partitioned > > your drive during the installation? > > I chose "entire disk", then deleted all partitions-suggestions except > the first one and created my own partitioning scheme. > (/, swap, var, usr, maybe /var/log and /home, too) > Ok, this is similar to my case. > > I have seen your specific issue exactly once, and reliably reproducing > > the problem has not been successful so far. > > > > BTW, what was on the drive before you did the install, if anything? > > It had a version of Solaris. Maybe Opensolaris. I don't know exactly. > And I don't know if it had zfsroot or not. I created a HW-RAID1 with > the HP P400 controller on it. > The drives were previously used in another server. > Ok, as long as they were not new drives. Thank you. > I tried to install 9.1RC2 twice on these disks and it always went back > to the grub-prompt after reboot. > Then I installed 9.0 and it's running now. > The grub prompt for (Open)Solaris? Or do you use grub on FreeBSD? I _think_ at this point, you've hit the same problem I hit, the only difference is that in my case, 9.1-PRERELEASE was installed twice, because the paritions were not ideal. So, my guess is if you were to boot the install cd and select 'Live CD' or 'Shell' from the first menu option, and wrote the GPT bootcode to da0p1 (assuming da0 is the drive) and reboot, it would have booted fine. In my case, the disk originally had an older FreeBSD install, so had an existing MBR. The odd thing though is that the system was bootable before the second installation. Glen pgpHsNFOoxOFQ.pgp Description: PGP signature
${CTFCONVERT_CMD} expands to empty string
On recent -stable I got a lots of (see subj) now due to CTF changes in *.mk files. I have WITHOUT_CDDL=yes in my /etc/src.conf and WITHOUT_CDDL have wider scope than WITHOUT_CTF suggested, but WITHOUT_CDDL is not checked in recent CTF changes. Please fix this thing. ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
Re: ${CTFCONVERT_CMD} expands to empty string
On 20.10.2012 5:06, Andrey Chernov wrote:
> On recent -stable I got a lots of (see subj) now due to CTF changes in
> *.mk files.
> I have
> WITHOUT_CDDL=yes
> in my /etc/src.conf and WITHOUT_CDDL have wider scope than WITHOUT_CTF
> suggested, but WITHOUT_CDDL is not checked in recent CTF changes.
> Please fix this thing.
>
BTW, I got that
${CTFCONVERT_CMD} expands to empty string
even placing
WITHOUT_CTF=yes
into /etc/src.conf
___
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
Re: Problem reading vitals from Gigabyte H77-DH3H
Hello Andriy, Friday, October 19, 2012, 6:27:11 AM, you wrote: > Here is a (quite large) patch: > http://people.freebsd.org/~avg/sensors.diff > Please note that if affects both kernel and userland code. > Read it(4) manual page after upgrading. Note that you will need to add some > entries to /boot/device.hints (unless your upgrade procedure would > automatically > merge the file). I applied it to RELENG_9 as of today, recompiled the userland and kernel (I did not see any errors). The it device loaded successfully, unfortunately I don't see any effect; the hw.acpi.thermal does not change (though I guess it not supposed to), sysctl hw.sensors and hw._sensors do not return anything (not even a complaint that it does not exist). sensord returns: sensorsd: no sensors found -- Best regards, Derekmailto:tak...@takeda.tk "unzip; strip; touch; finger; mount; fsck; more; yes; unmount; sleep" - my daily unix command list ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
9.1 and intel graphics
Yesterday I have gotten lenovo e320 laptop, with core i3 2350 and HD3000 integrated. Gonna wait few days till 9.1 release. I never used anything aside "intel" on my old laptop. Kostik Belousov made a port of kms and I found patches from june and jule on the net. What should I do after 9.1 install in this case? I assume kms is in xorg. Do I have to find and install some driver from intel? Do I need to change xorg.conf after configure flag, that will make conf file? Finally, what happens when I leave x and want to go back to console mode? I tried out live RC2 from usb stick. Few acpi errors, intel 1000 wifi found. After some time "sysctl hw.acpi" gave me the cpu temperature of 50C. Fan was on. Probably temp gonna go down when I add powerd and cx_lowest to rc.conf on hdd. Is it normal temp for this cpu? Best regards all Zoran ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
Re: 9.1-RC2 - could it be that the installer does not write the MBR?
On Sat, 20 Oct 2012, Rainer Duffner wrote: Am Fri, 19 Oct 2012 17:11:30 -0400 schrieb Glen Barber : On Fri, Oct 19, 2012 at 10:38:41PM +0200, Rainer Duffner wrote: If I select the "entire disk" for FreeBSD, I think it's a reasonable assumption that the MBR should replaced, too. Please don't make people install FreeBSD 9.0 first on disks with non-FreeBSD MRRs and then upgrade to 9.1. Can you outline for me in detail what you did when you partitioned your drive during the installation? I chose "entire disk", then deleted all partitions-suggestions except the first one and created my own partitioning scheme. (/, swap, var, usr, maybe /var/log and /home, too) I have seen your specific issue exactly once, and reliably reproducing the problem has not been successful so far. BTW, what was on the drive before you did the install, if anything? It had a version of Solaris. Maybe Opensolaris. I don't know exactly. And I don't know if it had zfsroot or not. I created a HW-RAID1 with the HP P400 controller on it. The drives were previously used in another server. I tried to install 9.1RC2 twice on these disks and it always went back to the grub-prompt after reboot. Then I installed 9.0 and it's running now. I don't know if this is the problem, but it is worth pointing out that graid(8) is now included in GENERIC. Leftover hardware RAID metadata could make for unexpected results. For example, http://forums.freebsd.org/showthread.php?t=35168 ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
Re: 9.1 and intel graphics
On Sat, Oct 20, 2012 at 06:14:08AM +0200, Zoran Kolic wrote: > Yesterday I have gotten lenovo e320 laptop, with core i3 2350 > and HD3000 integrated. Gonna wait few days till 9.1 release. > I never used anything aside "intel" on my old laptop. Kostik > Belousov made a port of kms and I found patches from june and > jule on the net. What should I do after 9.1 install in this > case? I assume kms is in xorg. Do I have to find and install > some driver from intel? Do I need to change xorg.conf after > configure flag, that will make conf file? The i915kms driver is in the 9-STABLE branch, I am not 100% certain if it is what will be 9.1-RELEASE. > Finally, what happens when I leave x and want to go back to > console mode? Currently, you cannot go back to console once i915kms is loaded. > I tried out live RC2 from usb stick. Few acpi errors, intel > 1000 wifi found. After some time "sysctl hw.acpi" gave me the > cpu temperature of 50C. Fan was on. Probably temp gonna go > down when I add powerd and cx_lowest to rc.conf on hdd. Is > it normal temp for this cpu? Yes. Glen pgpT4jLjdJF4M.pgp Description: PGP signature
Re: 9.1 and intel graphics
On Fri, Oct 19, 2012 at 9:14 PM, Zoran Kolic wrote: > Yesterday I have gotten lenovo e320 laptop, with core i3 2350 > and HD3000 integrated. Gonna wait few days till 9.1 release. > I never used anything aside "intel" on my old laptop. Kostik > Belousov made a port of kms and I found patches from june and > jule on the net. What should I do after 9.1 install in this > case? I assume kms is in xorg. Do I have to find and install > some driver from intel? Do I need to change xorg.conf after > configure flag, that will make conf file? Full support for the HD3000 is in 9-stable and 9.1-Beta and all RCs. To use it you need to build X drivers and drm and the kernel with: WITH_NEW_XORG=YES WITH_KMS=YES in /etc/make.conf. Specifically, the kernel and a few ports. graphics/drm and your org-drivers: xf86-video-intel, xf86-input-synaptics, xf86-input-mouse, and xf86-input-keyboard. Then just start X. Don't try loading the kernel module. It will be loaded by the startx. > Finally, what happens when I leave x and want to go back to > console mode? You don't If you try, your system will lock up. You need to shutdown from a window in X. Hopefully someone will implement switching back to console mode some day, but it has not happened, yet. > I tried out live RC2 from usb stick. Few acpi errors, intel > 1000 wifi found. After some time "sysctl hw.acpi" gave me the > cpu temperature of 50C. Fan was on. Probably temp gonna go > down when I add powerd and cx_lowest to rc.conf on hdd. Is > it normal temp for this cpu? Pretty reasonable. Be sure to set both cx_lowest to "Cmax". It is new to 9.1 and fixes some serious issues with C-states on many newer platforms. Specifically that some platforms skip some C-states and FreeBSD never used the ones saving more power than hte one skipped. I always remind folks to blow out the heat sink on laptops about one a year. Dust is a great insulator and laptops often collect a lot more dust than office systems, though my office system started dying during buildworld last week and blowing out the CPU heat sink fixed it up, but it had been sitting around for almost three years collecting dust. -- R. Kevin Oberman, Network Engineer E-mail: kob6...@gmail.com ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
Re: 9.1 and intel graphics
Hi, On Fri, 19 Oct 2012 23:29:28 -0700 Kevin Oberman wrote: > On Fri, Oct 19, 2012 at 9:14 PM, Zoran Kolic wrote: > > I always remind folks to blow out the heat sink on laptops about one a > year. Dust is a great insulator and laptops often collect a lot more I never did this on a laptop as all of mine where build in a way that dust could not collect. So, it depends very much on the model. > dust than office systems, though my office system started dying during > buildworld last week and blowing out the CPU heat sink fixed it up, > but it had been sitting around for almost three years collecting dust. I do this every year on my desktop. The temperature drops then by 10K. You can use the CPU temperature as an indicator when a cleaning is needed. But blowing does not work on my machine. I really have to take screw driver and tweezers to get the work finally done. Erich ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
