From scheng at msica.com Mon Jul 5 18:58:01 2004 From: scheng at msica.com (scheng at msica.com) Date: Mon Jul 5 18:58:01 2004 Subject: A bug was found in freebios2/src/northbridge/via/vt8601/raminit.c Message-ID: <63235.24.87.201.99.1089073650.squirrel@www.nome.ca> I am trying to use LinuxBIOS V2 + Filo to boot local Linux on hard disk (EPIA 800 board). I found that LinuxBIOS executes an infinite loop in dumpnorth() function of freebios2/src/northbridge/via/vt8601/raminit.c . The function is: void dumpnorth(device_t north) { uint8_t r, c; for(r = 0; r < 256; r += 16) { print_debug_hex8(r); print_debug(":"); for(c = 0; c < 16; c++) { print_debug_hex8(pci_read_config8(north, r+c)); print_debug(" "); } print_debug("\r\n"); } } Since r is an unsigned char, it will never reach 256. To fix the problem, I simply added a line at the end of the loop: if( r >= 240 ) break; ******************************************************************* By the way, I am still working on filo. In my machine, after elfboot passing control to filo, LinuxBIOS Fallback restarts again. Following is a piece of screenshot: ...... Loading Segment: addr: 0x0000000000100000 memsz: 0x00000000000240e0 filesz: 0x000000000000a048 Clearing Segment: addr: 0x000000000010a048 memsz: 0x000000000001a098 Loading Segment: addr: 0x00000000001240e0 memsz: 0x0000000000000048 filesz: 0x0000000000000048 Jumping to boot code at 0x107d28 .8(=?sio?. LinuxBIOS-1.1.6.0Fallback Mon Jul 5 15:38:49 PDT 2004 starting... 87 is the comm register SMBus controller enabled ....... Does anyone have any suggestion about this? Thanks, Simon MSICA.com From rminnich at lanl.gov Tue Jul 6 09:59:01 2004 From: rminnich at lanl.gov (ron minnich) Date: Tue Jul 6 09:59:01 2004 Subject: A bug was found in freebios2/src/northbridge/via/vt8601/raminit.c In-Reply-To: <63235.24.87.201.99.1089073650.squirrel@www.nome.ca> Message-ID: On Mon, 5 Jul 2004 scheng at msica.com wrote: > I am trying to use LinuxBIOS V2 + Filo to boot local Linux on hard disk > (EPIA 800 board). > > I found that LinuxBIOS executes an infinite loop in dumpnorth() function > of freebios2/src/northbridge/via/vt8601/raminit.c . > > The function is: > void > dumpnorth(device_t north) > { > uint8_t r, c; > for(r = 0; r < 256; r += 16) { > print_debug_hex8(r); > print_debug(":"); > for(c = 0; c < 16; c++) { > print_debug_hex8(pci_read_config8(north, r+c)); > print_debug(" "); > } > print_debug("\r\n"); > } > } > > Since r is an unsigned char, it will never reach 256. To fix the problem, > I simply added a line at the end of the loop: if( r >= 240 ) break; thanks for the fix, did you do something like this: void dumpnorth(device_t north) { uint8_t r, c; for(r = 0; ; r += 16) { print_debug_hex8(r); print_debug(":"); for(c = 0; c < 16; c++) { print_debug_hex8(pci_read_config8(north, r+c)); print_debug(" "); } print_debug("\r\n"); if (r >= 240) break; } } (r and c are u8 because we're trying to use bytes whereever possible; this is rommcc-compiled) Let me know if this works and I'll commit it. > > ******************************************************************* > By the way, I am still working on filo. In my machine, after elfboot > passing control to filo, LinuxBIOS Fallback restarts again. Following is > a piece of screenshot: > ...... > Loading Segment: addr: 0x0000000000100000 memsz: 0x00000000000240e0 > filesz: 0x000000000000a048 > Clearing Segment: addr: 0x000000000010a048 memsz: 0x000000000001a098 > Loading Segment: addr: 0x00000000001240e0 memsz: 0x0000000000000048 > filesz: 0x0000000000000048 > Jumping to boot code at 0x107d28 > .8(=?sio?. This looks like baud rate troubles in part. also, what does readelf -a of the filo show? your start address seems odd. David, what do you think? ron From leidenfrost at corscience.de Tue Jul 6 10:24:01 2004 From: leidenfrost at corscience.de (Thomas Leidenfrost) Date: Tue Jul 6 10:24:01 2004 Subject: Wanted: Binary File for the Gene 4312 w/ NS Geode & Cx5530 Message-ID: <40EACCCC.9070905@corscience.de> Hello, at the moment I'm using the Gene-4312-Board with the NS Geode CPU and the Cx5530. Reading the archive I found out, that some people were using a similar combination. So I wanted to ask, if somebody can send me a binary file that I simply can try to flash? (If it won't work, the original Bios is backupped in a seperate ROM). And Is there any support for the onboard-flatpanel-connector? Thanks in advance, Tom. -- Thomas Leidenfrost Corscience GmbH & Co. KG Henkestra?e 91 91052 Erlangen Tel: +49-9131-97798635 Fax: +49-9131-97798659 leidenfrost at corscience.de From scheng at msica.com Tue Jul 6 10:57:00 2004 From: scheng at msica.com (scheng at msica.com) Date: Tue Jul 6 10:57:00 2004 Subject: A bug was found in freebios2/src/northbridge/via/vt8601/raminit.c In-Reply-To: References: <63235.24.87.201.99.1089073650.squirrel@www.nome.ca> Message-ID: <64028.24.87.201.99.1089131173.squirrel@www.nome.ca> > On Mon, 5 Jul 2004 scheng at msica.com wrote: > >> I am trying to use LinuxBIOS V2 + Filo to boot local Linux on hard disk >> (EPIA 800 board). >> >> I found that LinuxBIOS executes an infinite loop in dumpnorth() function >> of freebios2/src/northbridge/via/vt8601/raminit.c . >> >> The function is: >> void >> dumpnorth(device_t north) >> { >> uint8_t r, c; >> for(r = 0; r < 256; r += 16) { >> print_debug_hex8(r); >> print_debug(":"); >> for(c = 0; c < 16; c++) { >> print_debug_hex8(pci_read_config8(north, r+c)); >> print_debug(" "); >> } >> print_debug("\r\n"); >> } >> } >> >> Since r is an unsigned char, it will never reach 256. To fix the >> problem, >> I simply added a line at the end of the loop: if( r >= 240 ) break; > > thanks for the fix, did you do something like this: > > void > dumpnorth(device_t north) > { > uint8_t r, c; > for(r = 0; ; r += 16) { > print_debug_hex8(r); > print_debug(":"); > for(c = 0; c < 16; c++) { > print_debug_hex8(pci_read_config8(north, r+c)); > print_debug(" "); > } > print_debug("\r\n"); > if (r >= 240) > break; > } > } > > (r and c are u8 because we're trying to use bytes whereever possible; this > is rommcc-compiled) > > Let me know if this works and I'll commit it. Yes, it works. > > >> >> ******************************************************************* >> By the way, I am still working on filo. In my machine, after elfboot >> passing control to filo, LinuxBIOS Fallback restarts again. Following >> is >> a piece of screenshot: >> ...... >> Loading Segment: addr: 0x0000000000100000 memsz: 0x00000000000240e0 >> filesz: 0x000000000000a048 >> Clearing Segment: addr: 0x000000000010a048 memsz: 0x000000000001a098 >> Loading Segment: addr: 0x00000000001240e0 memsz: 0x0000000000000048 >> filesz: 0x0000000000000048 >> Jumping to boot code at 0x107d28 >> .8(=?sio?. > > This looks like baud rate troubles in part. > > also, what does readelf -a of the filo show? your start address seems odd. Here is the readelf -a filo.elf: **************************************************************** epia1:/usr/src# readelf -a filo.elf ELF Header: Magic: 7f 45 4c 46 01 01 01 00 00 00 00 00 00 00 00 00 Class: ELF32 Data: 2's complement, little endian Version: 1 (current) OS/ABI: UNIX - System V ABI Version: 0 Type: EXEC (Executable file) Machine: Intel 80386 Version: 0x1 Entry point address: 0x107d28 Start of program headers: 52 (bytes into file) Start of section headers: 41400 (bytes into file) Flags: 0x0 Size of this header: 52 (bytes) Size of program headers: 32 (bytes) Number of program headers: 4 Size of section headers: 40 (bytes) Number of section headers: 10 Section header string table index: 9 Section Headers: [Nr] Name Type Addr Off Size ES Flg Lk Inf Al [ 0] NULL 00000000 000000 000000 00 0 0 0 [ 1] .note NOTE 00100000 0000c0 000078 00 A 0 0 32 [ 2] .text PROGBITS 00100080 000140 008d28 00 WAX 0 0 16 [ 3] .rodata PROGBITS 00108dc0 008e80 000f29 00 A 0 0 32 [ 4] .eh_frame PROGBITS 00109cec 009dac 000058 00 A 0 0 4 [ 5] .data PROGBITS 00109d60 009e20 0002e8 00 WA 0 0 32 [ 6] .bss NOBITS 0010a060 00a120 01a080 00 WA 0 0 32 [ 7] .initctx PROGBITS 001240e0 00a120 000048 00 WA 0 0 32 [ 8] .note.GNU-stack NOTE 00000000 00a168 000000 00 X 0 0 1 [ 9] .shstrtab STRTAB 00000000 00a168 00004d 00 0 0 1 Key to Flags: W (write), A (alloc), X (execute), M (merge), S (strings) I (info), L (link order), G (group), x (unknown) O (extra OS processing required) o (OS specific), p (processor specific) Program Headers: Type Offset VirtAddr PhysAddr FileSiz MemSiz Flg Align LOAD 0x0000c0 0x00100000 0x00100000 0x0a048 0x240e0 RWE 0x20 LOAD 0x00a120 0x001240e0 0x001240e0 0x00048 0x00048 RW 0x20 NOTE 0x0000c0 0x00100000 0x00100000 0x00078 0x00078 R 0x20 STACK 0x000000 0x00000000 0x00000000 0x00000 0x00000 RWE 0x4 Section to Segment mapping: Segment Sections... 00 .note .text .rodata .eh_frame .data .bss 01 .initctx 02 .note 03 There is no dynamic segment in this file. There are no relocations in this file. There are no unwind sections in this file. No version information found in this file. ******************************************************************* Ron, I am a newbie to LinuxBIOS and booting area. There are too many things to learn. Thank you for your help. Simon > David, what do you think? > > ron > > From rminnich at lanl.gov Tue Jul 6 11:07:01 2004 From: rminnich at lanl.gov (ron minnich) Date: Tue Jul 6 11:07:01 2004 Subject: A bug was found in freebios2/src/northbridge/via/vt8601/raminit.c In-Reply-To: <64028.24.87.201.99.1089131173.squirrel@www.nome.ca> Message-ID: On Tue, 6 Jul 2004 scheng at msica.com wrote: > > Let me know if this works and I'll commit it. > > Yes, it works. I just committed the fix, thanks what's you serial port baud rate? I can just send you one of our filo images to test. Whats' your build machine again? ron From ebiederman at lnxi.com Tue Jul 6 11:20:01 2004 From: ebiederman at lnxi.com (Eric W. Biederman) Date: Tue Jul 6 11:20:01 2004 Subject: A bug was found in freebios2/src/northbridge/via/vt8601/raminit.c In-Reply-To: References: Message-ID: ron minnich writes: > On Mon, 5 Jul 2004 scheng at msica.com wrote: > > > I am trying to use LinuxBIOS V2 + Filo to boot local Linux on hard disk > > (EPIA 800 board). > > > > I found that LinuxBIOS executes an infinite loop in dumpnorth() function > > of freebios2/src/northbridge/via/vt8601/raminit.c . > > > > The function is: > > void > > dumpnorth(device_t north) > > { > > uint8_t r, c; > > for(r = 0; r < 256; r += 16) { > > print_debug_hex8(r); > > print_debug(":"); > > for(c = 0; c < 16; c++) { > > print_debug_hex8(pci_read_config8(north, r+c)); > > print_debug(" "); > > } > > print_debug("\r\n"); > > } > > } > > > > Since r is an unsigned char, it will never reach 256. To fix the problem, > > I simply added a line at the end of the loop: if( r >= 240 ) break; > > thanks for the fix, did you do something like this: > > void > dumpnorth(device_t north) > { > uint8_t r, c; > for(r = 0; ; r += 16) { > print_debug_hex8(r); > print_debug(":"); > for(c = 0; c < 16; c++) { > print_debug_hex8(pci_read_config8(north, r+c)); > print_debug(" "); > } > print_debug("\r\n"); > if (r >= 240) > break; > } > } > > (r and c are u8 because we're trying to use bytes whereever possible; this > is rommcc-compiled) Hmm.. Using bytes does not help the register pressure and in fact slightly increases code size. If the byte register instructions on x86 were more symmetric this might be different, but... I cannot think of an architecture where using bytes would be better. The increase in code size is because of the need to clamp the values at their maximum so code like this fails properly. Earlier versions of romcc were buggy and did not clamp values after they were put into a register even if you said it was a character value. So an unsigned char could hold the value of 256 if you incremented it to there. Probably the easiest way to imagine how code generation works in romcc is to think of a non byte addressed machine, and how awkward that makes smaller than word size quantities. Not really bad but certainly awkward. > Let me know if this works and I'll commit it. The code will be more efficient if you just use an int or an unsigned int. Eric From rminnich at lanl.gov Tue Jul 6 11:29:01 2004 From: rminnich at lanl.gov (ron minnich) Date: Tue Jul 6 11:29:01 2004 Subject: A bug was found in freebios2/src/northbridge/via/vt8601/raminit.c In-Reply-To: Message-ID: On 6 Jul 2004, Eric W. Biederman wrote: > Hmm.. Using bytes does not help the register pressure and in fact > slightly increases code size. If the byte register instructions > on x86 were more symmetric this might be different, but... sad that they don't work well. > > I cannot think of an architecture where using bytes would be better. > The increase in code size is because of the need to clamp the values > at their maximum so code like this fails properly. They exist :-) thanks for the tip, this is very good to know. thanks ron From dwh at lanl.gov Tue Jul 6 13:32:00 2004 From: dwh at lanl.gov (Hendricks David W.) Date: Tue Jul 6 13:32:00 2004 Subject: A bug was found in freebios2/src/northbridge/via/vt8601/raminit.c In-Reply-To: Message-ID: Garbled output is usually a symptom of incorrect serial baud rate. It seems fine in the boot loader, perhaps he needs to pass console=ttys0,115200 to his kernel. > > > > ******************************************************************* > > By the way, I am still working on filo. In my machine, after elfboot > > passing control to filo, LinuxBIOS Fallback restarts again. Following is > > a piece of screenshot: > > ...... > > Loading Segment: addr: 0x0000000000100000 memsz: 0x00000000000240e0 > > filesz: 0x000000000000a048 > > Clearing Segment: addr: 0x000000000010a048 memsz: 0x000000000001a098 > > Loading Segment: addr: 0x00000000001240e0 memsz: 0x0000000000000048 > > filesz: 0x0000000000000048 > > Jumping to boot code at 0x107d28 > > .8(=?sio?. > > This looks like baud rate troubles in part. > > also, what does readelf -a of the filo show? your start address seems odd. > David, what do you think? > > ron > > _______________________________________________ > Linuxbios mailing list > Linuxbios at clustermatic.org > http://www.clustermatic.org/mailman/listinfo/linuxbios > From ebiederman at lnxi.com Tue Jul 6 14:27:00 2004 From: ebiederman at lnxi.com (Eric W. Biederman) Date: Tue Jul 6 14:27:00 2004 Subject: A bug was found in freebios2/src/northbridge/via/vt8601/raminit.c In-Reply-To: References: Message-ID: ron minnich writes: > On 6 Jul 2004, Eric W. Biederman wrote: > > > Hmm.. Using bytes does not help the register pressure and in fact > > slightly increases code size. If the byte register instructions > > on x86 were more symmetric this might be different, but... > > sad that they don't work well. They work well unless you are register starved, and since romcc is always register starved they don't work well in that context. There are no general register to register move instructions to let me move a byte register into a longer register and vice versa. So generally I don't even bother with the byte registers. > > I cannot think of an architecture where using bytes would be better. > > The increase in code size is because of the need to clamp the values > > at their maximum so code like this fails properly. > > They exist :-) Where bytes are better for register pressure? Beyond the theoretical case where something could be built I would love to see one. Note this is limited to treating any instruction set as a load/store architecture, because register to memory instructions can't be used. Which is the primary thing that cripples the x86 case and bytes. > thanks for the tip, this is very good to know. There are 2 important cases for registers. 1) Using them. 2) Storing data in them. When you are using a register it is best to have the value unpacked and to just use that register. When you are simply storing data in a register the trade offs change because you can afford a second register to hold the value when you take it out and modify it. For optimizing the storage case I have implemented bitfields. When they are unpacked and being manipulated they need an extra. In the cases where registers are tight bitfields could be handy, in structures could be handy for passing around multiple values. A loop counter usually does not fit that description though. Especially not when you don't have something else to put in the same register. Since values are mostly used and not stored in registers I leave it up to the programmer to implement the storage optimization case. Although by implementing bitfields I am as helpful as I can be. Eric From rminnich at lanl.gov Tue Jul 6 15:24:01 2004 From: rminnich at lanl.gov (ron minnich) Date: Tue Jul 6 15:24:01 2004 Subject: A bug was found in freebios2/src/northbridge/via/vt8601/raminit.c In-Reply-To: Message-ID: On 6 Jul 2004, Eric W. Biederman wrote: > > They exist :-) > > Where bytes are better for register pressure? on the Tera machine this kind of thing is called 'puddle arithmetic' and it was kind of neat. My memory of the instruction set is that it works. ron From scheng at msica.com Tue Jul 6 17:54:00 2004 From: scheng at msica.com (Simon Xin Cheng) Date: Tue Jul 6 17:54:00 2004 Subject: A bug was found in freebios2/src/northbridge/via/vt8601/raminit.c In-Reply-To: References: <64028.24.87.201.99.1089131173.squirrel@www.nome.ca> Message-ID: <61217.24.87.201.99.1089156219.squirrel@www.nome.ca> > On Tue, 6 Jul 2004 scheng at msica.com wrote: > >> > Let me know if this works and I'll commit it. >> >> Yes, it works. > > I just committed the fix, thanks > > what's you serial port baud rate? I can just send you one of our filo > images to test. > > > Whats' your build machine again? > > ron Whats' your build machine again? > > ron I adjusted the baud rate to 115200 for LinuxBIOS, filo and kernel command. Right now, I can get into filo, but right after it began relocate system info, the LinuxBIOS restarts. A truncation of screen shot is: ************************************** Found ELF candiate at offset 0 New segment addr 0x100000 size 0x264e0 offset 0xc0 filesize 0xc448 (cleaned up) New segment addr 0x100000 size 0x264e0 offset 0xc0 filesize 0xc448 New segment addr 0x1264e0 size 0x48 offset 0xc520 filesize 0x48 (cleaned up) New segment addr 0x1264e0 size 0x48 offset 0xc520 filesize 0x48 Dropping non PT_LOAD segment Dropping non PT_LOAD segment Loading Segment: addr: 0x0000000000100000 memsz: 0x00000000000264e0 filesz: 0x000000000000c448 Clearing Segment: addr: 0x000000000010c448 memsz: 0x000000000001a098 Loading Segment: addr: 0x00000000001264e0 memsz: 0x0000000000000048 filesz: 0x0000000000000048 Jumping to boot code at 0x108c68 FILO version 0.4.2 (root at epia1) Tue Jul 6 15:55:32 PDT 2004 collect_sys_info: boot eax = 0xe1fb007 collect_sys_info: boot ebx = 0x9ff5294 collect_sys_info: boot arg = 0x9ff5294 collect_linuxbios_info: Searching for LinuxBIOS tables... find_lb_table: Found canidate at: 00000500 find_lb_table: header checksum o.k. find_lb_table: table checksum o.k. find_lb_table: record count o.k. collect_linuxbios_info: Found LinuxBIOS table at: 00000500 malloc_diag: alloc: 0 bytes (0 blocks), free: 16376 bytes (1 blocks) malloc_diag: alloc: 40 bytes (1 blocks), free: 16336 bytes (1 blocks) convert_memmap: 0x00000000000000 0x00000000000b3c 16 convert_memmap: 0x00000000000b3c 0x00000009fff4c4 1 collect_sys_info: 0000000000000b3c-000000000a000000 collect_sys_info: RAM 160 MB collect_sys_info is done begin relocate systeminfo _start = 100000 ; _end = 126528 relocate: prog_addr=100000 relocate: prog_size=26528 relocate: Current location: 0x100000-0x126527 relocate: Relocating to 0x9fd9ad0-0x9fffff7... 0 LinuxBIOS-1.1.6.0Fallback Tue Jul 6 15:57:28 PDT 2004 starting... 87 is the comm register SMBus controller enabled vt8601 init starting 00000000 is the north 1106 0601 0120d4 is the computed timing ************************************** My build machine is EPIA800. Here is the lspci: ************************************ epia1:~# lspci 0000:00:00.0 Host bridge: VIA Technologies, Inc. VT8601 [Apollo ProMedia] (rev 05) 0000:00:01.0 PCI bridge: VIA Technologies, Inc. VT8601 [Apollo ProMedia AGP] 0000:00:11.0 ISA bridge: VIA Technologies, Inc. VT8231 [PCI-to-ISA Bridge] (rev 10) 0000:00:11.1 IDE interface: VIA Technologies, Inc. VT82C586A/B/VT82C686/A/B/VT823x/A/C PIPC Bus Master IDE (rev 06) 0000:00:11.2 USB Controller: VIA Technologies, Inc. VT82xxxxx UHCI USB 1.1 Controller (rev 1e) 0000:00:11.3 USB Controller: VIA Technologies, Inc. VT82xxxxx UHCI USB 1.1 Controller (rev 1e) 0000:00:11.4 Bridge: VIA Technologies, Inc. VT8235 ACPI (rev 10) 0000:00:11.5 Multimedia audio controller: VIA Technologies, Inc. VT82C686 AC97 Audio Controller (rev 40) 0000:00:12.0 Ethernet controller: VIA Technologies, Inc. VT6102 [Rhine-II] (rev 51) 0000:01:00.0 VGA compatible controller: Trident Microsystems CyberBlade/i1 (rev 6a) ************************************** Thanks a lot. Simon Cheng www.msica.com From ts1 at tsn.or.jp Tue Jul 6 21:22:01 2004 From: ts1 at tsn.or.jp (Takeshi Sone) Date: Tue Jul 6 21:22:01 2004 Subject: A bug was found in freebios2/src/northbridge/via/vt8601/raminit.c In-Reply-To: <61217.24.87.201.99.1089156219.squirrel@www.nome.ca> References: <64028.24.87.201.99.1089131173.squirrel@www.nome.ca> <61217.24.87.201.99.1089156219.squirrel@www.nome.ca> Message-ID: <20040707025139.GA30797@tsn.or.jp> On Tue, Jul 06, 2004 at 04:23:39PM -0700, Simon Xin Cheng wrote: > collect_linuxbios_info: Found LinuxBIOS table at: 00000500 > malloc_diag: alloc: 0 bytes (0 blocks), free: 16376 bytes (1 blocks) > malloc_diag: alloc: 40 bytes (1 blocks), free: 16336 bytes (1 blocks) > convert_memmap: 0x00000000000000 0x00000000000b3c 16 > convert_memmap: 0x00000000000b3c 0x00000009fff4c4 1 > collect_sys_info: 0000000000000b3c-000000000a000000 > collect_sys_info: RAM 160 MB > collect_sys_info is done > begin relocate systeminfo > _start = 100000 ; _end = 126528 > relocate: prog_addr=100000 > relocate: prog_size=26528 > relocate: Current location: 0x100000-0x126527 > relocate: Relocating to 0x9fd9ad0-0x9fffff7... 0 > > LinuxBIOS-1.1.6.0Fallback Tue Jul 6 15:57:28 PDT 2004 starting... Maybe the memory map information is wrong. (FILO tries to relocate itself to non-existent RAM area and crashes?) Are you sure you have 160MB RAM and none of it is allocated for framebuffer? You should run memtest86 as payload so you can see if memory configuration is ok. -- Takeshi From thomas at wehrspann.de Wed Jul 7 05:20:01 2004 From: thomas at wehrspann.de (Thomas Wehrspann) Date: Wed Jul 7 05:20:01 2004 Subject: freebios1 sis-kernel_patch for 2.6 Message-ID: <200407071219.44352.thomas@wehrspann.de> Hi, i'm still using the K7SEM Motherboard with DiskOnChip Milleniuim an LinuxBIOS. Linux 2.6 has some features i need and want, so i ported parts of the latest 2.4 sis-kernel_patch and the ide-spinup.patch to the 2.6 kernel some time ago. I combined both patches into one. I didn't port the SiSFB-Lite part of the SiS-Patch, because the SiS graphics driver in the kernel changed a lot. The SiS framebuffer seems to work better with kernel 2.6 and linuxbios than it was with kernel 2.4 and linuxbios. But i have to call the fbset utility first after booting with linuxbios. I do not have the knowledge to fix that. Greetings Thomas Wehrspann -------------- next part -------------- A non-text attachment was scrubbed... Name: linux-2.6.4-sis+ide-spinup.patch Type: text/x-diff Size: 7524 bytes Desc: not available URL: From dwh at lanl.gov Wed Jul 7 14:04:01 2004 From: dwh at lanl.gov (Hendricks David W.) Date: Wed Jul 7 14:04:01 2004 Subject: freebios1 sis-kernel_patch for 2.6 In-Reply-To: <200407071219.44352.thomas@wehrspann.de> Message-ID: Ollie Lo would be the person to ask about that. He's on leave at the moment, visiting with relatives. Please wait patiently for his respnose if nobody else can help. On Wed, 7 Jul 2004, Thomas Wehrspann wrote: > Hi, > > i'm still using the K7SEM Motherboard with DiskOnChip Milleniuim an LinuxBIOS. > > Linux 2.6 has some features i need and want, so i ported parts of the latest > 2.4 sis-kernel_patch and the ide-spinup.patch to the 2.6 kernel some time > ago. > I combined both patches into one. > I didn't port the SiSFB-Lite part of the SiS-Patch, because the SiS graphics > driver in the kernel changed a lot. > > The SiS framebuffer seems to work better with kernel 2.6 and linuxbios than it > was with kernel 2.4 and linuxbios. But i have to call the fbset utility first > after booting with linuxbios. > I do not have the knowledge to fix that. > > Greetings > Thomas Wehrspann > From scheng at msica.com Wed Jul 7 17:13:00 2004 From: scheng at msica.com (Simon Xin Cheng) Date: Wed Jul 7 17:13:00 2004 Subject: A bug was found in freebios2/src/northbridge/via/vt8601/raminit.c In-Reply-To: <20040707025139.GA30797@tsn.or.jp> References: <64028.24.87.201.99.1089131173.squirrel@www.nome.ca> <61217.24.87.201.99.1089156219.squirrel@www.nome.ca> <20040707025139.GA30797@tsn.or.jp> Message-ID: <60092.24.87.201.99.1089240165.squirrel@www.nome.ca> > Maybe the memory map information is wrong. > (FILO tries to relocate itself to non-existent RAM area and crashes?) > Are you sure you have 160MB RAM and none of it is allocated for > framebuffer? > You should run memtest86 as payload so you can see if memory > configuration is ok. > > -- > Takeshi > Takeshi, Thank you for your suggestion. I tried memtest86-3.1.a. This guy creates a 69356Byte elf file. It exceeds 64KB. So, I disabled fallback. However, I can not boot from the romimage I created (i.e. cann't get any information from serial console). Following is the configure file. If you have time, would you please check it. Thanks again! *************************************** loadoptions target epia uses ARCH uses CONFIG_COMPRESS uses CONFIG_IOAPIC uses CONFIG_ROM_STREAM uses CONFIG_ROM_STREAM_START uses CONFIG_UDELAY_TSC uses CPU_FIXUP uses FALLBACK_SIZE uses HAVE_FALLBACK_BOOT uses HAVE_MP_TABLE uses HAVE_PIRQ_TABLE uses HAVE_HARD_RESET uses i586 uses i686 uses INTEL_PPRO_MTRR uses HEAP_SIZE uses IRQ_SLOT_COUNT uses MAINBOARD_PART_NUMBER uses MAINBOARD_VENDOR uses CONFIG_SMP uses CONFIG_MAX_CPUS uses MEMORY_HOLE uses PAYLOAD_SIZE uses _RAMBASE uses _ROMBASE uses ROM_IMAGE_SIZE uses ROM_SECTION_OFFSET uses ROM_SECTION_SIZE uses ROM_SIZE uses STACK_SIZE uses USE_FALLBACK_IMAGE uses USE_OPTION_TABLE uses HAVE_OPTION_TABLE uses MAXIMUM_CONSOLE_LOGLEVEL uses DEFAULT_CONSOLE_LOGLEVEL uses CONFIG_CONSOLE_SERIAL8250 uses MAINBOARD uses CONFIG_CHIP_CONFIGURE uses XIP_ROM_SIZE uses XIP_ROM_BASE uses LINUXBIOS_EXTRA_VERSION uses TTYS0_BAUD option TTYS0_BAUD=115200 option CONFIG_CHIP_CONFIGURE=1 option MAXIMUM_CONSOLE_LOGLEVEL=8 option DEFAULT_CONSOLE_LOGLEVEL=8 option CONFIG_CONSOLE_SERIAL8250=1 option CPU_FIXUP=1 option CONFIG_UDELAY_TSC=0 option i686=1 option i586=1 option INTEL_PPRO_MTRR=1 option ROM_SIZE=256*1024 option HAVE_OPTION_TABLE=1 option CONFIG_ROM_STREAM=1 option HAVE_FALLBACK_BOOT=0 ### ### Compute the location and size of where this firmware image ### (linuxBIOS plus bootloader) will live in the boot rom chip. ### option FALLBACK_SIZE=0 ## ROM_IMAGE_SIZE is the amount of space to allow linuxBIOS to occupy. option ROM_IMAGE_SIZE=65536 ## LinuxBIOS C code runs at this location in RAM option _RAMBASE=0x00004000 romimage "normal" option USE_FALLBACK_IMAGE=0 option PAYLOAD_SIZE=69356 option LINUXBIOS_EXTRA_VERSION=".0Normal" mainboard via/epia payload /usr/src/memtest end buildrom ./linuxbios.rom ROM_SIZE "normal" **************************************************** Simon Cheng www.msica.com From YhLu at tyan.com Wed Jul 7 17:59:01 2004 From: YhLu at tyan.com (YhLu) Date: Wed Jul 7 17:59:01 2004 Subject: =?GB2312?B?tPC4tDogQSBidWcgd2FzIGZvdW5kIGluICBmcmVlYmlvczIvc3Jj?= =?GB2312?B?L25vcnRoYnJpZGdlL3ZpYS92dDg2MDEvcmFtaW5pdC5j?= Message-ID: <3174569B9743D511922F00A0C94314230553616A@TYANWEB> You may only disabe normal instead of fallback. LB will execute failover at first. -----????----- ???: Simon Xin Cheng [mailto:scheng at msica.com] ????: 2004?7?7? 15:43 ???: Takeshi Sone ??: Simon Xin Cheng; linuxbios at clustermatic.org ??: Re: A bug was found in freebios2/src/northbridge/via/vt8601/raminit.c > Maybe the memory map information is wrong. > (FILO tries to relocate itself to non-existent RAM area and crashes?) > Are you sure you have 160MB RAM and none of it is allocated for > framebuffer? > You should run memtest86 as payload so you can see if memory > configuration is ok. > > -- > Takeshi > Takeshi, Thank you for your suggestion. I tried memtest86-3.1.a. This guy creates a 69356Byte elf file. It exceeds 64KB. So, I disabled fallback. However, I can not boot from the romimage I created (i.e. cann't get any information from serial console). Following is the configure file. If you have time, would you please check it. Thanks again! *************************************** loadoptions target epia uses ARCH uses CONFIG_COMPRESS uses CONFIG_IOAPIC uses CONFIG_ROM_STREAM uses CONFIG_ROM_STREAM_START uses CONFIG_UDELAY_TSC uses CPU_FIXUP uses FALLBACK_SIZE uses HAVE_FALLBACK_BOOT uses HAVE_MP_TABLE uses HAVE_PIRQ_TABLE uses HAVE_HARD_RESET uses i586 uses i686 uses INTEL_PPRO_MTRR uses HEAP_SIZE uses IRQ_SLOT_COUNT uses MAINBOARD_PART_NUMBER uses MAINBOARD_VENDOR uses CONFIG_SMP uses CONFIG_MAX_CPUS uses MEMORY_HOLE uses PAYLOAD_SIZE uses _RAMBASE uses _ROMBASE uses ROM_IMAGE_SIZE uses ROM_SECTION_OFFSET uses ROM_SECTION_SIZE uses ROM_SIZE uses STACK_SIZE uses USE_FALLBACK_IMAGE uses USE_OPTION_TABLE uses HAVE_OPTION_TABLE uses MAXIMUM_CONSOLE_LOGLEVEL uses DEFAULT_CONSOLE_LOGLEVEL uses CONFIG_CONSOLE_SERIAL8250 uses MAINBOARD uses CONFIG_CHIP_CONFIGURE uses XIP_ROM_SIZE uses XIP_ROM_BASE uses LINUXBIOS_EXTRA_VERSION uses TTYS0_BAUD option TTYS0_BAUD=115200 option CONFIG_CHIP_CONFIGURE=1 option MAXIMUM_CONSOLE_LOGLEVEL=8 option DEFAULT_CONSOLE_LOGLEVEL=8 option CONFIG_CONSOLE_SERIAL8250=1 option CPU_FIXUP=1 option CONFIG_UDELAY_TSC=0 option i686=1 option i586=1 option INTEL_PPRO_MTRR=1 option ROM_SIZE=256*1024 option HAVE_OPTION_TABLE=1 option CONFIG_ROM_STREAM=1 option HAVE_FALLBACK_BOOT=0 ### ### Compute the location and size of where this firmware image ### (linuxBIOS plus bootloader) will live in the boot rom chip. ### option FALLBACK_SIZE=0 ## ROM_IMAGE_SIZE is the amount of space to allow linuxBIOS to occupy. option ROM_IMAGE_SIZE=65536 ## LinuxBIOS C code runs at this location in RAM option _RAMBASE=0x00004000 romimage "normal" option USE_FALLBACK_IMAGE=0 option PAYLOAD_SIZE=69356 option LINUXBIOS_EXTRA_VERSION=".0Normal" mainboard via/epia payload /usr/src/memtest end buildrom ./linuxbios.rom ROM_SIZE "normal" **************************************************** Simon Cheng www.msica.com _______________________________________________ Linuxbios mailing list Linuxbios at clustermatic.org http://www.clustermatic.org/mailman/listinfo/linuxbios From dwh at lanl.gov Wed Jul 7 18:03:01 2004 From: dwh at lanl.gov (Hendricks David W.) Date: Wed Jul 7 18:03:01 2004 Subject: =?GB2312?B?tPC4tDogQSBidWcgd2FzIGZvdW5kIGluICBmcmVlYmlvczIvc3Jj?= =?GB2312?B?L25vcnRoYnJpZGdlL3ZpYS92dDg2MDEvcmFtaW5pdC5j?= In-Reply-To: <3174569B9743D511922F00A0C94314230553616A@TYANWEB> Message-ID: Also, you might want to make PAYLOAD_SIZE = (ROM_SECTION_SIZE - ROM_IMAGE_SIZE) On Wed, 7 Jul 2004, YhLu wrote: > You may only disabe normal instead of fallback. > > LB will execute failover at first. > > -----????????----- > ??????: Simon Xin Cheng [mailto:scheng at msica.com] > ????????: 2004??7??7?? 15:43 > ??????: Takeshi Sone > ????: Simon Xin Cheng; linuxbios at clustermatic.org > ????: Re: A bug was found in freebios2/src/northbridge/via/vt8601/raminit.c > > > Maybe the memory map information is wrong. > > (FILO tries to relocate itself to non-existent RAM area and crashes?) > > Are you sure you have 160MB RAM and none of it is allocated for > > framebuffer? > > You should run memtest86 as payload so you can see if memory > > configuration is ok. > > > > -- > > Takeshi > > > > Takeshi, > > Thank you for your suggestion. I tried memtest86-3.1.a. This guy creates a > 69356Byte elf file. It exceeds 64KB. So, I disabled fallback. However, I > can not boot from the romimage I created (i.e. cann't get any information > from serial console). Following is the configure file. If you have time, > would you please check it. Thanks again! > *************************************** > > loadoptions > > target epia > > uses ARCH > uses CONFIG_COMPRESS > uses CONFIG_IOAPIC > uses CONFIG_ROM_STREAM > uses CONFIG_ROM_STREAM_START > uses CONFIG_UDELAY_TSC > uses CPU_FIXUP > uses FALLBACK_SIZE > uses HAVE_FALLBACK_BOOT > uses HAVE_MP_TABLE > uses HAVE_PIRQ_TABLE > uses HAVE_HARD_RESET > uses i586 > uses i686 > uses INTEL_PPRO_MTRR > uses HEAP_SIZE > uses IRQ_SLOT_COUNT > uses MAINBOARD_PART_NUMBER > uses MAINBOARD_VENDOR > uses CONFIG_SMP > uses CONFIG_MAX_CPUS > uses MEMORY_HOLE > uses PAYLOAD_SIZE > uses _RAMBASE > uses _ROMBASE > uses ROM_IMAGE_SIZE > uses ROM_SECTION_OFFSET > uses ROM_SECTION_SIZE > uses ROM_SIZE > uses STACK_SIZE > uses USE_FALLBACK_IMAGE > uses USE_OPTION_TABLE > uses HAVE_OPTION_TABLE > uses MAXIMUM_CONSOLE_LOGLEVEL > uses DEFAULT_CONSOLE_LOGLEVEL > uses CONFIG_CONSOLE_SERIAL8250 > uses MAINBOARD > uses CONFIG_CHIP_CONFIGURE > uses XIP_ROM_SIZE > uses XIP_ROM_BASE > uses LINUXBIOS_EXTRA_VERSION > uses TTYS0_BAUD > > option TTYS0_BAUD=115200 > > option CONFIG_CHIP_CONFIGURE=1 > > option MAXIMUM_CONSOLE_LOGLEVEL=8 > option DEFAULT_CONSOLE_LOGLEVEL=8 > option CONFIG_CONSOLE_SERIAL8250=1 > > option CPU_FIXUP=1 > option CONFIG_UDELAY_TSC=0 > option i686=1 > option i586=1 > option INTEL_PPRO_MTRR=1 > option ROM_SIZE=256*1024 > > option HAVE_OPTION_TABLE=1 > option CONFIG_ROM_STREAM=1 > option HAVE_FALLBACK_BOOT=0 > > ### > ### Compute the location and size of where this firmware image > ### (linuxBIOS plus bootloader) will live in the boot rom chip. > ### > option FALLBACK_SIZE=0 > ## ROM_IMAGE_SIZE is the amount of space to allow linuxBIOS to occupy. > option ROM_IMAGE_SIZE=65536 > > ## LinuxBIOS C code runs at this location in RAM > option _RAMBASE=0x00004000 > > romimage "normal" > option USE_FALLBACK_IMAGE=0 > option PAYLOAD_SIZE=69356 > option LINUXBIOS_EXTRA_VERSION=".0Normal" > mainboard via/epia > payload /usr/src/memtest > end > > buildrom ./linuxbios.rom ROM_SIZE "normal" > > **************************************************** > > > > > > > Simon Cheng > www.msica.com > _______________________________________________ > Linuxbios mailing list > Linuxbios at clustermatic.org > http://www.clustermatic.org/mailman/listinfo/linuxbios > _______________________________________________ > Linuxbios mailing list > Linuxbios at clustermatic.org > http://www.clustermatic.org/mailman/listinfo/linuxbios > From rminnich at lanl.gov Wed Jul 7 18:07:00 2004 From: rminnich at lanl.gov (ron minnich) Date: Wed Jul 7 18:07:00 2004 Subject: =?GB2312?B?tPC4tDogQSBidWcgd2FzIGZvdW5kIGluICBmcmVlYmlvczIvc3Jj?= =?GB2312?B?L25vcnRoYnJpZGdlL3ZpYS92dDg2MDEvcmFtaW5pdC5j?= In-Reply-To: <3174569B9743D511922F00A0C94314230553616A@TYANWEB> Message-ID: Here is a config file that only has fallback, not normal. It uses a kernel as the payload. # the Arima HDAMA # This will make a target directory of ./hdama loadoptions target hdama uses ARCH uses CONFIG_COMPRESS uses CONFIG_IOAPIC uses CONFIG_ROM_STREAM uses CONFIG_ROM_STREAM_START uses CONFIG_UDELAY_TSC uses CPU_FIXUP uses FALLBACK_SIZE uses HAVE_FALLBACK_BOOT uses HAVE_MP_TABLE uses HAVE_PIRQ_TABLE uses HAVE_HARD_RESET uses i586 uses i686 uses INTEL_PPRO_MTRR uses HEAP_SIZE uses IRQ_SLOT_COUNT uses k7 uses k8 uses MAINBOARD_PART_NUMBER uses MAINBOARD_VENDOR uses CONFIG_SMP uses CONFIG_MAX_CPUS uses MEMORY_HOLE uses PAYLOAD_SIZE uses _RAMBASE uses _ROMBASE uses ROM_IMAGE_SIZE uses ROM_SECTION_OFFSET uses ROM_SECTION_SIZE uses ROM_SIZE uses STACK_SIZE uses USE_FALLBACK_IMAGE uses USE_OPTION_TABLE uses HAVE_OPTION_TABLE uses MAXIMUM_CONSOLE_LOGLEVEL uses DEFAULT_CONSOLE_LOGLEVEL uses CONFIG_CONSOLE_SERIAL8250 uses MAINBOARD uses CONFIG_CHIP_CONFIGURE uses XIP_ROM_SIZE uses XIP_ROM_BASE uses LINUXBIOS_EXTRA_VERSION option CONFIG_CHIP_CONFIGURE=1 option MAXIMUM_CONSOLE_LOGLEVEL=8 option DEFAULT_CONSOLE_LOGLEVEL=8 option CONFIG_CONSOLE_SERIAL8250=1 option CPU_FIXUP=1 option CONFIG_UDELAY_TSC=0 option i686=1 option i586=1 option INTEL_PPRO_MTRR=1 option k7=1 option k8=1 option ROM_SIZE=0x100000 option HAVE_OPTION_TABLE=1 option CONFIG_ROM_STREAM=1 option HAVE_FALLBACK_BOOT=1 ### ### Compute the location and size of where this firmware image ### (linuxBIOS plus bootloader) will live in the boot rom chip. ### option FALLBACK_SIZE=ROM_SIZE ## LinuxBIOS C code runs at this location in RAM option _RAMBASE=0x00004000 # ### ### Compute the start location and size size of ### The linuxBIOS bootloader. ### # # Arima hdama romimage "fallback" option USE_FALLBACK_IMAGE=1 option ROM_IMAGE_SIZE=0x10000 # option ROM_SECTION_SIZE=0x100000 option LINUXBIOS_EXTRA_VERSION=".0Fallback" mainboard arima/hdama # payload ../../../../tg3--ide_disk.zelf payload ../../../../opteron_phase1_p4_noapic # payload ../../../../../../hdama-1 # payload /usr/share/etherboot/5.1.9pre2-lnxi-lb/tg3--ide_disk.zelf end buildrom ./luxbios.rom ROM_SIZE "fallback" From ebiederman at lnxi.com Wed Jul 7 22:31:00 2004 From: ebiederman at lnxi.com (Eric W. Biederman) Date: Wed Jul 7 22:31:00 2004 Subject: CPU refactoring status.... In-Reply-To: References: <3174569B9743D511922F00A0C943142305535CCC@TYANWEB> Message-ID: ebiederman at lnxi.com (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 #include #include #include #include #include #include #include #include #include #include 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); } From rminnich at lanl.gov Wed Jul 7 22:42:01 2004 From: rminnich at lanl.gov (ron minnich) Date: Wed Jul 7 22:42:01 2004 Subject: CPU refactoring status.... In-Reply-To: Message-ID: 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. ron From ebiederman at lnxi.com Wed Jul 7 22:42:07 2004 From: ebiederman at lnxi.com (Eric W. Biederman) Date: Wed Jul 7 22:42:07 2004 Subject: CPU refactoring status.... In-Reply-To: References: Message-ID: ron minnich 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. Sure. Not a problem. I will see what I can put together in the next couple of days. > 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. Sounds like a reasonable time line. The biggest advantage I see (besides making cpu initialization more maintainable) is that it reduces the amount of unconditional generic code. Eric From ollie at lanl.gov Thu Jul 8 09:24:00 2004 From: ollie at lanl.gov (Li-Ta Lo) Date: Thu Jul 8 09:24:00 2004 Subject: freebios1 sis-kernel_patch for 2.6 In-Reply-To: References: Message-ID: <1089298437.5698.133.camel@exponential.lanl.gov> On Wed, 2004-07-07 at 13:33, Hendricks David W. wrote: > Ollie Lo would be the person to ask about that. He's on leave at the > moment, visiting with relatives. Please wait patiently for his respnose if > nobody else can help. > 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 > On Wed, 7 Jul 2004, Thomas Wehrspann wrote: > > > Hi, > > > > i'm still using the K7SEM Motherboard with DiskOnChip Milleniuim an LinuxBIOS. > > > > Linux 2.6 has some features i need and want, so i ported parts of the latest > > 2.4 sis-kernel_patch and the ide-spinup.patch to the 2.6 kernel some time > > ago. > > I combined both patches into one. > > I didn't port the SiSFB-Lite part of the SiS-Patch, because the SiS graphics > > driver in the kernel changed a lot. > > > > The SiS framebuffer seems to work better with kernel 2.6 and linuxbios than it > > was with kernel 2.4 and linuxbios. But i have to call the fbset utility first > > after booting with linuxbios. > > I do not have the knowledge to fix that. > > > > Greetings > > Thomas Wehrspann > > > > _______________________________________________ > Linuxbios mailing list > Linuxbios at clustermatic.org > http://www.clustermatic.org/mailman/listinfo/linuxbios > From YhLu at tyan.com Thu Jul 8 12:38:01 2004 From: YhLu at tyan.com (YhLu) Date: Thu Jul 8 12:38:01 2004 Subject: =?GB2312?B?tPC4tDogQ1BVIHJlZmFjdG9yaW5nIHN0YXR1cy4uLi4=?= Message-ID: <3174569B9743D511922F00A0C943142305536224@TYANWEB> 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 -----????----- ???: ebiederman at lnxi.com [mailto:ebiederman at lnxi.com] ????: 2004?7?7? 21:03 ???: LinuxBIOS ??: YhLu; ron minnich; Stefan Reinauer ??: Re: CPU refactoring status.... ebiederman at lnxi.com (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 #include #include #include #include #include #include #include #include #include #include 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); } From Matt.Bellizzi at nokia.com Thu Jul 8 12:41:01 2004 From: Matt.Bellizzi at nokia.com (Matt.Bellizzi at nokia.com) Date: Thu Jul 8 12:41:01 2004 Subject: Linux bios and IBM Netvista 8363-EXX Message-ID: <97C16120D52CD249ADE310B69842D5B902B7F702@daebe004.americas.nokia.com> Hello I'm curious if a IBM thin client (8363-EXX or Netvista 2200) can use linuxbios? Thanks for any info From ebiederman at lnxi.com Thu Jul 8 13:09:01 2004 From: ebiederman at lnxi.com (Eric W. Biederman) Date: Thu Jul 8 13:09:01 2004 Subject: =?gb2312?b?tPC4tA==?=: CPU refactoring status.... In-Reply-To: <3174569B9743D511922F00A0C943142305536224@TYANWEB> References: <3174569B9743D511922F00A0C943142305536224@TYANWEB> Message-ID: YhLu 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 From rminnich at lanl.gov Thu Jul 8 14:19:00 2004 From: rminnich at lanl.gov (ron minnich) Date: Thu Jul 8 14:19:00 2004 Subject: Linux bios and IBM Netvista 8363-EXX In-Reply-To: <97C16120D52CD249ADE310B69842D5B902B7F702@daebe004.americas.nokia.com> Message-ID: we can't tell without knowing what the chipset is. ron From thomas at wehrspann.de Thu Jul 8 15:10:00 2004 From: thomas at wehrspann.de (Thomas Wehrspann) Date: Thu Jul 8 15:10:00 2004 Subject: freebios1 sis-kernel_patch for 2.6 In-Reply-To: <1089298437.5698.133.camel@exponential.lanl.gov> References: <1089298437.5698.133.camel@exponential.lanl.gov> Message-ID: <200407082239.53544.thomas@wehrspann.de> 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 From daubin at actuality-systems.com Thu Jul 8 15:27:01 2004 From: daubin at actuality-systems.com (David Aubin) Date: Thu Jul 8 15:27:01 2004 Subject: Filo Error Help In-Reply-To: <3174569B9743D511922F00A0C943142305536224@TYANWEB> References: <3174569B9743D511922F00A0C943142305536224@TYANWEB> Message-ID: <1089320132.5785.19.camel@buildserver1> 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 (daubin at buildserver1) #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: sse2x1 2351 MB/s raid6: sse2x2 3367 MB/s raid6: sse2x4 3578 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: dm at uk.sistina.com 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 From ollie at lanl.gov Thu Jul 8 15:35:00 2004 From: ollie at lanl.gov (Li-Ta Lo) Date: Thu Jul 8 15:35:00 2004 Subject: freebios1 sis-kernel_patch for 2.6 In-Reply-To: <200407082239.53544.thomas@wehrspann.de> References: <1089298437.5698.133.camel@exponential.lanl.gov> <200407082239.53544.thomas@wehrspann.de> Message-ID: <1089320740.5698.316.camel@exponential.lanl.gov> 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 From ebiederman at lnxi.com Thu Jul 8 15:38:00 2004 From: ebiederman at lnxi.com (Eric W. Biederman) Date: Thu Jul 8 15:38:00 2004 Subject: CPU refactoring status.... In-Reply-To: References: Message-ID: ron minnich 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 From YhLu at tyan.com Thu Jul 8 15:38:06 2004 From: YhLu at tyan.com (YhLu) Date: Thu Jul 8 15:38:06 2004 Subject: Filo Error Help Message-ID: <3174569B9743D511922F00A0C943142305536250@TYANWEB> 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 From daubin at actuality-systems.com Thu Jul 8 15:57:00 2004 From: daubin at actuality-systems.com (David Aubin) Date: Thu Jul 8 15:57:00 2004 Subject: Filo Error Help In-Reply-To: <3174569B9743D511922F00A0C943142305536250@TYANWEB> References: <3174569B9743D511922F00A0C943142305536250@TYANWEB> Message-ID: <1089321945.5785.25.camel@buildserver1> 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 -------------- next part -------------- An HTML attachment was scrubbed... URL: From daubin at actuality-systems.com Thu Jul 8 15:59:00 2004 From: daubin at actuality-systems.com (David Aubin) Date: Thu Jul 8 15:59:00 2004 Subject: Filo Error Help In-Reply-To: <1089321945.5785.25.camel@buildserver1> References: <3174569B9743D511922F00A0C943142305536250@TYANWEB> <1089321945.5785.25.camel@buildserver1> Message-ID: <1089322042.5786.27.camel@buildserver1> 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 > From YhLu at tyan.com Thu Jul 8 16:04:00 2004 From: YhLu at tyan.com (YhLu) Date: Thu Jul 8 16:04:00 2004 Subject: Filo Error Help Message-ID: <3174569B9743D511922F00A0C94314230553625D@TYANWEB> How about the size of the elf? YH -----Original Message----- From: David Aubin [mailto:daubin at actuality-systems.com] 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 > From rminnich at lanl.gov Thu Jul 8 16:11:01 2004 From: rminnich at lanl.gov (ron minnich) Date: Thu Jul 8 16:11:01 2004 Subject: Filo Error Help In-Reply-To: <1089320132.5785.19.camel@buildserver1> Message-ID: 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 From rminnich at lanl.gov Thu Jul 8 16:15:00 2004 From: rminnich at lanl.gov (ron minnich) Date: Thu Jul 8 16:15:00 2004 Subject: Filo Error Help In-Reply-To: <1089322042.5786.27.camel@buildserver1> Message-ID: 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 From rminnich at lanl.gov Thu Jul 8 16:15:07 2004 From: rminnich at lanl.gov (ron minnich) Date: Thu Jul 8 16:15:07 2004 Subject: CPU refactoring status.... In-Reply-To: Message-ID: On 8 Jul 2004, Eric W. Biederman wrote: > Ron does a branch sound good? works for me! ron From YhLu at tyan.com Thu Jul 8 16:16:00 2004 From: YhLu at tyan.com (YhLu) Date: Thu Jul 8 16:16:00 2004 Subject: Filo Error Help Message-ID: <3174569B9743D511922F00A0C94314230553626A@TYANWEB> I could send you my elf, but it is about 6Mb. YH -----Original Message----- From: ron minnich [mailto:rminnich at lanl.gov] 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 From daubin at actuality-systems.com Thu Jul 8 16:18:00 2004 From: daubin at actuality-systems.com (David Aubin) Date: Thu Jul 8 16:18:00 2004 Subject: Filo Error Help In-Reply-To: <3174569B9743D511922F00A0C94314230553625D@TYANWEB> References: <3174569B9743D511922F00A0C94314230553625D@TYANWEB> Message-ID: <1089323213.5786.30.camel@buildserver1> 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:daubin at actuality-systems.com] > 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 > > From YhLu at tyan.com Thu Jul 8 16:20:00 2004 From: YhLu at tyan.com (YhLu) Date: Thu Jul 8 16:20:00 2004 Subject: Filo Error Help Message-ID: <3174569B9743D511922F00A0C94314230553626F@TYANWEB> I wonder if it is after gzip or before gzip. -----Original Message----- From: ron minnich [mailto:rminnich at lanl.gov] 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 From daubin at actuality-systems.com Thu Jul 8 16:20:04 2004 From: daubin at actuality-systems.com (David Aubin) Date: Thu Jul 8 16:20:04 2004 Subject: Filo Error Help In-Reply-To: References: Message-ID: <1089323334.5785.33.camel@buildserver1> 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 > From daubin at actuality-systems.com Thu Jul 8 16:22:00 2004 From: daubin at actuality-systems.com (David Aubin) Date: Thu Jul 8 16:22:00 2004 Subject: Filo Error Help In-Reply-To: References: Message-ID: <1089323418.5786.35.camel@buildserver1> Hi, I currently have the kernel with 8000. Here's the output of the kernel booting: RAMDISK driver initialized: 16 RAM disks of 8000K size 1024 blocksize loop: loaded (max 8 devices) Dave On Thu, 2004-07-08 at 17:43, ron minnich wrote: > 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 > From daubin at actuality-systems.com Thu Jul 8 16:22:05 2004 From: daubin at actuality-systems.com (David Aubin) Date: Thu Jul 8 16:22:05 2004 Subject: Filo Error Help In-Reply-To: <3174569B9743D511922F00A0C94314230553626A@TYANWEB> References: <3174569B9743D511922F00A0C94314230553626A@TYANWEB> Message-ID: <1089323474.5786.37.camel@buildserver1> 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:rminnich at lanl.gov] > 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 -------------- next part -------------- An HTML attachment was scrubbed... URL: From daubin at actuality-systems.com Thu Jul 8 17:06:01 2004 From: daubin at actuality-systems.com (David Aubin) Date: Thu Jul 8 17:06:01 2004 Subject: Filo Error Help In-Reply-To: <3174569B9743D511922F00A0C94314230553626F@TYANWEB> References: <3174569B9743D511922F00A0C94314230553626F@TYANWEB> Message-ID: <1089326101.5786.46.camel@buildserver1> 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 00000008:00000006:00000050 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 (root at tst288xsuse9) #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:rminnich at lanl.gov] > 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 From dwh at lanl.gov Thu Jul 8 17:36:01 2004 From: dwh at lanl.gov (Hendricks David W.) Date: Thu Jul 8 17:36:01 2004 Subject: Filo Error Help In-Reply-To: <1089326101.5786.46.camel@buildserver1> Message-ID: 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 > 00000008:00000006:00000050 > 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 (root at tst288xsuse9) #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:rminnich at lanl.gov] > > 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 > Linuxbios at clustermatic.org > http://www.clustermatic.org/mailman/listinfo/linuxbios > From kinema at gmail.com Fri Jul 9 01:17:00 2004 From: kinema at gmail.com (Adam Hunt) Date: Fri Jul 9 01:17:00 2004 Subject: Status of the EPIA port? Message-ID: What is the current state of the EPIA port? I am interested in running LinuxBIOS on a EPIA PD 10000 (as soon as I can find a supplier in the States). Can X be run via the on-board VGA (as apposed to the LVDS). --adam From daubin at actuality-systems.com Fri Jul 9 06:57:00 2004 From: daubin at actuality-systems.com (David Aubin) Date: Fri Jul 9 06:57:00 2004 Subject: Filo Error Help In-Reply-To: References: Message-ID: <1089375926.9481.5.camel@buildserver1> Both his kernel and my kernel work, it is the initrd that fails. Also, note that my same elf image works fine in etherboot. So this disproves your /etc/fstab & vt support theory. I think it is a configuration problem with filo, but I do not know what to change. I have the filo drop off of etherboot 5.2.4. Do I need to modify ram storage for filo someplace? Here is my filo config: # !!! NOTE !!! # Do NOT add spaces or comments at the end of option lines. # It confuses some versions of make. # Image filename for automatic boot and optional command line parameter #AUTOBOOT_FILE = "hda3:/boot/vmlinuz root=/dev/hda3 console=tty0 console=ttyS0,115200" #AUTOBOOT_FILE = "hda2:/boot/vmlinuz initrd=/boot/initrd ro root=/dev/hda2 console=tty0 console=ttyS0,115200" #AUTOBOOT_FILE = "mem at 0xfff80000" #AUTOBOOT_FILE = "hde1 at 0" AUTOBOOT_FILE = "uda1:/ram0_2.5_2.6.5_k8.2_mydisk7.elf" # Time in second before booting AUTOBOOT_FILE AUTOBOOT_DELAY = 2 # Driver for hard disk, CompactFlash, and CD-ROM on IDE bus IDE_DISK = 1 # Driver for USB disk USB_DISK = 1 # Filesystems # To make filo.zelf < 32 k, You may not enable JFS, MINIX, XFS # Is anyone still using these file system? BY LYH FSYS_EXT2FS = 1 FSYS_FAT = 1 #FSYS_JFS = 1 #FSYS_MINIX = 1 FSYS_REISERFS = 1 #FSYS_XFS = 1 FSYS_ISO9660 = 1 # Support for boot disk image in bootable CD-ROM (El Torito) ELTORITO = 1 # PCI support SUPPORT_PCI = 1 # Debugging #DEBUG_ALL = 1 #DEBUG_ELFBOOT = 1 #DEBUG_ELFNOTE = 1 #DEBUG_LINUXBIOS = 1 #DEBUG_MALLOC = 1 #DEBUG_MULTIBOOT = 1 #DEBUG_SEGMENT = 1 #DEBUG_SYS_INFO = 1 #DEBUG_TIMER = 1 #DEBUG_BLOCKDEV = 1 #DEBUG_PCI = 1 #DEBUG_LINUXLOAD = 1 #DEBUG_IDE = 1 #DEBUG_USB = 1 #DEBUG_ELTORITO = 1 # i386 options # Loader for standard Linux kernel image, a.k.a. /vmlinuz LINUX_LOADER = 1 # Boot FILO from Multiboot loader (eg. GRUB) # You need to modify i386/multiboot.c to use it. change mmrange to e820entries. # By LYH #MULTIBOOT_IMAGE = 1 # Use PCI Configuration Mechanism #1 (most boards) PCI_CONFIG_1 = 1 On Thu, 2004-07-08 at 19:05, Hendricks David W. wrote: > 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 > > 00000008:00000006:00000050 > > 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 (root at tst288xsuse9) #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:rminnich at lanl.gov] > > > 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 > > Linuxbios at clustermatic.org > > http://www.clustermatic.org/mailman/listinfo/linuxbios > > > From YhLu at tyan.com Fri Jul 9 11:30:00 2004 From: YhLu at tyan.com (YhLu) Date: Fri Jul 9 11:30:00 2004 Subject: Filo Error Help Message-ID: <3174569B9743D511922F00A0C9431423055362EF@TYANWEB> Did you try the tg3--filo.zelf I sent to you? YH From daubin at actuality-systems.com Fri Jul 9 13:38:00 2004 From: daubin at actuality-systems.com (David Aubin) Date: Fri Jul 9 13:38:00 2004 Subject: Filo Error Help In-Reply-To: <3174569B9743D511922F00A0C9431423055362EF@TYANWEB> References: <3174569B9743D511922F00A0C9431423055362EF@TYANWEB> Message-ID: <1089400006.12136.44.camel@buildserver1> Hi, Yes, I did, but I don't have a DHCP environment so it kept searching at the DHCP phase. This problem is odd. I can boot my elf fine with etherboot, but not with filo. I can boot my kernel fine with filo, but not the initrd. I can even boot your kernel of the ram.elf you sent me, but when it hits the initrd it fails with the same error as mine. I suspect either my filo is not configured like yours or that there is a problem loading a mulitpart elf (kernel & initrd in filo). I'm confused as to why filo didn't just use the etherboot portion of elf_load. It could be you were on the, "bleeding" edge? ;) Can you tell me how much memory you have in your working system? I have just one cpu and 512meg memory. Curious if loading it high & it runs out of memory or something like that. Thanks, Dave On Fri, 2004-07-09 at 13:05, YhLu wrote: > Did you try the tg3--filo.zelf I sent to you? > > YH > -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: smiley-4.png Type: image/png Size: 822 bytes Desc: not available URL: From YhLu at tyan.com Fri Jul 9 14:13:01 2004 From: YhLu at tyan.com (YhLu) Date: Fri Jul 9 14:13:01 2004 Subject: Filo Error Help Message-ID: <3174569B9743D511922F00A0C943142305A9EA2F@TYANWEB> I have got two cpus and four dimms for every CPU. YH _____ From: David Aubin [mailto:daubin at actuality-systems.com] Sent: Friday, July 09, 2004 12:07 PM To: YhLu Cc: Hendricks David W.; ron minnich; LinuxBIOS Subject: RE: Filo Error Help Hi, Yes, I did, but I don't have a DHCP environment so it kept searching at the DHCP phase. This problem is odd. I can boot my elf fine with etherboot, but not with filo. I can boot my kernel fine with filo, but not the initrd. I can even boot your kernel of the ram.elf you sent me, but when it hits the initrd it fails with the same error as mine. I suspect either my filo is not configured like yours or that there is a problem loading a mulitpart elf (kernel & initrd in filo). I'm confused as to why filo didn't just use the etherboot portion of elf_load. It could be you were on the, "bleeding" edge? ;) Can you tell me how much memory you have in your working system? I have just one cpu and 512meg memory. Curious if loading it high & it runs out of memory or something like that. Thanks, Dave On Fri, 2004-07-09 at 13:05, YhLu wrote: Did you try the tg3--filo.zelf I sent to you? YH -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: image001.gif Type: image/gif Size: 1066 bytes Desc: not available URL: From scheng at msica.com Fri Jul 9 18:23:00 2004 From: scheng at msica.com (Simon Xin Cheng) Date: Fri Jul 9 18:23:00 2004 Subject: Finally, I got filo boot into kernel in hard disk, but ... Message-ID: <63305.24.87.201.99.1089417166.squirrel@www.nome.ca> Hi, Thanks for everyone who helped me building the LinuxBIOS V2 on epia board. I fixed two problems during trying to use FILO to boot a kernel in hard disk. 1) One memory module is broken. I did not use memtest86. It takes too long time. I just remove a very old memory module, the filo can reach the last step. 2) hard disk should be set as MASTER. It has been set as slave. So I got error message: no IDE dev at channel 0. Right now the booting of kernel stopps at initialize AGP stuff, following is the error message before the kernel crashes: ******************************************** Initializing Cryptographic API Real Time Clock Driver v1.12 Linux agpgart interface v0.100 (c) Dave Jones agpgart: Detected VIA Apollo MVP4 chipset agpgart: Maximum main memory to use for agp memory: 96M 0 LinuxBIOS-1.1.6.0Fallback Fri Jul 9 14:06:03 PDT 2004 starting... *********************************************** I have several questions: 1) DO i need to enable GP_APERTURE_SIZE? And how to set the value? (i.e. by byte or M ) 2) Does the kernel need patch? Right now, I am using 2.6.7 pure kernel. Thanks a lot. Simon Cheng www.msica.com From daubin at actuality-systems.com Mon Jul 12 14:21:00 2004 From: daubin at actuality-systems.com (David Aubin) Date: Mon Jul 12 14:21:00 2004 Subject: Filo Error Help In-Reply-To: <3174569B9743D511922F00A0C943142305A9EA2F@TYANWEB> References: <3174569B9743D511922F00A0C943142305A9EA2F@TYANWEB> Message-ID: <1089661821.5608.8.camel@buildserver1> Hi, I am unable to get my kernel & initrd off of the usb stick. I was reading through the documents and came across this line in README.etherboot_in_filo: You can not use filo and ide_disk at the same time. Can you tell me what this means? Do I need to rebuild filo without IDE support to get USB support? Just to recap: My kernel & initrd fails as the initrd execution complaining of a bad CRC when I use the elf as a payload to load with with filo. I then try uda1:/kernel initrd=/boot/initrd root=/dev/sda1 and I get those td errors. I then tried your ramfs.elf and I get the same behavior are my elf image with the CRC complaining when the initrd portion is executed. Note, I have confirmed my elf works with etherboot, just not filo yet.... The CRC error makes me think that the image did not get loaded correctly by the elf boot. Can you confirm you used Eric's mkelfImage2-5? Here is my dump of the readelf -a. ELF Header: Magic: 7f 45 4c 46 01 01 01 00 00 00 00 00 00 00 00 00 Class: ELF32 Data: 2's complement, little endian Version: 1 (current) OS/ABI: UNIX - System V ABI Version: 0 Type: EXEC (Executable file) Machine: Intel 80386 Version: 0x1 Entry point address: 0x10000 Start of program headers: 52 (bytes into file) Start of section headers: 0 (bytes into file) Flags: 0x0 Size of this header: 52 (bytes) Size of program headers: 32 (bytes) Number of program headers: 5 Size of section headers: 0 (bytes) Number of section headers: 0 Section header string table index: 0 There are no sections in this file. Program Headers: Type Offset VirtAddr PhysAddr FileSiz MemSiz Flg Align NOTE 0x0000d4 0x00000000 0x00000000 0x00088 0x00088 RWE 0 LOAD 0x00015c 0x00010000 0x00010000 0x0559c 0x1aa24 RWE 0 LOAD 0x0056f8 0x00091000 0x00091000 0x00000 0x00070 RWE 0 LOAD 0x0056f8 0x00100000 0x00100000 0x1a952a 0x700000 RWE 0 LOAD 0x1aec22 0x00800000 0x00800000 0x2769f5 0x2769f5 RWE 0 There is no dynamic segment in this file. There are no relocations in this file. There are no unwind sections in this file. No version information found in this file. Thanks, Dave On Fri, 2004-07-09 at 15:48, YhLu wrote: > I have got two cpus and four dimms for every CPU. > > > > YH > > > > > ______________________________________________________________________ > > From:David Aubin [mailto:daubin at actuality-systems.com] > Sent: Friday, July 09, 2004 12:07 PM > To: YhLu > Cc: Hendricks David W.; ron minnich; LinuxBIOS > Subject: RE: Filo Error Help > > > > > Hi, > > Yes, I did, but I don't have a DHCP environment so it kept searching > at the DHCP phase. > > This problem is odd. I can boot my elf fine with etherboot, but not > with filo. I can boot > my kernel fine with filo, but not the initrd. I can even boot your > kernel of the ram.elf you > sent me, but when it hits the initrd it fails with the same error as > mine. > > I suspect either my filo is not configured like yours or that there > is a problem loading a > mulitpart elf (kernel & initrd in filo). I'm confused as to why filo > didn't just use the etherboot > portion of elf_load. It could be you were on the, "bleeding" edge? > ;) > > Can you tell me how much memory you have in your working system? I > have just > one cpu and 512meg memory. Curious if loading it high & it runs out > of memory or > something like that. > > Thanks, > Dave > > > On Fri, 2004-07-09 at 13:05, YhLu wrote: > > > Did you try the tg3--filo.zelf I sent to you? > > YH -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: image001.gif Type: image/gif Size: 1066 bytes Desc: not available URL: From daubin at actuality-systems.com Mon Jul 12 14:27:00 2004 From: daubin at actuality-systems.com (David Aubin) Date: Mon Jul 12 14:27:00 2004 Subject: Filo Error Help In-Reply-To: <3174569B9743D511922F00A0C943142305A9EAE1@TYANWEB> References: <3174569B9743D511922F00A0C943142305A9EAE1@TYANWEB> Message-ID: <1089662209.5608.10.camel@buildserver1> Ah, I got ya. Yes, I do. I'll let you know, if that worked. Thanks, Dave On Mon, 2004-07-12 at 16:01, YhLu wrote: > I mean if you build tg3?filo?ide_disk.zelf, it will confuse the > Etherboot. So you can only build tg3?filo.zelf or tg3?ide_disk.zelf. > > > > Do you have spare IDE disk? If So format the disk into ext3 or fat > format and copy the .elf file into it. > > > > Then connect that to your MB do test. > > > > hda1:/ram0_......elf > > > > Regards > > > > YH > > > > > ______________________________________________________________________ > > From:David Aubin [mailto:daubin at actuality-systems.com] > Sent: Monday, July 12, 2004 12:50 PM > To: YhLu > Cc: Hendricks David W.; ron minnich; LinuxBIOS > Subject: RE: Filo Error Help > > > > > Hi, > > I am unable to get my kernel & initrd off of the usb stick. I was > reading > through the documents and came across this line in > README.etherboot_in_filo: > You can not use filo and ide_disk at the same time. > > Can you tell me what this means? Do I need to rebuild filo without > IDE > support to get USB support? > > Just to recap: My kernel & initrd fails as the initrd execution > complaining of > a bad CRC when I use the elf as a payload to load with with filo. I > then try > uda1:/kernel initrd=/boot/initrd root=/dev/sda1 and I get those td > errors. I then > tried your ramfs.elf and I get the same behavior are my elf image with > the CRC > complaining when the initrd portion is executed. Note, I have > confirmed my elf > works with etherboot, just not filo yet.... > > The CRC error makes me think that the image did not get loaded > correctly > by the elf boot. Can you confirm you used Eric's mkelfImage2-5? Here > is > my dump of the readelf -a. > > ELF Header: > Magic: 7f 45 4c 46 01 01 01 00 00 00 00 00 00 00 00 00 > Class: ELF32 > Data: 2's complement, little endian > Version: 1 (current) > OS/ABI: UNIX - System V > ABI Version: 0 > Type: EXEC (Executable file) > Machine: Intel 80386 > Version: 0x1 > Entry point address: 0x10000 > Start of program headers: 52 (bytes into file) > Start of section headers: 0 (bytes into file) > Flags: 0x0 > Size of this header: 52 (bytes) > Size of program headers: 32 (bytes) > Number of program headers: 5 > Size of section headers: 0 (bytes) > Number of section headers: 0 > Section header string table index: 0 > > There are no sections in this file. > > Program Headers: > Type Offset VirtAddr PhysAddr FileSiz MemSiz Flg > Align > NOTE 0x0000d4 0x00000000 0x00000000 0x00088 0x00088 RWE 0 > LOAD 0x00015c 0x00010000 0x00010000 0x0559c 0x1aa24 RWE 0 > LOAD 0x0056f8 0x00091000 0x00091000 0x00000 0x00070 RWE 0 > LOAD 0x0056f8 0x00100000 0x00100000 0x1a952a 0x700000 RWE > 0 > LOAD 0x1aec22 0x00800000 0x00800000 0x2769f5 0x2769f5 RWE > 0 > > There is no dynamic segment in this file. > > There are no relocations in this file. > > There are no unwind sections in this file. > > No version information found in this file. > > > Thanks, > Dave > > On Fri, 2004-07-09 at 15:48, YhLu wrote: > > I have got two cpus and four dimms for every CPU. > > > > YH > > > > > ______________________________________________________________________ > > > > From:David Aubin [mailto:daubin at actuality-systems.com] > Sent: Friday, July 09, 2004 12:07 PM > To: YhLu > Cc: Hendricks David W.; ron minnich; LinuxBIOS > Subject: RE: Filo Error Help > > > > > Hi, > > Yes, I did, but I don't have a DHCP environment so it kept searching > at the DHCP phase. > > This problem is odd. I can boot my elf fine with etherboot, but not > with filo. I can boot > my kernel fine with filo, but not the initrd. I can even boot your > kernel of the ram.elf you > sent me, but when it hits the initrd it fails with the same error as > mine. > > I suspect either my filo is not configured like yours or that there > is a problem loading a > mulitpart elf (kernel & initrd in filo). I'm confused as to why filo > didn't just use the etherboot > portion of elf_load. It could be you were on the, "bleeding" edge? > ;) > > Can you tell me how much memory you have in your working system? I > have just > one cpu and 512meg memory. Curious if loading it high & it runs out > of memory or > something like that. > > Thanks, > Dave > > > On Fri, 2004-07-09 at 13:05, YhLu wrote: > > > Did you try the tg3--filo.zelf I sent to you? > > YH -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: image001.gif Type: image/gif Size: 1066 bytes Desc: not available URL: From YhLu at tyan.com Mon Jul 12 14:29:10 2004 From: YhLu at tyan.com (YhLu) Date: Mon Jul 12 14:29:10 2004 Subject: Filo Error Help Message-ID: <3174569B9743D511922F00A0C943142305A9EAE1@TYANWEB> I mean if you build tg3filoide_disk.zelf, it will confuse the Etherboot. So you can only build tg3filo.zelf or tg3ide_disk.zelf. Do you have spare IDE disk? If So format the disk into ext3 or fat format and copy the .elf file into it. Then connect that to your MB do test. hda1:/ram0_......elf Regards YH _____ From: David Aubin [mailto:daubin at actuality-systems.com] Sent: Monday, July 12, 2004 12:50 PM To: YhLu Cc: Hendricks David W.; ron minnich; LinuxBIOS Subject: RE: Filo Error Help Hi, I am unable to get my kernel & initrd off of the usb stick. I was reading through the documents and came across this line in README.etherboot_in_filo: You can not use filo and ide_disk at the same time. Can you tell me what this means? Do I need to rebuild filo without IDE support to get USB support? Just to recap: My kernel & initrd fails as the initrd execution complaining of a bad CRC when I use the elf as a payload to load with with filo. I then try uda1:/kernel initrd=/boot/initrd root=/dev/sda1 and I get those td errors. I then tried your ramfs.elf and I get the same behavior are my elf image with the CRC complaining when the initrd portion is executed. Note, I have confirmed my elf works with etherboot, just not filo yet.... The CRC error makes me think that the image did not get loaded correctly by the elf boot. Can you confirm you used Eric's mkelfImage2-5? Here is my dump of the readelf -a. ELF Header: Magic: 7f 45 4c 46 01 01 01 00 00 00 00 00 00 00 00 00 Class: ELF32 Data: 2's complement, little endian Version: 1 (current) OS/ABI: UNIX - System V ABI Version: 0 Type: EXEC (Executable file) Machine: Intel 80386 Version: 0x1 Entry point address: 0x10000 Start of program headers: 52 (bytes into file) Start of section headers: 0 (bytes into file) Flags: 0x0 Size of this header: 52 (bytes) Size of program headers: 32 (bytes) Number of program headers: 5 Size of section headers: 0 (bytes) Number of section headers: 0 Section header string table index: 0 There are no sections in this file. Program Headers: Type Offset VirtAddr PhysAddr FileSiz MemSiz Flg Align NOTE 0x0000d4 0x00000000 0x00000000 0x00088 0x00088 RWE 0 LOAD 0x00015c 0x00010000 0x00010000 0x0559c 0x1aa24 RWE 0 LOAD 0x0056f8 0x00091000 0x00091000 0x00000 0x00070 RWE 0 LOAD 0x0056f8 0x00100000 0x00100000 0x1a952a 0x700000 RWE 0 LOAD 0x1aec22 0x00800000 0x00800000 0x2769f5 0x2769f5 RWE 0 There is no dynamic segment in this file. There are no relocations in this file. There are no unwind sections in this file. No version information found in this file. Thanks, Dave On Fri, 2004-07-09 at 15:48, YhLu wrote: I have got two cpus and four dimms for every CPU. YH _____ From:David Aubin [mailto:daubin at actuality-systems.com] Sent: Friday, July 09, 2004 12:07 PM To: YhLu Cc: Hendricks David W.; ron minnich; LinuxBIOS Subject: RE: Filo Error Help Hi, Yes, I did, but I don't have a DHCP environment so it kept searching at the DHCP phase. This problem is odd. I can boot my elf fine with etherboot, but not with filo. I can boot my kernel fine with filo, but not the initrd. I can even boot your kernel of the ram.elf you sent me, but when it hits the initrd it fails with the same error as mine. I suspect either my filo is not configured like yours or that there is a problem loading a mulitpart elf (kernel & initrd in filo). I'm confused as to why filo didn't just use the etherboot portion of elf_load. It could be you were on the, "bleeding" edge? ;) Can you tell me how much memory you have in your working system? I have just one cpu and 512meg memory. Curious if loading it high & it runs out of memory or something like that. Thanks, Dave On Fri, 2004-07-09 at 13:05, YhLu wrote: Did you try the tg3--filo.zelf I sent to you? YH -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: image001.gif Type: image/gif Size: 1066 bytes Desc: not available URL: From daubin at actuality-systems.com Mon Jul 12 15:45:00 2004 From: daubin at actuality-systems.com (David Aubin) Date: Mon Jul 12 15:45:00 2004 Subject: Filo Error Help In-Reply-To: <3174569B9743D511922F00A0C943142305A9EAE1@TYANWEB> References: <3174569B9743D511922F00A0C943142305A9EAE1@TYANWEB> Message-ID: <1089666879.10642.36.camel@buildserver1> Here are the results: I took my known working hard drive and stuck it in the device to test with filo. The results were the same! Meaning a known working kernel & intird on my hard drive failed at the initrd portion, again with the crc error. I'm now going to try a basic etherboot test without filo to see if I can read off of the hard drive, just as a baseline. Any other ideas would be appreciated. Thanks, Dave On Mon, 2004-07-12 at 16:01, YhLu wrote: > I mean if you build tg3?filo?ide_disk.zelf, it will confuse the > Etherboot. So you can only build tg3?filo.zelf or tg3?ide_disk.zelf. > > > > Do you have spare IDE disk? If So format the disk into ext3 or fat > format and copy the .elf file into it. > > > > Then connect that to your MB do test. > > > > hda1:/ram0_......elf > > > > Regards > > > > YH > > > > > ______________________________________________________________________ > > From:David Aubin [mailto:daubin at actuality-systems.com] > Sent: Monday, July 12, 2004 12:50 PM > To: YhLu > Cc: Hendricks David W.; ron minnich; LinuxBIOS > Subject: RE: Filo Error Help > > > > > Hi, > > I am unable to get my kernel & initrd off of the usb stick. I was > reading > through the documents and came across this line in > README.etherboot_in_filo: > You can not use filo and ide_disk at the same time. > > Can you tell me what this means? Do I need to rebuild filo without > IDE > support to get USB support? > > Just to recap: My kernel & initrd fails as the initrd execution > complaining of > a bad CRC when I use the elf as a payload to load with with filo. I > then try > uda1:/kernel initrd=/boot/initrd root=/dev/sda1 and I get those td > errors. I then > tried your ramfs.elf and I get the same behavior are my elf image with > the CRC > complaining when the initrd portion is executed. Note, I have > confirmed my elf > works with etherboot, just not filo yet.... > > The CRC error makes me think that the image did not get loaded > correctly > by the elf boot. Can you confirm you used Eric's mkelfImage2-5? Here > is > my dump of the readelf -a. > > ELF Header: > Magic: 7f 45 4c 46 01 01 01 00 00 00 00 00 00 00 00 00 > Class: ELF32 > Data: 2's complement, little endian > Version: 1 (current) > OS/ABI: UNIX - System V > ABI Version: 0 > Type: EXEC (Executable file) > Machine: Intel 80386 > Version: 0x1 > Entry point address: 0x10000 > Start of program headers: 52 (bytes into file) > Start of section headers: 0 (bytes into file) > Flags: 0x0 > Size of this header: 52 (bytes) > Size of program headers: 32 (bytes) > Number of program headers: 5 > Size of section headers: 0 (bytes) > Number of section headers: 0 > Section header string table index: 0 > > There are no sections in this file. > > Program Headers: > Type Offset VirtAddr PhysAddr FileSiz MemSiz Flg > Align > NOTE 0x0000d4 0x00000000 0x00000000 0x00088 0x00088 RWE 0 > LOAD 0x00015c 0x00010000 0x00010000 0x0559c 0x1aa24 RWE 0 > LOAD 0x0056f8 0x00091000 0x00091000 0x00000 0x00070 RWE 0 > LOAD 0x0056f8 0x00100000 0x00100000 0x1a952a 0x700000 RWE > 0 > LOAD 0x1aec22 0x00800000 0x00800000 0x2769f5 0x2769f5 RWE > 0 > > There is no dynamic segment in this file. > > There are no relocations in this file. > > There are no unwind sections in this file. > > No version information found in this file. > > > Thanks, > Dave > > On Fri, 2004-07-09 at 15:48, YhLu wrote: > > I have got two cpus and four dimms for every CPU. > > > > YH > > > > > ______________________________________________________________________ > > > > From:David Aubin [mailto:daubin at actuality-systems.com] > Sent: Friday, July 09, 2004 12:07 PM > To: YhLu > Cc: Hendricks David W.; ron minnich; LinuxBIOS > Subject: RE: Filo Error Help > > > > > Hi, > > Yes, I did, but I don't have a DHCP environment so it kept searching > at the DHCP phase. > > This problem is odd. I can boot my elf fine with etherboot, but not > with filo. I can boot > my kernel fine with filo, but not the initrd. I can even boot your > kernel of the ram.elf you > sent me, but when it hits the initrd it fails with the same error as > mine. > > I suspect either my filo is not configured like yours or that there > is a problem loading a > mulitpart elf (kernel & initrd in filo). I'm confused as to why filo > didn't just use the etherboot > portion of elf_load. It could be you were on the, "bleeding" edge? > ;) > > Can you tell me how much memory you have in your working system? I > have just > one cpu and 512meg memory. Curious if loading it high & it runs out > of memory or > something like that. > > Thanks, > Dave > > > On Fri, 2004-07-09 at 13:05, YhLu wrote: > > > Did you try the tg3--filo.zelf I sent to you? > > YH -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: image001.gif Type: image/gif Size: 1066 bytes Desc: not available URL: From scheng at msica.com Mon Jul 12 19:00:01 2004 From: scheng at msica.com (Simon Xin Cheng) Date: Mon Jul 12 19:00:01 2004 Subject: Does LinuxBIOS V2 support AGP (vedio card) for via/epia board Message-ID: <61394.24.87.201.99.1089678627.squirrel@www.nome.ca> I successfully boot Linux kernel 2.6.7 by LinuxBIOS V2 + filo. However, I have to disable AGP support in the kernel because I got some errors when Kernel initialized agpgart. I checked the source code. It seems that AGP is not supported for via/epia board either in V1 or in V2. Am I right? How can I obtain AGP support? I need Xwindow. Thanks. Simon Cheng www.msica.com From ts1 at tsn.or.jp Mon Jul 12 20:25:01 2004 From: ts1 at tsn.or.jp (Takeshi Sone) Date: Mon Jul 12 20:25:01 2004 Subject: Filo Error Help In-Reply-To: <1089666879.10642.36.camel@buildserver1> References: <3174569B9743D511922F00A0C943142305A9EAE1@TYANWEB> <1089666879.10642.36.camel@buildserver1> Message-ID: <20040713015600.GA8220@tsn.or.jp> Can you try out my FILO? (http://te.to/~ts1/filo/) If it works, it might help narrow the problem. On Mon, Jul 12, 2004 at 05:14:39PM -0400, David Aubin wrote: > Here are the results: > > I took my known working hard drive and stuck it in the device to test > with filo. > The results were the same! Meaning a known working kernel & intird on > my hard drive failed at the initrd portion, again with the crc error. > > I'm now going to try a basic etherboot test without filo to see if I can > read off of the > hard drive, just as a baseline. > > Any other ideas would be appreciated. > > Thanks, > Dave > > On Mon, 2004-07-12 at 16:01, YhLu wrote: > > > I mean if you build tg3?filo?ide_disk.zelf, it will confuse the > > Etherboot. So you can only build tg3?filo.zelf or tg3?ide_disk.zelf. > > > > > > > > Do you have spare IDE disk? If So format the disk into ext3 or fat > > format and copy the .elf file into it. > > > > > > > > Then connect that to your MB do test. > > > > > > > > hda1:/ram0_......elf > > > > > > > > Regards > > > > > > > > YH > > > > > > > > > > ______________________________________________________________________ > > > > From:David Aubin [mailto:daubin at actuality-systems.com] > > Sent: Monday, July 12, 2004 12:50 PM > > To: YhLu > > Cc: Hendricks David W.; ron minnich; LinuxBIOS > > Subject: RE: Filo Error Help > > > > > > > > > > Hi, > > > > I am unable to get my kernel & initrd off of the usb stick. I was > > reading > > through the documents and came across this line in > > README.etherboot_in_filo: > > You can not use filo and ide_disk at the same time. > > > > Can you tell me what this means? Do I need to rebuild filo without > > IDE > > support to get USB support? > > > > Just to recap: My kernel & initrd fails as the initrd execution > > complaining of > > a bad CRC when I use the elf as a payload to load with with filo. I > > then try > > uda1:/kernel initrd=/boot/initrd root=/dev/sda1 and I get those td > > errors. I then > > tried your ramfs.elf and I get the same behavior are my elf image with > > the CRC > > complaining when the initrd portion is executed. Note, I have > > confirmed my elf > > works with etherboot, just not filo yet.... > > > > The CRC error makes me think that the image did not get loaded > > correctly > > by the elf boot. Can you confirm you used Eric's mkelfImage2-5? Here > > is > > my dump of the readelf -a. > > > > ELF Header: > > Magic: 7f 45 4c 46 01 01 01 00 00 00 00 00 00 00 00 00 > > Class: ELF32 > > Data: 2's complement, little endian > > Version: 1 (current) > > OS/ABI: UNIX - System V > > ABI Version: 0 > > Type: EXEC (Executable file) > > Machine: Intel 80386 > > Version: 0x1 > > Entry point address: 0x10000 > > Start of program headers: 52 (bytes into file) > > Start of section headers: 0 (bytes into file) > > Flags: 0x0 > > Size of this header: 52 (bytes) > > Size of program headers: 32 (bytes) > > Number of program headers: 5 > > Size of section headers: 0 (bytes) > > Number of section headers: 0 > > Section header string table index: 0 > > > > There are no sections in this file. > > > > Program Headers: > > Type Offset VirtAddr PhysAddr FileSiz MemSiz Flg > > Align > > NOTE 0x0000d4 0x00000000 0x00000000 0x00088 0x00088 RWE 0 > > LOAD 0x00015c 0x00010000 0x00010000 0x0559c 0x1aa24 RWE 0 > > LOAD 0x0056f8 0x00091000 0x00091000 0x00000 0x00070 RWE 0 > > LOAD 0x0056f8 0x00100000 0x00100000 0x1a952a 0x700000 RWE > > 0 > > LOAD 0x1aec22 0x00800000 0x00800000 0x2769f5 0x2769f5 RWE > > 0 > > > > There is no dynamic segment in this file. > > > > There are no relocations in this file. > > > > There are no unwind sections in this file. > > > > No version information found in this file. > > > > > > Thanks, > > Dave > > > > On Fri, 2004-07-09 at 15:48, YhLu wrote: > > > > I have got two cpus and four dimms for every CPU. > > > > > > > > YH > > > > > > > > > > ______________________________________________________________________ > > > > > > > > From:David Aubin [mailto:daubin at actuality-systems.com] > > Sent: Friday, July 09, 2004 12:07 PM > > To: YhLu > > Cc: Hendricks David W.; ron minnich; LinuxBIOS > > Subject: RE: Filo Error Help > > > > > > > > > > Hi, > > > > Yes, I did, but I don't have a DHCP environment so it kept searching > > at the DHCP phase. > > > > This problem is odd. I can boot my elf fine with etherboot, but not > > with filo. I can boot > > my kernel fine with filo, but not the initrd. I can even boot your > > kernel of the ram.elf you > > sent me, but when it hits the initrd it fails with the same error as > > mine. > > > > I suspect either my filo is not configured like yours or that there > > is a problem loading a > > mulitpart elf (kernel & initrd in filo). I'm confused as to why filo > > didn't just use the etherboot > > portion of elf_load. It could be you were on the, "bleeding" edge? > > ;) > > > > Can you tell me how much memory you have in your working system? I > > have just > > one cpu and 512meg memory. Curious if loading it high & it runs out > > of memory or > > something like that. > > > > Thanks, > > Dave > > > > > > On Fri, 2004-07-09 at 13:05, YhLu wrote: > > > > > > Did you try the tg3--filo.zelf I sent to you? > > > > YH -- Takeshi From YhLu at tyan.com Mon Jul 12 20:29:01 2004 From: YhLu at tyan.com (YhLu) Date: Mon Jul 12 20:29:01 2004 Subject: Filo Error Help Message-ID: <3174569B9743D511922F00A0C943142305A9EB59@TYANWEB> Good idea. -----Original Message----- From: Takeshi Sone [mailto:ts1 at tsn.or.jp] Sent: Monday, July 12, 2004 6:56 PM To: David Aubin Cc: YhLu; Hendricks David W.; ron minnich; LinuxBIOS Subject: Re: Filo Error Help Can you try out my FILO? (http://te.to/~ts1/filo/) If it works, it might help narrow the problem. On Mon, Jul 12, 2004 at 05:14:39PM -0400, David Aubin wrote: > Here are the results: > > I took my known working hard drive and stuck it in the device to test > with filo. > The results were the same! Meaning a known working kernel & intird on > my hard drive failed at the initrd portion, again with the crc error. > > I'm now going to try a basic etherboot test without filo to see if I can > read off of the > hard drive, just as a baseline. > > Any other ideas would be appreciated. > > Thanks, > Dave > > On Mon, 2004-07-12 at 16:01, YhLu wrote: > > > I mean if you build tg3?filo?ide_disk.zelf, it will confuse the > > Etherboot. So you can only build tg3?filo.zelf or tg3?ide_disk.zelf. > > > > > > > > Do you have spare IDE disk? If So format the disk into ext3 or fat > > format and copy the .elf file into it. > > > > > > > > Then connect that to your MB do test. > > > > > > > > hda1:/ram0_......elf > > > > > > > > Regards > > > > > > > > YH > > > > > > > > > > ______________________________________________________________________ > > > > From:David Aubin [mailto:daubin at actuality-systems.com] > > Sent: Monday, July 12, 2004 12:50 PM > > To: YhLu > > Cc: Hendricks David W.; ron minnich; LinuxBIOS > > Subject: RE: Filo Error Help > > > > > > > > > > Hi, > > > > I am unable to get my kernel & initrd off of the usb stick. I was > > reading > > through the documents and came across this line in > > README.etherboot_in_filo: > > You can not use filo and ide_disk at the same time. > > > > Can you tell me what this means? Do I need to rebuild filo without > > IDE > > support to get USB support? > > > > Just to recap: My kernel & initrd fails as the initrd execution > > complaining of > > a bad CRC when I use the elf as a payload to load with with filo. I > > then try > > uda1:/kernel initrd=/boot/initrd root=/dev/sda1 and I get those td > > errors. I then > > tried your ramfs.elf and I get the same behavior are my elf image with > > the CRC > > complaining when the initrd portion is executed. Note, I have > > confirmed my elf > > works with etherboot, just not filo yet.... > > > > The CRC error makes me think that the image did not get loaded > > correctly > > by the elf boot. Can you confirm you used Eric's mkelfImage2-5? Here > > is > > my dump of the readelf -a. > > > > ELF Header: > > Magic: 7f 45 4c 46 01 01 01 00 00 00 00 00 00 00 00 00 > > Class: ELF32 > > Data: 2's complement, little endian > > Version: 1 (current) > > OS/ABI: UNIX - System V > > ABI Version: 0 > > Type: EXEC (Executable file) > > Machine: Intel 80386 > > Version: 0x1 > > Entry point address: 0x10000 > > Start of program headers: 52 (bytes into file) > > Start of section headers: 0 (bytes into file) > > Flags: 0x0 > > Size of this header: 52 (bytes) > > Size of program headers: 32 (bytes) > > Number of program headers: 5 > > Size of section headers: 0 (bytes) > > Number of section headers: 0 > > Section header string table index: 0 > > > > There are no sections in this file. > > > > Program Headers: > > Type Offset VirtAddr PhysAddr FileSiz MemSiz Flg > > Align > > NOTE 0x0000d4 0x00000000 0x00000000 0x00088 0x00088 RWE 0 > > LOAD 0x00015c 0x00010000 0x00010000 0x0559c 0x1aa24 RWE 0 > > LOAD 0x0056f8 0x00091000 0x00091000 0x00000 0x00070 RWE 0 > > LOAD 0x0056f8 0x00100000 0x00100000 0x1a952a 0x700000 RWE > > 0 > > LOAD 0x1aec22 0x00800000 0x00800000 0x2769f5 0x2769f5 RWE > > 0 > > > > There is no dynamic segment in this file. > > > > There are no relocations in this file. > > > > There are no unwind sections in this file. > > > > No version information found in this file. > > > > > > Thanks, > > Dave > > > > On Fri, 2004-07-09 at 15:48, YhLu wrote: > > > > I have got two cpus and four dimms for every CPU. > > > > > > > > YH > > > > > > > > > > ______________________________________________________________________ > > > > > > > > From:David Aubin [mailto:daubin at actuality-systems.com] > > Sent: Friday, July 09, 2004 12:07 PM > > To: YhLu > > Cc: Hendricks David W.; ron minnich; LinuxBIOS > > Subject: RE: Filo Error Help > > > > > > > > > > Hi, > > > > Yes, I did, but I don't have a DHCP environment so it kept searching > > at the DHCP phase. > > > > This problem is odd. I can boot my elf fine with etherboot, but not > > with filo. I can boot > > my kernel fine with filo, but not the initrd. I can even boot your > > kernel of the ram.elf you > > sent me, but when it hits the initrd it fails with the same error as > > mine. > > > > I suspect either my filo is not configured like yours or that there > > is a problem loading a > > mulitpart elf (kernel & initrd in filo). I'm confused as to why filo > > didn't just use the etherboot > > portion of elf_load. It could be you were on the, "bleeding" edge? > > ;) > > > > Can you tell me how much memory you have in your working system? I > > have just > > one cpu and 512meg memory. Curious if loading it high & it runs out > > of memory or > > something like that. > > > > Thanks, > > Dave > > > > > > On Fri, 2004-07-09 at 13:05, YhLu wrote: > > > > > > Did you try the tg3--filo.zelf I sent to you? > > > > YH -- Takeshi From ebiederman at lnxi.com Tue Jul 13 00:09:01 2004 From: ebiederman at lnxi.com (Eric W. Biederman) Date: Tue Jul 13 00:09:01 2004 Subject: CPU refactoring status.... In-Reply-To: References: Message-ID: ron minnich writes: > On 8 Jul 2004, Eric W. Biederman wrote: > > > Ron does a branch sound good? > > works for me! While attempting to tag the tree early today to create a branch I ran into a problem. It appears Stefan has one of CVS's internal locks on src/cpu/p5 and so I can't get past that.... It is probably just CVS messed up somewhere but anyway. I will look back tomorrow and see what I can accomplish. Eric From zhushisongzhu at yahoo.com Tue Jul 13 06:06:00 2004 From: zhushisongzhu at yahoo.com (zhu shi song) Date: Tue Jul 13 06:06:00 2004 Subject: question about via 82c686b, 82c686, vt8601 , vt8601t Message-ID: <20040713113718.44523.qmail@web13201.mail.yahoo.com> dear sir, I've got one mainboard. Its northbridge is vt8601t, southbridge is 82c686b. I checked freebios source , there exists mainboard vt5426 which is very near my configuration. the northbridge and southbridge of vt5426 are seperately vt8601 and 82c686. Who know the difference between them? By the way , where can I get the manual of vt8601t and 82c686b? I have checked via website, there is no deep technical information about them. tks zhu --------------------------------- Do you Yahoo!? Yahoo! Mail Address AutoComplete - You start. We finish. -------------- next part -------------- An HTML attachment was scrubbed... URL: From daubin at actuality-systems.com Tue Jul 13 06:52:00 2004 From: daubin at actuality-systems.com (David Aubin) Date: Tue Jul 13 06:52:00 2004 Subject: Filo Error Help In-Reply-To: <20040713015600.GA8220@tsn.or.jp> References: <3174569B9743D511922F00A0C943142305A9EAE1@TYANWEB> <1089666879.10642.36.camel@buildserver1> <20040713015600.GA8220@tsn.or.jp> Message-ID: <1089721301.24650.0.camel@buildserver1> Yes, yes indeed I will try it and Thank you:) On Mon, 2004-07-12 at 21:56, Takeshi Sone wrote: > Can you try out my FILO? (http://te.to/~ts1/filo/) > If it works, it might help narrow the problem. > > On Mon, Jul 12, 2004 at 05:14:39PM -0400, David Aubin wrote: > > Here are the results: > > > > I took my known working hard drive and stuck it in the device to test > > with filo. > > The results were the same! Meaning a known working kernel & intird on > > my hard drive failed at the initrd portion, again with the crc error. > > > > I'm now going to try a basic etherboot test without filo to see if I can > > read off of the > > hard drive, just as a baseline. > > > > Any other ideas would be appreciated. > > > > Thanks, > > Dave > > > > On Mon, 2004-07-12 at 16:01, YhLu wrote: > > > > > I mean if you build tg3?filo?ide_disk.zelf, it will confuse the > > > Etherboot. So you can only build tg3?filo.zelf or tg3?ide_disk.zelf. > > > > > > > > > > > > Do you have spare IDE disk? If So format the disk into ext3 or fat > > > format and copy the .elf file into it. > > > > > > > > > > > > Then connect that to your MB do test. > > > > > > > > > > > > hda1:/ram0_......elf > > > > > > > > > > > > Regards > > > > > > > > > > > > YH > > > > > > > > > > > > > > > ______________________________________________________________________ > > > > > > From:David Aubin [mailto:daubin at actuality-systems.com] > > > Sent: Monday, July 12, 2004 12:50 PM > > > To: YhLu > > > Cc: Hendricks David W.; ron minnich; LinuxBIOS > > > Subject: RE: Filo Error Help > > > > > > > > > > > > > > > Hi, > > > > > > I am unable to get my kernel & initrd off of the usb stick. I was > > > reading > > > through the documents and came across this line in > > > README.etherboot_in_filo: > > > You can not use filo and ide_disk at the same time. > > > > > > Can you tell me what this means? Do I need to rebuild filo without > > > IDE > > > support to get USB support? > > > > > > Just to recap: My kernel & initrd fails as the initrd execution > > > complaining of > > > a bad CRC when I use the elf as a payload to load with with filo. I > > > then try > > > uda1:/kernel initrd=/boot/initrd root=/dev/sda1 and I get those td > > > errors. I then > > > tried your ramfs.elf and I get the same behavior are my elf image with > > > the CRC > > > complaining when the initrd portion is executed. Note, I have > > > confirmed my elf > > > works with etherboot, just not filo yet.... > > > > > > The CRC error makes me think that the image did not get loaded > > > correctly > > > by the elf boot. Can you confirm you used Eric's mkelfImage2-5? Here > > > is > > > my dump of the readelf -a. > > > > > > ELF Header: > > > Magic: 7f 45 4c 46 01 01 01 00 00 00 00 00 00 00 00 00 > > > Class: ELF32 > > > Data: 2's complement, little endian > > > Version: 1 (current) > > > OS/ABI: UNIX - System V > > > ABI Version: 0 > > > Type: EXEC (Executable file) > > > Machine: Intel 80386 > > > Version: 0x1 > > > Entry point address: 0x10000 > > > Start of program headers: 52 (bytes into file) > > > Start of section headers: 0 (bytes into file) > > > Flags: 0x0 > > > Size of this header: 52 (bytes) > > > Size of program headers: 32 (bytes) > > > Number of program headers: 5 > > > Size of section headers: 0 (bytes) > > > Number of section headers: 0 > > > Section header string table index: 0 > > > > > > There are no sections in this file. > > > > > > Program Headers: > > > Type Offset VirtAddr PhysAddr FileSiz MemSiz Flg > > > Align > > > NOTE 0x0000d4 0x00000000 0x00000000 0x00088 0x00088 RWE 0 > > > LOAD 0x00015c 0x00010000 0x00010000 0x0559c 0x1aa24 RWE 0 > > > LOAD 0x0056f8 0x00091000 0x00091000 0x00000 0x00070 RWE 0 > > > LOAD 0x0056f8 0x00100000 0x00100000 0x1a952a 0x700000 RWE > > > 0 > > > LOAD 0x1aec22 0x00800000 0x00800000 0x2769f5 0x2769f5 RWE > > > 0 > > > > > > There is no dynamic segment in this file. > > > > > > There are no relocations in this file. > > > > > > There are no unwind sections in this file. > > > > > > No version information found in this file. > > > > > > > > > Thanks, > > > Dave > > > > > > On Fri, 2004-07-09 at 15:48, YhLu wrote: > > > > > > I have got two cpus and four dimms for every CPU. > > > > > > > > > > > > YH > > > > > > > > > > > > > > > ______________________________________________________________________ > > > > > > > > > > > > From:David Aubin [mailto:daubin at actuality-systems.com] > > > Sent: Friday, July 09, 2004 12:07 PM > > > To: YhLu > > > Cc: Hendricks David W.; ron minnich; LinuxBIOS > > > Subject: RE: Filo Error Help > > > > > > > > > > > > > > > Hi, > > > > > > Yes, I did, but I don't have a DHCP environment so it kept searching > > > at the DHCP phase. > > > > > > This problem is odd. I can boot my elf fine with etherboot, but not > > > with filo. I can boot > > > my kernel fine with filo, but not the initrd. I can even boot your > > > kernel of the ram.elf you > > > sent me, but when it hits the initrd it fails with the same error as > > > mine. > > > > > > I suspect either my filo is not configured like yours or that there > > > is a problem loading a > > > mulitpart elf (kernel & initrd in filo). I'm confused as to why filo > > > didn't just use the etherboot > > > portion of elf_load. It could be you were on the, "bleeding" edge? > > > ;) > > > > > > Can you tell me how much memory you have in your working system? I > > > have just > > > one cpu and 512meg memory. Curious if loading it high & it runs out > > > of memory or > > > something like that. > > > > > > Thanks, > > > Dave > > > > > > > > > On Fri, 2004-07-09 at 13:05, YhLu wrote: > > > > > > > > > Did you try the tg3--filo.zelf I sent to you? > > > > > > YH > > -------------- next part -------------- An HTML attachment was scrubbed... URL: From daubin at actuality-systems.com Tue Jul 13 10:05:01 2004 From: daubin at actuality-systems.com (David Aubin) Date: Tue Jul 13 10:05:01 2004 Subject: Filo Error Help In-Reply-To: <20040713015600.GA8220@tsn.or.jp> References: <3174569B9743D511922F00A0C943142305A9EAE1@TYANWEB> <1089666879.10642.36.camel@buildserver1> <20040713015600.GA8220@tsn.or.jp> Message-ID: <1089732900.5854.6.camel@buildserver1> Thank yo for the image, but oddly it fails exactly the same way.... Found initrd block 0 crc error I'm using reiserfs, I'll try ext2. I'm really running out of ideas. Thanks, Dave On Mon, 2004-07-12 at 21:56, Takeshi Sone wrote: > Can you try out my FILO? (http://te.to/~ts1/filo/) > If it works, it might help narrow the problem. > > On Mon, Jul 12, 2004 at 05:14:39PM -0400, David Aubin wrote: > > Here are the results: > > > > I took my known working hard drive and stuck it in the device to test > > with filo. > > The results were the same! Meaning a known working kernel & intird on > > my hard drive failed at the initrd portion, again with the crc error. > > > > I'm now going to try a basic etherboot test without filo to see if I can > > read off of the > > hard drive, just as a baseline. > > > > Any other ideas would be appreciated. > > > > Thanks, > > Dave > > > > On Mon, 2004-07-12 at 16:01, YhLu wrote: > > > > > I mean if you build tg3?filo?ide_disk.zelf, it will confuse the > > > Etherboot. So you can only build tg3?filo.zelf or tg3?ide_disk.zelf. > > > > > > > > > > > > Do you have spare IDE disk? If So format the disk into ext3 or fat > > > format and copy the .elf file into it. > > > > > > > > > > > > Then connect that to your MB do test. > > > > > > > > > > > > hda1:/ram0_......elf > > > > > > > > > > > > Regards > > > > > > > > > > > > YH > > > > > > > > > > > > > > > ______________________________________________________________________ > > > > > > From:David Aubin [mailto:daubin at actuality-systems.com] > > > Sent: Monday, July 12, 2004 12:50 PM > > > To: YhLu > > > Cc: Hendricks David W.; ron minnich; LinuxBIOS > > > Subject: RE: Filo Error Help > > > > > > > > > > > > > > > Hi, > > > > > > I am unable to get my kernel & initrd off of the usb stick. I was > > > reading > > > through the documents and came across this line in > > > README.etherboot_in_filo: > > > You can not use filo and ide_disk at the same time. > > > > > > Can you tell me what this means? Do I need to rebuild filo without > > > IDE > > > support to get USB support? > > > > > > Just to recap: My kernel & initrd fails as the initrd execution > > > complaining of > > > a bad CRC when I use the elf as a payload to load with with filo. I > > > then try > > > uda1:/kernel initrd=/boot/initrd root=/dev/sda1 and I get those td > > > errors. I then > > > tried your ramfs.elf and I get the same behavior are my elf image with > > > the CRC > > > complaining when the initrd portion is executed. Note, I have > > > confirmed my elf > > > works with etherboot, just not filo yet.... > > > > > > The CRC error makes me think that the image did not get loaded > > > correctly > > > by the elf boot. Can you confirm you used Eric's mkelfImage2-5? Here > > > is > > > my dump of the readelf -a. > > > > > > ELF Header: > > > Magic: 7f 45 4c 46 01 01 01 00 00 00 00 00 00 00 00 00 > > > Class: ELF32 > > > Data: 2's complement, little endian > > > Version: 1 (current) > > > OS/ABI: UNIX - System V > > > ABI Version: 0 > > > Type: EXEC (Executable file) > > > Machine: Intel 80386 > > > Version: 0x1 > > > Entry point address: 0x10000 > > > Start of program headers: 52 (bytes into file) > > > Start of section headers: 0 (bytes into file) > > > Flags: 0x0 > > > Size of this header: 52 (bytes) > > > Size of program headers: 32 (bytes) > > > Number of program headers: 5 > > > Size of section headers: 0 (bytes) > > > Number of section headers: 0 > > > Section header string table index: 0 > > > > > > There are no sections in this file. > > > > > > Program Headers: > > > Type Offset VirtAddr PhysAddr FileSiz MemSiz Flg > > > Align > > > NOTE 0x0000d4 0x00000000 0x00000000 0x00088 0x00088 RWE 0 > > > LOAD 0x00015c 0x00010000 0x00010000 0x0559c 0x1aa24 RWE 0 > > > LOAD 0x0056f8 0x00091000 0x00091000 0x00000 0x00070 RWE 0 > > > LOAD 0x0056f8 0x00100000 0x00100000 0x1a952a 0x700000 RWE > > > 0 > > > LOAD 0x1aec22 0x00800000 0x00800000 0x2769f5 0x2769f5 RWE > > > 0 > > > > > > There is no dynamic segment in this file. > > > > > > There are no relocations in this file. > > > > > > There are no unwind sections in this file. > > > > > > No version information found in this file. > > > > > > > > > Thanks, > > > Dave > > > > > > On Fri, 2004-07-09 at 15:48, YhLu wrote: > > > > > > I have got two cpus and four dimms for every CPU. > > > > > > > > > > > > YH > > > > > > > > > > > > > > > ______________________________________________________________________ > > > > > > > > > > > > From:David Aubin [mailto:daubin at actuality-systems.com] > > > Sent: Friday, July 09, 2004 12:07 PM > > > To: YhLu > > > Cc: Hendricks David W.; ron minnich; LinuxBIOS > > > Subject: RE: Filo Error Help > > > > > > > > > > > > > > > Hi, > > > > > > Yes, I did, but I don't have a DHCP environment so it kept searching > > > at the DHCP phase. > > > > > > This problem is odd. I can boot my elf fine with etherboot, but not > > > with filo. I can boot > > > my kernel fine with filo, but not the initrd. I can even boot your > > > kernel of the ram.elf you > > > sent me, but when it hits the initrd it fails with the same error as > > > mine. > > > > > > I suspect either my filo is not configured like yours or that there > > > is a problem loading a > > > mulitpart elf (kernel & initrd in filo). I'm confused as to why filo > > > didn't just use the etherboot > > > portion of elf_load. It could be you were on the, "bleeding" edge? > > > ;) > > > > > > Can you tell me how much memory you have in your working system? I > > > have just > > > one cpu and 512meg memory. Curious if loading it high & it runs out > > > of memory or > > > something like that. > > > > > > Thanks, > > > Dave > > > > > > > > > On Fri, 2004-07-09 at 13:05, YhLu wrote: > > > > > > > > > Did you try the tg3--filo.zelf I sent to you? > > > > > > YH > > From stuge-linuxbios at cdy.org Tue Jul 13 10:18:00 2004 From: stuge-linuxbios at cdy.org (Peter Stuge) Date: Tue Jul 13 10:18:00 2004 Subject: Filo Error Help In-Reply-To: <1089732900.5854.6.camel@buildserver1> References: <3174569B9743D511922F00A0C943142305A9EAE1@TYANWEB> <1089666879.10642.36.camel@buildserver1> <20040713015600.GA8220@tsn.or.jp> <1089732900.5854.6.camel@buildserver1> Message-ID: <20040713154852.GB17513@foo.birdnet.se> On Tue, Jul 13, 2004 at 11:35:01AM -0400, David Aubin wrote: > Thank yo for the image, but oddly it fails exactly the > same way.... > Found initrd block 0 > crc error > > I'm using reiserfs, I'll try ext2. I'm really running out > of ideas. For the initrd? I believe only ext2, minix, cramfs and perhaps one other filesystem is actually supported for initrd:s. //Peter From daubin at actuality-systems.com Tue Jul 13 10:39:00 2004 From: daubin at actuality-systems.com (David Aubin) Date: Tue Jul 13 10:39:00 2004 Subject: Filo Error Help In-Reply-To: <20040713154852.GB17513@foo.birdnet.se> References: <3174569B9743D511922F00A0C943142305A9EAE1@TYANWEB> <1089666879.10642.36.camel@buildserver1> <20040713015600.GA8220@tsn.or.jp> <1089732900.5854.6.camel@buildserver1> <20040713154852.GB17513@foo.birdnet.se> Message-ID: <1089734925.5854.14.camel@buildserver1> Hi, No no no, the disk. The initrd is ext2. Tried changing the disk to ext2 and still get the same results. This did work, but is not what I need. 1. Etherboot the filo.elf (4.2) as a payload 2. Run the filo.elf 3. It is able to load my kernel & initrd.elf, only off of the hd, not the usb stick. Arg! My setup uses etherboot as a primary to get the kernel & intird as an elf. But if that connection dies I want it to use the kernel & initrd elf on my usb stick. This first part works just fine. It is finding a way to get the second part that is taking me weeks! :( On Tue, 2004-07-13 at 11:48, Peter Stuge wrote: > On Tue, Jul 13, 2004 at 11:35:01AM -0400, David Aubin wrote: > > Thank yo for the image, but oddly it fails exactly the > > same way.... > > Found initrd block 0 > > crc error > > > > I'm using reiserfs, I'll try ext2. I'm really running out > > of ideas. > > For the initrd? I believe only ext2, minix, cramfs and perhaps one > other filesystem is actually supported for initrd:s. > > > //Peter > _______________________________________________ > Linuxbios mailing list > Linuxbios at clustermatic.org > http://www.clustermatic.org/mailman/listinfo/linuxbios -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: smiley-6.png Type: image/png Size: 796 bytes Desc: not available URL: From YhLu at tyan.com Tue Jul 13 11:13:01 2004 From: YhLu at tyan.com (YhLu) Date: Tue Jul 13 11:13:01 2004 Subject: Filo Error Help Message-ID: <3174569B9743D511922F00A0C943142305A9EB75@TYANWEB> Can you get two cpus for the S2885? I would send my rom image to you for test. Regards YH _____ From: David Aubin [mailto:daubin at actuality-systems.com] Sent: Tuesday, July 13, 2004 9:09 AM To: Peter Stuge Cc: LinuxBIOS Subject: Re: Filo Error Help Hi, No no no, the disk. The initrd is ext2. Tried changing the disk to ext2 and still get the same results. This did work, but is not what I need. 1. Etherboot the filo.elf (4.2) as a payload 2. Run the filo.elf 3. It is able to load my kernel & initrd.elf, only off of the hd, not the usb stick. Arg! My setup uses etherboot as a primary to get the kernel & intird as an elf. But if that connection dies I want it to use the kernel & initrd elf on my usb stick. This first part works just fine. It is finding a way to get the second part that is taking me weeks! :( On Tue, 2004-07-13 at 11:48, Peter Stuge wrote: On Tue, Jul 13, 2004 at 11:35:01AM -0400, David Aubin wrote: > Thank yo for the image, but oddly it fails exactly the > same way.... > Found initrd block 0 > crc error > > I'm using reiserfs, I'll try ext2. I'm really running out > of ideas. For the initrd? I believe only ext2, minix, cramfs and perhaps one other filesystem is actually supported for initrd:s. //Peter _______________________________________________ Linuxbios mailing list Linuxbios at clustermatic.org http://www.clustermatic.org/mailman/listinfo/linuxbios -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: image001.gif Type: image/gif Size: 663 bytes Desc: not available URL: From daubin at actuality-systems.com Tue Jul 13 11:33:00 2004 From: daubin at actuality-systems.com (David Aubin) Date: Tue Jul 13 11:33:00 2004 Subject: Filo Error Help In-Reply-To: <3174569B9743D511922F00A0C943142305A9EB75@TYANWEB> References: <3174569B9743D511922F00A0C943142305A9EB75@TYANWEB> Message-ID: <1089738182.5854.17.camel@buildserver1> Hello, With all due respect do you really think that an extra cpu would fix this problem? I've looked at filo and to the best of my knowledge I did not see any SMP related calls in there. I sincerely appreciate your help, but I do not think this is the culprit. Thanks, Dave On Tue, 2004-07-13 at 12:49, YhLu wrote: > Can you get two cpus for the S2885? I would send my rom image to you > for test. > > > > Regards > > > > YH > > > > > ______________________________________________________________________ > > From:David Aubin [mailto:daubin at actuality-systems.com] > Sent: Tuesday, July 13, 2004 9:09 AM > To: Peter Stuge > Cc: LinuxBIOS > Subject: Re: Filo Error Help > > > > > Hi, > > No no no, the disk. The initrd is ext2. > > Tried changing the disk to ext2 and still get the same results. > > This did work, but is not what I need. > 1. Etherboot the filo.elf (4.2) as a payload > 2. Run the filo.elf > 3. It is able to load my kernel & initrd.elf, only off of the hd, not > the usb stick. > > Arg! > > My setup uses etherboot as a primary to get the kernel & intird as > an elf. > But if that connection dies I want it to use the kernel & initrd elf > on my > usb stick. This first part works just fine. It is finding a way to > get the second > part that is taking me weeks! :( > > On Tue, 2004-07-13 at 11:48, Peter Stuge wrote: > > > On Tue, Jul 13, 2004 at 11:35:01AM -0400, David Aubin wrote: > > Thank yo for the image, but oddly it fails exactly the > > same way.... > > Found initrd block 0 > > crc error > > > > I'm using reiserfs, I'll try ext2. I'm really running out > > of ideas. > > For the initrd? I believe only ext2, minix, cramfs and perhaps one > other filesystem is actually supported for initrd:s. > > > //Peter > _______________________________________________ > Linuxbios mailing list > Linuxbios at clustermatic.org > http://www.clustermatic.org/mailman/listinfo/linuxbios -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: image001.gif Type: image/gif Size: 663 bytes Desc: not available URL: From rminnich at lanl.gov Tue Jul 13 13:56:01 2004 From: rminnich at lanl.gov (ron minnich) Date: Tue Jul 13 13:56:01 2004 Subject: Filo Error Help In-Reply-To: <1089732900.5854.6.camel@buildserver1> Message-ID: On Tue, 13 Jul 2004, David Aubin wrote: > Thank yo for the image, but oddly it fails exactly the > same way.... > Found initrd block 0 > crc error the few times I've seen the crc error is the initrd is configured too small. I still think you might have a config problem here. Put some debug prints in the initrd code and try to zoom in better to what's going on. ron From daubin at actuality-systems.com Tue Jul 13 14:11:01 2004 From: daubin at actuality-systems.com (David Aubin) Date: Tue Jul 13 14:11:01 2004 Subject: Filo Error Help In-Reply-To: References: Message-ID: <1089747618.5854.71.camel@buildserver1> That's interesting. Too small? Uncompressed it is: ls -la : 8192000 2004-07-13 15:37 initrd I have my ram disk set to 65536. I made it bigger just to be sure. Are you saying the initrd and the ramdisk_size must be equal? If so then this would explain why Yhlu's and my elf's did not work. I'll try an exact ramdisk_size and initrd. Thanks, Dave On Tue, 2004-07-13 at 15:27, ron minnich wrote: > On Tue, 13 Jul 2004, David Aubin wrote: > > > Thank yo for the image, but oddly it fails exactly the > > same way.... > > Found initrd block 0 > > crc error > > the few times I've seen the crc error is the initrd is configured too > small. I still think you might have a config problem here. > > Put some debug prints in the initrd code and try to zoom in better to > what's going on. > > ron > > -------------- next part -------------- An HTML attachment was scrubbed... URL: From YhLu at tyan.com Tue Jul 13 14:15:01 2004 From: YhLu at tyan.com (YhLu) Date: Tue Jul 13 14:15:01 2004 Subject: Filo Error Help Message-ID: <3174569B9743D511922F00A0C943142305A9EBBB@TYANWEB> FILO in TWO CPU version LinuxBIOS works well S2885 in LANL and my lab. So I still suggest that you get another CPU to verify the whole process. Regards YH _____ From: David Aubin [mailto:daubin at actuality-systems.com] Sent: Tuesday, July 13, 2004 12:40 PM To: ron minnich Cc: Takeshi Sone; YhLu; Hendricks David W.; LinuxBIOS Subject: Re: Filo Error Help That's interesting. Too small? Uncompressed it is: ls -la : 8192000 2004-07-13 15:37 initrd I have my ram disk set to 65536. I made it bigger just to be sure. Are you saying the initrd and the ramdisk_size must be equal? If so then this would explain why Yhlu's and my elf's did not work. I'll try an exact ramdisk_size and initrd. Thanks, Dave On Tue, 2004-07-13 at 15:27, ron minnich wrote: On Tue, 13 Jul 2004, David Aubin wrote: > Thank yo for the image, but oddly it fails exactly the > same way.... > Found initrd block 0 > crc error the few times I've seen the crc error is the initrd is configured too small. I still think you might have a config problem here. Put some debug prints in the initrd code and try to zoom in better to what's going on. ron -------------- next part -------------- An HTML attachment was scrubbed... URL: From daubin at actuality-systems.com Tue Jul 13 14:49:00 2004 From: daubin at actuality-systems.com (David Aubin) Date: Tue Jul 13 14:49:00 2004 Subject: Filo Error Help In-Reply-To: References: Message-ID: <1089749872.5854.75.camel@buildserver1> I now have a matching kernel ramdisk size of 8192k and initrd of the same size. It is failing the crc check in the kernel lib/inflate.c. I haven't probed further than that. Next step is to see what the kernel thinks the initrd is. Dave On Tue, 2004-07-13 at 15:27, ron minnich wrote: > On Tue, 13 Jul 2004, David Aubin wrote: > > > Thank yo for the image, but oddly it fails exactly the > > same way.... > > Found initrd block 0 > > crc error > > the few times I've seen the crc error is the initrd is configured too > small. I still think you might have a config problem here. > > Put some debug prints in the initrd code and try to zoom in better to > what's going on. > > ron > > -------------- next part -------------- An HTML attachment was scrubbed... URL: From stepan at openbios.org Tue Jul 13 15:14:01 2004 From: stepan at openbios.org (Stefan Reinauer) Date: Tue Jul 13 15:14:01 2004 Subject: CPU refactoring status.... In-Reply-To: References: Message-ID: <20040713204521.GC7880@openbios.org> * Eric W. Biederman [040713 07:40]: > It appears Stefan has one of CVS's internal locks on src/cpu/p5 and so I can't > get past that.... It is probably just CVS messed up somewhere but anyway. > > I will look back tomorrow and see what I can accomplish. Weird, all my commits are quite a while ago and were completed without trouble. Is there anything I can do to fix this? Stefan From rminnich at lanl.gov Tue Jul 13 16:25:00 2004 From: rminnich at lanl.gov (ron minnich) Date: Tue Jul 13 16:25:00 2004 Subject: Filo Error Help In-Reply-To: <1089747618.5854.71.camel@buildserver1> Message-ID: On Tue, 13 Jul 2004, David Aubin wrote: > I have my ram disk set to 65536. I made it bigger just to be sure. > Are you saying the initrd and the ramdisk_size must be equal? no, now that I see what you're doing I'm lost as to the problem. When I've had this problem I just jam debug printks into the kernel and see why it's really failing. It always boils down to a failure to read or copy out the ramdisk image. ron From ebiederman at lnxi.com Tue Jul 13 19:33:01 2004 From: ebiederman at lnxi.com (Eric W. Biederman) Date: Tue Jul 13 19:33:01 2004 Subject: CPU refactoring status.... In-Reply-To: <20040713204521.GC7880@openbios.org> References: <20040713204521.GC7880@openbios.org> Message-ID: Stefan Reinauer writes: > * Eric W. Biederman [040713 07:40]: > > It appears Stefan has one of CVS's internal locks on src/cpu/p5 and so I can't > > > get past that.... It is probably just CVS messed up somewhere but anyway. > > > > I will look back tomorrow and see what I can accomplish. > > Weird, all my commits are quite a while ago and were completed without > trouble. Is there anything I can do to fix this? I think someone needs to log into the cvs server and fix it. Which like requires a project admin to ask the sourceforge administrators. My hunch is that something exited abnormally quite a while ago. Eric From scheng at msica.com Tue Jul 13 19:37:01 2004 From: scheng at msica.com (Simon Xin Cheng) Date: Tue Jul 13 19:37:01 2004 Subject: ADLO: linuxbios v1 hangs after jumping to boot code at 0x7c00 In-Reply-To: <61394.24.87.201.99.1089678627.squirrel@www.nome.ca> References: <61394.24.87.201.99.1089678627.squirrel@www.nome.ca> Message-ID: <62006.24.87.201.99.1089767059.squirrel@www.nome.ca> I am trying to use ADLO + video bios to enable VGA support for my EPIA 800 board. Unfortunately, the code hangs after the elfboot "Jumping to boot code at 0x7c00 " According to ADLO document, I enabled the original bios shadow from C0000 to DFFFF and capture the vedio bios by: dd if=/proc/kcore of=/usr/src/video.bios.bin bs=1 count=65536 skip=790528 Program headers of the /proc/kcore is: Program Headers: Type Offset VirtAddr PhysAddr FileSiz MemSiz Flg Align NOTE 0x000094 0x00000000 0x00000000 0x006bc 0x00000 0 LOAD 0x8001000 0xc8000000 0x00000000 0x37fee000 0x37fee000 RWE 0x1000 LOAD 0x001000 0xc0000000 0x00000000 0x77f0000 0x77f0000 RWE 0x1000 Then I make payload and romimage. Is there anything wrong with my procedure? By the way, how to debug ADLO? Simon Cheng www.msica.com From rsmith at bitworks.com Tue Jul 13 20:07:01 2004 From: rsmith at bitworks.com (Richard Smith) Date: Tue Jul 13 20:07:01 2004 Subject: ADLO: linuxbios v1 hangs after jumping to boot code at 0x7c00 In-Reply-To: <62006.24.87.201.99.1089767059.squirrel@www.nome.ca> References: <61394.24.87.201.99.1089678627.squirrel@www.nome.ca> <62006.24.87.201.99.1089767059.squirrel@www.nome.ca> Message-ID: <40F48E81.9040408@bitworks.com> Simon Xin Cheng wrote: > I am trying to use ADLO + video bios to enable VGA support for my EPIA 800 > board. Unfortunately, the code hangs after the elfboot "Jumping to boot > code at 0x7c00 " > > According to ADLO document, I enabled the original bios shadow from C0000 > to DFFFF and capture the vedio bios by: Make sure your shadowing is enable correctly. You want to read from the bios chip and write to RAM. Then enable the full shadow of that location. > dd if=/proc/kcore of=/usr/src/video.bios.bin bs=1 count=65536 skip=790528 Examine this file and see if it has the BIOS extension signature of 0xaa55 (or 0x55aa depending on what endian you view it as) You should also see some text iding the bios. > By the way, how to debug ADLO? In ./util/ADLO/bochs/bios/rombios.c there should be a #define DEBUG_SERIAL. Set that to 1 and all of the bios messages will go out the serial port. Note you have to disable it to get video since it bypases screenwrites. DEBUG_SERIAL is from a patch but I don't know if it make it into CVS. If you don't have a DEBUG_SERIAL then search the archives for the patch. If you can't find it then let me know and I'll see about generating one for you. rombios.c also has lots of debug options as well look at the source. One thing to note is that if you do any hacking on the assembly in rombios.c you must be very careful about shifting the positions of all the bios entry points. A single instrution in some of those assembly blocks will break all the bios entry points. From ts1 at tsn.or.jp Tue Jul 13 20:11:11 2004 From: ts1 at tsn.or.jp (Takeshi Sone) Date: Tue Jul 13 20:11:11 2004 Subject: Filo Error Help In-Reply-To: <1089732900.5854.6.camel@buildserver1> References: <3174569B9743D511922F00A0C943142305A9EAE1@TYANWEB> <1089666879.10642.36.camel@buildserver1> <20040713015600.GA8220@tsn.or.jp> <1089732900.5854.6.camel@buildserver1> Message-ID: <20040714013843.GA25753@tsn.or.jp> On Tue, Jul 13, 2004 at 11:35:01AM -0400, David Aubin wrote: > Thank yo for the image, but oddly it fails exactly the > same way.... > Found initrd block 0 > crc error Have you tried booting bzImage kernel with FILO? If it succeeds the culprit is my version of ELF boot code. Anyways I would like to see full DEBUG_ALL output of FILO. -- Takeshi From rminnich at lanl.gov Tue Jul 13 20:37:01 2004 From: rminnich at lanl.gov (ron minnich) Date: Tue Jul 13 20:37:01 2004 Subject: CPU refactoring status.... In-Reply-To: Message-ID: On 13 Jul 2004, Eric W. Biederman wrote: > I think someone needs to log into the cvs server and fix it. Which > like requires a project admin to ask the sourceforge administrators. I'll do it tomorrow. usually these things time out, but ... !@$#@! ron From ebiederman at lnxi.com Wed Jul 14 00:24:00 2004 From: ebiederman at lnxi.com (Eric W. Biederman) Date: Wed Jul 14 00:24:00 2004 Subject: CPU refactoring status.... In-Reply-To: References: Message-ID: ron minnich writes: > On 13 Jul 2004, Eric W. Biederman wrote: > > > I think someone needs to log into the cvs server and fix it. Which > > like requires a project admin to ask the sourceforge administrators. > > I'll do it tomorrow. usually these things time out, but ... > > !@$#@! Agreed. Thank you very much for taking the time to do this. What does it involve anyway? Eric From zhushisongzhu at yahoo.com Wed Jul 14 07:35:01 2004 From: zhushisongzhu at yahoo.com (zhu shi song) Date: Wed Jul 14 07:35:01 2004 Subject: via 686b, 8601t mainboard ipl.S hlt In-Reply-To: <20040714000701.18303.37946.Mailman@nwn.definitive.org> Message-ID: <20040714130653.51901.qmail@web13202.mail.yahoo.com> I've got QDIA6T mainboard see http://www.qdigrp.com. It use via 8601t and 686b. I try to boot it using vt5426 mainboard in freebios V1. After testing, ipl.S will loop forever in the following code(in src/northbridge/via/8601/ipl.S): ............ wait_for_flash_ready: /* delay by reding NOP register before polling the FLASH READY bit, this is inlined to save a call/ret pair */ movb $0xbb, %al outb %al,$0x80 doc_delay: movb %ds:0x04(%di),%ah movw $0x04, %cx # this one is DANGEROUS but I am # sure the upper 3 bytes == 0x00 0: movb %ds:0x20(%di), %al # read DOC NOP retisger loop 0b # four times testb $0x80,%ah # is flash ready ? jz wait_for_flash_ready ........ Anybody can explain me what the code work for? thanks zhu --------------------------------- Do you Yahoo!? Yahoo! Mail - 50x more storage than other providers! -------------- next part -------------- An HTML attachment was scrubbed... URL: From rminnich at lanl.gov Wed Jul 14 08:18:00 2004 From: rminnich at lanl.gov (ron minnich) Date: Wed Jul 14 08:18:00 2004 Subject: CPU refactoring status.... In-Reply-To: Message-ID: you need to send me the file name again (I forgot it) and then I file a trouble ticket with sourceforge, etc., etc., since I don't have direct access to the repo. ron From ebiederman at lnxi.com Wed Jul 14 08:30:01 2004 From: ebiederman at lnxi.com (Eric W. Biederman) Date: Wed Jul 14 08:30:01 2004 Subject: CPU refactoring status.... In-Reply-To: References: Message-ID: ron minnich writes: > you need to send me the file name again (I forgot it) and then I file a > trouble ticket with sourceforge, etc., etc., since I don't have direct > access to the repo. src/cpu/p5/ All I have is a directory name because I was attempting to branch the CVS tree with cvs tag. Eric From tony_cheng at pcmagic.net Wed Jul 14 13:46:01 2004 From: tony_cheng at pcmagic.net (Tony Cheng) Date: Wed Jul 14 13:46:01 2004 Subject: Serenade BIOS Message-ID: <002001c469d7$3d168e30$919814ac@trans.corp> Hi Ollie, I finally got the AMD Seranade board and tried the Serenade Linux BIOS. But I've got the serial port message like following and doesn't have any VGA output. (Seranade board come with a ATI Rage VGA card), I suppose the current Serenade LinuxBIOS doesn't have the VGA support? The serial output has a lot of "POST: 0x00" message output at at beginning and ending make me think I probably missed something. The changes I did with the BIOS is very minor. they are: 1. option ROM_SIZE changed to 512K, instead of 1MB to fit my Flash Part size. 2. option MAXIMUM_CONSOLE_LOGLEVEL and option DEFAULT_CONSOLE_LOGLEVEL changed to value 7, instead of value 8, in order to build. (Follow your instruction) Any input would be appriciated. Thanks Tony --- Attached Seranade LinuxBIOS Serial Port output ---- POST: 0x00 POST: 0x00 POST: 0x00 POST: 0x00 POST: 0x00 POST: 0x00 POST: 0x00 POST: 0x00 LinuxBIOS-1.1.6.0Fallback Tue Jul 13 19:16:21 PDT 2004 starting... setting up resource map....done. 02 nodes initialized. coherent_ht_finalize done ht reset - LinuxBIOS-1.1.6.0Fallback Tue Jul 13 19:16:21 PDT 2004 starting... setting up resource map....done. 02 nodes initialized. coherent_ht_finalize done PCI: 00:01.00 PCI: 00:01.01 PCI: 00:02.00 PCI: 00:02.01 PCI: 00:03.00 PCI: 00:04.00 PCI: 00:04.01 PCI: 00:04.02 PCI: 00:04.03 PCI: 00:04.05 PCI: 00:04.06 PCI: 00:18.00 PCI: 00:18.01 PCI: 00:18.02 PCI: 00:18.03 PCI: 00:19.00 PCI: 00:19.01 PCI: 00:19.02 PCI: 00:19.03 Ram1.00 Ram1.01 Ram2.00 Ram2.01 No memory for this cpu Ram3 Initializing memory: done Clearing LinuxBIOS memory: done Ram4 PCI: 00:01.00 PCI: 00:01.01 PCI: 00:02.00 PCI: 00:02.01 PCI: 00:03.00 PCI: 00:04.00 PCI: 00:04.01 PCI: 00:04.02 PCI: 00:04.03 PCI: 00:04.05 PCI: 00:04.06 PCI: 00:18.00 PCI: 00:18.01 PCI: 00:18.02 PCI: 00:18.03 PCI: 00:19.00 PCI: 00:19.01 PCI: 00:19.02 PCI: 00:19.03 POST: 0x39 LinuxBIOS-1.1.6.0Fallback Tue Jul 13 19:16:21 PDT 2004 booting... POST: 0x40 Finding PCI configuration type. POST: 0x5f Enumerating static devices... Enumerating buses... POST: 0x24 POST: 0x25 POST: 0x24 POST: 0x25 POST: 0x24 POST: 0x25 POST: 0x55 POST: 0x24 POST: 0x25 POST: 0x55 POST: 0x24 POST: 0x25 POST: 0x55 POST: 0x55 POST: 0x55 done POST: 0x66 Allocating resources... done. POST: 0x88 Enabling resourcess... Kid 0 of k8: bridge ctrl says: 0x0 Kid 1 of k8: bridge ctrl says: 0x0 Kid 2 of k8: bridge ctrl says: 0x0 Kid 0 of k8: bridge ctrl says: 0x0 Kid 1 of k8: bridge ctrl says: 0x0 Kid 2 of k8: bridge ctrl says: 0x0 done. Initializing devices... POST: 0x00 POST: 0x00 POST: 0x00 POST: 0x00 POST: 0x00 POST: 0x00 POST: 0x00 POST: 0x00 POST: 0x00 POST: 0x00 POST: 0x00 POST: 0x00 POST: 0x00 POST: 0x00 POST: 0x00 ............ Senerade BIOS will keep sending "POST: 0x00" message. ----- Original Message ----- From: "Li-Ta Lo" To: "Tony Cheng" Cc: "LinuxBIOS" Sent: Monday, June 28, 2004 8:06 AM Subject: Re: Serenade BIOS > On Fri, 2004-06-25 at 17:17, Tony Cheng wrote: > > Hi Ollie, > > > > The Serenade BIOS I've got from CVS Server can not build. Do you see > > this also? The payload size of my binary is about 55k. > > > > The error messages are as follow: > > > > objcopy -O binary linuxbios_c linuxbios_payload.bin > > ./nrv2b e linuxbios_payload.bin linuxbios_payload.nrv2b > > input/output = 67188/26767 = 2.510 > > cp linuxbios_payload.nrv2b linuxbios_payload > > gcc -nostdlib -nostartfiles -static -o linuxbios -T ldscript.ld crt0.o > > /usr/bin/ld: section .id [ffffffd8 -> ffffffef] overlaps section > > .payload [ffff9750 -> ffffffe2] > > collect2: ld returned 1 exit status > > make[1]: *** [linuxbios] Error 1 > > make[1]: Leaving directory > > `/root/dl/freebios2/targets/amd/serenade/serenade/fallback' > > make: *** [fallback-rom] Error 1 > > > > It is the 64kB size limit problem. Please set the > > option MAXIMUM_CONSOLE_LOGLEVEL=8 > option DEFAULT_CONSOLE_LOGLEVEL=8 > > in Config.lb to some lower value. > > Ollie > > > > > Thanks > > > > Tony > > > > > > > > > > -------------- next part -------------- An HTML attachment was scrubbed... URL: From ollie at lanl.gov Wed Jul 14 13:58:01 2004 From: ollie at lanl.gov (Li-Ta Lo) Date: Wed Jul 14 13:58:01 2004 Subject: Serenade BIOS In-Reply-To: <002001c469d7$3d168e30$919814ac@trans.corp> References: <002001c469d7$3d168e30$919814ac@trans.corp> Message-ID: <1089833365.3822.8.camel@exponential.lanl.gov> On Wed, 2004-07-14 at 13:17, Tony Cheng wrote: > > Hi Ollie, > I finally got the AMD Seranade board and tried the Serenade Linux > BIOS. > > But I've got the serial port message like following and doesn't have > any VGA output. (Seranade board come with a ATI Rage VGA card), I > suppose the current Serenade LinuxBIOS doesn't have the VGA > support? The serial output has a lot of "POST: 0x00" message output at > at beginning and ending make me think I probably missed something. The serenade port does not support VGA yet. It is "normal" to have those post 0x00. The keyboard controller on that board is serously fucked up. LinuxBIOS is trying to init the keyboard when printing these 0x00. Please grep something like "init_keyboard" and remove it. From rsmith at bitworks.com Wed Jul 14 13:59:01 2004 From: rsmith at bitworks.com (Richard Smith) Date: Wed Jul 14 13:59:01 2004 Subject: V1 PIRQ table In-Reply-To: References: Message-ID: <40F589C6.10906@bitworks.com> I've reciently learned that my PIRQ table isn't making it into RAM. Going through the code I see that the the last thing that hardware_main does before loading an elf image is call write_tables() which will try and copy the various tables to thier final destination. I don't uderstand how this will work. In order for those writes to go to RAM you have to have your shadowing control set up properly. On my chipset at this stage both reads and writes to areas such as f0000 are forwarded to PCI so the write will fail. I don't see any mention of enableing writes for these ranges to go to RAM. Am I missing something? From rminnich at lanl.gov Wed Jul 14 14:16:01 2004 From: rminnich at lanl.gov (ron minnich) Date: Wed Jul 14 14:16:01 2004 Subject: V1 PIRQ table In-Reply-To: <40F589C6.10906@bitworks.com> Message-ID: On Wed, 14 Jul 2004, Richard Smith wrote: > I don't uderstand how this will work. In order for those writes to go > to RAM you have to have your shadowing control set up properly. On my > chipset at this stage both reads and writes to areas such as f0000 are > forwarded to PCI so the write will fail. What I do in this case is set CONFIG_COMPRESSED to 0, since if you don't have shadow ram working you're toast. ron From rsmith at bitworks.com Wed Jul 14 14:22:01 2004 From: rsmith at bitworks.com (Richard Smith) Date: Wed Jul 14 14:22:01 2004 Subject: V1 PIRQ table In-Reply-To: References: Message-ID: <40F58F45.1030602@bitworks.com> ron minnich wrote: > On Wed, 14 Jul 2004, Richard Smith wrote: > > >>I don't uderstand how this will work. In order for those writes to go >>to RAM you have to have your shadowing control set up properly. On my >>chipset at this stage both reads and writes to areas such as f0000 are >>forwarded to PCI so the write will fail. > > > What I do in this case is set CONFIG_COMPRESSED to 0, since if you > don't have shadow ram working you're toast. > I don't use compression. I've got shadow ram working fine. ADLO won't boot without it. I was just asking before I try to add something that isn't necessary. The tables depend on shadowing yes? From rminnich at lanl.gov Wed Jul 14 14:30:01 2004 From: rminnich at lanl.gov (ron minnich) Date: Wed Jul 14 14:30:01 2004 Subject: V1 PIRQ table In-Reply-To: <40F58F45.1030602@bitworks.com> Message-ID: On Wed, 14 Jul 2004, Richard Smith wrote: > The tables depend on shadowing yes? no, they don't. If you don't have shadowing, and you don't have compression, then the tables will be there in FLASH and linux will find them. I think I don't understand the problem, I misread it, so I'll go back and reread. ron From rsmith at bitworks.com Wed Jul 14 14:44:01 2004 From: rsmith at bitworks.com (Richard Smith) Date: Wed Jul 14 14:44:01 2004 Subject: V1 PIRQ table In-Reply-To: References: Message-ID: <40F59476.5090902@bitworks.com> ron minnich wrote: > On Wed, 14 Jul 2004, Richard Smith wrote: > > >>The tables depend on shadowing yes? > > no, they don't. If you don't have shadowing, and you don't have > compression, then the tables will be there in FLASH and linux will find > them. > > I think I don't understand the problem, I misread it, so I'll go back and > reread. Ah.. I'm begining to understand. The table is pre-locaed at 0xf0000 then. That makes sense. The code then is very confusing since it says things like "Copying tables..." and then "Verifying..." and the function called write_tables(). So I just assumed it was stuck in ROM at any old location and moved to the correct position. What address is the PIRQ table supposed to show up at? From rminnich at lanl.gov Wed Jul 14 14:49:00 2004 From: rminnich at lanl.gov (ron minnich) Date: Wed Jul 14 14:49:00 2004 Subject: V1 PIRQ table In-Reply-To: <40F59476.5090902@bitworks.com> Message-ID: On Wed, 14 Jul 2004, Richard Smith wrote: > Ah.. I'm begining to understand. The table is pre-locaed at 0xf0000 > then. That makes sense. The code then is very confusing since it says > things like "Copying tables..." and then "Verifying..." and the function > called write_tables(). So I just assumed it was stuck in ROM at any old > location and moved to the correct position. yes, that code is very annoying. > What address is the PIRQ table supposed to show up at? I know for sure Linux looks for the $PIR signature in the F segment, and one or two other places. ron From daubin at actuality-systems.com Wed Jul 14 17:17:01 2004 From: daubin at actuality-systems.com (David Aubin) Date: Wed Jul 14 17:17:01 2004 Subject: How to build vgabios Message-ID: <1089845244.19992.133.camel@buildserver1> Hello, I am having difficulty building vgabios. Can someone please give me a hand? I took the latest code off of the freebios2 branch (6 days old, by Ollie) I get the following Errors when I try to compile. It looks like I am missing files in the drop #include gcc -Wall -Ix86emu/include -O2 -g -m32 -march=i386 -c -o pci-userspace.o pci-userspace.c pci-userspace.c:2:21: pci/pci.h: No such file or directory In file included from pci-userspace.c:4: pci.h:1: error: parse error before "port" pci-userspace.c: In function `pciInit': pci-userspace.c:20: warning: implicit declaration of function `pci_alloc' pci-userspace.c:20: warning: assignment makes pointer from integer without a cast pci-userspace.c:22: warning: implicit declaration of function `pci_init' pci-userspace.c:23: warning: implicit declaration of function `pci_scan_bus' pci-userspace.c:24: error: dereferencing pointer to incomplete type pci-userspace.c:24: error: dereferencing pointer to incomplete type pci-userspace.c:25: warning: implicit declaration of function `pci_fill_info' pci-userspace.c:25: error: `PCI_FILL_IDENT' undeclared (first use in this function) pci-userspace.c:25: error: (Each undeclared identifier is reported only once pci-userspace.c:25: error: for each function it appears in.) pci-userspace.c:25: error: `PCI_FILL_BASES' undeclared (first use in this function) pci-userspace.c: In function `pciExit': pci-userspace.c:32: warning: implicit declaration of function `pci_cleanup' pci-userspace.c: In function `findPci': pci-userspace.c:44: error: dereferencing pointer to incomplete type pci-userspace.c:45: error: dereferencing pointer to incomplete type pci-userspace.c:46: error: dereferencing pointer to incomplete type pci-userspace.c:48: warning: implicit declaration of function `pci_get_dev' pci-userspace.c: At top level: pci-userspace.c:54: error: parse error before "pciSlotBX" pci-userspace.c:55: warning: return type defaults to `int' pci-userspace.c: In function `pciSlotBX': pci-userspace.c:56: error: dereferencing pointer to incomplete type pci-userspace.c:56: error: dereferencing pointer to incomplete type pci-userspace.c:56: error: dereferencing pointer to incomplete type pci-userspace.c: At top level: pci-userspace.c:59: error: parse error before "pciReadByte" pci-userspace.c:59: error: parse error before "u32" pci-userspace.c:60: warning: return type defaults to `int' pci-userspace.c: In function `pciReadByte': pci-userspace.c:62: error: `tag' undeclared (first use in this function) pci-userspace.c:62: warning: assignment makes pointer from integer without a cast pci-userspace.c:63: warning: implicit declaration of function `pci_read_byte' pci-userspace.c:63: error: `idx' undeclared (first use in this function) pci-userspace.c: At top level: pci-userspace.c:71: error: parse error before "pciReadWord" pci-userspace.c:71: error: parse error before "u32" pci-userspace.c:72: warning: return type defaults to `int' pci-userspace.c: In function `pciReadWord': pci-userspace.c:74: error: `tag' undeclared (first use in this function) pci-userspace.c:74: warning: assignment makes pointer from integer without a cast pci-userspace.c:75: warning: implicit declaration of function `pci_read_word' pci-userspace.c:75: error: `idx' undeclared (first use in this function) pci-userspace.c: At top level: pci-userspace.c:83: error: parse error before "pciReadLong" pci-userspace.c:83: error: parse error before "u32" pci-userspace.c:84: warning: return type defaults to `int' pci-userspace.c: In function `pciReadLong': pci-userspace.c:86: error: `tag' undeclared (first use in this function) pci-userspace.c:86: warning: assignment makes pointer from integer without a cast pci-userspace.c:87: warning: implicit declaration of function `pci_read_long' pci-userspace.c:87: error: `idx' undeclared (first use in this function) pci-userspace.c: At top level: pci-userspace.c:96: error: parse error before "u32" pci-userspace.c: In function `pciWriteLong': pci-userspace.c:99: error: `tag' undeclared (first use in this function) pci-userspace.c:99: warning: assignment makes pointer from integer without a cast pci-userspace.c:100: warning: implicit declaration of function `pci_write_long' pci-userspace.c:100: error: `idx' undeclared (first use in this function) pci-userspace.c:100: error: `data' undeclared (first use in this function) pci-userspace.c: At top level: pci-userspace.c:108: error: parse error before "u32" pci-userspace.c: In function `pciWriteWord': pci-userspace.c:111: error: `tag' undeclared (first use in this function) pci-userspace.c:111: warning: assignment makes pointer from integer without a cast pci-userspace.c:112: warning: implicit declaration of function `pci_write_word' pci-userspace.c:112: error: `idx' undeclared (first use in this function) pci-userspace.c:112: error: `data' undeclared (first use in this function) pci-userspace.c: At top level: pci-userspace.c:121: error: parse error before "u32" pci-userspace.c: In function `pciWriteByte': pci-userspace.c:124: error: `tag' undeclared (first use in this function) pci-userspace.c:124: warning: assignment makes pointer from integer without a cast pci-userspace.c:125: error: `idx' undeclared (first use in this function) pci-userspace.c:125: error: `data' undeclared (first use in this function) /usr/include/bits/stdio.h: At top level: pci-userspace.c:13: error: storage size of `ltag' isn't known make: *** [pci-userspace.o] Error 1 Can someone please tell me where I can find the correct pci files? I have a Suse 9.0 x64 distribution. Thanks, Dave From rminnich at lanl.gov Wed Jul 14 17:24:00 2004 From: rminnich at lanl.gov (ron minnich) Date: Wed Jul 14 17:24:00 2004 Subject: How to build vgabios In-Reply-To: <1089845244.19992.133.camel@buildserver1> Message-ID: On Wed, 14 Jul 2004, David Aubin wrote: > gcc -Wall -Ix86emu/include -O2 -g -m32 -march=i386 -c -o > pci-userspace.o pci-userspace.c > pci-userspace.c:2:21: pci/pci.h: No such file or directory your problems start here. do you have the pciutils installed? You need: pciutils-devel-2.1.9-2 or later. ron From ollie at lanl.gov Wed Jul 14 17:29:00 2004 From: ollie at lanl.gov (Li-Ta Lo) Date: Wed Jul 14 17:29:00 2004 Subject: How to build vgabios In-Reply-To: <1089845244.19992.133.camel@buildserver1> References: <1089845244.19992.133.camel@buildserver1> Message-ID: <1089846002.3822.12.camel@exponential.lanl.gov> On Wed, 2004-07-14 at 16:47, David Aubin wrote: > Hello, > > I am having difficulty building vgabios. Can someone please give me > a hand? I took the latest code off of the freebios2 branch (6 days old, > by Ollie) > I get the following Errors when I try to compile. It looks like I am > missing > files in the drop #include > you need to rpm -i (yast ??) pciutil-devel. Ollie From rsmith at bitworks.com Wed Jul 14 17:39:01 2004 From: rsmith at bitworks.com (Richard Smith) Date: Wed Jul 14 17:39:01 2004 Subject: How to build vgabios In-Reply-To: <1089845244.19992.133.camel@buildserver1> References: <1089845244.19992.133.camel@buildserver1> Message-ID: <40F5BD5D.4020106@bitworks.com> David Aubin wrote: > I get the following Errors when I try to compile. It looks like I am > missing > files in the drop #include > > gcc -Wall -Ix86emu/include -O2 -g -m32 -march=i386 -c -o > pci-userspace.o pci-userspace.c Install the pciutils-dev package or get the tarball. From YhLu at tyan.com Wed Jul 14 17:48:00 2004 From: YhLu at tyan.com (YhLu) Date: Wed Jul 14 17:48:00 2004 Subject: How to build vgabios Message-ID: <3174569B9743D511922F00A0C943142305A9ECD8@TYANWEB> You compile the LinuxBIOS, filo, .... in Suse 9 for AMD 64 ? -----Original Message----- From: ron minnich [mailto:rminnich at lanl.gov] Sent: Wednesday, July 14, 2004 3:55 PM To: David Aubin Cc: LinuxBIOS Subject: Re: How to build vgabios On Wed, 14 Jul 2004, David Aubin wrote: > gcc -Wall -Ix86emu/include -O2 -g -m32 -march=i386 -c -o > pci-userspace.o pci-userspace.c > pci-userspace.c:2:21: pci/pci.h: No such file or directory your problems start here. do you have the pciutils installed? You need: pciutils-devel-2.1.9-2 or later. ron _______________________________________________ Linuxbios mailing list Linuxbios at clustermatic.org http://www.clustermatic.org/mailman/listinfo/linuxbios From scheng at msica.com Wed Jul 14 19:36:00 2004 From: scheng at msica.com (Simon Xin Cheng) Date: Wed Jul 14 19:36:00 2004 Subject: ADLO: linuxbios v1 hangs after jumping to boot code at 0x7c00 In-Reply-To: <40F48E81.9040408@bitworks.com> References: <61394.24.87.201.99.1089678627.squirrel@www.nome.ca> <62006.24.87.201.99.1089767059.squirrel@www.nome.ca> <40F48E81.9040408@bitworks.com> Message-ID: <60536.24.87.201.99.1089853618.squirrel@www.nome.ca> Richard, Thanks for your suggestions. I tried them, however, the system still hangs when jumping to boot code at 0x7c00. > Examine this file and see if it has the BIOS extension signature of > 0xaa55 (or 0x55aa depending on what endian you view it as) You should > also see some text iding the bios. I enabled all shadowing and found 0xaa55 and bios copyright information at the beginning of file. > In ./util/ADLO/bochs/bios/rombios.c there should be a #define > DEBUG_SERIAL. Set that to 1 and all of the bios messages will go out > the serial port. My source has DEBUG_SERIAL and by default it is enabled. Nothing appears for this default configuration. I also tried to disabled DEBUG_SERIAL, but no video appears either. Right now I suspect that something wrong with loder.s. My question is how to debug loader.s? Thanks again. Simon Cheng www.msica.com From tony_cheng at pcmagic.net Wed Jul 14 19:44:01 2004 From: tony_cheng at pcmagic.net (Tony Cheng) Date: Wed Jul 14 19:44:01 2004 Subject: Serenade BIOS References: <002001c469d7$3d168e30$919814ac@trans.corp> <1089833365.3822.8.camel@exponential.lanl.gov> Message-ID: <000401c46a09$3b9e8170$932614ac@trans.corp> After I comment out the "init_pc_keyboard" from superio.c, Serenade LinuxBIOS boots muck better. For the keyboard support, the AMI BIOS which come with the Serenade board works OK, do you have any comment on this? Thanks Tony ----- Original Message ----- From: "Li-Ta Lo" To: "Tony Cheng" Cc: "ron minnich" ; "LinuxBIOS" Sent: Wednesday, July 14, 2004 12:29 PM Subject: Re: Serenade BIOS > On Wed, 2004-07-14 at 13:17, Tony Cheng wrote: > > > > Hi Ollie, > > I finally got the AMD Seranade board and tried the Serenade Linux > > BIOS. > > > > But I've got the serial port message like following and doesn't have > > any VGA output. (Seranade board come with a ATI Rage VGA card), I > > suppose the current Serenade LinuxBIOS doesn't have the VGA > > support? The serial output has a lot of "POST: 0x00" message output at > > at beginning and ending make me think I probably missed something. > > The serenade port does not support VGA yet. > > It is "normal" to have those post 0x00. The keyboard controller on that > board is serously fucked up. LinuxBIOS is trying to init the keyboard > when printing these 0x00. Please grep something like "init_keyboard" and > remove it. > > > > _______________________________________________ > Linuxbios mailing list > Linuxbios at clustermatic.org > http://www.clustermatic.org/mailman/listinfo/linuxbios > From rsmith at bitworks.com Wed Jul 14 19:45:01 2004 From: rsmith at bitworks.com (Richard Smith) Date: Wed Jul 14 19:45:01 2004 Subject: ADLO: linuxbios v1 hangs after jumping to boot code at 0x7c00 In-Reply-To: <60536.24.87.201.99.1089853618.squirrel@www.nome.ca> References: <61394.24.87.201.99.1089678627.squirrel@www.nome.ca> <62006.24.87.201.99.1089767059.squirrel@www.nome.ca> <40F48E81.9040408@bitworks.com> <60536.24.87.201.99.1089853618.squirrel@www.nome.ca> Message-ID: <40F5DADB.1050708@bitworks.com> Simon Xin Cheng wrote: > Richard, > > Thanks for your suggestions. I tried them, however, the system still hangs > when jumping to boot code at 0x7c00. > > Right now I suspect that something wrong with loder.s. My question is how > to debug loader.s? Thanks again. The most likely problem is that your shadowing is not working. Right after loader finishes copying to ram and you have enabled reads to be routed to RAM dump the first few bytes from 0x7c00 and dump them out the seial port and make sure things really got copied to RAM. From daubin at actuality-systems.com Thu Jul 15 06:58:00 2004 From: daubin at actuality-systems.com (David Aubin) Date: Thu Jul 15 06:58:00 2004 Subject: How to build vgabios In-Reply-To: <3174569B9743D511922F00A0C943142305A9ECD8@TYANWEB> References: <3174569B9743D511922F00A0C943142305A9ECD8@TYANWEB> Message-ID: <1089894496.6988.0.camel@buildserver1> Yes, although I put -m32 and some other magic flags to make the whole thing think it is a 32 bit environment. You guys all ROCK! Thank you!!! On Wed, 2004-07-14 at 19:23, YhLu wrote: > You compile the LinuxBIOS, filo, .... in Suse 9 for AMD 64 ? > > -----Original Message----- > From: ron minnich [mailto:rminnich at lanl.gov] > Sent: Wednesday, July 14, 2004 3:55 PM > To: David Aubin > Cc: LinuxBIOS > Subject: Re: How to build vgabios > > On Wed, 14 Jul 2004, David Aubin wrote: > > > gcc -Wall -Ix86emu/include -O2 -g -m32 -march=i386 -c -o > > pci-userspace.o pci-userspace.c > > pci-userspace.c:2:21: pci/pci.h: No such file or directory > > your problems start here. > > do you have the pciutils installed? You need: > > pciutils-devel-2.1.9-2 > > or later. > > > ron > > _______________________________________________ > Linuxbios mailing list > Linuxbios at clustermatic.org > http://www.clustermatic.org/mailman/listinfo/linuxbios -------------- next part -------------- An HTML attachment was scrubbed... URL: From daubin at actuality-systems.com Thu Jul 15 08:31:00 2004 From: daubin at actuality-systems.com (David Aubin) Date: Thu Jul 15 08:31:00 2004 Subject: Can someone please explain this VGABIOS Error Message-ID: <1089900095.6988.22.camel@buildserver1> Hello, I got the testbios built and tried it and got the following error doing: ./testbios -d 0x200 -t vgabios.bin I made my vgabios.bin by doing: dd if=/dev/mem of=vgabios.bin skip=1536 count=128 The error is: c000:00dc 6e OUTSB AX=1cff BX=ffff CX=ff00 DX=60ac SP=fff4 BP=0000 SI=0002 DI=0002 DS=0040 ES=0000 SS=0030 CS=c000 IP=00de NV UP DI PL NZ NA PE NC c000:00dd f4 HALT halt_sys: file ops.c, line 9804 halted AX=1cff BX=ffff CX=ff00 DX=60ac SP=fff4 BP=0000 SI=0002 DI=0002 DS=0040 ES=0000 SS=0030 CS=c000 IP=00de NV UP DI PL NZ NA PE NC c000:00de 6e HALT Can someone please explain this error to me and how to possibly fix it? I have a Tyan mb with a 2885 chipset. AMD64 chip. And an Nvidia FX 5950 video card. Any help would be appreciated:) Thank you, Dave -------------- next part -------------- An HTML attachment was scrubbed... URL: From rminnich at lanl.gov Thu Jul 15 08:42:00 2004 From: rminnich at lanl.gov (ron minnich) Date: Thu Jul 15 08:42:00 2004 Subject: Can someone please explain this VGABIOS Error In-Reply-To: <1089900095.6988.22.camel@buildserver1> Message-ID: david hendricks or ollie, can you send david the command line we use for our vga cards on tyan mb? thanks ron From zhushisongzhu at yahoo.com Thu Jul 15 08:43:00 2004 From: zhushisongzhu at yahoo.com (zhu shi song) Date: Thu Jul 15 08:43:00 2004 Subject: how to read spd(serial presence detect) in linux Message-ID: <20040715141458.37532.qmail@web13201.mail.yahoo.com> I need to know the value of spd byte from linux. Is there any linux utility to read spd bytes? tks zhu --------------------------------- Do you Yahoo!? Yahoo! Mail is new and improved - Check it out! -------------- next part -------------- An HTML attachment was scrubbed... URL: From rminnich at lanl.gov Thu Jul 15 08:47:01 2004 From: rminnich at lanl.gov (ron minnich) Date: Thu Jul 15 08:47:01 2004 Subject: how to read spd(serial presence detect) in linux In-Reply-To: <20040715141458.37532.qmail@web13201.mail.yahoo.com> Message-ID: On Thu, 15 Jul 2004, zhu shi song wrote: > I need to know the value of spd byte from linux. Is there any linux > utility to read spd bytes? what chipset? ron From zhushisongzhu at yahoo.com Thu Jul 15 08:51:01 2004 From: zhushisongzhu at yahoo.com (zhu shi song) Date: Thu Jul 15 08:51:01 2004 Subject: sis630 IPL read wrong number of SPD RAM type Message-ID: <20040715142234.68764.qmail@web13207.mail.yahoo.com> (1) RAM type sis630 IPL.S read is not 04 I debug sis630 IPL.S, I find the RAM type value that IPL read is 01 or 00 for different RAM but not 04. But my RAM is definitely SDRAM. The code is: ........... movb $0x02, %al # Read the RAM Type (SPD byte 2) CALL_SP(read_spd) # of the dram on current DIMM. movb %bl, %al # %bl is 01 or 00 for different RAM,not 04 outb %al, $0x80 cmpb $0x04, %bl # If the RAM Type = SDRAM ?? jne no_sdram # no, exit ....... Is there any bug in the codes reading spd bytes? (2) for some Sis630 mainboard, docipl will hang. Linuxbios can't be executed. I think the RAM initialization procedure is as compatible as BIOS. Thanks zhu --------------------------------- Do you Yahoo!? New and Improved Yahoo! Mail - 100MB free storage! -------------- next part -------------- An HTML attachment was scrubbed... URL: From zhushisongzhu at yahoo.com Thu Jul 15 08:58:01 2004 From: zhushisongzhu at yahoo.com (zhu shi song) Date: Thu Jul 15 08:58:01 2004 Subject: vt5426 can't detect doc millenium Message-ID: <20040715142956.73509.qmail@web13205.mail.yahoo.com> Dear sir, I've got one mainboard named A6T. A6T uses the same VIA northbridge and southbridge as vt5426. I boot linux from the mainboard and insert doc2001 in the BIOS slot. Then run the following commands: insmod docecc insmod doc2001 insmod docprobe these commands can detect doc2001 successfully in SIS630 mainboard. But in A6T they can't detect doc2001. ( I check /proc/mtd file, it is null ). SIS630 need flash_on utility, does VT5426 need some utility? Who knows the cause? thanks zhu --------------------------------- Do you Yahoo!? New and Improved Yahoo! Mail - Send 10MB messages! -------------- next part -------------- An HTML attachment was scrubbed... URL: From rminnich at lanl.gov Thu Jul 15 09:19:01 2004 From: rminnich at lanl.gov (ron minnich) Date: Thu Jul 15 09:19:01 2004 Subject: sis630 IPL read wrong number of SPD RAM type In-Reply-To: <20040715142234.68764.qmail@web13207.mail.yahoo.com> Message-ID: some mobos (ASUS) have special requirements for enabling SPD for dram. I think you have a motherboard that works that way. ron From ucapajr at yahoo.co.uk Thu Jul 15 10:08:01 2004 From: ucapajr at yahoo.co.uk (=?iso-8859-1?q?Andrew=20Richardson?=) Date: Thu Jul 15 10:08:01 2004 Subject: SiS 530 Message-ID: <20040715154009.9377.qmail@web60007.mail.yahoo.com> Dear All, I am new to this list and have been emailing Ron a few times about the SiS530. Ron sugested that I use FILO for my project and I have had a trawl around to find filo, and have downloaded a BZ from a fairly unreputable looking web site. Does anyone have the "official" website address at all? Also Ron said to configure LinuxBIOS for the 530, but I thought that it was not supported by the LinuxBIOS project. I understand (basically) the idea of having payload code (which is filo from your advice), but I think I may need some more explicit instructions: do I assume correctly that I need to flash my current 530 board bios with LinuxBIOS with a payload of filo and have filo point to boot off HDA1? Then this leads me onto another question: can I pull a bios chip from another PC and use that to flash LB onto to use with the 530, or are some regions of the BIOS chip un-writable and/or mobo specific? If the latter then would it not be safer to get a small DoC and flash that, as I only have one 530 Mobo. Thanks andy ___________________________________________________________ALL-NEW Yahoo! Messenger - sooooo many all-new ways to express yourself http://uk.messenger.yahoo.com From ollie at lanl.gov Thu Jul 15 10:18:00 2004 From: ollie at lanl.gov (Li-Ta Lo) Date: Thu Jul 15 10:18:00 2004 Subject: Serenade BIOS In-Reply-To: <000401c46a09$3b9e8170$932614ac@trans.corp> References: <002001c469d7$3d168e30$919814ac@trans.corp> <1089833365.3822.8.camel@exponential.lanl.gov> <000401c46a09$3b9e8170$932614ac@trans.corp> Message-ID: <1089906598.3822.17.camel@exponential.lanl.gov> On Wed, 2004-07-14 at 19:15, Tony Cheng wrote: > After I comment out the "init_pc_keyboard" from superio.c, Serenade > LinuxBIOS boots muck better. > > For the keyboard support, the AMI BIOS which come with the Serenade board > works OK, do you have any comment on this? > No. I thought the porting was an easy one but I was wrong. There is something I don't know about the board. Unfortunately, I have no interest in digging any further at the moment. Ollie From ollie at lanl.gov Thu Jul 15 10:20:01 2004 From: ollie at lanl.gov (Li-Ta Lo) Date: Thu Jul 15 10:20:01 2004 Subject: SiS 530 In-Reply-To: <20040715154009.9377.qmail@web60007.mail.yahoo.com> References: <20040715154009.9377.qmail@web60007.mail.yahoo.com> Message-ID: <1089906704.3822.19.camel@exponential.lanl.gov> On Thu, 2004-07-15 at 09:40, Andrew Richardson wrote: > Dear All, > I am new to this list and have been emailing Ron a few > times about the SiS530. > Ron sugested that I use FILO for my project and > I have had a trawl around to find filo, and have > downloaded a BZ from a fairly unreputable looking web > site. Does anyone have the "official" website > address at all? > > Also Ron said to configure LinuxBIOS for the 530, but > I thought that it was not supported by the LinuxBIOS > project. > > I understand (basically) the idea of having payload > code (which is filo from your advice), but I think I > may need some more explicit instructions: do I assume > correctly that I need to flash my current 530 board > bios with LinuxBIOS with a payload of filo and have > filo point to boot off HDA1? > > Then this leads me onto another question: can I pull > a bios chip from another PC and use that to flash LB > onto to use with the 530, or are some regions of the > BIOS chip un-writable and/or mobo specific? If the > latter then would it not be safer to get a small DoC > and flash that, as I only have one 530 Mobo. > Can you still get SiS 530 board this day ? I thought it is obsoleted long time ago. Ollie From ollie at lanl.gov Thu Jul 15 10:27:00 2004 From: ollie at lanl.gov (Li-Ta Lo) Date: Thu Jul 15 10:27:00 2004 Subject: Can someone please explain this VGABIOS Error In-Reply-To: <1089900095.6988.22.camel@buildserver1> References: <1089900095.6988.22.camel@buildserver1> Message-ID: <1089907123.3822.25.camel@exponential.lanl.gov> On Thu, 2004-07-15 at 08:01, David Aubin wrote: > Hello, > > I got the testbios built and tried it and got the following error > doing: > ./testbios -d 0x200 -t vgabios.bin > > I made my vgabios.bin by doing: > dd if=/dev/mem of=vgabios.bin skip=1536 count=128 > > The error is: > c000:00dc 6e OUTSB > AX=1cff BX=ffff CX=ff00 DX=60ac SP=fff4 BP=0000 SI=0002 > DI=0002 > DS=0040 ES=0000 SS=0030 CS=c000 IP=00de NV UP DI PL NZ > NA PE NC > c000:00dd f4 HALT > halt_sys: file ops.c, line 9804 > halted > AX=1cff BX=ffff CX=ff00 DX=60ac SP=fff4 BP=0000 SI=0002 > DI=0002 > DS=0040 ES=0000 SS=0030 CS=c000 IP=00de NV UP DI PL NZ > NA PE NC > c000:00de 6e HALT > > > Can someone please explain this error to me and how to possibly fix > it? > It means there was NO ERROR. It ran perfectly. If it is the case, you should see acrambled screen at this point. > I have a Tyan mb with a 2885 chipset. AMD64 chip. And an Nvidia FX > 5950 video card. > Any help would be appreciated:) > The correct command line would be: ./testbios -s 65536 -d 0x200 -t --abseg /dev/mem ../nvbios.bin BTW, you need recent CVS tree to make it work on s2885. Ollie > Thank you, > Dave From daubin at actuality-systems.com Thu Jul 15 10:39:01 2004 From: daubin at actuality-systems.com (David Aubin) Date: Thu Jul 15 10:39:01 2004 Subject: Can someone please explain this VGABIOS Error In-Reply-To: <1089907123.3822.25.camel@exponential.lanl.gov> References: <1089900095.6988.22.camel@buildserver1> <1089907123.3822.25.camel@exponential.lanl.gov> Message-ID: <1089907759.6988.42.camel@buildserver1> Yeah, its works:) Just to recap for anyone reading this thread after me:dd if=/dev/mem of=vgabios.bin skip=1536 count=128 1. Get http://atrey.karlin.mff.cuni.cz/~mj/pciutils.shtml 2. Get the freebios2 source 3. Build the freebios2/util/vgabios A. You may need to modify makefiles to suit your needs I did in order to get it to build under a 64 bit machine. You want 32 bit apps. 4. Do dd if=/dev/mem of=vgabios.bin skip=1536 count=128 on the card when it up and running normally 5. On the target machine, preferably in your initrd Put the following line: ./testbios -s 65536 -d 0x200 -t --abseg /dev/mem ./vgabios Thank you for all your help:):):):) Thanks, Dave On Thu, 2004-07-15 at 11:58, Li-Ta Lo wrote: > On Thu, 2004-07-15 at 08:01, David Aubin wrote: > > Hello, > > > > I got the testbios built and tried it and got the following error > > doing: > > ./testbios -d 0x200 -t vgabios.bin > > > > I made my vgabios.bin by doing: > > dd if=/dev/mem of=vgabios.bin skip=1536 count=128 > > > > The error is: > > c000:00dc 6e OUTSB > > AX=1cff BX=ffff CX=ff00 DX=60ac SP=fff4 BP=0000 SI=0002 > > DI=0002 > > DS=0040 ES=0000 SS=0030 CS=c000 IP=00de NV UP DI PL NZ > > NA PE NC > > c000:00dd f4 HALT > > halt_sys: file ops.c, line 9804 > > halted > > AX=1cff BX=ffff CX=ff00 DX=60ac SP=fff4 BP=0000 SI=0002 > > DI=0002 > > DS=0040 ES=0000 SS=0030 CS=c000 IP=00de NV UP DI PL NZ > > NA PE NC > > c000:00de 6e HALT > > > > > > Can someone please explain this error to me and how to possibly fix > > it? > > > > It means there was NO ERROR. It ran perfectly. If it is the case, you > should see acrambled screen at this point. > > > I have a Tyan mb with a 2885 chipset. AMD64 chip. And an Nvidia FX > > 5950 video card. > > Any help would be appreciated:) > > > > The correct command line would be: > > ./testbios -s 65536 -d 0x200 -t --abseg /dev/mem ../nvbios.bin > > BTW, you need recent CVS tree to make it work on s2885. > > Ollie > > > Thank you, > > Dave > -------------- next part -------------- An HTML attachment was scrubbed... URL: From dwh at lanl.gov Thu Jul 15 12:00:01 2004 From: dwh at lanl.gov (Hendricks David W.) Date: Thu Jul 15 12:00:01 2004 Subject: SiS 530 In-Reply-To: <20040715154009.9377.qmail@web60007.mail.yahoo.com> Message-ID: > Ron sugested that I use FILO for my project and > I have had a trawl around to find filo, and have > downloaded a BZ from a fairly unreputable looking web > site. Does anyone have the "official" website > address at all? http://te.to/~ts1/filo/ No fancy graphics, but effective none the less. > Also Ron said to configure LinuxBIOS for the 530, but > I thought that it was not supported by the LinuxBIOS > project. Hmm, might've been thinking of the SiS630. > may need some more explicit instructions: do I assume > correctly that I need to flash my current 530 board > bios with LinuxBIOS with a payload of filo and have > filo point to boot off HDA1? Correct. > Then this leads me onto another question: can I pull > a bios chip from another PC and use that to flash LB > onto to use with the 530, or are some regions of the > BIOS chip un-writable and/or mobo specific? If the > latter then would it not be safer to get a small DoC > and flash that, as I only have one 530 Mobo. Yes, you may use another PC for flashing. I do that all the time here at LANL since I usually render my target machine unbootable and have to use another machine to flash a part to fix it :) Be careful, you might run into compatibility issues going between machines having to do with the type of programmer the southbridge uses (parallel programming mode or LPC). And you might have to use MTD to flash on an old southbridge like the 530. From rminnich at lanl.gov Thu Jul 15 13:44:00 2004 From: rminnich at lanl.gov (ron minnich) Date: Thu Jul 15 13:44:00 2004 Subject: Can someone please explain this VGABIOS Error In-Reply-To: <1089907759.6988.42.camel@buildserver1> Message-ID: On Thu, 15 Jul 2004, David Aubin wrote: > Yeah, its works:) GREAT! Wanna write a howto and FAQ? ron From daubin at actuality-systems.com Thu Jul 15 14:13:00 2004 From: daubin at actuality-systems.com (David Aubin) Date: Thu Jul 15 14:13:00 2004 Subject: Can someone please explain this VGABIOS Error In-Reply-To: References: Message-ID: <1089920606.5923.8.camel@buildserver1> Hi Ron, It is good to give. I think I will, just please don't hold your breath on this. Thanks, Dave On Thu, 2004-07-15 at 15:15, ron minnich wrote: > On Thu, 15 Jul 2004, David Aubin wrote: > > > Yeah, its works:) > > > GREAT! > > Wanna write a howto and FAQ? > > ron > -------------- next part -------------- An HTML attachment was scrubbed... URL: From dwh at lanl.gov Thu Jul 15 14:19:00 2004 From: dwh at lanl.gov (Hendricks David W.) Date: Thu Jul 15 14:19:00 2004 Subject: Can someone please explain this VGABIOS Error In-Reply-To: <1089920606.5923.8.camel@buildserver1> Message-ID: So what's your current status, anyway? You boot with LinuxBIOS and FILO/Etherboot, then log in remotely (Serial or ethernet?) and run the testbios, then start X? Are you using framebuffering or anything for console support? On Thu, 15 Jul 2004, David Aubin wrote: > Hi Ron, > > It is good to give. I think I will, just please don't hold your > breath on this. > > Thanks, > Dave > On Thu, 2004-07-15 at 15:15, ron minnich wrote: > > > On Thu, 15 Jul 2004, David Aubin wrote: > > > > > Yeah, its works:) > > > > > > GREAT! > > > > Wanna write a howto and FAQ? > > > > ron > > > From daubin at actuality-systems.com Thu Jul 15 14:31:01 2004 From: daubin at actuality-systems.com (David Aubin) Date: Thu Jul 15 14:31:01 2004 Subject: Can someone please explain this VGABIOS Error In-Reply-To: References: Message-ID: <1089921684.5923.19.camel@buildserver1> Current status is this: 1. Boot with linux bios on Tyan MB with 2885 chipset 2. Linux bios payload is my custom (static ip support) etherboot with filo 3. etherboot then remotely retrieves elf image of a 2.6 kernel and initrd A. filo with usb does not work for some reason with my setup, it is something I want/need 4. Then USB stick is mounted with custom initrd to USB support 5. Home made 2.6 linux boots up 6. inside boot.local I have the call to enable Nvidia bios ./testbios -s 65536 -d 0x200 -t --abseg /dev/mem ./vgabios 7. Then I have currently xf86config configured to use old nv driver(#18?) for x windows. A. I'm in the process now of integrating the new Nvidia driver and that is my goal. Appendix: A. I can log in via serial console or remotely with (tftp, rlogin, ssh for debugging) On Thu, 2004-07-15 at 15:50, Hendricks David W. wrote: > So what's your current status, anyway? You boot with LinuxBIOS and > FILO/Etherboot, then log in remotely (Serial or ethernet?) and run the > testbios, then start X? Are you using framebuffering or anything for > console support? > > On Thu, 15 Jul 2004, David Aubin wrote: > > > Hi Ron, > > > > It is good to give. I think I will, just please don't hold your > > breath on this. > > > > Thanks, > > Dave > > On Thu, 2004-07-15 at 15:15, ron minnich wrote: > > > > > On Thu, 15 Jul 2004, David Aubin wrote: > > > > > > > Yeah, its works:) > > > > > > > > > GREAT! > > > > > > Wanna write a howto and FAQ? > > > > > > ron > > > > > > -------------- next part -------------- An HTML attachment was scrubbed... URL: From dwh at lanl.gov Thu Jul 15 14:47:00 2004 From: dwh at lanl.gov (Hendricks David W.) Date: Thu Jul 15 14:47:00 2004 Subject: Can someone please explain this VGABIOS Error In-Reply-To: <1089921684.5923.19.camel@buildserver1> Message-ID: Sounds good, any HOWTOs you can produce should be an interesting read. If you have any difficulty with AGP, let us know. We've tested the S2885 with a GeForce FX 5600 card with nVidia's driver and Linux AGPGART and have been rather pleased with the results. On Thu, 15 Jul 2004, David Aubin wrote: > Current status is this: > 1. Boot with linux bios on Tyan MB with 2885 chipset > 2. Linux bios payload is my custom (static ip support) etherboot with > filo > 3. etherboot then remotely retrieves elf image of a 2.6 kernel and > initrd > A. filo with usb does not work for some reason with my setup, it is > something I want/need > 4. Then USB stick is mounted with custom initrd to USB support > 5. Home made 2.6 linux boots up > 6. inside boot.local I have the call to enable Nvidia bios > ./testbios -s 65536 -d 0x200 -t --abseg /dev/mem ./vgabios > 7. Then I have currently xf86config configured to use old nv > driver(#18?) for x windows. > A. I'm in the process now of integrating the new Nvidia driver and > that is my goal. > > Appendix: > A. I can log in via serial console or remotely with (tftp, rlogin, ssh > for debugging) > > > On Thu, 2004-07-15 at 15:50, Hendricks David W. wrote: > > > So what's your current status, anyway? You boot with LinuxBIOS and > > FILO/Etherboot, then log in remotely (Serial or ethernet?) and run the > > testbios, then start X? Are you using framebuffering or anything for > > console support? > > > > On Thu, 15 Jul 2004, David Aubin wrote: > > > > > Hi Ron, > > > > > > It is good to give. I think I will, just please don't hold your > > > breath on this. > > > > > > Thanks, > > > Dave > > > On Thu, 2004-07-15 at 15:15, ron minnich wrote: > > > > > > > On Thu, 15 Jul 2004, David Aubin wrote: > > > > > > > > > Yeah, its works:) > > > > > > > > > > > > GREAT! > > > > > > > > Wanna write a howto and FAQ? > > > > > > > > ron > > > > > > > > > > From daubin at actuality-systems.com Thu Jul 15 14:56:01 2004 From: daubin at actuality-systems.com (David Aubin) Date: Thu Jul 15 14:56:01 2004 Subject: Can someone please explain this VGABIOS Error In-Reply-To: References: Message-ID: <1089923154.5923.23.camel@buildserver1> I only have a partial hand in it. Another guy here named Jay Miller got me going. Along with everyone else here who helped me:) Thanks everybody:) On Thu, 2004-07-15 at 16:18, Hendricks David W. wrote: > Sounds good, any HOWTOs you can produce should be an interesting read. > > If you have any difficulty with AGP, let us know. We've tested the S2885 > with a GeForce FX 5600 card with nVidia's driver and Linux AGPGART and > have been rather pleased with the results. > > On Thu, 15 Jul 2004, David Aubin wrote: > > > Current status is this: > > 1. Boot with linux bios on Tyan MB with 2885 chipset > > 2. Linux bios payload is my custom (static ip support) etherboot with > > filo > > 3. etherboot then remotely retrieves elf image of a 2.6 kernel and > > initrd > > A. filo with usb does not work for some reason with my setup, it is > > something I want/need > > 4. Then USB stick is mounted with custom initrd to USB support > > 5. Home made 2.6 linux boots up > > 6. inside boot.local I have the call to enable Nvidia bios > > ./testbios -s 65536 -d 0x200 -t --abseg /dev/mem ./vgabios > > 7. Then I have currently xf86config configured to use old nv > > driver(#18?) for x windows. > > A. I'm in the process now of integrating the new Nvidia driver and > > that is my goal. > > > > Appendix: > > A. I can log in via serial console or remotely with (tftp, rlogin, ssh > > for debugging) > > > > > > On Thu, 2004-07-15 at 15:50, Hendricks David W. wrote: > > > > > So what's your current status, anyway? You boot with LinuxBIOS and > > > FILO/Etherboot, then log in remotely (Serial or ethernet?) and run the > > > testbios, then start X? Are you using framebuffering or anything for > > > console support? > > > > > > On Thu, 15 Jul 2004, David Aubin wrote: > > > > > > > Hi Ron, > > > > > > > > It is good to give. I think I will, just please don't hold your > > > > breath on this. > > > > > > > > Thanks, > > > > Dave > > > > On Thu, 2004-07-15 at 15:15, ron minnich wrote: > > > > > > > > > On Thu, 15 Jul 2004, David Aubin wrote: > > > > > > > > > > > Yeah, its works:) > > > > > > > > > > > > > > > GREAT! > > > > > > > > > > Wanna write a howto and FAQ? > > > > > > > > > > ron > > > > > > > > > > > > > > > -------------- next part -------------- An HTML attachment was scrubbed... URL: From rsmith at bitworks.com Thu Jul 15 15:04:01 2004 From: rsmith at bitworks.com (Richard Smith) Date: Thu Jul 15 15:04:01 2004 Subject: V1 PIRQ table In-Reply-To: <40F59476.5090902@bitworks.com> References: <40F59476.5090902@bitworks.com> Message-ID: <40F6EAA9.6070908@bitworks.com> ron minnich wrote: things like "Copying tables..." and then "Verifying..." and the function called write_tables(). So I just assumed it was stuck in ROM at any old location and moved to the correct position. > yes, that code is very annoying. I Look at the PIRQ code. The code that I looked at was the stuff included with HAVE_PIRQ_TABLE=1 and it most definintly _copies_ the table to 0xf0000. So for this code to work shadowing must be setup. Unless there is some linker magic going on that actually locates the structure at that location in the ROM as well then PIRQ stuff will not work w/o shadowing. On my build the table is located in the ROM image and will show up at 0xf2e29. Linux searches for the table from 0xf0000 to 0x100000 but only at mutiples of 0x0f. So linux will not find this table. There must be some sort of ELF section alignment thats missing in the linking of irq_tables.o From rsmith at bitworks.com Thu Jul 15 15:11:01 2004 From: rsmith at bitworks.com (Richard Smith) Date: Thu Jul 15 15:11:01 2004 Subject: V1 PIRQ table In-Reply-To: References: Message-ID: <40F6EC48.2050309@bitworks.com> ron minnich wrote: > no, it's worse than that. > > If the copy fails, and you're uncompressed, and you don't map ram over > flash, the table is still there. > > Yeah, it sucks all right. > >>There must be some sort of ELF section alignment thats missing in the >>linking of irq_tables.o > > We have to fix this. I just never had time. Can't ELF do alignments? If so then we can just create this table into a seperate section and tell the linker to align it properly or perhaps locate it absolutly. From rminnich at lanl.gov Thu Jul 15 15:31:01 2004 From: rminnich at lanl.gov (ron minnich) Date: Thu Jul 15 15:31:01 2004 Subject: V1 PIRQ table In-Reply-To: <40F6EC48.2050309@bitworks.com> Message-ID: On Thu, 15 Jul 2004, Richard Smith wrote: > Can't ELF do alignments? If so then we can just create this table into > a seperate section and tell the linker to align it properly or perhaps > locate it absolutly. If somebody can take a look at the .lds I think it is easy. I can't do it today. ron From ollie at lanl.gov Thu Jul 15 15:54:00 2004 From: ollie at lanl.gov (Li-Ta Lo) Date: Thu Jul 15 15:54:00 2004 Subject: V1 PIRQ table In-Reply-To: References: Message-ID: <1089926769.3822.47.camel@exponential.lanl.gov> On Thu, 2004-07-15 at 15:02, ron minnich wrote: > On Thu, 15 Jul 2004, Richard Smith wrote: > > > Can't ELF do alignments? If so then we can just create this table into > > a seperate section and tell the linker to align it properly or perhaps > > locate it absolutly. > > If somebody can take a look at the .lds I think it is easy. I can't do it > today. > The problem Richard has is the PRIQ table is not "aligned" correct. It is placed corrected in the F segment. It has nothing to do with .lds. The way to solve it is to use a gcc __attribute__. (which Ron hates a lot) Ollie > ron > > _______________________________________________ > Linuxbios mailing list > Linuxbios at clustermatic.org > http://www.clustermatic.org/mailman/listinfo/linuxbios > From rsmith at bitworks.com Thu Jul 15 17:10:01 2004 From: rsmith at bitworks.com (Richard Smith) Date: Thu Jul 15 17:10:01 2004 Subject: V1 PIRQ table In-Reply-To: <1089926769.3822.47.camel@exponential.lanl.gov> References: <1089926769.3822.47.camel@exponential.lanl.gov> Message-ID: <40F70836.5000305@bitworks.com> Li-Ta Lo wrote: > The problem Richard has is the PRIQ table is not "aligned" correct. It > is placed corrected in the F segment. It has nothing to do with .lds. > The way to solve it is to use a gcc __attribute__. (which Ron hates > a lot) I don't have much experience with the internals of ELF stuff but the way I normally solve things like this in most of our microcontroller setups is to define the .c file to be in in own linker section and then place that section such that it will align correctly. irq_tables.c has nothing else in it but the PIR table so can we set that up as its own section and then specify some parameter so that it can be explicitly placed? From rminnich at lanl.gov Thu Jul 15 17:14:00 2004 From: rminnich at lanl.gov (ron minnich) Date: Thu Jul 15 17:14:00 2004 Subject: V1 PIRQ table In-Reply-To: <40F70836.5000305@bitworks.com> Message-ID: On Thu, 15 Jul 2004, Richard Smith wrote: > I don't have much experience with the internals of ELF stuff but the way > I normally solve things like this in most of our microcontroller setups > is to define the .c file to be in in own linker section and then place > that section such that it will align correctly. > > irq_tables.c has nothing else in it but the PIR table so can we set that > up as its own section and then specify some parameter so that it can be > explicitly placed? no, do what ollie says and add the __align__ attribute to the table. That's simple and will work without changing much else. thanks ron From rsmith at bitworks.com Thu Jul 15 17:40:01 2004 From: rsmith at bitworks.com (Richard Smith) Date: Thu Jul 15 17:40:01 2004 Subject: V1 PIRQ table In-Reply-To: References: Message-ID: <40F70F3C.9020406@bitworks.com> ron minnich wrote: > On Thu, 15 Jul 2004, Richard Smith wrote: > > no, do what ollie says and add the __align__ attribute to the table. > That's simple and will work without changing much else. Oops... Looks like I was WAY off. My problem was that ADLO contains it's own PIR table and it was messed up. So linux never reached the linux bios PIR table. The 0xf2e29 was actually the PIR in the verify _code_ and not the actual table. My rom image has 3 PIR strings rather than 2. The table is showing up at 0xf8310 which is aligned correctly. The write_tables() code still fails though due to no shadowing at that stage in the boot. From zhushisongzhu at yahoo.com Thu Jul 15 20:43:01 2004 From: zhushisongzhu at yahoo.com (zhu shi song) Date: Thu Jul 15 20:43:01 2004 Subject: (no subject) Message-ID: <20040716021448.38048.qmail@web13201.mail.yahoo.com> I find winfast 6300 Max pro using Sis630e chipset. The problem of reading spd RAM type byte is also return 01 or 00 for different SDRAM but no 04. Is it a problem? thanks zhu --------------------------------- Do you Yahoo!? Yahoo! Mail - 50x more storage than other providers! -------------- next part -------------- An HTML attachment was scrubbed... URL: From zhushisongzhu at yahoo.com Fri Jul 16 07:28:01 2004 From: zhushisongzhu at yahoo.com (zhu shi song) Date: Fri Jul 16 07:28:01 2004 Subject: sis630 ipl SDRAM initializtion make some trouble Message-ID: <20040716130017.45213.qmail@web13205.mail.yahoo.com> I've got two kind of sis630e motherboard, one is winfast 6300 Max pro, the other is from ellite group. (1) for winfast 6300 I've burned one DOC2001 to boot it, for some SDRAM it works well, for some other SDRAM it can't boot, it hangup on jmp spl_vector(after my debug testing ). (2) for ellite board The same doc2001 chip which works well on winfast 6300 can't boot ellite board. It also hangup on jmp spl_vector. For some SDRAM it can boot linux, but linux will hangup at anytime. (3) conclusion I think IPL SDRAM initialization has some problem. So the SDRAM can't work stably. Who has sis630 manual? I can check if I can adjust the SDRAM control parameters. Or someone can point out what's the exact reason causing the problem. tks zhu --------------------------------- Do you Yahoo!? New and Improved Yahoo! Mail - 100MB free storage! -------------- next part -------------- An HTML attachment was scrubbed... URL: From ollie at lanl.gov Fri Jul 16 08:59:01 2004 From: ollie at lanl.gov (Li-Ta Lo) Date: Fri Jul 16 08:59:01 2004 Subject: sis630 ipl SDRAM initializtion make some trouble In-Reply-To: <20040716130017.45213.qmail@web13205.mail.yahoo.com> References: <20040716130017.45213.qmail@web13205.mail.yahoo.com> Message-ID: <1089988224.3822.55.camel@exponential.lanl.gov> On Fri, 2004-07-16 at 07:00, zhu shi song wrote: > I've got two kind of sis630e motherboard, one is winfast 6300 Max pro, > the other is from ellite group. > (1) for winfast 6300 > I've burned one DOC2001 to boot it, for some SDRAM it works well, > for some other SDRAM it can't boot, it hangup on jmp spl_vector(after > my debug testing ). > (2) for ellite board > The same doc2001 chip which works well on winfast 6300 can't boot > ellite board. It also hangup on jmp spl_vector. For some SDRAM it > can boot linux, but linux will hangup at anytime. > (3) conclusion > I think IPL SDRAM initialization has some problem. So the SDRAM can't > work stably. Who has sis630 manual? I can check if I can adjust the > SDRAM control parameters. Or someone can point out what's the exact > reason causing the problem. It is known that some SDRAM DIMM have broken SPD data. Probably your SDRAM is one of them. Are you using the same image for both winfast and ecs ? You need different image for different mainboard. Nobody outside SiS have the manual. You have to ask SiS for the manual, good luck. Ollie From rminnich at lanl.gov Fri Jul 16 15:15:01 2004 From: rminnich at lanl.gov (ron minnich) Date: Fri Jul 16 15:15:01 2004 Subject: I'm offline for a period of time Message-ID: ----- Message Text ----- There is some work going on here and I will not be available for technical discussions. I hope to be back in a bit. thanks ron From dwh at lanl.gov Fri Jul 16 15:24:00 2004 From: dwh at lanl.gov (Hendricks David W.) Date: Fri Jul 16 15:24:00 2004 Subject: I'm offline for a period of time In-Reply-To: Message-ID: Same goes for me and Ollie. On Fri, 16 Jul 2004, ron minnich wrote: > ----- Message Text ----- > There is some work going on here and I will not be available for technical > discussions. > > I hope to be back in a bit. > > thanks > > ron > > > > > _______________________________________________ > Linuxbios mailing list > Linuxbios at clustermatic.org > http://www.clustermatic.org/mailman/listinfo/linuxbios > From zhushisongzhu at yahoo.com Sat Jul 17 01:37:00 2004 From: zhushisongzhu at yahoo.com (zhu shi song) Date: Sat Jul 17 01:37:00 2004 Subject: how to setup dll.inc of sis630 Message-ID: <20040717070907.5701.qmail@web13204.mail.yahoo.com> I've got elitegroup MB P6STMT based sis630e. It's hard for me to setup the correct value of dll.inc(0x8c~0x8f). (1) I copy the value from winfast6300. My Doc2001 can boot but linux kernel will hangup. (2) I copy the value from pcchips/m787cl+. MB halt. (3) I copy the value from elitegroup/p6stp-fl. It is just the same as winfast6300. who know how to guess the four values in dll.inc? thanks zhu --------------------------------- Do you Yahoo!? Vote for the stars of Yahoo!'s next ad campaign! -------------- next part -------------- An HTML attachment was scrubbed... URL: From zhushisongzhu at yahoo.com Sat Jul 17 05:58:00 2004 From: zhushisongzhu at yahoo.com (zhu shi song) Date: Sat Jul 17 05:58:00 2004 Subject: sis630et and sis630 difference Message-ID: <20040717113008.7319.qmail@web13207.mail.yahoo.com> The only difference between ecs p6stmt MB and winfast6300 is that they use the different sis chipset. P6stmt use sis630ET, winfast6300 use sis630. So Doc2001 which can work on winfast6300 can't work on P6stmt. Is it right? thanks zhu --------------------------------- Do you Yahoo!? Vote for the stars of Yahoo!'s next ad campaign! -------------- next part -------------- An HTML attachment was scrubbed... URL: From leidenfrost at corscience.de Mon Jul 19 06:45:00 2004 From: leidenfrost at corscience.de (Thomas Leidenfrost) Date: Mon Jul 19 06:45:00 2004 Subject: Compile Error while doing make Message-ID: <40FBBB05.3000700@corscience.de> Hello, after using the config-file from the Advantech PCM-5823 and adding the option "HAVE_FRAMEBUFFER=1" in the config-file I got this Errormessage: (kernelpath set to systemkernel 2.6.7) holodoc:/home/thomasle/Desktop/awb651 # make gcc -x assembler-with-cpp -DASSEMBLY -E ... crt0.S > crt0.s gcc ... -o crt0.o crt0.s crt0.S: Assembler messages: crt0.S:156: Warning: indirect jmp without `*' gcc ... -o version.o /home/thomasle/freebios/src/lib/version.c gcc ... -o mainboard.o /home/thomasle/freebios/src/mainboard/ics-d/awb651/mainboard.c gcc ... -o irq_tables.o /home/thomasle/freebios/src/mainboard/ics-d/awb651/irq_tables.c rm -f linuxbios.a ar cr linuxbios.a linuxbiosmain.o linuxpci.o newpci.o clog2.o printk.o serial_subr.o subr.o vsprintf.o memset.o memcpy.o memcmp.o malloc.o elfboot.o do_inflate.o delay.o compute_ip_checksum.o version.o keyboard.o mc146818rtc.o isa-dma.o ide.o boot.o linuxbios_table.o i386_subr.o params.o hardwaremain.o pirq_routing.o c_start.o cpuid.o delay_tsc.o northbridge.o southbridge.o superio_SMC_fdc37b72x.o nsuperio.o mainboard.o irq_tables.o gcc -nostdlib -r -o linuxbios_c.o c_start.o rom_fill_inbuf.o linuxbios.a /usr/lib/gcc-lib/i586-suse-linux/3.3.1/libgcc.a perl -e 'foreach $var (split(" ", $ENV{VARIABLES})) { if ($ENV{$var} =~ m/^(0x[0-9a-fA-F]+|0[0-7]+|[0-9]+)$/) { print "$var = $ENV{$var};\n"; }}' > ldoptions gcc -nostdlib -nostartfiles -static -o linuxbios_c -T /home/thomasle/freebios/src/config/linuxbios_c.ld linuxbios_c.o linuxbios_c.o(.text+0xa56): In function `hardwaremain': : undefined reference to `framebuffer_on' collect2: ld returned 1 exit status make: *** [linuxbios_c] Error 1 Can anyone give me a hint please? What did I wrong? Thx, Tom From daubin at actuality-systems.com Mon Jul 19 07:36:01 2004 From: daubin at actuality-systems.com (David Aubin) Date: Mon Jul 19 07:36:01 2004 Subject: Compile Error while doing make In-Reply-To: <40FBBB05.3000700@corscience.de> References: <40FBBB05.3000700@corscience.de> Message-ID: <1090242415.25918.1.camel@buildserver1> Hi, Well I have not used PCM or Frame buffering, but your error looks like you have the framebuffer definition/ prototype, but no implementation. Look for where `framebuffer_on' is implemented and see if there is an additional compile switch needed to build this in for support. Hope this helps. Dave On Mon, 2004-07-19 at 08:13, Thomas Leidenfrost wrote: > Hello, > > > after using the config-file from the Advantech PCM-5823 and adding the > option "HAVE_FRAMEBUFFER=1" in the config-file I got this Errormessage: > (kernelpath set to systemkernel 2.6.7) > > holodoc:/home/thomasle/Desktop/awb651 # make > gcc -x assembler-with-cpp -DASSEMBLY -E ... crt0.S > crt0.s > gcc ... -o crt0.o crt0.s > crt0.S: Assembler messages: > crt0.S:156: Warning: indirect jmp without `*' > gcc ... -o version.o /home/thomasle/freebios/src/lib/version.c > gcc ... -o mainboard.o > /home/thomasle/freebios/src/mainboard/ics-d/awb651/mainboard.c > gcc ... -o irq_tables.o > /home/thomasle/freebios/src/mainboard/ics-d/awb651/irq_tables.c > rm -f linuxbios.a > ar cr linuxbios.a linuxbiosmain.o linuxpci.o newpci.o clog2.o printk.o > serial_subr.o subr.o vsprintf.o memset.o memcpy.o memcmp.o malloc.o > elfboot.o do_inflate.o delay.o compute_ip_checksum.o version.o > keyboard.o mc146818rtc.o isa-dma.o ide.o boot.o linuxbios_table.o > i386_subr.o params.o hardwaremain.o pirq_routing.o c_start.o cpuid.o > delay_tsc.o northbridge.o southbridge.o superio_SMC_fdc37b72x.o > nsuperio.o mainboard.o irq_tables.o > gcc -nostdlib -r -o linuxbios_c.o c_start.o rom_fill_inbuf.o > linuxbios.a /usr/lib/gcc-lib/i586-suse-linux/3.3.1/libgcc.a > perl -e 'foreach $var (split(" ", $ENV{VARIABLES})) { if ($ENV{$var} =~ > m/^(0x[0-9a-fA-F]+|0[0-7]+|[0-9]+)$/) { print "$var = $ENV{$var};\n"; > }}' > ldoptions > gcc -nostdlib -nostartfiles -static -o linuxbios_c -T > /home/thomasle/freebios/src/config/linuxbios_c.ld linuxbios_c.o > linuxbios_c.o(.text+0xa56): In function `hardwaremain': > : undefined reference to `framebuffer_on' > collect2: ld returned 1 exit status > make: *** [linuxbios_c] Error 1 > > > Can anyone give me a hint please? What did I wrong? > > > Thx, Tom > > _______________________________________________ > Linuxbios mailing list > Linuxbios at clustermatic.org > http://www.clustermatic.org/mailman/listinfo/linuxbios -------------- next part -------------- An HTML attachment was scrubbed... URL: From daubin at actuality-systems.com Mon Jul 19 07:51:00 2004 From: daubin at actuality-systems.com (David Aubin) Date: Mon Jul 19 07:51:00 2004 Subject: Compile Error while doing make In-Reply-To: <40FBBB05.3000700@corscience.de> References: <40FBBB05.3000700@corscience.de> Message-ID: <1090243336.25918.4.camel@buildserver1> Hi Again, Just out of curiosity I poked around again and I don't think the PCM-5823 has support for the frame buffering. You could try VGA bios/testbios to get your card to initialize. You'll need pcituils to compile it, but it should work. Dave On Mon, 2004-07-19 at 08:13, Thomas Leidenfrost wrote: > Hello, > > > after using the config-file from the Advantech PCM-5823 and adding the > option "HAVE_FRAMEBUFFER=1" in the config-file I got this Errormessage: > (kernelpath set to systemkernel 2.6.7) > > holodoc:/home/thomasle/Desktop/awb651 # make > gcc -x assembler-with-cpp -DASSEMBLY -E ... crt0.S > crt0.s > gcc ... -o crt0.o crt0.s > crt0.S: Assembler messages: > crt0.S:156: Warning: indirect jmp without `*' > gcc ... -o version.o /home/thomasle/freebios/src/lib/version.c > gcc ... -o mainboard.o > /home/thomasle/freebios/src/mainboard/ics-d/awb651/mainboard.c > gcc ... -o irq_tables.o > /home/thomasle/freebios/src/mainboard/ics-d/awb651/irq_tables.c > rm -f linuxbios.a > ar cr linuxbios.a linuxbiosmain.o linuxpci.o newpci.o clog2.o printk.o > serial_subr.o subr.o vsprintf.o memset.o memcpy.o memcmp.o malloc.o > elfboot.o do_inflate.o delay.o compute_ip_checksum.o version.o > keyboard.o mc146818rtc.o isa-dma.o ide.o boot.o linuxbios_table.o > i386_subr.o params.o hardwaremain.o pirq_routing.o c_start.o cpuid.o > delay_tsc.o northbridge.o southbridge.o superio_SMC_fdc37b72x.o > nsuperio.o mainboard.o irq_tables.o > gcc -nostdlib -r -o linuxbios_c.o c_start.o rom_fill_inbuf.o > linuxbios.a /usr/lib/gcc-lib/i586-suse-linux/3.3.1/libgcc.a > perl -e 'foreach $var (split(" ", $ENV{VARIABLES})) { if ($ENV{$var} =~ > m/^(0x[0-9a-fA-F]+|0[0-7]+|[0-9]+)$/) { print "$var = $ENV{$var};\n"; > }}' > ldoptions > gcc -nostdlib -nostartfiles -static -o linuxbios_c -T > /home/thomasle/freebios/src/config/linuxbios_c.ld linuxbios_c.o > linuxbios_c.o(.text+0xa56): In function `hardwaremain': > : undefined reference to `framebuffer_on' > collect2: ld returned 1 exit status > make: *** [linuxbios_c] Error 1 > > > Can anyone give me a hint please? What did I wrong? > > > Thx, Tom > > _______________________________________________ > Linuxbios mailing list > Linuxbios at clustermatic.org > http://www.clustermatic.org/mailman/listinfo/linuxbios From leidenfrost at corscience.de Mon Jul 19 08:20:01 2004 From: leidenfrost at corscience.de (Thomas Leidenfrost) Date: Mon Jul 19 08:20:01 2004 Subject: Compile Error while doing make In-Reply-To: <1090243336.25918.4.camel@buildserver1> References: <40FBBB05.3000700@corscience.de> <1090243336.25918.4.camel@buildserver1> Message-ID: <40FBD160.3050405@corscience.de> Hi, currently I'm using the AW-B651 from ICS, it is very similar to the PCM-5823, except the other superio-chip (Winbond M83977EF), I changed the Config-File according to this. Also I removed the option "HAVE_FRAMEBUFFER=1" for the second try, but the error-message was very similar to the previous one. ..cp linuxbios_payload.nrv2b linuxbios_payload echo "INCLUDE ldoptions" > ldscript.ld ; for file in /home/thomasle/freebios/src/arch/i386/config/ldscript.base /home/thomasle/freebios/src/cpu/i386/entry16.lds /home/thomasle/freebios/src/cpu/i386/entry32.lds /home/thomasle/freebios/src/cpu/i386/reset16.lds ; do echo "INCLUDE $file" >> ldscript.ld ; done gcc -nostdlib -nostartfiles -static -o linuxbios -T ldscript.ld crt0.o crt0.o(.rom.text+0x7e): In function `__protected_start': : undefined reference to `SERIAL_SUPERIO_BASEADDRESS' crt0.o(.rom.text+0x8f): In function `__protected_start': : undefined reference to `SERIAL_SUPERIO_BASEADDRESS' crt0.o(.rom.text+0xa0): In function `__protected_start': : undefined reference to `SERIAL_SUPERIO_BASEADDRESS' crt0.o(.rom.text+0xb1): In function `__protected_start': : undefined reference to `SERIAL_SUPERIO_BASEADDRESS' crt0.o(.rom.text+0xc2): In function `__protected_start': : undefined reference to `SERIAL_SUPERIO_BASEADDRESS' crt0.o(.rom.text+0xd3): more undefined references to `SERIAL_SUPERIO_BASEADDRESS' follow collect2: ld returned 1 exit status make: *** [linuxbios] Error 1 Anyway, thanks @David for your advice, but I'm an absolutely novice without any idea of your intention, neither was it pcituils nor where to get it or how to use it. So I think I want to make it work anyway and then comes the fine-tuning. Thx, Tom David Aubin wrote: > Hi Again, > > Just out of curiosity I poked around again and I don't think the > PCM-5823 has > support for the frame buffering. You could try VGA bios/testbios to get > your > card to initialize. You'll need pcituils to compile it, but it should > work. > > Dave > On Mon, 2004-07-19 at 08:13, Thomas Leidenfrost wrote: > >>Hello, >> >> >>after using the config-file from the Advantech PCM-5823 and adding the >>option "HAVE_FRAMEBUFFER=1" in the config-file I got this Errormessage: >>(kernelpath set to systemkernel 2.6.7) >> >>holodoc:/home/thomasle/Desktop/awb651 # make >>gcc -x assembler-with-cpp -DASSEMBLY -E ... crt0.S > crt0.s >>gcc ... -o crt0.o crt0.s >>crt0.S: Assembler messages: >>crt0.S:156: Warning: indirect jmp without `*' >>gcc ... -o version.o /home/thomasle/freebios/src/lib/version.c >>gcc ... -o mainboard.o >>/home/thomasle/freebios/src/mainboard/ics-d/awb651/mainboard.c >>gcc ... -o irq_tables.o >>/home/thomasle/freebios/src/mainboard/ics-d/awb651/irq_tables.c >>rm -f linuxbios.a >>ar cr linuxbios.a linuxbiosmain.o linuxpci.o newpci.o clog2.o printk.o >>serial_subr.o subr.o vsprintf.o memset.o memcpy.o memcmp.o malloc.o >>elfboot.o do_inflate.o delay.o compute_ip_checksum.o version.o >>keyboard.o mc146818rtc.o isa-dma.o ide.o boot.o linuxbios_table.o >>i386_subr.o params.o hardwaremain.o pirq_routing.o c_start.o cpuid.o >>delay_tsc.o northbridge.o southbridge.o superio_SMC_fdc37b72x.o >>nsuperio.o mainboard.o irq_tables.o >>gcc -nostdlib -r -o linuxbios_c.o c_start.o rom_fill_inbuf.o >>linuxbios.a /usr/lib/gcc-lib/i586-suse-linux/3.3.1/libgcc.a >>perl -e 'foreach $var (split(" ", $ENV{VARIABLES})) { if ($ENV{$var} =~ >>m/^(0x[0-9a-fA-F]+|0[0-7]+|[0-9]+)$/) { print "$var = $ENV{$var};\n"; >>}}' > ldoptions >>gcc -nostdlib -nostartfiles -static -o linuxbios_c -T >>/home/thomasle/freebios/src/config/linuxbios_c.ld linuxbios_c.o >>linuxbios_c.o(.text+0xa56): In function `hardwaremain': >>: undefined reference to `framebuffer_on' >>collect2: ld returned 1 exit status >>make: *** [linuxbios_c] Error 1 >> >> >>Can anyone give me a hint please? What did I wrong? >> >> >>Thx, Tom >> >>_______________________________________________ >>Linuxbios mailing list >>Linuxbios at clustermatic.org >>http://www.clustermatic.org/mailman/listinfo/linuxbios -- Thomas Leidenfrost Corscience GmbH & Co. KG Henkestra?e 91 91052 Erlangen Tel: +49-9131-97798635 Fax: +49-9131-97798659 leidenfrost at corscience.de From rsmith at bitworks.com Mon Jul 19 10:55:01 2004 From: rsmith at bitworks.com (Richard Smith) Date: Mon Jul 19 10:55:01 2004 Subject: Compile Error while doing make In-Reply-To: <40FBD160.3050405@corscience.de> References: <40FBBB05.3000700@corscience.de> <1090243336.25918.4.camel@buildserver1> <40FBD160.3050405@corscience.de> Message-ID: <40FBF685.1020802@bitworks.com> Thomas Leidenfrost wrote: > ..cp linuxbios_payload.nrv2b linuxbios_payload > echo "INCLUDE ldoptions" > ldscript.ld ; for file in > /home/thomasle/freebios/src/arch/i386/config/ldscript.base > /home/thomasle/freebios/src/cpu/i386/entry16.lds > /home/thomasle/freebios/src/cpu/i386/entry32.lds > /home/thomasle/freebios/src/cpu/i386/reset16.lds ; do echo "INCLUDE > $file" >> ldscript.ld ; done > gcc -nostdlib -nostartfiles -static -o linuxbios -T ldscript.ld crt0.o > crt0.o(.rom.text+0x7e): In function `__protected_start': > : undefined reference to `SERIAL_SUPERIO_BASEADDRESS' > crt0.o(.rom.text+0x8f): In function `__protected_start': > : undefined reference to `SERIAL_SUPERIO_BASEADDRESS' > crt0.o(.rom.text+0xa0): In function `__protected_start': > : undefined reference to `SERIAL_SUPERIO_BASEADDRESS' > crt0.o(.rom.text+0xb1): In function `__protected_start': > : undefined reference to `SERIAL_SUPERIO_BASEADDRESS' > crt0.o(.rom.text+0xc2): In function `__protected_start': > : undefined reference to `SERIAL_SUPERIO_BASEADDRESS' > crt0.o(.rom.text+0xd3): more undefined references to > `SERIAL_SUPERIO_BASEADDRESS' follow Looks like the boot up serial_setup is not right. crt0.s is built from files specified in your ./mainboard/Avantech/pcm-5823/Config the serial boot output stuff is built from this line. mainboardinit superio/SMC/fdc37b72x/setup_serial.inc Looking at the .inc for the advantech stuff and the config and some grepping I see that the superio base address is set with SMC_BASE in the pcm-5823 but set with SERIAL_SUPERIO_BASEADDRESS in the pcm-9574. What did you change this like to? Go look at whatever seteup_serial.inc you have and see what option it needs set for the serial base address. It may be as simple as adding a option SERIAL_SUPERIO_BASEADDRESS 0x to your mainboard config file or you may have to make some setup_serial.inc mods for whatever superio you changed to. From leidenfrost at corscience.de Mon Jul 19 13:12:01 2004 From: leidenfrost at corscience.de (Thomas Leidenfrost) Date: Mon Jul 19 13:12:01 2004 Subject: Compile Error while doing make In-Reply-To: <40FBF685.1020802@bitworks.com> References: <40FBBB05.3000700@corscience.de> <1090243336.25918.4.camel@buildserver1> <40FBD160.3050405@corscience.de> <40FBF685.1020802@bitworks.com> Message-ID: <40FC15DE.7000303@corscience.de> Now I am one step closer to the end, thanks for your patience and help! Probably not the last, but my actual problem: :-) ...dd if=linuxbios.strip of=linuxbios.rom bs=1 seek=`expr 65536 - $size` 65536 65536+0 Records ein 65536+0 Records aus objcopy -O binary -R .note -R .comment -S /boot/vmlinux linux.bin objcopy: /boot/vmlinux: File format not recognized make: *** [linux.bin] Error 1 I got a linuxbios.rom and a linuxbios.strip, both 64kB. But somehow, I think, the other 192kB of the Bios have to be filled with some kernel-sources. I read something about kernel 2.4.10 and a patch, but I can't find these instructions again. Then, if done, I think I have to put the linuxbios.rom & the linux.bin together with the tool nrv2b. Am I right? Thanks again, Tom P.S. @Richard: I added this to the config-file (didn't know it should be there): option SERIAL_SUPERIO_BASEADDRESS=0x3f0 Richard Smith wrote: > Thomas Leidenfrost wrote: > >> ..cp linuxbios_payload.nrv2b linuxbios_payload >> echo "INCLUDE ldoptions" > ldscript.ld ; for file in >> /home/thomasle/freebios/src/arch/i386/config/ldscript.base >> /home/thomasle/freebios/src/cpu/i386/entry16.lds >> /home/thomasle/freebios/src/cpu/i386/entry32.lds >> /home/thomasle/freebios/src/cpu/i386/reset16.lds ; do echo "INCLUDE >> $file" >> ldscript.ld ; done >> gcc -nostdlib -nostartfiles -static -o linuxbios -T ldscript.ld crt0.o >> crt0.o(.rom.text+0x7e): In function `__protected_start': >> : undefined reference to `SERIAL_SUPERIO_BASEADDRESS' >> crt0.o(.rom.text+0x8f): In function `__protected_start': >> : undefined reference to `SERIAL_SUPERIO_BASEADDRESS' >> crt0.o(.rom.text+0xa0): In function `__protected_start': >> : undefined reference to `SERIAL_SUPERIO_BASEADDRESS' >> crt0.o(.rom.text+0xb1): In function `__protected_start': >> : undefined reference to `SERIAL_SUPERIO_BASEADDRESS' >> crt0.o(.rom.text+0xc2): In function `__protected_start': >> : undefined reference to `SERIAL_SUPERIO_BASEADDRESS' >> crt0.o(.rom.text+0xd3): more undefined references to >> `SERIAL_SUPERIO_BASEADDRESS' follow > > > Looks like the boot up serial_setup is not right. crt0.s is built from > files specified in your ./mainboard/Avantech/pcm-5823/Config > > the serial boot output stuff is built from this line. > > mainboardinit superio/SMC/fdc37b72x/setup_serial.inc > > Looking at the .inc for the advantech stuff and the config and some > grepping I see that the superio base address is set with SMC_BASE in the > pcm-5823 but set with SERIAL_SUPERIO_BASEADDRESS in the pcm-9574. > > What did you change this like to? > > Go look at whatever seteup_serial.inc you have and see what option it > needs set for the serial base address. > > It may be as simple as adding a > > option SERIAL_SUPERIO_BASEADDRESS 0x > > to your mainboard config file or you may have to make some > setup_serial.inc mods for whatever superio you changed to. -- Thomas Leidenfrost Corscience GmbH & Co. KG Henkestra?e 91 91052 Erlangen Tel: +49-9131-97798635 Fax: +49-9131-97798659 leidenfrost at corscience.de From rsmith at bitworks.com Mon Jul 19 14:06:01 2004 From: rsmith at bitworks.com (Richard Smith) Date: Mon Jul 19 14:06:01 2004 Subject: Compile Error while doing make In-Reply-To: <40FC15DE.7000303@corscience.de> References: <40FBBB05.3000700@corscience.de> <1090243336.25918.4.camel@buildserver1> <40FBD160.3050405@corscience.de> <40FBF685.1020802@bitworks.com> <40FC15DE.7000303@corscience.de> Message-ID: <40FC234A.7090402@bitworks.com> Thomas Leidenfrost wrote: > Now I am one step closer to the end, thanks for your patience and help! > Probably not the last, but my actual problem: :-) > > ...dd if=linuxbios.strip of=linuxbios.rom bs=1 seek=`expr 65536 - $size` > 65536 > 65536+0 Records ein > 65536+0 Records aus > objcopy -O binary -R .note -R .comment -S /boot/vmlinux linux.bin > objcopy: /boot/vmlinux: File format not recognized > make: *** [linux.bin] Error 1 > > > I got a linuxbios.rom and a linuxbios.strip, both 64kB. But somehow, I > think, the other 192kB of the Bios have to be filled with some > kernel-sources. I read something about kernel 2.4.10 and a patch, but I > can't find these instructions again. Then, if done, I think I have to > put the linuxbios.rom & the linux.bin together with the tool nrv2b. Am I > right? Now you are getting out of my realm on this board. I've never used nrv2b. The error your getting above is because you have the default payload setup and it dosen't exist. If you don't specify a payload it defaults to linux. The actual linuxbios build is complete. You can take linuxbios.rom and put it in a chip. Only linuxbios will run though since you don't have a payload. > P.S. @Richard: I added this to the config-file (didn't know it should be > there): option SERIAL_SUPERIO_BASEADDRESS=0x3f0 Make sure you document up all the changes you had to make and funnel them back to the list so CVS can be updated and it works for the next guy. From bqs at mitre.org Mon Jul 19 14:44:00 2004 From: bqs at mitre.org (Bruce Q. Simmons) Date: Mon Jul 19 14:44:00 2004 Subject: NEWBIE Question Message-ID: <200407192016.i6JKGeZ06280@smtp-mclean.mitre.org> I am new at the LINUX Bios idea and need to figure out how I can tell if there is a solution for my system. Can someone point me in the right direction please? -Bruce Simmons -------------- next part -------------- An HTML attachment was scrubbed... URL: From rsmith at bitworks.com Mon Jul 19 14:57:00 2004 From: rsmith at bitworks.com (Richard Smith) Date: Mon Jul 19 14:57:00 2004 Subject: NEWBIE Question In-Reply-To: <200407192016.i6JKGeZ06280@smtp-mclean.mitre.org> References: <200407192016.i6JKGeZ06280@smtp-mclean.mitre.org> Message-ID: <40FC2F13.1060507@bitworks.com> Bruce Q. Simmons wrote: > I am new at the LINUX Bios idea and need to figure out how I can tell if > there is a solution for my system. Can someone point me in the right > direction please? > Boot linux on your ststem and send the output of lspci to the list so we know what chipset is on the system. From rminnich at lanl.gov Mon Jul 19 14:58:00 2004 From: rminnich at lanl.gov (ron minnich) Date: Mon Jul 19 14:58:00 2004 Subject: Compile Error while doing make In-Reply-To: <40FC15DE.7000303@corscience.de> Message-ID: sorry that LANL is going to be so quiet here, if you read wired.com you'll know how. I hope we can get back to helping out soon. ron From leidenfrost at corscience.de Mon Jul 19 15:00:00 2004 From: leidenfrost at corscience.de (Thomas Leidenfrost) Date: Mon Jul 19 15:00:00 2004 Subject: Compile Error while doing make In-Reply-To: <40FC234A.7090402@bitworks.com> References: <40FBBB05.3000700@corscience.de> <1090243336.25918.4.camel@buildserver1> <40FBD160.3050405@corscience.de> <40FBF685.1020802@bitworks.com> <40FC15DE.7000303@corscience.de> <40FC234A.7090402@bitworks.com> Message-ID: <40FC2F1F.2050005@corscience.de> >> objcopy -O binary -R .note -R .comment -S /boot/vmlinux linux.bin >> objcopy: /boot/vmlinux: File format not recognized >> make: *** [linux.bin] Error 1 >> > > The error your getting above is because you have the default payload > setup and it dosen't exist. If you don't specify a payload it defaults > to linux. The actual linuxbios build is complete. You can take > linuxbios.rom and put it in a chip. Only linuxbios will run though > since you don't have a payload. How do I specify a payload? I decompressed the sources of my actual running kernel (2.4.22) to /stuff2/Linuxe/kernel2422 and copied the current-used vmlinux into the same directory. But thats not all, I think... > Make sure you document up all the changes you had to make and funnel > them back to the list so CVS can be updated and it works for the next guy. I'll do after successful testing! :-) Greetz, Tom > _______________________________________________ > Linuxbios mailing list > Linuxbios at clustermatic.org > http://www.clustermatic.org/mailman/listinfo/linuxbios From daubin at actuality-systems.com Mon Jul 19 15:05:01 2004 From: daubin at actuality-systems.com (David Aubin) Date: Mon Jul 19 15:05:01 2004 Subject: NEWBIE Question In-Reply-To: <200407192016.i6JKGeZ06280@smtp-mclean.mitre.org> References: <200407192016.i6JKGeZ06280@smtp-mclean.mitre.org> Message-ID: <1090269343.5950.13.camel@buildserver1> 1. Check out http://cvs.sourceforge.net/viewcvs.py/freebios/ A. Look at the freebios2 target's area and see if your chipset is supported B. If your system is older check out the freebios/linuxbios area I'm having good luck with Tyan, so I personally might recommend them. Dave On Mon, 2004-07-19 at 16:16, Bruce Q. Simmons wrote: > I am new at the LINUX Bios idea and need to figure out how I can tell > if there is a solution for my system. Can someone point me in the > right direction please? > > -Bruce Simmons -------------- next part -------------- An HTML attachment was scrubbed... URL: From bqs at mitre.org Mon Jul 19 15:18:01 2004 From: bqs at mitre.org (Bruce Q. Simmons) Date: Mon Jul 19 15:18:01 2004 Subject: NEWBIE Question In-Reply-To: <40FC2F13.1060507@bitworks.com> Message-ID: <200407192050.i6JKoJZ03514@smtp-mclean.mitre.org> LSPCI results: Host bridge: Intel Corp. 440BX/ZX/DX - 82443BX/ZX/DX Host bridge (rev 01) PCI bridge: Intel Corp. 440BX/ZX/DX - 82443BX/ZX/DX AGP bridge (rev 01) ISA bridge: Intel Corp. 82371AB/EB/MB PIII4 ISA (rev 08) IDE interface: Intel Corp. 82371AB/EB/MB PIII4 IDE (rev 01) USB Controller: Intel Corp. 82371AB/EB/MB PIII4 USB Bridge: Intel Corp. 82371AB/EB/MB PIII4 ACPI (rev 08) How do I map this to the list of supported BIOS mainboards? -Bruce -----Original Message----- From: Richard Smith [mailto:rsmith at bitworks.com] Sent: Monday, July 19, 2004 4:29 PM To: bqs at mitre.org Cc: linuxbios at clustermatic.org Subject: Re: NEWBIE Question Bruce Q. Simmons wrote: > I am new at the LINUX Bios idea and need to figure out how I can tell if > there is a solution for my system. Can someone point me in the right > direction please? > Boot linux on your ststem and send the output of lspci to the list so we know what chipset is on the system. From daubin at actuality-systems.com Mon Jul 19 15:59:01 2004 From: daubin at actuality-systems.com (David Aubin) Date: Mon Jul 19 15:59:01 2004 Subject: NEWBIE Question In-Reply-To: <200407192050.i6JKoJZ03514@smtp-mclean.mitre.org> References: <200407192050.i6JKoJZ03514@smtp-mclean.mitre.org> Message-ID: <1090272606.5950.15.camel@buildserver1> I think you have this: http://cvs.sourceforge.net/viewcvs.py/freebios/freebios/src/mainboard/intel/l440bx On Mon, 2004-07-19 at 16:47, Bruce Q. Simmons wrote: > LSPCI results: > > Host bridge: Intel Corp. 440BX/ZX/DX - 82443BX/ZX/DX Host bridge (rev 01) > PCI bridge: Intel Corp. 440BX/ZX/DX - 82443BX/ZX/DX AGP bridge (rev 01) > ISA bridge: Intel Corp. 82371AB/EB/MB PIII4 ISA (rev 08) > IDE interface: Intel Corp. 82371AB/EB/MB PIII4 IDE (rev 01) > USB Controller: Intel Corp. 82371AB/EB/MB PIII4 USB > Bridge: Intel Corp. 82371AB/EB/MB PIII4 ACPI (rev 08) > > How do I map this to the list of supported BIOS mainboards? > > -Bruce > > -----Original Message----- > From: Richard Smith [mailto:rsmith at bitworks.com] > Sent: Monday, July 19, 2004 4:29 PM > To: bqs at mitre.org > Cc: linuxbios at clustermatic.org > Subject: Re: NEWBIE Question > > Bruce Q. Simmons wrote: > > > I am new at the LINUX Bios idea and need to figure out how I can tell if > > there is a solution for my system. Can someone point me in the right > > direction please? > > > > Boot linux on your ststem and send the output of lspci to the list so we > know what chipset is on the system. > > > > > > > > > _______________________________________________ > Linuxbios mailing list > Linuxbios at clustermatic.org > http://www.clustermatic.org/mailman/listinfo/linuxbios From rsmith at bitworks.com Mon Jul 19 16:05:00 2004 From: rsmith at bitworks.com (Richard Smith) Date: Mon Jul 19 16:05:00 2004 Subject: NEWBIE Question In-Reply-To: <200407192050.i6JKoJZ03514@smtp-mclean.mitre.org> References: <200407192050.i6JKoJZ03514@smtp-mclean.mitre.org> Message-ID: <40FC3F30.3010608@bitworks.com> Bruce Q. Simmons wrote: > LSPCI results: > > Host bridge: Intel Corp. 440BX/ZX/DX - 82443BX/ZX/DX Host bridge (rev 01) > PCI bridge: Intel Corp. 440BX/ZX/DX - 82443BX/ZX/DX AGP bridge (rev 01) > ISA bridge: Intel Corp. 82371AB/EB/MB PIII4 ISA (rev 08) > IDE interface: Intel Corp. 82371AB/EB/MB PIII4 IDE (rev 01) > USB Controller: Intel Corp. 82371AB/EB/MB PIII4 USB > Bridge: Intel Corp. 82371AB/EB/MB PIII4 ACPI (rev 08) > Looks like your are golden. Intel 440 is supported and I'm the maintianer. Yay! another 440?x user. I though I would be the only one. Do you know which ?X flavor you have. Whats the partnumber off the Northbridge? Who makes your board? The only testing all my code changes have had is with my 440BX but If the ZX and DX shouldn't be that much different. I tried to keep all my bitworks board specific changes out of the CVS setup but there may be a few that I couldn't abstract out without lots of changes but they all should wrapped with option BLAH=[10] enables From rsmith at bitworks.com Mon Jul 19 16:08:01 2004 From: rsmith at bitworks.com (Richard Smith) Date: Mon Jul 19 16:08:01 2004 Subject: NEWBIE Question In-Reply-To: <1090272606.5950.15.camel@buildserver1> References: <200407192050.i6JKoJZ03514@smtp-mclean.mitre.org> <1090272606.5950.15.camel@buildserver1> Message-ID: <40FC3FC8.1070102@bitworks.com> David Aubin wrote: > I think you have this: > http://cvs.sourceforge.net/viewcvs.py/freebios/freebios/src/mainboard/intel/l440bx Yes but he should start with mainboard/bitworks/ims as I've made lots of upgrades/fixes. From rsmith at bitworks.com Mon Jul 19 16:20:01 2004 From: rsmith at bitworks.com (Richard Smith) Date: Mon Jul 19 16:20:01 2004 Subject: NEWBIE Question In-Reply-To: <1090272606.5950.15.camel@buildserver1> References: <200407192050.i6JKoJZ03514@smtp-mclean.mitre.org> <1090272606.5950.15.camel@buildserver1> Message-ID: <40FC42B8.9050102@bitworks.com> David Aubin wrote: > I think you have this: > http://cvs.sourceforge.net/viewcvs.py/freebios/freebios/src/mainboard/intel/l440bx Yes but he should start with mainboard/bitworks/ims as I've made lots of upgrades/fixes. From jay.nelson at copansys.com Mon Jul 19 16:23:01 2004 From: jay.nelson at copansys.com (Jay Nelson) Date: Mon Jul 19 16:23:01 2004 Subject: Pentium-M with E7501 Chipset Implementation Message-ID: Hello, I am so pleased to find a freebios for Linux I'm beside myself. I have been researching freebios2 with the hope that I can use it for the following configuration: Intel Pentium-M (Dothan) 2MB L2 cache running at 1.8GHz Intel E7501 chipset: MCH P64H (82870P2) ICH3 (82801CA) Headless with RS232 mapped to a custom FPGA connected to the ICH3 PCI32 bus. It appears that the Tyan platform S2735 is the closest match to my configuration. The 82801CA is probably close enough to the 82801ER to work. Any hints/thoughts on this project would be appreciated. Thanks. Jay Nelson Principal Development Engineer -------------- next part -------------- An HTML attachment was scrubbed... URL: From leidenfrost at corscience.de Mon Jul 19 16:41:01 2004 From: leidenfrost at corscience.de (Thomas Leidenfrost) Date: Mon Jul 19 16:41:01 2004 Subject: Compile Error while doing make In-Reply-To: References: Message-ID: <40FC46C0.6090807@corscience.de> Furtunally I made it work somehow to have a payload! :-) (according to howto's e.g. from sis630) But now there are two new issues to be solved... The Linuxbios.rom is 64 kB, the Bioschip is 256 kB and the flashutility says: "File and ROM size mismatch" -> Do I need a new smaller Bios-ROM? Or is there another way making it work? And when using the payloader, which file is the right one? 1. romimage (1.4 MB) 2. payload.block (1.3 MB) 3. linux.bin.gz (1.2 MB) Thanks in advance for any hint. Yours, Tom (almost lucky) ron minnich wrote: > sorry that LANL is going to be so quiet here, if you read wired.com you'll > know how. I hope we can get back to helping out soon. > > ron > > _______________________________________________ > Linuxbios mailing list > Linuxbios at clustermatic.org > http://www.clustermatic.org/mailman/listinfo/linuxbios -- From YhLu at tyan.com Mon Jul 19 18:08:01 2004 From: YhLu at tyan.com (YhLu) Date: Mon Jul 19 18:08:01 2004 Subject: Pentium-M with E7501 Chipset Implementation Message-ID: <3174569B9743D511922F00A0C943142305A9EEE7@TYANWEB> You may need to copy 82801ER to 82801CA, and change device id to meet that with CA. Regards YH _____ From: Jay Nelson [mailto:jay.nelson at copansys.com] Sent: Monday, July 19, 2004 2:57 PM To: linuxbios at clustermatic.org Subject: Pentium-M with E7501 Chipset Implementation Hello, I am so pleased to find a freebios for Linux Im beside myself. I have been researching freebios2 with the hope that I can use it for the following configuration: Intel Pentium-M (Dothan) 2MB L2 cache running at 1.8GHz Intel E7501 chipset: MCH P64H (82870P2) ICH3 (82801CA) Headless with RS232 mapped to a custom FPGA connected to the ICH3 PCI32 bus. It appears that the Tyan platform S2735 is the closest match to my configuration. The 82801CA is probably close enough to the 82801ER to work. Any hints/thoughts on this project would be appreciated. Thanks. Jay Nelson Principal Development Engineer -------------- next part -------------- An HTML attachment was scrubbed... URL: From leidenfrost at corscience.de Tue Jul 20 04:28:01 2004 From: leidenfrost at corscience.de (Thomas Leidenfrost) Date: Tue Jul 20 04:28:01 2004 Subject: ROM-Size-Problem Message-ID: <40FCEC90.1050405@corscience.de> Hello list, here's my actual config-file, but somehow the resulting linuxbios.rom is only 64 kB instead of 256 kB, although setting: "option ROM_SIZE=262144" Filling the Linuxbios.rom to 256 kB with zeros (dd if=/dev/zero bs=1k count=192 >> linuxbios.rom) or with itself three more times (cat linuxbios.rom linuxbios.rom linuxbios.rom linuxbios.rom > bios256.rom) doesn't work, the monitor displays nothing (is framebuffer neccessary for that?!). So, how to make the generated linuxbios.rom will be 256 kB? Thx, Tom target testawb651 mainboard ics-d/awb651 # Enable Serial Console for debugging option SERIAL_CONSOLE=1 option TTYS0_BAUD=38400 option VIDEO_CONSOLE=1 option DEFAULT_CONSOLE_LOGLEVEL=9 option DEBUG=1 # option HAVE_FRAMEBUFFER=1 option USE_GENERIC_ROM=1 option USE_ELF_BOOT=1 option ROM_SIZE=262144 option STD_FLASH=1 linux /stuff2/Linuxe/kernel2422 commandline root=/dev/hda1 console=ttyS0,115200 FS_MODE=ro hda=flash From stepan at openbios.org Tue Jul 20 05:12:01 2004 From: stepan at openbios.org (Stefan Reinauer) Date: Tue Jul 20 05:12:01 2004 Subject: ROM-Size-Problem In-Reply-To: <40FCEC90.1050405@corscience.de> References: <40FCEC90.1050405@corscience.de> Message-ID: <20040720104436.GB4680@openbios.org> * Thomas Leidenfrost [040720 11:57]: > Filling the Linuxbios.rom to 256 kB with zeros (dd if=/dev/zero bs=1k > count=192 >> linuxbios.rom) or with itself three more times (cat > linuxbios.rom linuxbios.rom linuxbios.rom linuxbios.rom > bios256.rom) > doesn't work, the monitor displays nothing (is framebuffer neccessary > for that?!). So, how to make the generated linuxbios.rom will be 256 kB? Please try connecting a serial nullmodem cable and see if you get any output there. What graphics card does the system have? LinuxBIOS is unlikely to initialize your video correctly, except on a very small number of boards with onboard graphics (or with testbios) linuxbios.rom is only the linuxbios image without the payload it seems. I have in mind that V1 was not as solid with payload handling as V2 is, but I may be wrong.. > From leidenfrost at corscience.de Tue Jul 20 05:59:00 2004 From: leidenfrost at corscience.de (Thomas Leidenfrost) Date: Tue Jul 20 05:59:00 2004 Subject: ROM-Size-Problem In-Reply-To: <20040720104436.GB4680@openbios.org> References: <40FCEC90.1050405@corscience.de> <20040720104436.GB4680@openbios.org> Message-ID: <40FD01CA.80700@corscience.de> okay, I've got a nullmodem-cable here, but how can I see if there is any output? my graphics-controller is integrated in the Cx5530A-chipset. I think it should be supported, or am I wrong? Thx, Tom Stefan Reinauer wrote: > * Thomas Leidenfrost [040720 11:57]: > >>Filling the Linuxbios.rom to 256 kB with zeros (dd if=/dev/zero bs=1k >>count=192 >> linuxbios.rom) or with itself three more times (cat >>linuxbios.rom linuxbios.rom linuxbios.rom linuxbios.rom > bios256.rom) >>doesn't work, the monitor displays nothing (is framebuffer neccessary >>for that?!). So, how to make the generated linuxbios.rom will be 256 kB? > > > Please try connecting a serial nullmodem cable and see if you get any > output there. What graphics card does the system have? LinuxBIOS is > unlikely to initialize your video correctly, except on a very small > number of boards with onboard graphics (or with testbios) > > linuxbios.rom is only the linuxbios image without the payload it seems. > I have in mind that V1 was not as solid with payload handling as V2 is, > but I may be wrong.. > > > _______________________________________________ > Linuxbios mailing list > Linuxbios at clustermatic.org > http://www.clustermatic.org/mailman/listinfo/linuxbios From daubin at actuality-systems.com Tue Jul 20 07:28:01 2004 From: daubin at actuality-systems.com (David Aubin) Date: Tue Jul 20 07:28:01 2004 Subject: Compile Error while doing make In-Reply-To: <40FC46C0.6090807@corscience.de> References: <40FC46C0.6090807@corscience.de> Message-ID: <1090328369.24671.1.camel@buildserver1> Hi, Some flash utilities allow you to flash segments with beginning and ending offsets. Or what you could do is make 4 copies of your rom and write them, back to back to back to back:) Dave On Mon, 2004-07-19 at 18:10, Thomas Leidenfrost wrote: > Furtunally I made it work somehow to have a payload! :-) > (according to howto's e.g. from sis630) > > But now there are two new issues to be solved... > > The Linuxbios.rom is 64 kB, the Bioschip is 256 kB and the flashutility > says: "File and ROM size mismatch" -> Do I need a new smaller Bios-ROM? > Or is there another way making it work? > > > And when using the payloader, which file is the right one? > > 1. romimage (1.4 MB) > 2. payload.block (1.3 MB) > 3. linux.bin.gz (1.2 MB) > > > Thanks in advance for any hint. > > Yours, > Tom (almost lucky) > > > > ron minnich wrote: > > sorry that LANL is going to be so quiet here, if you read wired.com you'll > > know how. I hope we can get back to helping out soon. > > > > ron > > > > _______________________________________________ > > Linuxbios mailing list > > Linuxbios at clustermatic.org > > http://www.clustermatic.org/mailman/listinfo/linuxbios > -------------- next part -------------- An HTML attachment was scrubbed... URL: From rsmith at bitworks.com Tue Jul 20 09:54:01 2004 From: rsmith at bitworks.com (Richard Smith) Date: Tue Jul 20 09:54:01 2004 Subject: NEWBIE Question In-Reply-To: References: <200407192050.i6JKoJZ03514@smtp-mclean.mitre.org> <1090272606.5950.15.camel@buildserver1> <40FC42B8.9050102@bitworks.com> Message-ID: <40FD39A8.3070502@bitworks.com> Adam Hunt wrote: > I wasn't aware that the BX was supported. That's great. I have a > 440BX based board that I would like to try LinuxBIOS on. The board is > an ABIT BE6-II. I have included the output of lspci below. Do you > see any major obstacles in getting LB to run on my system? > > 0000:00:0b.0 FireWire (IEEE 1394): VIA Technologies, Inc. IEEE 1394 > Host Controller (rev 46) > 0000:00:13.0 Unknown mass storage controller: Triones Technologies, > Inc. HPT366/368/370/370A/372 (rev 03) As long as you don't want to boot from these devices you should be ok. > 0000:01:00.0 VGA compatible controller: 3Dfx Interactive, Inc. Voodoo 3 (rev 01) This may be a problem. None of the AGP registers in the Northbridge are set. Our board has onboard PCI video. A bitworks/ims manboard config should boot to a payload easy assuming you can program the flash. Is the flash part socketed? Also lspci dosen't show what SuperIO you have. What superIO is on the board? You will have to have that setup correctly to get serial output. From drwho8 at worldnet.att.net Tue Jul 20 10:03:01 2004 From: drwho8 at worldnet.att.net (Gregg C Levine) Date: Tue Jul 20 10:03:01 2004 Subject: NEWBIE Question References: <200407192050.i6JKoJZ03514@smtp-mclean.mitre.org> <1090272606.5950.15.camel@buildserver1> <40FC3FC8.1070102@bitworks.com> Message-ID: <000b01c46e6f$785cf640$6401a8c0@who5> Hello (again) from Gregg C Levine Nice discovery Bruce. I hope your project works out. Now my display of witt. Richard, Bruce, everyone go ahead and laugh, but the 440 chipset is one of my favorites. In fact the Del that I'm writing this on, happens to be a 440. Someday I'll swap the commercial thing for LinuxBIOS, never mind its really a Dell. Gregg C Levine drwho8 atsign worldnet dot att dot net "Oh my!" The Second Doctor's nearly favorite phrase. ----- Original Message ----- From: "Richard Smith" To: Cc: "Bruce Q. Simmons" ; Sent: Monday, July 19, 2004 5:40 PM Subject: Re: NEWBIE Question > David Aubin wrote: > > > I think you have this: > > http://cvs.sourceforge.net/viewcvs.py/freebios/freebios/src/mainboard/intel/l440bx > > Yes but he should start with mainboard/bitworks/ims as I've made lots of > upgrades/fixes. > > > _______________________________________________ > Linuxbios mailing list > Linuxbios at clustermatic.org > http://www.clustermatic.org/mailman/listinfo/linuxbios From rsmith at bitworks.com Tue Jul 20 10:12:01 2004 From: rsmith at bitworks.com (Richard Smith) Date: Tue Jul 20 10:12:01 2004 Subject: Compile Error while doing make In-Reply-To: <40FC46C0.6090807@corscience.de> References: <40FC46C0.6090807@corscience.de> Message-ID: <40FD3DED.8080008@bitworks.com> Thomas Leidenfrost wrote: > The Linuxbios.rom is 64 kB, the Bioschip is 256 kB and the flashutility > says: "File and ROM size mismatch" -> Do I need a new smaller Bios-ROM? > Or is there another way making it work? > well you could dd if=/dev/zero of=outimage.rom bs=1k count=256 dd if=Linuxbios.rom of=outimage.rom bs=1k seek=192 This will give you a 256kb Image with LB located in the last 64k. Also you can mess with option ROM_IMAGE_SIZE and option PAYLOAD_SIZE I set ROM_IMAGE_SIZE to Chip size - payload size. These control various parameters that are given to dd when it builds the imagefile. > And when using the payloader, which file is the right one? > > 1. romimage (1.4 MB) > 2. payload.block (1.3 MB) > 3. linux.bin.gz (1.2 MB) the 'payload' statement in the config file determines what payload file is used. From mcwhorter at mitre.org Tue Jul 20 13:56:01 2004 From: mcwhorter at mitre.org (Mike McWhorter) Date: Tue Jul 20 13:56:01 2004 Subject: A quick question... Message-ID: <40FD7269.9040107@mitre.org> I checked the LinuxBIOS status page to see if my motherboard is supported, but I found it to be a little confusing. I'm using an older Dell Optiplex and (based on the lspci output) I believe it uses the Intel 440BX chipset. Does anyone know if this board is supported? Thanks, - Mike knoppix at ttyp0[knoppix]$ lspci 0000:00:00.0 Host bridge: Intel Corp. 440BX/ZX/DX - 82443BX/ZX/DX Host bridge (rev 03) 0000:00:01.0 PCI bridge: Intel Corp. 440BX/ZX/DX - 82443BX/ZX/DX AGP bridge (rev 03) 0000:00:07.0 ISA bridge: Intel Corp. 82371AB/EB/MB PIIX4 ISA (rev 02) 0000:00:07.1 IDE interface: Intel Corp. 82371AB/EB/MB PIIX4 IDE (rev 01) 0000:00:07.2 USB Controller: Intel Corp. 82371AB/EB/MB PIIX4 USB (rev 01) 0000:00:07.3 Bridge: Intel Corp. 82371AB/EB/MB PIIX4 ACPI (rev 02) 0000:00:0e.0 Multimedia audio controller: Aureal Semiconductor Vortex 1 (rev 02) 0000:00:0f.0 PCI bridge: Digital Equipment Corporation DECchip 21152 (rev 03) 0000:00:11.0 Ethernet controller: 3Com Corporation 3c905B 100BaseTX [Cyclone] (rev 24) 0000:01:00.0 VGA compatible controller: ATI Technologies Inc 3D Rage Pro AGP 1X/2X (rev 5c) -------------- next part -------------- A non-text attachment was scrubbed... Name: smime.p7s Type: application/x-pkcs7-signature Size: 2923 bytes Desc: S/MIME Cryptographic Signature URL: From rsmith at bitworks.com Tue Jul 20 14:13:01 2004 From: rsmith at bitworks.com (Richard Smith) Date: Tue Jul 20 14:13:01 2004 Subject: NEWBIE Question In-Reply-To: <00a301c46e8c$a118f260$1efb1d80@simmonspc> References: <00a301c46e8c$a118f260$1efb1d80@simmonspc> Message-ID: <40FD7665.4030209@bitworks.com> Bruce Q. Simmons wrote: what do I need > to do next? > Bruce, I'm cc'ing the list so that others may benefit when they search through the list archives. I don't mind the direct mail but please cc the list for any LB related questions and such as there is a lot of stuff that I may not know the answer to or that someeone has a better answer for. First: You need to figure out how you are going to get LB onto your motherboard. You need to figure out what type of Flash part you have and how you are going to program it. Who makes your mainboard? Are there specs (or pictures) on-line I can go look at? What kind of IC programming tools to you have access to? Second: You need to figure out what SuperIO is on your motherboard and if LB supports it. The SuperIO is going to be responsible for the serial port output. If you don't have serial output. Debugging is going to be _much_ harder. SuperIO's are usually on the ISA bus so lspci isn't much help you have to look on the board and get a Mfg and a part number. If LB dosn't support you super IO it's not hard to add but you will need the SuperIO docs. From rsmith at bitworks.com Tue Jul 20 14:24:01 2004 From: rsmith at bitworks.com (Richard Smith) Date: Tue Jul 20 14:24:01 2004 Subject: A quick question... In-Reply-To: <40FD7269.9040107@mitre.org> References: <40FD7269.9040107@mitre.org> Message-ID: <40FD7903.3010408@bitworks.com> Mike McWhorter wrote: > I checked the LinuxBIOS status page to see if my motherboard is > supported, but I found it to be a little confusing. I'm using an older > Dell Optiplex and (based on the lspci output) I believe it uses the > Intel 440BX chipset. Does anyone know if this board is supported? Wow. You are the 3rd person in 2 days to ask about 440bx. A year of nothing and then pow. Things come in 3's I guess. Yes. 440bx is supported. Currently AGP may or may not work. The default routing of Legacy VGA stuff is controlled by a strap setting on the Nortbridge so its just possible that if the strap setting is right that AGP might be up enough for the emulator to bring up a card. Our board does not have AGP so I don't know if its setup right (if at all) Start with mainboard/bitworks/ims and go from there. Also see my next post on possible memory issues. From rsmith at bitworks.com Tue Jul 20 14:49:00 2004 From: rsmith at bitworks.com (Richard Smith) Date: Tue Jul 20 14:49:00 2004 Subject: 440bx possible RAM problems In-Reply-To: <000b01c46e6f$785cf640$6401a8c0@who5> References: <200407192050.i6JKoJZ03514@smtp-mclean.mitre.org> <1090272606.5950.15.camel@buildserver1> <40FC3FC8.1070102@bitworks.com> <000b01c46e6f$785cf640$6401a8c0@who5> Message-ID: <40FD7ED4.4030104@bitworks.com> I just realized a potential problem for you guys that are going to try LB on 440bx systems. The Bitworks IMS board useses a 66Mhz front side bus but the chipset can do 100Mhz. I suspect that most of these commercial mainboards will be useing 100Mhz. Pretty much all the memory settings in the northbridge are the default which I think are the 66Mhz settings. Only the stuff that is read out of the SPD is configured. At 100Mhz the settings for the Memory strength buffers are much toucher. (According to an Intel rep) so if your board runs with a FSB of 100Mhz RAM may not be reliable for you or may not work at all. Be sure to give it a good test with memtest. I don't know a lot about the memory strength settings but I'll try to help. I debugged the original memory setup by comparing config space dumps of a Comercial BIOS Northbridge settings vs what LB was doing. Before you flash in LB get a lspci -xxx of the north bridge settings with 'lspci -s 0 -xxx' so you can compare. Also the smbus controller is in the southbridge and thats what reads the SPD settings out of the RAM. So far all the lspci listings I have seen have the southbridge at Dev 07 which should work but if your southbridge shows up somewhere else then you will have to set the PIIX4_DEVFN option for memory SPD reading to work. This also assumes your mainboard Mfg hasn't done something flaky with the SMbus. From scheng at msica.com Tue Jul 20 19:23:00 2004 From: scheng at msica.com (Simon Xin Cheng) Date: Tue Jul 20 19:23:00 2004 Subject: ADLO: linuxbios v1 hangs after jumping to boot code at 0x7c00 In-Reply-To: <40F5DADB.1050708@bitworks.com> References: <61394.24.87.201.99.1089678627.squirrel@www.nome.ca> <62006.24.87.201.99.1089767059.squirrel@www.nome.ca> <40F48E81.9040408@bitworks.com> <60536.24.87.201.99.1089853618.squirrel@www.nome.ca> <40F5DADB.1050708@bitworks.com> Message-ID: <40FDBF06.40601@msica.com> Richard Smith wrote: > Simon Xin Cheng wrote: > >> Richard, >> >> Thanks for your suggestions. I tried them, however, the system still >> hangs >> when jumping to boot code at 0x7c00. >> >> Right now I suspect that something wrong with loder.s. My question is >> how >> to debug loader.s? Thanks again. > > > The most likely problem is that your shadowing is not working. > > Right after loader finishes copying to ram and you have enabled reads > to be routed to RAM dump the first few bytes from 0x7c00 and dump them > out the seial port and make sure things really got copied to RAM. > > > > > Richard, Thanks for your help on ADLO. I tried to trace loader.s, and have following problems: 1. Before sti jmp 0xFFFF:0x0000 I can print out something. But right after sti, I can not print out anything. So, I am not sure that the code really jumps to the power on entry point. 2. The first 16 bytes after 0xF0000 after shadowing are the same as rombios.bin. However, when I tried to print out more bytes, I can only get 16 output. What is the problem? My code is right after copy bios to 0xF0000: mov ax, #0x10 mov ds, ax mov eax, #0xF0000 mov esi, eax mov ecx, #0x30 ; loop counter mov dx, #0x3f8 ; serial port cld str_loop: lodsb out dx, al loop str_loop Thanks, Simon From alfafive at hotmail.ru Wed Jul 21 04:14:01 2004 From: alfafive at hotmail.ru (Doctor) Date: Wed Jul 21 04:14:01 2004 Subject: MB DFI CA61 Message-ID: <1877117647.20040721134631@hotmail.ru> Hello, linuxbios. I want to make my own bios for my MB DFI CA61 chipset is VIA82C693 Can I make it by myself, if you have knowledge to start it more easy, please, send a message... 00:00.0 Host bridge: VIA Technologies, Inc. VT82C693A/694x [Apollo PRO133x] (rev 44) 00:01.0 PCI bridge: VIA Technologies, Inc. VT82C598/694x [Apollo MVP3/Pro133x AGP] 00:07.0 ISA bridge: VIA Technologies, Inc. VT82C596 ISA [Mobile South] (rev 22) 00:07.1 IDE interface: VIA Technologies, Inc. VT82C586/B/686A/B PIPC Bus Master IDE (rev10) 00:07.2 USB Controller: VIA Technologies, Inc. USB (rev 11) 00:07.3 Host bridge: VIA Technologies, Inc. VT82C596 Power Management (rev 30) 00:09.0 Multimedia audio controller: Ensoniq ES1371 [AudioPCI-97] (rev 08) 00:0b.0 VGA compatible controller: S3 Inc. ViRGE/DX or /GX (rev 01) 00:0d.0 Ethernet controller: Realtek Semiconductor Co., Ltd. RTL-8139/8139C/8139C+ (rev 10) 01:00.0 VGA compatible controller: nVidia Corporation NV5 [Riva TnT2] (rev 11) -- Arno mailto:alfafive at hotmail.ru From zhushisongzhu at yahoo.com Wed Jul 21 08:04:00 2004 From: zhushisongzhu at yahoo.com (zhu shi song) Date: Wed Jul 21 08:04:00 2004 Subject: trouble with SDRAM when using sis630 SDRAM synchronous mode Message-ID: <20040721133659.88502.qmail@web13201.mail.yahoo.com> (1) ECS P6stmt board use SDRAM synchronous mode. I've got P6STMT motherboard based on sis630et. It's strange that the 0x8e is equal 0 which I have read from linux running on the board, that means the board uses SDRAM synchronous mode. (2) The board halt after setting 0x8c~8f value same as bios setting. I set 0x8c~8f (in dll.inc) values to which I have read under linux. But ipl can't copy linuxbios from Doc to RAM. I have tested doc_mil.inc. When the second "call doc_reset" that is the second time to use RAM stack(%ss=$0x400, %sp=$0x0), the board halt. (3) winfast 6300 Max board use SDRAM asynchronous mode. I have read 0x8c~8f values of winfast 6300. The value of 0x8e is 0x3. So winfast6300 use SDRAM asynchronous mode. IPL can boot linuxbios and linux successfully. (4)under p6stmt Even I set register 0x50~0x5A (except 0x52 and 0x57) value to what I have read from its bios. IPL can't copy linuxbios to RAM either. Who has met the same experience? I need help. zhu --------------------------------- Do you Yahoo!? Vote for the stars of Yahoo!'s next ad campaign! -------------- next part -------------- An HTML attachment was scrubbed... URL: From rsmith at bitworks.com Wed Jul 21 10:06:00 2004 From: rsmith at bitworks.com (Richard Smith) Date: Wed Jul 21 10:06:00 2004 Subject: ADLO: linuxbios v1 hangs after jumping to boot code at 0x7c00 In-Reply-To: <40FDBF06.40601@msica.com> References: <61394.24.87.201.99.1089678627.squirrel@www.nome.ca> <62006.24.87.201.99.1089767059.squirrel@www.nome.ca> <40F48E81.9040408@bitworks.com> <60536.24.87.201.99.1089853618.squirrel@www.nome.ca> <40F5DADB.1050708@bitworks.com> <40FDBF06.40601@msica.com> Message-ID: <40FE8E00.8070207@bitworks.com> Simon Xin Cheng wrote: > rombios.bin. However, when I tried to print out more bytes, I can only > get 16 output. What is the problem? My code is right after copy bios to > 0xF0000: > > mov ax, #0x10 > mov ds, ax > mov eax, #0xF0000 > mov esi, eax > > mov ecx, #0x30 ; loop counter > mov dx, #0x3f8 ; serial port > > cld > str_loop: lodsb > out dx, al > loop str_loop > Thats because you have forgotten that the CPU runs several orders of magnitude faster than the serial port. You only get 16 bytes because the 16550 UART FIFO is only 16 bytes deep. After that your bytes are going to the bit bucket. You have to wait until the busy flag of the 16550 is clear after you write each byte. See the a data sheet on the UART. From zhushisongzhu at yahoo.com Thu Jul 22 01:44:01 2004 From: zhushisongzhu at yahoo.com (zhu shi song) Date: Thu Jul 22 01:44:01 2004 Subject: Sis 630 memory init Message-ID: <20040722071651.97033.qmail@web13204.mail.yahoo.com> I have met two problems when using V1 linuxbios for winfast 6300. (1) For winfast 6300, it is not compatible with some SDRAM. (2) For ECS P6STMT board which uses sis630et chipset, IPL hangs when ipl use stack to read Linuxbios from DOC. The two problems are all related to memory init. Maybe the current memory init procedures in freebios V1 is not complete. Who know how to init SDRAM correctly, so it can work for more SDRAM and more boards? zhu --------------------------------- Do you Yahoo!? New and Improved Yahoo! Mail - 100MB free storage! -------------- next part -------------- An HTML attachment was scrubbed... URL: From casper at meteor.dp.ua Thu Jul 22 08:06:01 2004 From: casper at meteor.dp.ua (Friendly Ghost) Date: Thu Jul 22 08:06:01 2004 Subject: Newbie In-Reply-To: =?iso-8859-1?Q?=3C20040722071651=2E97033?= =?iso-8859-1?Q?=2Eqmail=40web13204=2Email=2Eyahoo=2Ecom=3E=3B_from_zhushi?= =?iso-8859-1?B?c29uZ3podUB5YWhvby5jb20gb24g/tTXLCDpwA==?= =?iso-8859-1?Q?=CC?= 22, 2004 at 10:16:51 +0300 References: <20040722071651.97033.qmail@web13204.mail.yahoo.com> Message-ID: <20040722162905.G4397@casper.meteor.my.net> Hello, My name is Kostik I'm new to this and I'm interested in this project. I please tell me if the project is still alive. I ask because the source code is dated 2001. An other question: how much memory is in Award's bios chip? Best regards, Kostik. From pyro at linuxlabs.com Thu Jul 22 09:18:00 2004 From: pyro at linuxlabs.com (Steven James) Date: Thu Jul 22 09:18:00 2004 Subject: Newbie In-Reply-To: <20040722162905.G4397@casper.meteor.my.net> References: <20040722071651.97033.qmail@web13204.mail.yahoo.com> <20040722162905.G4397@casper.meteor.my.net> Message-ID: Greetings, The projuect is very much alive. The source drops are quite out of date. You will want to use CVS. G'day, sjames -------------------------steven james, director of research, linux labs ... ........ ..... .... 230 peachtree st nw ste 2701 the original linux labs atlanta.ga.us 30303 -since 1995 http://www.linuxlabs.com office & fax 866.545.6306 ----------------------------------------------------------------------- On Thu, 22 Jul 2004, Friendly Ghost wrote: > Hello, > > My name is Kostik I'm new to this and I'm interested in this project. > > I please tell me if the project is still alive. I ask because the > source code is dated 2001. > > An other question: how much memory is in Award's bios chip? > > Best regards, > Kostik. > _______________________________________________ > Linuxbios mailing list > Linuxbios at clustermatic.org > http://www.clustermatic.org/mailman/listinfo/linuxbios > From tomfritz at direcpc.com Thu Jul 22 15:01:01 2004 From: tomfritz at direcpc.com (Thomas Fritz) Date: Thu Jul 22 15:01:01 2004 Subject: Was a newbie, now a polliwog In-Reply-To: <20040722160001.3725.41492.Mailman@nwn.definitive.org> References: <20040722160001.3725.41492.Mailman@nwn.definitive.org> Message-ID: <41002338.80902@direcpc.com> I became interested in linuxbios a while back, and while I've subscribed to this list I've never done anything with it. I've learned quite a bit more since then, and I'm even working on reading the Linux From Scatch book. I've come back around to it again, for two reasons...I have a working laptop (IBM TP 390X), and an extra mainboard for the laptop. I have to do a password recovery on mainboard, but I was thinking if I'm going to go through the trouble, I would like to try something with it. Especially with the TSSOP flash bios chip within easy reach :) The other reason...I've been looking at embedded applications lately, and I don't really feel like going the DIY hardware route...since I have access to a surplus source of IBM thin clients (403GCX PPC, PC87303 SuperIO, S3 Trio64V+ video, single PCMCIA slot, two EDO SIMM slots, parport, serial, mouse/keybd, DP83907 ATLANTIC II ethernet, and a whopping 512KB AM29F040 flash bios), which have everything I could want, except USB, which a PCMCIA card could fix. What I want to do with one of the thin clients is put on linuxbios, and since I would be using the PCMCIA for USB, boot a compact system off of a USB memory stick. I was wondering how far along things have come, and if anyone has done something like the USB booting, or even what other devices linuxbios can boot a system off of? Also, after reading about all that's been done with the X-box project, and the mod chips they sell, I was wondering if anyone has had any thoughts on something like the Xenium X-box mod chip? From dwh at lanl.gov Thu Jul 22 15:28:01 2004 From: dwh at lanl.gov (Hendricks David W.) Date: Thu Jul 22 15:28:01 2004 Subject: Was a newbie, now a polliwog In-Reply-To: <41002338.80902@direcpc.com> Message-ID: I figure now might be a good time to remind readers that LANL personnel (Ron Minnich, Ollie Lho, Greg Watson, and myself) on this list are currently unable to respond to inquiries on this mailing list due to a lab-wide stand down. You can read more about it here: http://www.lamonitor.com/articles/2004/07/19/headline_news/news08.txt We try to be responsive and helpful, but this is impossible for now and the immediate future. Fortunately there are several other helpful readers on this mailing list who can help. I just don't want anyone thinking that the LANL guys are blowing this list off or anything like that (Especially since the recent Slashdot article might spur some more interest in this project). On Thu, 22 Jul 2004, Thomas Fritz wrote: > I became interested in linuxbios a while back, and while I've subscribed > to this list I've never done anything with it. > > I've learned quite a bit more since then, and I'm even working on > reading the Linux From Scatch book. > > I've come back around to it again, for two reasons...I have a working > laptop (IBM TP 390X), and an extra mainboard for the laptop. I have to > do a password recovery on mainboard, but I was thinking if I'm going to > go through the trouble, I would like to try something with it. > Especially with the TSSOP flash bios chip within easy reach :) > > The other reason...I've been looking at embedded applications lately, > and I don't really feel like going the DIY hardware route...since I have > access to a surplus source of IBM thin clients (403GCX PPC, PC87303 > SuperIO, S3 Trio64V+ video, single PCMCIA slot, two EDO SIMM slots, > parport, serial, mouse/keybd, DP83907 ATLANTIC II ethernet, and a > whopping 512KB AM29F040 flash bios), which have everything I could want, > except USB, which a PCMCIA card could fix. > > What I want to do with one of the thin clients is put on linuxbios, and > since I would be using the PCMCIA for USB, boot a compact system off of > a USB memory stick. > > I was wondering how far along things have come, and if anyone has done > something like the USB booting, or even what other devices linuxbios can > boot a system off of? > > > > Also, after reading about all that's been done with the X-box project, > and the mod chips they sell, I was wondering if anyone has had any > thoughts on something like the Xenium X-box mod chip? > _______________________________________________ > Linuxbios mailing list > Linuxbios at clustermatic.org > http://www.clustermatic.org/mailman/listinfo/linuxbios > From rsmith at bitworks.com Thu Jul 22 16:17:00 2004 From: rsmith at bitworks.com (Richard Smith) Date: Thu Jul 22 16:17:00 2004 Subject: Was a newbie, now a polliwog In-Reply-To: <41002338.80902@direcpc.com> References: <20040722160001.3725.41492.Mailman@nwn.definitive.org> <41002338.80902@direcpc.com> Message-ID: <4100368D.8070106@bitworks.com> Thomas Fritz wrote: > What I want to do with one of the thin clients is put on linuxbios, and > since I would be using the PCMCIA for USB, boot a compact system off of > a USB memory stick. The PCMCIA is a problem. PCMCIA cardservices is a big beast. Linuxbios dosen't currently do PCMCIA. I created a setup with one of our boards that net booted via a PCMCIA wireless card. To make that happen I had to boot a linux kernel and then kexec into my netbooted image. At that time kernel cardservices would not do our wifi card and I had to use pcmcia-cs. Compiling a only the necessary programs from pcmcia-cs against uclibc I was able to get a kernel+initrd down to just less than a meg. Our board has 2 29F040b's on it (designed with this in mind) so I got it all on board. Took work though. If you use 2.6.x and the set of tiny patches that allows you rips out most of the features that make it large you _might_ get down to less 512k Probally going to be tight though. This route has be talked about but I don't think anyone has ever seen how small you can get 2.6.x with the tiny1 patches. Eric B. mentioned that he was going to play with this someday but I don't know if he ever did. Here's the link for the tiny1 tree. Give it a whirl and report back what you find. Using Linux as the bootloader is the holy grail of linuxbios booting. http://www.selenic.com/tiny-about/ From love at ccpu.com Thu Jul 22 18:00:01 2004 From: love at ccpu.com (Chris Love) Date: Thu Jul 22 18:00:01 2004 Subject: Starting point for a SuperIO port (SMC LPC47B272) Message-ID: <41004EC3.3060805@ccpu.com> I am trying to bring up LinuxBIOS on an x86 CPCI blade here. Output from lspci is included below. The one item I've noticed so far is that the SuperIO device doesn't appear to be supported in either source tree. The northbridge, southbridge, and BIOS flash device (82802AC) appear to be supported in the freebios tree. Has anyone dealt with this SuperIO device before? Are any of the other SMC superio drivers a good or bad starting point for a port? My first step is probably going to be comparing datasheets between this and some of the other devices, but other suggestions would be welcome. Thanks in advance, Chris 00:00.0 Host bridge: Intel Corp.: Unknown device 254c (rev 01) 00:02.0 PCI bridge: Intel Corp. e7500 [Plumas] HI_B Virtual PCI Bridge (F0) (rev 01) 00:1d.0 USB Controller: Intel Corp. 82801CA/CAM USB (Hub #1) (rev 02) 00:1e.0 PCI bridge: Intel Corp. 82801BA/CA/DB PCI Bridge (rev 42) 00:1f.0 ISA bridge: Intel Corp. 82801CA ISA Bridge (LPC) (rev 02) 00:1f.1 IDE interface: Intel Corp. 82801CA IDE U100 (rev 02) 00:1f.3 SMBus: Intel Corp. 82801CA/CAM SMBus (rev 02) 01:01.0 SCSI storage controller: LSI Logic / Symbios Logic 53c896 (rev 07) 01:01.1 SCSI storage controller: LSI Logic / Symbios Logic 53c896 (rev 07) 01:02.0 Ethernet controller: Intel Corp. 82559ER (rev 09) 01:03.0 Ethernet controller: Intel Corp. 82559ER (rev 09) 01:05.0 Serial controller: Exar Corp.: Unknown device 0154 (rev 03) 01:08.0 Ethernet controller: Intel Corp. 82801CAM (ICH3) PRO/100 VE (LOM) Ethernet Controller (rev 42) 02:1c.0 PIC: Intel Corp. 82870P2 P64H2 I/OxAPIC (rev 04) 02:1d.0 PCI bridge: Intel Corp. 82870P2 P64H2 Hub PCI Bridge (rev 04) 02:1e.0 PIC: Intel Corp. 82870P2 P64H2 I/OxAPIC (rev 04) 02:1f.0 PCI bridge: Intel Corp. 82870P2 P64H2 Hub PCI Bridge (rev 04) 03:01.0 PCI bridge: Intel Corp. 21154 PCI-to-PCI Bridge 03:02.0 VGA compatible controller: Silicon Motion, Inc. SM710 LynxEM (rev a3) 05:01.0 Ethernet controller: Intel Corp. 82546EB Gigabit Ethernet Controller (Copper) (rev 01) 05:01.1 Ethernet controller: Intel Corp. 82546EB Gigabit Ethernet Controller (Copper) (rev 01) -- Chris Love // Continuous Computing Corporation love at ccpu.com // http://www.ccpu.com From joey at joescan.com Thu Jul 22 19:19:01 2004 From: joey at joescan.com (Joey Nelson) Date: Thu Jul 22 19:19:01 2004 Subject: Change in flash chip kills my linuxbios. In-Reply-To: <40FD7903.3010408@bitworks.com> Message-ID: <200407222318.i6MNIMK05348@nwn.definitive.org> I've had linux bios running on a Fabiatech FB2510 for some time. The most recent batch of boards have switched from an SST 39SF020A flash, to a Winbond W29C020C. Both are 265Kx8 flash roms. My image no longer works with the Winbond. I've tested with an old SST flash on the new boards and everything works smashing. But with the Winbond I get nothing; no serial output or anything. I've verified that the images are identical using a chip programmer. Any ideas on what might cause this? Any easy fixes? Thanks, Joey Nelson From rsmith at bitworks.com Fri Jul 23 09:36:01 2004 From: rsmith at bitworks.com (Richard Smith) Date: Fri Jul 23 09:36:01 2004 Subject: Sis 630 memory init In-Reply-To: <20040723090310.38600.qmail@web13206.mail.yahoo.com> References: <20040723090310.38600.qmail@web13206.mail.yahoo.com> Message-ID: <41012A34.9010304@bitworks.com> zhu shi song wrote: > Where is work placed? Can you kindly send me for reference? > Look in northbridge/intel/440bx/raminit.inc > I have checked the value of (sdram type, row, col, bank ,side ) through post code(output to 0x80 port). They are all correct values. But I still can't use SDRAM on ECS P6STMT board. > Do you know what errors of original code have been corrected after using the new code? > tks If I remember correctly the page size and the ram boundrys were not being set correctly. The orginal RAM routines tried to set all the registers in one big loop so it was really hard to debug. I switced to the newer code since it did things one step at a time and would be easier to debug. Switching had the side-effect of making things work so I didn't bother totaly figureing out what was wrong with the orginal code. From rsmith at bitworks.com Fri Jul 23 09:43:02 2004 From: rsmith at bitworks.com (Richard Smith) Date: Fri Jul 23 09:43:02 2004 Subject: Sis 630 memory init In-Reply-To: <20040723090310.38600.qmail@web13206.mail.yahoo.com> References: <20040723090310.38600.qmail@web13206.mail.yahoo.com> Message-ID: <41012AAF.1080003@bitworks.com> zhu shi song wrote: > Do you know what errors of original code have been corrected after using the new code? My suggestion would be to dump the northbridge of a BIOS that works correctly and compare it to what LinuxBios does. The go consult the data sheet on each difference. From rsmith at bitworks.com Fri Jul 23 10:09:01 2004 From: rsmith at bitworks.com (Richard Smith) Date: Fri Jul 23 10:09:01 2004 Subject: Change in flash chip kills my linuxbios. In-Reply-To: <200407222318.i6MNIMK05348@nwn.definitive.org> References: <200407222318.i6MNIMK05348@nwn.definitive.org> Message-ID: <410131EE.9050208@bitworks.com> Joey Nelson wrote: > > I've verified that the images are identical using a chip programmer. > > Any ideas on what might cause this? Any easy fixes? Subtle timeing problems? Whats the speed rating of both parts? How many address lines does the board really use? Its possible that if some of the address lines were floating that it might work with one part but not the other. How big is your LB image. Try makeing mutiple copies of the image in the rom. Then it won't matter if the upper address lines float the wrong way. From jmiller at actuality-systems.com Fri Jul 23 15:11:01 2004 From: jmiller at actuality-systems.com (Jay Miller) Date: Fri Jul 23 15:11:01 2004 Subject: AMD 8111 GPIO Message-ID: We've got Linux up and running on our Tyan S2885 motherboards, using etherboot and filo with USB support. Thanks for all your help, and patience! I was hoping that with all the expertise here with AMD 8111 chipset, that someone would be able to answer my question. Although it's not strictly LinuxBIOS, it is Linux. ;-) So I'm trying to write a Linux driver for the GPIO pins on the AMD 8111. I saw a comment in amd8111_smbus.c that PMIOEN is set. I believe this is part of what I need to be able to drive the GPIOs. But how/where were all those hex values determined? The spec uses mnemonics to abstract the addresses, and I don't see how they correlate. Thanks, Jay Miller 781-229-7812x117 Actuality Systems, Inc. jmiller at acutality-systems.com From scheng at msica.com Fri Jul 23 18:57:00 2004 From: scheng at msica.com (Simon Xin Cheng) Date: Fri Jul 23 18:57:00 2004 Subject: ADLO: no serial output after sti in loader.s In-Reply-To: <40FE8E00.8070207@bitworks.com> References: <61394.24.87.201.99.1089678627.squirrel@www.nome.ca> <62006.24.87.201.99.1089767059.squirrel@www.nome.ca> <40F48E81.9040408@bitworks.com> <60536.24.87.201.99.1089853618.squirrel@www.nome.ca> <40F5DADB.1050708@bitworks.com> <40FDBF06.40601@msica.com> <40FE8E00.8070207@bitworks.com> Message-ID: <4101ADBD.80208@msica.com> Hi, I am working on booting Linux from hard disk with VGA support on an EPIA board. I am using ADLO to load video bios and bochs bios. I found an interesting thing. The last two instructions in the loader.s of ADLO is : sti jmp 0xFFFF:0x0000 I turned DEBUG_SERIAL on in rombios.c. But I can not see any debugging information through serial port after the jumping. However, if I commented out the sti, I can see all debugging information. So what is the problem with the sti? Are there any LinuxBIOS interrupt service routines that never return back? Simon From zhushisongzhu at yahoo.com Sun Jul 25 04:36:00 2004 From: zhushisongzhu at yahoo.com (zhu shi song) Date: Sun Jul 25 04:36:00 2004 Subject: sis630et memory init problem Message-ID: <20040725100931.15317.qmail@web13204.mail.yahoo.com> Hi, lists, I've got one ECS p6stmt motherboard based on sis630et. I have dumped pci host bridge settings: P6STMT 00:00.0 Host bridge: Silicon Integrated Systems: Unknown device 0630 (rev 30) 00: 39 10 30 06 07 00 10 22 30 00 00 06 00 20 80 00 10: 00 00 00 d8 00 00 00 00 00 00 00 00 00 00 00 00 20: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 30: 00 00 00 00 c0 00 00 00 00 00 00 00 00 00 00 00 40: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 50: 9e 00 c5 00 00 19 00 01 00 15 51 00 00 00 00 00 60: 0b 00 00 a1 00 00 00 00 01 50 c6 00 e0 00 00 00 70: 3f 90 00 00 00 00 00 00 00 00 00 00 00 00 00 00 80: 20 ff 7f 1f 60 00 03 40 00 08 00 00 78 88 00 55 90: 00 00 00 00 40 00 00 01 00 00 00 00 02 00 00 00 a0: 00 00 03 01 aa 00 00 00 00 00 00 00 00 00 f8 00 b0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 c0: 02 00 20 00 07 02 00 1f 04 00 00 00 00 00 00 00 d0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 e0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 f0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 SPD dump: Memory Type 0x04 Number of Row Address bits 0x0d Number of Column Address bits 0x0a Number of Sides 0x01 Number of Banks 0x04 I try to set the values just as the same as bios settings. But when ipl use stack, it hangs on copying linuxbios from DOC. It's obvious that memory init failed. I noticed that 0x8e is 0, It's very different with winfast6300's. winfast6300 0x8e is 03. What's the problem behind it? tks zhu --------------------------------- Do you Yahoo!? Yahoo! Mail is new and improved - Check it out! -------------- next part -------------- An HTML attachment was scrubbed... URL: From marc at geekythings.com Sun Jul 25 15:07:00 2004 From: marc at geekythings.com (Marc Nicholas) Date: Sun Jul 25 15:07:00 2004 Subject: Is LinuxBIOS still alive? Message-ID: Hello... I used to be on the LinuxBIOS list a few years back...the website seems a little dry on information these days -- is LB still alive and kicking? I'm specifically interested in getting things working with VIA Mini-ITX boards, namely the M and MII. -marc From Antony at Soft-Solutions.co.uk Sun Jul 25 15:25:00 2004 From: Antony at Soft-Solutions.co.uk (Antony Stone) Date: Sun Jul 25 15:25:00 2004 Subject: Is LinuxBIOS still alive? In-Reply-To: References: Message-ID: <200407252158.48843.Antony@Soft-Solutions.co.uk> On Sunday 25 July 2004 9:39 pm, Marc Nicholas wrote: > Hello... > > I used to be on the LinuxBIOS list a few years back...the website seems a > little dry on information these days -- is LB still alive and kicking? Very much so. Try checking out the CVS. > I'm specifically interested in getting things working with VIA Mini-ITX > boards, namely the M and MII. I'm pretty sure people here have had success with those. Regards, Antony. -- Abandon hope, all ye who enter here. You'll feel much better about things once you do. Please reply to the list; please don't CC me. From rsmith at bitworks.com Sun Jul 25 22:23:00 2004 From: rsmith at bitworks.com (Richard Smith) Date: Sun Jul 25 22:23:00 2004 Subject: Was a newbie, now a polliwog In-Reply-To: <41047751.8090002@direcpc.com> References: <20040722160001.3725.41492.Mailman@nwn.definitive.org> <41002338.80902@direcpc.com> <4100368D.8070106@bitworks.com> <41047751.8090002@direcpc.com> Message-ID: <4104810C.8020507@bitworks.com> Thomas Fritz wrote: > There's a PDF file on the tiny-linux site, which has a descriptions of > results - with a 2.6 kernel with more features than I'd need, the writer > says that he got it as small as a compressed 363K image, and a user > reported a compressed image as small as 191K. Thats very encouraging. I wonder what was enabled in the 191Kib version. 191+64 is just enough for those people with 256Kib flashes. > This is all very interesting, but while I have 512K to work in right > now, I have no idea how much space linuxbios needs. Also, keep in mind > I'm going to be trying to cross-compile for the PowerPC...does the same > code need more bytes or fewer bytes? In my current LB1 setup that does not netboot: LB = 60Kib ADLO = 136Kib By the time they run through the script the whole thing ends up being 228Kib but I have my settings so that the smallest alignment is like 64k or so. I don't remember exactly so I've got wasted space. I have no idea how the PPC code compares to x86. I've cc: this to the list perhaps some PPC person can comment. I think V2 is much larger due to the use of romcc but I don't have any hard info on that as I haven't made the jump yet. From vbarbarin at ifrance.com Mon Jul 26 03:46:01 2004 From: vbarbarin at ifrance.com (Vincent BARBARIN) Date: Mon Jul 26 03:46:01 2004 Subject: [NEWBIE question] LinuxBIOS & IEEE 1394 Message-ID: <4104CE05.2020008@ifrance.com> Hi, here's a new one there, tired of those "Boot from ".... options that are not so available on those PCs... I'd like to know if there's any project going on to put in LinuxBIOS Int 13 support for IEEE 1394 drives (why not USB too ? motherboard integrated or not) Any link with linux1394.org ? Just for making any OS boot loader running from any drive... pleeeeeeeeeese ? From nick.jarmany at densitron.co.uk Mon Jul 26 05:49:00 2004 From: nick.jarmany at densitron.co.uk (Nick Jarmany) Date: Mon Jul 26 05:49:00 2004 Subject: sis630et memory init problem Message-ID: Zhu, On SiS630ET x8Eh has two active bits:- Bit 0: SDRAM synchronous mode. 0=Enable, 1=Disable Bit 1:Relationship between CPU & SDRAM clocks. 0=CPU>SDRAM, 1=CPU it out! -------------- next part -------------- An HTML attachment was scrubbed... URL: From zhushisongzhu at yahoo.com Mon Jul 26 06:49:01 2004 From: zhushisongzhu at yahoo.com (zhu shi song) Date: Mon Jul 26 06:49:01 2004 Subject: sis630et memory init problem In-Reply-To: Message-ID: <20040726122325.96747.qmail@web13206.mail.yahoo.com> Sir, (1) On my sis630et board P6STMT, bios value of 0x8E is 00 (2) if I set 0x8E to 00 in IPL, ipl hangs on using stack to read linuxbios from DOC to ram (3) if I set 0x8E to 03 in IPL, linuxbios can start linux image successfully, but linux hangs at random time. (4) conclusion IPL init SDRAM has some trouble, memory can't work stably. It's so strange I have setted the values after the bios values. Is there any trick to init SDRAM on SIS630ET? tks zhu Nick Jarmany wrote: Zhu, On SiS630ET x8Eh has two active bits:- Bit 0: SDRAM synchronous mode. 0=Enable, 1=Disable Bit 1:Relationship between CPU & SDRAM clocks. 0=CPU>SDRAM, 1=CPU From YhLu at tyan.com Mon Jul 26 11:47:00 2004 From: YhLu at tyan.com (YhLu) Date: Mon Jul 26 11:47:00 2004 Subject: [NEWBIE question] LinuxBIOS & IEEE 1394 Message-ID: <3174569B9743D511922F00A0C943142305A9F1F7@TYANWEB> You can use FILO in Etherboot to get boot from USB (UHCI and OHCI). https://sourceforge.net/tracker/?func=detail&aid=943300&group_id=4233&atid=3 04233 Next step maybe EHCI support. Is there any 1394 sticks now? Regards YH -----Original Message----- From: Vincent BARBARIN [mailto:vbarbarin at ifrance.com] Sent: Monday, July 26, 2004 2:25 AM To: linuxbios at clustermatic.org Subject: [NEWBIE question] LinuxBIOS & IEEE 1394 Hi, here's a new one there, tired of those "Boot from ".... options that are not so available on those PCs... I'd like to know if there's any project going on to put in LinuxBIOS Int 13 support for IEEE 1394 drives (why not USB too ? motherboard integrated or not) Any link with linux1394.org ? Just for making any OS boot loader running from any drive... pleeeeeeeeeese ? _______________________________________________ Linuxbios mailing list Linuxbios at clustermatic.org http://www.clustermatic.org/mailman/listinfo/linuxbios From YhLu at tyan.com Mon Jul 26 13:06:01 2004 From: YhLu at tyan.com (YhLu) Date: Mon Jul 26 13:06:01 2004 Subject: AMD 8111 GPIO Message-ID: <3174569B9743D511922F00A0C943142305A9F20A@TYANWEB> You can use GPIO from AMD8111 and SuperIO Winbond 86327hf. But you need to check which pin can be linked out. Regards YH -----Original Message----- From: Jay Miller [mailto:jmiller at actuality-systems.com] Sent: Friday, July 23, 2004 1:45 PM To: linuxbios at clustermatic.org Subject: AMD 8111 GPIO We've got Linux up and running on our Tyan S2885 motherboards, using etherboot and filo with USB support. Thanks for all your help, and patience! I was hoping that with all the expertise here with AMD 8111 chipset, that someone would be able to answer my question. Although it's not strictly LinuxBIOS, it is Linux. ;-) So I'm trying to write a Linux driver for the GPIO pins on the AMD 8111. I saw a comment in amd8111_smbus.c that PMIOEN is set. I believe this is part of what I need to be able to drive the GPIOs. But how/where were all those hex values determined? The spec uses mnemonics to abstract the addresses, and I don't see how they correlate. Thanks, Jay Miller 781-229-7812x117 Actuality Systems, Inc. jmiller at acutality-systems.com _______________________________________________ Linuxbios mailing list Linuxbios at clustermatic.org http://www.clustermatic.org/mailman/listinfo/linuxbios From jmiller at actuality-systems.com Mon Jul 26 14:21:01 2004 From: jmiller at actuality-systems.com (Jay Miller) Date: Mon Jul 26 14:21:01 2004 Subject: AMD 8111 GPIO Message-ID: The GPIO pins are I/O mapped at an offset from the Power Management base address. The PM base address is at the second PCI device, function 3, offset 0x58. On a typical PC-BIOS this value is usually 0x5000. But when I do an lspci -xxx on a system running LinuxBIOS the value at offset 0x58 is 0x0000. I guess the question now is, does LinuxBIOS setup the PM base address? Jay Miller 781-229-7812x117 Actuality Systems, Inc. jmiller at acutality-systems.com -----Original Message----- From: YhLu [mailto:YhLu at tyan.com] Sent: Monday, July 26, 2004 2:46 PM To: Jay Miller; linuxbios at clustermatic.org Subject: RE: AMD 8111 GPIO You can use GPIO from AMD8111 and SuperIO Winbond 86327hf. But you need to check which pin can be linked out. Regards YH -----Original Message----- From: Jay Miller [mailto:jmiller at actuality-systems.com] Sent: Friday, July 23, 2004 1:45 PM To: linuxbios at clustermatic.org Subject: AMD 8111 GPIO We've got Linux up and running on our Tyan S2885 motherboards, using etherboot and filo with USB support. Thanks for all your help, and patience! I was hoping that with all the expertise here with AMD 8111 chipset, that someone would be able to answer my question. Although it's not strictly LinuxBIOS, it is Linux. ;-) So I'm trying to write a Linux driver for the GPIO pins on the AMD 8111. I saw a comment in amd8111_smbus.c that PMIOEN is set. I believe this is part of what I need to be able to drive the GPIOs. But how/where were all those hex values determined? The spec uses mnemonics to abstract the addresses, and I don't see how they correlate. Thanks, Jay Miller 781-229-7812x117 Actuality Systems, Inc. jmiller at acutality-systems.com _______________________________________________ Linuxbios mailing list Linuxbios at clustermatic.org http://www.clustermatic.org/mailman/listinfo/linuxbios From joey at joescan.com Mon Jul 26 19:17:01 2004 From: joey at joescan.com (Joey Nelson) Date: Mon Jul 26 19:17:01 2004 Subject: Change in flash chip kills my linuxbios. In-Reply-To: <410131EE.9050208@bitworks.com> Message-ID: <200407262316.i6QNGfK29343@nwn.definitive.org> I forgot to mention, the computer is supplied with award bios on the flashes, and the new Winbond flashes work fine with the included bios. > Subtle timeing problems? Whats the speed rating of both parts? This is possible. The SST was a 70ns part and the winbond a 90ns part. The PC104 computer is a FB2510, a basic GEODE GX1 with CS5530A. I am actually getting serial output (accidentally had it disabled before). It dies at: Jumping to LinuxBIOS. Everything up to that point is identical between the SST and Winbond parts. Only the SST continues on for the rest of the boot process. I've been pouring over the source code, and the datasheets for the GX1 and CS5530. But haven't seen any red flags yet. I have a logic analyzer that I can hook up to the isa bus to ensure that no timing is being violated for the 90ns parts. But I'd rather not have to go through that exercise. I'd love any additional hints on where to look. > How many address lines does the board really use? Its > possible that if some of the address lines were floating that > it might work with one part but not the other. I checked the socket against the PC/104 header and found that all the address lines are connected. Thanks for the input thus far. Joey From zhushisongzhu at yahoo.com Tue Jul 27 07:15:01 2004 From: zhushisongzhu at yahoo.com (zhu shi song) Date: Tue Jul 27 07:15:01 2004 Subject: how to setup FSB Message-ID: <20040727124852.11575.qmail@web13201.mail.yahoo.com> Dear lists, who knows how to setup FSB of winfast6300? I need linuxbios to support > 733M celeron. tks zhu __________________________________ Do you Yahoo!? New and Improved Yahoo! Mail - 100MB free storage! http://promotions.yahoo.com/new_mail From Stephen.Kimball at bench.com Wed Jul 28 09:54:02 2004 From: Stephen.Kimball at bench.com (Stephen.Kimball at bench.com) Date: Wed Jul 28 09:54:02 2004 Subject: Freebios2 amd/serenade keyboard init error Message-ID: <9B124F08B3EFDA4F8813B05102DC719501A90203@nh-ex01.nh.bench.com> I have built LinuxBIOS for the amd/serenade target and I get about 600 lines of good output to the serial port, which ends with Initializing devices... PCI: 00:18.0 init PCI: 00:18.3 init NB: Function 3 Misc Control.. done. PCI: 00:19.0 init PCI: 00:19.3 init NB: Function 3 Misc Control.. done. PCI: 01:01.0 init PCI: 01:02.0 init PNP: 002e.0 init PNP: 002e.2 init PNP: 002e.5 init POST: 0x00 POST: 0x00 POST: 0x00 POST: 0x00 POST: 0x00 POST: 0x00 The last line "POST: 0x00" repeats forever. PC80/keyboard.c is trying to initialize the keyboard. The code that is running is /* empty input buffer or any other command/data will be lost */ while ((inb(0x64) & 0x02)) post_code(0); The inb(0x64) reads 0xff forever. I heard that the keyboard initialization may not be needed. How can I fix this? Thanks. Steve -------------- next part -------------- An HTML attachment was scrubbed... URL: From tony_cheng at pcmagic.net Wed Jul 28 12:52:00 2004 From: tony_cheng at pcmagic.net (Tony Cheng) Date: Wed Jul 28 12:52:00 2004 Subject: Freebios2 amd/serenade keyboard init error References: <9B124F08B3EFDA4F8813B05102DC719501A90203@nh-ex01.nh.bench.com> Message-ID: <001801c474d0$71ef6330$932614ac@trans.corp> you can try to comment out the "init_pc_keyboard" from superio.c Tony ----- Original Message ----- From: Stephen.Kimball at bench.com To: linuxbios at clustermatic.org Sent: Wednesday, July 28, 2004 8:27 AM Subject: Freebios2 amd/serenade keyboard init error I have built LinuxBIOS for the amd/serenade target and I get about 600 lines of good output to the serial port, which ends with Initializing devices... PCI: 00:18.0 init PCI: 00:18.3 init NB: Function 3 Misc Control.. done. PCI: 00:19.0 init PCI: 00:19.3 init NB: Function 3 Misc Control.. done. PCI: 01:01.0 init PCI: 01:02.0 init PNP: 002e.0 init PNP: 002e.2 init PNP: 002e.5 init POST: 0x00 POST: 0x00 POST: 0x00 POST: 0x00 POST: 0x00 POST: 0x00 The last line "POST: 0x00" repeats forever. PC80/keyboard.c is trying to initialize the keyboard. The code that is running is /* empty input buffer or any other command/data will be lost */ while ((inb(0x64) & 0x02)) post_code(0); The inb(0x64) reads 0xff forever. I heard that the keyboard initialization may not be needed. How can I fix this? Thanks. Steve -------------- next part -------------- An HTML attachment was scrubbed... URL: From Stephen.Kimball at bench.com Wed Jul 28 14:47:00 2004 From: Stephen.Kimball at bench.com (Stephen.Kimball at bench.com) Date: Wed Jul 28 14:47:00 2004 Subject: Freebios2 amd/serenade keyboard init error Message-ID: <9B124F08B3EFDA4F8813B05102DC719501A90204@nh-ex01.nh.bench.com> Tony, Thanks. It worked. Instead I commented out the code in keyboard.c inside init_pc_keyboard(), since there are several versions of superio.c. Not sure which is used. Steve -----Original Message----- From: Tony Cheng [mailto:tony_cheng at pcmagic.net] Sent: Wednesday, July 28, 2004 2:27 PM To: Kimball, Stephen; linuxbios at clustermatic.org Subject: Re: Freebios2 amd/serenade keyboard init error you can try to comment out the "init_pc_keyboard" from superio.c Tony -------------- next part -------------- An HTML attachment was scrubbed... URL: From okajima at digitalinfra.co.jp Fri Jul 30 09:19:00 2004 From: okajima at digitalinfra.co.jp (Digital Infra, Inc.) Date: Fri Jul 30 09:19:00 2004 Subject: Linux from NTLDR Message-ID: <200407301450.AA01642@winxp.digitalinfra.co.jp> (Doublely posted to Grub and LinuxBIOS ML. Tell me which is appropriate.) Hello. I am working on booting Linux from NTLDR. I mean, you dont have to install a Grub on your MBR. Check this: http://denbbs.angelskyarea.com/YaBB.cgi?board=discuss;action=display;num= 1087892282;start=180 First, I want to hear your opinion about it. And I appriciate much if you give me even hints of development. Second, Do you know a small Linux kernel build which runs as one relocatable binary file? In other words, vmlinux.com. Of course, I use .com here as not internet, but MS-DOS word. Okajima, Jun. Digital Infra, Inc. Tokyo, Japan. (Japanese native can mail me directly with Japanese lang.) From matt at rolec.ltd.uk Fri Jul 30 09:34:01 2004 From: matt at rolec.ltd.uk (Matt Jarvis) Date: Fri Jul 30 09:34:01 2004 Subject: Linux from NTLDR In-Reply-To: <200407301450.AA01642@winxp.digitalinfra.co.jp> References: <200407301450.AA01642@winxp.digitalinfra.co.jp> Message-ID: <410A644E.4070506@rolec.ltd.uk> A cursory google throws up loads of stuff about doing this : http://www.devhood.com/tutorials/tutorial_details.aspx?tutorial_id=313 http://jaeger.morpheus.net/linux/ntldr.html Personally I would use grub, but each to their own... Digital Infra, Inc. wrote: > (Doublely posted to Grub and LinuxBIOS ML. Tell me which is appropriate.) > > Hello. > > I am working on booting Linux from NTLDR. I mean, you dont have to > install a Grub on your MBR. > > Check this: > http://denbbs.angelskyarea.com/YaBB.cgi?board=discuss;action=display;num= > 1087892282;start=180 > > First, I want to hear your opinion about it. And I appriciate much > if you give me even hints of development. > > Second, Do you know a small Linux kernel build which runs as one > relocatable binary file? In other words, vmlinux.com. > Of course, I use .com here as not internet, but MS-DOS word. > > Okajima, Jun. Digital Infra, Inc. Tokyo, Japan. > (Japanese native can mail me directly with Japanese lang.) > > > _______________________________________________ > Linuxbios mailing list > Linuxbios at clustermatic.org > http://www.clustermatic.org/mailman/listinfo/linuxbios -- Matt Jarvis Technical Development Manager Rolec Music Ltd 210 Belgravia Works, Marlborough Road, London, UK N19 4NF Tel: +44 207 281 4776 Fax : +44 207 281 4565 mailto: matt at rolec.ltd.uk web: www.rolecmusic.com This email is strictly confidential and intended solely for the addressee(s). It may contain personal and confidential information and as such may be protected by the Data Protection Act 1998. If this email has come to you in error you must take no action based on it, nor must you copy or show it to anyone; please reply to this email and highlight the error. Any views or opinions expressed within this email are those of the author, and do not necessarily represent those of the company. Although we have taken steps to ensure that this email and attachments are free from any virus, we advise that in keeping with good computer practice the recipient should ensure they are actually virus free. From stuge-linuxbios at cdy.org Fri Jul 30 10:05:01 2004 From: stuge-linuxbios at cdy.org (Peter Stuge) Date: Fri Jul 30 10:05:01 2004 Subject: Linux from NTLDR In-Reply-To: <410A644E.4070506@rolec.ltd.uk> References: <200407301450.AA01642@winxp.digitalinfra.co.jp> <410A644E.4070506@rolec.ltd.uk> Message-ID: <20040730154015.GA26882@foo.birdnet.se> On Fri, Jul 30, 2004 at 04:07:58PM +0100, Matt Jarvis wrote: > A cursory google throws up loads of stuff about doing this : > > http://www.devhood.com/tutorials/tutorial_details.aspx?tutorial_id=313 > > http://jaeger.morpheus.net/linux/ntldr.html > > Personally I would use grub, but each to their own... Without reading any of the above, this is what I do: # in Linux dd if=/dev/hda of=/boot/bootsect.lix bs=512 count=1 cat << EOF > /etc/lilo.conf lba32 boot=/boot/bootsect.lix root=/dev/hda2 read-only image=/usr/src/linux-2.6.7/arch/i386/boot/bzImage label=lix267 EOF lilo # then copy /boot/bootsect.lix to wherever Windows thinks is C:\ # and add this line to C:\boot.ini in the appropriate section. C:\bootsect.lix=Linux I can see how using GRUB would be especially beneficial under these circumstances but I much prefer LILO anyway. Call me old-fashioned if you like. :) //Peter From okajima at digitalinfra.co.jp Sat Jul 31 15:19:00 2004 From: okajima at digitalinfra.co.jp (Digital Infra, Inc.) Date: Sat Jul 31 15:19:00 2004 Subject: Linux from NTLDR In-Reply-To: <20040730154015.GA26882@foo.birdnet.se> References: <20040730154015.GA26882@foo.birdnet.se> Message-ID: <200407312053.AA01655@winxp.digitalinfra.co.jp> Thank you Stuge, Jarvis, for replying me. Sorry, I lost very imporant point in the previous mail. What we has been committing is, 1. Install Linux partitiln as a very big file on NTFS. In other words, you can install Linux without creating a new partition dedicated to Linux. 2. Boot Linux from that big file by NTLDR. What you told me is right and useful but it is not I am disucussing. It is about booting Linux from Linux partition with NTLDR. What I am seeking is, booting from NTFS partition. First, We ( Okajima and Topologi Linux guys ) believe that current Linux distribution has a fault for newbies. It requies a new partition and Grub (or Lilo) installed to their MBR. You can understand how much this is painful for newbies? Then, we started creating a newbie friendily Linux. We has succeeded for some degree. We has booted Linux by Grub. And there has been MLD which is a very similar commercial distribution using Lilo. Both technology is almost same. They map absolute sector numbers of stage2 to stage1. This works if you dont defrag. But if someone defrag? it does not boot. We did has been wanting to eliminate this problem. And it comes. A hacker named Tinybit solves. His boot loader can load Grub stage2 on NTFS without sector mapping. Good......Thanks, Tinybit. But even his great code still has a problem. Grub can not understand all of NTFS. Even with his code, some NTFS partition does not boot. I am seeking solving this problem. My proposal is this. 1. We already succeeded to boot Grub stage2 from NTLDR directly. 2. The format of grub2 we used is same as .com file of MSDOS. 3. Then, if we have vmlinux.com, I think we can boot vmlinux directly. 4. If it boots, we can boot any vmlinux on NTFS/IDE drive which current linux can handle. Because, if once we boot any linux, we can use kexec to boot another linux. Huuuah. Tired with writing long (wrong?) English. Okay? So I want your opinion. 1. What do you think about my project? 2. Can you give me any hints? 3. Do you know something like vmlinux.com? Sorry for LinuxBIOS guys. This seems to be not related to an embedded matter. But, If you are a cluster computing guy, making Linux newbie friendly would be your profit. More people come to Linux, you get more grid node automatically. FYI, check these URLs. http://www.topologilinux.com/ http://www.mlb.co.jp/linux/support-mld7/hwtest.html ftp://www.mlb.co.jp/pub/linux/mld7/mld7hwtest.exe (Free Sample version of MLD) http://denbbs.angelskyarea.com/YaBB.cgi?board=discuss;action=display;num= 1087892282;start=195 --- Okajima. Tokyo, Japan. --------------------------------------------------------------------- >On Fri, Jul 30, 2004 at 04:07:58PM +0100, Matt Jarvis wrote: >> A cursory google throws up loads of stuff about doing this : >> >> http://www.devhood.com/tutorials/tutorial_details.aspx?tutorial_id=313 >> >> http://jaeger.morpheus.net/linux/ntldr.html >> >> Personally I would use grub, but each to their own... > >Without reading any of the above, this is what I do: > ># in Linux >dd if=/dev/hda of=/boot/bootsect.lix bs=512 count=1 >cat << EOF > /etc/lilo.conf >lba32 >boot=/boot/bootsect.lix >root=/dev/hda2 >read-only >image=/usr/src/linux-2.6.7/arch/i386/boot/bzImage > label=lix267 >EOF >lilo > ># then copy /boot/bootsect.lix to wherever Windows thinks is C:\ ># and add this line to C:\boot.ini in the appropriate section. >C:\bootsect.lix=Linux > >I can see how using GRUB would be especially beneficial under these >circumstances but I much prefer LILO anyway. Call me old-fashioned >if you like. :) > > >//Peter >_______________________________________________ >Linuxbios mailing list >Linuxbios at clustermatic.org >http://www.clustermatic.org/mailman/listinfo/linuxbios >