search for: openfirmwar

https://bugs.freedesktop.org/show_bug.cgi?id=91319 Bug ID: 91319 Summary: Nouveau driver cannot extract FCODE ROM / DCB Block from OpenFirmware Device tree Product: xorg Version: unspecified Hardware: PowerPC OS: Linux (All) Status: NEW Severity: normal Priority: medium Component: Driver/nouveau Assignee: nouveau at lists.freedesktop.org...

Am 15.09.2015 um 17:12 schrieb Keith Keller <kkeller at wombat.san-francisco.ca.us>: > On 2015-09-15, wwp <subscript at free.fr> wrote: >> >> Searching the web, I see very few possibilities to install a recent (I >> need gnome2) GNU/Linux distro on such hardware. I gave Linux MintPPC 11 >> (http://www.mintppc.org/content/list-macs) a try, but the netinstall

...eonfauster at googlemail.com> wrote: >>> On 2015-09-15, wwp <subscript at free.fr> wrote: >> >> this also helps to boot >> >> http://www.rodsbooks.com/refind/ > > rEFInd will work on EFI-based Macs, but not on old PPC Macs, which are > based on OpenFirmware (so grub won't work either). you are right - its long time ago that i used a macmini and it was indeed intel based. Before that i used a powerbook and remember that the boot loader was http://mac.linux.be/content/yaboot -- LF

Posting video cards usually require running x86 ROMs. This doesn't work to well when people plug x86 video cards into ia64 and ppc machines. People do this because the x86 versions are half the price of the OpenFirmware ones. Even x86 machines need to run the ROMs for secondary cards. I'm in the process of modifying fbdev to use hotplug events to run these ROMs. What about including emu86 support in non-x86 builds and vm86 on x86 in klibc? The linux BIOS people have a 40K version of emu86 available. Right n...

Hi, OLPC's Openfirmware (OFW) implementation chokes when attempting to boot an iso created by isohybrid. The problem is that OFW's ISO-9660 support expects a partition type of 0x96 (CHRP ISO-9660, according to http://en.wikipedia.org/wiki/Partition_type). I see from http://git.kernel.org/cgit/boot/syslinux/syslinux...

At 04:18 PM 8/4/2020, you wrote: >Am 05.08.20 um 01:09 schrieb david: >>At 01:54 PM 8/4/2020, you wrote: >>>On Tue, 04 Aug 2020 13:44:05 -0700 >>>david wrote: >>> >>> > After all the updates, the system was NOT bootable. >>> >>>How long did you wait for it to boot, and what >>>did it do when it failed to boot?? What text

...u use UEFI, right?) >>> >>>-- >>>Leon >>>____________ >> >>I'm not sure how to turn 'secure boot' off or if it exists. >>(MacMini5.2).? I presume it uses UEFI, but not sure how to answer that. > >Oh, an apple device. AFAIK the openfirmware of >such hardware have also a legacy mode. So first >check if it uses the UEFI mode at all by checking >if this directory exists (in the working/bootable system): > ># ls -la /sys/firmware/efi > >if so test the secure boot state with > ># mokutil --sb-state > > &...

...veaufb vs OFfb NVDA,Displ - removing generic driver Console: switching to colour dummy device 80x25 nouveau [ DEVICE][0000:0a:00.0] BOOT0 : 0x043200a4 nouveau [ DEVICE][0000:0a:00.0] Chipset: NV43 (NV43) nouveau [ DEVICE][0000:0a:00.0] Family : NV40 nouveau [ VBIOS][0000:0a:00.0] checking OpenFirmware for image... nouveau [ VBIOS][0000:0a:00.0] ... checksum invalid nouveau [ VBIOS][0000:0a:00.0] checking PRAMIN for image... nouveau [ VBIOS][0000:0a:00.0] ... signature not found nouveau [ VBIOS][0000:0a:00.0] checking PROM for image... nouveau [ VBIOS][0000:0a:00.0] ... signature...

...for helping me get my 7043-150 doing something useful! Sincerely, Richard PS: Has anyone tried running other Linux distros? I did not have any luck booting the latest Debian (debian-31r0a-powerpc-binary-1.iso) or NetBSD (2.0.2, prepcd.iso) on this system, but maybe I wasn't using the right OpenFirmware commands.

On Wed, Apr 27, 2016 at 07:31:43AM -0700, Andy Lutomirski wrote: > On Wed, Apr 27, 2016 at 7:23 AM, Joerg Roedel <joro at 8bytes.org> wrote: > > On Wed, Apr 27, 2016 at 04:37:04PM +0300, Michael S. Tsirkin wrote: > >> One correction: it's a feature of the device in the system. > >> There could be a mix of devices bypassing and not > >> bypassing the

On Wed, Apr 27, 2016 at 07:31:43AM -0700, Andy Lutomirski wrote: > On Wed, Apr 27, 2016 at 7:23 AM, Joerg Roedel <joro at 8bytes.org> wrote: > > On Wed, Apr 27, 2016 at 04:37:04PM +0300, Michael S. Tsirkin wrote: > >> One correction: it's a feature of the device in the system. > >> There could be a mix of devices bypassing and not > >> bypassing the

...EMU (or whatever), put in your magic developing stuff, and try to flash the BIOS. Of course you want to make sure you're running on an emulated processor, not your real one. QEMU does have a -bios option to "set the filename for the BIOS", and it looks like that's how the folks at openfirmware are trying things out, though I don't know if QEMU supports _writing_ back to the file. Cheers, Jake

...ration AFAICT that has virtio and and > IOMMU. So maybe the right solution is to fix q35-iommu to use DMAR > correctly (thus breaking q35-iommu users with older guest kernels, > which hopefully don't actually exist) and to come up with a PPC- and > SPARC-specific solution, or maybe OpenFirmware-specific solution, to > handle PPC and SPARC down the road. > > [1] I'm pretty sure I emailed the QEMU list before q35-iommu ever > showed up in a release asking the QEMU team to please not do that > until this issue was resolved. Sadly, that email was ignored :( > > --...

...ration AFAICT that has virtio and and > IOMMU. So maybe the right solution is to fix q35-iommu to use DMAR > correctly (thus breaking q35-iommu users with older guest kernels, > which hopefully don't actually exist) and to come up with a PPC- and > SPARC-specific solution, or maybe OpenFirmware-specific solution, to > handle PPC and SPARC down the road. > > [1] I'm pretty sure I emailed the QEMU list before q35-iommu ever > showed up in a release asking the QEMU team to please not do that > until this issue was resolved. Sadly, that email was ignored :( > > --...

https://bugs.freedesktop.org/show_bug.cgi?id=31122 Summary: Cannot control backlight intensity on Powerbook Product: xorg Version: unspecified Platform: PowerPC OS/Version: Linux (All) Status: NEW Severity: enhancement Priority: medium Component: Driver/nouveau AssignedTo: nouveau at

...iso simply fails in installing a boot loader that conserves the >>> original OS/X partition even after many tries and workarounds. > > this also helps to boot > > http://www.rodsbooks.com/refind/ rEFInd will work on EFI-based Macs, but not on old PPC Macs, which are based on OpenFirmware (so grub won't work either). --keith -- kkeller at wombat.san-francisco.ca.us

...sure; I imply that you use UEFI, right?) >> >> -- >> Leon >> ____________ > > > I'm not sure how to turn 'secure boot' off or if it exists. > (MacMini5.2).? I presume it uses UEFI, but not sure how to answer that. Oh, an apple device. AFAIK the openfirmware of such hardware have also a legacy mode. So first check if it uses the UEFI mode at all by checking if this directory exists (in the working/bootable system): # ls -la /sys/firmware/efi if so test the secure boot state with # mokutil --sb-state > > Boot failure only occurs when the g...

.../subdev/bios/shadowof.c +++ b/drivers/gpu/drm/nouveau/nvkm/subdev/bios/shadowof.c @@ -66,11 +66,16 @@ of_init(struct nvkm_bios *bios, const char *name) return ERR_PTR(-EINVAL); } +static void of_fini(void *p) +{ + return kfree(p); +} + const struct nvbios_source nvbios_of = { .name = "OpenFirmware", .init = of_init, - .fini = (void(*)(void *))kfree, + .fini = of_fini, .read = of_read, .size = of_size, .rw = false, -- 2.39.2

...Problem is repeatable, even after repairing file permissions. Installation log file shown here: R 1.9.1 Installation Log Target Selection _volumeAppeared: Adding volume Macintosh HD deactivate: removing all cells from _volumeMatrix Selected volume "Macintosh HD" Mounted at: / OpenFirmware: mac-io/ata-4@1f000/@0:5 Partition type: HFS+ Partition map: disk0s5 Partition: 5 Protocol: ATA Media Type: Generic Volume Size: 80019709952 rm: /Library/Frameworks/R.framework/Versions/Current : Permission denied rm: /Library/Frameworks/R.framework/R : Permission denied r...

...is no other configuration AFAICT that has virtio and and IOMMU. So maybe the right solution is to fix q35-iommu to use DMAR correctly (thus breaking q35-iommu users with older guest kernels, which hopefully don't actually exist) and to come up with a PPC- and SPARC-specific solution, or maybe OpenFirmware-specific solution, to handle PPC and SPARC down the road. [1] I'm pretty sure I emailed the QEMU list before q35-iommu ever showed up in a release asking the QEMU team to please not do that until this issue was resolved. Sadly, that email was ignored :( --Andy