daz wrote:You should be looking in the main Hyperion site not the beta test one.
I've only just found this out but I also only registered my machine recently so I didn't have much chance of seeing it there beforehand!
Not that I'm aware of. You really shouldn't need modules unless you have a very unusual hardware setup.
Well my system is not unusual AFAIK. I have a HD4890, a 1TB HD and BD drive inserted in the specified slots. A Mac keyboard in USB.
But I did some extra testing. It gets past loading GNOME and gdm on console, MTA and then NET. It then stops. I can actually switch consoles. But the desktop console is blank except for a cursor. On the other consoles I can't press enter to log in. Nor does the boot console work. However I can press reset combo to shut down kernel.
Might try booting installer image again and making sure the modules are latest from 39D.
Why did you do all that? The install guide uses the initrd without unpacking, and this works as it has been tested by Trevor
At the timeI the guide I had didn't have Ubuntu instructions. And I did it because the initrd from CD I downloaded failed. The kernel didn't understand an LZMA initramfs. When I repacked with GZip it worked. Well it loaded in any case. Then failed while booting. However this was using the standard 39 kernel.
I just found an updated guide. However it uses an Ubuntu net install initrd.gz from the internet. This is not standard on an Ubuntu desktop installer CD, nor console installer CD, as they both use a LZMA initrd without extension. Although not using an extension isn't exactly standard so don't know why that is. It does confuse a Linux desktop into not knowing it's an initrd and also LZMA itself which refuses to touch unless it's renamed properly.
So it looks like I was on the right track. As the install guide uses a GZipped initrd. Having said that, it's anet install. Which for me is unsuitable, as I'd have to stay up all night after 1AM, so it downloaded during my offpeak and my speed isn't great. However, it should detect a CD in the drive.
Also you need to forget all the boot instructions for the A1 THEY DO NOT APPLY HERE, you are booting an X1000.
Yes I know that. But I wasn;t talking about booting an A1, I was talking about the A1 kernels, which are based on the Debian kernels that off load a minimum set of modules into a boot initrd image that is needed to boot. So in essence my point was about how a modern kernel is usually constructed.
The A1 is mainstream in PPC linux, the X1000 is not, and therefore needs a custom kernel.
The A1 is mainstream? LOL!
Where did you get that idea? You can't exactly boot a Mac Linux CD on an A1! The A1 is the same as the X1000 and requires a custom kernel as well.
But I was suprised that Linux didn't work out of the box on the X1000 since it is robust new hardware that doesn't have the A1 hardware problems like no cache coherency AFAIK. Of course, Linux is made to boot on a Mac or an IBM RISC machine. They did support Pegasos (being OF based) but the files are broken. I just expected they'd replace the broken Pegasos files which is an old machine now and replace it with X1000 files for autoboot. Or at least add support. I don't know if anyone has requested support from Debian for example. I thought Varisys might have done so in the beginning.but board hasn't been out long.
Please try following the guide Trevor has written and see how far you get. It's worked for a number of other people and knowing where your system fails may help us sort your problems out.
As previously stated I had managed to install Debian months ago following an early install guide. But it can't get up to a desktop. I will read the latest guide to see if there is anytihng I have missed. Thanks.
