So, I grabbed an ASUS A7N8X-VM after reading a few success stories on this board and tried my luck again (you may not know that I had problems earlier with an old HP).

Still no luck.

So besides the aforementioned board, I added a Micro ATX power supply, Athlon 2200 XP processor, 256 M of 2700 DDR RAM, 30 GB IDE hard drive, a CR-RW drive (from my HP) and a PVR-250 card.

When R4v2 comes up it enters:

Autoconfiguring devices... (ASCII progress bar)

Then it comes up:

Oops:0002
serial usb-ohci: usbcore apm rtc cloop
:
: {bunch of Hex and such}
:
Segmentation Fault
Please check.
Soundcard driver ALSA Autodetect {etc.}

(other details missing because because I was trying to write this down)

It soon comes up to the main install screen, but an ASCII progress bar is always marching on endlessly. I try to do Auto Install and it soon fails....

My copy of R4v2 appears to be good. I use a Mac (which should explain a lot, I have never confugured or built a PC before). Mac OS X's Disk Utility will generate MD5 checksums for disk images and disks — it gives different checksums than have been supplied with the .iso of R4v2, but it is internally consistent — that is, I downloaded the disk image a second time and got the same MD5 (and the CD's I've bruned too share the same MD5 checksum).

I've left the jumpers and BIOS to basically factory settings. Curiously, twice I've had the board power up and tell me the CMOS checksum was bad — whatever that means — BIOS? In any event, I've reset to factory settings and continued).

I played around with R4 as well with different results — although it still failed. I believe there was a Kernel panic during the Copying Files stage or perhaps and installer crash, I didn't write it down and decided it was a lost cause to try to get an older version of KnoppMyth going.

