Tons of error reports, hang-ups, failing repositories all since I last updated...

Your solution is better, Matt. Long commands connected through pipes look rather intimidating to new users, and we are in the Absolute Beginners Section. But I've got a question, too. Locking linux-image at the current version would undoubtedly work in precise as this package has versioned dependencies there. The OP however is using quantal, and from what i see here, it seems that locking linux-image won't prevent newer versions of linux-image-generic from being installed. Perhaps linux-image-generic should be locked instead?

Hi

Quote:

---

Originally Posted by schragge

Your solution is better, Matt. Long commands connected through pipes look rather intimidating to new users, and we are in the Absolute Beginners Section. But I've got a question, too. Locking linux-image at the current version would undobtedly work in precise as this package has versioned dependencies there. The OP however is using quantal, and from what i see here, it seems that locking linux-image won't prevent newer versions of linux-image-generic from being installed. Perhaps linux-image-generic should be locked instead?

---

I think you are right schragge. Good catch ! It's been a good while since i pinned a kernel.

@OP. Lock linux-image-generic.

Kind regards

Thanks matt and schragge!

I ended up using matt's method because schragge's gave me an error. I really appreciate all the help from you and thank you Bashing-om! I learned a lot from all of your help!

How do I mark this as solved? And my wifi/wired connection is still acting up... should we solve that hear or should I make a different thread since it's a different issue?

vadertater;

Appreciate your including me in the thanks, to be honest, I did little but learn some too.
Yes, A different issue == another thread.
And the interim method to mark as solved:

Quote:

---

Go to the first post in your thread. Click on "Edit Post". Now click on the orange "Go Advanced" button. In the advanced editor change the prefix to "SOLVED". Now click on the orange "Save Changes" button.

---

enjoyed working with all

Ok, I lied... just got another error message from usr/share/apport/apportcheckresume just occured when I logged in after a short hibernation. I also got a message about how I need to file a bug report with bugzilla since the new kernel is not a standard linux kernel, the message made me click out before I could just copy and paste it. I'll try to get a more accurate description for the error soon

Hi

That sounds like a different issue than the GPU hang issue.

Have you had any GPU hangs since installing the new kernel ?

Kind regards

No GPU hangs. My friend recommended I just turn off apport by going into the text and setting enable=0 instead of 1

Hi

Your friends suggestion would disable apport and you would not see the error message.

You'll need to edit the file

Code:

---

/etc/default/apport

---

and the run the update-initramfs command (IIRC).

If your interested in getting to the root cause of the problem though then post back any error message when it happens again.

Keep an eye on the log file...

Code:

---

/var/log/syslog

---

Kind regards

I'll post back when it pops up again. May be a while... this error doesn't seem to occur as frequently as the last ones.

Thanks very much to matt_symes for pointing me to this thread and to all participants. Yes I do have in-built intel sandybridge x86/MMX/SSE2. The messages here were a little daunting to start with but I have stuck with it. I used the http://www.liberiangeek.net/2013/03/...-ubuntu-12-10 link in this thread. I have had no problems since (only an hour or so ago though!:))

Thank you all very much. Keep up the good work guys :KS