Try please
cat /var/log/syslog | grep -v atkbd |tail
short after you inserted the disc.
The -v inverts grep, so it will filter the keyborad stuff…
2 Likes
i don’t see anything there overtly related to your cd/dvd player (sr0). you could also try journalctl | grep sr0 | tail.
2 Likes
i hadn’t seen that before. quite handy
2 Likes
Googling this direction it seems these are ACPI events. I found this:
interesting fix and that such a thing (didn’t read the entire launchpad page to see if it was actually diagnosed) would present with essentially a keyboard error = a pretty good reason why diagnosing with logs can be a bit of a rabbit hole.
1 Like
I don’t really get the idea, why the BIOS want to boot from LAN, after it fails with DVD. It should go on with the next in the order: HDD.
So we need to see, something weird is going on here. A weird case might have a strange solution 
So why not?
As a last resort I’d call Ghost Busters…
Whatever I set in BIOS, I get an option when I press F12 ( boot options )
- Hard Drive
- CD/DVD/CD-RW Device
- Network
- Diagnostics
- Enter Setup
Possibly, this option is directing the boot to Network. But why skip the contents of DVD ?
1 Like
Did you try an external DVD Player?
2 Likes
I don’t have one. You mean a USB powered one, right ?
1 Like
One that is connected via USB, but not necessarily powered over USB. If you try that out, you can see if the PC accepts any type of CD/DVD, at all.
Luckily they are cheap (about 10 bucks) and you can always use one for many purposes.
1 Like
DVDs are read through Nautilus, but not booting. That is where we are stuck.
Thanks for the tip.
1 Like
That’s why you should check if the error is hardware-related. Which could be achieved by using an entirely different device as an interface for the DVDs.
2 Likes
~$ cat /var/log/syslog | grep -v atkbd |tail
Feb 12 21:04:07 my_PC rtkit-daemon[1501]: Supervising 4 threads of 2 processes of 1 users.
Feb 12 21:04:07 my_PC rtkit-daemon[1501]: Supervising 4 threads of 2 processes of 1 users.
Feb 12 21:04:13 my_PC dbus-daemon[1351]: [session uid=1000 pid=1351] Activating service name='org.gnome.ChromeGnomeShell' requested by ':1.45' (uid=1000 pid=1931 comm="/usr/bin/python3 /usr/bin/chrome-gnome-shell /usr/" label="unconfined")
Feb 12 21:04:13 my_PC rtkit-daemon[1501]: Supervising 4 threads of 2 processes of 1 users.
Feb 12 21:04:14 my_PC rtkit-daemon[1501]: message repeated 3 times: [ Supervising 4 threads of 2 processes of 1 users.]
Feb 12 21:04:14 my_PC upowerd[1537]: treating change event as add on /sys/devices/LNXSYSTM:00/LNXSYBUS:00/PNP0C0A:00/power_supply/BAT0
Feb 12 21:04:14 my_PC dbus-daemon[1351]: [session uid=1000 pid=1351] Successfully activated service 'org.gnome.ChromeGnomeShell'
Feb 12 21:04:15 my_PC rtkit-daemon[1501]: Supervising 4 threads of 2 processes of 1 users.
Feb 12 21:04:20 my_PC rtkit-daemon[1501]: message repeated 3 times: [ Supervising 4 threads of 2 processes of 1 users.]
Feb 12 21:04:25 my_PC upowerd[1537]: treating change event as add on /sys/devices/LNXSYSTM:00/LNXSYBUS:00/PNP0C0A:00/power_supply/BAT0
1 Like
I tried this command, but nothing happens. The cursor moves one line down and stays there infinitely.
1 Like
rtkit is related to pulseaudio (my system shows similar messages and a web search yielded results suggesting it isn’t any kind of error) and that upowerd message is probably related to the acpi/kbd error.
agreed that this as well as (when/if you get access to another dvd) trying a different burn/image write method as suggested by @kovacslt are two ways to try and eliminate a couple of other possible errors.
Finally the command gave this output
~$ journalctl | grep sr0 | tail
Feb 12 19:03:06 my_PC kernel: sr 4:0:0:0: [sr0] scsi3-mmc drive: 24x/24x writer dvd-ram cd/rw xa/form2 cdda tray
Feb 12 19:03:06 my_PC kernel: sr 4:0:0:0: Attached scsi CD-ROM sr0
Feb 12 19:07:21 my_PC kernel: sr 4:0:0:0: [sr0] scsi3-mmc drive: 24x/24x writer dvd-ram cd/rw xa/form2 cdda tray
Feb 12 19:07:21 my_PC kernel: sr 4:0:0:0: Attached scsi CD-ROM sr0
Feb 12 19:48:03 my_PC kernel: sr 4:0:0:0: [sr0] scsi3-mmc drive: 24x/24x writer dvd-ram cd/rw xa/form2 cdda tray
Feb 12 19:48:03 my_PC kernel: sr 4:0:0:0: Attached scsi CD-ROM sr0
Feb 12 21:00:20 my_PC udisksd[978]: Mounted /dev/sr0 at /media/my_PC/Ubuntu 18.04.3 LTS amd64 on behalf of uid 1000
Feb 12 21:02:28 my_PC kernel: sr 4:0:0:0: [sr0] scsi3-mmc drive: 62x/62x writer dvd-ram cd/rw xa/form2 cdda tray
Feb 12 21:02:28 my_PC kernel: sr 4:0:0:0: Attached scsi CD-ROM sr0
Feb 12 21:03:41 my_PC udisksd[998]: Mounted /dev/sr0 at /media/my_PC/Ubuntu 18.04.3 LTS amd64 on behalf of uid 1000it is nothing definitive, but i went through my journalctl history for the last couple of days to find as many “Attached” entries as your system shows in two hours.
Does that mean there is some hardware error ?
If the DVDs’ integrities are verified and you tried to boot off at least 3 different DVDs that work on other computers but not this one, then you need to check the hardware.
Now, if you have a fancy laptop or just a simple computer, you might either
- insert a second HDD into the laptop with a live medium “burnt” onto it and try to boot off that one
- you could ideally maybe stick it into the SATA connector, the DVD player uses and see if you can boot a live medium off of this HDD that uses the same connection (however you would need to remove the DVD player and depending on the Laptop model this could result in a small to a large amount of disassembling)
or - unplug the DVD player within your computer and plug an HDD into the same SATA connector that the DVD player used and try to boot a live medium off of this HDD (no need for disassembling anything when using a PC)
(P.S.: This is another example, why PCs are superior. If you have a Laptop, usually you’re done or the repair is not worth it or too complicated. Whereas having a PC gives you all the opportunities to tinker with its insides…)