Here are the results of these two further terminal inputs with my non-Slacko-mounting CD.@davids45:
Run "probepart". Does it see the disk as UDF?
Run "guess_fstype /dev/sr0". What does it see?
Regards,
David S.
Here are the results of these two further terminal inputs with my non-Slacko-mounting CD.@davids45:
Run "probepart". Does it see the disk as UDF?
Run "guess_fstype /dev/sr0". What does it see?
You are, as Oscar said, likely running into 64-bit sfs files on a 32-bit machine. The binaries will say amd64. Chrome is also 64-bit only, but you can use the stable branch of Vivaldi 1.9.818.50, which is available for 32-bit machines (i386). I'm running this now on that beat-up D600. It is painfully slow on such a slow machine, but that is what I'm trying to use to expose a nondeterministic timing problem.josepinto wrote:Hi,
I used the included browser installer to create Opera 46 sfs but it does not run after loading the sfs.
Opera 45 worked ok.
I did not tested Chrome or Vivaldi.
Thanks in advance,
José Pinto
2 ways I can think of. 1)Try downloading all the necessary xorg/mesa/intel components from slackware -current and run them through the woof templates then construct a y-drive or 2)ask peebee. I do get the issue on my wife's macbook but I won't get a chance to play with that until Saturday. Since the 'uxa' thing seems to be the key for most I want to try and detect errors in the xorg/kernel logs and apply that fix before X starts or if not apply it and suggest an X re-start in a message window (possibly a terminal window or something that doesn't rely on too much 'tool-kit').gyro wrote:01micko,
I did some testing of my video problem, GPU hangs until set "XUA".
I notied that LxPupSc 17.06.22 does not have this probelm, so I tried using it's 4.11.5 kernel with slacko, but that did not fix the problem.
I then noticed that slacko has "X.Org 1.18.3, Open GL 3.0 Mesa 11.2.2."
Where as lxpupsc has "X.Org 1.19.3, Open GL 3.0 Mesa 17.1.2".
How can I upgrade this X stuff in slacko to see if that fixes the issue?
gyro
So there is a bug in probepart (and further up 'blkid').davids45 wrote:udf
Hi,prehistoric wrote:You are, as Oscar said, likely running into 64-bit sfs files on a 32-bit machine. The binaries will say amd64. Chrome is also 64-bit only, but you can use the stable branch of Vivaldi 1.9.818.50, which is available for 32-bit machines (i386). I'm running this now on that beat-up D600. It is painfully slow on such a slow machine, but that is what I'm trying to use to expose a nondeterministic timing problem.josepinto wrote:Hi,
I used the included browser installer to create Opera 46 sfs but it does not run after loading the sfs.
Opera 45 worked ok.
I did not tested Chrome or Vivaldi.
Thanks in advance,
José Pinto
Aside for others: At the moment the damn thing refuses to misbehave. None of the machines I wanted to try have been slower, or limited to 32-bit software. If this continues, I'd say you are unlikely to hear from people bothered by it, assuming the dhcpcd_drop_wait pet is applied. This fix seems time-dependent, but I believe the slow hardware which most often exposes the bug will disappear in a few years. I wouldn't bet my life on this software, but shouldn't have to.
For those who have been irritated by my approach I can only say I appreciate that they have stopped short of threatening violence, as did happen in the past when I worked to expose concurrency problems programmers had spent months or years making less likely without fixing. I found the problems, but upset quite a few people in the process. Ordinary sequential reasoning doesn't work well until you have narrowed the possibilities considerably, so my actions seem perverse and illogical. Until you've seen some real-life examples you would not believe the way concurrency multiplies the number of combinations of possible states and state transitions. Nobody can handle such overhelming complexity directly.
If you can run any 64-bit software, the problem is not 32-bit versus 64-bit. You might still stick with the stable branch of Opera, Vivaldi or Chrome.josepinto wrote:...Hi,
Thank you for the explanation.
I think I have a processor capable of 64 bit instructions as described here: https://wiki.archlinux.org/index.php/Samsung_N150
Should I run 32 bit of 64 bit slacko?
I am testing the 64 bit version with Palemoon and Libreoffice.
Does the 64bit Slacko you are testing have GTK+3 included? If not, try installing it via PPM.josepinto wrote:I am testing the 64 bit version with Palemoon and Libreoffice.
@Sailor EnceladusSailor Enceladus wrote:@gyro and norgo: Do you get the desktop freeze in LxPupSc if you switch to jwm in the desktop menu and restart the graphical server? Maybe having a slacko-current option in woof-CE would be a good idea? Though, updating often is kind of a pita... when I try devuan ascii builds it seems like debian team updates something every day... or maybe it's just because stretch is now out in the wild.
I'm happy to report that it's fixed in a rationalise build done todaySailor Enceladus wrote:Thanks Billtoo. 01micko is working on this in the "rationalise" branch so if you build with that you might not need the pet any more
https://github.com/puppylinux-woof-CE/woof-CE/commit/82044e6d1e217010723fa921350c3c8218990de0
Thanks,8Geee wrote:josepinto:
The Samsung N150 is a 64-bit NETBOOK. You will need to download the Intel 64bit version of this Slacko. 1Gb memory might not be enough, 2Gb is preferred on these newest Slacko's.
========================================================================
FWIW I D/L the 6996 32-bit NP k3.16.43 version and with A, z, and f sfs's ... holy cow 915Mb in RAM ... 32bit non-PAE ain't what it used to be. To get this down to a netbook useful size involves LOTSA pruning. (Slacko5.7 EONS for Netbooks of the 2008-10 era is 444Mb RAM)
Regards
8Geee
I just switched my install of LxPupSc to use jwm, and was still unable to produce a freeze.Sailor Enceladus wrote:@gyro and norgo: Do you get the desktop freeze in LxPupSc if you switch to jwm in the desktop menu and restart the graphical server?
That must be my problem.OscarTalks wrote:Does the 64bit Slacko you are testing have GTK+3 included? If not, try installing it via PPM.josepinto wrote:I am testing the 64 bit version with Palemoon and Libreoffice.
Read:josepinto wrote:Hi,
Is it possible to mount Android devices in slacko-700 64?
Code: Select all
PKGTYPE=sfs ./build_xf86_intel