Siduction Forum
Siduction Forum => Software - Support => Topic started by: Dachs on 2014/08/15, 13:49:47
-
Hi.
I did a system upgrade and then shut down my laptop about 3 weeks ago before going on holiday. When I start up the screen boots to a blank screen with a flashing cursor, I checked the bios and the boot order starts HDD, I guess the next step is it use live cd but what is the best thing to use? should I use a siduction live cd or a recovery cd like systemRescueCd, if I use the siduction cd what do I do when I'm in? I've used recovery cd to fix the boot register on windows in the past but I'm sure this is different, any other ideas?
Grüß
-
Blinkender cursor kann vieles sein - wie wäre es mit ein paar ergänzenden Informationen, z.B. Graka, verwendeter Treiber etc?
bis dahin erklären wir mal den Boot für ganz normal - im Bootmenu 'e' drücken und in der Kernelzeile eine 3 ans Ende sollte zumindest den Textmodus erreichen. Und von da kann man dann ganz bequem X reparieren.
-
Blinking cursor on black screen could also be VT7 and login-manager not started. Probably dist-upgrade was incomplete or xorg-issues (as you said is was 3 weeks ago).
Can you switch to VT1 with Alt+F1 or at least Ctrl+Alt+F1? Login as root, apt-get install -f and update/dist-upgrade again (be aware that there are issues today regarding ongoing perl-transition, see forum section Upgrade Warnings).
-
melmaker Vielen Dank für Ihre Antwort,
I've managed to boot into my siduction partition using a superprub 2 live cd and I did I system upgrade but this has not fixed to problem, it still boots with the flashing cursor but this time it gets stuck in a loop of rebooting and blinking. do you think it could be a problem with GRUB, would reinstalling GRUB help?
thanks, and sorry for the delay in reply,
cpu:
Intel(R) Core(TM)2 Duo CPU T6570 @ 2.10GHz, 2100 MHz
Intel(R) Core(TM)2 Duo CPU T6570 @ 2.10GHz, 2100 MHz
keyboard:
/dev/input/event0 AT Translated Set 2 keyboard
mouse:
/dev/input/mice ALPS PS/2 Device
/dev/input/mice AlpsPS/2 ALPS GlidePoint
graphics card:
Intel Mobile 4 Series Chipset Integrated Graphics Controller
Intel Mobile 4 Series Chipset Integrated Graphics Controller
sound:
Intel 82801I (ICH9 Family) HD Audio Controller
storage:
Intel 82801IBM/IEM (ICH9M/ICH9M-E) 4 port SATA Controller [AHCI mode]
network:
wlan0 Broadcom BCM4312 802.11b/g LP-PHY
eth0 Lenovo IdeaPad S10e
network interface:
eth0 Ethernet network interface
lo Loopback network interface
wlan0 WLAN network interface
disk:
/dev/sda WDC WD3200BEVT-2
partition:
/dev/sda1 Partition
/dev/sda2 Partition
/dev/sda3 Partition
/dev/sda5 Partition
cdrom:
/dev/sr0 HL-DT-ST DVDRAM GT30N
usb controller:
Intel 82801I (ICH9 Family) USB UHCI Controller #4
Intel 82801I (ICH9 Family) USB UHCI Controller #5
Intel 82801I (ICH9 Family) USB UHCI Controller #6
Intel 82801I (ICH9 Family) USB2 EHCI Controller #2
Intel 82801I (ICH9 Family) USB UHCI Controller #1
Intel 82801I (ICH9 Family) USB UHCI Controller #2
Intel 82801I (ICH9 Family) USB UHCI Controller #3
Intel 82801I (ICH9 Family) USB2 EHCI Controller #1
bios:
BIOS
bridge:
Intel Mobile 4 Series Chipset Memory Controller Hub
Intel 82801I (ICH9 Family) PCI Express Port 1
Intel 82801I (ICH9 Family) PCI Express Port 2
Intel 82801I (ICH9 Family) PCI Express Port 3
Intel 82801I (ICH9 Family) PCI Express Port 4
Intel 82801I (ICH9 Family) PCI Express Port 6
Intel 82801 Mobile PCI Bridge
Intel ICH9M LPC Interface Controller
hub:
Linux 3.16-1.towo-siduction-amd64 uhci_hcd UHCI Host Controller
Linux 3.16-1.towo-siduction-amd64 uhci_hcd UHCI Host Controller
Linux 3.16-1.towo-siduction-amd64 uhci_hcd UHCI Host Controller
Linux 3.16-1.towo-siduction-amd64 uhci_hcd UHCI Host Controller
Linux 3.16-1.towo-siduction-amd64 ehci_hcd EHCI Host Controller
Linux 3.16-1.towo-siduction-amd64 uhci_hcd UHCI Host Controller
Linux 3.16-1.towo-siduction-amd64 ehci_hcd EHCI Host Controller
Linux 3.16-1.towo-siduction-amd64 uhci_hcd UHCI Host Controller
memory:
Main Memory
unknown:
FPU
DMA controller
PIC
Timer
Keyboard controller
Intel 82801I (ICH9 Family) SMBus Controller
Intel 82801I (ICH9 Family) Thermal Subsystem
/dev/input/event9 Feiya Lenovo EasyCamera
-
If you are able to boot into your system with supergrub, you propably have nomodeset or i915.modeset=0 in your grub.cfg.
-
I couldn't find any reference to nomodeset or i915 in the grub. cfg. does this tell you anything? should I post more of the file?
### BEGIN /etc/grub.d/00_header ###
if [ -s $prefix/grubenv ]; then
set have_grubenv=true
load_env
fi
if [ "${next_entry}" ] ; then
set default="${next_entry}"
set next_entry=
save_env next_entry
set boot_once=true
else
set default="0"
fi
if [ x"${feature_menuentry_id}" = xy ]; then
menuentry_id_option="--id"
else
menuentry_id_option=""
fi
export menuentry_id_option
if [ "${prev_saved_entry}" ]; then
set saved_entry="${prev_saved_entry}"
save_env saved_entry
set prev_saved_entry=
save_env prev_saved_entry
set boot_once=true
fi
function savedefault {
if [ -z "${boot_once}" ]; then
saved_entry="${chosen}"
save_env saved_entry
fi
}
function load_video {
if [ x$feature_all_video_module = xy ]; then
insmod all_video
else
insmod efi_gop
insmod efi_uga
insmod ieee1275_fb
insmod vbe
insmod vga
insmod video_bochs
insmod video_cirrus
fi
}
if [ x$feature_default_font_path = xy ] ; then
font=unicode
else
insmod part_gpt
insmod ext2
set root='hd0,gpt3'
if [ x$feature_platform_search_hint = xy ]; then
search --no-floppy --fs-uuid --set=root --hint-bios=hd0,gpt3 --hint-efi=hd0,gpt3 --hint-baremetal=ahci0,gpt3 1d56e351-6572-483c-885a-76c5d8b4c8a5
else
search --no-floppy --fs-uuid --set=root 1d56e351-6572-483c-885a-76c5d8b4c8a5
fi
font="/usr/share/grub/unicode.pf2"
fi
if loadfont $font ; then
set gfxmode=auto
load_video
insmod gfxterm
set locale_dir=$prefix/locale
set lang=en_GB
insmod gettext
fi
terminal_output gfxterm
if [ "${recordfail}" = 1 ] ; then
set timeout=-1
else
if [ x$feature_timeout_style = xy ] ; then
set timeout_style=menu
set timeout=5
# Fallback normal timeout code in case the timeout_style feature is
# unavailable.
else
set timeout=5
fi
fi
### END /etc/grub.d/00_header ###
### BEGIN /etc/grub.d/05_debian_theme ###
set menu_color_normal=cyan/blue
set menu_color_highlight=white/blue
### END /etc/grub.d/05_debian_theme ###
### BEGIN /etc/grub.d/10_linux ###
function gfxmode {
set gfxpayload="${1}"
}
set linux_gfx_mode=
export linux_gfx_mode
menuentry 'siduction 2013.2.1 december (kde) GNU/Linux' --class siduction --class gnu-linux --class gnu --class os $menuentry_id_option 'gnulinux-simple-1d56e351-6572-483c-885a-76c5d8b4c8a5' {
load_video
insmod gzio
insmod part_gpt
insmod ext2
set root='hd0,gpt3'
-
Hello Dachs,
The menuentry for your siduction seems to be cut off. I hope it's only a Copy 'n Paste Error?
also " set linux_gfx_mode= " looks weird. Why is there no value set to the variable?
greetings
musca
-
Hi Musca
no copy and past error but just in case here it is again, is it safe to past the whole file or would that be a security risk? I have no idea why no value is set to the variable to be honest, could that be part of my problem?
thanks
### BEGIN /etc/grub.d/00_header ###
if [ -s $prefix/grubenv ]; then
set have_grubenv=true
load_env
fi
if [ "${next_entry}" ] ; then
set default="${next_entry}"
set next_entry=
save_env next_entry
set boot_once=true
else
set default="0"
fi
if [ x"${feature_menuentry_id}" = xy ]; then
menuentry_id_option="--id"
else
menuentry_id_option=""
fi
export menuentry_id_option
if [ "${prev_saved_entry}" ]; then
set saved_entry="${prev_saved_entry}"
save_env saved_entry
set prev_saved_entry=
save_env prev_saved_entry
set boot_once=true
fi
function savedefault {
if [ -z "${boot_once}" ]; then
saved_entry="${chosen}"
save_env saved_entry
fi
}
function load_video {
if [ x$feature_all_video_module = xy ]; then
insmod all_video
else
insmod efi_gop
insmod efi_uga
insmod ieee1275_fb
insmod vbe
insmod vga
insmod video_bochs
insmod video_cirrus
fi
}
if [ x$feature_default_font_path = xy ] ; then
font=unicode
else
insmod part_gpt
insmod ext2
set root='hd0,gpt3'
if [ x$feature_platform_search_hint = xy ]; then
search --no-floppy --fs-uuid --set=root --hint-bios=hd0,gpt3 --hint-efi=hd0,gpt3 --hint-baremetal=ahci0,gpt3 1d56e351-6572-483c-885a-76c5d8b4c8a5
else
search --no-floppy --fs-uuid --set=root 1d56e351-6572-483c-885a-76c5d8b4c8a5
fi
font="/usr/share/grub/unicode.pf2"
fi
if loadfont $font ; then
set gfxmode=auto
load_video
insmod gfxterm
set locale_dir=$prefix/locale
set lang=en_GB
insmod gettext
fi
terminal_output gfxterm
if [ "${recordfail}" = 1 ] ; then
set timeout=-1
else
if [ x$feature_timeout_style = xy ] ; then
set timeout_style=menu
set timeout=5
# Fallback normal timeout code in case the timeout_style feature is
# unavailable.
else
set timeout=5
fi
fi
### END /etc/grub.d/00_header ###
### BEGIN /etc/grub.d/05_debian_theme ###
set menu_color_normal=cyan/blue
set menu_color_highlight=white/blue
### END /etc/grub.d/05_debian_theme ###
### BEGIN /etc/grub.d/10_linux ###
function gfxmode {
set gfxpayload="${1}"
}
set linux_gfx_mode=
export linux_gfx_mode
menuentry 'siduction 2013.2.1 december (kde) GNU/Linux' --class siduction --class gnu-linux --class gnu --class os $menuentry_id_option 'gnulinux-simple-1d56e351-6572-483c-885a-76c5d8b4c8a5' {
load_video
insmod gzio
insmod part_gpt
insmod ext2
set root='hd0,gpt3'
if [ x$feature_platform_search_hint = xy ]; then
-
Hello Dachs,
The menuentry for your siduction seems to be cut off. I hope it's only a Copy 'n Paste Error?
also " set linux_gfx_mode= " looks weird. Why is there no value set to the variable?
greetings
musca
I don't have a value set either, actually, none of my installs do.
I use 40_custom, but that shouldn't matter
### END /etc/grub.d/05_debian_theme ###
### BEGIN /etc/grub.d/10_linux ###
function gfxmode {
set gfxpayload="${1}"
}
set linux_gfx_mode=
export linux_gfx_mode
menuentry 'siduction 2013.2.0 paintitblack (kde) GNU/Linux' --class siduction --class gnu-linux --class gnu --class os $menuentry_id_option 'gnulinux-simple-db14072c-79bf-4a93-a269-eebeebc77c5a' {
load_video
insmod gzio
insmod part_msdos
insmod ext2
set root='hd0,msdos3'
if [ x$feature_platform_search_hint = xy ]; then
search --no-floppy --fs-uuid --set=root --hint-bios=hd0,msdos3 --hint-efi=hd0,msdos3 --hint-baremetal=ahci0,msdos3 --hint='hd0,msdos3' db14072c-79bf-4a93-a269-eebeebc77c5a
else
search --no-floppy --fs-uuid --set=root db14072c-79bf-4a93-a269-eebeebc77c5a
fi
echo 'Loading Linux 3.16-1.towo-siduction-amd64 ...'
linux /boot/vmlinuz-3.16-1.towo-siduction-amd64 root=UUID=db14072c-79bf-4a93-a269-eebeebc77c5a ro quiet
echo 'Loading initial ramdisk ...'
initrd /boot/initrd.img-3.16-1.towo-siduction-amd64
}
-
... should I post more of the file? ...
Yes please!! ??? To debug errors normally as much information as possible is needed, so we want to see the whole content of /boot/grub/grub.cfg, there are no secrets hidden within. If you look again at the first paste you gave us it ends with
set root='hd0,gpt3'
Your next paste ends with
set root='hd0,gpt3'
if [ x$feature_platform_search_hint = xy ]; then
so one more line, interrupted in the very middle of an {if;then}, and possibly the most interesting information is in the lines you have not posted yet.
Additionally the output of 'blkid' to see Partitions/UUIDs might be interesting. Are you able to boot siduction into rescue.target?
-
Hi der-bud the file was too big to paste so i have attached it, here is the output from blkid, I have Ubuntu on the partition labelled 'Ferdora' and siduction on sda2 and a data partition on sda5. hope this sheds some light on the problem, thanks for all the help so far.
root@cheekybadger:~# blkid
/dev/sr0: LABEL="ISOIMAGE" TYPE="iso9660"
/dev/sda1: UUID="bbd8e2eb-54de-46f2-9a49-52c7102abe16" TYPE="swap"
/dev/sda2: UUID="24226c50-924f-4a0b-9013-22b795e2cd91" TYPE="ext4"
/dev/sda3: LABEL="_Fedora-15-Beta-" UUID="1d56e351-6572-483c-885a-76c5d8b4c8a5" TYPE="ext4"
/dev/sda5: LABEL="data" UUID="dd529d7b-012d-4b9f-95ad-a63a31f58b85" TYPE="ext4"
-
Hello Dachs,
the UUID is wrong. Your grub.cfg points siduction to the partition with the "_Fedora-15-Beta" label.
greetings
musca
-
Hi musca, thanks for checking it, what should I edit it to?
-
Hello Dachs,
you said your siduction lives on /dev/sda2 and
your blkid says /dev/sda2: UUID="24226c50-924f-4a0b-9013-22b795e2cd91" TYPE="ext4"
so, the menuentry for siduction in your grub.cfg should refer to this UUID.
But simply changing this file will not be sufficient, because there is this warning in grub.cfg:
#
# DO NOT EDIT THIS FILE
#
# It is automatically generated by grub-mkconfig using templates
# from /etc/grub.d and settings from /etc/default/grub
#
The real question is: Why was your grub.cfg automatically created with a wrong UUID?
greetings
musca
-
Hi musca
sorry for the delay, after some head scratching I can't think why it was changed I haven't been playing around with the file, It happened after a system upgrade, could it possibly be the result of a grub update?I was having some problems with my other kubuntu/ubuntu partition as well problems with the login and graphics driver but I don't think it should affect the grub on this partition, before I chain-loaded aptosid using grub from the kubuntu partition but when I switched to siduction I did a fresh install using the siduction grub, I don't suppose any of this is relevant though!
cheers
Dachs
-
on my system it was exactly the same:
UUID has changed.
And i found out the reason:
First partition: Win-XP
Sec. partition: aptosid
third.partition: siduction
after my d-u in june or so ... the grub config has changed: because the 3.partition was suddenly the main system after d-u.:
"update-grub" only works from 3.part: siduction
...last year the main-system was the second-partition: update-grub works only from 2.part: aptosid
so i decided to manage "update-grub" from my admin-system: siduction (partition-3) only.
and: in june 2014 i found out: UUID has changed so i had to edit fstab in 3.partition and all was fine. (it was the time systemd journal found out that my system-time and bios-time was windows time :) )
-
Problem solved with recent dist-upgrade ;-P
a big thanks to everyone for their help!
ps. this seems like a stupid question but how do I mark the topic as solved not just the reply...
-
Edit your first Post. There you could change the thread title too