Re: Jessie: Set up Samba and Winbind, can't log in to the domain

[Stefan Pietsch]

On 14.05.2015 23:47, Dalton D wrote:
> Hello!
> 
> I'm trying to install Pykota on Debian Jessie. At the moment, I'm trying
> to get it so that I can log in to the system with Active Directory
> accounts. I set up Samba and Winbind correctly but still can't do this.
> From the syslog, it seems that Winbind is crashing when I try to log in.
> 
> I can get a list of users by doing wbinfo -u. I can also get correct
> entries using getent passwd.
> 
> The relevant part of my syslog: http://pastebin.com/5SkkwA1d
> 
> My smb.conf: http://pastebin.com/FR4F44kT
> 
> I installed all the needed packages using apt and the system is fully
> upgraded. Winbind is enabled in pam-auth-config. 


It looks like Debian bug 784656 affects some more users.

If you change the permissions on the /var/log/samba/cores/winbindd
directory, winbindd will write a core file.


Regards,
Stefan


-- 
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org 
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: https://lists.debian.org/5557074c.2050...@sp.consulting.lsexperts.de

Re: how to start gnome from the command line

[Jeremy Cooney]

Thank you and God bless!


-- 
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org 
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: 
https://lists.debian.org/fcbad620-0666-4b8c-a2dc-59bbc4d43...@icloud.com

Re: out of the box wifi adapter

[Tony van der Hoff]

On 16/05/15 01:09, Bob Proulx wrote:
> Raymond Jennings wrote:
>> I wound up buying a 100 foot cat5 cable and running it from the house to
>> the trailer :P
> 
> My perspective is that nothing is as reliable as hardline wire!  It
> will be much more immune to radio noise trouble.  Speedy and
> reliable.  Wire will almost always be my choice if possible.
> 
> If you didn't think of http://www.monoprice.com/ for that 100 foot
> cable let me make a mention of it here for the future.  I am a happy
> customer of them.
> 
>   http://www.monoprice.com/Category?c_id=105&cp_id=10208&cs_id=1020814
> 
> Bob
> 
> 
Beware: These cables tend to be prone to UV degradation; best to run
them in some sort of conduit for use outdoors. Outdoor grade cable is
available, though, as is armoured cable.

-- 
Tony van der Hoff  | mailto:t...@vanderhoff.org
Ariège, France |


-- 
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org 
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: https://lists.debian.org/5557176f.2050...@vanderhoff.org

dmfe: big packet = 1518

[Mimiko]

Hello.

How to find on which interface this packet appears?

--
Mimiko desu.


--
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org 
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org

Archive: https://lists.debian.org/55572382.6060...@gmail.com

Re: Need SAS HBA for Debian Jessie

[Leslie Rhorer]

On Sunday, May 3, 2015 at 10:30:03 PM UTC-5, Bob Bernstein wrote:
> On Sun, 3 May 2015, Leslie Rhorer wrote:
> 
> > Many specifically list SuSe and Red Hat, but very 
> > few list Debian [...]
> 
> And you have your answer: send money to RH. They used 

   I don't have money to send to Red Hat.  First of all, one reason (although 
not the only one, by far) I am using Linux is it is free of commercial 
restraints.  Secondly, these are not commercial systems. These are a pair of 
home RAID arrays used primarily to store a personal video library.  Thirdly, I 
rather dislike Red Hat's distribution and administration system.  I much prefer 
Debian.

   Just as an aside, this is a Debian user forum.  Frankly, it strikes me as a 
bit strange to advise someone asking a question concerning an ordinary use of 
Debian to go somewhere else.

> to be very good at reliably supporting a lot of 
> different hardware. (I'm out of that consulting 
> biz now...for some time now.)

   Honestly, IMO this isn't primarily an issue of hardware support.  It is an 
issue of informational support by the hardware manufacturers.  They post lots 
of fru-fru information about their product without posting the information one 
really needs to know to make an informed purchase.  Very few of the HBA 
manufactureer inform the user whether the card at hand supports LBA 48 or not.  
I have purchase several controllers only to find the drive size limited to 2T.  
Many devices that only specify RH and / or SuSE are in fact perfectly well 
supported under Debian and most of its derivatives.  Many just report Linux 
support, when in fact there is no support under many distros.

> There are many fates worse than becoming, for certain 
> of one's key systems, a RH customer. Even more so if 
> making money, or deliverables, is part of the job of 
> said key systems.

   It is not, and economy is definitely a key consideration, here.  What's 
