This is a bit long:
installation on a laptop:
boot live system and select install to disk
The screen brightness is adjustable by only two steps and the screen is way too bright at almost maximum.
The built-in dedicated graphics card is not used but not switched off, either. The resulting power drain would make it impossible to complete the installation on battery power.
Language selection is confusing because you have to discover the Continue button, which is located out of sight far off at the right edge of the screen.
Tapping on the scratchpad doesn`t have any effect (should simulate a mouse click). Scrolling with two fingers doesn`t work, either. At least the scratchpad is working (fortunately, it does have buttons).
Keyboard selection should be a step within language selection rather than an extra step.
Network configuration doesn`t have any way to enter the IP address.
Installation Destination ... The disks show up, but how the hell do I create a software raid-1 from them?? There are no options to do anything like that. Well, I`ve selected the disks now, which is pretty weird and confusing. I want to create a raid and not select them.
Why is the Done button so inconveniently placed at the left top of the screen? Why not out of sight like the Continue button, or better, under the "Add a disk" button ...
The installer claims I have 659.36GB of free space, which is incorrect. The disks I have selected are shown as 715.40GB each (which is about right), which makes 1430.8GB and not 659.36GB.
Why is LVM a default "Partition scheme" (whatever that means)? I have no use for lvm.
Let`s say "I want more space" ... and "Standard Partition" (whatever that is) and "Encrypt my data and set a passphrase later".
Continue and I`m asked for a passphrase! That was supposed to happen LATER, not NOW ... So enter a passphrase ... Now I can either "Cancel" or "Save Passphrase". Seriously? Where is my passphrase saved? I suppose I could as well write it on a sticker and glue it to the monitor ...
Hm, ok delete all partitions. Now I could begin the installation. But how do I install on software raid-1?? Why can`t I do that and partition the disks after I deleted all partitions? Is the installation now going to proceed without partitions?
So select a destination again ... and to review/modify the partitions. Now it`s asking me a passphrase again --- wasn`t that saved? There are dots in the entry fields, so which passphrase is it using? Better enter that again ... and save it to where ever :(
Now I can apparently create mount points. Why would I create mount points before making a raid and before creating partitions?? Why can`t I just press the + key rather having to click the + button?
I don`t like this installer ...
Hm, now I can only create a mount point but no raid :( It says at the bottom that two storage devices are selected, which looks like a link. And when I click on it, it shows two disks in a window, one of them is marked as "Boot".
Why can`t change that? I don`t want to boot from that disk ... So perhaps let`s make two small partitions to be mounted as /boot, one of which is going to be a mirror of the other. Perhaps the installer then finally lets me create a raid-1 ...
Hmm ... let`s make that 512M ... There we go, finally I can say that this partition is supposed to be RAID --- which probably doesn`t work anyway, but since it`s allowed, I make it RAID-1 with ext4.
+ swap 64GB: Is that going to be on the raid or what? It says sda2, so apparently not :( Now fiddle around to get the swap on the raid ... which seems actually easy to do, same as with /boot.
+ /usr, 16GB, RAID, ext4, encrypt
Now why does the swap partition displayed after /usr rather than before it where I put it??? Anyway ...
+ /usr/local, 8GB, RAID, ext4, encrypt --- why does the cursor disappear when pressing the Tab key rather going into the "Capacity" field? Why does nothing happen when I press Return after entering "8G"?
Strange, the available disk space on the left disk is decreasing while the it stays the same on the right one. Where is it going to put the raid?
+ /var, 512GB, RAID, ext4, encrypted + /home, 8GB, RAID, ext4, encrypted
That`s ok so far, I`m done. ...
WOW! The settings I made are going to destroy devices! They don`t only destroy data and partitions, they actually destroy devices. Should I accept that?
Let`s see ... Hm, why is it asking me for the passphrase again? At least typing it so many times helps me to remember it.
But now there is an error with checking the storage configuration. Hm. Ah, hm, I don`t have defined a root partition. Modify Storage Layout ...
Ugh. Do I seriously have to start all over again?? :((((
Great, I must enter the passphrase again ... What was it saved for earlier? Or wasn`t it?
But at least I don`t need to start over with the partitioning :)
+ /, 8GB, RAID, ext4, encrypted --- that the Tab key doesn`t work is really annoying ...
Done, destroy devices, enter passphrase again --- this now annoys me, too.
There is no way to tell what passphrase is going to be used because the entry fields are full of dots, so you have to enter it all the time. Either omit the dots or don`t keep asking. If not asking, add a button to change the passphrase.
Finally I can begin the installation. This took about an hour so far.
And so far, this installer is WAYYYY better than the Fedora ones I`ve seen before. Lots of thanks goes to the developers!
But only so far. The installation finished, and I can`t boot. Only thing I`m getting is a dot at the top left of the screen and a blinking cursor underneath.
Now what? Enter the passphrase? That doesn`t have any effect. Have some devices been destroyed?
On Wednesday, May 28, 2014 08:24:09 PM lee wrote:
This is a bit long:
installation on a laptop:
boot live system and select install to disk
The screen brightness is adjustable by only two steps and the screen is way too bright at almost maximum.
The built-in dedicated graphics card is not used but not switched off, either. The resulting power drain would make it impossible to complete the installation on battery power.
Because the dual graphic card support came in later Kernels than the one shipped with Fedora 20.
Language selection is confusing because you have to discover the Continue button, which is located out of sight far off at the right edge of the screen.
...
Why is the Done button so inconveniently placed at the left top of the screen? Why not out of sight like the Continue button, or better, under the "Add a disk" button ...
...
I don`t like this installer ...
I concur. I certainly don't like the work flow of Anaconda where you have continue button on top-left corner. It breaks the intuitive linear flow that you would expect from an installer. It feels like going one step forward and two step backwards. I certainly don't prefer an ugly GTK+ installer to install Fedora KDE. But you get to hate it only once or twice a year.
On Thu, 2014-05-29 at 06:45 +0630, Sudhir Khanger wrote:
I certainly don't like the work flow of Anaconda where you have continue button on top-left corner. It breaks the intuitive linear flow that you would expect from an installer.
Nods in agreement...
I certainly don't prefer an ugly GTK+ installer to install Fedora KDE. But you get to hate it only once or twice a year.
Or several times, if you have to install to different computers. Especially if those computers are different, so you can't just make one standard install, and let it loose on the others with a prepared configuration.
Sudhir Khanger sudhir@sudhirkhanger.com writes:
On Wednesday, May 28, 2014 08:24:09 PM lee wrote:
The built-in dedicated graphics card is not used but not switched off, either. The resulting power drain would make it impossible to complete the installation on battery power.
Because the dual graphic card support came in later Kernels than the one shipped with Fedora 20.
Hm, are such cards going to be supported soon? So far, I haven`t been able to use it at all because when I switch, there is no output to the screen anymore.
Language selection is confusing because you have to discover the Continue button, which is located out of sight far off at the right edge of the screen.
...
Why is the Done button so inconveniently placed at the left top of the screen? Why not out of sight like the Continue button, or better, under the "Add a disk" button ...
...
I don`t like this installer ...
I concur. I certainly don't like the work flow of Anaconda where you have continue button on top-left corner. It breaks the intuitive linear flow that you would expect from an installer. It feels like going one step forward and two step backwards. I certainly don't prefer an ugly GTK+ installer to install Fedora KDE.
After all, I think it`s little things that might be improved over time. And the installer really has become much better already.
More importantly, the system doesn`t boot. Any ideas how to install Fedora with the setup I described so that it boots, or how to get it to boot?
On Thursday, May 29, 2014 02:19:55 PM lee wrote:
Sudhir Khanger sudhir@sudhirkhanger.com writes:
On Wednesday, May 28, 2014 08:24:09 PM lee wrote:
The built-in dedicated graphics card is not used but not switched off, either. The resulting power drain would make it impossible to complete the installation on battery power.
Because the dual graphic card support came in later Kernels than the one shipped with Fedora 20.
Hm, are such cards going to be supported soon? So far, I haven`t been able to use it at all because when I switch, there is no output to the screen anymore.
Recent Kernels do support power management to turn off dedicated graphic cards. It being able to automagically switch graphic card for GPU load is a long shot at the moment.
Nouveau doesn't even work on my system. It floods my system with messages [1] which makes it impossible to get to the desktop. I use Nvidia binary drivers through Bumblebee which works fine.
Language selection is confusing because you have to discover the Continue button, which is located out of sight far off at the right edge of the screen.
...
Why is the Done button so inconveniently placed at the left top of the screen? Why not out of sight like the Continue button, or better, under the "Add a disk" button ...
...
I don`t like this installer ...
I concur. I certainly don't like the work flow of Anaconda where you have continue button on top-left corner. It breaks the intuitive linear flow that you would expect from an installer. It feels like going one step forward and two step backwards. I certainly don't prefer an ugly GTK+ installer to install Fedora KDE.
After all, I think it`s little things that might be improved over time. And the installer really has become much better already.
More importantly, the system doesn`t boot. Any ideas how to install Fedora with the setup I described so that it boots, or how to get it to boot?
The docs tell me it is quite possible to create RAID partition using Anaconda.
http://docs.fedoraproject.org/en-US/Fedora/20/html/Installation_Guide/Create...
http://docs.fedoraproject.org/en-US/Fedora/17/html/Installation_Guide/Create...
Why is LVM a default "Partition scheme" (whatever that means)? I have no use for lvm.
Let`s say "I want more space" ... and "Standard Partition" (whatever that is) and "Encrypt my data and set a passphrase later".
Continue and I`m asked for a passphrase! That was supposed to happen LATER, not NOW ... So enter a passphrase ... Now I can either "Cancel" or "Save Passphrase". Seriously? Where is my passphrase saved? I suppose I could as well write it on a sticker and glue it to the monitor
Why do you want to use RAID-1 when you say that you have no idea what LVM or even Standard Partitions are? And same goes for employing full-disk encryption. If you don't know what to do with passphrase, you will inevitably use your data permanently and blame Fedora.
[1] https://bugzilla.redhat.com/show_bug.cgi?id=1085478
Sudhir Khanger sudhir@sudhirkhanger.com writes:
On Thursday, May 29, 2014 02:19:55 PM lee wrote:
Sudhir Khanger sudhir@sudhirkhanger.com writes:
On Wednesday, May 28, 2014 08:24:09 PM lee wrote:
The built-in dedicated graphics card is not used but not switched off, either. The resulting power drain would make it impossible to complete the installation on battery power.
Because the dual graphic card support came in later Kernels than the one shipped with Fedora 20.
Hm, are such cards going to be supported soon? So far, I haven`t been able to use it at all because when I switch, there is no output to the screen anymore.
Recent Kernels do support power management to turn off dedicated graphic cards. It being able to automagically switch graphic card for GPU load is a long shot at the moment.
If would already help if I could switch manually.
Nouveau doesn't even work on my system. It floods my system with messages [1] which makes it impossible to get to the desktop. I use Nvidia binary drivers through Bumblebee which works fine.
It`s some ATI card in this case. Perhaps the drivers would work, but there won`t be any point when nothing is displayed ...
More importantly, the system doesn`t boot. Any ideas how to install Fedora with the setup I described so that it boots, or how to get it to boot?
The docs tell me it is quite possible to create RAID partition using Anaconda.
http://docs.fedoraproject.org/en-US/Fedora/20/html/Installation_Guide/Create...
http://docs.fedoraproject.org/en-US/Fedora/17/html/Installation_Guide/Create...
It was possible to create them --- or least to tell the installer to do so. Since it doesn`t boot, I don`t know what was actually done.
Why is LVM a default "Partition scheme" (whatever that means)? I have no use for lvm.
Let`s say "I want more space" ... and "Standard Partition" (whatever that is) and "Encrypt my data and set a passphrase later".
Why do you want to use RAID-1 when you say that you have no idea what LVM or even Standard Partitions are?
I`m not saying that I have no idea what LVM is, only that I don`t have use for it. And the installer doesn`t say what it means by "standard partitions". I want to use raid because I don`t store data on a single disk only.
And same goes for employing full-disk encryption. If you don't know what to do with passphrase, you will inevitably use your data permanently and blame Fedora.
I`m not saying that I don`t know what to do with it. Why do I have to enter the passphrase like 10 times? Why does the installer want to save it, and where?
Anyway, I want to use the system. Since Fedora fails and there aren`t any ideas about getting it to work, it seems I have to install something else.
On 05/30/2014 04:29 AM, lee wrote:
Sudhir Khanger sudhir@sudhirkhanger.com writes:
On Thursday, May 29, 2014 02:19:55 PM lee wrote:
Sudhir Khanger sudhir@sudhirkhanger.com writes:
On Wednesday, May 28, 2014 08:24:09 PM lee wrote:
The built-in dedicated graphics card is not used but not switched off, either. The resulting power drain would make it impossible to complete the installation on battery power.
Because the dual graphic card support came in later Kernels than the one shipped with Fedora 20.
Hm, are such cards going to be supported soon? So far, I haven`t been able to use it at all because when I switch, there is no output to the screen anymore.
Recent Kernels do support power management to turn off dedicated graphic cards. It being able to automagically switch graphic card for GPU load is a long shot at the moment.
If would already help if I could switch manually.
Nouveau doesn't even work on my system. It floods my system with messages [1] which makes it impossible to get to the desktop. I use Nvidia binary drivers through Bumblebee which works fine.
It`s some ATI card in this case. Perhaps the drivers would work, but there won`t be any point when nothing is displayed ...
More importantly, the system doesn`t boot. Any ideas how to install Fedora with the setup I described so that it boots, or how to get it to boot?
The docs tell me it is quite possible to create RAID partition using Anaconda.
http://docs.fedoraproject.org/en-US/Fedora/20/html/Installation_Guide/Create...
http://docs.fedoraproject.org/en-US/Fedora/17/html/Installation_Guide/Create...
It was possible to create them --- or least to tell the installer to do so. Since it doesn`t boot, I don`t know what was actually done.
Why is LVM a default "Partition scheme" (whatever that means)? I have no use for lvm. Let`s say "I want more space" ... and "Standard Partition" (whatever that is) and "Encrypt my data and set a passphrase later".
Why do you want to use RAID-1 when you say that you have no idea what LVM or even Standard Partitions are?
I`m not saying that I have no idea what LVM is, only that I don`t have use for it. And the installer doesn`t say what it means by "standard partitions". I want to use raid because I don`t store data on a single disk only.
And same goes for employing full-disk encryption. If you don't know what to do with passphrase, you will inevitably use your data permanently and blame Fedora.
I`m not saying that I don`t know what to do with it. Why do I have to enter the passphrase like 10 times? Why does the installer want to save it, and where?
Anyway, I want to use the system. Since Fedora fails and there aren`t any ideas about getting it to work, it seems I have to install something else.
Hi Lee, Just my 2 cents worth, the dot you are seeing on the top left of the screen is displayed just before the grub boot menu is displayed, which as the menu is not displayed means that the system can't find grub.cfg which is in /boot/grub2. I haven't tried playing around with software raid much, which also leads to the question of why raid1 which is mirroring rather than raid0 which is striping and provides more disk space availability, but I digress. I thought that support for software raid was implemented in kernel modules, which if correct, the kernel is in /boot, which I thought you said was a raid device, hence how does it load the drivers to support raid from a raid device before it has the drivers, if you know what I mean, which would also explain why it can't load grub.cfg. I know its a pain, but I would try reinstalling again and configuring your devices with /boot as non-raid, and configuring everything else as raid.
regards, Steve
On May 29, 2014, at 6:19 AM, lee lee@yun.yagibdah.de wrote:
More importantly, the system doesn`t boot. Any ideas how to install Fedora with the setup I described so that it boots, or how to get it to boot?
There are more than 10,000 reasons why a system won't boot. So you're going to have to tell us what does happen rather than what doesn't happen.
Chris Murphy
On May 29, 2014, at 12:29 PM, lee lee@yun.yagibdah.de wrote:
I`m not saying that I have no idea what LVM is, only that I don`t have use for it.
I still think it shouldn't be default for workstation or cloud, only for server. It's got very cool features, but it causes way more problems and complications than it solves, therefore I think it's better if people who want it have to choose to use it, rather than people who don't know what it is or won't benefit from it having to know to disable something they don't know to disable. The explanation is that "eventually we're going to move to Btrfs by default so why make a change from LVM to plain partitions and then to btrfs; why not just do the change once when we're ready?" And that logic won the argument. I still think it's better to do the simplest thing at the moment, even if it means back to back changes.
But whatever, if you know what it is, and you know that you don't need it, you don't really have much reason to just advertise that you don't need it. It's not really going to do much good in this forum (just like the above paragraph of mine), there are other forums for that.
And the installer doesn`t say what it means by "standard partitions".
It means "don't use LVM" it just uses plain partitions for each chosen mount point in the installer.
I want to use raid because I don`t store data on a single disk only.
RAID1/Mirroring in the Fedora installer translates to md raid. It will support existing IMSM (Intel firmware initiated RAID), also via md. The md driver is part of the kernel, and the user space tool is mdadm.
And same goes for employing full-disk encryption. If you don't know what to do with passphrase, you will inevitably use your data permanently and blame Fedora.
I`m not saying that I don`t know what to do with it. Why do I have to enter the passphrase like 10 times? Why does the installer want to save it, and where?
If it asks for a passphrase on more than one page (two times on the same page, the 2nd one is a confirmation) then you've probably run into a bug or confusing design. With Fedora 19 for example it was possible to inadvertently create encrypted partitions, which became LVM PVs, and then you could also separately encrypt each LV. So you were getting double encryption. This logic was fixed in Fedora 20 but you might still be running into some confusing UI, but it shouldn't let you actually create a layout with double encryption.
In any case, almost no one is going to understand what you're talking about unless you either write out discrete steps, maybe annotated with screen shots. Or better (and easier) if you can make a video of it.
Anyway, I want to use the system. Since Fedora fails and there aren`t any ideas about getting it to work, it seems I have to install something else.
I'm willing to bet dollars to donuts no one even understands exactly how it's failing. That is it failing isn't specific enough, like I said earlier there are thousands of ways an OS can fail to boot or startup. A good starting point for troubleshooting is to edit the boot menu entry in grub (use e to edit) and find the linux line, and remove rhgb quiet. That's a one time thing, the next time you boot those options will be back in there so if you need to keep troubleshooting you have to remove them each time. Another idea if this might be video card related is to try adding the option nomodeset. And then take a photo with a cell phone where the text scrolling stops and put it up somewhere.
Even better if you can ssh into the computer remotely and post the result from:
journalctl -b -l -o short-monotonic > journal.txt scp journal.txt <remotehost>
It's probably too big for fpaste but you could try it: fpaste journal.txt
Chris Murphy
Stephen Morris samorris@netspace.net.au writes:
Hi Lee, Just my 2 cents worth, the dot you are seeing on the top left of the screen is displayed just before the grub boot menu is displayed, which as the menu is not displayed means that the system can't find grub.cfg which is in /boot/grub2. I haven't tried playing around with software raid much, which also leads to the question of why raid1 which is mirroring rather than raid0 which is striping and provides more disk space availability, but I digress.
http://en.wikipedia.org/wiki/RAID
I thought that support for software raid was implemented in kernel modules, which if correct, the kernel is in /boot, which I thought you said was a raid device, hence how does it load the drivers to support raid from a raid device before it has the drivers, if you know what I mean, which would also explain why it can't load grub.cfg.
Yes, I`ve been thinking that. Yet:
1: When the system cannot boot when /boot is on a software raid, the installer should give you a warning and an explanation.
2: I have had a Debian installation running with /boot on software raid-1 just fine for years.
As to 2: If the installer created the /boot partition correctly and unless the md tools changed significantly in the way they deal with raid-1 partitions, grub is able to read from that partition even though it might just read from only one of the drives.
Thirdly, what are the mdraid* modules in /boot/grub2/i386-pc/ for? "Grub 2 supports Linux mdraid volumes natively."[1] So either there is a problem in the installer, or grub2 doesn`t support mdraid.
[1]: http://unix.stackexchange.com/questions/17481/grub2-raid-boot
I know its a pain, but I would try reinstalling again and configuring your devices with /boot as non-raid, and configuring everything else as raid.
Well, either someone knows a solution, or I try to fix the problem with a rescue/life system, or I install something else. I might give centos a try because I think I might actually get a server sooner or later (which is likely to be some proliant --- which would put some sense to using centos --- despite HP can`t even deliver a replacement battery for a UPS ... ). I`d have tried mint, but my USB stick holds only 1GB and their installer is 1.2GB. Or perhaps I`ll try gentoo ...
The only reason I tried Fedora is because it`s still on my computer and the installer fits on my USB stick. Since, in the context of Fedora.next, it has been established in this mailing list that developers of Fedora don`t care at all what users of Fedora think and the Fedora project nonetheless feels that they shall be positioned to lead the advancement of OSS, without caring, using Fedora is a pretty moot point for me: That they happen to make a good distribution is obviously a random side effect which can go away any time.
So I`m merely giving some feedback here. This is one way to contribute (which will probably be ignored anyway). A while ago someone here seemed to be interested in why ppl who are using Linux are not using Fedora ...
Chris Murphy lists@colorremedies.com writes:
On May 29, 2014, at 12:29 PM, lee lee@yun.yagibdah.de wrote:
I`m not saying that I have no idea what LVM is, only that I don`t have use for it.
But whatever, if you know what it is, and you know that you don't need it, you don't really have much reason to just advertise that you don't need it. It's not really going to do much good in this forum (just like the above paragraph of mine), there are other forums for that.
I`m merely giving some feedback. I know, ppl wanted bug reports --- and I can still compile all the mails in this thread and put them into a bug report. That bug reports aren`t suited in this case has been persistently ignored.
And the installer doesn`t say what it means by "standard partitions".
It means "don't use LVM" it just uses plain partitions for each chosen mount point in the installer.
That is left to be guessed by the user.
I want to use raid because I don`t store data on a single disk only.
RAID1/Mirroring in the Fedora installer translates to md raid. It will support existing IMSM (Intel firmware initiated RAID), also via md. The md driver is part of the kernel, and the user space tool is mdadm.
Are you saying the installer would secretly use some Intel fake-raid onboard-controller if it`s available? That is pretty much the last thing I would want to use.
And same goes for employing full-disk encryption. If you don't know what to do with passphrase, you will inevitably use your data permanently and blame Fedora.
I`m not saying that I don`t know what to do with it. Why do I have to enter the passphrase like 10 times? Why does the installer want to save it, and where?
If it asks for a passphrase on more than one page (two times on the same page, the 2nd one is a confirmation) then you've probably run into a bug or confusing design.
It`s been asking for a passphrase together with confirmation many times. The entry fields were full of dots after the first time, so there is no way to tell what passphrase it might use. So obviously, you have to enter the passphrase every time you`re being asked.
It doesn`t even give you choice to not save the passphrase.
With Fedora 19 for example it was possible to inadvertently create encrypted partitions, which became LVM PVs, and then you could also separately encrypt each LV. So you were getting double encryption. This logic was fixed in Fedora 20 but you might still be running into some confusing UI, but it shouldn't let you actually create a layout with double encryption.
Since the system doesn`t boot, I haven`t checked for this ...
In any case, almost no one is going to understand what you're talking about unless you either write out discrete steps, maybe annotated with screen shots. Or better (and easier) if you can make a video of it.
Where would I store screenshots or a video when I can`t even enter an IP address to configure the network, which might give me a chance to store files somewhere? Recording a video that goes for an hour or two doesn`t exactly create only a small file. And does the installer come with some screen recording software?
So I wrote down the steps I took.
Anyway, I want to use the system. Since Fedora fails and there aren`t any ideas about getting it to work, it seems I have to install something else.
I'm willing to bet dollars to donuts no one even understands exactly how it's failing. That is it failing isn't specific enough, like I said earlier there are thousands of ways an OS can fail to boot or startup.
You can try it for yourself, doing the same steps I did. And I haven`t touched it yet, so if you can tell me exactly what information you need, I might be able to boot a live/rescue system and obtain it.
A good starting point for troubleshooting is to edit the boot menu entry in grub (use e to edit) and find the linux line, and remove rhgb quiet.
There is no boot menu. I`d have to boot a live/rescue system to do that.
That's a one time thing, the next time you boot those options will be back in there so if you need to keep troubleshooting you have to remove them each time.
Where`s this line coming from? "rhgb" isn`t anywhere the grub.cfg on my computer.
Another idea if this might be video card related is to try adding the option nomodeset. And then take a photo with a cell phone where the text scrolling stops and put it up somewhere.
There is no text scrolling, and it`s a pita to get any data off or onto my cell phone, if possible at all. And does anyone really need a picture to understand that, when trying to boot, there`s a dot in the top left corner of the screen and a blinking cursor below that, as I explained?
Besides, I`ve had Debian and Fedora on the same laptop before, and nomodeset wasn`t required.
Even better if you can ssh into the computer remotely and post the result from:
How do you ssh into a computer that doesn`t boot? Is sshd installed and enabled, using the ssh port, by the default installation, and not blocked by firewalling? If so, I`d consider that a security risk, and such a default needs to be changed.
Chris Murphy lists@colorremedies.com writes:
On May 29, 2014, at 6:19 AM, lee lee@yun.yagibdah.de wrote:
More importantly, the system doesn`t boot. Any ideas how to install Fedora with the setup I described so that it boots, or how to get it to boot?
There are more than 10,000 reasons why a system won't boot. So you're going to have to tell us what does happen rather than what doesn't happen.
In the lengthy installation report, I told you exactly what I did and what happened.
Hm, perhaps I could configure the network card from the console, if there is one, and get so far as to be able make a video of the installation --- provided that network manager doesn`t mess up such a configuration. But who`s going to watch that? And it won`t show how the system doesn`t boot ...