Soekris Net 5501 & RT2860/2850 hangs in 4.6-beta
I've been trying to use a Soekris Net5501 with a ral PCI card for a
wireless access point. I'm running the most recent snapshot but I'm
still getting the weird hangs that people were reporting on misc@ back
in 4.4.
Doing heavy traffic through the Soekris (e.g. ftp a large file) will
consistently and predictably cause the system to hang; whether the
traffic is through ral0 or not doesn't matter. If ral0 is up and in
hostAP mode, a large ftp transfer or similar traffic load will hang
the system. When the hang happens, even the console becomes
unresponsive (and thus I can't give you ddb output.)
I've tried everything I can to narrow down the problem, but I'm not
getting anywhere. I would REALLY like to get this problem fixed; any
help would be greatly appreciated. If the devs need something on my
end (testing, equipment, beer money), I'll be happy to accommodate,
just let me know.
Below is a dmesg and what I've tried so far.
*Using or not using wpa doesn't change anything
*The power supply is not an issue; I've tried half a dozen different
ones and the get the same hang.
*I couldn't make the hang happen in BSS mode or when ral0 was down.
*Making ral be part of a bridge doesn't change anything.
*I couldn't get the console to give me ddb access after the hang, so I
tried sending it a break before and then "c". I get that far, but
when the system hangs ddb is unresponsive.
OpenBSD 4.6-beta (GENERIC) #29: Sat Jun 27 18:37:05 MDT 2009
dera...@i386.openbsd.org:/usr/src/sys/arch/i386/compile/GENERIC
cpu0: Geode(TM) Integrated Processor by AMD PCS ("AuthenticAMD"
586-class) 500 MHz
cpu0: FPU,DE,PSE,TSC,MSR,CX8,SEP,PGE,CMOV,CFLUSH,MMX
real mem = 536440832 (511MB)
avail mem = 509902848 (486MB)
mainbus0 at root
bios0 at mainbus0: AT/286+ BIOS, date 20/80/26, BIOS32 rev. 0 @ 0xfac40
pcibios0 at bios0: rev 2.0 @ 0xf/0x1
pcibios0: pcibios_get_intr_routing - function not supported
pcibios0: PCI IRQ Routing information unavailable.
pcibios0: PCI bus #0 is the last bus
bios0: ROM list: 0xc8000/0xa800
cpu0 at mainbus0: (uniprocessor)
amdmsr0 at mainbus0
pci0 at mainbus0 bus 0: configuration mode 1 (bios)
io address conflict 0x6100/0x100
io address conflict 0x6200/0x200
extent `pciio' (0x0 - 0x), flags=0
0x6000 - 0x7fff
0xe000 - 0xe00f
0xe100 - 0xe4ff
0x1 - 0x
extent `pcimem' (0x0 - 0x), flags=0
0x0 - 0x9
0xf - 0x1fff
0xa000 - 0xa00043ff
0xa001 - 0xa0021fff
0xfff0 - 0x
pchb0 at pci0 dev 1 function 0 "AMD Geode LX" rev 0x33
glxsb0 at pci0 dev 1 function 2 "AMD Geode LX Crypto" rev 0x00: RNG AES
vr0 at pci0 dev 6 function 0 "VIA VT6105M RhineIII" rev 0x96: irq 11,
address 00:00:24:cc:10:7c
ukphy0 at vr0 phy 1: Generic IEEE 802.3u media interface, rev. 3: OUI
0x004063, model 0x0034
vr1 at pci0 dev 7 function 0 "VIA VT6105M RhineIII" rev 0x96: irq 5,
address 00:00:24:cc:10:7d
ukphy1 at vr1 phy 1: Generic IEEE 802.3u media interface, rev. 3: OUI
0x004063, model 0x0034
vr2 at pci0 dev 8 function 0 "VIA VT6105M RhineIII" rev 0x96: irq 9,
address 00:00:24:cc:10:7e
ukphy2 at vr2 phy 1: Generic IEEE 802.3u media interface, rev. 3: OUI
0x004063, model 0x0034
vr3 at pci0 dev 9 function 0 "VIA VT6105M RhineIII" rev 0x96: irq 12,
address 00:00:24:cc:10:7f
ukphy3 at vr3 phy 1: Generic IEEE 802.3u media interface, rev. 3: OUI
0x004063, model 0x0034
ral0 at pci0 dev 14 function 0 "Ralink RT2860" rev 0x00: irq 10,
address 00:1e:e5:e8:ea:c9
ral0: MAC/BBP RT2860 (rev 0x0103), RF RT2850 (MIMO 2T2R)
glxpcib0 at pci0 dev 20 function 0 "AMD CS5536 ISA" rev 0x03: rev 0,
32-bit 3579545Hz timer, watchdog, gpio
gpio0 at glxpcib0: 32 pins
pciide0 at pci0 dev 20 function 2 "AMD CS5536 IDE" rev 0x01: DMA,
channel 0 wired to compatibility, channel 1 wired to compatibility
wd0 at pciide0 channel 0 drive 0:
wd0: 4-sector PIO, LBA, 1953MB, 4001760 sectors
wd0(pciide0:0:0): using PIO mode 4, DMA mode 2
pciide0: channel 1 ignored (disabled)
ohci0 at pci0 dev 21 function 0 "AMD CS5536 USB" rev 0x02: irq 15,
version 1.0, legacy support
ehci0 at pci0 dev 21 function 1 "AMD CS5536 USB" rev 0x02: irq 15
usb0 at ehci0: USB revision 2.0
uhub0 at usb0 "AMD EHCI root hub" rev 2.00/1.00 addr 1
isa0 at glxpcib0
isadma0 at isa0
com0 at isa0 port 0x3f8/8 irq 4: ns16550a, 16 byte fifo
com0: console
com1 at isa0 port 0x2f8/8 irq 3: ns16550a, 16 byte fifo
pckbc0 at isa0 port 0x60/5
pckbd0 at pckbc0 (kbd slot)
pckbc0: using irq 1 for kbd slot
wskbd0 at pckbd0: console keyboard
pcppi0 at isa0 port 0x61
midi0 at pcppi0:
spkr0 at pcppi0
nsclpcsio0 at isa0 port 0x2e/2: NSC PC87366 rev 9: GPIO VLM TMS
gpio1 at nsclpcsio0: 29 pins
npx0 at isa0 port 0xf0/16: reported by CPUID; using exception 16
usb1 at ohci0: USB revision 1.0
uhub1 at usb1 "AMD OHCI root hub" rev 1.00/1.00 addr 1
biomask e1c5 netmask ffe5 ttymask
mtrr: K6-family MTRR support (2 registers)
softraid0 at root
root on wd0a swap on wd0b dump on wd0b
WARNING: / was not properly unmounted
Curso EMDR Parte I.
Sociedad Argentina de Psicotrauma y Centro de Estris Traumatico de la UBA Auspician Entrenamiento en Tratamientos Eficaces: EMDR (Francine Shapiro Ph.D.) Modelo Psicoterapiutico considerado en la actualidad convencional y reconocido en todo el mundo por su eficacia en el tratamiento del trauma. Entrenamiento Basico, Parte 1 de 2 Viernes 14, sabado 15, y domingo 16 de Agosto. Bases tesricas, practica y procedimiento actualizados a marzo de 2009. El entrenamiento esta dirigido exclusivamente a profesionales de la Salud Mental (midicos y psicslogos) interesados en una aplicacisn estricta de sus procedimientos. EMDR puede ser integrado a otras formas de psicoterapia siguiendo rigurosos procedimientos validados. Doble certificacisn de EMDR Institute Inc. (USA) y SAPsi (Sociedad Argentina de Psicotrauma) Informes e inscripcisn: entrenamientose...@gmail.com Mas informacisn acerca del modelo EMDR y los entrenamientos en: www.psicoterapiastrauma.com.ar El horario de cursada es de 9 a 19 hs. los tres dmas del entrenamiento. Aranceles segzn fecha de inscripcisn: $700 hasta el 16/07 $750 hasta el 23/07 $800 hasta la fecha del entrenamiento Ofrecemos descuentos por inscripciones grupales Los 10 primeros inscriptos obtendran aranceles preferenciales de $600 (valido hasta el 9/07) Lugar: SAPsi Campichuelo 215 (C1405BOA) Ciudad de Buenos Aires - Argentina Telefax (005411) 4903-0493
Re: New disklable doesn't keep old partitions if requested
This whole thread is actually one more proof that nobody ever reads the installation notes (INSTALL.*). Miod
Re: New disklable doesn't keep old partitions if requested
Hi Matthew > Use 'n' instead of 'm' to provide the needed mount points. That address my question. An obvious over site on my part! I never used it until today as far back as version 2.8. > With the old installer, while in the disk label editor, you could name > your mount points while creating (command 'a') or modifying (command 'm') > your partitions, or you could just name the mount points for existing > partitions without otherwise those partitions (command 'n'). I see that now. > After you finished the disk label editor, the old installer would then > prompt you to name your mount points. If you'd already named them in the > disk label editor, this was redundant. The new installer removes the > redundancy and requires that you name your mount points in the editor. That's where my confusion came from. I wrongly assume that you create the partitions and then named them after the fact. I was obviously wrong and made the wrong assumptions here. > When you choose "C" for a custom layout, the installer shows you this: > > -- > You will now create an OpenBSD disklabel inside the OpenBSD MBR > partition. The disklabel defines how OpenBSD splits up the MBR partition > into OpenBSD partitions in which filesystems and swap space are created. > You must provide each filesystem's mountpoint in this program. > -- > > Note the last sentence. I saw that one and obviously read it, but didn't sync in for me. Based on previous years, I assume that, yes you need to partition your disk and then obviously will also need to provide the mount point when you are done. Before, you could provide them after the fact like you explain and obviously was a miss understanding of the process on my part that you clarify for me. Sorry for the noise. And Theo, I am truly sorry you got upset on this question from me here. I obviously failed to understand it properly and that's why I asked the question. My apology for your increase in temper cause by my question, but I just obviously didn't get it right and this clear it up for me. I was obviously wrongly looking for the installer asking me for the mount point as before, witch I see now was wrong to assume on my part. Thanks for your time and clarification on my miss understanding. One need to be ready to get a beat up to get clarifications, but that's fine. And Theo, I NEVER intended to make you waste time here. It was an honest miss understanding on my part obviously. Best regards, Daniel
Re: i386 snapshot kernel crash (intagp)
No idea ?
Le Thu, 2 Jul 2009 19:43:22 +0200,
Julien Cabillot a C)crit :
> Hi,
> I'm have a problem with the latest snapshot (1er july), the kernel crash on
> intagp,
> I don't have serial connected so I take a little picture :
> http://img33.imageshack.us/img33/6628/img4400g.jpg
> And trace give that :
> http://img194.imageshack.us/img194/8093/img4402s.jpg
>
> My last update (25 Jun) work nice (it's a GENERIC.MP + raidframe).
>
> OpenBSD 4.5 (GENERIC.MP) #0: Thu Jun 25 20:33:02 CEST 2009
> root@:/usr/sys/arch/i386/compile/GENERIC.MP
> cpu0: Intel(R) Core(TM)2 CPU 6400 @ 2.13GHz ("GenuineIntel" 686-class) 2.14
> GHz
> cpu0:
>
FPU,V86,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,CFLUS
>
H,DS,ACPI,MMX,FXSR,SSE,SSE2,SS,HTT,TM,SBF,SSE3,MWAIT,DS-CPL,VMX,EST,TM2,CX16,
> xTPR
> real mem = 1070034944 (1020MB)
> avail mem = 1025949696 (978MB)
> mainbus0 at root
> bios0 at mainbus0: AT/286+ BIOS, date 08/20/08, BIOS32 rev. 0 @ 0xfb210,
> SMBIOS rev. 2.4 @ 0xf0100 (34 entries)
> bios0: vendor Award Software International, Inc. version "F4" date
08/20/2008
> bios0: Gigabyte Technology Co., Ltd. G31M-ES2L
> acpi0 at bios0: rev 0
> acpi0: tables DSDT FACP HPET MCFG APIC SSDT
> acpi0: wakeup devices PEX0(S5) PEX1(S5) PEX2(S5) PEX3(S5) PEX4(S5) PEX5(S5)
> HUB0(S5) UAR1(S3) USB0(S3) USB1(S3) USB2(S3) USB3(S3) USBE(S3) AZAL(S5)
> PCI0(S5)
> acpitimer0 at acpi0: 3579545 Hz, 24 bits
> acpihpet0 at acpi0: 14318179 Hz
> acpimadt0 at acpi0 addr 0xfee0: PC-AT compat
> cpu0 at mainbus0: apid 0 (boot processor)
> cpu0: apic clock running at 266MHz
> cpu1 at mainbus0: apid 1 (application processor)
> cpu1: Intel(R) Core(TM)2 CPU 6400 @ 2.13GHz ("GenuineIntel" 686-class) 2.14
> GHz
> cpu1:
>
FPU,V86,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,CFLUS
>
H,DS,ACPI,MMX,FXSR,SSE,SSE2,SS,HTT,TM,SBF,SSE3,MWAIT,DS-CPL,VMX,EST,TM2,CX16,
> xTPR
> ioapic0 at mainbus0: apid 2 pa 0xfec0, version 20, 24 pins
> ioapic0: misconfigured as apic 0, remapped to apid 2
> acpiprt0 at acpi0: bus 0 (PCI0)
> acpiprt1 at acpi0: bus 1 (PEX0)
> acpiprt2 at acpi0: bus 2 (PEX1)
> acpiprt3 at acpi0: bus -1 (PEX2)
> acpiprt4 at acpi0: bus -1 (PEX3)
> acpiprt5 at acpi0: bus -1 (PEX4)
> acpiprt6 at acpi0: bus -1 (PEX5)
> acpiprt7 at acpi0: bus 3 (HUB0)
> acpicpu0 at acpi0
> acpicpu1 at acpi0
> acpibtn0 at acpi0: PWRB
> bios0: ROM list: 0xc/0xb400!
> pci0 at mainbus0 bus 0: configuration mode 1 (bios)
> pchb0 at pci0 dev 0 function 0 "Intel 82G33 Host" rev 0x10
> vga1 at pci0 dev 2 function 0 "Intel 82G33 Video" rev 0x10
> wsdisplay0 at vga1 mux 1: console (80x25, vt100 emulation)
> wsdisplay0: screen 1-5 added (80x25, vt100 emulation)
> intagp0 at vga1
> agp0 at intagp0: aperture at 0xd000, size 0x1000
> inteldrm0 at vga1: apic 2 int 16 (irq 5)
> drm0 at inteldrm0
> azalia0 at pci0 dev 27 function 0 "Intel 82801GB HD Audio" rev 0x01: apic 2
> int 16 (irq 5)
> azalia0: codecs: Realtek ALC883
> audio0 at azalia0
> ppb0 at pci0 dev 28 function 0 "Intel 82801GB PCIE" rev 0x01: apic 2 int 16
> (irq 5)
> pci1 at ppb0 bus 1
> ppb1 at pci0 dev 28 function 1 "Intel 82801GB PCIE" rev 0x01: apic 2 int 17
> (irq 10)
> pci2 at ppb1 bus 2
> re0 at pci2 dev 0 function 0 "Realtek 8168" rev 0x02: RTL8168C/8111C
(0x3c00),
> apic 2 int 17 (irq 10), address 00:1f:d0:14:72:b2
> rgephy0 at re0 phy 7: RTL8169S/8110S PHY, rev. 2
> uhci0 at pci0 dev 29 function 0 "Intel 82801GB USB" rev 0x01: apic 2 int 23
> (irq 7)
> uhci1 at pci0 dev 29 function 1 "Intel 82801GB USB" rev 0x01: apic 2 int 19
> (irq 11)
> uhci2 at pci0 dev 29 function 2 "Intel 82801GB USB" rev 0x01: apic 2 int 18
> (irq 3)
> uhci3 at pci0 dev 29 function 3 "Intel 82801GB USB" rev 0x01: apic 2 int 16
> (irq 5)
> ehci0 at pci0 dev 29 function 7 "Intel 82801GB USB" rev 0x01: apic 2 int 23
> (irq 7)
> usb0 at ehci0: USB revision 2.0
> uhub0 at usb0 "Intel EHCI root hub" rev 2.00/1.00 addr 1
> ppb2 at pci0 dev 30 function 0 "Intel 82801BA Hub-to-PCI" rev 0xe1
> pci3 at ppb2 bus 3
> ichpcib0 at pci0 dev 31 function 0 "Intel 82801GB LPC" rev 0x01: PM
disabled
> pciide0 at pci0 dev 31 function 1 "Intel 82801GB IDE" rev 0x01: DMA, channel
0
> configured to compatibility, channel 1 configured to compatibility
> wd0 at pciide0 channel 0 drive 0:
> wd0: 16-sector PIO, LBA48, 152626MB, 312579695 sectors
> wd1 at pciide0 channel 0 drive 1:
> wd1: 16-sector PIO, LBA48, 78533MB, 160836480 sectors
> wd0(pciide0:0:0): using PIO mode 4, Ultra-DMA mode 5
> wd1(pciide0:0:1): using PIO mode 4, Ultra-DMA mode 5
> pciide0: channel 1 disabled (no drives)
> pciide1 at pci0 dev 31 function 2 "Intel 82801GB SATA" rev 0x01: DMA,
channel
> 0 configured to native-PCI, channel 1 configured to native-PCI
> pciide1: using apic 2 int 19 (irq 11) for native-PCI interrupt
> wd2 at pciide1 channel 0 drive 0:
> wd2: 16-sector PIO, LBA48, 238475MB, 488397168 sectors
> wd2(pciide1:0:0): using PIO mode 4, Ultra-DMA mode 5
> wd3 at pciide1 channel 1 drive 0:
> wd3: 16-sector PIO, LBA48, 238475MB, 48
Re: New disklable doesn't keep old partitions if requested
Hi Daniel, It appears as if you're still confused. Specifiy the mount points within disklabel using 'm' or 'n' has been standard proceedure for some time. Some users skipped this and waited for the confirmation prompts after quiting disklabel. This was deemed redundant, users can already specify the mount points from within disklabel. You cannot do that anymore, using 'n' as Theo suggessted might save you some "time". HTH. -Brynet
Re: New disklable doesn't keep old partitions if requested
Sat, Sep 05, 2009 at 10:13:05PM -0400, Daniel Ouellet may have written: > > You need to learn how to listen. > > That's fair Theo. > > But to make it short. Before when at the disklabel part of the install, one > could just type 'q' and it was then asked for the mount point of that actual > unchanged partition as before and skip the 'm' steps if you want. Now you > can't > just type 'q' and do this, but needs to do 'm' for each partitions and keep > the > same size, offset, etc the same and provide then the mount point, then save, > quit and keep going. > > If there is a way to skip these additional steps using 'm' on disk unchanged > partition between install and just need to type 'q' as before and provide the > needed mount points obviously, I would like to know how now? > > Doesn't appear to be possible anymore. Am I wrong? > > Best, > > Daniel Use 'n' instead of 'm' to provide the needed mount points. With the old installer, while in the disk label editor, you could name your mount points while creating (command 'a') or modifying (command 'm') your partitions, or you could just name the mount points for existing partitions without otherwise those partitions (command 'n'). After you finished the disk label editor, the old installer would then prompt you to name your mount points. If you'd already named them in the disk label editor, this was redundant. The new installer removes the redundancy and requires that you name your mount points in the editor. When you choose "C" for a custom layout, the installer shows you this: -- You will now create an OpenBSD disklabel inside the OpenBSD MBR partition. The disklabel defines how OpenBSD splits up the MBR partition into OpenBSD partitions in which filesystems and swap space are created. You must provide each filesystem's mountpoint in this program. -- Note the last sentence. Matt. -- ... let us keep in mind the basic governing philosophy of The Brotherhood, as handsomely summarized in these words: we believe in healthy, hearty laughter -- at the expense of the whole human race, if needs be. Needs be. -- H. Allen Smith, "Rude Jokes"
Re: per interface/route window size ?
On Sun, Jul 5, 2009 at 7:32 AM, Rick Ballard wrote: > I have my network windows set high for my 5MB cable connection, but I'd > really like a smaller window size for the wireless interface. What problem are you trying to solve and why do you think that what you describe would solve it? ... > net.inet.udp.recvspace=65535 # Increase UDP "recieve" windows size to increase performance > net.inet.udp.sendspace=65535 # Increase UDP "send" windows size to increase performance The comments on these lines make no sense; these settings have no relation to performance and almost certainly are merely wasting memory on your system. Just say no to cargo-cult tuning! Philip Guenther
Re: New disklable doesn't keep old partitions if requested
Theo de Raadt wrote: > Or 'n' Thank you. > There is a reason why the installer disklabel and fdisk commands both > have a 'M' command in them, to show the manual page. I agree, that is a handy shortcut. :-) > I am not being sarcastic. B I truly am sick of having my time wasted. Many people get frustrated when things change, but they did have the opportunity to test and influence the changes.. instead they wait until the last moment and send frustrated messages to the lists. I'm sure many here respect the time and effort you dedicate to the project and to these lists, hopefully you won't be driven away by it all. How were your Canada Day celebrations? -Brynet
Re: New disklable doesn't keep old partitions if requested
> You *NEED* to use 'm' to define mount points, this information will be passed > to the installer and won't be retained on-disk. Or 'n' There is a reason why the installer disklabel and fdisk commands both have a 'M' command in them, to show the manual page. > Hopefully you are now aware of the required steps, a native English speaker > would have noticed the sarcasm in Theo's message. I am not being sarcastic. I truly am sick of having my time wasted.
Re: New disklable doesn't keep old partitions if requested
Daniel, As made quite clear in Theo's post, a disklabel does not contain any information about mount points. All of the partitions you created in 4.5 exist, but the installer does not know where to mount them, or even if you want to. In 4.6 selecting "(C)ustom layout" will show you what's actually on-disk, if anything is. In your email, you simply type 'w' and 'q' without setting any mount points. This will obviously fail. You *NEED* to use 'm' to define mount points, this information will be passed to the installer and won't be retained on-disk. The act of not doing this will loop the installation, you will no longer be prompted to "confirm" mount points. Hopefully you are now aware of the required steps, a native English speaker would have noticed the sarcasm in Theo's message. Take care. -Brynet
Re: New disklable doesn't keep old partitions if requested
> > You need to learn how to listen. > > That's fair Theo. > > But to make it short. Before when at the disklabel part of the install, one > could just type 'q' and it was then asked for the mount point of that actual > unchanged partition as before and skip the 'm' steps if you want. You still are being asked. Do you see mountpoints on the listing with your partitions? No you don't. So why don't you set them up? I think it is because you prefer writing essays. > Am I wrong? Yes you are wrong, and damn infuriating too.
Re: New disklable doesn't keep old partitions if requested
> You need to learn how to listen. That's fair Theo. But to make it short. Before when at the disklabel part of the install, one could just type 'q' and it was then asked for the mount point of that actual unchanged partition as before and skip the 'm' steps if you want. Now you can't just type 'q' and do this, but needs to do 'm' for each partitions and keep the same size, offset, etc the same and provide then the mount point, then save, quit and keep going. If there is a way to skip these additional steps using 'm' on disk unchanged partition between install and just need to type 'q' as before and provide the needed mount points obviously, I would like to know how now? Doesn't appear to be possible anymore. Am I wrong? Best, Daniel
Re: Shooting myself, again, and not realizing it
On Sunday 05 July 2009 21:47:09 Chris Kuethe wrote: > assuming you didn't do anything like formatting the disk, you can > generally put the partition table and disk label back with no ill > effect. All is well, though I am still confused as to what happened. Thanks. --STeve Andre'
Re: Shooting myself, again, and not realizing it
> paladin ~ fdisk sd1 > Disk: sd1 geometry: 64601/240/63 [976773168 Sectors] > Offset: 0 Signature: 0x0 As of a few months ago, this is an invalid MBR. It does not have the correct signature. We now check. If it is wrong, sorry but the disklabel will not be read for that disk.
Shooting myself, again, and not realizing it
This is embarrassing. I have a second disk in my laptop which I use for storing large things (500G disk). A few weeks ago I was dealing with a bunch of USB disks, and I guess I managed to blitz sd1 (500G disk) in the process. It used to be one 'a' partition of the entire disk. When I looked just a moment ago (see data below) I have a very small part of the disk carved up for OpenBSD and no partitions. Somehow during my diskfest I worked on the wrong disk. It's not the end of the world if I don't get it back, and I do have some backups, but still. My thought is to run fdisk again and give it the entire disk and then disklabel it with the one 'a' partition. Assuming that I didn't write to the disk (I don't think I did), this should work... Right? Thanks, --STeve Andre' (red faced at the moment) [relevant data] paladin ~ fdisk sd1 Disk: sd1 geometry: 64601/240/63 [976773168 Sectors] Offset: 0 Signature: 0x0 Starting Ending LBA Info: #: id C H S - C H S [ start:size ] --- 0: 00 0 0 0 - 0 0 0 [ 0: 0 ] unused 1: 00 0 0 0 - 0 0 0 [ 0: 0 ] unused 2: 00 0 0 0 - 0 0 0 [ 0: 0 ] unused 3: A6 0 1 1 - 66 34 1 [ 63: 100 ] OpenBSD paladin ~ disklabel sd1 # /dev/rsd1c: type: SCSI disk: SCSI disk label: ST9500325AS flags: bytes/sector: 512 sectors/track: 63 tracks/cylinder: 240 sectors/cylinder: 15120 cylinders: 64601 total sectors: 976773168 rpm: 3600 interleave: 1 boundstart: 0 boundend: 976773168 drivedata: 0 16 partitions: #size offset fstype [fsize bsize cpg] c:9767731680 unused paladin ~
Re: Question about webmail for users who are not busy on ports prep for 4.6
Jacob L. Leifman wrote: So far this thread has focused on the various IMAP based solutions and the merits of the many alternate components to such. Keying off some comments in the OP (below) I would like to point out that there _is_ an OpenBSD package openwebmail-2.51p1.tgz for a non-IMAP webmail. A few of the things that I like about this solution are: - it is written entirely in perl (no php or other non-base prereqs) - it works well when deployed on the mail server or over POP3 - its interface is very clean yet fairly feature rich - it is browser agnostic and renders decently even on mobiles Again, I bring this up only because it seems to me that the original goal was a simple non-IMAP solution and this suggestion should be taken completely independent of the rest of this thread -- IMAP adds capabilities and complexities that make any comparison of solutions with and without it mostly invalid. I looked at openwebmail very seriously. Openwebmail requires apache to be run unchrooted. The other options I found were not perl based, which I like, but PHP based. I basically had to decide between PHP or unchrooting apache. Tough choice. I went with squirrelmail, which is PHP. Chroot or not chroot, that is the question!? Chris Bennett
Re: New disklable doesn't keep old partitions if requested
> > Let me guess. The last time you used this disk, partition d was your > > /home partition, right, and i is /var? > > Nope. > > Here is the standard setup on a truck load of servers. All use the same > partition table, unless there is a very special need. How would we know that? You are doing an *INSTALL* We know nothing about your practices. [paragraphs of extra text deleted] > That I totally agree, but when I do the custom, and make no changes to the > partition table, then why does it come back asking me to redo it instead of > keep > going and then I can re-enter the old mount name in the old partitions as it > used to be? Partition tables do not contain mount point information. > Same results with edit auto label as well. I can pass this pass deleting all > and > recreating all, but before (4.5 and before) I could keep the same label, and > yes > I needed to enter the mount point in label, witch was fine and I have no issue > with that or doing it. Labels do not contain mount point information. [paragraphs of moaning and complaining deleted] > That's how it was before. Is there really a need not to allow this? You need to learn how to listen.
Re: New disklable doesn't keep old partitions if requested
>> No label changes. > > Wait. Don't you see what is wrong above? > > Let me guess. The last time you used this disk, partition d was your > /home partition, right, and i is /var? Nope. Here is the standard setup on a truck load of servers. All use the same partition table, unless there is a very special need. I try to keep them all similar as much as possible and I do all fresh install every 6 months (not upgrade) using the sitexx.tgz files. It's more work to keep the sitexx.tgz files in sync, but at the same time, it provide for quick install and always run clean fresh install, plus should one server blow up, putting one back in service is just less the 10 minutes away max. And it force anyone to keep documentation of the setup, or changes of it by needing to keep sitexx.tgz in order. Here is an example here for fstab: # cat /etc/fstab /dev/wd0a / ffs rw 1 1 /dev/wd0i /data ffs rw,nodev,nosuid 1 2 /dev/wd0h /home ffs rw,nodev,nosuid 1 2 /dev/wd0d /tmp ffs rw,nodev,nosuid 1 2 /dev/wd0g /usr ffs rw,nodev 1 2 /dev/wd0e /var ffs rw,nodev,nosuid 1 2 /dev/wd0f /var/log ffs rw,nodev,nosuid 1 2 > We don't know what partition to mount where. That I totally agree, but when I do the custom, and make no changes to the partition table, then why does it come back asking me to redo it instead of keep going and then I can re-enter the old mount name in the old partitions as it used to be? Same results with edit auto label as well. I can pass this pass deleting all and recreating all, but before (4.5 and before) I could keep the same label, and yes I needed to enter the mount point in label, witch was fine and I have no issue with that or doing it. > You failed to fill in the information, using at least the 'm' command, > and then when you quit disklabel it correctly says: Theo, I failed to follow you here. Sorry if that's obvious, but I fail to see it. The man page does say the m command is to modify parameters for an existing partition. I am not creating a new one, but just want to use the old one and I have no problem if I need to re inter the mount point obviously as it needed to be done as well before. But it doesn't allow me to do so IF I do not make changes to the partition table. It does force me to do m for each partition, not changing any data other then entering the mount point. Before, I could pass this and just enter the mount point and keep going. So, I have redone it to test it and yes, I can use the m for each partitions and not modify any data for the partition size and all and just provide the mount point then when I write it and quit, it does continue the process as before. But this wasn't required before. So, if one wants to keep the same partition then before, what would be the best way then? I thought that it would be logical to do the custom selection, not making any changes to the partition table as before and then when save, just needed to type the mount point and move on. But I can't do that now without needed to use the m for each partition, not making any changes to the partition size, offset and all and then provide the mount point. >> '/' must be configured! > > Read what it says. > > The nice install script then nicely goes back to trying to see if you > will learn to read next time. I am sure not saying it's not nice. It is very nice and I like the new way for sure. I just never used to have the need to do this before. It previous version allow me to provide the name after no changes where done in the partition and the system didn't know what the partition were instead of going back to it asking to redo it all. That part of the previous install made more sense to me, but I sure can do it the new way. Instead of using the same partition table and then have to enter the mount point for each one, now it needs to use m for each partition, keep the setting the same for the size, offset and all and only enter the mount point now. It does add way more steps in that situation yes. Is that a big deal, no, just wonder why or if there was a way to skip that to be like in previous version? Wouldn't it make more sense if a custom setup is selected and no changes are done to the partition label, then to be assume the partition itself wanted to be kept intact and then only the mount label needed to be provided as before? The short of it is if you make no changes to the partition table, yes the system do not know what mount point you want, then why not only asked for the mount point then when getting out of the custom disklable part? That's how it was before. Is there really a need not to allow this? I really have no problem either way, but just wonder why or if there was a way to skip it. That was the essence of my question. Best, Daniel
Re: per interface/route window size ?
On 2009-07-05, Rick Ballard wrote: > I am running a soekris net5501 with OBSD 4.4 and a ral PCI wifi card. > > I have my network windows set high for my 5MB cable connection, but I'd > really like a smaller window size for the wireless interface. > > inet 172.16.1.254 255.255.255.0 NONE media OFDM54 mediaopt hostap mode 11g > nwid NWID nwkey NWKEY chan 1 description wifi up > [ Using WEP till I get WPA2 working with my IPOD Touch ] > > net.inet.tcp.rfc3390=1 # 0=Disable RFC3390 for TCP window > increasing > net.inet.tcp.recvspace=65535 # Increase TCP "recieve" windows size to > increase performance > net.inet.tcp.sendspace=65535 # Increase TCP "send" windows size to > increase performance > net.inet.udp.recvspace=65535 # Increase UDP "recieve" windows size to > increase performance > net.inet.udp.sendspace=65535 # Increase UDP "send" windows size to > increase performance > > ral0 at pci0 dev 14 function 0 "Ralink RT2561S" rev 0x00: irq 10, address > 00:22:6b:9b:2b:f0 > ral0: MAC/BBP RT2561C, RF RT2527 > > I have googled and rtfm'd but I cannot see how to set a per interface/route > tcp/udp window size on OpenBSD. Is this even possible ? > No, it isn't.
Re: New disklable doesn't keep old partitions if requested
> I try to keep the actual partition of the disk as it was before and do a fresh > install, but the snapshots looks like simply do not allow this now. > > You can select Custom label and it will show the previous label, but then when > you write it, obviously no changes are present, but when you Quit it, it comes > back to the same question and looks like you can't move on from there. > > Good if you want to use the auto label, but if you want to keep the old one, > then what really should be the step then? > > Here is an example: > > No label changes. > '/' must be configured! > The auto-allocated layout for wd0 is: > #size offset fstype [fsize bsize cpg] > a: 1.0G0 4.2BSD 2048 163841 # / > b: 1.3G 2097648swap > c:74.5G0 unused > d: 4.0G 4719456 4.2BSD 2048 163841 # /tmp > e: 6.0G 13109040 4.2BSD 2048 163841 # /var > f: 1.9G 25692912 4.2BSD 2048 163841 # /usr > g: 1.0G 29778336 4.2BSD 2048 163841 # /usr/X11R6 > h: 5.4G 31875984 4.2BSD 2048 163841 # /usr/local > i: 2.0G 43210944 4.2BSD 2048 163841 # /usr/src > j: 2.0G 47406240 4.2BSD 2048 163841 # /usr/obj > k:49.9G 51601536 4.2BSD 2048 163841 # /home > Use (A)uto layout, (E)dit auto layout, or create (C)ustom layout? [a] C > > You will now create a Sun-style disklabel on the disk. The disklabel defines > how OpenBSD splits up the disk into OpenBSD partitions in which filesystems > and swap space are created. You must provide each filesystem's mountpoint > in this program. > > This platform requires that partition offsets/sizes be on cylinder boundaries. > Partition offsets/sizes will be rounded to the nearest cylinder automatically. > Label editor (enter '?' for help at any prompt) > > p > OpenBSD area: 0-156301488; size: 156301488; free: 0 > #size offset fstype [fsize bsize cpg] > a: 10493280 4.2BSD 2048 163841 > b: 8389584 1049328swap > c:1563014880 unused > d: 2097648 9438912 4.2BSD 2048 163841 > e: 20972448 11536560 4.2BSD 2048 163841 > f: 2097648 32509008 4.2BSD 2048 163841 > g: 10486224 34606656 4.2BSD 2048 163841 > h: 2097648 45092880 4.2BSD 2048 163841 > i:109110960 47190528 4.2BSD 2048 163841 > > w > > q > No label changes. Wait. Don't you see what is wrong above? Let me guess. The last time you used this disk, partition d was your /home partition, right, and i is /var? We don't know what partition to mount where. You failed to fill in the information, using at least the 'm' command, and then when you quit disklabel it correctly says: > '/' must be configured! Read what it says. The nice install script then nicely goes back to trying to see if you will learn to read next time. > The auto-allocated layout for wd0 is: > #size offset fstype [fsize bsize cpg] > a: 1.0G0 4.2BSD 2048 163841 # / > b: 1.3G 2097648swap > c:74.5G0 unused > d: 4.0G 4719456 4.2BSD 2048 163841 # /tmp > e: 6.0G 13109040 4.2BSD 2048 163841 # /var > f: 1.9G 25692912 4.2BSD 2048 163841 # /usr > g: 1.0G 29778336 4.2BSD 2048 163841 # /usr/X11R6 > h: 5.4G 31875984 4.2BSD 2048 163841 # /usr/local > i: 2.0G 43210944 4.2BSD 2048 163841 # /usr/src > j: 2.0G 47406240 4.2BSD 2048 163841 # /usr/obj > k:49.9G 51601536 4.2BSD 2048 163841 # /home > Use (A)uto layout, (E)dit auto layout, or create (C)ustom layout? [a] E > This platform requires that partition offsets/sizes be on cylinder boundaries. > Partition offsets/sizes will be rounded to the nearest cylinder automatically. > Label editor (enter '?' for help at any prompt)
New disklable doesn't keep old partitions if requested
Hi, I try to keep the actual partition of the disk as it was before and do a fresh install, but the snapshots looks like simply do not allow this now. You can select Custom label and it will show the previous label, but then when you write it, obviously no changes are present, but when you Quit it, it comes back to the same question and looks like you can't move on from there. Good if you want to use the auto label, but if you want to keep the old one, then what really should be the step then? Here is an example: No label changes. '/' must be configured! The auto-allocated layout for wd0 is: #size offset fstype [fsize bsize cpg] a: 1.0G0 4.2BSD 2048 163841 # / b: 1.3G 2097648swap c:74.5G0 unused d: 4.0G 4719456 4.2BSD 2048 163841 # /tmp e: 6.0G 13109040 4.2BSD 2048 163841 # /var f: 1.9G 25692912 4.2BSD 2048 163841 # /usr g: 1.0G 29778336 4.2BSD 2048 163841 # /usr/X11R6 h: 5.4G 31875984 4.2BSD 2048 163841 # /usr/local i: 2.0G 43210944 4.2BSD 2048 163841 # /usr/src j: 2.0G 47406240 4.2BSD 2048 163841 # /usr/obj k:49.9G 51601536 4.2BSD 2048 163841 # /home Use (A)uto layout, (E)dit auto layout, or create (C)ustom layout? [a] C You will now create a Sun-style disklabel on the disk. The disklabel defines how OpenBSD splits up the disk into OpenBSD partitions in which filesystems and swap space are created. You must provide each filesystem's mountpoint in this program. This platform requires that partition offsets/sizes be on cylinder boundaries. Partition offsets/sizes will be rounded to the nearest cylinder automatically. Label editor (enter '?' for help at any prompt) > p OpenBSD area: 0-156301488; size: 156301488; free: 0 #size offset fstype [fsize bsize cpg] a: 10493280 4.2BSD 2048 163841 b: 8389584 1049328swap c:1563014880 unused d: 2097648 9438912 4.2BSD 2048 163841 e: 20972448 11536560 4.2BSD 2048 163841 f: 2097648 32509008 4.2BSD 2048 163841 g: 10486224 34606656 4.2BSD 2048 163841 h: 2097648 45092880 4.2BSD 2048 163841 i:109110960 47190528 4.2BSD 2048 163841 > w > q No label changes. '/' must be configured! The auto-allocated layout for wd0 is: #size offset fstype [fsize bsize cpg] a: 1.0G0 4.2BSD 2048 163841 # / b: 1.3G 2097648swap c:74.5G0 unused d: 4.0G 4719456 4.2BSD 2048 163841 # /tmp e: 6.0G 13109040 4.2BSD 2048 163841 # /var f: 1.9G 25692912 4.2BSD 2048 163841 # /usr g: 1.0G 29778336 4.2BSD 2048 163841 # /usr/X11R6 h: 5.4G 31875984 4.2BSD 2048 163841 # /usr/local i: 2.0G 43210944 4.2BSD 2048 163841 # /usr/src j: 2.0G 47406240 4.2BSD 2048 163841 # /usr/obj k:49.9G 51601536 4.2BSD 2048 163841 # /home Use (A)uto layout, (E)dit auto layout, or create (C)ustom layout? [a] E This platform requires that partition offsets/sizes be on cylinder boundaries. Partition offsets/sizes will be rounded to the nearest cylinder automatically. Label editor (enter '?' for help at any prompt)
Re: Question about webmail for users who are not busy on ports prep for 4.6
So far this thread has focused on the various IMAP based solutions and the merits of the many alternate components to such. Keying off some comments in the OP (below) I would like to point out that there _is_ an OpenBSD package openwebmail-2.51p1.tgz for a non-IMAP webmail. A few of the things that I like about this solution are: - it is written entirely in perl (no php or other non-base prereqs) - it works well when deployed on the mail server or over POP3 - its interface is very clean yet fairly feature rich - it is browser agnostic and renders decently even on mobiles Again, I bring this up only because it seems to me that the original goal was a simple non-IMAP solution and this suggestion should be taken completely independent of the rest of this thread -- IMAP adds capabilities and complexities that make any comparison of solutions with and without it mostly invalid. On 4 Jul 2009 at 20:05, Rod Whitworth wrote: > I have been running email for a couple of small domains for a few years > using Postfix and Teapop on OpenBSD. No complaints. > > I have scripted user addition with passwords etc etc. > > Now somebody (important of course) wants webmail. > > I went hunting. About the only webmail server I found that did not need > an imapd was sqwebmail and we don't have a port for that. Yes, I could > have a crack at making a port but that, given a lng absence from C > for me and also that it doesn't look really modern, sounded like it > would be loading myself with a pressure job. > > So looking at others needing imap showed me RoundCube. Pretty snazzy > looks, renders all that fancy junk that seems to be all the go now and > we have a package for it. > > So which imap? Dovecot looked like a candidate. It can use sqlite as > does Roundcube and I know it can do authentication for Postfix so it > looked like a suitable candidate. > > Then I found out that Roundcube uses sqlite and Dovecot uses sqlite3. I > don't think I want to have to synch two databases all the time. > > Does anybody know what combination works well with nothing as silly as > mismatched db versions? Maybe there is a way to get Roundcube (the > component I'd like to keep) to compile with sqlite3 but I haven't seen > a hint that that is supported, and whilst I do more research I'd like > to hear from someone who has invented the wheel I'm working on. > > Thanks, > > *** NOTE *** Please DO NOT CC me. I subscribed to the list. > Mail to the sender address that does not originate at the list server is > tarpitted. The reply-to: address is provided for those who feel compelled to > reply off list. Thankyou. > > Rod/ > /earth: write failed, file system is full > cp: /earth/creatures: No space left on device
Re: Problems with 4.5 as a KVM guest
same problem for me too. Michiel van Baak a icrit : > On 10:36, Sun 05 Jul 09, stan wrote: >> I am trying to get OpenBSD 4.5 working as a guest OS using KVM on Linux. I >> have been able to get 4.4 to install and run fine, but 4.5 never gives me a >> login prompt. The last message I see is about setting tty flgas. On the >> reboot after first install t paniced. > > I have the same. Google shows some others have as well. >> Any sugestions as to what to do to get this working? > > Run openbsd on real hardware :)
Re: Problems with 4.5 as a KVM guest
On 10:36, Sun 05 Jul 09, stan wrote: > I am trying to get OpenBSD 4.5 working as a guest OS using KVM on Linux. I > have been able to get 4.4 to install and run fine, but 4.5 never gives me a > login prompt. The last message I see is about setting tty flgas. On the > reboot after first install t paniced. I have the same. Google shows some others have as well. > > Any sugestions as to what to do to get this working? Run openbsd on real hardware :) -- Michiel van Baak mich...@vanbaak.eu http://michiel.vanbaak.eu GnuPG key: http://pgp.mit.edu:11371/pks/lookup?op=get&search=0x71C946BD "Why is it drug addicts and computer aficionados are both called users?"
Re: Cannot Boot with Intel D201GLY Motherboard
2009/7/5 Hendrickson, Kenneth : >> However, the best option would be to simply acquire an >> old beige box and install OpenBSD and back up the files >> to another system on your network. > > Unfortunately, this seems to be my only option. It is not good that OpenBSD > will not boot on the D201GLY motherboard. :-( You are using i386? Have you tried amd64? I have D201GLY2, and IIRC, with OpenBSD 4.5, the i386 kernel seemed to have been resetting the box right during the boot process, whereas the amd64 kernel worked (and still works) without a single problem. C.
per interface/route window size ?
I am running a soekris net5501 with OBSD 4.4 and a ral PCI wifi card. I have my network windows set high for my 5MB cable connection, but I'd really like a smaller window size for the wireless interface. inet 172.16.1.254 255.255.255.0 NONE media OFDM54 mediaopt hostap mode 11g nwid NWID nwkey NWKEY chan 1 description wifi up [ Using WEP till I get WPA2 working with my IPOD Touch ] net.inet.tcp.rfc3390=1 # 0=Disable RFC3390 for TCP window increasing net.inet.tcp.recvspace=65535 # Increase TCP "recieve" windows size to increase performance net.inet.tcp.sendspace=65535 # Increase TCP "send" windows size to increase performance net.inet.udp.recvspace=65535 # Increase UDP "recieve" windows size to increase performance net.inet.udp.sendspace=65535 # Increase UDP "send" windows size to increase performance ral0 at pci0 dev 14 function 0 "Ralink RT2561S" rev 0x00: irq 10, address 00:22:6b:9b:2b:f0 ral0: MAC/BBP RT2561C, RF RT2527 I have googled and rtfm'd but I cannot see how to set a per interface/route tcp/udp window size on OpenBSD. Is this even possible ? -- Rick Ballard Dartmouth,Nova Scotia, Canada http://www.ideaphore.com
Problems with 4.5 as a KVM guest
I am trying to get OpenBSD 4.5 working as a guest OS using KVM on Linux. I have been able to get 4.4 to install and run fine, but 4.5 never gives me a login prompt. The last message I see is about setting tty flgas. On the reboot after first install t paniced. Any sugestions as to what to do to get this working? -- One of the main causes of the fall of the roman empire was that, lacking zero, they had no way to indicate successful termination of their C programs.
Re: running spamd at same machine of the real smtp server
On 08:14, Sun 05 Jul 09, Robson Caetano wrote: > Hi, > > Is it possible to run spamd in the same host where > the SMTP server is running? Yes > > Is anyone in the list doing this? Could you share > your experience? Yes, and it works great. > > I thought of 2 ways but I do not know if there any > negative implications: > > 1 to run spamd on guest OS in an vmware server. > 2 to have the real smtp server listen on a different > TCP port Why ? spamd and smtpd listen on different ports. Read the man pages and the faq. -- Michiel van Baak mich...@vanbaak.eu http://michiel.vanbaak.eu GnuPG key: http://pgp.mit.edu:11371/pks/lookup?op=get&search=0x71C946BD "Why is it drug addicts and computer aficionados are both called users?"
Re: running spamd at same machine of the real smtp server
Robson Caetano wrote: Hi, Is it possible to run spamd in the same host where the SMTP server is running? Is anyone in the list doing this? Could you share your experience? I run spamd on one machine using sendmail, dovecot, and squirrelmail. No problems at all. Local traffic, of course, doesn't pass through spamd at all. Chris Bennett
Re: running spamd at same machine of the real smtp server
On 2009-07-05, Robson Caetano wrote: > Is it possible to run spamd in the same host where > the SMTP server is running? yes. > 1 to run spamd on guest OS in an vmware server. > 2 to have the real smtp server listen on a different > TCP port no need for any of this. the basic setup detailed in the manual works just fine. don't forget the "pass log" rules for spamlogd.
running spamd at same machine of the real smtp server
Hi, Is it possible to run spamd in the same host where the SMTP server is running? Is anyone in the list doing this? Could you share your experience? I thought of 2 ways but I do not know if there any negative implications: 1 to run spamd on guest OS in an vmware server. 2 to have the real smtp server listen on a different TCP port Thanks in advance. Regards, Robson -- Be Yourself @ mail.com! Choose From 200+ Email Addresses Get a Free Account at www.mail.com
Re: Cannot Boot with Intel D201GLY Motherboard [dmesg, fdisk, disklabel]
> Date: Sun, 5 Jul 2009 07:30:58 -0400 > From: "Hendrickson, Kenneth" > > > Unfortunately I cannot see your attachments.. > > as the lists do not permit them. > > I will post them in this message. > However, I cannot post OpenBSD.PBR because it is a binary file. > > > As this is a strictly a recovery operating, > > I would like to run OpenBSD on my D201GLY motherboard. > It is not strictly a recovery operation. > > During booting, the kernel dies very shortly after printing "cpu0 at > mainbus0". > However, it boots just fine from the install CD. Given the fact that the machine boots just fine from the CD you could try the following: 1. Boot from CD; interrupt the bootloader. 2. type "boot hd0a:/bsd" If that doesn't work, you can try disabling device drivers. 1. Boot from disk; interrupt the bootloader. 2. type "boot /bsd -c" 3. at the UKC> prompt type "disable " I'd start with disabling all the ACPI crap: acpitimer acpihpet acpiac acpibat acpibtn acpicpu acpidock acpiec acpivideo acpivout acpipwrres Other drivers that are worth trying are: azalia ohci ehci
Re: Problems using ppp on my cell phone
2009/7/3 STeve Andre' > On Thursday 02 July 2009 14:15:35 Andrej Elizarov wrote: > > If Aaron is right, you need to call to your mobile operators and ask > about > > "initialization string" in cell-modem properties in Windows > > (like /AT+CGDCONT=1,"IP","web.pt.lu"/ ), at first. And about new phone > > number for dial-up connection. > > In some rare cases i had to edit resolve.conf manually ( you can ask > > operator for dns ). > > This was in fact a bug, and Claudio fixed it, at least for me. The changes > to usr.sbin/ppp were put into the tree today. > Found thread in tech@, thanks to Claudio. Back when I first got this T-Mobile account and data plan, *no one* at > T-Mobile could help a non-Windows non-Mac user. There was simply no > one there who could help. I realize that. But magic words ' "initialization string" in cell-modem properties in Windows' must turn support's brain in right way and help get some usefull info. It took a lot of reading manuals for me to > build the ppp.conf file that worked. Perhaps other carriers are less > useless. > I belive your ppp.conf is correct. Stuff that could be changed on the operator side are init string and dial number. Anyway, happy ppping and sorry for bothering)
Re: Cannot Boot with Intel D201GLY Motherboard [dmesg, fdisk, disklabel]
> Unfortunately I cannot see your attachments..
> as the lists do not permit them.
I will post them in this message.
However, I cannot post OpenBSD.PBR because it is a binary file.
> As this is a strictly a recovery operating,
I would like to run OpenBSD on my D201GLY motherboard.
It is not strictly a recovery operation.
During booting, the kernel dies very shortly after printing "cpu0 at
mainbus0".
However, it boots just fine from the install CD.
-- 8< --
OpenBSD 4.5 (RAMDISK_CD) #1112: Sat Feb 28 15:06:26 MST 2009
dera...@i386.openbsd.org:/usr/src/sys/arch/i386/compile/RAMDISK_CD
cpu0: Intel(R) Celeron(R) CPU 220 @ 1.20GHz ("GenuineIntel" 686-class) 1.21
GHz
cpu0:
FPU,V86,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,CFLUS
H,DS,ACPI,MMX,FXSR,SSE,SSE2,SS,TM,SBF,SSE3,MWAIT,DS-CPL,TM2,CX16,xTPR
real mem = 935886848 (892MB)
avail mem = 898048000 (856MB)
mainbus0 at root
bios0 at mainbus0: AT/286+ BIOS, date 08/22/07, SMBIOS rev. 2.4 @ 0xe4da0 (23
entries)
bios0: vendor Intel Corp. version "LY66210M.86A.0122.2007.0822.2001" date
08/22/2007
bios0: Intel Corporation D201GLY
acpi0 at bios0: rev 0
acpi0: tables DSDT FACP APIC
acpimadt0 at acpi0 addr 0xfee0: PC-AT compat
cpu0 at mainbus0: apid 0 (boot processor)
cpu0: apic clock running at 133MHz
ioapic0 at mainbus0: apid 4 pa 0xfec0, version 14, 24 pins
ioapic0: misconfigured as apic 0, remapped to apid 4
acpiprt0 at acpi0: bus 0 (PCI0)
acpiprt1 at acpi0: bus 1 (P0P1)
bios0: ROM list: 0xc/0x1 0xd/0xa000
pci0 at mainbus0 bus 0: configuration mode 1 (bios)
pchb0 at pci0 dev 0 function 0 "SiS 662 PCI" rev 0x01
ppb0 at pci0 dev 1 function 0 "SiS 648FX AGP" rev 0x00
pci1 at ppb0 bus 1
vga1 at pci1 dev 0 function 0 "SiS 6330 VGA" rev 0x04
wsdisplay0 at vga1 mux 1: console (80x25, vt100 emulation)
pcib0 at pci0 dev 2 function 0 "SiS 964 ISA" rev 0x36
pciide0 at pci0 dev 2 function 5 "SiS 5513 EIDE" rev 0x01: 964: DMA, channel 0
wired to compatibility, channel 1 wired to compatibility
wd0 at pciide0 channel 0 drive 0:
wd0: 16-sector PIO, LBA, 114473MB, 234441648 sectors
atapiscsi0 at pciide0 channel 0 drive 1
scsibus0 at atapiscsi0: 2 targets
cd0 at scsibus0 targ 0 lun 0: ATAPI 5/cdrom removable
wd0(pciide0:0:0): using PIO mode 4, Ultra-DMA mode 5
cd0(pciide0:0:1): using PIO mode 4, Ultra-DMA mode 2
pciide0: channel 1 disabled (no drives)
"SiS 7012 AC97" rev 0xa0 at pci0 dev 2 function 7 not configured
ohci0 at pci0 dev 3 function 0 "SiS 5597/5598 USB" rev 0x0f: apic 4 int 20
(irq 11), version 1.0, legacy support
ohci1 at pci0 dev 3 function 1 "SiS 5597/5598 USB" rev 0x0f: apic 4 int 21
(irq 10), version 1.0, legacy support
ohci2 at pci0 dev 3 function 2 "SiS 5597/5598 USB" rev 0x0f: apic 4 int 22
(irq 11), version 1.0, legacy support
ehci0 at pci0 dev 3 function 3 "SiS 7002 USB" rev 0x00: apic 4 int 23 (irq
10)
ehci0: timed out waiting for BIOS
usb0 at ehci0: USB revision 2.0
uhub0 at usb0 "SiS EHCI root hub" rev 2.00/1.00 addr 1
sis0 at pci0 dev 4 function 0 "SiS 900 10/100BaseTX" rev 0x91: apic 4 int 19
(irq 11), address 00:1c:c0:26:8a:c3
ukphy0 at sis0 phy 1: Generic IEEE 802.3u media interface, rev. 1: OUI
0x0050ef, model 0x0007
pciide1 at pci0 dev 5 function 0 "SiS 181 SATA" rev 0x01: DMA
pciide1: using apic 4 int 17 (irq 10) for native-PCI interrupt
ppb1 at pci0 dev 31 function 0 "SiS PCI-PCI" rev 0x00
pci2 at ppb1 bus 2
isa0 at pcib0
isadma0 at isa0
com0 at isa0 port 0x3f8/8 irq 4: ns16550a, 16 byte fifo
pckbc0 at isa0 port 0x60/5
pckbd0 at pckbc0 (kbd slot)
pckbc0: using irq 1 for kbd slot
wskbd0 at pckbd0: console keyboard, using wsdisplay0
npx0 at isa0 port 0xf0/16: reported by CPUID; using exception 16
usb1 at ohci0: USB revision 1.0
uhub1 at usb1 "SiS OHCI root hub" rev 1.00/1.00 addr 1
usb2 at ohci1: USB revision 1.0
uhub2 at usb2 "SiS OHCI root hub" rev 1.00/1.00 addr 1
usb3 at ohci2: USB revision 1.0
uhub3 at usb3 "SiS OHCI root hub" rev 1.00/1.00 addr 1
rd0: fixed, 3800 blocks
"American Power Conversion Back-UPS RS 900 FW:9.o2 .D USB FW:o2" rev 1.10/1.06
addr 2 at uhub2 port 2 not configured
softraid0 at root
root on rd0a swap on rd0b dump on rd0b
-- 8< --
Disk: wd0 geometry: 232581/16/63 [234441648 Sectors]
Offset: 0 Signature: 0xAA55
Starting Ending LBA Info:
#: id C H S - C H S [ start:size ]
-
--
0: A6 0 1 1 -495 15 63 [ 63: 499905 ] OpenBSD
*1: 07496 0 1 - 13393 15 63 [ 499968:13001184 ]
HPFS/QNX/AUX
2: 05 13394 0 1 - 202759 15 63 [13501152: 190880928 ] Extended
DOS
3: DA 202760 0 1 - 232580 15 63 [ 204382080:30059568 ]
Offset: 13501152Signature: 0xAA55
Starting Ending LBA Info:
#: id C H S - C H S [ start:size ]
---
Re: Cannot Boot with Intel D201GLY Motherboard
> perhaps the geometry reported by the pciide(4) > driver differs from the one determined by the BIOS, Nope. I cannot get OpenBSD to boot on my D201GLY motherboard even without the Promise IDE controller plugged in. (I've tried both with and without the Promise IDE controller.) > However, the best option would be to simply acquire an > old beige box and install OpenBSD and back up the files > to another system on your network. Unfortunately, this seems to be my only option. It is not good that OpenBSD will not boot on the D201GLY motherboard. :-( Thanks, Kenneth J. Hendrickson
Re: external monitor for laptop using nv driver not working
On Sun, Jul 05, 2009 at 05:46:54AM -0400, Sturm Mabie wrote: > > is the panel on crtc 1 the one the POST messages appeared on? > > As in, the bootup BIOS messages? No, they appear on my laptop > screen, the LCD only starts working when OpenBSD starts booting. > > Can I somehow change this? I don't know. is there an option in the BIOS, or maybe it's explained in the user's manual for the laptop? -- jake...@sdf.lonestar.org SDF Public Access UNIX System - http://sdf.lonestar.org
Re: external monitor for laptop using nv driver not working
> is the panel on crtc 1 the one the POST messages appeared on? As in, the bootup BIOS messages? No, they appear on my laptop screen, the LCD only starts working when OpenBSD starts booting. Can I somehow change this?
Re: external monitor for laptop using nv driver not working
On Sun, Jul 05, 2009 at 12:45:45AM -0400, Sturm Mabie wrote: > I'm having some trouble getting my LG 1920x1080 monitor working > under OpenBSD 4.5. The relevant sections of my xorg.conf are as > follows: > Option "CrtcNumber" "1" > (--) NV(0): CRTC 0 is currently programmed for DFP > (**) NV(0): Forcing CRTCNumber 1 as specified > (II) NV(0): Using DFP on CRTC 1 > (--) NV(0): Panel size is 1 x 1 > (II) NV(0): NOTE: This driver cannot reconfigure the BIOS-programmed size. > The problem seems to be that the panel size is detected as a 1x1 instead > of a 1920x1080. Why is this happening and what must be done to fix it? > (the nv(4) manpage offered no insight). from nv(4): Option "FlatPanel" "boolean" ... With this driver, a digital flat panel will work only if it was POSTed by the BIOS, that is, the computer must have booted to the panel. is the panel on crtc 1 the one the POST messages appeared on? -- jake...@sdf.lonestar.org SDF Public Access UNIX System - http://sdf.lonestar.org
Re: Cannot Boot with Intel D201GLY Motherboard
On Sat, Jul 04, 2009 at 07:44:16PM -0400, Hendrickson, Kenneth wrote: > This is a very disappointing result!!! :-( > > I am trying to recover old data from a ccd device, on a > Promise hard drive controller card. > > If I cannot use the Promise HDD controller card, then I > cannot recover my data. Use another system that's booting ok and put the promise cards with its disks into it. -Otto > > If I must use another PCI video card, then I will not be > able to use the Promise HDD controller card, because my > motherboard has only 1 PCI slot. > > So this will defeat the entire purpose! > > If anybody else has any suggestions, please let me know! > > Thanks, > Kenneth J. Hendrickson > > > > -Original Message- > From: Mike Belopuhov [mailto:mi...@lucifier.net] > Sent: Sat 7/4/2009 6:39 PM > To: Hendrickson, Kenneth > Subject: Re: Cannot Boot with Intel D201GLY Motherboard > > > you have to put a PCI video card in. it's SiS video that blows things up. > though, as RAMDISK kernel works, surely it's openbsd defficiency. nobody > has figured out what's actually is a problem because of the lack of this > hardware. > > On Sat, Jul 04, 2009 at 17:00 -0400, Hendrickson, Kenneth wrote: > > Cannot Boot with Intel D201GLY Motherboard > > > > Disk is 120GB PATA IDE > > > > dmesg, fdisk output, and disklabel output are all attached > > OpenBSD.PDR is also attached > > > > I have Googled for problems/answers, and still run into a dead end. > > > > There must be a requirement which is not stated in the documentation, > > which I am not following. Please help. > > > > (I am an experienced OpenBSD user, having used OpenBSD continuously > > since 1998, and having built my own kernels/userland, and also have > > built OpenBSD for embedded systems.) > > > > The instructions for booting from NTLDR (Windows 2000) do not work. > > As soon as the messages get to the CPU, the system reboots. Booting > > never works, either from the OpenBSD partition, or from NTLDR from > > Windows 2000. I have included my OpenBSD.PDR file for examination. > > > > Originally, my OpenBSD partition was #4 in fdisk. I added the #1 > > partition, and had both #1 and #4 set to "a6" for OpenBSD. That > > didn't work. I then chose only #1 partition to be "a6" for OpenBSD, > > and #4 partition was set to "da" for "No Filesystem". That also > > didn't work. Please note that my entire OpenBSD / filesystem is > > within the 1024 cylinder boundary. The /boot file is totally > > contained within the 1024 cylinder boundary. It still won't boot. > > It won't boot on its own, nor will it boot from the Windows 2000 > > NTLDR bootloader. > > > > Also note that while my fdisk and disklabel indicates Linux > > partitions, none of them have yet been installed. I installed > > Windows 2000 first, then OpenBSD. Since I could never get OpenBSD > > to boot, I have not yet installed Linux. > > > > Please help if you can. > > > > Thank you, > > Kenneth J. Hendrickson > > > > [demime 1.01d removed an attachment of type application/octet-stream which > had a name of dmesg] > > > > [demime 1.01d removed an attachment of type application/octet-stream which > had a name of fdisk] > > > > [demime 1.01d removed an attachment of type application/octet-stream which > had a name of disklabel] > > > > [demime 1.01d removed an attachment of type application/octet-stream which > had a name of OpenBSD.PDR]
Re: Cannot Boot with Intel D201GLY Motherboard
On 2009/07/04 23:04, Brynet wrote: > Stuart Henderson wrote: > > some of the Atom boards seem to need APIC; if you want to stick with > > 4.5 then try the GENERIC.MP kernel (bsd.mp); otherwise try a -current > > snapshot (where APIC is used in GENERIC as well as GENERIC.MP). > > Hi sthen, > > OpenBSD 4.5 shipped with APIC/IOAPIC in the SP kernel, it's not longer > needed to boot MP kernels. :-) Ah, you're right, I thought it was more recent than that.
