The "Invalid ROM" is an error that appears once KMS is working. I shows up on G4 machines as well. On Wed, 8 Jul 2015 14:42:00 -0700 Rick Thomas <rbthomas@pobox.com> wrote: > Thanks Peter! > > I’m sure I’ve got the 3.18 kernel. I confirmed that with “uname -a” after the boot. Your yaboot stanza looks exactly (in the relevant particulars) like mine. And, yes, I did “ybin -v” and checked to make sure the output looked right. > > The ppdev and parport_pc anomalies have been there all along. I don’t think they have anything to do with this problem, though. > > The only thing I can think of that might be related (and possibly causing the “Invalid ROM” message) is that the base system is Sid, not Jessie. The default kernel is > > > rbthomas@bigal:~$ uname -a > > Linux bigal 4.0.0-2-powerpc64 #1 SMP Debian 4.0.5-1 (2015-06-16) ppc64 GNU/Linux > > So there may be remnants of that lying around that confuse the issue when running with your kernel… > > Didn’t you mention you had some trouble with the firmware blob in Sid? > > I’ll be interested to look at your dmesg and xorg logs. I’m not getting to anything involving xorg — the black screen happens before I get to the login prompt. I have /etc/X11/default-display-manager set to “/bin/false" to prevent X from starting up automatically. When I want to start X, I do a manual “startx” from a text console. > > Enjoy! > Rick > > PS: I’m planning to install a plain-vanilla, fresh-out-of-the-box, Jessie then add your kernel, and I’ll report back on that. > > Re, the FCODE ROM: Where can I read-up (RTFM, but what FM?) on the nouveau module parameters? > > Thanks! > > On Jul 8, 2015, at 1:04 PM, Peter Saisanas <psaisanas@gmail.com> wrote: > > > Hi Rick, > > I should probably start a new thread for reports.... > > > > Seems odd to me that systemd is attempting to load modules ppdev, parport_pc along with snd-powermac... > > > > Are you sure you are booting up with my actual compiled kernel and initrd? > > > > Please confirm your /etc/yaboot.conf file has entries for the image and initrd, see below. > > > > image=/boot/vmlinux-3.18.16-powerpc64 > > label=linux > > read-only > > initrd=/boot/initrd.img-3.18.16-powerpc64 > > append="" > > > > Ensure you have saved the yaboot.conf and then run "ybin -v" to apply the changes to your boot loader. > > > > I have attached a dmesg log from my system. note my audio hardware isn't working (hardware fault), so disregard the issues with snd-aoa-onyx. > > > > I have also attached my xorg log for reference. > > > > The nouveau driver attempts to scan for the nVidia DCB block (within a typical VGA bios or FCODE ROM via alternate methods, it seems to perform this scan automatically, but if curious, refer to the "NvBios" nouveau module parameter. > > > > Let me know how you go. > > > > Cheers, > > Peter > > > > > > On 08/07/15 19:40, Rick Thomas wrote: > >> On Jun 30, 2015, at 3:48 AM, Rick Thomas <rbthomas@pobox.com> > >> wrote: > >> > >> > >>> I’ll definitely report on how things work on my hardware with your kernel, but it will have to wait til after the weekend. 4th of July == US Independence Day == lots of neighborhood/family/etc parties and celebrations == no time for playing with computers. > >>> > >>> I’m looking forward to sending a report soon! > >>> Rick > >>> > >> Hi Peter, > >> > >> I installed your 3.18… kernel. I get a black screen. > >> > >> Here’s what “journalctl -b | grep -C5 nouveau ” says. I hope it help. Note the error from nouveau about “Invalid ROM contents”. Is that expected? > >> > >> Thanks! > >> Rick > >> > >> > >> > >> > >> > >> > > > > <dmesg.log><Xorg.0.log> > > > -- > To UNSUBSCRIBE, email to debian-powerpc-REQUEST@lists.debian.org > with a subject of "unsubscribe". Trouble? Contact listmaster@lists.debian.org > Archive: [🔎] B3819C60-BBD0-45C3-920C-5FC1E09A2862@pobox.com">https://lists.debian.org/[🔎] B3819C60-BBD0-45C3-920C-5FC1E09A2862@pobox.com > -- Herminio Hernandez Jr <herminio.hernandezjr@gmail.com>
Attachment:
pgpwnBZJcOW9V.pgp
Description: PGP signature