minimyth-0.2-jm with all modules

Announce/Discuss projects you are working on for MiniMyth

Moderator: Pablo

jmw
Member
Posts: 32
Joined: Thu Nov 13, 2003 4:39 am

it's the kernel

Post by jmw »

Hairlocks -

I tried a few more tests, and it turns out that the kernel-0.2-jm is what is causing my reboot loop.

I tried the stock 0.2 kernel with the rootfs-jm that i built, and it loaded (it didn't quite make it to opening mythfrontend, but that's to be expected). I also tried the kernel-0.2-jm with my stock 0.2 rootfs. It still had the reboot loop. Apparently it wasn't crashing while downloading the rootfs - it had actually finished doing that, and the instant after, it tried to open up the kernel, it crashes. So... what might be causing that?

Do i need to do anything to the kernel file before sticking it in my tftp directory?

Here's my default file, anyone see any problems here?
PROMPT 1
DEFAULT linux-ramdisk
DISPLAY messages
TIMEOUT 5
label linux-ramdisk

KERNEL kernel-0.2-jm
# don't use quotes on the append line
APPEND initrd=rootfs-jm ramdisk_blocksize=4096 ramdisk=75000 devfs=mount LIR
C=pctv MYTHSERVER=192.168.0.1 HWMPEG2=foo
jmw
Member
Posts: 32
Joined: Thu Nov 13, 2003 4:39 am

kernel

Post by jmw »

Hairlocks,

I am running on an ME6000. Is that what you have? If not, could that cause this problem? Whoever got this kernel to run, what hardware do you have?

I tried replacing my tftp server with one that the pxelinux website recommends. I tried downloading the kernel again to make sure it wasn't corrupted. Nothing has made any difference so far.

