Re: Linux 2.4.5-ac21
> 2.4.5-ac21
> o Fix pnpbios compile failure and add docking (me)
> station hotplug (/sbin/hotplug dock)
gcc -D__KERNEL__ -I/usr/src/linux/include -Wall -Wstrict-prototypes -Wno-trigraphs -O2
-fomit-frame-pointer -fno-strict-aliasing -fno-common -pipe
-mpreferred-stack-boundary=2 -march=athlon -DEXPORT_SYMTAB -c pnp_bios.c
pnp_bios.c: In function `pnp_dock_event':
pnp_bios.c:442: `hotplug_path' undeclared (first use in this function)
pnp_bios.c:442: (Each undeclared identifier is reported only once
pnp_bios.c:442: for each function it appears in.)
pnp_bios.c: In function `pnp_dock_thread':
pnp_bios.c:496: warning: `d' might be used uninitialized in this function
pnp_bios.c: At top level:
pnp_bios.c:597: warning: `pnp_bios_exit' defined but not used
{standard input}: Assembler messages:
{standard input}:64: Warning: indirect lcall without `*'
{standard input}:135: Warning: indirect lcall without `*'
{standard input}:188: Warning: indirect lcall without `*'
{standard input}:229: Warning: indirect lcall without `*'
make[3]: *** [pnp_bios.o] Error 1
make[3]: Leaving directory `/usr/src/linux/drivers/pnp'
make[2]: *** [first_rule] Error 2
make[2]: Leaving directory `/usr/src/linux/drivers/pnp'
make[1]: *** [_subdir_pnp] Error 2
make[1]: Leaving directory `/usr/src/linux/drivers'
make: *** [_dir_drivers] Error 2
I'm using gcc-2.95.6 (Mandrake 8.0) and binutils 2.10.1.0.2.
--
Garett
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [EMAIL PROTECTED]
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Re: 2.4.4 breaks dhcpcd with Realtek 8139
> I'm plugged in to a cable modem, with the DHCP server at the ISP. The > server requires the MAC address to be registered, so sending the DHCP > request with a different MAC address could cause the symptoms. I doubt > it's a timing problem - replacing the 8139 driver with the 2.4.3 version > but otherwise using the distributed 2.4.4 makes DHCP work as expected. I meant to get back sooner. I'm also plugged into a cable modem (though trhough a 5 port hub). Same symptoms for me. -- Garett - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Re: 2.4.4 breaks dhcpcd with Realtek 8139
On Sat, 28 Apr 2001, Michael F Gordon wrote: > dhcpcd stops working if I install 2.4.4. Replacing the 2.4.4 version of > 8139too.c with the 2.4.3 version and leaving everything else exactly > the same gets things working again. Configuring the interface by hand > after dhcpcd has timed out also works. Has anyone else seen this? I noticed this in 2.4.3-acX series as well. But here's the funny part: When dhcp starts up during bootup it doesn't work. But as soon as I log in and do a su -c '/etc/rc.d/init.d/network restart' there's instant success! This is on Mandrake 8.0 It doesn't make much sense to me. -- Garett > ISC DHCP 2.0, kernel compiled with gcc 2.95.2 > > lspci: > 00:12.0 Ethernet controller: Realtek Semiconductor Co., Ltd. 8139 (rev 10) > > Boot messages with 2.4.3 version: > 8139too Fast Ethernet driver 0.9.15c loaded > PCI: Found IRQ 5 for device 00:12.0 > eth0: RealTek RTL8139 Fast Ethernet at 0xc9804f00, 00:10:a7:05:8e:da, IRQ 5 > eth0: Identified 8139 chip type 'RTL-8139C' > > Boot messages with 2.4.4 version: > 8139too Fast Ethernet driver 0.9.16 > PCI: Found IRQ 5 for device 00:12.0 > eth0: RealTek RTL8139 Fast Ethernet at 0xc9804f00, 00:10:a7:05:8e:da, IRQ 5 > eth0: Identified 8139 chip type 'RTL-8139C' > > > > Michael Gordon > - > To unsubscribe from this list: send the line "unsubscribe linux-kernel" in > the body of a message to [EMAIL PROTECTED] > More majordomo info at http://vger.kernel.org/majordomo-info.html > Please read the FAQ at http://www.tux.org/lkml/ > - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Re: [PATCH] Single user linux
> that also explain why win95 user doesn't want to use NT. not > because they can't afford it (belive me, here NT costs only > us$2), but additional headache isn't acceptable. I'm going to speak from experience: My mother, who is the biggest windoze fan on the face of the universe, got fed up with win98 and decided to move to win2k. The hole "multi-user" thing doesn't bother her in the slightest. She has a non-admin account for herself "karen". You want a better example? My little cousin is not much into computers but he uses one enough to check mail, surf the web etc... Like many win98 users he was re-installing it about once a month. He finally got so fed up he asked me to install Linux for him! He is now very happy. He doesn't care about the fact that he has to type in his user name. He even doesn't know any shell commands. He would probably actually get concerned if he had to use root always because that would reveal the same problems that he was having with win98. There's a lot of things you can do to make Linux easier for newbies. None of them involve hacking the kernel. Have you tried Linux-Mandrake 8.0 yet? -- Garett Spencley - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
