On Mon, Jan 7, 2013 at 6:27 PM, Beco wrote:
>
> I think I might have a problem. It seems like the upgrade wont keep KDE.
>
> Is that so?
>
> Bellow the warnings.
>
> Any help in upgrading without so much trouble? Maybe removing
> beforehand "some" troublemaker packages?
>
> Thanks!
> Beco.
>
> PS.
On Mon, Jan 7, 2013 at 1:53 PM, Bob Proulx wrote:
> Tom H wrote:
>>
>> Dracut, the initramfs infrastructure that RH uses and that I often use
>> on Debian, doesn't require the UUID of an array on the kernel command
>> line.
>
> It isn't a dracut requirement. But it is how a default installation
>
On Mon, Jan 7, 2013 at 1:44 PM, Hendrik Boom wrote:
> On Mon, 07 Jan 2013 11:20:45 -0700, Bob Proulx wrote:
>> Hendrik Boom wrote:
>>>
>>> Won't boot. Gets stick at the initramfs prompt after complaining
>>> that it can't run /sbin/init
>>>
>>> I look with ls, and discover that /sbin exists, bit
On Mon, Jan 7, 2013 at 12:52 PM, Hendrik Boom wrote:
> On Mon, 07 Jan 2013 00:14:31 -0700, Bob Proulx wrote:
>> Hendrik Boom wrote:
>> Did you rebuild the initrd images for the booting kernel after having
>> done this?
>>
>> Example:
>>
>> dpkg-reconfigure linux-image-3.2.0-4-amd64
>
> dpkg-reconf
- Original Message -
> From: Mark Allums
> To: 'Debian User'
> Cc:
> Sent: Sunday, January 6, 2013 1:26 PM
> Subject: RE: Wheezy Installer Auto-Partition Oddity
>
>
> [snip]
>>
>> So, again I ask: Why that 1MiB unpartitioned space before the beginning
> of
>> a new partition?
On Mon, Jan 7, 2013 at 11:47 AM, Ross Boylan wrote:
> On Mon, 2013-01-07 at 03:23 -0500, Tom H wrote:
>>
>> "FD00" only matters when using v0.9 metadata. Squeeze defaults to v1.x
>> (1.2 IIRC), which isn't auto-assembled by the kernel.
>
> This leaves me slightly confused about Debian's behavior.
On Mon, 07 Jan 2013 16:00:03 +0100
Sthu Deus wrote:
> I probably will forbear here, and wait for year or so - may situation
> will change w/ jackd - You know it is as w/ PA - terrible, but things
> slowly change and something else will come instead. I do not believe
> that the jackd similar softw
On Mon, Jan 7, 2013 at 10:40 AM, Hendrik Boom wrote:
> On Mon, 07 Jan 2013 03:40:07 -0500, Tom H wrote:
>> On Mon, Jan 7, 2013 at 3:19 AM, Tom H wrote:
>>>
>>> Did you rebuild your initramfs?
>
> No, and no, and that's probably the problem.
Most probably.
--
To UNSUBSCRIBE, email to debian-us
Hi friend,
Are u interested in our new laser bike rear light ?
Below is picture with quotation for u reference .Don't delay ！Just
promotion 3days
<>
On Mon, 07 Jan 2013 12:10:03 -0700, Bob Proulx wrote:
> Hendrik Boom wrote:
>> Bob Proulx wrote:
>> > And just noting for the archive readers that in addition to working
>> > through the initrd busybox prompt it is also possible to use the
>> > Debian install media as a rescue system in the case t
I am not on the list, please keep me in CC.
I'm using apt in a way that works for me. I have a local mirror and apt was
setup to use /debian/apt- for various apt files (like sources.list,
the /var/lib/apt/lists, /var/cache/apt, ...). This allows me to never need
to do apt-get update.
The questi
With the intention of logging the problem so others can google, bellow
the same system but trying with apt-get.
It seems that apt-get is doing a better job.
Based on what I emailed (aptitude and apt-get outputs), what would be
best to do?
Thanks!
Beco.
PS. The command and its output:
--
Re
Hi guys,
I think I might have a problem. It seems like the upgrade wont keep KDE.
Is that so?
Bellow the warnings.
Any help in upgrading without so much trouble? Maybe removing
beforehand "some" troublemaker packages?
Thanks!
Beco.
PS. The command and its output:
root@Capivara:/etc/apt# apt
>> I have a binary file that I'm trying to execute. It works on my
>> squeeze system but not on wheezy.
>
> What is the error message?
I don't see any error message. Is there a system level log that would
capture something?
>
>> execve("./myApp.run", ["./myApp"...], [/* 17 vars */]) = 0
>> [
On 2013-01-07 22:17 +0100, ChadDavis wrote:
> I have a binary file that I'm trying to execute. It works on my
> squeeze system but not on wheezy.
What is the error message?
> the file commands gives me:
>
> ELF 32-bit LSB executable, Intel 80386, version 1 (GNU/Linux),
> statically linked, stri
both of my systems are 64 bit amd.
On Mon, Jan 7, 2013 at 2:17 PM, ChadDavis wrote:
> I have a binary file that I'm trying to execute. It works on my
> squeeze system but not on wheezy.
>
> the file commands gives me:
>
> ELF 32-bit LSB executable, Intel 80386, version 1 (GNU/Linux),
> statical
Hello,
I require a VGA & HDMI capture card and only using Linux is causing problems
I have found this on amazon
http://www.amazon.co.uk/StarTech-com-Express-1080p-Video-Capture/dp/tech-data/B007U5MGBE/ref=de_a_smtd
and it does say Linux, but when I checkout the manufacturers website
http://intrl.
On Mon, Jan 07, 2013 at 09:57:49PM +0700, Sthu Deus wrote:
> For sure.
>
> Thank You, Rob, for Your time and effort!
>
> Please excuse me for quick giving up - I did not meant to give the
> problem so much time / effort (reboot each time I try).
>
I understand that you're giving up for now. If
Hendrik Boom wrote:
> Bob Proulx wrote:
> > And just noting for the archive readers that in addition to working
> > through the initrd busybox prompt it is also possible to use the
> > Debian install media as a rescue system in the case this happens and
> > can't make other progress. The Debian in
Tom H wrote:
> Bob Proulx wrote:
> > Also I know that RHEL/CentOS at least also moved from an autoraid of
> > 0xFD to an explicitly mounted system too for the same reasons. But
> > they do it by specifying the UUIDs on the kernel command line from
> > grub. It makes for some very long command lines
On Mon, 07 Jan 2013 11:20:45 -0700, Bob Proulx wrote:
> Hendrik Boom wrote:
>> Now won't boot
>> ...
>> I had to mdadm --assemble /dev/md1 /dev/sdd2 /dev/sdb2 first.
>
> Oh! I am glad to hear that you were able to work through it manually
> though and get going.
>
>> > Did you rebuild the initr
Hendrik Boom wrote:
> Now won't boot
> ...
> I had to mdadm --assemble /dev/md1 /dev/sdd2 /dev/sdb2 first.
Oh! I am glad to hear that you were able to work through it manually
though and get going.
> > Did you rebuild the initrd images for the booting kernel after having
> > done this?
> >
> >
On Mon, 07 Jan 2013 10:58:04 -0500, Tom H wrote:
> On Mon, Jan 7, 2013 at 6:06 AM, Sven Hartge wrote:
>> Tom H wrote:
>>> On Mon, Jan 7, 2013 at 12:07 AM, Sven Hartge wrote:
Hendrik Boom wrote:
>>
> Any ideas where to look? Or how to work around the problem?
>>
What type are tho
On Mon, 07 Jan 2013 00:14:31 -0700, Bob Proulx wrote:
> Hendrik Boom wrote:
>> I have two RAID arrays on my Debian squeeze system. The old one, which
>> still works, and has worked for years, is on a pair of partitions on two
>> 750GB disks. THe new one is not recognized at boot.
>
> Does at
Hendrik Boom wrote:
> On Mon, 07 Jan 2013 06:07:37 +0100, Sven Hartge wrote:
>> Hendrik Boom wrote:
>>> But it is not recognized at boot. The dmesg output tells me all
>>> about finding the old RAID, but it doesn't even notice the new one,
>>> not even to complain about it.
>>
>>> It seems th
I have some advice and a more general question.
First, try assembling the array (using mdadm from the command line) once
the system is up. Once you're sure that works, you do need to update
mdadm.conf and the initrd.
BTW, the fact that the kernel is showing the partitions indicates that
it's han
On Monday 07 January 2013 06:46:31 Chris Bannister wrote:
> I read the output [unfortunately it's been snipped] as 2GB was the maximum
> capacity for that slot. Are there four slots?
The answer to this appears to be a large part of the problem.
Vardhan, if you get the memory you are going to ha
On Mon, Jan 7, 2013 at 6:06 AM, Sven Hartge wrote:
> Tom H wrote:
>> On Mon, Jan 7, 2013 at 12:07 AM, Sven Hartge wrote:
>>> Hendrik Boom wrote:
>
Any ideas where to look? Or how to work around the problem?
>
>>> What type are those partitions for your RAID inside the GPT? They should
>>>
On Mon, 07 Jan 2013 03:40:07 -0500, Tom H wrote:
> On Mon, Jan 7, 2013 at 3:19 AM, Tom H wrote:
>> On Sun, Jan 6, 2013 at 9:35 PM, Hendrik Boom wrote:
>>>
...
...
>>> Any ideas where to look? Or how to work around the problem?
>>
>> Is the new array listed in mdadm.conf?
>>
>> Did you rebuild y
On Mon, 07 Jan 2013 00:14:31 -0700, Bob Proulx wrote:
> Hendrik Boom wrote:
>> I have two RAID arrays on my Debian squeeze system. The old one, which
>> still works, and has worked for years, is on a pair of partitions on two
>> 750GB disks. THe new one is not recognized at boot.
>
> Does at
On Mon, 07 Jan 2013 06:07:37 +0100, Sven Hartge wrote:
> Hendrik Boom wrote:
>
>> But it is not recognized at boot. The dmesg output tells me all about
>> finding the old RAID, but it doesn't even notice the new one, not even to
>> complain about it.
>
>> It seems the significant differences
You wrote:
> http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=646248
>
> I thought it was particularly interesting that an HDMI-capable video
> card could be detected as an audio device and possibly "intercept"
> your jackd command.
I have no such a card! :o) So, not my case.
Thanks again!!
S
Good time of the day, Rob.
Thank You, Rob, for Your time and answer. You wrote:
> You may also want to start qjackctl with its default settings and see
> how that goes. Delete QjackCtl.conf and .jackdrc
It works some how - but weird. - In messages window it says that the
jack server got signal
On Sun, Jan 06, 2013 at 02:10:43AM -0800, - - wrote:
> Hello,
>
> I am trying to write an init script for cherokee webserver. Not, there is
> already one, but I wanted to have one derived from skeleton.
>
>
>
> In function "do_stop()" the script executes this line:
> "start-stop-daemon --stop
Tom H wrote:
> On Mon, Jan 7, 2013 at 12:07 AM, Sven Hartge wrote:
>> Hendrik Boom wrote:
>>> Any ideas where to look? Or how to work around the problem?
>> What type are those partitions for your RAID inside the GPT? They should
>> look like this (output from gdisk -l):
>>
>> Number Start (
Hi Vishnu,
maybe you have to update the BIOS of the notebook?
The output of dmidecode shows "SMBIOS 2.7". Looking at the website
http://www.toshiba-india.com/laptop/satellite-c850-amd-viewmodel.html under
Service & Support --> Download Drivers for BIOS of Sattelite C850 it says the
newest is
23
On Mon, Jan 7, 2013 at 3:19 AM, Tom H wrote:
> On Sun, Jan 6, 2013 at 9:35 PM, Hendrik Boom wrote:
>>
>> I have two RAID arrays on my Debian squeeze system. The old one, which
>> still works, and has worked for years, is on a pair of partitions on two
>> 750GB disks. THe new one is not recogniz
On Mon, Jan 7, 2013 at 2:14 AM, Bob Proulx wrote:
>
> Also I know that RHEL/CentOS at least also moved from an autoraid of
> 0xFD to an explicitly mounted system too for the same reasons. But
> they do it by specifying the UUIDs on the kernel command line from
> grub. It makes for some very long c
On Mon, Jan 7, 2013 at 12:07 AM, Sven Hartge wrote:
> Hendrik Boom wrote:
>
>> But it is not recognized at boot. The dmesg output tells me all about
>> finding the old RAID, but it doesn't even notice the new one, not even to
>> complain about it.
>
>> It seems the significant differences bwtwee
On Sun, Jan 6, 2013 at 9:35 PM, Hendrik Boom wrote:
>
> I have two RAID arrays on my Debian squeeze system. The old one, which
> still works, and has worked for years, is on a pair of partitions on two
> 750GB disks. THe new one is not recognized at boot.
>
> boot is *not* on any of these RAIDs;
40 matches
Mail list logo
