usb flash install - waiting for directory /minimyth to mount

Help with booting MiniMyth

Moderator: Pablo

kingmoffa
Member
Posts: 39
Joined: Wed Sep 05, 2007 9:35 pm

usb flash install - waiting for directory /minimyth to mount

Post by kingmoffa » Wed Sep 05, 2007 9:42 pm

Hi,

I've just got some new hardware for my mini myth frontend. However using my 20.1 install my machine hung on waiting for

waiting for directory /minimyth to mount ...

Under 20.2 this is also the case. I have telnet access to the box and in /var/log/messages there :

Sep 5 20:32:14 (none) local0.info minimyth: starting telnet ...
Sep 5 20:32:15 (none) local0.info minimyth: loading kernel modules (automatic) ...
Sep 5 20:32:17 (none) local0.info minimyth: waiting for directory /minimyth to mount ...
Sep 5 20:32:18 (none) local0.info minimyth: waiting for directory /minimyth to mount ...

Looking at a previous post with a similar problem. It seemed an ide module may have caused this.

Can anyone pls help me resolve?

Pablo
Site Admin
Posts: 4182
Joined: Tue Dec 14, 2004 2:13 am
Location: La Jolla
Contact:

Post by Pablo » Sat Sep 08, 2007 2:12 am

What is the hardware?
What is the MiniMyth version?
MiniMyth running on an Acer ApireRevo 3610 and a Zotac ZBOX-ID80-U. Find out more at my MythTV page.

kingmoffa
Member
Posts: 39
Joined: Wed Sep 05, 2007 9:35 pm

Post by kingmoffa » Sat Sep 08, 2007 12:18 pm

Hi Pablo ,

Its the latest stable mythmini, 0.20.2-30 i think. I used the mm_local_install script and it grabbed data from the internet with whatever the URL_DEFAULT setting is.

I had the same problem with the older mimimyth install i had which was whatever the stable version was about 5 months ago.

The hardware is a celeron processor 2.5Ghz , with a Asustek P4S800-MX motherboard. The ide controller i is: 00:02.5 IDE interface: Silicon Integrated Systems [SiS] 5513 [IDE].

As mentioned, this is was a hardware upgrade from a celeron 900mhz. The same 1gb sandisk compact flash card and ide->cf adaptor are being used.

The onboard network card is a bit tempremental , so I have a 3com pci nic. I think this may rule out a network boot, so flash is the only way.


Im wondering if its an ide problem. This maybe useful (or not) as I t

root@(none):/var/log $ dmesg | grep -i ide
Boot video device is 0000:01:00.0
eth0: Identified 8139 chip type 'RTL-8139C'
root@(none):/var/log $ dmesg | grep -i sis
Enabling SiS 96x SMBus.

Pablo
Site Admin
Posts: 4182
Joined: Tue Dec 14, 2004 2:13 am
Location: La Jolla
Contact:

Post by Pablo » Sun Sep 09, 2007 5:48 pm

MiniMyth does not have the sis5513 IDE kernel driver. As a result, I suspect the kernel cannot mount the flash drive.

In addition, MiniMyth does not have the SiS Xorg driver. As a result, I suspect that X will not start were you to get past the problem that you are currently having.
MiniMyth running on an Acer ApireRevo 3610 and a Zotac ZBOX-ID80-U. Find out more at my MythTV page.

kingmoffa
Member
Posts: 39
Joined: Wed Sep 05, 2007 9:35 pm

Post by kingmoffa » Sun Sep 09, 2007 6:52 pm

thanks. I thought it may be something that looking at the modules dir. I have an nvidia card , so graphics wont be a prob.

Would building mythmini from source solve the problem of the missing ide module?

Pablo
Site Admin
Posts: 4182
Joined: Tue Dec 14, 2004 2:13 am
Location: La Jolla
Contact:

Post by Pablo » Sun Sep 09, 2007 11:42 pm

The MiniMyth build system does not support building the SiS drivers. However, I could add it relatively easily. Could you provide the output of the following commands so that I make sure that I include the drivers for you motherboard in the build system:

Code: Select all

dmidecode -t baseboard

Code: Select all

dmidecode -t processor

Code: Select all

lspci -mn

Code: Select all

lsusb
MiniMyth running on an Acer ApireRevo 3610 and a Zotac ZBOX-ID80-U. Find out more at my MythTV page.

