Gentoo Forums
Gentoo Forums
Gentoo Forums
Quick Search: in
Help newbie with Liva X installation
View unanswered posts
View posts from last 24 hours

 
Reply to topic    Gentoo Forums Forum Index Installing Gentoo
View previous topic :: View next topic  
Author Message
jamtat
Apprentice
Apprentice


Joined: 09 Aug 2003
Posts: 155

PostPosted: Sat Mar 14, 2015 4:24 pm    Post subject: Help newbie with Liva X installation Reply with quote

Ok. Pay no attention to the fact that I've been a member of this forum for over a decade. The fact of the matter is that all those years ago a friend of mine who was a Gentoo user installed the OS onto my laptop, after which he turned it over to me and I administered the system for a time. That was when/why I joined this forum. I spent a few months administering the system before deciding that Gentoo was just too complex and time-consuming for me. I went back to Debian/Ubuntu after that, though I did, some years later, switch from that to Arch. All this is to say that, though I've been a member of this board for a long time and do have limited experience running Gentoo, I am still a newbie when it comes to installing and running this distro.

I'm coming back to Gentoo after all these years as a MythTV user who is upgrading hardware. I learned on the MythTV users list that someone had managed to install and run quite well on their 1st generation Liva, a MythTV installation under Gentoo. So I thought I'd have a crack at it too. See the posts of those Liva users at https://forums.gentoo.org/viewtopic-t-1006786-start-0-postdays-0-postorder-asc-highlight-liva.html

So yesterday I used my Bohdi bootable USB stick to install Gentoo. I went through the handbook, adapting the directions to my boot media, prepared disks, got and unpacked the stage 3 tarball on the prepared partition. Everything went pretty smoothly and I got to the part that I was most hesitant about, compiling the kernel. I made my way through that--even though at least 50% of the options made little to no sense to me--and got to the stage of rebooting the machine. I should mention that, when compiling the kernel, I went with the suggestion offered in this thread https://forums.gentoo.org/viewtopic-t-1012666.html of "the . . . built in command line. . . . edit it during menuconfig to have a correct root= option." The option I entered in was root=/dev/mmcblk0p3 (3rd partition on the main hard drive, which is eMMC storage). Copied the kernel over to the fat32 partition on /boot/efi/boot and renamed it accordingly, crossed my fingers and rebooted.

On the reboot, as the machine began to boot into the new Gentoo installation, I got . . . drumroll . . . kernel panic. I actually would have been surprised if the system had booted on a first try like this. So I need help determing what the issue is and how to fix it. The kernal panic message, by the way, at the end of the stack trace, is "end kernel panic - not syncing: VFS: unable to mount the root fs on unknown--block (0,0)." So it's obviously not finding the root file system and likely the drive/partition itself. I should also state that my aim was to do without an initramfs--that's why I took the recommendation to do the built-in command line. I did not use genkernel.

So I know how to boot from my Bohdi USB drive and chroot back into Gentoo. It looks like, at the least, I've got to do another kernel compilation. What I need now is help in interpreting the kernel panic message and recommendations for how to recompile the kernel. I'll post below some output I generated using my Bodhi boot disk that will tell you more about the target hardware. Thanks in advance for any tips or pointers.

Hardware specifics:
Code:
lshw -short
H/W path         Device    Class       Description
==================================================
                           system      LIVA-XBAT2NBW-64 (To be filled by O.E.M.)
/0                         bus         BAT-MINI2
/0/0                       memory      64KiB BIOS
/0/28                      memory      4GiB System Memory
/0/28/0                    memory      4GiB DIMM DDR3 1600 MHz (0.6 ns)
/0/30                      memory      112KiB L1 cache
/0/31                      memory      1MiB L2 cache
/0/32                      processor   Intel(R) Celeron(R) CPU  N2808  @ 1.58GHz
/0/100                     bridge      ValleyView SSA-CUnit
/0/100/2                   display     ValleyView Gen7
/0/100/13                  storage     ValleyView 6-Port SATA AHCI Controller
/0/100/14                  bus         ValleyView USB xHCI Host Controller
/0/100/17                  generic     ValleyView MIPI-HSI Controller
/0/100/1a                  generic     ValleyView SEC
/0/100/1b                  multimedia  ValleyView High Definition Audio Controller
/0/100/1c                  bridge      ValleyView PCI Express Root Port
/0/100/1c.1                bridge      ValleyView PCI Express Root Port
/0/100/1c.1/0    wlan0     network     RT3290 Wireless 802.11n 1T/1R PCIe
/0/100/1c.1/0.1            generic     RT3290 Bluetooth
/0/100/1c.2                bridge      ValleyView PCI Express Root Port
/0/100/1c.2/0    p2p1      network     RTL8111/8168/8411 PCI Express Gigabit Ethernet Controller
/0/100/1f                  bridge      ValleyView Power Control Unit
/0/100/1f.3                bus         ValleyView SMBus Controller
/0/1             scsi2     storage     
/0/1/0.0.0       /dev/sda  disk        1048MB SCSI Disk

