Re: Booting Debian from floppies on UltraSparc.
Last I knew, when I tried to install the first time on my Ultra 1 about 6 mos ago, and from what I have heard, you cannot install from a floppy. There is a problem booting Ultra machines off of a floppy. I would recomend waiting for the ISO's and doing it that way. It is a much easier way than the alternatives I know of (tftpboot :( )Chris B [EMAIL PROTECTED] wrote: > I am trying to install the current frozen distribution, but I wouldn't > mind even older one (assuming dselect and apt-get would work after > that). Just to start. I am downloading ISO images right now, but > tomorrow morning PDT, I would like to start installation. If I could > make it from floppies, I would be happier, though. I know that Red Hat > is bootable there, but it was from a CD (that's why am I downloading ISO > images - I wouldn't otherwise). > > When I press Stop-A and after I get ok prompt, I can test floppy > which shows it's there and successfuly readable. "boot floppy" doesn't > work, though. The error message says "Can't open disk label package" and > something about "bad magic number". > > I tried to find help on > http://www.debian.org/releases/frozen/sparc/install.en.txt, but that > document isn't very useful. > > Any help would be greatly appreciated. > > Peter. > > P.S.: I even tried today version of bootfloppies. > > -- > To UNSUBSCRIBE, email to [EMAIL PROTECTED] > with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Booting Debian from floppies on UltraSparc.
I am trying to install the current frozen distribution, but I wouldn't mind even older one (assuming dselect and apt-get would work after that). Just to start. I am downloading ISO images right now, but tomorrow morning PDT, I would like to start installation. If I could make it from floppies, I would be happier, though. I know that Red Hat is bootable there, but it was from a CD (that's why am I downloading ISO images - I wouldn't otherwise). When I press Stop-A and after I get ok prompt, I can test floppy which shows it's there and successfuly readable. "boot floppy" doesn't work, though. The error message says "Can't open disk label package" and something about "bad magic number". I tried to find help on http://www.debian.org/releases/frozen/sparc/install.en.txt, but that document isn't very useful. Any help would be greatly appreciated. Peter. P.S.: I even tried today version of bootfloppies.
Re: Unable to compile; sys/io.h not found (fwd)
On Wed, Jun 07, Stephen R. Gore wrote: > I found it in /usr/include/asm/io.h on sparc. Not sure if this is a bug, > or really necessary. There needs to at least be a link from > /usr/include/sys/io.h for most builds to find the header. sys/io.h does not exist on SPARC. And you don't need it. You even cannot use it, because it is not supported by the SPARC hardware. You don't have IO ports. If you have a program which depends on it, you need to rewrite it for a SPARC port. Linking asm/io.h to sys/io.h does not help, because the program will not compile with it. Thorsten -- Thorsten Kukuk http://www.suse.de/~kukuk/ [EMAIL PROTECTED] SuSE GmbHSchanzaeckerstr. 1090443 Nuernberg Linux is like a Vorlon. It is incredibly powerful, gives terse, cryptic answers and has a lot of things going on in the background.
Re: Unable to compile; sys/io.h not found (fwd)
I found it in /usr/include/asm/io.h on sparc. Not sure if this is a bug, or really necessary. There needs to at least be a link from /usr/include/sys/io.h for most builds to find the header. Regards, Steve [EMAIL PROTECTED] wrote: > > I'm going to be recompiling libc6 as a verification pass. The powertweak > people are saying we should have a sys/io.h, but it looks like it's > something specific to arches that use ISA. > > > -- Forwarded message -- > Date: Tue, 06 Jun 2000 17:28:18 -0700 > From: Sudhakar Chandra <[EMAIL PROTECTED]> > To: [EMAIL PROTECTED] > Subject: Re: Unable to compile; sys/io.h not found > > Dave Jones proclaimed: > > > > [EMAIL PROTECTED] <[EMAIL PROTECTED]> wrote: > > > > > My system doesn't seem to have a sys/io.h under /usr/include. > > > > Then it would appear to be borken. > > > > > I'm running Debian potato prerelease. Kernel 2.2.15, libc6 2.1.3, with > > > standard libc headers. > > > > Looks like a debian-specific problem. Thaths?, Anyone ? > > If you've got the devel stuff installed, then it maybe that the > > packager screwed up, and missed a file ? > > > > See if you sys/io.h is listed in /var/lib/dpkg/info/libc6-dev.list > > It is is not, then the package maintainer messed up. If it is, your system > has somehoe landed in an inconsistent state. Download the libc6-dev deb > again and reinstall it. Before reinstalling it do a 'dpkg --contents > libc6-dev*.deb | more' to see if sys/io.h is part of the package that you > downloaded. > > S. > -- > "Now, let's all turn around and pay attention to me again." > -- Homer J. Simpson > Sudhakar C13nhttp://www.aunet.org/thaths/Lead Indentured Slave > > > -- > To UNSUBSCRIBE, email to [EMAIL PROTECTED] > with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED] >
Sparc ELC w limited resources - trouble installing
Hi, I have a working ELC, after replacing the NVRAM... it did boot SunOS 4 last time I tried. I'm having some trouble figuring out the (best) way to install Linux on this machine. I've studied the available install doc from Debian, UltraSparc and RedHat to no total enlightenment. I've tried several methods to not much success so far. Configuration: 12 MB RAM Ethernet and a fully functional 2.2.15 PII connected (rarp and tftp set up and working) 650 MB Hard disk I can either use on the PII Linux box or the ELC. I thought that should do it - but not much luck. My equipment precludes me from using either CD or Floppy, apparently the preferred install media. That together with little RAM seems to block the more treaden paths (rescue disks etc.). TFTP: I know my memory is a little tight and none of the tftp boots have ever worked. Should they have? One thing I noticed that my machine always seems to hang after the load unless I pad the file to a multiple of a block size. That might be worth noting or even add to the scripts for producing these thingies we tftp over. The doc on 'low memory TFTP install' is a complete mystery to me - see NFS questions below. NFS: I also tried to boot with an NFS root, but the the kernel never managed to mount it: "cant mount root on 00:00\nPress L1 A to reboot". The docs are not clear what the correct syntax is for an NFS mounted root... that shouldn't be hard to add. I tried root=/dev/nfs nfsroot=192.168.100.100:/the/root/path Obviously that depends on the kernel to have support built in for it, but how can I tell if the .config isn't provided with the kernel? (Debian linux-2.2.1.a.out or so) HD: I managed to partition and setup the HD with the base2_1.tar.gz content. That booted great, but simply told me to stick in the boot floppy, then confiure the system. Stuck. Why is it so hard to set up a minimal system from Linux box of a different architecture I don't understand. If left to my own resources, I'll try the same stuff again with a newer potato install kit I've learned about on the list today. I'll also try to abuse my swap partition on the HD as a 'root'. That should be feasible for Debian, but RedHat wanted all their RPMS in there, taking too much space. Am I missing something important? Bonus question: Also, I can't claim I've fully understood the full detailed mechanics of an installation. Wha'ts the main thing to kick off after a minimal RAM or disk based system is up and running and why can't it be on the same partition as the system being installed? Your help is very much appreciated... Martin
Re: Unable to compile; sys/io.h not found (fwd)
I'm going to be recompiling libc6 as a verification pass. The powertweak people are saying we should have a sys/io.h, but it looks like it's something specific to arches that use ISA. -- Forwarded message -- Date: Tue, 06 Jun 2000 17:28:18 -0700 From: Sudhakar Chandra <[EMAIL PROTECTED]> To: [EMAIL PROTECTED] Subject: Re: Unable to compile; sys/io.h not found Dave Jones proclaimed: > > [EMAIL PROTECTED] <[EMAIL PROTECTED]> wrote: > > > My system doesn't seem to have a sys/io.h under /usr/include. > > Then it would appear to be borken. > > > I'm running Debian potato prerelease. Kernel 2.2.15, libc6 2.1.3, with > > standard libc headers. > > Looks like a debian-specific problem. Thaths?, Anyone ? > If you've got the devel stuff installed, then it maybe that the > packager screwed up, and missed a file ? See if you sys/io.h is listed in /var/lib/dpkg/info/libc6-dev.list It is is not, then the package maintainer messed up. If it is, your system has somehoe landed in an inconsistent state. Download the libc6-dev deb again and reinstall it. Before reinstalling it do a 'dpkg --contents libc6-dev*.deb | more' to see if sys/io.h is part of the package that you downloaded. S. -- "Now, let's all turn around and pay attention to me again." -- Homer J. Simpson Sudhakar C13nhttp://www.aunet.org/thaths/Lead Indentured Slave
Re: Serial PCI ports
> > > > PCIO serial driver version 1.18.2.6 > > > > su(serial) at 0xf9fff13803f8 (tty 0 irq 6,7dc) is a 16550A > > > > su(serial) at 0xf9fff13602f8 (tty 1 irq 6,7d4) is a 16550A > > > > > > Hmm, for some reason it doesn't look like the serial is configured > > > completely. On my system I get this: > > > > > > PCIO serial driver version 1.18.2.5 > > > su(serial) at 0xf9fff13803f8 (tty 0 irq 6,7dc) is a 16550A > > > su(serial) at 0xf9fff13602f8 (tty 1 irq 4,7dd) is a 16550A > > > SAB82532 serial driver version 1.30.2.2 > > > ttyS00 at 0x1fff140 (irq = 12,7eb) is a SAB82532 V3.2 > > > ttyS01 at 0x1fff1400040 (irq = 12,7eb) is a SAB82532 V3.2 > > > Console: ttyS0 (SAB82532) > > > > > > Which version of boot-floppies are you using? > > > > I have tried several, but the log is from 2.2.13. > > Can you be more specific on which ones you have tried? Did you try the > 2.2.15 images at: > > http://auric.debian.org/~bcollins/disk-sparc/current/ > > This would help a lot in pinpointing the initialization problem. > 2.2.15 -> same problem. 2.2.12 -> Does not start, error message "no kernel". I am using the sun4u image ( maybe goes without saying? ). /Thomas Lange/
Re: Serial PCI ports
On Wed, Jun 07, 2000 at 11:50:00AM +0200, Thomas Lange wrote: > > > > PCIO serial driver version 1.18.2.6 > > > su(serial) at 0xf9fff13803f8 (tty 0 irq 6,7dc) is a 16550A > > > su(serial) at 0xf9fff13602f8 (tty 1 irq 6,7d4) is a 16550A > > > > Hmm, for some reason it doesn't look like the serial is configured > > completely. On my system I get this: > > > > PCIO serial driver version 1.18.2.5 > > su(serial) at 0xf9fff13803f8 (tty 0 irq 6,7dc) is a 16550A > > su(serial) at 0xf9fff13602f8 (tty 1 irq 4,7dd) is a 16550A > > SAB82532 serial driver version 1.30.2.2 > > ttyS00 at 0x1fff140 (irq = 12,7eb) is a SAB82532 V3.2 > > ttyS01 at 0x1fff1400040 (irq = 12,7eb) is a SAB82532 V3.2 > > Console: ttyS0 (SAB82532) > > > > Which version of boot-floppies are you using? > > I have tried several, but the log is from 2.2.13. Can you be more specific on which ones you have tried? Did you try the 2.2.15 images at: http://auric.debian.org/~bcollins/disk-sparc/current/ This would help a lot in pinpointing the initialization problem. -- ---===-=-==-=---==-=-- / Ben Collins -- ...on that fantastic voyage... -- Debian GNU/Linux \ ` [EMAIL PROTECTED] -- [EMAIL PROTECTED] -- [EMAIL PROTECTED] ' `---=--===-=-=-=-===-==---=--=---'
Re: Serial PCI ports
> > PCIO serial driver version 1.18.2.6 > > su(serial) at 0xf9fff13803f8 (tty 0 irq 6,7dc) is a 16550A > > su(serial) at 0xf9fff13602f8 (tty 1 irq 6,7d4) is a 16550A > > Hmm, for some reason it doesn't look like the serial is configured > completely. On my system I get this: > > PCIO serial driver version 1.18.2.5 > su(serial) at 0xf9fff13803f8 (tty 0 irq 6,7dc) is a 16550A > su(serial) at 0xf9fff13602f8 (tty 1 irq 4,7dd) is a 16550A > SAB82532 serial driver version 1.30.2.2 > ttyS00 at 0x1fff140 (irq = 12,7eb) is a SAB82532 V3.2 > ttyS01 at 0x1fff1400040 (irq = 12,7eb) is a SAB82532 V3.2 > Console: ttyS0 (SAB82532) > > Which version of boot-floppies are you using? I have tried several, but the log is from 2.2.13. /Thomas Lange/
