Re: SILO and Create Boot Floppy Fails.
On Wed, Mar 26, 2003 at 01:14:44PM -0500, Andrew Bolyea wrote: I am attempting to resurrect an old SpacStation10... I booted the machine using a rescue floppy, and proceeded with at net install of the Debian base system. Everything seemed to work perfectly right up until the last step. SILO wasn't able to install. ...but no indication of why? Any ideas? so I tried to create a boot floppy. Creation of boot floppy failed. I tried 3 different floppies to no avail. so I checked tty3: formatting floppy with cmd 'export LD_LIBRARY_PATH=/target/lib: /target/usr/lib; /target/usr/bin/superformat /dev/fd0 hd umount /dev/fd0: No such file or directory umount /floppy: Invalid argument So now I can't boot from SILO or a custom boot floppy... does anyone have any ideas as to what I can do next? Any help would be greatly appreciated. Thank you, Andrew. I had the same problem some months ago with my SS5 and, iirc, it was because when partitioning the disk, I had deleted the ?Sun Disk Label?, the partition #3 that encompasses the whole disk. hth Mike Y. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED] -- I heartily accept the motto - 'That government is best which governs least;' and I should like to see it acted up to more rapidly and systematically. Carried out it finally amounts to this, which I also believe - 'That government is best which governs not at all;' and when men are prepared for it, that will be the kind of government which they will have. -- Henry David Thoreau myehle at wanadoo dot fr
Re: Two problems
On Thu, Mar 27, 2003 at 04:38:41PM +1100, Conrad Canterford wrote: First, sound: I am getting sound under X for root, but not for my userid. Following what I read on this list, I added my userid to the audio group and checked that /dev/dsp had rw permissions for that group and was owned that group. This doesn't appear to have made any difference (and yes, I restarted X and the associated other stuff). Its probably something really obvious, but I don't know what Suppose you type 'id $username'. Do you see the audio group listed? You will have to log out and log in again for your processes to be granted that identity. It's not instantaneous. Second, X crashes: My X dies all to frequently with a Received Signal 11 (or words to that effect) message. Very occasionally it is a Signal 10 instead. There does not appear to be any consistency that I can identify, other than that most of the time its while I'm not at that computer. I have a CG6 framebuffer and 192M RAM in it at the moment, but it was also doing something very similar or the same (I don't remember exactly) while I had the CG3 framebuffer and only 64M RAM in it. My attempts to identify a cause have so far drawn a blank. Has anyone any ideas (or better yet, a solution)? Please? This makes that machine somewhat less useful than I has hoping. Eh, this is a difficult problem to place. It is almost certainly a hardware problem. The canonical hardware test is to compile a kernel from source. If you get SEGVs doing that, then look for a CPU or RAM problem, or some environmental problem causing them (like heat, X-rays, or poultergeists). If compiling doesn't tickle problems, then it might be the X server, but that's pretty unlikely, IMO. - chad pgpnoHInO1HF2.pgp Description: PGP signature
Re: SILO and Create Boot Floppy Fails.
On Wed, Mar 26, 2003 at 05:55:40PM -0500, Andrew Bolyea wrote: [ please don't top post ] I have a small /boot partition (/dev/sda1) consisting of the first 10M of sda. /boot /dev/sda1 /usr /dev/sda2 / /dev/sdb1 swap /dev/sdb2 Currently silo.conf is pointing to root=/dev/sdb1 Which is correct. And there is link to vmlinuz in that dir. Should I change it to the /boot partition? Despite its name, SILO does not work like LILO. It works much more like GRUB on i386. That is, SILO expects its config file to be readable at boot time. So ... if you use a /boot partition, you have to move the SILO config file there. This means you'll end up with a directory in /boot named etc which contains the file silo.conf . You can then symlink /etc/silo.conf to /boot/etc/silo.conf so that you can edit SILO config without thinking too hard :-) Your silo.conf should look something like this: partition=1 timeout=50 image=1/vmlinuz-2.4.18-sun4cdm label=linux root=/dev/sdb1 read-only What's a bit confusing here is that the kernel filename is _relative_ to the filesystem named by the partition argument; IOW even though /dev/sda1 is eventually mounted as /boot by linux, SILO does not know that. As a side effect, the kernel sumlinks in the root filesystem /dev/sdb1 are superfluous. To install SILO, you'll have to use the '-r' flag as follows: # silo -r /boot BTW, I am sure that the reason SILO wouldn't install automatically is because your root is on /dev/sdb. Doesn't something need to be written to the MBR inorder for the system to boot using SILO? Well, the way I understand it, there is no MBR on a sparc. OpenBoot knows how to do the right thing (that is; if you have the whole disk partition on partition 3, as someone else noted. fdisk can set this up for you if you choose to install a new Sun disklabel, option 's'). Do I need to change something in OpenBoot? What does printenv boot-device at an OpenBoot prompt say? If this is an SS5 or friends they swap device 0 and 3 for some reason. I mention this because you have two drives and this can end up violating the principle of least surprise. Right now everytime I boot the machine it puts me to the ok prompt. I belive this is OpenBoot? Then I insert the Debian Rescue Floppy and boot from it. ok boot floppy Then I use the boot option... boot: linux root=/dev/sdb1 Which correctly boots the machine (I believe using the kernel on the hard dirve, not the floppy?) No, you're using the kernel on the floppy. Sorry for all the questions... I am familiar with Debian on i386. This is my first time installing Debian on a sparc. It's a little different, but I think you'll enjoy it! -- Nathan Norman - Incanus Networking mailto:[EMAIL PROTECTED] It doesn't matter what you are doing, emacs is always overkill. -- Stephen J. Carpenter
Error with nfs-root install
Hi all, I've gotten a bit further with installing debian. It looked like the last install I did hadn't completed like I thought it had. I tried again but now I get a different error. To recap, this is a sparc classic with no disk/floppy/cdrom. It's nfs-root, installed over the internet. This is the error I get: x Failure trying to run: chroot /target dpkg --force-depends x x --install x x /var/cache/apt/archives/base-files_3.0.2_sparc.deb x x /var/cache/apt/archives/base-passwd_3.4.1_sparc.deb x And then: x debootstrap exited with an error (return value 1) x /target/tmp/debootstrap.log contains a single line: dpkg: unable to lock dpkg status database: No locks available Can anyone provide any help? Cheers, Bob -- Bob Ham [EMAIL PROTECTED]
Re: sungem
On Thu, Mar 27, 2003 at 11:51:27AM -0800, [EMAIL PROTECTED] wrote: Hello, Debian woody on a dual ultrasparc. I have a 1000b-sx Gb ethernet card. I have re-compiled the kernel and have the sungem as a loadable module. It loads fine and I can assign an IP address. This is hooked up to a cisco catalyst 4000. I can move traffic around for about 45 seconds then it dies for 2 minutes, it comes back traffic goes for another 45 seconds and then dies again. I have tried the different link modes and all of them have the same issue. I have tried different cables same problem. different Gbics in the cisco, same problem. Has anybody else had these problems? Anybody have a solution or any ideas on what I could try to get this working? Tried different IP's? Sounds to me like you are getting some ARP corruption. -- Debian - http://www.debian.org/ Linux 1394 - http://www.linux1394.org/ Subversion - http://subversion.tigris.org/ Deqo - http://www.deqo.com/
