Hi! I'd like to try LinuxBIOS on a 440BX-based Abit BE6-II V2.0. After talking on IRC, I'm sending the output of 'lspci -tvnn' and 'superiotool -dV' and a generated irq_tabl.c.
'lspci -tvnn' output: -[0000:00]-+-00.0 Unknown device [8086:7190] +-01.0-[0000:01]----00.0 Unknown device [10de:0110] +-07.0 Unknown device [8086:7110] +-07.1 Unknown device [8086:7111] +-07.2 Unknown device [8086:7112] +-07.3 Unknown device [8086:7113] +-0f.0 Unknown device [11ab:4320] -13.0 Unknown device [1103:0004]
'superiotool -dV' output: superiotool r Probing for ALi Super I/O at 0x3f0... Failed. Returned data: id=0xffff, rev=0xff Probing for ALi Super I/O at 0x370... Failed. Returned data: id=0xffff, rev=0xff Probing for Fintek Super I/O at 0x2e... Failed. Returned data: vid=0xffff, id=0xffff Probing for Fintek Super I/O at 0x4e... Failed. Returned data: vid=0xffff, id=0xffff Probing for ITE Super I/O (init=0x87,0x01,0x55,0x55/0xaa) at 0x2e... Failed. Returned data: id=0xffff, rev=0xf Probing for ITE Super I/O (init=0x87,0x87) at 0x2e... Failed. Returned data: id=0xffff, rev=0xf Probing for ITE Super I/O (init=0x87,0x01,0x55,0x55/0xaa) at 0x4e... Failed. Returned data: id=0xffff, rev=0xf Probing for ITE Super I/O (init=0x87,0x87) at 0x4e... Failed. Returned data: id=0xffff, rev=0xf Probing for NSC Super I/O at 0x2e... Failed. Returned data: port=0xff, port+1=0xff Probing for NSC Super I/O at 0x4e... Failed. Returned data: port=0xff, port+1=0xff Probing for SMSC Super I/O (idregs=0x20/0x21) at 0x2e... Failed. Returned data: id=0xff, rev=0xff Probing for SMSC Super I/O (idregs=0x0d/0x0e) at 0x2e... Failed. Returned data: id=0xff, rev=0xff Probing for SMSC Super I/O (idregs=0x20/0x21) at 0x4e... Failed. Returned data: id=0xff, rev=0xff Probing for SMSC Super I/O (idregs=0x0d/0x0e) at 0x4e... Failed. Returned data: id=0xff, rev=0xff Probing for SMSC Super I/O (idregs=0x20/0x21) at 0x162e... Failed. Returned data: id=0xff, rev=0xff Probing for SMSC Super I/O (idregs=0x0d/0x0e) at 0x162e... Failed. Returned data: id=0xff, rev=0xff Probing for SMSC Super I/O (idregs=0x20/0x21) at 0x164e... Failed. Returned data: id=0xff, rev=0xff Probing for SMSC Super I/O (idregs=0x0d/0x0e) at 0x164e... Failed. Returned data: id=0xff, rev=0xff Probing for SMSC Super I/O (idregs=0x20/0x21) at 0x3f0... Failed. Returned data: id=0xff, rev=0xff Probing for SMSC Super I/O (idregs=0x0d/0x0e) at 0x3f0... Failed. Returned data: id=0xff, rev=0xff Probing for SMSC Super I/O (idregs=0x20/0x21) at 0x370... Failed. Returned data: id=0xff, rev=0xff Probing for SMSC Super I/O (idregs=0x0d/0x0e) at 0x370... Failed. Returned data: id=0xff, rev=0xff Probing for Winbond Super I/O (init=0x88) at 0x2e... Failed. Returned data: id/oldid=0xff/0x0f, rev=0xff Probing for Winbond Super I/O (init=0x89) at 0x2e... Failed. Returned data: id/oldid=0xff/0x0f, rev=0xff Probing for Winbond Super I/O (init=0x86,0x86) at 0x2e... Failed. Returned data: id/oldid=0xff/0x0f, rev=0xff Probing for Winbond Super I/O (init=0x87,0x87) at 0x2e... Failed. Returned data: id/oldid=0xff/0x0f, rev=0xff Probing for Winbond Super I/O (init=0x88) at 0x4e... Failed. Returned data: id/oldid=0xff/0x0f, rev=0xff Probing for Winbond Super I/O (init=0x89) at 0x4e... Failed. Returned data: id/oldid=0xff/0x0f, rev=0xff Probing for Winbond Super I/O (init=0x86,0x86) at 0x4e... Failed. Returned data: id/oldid=0xff/0x0f, rev=0xff Probing for Winbond Super I/O (init=0x87,0x87) at 0x4e... Failed. Returned data: id/oldid=0xff/0x0f, rev=0xff Probing for Winbond Super I/O (init=0x88) at 0x3f0... Failed. Returned data: id/oldid=0xff/0x0f, rev=0xff Probing for Winbond Super I/O (init=0x89) at 0x3f0... Failed. Returned data: id/oldid=0xff/0x0f, rev=0xff Probing for Winbond Super I/O (init=0x86,0x86) at 0x3f0... Failed. Returned data: id/oldid=0xff/0x0f, rev=0xff Probing for Winbond Super I/O (init=0x87,0x87) at 0x3f0... Found Winbond W83627HF/F/HG/G (id=0x52, rev=0xf4) at 0x3f0 Register dump: idx 02 07 20 21 22 23 24 25 26 28 29 2a 2b 2c 2e 2f val ff 0b 52 f4 ff fe 80 00 00 00 ff 00 00 00 00 ff def 00 NA 52 NA ff 00 MM 00 00 00 00 7c c0 00 00 00 LDN 0x00 (Floppy) idx 30 60 61 70 74 f0 f1 f2 f4 f5 val 01 03 f0 06 02 0c 00 ff 00 00 def 01 03 f0 06 02 0e 00 ff 00 00 LDN 0x01 (Parallel port) idx 30 60 61 70 74 f0 val 01 03 78 07 03 00 def 01 03 78 07 04 3f LDN 0x02 (COM1) idx 30 60 61 70 f0 val 01 03 f8 04 00 def 01 03 f8 04 00 LDN 0x03 (COM2) idx 30 60 61 70 f0 f1 val 01 02 f8 03 00 00 def 01 02 f8 03 00 00 LDN 0x05 (Keyboard) idx 30 60 61 62 63 70 72 f0 val 01 00 60 00 64 01 00 40 def 01 00 60 00 64 01 0c 80 LDN 0x06 (Consumer IR) idx 30 60 61 70 val 00 00 00 00 def 00 00 00 00 LDN 0x07 (Game port, MIDI port, GPIO 1) idx 30 60 61 62 63 70 f0 f1 f2 val 01 00 00 00 00 00 ff 00 ff def 00 02 01 03 30 09 ff 00 00 LDN 0x08 (GPIO 2, Watchdog timer) idx 30 f0 f1 f2 f3 f5 f6 f6 f7 val 01 00 ff 00 00 ff ff ff ff def 00 ff 00 00 00 00 00 00 00 LDN 0x09 (GPIO 3) idx 30 f0 f1 f2 f3 val 00 ff ff ff ff def 00 ff 00 00 00 LDN 0x0a (ACPI) idx 30 70 e0 e1 e2 e3 e4 e5 e6 e7 f0 f1 f3 f4 f6 f7 f9 fe ff val 00 00 00 00 08 00 00 00 00 00 00 8f 37 00 00 00 00 00 00 def 00 00 00 00 NA NA 00 00 00 00 00 00 00 00 00 00 00 00 00 LDN 0x0b (Hardware monitor) idx 30 60 61 70 f0 val 01 ff ff ff ff def 00 00 00 00 00 Probing for Winbond Super I/O (init=0x88) at 0x370... Failed. Returned data: id/oldid=0xff/0x0f, rev=0xff Probing for Winbond Super I/O (init=0x89) at 0x370... Failed. Returned data: id/oldid=0xff/0x0f, rev=0xff Probing for Winbond Super I/O (init=0x86,0x86) at 0x370... Failed. Returned data: id/oldid=0xff/0x0f, rev=0xff Probing for Winbond Super I/O (init=0x87,0x87) at 0x370... Failed. Returned data: id/oldid=0xff/0x0f, rev=0xff Probing for Winbond Super I/O (init=0x88) at 0x250... Failed. Returned data: id/oldid=0xff/0x0f, rev=0xff Probing for Winbond Super I/O (init=0x89) at 0x250... Failed. Returned data: id/oldid=0xff/0x0f, rev=0xff Probing for Winbond Super I/O (init=0x86,0x86) at 0x250... Failed. Returned data: id/oldid=0xff/0x0f, rev=0xff Probing for Winbond Super I/O (init=0x87,0x87) at 0x250... Failed. Returned data: id/oldid=0xff/0x0f, rev=0xff
On Fri, Dec 07, 2007 at 01:39:43PM +0300, Sergei Antonov wrote:
I'd like to try LinuxBIOS on a 440BX-based Abit BE6-II V2.0. After talking on IRC, I'm sending the output of 'lspci -tvnn' and 'superiotool -dV' and a generated irq_tabl.c.
Thanks, here's a patch for your board you can test. I guess most of the hardware should work with this code, but some smaller issues might need to be fixed after it has been tested on real hardware.
Uwe.
On Dec 9, 2007 9:42 PM, Uwe Hermann uwe@hermann-uwe.de wrote:
On Fri, Dec 07, 2007 at 01:39:43PM +0300, Sergei Antonov wrote:
I'd like to try LinuxBIOS on a 440BX-based Abit BE6-II V2.0. After talking on IRC, I'm sending the output of 'lspci -tvnn' and 'superiotool -dV' and a generated irq_tabl.c.
Thanks, here's a patch for your board you can test. I guess most of the hardware should work with this code, but some smaller issues might need to be fixed after it has been tested on real hardware.
After some experiments it works. I've found 2 issues.
1. The keyboard doesn't work. Here is a piece of log from the serial port: ===================================== PNP: 03f0.5 init Keyboard init... Keyboard input buffer would not empty =====================================
2. I had to change filo-0.5\drivers\ide.c function 'find_ide_controller'. For some reason it first looks for IDE controller with class 0x0180 and only if nothing was found looks for class 0x0101. I think it is wrong, but where can I report about that? It worked right for me after this change: -dev = pci_find_device(-1, -1, 0x0180, -1, pci_index); // S-ATA first. +dev = 0;
On Dec 12, 2007 2:38 PM, Sergei Antonov saproj@gmail.com wrote:
- The keyboard doesn't work. Here is a piece of log from the serial port:
===================================== PNP: 03f0.5 init Keyboard init... Keyboard input buffer would not empty =====================================
hmm. Are you sure you know where the kb is connected?
- I had to change filo-0.5\drivers\ide.c function
'find_ide_controller'. For some reason it first looks for IDE controller with class 0x0180 and only if nothing was found looks for class 0x0101. I think it is wrong, but where can I report about that? It worked right for me after this change: -dev = pci_find_device(-1, -1, 0x0180, -1, pci_index); // S-ATA first. +dev = 0;
interesting! I wonder what the right thing to do here is? You are arguing to prefer sata over pata, right? Where does this leave cdroms as on my shuttles?
can you send a more complete patch?
ron
On Dec 13, 2007 2:06 AM, ron minnich rminnich@gmail.com wrote:
On Dec 12, 2007 2:38 PM, Sergei Antonov saproj@gmail.com wrote:
- The keyboard doesn't work. Here is a piece of log from the serial port:
===================================== PNP: 03f0.5 init Keyboard init... Keyboard input buffer would not empty =====================================
hmm. Are you sure you know where the kb is connected?
Pretty sure that I connected it to the PS/2 keyboard port.
- I had to change filo-0.5\drivers\ide.c function
'find_ide_controller'. For some reason it first looks for IDE controller with class 0x0180 and only if nothing was found looks for class 0x0101. I think it is wrong, but where can I report about that? It worked right for me after this change: -dev = pci_find_device(-1, -1, 0x0180, -1, pci_index); // S-ATA first. +dev = 0;
interesting! I wonder what the right thing to do here is? You are arguing to prefer sata over pata, right? Where does this leave cdroms as on my shuttles?
I'm arguing to prefer the order of drives which the kernel uses when assigns hda, hdb and so on. I don't see the problem with cdroms. Can you explain it?
can you send a more complete patch?
The patch is attached. It works correctly on my computer with both hda (sits on 0x0101) and hde (sits on 0x0180).
On Dec 13, 2007 11:12 AM, Sergei Antonov saproj@gmail.com wrote:
On Dec 13, 2007 2:06 AM, ron minnich rminnich@gmail.com wrote:
On Dec 12, 2007 2:38 PM, Sergei Antonov saproj@gmail.com wrote:
- The keyboard doesn't work. Here is a piece of log from the serial port:
===================================== PNP: 03f0.5 init Keyboard init... Keyboard input buffer would not empty =====================================
hmm. Are you sure you know where the kb is connected?
Pretty sure that I connected it to the PS/2 keyboard port.
I'd be happy to get any clues on how to troubleshoot.
- I had to change filo-0.5\drivers\ide.c function
'find_ide_controller'. For some reason it first looks for IDE controller with class 0x0180 and only if nothing was found looks for class 0x0101. I think it is wrong, but where can I report about that? It worked right for me after this change: -dev = pci_find_device(-1, -1, 0x0180, -1, pci_index); // S-ATA first. +dev = 0;
interesting! I wonder what the right thing to do here is? You are arguing to prefer sata over pata, right? Where does this leave cdroms as on my shuttles?
I'm arguing to prefer the order of drives which the kernel uses when assigns hda, hdb and so on. I don't see the problem with cdroms. Can you explain it?
can you send a more complete patch?
The patch is attached. It works correctly on my computer with both hda (sits on 0x0101) and hde (sits on 0x0180).
I've updated the patch. It had a bug.
On Dec 13, 2007 12:12 AM, Sergei Antonov saproj@gmail.com wrote:
On Dec 13, 2007 2:06 AM, ron minnich rminnich@gmail.com wrote:
On Dec 12, 2007 2:38 PM, Sergei Antonov saproj@gmail.com wrote:
- The keyboard doesn't work. Here is a piece of log from the serial port:
===================================== PNP: 03f0.5 init Keyboard init... Keyboard input buffer would not empty =====================================
hmm. Are you sure you know where the kb is connected?
Pretty sure that I connected it to the PS/2 keyboard port.
right, but which chip is that port connected to? There are multiple choices.
thanks
ron
On Dec 14, 2007 8:22 PM, ron minnich rminnich@gmail.com wrote:
On Dec 13, 2007 12:12 AM, Sergei Antonov saproj@gmail.com wrote:
On Dec 13, 2007 2:06 AM, ron minnich rminnich@gmail.com wrote:
On Dec 12, 2007 2:38 PM, Sergei Antonov saproj@gmail.com wrote:
- The keyboard doesn't work. Here is a piece of log from the serial port:
===================================== PNP: 03f0.5 init Keyboard init... Keyboard input buffer would not empty =====================================
hmm. Are you sure you know where the kb is connected?
Pretty sure that I connected it to the PS/2 keyboard port.
right, but which chip is that port connected to? There are multiple choices.
Winbond W83977EF
On Dec 14, 2007 3:00 PM, Sergei Antonov saproj@gmail.com wrote:
On Dec 14, 2007 8:22 PM, ron minnich rminnich@gmail.com wrote:
On Dec 13, 2007 12:12 AM, Sergei Antonov saproj@gmail.com wrote:
On Dec 13, 2007 2:06 AM, ron minnich rminnich@gmail.com wrote:
On Dec 12, 2007 2:38 PM, Sergei Antonov saproj@gmail.com wrote:
- The keyboard doesn't work. Here is a piece of log from the serial port:
===================================== PNP: 03f0.5 init Keyboard init... Keyboard input buffer would not empty =====================================
hmm. Are you sure you know where the kb is connected?
Pretty sure that I connected it to the PS/2 keyboard port.
right, but which chip is that port connected to? There are multiple choices.
Winbond W83977EF
ok and, sorry to belabor this point, but the mainboard config you are using does set up this superio as the KB controller? IIRC you were using a different mainboard for this board you have. Sorry if I have lost the thread here. There are so many new 440bx mainboards coming up I'm losing track.
ron
On Dec 15, 2007 8:59 PM, ron minnich rminnich@gmail.com wrote:
On Dec 14, 2007 3:00 PM, Sergei Antonov saproj@gmail.com wrote:
On Dec 14, 2007 8:22 PM, ron minnich rminnich@gmail.com wrote:
On Dec 13, 2007 12:12 AM, Sergei Antonov saproj@gmail.com wrote:
On Dec 13, 2007 2:06 AM, ron minnich rminnich@gmail.com wrote:
On Dec 12, 2007 2:38 PM, Sergei Antonov saproj@gmail.com wrote:
- The keyboard doesn't work. Here is a piece of log from the serial port:
===================================== PNP: 03f0.5 init Keyboard init... Keyboard input buffer would not empty =====================================
hmm. Are you sure you know where the kb is connected?
Pretty sure that I connected it to the PS/2 keyboard port.
right, but which chip is that port connected to? There are multiple choices.
Winbond W83977EF
ok and, sorry to belabor this point, but the mainboard config you are using does set up this superio as the KB controller? IIRC you were using a different mainboard for this board you have. Sorry if I have lost the thread here. There are so many new 440bx mainboards coming up I'm losing track.
The src/mainboard/abit/be6-ii_v2_0/Config.lb Uwe gave me contains this string: chip superio/winbond/w83977tf # Super I/O (FIXME: It's W83977EF!) Is it an answer to your question?
-
ron minnich -
Sergei Antonov -
Uwe Hermann