lsmod=================================================

Module                  Size  Used by
zram                   20081  2
lz4_compress           12529  1 zram
tda18212               13063  1
lgdt3305               19271  1
em28xx_dvb             31985  0
dvb_core              121659  2 em28xx_dvb,lgdt3305
intel_rapl             18783  0
arc4                   12608  2
rt2800pci              13630  0
rt2800mmio             20986  1 rt2800pci
rt2800lib              89076  2 rt2800pci,rt2800mmio
snd_hda_codec_hdmi     47548  1
rt2x00pci              13287  1 rt2800pci
intel_powerclamp       18823  0
rt2x00mmio             13603  2 rt2800pci,rt2800mmio
rt2x00lib              55307  5 rt2x00pci,rt2800lib,rt2800pci,rt2800mmio,rt2x00mmio
coretemp               13441  0
snd_hda_codec_realtek    72791  1
snd_hda_codec_generic    68937  1 snd_hda_codec_realtek
em28xx                 84619  1 em28xx_dvb
mac80211              652718  3 rt2x00lib,rt2x00pci,rt2800lib
snd_hda_intel          30428  5
snd_hda_controller     31056  1 snd_hda_intel
snd_hda_codec         139682  5 snd_hda_codec_realtek,snd_hda_codec_hdmi,snd_hda_codec_generic,snd_hda_intel,snd_hda_controller
kvm_intel             143590  0
kvm                   452043  1 kvm_intel
snd_hwdep              17698  1 snd_hda_codec
snd_pcm               104112  5 snd_hda_codec_hdmi,snd_hda_codec,snd_hda_intel,snd_hda_controller
snd_seq_midi           13564  0
snd_seq_midi_event     14899  1 snd_seq_midi
tveeprom               21216  1 em28xx
snd_rawmidi            30876  1 snd_seq_midi
cfg80211              494330  2 mac80211,rt2x00lib
snd_seq                63074  2 snd_seq_midi_event,snd_seq_midi
v4l2_common            15681  1 em28xx
crct10dif_pclmul       14307  0
videodev              153793  2 em28xx,v4l2_common
crc32_pclmul           13133  0
eeprom_93cx6           13344  1 rt2800pci
ghash_clmulni_intel    13230  0
dm_multipath           22843  0
cryptd                 20359  1 ghash_clmulni_intel
scsi_dh                14882  1 dm_multipath
joydev                 17393  0
snd_seq_device         14497  3 snd_seq,snd_rawmidi,snd_seq_midi
crc_ccitt              12707  1 rt2800lib
media                  21903  1 videodev
snd_timer              29562  2 snd_pcm,snd_seq
snd                    79468  20 snd_hda_codec_realtek,snd_hwdep,snd_timer,snd_hda_codec_hdmi,snd_pcm,snd_seq,snd_rawmidi,snd_hda_codec_generic,snd_hda_codec,snd_hda_intel,snd_seq_device
mei_txe                19704  0
mei                    87875  1 mei_txe
soundcore              15047  2 snd,snd_hda_codec
snd_soc_sst_acpi       13007  0
lpc_ich                21093  0
iosf_mbi               13541  0
mac_hid                13227  0
parport_pc             32741  0
ppdev                  17671  0
lp                     17759  0
parport                42348  3 lp,ppdev,parport_pc
squashfs               48362  1
overlayfs              27916  1
nls_utf8               12557  1
isofs                  39837  1
dm_mirror              22135  0
dm_region_hash         20862  1 dm_mirror
dm_log                 18411  2 dm_region_hash,dm_mirror
hid_generic            12559  0
usbhid                 52616  0
hid                   110426  2 hid_generic,usbhid
uas                    23159  0
usb_storage            66545  2 uas
mmc_block              36056  0
r8169                  71694  0
i915                  905798  6
mii                    13934  1 r8169
i2c_algo_bit           13413  1 i915
video                  20128  1 i915
drm_kms_helper         61574  1 i915
ahci                   34062  0
drm                   311018  8 i915,drm_kms_helper
libahci                32424  1 ahci
sdhci_pci              23301  0
sdhci                  43685  1 sdhci_pci

