Shutdown failing - modprobe [SOLVED]
Well now, there's gotta be sumpthin bigger behind this than resurrecting a three year old thread.
Is this install on an ext2 file system? This alone should say: mount
I've got a usb install I can try this on but you should look too.
Also, you went from 5.28 to 5.29 at one point.. <also known as> an in place upgrade, correct?
Boot your 5.29 disk live: puppy pfix=ram and hit the install icon.
As I'm sure you can cancel at an appropriate time, does it ask if you'd like to upgrade?
I'm not positive but recall this type install keeps your current setup, replacing only system files.
If something got corrupted, and it sure sounds like it.. this may be one way to recover.
Try'n make sure you answer all questions.
Is this install on an ext2 file system? This alone should say: mount
I've got a usb install I can try this on but you should look too.
Also, you went from 5.28 to 5.29 at one point.. <also known as> an in place upgrade, correct?
Boot your 5.29 disk live: puppy pfix=ram and hit the install icon.
As I'm sure you can cancel at an appropriate time, does it ask if you'd like to upgrade?
I'm not positive but recall this type install keeps your current setup, replacing only system files.
If something got corrupted, and it sure sounds like it.. this may be one way to recover.
Try'n make sure you answer all questions.
Last edited by Semme on Sun 03 Mar 2013, 21:03, edited 1 time in total.
Semme wrote:Well now, there's gotta be sumpthin bigger behind this than resurrecting a three year old thread.
Is this install on an ext2 file system? This alone should say: mount
Code: Select all
sh-4.1# mount
rootfs on / type rootfs (rw)
/dev/root on / type ext3 (rw,relatime,errors=continue,barrier=0,data=writeback)
none on /proc type proc (rw,relatime)
none on /dev/pts type devpts (rw,relatime,gid=2,mode=620)
none on /sys type sysfs (rw,relatime)
shmfs on /dev/shm type tmpfs (rw,relatime,size=244152k)
none on /proc/bus/usb type usbfs (rw,relatime)
/dev/sda1 on /mnt/sda1 type ext3 (rw,relatime,errors=continue,barrier=0,data=writeback)
This is a full install and I do not have the install disk anymore. But I'm pretty sure it was not upgraded from 528 to 529.[/code]I've got a usb install I can try this on but you should look too.
Also, you went from 5.28 to 5.29 at one point.. <also known as> an in place upgrade, correct?
Boot your 5.29 disk live: puppy pfix=ram and hit the install icon.
As I'm sure you can cancel at an appropriate time, does it ask if you'd like to upgrade?
I'm not positive but recall this type install keeps your current setup, replacing only system files.
If something got corrupted, and it sure sounds like it.. this may be one way to recover.
Try'n make sure you answer all questions.
Buy silver, crash JPMorgan
I'm not sure what's up.. too many things wrong there. I'm leaning towards you get'n a copy.
Semme wrote:Let's see the contents of your menu.lst file. Pfind if you're unsure it's whereabouts..
Code: Select all
menu.lst produced by grub4dosconfig-v
color white/blue black/cyan white/black cyan/black
timeout 10
default 0
# Full installed Linux
title Three-Headed Dog 529 (sda1/boot)
uuid f5906585-1a70-42ca-821c-5df303cfdeb3
kernel /boot/vmlinuz root=/dev/sda1 ro
# Windows
# this entry searches Windows on the HDD and boot it up
title Windows\nBoot up Windows if installed
errorcheck off
find --set-root --ignore-floppies --ignore-cd /bootmgr
chainloader /bootmgr
find --set-root --ignore-floppies --ignore-cd /ntldr
chainloader /ntldr
find --set-root --ignore-floppies --ignore-cd /io.sys
chainloader /io.sys
errorcheck on
# Boot from Partition Boot Record
title Three-Headed Dog 529 (sda1/boot:PBR)
uuid f5906585-1a70-42ca-821c-5df303cfdeb3
chainloader +1
# additionals
title Find Grub2\nBoot up grub2 if installed
find --set-root --ignore-floppies --ignore-cd /boot/grub/core.img
kernel /boot/grub/core.img
title Grub4Dos commandline\n(for experts only)
commandline
title Reboot computer
reboot
title Halt computer
halt
Buy silver, crash JPMorgan
Before what follows, one'a these: cat /var/log/messages | grep Bug
==
If during the day you get this, reboot and at the boot prompt type: puppy acpi=off
Whether this is power related or caused by a graphics or network card, time will tell.
It goes without saying.. you'll be minding that shutdown / reboot time..
==
If during the day you get this, reboot and at the boot prompt type: puppy acpi=off
Whether this is power related or caused by a graphics or network card, time will tell.
It goes without saying.. you'll be minding that shutdown / reboot time..
Semme wrote:Before what follows, one'a these: cat /var/log/messages | grep Bug
==
Code: Select all
sh-4.1# cat /var/log/messages | grep Bug
Mar 4 15:54:38 zimmer user.notice kernel: [Firmware Bug]: ACPI: BIOS _OSI(Linux) query ignored
Mar 4 15:54:38 zimmer user.warn kernel: [Firmware Bug]: ACPI: No _BQC method, cannot determine initial brightness
Mar 4 15:54:38 zimmer user.warn kernel: [Firmware Bug]: ACPI: No _BQC method, cannot determine initial brightness
sh-4.1#
what are you talking about here?If during the day you get this, reboot and at the boot prompt type: puppy acpi=off
Buy silver, crash JPMorgan
The line in your menu.lst up top >> kernel /boot/vmlinuz root=/dev/sda1 ro
Make it look like this, then save:
We'll try this first.
Make it look like this, then save:
Code: Select all
kernel /boot/vmlinuz root=/dev/sda1 ro acpi=force
just tried this, no changeSemme wrote:The line in your menu.lst up top >> kernel /boot/vmlinuz root=/dev/sda1 ro
Make it look like this, then save:We'll try this first.Code: Select all
kernel /boot/vmlinuz root=/dev/sda1 ro acpi=force
Buy silver, crash JPMorgan
Dont know if that make a difference :
There is a 3rd acpi kernel parameter :
kernel /boot/vmlinuz root=/dev/sda1 acpi_enforce_resources=lax
I needed that to be able to load the it87.ko temperature driver on one older P4 Board from 2001 or 2003.
There is a 3rd acpi kernel parameter :
kernel /boot/vmlinuz root=/dev/sda1 acpi_enforce_resources=lax
I needed that to be able to load the it87.ko temperature driver on one older P4 Board from 2001 or 2003.
https://www.kernel.org/doc/Documentation/kernel-parameters.txt wrote:acpi_enforce_resources= [ACPI]
{ strict | lax | no }
Check for resource conflicts between native drivers
and ACPI OperationRegions (SystemIO and SystemMemory
only). IO ports and memory declared in ACPI might be
used by the ACPI subsystem in arbitrary AML code and
can interfere with legacy drivers.
strict (default): access to resources claimed by ACPI
is denied; legacy drivers trying to access reserved
resources will fail to bind to device using them.
lax: access to resources claimed by ACPI is allowed;
legacy drivers trying to access reserved resources
will bind successfully but a warning message is logged.
no: ACPI OperationRegions are not marked as reserved,
no further checks are performed.
Tried that Karlgodt, no joyKarl Godt wrote:Dont know if that make a difference :
There is a 3rd acpi kernel parameter :
kernel /boot/vmlinuz root=/dev/sda1 acpi_enforce_resources=lax
I needed that to be able to load the it87.ko temperature driver on one older P4 Board from 2001 or 2003.https://www.kernel.org/doc/Documentation/kernel-parameters.txt wrote:acpi_enforce_resources= [ACPI]
{ strict | lax | no }
Check for resource conflicts between native drivers
and ACPI OperationRegions (SystemIO and SystemMemory
only). IO ports and memory declared in ACPI might be
used by the ACPI subsystem in arbitrary AML code and
can interfere with legacy drivers.
strict (default): access to resources claimed by ACPI
is denied; legacy drivers trying to access reserved
resources will fail to bind to device using them.
lax: access to resources claimed by ACPI is allowed;
legacy drivers trying to access reserved resources
will bind successfully but a warning message is logged.
no: ACPI OperationRegions are not marked as reserved,
no further checks are performed.
Buy silver, crash JPMorgan
Can anybody see any problem with this code in /etc/inittab:
[/code]
Code: Select all
::sysinit:/etc/rc.d/rc.sysinit
tty1::respawn:/sbin/getty -n -l /bin/autologinroot 38400 tty1
tty2::respawn:/sbin/getty 38400 tty2
::shutdown:/etc/rc.d/rc.shutdown
::ctrlaltdel:/sbin/reboot
Buy silver, crash JPMorgan
No. An original inittab looks like
There had been some new adjustments while introducing minint instead of busybox init or getty in current Puppies. There had been also complaints about PUPMODE=6 on USBflash to entire partitions. BK claimed some time ago, that he fixed that. Must be on his old bkhome.org/blog/ , while actually he uses the bkhome.org/blog2/ .
Somehow i suspect that you there are changes in the software in your partition that cause all this or some files in the lost+found folder.
Code: Select all
::sysinit:/etc/rc.d/rc.sysinit
tty1::respawn:/sbin/getty -n -l /bin/autologinroot 38400 tty1
tty2::respawn:/sbin/getty 38400 tty2
tty3::respawn:/sbin/getty 38400 tty3
::ctrlaltdel:/sbin/reboot
Somehow i suspect that you there are changes in the software in your partition that cause all this or some files in the lost+found folder.
errata : it is mingetty replacing getty , not mininit.
slacko-5.3.1 inittab:
And your inittab is a inittabPREV on slacko.
slacko-5.3.1 inittab:
Code: Select all
::sysinit:/etc/rc.d/rc.sysinit
tty1::respawn:/sbin/mingetty --autologin root tty1
tty2::respawn:/sbin/getty 38400 tty2
tty3::respawn:/sbin/getty 38400 tty3
::ctrlaltdel:/sbin/reboot