Can't boot Salix -Openbox-14.1 on AMD K6-2 machines

[junqueman]

On bootloader command line, e.g. for runlevel 3: The_Kernel_Name 3

Thanks.

A noob who uses Virtualbox but does not know what runlevels are.

Yeah, I'm beginning to see I'm an odd case. Sorry; I'm trying to learn.

Then this Firefox is not for your AMD K6.

OK. I used Slapt Package Manager to install Midori, thinking I may have better luck with it. I launch it and briefly see a window, but it promptly dissappears.

Looks like no echo. A mis-configuration, perhaps. Correct it or try other terminal emulations.

I went into Preferences for LXterminal and saw no options for turning echo on/off, or changing emulation. Do you mean that I should try installing a different terminal program?

To /etc/X11/xorg.conf.d add the files:

50-serverflags.conf (file edited out by junqueman for brevity)

50-files.conf (file edited out by junqueman for brevity)

50-module.conf (file edited out by junqueman for brevity)

50-extensions.conf (file edited out by junqueman for brevity)

Perhaps it helps. And don't be stupid and type all this in. Copy it to files on a full working system and move the files to the HOH. There are more files to be add. But for the moment...

OK, I did this the smart (or at least a smarter) way. However, upon rebooting the login screen became unreadable, so I had to disable the files (I added a meaningless extension by editing the filenames from Puppy Linux) to get back to where I was. I copied the files you provided directly so no possibilities of typos, at least not mine.

By the way, even before I added those files, once I started booting Salix from the hard drive using grub the text that appears on the display before the (graphical) login screen is displayed, and upon shutdown, became unreadable, which is why disabling the new files from tty in Salix was not an option. The last readible text during startup is "Loading Linux 3.10.17."

I'm impressed at how you come up with these suggestions. Did this come directly from your brain, or did you have to look it up? If the latter, how do you know what to look for and where to look?

With the older kernels, on both machines:
cat /proc/cpuinfo

Ah, OK. What I did before you responded with this suggestion was to run AniX-16 from live CD, which offers the inxi command. Here is the output from inxi -Cf:

CPU: Single core AMD-K6 3D (-UP-) cache: 64 KB speed 314 MHz (max)
CPU flags: 3dnow 3dnowprefetch CX8 de fpu K6-mtrr max msr pge pse
syscall tsc vme vmmcall

The flags in plain text are the ones in the list from the other K6-III machine in which I could not get beyond the ISOLINUX boot: prompt, and also represent the complete list of CPU flags displayed when I executed the same command on that machine. The flags in bold are new ones not seen on that machine.

And, for completeness, here is the output from inxi -Fxx on the current machine:

System: Host: antix1 Kernel: 4.4.10-antix.1-486-smp i586 (32 bit gcc: 4.9.3)
Desktop: IceWM 1.3.8 dm: slim
Distro: antiX-16-b5_386-full Berta Cáceres 19 May 2016
Machine: No /sys/class/dmi; using dmidecode: you must be root to run dmidecode
CPU: Single core AMD-K6 3D (-UP-) cache: 64 KB
flags: (-) bmips: 629 speed: 314 MHz (max)
Graphics: Card: Silicon Integrated Systems [SiS] 86C326 5598/6326
bus-ID: 01:00.0 chip-ID: 1039:6326
Display Server: X.Org 1.16.4 driver: N/A
Resolution: 1024x768@60.00hz
GLX Renderer: Gallium 0.4 on llvmpipe (LLVM 3.5, 128 bits)
GLX Version: 3.0 Mesa 10.3.2 Direct Rendering: Yes
Audio: Card Ensoniq ES1371 / Creative Labs CT2518 [AudioPCI-97]
driver: snd_ens1371 port: df00 bus-ID: 00:0a.0 chip-ID: 1274:1371
Sound: ALSA v: k4.4.10-antix.1-486-smp
Network: Card: ADMtek NC100 Network Everywhere Fast Ethernet 10/100
driver: tulip v: 1.1.15-NAPI port: dc00
bus-ID: 00:09.0 chip-ID: 1317:0985
IF: eth0 state: unknown speed: N/A duplex: N/A
mac: 00:0c:41:21:8d:05
Drives: HDD Total Size: 6.4GB (7.9% used)
ID-1: /dev/sda model: Maxtor_86480D6 size: 6.4GB serial: L60A89HA
Partition: ID-1: / size: 232M used: 1.8M (1%) fs: overlay dev: N/A
ID-2: swap-1 size: 0.54GB used: 0.00GB (0%) fs: swap dev: /dev/sda2
Sensors: System Temperatures: cpu: 48.8C mobo: N/A
Fan Speeds (in rpm): cpu: 0 fan-2: 0
Info: Processes: 95 Uptime: 23 min Memory: 63.2/306.8MB
Init: SysVinit v: 2.88 runlevel: 5 default: 5 Gcc sys: 4.9.2
Client: Shell (bash 4.3.301 running in roxterm) inxi: 2.3.0

