Bristol Digest, Vol 535, Issue 4

Send Bristol mailing list submissions to
bristol@mailman.lug.org.uk

To subscribe or unsubscribe via the World Wide Web, visit
https://mailman.lug.org.uk/mailman/listinfo/bristol
or, via email, send a message with subject or body 'help' to
bristol-request@mailman.lug.org.uk

You can reach the person managing the list at
bristol-owner@mailman.lug.org.uk

When replying, please edit your Subject line so it is more specific
than "Re: Contents of Bristol digest..."


Today's Topics:

1. Re: Squeeze > Wheezy upgrade problem. (Simon Iremonger (bblug))
2. Re: Squeeze > Wheezy upgrade problem. (Martin Moore)
3. Re: modprobe: bad line 1: 1 tokens found, 2 needed (Martin Moore)
4. Re: modprobe: bad line 1: 1 tokens found, 2 needed (Chris)
5. WAS modprobe: bad line 1: 1 tokens found, 2 needed NOW How
to add image to GRUB2 (Martin Moore)


----------------------------------------------------------------------

Message: 1
Date: Thu, 30 Jan 2014 13:24:55 +0000
From: "Simon Iremonger (bblug)" <bblug@iremonger.me.uk>
To: martinm@it-helps.co.uk, Bristol and Bath Linux User Group
<bristol@mailman.lug.org.uk>
Subject: Re: [bristol] Squeeze > Wheezy upgrade problem.
Message-ID: <52EA52A7.4050908@iremonger.me.uk>
Content-Type: text/plain; charset=ISO-8859-1

> E: Could not perform immediate configuration on 'libgd-gd2-perl'. Please see
> man 5 apt.conf under APT::Immediate-Configure for details. (2

http://www.debian.org/releases/stable/i386/release-notes/ch-upgrading.en.html#upgrading-full

See error mentioned.
Solution mentioned.

Also, worth looking at rest of release notes, they have actually
been helpful. =)

> Martin.
--Simon





------------------------------

Message: 2
Date: Thu, 30 Jan 2014 13:56:37 -0000
From: "Martin Moore" <martinm@it-helps.co.uk>
To: "'Bristol and Bath Linux User Group'" <bristol@mailman.lug.org.uk>
Subject: Re: [bristol] Squeeze > Wheezy upgrade problem.
Message-ID:
<!&!AAAAAAAAAAAYAAAAAAAAAFLxZtQqo65Oo+1jhlUB9DvCgAAAEAAAAKwXP/uI5V9KgQBVg8L1FKEBAAAAAA==@it-helps.co.uk>

Content-Type: text/plain; charset="us-ascii"

Found that and it worked, cheers.



-----Original Message-----
From: bristol-bounces@mailman.lug.org.uk
[mailto:bristol-bounces@mailman.lug.org.uk] On Behalf Of Simon Iremonger
(bblug)
Sent: 30 January 2014 13:25
To: martinm@it-helps.co.uk; Bristol and Bath Linux User Group
Subject: Re: [bristol] Squeeze > Wheezy upgrade problem.

> E: Could not perform immediate configuration on 'libgd-gd2-perl'.
> Please see man 5 apt.conf under APT::Immediate-Configure for details.
> (2

http://www.debian.org/releases/stable/i386/release-notes/ch-upgrading.en.htm
l#upgrading-full

See error mentioned.
Solution mentioned.

Also, worth looking at rest of release notes, they have actually been
helpful. =)

> Martin.
--Simon



_______________________________________________
Bristol mailing list
Bristol@mailman.lug.org.uk
https://mailman.lug.org.uk/mailman/listinfo/bristol
-----
No virus found in this message.
Checked by AVG - www.avg.com
Version: 2014.0.4259 / Virus Database: 3681/7042 - Release Date: 01/29/14




------------------------------

Message: 3
Date: Thu, 30 Jan 2014 14:20:20 -0000
From: "Martin Moore" <martinm@it-helps.co.uk>
To: "'Bristol and Bath Linux User Group'"
<bristol@mailman.lug.org.uk>, "'Chris'" <cshorler@googlemail.com>
Subject: Re: [bristol] modprobe: bad line 1: 1 tokens found, 2 needed
Message-ID:
<!&!AAAAAAAAAAAYAAAAAAAAAFLxZtQqo65Oo+1jhlUB9DvCgAAAEAAAANjzJ17iTN9Nk3BRSvkt8ZoBAAAAAA==@it-helps.co.uk>

Content-Type: text/plain; charset="us-ascii"

Do I need to do anything with update-initramfs ?

Or have I bypassed this requirement?



-----Original Message-----
From: bristol-bounces@mailman.lug.org.uk
[mailto:bristol-bounces@mailman.lug.org.uk] On Behalf Of Martin Moore
Sent: 30 January 2014 10:47
To: bristol@mailman.lug.org.uk; 'Chris'
Cc: martinm@it-helps.co.uk
Subject: Re: [bristol] modprobe: bad line 1: 1 tokens found, 2 needed