I am about out of ideas here. :(

jmw
Hairlocks
Contributor
Posts: 107
Joined: Wed Aug 27, 2003 12:23 pm
Location: Reading, UK
Contact:

Post by Hairlocks »

If it works with the normal minimyth-0.2 kernel I would use that for the moment. The only thing I have changed from that is the stuff for CD support in the SCSI drivers.
Hairlocks
Contributor
Posts: 107
Joined: Wed Aug 27, 2003 12:23 pm
Location: Reading, UK
Contact:

Post by Hairlocks »

The problem is probably cause by the compiler options, as I haven't altered them. I just assumed that the C3 will work with the PII option I suspect my compiler is using. Anyone remember want setting I ought to use for the pre Nehemiah chip?
jmw
Member
Posts: 32
Joined: Thu Nov 13, 2003 4:39 am

ah

Post by jmw »

OK, I didn't realize i could use the minimyth 0.2 kernel.

I did briefly try the 0.2 kernel - there was some error, but I didn't investigate it because i didn't know it had a chance of working. I'll look into that this evening. Thanks!

jmw
lmatter
Contributor
Posts: 632
Joined: Sat Aug 23, 2003 5:13 pm
Location: California, USA

Post by lmatter »

For compiling I generally use -march=i586. If it's a graphical program I'll add -mmmx. This should work on all EPIA M's.

Larry
jmw
Member
Posts: 32
Joined: Thu Nov 13, 2003 4:39 am

Post by jmw »

Hairlocks,
I tried booting up with the 0.2 kernel, and the rootfs I made by combining your usr and root files into one cramfs.

It gets to the screen where it's sort of a gray halftone pattern with a white dot in the middle (mouse pointer)? Where X is starting up right before you'd see the mythfronted GUI.

It crashes out of X with an error message saying it can't find the file
/usr/local/share/fvwm/ConfigFvwmDefaults

There is a file in that dir called ConfigFvwmDefaults.old, and i tried renaming it to ConfigFvwmDefaults in the cramfs. Booting again, it just died a bit later complaining about some of the options in that file. I have tried a few things to make fvwm work the same way it does as in the 0.2 release. No luck. The fvwm in your release seems to insist that all these config files are present, whereas the 0.2 doesn't care (and none of them are present). Both fvwm binaries and Xfree86 binaries are the same as the 0.2 release's (as i'm sure you know) so this baffles me. Any ideas on what to try next?

thanks!

jeff
dewpac
Member
Posts: 19
Joined: Thu Nov 13, 2003 9:39 pm

Post by dewpac »

jmw:

I had what I believe is the same problem you're seeing:

In that file, look around like 47-48..should look something like this IIRC:

Style * UseIconPosition, RightTitleRotatedCW, UseTitleDecorRotation
Style * EWMHPlacementUseDynamicWorkingArea, EWMHMaximizeUseDynamicWorkingArea

(just 2 lines if this board breaks it up wierd.

I changed mine to look like this:

Style * UseIconPosition
#, RightTitleRotatedCW, UseTitleDecorRotation
#Style * EWMHPlacementUseDynamicWorkingArea, EWMHMaximizeUseDynamicWorkingArea

(now 3 lines, commenting out the second 2 options that were on the first line, and commenting out the entirety of what was the second line.

I believe that is what solved it for me. Does this solve your issue?
jmw
Member
Posts: 32
Joined: Thu Nov 13, 2003 4:39 am

Post by jmw »

dewpac -

Thanks for the suggestion. Unfortunately, it doesn't work for me.

I get this:
-----------------------------
(==) Using config file: "/etc/X11/XF86Config"
VIAScreenInit : V4L Enabled : fd2 = 8
(WW) via(0): Failed to set up write-combining range (0xd8000000,0x2000000)
FillGraphicInfo!!
(EE) Create .VIAGAMMARC failure!
FillGraphicInfo!!
error opening security policy file /usr/X11R6/lib/X11/xserver/SecurityPolicy
Couldn't load XKB keymap, falling back to pre-XKB keymap
[FVWM][main]: <<WARNING>> X does not support current locale: C

Illegal instruction

waiting for X server to shut down
------------------------------

I take it you renamed that file, removing the ".old"? Did you do anything else?
Hairlocks
Contributor
Posts: 107
Joined: Wed Aug 27, 2003 12:23 pm
Location: Reading, UK
Contact:

Post by Hairlocks »

The first thing you could try is to remove fvwm2 from the /.xinitrc file, to see if it is really the application crashing X. You actually only need fvwm2 with MythDVD and MythVideo, everything else is fine without it. (is you don't have fvwm2 running, you can start mplayer to watch a film, it is just you have no control, like pause, stop, fast forward etc. unless you do it from a telnet session.)


There error log of my X startup ends with.

[FVWM][main]: <<WARNING>> X does not support current locale: C

irxevent: could not connect to socket
irxevent: No such file or directory
[FVWM][Read]: <<ERROR>> file '/usr/local/share/fvwm/ConfigFvwmDefaults' not found in //.fvwm or /usr/local/share/fvwm
Fontconfig error: Cannot load default config file
Qt: Locales not supported on X server

I ended up using /usr/local/fvwm/system.fvwm2rc as the configuration file and it seems to work for me.
jmw
Member
Posts: 32
Joined: Thu Nov 13, 2003 4:39 am

Post by jmw »

I tried removing fvwm from the .xinitrc. Unfortunately it *is* the application crashing X:

(==) Using config file: "/etc/X11/XF86Config"
VIAScreenInit : V4L Enabled : fd2 = 8
(WW) via(0): Failed to set up write-combining range (0xd8000000,0x2000000)
FillGraphicInfo!!
(EE) Create .VIAGAMMARC failure!
FillGraphicInfo!!
error opening security policy file /usr/X11R6/lib/X11/xserver/SecurityPolicy
Couldn't load XKB keymap, falling back to pre-XKB keymap
Illegal instruction

waiting for X server to shut down

Everything except the "illegal instruction" appears long before it crashes. So now i'm guessing that since the kernel and the app don't work, that maybe they were not built for the ME6000's architecture? (Am i correct in saying that the ME6000 is "ezra" and the higher M series are "nehemiah"?)
Hairlocks
Contributor
Posts: 107
Joined: Wed Aug 27, 2003 12:23 pm
Location: Reading, UK
Contact:

Post by Hairlocks »

I am a little confused as why mythfrontend doesn't even start as I didn
ldormon
New Member
Posts: 6
Joined: Mon Dec 29, 2003 11:08 pm
Location: London, England

Post by ldormon »

Err not going all AOL mode, but "Me too"

I seem to be having exactly the same probs as jmw, was there a fix? Or is it time to get down and dirty with it

Cheers
Lee

Ps Thats on a 933 by the way
Post Reply