Thanks for all your help. I hope I'm not frustrating you too badly with my noobiness. If you get tired and want to leave this "project" at any time I'll understand and be grateful for all the assistance you've given me.

[westms]

OK. I used Slapt Package Manager to install Midori, thinking I may have better luck with it. I launch it and briefly see a window, but it promptly dissappears.

Before the launch of Firefox or Midori and after the run sift through log files, and notice the differences.
The log file .xsession-errors in home directory and furthermore, the following log files:
/var/log/dmesg (with program call dmesg as superuser)
/var/log/messages
/var/log/syslog
/var/log/debug

I went into Preferences for LXterminal and saw no options for turning echo on/off, or changing emulation. Do you mean that I should try installing a different terminal program?

Can say nothing more to it. Both the program crashes of Firefox and Midori, and this behavior may be due to improper compilation of programs for this old CPU.

OK, I did this the smart (or at least a smarter) way. However, upon rebooting the login screen became unreadable, so I had to disable the files (I added a meaningless extension by editing the filenames from Puppy Linux) to get back to where I was. I copied the files you provided directly so no possibilities of typos, at least not mine.

What is it meaning: unreadable? I don't know how it looks for Openbox/Fluxbox.

How can one disable files? One can move or delete them.

What does it mean: I added a meaningless extension by editing the filenames from Puppy Linux ?
The file names can be chosen almost freely ([1-9][0-9]-*.conf).

By the way, even before I added those files, once I started booting Salix from the hard drive using grub the text that appears on the display before the (graphical) login screen is displayed, and upon shutdown, became unreadable, which is why disabling the new files from tty in Salix was not an option. The last readible text during startup is "Loading Linux 3.10.17."

When the boot loader hands over control to the kernel, then the output is shown in a VGA mode, which was given to him in a data structure from the bootloader. "Loading Linux 3:10:17" still comes from the bootloader. Thereafter, when there is nothing to read, then you have set a wrong or not supported VGA mode in GRUB2.

Once you have solved the display problem, you can reapply the files. Then, when a X server malfunction occurs, you can search in log file /var/log/Xorg.0.log for error messages. The log file can be transported to a functioning system for later analysis too.

CPU: Single core AMD-K6 3D (-UP-) cache: 64 KB speed 314 MHz (max)
CPU flags: 3dnow 3dnowprefetch CX8 de fpu K6-mtrr max msr pge pse
syscall tsc vme vmmcall

3dnowprefetch is probably not important. max does not exist. Perhaps you mean MMX. MMX is included in 3DNow!. In vmmcall I'm not sure. VMMCALL describes a property that can actually be used only useful in ring 0.

Added: The in my opinion best way to get here on, is a Salix reinstallation in full mode, which uses the LILO. With the full mode, the necessary programs are available. LILO has good default settings and will work quite safe. Thus, the artificially created GRUB2 problem is eliminated and it is possible to take care of the real problem.

Second addition: For Salix Xfce 14.1, the kernel has been configured for use with the CMOV feature. That suggests that applications have been translated the same way. If the Fluxbox / Openbox versions were configured for use with the CMOV feature, too, they are not suitable for those old computers.

The kernel huge.s from the distribution salix-xfce-14.2beta1.iso is configured without using the CMOV feature. Also other by the CPU not provided features have been omitted in this configuration. Thus, the Salix Xfce 14.2beta1 would be suitable for this old computer.

[junqueman]

Before the launch of Firefox or Midori and after the run sift through log files, and notice the differences.
The log file .xsession-errors in home directory and furthermore, the following log files:
/var/log/dmesg (with program call dmesg as superuser)
/var/log/messages
/var/log/syslog
/var/log/debug

