Forum › Forums › Official Releases › antiX-19 “Marielle Franco, Hannie Schaft, Manolis Glezos, Grup Yorum, Wobblies” › Can't get into X with live USB
- This topic has 5 replies, 3 voices, and was last updated Oct 26-9:47 pm by LogstarGo.
-
AuthorPosts
-
October 25, 2019 at 12:55 am #28533Member
LogstarGo
I’ve installed antiX on a few systems: VMs on VMware, an old 32-bit netbook from 10 years ago, and so forth with no problems at all. I’ve tried installing it (many times) on my Asus Vivobook E203MA. Whenever I try using the live USB it never works. I can’t get into X at all. I get errors like “cannot assign requested address” after trying to start X at the command line, or things about there not being a window, and nothing I do gets me to any sort of desktop. I will note that, even though I don’t remember what was required, it was originally hard to get Lubuntu (the present OS) on the system to begin with; in those cases at least X or something comparable started. Has anyone come across this sort of error before? I’d love to use AntiX since the VM I’ve set up on the Lubuntu box is more responsive than the system it’s on and it would be great to have my whole system work that way.
October 25, 2019 at 3:55 am #28539Moderator
caprea
::It would be better to know more about your harddware, so an
inxi -zv7
from your installed ubuntu might help.
Also might important, how did you create the live-usb ?October 25, 2019 at 4:01 am #28540Forum Admin
rokytnji
::Arch linux did a good write up on the predecessor of your netbook which also was built with issues on having linux installed on it.
https://wiki.archlinux.org/index.php/ASUS_x205ta
Since my last foray with a Asus Touchscreen laptop. Asus gear leaves a bad taste in my mouth.
Hardware access is not easy and connections, fragile.Sometimes I drive a crooked road to get my mind straight.
Not all who Wander are Lost.
I'm not outa place. I'm from outer space.Linux Registered User # 475019
How to Search for AntiX solutions to your problemsOctober 26, 2019 at 7:53 pm #28624MemberLogstarGo
::Huh, it took me awhile to post here since I figured it was a dumb question. Sounds like it wasn’t (and I’ll look through the writeup soon). Anyway…
For live-usb I have used 3 different drives, tried both base and core, and have tried it using the Live USB utility on an antiX 19 64-bit VM (on another system) and Etcher on Windows 8.1. Same things happened each time.
As for the inxi thing, running as root:
System: Host: TheClassic Kernel: 4.15.0-64-generic x86_64
bits: 64 gcc: 7.4.0
Desktop: LXDE (Openbox 3.6.1) info: lxpanel dm: lightdm
Distro: Ubuntu 18.04.3 LTS
Machine: Device: laptop System: ASUSTeK product: VivoBook 12_ASUS Laptop E203MAS_E203MA v: 1.0 serial: <filter>
Mobo: ASUSTeK model: E203MAS v: 1.0 serial: <filter>
UEFI: American Megatrends v: E203MAS.302 date: 06/26/2018
Battery BAT0: charge: 28.8 Wh 98.5% condition: 29.2/38.0 Wh (77%)
volts: 7.6/7.6
model: ASUSTeK ASUS Li-ion serial: N/A status: Discharging cycles: 0
CPU: Dual core Intel Celeron N4000 (-MCP-) arch: N/A cache: 4096 KB
flags: (lm nx sse sse2 sse3 sse4_1 sse4_2 ssse3 vmx) bmips: 4377
clock speeds: min/max: 800/2600 MHz 1: 1768 MHz 2: 1761 MHz
Memory: Array-1 capacity: 8 GB devices: 4 EC: None
Device-1: A1_DIMM0 size: 1 GB speed: 2400 MT/s
type: LPDDR4 (Synchronous) bus width: 16 bits
manufacturer: ABCD part: 123456789012345678 serial: <filter>
Device-2: A1_DIMM1 size: 1 GB speed: 2400 MT/s
type: LPDDR4 (Synchronous) bus width: 16 bits
manufacturer: ABCD part: 123456789012345678 serial: <filter>
Device-3: A1_DIMM2 size: No Module Installed
type: DDR2 (Synchronous) bus width: 64 bits
Device-4: A1_DIMM3 size: No Module Installed
type: DDR2 (Synchronous) bus width: 64 bits
Graphics: Card: Intel Device 3185 bus-ID: 00:02.0 chip-ID: 8086:3185
Display Server: X.Org 1.19.6
drivers: modesetting (unloaded: fbdev,vesa)
Resolution: 1366×768@60.00hz
OpenGL: renderer: Mesa DRI Intel UHD Graphics 600 (Geminilake 2×6)
version: 4.5 Mesa 19.0.8 (compat-v: 3.0) Direct Render: Yes
Audio: Card Intel Device 3198
driver: snd_hda_intel bus-ID: 00:0e.0 chip-ID: 8086:3198
Sound: Advanced Linux Sound Architecture v: k4.15.0-64-generic
Network: Card: Intel Device 31dc
driver: iwlwifi bus-ID: 00:0c.0 chip-ID: 8086:31dc
IF: wlo1 state: up speed: N/A duplex: N/A mac: <filter>
WAN IP: <filter>
IF: vmnet8 ip-v4: <filter> ip-v6-link: <filter>
IF: wlo1 ip-v4: <filter> ip-v6-link: <filter>
IF: vmnet1 ip-v4: <filter> ip-v6-link: <filter>
Drives: HDD Total Size: NA (-)
ID-1: /dev/mmcblk0 model: N/A size: 31.3GB serial: N/A
Optical: No optical drives detected.
Partition: ID-1: / size: 28G used: 18G (67%) fs: ext4 dev: /dev/mmcblk0p2
label: N/A uuid: 4b2c748b-e7de-446e-840b-bef6f3c2c211
ID-2: /boot/efi size: 511M used: 6.1M (2%)
fs: vfat dev: /dev/mmcblk0p1 label: N/A uuid: 40C2-BFC4
ID-3: swap-1 size: 1.02GB used: 0.01GB (1%)
fs: swap dev: /dev/mmcblk0p3
label: N/A uuid: 668d8eaf-97f4-44c6-a69d-be238d32aefe
RAID: System: supported: N/A
No RAID devices: /proc/mdstat, md_mod kernel module present
Unused Devices: none
Unmounted: ID-1: /dev/mmcblk0 size: 31.27G label: N/A uuid: N/A
ID-2: /dev/mmcblk0boot1 size: 0.00G label: N/A uuid: N/A
ID-3: /dev/mmcblk0boot0 size: 0.00G label: N/A uuid: N/A
Sensors: System Temperatures: cpu: 40.0C mobo: N/A
Fan Speeds (in rpm): cpu: N/A
Info: Processes: 169 Uptime: 6 min Memory: 1079.0/1817.1MB
Init: systemd v: 237 runlevel: 5 Gcc sys: 7.4.0 alt: 5
Client: Shell (bash 4.4.201 running in sudo) inxi: 2.3.56And thank you!
October 26, 2019 at 8:45 pm #28626Moderator
caprea
::tried both base and core
First for clarification general, on antiX-core there is no X.
You shouldn’t hesitate to ask, you have nothing to fear, in my opinion.There are no dumb questions, there are might stupid answers.October 26, 2019 at 9:47 pm #28627MemberLogstarGo
::Oh, sorry, it was base and full. I looked into core and decided it wasn’t a good idea due to things like that.
-
AuthorPosts
- You must be logged in to reply to this topic.