Menu
▾
▴
devil-linux-discuss — General Mailing List for all discussions
You can subscribe to this list here.
| 2001 |
Jan
|
Feb
|
Mar
|
Apr
|
May
|
Jun
|
Jul
|
Aug
(59) |
Sep
(57) |
Oct
(5) |
Nov
(45) |
Dec
(21) |
|---|---|---|---|---|---|---|---|---|---|---|---|---|
| 2002 |
Jan
(13) |
Feb
(22) |
Mar
(14) |
Apr
(7) |
May
(33) |
Jun
(57) |
Jul
(25) |
Aug
(40) |
Sep
(53) |
Oct
(58) |
Nov
(75) |
Dec
(22) |
| 2003 |
Jan
(101) |
Feb
(101) |
Mar
(103) |
Apr
(125) |
May
(85) |
Jun
(57) |
Jul
(62) |
Aug
(42) |
Sep
(76) |
Oct
(214) |
Nov
(290) |
Dec
(274) |
| 2004 |
Jan
(187) |
Feb
(172) |
Mar
(313) |
Apr
(209) |
May
(169) |
Jun
(147) |
Jul
(118) |
Aug
(193) |
Sep
(227) |
Oct
(125) |
Nov
(246) |
Dec
(191) |
| 2005 |
Jan
(244) |
Feb
(175) |
Mar
(165) |
Apr
(130) |
May
(217) |
Jun
(122) |
Jul
(188) |
Aug
(235) |
Sep
(165) |
Oct
(133) |
Nov
(209) |
Dec
(88) |
| 2006 |
Jan
(66) |
Feb
(89) |
Mar
(108) |
Apr
(91) |
May
(29) |
Jun
(45) |
Jul
(64) |
Aug
(42) |
Sep
(44) |
Oct
(81) |
Nov
(64) |
Dec
(9) |
| 2007 |
Jan
(24) |
Feb
(122) |
Mar
(55) |
Apr
(50) |
May
(84) |
Jun
(13) |
Jul
(80) |
Aug
(70) |
Sep
(78) |
Oct
(45) |
Nov
(56) |
Dec
(42) |
| 2008 |
Jan
(65) |
Feb
(3) |
Mar
(51) |
Apr
(151) |
May
(54) |
Jun
(72) |
Jul
(73) |
Aug
(47) |
Sep
(55) |
Oct
(123) |
Nov
(16) |
Dec
(4) |
| 2009 |
Jan
(23) |
Feb
(39) |
Mar
(27) |
Apr
(36) |
May
(35) |
Jun
(51) |
Jul
(11) |
Aug
(14) |
Sep
(40) |
Oct
(67) |
Nov
(38) |
Dec
(13) |
| 2010 |
Jan
(15) |
Feb
(35) |
Mar
(40) |
Apr
(11) |
May
(26) |
Jun
(10) |
Jul
(5) |
Aug
(50) |
Sep
(86) |
Oct
(67) |
Nov
(36) |
Dec
(11) |
| 2011 |
Jan
(50) |
Feb
(6) |
Mar
(13) |
Apr
(13) |
May
(29) |
Jun
(27) |
Jul
(26) |
Aug
(27) |
Sep
(21) |
Oct
(7) |
Nov
(27) |
Dec
(4) |
| 2012 |
Jan
(11) |
Feb
(20) |
Mar
(48) |
Apr
(18) |
May
(8) |
Jun
(19) |
Jul
|
Aug
(15) |
Sep
(3) |
Oct
(4) |
Nov
(5) |
Dec
(1) |
| 2013 |
Jan
(13) |
Feb
(7) |
Mar
(4) |
Apr
(25) |
May
(2) |
Jun
(8) |
Jul
(4) |
Aug
(8) |
Sep
(7) |
Oct
|
Nov
(5) |
Dec
(10) |
| 2014 |
Jan
|
Feb
|
Mar
(6) |
Apr
(20) |
May
(5) |
Jun
|
Jul
(2) |
Aug
|
Sep
(8) |
Oct
(21) |
Nov
(4) |
Dec
(7) |
| 2015 |
Jan
(10) |
Feb
(9) |
Mar
(4) |
Apr
|
May
|
Jun
|
Jul
|
Aug
(5) |
Sep
(11) |
Oct
|
Nov
(17) |
Dec
(32) |
| 2016 |
Jan
(10) |
Feb
(15) |
Mar
(4) |
Apr
(7) |
May
(10) |
Jun
(11) |
Jul
(15) |
Aug
(26) |
Sep
(13) |
Oct
(10) |
Nov
(16) |
Dec
(6) |
| 2017 |
Jan
(9) |
Feb
(3) |
Mar
|
Apr
(2) |
May
(2) |
Jun
|
Jul
|
Aug
(3) |
Sep
(3) |
Oct
(6) |
Nov
(8) |
Dec
|
| 2018 |
Jan
(12) |
Feb
|
Mar
|
Apr
|
May
|
Jun
|
Jul
|
Aug
(4) |
Sep
|
Oct
|
Nov
|
Dec
|
|
From: Heiko Z. <he...@zu...> - 2008-08-29 13:24:01
|
Did you add the extensions to the file build/scripts/config/perl-ext (wrote it our of memory, but should be close)? Heiko > -----Original Message----- > From: dev...@li... [mailto:devil- > lin...@li...] On Behalf Of Riccardo > Marcon > Sent: Friday, August 29, 2008 2:14 AM > To: dev...@li... > Subject: [Devil-Linux-discuss] building 1.2.15 with perl extensions > > hello, > > i got some trouble in building DL 1.2.15 with > Mail-POP3Client and WWW-Curl perl extensions. > > build process skips the install step (make install results in 'nothing > to do') for the above extensions, while build step is ok. > > any hint to handle extensions embedding ? ... > > thanks > > riccardo > > -- > ---------------------------- > riccardo marcon > dipartimento di scienze economiche > universita' di padova > via del santo 33 - 35123 padova > tel +39 049 827 4272 (4212) > fax +39 049 827 4211 > e-mail: ric...@un... > > > ----------------------------------------------------------------------- > -- > This SF.Net email is sponsored by the Moblin Your Move Developer's > challenge > Build the coolest Linux based applications with Moblin SDK & win great > prizes > Grand prize is a trip for two to an Open Source event anywhere in the > world > http://moblin-contest.org/redirect.php?banner_id=100&url=/ > _______________________________________________ > Devil-linux-discuss mailing list > Dev...@li... > https://lists.sourceforge.net/lists/listinfo/devil-linux-discuss |
|
From: Dom <dl...@ed...> - 2008-08-29 10:17:02
|
<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
<html>
<head>
<meta content="text/html;charset=ISO-8859-1" http-equiv="Content-Type">
</head>
<body bgcolor="#ffffff" text="#000000">
Bruce Smith wrote:
<blockquote
cite="mid:5f9...@ma..."
type="cite">
<blockquote type="cite">
<pre wrap="">I am delighted to say that having previously been unable to boot our DL
machine with a DL 1.3 testing release I now succeeded with
devil-linux-1.3.6-2008-08-28-i686-bs - thanks!
</pre>
</blockquote>
<pre wrap=""><!---->
Great!
</pre>
<blockquote type="cite">
<pre wrap="">But when I save the configuration back onto the USB stick I see:
root@Samba:~ # save-config -q
using device /dev/sda1
Updating file on device...
Saving current configuration
tar: etc-mods/samba/lock/winbindd_privileged/pipe: socket ignored
chmod: changing permissions of `/var/adm/mount/etc-mods.tar.bz2':
Operation not permitted
Configuration saved
So there seems to be a tar error and then a chmod error. I haven't yet
rebooted the DL machine after the initial reconfiguration, because
although it says the configuration is saved I am unsure if it has worked
or if I will have problems upon reboot. Can I just ignore these
messages? Grateful for any advice.
</pre>
</blockquote>
<pre wrap=""><!---->
Yes, those warning messages can be ignored.
The 'socket ignored' message is common with tar, since sockets are not
"real files" and hence cannot be backed up. They don't contain any
real data (no need to back them up) and are dynamically created by the
applications when needed.
The 'chmod' message is because the Dos/Windows filesystem (vfat)
doesn't support Linux/Unix file permissions, and it's just a warning
telling you that. If you were to reformat your config media with a
Linux filesystem, the message would go away (but you would no longer
be able to read the media in a Windows machine). So just ignore it.
I might take a look at the save-config script sometime, and skip the
chmod command if it's vfat.
- BS
</pre>
</blockquote>
Thanks Bruce, that's great, I can relax now! I feel more comfortable
being able to read the stick from a Windows machine (if ever required,
for instance as an emergency way to recover the configuration), so I'll
stick with vfat and ignore the messages.<br>
<br>
While I'm enjoying success, I might try running the install-on-usb
script to migrate the installation from CD to the (vfat) usb stick.
Does this make it more complicated later on to upgrade DL?<br>
<br>
Regards<br>
<br>
Dom<br>
<br>
</body>
</html>
|
|
From: Bruce S. <bw...@re...> - 2008-08-29 09:50:43
|
> I am delighted to say that having previously been unable to boot our DL > machine with a DL 1.3 testing release I now succeeded with > devil-linux-1.3.6-2008-08-28-i686-bs - thanks! Great! > But when I save the configuration back onto the USB stick I see: > > root@Samba:~ # save-config -q > using device /dev/sda1 > Updating file on device... > Saving current configuration > tar: etc-mods/samba/lock/winbindd_privileged/pipe: socket ignored > chmod: changing permissions of `/var/adm/mount/etc-mods.tar.bz2': > Operation not permitted > Configuration saved > > So there seems to be a tar error and then a chmod error. I haven't yet > rebooted the DL machine after the initial reconfiguration, because > although it says the configuration is saved I am unsure if it has worked > or if I will have problems upon reboot. Can I just ignore these > messages? Grateful for any advice. Yes, those warning messages can be ignored. The 'socket ignored' message is common with tar, since sockets are not "real files" and hence cannot be backed up. They don't contain any real data (no need to back them up) and are dynamically created by the applications when needed. The 'chmod' message is because the Dos/Windows filesystem (vfat) doesn't support Linux/Unix file permissions, and it's just a warning telling you that. If you were to reformat your config media with a Linux filesystem, the message would go away (but you would no longer be able to read the media in a Windows machine). So just ignore it. I might take a look at the save-config script sometime, and skip the chmod command if it's vfat. - BS |
|
From: Dom <dl...@ed...> - 2008-08-29 09:04:11
|
I am delighted to say that having previously been unable to boot our DL
machine with a DL 1.3 testing release I now succeeded with
devil-linux-1.3.6-2008-08-28-i686-bs - thanks!
But when I save the configuration back onto the USB stick I see:
root@Samba:~ # save-config -q
using device /dev/sda1
Updating file on device...
Saving current configuration
tar: etc-mods/samba/lock/winbindd_privileged/pipe: socket ignored
chmod: changing permissions of `/var/adm/mount/etc-mods.tar.bz2':
Operation not permitted
Configuration saved
So there seems to be a tar error and then a chmod error. I haven't yet
rebooted the DL machine after the initial reconfiguration, because
although it says the configuration is saved I am unsure if it has worked
or if I will have problems upon reboot. Can I just ignore these
messages? Grateful for any advice.
Thanks
Dom
http://www.edendevelopments.co.uk/dlsetup
|
|
From: Riccardo M. <ric...@un...> - 2008-08-29 07:41:20
|
hello, i got some trouble in building DL 1.2.15 with Mail-POP3Client and WWW-Curl perl extensions. build process skips the install step (make install results in 'nothing to do') for the above extensions, while build step is ok. any hint to handle extensions embedding ? ... thanks riccardo -- ---------------------------- riccardo marcon dipartimento di scienze economiche universita' di padova via del santo 33 - 35123 padova tel +39 049 827 4272 (4212) fax +39 049 827 4211 e-mail: ric...@un... |
|
From: Serge L. <fi...@in...> - 2008-08-28 21:49:06
|
Hello, John Bridleman wrote: .. > > Next I went into the raid utility and setup the drives for mirroring, > rebooted and got the same error. Try to say "Y" for the question "Would you like to probe for SCSI controllers now?". It will load SCSI/SATA modules which is necessary for correct mounting your CDROM drives. You should do it only once, till there is no config files with the module name (/etc/sysconfig/config: INITRD_MODULES="xxxxx") which is required for preboot stage. Sometimes the loading of tons modules may cause kernel panic or oops, though... -- Serge |
|
From: John B. <jbr...@gm...> - 2008-08-28 21:00:18
|
The BIOS has two settings for SATA. IDE and RAID. It was set to IDE. I changed it to RAID which offered me the chance to setup raid when booting. I left it alone for now. Setting it to RAID did get rid of the double y thing but it still gives the "wrong media" error when I tell it I want the default configuration to be copied to /dev/sda1. Next I went into the raid utility and setup the drives for mirroring, rebooted and got the same error. On Thu, Aug 28, 2008 at 4:35 PM, Martin Hotze <ma...@ho...> wrote: > Hi, > > try to change the SATA settings in the BIOS to something like > "compatible mode" > > hth, #m > > ________________________________ > > Von: dev...@li... im Auftrag von > John Bridleman > Gesendet: Do 28.08.2008 21:44 > An: dev...@li... > Betreff: [Devil-Linux-discuss] SATA CDROM boot problem? > > > DL 1.3.6-2008-08-28-i686-bs > Dell Vostro 200. Dual SATA hard drives and SATA CD-ROM drive. > I have a usb thumb drive for the configuration. > > So DL boots and gets to the found empty ... media - /dev/sda1 > Shall I copy .... to it? (y/n) > I hit y and it gives me yy. > > Weird. So I let it say yy,(because hitting backspace makes them both > go away) hit enter,it beeps 3 times and I get: > "Would you really like to load DL without Configuration Media?" (y/n) > then it drops down a line and says > Please insert configuration media and press 'Enter' > I can't get any farther. > > > So, I put an older config file on the usb to see what I get and it > says: > > > checking /dev/sda1.... wrong media > then it says > !!! Devil-Linux CD-ROM not found !!! > Please check your hardware! > Booting will not continue, you have to reset and try again. > > A friend mentioned it might be a "DL doesn't like to be booted from a > sata cdrom drive problem". > > Is that what I'm looking at or something else? > -- > > > > ------------------------------------------------------------------------- > This SF.Net email is sponsored by the Moblin Your Move Developer's > challenge > Build the coolest Linux based applications with Moblin SDK & win great > prizes > Grand prize is a trip for two to an Open Source event anywhere in the world > http://moblin-contest.org/redirect.php?banner_id=100&url=/ > _______________________________________________ > Devil-linux-discuss mailing list > Dev...@li... > https://lists.sourceforge.net/lists/listinfo/devil-linux-discuss > > -- John Bridleman |
|
From: Martin H. <ma...@ho...> - 2008-08-28 20:38:13
|
Hi, try to change the SATA settings in the BIOS to something like "compatible mode" hth, #m ________________________________ Von: dev...@li... im Auftrag von John Bridleman Gesendet: Do 28.08.2008 21:44 An: dev...@li... Betreff: [Devil-Linux-discuss] SATA CDROM boot problem? DL 1.3.6-2008-08-28-i686-bs Dell Vostro 200. Dual SATA hard drives and SATA CD-ROM drive. I have a usb thumb drive for the configuration. So DL boots and gets to the found empty ... media - /dev/sda1 Shall I copy .... to it? (y/n) I hit y and it gives me yy. Weird. So I let it say yy,(because hitting backspace makes them both go away) hit enter,it beeps 3 times and I get: "Would you really like to load DL without Configuration Media?" (y/n) then it drops down a line and says Please insert configuration media and press 'Enter' I can't get any farther. So, I put an older config file on the usb to see what I get and it says: checking /dev/sda1.... wrong media then it says !!! Devil-Linux CD-ROM not found !!! Please check your hardware! Booting will not continue, you have to reset and try again. A friend mentioned it might be a "DL doesn't like to be booted from a sata cdrom drive problem". Is that what I'm looking at or something else? -- |
|
From: John B. <jbr...@gm...> - 2008-08-28 19:44:16
|
DL 1.3.6-2008-08-28-i686-bs Dell Vostro 200. Dual SATA hard drives and SATA CD-ROM drive. I have a usb thumb drive for the configuration. So DL boots and gets to the found empty ... media - /dev/sda1 Shall I copy .... to it? (y/n) I hit y and it gives me yy. Weird. So I let it say yy,(because hitting backspace makes them both go away) hit enter,it beeps 3 times and I get: "Would you really like to load DL without Configuration Media?" (y/n) then it drops down a line and says Please insert configuration media and press 'Enter' I can't get any farther. So, I put an older config file on the usb to see what I get and it says: checking /dev/sda1.... wrong media then it says !!! Devil-Linux CD-ROM not found !!! Please check your hardware! Booting will not continue, you have to reset and try again. A friend mentioned it might be a "DL doesn't like to be booted from a sata cdrom drive problem". Is that what I'm looking at or something else? -- |
|
From: Chris G. <dj_...@ti...> - 2008-08-12 17:45:21
|
Hi again. First off, Yes the devices do work on the USB 1.1 ports. Second, I've just spent 2 hours fighting with 1.3 with no luck. Whereas 1.2 sees the device plugged and just complains it can't assign an address, 1.3 just seems to completely ignore it all together. I'm just wondering whether or not there is any way of assigning IRQ's to a device as for some reason it seems to be IRQ sharing and I'm wondering whether that is causing a conflict. Thanks again for any help. From: dev...@li... [mailto:dev...@li...] On Behalf Of Heiko Zuerker Sent: 11 August 2008 16:19 To: dev...@li... Subject: Re: [Devil-Linux-discuss] Devil-Linux with a PCI USB card It may be an incomatability between the USB device and the Linux Kernel. Do the devices work on the USB 1.1 ports? You could also try the 1.3 version of DL (beta, but very stable), which is based on the 2.6 Kernel. Heiko Quoting Chris Grove <dj_...@ti...>: Hi all, I've got devil linux running very nicely on my little MSI machine. The problem is that the onboard ports are only usb 1.1 compliant. So I thought "I know, i'll buy a usb 2.0 PCI card" This all worked out well as i found a nice little one with a VIA chipset on ebay. It arrived, and i installed it. Now here's where the fun starts. Linux sees the device during boot-up. It also sees it if I type in lspci, but I can't see/mount any hdd's or memory sticks that I plug in. Has anybody any ideas please. In case its any help, here's what lspci has to say about it: this is the onboard one: 00:1f.2 USB Controller: Intel Corporation 82801BA/BAM USB Controller #1 (rev 05) 00:1f.4 USB Controller: Intel Corporation 82801BA/BAM USB Controller #1 (rev 05) and this is the PCI one: 01:00.0 USB Controller: VIA Technologies, Inc. VT82xxxxx UHCI USB 1.1 Controller (rev 62) 01:00.1 USB Controller: VIA Technologies, Inc. VT82xxxxx UHCI USB 1.1 Controller (rev 62) 01:00.2 USB Controller: VIA Technologies, Inc. USB 2.0 (rev 65) And dmesg says this: usb.c: registered new driver usbdevfs usb.c: registered new driver hub PCI: Found IRQ 5 for device 01:00.2 ehci_hcd 01:00.2: VIA Technologies, Inc. USB 2.0 ehci_hcd 01:00.2: irq 5, pci mem c881e000 usb.c: new USB bus registered, assigned bus number 1 ehci_hcd 01:00.2: USB 2.0 enabled, EHCI 1.00, driver 2003-Dec-29/2.4 hub.c: USB hub found hub.c: 4 ports detected host/usb-uhci.c: $Revision: 1.275 $ time 19:10:59 Nov 20 2007 host/usb-uhci.c: High bandwidth mode enabled PCI: Found IRQ 12 for device 00:1f.2 PCI: Setting latency timer of device 00:1f.2 to 64 host/usb-uhci.c: USB UHCI at I/O 0xcc00, IRQ 12 host/usb-uhci.c: Detected 2 ports usb.c: new USB bus registered, assigned bus number 2 hub.c: USB hub found hub.c: 2 ports detected PCI: Found IRQ 10 for device 00:1f.4 PCI: Setting latency timer of device 00:1f.4 to 64 host/usb-uhci.c: USB UHCI at I/O 0xd400, IRQ 10 host/usb-uhci.c: Detected 2 ports usb.c: new USB bus registered, assigned bus number 3 hub.c: USB hub found hub.c: 2 ports detected PCI: Found IRQ 11 for device 01:00.1 PCI: Sharing IRQ 11 with 00:1f.3 PCI: Sharing IRQ 11 with 00:1f.5 host/usb-uhci.c: USB UHCI at I/O 0xac00, IRQ 11 host/usb-uhci.c: Detected 2 ports usb.c: new USB bus registered, assigned bus number 4 hub.c: USB hub found hub.c: 2 ports detected PCI: Found IRQ 9 for device 01:00.0 PCI: Sharing IRQ 9 with 00:02.0 host/usb-uhci.c: USB UHCI at I/O 0xa800, IRQ 9 host/usb-uhci.c: Detected 2 ports usb.c: new USB bus registered, assigned bus number 5 hub.c: USB hub found hub.c: 2 ports detected host/usb-uhci.c: v1.275:USB Universal Host Controller Interface driver usb.c: registered new driver hiddev usb.c: registered new driver hid hid-core.c: v1.8.1 Andreas Gal, Vojtech Pavlik <vo...@su...> hid-core.c: USB HID support drivers Initializing USB Mass Storage driver... usb.c: registered new driver usb-storage USB Mass Storage support registered. Initializing Cryptographic API IEEE 802.2 LLC for Linux 2.1 (c) 1996 Tim Alpaerts NET4: Linux TCP/IP 1.0 for NET4.0 IP Protocols: ICMP, UDP, TCP, IGMP IP: routing cache hash table of 512 buckets, 4Kbytes TCP: Hash tables configured (established 8192 bind 8192) Linux IP multicast router 0.06 plus PIM-SM NET4: Unix domain sockets 1.0/SMP for Linux NET4.0. 802.1Q VLAN Support v1.8 Ben Greear <gr...@ca...> All bugs added by David S. Miller <da...@re...> RAMDISK: Compressed image found at block 0 hub.c: new USB device 00:1f.2-1, assigned address 2 Freeing initrd memory: 2522k freed VFS: Mounted root (cramfs filesystem) readonly. Mounted devfs on /dev Freeing unused kernel memory: 156k freed scsi0 : SCSI emulation for USB Mass Storage devices Vendor: Model: Hitachi HDT72503 Rev: V54O Type: Direct-Access ANSI SCSI revision: 02 Attached scsi disk sda at scsi0, channel 0, id 0, lun 0 SCSI device sda: 625142448 512-byte hdwr sectors (320073 MB) /dev/scsi/host0/bus0/target0/lun0: p1 WARNING: USB Mass Storage data integrity not assured USB Mass Storage device found at 2 hub.c: new USB device 00:1f.2-2, assigned address 3 scsi1 : SCSI emulation for USB Mass Storage devices Vendor: Maxtor 2 Model: B010H1 Rev: 0 0 Type: Direct-Access ANSI SCSI revision: 02 Attached scsi disk sdb at scsi1, channel 0, id 0, lun 0 SCSI device sdb: 20012832 512-byte hdwr sectors (10247 MB) /dev/scsi/host1/bus0/target0/lun0: p1 WARNING: USB Mass Storage data integrity not assured USB Mass Storage device found at 3 hub.c: new USB device 01:00.2-4, assigned address 2 usb_control/bulk_msg: timeout usb.c: USB device not accepting new address=2 (error=-110) hub.c: new USB device 01:00.2-4, assigned address 3 usb_control/bulk_msg: timeout usb.c: USB device not accepting new address=3 (error=-110) I've tried turning to onboard one off, and starting again with a blank config, neither of which work. Any help would be greatly appreciated.. Thanks in advance for your help. -- Regards Heiko Zuerker http://www.devil-linux.org <http://www.devil-linux.org/> ---------------------------------------------------------------- This message was sent using IMP, the Internet Messaging Program. No virus found in this incoming message. Checked by AVG - http://www.avg.com Version: 8.0.138 / Virus Database: 270.6.0/1604 - Release Date: 11/08/2008 05:50 |
|
From: Heiko Z. <he...@zu...> - 2008-08-12 14:33:54
|
Quoting Milton Calnek <mi...@ca...>: > -----BEGIN PGP SIGNED MESSAGE----- > Hash: SHA1 > > Hi, > > I was wondering if bind was going to be upgraded anytime soon? > P2 didn't make it obviously into 1.2.15. If you need P2, the 1.3 testing release on the FTP server has it. -- Regards Heiko Zuerker http://www.devil-linux.org ---------------------------------------------------------------- This message was sent using IMP, the Internet Messaging Program. |
|
From: Heiko Z. <he...@zu...> - 2008-08-11 18:39:30
|
Quoting Geir Inge <gei...@gm...>: > Thank you for your response. > > Is this the version I should test: > http://devil-linux.linjection.org/devel/testing/devil-linux-1.3.6-2008-08-05-i586.tar.bz2 > ? Yes try that one > I did not find a SMP release of DL 1.3 but that is probably not > important right now. All 1.3 releases are SMP > > Installing the 1.3.6 release on a usb stick with the included > install-on-usb script gives the same problems as the 1.5.12 release > (run on a ubuntu hardy machine) : > > 1) selecting lilo as the bootloader, the script fails: > > Do you want to edit the lilo menu file (y/n) n > cp: cannot stat `/boot/boot.b': No such file or directory > Install failed! > syncing and unmounting (this could take a while) > > 2) selecting syslinux as bootloader, the script fails: > > Installing syslinux MBR > 0+1 records in > 0+1 records out > 404 bytes (404 B) copied, 0.00895628 s, 45.1 kB/s > installing SysLinux boot sector > umount: /tmp/syslinux.mnt.4674.0: device is busy > umount: /tmp/syslinux.mnt.4674.0: device is busy > Install failed! > syncing and unmounting (this could take a while) > > Selecting grub (no serial), the script fails (work ok on the 1.2.15 > release) with: > > Configuring Grub boot sector and menu... > Do you want to edit the grub menu file (y/n) n > Probing devices to guess BIOS drives. This may take a long time. > ./install-on-usb: line 119: 5069 Segmentation fault $grub_shell > --batch --device-map=$device_map > /dev/null <<-EOF > root $root_drive > setup $force_lba $install_drive > quit > EOF > > Should we move to the develop mailinglist ? That may be best. Not sure about this one and I won't be able to look at it anytime soon. > On Mon, Aug 11, 2008 at 5:23 PM, Heiko Zuerker <he...@zu...> wrote: >> Quoting Geir Inge <gei...@gm...>: >> >>> Hi. >>> >>> I am trying to set up devil linux on a Intel D945GCLF motherboard >>> (mini itx format, atom cpu). >>> >>> DL has no problem booting and configuring my second network card >>> (intel pci card), but fails to load the r8169 module for the on-board >>> RTL8101E LAN adapter. >>> >>> Booting with a 2.6.25 kernel on the same motherboard, loads the >>> realtek driver without any >>> problems.http://devil-linux.linjection.org/devel/testing/devil-linux-1.3.6-2008-08-05-i586.tar.bz2 >>> >>> output from lspci (on DL): >>> >>> 01:00.0 Ethernet controller: Realtek Semiconductor Co., Ltd. RTL8101E >>> PCI Express Fast Ethernet controller (rev 02) >>> >>> >>> modprobe r8169 gives the following error: >>> >>> /lib/modules/2.4.36.6-grsec/kernel/drivers/net/r8169.o: init_module: >>> No such device >>> Hint: insmod errors can be caused by incorrect module parameters, >>> including invalid IO or IRQ parameters. >>> You may find more information in syslog or the output from dmesg >>> /lib/modules/2.4.36.6-grsec/kernel/drivers/net/r8169.o: insmod >>> /lib/modules/2.4.36.6-grsec/kernel/drivers/net/r8169.o failed >>> /lib/modules/2.4.36.6-grsec/kernel/drivers/net/r8169.o: insmod r8169 failed >>> >>> There is no record of this operation in dmesg or syslog (syslog is empty) >>> >>> Please advice >> >> Looks like the 2.4 Kernel doesn't like your card. >> Try using DL 1.3 (beta, but stable), it is based on the 2.6 Kernel and >> may just work. >> -- Regards Heiko Zuerker http://www.devil-linux.org ---------------------------------------------------------------- This message was sent using IMP, the Internet Messaging Program. |
|
From: Geir I. <gei...@gm...> - 2008-08-11 17:23:48
|
Thank you for your response. Is this the version I should test: http://devil-linux.linjection.org/devel/testing/devil-linux-1.3.6-2008-08-05-i586.tar.bz2 ? I did not find a SMP release of DL 1.3 but that is probably not important right now. Installing the 1.3.6 release on a usb stick with the included install-on-usb script gives the same problems as the 1.5.12 release (run on a ubuntu hardy machine) : 1) selecting lilo as the bootloader, the script fails: Do you want to edit the lilo menu file (y/n) n cp: cannot stat `/boot/boot.b': No such file or directory Install failed! syncing and unmounting (this could take a while) 2) selecting syslinux as bootloader, the script fails: Installing syslinux MBR 0+1 records in 0+1 records out 404 bytes (404 B) copied, 0.00895628 s, 45.1 kB/s installing SysLinux boot sector umount: /tmp/syslinux.mnt.4674.0: device is busy umount: /tmp/syslinux.mnt.4674.0: device is busy Install failed! syncing and unmounting (this could take a while) Selecting grub (no serial), the script fails (work ok on the 1.2.15 release) with: Configuring Grub boot sector and menu... Do you want to edit the grub menu file (y/n) n Probing devices to guess BIOS drives. This may take a long time. ./install-on-usb: line 119: 5069 Segmentation fault $grub_shell --batch --device-map=$device_map > /dev/null <<-EOF root $root_drive setup $force_lba $install_drive quit EOF Should we move to the develop mailinglist ? On Mon, Aug 11, 2008 at 5:23 PM, Heiko Zuerker <he...@zu...> wrote: > Quoting Geir Inge <gei...@gm...>: > >> Hi. >> >> I am trying to set up devil linux on a Intel D945GCLF motherboard >> (mini itx format, atom cpu). >> >> DL has no problem booting and configuring my second network card >> (intel pci card), but fails to load the r8169 module for the on-board >> RTL8101E LAN adapter. >> >> Booting with a 2.6.25 kernel on the same motherboard, loads the >> realtek driver without any problems.http://devil-linux.linjection.org/devel/testing/devil-linux-1.3.6-2008-08-05-i586.tar.bz2 >> >> output from lspci (on DL): >> >> 01:00.0 Ethernet controller: Realtek Semiconductor Co., Ltd. RTL8101E >> PCI Express Fast Ethernet controller (rev 02) >> >> >> modprobe r8169 gives the following error: >> >> /lib/modules/2.4.36.6-grsec/kernel/drivers/net/r8169.o: init_module: >> No such device >> Hint: insmod errors can be caused by incorrect module parameters, >> including invalid IO or IRQ parameters. >> You may find more information in syslog or the output from dmesg >> /lib/modules/2.4.36.6-grsec/kernel/drivers/net/r8169.o: insmod >> /lib/modules/2.4.36.6-grsec/kernel/drivers/net/r8169.o failed >> /lib/modules/2.4.36.6-grsec/kernel/drivers/net/r8169.o: insmod r8169 failed >> >> There is no record of this operation in dmesg or syslog (syslog is empty) >> >> Please advice > > Looks like the 2.4 Kernel doesn't like your card. > Try using DL 1.3 (beta, but stable), it is based on the 2.6 Kernel and > may just work. > > -- > > Regards > Heiko Zuerker > http://www.devil-linux.org > > > ---------------------------------------------------------------- > This message was sent using IMP, the Internet Messaging Program. > > > ------------------------------------------------------------------------- > This SF.Net email is sponsored by the Moblin Your Move Developer's challenge > Build the coolest Linux based applications with Moblin SDK & win great prizes > Grand prize is a trip for two to an Open Source event anywhere in the world > http://moblin-contest.org/redirect.php?banner_id=100&url=/ > _______________________________________________ > Devil-linux-discuss mailing list > Dev...@li... > https://lists.sourceforge.net/lists/listinfo/devil-linux-discuss > |
|
From: Milton C. <mi...@ca...> - 2008-08-11 15:32:19
|
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Hi, I was wondering if bind was going to be upgraded anytime soon? - -- Milton Calnek BSc, A/Slt(Ret.) mi...@ca... 306-717-8737 -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.5 (GNU/Linux) Comment: Using GnuPG with CentOS - http://enigmail.mozdev.org iD8DBQFIoFuBHgnbf2T2QqMRAmUbAKCURpgkNg5yuZpNQ42zykwgbua0nwCbBibG hNfSpwJoupZXaRRSm5HA/1o= =71Ez -----END PGP SIGNATURE----- -- This message has been scanned for viruses and dangerous content by MailScanner, and is believed to be clean. |
|
From: Heiko Z. <he...@zu...> - 2008-08-11 15:23:14
|
Quoting Geir Inge <gei...@gm...>: > Hi. > > I am trying to set up devil linux on a Intel D945GCLF motherboard > (mini itx format, atom cpu). > > DL has no problem booting and configuring my second network card > (intel pci card), but fails to load the r8169 module for the on-board > RTL8101E LAN adapter. > > Booting with a 2.6.25 kernel on the same motherboard, loads the > realtek driver without any problems. > > output from lspci (on DL): > > 01:00.0 Ethernet controller: Realtek Semiconductor Co., Ltd. RTL8101E > PCI Express Fast Ethernet controller (rev 02) > > > modprobe r8169 gives the following error: > > /lib/modules/2.4.36.6-grsec/kernel/drivers/net/r8169.o: init_module: > No such device > Hint: insmod errors can be caused by incorrect module parameters, > including invalid IO or IRQ parameters. > You may find more information in syslog or the output from dmesg > /lib/modules/2.4.36.6-grsec/kernel/drivers/net/r8169.o: insmod > /lib/modules/2.4.36.6-grsec/kernel/drivers/net/r8169.o failed > /lib/modules/2.4.36.6-grsec/kernel/drivers/net/r8169.o: insmod r8169 failed > > There is no record of this operation in dmesg or syslog (syslog is empty) > > Please advice Looks like the 2.4 Kernel doesn't like your card. Try using DL 1.3 (beta, but stable), it is based on the 2.6 Kernel and may just work. -- Regards Heiko Zuerker http://www.devil-linux.org ---------------------------------------------------------------- This message was sent using IMP, the Internet Messaging Program. |
|
From: Heiko Z. <he...@zu...> - 2008-08-11 15:18:46
|
It may be an incomatability between the USB device and the Linux Kernel. Do the devices work on the USB 1.1 ports? You could also try the 1.3 version of DL (beta, but very stable), which is based on the 2.6 Kernel. Heiko Quoting Chris Grove <dj_...@ti...>: > > > Hi all, I've got devil linux running very nicely on my little MSI machine. The problem is that the onboard ports are only usb 1.1 compliant. So I thought "I know, i'll buy a usb 2.0 PCI card" This all worked out well as i found a nice little one with a VIA chipset on ebay. It arrived, and i installed it. Now here's where the fun starts. Linux sees the device during boot-up. It also sees it if I type in lspci, but I can't see/mount any hdd's or memory sticks that I plug in. Has anybody any ideas please. In case its any help, here's what lspci has to say about it: > this is the onboard one: > 00:1f.2 USB Controller: Intel Corporation 82801BA/BAM USB Controller #1 (rev 05) > 00:1f.4 USB Controller: Intel Corporation 82801BA/BAM USB Controller #1 (rev 05) > and this is the PCI one: > 01:00.0 USB Controller: VIA Technologies, Inc. VT82xxxxx UHCI USB 1.1 Controller (rev 62) > 01:00.1 USB Controller: VIA Technologies, Inc. VT82xxxxx UHCI USB 1.1 Controller (rev 62) > 01:00.2 USB Controller: VIA Technologies, Inc. USB 2.0 (rev 65) > > > > > > > > > > > > > > > > And dmesg says this: > > > > > > > > usb.c: registered new driver usbdevfs > usb.c: registered new driver hub > PCI: Found IRQ 5 for device 01:00.2 > ehci_hcd 01:00.2: VIA Technologies, Inc. USB 2.0 > ehci_hcd 01:00.2: irq 5, pci mem c881e000 > usb.c: new USB bus registered, assigned bus number 1 > ehci_hcd 01:00.2: USB 2.0 enabled, EHCI 1.00, driver 2003-Dec-29/2.4 > hub.c: USB hub found > hub.c: 4 ports detected > host/usb-uhci.c: $Revision: 1.275 $ time 19:10:59 Nov 20 2007 > host/usb-uhci.c: High bandwidth mode enabled > PCI: Found IRQ 12 for device 00:1f.2 > PCI: Setting latency timer of device 00:1f.2 to 64 > host/usb-uhci.c: USB UHCI at I/O 0xcc00, IRQ 12 > host/usb-uhci.c: Detected 2 ports > usb.c: new USB bus registered, assigned bus number 2 > hub.c: USB hub found > hub.c: 2 ports detected > PCI: Found IRQ 10 for device 00:1f.4 > PCI: Setting latency timer of device 00:1f.4 to 64 > host/usb-uhci.c: USB UHCI at I/O 0xd400, IRQ 10 > host/usb-uhci.c: Detected 2 ports > usb.c: new USB bus registered, assigned bus number 3 > hub.c: USB hub found > hub.c: 2 ports detected > PCI: Found IRQ 11 for device 01:00.1 > PCI: Sharing IRQ 11 with 00:1f.3 > PCI: Sharing IRQ 11 with 00:1f.5 > host/usb-uhci.c: USB UHCI at I/O 0xac00, IRQ 11 > host/usb-uhci.c: Detected 2 ports > usb.c: new USB bus registered, assigned bus number 4 > hub.c: USB hub found > hub.c: 2 ports detected > PCI: Found IRQ 9 for device 01:00.0 > PCI: Sharing IRQ 9 with 00:02.0 > host/usb-uhci.c: USB UHCI at I/O 0xa800, IRQ 9 > host/usb-uhci.c: Detected 2 ports > usb.c: new USB bus registered, assigned bus number 5 > hub.c: USB hub found > hub.c: 2 ports detected > host/usb-uhci.c: v1.275:USB Universal Host Controller Interface driver > usb.c: registered new driver hiddev > usb.c: registered new driver hid > hid-core.c: v1.8.1 Andreas Gal, Vojtech Pavlik <vo...@su...[1]> > hid-core.c: USB HID support drivers > Initializing USB Mass Storage driver... > usb.c: registered new driver usb-storage > USB Mass Storage support registered. > Initializing Cryptographic API > IEEE 802.2 LLC for Linux 2.1 (c) 1996 Tim Alpaerts > NET4: Linux TCP/IP 1.0 for NET4.0 > IP Protocols: ICMP, UDP, TCP, IGMP > IP: routing cache hash table of 512 buckets, 4Kbytes > TCP: Hash tables configured (established 8192 bind 8192) > Linux IP multicast router 0.06 plus PIM-SM > NET4: Unix domain sockets 1.0/SMP for Linux NET4.0. > 802.1Q VLAN Support v1.8 Ben Greear <gr...@ca...[2]> > All bugs added by David S. Miller <da...@re...[3]> > RAMDISK: Compressed image found at block 0 > hub.c: new USB device 00:1f.2-1, assigned address 2 > Freeing initrd memory: 2522k freed > VFS: Mounted root (cramfs filesystem) readonly. > Mounted devfs on /dev > Freeing unused kernel memory: 156k freed > scsi0 : SCSI emulation for USB Mass Storage devices > Vendor: Model: Hitachi HDT72503 Rev: V54O > Type: Direct-Access ANSI SCSI revision: 02 > Attached scsi disk sda at scsi0, channel 0, id 0, lun 0 > SCSI device sda: 625142448 512-byte hdwr sectors (320073 MB) > /dev/scsi/host0/bus0/target0/lun0: p1 > WARNING: USB Mass Storage data integrity not assured > USB Mass Storage device found at 2 > hub.c: new USB device 00:1f.2-2, assigned address 3 > scsi1 : SCSI emulation for USB Mass Storage devices > Vendor: Maxtor 2 Model: B010H1 Rev: 0 0 > Type: Direct-Access ANSI SCSI revision: 02 > Attached scsi disk sdb at scsi1, channel 0, id 0, lun 0 > SCSI device sdb: 20012832 512-byte hdwr sectors (10247 MB) > /dev/scsi/host1/bus0/target0/lun0: p1 > WARNING: USB Mass Storage data integrity not assured > USB Mass Storage device found at 3 > hub.c: new USB device 01:00.2-4, assigned address 2 > usb_control/bulk_msg: timeout > usb.c: USB device not accepting new address=2 (error=-110) > hub.c: new USB device 01:00.2-4, assigned address 3 > usb_control/bulk_msg: timeout > usb.c: USB device not accepting new address=3 (error=-110) > > I've tried turning to onboard one off, and starting again with a blank config, neither of which work. Any help would be greatly appreciated.. Thanks in advance for your help. > > > > -- Regards Heiko Zuerker http://www.devil-linux.org[4] Links: ------ [1] mailto:vo...@su... [2] mailto:gr...@ca... [3] mailto:da...@re... [4] http://www.devil-linux.org/ ---------------------------------------------------------------- This message was sent using IMP, the Internet Messaging Program. |
|
From: Geir I. <gei...@gm...> - 2008-08-10 09:07:48
|
Hi.
I am trying to set up devil linux on a Intel D945GCLF motherboard
(mini itx format, atom cpu).
DL has no problem booting and configuring my second network card
(intel pci card), but fails to load the r8169 module for the on-board
RTL8101E LAN adapter.
Booting with a 2.6.25 kernel on the same motherboard, loads the
realtek driver without any problems.
output from lspci (on DL):
01:00.0 Ethernet controller: Realtek Semiconductor Co., Ltd. RTL8101E
PCI Express Fast Ethernet controller (rev 02)
modprobe r8169 gives the following error:
/lib/modules/2.4.36.6-grsec/kernel/drivers/net/r8169.o: init_module:
No such device
Hint: insmod errors can be caused by incorrect module parameters,
including invalid IO or IRQ parameters.
You may find more information in syslog or the output from dmesg
/lib/modules/2.4.36.6-grsec/kernel/drivers/net/r8169.o: insmod
/lib/modules/2.4.36.6-grsec/kernel/drivers/net/r8169.o failed
/lib/modules/2.4.36.6-grsec/kernel/drivers/net/r8169.o: insmod r8169 failed
There is no record of this operation in dmesg or syslog (syslog is empty)
Please advice
|
|
From: Chris G. <dj_...@ti...> - 2008-08-08 17:44:59
|
Hi all, I've got devil linux running very nicely on my little MSI machine. The problem is that the onboard ports are only usb 1.1 compliant. So I thought "I know, i'll buy a usb 2.0 PCI card" This all worked out well as i found a nice little one with a VIA chipset on ebay. It arrived, and i installed it. Now here's where the fun starts. Linux sees the device during boot-up. It also sees it if I type in lspci, but I can't see/mount any hdd's or memory sticks that I plug in. Has anybody any ideas please. In case its any help, here's what lspci has to say about it: this is the onboard one: 00:1f.2 USB Controller: Intel Corporation 82801BA/BAM USB Controller #1 (rev 05) 00:1f.4 USB Controller: Intel Corporation 82801BA/BAM USB Controller #1 (rev 05) and this is the PCI one: 01:00.0 USB Controller: VIA Technologies, Inc. VT82xxxxx UHCI USB 1.1 Controller (rev 62) 01:00.1 USB Controller: VIA Technologies, Inc. VT82xxxxx UHCI USB 1.1 Controller (rev 62) 01:00.2 USB Controller: VIA Technologies, Inc. USB 2.0 (rev 65) And dmesg says this: usb.c: registered new driver usbdevfs usb.c: registered new driver hub PCI: Found IRQ 5 for device 01:00.2 ehci_hcd 01:00.2: VIA Technologies, Inc. USB 2.0 ehci_hcd 01:00.2: irq 5, pci mem c881e000 usb.c: new USB bus registered, assigned bus number 1 ehci_hcd 01:00.2: USB 2.0 enabled, EHCI 1.00, driver 2003-Dec-29/2.4 hub.c: USB hub found hub.c: 4 ports detected host/usb-uhci.c: $Revision: 1.275 $ time 19:10:59 Nov 20 2007 host/usb-uhci.c: High bandwidth mode enabled PCI: Found IRQ 12 for device 00:1f.2 PCI: Setting latency timer of device 00:1f.2 to 64 host/usb-uhci.c: USB UHCI at I/O 0xcc00, IRQ 12 host/usb-uhci.c: Detected 2 ports usb.c: new USB bus registered, assigned bus number 2 hub.c: USB hub found hub.c: 2 ports detected PCI: Found IRQ 10 for device 00:1f.4 PCI: Setting latency timer of device 00:1f.4 to 64 host/usb-uhci.c: USB UHCI at I/O 0xd400, IRQ 10 host/usb-uhci.c: Detected 2 ports usb.c: new USB bus registered, assigned bus number 3 hub.c: USB hub found hub.c: 2 ports detected PCI: Found IRQ 11 for device 01:00.1 PCI: Sharing IRQ 11 with 00:1f.3 PCI: Sharing IRQ 11 with 00:1f.5 host/usb-uhci.c: USB UHCI at I/O 0xac00, IRQ 11 host/usb-uhci.c: Detected 2 ports usb.c: new USB bus registered, assigned bus number 4 hub.c: USB hub found hub.c: 2 ports detected PCI: Found IRQ 9 for device 01:00.0 PCI: Sharing IRQ 9 with 00:02.0 host/usb-uhci.c: USB UHCI at I/O 0xa800, IRQ 9 host/usb-uhci.c: Detected 2 ports usb.c: new USB bus registered, assigned bus number 5 hub.c: USB hub found hub.c: 2 ports detected host/usb-uhci.c: v1.275:USB Universal Host Controller Interface driver usb.c: registered new driver hiddev usb.c: registered new driver hid hid-core.c: v1.8.1 Andreas Gal, Vojtech Pavlik <vo...@su...> hid-core.c: USB HID support drivers Initializing USB Mass Storage driver... usb.c: registered new driver usb-storage USB Mass Storage support registered. Initializing Cryptographic API IEEE 802.2 LLC for Linux 2.1 (c) 1996 Tim Alpaerts NET4: Linux TCP/IP 1.0 for NET4.0 IP Protocols: ICMP, UDP, TCP, IGMP IP: routing cache hash table of 512 buckets, 4Kbytes TCP: Hash tables configured (established 8192 bind 8192) Linux IP multicast router 0.06 plus PIM-SM NET4: Unix domain sockets 1.0/SMP for Linux NET4.0. 802.1Q VLAN Support v1.8 Ben Greear <gr...@ca...> All bugs added by David S. Miller <da...@re...> RAMDISK: Compressed image found at block 0 hub.c: new USB device 00:1f.2-1, assigned address 2 Freeing initrd memory: 2522k freed VFS: Mounted root (cramfs filesystem) readonly. Mounted devfs on /dev Freeing unused kernel memory: 156k freed scsi0 : SCSI emulation for USB Mass Storage devices Vendor: Model: Hitachi HDT72503 Rev: V54O Type: Direct-Access ANSI SCSI revision: 02 Attached scsi disk sda at scsi0, channel 0, id 0, lun 0 SCSI device sda: 625142448 512-byte hdwr sectors (320073 MB) /dev/scsi/host0/bus0/target0/lun0: p1 WARNING: USB Mass Storage data integrity not assured USB Mass Storage device found at 2 hub.c: new USB device 00:1f.2-2, assigned address 3 scsi1 : SCSI emulation for USB Mass Storage devices Vendor: Maxtor 2 Model: B010H1 Rev: 0 0 Type: Direct-Access ANSI SCSI revision: 02 Attached scsi disk sdb at scsi1, channel 0, id 0, lun 0 SCSI device sdb: 20012832 512-byte hdwr sectors (10247 MB) /dev/scsi/host1/bus0/target0/lun0: p1 WARNING: USB Mass Storage data integrity not assured USB Mass Storage device found at 3 hub.c: new USB device 01:00.2-4, assigned address 2 usb_control/bulk_msg: timeout usb.c: USB device not accepting new address=2 (error=-110) hub.c: new USB device 01:00.2-4, assigned address 3 usb_control/bulk_msg: timeout usb.c: USB device not accepting new address=3 (error=-110) I've tried turning to onboard one off, and starting again with a blank config, neither of which work. Any help would be greatly appreciated.. Thanks in advance for your help. |
|
From: Dick M. <di...@fo...> - 2008-08-06 12:19:41
|
KyleJHarper wrote: > In my experience with PAM there is always a file called system-auth or > common-auth in the /etc/pam.d/ directory. When I load devil I do not see > either of these files. These are distro specific configurations. Debian for example, uses them. They're just include files; separates out the common parts of a pam file. No reason why you can't do the same in DL. Empahasis on the *you* since DL doesn't provide default configs (unlike other distros). Several of my DL configs are copied, more or less, from Debian. Dick |
|
From: Heiko Z. <he...@zu...> - 2008-08-06 12:12:01
|
Hey, PAM is actually active and working in DL. The PAM configuration you see is the default one as it's delivered from the developers of the package. I'd say search on google for instructions on what specifically you're trying to implement/solve. Heiko Quoting KyleJHarper <ky...@ca...>: > > In my experience with PAM there is always a file called system-auth or > common-auth in the /etc/pam.d/ directory. When I load devil I do not see > either of these files. > > I have tried manually adding each of these files and configuring them > accordingly but they never affect my login settings like they do on other > linux machines I have. > > Can anyone help point me in the right direction for using PAM with devil? > I'm sure the missing files are intentional, I'm just not comprehending how > to get this going... > > Thanks, > Kyle Harper > -- > View this message in context: > http://www.nabble.com/PAM-common-system-auth-tp18843467p18843467.html > Sent from the devil-linux-discuss mailing list archive at Nabble.com. > > > ------------------------------------------------------------------------- > This SF.Net email is sponsored by the Moblin Your Move Developer's challenge > Build the coolest Linux based applications with Moblin SDK & win great prizes > Grand prize is a trip for two to an Open Source event anywhere in the world > http://moblin-contest.org/redirect.php?banner_id=100&url=/ > _______________________________________________ > Devil-linux-discuss mailing list > Dev...@li... > https://lists.sourceforge.net/lists/listinfo/devil-linux-discuss > -- Regards Heiko Zuerker http://www.devil-linux.org ---------------------------------------------------------------- This message was sent using IMP, the Internet Messaging Program. |
|
From: KyleJHarper <ky...@ca...> - 2008-08-06 03:01:46
|
In my experience with PAM there is always a file called system-auth or common-auth in the /etc/pam.d/ directory. When I load devil I do not see either of these files. I have tried manually adding each of these files and configuring them accordingly but they never affect my login settings like they do on other linux machines I have. Can anyone help point me in the right direction for using PAM with devil? I'm sure the missing files are intentional, I'm just not comprehending how to get this going... Thanks, Kyle Harper -- View this message in context: http://www.nabble.com/PAM-common-system-auth-tp18843467p18843467.html Sent from the devil-linux-discuss mailing list archive at Nabble.com. |
|
From: Heiko Z. <he...@zu...> - 2008-07-30 19:19:01
|
Quoting Bruce Smith <bw...@re...>: >>> I have the latest DL 1.3.6 running in VMware ESX 3i server with the >>> VMware tools running. >>> >>> I changed the settings on the VM so the reset button and the power >>> button to reboot/shutdown the server instead of a hard reset or >>> power-off. >>> >>> Now when I press the power or reset button with DL running, it pops up >>> a message saying: >>> "A general system error Occurred: Cannot execute scripts". >> >> It used to work. >> These are the files which handle the shutdown: >> >> ls -la /etc/vmware-tools/ >> >> -rwxrwxr-x 1 root root 1332 Dec 31 1979 poweroff-vm-default >> -rwxrwxr-x 1 root root 1332 Dec 31 1979 poweron-vm-default >> -rwxrwxr-x 1 root root 3023 Dec 31 1979 resume-vm-default >> -rwxrwxr-x 1 root root 2619 Dec 31 1979 suspend-vm-default > > Yes, I have those four scripts on my DL too. > > How does VMware know where to find the scripts, and the script names? > Maybe something changed? I'm not sure. Check the open-vm-tools sources if they mention anything... -- Regards Heiko Zuerker http://www.devil-linux.org ---------------------------------------------------------------- This message was sent using IMP, the Internet Messaging Program. |
|
From: Bruce S. <bw...@re...> - 2008-07-30 18:22:16
|
>> I have the latest DL 1.3.6 running in VMware ESX 3i server with the >> VMware tools running. >> >> I changed the settings on the VM so the reset button and the power >> button to reboot/shutdown the server instead of a hard reset or >> power-off. >> >> Now when I press the power or reset button with DL running, it pops up >> a message saying: >> "A general system error Occurred: Cannot execute scripts". > > It used to work. > These are the files which handle the shutdown: > > ls -la /etc/vmware-tools/ > > -rwxrwxr-x 1 root root 1332 Dec 31 1979 poweroff-vm-default > -rwxrwxr-x 1 root root 1332 Dec 31 1979 poweron-vm-default > -rwxrwxr-x 1 root root 3023 Dec 31 1979 resume-vm-default > -rwxrwxr-x 1 root root 2619 Dec 31 1979 suspend-vm-default Yes, I have those four scripts on my DL too. How does VMware know where to find the scripts, and the script names? Maybe something changed? - BS |
|
From: Heiko Z. <he...@zu...> - 2008-07-30 18:12:37
|
Quoting Bruce Smith <bw...@re...>: > I have the latest DL 1.3.6 running in VMware ESX 3i server with the > VMware tools running. > > I changed the settings on the VM so the reset button and the power > button to reboot/shutdown the server instead of a hard reset or > power-off. > > Now when I press the power or reset button with DL running, it pops up > a message saying: > "A general system error Occurred: Cannot execute scripts". > > Is something not configured correctly? Or is it possible to make this work? It used to work. These are the files which handle the shutdown: ls -la /etc/vmware-tools/ -rwxrwxr-x 1 root root 1332 Dec 31 1979 poweroff-vm-default -rwxrwxr-x 1 root root 1332 Dec 31 1979 poweron-vm-default -rwxrwxr-x 1 root root 3023 Dec 31 1979 resume-vm-default -rwxrwxr-x 1 root root 2619 Dec 31 1979 suspend-vm-default -- Regards Heiko Zuerker http://www.devil-linux.org ---------------------------------------------------------------- This message was sent using IMP, the Internet Messaging Program. |
|
From: Bruce S. <bw...@re...> - 2008-07-30 18:05:29
|
I have the latest DL 1.3.6 running in VMware ESX 3i server with the VMware tools running. I changed the settings on the VM so the reset button and the power button to reboot/shutdown the server instead of a hard reset or power-off. Now when I press the power or reset button with DL running, it pops up a message saying: "A general system error Occurred: Cannot execute scripts". Is something not configured correctly? Or is it possible to make this work? - BS |
50 messages has been excluded from this view by a project administrator.
