Are RTL8188CE-based Wi-Fi adapters supported?
Hello, I recently purchased a Thinkpad T420 and am running -current from Dec. 23. The wi-fi card doesn't appear to currently be supported. When making my order I selected ThinkPad Wi-Fi. This device ended up being a Realtek 8188CE mini PCI express b/g/n card. The card is identified in dmesg output as: Realtek 8188CE rev 0x01 at pci2 dev 0 function 0 not configured I found that damien@ added some RTL8188CE device ids in revision 1.520 of usbdevs and are matched by urtwn(4). The non-working device attaches as PCI, not USB, though. Dmesg and verbose pcidump output will follow. Is there any work currently being done in this area? Thanks, Jamie Dmesg from -current as of Dec 23: OpenBSD 5.0-current (GENERIC.MP) #0: Sat Dec 24 01:03:21 CST 2011 r...@otto.whitewater.gavahan.net:/usr/src/sys/arch/amd64/compile/GENERIC.MP real mem = 8466853888 (8074MB) avail mem = 8227323904 (7846MB) mainbus0 at root bios0 at mainbus0: SMBIOS rev. 2.6 @ 0xdae9c000 (65 entries) bios0: vendor LENOVO version 83ET64WW (1.34 ) date 09/08/2011 bios0: LENOVO 4177CTO acpi0 at bios0: rev 2 acpi0: sleep states S0 S3 S4 S5 acpi0: tables DSDT FACP SLIC SSDT SSDT SSDT HPET APIC MCFG ECDT ASF! TCPA SSDT SSDT UEFI UEFI UEFI acpi0: wakeup devices LID_(S3) SLPB(S3) IGBE(S4) EXP4(S4) EHC1(S3) EHC2(S3) HDEF(S4) 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: Intel(R) Core(TM) i5-2410M CPU @ 2.30GHz, 2292.86 MHz cpu0: FPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,CFLUSH,DS,ACPI,MMX,FXSR,SSE,SSE2,SS,HTT,TM,SBF,SSE3,PCLMUL,MWAIT,DS-CPL,VMX,EST,TM2,SSSE3,CX16,xTPR,PDCM,SSE4.1,SSE4.2,x2APIC,POPCNT,AES,XSAVE,AVX,NXE,LONG cpu0: 256KB 64b/line 8-way L2 cache cpu0: apic clock running at 99MHz cpu1 at mainbus0: apid 1 (application processor) cpu1: Intel(R) Core(TM) i5-2410M CPU @ 2.30GHz, 2292.56 MHz cpu1: FPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,CFLUSH,DS,ACPI,MMX,FXSR,SSE,SSE2,SS,HTT,TM,SBF,SSE3,PCLMUL,MWAIT,DS-CPL,VMX,EST,TM2,SSSE3,CX16,xTPR,PDCM,SSE4.1,SSE4.2,x2APIC,POPCNT,AES,XSAVE,AVX,NXE,LONG cpu1: 256KB 64b/line 8-way L2 cache cpu2 at mainbus0: apid 2 (application processor) cpu2: Intel(R) Core(TM) i5-2410M CPU @ 2.30GHz, 2292.55 MHz cpu2: FPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,CFLUSH,DS,ACPI,MMX,FXSR,SSE,SSE2,SS,HTT,TM,SBF,SSE3,PCLMUL,MWAIT,DS-CPL,VMX,EST,TM2,SSSE3,CX16,xTPR,PDCM,SSE4.1,SSE4.2,x2APIC,POPCNT,AES,XSAVE,AVX,NXE,LONG cpu2: 256KB 64b/line 8-way L2 cache cpu3 at mainbus0: apid 3 (application processor) cpu3: Intel(R) Core(TM) i5-2410M CPU @ 2.30GHz, 2292.56 MHz cpu3: FPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,CFLUSH,DS,ACPI,MMX,FXSR,SSE,SSE2,SS,HTT,TM,SBF,SSE3,PCLMUL,MWAIT,DS-CPL,VMX,EST,TM2,SSSE3,CX16,xTPR,PDCM,SSE4.1,SSE4.2,x2APIC,POPCNT,AES,XSAVE,AVX,NXE,LONG cpu3: 256KB 64b/line 8-way L2 cache ioapic0 at mainbus0: apid 2 pa 0xfec0, version 20, 24 pins acpimcfg0 at acpi0 addr 0xf800, bus 0-63 acpiec0 at acpi0 acpiprt0 at acpi0: bus 0 (PCI0) acpiprt1 at acpi0: bus -1 (PEG_) acpiprt2 at acpi0: bus 2 (EXP1) acpiprt3 at acpi0: bus 3 (EXP2) acpiprt4 at acpi0: bus 5 (EXP4) acpiprt5 at acpi0: bus 13 (EXP5) acpicpu0 at acpi0: C3, C1, PSS acpicpu1 at acpi0: C3, C1, PSS acpicpu2 at acpi0: C3, C1, PSS acpicpu3 at acpi0: C3, C1, PSS acpipwrres0 at acpi0: PUBS acpitz0 at acpi0: critical temperature is 98 degC acpibtn0 at acpi0: LID_ acpibtn1 at acpi0: SLPB acpibat0 at acpi0: BAT0 model 42T4793 serial 10138 type LION oem Panasonic acpibat1 at acpi0: BAT1 not present acpiac0 at acpi0: AC unit online acpithinkpad0 at acpi0 cpu0: Enhanced SpeedStep 2292 MHz: speeds: 2301, 2300, 2000, 1800, 1600, 1400, 1200, 1000, 800 MHz pci0 at mainbus0 bus 0 pchb0 at pci0 dev 0 function 0 Intel Core 2G Host rev 0x09 vga1 at pci0 dev 2 function 0 Intel GT2 Video rev 0x09 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 0xe000, size 0x1000 inteldrm0 at vga1: apic 2 int 16 drm0 at inteldrm0 Intel 6 Series MEI rev 0x04 at pci0 dev 22 function 0 not configured em0 at pci0 dev 25 function 0 Intel 82579LM rev 0x04: msi, address 00:21:cc:6a:3c:6b ehci0 at pci0 dev 26 function 0 Intel 6 Series USB rev 0x04: apic 2 int 16 usb0 at ehci0: USB revision 2.0 uhub0 at usb0 Intel EHCI root hub rev 2.00/1.00 addr 1 azalia0 at pci0 dev 27 function 0 Intel 6 Series HD Audio rev 0x04: msi azalia0: codecs: Conexant/0x506e, Intel/0x2805, using Conexant/0x506e audio0 at azalia0 ppb0 at pci0 dev 28 function 0 Intel 6 Series PCIE rev 0xb4: msi pci1 at ppb0 bus 2 ppb1 at pci0 dev 28 function 1 Intel 6 Series PCIE rev 0xb4: msi pci2 at ppb1 bus 3 Realtek 8188CE rev 0x01 at pci2 dev 0 function 0 not configured ppb2 at pci0 dev 28 function 3 Intel 6 Series PCIE rev 0xb4: msi pci3 at ppb2 bus 5 ppb3 at pci0 dev 28 function 4
Re: root/boot on softraid in 5.0
On 23.12.2011 P3. 08:01 Q., Raymond Lillard wrote: On 12/22/2011 09:07 PM, Paul B. Henson wrote: On Wed, Dec 21, 2011 at 08:08:08PM -0800, Josh Grosse wrote: Woops. I misread your post. The commits were September 19, which is -current, beyond 5.0-release. You must either migrate to -current, or await 5.1-release. Ah, ok, thanks for the clarification. The installboot piece that lets you install bootblocks on softraid is in 5.0, so when that part worked I assumed it all was. The dates (commits in Sept, your post in Oct, 5.0 release in Nov) also led me to misbelieve it was in 5.0. But looking at the changelogs I see the bits that store boot info in softraid metadata and dynamically figure out the root happened after the 5.0 freeze. Something to look forward to in 5.1 :). Thanks again... Why wait? I have two amd64 servers in production on -current and all is humming along magnificently. One is heavily loaded by large image file manipulation over samba. Of course that has little to do with the boot block business. Both servers were booted more than a dozen times during provisioning so I feel good that they will come up after an extended power outage. I did boot with sd0 removed to force a boot from sd1. I then took a third disk and rebuilt sd0 while the machine was up and running. All went well. To me it was worth the trouble to pick a snapshot between commit storms by the developers, just so I didn't have to deal with the altroot thing any more. I have been using OBSD for Internet facing infrastructure for the last 10 years but always used RedHat/CentOS for internal servers. In Oct I installed the first of the two and don't see going back. I am so done with Linux servers. OBSD is getting close to the point where I can use it as a workstation/desktop. My biggest hindrance is no wine. I guess I am going to be forced to make friends with some VM system and cross mount the filesystems via samba. I assume smarter people than me have done that already. I would take suggestions of a preferred VM off-list so as not to hijack this tread. Regards all Sorry for hijacking this tread. Can someone take time to clarify install process on softraid. I read the article on undeadly.org, preform the install on sd2, my softraid0, copy kernels on sd0a and sd1a, everything went well, and after reboot, it does not find bootable media. I put install cd, drop to shell, mount sd0a, then sd1a and then sd2a, everything is there. Do I miss some obvious step here... Can you point out what is wrong? It is AMD64 20 December snapshot on HP microserver. I cannot take dmesg at this point. I can take one from standard install if you need it. Happy Holidays! Thanks for the help, Ivo
Re: root/boot on softraid in 5.0
On Sat, Dec 24, 2011 at 02:26:26PM +0200, Ivo Chutkin wrote: Sorry for hijacking this tread. Can someone take time to clarify install process on softraid. I read the article on undeadly.org, preform the install on sd2, my softraid0, copy kernels on sd0a and sd1a, everything went well, and after reboot, it does not find bootable media. I put install cd, drop to shell, mount sd0a, then sd1a and then sd2a, everything is there. Do I miss some obvious step here... Can you point out what is wrong? The kernels are loaded from outside the softraid array (sd0a, or sd1a) by the second stage bootloader. But the second stage bootloader is loaded from the array. So, assuming sd2 is your softraid array, and you have an sd2a root partition, reboot the install cd and try: # mount /dev/sd2a /mnt # cp -p /usr/mdec/boot /mnt/boot # /usr/mdec/installboot -v /mnt/boot /usr/mdec/biosboot sd2 It is AMD64 20 December snapshot on HP microserver. I cannot take dmesg at this point. I can take one from standard install if you need it. Both amd64 and i386 use the same installboot(8) program.
Re: root/boot on softraid in 5.0
On 24.12.2011 P3. 15:06 Q., Josh Grosse wrote: On Sat, Dec 24, 2011 at 02:26:26PM +0200, Ivo Chutkin wrote: Sorry for hijacking this tread. Can someone take time to clarify install process on softraid. I read the article on undeadly.org, preform the install on sd2, my softraid0, copy kernels on sd0a and sd1a, everything went well, and after reboot, it does not find bootable media. I put install cd, drop to shell, mount sd0a, then sd1a and then sd2a, everything is there. Do I miss some obvious step here... Can you point out what is wrong? The kernels are loaded from outside the softraid array (sd0a, or sd1a) by the second stage bootloader. But the second stage bootloader is loaded from the array. So, assuming sd2 is your softraid array, and you have an sd2a root partition, reboot the install cd and try: # mount /dev/sd2a /mnt # cp -p /usr/mdec/boot /mnt/boot # /usr/mdec/installboot -v /mnt/boot /usr/mdec/biosboot sd2 It is AMD64 20 December snapshot on HP microserver. I cannot take dmesg at this point. I can take one from standard install if you need it. Both amd64 and i386 use the same installboot(8) program. Hi Josh, I try it but it does not boot as well. Here is what I do step by step: 1.boot from cd 2.drop to shell 3.cd /dev, sh MAKEDEV sd1 4.fdisk -iy sd0 and sd1 5.disklabel -E sd0, add a, 100m, add d, the rest of disk, raid fail system 6. disklabel -R sd1 disklabel.sd1 7. bioctl -c 1 -l sd0d,sd1d softraid0 8.^D 9.install 10. when I am asked which one I wish to initiate i choose sd2 which is my raid partition. 11. continue with normal install and / is on sd2a 12. newfs sd0a and sd1a 13. copy kernels to sd0a and sd1a everything went well I tried installboot step before and after reboot, it does not boot. I will change hardware now to check if it could be some HP specific problem. Thanks, Ivo
Re: root/boot on softraid in 5.0
On 24.12.2011 P3. 15:42 Q., Ivo Chutkin wrote: On 24.12.2011 P3. 15:06 Q., Josh Grosse wrote: On Sat, Dec 24, 2011 at 02:26:26PM +0200, Ivo Chutkin wrote: Sorry for hijacking this tread. Can someone take time to clarify install process on softraid. I read the article on undeadly.org, preform the install on sd2, my softraid0, copy kernels on sd0a and sd1a, everything went well, and after reboot, it does not find bootable media. I put install cd, drop to shell, mount sd0a, then sd1a and then sd2a, everything is there. Do I miss some obvious step here... Can you point out what is wrong? The kernels are loaded from outside the softraid array (sd0a, or sd1a) by the second stage bootloader. But the second stage bootloader is loaded from the array. So, assuming sd2 is your softraid array, and you have an sd2a root partition, reboot the install cd and try: # mount /dev/sd2a /mnt # cp -p /usr/mdec/boot /mnt/boot # /usr/mdec/installboot -v /mnt/boot /usr/mdec/biosboot sd2 It is AMD64 20 December snapshot on HP microserver. I cannot take dmesg at this point. I can take one from standard install if you need it. Both amd64 and i386 use the same installboot(8) program. Hi Josh, I try it but it does not boot as well. Here is what I do step by step: 1.boot from cd 2.drop to shell 3.cd /dev, sh MAKEDEV sd1 4.fdisk -iy sd0 and sd1 5.disklabel -E sd0, add a, 100m, add d, the rest of disk, raid fail system 6. disklabel -R sd1 disklabel.sd1 7. bioctl -c 1 -l sd0d,sd1d softraid0 8.^D 9.install 10. when I am asked which one I wish to initiate i choose sd2 which is my raid partition. 11. continue with normal install and / is on sd2a 12. newfs sd0a and sd1a 13. copy kernels to sd0a and sd1a everything went well I tried installboot step before and after reboot, it does not boot. I will change hardware now to check if it could be some HP specific problem. Thanks, Ivo Hello again, The problem was in HP microserver bios. I have to change SATA mode from AHCI to IDE When I moved disks to some ordinary PC everything went well and I realise what could be the problem. Below is dmesg from it. Thanks for the help, Ivo Here is dmesg from HP microserver running from softraid :-) # dmesg OpenBSD 5.0-current (GENERIC.MP) #159: Tue Dec 20 11:02:37 MST 2011 dera...@amd64.openbsd.org:/usr/src/sys/arch/amd64/compile/GENERIC.MP real mem = 2011758592 (1918MB) avail mem = 1944121344 (1854MB) mainbus0 at root bios0 at mainbus0: SMBIOS rev. 2.6 @ 0xfb330 (35 entries) bios0: vendor HP version O41 date 04/02/2011 bios0: HP ProLiant MicroServer acpi0 at bios0: rev 2 acpi0: sleep states S0 S4 S5 acpi0: tables DSDT FACP APIC MCFG SPMI OEMB HPET EINJ BERT ERST HEST SSDT acpi0: wakeup devices PCE2(S4) PCE3(S4) PCE4(S4) PCE5(S4) PCE6(S4) PCE7(S4) PCE9(S4) PCEA(S4) PCEB(S4) PCEC(S4) SBAZ(S4) P0PC(S4) PE20(S4) PE21(S4) PE22(S4) PE23(S4) acpitimer0 at acpi0: 3579545 Hz, 32 bits acpimadt0 at acpi0 addr 0xfee0: PC-AT compat cpu0 at mainbus0: apid 0 (boot processor) cpu0: AMD Turion(tm) II Neo N40L Dual-Core Processor, 1497.77 MHz cpu0: FPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,CFLUSH,MMX,FXSR,SSE,SSE2,HTT,SSE3,MWAIT,CX16,POPCNT,NXE,MMXX,FFXSR,LONG,3DNOW2,3DNOW cpu0: 64KB 64b/line 2-way I-cache, 64KB 64b/line 2-way D-cache, 1MB 64b/line 16-way L2 cache cpu0: ITLB 32 4KB entries fully associative, 16 4MB entries fully associative cpu0: DTLB 48 4KB entries fully associative, 48 4MB entries fully associative cpu0: apic clock running at 199MHz cpu1 at mainbus0: apid 1 (application processor) cpu1: AMD Turion(tm) II Neo N40L Dual-Core Processor, 1497.52 MHz cpu1: FPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,CFLUSH,MMX,FXSR,SSE,SSE2,HTT,SSE3,MWAIT,CX16,POPCNT,NXE,MMXX,FFXSR,LONG,3DNOW2,3DNOW cpu1: 64KB 64b/line 2-way I-cache, 64KB 64b/line 2-way D-cache, 1MB 64b/line 16-way L2 cache cpu1: ITLB 32 4KB entries fully associative, 16 4MB entries fully associative cpu1: DTLB 48 4KB entries fully associative, 48 4MB entries fully associative ioapic0 at mainbus0: apid 2 pa 0xfec0, version 21, 24 pins acpimcfg0 at acpi0 addr 0xe000, bus 0-255 acpihpet0 at acpi0: 14318180 Hz acpi0: unable to load \\_SB_._INI.EXH1 acpiprt0 at acpi0: bus 0 (PCI0) acpiprt1 at acpi0: bus 1 (P0P1) acpiprt2 at acpi0: bus -1 (PCE2) acpiprt3 at acpi0: bus 2 (PCE4) acpiprt4 at acpi0: bus 3 (PCE6) acpicpu0 at acpi0: PSS acpicpu1 at acpi0: PSS acpibtn0 at acpi0: PWRB ipmi at mainbus0 not configured cpu0: 1497 MHz: speeds: 1500 1300 1000 800 MHz pci0 at mainbus0 bus 0 pchb0 at pci0 dev 0 function 0 AMD RS880 Host rev 0x00 ppb0 at pci0 dev 1 function 0 vendor Hewlett-Packard, unknown product 0x9602 rev 0x00 pci1 at ppb0 bus 1 vga1 at pci1 dev 5 function 0 ATI Mobility Radeon HD 4200 rev 0x00 wsdisplay0 at vga1 mux 1: console (80x25, vt100 emulation) wsdisplay0: screen 1-5 added (80x25, vt100 emulation) radeondrm0 at vga1: apic 2 int 18 drm0 at radeondrm0 ppb1 at pci0 dev 4 function 0 AMD RS780 PCIE
Postscript printer: is poscript support enough to get it running?
Hi, I've been considering buying a printer, and after a bit of homework, I found that postscript is the standard supported method for printing (even though most printers nowdays do all the work on CPU rather than themselves to cut costs). So I looked up a model but I really *don't* understand that much, this is the first time *ever* I'd be buying/using/installing a printer, so what I'd like to know is: Is postscript support in an ethernet/USB printer enough? Or do I need to take some other specification into consideration? If so, which? I don't want to go out and buy a printer, only to find out that I need support for X, for Y software for the platform where I'll use it. As a side note, it's the HP P2055 I've been considering, and supports PS3. Thanks -- Hugo Osvaldo Barrera
Re: Postscript printer: is poscript support enough to get it running?
Print languages:HP PCL 5c; HP PCL 6; HP postscript level 3 emulation with automatic language switching source: http://www.shopping.hp.com/product/printer/LaserJet/1/storefronts/CE459A%2523 ABA;HHOJSID=PhcXT2lHNxpKCxk8X1TLbrMJ35K5BT2F5Z5XnzGRDmgZJhKtM9nh!743062901 On Sat, Dec 24, 2011 at 9:38 AM, Hugo Osvaldo Barrera h...@osvaldobarrera.com.ar wrote: Hi, I've been considering buying a printer, and after a bit of homework, I found that postscript is the standard supported method for printing (even though most printers nowdays do all the work on CPU rather than themselves to cut costs). So I looked up a model but I really *don't* understand that much, this is the first time *ever* I'd be buying/using/installing a printer, so what I'd like to know is: Is postscript support in an ethernet/USB printer enough? Or do I need to take some other specification into consideration? If so, which? I don't want to go out and buy a printer, only to find out that I need support for X, for Y software for the platform where I'll use it. As a side note, it's the HP P2055 I've been considering, and supports PS3. Thanks -- Hugo Osvaldo Barrera
Re: Postscript printer: is poscript support enough to get it running?
On Sat, 24 Dec 2011 14:38:08 -0300 Hugo Osvaldo Barrera h...@osvaldobarrera.com.ar wrote: Is postscript support in an ethernet/USB printer enough? Or do I need to take some other specification into consideration? If so, which? I don't If the printer talks postscript, you just feed it a postscript file. So the most simple setup is to have a PS printer with an ethernet port. Just add something like this to your /etc/printcap and start lpd: lp:\ :sd=/some/spool/folder/lp:\ :mx#0:\ :sh:\ :rm=10.11.12.13:\ :rp=lp: If you want to do fancy things, look at the a2ps package. But otherwise you don't need any special software. Oh, and don't forget to update your firmware [1]. kind regards, Robert [1] http://www.hp.com/hpinfo/newsroom/press/2011/29b.html
Re: Can't create 1.5TB softraid partition.
Hi Christian, I'll will try as soon as I can. That's going to be early next year now as I accidentally messed with the wrong disk in the server and will now need to make a wee trip to the data center to reinstall obsd oops... Cheers Keith On 22/12/2011 23:05, Christian Weisgerber wrote: Keithke...@scott-land.net wrote: I am having some trouble getting 4 x 2TB sata disks into one big single softraid (raid 5) disk. I can create the softraid0 disk and it's 5.5TB want would like to get a single 5.5TB partition but can only make one single 1.5TB partition! Can someone tell me where I'm going wrong. #fdisk -iy sd1 The MBR format is limited to a 32-bit number of sectors. Given 512-byte sectos, it cannot handle values larger than 2TB. However, this doesn't matter if you don't want to share the disk with other operating systems. In disklabel(8), simply set the OpenBSD disk boundaries 'b' to the real size '*'; see the man page. Here's the partition info I put on a 3TB disk: # fdisk sd1 Disk: sd1 geometry: 364801/255/63 [1565565872 Sectors] Offset: 0 Signature: 0xAA55 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 2 - 267349 89 3 [ 64: 4294967231 ] OpenBSD # disklabel sd1 # /dev/rsd1c: type: SCSI disk: SCSI disk label: Hitachi HUA72303 duid: aa3700ccfc518ee8 flags: bytes/sector: 512 sectors/track: 63 tracks/cylinder: 255 sectors/cylinder: 16065 cylinders: 364801 total sectors: 5860533168 boundstart: 64 boundend: 4294967295 drivedata: 0 16 partitions: #size offset fstype [fsize bsize cpg] c: 58605331680 unused d: 5860533056 64 4.2BSD 8192 655361 # /export
Upgrading 4.9 to 5.0 problems: can't build kernel, errata patch not in CVS, no documentation for netstart changes
Some strange things going on... Running OpenBSD 5.0 on an x86 32 bit, upgraded smoothly from 4.9 aside from at upgrade from 4.9 to 5.0, the upgrade failed at first trying to start the network with this hostname.if file for my external facing interface: up dhcp -inet6 ... complaining that it is an invalid hostname file. This worked just fine in 4.9. After scratching my head for a long time, I changed it to be: up -inet6 dhcp .. and it worked... looks like /etc/netstart changed how it parses hostname.if files but there is no documentation about this. Once I had a working system again after completing the full upgrade process, I primed my source directories by removing /usr/src/*, /usr/xenocara, and /usr/ports. I then downloaded the 4 source tarballs from http://ftp5.usa.openbsd.org/pub/OpenBSD/5.0/*.tar.gz, unpacked them into the proper places and ran cvs update on them (using the proper options for the -stable branch, of course, as per the FAQ). There were no updates patched into the trees. The patch for the bind DoS (http://ftp.openbsd.org/pub/OpenBSD/patches/5.0/common/001_bind.patch) specifically was not in the CVS stable branch, almost a month after the patch came out. I had to add it manually to the tree. I then tried to build the kernel as a regular user following this text: Variation on above process: Read-only source tree Sometimes, you may wish to ensure your /usr/src/sys directory remains untouched. This can be done by using the following process: $ cd /somewhere $ cp /usr/src/sys/arch/i386/conf/GENERIC . $ config -s /usr/src/sys -b . GENERIC $ make clean make depend make ... lots of output ... ... which is missing now from the latest FAQ page (http://www.openbsd.org/faq/faq5.html#BldKernel)... I had to search the internet to find this text again. It still _does_say: Note that you can build a kernel without root access, but you must have root to install the kernel. but the procedure on how to do it is gone. When I try to build the kernel in an empty limited user directory after the config command above, I get the following error: $ make clean make depend make rm -f eddep *bsd *bsd.gdb tags *.[dio] [a-z]*.s [Ee]rrs linterrs assym.h make: don't know how to make /usr/src/sys/uvm/uvm_pglist.h. Stop in /home//kernel-build. $ Can anybody tell me what is going on or what I'm missing or did wrong? Is building a kernel from read-only sources now not supported?? I didn't try to build this as root yet, figuring I have some sort of borked system. Any insight welcomed. I don't follow the maling lists too regularly so I must have missed something.
Re: Upgrading 4.9 to 5.0 problems: can't build kernel, errata patch not in CVS, no documentation for netstart changes
First, sorry for the bogus formatting in my previous email... hopefully, this one is better. It turns out that I needed to manually delete the .depend file from a previous kernel build in my local build directory. The makefile has only this under the depend target: touch $@ and 'make clean' didn't delete '.depend' as I would expect it should. It looks like a new .depend file is not written out, but the old one was recognized and used which caused my problems. Nice gotcha! Shouldn't this be documented? Also, what happened to the FAQ text about non-root kernel build procedures?? On 24 Dec 2011 at 18:10, misc@openbsd.org wrote: Some strange things going on... Running OpenBSD 5.0 on an x86 32 bit, upgraded smoothly from 4.9 aside from at upgrade from 4.9 to 5.0, the upgrade failed at first trying to start the network with this hostname.if file for my external facing interface: up dhcp -inet6 ... complaining that it is an invalid hostname file. This worked just fine in 4.9. After scratching my head for a long time, I changed it to be: up -inet6 dhcp .. and it worked... looks like /etc/netstart changed how it parses hostname.if files but there is no documentation about this. Once I had a working system again after completing the full upgrade process, I primed my source directories by removing /usr/src/*, /usr/xenocara, and /usr/ports. I then downloaded the 4 source tarballs from http://ftp5.usa.openbsd.org/pub/OpenBSD/5.0/*.tar.gz, unpacked them into the proper places and ran cvs update on them (using the proper options for the -stable branch, of course, as per the FAQ). There were no updates patched into the trees. The patch for the bind DoS (http://ftp.openbsd.org/pub/OpenBSD/patches/5.0/common/001_bind.patch) specifically was not in the CVS stable branch, almost a month after the patch came out. I had to add it manually to the tree. I then tried to build the kernel as a regular user following this text: Variation on above process: Read-only source tree Sometimes, you may wish to ensure your /usr/src/sys directory remains untouched. This can be done by using the following process: $ cd /somewhere $ cp /usr/src/sys/arch/i386/conf/GENERIC . $ config -s /usr/src/sys -b . GENERIC $ make clean make depend make ... lots of output ... ... which is missing now from the latest FAQ page (http://www.openbsd.org/faq/faq5.html#BldKernel)... I had to search the internet to find this text again. It still _does_say: Note that you can build a kernel without root access, but you must have root to install the kernel. but the procedure on how to do it is gone. When I try to build the kernel in an empty limited user directory after the config command above, I get the following error: $ make clean make depend make rm -f eddep *bsd *bsd.gdb tags *.[dio] [a-z]*.s [Ee]rrs linterrs assym.h make: don't know how to make /usr/src/sys/uvm/uvm_pglist.h. Stop in /home//kernel-build. $ Can anybody tell me what is going on or what I'm missing or did wrong? Is building a kernel from read-only sources now not supported?? I didn't try to build this as root yet, figuring I have some sort of borked system. Any insight welcomed. I don't follow the maling lists too regularly so I must have missed something.
