Felix Miata wrote:
> Neither X server nor Intel driver are static. They keep
evolving, and bugs
> creep in. With fewer and fewer i686 alpha and beta testers
reporting
> problems, and fewer developers to both care about and able
to fix them,
> getting bugs found and fixed takes longer, and long
Felix Miata wrote:
> Nomodeset has three primary purposes:
>
> 1-workaround for Anaconda, which can't always work with all
hardware. It
> causes fallback to a low-performance generic Xorg video
driver, good only
> to make X work at all when something is broken.
The fallback works, sort of. Goo
Adam Williamson wrote:
> That's a kernel crash. If you boot with 'nomodeset' added
back you
> should be able to report a bug for it. I can't remember if
we have abrt
> collection of kernel traces set up ATM; if not, you can
just file a bug
> at https://bugs.freedesktop.org (against xorg
Driver
If you have anything to add, I have made a bug report:
https://bugzilla.redhat.com/show_bug.cgi?id=1338076
--
test mailing list
test@lists.fedoraproject.org
To unsubscribe:
http://lists.fedoraproject.org/admin/lists/test@lists.fedoraproject.org
There's definitely a bug here!
First try, I removed nomodeset and I got the expected fedora
infinity and everything went well, just like in f23 and just
like in the regular anaconda installer on the live CD,
except...
GDM never starts! The computer just hangs. I cannot use ESC
to switch to th
That's lots of information and none of it conflicting. Thanks,
guys! I'll give it a try. It sounds very encouraging. This old
box isn't done yet ;-)
Yep, I realize that i686 is no longer supported, but I just
can't rationalize spending hundreds on a new laptop (or other
portable), considering
In F23, all went fine, but in F24, some video problems are
showing up.
After the grub menu, the machine is supposed to switch to the
framebuffer and the boot image (fedora infinity goes from
white to filled in) appears and one can switch to the boot
message display with ESC.
Well, not in F24
Sérgio Basto wrote:
> yeah ß is not an β
> alt gr + s writes ß ( but this is not an beta )
I never knew that there was a real beta character! es-zett is
easy to type: just right-alt-s. How do you type the Greek beta
from the keyboard (I use US dead keys—always and exclusively)?
--
test mailing
Just a test to see if I configured Knode correctly, but might
as well make it worthwhile ;-)
I'm very pleased with the release so far and have run into no
problems (exception: TPM on laptop, but that's something for
bugzilla).
--
test mailing list
test@lists.fedoraproject.org
To unsubscribe:
ht
for the Knode setup in fedora 21ß
--
test mailing list
test@lists.fedoraproject.org
To unsubscribe:
https://admin.fedoraproject.org/mailman/listinfo/test
Ed Greshko wrote:
> Sorry to start yet another thread on the same
issue
I downloaded the KDE live image and then, even though I
never use it, ran:
sudo yum groupinstall "GNOME"
Next, this got me a few more programs:
sudo yum groupinstall "Fedora Workstation"
I aborted the following, bec
Tom H wrote:
> info -f grub2 -n 'Simple configuration'
Thanks. I found that later on. I put info:/grub2 into konqueror and the simple
configuration link leapt out at me.
--
test mailing list
test@lists.fedoraproject.org
To unsubscribe:
https://admin.fedoraproject.org/mailman/listinfo/test
Adam Williamson wrote:
> 'systemctl status sshd.service' will tell you about the service: it
> should say 'active (running)'. 'failed' or 'active (exited)' would be
> bad.
This is the command I have been relying on.
>> 1. systemd will automatically recognize that I need sshd.service to be
>> sta
In the system-config-services, I see that sshd is not running when I boot the
computer.
The message at the top right says that:
"The sshd service is managed by systemd. It may be started then run in the
background, or be activated on demand..."
I am unclear about the "be activated on demand" p
Tom H wrote:
> I wasn't implying that you had.
I never got the impression that you were implying that I had changed the file
:-)
I thought you were stating that I _must_ change the file to get the result I
wanted :-)
> I was only pointing out that some people - like me - do so
I looked at th
Tom H wrote:
> On Sun, Aug 28, 2011 at 1:46 AM, Peter G. wrote:
>> - no rescue mode menu entry for the kernel-PAE was created
>
> Because grubby only creates one entry when a new kernel's installed;
> "grub2-mkconfig ..." creates a "regular" entry an
I installed (rpm -ivh) kernel-PAE on a Fedora 16α system.
I changed /etc/sysconfig/kernel: DEFAULTKERNEL=kernel-PAE
The new kernel-PAE shows up in grub.cfg, but some things are not quite how they
should be:
- the menu entry for kernel-PAE is not of the same format as the other lines
- the echo l
Michael Spahn wrote:
> In my opionion it's still a bug, the should be a notice what "Apply" mean.
I agree. I meant that I don't need any more hints or tips, because I have
solved
the problem and I now have ssh working. Clearly, as I was trying to get this
solved, we stumbled across a bug in th
Michael Cronenworth wrote:
> # ip(6)tables -A INPUT -m state --state NEW -m tcp -p tcp --dport 22 -j
> # ACCEPT
> run "systemctl restart iptables.service" and
> "systemctl restart ip6tables.service"
This works.
--
test mailing list
test@lists.fedoraproject.org
To unsubscribe:
https://admin.fe
Marty Felkler wrote:
> you can use the command
> "grub2-mkconfig -o /boot/grub/grub.cfg" to create grub.cfg
grub2-mkconfig -o /boot/grub2/grub.cfg
> you have to hand edit to grub.cfg to make the other entries.
create other entries in /boot/grub2/custom.cfg
don't hand edit grub.cfg at all
--
te
Michael Spahn wrote:
> Bug is opened, feel free to add a comment.
>
> https://bugzilla.redhat.com/show_bug.cgi?id=733778
>
> Regards
>
> Michael
Thanks. I was going to do that after I get back from a jog :-)
--
test mailing list
test@lists.fedoraproject.org
To unsubscribe:
https://admin.fed
Michael Cronenworth wrote:
> Peter G. wrote:
>> iptables -L does now show an ssh entry. Does this also do ipv6 (or would
>> I ever need to deal with this in an ipv6 situation, down the road?)?
>
> No. You will want ip6tables for that.
Odd. I just checked /etc/sysconfig/i
Michael Cronenworth wrote:
> The apply button in system-config-firewall should apply the firewall
> settings. He shouldn't need to reboot or reload the iptables rules.
That's what I thought. That's why it says apply. Apply means to put into being,
now.
--
test mailing list
test@lists.fedorapro
Clyde E. Kunkel wrote:
> I assume you have rebooted after changing firewall rules
no. I didn't. Linux folklore states that rebooing is not necessary
> and/or issued:
>
> # systemctl restart iptables.service
I didn know I had to.
> If so, then I dunno
but I do... now.
--
test maili
Michael Cronenworth wrote:
> # iptables -A INPUT -m state --state NEW -m tcp -p tcp --dport 22 -j
> # ACCEPT
>
> As Michael said, system-config-firewall has a bug. You two should file a
> bug against it.
Thanks for all the help. I hope this will now work. I will try it in a couple
of
hours...
Michael Spahn wrote:
> I learned that the firewall system-config tool doesn't work.
>
> I actually don't know why but I always had to disable the whole firewall.
I never had to disable the firewall in f13 or f14 or f15 for ssh (only for nfs,
which I no longer use, because of that and other reas
Michael Cronenworth wrote:
> # iptables -L | grep ssh
> ACCEPT tcp -- anywhere anywherestate NEW
> tcp dpt:ssh
You know, I just tried your command again, but this time without grepping, and
I see that ssh is nowhere in the output, so how could grep ssh ever return
Michael Cronenworth wrote:
> netstat lists network port information. It does not know about or list
> firewall configuration information.
>
> iptables is the command-line tool to view, add, delete, or change
> firewall rules.
>
> # iptables -L# lists default table rules
>
> # iptables -L |
Michael Cronenworth wrote:
> Is the firewall on both machines configure to allow port 22 through?
I think so. I unclicked and reclicked ssh in the firewall configuration, then
apply.
Then I restarted sshd.service on both computers and on both computers netstat
showed:
tcp0 0 0.0.
I have fedora 16α installed on both computers.
The two computers are connected to one another via a router.
They can ping one another.
sshd is running on both computers.
# netstat -tulpn | grep :22
tcp0 0 0.0.0.0:22 0.0.0.0:*
LISTEN 11865/sshd
Tom H wrote:
> The default Fedora install, up to now, has been to have a separate
> "/boot" in order to use LVM for "/". That's one reason and there are
> others (for example, some people don't mount "/boot" at boot; they
> only mount it to update the kernel and the boot config and then
> unmount
Peter G. wrote:
> Adam Williamson wrote:
>
>> did you run 'update_grub'?
>
> no I didn't. first I heard of it. that might
> explain it. but I learned something and I think
I
> prefer the custom.cfg method, anyway :-)
>
I don't seem to have t
Adam Williamson wrote:
> did you run 'update_grub'?
no I didn't. first I heard of it. that might
explain it. but I learned something and I think I
prefer the custom.cfg method, anyway :-)
--
test mailing list
test@lists.fedoraproject.org
To unsubscribe:
https://admin.fedoraproject.org/mailma
33 matches
Mail list logo
