coreboot

coreboot@coreboot.org

5 participants
39705 discussions

can pcm-5823 boot linux from doc directly
by zhu shi song 17 Feb '03

17 Feb '03

linuxbios can support pcm-5823, but it needs etherboot. can pcm-5823 boot linux from doc embedded in the board directly? zhu --------------------------------- Do you Yahoo!? Yahoo! Shopping - Send Flowers for Valentine's Day

2 1

Re:Re: FW: Re:Re: Re:Re:Re:Re: rtl8139 NIC IRQ is 0 on m758lmr+ mainboard
by riskin＠263.net 17 Feb '03

17 Feb '03

>On Fri, 2003-02-14 at 08:59, riskin(a)263.net wrote: >> ----- Original Message ----- >> From: "Ronald G. Minnich" <rminnich(a)lanl.gov> >> To: <riskin(a)263.net> >> Cc: <ollie(a)sis.com.tw>,<aip(a)cwlinux.com>,<jerj(a)coplanar.net>,<linuxbios(a)clustermatic.org> >> Sent: 2003-02-14 07:21:19 >> Subject: Re:Re: Re:Re:Re:Re: rtl8139 NIC IRQ is 0 on m758lmr+ mainboard >> > >No difference in theory. I think the problem is that you have wrong IRQ >table. Did you tried get_irqtable util ? > > >-- >ollie lho <ollie(a)sis.com.tw> Thanks, I have resolved these problems. riskin ========================== 263电子邮件－信赖邮自专业

1 0

how to build linuxbios rom image(256k)
by zhu shi song 16 Feb '03

16 Feb '03

how to build linuxbios rom images( for 256 flash ) which can boot linux from hda? I need the info about the tools we need and the steps we should follow. thanks zhu --------------------------------- Do you Yahoo!? Yahoo! Shopping - Send Flowers for Valentine's Day

1 0

development branch
by Ronald G. Minnich 14 Feb '03

14 Feb '03

I think another goal is going to be setting up IRQs. ron

1 0

parallel port and joyport
by Andre Dias 14 Feb '03

14 Feb '03

I am having trouble trying to use the m810 parallel port and joyport with linuxbios. Perhaps the BIOS sets the port/irq etc. Has anyone gone over this problems? andre http://usuarios.uninet.com.br/~aod ----------------------------------------------

2 1

FW: Re:Re: Re:Re:Re:Re: rtl8139 NIC IRQ is 0 on m758lmr+ mainboard
by riskin＠263.net 14 Feb '03

14 Feb '03

----- Original Message ----- From: "Ronald G. Minnich" <rminnich(a)lanl.gov> To: <riskin(a)263.net> Cc: <ollie(a)sis.com.tw>,<aip(a)cwlinux.com>,<jerj(a)coplanar.net>,<linuxbios(a)clustermatic.org> Sent: 2003-02-14 07:21:19 Subject: Re:Re: Re:Re:Re:Re: rtl8139 NIC IRQ is 0 on m758lmr+ mainboard >did you get the right linuxbios? we had ANOTHER problem with these >mainboards in that the three slot one could not run with the 2 slot >linuxbios -- they rewired things. > >I don't use these chipsets right now so I am not much help, sorry. > >ron Could you tell me the difference between sis630 and sis630e chipset? ========================== 263电子邮件－信赖邮自专业

2 1

questions
by Sanjay lal 13 Feb '03

13 Feb '03

hello, I had a few questions regarding linuxbios: 1) Does it support tftpboot,bootp etc? 2) Does it support GDB stubs for debugging? 3) Are there any licensing issues involved if used? Any information is of great help. thanks in advance Sanju _________________________________________________________________ MSN 8 helps eliminate e-mail viruses. Get 2 months FREE*. http://join.msn.com/?page=features/virus

5 5

Re: Q: MTD and NIC Roms...
by Jeremy Jackson 13 Feb '03

13 Feb '03

On Thu, 2003-02-13 at 01:14, Jeff Garzik wrote: > Eric W. Biederman wrote: > > Currently I have a patch to eepro100.c that adds an MTD map driver so > > the onboard rom can be written. Making code like etherboot easier to > > flash etc. > [...] > > I am currently looking for ideas on ways to cleanly get this code > > into the kernel, and I am looking for ideas. The map driver is > > > Well... this functionality has existed for a while, and it doesn't need > to be in the kernel :) > > Donald Becker's diag suite can do flashing. > ftp://www.scyld.com/pub/diag/ He provides means to program the flash > from userspace. I tried it on a tulip, and it caused a hard reset. PCI bus issues? Also, by making it a map driver, I can flash LinuxBIOS into EEPROM, disable write access to the EEPROM, and put the *DoC* in the NIC socket. Putting a public key in the EEPROM and making it RO makes the whole system secure. Or I could port DoC and jffs driver to userspace... Porting devbios to MTD will then give a large library of NOR flash, including quirks (like ATMEL has different versions, and none work if you just use the datasheet), and allow them to be used in arbitrary sockets. Also, say bye bye to the "pull out the eeprom and put in DoC quick so the electrons don't notice" trick. Just put the DoC into the NIC, boot up, flash, power down, swap to BIOS socket. Sorry LinuxBIOS guys, I guess you'll have to switch back to drinking coffee. > > And I think that's the best place for it. We _could_ bloat up the > kernel code by adding the ability flash -- but how many users is that > going to serve, that are not already served by existing programs? So, I > disagree with getting this stuff into the kernel at all. > > Jeff > > > > > ______________________________________________________ > Linux MTD discussion mailing list > http://lists.infradead.org/mailman/listinfo/linux-mtd/ -- Jeremy Jackson <jerj(a)coplanar.net>

