off-topic part 2: PIC and ETRAX [was: Memtest+]
Again Peter, very nice:) I will give you one more tid bit as it consumes less power than the Axis, but still runs Linux and is quite small:) Check out: http://www.brightstareng.com/ They have entire set ups on a form factor less than a credit card Running Linux:) Although it is still not a PIC, it is very good For PIC type needs. Thanks again, Dave:) -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Peter Stuge Sent: Thursday, December 30, 2004 2:54 PM To: LinuxBIOS Subject: Re: off-topic: PIC and ETRAX [was: Memtest+] On Thu, Dec 30, 2004 at 02:25:47PM -0500, Dave Aubin wrote: > Nice read Peter, thank you for the info:) No problem! > Would be nice to use some voltage reference differencing Instead of > using a Max 232, but the Max is probably a cleaner approach. The MAX232 is pretty common for connecting both PIC and AVR devices to RS-232 equipment. It just needs a few external capacitors, which is nice. > A nerdy aside, I heard the 18F4550 and 18F2550 can run up to 12MIPs > from a 4MHz crystal, they've got a whopping 16K of flash, and they > have a Full-Speed USB v2.0 hardware. Yep. And 2kb RAM. Check out the data sheet page 11 and chapter 2. http://ww1.microchip.com/downloads/en/DeviceDoc/39632b.pdf > Now if I could only run Linux on a PIC;) Linux? That's for the ETRAX, made by Axis. Check out http://developer.axis.com/ Everything-is-included Linux chip with 10/100 and both NOR and NAND flash for boot as well as storage. They've ported the GNU toolchain too. I'm still waiting for some project where I can use the MCM and end up with a few extra boards. :) //Peter ___ Linuxbios mailing list Linuxbios@clustermatic.org http://www.clustermatic.org/mailman/listinfo/linuxbios ___ Linuxbios mailing list Linuxbios@clustermatic.org http://www.clustermatic.org/mailman/listinfo/linuxbios
RE: Memtest+
Nice read Peter, thank you for the info:) Would be nice to use some voltage reference differencing Instead of using a Max 232, but the Max is probably a cleaner approach. A nerdy aside, I heard the 18F4550 and 18F2550 can run up to 12MIPs from a 4MHz crystal, they've got a whopping 16K of flash, and they have a Full-Speed USB v2.0 hardware. Now if I could only run Linux on a PIC;) Thanks, Dave -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Peter Stuge Sent: Thursday, December 30, 2004 1:57 PM To: LinuxBIOS Subject: Re: Memtest+ On Wed, Dec 29, 2004 at 04:58:57PM -0500, Dave Aubin wrote: > Has no one else hit this? One idea I have being a PIC lover is To > use some LED's on the mother board and make a serial protocol Over the > LED's, much like a software UART for a PIC. > Anyone have an input on this? That will work just fine, but watch out for running the "GPIO serial bus" too fast for the PIC. (With GPIO I'm referring to pins driving the LEDs on the target system, not a PIC GPIO port.) If simplex is fun enough, you could use a single GPIO pin and connect that to RX on the PIC, connect TX on the PIC to a MAX232 and plug that into a regular serial port on a PC running a terminal emulator. All the PIC has to do then is read from RCREG and send everything back out through TXREG. Any PIC with a USART in async mode should do for this. For duplex (etherboot/filo menu) you may need a separate GPIO pin for flow control, the usual serial start/stop bit handshake may not be very reliable without a hardware UART on the target system. The easy solution is to use a synchronous serial interface instead; add a clock signal driven by the target. This also overcomes any problems caused by the PIC baud rate generator being controllable only with relatively low precision. The 16F87x series have both an MSSP and a USART; the MSSP could be used in SPI Slave mode for duplex communication with the target system, and the USART for talking to the PC running the terminal emulator. One thing to keep in mind is that SPI always transmits data in both directions, this means that the serial port wont be 8-bit clean unless you make a small protocol to indicate when data actually is available, this wastes twice the bandwidth, but may still be good enough. A USB device with a 16C745 or possibly 18F2550 if they can be sourced is tempting, but that also requires writing some kind of driver for the USB device, or figuring out how an existing USB<->serial adapter works and reimplementing that. Too much work. Plus the 16C7x5 only do low-speed USB. Hope it works out though! //Peter ___ Linuxbios mailing list Linuxbios@clustermatic.org http://www.clustermatic.org/mailman/listinfo/linuxbios ___ Linuxbios mailing list Linuxbios@clustermatic.org http://www.clustermatic.org/mailman/listinfo/linuxbios
RE: Memtest+
Hi, Home groan motherboard that does not have a serial connection Due to cost concerns. So using the serial line is out of the Question. Has no one else hit this? One idea I have being a PIC lover is To use some LED's on the mother board and make a serial protocol Over the LED's, much like a software UART for a PIC. Anyone have an input on this? Thanks, Dave -Original Message- From: YhLu [mailto:[EMAIL PROTECTED] Sent: Wednesday, December 29, 2004 5:06 PM To: Dave Aubin; LinuxBIOS Subject: RE: Memtest+ What's you motherboard... If you are using btext_console, then you may need to add bcontext console calling in memtest+, Please refer btext in Etherboot YH -Original Message----- From: Dave Aubin [mailto:[EMAIL PROTECTED] Sent: Wednesday, December 29, 2004 12:27 PM To: LinuxBIOS Subject: Memtest+ Hi, I'm trying to get memtest+ to fly on our system. Problem is That I don't have a console on my system. I have USB and a video card, But the video card bios isn't run since I run linuxbios. Can anyone please give me a hint as to how they've done it? Thanks, Dave ___ Linuxbios mailing list Linuxbios@clustermatic.org http://www.clustermatic.org/mailman/listinfo/linuxbios ___ Linuxbios mailing list Linuxbios@clustermatic.org http://www.clustermatic.org/mailman/listinfo/linuxbios
Memtest+
Hi, I'm trying to get memtest+ to fly on our system. Problem is That I don't have a console on my system. I have USB and a video card, But the video card bios isn't run since I run linuxbios. Can anyone please give me a hint as to how they've done it? Thanks, Dave ___ Linuxbios mailing list Linuxbios@clustermatic.org http://www.clustermatic.org/mailman/listinfo/linuxbios
RE: booting slow
-Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Ronald G. Minnich Sent: Wednesday, December 15, 2004 11:22 PM To: Gin Cc: 'LinuxBIOS' Subject: RE: booting slow On Thu, 16 Dec 2004, Gin wrote: > The getpir util generates a routing table by looking at the memory > config of my "developing" machine. How's it related to my target > machine? It almost certainly is wrong, unless all the wires on the machines are absolutely identical. I am willing to guess your irq tabls for the target are wrong. You can only use getpir if you have a working bios. Otherwise you Will get junk. Considering your board is new, you don't have a Working bios, no? You have to go the hard way and read the Bottom link as to how to make the irq.c file. Base it off of your Motherboard design and make changes where the wires are, based on The shematic. Enjoy:) > Any document I can reference? This link mentioned on irq_tables.c > http://www.microsoft.com/hwdev/busbios/PCIIRQ.HTM doesn't work. oh great. I will try to find a copy here. Ron Here it is: http://www.microsoft.com/whdc/archive/pciirq.mspx ___ Linuxbios mailing list [EMAIL PROTECTED] http://www.clustermatic.org/mailman/listinfo/linuxbios ___ Linuxbios mailing list [EMAIL PROTECTED] http://www.clustermatic.org/mailman/listinfo/linuxbios
RE: booting slow
Oh, one more thing. It was easy to see when doing A cat /proc/interrupts and watching the offending interrupt configured wrong Just increment like mad. -Original Message- From: Ronald G. Minnich [mailto:[EMAIL PROTECTED] Sent: Wednesday, December 15, 2004 11:09 AM To: Dave Aubin Cc: Gin; LinuxBIOS Subject: RE: booting slow On Wed, 15 Dec 2004, Dave Aubin wrote: > Seen this when interrupts in irq.c were wrong based on The motherboard. > In our case we'd use etherboot to Load the kernel (which doesn't > handle > interrupts) then Once kernel was loaded we'd see the problem. This > Was fixed by fixing the irq table. glad to see someone else confirm this ... ron ___ Linuxbios mailing list [EMAIL PROTECTED] http://www.clustermatic.org/mailman/listinfo/linuxbios
RE: booting slow
Seen this when interrupts in irq.c were wrong based on The motherboard. In our case we'd use etherboot to Load the kernel (which doesn't handle interrupts) then Once kernel was loaded we'd see the problem. This Was fixed by fixing the irq table. Dave -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Ronald G. Minnich Sent: Tuesday, December 14, 2004 9:20 PM To: Gin Cc: 'LinuxBIOS' Subject: RE: booting slow On Wed, 15 Dec 2004, Gin wrote: > The serial interrupt? Shouldn't it be easy like assigning it an irq? > What other causes that you've found out? One possibility I can think > of is the cache. It was turned off. well, that was the other possibility I was going to mention, on our first tries at smp four years ago we'd see things run fast until the other SMP CPU got turned on, then run slow. Turns out the cache was only enabled on one cpu ... ron ___ Linuxbios mailing list [EMAIL PROTECTED] http://www.clustermatic.org/mailman/listinfo/linuxbios ___ Linuxbios mailing list [EMAIL PROTECTED] http://www.clustermatic.org/mailman/listinfo/linuxbios
RE: Stuck. Compile error with a clean tree.
Do you have access to the network? If you don't have a com cable (like I did in the beginning) then You could try netconsole. Here are some links to what it is. http://lwn.net/Articles/43852/ http://technocrat.net/article.pl?sid=04/08/14/0236245&mode=nested Although this will only help you if you are getting to a 2.6 kernel And have a network connection. Dave -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Adam Talbot Sent: Monday, November 29, 2004 5:19 PM To: Ronald G. Minnich Cc: [EMAIL PROTECTED] Subject: Re: Stuck. Compile error with a clean tree. Clean compile of the adl855pc. I changed 2 lines in the config and added one. added:option ROM_SIZE=524288 normal, changed: option ROM_IMAGE_SIZE=0x1tooption ROM_IMAGE_SIZE=0x15000 fallback, changed: option ROM_IMAGE_SIZE=0x1tooption ROM_IMAGE_SIZE=0x15000 Still get garbage to the screen... Bad cable? Switched cables, same. Idea, added console redirect to my grub.conf set the speed to 115200 8n1, works fine. Hummm What does it take to get the onboard VGA running? Can you give me a quick "how to"? -Adam Talbot - Original Message - From: "Ronald G. Minnich" <[EMAIL PROTECTED]> To: "Adam Talbot" <[EMAIL PROTECTED]> Cc: <[EMAIL PROTECTED]> Sent: Monday, November 29, 2004 1:47 PM Subject: Re: Stuck. Compile error with a clean tree. > that's odd, in the adl855pc I got output just fine. > > For the heck of it, build an adl855pc target and see if you get the same > problem. > > ron > > ___ Linuxbios mailing list [EMAIL PROTECTED] http://www.clustermatic.org/mailman/listinfo/linuxbios ___ Linuxbios mailing list [EMAIL PROTECTED] http://www.clustermatic.org/mailman/listinfo/linuxbios
RE: FILO fixups
Then I am happy:-) -Original Message- From: Ronald G. Minnich [mailto:[EMAIL PROTECTED] Sent: Monday, November 01, 2004 3:58 PM To: Dave Aubin Cc: Li-Ta Lo; YhLu; LinuxBIOS Subject: RE: FILO fixups On Mon, 1 Nov 2004, Dave Aubin wrote: > Although...sniff I do like it in etherboot;) it will stay in etherboot, no question about that! ron ___ Linuxbios mailing list [EMAIL PROTECTED] http://www.clustermatic.org/mailman/listinfo/linuxbios
RE: FILO fixups
Filo does need a home and it can run outside of etherboot So I would concede that is ok to have a home for it. Although...sniff I do like it in etherboot;) -Original Message- From: Li-Ta Lo [mailto:[EMAIL PROTECTED] Sent: Monday, November 01, 2004 3:46 PM To: Dave Aubin Cc: Ronald G. Minnich; YhLu; LinuxBIOS Subject: RE: FILO fixups On Mon, 2004-11-01 at 13:21, Dave Aubin wrote: > Hi, > > I'll voice my desire to have etherboot with filo. > I love the fact that I can first try to boot remotely And then if not > use filo. For this reason alone I am A fan of the mechanism. Try > remote first then if fail Use local storage. If we can, can we please > put the Etherboot flavor in utils that has both network & filo > support? > First of all, we didn't say we don't want choice. Actually we want more, including the choice of not having some choices. The problems of FILO/Etherboot are: 1. Some people have hard time building Etherboot. 2. Some people don't want the feature provided by Etherboot, they are satisfied by FILO itself. 3. FILO (as FILO itself) does not have an official host. If we want to continue maintain FILO to serve people in 1. and 2., we have to put it somewhere. If you want FILO as FILO+Etherboot, why don't you get it from etherboot project? Ollie ___ Linuxbios mailing list [EMAIL PROTECTED] http://www.clustermatic.org/mailman/listinfo/linuxbios
RE: FILO fixups
Ah, that could be the culprit. I'm using reiserfs, not ext2 With filo. Although it says it supports it. Perhaps it is The file system that caused my hair loss ;) Yes, having the net connection does make things nice...if ya have it:) -Original Message- From: Ronald G. Minnich [mailto:[EMAIL PROTECTED] Sent: Monday, November 01, 2004 3:42 PM To: Dave Aubin Cc: Li-Ta Lo; YhLu; LinuxBIOS Subject: RE: FILO fixups On Mon, 1 Nov 2004, Dave Aubin wrote: > Consider the redundancy aspect of it. First try remote. again, if you have remote to try, that's fine, go for it. If you don't have that ethernet connection, then counting on etherboot is kind of pointless :-) > There is also the error in filo where it can not handle an elf With > both a kernel and initrd. It can only handle a kernel. > To use filo I had to pack it up with initramfs, i.e. one big kernel. > Etherboot remote boot doesn't have this problem. ?? in an ext2 on filo, i've got a kernel and initrd and it loads it up just fine, so I don't see what you mean. ron ___ Linuxbios mailing list [EMAIL PROTECTED] http://www.clustermatic.org/mailman/listinfo/linuxbios
RE: FILO fixups
Consider the redundancy aspect of it. First try remote. If that fails go local or vs versa. Kinda like if mom is Around listen to her, if she's not around well then think For yourself;) Consider embedded size aspect of it as well. A kernel and Initrd in my situation is about 4Meg. On my local drive it Is about half that. Size costs more on my embedded local side. I do like the versatility of etherboot having both local and Net in one, but I totally understand why you'd want just filo As the kernel can do the remote side. There is also the error in filo where it can not handle an elf With both a kernel and initrd. It can only handle a kernel. To use filo I had to pack it up with initramfs, i.e. one big kernel. Etherboot remote boot doesn't have this problem. -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Li-Ta Lo Sent: Monday, November 01, 2004 3:05 PM To: YhLu Cc: Ronald G. Minnich; LinuxBIOS Subject: RE: FILO fixups On Mon, 2004-11-01 at 12:00, YhLu wrote: > The reason for put filo in etherboot. > 1. It can let boot from HD or net according to CMOS setting. > 2. Etherboot can produce zelf. We may got more space to put other > stuff such as USB support... > 3. Etherboot structure and support... > > I may check if filo.zlef only include FILO ..., even it is not, we > still can make it clean. > You have the same blind spot as Eric. For many people, boot over net is irrelevant. Why do they need to live with the overhead of network protocol stack and driver if all they want to to boot form some mass storage device ? Ollie ___ Linuxbios mailing list [EMAIL PROTECTED] http://www.clustermatic.org/mailman/listinfo/linuxbios ___ Linuxbios mailing list [EMAIL PROTECTED] http://www.clustermatic.org/mailman/listinfo/linuxbios
RE: FILO fixups
Hi, I'll voice my desire to have etherboot with filo. I love the fact that I can first try to boot remotely And then if not use filo. For this reason alone I am A fan of the mechanism. Try remote first then if fail Use local storage. If we can, can we please put the Etherboot flavor in utils that has both network & filo support? Kind thanks, Dave:) -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Ronald G. Minnich Sent: Monday, November 01, 2004 2:56 PM To: YhLu Cc: Li-Ta Lo; LinuxBIOS Subject: RE: FILO fixups On Mon, 1 Nov 2004, YhLu wrote: > 1. It can let boot from HD or net according to CMOS setting. only useful if your ethernet is hooked up. 15/16 of our nodes here have no ethernet. > 2. Etherboot can produce zelf. We may got more space to put other > stuff such as USB support... not that important to us. > 3. Etherboot structure and support... not clear at the moment if this is a plus or minus. Seeing that it has trouble building under certain tool chains, there still seem to be problems with it. > I may check if filo.zlef only include FILO ..., even it is not, we > still can make it clean. We still need to add my performance improvements. ron ___ Linuxbios mailing list [EMAIL PROTECTED] http://www.clustermatic.org/mailman/listinfo/linuxbios ___ Linuxbios mailing list [EMAIL PROTECTED] http://www.clustermatic.org/mailman/listinfo/linuxbios
RE: Kernel for linuxbios
Two things strike me as odd. 1. Your ," PCI: IRQ 0 for device :02:00.1 doesn't match PIRQ mask - try pci=usepirqmaskPCI: 02:01.0 [1022/7462] disabled" Type of errors. Looks like you pcirqp map is bad? Are you making your Own mother board? If so it is important that you get this and the mp Table correct based on your wiring. 2. You did get to initramfs, good job, but it did fail to mount you File system. This could be anything. Please send your init script And Describe what are you trying to mount. A USB stick, ide, what? -Original Message- From: Sagiv Yefet [mailto:[EMAIL PROTECTED] Sent: Sunday, October 31, 2004 5:45 AM To: Dave Aubin Cc: [EMAIL PROTECTED] Subject: RE: Kernel for linuxbios I took your advise and try the 2.6. I am using the initramfs_data.cpio.gz from the link you send me. The mkelf command is: ./objdir/sbin/mkelfImage -t bzImage-i386 --kernel=/home/sagivy/bzImage-2.6. --command-line="rw console=ttyS0,115200 root=/dev/ram0" --initrd=/home/sagivy/initramfs_data.cpio.gz --output=/home/sagivy/bzImage2.6.8.elf And here is the output: Jumping to Linux Linux version 2.6.8 ([EMAIL PROTECTED]) (gcc version 3.3.3) #6 Mon Nov 17 21:49:23 IST 2003 BIOS-provided physical RAM map: BIOS-e820: - 0d54 (rese BIOS-e820: 0d54 - 000a (usable) BIOS-e820: 000f - 000f0400 (reserved) BIOS-e820: 0010 - 2000 (usable) 0MB HIGHMEM available. 512MB LOWMEM available. DMI not present. ACPI: Unable to locate RSDP Built 1 zonelists Kernel command line: rw console=ttyS0,115200 root=/dev/ram0 Initializing CPU#0 PID hash table entries: 4096 (order 12: 32768 bytes) Detected 1603.740 MHz processor. Using tsc for high-res timesource Console: colour VGA+ 80x25 Dentry cache hash table entries: 131072 (order: 7, 524288 bytes).. Inode-cache hash table entries: 65536 (order: 6, 262144 bytes) PCI: Using configuration type 1 Memory: 515700k/524288k available (1525k kernel code, 7824k reserved, 702k data, K8 Northbridge Enumerating: AMD K8 CPU 228k init, 0k highmem)g: AMD 8111 Southbridge Checking if this processor honours the WP bit even in supervisor mode... Ok. Enumerating buses... amdk8_scan_root_bus Calibrating delay loop... 3162.11 BogoMIPSart scaning pci bus Mount-cache hash table entries: 512 (order: 0, 4096 bytes) PCI: 00:18.0 [1022/1100] enabled CPU: L1 I Cache: 64K (64 bytes/line), D cache 64K (64 bytes/line) PCI: 00:18.2 [1022/1102] enabled CPU: L2 Cache: 1024K (64 bytes/line)022/1103] ops Enabling fast FPU save and restore... done. HyperT rese Enabling unmasked SIMD FPU exception support... done.for bus 1 PCI: 01:01.0 [10 Checking 'hlt' instruction... OK. PCI: 01:01.0 [1022 checking if image is initramfs... it is PCI: 01:02.0 [1022/7468] bus ops Freeing initrd memory: 151k freedCI: 01:02.0 [1022/7468] enabled NET: Registered protocol family 16 01:02.1 [1022/7469] ops EISA bus registeredCI: 01:02.1 [1022/7 PCI: Using configuration type 1 PCI: 01:02.2 [1022 mtrr: v2.0 (20020519) Linux Plug and Play Support v0.97 (c) Adam Belay PCI: 01:02.3 [1022/746b] enabled PCI: Probing PCI hardware PCI: 01:02.5 [1022/746 PCI: IRQ 0 for device :02:00.0 doesn't match PIRQ mask - try pci=usepirqmask7463] ops PCI: 02:00.2 [1022/7463] disabled PCI: IRQ 0 for device :02:00.1 doesn't match PIRQ mask - try pci=usepirqmaskPCI: 02:01.0 [1022/7462] disabled PCI: 02:0a.0 PCI: IRQ 0 for device :02:0a.0 doesn't match PIRQ mask - try pci=usepirqmask PCI: 02:0b.0 [1002/4752] enabled PCI: IRQ 0 for device :02:0b.0 doesn't match PIRQ m PCI: 02:0e.0 [14e PNP: 002e.7 disabled apm: BIOS not found. disabled VFS: Disk quotas dquot_6.5.1d PNP: 0 Dquot-cache hash table entries: 1024 (order 0, 4096 bytes) scan_static_bus done PC isapnp: Scanning for PnP cards...=02 isapnp: No Plug & Play device found 0 new max: 2 Real Time Clock Driver v1.12ort scan link done Serial: 8250/16550 driver $Revision: 1.90 $ 48 ports, IRQ sharing enabled PCI: pci_scan_bus returning with max=02 ttyS0 at I/O 0x3f8 (irq = bus: AMD8111: not 100% native mode: w
RE: Makefile changes for symbols
Hi, I don't know if this is your problem or not, but I have seen Issues when using #if 0 or #ifdef causing Alignment issues. What you co do is run the file through the Pre-procesor to generate output as what the compiler sees and then Use this as your source. Windows .net actuality is the one I've Seen this alignment issue with. That might be it. Dave -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Ronald G. Minnich Sent: Friday, October 22, 2004 11:33 AM To: [EMAIL PROTECTED] Cc: [EMAIL PROTECTED]; [EMAIL PROTECTED]; [EMAIL PROTECTED] Subject: RE: Makefile changes for symbols On Fri, 22 Oct 2004 [EMAIL PROTECTED] wrote: > Rod, > > I'm using Source Point 7.0.0. I can see the source files. I can > display source, disassembly or mixed. However, the disassembly > doesn't match up with the source code. There is a way to give Source > Point an offset when the symbols are loaded, but I can't seem to get > the right value. I know the address of _start and __protected_start > but these labels are not in linuxbios_c.o. I need to find the > location of a symbol in linuxbios_c.o to compute the offset. there is a file we create called linuxbios.map, did you check that out? ron ___ Linuxbios mailing list [EMAIL PROTECTED] http://www.clustermatic.org/mailman/listinfo/linuxbios ___ Linuxbios mailing list [EMAIL PROTECTED] http://www.clustermatic.org/mailman/listinfo/linuxbios
RE: Makefile changes for symbols
Hi Steve, Nice to hear someone else in the northeast is using lb:) Methods we use to do linux bios debugging: 1. Serial 2. netconsole (same as serial but over ethernet) 3. Hardware Emulator with debugger 4. Toggling leds at certain places (i.e. like printfs for leds;) -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of [EMAIL PROTECTED] Sent: Wednesday, October 20, 2004 8:29 AM To: [EMAIL PROTECTED] Cc: [EMAIL PROTECTED] Subject: RE: Makefile changes for symbols Ron, Is LinuxBIOS development done with only serial port debug messages? You guys are good. Steve -Original Message- From: Ronald G. Minnich [mailto:[EMAIL PROTECTED] Sent: Tuesday, October 19, 2004 5:25 PM To: Kimball, Stephen Cc: [EMAIL PROTECTED] Subject: Re: Makefile changes for symbols On Tue, 19 Oct 2004 [EMAIL PROTECTED] wrote: > > Someone must have some experience with source code level debugging of > LinuxBIOS with an American Arium ECM-50. Thanks. wow! I want to hear about that when you get it going. Another FAQ entry. ron ___ Linuxbios mailing list [EMAIL PROTECTED] http://www.clustermatic.org/mailman/listinfo/linuxbios ___ Linuxbios mailing list [EMAIL PROTECTED] http://www.clustermatic.org/mailman/listinfo/linuxbios
RE: PCI IRQ tables
Don't I wish! PCI-X is dangled off of the 8131? I think My memory is bad. But one needs to configure the pci irq Before getting to the pci-x in order to see it show up Correctly under linux by lspci. Then I believe your Messages can be handled via the virtual signaled interrupts. -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] Sent: Tuesday, October 19, 2004 1:17 PM To: Liu Tao Cc: YhLu; Dave Aubin; [EMAIL PROTECTED] Subject: Re: PCI IRQ tables On Tue, Oct 19, 2004 at 12:12:50PM +0800, Liu Tao wrote: > Or does the interrupt router in pirq table only responses of legacy > 32bitPCI/ISA devices, and Linux handles all the AMD8131? Forgive my ignorance, but doesn't the fact that PCI-X is all message signaled interrupts obviate the need for a PCIIRQ table? ___ Linuxbios mailing list [EMAIL PROTECTED] http://www.clustermatic.org/mailman/listinfo/linuxbios
RE: linux kernel patch
http://sourceforge.net/cvs/?group_id=3206 Freebios2 is the latest chipsets and mainboards. -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Gin Sent: Thursday, October 14, 2004 5:05 AM To: 'David Hendricks' Cc: [EMAIL PROTECTED] Subject: RE: linux kernel patch Hello David, Thanks for your quick response. Do you know where I can get the latest linuxbios source code(freebios2)? Call me crazy, but I couldn't seem able to find it through SourceForge. http://sourceforge.net/ thanks, Gin -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of David Hendricks Sent: Thursday, October 14, 2004 4:08 PM To: [EMAIL PROTECTED] Subject: Re: linux kernel patch We appreciate your interest in the project! As I recall, the patches were just something for some SiS chipset support in older LinuxBIOS versions (freebios1). Since then, LinuxBIOS has advanced to include more generic chipset support that does not require kernel patches. The current LinuxBIOS (freebios2) will work without patches to your kernel. On Thu, 14 Oct 2004 15:34:13 +0800 "Gin" <[EMAIL PROTECTED]> wrote: > Hello Ron, > I don't' know if you are still working on this project since it's 2004 > now. I just finished a presentation of Linuxbios at work. We are > highly interested in getting linuxbios running on our systems(we > design motherboards). I have a question about the way you do the > kernel patch. If the patch is to initialize the uninitialized hardware > in order to run linux. Then why didn't we add it into the C code. Let > it become part of linuxbios rom image? Furthermore, why do you have > different patches for different linux kernel versions? > Sorry if the questions are too basic. We just started trying to get it > built. > > Thanks, > Gin > ___ Linuxbios mailing list [EMAIL PROTECTED] http://www.clustermatic.org/mailman/listinfo/linuxbios ___ Linuxbios mailing list [EMAIL PROTECTED] http://www.clustermatic.org/mailman/listinfo/linuxbios ___ Linuxbios mailing list [EMAIL PROTECTED] http://www.clustermatic.org/mailman/listinfo/linuxbios
RE: Kernel for linuxbios
disk floppy. Some users may wish to combine steps (d) and (f) by using a pipe. -- Paul Gortmaker 12/95 -Original Message- From: Stefan Reinauer [mailto:[EMAIL PROTECTED] Sent: Wednesday, October 13, 2004 10:28 AM To: Sagiv Yefet Cc: Dave Aubin; [EMAIL PROTECTED] Subject: Re: Kernel for linuxbios * Sagiv Yefet <[EMAIL PROTECTED]> [041013 16:11]: > Actually, I am using 2.4.24. > Maybe I should upgrade to 2.6.*. > but in the meanwhile what could be the problem? > > The command is: > > ./objdir/sbin/mkelfImage -t bzImage-i386 --kernel=/home/sagivy/bzImage > --command-line="rw console=ttyS0,115200 root=/dev/ram0" > --initrd=/home/sagivy/initrd --output=/home/sagivy/bzImage.elf leave root=/dev/ram0 away in the parameters and say initrd=initrd instead. IIRC there was some check in Linux that it only looks for an initrd if there is a parameter saying that there is one. Stefan ___ Linuxbios mailing list [EMAIL PROTECTED] http://www.clustermatic.org/mailman/listinfo/linuxbios
RE: Kernel for linuxbios
Sorry for the late response. Are you using Linux 2.6.*. If so give initramfs a try. Here is a link to aid you in how: http://linuxfromscratch.org/pipermail/lfs-hackers/2004-June/001424.html Dave -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Sagiv Yefet Sent: Wednesday, October 13, 2004 8:10 AM To: Stefan Reinauer Cc: [EMAIL PROTECTED] Subject: RE: Kernel for linuxbios I tried to use initrd - same problem. Sagiv -Original Message- From: Stefan Reinauer [mailto:[EMAIL PROTECTED] Sent: Monday, October 11, 2004 11:21 AM To: Sagiv Yefet Cc: [EMAIL PROTECTED] Subject: Re: Kernel for linuxbios * Sagiv Yefet <[EMAIL PROTECTED]> [041011 11:06]: > > I add the console support and there is output. Thanks. > > My machine has no disks and I need initrd. So I took initrd from > Thinstation and build the elf file by the command : > > RAMDISK: Couldn't find valid RAM disk image starting at 0. > Freeing initrd memory: 11922k freed > Kernel panic: VFS: Unable to mount root fs on 01:00 use initrd, not ramdisk! Stefan ___ Linuxbios mailing list [EMAIL PROTECTED] http://www.clustermatic.org/mailman/listinfo/linuxbios ___ Linuxbios mailing list [EMAIL PROTECTED] http://www.clustermatic.org/mailman/listinfo/linuxbios
RE: testbios loops?
I now have it working. I had to use a ... Gasp dos tool to help me! I suspected the linux dd wasn't retrieving the rom correctly For some reason either linux didn't copy the rom correctly Or it got modified after linux ran or what have you. So I found this nvflash utility from http://www.nvplanet.com/modules.php?name=Downloads&d_op=viewdownload&cid =10 I had to a dos boot disk. I picked 6.22 from: http://www.bootdisk.com/bootdisk.htm Removed all things qbasic to free up some room. Then copied over the nvflash utilities and rebooted A windows machine with said graphics card. Ran the utility nvflash --save nv6800w.rom (remember 8.3 format here) I then compared the linux retrieved image with the nvflash Image and they were slightly different at first by a byte or two, Then got progressively different as the file went on. So what this means is the dd method might not always work, but this Dos method did do the trick. Good news is it seems to work with A lot of nvidia roms:) Hope this helps. Thanks, Dave:) -Original Message- From: Dave Aubin Sent: Friday, October 08, 2004 1:36 PM To: Dave Aubin; Li-Ta Lo Cc: LinuxBIOS Subject: RE: testbios loops? Update... Well the last complete trace I sent was due to only having 32k And not 64k of the image. Weird is that iomem shows linux as using Only 0xc to 0xc7fff which is 32k. Now when I excute a 64k Code size it eventually loops, but takes a bit longer. What's Really funny is that appears the image is doing nothing of interest. Here is a snap shot of what I mean. It just keeps adding BX+SI which Are both 0. Any ideas??? Thanks, Dave running file vgabios-1k.rom No base specified. defaulting to 0xc No initial code segment specified. defaulting to 0xc000 No initial instruction pointer specified. defaulting to 0x0003 Switching to single step mode. AX=00ff BX= CX= DX=0080 SP=fff8 BP= SI= DI= DS=0040 ES= SS=0030 CS=c000 IP=0005 NV UP DI PL NZ NA PO NC c000:0003 eb4bJMP 50 AX=00ff BX= CX= DX=0080 SP=fff8 BP= SI= DI= DS=0040 ES= SS=0030 CS=c000 IP=0053 NV UP DI PL NZ NA PO NC c000:0050 e9bcd4 JMP d50f AX=00ff BX= CX= DX=0080 SP=fff8 BP= SI= DI= DS=0040 ES= SS=0030 CS=c000 IP=d511 NV UP DI PL NZ NA PO NC c000:d50f 1818SBB [BX+SI],BL AX=00ff BX= CX= DX=0080 SP=fff8 BP= SI= DI= DS=0040 ES= SS=0030 CS=c000 IP=d513 NV UP DI PL ZR NA PE NC c000:d511 ADD [BX+SI],AL AX=00ff BX= CX= DX=0080 SP=fff8 BP= SI= DI= DS=0040 ES= SS=0030 CS=c000 IP=d516 NV UP DI NG NZ NA PE NC c000:d513 3366cc XOR SP,-52[BP] AX=00ff BX= CX= DX=0080 SP=fff8 BP= SI= DI= DS=0040 ES= SS=0030 CS=c000 IP=d517 NV UP DI NG NZ NA PO NC c000:d516 66 DATA: AX=00ff BX= CX= DX=0080 SP=fff8 BP= SI= DI= DS=0040 ES= SS=0030 CS=c000 IP=d519 NV UP DI NG NZ NA PO NC c000:d517 3300XOR EAX,[BX+SI] AX= BX= CX= DX=0080 SP=fff8 BP= SI= DI= DS=0040 ES= SS=0030 CS=c000 IP=d51b NV UP DI PL ZR NA PE NC c000:d519 ADD [BX+SI],AL AX= BX= CX= DX=0080 SP=fff8 BP= SI= DI= DS=0040 ES= SS=0030 CS=c000 IP=d51c NV UP DI NG NZ NA PE NC c000:d51b cc INT 3 int3 vector at 0 AX= BX= CX= DX=0080 SP=fff2 BP= SI= DI= DS=0040 ES= SS=0030 CS= IP=0002 NV UP DI NG NZ NA PE NC : ADD [BX+SI],AL AX= BX= CX= DX=0080 SP=fff2 BP= SI= DI= DS=0040 ES= SS=0030 CS= IP=0004 NV UP DI NG NZ NA PE NC :0002 ADD [BX+SI],AL AX= BX= CX= DX=0080 SP=fff2 BP= SI= DI= DS=0040 ES= SS=0030 CS= IP=0006 NV UP DI NG NZ NA PE NC :0004 ADD [BX+SI],AL AX= BX= CX= DX=0080 SP=fff2 BP= SI= DI= DS=0040 ES= SS=0030 CS= IP=0008 NV UP DI NG NZ NA PE NC :0006 ADD [BX+SI],AL AX= BX= CX= DX=0080 SP=fff2 BP= SI= DI= DS=0040 ES= SS=0030 CS= IP=000a NV UP DI NG NZ NA PE NC :0008 ADD [BX+SI],AL AX= BX= CX= DX=0080 SP=fff2 BP= SI= DI= DS=0040 ES= SS=0030 CS= IP=000c NV UP DI NG NZ NA PE NC :000a ADD [BX+SI],AL AX= BX= CX
RE: testbios loops?
0 CX= DX=0080 SP=fff2 BP= SI= DI= DS=0040 ES= SS=0030 CS= IP=010a NV UP DI NG NZ NA PE NC :0108 ADD [BX+SI],AL AX= BX= CX= DX=0080 SP=fff2 BP= SI= DI= DS=0040 ES= SS=0030 CS= IP=010c NV UP DI NG NZ NA PE NC :010a ADD [BX+SI],AL AX= BX= CX= DX=0080 SP=fff2 BP= SI= DI= DS=0040 ES= SS=0030 CS= IP=010e NV UP DI NG NZ NA PE NC :010c ADD [BX+SI],AL AX= BX= CX= DX=0080 SP=fff2 BP= SI= DI= DS=0040 ES= SS=0030 CS= IP=0110 NV UP DI NG NZ NA PE NC :010e ADD [BX+SI],AL AX= BX= CX= DX=0080 SP=fff2 BP= SI= DI= DS=0040 ES= SS=0030 CS= IP=0112 NV UP DI NG NZ NA PE NC :0110 ADD [BX+SI],AL AX= BX= CX= DX=0080 SP=fff2 BP= SI= DI= DS=0040 ES= SS=0030 CS= IP=0114 NV UP DI NG NZ NA PE NC :0112 ADD [BX+SI],AL AX= BX= CX= DX=0080 SP=fff2 BP= SI= DI= DS=0040 ES= SS=0030 CS= IP=0116 NV UP DI NG NZ NA PE NC :0114 ADD [BX+SI],AL AX= BX= CX= DX=0080 SP=fff2 BP= SI= DI= DS=0040 ES= SS=0030 CS= IP=0118 NV UP DI NG NZ NA PE NC :0116 ADD [BX+SI],AL AX= BX= CX= DX=0080 SP=fff2 BP= SI= DI= DS=0040 ES= SS=0030 CS= IP=011a NV UP DI NG NZ NA PE NC :0118 ADD [BX+SI],AL AX= BX= CX= DX=0080 SP=fff2 BP= SI= DI= DS=0040 ES= SS=0030 CS= IP=011c NV UP DI NG NZ NA PE NC :011a ADD [BX+SI],AL AX= BX= CX= DX=0080 SP=fff2 BP= SI= DI= DS=0040 ES= SS=0030 CS= IP=011e NV UP DI NG NZ NA PE NC :011c ADD [BX+SI],AL AX= BX= CX= DX=0080 SP=fff2 BP= SI= DI= DS=0040 ES= SS=0030 CS= IP=0120 NV UP DI NG NZ NA PE NC :011e ADD [BX+SI],AL AX= BX= CX= DX=0080 SP=fff2 BP= SI= DI= DS=0040 ES= SS=0030 CS= IP=0122 NV UP DI NG NZ NA PE NC :0120 ADD [BX+SI],AL AX= BX= CX= DX=0080 SP=fff2 BP= SI= DI= DS=0040 ES= SS=0030 CS= IP=0124 NV UP DI NG NZ NA PE NC :0122 ADD [BX+SI],AL AX= BX= CX= DX=0080 SP=fff2 BP= SI= DI= DS=0040 ES= SS=0030 CS= IP=0126 NV UP DI NG NZ NA PE NC :0124 ADD [BX+SI],AL AX= BX= CX= DX=0080 SP=fff2 BP= SI= DI= DS=0040 ES= SS=0030 CS= IP=0128 NV UP DI NG NZ NA PE NC :0126 ADD [BX+SI],AL AX= BX= CX= DX=0080 SP=fff2 BP= SI= DI= DS=0040 ES= SS=0030 CS= IP=012a NV UP DI NG NZ NA PE NC :0128 ADD [BX+SI],AL AX= BX= CX= DX=0080 SP=fff2 BP= SI= DI= DS=0040 ES= SS=0030 CS= IP=012c NV UP DI NG NZ NA PE NC :012a ADD [BX+SI],AL AX= BX= CX= DX=0080 SP=fff2 BP= SI= DI= DS=0040 ES= SS=0030 CS= IP=012e NV UP DI NG NZ NA PE NC :012c ADD [BX+SI],AL AX= BX= CX= DX=0080 SP=fff2 BP= SI= DI= DS=0040 ES= SS=0030 CS= IP=0130 NV UP DI NG NZ NA PE NC -Original Message- From: Dave Aubin Sent: Friday, October 08, 2004 11:40 AM To: 'Li-Ta Lo' Cc: LinuxBIOS Subject: RE: testbios loops? Here is a dump of the following: /usr/bin/testbios -s 65536 -d 0x200 --abseg /dev/mem /usr/bin/nv6800gt.bin -t I slightly different behavior with this incantation. Normally I leave off The -d 0x200. My device is located off of 2:0:0. running file /usr/bin/nv6800gt.bin No base specified. defaulting to 0xc No initial code segment specified. defaulting to 0xc000 No initial instruction pointer specified. defaulting to 0x0003 Switching to single step mode. AX=0200 BX= CX= DX=0080 SP=fff8 BP= SI= DI= DS=0040 ES= SS=0030 CS=c000 IP=0005 NV UP DI PL NZ NA PO NC c000:0003 eb4bJMP 50 AX=0200 BX= CX= DX=0080 SP=fff8 BP= SI= DI= DS=00
RE: testbios loops?
DX=03d4 SP=ffca BP= SI= DI= DS=0040 ES= SS=0030 CS=c000 IP=15ca NV UP DI PL ZR NA PE NC c000:15c7 e83002 CALL 17fa AX=fe2c BX=0044 CX= DX=03d4 SP=ffc8 BP= SI= DI= DS=0040 ES= SS=0030 CS=c000 IP=17fb NV UP DI PL ZR NA PE NC c000:17fa 50 PUSH AX AX=fe2c BX=0044 CX= DX=03d4 SP=ffc6 BP= SI= DI= DS=0040 ES= SS=0030 CS=c000 IP=17fe NV UP DI PL ZR NA PE NC -Original Message- From: Li-Ta Lo [mailto:[EMAIL PROTECTED] Sent: Friday, October 08, 2004 11:14 AM To: Dave Aubin Cc: LinuxBIOS Subject: RE: testbios loops? On Fri, 2004-10-08 at 09:04, Dave Aubin wrote: > Hi, > > Oh it does. I just left that snippet out. It starts at the correct > place:) > Then there is a big problem. The code just to somewhere that is not code (). Can you send more messages ? Ollie > -Original Message- > From: Li-Ta Lo [mailto:[EMAIL PROTECTED] > Sent: Friday, October 08, 2004 11:02 AM > To: Dave Aubin > Cc: LinuxBIOS > Subject: RE: testbios loops? > > On Fri, 2004-10-08 at 08:58, Dave Aubin wrote: > > Hi, > > Why it starts from c000:fffd ? It should starts from c000:0003 > > Ollie > > > > > It will first do this (I'm using the testbios -t option) > > c000:fffd ADD [BX+SI],AL > > AX=0200 BX= CX= DX=0080 SP=fff8 BP= SI= > > DI= > > DS=0040 ES= SS=0030 CS=c000 IP=0002 NV UP DI PL ZR > NA > > PE NC > > c000: 00 ADD -86[DI],DL > > AX=0200 BX= CX= DX=0080 SP=fff8 BP= SI= > > DI= > > DS=0040 ES= SS=0030 CS=c000 IP=0004 NV UP DI NG NZ > NA > > PO NC > > c000:0002 74ebJZffef > > AX=0200 BX= CX= DX=0080 SP=fff8 BP= SI= > > DI= > > DS=0040 ES= SS=0030 CS=c000 IP=0005 NV UP DI NG NZ > NA > > PO NC > > c000:0004 4b DEC BX > > AX=0200 BX= CX= DX=0080 SP=fff8 BP= SI= > > DI= > > DS=0040 ES= SS=0030 CS=c000 IP=0006 NV UP DI NG NZ > AC > > PE NC > > c000:0005 37 AAA > > AX=0306 BX= CX= DX=0080 SP=fff8 BP= SI= > > DI= > > DS=0040 ES= SS=0030 CS=c000 IP=0008 NV UP DI PL NZ > AC > > PE CY > > > > Then it will do this: > > c000:0137 0d0a00 ORAX,a > > AX=debf BX= CX=0335 DX=0080 SP=ffef BP= SI=0004 > > DI=0002 > > DS=0040 ES= SS=0030 CS=c000 IP=013c NV UP DI NG NZ > NA > > PO NC > > c000:013a ADD [BX+SI],AL > > AX=debf BX= CX=0335 DX=0080 SP=ffef BP= SI=0004 > > DI=0002 > > DS=0040 ES= SS=0030 CS=c000 IP=013f NV UP DI NG NZ > AC > > PO CY > > c000:013c ba9198 MOV DX,9891 > > AX=debf BX= CX=0335 DX=9891 SP=ffef BP= SI=0004 > > DI=0002 > > DS=0040 ES= SS=0030 CS=c000 IP=0140 NV UP DI NG NZ > AC > > PO CY > > c000:013f 96 XCHG AX,SI > > AX=0004 BX= CX=0335 DX=9891 SP=ffef BP= SI=debf > > DI=0002 > > DS=0040 ES= SS=0030 CS=c000 IP=0141 NV UP DI NG NZ > AC > > PO CY > > c000:0140 91 XCHG AX,CX > > AX=0335 BX= CX=0004 DX=9891 SP=ffef BP= SI=debf > > DI=0002 > > DS=0040 ES= SS=0030 CS=c000 IP=0146 NV UP DI NG NZ > AC > > PO CY > > c000:0141 9a9a8d9691 CALL 9196:8d9a > > AX=0335 BX= CX=0004 DX=9891 SP=ffeb BP= SI=debf > > DI=0002 > > DS=0040 ES= SS=0030 CS=9196 IP=8d9c NV UP DI NG NZ > AC > > PO CY > > 9196:8d9a ADD [BX+SI],AL > > AX=0335 BX= CX=0004 DX=9891 SP=ffeb BP= SI=debf > > DI=0002 > > DS=0040 ES= SS=0030 CS=9196 IP=8d9e NV UP DI PL NZ > NA > > PE NC > > 9196:8d9c ADD [BX+SI],AL > > AX=0335 BX= CX=0004 DX=9891 SP=ffeb BP= SI=debf > > DI=0002 > > DS=0040 ES= SS=0030 CS=9196 IP=8da0 NV UP DI PL NZ > NA > > PE NC > > > > I'm still looking for the openbios utility. So far found broken > > links:( I can get some other bios to work, but they appear to be &g
RE: testbios loops?
Starting up X causes bad things, ie hang! I'm building the log now and will send in separate message. Thanks, Dave -Original Message- From: Richard Smith [mailto:[EMAIL PROTECTED] Sent: Friday, October 08, 2004 11:15 AM To: [EMAIL PROTECTED]; Dave Aubin Cc: [EMAIL PROTECTED] Subject: Re: testbios loops? Stefan Reinauer wrote: > * Dave Aubin <[EMAIL PROTECTED]> [041008 16:35]: >> I went back to trying to get the Nvida 6800gt card's bios, but still >>even with dd -if=/dev/mem of=vgabios.rom skip=786432 bs=1 count=32768 >>I get the same binary as dd -if=/dev/mem of=vgabios.rom skip=1536 >>count=64. > > Does the bios have a valid pci option rom signature? (55aa plus the > other stuff, see romheaders utility in the openbios tree) Or use hd and see whats at 0xc. Also fire up X and look at your log. It outputs a lot of good info. -- Richard A. Smith ___ Linuxbios mailing list [EMAIL PROTECTED] http://www.clustermatic.org/mailman/listinfo/linuxbios
RE: testbios loops?
Hi, Oh it does. I just left that snippet out. It starts at the correct place:) -Original Message- From: Li-Ta Lo [mailto:[EMAIL PROTECTED] Sent: Friday, October 08, 2004 11:02 AM To: Dave Aubin Cc: LinuxBIOS Subject: RE: testbios loops? On Fri, 2004-10-08 at 08:58, Dave Aubin wrote: > Hi, Why it starts from c000:fffd ? It should starts from c000:0003 Ollie > > It will first do this (I'm using the testbios -t option) > c000:fffd ADD [BX+SI],AL > AX=0200 BX= CX= DX=0080 SP=fff8 BP= SI= > DI= > DS=0040 ES= SS=0030 CS=c000 IP=0002 NV UP DI PL ZR NA > PE NC > c000: 00 ADD -86[DI],DL > AX=0200 BX= CX= DX=0080 SP=fff8 BP= SI= > DI= > DS=0040 ES= SS=0030 CS=c000 IP=0004 NV UP DI NG NZ NA > PO NC > c000:0002 74ebJZffef > AX=0200 BX= CX= DX=0080 SP=fff8 BP= SI= > DI= > DS=0040 ES= SS=0030 CS=c000 IP=0005 NV UP DI NG NZ NA > PO NC > c000:0004 4b DEC BX > AX=0200 BX= CX= DX=0080 SP=fff8 BP= SI= > DI= > DS=0040 ES= SS=0030 CS=c000 IP=0006 NV UP DI NG NZ AC > PE NC > c000:0005 37 AAA > AX=0306 BX= CX= DX=0080 SP=fff8 BP= SI= > DI= > DS=0040 ES= SS=0030 CS=c000 IP=0008 NV UP DI PL NZ AC > PE CY > > Then it will do this: > c000:0137 0d0a00 ORAX,a > AX=debf BX= CX=0335 DX=0080 SP=ffef BP= SI=0004 > DI=0002 > DS=0040 ES= SS=0030 CS=c000 IP=013c NV UP DI NG NZ NA > PO NC > c000:013a ADD [BX+SI],AL > AX=debf BX= CX=0335 DX=0080 SP=ffef BP= SI=0004 > DI=0002 > DS=0040 ES= SS=0030 CS=c000 IP=013f NV UP DI NG NZ AC > PO CY > c000:013c ba9198 MOV DX,9891 > AX=debf BX= CX=0335 DX=9891 SP=ffef BP= SI=0004 > DI=0002 > DS=0040 ES= SS=0030 CS=c000 IP=0140 NV UP DI NG NZ AC > PO CY > c000:013f 96 XCHG AX,SI > AX=0004 BX= CX=0335 DX=9891 SP=ffef BP= SI=debf > DI=0002 > DS=0040 ES= SS=0030 CS=c000 IP=0141 NV UP DI NG NZ AC > PO CY > c000:0140 91 XCHG AX,CX > AX=0335 BX= CX=0004 DX=9891 SP=ffef BP= SI=debf > DI=0002 > DS=0040 ES= SS=0030 CS=c000 IP=0146 NV UP DI NG NZ AC > PO CY > c000:0141 9a9a8d9691 CALL 9196:8d9a > AX=0335 BX= CX=0004 DX=9891 SP=ffeb BP= SI=debf > DI=0002 > DS=0040 ES= SS=0030 CS=9196 IP=8d9c NV UP DI NG NZ AC > PO CY > 9196:8d9a ADD [BX+SI],AL > AX=0335 BX= CX=0004 DX=9891 SP=ffeb BP= SI=debf > DI=0002 > DS=0040 ES= SS=0030 CS=9196 IP=8d9e NV UP DI PL NZ NA > PE NC > 9196:8d9c ADD [BX+SI],AL > AX=0335 BX= CX=0004 DX=9891 SP=ffeb BP= SI=debf > DI=0002 > DS=0040 ES= SS=0030 CS=9196 IP=8da0 NV UP DI PL NZ NA > PE NC > > I'm still looking for the openbios utility. So far found broken > links:( I can get some other bios to work, but they appear to be > flacky. I really think I should be using the one that came programmed > on the board. > > Thanks, > Dave > > -Original Message- > From: Li-Ta Lo [mailto:[EMAIL PROTECTED] > Sent: Friday, October 08, 2004 10:53 AM > To: Dave Aubin > Cc: LinuxBIOS > Subject: Re: testbios loops? > > On Fri, 2004-10-08 at 08:35, Dave Aubin wrote: > > Hi, > > > > I went back to trying to get the Nvida 6800gt card's bios, but > > still > > > even with dd -if=/dev/mem of=vgabios.rom skip=786432 bs=1 > > count=32768 I get the same binary as dd -if=/dev/mem of=vgabios.rom > > skip=1536 count=64. > > I used dhex (free util) to verify they are the same. > > What happens when I run them trough testbios is that once it is > > done > > > programming 0xc7fff it jump to 0x9 something or other and the video > > bios isn't programmed correctly. > > > What do you mean by 'programming oxc7ff it jump to 0x9' ? > > Ollie > > > ___ Linuxbios mailing list [EMAIL PROTECTED] http://www.clustermatic.org/mailman/listinfo/linuxbios
RE: testbios loops?
I got it and here are the results: [EMAIL PROTECTED]:~/tmp/utils> ./romheaders /common/home/daubin/vgabios-1.rom Image 1: PCI Expansion ROM Header: Signature: 0x55aa (Ok) CPU unique data: 0x74 0xeb 0x4b 0x37 0x34 0x30 0x30 0xe9 0x4c 0x19 0x77 0xcc 0x56 0x49 0x44 0x45 Pointer to PCI Data Structure: 0x0090 PCI Data Structure: Signature: 'PCIR' (Ok) Vendor ID: 0x10de Device ID: 0x0045 Reserved: 0x PCI Data Structure Length: 0x0018 (24 bytes) PCI Data Structure Revision: 0x00 Class Code: 0x000300 (VGA Display) Image Length: 0x0074 blocks (59392 bytes) Revision Level of Code/Data: 0x0001 Code Type: 0x00 (Intel x86) Indicator: 0x80 (last image in rom) Reserved: 0x Platform specific data for x86 compliant option rom: Initialization Size: 0x74 (59392 bytes) Entry point for INIT function: 0x50 Can you please help explain this to me:) Thanks, Dave:) -Original Message- From: Stefan Reinauer [mailto:[EMAIL PROTECTED] Sent: Friday, October 08, 2004 10:49 AM To: Dave Aubin Cc: [EMAIL PROTECTED] Subject: Re: testbios loops? * Dave Aubin <[EMAIL PROTECTED]> [041008 16:35]: > Hi, > > I went back to trying to get the Nvida 6800gt card's bios, but still > even with dd -if=/dev/mem of=vgabios.rom skip=786432 bs=1 count=32768 > I get the same binary as dd -if=/dev/mem of=vgabios.rom skip=1536 > count=64. Does the bios have a valid pci option rom signature? (55aa plus the other stuff, see romheaders utility in the openbios tree) Stefan ___ Linuxbios mailing list [EMAIL PROTECTED] http://www.clustermatic.org/mailman/listinfo/linuxbios
RE: testbios loops?
Hi, It will first do this (I'm using the testbios -t option) c000:fffd ADD [BX+SI],AL AX=0200 BX= CX= DX=0080 SP=fff8 BP= SI= DI= DS=0040 ES= SS=0030 CS=c000 IP=0002 NV UP DI PL ZR NA PE NC c000: 00 ADD -86[DI],DL AX=0200 BX= CX= DX=0080 SP=fff8 BP= SI= DI= DS=0040 ES= SS=0030 CS=c000 IP=0004 NV UP DI NG NZ NA PO NC c000:0002 74ebJZffef AX=0200 BX= CX= DX=0080 SP=fff8 BP= SI= DI= DS=0040 ES= SS=0030 CS=c000 IP=0005 NV UP DI NG NZ NA PO NC c000:0004 4b DEC BX AX=0200 BX= CX= DX=0080 SP=fff8 BP= SI= DI= DS=0040 ES= SS=0030 CS=c000 IP=0006 NV UP DI NG NZ AC PE NC c000:0005 37 AAA AX=0306 BX= CX= DX=0080 SP=fff8 BP= SI= DI= DS=0040 ES= SS=0030 CS=c000 IP=0008 NV UP DI PL NZ AC PE CY Then it will do this: c000:0137 0d0a00 ORAX,a AX=debf BX= CX=0335 DX=0080 SP=ffef BP= SI=0004 DI=0002 DS=0040 ES= SS=0030 CS=c000 IP=013c NV UP DI NG NZ NA PO NC c000:013a ADD [BX+SI],AL AX=debf BX= CX=0335 DX=0080 SP=ffef BP= SI=0004 DI=0002 DS=0040 ES= SS=0030 CS=c000 IP=013f NV UP DI NG NZ AC PO CY c000:013c ba9198 MOV DX,9891 AX=debf BX= CX=0335 DX=9891 SP=ffef BP= SI=0004 DI=0002 DS=0040 ES= SS=0030 CS=c000 IP=0140 NV UP DI NG NZ AC PO CY c000:013f 96 XCHG AX,SI AX=0004 BX= CX=0335 DX=9891 SP=ffef BP= SI=debf DI=0002 DS=0040 ES= SS=0030 CS=c000 IP=0141 NV UP DI NG NZ AC PO CY c000:0140 91 XCHG AX,CX AX=0335 BX= CX=0004 DX=9891 SP=ffef BP= SI=debf DI=0002 DS=0040 ES= SS=0030 CS=c000 IP=0146 NV UP DI NG NZ AC PO CY c000:0141 9a9a8d9691 CALL 9196:8d9a AX=0335 BX= CX=0004 DX=9891 SP=ffeb BP= SI=debf DI=0002 DS=0040 ES= SS=0030 CS=9196 IP=8d9c NV UP DI NG NZ AC PO CY 9196:8d9a ADD [BX+SI],AL AX=0335 BX= CX=0004 DX=9891 SP=ffeb BP= SI=debf DI=0002 DS=0040 ES= SS=0030 CS=9196 IP=8d9e NV UP DI PL NZ NA PE NC 9196:8d9c ADD [BX+SI],AL AX=0335 BX= CX=0004 DX=9891 SP=ffeb BP= SI=debf DI=0002 DS=0040 ES= SS=0030 CS=9196 IP=8da0 NV UP DI PL NZ NA PE NC I'm still looking for the openbios utility. So far found broken links:( I can get some other bios to work, but they appear to be flacky. I really think I should be using the one that came programmed on the board. Thanks, Dave -Original Message- From: Li-Ta Lo [mailto:[EMAIL PROTECTED] Sent: Friday, October 08, 2004 10:53 AM To: Dave Aubin Cc: LinuxBIOS Subject: Re: testbios loops? On Fri, 2004-10-08 at 08:35, Dave Aubin wrote: > Hi, > > I went back to trying to get the Nvida 6800gt card's bios, but still > even with dd -if=/dev/mem of=vgabios.rom skip=786432 bs=1 count=32768 > I get the same binary as dd -if=/dev/mem of=vgabios.rom skip=1536 > count=64. > I used dhex (free util) to verify they are the same. > What happens when I run them trough testbios is that once it is done > programming 0xc7fff it jump to 0x9 something or other and the video > bios isn't programmed correctly. What do you mean by 'programming oxc7ff it jump to 0x9' ? Ollie ___ Linuxbios mailing list [EMAIL PROTECTED] http://www.clustermatic.org/mailman/listinfo/linuxbios
testbios loops?
Hi, I went back to trying to get the Nvida 6800gt card's bios, but still even with dd -if=/dev/mem of=vgabios.rom skip=786432 bs=1 count=32768 I get the same binary as dd -if=/dev/mem of=vgabios.rom skip=1536 count=64. I used dhex (free util) to verify they are the same. What happens when I run them trough testbios is that once it is done programming 0xc7fff it jump to 0x9 something or other and the video bios isn't programmed correctly. My iomem looks like this: -0009fbff : System RAM0009fc00-0009 : reserved000a-000b : Video RAM area000c-000c7fff : Video ROM000f-000f : System ROM0010-1ffe : System RAM 0010-002b00be : Kernel code 002b00bf-003d78bf : Kernel data1fff-1fffefff : ACPI Tables1000-1fff : ACPI Non-volatile Storagec9f0-c9ff : PCI Bus #01ca00-ca0f : PCI Bus #02ca10-ca1f : PCI Bus #03 Any ideas as to what is wrong? Thanks, Dave:)
RE: Adding a PCI device that doesn't exist (yet)
Very nice:)
Thanks you:):):)
-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of [EMAIL PROTECTED]
Sent: Wednesday, October 06, 2004 2:35 PM
To: Jay Miller
Cc: Ronald G. Minnich; YhLu; [EMAIL PROTECTED]
Subject: Re: Adding a PCI device that doesn't exist (yet)
Jay Miller wrote:
> Thanks Ty, that's exactly what we're looking for. The de-allocation
> wouldn't be an issue as we would be re-programming on the reboot
anyway.
>
> Did you use the proc_pci_attach_device() mechanism?
>
> Cheers,
>
> Jay Miller
> 781-229-7812x117
> Actuality Systems, Inc.
> [EMAIL PROTECTED]
>
>
> -Original Message-
> From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]
> Sent: Wednesday, October 06, 2004 1:52 PM
> To: Jay Miller
> Cc: Ronald G. Minnich; YhLu; [EMAIL PROTECTED]
> Subject: Re: Adding a PCI device that doesn't exist (yet)
>
> Hopping in mid-thread here so I may have the context wrong:
>
> I have succeeded at programming the FPGA to create a PCI device after
> the boot process. I was then able to have the device driver add the
> device to the pci device table and get resources allocated for it and
> get it paired up with the alread loaded device driver.
>
> I did not figure out how to de-allocate/de-register such that I could
> cleanely re-program the FPGA without a re-boot.
>
> Is this relevant?
>
> Cheers!
> Ty
It is only a specific variation of this device that needed this code so
it is hacked in by conditionally including the header file below into a
.c file. Crufty code organization, but now you know.
This was made to work by having user level initialization scripts
program the FPGA before loading the device driver. The first thing that
the device driver did in its init function was call the function below.
This is working code as it sits. The things like
"PCI_VENDOR_ID_IROBOT" are our own local hacks and defines. Things like
"list_for_each_safe() come from the kernel headers. I think that
was all I needed for this part of the code but it might be
dependent on others as well.
I'd be happy to attempt to answer specific questions, but I think
everything needed is here. I figured this out thought a lot of grepping
and "use the source Luke!".
Cheers!
Ty
===
/*
* neolink2.h
*/
#define PCI_FNBUS 0
#define PCI_FNSLOT 16
#define PCI_FNFUNC 0
static int __init neolink2_init(void)
{
struct list_head *list, *list_tmp;
struct pci_bus *bus;
struct pci_dev dev, *dev1;
if (pci_find_device(PCI_VENDOR_ID_IROBOT, PCI_DEVICE_ID_IROBOT_FN2A,
NULL)) {
printk("%6d:%s:%s() - Device is already initialized\n",
__LINE__, __FILE__, __FUNCTION__);
return 0;
}
list_for_each_safe(list, list_tmp, &pci_root_buses) {
bus = pci_bus_b(list);
if (bus->number == PCI_FNBUS) {
memset(&dev, 0, sizeof(dev));
dev.bus = bus;
dev.sysdata = bus->sysdata;
dev.devfn = PCI_DEVFN(PCI_FNSLOT, PCI_FNFUNC);
dev1 = pci_scan_slot(&dev);
if (!dev1) {
printk("%6d:%s:%s() - No device found\n",
__LINE__, __FILE__, __FUNCTION__);
return -ENODEV;
}
else {
printk("%6d:%s:%s() - Found device %s\n",
__LINE__, __FILE__, __FUNCTION__, dev1->name);
pci_set_power_state(dev1, 0);
pci_assign_resource(dev1, 0);
pci_enable_device(dev1);
// pci_announce_device_to_drivers(dev1);
return 0;
}
break;
}
}
printk("%6d:%s:%s() - Bus %d found\n",
__LINE__, __FILE__, __FUNCTION__, PCI_FNBUS);
return -ENODEV;
}
=
--
Tyson D Sawyer iRobot Corporation
Lead Systems Engineer Government & Industrial Robotics
[EMAIL PROTECTED] Robots for the Real World
781-345-0200 ext 3329 http://www.irobot.com
___
Linuxbios mailing list
[EMAIL PROTECTED]
http://www.clustermatic.org/mailman/listinfo/linuxbios
___
Linuxbios mailing list
[EMAIL PROTECTED]
http://www.clustermatic.org/mailman/listinfo/linuxbios
RE: Adding a PCI device that doesn't exist (yet)
Hi Ty, Please tell:) What approach did you use to create the pci Device after boot? Thanks, Dave:) -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of [EMAIL PROTECTED] Sent: Wednesday, October 06, 2004 1:52 PM To: Jay Miller Cc: Ronald G. Minnich; YhLu; [EMAIL PROTECTED] Subject: Re: Adding a PCI device that doesn't exist (yet) Hopping in mid-thread here so I may have the context wrong: I have succeeded at programming the FPGA to create a PCI device after the boot process. I was then able to have the device driver add the device to the pci device table and get resources allocated for it and get it paired up with the alread loaded device driver. I did not figure out how to de-allocate/de-register such that I could cleanely re-program the FPGA without a re-boot. Is this relevant? Cheers! Ty Jay Miller wrote: > Thanks for your help. Certainly that's not ideal, but it may turn out > to be our only option. > > Currently I'm investigating using proc_pci_attach_device() at the > kernel level to add the device from the driver module > init(post-program), but it's not looking promising. > > Thanks, > > Jay Miller > 781-229-7812x117 > Actuality Systems, Inc. > [EMAIL PROTECTED] > > > -Original Message- > From: Ronald G. Minnich [mailto:[EMAIL PROTECTED] > Sent: Wednesday, October 06, 2004 12:23 PM > To: YhLu > Cc: Jay Miller; [EMAIL PROTECTED] > Subject: RE: Adding a PCI device that doesn't exist (yet) > > > > On Tue, 5 Oct 2004, YhLu wrote: > > >>Can you for the FPGA programming in the auto.c and issue an soft_reset > > in > >>auto.c? > > > I think this can work with the current mechanisms. You need to have > your > > chip programmed pre-pci-scan, and the current config mechanism > supports that fine. > > > Is this V1 or V2, I forget. > > ron > ___ > Linuxbios mailing list > [EMAIL PROTECTED] > http://www.clustermatic.org/mailman/listinfo/linuxbios -- Tyson D Sawyer iRobot Corporation Lead Systems Engineer Government & Industrial Robotics [EMAIL PROTECTED] Robots for the Real World 781-345-0200 ext 3329 http://www.irobot.com ___ Linuxbios mailing list [EMAIL PROTECTED] http://www.clustermatic.org/mailman/listinfo/linuxbios ___ Linuxbios mailing list [EMAIL PROTECTED] http://www.clustermatic.org/mailman/listinfo/linuxbios
RE: Adding a PCI device that doesn't exist (yet)
Yes, hotplug in 2.6 would be excellent, but in order to Make the device hotplug it needs to show up the /sys/bus/pci... Power entry. I'm not sure how to make that happen. If it did then all things would be great. Thanks, Dave -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Ronald G. Minnich Sent: Wednesday, October 06, 2004 1:23 PM To: Jay Miller Cc: YhLu; [EMAIL PROTECTED] Subject: RE: Adding a PCI device that doesn't exist (yet) On Wed, 6 Oct 2004, Jay Miller wrote: > Thanks for your help. Certainly that's not ideal, but it may turn out > to be our only option. the reason being you don't want to embed the bitstream in linuxbios, right? Are you sure that you can't take advantage of the hotplug stuff in 2.6 for your device? Is your device a bridge or ... ron ___ Linuxbios mailing list [EMAIL PROTECTED] http://www.clustermatic.org/mailman/listinfo/linuxbios ___ Linuxbios mailing list [EMAIL PROTECTED] http://www.clustermatic.org/mailman/listinfo/linuxbios
RE: Testbios help with nvidia 6800Gt and simple how to
Ron, Please change my second example in the testbios faq to Reflect Richard's change please. Thanks, Dave:) -Original Message- From: Richard Smith [mailto:[EMAIL PROTECTED] Sent: Tuesday, October 05, 2004 4:01 PM To: Dave Aubin Cc: [EMAIL PROTECTED] Subject: Re: Testbios help with nvidia 6800Gt and simple how to Dave Aubin wrote: > the video card you wish to work under linux bios. > ii. From the command line enter: > dd if=/dev/mem of=vgabios.bin skip=1536 count=128 or > dd if=/dev/mem of=vgabios.bin bs=1k count=64 skip=786432 > Oop. Thinko. My line is jacked up. should be for bs=1k skip=768. skip=786432 is for a block size of 1 byte. -- Richard A. Smith ___ Linuxbios mailing list [EMAIL PROTECTED] http://www.clustermatic.org/mailman/listinfo/linuxbios
RE: Testbios help with nvidia 6800Gt and simple how to
ou could have a 32bit testbios executable made. Depending on your embedded environment you might want to have it built shared as the above example makes it static. Just remove -static-libgcc -static from the LDFLAGS on ./Makefile if you wish to have it built shared. 4. How to retrieve a good video bios A. There are sites that have video bios roms on their website. I know of this one for nvidia cards: http://whitebunny.demon.nl/hardware/chipset_nvidia.html B. However you should be able to retrieve your own video bios as well with linux. i. Boot up a machine with a commercial bios (not linux bios) with the video card you wish to work under linux bios. ii. From the command line enter: dd if=/dev/mem of=vgabios.bin skip=1536 count=128 or dd if=/dev/mem of=vgabios.bin bs=1k count=64 skip=786432 This assumes you card's bios is cached in 0xc. You can see where and how much your card's bios is using by doing a cat iomem | grep "Video ROM" a. dd Explained (man dd to learn more): 1. if is the location to retrieve from. 2. of is the output file (your rom image) 3. skip jumps n blocks where the default n is 512 bytes 4. count is how many blocks you wish to read 5. bs is the block size C. You now have a video bios image 5. How to use testbios A. Currently testbios only works from user space linux (10/4/04) B. Example from a linux command line or script enter the following to get your video bios programmed: ./testbios -s 65536 --abseg /dev/mem ./vgabios.bin i. Testbios explained a. -s how much of the video bios is there b. --abseg where would you like to write this (/dev/mem default) c. filename of video bios d. -d diag mode 1. How to get pci busdevfn A. lspci B. look for your video card Example: 2:00:00 2 (00 << 3) | 00 = 0x200 Example: 00:12.0: 0 (12 << 3) | 0 = 0x90 e. -t dump f. -c codesegment Where do you want to start, default is 0xc g. -b base Where do you want base to be default is 0xc000 h. -i instruction pointer usually left off as the default -----Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Dave Aubin Sent: Tuesday, October 05, 2004 2:22 PM To: Richard Smith Cc: [EMAIL PROTECTED] Subject: RE: Testbios help with nvidia 6800Gt and simple how to Hi, Thank you:) Yes, it was at 0xc-0xc7fff, which is only 32k. But the image I got from the windows tool was 64k (double 8000). Weird. I would like to stay away from window tools. The info you provided is nice. I wish there was a way for us To make a faq and we could add this to the testbios faq. There Is a lot of good info on the clustermatic list, but it is all Dispersed. Ron if I write a simple faq can you provide some mechanism to Allow updates to it? Thanks, Dave -Original Message----- From: Richard Smith [mailto:[EMAIL PROTECTED] Sent: Tuesday, October 05, 2004 2:16 PM To: Dave Aubin Cc: [EMAIL PROTECTED] Subject: Re: Testbios help with nvidia 6800Gt and simple how to Dave Aubin wrote: > It seems my dd returned an unusable binary. I found a good binary for > The nvidia card from here: > http://whitebunny.demon.nl/hardware/chipset_nvidia.html > I was wondering about your dd command that but I had not had a chance to respond yet. This is what I use: dd if=/dev/mem of=vbios.bin bs=1k count=64 skip=786432 That will rip the bios from 0x0c. You can verify that you actually have bios there with 'hd -s 0x0c -n 256 /dev/mem' in some cases it may be located at 0x0e rather than 0x0c. It should start with the 0x55aa (Little endian) or 0xaa55 (big endian) and futher on you should see some text identifying the bios. -- Richard A. Smith ___ Linuxbios mailing list [EMAIL PROTECTED] http://www.clustermatic.org/mailman/listinfo/linuxbios ___ Linuxbios mailing list [EMAIL PROTECTED] http://www.clustermatic.org/mailman/listinfo/linuxbios
RE: Testbios help with nvidia 6800Gt and simple how to
Hi, Thank you:) Yes, it was at 0xc-0xc7fff, which is only 32k. But the image I got from the windows tool was 64k (double 8000). Weird. I would like to stay away from window tools. The info you provided is nice. I wish there was a way for us To make a faq and we could add this to the testbios faq. There Is a lot of good info on the clustermatic list, but it is all Dispersed. Ron if I write a simple faq can you provide some mechanism to Allow updates to it? Thanks, Dave -Original Message- From: Richard Smith [mailto:[EMAIL PROTECTED] Sent: Tuesday, October 05, 2004 2:16 PM To: Dave Aubin Cc: [EMAIL PROTECTED] Subject: Re: Testbios help with nvidia 6800Gt and simple how to Dave Aubin wrote: > It seems my dd returned an unusable binary. I found a good binary for > The nvidia card from here: > http://whitebunny.demon.nl/hardware/chipset_nvidia.html > I was wondering about your dd command that but I had not had a chance to respond yet. This is what I use: dd if=/dev/mem of=vbios.bin bs=1k count=64 skip=786432 That will rip the bios from 0x0c. You can verify that you actually have bios there with 'hd -s 0x0c -n 256 /dev/mem' in some cases it may be located at 0x0e rather than 0x0c. It should start with the 0x55aa (Little endian) or 0xaa55 (big endian) and futher on you should see some text identifying the bios. -- Richard A. Smith ___ Linuxbios mailing list [EMAIL PROTECTED] http://www.clustermatic.org/mailman/listinfo/linuxbios
RE: Testbios help with nvidia 6800Gt and simple how to
Found the answer. It seems my dd returned an unusable binary. I found a good binary for The nvidia card from here: http://whitebunny.demon.nl/hardware/chipset_nvidia.html Seems they use a windows tool to retrieve the rom. Perhaps with this Card being so new this was the problem I was having. In any even My GeForce 6800GT now works under Linux bios:) Hope this helps someone. -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Dave Aubin Sent: Tuesday, October 05, 2004 10:01 AM To: [EMAIL PROTECTED] Subject: Testbios help with nvidia 6800Gt and simple how to Hello, I'm trying to get an nvidia 6800 Gt video card to work with linuxbios, but I am coming up short. Below is a mini how to with test bios and I did follow the steps, but it still doesn't work. Can someone please help me? I did the exact same steps with an nvidia5950 and it worked great. Is there something I am missing? Simple Test Bios How to. Purpose: Testbios provides an i386 emulator for programming the video bios. How to: First you need to retrieve the video bios from a machine booted up with a commercial bios running linux. Then once that is done you can execute the bios by using testbios. How to retrieve video bios 1. Boot up machine with commercial bios in to a linux environment 2. dd if=/dev/mem of=vgabios.bin skip=1536 count=128 from a terminal window A. This copies the video bios out of /dev/mem and places it in vgabios.bin How to execute testbios 1. Boot up machine with Linuxbios in to a linux environment 2. run testbios --abseg /dev/mem -s 65536 /root/vgabios.bin A. If working you should see the video bios welcome message on the screen Thanks, Dave:) ___ Linuxbios mailing list [EMAIL PROTECTED] http://www.clustermatic.org/mailman/listinfo/linuxbios ___ Linuxbios mailing list [EMAIL PROTECTED] http://www.clustermatic.org/mailman/listinfo/linuxbios
Testbios help with nvidia 6800Gt and simple how to
Hello, I'm trying to get an nvidia 6800 Gt video card to work with linuxbios, but I am coming up short. Below is a mini how to with test bios and I did follow the steps, but it still doesn't work. Can someone please help me? I did the exact same steps with an nvidia5950 and it worked great. Is there something I am missing? Simple Test Bios How to. Purpose: Testbios provides an i386 emulator for programming the video bios. How to: First you need to retrieve the video bios from a machine booted up with a commercial bios running linux. Then once that is done you can execute the bios by using testbios. How to retrieve video bios 1. Boot up machine with commercial bios in to a linux environment 2. dd if=/dev/mem of=vgabios.bin skip=1536 count=128 from a terminal window A. This copies the video bios out of /dev/mem and places it in vgabios.bin How to execute testbios 1. Boot up machine with Linuxbios in to a linux environment 2. run testbios --abseg /dev/mem -s 65536 /root/vgabios.bin A. If working you should see the video bios welcome message on the screen Thanks, Dave:) ___ Linuxbios mailing list [EMAIL PROTECTED] http://www.clustermatic.org/mailman/listinfo/linuxbios
RE: PCI IRQ tables
PCI IRQ specification:) http://www.microsoft.com/whdc/archive/pciirq.mspx -Original Message- From: Ronald G. Minnich [mailto:[EMAIL PROTECTED] Sent: Thursday, September 30, 2004 3:49 PM To: Dave Aubin Cc: [EMAIL PROTECTED] Subject: RE: PCI IRQ tables you can find the definition of $PIR standard at microsoft -- I always lose it, but google always finds it. ron ___ Linuxbios mailing list [EMAIL PROTECTED] http://www.clustermatic.org/mailman/listinfo/linuxbios
RE: PCI IRQ tables
Hi, No I think my question is even simpler than that. Where do I go to learn about the magic that is inside the mp and irq files? Thanks, Dave:) From: YhLu [mailto:[EMAIL PROTECTED] Sent: Thursday, September 30, 2004 3:14 PMTo: Dave Aubin; [EMAIL PROTECTED]Subject: RE: PCI IRQ tables SMP or single CPU? If SMP, and io apci is enabled, you may only focus on mptable.c and irq-tables.c may only contain device that point to the peer roots bus. YH From: Dave Aubin [mailto:[EMAIL PROTECTED] Sent: Thursday, September 30, 2004 11:53 AMTo: Dave Aubin; [EMAIL PROTECTED]Subject: RE: PCI IRQ tables Hi, I didn't get an answer from the previous post so I'll just simplify a little bit. Can someone point me to where I can learn more about the magic that makes the pci_irq files? Thanks, Dave:) From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Dave AubinSent: Wednesday, September 29, 2004 5:18 PMTo: [EMAIL PROTECTED]Subject: PCI IRQ tables Hi, What happens if the pci irq mapping is a mess? I know you can use getpir with a good bios, but what if you don't have one? Is there a way to get the pci irq mapping without a standard bios? If you had to do it by hand could you explain how it should be done? Thanks, Dave
RE: PCI IRQ tables
Hi, I didn't get an answer from the previous post so I'll just simplify a little bit. Can someone point me to where I can learn more about the magic that makes the pci_irq files? Thanks, Dave:) From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Dave AubinSent: Wednesday, September 29, 2004 5:18 PMTo: [EMAIL PROTECTED]Subject: PCI IRQ tables Hi, What happens if the pci irq mapping is a mess? I know you can use getpir with a good bios, but what if you don't have one? Is there a way to get the pci irq mapping without a standard bios? If you had to do it by hand could you explain how it should be done? Thanks, Dave
PCI IRQ tables
Hi, What happens if the pci irq mapping is a mess? I know you can use getpir with a good bios, but what if you don't have one? Is there a way to get the pci irq mapping without a standard bios? If you had to do it by hand could you explain how it should be done? Thanks, Dave
RE: Boot problem
I second Stefan's response. I was so stubborn at first to try This and then it helped me so much! So please try this or Netconsole. I suspect your kernel could not mount the file System you specified. If you try the above methods you should See exactly what failed. I think... FYI Netconsole link: http://technocrat.net/article.pl?sid=04/08/14/0236245&mode=nested -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Stefan Reinauer Sent: Tuesday, September 21, 2004 3:56 AM To: Sagiv Yefet Cc: [EMAIL PROTECTED] Subject: Re: Boot problem * Sagiv Yefet <[EMAIL PROTECTED]> [040921 10:21]: > I prepared a kernel elf file. > The station is up and it loads the elf file. > Then nothing happens. > Just print something: > Firmware: bios is Linuxbios One note: It would be a lot easier to help you if you posted a bit of context around your debug reports, like 2-3 lines of serial output before the hang etc. Plus, just pasting the actual serial output is easier to debug than writing error messages down from memory. Detailed reports will give you higher quality and quicker answers. > What can be the problem? You did not specify to use serial console for your Linux kernel. add something like "console=ttyS0,115200n8" to your command line. Stefan ___ Linuxbios mailing list [EMAIL PROTECTED] http://www.clustermatic.org/mailman/listinfo/linuxbios ___ Linuxbios mailing list [EMAIL PROTECTED] http://www.clustermatic.org/mailman/listinfo/linuxbios
RE: about linux, linuxbios and bootup times
Ok, I will add my 2 cents. This is my setup. 1. Linux bios configures the MB (takes about 1-2 seconds for me and my Tyan) 2. Then it loads etherboot (add maybe another second here) 3. Etherboot remotely loads Kernel from a machine already running thus saving disk spin up time (4-5 seconds) A. I suppose you could have this in RAM and send over a gig pipe or 10 gig pipe if speed is an issue 4. Then Kernel runs (5-10 seconds later) 5. Bash prompt with a well configured linux system What is great about Linux bios is it is flexible. It is also faster than my standard bios as it doesn't Do memory checks and such. It just get's right on to it. Although you can add in your own tests in the Bios or in the payload area. FYI: I've heard a bproc setup gets going in about 10 seconds from power on to running. Here is an even faster plausible setup, you can't do this with a proprietary bios;) 1. Linux bios configures the MB (takes about 1-2 seconds for me and my Tyan) 2. Then it jumps to the linux kernel itself embedded on the BIOS itself 3. Kernel is done loading about 5 to 10 seconds later and you're at cli prompt. This is an ideal case for speed if you have a big enough bios size. M-Tech is Supposed to have an LPC interface to their DOC (disk on chip). This would have made My life so nice, but as far as I know it isn't ready yet. Hope this helps. Oh and the support from this email list is quite awesome. People Here always help me so I try to return the favor as much as I can. Dave -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of linuxg33k Sent: Thursday, September 09, 2004 9:59 PM To: [EMAIL PROTECTED] Subject: about linux, linuxbios and bootup times Hi everyone. I'm a new member, I joined the list to learn more about the Linuxbios project. A question for anyone that can point me in the right direction to information: Q: I read everything on linuxbios.org as well as googled until i got a nosebleed, but i can't find any real world examples of linuxbios + linuxdistro setups. I am looking right now to purchase a linux bios compatable mobo based on the list from linuxbios.org to play around with, but what i was wondering is, just how can linuxbios speed up the boot process of a linux based system? Pardon my newbieness, but I have never had a bios be anything more than a fraction of the total bootup time on any linux system, so does linuxbios have the capability to litterally boot a linux system to cli login prompt of any distro within seconds or not? I realize it's a general question, assume I'm running debian base install ( no x, no desktop environment, boot staright to command line), most of the bootup process is taken up by the bootup scripts checking the hardware and starting up various services (I probably have too many and unoptimized i'm sure but thats another issue alltogether). From everything that I have read, I am understanding that basically its a faster bios that jumps to the distros bootloader when done? Or does this redefine the bootup process where the linuxbios is the bootloader and upon coming to life jumps straight to the distro kernel? If it jumps to the distro bootloader surely the time savings are a few seconds at best? If linuxbios takes over some of the bootloader functions, how does this affect a typicall install if at all? Sorry for the overgeneralized questions, I just need a few answers here, even if vague to help me create a knowledge sandbox into which i can then drill down to proper understanding. By the way, i read an article recently of an interview with the president of Tyan. According to the interview Tyan will be shipping all motherboards with Linuxbios. I have no idea if they are using the real deal from cvs, or forking it, or what, but goddamn that really cool stuff. I'm hoping some of the answers to my question will mean that linux on the desktop has a bright future vis a vis Tyan at least. If anyone wants a copy of it, email me and I will attach the html document - I knew they would take it down as indeed they have. Thanks aforehand - Rob ___ Linuxbios mailing list [EMAIL PROTECTED] http://www.clustermatic.org/mailman/listinfo/linuxbios ___ Linuxbios mailing list [EMAIL PROTECTED] http://www.clustermatic.org/mailman/listinfo/linuxbios
RE: Windows over LinuxBIOS
Hi, Read this: http://pcburn.com/article.php?op=Print&sid=62 From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Dave BeltSent: Wednesday, September 08, 2004 9:02 AMTo: [EMAIL PROTECTED]Subject: Windows over LinuxBIOS I have a customer building a custom PC based board. I have been presenting LinuxBIOS as a viable BIOS option; however, they have a serious interest in running Windows, likely 2K & XP, on this board. Does anybody have experience in this area to share? I’m currently trying to get a grasp of the effort required beyond the LinuxBIOS port itself. Also, what kind of reliability are you getting with your implementation? Any info you could provide would be much appreciated. Thanks
RE: use ramdisk as root file system
Pass the following in to your kernel parameter list console=tty0, console=ttyS0,115200 Then connect a serial line to your serial port and to another machine and Look at the serial output with hyperterm or something. I didn't want to Do this at first, but it has made my life so much easier. If you can't Do this, consider also that 2.6 kernel has netconsole. Netconsole can Send the same serial information over the network so you can see what is Failing. -Original Message- From: zhu shi song [mailto:[EMAIL PROTECTED] Sent: Friday, September 03, 2004 9:25 AM To: Dave Aubin; [EMAIL PROTECTED] Subject: RE: use ramdisk as root file system I've made one initrd to try. But when executing at /sbin/init, linux halts. Output log is as following: RAMDISK: Compressed image found at block 0 Freeing initrd memory: 3687k freed VFS: Mounted root (ext2 filesystem) readonly. Freeing unused kernel memory: 64k freed Warning: unable to open an initial console. [end] By the way, using initramfs, can I have rw root fs on ramdisk? tks zhu --- Dave Aubin <[EMAIL PROTECTED]> wrote: > Here is a good way to do initramfs. Initramfs becomes part of the > kernel and Then executes it's programs in user space which makes > things nice. But there Are other advantages as well. Feel free to > read these while on the > thrown;) > > http://linuxfromscratch.org/pipermail/lfs-hackers/2004-June/001424.html > http://seclists.org/lists/linux-kernel/2004/Jul/0154.html > http://lwn.net/Articles/14776/ > > For my needs initramfs is a life saver, but initrd is good too. Heck > you could Go NFS if you wish. > > Enjoy, > Dave:) > > > > -Original Message- > From: [EMAIL PROTECTED] > [mailto:[EMAIL PROTECTED] On Behalf Of zhu shi song > Sent: Friday, September 03, 2004 6:53 AM > To: [EMAIL PROTECTED] > Subject: use ramdisk as root file system > > I now can boot my QDIA6T(vt8601/vt82c686b) MB using hard disk as root > file system though there is no vga turned on. But I don't need HD. I > hope I can mount RAMDisk as my root filesystem which can be read and > written. How should I do to start such work? I have read some > material about initrd but I don't understand it very clearly. > > tks > zhu > > > > > __ > Do you Yahoo!? > New and Improved Yahoo! Mail - 100MB free storage! > http://promotions.yahoo.com/new_mail > ___ > Linuxbios mailing list > [EMAIL PROTECTED] > http://www.clustermatic.org/mailman/listinfo/linuxbios > __ Do you Yahoo!? Read only the mail you want - Yahoo! Mail SpamGuard. http://promotions.yahoo.com/new_mail ___ Linuxbios mailing list [EMAIL PROTECTED] http://www.clustermatic.org/mailman/listinfo/linuxbios
RE: use ramdisk as root file system
Here is a good way to do initramfs. Initramfs becomes part of the kernel and Then executes it's programs in user space which makes things nice. But there Are other advantages as well. Feel free to read these while on the thrown;) http://linuxfromscratch.org/pipermail/lfs-hackers/2004-June/001424.html http://seclists.org/lists/linux-kernel/2004/Jul/0154.html http://lwn.net/Articles/14776/ For my needs initramfs is a life saver, but initrd is good too. Heck you could Go NFS if you wish. Enjoy, Dave:) -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of zhu shi song Sent: Friday, September 03, 2004 6:53 AM To: [EMAIL PROTECTED] Subject: use ramdisk as root file system I now can boot my QDIA6T(vt8601/vt82c686b) MB using hard disk as root file system though there is no vga turned on. But I don't need HD. I hope I can mount RAMDisk as my root filesystem which can be read and written. How should I do to start such work? I have read some material about initrd but I don't understand it very clearly. tks zhu __ Do you Yahoo!? New and Improved Yahoo! Mail - 100MB free storage! http://promotions.yahoo.com/new_mail ___ Linuxbios mailing list [EMAIL PROTECTED] http://www.clustermatic.org/mailman/listinfo/linuxbios ___ Linuxbios mailing list [EMAIL PROTECTED] http://www.clustermatic.org/mailman/listinfo/linuxbios
RE: elf for USB boot in FILO in Etherboot
Here's is what I've found and made filo & elf work. I build with AMD64, 2.6.6 compiled under Suse 9.0, gcc 3.3.1. I build with mkelfImage also on Suse 9.0, Amd 64. There is a problem loading any mkelf image with an initrd. I don't think it has anything to do with the tools as I've tried An elf made with all 32 bit tools and an older compiler got the Same failure with the initrd portion. I suspect it is the elf Decompression in filo with a multipart built elf. I know mkelfImage with multipart works in etherboot, so I further think It is filo's elf reader. That said here's what I did to get around The problem. Don't use a kernel & initrd approach. Use a different early file system Approach. I use initramfs. It is one Big Fat Kernel (BFK). When I use this Approach it works for me. I hope this helps those who wish to use filo & etherboot. Thanks, Dave -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Yinghai Lu Sent: Thursday, September 02, 2004 12:37 PM To: 'ron minnich' Cc: 'LinuxBIOS' Subject: elf for USB boot in FILO in Etherboot I remember that some time ago, Miller met the problem with the use FILO and FILO in Etherboot to boot elf made by mkelfImage 2.5from Kernel and Init. The kernel said that can not find the init. Yesterday I met the same problem under following configuration: Kernel: 2.6.8.1 compiled under Suse 9.1 AMD64 ( gcc 3.3.3). Used mkelfImage under Redhat 9 to produce the final elf. When I use 2.6.5, 2.6.6, 2.6.7 with Suse 9 compiler gcc 3.3.1, all work well. Miller seems have problem with 2.6.6 and Suse 9.1. So I guess there is some problem with gcc 3.3.3 in Suse 9. or there is some optimization for (EM86T) cause problem. Miller, Can you try to compile your kernel under Suse 9.? Regards YH ___ Linuxbios mailing list [EMAIL PROTECTED] http://www.clustermatic.org/mailman/listinfo/linuxbios ___ Linuxbios mailing list [EMAIL PROTECTED] http://www.clustermatic.org/mailman/listinfo/linuxbios
RE: Redirect your console to the network
How to get netconsole to work: 1. Build your 2.6 kernel with tg3 support AND netconsole as part of the kernel A. This is the easiest way, I couldn't do it via modules as I couldn't get the polling to work. 2. Pass in to the kernel as a parameter the netconsole information A. This will automatically send the console information to the destination address when eth0 is up. Doing this worked for me, but a little bit of a pain was involved. Hope this helped. Dave -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Dave Aubin Sent: Wednesday, September 01, 2004 3:12 PM To: ron minnich Cc: [EMAIL PROTECTED] Subject: RE: Redirect your console to the network Hey Ron, If your tool doesn't have to support polling can you please pass that on to me? That's one side effect of the netconsole tool. You need to have polling enabled in the Network driver. I've been having trouble getting that to fly actually. Thanks, Dave -Original Message- From: ron minnich [mailto:[EMAIL PROTECTED] Sent: Wednesday, September 01, 2004 11:08 AM To: Dave Aubin Cc: [EMAIL PROTECTED] Subject: Re: Redirect your console to the network yes, we have used that off and on for a while. I hope they improved it to be a real module, but if not I have an iproved version here ... thanks for the pointer. ron ___ Linuxbios mailing list [EMAIL PROTECTED] http://www.clustermatic.org/mailman/listinfo/linuxbios ___ Linuxbios mailing list [EMAIL PROTECTED] http://www.clustermatic.org/mailman/listinfo/linuxbios
RE: Redirect your console to the network
Hey Ron, If your tool doesn't have to support polling can you please pass that on to me? That's one side effect of the netconsole tool. You need to have polling enabled in the Network driver. I've been having trouble getting that to fly actually. Thanks, Dave -Original Message- From: ron minnich [mailto:[EMAIL PROTECTED] Sent: Wednesday, September 01, 2004 11:08 AM To: Dave Aubin Cc: [EMAIL PROTECTED] Subject: Re: Redirect your console to the network yes, we have used that off and on for a while. I hope they improved it to be a real module, but if not I have an iproved version here ... thanks for the pointer. ron ___ Linuxbios mailing list [EMAIL PROTECTED] http://www.clustermatic.org/mailman/listinfo/linuxbios
Redirect your console to the network
Hi, I just came across this and I thought I'd pass it along as a nice tool to have. Especially when one doesn't have VGA and serial isn't working for you. I hope someone else finds it as useful for them as it does for me:) http://technocrat.net/article.pl?sid=04/08/14/0236245&mode=nested Enjoy, Dave
RE: booting other oses
Hi Stefan,
What is your goal to want to use Linux bios? If your goal is to get
It to load a Linux kernel, then try etherboot. There is also etherboot
With filo. Etherboot will provide an elf file for you that is network
Card aware and also has support for ide hd access. There is also a flavor
Of etherboot that has filo support in it. Filo gives the ability to load
Off of a usb stick. Knowing this you can use the net, ide drive or usb stick
To load your os. Gotta love it;)
Dave
-Original Message-
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Jakob Praher
Sent: Wednesday, August 25, 2004 6:50 AM
To: linuxbios
Subject: Re: booting other oses
hi Stefan,
thanks für the info.
I have included some additional questions.
but lets summarize what I think I know:
linuxbios is a bootstrapper thats able to load a linux kernel/elf binary from within a
flash rom/file/...?
or is linuxbios itself a linux kernel that is able to execute another elf binary?
if the first option is true, it would probably need hardware access code for accessing
ide/scsi disks without the 16bit callbacks (INT13 and
friends)
Am Mit, den 25.08.2004 schrieb Stefan Reinauer um 11:26:
> * Jakob Praher <[EMAIL PROTECTED]> [040825 09:31]:
> > how/where does linuxbios do the loading of other oses?
>
> LinuxBIOS can load an arbitrary static ELF binary from flash or disk.
how do you then be able to load ntldr or something like that?
afaik ntldr is no elf executable it is either a COFF/PE or it is a DOS exe ...
>
> > linuxbios loads the linux kernel from the flashrom, which then it is
> > in real mode imho.
>
> It can also load a bootloader from flash, like etherboot, filo or
> start openbios. This is all in protected mode though. Real mode is
> gone for good 17 instructions after power-on
thats good to know.
>
> > for instance how would linuxbios boot into for instance grub or lilo?
>
> grub and lilo both don't work in LinuxBIOS since they are using PCBIOS
> 16bit callbacks ("interrupts") for IO. If you want to use those
> anyways, have a look at ADLO
I understand. so what is the preferred boot loader with linuxbios?
>
>
> (See mailing list archive for above phrases ;)
hehe.
-- Jakob
>
___
Linuxbios mailing list
[EMAIL PROTECTED]
http://www.clustermatic.org/mailman/listinfo/linuxbios
___
Linuxbios mailing list
[EMAIL PROTECTED]
http://www.clustermatic.org/mailman/listinfo/linuxbios
