Hi all.
Where i can download tutorial and necessary files for install ubuntu 9.04 in pegasos2
Regards

A rough guide is somewhere in my "Sent" folder, I have yet to find it... Two files are available at: http://genesi.hu/ubuntu/ where "pegcdinst904" is to boot the install CD and "pegboot904" is to boot the installed system.

_________________
CzP
http://czanik.blogs.balabit.com/

Thx for the reply,Peter.
I hope you find the guide....
Regards
Jose

OK. Here it is. Actually cut from three different e-mails, which reflected a work in progress, so a bit confusing, but still I hope it helps...

Disclaimer: it was a long long time ago in the galaxy and I did not touch Ubuntu ever since on PPC...

http://cdimage.ubuntu.com/ports/release ... owerpc.iso

I'm just booting the desktop CD. It's a live filesystem, after 10
minutes it is still loading. OK, got it complaining about "low graphics
mode" after ~15 minutes. OK, installer started on the
live system. I formatted a partition with
"mke2fs -I 128 /dev/sdaX" to have a properly formatted partition for the
new installation. I copied the installer to a firmware readable
partition, which is /dev/sda1 in case you left the original partitioning
of the machine (the "genesi" partition). Then booted the installer with
the following command from the firmware:
boot hd:0 pegcdinst904 file=/cdrom/preseed/ubuntu.seed boot=casper
After accepting "low graphics mode" I started the installer from the
desktop. I choose "specify paritions manually (advanced)" and selected
the previously formatted partition as "/" without formatting it. Ooops,
according to the summary screen it formats the partition anyway :-( So
the boot kernel needs to go to another partition, most likely next to
the installer.
Installation finished successfully, I choose 'reboot' at the end. I also
created a boot kernel, both of these files are now available at
http://genesi.hu/ubuntu/ pegcdinst904 and pegboot904. These should be
downloaded to a firmware readable partition (or loaded by tftp). Then
instruction from my previous e-mail followed. The installed system can
be booted from the firmware prompt by:
boot hd:0 pegboot904 root=/dev/sda5
Assuming, that pegboot904 is in the root of /dev/sda1 and the system was
installed to /dev/sda5

_________________
CzP
http://czanik.blogs.balabit.com/

Thx Peter.
This night probe to install...
First is necesary make a linux partition in my hd from morphos?
Example:
i have little partition in the first FFS i have the boot.img from morphos and amigaboot.of for amigaos4.1

in the second partition have a linux partition make from morphos with "0x4c4e5800" custom filesystem

in the rest of partitions i have sfs filesystem for morphos and amigaos.
i have another 120gb hd in the second ide of pegasos2. can be used this second hd only for diferent linux distros and MOLK?

with the ubuntu-9.04-desktop-powerpc.iso in the cdrom i type this?

boot /pci/ide/cdrom install/pegasos
wait you news.....
What is the better linux distro for pegasos2 G4 with radeon 9000pro?
very thx for your help
Jose

The 120GB HDD should be fine. You should partition your second HDD from MorphOS and create a small ext2 partition to store your kernels. FFS is fine for booting, but no Linux can use it out of box, so you could not upgrade your kernel there...

"install/pegasos" does not work, the referred boot kernel is not there :-(

Best Linux distro for the Pegasos2: difficult question. The latest Ubuntu and openSUSE are quite slow on the machine. openSUSE 11.0 is probably the best still supported release. Earlier Ubuntu releases were also faster, but there are no security updates any more. I did not check recently, but the latest Debian should be most likely fast and still supported, at the price of not being so convenient to use, as Ubuntu or openSUSE.

_________________
CzP
http://czanik.blogs.balabit.com/

Hi again Peter.
I install 9.04 with your tips (low graphics mode in the install process).
When i reboot ....boot hd:0 pegboot904 root=/dev/sda2 the system only work in low mode.
How can change this?
My gfx is a radeon 9000pro
Regards

Sorry, but no idea. Partition already overwritten with openSUSE...

_________________
CzP
http://czanik.blogs.balabit.com/

if pegboot904 has radeonfb builtin try declaring your resolution:

_________________
acrux _at_ linuxmail _dot_ org

You shouldn't even need to declare the resolution, just let radeonfb find the best screen mode from the monitor using EDID.

_________________
Matt Sealey

Hi,

My card is an ATI Radeon 9200SE, and I solved the problem by changing the xorg.conf.

after installing Ubuntu 9.04 I upgraded to Ubuntu 9.10, and it works, slowly, but works !

here is my xorg.conf:

------------
Section "Files"
FontPath "/usr/share/X11/fonts/misc"
FontPath "/usr/share/X11/fonts/cyrillic"
FontPath "/usr/share/X11/fonts/100dpi/:unscaled"
FontPath "/usr/share/X11/fonts/75dpi/:unscaled"
FontPath "/usr/share/X11/fonts/Type1"
FontPath "/usr/share/X11/fonts/CID"
FontPath "/usr/share/X11/fonts/100dpi"
FontPath "/usr/share/X11/fonts/75dpi"
# paths to defoma fonts
FontPath "/var/lib/defoma/x-ttcidfont-conf.d/dirs/TrueType"
FontPath "/var/lib/defoma/x-ttcidfont-conf.d/dirs/CID"
EndSection

Section "Module"
Load "GLcore"
Load "i2c"
Load "bitmap"
Load "ddc"
Load "dri"
Load "extmod"
Load "freetype"
Load "glx"
Load "int10"
Load "type1"
Load "vbe"
EndSection

Section "Device"
Identifier "ATI Technologies, Inc. Radeon 9200 (RV280)"
Driver "radeon"
Option "BusType" "PCI"
# BusID "PCI:1:8:0"
# Option "UseFBDev" "true"
EndSection

Section "Monitor"
Identifier "Configured Monitor"
EndSection

Section "Screen"
Identifier "Default Screen"
Monitor "Configured Monitor"
Device "Configured Video Device"
EndSection

Section "DRI"
Mode 0666
EndSection

--------------------

I meet several issues with Jaunty Jackalope on my Pegasos 2 / ATI Radeon 9250.

1. X11 server "low-graphics" mode starting issue
The X11 server failed to start because of an invalid format for "BusId" parameters recovered from my Hardy Heron install.
To solve the problem, I had to replace "PCI:1:8:0" by "PCI:1@1:8:0".

But now, even if the X11 server starts correctly, a glxgears test gives a very low 65 fps result whereas it gives 510 fps with Hardy Heron.

Accorgind this page, it is a known problem with PowerPC :
https://wiki.ubuntu.com/PowerPCKnownIss ... 0Jackalope

2. Boot process is too long (~ 10 minutes)
During process boot, there are two issues which take too much time :

First issue, after HD and CD readers detection, just before the script "local-premount" was launched :
...
[ 5.268623] Uniform CD-ROM driver Revision: 3.20
[ 5.270691] sr 1:0:0:0: Attached scsi CD-ROM sr0
[ 5.272886] microsoft 0003:045E:00F9.0003: input,hidraw2: USB HID v1.11 Mouse [Microsft Microsoft Wireless Desktop Receiver 3.1] on usb-0000:00:0c.3-2/input1
[ 5.292762] sr1: scsi3-mmc drive: 20x/48x cd/rw xa/form2 cdda tray
[ 5.295008] sr 1:0:1:0: Attached scsi CD-ROM sr1
[ 190.456248] EXT3-fs: INFO: recovery required on readonly filesystem.
[ 190.458158] EXT3-fs: write access will be enabled during recovery.
[ 190.537415] kjournald starting. Commit interval 5 seconds
[ 190.539327] EXT3-fs: recovery complete.
[ 190.541480] EXT3-fs: mounted filesystem with ordered data mode.
[ 195.045792] udev: starting version 141
[ 195.433259] irda_init()
...

Second issue, after the hardware detection, just before the loading of kernel modules :
...
[ 195.753266] parport_pc: VIA parallel port: io=0x3BC, irq=7
[ 197.458720] ppdev: user-space parallel port driver
[ 197.870955] VIA 82xx Modem 0000:00:0c.6: enabling device (0000 -> 0001)
[ 199.128689] VIA 82xx Modem: probe of 0000:00:0c.6 failed with error -13
[ 199.132067] VIA 82xx Audio 0000:00:0c.5: enabling device (0000 -> 0001)
[ 376.299918] Adding 1040312k swap on /dev/sda10. Priority:-1 extents:1 across:1040312k
[ 376.356785] Adding 540532k swap on /dev/sdb8. Priority:-2 extents:1 across:540532k
[ 376.883275] EXT3 FS on sda11, internal journal
[ 474.645009] kjournald starting. Commit interval 5 seconds
[ 474.645238] EXT3 FS on sda12, internal journal

Do you have the same behavior on your Pegasos ?

Does the Option "BusType" "PCI" fix do anything to help, as well as the right bus ID? You would need both..

I wonder if anything gets better in Karmic Koala here. IIRC Jaunty came out right between the libpciaccess rework in X.org so it was bound to have weird problems (and nobody at Canonical tested it on a system where graphics was not in the first PCI domain).
What's the problem here? The modem probe failure is normal. As for the partition things... you really have 12 partitions? What are sda10, 11 and 12 and what is sdb8?

_________________
Matt Sealey

PCI for BusType is set for both Hardy and Jaunty.
According a link in known bugs page, the problem is solved with kernel 2.6.29.-3.
In boot logs say :
[ 199.132067] VIA 82xx Audio 0000:00:0c.5: enabling device (0000 -> 0001)

And severals minutes later :
Loading kernel modules

It's too long regarding Hardy starting process.

Try using the via82cxxx driver instead of pata_via, or the other way around?

_________________
Matt Sealey