Scheduled Maintenance: We are aware of an issue with Google, AOL, and Yahoo services as email providers which are blocking new registrations. We are trying to fix the issue and we have several internal and external support tickets in process to resolve the issue. Please see: viewtopic.php?t=158230
After update kernel doesn't finish boot/login
-
- Posts: 84
- Joined: 2013-02-07 19:08
After update kernel doesn't finish boot/login
After updating last night I have to use an older kernel
to boot. Am running openbox on Debian 10 with intel
driver. This might be solved by modesetting but still
needs a fix.
I login in console and .bashrc contains the following :
[[ $(tty) = "/dev/tty1" ]] && exec startx &> $HOME/startx.txt
The above has been working for years.
My startx.txt log contains this -
xf86EnableIOPorts: failed to set IOPL for I/O (Operation not permitted)
pkexec version 0.105
(II) AIGLX: Suspending AIGLX clients for VT switch
The new kernel won't continue the boot, it is kernel
4.18.0-1-amd64 #1 SMP Debian 4.18.6-1 (2018-09-06) x86_64
The older kernel will finish the boot, it is kernel
4.16.0-2-amd64 #1 SMP Debian 4.16.12-1 (2018-05-27) x86_64
Also init (1.54) to 1.55 upgrade was made last night.
Any help ? or just FYI.
to boot. Am running openbox on Debian 10 with intel
driver. This might be solved by modesetting but still
needs a fix.
I login in console and .bashrc contains the following :
[[ $(tty) = "/dev/tty1" ]] && exec startx &> $HOME/startx.txt
The above has been working for years.
My startx.txt log contains this -
xf86EnableIOPorts: failed to set IOPL for I/O (Operation not permitted)
pkexec version 0.105
(II) AIGLX: Suspending AIGLX clients for VT switch
The new kernel won't continue the boot, it is kernel
4.18.0-1-amd64 #1 SMP Debian 4.18.6-1 (2018-09-06) x86_64
The older kernel will finish the boot, it is kernel
4.16.0-2-amd64 #1 SMP Debian 4.16.12-1 (2018-05-27) x86_64
Also init (1.54) to 1.55 upgrade was made last night.
Any help ? or just FYI.
Last edited by patrick013 on 2018-11-13 23:27, edited 1 time in total.
- Head_on_a_Stick
- Posts: 14114
- Joined: 2014-06-01 17:46
- Location: London, England
- Has thanked: 81 times
- Been thanked: 132 times
Re: After update kernel doesn't finish boot
Firstly, there is no "Debian 10" (but thanks for testing!).patrick013 wrote:Am running openbox on Debian 10 with intel
driver. This might be solved by modesetting
Secondly, have you tried removing xserver-xorg-video-intel?
I don't run Debian testing but my OpenBSD -current box lost the setuid bit on the Xorg binary yesterday to plug the X hole, perhaps you are experiencing this.
Can you get to a desktop by using a display manager?
deadbang
-
- Posts: 84
- Joined: 2013-02-07 19:08
Re: After update kernel doesn't finish boot
I can boot OK using the 4.16 kernel but not the 4.18 kernel as ofHead_on_a_Stick wrote:Firstly, there is no "Debian 10" (but thanks for testing!).patrick013 wrote:Am running openbox on Debian 10 with intel
driver. This might be solved by modesetting
Secondly, have you tried removing xserver-xorg-video-intel?
I don't run Debian testing but my OpenBSD -current box lost the setuid bit on the Xorg binary yesterday to plug the X hole, perhaps you are experiencing this.
Can you get to a desktop by using a display manager?
last night. I want to use intel as the uxa AccelMethod works well
on my machine. So the machine is fully operational today.
Thanks for the reply.
- Head_on_a_Stick
- Posts: 14114
- Joined: 2014-06-01 17:46
- Location: London, England
- Has thanked: 81 times
- Been thanked: 132 times
Re: After update kernel doesn't finish boot
UXA is ancient, SNA offers much better performance and Glamor (as used by the modesetting driver) should outperform UXA also.patrick013 wrote:I want to use intel as the uxa AccelMethod works well
deadbang
Re: After update kernel doesn't finish boot
If you made it far enough to startx, then didn't the kernel finish booting? I'd think that's a good clue that one kernel can startx but another can't, but it's not a bootup problem, probably intel driver like HoaS said. Easy enought to test.
There are some files created when booting that belong to root:video and so I always add users to 'video' group. This hasn't always been necessary, but I always do it anyway. You could try that. When I use a display manager, I add that dm to the video group also.
Looking up the error "xf86EnableIOPorts: failed to set IOPL for I/O (Operation not permitted)" might help figure it out also. I run rootless X on stretch with intel graphics and haven't had one problem using modesetting driver. I will try intel driver next boot and see what happens, thanks. I have a 4.18 bpo kernel so that too will get tested.
There are some files created when booting that belong to root:video and so I always add users to 'video' group. This hasn't always been necessary, but I always do it anyway. You could try that. When I use a display manager, I add that dm to the video group also.
Code: Select all
/dev/dri$ ls -l
total 0
crw-rw----+ 1 root video 226, 0 Oct 25 12:48 card0
crw-rw---- 1 root video 226, 64 Oct 25 12:48 controlD64
crw-rw----+ 1 root video 226, 128 Oct 25 12:48 renderD128
Code: Select all
$ ls -l /usr/bin/startx
-rwxr-xr-x 1 root root 5517 Oct 18 2015 /usr/bin/startx
$ ls -l /usr/bin/xinit
-rwxr-xr-x 1 root root 19136 Oct 18 2015 /usr/bin/xinit
$ ls -l /usr/bin/X
lrwxrwxrwx 1 root root 4 Oct 25 05:19 /usr/bin/X -> Xorg
$ ls -l /usr/bin/Xorg
-rwxr-xr-x 1 root root 274 Oct 25 05:19 /usr/bin/Xorg
$ apt policy xserver-xorg-legacy
xserver-xorg-legacy:
Installed: (none)
Candidate: 2:1.19.2-1+deb9u4
Version table:
2:1.19.2-1+deb9u4 500
500 http://security.debian.org stretch/updates/main amd64 Packages
2:1.19.2-1+deb9u2 500
500 http://deb.debian.org/debian stretch/main amd64 Packages
Never used ~/.bashrc for that, why would that be better than ~/.profile on default debian installation?I login in console and .bashrc contains the following :
[[ $(tty) = "/dev/tty1" ]] && exec startx &> $HOME/startx.txt
resigned by AI ChatGPT
Re: After update kernel doesn't finish boot
not relevant to the topic, but important nonetheless.bw123 wrote:Never used ~/.bashrc for that, why would that be better than ~/.profile on default debian installation?
.bashrc is sourced each time you open a terminal, .profile (and/or other files) are sourced only in a login shell.
in other words, there's no need to test for a tty each time you open a terminal.
Re: After update kernel doesn't finish boot
yes, I was wondering why we would want to startx every time bash was invoked non-login on tty1?debiman wrote:not relevant to the topic, but important nonetheless.bw123 wrote:Never used ~/.bashrc for that, why would that be better than ~/.profile on default debian installation?
.bashrc is sourced each time you open a terminal, .profile (and/or other files) are sourced only in a login shell.
in other words, there's no need to test for a tty each time you open a terminal.
[
Code: Select all
# ~/.bashrc: executed by bash(1) for non-login shells.
that is why I added, "... on a default debian system."
resigned by AI ChatGPT
-
- Posts: 84
- Joined: 2013-02-07 19:08
Re: After update kernel doesn't finish boot
So I moved the command to .profile with no errors noted.debiman wrote:not relevant to the topic, but important nonetheless.bw123 wrote:Never used ~/.bashrc for that, why would that be better than ~/.profile on default debian installation?
.bashrc is sourced each time you open a terminal, .profile (and/or other files) are sourced only in a login shell.
in other words, there's no need to test for a tty each time you open a terminal.
#Startx Automatically place at end of .profile
if [[ -z "$DISPLAY" ]] && [[ $(tty) = /dev/tty1 ]]; then
. startx &> $HOME/startx.txt
logout
fi
...or this seems to be working fine also in .profile
exec in front is optional
exec startx &> $HOME/startx.txt
Re: After update kernel doesn't finish boot
well done!patrick013 wrote:So I moved the command to .profile with no errors noted.
a few comments:
surely that is wrong, the dot at the beginning?. startx &> $HOME/startx.txt
if that is the desired behaviour, you might better uselogout
exec startx &> $HOME/startx.txt
-
- Posts: 84
- Joined: 2013-02-07 19:08
Re: After update kernel doesn't finish boot/login
Update:
Same problem, the 4.18 upgrade kernel stops after
console login for OpenBox (Buster). If I press Ctrl-x
a couple times OpenBox will start and the computer
will finish boot OK.
Is there any significance or clue why Ctrl-x would signal
the machine to continue and let OpenBox load, etc..
Thanks
Same problem, the 4.18 upgrade kernel stops after
console login for OpenBox (Buster). If I press Ctrl-x
a couple times OpenBox will start and the computer
will finish boot OK.
Is there any significance or clue why Ctrl-x would signal
the machine to continue and let OpenBox load, etc..
Thanks
Re: After update kernel doesn't finish boot/login
i have no idea.
for me, ctrl-x does exactly nothing on a logged in console.
have you tried just waiting a while, i.e. don't touch anything?
for me, ctrl-x does exactly nothing on a logged in console.
have you tried just waiting a while, i.e. don't touch anything?