kingmoffa
Member
Posts: 39
Joined: Wed Sep 05, 2007 9:35 pm

Post by kingmoffa » Mon Sep 10, 2007 12:56 pm

root@(none):~ $ dmidecode -t baseboard
# dmidecode 2.9
SMBIOS 2.3 present.

Handle 0x0002, DMI type 2, 8 bytes
Base Board Information
Manufacturer: ASUSTeK Computer INC.
Product Name: P4S800MX
Version: REV 1.xx
Serial Number: xxxxxxxxxxx



root@(none):~ $ dmidecode -t processor
# dmidecode 2.9
SMBIOS 2.3 present.

Handle 0x0004, DMI type 4, 32 bytes
Processor Information
Socket Designation: PGA 478
Type: Central Processor
Family: Celeron
Manufacturer: GenuineIntel
ID: 34 0F 00 00 FF FB EB BF
Signature: Type 0, Family 15, Model 3, Stepping 4
Flags:
FPU (Floating-point unit on-chip)
VME (Virtual mode extension)
DE (Debugging extension)
PSE (Page size extension)
TSC (Time stamp counter)
MSR (Model specific registers)
PAE (Physical address extension)
MCE (Machine check exception)
CX8 (CMPXCHG8 instruction supported)
APIC (On-chip APIC hardware supported)
SEP (Fast system call)
MTRR (Memory type range registers)
PGE (Page global enable)
MCA (Machine check architecture)
CMOV (Conditional move instruction supported)
PAT (Page attribute table)
PSE-36 (36-bit page size extension)
CLFSH (CLFLUSH instruction supported)
DS (Debug store)
ACPI (ACPI supported)
MMX (MMX technology supported)
FXSR (Fast floating-point save and restore)
SSE (Streaming SIMD extensions)
SSE2 (Streaming SIMD extensions 2)
SS (Self-snoop)
HTT (Hyper-threading technology)
TM (Thermal monitor supported)
PBE (Pending break enabled)
Version: Intel(R) Celeron(R)
Voltage: 1.3 V
External Clock: 133 MHz
Max Speed: 3733 MHz
Current Speed: 2533 MHz
Status: Populated, Enabled
Upgrade: ZIF Socket
L1 Cache Handle: 0x0008
L2 Cache Handle: 0x0009
L3 Cache Handle: 0x000A


root@(none):~ $ lspci -mn
00:00.0 "0600" "1039" "0661" -r11 "1043" "8113"
00:01.0 "0604" "1039" "0003" "" ""
00:02.0 "0601" "1039" "0963" -r25 "" ""
00:02.1 "0c05" "1039" "0016" "" ""
00:02.5 "0101" "1039" "5513" -p8a "1043" "8087"
00:02.7 "0401" "1039" "7012" -ra0 "1043" "810d"
00:03.0 "0c03" "1039" "7001" -r0f -p10 "1043" "8087"
00:03.1 "0c03" "1039" "7001" -r0f -p10 "1043" "8087"
00:03.3 "0c03" "1039" "7002" -p20 "1043" "8087"
00:09.0 "0200" "10ec" "8139" -r10 "10ec" "8139"
01:00.0 "0300" "10de" "0322" -ra1 "" ""

root@(none):~ $ lsusb

Bus 003 Device 001: ID 0000:0000
Bus 002 Device 001: ID 0000:0000
Bus 001 Device 001: ID 0000:0000

Pablo
Site Admin
Posts: 4182
Joined: Tue Dec 14, 2004 2:13 am
Location: La Jolla
Contact:

Post by Pablo » Mon Sep 10, 2007 4:00 pm

Thank you for the information.

Could you post the output of 'lspci -mn' with the onboard ethernet and video enabled? I would like to make sure that I include those drivers as well.
MiniMyth running on an Acer ApireRevo 3610 and a Zotac ZBOX-ID80-U. Find out more at my MythTV page.

kingmoffa
Member
Posts: 39
Joined: Wed Sep 05, 2007 9:35 pm

Post by kingmoffa » Mon Sep 10, 2007 5:39 pm

Hi ,

The machine is stashed away and access if difficult , so its a chore removing the extra network and video cards. Onboard video and network are disabled currently. The network may just be a bios setting, so that wont be much grief. Video however will prob involve physical access.

