Show Posts

This section allows you to view all posts made by this member. Note that you can only see posts made in areas you currently have access to.

Messages - Transdude1996

Pages: [1] 2
Help / Re: Error message when loading the desktop (Native)
« on: January 15, 2019, 04:48:11 AM »
Well, that sucks. Was hoping to begin migrating away from using Windows given the fresh hard drive on my laptop. Well, actually, I could still do that by having my desktop and my other laptop (Which, I honestly don't use that often because of how sensitive it is with the battery connection is) dualboot AROS since both seemed to load the drives without any problems.

Also, I don't really want to use UNIX. Anyways, thanks for the help.

Help / Re: Error message when loading the desktop (Native)
« on: January 14, 2019, 08:30:54 AM »
FreeDOS was able to install, but I experienced several hiccups along the way. Haiku either crashed or froze (Even on UEFI) before I could even do anything.

Should I just take the plunge and install Windows 8.1 on the darn thing, free up enough drive space to install AROS, and then see if I can dualboot it? Or will it not make much of a difference?

Help / Re: Error message when loading the desktop (Native)
« on: January 13, 2019, 08:39:06 PM »
How about a video of the shell loading with the debug (That I recorded on my phone)? Be aware that the file is...rather large.
Yes, that for sure helps (sorry i didn't think of that myself). I got two remarks on that a) the resolution is ridiculous (perhaps not something you are ale to do something about at recording time)
I can control that to an extent, and I set all the quality settings to the max figuring it would deliver the best clarity because earlier attempts had some of the text in the shell blurring together because of the screen's glow. I'll see about making it a more reasonable size next time.

b) it skips the last say about 10 seconds for me. So i had some delay in trying to fix that (sorry for that)
It's okay.

Just for the record: what version of AROS are you booting there exactly ? I seem to be missing some output ?
The ABIv0 build from last Monday.

So, overall, where does that leave things?
So, you are telling that you are unable to turn off secure boot in your BIOS ? Changing BIOS to use legacy boot does not change anything ?
There is no secure boot option, unless I set to boot mode for UEFI. And, I have changed the BIOS to allow USB legacy support, set boot mode to legacy support, set boot priority to legacy first, and changed the OS optimized defaults to Other OS. But, the problem is that I cannot find a way to actually change the SATA hard drive's mode to AHCI or IDE.

Just as a side-track, are you able to install (v1 as that seems to boot for you) onto a sd-card (i've just noticed your hardware has a sd-card slot)
Didn't know that I can do that. I'll see about giving it a whirl.

I'm a bit stuck with your installation of v1 issue as it seems a problem that was encountered during icaros desktop 2.x Wip releases (which is v0 abi). Same user methanoid reported something similar earlier in another thread, which seems more in line with your specific issue (i'll dig up that thread in case interrested, i can't find it back atm). Everything seems to boot fine but installing  onto internal SSD causes AROS to throw errors.

With regards to abiv0 it would be helpfull if you are able to give it another try and get into the early boot menu (press both left and right mousebuttons right after grub menu entry is booting) and have some pictures of that menu. In case your mouse isn't working in the EBM, then unplug and insert you mouse again (that usually helps). Then select to boot without startup-sequence to see if you are able to boot into a shell. If that works we could take the next step in attempting to identify the issue.
I know that the premade Icaros Grub options allows for the user to enter early boot without having to use any keyboard shortcuts. Would that still work? Never mind.

In case anyone else has an idea then please feel free to jump in. Also because I usually do not use V1 abi at all. A Aros developer might have better information with regards to v1 ABI, but systemn developers seems less active on the forums.
So, try to keep everything restricted to ABIv0. Okay.

EDIT: Actually, now I'm wondering something. Just to make sure that the problem isn't a complete OS lock-out (And just a problem with AROS), should I try to see if I can install a different OS, something light like FreeDOS or TempleOS (Something I can easily remove)?

Help / Re: Error message when loading the desktop (Native)
« on: January 13, 2019, 06:17:49 AM »
I think I may have found the source of my problems!

Decided to just say the heck with it and install the ABIv1 build, however I...actually cannot. For some reason, the AROS installer states that the "Drive is full". I didn't want to do a wipe just in case it breaks the hard drive (Especially since the drive is empty), so I started searching the the previous forum archives for that specific issue error message. And, it wasn't until I inputted into the search "Disk is full SATA" that I finally started getting somewhere. A poster by the name of "nikolaos" (I'm assuming nikos' previous account) made a some threads about his hard drive with changing the "SATA support". Remembering that you guys were talking about that as well, and pointed to this post on common fixes (It went way over my head at the time and I didn't fully understand what you were hitting at), I finally decided to start searching the internet on how to change the mode on my hard drive to IDE or AHCI (Because the BIOS sure wasn't giving me options to do it). Eventually, I stumbled across this article: Lenovo slammed for OS-locking BIOS block
The consumer PC arm of tech giant Lenovo has denied locking alternative operating systems out of its Yoga family of laptops, but evidence suggests the presence of a very deliberate BIOS lock for exactly that purpose.

Lenogo's Yoga 900 and 900S convertible laptops, boasting what Lenovo describes as 360-degree hinges designed to easily convert between laptop and tablet modes, are available with a bloat-free variant of Windows 10 installed known as Windows 10 Signature Edition. These machines have been tempting those looking to ditch the factory-fitted operating system - and, in the case of Lenovo's consumer offerings, possibly with very good reason - in favour of alternative operating systems such as GNU/Linux or a BSD variant.

Unfortunately, it turns out that's not possible. Users have taken to social media to complain that the storage device in these laptops is locked into a RAID mode - an odd choice for a single-drive system - which is exclusively compatible with Windows 10 with the installation of a Lenovo-penned driver module. Those attempting to install any other operating system - including older versions of Windows - find the storage device entirely absent from the list of places on which to install said operating system.

'Our Yoga design requires very specific, complex and unique drivers that require even greater amounts of testing, to ensure class-leading performance with Windows 10. To support our Yoga products and our industry-leading 360-hinge design in the best way possible we have used a storage controller mode that is unfortunately not supported by Linux and as a result, does not allow Linux to be installed,' Lenovo has claimed in a statement on the matter, published late last night. 'Beyond the controller setup limitation, other advanced capabilities of the Yoga design would likely not work with current Linux offerings. Lenovo does not intentionally block customers using other operating systems such as Linux on Yoga or any of its devices and is fully committed to providing Linux certifications and installation guidance on a wide range of suitable products.'

The trouble with Lenovo's explanation is that it doesn't hold water. The use of a RAID mode for storage devices has no impact on the clever-or-otherwise hinge mode. More tellingly, users have succeeded in modifying the stock BIOS to allow a previously unavailable AHCI storage mode to be selected - at which point installing any third-party operating system becomes entirely possible, and the laptop works perfectly during and after installation. Lenovo's statement also flies in the face of a comment received by an affected user from Lenovo's official support department, published to reddit as part of a complaint thread: 'This system has a Signature Edition of Windows 10 Home installed. It is locked per our agreement with Microsoft.'

Now, as I said in the OP, my laptop is a Yoga 2 13, which started seeing released back in 2013. However, later in August of 2015, there was an update to the BIOS (That I'm assuming has a similar functionality to the lock-out mentioned in the above article), and I must have installed it while I was using windows 8/10 at the time (My hard drive failed just last year, and that's when I decided to start making the OS switch). And, looking at my laptop's "official" drivers, there isn't a "known" way for me to back flash it like the Yoga 900 users were eventually able to.

So, overall, where does that leave things?

Site feedback / The change in the site layout
« on: January 12, 2019, 08:12:01 PM »


Help / Re: Error message when loading the desktop (Native)
« on: January 11, 2019, 05:26:57 AM »
Yes, there is but not many motherboards have a port for it anymore. The output you see during boot (and after) can be captured by a serial device. The only other possibility is when you are able to at least get a shell window up and then "capture" the log output with bifteck.
How about a video of the shell loading with the debug (That I recorded on my phone)? Be aware that the file is...rather large.

Help / Re: Error message when loading the desktop (Native)
« on: January 10, 2019, 08:35:14 PM »
Best would be to follow those instructions literally to see if any of it makes any differnce for you booting v0 abi. Use HD Toolbox (or your bootlog) to see if you are able to discover any hidden storage device(s) as suspected by dizzy.
Okay. When I load it up HDTool (On v1), it displays 5 devices: "scsi.device" (Units: 0), "ata.device" (Units: 0), "ahci.device" (Units: 1), "usbscsi.device" (Units: 0), and "usbmss.device" (Units: 0). Only "ahci.device" is selectable, and, when I do open it, it displays a selectable "Unit 0" and:
Size: 7.8G
Partition Table: PC-MBR
Partitions: 0

Also (On v0), deleting the ahci.device entry line in Grub didn't change much of anything aside from a screen briefly popping up, after the shell, stating that AROS is waiting for a bootable media, just before loading the GUI and delivers the error.

I would suggest to give it another try with a pendrive installation booting a v0 nightly and system debug grub addition in case it is able to get that far.
On v0, the error still appears upon loading the GUI, but I kept seeing the shell displaying something have to do with "poseidon.library " and "dos.library" popping up along with "Initresident". Is there a way I can get a more "complete" report for you?

Help / Re: Error message when loading the desktop (Native)
« on: January 10, 2019, 06:27:59 AM »
For starters you can only use the USB2.0 ports (if available outside) There is no working USB3.x driver for AROS.
Figured that by default (Which is why I've been plugging all my boot drives into the regular 2.0 port), but it seems to register my 3.0 port just fine. Or, is this in reference to VB?

Development (General) / Re: SMP Update?
« on: January 10, 2019, 01:50:01 AM »
I heard that BeOS could make all its programs multi-threaded automatically.
At most it's an urban legend: only programMERs can write multi-threaded code, and... manually. An o.s. cannot certainly do it, even automatically.
Isn't Crysis a prime example of this?

Help / Re: Error message when loading the desktop (Native)
« on: January 09, 2019, 10:54:07 PM »
Here's the PCITool report.

General Chat / Re: Computer Simulation
« on: January 09, 2019, 08:51:08 AM »
Just looking for an excuse to buy new hardware?

Help / Re: Error message when loading the desktop (Native)
« on: January 09, 2019, 08:46:05 AM »
ABIv1 doesn't have PCITools. Not yesterday's build, not today's build, and not the x64 build. However, I solved the problem with my thumbdrive (Apparently VirtualBox and AROS don't like a specific USB port on my desktop), so that option is available again, and I even tested it with the ABIv0 build (So back to the original problem).

Now, much earlier, you mentioned something about the Nightlies having a debugger that shows additional information. How do I access it?

Help / Re: Error message when loading the desktop (Native)
« on: January 08, 2019, 08:28:34 PM »
Yeah, it's still not working. AROS does register when I mount the USB in VB, and I can start the installation, but it still time's out after a certain point where it "freezes" for a few minutes and then produces and error. And, this was even with the "barebones" Icaros installation, after I restarted my entire computer after each action (First for wiping the thumbdrive in Windows, then after creating the SFS partition in VB), and after I unplugged all my USB devices aside from my keyboard and mouse.

Oh well. Given what I have, what can I do with the ABIv1 build that I burned to a disc (Since it's the only build of AROS that I can actually load) that would help solve the overall problem, or figure out why this problem is happening? Or, should I just install the nightly and call it a day?

Help / Re: Error message when loading the desktop (Native)
« on: January 08, 2019, 03:07:56 PM »
This happened first on v5.2 (Which worked just fine the previous day), and remained on v6.0. Also, this was on Icaros, and the Nightly builds, and this was without the use of a hard drive.
Did you perhaps by any chance mounted your USB pendrive as raw device and then attempted to install ? fwiw that is a no-go as it is able to destroy some pendrives. The way to do it is by using the host OS' virtual box USB drivers and then mount it to your virtual machine after AROS was boot up correctly from the mounted iso. Do note that VirtualBox is notorious for (re-)introducing bugs in those drivers (again and again unfortunately).

Also VirtualBox (especially in combination with AROS) has sometimes issues with time-outs provided with hubs that do not follow VirtalBox specifications. In that case try to mount from another (direct) header. Reboot of your Host OS is required when you run into such issues. AROS really only supports directly connected USB devices and in legacy (USB 1) mode only icw VirtualBox.

PS: with regards to USB, also note that windows (in case you are using that as host) seems to 'mount' a pendrive differently when you boot with a pendrive inserted. Please don't ask me why but it seems to be capable to disturb VirtualBox' drivers somehow. Might or might not be relevant for your case perhaps.

This happened first on v5.2 (Which worked just fine the previous day), and remained on v6.0
Also noteable: last time i checked, VB host OS drivers are not interchangeable between different versions
Pretty much did all that already. Even uninstalled VB, deleted the leftover files related to it, and then reinstalled the program and started from scratch. However, I don't know what you mean by "another (direct) header".

I'm not sure if I could be of any help, but I'm still thinking that the partition library might have some doing with the error msg on first post.

Grub has an emergency shell that can show partitions. Maybe your pc has some sort of integrated device that aros tries to mount.

You referring to the "ls" command? All it's displaying is the CD drive (That I have plugged in) and the hard drive.

Help / Re: Error message when loading the desktop (Native)
« on: January 08, 2019, 07:38:15 AM »
Which version of VirtualBox and what Operating System are you using ? Note that afaik legacy USB has to be configured for your Virtual Machine and the USB pendrive must be blank. Also take note of the boot order and not enable a internal drive/controller in case you boot dircetly from the .iso file.
This happened first on v5.2 (Which worked just fine the previous day), and remained on v6.0. Also, this was on Icaros, and the Nightly builds, and this was without the use of a hard drive.

Which grub option did you choose from ? afaik the default option will attempt to load drivers for your graphics card if it is recognized but in case your gfx chipset is not 100% supported or having monitor issues then this can result in AROS being booted correctly except for not displaying an actual output for you. In that case choose the vesa option.
It didn't load grub at all.

Pages: [1] 2