search

helloSystem / ISO

helloSystem Live and installation ISO
https://github.com/helloSystem/
BSD 3-Clause "New" or "Revised" License
808 stars 58 forks source link

[0E163] Installed system: Read-only file system, no Xorg #203

Closed schusz closed 3 years ago

schusz commented 3 years ago

Describe the bug Non-responisive dark screen after having booted installed system.

To Reproduce Steps to reproduce the behavior:

  1. boot Live USB
  2. Install to disk
  3. Reboot when installation finished
  4. Result when boot completed: black non-responive screen

Expected behavior I expect the same desktop as when booting from the Live USB

Screenshots N.A.: black screen (actually somewhat lighter than black)

Version (please complete the following information):

Computer (please complete the following information):

Additional context About this computer:

Dell Inc. Latitude E4300 FreeBSD 12.2-RELEASE r366954 GENERIC Kernel version: 1202000 Processor: Intel® Core™2 Duo CPU P9400 @ 2.40GHz Memory: 6 GiB Startup Disk: 59 GiB helloSystem build: 0E163 for commit: cba9edc

probonopd commented 3 years ago

Thanks @schusz.

Can you please do a verbose boot, do you see any error messages?

Also, do you hear the welcome sound playing while you see the black screen?

schusz commented 3 years ago

@probonopd I don't hear the welcome sound. The machine responds to ping when connected to LAN. It refuses an ssh connection, even though I checked the ssh box when installing to hard disk.

During verbose boot in the final part I noticed a reference to a graphics driver: After the last line on the photo the screen turns black and nothing further happpens. photo_2021-04-10_01-14-17

If needed I have a video screenrecording of the verbose boot I could send you.

probonopd commented 3 years ago

"Read-only file system" seems to be the culprit.

I was hoping that https://github.com/helloSystem/ISO/commit/aed27b945fb8826592281b7b1d91190d1a9d79d4 would have solved this, but I had done things in the wrong order. The next build should hopefully fix this. Sorry!

schusz commented 3 years ago

@probonopd /etc/rc.conf has line

root_rw_mount="NO"

And the file is read-only, so I am not able to change it to root_rw_mount="YES"

schusz commented 3 years ago

@probonopd I will install hello-0.5.0_0E166-FreeBSD-12.2-amd64.iso and hello-0.5.0_0E165-FreeBSD-13.0-amd64.iso and let you know the result.

schusz commented 3 years ago

@probonopd

Installed hello-0.5.0_0E166-FreeBSD-12.2-amd64.iso:

Installed hello-0.5.0_0E165-FreeBSD-13.0-amd64.iso:

Live version of hello-0.5.0_0E165-FreeBSD-13.0-amd64. still has split screen.

probonopd commented 3 years ago

If

/etc/rc.conf: root_rw_mount="YES"

then why

file '/etc/rc.conf' is unwritable

Hmmm.

Please try Ctrl-Alt-F2, then

sudo mount -uw /
sudo service slim restart
schusz commented 3 years ago

@probonopd I booted in single user mode, then pressed Ctrl-Alt-F2 and executed

sudo mount -uw /
sudo service slim restart

Resulting in short (2 sec) display of a garbled image (attached photo), and next a black, unresponsive screen again.

photo_2021-04-11_15-25-33

dotdash70 commented 3 years ago

I can confirm similar behavior on a Dell Vostro 1014. 141 works on this laptop, 163 boots and lets me install to the HDD, but upon restart X never starts, just a black screen. I can get a text prompt with ctrl-alt-f2. This laptop has Intel Mobile 4 Internal Graphics and the minimum 4 GB of ram. (Which is the max it supports) I didn't check if the filesystem was RO before reverting back to 141.

probonopd commented 3 years ago

"Read-only file system" seems to be the root cause but I don't know yet what is causing it. With a read-only file system, initgfx cannot configure the GPU.

schusz commented 3 years ago

@probonopd So when I boot in single user mode, press Ctrl-Alt-F2, and open /etc/rc.conf, it is is read-only. Then I do:

# zfs set readonly=off zroot
# zfs mount -a

Now /etc/rc.conf is writable. Attached rc.conf.jpg. rc conf

Then, however, when I do:

# sudo slim service restart

It again shows the garbled screen and then the black screen.

I'm afraid I lack the knowledge to investigate further, and need expert help.

schusz commented 3 years ago

@probonopd Installed 0E174-12.2 also boots into black screen.

antonpat commented 3 years ago

Not sure if it belongs here, or if I should start a new issue, but my installation of hello-0.5.0_0E177-FreeBSD-13.0-amd64 stalls here:

PXL_20210414_112920647

UPDATE: The latest experimental-12.2 behaves the same way.

ChasinHooDoos commented 3 years ago

Hello,

I confirm I've seen this exact display behavior on version E163 and newer versions up to E173.

E163 and newer were run as virtual machines on VMware Fusion 11.5.7. To test that Fusion was not the problem, version E173 was directly installed on a MacBook Pro 15" late 2013 laptop. Same display problem as running virtual. E150 ran correctly as a virtual machine on Fusion 11.5.7.

Thanks for all your work ! The HelloSystem team is making great progress! Best regards, C

ChasinHooDoos commented 3 years ago

To clarify prior post ... After installing FreeBSD to disk and rebooting, the black screen displays with no sound and no response to keyboard inputs, Ctrl-C, Ctrl-D, Ctrl-Z. Did not try Ctrl-Alt-F2.

C

probonopd commented 3 years ago

My problem at the moment is that I can't even get 0E177 and 0E178 installed due to https://github.com/helloSystem/ISO/issues/200.

