Puppy turns dark when booting
Puppy turns dark when booting
I have downloaded Puppy 5.2.5 and burned it to a DVD-R.
It boots from the DVD-R without problem, except this:
- when "loading kernel modules" the screen suddenly turns dark / dim, as if as least 50% of the light is turned off.
When boot is finished the screen remains dark / dim, making it difficult to see and really impossible to use.
Anyone experienced something like this?
This occurs only with Puppy 5.2.5.
Not tried any earlier Puppy.
It boots from the DVD-R without problem, except this:
- when "loading kernel modules" the screen suddenly turns dark / dim, as if as least 50% of the light is turned off.
When boot is finished the screen remains dark / dim, making it difficult to see and really impossible to use.
Anyone experienced something like this?
This occurs only with Puppy 5.2.5.
Not tried any earlier Puppy.
Puppy of that series seemed to have problems with some video cards.
You could try passing a kernel parameter of "pfix=nox" when you boot and then at the prompt type "xorgwizard" and follow the steps to see if that will help.
Also, if you tell us more about your PC, model, ram, video card model if known, it will give us more information to help you.
In the mean time, you might want to try a version that was not based on Ubuntu Lucid.
You could try passing a kernel parameter of "pfix=nox" when you boot and then at the prompt type "xorgwizard" and follow the steps to see if that will help.
Also, if you tell us more about your PC, model, ram, video card model if known, it will give us more information to help you.
In the mean time, you might want to try a version that was not based on Ubuntu Lucid.
Normally the pre-X should not dim like that (Xorg can play some mean tricks like dark gray on black or blue on black and that is kind of hard to deal with if it happens). If your desktop is unuseably dim once you get to it, it's possible to use setup..xvidtune if all else fails (but the warnings are there for a reason).
Rewritable media (*-rw discs) are actually a good choice for liveCD boot, you can always blank and reburn another pup if the one you got is not working for you. Recent wary 512 has an Xvesa option so you can bypass Xorg altogether if your system isn't happy with it.
Like 8-bit says, more info helps us help you.
Welcome to the plmf )
Rewritable media (*-rw discs) are actually a good choice for liveCD boot, you can always blank and reburn another pup if the one you got is not working for you. Recent wary 512 has an Xvesa option so you can bypass Xorg altogether if your system isn't happy with it.
Like 8-bit says, more info helps us help you.
Welcome to the plmf )
Nothing has helped.
Created a startup-disc for Wary 5.1.2.
Exactly the same dimming when "loading kernel modules" during the boot.
This is my PC, witg 2gb ram (can say no more).
http://support.acer.com/acerpanam/noteb ... Gsp2.shtml
The current OS is Linux Mint, no dual boot with Windows, only Linux Mint 9 Isadora.
Adding some more info about USBs with Linux OS-systems:
Peppermint 2 - normal
Mint 11 Katya - normal
Kubuntu 10.04 - normal
Kubuntu 11 - dimming
Puppy 4.2 - normal (but cannot set up to the wireless)
Puppy 5.2.5 - dimming
Puppy Wary 5.1.2 - dimming
Xubuntu - always been dimming, no matter which one
Fedora 12_love - normal
OpenSuse 11.1 - normal
Linux Mint 9 (the current OS) - normal
Windows XP Pro (the one that came with it) - normal
Created a startup-disc for Wary 5.1.2.
Exactly the same dimming when "loading kernel modules" during the boot.
This is my PC, witg 2gb ram (can say no more).
http://support.acer.com/acerpanam/noteb ... Gsp2.shtml
The current OS is Linux Mint, no dual boot with Windows, only Linux Mint 9 Isadora.
Adding some more info about USBs with Linux OS-systems:
Peppermint 2 - normal
Mint 11 Katya - normal
Kubuntu 10.04 - normal
Kubuntu 11 - dimming
Puppy 4.2 - normal (but cannot set up to the wireless)
Puppy 5.2.5 - dimming
Puppy Wary 5.1.2 - dimming
Xubuntu - always been dimming, no matter which one
Fedora 12_love - normal
OpenSuse 11.1 - normal
Linux Mint 9 (the current OS) - normal
Windows XP Pro (the one that came with it) - normal
Apparently /etc/rc.d/rc.sysinit starting udevd triggering /sbin/pup_event_backend_modprobe or /sbin/pup_event_backend_modprobe_protect
loaded a driver that produces this behavior .
The log files are located in the /tmp directory and in frugal installations additionally in the /initrd/tmp folder .
/tmp/bootsysinit.log
/tmp/bootkernel.log
Linux agpgart interface v0.103
agpgart-intel 0000:00:00.0: Intel 845G Chipset
agpgart-intel 0000:00:00.0: enabling device (0000 -> 0002)
agpgart-intel 0000:00:00.0: AGP aperture is 256M @ 0xe0000000
/tmp/pup_event_module_devpath_log
MODULE=intel_agp DEVPATH=/devices/pci0000:00/0000:00:00.0
/tmp/udevtrace.log
add_agpgart_module___
add_0000:00:1e.0_pci_0x8086_0x244e_pci:v00008086d0000244Esv00000000sd00000000bc06sc04i00
add_0000:00:01.0_pci_0x8086_0x1a31_pci:v00008086d00001A31sv00000000sd00000000bc06sc04i00
add_0000:00:00.0_pci_0x8086_0x1a30_pci:v00008086d00001A30sv00008086sd00001A30bc06sc00i00
add_agpgart-intel_drivers___
add_agpgart_misc___
add_intel_agp_module___
add_0000:01:00.0_pci_0x10de_0x0182_pci:v000010DEd00000182sv0000107Dsd00002922bc03sc00i00
add_vesafb.0_platform___platform:vesafb
*****
and the commandshows
00:00.0 060000 8086:1A30 <agpgart-intel>
... the graphic relevant driver for me .
Some ACPI , extra-laptop , LED or other kernel drivers may have an energy saving default backlight value , which can range from 0-8 or 0-15 depending on the driver .may show something .
loaded a driver that produces this behavior .
The log files are located in the /tmp directory and in frugal installations additionally in the /initrd/tmp folder .
/tmp/bootsysinit.log
/tmp/bootkernel.log
Linux agpgart interface v0.103
agpgart-intel 0000:00:00.0: Intel 845G Chipset
agpgart-intel 0000:00:00.0: enabling device (0000 -> 0002)
agpgart-intel 0000:00:00.0: AGP aperture is 256M @ 0xe0000000
/tmp/pup_event_module_devpath_log
MODULE=intel_agp DEVPATH=/devices/pci0000:00/0000:00:00.0
/tmp/udevtrace.log
add_agpgart_module___
add_0000:00:1e.0_pci_0x8086_0x244e_pci:v00008086d0000244Esv00000000sd00000000bc06sc04i00
add_0000:00:01.0_pci_0x8086_0x1a31_pci:v00008086d00001A31sv00000000sd00000000bc06sc04i00
add_0000:00:00.0_pci_0x8086_0x1a30_pci:v00008086d00001A30sv00008086sd00001A30bc06sc00i00
add_agpgart-intel_drivers___
add_agpgart_misc___
add_intel_agp_module___
add_0000:01:00.0_pci_0x10de_0x0182_pci:v000010DEd00000182sv0000107Dsd00002922bc03sc00i00
add_vesafb.0_platform___platform:vesafb
*****
and the command
Code: Select all
elspci -l
00:00.0 060000 8086:1A30 <agpgart-intel>
... the graphic relevant driver for me .
Some ACPI , extra-laptop , LED or other kernel drivers may have an energy saving default backlight value , which can range from 0-8 or 0-15 depending on the driver .
Code: Select all
find /sys -type f -name "backlight*" -exec cat '{}'\;
Do you want help with this? You need to provide some details. Like what model printer you have and what driver package (if any) you have installed.ove wrote:But, not at all acceptable as for setting up a printer. It's almost as reading the Bible in ancient greek...with no space between the words...
- Béèm
- Posts: 11763
- Joined: Wed 22 Nov 2006, 00:47
- Location: Brussels IBM Thinkpad R40, 256MB, 20GB, WiFi ipw2100. Frugal Lin'N'Win
ove, for your display issue in 525:
When running xorgwizard, don't XXxYYx24 resolution, but XXxYYx16
When running xorgwizard, don't XXxYYx24 resolution, but XXxYYx16
Time savers:
Find packages in a snap and install using Puppy Package Manager (Menu).
[url=http://puppylinux.org/wikka/HomePage]Consult Wikka[/url]
Use peppyy's [url=http://wellminded.com/puppy/pupsearch.html]puppysearch[/url]
Find packages in a snap and install using Puppy Package Manager (Menu).
[url=http://puppylinux.org/wikka/HomePage]Consult Wikka[/url]
Use peppyy's [url=http://wellminded.com/puppy/pupsearch.html]puppysearch[/url]
When you installed the printer, you must have picked some model from the list. What did you choose?ove wrote:No driver package has been installed. Done absolutely nothing. Priner: HP Photosmart 2575 All-in-one
What you really need is the hplip_print-3.11.10.pet driver package from here. It lists the Photosmart 2570 Series.
This is all I get.rcrsn51 wrote:After you select the Administration tab and click the Add Printer button, you will see a list of printing devices. Is your Photosmart not on the list?ove wrote:Add printer...yes... so what - start guessing?
Clicking on any of the buttons does not get me any further.
There is nothing behind any of them to help me further on, sorry to say.
Add Printer
Local Printers: SCSI Printer
pdf writer (PDF)
Discovered Network Printers:
Other Network Printers: LPD/LPR Host or Printer
Internet Printing Protocol (http)
AppSocket/HP JetDirect
Internet Printing Protocol (ipp)
Windows Printer using smbclient
Backend Error Handler
Then your computer is having a problem with USB hardware detection. Turn the printer off, turn it back on and run CUPS again.ove wrote:This is all I get.
Also, type the command
Code: Select all
sane-find-scanner
No.rcrsn51 wrote:Then your computer is having a problem with USB hardware detection. Turn the printer off, turn it back on and run CUPS again.ove wrote:This is all I get.
Also, type the commandDoes it detect the scanner part of your Photosmart?Code: Select all
sane-find-scanner
No SCSI scanners found.
No USB scanners found.