Re: initrd testing
On Thu, 13 May 2004, Joshua Kwan wrote: [ Sorry for the huge crosspost, but this is a pretty big deal. ] On Thu, May 13, 2004 at 04:21:46PM -0400, Ben Collins wrote: Some people have reported problems with initrd on sparc64. I'm trying to trace that problem (hard, because I can't reproduce it). If you've had the problem where silo reports loading the initrd into memory, but the kernel fails to detect and use it, please try the second.b in the url below, and recompile a kernel using one of the two patches there aswell (2.4 and 2.6). The new second.b will show the phys address that the initrd was loaded to, in addition to the virtual address. I've built debian-installer images for sparc based on kernels with this patch (for 2.4) and the new second.b. You probably want the CDROM image since it's the one most commonly reported as not being able to boot. (cdrom-mini.iso) I am personally not able to try these out until I receive a sparc64 machine, which should happen sometime in the near future. http://june.voxel.net/~joshk/d-i/images/2004-05-14/ I tried http://june.voxel.net/~joshk/d-i/images/2004-05-14/drom-mini.iso on two machines, an Ultra1 and an Ultra10; both failed, though differently. Ultra1: On this one, I got (modulo any typos) Loading initial ramdisk (1477684 bytes at 0x01x phys 022340800 virt) ... [spinning \/] Remapping the kernel ... FP Disabled ok and I was back to the OpenBoot 'ok' prompt. Ultra10: On this one, I got much further. The kernel was loading, but failed near the end. The last messages were RAMDISK: couldn't find valid ramdisk image starting at 0. Freeing initrd memory 1443k freed cramfs: wrong magic sh-2021: reiserfs_read_super: can not find reiserfs on ramdisk (1,0) Kernel panic: VFS: Unable to mount root fs on 00:00 I hope this means something to somebody. -- Andy Dougherty [EMAIL PROTECTED]
Re: initrd testing
On Fri, 14 May 2004, Ben Collins wrote: AD Ultra10: On this one, I got much further. The kernel was loading, AD but failed near the end. The last messages were AD AD RAMDISK: couldn't find valid ramdisk image starting at 0. AD Freeing initrd memory 1443k freed AD cramfs: wrong magic AD sh-2021: reiserfs_read_super: can not find reiserfs on ramdisk (1,0) AD Kernel panic: VFS: Unable to mount root fs on 00:00 This means something. Atleast we are showing a ramdisk, but the start point is all wrong. Did the old cd images work for you? I'm afraid I haven't been keeping up. The last CD boot I did was the woody install. I can try (a small number) of other images, if you have any specific suggestions. -- Andy Dougherty [EMAIL PROTECTED]
/lib64/libc.so.6: unexpected reloc type 0x08
I am currently running the testing distribution on an Ultra 10.
A trivial compilation produces the following error message:
echo 'int main(void) { return 0; }' x.c gcc -o x x.c ./x
./x: error while loading shared libraries: /lib64/libc.so.6: unexpected
reloc type 0x08
The relevant packages are:
Package: gcc
Version: 4:3.3.1-2
(though gcc itself reports gcc version 3.3.2 (Debian))
Package: libc6-sparc64
Version: 2.3.2.ds1-10
I know how to work around the problem with the sparc32 command or
with the -m32 option to gcc, and those are fine as temporary
workarounds, but is there something wrong with my setup?
If others are seeing this, does anyone know what the error message
means and how to go about fixing it?
Thanks,
Andy Dougherty [EMAIL PROTECTED]
Re: fdisk on sunos
On Tue, 19 Jun 2001, Ari Heitner wrote: Hmm, Linux's fdisk can handle things just fine, if you're willing to kill some Sun slices to make room for Linux. This seems to be the logical thing to do: copy the data from a slice or two to somewhere else, change Solaris's mounting rules not to mount the now-unecessary partitions (cursory examination of this machine seems to indicate this is in /etc/mnttab, and yes 'mnttab' is a man topic), and then later in the Linux install retag them as ext2 and mkfs them... For Solaris, you want to change /etc/vfstab. /etc/mnttab is a dynamic file maintained by Solaris to show what's actually mounted. You shouldn't change it yourself. -- Andy Dougherty [EMAIL PROTECTED] Dept. of Physics Lafayette College, Easton PA 18042
Re: deb-sparc X and other questions
On Fri, 2 Mar 2001 [EMAIL PROTECTED] wrote: 1) What's the general state of the debian-sparc port (from a day to day usage viewpoint, rather than a feature-list viewpoint). I'm trying to decide what OS to run on my SS20, between debian, OpenBSD, and Solaris.. Basically, I want to run a bunch of xterms and a browser (konquerer, mozilla, whichever). My experience has been that it's about as good as any other Debian GNU/Linux port. I have occasionally encountered some i386-centric things, (e.g. some packages expect you're using X86FConfig, but the Xsun server (in the 3.x packages) doesn't need it.) Generally, however, it works quite well. One thing to be aware of, however, is that third-party products may be available only for the i386 port, not for the sparc port. For example, if your work requires Adobe Acrobat Reader, you'll find it's available for Solaris/SPARC, Solaris/x86, and Linux/i386, but not for Linux/SPARC. You should check out the applications you'll need and determine what operating system they'll run under. -- Andy Dougherty [EMAIL PROTECTED] Dept. of Physics Lafayette College, Easton PA 18042
Re: printing on sparc
On Fri, 19 Jan 2001, Gabor Zoltan Csejtey wrote: I have some news. After sending some text to the printer (DEskJet 720C) the sun halted but then I unplugged the printer cable from the sun it came alive again. So it seems a hardware problem ? Is there a similar printer port on the Ultra 10? It looks similar to the PC's. Just for reference, I just had success with an old Apple LaserWriter (Postscript) on the parallel port on an Ultra 1 running 2.2.17. (This printer probably doesn't tax the bi-directional capabilities of the port very much, however:-). Had I a nice DeskJet around, I'd try that, but there are none around. Here's what I did. I don't know if all these are necessary, but life is short so I haven't tried all exhaustive combinations. MAKEDEV lp MAKEDEV parport And then in /etc/modules I added bpp parport After that, /dev/lp0 worked. -- Andy Dougherty [EMAIL PROTECTED] Dept. of Physics Lafayette College, Easton PA 18042
IP-Config: Not enough information
I'm running woody on an Ultra 1. During boot, I get the message IP-Config: Not enough information The message is coming from the kernel net/ipv4/ipconfig.c, but I don't know what information it doesn't have or how to supply it. I'm running kernel-image-2.2.17-sun4u. I just upgraded to the latest glibc 2.1.94-3 along with all the other stuff dselect suggested. The system had been working fine until then. Now, all NFS-related stuff doesn't work any more -- I get portmap: server localhost not responding, timed out I'd file a bug, but I'm not sure which package to file it against. I suspect one of the upgrades (maybe netbase?) may have left the network files in an incomplete configuration, but after two days of poking around on my own, I haven't found it yet. Any suggestions would be welcome. -- Andy Dougherty [EMAIL PROTECTED] Dept. of Physics Lafayette College, Easton PA 18042
Re: ypbind failure
On Thu, 12 Oct 2000 [EMAIL PROTECTED] wrote: Hi! I ran into some nasty problem this morning.. I did a apt-get dist-upgrade on my woody installation. Now ypbind is unable to talk to our NIS server. I'm running into what is probably a related problem (though I don't run NIS). At boot time, I'm getting the message: portmap: server localhost not responding, timed out Lots of stuff doesn't work after that, obviously. -- Andy Dougherty [EMAIL PROTECTED] Dept. of Physics Lafayette College, Easton PA 18042
Re: Weird working of X
On Tue, 19 Sep 2000, Ben Collins wrote: On Tue, Sep 19, 2000 at 02:14:13PM +0200, Ottavio Campana wrote: I'm using windowmaker on my ss10 with a cg6 framebuffer. I've noted a You seem to only be supporting 256 colors. [good explanation of palette shift omitted] palette, but it'll avoid the palette shift. However, since I've always had atleast 16bits (65k colors) when I use X, I'm not sure what the configuration is to change it (maybe email debian-x, if someone here doesn't know). I'm pretty sure the 256-color limit is a cg6 Sun hardware limit and there's nothing you can do to change it. (Certainly our Solaris 8 installations using the cg6 also only have 256 colors.) -- Andy Dougherty [EMAIL PROTECTED] Dept. of Physics Lafayette College, Easton PA 18042
