I have created a puppy linux bootup CD using UNETLOOPIN and the US lupo version of puppy. I have managed to get it to boot to the splash screen and it loads the drivers and files. It hangs at the input of the pc speakers device. At this point I have to turn the machine off and start over. Is there a way to deactivate this and actually reach the puppy desktop? I could not get a usb drive to work. I have found that if I choose a fdd <flash drive> that it brings up a one line description of linux, and then hangs.

I would really appreciate some help, I am trying to rescue my files off of a laptop before doing a complete factory reset. (Serious bootup issues)

Thanks all.Last edited by Rahvin on Wed 10 Oct 2012, 20:52; edited 1 time in total

and yes you got it right... I just guessed at the title since today is the first time I have used it or heard of it. (same for puppy but I absolutely love the idea of a ram only OS for troubleshooting and disk recovery)... it does hang at the same place all the time, the pc speaker device manager input line. (I can get the exact line for you if you need it)...

I am trying to recover a Toshiba Satellite L505 running windows 7 32 bit.
I didn't leave it for an extensive amount of time, how long is too long....

also note that I have used the WINDOWS MEMORY DIAGNOSTICS TOOL and it seems to have hanged as well... it has been on the same line for about 30 minutes... How long is too long?

Thanks for your help
(oh any advice on the jump drive deal? - I would much prefer using it instead of a CD)...

I have a Satellite L505-GS6000
I coudl not find any links to download the falcon bootup

I think the majority of my problems occurred when the owner let windows try to update itself without plugging the laptop in. Battery died in the middle of the update and probably left file handles open all over the place.

can't boot in normal mode
can't boot in safe mode
They didn't make a system restore disk
I will restore it to factory defaults but would like to try to save their files

can't get puppy to work, hangs on the pc speaker input line, never reaches the deskop.

Can't get puppy to boot from the usb drive at all, I checked the files on the drive and they are laid out in folders, there is a boot record on there, so the .iso write to the CD-R went off right, just can't get it to load

May want to try a search, in the support section, of the computer manufactures website, for help with a broken Windows update._________________I have found, in trying to help people, that the things they do not tell you, are usually the clue to solving the problem.
When I was a kid I wanted to be older.... This is not what I expected

Posted: Wed 10 Oct 2012, 10:38 Post subject:
RAM test passedSubject description: Still hanging on same line every time I boot puppy

Hello and thank you for helping me.

I tried the commnad line puppy pfix=nocopy but it didnt' change anything.

My puppy boot hangs at the same time every time.

the line:

input: PC Speaker as /devices/platform/pcspkr/input/input3

(It should be noted that puppy loaded fine on a second laptop that don't have HDD issues....)

I don't really need a pc speaker for the recovery operation that I am working on, is there a way to disable it? or skip this load line? Do you know what is going on here that is causing the boot to stop?

I think it is worth confirming the integrity of that first CD in a couple of other PCs as well - just in case there was a minor problem with the download or burn. Does the CD load perfectly in other systems?

(It is possible to have a data corruption on the CD that affects only one small part of the system performance...)

The pcspkr.ko kernel-driver-module is not essentially necessary . That is a

CONFIG_INPUT_PCSPKR:
Say Y here if you want the standard PC Speaker to be used for
bells and whistles.
If unsure, say Y.
To compile this driver as a module, choose M here: the
module will be called pcspkr.

from the kernel help .

There seems not to be a kernel-parameter for preventing the loading of the pcskr module .
Puppy has unfortunately no "pmodule=pcspkr:blacklist;radeon=param1:1,param2=0xb" boot parameter to pass to /etc/rc.d/rc.sysinit .
Blacklisting can only be done after at least booted to the prompt - either by editing /etc/rc.d/MODULESCONFIG or running /usr/sbin/bootmanager while in X . Newer Puppies should be able to honor the blacklist entries in /etc/modules.d/* files .

Lupu uses a script named /sbin/pup_event_modprobe_protect that does a cat for a pipe . Here it might be that the cat is waiting for something and thus stands everything . That script was dropped in later Woof but playdays had his own Woof after a while .

Also possible is a mismatch with acpi related things . Since the module loading happens in parallel to the boot process by triggering udevd it might be that files in /etc/init.d/ already are starting services that claim the /proc/acpi/event file for example ._________________«Give me GUI or Death» -- I give you [[Xx]term[inal]] [[Cc]on[s][ole]] .
Macpup user since 2010 on full installations.
People who want problems with Puppy boot frugal

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