Re: Error when compiling drivers for Asus PEB-10G/57811-1S

[Leslie Rhorer]

The motherboard has a built-in Ethernet port.

Re: Error when compiling drivers for Asus PEB-10G/57811-1S

[Leslie Rhorer]

Backup:/# ip link
1: lo:  mtu 65536 qdisc noqueue state UNKNOWN mode 
DEFAULT group default 
link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
2: eth2:  mtu 1500 qdisc pfifo_fast state UP 
mode DEFAULT group default qlen 1000
link/ether 50:46:5d:65:15:9c brd ff:ff:ff:ff:ff:ff
3: eth0:  mtu 1500 qdisc noop portid 086266a14051 state 
DOWN mode DEFAULT group default qlen 1000
link/ether 08:62:66:a1:40:51 brd ff:ff:ff:ff:ff:ff


Also:

Backup:/# ifconfig -a
eth0  Link encap:Ethernet  HWaddr 08:62:66:a1:40:51  
  inet addr:192.168.1.91  Bcast:192.168.1.255  Mask:255.255.255.0
  BROADCAST MULTICAST  MTU:1500  Metric:1
  RX packets:0 errors:0 dropped:0 overruns:0 frame:0
  TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
  collisions:0 txqueuelen:1000 
  RX bytes:0 (0.0 B)  TX bytes:0 (0.0 B)
  Interrupt:36 Memory:d300-d37f 

eth2  Link encap:Ethernet  HWaddr 50:46:5d:65:15:9c  
  inet addr:192.168.1.51  Bcast:192.168.1.255  Mask:255.255.255.0
  inet6 addr: fe80::5246:5dff:fe65:159c/64 Scope:Link
  UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
  RX packets:47553 errors:0 dropped:2 overruns:0 frame:0
  TX packets:272930 errors:0 dropped:0 overruns:0 carrier:0
  collisions:0 txqueuelen:1000 
  RX bytes:15175818 (14.4 MiB)  TX bytes:392583400 (374.3 MiB)

loLink encap:Local Loopback  
  inet addr:127.0.0.1  Mask:255.0.0.0
  inet6 addr: ::1/128 Scope:Host
  UP LOOPBACK RUNNING  MTU:65536  Metric:1
  RX packets:52 errors:0 dropped:0 overruns:0 frame:0
  TX packets:52 errors:0 dropped:0 overruns:0 carrier:0
  collisions:0 txqueuelen:0 
  RX bytes:5802 (5.6 KiB)  TX bytes:5802 (5.6 KiB)

Rappel : BeMyStreet devient gratuit pour les pros

[BeMyStreet]

BeMyStreet devient gratuit pour les pros.

Nous avons une bonne nouvelle pour vous ! BeMyStreet devient gratuit pour les 
professionnels pour votre plus grand plaisir. Alors ne vous en privez surtout 
pas, vendez en ligne facilement et profitez de tous les avantages BeMyStreet :

***Visibilité***

Votre boutique apparaît dans chacune des rues de vos abonnés.


***Simplicité***

Gérez vos pages et votre vitrine simplement grâce à nos outils et nos conseils.


Multipliez vos contacts*

Les relations se tissent de proche en proche sur le réseau social.


***Efficacité***

Communiquez efficacement grâce à vos pages, vos actualités ou la messagerie.


**Opportunité***

Avancez et sautez le pas de la vente en ligne, avec BeMyStreet c'est simple.


**Aucun risque**

Accédez à ce concept unique, dynamique et innovateur pour un tarif sans risque.


BeMyStreet est un réseau social orienté vente en ligne sur lequel les 
professionnels bénéficient d'outils simples et efficaces pour être visibles, 
communiquer, et développer leur activité en ligne.

BeMystreet se rémunère principalement sur les commissions de vente de vos 
produits, cela vous garantit que nous ferons toujours le maximum pour que vous 
vendiez vos produits ! Alors inscrivez-vous, parlez-en autour de vous et 
partagez...

Avec la gratuité, plus aucun risque pour vous, vous avez tout à gagner...


Découvrir ici : http://bemystreet.com

Vous avez une question ? N'hésitez pas à nous contacter en répondant à ce mail.

A tout de suite sur BeMyStreet
bemystreet.com

Re: Monitor de red

[Pablo Daniel Estigarribia Davyt]

Si tienes switches administrables puedes agregar observium también.

Lo uso y su instalación y mantenimiento lo hago con ansible al.igual que
nagios y todos sus agregados.

No tengo buena conexión ahora a Internet pero si te interesan los roles
ansible, los que yo uso están bajo la organización de github coffeeitworks,
todos funcionan con debian.
El 19/02/2017 22:51, "MARCELO IGNACIO nigro"  escribió:

> Hola
>
> Zabbix. Es exelente por rodos laso.
> Nagios tambien lo he probado
> Cacto menos complejidad
>
> Todo es segun lo que te quieras complucar al comienzo.
>
> Yo te zabbix
>
> Saludos
>
> Marcelo Nigro
>
> El 19/2/2017 22:06, "Santiago"  escribió:
>
>> Nagios es, sin ninguna duda, tu mejor opción.
>>
>>
>> El 19/02/17 a las 01:07, Luciana Coca escribió:
>> > Muy buenas a todos!
>> >
>> > Estoy buscando un monitor de red que me muestre en qué momentos se ha
>> > perdido señal en la red (red cableada).
>> > He investigado y vi que hay una gran variedad de monitores pero no me
>> > decidí por ninguno aún. Prefiero que ustedes, que tienen más
>> > conocimiento que yo, me recomienden alguno. No quiero meter la pata
>> > instalado y desinstalando (soy algo nueva en Debian).
>> > Podrían recomendarme monitores?
>> >
>> > Muchas gracias!
>> >
>> > Saludos cordiales,
>> > Luciana.
>> >
>>
>>

Re: Monitor de red

[MARCELO IGNACIO nigro]

Hola

Zabbix. Es exelente por rodos laso.
Nagios tambien lo he probado
Cacto menos complejidad

Todo es segun lo que te quieras complucar al comienzo.

Yo te zabbix

Saludos

Marcelo Nigro

El 19/2/2017 22:06, "Santiago"  escribió:

> Nagios es, sin ninguna duda, tu mejor opción.
>
>
> El 19/02/17 a las 01:07, Luciana Coca escribió:
> > Muy buenas a todos!
> >
> > Estoy buscando un monitor de red que me muestre en qué momentos se ha
> > perdido señal en la red (red cableada).
> > He investigado y vi que hay una gran variedad de monitores pero no me
> > decidí por ninguno aún. Prefiero que ustedes, que tienen más
> > conocimiento que yo, me recomienden alguno. No quiero meter la pata
> > instalado y desinstalando (soy algo nueva en Debian).
> > Podrían recomendarme monitores?
> >
> > Muchas gracias!
> >
> > Saludos cordiales,
> > Luciana.
> >
>
>

Re: Monitor de red

[Ernesto Escobedo]

Nagios es bueno pero no te grafica servicios o te da un historico a si que
lo conbinaria con cacty por otro lado el icinga te da ya esos dolos
funcionalidades juntas .


Munin tambien es otra opcion
Pero para minitoreo de red yo pondria solo el ntop

El 19/02/2017 19:33, "Cristian Mitchell"  escribió:



El 19 feb. 2017 10:04 PM, "Santiago" 
escribió:

Nagios es, sin ninguna duda, tu mejor opción.


