The email address it sends with the message didn't work? So, here is what I wrote in the email.
ftp://setzco.dyndns.org/g4l-v0.56alpha19-fc28.iso
Is the latest one I am working on, and it has later kernels.
Did you try the failsafe option?
Sometimes when it locks, the last thing it shows is the last thing that worked, and it is the next thing that is causing the issue.
As a last resort, I've sometimes removed the disk from the notebook, and connected it to another system either via regular connection or via a usb connection. The image process doesn't require the process to be done in the same machine.
That is my home machine, so speed isn't great. Have 50M down, but only about 2.5M up. Use to use a machine at college before I retired last year. They had 100M / 100M connection, but never would get better than about 20M after hours.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
so the same
ata8: PATA max PIO4 cmd 0x170 ctl 0x376 irq 15
device host6 device unregister
PM removing info for no bus host 6
bus scsi remove device host6
pm removing info for scsci host 6
pm removing info for no bus dev 8.0
pm removing info for no bus dev 8.0
pm removing info for no bus dev 8.1
pm removing info for no bus dev 8.1
pm removing info for no bus link8
pm removing info for no bus link8
pm removing info for no bus ata8
pm removing info for no bus ata8
bus platform remove device pata_legacy.1
pm removing info for platform: pata_legacy.1
device dummo0 device_add
pm adding info for no bus:dummy0
freeze
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
http://redsymbol.net/linux-kernel-boot-parameters/ seems to show some kernel options that disable various PATA drive options? Wonder if the system doesn't have a controller, and is thus locking when the kernel tries to prob for it.
What kind of disk does it have, and what is the interface?
In the earlier message, I was talking about taking the disk you want to create an image of, and hooking it to another machine to make an image. So, if there is another system (notebook or PC) that can hook up the disk.
Next step might be to try to build a kernel with no PATA devices,
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
ftp://setzco.dyndns.org/bz4x19.6x I created a kernel in which I commented out all the CONFIG_PATA lines.
Not sure how you are running the g4l, and if you are able to modify the boot by replacing the kernel
If it is a problem, I can build a special one with this kernel. It's currently almost 1am on December 4th, so will look at doing it tomorrow.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
There are only limited kernel options that exist and NoPATA isn't one of them.
The ones that might work are:
libata.dma= [LIBATA] DMA control
libata.dma=0 Disable all PATA and SATA DMA
libata.dma=1 PATA and SATA Disk DMA only
libata.dma=2 ATAPI (CDROM) DMA only
libata.dma=4 Compact Flash DMA only
Combinations also work, so libata.dma=3 enables DMA
for disks and CDROMs, but not CFs.
But those would be a lot of testing to see what works, and they are also looking at DMA not PIO?? But doing the disable option might do it. Would use the TAB on the menu to edit the boot line.
The kernel that I created, I had to manually go into the .config file and comment out all the CONFIG_PATA lines and the completely rebuild the kernel from the source code. That is why the 19.6x kernel is smaller, since it contains none of those drivers in the kernel.
Burning the ISO image to an USB is the quick way, but then has the limits of making any changes quickly without building a new ISO image. Another option is a g4l-lite I create from time to time. It just has the latest single kernel, and uses grub4dos to boot from the USB.
If the system is using grub to boot, the g4l kernel and the ramdisk.lzma can be added to the regular boot menu very easily. There is a 40_CUSTOM file that goes in the /etc/grub.d direcotry.
Not clear if the OS on system is Windows 10 or Linux or something else. grub4dos work fine with earlier windows, but version 10 of windows boot loader contains issues that are more complex than most users want to deal with.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
i now copy in the ftp://setzco.dyndns.org/bz4x19.6x and copy it over bz4x19.6 and boot the usb but now it stops at
VMware PVSCSI driver version 1.0.7.0-k
SCSI Media Changer Driver v0.25
i run with debug parameter
seems same
device class nvme registering
device class nvme-subsystem registering
bus pci add driver nvme
device dummy0 device_add
pm: adding info for no bus:dummy0
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
ftp://setzco.dyndns.org/g4l-v0.56alpha20-fc28.iso
I rebuilt the bz4x19.6 kernel with all the NVME options (except one for andriod) set to yes
The above messages seem to confirm that the last message before the freeze was the last process that ended successfully, and the freeze happens before info is displayed??
I don't have any physical NVME disks, so had only done testing with the VirtualBox NVME disks, and was able to get it to work just fine. Only had the basic NVME option set in kernel. Have not turned on about 7 more options. cat bz4x19.6.config | grep NVME will show them.
Don't know if that will solve the problem, or at least get it to show info or do nothing different.
What version of partedmagic are you using? I knew it had an older version that included g4l, but thought later versions didn't have it? Not sure if it includes the kernel .config file they use, but it might be interesting to see if there? Don't know if it might be some firmware issue. I have included some special firmware files that users needed, but don't know if NVME drives require any, and if so, why it wouldn't show some message rather than freezing.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Hi
Thank you for the ongoing efforts!
I now download alpha20-fc28.iso to flash drive and i select the 19.6 kernel it says 0.56a in the menu
but strange it seems same stop at ata8 PATA max PIO4 cmd 0x170 ctl 0x376 irq 15
i try also with tab debug parameter
PM removing info for no bus ata8
bus platform remove device pata_legacy.1
pm removing info for platform pata_legacy.1
device dummy0 device_add
pm adding info for no bus dummy0
freeeze
not sure if i do something wrong?
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
At this point, with the kernel not reporting any specific errors, it is kind of a shot in the dark.
Here are some things that might be worth trying. Not sure which order would be best to try.
I've seen on the syslinux list that some systems have issues with the actual bios code, and seeing if a new bios is available for the machine might make flashing the bios to the latest version. Have had bios updates solve various problems.
Might be some bios setting? At the college, we got some machines a few years ago, and they would not boot the g4l or the linux? Found in the bios it had an Enhanced boot option that was set on by default. Turning that back to the standard option made everything work just fine. Windows booted and ran fine. Ran disk benchmarks with the Enhanced and stand options and got exactly same results. So, with the disks in those machines it made no difference. Might have been with higher grade disks it would have done something, but was not compatible with g4l or linux. Did a similar just freezing wth no error.
Did a boot on my virtualbox test, and looked at dmesg. It only reported ata1, so not sure why yours is going all the way up to ata8? Even so, since we tried a kernel with all the ata stuff removed, it still froze with just another message.
Could be an issue with the syslinux boot loader with the configuration. I've also run g4l from a usb using grub4dos instead of the syslinux that the iso uses.
Have files that have less stuff, just the single latest kernel.
ftp://setzco.dyndns.org/g4l-lite-fc28.exe
That is a self-extracting 7z file.
You can extrat the files to a flash disk, and it includes the grub4dos programs to make the flash bootable. Seems to work great with linux, but sometimes windows doesn't actually make the flash bootable?? Believe there is a file that explans the process??
So, I would probable start with the BIOS settings, and see if there are any settings that might be causing the issue.
Last thing, is it could be some kind of EFI setting. The g4l kernels don't have the special signature for EFI boot, so if the machine is setup to only boot signed kernels, that might be it. We didn't use EFI boot at the college or on my own machines, and had some users that did, but they could turn off the option, make the image, and then turn it back on.. Syslinux has had a lot of discussion about it, and there are some people playing with it, but it is above my level at this time..
Had a user with a notebook that had other issues. I tried to go the makers site (don't recall), but to even asks for help they wanted a machine serial number and a service contract. I think a bios upgrade eventually solved that problem.
Good Luck.
Let me know if you come across anything that helps.
Also, a later version of bz4x19.7 kernel
ftp://setzco.dyndns.org/g4l-v0.56alpha21-fc28.iso
The source for the build.
ftp://setzco.dyndns.org/g4l-v0.56a21-fc28.devel.tar.xz
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Hi
1: Its a thinkpad t440p just installed latest BIOS but no difference
2: to look for something to disable in the BIOS do you know more specific what it could be?
All the secure boot is off since it boots linux ubuntu/mint mainly
3: I copied the g4l-lite-fc28.exe to the usb stick on another windows machine and it extracted but it is not making it bootable tried using grub4dos but could not get it bootable
4: trying the g4l-v0.56alpha21-fc28.iso and stops same ata8 PATA max PIO4 cmd 0x170 ctl 0x376 irq 15
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
In the bios I have set
UEFI/Legacy boot to legacy only
then i boot g4l 056 aplha 21 fc28 again
i select safe menu
press tab
add debug
and it just same after ata8 pata max pio4 cmd 0x170..
it goes device host 6 device unregister
bu scssi remove device host 6
then ending at
device dummy0 device add
pm adding info for no bus dummy0
Last edit: ben 2018-12-08
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Asked if anyone on syslinux knew of something that might help find the error.
Only got one reply so far. It kind of confirmed it must be whatever is checked after the test that is displayed, but don't know of a way to know what the thing after that would be. Checked the dmesg of my virtual box boot, and it only shows ata0 as being part of boot, but is a very simple option.
The message did mention that one might do something.
Use the mem= boot option to limit the amount of ram it is seeing.
Don't know if that would make a difference or not.
Tested it on my machine using Virtual box.
VirtualBox is configured to give 1G of ram to the boot, but if I add the mem=256M to the boot
usign (tab and then adding mem=512M. The system boots, and top only reports the 512M.
How much ram does the system have?? The g4l should work fine 256 - 512M. It creates a 128M ramdisk for the file system, but then just needs ram to run OS.
One other option in bios might be. Loading the video card membery, my one system has an option to load it above the 4G level. Since the g4l kernels are 32 bit, not sure if that would be an issue. Log ago, made a 64bot biuld, but it was a major project. Building the kernel wasn't a big deal, but then getting all the 64bit programs and libraries was a lot. Then did a test, and saw no significant change in size or speed.
Might also, be interestign to try hooking it to an external monitor? The kernel only uses basic video, and perhaps the monitor isn't supporting that vaa level..
Might want to boot, and add the command line option vga=ask, and try some of the vesa modes with the notebook screen, adn with a monitor.
When it freezes, does pressing the caps look or num lock key result in the lights changing??
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Hi
I just boot now
The laptop has 16 gb ram
1: I press tab add mem=256M
same stuck ata8 pata max pio4...
2: I reboot again add mem=512M
same stuck ata8 pata max io4...
3:When I go in the bios i can choose thinkpad lcd total graphics memory 256 MB or 512 i tried It was on 512 i tried put it to 256 and then also use mem=256 but just the same
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Having a hard time getting any info on finding the issue, but here is one more thing to try.
Looked at the kernel build options and found two little config settings that might get more info.
CONFIG_DEBUG_KOBJECT=y
CONFIG_DEBUG_NOTIFIERS=y
before the options were not set to y, but inactive. Have turned them on with the
bz14x19.8 kernel only.
The other option would be to use the tab key, and add the loglevel=15 to the boot line.
The default loglevel is 7,but it doesn't explain what the different levels do?? 15 is the max, and produces the most messages, so hopefully, it will show more info.
ftp://setzco.dyndns.org/g4l-v0.56alpha23-fc28.iso
You didn't mention if you had tried the grub4dos boot option?
Or what happens to the caps and numlock lights after the freeze.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Hi
Thank you for the ongoing efforts.
I now write 0.56alpha23 to the flash drive booting
1: I boot choose bz14x19.8 kernel same freeze ata8 pata max pio4 cmd 0x170
2: i boot again press tab and add loglevel=15
pm adding info for no bus dummy0
kobject dummy0 kobject uevent env
kobject dummy0 fill kobj path path devices virtual net dummy0
kobject queues kobject add internal parent dummy0
kobject queues kobject uevent env
kobject kobject add internal parent queues
kobject kobject uevent env
kobject fill kobj path path /devices/virtual/net/dummy0/queues/tx-0
3: did not try grub4dos could not get it to make the flash drive bootable
4: keyboard is complete dead after freeze nothing i press will work only thing i can do is hold down power button to it power off
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
The email address it sends with the message didn't work? So, here is what I wrote in the email.
ftp://setzco.dyndns.org/g4l-v0.56alpha19-fc28.iso
Is the latest one I am working on, and it has later kernels.
Did you try the failsafe option?
Sometimes when it locks, the last thing it shows is the last thing that worked, and it is the next thing that is causing the issue.
As a last resort, I've sometimes removed the disk from the notebook, and connected it to another system either via regular connection or via a usb connection. The image process doesn't require the process to be done in the same machine.
That is my home machine, so speed isn't great. Have 50M down, but only about 2.5M up. Use to use a machine at college before I retired last year. They had 100M / 100M connection, but never would get better than about 20M after hours.
Hi
Thanks for the fast reply.
I just writ the 0.56 alpha 19 to my usb drive reboot it.
I boot it up now with default kernel
I get the exact same
scsi 5.0.0.0 direct access ata samsung ssd 860...
sd 5 0 0 0 0attached scsi generic sg0 type 0
ata6.00 enabling discard_zeroes_data
sd 5 0 0 0 sda ...
sd 50 0 0 sda write protect is off
sd 5 0 0 0 sda write cache enabled...
ata 6.00 enabling discard_zeroest_data
sd 5 0 0 0 sda attached scsi disk
scsi host 6 pata_legacy
ata8: PATA max PIO4 cmd 0x170 ctl 0x376 irq 15
FREEZE
i just try the failsafe menu and also click kernel and just same goes to ata8 PATA max..
i try remove all ssd disk from machine and only boot the usb drive but just same goes like
floppy0:no floppy controllers found
work still pending
scsi host6 pata_legacy
ata8: PATA max PIO4 cmd 0x170... line
tried all 4 kernels in fail safe menu and all 4 in normal still same always stuck at ata8: PATA max PIO4 cmd...
i try now add tab kernel debug parameter it says:
so the same
ata8: PATA max PIO4 cmd 0x170 ctl 0x376 irq 15
device host6 device unregister
PM removing info for no bus host 6
bus scsi remove device host6
pm removing info for scsci host 6
pm removing info for no bus dev 8.0
pm removing info for no bus dev 8.0
pm removing info for no bus dev 8.1
pm removing info for no bus dev 8.1
pm removing info for no bus link8
pm removing info for no bus link8
pm removing info for no bus ata8
pm removing info for no bus ata8
bus platform remove device pata_legacy.1
pm removing info for platform: pata_legacy.1
device dummo0 device_add
pm adding info for no bus:dummy0
freeze
http://redsymbol.net/linux-kernel-boot-parameters/ seems to show some kernel options that disable various PATA drive options? Wonder if the system doesn't have a controller, and is thus locking when the kernel tries to prob for it.
What kind of disk does it have, and what is the interface?
In the earlier message, I was talking about taking the disk you want to create an image of, and hooking it to another machine to make an image. So, if there is another system (notebook or PC) that can hook up the disk.
Next step might be to try to build a kernel with no PATA devices,
ftp://setzco.dyndns.org/bz4x19.6x I created a kernel in which I commented out all the CONFIG_PATA lines.
Not sure how you are running the g4l, and if you are able to modify the boot by replacing the kernel
If it is a problem, I can build a special one with this kernel. It's currently almost 1am on December 4th, so will look at doing it tomorrow.
i just write the .iso to the usb drive can i convert above bz into 0.56NOPATA.iso ?
thanks
Or maybe more easy in the menu when booting add a NoPATA option kernel?
There are only limited kernel options that exist and NoPATA isn't one of them.
The ones that might work are:
libata.dma= [LIBATA] DMA control
libata.dma=0 Disable all PATA and SATA DMA
libata.dma=1 PATA and SATA Disk DMA only
libata.dma=2 ATAPI (CDROM) DMA only
libata.dma=4 Compact Flash DMA only
Combinations also work, so libata.dma=3 enables DMA
for disks and CDROMs, but not CFs.
But those would be a lot of testing to see what works, and they are also looking at DMA not PIO?? But doing the disable option might do it. Would use the TAB on the menu to edit the boot line.
The kernel that I created, I had to manually go into the .config file and comment out all the CONFIG_PATA lines and the completely rebuild the kernel from the source code. That is why the 19.6x kernel is smaller, since it contains none of those drivers in the kernel.
Burning the ISO image to an USB is the quick way, but then has the limits of making any changes quickly without building a new ISO image. Another option is a g4l-lite I create from time to time. It just has the latest single kernel, and uses grub4dos to boot from the USB.
If the system is using grub to boot, the g4l kernel and the ramdisk.lzma can be added to the regular boot menu very easily. There is a 40_CUSTOM file that goes in the /etc/grub.d direcotry.
Not clear if the OS on system is Windows 10 or Linux or something else. grub4dos work fine with earlier windows, but version 10 of windows boot loader contains issues that are more complex than most users want to deal with.
I try add tab
libata.dma=3 pata freeze again
libata.dma=4 pata freeze
like the libata.dmz=x has no effect?
i tried edit bz4x14_85.config and delete all config_pata lines then boot it put still freeze at PATA line?!
i now copy in the ftp://setzco.dyndns.org/bz4x19.6x and copy it over bz4x19.6 and boot the usb but now it stops at
VMware PVSCSI driver version 1.0.7.0-k
SCSI Media Changer Driver v0.25
i run with debug parameter
seems same
device class nvme registering
device class nvme-subsystem registering
bus pci add driver nvme
device dummy0 device_add
pm: adding info for no bus:dummy0
i tried booting partedmagic that worked and running g4l there but i rather have g4l working direct from usb and not use partedmagic at all
ftp://setzco.dyndns.org/g4l-v0.56alpha20-fc28.iso
I rebuilt the bz4x19.6 kernel with all the NVME options (except one for andriod) set to yes
The above messages seem to confirm that the last message before the freeze was the last process that ended successfully, and the freeze happens before info is displayed??
I don't have any physical NVME disks, so had only done testing with the VirtualBox NVME disks, and was able to get it to work just fine. Only had the basic NVME option set in kernel. Have not turned on about 7 more options. cat bz4x19.6.config | grep NVME will show them.
Don't know if that will solve the problem, or at least get it to show info or do nothing different.
What version of partedmagic are you using? I knew it had an older version that included g4l, but thought later versions didn't have it? Not sure if it includes the kernel .config file they use, but it might be interesting to see if there? Don't know if it might be some firmware issue. I have included some special firmware files that users needed, but don't know if NVME drives require any, and if so, why it wouldn't show some message rather than freezing.
Hi
Thank you for the ongoing efforts!
I now download alpha20-fc28.iso to flash drive and i select the 19.6 kernel it says 0.56a in the menu
but strange it seems same stop at ata8 PATA max PIO4 cmd 0x170 ctl 0x376 irq 15
i try also with tab debug parameter
PM removing info for no bus ata8
bus platform remove device pata_legacy.1
pm removing info for platform pata_legacy.1
device dummy0 device_add
pm adding info for no bus dummy0
freeeze
not sure if i do something wrong?
Is there something else I can try?
Thanks.
At this point, with the kernel not reporting any specific errors, it is kind of a shot in the dark.
Here are some things that might be worth trying. Not sure which order would be best to try.
I've seen on the syslinux list that some systems have issues with the actual bios code, and seeing if a new bios is available for the machine might make flashing the bios to the latest version. Have had bios updates solve various problems.
Might be some bios setting? At the college, we got some machines a few years ago, and they would not boot the g4l or the linux? Found in the bios it had an Enhanced boot option that was set on by default. Turning that back to the standard option made everything work just fine. Windows booted and ran fine. Ran disk benchmarks with the Enhanced and stand options and got exactly same results. So, with the disks in those machines it made no difference. Might have been with higher grade disks it would have done something, but was not compatible with g4l or linux. Did a similar just freezing wth no error.
Did a boot on my virtualbox test, and looked at dmesg. It only reported ata1, so not sure why yours is going all the way up to ata8? Even so, since we tried a kernel with all the ata stuff removed, it still froze with just another message.
Could be an issue with the syslinux boot loader with the configuration. I've also run g4l from a usb using grub4dos instead of the syslinux that the iso uses.
Have files that have less stuff, just the single latest kernel.
ftp://setzco.dyndns.org/g4l-lite-fc28.exe
That is a self-extracting 7z file.
You can extrat the files to a flash disk, and it includes the grub4dos programs to make the flash bootable. Seems to work great with linux, but sometimes windows doesn't actually make the flash bootable?? Believe there is a file that explans the process??
So, I would probable start with the BIOS settings, and see if there are any settings that might be causing the issue.
Last thing, is it could be some kind of EFI setting. The g4l kernels don't have the special signature for EFI boot, so if the machine is setup to only boot signed kernels, that might be it. We didn't use EFI boot at the college or on my own machines, and had some users that did, but they could turn off the option, make the image, and then turn it back on.. Syslinux has had a lot of discussion about it, and there are some people playing with it, but it is above my level at this time..
Had a user with a notebook that had other issues. I tried to go the makers site (don't recall), but to even asks for help they wanted a machine serial number and a service contract. I think a bios upgrade eventually solved that problem.
Good Luck.
Let me know if you come across anything that helps.
Also, a later version of bz4x19.7 kernel
ftp://setzco.dyndns.org/g4l-v0.56alpha21-fc28.iso
The source for the build.
ftp://setzco.dyndns.org/g4l-v0.56a21-fc28.devel.tar.xz
Hi
1: Its a thinkpad t440p just installed latest BIOS but no difference
2: to look for something to disable in the BIOS do you know more specific what it could be?
All the secure boot is off since it boots linux ubuntu/mint mainly
3: I copied the g4l-lite-fc28.exe to the usb stick on another windows machine and it extracted but it is not making it bootable tried using grub4dos but could not get it bootable
4: trying the g4l-v0.56alpha21-fc28.iso and stops same ata8 PATA max PIO4 cmd 0x170 ctl 0x376 irq 15
In the bios I have set
UEFI/Legacy boot to legacy only
then i boot g4l 056 aplha 21 fc28 again
i select safe menu
press tab
add debug
and it just same after ata8 pata max pio4 cmd 0x170..
it goes device host 6 device unregister
bu scssi remove device host 6
then ending at
device dummy0 device add
pm adding info for no bus dummy0
Last edit: ben 2018-12-08
Asked if anyone on syslinux knew of something that might help find the error.
Only got one reply so far. It kind of confirmed it must be whatever is checked after the test that is displayed, but don't know of a way to know what the thing after that would be. Checked the dmesg of my virtual box boot, and it only shows ata0 as being part of boot, but is a very simple option.
The message did mention that one might do something.
Use the mem= boot option to limit the amount of ram it is seeing.
Don't know if that would make a difference or not.
Tested it on my machine using Virtual box.
VirtualBox is configured to give 1G of ram to the boot, but if I add the mem=256M to the boot
usign (tab and then adding mem=512M. The system boots, and top only reports the 512M.
How much ram does the system have?? The g4l should work fine 256 - 512M. It creates a 128M ramdisk for the file system, but then just needs ram to run OS.
One other option in bios might be. Loading the video card membery, my one system has an option to load it above the 4G level. Since the g4l kernels are 32 bit, not sure if that would be an issue. Log ago, made a 64bot biuld, but it was a major project. Building the kernel wasn't a big deal, but then getting all the 64bit programs and libraries was a lot. Then did a test, and saw no significant change in size or speed.
Might also, be interestign to try hooking it to an external monitor? The kernel only uses basic video, and perhaps the monitor isn't supporting that vaa level..
Might want to boot, and add the command line option vga=ask, and try some of the vesa modes with the notebook screen, adn with a monitor.
When it freezes, does pressing the caps look or num lock key result in the lights changing??
Hi
I just boot now
The laptop has 16 gb ram
1: I press tab add mem=256M
same stuck ata8 pata max pio4...
2: I reboot again add mem=512M
same stuck ata8 pata max io4...
3:When I go in the bios i can choose thinkpad lcd total graphics memory 256 MB or 512 i tried It was on 512 i tried put it to 256 and then also use mem=256 but just the same
Having a hard time getting any info on finding the issue, but here is one more thing to try.
Looked at the kernel build options and found two little config settings that might get more info.
CONFIG_DEBUG_KOBJECT=y
CONFIG_DEBUG_NOTIFIERS=y
before the options were not set to y, but inactive. Have turned them on with the
bz14x19.8 kernel only.
The other option would be to use the tab key, and add the loglevel=15 to the boot line.
The default loglevel is 7,but it doesn't explain what the different levels do?? 15 is the max, and produces the most messages, so hopefully, it will show more info.
ftp://setzco.dyndns.org/g4l-v0.56alpha23-fc28.iso
You didn't mention if you had tried the grub4dos boot option?
Or what happens to the caps and numlock lights after the freeze.
Hi
Thank you for the ongoing efforts.
I now write 0.56alpha23 to the flash drive booting
1: I boot choose bz14x19.8 kernel same freeze ata8 pata max pio4 cmd 0x170
2: i boot again press tab and add loglevel=15
pm adding info for no bus dummy0
kobject dummy0 kobject uevent env
kobject dummy0 fill kobj path path devices virtual net dummy0
kobject queues kobject add internal parent dummy0
kobject queues kobject uevent env
kobject kobject add internal parent queues
kobject kobject uevent env
kobject fill kobj path path /devices/virtual/net/dummy0/queues/tx-0
3: did not try grub4dos could not get it to make the flash drive bootable
4: keyboard is complete dead after freeze nothing i press will work only thing i can do is hold down power button to it power off