OK, I had looked for other blacklists yesterday but didn't know about
initrd.

Using
http://www.thegeekstuff.com/2009/07/how-to-view-modify-and-recreate-initrd-i
mg/ I've removed the contents of the blacklist file (it still exists but is
empty)

and set the link /initrd.img > /boot/initrc.mynewimage

Still get the same error.


Martin

-----Original Message-----
From: Chris [mailto:cshorler@googlemail.com]
Sent: 29 January 2014 18:39
To: martinm@it-helps.co.uk; Bristol and Bath Linux User Group; Martin Moore;
'Bristol and Bath Linux User Group'
Subject: Re: [bristol] modprobe: bad line 1: 1 tokens found, 2 needed

On 29 January 2014 16:02:24 GMT+00:00, Martin Moore <martinm@it-helps.co.uk>
wrote:
>
>
>Upgraded a Dell from squeeze to wheezy. Go to the reboot and it stops
>with the error
>
>
>
>
><http://forums.debian.net/viewtopic.php?f=5&t=104868#p501288> modprobe:
>bad
>line 1: 1 tokens found, 2 needed
>
>
>
>
>
>
>Google reckons it's the blacklist file. I've moved it but still get the
>problem. Help.
>
>

When you say stops, do you have a shell?

Did you check for other syntax errors in modprobe conf files?

Does the initrd also contain a blacklist?

Chris




_______________________________________________
Bristol mailing list
Bristol@mailman.lug.org.uk
https://mailman.lug.org.uk/mailman/listinfo/bristol
-----
No virus found in this message.
Checked by AVG - www.avg.com
Version: 2014.0.4259 / Virus Database: 3681/7042 - Release Date: 01/29/14




------------------------------

Message: 4
Date: Thu, 30 Jan 2014 17:38:39 +0000
From: Chris <cshorler@googlemail.com>
To: martinm@it-helps.co.uk, Bristol and Bath Linux User Group
<bristol@mailman.lug.org.uk>
Subject: Re: [bristol] modprobe: bad line 1: 1 tokens found, 2 needed
Message-ID: <b2edf732-a036-4120-a5d5-b8a764fceddf@email.android.com>
Content-Type: text/plain; charset=UTF-8

On 30 January 2014 14:20:20 GMT+00:00, Martin Moore <martinm@it-helps.co.uk> wrote:
>Do I need to do anything with update-initramfs ?
>
>Or have I bypassed this requirement?

Well I'm not a Debian user, on SUSE though (from memory as I'm also not in front of a computer), the equivalent tool calls a PERL module that updates the boot loader configuration to point to the initrd created. The one you symlinked is only booted as a last result. Maybe the same is true on Debian?

>
>
>
>-----Original Message-----
>From: bristol-bounces@mailman.lug.org.uk
>[mailto:bristol-bounces@mailman.lug.org.uk] On Behalf Of Martin Moore
>Sent: 30 January 2014 10:47
>To: bristol@mailman.lug.org.uk; 'Chris'
>Cc: martinm@it-helps.co.uk
>Subject: Re: [bristol] modprobe: bad line 1: 1 tokens found, 2 needed
>
>OK, I had looked for other blacklists yesterday but didn't know about
>initrd.
>
>Using
>http://www.thegeekstuff.com/2009/07/how-to-view-modify-and-recreate-initrd-i
>mg/ I've removed the contents of the blacklist file (it still exists
>but is
>empty)
>
>and set the link /initrd.img > /boot/initrc.mynewimage
>
>Still get the same error.
>
>
>Martin
>
>-----Original Message-----
>From: Chris [mailto:cshorler@googlemail.com]
>Sent: 29 January 2014 18:39
>To: martinm@it-helps.co.uk; Bristol and Bath Linux User Group; Martin
>Moore;
>'Bristol and Bath Linux User Group'
>Subject: Re: [bristol] modprobe: bad line 1: 1 tokens found, 2 needed
>
>On 29 January 2014 16:02:24 GMT+00:00, Martin Moore
><martinm@it-helps.co.uk>
>wrote:
>>
>>
>>Upgraded a Dell from squeeze to wheezy. Go to the reboot and it stops
>>with the error
>>
>>
>>
>>
>><http://forums.debian.net/viewtopic.php?f=5&t=104868#p501288>
>modprobe:
>>bad
>>line 1: 1 tokens found, 2 needed
>>
>>
>>
>>
>>
>>
>>Google reckons it's the blacklist file. I've moved it but still get
>the
>>problem. Help.
>>
>>
>
>When you say stops, do you have a shell?
>
>Did you check for other syntax errors in modprobe conf files?
>
>Does the initrd also contain a blacklist?
>
>Chris
>
>
>
>
>_______________________________________________
>Bristol mailing list
>Bristol@mailman.lug.org.uk
>https://mailman.lug.org.uk/mailman/listinfo/bristol
>-----
>No virus found in this message.
>Checked by AVG - www.avg.com
>Version: 2014.0.4259 / Virus Database: 3681/7042 - Release Date:
>01/29/14
>
>
>_______________________________________________
>Bristol mailing list
>Bristol@mailman.lug.org.uk
>https://mailman.lug.org.uk/mailman/listinfo/bristol





