I've recently purchased a Toshiba Satellite L505D-GS6000:
specs:
AMD Turion II Dual-Core Mobile M500 2.20 GHz
4.00 GB RAM
64-bit OS
Windows 7 Home Premium

and i want to install Ubuntu 9.10 (or Debian 5.0 or even Fedora 12 at this point

Here's the problem...

Anytime I attempt to boot from a LiveCD or DVD or even a Live USB flash drive (I've tried using both 64 and 32-bit versions of each distro {even openSUSE & gentoo as well}), it takes approx 10 - 15 minutes to load (if it loads at all), and then once it does load, the keyboard and mouse pad don't do anything, the cap & number lock lights won't even come on.

I know that the Live CD/DVD/USB's work just fine as i have used these to install Linux on quite a few computers and laptops.

And i have no problem loading Hiren's BootCD or my windows 7 install disk...

After many hours of trial, error and google, the only thing that i can guess is maybe it has something to do with the AMD dual core CPU...

Any help anyone can offer me would be greatly appreciated...

I doubt that it has anything to do with your CPU. Especially if it seems to work fine with Win 7. It probably has something to do with booting from non-HD media. You might want to have a look into your BIOS settings. Also, if you have a bootable Windows DVD, give that a try and see if anything changes.

Cheers, Lou

I checked my bios settings, i've tried putting CD/DVD and USB to boot first, but still no dice. i snapped a pic of the message i get right before it finally does load (when the keyboard and mouse won't work). and that is HERE it seems to have an error code, but i can't make heads or tales of it...

my photo is a little fuzzy so i also typed out what it says...

[ 317.273074] usplash:300 freeing invalid memtype ffffffffe0000000-ffffffffe1000000
udevd[134]: worker [1037] unexpectedly returned with status 0x0100

udevd[134]: worker [1037] faileded whiles handling '/devices/LNXSYSTM:00/device:00/PNP0A08:00/device:06/device:07'

* Setting preliminary keymap...
(381.617086] shpchp 0000:00:01.0: Cannot reserve MMIO region
* Starting early crypto disks...
* Starting remaining crypto disks...
* Starting Kernel Oops catching service kerneloops
* Speech-dispatcher configured for user sessions
* Starting Common Unix Printing System: cupsd
* PulseAudio configured for per-user sessions
* Enabling additional executable binary formats binfmt-support
* Checking battery state...
...done.
_



any takers...?

I'm not sure, but it looks like it makes it as far as udev. Perhaps it's missing some module for your hardware? For some new computers the modules may not all have made it into the kernel yet.

When I have trouble booting other distros, I usually try Arch. I've had the best luck with that even on some really old computers.

No luck with Dreamlinux or Arch, some sort of ACPI Error with both of them...

ACPI Error (psargs-0359): [RS F] Namespace lookup failure, AE_NOT_FOUND
ACPI Error (psparse-0537): Method parse/execution failed [\_GPE._L07] (Node ffff
88010f830700), AE_NOT_FOUND
ACPI Exception (evgpe-0568): AE_NOT_FOUND, while evaluating GPE method [_L07] [2
0090320]

And this error message just keeps looping... And this is from the ArchLinux bootCD

This error message is similar to what i've gotten while trying to boot a couple other distro's live CD/DVD's

Does anyone have a clue as to what this could mean...Thanks in advanced

I read somewhere that there is a way to load (or maybe install ubuntu with the ACPI kernel turned off... Can anyone confirm this and if so can someone point me in the right direction...

Thanks

Hit tab or whatever is called for and add then boot.

I'm sorry, forgive my lack of knowledge but could you please be more specific... At what point in the boot process would i enter the above command?

Please if possible break it down step by step for me...

...anyone?

Those options should be appended to the kernel line in the bootloader. When the GRUB menu comes up, you can press "e" to edit that menu option and "e" again on the kernel line. Add those commands to the end of the kernel line and press "b" to boot.

I know some distros don't use grub, but they should still have an advanced boot option. I've had similar trouble with other laptops, especially ones where the battery doesn't charge. There is also an option in the BIOS of some laptops that cause them to shut down when power is low. I've found that when that is on, it can cause a laptop to shut down during boot (either during udev or ACPI). I hope that works for you.

Commands (boot arguments/options) such as that given in post #7 are used on the kernel boot line. The kernel boot line can be adjusted right in between:

"when you turn the machine on and get a GRUB, LILO, or Ubuntu Boot Menu"

here!

"now you've selected an item to boot"

So, assuming Ubuntu here: after turning on the machine with the Ubuntu CD in the drive, you are presented a menu with approx 5 or 6 items on it, such as "boot ubuntu" or "install ubuntu" etc... At least one menu item should be something like "add boot parameters" or something like that. Select that option, and you will be shown a long string of commands and options, beginning with a boot: prompt. That's your kernel boot line.

Using your cursor arrow keys (or perhaps the END key) go to the end of that line, hit SPACE, and add acpi=off noapic nolapic and/or whichever of these options you think you need. Then hit ENTER to boot (I think you hit enter -- it's been a while since I booted an Ubuntu, so you might need to hit ENTER and then select boot.)

A suggestion further:

1) you might want to also add the "nosplash" option, or select the "text" boot option (maybe it's called "safe VGA mode?), so you boot with a plain text console instead of the graphical boot screen, just in case that's causing a problem too; this eliminates just one potential unnecessary thing from the boot sequence.

2) also, I noticed in one of your earlier posts, when trying to boot some OS, you got some "udevd" errors. You can maybe get around this, at least to get booted the first time, by using the "noudev" option as well.

Good luck!!

Sasha

...okay, the update...

First off, thank you all for your responses... they all helped me solve the issue with loading up LiveCD/DVD/USB's...

BUT.....

now that i have the LiveCD's loaded and begin the installs...


Ubuntu 9.10 installs but when it loads up i have the same problem with the keyboard and mouse not working...
*i've read that this might be caused by the USB drivers not loading in time (and the kb & mouse are USB controlled on my laptop)

Debian 5.0 i can't get past the install it can't detect my cd-rom (even though it uses the cd-rom to get to this point)

Arch will install, but it won't detect my network adapters (wired or wireless) so there's no way to install .xorg...

so, this is where i am now... past where i was but still stuck...

once again,

any takers...

MODS: i'm not sure if this should still be posted under this title or moved to a new thread. please advise

STOP THE PRESSES!!!

on a whim i popped in an old Fedora 11 i686 LiveCD... booted up... same error... rebooted with "acpi=off" it loaded right up with both the mouse and keyboard working just fine... so i chose to install just for shits and giggles and lo and behold it installed without error and loaded up just fine on re-boot (well now i have to resolve the issue between fedora and my Realtek 8191SE wifi card... but i think that'll be for another thread).

not sure why an i686 install worked where all AMD64 installs failed considering there's an AMD64 processor in my lappy... oh well, i wanted a Debian based Gnome OS and fedora fits the bill...

now since i know that it works, i'm going to DL fedora 12 and hope it does the same...

also i'm going to shoot for the i686 version of debian 5.0 (once again just for shits and giggles) just to see if it works.

Special thanks to:
LouRobytes
kainosnous
Mr-Bisquit
GrapefruiTgirl

you all are AWESOME

...

I seem to recall from when I downloaded Linux Mint 8 and Sabayon Linux 5 that there were AMD-specific versions available. Is it possible that you are using an x86 version and not the AMD-specific one? Check this out; it may the problem.

32bit always has better hardware compatibility than 64bit(in my experience)... You could probably get any of those distros you mentioned, working w/ their respective 32bit versions.

IGF