El 19/02/17 a las 01:07, Luciana Coca escribió:
> Muy buenas a todos!
>
> Estoy buscando un monitor de red que me muestre en qué momentos se ha
> perdido señal en la red (red cableada).
> He investigado y vi que hay una gran variedad de monitores pero no me
> decidí por ninguno aún. Prefiero que ustedes, que tienen más
> conocimiento que yo, me recomienden alguno. No quiero meter la pata
> instalado y desinstalando (soy algo nueva en Debian).
> Podrían recomendarme monitores?
>
> Muchas gracias!
>
> Saludos cordiales,
> Luciana.
>

Si es para monitorear servicio zabbix
Si es para monitorear tráfico tshark o Wireshark

Re: Monitor de red

[Cristian Mitchell]

El 19 feb. 2017 10:04 PM, "Santiago" 
escribió:

Nagios es, sin ninguna duda, tu mejor opción.


El 19/02/17 a las 01:07, Luciana Coca escribió:
> Muy buenas a todos!
>
> Estoy buscando un monitor de red que me muestre en qué momentos se ha
> perdido señal en la red (red cableada).
> He investigado y vi que hay una gran variedad de monitores pero no me
> decidí por ninguno aún. Prefiero que ustedes, que tienen más
> conocimiento que yo, me recomienden alguno. No quiero meter la pata
> instalado y desinstalando (soy algo nueva en Debian).
> Podrían recomendarme monitores?
>
> Muchas gracias!
>
> Saludos cordiales,
> Luciana.
>

Si es para monitorear servicio zabbix
Si es para monitorear tráfico tshark o Wireshark

Re: Monitor de red

[Santiago]

Nagios es, sin ninguna duda, tu mejor opción.


El 19/02/17 a las 01:07, Luciana Coca escribió:
> Muy buenas a todos!
>
> Estoy buscando un monitor de red que me muestre en qué momentos se ha
> perdido señal en la red (red cableada).
> He investigado y vi que hay una gran variedad de monitores pero no me
> decidí por ninguno aún. Prefiero que ustedes, que tienen más
> conocimiento que yo, me recomienden alguno. No quiero meter la pata
> instalado y desinstalando (soy algo nueva en Debian).
> Podrían recomendarme monitores?
>
> Muchas gracias!
>
> Saludos cordiales,
> Luciana.
>

Correction: Re: Matrox Meteor frame grabber.

[peter]

*   From: Dan Ritter  E.

-- 

123456789 123456789 123456789 123456789 123456789 123456789 123456789
Tel: +1 360 639 0202  Pender Is.: +1 250 629 3757
http://easthope.ca/Peter.html  Bcc: peter at easthope. ca

Re (3): /etc/dhcp3 in jessie.

[peter]

*   From: Dan Ritter 
123456789 123456789 123456789 123456789 123456789 123456789 123456789
Tel: +1 360 639 0202  Pender Is.: +1 250 629 3757
http://easthope.ca/Peter.html  Bcc: peter at easthope. ca

Re: stretch, startx impossible

[JF Straeten]

Re,

On Sun, Feb 19, 2017 at 10:11:46PM +0100, David Pinson wrote:

> Est-ce que ce lien pourrait vous aider ?
> https://github.com/dnschneid/crouton/issues/2926

Tkx, déjà vu, mais pas exploitable :-/


-- 

JFS.

Re (2): /etc/dhcp3 in jessie.

[peter]

*   From: Brian 
123456789 123456789 123456789 123456789 123456789 123456789 123456789
Tel: +1 360 639 0202  Pender Is.: +1 250 629 3757
http://easthope.ca/Peter.html  Bcc: peter at easthope. ca

USB Token with power problem.

[GUSTAVO MARTINELLI]

*Hi, Guys!*

I am trying to use my USB Token on Debian Jessie, but it turns on the
light, and in three seconds, it turns off. So, the USB Token stops working.

I found in the Internet that it can be a power problem. They recommended to
run the following command:


*echo 'on' | tee /sys/bus/usb/devices/usb2/power/level*

It changes the value on that file, but the behavior remains the same.

In this way, I ask for help. My Debian informations are below.

*uname -na*
Linux ncc1701 3.16.0-4-amd64 #1 SMP Debian 3.16.39-1 (2016-12-30) x86_64
GNU/Linux

*lsusb*
Bus 001 Device 002: ID 8087:8001 Intel Corp.
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 003 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 002 Device 007: ID 0bda:5754 Realtek Semiconductor Corp.
Bus 002 Device 006: ID 0bda:0129 Realtek Semiconductor Corp. RTS5129 Card
Reader Controller
Bus 002 Device 005: ID 04f3:2013 Elan Microelectronics Corp.
Bus 002 Device 004: ID 8087:0a2a Intel Corp.
Bus 002 Device 011: ID 046d:c52f Logitech, Inc. Unifying Receiver
*Bus 002 Device 015: ID 1059:0017 Giesecke & Devrient GmbH (that is my USB
Token)*
Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub

*lsusb -t*
/:  Bus 03.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/4p, 5000M
/:  Bus 02.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/11p, 480M
*|__ Port 1: Dev 15, If 0, Class=Chip/SmartCard, Driver=, 12M*
|__ Port 3: Dev 11, If 0, Class=Human Interface Device, Driver=usbhid,
12M
|__ Port 3: Dev 11, If 1, Class=Human Interface Device, Driver=usbhid,
12M
|__ Port 5: Dev 4, If 0, Class=Wireless, Driver=btusb, 12M
|__ Port 5: Dev 4, If 1, Class=Wireless, Driver=btusb, 12M
|__ Port 6: Dev 5, If 0, Class=Human Interface Device, Driver=usbhid,
12M
|__ Port 7: Dev 6, If 0, Class=Vendor Specific Class, Driver=rtsx_usb,
480M
|__ Port 8: Dev 7, If 0, Class=Video, Driver=uvcvideo, 480M
|__ Port 8: Dev 7, If 1, Class=Video, Driver=uvcvideo, 480M
/:  Bus 01.Port 1: Dev 1, Class=root_hub, Driver=ehci-pci/2p, 480M
|__ Port 1: Dev 2, If 0, Class=Hub, Driver=hub/8p, 480M

*dmesg | grep 1059*
[1.612648] usb 2-1: New USB device found, idVendor=1059, idProduct=0017
[ 1002.610934] usb 2-1: New USB device found, idVendor=1059, idProduct=0017
[ 1053.523985] usb 2-2: New USB device found, idVendor=1059, idProduct=0017
[ 1090.249734] usb 2-2: New USB device found, idVendor=1059, idProduct=0017
[ 1762.296078] usb 2-1: New USB device found, idVendor=1059, idProduct=0017
[ 1788.281211] usb 2-1: New USB device found, idVendor=1059, idProduct=0017
[ 1794.658211] usb 2-2: New USB device found, idVendor=1059, idProduct=0017
[ 1997.061059] cfg80211:   (5724 KHz - 6372 KHz @ 216 KHz),
(N/A, 0 mBm), (N/A)
[ 7282.511744] usb 2-1: New USB device found, idVendor=1059, idProduct=0017

