On Fri, Nov 06, 2015 at 04:16:03PM -0500, David Mehler wrote: > Hello, > > I've just got my first Lfs 7.8 system to boot! > > I'm seeing a few problems and a few questions. Here are my boot up messages: > > Booting `LFS GNU/Linux' > error: no symbol table. > Loading Linux 3.19-lfs-7.8 ... > > The boot proceeds normally and I did see references to this, but no > solution. Is it a harmless error? I'm using a Vmware Workstation vm > for this install. > The error appears to come from grub. If the boot continues, then it is probably harmless. Last September, somebody who noticed this inferred that it was caused by stripping grub, but AFAICS he never followed up to confirm.
> [ 0.000000] WARNING: BIOS bug: CPU MTRRs don't cover all of memory, > losing 12MB of RAM. > [ 0.000000] WARNING: CPU: 0 PID: 0 at > arch/x86/kernel/cpu/mtrr/cleanup.c:971 > mtrr_trim_uncached_memory+0x45c/0x487() > > Googled these, didn't see anything. > > [ 0.000000] ACPI: Early table checksum verification disabled > > This one sounds worrisome, is it? > Probably not. ACPI is almost as much of a heap of ordure as BIOS and UEFI. Unless it stops something working, I would not worry about it. On real hardware I tend to get various ACPI messages but the kernels work fine for my needs. > [ 0.000000] smpboot: 128 Processors exceeds NR_CPUS limit of 64 > [ 0.000000] smpboot: Allowing 64 CPUs, 62 hotplug CPUs > > Is this one having to do with hotpluggable CPUs or my logical cores? > I've got an 8 core system, of which this vm has two cores. > I will guess that vmware is claiming to have 128 processors, but that your kernel .config used a lower number. On my own machines, I normally use a much smaller number (I don't have 8 cores) to save a _little_ kernel memory. If you run grep '^processor' /proc/cpuinfo how many CPUs are supposedly present ? I know nothing about the details of vmware, but if it gives a silly number, perhaps you can configure it. > [ 0.607618] pci 0000:00:18.6: BAR 7: no space for [io size 0x1000] > [ 0.608608] pci 0000:00:18.6: BAR 7: failed to assign [io size 0x1000] > [ 0.609618] pci 0000:00:18.5: BAR 7: no space for [io size 0x1000] > [ 0.610599] pci 0000:00:18.5: BAR 7: failed to assign [io size 0x1000] > [ 0.611608] pci 0000:00:18.4: BAR 7: no space for [io size 0x1000] > [ 0.612610] pci 0000:00:18.4: BAR 7: failed to assign [io size 0x1000] > > This one repeats for a while, do I need to adjust anything? > I googled for 'BAR 7 io space assignment error' : there was a thread on lkml in May, but that seems to have been for a Freescale machine (i.e. not x86). Perhaps vmware is just presenting itself as a weird machine. Dunno. > [ 2.593687] sound hdaudioC0D0: No codec parser is available > [ 2.602104] ALSA device list: > [ 2.602995] #0: HD-Audio Generic at 0xfdfec000 irq 59 > > Again this is with the vmware sound card emulation, what do I need to > give to allow my card to work the missing codec? > Again, I googled. One (probably old) post suggested vmware uses a Creative Labs SoundBlaster16 - I actually had one of those once, many years ago. I've no idea how vmware presents its soundcard, but it looks as if you have built hdaudio. Again, check how you have set up vmware (and see what sound "cards" it can claim to provide), then change the .config. Worst case, try building ALL the PC sound drivers as modules, with ALL of the options (when applicable, e.g. in hdaudio) enabled, then see if anything sticks. > This next one goes with the network interface. I'd prefer my > interfaces to be named eth0, eth1, etc and to let Linux worry about > the driver needed, I like consistent interface names. > > [ 3.930679] e1000 0000:02:01.0 eno16777736: renamed from eth0 > [ 3.938555] udevd[2664]: renamed network interface eth0 to eno16777736 > > There was a section in the book on this, which I have done, this is is > indicating I missed something. Any ideas welcome. > I think you are saying that you have created the ifconfig.eth0 file (for a static address) ? Check also section 7.4 'Managing Devices' which has options at 7.4.1.1 and 7.4.1.2. The first option looks easiest, but _if_ you ran the script (7.4.1.2) and it somehow created a _different_ MAC address in the rule, then the interface will be renamed - that has caught me in the past when I moved a copy of an LFS system to a new machine. ĸen -- Il Porcupino Nil Sodomy Est! (if you will excuse my latatian) aka "The hedgehog song" -- http://lists.linuxfromscratch.org/listinfo/lfs-support FAQ: http://www.linuxfromscratch.org/blfs/faq.html Unsubscribe: See the above information page Do not top post on this list. A: Because it messes up the order in which people normally read text. Q: Why is top-posting such a bad thing? A: Top-posting. Q: What is the most annoying thing in e-mail? http://en.wikipedia.org/wiki/Posting_style
