Siduction Forum
Siduction Forum => Installation - Support => Topic started by: mdavies5 on 2017/02/03, 01:58:58
-
Successfully created a bootable USB Stick and it boots into the menu. When proceeding there is about 5 seconds of activity on my USB stick then a black square appears and no further activity; waited 5 minutes but no further activity..
I created the USB Stick 3 times using Gnome Disks, Mint Image Writer and the dd command. Each time the same behaviour.
My hardware is a Toshiba Satellite Pro i5, 12Gb RAM, ssd drive, Intel 5500 Video.
The imahe was siduction-16.1.0-patience-xfce-amd64-201612240021.iso
Any suggestions welcomed.
-
When using a usb stick, in grub you have th choose the option fromhd/usb instead of the standard CD/DVD (from memory).
-
Thanks Devil, I should have mentioned earlier that I had tried that option. However, your answer did prompt me to try every option and Memtest and Help worked ok. I then went to the Time, Language and Keyboard settings and opened each one and changed time from UTC to Australia. Language and Keyboard settings I kept the same.
Now I got past the Grub Menu with many commands scrolling and the screen finally locking on following:
X86_64_Start_Kernel
Kernel Panic - Not Synching
Attempted to kill idle task!
I also tried different USB slots (USb2 and 3). The only option I didn't try was to enter some grub parameters but this is a bit beyond my expertise.
Cheers
Michael
-
Please provide us with the output of:
inxi -MGDNI. Please also see if the md5-sum matches
-
MD5 matches and inxi output below. I am downloading the KDE version and will let you know the results ater.
Machine: System: TOSHIBA product: Satellite Pro R50-C v: PS562A-04L001
Mobo: TOSHIBA model: Satellite Pro R50-C v: Version A0
Bios: TOSHIBA v: Version 1.10 date: 04/21/2015
Graphics: Card: Intel Broadwell-U Integrated Graphics
Display Server: X.Org 1.16.4 drivers: intel (unloaded: fbdev,vesa)
Resolution: 1366x768@60.00hz
GLX Renderer: Mesa DRI Intel HD Graphics 5500 (Broadwell GT2)
GLX Version: 3.0 Mesa 10.3.2
Network: Card-1: Intel Wireless 7265 driver: iwlwifi
Card-2: Intel Ethernet Connection (3) I218-V driver: e1000e
Drives: HDD Total Size: 132.0GB (23.9% used)
ID-1: /dev/sda model: SAMSUNG_MZNLF128 size: 128.0GB
ID-2: USB /dev/sdb model: DT_101_II size: 4.0GB
Info: Processes: 178 Uptime: 4:59 Memory: 1001.6/11952.9MB
Client: Shell (bash) inxi: 2.1.28
-
use irc - it might be a rare problem with the release
-
FYI the KDE version has the same problem. What does "use irc" mean, apart from "internet relay chat" but I am not sure how that will help? I may need to brush up on my acronyms :)
-
If you join us there, we might be able to help better. A button to join #siduction is on the desktop. Please mind we are in Europe mostly and best contacted from 8 -24 CET. If noone answers in #siduction after a few minutes, join #siduction.de to wake us up. :)
-
Thanks Devil for the offer. I think I have wasted enough of your time which I appreciate very much. Nobody else has reported this problem so it must be unique to my system. I will try it on other systems over the next few days and report if there is any interesting news. In the meantime I can wait for the Cinnamon version and try that when it is available.
-
OK Final Update! The USB Stick boots perfectly well on 6 year old Lenovo Laptop. I retried on my Toshiba with every various option in the BIOS setup but no luck. I was able to appreciate Siduction until my wife kicked me off her machine ;D . Clearly it is not your problem but thanks for all your assistance
-
you could do us a big favour - join IRC and as for a current Image for your DE - there are some new components in the maintime - such as the kernel, today a new grub arrived - so there are chances to solve this with a new build - the chances to solve this with remote analysis over the forum are not so high. And you are not alone, another user had struggles with one iso too - his stick works fine with all test machines - but refused to work on the targeted machine. So these cases are very rare, it might be that a current build will help.
And it would help us with another thing - this image will contain calamares, our new installer - and I'm happy about every machine calamares is tested on before we release it to a wider audience.
-
Nobody else has reported this problem so it must be unique to my system.
As an ex-Toshiba netbook owner running siduction, I can confirm that Toshibas can be quite a PITA for running Linux in general. Depending on how bad you need it and how hard you want to work, it is possible that if you could find an older Linux ISO that will boot and install "something", then you could change repos, delete everything you don't want except the kernel and networking, and then upgrade it to Debian and siduction. Sorry, it's probably not even worth two cents. :(
-
Thanks Dibl, All comments are welcomed, that's the great thing about forums. I am running Debian8, Mint 18 and MX16 with no problems. I have also tested many other distros (it is a hobby, sad but true). This is what makes the problem so frustrating and an obsession for me to solve :( . As an aside I have an old dekstop running Linux for years and suddenly it stopped booting any distro with a "KERNEL PANIC" message. That was what forced me to buy the Toshiba. Maybe I will dig it up and try Siduction on that.
Cheers
-
If you have Debian stable running on that Toshiba, it should be possible to "dd" it to a suitably-sized ( i.e. larger) partition, then you will need to use gparted to enlarge the filesystem to fill the partition, possibly need to reinstall grub, and then you can simply change the repos to unstable, add siduction repos, and full-upgrade it.
"Should" being the dangerous assumption here. But you said it was your hobby, so ..... ;D
-
I already had an image of Debian8 Cinnamon so I restored it to a spare partition and changed the repos. The upgrade seemd to go without fatal errors but there were some messages about missing certificates, so I guess some non-free software may not have been included. I could boot into the new systems but the desktop was a mixture of Cinnamon with Siduction dialogs which did no display components such as text boxes and buttons. They existed because I could click an empty space where the button should be and they operated as expected.
I won't take this any further for now. I will wait for Siduction Cinnamon to be released.
-
Not good, downloaded LXQT amd64 put it on a usb (like I always do with Debian based dists and never had a problem) all I got was a blue screen with a video error saying it can not display.
Different but similar stock Dell computer, different display, same thing.
Tried LXDE and same exact result. Both iso files check ok with sha256 and md5
Burned an image of Q4OS 2.3.1 (this is a Stretch based system with systemd) it run fine on the same stick.
I think tails runs on calamares too lately and it works fine on the same machines.
Then your forum nearly always runs into an error on the first link, it must be refreshed to display a page, which means "save your note elsewhere or you lose it after the first click".
Help!
-
Ohh.. here is a clue
If I boot up debian and then plug the stick on this is what it tells me (never seen this with an iso before)
Error mounting /dev/sdb3 at /media/roba/siduction: Command-line `mount -t "iso9660" -o "uhelper=udisks2,nodev,nosuid,uid=1002,gid=1002,iocharset=utf8,mode=0400,dmode=0500" "/dev/sdb3" "/media/roba/siduction"' exited with non-zero exit status 32: mount: wrong fs type, bad option, bad superblock on /dev/sdb3,
missing codepage or helper program, or other error
In some cases useful info is found in syslog - try
dmesg | tail or so.
-
Congratulations, glad to report that the latest Cinnamon release boots ok from USB stick. Now will try an install and give it a test run
-
Also have troubles booting up the live iso, gauge hangs half through boot process [/size]on a core2duo/intel GM965/GL960 setup like my old dell 1525. Iso flavour is xfce.
[/size]
[/size]My guess it might have something to dowith weird the kernel error "drm_kms_helper, flip_done timed out" bug I have with my install. Only way out is to use the last usuable kernel 4.7.6
[/size]
-
ok, have to take everything back, tried the lxqt iso and it now boots up.
Grepped the dmesg and it seems there's no drm_kms_helper hang while booting. (I do get this when using the same kernel version on my current install, but I'll see what kernel parameter is used vice versa and see if I can create a workaround)