headers
64 Studio | 1 Oct 2007 09:59
Favicon

Re: [64 Studio] #363: Ktoon export via Ming crashes

#363: Ktoon export via Ming crashes
---------------------------------+------------------------------------------
 Reporter:  daniel@...  |        Owner:  free
     Type:  defect               |       Status:  new 
 Priority:  normal               |    Milestone:  2.1 
Component:  packages             |      Version:  2.0 
 Severity:  normal               |   Resolution:      
 Keywords:                       |  
---------------------------------+------------------------------------------
Comment (by free@...):

 The new ktoon 0.8.1 is now in the testing branch. Does the problem still
 happen?

--

-- 
Ticket URL: <http://trac.64studio.com/64studio/ticket/363#comment:2>
64 Studio <>
Permalink | Reply | 0 comments |
headers
64 Studio | 1 Oct 2007 10:23
Favicon

Re: [64 Studio] #368: Software Properties dialogue has out of date information

#368: Software Properties dialogue has out of date information
---------------------------------+------------------------------------------
 Reporter:  daniel@...  |        Owner:  free  
     Type:  defect               |       Status:  closed
 Priority:  normal               |    Milestone:  2.1   
Component:  packages             |      Version:  2.0   
 Severity:  normal               |   Resolution:  fixed 
 Keywords:                       |  
---------------------------------+------------------------------------------
Changes (by free):

  * status:  new => closed
  * resolution:  => fixed

