Re: FreeBSD 7.2-RC1 Available
On Sat, 2009-04-18 at 00:40 +0100, Pete French wrote: - bce(4) updated (there is a report that lagg(4) does not work after the update, fixing that may need to be done as an Errata Notice after the release) [ this is http://www.freebsd.org/cgi/query-pr.cgi?pr=kern/133756 ] I just tested again with a csup of RELENG_7_2 and this still has the lagg problem. I know it most likely won't be fixed before release, so we do need a big warning in the release notes to tell people with this setup not to update, as it will just kill all network connectivity. -pete. We will, and if we do wind up shipping 7.2-REL with lagg(4) broken (there is still time for a fix if we find it fast enough so that's not definite yet...) apologies in advance. At least as things stand now it seems like the current driver is noticably better than the previous one in most regards so deciding whether to ship with this breakage versus reverting to the older driver isn't a particularly easy decision. -- Ken Smith - From there to here, from here to | kensm...@cse.buffalo.edu there, funny things are everywhere. | - Theodore Geisel | signature.asc Description: This is a digitally signed message part
Re: 6.x acpi powerbutton
Nate Lawson wrote: Ian Smith wrote: On Fri, 10 Apr 2009, Nate Lawson wrote: Andriy Gapon wrote: on 09/04/2009 23:24 Stephen Clark said the following: Is there a reason it doesn't send and event like Linux that can be acted upon by user space other than signaling init? I like to have a message written in /var/log/messages that someone pressed the powerbutton. I think that for all suspend states except S5 userland is notified via devd mechanism and potentially can veto the suspend. S5 (soft-off) is coded to start shutdown immediately. You can try to hack on acpi_ReqSleepState in sys/dev/acpica/acpi.c. I am not sure what is the reason for this special behavior of S5. But I like it, because it sometimes allows me to perform semi-clean shutdown when X goes crazy. But I also see when it could be useful to have S5 request go through userland. So this could be configurable. The reason for userland getting into the loop in the first place was to run programs to shut down devices and reinit them after resume. This isn't necessary in the shutdown case because init already sends a signal, as you mention. There's already a mechanism for timing out if userland is not responding, so a suspend will ultimately happen whether or not it answers. However, that waits for a while (1 minute?) and devd used to be optional, so I thought it best to keep the existing S5 behavior (immediate shutdown). It may be ok to enable this for S5 but I don't think it's very useful. Perhaps a silly question, but is it too late at this stage of the game to try logging S5 events to syslog before dying? I agree with Stephen, logging 'shutdown by powerbutton' surely beats what might otherwise resemble a spontaneous reboot? Or is something already logged here? I'm not resisting this, but I'm having trouble seeing the importance. What happens differently than if someone hits CTRL-ALT-DEL on a virtual console? Hi Nate, We have over 500 units in the field that are used as firewall/vpn/routers. They have no console, but they do have a powerbutton. We have had customers say the machine turned itself off. It would be nice to know that someone pressed the power button. Thanks, Steve -- They that give up essential liberty to obtain temporary safety, deserve neither liberty nor safety. (Ben Franklin) The course of history shows that as a government grows, liberty decreases. (Thomas Jefferson) ___ 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: 6.x acpi powerbutton
On Fri, 17 Apr 2009, Chuck Swiger wrote: On Apr 17, 2009, at 12:27 PM, Nate Lawson wrote: Perhaps a silly question, but is it too late at this stage of the game to try logging S5 events to syslog before dying? I agree with Stephen, logging 'shutdown by powerbutton' surely beats what might otherwise resemble a spontaneous reboot? Or is something already logged here? I'm not resisting this, but I'm having trouble seeing the importance. What happens differently than if someone hits CTRL-ALT-DEL on a virtual console? Well, I'd like to get a one-line message saying rebooted by CTRL-ALT-DEL versus shutdown by powerbutton. Other systems would log a one-liner like system rebooted by /etc/shutdown -i 6: _MESSAGE_ I don't know about C-A-D as I've always disabled it in my kernels - lest some 'windows expert' may be hoping to see a TaskList - but 'reboot' and 'shutdown -[rhp] ..' are already logged nicely: May 31 16:25:26 paqi reboot: rebooted by root May 31 16:25:26 paqi syslogd: exiting on signal 15 May 31 16:26:30 paqi syslogd: kernel boot file is /boot/kernel/kernel Mar 31 20:04:14 paqi shutdown: power-down by smithi: down after fixing localtime Sydney Mar 31 19:04:32 paqi named[16442]: stopping command channel on 127.0.0.1#953 Mar 31 19:04:33 paqi named[16442]: exiting Mar 31 19:04:33 paqi syslogd: exiting on signal 15 Mar 31 19:07:16 paqi syslogd: kernel boot file is /boot/kernel/kernel I suspect a 'windows expert' would have to break down doors to get to Nate's boxes, but for those of us condemned to being remote catherders, a powerbutton shutdown message would be helpful. cheers, Ian ___ 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
Update ... CD install 7.2RC1
dell 2350 bluford mobo p4 non-htt ich4 award acpi bios pri master = 9GB of zeros pri slave = empty sec master = gcr-8481b sec slave = sh-s182d All firmwares are current. I'm able to boot 7.1R disc1 from sec master. I load 7.1R fixit livefs in the opposing drive, remove the 7.1R boot disc1 and insert 7.2RC-1 disc1. Then do dd | sha256 from fixit on the 7.2RC-1 disc1. Hashes match. I'm able to boot 7.1R disc1 from sec slave. I load 7.1R fixit livefs in the opposing drive, remove the 7.1R boot disc1 and insert 7.2RC-1 disc1. Then do dd | sha256 from fixit on the 7.2RC-1 disc1. Hashes match. So my drives boot 7.1R disc1 and read the raw iso's fine and something's up with 7.2RC-1 disc1 booting on this hardware. Unfortunately I get NO output on the console when booting this disc1 so I'm at a loss. The drive lights up, after the drive's insert disc tasting sequence is complete and the disc is still spun up, so the system does read and try to boot something off the drive for sure. Then it silently passes to the bios/onboard netboot. The discs were written on the above writer. So I'm stuck... with cdrecord, installing 7.1R, copying in 7.2RC-1's loader and building RELENG_7. No big deal right :) If I have time, I'll do a RELENG_7 make relase and see what that disc1 does for me. ___ 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 7.2-RC1 Available
We will, and if we do wind up shipping 7.2-REL with lagg(4) broken (there is still time for a fix if we find it fast enough so that's not definite yet...) apologies in advance. At least as things stand now it Well, kind of my fault too for not getting aroiund to testing the driver for two weeks - I was out of the country so didn't get a chance. seems like the current driver is noticably better than the previous one in most regards so deciding whether to ship with this breakage versus reverting to the older driver isn't a particularly easy decision. Yes, I can see that, and a better bce driver is very much a Good Thing. I have another identical box running 7.2-PRE without lagg and that works beautifuly. What surprises me is that nobody else has made any reports either way - neither a me too on the issure, nor a it works ok here. Surely I cant be the only one using HP servers + Cisco switches and needing redundancy on the links ? Anyone else out there care to chip in ? Let me know if/wher there are things to test though - after the 7.1 relese routing problems I have now allocated a box for testing this kind of stuff, so it's fairly easy to do - I will be away from thursday for another a week though unfortunately which will make that hard :-( Sorry... -pete. ___ 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 7.2-RC1 Available
- bce(4) updated (there is a report that lagg(4) does not work after the update, fixing that may need to be done as an Errata Notice after the release) [ this is http://www.freebsd.org/cgi/query-pr.cgi?pr=kern/133756 ] I just tested again with a csup of RELENG_7_2 and this still has the lagg problem. I know it most likely won't be fixed before release, so we do need a big warning in the release notes to tell people with this setup not to update, as it will just kill all network connectivity. -pete. ___ 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: poweredge 1850 won't boot 7.1? maybe LSI-related : amr0: adapter is busy
I did some additional testing: 1) Installed 7.2-RC2 directly on the Perc 4e/Si H435 machine (RAID1) from a cd, this went fine. 2) Turned off, and placed one drive in the machine with Perc 4e/Si H430, boot went fine Checked install of 7.1-RELEASE from cd on the 4e/Si H435 machine, failed: no harddisk found. Checked install of 7.1-RELEASE from cd on the 4e/Si H430 machine, fine harddisk found. Jeroen Jeroen Hofstee schreef: I did the following to verify: 1) Installed 7.2-RC2 on the Perc 4e/Si H430 machine (RAID1), this went fine. 2) Turned off, and placed one drive in the machine with Perc 4e/Si H435, boot went fine and no long delays after amr0 So the problem as I encountered with 7.1-RELEASE-p4 is not present in 7.2-RC2. There are some messages about GEOM_LABEL and GEOM_LABEL: Label removed, which I haven't seen before. If they are of any interest let me know. Regards, Jeroen p.s. I copied the subject from the original thread. I haven't attempt to install 7.1-RELEASE myself. If it is of any additional value, I can try to install the 7.1- RELEASE directly to verify if it fails. Scott Long wrote: The just-released 7.2-RC2 should fix this problem. Please let me know ASAP if it works for you. Scott Interestingly enough, FreeBSD booted fine on the machine installed (updated from 7.0 to 7.1-RELEASE-p4). This machine is a PowerEdge 1850 bios A04 with Perc 4*e*/Si bios H430 / fwVer 521S. When booting a drive from this machine in another PowerEdge 1850, bios A07 Perc 4e/Si bios H435 FwVer 5B2D it drops to the mount root prompt... ___ 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 ___ 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: problems with 7.2, vm_page_insert: page already inserted
Dimitry Andric escribió: As a side note, isc-dhcp30-server port doesn't like the new jail stuff Please see http://www.freebsd.org/cgi/query-pr.cgi?pr=131515 for a possible fix. Your patch builds cleanly and looks good (against today's sources), at least not using jails at all :). Let me see about jailed dhcp, even compiling support for it I've never tried before XD. Regards, Raul ___ 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
page fault in sis.ko / drm.ko
Could a drm guru please have a look at kern/133554? Thanks, -cpghost. -- Cordula's Web. http://www.cordula.ws/ ___ 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: page fault in sis.ko / drm.ko
On Sat, 2009-04-18 at 19:13 +0200, cpghost wrote:
Could a drm guru please have a look at kern/133554?
Thanks,
-cpghost.
Give this patch a try, it looks like the sis driver doesn't have irq's.
robert.
--
Robert Noland rnol...@freebsd.org
FreeBSD
Index: dev/drm/drm_drv.c
===
--- dev/drm/drm_drv.c (revision 190987)
+++ dev/drm/drm_drv.c (working copy)
@@ -134,7 +134,7 @@
.d_flags = D_TRACKCLOSE
};
-int drm_msi = 1; /* Enable by default. */
+static int drm_msi = 1; /* Enable by default. */
TUNABLE_INT(hw.drm.msi, drm_msi);
static struct drm_msi_blacklist_entry drm_msi_blacklist[] = {
@@ -228,28 +228,31 @@
dev-pci_vendor = pci_get_vendor(dev-device);
dev-pci_device = pci_get_device(dev-device);
- if (drm_msi
- !drm_msi_is_blacklisted(dev-pci_vendor, dev-pci_device)) {
- msicount = pci_msi_count(dev-device);
- DRM_DEBUG(MSI count = %d\n, msicount);
- if (msicount 1)
- msicount = 1;
+ if (drm_core_check_feature(dev, DRIVER_HAVE_IRQ)) {
+ if (drm_msi
+ !drm_msi_is_blacklisted(dev-pci_vendor, dev-pci_device)) {
+ msicount = pci_msi_count(dev-device);
+ DRM_DEBUG(MSI count = %d\n, msicount);
+ if (msicount 1)
+msicount = 1;
- if (pci_alloc_msi(dev-device, msicount) == 0) {
- DRM_INFO(MSI enabled %d message(s)\n, msicount);
- dev-msi_enabled = 1;
- dev-irqrid = 1;
+ if (pci_alloc_msi(dev-device, msicount) == 0) {
+DRM_INFO(MSI enabled %d message(s)\n,
+msicount);
+dev-msi_enabled = 1;
+dev-irqrid = 1;
+ }
}
- }
- dev-irqr = bus_alloc_resource_any(dev-device, SYS_RES_IRQ,
- dev-irqrid, RF_SHAREABLE);
- if (!dev-irqr) {
- return ENOENT;
+ dev-irqr = bus_alloc_resource_any(dev-device, SYS_RES_IRQ,
+ dev-irqrid, RF_SHAREABLE);
+ if (!dev-irqr) {
+ return ENOENT;
+ }
+
+ dev-irq = (int) rman_get_start(dev-irqr);
}
- dev-irq = (int) rman_get_start(dev-irqr);
-
mtx_init(dev-dev_lock, drmdev, NULL, MTX_DEF);
mtx_init(dev-irq_lock, drmirq, NULL, MTX_DEF);
mtx_init(dev-vbl_lock, drmvbl, NULL, MTX_DEF);
signature.asc
Description: This is a digitally signed message part
Re: page fault in sis.ko / drm.ko
On Sat, Apr 18, 2009 at 01:58:39PM -0500, Robert Noland wrote:
On Sat, 2009-04-18 at 19:13 +0200, cpghost wrote:
Could a drm guru please have a look at kern/133554?
Thanks,
-cpghost.
Give this patch a try, it looks like the sis driver doesn't have irq's.
Ah, thank you. I'll try this tomorrow as soon as I'm in front of
this box again, and will report back.
Kind regards,
-cpghost.
robert.
--
Robert Noland rnol...@freebsd.org
FreeBSD
Index: dev/drm/drm_drv.c
===
--- dev/drm/drm_drv.c (revision 190987)
+++ dev/drm/drm_drv.c (working copy)
@@ -134,7 +134,7 @@
.d_flags = D_TRACKCLOSE
};
-int drm_msi = 1; /* Enable by default. */
+static int drm_msi = 1; /* Enable by default. */
TUNABLE_INT(hw.drm.msi, drm_msi);
static struct drm_msi_blacklist_entry drm_msi_blacklist[] = {
@@ -228,28 +228,31 @@
dev-pci_vendor = pci_get_vendor(dev-device);
dev-pci_device = pci_get_device(dev-device);
- if (drm_msi
- !drm_msi_is_blacklisted(dev-pci_vendor, dev-pci_device)) {
- msicount = pci_msi_count(dev-device);
- DRM_DEBUG(MSI count = %d\n, msicount);
- if (msicount 1)
- msicount = 1;
+ if (drm_core_check_feature(dev, DRIVER_HAVE_IRQ)) {
+ if (drm_msi
+ !drm_msi_is_blacklisted(dev-pci_vendor, dev-pci_device)) {
+ msicount = pci_msi_count(dev-device);
+ DRM_DEBUG(MSI count = %d\n, msicount);
+ if (msicount 1)
+ msicount = 1;
- if (pci_alloc_msi(dev-device, msicount) == 0) {
- DRM_INFO(MSI enabled %d message(s)\n, msicount);
- dev-msi_enabled = 1;
- dev-irqrid = 1;
+ if (pci_alloc_msi(dev-device, msicount) == 0) {
+ DRM_INFO(MSI enabled %d message(s)\n,
+ msicount);
+ dev-msi_enabled = 1;
+ dev-irqrid = 1;
+ }
}
- }
- dev-irqr = bus_alloc_resource_any(dev-device, SYS_RES_IRQ,
- dev-irqrid, RF_SHAREABLE);
- if (!dev-irqr) {
- return ENOENT;
+ dev-irqr = bus_alloc_resource_any(dev-device, SYS_RES_IRQ,
+ dev-irqrid, RF_SHAREABLE);
+ if (!dev-irqr) {
+ return ENOENT;
+ }
+
+ dev-irq = (int) rman_get_start(dev-irqr);
}
- dev-irq = (int) rman_get_start(dev-irqr);
-
mtx_init(dev-dev_lock, drmdev, NULL, MTX_DEF);
mtx_init(dev-irq_lock, drmirq, NULL, MTX_DEF);
mtx_init(dev-vbl_lock, drmvbl, NULL, MTX_DEF);
--
Cordula's Web. http://www.cordula.ws/
___
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
FreeBSD 7.2-rc1
I have encountered a rather interesting issue trying to install rc1. The system boots and then says there is no disk in the CD drive. The rc1 disk1 downloaded fine and the checksums matched. The CD will mount fine in other systems and can easily be read. I then let 7.0 boot on the test system and mounted the 7.2 cd. It mounts fine and I can read all the files ( well a few that I tested). Looking through the 7.0 dmesg I find some rather unexpected entries for the CD drive. acd0: FAILURE - READ_BIG MEDIUM ERROR asc=0x02 ascq=0x00 acd0: FAILURE - INQUIRY ILLEGAL REQUEST asc=0x24 ascq=0x00 cd0 at ata0 bus 0 target 1 lun 0 cd0: ATAPI CD ROM 1.5 Removable CD-ROM SCSI-0 device cd0: 3.300MB/s transfers cd0: cd present [287216 x 2048 byte records] ... acd0: FAILURE - READ_BIG MEDIUM ERROR asc=0x02 ascq=0x00 (cd0:ata0:0:1:0): READ(10). CDB: 28 0 0 4 61 ef 0 0 1 0 (cd0:ata0:0:1:0): CAM Status: SCSI Status Error (cd0:ata0:0:1:0): SCSI Status: Check Condition (cd0:ata0:0:1:0): MEDIUM ERROR asc:2,0 (cd0:ata0:0:1:0): No seek complete (cd0:ata0:0:1:0): Retrying Command (per Sense Data) acd0: FAILURE - READ_BIG MEDIUM ERROR asc=0x02 ascq=0x00 (cd0:ata0:0:1:0): READ(10). CDB: 28 0 0 4 61 ef 0 0 1 0 (cd0:ata0:0:1:0): CAM Status: SCSI Status Error (cd0:ata0:0:1:0): SCSI Status: Check Condition (cd0:ata0:0:1:0): MEDIUM ERROR asc:2,0 (cd0:ata0:0:1:0): No seek complete (cd0:ata0:0:1:0): Retrying Command (per Sense Data) acd0: FAILURE - READ_BIG MEDIUM ERROR asc=0x02 ascq=0x00 (cd0:ata0:0:1:0): READ(10). CDB: 28 0 0 4 61 ef 0 0 1 0 (cd0:ata0:0:1:0): CAM Status: SCSI Status Error (cd0:ata0:0:1:0): SCSI Status: Check Condition (cd0:ata0:0:1:0): MEDIUM ERROR asc:2,0 (cd0:ata0:0:1:0): No seek complete (cd0:ata0:0:1:0): Retrying Command (per Sense Data) acd0: FAILURE - READ_BIG MEDIUM ERROR asc=0x02 ascq=0x00 (cd0:ata0:0:1:0): READ(10). CDB: 28 0 0 4 61 ef 0 0 1 0 (cd0:ata0:0:1:0): CAM Status: SCSI Status Error (cd0:ata0:0:1:0): SCSI Status: Check Condition (cd0:ata0:0:1:0): MEDIUM ERROR asc:2,0 (cd0:ata0:0:1:0): No seek complete (cd0:ata0:0:1:0): Retrying Command (per Sense Data) acd0: FAILURE - READ_BIG MEDIUM ERROR asc=0x02 ascq=0x00 (cd0:ata0:0:1:0): READ(10). CDB: 28 0 0 4 61 ef 0 0 1 0 (cd0:ata0:0:1:0): CAM Status: SCSI Status Error (cd0:ata0:0:1:0): SCSI Status: Check Condition (cd0:ata0:0:1:0): MEDIUM ERROR asc:2,0 (cd0:ata0:0:1:0): No seek complete (cd0:ata0:0:1:0): Retries Exhausted (cd0:ata0:0:1:0): cddone: got error 0x5 back The drive works under 7.0, although with error messages. I also am hearing some rather unusual clicks and whines occasionally from the computer. I can't tell if they are from the CD drive but I suspect so. Many of them stop temporarily when I read a file from the CD. Taking the CD out seems to have stopped the noise. It would appear that I have some kind of CD drive failure. I don't understand why 7.0 can read the drive and 7.2 doesn't even see the disk in it. ___ 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
FreeBSD 7.2 RC1 amd64 Installation
Dear All , I have installed FreeBSD 7.2 amd64 RC1 from DVD .iso to test its installation issues . It detected hardware correctly and installed without any problems , but during installation of the packages the following errors occurred : Add of package ...name of package... aborted , error code 1 : apache-1.3.41 links-0.98,1 apache+mod_ssl-1.3.41+2.8.31 ghostscript7-nox11-7.07_20 emacs-22.3 Number of failed packages is significantly less than failed packages of Release 7.1 amd64 installation . Due to failed package installation , at the end Gnome in 7.1 Release and Stable was unusable , at least because terminal was not available in Gnome menus with nearly empty menus . Other points may be the following : (1) During user definition password confirmation is not asked but in root password definition it is asked . For the user , the same password entry box may be re-used for password confirmation without changing screen design because entered password is not plainly visible and during password confirmation it is not necessary to keep it there , and it does not require much work to include it . ( During installation of 7.1 , I carefully first recorded password on paper , entered it , later it did not worked . ) (2) CD/DVD drive is NOT released when the message ... ( be sure to remove any floppies/CDs/DVDs from the drives ) . (3) When shutdown is selected from Gnome menu either by the first user or the root , within displayed dialog box there is no a Shutdown item . It is necessary for the root open a terminal console , and enter shutdown -p now command . PC definition : Intel DG965WH main board with 2 GB memory , PS/2 mouse and keyboard . Installation Options : Starting FreeBSD menu : Default Standard installation Fresh install ( SATA II Disk cleared before start of installation and all of the disk allocated ) Standard boot Disk layout : Default All distributions selected All of the ports categories containing all of the packages selected with the following categories excluded : accessibility ( entries selected on dependency ) chinese , ipv6 , japanese , korean , palm . IPv6 : No DHCP : Yes , Ethernet to ADSL router : Yes , worked . Gateway : No iNetd and Network services : No SSH login : No FTP : No NFS Server : No NFS Client : No Console Settings : No Time zone setting : Yes Mouse : Tested , Worked Packages : Selected , Installed User : Defined Thank you very much Mehmet Erol Sanliturk ___ 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 7.2 RC1 amd64 Installation
On Sat, 2009-04-18 at 19:04 -0400, Mehmet Erol Sanliturk wrote: Thanks for the testing and feedback. I have installed FreeBSD 7.2 amd64 RC1 from DVD .iso to test its installation issues . It detected hardware correctly and installed without any problems , but during installation of the packages the following errors occurred : Add of package ...name of package... aborted , error code 1 : apache-1.3.41 links-0.98,1 apache+mod_ssl-1.3.41+2.8.31 ghostscript7-nox11-7.07_20 emacs-22.3 Number of failed packages is significantly less than failed packages of Release 7.1 amd64 installation . Due to failed package installation , at the end Gnome in 7.1 Release and Stable was unusable , at least because terminal was not available in Gnome menus with nearly empty menus . To be honest it never occured to me that someone would attempt to install all of the packages (or at least as many as you indicated in your summary that you did). The package failures you mention were almost certainly caused by conflicts (e.g. apache-1.3.41 and apache +mod_ssl-1.3.41+2.8.31 failing because apache-2.2.11_4 got installed first). When deciding what packages to include on the media as of late I haven't been taking the issue of possible conflicts into mind. Like I said I'm afraid it just never occured to me someone would just select virtually all of them as you did. I'll take this into consideration moving forward but just so you know it likely won't be addressed as part of 7.2-REL. It's likely you would need to be at least a little more selective in what packages you install if you want to avoid these sorts of package install failures caused by conflicts. Other points may be the following : (1) During user definition password confirmation is not asked but in root password definition it is asked . For the user , the same password entry box may be re-used for password confirmation without changing screen design because entered password is not plainly visible and during password confirmation it is not necessary to keep it there , and it does not require much work to include it . ( During installation of 7.1 , I carefully first recorded password on paper , entered it , later it did not worked . ) (2) CD/DVD drive is NOT released when the message ... ( be sure to remove any floppies/CDs/DVDs from the drives ) . Those are both fixed in head (what will become 8.0). I chose to not MFC those changes because they rearrange questions which might throw off people who are used to the older behavior, it's best to phase in that sort of thing as part of a new branch. (3) When shutdown is selected from Gnome menu either by the first user or the root , within displayed dialog box there is no a Shutdown item . It is necessary for the root open a terminal console , and enter shutdown -p now command . That one is a question for the Gnome folks but I *think* that's the intended behavior unless you configure the machine to launch the graphical interface as part of booting up. :-) -- Ken Smith - From there to here, from here to | kensm...@cse.buffalo.edu there, funny things are everywhere. | - Theodore Geisel | signature.asc Description: This is a digitally signed message part
Re: FreeBSD 7.2 RC1 amd64 Installation
On Sat, 18 Apr 2009 19:04:26 -0400 Mehmet Erol Sanliturk m.e.sanlit...@gmail.com wrote: (3) When shutdown is selected from Gnome menu either by the first user or the root , within displayed dialog box there is no a Shutdown item . It is necessary for the root open a terminal console , and enter shutdown -p now command . Have you installed sudo? I think those options (suspend/shutdown/hibernate) only get displayed if HAL sees sudo is available. -- Bruce Cran ___ 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 7.2 RC1 amd64 Installation
Bruce Cran wrote: On Sat, 18 Apr 2009 19:04:26 -0400 Mehmet Erol Sanliturk m.e.sanlit...@gmail.com wrote: (3) When shutdown is selected from Gnome menu either by the first user or the root , within displayed dialog box there is no a Shutdown item . It is necessary for the root open a terminal console , and enter shutdown -p now command . Have you installed sudo? I think those options (suspend/shutdown/hibernate) only get displayed if HAL sees sudo is available. Fact is you will get these options either if you have sudo and your user account is authorized to shutdown / reboot (this is the fallback method though) or if PolicyKit is configured (see /usr/local/etc/PolicyKit/PolicyKit.conf) to allow shutdown/reboot. Entries will look similar to these: match action=org.freedesktop.hal.power-management.shutdown match user=yourusername return result=yes/ /match /match match action=org.freedesktop.hal.power-management.reboot match user=yourusername return result=yes/ /match /match Have a look at http://www.freebsd.org/gnome/docs/halfaq.html for more HAL fun ;) ___ 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 7.2 RC1 amd64 Installation
On Sat, Apr 18, 2009 at 7:56 PM, Ken Smith kensm...@cse.buffalo.edu wrote: On Sat, 2009-04-18 at 19:04 -0400, Mehmet Erol Sanliturk wrote: To be honest it never occured to me that someone would attempt to install all of the packages (or at least as many as you indicated in your summary that you did). The package failures you mention were almost certainly caused by conflicts (e.g. apache-1.3.41 and apache +mod_ssl-1.3.41+2.8.31 failing because apache-2.2.11_4 got installed first). When deciding what packages to include on the media as of late I haven't been taking the issue of possible conflicts into mind. Like I said I'm afraid it just never occured to me someone would just select virtually all of them as you did. I'll take this into consideration moving forward but just so you know it likely won't be addressed as part of 7.2-REL. It's likely you would need to be at least a little more selective in what packages you install if you want to avoid these sorts of package install failures caused by conflicts. This is a test installation . Therefore installation of all the packages is a testing step . Such a test will show installability of packages and missing parts if any , and possible conflicts . Therefore package selection process rules may be adjusted accordingly . After marking selected packages I inspected every category list toward backward to see whether a last selection reverted a previously marked selection . Such a mark erasing did not occurred . Marking is able to select dependencies but at present it is not de-select conflicting selections . Another reason is that I am writing a multimedia information management system since 1986 and it is continuation of my PhD thesis subject . Concepts coverage is vast and I am studying every possible information sources one by one to learn at least their main ideas . This part is for me . That one is a question for the Gnome folks but I *think* that's the intended behavior unless you configure the machine to launch the graphical interface as part of booting up. :-) -- Ken Smith - From there to here, from here to | kensm...@cse.buffalo.edu there, funny things are everywhere. | - Theodore Geisel | After installation , FreeBSD boots in terminal mode . In this first boot , I have included gnome_enable=¨YES¨ into rc.conf and re-booted . Thank you very much Mehmet Erol Sanliturk ___ 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 7.2 RC1 amd64 Installation
On Sat, Apr 18, 2009 at 8:09 PM, Bruce Cran br...@cran.org.uk wrote: On Sat, 18 Apr 2009 19:04:26 -0400 Mehmet Erol Sanliturk m.e.sanlit...@gmail.com wrote: (3) When shutdown is selected from Gnome menu either by the first user or the root , within displayed dialog box there is no a Shutdown item . It is necessary for the root open a terminal console , and enter shutdown -p now command . Have you installed sudo? I think those options (suspend/shutdown/hibernate) only get displayed if HAL sees sudo is available. -- Bruce Cran It is very likely , because I had selected all of the packages . I do not know why HAL uses sudo for such a result . Actually I am using FreeBSD 7.1 i386 Stable again all of the packages installed but Gnome shut down menu is NOT affected by selection of sudo . Now I have checked my 7.1 i386 . sudo is installed and Gnome shutdown menu for the user ( not root ) included into operator group for USB mounts shows the menu item shudtdown . This means that there is a difference between i386 and amd64 shutdown rules in Gnome menus . Thank you very much Mehmet Erol Sanliturk ___ 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 7.2 RC1 amd64 Installation
On Sat, Apr 18, 2009 at 8:20 PM, Manolis Kiagias sonic200...@gmail.comwrote: Bruce Cran wrote: On Sat, 18 Apr 2009 19:04:26 -0400 Mehmet Erol Sanliturk m.e.sanlit...@gmail.com wrote: (3) When shutdown is selected from Gnome menu either by the first user or the root , within displayed dialog box there is no a Shutdown item . It is necessary for the root open a terminal console , and enter shutdown -p now command . Have you installed sudo? I think those options (suspend/shutdown/hibernate) only get displayed if HAL sees sudo is available. Fact is you will get these options either if you have sudo and your user account is authorized to shutdown / reboot (this is the fallback method though) or if PolicyKit is configured (see /usr/local/etc/PolicyKit/PolicyKit.conf) to allow shutdown/reboot. Entries will look similar to these: match action=org.freedesktop.hal.power-management.shutdown match user=yourusername return result=yes/ /match /match match action=org.freedesktop.hal.power-management.reboot match user=yourusername return result=yes/ /match /match Have a look at http://www.freebsd.org/gnome/docs/halfaq.html for more HAL fun ;) Nearly all of my expressed ideas about FreeBSD is not about my own requirements but especially newly beginning users . This point is utmost importance for me because my profession was the teaching of programming languages to the students in the University by starting from Introduction to computing . In those days computers were not available as they are today . I know how difficult is to make a start to learning to use a computing systems with respect to observations of the students . Then I want to emphasize the points that will be difficult for the new users to overcome at the beginning . If we do not reduce usage difficulty level of FreeBSD as much as possible it will prevent adoption of FreeBSD so much . Why FreeBSD so important for me is not a good question because FreeBSD is an excellent operating system with an immensely invested efforts by its very valuable developers and I think it is second to none . For my own difficulties : I wish - the Handbook includes more examples . - the man pages includes more examples for typical situations . In that respect my idea is that freebsd-questions and other lists contain excellent cases and solutions to them . In those days there is a concept of data mining . Actually these lists are containing very good sample cases and their solutions . By traversing the questions and problems and answers to them may be utilized to enhance the man pages and the handbook . This requires extensive knowledge about the Handbook and man pages which I do not have yet . Knowledgeable FreeBSD developers may contribute to this process . It is known that ideas expressed in mailing lists may be utilized for this process and my opinion is that no one will object to utilization of his/her ideas in such a utilization . Thank you very much . Mehmet Erol Sanliturk. ___ 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
