date:20171109

[Kernel-packages] [Bug 1723986] Re: Touchpad and TrackPoint Does Not Work on Lenovo X1C6 and X280

2017-11-09 Thread AaronMa

@binli, there's another ops to do: remove i2c_801 from modules
blacklist, please try again.

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1723986

Title:
  Touchpad and TrackPoint Does Not Work on Lenovo X1C6 and X280

Status in HWE Next:
  Fix Committed
Status in linux package in Ubuntu:
  Fix Committed
Status in linux source package in Artful:
  Fix Committed

Bug description:
  Synaptics devices on Lenovo X1C6 and X280 can not work via PS/2 mode, it show:
  [   11.366996] psmouse serio1: synaptics: Touchpad model: 1, fw: 9.16, id: 
0x1e2a1, caps: 0xf001a3/0x940300/0x12e800/0x50, board id: 3382, fw id: 
2629663
  [   11.367002] psmouse serio1: synaptics: serio: Synaptics pass-through port 
at isa0060/serio1/input0
  [   11.781876] psmouse serio2: Failed to reset mouse on synaptics-pt/serio0
  [   30.390508] psmouse serio2: Failed to deactivate mouse on 
synaptics-pt/serio0
  [   30.862260] psmouse serio2: Failed to enable mouse on synaptics-pt/serio0

  Enable SMBus mode on these devices will make them work.

  Cherrypick 3 patches from patchwork as sauce patches on Ubuntu Artful
  kernel.

To manage notifications about this bug go to:
https://bugs.launchpad.net/hwe-next/+bug/1723986/+subscriptions

-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp

Re: [Kernel-packages] [Bug 1729128] Re: Raspberry Pi 3 microSD support missing from the installer

2017-11-09 Thread William Grant

On 06/11/17 23:03, Paolo Pisati wrote:
> Your suggestion makes sense, but can you give me the exact steps on how
> to test it afterward?
>
> I gave a quick glance at u-boot master, but i couldn't find any 'uefi'
> or 'rpi3-uefi' target in configs. Or shall i just build the rpi3 target
> and then pass a UEFI fw as a payload? And where do i get the UEFI fw
> from? Instructions on how to setup the system are welcome.

It was lot easier to get working than I had expected. There are a couple
of gotchas left, but it works great (and is the cheapest way I know to
run arm64...) once you get through them... I intend to look at fixing
most of these for bionic.

Prepare an MBR-partitioned microSD card with a FAT16 or FAT32 partition
at the start to be used for firmware and as the UEFI ESP; 100MB is
ample. The only gotcha here is that the firmware doesn't seem to know
about partition type 0xEF (ESP), but u-boot will happily load GRUB from
a 0xE (FAT16 LBA) that the platform firmware is happy with.

Then give it firmware:

git clone git://git.denx.de/u-boot.git
pushd u-boot
make rpi_3_defconfig
make CROSS_COMPILE=aarch64-linux-gnu-
# kernel8.img is important -- the 8 forces start.elf to do aarch64.
cp u-boot.bin /PATH/TO/MICROSD/FAT16_OR_32/PART/kernel8.img
popd

git clone --depth 1 gh:raspberrypi/firmware raspberrypi-firmware
pushd raspberrypi-firmware
cp bootcode.bin start.elf fixup.dat /PATH/TO/MICROSD/FAT16_OR_32_PART/
popd

None of the dtbs are required.

Insert the microSD card into the RPi3. Also insert a USB mass storage
device with
http://ports.ubuntu.com/ubuntu-ports/dists/artful/main/installer-arm64/current/images/netboot/mini.iso
written to it.

Boot the RPi3 with Ethernet, HDMI and a USB keyboard. After a few
seconds of u-boot, a hideous looking, bright red, awfully corrupt, but
still readable GRUB 2 prompt will appear. d-i will automatically start,
with no visual issues.

Switch to another VT and grab bcm2835.ko for the relevant kernel. For
artful's 4.13.0-16.19:

wget --no-check-certificate https://williamgrant.id.au/f/1/2017/bcm2835.ko
insmod bcm2835.ko

Then switch back to tty0 and proceed with the install. The partitioner
will see the internal microSD, but care is required with partitioning:
if you recreate the partition table it will default to GPT, which the
RPi3 firmware can't read, and if you recreate the boot partition it'll
end up with no firmware and type 0xEF (both of which are fixable
afterwards from another machine). The easiest way is to just set the
existing boot partition as an ESP in the installer, which won't change
the type. Then create a partition for / etc. as, and proceed with the
install as normal.

Everything will now work fine, except nothing will be visible on HDMI
unless GRUB initialises the EFI console, which you can force after the
install by commenting out GRUB_HIDDEN_TIMEOUT in /etc/default/grub and
running update-grub, and you might also need to disable plymouth be
removing "splash".

I haven't tested GPU bits, but the only hardware I found that didn't
work was the WiFi chip, since linux-firmware is missing
brcmfmac43430-sdio.txt (it just has the .bin). But I grabbed a new
brcmfmac43430-sdio.{txt,bin}, and it all seems rock solid on -generic now.

--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1729128

Title:
Raspberry Pi 3 microSD support missing from the installer

Status in linux package in Ubuntu:
Confirmed
Status in linux source package in Bionic:
Confirmed

Bug description:
Please add bcm2835 to block-modules on arm64 (and armhf?).

artful's arm64 d-i mini.iso works fine on Raspberry Pi 3 when booting
with a UEFI-capable u-boot, except for one detail: mmc/host/bcm2835.ko
is missing from block-modules, so you can't install to microSD without
manually grabbing and loading the module.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1729128/+subscriptions

--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp

1 2 >

1 - 100 of 106 matches

Mail list logo