Patch 118844-21 killed my laptop!

Solaris 3/05 loaded just fine, recently patch 118844-21 installed GRUB as a bootloader, replacing the one that Sol 10 3/05 installed. Now the machine does not complete a boot. It loads the copyright notice and then hangs. Before this patch my laptop was quite happy. What gives?

Hi,
I'm new on Solaris, I installed the Solaris 10 3/05 on my lap and yesterday I installed the patches recommended and today I found that I can't boot with Solaris. I think I have the same problem but I don't know how to uninstall the patches that you mentioned.
Can you help me?
Thanks.

Similar Messages

Flash Player 11.3 r300 is literally killing my laptop

Sometimes when I'm watching videos on YouTube or other websites which require flash player I can't have more than 2-3 tabs open before my laptop goes nuts.
The fan starts running really loud and crazy, my laptop gets really warm and when I open the task bar, the CPU memory usage is at like 90% or higher and the file Adobe Flash Player 11.3 r300 (it's version 262 I believe) has 50 or higher under the "CPU".
This program is literally killing my laptop and I'm really afraid that my laptop will break down and I really don't want that to happen.
My laptop used to work fine but ever since a couple of months ago it has been harder and harder for it to keep up with flash programs. Now I can't even view news sites with flash banners at the side because it uses too much CPU memory.

I had a similar problem a few years back, running an old Windows XP-based PC operating with (don't laugh) 250 mb of memory. After I upgraded the memory to 500 mb, and blew six years worth of dust from the insides of the case, the problems with the fan went away. The CPU usage still spiked up to about 70% when watching some youtube videos, but normally ranged around 25-40%.
In order to get help, you'll probably have to put down some specs, including:
The brand of laptop you're using/how old it is.
The operating system--windows xp/windows seven/whatever.
The amount of RAM you have installed. (In that way, the techs can see if it meet's the basic system requirements for the newer versions of Flash Player.)
What browser you're using--Firefox/IE/etc.
The complete version number of flash player you're using.
HTH,
Ortho_Fan
(not a techie)

Patch 118844-28 fails to install on Ultra 20?

We're trying to run the standard updatemanager on our Ultra 20 running Solaris 10 x86. We've installed patches a number of times but we're hitting a wall with the recent kernel patch, 118844-28.
This patch shows up as needing to be applied in both the updatemanager gui as well as when we run smpatch analyze. The problem is that it doesn't seem like it will install even though the tools say that the installation procedure was successful. Specifically: we instruct the gui to install the patch, it goes off and looks like it's installing, it comes back and says that the installation is complete and successful and that we need to reboot the machine, we tell it to reboot the machine and it does. But when the machine comes back up the updatemanager (and smpatch) still says that this patch needs to be applied. And showrev says that we're still back at version 27. So it seems like it's properly applying the patch but then the patch isn't actually applied.
We tried to install the patch by hand with smpatch add in single user mode and we had a similar experience. The only exception being that the patch process complained that we had to have patch 117435-02 installed (which we do).
Has anybody seen this before? Has anybody gotten this patch to install on this hardware?

Yes, I agree with that fix- I just did it a little opposite:
# eeprom boot-device=/pci@0,0/pci-ide@11,1/ide@0/cmdk@0,0:a
which added an extra alias (permanently) to my 'BIOS' settings-
# eeprom | grep boot
bootpath=/pci@0,0/pci-ide@7/ide@0/cmdk@0,0:a
boot-device=/pci@0,0/pci-ide@7/ide@0/cmdk@0,0:a
I re-ran the 10 Rec. Cluster and it not only installed the kernel patch, but, a handful of other patches in the bundle too.
--David

Unable to boot the sytem after applying kernel patch 118844-27

We have an hp ProLiant DL380 Storage server connected to HP StorageWorks Moduler Smart Array 30 via SCSI. Solaris 03/05 was installed previously on this system with kernel 118844-20. When I queried and installed all required patches with 'smpatch add -i .. ' command, all patches applied and the system is rebooted. After reboot, the system kept restarting. I followed the instructions on Sun Alert document 102087, and installed grub using 01/06 1st CDROM. It installed successfully, but problem persisted. The systems started booting, but before printing 'Configuring devices' the system rebooted again. Providing -v option to the kernel, it lastly printed a PCI device id (/pci@....) and after 2-3 seconds rebooted again.
Finally I had to reinstall the solaris (this time 01/06). The disk was accessible after booting with CD ROM, and I was able to get cylinder numbers of disk, and I installed the new system to the root partition of the other live upgrade environment. The boot disk was partitioned under linux, it was three partitions, Solaris2 (50GB),Solaris(4GB),Linux(18GB). Installation medium told that the fdisk partition was invalid, and i repartitioned the whole disk again.
System up and running Solaris 10 01/06 now, but the strange thing is that, previously hard disk (both boot disk and disks on array) locations were identified as '/dev/rdsk/c0tx' but now, the system sees that hard disks at '/dev/c1tx' and CDROM at '/dev/c0t0'.
Now I want to ask tow questions:
* Could this disk number change made the system unbootable previously?
* May I safely apply patch 118844-28 to the system
-Thanks

Here's a similar topic https://bbs.archlinux.org/viewtopic.php?pid=536210 also if that doesn't work you should install vesa as it also says it's not found in your log.

Driver e1000g problem - patch 118844-30

Hi,
the situation is like this. I have fujitsu-siemens pc and Solaris 10 03/05 x86 installed. I wanted to patch it with latest recommended patch cluster. After that I was not able to get to default router and switch did not see my mac anymore. I looked in the patch cluster and removed patch by patch till the kernel patch 118844-30. I finished my todays troubleshooting with one big ZERO :-), but it works now a can sleep well. There was no error reported in log files, no smf failed, nothing. If anyone knows, where is the real problem or how to apply some work-around, it would be great.
Le

Yes, I also experienced the same thing with 118844-30 and 118822-30. It seems other people are also having issues with 118855-xx. I simply bypassed these patches, after a painful rebuild, and now everything is OK, including all other recommended patches.

Kernel patch 118844-30 problem

I have an AMD-64 computer and when I try to install patch 118844-30 (and dependent patch for send mail), and restart, I get a million error messages at bootup, including "is syslogd running?". I had to reinstall the whole OS to get back to normal. Other updates worked fine.

Yes, I also experienced the same thing with 118844-30 and 118822-30. It seems other people are also having issues with 118855-xx. I simply bypassed these patches, after a painful rebuild, and now everything is OK, including all other recommended patches.

Bonjour has (almost) killed my laptop!!!!

Has anyone else had this problem....I struggled to get it up and running again...it wouldn't even give me anything on my screen. When it finally did, I managed to get to the Task Manager ... look at Events (I don't even know anything about computers....)....and there was an event log of Bonjour about 1 bazillion times with "ERROR" next to it....I stopped it. Then re-started....my computer works again EXCEPT I then did an emergency back-up of everything in case I lose it again.
The only thing I had recently installed was the later version of iTunes because I got a new iPhone 4s (so HAD to update it). Now it won't "accept" my iPhone because I have de-activated Bonjour. I'm in a catch 22 situation. Too scared to risk re-activating Bonjour BUT need to update my Phone AND want to copy over my iTunes library onto a back-up system so that I don't lose my music if this god forsaken programme kills my laptop permanently.
It's a 2 year old Sony Vaio (never had any problems whatsoever with it)...then this happens. I literally spent ALL weekend trying to get it to re-boot....hundreds of attempts before I got anywhere!

look at Events (I don't even know anything about computers....)....and there was an event log of Bonjour about 1 bazillion times with "ERROR" next to it
Head back into the event logs and open up some of those events. Are the details of the events all the same? If so, please post the contents of a typical event log message for Bonjour in a reply here so we can have a look.

T61P died, 1 long beep - 2 short beeps problem - Do the updates from Lenovo KILL our laptop?

Hi all
I bought T61P from 2 years ago, everything is ok until yesterday, I turn on my laptop and nothing display on the screen, and with this : 1 long beep - 2 short beeps....
I make some search, and found a lot of people have the same problem, and almost happend from September - 2009 to now.
I asked my self why this problem does not happend in the 1st year of using T61P...and this only happend from September - 2009 to now? DO THE UPDATES FROM LENOVO KILL OUR LAPTOP?
My laptop is out of warranty, and I hate to replace another mainboard.... If I must do it, I will throw my laptop to the Trash, and never buy another Lenovo laptops.

so far it looks like a strict hardware problem, not related to updates. however, some manufacturers try to "cheat" with bios updates - they make fan to run at higher speed lowering the mainboard temp. This does not solve the problem per se, it just makes laptop survive beyond warranty expiration date, so you, dear customer, will have to foot the bill.

Solaris 10 X86 kernel patch 118844-30 ... probably bad

I installed the patch on some Dells. Seemed to run fine.
Actually, I installed 121127-01, 113000-07, and 118344-06
first since they were required by 118844-30.
Some problems have now turned up.
1. When you power cycle one of the patched machines they
refuse to boot with
Warning - The following files in / differ from the boot archive:
/boot/solaris/bootenv.rc
to continue booting .. #svc clear system/boot-archive
and then demand the root password.
2. Randomly, when you do a reboot, a patched machine will claim
that the hardware has changed and demand that you run
kdmconfig. Simply going in and out of kdmconfig, without
changes, does the job. Weird.
3. I went to patch the next machine and after the patch
install and reboot, it was a total brick, with the error
File not executable
Panic : No entry point in kernel/unix
Press any key to reboot
And, naturally, this patch cannot be backed out. For yucks
I tried the equivalent patches on a sparc. No problems. So
I think Sun effed up the GRUB stuff in the kernel patch

Ok ... I noticed that deep down in the README for the patch
they say to do a "reboot -r". Cute. We'll try that.
That seemed to go ok, but when I tried a power cycle, it
wouldn't boot, claiming
SMF database integrity check of /etc/svc/repository.db
failed making me run
/lib/svc/bin/restore_repository
which turned out to be a struggle.
My advice - stay FAR AWAY from this patch. At minumum,
it makes the power up boot process VERY delicate. Wait
for the -32 rev, which I predict will not be long in coming.
Thank you sun.

Bad patch 118844-30

Just wondering if no one else is having issues with the Sun kernel patches?
A month ago we tried to install 118844-28, which failed to install see http://forum.sun.com/thread.jspa?threadID=28707&tstart=0
Now they release a new kernel patch, which seem to have the exact same problem.
The patch refuses to install saying that patch 117435-02 must be installed first and machine must be rebooted. The 117435-02 patch came with the installation of the OS.
From the prepatch script     #
     # biosdev failed. We can still apply the patch if the rootdisk
     # is the same as the bootdisk
     bootdev=`prtconf -v /devices | sed -n '/boot-device/{n;p;}' | grep pci | cut -f 2 -d \'`
     rootdev=`df -k ${BASEDIR:-/} | nawk 'NR > 1 { print $1 }'`
     if [ -n "$bootdev" ] ; then
          ls -l $rootdev | grep $bootdev > /dev/null
          if [ $? = 0 ]; then
               return 0
          fi
     fiRunning prtconf -v /devices will result in the following (among other things)name='bootpath' type=string items=1
            value='/pci@0,0/pci-ide@7/ide@0/cmdk@0,0:a'
name='bios-boot-device' type=string items=1
            value='80'Since they are still using sed -n '/boot-device/{n;p;}' which will return value='80' this patch will fail to install.

I've been trying to upgrade past 118844-26 for a while. This machine started out as a Solaris 10 x86 1/06 DVD install. I experience errors like you guys have listed here. My favorite so far was this, though:
118844-27
Executing prePatch script...
Once this KU patch is installed and you have rebooted your system,
you will not be able to patchrm this patch safely. Once the NEWBOOT
support is installed, removing it may cause your system to not
be bootable.
Do you wish to continue this installation {yes or no} [yes]?
(by default, installation will continue in 60 seconds)
Checking installed patches...
Executing prepatch script...
Usage: grep -hblcnsviw pattern file . . .
ERROR: One of the following may need to be corrected prior to installing this patch.
ERROR:
ERROR: The boot device may be different from the root device on biteme4.
ERROR: If you have booted from a floppy disk, eject the disk and reboot biteme4 prior
ERROR: to installing this patch.
ERROR: You may have forgotten to reboot biteme4 AFTER installing 117435-02.
ERROR: This configuration requires that 117435-02 be installed first and the
ERROR: system must then be rebooted prior to installing this patch.
The prepatch script exited with return code 1.
Patchadd is terminating.note the usage error on 'grep' ... apparently this patch had its grep arguments not quite sorted :)
I'll try the techniques posted here to see if I can move forward. Thanks for the input on this subject, folks!

Manual install of patch 118844-28

I'm trying to do a patchadd on 118844-28, but it complains that patch 117435-02 must be installed first or that the computer needs to be rebooted after the patch 117435-02 has been applied.
When using the Update Manager it seems that 117435-02 has been installed and I've rebooted numerous times after that, but still when I try patchadd on the kernel patch above it gives me that error message.
Am I doing something wrong or what's going on?
It was quite awhile since I used Solaris and I've now installed Solaris 10 x86 1/06 and used the Update Manager to install patches, but the kernel patch apparently must be installed manually so I've done a "shutdown -i S" to get into single user mode (I'm not sure if that's how one is supposed to do it) then
cd /var/sadm/spool/
patchadd 118844-28
Any ideas?

There may be a bug in the patch, in the prepatch script to be precise.
In the prepatch script there the line
bootdev=`prtconf -v /devices | sed -n '/boot-device/{n;p;}' | grep pci | cut -f 2 -d \'`
change boot-device to bootpath and then the patch seems to install alright.
See this thread for more information http://forum.sun.com/thread.jspa?threadID=28707&tstart=0

Ndiswrapper literally killed my laptop: story time

Just wanted to let everyone know what happened to my dell m1330 this week in case someone else notices the same behavior on their own system.
Despite the fact that I have an iwl4965, I've been using ndiswrapper for the better part of the year on this laptop just because I was so use to broadcom chipsets, I didn't care to try out the native driver ("if it's not broke" mentality). It's worked just fine for quite some time...until recently. For the last week or so, I've noticed that ntos_wq would, on occasion, start taking up a considerable amount of cpu time. But as long as I restarted my networking when it started acting up, it would fall back in line. But back on sunday, I left it running on the table while I was out to the rink for a few hours. When I returned, the fans were at full blast, and top was reporting a load of 4.7 something. Upon seeing this, I immediately turned it off.
A few hours later, I turned it back on to see if everything was alright. The random character corruptions made me believe otherwise. And as the final nail in the coffin, running glxgears hardlocked it. I would have liked to test this again to make sure it wasn't a fluke, but since then the only thing the laptop would do on boot-up was produce a white screen then slowly fade to randomly-colored vertical stripes.
Thankfully, I still had a couple months left on my warranty, and Dell didn't ask how I managed to give this thing a load so heavy the fans couldn't save it. They just sent a guy over and put a new motherboard in.
...also I'm now using the iwl4965 driver. Lesson learned.
Edit: And by literally killed, I mean it literally worked it to a fiery death, figuratively... wait wat?
Last edited by jb (2008-04-22 01:43:52)

Damn - also: Hooray for warranty!
But looking at it from a different angle, I cannot stop thinking it is Dell's fault. If you want to use your laptop to compile some large packages, then the laptop would be loaded 100% for several hours or days. The laptop should still be equipped with sufficient fans, no?
Or did Dell sell this laptop with a warning that you cannot use this laptop at full speed for several hours? I don't think so...
Zl.

I want to roll ff back to 3.0, 4.0 and up is taking up to much space to run. since i have updated to 5.0 the problem is killing my laptop and i liked how well 3.0 ran, it didnt max out my cpu like 4.0 and up does.

firefox is using up to 90% of my PCU on my laptop. I spend more time twiddling my thumbs waiting for things to load or i watch my laptop crash from over heating. I did not have this problem with 3.0 and would like to go back to it, how do I roll back firefox to 3.0 so my laptop doesnt burn up ? i run vista on my laptop.

In case your Firefox profile became damaged during the upgrade, or add-on is causing the problem, you could test whether a new blank Firefox profile cures those ills.
First, I recommend backing up your Firefox settings in case something goes wrong. See [https://support.mozilla.com/en-US/kb/Backing+up+your+information Backing up your information]. (You can copy your entire Firefox profile folder somewhere outside of the Mozilla folder.)
Next, close Firefox and fire up the profile manager to create a new profile: [https://support.mozilla.com/kb/Managing+profiles Managing profiles].
If that tests out, you can import your bookmarks and move your saved passwords over from your problem profile to the new profile. [https://support.mozilla.com/en-US/kb/Recovering+important+data+from+an+old+profile Recovering important data from an old profile].
If that fails, here's the process to roll back:
First, I recommend backing up your Firefox settings in case something goes wrong. See [https://support.mozilla.com/en-US/kb/Backing+up+your+information Backing up your information]. (You can copy your entire Firefox profile folder somewhere outside of the Mozilla folder.)
Next, download and save Firefox 3.6 to your desktop for future installation. http://www.mozilla.com/firefox/all-older
Close Firefox 5.
You could install Firefox 3.6 over it (many have reported success) or you could uninstall Firefox first. If you uninstall, do not remove your personal data and settings, just the program.
Unless you have installed an incompatible add-on, Firefox 3.6 should pick up where you left off. If there are serious issues, please post back with details.
Note: I haven't actually tried this myself!

Nvidia module in X fails to load after Patch 118844-28

I'm new to Solaris so please bear with me.
I just received a shipment of Ultra 20 workstations and while setting up one of them, I used the Update manager to install all the patches. After installing the kernel update, X fails to run since the Nvidia module doesn't load, which makes sense since its a new kernel(Is this wrong, I'm used to Linux).
So I download the latest nvidia module from Nvidia.com and the installer runs with no problem. I reboot and still no go.
I've looked around and found something about using the update_drv command, and I tried that with no luck. Used reboot -- -r to reconfigure everything and still nothing. There is nothing that stands out from dmesg, so I'm at my wits end.
Any ideas?

After installing
the kernel update, X fails to run since the Nvidia
module doesn't load, which makes sense since its a
new kernel(Is this wrong, I'm used to Linux).I don't know why X or the Nvidia module fails after the kernel
upgrade...
But for Solaris is does not make sense that drivers start to fail
when the kernel is patched. This assumes the driver is using
documented kernel interfaces only - in this case a kernel update
should not cause driver failures.

Windows 10 update killed my laptop, P2PP BurnBoot Check Failed( restoration incomplete)

I tryed to update to windows 10, but I was in audit mode and could not, I rebooted my laptop out of audit mode and had to restore some software and settings, the restore failed and gave me this BurnBoot error.
I have already tried resetting the BIOS, changing time, putting it in legacy mode etc, still did not work, please help me!

I suggest to try performing a system recovery but set your expectation that this will remove everything that you have from your laptop and will set it up just like a brand new one again, then if you still have plans of going to WIndows 10 upgrade I strongly recommend to run all updates first through WIndows Update and HP SUpport Assistant Here's the guide to perform System Recovery http://support.hp.com/us-en/document/c03489643 Hope this helps

Patch 118844-21 killed my laptop!

Similar Messages

Maybe you are looking for