Re: I want all my 4GB!!!

2009-07-21 Thread Bjørn Mork
James Brown  writes:

> There is 3071MB RAM I can see in my BIOS.

I must be missing something, but let me ask the stupid question:  Why do
you think Linux should something else?


Bjørn


-- 
To UNSUBSCRIBE, email to debian-laptop-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org



Re: VM Ware Player under Debian Lenny AMD64 on laptop

2009-07-24 Thread Bjørn Mork
James Brown  writes:

> When I tried install the kvm, the system tell me: "Your system does not
> have the CPU extensions required to use KVM. Not doing anything. failed!"

from the kvm package description:


 KVM requires your system to support hardware virtualization, provided by AMD's
 SVM capability or Intel's VT. To find out if your processor has the necessary
 support, do as follows:
 .
 * Make sure you run Linux 2.6.16 or newer for AMD processors, or
 Linux 2.6.15 for Intel processors.  Older Linux versions do not report
 the virtualization capabilities.
 .
 * Run this command in a shell: egrep '^flags.*(vmx|svm)' /proc/cpuinfo
 .
 If it prints anything, the processor provides hardware virtualization
 support and is suitable for use with KVM.




But do check your BIOS setup if you think your CPU should support
hardware virtualization.  Most have some option to disable it, and it
may be disabled by default.

You'll probably have to check the Intel or AMD web sites to find out if
your CPU is supposed to have such support.


Bjørn


-- 
To UNSUBSCRIBE, email to debian-laptop-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org



Re: VM Ware Player under Debian Lenny AMD64 on laptop

2009-07-24 Thread Bjørn Mork
James Brown  writes:
> Bjørn Mork wrote:
>
>> But do check your BIOS setup if you think your CPU should support
>> hardware virtualization.  Most have some option to disable it, and it
>> may be disabled by default.
>>   
> What is the name of item I need to enable in BIOS if it exist in my BIOS?

Depends. It should be an option related to the CPU, and it will often
include the word "virtualization".

But I've also seen "Vanderpool Technology" used without any further
explanations...


Bjørn


-- 
To UNSUBSCRIBE, email to debian-laptop-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org



Re: VM Ware Player under Debian Lenny AMD64 on laptop

2009-07-24 Thread Bjørn Mork
lsore...@csclub.uwaterloo.ca (Lennart Sorensen) writes:
> On Fri, Jul 24, 2009 at 08:32:22PM +0200, Bjørn Mork wrote:
>> Depends. It should be an option related to the CPU, and it will often
>> include the word "virtualization".
>> 
>> But I've also seen "Vanderpool Technology" used without any further
>> explanations...
>
> What do you think 'VT' means? :)

I know now :-)

But a small additional text, like "(hardware virtualization support)"
wouldn't have hurt...


Bjørn


-- 
To UNSUBSCRIBE, email to debian-laptop-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org



Re: VM Ware Player under Debian Lenny AMD64 on laptop

2009-07-24 Thread Bjørn Mork
James Brown  writes:

> model name : Intel(R) Core(TM)2 CPU T5500 @ 1.66GHz

That one is supposed to support VT according to
http://ark.intel.com/Product.aspx?id=27253



Bjørn


-- 
To UNSUBSCRIBE, email to debian-laptop-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org



Re: Mini-PCI WifiCard experience?

2011-01-19 Thread Bjørn Mork
Michelle Konzack  writes:
> Am 2011-01-19 10:10:36, hacktest Du folgendes herunter:
>> Hello,
>> 
>> in my Laptop there is an Intel 3945ABG and it works fine.
>> Also take a look at this page: http://wiki.debian.org/iwlwifi
>
> OK tnaks, found the Link to the "ipw2200" and the
> non-free firmware is provided by the Debian Project.

You should read http://www.intellinuxwireless.org/?n=FAQ&s=license
before buying older Intel wireless cards.  The modern cards are better
in all ways, even wrt licensing.  Don't buy old junk just because you
can get it on eBay.


Bjørn


-- 
To UNSUBSCRIBE, email to debian-laptop-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: http://lists.debian.org/87zkqxyt4z@nemi.mork.no



Re: Measures against overheating