OK, thanks. I haven't had a chance to do this yet, though; I've had very limited time recently for this "project."

What is it meaning: unreadable? I don't know how it looks for Openbox/Fluxbox.

In Fluxbox my login screen has a solid blue background, with a box in the center for entering the username (and in the next screen, password). With those new .conf files you suggested I add I got a gray box full of dots and vertical lines, and no visible field in which to enter my username.

How can one disable files? One can move or delete them.
What does it mean: I added a meaningless extension by editing the filenames from Puppy Linux ?
The file names can be chosen almost freely ([1-9][0-9]-*.conf).

What I did was to add something like ".dis" after the filename. i.e., *.conf would be changed to *.conf.dis, and the file would then be ignored. That is what I meant by "adding a meaningless extension." That way, if I want to re-enable the file all I need to do is delete the ".dis" at the end. It's less work that way when experimenting.

When the boot loader hands over control to the kernel, then the output is shown in a VGA mode, which was given to him in a data structure from the bootloader. "Loading Linux 3:10:17" still comes from the bootloader. Thereafter, when there is nothing to read, then you have set a wrong or not supported VGA mode in GRUB2.

I didn't change the VGA mode from the default one after installing GRUB2. Will have to explore that. Although this new-old computer is capable of booting more distros, the SiS 6326 video chip doesn't seem to be handled well.

Once you have solved the display problem, you can reapply the files. Then, when a X server malfunction occurs, you can search in log file /var/log/Xorg.0.log for error messages. The log file can be transported to a functioning system for later analysis too.

OK. Been there, done that, just not for this problem yet (because of the display issue you've indicated is coming from GRUB.)

3dnowprefetch is probably not important. max does not exist. Perhaps you mean MMX. MMX is included in 3DNow!. In vmmcall I'm not sure. VMMCALL describes a property that can actually be used only useful in ring 0.

You're correct, it's mmx. My mistake.

Added: The in my opinion best way to get here on, is a Salix reinstallation in full mode, which uses the LILO. With the full mode, the necessary programs are available. LILO has good default settings and will work quite safe. Thus, the artificially created GRUB2 problem is eliminated and it is possible to take care of the real problem.

Second addition: For Salix Xfce 14.1, the kernel has been configured for use with the CMOV feature. That suggests that applications have been translated the same way. If the Fluxbox / Openbox versions were configured for use with the CMOV feature, too, they are not suitable for those old computers.

The kernel huge.s from the distribution salix-xfce-14.2beta1.iso is configured without using the CMOV feature. Also other by the CPU not provided features have been omitted in this configuration. Thus, the Salix Xfce 14.2beta1 would be suitable for this old computer.

Would the kernel for Salix Openbox or Fluxbox 14.1 be different for 14.1 Xfce in their use of CMOV? Because those boot from the CD and install without issue; the problems that occur are with some specific applications, and the display issues that we've discussed.

In any case, when I again have some time I'll try installing Salix Xfce 14.2 beta1 and see if I have better luck. I'll cross my fingers and install LILO when I do.

[junqueman]

UPDATE:

I've installed Salix-xfce-14.2-beta1 on the 350 MHz AMD K6-3D machine. With this version the sis driver package was installed automatically, and the login screen came right up. Once in the desktop, there were some annoying display problems with many of the application windows, but creating the previously-discussed file /etc/X11/xorg.conf.d/50-device-sis6326.conf seems to have resolved them. Also, and happily, the problem I had experienced in Salix Fluxbox 14.1 with the terminal window not echoing my typed characters is gone.

The web browser (Firefox?) still won't run. This time I am getting an error window displaying ""Failed to execute default Web Browser" and below that within the same window "input/output error."

Progress nonetheless.

I also tried booting 14.2-beta1 on the 366 MHz AMD K6-III box I had originally been playing with and it still returns "aborted." when attempting to launch "English-US-noPAE" at the Isolinux boot: prompt. So whatever prevented 14.1 Fluxbox and Openbox from getting past that point still exists in xfce-14.2.
(The menu for launching the different available kernels displays but is nonfunctional in this machine, too. The kernel names aren't highlighted with the up or down arrow keys, and the cursor is at the boot: prompt. Hitting the Tab key gives a list of the kernel option names which can be entered at the boot: prompt.)