Siduction Forum
Siduction Forum => Installation - Support => Topic started by: crankypuss on 2016/01/20, 10:33:16
-
Okay, starting with the 32bit LXQT paintitblack ISO downloaded yesterday. Note that I did not spend much time reading the manual, that would be cheating! <g>
1. Installer's graphical grub menu boots up nicely on Dell XPS13, but didn't try to install there, the XPS13 is (almost too) easy, we'll try the problem-child...
2. Moving to ASUS T100. This tablet/keyboard combo is UEFI-only. Bay Trail 64bit processor with OMG a 32bit EFI firmware. The 32bit stretch netinst will install on this box but some gymnastics are required to set up and keep a network connection, and then you get to go through the usual "find your driver" circus. Note my only network connection is via cellphone or aircard, usually just make the phone act as a wifi hotspot.
The graphical grub menu did not show up on this box, but USB sticks for most distros aren't even recognized as bootable so it's good to have *any* grub menu appear:
http://expirebox.com/download/aa491332d973f1e8a6e8d3096c1e459e.html
I had no clue what was going on there but hit ENTER and a normal-looking linux boot message-stream flashed down the screen and what I presume to be the "Live" version appeared. I poked around a bit but wasn't really interested in exploring LXQT so much as I wanted to see if it would install on the ASUS. So I clicked on the Installer icon and the following appeared:
http://expirebox.com/download/7e4c5803bcb97961cd4ce655c94f9487.html
Well, dang. Not much point in having a 1G ISO if it's a netinst. Apparently the installer build does not include all the drivers since no wifi connection as far as I could tell.
What now, boss? <g>
-
The driver for wifi should be there. To make sure, please post relevant info about your wireless chip. You can obtain that by running
lspci -vv | grep -i wireless.
greetz
devil
-
I suppose that message does not appear because of lacking internet connection. The installer magic runs on some webserver-port-80-foo thing, and I've seen it before (was some time ago) that the installer/browser-combination did not come up at the first attempt. Probably a race condition at boottime (webserver not stared), or reloading the installer (or refreshing that page) could be enough.
_
(Edit: As the picture hoster you used need download of the file, I shrinked and added the picture from your 'expirebox' here)
-
Hello crankypuss,
please start to read the docs immediately.
There is an "Errata"-Thread for the dev-release in the Installationsupport subforum.
And your issue is one of the known issues. Solution: click the "try again" button.
Please let me point out, we don't have the man power to do spoonfeeding with unwilling people.
siduction is a small project and we don't have touch-optimized applications to offer.
siduction isn't targeted at bay trail tablets.
From my point of view this was my last word in this case.
-
You may have better luck using the new dev release as it contains a more recent kernel plus non-free firmware.
-
The driver for wifi should be there. To make sure, please post relevant info about your wireless chip. You can obtain that by running lspci -vv | grep -i wireless.
Here is better information about both the chip and the driver than I can provide. I've gone through the process of installing the driver on stretch as is described here, but thought that wouldn't be necessray with siduction:
https://wiki.debian.org/InstallingDebianOn/Asus/T100TA (https://wiki.debian.org/InstallingDebianOn/Asus/T100TA)
I mean, if you really *want* to look at the output of lscpi on the ASUS, I could re-run the installer and presumably get up a terminal under LSQT, but somebody has already done that bit of work. Let me know, I can drag out the ASUS and transfer it to my Dell on a USB stick, but if that can be avoided while you get better info, hey I'm lazy.
BTW... I haven't finished going through the EFI Specification yet, but I seem to remember seeing some EFI call (C-language interface) that would tell you what kind of system it is. If there isn't there ought to be <g> and if there is it would make life easier for installers since the details would be a table-lookup that we could add to as new systems show up. Got a "Dell XPS13"? Ok, here's what that one needs, same as the Debian wiki. Just a thought.
-
I suppose that message does not appear because of lacking internet connection. The installer magic runs on some webserver-port-80-foo thing, and I've seen it before (was some time ago) that the installer/browser-combination did not come up at the first attempt. Probably a race condition at boottime (webserver not stared), or reloading the installer (or refreshing that page) could be enough.
_
(Edit: As the picture hoster you used need download of the file, I shrinked and added the picture from your 'expirebox' here)
1. Do you mean the installer magic runs on a local webserver? Hmmm. I did hit "Try Again" as I recall, but will do it again and see what happens.
2. That's the first picture I've uploaded in literally years, can you recommend a hoster and method of including photos?
Thanks.
-
You may have better luck using the new dev release as it contains a more recent kernel plus non-free firmware.
Sorry, I don't understand. This is the one that I downloaded:
siduction-15.1.0-paintitblack-lxqt-i386-201601171445.iso
If there is a newer "dev" release please advise how to find/access the dev releases. TIA.
-
Hello crankypuss,
please start to read the docs immediately.
There is an "Errata"-Thread for the dev-release in the Installationsupport subforum.
And your issue is one of the known issues. Solution: click the "try again" button.
Please let me point out, we don't have the man power to do spoonfeeding with unwilling people.
siduction is a small project and we don't have touch-optimized applications to offer.
siduction isn't targeted at bay trail tablets.
From my point of view this was my last word in this case.
From my point of view, I hope it *was* your last word in this case, grandma moderator, since you have nearly alienated me from contributing to siduction in any way whatsoever.
-
The driver for wifi should be there. To make sure, please post relevant info about your wireless chip. You can obtain that by running lspci -vv | grep -i wireless.
Yes, we are finding clues. It appears that siducer is not detecting the hardware. I saw this with stretch before installing the driver for the wifi chip; seems there was a startup message about some brcm device, if you can tell me where to find the startup messages maybe there is something to be seen. Here is the info you requested:
siducer@siduction:~$ man lspci
siducer@siduction:~$ lspci -vv | grep wireless
siducer@siduction:~$ /usr/bin/lspci -vv | grep wireless
siducer@siduction:~$ /usr/bin/lspci -vv
00:00.0 Host bridge: Intel Corporation Atom Processor Z36xxx/Z37xxx Series SoC Transaction Register (rev 0d)
Subsystem: ASUSTeK Computer Inc. Atom Processor Z36xxx/Z37xxx Series SoC Transaction Register
Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx-
Status: Cap- 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- <TAbort- <MAbort- >SERR- <PERR- INTx-
Latency: 0
Kernel driver in use: iosf_mbi_pci
Kernel modules: iosf_mbi
00:02.0 VGA compatible controller: Intel Corporation Atom Processor Z36xxx/Z37xxx Series Graphics & Display (rev 0d) (prog-if 00 [VGA controller])
Subsystem: ASUSTeK Computer Inc. Atom Processor Z36xxx/Z37xxx Series Graphics & Display
Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx+
Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- <TAbort- <MAbort- >SERR- <PERR- INTx-
Latency: 0
Interrupt: pin A routed to IRQ 205
Region 0: Memory at 90000000 (32-bit, non-prefetchable) [size=4M]
Region 2: Memory at 80000000 (32-bit, prefetchable) [/size][size=256M]
Region 4: I/O ports at 1000 [/size][size=8]
Expansion ROM at <unassigned> [disabled]
Capabilities: <access denied>
Kernel driver in use: i915
Kernel modules: i915
00:14.0 USB controller: Intel Corporation Atom Processor Z36xxx/Z37xxx Series USB xHCI (rev 0d) (prog-if 30 [XHCI])
Subsystem: ASUSTeK Computer Inc. Atom Processor Z36xxx/Z37xxx Series USB xHCI
Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx+
Status: Cap+ 66MHz- UDF- FastB2B+ ParErr- DEVSEL=medium >TAbort- <TAbort- <MAbort- >SERR- <PERR- INTx-
Latency: 0
Interrupt: pin A routed to IRQ 203
Region 0: Memory at 90800000 (64-bit, non-prefetchable) [/size][size=64K]
Capabilities: <access denied>
Kernel driver in use: xhci_hcd
Kernel modules: xhci_pci
00:1a.0 Encryption controller: Intel Corporation Atom Processor Z36xxx/Z37xxx Series Trusted Execution Engine (rev 0d)
Subsystem: ASUSTeK Computer Inc. Atom Processor Z36xxx/Z37xxx Series Trusted Execution Engine
Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR+ FastB2B- DisINTx+
Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- <TAbort- <MAbort- >SERR- <PERR- INTx-
Latency: 0
Interrupt: pin A routed to IRQ 202
Region 0: Memory at 90700000 (32-bit, non-prefetchable) [/size][size=1M]
Region 1: Memory at 90600000 (32-bit, non-prefetchable)
Capabilities: <access denied>
Kernel driver in use: mei_txe
Kernel modules: mei_txe
00:1f.0 ISA bridge: Intel Corporation Atom Processor Z36xxx/Z37xxx Series Power Control Unit (rev 0d)
Subsystem: ASUSTeK Computer Inc. Atom Processor Z36xxx/Z37xxx Series Power Control Unit
Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR+ FastB2B- DisINTx-
Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=medium >TAbort- <TAbort- <MAbort- >SERR- <PERR- INTx-
Latency: 0
Capabilities: <access denied>
Kernel driver in use: lpc_ich
Kernel modules: lpc_ich
siducer@siduction:~$
[/size][/size][/size][/size][/size]
-
There is an "Errata"-Thread for the dev-release in the Installationsupport subforum.
And your issue is one of the known issues. Solution: click the "try again" button.
"Try Again" did not work, nor did exiting and re-opening the 'Install' icon.
-
Please copy my link
lspci -vv | grep -i wirelessYou missed the -i
greetz
devil
-
siducer@siduction:~$ lspci -vv | grep -i wireless
siducer@siduction:~$
I'm not sure why you expect grep to return something that wasn't in the command, but I copied your command and put it on a USB stick and tried it on the ASUS as shown above. HTH.
-
You may have better luck using the new dev release as it contains a more recent kernel plus non-free firmware.
Sorry, I don't understand. This is the one that I downloaded:
siduction-15.1.0-paintitblack-lxqt-i386-201601171445.iso
If there is a newer "dev" release please advise how to find/access the dev releases. TIA.
Apologies, that is the dev release. Good luck!
Personally I wouldn't attempt to install it on a tablet, but I'm just a lowly user.
-
I don't view it as a tablet, as far as I'm concerned it's just a 10" netbook that comes apart at the hinge. Good luck finding a 10" netbook these days that isn't some sort of tablet. <g>
-
No, you have to see it as a tablet because in 1st instance it is a tablet.
It has a f**ing 32bit EFI as every Win-Tablet in the wild.
-
No, you have to see it as a tablet because in 1st instance it is a tablet.
It has a f**ing 32bit EFI as every Win-Tablet in the wild.
I hear you. Maybe I'll write that blog post I've been thinking about, "Computers Used To Have Switches". Hey, when I first signed up for a userid here, it asked for website, but I had trouble reading the captcha letters and I've never seen that again. Is there a way to put it in? I hunted in profile-settings for a while but didn't find it. Maybe events intervened, I don't remember.
Anyway, no, you don't have to care whether it's a tablet or a mainframe, what you have to remember is that it's a computer, and that sets certain requirements upon it, whether the implementation meets them or not.
We are in control here, not the hardware makers. What we ought to do, if money is needed to keep siduction afloat, is write up a spec and send it to China for manufacture then sell them for no more profit than necessary. I wonder if it's legal to sell dual-boot Windows/Linux systems... not that many linux users would care.
The ASUS T100 eats binary and poops output, so in my book it's just a computer.
-
towo` is right, its a fucking tablet - with a fucking 32 bit efi on a stupid assembled platform. So i guess you might be able to install a starting system if you find a starting image with matching efi. never tested it, but then you are eventually able to run a iso from grub and install siduction. And maybe you will find a matching efi package for the tablet in the debian repo.
Sorry, we don't care about this platform because non of the devs would buy such hardware and until now nobody™ was in this desparate state of mind to dedicate us such crap. 8)
-
Geez, a "Global Moderator" defying the roolz about vulgarity, right on, fuck the rules!
Tell you what, spud; Debian stretch runs just fine on it, only you have to go through the find-the-driver circus. I figured with siduction, I could get the drivers in the ISO and not need to do an inplace upate to sid; after all that's kind of the point of siduction, not needing to update to sid, and y'all did advertise as how you'd included the basic non-free drivers, right? Stupid me, huh?
"never tested it" seems to be about par for the course, you don't know much about it but you have the opinion that you're an expert, oh my!
What did You People think was going to happen with EFI, it was just going to go away?
I'd rather have a plain old BIOS system, but I'm pretty sure I'll keep this ASUS T100 because it's useful as a UEFI-Only testcase.
Tell you what, smart-guy; why don't you go find a 10" netbook with some kind of current hardware; wake me up when you get done.
-
Maybe your best bet is to run debian on it - and you are right, i have no clue about building a efi-enabled distribution nor a clue about debian and linux et all.
And it's only a hint: One should inform himself beforehand who one pisses and who better not , if one wants to preserve the chance of help or assistance in any form.
-
I tried to get you to find out what driver was needed. That did not go well, even though I just asked for the output of a simple command. So maybe you need to tone down a bit and realize that your tablet is not a normal device for efi tests and for sure not the best device to judge a new distribution on.
greetz
devil
-
I tried to get you to find out what driver was needed. That did not go well, even though I just asked for the output of a simple command. So maybe you need to tone down a bit and realize that your tablet is not a normal device for efi tests and for sure not the best device to judge a new distribution on.
Maybe You People ought to understand that Debian is "The Universal Operating System" and if you're going to play in that ballpark maybe you should deliver the goods instead of just talk.
I asked where to find the startup log, and I'm still waiting. I'm pretty sure I saw an obvious message about some brcm issue.
You want to maybe actually read the output of that command, which I posted. The lscpi command isn't going to report something the kernel hasn't recognized.
-
And it's only a hint: One should inform himself beforehand who one pisses and who better not , if one wants to preserve the chance of help or assistance in any form.
You might want to keep that in mind, I've been writing systems code and developer utilities since Linus Torvalids was in mommy's womb.
-
then you should be able to solve your problems alone - and with your attitude i think you must solve your problems alone
-
Hello crankypuss,
siduction is open for contributions of the community. Everybody is welcome to join the community and show up with ideas, feedback, bugreports, code, artwork or doing any kind of support. Recent contributions like the newly developed flavours siduction-lxqt and -mate are examples for this openess.
Demanding support for cornercases like 32 bit EFI is the opposite of contributing. Binding the manpower of a small project for your personal hardwaresupport isn't justified by the poor outcome. While we ignored your demands we have spend the time working on the installer URL issue you noticed.
Bad mood will immediately arise when such demanders happily announce that they are even unwilling to look at the docs. I think somebody should have closed this thread directly after my first post.
greetings
musca
-
Hello crankypuss,
we are tracking the network issue (http://bugs.siduction.org/issues/1823) as a combined weakness in cmst and qupzilla:
When cmst fails to configure the network, quipzilla won't connect to localhost.
This glitch prevents accessing the installer and the manual.
greetings
musca
-
It appears this thread has run to its natural conclusion with nothing further coming that would be productive, so locking thread now.
Couple of observations for future reference:
- people who voluntarily develop and support the distribution deserve the respect of users (i.e. their opinions and choices of priorities should be taken seriously, whether agreed upon or not)
- English is not the first language of many of the siduction team, so the insult detector needs to be turned way down, especially since written communications don't convey emotional content very well
Thanks.
-
Thanks dibl for the conclusion. Actualy the thread was closed already by me, which you might have overseen due to your mod status :)
greetz
devil