lspci============================

00:00.0 Host bridge: Intel Corporation ValleyView SSA-CUnit (rev 0e)
00:02.0 VGA compatible controller: Intel Corporation ValleyView Gen7 (rev 0e)
00:13.0 SATA controller: Intel Corporation ValleyView 6-Port SATA AHCI Controller (rev 0e)
00:14.0 USB controller: Intel Corporation ValleyView USB xHCI Host Controller (rev 0e)
00:17.0 SD Host controller: Intel Corporation ValleyView MIPI-HSI Controller (rev 0e)
00:1a.0 Encryption controller: Intel Corporation ValleyView SEC (rev 0e)
00:1b.0 Audio device: Intel Corporation ValleyView High Definition Audio Controller (rev 0e)
00:1c.0 PCI bridge: Intel Corporation ValleyView PCI Express Root Port (rev 0e)
00:1c.1 PCI bridge: Intel Corporation ValleyView PCI Express Root Port (rev 0e)
00:1c.2 PCI bridge: Intel Corporation ValleyView PCI Express Root Port (rev 0e)
00:1f.0 ISA bridge: Intel Corporation ValleyView Power Control Unit (rev 0e)
00:1f.3 SMBus: Intel Corporation ValleyView SMBus Controller (rev 0e)
02:00.0 Network controller: Ralink corp. RT3290 Wireless 802.11n 1T/1R PCIe
02:00.1 Bluetooth: Ralink corp. RT3290 Bluetooth
03:00.0 Ethernet controller: Realtek Semiconductor Co., Ltd. RTL8111/8168/8411 PCI Express Gigabit Ethernet Controller (rev 0c)
Back to top
View user's profile Send private message
jamtat
Apprentice
Apprentice


Joined: 09 Aug 2003
Posts: 155

PostPosted: Sat Mar 14, 2015 5:07 pm    Post subject: Reply with quote

Gotta admit that I find this whole eMMC storage thing a bit confusing. Here's some relevant dmesg output (gotten via Bodhi live environment), in case it may be helpful:
Code:
$dmesg |grep mmc
[    6.282627] mmc0: no vqmmc regulator found
[    6.282631] mmc0: no vmmc regulator found
[    6.305256] mmc0: SDHCI controller on PCI [0000:00:17.0] using ADMA
[    6.425735] mmc0: BKOPS_EN bit is not set
[    6.429529] mmc0: Got command interrupt 0x00000001 even though no command operation was in progress.
[    6.440206] mmc0: switch to bus width 2 failed
[    6.440528] mmc0: Got command interrupt 0x00000001 even though no command operation was in progress.
[    6.449616] mmc0: Got command interrupt 0x00010000 even though no command operation was in progress.
[    6.450914] mmc0: new HS200 MMC card at address 0001
[    6.454537] mmcblk0: mmc0:0001 064GE2 58.2 GiB
[    6.454756] mmcblk0boot0: mmc0:0001 064GE2 partition 1 4.00 MiB
[    6.454883] mmcblk0boot1: mmc0:0001 064GE2 partition 2 4.00 MiB
[    6.455016] mmcblk0rpmb: mmc0:0001 064GE2 partition 3 4.00 MiB
[    6.457613]  mmcblk0: p1 p2 p3
[    6.459455]  mmcblk0boot1: unknown partition table
[    6.460563]  mmcblk0boot0: unknown partition table
[    9.729558] EXT4-fs (mmcblk0p3): mounted filesystem with ordered data mode. Opts: (null)
[   23.028065] mmc0: Got data interrupt 0x00600000 even though no data operation was in progress.
[   39.164047] mmc0: Card stuck in programming state! __mmc_switch
[   39.164057] end_request: I/O error, dev mmcblk0, sector 268672
[   39.164065] Buffer I/O error on device mmcblk0p3, logical block 48
[   68.209046] EXT4-fs (mmcblk0p3): mounted filesystem with ordered data mode. Opts: (null)
[  467.446228] EXT4-fs (mmcblk0p3): mounted filesystem with ordered data mode. Opts: (null)

