I can post "Nothing new to report." in this thread every day if it will make you feel better.

At the moment there's no news because there is nothing new to report. Cecil is away for the week, we're still poking at the latest build he gave us before he left, and we're still waiting for somebody to come up with a real solution. It's just a hard problem.

Won't be a problem. The upgrade process doesn't really care about that kind of stuff. All it carries over are the media (and other) files in "/myth", the contents of the database, the contents of the home directories for the users, and a (very) few things in "/etc". Both of the last three things are extracted from the backup. Everything in other locations gets totally replaced.

I'm sure all of us that run home from work to see if it's ready, would appreciate any updates you can.

Of course, as always, we appreciate everything that you all do for this great project. We're eager to see all of the fixes and features discussed in this forum.

Some possible suggestions:

From Cecil's comments I understand that the problem is that Nvidia chipset
motherboards with both PATA and SATA can have what was hda come up
as sdb after the upgrade. I wouldn't be surprised if having an extra USB
thumb drive plugged in at boot could even move this down to sdc.

Apparently there is something else to the issue, else it would seem like
simply converting fstab to use UUID's would be a solution.

I expect that converting device references in the database (like where
the dvd drive is) is the another problem?

Perhaps the one time creation of a permanent list of old device names
from the old fstab and a new list of new device names on each boot of the
new system and writing a translate function to be used to get the new
name of the (e.g.) dvd.

I recall that there are ways to get udev to consistently use the same
device name on consecutive boots, but that discussion is in unfamiliar
territory for me.

Cliff

_________________
R5F27 using R5F1 Nvidia drivers
HD-5500 analog from NTSC Sat Rx, with OTA DVB too
GeForce MX-440 SVideo tvout to a TV
Older dual core 3.4ghz Intel CPU
Asus P5PE-VM Motherboard
2 GB RAM
1 TB LVM2
VirtualBox
Samba

Yep, an update occasionally will be great. Even "Cecil is out for the week" tells me to stop hitting refresh for awhile on the home page!

_________________
System Specs:
Intel P4 3.2Ghz; Intel mobo; nVid 7600gs AGP (512MB); SoundBlaster Audigy2 Sound; R5.5; PVR-500; HD Homerun; Vizio 42" LCD

I have a short bash script I wrote (GPL v3.0) which checks a web site to see if it's changed since the last run. If it's changed, it emails the specified address.

I've got it in my crontab, checking the announcements forum and the http://mysettopbox.tv home page every so often.

If anyone wants a copy, it's at http://fog.org/~douglask/webcheck.sh

Cheers,
Douglas

Then step up and help test. Search and search for anything related to the problem and help us fix it.

No one is more upset over this than I am. Since R5F27, I was hoping to get a release ready so it can be made public after 0.21 was released. Most everything was looking great until some testers stated they had issues w/ installing.

Actually, I had a build w/ 2.6.24 that didn't pass my QC so the testers didn't see it. Since 2.6.24 merged x86_32 and 64 the Debian utility the build the kernel omitted some items. While I was able to get pass the problem (or so I thought), I had issue build various modules. So, 2.6.24 was a no go. Thanks for sharing your experience!

have you tried just disabling libata?
Kernel Option:

Code:

hwprobe=-modules.pata

I know you (cecil) stated that you welcome us to step up and test, and help look for the answer, but can you provide (even privately) a copy of the new testing release for us to phsically test with? What is the proper proceedure for getting on the test team?

Please advise, and I would be glad to help if I can.

_________________
"If the facts don't fit the theory, change the facts"
--Albert Einstein

I was going to say the same thing. I am not a strong Knoppix guy, I run more towards Red Hat, but I run cloned hard drives and I would be happy to test (If I had access to the release)

_________________
System Specs:
Intel P4 3.2Ghz; Intel mobo; nVid 7600gs AGP (512MB); SoundBlaster Audigy2 Sound; R5.5; PVR-500; HD Homerun; Vizio 42" LCD

When I was having problems in the past, Cecil offered test releases to me in the IRC channel, so I would recommend checking there.

On a positive note, at least all of this SATA/PATA business will be solved now, and not be a distraction when R6 is being released!

I think I have this ironed out... Some more testing tonight and I'll get an ISO to the testers as soon as possible. As I was off last week, this week work work will have be busy catching up. So, stay tuned and thanks for your patiences.

Thanks for your tireless efforts. I have a number of Mythboxes running in the hands of 'non-experts' and no problems feeding back at all.... The current product is PRETTY DARN GOOD !!....

Almost there... I do believe the major issue has been addressed. The Testers have pointed out a few smaller ones (they still need to give me thumbs up on the major bug, but I'm confident it is been squashed)... Hopefully by this weekend, what the testers have will be solid (gold even ).

Thanks for the update

Wait...wha?!? I though you were going to work for Micro$oft?!?

Thanks for the update Cecil.

_________________
System Specs:
Intel P4 3.2Ghz; Intel mobo; nVid 7600gs AGP (512MB); SoundBlaster Audigy2 Sound; R5.5; PVR-500; HD Homerun; Vizio 42" LCD