Re: Bug#237075: Bug not related to Sparc64... Maybe related to Creator?
reassign 237075 kernel-image-2.4.26-sparc64 severity 237075 important merge 237075 245620 thanks On Fri, Mar 19, 2004 at 05:20:15PM +0100, Thomas Poindessous wrote: On Fri, Mar 19, 2004 at 03:18:47PM +0100, Reinhard Tartler wrote: This image still has the problem with unable to open initial console so the option devfs=mount was needed. Not so in Jeff Bailey's build. bterm keeps on segfaulting with this image too. then you indeed found a bug in bterm I think this is the same as 245620. It's a kernel bug, not bterm. -- Daniel Jacobowitz -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Bug#237075: Bug not related to Sparc64... Maybe related to Creator?
On Tue, Mar 16, 2004 at 03:50:27PM -0800, Blars Blarson wrote: The creator is removable, but unless you have an sbus framebuffer there isn't much point. The ultra 1 does not have an onboard framebuffer. You can try using a serial console by disconnecting the keyboard and using serial port a. (Default 9600 baud.) Well, due to the fact that I get the debian-installer menu when booting with the option framebuffer=false I think that installing via serial console works. But that doesn't resolve the Problem that bterm is broken on sparc64, i.e. that displaying UTF-8 characters is not possible. This Problem should at least be documented bevore d-i ist released. regards, Reinhard -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Bug#237075: Bug not related to Sparc64... Maybe related to Creator?
On Fri, Mar 19, 2004 at 12:16:51PM +0100, Reinhard Tartler wrote: On Tue, Mar 16, 2004 at 03:50:27PM -0800, Blars Blarson wrote: Well, due to the fact that I get the debian-installer menu when booting with the option framebuffer=false I think that installing via serial console works. But that doesn't resolve the Problem that bterm is broken on sparc64, i.e. that displaying UTF-8 characters is not possible. I think this problem is resolved. You were using unofficial image of d-i made by Jeff Bailey, and it seems that his build system wasn't using the last version of libbogl-dev. This Problem should at least be documented bevore d-i ist released. Could you please retry with a official build ? Thanks PS : you can use image from http://ftp.debian.org/debian/dists/unstable/main/installer-sparc/ -- Thomas Poindessous -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Bug#237075: Bug not related to Sparc64... Maybe related to Creator?
On Fri, Mar 19, 2004 at 02:43:28PM +0100, Thomas Poindessous wrote: I think this problem is resolved. You were using unofficial image of d-i made by Jeff Bailey, and it seems that his build system wasn't using the last version of libbogl-dev. [...] Could you please retry with a official build ? Sure. I just booted this image: http://ftp.debian.org/debian/dists/unstable/main/installer-sparc/20040315/images/sparc64/netboot/boot.img This image still has the problem with unable to open initial console so the option devfs=mount was needed. Not so in Jeff Bailey's build. bterm keeps on segfaulting with this image too. PS : you can use image from http://ftp.debian.org/debian/dists/unstable/main/installer-sparc/ These are not the daily builds, are they? I used Jeff's because they seemed to be newer. They also boot without that devfs=mount option. regards, Reinhard -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Bug#237075: Bug not related to Sparc64... Maybe related to Creator?
On Fri, Mar 19, 2004 at 03:18:47PM +0100, Reinhard Tartler wrote: This image still has the problem with unable to open initial console so the option devfs=mount was needed. Not so in Jeff Bailey's build. bterm keeps on segfaulting with this image too. then you indeed found a bug in bterm Could test this : booting with devfs=mount init=/bin/sh options you will get a shell and then bterm -f unifont.bgf and maybe also bterm -f unifont.bgf -l C.UTF-8 you should get an error message. PS : you can use image from http://ftp.debian.org/debian/dists/unstable/main/installer-sparc/ These are not the daily builds, are they? I used Jeff's because they seemed to be newer. They also boot without that devfs=mount option. Jeff's images are newer because they are builded from daily cvs. Images in installer-sparc/ are builded when a new version of debian-installer (the debian package) is released. I was thinking that your bug was coming from a old version of libbog-dev on Jeff's system. But I was obviously wrong. I hope you will find the error ! Thanks. -- Thomas Poindessous -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Bug#237075: Bug not related to Sparc64... Maybe related to Creator?
On Fri, Mar 19, 2004 at 05:20:15PM +0100, Thomas Poindessous wrote: then you indeed found a bug in bterm Could test this : booting with devfs=mount init=/bin/sh options you will get a shell and then bterm -f unifont.bgf and maybe also bterm -f unifont.bgf -l C.UTF-8 you should get an error message. nope. The screen in the upper half gets messed up, long thin horizontal blue lines, and nothings happens. As soon as I press any key i get a segmentation fault. I tested this with Jeff's image but I don't think that this result will differ from beta3. Any other ideas I could try? regards, Reinhard -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Bug#237075: Bug not related to Sparc64... Maybe related to Creator?
On Fri, Mar 19, 2004 at 05:35:19PM +0100, Reinhard Tartler wrote: On Fri, Mar 19, 2004 at 05:20:15PM +0100, Thomas Poindessous wrote: nope. The screen in the upper half gets messed up, long thin horizontal blue lines, and nothings happens. As soon as I press any key i get a segmentation fault. I tested this with Jeff's image but I don't think that this result will differ from beta3. Any other ideas I could try? yes, can you test bterm with the unifont.bgf in your console on a running debian sparc system ? If it stills segfaults, it will be far more easier to debug it :) If you don't have the unifont.bgf (from cvs's building), I can send it to you. Many thanks ! -- Thomas Poindessous -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Bug#237075: Bug not related to Sparc64... Maybe related to Creator?
In article [EMAIL PROTECTED] [EMAIL PROTECTED] writes: Gunnar Wolf [EMAIL PROTECTED] wrote: I worked some time ago with an Ultra 10, the Creator board was an add-on, and when it was removed the base VGA port came back to life. Does the Ultra 1 also have this? Have you tried without the Creator? I'm not very familiar with sun hardware, but looking inside and at the board, I don't think that I can remove the Creator board. :( The creator is removable, but unless you have an sbus framebuffer there isn't much point. The ultra 1 does not have an onboard framebuffer. You can try using a serial console by disconnecting the keyboard and using serial port a. (Default 9600 baud.) -- Blars Blarson [EMAIL PROTECTED] http://www.blars.org/blars.html With Microsoft, failure is not an option. It is a standard feature. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#237075: Bug not related to Sparc64... Maybe related to Creator?
Gunnar Wolf [EMAIL PROTECTED] wrote: I worked some time ago with an Ultra 10, the Creator board was an add-on, and when it was removed the base VGA port came back to life. Does the Ultra 1 also have this? Have you tried without the Creator? I'm not very familiar with sun hardware, but looking inside and at the board, I don't think that I can remove the Creator board. :( regards, Reinhard -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#237075: Bug not related to Sparc64... Maybe related to Creator?
Hi, I just had a successful install on a Sparc64 today (already sent the report, but have not got the message back confirming the BTS number). Maybe it is caused by your specific framebuffer model (the Creator 3d)? I found at least another report of a successful install on a Sparc64 (227854), but its lspci shows it has a 'VGA compatible controller: ATI Technologies Inc 3D Rage I/II 215GT [Mach64 GT] (rev 9a)'. There is another failed report (220640) indicating display problems, it might be related. I worked some time ago with an Ultra 10, the Creator board was an add-on, and when it was removed the base VGA port came back to life. Does the Ultra 1 also have this? Have you tried without the Creator? Greetings, -- Gunnar Wolf - [EMAIL PROTECTED] - (+52-55)5630-9700 ext. 1366 PGP key 1024D/8BB527AF 2001-10-23 Fingerprint: 0C79 D2D1 2C4E 9CE4 5973 F800 D80E F35A 8BB5 27AF -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