I have no idea what mmcblk0boot0, mmcblk0boot1, mmcblk0rpmb are. Those are not partitions I created, and they don't show up when I run fdisk or cfdisk on /dev/mmcblk0.
Back to top
View user's profile Send private message
jamtat
Apprentice
Apprentice


Joined: 09 Aug 2003
Posts: 155

PostPosted: Sat Mar 14, 2015 5:40 pm    Post subject: Reply with quote

Looking over my kernel config I've noticed that, under "USB physical layer drivers" I have "CONFIG_MMC is not set." Could this be a factor in the kernel panic? I remember seeing that option when I went through make menuconfig but was confused by it. The eMMC in this hardware is not, after all, a USB drive. Thoughts on this kernel option anyone, and whether, in my scenario, it should be set to Y?
Back to top
View user's profile Send private message
jamtat
Apprentice
Apprentice


Joined: 09 Aug 2003
Posts: 155

PostPosted: Sat Mar 14, 2015 6:57 pm    Post subject: Reply with quote

jamtat wrote:
Looking over my kernel config I've noticed that, under "USB physical layer drivers" I have "CONFIG_MMC is not set." Could this be a factor in the kernel panic? I remember seeing that option when I went through make menuconfig but was confused by it. The eMMC in this hardware is not, after all, a USB drive. Thoughts on this kernel option anyone, and whether, in my scenario, it should be set to Y?

I went through the make menuconfig again but do not find uner "USB physical layer drivers" any option for "CONFIG_MMC." I did find, under another section, some references to MMC/SD support that I'd not enabled. So I enabled those and recompiled the kernel. That didn't help though. I'm getting the same kernel panic. Any pointers, anyone?
Back to top
View user's profile Send private message
jamtat
Apprentice
Apprentice


Joined: 09 Aug 2003
Posts: 155

PostPosted: Sat Mar 14, 2015 8:18 pm    Post subject: Reply with quote

I found a thread at http://forum.porteus.org/viewtopic.php?t=3486&p=27572 that seemed to have some relevant information. To wit, in response to the question "which option in the config enables booting from eMMC cards?" the reply was :
Code:
[64bit config line:3939-3972]
==========================================================
CONFIG_MMC=y
# CONFIG_MMC_DEBUG is not set
# CONFIG_MMC_UNSAFE_RESUME is not set
# CONFIG_MMC_CLKGATE is not set

#
# MMC/SD/SDIO Card Drivers
#
CONFIG_MMC_BLOCK=y
CONFIG_MMC_BLOCK_MINORS=8
CONFIG_MMC_BLOCK_BOUNCE=y
CONFIG_SDIO_UART=m
# CONFIG_MMC_TEST is not set

#
# MMC/SD/SDIO Host Controller Drivers
#
CONFIG_MMC_SDHCI=y
CONFIG_MMC_SDHCI_PCI=m
CONFIG_MMC_RICOH_MMC=y
CONFIG_MMC_SDHCI_ACPI=y
CONFIG_MMC_SDHCI_PLTFM=m
CONFIG_MMC_SDHCI_PXAV3=m
CONFIG_MMC_SDHCI_PXAV2=m
CONFIG_MMC_WBSD=m
CONFIG_MMC_TIFM_SD=m
CONFIG_MMC_SDRICOH_CS=m
CONFIG_MMC_CB710=m
CONFIG_MMC_VIA_SDMMC=m
CONFIG_MMC_VUB300=m
CONFIG_MMC_USHC=m
CONFIG_MMC_REALTEK_PCI=m
CONFIG_MEMSTICK=y
# CONFIG_MEMSTICK_DEBUG is not set
==========================================================

I tried to mirror those options in a subsequent make menuconfig, and all but the CONFIG_MEMSTICK were available. I couldn't set that one so I did the others and recompiled. Still getting the kernel panic though.
Back to top
View user's profile Send private message
jamtat
Apprentice
Apprentice


Joined: 09 Aug 2003
Posts: 155

PostPosted: Sat Mar 14, 2015 8:29 pm    Post subject: Reply with quote

