Tiny Core Base > Release Candidate Testing
Core v4.2rc2
curaga:
@maro:
Edited to say 3.0 kernel. The Core change should wait until 4.2 is stable.
yoshi314:
--- Quote from: maro on December 19, 2011, 10:06:44 PM ---The fact that someone with 300+ posts in this forum here is not even aware of such IMHO "basic fact about Core" makes me really wonder why people are seemingly not even reading the first line of the Welcome page.
BTW that page probably needs some refresh to adjust to the fact that kernel v2.6 is now history, and possibly some more due to the change of focus from TC to Core.
--- End quote ---
i never thought that people can be judged by post count.
to me it was pretty obvious that busybox is used (as i am at least familiar with it), but mnany people do not care about internal workings of any given system, TC included. TC is fairly user friendly and can be used without extensive knowledge of its internals.
--- Quote from: mladen on December 20, 2011, 04:37:54 AM ---Booting stick on the PC connected to the dhcp network blocked without any message.
After removing "quiet" boot option, I noticed that system is waiting for relatively long time in the text mode for establishing network connection.
--- End quote ---
i am sometimes experiencing this on a system which has issues with r8169 network driver. r8168 driver is more stable for this particular hardware, but AFAIK it requires a manual build. the behavior is hard to connect to any specific software configuration.
curaga:
Hm, having waitusb=5 in the TC iso gives a bad impression. If the TC iso is not to be an isohybrid, I don't think it should have that wait there.
Reading the original request, it was about a new menu option in CorePlus having such, not in the default boot of the TC iso.
roberts:
Agreed and waitusb=5 have been removed.
roberts:
--- Quote from: mladen on December 20, 2011, 04:37:54 AM ---While testing v4.2rc1, I noticed some similarity with marcus reports. My stick created with CorePlus show next boot problems:
Booting stick on the PC connected to the dhcp network blocked without any message.
After removing "quiet" boot option, I noticed that system is waiting for relatively long time in the text mode for establishing network connection.
With Icewm boot option, system booted into X environment without waiting, but after I created mydata.tgz I had problems with rebooting flwm option.
I tried different installations and boot options and it seems to me that problems with ethernet connection establishing and problems with /tce location identification (local or network) during the booting of the core.gz part can block the process before installation of X extensions, leaving user without adequate message .
Now I am testing v4.2rc2 on the dhcp connected PC and gprs connected laptop. I tried to take care of network connectivity, and I haven`t noticed any booting problem so far.
--- End quote ---
Interesting as initial dhcp request is backgrounded. Please provide very specific details on how pendrive from CorePlus was created? dd, unetbootin, tc-install, or ? Typically on any boot time access to a usb device generally requires a waitusb=5. Do you have such in your pendrive boot parameters?
Navigation
[0] Message Index
[#] Next page
[*] Previous page
Go to full version