@ChasinHooDoos Live mode is working for you? (It is for me.)

schusz commented 3 years ago

@probonopd Live mode is working for me too. The installed version boots into a black screen. When I press Ctrl-Alt-F2, I get a FreeBSD login prompt. Login fails when I use the username and Password that I created during the installation. When I start in verbose single-user mode Ctrl-Alt-F2 does not work.

schusz commented 3 years ago

Correction on my previous post: in verbose single mode I have root access. Ctrl-Alt-F2 does not work, but when I do:

zfs set readonly=off zroot

zfs mount -a

Ctrl-Alt-F2 ís working.

probonopd commented 3 years ago

So the question is, what caused zfs to become read-only in the first place...

ChasinHooDoos commented 3 years ago

Tonight I installed E181-13 and had same black screen as described in the prior posts.

However, I followed some of the clues from the prior posts and got a fully functional root user display and regular user display working. This is how to mitigate the problem as I don't know the actual cause. If I had access to the build scripts or whatever the automated tools, I might stumble upon the cause.

The live system works as expected. Install FreeBSD onto hard disk, then restart, and wait for the black screen with no sound. As described by 'schusz', restart system, interrupt the boot process by pressing a key (space bar), the enter single user mode with 'boot -s'. Then enter

zfs set readonly=off zroot

zfs mount -a

Then I looked at various files to see what might appear odd. Found a clue here: https://forums.freebsd.org/threads/why-is-only-swap-in-fstab-after-install.68207/

So I added two lines to /boot/loader : vfs.root.mountfrom="zfs:zroot/ROOT/default" Then for good measure (this next line may be redundant) ... vfs.root.mountfrom.options="rw"

Then created password for root: passwd root new password new password again

Next, added line to /etc/rc.conf ; dbus_enable="YES" And, confirmed this line existed : slim_enable="YES"

exited and restarted system. Appears to be working as expected. Of course, we still have 'probonopd' same question ..."what caused ZFS to become read-only in the first place?" It seems the next logical step is to examine the scripts (or other automation) that start the boot process, mount filesystems, and populate the configuration files (/etc/rc.conf and /boot/loader.conf).

goodnight for now.

C

probonopd commented 3 years ago

Thanks @ChasinHooDoos, very useful.

Tonight I installed E181-13

So you manged to install 0E181. How? I am always running into https://github.com/helloSystem/ISO/issues/200... did you do anything special? Did you use the GUI or the CLI to install?

probonopd commented 3 years ago

Strange, my (older) installed system has no password for root, no vfs.root.mountfrom and no vfs.root.mountfrom.options="rw" in /boot/loader.conf and a completely empty /etc/fstab. Not sure what's going on. I wonder whether having done vfs.root.mountfrom.options="rw" would have been sufficient in your case.

probonopd commented 3 years ago

Let's see whether the next builds are working for you.

dotdash70 commented 3 years ago

I gave it another go using the 182 iso. First I'll note a quirk of my test machine in case it's significant: This laptop sits at zfs recv -F livecd for about 10 minutes when booting from the live USB image. I booted the live USB, installed and rebooted. Black screen. pulled up a tty using ctl-alt-f2, logged in with newly created user. File system is RW. ps shows slim running. If I kill the process, I can run startx and get a 90's circa black and white desktop going. The last line of slim.log shows 'failed to connect to socket /var/run/dbus/system_bus_socket: no such file or directory' . I added dbus_enable="YES" then rebooted. The system is now working. It seems my only problem was dbus not running.

schusz commented 3 years ago

@probonopd @adriaandegroot I tried Adriaan's solution and added dbus_enabled="YES" to /etc/rc.conf. Didn't have to add vfs.root.mountfrom.options="rw" to /boot/loader.conf

Upon reboot it booted nicely into the GUI :-).

I am not sure anymore which installed version of helloSystem it was. I think E163.

System info: --snip Dell Inc. Latitude E4300 FreeBSD 12.2-RELEASE r366954 GENERIC Kernel version: 1202000 Processor: Intel® Core™2 Duo CPU P9400 @ 2.40GHz Memory: 6 GiB Startup Disk: 149 GiB FreeBSD copyright information Other components are subject to their respective license terms --snip

I will give hello-0.5.0_0E184-FreeBSD-12.2-amd64.iso a try this evening.

ChasinHooDoos commented 3 years ago

Good morning ... Installed E183-13 this morning ... and HelloSystem live displayed fine. Installed FreeBSD and rebooted. All good. The HelloSystem splash screen played sight & sound as desired, then displayed functional window with expected icons. The Falkon browser ran ok and I was able to access public websites. As the regular user, I opened terminal and installed Firefox browser with this command 'sudo pkg add firefox'. Worked fine ... even added extensions. Next, downloaded and started Audacity fine. Rebooted system and all was still working as expected.

Next, installed E182-12.2. Boot messages appeared (as expected), then system stalled at black screen with white block cursor in top left corner of screen. Waited over 10 minutes. Never reached Live system. Tried several times, but no luck. Next, installed E184-12.2. Booted ISO, boot messages appear, stalls with black screen, then issues a 'fault message'. Tried 3 times. Never reached Live HelloSystem.

That is all for now. I've got to get some coffee. C

schusz commented 3 years ago

@probonopd Installed E184-12.2 without any problem.

Installed E183-13.0; Live boots into GUI, but still with split screen with only bottom half of Global Menu showing. Same with installed version.

probonopd commented 3 years ago

Thanks for re-testing.

The split screen is a separate topic which we will discuss in its own issue.