Just noted this at the https://forums.gentoo.org/viewtopic-t-1006786-highlight-liva.html thread:
Quote:
If it helps any, I found out that an initramfs / dracut is NOT required. I too like to keep things simple. The key was that the system was loading too fast for the eMMC to be available in time for the root mount... so the fix was to edit /etc/default/grub, and add 'rootdelay=8' to the GRUB_CMDLINE_LINUX_DEFAULT line for default kernel parameters and regenerate the grub config. After that, the system would pause on boot, the eMMC partitions would populate, and then the booting would resume with the root filesystem mount after the 8 second timeout. 8 seconds was somewhat arbitrary... less may be OK, but I decided to play it safe.
Perhaps that's my problem: the system is loading too fast for the eMMC to be available in time for the root mount. So what are valid arguments to pass to the built-in kernel command line? Can I, in addition to the root=/dev/mmcblk0p3 add the additional argument rootdelay=8? Or will that be valid only under GRUB?
Back to top
View user's profile Send private message
jamtat
Apprentice
Apprentice


Joined: 09 Aug 2003
Posts: 155

PostPosted: Sat Mar 14, 2015 9:39 pm    Post subject: Reply with quote

The rootdelay argument does seem to be a valid one for the built-in kernel command line--at least a period of inactivity occurs shortly after the boot starts, once that argument has been introduced and the kernel recompiled (the command line under discussion is root=/dev/mmcblk0p3 rootdelay=5). But I still get a kernel panic--just takes longer for it to show up. I tried both rootdelay=5 and then rootdelay=10, but I get the kernel panic with both.

I decided to compare my kernel config file with the one SiliconFiend posted at https://dl.dropboxusercontent.com/u/6715292/ECS%20Liva%203.17.7-gentoo.config . That config, with respect to the mmc options, pretty much matches what I had in my config before I introduced changes suggested at the porteus forum as listed above.

So I'm kinda at a loss here. Short of receiving input from someone more knowledgeable than myself as to what could be the nature of the problem I'm dealing with, the only thing I could think of to try would be to go the initramfs route. Seems like a bit of a cop-out if part of the idea of going through this sort of an installation is to learn something: doing that would be kind of like grasping at straws. So I think I'll have to set aside this project for now, waiting to either get input from someone who might have a better understanding of what I might be doing wrong, or until I get some other ideas, possibly from conducting further research about this hardware and about Gentoo.

Again, any input will be appreciated.
Back to top
View user's profile Send private message
jamtat
Apprentice
Apprentice


Joined: 09 Aug 2003
Posts: 155

PostPosted: Sat Mar 14, 2015 10:47 pm    Post subject: Reply with quote

Thought of a couple other things I could try. Decided first that, since I'm trying not to use an initramfs, and since the kernel seemed to be having problems detecting the mmc storage, that it didn't make sense to have mmc-related stuff compiled as modules. So I changed a bunch of MMC/SD/SDIO stuff from M to yes. Then I ran across another kernel option that can be passed instead of rootdelay=: that is rootwait. According to the kernel docs,
Quote:
rootwait [KNL] Wait (indefinitely) for root device to show up. Useful for devices that are detected asynchronously (e.g. USB and MMC devices).
The link that explains the various parameters that can be passed on the kernel command line is https://www.kernel.org/doc/Documentation/kernel-parameters.txt , incidentally.

So I went through another recompile with those options implemented. Not a whole lot changes with those tweaks. One sort of positive development is that there is no longer--owing, I think, to the rootwait switch--any kernel panic. But since the eMMC storage is not detected, the kernel just pauses indefinitely, waiting for it to appear. USB stuff is obviously detected, as screen output shows, but the built-in eMMC storage cannot, for whatever reason, be detected by the kernel.
Back to top
View user's profile Send private message
jamtat
Apprentice
Apprentice


Joined: 09 Aug 2003
Posts: 155

PostPosted: Sun Mar 15, 2015 9:37 pm    Post subject: Reply with quote

Still at a bit of a loss here, even after having done some additional research. In retrospect I might have named this thread differently--something along the lines "how to boot Gentoo from eMMC." But I presumed that this would be the first of a few problems I would confront, then resolve, with the Liva X: I envisioned adding additional requests to the thread as issues got resolved, so I gave it a more generic-sounding title. Of course if I can't resolve this first one, there'll be no further issues to discuss: I obviously can't finish installing Gentoo unless I'm able to boot to the drive where I'm already partway through the installation.

I did finally find and enable the CONFIG-MEMSTICK option, but a recompile after that didn't resolve my issues. I did manage to find out something about the mysterious /dev/mmcblk0rpmb partition at https://wiki.archlinux.org/index.php/Acer_Aspire_ES1-111M (Replay Protected Memory Block partition) as well, but that's not really pertinent to getting the kernel to see the eMMC.

