Could someone compile the following file for me? I'd do it myself, but, unfortunately, I don't have access to a computer, nor will I for a while (I'm touchpad only for now).
https://github.com/CyanogenMod/hp-kernel-tenderloin/blob/gingerbread/drivers/net/usb/mcs7830.c
The driver is for a USB-Ethernet adapter that I'm trying to get working on the Touchpad through ICS (cm9).
Thanks.
Is this for USB 3g dongles??
No, not for a 3G adapter, but for one that goes from USB to Ethernet cable.
jcsullins compiled it for me, by the way, so I no longer need the driver (many thanks to him).
However, I can confirm that ICS on CM9 recognized it without problems as eth0 and once I ran dhcpd and assigned a DNS server, I had no problems connecting to the internet. So feel free to add a driver for your own adapter if you have one.
So to review:
-copy driver (to /system/lib/modules)
-insert module ("insmod /system/lib/modules/*yourdriver*.ko")
-get an IP address (manually, or "/system/bin/dhcpd eth0")
-add DNS (setprop net.dns1 *yourDNSserver*)
A couple caveats, I've noticed.
1) It doesn't play nice with wifi. I sort of expected this, but bringing up wlan0 and eth0 at the same time crashes the tablet.
2) Not all apps recognize the internet connection. This is a bit frustrating since most do (including the Browser), but not all.
potissimus said:
No, not for a 3G adapter, but for one that goes from USB to Ethernet cable.
jcsullins compiled it for me, by the way, so I no longer need the driver (many thanks to him).
However, I can confirm that ICS on CM9 recognized it without problems as eth0 and once I ran dhcpd and assigned a DNS server, I had no problems connecting to the internet. So feel free to add a driver for your own adapter if you have one.
So to review:
-copy driver (to /system/lib/modules)
-insert module ("insmod /system/lib/modules/*yourdriver*.ko")
-get an IP address (manually, or "/system/bin/dhcpd eth0")
-add DNS (setprop net.dns1 *yourDNSserver*)
A couple caveats, I've noticed.
1) It doesn't play nice with wifi. I sort of expected this, but bringing up wlan0 and eth0 at the same time crashes the tablet.
2) Not all apps recognize the internet connection. This is a bit frustrating since most do (including the Browser), but not all.
Click to expand...
Click to collapse
Thanks for the extra info--but a link the the driver jcsullins provided you would be a lot more helpful! Any chance you can post it somewhere for us?
all4adriver said:
Thanks for the extra info--but a link the the driver jcsullins provided you would be a lot more helpful! Any chance you can post it somewhere for us?
Click to expand...
Click to collapse
*bump*
is there a USB ethernet adapter that will work on our touchpads without a driver?
all4adriver said:
*bump*
is there a USB ethernet adapter that will work on our touchpads without a driver?
Click to expand...
Click to collapse
I figured out how to compile drivers manually myself shortly after my posts in this thread. I havent used my build environment in a while though, should still be able to check out what (if any) drivers are built into the kernel by default. Do you already have an adapter?
ba114 said:
I figured out how to compile drivers manually myself shortly after my posts in this thread. I havent used my build environment in a while though, should still be able to check out what (if any) drivers are built into the kernel by default. Do you already have an adapter?
Click to expand...
Click to collapse
OMG thank you for responding! No, I don't have an adapter yet--was waiting to find out which one works and I'll buy that. I'm open to suggestions. Thank you!
You are my shining beacon of hope ba114! Have you had a chance to see what drivers might exist in the kernel?
I read elsewhere that the cyanogenmod for the asus transformer contains a driver compatible with Asix AX88772. That chipset is what this cheapo adapter (OMG, no links for noobs!) uses. I have half a mind to buy one just to see, but it would help immensely if someone could confirm that jcsullins cm9 or cm10 for the touchpad also has support for this chipset baked in...
Hopefully giving you something to work with will make this less of a "needle in the haystack"...
Thanks!
really wish I could post links, as jscullins has posted the driver!
hxxp://goo.im/devs/jcsullins/cmtouchpad/misc/mcs7830.ko
all4adriver said:
really wish I could post links, as jscullins has posted the driver!
hxxp://goo.im/devs/jcsullins/cmtouchpad/misc/mcs7830.ko
Click to expand...
Click to collapse
http://goo.im/devs/jcsullins/cmtouchpad/misc/mcs7830.ko
could use some help
OK, finally got my OTG cable and USB ethernet. Let's do this!
Tried to follow these instructions:
So to review:
-copy driver (to /system/lib/modules)
-insert module ("insmod /system/lib/modules/*yourdriver*.ko")
-get an IP address (manually, or "/system/bin/dhcpd eth0")
-add DNS (setprop net.dns1 *yourDNSserver*)
Had to troubleshoot why my Touchpad wasn't being seen as a USB mass storage device. DONE. I'm feeling like a boss.
Windows Explorer didn't see the main system--just the "SD Card". What ever--not big deal. I copied the driver over to the SD Card. Downloaded Astro File Manager to copy the file to /system/lib/modules. Nope. Denied.
No problem! Dropped to terminal and enabled super user. Astro is still a no go. No worries!! I'm a big boy--I'll do this in terminal! Taught myself enough command line jargon to navigate to the file, and copy it to the intended directory. NOPE. Directory is read only.
OK, so I navigate there and try to chmod the directory with u+w. "Bad mode". Research that to learn I have to use the numbers. So I try that (775) and now it tells me it is a read-only file system.
sigh
It might not seem like it, but I'm trying. I really am.
Can someone tell me how to get past step one of this process? Please? What on earth am I doing wrong?
I recently had to do some wizardry on my phone to get openvpn to co-operate, and I suspect that would work here but I don't understand the commands, and fear I'd end up screwing something up.
This was the command:
mount -o rw,remount -t yaffs2 /dev/block/mtdblock3 /system
I'm guessing I need to unmount the system so I can work on it and copy the file into that directory? Is that the case? Would the command line be the same, or different?
Anyone else get this to work now that the driver has been posted publicly?
Thanks!!!!
To help those who come after me:
Grab ES File Explorer. It includes a Root Explorer that lets you mount the file system as writable. The "copy to" command claimed to work but did not copy the file. Copy the driver, then manually navigate to /system/lib/modules and paste. Voila.
-insert module ("insmod /system/lib/modules/*yourdriver*.ko")
Click to expand...
Click to collapse
this appeared to work
-get an IP address (manually, or "/system/bin/dhcpd eth0")
Click to expand...
Click to collapse
this took me a long time to figure out. as far as I can tell, the only "directions" noobs like me have to follow contain typos. the command should read dhcpcd eth0
HOWEVER, what I get instead is eth0: interface not found or invalid
a little help here? Does the mcs7830.ko driver work with the Asix AX88772 chipset?
Stupid question--should I be expecting the touchpad to power the USB ethernet adapter via the OTG cable, or do I require a "Y" cable to supply power? Is that why I'm getting:
eth0: interface not found or invalid
Click to expand...
Click to collapse
all4adriver said:
Stupid question--should I be expecting the touchpad to power the USB ethernet adapter via the OTG cable, or do I require a "Y" cable to supply power? Is that why I'm getting:
Click to expand...
Click to collapse
I would assume so. Every HP Touchpad tutorial that I've see that mentions an OTG cable also mentions it needing to be powered.
This guide is intend to help you with "installing" Ubuntu 14.04 (12.04 also works) on the Amazon Fire TV 2 after @rbox recovery has been setup. Only headless mode is possible, similar to Ubuntu Server, but it still makes a nice little ARMv8 development box. Starting X.org or running systemd based Linux distributions will likely never be possible due to features missing from the Amazon kernel. Creative use of the framebuffer is possible if desired, maybe eventually a terminal emulator could be started. As long as you don't mount and modify mmcblk0pX there should be no possible way to mess up Android or brick the device. It's 100% reversible by just removing the SD card. You accept all responsibility for what you do with this work should something go wrong and the device becomes inoperable. With disclaimers and precursor knowledge out of the way let's get started.
To follow this guide you will need:
A micro SD card (2 GB+ recommended)
A Linux system
To login into Ubuntu you will need either:
A 1.8 V TTY USB serial device connected to the UART
A pair of USB serial devices and a null modem cable
I actually used a pair of Xbee's for testing the ttyUSB0 stuff, so hence a pair of FTDI chips would also work.
Preparing the SD Card
To get started you need to first partition the micro SD card:
Type = MBR
Part 1 = 100 MB, Fat32 (vfat)
Part 2 = Remainder, Ext4
Extract the attached zip file to the root of the first partition (extracted filename must be "ramdisk-recovery.cpio.lzma"). This is an alternative initramfs that simply uses busybox to clean up from the partial Android boot and prepare the filesystem for regular Linux. Extract an Ubuntu core root filesystem archive, ubuntu-core-14.04.4-core-arm64.tar.gz, to the root of the second partition as the root user (to preserve ownership/permissions). Make sure you sync or eject the device when done with this work so the data gets flushed to the SD card.
Now we need to make a few changes to the root filesystem to avoid usability issues and allow logins.
Replace /etc/fstab with the following contents to correct some mount options. This "disables" SELinux which fixes dpkg errors and some other login annoyances.
Code:
/dev/mmcblk1p2 / ext4 defaults,relatime 0 0
selinuxfs /sys/fs/selinux selinuxfs ro,relatime 0 0
Replace /etc/init/console.conf with the following contents to allow logins from the UART. Once the root password has been set (root is disabled by default) you can remove "-a root" if desired.
Code:
# console - getty
#
# This service maintains a getty on console from the point the system is
# started until it is shut down again.
start on stopped rc RUNLEVEL=[2345]
stop on runlevel [!2345]
respawn
exec /sbin/getty -s -a root console
Create /etc/init/ttyUSB0.conf with the following contents to allow logins from an attached USB serial device. This should help people who don't want to take apart their device to solder wires onto the UART test points. SSH would of course be an alternative but it's not installed by default in Ubuntu core and this guide is about the building blocks not providing pre-made images (yet). Since udev doesn't work due to devtmpfs not being enabled in the kernel you will need to attach the USB serial device before booting for this to work. As before you can remove "-a root" later if desired once the root password is set. Also you should change the baud rate if needed.
Code:
start on (tty-device-added ttyUSB0)
stop on (runlevel [!2345] or tty-device-removed ttyUSB0)
respawn
exec /sbin/getty -L -a root 115200 ttyUSB0 vt102
Preparing the Fire TV
Until the search order for the initramfs file is changed by @rbox you will need to rename the initramfs on the system partition so it will continue to search for one on the SD card or USB stick. You need to connect to the device using adb either over USB or the network to execute the following commands.
Code:
adb$ su
adb# mount -o remount,rw /system
adb# mv /system/recovery/ramdisk-recovery.cpio.lzma /system/recovery/ramdisk-recovery.cpio.lzma.bak
adb# mount -o remount,ro /system
Right now this prevents "su" from working, which should be fixed by @rbox in due time. To get "su" working again you should extract the original recovery initramfs file to a USB stick and boot the device with that USB stick inserted instead of the previously created SD card. Then to restore "su" you can repeat the above steps just swapping the order of the files in the "mv" command.
Booting Ubuntu
After connecting your serial device of choice simply insert the SD card and power on the device. It's that easy! With luck you should get a shell prompt that is already logged in as root. It's a good idea to set the root password before going much further. The device isn't too useful without networking, so you can install more packages. To solve that connect an ethernet cable (since it's simpler) and type "dhclient eth0" to get online. At this point you can install openssh-server using apt-get or do anything else you'd normally do on an Ubuntu VM or headless Ubuntu system. I'm interested in hearing what people plan to do with a more-or-less high-end ARM development system.
Tips and Tricks
NOTE: These changes, unless otherwise noted, are performed while logged into the target Ubuntu system.
Setting the Hostname
You can change the hostname using the following command:
Code:
echo sloane > /etc/hostname
You should also create a simple /etc/hosts file that matches the chosen hostname.
Code:
127.0.0.1 localhost
127.0.1.1 sloane
Enable Ethernet at Boot
Create the file /etc/network/interfaces.d/eth0 with the following contents:
Code:
auto eth0
iface eth0 inet dhcp
Allow Users Network Access
Since we are stuck running an Android kernel you need to create the following group and add users who need network access (such as ping) to this special group.
Code:
groupadd -g 3003 aid_inet
usermod -G aid_inet -a root
usermod -G aid_inet -a <username>
Removing Failed Services
There are a few services that fail to start due to hardware limitations. We should just prevent them from starting in the first place. We have no VT support enabled in the kernel (boo) so we can just remove the ttyX login prompt services. Also the console setup doesn't work since our console is a serial device not a virtual terminal or other "graphical" type terminal emulator.
Code:
rm /etc/init/tty?.conf
echo manual > /etc/init/console-font.override
echo manual > /etc/init/console-setup.override
Fix /dev Hotplug
As stated before udev doesn't work due to missing kernel features. The busybox applet mdev is a simple replacement for most users. After installing the "busybox-static" package run the following command:
Code:
ln -s /bin/busybox /sbin/mdev
Now add the following line to /etc/rc.local before "exit 0".
Code:
echo /sbin/mdev > /proc/sys/kernel/hotplug
Pre-installing SSH
See: http://forum.xda-developers.com/showpost.php?p=65595013&postcount=13 (thanks @segfault1978)
Thanks a lot, that was exactly the thing I was searching for. Since before today the Raspi3 came out, this box is the cheapest ARMv8 development machine available. With your instruction I was able to login via SSH and install all required software for my development environment. No GUI needed for that, I'm doing all remotely via SSH. Again, thank you!
segfault1978 said:
Thanks a lot, that was exactly the thing I was searching for. Since before today the Raspi3 came out, this box is the cheapest ARMv8 development machine available. With your instruction I was able to login via SSH and install all required software for my development environment. No GUI needed for that, I'm doing all remotely via SSH. Again, thank you!
Click to expand...
Click to collapse
Awesome to hear that it worked for you. Just curious if you went the USB serial route or soldered to the UART pins.
There is also the Dragonboard 410c which is a quad core A53 but has a bit more than the raspberry pi. The price is higher though but it has been out probably a year or so. Just FYI. The raspberry pi 3 is a good deal.
zeroepoch said:
Awesome to hear that it worked for you. Just curious if you went the USB serial route or soldered to the UART pins.
Click to expand...
Click to collapse
None of these methods (since I was in my weekend and all cables and adapters reside in my office)
I placed all .deb-files for openssh-server including all requiremens onto the microSD card, and placed a call "dpkg -i /*.deb" with logging options in /etc/rc.local. I also configured network by mounting the sd card, editing /etc/network/interfaces, and last changed /etc/shadow to have a valid root account for login. It took my some try-and-error loops, but finally it worked as expected. Call me crazy, but I succeeded without any hardware.
---------- Post added at 09:09 PM ---------- Previous post was at 09:03 PM ----------
zeroepoch said:
There is also the Dragonboard 410c which is a quad core A53 but has a bit more than the raspberry pi. The price is higher though but it has been out probably a year or so. Just FYI. The raspberry pi 3 is a good deal.
Click to expand...
Click to collapse
Thank you for the hint, I'll have a look for the availability of this board in germany.
I'm facing a memory problem, resulting in a reboot of the device when all RAM is being used. My compile session takes more than 1.x GB of RAM for the quite complex compilation of all required packages. I can reproduce the situation where all memory is consumed and the device instantly reboots when hitting "no memory left" situation. Since "swapon" is not supported by the kernel (really?): is there any way to enable swap functionality, i.e. via a kernel module? How to overcome this situation where more memory is needed?
segfault1978 said:
None of these methods (since I was in my weekend and all cables and adapters reside in my office)
I placed all .deb-files for openssh-server including all requiremens onto the microSD card, and placed a call "dpkg -i /*.deb" with logging options in /etc/rc.local. I also configured network by mounting the sd card, editing /etc/network/interfaces, and last changed /etc/shadow to have a valid root account for login. It took my some try-and-error loops, but finally it worked as expected. Call me crazy, but I succeeded without any hardware.
Click to expand...
Click to collapse
That is pretty crazy, but since you knew the changes required it worked Not everyone I expected to have such experience. I figured someone might even try to do a qemu chroot or debbootstrap to preinstall openssh. Multiple ways to solve the same problem I guess.
segfault1978 said:
I'm facing a memory problem, resulting in a reboot of the device when all RAM is being used. My compile session takes more than 1.x GB of RAM for the quite complex compilation of all required packages. I can reproduce the situation where all memory is consumed and the device instantly reboots when hitting "no memory left" situation. Since "swapon" is not supported by the kernel (really?): is there any way to enable swap functionality, i.e. via a kernel module? How to overcome this situation where more memory is needed?
Click to expand...
Click to collapse
Looking at the default kernel config from the source code drop from Amazon I see:
Code:
# CONFIG_SWAP is not set
Swap can not be compiled as a module. Even if you chose to use a USB stick or something as the swap device It wouldn't work. Given that we can't change the kernel we can't try stuff like zram or zswap either. The only other suggestion I might have is if you're using "-j4" or something while compiling just remove that so it does a single threaded compile. I'm sure you already tried that. Beyond that you could look at using the Linaro AArch64 toolchain and cross compile. Since we're running Ubuntu you shouldn't need to worry about static binaries.
zeroepoch said:
Looking at the default kernel config from the source code drop from Amazon I see:
Code:
# CONFIG_SWAP is not set
Swap can not be compiled as a module. Even if you chose to use a USB stick or something as the swap device It wouldn't work. Given that we can't change the kernel we can't try stuff like zram or zswap either. The only other suggestion I might have is if you're using "-j4" or something while compiling just remove that so it does a single threaded compile. I'm sure you already tried that. Beyond that you could look at using the Linaro AArch64 toolchain and cross compile. Since we're running Ubuntu you shouldn't need to worry about static binaries.
Click to expand...
Click to collapse
Unfortunately, I'm not compiling with parallel processes (I'm compilig Icinga2 for arm64), I'm running
Code:
dpkg-buildpackage -us -uc
within the source package. One single cpp call consumes so much memory (which is crazy in my eyes, never seen such a big compiler process until today), so I'll investigate the option of cross compiling and afterwards creating the deb file outside of the machine.
Code:
cd /root/icinga2-2.4.3/obj-aarch64-linux-gnu/lib/base && /usr/bin/aarch64-linux-gnu-g++ -DI2_BASE_BUILD -Doverride="" -g -O2 -fstack-protector --param=ssp-buffer-size=4 -Wformat -Werror=format-security -D_FORTIFY_SOURCE=2 -g -pthread -std=c++11 -Wno-inconsistent-missing-override -fPIC -I/root/icinga2-2.4.3 -I/root/icinga2-2.4.3/lib -I/root/icinga2-2.4.3/obj-aarch64-linux-gnu -I/root/icinga2-2.4.3/obj-aarch64-linux-gnu/lib -I/root/icinga2-2.4.3/third-party/execvpe -I/root/icinga2-2.4.3/third-party/mmatch -I/root/icinga2-2.4.3/third-party/socketpair -o CMakeFiles/base.dir/base_unity.cpp.o -c /root/icinga2-2.4.3/obj-aarch64-linux-gnu/lib/base/base_unity.cpp
I'm a novice in android devices: What would be required to use a custom kernel? A hacked boot loader, which is not available for the AFTV2?
segfault1978 said:
I'm a novice in android devices: What would be required to use a custom kernel? A hacked boot loader, which is not available for the AFTV2?
Click to expand...
Click to collapse
Yep... we need to be able to use fastboot to boot an unsigned kernel and initramfs (boot.img). I tried at one point to overwrite the boot partition with own image and it failed to boot. Since I had the preloader stuff worked out already I was able to restore the original boot image and get it working again.
On a side note, if you don't mind could you post the list of packages needed to install SSH server from rc.local? Others might find that useful. To get around the unset password issue you could have also saved a public key in /root/.ssh/authorized_keys which would also avoid you needing to change /etc/ssh/sshd_config to allow password logins as root.
segfault1978 said:
within the source package. One single cpp call consumes so much memory (which is crazy in my eyes, never seen such a big compiler process until today), so I'll investigate the option of cross compiling and afterwards creating the deb file outside of the machine.
Code:
cd /root/icinga2-2.4.3/obj-aarch64-linux-gnu/lib/base && /usr/bin/aarch64-linux-gnu-g++ -DI2_BASE_BUILD -Doverride="" -g -O2 -fstack-protector --param=ssp-buffer-size=4 -Wformat -Werror=format-security -D_FORTIFY_SOURCE=2 -g -pthread -std=c++11 -Wno-inconsistent-missing-override -fPIC -I/root/icinga2-2.4.3 -I/root/icinga2-2.4.3/lib -I/root/icinga2-2.4.3/obj-aarch64-linux-gnu -I/root/icinga2-2.4.3/obj-aarch64-linux-gnu/lib -I/root/icinga2-2.4.3/third-party/execvpe -I/root/icinga2-2.4.3/third-party/mmatch -I/root/icinga2-2.4.3/third-party/socketpair -o CMakeFiles/base.dir/base_unity.cpp.o -c /root/icinga2-2.4.3/obj-aarch64-linux-gnu/lib/base/base_unity.cpp
Click to expand...
Click to collapse
I see you are not using -pipe which is good, but a quick search suggested something that might not be simple since this package has it's own build system but changing from -O2 to -O1 might help.
I noticed that Debian has the package available for the same version and already built for arm64.
https://packages.debian.org/sid/icinga2
Maybe you already tried that. You could try going back to jessie which is probably an older version but I think most jessie packages work with Ubuntu 14.04.
zeroepoch said:
Yep... we need to be able to use fastboot to boot an unsigned kernel and initramfs (boot.img). I tried at one point to overwrite the boot partition with own image and it failed to boot. Since I had the preloader stuff worked out already I was able to restore the original boot image and get it working again.
On a side note, if you don't mind could you post the list of packages needed to install SSH server from rc.local? Others might find that useful. To get around the unset password issue you could have also saved a public key in /root/.ssh/authorized_keys which would also avoid you needing to change /etc/ssh/sshd_config to allow password logins as root.
Click to expand...
Click to collapse
This is the list of packages I manually downloaded for ARM64 (unfortunately I used Debian packages which worked first, but leads to a hell situation afterwards when dealing with other dependencies; be sure to use Ubuntu packages in order to avoid problems afterwards):
Code:
busybox_1.22.0
libedit2_3.1
libgssapi-krb5
libk5crypto3
libkeyutils1
libkrb5
libkrb5support0
libwrap0
openssh-client
openssh-server
openssh-sftp-server
This is the piece of calls in /etc/rc.local, right before the exit:
Code:
dpkg --force-all -i /*.deb > /install.log 2>/install.err
echo $? >> /install.log
echo "installation finished" >> /install.log
It took about 1-2 minutes before SSH started to work automatically, you can mount the SD card afterwards in another system in order to check the written logfiles.
Here are some notes for getting wireless working. In addition to the normal OS steps (installing wpasupplicant or wireless-tools and editing /etc/network/interfaces or using wicd) you will need some firmware files from /system (/dev/mmcblk0p13).
Code:
mount -o ro /dev/mmcblk0p13 /mnt
cp -r /mnt/etc/firmware/ /lib/
cp -r /mnt/etc/Wireless /etc/
umount /mnt
segfault1978 said:
None of these methods (since I was in my weekend and all cables and adapters reside in my office)
I placed all .deb-files for openssh-server including all requiremens onto the microSD card, and placed a call "dpkg -i /*.deb" with logging options in /etc/rc.local. I also configured network by mounting the sd card, editing /etc/network/interfaces, and last changed /etc/shadow to have a valid root account for login. It took my some try-and-error loops, but finally it worked as expected. Call me crazy, but I succeeded without any hardware.
Thank you for the the fire tv guide.
Click to expand...
Click to collapse
So, what's the verdict on this? I want to use my firetv 2 as an emby server. Is it worth it trying to get Ubuntu to run?
Sent from my Mi A1 using Tapatalk
mrchrister said:
So, what's the verdict on this? I want to use my firetv 2 as an emby server. Is it worth it trying to get Ubuntu to run?
Click to expand...
Click to collapse
If it has arm64 packages and headless you can give it a try. If you don't like it you can just revert the ramdisk and go back to Android.
Ok sweet, thanks for the reply
Sent from my Mi A1 using Tapatalk
Just curious if anyone's tried running Plex server on this?
I've been looking for a better solution without shelling out $500+ for a dedicated NAS. AFTV is tiny so I could hardwire it and hide it away.
Thanks
I got the same idea. Right now the firetv is still being used as a media streamer but I'm thinking of doing this soon
Hello,
I not familiar with Arch, so I will try Debian or Ubuntu in the MeMO Pad.
I have setup Ubuntu 21.04 in another computer on the SD card and put it in the tab.
I have put the vmlinuz and initrd.img on the adp partition.
With the config file ubuntu.conf in /esp/loader/entries (on the esp partition) :
title Ubuntu
volume 80868086-8086-8086-8086-000000000007
linux /vmlinuz-5.11.0-16-generic
initrd /intel-ucode.img
initrd /acpi-me176c.img
initrd /initrd.img-5.11.0-16-generic
options root=UUID=<UUID of the ubuntu partition in SD> rw
Click to expand...
Click to collapse
With or without the intel-ucode.img and acpi-me176c.img it the same.
I have touchscreen, sound, USB, rotation, but I don't have : Wifi, Bluetooth, battery management
I don't understand how to port the drivers ; https://github.com/me176c-dev/linux-me176c/blob/master/porting.md
Is it more easier with Debian or an older kernel ?
Can I use an arch or postmarketos package or is it directly in the kernel ?
Thanks in advance
Hey Daouid,
Have you had any further luck? I have one of these old MemoPads and would love to see it working again!
Cheers
Rockymars
Hey Rockymars,
Sorry, no ...
I don't have try more and don't have answers.
I think a solution can be to buy a low cost USB Ethernet or USB Wifi with standard driver to use this an OTG USB.
And to put the tab in charge when she is off or with Android.
I don't know if Ubuntu 22.04 could have this drivers.
Anybody know how to add drivers to Ubuntu or Debian ?