xwin refuses to start when booting F96-CE <Solved>

[simfann]

I use fossapup64-9.5 for more than half a year without problems booting from lick boot loader. As a part of the boot process "xwin" also works fine. Now I want to change to newer F96-CE (fossapup64-9.6) and use the same boot process (lick boot loader), but booting stops always at "xwin". Then I get the console info, that "xwin" just has run and I should type "xorgwizard" or "xwin -default". When typing "xwin -default", "xwin" tries again to work, but stops after a short while with the above mentioned info. When typing "xorgwizard", I can change video settings. I tried many different settings but nothing helps. Booting with or without external monitor makes no difference. Although I don't think, that the boot loader has anything to do with the problem, because fossapup64-9.5 boots fine with it, I want to mention it here, to give complete information.

Can anyone help me please?

Used operating system: F96-CE_4
Boot loader: LICK-1.3.4-win32

Here some of my computer facts:

-Computer-
PC Manufacturer: Hewlett-Packard
Product Name: HP 350 G2
Processor : Intel(R) Core(TM) i5-5200U CPU @ 2.20GHz, 2 cores, 4 threads
Memory : 3939MB (1830MB used)
Machine Type : Notebook

-Display-
Resolution : 3046x1050 pixels
OpenGL Renderer : Mesa Intel(R) HD Graphics 5500 (BDW GT2)
-Monitors-
Monitor 0 : 1366x768 pixels (internal)
Monitor 1 : 1680x1050 pixels (external)
-OpenGL-
Vendor : Intel
Renderer : Mesa Intel(R) HD Graphics 5500 (BDW GT2)
Version : 4.6 (Compatibility Profile) Mesa 20.0.8
Direct Rendering : Yes

[rockedge]

@simfann I think this might be the fdrv firmware SFS is missing your graphic device driver or the kernel is not configured for your display graphics.

Should try to swap the kernel from Fossapup64-9.5 into F96-CE_4, replacing that kernel.

First swap the fdrv SFS from the working Fossapup64 into F96-CE_4 and reboot.

Let's see what happens!

[simfann]

Thank you so much for your fast help. Swapping the fdrv SFS from the working Fossapup64-9.5 into F96-CE_4 has really brought the solution.

[simfann]

I must still add here an important information:
Swapping the fdrv SFS from the working Fossapup64-9.5 into F96-CE_4 has caused a new problem: WLAN networks couldn't be found, although hardware and driver were found by all configuration programs. I experimented a lot until I found the following solution:
1) Booting with fdrv SFS from the working Fossapup64-9.5 (original fdrv SFS renamed! --> "xwin" works
2) Deleting fdrv SFS coming from the working Fossapup64-9.5
3) Renaming original fdrv SFS to original name
4) Reboot with a save file
5) The following boot leads to a working "xwin" (derived from save file?) and WLAN configuration shows now all available networks and connecting also succeeds.
6) What I've found in the meantime is however frustrating: Next boot after step 1) ... 5) there is the same "xwin" problem as before. Then you have to go again through steps 1) ... 5).

The above listed solution is therefore really not good! I'm hard working, to find a better solution, for example finding the problematic xwin driver. Has anyone else another idea or help?

[simfann]

Heureka! After a long time I've found now no easy but a stable solution:
1) Install Fossapup64-9.5
2) Boot with Fossapup64-9.5 and copy fdrv_fossapup64_9.5.sfs from Fossapup64-9.5 to F96-CE
3) Rename fdrv_fossapup64_9.6.sfs to fdrv_fossapup64_9.6.sf (making inactive)
4) Reboot with F96-CE, rename fdrv_fossapup64_9.6.sf to fdrv_fossapup64_9.6.sfs (making active again) and rename fdrv_fossapup64_9.5.sfs to fdrv_fossapup64_9.5.sf
(making inactive)
5) Reboot with a save file F96-CE and all works fine, but
6) Reboot again with F96-CE and xwin stops the boot process
7) Reboot with Fossapup64-9.5 and open save file of F96-CE and edit /etc/x11/xorg.conf as follows:
Whatever is written in 'Section "Device"' overwrite it with:

Section "Device"
Identifier "Card0"
Driver "modesetting" #card0driver
BusID "0:2:0" #card0busid
EndSection

This solution was derived from "Fossapup Tips & Tricks" of Fossapup64-Forum
7) Reboot with F96-CE and from now on everything works fine!