*dmesg | grep 0017*
[0.744411] Freeing unused kernel memory: 216K (8800017ca000 -
88000180)
[1.612648] usb 2-1: New USB device found, idVendor=1059, idProduct=0017
[ 1002.610934] usb 2-1: New USB device found, idVendor=1059, idProduct=0017
[ 1053.523985] usb 2-2: New USB device found, idVendor=1059, idProduct=0017
[ 1090.249734] usb 2-2: New USB device found, idVendor=1059, idProduct=0017
[ 1762.296078] usb 2-1: New USB device found, idVendor=1059, idProduct=0017
[ 1788.281211] usb 2-1: New USB device found, idVendor=1059, idProduct=0017
[ 1794.658211] usb 2-2: New USB device found, idVendor=1059, idProduct=0017
[ 7282.511744] usb 2-1: New USB device found, idVendor=1059, idProduct=0017

Thank you for any help!

Regards,
Gustavo Martinelli

Re: Error when compiling drivers for Asus PEB-10G/57811-1S

[Leslie Rhorer]

It's still not working, but the card is in the udev file, and ifconfig -a shows 
the interface.  When I try to bring it up, however, it gives me an error:

Backup:/# ifconfig -a   
  
eth0  Link encap:Ethernet  HWaddr 08:62:66:a1:40:51 
 
  inet addr:192.168.1.97  Bcast:192.168.1.255  Mask:255.255.255.0   
 
  BROADCAST MULTICAST  MTU:1500  Metric:1   
 
  RX packets:0 errors:0 dropped:0 overruns:0 frame:0
  TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
  collisions:0 txqueuelen:1000 
  RX bytes:0 (0.0 B)  TX bytes:0 (0.0 B)
  Interrupt:36 Memory:d300-d37f 

eth2  Link encap:Ethernet  HWaddr 50:46:5d:65:15:9c  
  inet addr:192.168.1.51  Bcast:192.168.1.255  Mask:255.255.255.0
  inet6 addr: fe80::5246:5dff:fe65:159c/64 Scope:Link
  UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
  RX packets:180057 errors:0 dropped:2 overruns:0 frame:0
  TX packets:1502041 errors:0 dropped:0 overruns:0 carrier:0
  collisions:0 txqueuelen:1000 
  RX bytes:24120043 (23.0 MiB)  TX bytes:2220773875 (2.0 GiB)

loLink encap:Local Loopback  
  inet addr:127.0.0.1  Mask:255.0.0.0
  inet6 addr: ::1/128 Scope:Host
  UP LOOPBACK RUNNING  MTU:65536  Metric:1
  RX packets:58 errors:0 dropped:0 overruns:0 frame:0
  TX packets:58 errors:0 dropped:0 overruns:0 carrier:0
  collisions:0 txqueuelen:0 
  RX bytes:6254 (6.1 KiB)  TX bytes:6254 (6.1 KiB)

Backup:/# ifconfig eth0 192.168.1.97 up
SIOCSIFFLAGS: Cannot allocate memory
SIOCSIFFLAGS: Cannot allocate memory

Re: Error when compiling drivers for Asus PEB-10G/57811-1S

[Mark Fletcher]

On Sun, Feb 19, 2017 at 03:54:32AM -0800, Leslie Rhorer wrote:
> I purchased a couple of Asus PEB-10G/57811-1S 10G LAN adapters.  I am not 
> finding any pre-built binaries nor a .deb reporitory for these cards, so I am 
> attempting t o compile from scratch, but I get the following error during the 
> make operation:
> 
> Backup/Server-Main/Temp/netxtreme2-7.10.42/bnx2-2.710.30/src/bnx2.c: In 
> function ‘bnx2_rx_int’:
> /Backup/Server-Main/Temp/netxtreme2-7.10.42/bnx2-2.710.30/src/bnx2.c:3753:7: 
> error: ‘struct sk_buff’ has no member named ‘rxhash’
> skb->rxhash = rx_hdr->l2_fhdr_hash;
>^
> /usr/src/linux-headers-3.16.0-4-common/scripts/Makefile.build:268: recipe for 
> target '/Backup/Server-Main/Temp/netxtreme2-7.10.42/bnx2-2.710.30/src/bnx2.o' 
> failed
> 
> Does anyone have an ideas?  Are there any pre-built drivers for these cards 
> for Debian Jessie?
> 

As others on this thread have hinted, possibly less than completely 
clearly, this card is supported by the kernel and IF your particular 
kernel was built with support turned on, THEN all you should need is the 
firmware which is provided by a package deloptes pointed out.

I just checked in the stock Jessie kernel I am running, support for the 
BNX2 is included as a module. Assuming you are also using the stock 
Jessie kernel you get when you install Jessie (tell us if otherwise), 
you should have it as a module too. In that case, on detecting your 
hardware, if the hardware is healthy, udev should have automatically 
loaded the driver. So if you also install the firmware as deloptes 
pointed out, you should at least get the length of a functioning network 
card. Which is different from a functioning network connection you can 
actually use.

If you previously had another card installed, and that card is still 
present, you may have some futzing around to do to persuade the machine 
to bring up the new card and have it connect to the network. Let us know 
if that is so.

In the meantime, assuming you are using a stock kernel and not one you 
built yourself or had someone build for you, and assuming you have 
installed the firmware deloptes mentioned, what is the output of:

$ ip link

?

Mark

Re: Fstab Problem

[Stephen P. Molnar]

On 02/19/2017 01:39 PM, Jimmy Johnson wrote:

On 02/19/2017 04:37 AM, Stephen P. Molnar wrote:

This will probably turn out to be a forehead slapping red faced problem,
but this used to work.

I Had a Debian v-8.x catastrophe and had to reinstall.  I have several
hard drives on the computer and, of course the installer only found
/dev/sda.

Here are the results of blkid:

comp@AbNormal:~$ sudo blkid
[sudo] password for comp:
/dev/sdb1: UUID="d65867da-c658-4e35-928c-9dd2d6dd5742" TYPE="ext4"
PARTUUID="0003d403-01"
/dev/sdb2: UUID="007c1f16-34a4-438c-9d15-e3df601649ba" TYPE="ext4"
PARTUUID="0003d403-02"
/dev/sda1: UUID="3a2e7e1d-3365-447b-85c5-f454a2f0b446" TYPE="ext4"
PARTUUID="cdf775c6-01"
/dev/sda5: UUID="92727ce9-2cff-40f5-b6d0-e9580afdeef3" TYPE="swap"
PARTUUID="cdf775c6-05"

I edited fstab:

# /etc/fstab: static file system information.
#
# Use 'blkid' to print the universally unique identifier for a
# device; this may be used with UUID= as a more robust way to name
devices
# that works even if disks are added and removed. See fstab(5).
#
#
# / was on /dev/sda1 during installation
UUID=3a2e7e1d-3365-447b-85c5-f454a2f0b446 /   ext4
errors=remount-ro 0   1
# swap was on /dev/sda5 during installation
UUID=92727ce9-2cff-40f5-b6d0-e9580afdeef3 noneswapsw
  0   0
/dev/sr0/media/cdrom0   udf,iso9660 user,noauto 0   0

#UUID=d65867da-c658-4e35-928c-9dd2d6dd5742  /dev/sdb1 ext4
errors=remount-ro  0  1
#UUID=007c1f16-34a4-438c-9d15-e3df601649ba  /dev/sdb2 ext4
errors=remount-ro  0  1


I multi-boot and I like to keep things simple, including grub, I like a
neat menu.lst and fstab too and I always keep these things backed up
while installing a new system, this is the way I would do your fstab so
I can edit sdb1 and sdb2, note no auto mount on sdb1 and sdb2, but you
can now read and write.

