You might wonder how it went with the Linux install on my G5. Please read the previous post on this if you are one of my new readers!
It turned out that the Debian installer still couldn't figure out where to install itself, even when the free space ready for Linux was first on the disk. There is certainly something strange with the partition scheme from Apple. As a last resort I went to gentoo. What you can't do with gentoo, I guess you can't do at all. To make the story short, gentoo works as a charm. During my tests with the other distributions, I figured out how to create partitions and mount them using mac-fdisk, mkfs and mount directly. The problem was that even when I mounted partitions, the installer couldn't find them. And if I got beyond that point, I still wasn't abel to install the bootloader properly. With gentoo, everything is manual and up to me, so it was much more easy to perform the install.
The only problem I really had was with yaboot configuration. The yabootconfig script that should have created a yaboot.conf file was nonfunctional with my setup, so I had to write the config manually, based on some examples I found online. That wasn't that hard, but it took me some time to figure out the ofpath id's I needed to put in there, as well as which partition number the Tiger actually should boot from. It turned out that I should not specify the partition where the Tiger lives, but the one just infront of it.
So - end of the story is that I now have a working Tiger and a working gentoo, though it will still take some time to get all the software I need on gentoo. That's why I don't like gentoo that much. The power of the gentoo install, coupled with the power of apt-get/dpkg, that's really what I want. But I guess I stick with gentoo for now - it will certainly give me a lean, mean machine!
A short note on the Shuttle SN25P case is also appropriate here. I can tweak the ubuntu really to what I want. I got NIS and automount working, I have sound and DVD burning working, and most of the packages I want. Actually, I just think about it as Debian, and it works quite fine. Guess I can live with that!
Take care!
Sunday, October 30, 2005
Wednesday, October 26, 2005
Linux on a G5 PowerMac
I finally wanted to put linux on my G5 PowerMac, as I see my main linux computer today, a laptop, soon will be gone, replaced with a smaller and sweater laptop (the Fujitsu Siemens P1510). As I now have the Shuttle SN25P at the office, I'll also need a stationary computer at home running Linux. Don't get me wrong, the Mac OS X system is a decent system. Unfortunately, it's not up to my standards for doing real work.
This should be an easy task, right. I already have a free external firewire disk, and my intention was to load Linux on that one. Inserted the ubuntu cd (read the story on the Shuttle to get why I just started out with ubuntu), and keep going. Right. Tap, tap, tap, enter, enter, enter, ooopss. I accidentally erased the MacOSX partition instead of repartitioning the external drive. So, thats an extreme makeover for my MacOSX installation. Anyway, most important stuff I have elsewhere, so no big deal. So, took two steps back, installed Tiger on the internal drive, and went back to my original quest. Installation on the external drive went just fine, up to the point where the bootloader, yaboot, is to be installed. It can't be installed on the external firewire drive, at least not from the ubuntu installer. Another couple of steps back.
Next try, go for a split of the internal system. So, I install Tiger again on a smaller partition, leaving a spaceious 80GB towards the end of the drive for Linux. Bahh.. The ubuntu installers is unable to find the free partition and install there. So, I figured out I should start with partitioning from the linux side. So I did - removed the Tiger again, created partitions for Linux at the end of the disk, installed ubuntu. Only to discover that the mac disk utility is unable to create HFS+ partition in the free space for Tiger. I lost counting, but had to destroy everything once more.
This time I did some googling, especially on the Debian installer documentation for PPC. There I got the following recipe: Start with installation of MacOSX, leave free space for Debian at the beginning of the disk. Then, install MacOSX, and finally install Debian.
So, now I will try that and see how it goes. Btw, the one time I actually got ubuntu installed on the internal drive (alone, no MacOSX present) I was unable to boot it, because the SATA drivers was not loaded in the kernel at boottime. I guess I need to use initrd or something, but have to figure that out later on.
On to the next install, I'll see you all later :-)
This should be an easy task, right. I already have a free external firewire disk, and my intention was to load Linux on that one. Inserted the ubuntu cd (read the story on the Shuttle to get why I just started out with ubuntu), and keep going. Right. Tap, tap, tap, enter, enter, enter, ooopss. I accidentally erased the MacOSX partition instead of repartitioning the external drive. So, thats an extreme makeover for my MacOSX installation. Anyway, most important stuff I have elsewhere, so no big deal. So, took two steps back, installed Tiger on the internal drive, and went back to my original quest. Installation on the external drive went just fine, up to the point where the bootloader, yaboot, is to be installed. It can't be installed on the external firewire drive, at least not from the ubuntu installer. Another couple of steps back.
Next try, go for a split of the internal system. So, I install Tiger again on a smaller partition, leaving a spaceious 80GB towards the end of the drive for Linux. Bahh.. The ubuntu installers is unable to find the free partition and install there. So, I figured out I should start with partitioning from the linux side. So I did - removed the Tiger again, created partitions for Linux at the end of the disk, installed ubuntu. Only to discover that the mac disk utility is unable to create HFS+ partition in the free space for Tiger. I lost counting, but had to destroy everything once more.
This time I did some googling, especially on the Debian installer documentation for PPC. There I got the following recipe: Start with installation of MacOSX, leave free space for Debian at the beginning of the disk. Then, install MacOSX, and finally install Debian.
So, now I will try that and see how it goes. Btw, the one time I actually got ubuntu installed on the internal drive (alone, no MacOSX present) I was unable to boot it, because the SATA drivers was not loaded in the kernel at boottime. I guess I need to use initrd or something, but have to figure that out later on.
On to the next install, I'll see you all later :-)
Monday, October 24, 2005
Linux on Shuttle SN25P
Hi there,
I got my new Shuttle SN25P at work today, and want to load it with linux. The computer comes equipped with a AMD 3500+ 2.2GHz processor, 2GB of memory and a 250GB maxtor SATA disk from the pc-pusher. They have also put an Geforce 6600 something graphics adapter into it.
As a long-time Debian fan, I of course wanted to load it with that. Of course, I know of the, should we say, not so appealing situation with Debian and AMD64, but thought I'll be fine with the glitches that might appear, and eventually some manual work. Now, I found a unofficial sarge netinst image for AMD64, as well as a testing or sid netinst image. To start out easy, I head for sarge. Everything seems fine during the install process, but after a reboot I discovered that the included kernel was not able to properly detect the ethernet card included on the mainboard as part of the nForce4 chipset. Not very usefull with a netinstall image then. So, the sid-image next (it was labeled as sid, but from what I could see during install it's more like a etch image). This time the ethernet card was detected properly, but the installer was heavily broken. For instance, busybox was missing in the target system during installation of package, such that unpacking and installation of packages was impossible. After spending a good hour, trying to put in the necessary stuff from the host (boot) system, I just figured out that this was not the "right way".
To make the long story short - I grabbed the latest ubuntu for AMD64, slipped it in, booted, waited, and had a working system.
While I kind of want Debian where I know all the tricks of the trade, I guess I'll stick with ubuntu for a while, at least until Debian can get something supported out there for AMD64. Hopefully, the unstable also will be useable at that time - as I use unstable on all my x86-32 computers. I'm happy to do the upgrade from stable to unstable on anything, but it is important that I can get a working install at least with network and a compiler, possibly some X11, but that's not significant to get started.
Tomorrow I have to see if I can get the ubuntu install to be something like how I want it, I guess I can. But there are some stuff to sort out still, like sound support. So there will probably be a followup on this.
take care,
I got my new Shuttle SN25P at work today, and want to load it with linux. The computer comes equipped with a AMD 3500+ 2.2GHz processor, 2GB of memory and a 250GB maxtor SATA disk from the pc-pusher. They have also put an Geforce 6600 something graphics adapter into it.
As a long-time Debian fan, I of course wanted to load it with that. Of course, I know of the, should we say, not so appealing situation with Debian and AMD64, but thought I'll be fine with the glitches that might appear, and eventually some manual work. Now, I found a unofficial sarge netinst image for AMD64, as well as a testing or sid netinst image. To start out easy, I head for sarge. Everything seems fine during the install process, but after a reboot I discovered that the included kernel was not able to properly detect the ethernet card included on the mainboard as part of the nForce4 chipset. Not very usefull with a netinstall image then. So, the sid-image next (it was labeled as sid, but from what I could see during install it's more like a etch image). This time the ethernet card was detected properly, but the installer was heavily broken. For instance, busybox was missing in the target system during installation of package, such that unpacking and installation of packages was impossible. After spending a good hour, trying to put in the necessary stuff from the host (boot) system, I just figured out that this was not the "right way".
To make the long story short - I grabbed the latest ubuntu for AMD64, slipped it in, booted, waited, and had a working system.
While I kind of want Debian where I know all the tricks of the trade, I guess I'll stick with ubuntu for a while, at least until Debian can get something supported out there for AMD64. Hopefully, the unstable also will be useable at that time - as I use unstable on all my x86-32 computers. I'm happy to do the upgrade from stable to unstable on anything, but it is important that I can get a working install at least with network and a compiler, possibly some X11, but that's not significant to get started.
Tomorrow I have to see if I can get the ubuntu install to be something like how I want it, I guess I can. But there are some stuff to sort out still, like sound support. So there will probably be a followup on this.
take care,
Subscribe to:
Posts (Atom)