------------------------------

Message: 5
Date: Fri, 31 Jan 2014 11:01:00 -0000
From: "Martin Moore" <martinm@it-helps.co.uk>
To: "'Bristol and Bath Linux User Group'" <bristol@mailman.lug.org.uk>
Subject: [bristol] WAS modprobe: bad line 1: 1 tokens found, 2 needed
NOW How to add image to GRUB2
Message-ID: <19fe01cf1e73$bc1f8b90$345ea2b0$@co.uk>
Content-Type: text/plain; charset="us-ascii"

OK, found the problem - GRUB didn't have the new image listed so was still
booting the old one.....

I've booted the new one using a rescue CD, but need to add the new image to
GRUB2. Unbelievably I can't find how to do this!!

How to I add a new image to GRUB2?


Cheers,

Martin.

-----Original Message-----
From: bristol-bounces@mailman.lug.org.uk
[mailto:bristol-bounces@mailman.lug.org.uk] On Behalf Of Chris
Sent: 30 January 2014 17:39
To: martinm@it-helps.co.uk; Bristol and Bath Linux User Group
Subject: Re: [bristol] modprobe: bad line 1: 1 tokens found, 2 needed

On 30 January 2014 14:20:20 GMT+00:00, Martin Moore <martinm@it-helps.co.uk>
wrote:
>Do I need to do anything with update-initramfs ?
>
>Or have I bypassed this requirement?

Well I'm not a Debian user, on SUSE though (from memory as I'm also not in
front of a computer), the equivalent tool calls a PERL module that updates
the boot loader configuration to point to the initrd created. The one you
symlinked is only booted as a last result. Maybe the same is true on
Debian?

>
>
>
>-----Original Message-----
>From: bristol-bounces@mailman.lug.org.uk
>[mailto:bristol-bounces@mailman.lug.org.uk] On Behalf Of Martin Moore
>Sent: 30 January 2014 10:47
>To: bristol@mailman.lug.org.uk; 'Chris'
>Cc: martinm@it-helps.co.uk
>Subject: Re: [bristol] modprobe: bad line 1: 1 tokens found, 2 needed
>
>OK, I had looked for other blacklists yesterday but didn't know about
>initrd.
>
>Using
>http://www.thegeekstuff.com/2009/07/how-to-view-modify-and-recreate-ini
>trd-i mg/ I've removed the contents of the blacklist file (it still
>exists but is
>empty)
>
>and set the link /initrd.img > /boot/initrc.mynewimage
>
>Still get the same error.
>
>
>Martin
>
>-----Original Message-----
>From: Chris [mailto:cshorler@googlemail.com]
>Sent: 29 January 2014 18:39
>To: martinm@it-helps.co.uk; Bristol and Bath Linux User Group; Martin
>Moore; 'Bristol and Bath Linux User Group'
>Subject: Re: [bristol] modprobe: bad line 1: 1 tokens found, 2 needed
>
>On 29 January 2014 16:02:24 GMT+00:00, Martin Moore
><martinm@it-helps.co.uk>
>wrote:
>>
>>
>>Upgraded a Dell from squeeze to wheezy. Go to the reboot and it stops
>>with the error
>>
>>
>>
>>
>><http://forums.debian.net/viewtopic.php?f=5&t=104868#p501288>
>modprobe:
>>bad
>>line 1: 1 tokens found, 2 needed
>>
>>
>>
>>
>>
>>
>>Google reckons it's the blacklist file. I've moved it but still get
>the
>>problem. Help.
>>
>>
>
>When you say stops, do you have a shell?
>
>Did you check for other syntax errors in modprobe conf files?
>
>Does the initrd also contain a blacklist?
>
>Chris
>
>
>
>
>_______________________________________________
>Bristol mailing list
>Bristol@mailman.lug.org.uk
>https://mailman.lug.org.uk/mailman/listinfo/bristol
>-----
>No virus found in this message.
>Checked by AVG - www.avg.com
>Version: 2014.0.4259 / Virus Database: 3681/7042 - Release Date:
>01/29/14
>
>
>_______________________________________________
>Bristol mailing list
>Bristol@mailman.lug.org.uk
>https://mailman.lug.org.uk/mailman/listinfo/bristol



_______________________________________________
Bristol mailing list
Bristol@mailman.lug.org.uk
https://mailman.lug.org.uk/mailman/listinfo/bristol




------------------------------

_______________________________________________
Bristol mailing list
Bristol@mailman.lug.org.uk
https://mailman.lug.org.uk/mailman/listinfo/bristol

End of Bristol Digest, Vol 535, Issue 4
***************************************