2013-04-11 Thread Bjørn Mork
Stefan Monnier  writes:

>> into some random mailing list question.  For example, you made me just
>> install cpufreqd on my PC where i never considered that a priority.
>
> Nowadays installing cpufrequtils should be all you need to do.

No, actually, nowadays you don't even have to do that.  CPU frequency
scaling will Just Work(tm) by default, with no userspace interaction at
all:

 http://bugs.debian.org/678116
 http://bugs.debian.org/664813


Bjørn


--
To UNSUBSCRIBE, email to debian-laptop-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: http://lists.debian.org/87li8pwew4@nemi.mork.no



Re: Solid State Drive BIOS update and Memory Cell Clearing

2014-12-16 Thread Bjørn Mork
Florian Reitmeir  writes:

> All ssd should support TRIM, and all do, except some very old models.

The original X301 64GB and 128GB Samsung SSDs are definitely in the
"very old models" category.  They were manufactured in 2008, well before
TRIM became a standard feature on SSDs.

Personally I would throw the old SSD away and install a modern mSATA SSD
using an 1.8" micro-SATA to mSATA adapter instead.  In any case, that's
what I've done on my X301, which originally had the 128GB version of the
Samsung SSD.

Note that there are reports of mSATA SSDs not being recognized properly,
without the exact mechanisms being known.  So google the success stories
before going down this route.

And just to be clear:  No, you cannot install mSATA SSDs in any of the
mini-PCIe slots on the X301.  And no, it does not support 2.5" SSDs.
There are 3rd party adapters for the DVD slot, but that slot only
supports PATA drives [1] so this is not recommended - for the primary drive
anyway.


[1] I've been told the optical slot is PATA because all SATA DVD drives
  at the time were thicker.  The X301 DVD drive is exceptionally thin.


Bjørn


--
To UNSUBSCRIBE, email to debian-laptop-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: https://lists.debian.org/8761db4blz@nemi.mork.no



Re: No halt/poweroff on an EliteBook 840 G1 after upgrade

2014-12-18 Thread Bjørn Mork
Michael  writes:

> Edit /etc/default/halt and change the value as Eddy writes.
>
> Yes, systemd is probably the cause, it replaced pm acpi by its own
> terminology, disregarding the legacy convention.

Yes, systemd will happily break existing ACPI PM setups without any
warning.

The systemd point of view is that any breakage is caused by other
packages failing to detect that systemd is installed.  Their
interpretation of "not breaking unrelated software" is that any software
they break should detect that systemd is present and disable itself.

This systemd breakage is intentional, and any errors you experience is
entirely acpi-support's fault if you have configured it in such a way
that the disabling logic fails.

See https://bugs.debian.org/768025


> if nothing else helps, replace systemd with systemd-shim emulation
> (maybe also switching back to sysvinit).

This won't help.  systemd-shim needs systemd to provide
e.g. systemd-logind and that's where the breakage is.  You can disable
the systemd interference in this case by setting

 HandlePowerKey=ignore
 HandleSuspendKey=ignore
 HandleHibernateKey=ignore
 HandleLidSwitch=ignore

in /etc/systemd/logind.conf

BTW, I have given up reporting systemd bugs.  What's the point?  The
Debian maintainers have inherited the upstream point-of-view: "If
something broke when you installed systemd, then that is someone else's
fault for not adapting properly to systemd". And "broken by design is a
feature".


Bjørn


-- 
To UNSUBSCRIBE, email to debian-laptop-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: https://lists.debian.org/87388dz4t8@nemi.mork.no



Re: Intel Corporation Wireless 7260 (rev bb) and ilwifi on debian jessie

2015-01-21 Thread Bjørn Mork
"maiky.lambo...@runbox.no"  writes:

> Hi,
> I have just installed Debian Jessie in my new ultra-book that have Intel
> Corporation Wireless 7260 (rev bb).
>
> As I can read here
> http://forums.debian.net/viewtopic.php?f=7&t=111840
>
> It has open-source driver that are included in Linux Kernel 3.10 and
> Above. I'm running 3.16, but I can't use wifi.

Did you install firmware-iwlwifi from non-free?  If you did and still
have problems, then you should report a bug against the kernel.  This
will ensure that the necessary information is collected and the problem
is properly tracked: reportbug /boot/vmlinuz-`uname -r`


