Linux MintPPC Forums • View topic

este.el.paz · Joined:Wed Jun 15, 2011 10:57 pm Posts:403 Location: SoCal

macjena wrote:

Hallo,

i downloaded mini.iso from

http://d-i.debian.org/daily-images/powe ... c/netboot/
<snip>
by the way.
The Links to download the mini.iso were wrong.

Thanks for help. I would be very happy to have MintPPc runing on my Mac.

Just to confirm, yes, the link to the mini.iso from the "installation instructions" gets a 404 error--"not found"

e.e.p.

OmeLuuk · Joined:Tue Feb 28, 2012 10:05 pm Posts:11

New here, got this old Mac G4 350 MHz with outdated 10.4. No good use. So found this initiative and superb support! DatdoejegoeJeroen

.

Now my story, with the mini.iso (4G) and install url=mintppc.org installation got stuck at 85%. Seemed to be busy with /boot and creating initrd. Numerous re-installations, with various different option sets.

So please do not ask me what brought me here, but finally I got MintPPC installed. Had to use expert url=mintppc.org and selected some extra install options. Well, today this worked reasonably at last.

There are these error messages at boot time, which are not (?) problematic [something with udevd timeout killing sbin/modprobe - b pci#, occurring some 14000 times at boot up].

But now I see this login screen and want to login, but my mouse and keyboard are dead.

So I had to add some mouse/keyboard information, but there is no xorg.conf file. Also MintPPC went to /usr/share/X11/xorg.conf.d/

So what is the correct conf file for this apple keyboard and mouse?

<edit> It is even worse. I suppose it is not the 50-*conf files that cause this issue, because booting with Linux1 does not even allow me to input my root passwd. Mouse light is off, capslock does not lit... probably USB driver fails to load?

Booting in rescue url=mintppc.org does allow me to boot in my root system, but fails to load X. That is why I suspected the 50-*conf files </edit>

OmeLuuk · Joined:Tue Feb 28, 2012 10:05 pm Posts:11

Technical Details:

Code:

This is a Debian installation netboot image, built on 200120217-00:07

Using co-boot with old 10.4 Mac installation.
Disk 0 has sda1=map sda2=bootstrap sda3=/ sda4=/usr sda5=/var sda6=swap sda7=/tmp sda8=/home
I saved the installation logs.
PowerMac 1088 Mb 350 MHz

WARNING Bootstrap partition type is wrong: Apple_HFS type should be Apple_Bootstrap
Logitec Apple Optical USB Mouse and Mitsumi Electric Apple Extended USB Keyboard both fail to be recognized (however in Xorg.log.0 /dev/input/event3 Mouseemu and /dev/input/event0 PMU are loaded).
Lots of (EE) R128(0): FBIOPUT_VSCREENINFO: Invalid argument in Xorg.log.0
Loads of (EE) R128(0): R128CCEWaitForIdle: CCE idle / stop / start -9 errors
Oops: Machine check, sig: 7 [#1] (dmesg)

este.el.paz · Joined:Wed Jun 15, 2011 10:57 pm Posts:403 Location: SoCal

Quote:

New here, got this old Mac G4 350 MHz with outdated 10.4. No good use.

@Omeluuk: Just a quick comment, 350 MHz would be quite slow, perhaps even for Linux . . . it might be better to try MintPPC 9.3 as a way around all of these install issues that seem to be cropping up with 11??

e.e.p.

OmeLuuk · Joined:Tue Feb 28, 2012 10:05 pm Posts:11

Hmm, speed is not the issue. In mac-mode it performs well enough for the projected tasks, being outdated is an issue there. Currently reinstalled, now finishing with ssh so in spite of the failing keyboard I can connect to the machine.

So from the fresh install, I want to dig into the installation problems.
First there is this "udevd[248]: timeout: killing '/sbin/modprobe -b pci:" error for over 5K times in /var/log/deamon.log and syslog, and counting...

OmeLuuk · Joined:Tue Feb 28, 2012 10:05 pm Posts:11

OmeLuuk wrote:

"udevd[248]: timeout: killing '/sbin/modprobe -b pci:v0000106Bd00000019sv00000000sd00000000bc0Csc03i10" error for over 5K times in /var/log/deamon.log and syslog, and counting...

This explanation of modalias brought me to the point that the errors are related to:
./pci0001:10/0001:10:0d.0/0001:11:08.0/modalias
pci:v0000106Bd00000019sv00000000sd00000000bc0Csc03i10
./pci0001:10/0001:10:0d.0/0001:11:09.0/modalias
pci:v0000106Bd00000019sv00000000sd00000000bc0Csc03i10
of which lspci tells me:
0001:10:0d.0 PCI bridge: Digital Equipment Corporation DECchip 21154 (rev 05)

Now there is no matching modules.alias file. This could be interpreted as: there is no matching module installed providing a driver for this device.

este.el.paz · Joined:Wed Jun 15, 2011 10:57 pm Posts:403 Location: SoCal

Quote:

Now there is no matching modules.alias file. This could be interpreted as: there is no matching module installed providing a driver for this device.

@Omeluuk: Clearly you have more knowledge than I do as far as Linux goes. Your conclusion may be correct . . . there are some other threads here in the forum that might provide information on how to get the right driver, which might also be easier using 9.3 as I mentioned before. OR, you might have to wait for a week or so before "linuxojemac" returns to the forum with his experience that might be able to help you--I believe he is still out of town.

e.e.p.

OmeLuuk · Joined:Tue Feb 28, 2012 10:05 pm Posts:11

Fair, meanwhile I am puzzled about this part of dmesg:

Code:

[    9.726727] PowerMac i2c bus mac-io 0 registered
[    9.782725] firewire_ohci 0001:11:0a.0: enabling device (0014 -> 0016)
[    9.812056] PowerMac i2c bus uni-n 1 registered
[    9.891154] PowerMac i2c bus uni-n 0 registered
[    9.911603] usbcore: registered new interface driver usbfs
[    9.918710] Machine check in kernel mode.
[    9.925555] Caused by (from SRR1=49030): Transfer error ack signal
[    9.932476] Oops: Machine check, sig: 7 [#1]
[    9.939299] PowerMac
[    9.946127] Modules linked in: usbcore(+) firewire_ohci(+) firewire_core crc_itu_t i2c_powermac(+) sungem usb_common sungem_phy ext4 mbcache jbd2 crc16 sd_mod crc_t10dif
[    9.960861] NIP: f244f1dc LR: f244f150 CTR: c00658fc
[    9.968110] REGS: ef18fc40 TRAP: 0200   Not tainted  (3.2.0-1-powerpc)
[    9.975484] MSR: 00049030 <EE,ME,IR,DR>  CR: 22002428  XER: 00000000
[    9.982935] TASK = ef012eb0[267] 'modprobe' THREAD: ef18e000
[    9.983133] GPR00: 00000000 ef18fcf0 ef012eb0 4f4e9a00 ef012eb0 00000000 00000002 4f32fcc0
[    9.990809] GPR08: 00000000 f245a0dc 22002422 c00658fc ffffffff 10024b28 1000bea4 103e5d38
[    9.998468] GPR16: 1000c028 00000000 1000c004 00000000 1000c018 103e7b3c 00000a60 00000000
[   10.006060] GPR24: f244dd98 ef2b5654 ef2b5614 00000016 ef2b5574 f24055c4 ef877860 ef2b5000
[   10.021086] NIP [f244f1dc] ohci_enable+0x218/0x604 [firewire_ohci]
[   10.028776] LR [f244f150] ohci_enable+0x18c/0x604 [firewire_ohci]
[   10.036395] Call Trace:
[   10.043955] [ef18fcf0] [f244f03c] ohci_enable+0x78/0x604 [firewire_ohci] (unreliable)
[   10.051813] [ef18fd20] [f23fca68] fw_card_add+0x5c/0x9c [firewire_core]
[   10.059576] [ef18fd40] [f2451290] pci_probe+0x430/0x554 [firewire_ohci]
[   10.067219] [ef18fd70] [c01d2f70] pci_device_probe+0x9c/0x110
[   10.074724] [ef18fda0] [c0279124] driver_probe_device+0xe4/0x198
[   10.082155] [ef18fdc0] [c0279248] __driver_attach+0x70/0x98
[   10.089549] [ef18fde0] [c02781e4] bus_for_each_dev+0x60/0x9c
[   10.096913] [ef18fe10] [c0278d80] driver_attach+0x24/0x34
[   10.104222] [ef18fe20] [c027894c] bus_add_driver+0xb4/0x234
[   10.111421] [ef18fe40] [c02797f0] driver_register+0xb8/0x140
[   10.118607] [ef18fe60] [c01d3e24] __pci_register_driver+0x48/0xc0
[   10.125820] [ef18fe80] [f245602c] fw_ohci_init+0x2c/0x50 [firewire_ohci]
[   10.133067] [ef18fe90] [c0003f64] do_one_initcall+0xdc/0x1bc
[   10.140293] [ef18fec0] [c007585c] sys_init_module+0x181c/0x1a1c
[   10.147488] [ef18ff40] [c0014478] ret_from_syscall+0x0/0x40
[   10.154653] --- Exception: c01 at 0xff5dd28
[   10.154660]     LR = 0x1000539c
[   10.168662] Instruction dump:
[   10.175373] 7c004d2c 38000001 981f012a 813f0538 3800003f 392900dc 7c0004ac 7c004d2c
[   10.182503] 813f0538 392900dc 7c0004ac 7c004c2c <0c000000> 4c00012c 540006be 813f0538
[   10.189608] ---[ end trace 037d13934b58aaf0 ]---
[   10.269802] usbcore: registered new interface driver hub
[   10.311773] usbcore: registered new device driver usb
[   10.327153] sr0: scsi3-mmc drive: 38x/32x cd/rw xa/form2 cdda tray
[   10.334290] cdrom: Uniform CD-ROM driver Revision: 3.20
[   10.401607] sr 1:0:0:0: Attached scsi CD-ROM sr0
[   10.437222] ehci_hcd: USB 2.0 'Enhanced' Host Controller (EHCI) Driver

It tries to tell me something, similar posts tell about overlap in resources between devices... but which and why?

OmeLuuk · Joined:Tue Feb 28, 2012 10:05 pm Posts:11

OmeLuuk wrote:

Code:

[    9.782725] firewire_ohci 0001:11:0a.0: enabling device (0014 -> 0016) .....
[    9.918710] Machine check in kernel mode. .....
[    9.946127] Modules linked in: usbcore(+) firewire_ohci(+) firewire_core crc_itu_t i2c_powermac(+) sungem usb_common sungem_phy ext4 mbcache jbd2 crc16 sd_mod crc_t10dif .....
[   10.125820] [ef18fe80] [f245602c] fw_ohci_init+0x2c/0x50 [firewire_ohci]
[   10.133067] [ef18fe90] [c0003f64] do_one_initcall+0xdc/0x1bc
[   10.140293] [ef18fec0] [c007585c] sys_init_module+0x181c/0x1a1c
[   10.147488] [ef18ff40] [c0014478] ret_from_syscall+0x0/0x40

It tries to tell me something, similar posts tell about overlap in resources between devices... but which and why?

Well, reading this (and cutting away what is irrelevant) you can read: firewire_ohci is starting, the linked modules are shown, where firewire_core adds firewire_ohci and usb_core... Well keyboard and mouse are USB attached, and none are attached to the firewire, so why not blacklisting the firewire_ohci and firewire_core?

Code:

root@AppelSapje:/etc/modprobe.d# cat blacklist.local.conf 
# Local module settings
# Created by the Debian installer

blacklist snd-aoa-codec-tas
blacklist snd-aoa-fabric-layout
blacklist snd-aoa-i2sbus
blacklist snd-aoa-soundbus
blacklist snd-aoa
# added to avoid system check on bootup
blacklist firewire_ohci
blacklist firewire_core

Reboot and <drumroll> Keyboard and mouse are working correct! For info:

Code:

root@AppelSapje:/etc/modprobe.d# modinfo firewire_ohci
filename:       /lib/modules/3.2.0-1-powerpc/kernel/drivers/firewire/firewire-ohci.ko
alias:          ohci1394
license:        GPL
description:    Driver for PCI OHCI IEEE1394 controllers
author:         Kristian Hoegsberg <krh@bitplanet.net>
alias:          pci:v*d*sv*sd*bc0Csc00i10*
depends:        firewire-core
intree:         Y
vermagic:       3.2.0-1-powerpc mod_unload modversions 
parm:           quirks:Chip quirks (default = 0, nonatomic cycle timer = 1, reset packet generation = 2, AR/selfID endianess = 4, no 1394a enhancements = 8, disable MSI = 16, TI SLLZ059 erratum = 32) (int)
parm:           debug:Verbose logging (default = 0, AT/AR events = 1, self-IDs = 2, IRQs = 4, busReset events = 8, or a combination, or all = -1) (int)
root@AppelSapje:/etc/modprobe.d# modinfo firewire_core
filename:       /lib/modules/3.2.0-1-powerpc/kernel/drivers/firewire/firewire-core.ko
license:        GPL
description:    Core IEEE1394 transaction logic
author:         Kristian Hoegsberg <krh@bitplanet.net>
depends:        crc-itu-t
intree:         Y
vermagic:       3.2.0-1-powerpc mod_unload modversions

Uncle Slacky · Joined:Sun Mar 18, 2012 4:47 pm Posts:8

Latest news from my iMac G3/350 Blueberry installation attempts - It appeared to install OK up to the Yaboot installation, where it seemed to freeze at 0% of "Installing hfsutils".

Any ideas as to what to try next? I'm currently installing vanilla Debian testing to see what happens...

UPDATE: Debian (LXDE+XFCE CD installation) couldn't detect the CD-ROM drive, and I couldn't guess the device name, so that was that. I then tried Lubuntu 12.04 beta 1, first the live desktop (xorg failure - do I need to edit xorg.conf within the live session?) and the alternative installer (blank screen after about 5 minutes of modprobing).

Does the "installing hfsutils" part of the yaboot installation take a long time? Was I merely impatient? I'll try MintPPC 9.3 next, I think.

BTW the system has 256Mb RAM and ~7Gb hard drive (I will upgrade the HD to a 40 Gb one if I can be sure I can get *any* Linux to install!)