Yikes! Slink to Potato upgrade has nuked me.
Hello I tried to upgrade from slink to potato via apt and have crashed my system. I added the deb for potato to my apt/sources.list and did a update/upgrade. I got errors about glibc version. Now, I can't boot. ...err go multiuser. I can't even log in. How do I get out of this hole? John
RE: Keyboard/mouse problems with X
> > Did you install the kernel from potato, or did you use one > you compiled > yourself? I should warn you about woody though. The sparc > dist in woody > is not being kept up yet since I am still working out issues > with potato > before release, so you are venturing out on your own :) > Using these lines in sources.list... deb http://mirror.aarnet.edu.au/debian unstable main contrib non-free deb http://mirror.aarnet.edu.au/pub/linux/debian-non-US unstable/non-US main non-free Did 'apt-get -f install kernel-image-2.2.15-sun4cdm' which downloaded the package, but failed to install because of libc6-dev dependency issues (although I had already updated libc6 itself). Then did 'dpkg -i /var/cache/apt/archives/kernel-image-2.2.15-sun4cdm_2.2.15-0.19.4.deb' to install the kernel, rebooted and did the dist-upgrade. There was a little bit of stuffing around in there as well trying to get around the lic6-dev dependency problem but nothing terribly dramatic. I'm aware that running bleeding edge stuff sometimes hurts... but I just can't help myself 8^P Cheers Michael
Re: Keyboard/mouse problems with X
> > Any thoughts as to what may be causing this? > Damn, having a lot of X issues here lately :) Did you install the kernel from potato, or did you use one you compiled yourself? I should warn you about woody though. The sparc dist in woody is not being kept up yet since I am still working out issues with potato before release, so you are venturing out on your own :) Let me know about the kernel, and I'll see what I can come up with from there. -- ---===-=-==-=---==-=-- / Ben Collins -- ...on that fantastic voyage... -- Debian GNU/Linux \ ` [EMAIL PROTECTED] -- [EMAIL PROTECTED] -- [EMAIL PROTECTED] ' `---=--===-=-=-=-===-==---=--=---'
Re: Keyboard/mouse problems with X
Just a thought, I've noticed such behaviour when an X display manager (xdm, gdm, wdm, etc.) is installed, and you are using more than the default 6 virtual terminals. (X display manager tries to spawn on VT7 by default.) Did you happen to install a display manager when you upgraded? Regards, Steve Michael Anthon wrote: > Greetings, > I have an old Sparcstation IPC that I use as an X terminal sitting on my > desk here. It has been working fine for a while now (uptime was 96 days, > not bad for here considering it's not on a UPS) using a 2.0.36 kernel and I > think it was mostly potato based (could have been slink, it was so long ago > I have forgotten). > > Anyway, the 2.2.x kernel seemed to be getting a lot of good comments about > speed, so I installed that, then did a dist-upgrade to Woody ( I'm a > masochist, ok?). The upgrade seems to have gone pretty well, no major > faults to report in that process, however, now when I start X, the keyboard > and mouse stop working completely, even to the point where doing stop-a does > not work. Everything else seems to be ok, I can telnet/ssh in from > elsewhere and if I kill X off, I can redirect text to /dev/tty0 and it shows > up on screen. The only solution I have found that fixes the keyboard/mouse > it to do a shutdown and restart. > > Any thoughts as to what may be causing this? > > Cheers > Michael Anthon > > > > -- > To UNSUBSCRIBE, email to [EMAIL PROTECTED] > with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED] >
Keyboard/mouse problems with X
Greetings, I have an old Sparcstation IPC that I use as an X terminal sitting on my desk here. It has been working fine for a while now (uptime was 96 days, not bad for here considering it's not on a UPS) using a 2.0.36 kernel and I think it was mostly potato based (could have been slink, it was so long ago I have forgotten). Anyway, the 2.2.x kernel seemed to be getting a lot of good comments about speed, so I installed that, then did a dist-upgrade to Woody ( I'm a masochist, ok?). The upgrade seems to have gone pretty well, no major faults to report in that process, however, now when I start X, the keyboard and mouse stop working completely, even to the point where doing stop-a does not work. Everything else seems to be ok, I can telnet/ssh in from elsewhere and if I kill X off, I can redirect text to /dev/tty0 and it shows up on screen. The only solution I have found that fixes the keyboard/mouse it to do a shutdown and restart. Any thoughts as to what may be causing this? Cheers Michael Anthon
Re: Successful upgrade to potato, with work...
I'm glad to see things finally came around for you. Sorry that there were so many problems though. I'll try to resolve the libc6 issue with 2.0.x kernels. It appears that there are more people running this old thing than I had originally thought :) Most likely this close to release, I'll just add your (paraphrased) notes to the Release Notes for sparc. This should ease other users upgrades (sorry again that you had to be the one to do the trial and error :) Thanks for the report, Ben -- ---===-=-==-=---==-=-- / Ben Collins -- ...on that fantastic voyage... -- Debian GNU/Linux \ ` [EMAIL PROTECTED] -- [EMAIL PROTECTED] -- [EMAIL PROTECTED] ' `---=--===-=-=-=-===-==---=--=---'
Successful upgrade to potato, with work...
Greetings. The other day I posted a message decribing trouble my IPX
was having (primarily with ld.so) after an upgrade attempt from slink
to potato. After some effort, I've managed to successfully complete an
upgrade, and the machine appears to be functioning correctly. For
posterity, here is a summary of what initially failed and the steps I
took to make the upgrade successful:
Starting with a stock, "out of the box" Debian 2.1 installation from
CD ("standard" configuration, 2.0.x kernel), here is what *didn't*
work, using sound advice from the debian-user list:
1. 'apt-get update'; 'apt-get install apt': Dependency problem
with libc6 and the new apt version. Apt also told me I needed a
2.2.x kernel to install the new libc6 version.
Ok, forget upgrading apt...
2. 'apt-get update'; 'apt-get dist-upgrade': Incompatibility between
libc6 and the 2.0.x kernel. Ok, so I tried upgrading the kernel
to 2.2.x. Now I encountered a circular dependency; I couldn't
upgrade the kernel because I needed a new libc6, and I couldn't
upgrade libc6 because I needed a 2.2.x kernel. Sigh...
3. Reinstall Debian from CD, this time selecting the 2.2.1
kernel. Try the upgrade again. This time it works, only something
has gone wrong. The 'man' program produces an assertion failure
in ld.so; so does 'umount2' during reboot. Other related errors
while booting into runlevel 2. Removing ld.so.cache and running
ldconfig has no effect. Also, it looks like the 2.2.15 kernel
didn't get installed. Hmm...
Scratch head. Sigh again.
Here is what finally worked:
1. Reinstall Debian from CD, using the 2.2.1 kernel.
2. Explicitly upgrade to just the 2.2.15 kernel, nothing
else. Remote logins now fail due to insufficient PTYs. Saw this
in the list archives, but my system didn't have
/etc/init.d/devpts.sh (which cures the problem). So... upgraded
the sysutils and netbase packages from potato. One of these
contained the needed script, which solved the PTY problem. I now
have a functioning 2.2.15 system...
3. NOW: 'apt-get update'; 'apt-get dist-upgrade' to get potato
installed. This *works*; no ld.so problems.
4. Install some additional packages for nfs, telnetd. Goes fairly
ok, but now rsh, rlogin, rlogind are missing. Sigh. Install
rsh-client and rsh-server packages. Ok.
5. Reboot.
6. Up and humming.
I hope these notes prove useful to someone. Thanks to those on the
list that provided the APT steps to use when upgrading. FYI, my potato
installation is running on a SPARC IPX, 64mb ram:
[EMAIL PROTECTED]:/etc/init.d$ cat /proc/cpuinfo
cpu : Fujitsu or Weitek Power-UP
fpu : Fujitsu or Weitek on-chip FPU
promlib : Version 2 Revision 2
prom: 2.9
type: sun4c
ncpus probed: 1
ncpus active: 1
BogoMips: 39.83
vacsize : 65536 bytes
vachwflush : yes
vaclinesize : 32 bytes
mmuctxs : 8
mmupsegs: 256
kernelpsegs : 34
kfreepsegs : 0
usedpsegs : 53
ufreepsegs : 132
user_taken : 2
max_taken : 146
Regards,
--
-
David E. Young
Fujitsu Network Communications "The fact that ... we still
([EMAIL PROTECTED]) live well cannot ease the pain of
feeling that we no longer live nobly."
-- John Updike
"Programming should be fun,
programs should be beautiful"
-- P. Graham
Re: Ultra 5 "reproducible" XF86_Mach64 lockups
Ben Collins <[EMAIL PROTECTED]> writes: > Interesting. That source is working fine here on a U5 and a U10 class > system. What all are you running under X? What, if anything, are you > running on the system besides X related programs? The system was basically idle (nothing special apart from X server). Moreover, in order to diagnose the problem I've tried to run as little stuff as possible. The freezing happened with: fvwm + gnome-terminal (only terminal; not the full GNOME) + emacs + xdvi. I haven't tried to narrow it further. BTW I've seen also a minor unreproducible display problem with current XF86_Mach64 (trash displayed here and there on the screen; no lockup). Perhaps it would be interesting to build the new X11 and test it. Hein Roehrig <[EMAIL PROTECTED]> writes: > Just FYI, I can reproduce the problem here as well (almost same > setup, but stock 2.2.15). Now this gets really interesting! :) cheers -- TS
Re: Ultra 5 "reproducible" XF86_Mach64 lockups
It may not be the same problem, but I've recently seen XF86_Mach64 lock up using all the CPU when I do a rubber-banding operation in a Motif application running remotely. I'm using a self-built but vanilla 2.2.14 kernel. For what it's worth, it doesn't happen on an RH 5.2 x86 box with an S3 driver. I haven't time to investigate at the moment.
Re: Ultra 5 "reproducible" XF86_Mach64 lockups
Just FYI, I can reproduce the problem here as well (almost same setup, but stock 2.2.15). -Hein
Re: Ultra 5 "reproducible" XF86_Mach64 lockups
On Thu, May 18, 2000 at 02:41:02PM +0200, Tibor Simko wrote: > Ben Collins <[EMAIL PROTECTED]> writes: > > > Are you using the 2.2.15 kernel from potato, or one you compiled > > yourself from stock 2.2.15 source? > > The native potato one (2.2.15-0.19.4, from kernel-image-2.2.15-sun4u). Interesting. That source is working fine here on a U5 and a U10 class system. What all are you running under X? What, if anything, are you running on the system besides X related programs? Ben -- ---===-=-==-=---==-=-- / Ben Collins -- ...on that fantastic voyage... -- Debian GNU/Linux \ ` [EMAIL PROTECTED] -- [EMAIL PROTECTED] -- [EMAIL PROTECTED] ' `---=--===-=-=-=-===-==---=--=---'
Re: Ultra 5 "reproducible" XF86_Mach64 lockups
Ben Collins <[EMAIL PROTECTED]> writes: > Are you using the 2.2.15 kernel from potato, or one you compiled > yourself from stock 2.2.15 source? The native potato one (2.2.15-0.19.4, from kernel-image-2.2.15-sun4u). cheers -- TS
unsuscribe
Cordialement(Best) Kazem Bakhshesh E-Mail : [EMAIL PROTECTED] Tel: 01.41.79.56.47 Fax: 01.41.79.56.10 Charenton Conflans
Re: Ultra 5 "reproducible" XF86_Mach64 lockups
On Thu, May 18, 2000 at 01:00:33PM +0200, Tibor Simko wrote: > Hello > > I obtain repetitive lockups of Ultra 5 under X11, Sun Type 5 keyboard; > kernel 2.2.15, synced with current potato. Are you using the 2.2.15 kernel from potato, or one you compiled yourself from stock 2.2.15 source? If the latter, then you may want to check the patches I have from Dave Miller in the kernel-image-2.2.15-sparc source package (apt-get source kernel-image-2.2.15-sparc). I haven't actually tried a stock 2.2.15 kernel on my U5, so I don't know that this is the problem, but it works fine with the patch. Ben -- ---===-=-==-=---==-=-- / Ben Collins -- ...on that fantastic voyage... -- Debian GNU/Linux \ ` [EMAIL PROTECTED] -- [EMAIL PROTECTED] -- [EMAIL PROTECTED] ' `---=--===-=-=-=-===-==---=--=---'
Ultra 5 "reproducible" XF86_Mach64 lockups
Hello I obtain repetitive lockups of Ultra 5 under X11, Sun Type 5 keyboard; kernel 2.2.15, synced with current potato. The lockup typically occurs within 1 minute of intensive X input. To "reproduce" it I use xdvi and emacs and rapidly click with mouse here and there, change scales, skip through pages, reread file, etc. The lockup happens independently of the window manager (tested E, sawmill, fvwm). When the lockup happens both the mouse and keyboard are unusable. Machine respond to network connections and top shows that XF86_Mach64 is working hard. But I have not succeeded to kill X, nor to reboot over the network connection: after such attempts the connection itself is frozen. The only apparent solution is to cut the power off. I wonder whether anyone observes the same thing. What is the best method for further diagnosis? cheers -- TS
