Re: Re: installing woody 3.0r2 on HP Proliant DL140
I had the same problem using Slackware 10.1. I'm not sure what the problem is, but upgrading the BIOS to the latest and greatest didn't help. The only fix I found is to use GRUB. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Installing Woody and LARGE download of UNCHOOSEN packages
I have installed Debian Woody 3.0r5 from Netinstall CD disk. After installation has succesfuly finished I have made apt-get update and apt-get upgrade (even if it would'nt be necessary). Then I have open dselect and found MC package - chose it nad exit. Then I have selected Install and be surprised - beside MC there was a LARGE amount of packages which I have not chosen. There was aprox. 100 MB to download. Was it something wrong during Debian config? I have to mention that I have not say YES when asked Run TaskSel nor DSelect during Debian Config. Where did I failed? THNX Seba -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Installing Woody and LARGE download of UNCHOOSEN packages
Sebastijan Plut wrote: Was it something wrong during Debian config? I have to mention that I have not say YES when asked Run TaskSel nor DSelect during Debian Config. Where did I failed? I believe this is a well known and much hated side-effect of opening dselect - a default package selection list. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Installing woody 3.0r5 on HP Proliant DL140
Hi, after Debian 3.0r5 installation on HP Proliant DL140 the system is rebooted and I get this message LILO 22.2 Loading Linux... but the system hangs. If anyone has successfully installed this version on same server type and have some tips, I'd greatly appreciate it. Nicola Guarracino Dipartimento di Fisica Universita' della Calabria - Cosenza Italy -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Installing woody 3.0r5 on HP Proliant DL140
Looks like you don't have correct kernel for this server. If you do not find kernel allready compiled for this server, you will have to configure and compile kernel yourself. Dexter2 On Sun, 2005-05-22 at 09:08 +, Nicola Guarracino - Dip. Fisica UniCal +39 984 496030 wrote: Hi, after Debian 3.0r5 installation on HP Proliant DL140 the system is rebooted and I get this message LILO 22.2 Loading Linux... but the system hangs. If anyone has successfully installed this version on same server type and have some tips, I'd greatly appreciate it. Nicola Guarracino Dipartimento di Fisica Universita' della Calabria - Cosenza Italy -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
installing woody 3.0r2 on HP Proliant DL140
Hi, I download woody 3.0r2 (created CD) for i386 processor since server is running on Xeon chip (is this correct?) After installation is completed and system is rebooted, I only get the following msg: "LILO 2.22 Loading linux." and the system hangs. Is anyone experiencing this as well. If anyone has successfully installed this version on same server type (HP Proliant DL140) and have some tips, I'd greatly appreciate it. Hung Do you Yahoo!? The all-new My Yahoo! What will yours do?
Re: installing woody 3.0r2 on HP Proliant DL140
On Sun, 2004-12-05 at 00:38 -0800, HXD wrote: Hi, I download woody 3.0r2 (created CD) for i386 processor since server is running on Xeon chip (is this correct?) After installation is completed and system is rebooted, I only get the following msg: LILO 2.22 Loading linux. and the system hangs. Is anyone experiencing this as well. If anyone has successfully installed this version on same server type (HP Proliant DL140) and have some tips, I'd greatly appreciate it. Not knowing the peculiarities of the DL140, the standard answer here is, Use Sarge. It's much more advanced than Woody, seeing as how Woody is 2+ years old. Yes, it's not released yet, but it's close enough. -- - Ron Johnson, Jr. Jefferson, LA USA PGP Key ID 8834C06B I prefer encrypted mail. A great many open minds should be closed for repairs. Toledo Blade Newspaper signature.asc Description: This is a digitally signed message part
Installing Woody with USB keyboard and mouse.
On Thu, Nov 11, 2004 at 03:27:37AM +, [EMAIL PROTECTED] wrote: How do install Debian "Woody" with a USB keyboard and mouse? I only have usb ports. When I try it says "Keyboard not recognized". I want use Debian badly. I hate using Suse 9.1You'll probably have much better luck trying to install Sarge. Trythe "netinst CD image, with Debian base" from this page:http://www.debian.org/devel/debian-installer/Jason Thanks, that fixed the problem.
Installing Woody with USB keyboard and mouse.
How do install Debian Woody with a USB keyboard and mouse? I only have usb ports. When I try it says Keyboard not recognized. I want use Debian badly. I hate using Suse 9.1 I googled this problem and I could not find a solution. Thanks. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Installing Woody with USB keyboard and mouse.
On Thu, Nov 11, 2004 at 03:27:37AM +, [EMAIL PROTECTED] wrote: How do install Debian Woody with a USB keyboard and mouse? I only have usb ports. When I try it says Keyboard not recognized. I want use Debian badly. I hate using Suse 9.1 You'll probably have much better luck trying to install Sarge. Try the netinst CD image, with Debian base from this page: http://www.debian.org/devel/debian-installer/ Jason -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Can't get PCMCIA card going when installing Woody
Using the standard boot floppies (rescue, root, four driver disks) on an old P150 laptop with no CD drive. Get to 'Configure a network', and it correctly asks me if my network card is PCMCIA. However, if I then ask for it to auto-configure, it fails. Same for manually configured - I get a message saying I'm configured but not activated. Open up another console, find that it's complaining about missing file /var/lib/misc/pcmcia-scheme. I manually create this (zero length, as is on another Debian box I have) and it seems to get further. Now I get a large number of DHCPDISCOVER messages in /var/log/messages, but they end in failure. Configure manually (configuration kown to be valid) - nope. Sounds like the card is working because it beeps correctly, but there's still no network at the end of it. In /var/log/messages I get daemon.info.cardmgr: executing: 'modprobe serial_cs' daemon.info.cardmgr: exuting: './serial start ttyS1' daemon.info.cardmgr: socket 1: 3Com 572/574 Fasst Ethernet daemon.info.cardmgr: exeucting: 'modprobe 3c574_cs' daemon.info.cardmgr: executing: './network start eth0' (At which point I get the beeps). I'm a bit snookered here. Can't install the base without the network - any clues? Cheers, Ian -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Need help installing Woody
On Sat, 29 May 2004 23:30:11 +0200, Wolfgang Zocher wrote: Any hints to possible snares are welcome! Is it correct, what you ask is: 'Can I share the swap for both installs (distros) ? In case this is the question, the unambiguous answer is 'yes'. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Need help installing Woody
Hi friends, the HDD of a running system is structured as follows: hda1primary win95 Fat325GBBootable hda5logical Linux ext2 xxx hda6logical Linux swap yyy hda7logical Linux ReiserFS zzz Now, I want to install Debian Woody on hda1 sharing the same swap on hda6. Is this possible without any problems? btw. hda5,6,7 builds a SuSE Linux system, which, if Woody is running on this machine as stable as on my Laptop, should be replaced by Woody stable while the system on hda1 will be my testing system. Any hints to possible snares are welcome! Wolfgang -- Wolfgang Zocher http://www.wolfgang-zocher.privat.t-online.de/ Registered Linux User #337888 using Debian GNU/Linux 97.025% of statistics are wrong -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Problems installing woody
Hello list, i've put several hours, if not days into this attempt to install woody and i am at my wits end now. If you can , please help. As i cant follow the list, please cc: this address in any reply. I have bought an IBM x205 server and additionally ordered a ServeRaid 4lx raid controller as recommended by the hardware distributor (returning the items is not an option; they offered to install linux (redhat) and i refused; turns out redhat and suse support all devices that cause me trouble now). I have a problem now with getting the raid controller to work, as well as the Gigabit ethernet card that is onBoard (e1000). It seems as if there used to be an extended driver set on a boot floppy provided by blade at on http://people.debian.org/~blade/install/preload/ however when i go there, it tells me that the drivers are possibly (and most likely) have been corruped during the hacking of the debian server, and that the maintainer of that inofficial package has no interest in keeping it up to date. I can only open the archive after typing in a password saying Yes i want to screw my system with hacked code! or such. Naturally i prefer not to use them. Next i got myself the original kernel sources and headers for the bf24 kernel and built the module for the controller (ips.o) on another debian system. Put it on a floppy (into the /boot directory of course) and then tried to Add additional drivers from floppy when booting from the woody disk 1 (of course with kernel bf24). When i tell the dialog to insert that module, it will hang forever. If, instead , i open a terminal, manually mount the floppy, copy the module into the right place (/lib/modules/2.4something/kernel/drivers/scsi) and then do an insmod, it tells me the module is not built for that kernel. If finally i do a insmod -f ( that is what the dialog is doing, too) it tells me that the kernel is being tained, and it hangs forever. At other occasions, i saw that while the dialog is hanging, lsmod reports the module as being loaded (and initializing). I hope i am missing the right way to install woody on that system. Can anyone point me to some document that could help me with the installation? By the way googling pointed me to a dubious boot-floppies package all the time. On my other system i have repeatedly tried to apt-get or apt-cache search for that package without success. Would that solve my problems? Where could i get it? TIA, Daniel Mit schönen Grüßen von Yahoo! Mail - http://mail.yahoo.de -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
UPDATE: Problems installing woody
Out of curiosity i tried blade's boot floppy just to see wether the module would load cleanly (unlike the one i built). It indeed does. Boiling my problem down to: how did he make those modules? I really dont want to use the modules on the floppy as he himself says they could easily be compromised and this system i am working on is obviously a bit sensitive (hence the raid controller). Any hints on how to make a module that will actually load, or why my module just hangs? TIA, Daniel Mit schönen Grüßen von Yahoo! Mail - http://mail.yahoo.de -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: frustrating problem with networking encountered while installing Woody
On Mon, Mar 22, 2004 at 11:44:03AM -0800, Renhao Zhang wrote: --- Darik Horn [EMAIL PROTECTED] wrote: In addition to Windows, KNOPPIX networks just fine with no problems. If your computer runs Windows 98 and Knoppix properly, then your Debian installation isn't loading drivers for all of your hardware. This seemed to be the most likely culprit, but I couldn't rule out the possiblity that the problem is with the DHCP setup. Is there anything I can try to make sure? Package 'dhcping' allows you to test responses of a DHCP server. Never used it though. If ifconfig -a doesn't show your network card(eth0) the drivers aren't loaded. Find the module name and add to the end of /etc/modules. One thing that I don't think has been mentioned is that you could boot windows, get an IP and use it statically in Debian. There is of course a chance of an IP addres conflict. For testing its safe though. Brian Brian -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: networking problem encountered while installing Woody
Aurélien, Thank you for your prompt and insightful reply. I'll get a move on learning to compiling my own kernel. Hopefully, that'll get the networking functioning. In the mean time, I'd still like to learn exactly how my setup isn't working and what I am fixing. The following is the info you asked for: ifconfig eth0 Link encap:Ethernet HWaddr 00:A0:CC:D7:51:A4 UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 RX packets:0 errors:0 dropped:0 overruns:0 frame:0 TX packets:65 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:100 RX bytes:0 (0.0 b) TX bytes:22230 (21.7 KiB) Interrupt:12 Base address:0x6c00 loLink encap:Local Loopback inet addr:127.0.0.1 Mask:255.0.0.0 UP LOOPBACK RUNNING MTU:3924 Metric:1 RX packets:16 errors:0 dropped:0 overruns:0 frame:0 TX packets:16 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:0 RX bytes:1056 (1.0 KiB) TX bytes:1056 (1.0 KiB) --- lspci -v 00:00.0 Host bridge: Intel Corp. 430TX - 82439TX MTXC (rev 01) Flags: bus master, medium devsel, latency 64 00:07.0 ISA bridge: Intel Corp. 82371AB PIIX4 ISA (rev 01) Flags: bus master, medium devsel, latency 0 00:07.1 IDE interface: Intel Corp. 82371AB PIIX4 IDE (rev 01) (prog-if 80 [Master]) Flags: bus master, medium devsel, latency 64 I/O ports at f000 00:07.2 USB Controller: Intel Corp. 82371AB PIIX4 USB (rev 01) (prog-if 00 [UHCI]) Flags: bus master, medium devsel, latency 64, IRQ 11 I/O ports at 6400 00:07.3 Bridge: Intel Corp. 82371AB PIIX4 ACPI (rev 01) Flags: medium devsel 00:09.0 VGA compatible controller: 3Dfx Interactive, Inc. Voodoo Banshee (rev 03) (prog-if 00 [VGA]) Subsystem: Diamond Multimedia Systems Monster Fusion Flags: fast devsel, IRQ 10 Memory at e000 (32-bit, non-prefetchable) Memory at e200 (32-bit, prefetchable) I/O ports at 6800 Capabilities: [60] Power Management version 1 00:0b.0 Ethernet controller: Lite-On Communications Inc LNE100TX (rev 20) Subsystem: Netgear FA310TX Flags: bus master, medium devsel, latency 64, IRQ 12 I/O ports at 6c00 Memory at e400 (32-bit, non-prefetchable) --- Additionally, here is the content of my /etc/network/interfaces: --- # /etc/network/interfaces -- configuration file for ifup(8), ifdown(8) # The loopback interface auto lo iface lo inet loopback # The first network card - this entry was created during the Debian installation # (network, broadcast and gateway are optional) auto eth0 iface eth0 inet dhcp --- I know the following from the system console indicates that I have the DHCP client running in some form. I just don't know the meaning or cause of the behavior: --- Mar 21 21:59:22 debian dhclient-2.2.x: DHCPDISCOVER on eth0 to 255.255.255.255 port 67 interval 5 Mar 21 21:59:27 debian dhclient-2.2.x: DHCPDISCOVER on eth0 to 255.255.255.255 port 67 interval 6 Mar 21 21:59:33 debian dhclient-2.2.x: DHCPDISCOVER on eth0 to 255.255.255.255 port 67 interval 13 Mar 21 21:59:46 debian dhclient-2.2.x: DHCPDISCOVER on eth0 to 255.255.255.255 port 67 interval 14 Mar 21 22:00:00 debian dhclient-2.2.x: DHCPDISCOVER on eth0 to 255.255.255.255 port 67 interval 21 Mar 21 22:00:21 debian dhclient-2.2.x: DHCPDISCOVER on eth0 to 255.255.255.255 port 67 interval 2 Mar 21 22:00:23 debian dhclient-2.2.x: No DHCPOFFERS received. Mar 21 22:00:23 debian dhclient-2.2.x: No working leases in persistent database. Mar 21 22:00:24 debian dhclient-2.2.x: Sleeping. --- Whatever is the matter, Eth0 seems to at least be healthy. Is there something else I'm not seeing? Any insights are apreciated. Thanks again. -Ren --- Aurélien_Campéas [EMAIL PROTECTED] wrote: First, you should tell us the output of `ifconfig' and `lspci -v'. Then... I've observed that sometimes, debian pre-made ultra-modularized kernels don't work wrt networking. It's because of some stupid IRQ conflict. The only solution I found in those cases is to make your own kernel with network drivers compiled in (NOT modular). Then it works, presumably because the drivers check the hardware early enough and get over the (potential) conflict. Hope that helps. Le sam 20/03/2004 à 02:31, Renhao Zhang a écrit : I'm trying to dual boot an old Pentium box with Debian Woody and win98. The few bugs I've encountered are falling one by one as I work on the new installation. However, one persistant mystery has remained stuborn. Here is the problem: booting from Windows, I can get onto my home LAN and reach the internet just fine with a dial-up gateway (the Actiontec dual pc modem) as the DHCP server. But if the Linux partition boots, the network vanishes. It pauses for an unusually long time at configuring network
Re: frustrating problem with networking encountered while installing Woody
In addition to Windows, KNOPPIX networks just fine with no problems. If your computer runs Windows 98 and Knoppix properly, then your Debian installation isn't loading drivers for all of your hardware. First, install a recent kernel: # apt-get install kernel-image-2.4.18-386 Second, install the discover package: # apt-get install discover The discover package will autodetect the devices in your computer and load appropriate drivers when the system starts. Past that, you can install Knoppix to your hard disk with this command: # knx-hdinstall Knoppix is a derivative of Debian that is a good alternative of the official Debian distribution for casual users. You can upgrade the current version of Knoppix to Debian/sarge after your computer is working properly. Renhao Zhang wrote: I'm trying to dual boot an old Pentium box with Debian Woody and win98. The few bugs I've encountered are falling one by one as I work on the new installation. However, one persistant mystery has remained stuborn. Here is the problem: booting from Windows, I can get onto my home LAN and reach the internet just fine with a dial-up gateway (the Actiontec dual pc modem) as the DHCP server. But if the Linux partition boots, the network vanishes. It pauses for an unusually long time at configuring network interfaces.. By all indications, networking on the box is functional: there are no hardware related error messages during boot or in the kernel logs. loop-back is fine when I ping 127.0.0.1, but no other IPs are reachable. conversely, the box can't be pinged by any other machines on the network either. Flashing LEDs on my 8 port switch seems to indicate there is a signal present, but nothing is getting through in either direction when Woody is running. The NIC is a netgear FA 310TX for which I'm using the tulip driver. In addition to Windows, KNOPPIX networks just fine with no problems. An experienced collegue suggested that there might be a IRQ conflict with another device. Debian boot lists the NIC as using IRQ 12. In windows, the diagnostic tool AIDA32 returned the following: IRQ0Cshared NETGEAR FA310TX fast ethernet PCI adapter IRQ0Cshared IRQ Holder for PCI Steering First of all, what is PCI steering? Is there a way to uncouple the two so they use different IRQs? My own suspicion is that an old USR Sportster ISA winmodem might have something to do with it. The thing is useless with Linux but I don't want to trash it because it still works well under Win98. I think it is worth keeping for those rare emergencies. does anyone know if an IRQ would be assigned by Linux to hardware it doesn't recognize? The last time I handled Linux was when Redhat 5.2 was new. Back then I don't remember having much hardware headaches. At the end of my ropes, I even tried a few days ago to explicitly declare an IP, hoping the DHCP server might back down and just let the damn NIC talk to somebody-anybody. After some googling, I found one other account of almost the same problem: http://www.linuxquestions.org/questions/showthread.php?threadid=110910 the only difference is the router being used. The guy who started the thread never said if his problem was solved. I've tried everything suggested to him to no avail. Everthing that is, except the last one, which I didn't quite understand. I quote the following: I have the exact same network card that you do, and have had the same problem. I have never been able to do a net install with dhcp using the bf2.4 kernel. So what I do is just install the base system with the vanilla kernel. Then just apt-get the 2.4.18 kernel source and compile it with the tulip driver and MAKE SURE you also have packet filtering and socket filtering enabled as well. They are under the network options. You must have those two options enabled for dhcp to work with that card. So the bf2.4 kernel probably doesn't have them enabled. I'm not sure I understand what is being said. Are you supposed to apt-get the 2.4.18 kernel with the 'Woody' iso disc set as the source? I'll try to learn how to recompile the kernel to see if that solves the problem, but I wanted to see if anyone else has encountered similar problems and suceeded in solving it. Thanks in advance for any new insight. -Ren __ Do you Yahoo!? Yahoo! Mail - More reliable, more storage, less spam http://mail.yahoo.com -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: networking problem encountered while installing Woody
Le lun 22/03/2004 à 09:22, Renhao Zhang a écrit : Aurlien, Thank you for your prompt and insightful reply. I'll get a move on learning to compiling my own kernel. Wait a minute... ! # The first network card - this entry was created during the Debian installation # (network, broadcast and gateway are optional) auto eth0 iface eth0 inet dhcp --- I know the following from the system console indicates that I have the DHCP client running in some form. I just don't know the meaning or cause of the behavior: --- Mar 21 21:59:22 debian dhclient-2.2.x: DHCPDISCOVER on eth0 to 255.255.255.255 port 67 interval 5 You have a problem with dhcp here. Are you sure you want it ? It seems like the dhcp client doesn't find a dhcp server... I mean, why not pick up some private ip adress (like 192.168.0.2) and rewrite your eth0 entry in /etc/network/interfaces as : auto eth0 iface eth0 inet static address 192.168.0.2 netmask 255.255.255.0 network 192.168.0.0 broadcast 192.168.0.255 Hasn't your windows box a fixed IP already ? If so, just take the same IP... This may be simpler than trying to fix dhcp (also I don't have any experience with it so I can't help on that)... Q: How many Martians does it take to screw in a light bulb? A: One and a half. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: networking problem encountered while installing Woody
--- Aurélien_Campéas [EMAIL PROTECTED] wrote: You have a problem with dhcp here. Are you sure you want it ? It seems like the dhcp client doesn't find a dhcp server... I mean, why not pick up some private ip adress (like 192.168.0.2) and rewrite your eth0 entry in /etc/network/interfaces as : auto eth0 iface eth0 inet static address 192.168.0.2 netmask 255.255.255.0 network 192.168.0.0 broadcast 192.168.0.255 I've already tried to do this, hoping the DHCP serving modem might accept it. it didn't work. When I referenced the bullitin board I found with another case of the same situation, your suggestion of recompiling the kernel with networking built in was also mentioned. Since it was the only thing I have yet to try, I figured it was worth a shot. Hasn't your windows box a fixed IP already ? If so, just take the same IP... no...the windows is a DHCP client as well... This may be simpler than trying to fix dhcp (also I don't have any experience with it so I can't help on that)... Regardless, I appreciate your insights. Feel free to suggest anything that I might look into. Q: How many Martians does it take to screw in a light bulb? A: One and a half. Q: Are they running Woody, Sarge, or Sid? __ Do you Yahoo!? Yahoo! Finance Tax Center - File online. File on time. http://taxes.yahoo.com/filing.html -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: frustrating problem with networking encountered while installing Woody
--- Darik Horn [EMAIL PROTECTED] wrote: In addition to Windows, KNOPPIX networks just fine with no problems. If your computer runs Windows 98 and Knoppix properly, then your Debian installation isn't loading drivers for all of your hardware. This seemed to be the most likely culprit, but I couldn't rule out the possiblity that the problem is with the DHCP setup. Is there anything I can try to make sure? First, install a recent kernel: # apt-get install kernel-image-2.4.18-386 Second, install the discover package: # apt-get install discover The discover package will autodetect the devices in your computer and load appropriate drivers when the system starts. Past that, you can install Knoppix to your hard disk with this command: # knx-hdinstall Knoppix is a derivative of Debian that is a good alternative of the official Debian distribution for casual users. You can upgrade the current version of Knoppix to Debian/sarge after your computer is working properly. I love Knoppix, but it is a bit bloated for the Pentium 200. I used it for testing purposes to determine that networking can work properly, but I loath to use it regularly. If the discover package is what allowed Knoppix to handle networking so effortlessly, then I'm a happy camper. Thanks for your help Darik. -Ren Renhao Zhang wrote: I'm trying to dual boot an old Pentium box with Debian Woody and win98. The few bugs I've encountered are falling one by one as I work on the new installation. However, one persistant mystery has remained stuborn. Here is the problem: booting from Windows, I can get onto my home LAN and reach the internet just fine with a dial-up gateway (the Actiontec dual pc modem) as the DHCP server. But if the Linux partition boots, the network vanishes. It pauses for an unusually long time at configuring network interfaces.. By all indications, networking on the box is functional: there are no hardware related error messages during boot or in the kernel logs. loop-back is fine when I ping 127.0.0.1, but no other IPs are reachable. conversely, the box can't be pinged by any other machines on the network either. Flashing LEDs on my 8 port switch seems to indicate there is a signal present, but nothing is getting through in either direction when Woody is running. The NIC is a netgear FA 310TX for which I'm using the tulip driver. In addition to Windows, KNOPPIX networks just fine with no problems. An experienced collegue suggested that there might be a IRQ conflict with another device. Debian boot lists the NIC as using IRQ 12. In windows, the diagnostic tool AIDA32 returned the following: IRQ0Cshared NETGEAR FA310TX fast ethernet PCI adapter IRQ0Cshared IRQ Holder for PCI Steering First of all, what is PCI steering? Is there a way to uncouple the two so they use different IRQs? My own suspicion is that an old USR Sportster ISA winmodem might have something to do with it. The thing is useless with Linux but I don't want to trash it because it still works well under Win98. I think it is worth keeping for those rare emergencies. does anyone know if an IRQ would be assigned by Linux to hardware it doesn't recognize? The last time I handled Linux was when Redhat 5.2 was new. Back then I don't remember having much hardware headaches. At the end of my ropes, I even tried a few days ago to explicitly declare an IP, hoping the DHCP server might back down and just let the damn NIC talk to somebody-anybody. After some googling, I found one other account of almost the same problem: http://www.linuxquestions.org/questions/showthread.php?threadid=110910 the only difference is the router being used. The guy who started the thread never said if his problem was solved. I've tried everything suggested to him to no avail. Everthing that is, except the last one, which I didn't quite understand. I quote the following: I have the exact same network card that you do, and have had the same problem. I have never been able to do a net install with dhcp using the bf2.4 kernel. So what I do is just install the base system with the vanilla kernel. Then just apt-get the 2.4.18 kernel source and compile it with the tulip driver and MAKE SURE you also have packet filtering and socket filtering enabled as well. They are under the network options. You must have those two options enabled for dhcp to work with that card. So the bf2.4 kernel probably doesn't have them enabled. I'm not sure I understand what is being said. Are you supposed to apt-get the 2.4.18 kernel with the 'Woody' iso disc set as the source? I'll try to learn how to recompile the kernel to see if that solves the problem, but I wanted to see if anyone else has encountered similar problems and suceeded in solving it.
Re: frustrating problem with networking encountered while installing Woody
On Fri, Mar 19, 2004 at 05:31:42PM -0800, Renhao Zhang wrote: I have the exact same network card that you do, and have had the same problem. I have never been able to do a net install with dhcp using the bf2.4 kernel. So what I do is just install the base system with the vanilla kernel. Then just apt-get the 2.4.18 kernel source and compile it with the tulip driver and MAKE SURE you also have packet filtering and socket filtering enabled as well. They are under the network options. You must have those two options enabled for dhcp to work with that card. So the bf2.4 kernel probably doesn't have them enabled. I'm not sure I understand what is being said. Are you supposed to apt-get the 2.4.18 kernel with the 'Woody' iso disc set as the source? I'll try to learn how to recompile the kernel to see if that solves the problem, but I wanted to see if anyone else has encountered similar problems and suceeded in solving it. While I haven't solved my own problems with tulip(only work at 100Mbps) the instructions above translate to: Get linux.2.x.y.tar.bz2. One method is from kernel.org (as is sugested above - a vanilla kernel). Another is from your Woody disks to do 'apt-get install kernel-source 2.4.18'. I'd advise against this due to a) being old b) having at least 3 local root expliots. Once you've got it do the following: cd /usr/src tar -xjf linux.2.x.y.tar.bz2 (might be a different name) cd linux.2.x.y make menuconfig (needs libncurses5-dev - other options are oldconfig, config and xconfig. Menuconfig is just my favorite. This is where NET_FILTER etc. must be enabled) make dep bzImage modules modules_install install Then modify /etc/lilo.conf to ensure it points to the correct kernel you just installed in /boot and run 'lilo' Reboot and pray. I'd suggest getting everything working with static IPs first. Some handy commands for networking trouble: mii-tool, ethtool, ifconfig -a, route -n, arp Brian -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
frustrating problem with networking encountered while installing Woody
I'm trying to dual boot an old Pentium box with Debian Woody and win98. The few bugs I've encountered are falling one by one as I work on the new installation. However, one persistant mystery has remained stuborn. Here is the problem: booting from Windows, I can get onto my home LAN and reach the internet just fine with a dial-up gateway (the Actiontec dual pc modem) as the DHCP server. But if the Linux partition boots, the network vanishes. It pauses for an unusually long time at configuring network interfaces.. By all indications, networking on the box is functional: there are no hardware related error messages during boot or in the kernel logs. loop-back is fine when I ping 127.0.0.1, but no other IPs are reachable. conversely, the box can't be pinged by any other machines on the network either. Flashing LEDs on my 8 port switch seems to indicate there is a signal present, but nothing is getting through in either direction when Woody is running. The NIC is a netgear FA 310TX for which I'm using the tulip driver. In addition to Windows, KNOPPIX networks just fine with no problems. An experienced collegue suggested that there might be a IRQ conflict with another device. Debian boot lists the NIC as using IRQ 12. In windows, the diagnostic tool AIDA32 returned the following: IRQ0Cshared NETGEAR FA310TX fast ethernet PCI adapter IRQ0Cshared IRQ Holder for PCI Steering First of all, what is PCI steering? Is there a way to uncouple the two so they use different IRQs? My own suspicion is that an old USR Sportster ISA winmodem might have something to do with it. The thing is useless with Linux but I don't want to trash it because it still works well under Win98. I think it is worth keeping for those rare emergencies. does anyone know if an IRQ would be assigned by Linux to hardware it doesn't recognize? The last time I handled Linux was when Redhat 5.2 was new. Back then I don't remember having much hardware headaches. At the end of my ropes, I even tried a few days ago to explicitly declare an IP, hoping the DHCP server might back down and just let the damn NIC talk to somebody-anybody. After some googling, I found one other account of almost the same problem: http://www.linuxquestions.org/questions/showthread.php?threadid=110910 the only difference is the router being used. The guy who started the thread never said if his problem was solved. I've tried everything suggested to him to no avail. Everthing that is, except the last one, which I didn't quite understand. I quote the following: I have the exact same network card that you do, and have had the same problem. I have never been able to do a net install with dhcp using the bf2.4 kernel. So what I do is just install the base system with the vanilla kernel. Then just apt-get the 2.4.18 kernel source and compile it with the tulip driver and MAKE SURE you also have packet filtering and socket filtering enabled as well. They are under the network options. You must have those two options enabled for dhcp to work with that card. So the bf2.4 kernel probably doesn't have them enabled. I'm not sure I understand what is being said. Are you supposed to apt-get the 2.4.18 kernel with the 'Woody' iso disc set as the source? I'll try to learn how to recompile the kernel to see if that solves the problem, but I wanted to see if anyone else has encountered similar problems and suceeded in solving it. Thanks in advance for any new insight. -Ren __ Do you Yahoo!? Yahoo! Mail - More reliable, more storage, less spam http://mail.yahoo.com -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
installing woody using siig ultra ata/133 pci card
Hi all, I'm trying to install woody (3.0r1) from CD's on a PC with an AMD K6 II 500mhz and a brand new Seagate 80GB Barracuda Ultra ata/100 and a brand new SIIG ultra ata/133 pci controller. in addition to the new Seagate, the pc has an IO Magic CD-ROM and an LG CD-RW. Prior to buying the new Seagate and the new SIIG controller the pc ran fine with a 2GB Western Digital connected to the on board IDE. First I tested the the SIIG controller by connecting the old western digital to it's primary channel and connected the cd-rom and cd-re to it's secondary channel. I disabled the onboard ide in the BIOS. I booted. The SIIG sucessfully detected all drives and linux booted. Every worked. Then I took out the western digital and installed the new Seagate to the SIIG primary channel. I was hoping the SIIG was smart enough to boot from cd but it didn't. The SIGG detected all drives but wouldn't boot the cd. Now here's where I start my trial and error. I'm not sure what is the best configuration to use at this point. I removed the cd-rom and cd-rw from the SIIG and attached them back to the secondary onboard ide and re-enabled it in the BIOS. SIIG detected my new Seagate, the BIOS detected both CD drives and the Debian woody cd booted but the debian installation didn't see the new Seagate. Maybe the SIIG isn't even compatible with linux? Is there a boot floppy out there that I can use to get the installation going? How can I get the debian installation to see the Seagate? Jim Did you try fdisk the first thing after you booted the CD? Hi, I booted again to the CD and went to a shell and tried fdisk and cfdisk. neither one could see the hard drive. The weird thing is that when I boot my old western digital drive I am able to fdisk the new drive and mount it. But for some reason the kernel on the boot CD can't detect it. I've tried boot floppies too but I get kernel panics. :-( Jim -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED] -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: installing woody using siig ultra ata/133 pci card
Hi all, something very interesting. I booted debian on my old western digital as primary master (on board ide) and my cd-rom as secondary master and cd-rw as secondary slave. My siig ultra ata is installed and my seagate is connected to it's primary and the drive is jumped as master. The western digital has debian testing with kernel-image-2.4.24-1-k6. Ok, Linux boots up perfect. It sees the seagate and I am able to csfdisk and mkfs. as root I mounted /dev/hde and I can use the drive. The drive works. However, nothing has allowed me to boot the install CD and install a fresh debian onto the new seagate. The install insists there are no hard disks. I don't know what to do. I want the new seagate to be my boot drive. is there another option? Jim Hi all, I'm trying to install woody (3.0r1) from CD's on a PC with an AMD K6 II 500mhz and a brand new Seagate 80GB Barracuda Ultra ata/100 and a brand new SIIG ultra ata/133 pci controller. in addition to the new Seagate, the pc has an IO Magic CD-ROM and an LG CD-RW. Prior to buying the new Seagate and the new SIIG controller the pc ran fine with a 2GB Western Digital connected to the on board IDE. First I tested the the SIIG controller by connecting the old western digital to it's primary channel and connected the cd-rom and cd-re to it's secondary channel. I disabled the onboard ide in the BIOS. I booted. The SIIG sucessfully detected all drives and linux booted. Every worked. Then I took out the western digital and installed the new Seagate to the SIIG primary channel. I was hoping the SIIG was smart enough to boot from cd but it didn't. The SIGG detected all drives but wouldn't boot the cd. Now here's where I start my trial and error. I'm not sure what is the best configuration to use at this point. I removed the cd-rom and cd-rw from the SIIG and attached them back to the secondary onboard ide and re-enabled it in the BIOS. SIIG detected my new Seagate, the BIOS detected both CD drives and the Debian woody cd booted but the debian installation didn't see the new Seagate. Maybe the SIIG isn't even compatible with linux? Is there a boot floppy out there that I can use to get the installation going? How can I get the debian installation to see the Seagate? Jim -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
installing woody using siig ultra ata/133 pci card
Hi all, I'm trying to install woody (3.0r1) from CD's on a PC with an AMD K6 II 500mhz and a brand new Seagate 80GB Barracuda Ultra ata/100 and a brand new SIIG ultra ata/133 pci controller. in addition to the new Seagate, the pc has an IO Magic CD-ROM and an LG CD-RW. Prior to buying the new Seagate and the new SIIG controller the pc ran fine with a 2GB Western Digital connected to the on board IDE. First I tested the the SIIG controller by connecting the old western digital to it's primary channel and connected the cd-rom and cd-re to it's secondary channel. I disabled the onboard ide in the BIOS. I booted. The SIIG sucessfully detected all drives and linux booted. Every worked. Then I took out the western digital and installed the new Seagate to the SIIG primary channel. I was hoping the SIIG was smart enough to boot from cd but it didn't. The SIGG detected all drives but wouldn't boot the cd. Now here's where I start my trial and error. I'm not sure what is the best configuration to use at this point. I removed the cd-rom and cd-rw from the SIIG and attached them back to the secondary onboard ide and re-enabled it in the BIOS. SIIG detected my new Seagate, the BIOS detected both CD drives and the Debian woody cd booted but the debian installation didn't see the new Seagate. Maybe the SIIG isn't even compatible with linux? Is there a boot floppy out there that I can use to get the installation going? How can I get the debian installation to see the Seagate? Jim -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: installing woody using siig ultra ata/133 pci card
On Sun, 22 Feb 2004 18:57:07 -0500, xucaen wrote: Hi all, I'm trying to install woody (3.0r1) from CD's on a PC with an AMD K6 II 500mhz and a brand new Seagate 80GB Barracuda Ultra ata/100 and a brand new SIIG ultra ata/133 pci controller. in addition to the new Seagate, the pc has an IO Magic CD-ROM and an LG CD-RW. Prior to buying the new Seagate and the new SIIG controller the pc ran fine with a 2GB Western Digital connected to the on board IDE. First I tested the the SIIG controller by connecting the old western digital to it's primary channel and connected the cd-rom and cd-re to it's secondary channel. I disabled the onboard ide in the BIOS. I booted. The SIIG sucessfully detected all drives and linux booted. Every worked. Then I took out the western digital and installed the new Seagate to the SIIG primary channel. I was hoping the SIIG was smart enough to boot from cd but it didn't. The SIGG detected all drives but wouldn't boot the cd. Now here's where I start my trial and error. I'm not sure what is the best configuration to use at this point. I removed the cd-rom and cd-rw from the SIIG and attached them back to the secondary onboard ide and re-enabled it in the BIOS. SIIG detected my new Seagate, the BIOS detected both CD drives and the Debian woody cd booted but the debian installation didn't see the new Seagate. Maybe the SIIG isn't even compatible with linux? Is there a boot floppy out there that I can use to get the installation going? How can I get the debian installation to see the Seagate? Jim Did you try fdisk the first thing after you booted the CD? -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Re: installing woody using siig ultra ata/133 pci card
Maybe the SIIG isn't even compatible with linux? Is there a boot floppy out there that I can use to get the installation going? How can I get the debian installation to see the Seagate? Jim Did you try fdisk the first thing after you booted the CD? No, the installation doesn't see the drive and says something like (paraphrasing) Since there is no hard drive you must be trying to install from a network. Please configure your network settings to continue Usually I would get a prompt to create a swap partition then a prompt to create a root filesystem. I've been reading many differing opinions about this. Some say the kernel should detect the drive, others say I need to install knoppix then do a dist-upgrade to linux. I'm confused. Should the bf2.4 image work and if not does anyone know where I can get a boot image that will work? Thanks! Jim -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
RE: trouble installing Woody w/ raid card
On Friday, February 06, 2004 2:58 PM Isaac wrote: hello everyone, hello I trying to install Debian 3 on a IBM Netfinity 5600 (8664-4RY) server. This server has a IBM serveraid card (i think it is a 4L but might be a 4P) with 4 scsi disks in raid5+spare configuration. This server is dual P3 machine (only one processor installed) with a S3 video card, ide cd-rom, and currently has windows 2000 installed. OK I normally install Debian with a bf2.4 boot cd, however when booting the cd the machine froze early in the install process. I booted the cd normally, and saw the normal kernel output, with nothing unusual. Then the screen went white and hung there before asking me any questions. I found that could switch between virtual terminals initially, however after approximately 5 seconds the machine froze completely. I checked the log messages but saw nothing wrong, the last log message was something like dbootstrap initializing. I would try a couple of things here. First, update the BIOS on the server itself. Next, upgrade the firmware for the IBM ServeRaid card. After that I downloaded the floppy images for the compact installation set. I was able to boot off of these without a freeze. My problem is that I do not have a driver for the Serveraid card so I cannot see my disk array. I thought I would use the preload essential modules option to load the driver for the raid, but I could not find a driver that was suitable. This is strange. I wonder why this didn't give you any of the problems that the full Debian CD gave you? Anyway. Please update the BIOS and the firmware for the card. The driver that you want is here: http://people.debian.org/~blade/install/preload/ You should download the file: 2_4_18-bf2_4_scsi_and_bcm5700_preload_flopy-1440_bin_gz.zip This is a disk image that you can create using dd or something like winimage (www.winimage.com) on windows. This disk will be used in the installation to specify additional drivers to load. The actual driver module you are wanting to load is the ips.o module. I use this on several IBM ServeRaid cards perfectly. I thought I would use the technique mentioned at this web page The link you gave is bad. to compile my own driver for the raid card, but then I remembered that the compact installation set uses a 2.2.x kernel, and I am unsure if the 2.2.x series has an driver. Not sure myself. But like I said. I have 4 Netfinity 5500's, 1 5000, 1 4500r, and 1 4000r. All with ServeRaid cards and all working just fine. I installed each with Woody CD's using the bootdisk at the link provided above. So, (after my lengthy ramblings,) I was wondering if anyone could shed some light on why my bootcd froze. Also I was wondering if my plan to compile the raid module is sound, or if it is wrong and or unnecessary? If it was a problem with my cdrom drive, I could use the bf2.4 set to install woody, but if I need to use a set that has a 2.2.x kernel are there even drivers for my raid card? Thanks in advance for any help. Your welcome. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
trouble installing Woody w/ raid card
hello everyone, I trying to install Debian 3 on a IBM Netfinity 5600 (8664-4RY) server. This server has a IBM serveraid card (i think it is a 4L but might be a 4P) with 4 scsi disks in raid5+spare configuration. This server is dual P3 machine (only one processor installed) with a S3 video card, ide cd-rom, and currently has windows 2000 installed. I normally install Debian with a bf2.4 boot cd, however when booting the cd the machine froze early in the install process. I booted the cd normally, and saw the normal kernel output, with nothing unusual. Then the screen went white and hung there before asking me any questions. I found that could switch between virtual terminals initially, however after approximately 5 seconds the machine froze completely. I checked the log messages but saw nothing wrong, the last log message was something like dbootstrap initializing. After that I downloaded the floppy images for the compact installation set. I was able to boot off of these without a freeze. My problem is that I do not have a driver for the Serveraid card so I cannot see my disk array. I thought I would use the preload essential modules option to load the driver for the raid, but I could not find a driver that was suitable. I thought I would use the technique mentioned at this web page http://www.inference.phy.cam.ac.uk/saw27/notes/installing_debian_woody_on_su n_v65x_v60.html to compile my own driver for the raid card, but then I remembered that the compact installation set uses a 2.2.x kernel, and I am unsure if the 2.2.x series has an driver. So, (after my lengthy ramblings,) I was wondering if anyone could shed some light on why my bootcd froze. Also I was wondering if my plan to compile the raid module is sound, or if it is wrong and or unnecessary? If it was a problem with my cdrom drive, I could use the bf2.4 set to install woody, but if I need to use a set that has a 2.2.x kernel are there even drivers for my raid card? Thanks in advance for any help. Isaac Bush -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Installing woody on IBM xSeries 342
Hi I'm trying to install woody on IBM xSeries 342 server with server raid 4lx, but the installer doesn't recognize the card. after googling for it, I found some links to disk drivers, but they aren't available anymore. I tried to compile the ips.o module on another computer (downloaded the 2.4.18 source, copied the bf24 configuration added module support for ips and compiled - renamed the version in the makefile to bf24). but when I tried to give this module on floppy to the installer it had unresolved symboles and it didn't load. does anybody have a working link to a driver disk (or can instruct me how to compile the module so it will load)? thanks -- Izi -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Installing woody on IBM xSeries 342
On Mon, 2004-02-02 at 09:24, Izi Goldenberg wrote: Hi I'm trying to install woody on IBM xSeries 342 server with server raid 4lx, but the installer doesn't recognize the card. after googling for it, I found some links to disk drivers, but they aren't available anymore. I tried to compile the ips.o module on another computer (downloaded the 2.4.18 source, copied the bf24 configuration added module support for ips and compiled - renamed the version in the makefile to bf24). but when I tried to give this module on floppy to the installer it had unresolved symboles and it didn't load. does anybody have a working link to a driver disk (or can instruct me how to compile the module so it will load)? don't compile it as a module, just compile it into the kernel. once you compile the kernel, copy it over linux.bin on an install floppy. That avoids having to load the module when installing. If you are going to put your root fs on RAID, you'll need to compile support ServeRAID in anyway. -davidc -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
RE: Installing woody on IBM xSeries 342
I'm trying to install woody on IBM xSeries 342 server with server raid 4lx, Had the same problem tracking this down myself. does anybody have a working link to a driver disk (or can instruct me how to compile the module so it will load)? This page got me started on the hunt: http://people.debian.org/~blade/install/preload/index.old.html But the disk image is not there anymore, and I don't believe it was when I tried to find it. Try this link and you will find what your are looking for: http://people.debian.org/~blade/install/preload/ You want the: 2_4_18-bf2_4_scsi_and_bcm5700_preload_flopy-1440_bin_gz.zip image. Regards, Michael -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
installing woody
Hello. I have been using Mandrake linux for about 6 months now. It has been a nice little intro into the world of linux and have learned tons. Not entirely satisfied with the RPM package management system that MDK uses and after having done some research am considering switching to Debian(my first choice by the way). Downloaded Woody in its entirety, only realizing now that the first CD was all I really needed, and after having tried to install it a few times have become frustrated that I just can't get the system to pick up my NIC. Unfortunately, I dont have a nice comp at home. I'm still using my trusty P1 166. Will eventually upgrade to something much more modern. But, in the meantime, I could certainly use some assistance with this hardware issue. The NIC in question is a Surecom EP-325-T Full duplex PCI card. My mobo has no native PCI slots and is using a PCI-to-ISA bridge adapter. I've browsed through the Debian HCL and have determined that this card is supported and assume that it has something to due with my particular hardware. The install routine just never seems to pick it up and the DHCP portion of the setup always fails. Any suggestions would be most appreciated as I look forward to using the much bragged about APT-GET. Bye for now. Thanks, Jim -- My naturally sweet nature and disposition has been spoiled by the sport of billiards. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: installing woody
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On Thursday 03 April 2003 06:12 am, jim wrote: Hello. I have been using Mandrake linux for about 6 months now. It has been a nice little intro into the world of linux and have learned tons. Not entirely satisfied with the RPM package management system that MDK uses and after having done some research am considering switching to Debian(my first choice by the way). Downloaded Woody in its entirety, only realizing now that the first CD was all I really needed, and after having tried to install it a few times have become frustrated that I just can't get the system to pick up my NIC. Unfortunately, I dont have a nice comp at home. I'm still using my trusty P1 166. Will eventually upgrade to something much more modern. But, in the meantime, I could certainly use some assistance with this hardware issue. The NIC in question is a Surecom EP-325-T Full duplex PCI card. My mobo has no native PCI slots and is using a PCI-to-ISA bridge adapter. I've browsed through the Debian HCL and have determined that this card is supported and assume that it has something to due with my particular hardware. The install routine just never seems to pick it up and the DHCP portion of the setup always fails. Any suggestions would be most appreciated as I look forward to using the much bragged about APT-GET. Bye for now. Thanks, Jim Debian does not auto detect hardware set it up. The kernel either has a driver compiled in for a piece of hardware and the hardware works, or If the driver is not compiled into the kernel and is supported by Linux source a module may be available that will work. This is where disro's such as MDK would probe for the device and offer to configure it. Debian does not do this but you can do it yourselff with 'modconf'. All you need to know is the module needed for your device and you do the install with 'modconf'. During the install you are offered a chance to select drivers, this calls modconf. - -- Greg Madden -BEGIN PGP SIGNATURE- Version: GnuPG v1.2.1 (GNU/Linux) iD8DBQE+jQVvk7rtxKWZzGsRAuT7AJwNI1zmI2dU1sN5CBvzgzdXprT4sgCfVr6D hvpZsCzr8p+w9uc8mjze4LU= =n3JV -END PGP SIGNATURE- -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Problem installing woody
Hello I am trying to install the current stable version of Debian thru the network. I have a Netgear FA311 NIC. So while I am adding modules to the kernel, I add the netsami module(National Semiconductors). Now when I try to go online to download other packages, I can not do this. I have a verizon dsl, and have a home network of 4 pcs. My router is 2wire. While configuring my network, I give the IP as 172.16.0.10, netmask as 255.255.255.0, DNS as 172.16.0.1(same as router), name server again as 172.16.0.1. Why am I not able to get anything. It keeps trying to connect to a server then errors out by saying Something wicked has happened Does anybody know what I might be doing wrong. Incidently my other windows machines work fine. Thanks _ Srinivas Rao -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Problems installing Woody from Hard Disk using GRUB
On Mon, Feb 17, 2003 at 02:56:14PM +0100, Frank Murphy wrote: What is wrong with the following setup for Grub? I always ended up with problems booting from hda5, which is not a partition on my system. (hda1 is windows, hda2 is swap, hda3 is going to be Sarge, and hda4 is Woody.) Here's my Grub config: title Woody install kernel (hd0,3)/boot/newinstall/linux-2.4.bin initrd (hd0,3)/boot/newinstall/root-2.4.bin Any ideas as to why this doesn't work? I end up with a kernel panic because the root filesystem can't be mounted. Frank Have you tried telling the kernel where the root device is? kernel (hd0,3)/boot/newinstall/linux-2.4.bin root=/dev/hda4 Or go the grub command line and see if you can't boot by hand. The ability to get to a command line when having boot problems is the reason I use grub. I have tried the root= parameter. The problem is that the kernel should be using the initrd for it's initial filesystem. If I give root=/dev/hda4, then it boots into my normal system, not into the Debian installer. What is the required value for the root= parameter to get the kernel to use the init rd? Or is this a limitation of Grub? I notice that the Debian install guide says nothing of installing via Grub. You are right. Ignore my silly respose. The kernel parameter for initrd is just initrd=/boot/newinstall/root-2.4.bin but this is just doing what you have done with the grub command so I would expect anything different. Is your initrd image valid? Can you loopback mount it? -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Problems installing Woody from Hard Disk using GRUB
The kernel parameter for initrd is just initrd=/boot/newinstall/root-2.4.bin but this is just doing what you have done with the grub command so I would expect anything different. Is your initrd image valid? Can you loopback mount it? I think it's valid because I was able to dd a moot disk with it. However, how can I do a loopback mount to try? You're using Grub, right? Would you mind trying to start a Woody install off your HD? Just download these: http://http.us.debian.org/debian/dists/woody/main/disks-i386/current/images-1.44/root.bin ftp://ftp.debian.org/debian/dists/woody/main/disks-i386/current/linux.bin And add the following to menu.lst: title new Woody install root (hd0,3) kernel /boot/newinstall/linux-2.4.bin initrd /boot/newinstall/root-2.4.bin Just see if you can boot to the start screen. Thanks, Frank -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Problems installing Woody from Hard Disk using GRUB
What is wrong with the following setup for Grub? I always ended up with problems booting from hda5, which is not a partition on my system. (hda1 is windows, hda2 is swap, hda3 is going to be Sarge, and hda4 is Woody.) Here's my Grub config: title Woody install kernel (hd0,3)/boot/newinstall/linux-2.4.bin initrd (hd0,3)/boot/newinstall/root-2.4.bin Any ideas as to why this doesn't work? I end up with a kernel panic because the root filesystem can't be mounted. Frank Have you tried telling the kernel where the root device is? kernel (hd0,3)/boot/newinstall/linux-2.4.bin root=/dev/hda4 Or go the grub command line and see if you can't boot by hand. The ability to get to a command line when having boot problems is the reason I use grub. I have tried the root= parameter. The problem is that the kernel should be using the initrd for it's initial filesystem. If I give root=/dev/hda4, then it boots into my normal system, not into the Debian installer. What is the required value for the root= parameter to get the kernel to use the init rd? Or is this a limitation of Grub? I notice that the Debian install guide says nothing of installing via Grub. Frank -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Problems installing Woody from Hard Disk using GRUB
I wanted to install Sarge on an empty partition in my machine that I have booting with GRUB. So I decided to start by installing Woody. I tried following the Installation directions for booting from LILO, but modifying them for Grub. (I failed and ended up installing from floppies.) What is wrong with the following setup for Grub? I always ended up with problems booting from hda5, which is not a partition on my system. (hda1 is windows, hda2 is swap, hda3 is going to be Sarge, and hda4 is Woody.) Here's my Grub config: title Woody install kernel (hd0,3)/boot/newinstall/linux-2.4.bin initrd (hd0,3)/boot/newinstall/root-2.4.bin Any ideas as to why this doesn't work? I end up with a kernel panic because the root filesystem can't be mounted. Frank -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Problems installing Woody from Hard Disk using GRUB
On Sun, Feb 16, 2003 at 01:36:10PM +0100, Frank Murphy wrote: I wanted to install Sarge on an empty partition in my machine that I have booting with GRUB. So I decided to start by installing Woody. I tried following the Installation directions for booting from LILO, but modifying them for Grub. (I failed and ended up installing from floppies.) What is wrong with the following setup for Grub? I always ended up with problems booting from hda5, which is not a partition on my system. (hda1 is windows, hda2 is swap, hda3 is going to be Sarge, and hda4 is Woody.) Here's my Grub config: title Woody install kernel (hd0,3)/boot/newinstall/linux-2.4.bin initrd (hd0,3)/boot/newinstall/root-2.4.bin Any ideas as to why this doesn't work? I end up with a kernel panic because the root filesystem can't be mounted. Frank Have you tried telling the kernel where the root device is? kernel (hd0,3)/boot/newinstall/linux-2.4.bin root=/dev/hda4 Or go the grub command line and see if you can't boot by hand. The ability to get to a command line when having boot problems is the reason I use grub. ~Michael -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
PreDepend error in installing Woody from CDs
After having been away from my Debian Linux system for some time, I just purchased the set of 7 CDs to upgrade my system to Woody I followed the Release Notes, upgrading using dselect, and ran into a PreDepend error, which aborted the upgrade Ive been spending some time reading the FAQs and the Package Manual and while I understand the nature of the problem, I see (thus far) no indication of the dependency particulars nor suggestions of a particular resolution Id welcome any recommendations -- David
Problem with installing Woody
I installed the base system of Debian 3.0 from CD-Rom which was made bootable. Then, the installation program could not find /dev/cdrom any longer. It is linked to /dev/hdd. I tried to mount it manually, but I was told that no medium was present. I could not believe it because the base system was installed from it. Is there anything I can do to continue to install more packages with the same cdrom disc? By the way, I had installed Mandrake 9.0 on the same computer before but wanted to try Debian to learn the difference between two. So far Mandrake looks lot better. hans -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Installing Woody on MIPS via CDROM
Is there anything special about getting Woody installed on MIPS using a CDROM? I've loaded Woody on x86 and HPPA without any problems, but I cannot get my Indigo2 to boot off the cd to start the install. The same Indigo2 boots up off the cd and installs Irix 5.3 just fine. Thanks, Mike -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: installing woody off the cd's
On Mon, Nov 04, 2002 at 12:18:49AM -0500, blaise dupart wrote: I have been trying to install debian 3.0 for the first time using the cd's I burned from the image files. However, debian can't seem to find the files on the cd even though I can see them using any other computer. Is this a cd format issue, or is there some bug I don't know about? What exactly happens? Is the problem that when the installer asks you for your CDs (to index the available packages), it doesn't recognise them? Or is that when you try to install packages, and you insert the CDs that dselect can't find packages on a CD? You'll have to be a bit more specific... -rob msg10885/pgp0.pgp Description: PGP signature
SYSLINUX: Boot Failed installing woody
Greetings- I just built a new machine (AMD XP 2200+, 1G RAM), and I'm trying to do a network install of woody. I haven't done this, since I haven't inaugurated a new machine since potato. I created and verified the rescue, root, and driver floppies, and booted to the rescue floppy. But on booting, I just get the SYSLINUX line, followed by Boot Failed. Any ideas where to go? Thanks. -- Andrew J Perrin - http://www.unc.edu/~aperrin Assistant Professor of Sociology, U of North Carolina, Chapel Hill [EMAIL PROTECTED] * andrew_perrin (at) unc.edu -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: SYSLINUX: Boot Failed installing woody
Greetings- I just built a new machine (AMD XP 2200+, 1G RAM), and I'm trying to do a network install of woody. I haven't done this, since I haven't inaugurated a new machine since potato. I created and verified the rescue, root, and driver floppies, and booted to the rescue floppy. But on booting, I just get the SYSLINUX line, followed by Boot Failed. Any ideas where to go? Have you tried the 'safe' floppy images? These are (as far as I remember) safer in case of syslinux problems. You'll find these in 'safe' subdir in your disks-i386 directory. Regards, Adam -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Re: Re: installing woody
On Sun, 28 Apr 2002 20:54:37 -0400, you wrote: begin Noah Sombrero quotation: on a promise 66 card. Don't know why potato thinks it is e. Is it possible that woody thinks it is something else? dmesg | grep ^hd This would work if I were able to boot woody to run it. From Potato, of course, your command shows me that the drive in question is lettered as e. How can I know if woody would call it something else if I can't boot woody? Gleason -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Problems installing woody
Hi everybody, I`m just beggining using Linux, and decided to start with Debian. Heard a lot about how good it was and everything :-). I`m trying to install woody ( Debian 3.0) at an ACER 4300 with Celeron 500 processor, 128 mem, and onboard video (SIS530/620) and network drivers(SIS900)... when I finished my first installation I could ping the local and external network just fine, but I cannot enter in graphic mode. I already did an apt-get install in almost all of the xserver-* that I found...:-/ I even downloaded ( using another machine) the xfree86 4.2.0 and the 2.4.18 kernel, but I can`t mount my cdrom. I tried to mount it with the #mount /dev/cdrom /cdrom and it returns me: /dev/cdrom is not a block device. my /etc/fstab has the following lines for the cdrom: /dev/cdrom/cdromiso9660ro,user,noauto0 0 I would be glad if someone could help me putting up the xserver and the cdrom! regards! Francisco -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Problems installing woody
On Wed, 12 Jun 2002 18:01, Francisco Fialho wrote: Hi everybody, I`m just beggining using Linux, and decided to start with Debian. Heard a lot about how good it was and everything :-). I`m trying to install woody ( Debian 3.0) at an ACER 4300 with Celeron 500 processor, 128 mem, and onboard video (SIS530/620) and network drivers(SIS900)... when I finished my first installation I could ping the local and external network just fine, but I cannot enter in graphic mode. I already did an apt-get install in almost all of the xserver-* that I found...:-/ I even downloaded ( using another machine) the xfree86 4.2.0 and the 2.4.18 kernel, but I can`t mount my cdrom. I tried to mount it with the #mount /dev/cdrom /cdrom and it returns me: /dev/cdrom is not a block device. my /etc/fstab has the following lines for the cdrom: /dev/cdrom/cdromiso9660ro,user,noauto 0 0 I would be glad if someone could help me putting up the xserver and the cdrom! regards! Francisco In regards to the cdrom.I had the same problem. Change /dev/cdrom to /dev/hdc That fixed it for me -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Problems installing woody
Michael, I couldn`t mount the /cdrom even changing my /etc/fstab to /dev/hdc... got the same message: /dev/hdc is not a block device. regards - Original Message - From: Michael Biddulph [EMAIL PROTECTED] To: debian-user@lists.debian.org Sent: Wednesday, June 12, 2002 9:31 AM Subject: Re: Problems installing woody On Wed, 12 Jun 2002 18:01, Francisco Fialho wrote: Hi everybody, I`m just beggining using Linux, and decided to start with Debian. Heard a lot about how good it was and everything :-). I`m trying to install woody ( Debian 3.0) at an ACER 4300 with Celeron 500 processor, 128 mem, and onboard video (SIS530/620) and network drivers(SIS900)... when I finished my first installation I could ping the local and external network just fine, but I cannot enter in graphic mode. I already did an apt-get install in almost all of the xserver-* that I found...:-/ I even downloaded ( using another machine) the xfree86 4.2.0 and the 2.4.18 kernel, but I can`t mount my cdrom. I tried to mount it with the #mount /dev/cdrom /cdrom and it returns me: /dev/cdrom is not a block device. my /etc/fstab has the following lines for the cdrom: /dev/cdrom/cdromiso9660ro,user,noauto 0 0 I would be glad if someone could help me putting up the xserver and the cdrom! regards! Francisco In regards to the cdrom.I had the same problem. Change /dev/cdrom to /dev/hdc That fixed it for me -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED] -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Problems installing woody
On Wed, Jun 12, 2002 at 05:01:31AM -0300, Francisco Fialho wrote: I`m trying to install woody ( Debian 3.0) at an ACER 4300 with Celeron 500 processor, 128 mem, and onboard video (SIS530/620) and network drivers(SIS900)... when I finished my first installation I could ping the local and external network just fine, but I cannot enter in graphic mode. I already did an apt-get install in almost all of the xserver-* that I found...:-/ You say you can't enter graphic mode. Error messages? System hangs? There is a metapackage for a workstation installation of X. It's called x-window-system. That way you won't have to figure out what packages to get. Bob pgpwh616OujFt.pgp Description: PGP signature
Re: Problems installing woody
I did an apt-get install -s task-x-window-system and had a message of package dependency... so I went doing an apt-get install package ( xlib6g-dev) that required (libc6-dev) that required (libc6), and when a tried to update or upgrade libc6, it gave me the message that it was already at the newest version. I don`t know what to do now... I was told that Debian was dificult to install... :-) but I didn`t realized that is was that dificult :-) can any one help me! regards Francisco - Original Message - From: Robert Ian Smit [EMAIL PROTECTED] To: Francisco Fialho [EMAIL PROTECTED] Sent: Wednesday, June 12, 2002 10:41 AM Subject: Re: Problems installing woody -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Problems installing woody
on Wed, Jun 12, 2002, Robert Ian Smit ([EMAIL PROTECTED]) wrote: On Wed, Jun 12, 2002 at 05:01:31AM -0300, Francisco Fialho wrote: I`m trying to install woody ( Debian 3.0) at an ACER 4300 with Celeron 500 processor, 128 mem, and onboard video (SIS530/620) and network drivers(SIS900)... when I finished my first installation I could ping the local and external network just fine, but I cannot enter in graphic mode. I already did an apt-get install in almost all of the xserver-* that I found...:-/ You say you can't enter graphic mode. Error messages? System hangs? There is a metapackage for a workstation installation of X. It's called x-window-system. That way you won't have to figure out what packages to get. Also, you can re-run the initial configuration wizard by issuing the following command (as root): dpkg-reconfigure xserver-xfree86 In my N00bian days, I went nuts looking for that command - it's not mentioned when the x-window-system metapackage is installed :-) Take care, Peter. -- Peter Whysall [EMAIL PROTECTED] The TLD in my email address is sdrawkcab. Debian GNU/Linux 3.0 sid -- kernel 2.4.18 pgpANBgJMglMY.pgp Description: PGP signature
Re: Problems installing woody
This could help: after I ran startx, I had the following output: (--) SVGA: XAA... and so on System: `/usr/X11R6/lib/X11/xkb/xkbcomp -w 1 -R/usr/X11R6/lib/X11/xkb -xkm -m u_intl -em1 The XKEYBOARD keymap compiler (xkbcomp) reports: -emp -eml Errors from xkbcomp are not fatal to the X server keymap/xfree86 compiled/xfree86.xkm` Fatal Server error: Cannot Open Mouse ( No such file or directory) X connection to :0.0 broken ( explicit kill or shutdown). hope this helps! Francisco - Original Message - From: Francisco Fialho [EMAIL PROTECTED] To: Robert Ian Smit [EMAIL PROTECTED] Cc: Debian - US debian-user@lists.debian.org Sent: Wednesday, June 12, 2002 6:46 AM Subject: Re: Problems installing woody I did an apt-get install -s task-x-window-system and had a message of package dependency... so I went doing an apt-get install package ( xlib6g-dev) that required (libc6-dev) that required (libc6), and when a tried to update or upgrade libc6, it gave me the message that it was already at the newest version. I don`t know what to do now... I was told that Debian was dificult to install... :-) but I didn`t realized that is was that dificult :-) can any one help me! regards Francisco - Original Message - From: Robert Ian Smit [EMAIL PROTECTED] To: Francisco Fialho [EMAIL PROTECTED] Sent: Wednesday, June 12, 2002 10:41 AM Subject: Re: Problems installing woody -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED] -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Problems installing woody
Peter, the dpkg-reconfigure xserver-xfree86 command gave me the following output: Package xserver-xfree86 is not installed and no info is available. /usr/sbin/dpkg-reconfigure: xsrever-xfree86 is not fully installed. then I went and did a apt-get install xserver-xfree86 and got the: Couldn`t find package xserver-xfree86... where can I get this package? regards Francisco - Original Message - From: Peter Whysall [EMAIL PROTECTED] To: debian-user@lists.debian.org Sent: Wednesday, June 12, 2002 10:56 AM Subject: Re: Problems installing woody -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Problems installing woody
On Wed, 12 Jun 2002 05:01:31 -0300 Francisco Fialho [EMAIL PROTECTED] wrote: I`m trying to install woody ( Debian 3.0) at an ACER 4300 with Celeron 500 processor, 128 mem, and onboard video (SIS530/620) and network drivers(SIS900)... when I finished my first installation I could ping the local and external network just fine, but I cannot enter in graphic mode. I already did an apt-get install in almost all of the xserver-* that I found...:-/ Hi! First of all, remove all xserver-* packages except xserver-xfree86 (and of course xserver-common) which must be installed. If you don't know at all what to install to get a running X system, just remove the xserver-packages except the both mentioned, and then apt-get install x-window-system (as Bob mentioned). Is this a laptop which you're trying to install Debian on? If yes, then the following could help, if not, read on below the next three paragraphs ;): It is quite normal that X doesn't run on such a machine, because the X driver does not know how to handle a certain part which drives the LCD display or so. But there's a good sis driver under http://www.winischhofer.net/linuxsis630.shtml which solves the problem. I'd first try not to change the kernel (If you don't know what you're doing), but only to install the X driver. Don't get frustrated because there's so much information on the page - the setup instructions which'll probably work for you are in the part: Variant 4: I want to use X without DRI. You'll just have to download the precompiled driver for X4.1 and place it in the directory which is mentioned on the site. Then, you do dpkg-reconfigure xserver-xfree86 at the console and choose the sis driver in the configuration process. Choose a monitor type which can handle the resolution you normally have on your LCD at 60 Hz, and choose the resolution you want to have; choose 16 for the colour depth (or 24 if you desperately need many, many colours ;) ). Now, don't start X immediately! First, edit the /etc/X11/XF86Config-4 file (for example, go to this directory with the file manager mc (apt-get install mc and then just type mc) and select Edit) (if it isn't there, edit the XF86Config file!) as described on the winischhofer site under the link example XF86Config-4. The most important sections are, if I remember correctly: -The Section Monitor: There must not be any Mode Lines, if any is there, delete them (delete lines: F8 key in MC editor). But be careful not to delete the EndSection signature at the end of the monitor section ;). VertRefresh must be set to 50-75, HorizSync to 30-90. ATTENTION: If this isn't set correctly-The section Device: The driver must be sis (with those quotation marks!). The option MaxXFBMem should be set to 8192 (also both with quotation marks!). A mem or video ram option or something like that is not needed for those adapters, and should not be used. (if it is there, just change it to a comment by adding a # at the beginning of the line. BTW, the format of this configuration file mostly looks like this: keyword value Option optionname value Option optionname between keyword and value or between the keyword Option and the optionname or before any keyword, you can use tabs or spaces, as you want, I think. After having configured the file, just try startx. If you don't have a laptop, just try to configure the x server correctly by dpkg-reconfigure xserver-xfree86 (choose sis driver and a reasonable monitor (never run a monitor at too high frequencies - serious demage can occur!)). If you've got further problems, you can write me at [EMAIL PROTECTED] Just configured two laptops with similar video adapters ;). Cheers, Stephan -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Problems installing woody
On Wed, 12 Jun 2002 05:57:13 -0300 Francisco Fialho [EMAIL PROTECTED] wrote: Michael, I couldn`t mount the /cdrom even changing my /etc/fstab to /dev/hdc... got the same message: /dev/hdc is not a block device. regards Hi! Do you know which controller your drive is connected to? If it is... ... at the primary controller, slave position: try mount /dev/hdb /cdrom ... at the secondary controller, master position: try mount /dev/hdc /cdrom ... at the secondary controller, slave position: try mount /dev/hdd /cdrom ... at the scsi controller: try mount /dev/sr0 /cdrom You can also try out all those possibilities. Or you press shift+PgUp (several times) after having booted, so you can see what the kernel has printed out (and usually also a message about detected cdrom's); you come back down by pressing shift+PgDn. Cheers, Stephan -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Problems installing woody
On Wed, Jun 12, 2002 at 06:46:30AM -0300, Francisco Fialho wrote: I did an apt-get install -s task-x-window-system and had a message of package dependency... so I went doing an apt-get install package ( xlib6g-dev) that required (libc6-dev) that required (libc6), and when a tried to update or upgrade libc6, it gave me the message that it was already at the newest version. Could you quote the exact error messages, please? Thanks, -- Colin Watson [EMAIL PROTECTED] -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Problems installing woody
on Wed, Jun 12, 2002, Francisco Fialho ([EMAIL PROTECTED]) wrote: Peter, the dpkg-reconfigure xserver-xfree86 command gave me the following output: Package xserver-xfree86 is not installed and no info is available. /usr/sbin/dpkg-reconfigure: xsrever-xfree86 is not fully installed. then I went and did a apt-get install xserver-xfree86 and got the: Couldn`t find package xserver-xfree86... where can I get this package? xserver-xfree86 is the package that provides the actual X server binary itself and supporting files. The easiest way to obtain it, and all the other necessary packages, is to install the x-window-system metapackage: apt-get install x-window-system What x-window-system does is depend on all the appropriate packages for the basic X Window System installation. You'll then probably want to install a window manager or desktop environment of some sort. twm is functional but less than pretty. Personally, I favour GNOME. It would be much easier for you to install aptitude (apt-get install aptitude) and look at the tasks section there than it would be for me to enumerate all the packages you'd need :) Hope this helps Take care, Peter. -- Peter Whysall [EMAIL PROTECTED] The TLD in my email address is sdrawkcab. Debian GNU/Linux 3.0 sid -- kernel 2.4.18 pgp1pq1NWFfas.pgp Description: PGP signature
Re: Problems installing woody
Hi all, Am Mittwoch, 12. Juni 2002 16:28 schrieb Stephan Hachinger: [...] Do you know which controller your drive is connected to? If it is... ... at the primary controller, slave position: try mount /dev/hdb /cdrom [...] also you can try dmesg | grep hd to figure out on what /dev/hd? you got your cdrom-drive. If you got scsi try dmesg | grep sc . HTH gerhard -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Problems installing woody
Sorry for the big mail... this is what I get when apt-get install -s task-x-window-system... and so on! Regards, Francsico McLaren:/# apt-get install -s task-x-window-system Reading Package Lists...done Building Dependecy Tree... Done Some packages could not be installed.vThis mean that you have requested an impossible situation or if you are using the unstable distribution that some required packages have not yet been created or been moved out of Incoming. Since you only requested a single operation it is extremely likely that the package is simple not installable and a bug report against that package should be filed. The following information may help to resolve the situation: Sorry, but the following packagwes have unmet dependencies: task-x-window-system: depends: xlib6g-dev but it is not going to be installed. E: sorry, broken packages McLaren:/# apt-get install xlib6g-dev Reading Package Lists...done Building Dependecy Tree... Done Some packages could not be installed.vThis mean that you have requested an impossible situation or if you are using the unstable distribution that some required packages have not yet been created or been moved out of Incoming. Since you only requested a single operation it is extremely likely that the package is simple not installable and a bug report against that package should be filed. The following information may help to resolve the situation: Sorry, but the following packagwes have unmet dependencies: xlib6g-dev: depends: libc6-dev but it is not going to be installed. E: sorry, broken packages McLaren:/# apt-get install libc6-dev Reading Package Lists...done Building Dependecy Tree... Done Some packages could not be installed.vThis mean that you have requested an impossible situation or if you are using the unstable distribution that some required packages have not yet been created or been moved out of Incoming. Since you only requested a single operation it is extremely likely that the package is simple not installable and a bug report against that package should be filed. The following information may help to resolve the situation: Sorry, but the following packagwes have unmet dependencies: libc6-dev: depends: libc6 (= 2.1.3-20) but 2.2.5-6 is to be installed. E: sorry, broken packages McLaren:/# apt-get install libc6 Reading Package Lists...done Building Dependecy Tree... Done Sorry, libc6 is already the newest version. 0 packages upgraded, and so on... - Original Message - From: Colin Watson [EMAIL PROTECTED] To: Debian - US debian-user@lists.debian.org Sent: Wednesday, June 12, 2002 11:29 AM Subject: Re: Problems installing woody On Wed, Jun 12, 2002 at 06:46:30AM -0300, Francisco Fialho wrote: I did an apt-get install -s task-x-window-system and had a message of package dependency... so I went doing an apt-get install package ( xlib6g-dev) that required (libc6-dev) that required (libc6), and when a tried to update or upgrade libc6, it gave me the message that it was already at the newest version. Could you quote the exact error messages, please? Thanks, -- Colin Watson [EMAIL PROTECTED] -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED] -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Problems installing woody
Gerhard, thank you very much! I used the dmesg | grep hd command and found my cdrom at /dev/hdd made the change at /etc/fstab and it worked! I`m still fighting with my X config! :-) Thanks again regards Francisco - Original Message - From: Gerhard Gaussling [EMAIL PROTECTED] To: debian-user@lists.debian.org Sent: Wednesday, June 12, 2002 11:54 AM Subject: Re: Problems installing woody Hi all, Am Mittwoch, 12. Juni 2002 16:28 schrieb Stephan Hachinger: [...] Do you know which controller your drive is connected to? If it is... ... at the primary controller, slave position: try mount /dev/hdb /cdrom [...] also you can try dmesg | grep hd to figure out on what /dev/hd? you got your cdrom-drive. If you got scsi try dmesg | grep sc . HTH gerhard -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED] -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Problems installing woody
On Wed, Jun 12, 2002 at 08:04:45AM -0300, Francisco Fialho wrote: Sorry for the big mail... this is what I get when apt-get install -s task-x-window-system... In woody, use 'x-window-system', not 'task-x-window-system'. McLaren:/# apt-get install xlib6g-dev xlib6g-dev is present in woody, but only for compatibility. Sorry, but the following packagwes have unmet dependencies: libc6-dev: depends: libc6 (= 2.1.3-20) but 2.2.5-6 is to be installed. E: sorry, broken packages That looks to me as if you're trying to mix packages from potato and woody somehow ... -- Colin Watson [EMAIL PROTECTED] -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Problems installing woody
when I give an apt-get install x-window-system it returns: couldn`t find package x-window-system. how can I correct the mix packages search? regards Francisco - Original Message - From: Colin Watson [EMAIL PROTECTED] To: Debian - US debian-user@lists.debian.org Sent: Wednesday, June 12, 2002 12:17 PM Subject: Re: Problems installing woody On Wed, Jun 12, 2002 at 08:04:45AM -0300, Francisco Fialho wrote: Sorry for the big mail... this is what I get when apt-get install -s task-x-window-system... In woody, use 'x-window-system', not 'task-x-window-system'. McLaren:/# apt-get install xlib6g-dev xlib6g-dev is present in woody, but only for compatibility. Sorry, but the following packagwes have unmet dependencies: libc6-dev: depends: libc6 (= 2.1.3-20) but 2.2.5-6 is to be installed. E: sorry, broken packages That looks to me as if you're trying to mix packages from potato and woody somehow ... -- Colin Watson [EMAIL PROTECTED] -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED] -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Problems installing woody
On Wed, Jun 12, 2002 at 08:17:01AM -0300, Francisco Fialho wrote: when I give an apt-get install x-window-system it returns: couldn`t find package x-window-system. how can I correct the mix packages search? I bet I know what's wrong. The testing installation disks have 'stable' in the default contents of /etc/apt/sources.list (arguably a bug ... but it'll be OK once woody really goes stable). Edit /etc/apt/sources.list, change all references to 'stable' to 'woody', run 'dselect update', and try again. -- Colin Watson [EMAIL PROTECTED] -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Problems installing woody
Am Mittwoch, 12. Juni 2002 17:17 schrieb Colin Watson: That looks to me as if you're trying to mix packages from potato and woody somehow ... If so, it might be helpful to mail the output of the following commands : cat /etc/apt/preferences cat /etc/apt/sources.list ciao gerhard sorry about my poor english -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Problems installing woody
Am Mittwoch, 12. Juni 2002 12:02 schrieb Francisco Fialho: This could help: [...] Fatal Server error: Cannot Open Mouse ( No such file or directory) X connection to :0.0 broken ( explicit kill or shutdown). Without mouse the xserver can not start. What kind of mouse do you use? At what kind of port? What does 'ls -l /dev/mouse' print to the screen? hope this helps! [...] I don`t know what to do now... I was told that Debian was dificult to install... :-) but I didn`t realized that is was that dificult :-) Yes, it's hard in the begining. Did you already try 'dpkg-reconfigure xserver-xfree86' ? to configure your mouse and xserver? gerhard -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Problems installing woody
Am Mittwoch, 12. Juni 2002 13:08 schrieb Francisco Fialho: I used the dmesg | grep hd command and found my cdrom at /dev/hdd made the change at /etc/fstab and it worked! I`m still fighting with my X config! :-) Try 'apt-cdrom add' and insert your debian cdroms. see the output of 'man apt' (man man ;) ) for further details. Than you might be able to apt-get install gpm or the xserver stuff like mentioned by the other list-members. HTH gerhard -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Problems installing woody - it is solved and I have a graphic interface running :-)
I would like to thank everybody that helped me put up my X server up! It`s now working and I have a graphic interface! You guys are great! Hope I can learn and help you all, the same way you helped me! :-) Thank you all for your great help and support :-) Regards -- |Francisco | | | |GNU/LINUX distributions are just like religion, | |each one has it`s own. But only one takes you | |to the right place. Use LINUX, use Debian.| -- . Trouble? Contact debian-user@lists.debian.org -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Downloading and installing woody
I'm new to Debian, first heard about it at the Install Fest that took place at Univeristy of Campinas ( one of brazilians top 3 ). I downloaded it, and tried to install Debian 2.2rev6, but unsuccessfully. I had problems with the network and video card, but know I want to try it again with the latest woody. (it supports my hardware.) :-) I want to download the 650 Mg cds, and not just the 5 mg files I found in most of the Debian mirrors. Can anyone indicate a ftp or http site that I can download the full woody. Regards Francisco Fialho -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Downloading and installing woody
On Wed, 2002-06-05 at 13:02, Francisco Fialho wrote: I'm new to Debian, first heard about it at the Install Fest that took place at Univeristy of Campinas ( one of brazilians top 3 ). I downloaded it, and tried to install Debian 2.2rev6, but unsuccessfully. I had problems with the network and video card, but know I want to try it again with the latest woody. (it supports my hardware.) :-) I want to download the 650 Mg cds, and not just the 5 mg files I found in most of the Debian mirrors. Can anyone indicate a ftp or http site that I can download the full woody. Hi, Francisco. Try here: http://www.debian.org/CD/http-ftp/#testing good luck -Mark -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
installing woody
Booting from floppy or hd, stock kernel or handrolled, this is as close as I can get in booting woody: Request-Module[block-major-33]:Root fs not mounted VFS: cannot open root device 2109 or 21:09 Please append correct root= boot option The root option in lilo.cfg is root=/dev/hde9 What to do? potato boots fine. Gleason -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: installing woody
On Sun Apr 28, 2002 at 01:35:55AM -0700, Noah Sombrero wrote: Booting from floppy or hd, stock kernel or handrolled, this is as close as I can get in booting woody: Request-Module[block-major-33]:Root fs not mounted VFS: cannot open root device 2109 or 21:09 Please append correct root= boot option The root option in lilo.cfg is root=/dev/hde9 should that be /dev/hda9? -- -CraigW -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Re: installing woody
On Sun, 28 Apr 2002 09:13:23 -0700, you wrote: On Sun Apr 28, 2002 at 01:35:55AM -0700, Noah Sombrero wrote: Booting from floppy or hd, stock kernel or handrolled, this is as close as I can get in booting woody: Request-Module[block-major-33]:Root fs not mounted VFS: cannot open root device 2109 or 21:09 Please append correct root= boot option The root option in lilo.cfg is root=/dev/hde9 should that be /dev/hda9? I think I have the easy answers covered. I have two hard drives. a is an old 3gb drive on the secondary master slot. The e drive is on a promise 66 card. Don't know why potato thinks it is e. Is it possible that woody thinks it is something else? Gleason -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: installing woody
On Sun, Apr 28, 2002 at 01:35:55AM -0700, Noah Sombrero wrote: Booting from floppy or hd, stock kernel or handrolled, this is as close as I can get in booting woody: Request-Module[block-major-33]:Root fs not mounted VFS: cannot open root device 2109 or 21:09 Please append correct root= boot option The root option in lilo.cfg is root=/dev/hde9 ^--^ lilo.conf? What to do? potato boots fine. Gleason Did you install a new kernel when you upgraded to woody? woody should boot with same kernel you had with potato. Which kernel are you trying to use? Is it installed from a stock debian deb? Can you post your lilo configuration file? -- Jerome pgpU5hVZRwia4.pgp Description: PGP signature
Re: Re: installing woody
On Sun, 28 Apr 2002 16:10:05 -0400, you wrote: Did you install a new kernel when you upgraded to woody? woody should boot with same kernel you had with potato. You mean I can't use the new 2.4 line? Naw, that can't be right. Maybe I can't be trusted will all this new complicated stuff, spose? Which kernel are you trying to use? Is it installed from a stock debian deb? Can you post your lilo configuration file? 2.4.18-5 for amd k6-2. Also tried to roll my own. Same result. lilo on floppy: lba32 boot = /dev/fd0 install = boot.b map = map compact prompt timeout = 50 read-only image = vmlinuz label = linux initrd=/initrd.img root = /dev/hde6 I added the initrd part since mkboot did not. I also made sure the /vmlinuz and initrd links on / point to the correct files in /boot lilo on hd: lba32 boot=/dev/hde9 root=/dev/hde9 install=/boot/boot.b delay=20 map=/boot/map vga=normal image=/vmlinuz initrd=/initrd.img label=Linux read-only I thought the idea that woody might be calculating partition labels differently so good that I tried a few. hda9 does not work as does not hde6 The hd/partition layout is as follows: primary master - a- not used primary slave- b -not used secondary master -c- 3gb with partions 5,6,7 secondary slave - d - not used promise 66 - e - with partitions 1,5,6,7,8,9,10 All partitions are ntfs except that e9 is linux and c6 is dos Gleason -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Re: installing woody
On Sun, Apr 28, 2002 at 02:21:06PM -0700, Noah Sombrero wrote: On Sun, 28 Apr 2002 16:10:05 -0400, you wrote: Did you install a new kernel when you upgraded to woody? woody should boot with same kernel you had with potato. You mean I can't use the new 2.4 line? Naw, that can't be right. Maybe I can't be trusted will all this new complicated stuff, spose? Not just to you but Debian is cautious when it comes to Kernel upgrade. Changing sources.list does not upgrade kernel from 2.2 to 2.4. It requires you to install and at the same time configure few things. Mostly initrd related staff. Try booting with 2.2 kernel. If you lost them, boot with potato rescue floppy using rescue root=/dev/hda? at the prompt. If it boot OK, it must have been some configuration issues. Good luck. Check my Debian reference below for more hint. :) -- ~\^o^/~~~ ~\^.^/~~~ ~\^*^/~~~ ~\^_^/~~~ ~\^+^/~~~ ~\^:^/~~~ ~\^v^/~~~ + Osamu Aoki @ Cupertino CA USA See User's Guide: http://www.debian.org/doc/manuals/users-guide/ See Debian reference: http://www.debian.org/doc/manuals/reference/ Debian reference Project at: http://qref.sf.net I welcome your constructive criticisms and corrections. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Re: Re: installing woody
On Sun, 28 Apr 2002 14:35:48 -0700, you wrote: Not just to you but Debian is cautious when it comes to Kernel upgrade. Changing sources.list does not upgrade kernel from 2.2 to 2.4. It requires you to install and at the same time configure few things. Mostly initrd related staff. did apt-get update apt-get upgrade Then installed the new kernel. Yes, I can still boot 2.2 from a floppy. I have not removed the old kernel. This system never did boot from hard drive because of the remote location of the linux partition. What needs to be configured besides lilo? See User's Guide: http://www.debian.org/doc/manuals/users-guide/ See Debian reference: http://www.debian.org/doc/manuals/reference/ Debian reference Project at: http://qref.sf.net Will look at these. Usually, cooked references are acres of simple advice which never get around to mentioning the problem I am having. Or the problem is mentioned in the 10th sentence of the 12,375th paragraph, right here on page 1,323 with no reference anywhere that points to it. It is so much easier and quicker if somebody knows the answer. Gleason -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Re: Re: installing woody
On Sun, Apr 28, 2002 at 02:53:14PM -0700, Noah Sombrero wrote: On Sun, 28 Apr 2002 14:35:48 -0700, you wrote: Not just to you but Debian is cautious when it comes to Kernel upgrade. Changing sources.list does not upgrade kernel from 2.2 to 2.4. It requires you to install and at the same time configure few things. Mostly initrd related staff. did apt-get update apt-get upgrade Then installed the new kernel. Yes, I can still boot 2.2 from a floppy. I have not removed the old kernel. This system never did boot from hard drive because of the remote location of the linux partition. I think it may not be true with new lilo. Exactly spoken at: See Debian reference: http://www.debian.org/doc/manuals/reference/ 3.1.5 A Lilo myth Also, 5 Upgrading distribution, 7.2 Modularized 2.4 kernel may help. I remember /etc/kernel-pkg.conf needs to be touched. Oh, older 2.4 images may not be good. Use at least 2.4.18 or later. Anyway, I can assure you this initrd scheme and highly modular pre-packaged 2.4 kernel-image need steap lerning curve. It was tough on me. Will look at these. Usually, cooked references are acres of simple advice which never get around to mentioning the problem I am having. Or the problem is mentioned in the 10th sentence of the 12,375th paragraph, right here on page 1,323 with no reference anywhere that points to it. It is so much easier and quicker if somebody knows the answer. I know the feeling. Any suggestions for improvement welcomed :) -- ~\^o^/~~~ ~\^.^/~~~ ~\^*^/~~~ ~\^_^/~~~ ~\^+^/~~~ ~\^:^/~~~ ~\^v^/~~~ + Osamu Aoki @ Cupertino CA USA See Debian reference: http://www.debian.org/doc/manuals/reference/ Debian reference Project at: http://qref.sf.net I welcome your constructive criticisms and corrections. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Re: Re: Re: installing woody
Anyway, I can assure you this initrd scheme and highly modular pre-packaged 2.4 kernel-image need steap lerning curve. It was tough on me. Thanks for your useful advice. Gleason -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Re: Re: installing woody
On Sun, Apr 28, 2002 at 02:53:14PM -0700, Noah Sombrero wrote: On Sun, 28 Apr 2002 14:35:48 -0700, you wrote: Not just to you but Debian is cautious when it comes to Kernel upgrade. Changing sources.list does not upgrade kernel from 2.2 to 2.4. It requires you to install and at the same time configure few things. Mostly initrd related staff. did apt-get update apt-get upgrade If you didn't do apt-get dist-upgrade, do that to load new package (where potato package has been split into several in woody) and to solve dependency issues with any packages you have been kept back and not upgraded. Then installed the new kernel. Yes, I can still boot 2.2 from a floppy. I have not removed the old kernel. This system never did boot from hard drive because of the remote location of the linux partition. What needs to be configured besides lilo? See User's Guide: http://www.debian.org/doc/manuals/users-guide/ See Debian reference: http://www.debian.org/doc/manuals/reference/ Debian reference Project at: http://qref.sf.net Will look at these. Usually, cooked references are acres of simple advice which never get around to mentioning the problem I am having. Or the problem is mentioned in the 10th sentence of the 12,375th paragraph, right here on page 1,323 with no reference anywhere that points to it. It is so much easier and quicker if somebody knows the answer. Gleason -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED] -- Jerome pgpAVFLBSaOB0.pgp Description: PGP signature
Re: Re: installing woody
On Sun, Apr 28, 2002 at 02:21:06PM -0700, Noah Sombrero wrote: On Sun, 28 Apr 2002 16:10:05 -0400, you wrote: Did you install a new kernel when you upgraded to woody? woody should boot with same kernel you had with potato. You mean I can't use the new 2.4 line? Naw, that can't be right. Maybe I can't be trusted will all this new complicated stuff, spose? Which kernel are you trying to use? Is it installed from a stock debian deb? Can you post your lilo configuration file? 2.4.18-5 for amd k6-2. Also tried to roll my own. Same result. For the 2.4.x kernel debs, file system support is highly modularized. You may need to add a file system module to /etc/modules to boot. Check the config file in boot to see if the file system support you need is module or commpiled in. If you roll your own, make sure ide and root file system support is compiled into kernel. Also, if you configure initrd into kernel and use make-kpkg to compile your kernel image, add --initrd option; if you compiled without initrd option, make sure CONFIG_BLK_DEV_INITRD is not set in your configuration. lilo on floppy: lba32 boot = /dev/fd0 install = boot.b map = map compact prompt timeout = 50 read-only image = vmlinuz label = linux initrd=/initrd.img root = /dev/hde6 I added the initrd part since mkboot did not. I also made sure the /vmlinuz and initrd links on / point to the correct files in /boot lilo on hd: lba32 boot=/dev/hde9 root=/dev/hde9 install=/boot/boot.b delay=20 map=/boot/map vga=normal image=/vmlinuz initrd=/initrd.img label=Linux read-only I thought the idea that woody might be calculating partition labels differently so good that I tried a few. hda9 does not work as does not hde6 The hd/partition layout is as follows: primary master - a- not used primary slave- b -not used secondary master -c- 3gb with partions 5,6,7 secondary slave - d - not used promise 66 - e - with partitions 1,5,6,7,8,9,10 All partitions are ntfs except that e9 is linux and c6 is dos Gleason -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED] -- Jerome pgpuH7nterE5s.pgp Description: PGP signature
Re: Re: installing woody
begin Noah Sombrero quotation: on a promise 66 card. Don't know why potato thinks it is e. Is it possible that woody thinks it is something else? dmesg | grep ^hd -- Shawn McMahon| McMahon's Laws of Linux support: http://www.eiv.com | 1) There's more than one way to do it AIM: spmcmahonfedex, smcmahoneiv | 2) Somebody thinks your way is wrong pgp3zqn1qug3U.pgp Description: PGP signature
Re: problems with dpkg/deselct installing woody
thx Oliver! your suggestion worked perfectly :-))) yours, Richard On Sun, 2002-03-24 at 13:08, Oliver Elphick wrote: On Sun, 2002-03-24 at 11:53, Richard Palfalvi wrote: During the installation-process with dselect it run into the following error: Removing gnome-games /var/lib/dpkg/info/gnome-games.postrm: scrollkeeper-update: command not found dpkg: error processing gnome-games (--remove): subprocess post-removal script returned error exit status 127 ... So,the thing is that I cannot continue/finish the installation process because any retry runs in the same error-message. ... Is it a good idea to just erase all files in the /var/cache directories and restart the whole installation process from scratch or is there some nicer way to fix the problem? No. Your problem is with this particular package. Look at the script /var/lib/dpkg/info/gnome-games.postrm The error message says it is trying to run a command that is not present on your machine, so you need to make the script bypass the error. The easiest way is to delete the line containing the dud command (scrollkeeper-update), and any lines dependent on it. Then run dpkg --purge gnome-games If any other errors show up, repeat the procedure until they all go away and the package is successfully purged. -- Oliver Elphick[EMAIL PROTECTED] Isle of Wight http://www.lfix.co.uk/oliver GPG: 1024D/3E1D0C1C: CA12 09E0 E8D5 8870 5839 932A 614D 4C34 3E1D 0C1C But they that wait upon the Lord shall renew their strength; they shall mount up with wings as eagles; they shall run and not be weary; and they shall walk, and not faint. Isaiah 40:31 -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
problems with dpkg/deselct installing woody
Hi ! I have the following problem. I once installed potato on an old pentium-machine and then didn't use it for a year or so. Now I d like to use it again and tried to update to WOODY (before there was nothing really important on the machine), so I just pointed apt in sources.list to the testing-url. Then I started the update with dselect. Download of all files/packages worked fine! :-) BUT: During the installation-process with dselect it run into the following error: Removing gnome-games /var/lib/dpkg/info/gnome-games.postrm: scrollkeeper-update: command not found dpkg: error processing gnome-games (--remove): subprocess post-removal script returned error exit status 127 errors were encountered while processing: gnome-games dpkg --remove returned error exit status 1. press enter to continue. So,the thing is that I cannot continue/finish the installation process because any retry runs in the same error-message. I had a look in the man page of dpkg and tried some manual error fixing like: dpkg --force-reinstreq gnome-games or dpkg -purge gnome-games but I always got the same error messages the dpkg --status gnome-games command shows the output you can see in the inclosed attachment-textfile. Is it a good idea to just erase all files in the /var/cache directories and restart the whole installation process from scratch or is there some nicer way to fix the problem? any help and hints really appreciated, because it is impossible for me at the moment to finish the installation due to the cercle vicieux. thx in advance, Richard PS: please use my email-adress in the CC-line as I am not subscribed to the mailing list at the moment. -- Mag. Richard Palfalvi Wien - Vienne - Vienna Österreich - Autriche - Austria Package: gnome-games Status: purge ok installed Priority: optional Section: games Installed-Size: 2652 Maintainer: Ximian, Inc. [EMAIL PROTECTED] Version: 1.4.0.1-ximian.8 Depends: gnome-core (= 1.2.0-0), gnome-card-games (= 1.4.0.1-ximian.8), gnome-gnomine (= 1.4.0.1-ximian.8), gnome-stones (= 1.4.0.1-ximian.8), gnome-gturing (= 1.4.0.1-ximian.8), gnome-mahjongg (= 1.4.0.1-ximian.8), gnome-same-gnome (= 1.4.0.1-ximian.8), gnome-gnibbles (= 1.4.0.1-ximian.8), gnome-gnometris (= 1.4.0.1-ximian.8), gnome-gnotravex (= 1.4.0.1-ximian.8), gnome-gtali (= 1.4.0.1-ximian.8), gnome-gnobots2 (= 1.4.0.1-ximian.8), gnome-iagno (= 1.4.0.1-ximian.8), gnome-glines (= 1.4.0.1-ximian.8), gnome-gataxx (= 1.4.0.1-ximian.8) Description: Empty package that requires the installation of all gnome-games packages. Gnome is the GNU Network Object Model Environment . It is a project to build a complete, user-friendly desktop based entirely on free software.
Re: problems with dpkg/deselct installing woody
On Sun, 2002-03-24 at 11:53, Richard Palfalvi wrote: During the installation-process with dselect it run into the following error: Removing gnome-games /var/lib/dpkg/info/gnome-games.postrm: scrollkeeper-update: command not found dpkg: error processing gnome-games (--remove): subprocess post-removal script returned error exit status 127 ... So,the thing is that I cannot continue/finish the installation process because any retry runs in the same error-message. ... Is it a good idea to just erase all files in the /var/cache directories and restart the whole installation process from scratch or is there some nicer way to fix the problem? No. Your problem is with this particular package. Look at the script /var/lib/dpkg/info/gnome-games.postrm The error message says it is trying to run a command that is not present on your machine, so you need to make the script bypass the error. The easiest way is to delete the line containing the dud command (scrollkeeper-update), and any lines dependent on it. Then run dpkg --purge gnome-games If any other errors show up, repeat the procedure until they all go away and the package is successfully purged. -- Oliver Elphick[EMAIL PROTECTED] Isle of Wight http://www.lfix.co.uk/oliver GPG: 1024D/3E1D0C1C: CA12 09E0 E8D5 8870 5839 932A 614D 4C34 3E1D 0C1C But they that wait upon the Lord shall renew their strength; they shall mount up with wings as eagles; they shall run and not be weary; and they shall walk, and not faint. Isaiah 40:31 signature.asc Description: This is a digitally signed message part
Installing Woody from CD-8
I thought I saw soemwhere that someone installed woody from the disk8 iso. Well, I downloaded the iso (I had lots of problems downloading woody; the only computer I could get any success from has limited HD space,so I had to get the small one). When I booted the CD, all started going well until it asked for a 'floppies-144' directory (or some similar named diretory) which is not in the CD. So, what am I missing? I have a 56k connection at home, so a net install is not really an option. D I really have to downlad CD1? I figured CD8 had most of what I need, and I could 'apt-get update apt-get upgrade' and then 'apt-get install' any other packages I might need. I looked through http://www.debian.org/ and just didn't see (or recognize ;-) any helpful info. -- Paul F. Pearson ([EMAIL PROTECTED]) http://home.hiwaay.net/~ppearson/ Lord heal our land. Father heal our land. Hear our cry and turn our nation back to You - Heal Our Land, _Magnify The Lord_ (Integrity Music)
Re: Recommended approach for installing Woody
Scott Henson wrote: I really would not recomend installing potato then dist-upgrading. Having tried that several time, I could never recomend that. How long ago, what went wrong, and did you report bugs? We put a lot of effort into making upgrades to woody work well. -- see shy jo
Re: Recommended approach for installing Woody
* Scott Henson ([EMAIL PROTECTED]) spake thusly: On Wed, 2002-02-06 at 22:04, Chris Kenrick wrote: What's the recommended approach for installing Woody these days? I really would not recomend installing potato then dist-upgrading. Having tried that several time, I could never recomend that. What I did is got some woody disks and did a regular install. Now what I would recomend is useing the new net install CD's. I basically did that useing the regular CD's. The real advantage that I see is the smaller image. But I would really recomend that you install woody straight. You will save yourself so much pain. Intersting. My experience is exactly opposite -- last time I tried woody netinst image (couple of weeks ago), setup script was looking for Release file in the wrong place, so I couldn't install base system. Instlling potato and dist-upgrading to woody worked like a charm, OTOH. (Aside: why not put base on netinst CD? Sure the image will be bigger -- by what, 5%? -- but then you could install minimal bootable system off it.) Dima -- Surely there is a polite way to say FOAD.-- Shmuel Metz Go forth and multiply. -- Paul Martin
Re: Recommended approach for installing Woody
I've installed woody from potato via dist-upgrade apt-get --fix-broken --show-upgraded dist-upgrade now three times in the past year; twice on my own machine and twice on others, and have allways been successful. The first time, dpkg couldn't preconfigure and I had to start installing packages one by one with apt-get until I finally found out the complaint was that I didn't have apt-utils (if I remember correctly); after I installed that, everything was fine. I think one other time I had to run dist-upgrade to get everything to download and install, but that was no big problem. A lot of the trick with upgrading to woody from potato is making sure everything downloads. The two things that can prevent this that I can think of immediately are: a ppp connection that broke off--but you should know about this because you'll get messages; and either not having the right lines in your sources.list or, if your potato lines are still there too, not having the woody lines in the right place, above the potato lines. Of course, I know it's not that simple; there are plenty of other things that can go wrong, but these were the ones that I found. At any rate, I'd be pretty comfortable now upgrading from potato to woody if I had to do it on a machine of my own or for somebody else. -- Cheryl
Re: Recommended approach for installing Woody
On Thu, 7 Feb 2002 11:47:55 -0600 (CST) Cheryl Homiak [EMAIL PROTECTED] wrote: I've installed woody from potato via dist-upgrade apt-get --fix-broken --show-upgraded dist-upgrade now three times in the past year; twice on my own machine and twice on others, and have allways been successful. The first time, dpkg couldn't preconfigure and I had to start installing packages one by one with apt-get until I finally found out the complaint was that I didn't have apt-utils (if I remember correctly); after I installed that, everything was fine. I think one other time I had to run dist-upgrade to get everything to download and install, but that was no big problem. A lot of the trick with upgrading to woody from potato is making sure everything downloads. The two things that can prevent this that I can think of immediately are: a ppp connection that broke off--but you should know about this because you'll get messages; and either not having the right lines in your sources.list or, if your potato lines are still there too, not having the woody lines in the right place, above the potato lines. Of course, I know it's not that simple; there are plenty of other things that can go wrong, but these were the ones that I found. At any rate, I'd be pretty comfortable now upgrading from potato to woody if I had to do it on a machine of my own or for somebody else. One suggestion might be to do: apt-get -d dist-upgrade apt-get --fix-broken --show-upgraded dist-upgrade So, if your ppp (or broadband, for that matter) link goes down, your system isn't messed up. -- ++ | Ron Johnson, Jr.Home: [EMAIL PROTECTED]| | Jefferson, LA USA http://ronandheather.dhs.org:81| || ! As I like to joke, I may have invented it, but Microsoft | | made it popular David Bradley, regarding Ctrl-Alt-Del | ++
Re: Recommended approach for installing Woody
*** On Thu, 7 Feb 2002 at 12:33pm Ron Johnson shared this with the class:: One suggestion might be to do: apt-get -d dist-upgrade apt-get --fix-broken --show-upgraded dist-upgrade call me a newbie, but what would the exact lines be that someone should add to their sources.list file to do this from 2.2_rev5 and go up to woody?
Re: Recommended approach for installing Woody
On Thu, Feb 07, 2002 at 12:33:10PM -0600, Ron Johnson wrote: On Thu, 7 Feb 2002 11:47:55 -0600 (CST) Cheryl Homiak [EMAIL PROTECTED] wrote: I've installed woody from potato via dist-upgrade apt-get --fix-broken --show-upgraded dist-upgrade now three times in the past year; twice on my own machine and twice on others, and have allways been successful. The first time, dpkg couldn't preconfigure and I had to start installing packages one by one with apt-get until I finally found out the complaint was that I didn't have apt-utils (if I remember correctly); after I installed that, everything was fine. I think one other time I had to run dist-upgrade to get everything to download and install, but that was no big problem. A lot of the trick with upgrading to woody from potato is making sure everything downloads. The two things that can prevent this that I can think of immediately are: a ppp connection that broke off--but you should know about this because you'll get messages; and either not having the right lines in your sources.list or, if your potato lines are still there too, not having the woody lines in the right place, above the potato lines. Of course, I know it's not that simple; there are plenty of other things that can go wrong, but these were the ones that I found. At any rate, I'd be pretty comfortable now upgrading from potato to woody if I had to do it on a machine of my own or for somebody else. One suggestion might be to do: apt-get -d dist-upgrade apt-get --fix-broken --show-upgraded dist-upgrade So, if your ppp (or broadband, for that matter) link goes down, your system isn't messed up. I found that potato to woody upgrades went a lot better if the very first thing I did was apt-get install apt debconf I've done quite a few; all went reasonably well, though I've been using debian for a while now; my pain tolerance may be a little higher. -- Nathan Norman - Staff Engineer | A good plan today is better Micromuse Ltd. | than a perfect plan tomorrow. mailto:[EMAIL PROTECTED] | -- Patton pgpdKcQaklaeV.pgp Description: PGP signature
Re: Recommended approach for installing Woody
Joey Hess([EMAIL PROTECTED]) is reported to have said: Scott Henson wrote: I really would not recomend installing potato then dist-upgrading. Having tried that several time, I could never recomend that. How long ago, what went wrong, and did you report bugs? We put a lot of effort into making upgrades to woody work well. I have 3 boxen converted from potato to woody. On one box (the potato converted from slink box), atd would not start. I never filed a bug report but did ask about it on this list, with no results. Joey's question reminded me of the problem and I just found the cause. In the slink/potato/woody box the /var/spool/cron/ permissions were 700 on the 2 boxes that had Potato installed from potato CD's the permission of /var/spool/cron/ were 755. All work fine now. That one problem, probably caused by the slink-potato upgrade was the only problem encountered when I went from potato to woody. I used Bunks listings and apt-get dist-upgrade(d) with no problems to speak of. Debian (Apt) Rules -- Southern DOS: Y'all reckon? (Yep/Nope) ___
Re: Recommended approach for installing Woody
On Thu, 7 Feb 2002 15:04:34 -0500 (EST) Ray Bowles [EMAIL PROTECTED] wrote: *** On Thu, 7 Feb 2002 at 12:33pm Ron Johnson shared this with the class:: One suggestion might be to do: apt-get -d dist-upgrade apt-get --fix-broken --show-upgraded dist-upgrade call me a newbie, but what would the exact lines be that someone should add to their sources.list file to do this from 2.2_rev5 and go up to woody? Here's mine: deb http://non-us.debian.org/debian-non-US woody/non-US main contrib non-free deb-src http://non-us.debian.org/debian-non-US woody/non-US main contrib non-free deb http://wpila.org/debian/ woody main non-free contrib deb-src http://wpila.org/debian/ woody main non-free contrib -- ++ | Ron Johnson, Jr.Home: [EMAIL PROTECTED]| | Jefferson, LA USA http://ronandheather.dhs.org:81| || ! As I like to joke, I may have invented it, but Microsoft | | made it popular David Bradley, regarding Ctrl-Alt-Del | ++
Re: Recommended approach for installing Woody
Before getting to the steps below how would one go about getting around the issue of my Microsoft Natural Pro Keyboard and Wireless Intellimouse Explorer not working in the install screens of 2.2_rev5. I can press enter at the boot: prompt when the CD boots up, but the first screen locks up. I think it is just a CONTINUE prompt. I'm assuming this is because they are USB devices. *** On Thu, 7 Feb 2002 at 1:39pm Ron Johnson shared this with the class:: On Thu, 7 Feb 2002 15:04:34 -0500 (EST) Ray Bowles [EMAIL PROTECTED] wrote: *** On Thu, 7 Feb 2002 at 12:33pm Ron Johnson shared this with the class:: One suggestion might be to do: apt-get -d dist-upgrade apt-get --fix-broken --show-upgraded dist-upgrade call me a newbie, but what would the exact lines be that someone should add to their sources.list file to do this from 2.2_rev5 and go up to woody? Here's mine: deb http://non-us.debian.org/debian-non-US woody/non-US main contrib non-free deb-src http://non-us.debian.org/debian-non-US woody/non-US main contrib non-free deb http://wpila.org/debian/ woody main non-free contrib deb-src http://wpila.org/debian/ woody main non-free contrib -- ++ | Ron Johnson, Jr.Home: [EMAIL PROTECTED]| | Jefferson, LA USA http://ronandheather.dhs.org:81| || ! As I like to joke, I may have invented it, but Microsoft | | made it popular David Bradley, regarding Ctrl-Alt-Del | ++ -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED] Ray -- Do not follow where the path may lead. Go instead where there is no path and leave a trail.
Recommended approach for installing Woody
What's the recommended approach for installing Woody these days? Is is still best to install a minimal Potato then dist-upgrade, or is there a better way. - Chris __ Do You Yahoo!? Everything you'll ever need on one web page from News and Sport to Email and Music Charts http://uk.my.yahoo.com
Re: Recommended approach for installing Woody
On Wed, 2002-02-06 at 22:04, Chris Kenrick wrote: What's the recommended approach for installing Woody these days? I really would not recomend installing potato then dist-upgrading. Having tried that several time, I could never recomend that. What I did is got some woody disks and did a regular install. Now what I would recomend is useing the new net install CD's. I basically did that useing the regular CD's. The real advantage that I see is the smaller image. But I would really recomend that you install woody straight. You will save yourself so much pain. -- -Scott Henson [EMAIL PROTECTED]
Installing Woody from CD
Hi Whats the current status of the Woody CDs. I have downloaded all 8 dated the last week in January, if I actually blow CDs of these will I actually be able to do a clean install of Woody. I just wanted to cjeck before I wasted 8 CDRs. Thanks Pat -- --- Pat Colbeck E-mail: [EMAIL PROTECTED] Tel:I'm not telling ---
