* [9fans] Dell E4300?
@ 2009-08-15 20:19 Benjamin Huntsman
2009-08-15 21:34 ` erik quanstrom
2009-08-16 16:36 ` erik quanstrom
0 siblings, 2 replies; 12+ messages in thread
From: Benjamin Huntsman @ 2009-08-15 20:19 UTC (permalink / raw)
To: 9fans
Anyone here had a chance to try a Dell E4300? It's a nice, compact system, but it really refuses to boot Plan 9:
It has on-board SATA hd, SATA cd-rom, etc. I tried quanstro's 9atom.iso, and with the SATA controller in AHCI mode, it'll start booting, but hangs at:
45555 => 818807+1020832+474972=2314611
entry: f0100020
Plan 9
In modes other than AHCI, neither the "stock" or quanstro's cd's will recognize any devices other than fd0, and even then won't boot from it.
The "stock" cd will hang here in AHCI mode:
PBS1...
Plan 9 from Bell Labs
ELCR: 0C08
pcirouting: South bridge 8086, 2917 not found
Any idea where to start looking? (besides for a different laptop, that is :) )
Thanks!!
-Ben
^ permalink raw reply [flat|nested] 12+ messages in thread
* Re: [9fans] Dell E4300?
2009-08-15 20:19 [9fans] Dell E4300? Benjamin Huntsman
@ 2009-08-15 21:34 ` erik quanstrom
2009-08-15 22:41 ` Benjamin Huntsman
2009-08-16 16:36 ` erik quanstrom
1 sibling, 1 reply; 12+ messages in thread
From: erik quanstrom @ 2009-08-15 21:34 UTC (permalink / raw)
To: 9fans
> Anyone here had a chance to try a Dell E4300? It's a nice, compact system, but it really refuses to boot Plan 9:
>
> It has on-board SATA hd, SATA cd-rom, etc. I tried quanstro's 9atom.iso, and with the SATA controller in AHCI mode, it'll start booting, but hangs at:
>
> 45555 => 818807+1020832+474972=2314611
> entry: f0100020
>
> Plan 9
>
> In modes other than AHCI, neither the "stock" or quanstro's cd's will recognize any devices other than fd0, and even then won't boot from it.
i think there's a good chance things can work.
clearly we're relatively close to booting, because
we've gotten this far.
my semi-educated guess here is that either
we've done something antisocial in 9load that
has corrupted some SMM mode memory. the
leading potential culprit here is ahci. or that
some SMM-driven device, like a usb mouse that
is presented to the os as a ps/2 mouse is messing
up.
the easiest debugging step is to turn off usb
completely.
also, make sure to check for bios updates.
do you have a cpu server? is your laptop
PXE bootable? even a useable network card
would work. if so, it will be much easier to
narrow down the problem quickly.
>
> The "stock" cd will hang here in AHCI mode:
>
> PBS1...
> Plan 9 from Bell Labs
> ELCR: 0C08
> pcirouting: South bridge 8086, 2917 not found
i'll add this southbridge to my cd. this will definately
not hurt. could you send me pci output? if you use
lspci from linux make sure to use -vn so the vid/did
appear. the descriptive strings are fairly useless.
- erik
^ permalink raw reply [flat|nested] 12+ messages in thread
* Re: [9fans] Dell E4300?
2009-08-15 21:34 ` erik quanstrom
@ 2009-08-15 22:41 ` Benjamin Huntsman
0 siblings, 0 replies; 12+ messages in thread
From: Benjamin Huntsman @ 2009-08-15 22:41 UTC (permalink / raw)
To: Fans of the OS Plan 9 from Bell Labs
[-- Attachment #1: Type: text/plain, Size: 24918 bytes --]
>i'll add this southbridge to my cd. this will definately
>not hurt. could you send me pci output? if you use
>lspci from linux make sure to use -vn so the vid/did
>appear. the descriptive strings are fairly useless.
Sorry, I don't use Linux much. This machine currently runs OpenSolaris. Below is the output from 'prtconf -pv' which should be more-or-less similar to Linux's 'lspci -vn'. If you'd prefer the Linux output, I can go download a LiveCD really quick...
Thanks much for your time!!
-Ben
System Configuration: Sun Microsystems i86pc
Memory size: 4048 Megabytes
System Peripherals (PROM Nodes):
Node 0x000001
bios-boot-device: '82'
stdout: 00000000
name: 'i86pc'
Node 0x000002
existing: 00db2000.00000000.0bc58801.00000000
name: 'ramdisk'
Node 0x000003
bus-type: 'isa'
device_type: 'isa'
name: 'isa'
Node 0x000004
compatible: 'pciex_root_complex'
device_type: 'pciex'
reg: 00000000.00000000.00000000
#size-cells: 00000002
#address-cells: 00000003
name: 'pci'
Node 0x000005
reg: 00000000.00000000.00000000.00000000.00000000
compatible: 'pci8086,2a40.1028.24d.7' + 'pci8086,2a40.1028.24d' + 'pci1028,24d' + 'pci8086,2a40.7' + 'pci8086,2a40' + 'pciclass,060000' + 'pciclass,0600'
model: 'Host bridge'
power-consumption: 00000001.00000001
fast-back-to-back:
devsel-speed: 00000000
max-latency: 00000000
min-grant: 00000000
subsystem-vendor-id: 00001028
subsystem-id: 0000024d
unit-address: '0'
class-code: 00060000
revision-id: 00000007
vendor-id: 00008086
device-id: 00002a40
name: 'pci1028,24d'
Node 0x000006
assigned-addresses: 83001010.00000000.f6c00000.00000000.00400000.c3001018.00000000.e0000000.00000000.10000000.81001020.00000000.0000ef98.00000000.00000008.a1001000.00000000.000003b0.00000000.0000000c.a1001000.00000000.000003c0.00000000.00000020.82001000.00000000.000a0000.00000000.00020000
reg: 00001000.00000000.00000000.00000000.00000000.03001010.00000000.00000000.00000000.00400000.43001018.00000000.00000000.00000000.10000000.01001020.00000000.00000000.00000000.00000008.a1001000.00000000.000003b0.00000000.0000000c.a1001000.00000000.000003c0.00000000.00000020.82001000.00000000.000a0000.00000000.00020000
compatible: 'pci8086,2a42.1028.24d.7' + 'pci8086,2a42.1028.24d' + 'pci1028,24d' + 'pci8086,2a42.7' + 'pci8086,2a42' + 'pciclass,030000' + 'pciclass,0300'
model: 'VGA compatible controller'
power-consumption: 00000001.00000001
fast-back-to-back:
devsel-speed: 00000000
interrupts: 00000001
max-latency: 00000000
min-grant: 00000000
subsystem-vendor-id: 00001028
subsystem-id: 0000024d
device_type: 'display'
unit-address: '2'
class-code: 00030000
revision-id: 00000007
vendor-id: 00008086
device-id: 00002a42
name: 'display'
Node 0x000007
assigned-addresses: 83001110.00000000.f6b00000.00000000.00100000
reg: 00001100.00000000.00000000.00000000.00000000.03001110.00000000.00000000.00000000.00100000
compatible: 'pci8086,2a43.1028.24d.7' + 'pci8086,2a43.1028.24d' + 'pci1028,24d' + 'pci8086,2a43.7' + 'pci8086,2a43' + 'pciclass,038000' + 'pciclass,0380'
model: 'Video controller'
power-consumption: 00000001.00000001
fast-back-to-back:
devsel-speed: 00000000
max-latency: 00000000
min-grant: 00000000
subsystem-vendor-id: 00001028
subsystem-id: 0000024d
unit-address: '2,1'
class-code: 00038000
revision-id: 00000007
vendor-id: 00008086
device-id: 00002a43
name: 'pci1028,24d'
Node 0x000008
assigned-addresses: 8200c810.00000000.f6ae0000.00000000.00020000.8200c814.00000000.f6adb000.00000000.00001000.8100c818.00000000.0000efe0.00000000.00000020
reg: 0000c800.00000000.00000000.00000000.00000000.0200c810.00000000.00000000.00000000.00020000.0200c814.00000000.00000000.00000000.00001000.0100c818.00000000.00000000.00000000.00000020
compatible: 'pci8086,10f5.1028.24d.3' + 'pci8086,10f5.1028.24d' + 'pci1028,24d' + 'pci8086,10f5.3' + 'pci8086,10f5' + 'pciclass,020000' + 'pciclass,0200'
model: 'Ethernet controller'
power-consumption: 00000001.00000001
devsel-speed: 00000000
interrupts: 00000001
max-latency: 00000000
min-grant: 00000000
subsystem-vendor-id: 00001028
subsystem-id: 0000024d
unit-address: '19'
class-code: 00020000
revision-id: 00000003
vendor-id: 00008086
device-id: 000010f5
name: 'pci1028,24d'
Node 0x000009
assigned-addresses: 8100d020.00000000.00006f60.00000000.00000020
reg: 0000d000.00000000.00000000.00000000.00000000.0100d020.00000000.00000000.00000000.00000020
compatible: 'pci8086,2937.1028.24d.3' + 'pci8086,2937.1028.24d' + 'pci1028,24d' + 'pci8086,2937.3' + 'pci8086,2937' + 'pciclass,0c0300' + 'pciclass,0c03'
model: 'Universal Serial Bus UHCI compliant'
power-consumption: 00000001.00000001
fast-back-to-back:
devsel-speed: 00000001
interrupts: 00000001
max-latency: 00000000
min-grant: 00000000
subsystem-vendor-id: 00001028
subsystem-id: 0000024d
unit-address: '1a'
class-code: 000c0300
revision-id: 00000003
vendor-id: 00008086
device-id: 00002937
name: 'pci1028,24d'
Node 0x00000a
assigned-addresses: 8100d120.00000000.00006f80.00000000.00000020
reg: 0000d100.00000000.00000000.00000000.00000000.0100d120.00000000.00000000.00000000.00000020
compatible: 'pci8086,2938.1028.24d.3' + 'pci8086,2938.1028.24d' + 'pci1028,24d' + 'pci8086,2938.3' + 'pci8086,2938' + 'pciclass,0c0300' + 'pciclass,0c03'
model: 'Universal Serial Bus UHCI compliant'
power-consumption: 00000001.00000001
fast-back-to-back:
devsel-speed: 00000001
interrupts: 00000002
max-latency: 00000000
min-grant: 00000000
subsystem-vendor-id: 00001028
subsystem-id: 0000024d
unit-address: '1a,1'
class-code: 000c0300
revision-id: 00000003
vendor-id: 00008086
device-id: 00002938
name: 'pci1028,24d'
Node 0x00000b
assigned-addresses: 8100d220.00000000.00006fa0.00000000.00000020
reg: 0000d200.00000000.00000000.00000000.00000000.0100d220.00000000.00000000.00000000.00000020
compatible: 'pci8086,2939.1028.24d.3' + 'pci8086,2939.1028.24d' + 'pci1028,24d' + 'pci8086,2939.3' + 'pci8086,2939' + 'pciclass,0c0300' + 'pciclass,0c03'
model: 'Universal Serial Bus UHCI compliant'
power-consumption: 00000001.00000001
fast-back-to-back:
devsel-speed: 00000001
interrupts: 00000003
max-latency: 00000000
min-grant: 00000000
subsystem-vendor-id: 00001028
subsystem-id: 0000024d
unit-address: '1a,2'
class-code: 000c0300
revision-id: 00000003
vendor-id: 00008086
device-id: 00002939
name: 'pci1028,24d'
Node 0x00000c
assigned-addresses: 8200d710.00000000.fed1c400.00000000.00000400
reg: 0000d700.00000000.00000000.00000000.00000000.0200d710.00000000.00000000.00000000.00000400
compatible: 'pci8086,293c.1028.24d.3' + 'pci8086,293c.1028.24d' + 'pci1028,24d' + 'pci8086,293c.3' + 'pci8086,293c' + 'pciclass,0c0320' + 'pciclass,0c03'
model: 'Universal Serial Bus EHCI compliant'
power-consumption: 00000001.00000001
fast-back-to-back:
devsel-speed: 00000001
interrupts: 00000003
max-latency: 00000000
min-grant: 00000000
subsystem-vendor-id: 00001028
subsystem-id: 0000024d
unit-address: '1a,7'
class-code: 000c0320
revision-id: 00000003
vendor-id: 00008086
device-id: 0000293c
name: 'pci1028,24d'
Node 0x00000d
assigned-addresses: 8300d810.00000000.f6adc000.00000000.00004000
reg: 0000d800.00000000.00000000.00000000.00000000.0300d810.00000000.00000000.00000000.00004000
compatible: 'pciex8086,293e.1028.24d.3' + 'pciex8086,293e.1028.24d' + 'pciex8086,293e.3' + 'pciex8086,293e' + 'pciexclass,040300' + 'pciexclass,0403' + 'pci8086,293e.1028.24d.3' + 'pci8086,293e.1028.24d' + 'pci1028,24d' + 'pci8086,293e.3' + 'pci8086,293e' + 'pciclass,040300' + 'pciclass,0403'
model: 'Mixed Mode device'
power-consumption: 00000001.00000001
devsel-speed: 00000000
interrupts: 00000001
subsystem-vendor-id: 00001028
subsystem-id: 0000024d
unit-address: '1b'
class-code: 00040300
revision-id: 00000003
vendor-id: 00008086
device-id: 0000293e
name: 'pci1028,24d'
Node 0x00000e
reg: 0000e000.00000000.00000000.00000000.00000000
compatible: 'pciex8086,2940.3' + 'pciex8086,2940' + 'pciexclass,060400' + 'pciexclass,0604' + 'pci8086,2940.3' + 'pci8086,2940' + 'pciclass,060400' + 'pciclass,0604'
model: 'PCI-PCI bridge'
bus-range: 0000000b.0000000b
#size-cells: 00000002
#address-cells: 00000003
device_type: 'pciex'
power-consumption: 00000001.00000001
devsel-speed: 00000000
interrupts: 00000001
unit-address: '1c'
class-code: 00060400
revision-id: 00000003
vendor-id: 00008086
device-id: 00002940
pci-hotplug-type: 00000001
name: 'pci8086,2940'
Node 0x00000f
reg: 0000e100.00000000.00000000.00000000.00000000
compatible: 'pciex8086,2942.3' + 'pciex8086,2942' + 'pciexclass,060400' + 'pciexclass,0604' + 'pci8086,2942.3' + 'pci8086,2942' + 'pciclass,060400' + 'pciclass,0604'
model: 'PCI-PCI bridge'
ranges: 82000000.00000000.f6900000.82000000.00000000.f6900000.00000000.00100000
bus-range: 0000000c.0000000c
#size-cells: 00000002
#address-cells: 00000003
device_type: 'pciex'
power-consumption: 00000001.00000001
slot-names: 00000001.65696370.00000031
physical-slot#: 00000001
devsel-speed: 00000000
interrupts: 00000002
unit-address: '1c,1'
class-code: 00060400
revision-id: 00000003
vendor-id: 00008086
device-id: 00002942
pci-hotplug-type: 00000001
name: 'pci8086,2942'
Node 0x00001c
assigned-addresses: 830c0010.00000000.f69fe000.00000000.00002000
reg: 000c0000.00000000.00000000.00000000.00000000.030c0010.00000000.00000000.00000000.00002000
compatible: 'pciex8086,4235.8086.1121.0' + 'pciex8086,4235.8086.1121' + 'pciex8086,4235.0' + 'pciex8086,4235' + 'pciexclass,028000' + 'pciexclass,0280' + 'pci8086,4235.8086.1121.0' + 'pci8086,4235.8086.1121' + 'pci8086,1121' + 'pci8086,4235.0' + 'pci8086,4235' + 'pciclass,028000' + 'pciclass,0280'
model: 'Network controller'
power-consumption: 00000001.00000001
devsel-speed: 00000000
interrupts: 00000001
subsystem-vendor-id: 00008086
subsystem-id: 00001121
unit-address: '0'
class-code: 00028000
revision-id: 00000000
vendor-id: 00008086
device-id: 00004235
name: 'pci8086,1121'
Node 0x000010
reg: 0000e300.00000000.00000000.00000000.00000000
compatible: 'pciex8086,2946.3' + 'pciex8086,2946' + 'pciexclass,060400' + 'pciexclass,0604' + 'pci8086,2946.3' + 'pci8086,2946' + 'pciclass,060400' + 'pciclass,0604'
model: 'PCI-PCI bridge'
ranges: 81000000.00000000.0000d000.81000000.00000000.0000d000.00000000.00001000.82000000.00000000.f6600000.82000000.00000000.f6600000.00000000.00300000.c2000000.00000000.f0000000.c2000000.00000000.f0000000.00000000.00200000
bus-range: 0000000d.0000000e
#size-cells: 00000002
#address-cells: 00000003
device_type: 'pciex'
power-consumption: 00000001.00000001
slot-names: 00000001.65696370.00000033
physical-slot#: 00000003
devsel-speed: 00000000
interrupts: 00000004
unit-address: '1c,3'
class-code: 00060400
revision-id: 00000003
vendor-id: 00008086
device-id: 00002946
pci-hotplug-type: 00000001
name: 'pci8086,2946'
Node 0x000011
assigned-addresses: 8100e820.00000000.00006f00.00000000.00000020
reg: 0000e800.00000000.00000000.00000000.00000000.0100e820.00000000.00000000.00000000.00000020
compatible: 'pci8086,2934.1028.24d.3' + 'pci8086,2934.1028.24d' + 'pci1028,24d' + 'pci8086,2934.3' + 'pci8086,2934' + 'pciclass,0c0300' + 'pciclass,0c03'
model: 'Universal Serial Bus UHCI compliant'
power-consumption: 00000001.00000001
fast-back-to-back:
devsel-speed: 00000001
interrupts: 00000001
max-latency: 00000000
min-grant: 00000000
subsystem-vendor-id: 00001028
subsystem-id: 0000024d
unit-address: '1d'
class-code: 000c0300
revision-id: 00000003
vendor-id: 00008086
device-id: 00002934
name: 'pci1028,24d'
Node 0x000012
assigned-addresses: 8100e920.00000000.00006f20.00000000.00000020
reg: 0000e900.00000000.00000000.00000000.00000000.0100e920.00000000.00000000.00000000.00000020
compatible: 'pci8086,2935.1028.24d.3' + 'pci8086,2935.1028.24d' + 'pci1028,24d' + 'pci8086,2935.3' + 'pci8086,2935' + 'pciclass,0c0300' + 'pciclass,0c03'
model: 'Universal Serial Bus UHCI compliant'
power-consumption: 00000001.00000001
fast-back-to-back:
devsel-speed: 00000001
interrupts: 00000002
max-latency: 00000000
min-grant: 00000000
subsystem-vendor-id: 00001028
subsystem-id: 0000024d
unit-address: '1d,1'
class-code: 000c0300
revision-id: 00000003
vendor-id: 00008086
device-id: 00002935
name: 'pci1028,24d'
Node 0x000013
assigned-addresses: 8100ea20.00000000.00006f40.00000000.00000020
reg: 0000ea00.00000000.00000000.00000000.00000000.0100ea20.00000000.00000000.00000000.00000020
compatible: 'pci8086,2936.1028.24d.3' + 'pci8086,2936.1028.24d' + 'pci1028,24d' + 'pci8086,2936.3' + 'pci8086,2936' + 'pciclass,0c0300' + 'pciclass,0c03'
model: 'Universal Serial Bus UHCI compliant'
power-consumption: 00000001.00000001
fast-back-to-back:
devsel-speed: 00000001
interrupts: 00000003
max-latency: 00000000
min-grant: 00000000
subsystem-vendor-id: 00001028
subsystem-id: 0000024d
unit-address: '1d,2'
class-code: 000c0300
revision-id: 00000003
vendor-id: 00008086
device-id: 00002936
name: 'pci1028,24d'
Node 0x000014
assigned-addresses: 8200ef10.00000000.fed1c000.00000000.00000400
reg: 0000ef00.00000000.00000000.00000000.00000000.0200ef10.00000000.00000000.00000000.00000400
compatible: 'pci8086,293a.1028.24d.3' + 'pci8086,293a.1028.24d' + 'pci1028,24d' + 'pci8086,293a.3' + 'pci8086,293a' + 'pciclass,0c0320' + 'pciclass,0c03'
model: 'Universal Serial Bus EHCI compliant'
power-consumption: 00000001.00000001
fast-back-to-back:
devsel-speed: 00000001
interrupts: 00000001
max-latency: 00000000
min-grant: 00000000
subsystem-vendor-id: 00001028
subsystem-id: 0000024d
unit-address: '1d,7'
class-code: 000c0320
revision-id: 00000003
vendor-id: 00008086
device-id: 0000293a
name: 'pci1028,24d'
Node 0x000015
reg: 0000f000.00000000.00000000.00000000.00000000
compatible: 'pci8086,2448.93' + 'pci8086,2448' + 'pciclass,060401' + 'pciclass,0604'
model: 'Subtractive Decode PCI-PCI bridge'
ranges: 82000000.00000000.f6500000.82000000.00000000.f6500000.00000000.00100000
bus-range: 00000002.00000002
#size-cells: 00000002
#address-cells: 00000003
device_type: 'pci'
power-consumption: 00000001.00000001
devsel-speed: 00000000
unit-address: '1e'
class-code: 00060401
revision-id: 00000093
vendor-id: 00008086
device-id: 00002448
name: 'pci8086,2448'
Node 0x000019
assigned-addresses: 82020810.00000000.f65ff800.00000000.00000800
reg: 00020800.00000000.00000000.00000000.00000000.02020810.00000000.00000000.00000000.00000800
compatible: 'pci1180,832.1028.24d.5' + 'pci1180,832.1028.24d' + 'pci1028,24d' + 'pci1180,832.5' + 'pci1180,832' + 'pciclass,0c0010' + 'pciclass,0c00'
model: 'FireWire (IEEE 1394) OpenHCI compliant'
power-consumption: 00000001.00000001
devsel-speed: 00000001
interrupts: 00000001
max-latency: 00000004
min-grant: 00000002
subsystem-vendor-id: 00001028
subsystem-id: 0000024d
unit-address: '1'
class-code: 000c0010
revision-id: 00000005
vendor-id: 00001180
device-id: 00000832
name: 'pci1028,24d'
Node 0x00001a
assigned-addresses: 82020910.00000000.f65ff600.00000000.00000100
reg: 00020900.00000000.00000000.00000000.00000000.02020910.00000000.00000000.00000000.00000100
compatible: 'pci1180,822.1028.24d.22' + 'pci1180,822.1028.24d' + 'pci1028,24d' + 'pci1180,822.22' + 'pci1180,822' + 'pciclass,080501' + 'pciclass,0805'
model: 'Unknown class of pci/pnpbios device'
power-consumption: 00000001.00000001
devsel-speed: 00000001
interrupts: 00000002
max-latency: 00000000
min-grant: 00000000
subsystem-vendor-id: 00001028
subsystem-id: 0000024d
unit-address: '1,1'
class-code: 00080501
revision-id: 00000022
vendor-id: 00001180
device-id: 00000822
name: 'pci1028,24d'
Node 0x00001b
assigned-addresses: 82020a10.00000000.f65ff700.00000000.00000100
reg: 00020a00.00000000.00000000.00000000.00000000.02020a10.00000000.00000000.00000000.00000100
compatible: 'pci1180,843.1028.24d.12' + 'pci1180,843.1028.24d' + 'pci1028,24d' + 'pci1180,843.12' + 'pci1180,843' + 'pciclass,088000' + 'pciclass,0880'
model: 'System peripheral'
power-consumption: 00000001.00000001
devsel-speed: 00000001
interrupts: 00000002
max-latency: 00000000
min-grant: 00000000
subsystem-vendor-id: 00001028
subsystem-id: 0000024d
unit-address: '1,2'
class-code: 00088000
revision-id: 00000012
vendor-id: 00001180
device-id: 00000843
name: 'pci1028,24d'
Node 0x000016
reg: 0000f800.00000000.00000000.00000000.00000000
compatible: 'pci8086,2917.1028.24d.3' + 'pci8086,2917.1028.24d' + 'pci1028,24d' + 'pci8086,2917.3' + 'pci8086,2917' + 'pciclass,060100' + 'pciclass,0601'
model: 'ISA bridge'
power-consumption: 00000001.00000001
devsel-speed: 00000001
max-latency: 00000000
min-grant: 00000000
subsystem-vendor-id: 00001028
subsystem-id: 0000024d
unit-address: '1f'
class-code: 00060100
revision-id: 00000003
vendor-id: 00008086
device-id: 00002917
name: 'pci1028,24d'
Node 0x000017
assigned-addresses: 8100fa10.00000000.00006e70.00000000.00000008.8100fa14.00000000.00006e78.00000000.00000004.8100fa18.00000000.00006e80.00000000.00000008.8100fa1c.00000000.00006e88.00000000.00000004.8100fa20.00000000.00006ea0.00000000.00000020.8200fa24.00000000.fed1c800.00000000.00000800
reg: 0000fa00.00000000.00000000.00000000.00000000.0100fa10.00000000.00000000.00000000.00000008.0100fa14.00000000.00000000.00000000.00000004.0100fa18.00000000.00000000.00000000.00000008.0100fa1c.00000000.00000000.00000000.00000004.0100fa20.00000000.00000000.00000000.00000020.0200fa24.00000000.00000000.00000000.00000800
compatible: 'pci8086,2929.1028.24d.3' + 'pci8086,2929.1028.24d' + 'pci1028,24d' + 'pci8086,2929.3' + 'pci8086,2929' + 'pciclass,010601' + 'pciclass,0106'
model: 'SATA AHCI 1.0 Interface'
power-consumption: 00000001.00000001
66mhz-capable:
fast-back-to-back:
devsel-speed: 00000001
interrupts: 00000004
max-latency: 00000000
min-grant: 00000000
subsystem-vendor-id: 00001028
subsystem-id: 0000024d
unit-address: '1f,2'
class-code: 00010601
revision-id: 00000003
vendor-id: 00008086
device-id: 00002929
name: 'pci1028,24d'
Node 0x000018
assigned-addresses: 8300fb10.00000000.f6adaf00.00000000.00000100.8100fb20.00000000.00001100.00000000.00000020
reg: 0000fb00.00000000.00000000.00000000.00000000.0300fb10.00000000.00000000.00000000.00000100.0100fb20.00000000.00000000.00000000.00000020
compatible: 'pci8086,2930.1028.24d.3' + 'pci8086,2930.1028.24d' + 'pci1028,24d' + 'pci8086,2930.3' + 'pci8086,2930' + 'pciclass,0c0500' + 'pciclass,0c05'
model: 'SMBus (System Management Bus)'
power-consumption: 00000001.00000001
fast-back-to-back:
devsel-speed: 00000001
interrupts: 00000002
max-latency: 00000000
min-grant: 00000000
subsystem-vendor-id: 00001028
subsystem-id: 0000024d
unit-address: '1f,3'
class-code: 000c0500
revision-id: 00000003
vendor-id: 00008086
device-id: 00002930
name: 'pci1028,24d'
[-- Attachment #2: winmail.dat --]
[-- Type: application/ms-tnef, Size: 7564 bytes --]
^ permalink raw reply [flat|nested] 12+ messages in thread
* Re: [9fans] Dell E4300?
2009-08-15 20:19 [9fans] Dell E4300? Benjamin Huntsman
2009-08-15 21:34 ` erik quanstrom
@ 2009-08-16 16:36 ` erik quanstrom
2009-08-16 18:51 ` Benjamin Huntsman
1 sibling, 1 reply; 12+ messages in thread
From: erik quanstrom @ 2009-08-16 16:36 UTC (permalink / raw)
To: 9fans
there's a new ftp://ftp.quanstro.net/other/9atom.iso.bz2
> It has on-board SATA hd, SATA cd-rom, etc. I tried quanstro's 9atom.iso, and with the SATA controller in AHCI mode, it'll start booting, but hangs at:
>
> 45555 => 818807+1020832+474972=2314611
> entry: f0100020
>
> Plan 9
okay. i allowed the kernel to use the e820 scan
that 9load-e820 uses instead of using reamode
itself. this may not help, but it's a good guess,
anway. your machine appears to be crashing
during the e820 scan.
also,
> I also tried booting from Erik's atom iso, but don't get very far. eg:
> PBS1
> Plan 9 from Bell Labs
> ELCR: 0CA0
> pcirouting: south bridge 10de, 0260 not found
> aoepnp(<nil>)
> found 11 e820 entries
> Boot devices: fd0 fd1
> boot from:
>
> It doesn't detect IDE controller, so no local disk/CD-ROM to boot from.
fixed. sorry.
- erik
^ permalink raw reply [flat|nested] 12+ messages in thread
* Re: [9fans] Dell E4300?
2009-08-16 16:36 ` erik quanstrom
@ 2009-08-16 18:51 ` Benjamin Huntsman
2009-08-16 20:04 ` Benjamin Huntsman
2009-08-17 3:18 ` erik quanstrom
0 siblings, 2 replies; 12+ messages in thread
From: Benjamin Huntsman @ 2009-08-16 18:51 UTC (permalink / raw)
To: Fans of the OS Plan 9 from Bell Labs
[-- Attachment #1: Type: text/plain, Size: 1583 bytes --]
>there's a new ftp://ftp.quanstro.net/other/9atom.iso.bz2
The second part of your reply appears to not be directed to this issue, but something similar. I don't remember writing that.
Anyway, we're getting much further, but the boot process still dies:
.......
pat: 0107040600070406
ELCR: 0C08
pcirouting: BIOS workaround: PCI.0.29.0 at pin 1 link 4 irq 7 -> 3
pcirouting: BIOS workaround: PCI.0.29.1 at pin 2 link 5 irq 1 -> 11
pcirouting: BIOS workaround: PCI.0.29.7 at pin 1 link 4 irq 7 -> 3
pcirouting: BIOS workaround: PCI.0.26.0 at pin 1 link 4 irq 7 -> 3
pcirouting: BIOS workaround: PCI.0.26.1 at pin 2 link 5 irq 1 -> 11
pcirouting: BIOS workaround: PCI.0.27.0 at pin 1 link 5 irq 1 -> 11
#l0: i82567: 1000Mbps port 0xF6AE0000 irq 10 tu 1514: 002170b7a113
sdata: blind probe 1f0
sdata: blind probe 170
#S/sdE: ahci ich port 0xe0020800: ss 1 ncs 31 coal 1 mport 3 led 1 clo 1 ems 1
#S/sdE: ich: sata-II with 4 ports
3536M memory: 256M kernel data, 3280M user, 3905M swap
root is from (il, tcp, local)[local!bootdev/data]:
sdE0: LLBA 488,397,168 sectors
ST9250421ASG DE14 5TH05P1L [newdrive]
sdE1: LBA 0 sectors
TSSTcorp DVD+/-RW TS-U633A D200 [newdrive]
boot: can't connect to file server: '#S/sdD0' file does not exist
panic: boot process died: unknown
panic: boot process died: unknown
dumpstack disabled
cpo0: exiting
This is when attempting to use the "boot Plan 9 from this CD" option.
Booting into the "install Plan 9..." option loads the installer. I'm installing
now and will post the results.
Thanks again!!
-Ben
[-- Attachment #2: winmail.dat --]
[-- Type: application/ms-tnef, Size: 3184 bytes --]
^ permalink raw reply [flat|nested] 12+ messages in thread
* Re: [9fans] Dell E4300?
2009-08-16 18:51 ` Benjamin Huntsman
@ 2009-08-16 20:04 ` Benjamin Huntsman
2009-08-16 20:24 ` erik quanstrom
2009-08-17 3:18 ` erik quanstrom
1 sibling, 1 reply; 12+ messages in thread
From: Benjamin Huntsman @ 2009-08-16 20:04 UTC (permalink / raw)
To: Fans of the OS Plan 9 from Bell Labs
[-- Attachment #1: Type: text/plain, Size: 382 bytes --]
>I'm installing now and will post the results.
Okay, the install works perfectly, and I'm up and running!
Many thanks!
I recall reading that the CD is otherwise identical to the "stock"
version. So, if I recompile the kernel, it'll break, right? What
utterances do I need to enter in order to rebuild the kernel as it
appears on the 9atom cd?
Thanks again!!
-Ben
[-- Attachment #2: winmail.dat --]
[-- Type: application/ms-tnef, Size: 2556 bytes --]
^ permalink raw reply [flat|nested] 12+ messages in thread
* Re: [9fans] Dell E4300?
2009-08-16 20:04 ` Benjamin Huntsman
@ 2009-08-16 20:24 ` erik quanstrom
0 siblings, 0 replies; 12+ messages in thread
From: erik quanstrom @ 2009-08-16 20:24 UTC (permalink / raw)
To: 9fans
> I recall reading that the CD is otherwise identical to the "stock"
> version. So, if I recompile the kernel, it'll break, right? What
> utterances do I need to enter in order to rebuild the kernel as it
> appears on the 9atom cd?
the short answer is that you can't, exactly — yet.
here's the original post, which should answer your questions.
http://9fans.net/archive/2009/08/359
interestingly, googling for this with
site:9fans.net/archive/2009/08 PAT
returns nothing.
- erik
^ permalink raw reply [flat|nested] 12+ messages in thread
* Re: [9fans] Dell E4300?
2009-08-16 18:51 ` Benjamin Huntsman
2009-08-16 20:04 ` Benjamin Huntsman
@ 2009-08-17 3:18 ` erik quanstrom
2009-08-19 2:59 ` Fernan Bolando
1 sibling, 1 reply; 12+ messages in thread
From: erik quanstrom @ 2009-08-17 3:18 UTC (permalink / raw)
To: 9fans
> boot: can't connect to file server: '#S/sdD0' file does not exist
> panic: boot process died: unknown
> panic: boot process died: unknown
> dumpstack disabled
> cpo0: exiting
fixed. you should now be able to boot from the cd regardless
of which port you've plugged it into sdE5 should be fine.
> I recall reading that the CD is otherwise identical to the "stock"
> version. So, if I recompile the kernel, it'll break, right? What
> utterances do I need to enter in order to rebuild the kernel as it
> appears on the 9atom cd?
so, while i recommend that the contrib packages be used instead,
after some thought and a few hrs of quality time removing half-finished
bits, i packaged up the source used to build the 9atom kernels.
ftp://ftp.quanstro.net/other/kernel.mkfs.bz2
to extract to the current directory
bunzip2 < kernel.mkfs.bz2 | disk/mext -d .
if anyone objects to this being out there, i'll just remove it.
off the top of my head, this kernel has the following little
bits in addition to tje contrib packages:
- jumbo frames, used with aoe (#l0/ether0/mtu),
- /dev/cputemp on modern amd and intel processors,
- kbd led control, repluggable ps/2 mice, cec console server,
- console on non-onboard serial lines, turning serial console on/off,
- pat,
- /dev/nomp (mp irqs off), and /dev/mpirq (irqs turned on),
the kernel you build will *still* be a little different than mine
because of some changes to libauthsrv i made. these differences
are in the patch "readnvram" that allow nvram to be on any sd
device. this is particularly useful for ahci laptops that may have
sdE2 (cdrom) and sdE3 (hd). while they could have been added
to the big array in libauthsrv.c/nvram, i found it hard to manage.
- erik
^ permalink raw reply [flat|nested] 12+ messages in thread
* Re: [9fans] Dell E4300?
2009-08-17 3:18 ` erik quanstrom
@ 2009-08-19 2:59 ` Fernan Bolando
2009-08-19 3:13 ` erik quanstrom
[not found] ` <98019b81f174f69cfceed5718c7f6912@quanstro.net>
0 siblings, 2 replies; 12+ messages in thread
From: Fernan Bolando @ 2009-08-19 2:59 UTC (permalink / raw)
To: Fans of the OS Plan 9 from Bell Labs
On Mon, Aug 17, 2009 at 11:18 AM, erik quanstrom<quanstro@quanstro.net> wrote:
>> boot: can't connect to file server: '#S/sdD0' file does not exist
>> panic: boot process died: unknown
>> panic: boot process died: unknown
>> dumpstack disabled
>> cpo0: exiting
>
> fixed. you should now be able to boot from the cd regardless
> of which port you've plugged it into sdE5 should be fine.
>
>> I recall reading that the CD is otherwise identical to the "stock"
>> version. So, if I recompile the kernel, it'll break, right? What
>> utterances do I need to enter in order to rebuild the kernel as it
>> appears on the 9atom cd?
>
> so, while i recommend that the contrib packages be used instead,
> after some thought and a few hrs of quality time removing half-finished
> bits, i packaged up the source used to build the 9atom kernels.
> ftp://ftp.quanstro.net/other/kernel.mkfs.bz2
> to extract to the current directory
> bunzip2 < kernel.mkfs.bz2 | disk/mext -d .
> if anyone objects to this being out there, i'll just remove it.
>
> off the top of my head, this kernel has the following little
> bits in addition to tje contrib packages:
> - jumbo frames, used with aoe (#l0/ether0/mtu),
> - /dev/cputemp on modern amd and intel processors,
> - kbd led control, repluggable ps/2 mice, cec console server,
> - console on non-onboard serial lines, turning serial console on/off,
> - pat,
> - /dev/nomp (mp irqs off), and /dev/mpirq (irqs turned on),
>
> the kernel you build will *still* be a little different than mine
> because of some changes to libauthsrv i made. these differences
> are in the patch "readnvram" that allow nvram to be on any sd
> device. this is particularly useful for ahci laptops that may have
> sdE2 (cdrom) and sdE3 (hd). while they could have been added
> to the big array in libauthsrv.c/nvram, i found it hard to manage.
>
Does this include the cd writer bug fixed that we had recently?
Will i break my installation if I do replica/pull?
I dont know how much work it would be, I have always felt the openbsd
way of releasing snapshot seems very effective and replica + contrib
will make the whole process even more effective.
--
http://www.fernski.com
^ permalink raw reply [flat|nested] 12+ messages in thread
* Re: [9fans] Dell E4300?
2009-08-19 2:59 ` Fernan Bolando
@ 2009-08-19 3:13 ` erik quanstrom
[not found] ` <98019b81f174f69cfceed5718c7f6912@quanstro.net>
1 sibling, 0 replies; 12+ messages in thread
From: erik quanstrom @ 2009-08-19 3:13 UTC (permalink / raw)
To: fernanbolando, 9fans
> Does this include the cd writer bug fixed that we had recently?
i'm not sure what you're referring to. it includes all
the fixes that have been made.
> Will i break my installation if I do replica/pull?
it should not. local changes are supposed to be
preserved. i have not tried a pull myself.
- erik
^ permalink raw reply [flat|nested] 12+ messages in thread
* Re: [9fans] Dell E4300?
[not found] ` <98019b81f174f69cfceed5718c7f6912@quanstro.net>
@ 2009-08-19 3:24 ` Fernan Bolando
2009-08-19 3:30 ` erik quanstrom
0 siblings, 1 reply; 12+ messages in thread
From: Fernan Bolando @ 2009-08-19 3:24 UTC (permalink / raw)
To: 9fans
On Wed, Aug 19, 2009 at 11:13 AM, erik quanstrom<quanstro@quanstro.net> wrote:
>> Does this include the cd writer bug fixed that we had recently?
>
> i'm not sure what you're referring to. it includes all
> the fixes that have been made.
I was referring to this thread
http://9fans.net/archive/2009/08/330
>> Will i break my installation if I do replica/pull?
>
> it should not. local changes are supposed to be
> preserved. i have not tried a pull myself.
>
The only reason I want to do a pull is to have fix for the bug above.
If it is already in there
then I need to pull
thanks again
fernan
--
http://www.fernski.com
^ permalink raw reply [flat|nested] 12+ messages in thread
* Re: [9fans] Dell E4300?
2009-08-19 3:24 ` Fernan Bolando
@ 2009-08-19 3:30 ` erik quanstrom
0 siblings, 0 replies; 12+ messages in thread
From: erik quanstrom @ 2009-08-19 3:30 UTC (permalink / raw)
To: fernanbolando, 9fans
On Tue Aug 18 23:25:51 EDT 2009, fernanbolando@mailc.net wrote:
> On Wed, Aug 19, 2009 at 11:13 AM, erik quanstrom<quanstro@quanstro.net> wrote:
> >> Does this include the cd writer bug fixed that we had recently?
> >
> > i'm not sure what you're referring to. it includes all
> > the fixes that have been made.
>
> I was referring to this thread
> http://9fans.net/archive/2009/08/330
this fix is not on the kernel in sources yet,
but it is on 9atom.iso and it is in the
kernel source in the same directory.
but i wouldn't worry about it. i was the
first person to trip on that (and care)
in 20 years.
- erik
^ permalink raw reply [flat|nested] 12+ messages in thread
end of thread, other threads:[~2009-08-19 3:30 UTC | newest]
Thread overview: 12+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2009-08-15 20:19 [9fans] Dell E4300? Benjamin Huntsman
2009-08-15 21:34 ` erik quanstrom
2009-08-15 22:41 ` Benjamin Huntsman
2009-08-16 16:36 ` erik quanstrom
2009-08-16 18:51 ` Benjamin Huntsman
2009-08-16 20:04 ` Benjamin Huntsman
2009-08-16 20:24 ` erik quanstrom
2009-08-17 3:18 ` erik quanstrom
2009-08-19 2:59 ` Fernan Bolando
2009-08-19 3:13 ` erik quanstrom
[not found] ` <98019b81f174f69cfceed5718c7f6912@quanstro.net>
2009-08-19 3:24 ` Fernan Bolando
2009-08-19 3:30 ` erik quanstrom
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).