@geennaam
I was about do drop writing in this topic for good, but just want to clarify: i do not understand what you trying to arciieve with this your last post ? Who those amoral and bad guys are ?

Me, walkero and few others are bad guys of the same league, because we say that your drama actions hurt them and its all can handled better if in first place you dont act like you act ?

I mean , we amoral, bad, and that sort of peoples because we find your actions strange ?

And Acube bad too, because they simple not read readme, while you will teach them now how world is working and no one should ever forget to read readmes for your drivers in fear you again will act like that and remove something else ?

Honestly, i were sure today you will remove something else from os4depot for any reassons.

And just a little question: do you think, that with all you super moral you have, and the way how you act with all this drama users should hope and wait your developing when they know now, that in any day when you will dislike anything else (not forgotten readme, but someone call you bad, or doing what you dislike or whatever else), you will again remove something or stop something ? I mean this no worry you when you call some of us as a bad guys ? All ok and fine ?

Look, we need developers, you are good one, that for sure. But emotional stability is must if one work on anything amiga like, or its all false hopes and a carrot for users which we have many before

@geennaam
So, we (users) should understand your reassons, by reading GPL or whatever to drivers (which no one except ones include them do), but you not worry at all that you giving them at first driver, then remove it, then tell them to not use version from webarchive. Is it friendly to them ? Is it correct way if solving issues you had with acube ? Maybe we all immoral there, but at least we not show users something, and then remove it with explains that someone guilty for. If someone use driver from webarchive - what the problem ? Tell in friendly way that driver outdated and better one will be out only with Enhancer, why all that "i will not", just because users want to use old outdated driver ? Its all can be super moral from your side, and amoral from our, but this simple speaking strange.

As for Enhancer, i am not agaisnt it, i am against of how Mattew handle it, and how he grab Hyperions versioning theme for hes replacements and how he handle SDK for classes. But its all his iwn thing, and because he didnt do as some of us want, i didnt say "i will not" or "that is reasson why i xxxx" and so on.

@joerg
Let be honest, devs stop working on amigaos as they burnout, and things go not as perfect as they wish. But instead of dealing with issues, its always cool to bring some drama on users (who give a shit) about someone being guilty for something, right ?:)

Any of us can find nany excuses why better not do anything for os4, but we do, in favor of users.

@joerg
Quote:

Of course os4 kernel for peg2 do not support it : that the point of whole thread. And Hans trying to add support of it in the kernel. And while we are able to find RX/HD card behind the bridge, we fail to read things/addresses from properly : that need kernel fixes/changes, of course. Hans trying firstly RTAS , and fail. Now our way is direct access. And lately we trying to find if "config-l" commands and co can read from the card from firmware, to see correct adresses and stuff, and compare if it indeed RTAS do not works, or we just may use wrong addresses, etc.

@Balaton
Quote:

Aren't we trying to play with all this config-l@ stuff exactly for the reasons to know if smartfirmware read things correctly already, so to see if address we find is correct, so to not use RTAS if RTAS fail, but direct access ?

I mean what make you think that "they may not be accessible via RTAS" ?

@Hans
Tried all different ways of syntax and still have no luck (with 16 before, after, with spaces, etc ,etc).

But, what i find in some docs are:

There are two types of words, global and local. Global words come with the version of Open Firmware present on the computer. Some of these are placeholders that get overwritten by device specific local words. Local words are restricted in scope to the device that contains the word. The available global and local commands can be listed with the command "words"

So, if i come to the exactly video card and type "words", i then have nothing, see:



But if i go only to the bridge itself , i.e. just cd /pci/pci@7 and type "words", then:



As i understand, those local words (like config-l@) can be used only when we in some device which can be used with.

Then when i am in the bridge, then typing "config-l@" without args do not cause error. But also other ways too:




Simple help on config-l@ (while being in the bridge directory), print out that:



But i not sure, if that can help us ? I mean, what "config-addr -- data" mean, and, can we provide as argument "display@0" or "display@0,1" to read what we want to read ?

So far tried that with no luck:

config-l@ display@0 16
config-l@16 display@0

Question now what is that "config-addr -- data" , from where get it, and will it of any help for us.

Maybe we somehow need to open/select the card in firmware to be able to have those words like "config-l" to work with ..

@geennaam
You really think Acube "making money" ? And that they "illegally" rob you with exactly this intention to "make money" on your driver ? It sounds too much. Even if they forget to read readme, its your business with them. Wrote to max, explain what wrong with, and be done with. No needs for "i will, i will not". Dont want - dont do. If want - do. No one need all this driver uploads and then druver removal.