/dev/sda1 / ext4 errors=remount-ro 0 1
/dev/sda5 none swap sw 0 0
/dev/sdb1 /mnt/sdb1 ext4 noauto,users,exec,relatime 0 0
/dev/sdb2 /mnt/sdb2 ext4 noauto,users,exec,relatime 0 0
/dev/sr0 /media/cdrom udf,iso9660 noauto,users 0 0

If you use the above you will need to make two folders in /mnt named
sdb1 and sdb2


What have I missed?


I don't think you missed anything, just didn't know what you where
doing. :)


Thanks in advance.


regard,


Not know what I'm doing is nothing new.

That's hardly a useful response.


--
Stephen P. Molnar, Ph.D.Life is a fuzzy set
www.molecular-modeling.net  Stochastic and multivariate
(614)312-7528 (c)
Skype: smolnar1

Re: Error when compiling drivers for Asus PEB-10G/57811-1S

[Leslie Rhorer]

Well, that's good to know, but it's not coming up.  I've never added an 
Ethernet adapter post-install, so I suspect I need to do something, but I am 
not sure what.  I did an lsmod, and the bnx2x module is loaded, but not being 
used.  I loaded the firmware, but I get this error during boot:

[   20.327836] bnx2x :07:00.0: firmware: failed to load 
bnx2x/bnx2x-e2-7.8.19.0.fw (-2)
[   20.327840] bnx2x :07:00.0: Direct firmware load failed with error -2
[   20.327842] bnx2x :07:00.0: Falling back to user helper
[   20.328247] bnx2x: [bnx2x_func_hw_init:5506(eth3)]Error loading firmware
[   20.328252] bnx2x: [bnx2x_nic_load:2685(eth3)]HW init failed, aborting

Re: stretch, startx impossible

[David Pinson]

Le 19/02/2017 à 21:42, JF Straeten a écrit :
> Lo,
>
>
> On Sun, Feb 19, 2017 at 09:20:52PM +0100, maderios wrote:
>
> [...]
>>> il m'est impossible de lancer startx. [...] 
>>> xf86EnableIOPorts: failed to set IOPL for I/O (Operation not
>>> permitted)
> [...]
>> As tu installé xinit? /usr/bin/startx fait partie du paquet xinit
> Oui, ce message apparaît en exécutant startx, justement...
>
> J'ai le même problème sur une stretch aussi.
>
> Apparemment, ça semble lié au fait que X n'est plus lancé avec les
> droits root, ni même suid root, mais en utilisateur, sous stretch,
> mais je n'ai pas encore eu le temps d'aller plus loin :-/
>
> A+
>

Bonsoir,

Est-ce que ce lien pourrait vous aider ?
https://github.com/dnschneid/crouton/issues/2926

-- 
Librement vôtre,
David P. 

Re: stretch, startx impossible

[JF Straeten]

Lo,


On Sun, Feb 19, 2017 at 09:20:52PM +0100, maderios wrote:

[...]
> >il m'est impossible de lancer startx. [...] 
> >xf86EnableIOPorts: failed to set IOPL for I/O (Operation not
> >permitted)

[...]
> As tu installé xinit? /usr/bin/startx fait partie du paquet xinit

Oui, ce message apparaît en exécutant startx, justement...

J'ai le même problème sur une stretch aussi.

Apparemment, ça semble lié au fait que X n'est plus lancé avec les
droits root, ni même suid root, mais en utilisateur, sous stretch,
mais je n'ai pas encore eu le temps d'aller plus loin :-/

A+

-- 

JFS.

Re: stretch, startx impossible

[jérémy prego]

Le 19/02/2017 à 21:20, maderios a écrit :

Bonjour
As tu installé xinit?
/usr/bin/startx fait partie du paquet xinit


oui, du moins il l'ait par défaut
jerem.

Re: stretch, startx impossible

[maderios]

On 02/19/2017 01:58 PM, jérémy prego wrote:

bonjour à tous,

après avoir installé Stretch sur une machine avec le bureau mate, il
m'est impossible de lancer startx. Google me donne plein de résultat
mais c'est trop vieux et les commande ne fonctionnent plus sur ma
stretch. L'erreur que j'ai est la suivante:
[82.260] xf86EnableIOPorts: failed to set IOPL for I/O (Operation
not permitted)

avec lightdm, ça fonctionne très bien par contre, mais je préférerai
utiliser startx.

je précise que le système vient d'être installé et que rien n'a été touché.


Bonjour
As tu installé xinit?
/usr/bin/startx fait partie du paquet xinit

--
Maderios

Re: Whats the alternative to .xinitrc

[Brian]

On Sun 19 Feb 2017 at 11:00:25 +0100, Vincent Lefevre wrote:

> On 2017-02-18 20:59:44 +, Brian wrote:
> > The advice in startx(1) is sound but nothing stops you using a ,xinitrc.
> > The command doesn't work in a ,xinitrc? Perhaps it is incorrect or the
> > DM ignores it.
> 
> AFAIK, .xinitrc is not used by DM's, in particular because X has
> already been started.

I'd agree with the first statement. I am very unsure about the reason
advanced.

-- 
Brian.

Re: Re: Whats the alternative to .xinitrc

[Brian]

On Sun 19 Feb 2017 at 09:53:41 +, Rob Brewer wrote:

> >> I am running up to date KDE Sid with SDDM but I need to start the gnome 
> >> keyring at x startup to satisfy Midori dependencies.
> >> 
> >> The Midori FAQ suggests adding  “export `gnome-keyring-daemon –start`” to 
> >> the historical .xinitrc but this seems to be ignored as does .xsession as 
> >> suggested by the startx man page.
> >> 
> >> As .xinitrc has worked OK in the past, how do I now set the user 
> >environment 
> >> when X starts?
> >
> >My .xsessionrc is functional. The magic happens in
> >   /etc/X11/Xsession.d/40x11-common_xsessionrc
> >
> > +---
> > | # This file is sourced by Xsession(5), not executed.
> > | 
> > | #Source user defined xsessionrc (locales and other environment variables)
> > | if [ -r "$USERXSESSIONRC" ]; then
> > |   . "$USERXSESSIONRC"
> > | fi
> > +---
> >
> >Attention: I'm running SysV init -- perhaps things are different in other
> >settings.
> 
> Thank you for your help, I was wrong footed by the man page which suggested 
> using .xsession not .xsessionrc so I guess the man page needs an update. 
> Looks 
> like it is now OK after changing to .xsessionrc.

The startx man page merely points out that .xsession is used on Debian,
not .xinitrc. Perhaps you mislead yourself by not reading the correct
document: Xsession(5).

-- 
Brian.

Re: Fstab Problem

[Jimmy Johnson]

On 02/19/2017 04:37 AM, Stephen P. Molnar wrote:

This will probably turn out to be a forehead slapping red faced problem,
but this used to work.

I Had a Debian v-8.x catastrophe and had to reinstall.  I have several
hard drives on the computer and, of course the installer only found
/dev/sda.

Here are the results of blkid:

comp@AbNormal:~$ sudo blkid
[sudo] password for comp:
/dev/sdb1: UUID="d65867da-c658-4e35-928c-9dd2d6dd5742" TYPE="ext4"
PARTUUID="0003d403-01"
/dev/sdb2: UUID="007c1f16-34a4-438c-9d15-e3df601649ba" TYPE="ext4"
PARTUUID="0003d403-02"
/dev/sda1: UUID="3a2e7e1d-3365-447b-85c5-f454a2f0b446" TYPE="ext4"
PARTUUID="cdf775c6-01"
/dev/sda5: UUID="92727ce9-2cff-40f5-b6d0-e9580afdeef3" TYPE="swap"
PARTUUID="cdf775c6-05"

