Re: DVD burning stop to work...PLEASE HELP ME!!!
On a similar issue I've found that the latest update appears to have broken k3b (when attempting to burn an image I get the error (cdrecord returned error code 1) which appears to be permissions related, since it successfully burnt the image when run as root. I haven't checked all the permissions manually but k3b identifies when it starts up that "cdrecord will be run without root priviledges" and "cdrdao will be run without root priviledges". Starting k3bsetup to fix this currently gets me a blank panel (from the command "kcmshell 'k3bsetup2'"). Anyway, for the moment running k3b as root appears to deal with this if you have this issue.On 3/11/06, Tony Freeman < [EMAIL PROTECTED]> wrote:On Thu, 2006-03-09 at 21:20 -0300, Marlon Régis Schmitz wrote: > [EMAIL PROTECTED]: cdrecord -scanbusI see that you are logged in as a normal user ... try doing yourgrowisofs command as root.I had a similar problem just yesterday morning! I was using thenautilus cd/dvd burning gui as a normal user and was frustrated that the cd was not being burned. I then realized that my new updates to thesystem must have screwed some permissions somewhere (after all it is atesting distribution) so that a normal user could not burn cd/dvds ... I logged in as root and sure enough I could use the nautilus cd/dvdburning gui just fine.-- Tony--To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: Kernel panic on boot with 2.6.10 Kernel
Unfortunately this doesn't seem to make any difference. Are the kernel options (root, real_root) unchanged in this version? On Sat, 5 Feb 2005 17:20:54 +0000, Gordon Ball <[EMAIL PROTECTED]> wrote: > On Sat, 5 Feb 2005 17:01:30 +0100, Filippo Carone > <[EMAIL PROTECTED]> wrote: > > * Gordon Ball ([EMAIL PROTECTED]) ha scritto: > > > Having until recently been using the stock 2.6.8-1-amd64-k8 kernel > > > (without problems), I decided to try and compile a new one myself. > > > > > > Using the package for kernel-source-2.6.10 I compiled a monolithic > > > kernel with (I think) everything essential for boot compiled into the > > > kernel. > > > > > > I've run out of ideas on this one. Am I missing anything obvious? > > > > you may try to enable: > > > > # CONFIG_BLK_DEV_IDE_SATA is not set > > > > lj > > > > -- > > To UNSUBSCRIBE, email to [EMAIL PROTECTED] > > with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED] > > > > > I'll have a go. However, that option is marked as depreciated in > favour of CONFIG_SCSI_SATA. The stock kernel I was running has > CONFIG_BLK_DEV_IDE_SATA disabled. > -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: Kernel panic on boot with 2.6.10 Kernel
On Sat, 5 Feb 2005 17:01:30 +0100, Filippo Carone <[EMAIL PROTECTED]> wrote: > * Gordon Ball ([EMAIL PROTECTED]) ha scritto: > > Having until recently been using the stock 2.6.8-1-amd64-k8 kernel > > (without problems), I decided to try and compile a new one myself. > > > > Using the package for kernel-source-2.6.10 I compiled a monolithic > > kernel with (I think) everything essential for boot compiled into the > > kernel. > > > > I've run out of ideas on this one. Am I missing anything obvious? > > you may try to enable: > > # CONFIG_BLK_DEV_IDE_SATA is not set > > lj > > -- > To UNSUBSCRIBE, email to [EMAIL PROTECTED] > with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED] > > I'll have a go. However, that option is marked as depreciated in favour of CONFIG_SCSI_SATA. The stock kernel I was running has CONFIG_BLK_DEV_IDE_SATA disabled. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Kernel panic on boot with 2.6.10 Kernel
Having until recently been using the stock 2.6.8-1-amd64-k8 kernel (without problems), I decided to try and compile a new one myself. Using the package for kernel-source-2.6.10 I compiled a monolithic kernel with (I think) everything essential for boot compiled into the kernel. In this configuration the startup successfully detects the existence of both the SATA controller and IDE controller (and all the disks connected to both correctly) and correctly prints out the partition table for the SATA disk (which includes the root filesystem). However, when it gets to trying to mount the root filesystem it returns the error: Kernel Panic - not syncing: VFS: Unable to mount root fs on unknown-block(8,5) Block device 8 appears to be "sd" which I think is correct - the SATA controller in question is listed under SCSI devices. sda5 is the root partition. The system is a Gigabyte K8N-Pro motherboard (nForce3 chipset). The IDE controller uses amd74xx and the SATA controller sata_sil. The config file for the kernel is attached. The system is configured BIOS boots (hd0,0) containing GRUB and kernels for a different linux installation. GRUB points at (hd2,0) (sda1) which is /boot for debian-amd64 containing the kernel, initrd etc. sda5 contains the root filesystem, which is ext3. The GRUB invocation is root(hd2,0) kernel /vmlinuz real_root=/dev/sda1 root=/dev/sda5 vga=792 initrd /initrd.img This successfully boots the previous stock kernel (2.6.8-1-amd64-k8). I also attempted to compile the kernel with just about everything as modules, and then create an initrd (mkinitrd with ROOT=probe in /etc/mkinitrd/mkinitrd.conf). However, this configuration fails to even detect the SATA controller and the above kernel panic line ends with "unknown-block(0,0)" instead. I've run out of ideas on this one. Am I missing anything obvious? Many thanks Gordon Ball config Description: Binary data
K8 Mainboards List
I've used the 'intel8x0' driver with the Gigabyte GA-K8N Pro motherboard onboard sound with reasonable success (with ALSA). This was in Gentoo system with a 2.6.7 kernel. Whether this applies to the other Gigabyte mainboards with the same onboard sound (Realtek ALC658 Audio AC'97 Codec) I'm not sure, perhaps anyone with these boards could confirm. Gordon Ball _ This message has been checked for all known viruses by UUNET delivered through the MessageLabs Virus Control Centre. For further information visit http://www.uk.uu.net/products/security/virus/
