Author Topic: problem with k3b and HAL Daemon  (Read 2608 times)

Offline SuperKev

  • Full Member
  • ***
  • Posts: 181
problem with k3b and HAL Daemon
« on: May 31, 2010, 02:15:12 PM »
Just installed 2010 a few days ago (thanks OP!!) and part of the problem was that I could not boot from the DVD-ROM so I had to do it a much more complicated way with help from OP.

Today I wanted to burn an .iso using k3b as I always had and I get this error message:

No optical drive found.
K3b did not find any optical device in your system.
Solution: Make sure HAL daemon is running, it is used by K3b for finding devices.


Tried the terminal and got this output:

[root@localhost ~]# ls -l /dev |grep cdrom
lrwxrwxrwx  1 root  root           8 2010-05-30 01:01 cdrom -> /dev/sr0


Checked in the PCC and I am showing no DVD-ROM device-- not sure where to go from here.

Any ideas? Thanks!

Offline SuperKev

  • Full Member
  • ***
  • Posts: 181
Re: problem with k3b and HAL Daemon
« Reply #1 on: May 31, 2010, 04:32:19 PM »
After a little research, could this be a problem with the newer kernel in v2010 and IDE drives?

Offline Mark342

  • Sr. Member
  • ****
  • Posts: 334
Re: problem with k3b and HAL Daemon
« Reply #2 on: May 31, 2010, 04:33:33 PM »
Seems logical, try using an older kernel (install it with synaptic).
Anything worth doing is worth overdoing.

Registered Linux user #493318
Register yourself here: Linux Counter

Offline Old-Polack

  • Administrator
  • Super Villain
  • *****
  • Posts: 11540
  • ----IOFLU----
Re: problem with k3b and HAL Daemon
« Reply #3 on: May 31, 2010, 05:41:51 PM »
After a little research, could this be a problem with the newer kernel in v2010 and IDE drives?

Could be a problem of a module not being loaded; try

[root@localhost ~]# lspci |grep -i ide             <Enter>

so we can see what IDE controller you have.

Post your results.
Old-Polack

Of what use be there for joy, if not for the sharing thereof?



Lest we forget...

Offline SuperKev

  • Full Member
  • ***
  • Posts: 181
Re: problem with k3b and HAL Daemon
« Reply #4 on: May 31, 2010, 05:49:56 PM »
[root@localhost ~]# lspci |grep -i ide
00:02.5 IDE interface: Silicon Integrated Systems [SiS] 5513 [IDE] (rev d0)
[root@localhost ~]#

Offline Old-Polack

  • Administrator
  • Super Villain
  • *****
  • Posts: 11540
  • ----IOFLU----
Re: problem with k3b and HAL Daemon
« Reply #5 on: May 31, 2010, 06:05:43 PM »
[root@localhost ~]# lspci |grep -i ide
00:02.5 IDE interface: Silicon Integrated Systems [SiS] 5513 [IDE] (rev d0)
[root@localhost ~]#


Try;

[root@localhost ~]# modprobe pata_sis                 <Edit>

[root@localhost ~]# fdisk -l               <Enter>

Post your results.
Old-Polack

Of what use be there for joy, if not for the sharing thereof?



Lest we forget...

Offline SuperKev

  • Full Member
  • ***
  • Posts: 181
Re: problem with k3b and HAL Daemon
« Reply #6 on: May 31, 2010, 06:14:51 PM »
[root@localhost ~]# modprobe pata_sis
[root@localhost ~]# fdisk -l 

Disk /dev/sda: 30.8 GB, 30758289408 bytes
255 heads, 63 sectors/track, 3739 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes
Disk identifier: 0x8f800000

   Device Boot      Start         End      Blocks   Id  System
/dev/sda1   *           1        1912    15358108+  83  Linux
/dev/sda2            1913        1928      128520   83  Linux
/dev/sda3            1929        2166     1911735   82  Linux swap / Solaris
/dev/sda4            2167        3695    12281692+  83  Linux

Disk /dev/sdb: 40.0 GB, 40020664320 bytes
16 heads, 63 sectors/track, 77545 cylinders
Units = cylinders of 1008 * 512 = 516096 bytes
Disk identifier: 0x2a5815e1

   Device Boot      Start         End      Blocks   Id  System
/dev/sdb1   *           1       77535    39077608+  83  Linux
[root@localhost ~]#

Offline Old-Polack

  • Administrator
  • Super Villain
  • *****
  • Posts: 11540
  • ----IOFLU----
Re: problem with k3b and HAL Daemon
« Reply #7 on: May 31, 2010, 07:07:13 PM »
[root@localhost ~]# modprobe pata_sis
[root@localhost ~]# fdisk -l 

Disk /dev/sda: 30.8 GB, 30758289408 bytes
255 heads, 63 sectors/track, 3739 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes
Disk identifier: 0x8f800000

   Device Boot      Start         End      Blocks   Id  System
/dev/sda1   *           1        1912    15358108+  83  Linux
/dev/sda2            1913        1928      128520   83  Linux
/dev/sda3            1929        2166     1911735   82  Linux swap / Solaris
/dev/sda4            2167        3695    12281692+  83  Linux