more, I am not asking the OS to support any particular hardware.  What I am 
asking - even if it were REd Hat - is whihc hardware is supported.  That really 
should not be that difficult a question.  (Yes, I understand why it is in fact 
a difficult question.)


> It boils down to the question "How much of my time do 
> I want to waste looking for those hens' teeth, and, 

  These aren't hen's teeth.  They are type O-Positive blood donors.  I just 
need the bag labeled with the blood type so I know which one to choose.

> given what my time is worth, do I want to take that 
> hit?"

   As opposed to the huge amount of time it would take me to switch operating 
systems?  Few, if any, of the dozens of scripts I have in place to manage the 
system would work out of the box.  They would need to be re-written.  Nearly 
all of the software I have written would have to be re-compiled, and some might 
need to be re-written.  I would also have to spend a lot of time getting far 
more familiar with Red Hat than I am now.  No, by far the most economical route 
is just to buy HBAs that are compatible with the OS I have now.


--
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: 
https://lists.debian.org/ddafb41e-c254-43cc-baf0-a2031b8c8...@googlegroups.com

Re: out of the box wifi adapter

[Gene Heskett]

On Saturday 16 May 2015 06:09:51 Tony van der Hoff wrote:
> On 16/05/15 01:09, Bob Proulx wrote:
> > Raymond Jennings wrote:
> >> I wound up buying a 100 foot cat5 cable and running it from the
> >> house to the trailer :P
> >
> > My perspective is that nothing is as reliable as hardline wire!  It
> > will be much more immune to radio noise trouble.  Speedy and
> > reliable.  Wire will almost always be my choice if possible.
> >
> > If you didn't think of http://www.monoprice.com/ for that 100 foot
> > cable let me make a mention of it here for the future.  I am a happy
> > customer of them.
> >
> >  
> > http://www.monoprice.com/Category?c_id=105&cp_id=10208&cs_id=1020814
> >
> > Bob
>
> Beware: These cables tend to be prone to UV degradation; best to run
> them in some sort of conduit for use outdoors. Outdoor grade cable is
> available, though, as is armoured cable.

On the other side of this, I have 2 100 foot pieces of cat5, Belden's 
bright blue stuff, strung across my back yard, one from the switch at my 
router to a workshop/shed with 3 computers in it, and another from that 
shed back to the garage where another old linux box lives.  The run from 
the house to the shop is about 40 feet, and back to the garage is about 
40 feet.  It has been blowing in the wind for something north of a 
decade now, including 2 damaging windstorms, one of which was recorded 
at 112 mph a block away back in 2010.  The blue is fading, but the 
signal is rock solid on a 100 megabit circuit yet.  After the abuse its 
been thru, I have no idea why its still working, but it is.
> --
> Tony van der Hoff  | mailto:t...@vanderhoff.org
> Ariège, France |

Cheers, Gene Heskett
-- 
"There are four boxes to be used in defense of liberty:
 soap, ballot, jury, and ammo. Please use in that order."
-Ed Howdershelt (Author)
Genes Web page 


--
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: https://lists.debian.org/201505160910.35269.ghesk...@wdtv.com

Re: aptitude update errors for upgrade to Jessie on amd64

[Brian]

On Fri 15 May 2015 at 22:03:59 -0500, David Wright wrote:

