: CPU refactoring status....
The hardwaremain become more tidy.
How about the progress about the romcc? I hope I can enable debug info while
include all ati support stuff.
Regards
YH
--
: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]
: 200477 21:03
: LinuxBIOS
: YhLu; ron minnich; Stefan Reinauer
: Re: CPU refactoring status
[EMAIL PROTECTED] (Eric W. Biederman) writes:
The next big task is to get make the SMP cpu initialization methods
normal device tree methods. I have everything ready to do that
except I need a good way to get the information in the struct
mem_range array by sizeram(). My gut feel is that I want to
incorporate the sizeram functionality into the resource allocator,
Moving sizeram into read_resources/set_resources comes out fairly
clean, but it did require some grunt work.
That has allowed me to sort out the device tree and have a fairly
generic method of initializing cpus. Cpus don't fit into device
model methods as nicely as I would like (largely because their
methods have to run on the cpu in question). But it does work
well enough I can remove the special case from hardwaremain.
I still have a special case in the root_device methods but
that can be overridden, if necessary.
Because I have restructured where things fall in the device tree.
Because I have removed the sizeram call.
Because I have refactored x86 cpu handling.
Because I have removed the array initial_apic_id.
Every port in the tree is likely to break when I check this code in.
I have the arima/hdama working and I can with a little care
fix up the k8 based ports.
I can also likely fixup the recent e7501 forward port from the
freebios tree.
However beyond that I don't have testing resources to fix things up
so I am looking for some feedback before I break everything.
When in the next week or so is a good time?
Does any one have concerns about this set of changes?
I have attached my current version of hardwaremain below
to give a feel of what the changes look like.
Ok now I am off to bed. Before I commit anything I am going to let
the code sit a little.
Good Night,
Eric
/*
* C Bootstrap code for the LinuxBIOS
*/
#include console/console.h
#include mem.h
#include version.h
#include boot/tables.h
#include device/device.h
#include device/pci.h
#include device/chip.h
#include delay.h
#include stdlib.h
#include part/hard_reset.h
#include boot/elf.h
void hardwaremain(int boot_complete)
{
/* the order here is a bit tricky. We don't want to do much of
* anything that uses config registers until after
PciAllocateResources
* since that function also figures out what kind of config strategy
* to use (type 1 or type 2).
* so we turn on cache, then worry about PCI setup, then do other
* things, so that the other work can use the PciRead* and PciWrite*
* functions.
*/
struct lb_memory *lb_mem;
post_code(0x80);
CONFIGURE(CONF_PASS_PRE_CONSOLE);
/* displayinit MUST PRECEDE ALL PRINTK! */
console_init();
post_code(0x39);
printk_notice(LinuxBIOS-%s%s %s %s...\n,
linuxbios_version, linuxbios_extra_version, linuxbios_build,
(boot_complete)?rebooting:booting);
post_code(0x40);
/* If we have already booted attempt a hard reboot */
if (boot_complete) {
hard_reset();
}
init_timer(); /* needs to be moved into static configuration */
CONFIGURE(CONF_PASS_PRE_PCI);
/* pick how to scan the bus. This is first so we can get at memory
size. */
printk_info(Finding PCI configuration type.\n);
pci_set_method();
post_code(0x5f);
enumerate_static_devices();
dev_enumerate();
post_code(0x66);
/* Now do the real bus.
* We round the total ram up a lot for thing like the SISFB, which
* shares high memory with the CPU.
*/
dev_configure();
post_code(0x88);
dev_enable();
dev_initialize();
post_code(0x89);
CONFIGURE(CONF_PASS_POST_PCI);
/* Now that we have collected all of our information
* write our configuration tables.
*/
lb_mem = write_tables();
CONFIGURE(CONF_PASS_PRE_BOOT);
elfboot(lb_mem);
}
___
Linuxbios mailing list
[EMAIL PROTECTED]
http://www.clustermatic.org/mailman/listinfo/linuxbios
Linux bios and IBM Netvista 8363-EXX
Hello I'm curious if a IBM thin client (8363-EXX or Netvista 2200) can use linuxbios? Thanks for any info ___ Linuxbios mailing list [EMAIL PROTECTED] http://www.clustermatic.org/mailman/listinfo/linuxbios
Re: : CPU refactoring status....
YhLu [EMAIL PROTECTED] writes: The hardwaremain become more tidy. How about the progress about the romcc? I hope I can enable debug info while include all ati support stuff. The major bug that was causing the core dump is fixed. As far as improving the optimizations things are working well enough it is not killing me at the moment. At this point I feel more urgency for getting the APIs in the freebios2 tree to the point where we can comfortably freeze them. Thinking about it size is a significant factor so if I can't reduce the about of inlining in romcc we have some structural changes that are needed at least on x86. So that needs to come before a final freeze as well. YHLu your mailer currently breaks threads, because it does include a references line for older messages. Could see if that can be fixed? It makes it hard to keep all of the pieces of a conversation together. Eric ___ Linuxbios mailing list [EMAIL PROTECTED] http://www.clustermatic.org/mailman/listinfo/linuxbios
Re: Linux bios and IBM Netvista 8363-EXX
we can't tell without knowing what the chipset is. ron ___ Linuxbios mailing list [EMAIL PROTECTED] http://www.clustermatic.org/mailman/listinfo/linuxbios
Re: freebios1 sis-kernel_patch for 2.6
On Thursday 08 July 2004 16:53, Li-Ta Lo wrote: I can't help him with the 2.6 frame buffer neither. That driver is based on the official framebuffer driver released by SiS long time ago. It uses register table from vga bios image so there is a lot of code doing table parsing. It is totally beyond my knowledge. Unfortunately, that driver is not maintained by SiS any more. You probably should ask the independent maintainer Thomas Winischhofer http://www.winischhofer.net/ Ollie But after setting the videomode with fbset (the same mode that should be set after booting) framebuffer works. So i hoped it can't be that difficult. Are you sure about the official SiS driver? For me the 2.6 SiS driver seem to be nearly the same Thomas Winischhofer released on his site. And he stated that he had no help from SiS. Thomas ___ Linuxbios mailing list [EMAIL PROTECTED] http://www.clustermatic.org/mailman/listinfo/linuxbios
Filo Error Help
Hello, I'm using Linux BIOS with etherboot-filo. I have a usb stick has a kernel and a usb aware initrd on it. The problem I am having is when I use etherboot-filo to boot off of uba1:/boot/vmlinuz initrd=/boot/initrd root=/dev/sda1 console=tty0 console=ttyS0,115200. I get this: Mounted reiserfs Found Linux version 2.6.6 ([EMAIL PROTECTED]) #3 SMP Thu Jul 8 09:25:46 EDT 2004 bzImage. Loading kernel... ok Loading initrd... dma_to_td: can not find td dma_to_td: can not find td dma_to_td: can not find td dma_to_td: can not find td dma_to_td: can not find td Disk read error dev_type=3 drive=0 sector=00046d9d dma_to_td: can not find td dma_to_td: can not find td dma_to_td: can not find td Disk read error dev_type=3 drive=0 sector=00046da1 dma_to_td: can not find td dma_to_td: can not find td dma_to_td: can not find td Disk read error dev_type=3 drive=0 sector=00046da9 dma_to_td: can not find td dma_to_td: can not find td dma_to_td: can not find td Disk read error dev_type=3 drive=0 sector=00046db1 dma_to_td: can not find td dma_to_td: can not find td dma_to_td: can not find td Disk read error dev_type=3 drive=0 sector=00046db9 dma_to_td: can not find td dma_to_td: can not find td dma_to_td: can not find td Disk read error dev_type=3 drive=0 sector=00046dc1 dma_to_td: can not find td dma_to_td: can not find td dma_to_td: can not find td Disk read error dev_type=3 drive=0 sector=00046dc9 dma_to_td: can not find td dma_to_td: can not find td dma_to_td: can not find td Disk read error dev_type=3 drive=0 sec Ultimately I get this invalid image: ide1 at 0x170-0x177,0x376 on irq 15 ide-floppy driver 0.99.newide mice: PS/2 mouse device common for all mice serio: i8042 AUX port at 0x60,0x64 irq 12 serio: i8042 KBD port at 0x60,0x64 irq 1 md: linear personality registered as nr 1 md: raid0 personality registered as nr 2 md: raid1 personality registered as nr 3 md: raid5 personality registered as nr 4 raid5: measuring checksumming speed generic_sse: 5996.000 MB/sec raid5: using function: generic_sse (5996.000 MB/sec) raid6: int64x1 1656 MB/s raid6: int64x2 2390 MB/s raid6: int64x4 2585 MB/s raid6: int64x8 1750 MB/s raid6: sse2x12351 MB/s raid6: sse2x23367 MB/s raid6: sse2x43578 MB/s raid6: using algorithm sse2x4 (3578 MB/s) md: raid6 personality registered as nr 8 md: multipath personality registered as nr 7 md: md driver 0.90.0 MAX_MD_DEVS=256, MD_SB_DISKS=27 device-mapper: 4.1.0-ioctl (2003-12-10) initialised: [EMAIL PROTECTED] NET: Registered protocol family 2 IP: routing cache hash table of 2048 buckets, 32Kbytes TCP: Hash tables configured (established 65536 bind 65536) NET: Registered protocol family 1 Bluetooth: L2CAP ver 2.1 Bluetooth: L2CAP socket layer initialized Bluetooth: SCO (Voice Link) ver 0.3 Bluetooth: SCO socket layer initialized Bluetooth: RFCOMM ver 1.2 Bluetooth: RFCOMM socket layer initialized Bluetooth: RFCOMM TTY layer initialized Bluetooth: BNEP (Ethernet Emulation) ver 1.0 Bluetooth: BNEP filters: protocol multicast md: Autodetecting RAID arrays. md: autorun ... md: ... autorun DONE. RAMDISK: Compressed image found at block 0 invalid compressed format (err=2) Root-NFS: No NFS server available, giving up. VFS: Unable to mount root fs via NFS, trying floppy. VFS: Insert root floppy and press ENTER I've also placed an elf image of the kernel intird, but it too failed, but it seemed to fail in not even seeing the initrd bundled in the elf. This same elf works fine in etherboot. Any sugestions? Thanks, Dave ___ Linuxbios mailing list [EMAIL PROTECTED] http://www.clustermatic.org/mailman/listinfo/linuxbios
Re: freebios1 sis-kernel_patch for 2.6
On Thu, 2004-07-08 at 14:39, Thomas Wehrspann wrote: On Thursday 08 July 2004 16:53, Li-Ta Lo wrote: I can't help him with the 2.6 frame buffer neither. That driver is based on the official framebuffer driver released by SiS long time ago. It uses register table from vga bios image so there is a lot of code doing table parsing. It is totally beyond my knowledge. Unfortunately, that driver is not maintained by SiS any more. You probably should ask the independent maintainer Thomas Winischhofer http://www.winischhofer.net/ Ollie But after setting the videomode with fbset (the same mode that should be set after booting) framebuffer works. So i hoped it can't be that difficult. I got that problem for my SiSFB Lite too. On some version of the VGA core, it take two set modes to actually set the hardware to the correct vide mode. Probably you can try the same trick. Are you sure about the official SiS driver? For me the 2.6 SiS driver seem to be nearly the same Thomas Winischhofer released on his site. And he stated that he had no help from SiS. He based his code on a very old official SiS release. SiS lost their interest in supporting that stuff after a few public releases and pretty much abandoned it. I am really amazed that he could figure out their code without any support from SiS (and persisted for such a long period). Ollie ___ Linuxbios mailing list [EMAIL PROTECTED] http://www.clustermatic.org/mailman/listinfo/linuxbios
RE: Filo Error Help
1. which MB? Which USB stick 2. please try .elf at first. It would be uda1:/ram0_2.5_2.6.5_k8.2_mydisk7.elf format your usb disk with FAT or ext2, because it seems reiserfs driver has some problem, and it will not work after abnormal shutdown. 3. I guess td is not be freed right after use. Regards YH ___ Linuxbios mailing list [EMAIL PROTECTED] http://www.clustermatic.org/mailman/listinfo/linuxbios
Re: CPU refactoring status....
ron minnich [EMAIL PROTECTED] writes: Eric, would it make sense for you to send a few of us the tree so we can take a look and see what it will involve? I'm concerned about the EPIA port. i'd like to take a week or two on this if needed to make sure we are all good on it. It looks like a very useful set of changes. Thinking about this some more. I think what makes the most sense is for me to create a branch on of the freebios2 tree and check the code in there. That way everyone will have access to it, but nothing will immediately break. Then we can take and merge everything into the mainline once the code reviews and whatever are completed. I need to purge the nda bits from my tree before I give it to anyone, anyway. Ron does a branch sound good? Eric ___ Linuxbios mailing list [EMAIL PROTECTED] http://www.clustermatic.org/mailman/listinfo/linuxbios
RE: Filo Error Help
On Thu, 2004-07-08 at 17:11, YhLu wrote: 1. which MB? Which USB stick 2. please try .elf at first. It would be uda1:/ram0_2.5_2.6.5_k8.2_mydisk7.elf format your usb disk with FAT or ext2, because it seems reiserfs driver has some problem, and it will not work after abnormal shutdown. 3. I guess td is not be freed right after use. Regards YH Hi, 1. I'm using a S2885 chipset motherboard by Tyan;) I'm using a Kingston 2.0 stick. 2. At the bottom of my original post I mention I did the elf as well. Did your elf include an initrd? If so could it be a size issue? My initrd is 8Meg. 3. Can you point me as to how to remedy this? Thanks, Dave
RE: Filo Error Help
How about the size of the elf? YH -Original Message- From: David Aubin [mailto:[EMAIL PROTECTED] Sent: Thursday, July 08, 2004 2:27 PM To: YhLu Cc: LinuxBIOS Subject: RE: Filo Error Help Hi, 1. I'm using a S2885 chipset motherboard by Tyan;) I'm using a Kingston 2.0 stick. 2. At the bottom of my original post I mention I did the elf as well. Did your elf include an initrd? If so could it be a size issue? My initrd is 8Meg. 3. Can you point me as to how to remedy this? Thanks, Dave On Thu, 2004-07-08 at 17:25, David Aubin wrote: On Thu, 2004-07-08 at 17:11, YhLu wrote: 1. which MB? Which USB stick 2. please try .elf at first. It would be uda1:/ram0_2.5_2.6.5_k8.2_mydisk7.elf format your usb disk with FAT or ext2, because it seems reiserfs driver has some problem, and it will not work after abnormal shutdown. 3. I guess td is not be freed right after use. Regards YH Hi, 1. I'm using a S2885 chipset motherboard by Tyan;) I'm using a Kingston 2.0 stick. 2. At the bottom of my original post I mention I did the elf as well. Did your elf include an initrd? If so could it be a size issue? My initrd is 8Meg. 3. Can you point me as to how to remedy this? Thanks, Dave ___ Linuxbios mailing list [EMAIL PROTECTED] http://www.clustermatic.org/mailman/listinfo/linuxbios
Re: CPU refactoring status....
On 8 Jul 2004, Eric W. Biederman wrote: Ron does a branch sound good? works for me! ron ___ Linuxbios mailing list [EMAIL PROTECTED] http://www.clustermatic.org/mailman/listinfo/linuxbios
RE: Filo Error Help
I could send you my elf, but it is about 6Mb. YH -Original Message- From: ron minnich [mailto:[EMAIL PROTECTED] Sent: Thursday, July 08, 2004 2:42 PM To: David Aubin Cc: YhLu; LinuxBIOS Subject: Re: Filo Error Help On Thu, 8 Jul 2004, David Aubin wrote: RAMDISK: Compressed image found at block 0 well if found the image ... invalid compressed format (err=2) this is odd. you've got linux up, and it found an image, but it seems busted. Are you certain this initrd is ok? You could try booting the kernel and initrd on a known-good system to make sure the initrd is right. Do you have the right VFS for the initrd build into the kernel? ron ___ Linuxbios mailing list [EMAIL PROTECTED] http://www.clustermatic.org/mailman/listinfo/linuxbios
RE: Filo Error Help
The size of the elf is: ls -la boot.elf -r--r--r--1 daubin users 4059015 2004-07-08 17:46 boot.elf Dave On Thu, 2004-07-08 at 17:38, YhLu wrote: How about the size of the elf? YH -Original Message- From: David Aubin [mailto:[EMAIL PROTECTED] Sent: Thursday, July 08, 2004 2:27 PM To: YhLu Cc: LinuxBIOS Subject: RE: Filo Error Help Hi, 1. I'm using a S2885 chipset motherboard by Tyan;) I'm using a Kingston 2.0 stick. 2. At the bottom of my original post I mention I did the elf as well. Did your elf include an initrd? If so could it be a size issue? My initrd is 8Meg. 3. Can you point me as to how to remedy this? Thanks, Dave On Thu, 2004-07-08 at 17:25, David Aubin wrote: On Thu, 2004-07-08 at 17:11, YhLu wrote: 1. which MB? Which USB stick 2. please try .elf at first. It would be uda1:/ram0_2.5_2.6.5_k8.2_mydisk7.elf format your usb disk with FAT or ext2, because it seems reiserfs driver has some problem, and it will not work after abnormal shutdown. 3. I guess td is not be freed right after use. Regards YH Hi, 1. I'm using a S2885 chipset motherboard by Tyan;) I'm using a Kingston 2.0 stick. 2. At the bottom of my original post I mention I did the elf as well. Did your elf include an initrd? If so could it be a size issue? My initrd is 8Meg. 3. Can you point me as to how to remedy this? Thanks, Dave ___ Linuxbios mailing list [EMAIL PROTECTED] http://www.clustermatic.org/mailman/listinfo/linuxbios
RE: Filo Error Help
I wonder if it is after gzip or before gzip. -Original Message- From: ron minnich [mailto:[EMAIL PROTECTED] Sent: Thursday, July 08, 2004 2:44 PM To: David Aubin Cc: YhLu; LinuxBIOS Subject: RE: Filo Error Help On Thu, 8 Jul 2004, David Aubin wrote: If so could it be a size issue? My initrd is 8Meg. oh! did you config the kernel for that? default is 4M. ron ___ Linuxbios mailing list [EMAIL PROTECTED] http://www.clustermatic.org/mailman/listinfo/linuxbios
Re: Filo Error Help
This exact same elf boots up fine with etherboot. In fact I have etherboot-filo configured to boot off of the net and it grabs this elf and boots the system well. But when I use USB and this same elf, it gets a crc error during the initrd portion. It loads the kernel fine though. Dave On Thu, 2004-07-08 at 17:41, ron minnich wrote: On Thu, 8 Jul 2004, David Aubin wrote: RAMDISK: Compressed image found at block 0 well if found the image ... invalid compressed format (err=2) this is odd. you've got linux up, and it found an image, but it seems busted. Are you certain this initrd is ok? You could try booting the kernel and initrd on a known-good system to make sure the initrd is right. Do you have the right VFS for the initrd build into the kernel? ron ___ Linuxbios mailing list [EMAIL PROTECTED] http://www.clustermatic.org/mailman/listinfo/linuxbios
RE: Filo Error Help
Your self consists of a kernel and initrd correct? Made with Eric's mkelfImage2-5? On Thu, 2004-07-08 at 17:49, YhLu wrote: I could send you my elf, but it is about 6Mb. YH -Original Message- From: ron minnich [mailto:[EMAIL PROTECTED] Sent: Thursday, July 08, 2004 2:42 PM To: David Aubin Cc: YhLu; LinuxBIOS Subject: Re: Filo Error Help On Thu, 8 Jul 2004, David Aubin wrote: RAMDISK: Compressed image found at block 0 well if found the image ... invalid compressed format (err=2) this is odd. you've got linux up, and it found an image, but it seems busted. Are you certain this initrd is ok? You could try booting the kernel and initrd on a known-good system to make sure the initrd is right. Do you have the right VFS for the initrd build into the kernel? ron
RE: Filo Error Help
Hi, With your elf I get the following: boot: uda1:/ram0_2.5_2.6.5_k8.2_mydisk7.elf LinuxLabs USB bootloader New USB device, setting address 2 0008:0006:0050 Manufacturor: Kingston Product: DataTraveler2.0 Serial: 07B1F140E000617B Found USB block device 2 Mounted reiserfs errnum=15 boot: uda1:/ram.elf Loading Linux version 2.6.5 ([EMAIL PROTECTED]) #11 SMP Mon May 10 14:58:17 PDT 2004... Jumping to entry point... DFA Just before C's xstart32 Firmware type: LinuxBIOS old bootloader convention, maybe loadlin? Bootdata ok (command line is root=/dev/ram0 rw console=tty0 console=ttyS0,115200n8) . . RAMDISK driver initialized: 16 RAM disks of 16384K size 1024 blocksize loop: loaded (max 8 devices) . . usb 2-3: new full speed USB device using address 2 scsi4 : SCSI emulation for USB Mass Storage devices Vendor: Kingston Model: DataTraveler2.0 Rev: 4.70 Type: Direct-Access ANSI SCSI revision: 02 SCSI device sda: 1019392 512-byte hdwr sectors (522 MB) sda: assuming Write Enabled sda: assuming drive cache: write through sda: sda1 Attached scsi removable disk sda at scsi4, channel 0, id 0, lun 0 NET: Registered protocol family 2 IP: routing cache hash table of 2048 buckets, 32Kbytes TCP: Hash tables configured (established 65536 bind 65536) NET: Registered protocol family 1 NET: Registered protocol family 17 RAMDISK: Compressed image found at block 0 RAMDISK: incomplete write (-28 != 1) 16777216 crc error EXT2-fs warning: mounting unchecked fs, running e2fsck is recommended VFS: Mounted root (ext2 filesystem). Freeing unused kernel memory: 472k freed Kernel panic: No init found. Try passing init= option to kernel. This makes me feel a little better as it appears it is something in my etherboot-filo configuration perhaps? On Thu, 2004-07-08 at 17:53, YhLu wrote: I wonder if it is after gzip or before gzip. -Original Message- From: ron minnich [mailto:[EMAIL PROTECTED] Sent: Thursday, July 08, 2004 2:44 PM To: David Aubin Cc: YhLu; LinuxBIOS Subject: RE: Filo Error Help On Thu, 8 Jul 2004, David Aubin wrote: If so could it be a size issue? My initrd is 8Meg. oh! did you config the kernel for that? default is 4M. ron ___ Linuxbios mailing list [EMAIL PROTECTED] http://www.clustermatic.org/mailman/listinfo/linuxbios
RE: Filo Error Help
Looks more like a Linux config problem. Double check your /etc/fstab and make sure the root partition entry is correct and that you have virtual terminal (VT) support enabled in your kernel. On Thu, 8 Jul 2004, David Aubin wrote: Hi, With your elf I get the following: boot: uda1:/ram0_2.5_2.6.5_k8.2_mydisk7.elf LinuxLabs USB bootloader New USB device, setting address 2 0008:0006:0050 Manufacturor: Kingston Product: DataTraveler2.0 Serial: 07B1F140E000617B Found USB block device 2 Mounted reiserfs errnum=15 boot: uda1:/ram.elf Loading Linux version 2.6.5 ([EMAIL PROTECTED]) #11 SMP Mon May 10 14:58:17 PDT 2004... Jumping to entry point... DFA Just before C's xstart32 Firmware type: LinuxBIOS old bootloader convention, maybe loadlin? Bootdata ok (command line is root=/dev/ram0 rw console=tty0 console=ttyS0,115200n8) . . RAMDISK driver initialized: 16 RAM disks of 16384K size 1024 blocksize loop: loaded (max 8 devices) . . usb 2-3: new full speed USB device using address 2 scsi4 : SCSI emulation for USB Mass Storage devices Vendor: Kingston Model: DataTraveler2.0 Rev: 4.70 Type: Direct-Access ANSI SCSI revision: 02 SCSI device sda: 1019392 512-byte hdwr sectors (522 MB) sda: assuming Write Enabled sda: assuming drive cache: write through sda: sda1 Attached scsi removable disk sda at scsi4, channel 0, id 0, lun 0 NET: Registered protocol family 2 IP: routing cache hash table of 2048 buckets, 32Kbytes TCP: Hash tables configured (established 65536 bind 65536) NET: Registered protocol family 1 NET: Registered protocol family 17 RAMDISK: Compressed image found at block 0 RAMDISK: incomplete write (-28 != 1) 16777216 crc error EXT2-fs warning: mounting unchecked fs, running e2fsck is recommended VFS: Mounted root (ext2 filesystem). Freeing unused kernel memory: 472k freed Kernel panic: No init found. Try passing init= option to kernel. This makes me feel a little better as it appears it is something in my etherboot-filo configuration perhaps? On Thu, 2004-07-08 at 17:53, YhLu wrote: I wonder if it is after gzip or before gzip. -Original Message- From: ron minnich [mailto:[EMAIL PROTECTED] Sent: Thursday, July 08, 2004 2:44 PM To: David Aubin Cc: YhLu; LinuxBIOS Subject: RE: Filo Error Help On Thu, 8 Jul 2004, David Aubin wrote: If so could it be a size issue? My initrd is 8Meg. oh! did you config the kernel for that? default is 4M. ron ___ Linuxbios mailing list [EMAIL PROTECTED] http://www.clustermatic.org/mailman/listinfo/linuxbios ___ Linuxbios mailing list [EMAIL PROTECTED] http://www.clustermatic.org/mailman/listinfo/linuxbios