Disk /dev/sdb: 40.0 GB, 40020664320 bytes
16 heads, 63 sectors/track, 77545 cylinders
Units = cylinders of 1008 * 512 = 516096 bytes
Disk identifier: 0x2a5815e1

   Device Boot      Start         End      Blocks   Id  System
/dev/sdb1   *           1       77535    39077608+  83  Linux
[root@localhost ~]#


Are either of these drives IDE drives? If not, are any of your hard drives IDE? If only the optical drives are IDE, check In PCC --> Hardware --> Browse and configure hardware to see if they are now shown. If so, does k3b now see them?
Old-Polack

Of what use be there for joy, if not for the sharing thereof?



Lest we forget...

Offline SuperKev

  • Full Member
  • ***
  • Posts: 181
Re: problem with k3b and HAL Daemon
« Reply #8 on: May 31, 2010, 07:31:23 PM »
Yes, both my HDD and the optical drive is IDE as my linux box is using a bit older hardware. Everything worked fine with v2009. I did notice output from one CLI command I input the optical seemed to be listed as sr0, I don't know if that has any significance or not.

Optical does not show up in PCC and k3b does not detect it.

Offline Old-Polack

  • Administrator
  • Super Villain
  • *****
  • Posts: 11540
  • ----IOFLU----
Re: problem with k3b and HAL Daemon
« Reply #9 on: May 31, 2010, 08:18:25 PM »
[root@localhost ~]#
Yes, both my HDD and the optical drive is IDE as my linux box is using a bit older hardware. Everything worked fine with v2009. I did notice output from one CLI command I input the optical seemed to be listed as sr0, I don't know if that has any significance or not.

Optical does not show up in PCC and k3b does not detect it.

[root@localhost ~]# lsmod |grep sis              <Enter>

I want to see what else is associated with pata_sis.
Old-Polack

Of what use be there for joy, if not for the sharing thereof?



Lest we forget...

Offline SuperKev

  • Full Member
  • ***
  • Posts: 181
Re: problem with k3b and HAL Daemon
« Reply #10 on: May 31, 2010, 08:26:55 PM »
[root@localhost ~]# lsmod |grep sis
i2c_sis96x              2784  0
i2c_sis630              3998  0
sis900                 14568  0
i2c_core               18387  3 nvidia,i2c_sis96x,i2c_sis630
mii                     3885  1 sis900
sis5513                 5679  0
ide_core               85164  4 ide_generic,ide_pci_generic,sis5513,ide_gd_mod
pata_sis                7759  5
libata                143965  3 ata_generic,pata_acpi,pata_sis
[root@localhost ~]#

Offline Old-Polack

  • Administrator
  • Super Villain
  • *****
  • Posts: 11540
  • ----IOFLU----
Re: problem with k3b and HAL Daemon
« Reply #11 on: May 31, 2010, 09:17:25 PM »
[root@localhost ~]# lsmod |grep sis
i2c_sis96x              2784  0
i2c_sis630              3998  0
sis900                 14568  0
i2c_core               18387  3 nvidia,i2c_sis96x,i2c_sis630
mii                     3885  1 sis900
sis5513                 5679  0
ide_core               85164  4 ide_generic,ide_pci_generic,sis5513,ide_gd_mod
pata_sis                7759  5
libata                143965  3 ata_generic,pata_acpi,pata_sis
[root@localhost ~]#

Boot to the live session, and run fdisk -l to see if any other drives show. I realize there was the problem even in the live session, of not seeing the burned disk, but check in PCC to see if the optical drive shows at all.

Do you still have the old 2009 liveCD? If so, you could do a full lsmod, save it to a file in the new installation's /home/kevin directory.

[root@localhost ~]# mkdir /here             <Enter>

[root@localhost ~]# mount LABEL=home /here          <Enter>

[root@localhost ~]# lsmod > /here/kevin/2009-lsmod      <Enter>

When back in the installed OS, the same basic command could be issued;

[root@localhost ~]# lsmod > /home/kevin/2010-lsmod      <Enter>

then the two files could be compared.
« Last Edit: December 21, 2011, 06:20:27 PM by old-polack »
Old-Polack

Of what use be there for joy, if not for the sharing thereof?



Lest we forget...

Offline joseppi

  • Sr. Member
  • ****
  • Posts: 309
    • The Invitation Bible
Re: problem with k3b and HAL Daemon
« Reply #12 on: December 03, 2011, 06:07:32 PM »
This topics seems to end with no solution indicated?

I've just encountered the same problem and my CD/DVD burner is no longer found.
It doesn't read or write CDs or DVDs.

It was working recently, and I have made no changes in my system since it was working, so why did it quit working?


Offline Old-Polack

  • Administrator
  • Super Villain
  • *****
  • Posts: 11540
  • ----IOFLU----
Re: problem with k3b and HAL Daemon
« Reply #13 on: December 03, 2011, 06:44:09 PM »
This topics seems to end with no solution indicated?

I've just encountered the same problem and my CD/DVD burner is no longer found.
It doesn't read or write CDs or DVDs.

It was working recently, and I have made no changes in my system since it was working, so why did it quit working?



You are replying to a year and a half old thread. Start a new thread of your own and give as much detail as you can about your hardware, what DE you are running, and what you have tried, so far, to work out your problem. There is a lot better chance you'll get meaningful help with a new thread.
Old-Polack

Of what use be there for joy, if not for the sharing thereof?



Lest we forget...