Slacko32/64 700 BETA 2
I had gotten the report before I noticed the last post encouraging the PET vs the ".gz file". I did look thru the report but did not spot anything. Sure I am overlooking something.
Attached is my Slacko64-V7a on the Intel with the HDMI audio problem.
Attached is my Slacko64-V7a on the Intel with the HDMI audio problem.
- Attachments
-
- Reports for audio analysis.tar.gz
- This might be useful.
- (21.89 KiB) Downloaded 155 times
Find command error message. Bug?
New concern. This message from find commandThis is a pristine RAM only PC with no local storage, excepting the USB DVD.
Is this a concern?
Code: Select all
find / -name mscw*
o
o
o
o
find: WARNING: Hard link count is wrong for '/proc/fs' (saw only st_nlink=12 but we already saw 10 subdirectories): this may be a bug in your file system driver. Automatically turning on find's -noleaf option. Earlier results may have failed to include directories that should have been searched.
Is this a concern?
Last edited by gcmartin on Fri 02 Sep 2016, 17:19, edited 2 times in total.
-
- Posts: 1543
- Joined: Mon 22 Feb 2016, 19:43
I agree. It's a shame that those with booting issues (James C, Billtoo)gyro wrote:I hope not too soon, the debug stuff has not been pushed to woof-ce yet.mavrothal wrote:Maybe Mick will get 6.9.6 out soon.
I was rather hoping for at least 1 run in a real problem situation before pushing.
But such is life.
did not post their debug results, considering how much work you put
into making it. Or did they PM you their data? If it's not resolved then
I guess the bug they experienced will also be in Slacko 6.9.5 32-bit.
Placed the init script in the original initrd.gz.gyro wrote:A new debug version of the init script is attached.
A new debug version of the initrd.gz has been uploaded to the same place as the previous version.
This version has been pushed to woof-ce rationalise.
It no longer has any dropout points, it just produces messages, but an improved set.
gyro
Only thing to report is no boot and error messages zipping by faster than I can read them.
Something to the effect of can't locate var/vc/3 ,var/vc/4, and so on.
And it got up to pid1989 when I aborted.
Switched to one of the earlier debug inits I'd downloaded, still no boot but got some output at least.
- Attachments
-
- ps.txt.gz
- (822 Bytes) Downloaded 171 times
-
- probepart.log.gz
- (511 Bytes) Downloaded 163 times
-
- partitions.txt.gz
- (314 Bytes) Downloaded 156 times
-
- mount.txt.gz
- (157 Bytes) Downloaded 155 times
-
- lsof.txt.gz
- (142 Bytes) Downloaded 163 times
-
- dmesg.txt.gz
- (9.7 KiB) Downloaded 157 times
-
- df.txt.gz
- (135 Bytes) Downloaded 166 times
-
- bootinit.log.gz
- (146 Bytes) Downloaded 167 times
-
- ATADRIVES0.gz
- (39 Bytes) Downloaded 158 times
-
- ALLDRVS0.gz
- (41 Bytes) Downloaded 155 times
@James C,
Thankyou very much for testing.
I've only looked at the bootinit.log, and it's rather interesting.
Some variables are obviously empty when they should not be.
This results in the init failing to actually mount any thing.
I obviously need to do some more digging with your other files.
Then I will produce a test init that simply attempts to load a single partition.
Later edit:
Interestingly it should not be trying to cat '/sys/block//queue/rotational' unsless "pfix=trim" is specified.
gyro
Thankyou very much for testing.
I've only looked at the bootinit.log, and it's rather interesting.
Some variables are obviously empty when they should not be.
This results in the init failing to actually mount any thing.
I obviously need to do some more digging with your other files.
Then I will produce a test init that simply attempts to load a single partition.
Later edit:
Interestingly it should not be trying to cat '/sys/block//queue/rotational' unsless "pfix=trim" is specified.
gyro
A new version of the init script is attached.
An updated initrd.gz is available at http://www.fishprogs.software/puppy/slacko64/initrd.gz.
It still includes the code to write debug messages to bootinit.log.
@James C,
Based on your data, I was finally able to reproduce a problem that looked a lot like yours. The bootinit.log looked almost identical to the one you posted.
This version should fix it. Well at least it fixes a real bug. So, please give this one a go.
Hmm.. If this doesn't fix it, it's back to a small test init that doesn't do much and building piece by piece.
The problem occured when attempting to mount a partition with a large number of partitions present.
If you try to mount sdb1 and sdb10... exist the problem is triggered. I had to add a lot of partitions so that mounting sdc2 there were sdc20...
It was a grep that expected a single response but in that situation gets multiple responses.
Edit:
Download is withdrawn, the latest version will always be on woof-ce.
gyro
An updated initrd.gz is available at http://www.fishprogs.software/puppy/slacko64/initrd.gz.
It still includes the code to write debug messages to bootinit.log.
@James C,
Based on your data, I was finally able to reproduce a problem that looked a lot like yours. The bootinit.log looked almost identical to the one you posted.
This version should fix it. Well at least it fixes a real bug. So, please give this one a go.
Hmm.. If this doesn't fix it, it's back to a small test init that doesn't do much and building piece by piece.
The problem occured when attempting to mount a partition with a large number of partitions present.
If you try to mount sdb1 and sdb10... exist the problem is triggered. I had to add a lot of partitions so that mounting sdc2 there were sdc20...
It was a grep that expected a single response but in that situation gets multiple responses.
Edit:
Download is withdrawn, the latest version will always be on woof-ce.
gyro
Last edited by gyro on Sat 03 Sep 2016, 07:55, edited 1 time in total.
gyro wrote:A new version of the init script is attached.
An updated initrd.gz is available at http://www.fishprogs.software/puppy/slacko64/initrd.gz.
It still includes the code to write debug messages to bootinit.log.
@James C,
Based on your data, I was finally able to reproduce a problem that looked a lot like yours. The bootinit.log looked almost identical to the one you posted.
This version should fix it. Well at least it fixes a real bug. So, please give this one a go.
Hmm.. If this doesn't fix it, it's back to a small test init that doesn't do much and building piece by piece.
The problem occured when attempting to mount a partition with a large number of partitions present.
If you try to mount sdb1 and sdb10... exist the problem is triggered. I had to add a lot of partitions so that mounting sdc2 there were sdc20...
It was a grep that expected a single response but in that situation gets multiple responses.
gyro
I'll give the new init a try in a few hours when I free some time up.
Right now this box doesn't have my usual number of partitions (less) because of the tiny ssd. Most of the time there is a couple of rows of drive icons on the desktop ......
Excellent.James C wrote:I'll give the new init a try in a few hours when I free some time up.
In my test I only got up to sdc24 + 4 each for sda and sdb.James C wrote:Right now this box doesn't have my usual number of partitions (less) because of the tiny ssd. Most of the time there is a couple of rows of drive icons on the desktop ......
gyro
Swapped in the replacement initrd.gz linked above. Boots normally now.gyro wrote:A new version of the init script is attached.
An updated initrd.gz is available at http://www.fishprogs.software/puppy/slacko64/initrd.gz.
It still includes the code to write debug messages to bootinit.log.
All of my semi-new boxes have a minimum of 2 hard drives so I generally use lots of partitions.Getting ready to add a drive to this box when I find time,got a couple sitting in a box on the floor beside me ........ hard to pass up a good sale.
Code: Select all
-Computer-
Processor : 6x AMD FX(tm)-6300 Six-Core Processor
Memory : 16309MB (498MB used)
Machine Type : Physical machine
Operating System : Slacko64 Puppy - 6.9.5
User Name : root (root)
Date/Time : Fri 02 Sep 2016 06:45:03 PM CDT
-Display-
Resolution : 1440x900 pixels
OpenGL Renderer : Gallium 0.4 on NVA8
X11 Vendor : The X.Org Foundation
Code: Select all
# report-video
VIDEO REPORT: Slacko64 Puppy, version 6.9.5
Chip description:
unknown
Requested by /etc/X11/xorg.conf:
Modules requested to be loaded: dbe
Probing Xorg startup log file (/var/log/Xorg.0.log):
Driver loaded (and currently in use): nouveau
Loaded modules: dbe dri2 exa extmod fb fbdevhw glx kbd mouse shadowfb
Actual rendering on monitor:
Resolution: 1440x900 pixels (381x238 millimeters)
Depth: 24 planes
...the above also recorded in /tmp/report-video
Code: Select all
# free
total used free shared buff/cache available
Mem: 16309388 323064 15147740 329820 838584 15446820
Swap: 8396796 0 8396796
#
Booted no problem with initrd,gz replaced.
Several partitions on this one too.......
Code: Select all
-Computer-
Processor : 2x AMD Athlon(tm) 64 X2 Dual Core Processor 5200+
Memory : 4041MB (456MB used)
Machine Type : Physical machine
Operating System : Slacko64 Puppy - 6.9.5
User Name : root (root)
Date/Time : Fri 02 Sep 2016 09:16:59 PM CDT
-Display-
Resolution : 1440x900 pixels
OpenGL Renderer : Gallium 0.4 on NVA8
X11 Vendor : The X.Org Foundation
Code: Select all
# report-video
VIDEO REPORT: Slacko64 Puppy, version 6.9.5
Chip description:
unknown
Requested by /etc/X11/xorg.conf:
Modules requested to be loaded: dbe
Probing Xorg startup log file (/var/log/Xorg.0.log):
Driver loaded (and currently in use): nouveau
Loaded modules: dbe dri2 exa extmod fb fbdevhw glx kbd mouse shadowfb
Actual rendering on monitor:
Resolution: 1440x900 pixels (381x238 millimeters)
Depth: 24 planes
...the above also recorded in /tmp/report-video
Code: Select all
# free
total used free shared buff/cache available
Mem: 4041556 316628 2900208 326608 824720 3192120
Swap: 14540792 0 14540792
#
Code: Select all
# fdisk -l
Disk /dev/sda: 1000.2 GB, 1000204886016 bytes
224 heads, 19 sectors/track, 459004 cylinders, total 1953525168 sectors
Units = sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 4096 bytes
I/O size (minimum/optimal): 4096 bytes / 4096 bytes
Disk identifier: 0x80895fa3
Device Boot Start End Blocks Id System
/dev/sda1 * 2048 206847 102400 7 HPFS/NTFS/exFAT
/dev/sda2 206848 313343999 156568576 7 HPFS/NTFS/exFAT
/dev/sda3 313344000 356351999 21504000 83 Linux
/dev/sda4 356354046 1953524250 798585102+ 5 Extended
Partition 4 does not start on physical sector boundary.
/dev/sda5 356354048 372942847 8294400 82 Linux swap / Solaris
/dev/sda6 372944896 803024895 215040000 83 Linux
/dev/sda7 803026944 907474943 52224000 83 Linux
/dev/sda8 907476992 1011924991 52224000 83 Linux
/dev/sda9 1011927040 1116375039 52224000 83 Linux
/dev/sda10 1116377088 1220824353 52223633 83 Linux
/dev/sda11 1220827136 1427675135 103424000 83 Linux
/dev/sda12 1427677184 1532125183 52224000 83 Linux
/dev/sda13 1532127232 1636575231 52224000 83 Linux
/dev/sda14 1636577280 1741025279 52224000 83 Linux
/dev/sda15 1741027328 1845475327 52224000 83 Linux
/dev/sda16 1845477376 1953524250 54023437+ 83 Linux
Disk /dev/sdb: 250.1 GB, 250059350016 bytes
255 heads, 63 sectors/track, 30401 cylinders, total 488397168 sectors
Units = sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disk identifier: 0x8c3f2c41
Device Boot Start End Blocks Id System
/dev/sdb1 * 2048 51199313 25598633 83 Linux
/dev/sdb2 51200000 104450047 26625024 83 Linux
/dev/sdb3 104450048 167938047 31744000 83 Linux
/dev/sdb4 167940094 488396799 160228353 5 Extended
/dev/sdb5 167940096 180432895 6246400 82 Linux swap / Solaris
/dev/sdb6 180434944 237778943 28672000 83 Linux
/dev/sdb7 237780992 297172991 29696000 83 Linux
/dev/sdb8 297175040 329943039 16384000 83 Linux
/dev/sdb9 329945088 362713087 16384000 83 Linux
/dev/sdb10 362715136 395483135 16384000 83 Linux
/dev/sdb11 395485184 428253183 16384000 83 Linux
/dev/sdb12 428255232 461022810 16383789+ 83 Linux
/dev/sdb13 461025280 488396799 13685760 83 Linux
#
Several partitions on this one too.......
My P 7.0.7 running now has some latency in desktop
The stork drop xenialpup of its bill, and took off immediately
Not only one trouble for install.
My P 7.0.7 running now has some latency in desktop
Nevertheless i keep this version, on an USB stick.
I become lost in versions numbers. 6.9.5 and 7.0.7..
Feed back for video users, version 2.2.2 VLC reads MP4 at Home (xenialpup 7.0.7)
Bino is a video player 3D,
My packages :
bino_1.6.1-1|bino|1.6.1-1||Multimedia;video|1706K|pool/universe/b/bino|bino_1.6.1-1_amd64.deb|+libass5&ge0.13.0,+libavcodec-ffmpeg56&ge2.4,+libavdevice-ffmpeg56&ge2.4,+libavformat-ffmpeg56&ge2.4,+libavutil-ffmpeg54&ge2.4,+libc6&ge2.17,+libgcc1&ge4.1.1,+libgl1-mesa-glx,+libglewmx1.13&ge1.12.0,+liblircclient0,+libopenal1&ge1.14,+libqt5core5a&ge5.0.2,+libqt5gui5&ge5.0.2,+libqt5opengl5&ge5.0.2,+libqt5widgets5&ge5.0.2,+libstdc++6&ge5.2,+libswscale-ffmpeg3&ge2.4|3D video player|ubuntu|xenial||
libfaac0_1.28+cvs20151130-1|libfaac0|1.28+cvs20151130-1||BuildingBlock|168K|pool/multiverse/f/faac|libfaac0_1.28+cvs20151130-1_amd64.deb|+libc6&ge2.14|AAC audio encoder library|ubuntu|xenial||
Not only one trouble for install.
My P 7.0.7 running now has some latency in desktop
Nevertheless i keep this version, on an USB stick.
I become lost in versions numbers. 6.9.5 and 7.0.7..
Feed back for video users, version 2.2.2 VLC reads MP4 at Home (xenialpup 7.0.7)
Bino is a video player 3D,
My packages :
bino_1.6.1-1|bino|1.6.1-1||Multimedia;video|1706K|pool/universe/b/bino|bino_1.6.1-1_amd64.deb|+libass5&ge0.13.0,+libavcodec-ffmpeg56&ge2.4,+libavdevice-ffmpeg56&ge2.4,+libavformat-ffmpeg56&ge2.4,+libavutil-ffmpeg54&ge2.4,+libc6&ge2.17,+libgcc1&ge4.1.1,+libgl1-mesa-glx,+libglewmx1.13&ge1.12.0,+liblircclient0,+libopenal1&ge1.14,+libqt5core5a&ge5.0.2,+libqt5gui5&ge5.0.2,+libqt5opengl5&ge5.0.2,+libqt5widgets5&ge5.0.2,+libstdc++6&ge5.2,+libswscale-ffmpeg3&ge2.4|3D video player|ubuntu|xenial||
libfaac0_1.28+cvs20151130-1|libfaac0|1.28+cvs20151130-1||BuildingBlock|168K|pool/multiverse/f/faac|libfaac0_1.28+cvs20151130-1_amd64.deb|+libc6&ge2.14|AAC audio encoder library|ubuntu|xenial||
Last edited by Pelo on Sun 04 Sep 2016, 11:05, edited 3 times in total.
Great thanks gyro! I *should* have time tomorrow to build and upload a 32 bit version and update the 64 version.gyro wrote:This bug in init where it failed in the prescence of lots of partitions, is now fixed in the rationalise branch of woof-ce.
gyro
Cheers!
Puppy Linux Blog - contact me for access
I'm not going to provide direct downloads of the init script in the forum any more.
The latest working (at least for me) version, can always be found in the woof-ce 'rationalise' branch, at "initrd-progs/0initrd/init".
And it will also be available in the current initrd.gz at http://www.fishprogs.software/puppy/slacko64/initrd.gz.
Oh, the init in both these is not quite the same as the one most recently published here on the forum, but the changes are just slightly improved ways of doing the same thing.
Also on woof-ce, 'rationalise' branch, there is a new README.txt for the new init at "initrd-progs/0initrd/README.txt" that contains a lot of information about the new int script.
Thank you ninaholic and peebee for proof reading it.
gyro
The latest working (at least for me) version, can always be found in the woof-ce 'rationalise' branch, at "initrd-progs/0initrd/init".
And it will also be available in the current initrd.gz at http://www.fishprogs.software/puppy/slacko64/initrd.gz.
Oh, the init in both these is not quite the same as the one most recently published here on the forum, but the changes are just slightly improved ways of doing the same thing.
Also on woof-ce, 'rationalise' branch, there is a new README.txt for the new init at "initrd-progs/0initrd/README.txt" that contains a lot of information about the new int script.
Thank you ninaholic and peebee for proof reading it.
gyro
There's a serious bug and a new alpha release is required...
https://github.com/puppylinux-woof-CE/w ... issues/870
https://github.com/puppylinux-woof-CE/w ... issues/870
32 bit and 64 bit alpha 2 isos are uploading. Will be there soon barring any connection catastrophe.jlst wrote:There's a serious bug and a new alpha release is required...
https://github.com/puppylinux-woof-CE/w ... issues/870
See main post.
Puppy Linux Blog - contact me for access