I edited fstab:

# /etc/fstab: static file system information.
#
# Use 'blkid' to print the universally unique identifier for a
# device; this may be used with UUID= as a more robust way to name devices
# that works even if disks are added and removed. See fstab(5).
#
#
# / was on /dev/sda1 during installation
UUID=3a2e7e1d-3365-447b-85c5-f454a2f0b446 /   ext4
errors=remount-ro 0   1
# swap was on /dev/sda5 during installation
UUID=92727ce9-2cff-40f5-b6d0-e9580afdeef3 noneswapsw
  0   0
/dev/sr0/media/cdrom0   udf,iso9660 user,noauto 0   0

#UUID=d65867da-c658-4e35-928c-9dd2d6dd5742  /dev/sdb1 ext4
errors=remount-ro  0  1
#UUID=007c1f16-34a4-438c-9d15-e3df601649ba  /dev/sdb2 ext4
errors=remount-ro  0  1


I multi-boot and I like to keep things simple, including grub, I like a 
neat menu.lst and fstab too and I always keep these things backed up 
while installing a new system, this is the way I would do your fstab so 
I can edit sdb1 and sdb2, note no auto mount on sdb1 and sdb2, but you 
can now read and write.


/dev/sda1 / ext4 errors=remount-ro 0 1
/dev/sda5 none swap sw 0 0
/dev/sdb1 /mnt/sdb1 ext4 noauto,users,exec,relatime 0 0
/dev/sdb2 /mnt/sdb2 ext4 noauto,users,exec,relatime 0 0
/dev/sr0 /media/cdrom udf,iso9660 noauto,users 0 0

If you use the above you will need to make two folders in /mnt named 
sdb1 and sdb2



What have I missed?


I don't think you missed anything, just didn't know what you where doing. :)


Thanks in advance.


regard,
--
Jimmy Johnson

Debian Sid/Testing - Plasma 5.8.4 - EXT4 at sda15
Registered Linux User #380263

Re: Error when compiling drivers for Asus PEB-10G/57811-1S

[deloptes]

Leslie Rhorer wrote:

> bnx2
https://packages.debian.org/jessie/firmware-bnx2

Re: Error when compiling drivers for Asus PEB-10G/57811-1S

[deloptes]

Leslie Rhorer wrote:

> bnx2

most likely you'll need firmware for it as well

Re: Bug#1 Freeze - Re: Intel i965

[Jimmy Johnson]

On 02/19/2017 07:53 AM, Jimmy Johnson wrote:

On 02/10/2017 06:58 PM, Jimmy Johnson wrote:

On 02/10/2017 07:54 AM, debian-...@lists.debian.org wrote:

"Re: Bug#1 Freeze"
Jimmy Johnson doc

"Mine is an Intel Mobile GM965/GL960 Integrated Graphics and
it's now working swell with the Sid 4.8.0-2 kernel but not
as quick to load as the 4.7.0-1 kernel which works with no
problem. In Stretch the 4.8.0-2 kernel is freezing the system,
4.7.0-1 kernel works swell - Intel Mobile GM965/GL960 Integrated
Graphics. Plasma and SDDM."

Here's an update for the i965, the linux-image-4.7 is no longer in the
reposes, but is still on my laptop. linux-image-4.8 and 4.9 work only if
I keep pressing ctrl+alt+F1, F2, F7, etc., way to much regression.
Sometimes it will do a first boot without assistance from me but on the
reboot will lockup without assistance. I'm being forced to use the
linux-image from Jessie(works swell) in order to get updates.
jessie-backports 4.8 and 4.9 do not work with plasma on the i965.

If you need testing of assistance let me know.


Hello,
Update, linux-image-4.9.0-2-amd64 now in Sid is working with i965.
regards,


So..
I installed linux-image-4.9.0-2-amd64 to Stretch and it did not work, 
never got to sddm, just loads a black screen and then 
freeze/lockup/quits/dies/kaput.


Also I worth mentioning, the regression while booting Sid makes it 
painful to watch it boot, but it will get to the plasma desktop.

4.7.0-1-amd64 is still installed and quick too, works swell.

regards,
--
Jimmy Johnson

Debian St etch - Plasma 5.8.2 - Intel Mobile 965 - EXT4 at sda6
Registered Linux User #380263

unattended-upgrades: What's happening when I put my system into sleep?

[Merlin Büge]

Hallo all,


this is my first post here.
Last week I installed Debian 8 for the first time (on my laptop, a
Thinkpad T500).


I am currently setting up automatic updates on my system. I noticed a
systemd service (which got automatically enabled) called
'unattended-upgrades.service', which seems to take care of an
unattended upgrade process being finished properly in case of a
shutdown/reboot of the system. This is done via the python script
/usr/share/unattended-upgrades/unattendedupgrade-shutdown.

