Hi,
I found out that playing with suspend/resume (using acpiconf -s 3) on a
thinkpad x201 running 11.0-RC2 changes something in CMOS that prevents
poweroff from working.
I managed to trigger the problem om two x201 laptops (though from the
a single 11.0-RC2 installation).
Opening up the laptops
In your letter dated Wed, 7 Sep 2016 22:58:29 + you wrote:
>Any chance you can try this with 10.3-RELEASE?
On 10.3, I get a kernel panic during suspend (in something vesa related), so I
can't trigger the problem there.
On 11.0-RC2 suspend works, resume mostly works except that the screen sta
The main culprit seems to be putting 'hw.acpi.reset_video=1' in
/boot/loader.conf
this causes resume to hang half way through. I managed to trigger
CMOS corruption once, but I can't systematically trigger it.
Without hw.acpi.reset_video=1 in /boot/loader.conf, resume works except that
the screen
>What graphics driver are you using?
Just the default:
'VT(vga): resolution 640x480'
Booting with -v and switching I now noticed that each time I switch to a
different console I get a line
'Timeout initializing vt_vga'
___
freebsd-current@freebsd.org
In your letter dated Fri, 9 Sep 2016 17:39:42 +0200 you wrote:
>Hello, I am sorry if I did not introduce myself properly: I am a subscriber
>on this list, I have read this thread and I think that my own problem is
>related: I also have a Thinkpad X201 and I have been unable to
>suspend/resume with
In your letter dated Fri, 9 Sep 2016 07:51:35 -0700 you wrote:
>is it too new to "kldload i915kms" ?
Yes, i915kms does the trick.
In X, suspend/resume works. On a console it requires a console switch
go get screen output. It would be nice if the driver could do this
automaticaly.
I guess now the
>Note, releases from 13.2 and earlier are
>still problematic due to a file name being replaced with a directory of
>the same name. A patch is being tested currently, and we hope to have
>this resolved for 14.0-BETA4.
I tried upgrading from 13.2 to BETA4 and it seems that the issue is still
there.
>Also as the Moore's law curve flattens expect the life of these
>older, but not so old, machines to live quiet some time. I
>believe we are talking sandy bridge and earlier? If that is
>corret Sandy bridge is still a very viable system.
I noticed this lack of love for older systems recently.
>It's not that hard create a mbr based usb-stick. Far easier than to find a
>CD burner.
'Not hard' means
- undocumented. Or at least, if you start with release notes and install
instructions you won't find it.
- Probably only works if you already have a FreeBSD system.
And if it is indeed 'not
I tried both FreeBSD-11.2-BETA2-amd64-bootonly.iso.xz and
FreeBSD-11.2-BETA2-amd64-mini-memstick.img.xz on a Dell PowerEdge 2950
BIOS version 2.7.0. With both images, the USB stick is not recognized.
For reference I tried an image for a random other OS and in that case the
USB stick is recognize
>Can you download the image from
>https://people.freebsd.org/~emaste/mini-image.amd64.xz, uncompress and
>write it to a USB stick and try on this system? This is a
>MBR-partitioned dual-mode test image. It's not an installer - it
>should just boot to a login prompt - but can be used to test this
>s
>Strange. Can you try an updated test image of mine
>(https://people.freebsd.org/~emaste/mini-image-2018-05-28.xz)
That gives a 404.
I have the strong suspision that your previous image doesn't get recognized as
bootable because the C/H/S values are not filled in.
___
>https://download.freebsd.org/ftp/snapshots/amd64/amd64/ISO-IMAGES/12.0/FreeBSD
>-12.0-CURRENT-amd64-20180529-r334337-mini-memstick.img
Works fine on a Lenovo ThinkPad x201
Fails on a Dell PowerEdge 2950
- The USB stick doen't show up in the boot menu
- After fixing the partition table entries, t
13 matches
Mail list logo