The board nic is flaky and I'm using an nvidia fx5200 for the video. The additional nic is a 3com one, and has worked in a prev minimyth install - so Im not anticipating any probs with either.

However, if you want to improve things for other people - when I get some spare time I will report the needed information.

THanks for your help Pablo.

kingmoffa
Member
Posts: 39
Joined: Wed Sep 05, 2007 9:35 pm

Post by kingmoffa » Tue Sep 11, 2007 12:10 pm

Luckily the onboard video and lan , both have settings in the bios to enable/disable.

With both onboard video and lan enabled (but with nvidia video and 3com lan plugged in) here is the output:

root@(none):~ $ lspci -mn
00:00.0 "0600" "1039" "0661" -r11 "1043" "8113"
00:01.0 "0604" "1039" "0003" "" ""
00:02.0 "0601" "1039" "0963" -r25 "" ""
00:02.1 "0c05" "1039" "0016" "" ""
00:02.5 "0101" "1039" "5513" -p8a "1043" "8087"
00:02.7 "0401" "1039" "7012" -ra0 "1043" "810d"
00:03.0 "0c03" "1039" "7001" -r0f -p10 "1043" "8087"
00:03.1 "0c03" "1039" "7001" -r0f -p10 "1043" "8087"
00:03.3 "0c03" "1039" "7002" -p20 "1043" "8087"
00:04.0 "0200" "1039" "0900" -r91 "1043" "80ff"
00:09.0 "0200" "10ec" "8139" -r10 "10ec" "8139"
01:00.0 "0300" "10de" "0322" -ra1 "" ""


Pablo, please let me know once you have made the change needed for the sis5513 ide module to be created in the build process.

SmittyHalibut
New Member
Posts: 8
Joined: Sun Aug 29, 2004 10:38 pm

ETA on a new Kernel?

Post by SmittyHalibut » Mon Sep 17, 2007 12:45 am

I'm having this exact same problem with a very similar motherboard (Asus P4S333, the slower version of the one posted here; same SiS chipset regardless) and would love to know when to expect a patched kernel. Just an order of magnitude. Are we talking days, weeks or months?

Thank you very much for your work, Pablo. MiniMyth pretty much rules and is exactly what I need for a diskless Myth front-end by the TV. I really appreciate all the effort that goes into it. Keep up the good work!

-Mark

SmittyHalibut
New Member
Posts: 8
Joined: Sun Aug 29, 2004 10:38 pm

kernel config file

Post by SmittyHalibut » Mon Sep 17, 2007 12:49 am

Or, better yet, can you supply the kernel config file that I could use to compile my own kernel? I haven't dug into the build system to see if its in there.

I'll try just building a minimalistic kernel for my hardware and see if that works, but I'm not sure what else Myth relies on in the kernel. I guess I'll find out! :)

Thanks again.

-Mark

SmittyHalibut
New Member
Posts: 8
Joined: Sun Aug 29, 2004 10:38 pm

Found kernel .config

Post by SmittyHalibut » Mon Sep 17, 2007 7:30 am

I dug around in the gar source code and found the kernel files. There were a few patch files I applied and a .configure for my architecture. After applying all these files, I did a "make menuconfig" and added support for my IDE chip, and built the kernel. The hard part was unpacking the squashfs root bundle and applying the kernel modules. But I got that part figured out too and it's booting quite happily now!

...now to just figure out what kind of audio I have...

kingmoffa
Member
Posts: 39
Joined: Wed Sep 05, 2007 9:35 pm

Post by kingmoffa » Mon Sep 17, 2007 9:05 am

Hi there ,

Please could you explain in a bit more details what you did. I have a minimyth build system up and running and have managed (i think) to build a default setup successfully.

In the /script directory I have 4 kernel folders and am wondering in which one the (the newest?) I would have to run make menuconfig in.

Upon doing this, did you re-run the build process?

Also I have no idea how to unpack the squashfs and add the new module. Please could you help?

Thanks in advance.

SmittyHalibut
New Member
Posts: 8
Joined: Sun Aug 29, 2004 10:38 pm

Post by SmittyHalibut » Mon Sep 17, 2007 4:13 pm

I didn't provide details because I still haven't gotten the whole system working yet, and I think it's because of the changes I've made.