Let me close this post by asking whether my understanding of what I'm trying to do here sounds correct. I see myself as trying to compile into the kernel support for all hardware related to this machine so as to not have to do any module loading and, corollary to this, having a ramdisk. Is there anything incorrect in my understanding of the task or my conception of how all this is supposed to work?

Finally, on the issue of an initramfs. I cannot see how having one would address the issues I'm seeing: if I can't get the kernel to see the eMMC storage by compiling into the kernel support for it, how will having an initramfs (that will, presumably, contain loadable modules for the eMMC) help? Trying out an initramfs is still the only alternative I can think of to try. But, as I said, it seems a bit like grasping at straws, since I can't understand what is keeping the kernel from seeing the eMMC. It looks to me at this stage that trying that would end up being a matter of just kicking the can a bit further down the road. But I may well be wrong. Anyone see the initramfs approach as being a viable path forward?

Again, input will be appreciated.


Last edited by jamtat on Mon Mar 16, 2015 2:04 pm; edited 1 time in total
Back to top
View user's profile Send private message
gentoodriver
n00b
n00b


Joined: 16 Mar 2015
Posts: 1

PostPosted: Mon Mar 16, 2015 3:48 am    Post subject: Reply with quote

Here is a 32-bit kernel config that works with the LIVA X:

http://pastebin.com/z0cNGi67

A couple things to look for: there are a lot of Synopsys DesignWare components in this system, most of them have a DW in the config name. Good luck!

Edit: remove the "CONFIG_USB_OZONE=y" line, that is for a custom driver that isn't in stock kernel.
Back to top
View user's profile Send private message
jamtat
Apprentice
Apprentice


Joined: 09 Aug 2003
Posts: 155

PostPosted: Mon Mar 16, 2015 1:55 pm    Post subject: Reply with quote

Thanks for your response, gentoodriver. I'll be having a look over your config file, comparing it with mine, and paying particular attention to lines containing DW. I'll just point out additionally that it looks like we're not doing quite the same thing: I note that you do not have CONFIG_CMDLINE_BOOL set, and thus have no CONFIG_CMDLINE="root=" line either. That, it seems to me, is where my installation is getting tripped up.

I decided to follow your example as well and have posted my current kernel config at http://pastebin.com/tSsmxNRj . Perhaps this will enable me to get some further input on my issues.
Back to top
View user's profile Send private message
jamtat
Apprentice
Apprentice


Joined: 09 Aug 2003
Posts: 155

PostPosted: Mon Mar 23, 2015 11:57 pm    Post subject: Reply with quote

I took someone's suggestion to put the device into Windows 8 mode with CSM (compatibility support module), then to make the eMMC the first in boot device order. I don't know whether it was this by itself, or this in combination with additional kernel compilations I did, but the device began fully booting after I'd done that. Now that I've finally gotten it to fully boot, I'm trying to finish up the base installation and get networking and other central system features operational.

One thing I will want to do soon is to get a DHCP server running on the wired NIC in this thing. I'm setting up the wifi card as the main interface that will be used for most internet stuff, but will have a device that hooks to the wired port and should get its IP from the Liva. Can anyone offer some suggestions on getting a DHCP server running on the wired interface? Thanks.
Back to top
View user's profile Send private message
jamtat
Apprentice
Apprentice


Joined: 09 Aug 2003
Posts: 155

PostPosted: Tue Mar 24, 2015 6:03 am    Post subject: Reply with quote

jamtat wrote:
One thing I will want to do soon is to get a DHCP server running on the wired NIC in this thing. I'm setting up the wifi card as the main interface that will be used for most internet stuff, but will have a device that hooks to the wired port and should get its IP from the Liva. Can anyone offer some suggestions on getting a DHCP server running on the wired interface? Thanks.

I ran across this https://wiki.gentoo.org/wiki/Home_Router which looks fairly dated (references the 2.4.x kernel). Specifically, it directs to emerge the net-dns/dnsmasq package, describing how to get a given NIC to serve IP's--by editing /etc/dnsmasq.conf. Looks pretty simple if that's really all there is to it. So, are those directions still vaild?
Back to top
View user's profile Send private message
jamtat
Apprentice
Apprentice


Joined: 09 Aug 2003
Posts: 155

PostPosted: Tue Mar 24, 2015 4:10 pm    Post subject: Reply with quote