> Quoting Bob Proulx (b...@proulx.com):
> 
> > When the program looks up the ftp.us.debian.org name it will get all
> > three of the above in some order.  If your system is IPv6 capable it
> > will prefer the IPv6 address and always use it.  If not then it will
> > select one of the two IPv4 addresses and use it.  The different mirror
> > sites are using different software.  Some sites advertise their own
> > information and others do not.  The archive data provided is the same
> > in either case.  And regardless the Release file is cryptographically
> > signed and checksumed such that it can be trusted regardless of the
> > host transporting it.  We appreciate the mirrors making their
> > bandwidth and hosting available for Debian mirrors.
> 
> Thanks for that clear exposition. I myself have had no problem with
> these differences (assuming they could even be relevant). But can you
> throw any light on why Pierre is apparently being served a .xz
> compressed file by ftp.fr.debian.org which is making apt-get
> (presumably expecting to receive a .gz file) fail to verify the
> digest? (I can't even try reproducing this as I'm i386 and he's amd64.)

A comparison of the outputs from 'apt-config dump' on both laptops might
give something.

Unreproducible here on a new bare-bones i386 Wheezy install with the
same mirror.


-- 
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org 
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: 
https://lists.debian.org/16052015142357.38cfac72d...@desktop.copernicus.demon.co.uk

jesse partitioner

[Bob McKittrick]

after installing jesse and it boots, the bios kicks out the drive. I am
using an asus H61M motherboard with bios dated 2012 or 2013. The install
askes for
 rt1_nic/rt18168-1.fw . would that help ?
bob McKittrick

Re: aptitude update errors for upgrade to Jessie on amd64

[Pierre Frenkiel]

On Sat, 16 May 2015, Brian wrote:



A comparison of the outputs from 'apt-config dump' on both laptops might
give something.


  alas no!
  after copying the /etc/apt directory from laptop2 to my laptop, the only 
difference is

  ==> diff apt-config_dump.ch8 apt-config_dump.mynb

  132c132
  < Acquire::Languages:: "fr";
  ---
  > Acquire::Languages:: "en";
  133a134
  > Acquire::Languages:: "fr";

 I don't think it can explain the problem.
 I'm rather reluctant to do a bug report, as I'm the only one to
 have this issue, and will probably use one of the proposed workarounds,
 although it's frustating to leave this mystery unexplained.


Unreproducible here on a new bare-bones i386 Wheezy install with the
same mirror.


  for me too, on my i386 desktop, wheezy or jessie.

best regards,
--
Pierre Frenkiel


--
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org 
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org

Archive: 
https://lists.debian.org/alpine.deb.2.11.1505161626180.27...@pfr2.frenkiel-hure.net

Re: jesse partitioner

[Petter Adsen]

On Sat, 16 May 2015 10:24:52 -0400
Bob McKittrick  wrote:

> after installing jesse and it boots, the bios kicks out the drive. I

What do you mean by "the bios kicks out the drive"? What happens, and
what (if any) relevant log messages do you see?

> am using an asus H61M motherboard with bios dated 2012 or 2013. The
> install askes for
>  rt1_nic/rt18168-1.fw . would that help ?

It really shouldn't, as far as I can understand, as that is for an
Ethernet controller. Anyway, you can get that by installing
"firmware-realtek".

Petter

-- 
"I'm ionized"
"Are you sure?"
"I'm positive."


pgplBUdljia6D.pgp
Description: OpenPGP digital signature

Re: ulogd2 fails with kernel 4.0.0-1

[Hugo Vanwoerkom]

Sven Hartge wrote:

Hugo Vanwoerkom  wrote:


Running Sid dist-upgraded on May 12 2015 which went to kernel 4.0.0-1.
I run the firewall via Firehol and use  'FIREHOL_LOG_MODE="ULOG"'.
Iptables then gets errors because it cannot find ULOG.  That is
because ulogd2 failed with:



May 15 11:56:39 hdbb ulogd[5785]: Can't create ULOG handle
May 15 11:56:39 hdbb ulogd[5785]: error starting `ulog1'



When this dist-upgraded system is booted with kernel 3.16.0-4 ulogd2
starts correctly:



May 15 15:46:24 hdbb ulogd[27455]: building new pluginstance stack:
'ulog1:ULOG,base1:BASE,ip2str1:IP2STR,print1:PRINTPK



But I seem to be the first person that ran into this because I find no
references to this error. Is it because this kernel is new?


I would think so.

My guess is most people running ulogd run it on their firewall systems,
systems normally not running Sid.



Good point.

Hugo



--
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org 
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org

Archive: https://lists.debian.org/mj7ptl$gmv$1...@ger.gmane.org

Wrong library versions

[Gary Roach]

Hi All

I would put this on the freeCAD forum except I have been trying for 
several days to get authorization to join without success. So:


The copy of freeCAD is version 0.14 on all versions of Debian. I'm using 
jessie with amd64 software. I want to ppa the 0.15 version from the 
freeCAD web site. Unfortunately, 0.15 requires libboost 1.54 but jessie 
loads 1.55. Further, Debian has never used version 1.54 but skipped from 
1.4 something in wheezy to 1.55 in jessie. Is there an way around this 
problem.


I hate going off the official repository but the development of this 
package is proceeding at a furious rate. It's basically an alpha release 
but its the only game in town.


Any help will be seriously appreciated.

Gary R


--
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org 
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org

Archive: https://lists.debian.org/555781a4.4000...@verizon.net

Re: usb device umount option in menu missing for some devices [SOLVED]

[deloptes]

For the record

in
/opt/trinity/share/apps/konqueror/servicemenus/media_unmount.desktop

add

media/camera_mounted

to

[Desktop Entry]
X-TDE-ServiceTypes=,media/camera_mounted

at the end of the list like above.

Then reload the desktop session and the unmount option appears as expected.

regards


-- 
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org 
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: https://lists.debian.org/mj7vos$8q1$1...@ger.gmane.org

Re: jessie installation problem on arm sheevaplug

[Rodrigo Valiña Gutiérrez]

I had the same problem installing Debian 8 'Jessie' on a SheevaPlug.

I solved it temporarily by doing the following:

- In u-boot:

setenv machid 0692
saveenv

- Then install normally. The 'make the system bootable' phase will fail
because flash-kernel fails:
 /var/log/installer/syslog:
May 16 13:47:28 in-target: Setting up u-boot-tools (2014.10+dfsg1-5) ...^M
4-kirkwood
May 16 13:47:46 in-target: Unsupported platform.
May 16 13:47:46 flash-kernel-installer: error: flash-kernel failed
May 16 13:47:46 main-menu[170]: WARNING **: Configuring
'flash-kernel-installer' failed with error code 1
May 16 13:47:46 main-menu[170]: WARNING **: Menu item
'flash-kernel-installer' failed.


- Then select 'execute a shell' and write:

cd /target/boot/
/target/usr/bin/mkimage -A arm -O linux -T kernel  -C none -n uImage  -a
0x8000 -e 0x8000 -d vmlinuz uImage
/target/usr/bin/mkimage -A arm -O linux -T ramdisk -C none -n
uInitrd -d initrd.img  uInitrd

- It may be neccesary to change 0x8000 to 0x0080 in both cases, but
in my case it worked the way above.
- Then 'exit' the shell and select 'continue without boot loader'.
- I think that this last phase of mkimage should be repeated on every
kernel upgrade because I think flash-kernel (which calls mkimage) will fail
again.

Re: Wrong library versions

[Ric Moore]

On 05/16/2015 01:43 PM, Gary Roach wrote:

Hi All

I would put this on the freeCAD forum except I have been trying for
several days to get authorization to join without success. So:

The copy of freeCAD is version 0.14 on all versions of Debian. I'm using
jessie with amd64 software. I want to ppa the 0.15 version from the
freeCAD web site. Unfortunately, 0.15 requires libboost 1.54 but jessie
loads 1.55. Further, Debian has never used version 1.54 but skipped from
1.4 something in wheezy to 1.55 in jessie. Is there an way around this
problem.

I hate going off the official repository but the development of this
package is proceeding at a furious rate. It's basically an alpha release
but its the only game in town.

Any help will be seriously appreciated.


You could just create a link from the new version, that you have, to the 
older specific lib-version in /usr/lib/x86_64-linux-gnu/. It just might 
jump up and work. It's easiest enough to try. Too bad they don't just 
make the depend on version 1.54 or newer. Then, if 1.55 works, report 
the obvious error out to the project.


Trouble-shooting with a shot gun. Ric



--
My father, Victor Moore (Vic) used to say:
"There are two Great Sins in the world...
..the Sin of Ignorance, and the Sin of Stupidity.
Only the former may be overcome." R.I.P. Dad.
http://linuxcounter.net/user/44256.html


--
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org 
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org

Archive: https://lists.debian.org/55579bcc.6020...@gmail.com

Re: Wrong library versions

[Sven Joachim]

On 2015-05-16 19:43 +0200, Gary Roach wrote:

> I would put this on the freeCAD forum except I have been trying for
> several days to get authorization to join without success. So:
>
> The copy of freeCAD is version 0.14 on all versions of Debian. I'm
> using jessie with amd64 software. I want to ppa the 0.15 version from
> the freeCAD web site. Unfortunately, 0.15 requires libboost 1.54 but
> jessie loads 1.55. Further, Debian has never used version 1.54 but
> skipped from 1.4 something in wheezy to 1.55 in jessie. Is there an
> way around this problem.

The ppa for Ubuntu 15.04 uses libboost 1.55 AFAICS.  However, the
packages there might depend on libraries which are newer than in Jessie.

> I hate going off the official repository but the development of this
> package is proceeding at a furious rate. It's basically an alpha
> release but its the only game in town.
>
> Any help will be seriously appreciated.

The best method is probably to build from source.  If that's too
involved for you and the binary packages from the Ubuntu 15.04 ppa don't
work, it should be possible to obtain libboost1.54 packages from
snapshot.debian.org.

Good luck,
Sven


-- 
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org 
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: https://lists.debian.org/877fs8xqgf@turtle.gmx.de

Re: out of the box wifi adapter

[briand]

On Fri, 15 May 2015 17:09:59 -0600
Bob Proulx  wrote:

> Raymond Jennings wrote:
> > I wound up buying a 100 foot cat5 cable and running it from the house to
> > the trailer :P
> 
> My perspective is that nothing is as reliable as hardline wire!  It
> will be much more immune to radio noise trouble.  Speedy and
> reliable.  Wire will almost always be my choice if possible.
> 

you know the joke about wireless, right ?

it's a lossy, expensive cable.


-- 
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org 
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: https://lists.debian.org/20150516130144.0a68a...@cedar.deldotd.com

why are libraries in jessi more up to date

[Anil Duggirala]

Im a newbie and would like to know why libraries in Jessie are some much
more up to date than in wheezy ? If the libraries have been tested and
are stable then why arent they available in the wheezy repositories. I
had a terrible time, trying to get a newer version of glibc to play some
games in wheezy, and the version in jessie is much more up to date,
thanks for the info,


-- 
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org 
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: 
https://lists.debian.org/1431806505.1026848.270500385.44d15...@webmail.messagingengine.com

Re: Wrong library versions

[Lisi Reisz]

On Saturday 16 May 2015 20:38:56 Sven Joachim wrote:
> it should be possible to obtain libboost1.54 packages from
> snapshot.debian.org.

When Debian never used it???

> Further, Debian has never used version 1.54 but
> skipped from 1.4 something in wheezy to 1.55 in jessie. Is there an
> way around this problem.


Lis


-- 
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org 
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: https://lists.debian.org/201505162104.23141.lisi.re...@gmail.com

Re: Openbox: which packages install to have sound?

[briand]

On Fri, 15 May 2015 22:24:51 +
Rodolfo Medina  wrote:

> Pete Orrall  writes:
> 
> >>> after installing the packages (- bluez-alsa) you need to configure alsa
> >>> by creating .asoundrc file
> >>
> >> Thanks, but I don't know how.
> >
> > I'm running openbox on my Wheezy systems at home (a ThinkPad and a
> > massive workstation) and haven't needed to create an .asoundrc file.
> >
> >>> or, if the default device is correct, use alsamixer to turn on volumes of
> >>> the default card.
> >>
> >> By running alxamixer I turned all volumes on.  But still no sound.
> >
> > Other questions:
> >
> > 1) What is your sound card's make/model?
> > 2) What are you using as a listening device, ie headphones, basic
> > multimedia speakers, stereo receiver?
> > 3) Did you check your connections.  Are your (assuming) speakers
> > plugged into the audio OUT of your soundcard, and not MIC or Line IN?
> > 4) Did you check volume levels on speakers?
> 
> Many thanks to you too.  It's all right now: with alsamixer, I needed unmuting
> everything.
> 

one trap to watch out for is the audio device enables.  i have audio engine 
speakers and for some reason they were always disabled on boot.  i had to add:

set-default-sink 2
set-default-sink alsa_output.usb-Audioengine_Audioengine_2_-00-A2.analog-stereo

to my /etc/pulse/default.pa file, and it was a royal pain in the neck to figure 
out that i needed to do that.

just letting you know in case things seem to break on reboot.

Brian


-- 
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org 
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: https://lists.debian.org/20150516130358.408b5...@cedar.deldotd.com

Re: Wrong library versions

[Sven Joachim]

On 2015-05-16 22:04 +0200, Lisi Reisz wrote:

> On Saturday 16 May 2015 20:38:56 Sven Joachim wrote:
>> it should be possible to obtain libboost1.54 packages from
>> snapshot.debian.org.
>
> When Debian never used it???

That would be a problem, but it's not actually the case:
http://snapshot.debian.org/package/boost1.54/.

> 
>> Further, Debian has never used version 1.54 but
>> skipped from 1.4 something in wheezy to 1.55 in jessie.

This means that boost versions 1.50 through 1.54 have not been in a
_stable_ Debian release, but most of them were in unstable at some
time.

Cheers,
   Sven


-- 
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org 
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: https://lists.debian.org/87oalkw9x9@turtle.gmx.de

Re: Wrong library versions

[Lisi Reisz]

On Saturday 16 May 2015 21:21:22 Sven Joachim wrote:
> On 2015-05-16 22:04 +0200, Lisi Reisz wrote:
> > On Saturday 16 May 2015 20:38:56 Sven Joachim wrote:
> >> it should be possible to obtain libboost1.54 packages from
> >> snapshot.debian.org.
> >
> > When Debian never used it???
>
> That would be a problem, but it's not actually the case:
> http://snapshot.debian.org/package/boost1.54/.
>
> > 
> >
> >> Further, Debian has never used version 1.54 but
> >> skipped from 1.4 something in wheezy to 1.55 in jessie.
>
> This means that boost versions 1.50 through 1.54 have not been in a
> _stable_ Debian release, but most of them were in unstable at some
> time.

Ah!  Thank you.  That raises all sorts of questions for another time/thread.

Lisi


-- 
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org 
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: https://lists.debian.org/201505162134.50300.lisi.re...@gmail.com

Re: why are libraries in jessi more up to date

[Liam O'Toole]

On 2015-05-16, Anil Duggirala  wrote:
> Im a newbie and would like to know why libraries in Jessie are some much
> more up to date than in wheezy ? If the libraries have been tested and
> are stable then why arent they available in the wheezy repositories. I
> had a terrible time, trying to get a newer version of glibc to play some
> games in wheezy, and the version in jessie is much more up to date,
> thanks for the info,

The vey meaning of "stable" in a Debian context is that software
versions don't (usually) change over the course of a release. Therefore
it's no surprise that libraries in jessie (released last month) are more
up-to-date than those in wheezy (released in 2013).

-- 

Liam



-- 
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org 
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: https://lists.debian.org/slrnmlfnif.tmg.liam.p.otoole@dipsy.tubbynet

Re: jessie installation problem on arm sheevaplug

[Rick Thomas]

On May 16, 2015, at 10:33 AM, Rodrigo Valiña Gutiérrez  
wrote:

> I had the same problem installing Debian 8 'Jessie' on a SheevaPlug.
> 
> I solved it temporarily by doing the following:
> 
> - In u-boot:
> 
> setenv machid 0692
> saveenv
> 
> - Then install normally. The 'make the system bootable' phase will fail 
> because flash-kernel fails:
>  /var/log/installer/syslog:
> May 16 13:47:28 in-target: Setting up u-boot-tools (2014.10+dfsg1-5) ...^M
> 4-kirkwood
> May 16 13:47:46 in-target: Unsupported platform.
> May 16 13:47:46 flash-kernel-installer: error: flash-kernel failed
> May 16 13:47:46 main-menu[170]: WARNING **: Configuring 
> 'flash-kernel-installer' failed with error code 1
> May 16 13:47:46 main-menu[170]: WARNING **: Menu item 
> 'flash-kernel-installer' failed.
> 
> 
> - Then select 'execute a shell' and write:
> 
> cd /target/boot/
> /target/usr/bin/mkimage -A arm -O linux -T kernel  -C none -n uImage  -a 
> 0x8000 -e 0x8000 -d vmlinuz uImage
> /target/usr/bin/mkimage -A arm -O linux -T ramdisk -C none -n uInitrd 
> -d initrd.img  uInitrd
> 
> - It may be neccesary to change 0x8000 to 0x0080 in both cases, but 
> in my case it worked the way above.
> - Then 'exit' the shell and select 'continue without boot loader'.
> - I think that this last phase of mkimage should be repeated on every kernel 
> upgrade because I think flash-kernel (which calls mkimage) will fail again.

Thanks for the analysis, Rodrigo!

Could you submit a bug report against uboot-mkimage so the rest of us users of 
sheevaplug devices can get a working system without having to work-around this 
bug?  I think it’s just a matter of having mkimage recognize the sheevaplug’s 
machid as valid, but I’m not an expert.

Hopefully!
Rick

--
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: https://lists.debian.org/341975e0-fffd-4480-a9ad-944fd06d2...@pobox.com

Re: jessie installation problem on arm sheevaplug

[Martin Michlmayr]

* Rick Thomas  [2015-05-16 17:47]:
> > - In u-boot:
> > 
> > setenv machid 0692
> > saveenv

This is not the correct solution.

The problem is that there are different ways to boot on ARM machines.
The old way was for the boot loader to pass a machine ID to the kernel
which would tell the kernel which machine it's running on.  The new
way requires u-boot to pass a "device tree" to the kernel which
describes the hardware components of the system. (The workaround
suggested here simply tells the kernel a wrong machine ID and that
works because that particular device has not been converted over to
device tree yet, but this is not a good solution since you're telling
the kernel a wrong device, so it's possible some hardware components
won't work correctly.)

The u-boot in Debian passes the machine ID (because that's how you
configured it) but not the device tree.  Newer kernels require the
device tree on the SheevaPlug and no longer support the machine ID,
which is why you get the error about the machine ID not being known.

Ideally, u-boot would pass the device tree to the kernel, but this is
currently not done in Debian's u-boot (see #782293).

So the best solution now is to append the device tree blob (DTB) to
the kernel in the installer.  This way, the kernel will find the
correct device tree and can boot (and everything else will work since
flash-kernel already appends the DTB on the SheevaPlug).

I've to catch a flight now but I'll post a kernel image with the DTB
tomorrow.

Sorry for not fixing this earlier.

-- 
Martin Michlmayr
http://www.cyrius.com/


-- 
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org 
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: https://lists.debian.org/20150517013718.ga5...@jirafa.cyrius.com

Re: jessie installation problem on arm sheevaplug

[Martin Michlmayr]

* Martin Michlmayr  [2015-05-16 21:37]:
> So the best solution now is to append the device tree blob (DTB) to
> the kernel in the installer.  This way, the kernel will find the
> correct device tree and can boot (and everything else will work since
> flash-kernel already appends the DTB on the SheevaPlug).

Here's a test image.

Take the kernel from http://www.cyrius.com/tmp/sheevaplug/uImage
Take the ramdisk from 
http://ftp.debian.org/debian/dists/jessie/main/installer-armel/current/images/kirkwood/netboot/marvell/sheevaplug/uInitrd
Boot it as described here: 
http://www.cyrius.com/debian/kirkwood/sheevaplug/install/

Does this boot?

This is how I prepare the image:

wget 
http://ftp.debian.org/debian/dists/jessie/main/installer-armel/current/images/kirkwood/device-tree/kirkwood-sheevaplug.dtb
wget 
http://ftp.debian.org/debian/dists/jessie/main/installer-armel/current/images/kirkwood/netboot/marvell/sheevaplug/uImage
# Remove the u-boot header
dd if=uImage of=kernel.without bs=1 skip=64
rm -f uImage
# Append device tree
cat kirkwood-sheevaplug.dtb >> kernel.without
# Create new uImage
sudo apt-get install u-boot-tools
mkimage -A arm -O linux -T kernel -C none -a 0x8000 -e 0x8000 -n 
"Debian kernel" -d kernel.without uImage

-- 
Martin Michlmayr
http://www.cyrius.com/


-- 
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org 
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: https://lists.debian.org/20150517015607.ga6...@jirafa.cyrius.com

Re: Re: jessie installation problem on arm sheevaplug

[Rodrigo Valiña Gutiérrez]

I am not an expert...

The workaround just worked, but I don't know whether "0692
Marvell RD-88F6281 Reference Board"
is a valid machid for the sheevaplug, instead of the 'original' 0831.

At the beggining it worked, but now I have a problem: the sheevaplug
ethernet subsystem does not work well...
It does not get an IP by DHCP and assigning a static one does not work either...
I suspect that is caused by the workaround but I don't know.

So I do not recommend doing the procedure/workaround of changing machid,
as it may be unsafe and I warn thay may damage the hardware.

I hope Martin's solution will work... Where will you post the kernel image?

Re: why are libraries in jessi more up to date

[Gary Dale]

On 16/05/15 08:18 PM, Liam O'Toole wrote:

On 2015-05-16, Anil Duggirala  wrote:

Im a newbie and would like to know why libraries in Jessie are some much
more up to date than in wheezy ? If the libraries have been tested and
are stable then why arent they available in the wheezy repositories. I
had a terrible time, trying to get a newer version of glibc to play some
games in wheezy, and the version in jessie is much more up to date,
thanks for the info,

The vey meaning of "stable" in a Debian context is that software
versions don't (usually) change over the course of a release. Therefore
it's no surprise that libraries in jessie (released last month) are more
up-to-date than those in wheezy (released in 2013).



Just to put that in context. I had a server which originally ran Squeeze 
without problems. I upgraded to Wheezy some time later, again without 
problems. Somewhere over the course of Wheezy updates however, something 
broke.


The motherboard had USB3 ports and AMD graphics (although it was 
headless - just in case I needed to hook a monitor up) and the IOMMU 
started acting up (Strangely I have a workstation running Jessie with a 
similar problem). Even though the updates were mainly security fixes, I 
lost the ability to remotely (re)start the machine. My ssh connection 
couldn't establish because the IOMMU code for this particular board was 
broken. I had to be on site with monitor and keyboard to boot to repair 
mode then manually start the services I needed.


Last week I found myself having to upgrade to Jessie to fix the issue. 
Although Jessie code is what is currently causing the problem with my 
workstation, it fixed the problem on the server.


Stories like this abound, which is why people are leery about upgrading 
critical systems. Stable means that only serious bug fixes and security 
updates are issued, not feature enhancements. Limiting the numbers of 
updates means that larger installations get to test them before running 
them live, while smaller setups like small or home offices can usually 
feel safe performing updates.


Normally I wouldn't upgrade a server until the .1 release of the new 
Debian stable. In this case, I had a problem so I took a chance that 
upgrading on the .0 release would fix more than it broke. Thanks to the 
quality of the Debian development process, the upgrade went smoothly and 
the system is running properly again.


If you want to keep up with the latest libraries, etc., run 
Debian/Testing permanently. This is fairly stable but you will encounter 
problems from time to time, as you will with any "rolling release" distro.



--
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org 
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org

Archive: https://lists.debian.org/55580ee4.8040...@torfree.net

strange booting behavior

[gofloss gofloss]

please tell me if any further information is needed.

i am running wheezy and i want to upgrade to jessie.  i
can't do that until i have an immediately-usable backup
drive booting properly.  in my case, this means the same
environment (not a rescue cd).

for my second drive i will happily boot from either my new
internal toshiba or my thumb drive.  i don't care which one.

everything boots ok on my main internal drive.  the computer
runs bios and i formatted all disks to use mbr.  i don't use
lvm or raid.

i tried getting both the toshiba and the thumb drive to
boot.  to make each drive boot, i formatted as follows: ext2
for boot and luks with ext4 on root.  for example, on
toshiba, i have /boot on /dev/sda1 and /root on /dev/sda3.

i copied to root and to boot, confirmed that the copy was
perfect (using separate unix tools), edited the target's
crypttab and fstab (to set uuid and /dev/mapper/name, confirmed all of
the uuids etc.,
prepared a chroot (proc, sys, dev), entered the chroot, and
ran "update-initramfs -u -k all; update-grub;
dpkg-reconfigure grub-pc".  i got no errors.  i selected the
drive, not a partition, for the boot device.  (i was told
that that dpkg-reconfigure runs grub-install and is the
better option in this case because an upgrade could screw
everything up otherwise.)

both drives did not boot correctly, but in different ways.

the thumb drive is quick to describe.  it's in the bios boot
sequence, but even though i put grub on it, it doesn't boot.
it just defaults to the next item on the sequence.  so
perhaps my computer is not capable of booting thumb drive?

the rest of this email will be about my new toshiba internal
drive, which DOES run grub, but does not boot correctly.

grub comes up, i select the default debian version.  the
kernel loads and starts doing things for 7 seconds.

(by the way, i was able to notice that around 4 seconds, in
among a whole bunch of usb messages, it says something like
"waiting for encrypted source device...".  but there are too
many usb messages and scrolling does not work well so i
could not determine whether that sequence continued.)

then booting does nothing until 64 seconds.  the last boot
messages before this were attaching hard drives (it attached
sda sdb sdc i think; sdc is merely an external usb device).

then two lines saying USB disconnect, device number #.

then more messages.

then drops into a shell, initramfs.  the error message is
roughly like the following (transcribed manually, "..." not
in the original).

  Check cryptopts=source= bootarg:cat/proc/command line or
  missing modules, device:cat/proc/modules ls/dev
  -r ALERT!  /dev/disk/by-uuid/a89...32 does not exist
  dropping to a shell!

i do not understand this error message.  what does -r mean?  that partition
exists.  the uuid refers to /dev/sda3 (the raw partition that
contains encrypted root).

in fact, in the initrd busybox shell, i can do cryptsetup
luksOpen /dev/sda3 toshiba-root.  i do not know how or where
to mount it, however.  mounting it on / not work.

that seems to suggest that it exists, in contrast to the error message.

strangely, despite having dropped into an initramfs shell,
the kernel keeps spewing USB messages every 30 seconds or
so.  these start with usb disconnect, then new usb device
and it mentions my mouses and stuff.  i have to clear the
screen each time.

/proc/cmdline says
BOOT_IMAGE=/vmlinuz-3.2.0-4-amd64 root=/dev/mapper/toshibaroot ro

too many modules to transcribe, but include dm-crypt and dm-mod.

i would be very grateful for any help.

i am not subscribed to this list.


-- 
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org 
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: 
https://lists.debian.org/cadyyg0mbbuka3zwpn6f2svon5f5wd8cyt-hhsfz36erjdoh...@mail.gmail.com