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
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
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
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
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.
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 regardin
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 e
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 Cons
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 14
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
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
11 matches
Mail list logo
