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: John B. <jbr...@gm...> - 2008-08-30 13:15:01
|
On Sat, Aug 30, 2008 at 3:06 AM, Dick Middleton <di...@fo...> wrote: > > dmesg | more > > > > > > If I ever got it to a prompt. Or am I missing something? > > good point, sorry. > No, it's OK. I'm certainly not above missing the obvious! 8-) I'll report back once I get a bigger usb drive. Thanks for all the help! -- John Bridleman |
|
From: Dick M. <di...@fo...> - 2008-08-30 07:06:28
|
John Bridleman wrote: > On Fri, Aug 29, 2008 at 7:07 PM, Dick Middleton <di...@fo... > <mailto:di...@fo...>> wrote: > > John Bridleman wrote: > > > it will be with SATA - probably /dev/scd*. dmesg will tell you > > what's happening. > > > > > > Scrolls by so fast .... > > dmesg | more > > > If I ever got it to a prompt. Or am I missing something? good point, sorry. Dick |
|
From: Dom <dl...@ed...> - 2008-08-30 06:17:14
|
Heiko Zuerker wrote: >> -----Original Message----- >> From: dev...@li... [mailto:devil- >> lin...@li...] On Behalf Of Bruce Smith >> Sent: Friday, August 29, 2008 8:28 AM >> To: dev...@li... >> Subject: Re: [Devil-Linux-discuss] DL 1.3.6-2008-08-28-i686 Error >> message on save-config >> >> >>> 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. >>> >> Yes, it's always a good idea to make a copy of the config for backup >> purposes. >> >> >>> 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? >>> >> I haven't done much with the install-on-usb script for a long, so I'm >> probably not the best one to answer that question. >> >> Personally I really like the "RUNFROMRAM=y" option. (It takes an >> extra quarter GB of memory, but memory is cheap) That way the entire >> CD is read into RAM upon initial bootup and then the system runs from >> memory. It takes longer to boot, but after that, the system is FAST >> because it never has to go back to read the CD. >> >> > > There may be a problem with the latest 1.3.x and running from a media other > then CD. > I tried upgrading my Firewall last weekend and it blew up (found the ISO but > couldn't use it for some strange reason). > I had not have any time to investigate it. > > Heiko OK, on the principle of "if it ain't broke, don't fix it", I think I'll stick with CD-based running for now. Well I'm here I find myself thinking of a couple of other things: - Could anyone who understands these things upgrade Nano in DL 1.3 to v2? Nano is now DL's default editor, which is good for me, but DL is using v1.2.4. - In DL 1.3 the default configuration of Postfix (main.cf) requires as data_directory a directory /var/lib/postfix owned by postfix, so you have to create this manually after each boot before Postfix will work, how do I automate this process (and could this be fixed for a future release)? And even with this fixed manually I am at present unable to get Postfix working after the upgrade to DL 1.3. - What is the easiest way to configure DL to send outgoing emails (e.g. for crontab messages / warning / diagnostic purposes)? Maybe I don't need to use Postfix at all! Thanks and have a good weekend! Dom http://www.edendevelopments.co.uk/dlsetup |
|
From: John B. <jbr...@gm...> - 2008-08-30 01:50:42
|
On Fri, Aug 29, 2008 at 7:07 PM, Dick Middleton <di...@fo...> wrote: > John Bridleman wrote: > > > it will be with SATA - probably /dev/scd*. dmesg will tell you > > what's happening. > > > > > > Scrolls by so fast .... > > dmesg | more If I ever got it to a prompt. Or am I missing something? -- John Bridleman |
|
From: Dick M. <di...@fo...> - 2008-08-29 23:07:37
|
John Bridleman wrote: > it will be with SATA - probably /dev/scd*. dmesg will tell you > what's happening. > > > Scrolls by so fast .... dmesg | more Dick |
|
From: John B. <jbr...@gm...> - 2008-08-29 21:18:19
|
On Fri, Aug 29, 2008 at 5:10 PM, Chris Grove <dj_...@ti...>wrote: > I'm no developer and in fact I'm almost as stuck as you, but how about > trying a USB CDROM or an adapter to convert a SATA drive to a USB drive. > It's just a thought, If your motherboard supports booting from USB it might > allow it to boot properly. > Yea, I'm going to try the usb route this weekend. In the end, I think it will be a better solution anyway. -- John Bridleman |
|
From: Chris G. <dj_...@ti...> - 2008-08-29 21:11:12
|
I'm no developer and in fact I'm almost as stuck as you, but how about trying a USB CDROM or an adapter to convert a SATA drive to a USB drive. It's just a thought, If your motherboard supports booting from USB it might allow it to boot properly. From: dev...@li... [mailto:dev...@li...] On Behalf Of John Bridleman Sent: 29 August 2008 22:04 To: dev...@li... Subject: Re: [Devil-Linux-discuss] SATA CDROM boot problem? On Fri, Aug 29, 2008 at 4:32 PM, Heiko Zuerker <he...@zu...> wrote: How about going with a workaround if everything else fails? Can you install a plain old IDE-CDROM in the box ? Nope. sigh. It's got a connector for a floppy on the mboard but no IDE. 8-( Some day one of us will own a SATA CDROM too, then we can test it. I'll see when I need to have this up and running. Maybe I'll have time to drop it off at one of the developers house. ;-) -- John Bridleman No virus found in this incoming message. Checked by AVG - http://www.avg.com Version: 8.0.138 / Virus Database: 270.6.13/1641 - Release Date: 29/08/2008 07:07 |
|
From: John B. <jbr...@gm...> - 2008-08-29 21:03:37
|
On Fri, Aug 29, 2008 at 4:32 PM, Heiko Zuerker <he...@zu...> wrote: > How about going with a workaround if everything else fails? > > Can you install a plain old IDE-CDROM in the box ? > Nope. sigh. It's got a connector for a floppy on the mboard but no IDE. 8-( > Some day one of us will own a SATA CDROM too, then we can test it. > I'll see when I need to have this up and running. Maybe I'll have time to drop it off at one of the developers house. ;-) -- John Bridleman |
|
From: Heiko Z. <he...@zu...> - 2008-08-29 20:32:09
|
How about going with a workaround if everything else fails? Can you install a plain old IDE-CDROM in the box ? Some day one of us will own a SATA CDROM too, then we can test it. Heiko From: dev...@li... [mailto:dev...@li...] On Behalf Of John Bridleman Sent: Friday, August 29, 2008 3:17 PM To: di...@fo...; dev...@li... Subject: Re: [Devil-Linux-discuss] SATA CDROM boot problem? On Fri, Aug 29, 2008 at 3:02 PM, Dick Middleton <di...@fo...> wrote: Is it that there are 2 problems here? You have a problem finding a driver for your CDROM? You're stuck in a logical loop because you don't have a config file? There are a few funnies with the start-up script when there is no config file. I've pointed out a few in the past but they're not showstoppers and there's more interesting things to work on. The best plan is to put a config file on the USB stick before you start. If you don't want to do that you have to tell DL where you want to put your config file otherwise you get into the loop. echo device > /shm/DL_DEVICE or save-config -d device I did try that although it was an older (1.2) config file. It says: Pre-UnionFS config file found loading configuration Searching for Devil-Linux CD-ROM Search list: checking /dev/sda1 ... wrong media !!! Devil-Linux CD-ROM not found ..... > A friend mentioned it might be a "DL doesn't like to be booted from a > sata cdrom drive problem". DL uses a recent kernel; if there's a driver for your drive it will use it. Otherwise you're stuffed! I'm beginning to feel that way! 8-) If you're using IDE the device will be /dev/hd* or /dev/scd* - I don't know what it will be with SATA - probably /dev/scd*. dmesg will tell you what's happening. Scrolls by so fast .... To duck the problem is it possible you could use a USB stick for the ISO image? It's only about 256MB so it's not such a big deal these days. Personally I use a USB stick with one partition for the ISO and another (ext3) for the config files. If you have enough RAM you can use "copy ISO to ram" which allows you to remove the USB stick once you've booted. I've only got a small stick right now so I'm off to the store this weekend. I was able to get ubuntu working on this box but I would really rather use DL. |
|
From: John B. <jbr...@gm...> - 2008-08-29 20:17:23
|
On Fri, Aug 29, 2008 at 3:02 PM, Dick Middleton <di...@fo...> wrote: > Is it that there are 2 problems here? You have a problem finding a driver > for > your CDROM? You're stuck in a logical loop because you don't have a > config file? > > There are a few funnies with the start-up script when there is no config > file. > I've pointed out a few in the past but they're not showstoppers and there's > more > interesting things to work on. > > The best plan is to put a config file on the USB stick before you start. > If you > don't want to do that you have to tell DL where you want to put your config > file > otherwise you get into the loop. echo device > /shm/DL_DEVICE or > save-config -d > device I did try that although it was an older (1.2) config file. It says: Pre-UnionFS config file found loading configuration Searching for Devil-Linux CD-ROM Search list: checking /dev/sda1 ... wrong media !!! Devil-Linux CD-ROM not found ..... > A friend mentioned it might be a "DL doesn't like to be booted from a > > sata cdrom drive problem". > > DL uses a recent kernel; if there's a driver for your drive it will use it. > Otherwise you're stuffed! I'm beginning to feel that way! 8-) If you're using IDE the device will be /dev/hd* or /dev/scd* - I don't know > what > it will be with SATA - probably /dev/scd*. dmesg will tell you what's > happening. Scrolls by so fast .... > To duck the problem is it possible you could use a USB stick for the ISO > image? > It's only about 256MB so it's not such a big deal these days. Personally > I > use a USB stick with one partition for the ISO and another (ext3) for the > config > files. If you have enough RAM you can use "copy ISO to ram" which allows > you to > remove the USB stick once you've booted. I've only got a small stick right now so I'm off to the store this weekend. > I was able to get ubuntu working on this box but I would really rather use DL. -- John Bridleman |
|
From: Chris G. <dj_...@ti...> - 2008-08-29 20:14:36
|
The problem is that it's an HDD that works ok on the onboard USB ports. I've tried it with the newer kernel version but dmesg doesn't even see a device when you plug it in. It does however tell me that the device isn't running at full speed if I plug the HDD into the USB 1.1 ports. -----Original Message----- From: dev...@li... [mailto:dev...@li...] On Behalf Of Dick Middleton Sent: 29 August 2008 21:04 To: dev...@li... Subject: Re: [Devil-Linux-discuss] Devil-Linux with a PCI USB card Chris Grove wrote: > 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. > /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) USB controler is telling you it cannot set the address on the device you've plugged in; it's timing out. This could be a device error (possibly the caddy) or it could be scsi emulation problem. I have vague memory that scsi emulation was incompatible with atapi cdroms or some such. Try a USB stick, see if you can get that to work. The suggestion to move to linux 2.6 on DL 1.3 is probably a good one if it's a driver problem. Won't help if you've duff device. Dick ------------------------------------------------------------------------- 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 No virus found in this incoming message. Checked by AVG - http://www.avg.com Version: 8.0.138 / Virus Database: 270.6.13/1641 - Release Date: 29/08/2008 07:07 |
|
From: Dick M. <di...@fo...> - 2008-08-29 20:04:12
|
Chris Grove wrote: > 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. > /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) USB controler is telling you it cannot set the address on the device you've plugged in; it's timing out. This could be a device error (possibly the caddy) or it could be scsi emulation problem. I have vague memory that scsi emulation was incompatible with atapi cdroms or some such. Try a USB stick, see if you can get that to work. The suggestion to move to linux 2.6 on DL 1.3 is probably a good one if it's a driver problem. Won't help if you've duff device. Dick |
|
From: Chris G. <dj_...@ti...> - 2008-08-29 19:57:24
|
Ok, so that's all those possibilities exhausted. So what else can I try to get these ports working, or am I just destine to very sloooooow transfer rates?? -----Original Message----- From: dev...@li... [mailto:dev...@li...] On Behalf Of Heiko Zuerker Sent: 29 August 2008 20:30 To: dev...@li... Subject: Re: [Devil-Linux-discuss] Devil-Linux with a PCI USB card > -----Original Message----- > From: dev...@li... [mailto:devil- > lin...@li...] On Behalf Of Bruce Smith > Sent: Friday, August 29, 2008 2:27 PM > To: dev...@li... > Subject: Re: [Devil-Linux-discuss] Devil-Linux with a PCI USB card > > It shouldn't make any difference for USB. > > The i586 version _may_ have grsecurity enabled (is it working now > Heiko)? > But I don't know what difference that would make either. Yes GRSecurity is working in 1.3. H. ------------------------------------------------------------------------- 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: Heiko Z. <he...@zu...> - 2008-08-29 19:30:31
|
> -----Original Message----- > From: dev...@li... [mailto:devil- > lin...@li...] On Behalf Of Bruce Smith > Sent: Friday, August 29, 2008 2:27 PM > To: dev...@li... > Subject: Re: [Devil-Linux-discuss] Devil-Linux with a PCI USB card > > It shouldn't make any difference for USB. > > The i586 version _may_ have grsecurity enabled (is it working now > Heiko)? > But I don't know what difference that would make either. Yes GRSecurity is working in 1.3. H. |
|
From: Bruce S. <bw...@re...> - 2008-08-29 19:27:16
|
It shouldn't make any difference for USB. The i586 version _may_ have grsecurity enabled (is it working now Heiko)? But I don't know what difference that would make either. - BS On Fri, Aug 29, 2008 at 3:11 PM, Chris Grove <dj_...@ti...> wrote: > Ok cool, So is there any chance that the different versions 586 and 686 > might treat the PCI devices any difference?? I know it sounds like I'm > grasping at straws here, but I really want to get these USB ports working. I > copied 60gig the other days on the USB 1.1 ports and it took 25 hours!!! > Here's hoping we can get to the bottom of this. > > -----Original Message----- > From: dev...@li... > [mailto:dev...@li...] On Behalf Of > Bruce Smith > Sent: 29 August 2008 18:56 > To: dev...@li... > Subject: Re: [Devil-Linux-discuss] Devil-Linux with a PCI USB card > >> what is the differences between the 586 and the 686 builds? > > It is the CPU option selected when the entire distro is compiled. > > You can run a i586 compiled distro on a 586 (Pentium/P5), or above > (PPro, P-II, P-III, P-4, etc.) > > You cannot run a i686 compiled distro on a 586, or other CPU's that > doesn't support the i686 instruction set. (PPro and above should be > fine) > > Some older VIA/AMD CPU's have problems with the i686 distro. I don't > recall the specific models. > > - BS |
|
From: Chris G. <dj_...@ti...> - 2008-08-29 19:11:52
|
Ok cool, So is there any chance that the different versions 586 and 686 might treat the PCI devices any difference?? I know it sounds like I'm grasping at straws here, but I really want to get these USB ports working. I copied 60gig the other days on the USB 1.1 ports and it took 25 hours!!! Here's hoping we can get to the bottom of this. -----Original Message----- From: dev...@li... [mailto:dev...@li...] On Behalf Of Bruce Smith Sent: 29 August 2008 18:56 To: dev...@li... Subject: Re: [Devil-Linux-discuss] Devil-Linux with a PCI USB card > what is the differences between the 586 and the 686 builds? It is the CPU option selected when the entire distro is compiled. You can run a i586 compiled distro on a 586 (Pentium/P5), or above (PPro, P-II, P-III, P-4, etc.) You cannot run a i686 compiled distro on a 586, or other CPU's that doesn't support the i686 instruction set. (PPro and above should be fine) Some older VIA/AMD CPU's have problems with the i686 distro. I don't recall the specific models. - BS ------------------------------------------------------------------------- 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 No virus found in this incoming message. Checked by AVG - http://www.avg.com Version: 8.0.138 / Virus Database: 270.6.11/1639 - Release Date: 28/08/2008 07:39 |
|
From: Dick M. <di...@fo...> - 2008-08-29 19:02:50
|
John Bridleman wrote: > 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. Is it that there are 2 problems here? You have a problem finding a driver for your CDROM? You're stuck in a logical loop because you don't have a config file? There are a few funnies with the start-up script when there is no config file. I've pointed out a few in the past but they're not showstoppers and there's more interesting things to work on. The best plan is to put a config file on the USB stick before you start. If you don't want to do that you have to tell DL where you want to put your config file otherwise you get into the loop. echo device > /shm/DL_DEVICE or save-config -d device > A friend mentioned it might be a "DL doesn't like to be booted from a > sata cdrom drive problem". DL uses a recent kernel; if there's a driver for your drive it will use it. Otherwise you're stuffed! If you're using IDE the device will be /dev/hd* or /dev/scd* - I don't know what it will be with SATA - probably /dev/scd*. dmesg will tell you what's happening. To duck the problem is it possible you could use a USB stick for the ISO image? It's only about 256MB so it's not such a big deal these days. Personally I use a USB stick with one partition for the ISO and another (ext3) for the config files. If you have enough RAM you can use "copy ISO to ram" which allows you to remove the USB stick once you've booted. Dick |
|
From: Brian N. <br...@fu...> - 2008-08-29 18:34:17
|
Agreed. I did look at the save-config script and noticed that it was a
"tar -d" that was giving the difference output.
You could augment the save-config script to compensate and print all of
the files that will get tar'd from the etc-mods directory that are not
in the current tar file.
This is not bullet proof and there might be a better way of doing this,
but...:
cd /shm
# list differences in existing files
tar -djf $CONFIG_MOUNT/$DL_CONFIG_FILE etc-mods
# list new files to be added to the tarball
for file in `find etc-mods -type f`
do
tar -tjf $CONFIG_MOUNT/$DL_CONFIG_FILE | grep $file > /dev/null
if [ $? -ne 0 ]; then
echo $file: First save
fi
done
-----Original Message-----
From: dev...@li...
[mailto:dev...@li...] On Behalf Of
Bruce Smith
Sent: Friday, August 29, 2008 1:14 PM
To: dev...@li...
Subject: Re: [Devil-Linux-discuss] DL 1.3.6-2008-08-28-i686 save-config
showfile differences
> Been using DL 1.2.x for a few years now... and making the move to
1.3.6.
>
> I like the new save-config system only saving the files that changed,
vs the
> whole /etc directory.
Yes, that is nice, if I do say so myself. :-)
> Just something I have noticed when performing a save-config while its
> listing the differences. If the file does not exist yet in the
tarball (ie.
> It's the first edit to a file) it doesn't show up in the listing
differences
> but it does in fact get saved. Then when a 2nd edit is done and a
> save-config gets executed it does show up in the file differences
> (time/size).
>
> It would be nice to see "new file" or "first save" when a new file is
being
> added to the tarball for a little insurance J
You'll probably have to make that request to the maintainer of the
"tar" command. What you're seeing is the output of the tar "-d"
option.
- BS
------------------------------------------------------------------------
-
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: Bruce S. <bw...@re...> - 2008-08-29 17:55:55
|
> what is the differences between the 586 and the 686 builds? It is the CPU option selected when the entire distro is compiled. You can run a i586 compiled distro on a 586 (Pentium/P5), or above (PPro, P-II, P-III, P-4, etc.) You cannot run a i686 compiled distro on a 586, or other CPU's that doesn't support the i686 instruction set. (PPro and above should be fine) Some older VIA/AMD CPU's have problems with the i686 distro. I don't recall the specific models. - BS |
|
From: Chris G. <dj_...@ti...> - 2008-08-29 17:32:24
|
Hi. I've still got my problem with the USB ports on my PCI card not working, but I have another question. It's probably a bit of a silly question, but what is the differences between the 586 and the 686 builds? From: dev...@li... [mailto:dev...@li...] On Behalf Of Chris Grove Sent: 12 August 2008 18:45 To: dev...@li... Subject: Re: [Devil-Linux-discuss] Devil-Linux with a PCI USB card 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 No virus found in this incoming message. Checked by AVG - http://www.avg.com Version: 8.0.138 / Virus Database: 270.6.1/1605 - Release Date: 11/08/2008 16:59 |
|
From: John B. <jbr...@gm...> - 2008-08-29 17:19:36
|
Thanks for your help... BIOS settings SATA mode = RAID and in the RAID settings I don't have the drives mirrored. I get the "Shall I copy the default ....." and press y (and only get a singe y) Then I get the "Would you like to probe...." which I answer y. Probing all SCSI modules ... Then I get a long list of modules found (about 4 1/2 lines) then I get Searching for Devil-Linux CD-ROM Search list: checking /dev/sda1 ... wrong media !!! Devil-Linux CD-ROM not found !!! Cannot find CD drive - try probing for SCSI controllers Wold you really like to load DL without Configuration Media? (y/n) One thing I've noticed is that with the SATA BIOS setting at RAID the boot menu lists the CD-ROM drive as P4-HL-DT-STDVD-ROM and with it set to IDE it lists it as CDROM. Clue? On Thu, Aug 28, 2008 at 5:48 PM, Serge Leschinsky <fi...@in...>wrote: > 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... > -- John Bridleman |
|
From: Bruce S. <bw...@re...> - 2008-08-29 17:14:03
|
> Been using DL 1.2.x for a few years now… and making the move to 1.3.6. > > I like the new save-config system only saving the files that changed, vs the > whole /etc directory. Yes, that is nice, if I do say so myself. :-) > Just something I have noticed when performing a save-config while its > listing the differences. If the file does not exist yet in the tarball (ie. > It's the first edit to a file) it doesn't show up in the listing differences > but it does in fact get saved. Then when a 2nd edit is done and a > save-config gets executed it does show up in the file differences > (time/size). > > It would be nice to see "new file" or "first save" when a new file is being > added to the tarball for a little insurance J You'll probably have to make that request to the maintainer of the "tar" command. What you're seeing is the output of the tar "-d" option. - BS |
|
From: Brian N. <br...@fu...> - 2008-08-29 15:59:49
|
Been using DL 1.2.x for a few years now... and making the move to 1.3.6. I like the new save-config system only saving the files that changed, vs the whole /etc directory. Just something I have noticed when performing a save-config while its listing the differences. If the file does not exist yet in the tarball (ie. It's the first edit to a file) it doesn't show up in the listing differences but it does in fact get saved. Then when a 2nd edit is done and a save-config gets executed it does show up in the file differences (time/size). It would be nice to see "new file" or "first save" when a new file is being added to the tarball for a little insurance J |
|
From: Heiko Z. <he...@zu...> - 2008-08-29 13:32:57
|
> -----Original Message----- > From: dev...@li... [mailto:devil- > lin...@li...] On Behalf Of Bruce Smith > Sent: Friday, August 29, 2008 8:28 AM > To: dev...@li... > Subject: Re: [Devil-Linux-discuss] DL 1.3.6-2008-08-28-i686 Error > message on save-config > > > 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. > > Yes, it's always a good idea to make a copy of the config for backup > purposes. > > > 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? > > I haven't done much with the install-on-usb script for a long, so I'm > probably not the best one to answer that question. > > Personally I really like the "RUNFROMRAM=y" option. (It takes an > extra quarter GB of memory, but memory is cheap) That way the entire > CD is read into RAM upon initial bootup and then the system runs from > memory. It takes longer to boot, but after that, the system is FAST > because it never has to go back to read the CD. > There may be a problem with the latest 1.3.x and running from a media other then CD. I tried upgrading my Firewall last weekend and it blew up (found the ISO but couldn't use it for some strange reason). I had not have any time to investigate it. Heiko |
|
From: Bruce S. <bw...@re...> - 2008-08-29 13:28:12
|
> 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. Yes, it's always a good idea to make a copy of the config for backup purposes. > 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? I haven't done much with the install-on-usb script for a long, so I'm probably not the best one to answer that question. Personally I really like the "RUNFROMRAM=y" option. (It takes an extra quarter GB of memory, but memory is cheap) That way the entire CD is read into RAM upon initial bootup and then the system runs from memory. It takes longer to boot, but after that, the system is FAST because it never has to go back to read the CD. - BS |
50 messages has been excluded from this view by a project administrator.