Pure users shouldnt have all this drama on them if you made driver for them. You cant expect understanding on this "i remove driver" and put users in position of digging into your explaining of why it was for them, but now its not for them.

If you think Acube making money on your driver, and you cant talk with them about, let me cover all your fees for those 20-30 solded Sams, if that make you end all this "i will, i will not". How much you need for ?

We all mature persons for all this "if else i will i will not" : users dont care about reassons and emotions, they care about final thing to use. If what Acube did for users (and not fir money as you may think), i will happy cover all the fees for you for every board they sold with your driver which no one should ever find anymore as then you will not work on amigang stuff anymore. Its jyst funny, even if you see it as someone rob you. You by some reassons dont want to deal with and forget, but throw it at users.


Ps. If you cant deal with things you dont like, you need to know how amiga (dark) side can be, and this should not broke your intentions. For real, its just really bad to upload, and then remove driver. I didnt wrote about before, as were in hope you will deal with already, as you always sounds logical. Strange why in end of all it turns like this. But as i say i can cover for you all the fees you may think Acube should back at you. Just think of me as their worker, and i will deal with Max myself after, but the covering of fee will be done by me, no problems.

@geennaam
While i am fully on your side, i still should say it: Its only on amiga we made problems while there is none. Certain italian manufacturer is only the one keeping amiga-ng hardware for us. Point on them like they rob anyone with words "illegaly" is too much, for sure. Guys tried to keep it all alive for many years, and claim that they "illegaly" take a driver from os4depot and give it to users to make them have less problems is too much. Max and others always very helpfull, always produce hardware for us, always produce fixes and updates for uboot, which surely didnt cover a shit on their so called sales. Even if you feel its bad that they include your driver for users , why not forgive them for in favor of what they do for years ?

You made driver in first place for users, rigth ? Then, wtf play this premadona games like removing/not removing blabla ?

Yes, we lack developers, yes you are good one, yes, we need developers like you, but why on earth all skilled devs at first always please the community, and then plays all this poses, child-kind things, finding guilties and all that ?

What you expect from ppls ? That everyone will respect your wishes ? Especialy those "there is driver, no there is no driver" ? Why not give whole thing mature rest, and just keep doing stuff instead of bringing drama while there is none ?

If you have no interest in something - dont do it. If you have - do it. Playing emotional games werent strong mature thing ever.

This Italian manufacturer may forget to read readme and ask you, or whatever : give them a rest in favor of their past and present activites. Some user put link onvwebarchive with old driver ppls need ? Give them a rest as they only wish to help.

As i say, i fully at your side, and yes, things may be sorted better, but you skilked dev and a adequate one, why on eartg you want to block someone from using your driver, why you ever wrote that then ?

@Hans,Balaton

Ok so, I attached the bridge with X1950 to the first after AGP PCI slot, and then bridge show up on /pci@8000000/pci@7, so:



So on PCI line we have bridge, with 2 displays in (probably for 2 different video outputs?)


going to any of them via "cd" and typing "config-l@16" cause :



Same if i tried with space between, i.e. config-l@ 16. Writing "config-l" or "config" or "config-w" without args cause the same error. Typing it all with dot at beginning like ".config-l@16" or ".config-l@ 16" (with space) cause same errors.

Any ideas ?:)

Shouldn't we do something else to be able to use those "config-" commands ? Maybe we should enter in some mode first or something ?

@balaton
Quote:

Can you maybe point out of how/what exactly to check from OF ?

ps. If issue is passing the wrong address, it did't explain why debian fail to remap phys memory too and takes it as 0x000000.

@balaton
So in bboot you accessing PCI configuration registers directly and not OpenFirmware's calls for that? I.e. no RTAS and co ?

@Hypex
Quote:

The Debian net install can install without internet connection for sure : it says "you have no connection, install the base minimal setup ?" , but then, even if it installs it, it misses some post-install steps, making the system not bootable in the end.

Quote:

You didn't search close enough for, in the Google there are few places pointing to correct servers which can be used with Debian (at least the one for pegasos2, which is 8.11):




@All
Please not deral thread too much now, we need Balaton to see what Hans ask, as this is what important for us in this thread. Thanks !

@smarkusg
I of course tried and pure base install from netiso, and with manual typing of correct mirrors working today (archive...something, and it dl stuff from net when install), but in any case it fail. But from dvd1.iso all goes well. Its like net install is broken in some way and didnt manage properly to do post install steps to make system to boot.

But so far dvd one works, that enough for our tests :)

@All
Ok, that the next test i do :

