Re: silo problem?
On Wed, Oct 20, 2004 at 12:27:44PM +0200, Geert Stappers wrote: > Try to find out which program did report > "The file just load does not appear to be executable" The openboot firmware. (Which apparently thought that the silo bootloader was not bootable.) Admar
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
silo problem?
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? Best regards Admar
Re: Silo problem
On Sat, 9 Dec 2000, Antonio Musumeci wrote: > I installed silo on my sparc 10. However I get the following error on > boot: > > Read error on block 327684 > Cannot find /vmlinuz (Attempt to read block from filesystem resulted in > short read) > > any ideas? I had an older version of debian installed before this with > no problems. I descided to do a fresh install with the new stable and i > am having all kinds of problems. > You reinstalled?! I'm assuming you've reformatted your disks. Is your disk over 1G, if so does the kernel image lie inside the first gig? Can you boot it from a floppy or cdrom or network using the boot parameter; linux single root=/dev/"your root partition" , if that doesn't work try replacing single with -b. If that works, check your filesystem with e2fsck. If none of the above helps I hope you backed up. Good luck I'll be away for a week so I won't be able to help any further. Best Regards, Peter Firmstone. > > > -- > To UNSUBSCRIBE, email to [EMAIL PROTECTED] > with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED] > >
Silo problem
I installed silo on my sparc 10. However I get the following error on boot: Read error on block 327684 Cannot find /vmlinuz (Attempt to read block from filesystem resulted in short read) any ideas? I had an older version of debian installed before this with no problems. I descided to do a fresh install with the new stable and i am having all kinds of problems.
Silo Problem
I was trying to customize my silo.conf and screwed something up so I returned it to its original state as follows: partition=2 root=/dev/sda2 timeout=100 image=vmlinuz label=linux read-only but now when I reboot I get this SILO Syntax error in etc/silo.conf at "boot:" I try /vmlinuz root=/dev/sda2 or /boot/vmlinuz-2.0.35 root=/dev/sda2 and get Fatal error: Unable to open filesystem This setup worked before what else could I have changed to mess it up? I'm running Slink on an IPC, with Silo version 0.8.5. I've checked both /vmlinuz and /boot/vmlinuz-2.0.35 are present and spelled correctly. For now I have to boot off a floppy but I would like to fix this..help...
Re: SILO problem
[EMAIL PROTECTED] wrote: > Well I got the same problem and I have reported long ago without > getting any answers. But putting timeout=0 works for me (albeit that > this excludes dual boot). Here is my silo.conf file: timeout=0 *does* work for me. I must have flubbed something when I tried that before. Thanks for your help. -- Jeff Ebert [EMAIL PROTECTED]
Re: SILO problem
On Thu, Oct 29, 1998 at 10:36:16PM -0800, Jeffrey Ebert wrote: > I have a headless Sparc2, and I have succeeded in getting Debian running > on it. My problem is that the silo doesn't want to boot automatically. > It just sits there forever waiting for me to press the enter key. I > don't want to open the serial console every time I turn it on. I have > set the timeout to 0, removed the timeout line, tried various things > with the default= line, but nothing has worked. Any ideas? I'm going to upload this week-end, a new silo package. I'm using silo 0.8.1 and timeout works on my SS2. ciao -- [EMAIL PROTECTED] (PROSA srl) - [EMAIL PROTECTED] (Sparc Debian) PGP fingerprint = CD 8D A9 1E DB 0C B0 16 F8 2F BF 63 52 49 8B A8
SILO problem
Jeffrey Ebert writes: > I have a headless Sparc2, and I have succeeded in getting Debian running > on it. My problem is that the silo doesn't want to boot automatically. > It just sits there forever waiting for me to press the enter key. I > don't want to open the serial console every time I turn it on. I have > set the timeout to 0, removed the timeout line, tried various things > with the default= line, but nothing has worked. Any ideas? Well I got the same problem and I have reported long ago without getting any answers. But putting timeout=0 works for me (albeit that this excludes dual boot). Here is my silo.conf file: partition=1 root=/dev/sda1 #timeout=100 timeout=0 image=/vmlinuz label=Linux read-only --- PHAM Dinh Tuan | e-mail: [EMAIL PROTECTED] Laboratoire de Modelisation et Calcul | Tel: +33 4 76 51 44 23 BP 53, 38041 Grenoble cedex (France) | Fax: +33 4 76 63 12 63 ---
SILO problem
I have a headless Sparc2, and I have succeeded in getting Debian running on it. My problem is that the silo doesn't want to boot automatically. It just sits there forever waiting for me to press the enter key. I don't want to open the serial console every time I turn it on. I have set the timeout to 0, removed the timeout line, tried various things with the default= line, but nothing has worked. Any ideas? -- Jeff Ebert [EMAIL PROTECTED]
Silo problem, need help (fwd)
> hi, > > my name is arnold, and studying at the colorado university, > > I have a problem with Silo and am desperate for help, please help me > > I made a new .config file with the command make menuconfig. > All I added was support for a FAT filesystem, notthing else was changed. > Then I runned the following command: > make dep ; make clean ; make vmlinux ; make modules ; make > modules_install. > > seemed to work okay, just a view warnings > > I copied the new kernel in the boot directory and edited my silo.conf > correctly. > > I runned silo, and returned to runlevel 1 > there I did a fsck -p, and rebooted afterwards. > When I trie to reboot with the new kernel, it said: > "idle task may not sleep". > > have know idea how to solve this, > > hope you can help, thanks for the effort > > > -- > > > > Greetz from >>> > > > > /\ > /---arnold\ > \/ > | | > | | > \/ > > I'm not crazy, I'm a satellite > (design by Arnold v/d Lee) -- Eric Delaunay | "La guerre justifie l'existence des militaires. [EMAIL PROTECTED] | En les supprimant." Henri Jeanson (1900-1970) -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: silo problem
On Wed, 18 Feb 1998, Davide Barbieri wrote: > > 1) Modify the Makefile so the second stage bootloader no longer links with > > libc. Obviously, the userlevel "silo" utility needs to link with libc as > > usual. > > And how I can do this? silo is linked to libc, because it lacks a lot > of functions like str* and others... if I don't use libc, I had to > implement those functions on my own. Don't worry. I am working up patch for you right now. The files are all from arch/sparc/lib in the kernel source so they are all GPL'ed or LGPL'ed. Tom -- TO UNSUBSCRIBE FROM THIS MAILING LIST: e-mail the word "unsubscribe" to [EMAIL PROTECTED] . Trouble? e-mail to [EMAIL PROTECTED] .
Re: silo problem
And thus spake Davide Barbieri, on Wed, Feb 18, 1998 at 08:24:43AM +0100: > I'm not confident that I will able to do it :-) > > I had already try that way, but silo lacks these functions: > str* > mem* > ext2* > udiv, umul, urem and probably others... If you require having glibc around to build, you can just extract the object files you need from /usr/lib/libc.a using ar. You can then link silo using either a mini-libc you ar up from those, or just link directly with the object files. Or you could grab the source files from glibc. -- Elie Rosenblum That is not dead which can eternal lie, And with strange aeons even death may die. Developer / Mercenary / System Administrator - _The Necromicon_ -- TO UNSUBSCRIBE FROM THIS MAILING LIST: e-mail the word "unsubscribe" to [EMAIL PROTECTED] . Trouble? e-mail to [EMAIL PROTECTED] .
Re: silo problem
> Davide Barbieri writes:
Davide> Tom Dyas wrote:
>> >I'm still trying to have a silo working with glibc.
>> >
>> > I had some problems, with some assembler code.
>> >
>> > There is a file, called jmp.S which defines the symbol
>> > __setjmp, which is also defined in /usr/lib/libc.a
>> >
>> > So, when it is time to link silo, I had this error:
>> > /usr/lib/libc.a(setjmp.o): In function `_setjmp':
>> > setjmp.o(.text+0x0): multiple definition of `__setjmp'
>> > jmp.o(.text+0x0): first defined here
>> > make: *** [second] Error 1
>>
>> The problem is that the second stage bootloader links with libc to bring
>> in some minor functions like the strcmp and such. Ideally, it should be
>> linked without libc just like the kernel.
> [...]
Davide> BTW, isn't __setjmp already defined also in libc5?
Davide> (I haven't a libc5 system here)
All symbols starting with a underscore ("_") are reserved for internal
use of the C library by the ISO C standard. __setjmp might be defined
in libc5 but that's not relevant here. The bug is that silo uses a
_reserved_ identifier!
Either use setjmp completly from the C library or don't use the
library at all.
If you need all the str* function, just get them from glibc and
include them in silo. The sources are under the LGPL.
Andreas
--
Andreas Jaeger [EMAIL PROTECTED][EMAIL PROTECTED]
for pgp-key finger [EMAIL PROTECTED]
--
TO UNSUBSCRIBE FROM THIS MAILING LIST: e-mail the word "unsubscribe" to
[EMAIL PROTECTED] .
Trouble? e-mail to [EMAIL PROTECTED] .
Re: silo problem
Tom Dyas wrote: > >I'm still trying to have a silo working with glibc. > > > > I had some problems, with some assembler code. > > > > There is a file, called jmp.S which defines the symbol > > __setjmp, which is also defined in /usr/lib/libc.a > > > > So, when it is time to link silo, I had this error: > > /usr/lib/libc.a(setjmp.o): In function `_setjmp': > > setjmp.o(.text+0x0): multiple definition of `__setjmp' > > jmp.o(.text+0x0): first defined here > > make: *** [second] Error 1 > > The problem is that the second stage bootloader links with libc to bring > in some minor functions like the strcmp and such. Ideally, it should be > linked without libc just like the kernel. Ideally. Yes, but, as you said, it bring in some minor functions. > Linking with libc gets into conflicts just like you encountered. The fix > is as follows: > > 1) Modify the Makefile so the second stage bootloader no longer links with > libc. Obviously, the userlevel "silo" utility needs to link with libc as > usual. And how I can do this? silo is linked to libc, because it lacks a lot of functions like str* and others... if I don't use libc, I had to implement those functions on my own. > 2) Add implementations of any functions that become "missing". I'm not confident that I will able to do it :-) I had already try that way, but silo lacks these functions: str* mem* ext2* udiv, umul, urem and probably others... BTW, isn't __setjmp already defined also in libc5? (I haven't a libc5 system here) thanks Ciao -- Davide Barbieri - [EMAIL PROTECTED] - [EMAIL PROTECTED] (Sparc Debian) PGP fingerprint = CD 8D A9 1E DB 0C B0 16 F8 2F BF 63 52 49 8B A8 -- TO UNSUBSCRIBE FROM THIS MAILING LIST: e-mail the word "unsubscribe" to [EMAIL PROTECTED] . Trouble? e-mail to [EMAIL PROTECTED] .
Re: silo problem
On Tue, 17 Feb 1998, Davide Barbieri wrote: > I'm still trying to have a silo working with glibc. > > I had some problems, with some assembler code. > > There is a file, called jmp.S which defines the symbol > __setjmp, which is also defined in /usr/lib/libc.a > > So, when it is time to link silo, I had this error: > /usr/lib/libc.a(setjmp.o): In function `_setjmp': > setjmp.o(.text+0x0): multiple definition of `__setjmp' > jmp.o(.text+0x0): first defined here > make: *** [second] Error 1 The problem is that the second stage bootloader links with libc to bring in some minor functions like the strcmp and such. Ideally, it should be linked without libc just like the kernel. Linking with libc gets into conflicts just like you encountered. The fix is as follows: 1) Modify the Makefile so the second stage bootloader no longer links with libc. Obviously, the userlevel "silo" utility needs to link with libc as usual. 2) Add implementations of any functions that become "missing". Jakub, what do you think? Tom -- TO UNSUBSCRIBE FROM THIS MAILING LIST: e-mail the word "unsubscribe" to [EMAIL PROTECTED] . Trouble? e-mail to [EMAIL PROTECTED] .
silo problem
Ciao, I'm still trying to have a silo working with glibc. I had some problems, with some assembler code. There is a file, called jmp.S which defines the symbol __setjmp, which is also defined in /usr/lib/libc.a So, when it is time to link silo, I had this error: /usr/lib/libc.a(setjmp.o): In function `_setjmp': setjmp.o(.text+0x0): multiple definition of `__setjmp' jmp.o(.text+0x0): first defined here make: *** [second] Error 1 This is the jmp.S file: /* setjmp/longjmp code [skipping copyright statement] */ #define _SV save %sp, -0x40, %sp #define _RV restore #define FLUSH_ALL_WINDOWS \ _SV; _SV; _SV; _SV; _SV; _SV; _SV; \ _RV; _RV; _RV; _RV; _RV; _RV; _RV; /* Save our return PC and SP. */ .global __setjmp, setjmp setjmp: __setjmp: st %o7, [%o0] st %sp, [%o0 + 4] retl clr %o0 .global __longjmp, longjmp longjmp: __longjmp: /* Flush register windows. Write all the register windows to their stack slots, and mark them all as invalid (needing to be sucked up from the stack when used). This ensures that all information needed to unwind to these callers is in memory, not in the register windows. */ FLUSH_ALL_WINDOWS ld [%o0], %o7 /* Return PC. */ ld [%o0 + 4], %fp /* Saved SP. */ sub %fp, 64, %sp/* Allocate a register save area. */ tst %o1 be,a 1f mov 1, %o1 1: retl /* On the way out, put the return value in %o0. */ restore %o1, 0, %o0 So, what I have to do? I can change the symbol in jmp.S, but I got a warning: BFD: sta13957: warning: allocated section `.bss' not in segment anyway, it compiles succesfully, but it doesn't work [EMAIL PROTECTED]> ./silo Fatal: cannot read superblock on /dev/sd (READ_ONLY) even if I'm root. Any help, would be appreciated. Thanks -- Davide Barbieri - [EMAIL PROTECTED] - [EMAIL PROTECTED] (Sparc Debian) PGP fingerprint = CD 8D A9 1E DB 0C B0 16 F8 2F BF 63 52 49 8B A8 -- Davide Barbieri - [EMAIL PROTECTED] - [EMAIL PROTECTED] (Sparc Debian) PGP fingerprint = CD 8D A9 1E DB 0C B0 16 F8 2F BF 63 52 49 8B A8 -- TO UNSUBSCRIBE FROM THIS MAILING LIST: e-mail the word "unsubscribe" to [EMAIL PROTECTED] . Trouble? e-mail to [EMAIL PROTECTED] .
