Re: [9fans] Dell E4300?
On Tue Aug 18 23:25:51 EDT 2009, fernanbola...@mailc.net wrote: > On Wed, Aug 19, 2009 at 11:13 AM, erik quanstrom 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
Re: [9fans] Dell E4300?
On Wed, Aug 19, 2009 at 11:13 AM, erik quanstrom 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
Re: [9fans] Dell E4300?
> 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
Re: [9fans] Dell E4300?
On Mon, Aug 17, 2009 at 11:18 AM, erik quanstrom 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
Re: [9fans] Dell E4300?
> 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
Re: [9fans] Dell E4300?
> 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
Re: [9fans] Dell E4300?
>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 <>
Re: [9fans] Dell E4300?
>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 0xF6AE 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 <>
Re: [9fans] Dell E4300?
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: > > 4 => 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() > 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
Re: [9fans] Dell E4300?
>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 0x01 bios-boot-device: '82' stdout: name: 'i86pc' Node 0x02 existing: 00db2000..0bc58801. name: 'ramdisk' Node 0x03 bus-type: 'isa' device_type: 'isa' name: 'isa' Node 0x04 compatible: 'pciex_root_complex' device_type: 'pciex' reg: .. #size-cells: 0002 #address-cells: 0003 name: 'pci' Node 0x05 reg: .... compatible: 'pci8086,2a40.1028.24d.7' + 'pci8086,2a40.1028.24d' + 'pci1028,24d' + 'pci8086,2a40.7' + 'pci8086,2a40' + 'pciclass,06' + 'pciclass,0600' model: 'Host bridge' power-consumption: 0001.0001 fast-back-to-back: devsel-speed: max-latency: min-grant: subsystem-vendor-id: 1028 subsystem-id: 024d unit-address: '0' class-code: 0006 revision-id: 0007 vendor-id: 8086 device-id: 2a40 name: 'pci1028,24d' Node 0x06 assigned-addresses: 83001010..f6c0..0040.c3001018..e000..1000.81001020..ef98..0008.a1001000..03b0..000c.a1001000..03c0..0020.82001000..000a..0002 reg: 1000.....03001010....0040.43001018....1000.01001020....0008.a1001000..03b0..000c.a1001000..03c0..0020.82001000..000a..0002 compatible: 'pci8086,2a42.1028.24d.7' + 'pci8086,2a42.1028.24d' + 'pci1028,24d' + 'pci8086,2a42.7' + 'pci8086,2a42' + 'pciclass,03' + 'pciclass,0300' model: 'VGA compatible controller' power-consumption: 0001.0001 fast-back-to-back: devsel-speed: interrupts: 0001 max-latency: min-grant: subsystem-vendor-id: 1028 subsystem-id: 024d device_type: 'display' unit-address: '2' class-code: 0003 revision-id: 0007 vendor-id: 8086 device-id: 2a42 name: 'display' Node 0x07 assigned-addresses: 83001110..f6b0..0010 reg: 1100.....03001110....0010 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: 0001.0001 fast-back-to-back: devsel-speed: max-latency: min-grant: subsystem-vendor-id: 1028 subsystem-id: 024d unit-address: '2,1' class-code: 00038000 revision-id: 0007 vendor-id: 8086 device-id: 2a43 name: 'pci1028,24d' Node 0x08 assigned-addresses: 8200c810..f6ae..0002.8200c814..f6adb000..1000.8100c818..efe0..0020 reg: c800.....0200c810....0002.0200c814....1000.0100c818....0020 compatible: 'pci8086,10f5.1028.24d.3' + 'pci8086,10f5.1028.24d' + 'pci1028,24d' + 'pci8086,10f5.3' + 'pci8086,10f5' + 'pciclass,02' + 'pciclass,0200' model: 'Ethernet controller' power-consumption: 0001.0001 devsel-speed: interrupts: 0001 max-latency: min-grant: subsystem-vendor-id: 1028
Re: [9fans] Dell E4300?
> 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: > > 4 => 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
[9fans] Dell E4300?
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: 4 => 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