Bjørn


--
To UNSUBSCRIBE, email to debian-laptop-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: https://lists.debian.org/877fwgs82m@nemi.mork.no



Re: Intel Corporation Wireless 7260 (rev bb) and ilwifi on debian jessie

2015-01-21 Thread Bjørn Mork
"maiky.lambo...@runbox.no"  writes:
> On 21/01/15 12:10, Bjørn Mork wrote:
>
>> Did you install firmware-iwlwifi from non-free? 
>
> No, I need it?
> Does this card have opensource driver?
>
> Probably I'm wrong but this card should have opensource driver.
>
>
> lspci -vs 02:00.0
> 02:00.0 Network controller: Intel Corporation Wireless 7260 (rev bb)
>   Subsystem: Intel Corporation Dual Band Wireless-AC 7260
>   Flags: fast devsel, IRQ 19
>   Memory at f780 (64-bit, non-prefetchable) [size=8K]
>   Capabilities: [c8] Power Management version 3
>   Capabilities: [d0] MSI: Enable- Count=1/1 Maskable- 64bit+
>   Capabilities: [40] Express Endpoint, MSI 00
>   Capabilities: [100] Advanced Error Reporting
>   Capabilities: [140] Device Serial Number e8-b1-fc-ff-ff-7b-f0-8e
>   Capabilities: [14c] Latency Tolerance Reporting
>   Capabilities: [154] Vendor Specific Information: ID=cafe Rev=1  Len=014 
> 
>
> lsmod | grep iw
>
> iwlwifi96547  0
> cfg80211  405538  1 iwlwifi
>
> My kernel is 3.16.0-4-amd64
>
> http://www.intel.com/support/wireless/wlan/sb/CS-034398.htm
>
> "Driver development is done in the open source Linux community. [...]
> Development support is only available through the open source community
> mailing lists. "
>
>
> Intel® Wireless 7260 (3.10) is listed on
> http://wireless.kernel.org/en/users/Drivers/iwlwifi
>
> I'd like to use only FOSS so if I need proprietary driver, I'll change
> my wireless card.
>
> Please can you help me to understanding if is Open Drivers available?

The driver is open source, the firmware running on the WiFi card is
not. Like most WiFi modules out there.

If you really need open firmware too, then your choices are limited.
Here are some:
 https://wiki.debian.org/ath9k_htc/open_firmware
 http://www.ing.unibs.it/~openfwwf/index.php

I have no experience with any of these.

In any case, I doubt you have an ultra-book with an open firmware so I
don't see the problem with using closed source firmware for the WiFi
module. How about the firmware on your SSD?  Or the firmware controlling
the touchpad? Just accept the fact that a modern computer is made up of
a large number of separate systems, all having their own more or less
generic CPUs and proprietary firmware.  In theory it is of course
possible to open it all up. In practice it is probably easier to design
it all from scratch.

Good luck with that.



Bjørn


--
To UNSUBSCRIBE, email to debian-laptop-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: https://lists.debian.org/87twzkqq11@nemi.mork.no



Re: Huawei E3372

2015-02-26 Thread Bjørn Mork
Hannu Virtanen  writes:

> usb_modeswitch -H -v 0x12d1 -p 0x157d

Which usb_modeswitch version do you have?  This device is supported by
default since usb-modeswitch-data version 20140327-1, and should be
automatically switch when it is discovered.

In any case, the -H option won't work for this new device.  Use the -J
option if you want to switch it manually.  That's what the default
config will do:

 bjorn@nemi:~$ tar zxOvf /usr/share/usb_modeswitch/configPack.tar.gz 12d1:157d
 12d1:157d
 # Huawei E3331
 TargetVendor=0x12d1
 TargetProduct=0x14db
 HuaweiNewMode=1


But as I said:  Use the newest usb-modeswitch packages (from jessie).
You need software which is newer than your modem, and this variant is
pretty new.


Bjørn


--
To UNSUBSCRIBE, email to debian-laptop-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: https://lists.debian.org/877fv4yeuq@nemi.mork.no



Re: Lenovo Y520 and Debian?

