pclinuxos freezes on toshiba satellite c655-s5533 (solved)

[george]

hey y'all,

Here is my problem in a nutshell. I bought a Toshiba satellite c655-s5533 and I have tried no less than 6 different distros and all have the same issue.The screen freezes. I am using the latest version of pclinuxos kde mini me, the hope was that by using mini me I would have only what was needed. Alas, I was able to install with no problem but on rebooting the system it froze at the sign in screen (this required a hard boot) I restarted the system got as far as the desktop then it froze.I could use some help with this so any info you need just ask. Below are the specs.

AMD E-Series Processor E-300
GRAPHICS ENGINE*
AMD Radeon™ HD 6310
Memory and Storage
MEMORY*
4GB DDR3 1066MHz memory

[CaptainSarcastic]

This is something of a shot in the dark, but I have an Acer netbook with a C-60 processor, and there is a quirk that will lock up the machine if you don't have the BIOS set to try to boot from the network first.  It has to try the PXE boot, then have it fail and THEN boot from the hard drive.  It works just fine with that adjustment.

I'd try changing the boot order to try the network boot first, in case you are running into a similar issue that my hardware has.

You could also try disabling ACPI from the GRUB menu, or other safe boot options from there.

Best advice I have off the top of my head.

[jakesdad]

I have the same problem with my Toshiba 655D-S5518. Try booting into windows and do a restart, then select PClinux OS. Mine works great if I do a warm reboot. Locks up if I start from a cold boot. I have a post in laptop hardware.
.

[bicol_willem]

I have the same problem with my Toshiba 655D-S5518. Try booting into windows and do a restart, then select PClinux OS. Mine works great if I do a warm reboot. Locks up if I start from a cold boot. I have a post in laptop hardware.
.

Yes, I got a simular setup on a simular based machine (Emachines D443). E450 processor and Radeon HD6320. Will NOT boot Linux but, as you said, me too found out that if I installed Windows and boot that one  , then reboot, I go straight to a successful Linux boot. Amazing stuff I never was able to solve. The OP might sure want to try this.

[george]

Thanks everyone for your input. I have noticed that a cold boot into Linux is a no go, however as many have stated booting into win 7 first then into Linux is not a prob. I am very curios as to why this occurs.

[CaptainSarcastic]

Thanks everyone for your input. I have noticed that a cold boot into Linux is a no go, however as many have stated booting into win 7 first then into Linux is not a prob. I am very curios as to why this occurs.

Do you get to GRUB?  And did you try enabling PXE boot in the BIOS?

[bicol_willem]

Thanks everyone for your input. I have noticed that a cold boot into Linux is a no go, however as many have stated booting into win 7 first then into Linux is not a prob. I am very curios as to why this occurs.

You are not alone at that 

[Serj]

Thanks everyone for your input. I have noticed that a cold boot into Linux is a no go, however as many have stated booting into win 7 first then into Linux is not a prob. I am very curios as to why this occurs.

Based on my experience, I have come to the conclusion that some of the drivers for Windows 7 have features awakening or activation devices. Perhaps some Linux-drivers for these devices are not able to do it.
The method, which offered CaptainSarcastic, probably just awakens or activates a network card.
My conclusion is this: to work on modern computers, you must have the latest version of the drivers in the repo. At least for the main and the most common devices.

[george]

captainsarcastic,

sorry for the late reply I work full time and go to school full time add to that a wife and a kid and you get busy. I have not tried your suggestion about grub but I will this weekend and I will let you know how it went. Regardless of the outcome thanks for the suggestion.

[bicol_willem]

captainsarcastic,

sorry for the late reply I work full time and go to school full time add to that a wife and a kid and you get busy. I have not tried your suggestion about grub but I will this weekend and I will let you know how it went. Regardless of the outcome thanks for the suggestion.

Out of those two suggestions of captainsarcastic (grub and BIOS), my best guess is that your best chance on the solution will be found in the BIOS. (Happened to me). Set network boot as first boot option. A solution brought by loudog after a long long search and discussion that worked for me. Good luck!

[george]

thanks to all who gave input. Followed CapitanSarcastics advice regarding change in bios to boot from network works great.

[CaptainSarcastic]

thanks to all who gave input. Followed CapitanSarcastics advice regarding change in bios to boot from network works great.

Glad that it worked!

[Monkberry]

I've found a workaround for this boot problem is to add to the grub command line, "hpet=off" and "nomodeset", then it boots up just fine off of any live linux usb/cd, be it knoppix, mint, back track, etc..