Re: Bug#403364: SunBlade 150 problems - can anyone confirm?
Hello Frans, * Frans Pop <[EMAIL PROTECTED]>, [2007-07-02 15:09 +0200]: > On Monday 02 July 2007 14:21, Emanuele Rocca wrote: > > The "output to the wrong screen" issue is well known, here's last > > upstream comment: http://article.gmane.org/gmane.linux.ports.sparc/7659 > > Thanks for the link. Does that address both the "ATI + creator3D" case and > the "only ATI" case? I guess it should address both. > What about the "red dots" issue? Is that already known upstream? I don't know about this one, my blade 2k is not affected. Jim, could you please try the last rc kernel (2.6.22-rc7) and send a report to [EMAIL PROTECTED] if the bug is still present? Thanks. ciao, ema -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: Bug#403364: SunBlade 150 problems - can anyone confirm?
On Monday 02 July 2007 14:21, Emanuele Rocca wrote: > The "output to the wrong screen" issue is well known, here's last > upstream comment: http://article.gmane.org/gmane.linux.ports.sparc/7659 Thanks for the link. Does that address both the "ATI + creator3D" case and the "only ATI" case? What about the "red dots" issue? Is that already known upstream? pgpu0Kna3qTKz.pgp Description: PGP signature
Re: Bug#403364: SunBlade 150 problems - can anyone confirm?
Hello Frans, * Frans Pop <[EMAIL PROTECTED]>, [2007-07-02 14:14 +0200]: > Debian is not the place where such issues get solved, you have to get onto > the upstream list ([EMAIL PROTECTED]) or the kernel BTS > (bugzilla.kernel.org). Both issues are probably already known upstream, > but it is good to remind the upstream developers about them once in a > while. The "output to the wrong screen" issue is well known, here's last upstream comment: http://article.gmane.org/gmane.linux.ports.sparc/7659 ciao, ema -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: Bug#403364: SunBlade 150 problems - can anyone confirm?
On Monday 02 July 2007 13:44, jim watson wrote: > On my Sunblade100 this is fixed in debian unstable 2.6.21-1 but > video=atyfb:off is still needed anyway to avoid those red dots. Hmm. I seem to be having dejavu experiences in this thread... Is anybody currently trying to work with the upstream kernel people to get these issues resolved or is everybody just kind of looking at each other and hoping things will magically get resolved somehow? Debian is not the place where such issues get solved, you have to get onto the upstream list ([EMAIL PROTECTED]) or the kernel BTS (bugzilla.kernel.org). Both issues are probably already known upstream, but it is good to remind the upstream developers about them once in a while. Cheers, FJP pgpPZLdeB9Mu3.pgp Description: PGP signature
Re: Bug#403364: SunBlade 150 problems - can anyone confirm?
निशांत / Nishant wrote: Hi, On 7/2/07, Thomas Köllmann <[EMAIL PROTECTED]> wrote: > >> Maybe this is useful to the next guy installing Etch (or some other >> post-2.6.16 kernel) on a Blade 150 (or 100). > > Can you confirm that with a 2.6.16 kernel the problem is not > reproducible? But now I am facing the problem with 2.6.18-4-sparc64. I need to use video=atyfb:off to be able to boot. I am on a SunBlade150. regards, Nishant On my Sunblade100 this is fixed in debian unstable 2.6.21-1 but video=atyfb:off is still needed anyway to avoid those red dots. jim -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: Bug#403364: SunBlade 150 problems - can anyone confirm?
Hi, On 7/2/07, Thomas Köllmann <[EMAIL PROTECTED]> wrote: > >> Maybe this is useful to the next guy installing Etch (or some other >> post-2.6.16 kernel) on a Blade 150 (or 100). > > Can you confirm that with a 2.6.16 kernel the problem is not > reproducible? But now I am facing the problem with 2.6.18-4-sparc64. I need to use video=atyfb:off to be able to boot. I am on a SunBlade150. regards, Nishant -- How about some patent on "(a+b)2 = a2+2ab+b2". Choose free software! http://www.nishants.net
Re: Bug#403364: SunBlade 150 problems - can anyone confirm?
Hi, Emanuele! Sorry for the late reply -- I moved, switched jobs, started a new and much better life... :-) Emanuele Rocca wrote: > Hello Thomas, > > * Thomas Köllmann <[EMAIL PROTECTED]>, [2006-12-17 22:43 +0100]: >> On Sat, 16 Dec 2006 11:01:07 -0800 >> Jurij Smakov <[EMAIL PROTECTED]> wrote: >> >> > I don't remember anyone reporting problems with xorg on these >> > machines, it would be very valuable information if you could try it >> > and report back. >> >> Maybe this is useful to the next guy installing Etch (or some other >> post-2.6.16 kernel) on a Blade 150 (or 100). > > Can you confirm that with a 2.6.16 kernel the problem is not > reproducible? Yes, I can confirm that. linux-image-2.6.16-2-sparc64 worked well and without the video=atyfb:off boot parameter. > Does the machine completely fail to boot if you don't pass > video=atyfb:off to the kernel? (ie: are you able to login somehow, for > instance via ssh?). Yes, it hangs very early in the boot process after the messages: Remapping the kernel... done. Booting Linux... No harddisk activity after that, no ssh, no ping echo, no nothing. Greetings, - Thomas -- /* PGP key auf Wunsch per e-mail || PGP key sent on request */ -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: Bug#403364: SunBlade 150 problems - can anyone confirm?
Hello Thomas, * Thomas Köllmann <[EMAIL PROTECTED]>, [2006-12-17 22:43 +0100]: > On Sat, 16 Dec 2006 11:01:07 -0800 > Jurij Smakov <[EMAIL PROTECTED]> wrote: > > > I don't remember anyone reporting problems with xorg on these > > machines, it would be very valuable information if you could try it > > and report back. > > Maybe this is useful to the next guy installing Etch (or some other > post-2.6.16 kernel) on a Blade 150 (or 100). Can you confirm that with a 2.6.16 kernel the problem is not reproducible? Does the machine completely fail to boot if you don't pass video=atyfb:off to the kernel? (ie: are you able to login somehow, for instance via ssh?). Thanks. ciao, ema -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: Re: SunBlade 150 problems - can anyone confirm?
(Sorry about broken formatting, im replying to the archive) On 17/12/2006, at 5:55 AM, Thomas Köllmann wrote: On Sat, 16 Dec 2006 10:38:58 -0800 Jurij Smakov <[EMAIL PROTECTED]> wrote: Please try booting it with the boot parameter video=atyfb:off, i.e. instead of just pressing enter at the silo boot prompt type Linux video=atyfb:off Yes, that works. Does this have any drawbacks regarding the use of xorg? (I haven't yet installed that...) I can confirm this problem exists on Sunblade100 with the 2.6.18-3 (Mon 4 Dec) and the same fix works. :: my stuff :: I'm not able to boot a sunblade150. i'm using (what i assume is) an older install cd (2006), and I'm not entirely sure what kernel it uses. i think its a 2.6.17-* kernel. I'm hoping someone can look at what i entered and tell me how I'm passing the parameters wrong. Or tell me to use a newer cd :) * Video card in (an ATI Radeon from 2002, not sure what exactly) no switches video=atyfb:off ide=nodma ide=nodma mem=512 * Video card out (illegal instruction error for all trys, drops back to [ok]) no switches expert video=atyfb:off expert append="atyfb:off ide=nodma" expert append="video=atyfb:off ide=nodma" expert video=atyfb:off ide=nodma Karl (list member, just disconnected from main comp atm)
Re: SunBlade 150 problems - can anyone confirm?
On Sat, 16 Dec 2006 11:01:07 -0800 Jurij Smakov <[EMAIL PROTECTED]> wrote: > I don't remember anyone reporting problems with xorg on these > machines, it would be very valuable information if you could try it > and report back. Ok, thanks; I did, and xorg is working fine. You have to set Option "ReferenceClock""29.500MHz" in the "Device" section of your xorg.conf though (this seems known information). Also, apart from "video=atyfb:off" I gave the kernel a "ide=nodma" parameter because it complained about DMA timeouts soon after booting. (This, too, seems a known issue. Line added to my silo.conf: append="video=atyfb:off ide=nodma") Afterwards I installed hdparm and found that UDMA3 is the fastest mode in that the kernel does not complain (so far, at least). I made this permanent by setting hdparm_opts="-d1 -X udma3" in /etc/default/hdparm. Maybe this is useful to the next guy installing Etch (or some other post-2.6.16 kernel) on a Blade 150 (or 100). Thanks to everyone, - Thomas -- /* PGP key auf Wunsch per e-mail || PGP key sent on request */ -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: SunBlade 150 problems - can anyone confirm?
On 17/12/2006, at 5:55 AM, Thomas Köllmann wrote: On Sat, 16 Dec 2006 10:38:58 -0800 Jurij Smakov <[EMAIL PROTECTED]> wrote: Please try booting it with the boot parameter video=atyfb:off, i.e. instead of just pressing enter at the silo boot prompt type Linux video=atyfb:off Yes, that works. Does this have any drawbacks regarding the use of xorg? (I haven't yet installed that...) I can confirm this problem exists on Sunblade100 with the 2.6.18-3 (Mon 4 Dec) and the same fix works. I have been using xorg and also using video=atyfb:off to avoid the "red dots" issue, no problems I can see, only the alternative consoles have some unusable frame outside, about 20% of the screen area. Jim
Re: SunBlade 150 problems - can anyone confirm?
On Sat, 16 Dec 2006 10:38:58 -0800 Jurij Smakov <[EMAIL PROTECTED]> wrote: > On Sat, Dec 16, 2006 at 07:32:29PM +0100, Thomas Köllmann wrote: > > > atyfb: 3D RAGE XL (Mach64 GR, PCI-33) [0x4752 rev 0x27] > > atyfb: 8M SDRAM (1:1), 29.498928 MHz XTAL, 235 MHz PLL, 83 Mhz MCLK, 63 > > MHz XCLK Console: switching to colour frame buffer device 144x56 > > atyfb: fb0: ATY Mach64 frame buffer device on PCI > > Please try booting it with the boot parameter video=atyfb:off, i.e. > instead of just pressing enter at the silo boot prompt type > > Linux video=atyfb:off Yes, that works. Does this have any drawbacks regarding the use of xorg? (I haven't yet installed that...) Thanks, - Thomas -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: SunBlade 150 problems - can anyone confirm?
On Sat, Dec 16, 2006 at 07:55:13PM +0100, Thomas Köllmann wrote: > > Please try booting it with the boot parameter video=atyfb:off, i.e. > > instead of just pressing enter at the silo boot prompt type > > > > Linux video=atyfb:off > > Yes, that works. > > Does this have any drawbacks regarding the use of xorg? (I haven't > yet installed that...) I don't remember anyone reporting problems with xorg on these machines, it would be very valuable information if you could try it and report back. Thanks, -- Jurij Smakov [EMAIL PROTECTED] Key: http://www.wooyd.org/pgpkey/ KeyID: C99E03CC -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: Bug#403364: SunBlade 150 problems - can anyone confirm?
On Saturday 16 December 2006 17:58, Jurij Smakov wrote: > Since you are the only person who reported such a problem so far, I > feel that severity is a bit too high, so I'm dropping it to > 'important' for now. I'm also CC'ing this message to the debian-sparc > mailing list to ask whether anybody else is seeing similar problems. There's something similar for a SunBlade 100 in installation report #402282 [1]. Cheers, FJP [1] http://bugs.debian.org/402282 pgpzpvj7TjgeH.pgp Description: PGP signature
Re: SunBlade 150 problems - can anyone confirm?
Hi, Jurij! On Sat, 16 Dec 2006 08:58:55 -0800 Jurij Smakov <[EMAIL PROTECTED]> wrote: > Since you are the only person who reported such a problem so far, I > feel that severity is a bit too high, so I'm dropping it to > 'important' for now. Sure, whatever you feel is in order. > Do you have more than one videocard in this machine? No, only the onboard ATI card: atyfb: 3D RAGE XL (Mach64 GR, PCI-33) [0x4752 rev 0x27] atyfb: 8M SDRAM (1:1), 29.498928 MHz XTAL, 235 MHz PLL, 83 Mhz MCLK, 63 MHz XCLK Console: switching to colour frame buffer device 144x56 atyfb: fb0: ATY Mach64 frame buffer device on PCI (This is from dmesg when running 2.6.16-17.) Thanks, - Thomas -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: SunBlade 150 problems - can anyone confirm?
On Sat, Dec 16, 2006 at 07:32:29PM +0100, Thomas Köllmann wrote: > No, only the onboard ATI card: > > atyfb: 3D RAGE XL (Mach64 GR, PCI-33) [0x4752 rev 0x27] > atyfb: 8M SDRAM (1:1), 29.498928 MHz XTAL, 235 MHz PLL, 83 Mhz MCLK, 63 MHz > XCLK > Console: switching to colour frame buffer device 144x56 > atyfb: fb0: ATY Mach64 frame buffer device on PCI Please try booting it with the boot parameter video=atyfb:off, i.e. instead of just pressing enter at the silo boot prompt type Linux video=atyfb:off there. Thanks, -- Jurij Smakov [EMAIL PROTECTED] Key: http://www.wooyd.org/pgpkey/ KeyID: C99E03CC -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
SunBlade 150 problems - can anyone confirm?
severity 403364 important thanks Hi Thomas, On Sat, Dec 16, 2006 at 06:05:52PM +0100, Thomas Koellmann wrote: > Package: linux-image-2.6.18-3-sparc64 > Version: 2.6.18-7 > Severity: critical > Justification: breaks the whole system Since you are the only person who reported such a problem so far, I feel that severity is a bit too high, so I'm dropping it to 'important' for now. I'm also CC'ing this message to the debian-sparc mailing list to ask whether anybody else is seeing similar problems. > This kernel, which seems currently to be the latest in testing/etch, > hangs on my Sun Blade 150 after displaying "Booting Linux" (at that > stage where linux-image-2.6.16-2-sparc64 switches video resolution). > > This is a fresh install using d-i beta-3 (d-i etch rc-1 also hangs > early in the boot process). Do you have more than one videocard in this machine? If that's the case, it might be that the machine is still booting, but the output goes to a different videocard. Best regards, -- Jurij Smakov [EMAIL PROTECTED] Key: http://www.wooyd.org/pgpkey/ KeyID: C99E03CC -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
