Tiny Core Base > Release Candidate Testing
Core v4.2rc2
coreplayer2:
besides, the few can always add the waitusb=5 as needed
gerald_clark:
You should not have to do anything special to boot the CD just because it is connected by USB.
That would cause a storm of forum posts because it doesn't boot properly.
mladen:
--- Quote from: roberts on December 20, 2011, 08:54:04 AM ---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?
--- End quote ---
After I read yoshi314`s post:
--- Quote from: yoshi314 on December 20, 2011, 07:25:24 AM ---
--- 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.
--- End quote ---
I analyzed dmesg from my PC installation and noticed just what yoshi314 said - problem with r8169 driver which temporarily blocked on
eth0: link down
etho: link up
kernel boot phase.
So I can very gladly say that problem I had is not concerned with 2rc1 release !
With best regards
coreplayer2:
--- Quote from: roberts on December 19, 2011, 11:45:06 AM --- I suspect that hdparm -z is not being supported by your vm. hdparm -z is required to re-read an in session change to a drive partition table.
--- End quote ---
As you suspected hdparm -z is unable to reinitialize reading of partition table structures.
coreplayer2:
--- Quote from: yoshi314 on December 20, 2011, 07:25:24 AM ---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.
--- End quote ---
I too know what busy box is, just had a senior moment is all.. lol
--- Quote from: mladen on December 20, 2011, 04:37:54 AM ---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.
--- End quote ---
I have compiled the r8168 Ethernet driver for tc4.1 some weeks back and forgot to submit it. meanwhile it's been thoroughly tested so I'll get it submitted today.
hope it helps someone
Navigation
[0] Message Index
[*] Previous page
Go to full version