Any ideas? I mentioned being new to all of this (PC's, BIOS, Knoppix, MythTV, etc.). I know a few people on the forum have similar hardware set-ups, perhaps they flashed the BIOS or somesuch thing that seemed obvious to them but not to a new-comer.

john calhoun–

if you are getting a different MD5SUM than the one I provide, you have a coaster. If you are getting cloop errors during the install you have a coaster. Download again and verify the MD5SUM matchs what I provided, try burning at a lower speed.

_________________
cesman

When the source is open, the possibilities are endless!

I'm about to write a tier 1 report of my ASUS A7N8X-VM/400 install. I was inspired by Elliott's very useful report and I think v4r2 moves the A7N8X to tier 1.

I did several "test" installs with v4 while waiting for my WinTV 401 to arrive and everything repeatedly went smooth several times but then it started getting weird. I had been less than careful with my v4 CD while using my living room floor as a workbench, I burned a new v4 CD and problems went away.

With v4r2 (my 3rd KnoppMyth CD) the A7N8X-VM/400, 256MB, 2200+ Athlon XP, WinTV 401, PVR-250 install has been easy and smooth.

If your checksums aren't matching, re-download and re-burn. A bad CD really can take away the fun!

One little A7N8X tip: I was pulling my hair out getting TV Out working until I realized that the BIOS's default for TV Out is PAL. I changed the TV Out to NTSC (under chipset settings in bios settings) and things suddenly just worked! (Just needed option "ConnectedMonitor" "TV" once I was ready to switch off the VGA monitor I was using for set-up)

Cesman,

Can you point me towards how to get an MD5SUM off of the CD I've burned? I'll be happy to share it with John to insure that what I've downloaded and been sucessfull with does or doesn't match what he has and what you say it should be.

Don

[quote="MythDon"Can you point me towards how to get an MD5SUM off of the CD I've burned? [/quote]
You should check the md5sum before burning the CD.
md5sum KnoppMythver.iso
md5sum /mnt/cdrom may work, but I've never tried it...

_________________
cesman

When the source is open, the possibilities are endless!

Re: MD5 checksums....

I wonder if anyone else with a Mac can point to a utility or command-line-tool that gives matching MD5 checksums. As I pointed out, I've used Disk Utility (part of OS X) and it gives different MD5's from the posted numbers (apparently). That strikes me as a bit odd, but I'm willing to accept that the implementation is different.

I will, BTW, try a second burn off a second .iso image and post my results, but as the checksum with Disk Utility was at least "internally" consistent, I sort of have my doubts this will be the problem....

Thanks so far for the suggestions.

...Also, I'm in the process now of building a suite of Redhat install CD's to sort of see that the hardware set-up is legitimate.

john calhoun–

Note: I don't own an OSX machine (although I wish I did) but I am experienced with FreeBSD so maybe I'm not talking totally out of my rear

Since you're running OSX, which is a *nix variant, just pop a commandline and type "md5sum <file.iso>" Hopefully, they included the md5sum command and it's in your path. I'd imagine that they did since it's a pretty basic command.

Again, I could be totally wrong, but if I were a bettin' man, I'd take a bet that md5sum is somewhere on an OSX system.

Mike

No md5sum tool on OS X. I have developer tools installed as well, but — nada. Searched the drive, nope.

I have tried a second CD with the same errors. I have tried a known working CD (borrowed from a friend who has sucessfully installed) and it fails as well....

So I'm going on to investigate the hardware.

FWIW, I did some brief checking around on the Web and noticed that sometimes PPC and i386 checksums are given (they are not the same). Might be confirmation of my suspicion that Mac OS X could give different (but nonetheless accurate) checksums from those posted. Likely an endian issue with the MD5 algorithm?

Well, onto hardware investiagtions....

john calhoun–

If anyone is interested, I think I can safely say (after three CD's now) that the correct MD5 checksum for R4v2 using Mac OS X's Disk Utility is:

$869FA9139F552533DB6BE0D234C20D6D

This on Panther (10.3) anyway (and likely earlier versions of the OS as well).

john calhoun—

The md5 diffs must be a little-endian vs. big-endian thing.

Mike

The endian theory is interesting but if MD5SUMs are endian-sensitive then I would think they'd lose any usefullness.

In any event, the MD5SUM of the r4v2 .iso that I downloaded from ftp.rdt1.org and used successfully is 53d876be70b878d4d3ca1e7e9388bb3e which matches the official MD5SUM.

Try downloading Knoppix and use it to test your hardware.

http://www.knopper.net/knoppix-mirrors/index-en.html

Have the BIOS checksum problems gone away?

To get a comparable md5sum in Panther (X 10.3) in a terminal session execute the command 'md5 filename' The output should be the same as the .md5sum file, with the content effectively reversed, (format of output is filename md5sum vs the .md5sum file being md5sum filename)

If the two numbers don't match, you have a bad .iso file.

As a temporary measure, I have posted the files to my web server as well, http://www.beresourceful.net/KnoppMyth/ I would request not hitting the server too hard. It is behind a cable modem, so upload speeds will not be particularly high. If you get a 'no longer available' message, I have pulled the page...

-Rusty

_________________
Master:
- AMD 1800XP on a MSI KT4V motherboard, via KT400 bios
- 120 G Segate Baracuda /, /cache, /myth, swap
- 200 G Segate Baracuda /myth/tv
- 3 Haupauge! WinTV PVR250s
- 19" Daewoo Monitor (1280x1024 ni)

My machine is working! To close up this thread:

I took my "set-up" (bunch of hardware taped to a board) into work. It failed as per usual, but someone asked about the memory.

I pointed out that I had tried it in both slots and just to show them, I moved the memory back to the original slot I had been trying.

The install went flawlessly this time. Perhaps the memory was not adequately seated? Inquiring minds don't want to jinx the set-up and so ... I'm no longer pondering it.

Having fun exploring the UI. Got MAME working (changed the permissions on the game settings file and played with the settings until it saw some MAME ROMs - played a few games ... my machine locked up though after ... coincidence?).

Thanks for the help.

john calhoun—