2017-09-18 Thread Bjørn Mork
Bill Harris  writes:

> Besides, I think my concern comes ahead of  that: do I need to do anything
> special to prepare for Intel RST (fake RAID)?  If I knew that there were no
> problems ahead with that feature, then I could just start the installer,
> choosing to repartition for dual-boot or for only Linux, if I wished.

I have no experience with this feature, but this wiki page might help?:
https://wiki.debian.org/DebianInstaller/SataRaid



Bjørn



Re: Does not Debian support mobile broadband anymore?

2017-11-23 Thread Bjørn Mork
wg...@china.com writes:

> Hi, everyone,
>
> Since my Debian testing was upgraded on Oct 29, the mobile broadband in my 
> laptop could not be used. The mobile broadband is missing in the 
> network-manager UI, and wvdialconf can not configure the broadband either. 
> The message of wvdialconf is as below,
>
> **
> Editing `/etc/wvdial.conf'.
>
> Scanning your serial ports for a modem.
>
> ttyS0<*1>: ATQ0 V1 E1 -- failed with 2400 baud, next try: 9600 baud
> ttyS0<*1>: ATQ0 V1 E1 -- failed with 9600 baud, next try: 115200 baud
> ttyS0<*1>: ATQ0 V1 E1 -- and failed too at 115200, giving up.
> Modem Port Scan<*1>: S1   S2   S3   
> WvModem<*1>: Cannot get information for serial port.
> ttyUSB0<*1>: ATQ0 V1 E1 -- [01]
> ttyUSB0<*1>: failed with 2400 baud, next try: 9600 baud
> ttyUSB0<*1>: ATQ0 V1 E1 -- [01]
> ttyUSB0<*1>: failed with 9600 baud, next try: 9600 baud
> ttyUSB0<*1>: ATQ0 V1 E1 -- [01]
> ttyUSB0<*1>: and failed too at 115200, giving up.

ttyS0 is not your modem, and ttyUSB0 is either the EM7455 DIAG port or
firmware upgrade port, depending on modem state.  So this result from
wvdialconf is expected.  Don't know the first thin about wvdial...

Please provide some useful info instead:

lsusb -v
  will tell you whether the modem is detected and has booted properly, and
  also which mode it is configured for.

mmcli -L
  will show you a list of modems detected by modemmanger

mmcli -m X, where X is an index from the above list
  will show you more details on the specific modem


Further debug steps depend on the results of these commands.  You might
want to look at the generic ModemManager debug steps:
https://www.freedesktop.org/wiki/Software/ModemManager/Debugging/



Bjørn



Re: Does not Debian support mobile broadband anymore?

2017-11-23 Thread Bjørn Mork
wg...@china.com writes:

> I use dmesg to view the system message, and get these informations as below,
>
> [ 1535.372130] usb 1-6: new high-speed USB device number 8 using xhci_hcd
> [ 1535.378889] thinkpad_acpi: unknown possible thermal alarm or keyboard 
> event received
> [ 1535.378893] thinkpad_acpi: unhandled HKEY event 0x60b0
> [ 1535.378894] thinkpad_acpi: please report the conditions when this event 
> happened to ibm-acpi-de...@lists.sourceforge.net
> [ 1535.513304] usb 1-6: New USB device found, idVendor=1199, idProduct=9078
> [ 1535.513308] usb 1-6: New USB device strings: Mfr=1, Product=2, 
> SerialNumber=3
> [ 1535.513310] usb 1-6: Product: Sierra Wireless EM7455 Qualcomm
> [ 1535.513312] usb 1-6: Manufacturer: Sierra Wireless, Incorporated
> [ 1535.513313] usb 1-6: SerialNumber: LF72567821041020
> [ 1535.513996] qcserial 1-6:1.0: Qualcomm USB modem converter detected
> [ 1535.514212] usb 1-6: Qualcomm USB modem converter now attached to ttyUSB0
> [ 1535.515015] usb 1-6: USB disconnect, device number 8
> [ 1535.515330] qcserial ttyUSB0: Qualcomm USB modem converter now 
> disconnected from ttyUSB0
> [ 1535.515356] qcserial 1-6:1.0: device disconnected
> [ 1536.014626] thinkpad_acpi: unknown possible thermal alarm or keyboard 
> event received
> [ 1536.014628] thinkpad_acpi: unhandled HKEY event 0x60b1
> [ 1536.014629] thinkpad_acpi: please report the conditions when this event 
> happened to ibm-acpi-de...@lists.sourceforge.net
> [ 1536.524163] usb 1-6: new high-speed USB device number 9 using xhci_hcd
> [ 1536.665054] usb 1-6: config 1 interface 0 altsetting 0 bulk endpoint 0x1 
> has invalid maxpacket 64
> [ 1536.665058] usb 1-6: config 1 interface 0 altsetting 0 bulk endpoint 0x81 
> has invalid maxpacket 64
> [ 1536.665988] usb 1-6: New USB device found, idVendor=1199, idProduct=9078
> [ 1536.665992] usb 1-6: New USB device strings: Mfr=1, Product=2, 
> SerialNumber=3
> [ 1536.665994] usb 1-6: Product: Sierra Wireless EM7455 Qualcomm
> [ 1536.665996] usb 1-6: Manufacturer: Sierra Wireless, Incorporated
> [ 1536.665998] usb 1-6: SerialNumber: LF72567821041020
> [ 1536.666822] usb 1-6: USB disconnect, device number 9
> [ 1544.686163] thinkpad_acpi: unknown possible thermal alarm or keyboard 
> event received
> [ 1544.686167] thinkpad_acpi: unhandled HKEY event 0x60b0
> [ 1544.686168] thinkpad_acpi: please report the conditions when this event 
> happened to ibm-acpi-de...@lists.sourceforge.net
> [ 1553.785361] usb 1-6: new high-speed USB device number 11 using xhci_hcd
> [ 1553.926371] usb 1-6: New USB device found, idVendor=1199, idProduct=9078
> [ 1553.926390] usb 1-6: New USB device strings: Mfr=1, Product=2, 
> SerialNumber=3
> [ 1553.926392] usb 1-6: Product: Sierra Wireless EM7455 Qualcomm
> [ 1553.926394] usb 1-6: Manufacturer: Sierra Wireless, Incorporated
> [ 1553.926395] usb 1-6: SerialNumber: LF72567821041020
> [ 1553.926986] qcserial 1-6:1.0: Qualcomm USB modem converter detected
> [ 1553.927112] usb 1-6: Qualcomm USB modem converter now attached to ttyUSB0
> [ 1553.928024] usb 1-6: USB disconnect, device number 11
> [ 1553.928258] qcserial ttyUSB0: Qualcomm USB modem converter now 
> disconnected from ttyUSB0
> [ 1553.928275] qcserial 1-6:1.0: device disconnected
> [ 1554.937425] usb 1-6: new high-speed USB device number 12 using xhci_hcd
> [ 1555.078351] usb 1-6: config 1 interface 0 altsetting 0 bulk endpoint 0x1 
> has invalid maxpacket 64
> [ 1555.078354] usb 1-6: config 1 interface 0 altsetting 0 bulk endpoint 0x81 
> has invalid maxpacket 64
> [ 1555.079241] usb 1-6: New USB device found, idVendor=1199, idProduct=9078
> [ 1555.079245] usb 1-6: New USB device strings: Mfr=1, Product=2, 
> SerialNumber=3
> [ 1555.079247] usb 1-6: Product: Sierra Wireless EM7455 Qualcomm
> [ 1555.079249] usb 1-6: Manufacturer: Sierra Wireless, Incorporated
> [ 1555.079250] usb 1-6: SerialNumber: LF72567821041020
> [ 1555.080269] usb 1-6: USB disconnect, device number 12
>
>
> That is to say, the device Sierra Wireless EM7455 is connected and 
> disconnected frequently. It should be a problem of something. But I do not 
> known what it is. This device worked fine before Oct 29.

This is the problem, but I don't it is related to Debian versions in any
way.

The modem seems to be constantly resetting.  I expect it eventually
settles when the (modem) bootloader failsafe mode kicks in.  But it will
then probably be in a debug mode.

Notice that the device ID is 1199:9078 all the way.  This is the
bootloader ID.  The application ID is 1199:9079.  If you have older logs
from when the modem worked, then I am pretty sure you'll see that ID
instead.

I'm afraid there is little which can be done about this on an OS level,
unless the root cause is some platform (Lenovo) specific issue which
triggers the modem boot failure.  My advice would be to test this with
another OS, if possible, and then contact Lenovo support if it fails
there as well.



Bjørn



Re: Does not Debian support mobile broadband anymore?

2017-11-23 Thread Bjørn Mork
Yes, this is expected.  As I said: 1199:9078 is a booloader mode.  This mode is
normally only visible in two situations:

 1) when upgrading firmware
 2) when the firmware fails to boot

Your case is numer 2. The booloader will try to boot the modem firmware
a few times (seen as multiple connect+disconnect events) and then enter
a failsafe/debug mode.  There is only a single USB interface available
in this mode, as you can see from your lsusb output.  This is a serial
function which is handled by the same driver that will handle the normal
modem serial function, making it appear to the system as typically
/dev/ttyUSB0.  But there is *no modem* related function there.  Only a
Qualcomm or Sierra Wireless bootloader debug function, speaking the
SAHARA protocol.

As I said: Please verify that the modem works on any other OS if you
can.  Downgrade your Debian install if you believe that will help. If it
doesn't, then you should assume that the firmware or NVRAM on this modem
is damaged. This is most likely a warranty repair since this is a rather
new laptop.  You should therefore contact Lenovo support.


Bjørn

wg...@china.com writes:

> Sometimes, the device Sierra Wireless EM7455 is connected success, and run 
> lsusb, mmcli -L, their output is below. No any modem is found.
>
> lsusb -v
> 
> Bus 001 Device 009: ID 1199:9078 Sierra Wireless, Inc. 
> Couldn't open device, some information will be missing
> Device Descriptor:
>   bLength18
>   bDescriptorType 1
>   bcdUSB   2.00
>   bDeviceClass0 (Defined at Interface level)
>   bDeviceSubClass 0 
>   bDeviceProtocol 0 
>   bMaxPacketSize064
>   idVendor   0x1199 Sierra Wireless, Inc.
>   idProduct  0x9078 
>   bcdDevice0.00
>   iManufacturer   1 
>   iProduct2 
>   iSerial 3 
>   bNumConfigurations  1
>   Configuration Descriptor:
> bLength 9
> bDescriptorType 2
> wTotalLength   32
> bNumInterfaces  1
> bConfigurationValue 1
> iConfiguration  0 
> bmAttributes 0x80
>   (Bus Powered)
> MaxPower2mA
> Interface Descriptor:
>   bLength 9
>   bDescriptorType 4
>   bInterfaceNumber0
>   bAlternateSetting   0
>   bNumEndpoints   2
>   bInterfaceClass   255 Vendor Specific Class
>   bInterfaceSubClass255 Vendor Specific Subclass
>   bInterfaceProtocol255 Vendor Specific Protocol
>   iInterface  0 
>   Endpoint Descriptor:
> bLength 7
> bDescriptorType 5
> bEndpointAddress 0x81  EP 1 IN
> bmAttributes2
>   Transfer TypeBulk
>   Synch Type   None
>   Usage Type   Data
> wMaxPacketSize 0x0200  1x 512 bytes
> bInterval   0
>   Endpoint Descriptor:
> bLength 7
> bDescriptorType 5
> bEndpointAddress 0x01  EP 1 OUT
> bmAttributes2
>   Transfer TypeBulk
>   Synch Type   None
>   Usage Type   Data
> wMaxPacketSize 0x0200  1x 512 bytes
> bInterval   0
> *****
>
> mmcli -L
> 
> No modems were found
> 
>
>
>> -原始邮件-
>> 发件人: "Bjørn Mork" 
>> 发送时间: 2017-11-23 16:38:25 (星期四)
>> 收件人: wg...@china.com
>> 抄送: debian-laptop@lists.debian.org
>> 主题: Re: Does not Debian support mobile broadband anymore?
>> 
>> wg...@china.com writes:
>> 
>> > I use dmesg to view the system message, and get these informations as 
>> > below,
>> >
>> > [ 1535.372130] usb 1-6: new high-speed USB device number 8 using xhci_hcd
>> > [ 1535.378889] thinkpad_acpi: unknown possible thermal alarm or keyboard 
>> > event received
>> > [ 1535.378893] thinkpad_acpi: unhandled HKEY event 0x60b0
>> > [ 1535.378894] thinkpad_acpi: please report the conditions when this event 
>> > happened to ibm-acpi-de...@lists.sourceforge.net
>> > [ 1535.513304] usb 1-6: New USB device found, idVendor=1199, idProduct=9078
>> > [ 1535.513308] usb 1-6: New USB device strings: Mfr=1, Product=2, 
>> > SerialNumber=3
>> > [ 1535.51331

Re: ThinkPad T60p X11 driver problems

2018-05-14 Thread Bjørn Mork
Bob Proulx  writes:

> IBM ThinkPad T60p
> Intel T2600 cpu (32-bits)
> AMD/ATI RV530/M56 GL Mobility FireGL V5200 graphics
>
> Fresh install of Debian Stretch 9.  X11 starts in software rendering
> mode.  The same laptop with Ubuntu 16.04 runs with hardware rendering.
>
> Any hints on how what is needed for hardware rendering with this
> hardware combination in Debian?  I am sure this hardware used to be
> fully supported and therefore hardware support must have been dropped
> at some point.

Does

 dmesg | grep radeon

say anything about firmware?  Do you have the firmware-amd-graphics
package installed (from non-free)?



Bjørn



Re: Discussions about Partitioning

2018-10-28 Thread Bjørn Mork
Leslie S Satenstein  writes:

> BTW, swap should be completely _unused_ during normal computer operation 
> if you don't want a snail slow machine.
> Consider to install a swap file instead of a swap partition for the rare 
> cases where you run out of physical  memory.
>
> The only situation you really want a _large_ swap is IMHO when 
> developing kernel programs to get access to the whole messy system via a 
> crash dump.

You might want enough swap to support hibernation.  Even if you don't
use it normally, it can be quite useful for the situations where the
battery runs out completely.

See https://wiki.debian.org/Hibernation and
https://wiki.debian.org/SystemdSuspendSedation for more details


Bjørn



Re: Failed to detect SSD when installing Bullseye

2021-08-21 Thread Bjørn Mork
> On Sat, Aug 21, 2021 at 7:42 AM Bjørn Mork  wrote:
>
>> try booting with intel_iommu=off on the kernel command line
>
> It works now, thanks for your help.

Great!  Glad it could be resolved as easily as that.

> Is there a known bug or something?

Probably a firmware bug. I don't know.  Such issues are pretty common,
and disabling the IOMMU is the first thing you should try.  Sometimes
it just doesn't play well with some other feature.  If you don't need
it then you might as well just disable it.

My Thinkpad fails to suspend if I enable both IOMMU and TPM 2.0.  One of
them is OK, but not both.  Go figure.  This is https://bugs.debian.org/949020

For some background:
https://www.kernel.org/doc/html/latest/x86/intel-iommu.html

There are also a number of other options than "off" you could try if you
want to play with it:
https://www.kernel.org/doc/html/v4.14/admin-guide/kernel-parameters.html

Note that the bug has probably always been there in your PC firmware.
It showed up now because Debian changed the default from "off" to "on".



Bjørn



Allow Microsoft 3rd Party UEFI CA

2022-10-22 Thread Bjørn Mork
Just had an interesting experience installing Debian bullseye on a
Lenovo Thinkpad P14s Gen 3.

I tried to PXE boot the Debian installer and could see in the tftp
server log that the Thinkpad loaded the shim, but nothing more.  It just
jumped back to the PXE boot menu.

After several failed attempts, I was ready to give up and just disable
secure boot.  So I entered the BIOS settings.  But in the Secure Boot
page there I noticed an unknown (to me) new setting, which was disabled
by default:

  "Allow Microsoft 3rd Party UEFI CA"

I enabled it and tried PXE booting the Debian install again.  And voilà
- the shim ran and loaded grub etc as it should.

So to anyone struggling with secure boot: Look for this setting or
something similar in the BIOS. They've obviously found a new way to
break secure boot by default.


Bjørn