1 0

Re:Re: Re:Re:Re:Re: rtl8139 NIC IRQ is 0 on m758lmr+ mainboard
by riskin＠263.net 13 Feb '03

13 Feb '03

>I don't think the 2.2.x kernel can set up IRQs correctly. Can you try >2.4.x kernel first ? >ollie lho <ollie(a)sis.com.tw> I have tried 2.4.17 kernel,solt1 and solt2 can work normally. Though solt3 can get IRQ,it can't work. Could you tell me how the mainboard(pcchips m758lmr+: sis630 chip set) IRQ lines is wired? Is the pcchips m758lmr+(sis630 chip set) wired as following? * INTA INTB INTC INTD * ---------------------------- * slot 1: dev=0x9 wiring: PIRQ_C PIRQ_D PIRQ_A PIRQ_B * slot 2: dev=0xb wiring: PIRQ_B PIRQ_C PIRQ_D PIRQ_A * slot 3: dev=0xd wiring: PIRQ_A PIRQ_B PIRQ_C PIRQ_D Thanks. riskin ========================== 263电子邮件－信赖邮自专业

4 3

Bringing up eth0 failed
by lawrence 13 Feb '03

13 Feb '03

Hi, all: I have a problem about etho bringing up. The error output is following: Bringing up interface eth0: dhcpcd[440]: timed out waiting for a valid DHCP server response Determining IP information for eth0... failed. So I check the packets transmitted between DHCP server and client base on LinuxBIOS. I find the client can submit a request, but it can not receive the ACK from DHCP server, so it fail to determine its IP. The output differences between the normal BIOS and LinuxBIOS: normal BIOS: ENABLING IO-APIC IRQs Setting 8 in the phys_id_present_map ...changing IO-APIC physical APIC ID to 8 ... ok. Setting 9 in the phys_id_present_map ...changing IO-APIC physical APIC ID to 9 ... ok. Setting 10 in the phys_id_present_map ...changing IO-APIC physical APIC ID to 10 ... ok. ..TIMER: vector=0x31 pin1=2 pin2=0 PCI: Using IRQ router PIIX [8086/2480] at 00:1f.0 PCI->APIC IRQ transform: (B0,I29,P0) -> 16 PCI->APIC IRQ transform: (B0,I31,P0) -> 18 PCI->APIC IRQ transform: (B0,I31,P1) -> 17 PCI->APIC IRQ transform: (B4,I1,P0) -> 48 PCI->APIC IRQ transform: (B1,I1,P0) -> 17 PCI->APIC IRQ transform: (B1,I2,P0) -> 18 e100: eth0: Intel(R) PRO/100 S Server Adapter Mem:0xfe7fe000 IRQ:17 Speed:0 Mbps Dx:N/A Hardware receive checksums enabled Setting network parameters: [ OK ] Bringing up loopback interface: [ OK ] Bringing up interface eth0: [ OK ] LinuxBIOS: Setting 8 in the phys_id_present_map ...changing IO-APIC physical APIC ID to 8 ... ok. Transparent bridge - Intel Corp. 82801BA/CA/DB PCI Bridge PCI->APIC IRQ transform: (B0,I29,P0) -> 16 PCI->APIC IRQ transform: (B0,I29,P1) -> 16 PCI->APIC IRQ transform: (B0,I29,P2) -> 16 PCI->APIC IRQ transform: (B0,I31,P0) -> 18 PCI->APIC IRQ transform: (B0,I31,P1) -> 17 PCI->APIC IRQ transform: (B4,I1,P0) -> 24 Bringing up loopback interface: [ OK ] Bringing up interface eth0: dhcpcd[440]: timed out waiting for a valid DHCP server response Determining IP information for eth0... failed. [FAILED] Does the problem come from mptable.c? How can I do next? Who can tell me? Thanks a lot! Best Regards, Lawrence

1 0

Jump to page:

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

2005

2004

2003

2002

coreboot