Wireless not working with Linksys
Hi, I just got Linksys 1900ACS wireless router and it works great, except with OpenBSD. I've got Thinkpad T430s running -current and I can't get DHCP lease from the new router. I noticed lines: "dhclient[22294]: fatal in iwn0: yielding responsibility" in messages file which might be relating to this. Any ideas what could be the problem and how to begin debugging this further? Timo OpenBSD 6.2-beta (RAMDISK_CD) #103: Mon Sep 18 23:35:48 MDT 2017 dera...@amd64.openbsd.org:/usr/src/sys/arch/amd64/compile/RAMDISK_CD real mem = 16973611008 (16187MB) avail mem = 16455442432 (15693MB) mainbus0 at root bios0 at mainbus0: SMBIOS rev. 2.7 @ 0xdae9c000 (68 entries) bios0: vendor LENOVO version "G7ETA4WW (2.64 )" date 10/08/2015 bios0: LENOVO 2355C16 acpi0 at bios0: rev 2 acpi0: tables DSDT FACP SLIC TCPA SSDT SSDT SSDT HPET APIC MCFG ECDT FPDT ASF! UEFI UEFI POAT SSDT SSDT DMAR UEFI DBG2 acpimadt0 at acpi0 addr 0xfee0: PC-AT compat cpu0 at mainbus0: apid 0 (boot processor) cpu0: Intel(R) Core(TM) i5-3320M CPU @ 2.60GHz, 2594.57 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,PBE,SSE3,PCLMUL,DTES64,MWAIT,DS-CPL,VMX,SMX,EST,TM2,SSSE3,CX16,xTPR,PDCM,PCID,SSE4.1,SSE4.2,x2APIC,POPCNT,DEADLINE,AES,XSAVE,AVX,F16C,RDRAND,NXE,RDTSCP,LONG,LAHF,PERF,ITSC,FSGSBASE,SMEP,ERMS,SENSOR,ARAT cpu0: 256KB 64b/line 8-way L2 cache cpu0: TSC frequency 2594566800 Hz cpu0: apic clock running at 99MHz cpu0: mwait min=64, max=64, C-substates=0.2.1.1.2, IBE cpu at mainbus0: not configured cpu at mainbus0: not configured cpu at mainbus0: not configured ioapic0 at mainbus0: apid 2 pa 0xfec0, version 20, 24 pins 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 4 (EXP3) acpiprt5 at acpi0: bus -1 (EXP5) acpiprt6 at acpi0: bus -1 (EXP6) acpiprt7 at acpi0: bus -1 (EXP7) acpiprt8 at acpi0: bus -1 (EXP8) acpicpu at acpi0 not configured acpipwrres at acpi0 not configured acpitz at acpi0 not configured "PNP0C0D" at acpi0 not configured "PNP0C0E" at acpi0 not configured "LEN0071" at acpi0 not configured "LEN0015" at acpi0 not configured "SMO1200" at acpi0 not configured "PNP0C0A" at acpi0 not configured "ACPI0003" at acpi0 not configured "LEN0078" at acpi0 not configured "LEN0068" at acpi0 not configured "PNP0C14" at acpi0 not configured "PNP0C14" at acpi0 not configured "PNP0C14" at acpi0 not configured pci0 at mainbus0 bus 0 pchb0 at pci0 dev 0 function 0 "Intel Core 3G Host" rev 0x09 "Intel HD Graphics 4000" rev 0x09 at pci0 dev 2 function 0 not configured xhci0 at pci0 dev 20 function 0 "Intel 7 Series xHCI" rev 0x04: msi usb0 at xhci0: USB revision 3.0 uhub0 at usb0 configuration 1 interface 0 "Intel xHCI root hub" rev 3.00/1.00 addr 1 "Intel 7 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 3c:97:0e:60:8d:ca ehci0 at pci0 dev 26 function 0 "Intel 7 Series USB" rev 0x04: apic 2 int 16 usb1 at ehci0: USB revision 2.0 uhub1 at usb1 configuration 1 interface 0 "Intel EHCI root hub" rev 2.00/1.00 addr 1 "Intel 7 Series HD Audio" rev 0x04 at pci0 dev 27 function 0 not configured ppb0 at pci0 dev 28 function 0 "Intel 7 Series PCIE" rev 0xc4: msi pci1 at ppb0 bus 2 ppb1 at pci0 dev 28 function 1 "Intel 7 Series PCIE" rev 0xc4: msi pci2 at ppb1 bus 3 iwn0 at pci2 dev 0 function 0 "Intel Centrino Advanced-N 6205" rev 0x34: msi, MIMO 2T2R, MoW, address 60:67:20:f8:17:f4 ppb2 at pci0 dev 28 function 2 "Intel 7 Series PCIE" rev 0xc4: msi pci3 at ppb2 bus 4 sdhc0 at pci3 dev 0 function 0 "Ricoh 5U823 SD/MMC" rev 0x04: apic 2 int 18 sdhc0: SDHC 3.0, 50 MHz base clock sdmmc0 at sdhc0: 4-bit, sd high-speed, mmc high-speed ehci1 at pci0 dev 29 function 0 "Intel 7 Series USB" rev 0x04: apic 2 int 23 usb2 at ehci1: USB revision 2.0 uhub2 at usb2 configuration 1 interface 0 "Intel EHCI root hub" rev 2.00/1.00 addr 1 "Intel QM77 LPC" rev 0x04 at pci0 dev 31 function 0 not configured ahci0 at pci0 dev 31 function 2 "Intel 7 Series AHCI" rev 0x04: msi, AHCI 1.3 ahci0: port 0: 6.0Gb/s ahci0: port 1: 1.5Gb/s scsibus0 at ahci0: 32 targets sd0 at scsibus0 targ 0 lun 0: SCSI3 0/direct fixed naa.50025388400c34c6 sd0: 488386MB, 512 bytes/sector, 1000215216 sectors, thin cd0 at scsibus0 targ 1 lun 0: ATAPI 5/cdrom removable "Intel 7 Series SMBus" rev 0x04 at pci0 dev 31 function 3 not configured isa0 at mainbus0 pckbc0 at isa0 port 0x60/5 irq 1 irq 12 pckbd0 at pckbc0 (kbd slot) wskbd0 at pckbd0: console keyboard efifb0 at mainbus0: 1600x900, 32bpp wsdisplay0 at efifb0 mux 1: console (std, vt100 emulation), using wskbd0 "Lenovo H5321 gw" rev 2.00/0.00 addr 2 at uhub0 port 4 not configured uhub3 at uhub1 port 1 configuration 1 interface 0 "vendor 0x8087 product 0x0024" rev 2.00/0.00 addr 2 "Lenovo Integrated Smart Card Reader" rev 2.00/1.00 addr 3 at uhub3 port 1 not configure
Re: Is Matrox G200e supported?
On 23/09/17 02:56, Philippe PONCEBLANC wrote: > Hello, > "Why is my Matrox MGA G200e not supported?" on a Proliant ML150 G6, > OpenBSD 6.1 for I386, My full dmesg output, complete output of sysctl > and Xorg.0.log in this message. "Matrox G200e: back to software > rendering". 2d acceleration is not available. Gnome appears but the > windows of the programs move very slowly, I think it lacks a firmware > or settings for the server X. > > Kinds Regards > Philippe Ponceblanc > As Xenocara tracks Xorg then this may be related to this bug only recently fixed in Linux systems https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/1316035
Re: Wireless not working with Linksys
TimoMyyrä wrote: > I just got Linksys 1900ACS wireless router and it works great, except with > OpenBSD. I've got Thinkpad T430s running -current and I can't get DHCP lease > from the new > router. > I noticed lines: "dhclient[22294]: fatal in iwn0: yielding responsibility" in > messages file which might be relating to this. > > Any ideas what could be the problem and how to begin debugging this further? Does it work with 6.0? Does the network appear in scan?
Re: Wireless not working with Linksys
On 23 Sep 2017, Timo Myyrä wrote: > I just got Linksys 1900ACS wireless router and it works great, except with > OpenBSD. I've got Thinkpad T430s running -current and I can't get DHCP lease > from the new > router. > I noticed lines: "dhclient[22294]: fatal in iwn0: yielding responsibility" in > messages file which might be relating to this. > > Any ideas what could be the problem and how to begin debugging this further? Could try disabling some of the fancier wifi features / variants on the WAP to see if it then starts working better - there's sometimes a workaround or clue in the outcome of that. -- Mark
Re: Wireless not working with Linksys
"Ted Unangst" writes: > TimoMyyrä wrote: > >> I just got Linksys 1900ACS wireless router and it works great, except with >> OpenBSD. I've got Thinkpad T430s running -current and I can't get DHCP lease >> from the new >> router. >> I noticed lines: "dhclient[22294]: fatal in iwn0: yielding responsibility" in >> messages file which might be relating to this. >> >> Any ideas what could be the problem and how to begin debugging this further? > > Does it work with 6.0? Does the network appear in scan? Haven't tested the older release, as I said just got the new router. I can try later with older bsd.rd to see if it works with it. But scan results see the 2.4Ghz network but not the 5Ghz network: $ doas ifconfig iwn0 scan | grep MyNet nwid MyNet chan 11 bssid xx:xx:xx:xx:xx:xx -21dBm HT-MCS23 privacy,short_preamble,short_slottime,wpa2,wpa1 timo
Re: Wireless not working with Linksys
timo.my...@wickedbsd.net (Timo Myyrä) writes: > "Ted Unangst" writes: > >> TimoMyyrä wrote: >> >>> I just got Linksys 1900ACS wireless router and it works great, except with >>> OpenBSD. I've got Thinkpad T430s running -current and I can't get DHCP >>> lease from the new >>> router. >>> I noticed lines: "dhclient[22294]: fatal in iwn0: yielding responsibility" >>> in >>> messages file which might be relating to this. >>> >>> Any ideas what could be the problem and how to begin debugging this further? >> >> Does it work with 6.0? Does the network appear in scan? > > Haven't tested the older release, as I said just got the new router. > I can try later with older bsd.rd to see if it works with it. > > But scan results see the 2.4Ghz network but not the 5Ghz network: > > $ doas ifconfig iwn0 scan | grep MyNet > nwid MyNet chan 11 bssid xx:xx:xx:xx:xx:xx -21dBm HT-MCS23 > privacy,short_preamble,short_slottime,wpa2,wpa1 > > > timo Actually, did quick test and seems that I can get link and ip when booting 6.0 bsd.rd. Timo
Re: Wireless not working with Linksys
TimoMyyrä wrote: > > But scan results see the 2.4Ghz network but not the 5Ghz network: > > > > $ doas ifconfig iwn0 scan | grep MyNet > > nwid MyNet chan 11 bssid xx:xx:xx:xx:xx:xx -21dBm HT-MCS23 > > privacy,short_preamble,short_slottime,wpa2,wpa1 > > > > > > timo > > Actually, did quick test and seems that I can get link and ip when booting 6.0 > bsd.rd. Not that this is much help, but the reason I asked is I have (had) an AP (made by WD) with a similar problem. Worked without problems with 6.0, then sometime after that the new 802.11n code made it disappear. Can't associate, can't see the AP at all in ifconfig scan. The problem is unresolved (I ended up replacing the AP). There is a particular kind of packet which seems to be "invisible". But I'm out of my depth. Nobody else had seen this, but you appear to be the lucky second victim.
fu^3: wdc_pcmcia and ATA mode
Work continues on this issue. I found a copy of the CompactFlash 3.0 specification at [1]. In section 1.3, "Overview of CompactFlash Storage Card": from file cfspc3_0.pdf: > A CompactFlash storage card also runs in True IDE mode that is > electrically compatible with an IDE disk drive." This is obviously the way I'm trying to use the card. > Once the CompactFlash Storage Card has been configured by the host, > it appears to the host as a standard ATA (IDE) disk drive. Note the term 'disk drive'. OpenBSD finds not a drive, but a controller with a drive attached. That would appear to be PCMCIA (or, as the standard puts it, 'PC Card') mode, alright. In section 4.2, "Electrical Description": > The CompactFlash Storage Card functions in three basic modes: 1) PC > Card ATA using I/O Mode, Aha, that's indeed what OpenBSD's using! > 2) PC Card ATA using Memory Mode, This must be the 'memory-mapped' mode that NetBSD appears to (at least theoretically) support, and which might yield a performance improvement compared to mode 1). Might... > 3) True IDE Mode, which is compatible with most disk drives. Yup, that's what I want alright. And that's also what I foolishly expected to work... Next, in table 4, "Pin Assignments and Pin Type", the OE signal is shown to double as 'ATA SEL' in ATA mode. In the the following table 5, "Signal Description", the following hint is given: > To enable True IDE Mode this input should be grounded by the host. In section 4.7.1, "True IDE Mode I/O Function": > The CompactFlash Storage Card and CF+ Card can be configured in a > True IDE Mode of operation. The CompactFlash Storage Card is > configured in this mode only when the -OE input signal is grounded by > the host during the power off to power on cycle. Power off to power on? Yelp. One could of course physically wire it so, but then the host (and quite possibly its firmware!) would need to know wtf is going on, or else it'd get very confused... However, some escape is provided: > Optionally, the CompactFlash Storage Cards and CF+ Cards may support > the following optional detection methods: > > 1. The card is permitted to monitor the -OE (-ATA SEL) signal at any >time(s) and switch to PCMCIA mode upon detecting a high level on >the pin. > > 2. The card is permitted to re-arbitrate the interface mode >determination following a transition of the (-)RESET pin. > > 3. The card is permitted to monitor the -OE (-ATA SEL) signal at any >time(s) and switch to True IDE mode upon detection of a continuous >low level on pin for an extended period of time. 'continuous'? 'extended'? That would seem to be rather open to interpretation. Nonetheless, when supported by the card, and given approrpriate host hardware, any of these methods would appear to suffice. Section 6, "Software Interface", as a whole appears to confirm that the wdc(4) detected and used by OpenBSD is in fact on the card itself. Table 61, "Pinout Differences Between CF Storage Card and CF Adapter", shows that the OE signal *does not* double as 'ATA SEL' on the PCMCIA end, even though the wiring is supposed to be passive. This is worrying. Next we consult the PCMCIA specification, volume 8, "PC Card Host System Specification", found at [2]. Specifically, section 4, "PCI-to-CardBus Bridge Register Description". Nothings there appears to say anything about ATA mode, or software control of the OE signal -- it was clearly not on the mind of anyone involved in writing that standard. So this is where it ends :( Just another piece of pee-cee pseudo-standardization. Yuck. Not an OpenBSD problem. Sorry for the noise. Hope it's been useful regardless. --schaafuit. [1] http://rumkin.com/reference/aquapad/media/cfspc3_0.pdf [2] http://affon.narod.ru/08ho80.pdf
re: Thinkpad R40 varia
Hi, florian.ermi...@mailbox.org wrote: > Have you checked for a separate CMOS > battery - which is probably long dead? As a matter of fact I haven't yet. Stay tuned. > I would be surprised if there's more than > some diagnostic software for to ease the > job of IBM's customer support=2E > I installed OpenBSD on an ancient T20 > (which has a serial port, that's why I kept > it around) once and didn't look out for any=20 > "system partitions" Trouble is, it appears to be integrated with the BIOS to an unclear degree. > Probably be a second PCMCIA/CardBus=20 > slot=2E Those were important back then=2E Then why is it of the opposite gender? Upon further inspection, the guide rail also appears to be different. My best guess is still ATA... --schaafuit.
re: Thinkpad R40 varia
riccardo.mott...@libero.it wrote: > there is one, usually wrapped in a yellow plastic. a Lithium battery. I > have seen dozens of thinkpads of your vintage. From model to model it > might change place and way to access it. Usually under the palmrest or > under the keyboard. Sometimes near the RAM access door. Thanks, I'll cross-check with the manual and then have a look. > A non original hard-disk might give you a Bios error, but will work. No > need for any extra partition, you can install OpenBSD (or NetBSD or also > Linux) just straight on it. I have done that on many thinkpads, in > cluding models very similar to yours. Thanks for the assurance! I think I'll keep it for now as a curiosity, but it's good to know that I'm not so dependent on it as I had feared. --schaafuit.
Re: Wireless not working with Linksys
On Sat, Sep 23, 2017 at 12:18:22PM +0300, Timo Myyrä wrote: > $ doas ifconfig iwn0 scan | grep MyNet > nwid MyNet chan 11 bssid xx:xx:xx:xx:xx:xx -21dBm HT-MCS23 > privacy,short_preamble,short_slottime,wpa2,wpa1 Try disabling WPA1 on your AP. In your AP's configuration, look for config items such as "WPA2", "CCMP", "AES" and enable them. Disable anything labeled "WPA1" and/or "TKIP".
Re: Wireless not working with Linksys
On 2017-09-23, Timo Myyrä wrote: > "Ted Unangst" writes: > >> TimoMyyrä wrote: >> >>> I just got Linksys 1900ACS wireless router and it works great, except with >>> OpenBSD. I've got Thinkpad T430s running -current and I can't get DHCP >>> lease from the new >>> router. >>> I noticed lines: "dhclient[22294]: fatal in iwn0: yielding responsibility" >>> in >>> messages file which might be relating to this. >>> >>> Any ideas what could be the problem and how to begin debugging this further? >> >> Does it work with 6.0? Does the network appear in scan? > > Haven't tested the older release, as I said just got the new router. > I can try later with older bsd.rd to see if it works with it. > > But scan results see the 2.4Ghz network but not the 5Ghz network: > > $ doas ifconfig iwn0 scan | grep MyNet > nwid MyNet chan 11 bssid xx:xx:xx:xx:xx:xx -21dBm HT-MCS23 > privacy,short_preamble,short_slottime,wpa2,wpa1 > > > timo > > - does it associate or not? (Paste output from just "ifconfig iwn0") - what shows up in logs if you do "ifconfig iwn0 debug" and then "ifconfig iwn0 scan" ? - it might be useful to capture some beacons: tcpdump -n -s 4096 -y IEEE802_11_RADIO -v type mgt subtype beacon -i iwn0
fu: Thinkpad R40 varia
Alright, I opened the sucker up. First of all, it's a type 2722, w/ a 14" display. Sorry for omitting that information before. The CMOS battery is indeed there, wrapped in black rubber (or rubber-like plastic), under the keyboard, next to the keyboard and touchpad connectors. I suppose I'll see about replacing it, it ain't a standard one. While I haven't removed them, I also got a closer look at the PCMCIA/ATA slots. They are indeed as I described, though they *appear* to be connected to the same bus. It's small work so I might be wrong, though. I've decided to just nuke the hdd contents (minus the system partition, for now). Installing OpenBSD is more important =) --schaafuit.
Re: Wireless not working with Linksys
Stefan Sperling writes: > On Sat, Sep 23, 2017 at 12:18:22PM +0300, Timo Myyrä wrote: >> $ doas ifconfig iwn0 scan | grep MyNet >> nwid MyNet chan 11 bssid xx:xx:xx:xx:xx:xx -21dBm HT-MCS23 >> privacy,short_preamble,short_slottime,wpa2,wpa1 > > Try disabling WPA1 on your AP. In your AP's configuration, > look for config items such as "WPA2", "CCMP", "AES" and enable them. > Disable anything labeled "WPA1" and/or "TKIP". Ah, this worked. Switched the AP security mode from "WPA2/WPA Personal mixed" to "WPA2 Personal" and now I can associate and get DHCP lease from the AP. Seems the wpa1 support is needed when the AP is supporting both in order to negotiate which mode to support. Timo
6.2 snapshots and lumina
hi all . i tried amd64 snaphots (9/23) & lumina . the setting is simple --- cat .xsession exec start-lumina-desktop --- after using make world , lumina runs well . the desk top setting of xfce4 also appears on the lumina's desktop . 1) https://wiki.archlinux.org/index.php/Lumina says that Lumina DE is primarily targeted at FreeBSD, not Linux. 2) http://gihyo.jp/admin/serial/01/bsd-yomoyama/0069 says that gnome and kde use linux specific codes , so using them have too big effort for bsd . --- regards http://openbsd-akita.blogspot.jp/2017/09/openbsd-62-snapshots-september-23th.html
dmesg of 'OpenBSD i386' 'bsd' on 'Thinkpad R40'
Included below.
--schaafuit.
bsd wrote:
> OpenBSD 6.1 (GENERIC) #291: Sat Apr 1 13:49:08 MDT 2017
> dera...@i386.openbsd.org:/usr/src/sys/arch/i386/compile/GENERIC
> cpu0: Intel(R) Pentium(R) M processor 1300MHz ("GenuineIntel" 686-class) 1.30
> GHz
> cpu0:
> FPU,V86,DE,PSE,TSC,MSR,MCE,CX8,SEP,MTRR,PGE,MCA,CMOV,CFLUSH,DS,ACPI,MMX,FXSR,SSE,SSE2,TM,PBE,EST,TM2,PERF
> real mem = 535707648 (510MB)
> avail mem = 512741376 (488MB)
> mpath0 at root
> scsibus0 at mpath0: 256 targets
> mainbus0 at root
> bios0 at mainbus0: date 07/15/03, BIOS32 rev. 0 @ 0xfd7b0, SMBIOS rev. 2.31 @
> 0xe0010 (53 entries)
> bios0: vendor IBM version "1PET46WW (1.14 )" date 07/15/2003
> bios0: IBM 27223DG
> acpi0 at bios0: rev 2
> acpi0: sleep states S0 S3 S4 S5
> acpi0: tables DSDT FACP SSDT ECDT TCPA BOOT
> acpi0: wakeup devices LID_(S3) SLPB(S3) UART(S3) PCI0(S3) PCI1(S4) USB0(S3)
> USB1(S3) USB2(S3) AC9M(S4)
> acpitimer0 at acpi0: 3579545 Hz, 24 bits
> acpiec0 at acpi0
> acpiprt0 at acpi0: bus 0 (PCI0)
> acpiprt1 at acpi0: bus 1 (AGP_)
> acpiprt2 at acpi0: bus 2 (PCI1)
> acpipwrres0 at acpi0: PUBS, resource for USB0, USB1, USB7
> acpitz0 at acpi0: critical temperature is 97 degC
> acpibtn0 at acpi0: LID_
> acpibtn1 at acpi0: SLPB
> "PNP0303" at acpi0 not configured
> "IBM0057" at acpi0 not configured
> "PNP0501" at acpi0 not configured
> "PNP0400" at acpi0 not configured
> "IBM0071" at acpi0 not configured
> acpibat0 at acpi0: BAT0 model "IBM-02K6928" serial 2694 type LION oem
> "Panasonic"
> acpiac0 at acpi0: AC unit online
> acpithinkpad0 at acpi0
> acpivideo0 at acpi0: VID_
> bios0: ROM list: 0xc/0x1 0xe/0x1
> cpu0 at mainbus0: (uniprocessor)
> mtrr: Pentium Pro MTRR support, 8 var ranges, 88 fixed ranges
> cpu0: Enhanced SpeedStep 1300 MHz: speeds: 1300, 1200, 1000, 800, 600 MHz
> pci0 at mainbus0 bus 0: configuration mode 1 (bios)
> pchb0 at pci0 dev 0 function 0 "Intel 82855PM Host" rev 0x03
> intelagp0 at pchb0
> agp0 at intelagp0: aperture at 0xd000, size 0x1000
> ppb0 at pci0 dev 1 function 0 "Intel 82855PM AGP" rev 0x03
> pci1 at ppb0 bus 1
> radeondrm0 at pci1 dev 0 function 0 "ATI Radeon Mobility M7" rev 0x00
> drm0 at radeondrm0
> radeondrm0: irq 11
> uhci0 at pci0 dev 29 function 0 "Intel 82801DB USB" rev 0x01: irq 11
> uhci1 at pci0 dev 29 function 1 "Intel 82801DB USB" rev 0x01: irq 11
> uhci2 at pci0 dev 29 function 2 "Intel 82801DB USB" rev 0x01: irq 11
> ehci0 at pci0 dev 29 function 7 "Intel 82801DB USB" rev 0x01: irq 11
> usb0 at ehci0: USB revision 2.0
> uhub0 at usb0 configuration 1 interface 0 "Intel EHCI root hub" rev 2.00/1.00
> addr 1
> ppb1 at pci0 dev 30 function 0 "Intel 82801BAM Hub-to-PCI" rev 0x81
> pci2 at ppb1 bus 2
> cbb0 at pci2 dev 0 function 0 "TI PCI1510 CardBus" rev 0x00: irq 11
> ipw0 at pci2 dev 2 function 0 "Intel PRO/Wireless 2100" rev 0x04: irq 11,
> address 00:04:23:81:d8:72
> "TI TSB43AB21 FireWire" rev 0x00 at pci2 dev 7 function 0 not configured
> fxp0 at pci2 dev 8 function 0 "Intel PRO/100 VE" rev 0x81, i82562: irq 11,
> address 00:06:1b:d3:19:22
> inphy0 at fxp0 phy 1: i82562ET 10/100 PHY, rev. 0
> cardslot0 at cbb0 slot 0 flags 0
> cardbus0 at cardslot0: bus 3 device 0 cacheline 0x8, lattimer 0xb0
> pcmcia0 at cardslot0
> ichpcib0 at pci0 dev 31 function 0 "Intel 82801DBM LPC" rev 0x01
> pciide0 at pci0 dev 31 function 1 "Intel 82801DBM 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, LBA, 38154MB, 78140160 sectors
> wd0(pciide0:0:0): using PIO mode 4, Ultra-DMA mode 5
> atapiscsi0 at pciide0 channel 1 drive 0
> scsibus1 at atapiscsi0: 2 targets
> cd0 at scsibus1 targ 0 lun 0: ATAPI
> 5/cdrom removable
> cd0(pciide0:1:0): using PIO mode 4, Ultra-DMA mode 2
> ichiic0 at pci0 dev 31 function 3 "Intel 82801DB SMBus" rev 0x01: irq 11
> iic0 at ichiic0
> spdmem0 at iic0 addr 0x50: 256MB DDR SDRAM non-parity PC2100CL2.5
> spdmem1 at iic0 addr 0x51: 256MB DDR SDRAM non-parity PC2100CL2.5
> auich0 at pci0 dev 31 function 5 "Intel 82801DB AC97" rev 0x01: irq 11, ICH4
> ac97: codec id 0x41445374 (Analog Devices AD1981B)
> ac97: codec features headphone, 20 bit DAC, No 3D Stereo
> audio0 at auich0
> "Intel 82801DB Modem" rev 0x01 at pci0 dev 31 function 6 not configured
> usb1 at uhci0: USB revision 1.0
> uhub1 at usb1 configuration 1 interface 0 "Intel UHCI root hub" rev 1.00/1.00
> addr 1
> usb2 at uhci1: USB revision 1.0
> uhub2 at usb2 configuration 1 interface 0 "Intel UHCI root hub" rev 1.00/1.00
> addr 1
> usb3 at uhci2: USB revision 1.0
> uhub3 at usb3 configuration 1 interface 0 "Intel UHCI root hub" rev 1.00/1.00
> addr 1
> isa0 at ichpcib0
> isadma0 at isa0
> pckbc0 at isa0 port 0x60/5 irq 1 irq 12
> pckbd0 at pckbc0 (kbd slot)
> wskbd0 at pckbd0: console keyboard
> pms0 at pckbc0 (aux slot)
> wsmouse0 at pms0 mux 0
> pcppi0 at isa0 port 0x61
> spkr0 at pcppi0
> lpt2 at isa0 port 0x3bc/4: polled
> npx0 at isa0 port 0
fs level 0
Hi, While installing OpenBSD 6.1, out of sheer, raging paranoia, I created the root file system with -O 0. This worked fine, until I had extracted everything, and the kernel crashed with some uvm error (the automagic reboot came too soon for me to jot it down -- is it such a good idea for bsd.rd to reboot so soon after a panic?), teaching me a lesson. The obligatory fsck afterwards failed, as the level 0 fses are apparently considered to be too old. Fair enough, but is it such a good idea to continue support for them in newfs, and the kernel? I propose that we don't leave it half-supported like this, and that the relevant code be removed. Or is there some use for it, that I'm overlooking? --schaafuit.
Re: fs level 0
On 09/23/17 21:45, leo_...@volny.cz wrote: > While installing OpenBSD 6.1, out of sheer, raging paranoia, I created > the root file system with -O 0. This worked fine, until I had extracted > everything, and the kernel crashed with some uvm error (the automagic > reboot came too soon for me to jot it down -- is it such a good idea > for bsd.rd to reboot so soon after a panic?), teaching me a lesson. > > The obligatory fsck afterwards failed, as the level 0 fses are > apparently considered to be too old. Fair enough, but is it such a good > idea to continue support for them in newfs, and the kernel? > > I propose that we don't leave it half-supported like this, and that the > relevant code be removed. > > Or is there some use for it, that I'm overlooking? You probably read too much (or too little) into this part: 04.3BSD format file system. This option is primarily used to build root file systems that can be understood by older boot ROMs. Checking CVSweb, it looks like this part was in the newfs man page at initial import in 1995. So for the option to be useful, you would need to look for hardware and ROMs that were considered old in 1995 or even earlier. It's possible that modern OpenBSD still supports some hardware that actually matches the description, but others will know for sure. Anyway, your R40 is likely to be no older than 2003 or so, and to me at least it sounds like the most useful thing to do would be to simply reinstall with as little deviation from the defaults as possible. I didn't get hold of a ThinkPad that I was allowed to install OpenBSD on until about 2006, but by then the install and use experience was straightforward. - P -- Peter N. M. Hansteen, member of the first RFC 1149 implementation team http://bsdly.blogspot.com/ http://www.bsdly.net/ http://www.nuug.no/ "Remember to set the evil bit on all malicious network traffic" delilah spamd[29949]: 85.152.224.147: disconnected after 42673 seconds.
re: fs level 0
pe...@bsdly.net wrote: > You probably read too much (or too little) into this part: > > 04.3BSD format file system. This option is > primarily used to build root file systems that can > be understood by older boot ROMs. Yes. Although my dislike of fanciness for (especially) the root file system plays just as a big a part. Turns out things can get *too* unfancy =) > Checking CVSweb, it looks like this part was in the newfs man page at > initial import in 1995. So for the option to be useful, you would need > to look for hardware and ROMs that were considered old in 1995 or even > earlier. It's possible that modern OpenBSD still supports some hardware > that actually matches the description, but others will know for sure. Yeah. That's how I understood it. > Anyway, your R40 is likely to be no older than 2003 or so, and to me at > least it sounds like the most useful thing to do would be to simply > reinstall with as little deviation from the defaults as possible. That's asking a lot from a deviate ;) Seriously though, I already re-did my work, w/ the root fs at level 1. I take it as a lesson learned. > I didn't get hold of a ThinkPad that I was allowed to install OpenBSD on > until about 2006, but by then the install and use experience was > straightforward. I don't seem to be running into any ThinkPad-specific problems either. Except of course some hardware problems attributable to old age, but I can hardly blame OpenBSD for that . > - P --schaafuit.
fu^2: Thinkpad R40 varia
About the system partition: In the process of preparing to install OpenBSD, I set the 'IBM Predesktop Area' BIOS option to 'Disabled', expecting a hidden partition to appear. Imagine my surprise when only the NTFS partition (it came w/ m$ poop installed), which filled the entire disk, was visible. Did IBM really put it there? Either way, out of expediency, I blasted the whole thing to make room for OpenBSD. It seems to work fine, no error, and pressing the 'Access IBM' button during boot now brings up a small, textual boot menu, including an option to enter the BIOS setup. Yay! --schaafuit.
