Re: Problems with X11 on Ultra10, BusID value
Op 2014-05-04 om 13:38 schreef David Gosselin: > From: Sad Clouds > Sent: Sunday, May 04, 2014 3:57 AM > > On Sun, 4 May 2014 08:25:16 +0100 Sad Clouds wrote: > > >On Sat, 03 May 2014 17:20:33 -0600 Hayden Kroepfl wrote: > > >> On 03/05/14 03:39 PM, Sad Clouds wrote: > > >> > Hello, I'm new to Debian and trying it out on Ultra10 which has > > >> > Creator3D framebuffer. > > >> > > > >> > I installed Debian stable and seem to be having some issues with > > >> > X11 or display manager. The system boots OK and I can see boot > > >> > messages, but when it goes to start display manager the screen > > >> > goes black and nothing happens. No windows, no mouse cursor, > > >> > nothing. > > >> > > > >> > Any ideas? > > >> > > > >> > > > >> > > >> Might as well ask about the obvious right away, do you have your > > >> monitor hooked up to the onboard video in the bottom left corner > > >> (facing the back), or to the 13W3 video connector on the Creator3D? > > >> What could be happening is X11 picked the wrong card by default and > > >> is only showing it on the opposite connector. If you have a second > > >> monitor try hooking one up to the 13W3 and one to the VGA connector. > > >> > > >> Hayden K. > > > > > >Hello, that was the first thing I tried however there is no VGA signal > > >on machfb. I managed to get IP address assigned to this machine from > > >DHCP server, logged in via ssh and looked at the logs. Looks like X > > >server has problems configuring framebuffer device. > > > > > >So I generated xorg.conf manually with 'X -configure' and it thinks I > > >have 3 cards: > > > > > >Identifier "Card0" > > >Driver "mach64" > > >BusID "PCI:1:2:0" > > > > > >Identifier "Card1" > > >Driver "fbdev" > > >BusID "PCI:1:2:0" > > > > > >Identifier "Card2" > > >Driver "vesa" > > >BusID "PCI:1:2:0" > > > > > > > > >This looks wrong to me, one of them should be using sunffb driver. And > > >why all three drivers refer to the same BusID? > > > > > >I tried copying this file to /etc/X11/xorg.conf and leaving only > > > > > >Identifier "Card1" > > >Driver "sunffb" > > >BusID "PCI:1:2:0" > > > > > >But still can't get X11 running > > > > > >Any ideas? > > > > OK changed that to > > > > BusID "SBUS:/SUNW,ffb@1e,0" > > > > and X11 works now. > > > > Hi, > I was curious as to what prompted you to try "SBUS:/SUNW,ffb@1e,0" > for the BusID value? Me too > Thanks, > Dave And the archive mostlike also. Please respect the discussion sequence and reply below the text. Groeten Geert Stappers -- Leven en laten leven signature.asc Description: Digital signature
Re: Console problems during installation of Lenny
Op 20081213 om 17:14 schreef Klaus Klein: > Geert Stappers wrote: >> Op 20081213 om 13:54 schreef Frans Pop: >>> I've looked at the logs you sent me provately and the first showed a >>> stupid syntax error in the reopen-console script. I've just uploaded >>> a new version of rootskel to fix that. >> a Local build of the Sparc rootskel udeb was done. >> >>> Daily images that include the new version (1.72) should work >>> correctly. Those should normally be available tomorrow, but to be >>> certain you could wait an extra day to retry. >> an Extra daily build was done for Sparc > > Wow, that's fast!! Thanks for the compliment >>> You can check which version is included in daily images by looking at: >>> http://people.debian.org/~stappers/d-i/sparc/daily/MANIFEST.udebs >> The temporary udeb is named rootskel 1.72+localudeb >> and will be gone after tomorrow. > > I guess I better then download it today! Relax, the temporary rootskel_1.72+localudeb will replaced with rootskel_1.72 > Unfortunately, the daily build on > http://cdimage.debian.org/cdimage/daily-builds/daily/arch-latest/sparc/iso-cd/ > > is still from 10:38 (09:38 UTC). Is that the one you referring to? Now with URL: http://people.debian.org/~stappers/d-i/sparc/daily/ >> Feedback of the new tests are welcome. > > I'll do that. :-) I'm looking forward to it. Cheers Geert Stappers -- To UNSUBSCRIBE, email to debian-sparc-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Re: Console problems during installation of Lenny
Op 20081213 om 13:54 schreef Frans Pop: > > I've looked at the logs you sent me provately and the first showed a > stupid syntax error in the reopen-console script. I've just uploaded a > new version of rootskel to fix that. a Local build of the Sparc rootskel udeb was done. > Daily images that include the new version (1.72) should work correctly. > Those should normally be available tomorrow, but to be certain you could > wait an extra day to retry. an Extra daily build was done for Sparc > You can check which version is included in daily images by looking at: > http://people.debian.org/~stappers/d-i/sparc/daily/MANIFEST.udebs The temporary udeb is named rootskel 1.72+localudeb and will be gone after tomorrow. Feedback of the new tests are welcome. Cheers Geert Stappers signature.asc Description: Digital signature
Re: Console problems during installation of Lenny
Op 20081213 om 13:23 schreef Klaus Klein: > > Where should I put them (gzip'ed)? Bugreport #504721, Console broken on debian-installer on Sparc LDOM, did came to mind. Checking http://bugs.debian.org/504721 showed that the BR is closed. So E-mailing them to 504...@bugs.debian.org is not a good thing. > Should I really send as an attachment to this list? Open a bugreport for it by sending an E-mail to sub...@bugs.debian.org Start the E-mail message with these lines: Package: rootskel Version: 1.71 You get a bug report acknowledge message with bugreport number back. Send to $bugreportnum...@bugs.debian.org the log files. By keeping the BR opening E-mail small, will the BR closing msg also small. That is because the closing message contains the complete opening mail. Cheers Geert Stappers signature.asc Description: Digital signature
include e1000e module WAS: t5120 support?
Op 20081128 om 13:20 schreef david manyé: > > thanks brian, > > now i can successfully boot the machine but the problem is now the network > card: there are 4 nics intel 82571 that, if i'm not wrong, require the > e1000e driver and in the boot.img used to boot this driver is missing. > > if i knew how to rebuild the boot.img file... > > any idea?hello, > > now i can successfully boot the machine but the problem is now the network > card: there are 4 nics intel 82571 that, if i'm not wrong, require the > e1000e driver and in the boot.img used to boot this driver is missing. > > if i knew how to rebuild the boot.img file... > > i'll post a message on debian-boot ... > > any idea? thanks. Be aware that you can encounter BR #507148, http://bugs.debian.org/507148 But that problem will be an easier way then to backport the e1000e driver to the previous Debian release. Cheers Geert Stappers signature.asc Description: Digital signature
Re: preventing that a module is being loaded
Op 20081026 om 19:19 schreef Brian Thompson: > Has anyone had any success with disabling/blacklisting a > kernel module? The Debian docs show the following but > it's not working for me on 2.6.18-6-sparc64... The module > still loads. It was a long time ago that I succesfull blacklisted a kernel module. >> Sometimes two different modules claim support for the same device, >> usually because two slightly different versions of the device exist, >> requiring different kernel modules to operate. In such situation udev >> loads both kernel modules, with unpredictable results. To avoid this >> problem, you can prevent any module (let's say, tulip) from loading by >> creating an arbitrarily named file, containing a line >> >> blacklist tulip >> That doc doesn't tell the full path of the "black list file" Being curious about the full path, I searched on system here available and found /etc/modprobe.d/blacklist It didn't contain module names I had add myself, so now I'm curious if /etc/modprobe.d/blacklist works for the original poster. Cheers Geert Stappers -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: Problem installing Debian 4.0r4a on SunBlade 100
Op 20081022 om 08:08 schreef Ambrogio Sironi: > Glacier Hi all > > I'm trying to install Debian 4.0r4a on SunBlade100. > > WS conf.: > OBP: 4.17.1 > Ram: 1Gb > > Debian: > SILO 1.4.13 > > > Staring the boot from CD I see: > > Allocated 8 Megs of memory at 0x4000 for kernel > > Loaded kernel version 2.6.18 > > Loading initial ramdisk (3881967 bytes at 0x3F802000 phys, 0x40C0 > virt)... > > ERROR: Last trap: Illegal Instruction > > Error -256 > ERROR: Last trap: Fast Data Access MMU Miss I did seen such messages myself. I got them at a warm boot and could resolve them by a cold boot. (power down, machine gets cold, power up) > Error -256 > > Stack Underflow > > ok > > Help me !!!! > Thanks in advance. Real feedback is also appriciated, especial for the archive. > By Cheers Geert Stappers -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: Sparc Classic 4.
Op 20080929 om 12:27 schreef Gerfried Fuchs:
> Am Samstag, den 27.09.2008, 21:08 -0400 schrieb Pablo Elías Abarca Salvo:
> > Hey, I need to know which version of Debian I used to a Sparc Classic 4.
>
> Personally I am not sure, but I guess debian-sparc@lists.debian.org is
> the better list to ask for that (forwarded your message there).
IIRC is the Classic 4 a 32-bit Sparc,
so you will need version 3.0 a.k.a. Sarge.
( Since version 3.1 ("Etch") are only the 64-bit Sparc machines
supported )
HtH
GSt
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: PCI cards on Ultra5
Op 20080824 om 15:25 schreef Christian Euler: > Hi everybody, > > I plugged a PCI USB card in my good old Ultra 5 box (running Debian Etch > with 2.6.24 kernel), but the card doesnt show up in lspci. > > Is there anything special about PCI support on UltraSparc? Not as far I known. I think the original poster is encountering hardware defects. Hardware test to preform: * place a known to be working PCI (Network) card in the Ultra 5 * place the PCI USB card in known to be working PCI slot. HtH G -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: esp_scsi in the debian installer
Op 10-04-2008 om 19:37 schreef Nick Schmalenberger: > Hi, > I thought the esp scsi driver was supposed to be fixed in 2.6.23 or > 2.6.24, but on my Ultra/1 it isn't working with todays daily build of > the netboot installer. Attached are the debug logs. Has anybody had this > working? Thanks. > Nick Schmalenberger > Apr 11 01:48:49 syslogd started: BusyBox v1.9.2 > Apr 11 01:59:57 net/hw-detect.hotplug: Detected hotpluggable network > interface eth0 > Apr 11 01:59:57 net/hw-detect.hotplug: Detected hotpluggable network > interface lo > Apr 11 01:59:58 hw-detect: ISA bus detected; loading module 'ide-generic' > Apr 11 01:59:58 hw-detect: insmod > /lib/modules/2.6.24-1-sparc64/kernel/drivers/ide/ide-generic.ko > Apr 11 01:59:58 net/hw-detect.hotplug: Detected hotpluggable network > interface eth0 > Apr 11 01:59:58 net/hw-detect.hotplug: Detected hotpluggable network > interface lo > Apr 11 02:00:02 hw-detect: Missing modules 'esp (ESP SCSI), usb-storage (USB > storage) > Apr 11 02:00:03 net/hw-detect.hotplug: Detected hotpluggable network > interface eth0 > Apr 11 02:00:03 net/hw-detect.hotplug: Detected hotpluggable network > interface lo > Apr 11 02:00:04 kernel: end_request: I/O error, dev fd0, sector 0 > Apr 11 02:00:06 kernel: end_request: I/O error, dev fd0, sector 0 > Apr 11 02:00:08 kernel: end_request: I/O error, dev fd0, sector 0 > Apr 11 02:01:17 kernel: SCSI subsystem initialized > Apr 11 02:01:17 disk-detect: insmod > /lib/modules/2.6.24-1-sparc64/kernel/drivers/scsi/scsi_mod.ko > Apr 11 02:01:17 disk-detect: insmod > /lib/modules/2.6.24-1-sparc64/kernel/drivers/scsi/scsi_transport_spi.ko > Apr 11 02:01:17 disk-detect: insmod > /lib/modules/2.6.24-1-sparc64/kernel/drivers/scsi/esp_scsi.ko > Apr 11 02:01:17 kernel: end_request: I/O error, dev fd0, sector 0 > Apr 11 02:01:19 kernel: end_request: I/O error, dev fd0, sector 0 > Apr 11 02:01:21 kernel: end_request: I/O error, dev fd0, sector 0 > Apr 11 02:01:40 main-menu[599]: INFO: Menu item 'disk-detect' succeeded but > requested to be left unconfigured. > Apr 11 02:01:40 main-menu[599]: INFO: Modifying debconf priority limit from > 'high' to 'medium' > Apr 11 02:01:40 debconf: Setting debconf/priority to medium > Apr 11 02:02:16 main-menu[599]: INFO: Falling back to the package description > for auto-install > Apr 11 02:02:16 main-menu[599]: INFO: Falling back to the package description > for ai-choosers > Apr 11 02:02:16 main-menu[599]: INFO: Restoring default debconf priority > 'high' > Apr 11 02:02:16 debconf: Setting debconf/priority to high > Apr 11 02:02:16 main-menu[599]: INFO: Menu item 'download-installer' selected Please elaborate "it isn't working with todays daily" What kind of error does occure? Could the error message(s?) be posted to the list? Cheers Geert Stappers -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: How to Send BREAK signal from Minicom to Ultra5?
Op 06-03-2008 om 03:54 schreef Ivan Kabaivanov: > On Thursday 06 March 2008, beeej wrote: > > Hi, I am attempting to gain console access to my Ultra5/ttyb from > > Ubunutu/Minicom. > > I have connected from my Desktop USB --> USB converter --> Serial > > Cable --> Null Modem --> Ultra5/ttyb. > > > > Do you have a real serial port on that machine? Get USB out of the equation. > > > I have a serial cable+null modem connected to ttya on a Sunfire280r, blade100 > and an ultra enterprise2 and ctrl+a+f always works. And most likely on ttya. About documenting succes: At Sparc side I use ttya, the 25-pins connector, at the other side a real[1] serialport and inbetween 9600baud 8N1 Cheers Geert Stappers [1] 'real' as in "not a USB to serial convertor" -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: serial port OK prompt
Op 06-03-2008 om 01:17 schreef beeej: > > > > Within minicom, my serial line terminal, I did send the break signal. > > I was expecting to get the OK prompt, but didn't get it. > > > > What is the way to get to the OK prompt > > when the console is a serial terminal? > > > > Hi, did you get this working? Yes. ( http://lists.debian.org/debian-sparc/2008/01/msg00044.html ) > I am also not able to send a break signal to my ultra5 from minicom. > i see output from the console and watch teh solaris system booting up > but cannot stop the process with ALT-A-F sequence as per minicom > guide. FYI: I estimate that my break signal from minicom comes in about nine out of ten tries through. > also im not sure that the input is setup correctly as i dont get > output from keyboard. ie at Solaris Login Prompt, when i attempt to > key in the username, the console responds to what looks like a > carriage return and i cannot see what i type. > > any help much appreciated. I assume a mismatch in parity and/or word size. > beej Cheers Geert Stappers -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: problem to install on Blade 1000
Op 29-01-2008 om 11:25 schreef a.m.: > > Hi all. I need to recover an installation in which there is a mistake and > it doesn't boot. > I decided to install a small debian on a partition on my blade 1000, > using boot net. > Two years ago I installed the system with boot net. This time it doesn't > work and my blade deen't find the disk. I know that the > problem in qlogic, but I don'remember how to solve it. > I used "Debian install on SUN Blade 1000" but when I try: modprobe qlogicfc > system say that doesn't exist. My guess is that the kernel module is renamed. You might find the new name with ls /lib/modules/$(uname -r)/kernel/drivers/scsi/ql* then "modprobe" the module without the path and the .ko > Con you help me to solve my problem? > Alternatively, when appears silo promp What instruction I've to give it to > start: > vmlinuz > initrd > root partition > ... > > What is the correct manner to give these instruction? The setup of silo is done fine by debian-installer, if you have to setup silo, something else went wrong. (like a disk controllor not being found) Futher: I think it is a good thing to file an installation report for your computer, see http://d-i.alioth.debian.org/manual/en.sparc/ch05s03.html#problem-report for more information. Especial because you want that the next install is even smoother. Cheers Geert Stappers signature.asc Description: Digital signature
Re: OBP help, please.
Op 27-01-2008 om 20:36 schreef Chris Andrew: > On 27/01/2008, Geert Stappers <[EMAIL PROTECTED]> wrote: > > Op 26-01-2008 om 14:11 schreef Chris Andrew: > > > Hi, all. > > > > > > I've just rebuilt my Ultra 10, with different drives. Unfortunately > > > my CDROM no longer seems to be mapped correctly. > > > > > > I've made this mistake before, but can't remember how I got around it. > > > > > > I know I need to do something with devalias/ nvalias and show-disks, > > > but I can't for the life of me remember what. > > > > > > Additionally, I seem to have several entries for my CDROM (my fault, > > > trying to create a good alias). > > > > Could 'set-default' help? > > > > > Can anyone spell it out for me, so I can do a fresh install on this box. > > > > > > I could have miss spelled 'set-default'. > > Geert, > > Thanks for your advice. I tried set-default, and nothing seemed to change. > > Still trying to resolve this problem. And meanwhile you have more problems to solve, at least some things to notice. The important one is to read http://www.catb.org/~esr/faqs/smart-questions.html because that document would have prevent you from asking off-topic questions and "I shoot myself in the foot, could you help me?" questions. Bringing a private reply back to a public list, is the same as saying: "Public posting and Private posting are equal to me" For your information: There is huge difference between public and private ... And if one brings a posting to the public, then allow your audience to read in the discussion order. Geert Stappers In a "reply-to-list" -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: Netboot E250 -- tftp problem, cables and IDE
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Op 23-01-2008 om 10:30 schreef Hero_xbd!.RRR: > Martin wrote: >> PC in dorm <--> ... some network ... <--> switch <--> server >> ^ >> | >> | >> V >> E250 >> >> (Where arrows are ethernet cables) >> >> then you will have tested all but the cable that goes from the switch to >> the E250. If your topology is different then what you have tested will >> be different. >> > Hmm, I think I can interchange the cable of E250 and server to test(The > Switch is not accessible to me now) In another posting there was stated to not use a switch. My advice is to NOT got there. Even if you have a UTP cross cable, there is still the risk that it fails due no link single. I recomment to use some home office switch, one of those simple eight port devices. And replug UTP cable when debian-installer is netbooted. Start: univeristy core small network switch switch ^^ / | / | / | vV E250startsrv Replugged: univeristy core small network switch switch ^ | | | v E250startsrv That way you have only to install rarpd & tftp programs on the start server, only configure /etc/ethers and only the sparc boot image in the tftpboot directory ( no http server, no debian archive mirror ) >> PS If you get really stuck netbooting, you could pull the disks, dump a >> minimal filesystem on them and then boot from disk. >> > E250 is using an old scsi interface. Here in my university you can rarely > see scsi, and if there is one, it is of new interface... > > I myself is not fimilar with scsi, I do not know the specification of the > bus(I know they're different, one is old one is new) Is the CDROM driver also a SCSI device? ( It might be IDE ... ) > Oh, perhaps I can have an IDE PCI card on E250 use an IDE HDD to boot. The original idea[1] of PCI was, to put machine independent program code in the ROMs of the cards. So when you have IDE PCI card with bootROM, that boots for an i386, your changes are good that it boots on Sparc. > While I am still curious about what is blocking me from netbooting... Me too Cheers Geert Stappers [1] Actual it is in the specification of PCI. PS If you get _really stuck_ netbooting, you could consider serial download. ( might even work for a firmware upgrade ) -BEGIN PGP SIGNATURE- Version: GnuPG v1.2.4 (GNU/Linux) iD8DBQFHlzQAOSINbgwa/7sRAlKnAJ9Ib+mFCmkzAt1mKPD1hQmIHRJznwCfU4o3 aopWJujqBcreWUqW4e+UJWI= =Imya -END PGP SIGNATURE- -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
dump and Fast Data Access MMU Miss
Op 23-01-2008 om 15:39 schreef Hero_xbd!.RRR: >> ok 4200 Data Access Error >> >> ... > I have tried again as follows: > > ok boot net > > 4400 Data Access Error > > ok dump 4000 600 > > 0 Fast Data Access MMU Miss > > I think this "MMU Miss" message is an important clue. I don't think so :-) The OpenBoot PROM has a Forth interpreter. ( http://en.wikipedia.org/wiki/Forth_%28programming_language%29 ) Forth is stack based, it uses RPN, Reverse Polish notation as seen also in Hewlett&Packard Calculators. 4000 600 dump does work fine, but I think you want 4400 200 dump for screen size reasons. Cheers Geert Stappers -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: Netboot E250 -- tftp problem
Op 22-01-2008 om 21:31 schreef Hero_xbd!.RRR: > Geert Stappers wrote: >> Could it be firewall software on the TFTP server? > > I am using fail2ban[1] on the TFTP server, which functions on iptables and > is supposed to modify only "ftp ftps ftp-data ftps-data ssh"ports. Except > it, I did not do anything with firewall. Right now, we don't known what is blocking us, we have to put fail2ban on the list of suspects ... > Oh, maybe I should use a shiny minimum debian mechine to act as the TFTP > server. That will eliminate various potential blocks. I think that is a very good option. > Is it possible the NICs and Net Switch produce the problem? Unlikely, but put it the bottom of the list with suspects. > Does the working rarp session eliminate all the possibility? The RARP session was indeed succesfull. But RARP is on a different network layer as TFTP is. So it could indeed that a network component like a switch, does screw TFTP, but doesn't mangle RARP > Stappers, I have noticed that your .pcap file also has one packet with > checksum error. Does it infer that "checksum error" is in some degree > irrelevant? Rechecking http://www.stappers.nl/gst/temporary/e250/rodebes.pcap reveals indeed a checksum error. However it is the last TFTP block of the file. The block size is 28, not the regular 512. The download is succesfull, the program works fine and there is surely not 'Data access error'. I just did `ls > /var/lib/tftpboot/AC18000F` to get less then 512 bytes in the file that my Sparc (at address 172.24.0.15) downloads with the 'ok' prompt command `load net`. The single TFTP packet had according wireshark also a checksum error, but the transfer was fine. ( checked with `4000 200 55 fill`, `load net` and `4000 200 dump` ) > > 1. http://www.fail2ban.org Cheers Geert Stappers P.S. About latin names: It is indeed common to use the first name, it is just me who choose an uncommon family name as nick name. P.P.S. I'm subscribed to the mailinglist -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: Netboot E250 -- tftp problem
Op 22-01-2008 om 11:01 schreef Hero_xbd!.RRR: > Geert Stappers wrote: >> My advise is to check the version the tftpd server. >> Over here says `dpkg -l tftpd-hpa` that I'm using version 0.48-1. >> >> For reference you may wireshark >> http://www.stappers.nl/gst/temporary/e250/rodebes.pcap >> Rodebes is the hostname of an Ultra5 at address 172.24.0.15 > > Greet, Great, is is actual Geert By the way, I prefer 'stappers', it goes back to the mid 1990 when I on the same mailinglist as Geert Uyterhoeven. With 'stappers' it is unambiguous which Geert is meant. Stappers is also my IRC nickname and Debian account name. > I have followed your instructions, and the memory seems to be alright. (it > fills "55" and "aa" as expected) > I have removed "-r blocksize" and it gives no difference. > (Maybe I should try out inetd? Almost all the documents around the net > netbooting sparc use inetd instead of standalone tftpd.) > > I have also checked the version: > > Openboot 3.12 > tftpd-hpa 0.48-1 > > I compared the .pcap file with yours, and it seems there is no difference > except for the "check sum error". (Wireshark said 'maybe caused by "UDP > checksum offload"? ' -- what does that mean? Can it give us some clue?) Over here I can't reproduce the error when the TFTP server is standalone. Still it is a good thing try how the TFTP server behaves under inetd. Because netbooting SUNs is a working thing, I'm curious what blocks it this time. Could it be firewall software on the TFTP server? Cheers Geert Stappers -- Bonus points for respecting the discussion order (in other words: Reply _below_ the text ... ) -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: Netboot E250 -- tftp problem
Op 21-01-2008 om 15:43 schreef Hero_xbd!.RRR: > Hi, everybody! Hello, > I am trying to install a debian-sparc system on an old Enterprise 250(E250) > in our lab. ~ > 2. Turn on E250(in the same LAN as netboot server), Press Stop-A to get the > OPENBOOT prompt, issue"boot net", it reads that: > Boot device:/[EMAIL PROTECTED],4000/[EMAIL PROTECTED],1 File and Args: > Time out waiting for ARP/RARP packet > 4200 Data Access Error > and throw me to the "ok" prompt again. ~ > I don't know what to do now, I have tried everything I know and everything > I can find on the net, but still stack with this problem. Please give me > some suggestions. > > Thanks in advance! Thank YOU for the good posting! It really shows you did your part!!! The 'Time out waiting for ARP/RARP packet' is normal, if there was no RARP deamon responding, there would be much more RARP Time-out messages. But the '4200 Data Access Error' is a scary one ... 4000 is the default download start address. 4200 is start plus 200. 0x200 is 512 decimal, the size of a default TFTP packet. How to classify 'Data Access Error' is the challenge. If there are problems with memory, the 'ok' wouldn't probably not been show. Just do a simple check by these five separate command at the 'ok' prompt: 4 400 dump 4 400 55 fill 4 400 dump 4 400 AA fill 4 400 dump to make sure it is really no memory problem. I see one possible cause of the probleem: Size of the TFTP packet. I imagine that the first TFTP block is transferred fine and the next block goes wrong, due allocated size and actual size differences. The wireshark analyzis could reveal it ... [1] Over here I do succesfull netboots on an Ultra 5, it has OpenBoot 3.19. As tftp server is also tftpd-hpa used, under inetd. But shouldn't make a difference. Difference is that I don't do '-r blocksize' Cheers Geert Stappers DD [1] I'm willing to check a wireshark slash tcpdump .pcap file that is all ready filtered to contain only packets that match the MAC address of the E250. You may send that binary file off-list to me. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: serial port OK prompt
Op 10-01-2008 om 15:26 schreef ?? / Nishant: > On Jan 10, 2008 3:10 PM, Geert Stappers <[EMAIL PROTECTED]> wrote: > > What is the way to get to the OK prompt > > when the console is a serial terminal? > > My experience says - powercycle the box and remove monitor, keyboard > and mouse before it loads openprom. Did it once on a SunBlade100 with > minicom on a Linux box connected using a serial cable. That will still boot the SUN. With setting setenv auto-boot? false I get the OK prompt. And for some reason does sending break now get me the OK prompt. (Previous it didn't, hence the reason for this thread) Note: The serial break doesn't get so fast to OK as 'STOP-A' does. Thanks Geert Stappers -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
serial port OK prompt
Hello, On a SUN Ultra 5 with Sun keyboard you press 'STOP-A' to get the OK prompt from the OpenPROM ROM software. When the keyboard is removed, "console" is switched to the serial port. Within minicom, my serial line terminal, I did send the break signal. I was expecting to get the OK prompt, but didn't get it. What is the way to get to the OK prompt when the console is a serial terminal? Cheers Geert Stappers -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
The 'Illegal instruction' problem occurs unless ...
For your information - Forwarded message from Josip Rodin <[EMAIL PROTECTED]> - From: Josip Rodin <[EMAIL PROTECTED]> To: dat <[EMAIL PROTECTED]> Cc: [EMAIL PROTECTED] Subject: Re: Unidentified subject! Date: Mon, 7 May 2007 00:57:14 +0200 User-Agent: Mutt/1.5.13 (2006-08-11) On Thu, May 03, 2007 at 01:08:33PM -0700, dat wrote: > As requested ( section 3.2 of > http://www.debian.org/releases/etch/sparc/release-notes/ch-installing.en.html#s-sparc_illegal_instruction > )... > > You can add Enterprise 220R boxes to the list. The 'Illegal instruction' > problem occurs unless system is powered down and then booted directly > from cdrom without allowing solaris to begin to boot. Thanks for the info. -- 2. That which causes joy or happiness. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED] - End forwarded message - HtH GSt -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: How to edit the boot.img
On Tue, Oct 25, 2005 at 12:16:17AM +0200, Riccardo Tortorici wrote: > (CCing Geert Stappers and debian-sparc list) ( this message is also crossposted and assumes subscription to MLs ) > Just a question: how can I edit my own boot.img? I'm new to D-I and I > would like to customize a 2.6.12 kernel in order to fix the FB and > put it inside the image I used this time. Thanks in advance, More eye-balls on d-i, especial in the sparc corner, are allways welcome. The "boot.img" is a kernel and Debian-Installer initial ramdisk (initrd) in one file. Visit http://wiki.debian.org/?DebianInstaller for information how to edit it. Cheers Geert Stappers signature.asc Description: Digital signature
Re: D-I update for Sparc (daily builds)
On Mon, Sep 05, 2005 at 03:59:45PM -0700, Tyler wrote: > Frans Pop wrote: > > >Hi, > > > >The default kernel for sparc64 installations is now 2.6.12, > >with 2.4.27 as alternative. > > > > > What is the address where the daily builds are available? Also, does > this imply that there is a *working* bootable image for people having > the Fast MMU Access error with any/all CD's they've tried thus far? If > it doesn't fix this problem, when can we expect a working image? Also, > is there a direct link to an image that *does* work... the only one I've > found to be reported as working around this bug, was a daily image from > a few months ago, that is no longer on any archives/sites/mirrors that I > can find. Visit http://www.nl.debian.org/devel/debian-installer/ports-status for another click to the daily images. About the "Fast MMU Access" error: What I understand for the problem is that the sysvinit source code is fine, but for Sparc generates the compiler executable code that uses registers that are not available in all Sparc CPUs. It is worth to try again. The buildd log at http://buildd.debian.org/fetch.php?&pkg=sysvinit&ver=2.86.ds1-1.1&arch=sparc&stamp=1124310602&file=log&as=raw says that sysvinit is now rebuild with GCC 4.01. The previous version from januari was build with 3.3. > > Thanks, > Tyler. Please provide feedback St signature.asc Description: Digital signature
Re: Proposal to document sparc installation issues
On Tue, Mar 29, 2005 at 10:53:32PM +0200, Frans Pop wrote: > On Tuesday 29 March 2005 22:45, Geert Stappers wrote: | | [ kernel upgrade from 2.4 to 2.6 causes broken keyboard setup ] > > > >Login by ssh or serial line to cover keyboard. Login by ssh or serial line to recover keyboard. > > > > Probaly more informative. > > Could you elaborate? No idea what you mean by "cover" here. typo, sorry > BTW. logging in via SSH at that stage is not possible because: > A) ssh is not yet installed, so no sshd running (except if you installed >using network-console); > B) root does not yet have a password and logging in over SSH without >password is disabled anyway (so even in the network-console case this >is not a solution). Even beyond d-i a kernel upgrade breaks keyboard setup. > > Cheers, > FJP Cheers Geert Stappers signature.asc Description: Digital signature
[EMAIL PROTECTED]: time's up]
Hi, The message below showed up on debian-boot@lists.debian.org and now it is at the Sparc mailinglist of Debian. Please update the Silo bugreports with the information that you have. Cheers Geert Stappers - Forwarded message from Steve Langasek <[EMAIL PROTECTED]> - From: Steve Langasek <[EMAIL PROTECTED]> To: [EMAIL PROTECTED], [EMAIL PROTECTED] Cc: debian-boot@lists.debian.org Subject: time's up Date: Tue, 22 Mar 2005 02:54:12 -0800 User-Agent: Mutt/1.5.6+20040907i severity 261824 important severity 267428 important thanks Time's up, folks; if no fix has been found yet for these bootloader bugs, they'll have to remain hardware-specific errata for sarge. They will no longer be allowed to block the release, since silo still works on the majority of sparc hardware. Someone should, however, document these problems for the install manual and/or d-i errata. If someone can determine one way or another whether the gcc-2.95 rebuild actually fixes the problem on Ultra5 for someone other than Geert, that would help me in deciding whether an NMU is warranted. Thanks, -- Steve Langasek postmodern programmer - End forwarded message - signature.asc Description: Digital signature
Re: boot cdrom error
On Fri, Mar 04, 2005 at 04:52:06AM +0100, gaspo wrote: > hi i have this problem now..i wanna reinstall my freebsd for have a > fresh installation of debian... on my ultra5 sun server... > but when i type: > stop A > ok > boot cdrom > Can't read disk label. > Can't open disk label package > Can't open boot device > > how is possible? > because on this hard disk was installed solaris5.7.. i replace freebsd > 5.3 some day ago with normal installation on cd boot cdrom ecc.and > all work...perfectly..now WITH same hard disk and same CD...i can boot > freebsd rom cd > > why?? > i have tried also to reburn cdrom...change CDROM ..change Operative > sistem...like netbsd openbsd ecc... but The only sistem boot from Cd > is sun 10.. > anybody have any idea? Something wrong with the image? Cheers Geert Stappers signature.asc Description: Digital signature
Re: Changing ip and hostname, gnome problem
On Tue, Dec 07, 2004 at 10:42:20AM -0600, Chanslor, Michael David wrote: > Debians - I have changed debian/sparc/testing ip address and hostname to > a new subnet. > Modified: > /etc/network/interfaces > /etc/hosts > > 1.)Changes reflect in ifconfig, and talks on network OK > 2.)The problem is now gnome starts, but does NOT start menu bars, it's > almost like a fail-safe session because I get one window and can not > move it around... > 3.) I can change /etc/hosts and /etc/network/interfaces back to old and > everything works fine... > > Any ideas? Convines us that it is debian-sparc@lists.debian.org related. Cheers Geert Stappers -- Choose the forum carefully --smart questions rule #1 signature.asc Description: Digital signature
Re: Serial Terminal Virtual Consoles
On Tue, Dec 07, 2004 at 07:58:46PM -0800, Jason Parvu wrote: > Does anyone how would I switch consoles (Ctrl-Alt-F2, etc) from > a serial terminal or is this possible. I am using a wyse-60 terminal and it > has no alt key? Welcome the wonderfull world of ASCII. I think you are looking for Package: screen Description: a terminal multiplexor with VT100/ANSI terminal emulation screen is a terminal multiplexor that runs several separate "screens" on a single physical character-based terminal. Each virtual terminal emulates a DEC VT100 plus several ANSI X3.64 and ISO 2022 functions. Screen sessions can be detached and resumed later on a different terminal. . Screen also supports a whole slew of other features. Some of these are: configurable input and output translation, serial port support, configurable logging, multi-user support, and utf8 charset support. Cheers Geert Stappers signature.asc Description: Digital signature
Re: Question on netboot
On Mon, Nov 22, 2004 at 12:20:14PM +0100, Jurzitza, Dieter wrote: > Dear listmembers, > to realize a netboot, I set up one of my boxes to run rarpd. The other one > (that should boot) boots usually from cdrom. > I took the vmlinuz, the System.map and the initrd file from the cdrom, > uncompressed vmlinuz, converted it to an aout file using elftoaout. > > Then I grouped the files by piggyback64 using > > piggyback64 vmlinux System.map initrd > > and put the resulting file vmlinux into the boot-server's tftpboot directory, > making a link to the target's ip-address. > > Everything seems to work, the boot starts, the kernel is being downloaded > from the server, the actual boot starts. > Then I get: > > *** > Freeing initrd memory - 923k freed > VFS: mounted root (ext2 filesystem). > /bin/sh: Can't open 172.16.56.152 (this is my tftp - server's IP address) > Unimplemented Sparc System Call 188 (propably unrelated) > Kernel panic: Attempted to kill init > press L1 > > Can anybody help me out of this? Many thanks in advance, > take care "boot net vmlinuz ramdisk=... ramdisk_size" See Debian-Installer Manual for detailed examples. > > > > Dieter Jurzitza Geert Stappers signature.asc Description: Digital signature
Re: Whats the trick to keep a Ultra 2 booting?
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On Sat, Nov 20, 2004 at 07:15:42AM -0700, Walt L. Williams wrote: > Greetings all Hello all, > I have been trying to load Sarge onto an Ultra 2. > I have tried several things in an effort to load so > it will boot. > > I seems to load ok after I do the modprobe work > around. But when the system goes to re-boot > it comes up and starts to run silo and promptly > terminates "Program terminated" > > In the partitioning I have set the boot flag to on, > then left it off. That didn't make any difference. > I pulled the second CPU thinking there was > something wrong with the SMP kernel. This > also didn't make any difference. I've even selected > the ext2 in the partitioning. That also didn't > make any difference. > > Any thoughts? Mmmm, http://bugs.debian.org/267428 is still open. > My system is an Ultra 2 with 256MB of ram > and dual 200MHZ processors. It has a 9GB > and an 18GB hard drive it it. I am hoping to > make a web server out of it. It was loaded > with Debain 3.0r0 . > > Any comments will be appreciated. Try http://www.stappers.nl/gst/pool/main/s/silo/silo_1.4.8-1.01_sparc.deb and tell us your milage. > Walt Williams Geert Stappers # md5sum silo_1.4.8-1.01_sparc.deb 5a5dfbb8192b6a9e04bff25b37e9eed6 silo_1.4.8-1.01_sparc.deb -BEGIN PGP SIGNATURE- Version: GnuPG v1.2.4 (GNU/Linux) iD8DBQFBn6siOSINbgwa/7sRAutEAKCasBMdZi1b/BKvAzzs9t32iPQJcACglOPd B+h4DKcux8Kaf9gKRP52X04= =yPb/ -END PGP SIGNATURE-
Re: mount ufs
On Fri, Nov 19, 2004 at 02:27:46PM -0800, Enrique Morfin wrote: > Hi! > > in sunblade150: > > i want to mount my solaris system, so: > > # mount -t ufs -o ufstype=sun /dev/hda1 /mnt/solaris/ ^ > mount: wrong fs type, bad option, bad superblock on > /dev/hda1,or too many mounted file systems > > but: > > #fdisk /dev/hda > > Command (m for help): p > > Disk /dev/hda (Sun disk label): 16 heads, 255 sectors, > 38307 cylinders > Units = cylinders of 4080 * 512 bytes > >Device FlagStart EndBlocks Id System > /dev/hda1 32911 38052 104876400 Empty Here seems /dev/hda1 empty > /dev/hda2 u 38052 383075202003 SunOS swap > /dev/hda3 0 38307 781462805 Whole disk > /dev/hda4 u 4 132261120 82 Linux swap > /dev/hda5 u133 10172 20479560 83 Linux native > /dev/hda6 u 10173 22722 25599960 83 Linux native > /dev/hda7 u 22723 32910 20781480 83 Linux native > /dev/hda8 0 3 61200 Empty > > > if i boot solaris, it boot without any trouble. > > is the fs wrong? I think you have something mixed up. Cheers Geert Stappers
Re: sun blade 1500 install
On Wed, Oct 27, 2004 at 02:27:46PM -0500, Matt Zagrabelny wrote: > hello, > > i am trying to install debian on a sun blade 1500. > > this box has: > > * hard disk, obviously :) > * cdrom > * network port > > * NO floppy > > i have tried installing with two different approaches: > > 1) tftp boot install. > > short answer why this approach fails: the boot image does not seem to > contain support for the network interface (tg3). Contact your hardware supplier (or better: demand GPL drivers before you buy) > > > 2) cdrom sarge pre rc2 install. > > short answer why this approach fails: the boot image has no keyboard > support after leaving the openboot prompt. Has the machine a serial port? > does anyone have any suggestions? Disassemble the computer Take the hard disk drive to another computer Assemble the computer > thanks, The price is to tell what worked :-) > matt zagrabelny Geert Stappers signature.asc Description: Digital signature
Re: silo problem?
On Sat, Oct 16, 2004 at 04:24:44PM +0200, Admar Schoonen wrote: > Hi > > A weird thing happened today. This morning, my Sun Ultra 5, running > debian unstable, booted fine like it always did. I upgraded the system > since it was a week old. A few hours later I had to reboot since a > process was misbehaving and couldn't be killed - not even with kill > -KILL. When the open boot had passed, it suddenly said 'The file just > loaded does not appear to be executable'. Booting with 'boot disk0:1' > gave the same message (while I am sure that was the right boot disk). > > I decided to do a netboot since I had a woody netboot image laying > around somewhere. I mounted the root disk, chrooted into it, downloaded > silo 1.4.8-1 (the latest in unstable - same as in testing), and > reinstalled it. After that, the system booted again like nothing > happened. > > I am sure I didn't upgrade my kernel today and I'm quite sure silo > wasn't upgraded either, since silo in testing is the same as silo in > unstable. Is there somebody here who can tell me what was going on? Try to find out which program did report "The file just load does not appear to be executable" > > Best regards > > Admar Geert Stappers
Re: Sarge boot problem w/ 2.6 kernel
On Fri, Oct 01, 2004 at 03:34:16PM -0500, Matthew Allen wrote:
> Hi-
> I'm trying to get the 2.6 kernel running on sparc linux for some research
> I am doing. I had been running woody for a while with no problems on a
> SunFire machine. My plan was to upgrade to sarge, and then to the 2.6
> kernel. When I upgraded to sarge I had the "Fast Data Access MMU Miss"
> problem, which I resolved by dropping back to the woody version of SILO.
>
> Now I have installed the 2.6.8 kernel, and can't get the machine to boot.
> With SILO 1.4.8 I get the following error message:
>
> SILO Version 1.4.8
> boot:
> Allocated 8 Megs of memory at 0x4000 for kernel
> Uncompressing image...
> Memory Address not Aligned
> {0} ok .registers
> Normal Alternate MMU Vector
> 0: 0000
> 1: 0 fff916d0 441e02 f1
> 2: 1 f000 14 f000
> 3:200 fffd0
> 4:3a5c000 4000
> 5: 0f fff90
> 6: 0 441606 80003ff180b6e
> 7: 342 f0061e80
> %PC 4000c000 %nPC 4000c004
> %TBA f000 %CCR 44 XCC:nZvc ICC:nZvc
> {0} ok
>
> Rolling back to the woody version of SILO (which is what fixed my original
> 2.4 kernel sarge install) produces a slightly different error message:
> SILO boot:
> Uncompressing image...
> Loading initial ramdisk
> Fast Data Access MMU Miss
> {0} ok .registers
> Normal Alternate MMU Vector
> 0: 0000
> 1: f005844c1 fff916d0 f1
> 2: f000 f00085b4 f000 f000
> 3: fffd fffd40
> 4: 800004 4000
> 5: f0012944 ffdbd7e0f0
> 6: fffefde0 881604 fffde
> 7: fffef780 4e 68 f0061e80
> %PC f000ad94 %nPC f000ad84
> %TBA f000 %CCR 88 XCC:Nzvc ICC:Nzvc
> {0} ok
>
>
> Any idea what is going wrong here? I'd really like to use the 2.6 kernel
> on this machine.
Update http://bugs.debian.org/261824
> Thanks in advance,
Learn to use the Debian Bug Tracking System.
> Matt
Geert Stappers
pgpD6ZvJ1doi2.pgp
Description: PGP signature
Re: Sysrq via serial line?
On Thu, Sep 30, 2004 at 06:01:39PM +0100, Martin Habets wrote: > Hi, > > I'm using minicom to connect to a headless sparc running 2.6.8. > Have MAGIC_SYSRQ built into the kernel, but cannot find a way to trigger > it from the keyboard. echo into /proc/sysrq-trigger works fine. > > Sending a break gets me into openboot prompt. > > Have tried to use setkeycodes but it does not work for me. Initially > I had CONFIG_VT turned off, and setkeycodes gave: > Cannot get file desciptor for console > or something similar to that. > With CONFIG_VT turned on, but no keyboard support, I get: > KDSETKEYCODE: No such device > failed to set scancode 1b73 to keycode 84 > Turning on keyboard may help, but that's not right is it? I'm using a > serial port, not a keyboard. > > I'm using the sunzilog driver, but it seems to trigger sysrq after a > break signal in uart_handle_break(). But sendig a break gets me into > openboot. > > Is there a solution? Add hardware that can activate the sysrq line, like a keyboard. (CTRL-ALT-DEL is not in the ASCII table, ASCII is what a terminal sends) > > >From dmesg: > ttyS0 at MMIO 0x0 (irq = 44) is a SunZilog > > Thanks, My appology for saying "it can't be done" Geert Stappers pgpRd6h86xPMZ.pgp Description: PGP signature
Re: Serial Port problem on Ultra 2....
On Sat, Sep 25, 2004 at 08:17:35AM -0400, mark acierno wrote: > > On Sat, 25 Sep 2004 2:10:05 -0400, mark acierno wrote > (in message <[EMAIL PROTECTED]>): > > > I had a disasterous attempt at updating my SUN Ultra 2 to Sarge and thought > > I > > would attempt a clean install of 3.0 which was running nicely on my system > > up until a few days ago. I installed the os(3.0) with little problem - > > only > > now I cannot access the serial ports. If I run setserial it shows me that > > the > > uart is unknown, port is 0x f114, IRQ 704 > > if I attempt an autoconfig (in root) I get the error "Cannot set serial > > information : Invalid argument" . As a matter of fact ANY attempt to modify > > the ports is greeted by a similar error. Could someone point me as to > > where > > to look next for the source of my problem - and how to fix this > > > > > I attempted to reconfigure (dpkg-reconfigure) setserial but no matter what I > selected, I get the same error > > dpmod: *** unresolved symboles in lib/modules/2.4.18/kernel/fs/binfmt_elf.o > > anyone have thoughts? Think logical, write in the logical order. Is the kernel aware of the serial ports? (insmod?) > mark > > > > > > > thanx everyone ! > > Top quoter :/ > > mark Cheers Geert Stappers pgptObg5GxB3h.pgp Description: PGP signature
Re: Debian Sarge on Ultra 5
On Fri, Sep 24, 2004 at 09:25:55PM -0700, Herminder Sidhu wrote: > Hi, > > I'm trying to install debian on ultra sparc 5, but seem to be having > some issues with it. I used the Sarge install and it failed to > install silo then i decided to use the srage installer that is updated > daily and used the one for 09/25/04 but after it boot of the cd the > install refuses to mount the cdrom and fails there. > > Can some one please help me figure out what I could be doing differently? Tell which version of installer you are using. Telling more about the error is also helpfull. > Thanks, > > Herminder Cheers Geert Stappers pgpD3wDZf8rqI.pgp Description: PGP signature
Re: Ultra 5 silo installation problem
On Sat, Sep 18, 2004 at 10:56:18AM -0400, John Kerr Anderson wrote: > On Sat, 18 Sep 2004, Geert Stappers wrote: > > On Fri, Sep 17, 2004 at 09:07:19PM -0400, John Kerr Anderson wrote: > >> Hello, > >> > >> I'm trying to install Debian 3.0 on an Ultra 5. After installing the base > >> packages, the machine says that Silo will be installed, but it keeps on > >> failing. This is what it says: > >> > >> "Silo wasn't able to install. You'll still be able to boot your system if > >> you create a boot floppy, but it won't be able to boot without a floppy." > >> > >> I can't get the machine to create a boot disk either. I know the drive > >> works OK. > >> > >> Can anyone tell me what's wrong? The kernel version is 2.4.18. > >> Any help would be appreciated! > > > > At http://bugs.debian.org/271477 is succesfull report of an installation > > with the installer that will be used in in Debian 3.1. > > > > My advice is that you use the new Debian Installer. > > And I'm curious if you will encounter http://bugs.debian.org/267428 > > which is also about a "conflict" of Ultra 5 and silo. > > > >> Thanks in advace. > > Feedback is always good. > > > Hi, > > Thanks for the pointers, but I still think something is wrong. I created > a cd image from http://www.debian.org/devel/debian-installer/ the > installation went fine until once again, silo wouldn't install. It gave > me a silo error code of 1. I used the sarge debian installer image, > should I use one of the daily build images instead? Any help again would > be appreciated. :-) > Recently I saw a simular message. I adviced to follow the defaults of the Debian Installer [1] It was replied with "now it works". ((sorry)no details where included) > Any help again would be appreciated. :-) Feedback is allways welcome. > Cheers, > > John Cheers Geert Stappers [1] much of the research of d-i is in sane defaults P.S. Allow people that use the archive (Google is their friend) to read the text in the sequence as it was written. In otherwords: Please reply below the text pgpaLVNewe5di.pgp Description: PGP signature
Re: Ultra 5 silo installation problem
On Fri, Sep 17, 2004 at 09:07:19PM -0400, John Kerr Anderson wrote: > Hello, > > I'm trying to install Debian 3.0 on an Ultra 5. After installing the base > packages, the machine says that Silo will be installed, but it keeps on > failing. This is what it says: > > "Silo wasn't able to install. You'll still be able to boot your system if > you create a boot floppy, but it won't be able to boot without a floppy." > > I can't get the machine to create a boot disk either. I know the drive > works OK. > > Can anyone tell me what's wrong? The kernel version is 2.4.18. > Any help would be appreciated! At http://bugs.debian.org/271477 is succesfull report of an installation with the installer that will be used in in Debian 3.1. My advice is that you use the new Debian Installer. And I'm curious if you will encounter http://bugs.debian.org/267428 which is also about a "conflict" of Ultra 5 and silo. > Thanks in advace. Feedback is always good. > John Cheers Geert Stappers pgpnTObBNqNwL.pgp Description: PGP signature
