Re: Golded+ on Sparc64
Same problem here. I've submitted a bugreport. Daniel van Eeden [EMAIL PROTECTED] On Mon, 2004-05-24 at 16:46, Peter Karlsson wrote: Cc'ing Debian-Sparc. Full quote of original message: When I launch golded on my Sparc I get Bus error. I tried to recompile it by my own, but got the same. I use up to date Debian/Sid with kernel 2.4.26 cat /proc/cpuinfo cpu : TI UltraSparc IIi (Sabre) fpu : UltraSparc IIi integrated FPU promlib : Version 3 Revision 19 prom: 3.19.4 type: sun4u ncpus probed: 1 ncpus active: 1 Cpu0Bogo: 665.19 Cpu0ClkTck : 13d92d40 MMU Type: Spitfire Can you help? Do you need some more info? I haven't really tried running it on anything but i386 (I don't remember if I ever ran it on m68k, but I do remember it taking ages to compile). I would think it is an endian problem or similar, the program was originally an MS-DOS applictaion, and both 32-bit support and Linux ports were added later on, and it may very well be that the code assumes something to behave just like i386 does. Hopefully, someone on Debian-Sparc could help. Please Cc me on replies, I'm not on the list. -- \\// Peter - http://www.softwolves.pp.se/ I do not read or respond to mail with HTML attachments. -- Daniel van Eeden [EMAIL PROTECTED] http://compukid.no-ip.org/ jabber: [EMAIL PROTECTED] aim: Compukid128 icq: 36952189
Re: Keyboard-Problems with kernel 2.6 and my Ultra60 solved
On Mon, May 24, 2004 at 08:40:54AM +0200, Joerg Friedrich wrote: some weeks ago I reported a problem with my keyboard (and mouse) not working with kernel = 2.6.5 on my Ultra60. After searching a lot and even more kernel building I know now that is absolutly neccessary to set CONFIG_SERIAL_SUNSU=y The sun keyboard connection a serial one and the the su driver is needed to use it. Additionally I had to tell console-data to keep the kernels keymap. every other setting leads to an unusable keyboard. Hmm, thanks for this info! It solves exactly my problem I posted a few days ago! Christian
Re: Keyboard-Problems with kernel 2.6 and my Ultra60 solved
On Mon, 24 May 2004, Joerg Friedrich wrote: Hi, some weeks ago I reported a problem with my keyboard (and mouse) not working with kernel = 2.6.5 on my Ultra60. After searching a lot and even more kernel building I know now that is absolutly neccessary to set CONFIG_SERIAL_SUNSU=y The sun keyboard connection a serial one and the the su driver is needed to use it. Additionally I had to tell console-data to keep the kernels keymap. every other setting leads to an unusable keyboard. I'm not sure if this is related, but I just installed Debian Woody on my Ultra1. I've since did a apt-get dist-upgrade and everything seems to work, except for the keyboard in X. The Sun keyboard works fine on the console, but as soon as I startx, the keyboard stops working. I've searched on google for some XF86Config files, and my XF86Config file looks similar to those posted. Has any one run into this issue before as well? Thanks for any tips. -- Jiann-Ming Su [EMAIL PROTECTED] Network Communications, Emory University
Upgraded to testing, now xserver freezes
Ok, I successfully had stable running on my Ultra 5 with no problems for a few months. But I was a bit disappointed with the age of some of the apps, so deciding between backports and going to testing, I chose the latter route. So following the instructions at http://www.debian.org/doc/manuals/reference/ch-woody.en.html I proceeded, having to (re)issue apt-get -f install several times when the upgrade would stop with some error, and then (re)issue apt-get -t testing dist-upgrade... etc. Anyway, after some time and several cycles through this process, I the upgrade ended with no reported errors... great!! However, now.. after startx, I get the gray thatch screen and I can see my mouse (which responds to mouse movements) but thats it... the window manager never comes up (before the KDE window showing whats being loaded would come up at this point, but no more). if I ssh in, i see the following processes: So anyway, if anyone can point me in the right direction to troubleshoot this I'd be grateful :) Joubin
Re: Upgraded to testing, now xserver freezes
On Tue, May 25, 2004 at 04:40:35PM -0700, Joubin Moshrefzadeh wrote: Ok, I successfully had stable running on my Ultra 5 with no problems for a few months. But I was a bit disappointed with the age of some of the apps, so deciding between backports and going to testing, I chose the latter route. So following the instructions at http://www.debian.org/doc/manuals/reference/ch-woody.en.html I proceeded, having to (re)issue apt-get -f install several times when the upgrade would stop with some error, and then (re)issue apt-get -t testing dist-upgrade... etc. Anyway, after some time and several cycles through this process, I the upgrade ended with no reported errors... great!! This process is usually easier if you don't install anything beforehand.. :-) However, now.. after startx, I get the gray thatch screen and I can see my mouse (which responds to mouse movements) but thats it... the window manager never comes up (before the KDE window showing whats being loaded would come up at this point, but no more). if I ssh in, i see the following processes: what processes? If your mouse is moving, then this sounds like a KDE problem, and not an X problem. Check your ~/.xsession-errors, and try installing some other windowmanager(apt-cache showpkg x-window-manger) and see how that works. -- -Justin
xserver hangs after upgrade to testing
Ok, I successfully had stable running on my Ultra 5 with no problems for a few months. But I was a bit disappointed with the age of some of the apps, so deciding between backports and going to testing, I chose the latter route. So following the instructions at http://www.debian.org/doc/manuals/reference/ch-woody.en.html I proceeded, having to (re)issue apt-get -f install several times when the upgrade would stop with some error, and then (re)issue apt-get -t testing dist-upgrade... etc. Anyway, after some time and several cycles through this process, I the upgrade ended with no reported errors... great!! However, now.. after startx, I get the gray thatch screen and I can see my mouse (which responds to mouse movements) but thats it... the window manager never comes up (before the KDE window showing whats being loaded would come up at this point, but no more). if I ssh in, i see the following processes: So anyway, if anyone can point me in the right direction to troubleshoot this I'd be grateful :) Joubin
Online meds without having to wait in line QmJiYM2YV5GLHVo9fzZN
We are providing an online solution to finding and receiving prescription medications from the comfort of your own home, you will be able to save money, save time, save yourself from worry, and most of all, save your life! %RND_AD_2 Plus: %RND_ALL_OTHER_MEDS We don't require any prescriptions. No waiting rooms. Here.. Use Microsoft Internet Explorer to view the following website: www.%RND_HOST. Please copy and paste the URL on your browser's address field. %RND_PHRASE %RND_PHRASE %RND_PHRASE %RND_PHRASE