Comment:

 (In [280]) * Deleted Sarge from software-properties list (closes #368)

--

-- 
Ticket URL: <http://trac.64studio.com/64studio/ticket/368#comment:2>
64 Studio <>
Permalink | Reply | 0 comments |
headers
tim hall | 1 Oct 2007 12:28
Favicon

Re: [64studio-users] Version 2.0 boot failure

William McCanless wrote:
> Hello to all,
>
> I just installed version 2.0 on my AMD64 box, Athlon 64 2800+ on a
> PCCHIPS M848A board, with 1 gig memory, CD-rom, Pioneer DVD -+rw, and 2
> Seagate 120 gig IDE hard drives. Install was to hdb, with Suse 10.1
> running on hda. Install seemed to go fine, but stops right after boot
> begins, with message:
>
>    Begin: Waiting for root file system... ...
>
> After some time, it prints messages:
>
>    Check root=bootarg cat /proc/cmdline
>    or missing modules, devices: cat /proc/modules ls /dev
>    ALERT! /dev/hdb1 does not exist
>    Dropping to shell!
>
>    BusyBox v1.1.3 (Debian 1:1.1.3-4) Built-in shell (ash)
>    /bin/sh: can't access tty;
>
>    Job control turned off
>    (initramfs)_
>
> I have read everything I can find on the mail lists and forums, but
> found no solutions.  I suspect the problem lies somewhere in the boot
> files written into the master boot record by the installer, but I
> don't know enough about Linux to access that area.  This suspicion
> comes from a previous experience trying to install Debian. On that
> occasion the MBR was re-written in such a way as to cause Suse not to
(Continue reading)

Permalink | Reply | 0 comments |
headers
William McCanless | 1 Oct 2007 18:54
Picon

Re: Version 2.0 boot failure

On 10/1/07, tim hall <tim@...> wrote:
> William McCanless wrote:
> >  I suspect the problem lies somewhere in the boot
> > files written into the master boot record by the installer, but I
> > don't know enough about Linux to access that area.  This suspicion
> > comes from a previous experience trying to install Debian. On that
> > occasion the MBR was re-written in such a way as to cause Suse not to
> > boot on hda.
> >
> > I hope this info helps someone to help me and others,
> >
>
> Sorry I can't give an immediate answer.
> I am very interested in boot failures and am currently on an information
> gathering exercise myself.
> If I come across anything pertinent I'll post it.
>
> cheers,
>
> tim
>
>
I have done some more research on how the system is booted, and found
that info is hard to acquire.

I know that the OS must appear in the boot menu, and it does. But I
can't seem to recognize anything concerning Debian or 64Studio in the
"menu.lst" file.  Here's what I found so far:

    linux-prompt:~ # cd /boot/grub
(Continue reading)

Permalink | Reply | 2 comments |
headers
Gustin Johnson | 1 Oct 2007 20:35
Picon

Re: Version 2.0 boot failure


You likely installed 64Studio with its own grub into the second hard
drive.  Basically you have two different copies of grub installed, but
the bios will boot from the first one it finds (this is the short short
answer, there is plenty of documentation for those who are curious about
the details).

In SuSe you should be able to list the partitions on the second drive,
then mount them to have a look.

sudo parted /dev/hdb print

sudo mkdir /mnt/temp
sudo mount /dev/hdb1 /mnt/temp

This is easy if everything is one partition, else you will have to mount
each partition to have a look at it.  What you are looking for is the
partition that holds /boot

You can copy some of the entries out of your 64Studio menu.lst and copy
them into your SuSe menu.lst.   When you reboot you will see entries for
64Studio.

Pay attention to the root option in grub.  root = (hd0,0) is referring
to /dev/hda1 (or possibly /dev/sda1 if you have SATA).  The 64Studio
portion should be (hd1,0) or something similar, depending on the layout
of the partitions on that drive.

Some links for you (this is not a complete list of useful links, just
enough to get you started).
(Continue reading)

Permalink | Reply | 1 comment |
headers
William McCanless | 1 Oct 2007 21:18
Picon

Re: Version 2.0 boot failure

On 10/1/07, Gustin Johnson <gustin@...> wrote:
> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA1
>
> You likely installed 64Studio with its own grub into the second hard
> drive.  Basically you have two different copies of grub installed, but
> the bios will boot from the first one it finds (this is the short short
> answer, there is plenty of documentation for those who are curious about
> the details).

This is true, and when booting 64studio appears on the boot list, but
something seems to be fouled up between there and the actual boot
sequence on hdb.
>
SNIP

> This is easy if everything is one partition, else you will have to mount
> each partition to have a look at it.  What you are looking for is the
> partition that holds /boot

This is good, on my second install attempt I made only one partition,
to see if that would change anything.
>
> You can copy some of the entries out of your 64Studio menu.lst and copy
> them into your SuSe menu.lst.   When you reboot you will see entries for
> 64Studio.

The entry is there already. The boot starts but then stalls before
transferring to hdb (see my first message on this subject).
(Continue reading)

Permalink | Reply | 0 comments |
headers
William McCanless | 2 Oct 2007 04:11
Picon

Version 2.0 boot failure

I have been doing more homework. This is what I found as my multi boot set up:

	## ## End Default Options ##

	title           64 Studio, kernel 2.6.21-1-multimedia-amd64
	root            (hd1,0)
	kernel          /boot/vmlinuz-2.6.21-1-multimedia-amd64
root=/dev/hdb1 ro vga=791
              splash=silent
	initrd          /boot/initrd.img-2.6.21-1-multimedia-amd64
	savedefault
	
	title           64 Studio, kernel 2.6.21-1-multimedia-amd64 (single-user mode)
	root            (hd1,0)
	kernel          /boot/vmlinuz-2.6.21-1-multimedia-amd64
root=/dev/hdb1 ro vga=791
             splash=silent single
	initrd          /boot/initrd.img-2.6.21-1-multimedia-amd64
	savedefault

	### END DEBIAN AUTOMAGIC KERNELS LIST
	
	# This is a divider, added to separate the menu items below from the Debian
	# ones.
	title           Other operating systems:
	root
	
	
	# This entry automatically added by the Debian installer for an existing
	# linux installation on /dev/hda2.
(Continue reading)

Permalink | Reply | 3 comments |
headers
64 Studio | 4 Oct 2007 14:27
Favicon

[64 Studio] #381: Add python-xml package for Inkscape

#381: Add python-xml package for Inkscape
---------------------------------+------------------------------------------
 Reporter:  daniel@...  |       Owner:  free
     Type:  enhancement          |      Status:  new 
 Priority:  normal               |   Milestone:  2.1 
Component:  packages             |     Version:      
 Severity:  normal               |    Keywords:      
---------------------------------+------------------------------------------
 Inkscape requires the python-xml package (already in Etch) for some
 features to work, but we don't currently ship it.

--

-- 
Ticket URL: <http://trac.64studio.com/64studio/ticket/381>
64 Studio <>
Permalink | Reply | 1 comment |
headers
64 Studio | 4 Oct 2007 14:34
Favicon

[64 Studio] #382: Synaptic can't see our linux-source package by defualt

#382: Synaptic can't see our linux-source package by defualt
---------------------------------+------------------------------------------
 Reporter:  daniel@...  |       Owner:  free
     Type:  defect               |      Status:  new 
 Priority:  normal               |   Milestone:  2.1 
Component:  packages             |     Version:  2.0 
 Severity:  normal               |    Keywords:      
---------------------------------+------------------------------------------
 When using the following apt repositories:

 deb http://ftp.debian.org/debian/ etch main

 deb http://apt.64studio.com/64studio/testing/ 64studio main

 the Debian linux-source package for 2.6.18 is available in Synaptic, but
 our linux-source packages for 2.6.21 and 2.6.22 are not. Could be because
 our linux-source packages are in the custom branch. Should we update our
 apt information in the default 64studio.list file? What about users on the
 stable branch?

--

-- 
Ticket URL: <http://trac.64studio.com/64studio/ticket/382>
64 Studio <>
Permalink | Reply | 1 comment |
headers
Michael Jarosch | 4 Oct 2007 15:41
Picon
Favicon

Interrupts and stuff

Hi!

Got a problem on an ASUS A8V Deluxe / AMD Athlon 64 3000+ / RME HDSP 
9652 -System. I can see, that this or similar combination is often used 
for sound-producing and I read lots about people, working with latencies 
under 2ms without getting xruns. Well I'm using 10 ms latency, but xruns 
appear from time to time, anyway.
Looking at my interrupts, it seems quite clear, why:

mitsch <at> 64studio:~$ cat /proc/interrupts
           CPU0
  0:        193   IO-APIC-edge      timer
  1:       1854   IO-APIC-edge      i8042
  5:          0   IO-APIC-edge      MPU401 UART
  8:          0   IO-APIC-edge      rtc
  9:          0   IO-APIC-fasteoi   acpi
 12:          4   IO-APIC-edge      i8042
 14:      21954   IO-APIC-edge      ide0
 16:     182052   IO-APIC-fasteoi   ohci1394, nvidia
 17:      72482   IO-APIC-fasteoi   eth0, hdsp
 18:          0   IO-APIC-fasteoi   libata
 20:      42601   IO-APIC-fasteoi   libata
 21:     110985   IO-APIC-fasteoi   uhci_hcd:usb1, uhci_hcd:usb2, 
uhci_hcd:usb3, ehci_hcd:usb4, uhci_hcd:usb5
 22:          0   IO-APIC-fasteoi   VIA8237
NMI:          0
LOC:    2476944
ERR:          0

My card (hdsp) is on IRQ 17, sharing it with the Ethernet-Port, now.
(Continue reading)

Permalink | Reply | 1 comment |

Gmane