First of all, thanks a lot for the great job. Puppy is so fast, it's amazing! After testing the regular Puppy Linux, I've chosen to full-install the puplet Browser Linux 360 (based on Puppy Linux 4.3.1 / kernel 2.6.30.5 with Firefox 3.6.0) since I'm using my laptop for Internet/streaming/online work only. I love it!

My issue is that Puppy doesn't boot; after GRUB, the computer stucks at the first step ("Starting up..."). I've tested other Linux distros in the past (Ubuntu, Xubuntu, Fedora, TinyMe, Slax, Tiny Core, Sabayon), and from what I remember, the problem pertains to the ACPI layer. I looked up on the Forum and tried different things. I am a newbie so most of these might not be related to my problem at all (I gave it a try when the issue looked similar ):
- noapic
- nolapic
- modprobe apm in the rc.local file
- nopcmcia
- acpi=force
- acpi=strict
None of them worked. I used "debug" to get more details, and here is what I get:

Thank you for the quick answer
I was probably not very clear, but I already tried acpi=force. After a search on the Forum, I tried the following boot options, and they didn't help:
- noapic
- nolapic
- modprobe apm in the rc.local file
- nopcmcia
- acpi=force
- acpi=strict

In all of these cases, the computer doesn't boot and stops at "Starting up...". I hope the "debug" option can give you more details on where it actually stops (see my first message). The only way I manage to boot is using acpi=off, but then I have the "system halted" thing. Any idea?

OK, so maybe we weren't exactly on the same
Yes, I am currently booting all the way to the desktop using acpi=off.

I have this option in the menu.lst file so I don't have to edit the boot command every time I start up my computer, but there is no difference in having the option written in the menu.lst or editing the boot command manually in GRUB at start up. I tried the 5 different options above in the boot command, each by itself (without acpi=off), and none of them managed to boot. I also tried noapic nolapic together -- same (absence of) result, and the "modprobe apm" in rc.local, idem.

Maybe some sort of combination will work, but which one? Or something completely different? I don't know which part of the ACPI is not working properly. If I could identify it, it might be possible to load the rest of the ACPI except the problematic part -- but I don't know how to do that. Or if somebody knows how to load just the small part that allows the system to shutdown (and let the rest of the ACPI R.I.P.), that will solve the issue too

I would try an earlier puppy, 4.1.2 would be good; and not one
of the puplets or derivatives.
With your system you won't notice any difference in speed
between the stripped down version you have now and a larger
one anyway.

I haven't been able to access the forum for few days, and in the meantime I've found a solution:

Boot with pci=noacpi option.

That's not the same than acpi=off/noacpi/nolapic; the computer boots fine, ACPI is partially loaded, and the system switches off completely. David45, I might try your solution too, but I'm hesitant to fix something that's working (for now)... I don't know if my solution would work on another computer, so it's good to have several options for the same problem (which seems to originate from hardware variously compatible with the ACPI layer of the Linux kernel).

Just edited the file with pci=noacpi option, i could boot via cd with the acpi=off, and reenter everything, like xorg config each time...

Your post worked. edited /boot/grub/menu.lst with ^no pci=noacpi!

The notebook, Dell Inspiron 2650 128ram, is my 80 year old father's, so i didn't want him to have to boot via cd.

Now my slight gripe is at the grub prompt i have to hit enter, to boot off hd.

Anyway thanks again Max2

----
Max2 Posted: Sun 14 Feb 2010, 10:12 Post subject:

I haven't been able to access the forum for few days, and in the meantime I've found a solution:

Boot with pci=noacpi option.

That's not the same than acpi=off/noacpi/nolapic; the computer boots fine, ACPI is partially loaded, and the system switches off completely. David45, I might try your solution too, but I'm hesitant to fix something that's working (for now)... I don't know if my solution would work on another computer, so it's good to have several options for the same problem (which seems to originate from hardware variously compatible with the ACPI layer of the Linux kernel).

Hi folks, I´m really a newcomer on Linux and even less an expert and swell I know that the issue is solved but it might be interesting to some other people like me.
I had a little hard time for a couple of days.
At first I had this start-problem from cd.
When the first Puppy-picture comes there is the choice to select F2 or F3.
After some reading and a couple of trials I typed Puppy pci=noacpi which is not in the list under F2 and I got it running from cd.
The I installed it on HD and it kept hanging on start up.
So I prolonged the kernel-line in mnt/sda.../boot/grub/menu.1st like
...sda2 pmedia=atahd pci=noacpi and WOW! it started.
Then I had this well-known shut-down problem.
Again a lot of reading and again I tried to prolong the mentioned kernel-line like
...sda2 pmedia=atahd pci=noacpi acpi=force and it´s shutting down perfectly.
Apart all that it´s a nice OS which boots in less than 45secs and runs fast like a rabbit, not like me former XP.
Thanks to You all! Jeeco

You cannot post new topics in this forumYou cannot reply to topics in this forumYou cannot edit your posts in this forumYou cannot delete your posts in this forumYou cannot vote in polls in this forumYou cannot attach files in this forumYou can download files in this forum