LinuxQuestions.org - slackware-live-{xfce-,}current.iso’s do not boot on my i7/6700 box

- Slackware (https://www.linuxquestions.org/questions/slackware-14/)

- - slackware-live-{xfce-,}current.iso’s do not boot on my i7/6700 box (https://www.linuxquestions.org/questions/slackware-14/slackware-live-%7Bxfce-%7Dcurrent-iso%92s-do-not-boot-on-my-i7-6700-box-4175609151/)

slackware-live-{xfce-,}current.iso’s do not boot on my i7/6700 box

Slack64 Current XFCE + some Mate -- Intel i7/6700

Every once in a while I need to compile a program for 32-bit.
I never liked maintaining a separate 32-bit install for this.
For quite some time I used Alien Bob's multilib with a quite long list of 32-bit packages. Not all packages turned out to be buildable this way -- IIRC especially packages referring to Python or Perl were affected.
As the "while" as mentioned above became longer and longer the maintenance overhead became disproportional. And in the meantime the Slackware live CD's had become available. So I switched to using the 32-bit ISO's (dd'ed to USB) instead.
After half a year or so I had to compile a 32-bit program again. Alas I found that the current slackware-live-{xfce-,}current.iso’s no longer boot my new i7/6700 box, whereas they did so successfully on my old i7/2600 one. The screen is as follows:

Code:

loading /boot/generic......

loading /boot/initrd.img.......................ready.

early console in extract_kernel

input_data: 0x0175e069

input_length: 0x003d090f

output: 0x01000000

output_length: 0x0099b3a0

kernel_total_size: 0x00b43000



Decompressing Linux... Parsing ELF... done.

Booting the kernel.

And that is it, no activity any more and complete silence -- only a hard boot is possible.
As this seems to be very early in the boot sequence I would not know how to debug this.

The last 32-bit ISO's available are from 170512. As I suspected the firmware to be somewhat outdated I genned the current (170630) one (via make_slackare_live.sh and friends). Alas the problem persisted.
With quite some trial and error I found that the only kernel booting through is the huge SMP one (from the a/kernel-huge-smp-4.9.35_smp-i686-1.txz pacakge). And after adding the /lib/modules (from the a/kernel-modules-smp-4.9.35_smp-i686-1.txz package to the initrd I was able to build the 32-bit package.

You may need to pass nomodeset to the kernel boot parameters as the newer Intel video cards have been known to be problematic with various Linux drivers out there.

Thank you for responding.
I did not say so but the "nomodeset" workaround was the first thing I tried when I saw the problem a week ago or so. See http://www.linuxquestions.org/questi...et-4175604079/ for details. I then tried with updating the firmware, but to no avail too.
:D

Is this connected to the internet using wifi or ethernet? If it is ethernet, have you checked to see if it completes the bootup by trying to ping it or using ssh to log in?

It is on my LAN (nothing big) and I tried to ping it: no response.
As I see no disk light, hear no sounds and see no outputs I assume the problem to be early in the kernel boot sequence ...

When reading back this thread I notice that I did not mention that the DVD and USB boot successfully on my other desktop (Celeron) and laptops (Core Duo and an early I5). So things really have to do with this I7/6700 ...

Actually I can live with the situation as it now is. If someone wants to follow-up I am in. But if noone is interested right now things are at least recorded.
:D