From: Brunet Eric <rickos@ifrance.com>
To: linux-kernel@vger.kernel.org
Cc: eric.brunet@voila.fr
Subject: compile and bootdisk problems
Date: Fri, 13 Jul 2001 18:38:45 +0200 [thread overview]
Message-ID: <3B4F2415.559A12D9@ifrance.com> (raw)
Hello,
i meet some problems in order to create a linux bootdisk:
therefore, i tries to make a polyvalent kernel (in one floppy) with:
-no module
-a lot of ethernet card drivers
This flopppy disk will be used to boot windows machine with partimage
program in order to backup entire FS to a backup server!!
The first, i couldn't compile the kernel with all ethernets card
drivers, specially i have an errors for the drivers
"CONFIG_ARM_AM79C961A" and "CONFIG_FEALNX" for kernels 2.4.3 and 2.4.6(i
think others version too), is it normal??
For "CONFIG_ARM_AM79C961A":
am79c961a.c: In function `am79c961_init':
am79c961a.c:638: `IRQ_EBSA110_ETHERNET' undeclared (first use in this
function)
am79c961a.c:638: (Each undeclared identifier is reported only once
am79c961a.c:638: for each function it appears in.)
make[3]: *** [am79c961a.o] Erreur 1
make[2]: *** [first_rule] Erreur 2
make[1]: *** [_subdir_net] Erreur 2
make: *** [_dir_drivers] Erreur 2
notice: the definition of IRQ_EBSA110_ETHERNET is in ./include/asm_arm
# define IRQ_EBSA110_ETHERNET 3
I understand that device is supported only by arm architecure, it don't
compile because it's a x86 machine?? and if yes,why aren't anywarning
message to indicate me that drivers is useless????
For "CONFIG_FEALNX":
gcc -D__KERNEL__ -I/usr/src/linux-2.4.6/include -Wall
-Wstrict-prototypes -Wno-trigraphs -O2 -fomit-frame-pointer
-fno-strict-aliasing -pipe -mpreferred-stack-boundary=2 -march=i686
-c -o fealnx.o fealnx.c
fealnx.c:1817: parse error before `__attribute__'
make[3]: *** [fealnx.o] Erreur 1
make[3]: Quitte le répertoire `/usr/src/linux-2.4.6/drivers/net'
make[2]: *** [first_rule] Erreur 2
make[2]: Quitte le répertoire `/usr/src/linux-2.4.6/drivers/net'
make[1]: *** [_subdir_net] Erreur 2
make[1]: Quitte le répertoire `/usr/src/linux-2.4.6/drivers'
make: *** [_dir_drivers] Erreur 2
-the other problem is in boot sequence, i prapre the kernel image for
the rootdisk(it work with a Slackware bootdisk) like this:
> rdev bzImage /dev/fd0
> rdev -r bzImage 49152 (49152 = ask disk, and read from 0)
> rdev -R bzImage 0 (to make the root RW and allow to login)
> dd if=bzImage of=/dev/fd0 bs=1k
howener then i insert root disk, 10 second oafter, i see this message:
>wrong magic
>MSDOS: Harware sector size is 1024
>fatfs: bogus cluster size
>MSDOS: Harware sector size is 1024
>fatfs: bogus cluster size
>MSDOS: Harware sector size is 1024
>fatfs: bogus cluster size
>UMSDOS: msdos_read_super failed, mount aborted.
>kernel panic: VFS: Unable to mount fs on 01:00
I read many FAQ, ML and bootdisk HOWTO(of course) wtihout response
please help me :~(
:))I
thank in advance for your response
______________________________________________________________________________
ifrance.com, l'email gratuit le plus complet de l'Internet !
vos emails depuis un navigateur, en POP3, sur Minitel, sur le WAP...
http://www.ifrance.com/_reloc/email.emailif
next reply other threads:[~2001-07-13 16:38 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-07-13 16:38 Brunet Eric [this message]
2001-07-13 17:03 ` compile and bootdisk problems Ignacio Vazquez-Abrams
-- strict thread matches above, loose matches on Subject: below --
2001-07-13 16:58 Colin Bayer
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=3B4F2415.559A12D9@ifrance.com \
--to=rickos@ifrance.com \
--cc=eric.brunet@voila.fr \
--cc=linux-kernel@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox