Black screen with Slacko 5.7 and Intel Graphics
Black screen with Slacko 5.7 and Intel Graphics
When booting Puppy slacko 5.7 on an older Intel atom board (with Intel Graphics) a black screen results and the system must be rebooted. Using the Non-PAE version.
If boot parameters nox,ram supplied then xorgwizard can be run to select a driver and then xwin can be run from the command line and the system runs fine for the most part. Apparently this feature/bug was introduced into puppy slacko 5.6. Now I can live with a work around but what about anyone who might be new to linux and Puppy in particular? Might not leave the best first impression.
Any possibility this problem can be fixed for version 5.7.1?
Thanks
If boot parameters nox,ram supplied then xorgwizard can be run to select a driver and then xwin can be run from the command line and the system runs fine for the most part. Apparently this feature/bug was introduced into puppy slacko 5.6. Now I can live with a work around but what about anyone who might be new to linux and Puppy in particular? Might not leave the best first impression.
Any possibility this problem can be fixed for version 5.7.1?
Thanks
black screen
At what point does it boot to a black screen?
Do you mean the grub menu? If it is then edit menu.list and comment out with a # this line splashimage=/splash.xpm
so it will look like this
# splashimage=/splash.xpm
Do you mean the grub menu? If it is then edit menu.list and comment out with a # this line splashimage=/splash.xpm
so it will look like this
# splashimage=/splash.xpm
Slacko 5.7 release notes:
Known Issues
If you boot to blackscreen:
for intel cards:
i915.modeset=0
ATI/AMD radeon cards:
radeon.modeset=0
nvidia cards:
nouveau.modeset=0
Those strings must be placed after (example) "puppy pfix=ram i915.modeset=0" for live boot or on the kernel line of extlinux.conf, syslinux.conf, menu.lst, lilo.conf
Old nvidia N3x cards (mx440, fx5200 and some others) often do not render properly.
For those use this string in a similar fashion to above:
nouveau.noaccel=1
If you have an Intel® Brookdale graphics controller you must enable 8 MB of memory to the graphics in the BIOS of the computer.
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
YaPI(any iso installer)
When I was a kid I wanted to be older.... This is not what I expected
YaPI(any iso installer)
I too have this problem on some puppies ! And here is best method I have found !
During boot-up when you are waiting for boot 5-sec on cd 10-sec if you use grub 4 dos During the countdown Hold down function key "usually blue and labled FN " and press brightness up key "Usually arrow up " "Some models differ" You will notice the screen gets a little dimmer when you do this That's it ! This is the only way I have found to get the correct video driver loaded ! Using for example i915.modeset=0 works BUT ! Video is not as good ! Hope this works for some others Works great for me It becomes second nature once you get used to it ! same problem with Ubuntu etc. Was fixed on later kernels
This is not a puppy problem it is a kernel problem
During boot-up when you are waiting for boot 5-sec on cd 10-sec if you use grub 4 dos During the countdown Hold down function key "usually blue and labled FN " and press brightness up key "Usually arrow up " "Some models differ" You will notice the screen gets a little dimmer when you do this That's it ! This is the only way I have found to get the correct video driver loaded ! Using for example i915.modeset=0 works BUT ! Video is not as good ! Hope this works for some others Works great for me It becomes second nature once you get used to it ! same problem with Ubuntu etc. Was fixed on later kernels
This is not a puppy problem it is a kernel problem
[color=red]Anyone can build a fast processor. The trick is to build a fast system. (Seymour Cray)[/color] :wink:
Perhaps I did not identify the issue well enough
Perhaps I did not identify the issue well enough.
Yes using boot parameters: puppy pfix=ram i915.modeset=0
works as expected and I do not mind adding boot parameters.
However, I was trying to provide a perspective of a new user, who might not be used to adding boot parameters. I realize that the kernel might have changed from Puppy 5.5 to Puppy 5.7, but is there a way setup can be made easier for new users so that they do not have to specify command line arguments?
From the perspective of someone used to running Puppy 5.5 and earlier, this issue appears to be a bug (something has changed unexpectedly). An old XP machine can usually run Puppy. Making Puppy easier for new users to run can only help in the long term.
Can anything be done to make Puppy easier to run for new users with respect to automatic display setup? Many new users probably do not want to read documentation, especially about boot parameters.
Thanks
Yes using boot parameters: puppy pfix=ram i915.modeset=0
works as expected and I do not mind adding boot parameters.
However, I was trying to provide a perspective of a new user, who might not be used to adding boot parameters. I realize that the kernel might have changed from Puppy 5.5 to Puppy 5.7, but is there a way setup can be made easier for new users so that they do not have to specify command line arguments?
From the perspective of someone used to running Puppy 5.5 and earlier, this issue appears to be a bug (something has changed unexpectedly). An old XP machine can usually run Puppy. Making Puppy easier for new users to run can only help in the long term.
Can anything be done to make Puppy easier to run for new users with respect to automatic display setup? Many new users probably do not want to read documentation, especially about boot parameters.
Thanks
@rb4linux
I totally agree with you ! Especially about having to read documentation
I am curious though did my method work for you ?
you should see a big diff in glx gears and games
I have searched far and wide for a better solution with no avail
If we are to attempt to fix this issue we need to know what works best wouldn't you agree ?
I totally agree with you ! Especially about having to read documentation
I am curious though did my method work for you ?
you should see a big diff in glx gears and games
I have searched far and wide for a better solution with no avail
If we are to attempt to fix this issue we need to know what works best wouldn't you agree ?
[color=red]Anyone can build a fast processor. The trick is to build a fast system. (Seymour Cray)[/color] :wink:
More info on Intel Graphics
@partsman
I have an old 101-style keyboard so the function key you were talking about could not be found on my keyboard.
I wonder if you are using a laptop.
Brightness does not seem to be an issue with this old PC/monitor.
A couple of things that might be of help to you (and you will have to do more research) might the kernel parameters
i915.invert_brightness=1 (default is 0)
video.brightness_switch_enabled=0 (default is 1)
or some other parameter
kernel.org/doc/Documentation/kernel-parameters.txt
looks to be somewhat aged.
If you could find a kernel param it might be useful to other people.
I have an old 101-style keyboard so the function key you were talking about could not be found on my keyboard.
I wonder if you are using a laptop.
Brightness does not seem to be an issue with this old PC/monitor.
A couple of things that might be of help to you (and you will have to do more research) might the kernel parameters
i915.invert_brightness=1 (default is 0)
video.brightness_switch_enabled=0 (default is 1)
or some other parameter
kernel.org/doc/Documentation/kernel-parameters.txt
looks to be somewhat aged.
If you could find a kernel param it might be useful to other people.
Hello rb4linux
If i knew what was happening when i "Hold function & Press brightness up" at grub menu . Maybe it could be dealt with on a puppy level insted of a kernel level
Ya know what i am saying
The box i am using is a
http://www.google.com/url?sa=t&rct=j&q= ... Ww&cad=rja
Running Racy 5.5 & Slacko 5.6
May I ask what kind of box you are using ?
Also yes i have tried numerous kernel parameters with no avail
Using my method here is my video info :
Resolution = 1366x768
Xorg 1.12.4
Vendor = Tungsten Graphics , inc
Renderer = Mesa DRI mobile intel GM45 Express chipset x86/MMX/SSE2
Version = 2.1 mesa 8.0.4
Direct Rendering = Yes
That is with my method
Now if use i915.modeset=o
It loads a diff driver
It works but not near as well
Example : neverball game plays super nice ! smooth ! perfect ! if i use "Hold function & Press brightness up" at grub menu"
If i use : i915.modeset=o neverball game is choppy almost unplayable
I will continue to try and find an a solution
I am sorry i didnt think of thatI have an old 101-style keyboard so the function key you were talking about could not be found on my keyboard.
If i knew what was happening when i "Hold function & Press brightness up" at grub menu . Maybe it could be dealt with on a puppy level insted of a kernel level
Ya know what i am saying
The box i am using is a
http://www.google.com/url?sa=t&rct=j&q= ... Ww&cad=rja
Running Racy 5.5 & Slacko 5.6
May I ask what kind of box you are using ?
Also yes i have tried numerous kernel parameters with no avail
Using my method here is my video info :
Resolution = 1366x768
Xorg 1.12.4
Vendor = Tungsten Graphics , inc
Renderer = Mesa DRI mobile intel GM45 Express chipset x86/MMX/SSE2
Version = 2.1 mesa 8.0.4
Direct Rendering = Yes
That is with my method
Now if use i915.modeset=o
It loads a diff driver
It works but not near as well
Example : neverball game plays super nice ! smooth ! perfect ! if i use "Hold function & Press brightness up" at grub menu"
If i use : i915.modeset=o neverball game is choppy almost unplayable
I will continue to try and find an a solution
[color=red]Anyone can build a fast processor. The trick is to build a fast system. (Seymour Cray)[/color] :wink:
Set intel brightness
This should help avoid key presses on start - unzip & put in /root/Startup & reboot. If not bright enough, in line 5, change 3 to 4 & restart X. Intel only. Works under Slacko 5.7.0 on an Acer Aspire V5-132, which requires the modesetting driver.
- Attachments
-
- setibklt.zip
- (292 Bytes) Downloaded 306 times
Last edited by ozsouth on Wed 04 Jun 2014, 00:02, edited 1 time in total.
Hello ozsouth
Thanks for the reply
Yes this works in Slacko 5.7
My only problem with it is if i drop-out to command prompt I cannot see
anything
In other words what if for some reason X fails to start the user cannot see to run Xorgwizard etc.
This is definitely a step in the right direction though
Very good job
Thank you
Sorry for the late reply
Thanks for the reply
Yes this works in Slacko 5.7
My only problem with it is if i drop-out to command prompt I cannot see
anything
In other words what if for some reason X fails to start the user cannot see to run Xorgwizard etc.
This is definitely a step in the right direction though
Very good job
Thank you
Sorry for the late reply
[color=red]Anyone can build a fast processor. The trick is to build a fast system. (Seymour Cray)[/color] :wink: