Neither TinyCore nor CorePlus 4.7.7 will boot without option "nofstab"

[mirimir]

I'm working on a new machine with an msi B85M-P33 motherboard (USB 3.0, SATA 6Gb/s) with a Core i5 4430 3.0GHz quad-core CPU, 8GB RAM, and a 1TB Hitachi HDD. CDs with TinyCore-4.7.7.iso or CorePlus-4.7.7.iso won't boot unless I add the boot option "nofstab". Without that option, boot hangs after the USB device lines. With the boot option "nofstab", I get to "tc@box:~$". Executing "startx" does nada. But if I first execute "sudo /usr/sbin/rebuildfstab" and "sudo /etc/init.d/tc-config", "startx" gives me the desktop.

What's the best way to fix this?

[curaga]

That's a very recent system (June 2013 Haswell). Please try the 5.0 series, as it has a more recent kernel.

[coreplayer2]

I can confirm tc-5.x boots the new Intel Haswell systems perfectly

[mirimir]

@curaga

Thank you. I did suspect that.

I picked 4.7.7 because there's a tcz for VirtualBox, and I didn't see one in 5.0 rc1. I want to use ezremaster to create a LiveCD with VirtualBox and a few VMs. Is there a tcz for 5.0? If not, what would it take to build one?

@coreplayer2

Thank you. That's very good to know

Edit: It boots fine with CorePlus 5.0rc1, but USB keyboard and mouse don't work with any of the window managers. Booting to command line works fine. Both keyboard and mouse still work with 4.7.7 as described initially.

[gerald_clark]

Don't hijack threads.

[coreplayer2]

I suspect the issue is not related to the mouse or keyboard per se, but perhaps only the result of the underlying issue.   Try connecting via USB 2.0 ports?

One thing I should do ASAP which you have just reminded me of, is submit the Ethernet driver for the new Haswell boards in a tcz  which is missing at present.  The new Haswell chip uses an updated version of the e1000e Ethernet driver

[mirimir]

Don't hijack threads.

OK.

Should I have started a new thread? Or would it have been proper to edit the subject?

[gerald_clark]

New question - new thread.

[genec]

Interesting.  My brand-new system (Dell Latitude E6540; i7-4800QM) also seemed to hang in about the same spot.  Scrolling back, I saw there was a kernel panic that appeared to be xhci_hcd.  Adding

Code: [Select]

blacklist=xhci_hcd solved my issue.