Okay I will try to include that. Intel N2600/2800 uses intel GMA 3600 but it works through fbdev driver?Volhout wrote:Dear mistfire,
Is it possible for you to include 'modesetting_drv.la' or 'modesetting_drv.so' into Xslacko Slim.
This is the video driver needed for Intel Atom N2600/2800 video.
It is located (in previous XSlacko's) in /usr/lib/xorg/modules/drivers
Maybe you can use the one from R54 (slightly different kernel 4.12.2 versus 4.12.8 in R58).
Dear Regards.
Volhout
X-Slacko Slim 4.4r49 (unique, stable, and flexible)
Re: video driver
New X-Slacko Slim iteration released
Changes:
* More user friendly error-handling in initrd
* Some bugfix
Download: https://drive.google.com/open?id=0B2FRk ... XNuWWI4ajg
MD5 Checksum:7d5ddfa7f1626d464dafcc0a8fc36c1b
Changes:
* More user friendly error-handling in initrd
* Some bugfix
Download: https://drive.google.com/open?id=0B2FRk ... XNuWWI4ajg
MD5 Checksum:7d5ddfa7f1626d464dafcc0a8fc36c1b
Worst yet!
Sorry.
More: No idea where it all goes wrong, but r59 DOES contain xslacko_4.2/puppy_xslacko_4.2.sfs and
xslacko_4.2/zdrv_xslacko_4.2.sfs
None of the comments have any point if it doesn't run further than the opening boot screen.White oblong - FATAL ERROR.
pup...... .sfs not found
Select SAVE FILES for diagnostic purposes (there aren't any - didn't run)
...
GO TO PROMPT for advanced purposes (no point!)
...
...
0. Save temp files (there aren't any)
1. Go to prompt
2.Reboot! (why? in desperation!)
Sorry.
More: No idea where it all goes wrong, but r59 DOES contain xslacko_4.2/puppy_xslacko_4.2.sfs and
xslacko_4.2/zdrv_xslacko_4.2.sfs
Misunderstanding, misty. That message shows BEFORE anything starts up. There's nothing to save, there's no partition!
This version doesn't start on any machine, 32 or 64bit, radeon or nV, no combination of HW. There's something radically wrong because r54 works just fine on every machine and so does r57 modified according your instructions.
This version doesn't start on any machine, 32 or 64bit, radeon or nV, no combination of HW. There's something radically wrong because r54 works just fine on every machine and so does r57 modified according your instructions.
@Sage Did you boot that on a real machine? If yes, then If there is no partition to save just plugged a usb flash drive before selecting "save temp file" in fatal error dialog in order to get that temp files.
Upon booting, did you see these messages before fatal error dialog shown?
Loading modules to access drives...
Searching for Puppy Files...
Upon booting, did you see these messages before fatal error dialog shown?
Loading modules to access drives...
Searching for Puppy Files...
Fatal error message dialog explained.
This dialog is the unique feature of X-Slacko Slim's initrd. Its more user friendly than the vanilla one. The user gives options what to do next.
Options:
1. Save Temp Files - This will save the contents of /tmp of initrd to a disk (When puppy sfs is sucessfully loaded and perform switch root, it moves to /initrd/tmp). the /tmp folder of the initrd contains log files created by init script. Which is useful for troubleshooting. When the user choose this option. It shows list of storage device and the user must choose where to save the temp files in tarball file.
2. Go to prompt - Just access the ramdisk shell
3. Reboot - Just restart the computer
This dialog is the unique feature of X-Slacko Slim's initrd. Its more user friendly than the vanilla one. The user gives options what to do next.
Options:
1. Save Temp Files - This will save the contents of /tmp of initrd to a disk (When puppy sfs is sucessfully loaded and perform switch root, it moves to /initrd/tmp). the /tmp folder of the initrd contains log files created by init script. Which is useful for troubleshooting. When the user choose this option. It shows list of storage device and the user must choose where to save the temp files in tarball file.
2. Go to prompt - Just access the ramdisk shell
3. Reboot - Just restart the computer
Sage
If you get the message with the options, just select the Save Temp files one (it is first so probably already highlighted). Hit enter and pick a partition to save on.
It does work - I deliberately changed the name of the puppy_xslacko_4.2.sfs so it would not be found.
I was booting from a USB stick so saved to that.
If all goes well you will have a file called:
puppy-initrd-temp-files.tar.gz
Then again, is anything Sage proof?
If you get the message with the options, just select the Save Temp files one (it is first so probably already highlighted). Hit enter and pick a partition to save on.
It does work - I deliberately changed the name of the puppy_xslacko_4.2.sfs so it would not be found.
I was booting from a USB stick so saved to that.
If all goes well you will have a file called:
puppy-initrd-temp-files.tar.gz
Then again, is anything Sage proof?
modesetting
hi mistfire
the modesetting.so you placed in /usr/lib/x/drivers-alternate/ is the correct one for this kernel.
I copied it to /usr/lib/xorg/modules/drivers/ to replace the older modesetting.so that was in that folder.
The older modesetting.so was incompatible with current kernel.
I finally have all graphics modes now !!
Please, for R60, make this change.
Regards,
Volhout
the modesetting.so you placed in /usr/lib/x/drivers-alternate/ is the correct one for this kernel.
I copied it to /usr/lib/xorg/modules/drivers/ to replace the older modesetting.so that was in that folder.
The older modesetting.so was incompatible with current kernel.
I finally have all graphics modes now !!
Please, for R60, make this change.
Regards,
Volhout
fine tuning the desktop files and menu
mistfire,
I am using, and exploring, XSlack Slim for a while now, and notice that there are many duplicate functions in the menu, and some are missing, or in the wrong section.
i.e. lighthouse system info is not in "system", but in "all"
this combines several independent system info tools
i.e.
control pane, combines many settings (XFCE, timezone etc..)
all the individual entries could be removed from the menu.
This is typically optimized by editting the .dekstop files in /usr/share/applications.
Are you interested in this type of cleaning up, or are you completely happy with how the menu's are structured now.
If you agree, I will spend an evening in trying to clean it up. Most of it can be done by simply adding "NoShow=true" in the items that can disappear from the menu.
Regards,
Volhout
I am using, and exploring, XSlack Slim for a while now, and notice that there are many duplicate functions in the menu, and some are missing, or in the wrong section.
i.e. lighthouse system info is not in "system", but in "all"
this combines several independent system info tools
i.e.
control pane, combines many settings (XFCE, timezone etc..)
all the individual entries could be removed from the menu.
This is typically optimized by editting the .dekstop files in /usr/share/applications.
Are you interested in this type of cleaning up, or are you completely happy with how the menu's are structured now.
If you agree, I will spend an evening in trying to clean it up. Most of it can be done by simply adding "NoShow=true" in the items that can disappear from the menu.
Regards,
Volhout
New X-Slacko Slim iteration released
Changes:
* Some fixes on PPM.
* Wrong modesetting driver fixed. (thanks Volhaut)
Download: https://drive.google.com/open?id=0B2FRk ... GIwVlhZS0U
MD5 Checksum: 081e707158ea572df5412b53dead38d3
Changes:
* Some fixes on PPM.
* Wrong modesetting driver fixed. (thanks Volhaut)
Download: https://drive.google.com/open?id=0B2FRk ... GIwVlhZS0U
MD5 Checksum: 081e707158ea572df5412b53dead38d3
@Sage thats why I need the initrd tmp files that was saved in tarball (puppy-initrd-temp-files.tar.gz ). In order to trace the problem that was occured in your machine because it contains log files generated by init. If you encountered that fatal error, you must save the initrd temp files by choosing "save temp files". select a partition to save and upload puppy-initrd-temp-files.tar.gz here.
I cannot perform miracles! There are NO initrd temp files. There is NO partition to save. It never, ever starts!!! ipso facto, I cannot upload anything.you must save the initrd temp files by choosing "save temp files". select a partition to save and upload puppy-initrd-temp-files.tar.gz here
The whole thing is broken, unlike r54 which works perfectly. I cannot give you any other information until you provide a version that starts!
Exasperated...
@Sage we have a misunderstanding here. let me explain to you. initrd temp files exists. It was on the ram when puppy boot. To prove it, boot X-Slacko Slim using pfix=initrd parameter then you will get to the terminal, type ls and you will notice that "tmp" folder was shown. Thats what I talked about. The contents of tmp folder must be compressed to tarball and saved it to a partition.
About there is no partition to save scenario. Is there any hard drives exists on your computer? If not, connect a hard drive before booting or just plug a usb flash drive upon encountering the fatal error dialog then choose save temp files. The flash drive will be detected because the kernel has builtin USB modules on it. Keef tested that and it works.
We need any way to get that puppy-initrd-temp-files.tar.gz and analyze the logs created by init to solve the issue on your machine.
About there is no partition to save scenario. Is there any hard drives exists on your computer? If not, connect a hard drive before booting or just plug a usb flash drive upon encountering the fatal error dialog then choose save temp files. The flash drive will be detected because the kernel has builtin USB modules on it. Keef tested that and it works.
We need any way to get that puppy-initrd-temp-files.tar.gz and analyze the logs created by init to solve the issue on your machine.
Yes, of course. Bit busy this week so don't hold your breath. Also resurrected an Intel machine in order to throw more light on why so many Puppies have suddenly stopped working or displaying correctly. To date the only constancy have been my utterly reliable AMD 32&64bit single and multiple core machines!mistfire wrote:@Sage I have an idea how to fix your problem in your machine. But first can I have a favor to you, Can you boot a pristine X-Slacko 4.2 on your machine?
Later.
OK - it's later, and the answer is YES. I can boot XSlacko 4.2 from the .iso on all 7 machines presently running, different video cards - nv or Radeon, various cpu, - AMD , various mem., various screen sizes and resolutions, 32 & 64bit : no problems.
What would you like me to do next?
Incidentally, it's not just your Puppy distro that fails to boot, problems also with peebee's Zesty and Artful - there is nothing I can boot nor save from those, either.
PS: but NOT Intel !
Oh, how I hate Intel. A thousand curses on the Wintel cartel and all their leverage strategies. Nothing but trouble since 8088 and DOS 1. Killers of good science, DRDOS, Novell, : add your list here.....
If they love $$$ so much maybe someone over there can stuff a bunch of $ bills down their gullets. Would beat capital punishment.