Strange pkg upgrade

Hi all,
Today i run the pacman -Syu, and i get this:
# pacman -Syu
:: Synchronizing package databases...
:: current is up to date
error: anonymous login failed
:: extra is up to date
community [###############################################] 100% 109K 3.7K/s 00:00:29
:: Replace alsa-driver with kernel26 from "current"? [Y/n]
:: Replace devfsd with udev from "current"? [Y/n]
:: Replace rar with unrar from "current"? [Y/n]
Remove: alsa-driver devfsd rar
Targets: klibc-1.4-1 klibc-extras-1.6-1 klibc-udev-094-2 gen-init-cpio-2.6.17-1 mkinitcpio-0.4.2-1
kernel26-2.6.17.1-1 udev-094-2 unrar-3.6.4-2 archlinux-menus-1.1-2 kde-common-3.5.3-3 arts-1.5.3-2
avahi-0.6.10-3 bind-9.3.2-3 binutils-2.16.1-3 libstdc++5-3.3.6-1 codecs-20060501-4 coreutils-5.96-2
cups-1.2.1-3 curl-7.15.1-2 cyrus-sasl-2.1.21-4 db-4.4.20-2 dnsutils-9.3.2-2 gcc-4.1.1-3
ghostscript-8.15.2-3 gkrellm-2.2.7-3 glib2-2.10.3-1 kernel-headers-2.6.12.0-1 glibc-2.4-2
gnome-desktop-2.14.2-1 libtasn1-0.3.4-1 gnutls-1.4.0-1 gnome-vfs-2.14.2-1 pango-1.12.3-1 gtk2-2.8.18-1
gtkhtml-3.10.2-1 heimdal-0.7.2-3 hplip-1.6.6-1 initscripts-0.7.2-3 iputils-021109-5 kbd-1.12-5
kdelibs-3.5.3-3 kdebase-3.5.3-3 kde-i18n-pt_br-3.5.3-1 kdeaccessibility-3.5.3-1 bluez-libs-2.25-1
kdepim-3.5.3-1 kdemultimedia-3.5.3-2 kdegames-3.5.3-1 kdeaddons-3.5.3-2 kdeadmin-3.5.3-1
kdeartwork-3.5.3-2 kdebindings-3.5.3-1 kdeedu-3.5.3-1 kdegraphics-3.5.3-1 kdenetwork-3.5.3-3
kdesdk-3.5.3-2 kdetoys-3.5.3-1 kdeutils-3.5.3-2 kdewebdev-3.5.3-1 libsoup-2.2.93-1 libtiff-3.8.2-2
libxau-1.0.1-1 libxmu-1.0.2-1 libxss-1.1.0-1 libxt-1.0.2-1 licq-1.3.2-3 links-2.1pre20-2 lua-5.1.1-1
lynx-2.8.5-3 mcpp-2.5-3 module-init-tools-3.2.2-3 mozilla-firefox-1.5.0.4-1
mozilla-thunderbird-1.5.0.4-1 mysql-5.0.22-1 net-snmp-5.2.1-4 nmap-4.01-2 nspr-4.6.2-1 nss-3.11.1-1
openldap-2.3.21-3 openslp-1.2.0-3 openssl-0.9.8b-1 openssh-4.3p2-2 pam-0.81-2 perl-5.8.8-4
perl-net-ssleay-1.25-2 pmount-0.9.11-1 poppler-0.5.3-2 postfix-2.2.10-3 python-2.4.3-3 qca-tls-1.0-3
qscintilla-1.6-2 rdesktop-1.4.1-3 ruby-1.8.4-3 sip-4.4.5-2 smbclient-3.0.22A-3 totem-plparser-1.4.1-1
totem-1.4.1-1 totem-plugin-1.4.1-2 vim-7.0.17-2 weechat-0.1.9-4 wget-1.10.2-2 libxvmc-1.0.2-1
xine-lib-1.1.1-3 xine-ui-0.99.4-3 xorg-server-utils-1.0.2-1
Total Package Size: 435.2 MB
Proceed with upgrade? [Y/n]
This is correct?

Penguin wrote:
eduac wrote:
Snowman wrote:Yes.
http://www.archlinux.org/news.php#242
http://www.archlinux.org/news.php#244
What are the benefits to upgrade 435.2 MB of pkgs? I still cant understand
because gcc was updated?
humm...thats why? thx!

Similar Messages

Strange pkg-get problem help!!

Hello all,
I am trying to update my pkg-get catalog and I get the following error. Its a fresh install from a day ago.
# /opt/csw/bin/pkg-get -U
WARNING: gpg not found
Getting catalog...
--12:44:38-- http://www.ibiblio.org/pub/packages/solaris/csw/i386/5.10/catalog
=> `catalog'
Resolving www.ibiblio.org... 152.46.7.80
Connecting to www.ibiblio.org[152.46.7.80]:80... connected.
HTTP request sent, awaiting response... 404 Not Found
12:44:40 ERROR 404: Not Found.
ERROR: could not get catalog file
Looks like the catalog file does not exist on the host. How can I change the path to the catalog file?
Cheers,
Rob

Very strange,
The catalog path when launching the pkg-get -U is : http://www.ibiblio.org/pub/packages/solaris/csw/i386/5.10/catalog
In my /opt/csw/etc/pkg-get.conf . Looks like its getting the catalog path from somewhere else?
#pwd
# /opt/csw/etc
# cat pkg-get.conf
# Configuration file for "pkg-get"
# man pkg-get for details on the program
# This config file has been pre-customized for use with CSW packages.
# The latest set of CSW mirrors is always available at
# http://www.blastwave.org/mirrors.html
# default site, in USA:
url=http://usesolaris.org/pub/csw/unstable/
# secondary US mirror
#url=http://mirrors.usc.edu/pub/blastwave/unstable
url=http://www.ibiblio.org/pub/packages/solaris/csw
# See above url for other sites to use.
# If you are behind a firewall, set one of these as appropriate
#ftp_proxy=http://your-proxy:8023
#http_proxy=http://your-proxy:8023
#export http_proxy ftp_proxy
# You may also set PROXYFLAGS in your environment to set flags
# for wget like
# export PROXYFLAGS="--proxy-user=xxxx --proxy-passwd=yyy"
# Or set them here. but make sure the perms are readable.
# And consider that anyone on the machine can check your environment
# and grab the user/password combo.
# Solaris 10: If you wish to limit pkg-get to installing packages
# ONLY to the global zone, then uncomment this line
#PKGADDFLAGS=-G
# pkg-get now defaults to downloading to /var/pkg-get/downloads
# If you'd like it somewhere else, change it here
# PKGGET_DOWNLOAD_DIR=/some/large/dir/pkg-get
# By default, pkg-get keeps downloaded files, in PKGGET_DOWNLOAD_DIR,
# but removes them once they have been successfully pkgadd'd to the system.
# IF you set the following var to something, it will keep the
# downloaded file around, even after add.
#PKGGET_CACHE_FILES=true
# To disable use of gpg or md5, uncomment these
#use_gpg=false
#use_md5=false
#

Safari behaves strangely after upgrading to Lion

After upgrading to Lion, Safari is behaving strangely. When re-opening Safari after quitting, all windows from previous session re-opens. It didn't used to happen and also quite annoying. How can that be fixed? I only want my homepage to open, if I individually quit the windows by the red x-button, and then quite Safari normally, it opens up as priviously. Any ideas?
thanks

It is one of the over 250 new features of the World's Most Advanced Operating System called Resume.
If this is all that's bothering you just close all windows before quitting Safari or hold Shift when you launch Safari
If the whole resume thing is overbearing then...
Also in System Preferences > General there is a hard-to-find checkbox under "Number of recent items" you can turn off.
Also, you can hold the shift key to disable resume on a one time basis.
If you want to turn it off on a per app basis, (TextEdit is by example, replace TextEdit with the name of the app)
Launch Terminal and copy/paste this at the prompt...
defaults write com.apple.TextEdit NSQuitAlwaysKeepsWindows -bool false
Press return.
YOu can aslo accomplish this thriugh the GUI by going to ~/Library/Saved Application State/TextEdit and delete that file/
To turn off Resume globally...
chflags uchg ~/Library/"Saved Application State"
Press return
The reverse of the first one is to replace false with true.
The reverse of the second one is
chflags nouchg ~/Library/"Saved Application State"
Again, you can accomplish this through Finder by going to ~/Library/Saved Application State and deleting the folder.

[SOLVED] Desktop looks strange after upgrade to Gnome3!

Hi there,
I just upgraded my system (about 200 packages) and when I rebooted my Login-Screen looked strange.
When I logged in the strange screen persisted... Arch told me that Gnome3 couldn't be loaded and
that this has probably something to do with my graphics hardware.
This is what it looks like:
http://imageshack.us/photo/my-images/70 … otown.png/
As you can see my Dekstop looks like shit. Also the WiFi Password isnt saved, which is a minor issue for me.
But what really sucks is that the system flag is missing!!
I have no idea how to even start to solve this...
Please help!!!
-- mod edit: read the Forum Etiquette and only post thumbnails http://wiki.archlinux.org/index.php/For … s_and_Code [jwr] --
Last edited by gunjah292 (2011-05-05 13:03:56)

gunjah292 wrote:
I found out the problem, I checked the box in the second tab of the gnome-session-properties! I renamed the /.config directory in my home directory, rebooted than deleted the new .config and named the old one back!
Now it works again!!
Sorry to have stolen your time!
bug https://bugzilla.gnome.org/show_bug.cgi?id=647359
gunjah292 wrote:How can I mark this solved??
edit the first post.

24" iMac (Primo 2009) strange RAM upgrade issue

I have a 24" iMac (Primo 2009) at work. I been granted a RAM upgrade by the IT department and have received 2 indentical 4 GB modules.
The 24" iMac (Primo 2009) uses 1066 MHz DDR3 modules and supports up to 8 GB RAM in 2 slots. I have purchased RAM from this source http://www.dustin.dk/product/5010642132/corsair-4gb-ddr3-1066mhz-1x4gb-so-dimm-i mac-macbook-macpro/#intcmp=searchProvider_SiteSeeker (Corsair Mac Memory so they SHOULD be fine.)
Here's the issue:
I had 2x 2GB modules. I have taken both out.
I have inserted the new 2x 4GB modules but the machine refuses to boot. It gives off 3 beeps-interval-3 beeps-interval (repeats).
I took out one of the 4GB modules from slot B. It boots.
I inserted the one I removed in slot B again so we're back at 8GB. same beeps. No boot.
I switched the 2 4GB modules from slot A+B around. Now beep-interval-beep-interval (repeats) No boot.
I inserted one 4 GB in slot 1, and one of the old 2 GB in slot 2. It boots with 6GB RAM.
I inerted only the one that won't boot when in slot B in slot A, beep-interval-beep-interval (repeats) No boot.
OK - so logical deduction tells me one of the new 4GB RAM modules is defective. No matter what configuration, booting fails with that specific module inserted, though there are different beeps. I also know tha both slots work since the machine works with 6 GB RAM (2+4).
So I called Dustin, and since we're a big customer they sent a new moduel for free. But, I have the same isssue with the new module!! What are the chances I have recived 1 working and 2 defective modules? not big right? So my iMac seems fine with the old 2GB modules and one of the new 4 GB modules, but says no to the 2 other 4GB modules.
YES - I have tried resetting PRAM and SMC to no avail. Any clue?

Switched the 2 modules around, so there's now a 2GB in slot A and a 4 GB in slot B. Still works fine
Model Name:
iMac
Model Identifier:
iMac9,1
Processor Name:
Intel Core 2 Duo
Processor Speed:
2,93 GHz
Number of Processors:
1
Total Number of Cores:
2
L2 Cache:
6 MB
Memory:
6 GB
Bus Speed:
1,07 GHz
Boot ROM Version:
IM91.008D.B08
SMC Version (system):
1.45f0

Split View App acting Strangely after Upgrades

I have a Split View app with 6 views. I just upgraded to Xcode 3.2.5 (from 3.2.4) and also have the 4.2.1 OS update on the iPad.
Before the updates, my app on launch would always open on the first view. Now the app opens on the whatever the last view that was loaded before quiting the app.
I know I didn't make this happen. Is there something in the new software that forces this feature?
Steve

[Multitasking|http://developer.apple.com/library/ios/#documentation/iphone/conce ptual/iphoneosprogrammingguide/CoreApplication/CoreApplication.html#//apple_ref/ doc/uid/TP40007072-CH3-SW1] comes with 4.2.1.

A strange UCS upgrade story (N1k was the bad guy)

FYI
I would like to give you some information which caused quite a bit of trouble.
UCS with 4 chassis and 16 B250-M2, HDS storage, Brocade SAN, running 2.0.4d, ESXi 5.1.
We upgraded infrastructure to 2.2.3c and servers to 2.1.3f.
Due to some wrong setup, we also had to create new pools for UUID, MAC, pwwn, nwwn, new Template, and therefore 16 new SP.
After about 10 servers were updated without problems, the sh... hit the fan: moving any VM back to a newly upgraded server: no IP reachability (ping failed); management interface of the ESXi was reachable, ESXi properly joined Vcenter server.
This task was done remotely, from Europe to SFO (9 hours time difference) ! There was also no network guy available.
Solution:
Management interface was on a old fashion vswitch (what we preach since years ! otherwise a supergau would happened); all the remaining interfaces were on N1k DVS.
N1k licensing: http://www.cisco.com/c/en/us/support/docs/switches/nexus-1000v-switch-vmware-vsphere/116257-trouble-uuid-vsm-00.html
Nexus 1000v VSM and Host UUID Changes
The VSM of a Nexus 1000v switch issues licensing to hosts based on the universally unique identifier (UUID) of the hardware. This means that, if a host UUID changes for whatever reason, it is viewed as a new host by the VSM. While it is unusual for a host UUID to change during its lifetime, Cisco is aware of two situations that can cause a UUID change - a VMware software defect in ESXi 5.0 and a Cisco Unified Computing System (UCS) firmware defect on M3 blades.
When the UUID changes, the VSM sees the previously loaded module as a new host. The host is loaded as a new module and assigned a new module number and new license. If no licenses are available, the host is assigned an overdraft license; if there are no overdrafts available, the host is not assigned a license at all. If there are production virtual machines (VMs) on this host, they can no longer pass traffic, because unlicensed hosts cannot receive programming from the VSM.

I personally like the extra beeps, as you know the USB devices are working.
But MSI could had made an effort and document it, as many people get worried over nothing.
Anyway, glad you tested it and it was the USB beeps

Searching from Finder works strangely after upgrade

I get the appropriate list of files. But I cannot select them, and the status bar says 0 items.
For some reason I can't attach a screenshot here -- the site says the file type (tif) is not allowed.

Hi Again alamogirl!
You wrote "The install CDs that I used were grey instead of black.
That is the source of your problem!
USING OS X INSTALL CDS/DVDS ON MULTIPLE MACS
The question of using system/software install CDs/DVDs on more than one machine is frequently asked.
So, FYI:
System software installation CDs/DVDs, that come with a particular Mac model, are hardware specific to that model, and not intended to be used on other Mac models. For instance, the CDs/DVDs that are shipped with an iMac are not to be used on an iBook or eMac.
And the "Tiger" DVDs that are shipped with any new Mac, also are not to be used on other Mac models.
If such an installation were possible, or somehow accomplished successfully, that action would constitute a violation of your license agreement, which limits installation to a single computer.
The "Single User Software License Agreement" can be found here Software License Agreement.
Similarly, any "Upgrade" CDs/DVDs for a particular Mac OS will ONLY work for that Mac & system. For example, if a new Mac that shipped with Jaguar/Panther, was purchased shortly before the release of Panther/Tiger, the user may have purchased "Upgrade" CDs/DVDs, for a lesser price than the full install set. These CDs/DVDs do not contain all of the necessary components for an independent installation of Panther or Tiger.
The license agreement applies to single user retail versions of system software. The "Panther" or "Tiger" boxed set, for example.
If you wish to upgrade to Panther or Tiger, you have to purchase a Full Retail Version, of either OS.
Good Luck!
ali b

Upgrade IDSM2 from 4.1(5)S225 to 5,1 using application partition

can i upgrade an IDSM2 (WS-SVC-IDSM2-BUN)in a 6513 from 4.1(5)S225 to 5.1 by copying the 5.1 application partition to the sensor
[from the cisco userguide]
Chapter 10 Configuring the Sensor Using the CLI
Reimaging Appliances and Modules
Reimaging the IDSM-2
This section contains the following topics:
Catalyst Software, page 10-124
Cisco IOS Software, page 10-126
Catalyst Software
To reimage the application partition, follow these steps:
Step 1 Obtain the application partition file from Software Center on Cisco.com and copy
it to an FTP server.
Step 2 Log in to the switch CLI.
Step 3 Boot the IDSM-2 to the maintenance partition:
cat6k> (enable) reset module_number cf:1
Step 4 Log in to the maintenance partition CLI:
login: guest
Password: cisco
Step 5 Reimage the application partition:
[email protected]# upgrade ftp://user@ftp server IP/directory
path/image file
Step 6 Specify the FTP server password.
After the application partition file has been downloaded, you are asked if you
want to proceed:
Upgrading will wipe out the contents on the hard disk. Do you want to
proceed installing it [y|n]:
Step 7 Type y to continue.
When the application partition file has been installed, you are returned to the
maintenance partition CLI.
Step 8 Exit the maintenance partition CLI and return to the switch CLI.
Step 9 Reboot the IDSM-2 to the application partition:
cat6k> (enable) reset module_number hdd:1
Step 10 When the IDSM-2 has rebooted, check the software version.
Step 11 Log in to the application partition CLI and initialize the IDSM-2.
See Initializing the Sensor, page 10-2, for the procedure.
IF NOT, THEN IS THERE A SHORT CUT FROM 4.1 to 5.1 ?

Just wanted to clarify some things.
As Scott has already confirmed you can re-image using the method described and following Scott's advice on what additional updates to install.
BUT understand that any configuration you have your 4.1 sensor will be lost during that method of re-imaging to 5.1.
Another alternative is to first upgrade from 4.1(5)S225 to 5.0(1), and then to upgrade to 5.1(1).
The upgrade to 5.0(1) will convert the 4.1 configuration into a compatible 5.0 format.
I saw another post you made implying that you had to downgrade back to 4.1(5)S189 to do the 5.0(1) upgrade. This is not the case. You can upgrade directly from your current 4.1(5)S225 to 5.0(1).
You can install the IPS-K9-maj-5.0-1-S149.rpm.pkg file directly on your current 4.1(5)S225 sensor.
When S225 was installed on your 4.1(5) sensor, it also placed in storage the corresponding S225 update for your 5.0 sensor.
So when IPS-K9-maj-5.0-1-S149.rpm.pkg is installed on the sensor it will detect that stored off S225 for 5.0 and install it at the same time.
So once installed you will be immediately at 5.0(1)S225.
Once at 5.0(1)S225, then you can upgrade directly to 5.1(1) using the IPS-K9-min-5.1-1d.pkg upgrade.
(NOTE: 5.1-1d file was created to fix some upgrade bugs, but still installs the same 5.1(1) files as the original 5.1(1) upgrade package).
So you will wind up at 5.1(1)S225.
Now at this point I would recommend installing at least one later signature update (S226 or higher in your case) BEFORE installing the 5.1(1p1) patch.
And AFTER the signature update, then install the 5.1(1p1) Engineering Patch (contact the TAC for this patch).
Because of this specific upgrade path, the best way to avoid some issues is to install at least one signature update before installing the 5.1(1p1) patch. The signature update helps to ensure the sensor is ready for the 5.1(1p1) upgrade. Some of the files needed for the 5.1(1p1) upgrade have been seen to not get carried forward properly in the upgrade from 5.0(1) to 5.1(1), but a signature update corrects those issues.
NOTE: This precaution of installing the signature update BEFORE the 5.1(1p1) is only needed when upgrading from 5.0(1) to 5.1(1). If imaging directly to 5.1(1) using the maintenance partition, then the 5.1(1p1) can be installed before a signature update without an issue.
Once 5.1(1p1) is up and running and monitoring packets and generating alarms, then additional signature updates can be installed afterwards.

Can't use slim after recent upgrade

Hi all,
Just did pacman -Syu and now I can't use slim to login anymore. I searched the forum but I didn't see any other complaints with X and upgrades, lately.
This is the end of my pacman.log
[2010-08-26 08:33] synchronizing package lists
[2010-08-26 08:34] starting full system upgrade
[2010-08-26 08:34] upgraded bison (2.4.2-1 -> 2.4.3-1)
[2010-08-26 08:34] upgraded evince (2.30.3-1 -> 2.30.3-2)
[2010-08-26 08:34] upgraded glproto (1.4.11-2 -> 1.4.12-1)
[2010-08-26 08:34] upgraded kbproto (1.0.4-1 -> 1.0.5-1)
[2010-08-26 08:34] upgraded libfetch (2.32-1 -> 2.33-1)
[2010-08-26 08:34] upgraded libxau (1.0.5-1 -> 1.0.6-1)
[2010-08-26 08:34] upgraded libxcb (1.6-1 -> 1.7-1)
[2010-08-26 08:34] upgraded libx11 (1.3.4-1 -> 1.3.5-1)
[2010-08-26 08:34] upgraded libxi (1.3-2 -> 1.3.2-1)
[2010-08-26 08:34] upgraded mlocate (0.22.4-1 -> 0.22.4-2)
[2010-08-26 08:34] warning: /etc/pacman.d/mirrorlist installed as /etc/pacman.d/mirrorlist.pacnew
[2010-08-26 08:34] upgraded pacman-mirrorlist (20100808-1 -> 20100825-1)
[2010-08-26 08:34] upgraded renderproto (0.11-1 -> 0.11.1-1)
[2010-08-26 08:34] upgraded sqlite3 (3.7.0.1-1 -> 3.7.1-1)
[2010-08-26 08:35] upgraded tzdata (2010k-1 -> 2010l-1)
[2010-08-26 08:35] upgraded videoproto (2.3.0-1 -> 2.3.1-1)
[2010-08-26 08:35] upgraded xorg-server-utils (7.5-4 -> 7.5-6)
[2010-08-26 08:35] upgraded xorg-utils (7.6-2 -> 7.6-3)
[2010-08-26 08:35] upgraded xterm (259-1 -> 261-1)
Because of the xorg pkg. upgrades, I first thought X problems with my nvidia card but I found if I don't use slim, I can startx from console with no problem. I found if I changed to a different tty, killed x, etc. I could login and startx but the session would only last a couple of minutes and x would die. Seemed to do this even if I stopped slim with /etc/rc.d/slim stop but I was messing around with so many things that I can't be sure I actually stopped slim. As long as I didn't start it, everything seems to be fine.
The slim log isn't much help--it just mentions unable to connect to xserver, so for slim, it seems the upgrade to xorg-utils or xorg-server-utils is a problem.
Personally, I prefer to use no login manager anyway but this is on the main home computer and the wife likes to see a nice login screen (she doesn't like changes to the computer setup much).
Last edited by bgc1954 (2010-08-26 17:37:32)

Hello!
I'm experiencing the same problem: since I updated my system with 'pacman -Syu' slim no longer works on my laptop. More precisely, in place of the usual login screen of slim I get a black screen without prompt, but I still can use Ctrl-Alt-F1 to login in on tty. I tried to start slim from rc.conf or from inittab, no difference.
This problem does not seem to be related to Xorg and my (trident) video driver, as I believed first: replacing slim by lxdm without changing anything else solved the problem completely. Nevertheless I was very fond of the simplicity of slim and I would prefer to use it again if possible, but I have absolutely no idea of what is going on.
@Iceman81: I followed your link without understanding how to use the information there.
@bgc1954: Did you eventually solve your problem?
@Everybody: Could anyone give me a hint? I'm an ordinary Arch user, not a "master of Kyudo".
Regards,
LuX.

After Solaris 11.1 upgrade "GPU hung" OS starts, but no graphics, GPU hung

I have an Intel DH77EB motherboard. Solaris 11 installed fine (after disabling Intel VT-d). Upgrade to 11.1 processes went fine. OS boots up. Not services in maintenance mode. But, I can't access the console because the GPU has hung. Get the following in /var/adm/messages:
Nov 8 15:18:51 media genunix: [ID 851289 kern.warning] WARNING: [drm:i915_do_wait_request:1479] wait_for: i915_do_wait_request taking EBUSY
Nov 8 15:18:51 media genunix: [ID 552796 kern.warning] WARNING: [drm:i915_do_wait_request:1490] i915_do_wait_request returns -16 (awaiting 1292 at 1291, next 1293)
Nov 8 15:18:54 media genunix: [ID 851289 kern.warning] WARNING: [drm:i915_do_wait_request:1479] wait_for: i915_do_wait_request taking EBUSY
Nov 8 15:18:54 media genunix: [ID 552796 kern.warning] WARNING: [drm:i915_do_wait_request:1490] i915_do_wait_request returns -16 (awaiting 1292 at 1291, next 1293)
Nov 8 15:18:57 media genunix: [ID 851289 kern.warning] WARNING: [drm:i915_do_wait_request:1479] wait_for: i915_do_wait_request taking EBUSY
Nov 8 15:18:57 media genunix: [ID 552796 kern.warning] WARNING: [drm:i915_do_wait_request:1490] i915_do_wait_request returns -16 (awaiting 1292 at 1291, next 1293)
Nov 8 15:19:03 media genunix: [ID 409100 kern.warning] WARNING: [drm:i915_hangcheck_elapsed:1447] Hangcheck timer elapsed... GPU hung
scanpci output:
pci bus 0x0000 cardnum 0x02 function 0x00: vendor 0x8086 device 0x0152
Intel Corporation Xeon E3-1200 v2/3rd Gen Core processor Graphics Controller
In the HCL, it appears that the graphics device is supported.
HCL webpage snippet:
8086,162
i915
Information
Video
Intel Corporation
Xeon E3-1200 v2/3rd Gen Core processor Graphics Controller
8086,152
i915
Information
Video
Intel Corporation
Xeon E3-1200 v2/3rd Gen Core processor Graphics Controller
end snippet

I had trouble with Gnome desktop after upgrading from 11.0 to 11.1
Solution was to remove pkg SUNWvboxguest.
After suggessful remove I could re-run pkg upgrade.
Check/paste /var/log/Xorg.0.log that might give some hints...
I got eg. this error; but NOW its working...:)
Nov 15 20:18:59 dagobert11 gdm-binary[1109]: [ID 702911 daemon.warning] WARNING: GdmDisplay: Display /org/gnome/DisplayManager/Display1 failed 5 times in 18.000000 seconds, no longer managing display

Return to Original - Doesn work after upgrade

Strangely after upgrading iPhoto, in Edit mode, "Enhance" button does not seem to have any effect. Plus, after edit if we click "Return to Original" the image is damaged forever in iPhoto... kind of blurred image. It was working fine before the Mavericks upgrade. Also it was a new set of photos.. not from the old iPhoto library.

Can't reproduce that here.
What does
if we click "Return to Original" the image is damaged forever
mean?
As a Test:
Hold down the option (or alt) key and launch iPhoto. From the resulting menu select 'Create Library'
Import a few pics into this new, blank library. Is the Problem repeated there?
Post back with the result.

InDesign CS5 upgrade fails, erratic behavior. Caused by Siebel?

PC1 and PC2 upgrading from CS4 to CS5. Both PCs are identical. Install on one of them fails with odd icon issues, file association probelms, etc.The only difference we can find is that the PC that had a failed install has Oracle's Siebel CRM installed. Further evidence, after InDesign CS5 had been installed, my Sieble quit and had to be reinstalled. The only variable we can find is the installation of Siebel.
Is it possible that InDesign CS5 and Oracle's Siebel CRM have conflicts? We've been battling this for quite a while and may have to downgrade our entire enterprise back to CS4 is we can't eliminate the CS5 bugs. Please advise.

I'm on a fact finding mission right now. All the computers in our department that have CS4 and Siebel installed (and working fine) start acting really strange when upgrading. As soon as we try to updgrade CS4 to CS5, there are all these wierd errors and failures and exception erros, etc. So either Siebel was built with a bug way back when (we use an older version), or Siebel and CS5 try to use the same frameworks without playing nicely.
You're right, it could be Siebel. But it could be InDesign, just pulling togther info at the moment and want to know if anyone else is having problems. Our IS tam is patching Siebel this weekend, so we'll know a little more.

RE: Upgrading IDS4210 to Signature S289

Hello,
With regard to the Upgrading of the above IDS device, just reading through the "Cisco IPS Active Update Bulletin: 06-05-2007" that was emailed to me it states:
"The S289 signature update can ONLY be applied to version 5.1(5)E1 or later sensors as follows:
This signature update is supported on the IDS-4210, IDS-4215, IDS-4235, IPS-4240, IDS-4250, IPS-4255 and IPS-4260 Series Sensor Appliances"
But reading the Readme file on the Website it states:
"The IPS-sig-S289-req-E1.pkg upgrade file can be applied to
the following sensor platforms:
- IPS-42xx Cisco Intrusion Prevention System (IPS) sensors
- IDS-42xx Cisco Intrusion Detection System (IDS) sensors (except the IDS-4210, IDS-4220, and IDS-4230)"
Which one is right?
Slightly confused.
Regards,
Mark

It is a grey area.
The IDS-4210 was End-of-sale back on Dec 6, 2003:
http://www.cisco.com/en/US/products/hw/vpndevc/ps4077/prod_eol_notice09186a008032d508.html
By Cisco's Policy it will support signature updates on an End-of-sale sensor for a minimum of 3 years from the End-of-sale. So Signature Update support was guaranteed by policy only up till this past Dec 3, 3006.
http://www.cisco.com/en/US/products/hw/vpndevc/ps4077/prod_bulletin0900aecd80358daa.html
However, nothing has been done to intentionally prevent signature udpates newer than Dec 2006 from being installed on an IDS-4210.
I am not aware of any plan at this point to intentionally prevent installation of siganture updates on an IDS-4210.
In addition understand that the policy is a minimum of 3 years, but I am not sure how much longer than 3 years it would be officially supported.
IPS 5.1 software will continue to receive signature updates for another 18 months, and it is possible these 5.1 sig updates will continue to be installable on an IDS-4210.
This confusion is likely why the 2 documents are not in sync.
In addition the E1 signature update readme was originally written for 6.0 updates and IDS-4210 is not supported in 6.0. The 5.1 versions did not switch to E1 until later. When the readme was updated to cover both 5.1 and 6.0 it is possible that the supported platform list change (to add back in IDS-4210) was just overlooked. So I am not sure if it was intentionally put in not to support the IDS-4210 or if it was an editing mistake.
Personally I would recommend going ahead and installing it (save off your config before upgrading just in case).
If it installs OK (no bugs pop up during installation), then you should be fine running it on your IDS-4210.
But if problems do arise in installation of a future signature update, then you hit that grey area. And I am not sure what the response would be if that were to happen.
I will send an email out to our internal team and see what the "official" word is on IDS-4210 sig update support.
I would, however, recommend that you go ahead and see about upgrading to a newer sensor model.

Mail problems, slow browsing and Facebook problems after upgrading to Mountain Lion

Hi !
I have a 27” iMac from late 2009 which started acting really strange after upgrading to Mountain Lion.
Before that everything works fine but now Mail does not work, will not send replies or add attachments and browsing has become so slow that it usually times out. Another strange problem is Facebook messages which does not work at all (cannot read nor send(.
I have Lenovo laptop connected to the same network so I can benchmark and browsing works just fine on that aswell as FB messages.
Anybody got a solution to this other than using the iMac for offline use only ?

Hi !
I booted both the modem and router but it did not help. Then I tried using the iMac on wireless and now it works so must be something in my D-Link router.
Thanks for pointing me to the right direction !

Strange pkg upgrade

Similar Messages

Maybe you are looking for