My changes were not made using the MiniMyth build system. I attempted to just rebuild the kernel on my own instead of rebuilding the whole darn thing, and I think that's what's killing me. First I'll tell you what I did (and what's currently not working), then I'll tell you what I suspect would work using the whole MiniMyth build system.

What I did:
The version of MiniMyth I'm using (0.20.2-3) uses a 2.6.21.7 kernel, so I downloaded the kernel source from ftp.kernel.org. I tried configuring a kernel myself, but quickly gave that up. Instead I downloaded the GAR system for MiniMyth to hunt down the patch files and .config for the kernel. In the GAR bundle are 4 different kernel directories. I just grabbed the files out of the 2.6.21.7 directory.

There are a few .patch files that need to be applied:
cd [kernel directory]
patch -p1 < [patch file]
patch -p1 < [next patch file]
...

Then I had to pick the .config file for my architecture. I used the i386-mmx file because my hardware is a beige box, not a VIA or C3 or whatever. (Specifically, it's a P4 1.8GHz, Asus P4S333 motherboard with a SiS chipset, which is afterall the whole problem here. :) Just copy that config file to [kernel directory]/.config

That'll start your kernel configuration out with where MiniMyth is. From there, you make a change to the kernel config by typing "make menuconfig" Here, you should probably know a little bit about compiling kernels. But, as a starting point, go into the "Device drivers" section, then "ATA/ATAPI/MFM/RLL support" Go down to the "SiS5513 chipset support" line and hit space until you see "<M>" on the left. This will compile the SiS5513 driver as a module.

This is what I think killed me for later. Since I know my system is a P4, I also updated the optimization architecture for Pentium 4. This changes a number of other things that I think is breaking some other modules being loaded. Don't do this. :)

Then select Exit by hitting Tab, Enter. Do this until you're out of the kernel configuration tool. Make sure to save your changes. Now, you build the kernel by typing "make" Depending on your hardware, this may take a while. (My first kernel compile back in 1993 took almost 36 hours. These days, they typically take just a couple minutes.)

Anyway. I copied the new kernel from [kernel directory]/arch/i386/boot/bzImage to the root directory of the flash drive I'm installing all this on. I called my kernel "kernel00.mts" (MTS are my initials) Since we're on a FAT filesystem, we're stuck with 8.3 filenames. I don't know how you're doing your boot, so you're kinda on your own here.

Then, you install the modules. This is the hard part.

First, you need to unpack the existing rootfs file: Make a temporary mount point, mount the squashfs file there, copy everything out of it into a new working directory that's read/write, make your changes, then bundle a new rootfs file. To summarize:
mkdir mnt
mount -o loop -t squashfs rootfs mnt
cp -r mnt root-mts # Again, MTS are my initials.
umount mnt
pushd [kernel directory]
export INSTALL_MOD_PATH=[full path to root-mts]/rootfs-ro
make modules_install
popd
mksquashfs root-mts rootfs00.mts

Now, copy rootfs00.mts to the same directory you just copied your new kernel00.mts.

Next, we need to tell the boot system to use the new files. Edit syslinux.cfg and make it look like this now:

----- snip! -----
LABEL minimyth-ram-mts00
KERNEL kernel00.mts
APPEND ro root=/dev/ram0 initrd=rootfs00.mts ramdisk=64000
----- snip! -----

Note the changes to the "KERNEL" line and the "initrd=" parameter. If you still only have this one group, you can leave the LABEL the same, but I added multiple groups, so the LABEL had to change.

Anyway. Once you copy the kernel and rootfs onto the boot source and change the syslinux.cfg file, you should be ready to go.


What will hopefully work for you:
I'm totally unfamiliar with the GAR process so I'm not sure where the best place to do this is, but you just need to make the change to the kernel .configure file. You might be able to do what I described above with the kernel configuration then grab the .config file and drop it in place over the one distributed with GAR, then have it go through the whole rebuild process. I'd be very interested to see if this works. It'll handle all the squashfs stuff for you, and probably will even rebuild the other kernel modules that I had troubles with (which I left out of my discussion above. I actually went through many rounds of the above procedure trying to get things working. I believe what I described above is a good summary of what will hopefully work, when I get a chance. I ran out of time last night.)

Anyway. This was very long and rambling. For this, I apologize. Hopefully it'll get you on the right track. Enjoy.

And again, thank you very much Pablo for all your work on getthing this thing as cool as it is. :)

Post Reply