jamtat wrote:
I ran across this https://wiki.gentoo.org/wiki/Home_Router which looks fairly dated (references the 2.4.x kernel). Specifically, it directs to emerge the net-dns/dnsmasq package, describing how to get a given NIC to serve IP's--by editing /etc/dnsmasq.conf. Looks pretty simple if that's really all there is to it. So, are those directions still vaild?

I went ahead and used those directions and they worked. The only minor hang-up was a user error: I initially gave the Liva's wired NIC a subnet address ending in 0 (e.g., 192.168.100.0) and, although a test machine hooked to the Liva's wired NIC would get an IP when it polled for one, no traffic was moving to or from the Liva. I realized my mistake fairly quickly though, and once I'd corrected matters and given the wired NIC a subnet address ending in 1 (e.g., 192.168.100.1), all began working fine. So, another hurdle surmounted, it seems.
Back to top
View user's profile Send private message
jamtat
Apprentice
Apprentice


Joined: 09 Aug 2003
Posts: 155

PostPosted: Tue Mar 24, 2015 7:41 pm    Post subject: Reply with quote

I'm moving on now to installing MythTV, which will be the primary function of this hardware. I'm following instructions that can were posted recently on the mythtv-users mailing list, as follows:
Quote:
2/27/15 rev
1. Install the MythTV

# emerge -av mythtv

2. Enable and start MySQL

# emerge --config =dev-db/mariadb-10.0.16
# rc-update add mysql default && rc-service mysql start

3. You'll also need to check that the "networking" feature of MySQL is
turned on. Check that /etc/mysql/my.cnf does not contain skip-networking.
If it does, either remove that line or comment it out. Also verify that
bind-address is set to your IP address instead of 127.0.0.1. Alternatively
/etc/conf.d/mysql can be used to address skip-networking and bind-address.
Set MY_ARGS="--bind-address=masterbackendipaddress" and skip-networking
default is off. If you change either of these items, restart MySQL.

# rc-service mysql restart

4. Setup mysql and add a password:

# mysql_secure_installation

5. Create the database structure: (See example using root as user and 1234
as password)

# mysql -u root -p1234 </usr/share/mythtv/database/mc.sql

6. Update your database (Optional with new install): (See example using
root as user and 1234 as password)

# mysql_upgrade -u root -p1234

7. Add time zone tables: (See example using root as user and 1234 as
password)

$ mysql_tzinfo_to_sql /usr/share/zoneinfo | mysql -u root -p1234 mysql

8. Allow remote frontends access: (See example using mythtv as user, mythtv
as password and root as user, 1234 as password)

# mysql -u root -p1234
MariaDB [(none)]> GRANT ALL ON mythconverg.* TO 'mythtv'@'192.168.97.%'
IDENTIFIED BY 'mythtv';
***Query OK, 0 rows affected (0.00 sec)***output only!
MariaDB [(none)]> FLUSH PRIVILEGES;
***Query OK, 0 rows affected (0.00 sec)***output only!
MariaDB [(none)]> exit
***Bye***output only!

9. Enable mythbackend

# rc-update add mythbackend default

10. Setup mythbackend

$ mythtv-setup

If restoring a database backup, complete the General section only then
perform the database backup.
Example command:
./mythconverg_restore.pl --drop_database --create_database --directory
/home/username/Desktop --filename mythconverg-1317-20150227105348.sql.gz

11. Setup logging for mythfrontend and mythbackend.

A. Change permissions on /var/log/mythtv with chown for the user you are
running mythtv.

B. Edit /etc/conf.d/mythfrontend
Replace
#MYTHFRONTEND_OPTS="--syslog local7"
With
MYTHFRONTEND_OPTS="--quiet --logpath /var/log/mythtv"

C. Edit /etc/conf.d/mythbackend
Replace
#MYTHBACKEND_OPTS=""
With
MYTHBACKEND_OPTS="--quiet --logpath /var/log/mythtv"
*****This isn't needed due it is setup in the /etc/init.d/mythbackend

12. No icons/launchers, to start Mythtv frontend or backend are created.
Solution - KDE
Right click on KDE homerun icon and select edit applications.
Select Multimedia
Select new item
Enter Mythtv for item name
Enter mythfrontend for command
Select the empty icon window
Select other icons and then browse
Select mythfrontend photo
Select edit>sort>sort all by name
Select save and close
Back to top
View user's profile Send private message
jamtat
Apprentice
Apprentice


