Alan Feuerbacher wrote:
> On 11/25/2013 8:40 PM, Bruce Dubbs wrote:
>> Alan Feuerbacher wrote:
>>> On 11/25/2013 11:50 AM, Bruce Dubbs wrote:
Dan McGhee wrote:
>>>
>> r8169 71677 0
>> mii13527 1 r8169
Looking at the help in the kernel fo
On 11/25/2013 8:40 PM, Bruce Dubbs wrote:
> Alan Feuerbacher wrote:
>> On 11/25/2013 11:50 AM, Bruce Dubbs wrote:
>>> Dan McGhee wrote:
>>
> r8169 71677 0
> mii13527 1 r8169
>>>
>>> Looking at the help in the kernel for CONFIG_R8169:
>>>
>>> Selects: F
> From: Simon Geard
> To: lfs-support@linuxfromscratch.org
> Date: Fri, 29 Nov 2013 21:23:05 +1300
> Subject: Re: [lfs-support] Ethernet Card Not Found
>
> On Thu, 2013-11-28 at 10:28 +, akhiezer wrote:
> > You're expending resources to try to persuade people th
On Thu, 2013-11-28 at 10:28 +, akhiezer wrote:
> You're expending resources to try to persuade people that there's no issue
> here.
I'm not trying to persuade anyone anything... I'm trying to understand
why this is considered such an important thing, why it comes up again
and again as a sourc
> From lfs-support-boun...@linuxfromscratch.org Wed Nov 27 11:07:47 2013
> From: Simon Geard
> To: lfs-support@linuxfromscratch.org
> Date: Wed, 27 Nov 2013 23:46:50 +1300
> Subject: Re: [lfs-support] Ethernet Card Not Found
>
> On Tue, 2013-11-26 at 13:27 -0600, Bruce
Le 28/11/2013 10:48, akhiezer a écrit :
> I think the _prime_ example actually would be Slackware, in this and
> many other instances.
Any prime example on an LFS mail list is LFS ;-)
Sorry, couldn't refrain...
Pierre
--
http://linuxfromscratch.org/mailman/listinfo/lfs-support
FAQ: http://www.
> From lfs-support-boun...@linuxfromscratch.org Wed Nov 27 23:33:32 2013
> Date: Wed, 27 Nov 2013 17:13:29 -0600
> From: Bruce Dubbs
> To: LFS Support List
> Subject: Re: [lfs-support] Ethernet Card Not Found
>
> Gordon Findlay wrote:
> >>
> >>
> >
Gordon Findlay wrote:
>>
>>
>>
>> That's kind of what confuses me about this whole issue... the degree to
>> which discussions here and elsewhere get so heated and angry. It's
>> obviously supremely important to some people - but I don't understand
>> why, when to me it seems such a small thing.
>
>
>
>
> That's kind of what confuses me about this whole issue... the degree to
> which discussions here and elsewhere get so heated and angry. It's
> obviously supremely important to some people - but I don't understand
> why, when to me it seems such a small thing.
>
> Simon.
>
> I teach Linux, a
On 11/26/2013 09:23 PM, William Harrington wrote:
> On Nov 26, 2013, at 6:19 PM, Baho Utot wrote:
>
>> Want to bet which one of these I can remember?
> p33p1 for people!
Nope too many characters
--
http://linuxfromscratch.org/mailman/listinfo/lfs-support
FAQ: http://www.linuxfromscratch.org/lfs/
On Tue, 2013-11-26 at 13:27 -0600, Bruce Dubbs wrote:
> The wording in this message comes across a little too strong. Yes, we
> sometimes get a little emotional about the foolishness that we see, but
> lets try to be a little more civil when discussing technical matters.
>
That's kind of what
On Tue, 2013-11-26 at 19:24 +, akhiezer wrote:
> that particular machine; or what? It's an intriguing concept - *never*
> needing
> to know the name of network device(s) on one's Linux computer, and for
> someone
> like yourself who would appear to be an (>=)advanced user.
Like I said... "
On Nov 26, 2013, at 6:19 PM, Baho Utot wrote:
> Want to bet which one of these I can remember?
p33p1 for people!
--
http://linuxfromscratch.org/mailman/listinfo/lfs-support
FAQ: http://www.linuxfromscratch.org/lfs/faq.html
Unsubscribe: See the above information page
On 11/26/2013 03:09 AM, Simon Geard wrote:
> On Mon, 2013-11-25 at 20:12 -0500, Alan Feuerbacher wrote:
>> On 11/25/2013 11:04 AM, William Harrington wrote:
>>> Your link name is p4p1.
>> How does this name, given by Fedora, relate to the "enp3s0" that my
>> kernel assigned (see my earlier reply t
> Date: Tue, 26 Nov 2013 13:27:26 -0600
> From: Bruce Dubbs
> To: LFS Support List
> Subject: Re: [lfs-support] Ethernet Card Not Found
>
.
.
> The wording in this message comes across a little too strong. Yes, we
> sometimes get a little emotional about th
akhiezer wrote:
>> From: Simon Geard
>> To: lfs-support@linuxfromscratch.org
>> Date: Tue, 26 Nov 2013 21:05:53 +1300
>> Subject: Re: [lfs-support] Ethernet Card Not Found
>>
> .
> .
>> But really, what's wrong with it? All the
> From: Simon Geard
> To: lfs-support@linuxfromscratch.org
> Date: Tue, 26 Nov 2013 21:05:53 +1300
> Subject: Re: [lfs-support] Ethernet Card Not Found
>
.
.
> But really, what's wrong with it? All the melodrama, talking about
> "abominations
On 11/26/2013 10:34 AM, Bruce Dubbs wrote:
> Simon Geard wrote:
>> On Mon, 2013-11-25 at 20:18 -0600, Bruce Dubbs wrote:
>>> I know the answer to that one. To ensure that really big iron with many
>>> ethernet devices will not have ethx assigned in random order due to race
>>> conditions. It prob
Simon Geard wrote:
> On Mon, 2013-11-25 at 20:18 -0600, Bruce Dubbs wrote:
>> I know the answer to that one. To ensure that really big iron with many
>> ethernet devices will not have ethx assigned in random order due to race
>> conditions. It probably comes up more frequently when using systemd
Em 25-11-2013 21:44, Alan Feuerbacher escreveu:
> How does someone setting up an LFS system find out the "IP" address? I
> had to look at what Fedora had done to figure this out.
Depends on the router. It can have the address set to 10.0.1.1 as yours,
and somewhere in its configuration there is
On Mon, 2013-11-25 at 20:12 -0500, Alan Feuerbacher wrote:
> On 11/25/2013 11:04 AM, William Harrington wrote:
> > Your link name is p4p1.
>
> How does this name, given by Fedora, relate to the "enp3s0" that my
> kernel assigned (see my earlier reply to Fernando).
Looks like Fedora uses a differ
On Mon, 2013-11-25 at 20:18 -0600, Bruce Dubbs wrote:
> I know the answer to that one. To ensure that really big iron with many
> ethernet devices will not have ethx assigned in random order due to race
> conditions. It probably comes up more frequently when using systemd
> which launches proc
Em 25-11-2013 23:00, Bruce Dubbs escreveu:
> Fernando de Oliveira wrote:
>> I am telling it because I thing it is better something "Open" than
>> google. But i am not sure at all about it, is it really "Open"? Please,
>> what is your opinion?
>
> I don't know if one is better than the other. I'm
Ken Moffat wrote:
> On Mon, Nov 25, 2013 at 07:44:16PM -0500, Alan Feuerbacher wrote:
>>
>> Apparently things in the linux world have changed recently with respect
>> to naming devices generally, so that old conventions like "eth0" have
>> been replaced by conventions that are said to make more sen
Em 25-11-2013 22:37, Bruce Dubbs escreveu:
> Alan Feuerbacher wrote:
> $ cat /etc/resolv.conf
> domain linuxfromscratch.org
> nameserver 8.8.4.4
> nameserver 8.8.8.8
Bruce, I use OpenDNS:
208.67.222.222
208.67.220.220
I am telling it because I think it is better something "Open" than
google. Bu
On Mon, Nov 25, 2013 at 07:44:16PM -0500, Alan Feuerbacher wrote:
>
> Apparently things in the linux world have changed recently with respect
> to naming devices generally, so that old conventions like "eth0" have
> been replaced by conventions that are said to make more sense. I suppose
> "enp
Fernando de Oliveira wrote:
> Em 25-11-2013 22:37, Bruce Dubbs escreveu:
>> Alan Feuerbacher wrote:
>
>> $ cat /etc/resolv.conf
>> domain linuxfromscratch.org
>> nameserver 8.8.4.4
>> nameserver 8.8.8.8
>
> Bruce, I use OpenDNS:
>
> 208.67.222.222
> 208.67.220.220
>
> I am telling it because I thin
Em 25-11-2013 22:37, Bruce Dubbs escreveu:
> Alan Feuerbacher wrote:
> $ cat /etc/resolv.conf
> domain linuxfromscratch.org
> nameserver 8.8.4.4
> nameserver 8.8.8.8
Bruce, I use OpenDNS:
208.67.222.222
208.67.220.220
I am telling it because I thing it is better something "Open" than
google. Bu
On 11/25/2013 07:19 PM, Alan Feuerbacher wrote:
> On 11/25/2013 11:27 AM, Dan McGhee wrote:
>> lsmod
>> ##
>> Module SizeUsed by
>> x86_pkg_temp_thermal45110
>> ##
>> This shows that either the module is not loaded or that it's configured
>>
Alan Feuerbacher wrote:
> On 11/25/2013 11:27 AM, Dan McGhee wrote:
>>
>> Alan, you have gotten a number of great suggestions from some really
>> helpful people. I think, however, that the waters are very muddy right
>> now. The main problem is that your system can't find your ethernet
>> card--e
Em 25-11-2013 21:44, Alan Feuerbacher escreveu:
> On 11/25/2013 10:15 AM, Fernando de Oliveira wrote:
>> Em 25-11-2013 11:59, Alan Feuerbacher escreveu:
>
>>> 2: p4p1: mtu 1500 qdisc pfifo_fast
>>> state UP mode DEFAULT group default qlen 1000
>>> link/ether 30:85:a9:8f:31:09 brd ff:ff:ff:f
Alan Feuerbacher wrote:
> On 11/25/2013 11:50 AM, Bruce Dubbs wrote:
>> Dan McGhee wrote:
>
r8169 71677 0
mii13527 1 r8169
>>
>> Looking at the help in the kernel for CONFIG_R8169:
>>
>> Selects: FW_LOADER [=y] && CRC32 [=y] && MII [=y]
>
> How does
Alan Feuerbacher wrote:
> The file that worked:
>
> ifconfig.enp3s0
> ###
> ONBOOT=yes
> IFACE=enp3s0
> SERVICE=ipv4-static
> IP=10.0.1.31
> GATEWAY=10.0.1.1
> PREFIX=24
> BROADCAST=192.168.0.255
The BROADCAST is still wrong. It needs top be 10.0.1.255. You are not
a part of the 192.168.0
On 11/25/2013 07:44 PM, Alan Feuerbacher wrote:
[putolin]
> ONBOOT=yes
> IFACE=p4p1
> SERVICE=ipv4-static
> IP=10.0.1.31
> GATEWAY=10.0.1.1
> PREFIX=24
> BROADCAST=192.168.0.255
>
> the problem, perhaps, would be solved.
> That helped, thank you. What finally solved the problem, though, was
> Wi
On 11/25/2013 11:50 AM, Bruce Dubbs wrote:
> Dan McGhee wrote:
>>> r8169 71677 0
>>> mii13527 1 r8169
>
> Looking at the help in the kernel for CONFIG_R8169:
>
> Selects: FW_LOADER [=y] && CRC32 [=y] && MII [=y]
How does one access this "help"?
> so mii is
On 11/25/2013 11:32 AM, Bruce Dubbs wrote:
> Alan Feuerbacher wrote:
>
>> r8169 71677 0
>
> This is what you need to configure in your kernel. Use y and not m.
Done.
My earlier emails indicate that I've gotten the card working.
> Then when you boot, you should see a device in
On 11/25/2013 11:27 AM, Dan McGhee wrote:
>
> Alan, you have gotten a number of great suggestions from some really
> helpful people. I think, however, that the waters are very muddy right
> now. The main problem is that your system can't find your ethernet
> card--eth0. That's the first goal. A
On 11/25/2013 11:04 AM, William Harrington wrote:
>
> On Nov 25, 2013, at 8:59 AM, Alan Feuerbacher wrote:
>
>> 2: p4p1: mtu 1500 qdisc pfifo_fast
>> state UP group default qlen 1000
>> link/ether 30:85:a9:8f:31:09 brd ff:ff:ff:ff:ff:ff
>> inet 10.0.1.31/24 brd 10.0.1.255 scope global p4
On 11/25/2013 10:15 AM, Fernando de Oliveira wrote:
> Em 25-11-2013 11:59, Alan Feuerbacher escreveu:
>> 2: p4p1: mtu 1500 qdisc pfifo_fast
>> state UP mode DEFAULT group default qlen 1000
>> link/ether 30:85:a9:8f:31:09 brd ff:ff:ff:ff:ff:ff
> I think that if you s/etho0/p4p1/ in the /etc
Dan McGhee wrote:
> I hope he either gets his card to come up or posts the results of 'dmesg
> | grep Ethernet' to determine whether the driver was loaded.
That may work for the Realtek driver, but it is not universal. I get no
output at all for that expression. I have:
e1000e: Intel(R) PRO/1
On 11/25/2013 12:46 PM, Fernando de Oliveira wrote:
> Em 25-11-2013 15:22, Dan McGhee escreveu:
>> On 11/25/2013 11:05 AM, Fernando de Oliveira wrote:
>>> Em 25-11-2013 13:27, Dan McGhee escreveu:
>
>>> It can find the interface.
>>>
>>> Replying to Ken, Alan wrote:
>>>
>>> Em 24-11-2013 14:04, Ala
Em 25-11-2013 15:22, Dan McGhee escreveu:
> On 11/25/2013 11:05 AM, Fernando de Oliveira wrote:
>> Em 25-11-2013 13:27, Dan McGhee escreveu:
>> It can find the interface.
>>
>> Replying to Ken, Alan wrote:
>>
>> Em 24-11-2013 14:04, Alan Feuerbacher escreveu:
>>> On 11/24/2013 10:48 AM, Ken Moffa
On 11/25/2013 11:05 AM, Fernando de Oliveira wrote:
> Em 25-11-2013 13:27, Dan McGhee escreveu:
>> Please excuse the "top post." I've done it for a reason.
>>
>> Alan, you have gotten a number of great suggestions from some really
>> helpful people. I think, however, that the waters are very mudd
On 11/25/2013 10:50 AM, Bruce Dubbs wrote:
> Dan McGhee wrote:
>> Please excuse the "top post." I've done it for a reason.
>>
>> Alan, you have gotten a number of great suggestions from some really
>> helpful people. I think, however, that the waters are very muddy right
>> now. The main problem
Em 25-11-2013 13:27, Dan McGhee escreveu:
> Please excuse the "top post." I've done it for a reason.
>
> Alan, you have gotten a number of great suggestions from some really
> helpful people. I think, however, that the waters are very muddy right
> now. The main problem is that your system ca
Dan McGhee wrote:
> Please excuse the "top post." I've done it for a reason.
>
> Alan, you have gotten a number of great suggestions from some really
> helpful people. I think, however, that the waters are very muddy right
> now. The main problem is that your system can't find your ethernet
> ca
Alan Feuerbacher wrote:
> r8169 71677 0
This is what you need to configure in your kernel. Use y and not m.
Then when you boot, you should see a device in /sys/class/net. It may
be p4p1 or something else.
You should have a file /etc/sysconfig/ifconfig.eth0
ONBOOT=yes
IFAC
Please excuse the "top post." I've done it for a reason.
Alan, you have gotten a number of great suggestions from some really
helpful people. I think, however, that the waters are very muddy right
now. The main problem is that your system can't find your ethernet
card--eth0. That's the firs
On Nov 25, 2013, at 8:59 AM, Alan Feuerbacher wrote:
> 2: p4p1: mtu 1500 qdisc pfifo_fast
> state UP group default qlen 1000
> link/ether 30:85:a9:8f:31:09 brd ff:ff:ff:ff:ff:ff
> inet 10.0.1.31/24 brd 10.0.1.255 scope global p4p1
>valid_lft forever preferred_lft forever
> in
Em 25-11-2013 11:59, Alan Feuerbacher escreveu:
> On 11/24/2013 2:33 PM, Pierre Labastie wrote:
>> Le 24/11/2013 19:24, David Kredba a écrit :
>> Before that and if you are still on LFS:
>> ip link list
>
> ###
> 1: lo: mtu 65536 qdisc noqueue state UNKNOWN mode
> DEFAULT group default
>
On 11/24/2013 2:33 PM, Pierre Labastie wrote:
> Le 24/11/2013 19:24, David Kredba a écrit :
>> Do you have pciutils installed?
>> If not install it (you can use liveCD or what you used to do first
>> installation and chroot inside your current system or download it and
>> copy in if you have USB st
On 11/24/2013 1:24 PM, David Kredba wrote:
> 2013/11/24 Alan Feuerbacher :
>> On 11/24/2013 10:33 AM, Bruce Dubbs wrote:
>>> Alan Feuerbacher wrote:
On 11/24/2013 12:19 AM, Bruce Dubbs wrote:
>>
>> Per Ken's suggestion, I added the ethernet driver for my Realtek
>> ethernet device, recompiled
Le 24/11/2013 19:24, David Kredba a écrit :
> Do you have pciutils installed?
> If not install it (you can use liveCD or what you used to do first
> installation and chroot inside your current system or download it and
> copy in if you have USB storage working etc.).
> Then start in single mode and
Do you have pciutils installed?
If not install it (you can use liveCD or what you used to do first
installation and chroot inside your current system or download it and
copy in if you have USB storage working etc.).
Then start in single mode and post output of lspci -v.
David
2013/11/24 Alan Feue
On 11/24/2013 10:33 AM, Bruce Dubbs wrote:
> Alan Feuerbacher wrote:
>> On 11/24/2013 12:19 AM, Bruce Dubbs wrote:
Per Ken's suggestion, I added the ethernet driver for my Realtek
ethernet device, recompiled the kernel, reinstalled systemd/udev from
scratch. Still no luck.
When linux starts, I
On 11/24/2013 10:48 AM, Ken Moffat wrote:
> I think Alan needs the r8169, this is what I use :
>
> CONFIG_NET_VENDOR_REALTEK=y
> and
> CONFIG_R8169=m (actually 'y' would be better, i.e. faster to come
> up)
Ok, I set that and recompiled the kernel. No luck; the eth0 interface
will not come up
On Sun, Nov 24, 2013 at 09:33:54AM -0600, Bruce Dubbs wrote:
> Alan Feuerbacher wrote:
> > On 11/24/2013 12:19 AM, Bruce Dubbs wrote:
> >> Alan Feuerbacher wrote:
> >>> Can anyone clue me in?
> >>
> >> It sounds like you don't have the right ethernet driver built. We
> >> recommend building it int
Alan Feuerbacher wrote:
> On 11/24/2013 12:19 AM, Bruce Dubbs wrote:
>> Alan Feuerbacher wrote:
>>> Can anyone clue me in?
>>
>> It sounds like you don't have the right ethernet driver built. We
>> recommend building it into the kernel.
>
> Ok, then I must have missed something when building the s
On 11/24/2013 12:19 AM, Bruce Dubbs wrote:
> Alan Feuerbacher wrote:
>> Can anyone clue me in?
>
> It sounds like you don't have the right ethernet driver built. We
> recommend building it into the kernel.
Ok, then I must have missed something when building the system. What do
I look for in the
Alan Feuerbacher wrote:
> Howdy,
>
> Now that my shiny new LFS system is more or less running, I'm trying to
> get all of the bits and pieces runnning.
>
> The system seems unable to find the ethernet card. The card is actually
> built into the mother board -- a Realtek RTL8111/8168/8411. After
> f
Howdy,
Now that my shiny new LFS system is more or less running, I'm trying to
get all of the bits and pieces runnning.
The system seems unable to find the ethernet card. The card is actually
built into the mother board -- a Realtek RTL8111/8168/8411. After
following the LFS book's instruction
61 matches
Mail list logo