I'm wondering what's happening if I put my system to sleep (via
suspend-to-RAM or via hibernation) during an unattended upgrade. I
found /etc/pm/sleep.d/10_unattended-upgrades-hibernate -- but as far
as I know (and tested), scripts in /etc/pm/sleep.d/ are no longer
executed with systemd. Now the right place would be
/lib/systemd/systemd-sleep/ (correct me if I'm wrong) -- but
that's empty.

Have I missed something? Or is it simply not implemented at the moment?

Maybe this would be worth fixing before unattended-upgrades are
enabled by default, as discussed in this thread:

https://lists.debian.org/debian-devel/2016/11/msg00117.html


Thanks!

Merlin






-- 
Merlin Büge 

Re: Bug#1 Freeze - Re: Intel i965

[Jimmy Johnson]

On 02/10/2017 06:58 PM, Jimmy Johnson wrote:

On 02/10/2017 07:54 AM, debian-...@lists.debian.org wrote:

"Re: Bug#1 Freeze"
Jimmy Johnson doc

"Mine is an Intel Mobile GM965/GL960 Integrated Graphics and
it's now working swell with the Sid 4.8.0-2 kernel but not
as quick to load as the 4.7.0-1 kernel which works with no
problem. In Stretch the 4.8.0-2 kernel is freezing the system,
4.7.0-1 kernel works swell - Intel Mobile GM965/GL960 Integrated
Graphics. Plasma and SDDM."

Here's an update for the i965, the linux-image-4.7 is no longer in the
reposes, but is still on my laptop. linux-image-4.8 and 4.9 work only if
I keep pressing ctrl+alt+F1, F2, F7, etc., way to much regression.
Sometimes it will do a first boot without assistance from me but on the
reboot will lockup without assistance. I'm being forced to use the
linux-image from Jessie(works swell) in order to get updates.
jessie-backports 4.8 and 4.9 do not work with plasma on the i965.

If you need testing of assistance let me know.


Hello,
Update, linux-image-4.9.0-2-amd64 now in Sid is working with i965.
regards,
--
Jimmy Johnson

Debian Sid/Testing - Plasma 5.8.4 - AMD64 - EXT4 at sda9
Registered Linux User #380263

Re: Fstab Problem

[Stephen P. Molnar]

On 02/19/2017 07:43 AM, Andy Smith wrote:

Hi Stephen,

On Sun, Feb 19, 2017 at 07:37:50AM -0500, Stephen P. Molnar wrote:

#


[…]


#UUID=d65867da-c658-4e35-928c-9dd2d6dd5742  /dev/sdb1 ext4
errors=remount-ro  0  1
#UUID=007c1f16-34a4-438c-9d15-e3df601649ba  /dev/sdb2 ext4
errors=remount-ro  0  1


You've put the device path (e.g. /dev/sdb2) in the second column
instead of the mount point. Since you've specified UUID you don't
need to specify device path.

Cheers,
Andy


That solved the problem.

Many thanks.

--
Stephen P. Molnar, Ph.D.Life is a fuzzy set
www.molecular-modeling.net  Stochastic and multivariate
(614)312-7528 (c)
Skype: smolnar1

Re: Error when compiling drivers for Asus PEB-10G/57811-1S

[Sven Hartge]

Leslie Rhorer  wrote:

> I purchased a couple of Asus PEB-10G/57811-1S 10G LAN adapters.  I am
> not finding any pre-built binaries nor a .deb reporitory for these
> cards, so I am attempting t o compile from scratch,

Why? The bnx2 module is available in the default kernel and should
support those NIC out of the box.

Grüße,
Sven.

-- 
Sigmentation fault. Core dumped.

stretch, startx impossible

[jérémy prego]

bonjour à tous,

après avoir installé Stretch sur une machine avec le bureau mate, il 
m'est impossible de lancer startx. Google me donne plein de résultat 
mais c'est trop vieux et les commande ne fonctionnent plus sur ma 
stretch. L'erreur que j'ai est la suivante:
[82.260] xf86EnableIOPorts: failed to set IOPL for I/O (Operation 
not permitted)


avec lightdm, ça fonctionne très bien par contre, mais je préférerai 
utiliser startx.


je précise que le système vient d'être installé et que rien n'a été touché.

je vous remercie pour votre réponse

jerem

Re: Desligamento Abrupto

[Gabriel Ricardo]

Dependendo da configuração do seu equipamento o sistema pode estar
finalizando bem rápido corretamente e você nem estar percebendo.

Mas pode ocorrer também do seu shutdown não estar utilizando o systemd para
o desligamento.

Esses Debian 8 é atualizado ou instalado diretamente do zero?

Verifica se com o comando "systemctl poweroff" mostra os serviços sendo
finalizados.

Verifica também se o shutdown está apontando para o systemctl:

root@debian:~# ls -l $(which shutdown)
lrwxrwxrwx 1 root root 14 Jan  4 21:42 /sbin/shutdown -> /bin/systemctl

Abraços,


Atenciosamente,
*Gabriel Ricardo*
Fone: +55 41 88817828
Skype: gabriel.nerdworkti


Em 18 de fevereiro de 2017 17:40, Jackson  escreveu:

>
> Hoje o padrão, e não apenas no Debian, é tanto ligar quanto desligar em
>> paralelo, não serialmente, mas levando em conta as dependências. Obviamente
>> as dependências são muito mais importantes ao ligar que ao desligar, além
>> de ser muito mais rápido baixar um processo que levantá-lo.  Creio que é
>> isso que te está incomodando:
>>
> Realmente é um incomodo, de repente por não estar habituado com a
> situação, mais se todos os *serviços* realmente estão sendo finalizados de
> forma correta, fico tranquilo.
>
> (1) qual o comando que o botão de desligar aciona — no Gnome tem uma opção
>> para isso no painel de controle, mas num servidor não sei dizer de cabeça
>> como verificar; e
>>
> ele tem a mesma ação que acontece com 7.x, só que ele ignora as funções,
> passa direto e desliga.
>
> (2) como tuas instalações se comportam se, em vez de apertar o botão, você
>> der o comando normalmente, numa linha de comando.
>>
>> o comando *shutdown* em linha de comando é o mesmo comportamento de
> apertar o botão.
>
>
> Fico no aguardo para mais esclarecimentos.
>
> isso se houver :)
>
>
> --
> ==
>  []___
>  //\Jackson Douglas C. Brito
> /_/\_///\   Engenheiro de Soluções
> | || |||  |||   OnTop Sistemas / Wild Sistemas
> | || |||__|||   Boa Vista - RR (95)-98112-8570
> ==
>
>

Re: Fstab Problem

[Frank]

Op 19-02-17 om 13:37 schreef Stephen P. Molnar:

#UUID=d65867da-c658-4e35-928c-9dd2d6dd5742  /dev/sdb1 ext4
errors=remount-ro  0  1
#UUID=007c1f16-34a4-438c-9d15-e3df601649ba  /dev/sdb2 ext4
errors=remount-ro  0  1

The problem is, that when I reboot the system it doesn't like the new
fstab entries and halts.  It's easy to fix in recovery mode by
commenting out the new lines, but that doesn't solve the problem.


Somehow I don't think you can use the device name as mountpoiint (i.e. 
you're mounting /dev/sdb1 on /dev/sdb1...).


Also, the sixth field of fstab lines is only supposed to be 1 for the 
root filesystem. Others should have 2 (or 0 if you don't want the check 
to run at all).


Regards,
Frank

Re: Fstab Problem

[Hans]

Am Sonntag, 19. Februar 2017, 07:37:50 CET schrieb Stephen P. Molnar:
Hi Stepehen,
did you try, to enter just the devices (like /dev/sda1, dev/sdb1 etc.) instead 
of using UUID?

If that is working, try to add the UUID later.
Asd far as I know, there is also a kernel parameter, which inhibits to check 
for UUIDs. I blieve, it is nouuid, but I am not sure.

I would think in that direction, maybe the UUIDs are wrong.

Good luck!

Hans

> This will probably turn out to be a forehead slapping red faced problem,
> but this used to work.
> 
> I Had a Debian v-8.x catastrophe and had to reinstall.  I have several
> hard drives on the computer and, of course the installer only found
> /dev/sda.
> 
> Here are the results of blkid:
> 
> comp@AbNormal:~$ sudo blkid
> [sudo] password for comp:
> /dev/sdb1: UUID="d65867da-c658-4e35-928c-9dd2d6dd5742" TYPE="ext4"
> PARTUUID="0003d403-01"
> /dev/sdb2: UUID="007c1f16-34a4-438c-9d15-e3df601649ba" TYPE="ext4"
> PARTUUID="0003d403-02"
> /dev/sda1: UUID="3a2e7e1d-3365-447b-85c5-f454a2f0b446" TYPE="ext4"
> PARTUUID="cdf775c6-01"
> /dev/sda5: UUID="92727ce9-2cff-40f5-b6d0-e9580afdeef3" TYPE="swap"
> PARTUUID="cdf775c6-05"
> 
> I edited fstab:
> 
> # /etc/fstab: static file system information.
> #
> # Use 'blkid' to print the universally unique identifier for a
> # device; this may be used with UUID= as a more robust way to name devices
> # that works even if disks are added and removed. See fstab(5).
> #
> #
> # / was on /dev/sda1 during installation
> UUID=3a2e7e1d-3365-447b-85c5-f454a2f0b446 /   ext4
> errors=remount-ro 0   1
> # swap was on /dev/sda5 during installation
> UUID=92727ce9-2cff-40f5-b6d0-e9580afdeef3 noneswapsw
>0   0
> /dev/sr0/media/cdrom0   udf,iso9660 user,noauto 0   0
> 
> #UUID=d65867da-c658-4e35-928c-9dd2d6dd5742  /dev/sdb1 ext4
> errors=remount-ro  0  1
> #UUID=007c1f16-34a4-438c-9d15-e3df601649ba  /dev/sdb2 ext4
> errors=remount-ro  0  1
> 
> The problem is, that when I reboot the system it doesn't like the new
> fstab entries and halts.  It's easy to fix in recovery mode by
> commenting out the new lines, but that doesn't solve the problem.
> 
> My computer log doesn't record what actions I might had to take to get
> this to work the last time it. happened.
> 
> What have I missed?
> 
> Thanks in advance.

