Thanks for the feedback Brian - yes, this blank screen issue affects some users and is a royal pain in the...
Just to see if there was any difference between my earlier installs and the latest 7.4 just upgraded the last of the Atoms here from 6.9 to 7.x.
As this last machine had plenty of free un-partitioned disk space decided to make this a dual boot 6.x/7.s system...
System - Motherboard Intel D945GCLF2 with Intel Atom 330
Screen - HP 1502 LCD 4:3 1024x768 native resolution
Downloaded the latest 7.4 and created the USB drive using dd
Booted from the USB drive, selected a normal graphical install - OK. Selected do do my own custom partitioning with standard partitions - created the new partitions within the free space and started the install...
Anti-climax - install proceeded normally - finished - reboot and the Network Console displayed correctly indicating the address for a web browser to initiate the wizard to complete the installation. Completed the wizard and re-booted... all OK.
Now when the system boots can just hit any key at the appropriate time and select between 6.x or 7.x on the menu and which kernel to use...
Interesting - seems like a similar problem to what Brian is experiencing as detailed in his "Installation frustrations" thread - have you read it? Made a few suggestions there so will not repeat here - just read that thread. Have a very similar Atom board - an ASRock AD2700-ITX that had no problems installing 7.x after running 6.x for several years...
Get a 404 from that url...
Are you able to see the screen long enough to select the middle (if remember correctly) option that says something like"Test this media and Install"?
Did you run this to check the USB image integrity? OK?
Alternatively, can you move the disk and install on another machine, then move the disk back? This is usually successful provided you have standard disk controllers in each machine. Then the only thing that will need sorting are the NIC addresses..
On one machine (not an Atom) had to remove the "nomodeset" option from the " kernel /vmlinuz....." line so the display could change to graphics mode rather than going blank...
Currently 3 of my 4 Atoms are on 7.4 - the last needs to be upgraded from 6.9... wonder what is different with yours?
One last thought - had problems with the two Atom Intel motherboards until the BIOS was upgraded to the latest - though the problems were nothing to do with the display. You are at the latest level?
Thanks Nick - you will see my box is running at 100% CPU
Asked about testing as was wondering if this MultiWan issue was a known problem, and hence would not wasted any more time on it...
ClearOS used to provide details with a Beta release - and list known problems... However, a check of https://www.clearos.com/clearfoundation/development/clearos/announcements:releases:start shows the information there is woefully out-of-date - nobody at ClearOS can be bothered with updating it?
Nick a result for you - just updated a test server to ClearOS 7.5
One major problem - multiwan
This machine through 6.x and 7.x (up-to 7.4) has run successfully with two external interfaces
1) cable modem - static 2) ADSLl2+ modem dynamic
After re-booting after the upgrade the firewall immediately went into panic mode and refused any attempts to rectify...
As a test removed using webconfig the interface to the ADSL modem - no firewall panic
Re-added the ADSL interface using a static address - no firewall panic
Changed ADSL interface back to dynamic - immediate panic...
Nothing to do with kmod drivers as both these external interfaces are Intel e1000...
Have resorted to static at the moment so the machine can do a 'soak' test..
Not good - was this configuration tested? - and don't have any more time to chase this at the moment...
On the kmod front - this machine used the kmod-r8169 and kmod-via-rhine drivers on 7.4
The kmod-r8169 updated OK with the upgrade and used the kmod-via-rhine 7.5 driver from your site Nick - saved me time to compile - thanks
Both interfaces came up OK after the re-boot with the new kmod drivers...
Also a nice surprise - re-booted back to the previous 7.4 kernel - and both older kmod drivers were still on the system and the interfaces all cam up OK - so no "burnt bridges"
Note that this system, like all mine, is not 'typical' ClearOS installations
1. No flexshares or ftp
2. No dnsmasq - use bind and the dhcpd from ISC
3. Samba is not configured the "ClearOS way'
4. No paid apps
5. Several hundred rpms over and above the base ClearOS install
6. Monitoring tools are mostly 'homegrown'
7. Extensive changes made to numerous configuration files
8. Use home-frown attack-detector - the ClearOS one is too resource heavy for my systems
Will re-append with any additional information as a result of prolonged testing over the next day or two...
Fair enough, though with auto update turned off (which you want anyway for reliability) and controlling when and what updates are applied that kmod driver should not be a problem - get the updated driver, update kernel, update driver - done...
You appear to only have one NIC according to your append - how is the ClearOS system configured? Does it have a static address or one assigned from another dhcp server? eg using the MAC address to always assign the same dynamic address...
By the way - there is a kmod driver for forcedeth available for ClearOS 7.4 if that is the reason for not installing 7.4...
"service smb start" in /etc/rc.d/rc.local will try to start smb - however, never had this problem going all the way back to the ClarkConnect days...