I plugged off Radeon9250, keep only Bridge+Radeon X1950 in, installed SSHD server, and boot the linux. Now, when i do "lspci -knn" , i had:



So the same bridge and X1950 in found, but no driver loaded (probabaly this "radeon" driver should be ok for ?)

Then, i do "dmesg | egrep 'drm|radeon'" , and that what we have:



I can be wrong, but it seems that phys address is set to 0x0 again (the same as we have under amigaos4 as far as i understand).

@All
So, installation done, working , i attached my Pericom "PI7C9X111SL" bridge to pegasos2 and install an X1950 XT in it (this is together with Radeon9250 installed in and booted from).

Now, when i type "lspci -knn", i do have this:



So, bridge definitely can be seen:



So as X1950 XT in it:



Now the question is : how to make X1950 to output on ? Should i install some driver for firstly somehow (at least as i know X1950 do have powerpc drivers, right?)

Simple plugging radeon9250 off, and attach video cable to X1950 do not make any output (probably because no driver loaded up automatically, dunno).

Is this "radeon" driver should support X1950 ? If so, how can i say to kernel to use the card in the bridge, and not the radeon9250 in AGP ? Or maybe another driver should be used ?

@smarksugs
Installing from powerpc-DVD-1.iso works fine ! I can see that when installation finished, it doing some more steps in "Finishing installation" stage, and then, i am able to boot correctly, and in the log i can see that initrd image attached.

So, netinstall.iso is broken for full installation seems so (at least on real Pegasos2). You can boot from it, but not sure if you can install working system from netinstall.iso even over QEMU.

Now ... Time to check Bridge with something like X1500 if it works at all.

@all
Which version of Ubuntu is the latest one for pegasos2 ? I mean 16.04, but which one ? I found these:

ubuntu-16.04.6-server-powerpc.iso (720 mb of size)
ubuntu-mate-16.04.1-desktop-powerpc.iso (1.6gb of size)

If someone can bring a working link to the very latest working one, that will help, thanks !

@smarkusg

Do you use DVD-ISO1 always, and never netinstall.iso ? I vaguely remember this one may have an issue, can't remember which ones... found this:

https://lists.debian.org/debian-powerpc/2015/06/msg00005.html


Also issues with un-reading ext2 fs from OF can be because of "too many" previous volumes, or too far behind the beginning (200-300gb) or something .. At least with new hdd , i can list ext2fs partition, but then it didn't fix my issue with non-booting after install, as they seem different.

But then it also mean, that then i basically can use my old FFS boot partition with no problems either once i deal with this non booting issue, as it seems irrelevant from where boot kernel if OF can see it: all it needs to provide path to root partition (if installation went fine..)

Will try CD-1.iso instead of netinstall.iso now

@all
So, tried clean SSD : created 100mb of Ext2 (with mount point /boot) , 50 GB of Ext3 and (with mount point /) and 5 gb of SWAP. Then installed the base system , reboot, and can do "ls hd:0" :



Then typed:

boot hd:0 vmlinuz root=/dev/sda2

And it again the same hang ! Again didn't take into action initrd:



@smarkusg
Quote:

Yeah, when i do have ext2 as first one, then insdeed i can "ls" it from openfirmware. But then, i can the same manually put kernels to my FFS boot partition and boot from it. As of now, it seems that problem somewhere else on my own, because it always can't attach/find initrd , even if I use clean SSD.

It's like installation process didn't do something which should call to load initrd stuff.


ps. And i also use debian-8.11.0-powerpc-netinst.iso if that make sence when installing OS.

@balaton
I will try now just the clean SSD, and will experiment a bit. I am sure someone already did all of this back in the past, just can't find anything about in the google.

@smarkusg
Yeah, you definitely can list content in !
But, hd:0 is your first partition, so maybe that matter ? (my one is the 6,7 and 8st ones for linux, not the first one). And what is interesting is that when i install linux, it says before installing starts "your boot partition should be the first one in order to boot, want to make it as first one, or keep it as it ?" . So i keep it as it, as my first one is my boot FFS partition, which had os4 and morphos boot imgs, and which i can't delete.

Maybe OF of pegasos2 can access to ext2fs only when it in hd:0 ? But then wtf :)

And your boot partition is surely EXT2 ? Can you plz also do that:

cd ide
ls

?

ps, see how my list of partitions looks like (only different that on video i tried now for #6 is ext3fs for root partition, before all tests were with ext2):



And you can see on 0:14 that error about "your boot is not located on the first partition of the disk", but then, my boot is the first one, I use it for os4 and mos. And why i can't list content of ext2 partitions from OF and you can is quite strange.