Bug#782058: Pegasos II: installer boots up to 'returning from prom_init'
-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 On 12/09/2015 03:39 AM, Milan Kupcevic wrote: > The module in question gets loaded and is used in D-I only. Pay > attention to the case you are pointing at: the graphics does not > work on boot/reboot into an installed system. At this point this > module plays no role because it is blacklisted in the main system. > This user is having some other issues unrelated to this module. Did you actually check that it is blacklisted after installation? radeon KMS worked fine on every PPC Mac hardware that I tested. However, I always ran into exactly this issue when radeonfb was loaded, even when it was unloaded later. Apparently, radeonfb sets the GPU in a state from which the radeon KMS module cannot recover it. My Mac Mini G4 is currently packed up because I am moving soon. But I will re-test this at some point because I am pretty sure this is again radeonfb messing with the GPU as the symptoms are the same. Adrian - -- .''`. John Paul Adrian Glaubitz : :' : Debian Developer - glaub...@debian.org `. `' Freie Universitaet Berlin - glaub...@physik.fu-berlin.de `-GPG: 62FF 8A75 84E0 2956 9546 0006 7426 3B37 F5B5 F913 -BEGIN PGP SIGNATURE- Version: GnuPG v2 iQIcBAEBCAAGBQJWZ/h2AAoJEHQmOzf1tfkTG5QP/3fIYZCRl+V3MbpWoXjivBU/ Njgwtsjh67Z/vouM9eT50U2Jc3Db/6a8rtWb3cwuYfES+36fxxK3HiExr5/aRwzo 19gBbkCweYGDErZLoc0OnY7UZT1Fk0FcNfU4FdC4edMtrb63dYsQAhxFbI8NVfba tJTH1pJi5MqLx03rzcPKl97/4OKFTP4b1+54nojZaXYnQG7pmFsK1Amx4nM4xqAJ 5uxbJ/q/ViEGqgLE8xso9471mKyTYm3+FI8kcxq83XNEqf9WDilRBcQgPvIkwfvW lB5ALaKpd3fjb2yOM2557W857hMuzD7+i0jW23P5ieKcb0hxc3HVOJKLCTNDrYDR inknkx/ZoOGhzHQC1sr4e8AHsT6Tp1dQLK0fyuGKasa2FKHeqN4eueYZImO2QFpG Ir/xoYYVXZPWyAS0xGH3sddn9WsP7tvOphChgPyi5VBMoaaJqq2CBupdUTLarc9/ cZeU4jPYZo7seRtCKcdTPibm0V+keInzUC5PNoVb2lDD20kWSlDpaeCHcVp+yp8s Y1ZwFUtaPYjGljz6ei23+0v+VIei2fhGyzpLkQ8xJjQt2/XsGaWT0eD9CAsNPocC C/nWxruTt8+RUg9Wg/fO9K8X1cNCh/HfU9wNtMid74ski9prxZNG+xxFgOOfzxo1 2UEz9Xkajsesb8+nZTaA =21XG -END PGP SIGNATURE-
Bug#782058: Pegasos II: installer boots up to 'returning from prom_init'
On 12/08/2015 06:30 PM, John Paul Adrian Glaubitz wrote: > On Fri, Apr 10, 2015 at 05:39:50PM -0400, Milan Kupcevic wrote: > > The module landed in sid D-I. It gets loaded automatically as it is not >> blacklisted in D-I. I've been able to boot and run the installer on an >> XServe G4 DP, a G4 Mac Mini, and a Pegasos II. All three machines have >> radeon cards. > > This reddit user got different results which rather support my stance: > >> https://www.reddit.com/r/debian/3vyn0p/ > Hi John, The module in question gets loaded and is used in D-I only. Pay attention to the case you are pointing at: the graphics does not work on boot/reboot into an installed system. At this point this module plays no role because it is blacklisted in the main system. This user is having some other issues unrelated to this module. M signature.asc Description: OpenPGP digital signature
Bug#782058: Pegasos II: installer boots up to 'returning from prom_init'
On Fri, Apr 10, 2015 at 05:39:50PM -0400, Milan Kupcevic wrote: > The module landed in sid D-I. It gets loaded automatically as it is not > blacklisted in D-I. I've been able to boot and run the installer on an > XServe G4 DP, a G4 Mac Mini, and a Pegasos II. All three machines have > radeon cards. This reddit user got different results which rather support my stance: > https://www.reddit.com/r/debian/3vyn0p/ Frankly, I think it's more important to have a working graphics driver on ubiqutous Apple PowerPC hardware than on these extremely obscure Pegasos-II boards which have very negligible user base given the fact that those were rather expensive due to their low production numbers. So my opinion remains unchanged: Drop radeonfb by any means as it's obsolete and breaks the way more ubiqutous radeon KMS driver. Cheers, Adrian -- .''`. John Paul Adrian Glaubitz : :' : Debian Developer - glaub...@debian.org `. `' Freie Universitaet Berlin - glaub...@physik.fu-berlin.de `-GPG: 62FF 8A75 84E0 2956 9546 0006 7426 3B37 F5B5 F913
Bug#782058: Pegasos II: installer boots up to 'returning from prom_init'
On 04/10/2015 06:05 PM, Ben Hutchings wrote: > On Fri, 2015-04-10 at 17:39 -0400, Milan Kupcevic wrote: >> On 04/09/2015 08:21 AM, Ben Hutchings wrote: >> [...] >> >>> >>> It isn't reverted. All I've done is to add radeonfb.ko to the drivers >>> that are included *in the installer*. >>> >>> Neither radeon.ko nor xserver-xorg-video-radeon are included in the >>> installer, so how could they possibly be used? If you though those >>> should be used in the installer, you should have told people that >>> earlier. >>> >>> As it is, I think that the installer should be able to work using >>> radeonfb.ko and xserver-xorg-video-fbdev, though I'm not sure whether >>> radeonfb.ko will be loaded automatically. >>> >>> Ben. >>> >> >> The module landed in sid D-I. It gets loaded automatically as it is not >> blacklisted in D-I. I've been able to boot and run the installer on an >> XServe G4 DP, a G4 Mac Mini, and a Pegasos II. All three machines have >> radeon cards. > > Using the graphical or text-based installer? > > Ben. > Using text-based installer. I do not remember when I last time saw graphical installer on PowerPC platform. As far as I know there is no graphical installer on this platform for very long time. It seems no one is even trying to make it work. Milan signature.asc Description: OpenPGP digital signature
Bug#782058: Pegasos II: installer boots up to 'returning from prom_init'
On Fri, 2015-04-10 at 17:39 -0400, Milan Kupcevic wrote: > On 04/09/2015 08:21 AM, Ben Hutchings wrote: > [...] > > > > > It isn't reverted. All I've done is to add radeonfb.ko to the drivers > > that are included *in the installer*. > > > > Neither radeon.ko nor xserver-xorg-video-radeon are included in the > > installer, so how could they possibly be used? If you though those > > should be used in the installer, you should have told people that > > earlier. > > > > As it is, I think that the installer should be able to work using > > radeonfb.ko and xserver-xorg-video-fbdev, though I'm not sure whether > > radeonfb.ko will be loaded automatically. > > > > Ben. > > > > The module landed in sid D-I. It gets loaded automatically as it is not > blacklisted in D-I. I've been able to boot and run the installer on an > XServe G4 DP, a G4 Mac Mini, and a Pegasos II. All three machines have > radeon cards. Using the graphical or text-based installer? Ben. -- Ben Hutchings Everything should be made as simple as possible, but not simpler. - Albert Einstein signature.asc Description: This is a digitally signed message part
Bug#782058: Pegasos II: installer boots up to 'returning from prom_init'
On 04/09/2015 08:21 AM, Ben Hutchings wrote: [...] > > It isn't reverted. All I've done is to add radeonfb.ko to the drivers > that are included *in the installer*. > > Neither radeon.ko nor xserver-xorg-video-radeon are included in the > installer, so how could they possibly be used? If you though those > should be used in the installer, you should have told people that > earlier. > > As it is, I think that the installer should be able to work using > radeonfb.ko and xserver-xorg-video-fbdev, though I'm not sure whether > radeonfb.ko will be loaded automatically. > > Ben. > The module landed in sid D-I. It gets loaded automatically as it is not blacklisted in D-I. I've been able to boot and run the installer on an XServe G4 DP, a G4 Mac Mini, and a Pegasos II. All three machines have radeon cards. Milan signature.asc Description: OpenPGP digital signature
Bug#782058: Pegasos II: installer boots up to 'returning from prom_init'
On 04/09/2015 02:21 PM, Ben Hutchings wrote: > It isn't reverted. All I've done is to add radeonfb.ko to the > drivers that are included *in the installer*. Yes, I understand that. I still disagree with the change. > Neither radeon.ko nor xserver-xorg-video-radeon are included in > the installer, so how could they possibly be used? If you though > those should be used in the installer, you should have told people > that earlier. I didn't know they weren't included. I assumed that the graphics driver modules are important enough to be present in the installer image. > As it is, I think that the installer should be able to work using > radeonfb.ko and xserver-xorg-video-fbdev, though I'm not sure > whether radeonfb.ko will be loaded automatically. As I have said before [1], radeonfb and xserver-xorg-video-fbdev aren't really working, the graphics are broken. Here's how it looks on a Powerbook G4 (with the same result on a Mac Mini G4) with radeonfb enabled: > http://i.imgur.com/Miw5CR1.jpg http://i.imgur.com/AfpNdx3.jpg > http://i.imgur.com/QBUPwRA.jpg On 04/09/2015 02:24 PM, Milan Kupcevic wrote: > How is that X display in debian installer on PowerPC platform > working for you? I never said it is. I said your suggested fix was wrong. > Your understanding of the consequences of your changes is trully > stellar. So you basically disagree about the graphical installer being broken on all PowerPC machines with Radeon graphics is not an important issue? OK. > Well, I've asked, no one complained until you showed up. The > resulting discussion spreads very interesting scent. I complained because I care about the end product. > Are you sure you want to know about every non-x86 issue I face on > daily basis? If it involves making such important changes to the kernel configuration, then yes. I am a porter for the m68k and sh4 architectures in Debian and also have large numbers of different hardware platforms available to test Debian on, ranging from a 22-year-old Amiga with 68030/50 MHz to an SGI UV-1000 supercomputer, so I can cover lots of use cases and I do lots of testing. On 04/09/2015 08:11 PM, Milan Kupcevic wrote: > Sorry, my reaction to personal attacks was too harsh. Will stick > to technical issues and ignore any personal slurs from now on. That wasn't a personal attack. I was criticizing you for requesting such a change without apparently reading the bug report where I elaborated why I said we should no longer use radeonfb. I have repeated several times that this driver produces broken graphics and I am starting to feel like an idiot having to repeat this over and over again. Cheers, Adrian > [1] https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=748398#106 -- .''`. John Paul Adrian Glaubitz : :' : Debian Developer - glaub...@debian.org `. `' Freie Universitaet Berlin - glaub...@physik.fu-berlin.de `-GPG: 62FF 8A75 84E0 2956 9546 0006 7426 3B37 F5B5 F913 -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#782058: Pegasos II: installer boots up to 'returning from prom_init'
On 04/09/2015 12:29 PM, Ben Hutchings wrote: > > Let's try to keep this civil, please. > > Ben. > Sorry, my reaction to personal attacks was too harsh. Will stick to technical issues and ignore any personal slurs from now on. Milan signature.asc Description: OpenPGP digital signature
Bug#782058: Pegasos II: installer boots up to 'returning from prom_init'
On Thu, 2015-04-09 at 08:24 -0400, Milan Kupcevic wrote: [...] > Your understanding of the consequences of your changes is trully stellar. [...] > Well, I've asked, no one complained until you showed up. The resulting > discussion spreads very interesting scent. [...] Let's try to keep this civil, please. Ben. -- Ben Hutchings I'm always amazed by the number of people who take up solipsism because they heard someone else explain it. - E*Borg on alt.fan.pratchett signature.asc Description: This is a digitally signed message part
Bug#782058: Pegasos II: installer boots up to 'returning from prom_init'
On 04/09/2015 04:08 AM, John Paul Adrian Glaubitz wrote: > On 04/09/2015 12:38 AM, Milan Kupcevic wrote: >>> Well, yes. As you could see from the bug report you linked above, >>> compiling radeonfb into the kernel broke X on basically all >>> Radeon cards. >>> > >> It seems that radeonfb was compiled into the kernel since the dawn >> of time. > > On the powerpc Debian kernel, yes, on the other architectures, no. > radeonfb has been deprecated long time ago and should no longer be > used. > > The only reason it was compiled into the powerpc kernel without anyone > complaining is the fact that the xf86-video-ati (= Radeon X.Org) driver > in Wheezy was still old enough [1] to support userland mode-setting > which was dropped upstream in version 7.0.0 almost three years ago [2]. > > This is no longer true in Jessie and therefore we have to use radeon, > not radeonfb. Otherwise you won't get any X display. What did you do to ensure the radeon module is included in debian installer? > >>> The reason is that the radeon KMS module does not work once >>> radoenfb has been loaded once. Even if you unload radeonfb later, >>> the radeon module will still refuse to work meaning X will not be >>> usable. >>> > >> This is good to know. > > I did thorough testing for the bug report you linked above which is > why I am a bit surprised you could convince Ben so easily to partly > revert my change. I think I also explained in the other bug tracker > that you have to use KMS these days as UMS is being phased out. > There is no revert of your change at all. We are just trying to add a module to debian installer to enable installation on machines with no native offb support, the machines you have skipped in your thorough testing. Any input on the best way to achieve this is welcome. >>> Well, I think this can be answered straight-forward: radeonfb is >>> the wrong solution as radeonfb does not support X which means you >>> can use the text-based installer only. But I guess you never >>> tested that as you stated in your bug report. >>> How is that X display in debian installer on PowerPC platform working for you? >>> The proper fix for your problem is not to revert my previous fix >>> but to use the proper driver, thus reopening. >>> > >> There was no "my previous fix," just reporting about the state of >> the things in RC1 and RC2. I'm trying to help as I have access to >> more than a few power and powerpc machines. > > Sure, but please ask people in the future before you are asking for > changes which you don't understand. Your understanding of the consequences of your changes is trully stellar. > I also have tons of different > hardware available here, including several powerpc machines and > way beyond that (m68k, sh4, mips etc). > b > I think you should at least discuss such changes with some more people > before you ask for them to be integrated. Well, I've asked, no one complained until you showed up. The resulting discussion spreads very interesting scent. > For anyone who follows X.Org > and kernel development, it is common knowledge that all the non-KMS > drivers in the kernel are being deprecated and that you should no > longer use them. This also applies to X.Org. > > It would be nice if you could CC me in the future if you are having > issues with non-x86 hardware, especially anything that's powerpc, > Macintosh, or - like in this case - Amiga-related hardware. Are you sure you want to know about every non-x86 issue I face on daily basis? M signature.asc Description: OpenPGP digital signature
Bug#782058: Pegasos II: installer boots up to 'returning from prom_init'
On Thu, 2015-04-09 at 10:08 +0200, John Paul Adrian Glaubitz wrote: > On 04/09/2015 12:38 AM, Milan Kupcevic wrote: > >> Well, yes. As you could see from the bug report you linked above, > >> compiling radeonfb into the kernel broke X on basically all > >> Radeon cards. > >> > > > > It seems that radeonfb was compiled into the kernel since the dawn > > of time. > > On the powerpc Debian kernel, yes, on the other architectures, no. > radeonfb has been deprecated long time ago and should no longer be > used. > > The only reason it was compiled into the powerpc kernel without anyone > complaining is the fact that the xf86-video-ati (= Radeon X.Org) driver > in Wheezy was still old enough [1] to support userland mode-setting > which was dropped upstream in version 7.0.0 almost three years ago [2]. > > This is no longer true in Jessie and therefore we have to use radeon, > not radeonfb. Otherwise you won't get any X display. If you use the xserver-xorg-video-radeon driver. (Which of course, is the sensible choice in an actual Debian installation.) > >> The reason is that the radeon KMS module does not work once > >> radoenfb has been loaded once. Even if you unload radeonfb later, > >> the radeon module will still refuse to work meaning X will not be > >> usable. > >> > > > > This is good to know. > > I did thorough testing for the bug report you linked above which is > why I am a bit surprised you could convince Ben so easily to partly > revert my change. I think I also explained in the other bug tracker > that you have to use KMS these days as UMS is being phased out. [...] It isn't reverted. All I've done is to add radeonfb.ko to the drivers that are included *in the installer*. Neither radeon.ko nor xserver-xorg-video-radeon are included in the installer, so how could they possibly be used? If you though those should be used in the installer, you should have told people that earlier. As it is, I think that the installer should be able to work using radeonfb.ko and xserver-xorg-video-fbdev, though I'm not sure whether radeonfb.ko will be loaded automatically. Ben. -- Ben Hutchings I'm always amazed by the number of people who take up solipsism because they heard someone else explain it. - E*Borg on alt.fan.pratchett signature.asc Description: This is a digitally signed message part
Bug#782058: Pegasos II: installer boots up to 'returning from prom_init'
-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 On 04/09/2015 10:08 AM, John Paul Adrian Glaubitz wrote: > The only reason it was compiled into the powerpc kernel without > anyone complaining is the fact that the xf86-video-ati (= Radeon > X.Org) driver in Wheezy was still old enough [1] to support > userland mode-setting which was dropped upstream in version 7.0.0 > almost three years ago [2]. Forgot the references. > [1] https://packages.qa.debian.org/x/xserver-xorg-video-ati.html > [2] > http://lists.x.org/archives/xorg-announce/2012-November/002093.html - -- > .''`. John Paul Adrian Glaubitz : :' : Debian Developer - glaub...@debian.org `. `' Freie Universitaet Berlin - glaub...@physik.fu-berlin.de `-GPG: 62FF 8A75 84E0 2956 9546 0006 7426 3B37 F5B5 F913 -BEGIN PGP SIGNATURE- Version: GnuPG v1 iQIcBAEBCAAGBQJVJjOqAAoJEHQmOzf1tfkTKVMP/jfVh6SApUn4+CZLWvouH3Vx gJbD9k1sv1BQ9PbF9LZXtxoUX5nEkqZPdGBx3YFbwgv6wxdshELP6T6oIEf/ui+L xtPoA1BuRf4FFZVWOzT/5+agXuJYIYkc6Wn2ctT5glU6wgjYB0iArxuR2spxuoDg wfsDpGQ93W9XB2BEyxFpolTkY+tYR/OyTQRWPYMqg1MvAnPte5WXsLpI7fT7PERt ACcNDDgV9O780GDKS0KgntlV30JDk3yBVuFXqAFEMLTK7exIiaurKR0CUxRqFvR5 kU80jw9FK0wxQ7VppMxRbrudqeWByqwNd1CKrD7wA8Yq3uIfC0IZyoxcPR54STc5 bqfuCMOZU2NwsANRjNXHo7ywbuMJLymgMW0sO1Y51ke0JsYAzFFeoTd4eVnvv1Ft /8D1ETEYdgQbgTn9VSciMplPCMenKh61Em2RPh310VgCczcPH+bVyQAtrbSSYLUe +6d25iCM98OeHJRwUY9taCQXzTl22Ix+fmOT9EwPshzwJ8IaurvpDYr3eVi88KaY VF0oqNBsTbAdtgZPz2cZOITRiHe6yrQMSjwvPxK0AYJhMr16ecXYuQpPP6DlNyE2 OASqNVLKLSkwrCGqXwAa87glr7/DX499V2EwSuYEaq8M2oJhtSePrk0eD6K86vmF yFnT92Z0zB8vRh9UfoIp =qino -END PGP SIGNATURE- -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#782058: Pegasos II: installer boots up to 'returning from prom_init'
-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 On 04/09/2015 12:38 AM, Milan Kupcevic wrote: >> Well, yes. As you could see from the bug report you linked above, >> compiling radeonfb into the kernel broke X on basically all >> Radeon cards. >> > > It seems that radeonfb was compiled into the kernel since the dawn > of time. On the powerpc Debian kernel, yes, on the other architectures, no. radeonfb has been deprecated long time ago and should no longer be used. The only reason it was compiled into the powerpc kernel without anyone complaining is the fact that the xf86-video-ati (= Radeon X.Org) driver in Wheezy was still old enough [1] to support userland mode-setting which was dropped upstream in version 7.0.0 almost three years ago [2]. This is no longer true in Jessie and therefore we have to use radeon, not radeonfb. Otherwise you won't get any X display. >> The reason is that the radeon KMS module does not work once >> radoenfb has been loaded once. Even if you unload radeonfb later, >> the radeon module will still refuse to work meaning X will not be >> usable. >> > > This is good to know. I did thorough testing for the bug report you linked above which is why I am a bit surprised you could convince Ben so easily to partly revert my change. I think I also explained in the other bug tracker that you have to use KMS these days as UMS is being phased out. >> Well, I think this can be answered straight-forward: radeonfb is >> the wrong solution as radeonfb does not support X which means you >> can use the text-based installer only. But I guess you never >> tested that as you stated in your bug report. >> >> The proper fix for your problem is not to revert my previous fix >> but to use the proper driver, thus reopening. >> > > There was no "my previous fix," just reporting about the state of > the things in RC1 and RC2. I'm trying to help as I have access to > more than a few power and powerpc machines. Sure, but please ask people in the future before you are asking for changes which you don't understand. I also have tons of different hardware available here, including several powerpc machines and way beyond that (m68k, sh4, mips etc). I think you should at least discuss such changes with some more people before you ask for them to be integrated. For anyone who follows X.Org and kernel development, it is common knowledge that all the non-KMS drivers in the kernel are being deprecated and that you should no longer use them. This also applies to X.Org. It would be nice if you could CC me in the future if you are having issues with non-x86 hardware, especially anything that's powerpc, Macintosh, or - like in this case - Amiga-related hardware. Adrian - -- .''`. John Paul Adrian Glaubitz : :' : Debian Developer - glaub...@debian.org `. `' Freie Universitaet Berlin - glaub...@physik.fu-berlin.de `-GPG: 62FF 8A75 84E0 2956 9546 0006 7426 3B37 F5B5 F913 -BEGIN PGP SIGNATURE- Version: GnuPG v1 iQIcBAEBCAAGBQJVJjNyAAoJEHQmOzf1tfkTItwQAJid5vaSBdjsJBSROc7URnNp G7kc6AEF3oaEbX1lsqQ/wfvfKsFdKztN+ro4oAPW7xgo/QxQI7qWuDxNgTvbyOl2 9ApGjwliLKU5D4em479V58qTUnl0agcTqJxruWU88Kdb5NxUQrtAnRdqrmak6e5m pHPA+uMREu8KKM1TDOjw1ErJEKUXV8lnH+LVKIWRvWBoS9n63mHTZv69YDwSTZvh +V4zhVqwb++kcrVYX+GqPaeX+/N5hH1SaS2PAwqZCXXNXMm0x3XAHNVwk1GvvDek e+pZEiJi3pr7AtyJuzHsREQyIc3ivgDzw14DUvXIpSdrvkufj1jo/WbmkT+F9aik W0Tl5mu3zFW5pmXnGInL1umUv1JcE6yE79WorCYf+xDPHnfAZfkozy7nzPdjdZrO tV1PVdNg+tpPzJzD3JC8/x+YonvOolpvVCBRiJ43c5s80pV3yNglavPNEe/TEkFE ULwzvAbp72HyBirFX1S0aTlLbI85oRrxzcGfZrao0HTA6tm9nj9rsjPWpbaGjjsQ oWcX2b6xjBu7ng73Hpi8BIaLj6ECrt0hdMUGAvDf1OnMdYzNjSqX8gpJjjOJJpDs QQwfkSeZW8IVF1Nm5U6QTJ9Mgbcma19EDQyARyCiAKnscFMMp+iWDs0pBmKfXqZA zHWeVlv7eqivC+qDfMmU =mU0y -END PGP SIGNATURE- -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#782058: Pegasos II: installer boots up to 'returning from prom_init'
On 04/08/2015 04:02 PM, John Paul Adrian Glaubitz wrote: > Control: reopen -1 > > On 04/08/2015 09:51 PM, Milan Kupcevic wrote: >> In Wheezy and in Jessie RC1 radenfb was compiled in the kernel >> itself while debian installer worked fine on this machine. > > Well, yes. As you could see from the bug report you linked above, > compiling radeonfb into the kernel broke X on basically all Radeon > cards. > It seems that radeonfb was compiled into the kernel since the dawn of time. > The reason is that the radeon KMS module does not work once radoenfb > has been loaded once. Even if you unload radeonfb later, the radeon > module will still refuse to work meaning X will not be usable. > This is good to know. > If you want to use X, you **have** to use the radeon KMS driver as > the xf86-video-radeon driver does no longer support UMS modesetting > which means no matter what you do, you will **never** be able to run > X once radeonfb is loaded until next reboot. > Okay. >> Neither radeon nor radeonfb driver is included in RC2 debian >> installer. > > Well, yes, we forgot to include radeon, true. > [...] > >> Whether we want to include radeonfb module or radeon KMS module in >> debian installer is question open to discussion. > > Well, I think this can be answered straight-forward: radeonfb is the > wrong solution as radeonfb does not support X which means you can use > the text-based installer only. But I guess you never tested that as > you stated in your bug report. > > The proper fix for your problem is not to revert my previous fix but > to use the proper driver, thus reopening. > There was no "my previous fix," just reporting about the state of the things in RC1 and RC2. I'm trying to help as I have access to more than a few power and powerpc machines. As for the "proper driver," I'm all for it. We are lucky to have you around to take care of these issues. I'm looking forward to download and install final Jessie release on many machines with no problems at all. Milan signature.asc Description: OpenPGP digital signature
Bug#782058: Pegasos II: installer boots up to 'returning from prom_init'
On 04/08/2015 02:03 PM, John Paul Adrian Glaubitz wrote: > Hi Milan! > > I just stumbled across this bug report and was actually wondering why > your Pegasos-II board won't work properly with the radeon KMS driver. > > As far as I know, the Radeon 9250 found on the Pegasos-II board is fully > supported by the radeon KMS driver, so I'd expect it to work out-of > the-box. I always had the opinion that radeonfb was deprecated in > favor of the KMS driver and therefore the latter is the one you should > be using. > > Maybe it's a good idea to report any issues with the KMS driver to the > radeon upstream developers? > In Wheezy and in Jessie RC1 radenfb was compiled in the kernel itself while debian installer worked fine on this machine. Neither radeon nor radeonfb driver is included in RC2 debian installer. OpenFirmware frame buffer never worked on Pegasos machines so I had to use serial port to install RC2. After successful installation, the machine boots up and uses radeon KMS installed on its HD. Whether we want to include radeonfb module or radeon KMS module in debian installer is question open to discussion. Milan -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#782058: Pegasos II: installer boots up to 'returning from prom_init'
Control: reopen -1 Hi! On 04/08/2015 09:51 PM, Milan Kupcevic wrote: > In Wheezy and in Jessie RC1 radenfb was compiled in the kernel itself > while debian installer worked fine on this machine. Well, yes. As you could see from the bug report you linked above, compiling radeonfb into the kernel broke X on basically all Radeon cards. The reason is that the radeon KMS module does not work once radoenfb has been loaded once. Even if you unload radeonfb later, the radeon module will still refuse to work meaning X will not be usable. If you want to use X, you **have** to use the radeon KMS driver as the xf86-video-radeon driver does no longer support UMS modesetting which means no matter what you do, you will **never** be able to run X once radeonfb is loaded until next reboot. > Neither radeon nor radeonfb driver is included in RC2 debian installer. Well, yes, we forgot to include radeon, true. > OpenFirmware frame buffer never worked on Pegasos machines so I had to > use serial port to install RC2. After successful installation, the > machine boots up and uses radeon KMS installed on its HD. Alright, then your fix was wrong. We should have included radeon, **not** the deprecated radeonfb driver which does no longer work with X and will probably removed from the kernel at some point. > Whether we want to include radeonfb module or radeon KMS module in > debian installer is question open to discussion. Well, I think this can be answered straight-forward: radeonfb is the wrong solution as radeonfb does not support X which means you can use the text-based installer only. But I guess you never tested that as you stated in your bug report. The proper fix for your problem is not to revert my previous fix but to use the proper driver, thus reopening. Cheers, Adrian -- .''`. John Paul Adrian Glaubitz : :' : Debian Developer - glaub...@debian.org `. `' Freie Universitaet Berlin - glaub...@physik.fu-berlin.de `-GPG: 62FF 8A75 84E0 2956 9546 0006 7426 3B37 F5B5 F913 -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#782058: Pegasos II: installer boots up to 'returning from prom_init'
Hi Milan! I just stumbled across this bug report and was actually wondering why your Pegasos-II board won't work properly with the radeon KMS driver. As far as I know, the Radeon 9250 found on the Pegasos-II board is fully supported by the radeon KMS driver, so I'd expect it to work out-of the-box. I always had the opinion that radeonfb was deprecated in favor of the KMS driver and therefore the latter is the one you should be using. Maybe it's a good idea to report any issues with the KMS driver to the radeon upstream developers? Cheers, Adrian -- .''`. John Paul Adrian Glaubitz : :' : Debian Developer - glaub...@debian.org `. `' Freie Universitaet Berlin - glaub...@physik.fu-berlin.de `-GPG: 62FF 8A75 84E0 2956 9546 0006 7426 3B37 F5B5 F913 -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#782058: Pegasos II: installer boots up to 'returning from prom_init'
Package: src:linux Version: 3.16.7-ckt7-1 Severity: important Tags: d-i jessie The last line seen on the screen after installer CD boots is 'returning from prom_init'. This is a regression introduced in d-i rc2 which persist in daily builds. Connecting serial terminal and booting with 'console=ttyS0,9600' allows successful installation of jessie. (with some hiccups that warrant a separate bug report to mkvmlinuz). I'm aware that fix for bug #748398 actually introduced this regression. The radeonfb is currently compiled as module which is not included in the installer. I hope that including the radeonfb module in the installer will fix this issue. This report was generated on the same machine after successful installation. Could you please add radeonfb module to debian installer? Milan -- Package-specific info: ** Version: Linux version 3.16.0-4-powerpc (debian-ker...@lists.debian.org) (gcc version 4.8.4 (Debian 4.8.4-1) ) #1 Debian 3.16.7-ckt7-1 (2015-03-01) ** Command line: root=/dev/sda2 ** Tainted: W (512) * Taint on warning. ** Kernel log: [9.107171] [drm] Connector 0: [9.107180] [drm] VGA-1 [9.107193] [drm] DDC: 0x60 0x60 0x60 0x60 0x60 0x60 0x60 0x60 [9.107206] [drm] Encoders: [9.107216] [drm] CRT1: INTERNAL_DAC1 [9.107227] [drm] Connector 1: [9.107237] [drm] DVI-I-1 [9.107246] [drm] HPD1 [9.107258] [drm] DDC: 0x64 0x64 0x64 0x64 0x64 0x64 0x64 0x64 [9.107269] [drm] Encoders: [9.107279] [drm] CRT2: INTERNAL_DAC2 [9.107290] [drm] DFP1: INTERNAL_TMDS1 [9.138249] EXT4-fs (sda2): re-mounted. Opts: errors=remount-ro [9.222863] [drm] fb mappable at 0xC004 [9.222913] [drm] vram apper at 0xC000 [9.222924] [drm] size 5242880 [9.222934] [drm] fb depth is 24 [9.222944] [drm]pitch is 5120 [9.275221] Console: switching to colour frame buffer device 160x64 [9.316086] radeon 0001:01:08.0: fb0: radeondrmfb frame buffer device [9.316398] radeon 0001:01:08.0: registered panic notifier [9.320300] [drm] Initialized radeon 2.39.0 20080528 for 0001:01:08.0 on minor 0 [9.679644] Adding 3012180k swap on /dev/sda3. Priority:-1 extents:1 across:3012180k FS [9.722815] EXT4-fs (sda1): mounting ext2 file system using the ext4 subsystem [9.732480] EXT4-fs (sda1): mounted filesystem without journal. Opts: (null) [9.872623] snd_via82xx_modem: probe of :00:0c.6 failed with error -13 [9.873912] snd_via82xx :00:0c.5: enabling device ( -> 0001) [ 10.234992] systemd-journald[133]: Received request to flush runtime journal from PID 1 [ 10.425400] via-rhine :00:0d.0: enabling device ( -> 0003) [ 10.460940] via-rhine :00:0d.0 eth0: VIA Rhine II at 0xf1ffe900, 00:0b:2f:43:fb:04, IRQ 9 [ 10.462200] via-rhine :00:0d.0 eth0: MII PHY found at address 16, status 0x786d advertising 01e1 Link c5e1 [ 10.480763] uhci_hcd :00:0c.2: UHCI Host Controller [ 10.481103] uhci_hcd :00:0c.2: new USB bus registered, assigned bus number 1 [ 10.481482] uhci_hcd :00:0c.2: detected 2 ports [ 10.481768] uhci_hcd :00:0c.2: irq 9, io base 0x1040 [ 10.482306] usb usb1: New USB device found, idVendor=1d6b, idProduct=0001 [ 10.482646] usb usb1: New USB device strings: Mfr=3, Product=2, SerialNumber=1 [ 10.496172] usb usb1: Product: UHCI Host Controller [ 10.509022] usb usb1: Manufacturer: Linux 3.16.0-4-powerpc uhci_hcd [ 10.521857] usb usb1: SerialNumber: :00:0c.2 [ 10.587163] hub 1-0:1.0: USB hub found [ 10.587190] hub 1-0:1.0: 2 ports detected [ 10.587827] ehci-pci :00:05.2: EHCI Host Controller [ 10.587850] ehci-pci :00:05.2: new USB bus registered, assigned bus number 2 [ 10.588018] ehci-pci :00:05.2: irq 9, io mem 0x80002800 [ 10.596335] ehci-pci :00:05.2: USB 2.0 started, EHCI 1.00 [ 10.596575] usb usb2: New USB device found, idVendor=1d6b, idProduct=0002 [ 10.596581] usb usb2: New USB device strings: Mfr=3, Product=2, SerialNumber=1 [ 10.596585] usb usb2: Product: EHCI Host Controller [ 10.596589] usb usb2: Manufacturer: Linux 3.16.0-4-powerpc ehci_hcd [ 10.596593] usb usb2: SerialNumber: :00:05.2 [ 10.597535] hub 2-0:1.0: USB hub found [ 10.597685] hub 2-0:1.0: 5 ports detected [ 10.598436] uhci_hcd :00:0c.3: UHCI Host Controller [ 10.598457] uhci_hcd :00:0c.3: new USB bus registered, assigned bus number 3 [ 10.598473] uhci_hcd :00:0c.3: detected 2 ports [ 10.598522] uhci_hcd :00:0c.3: irq 9, io base 0x1060 [ 10.598731] usb usb3: New USB device found, idVendor=1d6b, idProduct=0001 [ 10.598737] usb usb3: New USB device strings: Mfr=3, Product=2, SerialNumber=1 [ 10.598741] usb usb3: Product: UHCI Host Controller [ 10.598744] usb usb3: Manufacturer: Linux 3.16.0-4-powerpc uhci_hcd [ 10.598748] usb usb3: SerialNumber: :00:0c.3 [ 10.599440] hub 3-0:1.0: USB hub found [ 10.599573] hub 3-0:1.0: 2 ports detected [ 10.946