Re: Fstab Problem

[Andy Smith]

Hi Stephen,

On Sun, Feb 19, 2017 at 07:37:50AM -0500, Stephen P. Molnar wrote:
> #

[…]

> #UUID=d65867da-c658-4e35-928c-9dd2d6dd5742  /dev/sdb1 ext4
> errors=remount-ro  0  1
> #UUID=007c1f16-34a4-438c-9d15-e3df601649ba  /dev/sdb2 ext4
> errors=remount-ro  0  1

You've put the device path (e.g. /dev/sdb2) in the second column
instead of the mount point. Since you've specified UUID you don't
need to specify device path.

Cheers,
Andy

-- 
https://bitfolk.com/ -- No-nonsense VPS hosting

Fstab Problem

[Stephen P. Molnar]

This will probably turn out to be a forehead slapping red faced problem, 
but this used to work.


I Had a Debian v-8.x catastrophe and had to reinstall.  I have several 
hard drives on the computer and, of course the installer only found 
/dev/sda.


Here are the results of blkid:

comp@AbNormal:~$ sudo blkid
[sudo] password for comp:
/dev/sdb1: UUID="d65867da-c658-4e35-928c-9dd2d6dd5742" TYPE="ext4" 
PARTUUID="0003d403-01"
/dev/sdb2: UUID="007c1f16-34a4-438c-9d15-e3df601649ba" TYPE="ext4" 
PARTUUID="0003d403-02"
/dev/sda1: UUID="3a2e7e1d-3365-447b-85c5-f454a2f0b446" TYPE="ext4" 
PARTUUID="cdf775c6-01"
/dev/sda5: UUID="92727ce9-2cff-40f5-b6d0-e9580afdeef3" TYPE="swap" 
PARTUUID="cdf775c6-05"


I edited fstab:

# /etc/fstab: static file system information.
#
# Use 'blkid' to print the universally unique identifier for a
# device; this may be used with UUID= as a more robust way to name devices
# that works even if disks are added and removed. See fstab(5).
#
#
# / was on /dev/sda1 during installation
UUID=3a2e7e1d-3365-447b-85c5-f454a2f0b446 /   ext4 
errors=remount-ro 0   1

# swap was on /dev/sda5 during installation
UUID=92727ce9-2cff-40f5-b6d0-e9580afdeef3 noneswapsw 
  0   0

/dev/sr0/media/cdrom0   udf,iso9660 user,noauto 0   0

#UUID=d65867da-c658-4e35-928c-9dd2d6dd5742  /dev/sdb1 ext4 
errors=remount-ro  0  1
#UUID=007c1f16-34a4-438c-9d15-e3df601649ba  /dev/sdb2 ext4 
errors=remount-ro  0  1


The problem is, that when I reboot the system it doesn't like the new 
fstab entries and halts.  It's easy to fix in recovery mode by 
commenting out the new lines, but that doesn't solve the problem.


My computer log doesn't record what actions I might had to take to get 
this to work the last time it. happened.


What have I missed?

Thanks in advance.
--
Stephen P. Molnar, Ph.D.Life is a fuzzy set
www.molecular-modeling.net  Stochastic and multivariate
(614)312-7528 (c)
Skype: smolnar1

Error when compiling drivers for Asus PEB-10G/57811-1S

[Leslie Rhorer]

I purchased a couple of Asus PEB-10G/57811-1S 10G LAN adapters.  I am not 
finding any pre-built binaries nor a .deb reporitory for these cards, so I am 
attempting t o compile from scratch, but I get the following error during the 
make operation:

Backup/Server-Main/Temp/netxtreme2-7.10.42/bnx2-2.710.30/src/bnx2.c: In 
function ‘bnx2_rx_int’:
/Backup/Server-Main/Temp/netxtreme2-7.10.42/bnx2-2.710.30/src/bnx2.c:3753:7: 
error: ‘struct sk_buff’ has no member named ‘rxhash’
skb->rxhash = rx_hdr->l2_fhdr_hash;
   ^
/usr/src/linux-headers-3.16.0-4-common/scripts/Makefile.build:268: recipe for 
target '/Backup/Server-Main/Temp/netxtreme2-7.10.42/bnx2-2.710.30/src/bnx2.o' 
failed

Does anyone have an ideas?  Are there any pre-built drivers for these cards for 
Debian Jessie?

Re: Matrox Meteor frame grabber.

[Dan Ritter]

On Sat, Feb 18, 2017 at 09:23:11PM -0800, pe...@easthope.ca wrote:
> There is an old Matrox Meteor PCI card here.
> http://easthope.ca/MatroxMeteor.jpg 
> As I understand, a frame grabber or video tuner.  
> 
> The connector on the lower left in the photo accepts an RCA plug.  The 
> connector immediately above that is S video.  The next above is a 3.5 
> mm TRS socket.  Audio? The connector on the shielding box is similar 
> to RCA but smaller.  Any ideas about that?  
> Which of these is input and which is output?

All of them are input.

> Can Debian display composite video using this card?  Which packages are 
> needed?

This is an input-only card, and while it was very good when it
was introduced, it is absolutely lousy by today's standards. No 
driver for it has been seen since 2005.

Hardware has become much cheaper and more powerful since then.
You can buy a used device that can handle NTSC and ATSC (HD) 
video for $30 or so -- and will have support.

To see the kernel docs on supported devices, look at
https://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git/tree/Documentation/media/v4l-drivers?id=refs/tags/v4.10-rc8

-dsr-

Re: Regarding: Installatie Debian voor PPC op ibook G4

[Mark Eijkman]

Beste allen,

Het is opgelost. Was inderdaad de grafische driver, heb de oplossing 
gebruikt die ik eerder vond voor Lubuntu:


radeon.modeset=1 video=radeonfb:off video=offb:off 
video=1024x768-32[enter your screen resolution] radeon.agpmode=-1


Om de een of andere reden kon ik /etc/yaboot.conf niet bewerken, maar 
gek genoeg start hij nu ook zonder het vast te leggen prima op.


Draait als een speer, voor zover dat gaat met 733 Mhz processor :)

Hartelijk bedankt voor het meedenken!

Ik ga Debian ontdekken.

Mark

Op 10-02-17 om 17:56 schreef Geert Stappers:

On Fri, Feb 10, 2017 at 02:33:33PM +0100, Mark Eijkman wrote:

Op 08-02-17 om 22:34 schreef Geert Stappers:

On Sun, Feb 05, 2017 at 06:54:05PM +0100, Mark Eijkman wrote:

Hallo,

lk heb geprobeerd Debian Jessie voor PowerPC op een iBook G4 te
installeren. Het installatieproces verliep probleemloos. Bij het
booten krijg ik twee keer een foutmelding, en aan het eind een zwart
scherm, dan even een cursor, en dan de melding (een OpenFirmware
scherm?) dat er iets is misgegaan en ik moet uitloggen en opnieuw
opstarten.

