My son came to me with a older hp laptop. it had Win. 7 on it Which was screwed up. ended up hard drive had some bad sectors and wouldn't boot. downloaded kill disk, removed MBR, and tried to re-install. No luck. Tried Ubuntu, and kbuntu. no luck. tried LXDE. couldn't get the wifi working.(the dreaded bcm 4311) not complaining it was fun trying all the different commands and learning more and more about this OS. Tried KDE and everything worked right out the box. tried to update via synaptic and CRASH!!! So my Question is... Is there a way to update a fresh install, this late in the game. By loading the update packages in the order they were released?
In your initial posting you don't say if it is synaptic that crashes or the whole system, of course I am assuming you are referring to the whole system, in which case I must ask, at the point of crash; does the system freeze and refuse to respond, does the screen go dark or some other color, does the system go into reboot, or refuse to reboot? I am not trying to be annoying, but all these things mean something. If the system gos into reboot, it could be receiving a stray command from one of the update scripts, if it refuses to boot, could be a bad entry in the boot mgr file, if it freezes, there could be drivers trying to load that are incompatible with some of your hardware, or many other things. In order to try and help, I need to know more specifics. Please post back with more info on what exactly is happening, when it happens and how it happens.
It went into the reboot. but stopped half way through and gave me a flashing cursor. after seeing this your going to need to know where it stopped, or the last line of what it was trying to do. I can answer this if I do another synaptic update and see if it crashes again. Let me know everything I'll need to report before I crash this again please.
On Tuesday, July 17, 2012 10:16:46 PM UTC-5, webrat wrote:
> In your initial posting you don't say if it is synaptic that crashes or > the whole system, of course I am assuming you are referring to the whole > system, in which case I must ask,
> On Tuesday, July 17, 2012 5:54:52 PM UTC-4, LinuxnooB wrote:
>> Guess not! Are there packages i can block during the update?
On Thursday, July 19, 2012 7:11:02 PM UTC-4, LinuxnooB wrote:
> It went into the reboot. but stopped half way through and gave me a > flashing cursor. after seeing this your going to need to know where it > stopped, or the last line of what it was trying to do. I can answer this if > I do another synaptic update and see if it crashes again. Let me know > everything I'll need to report before I crash this again please.
> On Tuesday, July 17, 2012 10:16:46 PM UTC-5, webrat wrote:
>> In your initial posting you don't say if it is synaptic that crashes or >> the whole system, of course I am assuming you are referring to the whole >> system, in which case I must ask,
>> On Tuesday, July 17, 2012 5:54:52 PM UTC-4, LinuxnooB wrote:
>>> Guess not! Are there packages i can block during the update?
>>> ?
>> Hello, sorry it took so long to get back. weird work hours, yes I would
like to know what the last line said and also if any daemons failed to start. Here is something you can check on before crashing it again. while it is running, open the Control Center and go to "Boot", in the first screen you should see two (2) drop down selection menus and three text fields. In the first drop down selection you should see "GRUB with graphical menu", if not; open and change it, in the second "/dev/sda (ATA ST1000DM003-9YN1)", of course your drive id will be different than mine, but similar. The "Delay before booting" is simply how long you want to look at the boot screen before the system boots, default is (10) so you have enough time to choose should you have more than one operating system. The second screen is very important; the first line should read: * linux (/boot/vmlinuz), the second linux-nonfb (/boot/vmlinuz) and the third failsafe (/boot/vmlinuz). If any of these are diferent, click modify and correct them, then close the Control Center and reboot with Cntr Alt Del. Did you install from a CD or a USB drive? If from USB, was the drive still pluged in during reboot? If so, shut the system all the down and remove the drive; them restart the system. Strange glitch when using an iso cd image from a usb drive. Promise to try to get back in a more timely manner. Remember, linux is the perfect operating system.
The time lag between posts is not a problem, for you can see I'm right on the ball too. My son is using one of my extras in the meantime. All the info in the boot menu matches, except of course for the Toshiba hard drive. the first crash was when i tried to update the system with symantic. After the update the system rebooted and crashed. I had read over and over that installing too many update can crash your system. But that would mean you could only install a pclos right around the release date. Which doesn't make a lot of sense to me. I used an ISO disk to do the initial install. I will update again with synaptic (should be about 188 packets). and if it crashes I will make note of what it's doing.
On Friday, July 20, 2012 8:49:56 PM UTC-5, webrat wrote:
> On Thursday, July 19, 2012 7:11:02 PM UTC-4, LinuxnooB wrote:
>> It went into the reboot. but stopped half way through and gave me a >> flashing cursor. after seeing this your going to need to know where it >> stopped, or the last line of what it was trying to do. I can answer this if >> I do another synaptic update and see if it crashes again. Let me know >> everything I'll need to report before I crash this again please.
>> On Tuesday, July 17, 2012 10:16:46 PM UTC-5, webrat wrote:
>>> In your initial posting you don't say if it is synaptic that crashes or >>> the whole system, of course I am assuming you are referring to the whole >>> system, in which case I must ask,
>>> On Tuesday, July 17, 2012 5:54:52 PM UTC-4, LinuxnooB wrote:
>>>> Guess not! Are there packages i can block during the update?
>>>> ?
>>> Hello, sorry it took so long to get back. weird work hours, yes I would > like to know what the last line said and also if any daemons failed to > start. Here is something you can check on before crashing it again. while > it is running, open the Control Center and go to "Boot", in the first > screen you should see two (2) drop down selection menus and three text > fields. In the first drop down selection you should see "GRUB with > graphical menu", if not; open and change it, in the second "/dev/sda (ATA > ST1000DM003-9YN1)", of course your drive id will be different than mine, > but similar. The "Delay before booting" is simply how long you want to > look at the boot screen before the system boots, default is (10) so you > have enough time to choose should you have more than one operating system. > The second screen is very important; the first line should read: * linux > (/boot/vmlinuz), the second linux-nonfb (/boot/vmlinuz) and the third > failsafe (/boot/vmlinuz). If any of these are diferent, click modify and > correct them, then close the Control Center and reboot with Cntr Alt Del. > Did you install from a CD or a USB drive? If from USB, was the drive still > pluged in during reboot? If so, shut the system all the down and remove > the drive; them restart the system. Strange glitch when using an iso cd > image from a usb drive. Promise to try to get back in a more timely manner. > Remember, linux is the perfect operating system.
On Saturday, July 21, 2012 9:06:44 PM UTC-4, LinuxnooB wrote:
> The time lag between posts is not a problem, for you can see I'm right on > the ball too. My son is using one of my extras in the meantime. > All the info in the boot menu matches, except of course for the Toshiba > hard drive. the first crash was when i tried to update the system with > symantic. After the update the system rebooted and crashed. I had read over > and over that installing too many update can crash your system. But that > would mean you could only install a pclos right around the release date. > Which doesn't make a lot of sense to me. I used an ISO disk to do the > initial install. > I will update again with synaptic (should be about 188 packets). and if it > crashes I will make note of what it's doing.
> On Friday, July 20, 2012 8:49:56 PM UTC-5, webrat wrote:
>> On Thursday, July 19, 2012 7:11:02 PM UTC-4, LinuxnooB wrote:
>>> It went into the reboot. but stopped half way through and gave me a >>> flashing cursor. after seeing this your going to need to know where it >>> stopped, or the last line of what it was trying to do. I can answer this if >>> I do another synaptic update and see if it crashes again. Let me know >>> everything I'll need to report before I crash this again please.
>>> On Tuesday, July 17, 2012 10:16:46 PM UTC-5, webrat wrote:
>>>> In your initial posting you don't say if it is synaptic that crashes or >>>> the whole system, of course I am assuming you are referring to the whole >>>> system, in which case I must ask,
>>>> On Tuesday, July 17, 2012 5:54:52 PM UTC-4, LinuxnooB wrote:
>>>>> Guess not! Are there packages i can block during the update?
>>>>> ?
>>>> Hello, sorry it took so long to get back. weird work hours, yes I >> would like to know what the last line said and also if any daemons failed >> to start. Here is something you can check on before crashing it again. >> while it is running, open the Control Center and go to "Boot", in the first >> screen you should see two (2) drop down selection menus and three text >> fields. In the first drop down selection you should see "GRUB with >> graphical menu", if not; open and change it, in the second "/dev/sda (ATA >> ST1000DM003-9YN1)", of course your drive id will be different than mine, >> but similar. The "Delay before booting" is simply how long you want to >> look at the boot screen before the system boots, default is (10) so you >> have enough time to choose should you have more than one operating system. >> The second screen is very important; the first line should read: * linux >> (/boot/vmlinuz), the second linux-nonfb (/boot/vmlinuz) and the third >> failsafe (/boot/vmlinuz). If any of these are diferent, click modify and >> correct them, then close the Control Center and reboot with Cntr Alt Del. >> Did you install from a CD or a USB drive? If from USB, was the drive still >> pluged in during reboot? If so, shut the system all the down and remove >> the drive; them restart the system. Strange glitch when using an iso cd >> image from a usb drive. Promise to try to get back in a more timely manner. >> Remember, linux is the perfect operating system.
Greetings from the webrat! Ok, let me recap this event, the install was from an iso cd, so there is no usb problem; the hardrive was wiped and clean, so there is no contamination from an old boot manager; the boot configuration is correct, so there is no freeze from the new boot manager; the drive was listed in the boot config, so grub has the path. Since nothing was reconfigured before the update, that only leaves one thing to do; before your new update, go to the applications menu > software center > update package sources list, and click; then click "Ok" through the next four dialog boxes, the synaptic package list update manager will then run a speed test to see which package download mirror is the fastest and ask you to select the number of online repositories to keep, the default is five, and is more than sufficient. After clicking ok on this one, you will be asked for the administrator (root) password, this will open synaptic and load the window. Once it is loaded, click the reload button in the upper left corner; another dialog box will open with two mirrors selected, I would select the next three also for a total of five. This gives you all the latest packages to update with. Now run the update, and if my guess is correct all should be fine. It is true that the more packages updated the greater the odds of a misconfiguration, but the programers do a pretty good job of weeding out the bad stuff. My last update was 264 packages, I'm running apache 2.0 web server with a DHCP server, a DNS server and an FTP server, so I do a lot of updating for efficiency, and security. As long as I keep my system clean and use the freshest packages I don't have to many problems. I thank a synaptic update before the system update will fix the glitch. Let me know how it comes out, and if there are any further snags, we will address them, good luck. Remember; Linux is the perfect operating system!
> Greetings from the webrat! Ok, let me recap this event, the
> install was from an iso cd, so there is no usb problem; the hardrive was
> wiped and clean, so there is no contamination from an old boot manager; the
> boot configuration is correct, so there is no freeze from the new boot
> manager; the drive was listed in the boot config, so grub has the path.
> Since nothing was reconfigured before the update, that only leaves one
> thing to do; before your new update, go to the applications menu > software
> center > update package sources list, and click; then click "Ok" through
> the next four dialog boxes, the synaptic package list update manager will
> then run a speed test to see which package download mirror is the fastest
> and ask you to select the number of online repositories to keep, the
> default is five, and is more than sufficient. After clicking ok on this
> one, you will be asked for the administrator (root) password, this will
> open synaptic and load the window. Once it is loaded, click the reload
> button in the upper left corner; another dialog box will open with two
> mirrors selected, I would select the next three also for a total of five.
> This gives you all the latest packages to update with. Now run the update,
> and if my guess is correct all should be fine. It is true that the more
> packages updated the greater the odds of a misconfiguration, but the
> programers do a pretty good job of weeding out the bad stuff. My last
> update was 264 packages, I'm running apache 2.0 web server with a DHCP
> server, a DNS server and an FTP server, so I do a lot of updating for
> efficiency, and security. As long as I keep my system clean and use the
> freshest packages I don't have to many problems. I thank a synaptic update
> before the system update will fix the glitch. Let me know how it comes
> out, and if there are any further snags, we will address them, good luck.
> Remember; Linux is the perfect operating system!
Hello!
Nice that this worked for you!
Only one advice left in my opinion: please select just 1 (one) repository
in Synaptic - one of which you know it's always very up-to-date. That's a
general "rule"/advice in PCLinuxOS ;-)
Everything you said was the process I went thru except, I was not offered to pick synaptic mirrors. The last package synaptic was working on was a USB update? I don't think that ever finished when the screen went blank. Tried to reboot and this was the last line:
Then I tried to reboot in safe mode and it stopped here: (these are the last two lines)
fuse init (API version 7.16) non volatile memory driver V1.3
I then pushed the power button to re-install the pclos iso disk and it rebooted to the log-in screen. I logged in got the desktop but nothing worked. Tried to reboot a couple times but got the same.
Now I have reinstalled the kde iso, and everything works. (without synaptic update).
On Saturday, July 21, 2012 8:57:14 PM UTC-5, webrat wrote:
> On Saturday, July 21, 2012 9:06:44 PM UTC-4, LinuxnooB wrote:
>> The time lag between posts is not a problem, for you can see I'm right on >> the ball too. My son is using one of my extras in the meantime. >> All the info in the boot menu matches, except of course for the Toshiba >> hard drive. the first crash was when i tried to update the system with >> symantic. After the update the system rebooted and crashed. I had read over >> and over that installing too many update can crash your system. But that >> would mean you could only install a pclos right around the release date. >> Which doesn't make a lot of sense to me. I used an ISO disk to do the >> initial install. >> I will update again with synaptic (should be about 188 packets). and if >> it crashes I will make note of what it's doing.
>> On Friday, July 20, 2012 8:49:56 PM UTC-5, webrat wrote:
>>> On Thursday, July 19, 2012 7:11:02 PM UTC-4, LinuxnooB wrote:
>>>> It went into the reboot. but stopped half way through and gave me a >>>> flashing cursor. after seeing this your going to need to know where it >>>> stopped, or the last line of what it was trying to do. I can answer this if >>>> I do another synaptic update and see if it crashes again. Let me know >>>> everything I'll need to report before I crash this again please.
>>>> On Tuesday, July 17, 2012 10:16:46 PM UTC-5, webrat wrote:
>>>>> In your initial posting you don't say if it is synaptic that crashes >>>>> or the whole system, of course I am assuming you are referring to the whole >>>>> system, in which case I must ask,
>>>>> On Tuesday, July 17, 2012 5:54:52 PM UTC-4, LinuxnooB wrote:
>>>>>> Guess not! Are there packages i can block during the update?
>>>>>> ?
>>>>> Hello, sorry it took so long to get back. weird work hours, yes I >>> would like to know what the last line said and also if any daemons failed >>> to start. Here is something you can check on before crashing it again. >>> while it is running, open the Control Center and go to "Boot", in the first >>> screen you should see two (2) drop down selection menus and three text >>> fields. In the first drop down selection you should see "GRUB with >>> graphical menu", if not; open and change it, in the second "/dev/sda (ATA >>> ST1000DM003-9YN1)", of course your drive id will be different than mine, >>> but similar. The "Delay before booting" is simply how long you want to >>> look at the boot screen before the system boots, default is (10) so you >>> have enough time to choose should you have more than one operating system. >>> The second screen is very important; the first line should read: * linux >>> (/boot/vmlinuz), the second linux-nonfb (/boot/vmlinuz) and the third >>> failsafe (/boot/vmlinuz). If any of these are diferent, click modify and >>> correct them, then close the Control Center and reboot with Cntr Alt Del. >>> Did you install from a CD or a USB drive? If from USB, was the drive still >>> pluged in during reboot? If so, shut the system all the down and remove >>> the drive; them restart the system. Strange glitch when using an iso cd >>> image from a usb drive. Promise to try to get back in a more timely manner. >>> Remember, linux is the perfect operating system.
> Greetings from the webrat! Ok, let me recap this event, the > install was from an iso cd, so there is no usb problem; the hardrive was > wiped and clean, so there is no contamination from an old boot manager; the > boot configuration is correct, so there is no freeze from the new boot > manager; the drive was listed in the boot config, so grub has the path. > Since nothing was reconfigured before the update, that only leaves one > thing to do; before your new update, go to the applications menu > software > center > update package sources list, and click; then click "Ok" through > the next four dialog boxes, the synaptic package list update manager will > then run a speed test to see which package download mirror is the fastest > and ask you to select the number of online repositories to keep, the > default is five, and is more than sufficient. After clicking ok on this > one, you will be asked for the administrator (root) password, this will > open synaptic and load the window. Once it is loaded, click the reload > button in the upper left corner; another dialog box will open with two > mirrors selected, I would select the next three also for a total of five. > This gives you all the latest packages to update with. Now run the update, > and if my guess is correct all should be fine. It is true that the more > packages updated the greater the odds of a misconfiguration, but the > programers do a pretty good job of weeding out the bad stuff. My last > update was 264 packages, I'm running apache 2.0 web server with a DHCP > server, a DNS server and an FTP server, so I do a lot of updating for > efficiency, and security. As long as I keep my system clean and use the > freshest packages I don't have to many problems. I thank a synaptic update > before the system update will fix the glitch. Let me know how it comes > out, and if there are any further snags, we will address them, good luck. > Remember; Linux is the perfect operating system!
On Sunday, July 22, 2012 11:42:28 AM UTC-4, LinuxnooB wrote:
> Everything you said was the process I went thru except, I was not offered > to pick synaptic mirrors. > The last package synaptic was working on was a USB update? > I don't think that ever finished when the screen went blank. Tried to > reboot and this was the last line:
> Then I tried to reboot in safe mode and it stopped here: > (these are the last two lines)
> fuse init (API version 7.16) > non volatile memory driver V1.3
> I then pushed the power button to re-install the pclos iso disk and it > rebooted to the log-in screen. I logged in got the desktop but nothing > worked. Tried to reboot a couple times but got the same.
> Now I have reinstalled the kde iso, and everything works. (without > synaptic update).
> On Saturday, July 21, 2012 8:57:14 PM UTC-5, webrat wrote:
>> On Saturday, July 21, 2012 9:06:44 PM UTC-4, LinuxnooB wrote:
>>> The time lag between posts is not a problem, for you can see I'm right >>> on the ball too. My son is using one of my extras in the meantime. >>> All the info in the boot menu matches, except of course for the Toshiba >>> hard drive. the first crash was when i tried to update the system with >>> symantic. After the update the system rebooted and crashed. I had read over >>> and over that installing too many update can crash your system. But that >>> would mean you could only install a pclos right around the release date. >>> Which doesn't make a lot of sense to me. I used an ISO disk to do the >>> initial install. >>> I will update again with synaptic (should be about 188 packets). and if >>> it crashes I will make note of what it's doing.
>>> On Friday, July 20, 2012 8:49:56 PM UTC-5, webrat wrote:
>>>> On Thursday, July 19, 2012 7:11:02 PM UTC-4, LinuxnooB wrote:
>>>>> It went into the reboot. but stopped half way through and gave me a >>>>> flashing cursor. after seeing this your going to need to know where it >>>>> stopped, or the last line of what it was trying to do. I can answer this if >>>>> I do another synaptic update and see if it crashes again. Let me know >>>>> everything I'll need to report before I crash this again please.
>>>>> On Tuesday, July 17, 2012 10:16:46 PM UTC-5, webrat wrote:
>>>>>> In your initial posting you don't say if it is synaptic that crashes >>>>>> or the whole system, of course I am assuming you are referring to the whole >>>>>> system, in which case I must ask,
>>>>>> On Tuesday, July 17, 2012 5:54:52 PM UTC-4, LinuxnooB wrote:
>>>>>>> Guess not! Are there packages i can block during the update?
>>>>>>> ?
>>>>>> Hello, sorry it took so long to get back. weird work hours, yes I >>>> would like to know what the last line said and also if any daemons failed >>>> to start. Here is something you can check on before crashing it again. >>>> while it is running, open the Control Center and go to "Boot", in the first >>>> screen you should see two (2) drop down selection menus and three text >>>> fields. In the first drop down selection you should see "GRUB with >>>> graphical menu", if not; open and change it, in the second "/dev/sda (ATA >>>> ST1000DM003-9YN1)", of course your drive id will be different than mine, >>>> but similar. The "Delay before booting" is simply how long you want to >>>> look at the boot screen before the system boots, default is (10) so you >>>> have enough time to choose should you have more than one operating system. >>>> The second screen is very important; the first line should read: * linux >>>> (/boot/vmlinuz), the second linux-nonfb (/boot/vmlinuz) and the third >>>> failsafe (/boot/vmlinuz). If any of these are diferent, click modify and >>>> correct them, then close the Control Center and reboot with Cntr Alt Del. >>>> Did you install from a CD or a USB drive? If from USB, was the drive still >>>> pluged in during reboot? If so, shut the system all the down and remove >>>> the drive; them restart the system. Strange glitch when using an iso cd >>>> image from a usb drive. Promise to try to get back in a more timely manner. >>>> Remember, linux is the perfect operating system.
>> Greetings from the webrat! Ok, let me recap this event, the >> install was from an iso cd, so there is no usb problem; the hardrive was >> wiped and clean, so there is no contamination from an old boot manager; the >> boot configuration is correct, so there is no freeze from the new boot >> manager; the drive was listed in the boot config, so grub has the path. >> Since nothing was reconfigured before the update, that only leaves one >> thing to do; before your new update, go to the applications menu > software >> center > update package sources list, and click; then click "Ok" through >> the next four dialog boxes, the synaptic package list update manager will >> then run a speed test to see which package download mirror is the fastest >> and ask you to select the number of online repositories to keep, the >> default is five, and is more than sufficient. After clicking ok on this >> one, you will be asked for the administrator (root) password, this will >> open synaptic and load the window. Once it is loaded, click the reload >> button in the upper left corner; another dialog box will open with two >> mirrors selected, I would select the next three also for a total of five. >> This gives you all the latest packages to update with. Now run the update, >> and if my guess is correct all should be fine. It is true that the more >> packages updated the greater the odds of a misconfiguration, but the >> programers do a pretty good job of weeding out the bad stuff. My last >> update was 264 packages, I'm running apache 2.0 web server with a DHCP >> server, a DNS server and an FTP server, so I do a lot of updating for >> efficiency, and security. As long as I keep my system clean and use the >> freshest packages I don't have to many problems. I thank a synaptic update >> before the system update will fix the glitch. Let me know how it comes >> out, and if there are any further snags, we will address them, good luck. >> Remember; Linux is the perfect operating system!
Greetings once more from the WebRat! The line "EIP: [<f0844a6e>] wl_cfg80211_detatch+0xl6e/0x180 [wl} ss:esp 0068:ec043 cac", in your last post is the update script attempting to configure your wireless fidelity, or (wifi) card. Since the ralink or realtek 802.11 wireless lan driver borrows the read info from the "Windows" driver to run the card, and you are running linux stand alone, there was no info to configure, normally the script will exit and continue on without it. Fuse init not integrating the 7.16 memory driver left me a bit stumped, so I contacted a friend of mine who knows a lot more about these things than I. Here is what I learned: Unless you are running open servers, or mail servers on your system, you don't really benefit from the full auto update, and according to my friend, even so, you are better off to go through the list of auto updates before install and pick only the ones you really need, the rest is generic baggage. He says that the original install of pclos 2011 is perfect for a laptop just the way it is and if you do update; only update things you use such as sound players, office, games, video drivers that are specific to your card and designed to run in linux, and personal programs, photo editing and album storage applications, and the like. He says always update security, but look up articles on the pclos site and educate yourself about the latest security updates and how they function in your system, then install and configure accordingly. He says most of those auto updates aren't even needed by the standard user, and if one is not prepared to manually configure each one to his system, they can actually do more harm than good. I even asked about the second return poster who says one mirror is sufficient, and my friend agreed. so, I stand corrected on the mirrors. And running the standard install after talking to my friend just seems like sound advice to me. In fact, I am thinking seriously of planning a project of my own; to move my servers to a backup machine and reconfigure my own system according to this advice. I would add one more thing. It is a good idea to keep your kernel updated, but again, read and ask questions to become educated about the procedures and the expected results, always backup your system first and always compile the kernel on your own machine so that the machines configuration becomes integrated with the new kernel. Good luck, happy linux computing, and of course, post back and let us all know how it turns out.
That is pretty much what I have been doing while waiting for your reply. Except, In order for me to install Office libre, I need to update the system. I will look for ways to do it, but everything I've tried I get the same reply. "system update is required".
I had figured out that it was hanging up on the wifi card, but I couldn't configure the network or anything for that matter after the reboot.
I did get Ubuntu to run on here, but can't stand the Unity desk top. Had to install Synaptic, (ARE YOU KIDDING ME!) and then install gnome. everything seems to be working. with a little fiddling of the WIFI driver.
I have not forgot about PCLOS. As soon as I get my spare back I will be installing KDE on it. Then I can fiddle around with it like a little kid in a candy store.
I want to thank you and whomever else helped me out here, and PCLinuxOS seems to be awesome.
On Monday, July 23, 2012 6:32:39 PM UTC-5, WebRat wrote:
> On Sunday, July 22, 2012 11:42:28 AM UTC-4, LinuxnooB wrote:
>> Everything you said was the process I went thru except, I was not offered >> to pick synaptic mirrors. >> The last package synaptic was working on was a USB update? >> I don't think that ever finished when the screen went blank. Tried to >> reboot and this was the last line:
>> Then I tried to reboot in safe mode and it stopped here: >> (these are the last two lines)
>> fuse init (API version 7.16) >> non volatile memory driver V1.3
>> I then pushed the power button to re-install the pclos iso disk and it >> rebooted to the log-in screen. I logged in got the desktop but nothing >> worked. Tried to reboot a couple times but got the same.
>> Now I have reinstalled the kde iso, and everything works. (without >> synaptic update).
>> On Saturday, July 21, 2012 8:57:14 PM UTC-5, webrat wrote:
>>> On Saturday, July 21, 2012 9:06:44 PM UTC-4, LinuxnooB wrote:
>>>> The time lag between posts is not a problem, for you can see I'm right >>>> on the ball too. My son is using one of my extras in the meantime. >>>> All the info in the boot menu matches, except of course for the Toshiba >>>> hard drive. the first crash was when i tried to update the system with >>>> symantic. After the update the system rebooted and crashed. I had read over >>>> and over that installing too many update can crash your system. But that >>>> would mean you could only install a pclos right around the release date. >>>> Which doesn't make a lot of sense to me. I used an ISO disk to do the >>>> initial install. >>>> I will update again with synaptic (should be about 188 packets). and if >>>> it crashes I will make note of what it's doing.
>>>> On Friday, July 20, 2012 8:49:56 PM UTC-5, webrat wrote:
>>>>> On Thursday, July 19, 2012 7:11:02 PM UTC-4, LinuxnooB wrote:
>>>>>> It went into the reboot. but stopped half way through and gave me a >>>>>> flashing cursor. after seeing this your going to need to know where it >>>>>> stopped, or the last line of what it was trying to do. I can answer this if >>>>>> I do another synaptic update and see if it crashes again. Let me know >>>>>> everything I'll need to report before I crash this again please.
>>>>>> On Tuesday, July 17, 2012 10:16:46 PM UTC-5, webrat wrote:
>>>>>>> In your initial posting you don't say if it is synaptic that crashes >>>>>>> or the whole system, of course I am assuming you are referring to the whole >>>>>>> system, in which case I must ask,
>>>>>>> On Tuesday, July 17, 2012 5:54:52 PM UTC-4, LinuxnooB wrote:
>>>>>>>> Guess not! Are there packages i can block during the update?
>>>>>>>> ?
>>>>>>> Hello, sorry it took so long to get back. weird work hours, yes I >>>>> would like to know what the last line said and also if any daemons failed >>>>> to start. Here is something you can check on before crashing it again. >>>>> while it is running, open the Control Center and go to "Boot", in the first >>>>> screen you should see two (2) drop down selection menus and three text >>>>> fields. In the first drop down selection you should see "GRUB with >>>>> graphical menu", if not; open and change it, in the second "/dev/sda (ATA >>>>> ST1000DM003-9YN1)", of course your drive id will be different than mine, >>>>> but similar. The "Delay before booting" is simply how long you want to >>>>> look at the boot screen before the system boots, default is (10) so you >>>>> have enough time to choose should you have more than one operating system. >>>>> The second screen is very important; the first line should read: * linux >>>>> (/boot/vmlinuz), the second linux-nonfb (/boot/vmlinuz) and the third >>>>> failsafe (/boot/vmlinuz). If any of these are diferent, click modify and >>>>> correct them, then close the Control Center and reboot with Cntr Alt Del. >>>>> Did you install from a CD or a USB drive? If from USB, was the drive still >>>>> pluged in during reboot? If so, shut the system all the down and remove >>>>> the drive; them restart the system. Strange glitch when using an iso cd >>>>> image from a usb drive. Promise to try to get back in a more timely manner. >>>>> Remember, linux is the perfect operating system.
>>> Greetings from the webrat! Ok, let me recap this event, the >>> install was from an iso cd, so there is no usb problem; the hardrive was >>> wiped and clean, so there is no contamination from an old boot manager; the >>> boot configuration is correct, so there is no freeze from the new boot >>> manager; the drive was listed in the boot config, so grub has the path. >>> Since nothing was reconfigured before the update, that only leaves one >>> thing to do; before your new update, go to the applications menu > software >>> center > update package sources list, and click; then click "Ok" through >>> the next four dialog boxes, the synaptic package list update manager will >>> then run a speed test to see which package download mirror is the fastest >>> and ask you to select the number of online repositories to keep, the >>> default is five, and is more than sufficient. After clicking ok on this >>> one, you will be asked for the administrator (root) password, this will >>> open synaptic and load the window. Once it is loaded, click the reload >>> button in the upper left corner; another dialog box will open with two >>> mirrors selected, I would select the next three also for a total of five. >>> This gives you all the latest packages to update with. Now run the update, >>> and if my guess is correct all should be fine. It is true that the more >>> packages updated the greater the odds of a misconfiguration, but the >>> programers do a pretty good job of weeding out the bad stuff. My last >>> update was 264 packages, I'm running apache 2.0 web server with a DHCP >>> server, a DNS server and an FTP server, so I do a lot of updating for >>> efficiency, and security. As long as I keep my system clean and use the >>> freshest packages I don't have to many problems. I thank a synaptic update >>> before the system update will fix the glitch. Let me know how it comes >>> out, and if there are any further snags, we will address them, good luck. >>> Remember; Linux is the perfect operating system!
> Greetings once more from the WebRat! > The line "EIP: [<f0844a6e>] wl_cfg80211_detatch+0xl6e/0x180 [wl} ss:esp > 0068:ec043 cac", in your last post is the update script attempting to > configure your wireless fidelity, or (wifi) card. Since the ralink or > realtek 802.11 wireless lan driver borrows the read info from the "Windows" > driver to run the card, and you are running linux stand alone, there was no > info to configure, normally the script will exit and continue on without > it. Fuse init not integrating the 7.16 memory driver left me a bit > stumped, so I contacted a friend of mine who knows a lot more about these > things than I. Here is what I learned: Unless you are running open > servers, or mail servers on your system, you don't really benefit from the > full auto update, and according to my friend, even so, you are better off > to go through the list of auto updates before install and pick only the > ones you really need, the rest is generic baggage. He says that the > original install of pclos 2011 is perfect for a laptop just the way it is > and if you do update; only update things you use such as sound players, > office, games, video drivers that are specific to your card and designed to > run in linux, and personal programs, photo editing and album storage > applications, and the like. He says always update security, but look up > articles on the pclos site and educate yourself about the latest security > updates and how they function in your system, then install and configure > accordingly. He says most of those auto updates aren't even needed by the > standard user, and if one is not prepared to manually configure each one to > his system, they can actually do more harm than good. I even asked about > the second return poster who says one mirror is sufficient, and my friend > agreed. so, I stand corrected on the mirrors. And running the standard > install after talking to my friend just seems like sound advice to me. In > fact, I am thinking seriously of planning a project of my own; to move my > servers to a backup machine and reconfigure my own system according to this > advice. I would add one more thing. It is a good idea to keep your kernel > updated, but again, read and ask questions to become educated about the > procedures and the expected results, always backup your system first and > always compile the kernel on your own machine so that the machines > configuration becomes integrated with the new
On Tuesday, July 24, 2012 1:17:12 PM UTC-4, LinuxnooB wrote:
> That is pretty much what I have been doing while waiting for your reply. > Except, In order for me to install Office libre, I need to update the > system. I will look for ways to do it, but everything I've tried I get the > same reply. "system update is required".
> I had figured out that it was hanging up on the wifi card, but I couldn't > configure the network or anything for that matter after the reboot.
> I did get Ubuntu to run on here, but can't stand the Unity desk top. Had > to install Synaptic, (ARE YOU KIDDING ME!) and then install gnome. > everything seems to be working. with a little fiddling of the WIFI driver.
> I have not forgot about PCLOS. As soon as I get my spare back I will be > installing KDE on it. Then I can fiddle around with it like a little kid in > a candy store.
> I want to thank you and whomever else helped me out here, and PCLinuxOS > seems to be awesome.
> On Monday, July 23, 2012 6:32:39 PM UTC-5, WebRat wrote:
>> On Sunday, July 22, 2012 11:42:28 AM UTC-4, LinuxnooB wrote:
>>> Everything you said was the process I went thru except, I was not >>> offered to pick synaptic mirrors. >>> The last package synaptic was working on was a USB update? >>> I don't think that ever finished when the screen went blank. Tried to >>> reboot and this was the last line:
>>> Then I tried to reboot in safe mode and it stopped here: >>> (these are the last two lines)
>>> fuse init (API version 7.16) >>> non volatile memory driver V1.3
>>> I then pushed the power button to re-install the pclos iso disk and it >>> rebooted to the log-in screen. I logged in got the desktop but nothing >>> worked. Tried to reboot a couple times but got the same.
>>> Now I have reinstalled the kde iso, and everything works. (without >>> synaptic update).
>>> On Saturday, July 21, 2012 8:57:14 PM UTC-5, webrat wrote:
>>>> On Saturday, July 21, 2012 9:06:44 PM UTC-4, LinuxnooB wrote:
>>>>> The time lag between posts is not a problem, for you can see I'm right >>>>> on the ball too. My son is using one of my extras in the meantime. >>>>> All the info in the boot menu matches, except of course for the >>>>> Toshiba hard drive. the first crash was when i tried to update the system >>>>> with symantic. After the update the system rebooted and crashed. I had read >>>>> over and over that installing too many update can crash your system. But >>>>> that would mean you could only install a pclos right around the release >>>>> date. Which doesn't make a lot of sense to me. I used an ISO disk to do >>>>> the initial install. >>>>> I will update again with synaptic (should be about 188 packets). and >>>>> if it crashes I will make note of what it's doing.
>>>>> On Friday, July 20, 2012 8:49:56 PM UTC-5, webrat wrote:
>>>>>> On Thursday, July 19, 2012 7:11:02 PM UTC-4, LinuxnooB wrote:
>>>>>>> It went into the reboot. but stopped half way through and gave me a >>>>>>> flashing cursor. after seeing this your going to need to know where it >>>>>>> stopped, or the last line of what it was trying to do. I can answer this if >>>>>>> I do another synaptic update and see if it crashes again. Let me know >>>>>>> everything I'll need to report before I crash this again please.
>>>>>>> On Tuesday, July 17, 2012 10:16:46 PM UTC-5, webrat wrote:
>>>>>>>> In your initial posting you don't say if it is synaptic that >>>>>>>> crashes or the whole system, of course I am assuming you are referring to >>>>>>>> the whole system, in which case I must ask,
>>>>>>>> On Tuesday, July 17, 2012 5:54:52 PM UTC-4, LinuxnooB wrote:
>>>>>>>>> Guess not! Are there packages i can block during the update?
>>>>>>>>> ?
>>>>>>>> Hello, sorry it took so long to get back. weird work hours, yes I >>>>>> would like to know what the last line said and also if any daemons failed >>>>>> to start. Here is something you can check on before crashing it again. >>>>>> while it is running, open the Control Center and go to "Boot", in the first >>>>>> screen you should see two (2) drop down selection menus and three text >>>>>> fields. In the first drop down selection you should see "GRUB with >>>>>> graphical menu", if not; open and change it, in the second "/dev/sda (ATA >>>>>> ST1000DM003-9YN1)", of course your drive id will be different than mine, >>>>>> but similar. The "Delay before booting" is simply how long you want to >>>>>> look at the boot screen before the system boots, default is (10) so you >>>>>> have enough time to choose should you have more than one operating system. >>>>>> The second screen is very important; the first line should read: * linux >>>>>> (/boot/vmlinuz), the second linux-nonfb (/boot/vmlinuz) and the third >>>>>> failsafe (/boot/vmlinuz). If any of these are diferent, click modify and >>>>>> correct them, then close the Control Center and reboot with Cntr Alt Del. >>>>>> Did you install from a CD or a USB drive? If from USB, was the drive still >>>>>> pluged in during reboot? If so, shut the system all the down and remove >>>>>> the drive; them restart the system. Strange glitch when using an iso cd >>>>>> image from a usb drive. Promise to try to get back in a more timely manner. >>>>>> Remember, linux is the perfect operating system.
>>>> Greetings from the webrat! Ok, let me recap this event, the >>>> install was from an iso cd, so there is no usb problem; the hardrive was >>>> wiped and clean, so there is no contamination from an old boot manager; the >>>> boot configuration is correct, so there is no freeze from the new boot >>>> manager; the drive was listed in the boot config, so grub has the path. >>>> Since nothing was reconfigured before the update, that only leaves one >>>> thing to do; before your new update, go to the applications menu > software >>>> center > update package sources list, and click; then click "Ok" through >>>> the next four dialog boxes, the synaptic package list update manager will >>>> then run a speed test to see which package download mirror is the fastest >>>> and ask you to select the number of online repositories to keep, the >>>> default is five, and is more than sufficient. After clicking ok on this >>>> one, you will be asked for the administrator (root) password, this will >>>> open synaptic and load the window. Once it is loaded, click the reload >>>> button in the upper left corner; another dialog box will open with two >>>> mirrors selected, I would select the next three also for a total of five. >>>> This gives you all the latest packages to update with. Now run the update, >>>> and if my guess is correct all should be fine. It is true that the more >>>> packages updated the greater the odds of a misconfiguration, but the >>>> programers do a pretty good job of weeding out the bad stuff. My last >>>> update was 264 packages, I'm running apache 2.0 web server with a DHCP >>>> server, a DNS server and an FTP server, so I do a lot of updating for >>>> efficiency, and security. As long as I keep my system clean and use the >>>> freshest packages I don't have to many problems. I thank a synaptic update >>>> before the system update will fix the glitch. Let me know how it comes >>>> out, and if there are any further snags, we will address them, good luck. >>>> Remember; Linux is the perfect operating system!
>> Greetings once more from the WebRat! >> The line "EIP: [<f0844a6e>] wl_cfg80211_detatch+0xl6e/0x180 [wl} ss:esp >> 0068:ec043 cac", in your last post is the update script attempting to >> configure your wireless fidelity, or (wifi) card. Since the ralink or >> realtek 802.11 wireless lan driver borrows the read info from the "Windows" >> driver to run the card, and you are running linux stand alone, there was no >> info to configure, normally the script will exit and continue on without >> it. Fuse init not integrating the 7.16 memory driver left me a bit >> stumped, so I contacted a friend of mine who knows a lot more about these >> things than I. Here is what I learned: Unless you are running open >> servers, or mail servers on your system, you don't really benefit from the >> full auto update, and according to my friend, even so, you are better off >> to go through the list of auto updates before install and pick only the >> ones you really need, the rest is generic baggage. He says that the >> original install of pclos 2011 is perfect for a laptop just the way it is >> and if you do update; only update things you use such as sound players, >> office, games, video drivers that are specific to your card and designed to >> run in linux, and personal programs, photo editing and album storage >> applications, and the like. He says always update security, but look up >> articles on the pclos site and educate yourself about the latest security >> updates and how they function in your system, then install and configure >> accordingly. He says most of those auto updates aren't even needed by the >> standard user, and if one is not prepared to manually configure each one to >> his system, they can actually do more harm than good. I even asked about >> the second return poster who says one mirror is sufficient, and my friend >> agreed. so, I stand corrected on the mirrors. And running the standard >> install after talking to my friend just seems like sound advice to me. In >> fact, I am thinking seriously of planning a project of my own; to move my >> servers to a backup machine and reconfigure my own system according to this >> advice. I would add one more thing. It is a good idea to keep your kernel >> updated, but
On Tue, Jul 24, 2012 at 8:48 PM, WebRat <web...@neo.rr.com> wrote:
> On Tuesday, July 24, 2012 1:17:12 PM UTC-4, LinuxnooB wrote:
>> That is pretty much what I have been doing while waiting for your reply.
>> Except, In order for me to install Office libre, I need to update the
>> system. I will look for ways to do it, but everything I've tried I get the
>> same reply. "system update is required".
>> I had figured out that it was hanging up on the wifi card, but I couldn't
>> configure the network or anything for that matter after the reboot.
>> I did get Ubuntu to run on here, but can't stand the Unity desk top. Had
>> to install Synaptic, (ARE YOU KIDDING ME!) and then install gnome.
>> everything seems to be working. with a little fiddling of the WIFI driver.
>> I have not forgot about PCLOS. As soon as I get my spare back I will be
>> installing KDE on it. Then I can fiddle around with it like a little kid in
>> a candy store.
>> I want to thank you and whomever else helped me out here, and PCLinuxOS
>> seems to be awesome.
>> On Monday, July 23, 2012 6:32:39 PM UTC-5, WebRat wrote:
>>> On Sunday, July 22, 2012 11:42:28 AM UTC-4, LinuxnooB wrote:
>>>> Everything you said was the process I went thru except, I was not
>>>> offered to pick synaptic mirrors.
>>>> The last package synaptic was working on was a USB update?
>>>> I don't think that ever finished when the screen went blank. Tried to
>>>> reboot and this was the last line:
>>>> Then I tried to reboot in safe mode and it stopped here:
>>>> (these are the last two lines)
>>>> fuse init (API version 7.16)
>>>> non volatile memory driver V1.3
>>>> I then pushed the power button to re-install the pclos iso disk and it
>>>> rebooted to the log-in screen. I logged in got the desktop but nothing
>>>> worked. Tried to reboot a couple times but got the same.
>>>> Now I have reinstalled the kde iso, and everything works. (without
>>>> synaptic update).
>>>> On Saturday, July 21, 2012 8:57:14 PM UTC-5, webrat wrote:
>>>>> On Saturday, July 21, 2012 9:06:44 PM UTC-4, LinuxnooB wrote:
>>>>>> The time lag between posts is not a problem, for you can see I'm
>>>>>> right on the ball too. My son is using one of my extras in the meantime.
>>>>>> All the info in the boot menu matches, except of course for the
>>>>>> Toshiba hard drive. the first crash was when i tried to update the system
>>>>>> with symantic. After the update the system rebooted and crashed. I had read
>>>>>> over and over that installing too many update can crash your system. But
>>>>>> that would mean you could only install a pclos right around the release
>>>>>> date. Which doesn't make a lot of sense to me. I used an ISO disk to do
>>>>>> the initial install.
>>>>>> I will update again with synaptic (should be about 188 packets). and
>>>>>> if it crashes I will make note of what it's doing.
>>>>>> On Friday, July 20, 2012 8:49:56 PM UTC-5, webrat wrote:
>>>>>>> On Thursday, July 19, 2012 7:11:02 PM UTC-4, LinuxnooB wrote:
>>>>>>>> It went into the reboot. but stopped half way through and gave me a
>>>>>>>> flashing cursor. after seeing this your going to need to know where it
>>>>>>>> stopped, or the last line of what it was trying to do. I can answer this if
>>>>>>>> I do another synaptic update and see if it crashes again. Let me know
>>>>>>>> everything I'll need to report before I crash this again please.
>>>>>>>> On Tuesday, July 17, 2012 10:16:46 PM UTC-5, webrat wrote:
>>>>>>>>> In your initial posting you don't say if it is synaptic that
>>>>>>>>> crashes or the whole system, of course I am assuming you are referring to
>>>>>>>>> the whole system, in which case I must ask,
>>>>>>>>> On Tuesday, July 17, 2012 5:54:52 PM UTC-4, LinuxnooB wrote:
>>>>>>>>>> Guess not! Are there packages i can block during the update?
>>>>>>>>>> ?
>>>>>>>>> Hello, sorry it took so long to get back. weird work hours, yes I
>>>>>>> would like to know what the last line said and also if any daemons failed
>>>>>>> to start. Here is something you can check on before crashing it again.
>>>>>>> while it is running, open the Control Center and go to "Boot", in the first
>>>>>>> screen you should see two (2) drop down selection menus and three text
>>>>>>> fields. In the first drop down selection you should see "GRUB with
>>>>>>> graphical menu", if not; open and change it, in the second "/dev/sda (ATA
>>>>>>> ST1000DM003-9YN1)", of course your drive id will be different than mine,
>>>>>>> but similar. The "Delay before booting" is simply how long you want to
>>>>>>> look at the boot screen before the system boots, default is (10) so you
>>>>>>> have enough time to choose should you have more than one operating system.
>>>>>>> The second screen is very important; the first line should read: * linux
>>>>>>> (/boot/vmlinuz), the second linux-nonfb (/boot/vmlinuz) and the third
>>>>>>> failsafe (/boot/vmlinuz). If any of these are diferent, click modify and
>>>>>>> correct them, then close the Control Center and reboot with Cntr Alt Del.
>>>>>>> Did you install from a CD or a USB drive? If from USB, was the drive still
>>>>>>> pluged in during reboot? If so, shut the system all the down and remove
>>>>>>> the drive; them restart the system. Strange glitch when using an iso cd
>>>>>>> image from a usb drive. Promise to try to get back in a more timely manner.
>>>>>>> Remember, linux is the perfect operating system.
>>>>> Greetings from the webrat! Ok, let me recap this event, the
>>>>> install was from an iso cd, so there is no usb problem; the hardrive was
>>>>> wiped and clean, so there is no contamination from an old boot manager; the
>>>>> boot configuration is correct, so there is no freeze from the new boot
>>>>> manager; the drive was listed in the boot config, so grub has the path.
>>>>> Since nothing was reconfigured before the update, that only leaves one
>>>>> thing to do; before your new update, go to the applications menu > software
>>>>> center > update package sources list, and click; then click "Ok" through
>>>>> the next four dialog boxes, the synaptic package list update manager will
>>>>> then run a speed test to see which package download mirror is the fastest
>>>>> and ask you to select the number of online repositories to keep, the
>>>>> default is five, and is more than sufficient. After clicking ok on this
>>>>> one, you will be asked for the administrator (root) password, this will
>>>>> open synaptic and load the window. Once it is loaded, click the reload
>>>>> button in the upper left corner; another dialog box will open with two
>>>>> mirrors selected, I would select the next three also for a total of five.
>>>>> This gives you all the latest packages to update with. Now run the update,
>>>>> and if my guess is correct all should be fine. It is true that the more
>>>>> packages updated the greater the odds of a misconfiguration, but the
>>>>> programers do a pretty good job of weeding out the bad stuff. My last
>>>>> update was 264 packages, I'm running apache 2.0 web server with a DHCP
>>>>> server, a DNS server and an FTP server, so I do a lot of updating for
>>>>> efficiency, and security. As long as I keep my system clean and use the
>>>>> freshest packages I don't have to many problems. I thank a synaptic update
>>>>> before the system update will fix the glitch. Let me know how it comes
>>>>> out, and if there are any further snags, we will address them, good luck.
>>>>> Remember; Linux is the perfect operating system!
>>> Greetings once more from the WebRat!
>>> The line "EIP: [<f0844a6e>] wl_cfg80211_detatch+0xl6e/**0x180 [wl}
>>> ss:esp 0068:ec043 cac", in your last post is the update script attempting
>>> to configure your wireless fidelity, or (wifi) card. Since the ralink or
>>> realtek 802.11 wireless lan driver borrows the read info from the "Windows"
>>> driver to run the card, and you are running linux stand alone, there was no
>>> info to configure, normally the script will exit and continue on without
>>> it. Fuse init not integrating the 7.16 memory driver left me a bit
>>> stumped, so I contacted a friend of mine who knows a lot more about these
>>> things than I. Here is what I learned: Unless you are running open
>>> servers, or mail servers on your system, you don't really benefit from the
>>> full auto update, and according to my friend, even so, you are better off
>>> to go through the list of auto updates before install and pick only the
>>> ones you really need, the rest is generic baggage. He says that the
>>> original install of pclos 2011 is perfect for a laptop just the way it is
>>> and if you do update; only update things you use such as sound players,
>>> office, games, video drivers that are specific to your card and designed to
>>> run in linux, and personal programs, photo editing and album storage
>>> applications, and the like. He says always update security, but look up
>>> articles on the pclos site and educate yourself about the latest security
>>> updates and how they function in your system, then install and configure
>>> accordingly. He says most of those auto updates aren't even needed by the
>>> standard user, and if one is not prepared to manually configure each one to
>>> his system, they can actually do more harm than good. I even asked about
>>> the second return poster who says one mirror is sufficient, and my friend
>>> agreed. so, I stand corrected on the mirrors. And running the standard
>>> install after talking to my friend
I downloaded the ISO the day of install. I will wait until the New distro is released and see what happens with that one. In regards to the OS "Of which we will not speak" I hate it! it's slow and has to many limitations.
Rem: This computer has some faults, and I was just trying to get an OS to work. for my son. what I did learn from PCloS, I liked, and will be using. Can't wait to see what I can do with it...
>> It is entirely possible to install libre office without running the >> synaptic updates on the system. Just open a terminal and at the prompt >> type "lomanager --no-updatetest" without the quotes, or copy what is inside >> the quotes and past in the terminal then press enter; you will be prompted >> for your root password and libre will install just fine. And you will have >> the original pclos install with libre office up and running.
>> Then as mentioned before, you can update only the things you need for >> your particular system.
>> I agree entirely about the ubuntu unity desktop, it looks as if it were >> drawn by a five year old with a box of crayons. But that's just my opinion. >> Keep at it; we'll have you up and running in no time.
>> Remember; Linux is the perfect operating system.
> The above red text is incorrect. Doing partial updates will cause you > serious problems. PCLinuxOS is a dynamic, i.e. rolling release system. If > you allow any part of it to become out of date (not updated), you will > cause it to break, if not right away, then soon enough.
> If you are having problems with the initial update after installation, it > could be that your download was corrupted. Did you check the md5sum? Or it > could be that you used an older ISO. Did you use one you already had? On a > dynamic system, as time passes and packages get updated, the upgrade path > from older ISOs to the present gets broken.
> We do not discuss other distros here. Please stop it.
