Problem setting up wired networking
Antonio Olivares
olivares14031 at yahoo.com
Fri Nov 14 13:16:17 UTC 2008
--- On Fri, 11/14/08, Anne Wilson <cannewilson at googlemail.com> wrote:
> From: Anne Wilson <cannewilson at googlemail.com>
> Subject: Re: Problem setting up wired networking
> To: "For testers of Fedora Core development releases" <fedora-test-list at redhat.com>
> Date: Friday, November 14, 2008, 4:10 AM
> On Friday 14 November 2008 00:21:48 Scott Robbins wrote:
> > On Thu, Nov 13, 2008 at 12:34:01PM -0600, Mike
> Chambers wrote:
> > > I would do as Jesse stated, and get the live-cd
> and use it and see if
> > > doing it from scratch works and then compare
> files/settings to get the
> > > installed working. Or to file bugs if it still
> doesn't?
> >
> I found everything exactly as on my own setup. It accepts
> my WPA key then
> requests a WEP key.
>
> > Just a note on this, both myself and one other fellow,
> on the Apsire
> > one, which is what I believe Anne is using, found that
> for some reason,
> > the LiveCD wouldn't connect properly (with NM or
> without) to a WPA2
> > network. An install and quick update fixed the
> issue--also, this was at
> > least a month ago, so if there's a newer kernel in
> the current live CD,
> > the results might be different.
> >
> Yes, this may be a kernel issue, because wireless worked
> when I installed out
> of the box, but the cabled connection didn't. It may
> be that I have to go
> back to the original kernel and manage without cabled
> altogether for the
> present. That could be one solution. I will alter the
> number of kernels kept
> (I can't remember, off-hand where that is, but I'm
> sure I'll find it).
[root at localhost ~]# cat /etc/yum.conf
[main]
cachedir=/var/cache/yum
keepcache=0
debuglevel=2
logfile=/var/log/yum.log
exactarch=1
obsoletes=1
gpgcheck=1
plugins=1
metadata_expire=1800
installonly_limit=4 <==== Here change the limit default is 3 :)
# PUT YOUR REPOS HERE OR IN separate files named file.repo
# in /etc/yum.repos.d
[root at localhost ~]#
installonly_limit=4 change this one and you are in business :)
>
> Is there any way to make an older kernel the default boot?
Change the default in /boot/grub/grub.conf to a kernel that was working :)
default=0 is the first kernel, 1 is the second and so forth. Change default=X where is the line of the kernel that you want to boot
[root at localhost ~]# cat /boot/grub/grub.conf
# grub.conf generated by anaconda
#
# Note that you do not have to rerun grub after making changes to this file
# NOTICE: You have a /boot partition. This means that
# all kernel and initrd paths are relative to /boot/, eg.
# root (hd0,1)
# kernel /vmlinuz-version ro root=/dev/VolGroup00/LogVol00 rhgb quiet
# initrd /initrd-version.img
#boot=/dev/sda
default=0
timeout=5
splashimage=(hd0,1)/grub/splash.xpm.gz
hiddenmenu
title Fedora (2.6.27.5-101.fc10.i686)
root (hd0,1)
kernel /vmlinuz-2.6.27.5-101.fc10.i686 ro root=/dev/VolGroup00/LogVol00
initrd /initrd-2.6.27.5-101.fc10.i686.img
title Fedora (2.6.26.6-79.fc9.i686)
root (hd0,1)
kernel /vmlinuz-2.6.26.6-79.fc9.i686 ro root=/dev/VolGroup00/LogVol00
initrd /initrd-2.6.26.6-79.fc9.i686.img
title Fedora (2.6.26.3-29.fc9.i686)
root (hd0,1)
kernel /vmlinuz-2.6.26.3-29.fc9.i686 ro root=/dev/VolGroup00/LogVol00
initrd /initrd-2.6.26.3-29.fc9.i686.img
title Fedora (2.6.25.14-108.fc9.i686)
root (hd0,1)
kernel /vmlinuz-2.6.25.14-108.fc9.i686 ro root=/dev/VolGroup00/LogVol00
initrd /initrd-2.6.25.14-108.fc9.i686.img
>
> Anne
> > In the very early 2.6.27 kernels, the ath5k was giving
> some people
> > (though not me) problems.
> > Ubuntu still has it blacklisted by default, I believe.
> (Judging from
> > Aspire One forums.)
> >
> >
>
> --
> fedora-test-list mailing list
> fedora-test-list at redhat.com
> To unsubscribe:
> https://www.redhat.com/mailman/listinfo/fedora-test-list
HTH,
Antonio
More information about the fedora-test-list
mailing list