Re: auto-boot
On Tue, 02 Feb 2021 17:51:35 +0100 Bastien Durel wrote: > PS: is 1kΩ enough ? I don't know if it's actually "high value" Well, "high value" is a relative term. In this case we're dealing with CMOS inputs which are quite high in impedance. 1kΩ might be "high" if we were talking TTL. I'd be aiming for at least 10kΩ, maybe 100kΩ. -- Stuart Longland (aka Redhatter, VK4MSL) I haven't lost my mind... ...it's backed up on a tape somewhere.
Re: auto-boot
Le mercredi 27 janvier 2021 à 08:20 -0700, Diana Eichert a écrit : > On Tue, Jan 26, 2021 at 5:30 AM Stuart Longland > wrote: > > > > On 25/1/21 11:40 pm, Bastien Durel wrote: > > > Hello, > > > > > > Short-circuit pins 3-5 using my DB9 cable as Mihai Popescu > > > said[1] > > > worked. > > > Alas, this setup prevent to plug-in the cable on the other side > > > ^^ > > > > > > But this confirm there is an hardware problem. > > The issue is the input RCV line is floating which causes spurious > characters, a > properly designed circuit should not have this issue. > > You really should insert a high ohm valu resistor in the path between > RCV and GND, > this would allow you to build a serial cable that still functions. > Hello again, I bought a pair of these : https://corrin.geekwu.org/owncloud/index.php/s/3Bci6SRDjR9gPgs and tried to put a 1kΩ resistor between pins 3 and 5, then reboot; but the router hanged again. I tried with pins 1-3 to make sure it was not a male/female numbering problem, but with no more success :( Worse : it did not boot with a wire between ports 3-5 (nor 1-5) Is there some other wiring to do to get the plug working ? (I tried to make it work before I plug actual cable, but maybe it's not possible ?) Thanks, PS: is 1kΩ enough ? I don't know if it's actually "high value" -- Bastien
Re: auto-boot
On 26/1/21 3:04 am, Mihai Popescu wrote: That short with a metallic wire was just for quick check. It is not recommended for prolonged usage! It will block any communication on the RS232 cable. Probably not very healthy for the RS-232 driver either. High-valued resistor is probably a safer bet. -- Stuart Longland (aka Redhatter, VK4MSL) I haven't lost my mind... ...it's backed up on a tape somewhere.
Re: auto-boot
On Tue, Jan 26, 2021 at 5:30 AM Stuart Longland wrote: > > On 25/1/21 11:40 pm, Bastien Durel wrote: > > Hello, > > > > Short-circuit pins 3-5 using my DB9 cable as Mihai Popescu said[1] > > worked. > > Alas, this setup prevent to plug-in the cable on the other side ^^ > > > > But this confirm there is an hardware problem. The issue is the input RCV line is floating which causes spurious characters, a properly designed circuit should not have this issue. You really should insert a high ohm valu resistor in the path between RCV and GND, this would allow you to build a serial cable that still functions.
Re: auto-boot
On 25/1/21 11:40 pm, Bastien Durel wrote: > Hello, > > Short-circuit pins 3-5 using my DB9 cable as Mihai Popescu said[1] > worked. > Alas, this setup prevent to plug-in the cable on the other side ^^ > > But this confirm there is an hardware problem. > > So if I understand well, I have to buy 2 of these[2], add a short- > circuit between pins in one side, and connet them with an ethernet > cable ? That's a possibility… another no-solder option as I say is you grab a suitable serial extension lead, chop it in half, and use screw terminal blocks to bridge the right connections make the appropriate cross-overs. Done that many times at work for an ad-hoc serial cable for wiring up various RS-485 serial interfaces (Moxa U-Port 1150s, Advantec industrial serial interfaces and el cheapo Jaycar no-name USB dongles) to Modbus and proprietary serial meter networks. A bonus with this approach is that you can easily change it if needed. A downside is it's less robust as the wires usually aren't designed for those kinds of stresses, so you may find some zip tied stress relief is needed. No good for a "professional" permanent install, but fine for private use or for a quick lash-up for testing purposes. There'll be some buzzing out of wires with a multimeter to figure out which wire is which, but for DE9 cables it usually isn't a big issue. It's not like you're trying to terminate a Ultra-160 SCSI cable. If you go the DE9→RJ-45 route, make sure you use a straight-through CAT5 cable, or you'll have much head scratching when stuff doesn't work. -- Stuart Longland (aka Redhatter, VK4MSL) I haven't lost my mind... ...it's backed up on a tape somewhere.
Re: auto-boot
That short with a metallic wire was just for quick check. It is not recommended for prolonged usage! It will block any communication on the RS232 cable. For future usage you still need a resistor.
Re: auto-boot
Le vendredi 22 janvier 2021 à 23:49 +1000, Stuart Longland a écrit : > On 21/1/21 7:48 am, Diana Eichert wrote: > > This is not as hard as you think. Get a couple (it is good to have > > extras and they are pretty cheap) RJ45-DB9 adapter, the pins > > will not be inserted in DB9 connector, therefore you can perform > > some > > wire surgery. Break open the RJ45 side, cut the cables from RJ45 > > connector. > > Another option is to get a DE9 serial cable and chop it in half. > > The big challenge is getting hold of such a beast. These days if you > walk into a computer shop and mutter things about serial ports, they > think you're talking about a place that sailors go for breakfast. > Hello, Short-circuit pins 3-5 using my DB9 cable as Mihai Popescu said[1] worked. Alas, this setup prevent to plug-in the cable on the other side ^^ But this confirm there is an hardware problem. So if I understand well, I have to buy 2 of these[2], add a short- circuit between pins in one side, and connet them with an ethernet cable ? Thanks, [1] https://corrin.geekwu.org/owncloud/index.php/s/fwPmq2CbyTy5mEX [2] https://www.amazon.fr/StarTech-com-Adaptateur-modulaire-RS232-RS422/dp/B6IRQA/ -- Bastien
Re: auto-boot
On 21/1/21 7:48 am, Diana Eichert wrote: > This is not as hard as you think. Get a couple (it is good to have > extras and they are pretty cheap) RJ45-DB9 adapter, the pins > will not be inserted in DB9 connector, therefore you can perform some > wire surgery. Break open the RJ45 side, cut the cables from RJ45 > connector. Another option is to get a DE9 serial cable and chop it in half. The big challenge is getting hold of such a beast. These days if you walk into a computer shop and mutter things about serial ports, they think you're talking about a place that sailors go for breakfast. -- Stuart Longland (aka Redhatter, VK4MSL) I haven't lost my mind... ...it's backed up on a tape somewhere.
Re: auto-boot
Correction: pin 3 and pin 5 must be connected.
Re: auto-boot
[ ... ] That serial port is a plug (male connector), so not so easy to put resistors on it. Plug the null modem cable in it, so you will get a socket (female connector) on the other. Grab the socket from the other end, and stick a plain metallic wire in pin 5 (GND) and 2 (RXD). Then check your boot sequence. No need for solder, adapters, rocket science schematics, etc. I doubt very much the noise is the problem, but it will not hurt to check. One can check the control pins of serial in code, so you need to be sure the bootcode doesn't check for some assert/deassert control lines. I remember about a serial connection between 2 OpenBSD machines that refused to work with RX, TX and GND only, I had to do a _proper_ null modem cable.
Re: auto-boot
we are way off course here folks, but I like serial for breakfast. On Wed, Jan 20, 2021 at 2:09 AM Bastien Durel wrote: > > Le mardi 19 janvier 2021 à 14:52 -0700, Diana Eichert a écrit : > > Hello > > > > Having spent way to many years working on serial devices it looks to > > me like either Rcv pin has noise on it because it is floating. If I > > remember correctly you can try a resistor between rcv and ground. > > > > diana > Hello, > > Thanks for the hint, but this is -- like Stuart's -- over my reach. I > have no soldering skills or tools, and the pins are very small[1] :( This is not as hard as you think. Get a couple (it is good to have extras and they are pretty cheap) RJ45-DB9 adapter, the pins will not be inserted in DB9 connector, therefore you can perform some wire surgery. Break open the RJ45 side, cut the cables from RJ45 connector. Now depending on whether this is DCE or DTE RCV can be pin 3 or pin 2, Ground is pin 5. Acquire a 50k ohm resistor, several small gauge wire nuts. Connect one wire with one end of resistor and twist on wire nut, do the same with the other end of the resistor. Insert one cable onto pin 5, the other to pin 3. Then test if you can reboot the system. If this doesn't work move the cable on pin 3 to pin 2. No soldering required and if it works you can pat your self on the back and tell everyone you are a hardware hacker. :-) diana
Re: auto-boot
On 1/20/21 10:01 AM, Bastien Durel wrote: If There is no software way to solve this problem, I shall need to buy a small HDMI screen and drop serial console ... If the console gets input from the serial port even with no cable plugged into it (and not just the other side disconnected), there's most likely something wrong with the port. Either it's malfunctioning on the electrical level, or some strange mode is set in the BIOS. best /m
Re: auto-boot
Le mardi 19 janvier 2021 à 14:52 -0700, Diana Eichert a écrit : > Hello > > Having spent way to many years working on serial devices it looks to > me like either Rcv pin has noise on it because it is floating. If I > remember correctly you can try a resistor between rcv and ground. > > diana Hello, Thanks for the hint, but this is -- like Stuart's -- over my reach. I have no soldering skills or tools, and the pins are very small[1] :( If There is no software way to solve this problem, I shall need to buy a small HDMI screen and drop serial console ... Thanks anyway, [1] https://corrin.geekwu.org/owncloud/index.php/s/QZXd8WBPimCxSs6 -- Bastien
Re: auto-boot
Hello Having spent way to many years working on serial devices it looks to me like either Rcv pin has noise on it because it is floating. If I remember correctly you can try a resistor between rcv and ground. diana On Mon, Jan 18, 2021 at 2:30 AM Bastien Durel wrote: > Hello, > > I set boot.conf to this : > > # cat -e /etc/boot.conf > stty com0 115200$ > set tty com0$ > set timeout 5$ > # > > But the router does not boot without beeing connected to a powered-up > machine :( > > -- > Bastien > > -- - Past hissy-fits are not a predictor of future hissy-fits. Nick Holland(06 Dec 2005) To announce that there must be no criticism of the president, or that we are to stand by the president, right or wrong, is not only unpatriotic and servile, but is morally treasonable to the American public. - Theodore Roosevelt(1918)
Re: auto-boot
Le samedi 16 janvier 2021 à 12:49 +0100, Marcus MERIGHI a écrit :
> bast...@durel.org (Bastien Durel), 2021.01.14 (Thu) 18:07 (CET):
> > Le jeudi 14 janvier 2021 à 16:59 +0100, Marcus MERIGHI a écrit :
> > > bast...@durel.org (Bastien Durel), 2021.01.14 (Thu) 16:05 (CET):
> > > > Le jeudi 14 janvier 2021 à 15:47 +0100, Marcus MERIGHI a
> > > > écrit :
> > > > > bast...@durel.org (Bastien Durel), 2021.01.14 (Thu) 10:20
> > > > > (CET):
> > > > > > I have a router connected via a serial port to another
> > > > > > machine
> > > > > > (which
> > > > > > is usually powered off), wich fails to boot until I connect
> > > > > > and
> > > > > > validate the boot> prompt
> > > > > >
> > > > > > I configured my boot.conf as it follows :
> > > > > >
> > > > > > # cat
> > > > > > /etc/boot.conf
> > > > > >
> > > > > > set timeout 10
> > > > > > set tty com0
> > > > >
> > > > > I usually have
> > > > >
> > > > > stty com0 115200
> > > > > set tty com0
> > > > > set timeout 2
> > > > >
> > > > > and the machines boot automagically...
> > > > >
> > > > > Marcus
> > > > >
> > > > Actually, it looks like the automagic boot depends on the
> > > > status of
> > > > the
> > > > attached computer : when it runs, the router boots
> > > > automagically,
> > > > and
> > > > when it does not, then the boot waits until I press enter
> > > > (after
> > > > booting it, obviously)
> > >
> > > Ah, I failed on getting what you meant!
> > >
> > > Emitting wild guesses now... As soon as the boot> prompt receives
> > > input,
> > > it cancels the timout counter (and doesn't auto-boot). Could it
> > > be
> > > that
> > > your non-auto-booting machine receives something that looks like
> > > input
> > > to the boot> prompt? Can you test with the serial cable detached?
> > >
> >
> > Done that; that's very strange : the router did not auto-boot, but
> > did
> > as soon as I plugged-in the serial cable in (I left minicom running
> > on
> > the other box) (or maybe after a few seconds, I did not checked in
> > real
> > time)
>
> so you have ruled out the second box, good!
>
> Things I'd try...
>
> - any stray empty lines in /etc/boot.conf?
> I'm not saying these would cause any harm, but I'd try
> - add the speed setting ("stty com0 115200")
> - move "set timeout X" to the end
>
> good luck! and please report back if you solve this puzzle!
>
> Marcus
>
Hello,
I set boot.conf to this :
# cat -e /etc/boot.conf
stty com0 115200$
set tty com0$
set timeout 5$
#
But the router does not boot without beeing connected to a powered-up
machine :(
--
Bastien
Re: auto-boot
On 2021-01-16, Marcus MERIGHI wrote:
> bast...@durel.org (Bastien Durel), 2021.01.14 (Thu) 18:07 (CET):
>> Le jeudi 14 janvier 2021 à 16:59 +0100, Marcus MERIGHI a écrit :
>> > bast...@durel.org (Bastien Durel), 2021.01.14 (Thu) 16:05 (CET):
>> > > Le jeudi 14 janvier 2021 à 15:47 +0100, Marcus MERIGHI a écrit :
>> > > > bast...@durel.org (Bastien Durel), 2021.01.14 (Thu) 10:20 (CET):
>> > > > > I have a router connected via a serial port to another machine
>> > > > > (which
>> > > > > is usually powered off), wich fails to boot until I connect and
>> > > > > validate the boot> prompt
>> > > > >
>> > > > > I configured my boot.conf as it follows :
>> > > > >
>> > > > > # cat
>> > > > > /etc/boot.conf
>> > > > > set timeout 10
>> > > > > set tty com0
>> > > >
>> > > > I usually have
>> > > >
>> > > > stty com0 115200
>> > > > set tty com0
>> > > > set timeout 2
>> > > >
>> > > > and the machines boot automagically...
>> > > >
>> > > > Marcus
>> > > >
>> > > Actually, it looks like the automagic boot depends on the status of
>> > > the
>> > > attached computer : when it runs, the router boots automagically,
>> > > and
>> > > when it does not, then the boot waits until I press enter (after
>> > > booting it, obviously)
>> >
>> > Ah, I failed on getting what you meant!
>> >
>> > Emitting wild guesses now... As soon as the boot> prompt receives
>> > input,
>> > it cancels the timout counter (and doesn't auto-boot). Could it be
>> > that
>> > your non-auto-booting machine receives something that looks like
>> > input
>> > to the boot> prompt? Can you test with the serial cable detached?
>> >
>>
>> Done that; that's very strange : the router did not auto-boot, but did
>> as soon as I plugged-in the serial cable in (I left minicom running on
>> the other box) (or maybe after a few seconds, I did not checked in real
>> time)
>
> so you have ruled out the second box, good!
>
> Things I'd try...
>
> - any stray empty lines in /etc/boot.conf?
> I'm not saying these would cause any harm, but I'd try
> - add the speed setting ("stty com0 115200")
> - move "set timeout X" to the end
>
> good luck! and please report back if you solve this puzzle!
On some machines you may need to loop back the RS232 control lines.
I normally use a DE9-RJ45 adapter on serial console machines, in most
cases I just connect up RXD TXD GND, but if it's one of those machines
then I'll short CD DTR DSR CTS together (pins 1/4/6/8 on the DE9 side).
Re: auto-boot
bast...@durel.org (Bastien Durel), 2021.01.14 (Thu) 18:07 (CET):
> Le jeudi 14 janvier 2021 à 16:59 +0100, Marcus MERIGHI a écrit :
> > bast...@durel.org (Bastien Durel), 2021.01.14 (Thu) 16:05 (CET):
> > > Le jeudi 14 janvier 2021 à 15:47 +0100, Marcus MERIGHI a écrit :
> > > > bast...@durel.org (Bastien Durel), 2021.01.14 (Thu) 10:20 (CET):
> > > > > I have a router connected via a serial port to another machine
> > > > > (which
> > > > > is usually powered off), wich fails to boot until I connect and
> > > > > validate the boot> prompt
> > > > >
> > > > > I configured my boot.conf as it follows :
> > > > >
> > > > > # cat
> > > > > /etc/boot.conf
> > > > > set timeout 10
> > > > > set tty com0
> > > >
> > > > I usually have
> > > >
> > > > stty com0 115200
> > > > set tty com0
> > > > set timeout 2
> > > >
> > > > and the machines boot automagically...
> > > >
> > > > Marcus
> > > >
> > > Actually, it looks like the automagic boot depends on the status of
> > > the
> > > attached computer : when it runs, the router boots automagically,
> > > and
> > > when it does not, then the boot waits until I press enter (after
> > > booting it, obviously)
> >
> > Ah, I failed on getting what you meant!
> >
> > Emitting wild guesses now... As soon as the boot> prompt receives
> > input,
> > it cancels the timout counter (and doesn't auto-boot). Could it be
> > that
> > your non-auto-booting machine receives something that looks like
> > input
> > to the boot> prompt? Can you test with the serial cable detached?
> >
>
> Done that; that's very strange : the router did not auto-boot, but did
> as soon as I plugged-in the serial cable in (I left minicom running on
> the other box) (or maybe after a few seconds, I did not checked in real
> time)
so you have ruled out the second box, good!
Things I'd try...
- any stray empty lines in /etc/boot.conf?
I'm not saying these would cause any harm, but I'd try
- add the speed setting ("stty com0 115200")
- move "set timeout X" to the end
good luck! and please report back if you solve this puzzle!
Marcus
Re: auto-boot
Le jeudi 14 janvier 2021 à 16:59 +0100, Marcus MERIGHI a écrit : > bast...@durel.org (Bastien Durel), 2021.01.14 (Thu) 16:05 (CET): > > Le jeudi 14 janvier 2021 à 15:47 +0100, Marcus MERIGHI a écrit : > > > bast...@durel.org (Bastien Durel), 2021.01.14 (Thu) 10:20 (CET): > > > > I have a router connected via a serial port to another machine > > > > (which > > > > is usually powered off), wich fails to boot until I connect and > > > > validate the boot> prompt > > > > > > > > I configured my boot.conf as it follows : > > > > > > > > # cat > > > > /etc/boot.conf > > > > set timeout 10 > > > > set tty com0 > > > > > > I usually have > > > > > > stty com0 115200 > > > set tty com0 > > > set timeout 2 > > > > > > and the machines boot automagically... > > > > > > Marcus > > > > > Actually, it looks like the automagic boot depends on the status of > > the > > attached computer : when it runs, the router boots automagically, > > and > > when it does not, then the boot waits until I press enter (after > > booting it, obviously) > > Ah, I failed on getting what you meant! > > Emitting wild guesses now... As soon as the boot> prompt receives > input, > it cancels the timout counter (and doesn't auto-boot). Could it be > that > your non-auto-booting machine receives something that looks like > input > to the boot> prompt? Can you test with the serial cable detached? > Done that; that's very strange : the router did not auto-boot, but did as soon as I plugged-in the serial cable in (I left minicom running on the other box) (or maybe after a few seconds, I did not checked in real time) -- Bastien
Re: auto-boot
bast...@durel.org (Bastien Durel), 2021.01.14 (Thu) 16:05 (CET): > Le jeudi 14 janvier 2021 à 15:47 +0100, Marcus MERIGHI a écrit : > > bast...@durel.org (Bastien Durel), 2021.01.14 (Thu) 10:20 (CET): > > > I have a router connected via a serial port to another machine > > > (which > > > is usually powered off), wich fails to boot until I connect and > > > validate the boot> prompt > > > > > > I configured my boot.conf as it follows : > > > > > > # cat > > > /etc/boot.conf > > > set timeout 10 > > > set tty com0 > > > > I usually have > > > > stty com0 115200 > > set tty com0 > > set timeout 2 > > > > and the machines boot automagically... > > > > Marcus > > > Actually, it looks like the automagic boot depends on the status of the > attached computer : when it runs, the router boots automagically, and > when it does not, then the boot waits until I press enter (after > booting it, obviously) Ah, I failed on getting what you meant! Emitting wild guesses now... As soon as the boot> prompt receives input, it cancels the timout counter (and doesn't auto-boot). Could it be that your non-auto-booting machine receives something that looks like input to the boot> prompt? Can you test with the serial cable detached? (It would be more comprehensible if it was the other way round: not booting with the supervising machine beeing *on* and by some strange mishaps sending input to the boot> prompt.) Marcus
Re: auto-boot
Le jeudi 14 janvier 2021 à 15:47 +0100, Marcus MERIGHI a écrit : > Hello, > > bast...@durel.org (Bastien Durel), 2021.01.14 (Thu) 10:20 (CET): > > I have a router connected via a serial port to another machine > > (which > > is usually powered off), wich fails to boot until I connect and > > validate the boot> prompt > > > > I configured my boot.conf as it follows : > > > > # cat > > /etc/boot.conf > > set timeout 10 > > set tty com0 > > I usually have > > stty com0 115200 > set tty com0 > set timeout 2 > > and the machines boot automagically... > > Marcus > Actually, it looks like the automagic boot depends on the status of the attached computer : when it runs, the router boots automagically, and when it does not, then the boot waits until I press enter (after booting it, obviously) -- Bastien
Re: auto-boot
Hello, bast...@durel.org (Bastien Durel), 2021.01.14 (Thu) 10:20 (CET): > I have a router connected via a serial port to another machine (which > is usually powered off), wich fails to boot until I connect and > validate the boot> prompt > > I configured my boot.conf as it follows : > > # cat /etc/boot.conf > set timeout 10 > set tty com0 I usually have stty com0 115200 set tty com0 set timeout 2 and the machines boot automagically... Marcus
auto-boot
Hello, I have a router connected via a serial port to another machine (which is usually powered off), wich fails to boot until I connect and validate the boot> prompt I configured my boot.conf as it follows : # cat /etc/boot.conf set timeout 10 set tty com0 # Shouln't the box boot by itself after 10 seconds ? Regards, dmesg: OpenBSD 6.8 (GENERIC.MP) #3: Thu Jan 7 07:35:39 MST 2021 r...@syspatch-68-amd64.openbsd.org:/usr/src/sys/arch/amd64/compile/GENERIC.MP real mem = 4196298752 (4001MB) avail mem = 4054081536 (3866MB) random: good seed from bootblocks mpath0 at root scsibus0 at mpath0: 256 targets mainbus0 at root bios0 at mainbus0: SMBIOS rev. 2.8 @ 0x8ce21000 (85 entries) bios0: vendor American Megatrends Inc. version "5.12" date 11/23/2018 bios0: Default string Default string acpi0 at bios0: ACPI 6.0 acpi0: sleep states S0 S3 S5 acpi0: tables DSDT FACP APIC FPDT FIDT MCFG SSDT SSDT HPET SSDT SSDT UEFI SSDT LPIT SSDT SSDT SSDT SSDT DBGP DBG2 SSDT DMAR ASF! WSMT acpi0: wakeup devices RP09(S3) PXSX(S3) RP10(S3) PXSX(S3) RP11(S3) PXSX(S3) RP12(S3) PXSX(S3) RP13(S3) PXSX(S3) RP01(S3) PXSX(S3) RP02(S3) PXSX(S3) RP03(S3) PXSX(S3) [...] acpitimer0 at acpi0: 3579545 Hz, 24 bits acpimadt0 at acpi0 addr 0xfee0: PC-AT compat cpu0 at mainbus0: apid 0 (boot processor) cpu0: Intel(R) Celeron(R) CPU 3865U @ 1.80GHz, 1696.62 MHz, 06-8e-09 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,EST,TM2,SSSE3,SDBG,CX16,xTPR,PDCM,PCID,SSE4.1,SSE4.2,x2APIC,MOVBE,POPCNT,DEADLINE,AES,XSAVE,RDRAND,NXE,PAGE1GB,RDTSCP,LONG,LAHF,ABM,3DNOWP,PERF,ITSC,FSGSBASE,TSC_ADJUST,SGX,SMEP,ERMS,INVPCID,MPX,RDSEED,SMAP,CLFLUSHOPT,PT,SRBDS_CTRL,MD_CLEAR,TSXFA,IBRS,IBPB,STIBP,L1DF,SSBD,SENSOR,ARAT,XSAVEOPT,XSAVEC,XGETBV1,XSAVES,MELTDOWN cpu0: 256KB 64b/line 8-way L2 cache cpu0: smt 0, core 0, package 0 mtrr: Pentium Pro MTRR support, 10 var ranges, 88 fixed ranges cpu0: apic clock running at 24MHz cpu0: mwait min=64, max=64, C-substates=0.2.1.2.4.1.1.1, IBE cpu1 at mainbus0: apid 2 (application processor) cpu1: Intel(R) Celeron(R) CPU 3865U @ 1.80GHz, 1696.06 MHz, 06-8e-09 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,PBE,SSE3,PCLMUL,DTES64,MWAIT,DS-CPL,VMX,EST,TM2,SSSE3,SDBG,CX16,xTPR,PDCM,PCID,SSE4.1,SSE4.2,x2APIC,MOVBE,POPCNT,DEADLINE,AES,XSAVE,RDRAND,NXE,PAGE1GB,RDTSCP,LONG,LAHF,ABM,3DNOWP,PERF,ITSC,FSGSBASE,TSC_ADJUST,SGX,SMEP,ERMS,INVPCID,MPX,RDSEED,SMAP,CLFLUSHOPT,PT,SRBDS_CTRL,MD_CLEAR,TSXFA,IBRS,IBPB,STIBP,L1DF,SSBD,SENSOR,ARAT,XSAVEOPT,XSAVEC,XGETBV1,XSAVES,MELTDOWN cpu1: 256KB 64b/line 8-way L2 cache cpu1: smt 0, core 1, package 0 ioapic0 at mainbus0: apid 2 pa 0xfec0, version 20, 120 pins acpimcfg0 at acpi0 acpimcfg0: addr 0xe000, bus 0-255 acpihpet0 at acpi0: 2399 Hz acpiprt0 at acpi0: bus 0 (PCI0) acpiprt1 at acpi0: bus -1 (PEG0) acpiprt2 at acpi0: bus -1 (PEG1) acpiprt3 at acpi0: bus -1 (PEG2) acpiprt4 at acpi0: bus -1 (RP09) acpiprt5 at acpi0: bus -1 (RP10) acpiprt6 at acpi0: bus -1 (RP11) acpiprt7 at acpi0: bus -1 (RP12) acpiprt8 at acpi0: bus -1 (RP13) acpiprt9 at acpi0: bus 1 (RP01) acpiprt10 at acpi0: bus 2 (RP02) acpiprt11 at acpi0: bus 3 (RP03) acpiprt12 at acpi0: bus 4 (RP04) acpiprt13 at acpi0: bus 5 (RP05) acpiprt14 at acpi0: bus 6 (RP06) acpiprt15 at acpi0: bus -1 (RP07) acpiprt16 at acpi0: bus -1 (RP08) acpiprt17 at acpi0: bus -1 (RP17) acpiprt18 at acpi0: bus -1 (RP18) acpiprt19 at acpi0: bus -1 (RP19) acpiprt20 at acpi0: bus -1 (RP20) acpiprt21 at acpi0: bus -1 (RP21) acpiprt22 at acpi0: bus -1 (RP22) acpiprt23 at acpi0: bus -1 (RP23) acpiprt24 at acpi0: bus -1 (RP24) acpiprt25 at acpi0: bus -1 (RP14) acpiprt26 at acpi0: bus -1 (RP15) acpiprt27 at acpi0: bus -1 (RP16) acpiec0 at acpi0: not present acpipci0 at acpi0 PCI0: 0x 0x0011 0x0001 acpicmos0 at acpi0 "INT344B" at acpi0 not configured acpibtn0 at acpi0: SLPB "PNP0C14" at acpi0 not configured "INT33A1" at acpi0 not configured acpibtn1 at acpi0: PWRB "PNP0C0B" at acpi0 not configured "PNP0C0B" at acpi0 not configured "PNP0C0B" at acpi0 not configured "PNP0C0B" at acpi0 not configured "PNP0C0B" at acpi0 not configured acpicpu0 at acpi0: C3(200@1034 mwait.1@0x60), C2(200@151 mwait.1@0x33), C1(1000@1 mwait.1), PSS acpicpu1 at acpi0: C3(200@1034 mwait.1@0x60), C2(200@151 mwait.1@0x33), C1(1000@1 mwait.1), PSS acpipwrres0 at acpi0: FN00, resource for FAN0 acpipwrres1 at acpi0: FN01, resource for FAN1 acpipwrres2 at acpi0: FN02, resource for FAN2 acpipwrres3 at acpi0: FN03, resource for FAN3 acpipwrres4 at acpi0: FN04, resource for FAN4 acpitz0 at acpi0: critical temperature is 119 degC acpitz1 at acpi0: critical temperature is 119 degC acpivideo0 at acpi0: GFX0 acpivout0 at acpivideo0: DD1F cpu0: using VERW MDS workaround (except on vmm entry) cpu0: Enhanced SpeedStep 1696 MHz: speeds: 1801