Joined: 09 Aug 2003
Posts: 155

PostPosted: Wed Mar 25, 2015 3:02 am    Post subject: Reply with quote

Now I've gotten kind of confused about what goes in make.conf regarding my video hardware. I've got Intel video hardware, the one that uses the i915 driver. Particularly, I'm confused by the statement '"intel" is for x11-base/xorg-drivers and i915 resp. i965 are for media-libs/mesa' as found on the wiki at https://wiki.gentoo.org/wiki/Intel . Does this mean I need both VIDEO_CARDS="intel" and VIDEO_CARDS="intel i915" in my make.conf? Or just one of those two entries . . . and if so, which one? Your input will be appreciated.
Back to top
View user's profile Send private message
Jaglover
Watchman
Watchman


Joined: 29 May 2005
Posts: 7092
Location: Saint Amant, Acadiana

PostPosted: Wed Mar 25, 2015 8:41 am    Post subject: Reply with quote

VIDEO_CARDS="intel i915" will work.

Just looked up this hardware, you do not want compile much on this baby, it is reported to reach 80 C under load (you can fry eggs on it). I strongly recommend distcc in pump mode.
_________________
Please learn how to denote units correctly!
Back to top
View user's profile Send private message
jamtat
Apprentice
Apprentice


Joined: 09 Aug 2003
Posts: 155

PostPosted: Wed Mar 25, 2015 3:42 pm    Post subject: Reply with quote

Thanks for your input, jaglover: I've now got X up and running. I'll look into distcc and see whether I might be able to implement that.

Meantime, here's my latest roadblock. I've got a USB tuner, the KWorld UB435-Q USB ATSC TV Stick (see http://www.linuxtv.org/wiki/index.php/KWorld_UB435-Q_USB_ATSC_TV_Stick ) that is supposed to be compatible with MythTv, but I'm having trouble setting it up. I believe the modules for it are all present, since I specifically tried to compile them into the kernel. The stick shows up when I run lsusb as Bus 001 Device 003: ID 1b80:e34c Afatech. Yet I am unable to set it up under mythtv-setup; I believe the issue is that there is somehow no device node present for it. Can anyone offer advice on how I can get the system to make this stick present to MythTV? Maybe I'll have to make a separate thread on this since the stick is actually an add-on I've connected to the Liva and so this is not a Liva-sepcific query. Anyway, input will be appreciated.

Follwoing is dmesg output related to this device:
Code:
[    4.756907] em28xx: New device  USB 2875 Device @ 480 Mbps (1b80:e34c, interface 0, class 0)
[    4.756914] em28xx: DVB interface 0 found: bulk
[    4.757286] em28xx: chip ID is em2874
[    4.932547] em2874 #0: EEPROM ID = 26 00 01 00, EEPROM hash = 0x5d3e97ab
[    4.932553] em2874 #0: EEPROM info:
[    4.932557] em2874 #0:       microcode start address = 0x0004, boot configuration = 0x01
[    4.956213] em2874 #0:       AC97 audio (5 sample rates)
[    4.956217] em2874 #0:       500mA max power
[    4.956222] em2874 #0:       Table at offset 0x24, strings=0x206a, 0x048a, 0x0000
[    4.956293] em2874 #0: Identified as KWorld USB ATSC TV Stick UB435-Q V3 (card=93)
[    4.956298] em2874 #0: dvb set to bulk mode.
[    4.956354] usbcore: registered new interface driver em28xx
[    4.961261] em2874 #0: Binding DVB extension
[    4.972469] DVB: registering new adapter (em2874 #0)
[    4.973853] em2874 #0: DVB extension successfully initialized
[    4.973861] em28xx: Registered (Em28xx dvb Extension) extension
Back to top
View user's profile Send private message
Jaglover
Watchman
Watchman


Joined: 29 May 2005
Posts: 7092
Location: Saint Amant, Acadiana

PostPosted: Wed Mar 25, 2015 5:19 pm    Post subject: Reply with quote

You probably miss a driver or two for this stick in your kernel.
_________________
Please learn how to denote units correctly!
Back to top
View user's profile Send private message
Display posts from previous:   
Reply to topic    Gentoo Forums Forum Index Installing Gentoo All times are GMT
Page 1 of 1

 
Jump to:  
You cannot post new topics in this forum
You cannot reply to topics in this forum
You cannot edit your posts in this forum
You cannot delete your posts in this forum
You cannot vote in polls in this forum