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
>>>
>>
Again with the great suggestions of several people, I got the mouse to work.
Bottom line: I completely misunderstood the instructions in the BLFS
book on installing Cups. A note on kernel configuration says:
"There is a conflict between the Cups libusb backend and the usblp
kernel driver. If yo
Now that I've got my linux-3.12 system up and running, and the ethernet
card running, I'm running into another problem:
The mouse is not detected.
The mouse (an older Microsoft Intellimouse USB model) works fine with
the mouse-based BIOS and with my Fedora installation, so there's
probably som
On 11/25/2013 9:06 PM, Dan McGhee wrote:
> ...
> Here's the mystery for me: Alan and I have the same NIC. We probably
> have different boxes, but I don't think that's relevant. He built
> LFS-7.4 just like I did. Kernel 3.10.10 + identical NIC = same kernel
> configuration. However, his NIC is
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,
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.
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
gt; 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 Feuerbacher :
>>> On 11/24/2013 10:33 AM, Bruce Dubbs wrote:
>>>> Alan Feuerbacher wrote:
>>>
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 drive
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 l
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 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. Wha
On 11/24/2013 12:07 AM, Bruce Dubbs wrote:
> Alan Feuerbacher wrote:
>> Well I finally found the problem why linux would not boot: for some
>> reason grub is assigning (hd0) to /dev/sdb.
>
> I suspect that's because you installed GRUB on /dev/sdb. IIRC, you did
>
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
On 11/23/2013 3:21 PM, Dan McGhee wrote:
> On 11/23/2013 01:32 PM, Alan Feuerbacher wrote:
>>> So for whatever reason, grub is not recognizing the disks. Having tried
>>> the same thing with the two other disks, /dev/sda and /dev/sdc, which
>>> grub lists above as
On 11/23/2013 3:05 PM, Ken Moffat wrote:
> I've also got a much-less-important comment on your kernel names as
> a reply to your earlier post: You had four variants of 3.12 lfs
> kernels. All of them had the same size in bytes, one was from nearly
> two days before the rest, of the others two h
Well I finally found the problem why linux would not boot: for some
reason grub is assigning (hd0) to /dev/sdb. The latter is where I've
installed LFS. So in grub.cfg I changed "set root=(hd1,1)" to "set
root=(hd0,1)". Following the syntax in the grub.cfg in Fedora19's
installation on /dev/sda,
On 11/23/2013 4:43 AM, Pierre Labastie wrote:
> Le 23/11/2013 03:39, Alan Feuerbacher a écrit :
>
> I do not see "vmlinuz-3.12-lfs-SVN-20131105" (as mentioned in
> /boot/grub/grub.cfg) in the listing of the /boot directory...
>
> I think the line in grub.cfg could be:
&
Having had no success this past week in getting an LFS system running under
UEFI booting with LVM volume management and GPT partitioning, I decided to
install a fresh copy of LFS on a new hard drive. I did my best to follow the
LFS book (development version) exactly, and this evening was able to tr
On 11/16/2013 6:10 PM, Dan McGhee wrote:
> If I can't make any head-way in the next few days, I'm going to install
> a minimal ArchLinux system and try the various GRUB options. I don't
> think they sign their kernels--see last paragraph--and that will test
> the GRUB stuff.
About 3 weeks ago, a
On 11/16/2013 8:56 PM, Geoff Swan wrote:
> On 17/11/2013 11:26 AM, Dan McGhee wrote:
>> Just so I understand. You got your kernel--3.10.10 (?)--to boot from
>> the EFI partition? And without initrd or initramfs? The answer to
>> this question is important to me.
>
> Yes. 3.10.10. Selectable in t
On 11/16/2013 8:17 PM, Dan McGhee wrote:
> Alan, thank you for validating my research. Let me validate yours. Those
> recommendations work.
Good!
> Did you see the questions I asked you earlier? I hope you will answer
> them. They are important to my research.
Yeah, I saw them. I'm in the proce
On 11/16/2013 7:43 PM, Nathanial Jones wrote:
> I would love it if someone could post a link to a mirror or send me the
> package directly.
Check your mail.
Alan
--
http://linuxfromscratch.org/mailman/listinfo/lfs-support
FAQ: http://www.linuxfromscratch.org/lfs/faq.html
Unsubscribe: See the a
On 11/16/2013 7:36 PM, Dan McGhee wrote:
> I think efivarfs is new in 3.10.10 "CONFIG_EFIVAR_FS=(y or m)" is what
> I recommend if you're using 3.10.10
The information I've gotten so far about setting these CONFIG variables,
from Arch Linux, rodsbooks.com and other places, is summarized here,
Hi,
After getting the stock LFS system installed, with an MBR type boot
installation, I'm experimenting with installing to a UEFI type boot
location on a brand new hard drive. I've been reading a lot of online
documentation, and have tried a first-cut installation, but am not
having success in
Howdy,
I've done a major reset by giving up on installing an LFS system on my
old 32-bit computer, and am now installing it on a new 64-bit system.
The new system now has Fedora as the host system. It's installed on
/dev/sdb and I want to put LFS on a blank 256G SSD -- /dev/sda.
In trying to f
28 matches
Mail list logo
