Is there any update on this Bug?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1256949
Title:
Dell Latitude E5420 doesn't boot if killswitch is turned to radio
off
To manage notifications about
Is there any update on this Bug?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1256949
Title:
Dell Latitude E5420 doesn't boot if killswitch is turned to radio
off
To manage notifications about
[Expired for upstart (Ubuntu) because there has been no activity for 60
days.]
** Changed in: upstart (Ubuntu)
Status: Incomplete = Expired
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
[Expired for linux (Ubuntu) because there has been no activity for 60
days.]
** Changed in: linux (Ubuntu)
Status: Incomplete = Expired
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1256949
Sounds like the original driver had caused the kernel to become totally
unresponsive. Glad the problem has been resolved for you.
Please could you attach the output of sudo lshw -c network to this bug
so we can see the details of your broadcom wireless card?
Thanks!
--
You received this bug
** Attachment added: lshw output
https://bugs.launchpad.net/ubuntu/+source/upstart/+bug/1256949/+attachment/3955643/+files/lshw_network.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1256949
Here are the results:
1.The Systems does not react while freezed to
alt + sysrq + s
alt + sysrq + u
alt + sysrq + b
no led is blinking the caps-lock led is not reacting
2. using the killswitch while running works as you would expect it (wifi and
bluetooth
ok after installing the broadcom-STA-wifi-driver the problem is
completly gone. so finaly it turn out to be a driver issue.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1256949
Title:
Dell
At this point, I'd suggest temporarily disabling the network-manager
upstart job (which will of course disable networking):
echo manual | sudo tee /etc/init/network-manager.override
Does this give a reliable boot? To undo this change simply delete the
override file:
sudo rm
Other things to try...
When the system freezes:
1) Can you still toggle the caps-lock light by pressing the caps-lock key?
2) Can you reboot by holding down *all* of the following keys combos (do all of
them):
alt + sysrq + s
alt + sysrq + u
alt + sysrq + b
Also, would it be
@meamy: Please can you try booting again with --debug - your attachment
in #14 looks like you booted with --verbose instead?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1256949
Title:
Dell
@meamy: if you boot the machine with the kill switch on and once booted
switch it to off does the machine cope with that ok?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1256949
Title:
Dell
Another thought - can you confirm that this system is being booted
without any external devices being plugged into it (ie no extermal
mouse, keyboard, monitor, printer, etc)?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
ok thanks I will test this as sone as I find some free time (so maybe
tomorow)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1256949
Title:
Dell Latitude E5420 doesn't boot if killswitch is turned
@meamy - ok, I am starting to suspect this is either a kernel or
graphics card issue. Adding linux to bug.
** Also affects: linux (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
@james
Ok i got the shell (/bin/sh) and was able to start getty (/sbin/getty -8 38400
tty8 )and to switch to tty8 (I was not able to login, but i guess thats
correct).
after I enter your second command the init process starts as usal and after a
while the system freeze (meaning i could no
@meamy - I don't think putting apport/dropbear into the initramfs is a
good idea, no. Please can you boot without 'quiet' and without 'splash'
but add '--debug' and attach a photo of the screen.
What do you mean that you could never reach the login screen with
crtl+alt+f8?:
1) Did the system
@meamy - In comment #6, I explain how to start a tty extremely early.
Please try this and let me know what happens.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1256949
Title:
Dell Latitude E5420
@james I did that but it never startet (or to be 100% correct I could
never reach it with crtl+alt+f8), the startup behaivor didnt changed
from what i cloud see (the point where it stops on every reboot is
always a bit diffrent).
Unfortunatly at the moment all Laptops are with our coustomers but
Hi James
we tryed both things but they didnt worked. It is unpredictabel how fare
upstarts boots but out of 10 trys it never
came to the point were it starts the ttys. Unfortunatly I did not finde any way
to configure upstart that way that it trys to start the ttys as early as
possible.
We
** Changed in: upstart (Ubuntu)
Status: New = Incomplete
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1256949
Title:
Dell Latitude E5420 doesn't boot if killswitch is turned to radio
off
Hi Rouven - thanks for the screenshot. No signs of failures there.
Please can you try a couple of things:
1) Let the system boot as far as it can, then try pressing
control+alt+F7 to see if this switches to the greeter to allow you to
login normally.
2) Please try installing the tty8.conf job
Hey James Daniel,
thanks for the quick response!
The boot behaviour doesn't change unfortunately, if i switch off
splash and quiet at the grub cmd line.
See screenshot attached
** Attachment added: Screenshot of the boot screen
** Attachment added: OCS Inventory file
https://bugs.launchpad.net/ubuntu/+bug/1256949/+attachment/3921479/+files/WS265-2013-11-21-12-17-37.xml
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
** Attachment added: syslog when running into the bug (radio: off)
https://bugs.launchpad.net/ubuntu/+bug/1256949/+attachment/3921480/+files/syslog_bug.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
** Attachment added: syslog when boot works fine (radio: on)
https://bugs.launchpad.net/ubuntu/+bug/1256949/+attachment/3921481/+files/syslog_without_bug.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Thank you for taking the time to report this bug and helping to make
Ubuntu better. It seems that your bug report is not filed about a
specific source package though, rather it is just filed against Ubuntu
in general. It is important that bug reports be filed about source
packages so that people
cyphermox this looks like something is stuck in the boot, the device does
boot file but some upstart job appears stuck
cyphermox I see NM didn't even get fired, anyway, that I can notice
** Package changed: ubuntu = upstart (Ubuntu)
--
You received this bug notification because you are a
Hi Daniel - A couple of initial questions...
1) Has this problem just started? If so, what changed?
2) How far into the boot does it get?
Can you try removing splash and quiet from the boot command-line.
Also, you could try copying tty8.conf from
1) It's a fresh 12.04.3 install.
2) See the attached syslog files. It appears to get stuck some time during the
network bits.
Rouven: can you try what James suggested in the comment above?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to
30 matches
Mail list logo