Iemand een idee? Ik ben een absolute beginner in Debian, wel wat
*buntu-ervaring, Xubuntu is mijn dagelijkse systeem.

Bij voorbaat dank!

Mark

Bericht nu pas gezien.
Maar ik begrijp het niet.
Mijn inschatting is dat er gemeldt wordt "Werkt, nog het laatste loodje".

Deze e-mail is om te vragen: "Heb je inderdaad een werkend system?"
Of is 'Failed to start Load Kernel Modules' toch "fataal"?

Dat om in te schatten welke prioriteit de vraag met krijgen.


Beste Geert,

Bedankt voor je antwoord. Sorry dat ik niet duidelijk was blijkbaar.
Het is een fatale fout; systeem start niet op. Als het alleen maar
een melding was en het werkt verder gewoon zou ik jullie niet lastig
vallen :)

De opstart lijkt volledig te worden doorlopen, en volkomen normaal,
(duurt ca. 55 seconden, lijkt me prima) behalve die twee rode
FAILED-meldingen dan, maar net als je denkt, daar komt de grafische
omgeving, want de laatste melding is:

Debian GNU/Linux 8 debian tty1
debian login:

dan krijg ik dus als volgende dit:


Oh no! Something has gone wrong

"Oh no! Something has gone wrong. A problem has occurred and the
system can't recover. Please log out and try again."

(soms eerst nog even een zwart scherm met cursor, maar ik kan niets doen)

En dan kan ik alleen nog maar op de Log Out-knop klikken. Of
bijvoorbeeld de spatiebalk indrukken. Het resultaat is hoe dan ook
een zwart scherm met wat backlight (die iBook schakelt niet helemaal
uit als je de aan/uit knop niet indrukt).

Is er een toets(encombinatie) die het opstartproces kan onderbreken
/ het scherm stil kan zetten zodat ik kan lezen wat de meldingen
precies zijn? Nu heb ik 20 keer opnieuw opgestart om elke keer een
deel van de tekst te kunnen lezen :)

Ik zou haast denken dat het iets grafisch is, dat is mijn ervaring
met andere Linuxen. Maar ik heb al geprobeerd met  parameters op te
starten, dat maakt geen verschil.

Dus zo. Ik begrijp dat het moeilijk is om van een afstand te
beoordelen wat er aan de hand is, ook al omdat ik natuurlijk een
exotische en oeroude configuratie heb. Maar het zou leuk zijn als ik
zo'n oud laptopje nog aan de praat kreeg, en Debian Jessie lijkt me
er het geschiktst voor van de mogelijke andere opties (Lubuntu,
Mint, Ubuntu PPC zijn dat geloof ik). Lubuntu werkt op dit apparaat,
maar heel traag.

Bedankt voor het meedenken!

Mark Eijkman


Twee dingen:

  * mail naar de ML
  * laat mensen in de discussie volgorde lezen ( antwoord _onder_ de tekst )


Groeten
Geert Stappers

Re: Re: Whats the alternative to .xinitrc

[tomas]

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

On Sun, Feb 19, 2017 at 09:53:41AM +, Rob Brewer wrote:

[...]

> Thank you for your help, I was wrong footed by the man page which suggested 
> using .xsession not .xsessionrc so I guess the man page needs an update. 
> Looks 
> like it is now OK after changing to .xsessionrc.

Glad it helped :)

> Also sorry for the double posting, I has DNS problems which caused me to be 
> unsubscribed and I didn't see the replies.

No worries.

Cheers
- -- t
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.12 (GNU/Linux)

iEYEARECAAYFAliph54ACgkQBcgs9XrR2kZw3QCcDFhumhUkrr1sPQ+jyibbbFSO
cPIAn2jXf7YyrPpw+K2FMYbapsHrcPaC
=GeJk
-END PGP SIGNATURE-

Re: Uefi

[miguel angel gonzalez]

Buenas,
Gracias por contestar a los dos. La partición está en Gpt, a que te
refieres con  hacerla visible en Linux?

Por más que miro en la Bios no encuentro la opción de legacy Mode, miraré
en el manual de la placa.


El 19 feb. 2017 9:52 a. m., "Ernesto Escobedo" 
escribió:

Muy buenas noches

define la particion gpt y hazla visible para el linux

ese es el truco

El 19 de febrero de 2017, 1:12, miguel angel gonzalez <
mangelgonza...@gmail.com> escribió:

>
> Buenas tardes,
> Tengo en un ordenador de nueva generación con la placa Gigabyte H170-H=
> D3 Socket 1151, una instalación  de Windows 10 y quiero instalar Debian
> , necesito Windows también por trabajo. Sabéis como puedo instalar los
> dos? Me trae de cabeza el tema de uefi, hago la instalación  con
> grub en el mismo disco y no me hace ni caso, ni aparece el arranque.
> Muchas gracias.
> Saludos.
>

Re: Whats the alternative to .xinitrc

[Vincent Lefevre]

On 2017-02-18 20:59:44 +, Brian wrote:
> The advice in startx(1) is sound but nothing stops you using a ,xinitrc.
> The command doesn't work in a ,xinitrc? Perhaps it is incorrect or the
> DM ignores it.

AFAIK, .xinitrc is not used by DM's, in particular because X has
already been started.

-- 
Vincent Lefèvre  - Web: 
100% accessible validated (X)HTML - Blog: 
Work: CR INRIA - computer arithmetic / AriC project (LIP, ENS-Lyon)

Re: Re: Whats the alternative to .xinitrc

[Rob Brewer]

>> I am running up to date KDE Sid with SDDM but I need to start the gnome 
>> keyring at x startup to satisfy Midori dependencies.
>> 
>> The Midori FAQ suggests adding  “export `gnome-keyring-daemon –start`” to 
>> the historical .xinitrc but this seems to be ignored as does .xsession as 
>> suggested by the startx man page.
>> 
>> As .xinitrc has worked OK in the past, how do I now set the user 
>environment 
>> when X starts?
>
>My .xsessionrc is functional. The magic happens in
>   /etc/X11/Xsession.d/40x11-common_xsessionrc
>
> +---
> | # This file is sourced by Xsession(5), not executed.
> | 
> | #Source user defined xsessionrc (locales and other environment variables)
> | if [ -r "$USERXSESSIONRC" ]; then
> |   . "$USERXSESSIONRC"
> | fi
> +---
>
>Attention: I'm running SysV init -- perhaps things are different in other
>settings.

Thank you for your help, I was wrong footed by the man page which suggested 
using .xsession not .xsessionrc so I guess the man page needs an update. Looks 
like it is now OK after changing to .xsessionrc.

Also sorry for the double posting, I has DNS problems which caused me to be 
unsubscribed and I didn't see the replies.

Rob

Re: Uefi

[Ernesto Escobedo]

Muy buenas noches

define la particion gpt y hazla visible para el linux

ese es el truco

El 19 de febrero de 2017, 1:12, miguel angel gonzalez <
mangelgonza...@gmail.com> escribió:

>
> Buenas tardes,
> Tengo en un ordenador de nueva generación con la placa Gigabyte H170-H=
> D3 Socket 1151, una instalación  de Windows 10 y quiero instalar Debian
> , necesito Windows también por trabajo. Sabéis como puedo instalar los
> dos? Me trae de cabeza el tema de uefi, hago la instalación  con
> grub en el mismo disco y no me hace ni caso, ni aparece el arranque.
> Muchas gracias.
> Saludos.
>