Re: PayPal pool for developer M1 Mac mini for OpenBSD port
Hi, the guys at corellium can boot the Linux kernel and also Ubuntu Linux on a arm based mac mini. Some details can be found at: https://corellium.com/blog/linux-m1 https://github.com/corellium https://asahilinux.org/ Some details sound strange: "...If that wasn't enough, Apple designed their own interrupt controller, the Apple Interrupt Controller (AIC), not compatible with either of the major ARM GIC standards. And not only that: the timer interrupts - normally connected to a regular per-CPU interrupt on ARM - are instead routed to the FIQ, an abstruse architectural feature, seen more frequently in the old 32-bit ARM days. Naturally, Linux kernel did not support delivering any interrupts via the FIQ path, so we had to add that..." Best regards, Sven On 12/3/20 8:35 AM, Otto Moerbeek wrote: On Thu, Dec 03, 2020 at 03:18:54AM +0200, Mihai Popescu wrote: I have only good wishes for the project, but I still don't get one thing: why do some people start to behave oddly whenever Apple comes into discussion. They are doing a proprietary thing, closed as hell, no documentation and so on. Why is this impulse to write code for such a thing. Just asking ... It's a new interesting ARM platform with very good performance. Yes, it is closed but it's also kind of a nice challenge to overcome that hurdle. So mixed feelings about that part. -Otto
Re: PayPal pool for developer M1 Mac mini for OpenBSD port
On 3.12.2020 21:46, Jasper Valentijn wrote: Op do 3 dec. 2020 om 11:28 schreef Stuart Henderson : On 2020-12-03, Janne Johansson wrote: > Den tors 3 dec. 2020 kl 02:21 skrev Mihai Popescu : > >> I have only good wishes for the project, but I still don't get one thing: >> why do some people start to behave oddly whenever Apple comes into >> discussion. >> > > It could also be that if it becomes operable, it is quite a useful machine, > whereas sticking to Pine64 experiment boards and FruityPi clones does quite > limit the usefulness even if they are all aarch64s. That, plus it's a challenge. Some people do sudoku or cryptic crosswords, some play musical instruments, some port OS to new hardware. And some do several of the above (and more). We as community could help to make that possible, I'm wondering how many machines would be needed to make it work. Plus it can be funny race with https://www.patreon.com/marcan Who asks for 4k USD/month for the same goal, just with Linux -- “We spend the first twelve months of our children's lives teaching them to walk and talk and the next twelve telling them to sit down and shut up.”
Re: PayPal pool for developer M1 Mac mini for OpenBSD port
Thanks everyone, this is very good news. Some people are maybe upset by Apple's recent move, but I think OpenBSD devs should be the most enthusiast. In a world of IT hell, "paradise" (simple, neat) software should welcome "paradise" hardware & infrastructure, this is why there was so much chipping in only a few days I think. "simple, neat" hardware & infrastructure doesn't mean "pull in more energy, make it hotter, more complex, and do everything". "free software" is really a way to enrich "some companies" to provide them complex technology for free while labelling "non free" stuff as evil. Someone has to do simple, neat hard and it has always been Apple. Cooperating will certainly lead to good results because companies like Apple put goodness before everything else, otherwise they wouldn't do what they are doing now. (ditching Them) Just throwing in random opinions for those who mistake free software and goodness, it's not as simple. Apple Silicon a lot faster and neat for less power, this is the way to the future. Of course you cannot disclose everything as soon as you release it because otherwise "they" would try to terminate it and nothing would ever be done. Chippers are wiser than fear mongerers Kawashima (just a periodic donator) > R2/12/04 8:12、Tom Smyth のメール: > > Thanks Patrik, Marcan, and Theo... > > Interesting project... OpenBSD on the M1 :) ... best of luck with it > > > >> On Thu, 3 Dec 2020 at 22:11, Patrick Wildt wrote: >> >> This really has shown how much interest there is in having OpenBSD >> running on those machines. Still, we would all not be here without >> the OpenBSD project itself. Not being able to host hackathons due to >> COVID-19 leaves an impact, and I hope that soon(TM) we'll be able to >> get back together to shut up and hack. >> >> I'm sure you all love using OpenBSD and hacking on OpenBSD as much as I >> do, so to help OpenBSD run infrastructure, organize hackathons and to >> flourish even more, please consider donating! >> >> https://www.openbsdfoundation.org/donations.html >> https://www.openbsd.org/donations.html >> >> Also a shoutout to marcan, who'll be doing a lot of reverse engineering >> on the M1. He's pretty good, and I'm supporting his project by being a >> patron. I'm looking forward to his work, because of all the people out >> there who can do it, he's definitely one of them. >> >> https://www.patreon.com/marcan >> >> Patrick >> >> Am Thu, Dec 03, 2020 at 02:33:34PM -0700 schrieb Ben Goren: >>> Oh, wow — it hasn’t even been a full day since I sent this out...and >> already enough of you have chipped in enough to buy not just a single M1 >> system for Patrick, but also a second one for his partner in crime, Mark >> Kettenis. >>> >>> Thank you to all! This show of generosity and support and excitement is >> most welcome. (And, frankly, a bit overwhelming.) >>> >>> If anybody reading this still wishes to donate to the cause, despite the >> immediate needs being met, the money will be put to good use. There are >> other developers who will eventually need their own hardware, and there are >> always other sorts of expenses related to development. Feel free to chip in >> at Patrick’s original link: >>> >>> https://www.paypal.com/pools/c/8uPSkfNJMp >>> >>> ...or, of course, to the OpenBSD general fund (which can *ALWAYS* use >> donations): >>> >>> https://www.openbsd.org/donations.html >>> >>> Thanks again, everybody! >>> >>> b& >>> >>>> On Dec 2, 2020, at 2:59 PM, Ben Goren wrote: >>>> Greetings, all! >>>> >>>> Patrick Wildt has set up a PayPal pool to raise funds to purchase an >> M1 Mac mini so he can start porting OpenBSD to the platform. If you’d like >> to be able to run OpenBSD on an M1 system, now would be a great time to >> throw some pennies his way. >>>> >>>> The donation link: https://paypal.me/pools/c/8uPSkfNJMp >>>> >>>> Read below for an idea of what one might expect if we can get a >> machine into Patrick’s hands. >>>> >>>> Cheers, >>>> >>>> b& >>>> >>>> Patrick wrote: >>>> >>>>> Yes, kettenis@ and me are the two ones doing the major work on >> porting >>>>> to new devices. Not sure if kettenis@ is interested, but I can ask >> him. >>>>> I definitely am, a Mac Mini as a dedi
Re: PayPal pool for developer M1 Mac mini for OpenBSD port
Otto Moerbeek writes: > It's a new interesting ARM platform with very good performance. Yes, > it is closed but it's also kind of a nice challenge to overcome that > hurdle. So mixed feelings about that part. Let's not also forget that it gives people a choice as to what software they can run - rather than having to run something out of necessity (i.e. macOS) because it's the only thing that will run. Is that not the dictionary definition of "vendor lock-in"? :-) It's probably more of an investment in the future, since somewhere down the line Apple will decide they want to extract some more money from their users, and stop supporting that particular piece of hardware. What do you do then? You either put up with running an old, out-of-date version of macOS on your perfectly good hardware, give up and buy new hardware, or, you start looking at alternative OS to run. OpenBSD being one of those alternatives would be splendid. That's not to say that if I had some compelling reason to purchase such a machine today, I wouldn't love to be able to run something other than macOS on it - preferably where the value of "something other than macOS" is OpenBSD. So I am definitely *not* saying that attempting to support such hardware in the nearish future is bad idea. In fact, I think it's tremendous. I wish those involved the best of luck. (Also, I envy those who have sufficient time to attempt such a thing, especially if it's just for nothing other than shits and giggles.) Ash
Re: Fwd: PayPal pool for developer M1 Mac mini for OpenBSD port
Clearly I missed Patriks Email ... earlier.. :/ sorry folks +1 if experienced Devs are working on it... it will happen Best of luck to the people working on getting it working ... cant be easy without all the docs ... Thanks On Thu, 3 Dec 2020 at 22:39, Tom Smyth wrote: > Hi Jeff, > > as far as Im aware... if you donate to the project they will source > hardware as the project sees fit.. > if there is an M1 in want.html (where a developer is looking for one to > make an initial POC before the project considers it viable to spend > resources... > it I would be happy to contribute... for that purpose .. > > I dont think anyone has anything specific against apple. per sya.. > there are objections to proprietary firmware... and binary blobs... > and this makes development of OpenSource Systems even harder than it > already is... > > but yes tthe M1 looks awesome it will be interesting to see if they open > it up (a little) ... but it is an arm chip ... so perhaps testing and > providing > open arm hardware would help the project more... check out want.html > > all of these are my own observations as a user over the years and im not > a developer in OpenBSD > > Thanks > Tom SMyth > > > > > > On Thu, 3 Dec 2020 at 22:11, Jeff Joshua Rollin > wrote: > >> >> >> >> Forwarded Message >> Subject:Fwd: PayPal pool for developer M1 Mac mini for OpenBSD >> port >> Date: Thu, 3 Dec 2020 21:56:51 + >> From: Jeff Joshua Rollin >> >> >> >> >> >> Oops, forgot to reply to the list. Sorry for the duplicate, Mihai. >> >> >> On 03/12/2020 01:18, Mihai Popescu wrote: >> > I have only good wishes for the project, but I still don't get one >> thing: >> > why do some people start to behave oddly whenever Apple comes into >> > discussion. >> > They are doing a proprietary thing, closed as hell, no documentation >> > and so >> > on. Why is this impulse to write code for such a thing. Just asking ... >> >> Apple make great products. My iMac, which is nearly ten years old, runs >> without problems even today (try that with Windows). iPads and iPhones >> have much better lifetimes than Android devices - we'll see if the >> increasing number of devices running "real Linux" make a dent in the >> market, but either way there are AFAIK no phones using any of the BSDs >> (unless you count macOS/iOS, which for these purposes I don't) anyway. >> >> Other than the fact that the platform is proprietary, the only other >> thing that annoys me about Macs, and always has, is their half-arsed >> attempt at a British keyboard, which unless it's changed since my iMac >> was manufactured still puts @ and " in the wrong places for Brits - >> exactly the opposite places on a US keyboard. (Even Commodore, infamous >> in its day for reliability problems and which bought the Amiga company >> in what no less august an institution than Amiga Format magazine called >> "a rare fit of insight," managed that one.) Fortunately, if you also use >> Linux/UNIX, the problem of switching between keyboards with @ and " in >> 'the wrong place' is easily solved for X11 by selecting a Mac UK >> keyboard in the software settings even on a PC. (They did stubbornly >> stick with that crap butterfly keyboard for four years, for reasons >> presumably best known to themselves, but luckily that era also seems to >> be over, and I didn't bother buying one during that time, for that and >> other reasons.) >> >> As for the proprietaryness, other than the fact that it's a nice new >> hardware architecture as other people have mentioned, pretty much every >> other architecture OpenBSD, NetBSD and Linux has ever run on (Amiga, Sun >> and VAX, for example) is/was proprietary. And that's without considering >> the closed peripherals (without which OpenBSD wouldn't have to eschew >> NDAs) or the BMC on a Wintel - heaven knows what that thing really gets >> up to. >> >> My £0.02 >> >> Jeff. >> >> > > -- > Kindest regards, > Tom Smyth. > -- Kindest regards, Tom Smyth.
Re: PayPal pool for developer M1 Mac mini for OpenBSD port
Thanks Patrik, Marcan, and Theo... Interesting project... OpenBSD on the M1 :) ... best of luck with it On Thu, 3 Dec 2020 at 22:11, Patrick Wildt wrote: > This really has shown how much interest there is in having OpenBSD > running on those machines. Still, we would all not be here without > the OpenBSD project itself. Not being able to host hackathons due to > COVID-19 leaves an impact, and I hope that soon(TM) we'll be able to > get back together to shut up and hack. > > I'm sure you all love using OpenBSD and hacking on OpenBSD as much as I > do, so to help OpenBSD run infrastructure, organize hackathons and to > flourish even more, please consider donating! > > https://www.openbsdfoundation.org/donations.html > https://www.openbsd.org/donations.html > > Also a shoutout to marcan, who'll be doing a lot of reverse engineering > on the M1. He's pretty good, and I'm supporting his project by being a > patron. I'm looking forward to his work, because of all the people out > there who can do it, he's definitely one of them. > > https://www.patreon.com/marcan > > Patrick > > Am Thu, Dec 03, 2020 at 02:33:34PM -0700 schrieb Ben Goren: > > Oh, wow — it hasn’t even been a full day since I sent this out...and > already enough of you have chipped in enough to buy not just a single M1 > system for Patrick, but also a second one for his partner in crime, Mark > Kettenis. > > > > Thank you to all! This show of generosity and support and excitement is > most welcome. (And, frankly, a bit overwhelming.) > > > > If anybody reading this still wishes to donate to the cause, despite the > immediate needs being met, the money will be put to good use. There are > other developers who will eventually need their own hardware, and there are > always other sorts of expenses related to development. Feel free to chip in > at Patrick’s original link: > > > > https://www.paypal.com/pools/c/8uPSkfNJMp > > > > ...or, of course, to the OpenBSD general fund (which can *ALWAYS* use > donations): > > > > https://www.openbsd.org/donations.html > > > > Thanks again, everybody! > > > > b& > > > > > On Dec 2, 2020, at 2:59 PM, Ben Goren wrote: > > > Greetings, all! > > > > > > Patrick Wildt has set up a PayPal pool to raise funds to purchase an > M1 Mac mini so he can start porting OpenBSD to the platform. If you’d like > to be able to run OpenBSD on an M1 system, now would be a great time to > throw some pennies his way. > > > > > > The donation link: https://paypal.me/pools/c/8uPSkfNJMp > > > > > > Read below for an idea of what one might expect if we can get a > machine into Patrick’s hands. > > > > > > Cheers, > > > > > > b& > > > > > > Patrick wrote: > > > > > >> Yes, kettenis@ and me are the two ones doing the major work on > porting > > >> to new devices. Not sure if kettenis@ is interested, but I can ask > him. > > >> I definitely am, a Mac Mini as a dedicated machine to do stuff with > and > > >> not care about what is installed would really help. > > >> > > >> Marcan has started a crowdfunding on Patreon. He's a really capable > > >> person, and he'll definitely lay a lot of groundwork needed for > porting > > >> OpenBSD to the platform. He apparenetly will also do his work in a > > >> dual-licensed fashion, so the BSDs will easily profit from it. > > >> > > >> So, the first steps are basically to follow Marcan's work and use all > > >> that information and code to port OpenBSD as well. > > >> > > >> This *will* take some time, because essentially there are only the > > >> binary drivers, but it's doable and I think with a bit of patience > > >> we will have OpenBSD running on the M1 as well. > > >> > > >> Biggest hurdle, as always, will be support for graphics acceleration. > > -- Kindest regards, Tom Smyth.
Re: Fwd: PayPal pool for developer M1 Mac mini for OpenBSD port
Hi Jeff, as far as Im aware... if you donate to the project they will source hardware as the project sees fit.. if there is an M1 in want.html (where a developer is looking for one to make an initial POC before the project considers it viable to spend resources... it I would be happy to contribute... for that purpose .. I dont think anyone has anything specific against apple. per sya.. there are objections to proprietary firmware... and binary blobs... and this makes development of OpenSource Systems even harder than it already is... but yes tthe M1 looks awesome it will be interesting to see if they open it up (a little) ... but it is an arm chip ... so perhaps testing and providing open arm hardware would help the project more... check out want.html all of these are my own observations as a user over the years and im not a developer in OpenBSD Thanks Tom SMyth On Thu, 3 Dec 2020 at 22:11, Jeff Joshua Rollin wrote: > > > > Forwarded Message > Subject:Fwd: PayPal pool for developer M1 Mac mini for OpenBSD port > Date: Thu, 3 Dec 2020 21:56:51 + > From: Jeff Joshua Rollin > > > > > > Oops, forgot to reply to the list. Sorry for the duplicate, Mihai. > > > On 03/12/2020 01:18, Mihai Popescu wrote: > > I have only good wishes for the project, but I still don't get one thing: > > why do some people start to behave oddly whenever Apple comes into > > discussion. > > They are doing a proprietary thing, closed as hell, no documentation > > and so > > on. Why is this impulse to write code for such a thing. Just asking ... > > Apple make great products. My iMac, which is nearly ten years old, runs > without problems even today (try that with Windows). iPads and iPhones > have much better lifetimes than Android devices - we'll see if the > increasing number of devices running "real Linux" make a dent in the > market, but either way there are AFAIK no phones using any of the BSDs > (unless you count macOS/iOS, which for these purposes I don't) anyway. > > Other than the fact that the platform is proprietary, the only other > thing that annoys me about Macs, and always has, is their half-arsed > attempt at a British keyboard, which unless it's changed since my iMac > was manufactured still puts @ and " in the wrong places for Brits - > exactly the opposite places on a US keyboard. (Even Commodore, infamous > in its day for reliability problems and which bought the Amiga company > in what no less august an institution than Amiga Format magazine called > "a rare fit of insight," managed that one.) Fortunately, if you also use > Linux/UNIX, the problem of switching between keyboards with @ and " in > 'the wrong place' is easily solved for X11 by selecting a Mac UK > keyboard in the software settings even on a PC. (They did stubbornly > stick with that crap butterfly keyboard for four years, for reasons > presumably best known to themselves, but luckily that era also seems to > be over, and I didn't bother buying one during that time, for that and > other reasons.) > > As for the proprietaryness, other than the fact that it's a nice new > hardware architecture as other people have mentioned, pretty much every > other architecture OpenBSD, NetBSD and Linux has ever run on (Amiga, Sun > and VAX, for example) is/was proprietary. And that's without considering > the closed peripherals (without which OpenBSD wouldn't have to eschew > NDAs) or the BMC on a Wintel - heaven knows what that thing really gets > up to. > > My £0.02 > > Jeff. > > -- Kindest regards, Tom Smyth.
Re: PayPal pool for developer M1 Mac mini for OpenBSD port
This really has shown how much interest there is in having OpenBSD running on those machines. Still, we would all not be here without the OpenBSD project itself. Not being able to host hackathons due to COVID-19 leaves an impact, and I hope that soon(TM) we'll be able to get back together to shut up and hack. I'm sure you all love using OpenBSD and hacking on OpenBSD as much as I do, so to help OpenBSD run infrastructure, organize hackathons and to flourish even more, please consider donating! https://www.openbsdfoundation.org/donations.html https://www.openbsd.org/donations.html Also a shoutout to marcan, who'll be doing a lot of reverse engineering on the M1. He's pretty good, and I'm supporting his project by being a patron. I'm looking forward to his work, because of all the people out there who can do it, he's definitely one of them. https://www.patreon.com/marcan Patrick Am Thu, Dec 03, 2020 at 02:33:34PM -0700 schrieb Ben Goren: > Oh, wow — it hasn’t even been a full day since I sent this out...and already > enough of you have chipped in enough to buy not just a single M1 system for > Patrick, but also a second one for his partner in crime, Mark Kettenis. > > Thank you to all! This show of generosity and support and excitement is most > welcome. (And, frankly, a bit overwhelming.) > > If anybody reading this still wishes to donate to the cause, despite the > immediate needs being met, the money will be put to good use. There are other > developers who will eventually need their own hardware, and there are always > other sorts of expenses related to development. Feel free to chip in at > Patrick’s original link: > > https://www.paypal.com/pools/c/8uPSkfNJMp > > ...or, of course, to the OpenBSD general fund (which can *ALWAYS* use > donations): > > https://www.openbsd.org/donations.html > > Thanks again, everybody! > > b& > > > On Dec 2, 2020, at 2:59 PM, Ben Goren wrote: > > Greetings, all! > > > > Patrick Wildt has set up a PayPal pool to raise funds to purchase an M1 Mac > > mini so he can start porting OpenBSD to the platform. If you’d like to be > > able to run OpenBSD on an M1 system, now would be a great time to throw > > some pennies his way. > > > > The donation link: https://paypal.me/pools/c/8uPSkfNJMp > > > > Read below for an idea of what one might expect if we can get a machine > > into Patrick’s hands. > > > > Cheers, > > > > b& > > > > Patrick wrote: > > > >> Yes, kettenis@ and me are the two ones doing the major work on porting > >> to new devices. Not sure if kettenis@ is interested, but I can ask him. > >> I definitely am, a Mac Mini as a dedicated machine to do stuff with and > >> not care about what is installed would really help. > >> > >> Marcan has started a crowdfunding on Patreon. He's a really capable > >> person, and he'll definitely lay a lot of groundwork needed for porting > >> OpenBSD to the platform. He apparenetly will also do his work in a > >> dual-licensed fashion, so the BSDs will easily profit from it. > >> > >> So, the first steps are basically to follow Marcan's work and use all > >> that information and code to port OpenBSD as well. > >> > >> This *will* take some time, because essentially there are only the > >> binary drivers, but it's doable and I think with a bit of patience > >> we will have OpenBSD running on the M1 as well. > >> > >> Biggest hurdle, as always, will be support for graphics acceleration.
Fwd: Fwd: PayPal pool for developer M1 Mac mini for OpenBSD port
Forwarded Message Subject:Fwd: PayPal pool for developer M1 Mac mini for OpenBSD port Date: Thu, 3 Dec 2020 21:56:51 + From: Jeff Joshua Rollin Oops, forgot to reply to the list. Sorry for the duplicate, Mihai. On 03/12/2020 01:18, Mihai Popescu wrote: I have only good wishes for the project, but I still don't get one thing: why do some people start to behave oddly whenever Apple comes into discussion. They are doing a proprietary thing, closed as hell, no documentation and so on. Why is this impulse to write code for such a thing. Just asking ... Apple make great products. My iMac, which is nearly ten years old, runs without problems even today (try that with Windows). iPads and iPhones have much better lifetimes than Android devices - we'll see if the increasing number of devices running "real Linux" make a dent in the market, but either way there are AFAIK no phones using any of the BSDs (unless you count macOS/iOS, which for these purposes I don't) anyway. Other than the fact that the platform is proprietary, the only other thing that annoys me about Macs, and always has, is their half-arsed attempt at a British keyboard, which unless it's changed since my iMac was manufactured still puts @ and " in the wrong places for Brits - exactly the opposite places on a US keyboard. (Even Commodore, infamous in its day for reliability problems and which bought the Amiga company in what no less august an institution than Amiga Format magazine called "a rare fit of insight," managed that one.) Fortunately, if you also use Linux/UNIX, the problem of switching between keyboards with @ and " in 'the wrong place' is easily solved for X11 by selecting a Mac UK keyboard in the software settings even on a PC. (They did stubbornly stick with that crap butterfly keyboard for four years, for reasons presumably best known to themselves, but luckily that era also seems to be over, and I didn't bother buying one during that time, for that and other reasons.) As for the proprietaryness, other than the fact that it's a nice new hardware architecture as other people have mentioned, pretty much every other architecture OpenBSD, NetBSD and Linux has ever run on (Amiga, Sun and VAX, for example) is/was proprietary. And that's without considering the closed peripherals (without which OpenBSD wouldn't have to eschew NDAs) or the BMC on a Wintel - heaven knows what that thing really gets up to. My £0.02 Jeff.
Re: PayPal pool for developer M1 Mac mini for OpenBSD port
Oh, wow — it hasn’t even been a full day since I sent this out...and already enough of you have chipped in enough to buy not just a single M1 system for Patrick, but also a second one for his partner in crime, Mark Kettenis. Thank you to all! This show of generosity and support and excitement is most welcome. (And, frankly, a bit overwhelming.) If anybody reading this still wishes to donate to the cause, despite the immediate needs being met, the money will be put to good use. There are other developers who will eventually need their own hardware, and there are always other sorts of expenses related to development. Feel free to chip in at Patrick’s original link: https://www.paypal.com/pools/c/8uPSkfNJMp ...or, of course, to the OpenBSD general fund (which can *ALWAYS* use donations): https://www.openbsd.org/donations.html Thanks again, everybody! b& > On Dec 2, 2020, at 2:59 PM, Ben Goren wrote: > Greetings, all! > > Patrick Wildt has set up a PayPal pool to raise funds to purchase an M1 Mac > mini so he can start porting OpenBSD to the platform. If you’d like to be > able to run OpenBSD on an M1 system, now would be a great time to throw some > pennies his way. > > The donation link: https://paypal.me/pools/c/8uPSkfNJMp > > Read below for an idea of what one might expect if we can get a machine into > Patrick’s hands. > > Cheers, > > b& > > Patrick wrote: > >> Yes, kettenis@ and me are the two ones doing the major work on porting >> to new devices. Not sure if kettenis@ is interested, but I can ask him. >> I definitely am, a Mac Mini as a dedicated machine to do stuff with and >> not care about what is installed would really help. >> >> Marcan has started a crowdfunding on Patreon. He's a really capable >> person, and he'll definitely lay a lot of groundwork needed for porting >> OpenBSD to the platform. He apparenetly will also do his work in a >> dual-licensed fashion, so the BSDs will easily profit from it. >> >> So, the first steps are basically to follow Marcan's work and use all >> that information and code to port OpenBSD as well. >> >> This *will* take some time, because essentially there are only the >> binary drivers, but it's doable and I think with a bit of patience >> we will have OpenBSD running on the M1 as well. >> >> Biggest hurdle, as always, will be support for graphics acceleration.
Re: PayPal pool for developer M1 Mac mini for OpenBSD port
Op do 3 dec. 2020 om 11:28 schreef Stuart Henderson : > > On 2020-12-03, Janne Johansson wrote: > > Den tors 3 dec. 2020 kl 02:21 skrev Mihai Popescu : > > > >> I have only good wishes for the project, but I still don't get one thing: > >> why do some people start to behave oddly whenever Apple comes into > >> discussion. > >> > > > > It could also be that if it becomes operable, it is quite a useful machine, > > whereas sticking to Pine64 experiment boards and FruityPi clones does quite > > limit the usefulness even if they are all aarch64s. > > That, plus it's a challenge. Some people do sudoku or cryptic crosswords, > some play musical instruments, some port OS to new hardware. And some do > several of the above (and more). We as community could help to make that possible, I'm wondering how many machines would be needed to make it work. -- “We spend the first twelve months of our children's lives teaching them to walk and talk and the next twelve telling them to sit down and shut up.”
Re: PayPal pool for developer M1 Mac mini for OpenBSD port
All right, let me do it. god damn. Caipenghui 于 2020年12月3日 GMT+08:00 下午6:26:24, Stuart Henderson 写到: >On 2020-12-03, Janne Johansson wrote: >> Den tors 3 dec. 2020 kl 02:21 skrev Mihai Popescu : >> >>> I have only good wishes for the project, but I still don't get one >thing: >>> why do some people start to behave oddly whenever Apple comes into >>> discussion. >>> >> >> It could also be that if it becomes operable, it is quite a useful >machine, >> whereas sticking to Pine64 experiment boards and FruityPi clones does >quite >> limit the usefulness even if they are all aarch64s. > >That, plus it's a challenge. Some people do sudoku or cryptic >crosswords, >some play musical instruments, some port OS to new hardware. And some >do >several of the above (and more).
Re: PayPal pool for developer M1 Mac mini for OpenBSD port
On 2020-12-03, Janne Johansson wrote: > Den tors 3 dec. 2020 kl 02:21 skrev Mihai Popescu : > >> I have only good wishes for the project, but I still don't get one thing: >> why do some people start to behave oddly whenever Apple comes into >> discussion. >> > > It could also be that if it becomes operable, it is quite a useful machine, > whereas sticking to Pine64 experiment boards and FruityPi clones does quite > limit the usefulness even if they are all aarch64s. That, plus it's a challenge. Some people do sudoku or cryptic crosswords, some play musical instruments, some port OS to new hardware. And some do several of the above (and more).
Re: PayPal pool for developer M1 Mac mini for OpenBSD port
Den tors 3 dec. 2020 kl 02:21 skrev Mihai Popescu : > I have only good wishes for the project, but I still don't get one thing: > why do some people start to behave oddly whenever Apple comes into > discussion. > It could also be that if it becomes operable, it is quite a useful machine, whereas sticking to Pine64 experiment boards and FruityPi clones does quite limit the usefulness even if they are all aarch64s. -- May the most significant bit of your life be positive.
Re: PayPal pool for developer M1 Mac mini for OpenBSD port
On Thu, Dec 03, 2020 at 03:18:54AM +0200, Mihai Popescu wrote: > I have only good wishes for the project, but I still don't get one thing: > why do some people start to behave oddly whenever Apple comes into > discussion. > They are doing a proprietary thing, closed as hell, no documentation and so > on. Why is this impulse to write code for such a thing. Just asking ... It's a new interesting ARM platform with very good performance. Yes, it is closed but it's also kind of a nice challenge to overcome that hurdle. So mixed feelings about that part. -Otto
Re: PayPal pool for developer M1 Mac mini for OpenBSD port
I think it's going to start all over again, transplanting takes a lot of time, and there are too many unknowns. Caipenghui 于 2020年12月3日 GMT+08:00 上午9:18:54, Mihai Popescu 写到: >I have only good wishes for the project, but I still don't get one >thing: >why do some people start to behave oddly whenever Apple comes into >discussion. >They are doing a proprietary thing, closed as hell, no documentation >and so >on. Why is this impulse to write code for such a thing. Just asking ...
Re: PayPal pool for developer M1 Mac mini for OpenBSD port
I have only good wishes for the project, but I still don't get one thing: why do some people start to behave oddly whenever Apple comes into discussion. They are doing a proprietary thing, closed as hell, no documentation and so on. Why is this impulse to write code for such a thing. Just asking ...
PayPal pool for developer M1 Mac mini for OpenBSD port
Greetings, all! Patrick Wildt has set up a PayPal pool to raise funds to purchase an M1 Mac mini so he can start porting OpenBSD to the platform. If you’d like to be able to run OpenBSD on an M1 system, now would be a great time to throw some pennies his way. The donation link: https://paypal.me/pools/c/8uPSkfNJMp Read below for an idea of what one might expect if we can get a machine into Patrick’s hands. Cheers, b& Patrick wrote: > Yes, kettenis@ and me are the two ones doing the major work on porting > to new devices. Not sure if kettenis@ is interested, but I can ask him. > I definitely am, a Mac Mini as a dedicated machine to do stuff with and > not care about what is installed would really help. > > Marcan has started a crowdfunding on Patreon. He's a really capable > person, and he'll definitely lay a lot of groundwork needed for porting > OpenBSD to the platform. He apparenetly will also do his work in a > dual-licensed fashion, so the BSDs will easily profit from it. > > So, the first steps are basically to follow Marcan's work and use all > that information and code to port OpenBSD as well. > > This *will* take some time, because essentially there are only the > binary drivers, but it's doable and I think with a bit of patience > we will have OpenBSD running on the M1 as well. > > Biggest hurdle, as always, will be support for graphics acceleration.
Re: Bootloader failing to install on 2012 Mac Mini (Openbsd 6.4)
The same issue occurred using a separate usb with a toshiba C55D and with a cd on a home built tower. At this point I'm just so confused at why it's fine installing to a usb but not a clean disk on not one but four different disk/computer configurations with varying Openbsd versions and install media. I installed 6.3 fine on my old efi xps but since the issue with the Mac Mini everything I've tried has failed to install to the disk and the old guides for making an efi partition fail in the same way, only coping the efi partition from a usb with Openbsd installed works. I thought I'd just quickly write a small guide on how I did it in case anyone has the same issue: 1. Install OpenBSD to a separate USB stick 2. dd the usb onto the hard drive 3. As all my USB's were 8gb ones the auto partitions were smaller and fewer, instead of mucking around expanding I found that I could now install Openbsd to the internal hard drive in the Openbsd portion of the disk (ie not choosing gpt as that would overwrite the whole disk) thus keeping the functioning efi parition in place. It's not the cleanest way to install but as I said, 4 failures in the same way with different configs and different images and versions and it seems that no one online has had the same issue ever before, or hasn't posted about it, so I'm stumped but happy that I have a method that works. On Sun, Nov 25, 2018 at 6:00 PM Liam Wigney wrote: > In case anyone is still following or is interested: Installing to my HP > stream 11 failed in the exact same way. Using the same workaround worked. > > On Sat, Oct 27, 2018 at 8:09 PM Liam Wigney wrote: > >> Thank you so much! >> >> So I dd'd using the raw devices for both the usb and the mac mini. It >> worked which is sweet, unfortunately due to the usb being only 4gb it >> didn't partition it in the normal Openbsd way, only / /home and /usr, but I >> have a bigger usb which should be able to get the normal partition >> treatment and copy that one across. >> >> At this point as annoying as it is that it won't just install normally, >> it's working, but for the sake of others I'd like to eventually work out >> how to fix the issue. >> >> I'm not sure where to look but I might have a bit of a look over how >> mkdir is being called as to why the argument invalid error is happening. >> >> But one again thank's so much for you and Phillip taking time out of your >> days to help. >> >> >> >> >> On Sat, Oct 27, 2018 at 6:55 PM snikolov wrote: >> >>> Now can you try to dd your USB stick from a Linux Live CD onto your >>> local drive and then try to boot. My guess is that there is some >>> UEFI/openBSD incompatibility. >>> In our case (U)EFI is representing the storage to the kernel and most >>> probably that is not OK. >>> Still, if you manage to boot from the drive (after a complete 'dd) , >>> then we should know that at least a workaround is possible. >>> >>> Strahil >>> >>> >>> >>> On Sat, 2018-10-27 at 18:42 +1030, Liam Wigney wrote: >>> > Hey Strahil, >>> > >>> > Just tried to install to a usb and it installed fine, an efi install >>> > at >>> > that, and it runs fine when booting. So it's something to do with >>> > installing onto the internal drive. But that makes little sense since >>> > I >>> > reformatted the internal hard drive to make sure it was like as new >>> > so I >>> > don't get why Openbsd is acting differently. >>> > >>> > On Sat, Oct 27, 2018 at 6:54 AM snikolov >>> > wrote: >>> > >>> > > Hi, >>> > > >>> > > have you tried to install openBSD on a USB stick (installer run on >>> > > another machine) and then boot from that USB stick ? >>> > > It will be interesting to find out what happens then. >>> > > >>> > > Best Regards, >>> > > Strahil >>> > > >>> > > On Fri, 2018-10-26 at 16:05 +1030, Liam Wigney wrote: >>> > > > Summery + update: >>> > > > >>> > > > So I thought I'd post one final update for the time being, it's >>> > > > been >>> > > > a long >>> > > > two day's reading man pages and looking though mailing >>> > > > lists/forums/reddit >>> > > > posts, and summary of where I'm at in case anyone in the future >>> > > > wants >>> > > > help. >>> > > > I'll >>> > > > >>> >
Re: Bootloader failing to install on 2012 Mac Mini (Openbsd 6.4)
In case anyone is still following or is interested: Installing to my HP
stream 11 failed in the exact same way. Using the same workaround worked.
On Sat, Oct 27, 2018 at 8:09 PM Liam Wigney wrote:
> Thank you so much!
>
> So I dd'd using the raw devices for both the usb and the mac mini. It
> worked which is sweet, unfortunately due to the usb being only 4gb it
> didn't partition it in the normal Openbsd way, only / /home and /usr, but I
> have a bigger usb which should be able to get the normal partition
> treatment and copy that one across.
>
> At this point as annoying as it is that it won't just install normally,
> it's working, but for the sake of others I'd like to eventually work out
> how to fix the issue.
>
> I'm not sure where to look but I might have a bit of a look over how mkdir
> is being called as to why the argument invalid error is happening.
>
> But one again thank's so much for you and Phillip taking time out of your
> days to help.
>
>
>
>
> On Sat, Oct 27, 2018 at 6:55 PM snikolov wrote:
>
>> Now can you try to dd your USB stick from a Linux Live CD onto your
>> local drive and then try to boot. My guess is that there is some
>> UEFI/openBSD incompatibility.
>> In our case (U)EFI is representing the storage to the kernel and most
>> probably that is not OK.
>> Still, if you manage to boot from the drive (after a complete 'dd) ,
>> then we should know that at least a workaround is possible.
>>
>> Strahil
>>
>>
>>
>> On Sat, 2018-10-27 at 18:42 +1030, Liam Wigney wrote:
>> > Hey Strahil,
>> >
>> > Just tried to install to a usb and it installed fine, an efi install
>> > at
>> > that, and it runs fine when booting. So it's something to do with
>> > installing onto the internal drive. But that makes little sense since
>> > I
>> > reformatted the internal hard drive to make sure it was like as new
>> > so I
>> > don't get why Openbsd is acting differently.
>> >
>> > On Sat, Oct 27, 2018 at 6:54 AM snikolov
>> > wrote:
>> >
>> > > Hi,
>> > >
>> > > have you tried to install openBSD on a USB stick (installer run on
>> > > another machine) and then boot from that USB stick ?
>> > > It will be interesting to find out what happens then.
>> > >
>> > > Best Regards,
>> > > Strahil
>> > >
>> > > On Fri, 2018-10-26 at 16:05 +1030, Liam Wigney wrote:
>> > > > Summery + update:
>> > > >
>> > > > So I thought I'd post one final update for the time being, it's
>> > > > been
>> > > > a long
>> > > > two day's reading man pages and looking though mailing
>> > > > lists/forums/reddit
>> > > > posts, and summary of where I'm at in case anyone in the future
>> > > > wants
>> > > > help.
>> > > > I'll
>> > > >
>> > > > Firstly, no matter how I try to install I still get the "
>> > > > installboot: mkdir('/tmp/installboot.hP11Q78IbS/efi') failed:
>> > > > Invalid
>> > > > argument" error but with different gibberish.
>> > > >
>> > > > Secondly there's a reddit thread with some info and discussion at
>> > > > https://www.reddit.com/r/openbsd/comments/9qllyy/bootloader_faili
>> > > > ng_t
>> > > > o_install_on_2012_mac_mini/
>> > > >
>> > > > Finally here's where I'm at:
>> > > >
>> > > > Openbsd documentation for (u)efi is highly lacking however in
>> > > > this
>> > > > case
>> > > > it's hard to say how helpful it would have been. I've only ever
>> > > > used
>> > > > openbsd with legacy boot on however mac's don't have the option
>> > > > to do
>> > > > so.
>> > > > When pressing the key combo for the boot menu of the mac I see
>> > > > two
>> > > > options.
>> > > > One named "windows" and one named "efi boot".
>> > > > They both boot into the openbsd installer but with several
>> > > > differences.
>> > > >
>> > > > The "windows" option boots into a full screen installer. With
>> > > > this
>> > > > boot
>> > > > option wd0 is the root disk and sd0 is the usb. Upon running
>> > > > dmesg |
>> > > > grep
>&g
Re: Bootloader failing to install on 2012 Mac Mini (Openbsd 6.4)
Thank you so much!
So I dd'd using the raw devices for both the usb and the mac mini. It
worked which is sweet, unfortunately due to the usb being only 4gb it
didn't partition it in the normal Openbsd way, only / /home and /usr, but I
have a bigger usb which should be able to get the normal partition
treatment and copy that one across.
At this point as annoying as it is that it won't just install normally,
it's working, but for the sake of others I'd like to eventually work out
how to fix the issue.
I'm not sure where to look but I might have a bit of a look over how mkdir
is being called as to why the argument invalid error is happening.
But one again thank's so much for you and Phillip taking time out of your
days to help.
On Sat, Oct 27, 2018 at 6:55 PM snikolov wrote:
> Now can you try to dd your USB stick from a Linux Live CD onto your
> local drive and then try to boot. My guess is that there is some
> UEFI/openBSD incompatibility.
> In our case (U)EFI is representing the storage to the kernel and most
> probably that is not OK.
> Still, if you manage to boot from the drive (after a complete 'dd) ,
> then we should know that at least a workaround is possible.
>
> Strahil
>
>
>
> On Sat, 2018-10-27 at 18:42 +1030, Liam Wigney wrote:
> > Hey Strahil,
> >
> > Just tried to install to a usb and it installed fine, an efi install
> > at
> > that, and it runs fine when booting. So it's something to do with
> > installing onto the internal drive. But that makes little sense since
> > I
> > reformatted the internal hard drive to make sure it was like as new
> > so I
> > don't get why Openbsd is acting differently.
> >
> > On Sat, Oct 27, 2018 at 6:54 AM snikolov
> > wrote:
> >
> > > Hi,
> > >
> > > have you tried to install openBSD on a USB stick (installer run on
> > > another machine) and then boot from that USB stick ?
> > > It will be interesting to find out what happens then.
> > >
> > > Best Regards,
> > > Strahil
> > >
> > > On Fri, 2018-10-26 at 16:05 +1030, Liam Wigney wrote:
> > > > Summery + update:
> > > >
> > > > So I thought I'd post one final update for the time being, it's
> > > > been
> > > > a long
> > > > two day's reading man pages and looking though mailing
> > > > lists/forums/reddit
> > > > posts, and summary of where I'm at in case anyone in the future
> > > > wants
> > > > help.
> > > > I'll
> > > >
> > > > Firstly, no matter how I try to install I still get the "
> > > > installboot: mkdir('/tmp/installboot.hP11Q78IbS/efi') failed:
> > > > Invalid
> > > > argument" error but with different gibberish.
> > > >
> > > > Secondly there's a reddit thread with some info and discussion at
> > > > https://www.reddit.com/r/openbsd/comments/9qllyy/bootloader_faili
> > > > ng_t
> > > > o_install_on_2012_mac_mini/
> > > >
> > > > Finally here's where I'm at:
> > > >
> > > > Openbsd documentation for (u)efi is highly lacking however in
> > > > this
> > > > case
> > > > it's hard to say how helpful it would have been. I've only ever
> > > > used
> > > > openbsd with legacy boot on however mac's don't have the option
> > > > to do
> > > > so.
> > > > When pressing the key combo for the boot menu of the mac I see
> > > > two
> > > > options.
> > > > One named "windows" and one named "efi boot".
> > > > They both boot into the openbsd installer but with several
> > > > differences.
> > > >
> > > > The "windows" option boots into a full screen installer. With
> > > > this
> > > > boot
> > > > option wd0 is the root disk and sd0 is the usb. Upon running
> > > > dmesg |
> > > > grep
> > > > efi to confirm that efi is noticed shows that's it's not. An
> > > > attempt
> > > > to
> > > > install with either gpt or mbr fails with the invalid argument
> > > > error.
> > > > The
> > > > "efi" boot option boots with the installer taking up the center
> > > > of
> > > > the
> > > > screen, in this boot option sd0 is root and sd1 is the usb, it
> > > > does
> > > > however
> > > > notice that the mac mini is an efi system. It &q
Re: Bootloader failing to install on 2012 Mac Mini (Openbsd 6.4)
Now can you try to dd your USB stick from a Linux Live CD onto your
local drive and then try to boot. My guess is that there is some
UEFI/openBSD incompatibility.
In our case (U)EFI is representing the storage to the kernel and most
probably that is not OK.
Still, if you manage to boot from the drive (after a complete 'dd) ,
then we should know that at least a workaround is possible.
Strahil
On Sat, 2018-10-27 at 18:42 +1030, Liam Wigney wrote:
> Hey Strahil,
>
> Just tried to install to a usb and it installed fine, an efi install
> at
> that, and it runs fine when booting. So it's something to do with
> installing onto the internal drive. But that makes little sense since
> I
> reformatted the internal hard drive to make sure it was like as new
> so I
> don't get why Openbsd is acting differently.
>
> On Sat, Oct 27, 2018 at 6:54 AM snikolov
> wrote:
>
> > Hi,
> >
> > have you tried to install openBSD on a USB stick (installer run on
> > another machine) and then boot from that USB stick ?
> > It will be interesting to find out what happens then.
> >
> > Best Regards,
> > Strahil
> >
> > On Fri, 2018-10-26 at 16:05 +1030, Liam Wigney wrote:
> > > Summery + update:
> > >
> > > So I thought I'd post one final update for the time being, it's
> > > been
> > > a long
> > > two day's reading man pages and looking though mailing
> > > lists/forums/reddit
> > > posts, and summary of where I'm at in case anyone in the future
> > > wants
> > > help.
> > > I'll
> > >
> > > Firstly, no matter how I try to install I still get the "
> > > installboot: mkdir('/tmp/installboot.hP11Q78IbS/efi') failed:
> > > Invalid
> > > argument" error but with different gibberish.
> > >
> > > Secondly there's a reddit thread with some info and discussion at
> > > https://www.reddit.com/r/openbsd/comments/9qllyy/bootloader_faili
> > > ng_t
> > > o_install_on_2012_mac_mini/
> > >
> > > Finally here's where I'm at:
> > >
> > > Openbsd documentation for (u)efi is highly lacking however in
> > > this
> > > case
> > > it's hard to say how helpful it would have been. I've only ever
> > > used
> > > openbsd with legacy boot on however mac's don't have the option
> > > to do
> > > so.
> > > When pressing the key combo for the boot menu of the mac I see
> > > two
> > > options.
> > > One named "windows" and one named "efi boot".
> > > They both boot into the openbsd installer but with several
> > > differences.
> > >
> > > The "windows" option boots into a full screen installer. With
> > > this
> > > boot
> > > option wd0 is the root disk and sd0 is the usb. Upon running
> > > dmesg |
> > > grep
> > > efi to confirm that efi is noticed shows that's it's not. An
> > > attempt
> > > to
> > > install with either gpt or mbr fails with the invalid argument
> > > error.
> > > The
> > > "efi" boot option boots with the installer taking up the center
> > > of
> > > the
> > > screen, in this boot option sd0 is root and sd1 is the usb, it
> > > does
> > > however
> > > notice that the mac mini is an efi system. It "usually" (Because
> > > I've
> > > tried
> > > a few times and noticed that sometimes it doesn't) creates the
> > > efi
> > > partition and then the regular openbsd partition. However
> > > regardless
> > > of
> > > which option is chosen the error still occurs.
> > >
> > >
> > > I've tested openbsd 6.3 and a snapshot and it fails in the exact
> > > same
> > > way.
> > > Sorry again if I've left anything out or missed anything.
> > >
> > > On Thu, Oct 25, 2018 at 4:43 PM Liam Wigney
> > > wrote:
> > >
> > > > Update:
> > > >
> > > > I noticed upon selecting the boot menu there were two ways to
> > > > boot
> > > > the usb
> > > > in the Mac's efi, I selected the one labled "windows". The
> > > > computer
> > > > has
> > > > never had windows installed and it's for booting the usb but I
> > > > never saw
> > > > anything noting that this would happen. I selected it and
> > > > instantly
> > > > the
> > > > ins
Re: Bootloader failing to install on 2012 Mac Mini (Openbsd 6.4)
Hey Strahil,
Just tried to install to a usb and it installed fine, an efi install at
that, and it runs fine when booting. So it's something to do with
installing onto the internal drive. But that makes little sense since I
reformatted the internal hard drive to make sure it was like as new so I
don't get why Openbsd is acting differently.
On Sat, Oct 27, 2018 at 6:54 AM snikolov wrote:
> Hi,
>
> have you tried to install openBSD on a USB stick (installer run on
> another machine) and then boot from that USB stick ?
> It will be interesting to find out what happens then.
>
> Best Regards,
> Strahil
>
> On Fri, 2018-10-26 at 16:05 +1030, Liam Wigney wrote:
> > Summery + update:
> >
> > So I thought I'd post one final update for the time being, it's been
> > a long
> > two day's reading man pages and looking though mailing
> > lists/forums/reddit
> > posts, and summary of where I'm at in case anyone in the future wants
> > help.
> > I'll
> >
> > Firstly, no matter how I try to install I still get the "
> > installboot: mkdir('/tmp/installboot.hP11Q78IbS/efi') failed: Invalid
> > argument" error but with different gibberish.
> >
> > Secondly there's a reddit thread with some info and discussion at
> > https://www.reddit.com/r/openbsd/comments/9qllyy/bootloader_failing_t
> > o_install_on_2012_mac_mini/
> >
> > Finally here's where I'm at:
> >
> > Openbsd documentation for (u)efi is highly lacking however in this
> > case
> > it's hard to say how helpful it would have been. I've only ever used
> > openbsd with legacy boot on however mac's don't have the option to do
> > so.
> > When pressing the key combo for the boot menu of the mac I see two
> > options.
> > One named "windows" and one named "efi boot".
> > They both boot into the openbsd installer but with several
> > differences.
> >
> > The "windows" option boots into a full screen installer. With this
> > boot
> > option wd0 is the root disk and sd0 is the usb. Upon running dmesg |
> > grep
> > efi to confirm that efi is noticed shows that's it's not. An attempt
> > to
> > install with either gpt or mbr fails with the invalid argument error.
> > The
> > "efi" boot option boots with the installer taking up the center of
> > the
> > screen, in this boot option sd0 is root and sd1 is the usb, it does
> > however
> > notice that the mac mini is an efi system. It "usually" (Because I've
> > tried
> > a few times and noticed that sometimes it doesn't) creates the efi
> > partition and then the regular openbsd partition. However regardless
> > of
> > which option is chosen the error still occurs.
> >
> >
> > I've tested openbsd 6.3 and a snapshot and it fails in the exact same
> > way.
> > Sorry again if I've left anything out or missed anything.
> >
> > On Thu, Oct 25, 2018 at 4:43 PM Liam Wigney
> > wrote:
> >
> > > Update:
> > >
> > > I noticed upon selecting the boot menu there were two ways to boot
> > > the usb
> > > in the Mac's efi, I selected the one labled "windows". The computer
> > > has
> > > never had windows installed and it's for booting the usb but I
> > > never saw
> > > anything noting that this would happen. I selected it and instantly
> > > the
> > > installer takes up the whole monitor as opposed to just being small
> > > and
> > > centred. It also, when selecting the default gpt full disk
> > > configuration,
> > > auto-made a EFI partition. However the install failed with the
> > > exact same
> > > error but with new numbers and letters after "installboot.".
> > >
> > > Maybe this is booting the usb with efi and previously it wasn't?
> > > Regardless, it's still not working. I might try 6.3 and a snapshot
> > > to see
> > > if it's just an issue with 6.4.
> > >
> > >
> > > On Wed, Oct 24, 2018 at 2:18 PM Liam Wigney
> > > wrote:
> > >
> > > > Thanks for the reply, I actually tried the install again after
> > > > wiping the
> > > > disk and noticed that it seems like and efi partition wasn't
> > > > auto-created
> > > > as part of the partitioning which seems odd since I swear it
> > > > usually is for
> > > > efi systems but then again maybe I just don't remember.
> > > > Install.txt doesn't
> > > > mention needing to create one e
Re: Bootloader failing to install on 2012 Mac Mini (Openbsd 6.4)
Summery + update:
So I thought I'd post one final update for the time being, it's been a long
two day's reading man pages and looking though mailing lists/forums/reddit
posts, and summary of where I'm at in case anyone in the future wants help.
I'll
Firstly, no matter how I try to install I still get the "
installboot: mkdir('/tmp/installboot.hP11Q78IbS/efi') failed: Invalid
argument" error but with different gibberish.
Secondly there's a reddit thread with some info and discussion at
https://www.reddit.com/r/openbsd/comments/9qllyy/bootloader_failing_to_install_on_2012_mac_mini/
Finally here's where I'm at:
Openbsd documentation for (u)efi is highly lacking however in this case
it's hard to say how helpful it would have been. I've only ever used
openbsd with legacy boot on however mac's don't have the option to do so.
When pressing the key combo for the boot menu of the mac I see two options.
One named "windows" and one named "efi boot".
They both boot into the openbsd installer but with several differences.
The "windows" option boots into a full screen installer. With this boot
option wd0 is the root disk and sd0 is the usb. Upon running dmesg | grep
efi to confirm that efi is noticed shows that's it's not. An attempt to
install with either gpt or mbr fails with the invalid argument error. The
"efi" boot option boots with the installer taking up the center of the
screen, in this boot option sd0 is root and sd1 is the usb, it does however
notice that the mac mini is an efi system. It "usually" (Because I've tried
a few times and noticed that sometimes it doesn't) creates the efi
partition and then the regular openbsd partition. However regardless of
which option is chosen the error still occurs.
I've tested openbsd 6.3 and a snapshot and it fails in the exact same way.
Sorry again if I've left anything out or missed anything.
On Thu, Oct 25, 2018 at 4:43 PM Liam Wigney wrote:
> Update:
>
> I noticed upon selecting the boot menu there were two ways to boot the usb
> in the Mac's efi, I selected the one labled "windows". The computer has
> never had windows installed and it's for booting the usb but I never saw
> anything noting that this would happen. I selected it and instantly the
> installer takes up the whole monitor as opposed to just being small and
> centred. It also, when selecting the default gpt full disk configuration,
> auto-made a EFI partition. However the install failed with the exact same
> error but with new numbers and letters after "installboot.".
>
> Maybe this is booting the usb with efi and previously it wasn't?
> Regardless, it's still not working. I might try 6.3 and a snapshot to see
> if it's just an issue with 6.4.
>
>
> On Wed, Oct 24, 2018 at 2:18 PM Liam Wigney wrote:
>
>> Thanks for the reply, I actually tried the install again after wiping the
>> disk and noticed that it seems like and efi partition wasn't auto-created
>> as part of the partitioning which seems odd since I swear it usually is for
>> efi systems but then again maybe I just don't remember. Install.txt doesn't
>> mention needing to create one even though one old guide I saw did as part
>> of the procedure. The previous efi partition I noticed when playing around
>> before wiping the disk must have been from the old Linux install.
>> Regardless the error is identical almost to the previous one but with new
>> numbers and letters after the ".".
>>
>> The exact and full error message is as follows:
>>
>> installboot: mkdir('/tmp/installboot.hP11Q78IbS/efi') failed: Invalid
>> argument
>>
>> Failed to install bootlocks.
>> You will not be able to book OpenBSD from sd0.
>>
>>
>> The output of df -k (Sorry about the formatting, I tried to replicate it
>> as best I could):
>>
>> Filesystem 1K-blocks Used AvailCapacity Mounted on
>> /dev/rd0a3535 5256279 92%/
>> /dev/sd0a 102887869194 908242 7% /mnt
>> /dev/sd0l 312080952 36 296476872 0%/mnt/home
>> /dev/sd0d 4125406 2 3919134 0% /mnt/tmp
>> /dev/sd0f2061054 577930 1380072 30% /mnt/usr
>> /dev/sd0g 1028878190628 786808 20% /mnt/usr/X11R6
>> /dev/sd0h 20636942 218 19604878 0% /mnt/usr/local
>> /dev/sd0k 6189758 2 58802700% /mnt/usr/obj
>> /dev/sd0j2061054 2 19580000% /mnt/usr/src
>> /dev/sd0e 20425598 3394 19400926 0% /mnt/var
>>
>> On Wed, Oct 24, 2018 at 1:51 PM Philip Guenther
>> wrote:
>>
>>> On Tue, Oct 23, 2018 at 4:38 PM Liam Wigney wrote:
>&
Re: Bootloader failing to install on 2012 Mac Mini (Openbsd 6.4)
Update:
I noticed upon selecting the boot menu there were two ways to boot the usb
in the Mac's efi, I selected the one labled "windows". The computer has
never had windows installed and it's for booting the usb but I never saw
anything noting that this would happen. I selected it and instantly the
installer takes up the whole monitor as opposed to just being small and
centred. It also, when selecting the default gpt full disk configuration,
auto-made a EFI partition. However the install failed with the exact same
error but with new numbers and letters after "installboot.".
Maybe this is booting the usb with efi and previously it wasn't?
Regardless, it's still not working. I might try 6.3 and a snapshot to see
if it's just an issue with 6.4.
On Wed, Oct 24, 2018 at 2:18 PM Liam Wigney wrote:
> Thanks for the reply, I actually tried the install again after wiping the
> disk and noticed that it seems like and efi partition wasn't auto-created
> as part of the partitioning which seems odd since I swear it usually is for
> efi systems but then again maybe I just don't remember. Install.txt doesn't
> mention needing to create one even though one old guide I saw did as part
> of the procedure. The previous efi partition I noticed when playing around
> before wiping the disk must have been from the old Linux install.
> Regardless the error is identical almost to the previous one but with new
> numbers and letters after the ".".
>
> The exact and full error message is as follows:
>
> installboot: mkdir('/tmp/installboot.hP11Q78IbS/efi') failed: Invalid
> argument
>
> Failed to install bootlocks.
> You will not be able to book OpenBSD from sd0.
>
>
> The output of df -k (Sorry about the formatting, I tried to replicate it
> as best I could):
>
> Filesystem 1K-blocks Used AvailCapacity Mounted on
> /dev/rd0a3535 5256279 92%/
> /dev/sd0a 102887869194 908242 7% /mnt
> /dev/sd0l 312080952 36 296476872 0%/mnt/home
> /dev/sd0d 4125406 2 3919134 0% /mnt/tmp
> /dev/sd0f2061054 577930 1380072 30% /mnt/usr
> /dev/sd0g 1028878190628 786808 20% /mnt/usr/X11R6
> /dev/sd0h 20636942 218 19604878 0% /mnt/usr/local
> /dev/sd0k 6189758 2 58802700% /mnt/usr/obj
> /dev/sd0j2061054 2 19580000% /mnt/usr/src
> /dev/sd0e 20425598 3394 19400926 0% /mnt/var
>
> On Wed, Oct 24, 2018 at 1:51 PM Philip Guenther
> wrote:
>
>> On Tue, Oct 23, 2018 at 4:38 PM Liam Wigney wrote:
>>
>>> I've used Openbsd before but my installs have gone smoothly with no
>>> issues
>>> and this is really the first time it's been a problem. The install is a
>>> super boring one, it's whole disk Openbsd with the default gpt partition
>>> layout and nothing else special.
>>>
>>> During the install after the sets are successfully installed there's a
>>> notification that the bootloader has failed to install due to mkdir being
>>> called with an invalid argument.
>>
>>
>> All the error messages from installboot from mkdir failing include both
>> the path and the specific error message. Those are included because
>> they're helpful in understanding exactly what failed (and thus what could
>> be wrong). Including the _exact_ and _full_ error message would make it
>> easier to assist.
>>
>> (Ruling out stuff that _didn't_ fail is key to figuring out root causes.)
>>
>>
>>
>>> Some research online said that I should
>>> try to do installboot manually in the subsequent prrompt, so I called
>>> installboot sd0 and got the following error
>>>
>>> installboot: /usr/mdec/biosboot: No such file or directory
>>>
>>
>> Yes, when running from the bsd.rd ramdisk additional argument are
>> necessary so that installboot can find the files it needs and disk on which
>> to install them. ...but doing that will just replicate what the upgrade
>> script already did and the error it gave you...
>>
>> At this point, the two pieces of information that would help the most are:
>> 1) the *EXACT AND FULL* error message that the upgrader reported from
>> installboot
>> 2) what your disklabel and partition layout looks like. The output of
>> "df -k" from the ramdisk shell prompt after the upgrade fails would be
>> good, for example, as it has everything mounted under /mnt.
>>
>>
>> Philip Guenther
>>
>>
Re: Bootloader failing to install on 2012 Mac Mini (Openbsd 6.4)
Thanks for the reply, I actually tried the install again after wiping the
disk and noticed that it seems like and efi partition wasn't auto-created
as part of the partitioning which seems odd since I swear it usually is for
efi systems but then again maybe I just don't remember. Install.txt doesn't
mention needing to create one even though one old guide I saw did as part
of the procedure. The previous efi partition I noticed when playing around
before wiping the disk must have been from the old Linux install.
Regardless the error is identical almost to the previous one but with new
numbers and letters after the ".".
The exact and full error message is as follows:
installboot: mkdir('/tmp/installboot.hP11Q78IbS/efi') failed: Invalid
argument
Failed to install bootlocks.
You will not be able to book OpenBSD from sd0.
The output of df -k (Sorry about the formatting, I tried to replicate it as
best I could):
Filesystem 1K-blocks Used AvailCapacity Mounted on
/dev/rd0a3535 5256279 92%/
/dev/sd0a 102887869194 908242 7% /mnt
/dev/sd0l 312080952 36 296476872 0%/mnt/home
/dev/sd0d 4125406 2 3919134 0% /mnt/tmp
/dev/sd0f2061054 577930 1380072 30% /mnt/usr
/dev/sd0g 1028878190628 786808 20% /mnt/usr/X11R6
/dev/sd0h 20636942 218 19604878 0% /mnt/usr/local
/dev/sd0k 6189758 2 58802700% /mnt/usr/obj
/dev/sd0j2061054 2 19580000% /mnt/usr/src
/dev/sd0e 20425598 3394 19400926 0% /mnt/var
On Wed, Oct 24, 2018 at 1:51 PM Philip Guenther wrote:
> On Tue, Oct 23, 2018 at 4:38 PM Liam Wigney wrote:
>
>> I've used Openbsd before but my installs have gone smoothly with no issues
>> and this is really the first time it's been a problem. The install is a
>> super boring one, it's whole disk Openbsd with the default gpt partition
>> layout and nothing else special.
>>
>> During the install after the sets are successfully installed there's a
>> notification that the bootloader has failed to install due to mkdir being
>> called with an invalid argument.
>
>
> All the error messages from installboot from mkdir failing include both
> the path and the specific error message. Those are included because
> they're helpful in understanding exactly what failed (and thus what could
> be wrong). Including the _exact_ and _full_ error message would make it
> easier to assist.
>
> (Ruling out stuff that _didn't_ fail is key to figuring out root causes.)
>
>
>
>> Some research online said that I should
>> try to do installboot manually in the subsequent prrompt, so I called
>> installboot sd0 and got the following error
>>
>> installboot: /usr/mdec/biosboot: No such file or directory
>>
>
> Yes, when running from the bsd.rd ramdisk additional argument are
> necessary so that installboot can find the files it needs and disk on which
> to install them. ...but doing that will just replicate what the upgrade
> script already did and the error it gave you...
>
> At this point, the two pieces of information that would help the most are:
> 1) the *EXACT AND FULL* error message that the upgrader reported from
> installboot
> 2) what your disklabel and partition layout looks like. The output of "df
> -k" from the ramdisk shell prompt after the upgrade fails would be good,
> for example, as it has everything mounted under /mnt.
>
>
> Philip Guenther
>
>
Re: Bootloader failing to install on 2012 Mac Mini (Openbsd 6.4)
On Tue, Oct 23, 2018 at 4:38 PM Liam Wigney wrote: > I've used Openbsd before but my installs have gone smoothly with no issues > and this is really the first time it's been a problem. The install is a > super boring one, it's whole disk Openbsd with the default gpt partition > layout and nothing else special. > > During the install after the sets are successfully installed there's a > notification that the bootloader has failed to install due to mkdir being > called with an invalid argument. All the error messages from installboot from mkdir failing include both the path and the specific error message. Those are included because they're helpful in understanding exactly what failed (and thus what could be wrong). Including the _exact_ and _full_ error message would make it easier to assist. (Ruling out stuff that _didn't_ fail is key to figuring out root causes.) > Some research online said that I should > try to do installboot manually in the subsequent prrompt, so I called > installboot sd0 and got the following error > > installboot: /usr/mdec/biosboot: No such file or directory > Yes, when running from the bsd.rd ramdisk additional argument are necessary so that installboot can find the files it needs and disk on which to install them. ...but doing that will just replicate what the upgrade script already did and the error it gave you... At this point, the two pieces of information that would help the most are: 1) the *EXACT AND FULL* error message that the upgrader reported from installboot 2) what your disklabel and partition layout looks like. The output of "df -k" from the ramdisk shell prompt after the upgrade fails would be good, for example, as it has everything mounted under /mnt. Philip Guenther
Bootloader failing to install on 2012 Mac Mini (Openbsd 6.4)
I've used Openbsd before but my installs have gone smoothly with no issues and this is really the first time it's been a problem. The install is a super boring one, it's whole disk Openbsd with the default gpt partition layout and nothing else special. During the install after the sets are successfully installed there's a notification that the bootloader has failed to install due to mkdir being called with an invalid argument. Some research online said that I should try to do installboot manually in the subsequent prrompt, so I called installboot sd0 and got the following error installboot: /usr/mdec/biosboot: No such file or directory Looking in /usr/medc/ the only program is mbr. Using installboot -v I saw that the second stage is supposed to be /usr/medc/boot which is also missing. It's my understanding anyway that these are for mbr legacy boot situations not gtp efi ones and Mac's use efi so I don't know if this is the issue. So I really don't know where to go from here. I saw a few other references in the mailing list to missing biosboot but they don't seem relevant to this case as it seems like they had other issues as well. I don't know if it's an Mac efi problem or not but I've noticed that lots of the community use(d) Macbooks including airs but I didn't notice any specific things to do when installing. Sorry if I've missed something obvious, I've actually never had any trouble with the install before so it's my first time actually trying to work out what's up. I just have no clue how to debug this issue so any pointers would be much appreciated.
Re: Add support for Mac mini 2014
On 31.10.17 8:41 , Mike Larkin wrote:
> This machine is not a macppc. This machine is an amd64.
I was talking about the Mac mini 2005, which was macppc when I last used
it. My current Mac mini 2014 is intel and amd64.
Anyway, my call is still on. Who wants to help with getting OpenBSD to
run on amd64 Mac Mini 2014?
Attaching again my patch and the dmesg of the Mac mini 2014.
*Kristian
--- 6.2/src/sys/dev/acpi/dsdt.c Sun May 28 17:36:45 2017
+++ src/sys/dev/acpi/dsdt.c Mon Oct 30 16:08:39 2017
@@ -2488,6 +2488,11 @@
aml_rwgas(ref1, fld->v_field.bitpos + bpos, blen,
val, mode, fld->v_field.flags);
break;
+ case ACPI_OPREG_CMOS:
+ printf("RegionSpace: %u\n", ref1->v_opregion.iospace);
+ aml_rwgas(ref1, fld->v_field.bitpos + bpos, blen,
+ val, mode, fld->v_field.flags);
+ break;
default:
aml_die("Unsupported RegionSpace 0x%x",
ref1->v_opregion.iospace);
OpenBSD 6.2-stable (GENERIC.MP) #3: Mon Oct 30 16:47:38 CET 2017
root@test.localnet:/home/src/sys/arch/amd64/compile/GENERIC.MP
real mem = 4147183616 (3955MB)
avail mem = 4014477312 (3828MB)
mpath0 at root
scsibus0 at mpath0: 256 targets
mainbus0 at root
bios0 at mainbus0: SMBIOS rev. 2.4 @ 0x88d1 (49 entries)
bios0: vendor Apple Inc. version "MM71.88Z.0224.B00.1708080033" date 08/08/2017
bios0: Apple Inc. Macmini7,1
acpi0 at bios0: rev 2
acpi0: sleep states S0 S3 S4 S5
acpi0: tables DSDT FACP HPET APIC SBST ECDT SSDT SSDT SSDT SSDT SSDT SSDT SSDT
SSDT DMAR MCFG
acpi0: wakeup devices P0P2(S3) EC__(S3) HDEF(S3) RP03(S4) ARPT(S4) RP04(S4)
GIGE(S4) SDXC(S3) RP05(S3) RP06(S3) XHC1(S3)
acpitimer0 at acpi0: 3579545 Hz, 24 bits
acpihpet0 at acpi0: 14318179 Hz
acpimadt0 at acpi0 addr 0xfee0: PC-AT compat
cpu0 at mainbus0: apid 0 (boot processor)
cpu0: Intel(R) Core(TM) i5-4260U CPU @ 1.40GHz, 2000.33 MHz
cpu0:
FPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,CFLUSH,DS,ACPI,MMX,FXSR,SSE,SSE2,SS,HTT,TM,PBE,SSE3,PCLMUL,DTES64,MWAIT,DS-CPL,VMX,EST,TM2,SSSE3,SDBG,FMA3,CX16,xTPR,PDCM,PCID,SSE4.1,SSE4.2,x2APIC,MOVBE,POPCNT,DEADLINE,AES,XSAVE,AVX,F16C,RDRAND,NXE,PAGE1GB,RDTSCP,LONG,LAHF,ABM,PERF,ITSC,FSGSBASE,BMI1,AVX2,SMEP,BMI2,ERMS,INVPCID,SENSOR,ARAT
cpu0: 256KB 64b/line 8-way L2 cache
cpu0: TSC frequency 2000329420 Hz
cpu0: smt 0, core 0, package 0
mtrr: Pentium Pro MTRR support, 10 var ranges, 88 fixed ranges
cpu0: apic clock running at 99MHz
cpu0: mwait min=64, max=64, C-substates=0.2.1.2.4.1.1.1, IBE
cpu1 at mainbus0: apid 2 (application processor)
cpu1: Intel(R) Core(TM) i5-4260U CPU @ 1.40GHz, 2000.00 MHz
cpu1:
FPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,CFLUSH,DS,ACPI,MMX,FXSR,SSE,SSE2,SS,HTT,TM,PBE,SSE3,PCLMUL,DTES64,MWAIT,DS-CPL,VMX,EST,TM2,SSSE3,SDBG,FMA3,CX16,xTPR,PDCM,PCID,SSE4.1,SSE4.2,x2APIC,MOVBE,POPCNT,DEADLINE,AES,XSAVE,AVX,F16C,RDRAND,NXE,PAGE1GB,RDTSCP,LONG,LAHF,ABM,PERF,ITSC,FSGSBASE,BMI1,AVX2,SMEP,BMI2,ERMS,INVPCID,SENSOR,ARAT
cpu1: 256KB 64b/line 8-way L2 cache
cpu1: smt 0, core 1, package 0
cpu2 at mainbus0: apid 1 (application processor)
cpu2: Intel(R) Core(TM) i5-4260U CPU @ 1.40GHz, 2000.00 MHz
cpu2:
FPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,CFLUSH,DS,ACPI,MMX,FXSR,SSE,SSE2,SS,HTT,TM,PBE,SSE3,PCLMUL,DTES64,MWAIT,DS-CPL,VMX,EST,TM2,SSSE3,SDBG,FMA3,CX16,xTPR,PDCM,PCID,SSE4.1,SSE4.2,x2APIC,MOVBE,POPCNT,DEADLINE,AES,XSAVE,AVX,F16C,RDRAND,NXE,PAGE1GB,RDTSCP,LONG,LAHF,ABM,PERF,ITSC,FSGSBASE,BMI1,AVX2,SMEP,BMI2,ERMS,INVPCID,SENSOR,ARAT
cpu2: 256KB 64b/line 8-way L2 cache
cpu2: smt 1, core 0, package 0
cpu3 at mainbus0: apid 3 (application processor)
cpu3: Intel(R) Core(TM) i5-4260U CPU @ 1.40GHz, 2000.00 MHz
cpu3:
FPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,CFLUSH,DS,ACPI,MMX,FXSR,SSE,SSE2,SS,HTT,TM,PBE,SSE3,PCLMUL,DTES64,MWAIT,DS-CPL,VMX,EST,TM2,SSSE3,SDBG,FMA3,CX16,xTPR,PDCM,PCID,SSE4.1,SSE4.2,x2APIC,MOVBE,POPCNT,DEADLINE,AES,XSAVE,AVX,F16C,RDRAND,NXE,PAGE1GB,RDTSCP,LONG,LAHF,ABM,PERF,ITSC,FSGSBASE,BMI1,AVX2,SMEP,BMI2,ERMS,INVPCID,SENSOR,ARAT
cpu3: 256KB 64b/line 8-way L2 cache
cpu3: smt 1, core 1, package 0
ioapic0 at mainbus0: apid 2 pa 0xfec0, version 20, 40 pins
acpiec0 at acpi0
acpimcfg0 at acpi0 addr 0xe000, bus 0-154
RegionSpace: 5
acpiprt0 at acpi0: bus 0 (PCI0)
acpiprt1 at acpi0: bus -1 (P0P2)
acpiprt2 at acpi0: bus 2 (RP03)
acpiprt3 at acpi0: bus 3 (RP04)
acpiprt4 at acpi0: bus 4 (RP05)
acpiprt5 at acpi0: bus -1 (RP06)
acpicpu0 at acpi0: C3(200@506 mwait.1@0x60), C2(200@148 mwait.1@0x33),
C1(1000@1 mwait.1), PSS
acpicpu1 at acpi0: C3(200@506 mwait.1@0x60), C2(200@148 mwait.1@0x33),
C1(1000@1 mwait.1), PSS
acpicpu2 at acpi0: C3(200@506 mwait.1@0x60), C2(200@148 mwait.1@0x33),
C1(1000@1 mwait.1), PSS
acpi
Re: Add support for Mac mini 2014
On Tue, Oct 31, 2017 at 08:34:12AM +0100, Kristian Peters wrote:
> Hi all,
>
> So, I'm taking this to openbsd-misc and kindly ask who wants to help
> with getting OpenBSD to run (again) on a Mac mini (latest intel model)?
>
> As my knowledge of programming gasio code is limited, I would need help
> to implement that what Mike suggested.
>
> Otherwise, I guess, it's time for me to move on after 10 years macppc or so.
>
This machine is not a macppc. This machine is an amd64.
-ml
> Best wishes, *Kristian
>
> On 30.10.17 21:27 , Mike Larkin wrote:
> >
> > I don't think this is right. It may be "solving" your problem but our rwgas
> > implementation doesn't handle this type of OpRegion. So, at best, we're
> > ignoring
> > the request (with the changes above), or worse, perhaps trashing some
> > memory.
> >
> > Someone needs to add the I/O for this type of region (CMOS NVRAM) to
> > the gasio code in acpi.c. There is a sequence of IN/OUT instructions that
> > need to
> > occur (in a proper order, with correct locking because the OS is using the
> > device also) to get at those NVRAM registers. It probably isn't a huge
> > amount
> > of work, but nobody has stepped up to do it yet.
> >
> > If you want a workaround, you might try just ignoring ACPI_OPREG_CMOS
> > locally
> > in your tree. That too isn't right but at least it won't be possibly causing
> > side effects/damage elsewhere.
> >
> > -ml
> >
> > On Mon, Oct 30, 2017 at 06:31:19PM +0100, Kristian Peters wrote:
> >> Hi,
> >>
> >> As I thought, a simple addition to acpi/dsdt.c and the Mac mini is able
> >> to boot. I used the external hard drive from a fresh 6.2-install on
> >> another computer to that purpose. This patch is tested (tried to compile
> >> the release under the newly built kernel) and was made against 6.2-release.
> >>
> >> I attach the patch and the dmesg-output of the Mac mini running with the
> >> patched kernel.
> >>
> >> Can you merge it in -current?
> >>
> >> --- 6.2/src/sys/dev/acpi/dsdt.c Sun May 28 17:36:45 2017
> >> +++ src/sys/dev/acpi/dsdt.c Mon Oct 30 16:08:39 2017
> >> @@ -2488,6 +2488,11 @@
> >> aml_rwgas(ref1, fld->v_field.bitpos + bpos, blen,
> >> val, mode, fld->v_field.flags);
> >> break;
> >> + case ACPI_OPREG_CMOS:
> >> + printf("RegionSpace: %u\n",
> >> ref1->v_opregion.iospace);
> >> + aml_rwgas(ref1, fld->v_field.bitpos + bpos, blen,
> >> + val, mode, fld->v_field.flags);
> >> + break;
> >> default:
> >> aml_die("Unsupported RegionSpace 0x%x",
> >> ref1->v_opregion.iospace);
> >>
> >> PS: I still fail to build the full release and, thus, also the
> >> install62.fs image I want to use for installation. So it would be great
> >> if you consider fixing the issue soon.
> >>
> >> Best wishes, *Kristian
> >>
>
Add support for Mac mini 2014
Hi all,
So, I'm taking this to openbsd-misc and kindly ask who wants to help
with getting OpenBSD to run (again) on a Mac mini (latest intel model)?
As my knowledge of programming gasio code is limited, I would need help
to implement that what Mike suggested.
Otherwise, I guess, it's time for me to move on after 10 years macppc or so.
Best wishes, *Kristian
On 30.10.17 21:27 , Mike Larkin wrote:
>
> I don't think this is right. It may be "solving" your problem but our rwgas
> implementation doesn't handle this type of OpRegion. So, at best, we're
> ignoring
> the request (with the changes above), or worse, perhaps trashing some memory.
>
> Someone needs to add the I/O for this type of region (CMOS NVRAM) to
> the gasio code in acpi.c. There is a sequence of IN/OUT instructions that
> need to
> occur (in a proper order, with correct locking because the OS is using the
> device also) to get at those NVRAM registers. It probably isn't a huge amount
> of work, but nobody has stepped up to do it yet.
>
> If you want a workaround, you might try just ignoring ACPI_OPREG_CMOS locally
> in your tree. That too isn't right but at least it won't be possibly causing
> side effects/damage elsewhere.
>
> -ml
>
> On Mon, Oct 30, 2017 at 06:31:19PM +0100, Kristian Peters wrote:
>> Hi,
>>
>> As I thought, a simple addition to acpi/dsdt.c and the Mac mini is able
>> to boot. I used the external hard drive from a fresh 6.2-install on
>> another computer to that purpose. This patch is tested (tried to compile
>> the release under the newly built kernel) and was made against 6.2-release.
>>
>> I attach the patch and the dmesg-output of the Mac mini running with the
>> patched kernel.
>>
>> Can you merge it in -current?
>>
>> --- 6.2/src/sys/dev/acpi/dsdt.c Sun May 28 17:36:45 2017
>> +++ src/sys/dev/acpi/dsdt.c Mon Oct 30 16:08:39 2017
>> @@ -2488,6 +2488,11 @@
>> aml_rwgas(ref1, fld->v_field.bitpos + bpos, blen,
>> val, mode, fld->v_field.flags);
>> break;
>> + case ACPI_OPREG_CMOS:
>> + printf("RegionSpace: %u\n",
>> ref1->v_opregion.iospace);
>> + aml_rwgas(ref1, fld->v_field.bitpos + bpos, blen,
>> + val, mode, fld->v_field.flags);
>> + break;
>> default:
>> aml_die("Unsupported RegionSpace 0x%x",
>> ref1->v_opregion.iospace);
>>
>> PS: I still fail to build the full release and, thus, also the
>> install62.fs image I want to use for installation. So it would be great
>> if you consider fixing the issue soon.
>>
>> Best wishes, *Kristian
>>
Mac mini acpiec(4) panic with Unsupported RegionSpace
I have two different Macmini7,1 systems (the late 2014 and most recent Mac mini model). On one of them, I was using OpenBSD -current in April but haven't used the system or upgraded it to a newer snapshot. I purchased another similar system and went to install OpenBSD -current on it from the June 22 and found that I had a panic early in the boot process. The panic is from below which I hand copied. This is from bsd.rd but the panic is identical with bsd.mp as well. I did not get far enough to get a full dmesg with the recent kernels but could pull an old one as well if needed. Also, this is using EFI boot from a USB stick which has worked fine in the past. real mem = 17032085504 (16243MB) avail mem = 16514179072 (15749MB) mainbus0 at root bios0 at mainbus0: SMBIOS rev. 2.4 @ 0x88d1 (49 entries) ... (snip) ... ioapic0 at mainbus0: apid 2 pa 0xfec0, version 20, 40 pins acpiec0 at acpi0 Unsupported RegionSpace panic: aml_die aml_rwfield:2475 The operating system has halted. Press press any key to reboot. rebooting... I believe the panic stems from revision 1.53 of acpiec.c. I can try reverting that commit on -current now and see if I can avoid the issue but there may be more to it than that. Any idea how to resolve this? There is also a separate issue that I will report in another message with "halt -p" causing a panic related to aml but that has been around for quite a while including in the April snapshot I am running on one of those systems. It isn't as important since reboot works fine. Bryan
mac mini - virtualbox - openbsd amd64?
Hi, I have only good experiences with running obenbsd inside virtual box. Last time I used openbsd like this is about 1 year ago. Performance was good. Screen resize via randr possible ( I had to define the video modes on the virtual box cmd line, beware of the color depth). I don't know what exactly you are trying to do, but playing 3d games inside the virtual box openbsd guest might become difficult. x11, Rdp ( virtual box include or as application inside the guest) is also a possible solution to connect to the VM via network an run virtual box headless. This might give you another option for screen resizing. Jan
mac mini - virtualbox - openbsd amd64?
has anybody tried running openbsd in virtualbox on a mac mini? is X11, etc feasable? -f -- if r is reverse, how come d is forward?
Re: mac mini - virtualbox - openbsd amd64?
On 2015-03-24 11:48, frantisek holop wrote: has anybody tried running openbsd in virtualbox on a mac mini? is X11, etc feasable? -f Never on a macmini, but I have on imac and many others. If you are seeking a virtual environment, I do not recommend using OpenBSD as the guest. Aside from the obvious security concerns, You will end up with frustrations such as mouse troubles and no ability to resize screen running X env. However, if you are determined for a virtual OpenBSD guest, use vmware fusion. Virtual box is good with Linux,Solaris,Illumos style guests. -JF
Re: mac mini - virtualbox - openbsd amd64?
2015-03-24 22:17 GMT+05:30 Jeremiah Ford m...@jeremiahford.com: On 2015-03-24 11:48, frantisek holop wrote: has anybody tried running openbsd in virtualbox on a mac mini? is X11, etc feasable? -f Never on a macmini, but I have on imac and many others. If you are seeking a virtual environment, I do not recommend using OpenBSD as the guest. Aside from the obvious security concerns, You will end up with frustrations such as mouse troubles and no ability to resize screen running X env. Is this the same reason as why XVFB can't change [virtual] screen resolution too? xvfb run with the -xrandr argument e.g. Xvfb -screen 0 1600x1200x32 +extension RANDR , and trying to change screen resolution using xrandr e.g. xrandr -display :0 --size 1280x1024 and hooked in graphically with x11vnc. It seems that the XRANDR extension is magically absent because the xrandr tool terminates with error RandR extension missing?!
Re: Mac Mini
On Thursday, November 20, 2014 at 6:40 PM, Austin Gilbert wrote: On Nov 20, 2014, at 4:08 PM, bodie bodz...@openbsd.cz (mailto:bodz...@openbsd.cz) wrote: What is the date of your bsd.rd and snapshot? They are new most of the time daily. Like eg. now 20-Nov-2014 21:40 7.2M Perhaps I got burned by cheating? I grabbed install56.iso burned it to a CD and booted that. I didnât verify the bsd.rd on the ISO is the latest version in the snapshot folder. 217M Nov 18 17:37 install56.iso Did you already try to install complete snapshot on USB flash disk and boot out of it to see if it's issue just with bsd.rd or even with regular kernel? Negative. When I tried installing onto the USB from my MacBook laptop (the only other amd64 hardware I have available) the USB wasnât recognized. I did that with the 5.6 release CD not snapshot/current, no surprise the USB 3 hardware wasnât supported. I think at this point, I will try to go with the unattended install + SSH and see if I can get her up and running that way. Then I can send a dmesg and debugging information along to any interested parties. I had the same issue. It looks like it might be fixed in current though: I just booted my 2012 Mac mini from the latest snapshot of install56.iso and the keyboard is working now.
Mac Mini
I have an amd64 based Mac Mini which I would like to run OpenBSD on. With OpenBSD 5.6, the USB keyboard works at the “boot” prompt, but not after booting BSD.rd. The Mac Mini has USB 3 ports, I thought perhaps the newly minted USB 3 support in current could help, but the nightly snapshot behaved the same as the last release version. Is there anything I can do at the “boot” prompt to try disabling/enabling different device drivers for the USB ports so the keyboard will work under BSD.rd? The other option I thought of would be setting the terminal to a serial port… which I can’t do as I don’t have any serial ports on the box. Only Thunderbolt 2, USB 3, Ethernet.
Re: Mac Mini
On Thu, Nov 20, 2014 at 12:37:58PM -0600, Austin Gilbert wrote: I have an amd64 based Mac Mini which I would like to run OpenBSD on. With OpenBSD 5.6, the USB keyboard works at the ?boot? prompt, but not after booting BSD.rd. The Mac Mini has USB 3 ports, I thought perhaps the newly minted USB 3 support in current could help, but the nightly snapshot behaved the same as the last release version. Is there anything I can do at the ?boot? prompt to try disabling/enabling different device drivers for the USB ports so the keyboard will work under BSD.rd? The other option I thought of would be setting the terminal to a serial port? which I can?t do as I don?t have any serial ports on the box. Only Thunderbolt 2, USB 3, Ethernet. There are many Mac mini models. We can tell nothing without a dmesg. See the FAQ on how to capture it. -Otto
Re: Mac Mini
On Nov 20, 2014, at 1:27 PM, Otto Moerbeek o...@drijf.net wrote: On Thu, Nov 20, 2014 at 12:37:58PM -0600, Austin Gilbert wrote: I have an amd64 based Mac Mini which I would like to run OpenBSD on. With OpenBSD 5.6, the USB keyboard works at the ?boot? prompt, but not after booting BSD.rd. The Mac Mini has USB 3 ports, I thought perhaps the newly minted USB 3 support in current could help, but the nightly snapshot behaved the same as the last release version. Is there anything I can do at the ?boot? prompt to try disabling/enabling different device drivers for the USB ports so the keyboard will work under BSD.rd? The other option I thought of would be setting the terminal to a serial port? which I can?t do as I don?t have any serial ports on the box. Only Thunderbolt 2, USB 3, Ethernet. There are many Mac mini models. We can tell nothing without a dmesg. I'd love to get a dmesg, just need a way for the keyboard to work under BSD.rd. I was really asking if there were some tricks I could use at the 'boot' to maybe change how the USB is getting driven. I have no PS2 port, only USB 3 for keyboard. I also have no serial ports, so redirecting console is not an option. See the FAQ on how to capture it. Do you have a specific link that covers my specific situation? http://www.openbsd.org/faq/faq4.html#getdmesg Mounting a writable drive requires the keyboard to work. Yeah? I have no serial ports I can redirect the console to. I gather I'm just dead in the water then. I assume the normal OS developer would debug under friendlier conditions. ;(
Re: Mac Mini
Austin Gilbert said: Is there anything I can do at the “boot” prompt to try disabling/enabling different device drivers for the USB ports so the keyboard will work under BSD.rd? Your best bet would probably be to install OpenBSD in unattended mode[1] and get dmesg via ssh. That said, you may try disabling controllers via UKC(8)[2], but I am not sure whether it is available in bsd.rd. -- Dmitrij D. Czarkoff [1] http://undeadly.org/cgi?action=articlesid=20140106055302 [2] http://www.openbsd.org/cgi-bin/man.cgi/OpenBSD-current/man8/UKC.8
Re: Mac Mini
On 2014-11-20 18:37, Austin Gilbert wrote: I have an amd64 based Mac Mini which I would like to run OpenBSD on. With OpenBSD 5.6, the USB keyboard works at the “boot” prompt, but not after booting BSD.rd. The Mac Mini has USB 3 ports, I thought perhaps the newly minted USB 3 support in current could help, but the nightly snapshot behaved the same as the last release version. Is there anything I can do at the “boot” prompt to try disabling/enabling different device drivers for the USB ports so the keyboard will work under BSD.rd? The other option I thought of would be setting the terminal to a serial port… which I can’t do as I don’t have any serial ports on the box. Only Thunderbolt 2, USB 3, Ethernet. The OpenBSD usb3 driver xhci was only released after the 5.6 disks so you might have to download the most 5.6-current in its most recent snapshot to get this to work. It will work to the bios because it has been manufactured that way. Good Luck Moss
Re: Mac Mini
Austin Gilbert [austin.gilb...@gmail.com] wrote: On Nov 20, 2014, at 1:27 PM, Otto Moerbeek o...@drijf.net wrote: On Thu, Nov 20, 2014 at 12:37:58PM -0600, Austin Gilbert wrote: I have an amd64 based Mac Mini which I would like to run OpenBSD on. With OpenBSD 5.6, the USB keyboard works at the ?boot? prompt, but not after booting BSD.rd. The Mac Mini has USB 3 ports, I thought perhaps the newly minted USB 3 support in current could help, but the nightly snapshot behaved the same as the last release version. Is there anything I can do at the ?boot? prompt to try disabling/enabling different device drivers for the USB ports so the keyboard will work under BSD.rd? The other option I thought of would be setting the terminal to a serial port? which I can?t do as I don?t have any serial ports on the box. Only Thunderbolt 2, USB 3, Ethernet. You might want to try a -current snapshot. They have a USB 3 driver!
Re: Mac Mini
On 20 November 2014 20:13:42 GMT+00:00, Austin Gilbert austin.gilb...@gmail.com wrote: I have no serial ports I can redirect the console to. I gather I'm just dead in the water then. I assume the normal OS developer would debug under friendlier conditions. ;( I was going to suggest yaifo, but it looks like it's dead. However, OpenBSD does support an unattended PXE install. Use that, then ssh in and do a dmesg? PK
Re: Mac Mini
On Nov 20, 2014, at 2:33 PM, Chris Cappuccio ch...@nmedia.net wrote: Austin Gilbert [austin.gilb...@gmail.com] wrote: On Nov 20, 2014, at 1:27 PM, Otto Moerbeek o...@drijf.net wrote: On Thu, Nov 20, 2014 at 12:37:58PM -0600, Austin Gilbert wrote: I have an amd64 based Mac Mini which I would like to run OpenBSD on. With OpenBSD 5.6, the USB keyboard works at the ?boot? prompt, but not after booting BSD.rd. The Mac Mini has USB 3 ports, I thought perhaps the newly minted USB 3 support in current could help, but the nightly snapshot behaved the same as the last release version. Is there anything I can do at the ?boot? prompt to try disabling/enabling different device drivers for the USB ports so the keyboard will work under BSD.rd? The other option I thought of would be setting the terminal to a serial port? which I can?t do as I don?t have any serial ports on the box. Only Thunderbolt 2, USB 3, Ethernet. You might want to try a -current snapshot. They have a USB 3 driver! I saw the news about the USB 3 driver in current and was very excited about that. The first thing I did was grab a snapshot. Sadly, the snapshot BSD.rd behaves the same as the stable 5.6 release (as of the 16th).
Re: Mac Mini
On 20.11.2014 22:49, Austin Gilbert wrote: On Nov 20, 2014, at 2:33 PM, Chris Cappuccio ch...@nmedia.net wrote: Austin Gilbert [austin.gilb...@gmail.com] wrote: On Nov 20, 2014, at 1:27 PM, Otto Moerbeek o...@drijf.net wrote: On Thu, Nov 20, 2014 at 12:37:58PM -0600, Austin Gilbert wrote: I have an amd64 based Mac Mini which I would like to run OpenBSD on. With OpenBSD 5.6, the USB keyboard works at the ?boot? prompt, but not after booting BSD.rd. The Mac Mini has USB 3 ports, I thought perhaps the newly minted USB 3 support in current could help, but the nightly snapshot behaved the same as the last release version. Is there anything I can do at the ?boot? prompt to try disabling/enabling different device drivers for the USB ports so the keyboard will work under BSD.rd? The other option I thought of would be setting the terminal to a serial port? which I can?t do as I don?t have any serial ports on the box. Only Thunderbolt 2, USB 3, Ethernet. You might want to try a -current snapshot. They have a USB 3 driver! I saw the news about the USB 3 driver in current and was very excited about that. The first thing I did was grab a snapshot. Sadly, the snapshot BSD.rd behaves the same as the stable 5.6 release (as of the 16th). What is the date of your bsd.rd and snapshot? They are new most of the time daily. Like eg. now 20-Nov-2014 21:40 7.2M Did you already try to install complete snapshot on USB flash disk and boot out of it to see if it's issue just with bsd.rd or even with regular kernel?
Re: Mac Mini
Austin Gilbert [austin.gilb...@gmail.com] wrote: I saw the news about the USB 3 driver in current and was very excited about that. The first thing I did was grab a snapshot. Sadly, the snapshot BSD.rd behaves the same as the stable 5.6 release (as of the 16th). xhci is commented out on the ramdisk, although I'm not sure why that is the case (It certainly should be on the RAMDISK_CD version!)
Re: Mac Mini
On Nov 20, 2014, at 4:08 PM, bodie bodz...@openbsd.cz wrote: What is the date of your bsd.rd and snapshot? They are new most of the time daily. Like eg. now 20-Nov-2014 21:407.2M Perhaps I got burned by cheating? I grabbed install56.iso burned it to a CD and booted that. I didn’t verify the bsd.rd on the ISO is the latest version in the snapshot folder. 217M Nov 18 17:37 install56.iso Did you already try to install complete snapshot on USB flash disk and boot out of it to see if it's issue just with bsd.rd or even with regular kernel? Negative. When I tried installing onto the USB from my MacBook laptop (the only other amd64 hardware I have available) the USB wasn’t recognized. I did that with the 5.6 release CD not snapshot/current, no surprise the USB 3 hardware wasn’t supported. I think at this point, I will try to go with the unattended install + SSH and see if I can get her up and running that way. Then I can send a dmesg and debugging information along to any interested parties.
Re: Mac Mini
On 20/11/14(Thu) 15:49, Austin Gilbert wrote: On Nov 20, 2014, at 2:33 PM, Chris Cappuccio ch...@nmedia.net wrote: Austin Gilbert [austin.gilb...@gmail.com] wrote: On Nov 20, 2014, at 1:27 PM, Otto Moerbeek o...@drijf.net wrote: On Thu, Nov 20, 2014 at 12:37:58PM -0600, Austin Gilbert wrote: I have an amd64 based Mac Mini which I would like to run OpenBSD on. With OpenBSD 5.6, the USB keyboard works at the ?boot? prompt, but not after booting BSD.rd. The Mac Mini has USB 3 ports, I thought perhaps the newly minted USB 3 support in current could help, but the nightly snapshot behaved the same as the last release version. Is there anything I can do at the ?boot? prompt to try disabling/enabling different device drivers for the USB ports so the keyboard will work under BSD.rd? The other option I thought of would be setting the terminal to a serial port? which I can?t do as I don?t have any serial ports on the box. Only Thunderbolt 2, USB 3, Ethernet. You might want to try a -current snapshot. They have a USB 3 driver! I saw the news about the USB 3 driver in current and was very excited about that. The first thing I did was grab a snapshot. Sadly, the snapshot BSD.rd behaves the same as the stable 5.6 release (as of the 16th). bsd.rd do not include xhci(4) for the moment, because there's a known issue with the driver some chips.
Re: Mac Mini
On 20.11.2014 23:40, Austin Gilbert wrote: On Nov 20, 2014, at 4:08 PM, bodie bodz...@openbsd.cz wrote: What is the date of your bsd.rd and snapshot? They are new most of the time daily. Like eg. now 20-Nov-2014 21:40 7.2M Perhaps I got burned by cheating? I grabbed install56.iso burned it to a CD and booted that. I didn’t verify the bsd.rd on the ISO is the latest version in the snapshot folder. 217M Nov 18 17:37 install56.iso Did you already try to install complete snapshot on USB flash disk and boot out of it to see if it's issue just with bsd.rd or even with regular kernel? Negative. When I tried installing onto the USB from my MacBook laptop (the only other amd64 hardware I have available) the USB wasn’t recognized. I did that with the 5.6 release CD not snapshot/current, no surprise the USB 3 hardware wasn’t supported. You can do this point anywhere where you have ability to provide USB flash to eg. virtual machine in VirtualBox, VMware Player, Qemu, whatever. It's sometimes handy to have such flash disk at hand. I think at this point, I will try to go with the unattended install + SSH and see if I can get her up and running that way. Then I can send a dmesg and debugging information along to any interested parties.
ATI Radeon 9200 on Mac Mini
This is current/macppc on a Mac Mini, see full dmesg below. It works fine, but the Radeon graphics, which is radeondrm0 at pci0 dev 16 function 0 ATI Radeon 9200 rev 0x01 might have some problems. This is how the boot sequence ends: root on wd0a (d2e7005f40cdabc7.a) swap on wd0b dump on wd0b drm: initializing kernel modesetting (RV280 0x1002:0x5962 0x1002:0x5962). error: [drm:pid0:radeon_get_bios] *ERROR* Unable to locate a BIOS ROM drm: Using generic clock info radeondrm0: VRAM: 128M 0x9800 - 0x9FFF (64M used) trying to bind memory to uninitialized GART ! error: [drm:pid0:radeon_ttm_backend_bind] *ERROR* failed to bind 1 pages at 0x error: [drm:pid0:radeon_wb_init] *ERROR* (-22) create WB bo failed error: [drm:pid0:r100_init] *ERROR* Disabling GPU acceleration drm: radeon: cp finalized drm: radeon: cp finalized Finalizing pool allocator ttm_pool_mm_shrink_fini stub drm: Zone kernel: Used memory at exit: 0 kiB drm: radeon: ttm finalized drm: Forcing AGP to PCI mode error: [drm:pid0:radeon_get_bios] *ERROR* Unable to locate a BIOS ROM drm: Using generic clock info radeondrm0: VRAM: 128M 0x9800 - 0x9FFF (64M used) radeondrm0: GTT: 512M 0x7800 - 0x97FF drm: PCI GART of 512M enabled (table at 0x0294A000). drm: Connector Table: 6 (mini external tmds) drm: No valid Ext TMDS info found in BIOS drm: No TV DAC info found in BIOS radeon_i2c_put_byte stub radeon_i2c_put_byte stub radeon_i2c_put_byte stub radeon_i2c_put_byte stub radeon_i2c_put_byte stub radeondrm0: 1280x1024 wsdisplay0 at radeondrm0 mux 1: console (std, vt100 emulation), using wskbd0 wskbd1: connecting to wsdisplay0 wsdisplay0: screen 1-5 added (std, vt100 emulation) Is this anything to worry about? What can I do to debug what radeon is complaining about? The graphics seems to work fine, and I can run X with machdep.allowaperture=0 (a good opportunity to thank all those who have been working on KMS!). One silly problem I am having with the graphics is that the textures of games/frozen-bubble are broken http://stare.cz/~hans/.tmp/fb.jpg For those of you deprived of the orgastic joys of frozen-bubble, the ball to be shooted should be shooting from a canon, and there is a penguin angling the canon to the left. In the left part, the level is supposed to be written. I don't know if this is frozen-bubble's problem, or a symptom of something wrong with my graphics. Jan [ using 554672 bytes of bsd ELF symbol table ] console out [ATY,RockHopper2_A]console in [keyboard] , using USB using parent ATY,RockHopper2Paren:: memaddr 9800 size 800, : consaddr 9c008000, : ioaddr 9002, size 2: width 1280 linebytes 1280 height 1024 depth 8 Copyright (c) 1982, 1986, 1989, 1991, 1993 The Regents of the University of California. All rights reserved. Copyright (c) 1995-2014 OpenBSD. All rights reserved. http://www.OpenBSD.org OpenBSD 5.5 (GENERIC) #166: Tue Mar 4 13:58:36 MST 2014 dera...@macppc.openbsd.org:/usr/src/sys/arch/macppc/compile/GENERIC real mem = 1073741824 (1024MB) avail mem = 1031159808 (983MB) mainbus0 at root: model PowerMac10,2 cpu0 at mainbus0: 7447A (Revision 0x102): 1499 MHz: 512KB L2 cache mem0 at mainbus0 spdmem0 at mem0: 1GB DDR SDRAM non-parity PC3200CL3.0 memc0 at mainbus0: uni-n rev 0xd2 hw-clock at memc0 not configured kiic0 at memc0 offset 0xf8001000 iic0 at kiic0 mpcpcibr0 at mainbus0 pci: uni-north pci0 at mpcpcibr0 bus 0 pchb0 at pci0 dev 11 function 0 Apple UniNorth AGP rev 0x00 radeondrm0 at pci0 dev 16 function 0 ATI Radeon 9200 rev 0x01 drm0 at radeondrm0 radeondrm0: irq 48 mpcpcibr1 at mainbus0 pci: uni-north pci1 at mpcpcibr1 bus 0 macobio0 at pci1 dev 23 function 0 Apple Intrepid rev 0x00 openpic0 at macobio0 offset 0x4: version 0x4614 feature 3f0302 LE macgpio0 at macobio0 offset 0x50 modem-reset at macgpio0 offset 0x1d not configured modem-power at macgpio0 offset 0x1c not configured macgpio1 at macgpio0 offset 0x9: irq 47 programmer-switch at macgpio0 offset 0x11 not configured gpio5 at macgpio0 offset 0x6f not configured gpio6 at macgpio0 offset 0x70 not configured extint-gpio15 at macgpio0 offset 0x67 not configured escc-legacy at macobio0 offset 0x12000 not configured zsc0 at macobio0 offset 0x13000: irq 22,23 zstty0 at zsc0 channel 0 zstty1 at zsc0 channel 1 aoa0 at macobio0 offset 0x1: irq 30,1,2 audio0 at aoa0 timer at macobio0 offset 0x15000 not configured adb0 at macobio0 offset 0x16000 apm0 at adb0: battery flags 0x0, 0% charged piic0 at adb0 iic1 at piic0 maxtmp0 at iic1 addr 0xc8: max6642 kiic1 at macobio0 offset 0x18000 iic2 at kiic1 wdc0 at macobio0 offset 0x2 irq 24: DMA bwi0 at pci1 dev 18 function 0 Broadcom BCM4318 rev 0x02: irq 52, address 00:11:24:bf:cb:2a ohci0 at pci1 dev 26 function 0 Apple Intrepid USB rev 0x00: irq 29, version 1.0, legacy support ohci1 at pci1 dev 27 function 0 NEC USB rev 0x43: irq 63, version 1.0 ohci2 at pci1 dev 27 function 1 NEC USB rev
Re: ATI Radeon 9200 on Mac Mini
On 08/03/14(Sat) 14:26, Jan Stary wrote: This is current/macppc on a Mac Mini, see full dmesg below. It works fine, but the Radeon graphics, which is radeondrm0 at pci0 dev 16 function 0 ATI Radeon 9200 rev 0x01 might have some problems. This is how the boot sequence ends: root on wd0a (d2e7005f40cdabc7.a) swap on wd0b dump on wd0b drm: initializing kernel modesetting (RV280 0x1002:0x5962 0x1002:0x5962). error: [drm:pid0:radeon_get_bios] *ERROR* Unable to locate a BIOS ROM drm: Using generic clock info radeondrm0: VRAM: 128M 0x9800 - 0x9FFF (64M used) trying to bind memory to uninitialized GART ! error: [drm:pid0:radeon_ttm_backend_bind] *ERROR* failed to bind 1 pages at 0x error: [drm:pid0:radeon_wb_init] *ERROR* (-22) create WB bo failed error: [drm:pid0:r100_init] *ERROR* Disabling GPU acceleration drm: radeon: cp finalized drm: radeon: cp finalized Finalizing pool allocator ttm_pool_mm_shrink_fini stub drm: Zone kernel: Used memory at exit: 0 kiB drm: radeon: ttm finalized drm: Forcing AGP to PCI mode error: [drm:pid0:radeon_get_bios] *ERROR* Unable to locate a BIOS ROM drm: Using generic clock info radeondrm0: VRAM: 128M 0x9800 - 0x9FFF (64M used) radeondrm0: GTT: 512M 0x7800 - 0x97FF drm: PCI GART of 512M enabled (table at 0x0294A000). drm: Connector Table: 6 (mini external tmds) drm: No valid Ext TMDS info found in BIOS drm: No TV DAC info found in BIOS radeon_i2c_put_byte stub radeon_i2c_put_byte stub radeon_i2c_put_byte stub radeon_i2c_put_byte stub radeon_i2c_put_byte stub radeondrm0: 1280x1024 wsdisplay0 at radeondrm0 mux 1: console (std, vt100 emulation), using wskbd0 wskbd1: connecting to wsdisplay0 wsdisplay0: screen 1-5 added (std, vt100 emulation) Is this anything to worry about? Not really. What can I do to debug what radeon is complaining about? You can try to figure out why AGP is no longer working, you'll need to enable appleagp for that in your kernel, if you find why I'm interested :) The graphics seems to work fine, and I can run X with machdep.allowaperture=0 (a good opportunity to thank all those who have been working on KMS!). One silly problem I am having with the graphics is that the textures of games/frozen-bubble are broken http://stare.cz/~hans/.tmp/fb.jpg For those of you deprived of the orgastic joys of frozen-bubble, the ball to be shooted should be shooting from a canon, and there is a penguin angling the canon to the left. In the left part, the level is supposed to be written. I don't know if this is frozen-bubble's problem, or a symptom of something wrong with my graphics. Or simply just a bug in the driver(s), was it working before? Coud you try with software rendering only, by setting LIBGL_ALWAYS_SOFTWARE before launching the application? See the Mesa page [0] for more informations. Martin [0] http://www.mesa3d.org/envvars.html
Re: mac mini
Doug Hardie writes: On 20 November 2013, at 10:09, Friedrich Locke friedrich.lo...@gmail.com wrote: Does anyone here run Open/FreeBSD on mac mini ? Does the OS fully supports macmini hadrwared ? I have a couple production servers using Minis running FreeBSD 9.1 and 9.2. Check the archives as I posted the procedures I used to install. Some current Minis require a bit of horsing around to get networking to work. I have never used a windowing system on them. I only use a dumb terminal for initial setup and then SSH in after that. I've been running FreeBSD on a 2008 Intel 8-core Mac Pro (the tower) for years, just bumped it up to the current 10-BETA3 (now that Andriy solved the ZFS/mmap bug I was fighting and I can trust my flac tagging pipeline again). Works great. I'm running the gnome desktop using the nvidia binary distribution to drive a 30 Dell monitor. Root on Zfs, two disk mirror. Swapping directly onto partitions, no mirror or ZFS involved. I'm still depending on the BIOS emulation to boot and it only gets triggered if you use MBR formatted disks, not GPT. That confused the daylights out of me for a bit. I'm not sure if the EFI (?) boot stuff works or not. One time out of 4 it hangs early in the kernel starting up. Never cared enough to get help tracking it down. g.
mac mini
Does anyone here run Open/FreeBSD on mac mini ? Does the OS fully supports macmini hadrwared ? Thank you for the answers. Fried.
Re: mac mini
On Nov 20 16:09:07, friedrich.lo...@gmail.com wrote: Does anyone here run Open/FreeBSD on mac mini ? Does the OS fully supports macmini hadrwared ? It works fine for me. Haven't tried the bwi(4) though. Jan OpenBSD 5.4-current (GENERIC) #79: Thu Nov 14 02:48:44 MST 2013 dera...@macppc.openbsd.org:/usr/src/sys/arch/macppc/compile/GENERIC real mem = 1073741824 (1024MB) avail mem = 1031204864 (983MB) mainbus0 at root: model PowerMac10,2 cpu0 at mainbus0: 7447A (Revision 0x102): 1499 MHz: 512KB L2 cache mem0 at mainbus0 spdmem0 at mem0: 1GB DDR SDRAM non-parity PC3200CL3.0 memc0 at mainbus0: uni-n rev 0xd2 hw-clock at memc0 not configured kiic0 at memc0 offset 0xf8001000 iic0 at kiic0 mpcpcibr0 at mainbus0 pci: uni-north pci0 at mpcpcibr0 bus 0 pchb0 at pci0 dev 11 function 0 Apple UniNorth AGP rev 0x00 radeondrm0 at pci0 dev 16 function 0 ATI Radeon 9200 rev 0x01: irq 48 drm0 at radeondrm0 mpcpcibr1 at mainbus0 pci: uni-north pci1 at mpcpcibr1 bus 0 macobio0 at pci1 dev 23 function 0 Apple Intrepid rev 0x00 openpic0 at macobio0 offset 0x4: version 0x4614 feature 3f0302 LE macgpio0 at macobio0 offset 0x50 modem-reset at macgpio0 offset 0x1d not configured modem-power at macgpio0 offset 0x1c not configured macgpio1 at macgpio0 offset 0x9: irq 47 programmer-switch at macgpio0 offset 0x11 not configured gpio5 at macgpio0 offset 0x6f not configured gpio6 at macgpio0 offset 0x70 not configured extint-gpio15 at macgpio0 offset 0x67 not configured escc-legacy at macobio0 offset 0x12000 not configured zsc0 at macobio0 offset 0x13000: irq 22,23 zstty0 at zsc0 channel 0 zstty1 at zsc0 channel 1 aoa0 at macobio0 offset 0x1: irq 30,1,2 audio0 at aoa0 timer at macobio0 offset 0x15000 not configured adb0 at macobio0 offset 0x16000 apm0 at adb0: battery flags 0x0, 0% charged piic0 at adb0 iic1 at piic0 maxtmp0 at iic1 addr 0xc8: max6642 kiic1 at macobio0 offset 0x18000 iic2 at kiic1 wdc0 at macobio0 offset 0x2 irq 24: DMA bwi0 at pci1 dev 18 function 0 Broadcom BCM4318 rev 0x02: irq 52, address 00:11:24:bf:cb:2a ohci0 at pci1 dev 26 function 0 Apple Intrepid USB rev 0x00: irq 29, version 1.0, legacy support ohci1 at pci1 dev 27 function 0 NEC USB rev 0x43: irq 63, version 1.0 ohci2 at pci1 dev 27 function 1 NEC USB rev 0x43: irq 63, version 1.0 ehci0 at pci1 dev 27 function 2 NEC USB rev 0x04: irq 63 usb0 at ehci0: USB revision 2.0 uhub0 at usb0 NEC EHCI root hub rev 2.00/1.00 addr 1 usb1 at ohci0: USB revision 1.0 uhub1 at usb1 Apple OHCI root hub rev 1.00/1.00 addr 1 usb2 at ohci1: USB revision 1.0 uhub2 at usb2 NEC OHCI root hub rev 1.00/1.00 addr 1 usb3 at ohci2: USB revision 1.0 uhub3 at usb3 NEC OHCI root hub rev 1.00/1.00 addr 1 mpcpcibr2 at mainbus0 pci: uni-north pci2 at mpcpcibr2 bus 0 kauaiata0 at pci2 dev 13 function 0 Apple Intrepid ATA rev 0x00 wdc1 at kauaiata0 irq 39: DMA atapiscsi0 at wdc1 channel 0 drive 0 scsibus0 at atapiscsi0: 2 targets cd0 at scsibus0 targ 0 lun 0: MATSHITA, DVD-R UJ-825, DAND ATAPI 5/cdrom removable wd0 at wdc1 channel 0 drive 1: ST9808211A wd0: 16-sector PIO, LBA, 76319MB, 156301488 sectors cd0(wdc1:0:0): using PIO mode 4, DMA mode 2, Ultra-DMA mode 4 wd0(wdc1:0:1): using PIO mode 4, DMA mode 2, Ultra-DMA mode 4 Apple UniNorth Firewire rev 0x81 at pci2 dev 14 function 0 not configured gem0 at pci2 dev 15 function 0 Apple Uni-N2 GMAC rev 0x80: irq 41, address 00:14:51:17:42:34 bmtphy0 at gem0 phy 0: BCM5221 100baseTX PHY, rev. 4 uhidev0 at uhub1 port 1 configuration 1 interface 0 Apple Computer HID-proxy rev 2.00/19.65 addr 2 uhidev0: iclass 3/1 ukbd0 at uhidev0: 8 variable keys, 6 key codes wskbd0 at ukbd0: console keyboard uhidev1 at uhub1 port 1 configuration 1 interface 1 Apple Computer HID-proxy rev 2.00/19.65 addr 2 uhidev1: iclass 3/1 ums0 at uhidev1: 5 buttons wsmouse0 at ums0 mux 0 uhidev2 at uhub2 port 1 configuration 1 interface 0 Chicony USB Keyboard rev 1.10/1.02 addr 2 uhidev2: iclass 3/1 ukbd1 at uhidev2: 8 variable keys, 6 key codes wskbd1 at ukbd1 mux 1 uhidev3 at uhub2 port 1 configuration 1 interface 1 Chicony USB Keyboard rev 1.10/1.02 addr 2 uhidev3: iclass 3/0, 3 report ids uhid0 at uhidev3 reportid 1: input=1, output=0, feature=0 uhid1 at uhidev3 reportid 2: input=1, output=0, feature=2 uhid2 at uhidev3 reportid 3: input=3, output=0, feature=0 uhidev4 at uhub3 port 1 configuration 1 interface 0 Logitech Optical USB Mouse rev 2.00/3.40 addr 2 uhidev4: iclass 3/1 ums1 at uhidev4: 3 buttons, Z dir wsmouse1 at ums1 mux 0 vscsi0 at root scsibus1 at vscsi0: 256 targets softraid0 at root scsibus2 at softraid0: 256 targets bootpath: /pci@f400/ata-6@d/disk@1:/bsd root on wd0a (3347fef298f5d246.a) swap on wd0b dump on wd0b drm: initializing kernel modesetting (RV280 0x1002:0x5962 0x1002:0x5962). error: [drm:pid0:radeon_get_bios] *ERROR* Unable to locate a BIOS ROM drm: Using generic clock info radeondrm0: VRAM: 128M 0x9800 - 0x9FFF (64M used) ttm_pool_mm_shrink_init stub trying to bind memory
Re: mac mini
There are many generations of Mac Mini. I have a i386 Core Duo (read: old) that ran OpenBSD. I have a macppc (read: older) that also runs OpenBSD quite well. I have wired Ethernet, so I wasn't concerned with wireless. I can't comment on that. On Wed, Nov 20, 2013 at 1:09 PM, Friedrich Locke friedrich.lo...@gmail.com wrote: Does anyone here run Open/FreeBSD on mac mini ? Does the OS fully supports macmini hadrwared ? Thank you for the answers. Fried.
Re: mac mini
On Wed, Nov 20, 2013 at 04:09:07PM -0200, Friedrich Locke wrote: Does anyone here run Open/FreeBSD on mac mini ? Does the OS fully supports macmini hadrwared ? Thank you for the answers. Fried. I'm typing this on OpenBSD on the last generation of powerpc mac mini's if that helps. Ken
Re: mac mini
On Wed, Nov 20, 2013 at 08:09:46PM +0200, Friedrich Locke wrote: Does anyone here run Open/FreeBSD on mac mini ? as mike said in the post below there are many models. i also run it on a macppc macmini and everything works like a charm. dmesg included. Does the OS fully supports macmini hadrwared ? Thank you for the answers. Fried. [ using 552884 bytes of bsd ELF symbol table ] console out [ATY,RockHopper2_A]console in [keyboard] , using USB using parent ATY,RockHopper2Paren:: memaddr 9800 size 800, : con saddr 9c008000, : ioaddr 9002, size 2: width 800 linebytes 1024 height 600 depth 8 Copyright (c) 1982, 1986, 1989, 1991, 1993 The Regents of the University of California. All rights reserve d. Copyright (c) 1995-2013 OpenBSD. All rights reserved. http://www.OpenBS D.org OpenBSD 5.4-current (GENERIC) #1: Sat Nov 9 12:31:10 EET 2013 r...@logic.2f30.org:/usr/src/sys/arch/macppc/compile/GENERIC real mem = 536870912 (512MB) avail mem = 507731968 (484MB) mainbus0 at root: model PowerMac10,2 cpu0 at mainbus0: 7447A (Revision 0x102): 1499 MHz: 512KB L2 cache mem0 at mainbus0 spdmem0 at mem0: 512MB DDR SDRAM non-parity PC3200CL3.0 memc0 at mainbus0: uni-n rev 0xd2 hw-clock at memc0 not configured kiic0 at memc0 offset 0xf8001000 iic0 at kiic0 mpcpcibr0 at mainbus0 pci: uni-north pci0 at mpcpcibr0 bus 0 pchb0 at pci0 dev 11 function 0 Apple UniNorth AGP rev 0x00 radeondrm0 at pci0 dev 16 function 0 ATI Radeon 9200 rev 0x01: irq 48 drm0 at radeondrm0 mpcpcibr1 at mainbus0 pci: uni-north pci1 at mpcpcibr1 bus 0 macobio0 at pci1 dev 23 function 0 Apple Intrepid rev 0x00 openpic0 at macobio0 offset 0x4: version 0x4614 feature 3f0302 LE macgpio0 at macobio0 offset 0x50 modem-reset at macgpio0 offset 0x1d not configured modem-power at macgpio0 offset 0x1c not configured macgpio1 at macgpio0 offset 0x9: irq 47 programmer-switch at macgpio0 offset 0x11 not configured gpio5 at macgpio0 offset 0x6f not configured gpio6 at macgpio0 offset 0x70 not configured extint-gpio15 at macgpio0 offset 0x67 not configured escc-legacy at macobio0 offset 0x12000 not configured zsc0 at macobio0 offset 0x13000: irq 22,23 zstty0 at zsc0 channel 0 zstty1 at zsc0 channel 1 aoa0 at macobio0 offset 0x1: irq 30,1,2 audio0 at aoa0 timer at macobio0 offset 0x15000 not configured adb0 at macobio0 offset 0x16000 apm0 at adb0: battery flags 0x0, 0% charged piic0 at adb0 iic1 at piic0 maxtmp0 at iic1 addr 0xc8: max6642 kiic1 at macobio0 offset 0x18000 iic2 at kiic1 wdc0 at macobio0 offset 0x2 irq 24: DMA bwi0 at pci1 dev 18 function 0 Broadcom BCM4318 rev 0x02: irq 52, addr ess 00:11:24:be:de:88 ohci0 at pci1 dev 26 function 0 Apple Intrepid USB rev 0x00: irq 29, v ersion 1.0, legacy support ohci1 at pci1 dev 27 function 0 NEC USB rev 0x43: irq 63, version 1.0 ohci2 at pci1 dev 27 function 1 NEC USB rev 0x43: irq 63, version 1.0 ehci0 at pci1 dev 27 function 2 NEC USB rev 0x04: irq 63 usb0 at ehci0: USB revision 2.0 uhub0 at usb0 NEC EHCI root hub rev 2.00/1.00 addr 1 usb1 at ohci0: USB revision 1.0 uhub1 at usb1 Apple OHCI root hub rev 1.00/1.00 addr 1 usb2 at ohci1: USB revision 1.0 uhub2 at usb2 NEC OHCI root hub rev 1.00/1.00 addr 1 usb3 at ohci2: USB revision 1.0 uhub3 at usb3 NEC OHCI root hub rev 1.00/1.00 addr 1 mpcpcibr2 at mainbus0 pci: uni-north pci2 at mpcpcibr2 bus 0 kauaiata0 at pci2 dev 13 function 0 Apple Intrepid ATA rev 0x00 wdc1 at kauaiata0 irq 39: DMA wd0 at wdc1 channel 0 drive 0: ST9808211A wd0: 16-sector PIO, LBA, 76319MB, 156301488 sectors atapiscsi0 at wdc1 channel 0 drive 1 scsibus0 at atapiscsi0: 2 targets cd0 at scsibus0 targ 0 lun 0: MATSHITA, DVD-R UJ-845, D8PB ATAPI 5/cdr om removable wd0(wdc1:0:0): using PIO mode 4, DMA mode 2, Ultra-DMA mode 4 cd0(wdc1:0:1): using PIO mode 4, DMA mode 2, Ultra-DMA mode 4 Apple UniNorth Firewire rev 0x81 at pci2 dev 14 function 0 not configu red gem0 at pci2 dev 15 function 0 Apple Uni-N2 GMAC rev 0x80: irq 41, add ress 00:14:51:17:3b:3a bmtphy0 at gem0 phy 0: BCM5221 100baseTX PHY, rev. 4 uhidev0 at uhub1 port 1 configuration 1 interface 0 Apple Computer HID- proxy rev 2.00/19.65 addr 2 uhidev0: iclass 3/1 ukbd0 at uhidev0: 8 variable keys, 6 key codes wskbd0 at ukbd0: console keyboard uhidev1 at uhub1 port 1 configuration 1 interface 1 Apple Computer HID- proxy rev 2.00/19.65 addr 2 uhidev1: iclass 3/1 ums0 at uhidev1: 5 buttons wsmouse0 at ums0 mux 0 vscsi0 at root scsibus1 at vscsi0: 256 targets softraid0 at root scsibus2 at softraid0: 256 targets bootpath: /pci@f400/ata-6@d/disk@0:/bsd root on wd0a (a83c01089213697c.a) swap on wd0b dump on wd0b drm: initializing kernel modesetting (RV280 0x1002:0x5962 0x1002:0x5962) . error: [drm:pid0:radeon_get_bios] *ERROR* Unable to locate a BIOS ROM drm: Using generic clock info radeondrm0: VRAM: 128M 0x9800 - 0x9FFF (64M used ) ttm_pool_mm_shrink_init stub trying to bind memory to uninitialized GART ! error: [drm:pid0:radeon_ttm_backend_bind] *ERROR* failed
Re: current/macppc on Mac Mini
Ha! This seems to assume that the (fdisk) DOS partition is the 'i' partition in the disklabel - it is not; I created a [c]ustom disklabel. A bunch of architectures work this way. And it is a quite normal expectation that the 'i' partition match the 'spoofed label' semantics. But for now I think you are the one who made the assumption that your machine can be setup *differently* .. and that everything would work. If you want to come up with a fix for the install script that can auto-determine the partition, we'll be waiting.
Re: current/macppc on Mac Mini
The saga continues: I tried to reinstall with 5.4-beta, and have a similar, but different problem now. To recall the previous situation: the kernel was confused about what 'cd0' and 'hd0' is, and I had to hardcode the bootpath into the kernel config. A patch from mpieuc...@nolizard.org solved it for me, but it is still considered not quite the right thing: On Dec 26 20:54:34, m...@online.fr wrote: I think I understand what goes wrong. The code responsible for matching the boot device to the actual kernel device on macppc is quite crude, especially for non-SCSI disks. Your bootpath specifies `disk@1' because the disk drive is the second device (slave) on the ATA channel, the cdrom drive being master. However, the kernel wants to match this information against a `wd1' device (as if there were two hard disks on the ATA channel). The kernel code needs to be fixed to use device_register() to match the boot path against actual attachment information, instead of walking the device tree at the end of autoconf. If nobody beats me to do this, I'll try to cook a diff in a few days. On May 23 09:29:25, h...@stare.cz wrote: On May 23 08:41:50, mpieuc...@nolizard.org wrote: Were you thinking of something like that? It works for me (c) tm, with my PowerBooks (disk@0/wd0), I haven't tried NFS boot yet. Jan, does it improve something for you? Yes it does: with this patch, I don't need to hardcode config bsd root on wd0a into my kernel, it figures the bootpath itself. [ using 500872 bytes of bsd ELF symbol table ] console out [ATY,RockHopper2_A]console in [keyboard] , using USB using parent ATY,RockHopper2Paren:: memaddr 9800 size 800, : consaddr 9c008000, : ioaddr 9002, size 2: memtag 8000, iotag 8000: width 1280 linebytes 1280 height 1024 depth 8 Copyright (c) 1982, 1986, 1989, 1991, 1993 The Regents of the University of California. All rights reserved. Copyright (c) 1995-2013 OpenBSD. All rights reserved. http://www.OpenBSD.org OpenBSD 5.3-current (GENERIC.MP) #5: Thu May 23 09:02:44 CEST 2013 r...@www.stare.cz:/usr/src/sys/arch/macppc/compile/GENERIC.MP real mem = 1073741824 (1024MB) avail mem = 1032151040 (984MB) mainbus0 at root: model PowerMac10,2 cpu0 at mainbus0: 7447A (Revision 0x102): 1499 MHz: 512KB L2 cache mem0 at mainbus0 spdmem0 at mem0: 1GB DDR SDRAM non-parity PC3200CL3.0 memc0 at mainbus0: uni-n rev 0xd2 hw-clock at memc0 not configured kiic0 at memc0 offset 0xf8001000 iic0 at kiic0 mpcpcibr0 at mainbus0 pci: uni-north pci0 at mpcpcibr0 bus 0 pchb0 at pci0 dev 11 function 0 Apple UniNorth AGP rev 0x00 appleagp0 at pchb0 agp0 at appleagp0: aperture at 0x0, size 0x1000 vgafb0 at pci0 dev 16 function 0 ATI Radeon 9200 rev 0x01, mmio wsdisplay0 at vgafb0 mux 1: console (std, vt100 emulation) mpcpcibr1 at mainbus0 pci: uni-north pci1 at mpcpcibr1 bus 0 pchb1 at pci1 dev 11 function 0 Apple UniNorth PCI rev 0x00 bwi0 at pci1 dev 18 function 0 Broadcom BCM4318 rev 0x02: irq 52, address 00:11:24:bf:cb:2a macobio0 at pci1 dev 23 function 0 Apple Intrepid rev 0x00 openpic0 at macobio0 offset 0x4: version 0x4614 feature 3f0302 LE macgpio0 at macobio0 offset 0x50 modem-reset at macgpio0 offset 0x1d not configured modem-power at macgpio0 offset 0x1c not configured macgpio1 at macgpio0 offset 0x9 irq 47 programmer-switch at macgpio0 offset 0x11 not configured gpio5 at macgpio0 offset 0x6f not configured gpio6 at macgpio0 offset 0x70 not configured extint-gpio15 at macgpio0 offset 0x67 not configured escc-legacy at macobio0 offset 0x12000 not configured zsc0 at macobio0 offset 0x13000: irq 22,23 zstty0 at zsc0 channel 0 zstty1 at zsc0 channel 1 aoa0 at macobio0 offset 0x1: irq 30,1,2 audio0 at aoa0 timer at macobio0 offset 0x15000 not configured adb0 at macobio0 offset 0x16000apm0 at adb0: battery flags 0x0, 0% charged piic0 at adb0 iic1 at piic0 maxtmp0 at iic1 addr 0xc8: max6642 kiic1 at macobio0 offset 0x18000 iic2 at kiic1 wdc0 at macobio0 offset 0x2 irq 24: DMA ohci0 at pci1 dev 24 function 0 Apple Intrepid USB rev 0x00: couldn't map interrupt ohci1 at pci1 dev 25 function 0 Apple Intrepid USB rev 0x00: couldn't map interrupt ohci2 at pci1 dev 26 function 0 Apple Intrepid USB rev 0x00: irq 29, version 1.0, legacy support ohci3 at pci1 dev 27 function 0 NEC USB rev 0x43: irq 63, version 1.0 ohci4 at pci1 dev 27 function 1 NEC USB rev 0x43: irq 63, version 1.0 ehci0 at pci1 dev 27 function 2 NEC USB rev 0x04: irq 63 usb0 at ehci0: USB revision 2.0 uhub0 at usb0 NEC EHCI root hub rev 2.00/1.00 addr 1 usb1 at ohci2: USB revision 1.0 uhub1 at usb1 Apple OHCI root hub rev 1.00/1.00 addr 1 usb2 at ohci3: USB revision 1.0 uhub2 at usb2 NEC OHCI root hub rev 1.00/1.00 addr 1 usb3 at ohci4: USB revision 1.0 uhub3 at usb3 NEC OHCI root hub rev 1.00/1.00 addr 1 mpcpcibr2 at mainbus0 pci: uni-north pci2 at mpcpcibr2 bus 0 pchb2 at pci2 dev 11 function 0
Re: current/macppc on Mac Mini
What troubles me is that whatever device (device name) I try, it is the 'ofwboot' which is not found. I don't mind calling my disk 'cd' in the boot sequence or altering the devaliases, or setenv boot-device cd:,ofwboot, but that doesn't work either, as shown above. How can I make sure that the installer has actually put the ofwboot on my disk? I mean, the ofwboot is supposed to be _somewhere_ on my disk, right? Where? In the small DOS partition at the beginning of the disk?
Re: current/macppc on Mac Mini
On Sat, Jul 20, 2013 at 11:45:07AM +0200, Jan Stary wrote:
What troubles me is that whatever device (device name) I try,
it is the 'ofwboot' which is not found.
I don't mind calling my disk 'cd' in the boot sequence
or altering the devaliases, or setenv boot-device cd:,ofwboot,
but that doesn't work either, as shown above.
How can I make sure that the installer
has actually put the ofwboot on my disk?
I mean, the ofwboot is supposed to be _somewhere_
on my disk, right? Where? In the small DOS partition
at the beginning of the disk?
Yes. From macppc install.md:
md_installboot() {
local _disk=$1
# If there is an MSDOS partition on the boot disk, copy ofwboot
# into it.
if fdisk $_disk | grep -q 'Signature: 0xAA55'; then
if fdisk $_disk | grep -q '^..: 06 '; then
if mount /dev/${_disk}i /mnt2 /dev/null 21; then
# Use cat to avoid holes created by cp(1)
cat /mnt/usr/mdec/ofwboot /mnt2/ofwboot
umount /mnt2
fi
fi
fi
}
Ken
Re: current/macppc on Mac Mini
On Jul 20 11:23:01, kwesterb...@rogers.com wrote:
On Sat, Jul 20, 2013 at 11:45:07AM +0200, Jan Stary wrote:
What troubles me is that whatever device (device name) I try,
it is the 'ofwboot' which is not found.
I don't mind calling my disk 'cd' in the boot sequence
or altering the devaliases, or setenv boot-device cd:,ofwboot,
but that doesn't work either, as shown above.
How can I make sure that the installer
has actually put the ofwboot on my disk?
I mean, the ofwboot is supposed to be _somewhere_
on my disk, right? Where? In the small DOS partition
at the beginning of the disk?
Yes. From macppc install.md:
md_installboot() {
local _disk=$1
# If there is an MSDOS partition on the boot disk, copy ofwboot
# into it.
if fdisk $_disk | grep -q 'Signature: 0xAA55'; then
if fdisk $_disk | grep -q '^..: 06 '; then
if mount /dev/${_disk}i /mnt2 /dev/null 21; then
# Use cat to avoid holes created by cp(1)
cat /mnt/usr/mdec/ofwboot /mnt2/ofwboot
umount /mnt2
fi
fi
fi
}
Ha! This seems to assume that the (fdisk) DOS partition
is the 'i' partition in the disklabel - it is not;
I created a [c]ustom disklabel.
When in the install sequence is this copy of ofwboot done?
Even my real wd0i partition, which is /usr/xobj
(untouched since install) does not contain ofwboot.
That leads me to speculate that this ofwboot copy
is performed _before_ the installing user edits
the disklabel; but perhaps at that moment,
wd0i _is_ really the DOS partiton, and later
I can make the disklabel what I want?
Or did I miss it somewhere in the macppc install documentation
to leave 'i' alone so that ofwboot gets copied to the right place?
Anyway, I tried getting to that copy ofwboot now, as follows:
I enlarged the disklabel-maintained area to the whole disk ('b')
and created a partion for the DOS piece of the disk. Looking at
Disk: wd0 geometry: 155061/16/63 [156301488 Sectors]
Offset: 0 Signature: 0xAA55
Starting Ending LBA Info:
#: id C H S - C H S [ start:size ]
---
*0: 06 0 0 2 - 2 0 33 [ 1:2048 ] DOS 32MB
1: 00 0 0 0 - 0 0 0 [ 0: 0 ] unused
2: 00 0 0 0 - 0 0 0 [ 0: 0 ] unused
3: A6 4 1 2 - 155060 15 63 [4096: 156297392 ] OpenBSD
I made the DOS partition start at 512 (and then 1024
and then everything under 4096 wherethe obsd part starts),
but never could I mount that DOS partition ...
I will reinstall again, leaving the [a]uto disklabel untouched.
Re: current/macppc on Mac Mini
I made the DOS partition start at 512 (and then 1024 and then everything under 4096 wherethe obsd part starts), but never could I mount that DOS partition ... Silly me, it's 1, not 512; and it mounts, and the ofwboot is NOT there, and not in the wd0i as designated by me either. So there is no copy of ofwboot on my disk. That is surely wrong. I will reinstall again, leaving the [a]uto disklabel untouched. Yes, this creates an 'i' entry for the DOS partition, which gets the ofwboot alright, and I can boot it, - just have to call it cd:,ofwboot in my OpenFirmware (or setup a devalias). When I do edit the disklabel during the install, but leave the 'i' untouched, or set one up that spans the (fdisk) DOS partition, the ofwboot gets installed to the right place too. So my conclusion is that you _need_ to have this partition in your disklabel; right? And the hd/cd confusion of my OpenFirmware has nothing to do with this, right? That would make the following paragraph from INSTALL.macppc not entirely accurate: For dedicated disks, macppc port boots off a boot program in an MSDOS filesystem. This is set up by the install program and no special setup is required. If I am right, should the 'i' partition that seems to be needed for a proper copy of the ofwboot be mentioned in INSTALL.macppc or perhaps http://www.openbsd.org/faq/faq4.html#InstProb ? Would other architectures that require some special partition to boot be affected similarly? Jan
Re: current/macppc on Mac Mini
On Sat, Jul 20, 2013 at 08:23:35PM +0200, Jan Stary wrote:
On Jul 20 11:23:01, kwesterb...@rogers.com wrote:
On Sat, Jul 20, 2013 at 11:45:07AM +0200, Jan Stary wrote:
What troubles me is that whatever device (device name) I try,
it is the 'ofwboot' which is not found.
I don't mind calling my disk 'cd' in the boot sequence
or altering the devaliases, or setenv boot-device cd:,ofwboot,
but that doesn't work either, as shown above.
How can I make sure that the installer
has actually put the ofwboot on my disk?
I mean, the ofwboot is supposed to be _somewhere_
on my disk, right? Where? In the small DOS partition
at the beginning of the disk?
Yes. From macppc install.md:
md_installboot() {
local _disk=$1
# If there is an MSDOS partition on the boot disk, copy ofwboot
# into it.
if fdisk $_disk | grep -q 'Signature: 0xAA55'; then
if fdisk $_disk | grep -q '^..: 06 '; then
if mount /dev/${_disk}i /mnt2 /dev/null 21; then
# Use cat to avoid holes created by cp(1)
cat /mnt/usr/mdec/ofwboot /mnt2/ofwboot
umount /mnt2
fi
fi
fi
}
Ha! This seems to assume that the (fdisk) DOS partition
is the 'i' partition in the disklabel - it is not;
I created a [c]ustom disklabel.
It does make the assumption that the DOS partition is the first spoofed
partition, i.e. 'i'. This should probably be revisited since we relaxed
the rules on partition naming a while ago.
When in the install sequence is this copy of ofwboot done?
It's done at the very end in the finish_up() function in install.sub.
Even my real wd0i partition, which is /usr/xobj
(untouched since install) does not contain ofwboot.
Your wd0i isn't an MBR partition.
That leads me to speculate that this ofwboot copy
is performed _before_ the installing user edits
the disklabel; but perhaps at that moment,
wd0i _is_ really the DOS partiton, and later
I can make the disklabel what I want?
Nope. See above. :-)
Or did I miss it somewhere in the macppc install documentation
to leave 'i' alone so that ofwboot gets copied to the right place?
In INSTALL.macppc:
If you have DOS or Linux partitions defined on the disk, these will
usually show up as 'i', 'j', and so on.
and
If the disk is partitioned using MBR, the bootloader will be
automatically installed if you setup a small (a few MB) MSDOS
partition as position `i' in the label.
Anyway, I tried getting to that copy ofwboot now, as follows:
I enlarged the disklabel-maintained area to the whole disk ('b')
and created a partion for the DOS piece of the disk. Looking at
Disk: wd0 geometry: 155061/16/63 [156301488 Sectors]
Offset: 0 Signature: 0xAA55
Starting Ending LBA Info:
#: id C H S - C H S [ start:size ]
---
*0: 06 0 0 2 - 2 0 33 [ 1:2048 ] DOS
32MB
1: 00 0 0 0 - 0 0 0 [ 0: 0 ] unused
2: 00 0 0 0 - 0 0 0 [ 0: 0 ] unused
3: A6 4 1 2 - 155060 15 63 [4096: 156297392 ] OpenBSD
I made the DOS partition start at 512 (and then 1024
and then everything under 4096 wherethe obsd part starts),
but never could I mount that DOS partition ...
I will reinstall again, leaving the [a]uto disklabel untouched.
Good plan.
Ken
Re: current/macppc on Mac Mini
On 23/05/13(Thu) 17:00, Miod Vallat wrote:
Were you thinking of something like that? It works for me (c) tm, with
my PowerBooks (disk@0/wd0), I haven't tried NFS boot yet.
Not exactly, but your version is probably better than what I was
thinking of. However, it will not allow for root on the second wd disk
of a controller, or on any secondary pciide controller.
Borrowing the sparc64 logic is a larger work but less error-prone.
Indeed it is, but until someone does it, here's a slightly improved
version that adds a check for the drive number.
Jan does is still work for you?
Index: macppc//autoconf.c
===
RCS file: /cvs/src/sys/arch/macppc/macppc/autoconf.c,v
retrieving revision 1.39
diff -u -p -r1.39 autoconf.c
--- macppc//autoconf.c 11 Nov 2010 17:58:21 - 1.39
+++ macppc//autoconf.c 29 May 2013 23:17:42 -
@@ -62,13 +62,12 @@
#include sys/disk.h
#include scsi/scsi_all.h
-#include scsi/scsi_disk.h
#include scsi/scsiconf.h
-#include scsi/sdvar.h
+#include dev/ata/atavar.h
void dumpconf(void);
static struct devmap *findtype(char **);
-void makebootdev(char *cp);
+void parseofwbp(char *);
intgetpno(char **);
/*
@@ -79,6 +78,9 @@ int getpno(char **);
intcold = 1; /* if 1, still working on cold-start */
char bootdev[16];/* to hold boot dev name */
struct device *bootdv = NULL;
+enum devclass bootdev_class = DV_DULL;
+intbootdev_type = 0;
+intbootdev_unit = 0;
struct dumpmem dumpmem[VM_PHYSSEG_MAX];
u_int ndumpmem;
@@ -165,9 +167,9 @@ findtype(char **s)
* '/ht@0,f200/pci@2/bcom5704@4/bsd'
*/
void
-makebootdev(char *bp)
+parseofwbp(char *bp)
{
- int unit, ptype;
+ int ptype;
char *dev, *cp;
struct devmap *dp;
@@ -184,6 +186,8 @@ makebootdev(char *bp)
} while((dp-type T_IFACE) == 0);
if (dp-att dp-type == T_IFACE) {
+ bootdev_class = DV_IFNET;
+ bootdev_type = dp-type;
strlcpy(bootdev, dp-dev, sizeof bootdev);
return;
}
@@ -193,24 +197,9 @@ makebootdev(char *bp)
ptype = dp-type;
dp = findtype(cp);
if (dp-att dp-type == T_DISK) {
- unit = getpno(cp);
- if (ptype == T_SCSI) {
- struct device *dv;
- struct sd_softc *sd;
-
- TAILQ_FOREACH(dv, alldevs, dv_list) {
- if (dv-dv_class != DV_DISK ||
- strcmp(dv-dv_cfdata-cf_driver-cd_name,
sd))
- continue;
- sd = (struct sd_softc *)dv;
- if (sd-sc_link-target != unit)
- continue;
- snprintf(bootdev, sizeof bootdev,
- %s%c, dv-dv_xname, 'a');
- return;
- }
- }
- snprintf(bootdev, sizeof bootdev, %s%d%c, dev, unit, 'a');
+ bootdev_class = DV_DISK;
+ bootdev_type = ptype;
+ bootdev_unit = getpno(cp);
return;
}
printf(Warning: boot device unrecognized: %s\n, bp);
@@ -239,25 +228,43 @@ getpno(char **cp)
void
device_register(struct device *dev, void *aux)
{
+ const char *drvrname = dev-dv_cfdata-cf_driver-cd_name;
+ const char *name = dev-dv_xname;
+
+ if (bootdv != NULL || dev-dv_class != bootdev_class)
+ return;
+
+ switch (bootdev_type) {
+ case T_SCSI:
+ if (strcmp(drvrname, sd) == 0) {
+ struct scsi_attach_args *sa = aux;
+
+ if (sa-sa_sc_link-target == bootdev_unit)
+ bootdv = dev;
+ }
+ case T_IDE:
+ if (strcmp(drvrname, wd) == 0) {
+ struct ata_atapi_attach *aa = aux;
+
+ if (aa-aa_drv_data-drive == bootdev_unit)
+ bootdv = dev;
+ }
+ break;
+ case T_IFACE:
+ if (strcmp(name, bootdev) == 0)
+ bootdv = dev;
+ break;
+ default:
+ break;
+ }
}
-/*
- * Now that we are fully operational, we can checksum the
- * disks, and using some heuristics, hopefully are able to
- * always determine the correct root disk.
- */
void
diskconf(void)
{
- dev_t temp;
- int part = 0;
-
printf(bootpath: %s\n, bootpath);
- makebootdev(bootpath);
- /* Lookup boot device from boot if not set by configuration */
- bootdv = parsedisk(bootdev, strlen(bootdev), 0, temp);
- setroot(bootdv, part, RB_USERREQ);
+ setroot(bootdv, 0, RB_USERREQ);
dumpconf();
}
Index:
Re: current/macppc on Mac Mini
On 26/12/12(Wed) 20:54, Miod Vallat wrote:
Just upgraded to a current again, with the same problem,
and the same solution:
[...]
wdc1 at kauaiata0 irq 39: DMA
atapiscsi0 at wdc1 channel 0 drive 0
scsibus0 at atapiscsi0: 2 targets
cd0 at scsibus0 targ 0 lun 0: MATSHITA, DVD-R UJ-825, DAND ATAPI 5/cdrom
removable
wd0 at wdc1 channel 0 drive 1: ST9808211A
wd0: 16-sector PIO, LBA, 76319MB, 156301488 sectors
[...]
bootpath: /pci@f400/ata-6@d/disk@1:/bsd
I think I understand what goes wrong. The code responsible for matching
the boot device to the actual kernel device on macppc is quite crude,
especially for non-SCSI disks.
Your bootpath specifies `disk@1' because the disk drive is the second
device (slave) on the ATA channel, the cdrom drive being master.
However, the kernel wants to match this information against a `wd1'
device (as if there were two hard disks on the ATA channel).
The kernel code needs to be fixed to use device_register() to match the
boot path against actual attachment information, instead of walking the
device tree at the end of autoconf. If nobody beats me to do this, I'll
try to cook a diff in a few days.
Were you thinking of something like that? It works for me (c) tm, with
my PowerBooks (disk@0/wd0), I haven't tried NFS boot yet.
Jan, does it improve something for you?
Index: autoconf.c
===
RCS file: /cvs/src/sys/arch/macppc/macppc/autoconf.c,v
retrieving revision 1.39
diff -u -p -r1.39 autoconf.c
--- autoconf.c 11 Nov 2010 17:58:21 - 1.39
+++ autoconf.c 22 May 2013 19:00:45 -
@@ -68,7 +68,7 @@
void dumpconf(void);
static struct devmap *findtype(char **);
-void makebootdev(char *cp);
+void parseofwbp(char *);
intgetpno(char **);
/*
@@ -79,6 +79,9 @@ int getpno(char **);
intcold = 1; /* if 1, still working on cold-start */
char bootdev[16];/* to hold boot dev name */
struct device *bootdv = NULL;
+enum devclass bootdev_class = DV_DULL;
+intbootdev_type = 0;
+intbootdev_unit = 0;
struct dumpmem dumpmem[VM_PHYSSEG_MAX];
u_int ndumpmem;
@@ -165,9 +168,9 @@ findtype(char **s)
* '/ht@0,f200/pci@2/bcom5704@4/bsd'
*/
void
-makebootdev(char *bp)
+parseofwbp(char *bp)
{
- int unit, ptype;
+ int ptype;
char *dev, *cp;
struct devmap *dp;
@@ -184,6 +187,8 @@ makebootdev(char *bp)
} while((dp-type T_IFACE) == 0);
if (dp-att dp-type == T_IFACE) {
+ bootdev_class = DV_IFNET;
+ bootdev_type = dp-type;
strlcpy(bootdev, dp-dev, sizeof bootdev);
return;
}
@@ -193,24 +198,9 @@ makebootdev(char *bp)
ptype = dp-type;
dp = findtype(cp);
if (dp-att dp-type == T_DISK) {
- unit = getpno(cp);
- if (ptype == T_SCSI) {
- struct device *dv;
- struct sd_softc *sd;
-
- TAILQ_FOREACH(dv, alldevs, dv_list) {
- if (dv-dv_class != DV_DISK ||
- strcmp(dv-dv_cfdata-cf_driver-cd_name,
sd))
- continue;
- sd = (struct sd_softc *)dv;
- if (sd-sc_link-target != unit)
- continue;
- snprintf(bootdev, sizeof bootdev,
- %s%c, dv-dv_xname, 'a');
- return;
- }
- }
- snprintf(bootdev, sizeof bootdev, %s%d%c, dev, unit, 'a');
+ bootdev_class = DV_DISK;
+ bootdev_type = ptype;
+ bootdev_unit = getpno(cp);
return;
}
printf(Warning: boot device unrecognized: %s\n, bp);
@@ -239,25 +229,44 @@ getpno(char **cp)
void
device_register(struct device *dev, void *aux)
{
+ const char *drvrname = dev-dv_cfdata-cf_driver-cd_name;
+ const char *name = dev-dv_xname;
+
+ if (bootdv != NULL || dev-dv_class != bootdev_class)
+ return;
+
+ switch (bootdev_type) {
+ case T_SCSI:
+ if (strcmp(drvrname, sd) == 0) {
+ struct sd_softc *sd = (struct sd_softc *)dev;
+
+ if (sd-sc_link-target == bootdev_unit)
+ bootdv = dev;
+ }
+ case T_IDE:
+ /*
+* Do not require the bootpath unit number to match
+* against the driver's one, a slave disk on the ATA
+* channel `disk@1' can attach as `wd0'.
+*/
+ if (strcmp(drvrname, wd) == 0)
+ bootdv = dev;
+ break;
+ case T_IFACE:
+ if (strcmp(name, bootdev) == 0)
+
Re: current/macppc on Mac Mini
On May 23 08:41:50, mpieuc...@nolizard.org wrote: On 26/12/12(Wed) 20:54, Miod Vallat wrote: Just upgraded to a current again, with the same problem, and the same solution: [...] wdc1 at kauaiata0 irq 39: DMA atapiscsi0 at wdc1 channel 0 drive 0 scsibus0 at atapiscsi0: 2 targets cd0 at scsibus0 targ 0 lun 0: MATSHITA, DVD-R UJ-825, DAND ATAPI 5/cdrom removable wd0 at wdc1 channel 0 drive 1: ST9808211A wd0: 16-sector PIO, LBA, 76319MB, 156301488 sectors [...] bootpath: /pci@f400/ata-6@d/disk@1:/bsd I think I understand what goes wrong. The code responsible for matching the boot device to the actual kernel device on macppc is quite crude, especially for non-SCSI disks. Your bootpath specifies `disk@1' because the disk drive is the second device (slave) on the ATA channel, the cdrom drive being master. However, the kernel wants to match this information against a `wd1' device (as if there were two hard disks on the ATA channel). The kernel code needs to be fixed to use device_register() to match the boot path against actual attachment information, instead of walking the device tree at the end of autoconf. If nobody beats me to do this, I'll try to cook a diff in a few days. Were you thinking of something like that? It works for me (c) tm, with my PowerBooks (disk@0/wd0), I haven't tried NFS boot yet. Jan, does it improve something for you? Yes it does: with this patch, I don't need to hardcode config bsd root on wd0a into my kernel, it figures the bootpath itself. Thank you! Jan [ using 500872 bytes of bsd ELF symbol table ] console out [ATY,RockHopper2_A]console in [keyboard] , using USB using parent ATY,RockHopper2Paren:: memaddr 9800 size 800, : consaddr 9c008000, : ioaddr 9002, size 2: memtag 8000, iotag 8000: width 1280 linebytes 1280 height 1024 depth 8 Copyright (c) 1982, 1986, 1989, 1991, 1993 The Regents of the University of California. All rights reserved. Copyright (c) 1995-2013 OpenBSD. All rights reserved. http://www.OpenBSD.org OpenBSD 5.3-current (GENERIC.MP) #5: Thu May 23 09:02:44 CEST 2013 r...@www.stare.cz:/usr/src/sys/arch/macppc/compile/GENERIC.MP real mem = 1073741824 (1024MB) avail mem = 1032151040 (984MB) mainbus0 at root: model PowerMac10,2 cpu0 at mainbus0: 7447A (Revision 0x102): 1499 MHz: 512KB L2 cache mem0 at mainbus0 spdmem0 at mem0: 1GB DDR SDRAM non-parity PC3200CL3.0 memc0 at mainbus0: uni-n rev 0xd2 hw-clock at memc0 not configured kiic0 at memc0 offset 0xf8001000 iic0 at kiic0 mpcpcibr0 at mainbus0 pci: uni-north pci0 at mpcpcibr0 bus 0 pchb0 at pci0 dev 11 function 0 Apple UniNorth AGP rev 0x00 appleagp0 at pchb0 agp0 at appleagp0: aperture at 0x0, size 0x1000 vgafb0 at pci0 dev 16 function 0 ATI Radeon 9200 rev 0x01, mmio wsdisplay0 at vgafb0 mux 1: console (std, vt100 emulation) mpcpcibr1 at mainbus0 pci: uni-north pci1 at mpcpcibr1 bus 0 pchb1 at pci1 dev 11 function 0 Apple UniNorth PCI rev 0x00 bwi0 at pci1 dev 18 function 0 Broadcom BCM4318 rev 0x02: irq 52, address 00:11:24:bf:cb:2a macobio0 at pci1 dev 23 function 0 Apple Intrepid rev 0x00 openpic0 at macobio0 offset 0x4: version 0x4614 feature 3f0302 LE macgpio0 at macobio0 offset 0x50 modem-reset at macgpio0 offset 0x1d not configured modem-power at macgpio0 offset 0x1c not configured macgpio1 at macgpio0 offset 0x9 irq 47 programmer-switch at macgpio0 offset 0x11 not configured gpio5 at macgpio0 offset 0x6f not configured gpio6 at macgpio0 offset 0x70 not configured extint-gpio15 at macgpio0 offset 0x67 not configured escc-legacy at macobio0 offset 0x12000 not configured zsc0 at macobio0 offset 0x13000: irq 22,23 zstty0 at zsc0 channel 0 zstty1 at zsc0 channel 1 aoa0 at macobio0 offset 0x1: irq 30,1,2 audio0 at aoa0 timer at macobio0 offset 0x15000 not configured adb0 at macobio0 offset 0x16000apm0 at adb0: battery flags 0x0, 0% charged piic0 at adb0 iic1 at piic0 maxtmp0 at iic1 addr 0xc8: max6642 kiic1 at macobio0 offset 0x18000 iic2 at kiic1 wdc0 at macobio0 offset 0x2 irq 24: DMA ohci0 at pci1 dev 24 function 0 Apple Intrepid USB rev 0x00: couldn't map interrupt ohci1 at pci1 dev 25 function 0 Apple Intrepid USB rev 0x00: couldn't map interrupt ohci2 at pci1 dev 26 function 0 Apple Intrepid USB rev 0x00: irq 29, version 1.0, legacy support ohci3 at pci1 dev 27 function 0 NEC USB rev 0x43: irq 63, version 1.0 ohci4 at pci1 dev 27 function 1 NEC USB rev 0x43: irq 63, version 1.0 ehci0 at pci1 dev 27 function 2 NEC USB rev 0x04: irq 63 usb0 at ehci0: USB revision 2.0 uhub0 at usb0 NEC EHCI root hub rev 2.00/1.00 addr 1 usb1 at ohci2: USB revision 1.0 uhub1 at usb1 Apple OHCI root hub rev 1.00/1.00 addr 1 usb2 at ohci3: USB revision 1.0 uhub2 at usb2 NEC OHCI root hub rev 1.00/1.00 addr 1 usb3 at ohci4: USB revision 1.0 uhub3 at usb3 NEC OHCI root hub rev 1.00/1.00 addr 1 mpcpcibr2 at mainbus0 pci: uni-north pci2 at mpcpcibr2 bus 0 pchb2 at pci2 dev
Re: current/macppc on Mac Mini
Were you thinking of something like that? It works for me (c) tm, with
my PowerBooks (disk@0/wd0), I haven't tried NFS boot yet.
Not exactly, but your version is probably better than what I was
thinking of. However, it will not allow for root on the second wd disk
of a controller, or on any secondary pciide controller.
Borrowing the sparc64 logic is a larger work but less error-prone.
Miod
Index: autoconf.c
===
RCS file: /cvs/src/sys/arch/macppc/macppc/autoconf.c,v
retrieving revision 1.39
diff -u -p -r1.39 autoconf.c
--- autoconf.c11 Nov 2010 17:58:21 - 1.39
+++ autoconf.c22 May 2013 19:00:45 -
@@ -68,7 +68,7 @@
void dumpconf(void);
static struct devmap *findtype(char **);
-void makebootdev(char *cp);
+void parseofwbp(char *);
int getpno(char **);
/*
@@ -79,6 +79,9 @@ int getpno(char **);
int cold = 1; /* if 1, still working on cold-start */
char bootdev[16];/* to hold boot dev name */
struct device *bootdv = NULL;
+enum devclass bootdev_class = DV_DULL;
+int bootdev_type = 0;
+int bootdev_unit = 0;
struct dumpmem dumpmem[VM_PHYSSEG_MAX];
u_int ndumpmem;
@@ -165,9 +168,9 @@ findtype(char **s)
*'/ht@0,f200/pci@2/bcom5704@4/bsd'
*/
void
-makebootdev(char *bp)
+parseofwbp(char *bp)
{
- int unit, ptype;
+ int ptype;
char *dev, *cp;
struct devmap *dp;
@@ -184,6 +187,8 @@ makebootdev(char *bp)
} while((dp-type T_IFACE) == 0);
if (dp-att dp-type == T_IFACE) {
+ bootdev_class = DV_IFNET;
+ bootdev_type = dp-type;
strlcpy(bootdev, dp-dev, sizeof bootdev);
return;
}
@@ -193,24 +198,9 @@ makebootdev(char *bp)
ptype = dp-type;
dp = findtype(cp);
if (dp-att dp-type == T_DISK) {
- unit = getpno(cp);
- if (ptype == T_SCSI) {
- struct device *dv;
- struct sd_softc *sd;
-
- TAILQ_FOREACH(dv, alldevs, dv_list) {
- if (dv-dv_class != DV_DISK ||
- strcmp(dv-dv_cfdata-cf_driver-cd_name,
sd))
- continue;
- sd = (struct sd_softc *)dv;
- if (sd-sc_link-target != unit)
- continue;
- snprintf(bootdev, sizeof bootdev,
- %s%c, dv-dv_xname, 'a');
- return;
- }
- }
- snprintf(bootdev, sizeof bootdev, %s%d%c, dev, unit, 'a');
+ bootdev_class = DV_DISK;
+ bootdev_type = ptype;
+ bootdev_unit = getpno(cp);
return;
}
printf(Warning: boot device unrecognized: %s\n, bp);
@@ -239,25 +229,44 @@ getpno(char **cp)
void
device_register(struct device *dev, void *aux)
{
+ const char *drvrname = dev-dv_cfdata-cf_driver-cd_name;
+ const char *name = dev-dv_xname;
+
+ if (bootdv != NULL || dev-dv_class != bootdev_class)
+ return;
+
+ switch (bootdev_type) {
+ case T_SCSI:
+ if (strcmp(drvrname, sd) == 0) {
+ struct sd_softc *sd = (struct sd_softc *)dev;
+
+ if (sd-sc_link-target == bootdev_unit)
+ bootdv = dev;
+ }
+ case T_IDE:
+ /*
+ * Do not require the bootpath unit number to match
+ * against the driver's one, a slave disk on the ATA
+ * channel `disk@1' can attach as `wd0'.
+ */
+ if (strcmp(drvrname, wd) == 0)
+ bootdv = dev;
+ break;
+ case T_IFACE:
+ if (strcmp(name, bootdev) == 0)
+ bootdv = dev;
+ break;
+ default:
+ break;
+ }
}
-/*
- * Now that we are fully operational, we can checksum the
- * disks, and using some heuristics, hopefully are able to
- * always determine the correct root disk.
- */
void
diskconf(void)
{
- dev_t temp;
- int part = 0;
-
printf(bootpath: %s\n, bootpath);
- makebootdev(bootpath);
- /* Lookup boot device from boot if not set by configuration */
- bootdv = parsedisk(bootdev, strlen(bootdev), 0, temp);
- setroot(bootdv, part, RB_USERREQ);
+ setroot(bootdv, 0, RB_USERREQ);
dumpconf();
}
Index: machdep.c
===
RCS file: /cvs/src/sys/arch/macppc/macppc/machdep.c,v
retrieving revision 1.135
diff -u -p -r1.135 machdep.c
--- machdep.c 6 Dec 2012 12:35:22 - 1.135
+++ machdep.c 22 May 2013 18:24:25 -
@@ -114,6
Re: current/macppc on Mac Mini
On Jun 13 14:12:45, h...@stare.cz wrote: This is current/macppc on a late 2005 Mac Mini, which is PowerMac10,2. I needed to hardcode the root device into the kernel config, otherwise boot stops with unknown root device, as discussed in the misc thread that starts at http://marc.info/?l=openbsd-miscm=133932614509618w=2 - probably a discrepancy in what ofw passes to the kernel. Just upgraded to a current again, with the same problem, and the same solution: Index: GENERIC === RCS file: /cvs/src/sys/arch/macppc/conf/GENERIC,v retrieving revision 1.216 diff -u -p -r1.216 GENERIC --- GENERIC 4 Dec 2012 10:58:05 - 1.216 +++ GENERIC 26 Dec 2012 14:46:06 - @@ -27,7 +27,7 @@ optionWSDISPLAY_COMPAT_RAWKBD # provid option USER_PCICONF# user-space PCI configuration -config bsd swap generic +config bsd root on wd0a mainbus0 at root cpu* at mainbus0 [ using 501892 bytes of bsd ELF symbol table ] console out [ATY,RockHopper2_A]console in [keyboard] , using USB using parent ATY,RockHopper2Paren:: memaddr 9800 size 800, : consaddr 9c008000, : ioaddr 9002, size 2: memtag 8000, iotag 8000: width 800 linebytes 1024 height 600 depth 8 Copyright (c) 1982, 1986, 1989, 1991, 1993 The Regents of the University of California. All rights reserved. Copyright (c) 1995-2012 OpenBSD. All rights reserved. http://www.OpenBSD.org OpenBSD 5.2-current (GENERIC.MP) #4: Wed Dec 26 15:08:07 CET 2012 r...@www.stare.cz:/usr/src/sys/arch/macppc/compile/GENERIC.MP real mem = 1073741824 (1024MB) avail mem = 1032146944 (984MB) mainbus0 at root: model PowerMac10,2 cpu0 at mainbus0: 7447A (Revision 0x102): 1499 MHz: 512KB L2 cache mem0 at mainbus0 spdmem0 at mem0: 1GB DDR SDRAM non-parity PC3200CL3.0 memc0 at mainbus0: uni-n rev 0xd2 hw-clock at memc0 not configured kiic0 at memc0 offset 0xf8001000 iic0 at kiic0 mpcpcibr0 at mainbus0 pci: uni-north, Revision 0xff pci0 at mpcpcibr0 bus 0 pchb0 at pci0 dev 11 function 0 Apple UniNorth AGP rev 0x00 appleagp0 at pchb0 agp0 at appleagp0: aperture at 0x0, size 0x1000 vgafb0 at pci0 dev 16 function 0 ATI Radeon 9200 rev 0x01, mmio wsdisplay0 at vgafb0 mux 1: console (std, vt100 emulation) mpcpcibr1 at mainbus0 pci: uni-north, Revision 0x5 pci1 at mpcpcibr1 bus 0 pchb1 at pci1 dev 11 function 0 Apple UniNorth PCI rev 0x00 bwi0 at pci1 dev 18 function 0 Broadcom BCM4318 rev 0x02: irq 52, address 00:11:24:bf:cb:2a macobio0 at pci1 dev 23 function 0 Apple Intrepid rev 0x00 openpic0 at macobio0 offset 0x4: version 0x4614 feature 3f0302 LE macgpio0 at macobio0 offset 0x50 modem-reset at macgpio0 offset 0x1d not configured modem-power at macgpio0 offset 0x1c not configured macgpio1 at macgpio0 offset 0x9 irq 47 programmer-switch at macgpio0 offset 0x11 not configured gpio5 at macgpio0 offset 0x6f not configured gpio6 at macgpio0 offset 0x70 not configured extint-gpio15 at macgpio0 offset 0x67 not configured escc-legacy at macobio0 offset 0x12000 not configured zsc0 at macobio0 offset 0x13000: irq 22,23 zstty0 at zsc0 channel 0 zstty1 at zsc0 channel 1 aoa0 at macobio0 offset 0x1: irq 30,1,2 audio0 at aoa0 timer at macobio0 offset 0x15000 not configured adb0 at macobio0 offset 0x16000 irq 25: via-pmu, 0 targets apm0 at adb0: battery flags 0x0, 0% charged piic0 at adb0 iic1 at piic0 maxtmp0 at iic1 addr 0xc8: max6642 kiic1 at macobio0 offset 0x18000 iic2 at kiic1 wdc0 at macobio0 offset 0x2 irq 24: DMA ohci0 at pci1 dev 24 function 0 Apple Intrepid USB rev 0x00: couldn't map interrupt ohci1 at pci1 dev 25 function 0 Apple Intrepid USB rev 0x00: couldn't map interrupt ohci2 at pci1 dev 26 function 0 Apple Intrepid USB rev 0x00: irq 29, version 1.0, legacy support ohci3 at pci1 dev 27 function 0 NEC USB rev 0x43: irq 63, version 1.0 ohci4 at pci1 dev 27 function 1 NEC USB rev 0x43: irq 63, version 1.0 ehci0 at pci1 dev 27 function 2 NEC USB rev 0x04: irq 63 usb0 at ehci0: USB revision 2.0 uhub0 at usb0 NEC EHCI root hub rev 2.00/1.00 addr 1 usb1 at ohci2: USB revision 1.0 uhub1 at usb1 Apple OHCI root hub rev 1.00/1.00 addr 1 usb2 at ohci3: USB revision 1.0 uhub2 at usb2 NEC OHCI root hub rev 1.00/1.00 addr 1 usb3 at ohci4: USB revision 1.0 uhub3 at usb3 NEC OHCI root hub rev 1.00/1.00 addr 1 mpcpcibr2 at mainbus0 pci: uni-north, Revision 0x6 pci2 at mpcpcibr2 bus 0 pchb2 at pci2 dev 11 function 0 Apple UniNorth PCI rev 0x00 kauaiata0 at pci2 dev 13 function 0 Apple Intrepid ATA rev 0x00 wdc1 at kauaiata0 irq 39: DMA atapiscsi0 at wdc1 channel 0 drive 0 scsibus0 at atapiscsi0: 2 targets cd0 at scsibus0 targ 0 lun 0: MATSHITA, DVD-R UJ-825, DAND ATAPI 5/cdrom removable wd0 at wdc1 channel 0 drive 1: ST9808211A wd0: 16-sector PIO, LBA, 76319MB, 156301488 sectors cd0(wdc1:0:0): using PIO mode 4, DMA mode 2, Ultra-DMA mode 4 wd0(wdc1:0:1): using PIO mode 4, DMA mode 2, Ultra-DMA mode 4 Apple UniNorth
Re: current/macppc on Mac Mini
Just upgraded to a current again, with the same problem, and the same solution: [...] wdc1 at kauaiata0 irq 39: DMA atapiscsi0 at wdc1 channel 0 drive 0 scsibus0 at atapiscsi0: 2 targets cd0 at scsibus0 targ 0 lun 0: MATSHITA, DVD-R UJ-825, DAND ATAPI 5/cdrom removable wd0 at wdc1 channel 0 drive 1: ST9808211A wd0: 16-sector PIO, LBA, 76319MB, 156301488 sectors [...] bootpath: /pci@f400/ata-6@d/disk@1:/bsd I think I understand what goes wrong. The code responsible for matching the boot device to the actual kernel device on macppc is quite crude, especially for non-SCSI disks. Your bootpath specifies `disk@1' because the disk drive is the second device (slave) on the ATA channel, the cdrom drive being master. However, the kernel wants to match this information against a `wd1' device (as if there were two hard disks on the ATA channel). The kernel code needs to be fixed to use device_register() to match the boot path against actual attachment information, instead of walking the device tree at the end of autoconf. If nobody beats me to do this, I'll try to cook a diff in a few days. Miod
apple : mac : mini : intel : core i5 : 5.2 : support?
would it be there? http://www.openbsd.org/plat.html shows nothing. googling around too showed information not upto date (from my location). need a reliable desktop system with a good resale value, hence a mac mini. :) thanks. -- simplicity can be marvelously powerful. - rahul jindal
Re: apple : mac : mini : intel : core i5 : 5.2 : support?
OpenBSD/amd64 and OpenBSD/i386 both support Core i5 based machines. Mayuresh Kathe [mayur...@kathe.in] wrote: would it be there? http://www.openbsd.org/plat.html shows nothing. googling around too showed information not upto date (from my location). need a reliable desktop system with a good resale value, hence a mac mini. :) thanks. -- simplicity can be marvelously powerful. - rahul jindal -- Keep them laughing half the time, scared of you the other half. And always keep them guessing. -- Clair George
Re: apple : mac : mini : intel : core i5 : 5.2 : support?
On Jul 11 20:56:24, Mayuresh Kathe wrote: would it be there? http://www.openbsd.org/plat.html shows nothing. googling around too showed information not upto date (from my location). need a reliable desktop system with a good resale value, hence a mac mini. :) Mine is not core i5, but runs 5.1 happily. Jan # uname -a OpenBSD mini.stare.cz 5.1 GENERIC#0 macppc # dmesg [ using 496832 bytes of bsd ELF symbol table ] console out [ATY,RockHopper2_A]console in [keyboard] , using USB using parent ATY,RockHopper2Paren:: memaddr 9800 size 800, : consaddr 9c008000, : ioaddr 9002, size 2: memtag 8000, iotag 8000: width 800 linebytes 1024 height 600 depth 8 Copyright (c) 1982, 1986, 1989, 1991, 1993 The Regents of the University of California. All rights reserved. Copyright (c) 1995-2012 OpenBSD. All rights reserved. http://www.OpenBSD.org uvm_km_kmem_grow: grown to 0xee00 OpenBSD 5.1-current (GENERIC) #0: Wed Jun 13 02:07:49 CEST 2012 r...@mini.stare.cz:/usr/src/sys/arch/macppc/compile/GENERIC real mem = 1073741824 (1024MB) avail mem = 1032196096 (984MB) mainbus0 at root: model PowerMac10,2 cpu0 at mainbus0: 7447A (Revision 0x102): 1499 MHz: 512KB L2 cache mem0 at mainbus0 spdmem0 at mem0: 1GB DDR SDRAM non-parity PC3200CL3.0 memc0 at mainbus0: uni-n hw-clock at memc0 not configured kiic0 at memc0 offset 0xf8001000 iic0 at kiic0 mpcpcibr0 at mainbus0 pci: uni-north, Revision 0xff pci0 at mpcpcibr0 bus 0 pchb0 at pci0 dev 11 function 0 Apple UniNorth AGP rev 0x00 vgafb0 at pci0 dev 16 function 0 ATI Radeon 9200 rev 0x01, mmio wsdisplay0 at vgafb0 mux 1: console (std, vt100 emulation) mpcpcibr1 at mainbus0 pci: uni-north, Revision 0x5 pci1 at mpcpcibr1 bus 0 pchb1 at pci1 dev 11 function 0 Apple UniNorth PCI rev 0x00 bwi0 at pci1 dev 18 function 0 Broadcom BCM4318 rev 0x02: irq 52, address 00:11:24:bf:cb:2a macobio0 at pci1 dev 23 function 0 Apple Intrepid rev 0x00 openpic0 at macobio0 offset 0x4: version 0x4614 feature 3f0302 LE macgpio0 at macobio0 offset 0x50 modem-reset at macgpio0 offset 0x1d not configured modem-power at macgpio0 offset 0x1c not configured macgpio1 at macgpio0 offset 0x9 irq 47 programmer-switch at macgpio0 offset 0x11 not configured gpio5 at macgpio0 offset 0x6f not configured gpio6 at macgpio0 offset 0x70 not configured extint-gpio15 at macgpio0 offset 0x67 not configured escc-legacy at macobio0 offset 0x12000 not configured zsc0 at macobio0 offset 0x13000: irq 22,23 zstty0 at zsc0 channel 0 zstty1 at zsc0 channel 1 aoa0 at macobio0 offset 0x1: irq 30,1,2 audio0 at aoa0 timer at macobio0 offset 0x15000 not configured adb0 at macobio0 offset 0x16000 irq 25: via-pmu, 0 targets apm0 at adb0: battery flags 0x0, 0% charged piic0 at adb0 iic1 at piic0 maxtmp0 at iic1 addr 0xc8: max6642 kiic1 at macobio0 offset 0x18000 iic2 at kiic1 wdc0 at macobio0 offset 0x2 irq 24: DMA ohci0 at pci1 dev 24 function 0 Apple Intrepid USB rev 0x00: couldn't map interrupt ohci1 at pci1 dev 25 function 0 Apple Intrepid USB rev 0x00: couldn't map interrupt ohci2 at pci1 dev 26 function 0 Apple Intrepid USB rev 0x00: irq 29, version 1.0, legacy support ohci3 at pci1 dev 27 function 0 NEC USB rev 0x43: irq 63, version 1.0 ohci4 at pci1 dev 27 function 1 NEC USB rev 0x43: irq 63, version 1.0 ehci0 at pci1 dev 27 function 2 NEC USB rev 0x04: irq 63 usb0 at ehci0: USB revision 2.0 uhub0 at usb0 NEC EHCI root hub rev 2.00/1.00 addr 1 usb1 at ohci2: USB revision 1.0 uhub1 at usb1 Apple OHCI root hub rev 1.00/1.00 addr 1 usb2 at ohci3: USB revision 1.0 uhub2 at usb2 NEC OHCI root hub rev 1.00/1.00 addr 1 usb3 at ohci4: USB revision 1.0 uhub3 at usb3 NEC OHCI root hub rev 1.00/1.00 addr 1 mpcpcibr2 at mainbus0 pci: uni-north, Revision 0x6 pci2 at mpcpcibr2 bus 0 pchb2 at pci2 dev 11 function 0 Apple UniNorth PCI rev 0x00 kauaiata0 at pci2 dev 13 function 0 Apple Intrepid ATA rev 0x00 wdc1 at kauaiata0 irq 39: DMA atapiscsi0 at wdc1 channel 0 drive 0 scsibus0 at atapiscsi0: 2 targets cd0 at scsibus0 targ 0 lun 0: MATSHITA, DVD-R UJ-825, DAND ATAPI 5/cdrom removable wd0 at wdc1 channel 0 drive 1: ST9808211A wd0: 16-sector PIO, LBA, 76319MB, 156301488 sectors cd0(wdc1:0:0): using PIO mode 4, DMA mode 2, Ultra-DMA mode 4 wd0(wdc1:0:1): using PIO mode 4, DMA mode 2, Ultra-DMA mode 4 Apple UniNorth Firewire rev 0x81 at pci2 dev 14 function 0 not configured gem0 at pci2 dev 15 function 0 Apple Uni-N2 GMAC rev 0x80: irq 41, address 00:14:51:17:42:34 bmtphy0 at gem0 phy 0: BCM5221 100baseTX PHY, rev. 4 uhidev0 at uhub1 port 1 configuration 1 interface 0 Apple Computer HID-proxy rev 2.00/19.65 addr 2 uhidev0: iclass 3/1 ukbd0 at uhidev0: 8 modifier keys, 6 key codes wskbd0 at ukbd0: console keyboard, using wsdisplay0 uhidev1 at uhub1 port 1 configuration 1 interface 1 Apple Computer HID-proxy rev 2.00/19.65 addr 2 uhidev1: iclass 3/1 ums0 at uhidev1: 5 buttons wsmouse0 at ums0 mux 0 uhidev2 at uhub2 port 1 configuration 1 interface 0 Genius Optical Mouse rev 1.10
Re: dmesg mac mini A1347
Hi
Yes i can test it. Keep you informed about it.
Cheers,
Wesley
MOUEDINE ASSABY
On 14.03.2012 05:18, Brad Smith wrote:
Hi Wesley,
Would you be able to build a kernel with the following diff
applied
and send me the dmesg from the new kernel?
Index:
sys/dev/pci/nviic.c
===
RCS file: /home/cvs/src/sys/dev/pci/nviic.c,v
retrieving revision
1.15
diff -u -p -r1.15 nviic.c
--- sys/dev/pci/nviic.c 8 Apr 2010
00:23:53 - 1.15
+++ sys/dev/pci/nviic.c 14 Mar 2012 00:41:22
-
@@ -125,7 +125,8 @@ const struct pci_matchid nviic_ids[] = {
{
PCI_VENDOR_NVIDIA, PCI_PRODUCT_NVIDIA_MCP67_SMB },
{
PCI_VENDOR_NVIDIA, PCI_PRODUCT_NVIDIA_MCP73_SMB },
{
PCI_VENDOR_NVIDIA, PCI_PRODUCT_NVIDIA_MCP77_SMB },
- {
PCI_VENDOR_NVIDIA, PCI_PRODUCT_NVIDIA_MCP79_SMB }
+ {
PCI_VENDOR_NVIDIA, PCI_PRODUCT_NVIDIA_MCP79_SMB },
+ {
PCI_VENDOR_NVIDIA, PCI_PRODUCT_NVIDIA_MCP89_SMB }
};
int
Re: dmesg mac mini A1347
Already done. On 12.03.2012 11:24, Sebastian Benoit wrote: Wesley(open...@e-solutions.re) on 2012.03.12 09:51:59 +0400: Hi, hw.sensors.cpu0.temp0=53.00 degC Here the dmesg running OpenBSD 5.0 RELEASE: you should send this to dm...@openbsd.org, not misc ;-) http://www.openbsd.org/faq/faq4.html#SendDmesg /Benno
dmesg mac mini A1347
Hi, hw.sensors.cpu0.temp0=53.00 degC Here the dmesg running OpenBSD 5.0 RELEASE: OpenBSD 5.0 (GENERIC.MP) #59: Wed Aug 17 10:19:44 MDT 2011 dera...@i386.openbsd.org:/usr/src/sys/arch/i386/compile/GENERIC.MP RTC BIOS diagnostic error 34config_unit,memory_size,invalid_time cpu0: Intel(R) Core(TM)2 Duo CPU P8600 @ 2.40GHz (GenuineIntel 686-class) 2.39 GHz cpu0: FPU,V86,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,CFLUSH,DS,ACPI,MMX,FXSR,SSE,SSE2,SS,HTT,TM,SBF,SSE3,MWAIT,DS-CPL,VMX,SMX,EST,TM2,SSSE3,CX16,xTPR,PDCM,SSE4.1,XSAVE real mem = 2942947328 (2806MB) avail mem = 2884734976 (2751MB) mainbus0 at root bios0 at mainbus0: AT/286+ BIOS, date 07/29/05, SMBIOS rev. 2.4 @ 0xe (44 entries) bios0: vendor Apple Inc. version MM41.88Z.0042.B00.1004221740 date 04/22/10 bios0: Apple Inc. Macmini4,1 acpi0 at bios0: rev 2 acpi0: sleep states S0 S3 S4 S5 acpi0: tables DSDT FACP HPET APIC APIC ASF! SBST ECDT SSDT SSDT MCFG SSDT SSDT acpi0: wakeup devices EC__(S3) OHC1(S3) EHC1(S3) OHC2(S3) EHC2(S3) ARPT(S5) GIGE(S5) acpitimer0 at acpi0: 3579545 Hz, 24 bits acpihpet0 at acpi0: 2500 Hz acpimadt0 at acpi0 addr 0xfee0: PC-AT compat cpu0 at mainbus0: apid 0 (boot processor) cpu0: apic clock running at 265MHz cpu1 at mainbus0: apid 1 (application processor) cpu1: Intel(R) Core(TM)2 Duo CPU P8600 @ 2.40GHz (GenuineIntel 686-class) 2.39 GHz cpu1: FPU,V86,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,CFLUSH,DS,ACPI,MMX,FXSR,SSE,SSE2,SS,HTT,TM,SBF,SSE3,MWAIT,DS-CPL,VMX,SMX,EST,TM2,SSSE3,CX16,xTPR,PDCM,SSE4.1,XSAVE ioapic0 at mainbus0: apid 1 pa 0xfec0, version 11, 24 pins ioapic0: misconfigured as apic 0, remapped to apid 1 acpiec0 at acpi0 acpimcfg0 at acpi0 addr 0xf000, bus 0-5 acpiprt0 at acpi0: bus 0 (PCI0) acpiprt1 at acpi0: bus 5 (IXVE) acpicpu0 at acpi0: C3, C2, C1, PSS acpicpu1 at acpi0: C3, C2, C1, PSS acpibtn0 at acpi0: PWRB acpibtn1 at acpi0: SLPB bios0: ROM list: 0xc/0xe400! cpu0: Enhanced SpeedStep 2390 MHz: speeds: 2394, 2128, 1862, 1596 MHz memory map conflict 0xffc0/0x40 pci0 at mainbus0 bus 0: configuration mode 1 (bios) mem address conflict 0xd350/0x8 pchb0 at pci0 dev 0 function 0 NVIDIA MCP89 Host rev 0xa1 NVIDIA MCP89 Memory rev 0xa1 at pci0 dev 0 function 1 not configured vendor NVIDIA, unknown product 0x0d6d (class memory subclass RAM, rev 0xa1) at pci0 dev 1 function 0 not configured vendor NVIDIA, unknown product 0x0d6e (class memory subclass RAM, rev 0xa1) at pci0 dev 1 function 1 not configured vendor NVIDIA, unknown product 0x0d6f (class memory subclass RAM, rev 0xa1) at pci0 dev 1 function 2 not configured vendor NVIDIA, unknown product 0x0d70 (class memory subclass RAM, rev 0xa1) at pci0 dev 1 function 3 not configured vendor NVIDIA, unknown product 0x0d71 (class memory subclass RAM, rev 0xa1) at pci0 dev 2 function 0 not configured vendor NVIDIA, unknown product 0x0d72 (class memory subclass RAM, rev 0xa1) at pci0 dev 2 function 1 not configured pcib0 at pci0 dev 3 function 0 NVIDIA MCP89 LPC rev 0xa2 NVIDIA MCP89 Memory rev 0xa1 at pci0 dev 3 function 1 not configured NVIDIA MCP89 SMBus rev 0xa1 at pci0 dev 3 function 2 not configured NVIDIA MCP89 Memory rev 0xa1 at pci0 dev 3 function 3 not configured NVIDIA MCP89 Co-processor rev 0xa1 at pci0 dev 3 function 4 not configured ohci0 at pci0 dev 4 function 0 NVIDIA MCP89 USB rev 0xa1: apic 1 int 11, version 1.0, legacy support ehci0 at pci0 dev 4 function 1 NVIDIA MCP89 USB rev 0xa2: apic 1 int 10 usb0 at ehci0: USB revision 2.0 uhub0 at usb0 NVIDIA EHCI root hub rev 2.00/1.00 addr 1 ohci1 at pci0 dev 6 function 0 NVIDIA MCP89 USB rev 0xa1: apic 1 int 7, version 1.0, legacy support ehci1 at pci0 dev 6 function 1 NVIDIA MCP89 USB rev 0xa2: apic 1 int 5 usb1 at ehci1: USB revision 2.0 uhub1 at usb1 NVIDIA EHCI root hub rev 2.00/1.00 addr 1 azalia0 at pci0 dev 8 function 0 NVIDIA MCP89 HD Audio rev 0xa2: msi azalia0: codecs: Cirrus Logic/0x4206, NVIDIA/0x000c, NVIDIA/0x000c, NVIDIA/0x000c, using Cirrus Logic/0x4206 audio0 at azalia0 pciide0 at pci0 dev 10 function 0 NVIDIA MCP89 SATA rev 0xa2: DMA pciide0: using apic 1 int 11 for native-PCI interrupt wd0 at pciide0 channel 0 drive 0: TOSHIBA MK3255GSXF wd0: 16-sector PIO, LBA48, 305245MB, 625142448 sectors wd0(pciide0:0:0): using PIO mode 4, Ultra-DMA mode 5 atapiscsi0 at pciide0 channel 1 drive 0 scsibus0 at atapiscsi0: 2 targets cd0 at scsibus0 targ 0 lun 0: HL-DT-ST, DVDRW GA32N, KC08 ATAPI 5/cdrom removable cd0(pciide0:1:0): using PIO mode 4, Ultra-DMA mode 5 vendor NVIDIA, unknown product 0x0d75 (class memory subclass RAM, rev 0xa1) at pci0 dev 11 function 0 not configured ppb0 at pci0 dev 14 function 0 NVIDIA MCP89 PCIE rev 0xa1: apic 1 int 16 pci1 at ppb0 bus 1 ppb1 at pci1 dev 0 function 0 vendor TI, unknown product 0x823e rev 0x01 pci2 at ppb1 bus 2 vendor TI, unknown product 0x823f (class serial bus subclass Firewire, rev 0x01) at pci2 dev 0 function 0 not configured ppb2 at pci0 dev 21 function 0 NVIDIA MCP89 PCIE
Re: Keyboard trouble on Mac Mini G4 / macppc
On Wed, Jan 18, 2012 at 3:56 PM, Martin Pieuchot mpieuc...@nolizard.org wrote: On 18/01/12(Wed) 15:27, Christer Solskogen wrote: On Wed, Jan 18, 2012 at 3:23 PM, Steffen Daode Nurpmeso sdao...@googlemail.com wrote: Hi, Christer Solskogen wrote [2012-01-17 19:07+0100]: I just installed the latest OpenBSD snapshot on my Mac Mini G4, and I've got trouble getting the keyboard encoding to work properly. keyboard.encoding=no is set in /etc/wsconsctl.conf (and I also see keyboard.encoding - no) during startup. But the keyboard encoding is still US (or whatever is the default) any hints? Are you sure your keyboard is detected as 'keyboard' and not 'keyboard1'? What is the output of: # wsconsctl Some macppc machines have a bluetooth hid adapted detected as 'keyboard'. That did the trick! keyboard1.encoding=no Thanks! -- chs,
Re: Keyboard trouble on Mac Mini G4 / macppc
On Wed, Jan 18, 2012 at 3:23 PM, Steffen Daode Nurpmeso sdao...@googlemail.com wrote: Hi, Christer Solskogen wrote [2012-01-17 19:07+0100]: I just installed the latest OpenBSD snapshot on my Mac Mini G4, and I've got trouble getting the keyboard encoding to work properly. keyboard.encoding=no is set in /etc/wsconsctl.conf (and I also see keyboard.encoding - no) during startup. But the keyboard encoding is still US (or whatever is the default) any hints? Never tried it, but have you looked at akbd(4) already? It is not enabled in amd64/conf/GENERIC by default ... Hope that helps, I'll take a look. But usually there is a reason why it's not enabled in the first place. (and this is ppc, not sure if akbd works there) -- chs,
Re: Keyboard trouble on Mac Mini G4 / macppc
On 18/01/12(Wed) 15:27, Christer Solskogen wrote: On Wed, Jan 18, 2012 at 3:23 PM, Steffen Daode Nurpmeso sdao...@googlemail.com wrote: Hi, Christer Solskogen wrote [2012-01-17 19:07+0100]: I just installed the latest OpenBSD snapshot on my Mac Mini G4, and I've got trouble getting the keyboard encoding to work properly. keyboard.encoding=no is set in /etc/wsconsctl.conf (and I also see keyboard.encoding - no) during startup. But the keyboard encoding is still US (or whatever is the default) any hints? Are you sure your keyboard is detected as 'keyboard' and not 'keyboard1'? What is the output of: # wsconsctl Some macppc machines have a bluetooth hid adapted detected as 'keyboard'. Never tried it, but have you looked at akbd(4) already? It is not enabled in amd64/conf/GENERIC by default ... Hope that helps, I'll take a look. But usually there is a reason why it's not enabled in the first place. (and this is ppc, not sure if akbd works there) It's not related to akbd(4) because mac mini use USB keyboards. Otherwise you may have a look at kbd(8) and write 'no' to /etc/kbdtype ;) Martin
Keyboard trouble on Mac Mini G4 / macppc
Hi! I just installed the latest OpenBSD snapshot on my Mac Mini G4, and I've got trouble getting the keyboard encoding to work properly. keyboard.encoding=no is set in /etc/wsconsctl.conf (and I also see keyboard.encoding - no) during startup. But the keyboard encoding is still US (or whatever is the default) any hints? -- chs,
Re: kernel panic (mii_phy_setmedia) on mac mini A1347 (bge device unknown)
thank's, small forget ;-) I will try it . On Fri, 23 Dec 2011 11:51:33 +0100, Mike Belopuhov m...@crypt.org.ru wrote: On Fri, Dec 23, 2011 at 11:43 AM, Wesley M. open...@e-solutions.re wrote: Hi, So i installed a fresh OpenBSD 4.9 to try to patch the files : brgphy.c and miidevs I have the following error when compiling : ... D_KERNEL B -c ../../../../dev/mii/brgphy.c ../../../../dev/mii/brgphy.c:177: error: 'MII_MODEL_xxBROADCOM3_BCM57765' undeclared here (not in a function) ../../../../dev/mii/brgphy.c:178: error: 'MII_STR_xxBROADCOM3_BCM57765' undeclared here (not in a function) *** Error code 1 Stop in /usr/src/sys/arch/i386/compile/GENERIC (line 92 of /usr/share/mk/sys.mk). you have to run make in /sys/dev/mii prior to compiling.
Re: kernel panic (mii_phy_setmedia) on mac mini A1347 (bge device unknown)
Thank you very much. It works, i can now use bge0 on the mac mini. (OpenBSD 4.9) Wesley.
kernel panic (mii_phy_setmedia) on mac mini A1347
Hi, I tried to install OpenBSD 4.9 on an Apple mac mini (new generation). Model : A1347 Core i5, thunderbolt Technology, HD 500Go At installation using 4.9 RELEASE : It takes a long time to format slides. At the reboot : i have a kernel panic just after starting network So i tried to use 5.0 RELEASE. This time, it formats quickly. But it is the same way : kernel panic when it starts the network. The following message appear : Starting network panic: mii_phy_setmedia Stopped at Debugger+0x4:popl %ebp a show panic at the ddb prompt: mii_phy_setmedia I can't note trace message, i have no serial port on the mac... :( So you can see the trace message attached (picture) and the ps message attached (picture) here is the dmesg issue : boot on bsd.rd : OpenBSD 5.0 (RAMDISK_CD) #36: Wed Aug 17 10:27:31 MDT 2011 dera...@i386.openbsd.org:/usr/src/sys/arch/i386/compile/RAMDISK_CD RTC BIOS diagnostic error a9 cpu0: Intel(R) Core(TM) i5-2415M CPU @ 2.30GHz (GenuineIntel 686-class) 2.30 GHz cpu0: FPU,V86,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,CFLUSH,DS,ACPI,MMX,FXSR,SSE,SSE2,SS,HTT,TM,SBF,SSE3,PCLMUL,MWAIT,DS-CPL,VMX,EST,TM2,SSSE3,CX16,xTPR,PDCM,SSE4.1,SSE4.2,x2APIC,POPCNT,XSAVE,AVX real mem = 2047619072 (1952MB) avail mem = 2007117824 (1914MB) mainbus0 at root bios0 at mainbus0: AT/286+ BIOS, date 07/29/05, SMBIOS rev. 2.4 @ 0xe (61 entries) bios0: vendor Apple Inc. version MM51.88Z.0075.B00.1106271442 date 06/27/2011 bios0: Apple Inc. Macmini5,1 acpi0 at bios0: rev 2 acpi0: sleep states S0 S3 S4 S5 acpi0: tables DSDT FACP HPET APIC SBST ECDT SSDT SSDT SSDT SSDT SSDT SSDT SSDT SSDT SSDT MCFG SSDT SSDT SSDT acpimadt0 at acpi0 addr 0xfee0: PC-AT compat cpu0 at mainbus0: apid 0 (boot processor) cpu0: apic clock running at 99MHz cpu at mainbus0: not configured cpu at mainbus0: not configured cpu at mainbus0: not configured ioapic0 at mainbus0: apid 2 pa 0xfec0, version 20, 24 pins ioapic0: misconfigured as apic 0, remapped to apid 2 acpiprt0 at acpi0: bus 0 (PCI0) acpiprt1 at acpi0: bus 1 (P0P2) acpiprt2 at acpi0: bus 5 (PEG1) acpiprt3 at acpi0: bus 2 (RP01) acpiprt4 at acpi0: bus -1 (RP02) acpiprt5 at acpi0: bus 3 (RP03) bios0: ROM list: 0xc/0xee00 memory map conflict 0xe00f8000/0x1000 memory map conflict 0xfed1c000/0x4000 memory map conflict 0xffed/0x3 pci0 at mainbus0 bus 0: configuration mode 1 (bios) pchb0 at pci0 dev 0 function 0 Intel Core 2G Host rev 0x09 ppb0 at pci0 dev 1 function 0 Intel Core 2G PCIE rev 0x09: apic 2 int 16 pci1 at ppb0 bus 1 ppb1 at pci0 dev 1 function 1 Intel Core 2G PCIE rev 0x09: apic 2 int 16 pci2 at ppb1 bus 5 ppb2 at pci2 dev 0 function 0 vendor Intel, unknown product 0x1513 rev 0x00 pci3 at ppb2 bus 6 ppb3 at pci3 dev 0 function 0 vendor Intel, unknown product 0x1513 rev 0x00: apic 2 int 17 pci4 at ppb3 bus 7 vendor Intel, unknown product 0x1513 (class system subclass miscellaneous, rev 0x00) at pci4 dev 0 function 0 not configured ppb4 at pci3 dev 3 function 0 vendor Intel, unknown product 0x1513 rev 0x00: apic 2 int 16 pci5 at ppb4 bus 8 ppb5 at pci3 dev 4 function 0 vendor Intel, unknown product 0x1513 rev 0x00: apic 2 int 17 pci6 at ppb5 bus 9 ppb6 at pci3 dev 5 function 0 vendor Intel, unknown product 0x1513 rev 0x00: apic 2 int 18 pci7 at ppb6 bus 58 ppb7 at pci3 dev 6 function 0 vendor Intel, unknown product 0x1513 rev 0x00: apic 2 int 19 pci8 at ppb7 bus 107 vga1 at pci0 dev 2 function 0 Intel GT2+ Video rev 0x09 wsdisplay0 at vga1 mux 1: console (80x25, vt100 emulation) Intel 6 Series MEI rev 0x04 at pci0 dev 22 function 0 not configured uhci0 at pci0 dev 26 function 0 vendor Intel, unknown product 0x1c2c rev 0x05: apic 2 int 21 ehci0 at pci0 dev 26 function 7 Intel 6 Series USB rev 0x05: apic 2 int 23 usb0 at ehci0: USB revision 2.0 uhub0 at usb0 Intel EHCI root hub rev 2.00/1.00 addr 1 Intel 6 Series HD Audio rev 0x05 at pci0 dev 27 function 0 not configured ppb8 at pci0 dev 28 function 0 Intel 6 Series PCIE rev 0xb5: apic 2 int 16 pci9 at ppb8 bus 2 bge0 at pci9 dev 0 function 0 Broadcom BCM57765 rev 0x10, unknown BCM57765 (0x57785100): apic 2 int 16, address 3c:07:54:0c:6b:b7 ukphy0 at bge0 phy 1: Generic IEEE 802.3u media interface, rev. 4: OUI 0x00d897, model 0x0024 Broadcom SD Host Controller rev 0x10 at pci9 dev 0 function 1 not configured ppb9 at pci0 dev 28 function 2 Intel 6 Series PCIE rev 0xb5: apic 2 int 18 pci10 at ppb9 bus 3 ppb10 at pci10 dev 0 function 0 vendor TI, unknown product 0x823e rev 0x01 pci11 at ppb10 bus 4 vendor TI, unknown product 0x823f (class serial bus subclass Firewire, rev 0x01) at pci11 dev 0 function 0 not configured uhci1 at pci0 dev 29 function 0 vendor Intel, unknown product 0x1c27 rev 0x05: apic 2 int 19 ehci1 at pci0 dev 29 function 7 Intel 6 Series USB rev 0x05: apic 2 int 22 usb1 at ehci1: USB revision 2.0 uhub1 at usb1 Intel EHCI root hub rev 2.00/1.00 addr 1 pcib0 at pci0 dev 31 function 0 Intel HM65 LPC rev 0x05 pciide0 at pci0 dev 31 function 2 Intel 6 Series SATA rev
kernel panic (mii_phy_setmedia) on mac mini A1347 with trace and ps picture url
Hi, I tried to install OpenBSD 4.9 on an Apple mac mini (new generation). Model : A1347 ; Core i5, thunderbolt Technology, HD 500Go At installation using 4.9 RELEASE : It takes a long time to format slides. At the reboot : i have a kernel panic just after starting network So i tried to use 5.0 RELEASE. This time, it formats quickly. But it is the same way : kernel panic when it starts the network. The following message appear : Starting network panic: mii_phy_setmedia Stopped at Debugger+0x4:popl %ebp a show panic at the ddb prompt: mii_phy_setmedia I can't note trace message, i have no serial port on the mac... :( Here is the ps message : http://i43.tinypic.com/mkufyo.jpg Here is the trace message : http://i40.tinypic.com/25syfxf.jpg here is the dmesg issue : boot on bsd.rd : OpenBSD 5.0 (RAMDISK_CD) #36: Wed Aug 17 10:27:31 MDT 2011 dera...@i386.openbsd.org:/usr/src/sys/arch/i386/compile/RAMDISK_CD RTC BIOS diagnostic error a9 cpu0: Intel(R) Core(TM) i5-2415M CPU @ 2.30GHz (GenuineIntel 686-class) 2.30 GHz cpu0: FPU,V86,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,CFLUSH,DS,ACPI,MMX,FXSR,SSE,SSE2,SS,HTT,TM,SBF,SSE3,PCLMUL,MWAIT,DS-CPL,VMX,EST,TM2,SSSE3,CX16,xTPR,PDCM,SSE4.1,SSE4.2,x2APIC,POPCNT,XSAVE,AVX real mem = 2047619072 (1952MB) avail mem = 2007117824 (1914MB) mainbus0 at root bios0 at mainbus0: AT/286+ BIOS, date 07/29/05, SMBIOS rev. 2.4 @ 0xe (61 entries) bios0: vendor Apple Inc. version MM51.88Z.0075.B00.1106271442 date 06/27/2011 bios0: Apple Inc. Macmini5,1 acpi0 at bios0: rev 2 acpi0: sleep states S0 S3 S4 S5 acpi0: tables DSDT FACP HPET APIC SBST ECDT SSDT SSDT SSDT SSDT SSDT SSDT SSDT SSDT SSDT MCFG SSDT SSDT SSDT acpimadt0 at acpi0 addr 0xfee0: PC-AT compat cpu0 at mainbus0: apid 0 (boot processor) cpu0: apic clock running at 99MHz cpu at mainbus0: not configured cpu at mainbus0: not configured cpu at mainbus0: not configured ioapic0 at mainbus0: apid 2 pa 0xfec0, version 20, 24 pins ioapic0: misconfigured as apic 0, remapped to apid 2 acpiprt0 at acpi0: bus 0 (PCI0) acpiprt1 at acpi0: bus 1 (P0P2) acpiprt2 at acpi0: bus 5 (PEG1) acpiprt3 at acpi0: bus 2 (RP01) acpiprt4 at acpi0: bus -1 (RP02) acpiprt5 at acpi0: bus 3 (RP03) bios0: ROM list: 0xc/0xee00 memory map conflict 0xe00f8000/0x1000 memory map conflict 0xfed1c000/0x4000 memory map conflict 0xffed/0x3 pci0 at mainbus0 bus 0: configuration mode 1 (bios) pchb0 at pci0 dev 0 function 0 Intel Core 2G Host rev 0x09 ppb0 at pci0 dev 1 function 0 Intel Core 2G PCIE rev 0x09: apic 2 int 16 pci1 at ppb0 bus 1 ppb1 at pci0 dev 1 function 1 Intel Core 2G PCIE rev 0x09: apic 2 int 16 pci2 at ppb1 bus 5 ppb2 at pci2 dev 0 function 0 vendor Intel, unknown product 0x1513 rev 0x00 pci3 at ppb2 bus 6 ppb3 at pci3 dev 0 function 0 vendor Intel, unknown product 0x1513 rev 0x00: apic 2 int 17 pci4 at ppb3 bus 7 vendor Intel, unknown product 0x1513 (class system subclass miscellaneous, rev 0x00) at pci4 dev 0 function 0 not configured ppb4 at pci3 dev 3 function 0 vendor Intel, unknown product 0x1513 rev 0x00: apic 2 int 16 pci5 at ppb4 bus 8 ppb5 at pci3 dev 4 function 0 vendor Intel, unknown product 0x1513 rev 0x00: apic 2 int 17 pci6 at ppb5 bus 9 ppb6 at pci3 dev 5 function 0 vendor Intel, unknown product 0x1513 rev 0x00: apic 2 int 18 pci7 at ppb6 bus 58 ppb7 at pci3 dev 6 function 0 vendor Intel, unknown product 0x1513 rev 0x00: apic 2 int 19 pci8 at ppb7 bus 107 vga1 at pci0 dev 2 function 0 Intel GT2+ Video rev 0x09 wsdisplay0 at vga1 mux 1: console (80x25, vt100 emulation) Intel 6 Series MEI rev 0x04 at pci0 dev 22 function 0 not configured uhci0 at pci0 dev 26 function 0 vendor Intel, unknown product 0x1c2c rev 0x05: apic 2 int 21 ehci0 at pci0 dev 26 function 7 Intel 6 Series USB rev 0x05: apic 2 int 23 usb0 at ehci0: USB revision 2.0 uhub0 at usb0 Intel EHCI root hub rev 2.00/1.00 addr 1 Intel 6 Series HD Audio rev 0x05 at pci0 dev 27 function 0 not configured ppb8 at pci0 dev 28 function 0 Intel 6 Series PCIE rev 0xb5: apic 2 int 16 pci9 at ppb8 bus 2 bge0 at pci9 dev 0 function 0 Broadcom BCM57765 rev 0x10, unknown BCM57765 (0x57785100): apic 2 int 16, address 3c:07:54:0c:6b:b7 ukphy0 at bge0 phy 1: Generic IEEE 802.3u media interface, rev. 4: OUI 0x00d897, model 0x0024 Broadcom SD Host Controller rev 0x10 at pci9 dev 0 function 1 not configured ppb9 at pci0 dev 28 function 2 Intel 6 Series PCIE rev 0xb5: apic 2 int 18 pci10 at ppb9 bus 3 ppb10 at pci10 dev 0 function 0 vendor TI, unknown product 0x823e rev 0x01 pci11 at ppb10 bus 4 vendor TI, unknown product 0x823f (class serial bus subclass Firewire, rev 0x01) at pci11 dev 0 function 0 not configured uhci1 at pci0 dev 29 function 0 vendor Intel, unknown product 0x1c27 rev 0x05: apic 2 int 19 ehci1 at pci0 dev 29 function 7 Intel 6 Series USB rev 0x05: apic 2 int 22 usb1 at ehci1: USB revision 2.0 uhub1 at usb1 Intel EHCI root hub rev 2.00/1.00 addr 1 pcib0 at pci0 dev 31 function 0 Intel HM65 LPC rev 0x05 pciide0 at pci0 dev
Re: kernel panic (mii_phy_setmedia) on mac mini A1347 with trace and ps picture url
On Mon, Dec 19, 2011 at 04:10:16PM +0400, Wesley M. wrote: Here is the ps message : http://i43.tinypic.com/mkufyo.jpg Here is the trace message : http://i40.tinypic.com/25syfxf.jpg Have you tried to disable whatever it is on boot? -- This message has been scanned for viruses and dangerous content by MailScanner, and is believed to be clean.
Re: kernel panic (mii_phy_setmedia) on mac mini A1347 with trace and ps picture url
On Mon, 19 Dec 2011 10:33:56 -0200, Daniel Bolgheroni dan...@cria.org.br wrote: On Mon, Dec 19, 2011 at 04:10:16PM +0400, Wesley M. wrote: Here is the ps message : http://i43.tinypic.com/mkufyo.jpg Here is the trace message : http://i40.tinypic.com/25syfxf.jpg Have you tried to disable whatever it is on boot? i tried disable bge0, boot, i still have a kernel panic just after Starting Network
Re: kernel panic (mii_phy_setmedia) on mac mini A1347 with trace and ps picture url
On 2011/12/19 16:10, Wesley M. wrote:
So i
tried to use 5.0 RELEASE.
This time, it formats quickly. But it is the same
way : kernel panic when it starts the network.
The following message
appear :
Starting network
panic: mii_phy_setmedia
Stopped at
Debugger+0x4:popl %ebp
a show panic at the ddb prompt:
mii_phy_setmedia
You can try this patch. Apply, run 'cd /sys/dev/mii make', then build
a new kernel. Obviously you will need to get the new kernel on to the
machine somehow; you can probably get it to boot with boot -c,
disable bge, quit - then you will need to either use a USB ethernet
device to get the source tree onto the machine, or copy a kernel built
on another machine via USB storage.
Index: brgphy.c
===
RCS file: /cvs/src/sys/dev/mii/brgphy.c,v
retrieving revision 1.93
diff -u -p -r1.93 brgphy.c
--- brgphy.c24 May 2010 21:23:23 - 1.93
+++ brgphy.c19 Dec 2011 12:43:02 -
@@ -174,6 +174,8 @@ static const struct mii_phydesc brgphys[
MII_STR_xxBROADCOM2_BCM5709S },
{ MII_OUI_xxBROADCOM2, MII_MODEL_xxBROADCOM2_BCM5709CAX,
MII_STR_xxBROADCOM2_BCM5709CAX },
+ { MII_OUI_xxBROADCOM3, MII_MODEL_xxBROADCOM3_BCM57765,
+ MII_STR_xxBROADCOM3_BCM57765 },
{ MII_OUI_xxBROADCOM3, MII_MODEL_xxBROADCOM3_BCM57780,
MII_STR_xxBROADCOM3_BCM57780 },
{ MII_OUI_BROADCOM2,MII_MODEL_BROADCOM2_BCM5906,
Index: miidevs
===
RCS file: /cvs/src/sys/dev/mii/miidevs,v
retrieving revision 1.116
diff -u -p -r1.116 miidevs
--- miidevs 21 Jan 2011 09:46:13 - 1.116
+++ miidevs 19 Dec 2011 12:43:02 -
@@ -159,6 +159,7 @@ model xxBROADCOM2 BCM5709C 0x003c BCM570
model xxBROADCOM2 BCM5761 0x003d BCM5761 10/100/1000baseT PHY
model xxBROADCOM2 BCM5709S 0x003f BCM5709S 1000/2500baseSX PHY
model xxBROADCOM3 BCM57780 0x0019 BCM57780 10/100/1000baseT PHY
+model xxBROADCOM3 BCM57765 0x0024 BCM57765 10/100/1000baseT PHY
model BROADCOM BCM5400 0x0004 BCM5400 1000baseT PHY
model BROADCOM BCM5401 0x0005 BCM5401 1000baseT PHY
model BROADCOM BCM5411 0x0007 BCM5411 1000baseT PHY
Actually I don't see any reason why not to commit this as-is.
It may not work but it's certainly not going to make things worse.
Any OKs for this?
I can't note trace message, i have no serial port on the mac... :(
Yes you can, just re-type it from the text on-screen. But in this case
the ramdisk dmesg you included is enough.
Re: kernel panic (mii_phy_setmedia) on mac mini A1347 with trace and ps picture url
Try this diff against -current. You'll have to apply
the patch from sys/dev/mii and run 'make' afterwards
to regenerate the headers.
Index: miidevs
===
RCS file: /cvs/src/sys/dev/mii/miidevs,v
retrieving revision 1.116
diff -u -p -r1.116 miidevs
--- miidevs 21 Jan 2011 09:46:13 - 1.116
+++ miidevs 19 Dec 2011 12:52:37 -
@@ -159,6 +159,7 @@ model xxBROADCOM2 BCM5709C 0x003c BCM570
model xxBROADCOM2 BCM5761 0x003d BCM5761 10/100/1000baseT PHY
model xxBROADCOM2 BCM5709S 0x003f BCM5709S 1000/2500baseSX PHY
model xxBROADCOM3 BCM57780 0x0019 BCM57780 10/100/1000baseT PHY
+model xxBROADCOM3 BCM57785 0x0024 BCM57785 10/100/1000baseT PHY
model BROADCOM BCM5400 0x0004 BCM5400 1000baseT PHY
model BROADCOM BCM5401 0x0005 BCM5401 1000baseT PHY
model BROADCOM BCM5411 0x0007 BCM5411 1000baseT PHY
Index: brgphy.c
===
RCS file: /cvs/src/sys/dev/mii/brgphy.c,v
retrieving revision 1.93
diff -u -p -r1.93 brgphy.c
--- brgphy.c24 May 2010 21:23:23 - 1.93
+++ brgphy.c19 Dec 2011 12:52:37 -
@@ -176,6 +176,8 @@ static const struct mii_phydesc brgphys[
MII_STR_xxBROADCOM2_BCM5709CAX },
{ MII_OUI_xxBROADCOM3, MII_MODEL_xxBROADCOM3_BCM57780,
MII_STR_xxBROADCOM3_BCM57780 },
+ { MII_OUI_xxBROADCOM3, MII_MODEL_xxBROADCOM3_BCM57785,
+ MII_STR_xxBROADCOM3_BCM57785 },
{ MII_OUI_BROADCOM2,MII_MODEL_BROADCOM2_BCM5906,
MII_STR_BROADCOM2_BCM5906 },
Re: kernel panic (mii_phy_setmedia) on mac mini A1347 with trace and ps picture url
It's committed so wait for new snaps and you can avoid this step.
On 2011/12/19 17:10, Wesley M. wrote:
Hi Stuart,
I tried this : boot -c at boot prompt (startup)
I have this message : kbc cmd word write error just after.
And i can't use keyboard at UKC Prompt :(
Wesley.
On Mon, 19 Dec 2011 12:51:58 +, Stuart Henderson s...@spacehopper.org
wrote:
On 2011/12/19 16:10, Wesley M. wrote:
So i
tried to use 5.0 RELEASE.
This time, it formats quickly. But it is the same
way : kernel panic when it starts the network.
The following message
appear :
Starting network
panic: mii_phy_setmedia
Stopped at
Debugger+0x4:popl %ebp
a show panic at the ddb prompt:
mii_phy_setmedia
You can try this patch. Apply, run 'cd /sys/dev/mii make', then build
a new kernel. Obviously you will need to get the new kernel on to the
machine somehow; you can probably get it to boot with boot -c,
disable bge, quit - then you will need to either use a USB ethernet
device to get the source tree onto the machine, or copy a kernel built
on another machine via USB storage.
Index: brgphy.c
===
RCS file: /cvs/src/sys/dev/mii/brgphy.c,v
retrieving revision 1.93
diff -u -p -r1.93 brgphy.c
--- brgphy.c24 May 2010 21:23:23 - 1.93
+++ brgphy.c19 Dec 2011 12:43:02 -
@@ -174,6 +174,8 @@ static const struct mii_phydesc brgphys[
MII_STR_xxBROADCOM2_BCM5709S },
{ MII_OUI_xxBROADCOM2, MII_MODEL_xxBROADCOM2_BCM5709CAX,
MII_STR_xxBROADCOM2_BCM5709CAX },
+ { MII_OUI_xxBROADCOM3, MII_MODEL_xxBROADCOM3_BCM57765,
+ MII_STR_xxBROADCOM3_BCM57765 },
{ MII_OUI_xxBROADCOM3, MII_MODEL_xxBROADCOM3_BCM57780,
MII_STR_xxBROADCOM3_BCM57780 },
{ MII_OUI_BROADCOM2,MII_MODEL_BROADCOM2_BCM5906,
Index: miidevs
===
RCS file: /cvs/src/sys/dev/mii/miidevs,v
retrieving revision 1.116
diff -u -p -r1.116 miidevs
--- miidevs 21 Jan 2011 09:46:13 - 1.116
+++ miidevs 19 Dec 2011 12:43:02 -
@@ -159,6 +159,7 @@ model xxBROADCOM2 BCM5709C 0x003c BCM570
model xxBROADCOM2 BCM5761 0x003d BCM5761 10/100/1000baseT PHY
model xxBROADCOM2 BCM5709S 0x003f BCM5709S 1000/2500baseSX PHY
model xxBROADCOM3 BCM57780 0x0019 BCM57780 10/100/1000baseT PHY
+model xxBROADCOM3 BCM57765 0x0024 BCM57765 10/100/1000baseT PHY
model BROADCOM BCM5400 0x0004 BCM5400 1000baseT PHY
model BROADCOM BCM5401 0x0005 BCM5401 1000baseT PHY
model BROADCOM BCM5411 0x0007 BCM5411 1000baseT PHY
Actually I don't see any reason why not to commit this as-is.
It may not work but it's certainly not going to make things worse.
Any OKs for this?
I can't note trace message, i have no serial port on the mac... :(
Yes you can, just re-type it from the text on-screen. But in this case
the ramdisk dmesg you included is enough.
Re: kernel panic (mii_phy_setmedia) on mac mini A1347 with trace and ps picture url
Ok, thank's.
Therefore, i have a problem. I use mailserv project, and it works only on
4.8; 4.9 RELEASE. Not on 5.0
Is there a way for me to have a 4.9 with patches ?
In short, is it possible to have a patch to use with 4.9-stable ?
Thank you very much.
Wesley.
On Mon, 19 Dec 2011 13:21:20 +, Stuart Henderson s...@spacehopper.org
wrote:
It's committed so wait for new snaps and you can avoid this step.
On 2011/12/19 17:10, Wesley M. wrote:
Hi Stuart,
I tried this : boot -c at boot prompt (startup)
I have this message : kbc cmd word write error just after.
And i can't use keyboard at UKC Prompt :(
Wesley.
On Mon, 19 Dec 2011 12:51:58 +, Stuart Henderson
s...@spacehopper.org
wrote:
On 2011/12/19 16:10, Wesley M. wrote:
So i
tried to use 5.0 RELEASE.
This time, it formats quickly. But it is the same
way : kernel panic when it starts the network.
The following message
appear :
Starting network
panic: mii_phy_setmedia
Stopped at
Debugger+0x4:popl %ebp
a show panic at the ddb prompt:
mii_phy_setmedia
You can try this patch. Apply, run 'cd /sys/dev/mii make', then
build
a new kernel. Obviously you will need to get the new kernel on to the
machine somehow; you can probably get it to boot with boot -c,
disable bge, quit - then you will need to either use a USB
ethernet
device to get the source tree onto the machine, or copy a kernel
built
on another machine via USB storage.
Index: brgphy.c
===
RCS file: /cvs/src/sys/dev/mii/brgphy.c,v
retrieving revision 1.93
diff -u -p -r1.93 brgphy.c
--- brgphy.c 24 May 2010 21:23:23 - 1.93
+++ brgphy.c 19 Dec 2011 12:43:02 -
@@ -174,6 +174,8 @@ static const struct mii_phydesc brgphys[
MII_STR_xxBROADCOM2_BCM5709S },
{ MII_OUI_xxBROADCOM2, MII_MODEL_xxBROADCOM2_BCM5709CAX,
MII_STR_xxBROADCOM2_BCM5709CAX },
+ { MII_OUI_xxBROADCOM3, MII_MODEL_xxBROADCOM3_BCM57765,
+MII_STR_xxBROADCOM3_BCM57765 },
{ MII_OUI_xxBROADCOM3, MII_MODEL_xxBROADCOM3_BCM57780,
MII_STR_xxBROADCOM3_BCM57780 },
{ MII_OUI_BROADCOM2,MII_MODEL_BROADCOM2_BCM5906,
Index: miidevs
===
RCS file: /cvs/src/sys/dev/mii/miidevs,v
retrieving revision 1.116
diff -u -p -r1.116 miidevs
--- miidevs21 Jan 2011 09:46:13 - 1.116
+++ miidevs19 Dec 2011 12:43:02 -
@@ -159,6 +159,7 @@ model xxBROADCOM2 BCM5709C 0x003c BCM570
model xxBROADCOM2 BCM5761 0x003d BCM5761 10/100/1000baseT PHY
model xxBROADCOM2 BCM5709S0x003f BCM5709S 1000/2500baseSX PHY
model xxBROADCOM3 BCM577800x0019 BCM57780 10/100/1000baseT PHY
+model xxBROADCOM3 BCM577650x0024 BCM57765 10/100/1000baseT PHY
model BROADCOM BCM54000x0004 BCM5400 1000baseT PHY
model BROADCOM BCM54010x0005 BCM5401 1000baseT PHY
model BROADCOM BCM54110x0007 BCM5411 1000baseT PHY
Actually I don't see any reason why not to commit this as-is.
It may not work but it's certainly not going to make things worse.
Any OKs for this?
I can't note trace message, i have no serial port on the mac... :(
Yes you can, just re-type it from the text on-screen. But in this
case
the ramdisk dmesg you included is enough.
Re: kernel panic (mii_phy_setmedia) on mac mini A1347 with trace and ps picture url
On 2011/12/19 17:43, Wesley M. wrote: Ok, thank's. Therefore, i have a problem. I use mailserv project, and it works only on 4.8; 4.9 RELEASE. Not on 5.0 Is there a way for me to have a 4.9 with patches ? In short, is it possible to have a patch to use with 4.9-stable ? Thank you very much. The maximum extent I will use -stable is occasionally to backport important bug fixes from -current to -stable from the last release. (And I don't have enough space for VMs to do this at the moment either). A diff adding this to 4.9 is certainly possible but I won't be providing it..
Audacity/Sound recording on a Mac Mini
I have a G4 Mac Mini (PowerMac 10,1) and have successfully installed OpenBSD 5.0 on it. I have also successfully built audacity from the ports tree. My thought was to create a small footprint audio recording system for a small charitable organization using OpenBSD. I've had two small problems: A. When sound is played e.g. When KDE starts up, there is a loud hissing sound which comes from the internal speaker(s). B. I am not really able to see any sound input coming from either the native MacMini audio input/output jack (aoa) nor from a USB (iMic) microphone (uaudio). Audacity seems to only show one source of audio input: sndio. Any help with be greatly appreciated. I do not want to have to go back to an unsupported version of Mac OS X, nor a Linux/Debian option. Has anyone used OpenBSD to do sound recording on a MacMini or other Apple PowerPC devices? Russell -- Russell Sutherand I+TS e: russell.sutherl...@utoronto.ca t: +1.416.978.0470 f: +1.416.978.6620 m: +1.416.803.0080
Re: Audacity/Sound recording on a Mac Mini
On Nov 22 09:33:06, Russell Sutherland wrote: I have a G4 Mac Mini (PowerMac 10,1) and have successfully installed OpenBSD 5.0 on it. I have also successfully built audacity from the ports tree. My thought was to create a small footprint audio recording system for a small charitable organization using OpenBSD. I've had two small problems: A. When sound is played e.g. When KDE starts up, there is a loud hissing sound which comes from the internal speaker(s). B. I am not really able to see any sound input coming from either the native MacMini audio input/output jack (aoa) nor from a USB (iMic) microphone (uaudio). Audacity seems to only show one source of audio input: sndio. Any help with be greatly appreciated. I do not want to have to go back to an unsupported version of Mac OS X, nor a Linux/Debian option. Has anyone used OpenBSD to do sound recording on a MacMini or other Apple PowerPC devices? I use aucat(1) and sox(1) on top of sndio without any problems on a MacBook3,1 (which is amd64 though).
Mac Mini Server
Has anyone used OpenBSD on the new mac mini servers which don't have an integrated optical drive? Is it possible to use apple's mac mini external dvd/cd drive once OpenBSD has been installed (for instance, to do a cd boot for a clean upgrade)? -- Devin M. Ceartas, owner NacreData L.L.C. nacred...@gmail.com
Re: Mac Mini Server
What is the sense to buy Mac and install openbsd on it? You pay for Mac OS when you buy a Mac. So what is the sense to install another OS on it? On 12:05 Wed 13 Jul , Devin Ceartas wrote: Has anyone used OpenBSD on the new mac mini servers which don't have an integrated optical drive? Is it possible to use apple's mac mini external dvd/cd drive once OpenBSD has been installed (for instance, to do a cd boot for a clean upgrade)? -- Devin M. Ceartas, owner NacreData L.L.C. nacred...@gmail.com -- sergeyb@ [demime 1.01d removed an attachment of type application/pgp-signature]
Re: Mac Mini Server
On Wed, Jul 13, 2011 at 9:55 AM, Sergey Bronnikov este...@gmail.com wrote: What is the sense to buy Mac and install openbsd on it? You pay for Mac OS when you buy a Mac. So what is the sense to install another OS on it? He wants to? Is another reason necessary? -B
Re: Mac Mini Server
Its his money and his machine. His choice. On Wed, Jul 13, 2011 at 11:55 AM, Sergey Bronnikov este...@gmail.com wrote: What is the sense to buy Mac and install openbsd on it? You pay for Mac OS when you buy a Mac. So what is the sense to install another OS on it? On 12:05 Wed 13 Jul , Devin Ceartas wrote: Has anyone used OpenBSD on the new mac mini servers which don't have an integrated optical drive? Is it possible to use apple's mac mini external dvd/cd drive once OpenBSD has been installed (for instance, to do a cd boot for a clean upgrade)? -- Devin M. Ceartas, owner NacreData L.L.C. nacred...@gmail.com -- sergeyb@ [demime 1.01d removed an attachment of type application/pgp-signature]
Re: Mac Mini Server
hi, of course it makes sense, it is done to make you talk about it, so that works. I think it should work, if apple let USB PC-CDROM work properly From: Sergey Bronnikov este...@gmail.com Sent: Wed Jul 13 18:55:21 CEST 2011 To: Devin Ceartas nacred...@gmail.com Subject: Re: Mac Mini Server What is the sense to buy Mac and install openbsd on it? You pay for Mac OS when you buy a Mac. So what is the sense to install another OS on it? On 12:05 Wed 13 Jul , Devin Ceartas wrote: Has anyone used OpenBSD on the new mac mini servers which don't have an integrated optical drive? Is it possible to use apple's mac mini external dvd/cd drive once OpenBSD has been installed (for instance, to do a cd boot for a clean upgrade)? -- Devin M. Ceartas, owner NacreData L.L.C. nacred...@gmail.com -- sergeyb@ [demime 1.01d removed an attachment of type application/pgp-signature] Cordialement Francois Pussault 3701 - 8 rue Marcel Pagnol 31100 ToulouseB FranceB +33 6 17 230 820 B +33 5 34 365 269 fpussa...@contactoffice.fr
Re: Mac Mini Server
On 7/13/11 11:15 AM, Francois Pussault wrote: hi, of course it makes sense, it is done to make you talk about it, so that works. Try loading an OpenBSD VM on the machine first to see if there are any surprises. Mehma
